Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Update: I just noticed I have the same issue with the trash can button not eking in the photos app when trying to delete. Anyone else?
 
Update: I just noticed I have the same issue with the trash can button not eking in the photos app when trying to delete. Anyone else?
the display should be operating fine without issues once you get pass the lock screen/notification screen. the problem only persist on those two screens.
 
Mine works perfectly. I use the Speck Presidio Pro case, no protector (not since the iPhone 4s). The light button is a little odd, as I'm coming from an iPhone X with Force Touch. It makes a nice clicking noise though to show the toggle.
 
the display should be operating fine without issues once you get pass the lock screen/notification screen. the problem only persist on those two screens.
Haha. Yah. I’ve gone back to try and duplicate the issue with trash can button. It now seems to be working as normal. I must have been doing something odd. Oh well. So yes, as now it’s only on the Lock Screen. Thanks for the reply.
 
Mine works perfectly. I use the Speck Presidio Pro case, no protector (not since the iPhone 4s). The light button is a little odd, as I'm coming from an iPhone X with Force Touch. It makes a nice clicking noise though to show the toggle.
The problem only happens when you have a case and also a screen protector applied to your phone. If you have either one on your phone but not both, you won’t experience the issue
 
Thats crazy. When i have to wear a mask and face id won‘t work, i can‘t type in the pin code by one hand. I have to use both, because one doesn‘t get completely recognized.

Out of Lockscreeen everything else works fine.

So it is 100% a bug?!
 
Some Twitter discussion was suggesting that the issue might be with the official apple cases specifically. I’m seeing this issue while using the Apple Silicone Case. Touch sensitivity seems to be as expected with the case removed.
 
If you have a case and no screen protector, it works fine. If have a screen protector and no case, it works fine. It’s when you try and use both at once that the problem shows.
Why is it that my 12 mini works completely fine after I unlock the phone? The only time I have issues is when I am on the lockscreen and trying to get into the phone. Both the swipe up AND the keypad don't work very well. I can log in pretty decently on the keypad when I use my finger nail to punch in the passcode.
 
Some Twitter discussion was suggesting that the issue might be with the official apple cases specifically. I’m seeing this issue while using the Apple Silicone Case. Touch sensitivity seems to be as expected with the case removed.
I have an otterbox that is magsafe compatible and I am having the same issue.
 
This is also affects the ability to enter the passcode. With a case and screen protector on, entering the code with your thumb as you normally would is a no go. If you enter the code with the tip of your thumb or tip of another finger, it works. Same with the swipe. Swipe with the tip of the thumb or other finger and it works.
I use my finger nail to log in and it works. I also touch the bottom to swipe up for a second and then swipe up and that seems to help
 
i have the same problems on my mini. but i do have both a screen protector and a case. when i take the case off it works fine. i imagine if it continues to bother me, iʻll simply remove the screen protector and leave the case on.
 
Why it is that the touch sensitivity is completely fine with a case and screen protector on, but I am having issues swiping up and touching the keypad on the lockscreen? I'm leaning more towards a firmware issue, not a case or screen protector issue.
 
Why it is that the touch sensitivity is completely fine with a case and screen protector on, but I am having issues swiping up and touching the keypad on the lockscreen? I'm leaning more towards a firmware issue, not a case or screen protector issue.

I haven't tested without a case/glass, but here's a guess: There's a palm rejection algorithm at work in the lock screen and notification center (shared functionality, shared code) and it's calibrated incorrectly for the Mini. Or it could be any part of the code that works with touch/gestures in those screens. Impossible to say.

If that's at least approximately true, they need to ship a supplemental software update to fix this. I cannot imagine a mechanism that would make this a hardware problem, since it works flawlessly in every other screen. Luckily it's still mostly usable in the lock screen too.

I called Apple Support. They didn't know about this or pretended not to know, but promised to write an incident report. I would suggest people give them a call and ask to do the same. They will suggest a reboot, full reset etc. but no need to follow those orders, unless you want to. Just make sure they'll report this, so the engineers get the memo. It's also a good idea to use the feedback form. The more noise people make, the faster a fix arrives. https://www.apple.com/feedback/
 
I haven't tested without a case/glass, but here's a guess: There's a palm rejection algorithm at work in the lock screen and notification center (shared functionality, shared code) and it's calibrated incorrectly for the Mini. Or it could be any part of the code that works with touch/gestures in those screens. Impossible to say.

If that's at least approximately true, they need to ship a supplemental software update to fix this. I cannot imagine a mechanism that would make this a hardware problem, since it works flawlessly in every other screen. Luckily it's still mostly usable in the lock screen too.

