Could maybe have been in the hardware section but, has anyone had this issue. I recently upgraded to iPhone11 and ever since my phone refuses to stay locked. Raise to wake is off but even if I'm not getting notifications which obviously opens the locked screen it just keeps unlocking. Not to the home screen but the lockscreen and reads previous notifications that may have arrived 10/15 minutes before and I haven't cleared. It's very odd. Tried a hard reset with no luck. Occasionally, it will stay locked but no where near all the time. I'm on iOS 13.5.1.
By Lee, 6 June, 2020
iOS and iPadOS
Have had this issue ever
Have had this issue ever simce IOS 13 when playing any kind of audio media with any app. I muted my phone first, which was inconvenient of course but worked at leastfor a while, until I found keeping the volume no higher than 60% is the better workaround.
yes me too
Yes I have had this issue as well since IOS 13.0 and I also figured out the volume work around. It can be incredibly annoying but it doesn't happen all the time. I have iPhone 8 and usually use wired headphones, doesn't happen on speaker. Also used to happen on my old iPhone SE 1G and I hoped it would not happen on my new phone but it does.
Exactly, I also have an 8. It
Exactly, I also have an 8. It never happens with speakers on, and neither does it with my bluetooth headset. The volume is fine but where I'd have it on 60 %on the wired headset, it's on 38 or 40 % on the bluetooth one.
Chris G, thanks for this. Raise to wake was off. Hadn't thought about the other part. Done that now. So lets see. Good thought though.
Tap To Wake
You might also want to make sure that tap to wake is off. This setting is under accessibility and touch.
I've had raise to wake off
I've had raise to wake off for some time, can see no tap to wake, and VO hasn't spoken notifications reliably when always speak notifications was on, mor does it reliably not speak them now that it is off.
Thanks Earl. I've never seen that option. I believe you may have solved this. That would also explain why despite what I said my battery didn't seem to be affected. Why you have that option in the first place seems silly if you have raise to wake anyway and it must default to "on" as well which is equally daft.
Raise to wake and tap to wake are 2 different settings. Most people know about raise to wake but a lot of people don't seem to know about tap to wake. The setting for tap to wake is located under accessibility then look for the heading that says physical and motor. The first option under that heading is touch and if you go in there, you will find the tap to wake option.
I don't really see the need for both raise to wake and tap to wake. Raise to wake should be enough for anyone who wants it. For the longest time I could never figure out why my iPhone 11 kept unlocking. I knew I had raise to wake off, but then a friend told me about tap to wake. As soon as I turned it off, everything was fine.
I do not have tap to wake in accessibility>touch, nor anywhere else in settings. I have even done a search for it in settings and it is not there. It sounds like that would be the fix but I don't have it! Very annoying.
iPhone 8, IOS 13.5.
To Chris R
Chris, I still have my old iPhone8 and can confirm touch to wake does not exist. Presumably only in newer phones. Weird though if you're having this issue if it isn't an option.
Yep. Tap to wake is only on
Yep. Tap to wake is only on the newer phones that don't have a home button.
I've never had the issue you describe, but I don't use wired headphones anymore.
I think It is the Volume thing.
I think on the older phones it is something to do with the volume being over 60%. As mentioned above this causes the screen to continually wake and sleep in a loop when media is playing unless the volume is turned down. It is as if there is a message that appears over 60% that keeps waking the screen but VO can't see it. Maybe something about prevent hearing damage at higher volumes. I don't know really but what ever it is it is very annoying when it happens.
It actually hasn't happened to me much recently since I switched to my new Lightning adapter setup but it still happens occasionally. Was more of a problem on my old SE.