iPhone 12 mini Bugs!

-

 

I just upgraded to the new iPhone 12 mini, and even though I was initially impressed, I quickly ran into some bugs, a few of which are pretty serious. Many of them relate to the phone not recognizing button presses from the lock screen, so hopefully these all have the same root cause.

  • Unable to answer phone calls! Kind of important for a phone to be able to answer incoming calls. My phone was locked at the time, and when presented with the "Swipe to answer" control, the phone did not react to my attempts to swipe to answer the call.
  • Buttons on Pin Screen are unresponsive. When you reboot your phone, you're required to enter your pin, even if you have Face ID enabled. Well, the pin number buttons are unresponsive, often requiring several presses to register...if at all. I had to hard reboot my phone a couple of times to get it to the point where it was, at the most, semi-responsive.
  • Buttons on the Lock Screen are unresponsive. This is probably the same issue as mentioned above. From the lock screen, the flashlight and camera buttons rarely register presses. The issue is not my screen protector, as the same areas of the screen function perfectly when the phone is unlocked.
  • Can't hang up phone call. When making a phone call, the button to end the call is unresponsive. Sometimes it works after multiple presses, other times you just need to wait for the other person to hang up first.
  • The camera shutter sound effect when taking pictures using "Portrait" style ignores the volume setting and plays very loud. When taking pictures the "Portrait" style, the camera shutter sound effect will play very LOUDLY regardless of how high or low the volume is currently set. Setting the camera style to a different style and taking another picture does not produce the same loud sound effect.
It's understandable for some bugs to slip by and make it into production, but some of these are serious (I can't answer my phone???) and I can't believe they weren't caught earlier. Hopefully, Apple will resolve these and release a fix soon.

Update:
A few days after posting this, I chatted with Apple support, and the support rep had not heard of the problems I was having. He scheduled an appointment for someone to call me later that night. They sent me an email confirmation of the scheduled call.

Nobody ever called. And I didn't receive any sort of apology or acknowledgement of that. Just...no call. Nothing.

A few days later, Apple finally released iOS 14.2.1, which corrected the lock screen problems. Of the problems I listed above, only the "shutter sound" problem remains. However, to the best of my knowledge, Apple never acknowledged these problems anywhere other than in the release notes to iOS 14.2.1. Some sort of announcement letting their customers know they were aware of the problem and working on it would have been nice. Instead, customers had dysfunctional phones for a week, wondering what was going on.


Comments

Post a Comment

Popular Posts

Resolving the "n timer(s) still in the queue" Error In Angular Unit Tests

-
A few months ago one of the developers I work with ran into the below error in an Angular unit test: 1 timer(s) still in the queue The fix was to specify a particular amount of time in the tick() call as shown below: it( 'should set accountConfirmationDetails when getAccountConfirmationDetails is called' , fakeAsync(() => {          // Arrange          let  spyGetAccountConfirmationDetails = spyOn(accountService,  'getAccountConfirmationDetails' )         .and         .returnValue(Promise.resolve(AccountMockData.mockAccountConfirmationDetails));                    // Act         fixture.detectChanges();         tick(15000);          // Assert         expect(spyGetPaymentConfirmationDetails).toHaveBeenCalled();           expect(comp.zone).toBe(42);           expect(comp.hasValidProfile).toBeTruthy(); })); Hoping this helps someone!
Read more

How to Get Norton Security Suite Firewall to Allow Remote Desktop Connections in Windows

-
Image
I ran into an issue recently with RDP connections being blocked by the firewall in Norton Security Suite. I checked the traffic rules under Settings > Firewall > Traffic Rules  and found that it was enabled by default (and couldn't be edited): But during further research, I found  this page  on Norton's support site which discusses the different trust levels of networks and mentions that, for the Public trust level, "This setting also blocks remote desktop connections by default.". I checked my network's trust level, and sure enough, it was set to Public (I'm not sure how/why). (Sidebar: Notice in the screenshot above that allowing Remote Desktop for Public Networks is defaulted to Allow , though that rule is not active). Here's what my network trust level looks like now after changing the setting to Private (accessible under Settings > Firewall > General Settings > Network Trust ): After changing the network trust level t
Read more

Silent Renew and the "login_required" Error When Using oidc-client

-
I recently implemented the Silent Renew functionality of oidc-client in an Angular application I work on, and was getting reports that the users' tokens were still expiring. This made no sense to me as I'd verified the code was working during development, but yesterday I found the problem and am hoping it will save someone some time. The error we were getting back was "Error from signinSilent: login_required". This indicates that the user's session is no longer active on IdentityServer and they must re-authenticate -- which, of course, is what we're trying to prevent by using Silent Renew. In our case, the problem wasn't with the Silent Renew functionality, but rather the user's session was expired. The reason why  it was expired was because, for some reason, we were setting the session length to 15 minutes instead of the default 10 hours . What was occurring was that Silent Renew was attempting to renew a token after 55 minutes (60 minutes expirat
Read more

Fixing the "Please add a @Pipe/@Directive/@Component annotation" Error In An Angular App After Upgrading to webpack 4

-
I'm currently in the process of upgrading an Angular application which does not  use the Angular CLI from webpack 2 to webpack 4. The incremental upgrade from webpack 2 to 3 was easy, but once I made the jump from 3 to 4, I encountered a lot of problems. I went through them one by one, but the one that had me stumped was the following: Unhandled Promise rejection: Unexpected value 'MakePositivePipe' declared by the module 'SharedModule'. Please add a @Pipe/@Directive/@Component annotation. ; Zone: <root> ; Task: null ; Value: Error: Unexpected value 'MakePositivePipe' declared by the module 'SharedModule'. Please add a @Pipe/@Directive/@Component annotation. The code was transpiling/compiling fine, but this error was occurring when I'd navigate to a page containing this pipe. This code has worked fine under webpack 2 and 3. I made sure that the pipe was being set up as a declaration , which it was. What finally  corrected the issue for me w
Read more

How to Determine if a Column Exists in a DataReader

-
I recently had to work on something which required me to query a database, open the results in a DataReader, and check for the existence of a particular column. While the DataReader doesn't have a method to do this, with just a few steps I was able to accomplish this task. Here's how. First, the DataReader has a method named GetSchemaTable() , which returns a DataTable consisting of information regarding the data contained in the DataReader. The first column in this DataTable is named ColumnName , and its value is (obviously) the name of the column. Knowing this, we can loop through the rows in the DataTable, checking the ColumnName column for a value that equals the name of the column we're looking for. To this end, I wrote a static method in one of my classes which takes the DataReader and the name of the column being sought: (C#) public static bool HasColumn(DbDataReader Reader, string ColumnName) {    foreach (DataRow row in Reader.GetSchemaTable().Rows)    {       
Read more