I called Apple Support. They didn't know about this or pretended not to know, but promised to write an incident report. I would suggest people give them a call and ask to do the same. They will suggest a reboot, full reset etc. but no need to follow those orders, unless you want to. Just make sure they'll report this, so the engineers get the memo. It's also a good idea to use the feedback form. The more noise people make, the faster a fix arrives. https://www.apple.com/feedback/
I put in a Feedback form on the apple website. Hopefully everyone else on this forum does the same thing.
 
I could buy that's it's a grounding issue... over the past 40+ years of Apple products not doing grounding right has been the #1 issue on their products (with until recently #2 being using a poor capacitor).

It's like there's an old-timer somewhere @ Apple they can't get rid of that partied too much the weekend before they covered grounding in EE university.

/s
 
I could buy that's it's a grounding issue... over the past 40+ years of Apple products not doing grounding right has been the #1 issue on their products (with until recently #2 being using a poor capacitor).

Hey, they could then fix it with ... a bumper? Like the last time we had square phones. :p

More seriously though: could you please cite a source for grounding being a #1 issue over 40 years? I do remember getting an occasional jolt from my 2008 Mac Pro back in the day, at the time plugged into a not-too-well-grounded wall socket. Using a grounded socket fixed that. But those were the days, and this is a wireless device.

Specifically: if it's a grounding issue (hardware and physics), how come it goes away when the phone is unlocked by its software (= computation and code)? What's the reasoning behind that?

I haven't built an Apple 1 and couldn't fix an old TV at gunpoint ... but it doesn't sit well in my mind, how a grounding issue would not affect all apps.

I'm betting my 1 cent towards a 14.2.1 supplemental update rather than a total recall of all phones due to a hardware problem.
 
  • Like
Reactions: Sparkletouch
Hey, they could then fix it with ... a bumper? Like the last time we had square phones. :p

More seriously though: could you please cite a source for grounding being a #1 issue over 40 years? I do remember getting an occasional jolt from my 2008 Mac Pro back in the day, at the time plugged into a not-too-well-grounded wall socket. Using a grounded socket fixed that. But those were the days, and this is a wireless device.

Specifically: if it's a grounding issue (hardware and physics), how come it goes away when the phone is unlocked by its software (= computation and code)? What's the reasoning behind that?

I haven't built an Apple 1 and couldn't fix an old TV at gunpoint ... but it doesn't sit well in my mind, how a grounding issue would not affect all apps.

I'm betting my 1 cent towards a 14.2.1 supplemental update rather than a total recall of all phones due to a hardware problem.
Well I was meaning the comment as more tongue-in-cheek than statistical fact (why i bolded the /s at the bottom)...

By the way a simple example of poor grounding from moons ago is the design of the "in-adapter" plug on the MB/P power supplies vs. the corded... A OCD engineer would have carried out the ground.


On the capacitor side the clearest example was the original AirPort base station... man they really used a el-cheapo cap on that one (which when it finally popped was replaceable by those who could unsolder/solder).

When it comes to layout, parts, signal traces, etc I'm very OCD and tend to really exceed the need... but I don't have to worry about every penny of costs and designing for the absolute least volume/lowest cost to mfg. device.

Anyway, they've certainly upped their game, but no one is perfect and if you push it too far you can get a kick in the butt... physics will always win and those electrons can be rascally.
 
I could buy that's it's a grounding issue... over the past 40+ years of Apple products not doing grounding right has been the #1 issue on their products (with until recently #2 being using a poor capacitor).

It's like there's an old-timer somewhere @ Apple they can't get rid of that partied too much the weekend before they covered grounding in EE university.

/s
How would an old timer have partied any harder than a younger person especially today with heavy pill popping counts?! I went to parties some in the 90’s but started being the old guy (barely) in late 2000’s and the difference is night & day. 90’s ppl would pop 1 at a time, maybe 2 an entire night if you had a dud. These days kids pop like it’s Pez or PacMan on a power pill binge! They also sound like MashMouth from afar Albert too! Me I’d rather just dance to the music always have.
 
So what’s the consensus? If it’s a hardware issue I’d rather return this iPhone and wait for them to potentially release a revised version. Signed up to an expensive plan and don’t want a phone that potentially has a hardware issue.
 
I’d bet my last nickel it’s hardware. The moment you say conductivity I say to myself, “Coming up tonight on Eyewitness News at 11, Apple recalls hundreds of thousands of iPhones due to a hardware issue”
 
Mine was fine with a case on. When I put on the screen protector yesterday I started having issues. I googled it and found this thread.
 
Mine has just arrived. Silicone clear case from Torras, no issues whatsoever 💁‍♂️
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.