I will tru that option but eish I am afraid of more problems.What about actually reinstalling iOS 10.3 (via iTunes, perhaps even using recovery mode or something like that)?
I will tru that option but eish I am afraid of more problems.What about actually reinstalling iOS 10.3 (via iTunes, perhaps even using recovery mode or something like that)?
After updating to iOS 10.3 the home button has become unresponsive, sometimes needing a second click to exit an application. The first press does register on the phone since I can feel it vibrate but it does nothing. This is entirely random and I never know if one press will be enough to exit an application. This behavior started after the update.
Phone: iPhone 7 Plus
Updated from: 10.2.1
Updated how: Over the air
Try to calibrate your home button following these steps:
1. Launch any app such as Stocks, Weather, etc. that comes pre-installed with your iPhone or iPad.
2. Press and hold the Power (Sleep/Wake)button until you “slide to power off” slider appears on the screen.
3. Release the power button and now press and hold the Home button until the “slide to power off” slider goes away.
Hope that helps.
[doublepost=1491108937][/doublepost]Same happening to me after the ios 10.3 update. The home button needs second click to perform the exit screen function. I think this is a software related bug which apple will be going to fix. The only problem is, are they aware of this bug? Well, I think they might be as people have also posted on apple's discussion page.After updating to iOS 10.3 the home button has become unresponsive, sometimes needing a second click to exit an application. The first press does register on the phone since I can feel it vibrate but it does nothing. This is entirely random and I never know if one press will be enough to exit an application. This behavior started after the update.
Phone: iPhone 7 Plus
Updated from: 10.2.1
Updated how: Over the air
Try to calibrate your home button following these steps:
1. Launch any app such as Stocks, Weather, etc. that comes pre-installed with your iPhone or iPad.
2. Press and hold the Power (Sleep/Wake)button until you “slide to power off” slider appears on the screen.
3. Release the power button and now press and hold the Home button until the “slide to power off” slider goes away.
Hope that helps.
Where did you find these steps to "calibrate" the home button?
Did that.. It helps for few minutes and again same problem happening!
To be fair, some people having a similar type of issue at some point in the past with some older devices doesn't necessarily mean that what some people might be experiencing now is the same or related in some way.From a dark place that will consume your soul! Executing the 3 steps I posted earlier is the beginning!
This problem is not new. If you google it you'll find posts from 2011 or maybe even earlier. I had the same issue with iPhone 4S back in the days and I had it now with iPhone 6 after updating from 10.2.1 to 10.3. Both times calibrating the home button fixed the issue for me.
If you are suspicious about what I wrote try googling "calibrate home button". I'm sure you'll find a source that you can trust
You can try rebooting first then execute the steps again. Can't guarantee that helps tho. For me reboot wasn't needed but I saw some old article that suggest this additional step.
Where did you find these steps to "calibrate" the home button?
To be fair, some people having a similar type of issue at some point in the past with some older devices doesn't necessarily mean that what some people might be experiencing now is the same or related in some way.
I tried this but it had no effect for me. I've seen one other user get this problem fixed by doing a Clean Install via iTunes. I'm not that desperate yet so will hold off for a bit longer before going that route.Tried everything and the only thing that seems to help is by disabling home button press and hold function. Settings - General - Accessibility - Home Button..
The issue is not resolved on 10.3.1.iOS 10.3.1 was just released, perhaps that might somehow resolve this issue for those who have been experiencing it?
iOS 10.3.1 was just released, perhaps that might somehow resolve this issue for those who have been experiencing it?
Might want to report it as an actual bug at http://bugreport.apple.comSadly I can also confirm that 10.3.1 does not resolve this issue.
I would like to encourage everyone that has this problem to submit their feedback to Apple at the following link:
http://www.apple.com/feedback/iphone.html
I get the feeling that this problem is not widespread and the more people that submit feedback, the better. Hopefully we can make Apple aware of the problem.
As of this writing Apple is still signing iOS 10.2.1, so anyone that wants to downgrade should do so ASAP.
Whats the effective difference between the bug portal at http://bugreport.apple.com as compared to the feedback submission.Might want to report it as an actual bug at http://bugreport.apple.com
Not likely that the same teams are involved. In the case of bug reports there's probably a more technical team following up on those, while in the case of general feedback it probably goes through some people that are more in the public relations and customer service type of positions, and it's not likely treated the same as bug reports.Whats the effective difference between the bug portal at http://bugreport.apple.com as compared to the feedback submission.
Dont both of them get examined by the same team.
Happened to me once on my iPhone 6 after updating to 10.3. Needed to press the home button a second time to exit the settings app but it hasn't happened again since.
As is the case with most updates, it's just fine and stable for most.Sticking with 10.2 until 10.3 is more stable
Might want to report it as an actual bug at http://bugreport.apple.com
Anyone can register as a free developer to report and follow up on bugs.Thanks, did not know about this. Will report it.
EDIT:
Are you sure anyone can use this to submit a bug report? Going to that site it asks me to login and then says "The account does not exist". Was thinking I might have to be a developer or Beta tester or something?
EDIT:
Yes, unfortunately one has to be a registered developer to use this.