Related
Hello,
I have recently upgraded from Cyanogenmod 10.1 to the latest Cyanogenmod 10.2-20130923 Nightly version and I am facing a problem with the lockscreen.
The lock screen has disappeared and the phone just won't lock. This problem has only happened after updating to the Android 4.3 via Cyanogenmod ROM. I have put the security option as well and tried every possible combination but it just won't show up. Even after setting up the PIN security the phone is still unlocked and it just opens in the homescreen after pressing power or home button.
Please give me a solution to this problem. All the other things seems to work fine.Has any one else faced the same problem?
Thanks,
Nimish
I have exactly same problem with 20130926 on jfltexx. Trying to solve it now.
See this:
There's a lock screen activation button on the quick settings (tiles that come down swiping down on the right side of the screen). It needs to be activated for lock screen to be active.
On logcat, this will only show as:
09-27 14:54:51.290 I/WindowManager( 716): No lock screen!
Either turn that button on, or add that button from settings and turn it on.
tapiov said:
See this:
There's a lock screen activation button on the quick settings (tiles that come down swiping down on the right side of the screen). It needs to be activated for lock screen to be active.
On logcat, this will only show as:
09-27 14:54:51.290 I/WindowManager( 716): No lock screen!
Either turn that button on, or add that button from settings and turn it on.
Click to expand...
Click to collapse
This still didn't fix the problem for me. Anyone else have any ideas? I tried changing the lock types but that had no effect either.
thebballkid said:
This still didn't fix the problem for me. Anyone else have any ideas? I tried changing the lock types but that had no effect either.
Click to expand...
Click to collapse
I was having the same problem, rebooted and it is now locking.
EDIT: Will work for a little while after rebooting and then goes back to not working.
Same
I also have the same issue where lock screen just stops engaging. It will work fine after a reboot but after a few hours it just stops locking.
This has been happening to me as well, and I just reboot whenever it happens. But, the strange thing is that I've noticed that whenever my phone reboots, I'll usually have a notification for app updates to download. I don't know if there is a correlation between the two things, but it just seems to happen too regularly for it to be a total coincidence. Anyone else have this happen?
Same problem on S3 i9305 LTE
Using CM 10.2 nightly 20131020.
Lock screen fails to appear on power button after working fine all day.
Reboot fixed it last time, but two reboots later tonight and it is still not appearing.
- "Power button instantly locks" option is ticked,
- pattern lock selected,
- auto lock after sleep set to immediate.
- PowerAmp lock screen is enabled but skips pattern lock on unlock request,
though sometimes it doesn't go into locked mode at all.
I've tried with PowerAmp lock screen completely disabled and also with the Android lock screen option ticked. No joy.
Similarly, I've tried adding the Lock Screen item to the Settings tiles and had no luck with that either.
Hope this is getting fixed soon...
---------- Post added at 09:42 PM ---------- Previous post was at 08:44 PM ----------
Interesting. I just upgraded to CM 10.2 nightly 20131024.
Had the same problem from first boot into that build.
I had Tasker running with a profile that is keyed to my house's WiFi SSID. I disabled Tasker but saw the same problem.
On a hunch, I disabled WiFi and a few seconds later I heard the little 'snict' noise of the lock working, followed by the lock screen kicking in. I've re-enabled WiFi and the screen is locking fine now.
Maybe some interaction with a Tasker profile with a WiFi context and keeps device open even if Tasker is disabled as it can still see the same WiFi SSID ?
Digging a little deeper, I was experimenting with Tasker and its only action is to produce an Alert saying "Home" if it sees my WiFi. Critically, the Action has "Show Over Keyguard" ticked. I've just gone through the process of unticking that option, saving the Action, exiting Tasker, dropping and re-enabling WiFi, (so now Lock screen works), and then rebooting (which causes the Tasker Action to create an alert), and the lock screen is working fine now.
So, kind of looks like going anywhere near that option in Tasker will balls up how the lock screen works, and will stick around even after Tasker has exited unless the criteria it is keyed on changes (i.e. the WiFi state).
Hope that helps someone!
fractos said:
Using CM 10.2 nightly 20131020.
Lock screen fails to appear on power button after working fine all day.
Reboot fixed it last time, but two reboots later tonight and it is still not appearing.
- "Power button instantly locks" option is ticked,
- pattern lock selected,
- auto lock after sleep set to immediate.
- PowerAmp lock screen is enabled but skips pattern lock on unlock request,
though sometimes it doesn't go into locked mode at all.
I've tried with PowerAmp lock screen completely disabled and also with the Android lock screen option ticked. No joy.
Similarly, I've tried adding the Lock Screen item to the Settings tiles and had no luck with that either.
Hope this is getting fixed soon...
Click to expand...
Click to collapse
Thanks!
Thank-you - this helped me today!
Couldn't for the life of me figure out why the lockscreen would stop working. I had an exit task on a Tasker profile with an Action where the "Show Over Keyguard" was on. Turning that to off solved the problem.
fractos said:
Using CM 10.2 nightly 20131020.
Lock screen fails to appear on power button after working fine all day.
Reboot fixed it last time, but two reboots later tonight and it is still not appearing.
- "Power button instantly locks" option is ticked,
- pattern lock selected,
- auto lock after sleep set to immediate.
- PowerAmp lock screen is enabled but skips pattern lock on unlock request,
though sometimes it doesn't go into locked mode at all.
I've tried with PowerAmp lock screen completely disabled and also with the Android lock screen option ticked. No joy.
Similarly, I've tried adding the Lock Screen item to the Settings tiles and had no luck with that either.
Hope this is getting fixed soon...
---------- Post added at 09:42 PM ---------- Previous post was at 08:44 PM ----------
Interesting. I just upgraded to CM 10.2 nightly 20131024.
Had the same problem from first boot into that build.
I had Tasker running with a profile that is keyed to my house's WiFi SSID. I disabled Tasker but saw the same problem.
On a hunch, I disabled WiFi and a few seconds later I heard the little 'snict' noise of the lock working, followed by the lock screen kicking in. I've re-enabled WiFi and the screen is locking fine now.
Maybe some interaction with a Tasker profile with a WiFi context and keeps device open even if Tasker is disabled as it can still see the same WiFi SSID ?
Digging a little deeper, I was experimenting with Tasker and its only action is to produce an Alert saying "Home" if it sees my WiFi. Critically, the Action has "Show Over Keyguard" ticked. I've just gone through the process of unticking that option, saving the Action, exiting Tasker, dropping and re-enabling WiFi, (so now Lock screen works), and then rebooting (which causes the Tasker Action to create an alert), and the lock screen is working fine now.
So, kind of looks like going anywhere near that option in Tasker will balls up how the lock screen works, and will stick around even after Tasker has exited unless the criteria it is keyed on changes (i.e. the WiFi state).
Hope that helps someone!
Click to expand...
Click to collapse
Same here. Had a Tasker task that was checked to show over keyguard (which I wanted). Unchecked that and the lockscreen has continued to work. Is this a bug with Tasker or CM?
Thx
tapiov said:
See this:
There's a lock screen activation button on the quick settings (tiles that come down swiping down on the right side of the screen). It needs to be activated for lock screen to be active.
On logcat, this will only show as:
09-27 14:54:51.290 I/WindowManager( 716): No lock screen!
Either turn that button on, or add that button from settings and turn it on.
Click to expand...
Click to collapse
Thx, that was it for me. CM10.2 Nigthly (15.11.) Galaxy Mini i9195:good:
Locking problems 10.2 nightly
SiggiSicher said:
Thx, that was it for me. CM10.2 Nigthly (15.11.) Galaxy Mini i9195:good:
Click to expand...
Click to collapse
Same problem for me. No tasker app installed. Using cm-10.2-20131127-nightly.
No way to lock the phone
Success
tapiov said:
See this:
There's a lock screen activation button on the quick settings (tiles that come down swiping down on the right side of the screen). It needs to be activated for lock screen to be active.
On logcat, this will only show as:
09-27 14:54:51.290 I/WindowManager( 716): No lock screen!
Either turn that button on, or add that button from settings and turn it on.
Click to expand...
Click to collapse
Woow It Worked!
neoruz said:
Woow It Worked!
Click to expand...
Click to collapse
Not for me
neoruz said:
Woow It Worked!
Click to expand...
Click to collapse
Inviato dal mio GT-I9300 utilizzando Tapatalk
dont work
same problem with my phone.. running nightly from today... my lockscreen is awaaaay (((
I probably found the problemi. A conflict with app Automate it pro. Disinstalled and look screen problem disappear
Inviato dal mio GT-I9300 utilizzando Tapatalk
Tasker is the issue for me
Running CM 10.2 on Galaxy S3 i535 (VZ). Disabled Tasker and phone locks as expected.
Still not working...
I have the same problem on the final version, installed over the holiday. Any word on fixes yet? I have not tried searching too deeply however this thread was very specific to my problem and thought it was most appropriate here.
10.2.0-d2spr here with no tasker installed.
Thanks!
jmbenedict said:
I have the same problem on the final version, installed over the holiday. Any word on fixes yet? I have not tried searching too deeply however this thread was very specific to my problem and thought it was most appropriate here.
10.2.0-d2spr here with no tasker installed.
Thanks!
Click to expand...
Click to collapse
I'm having the same problem, on the final version as well. I flashed about 3 hours ago
Is there any secret to making this work better to wake up the phone. I cannot seem to hit it right to get it to unlock. Sensitivity adjust?
I like the phone otherwise.
Tap the screen quickly and firmly in the same spot two times. I have no problems with it using that method.
Train wreck for me. Double tap is horrible! I started a return through Amazon, wondering if I should try a replacement first though. I have huge lag issues too on this phone.
I am having the problem with tap to open too. There are many reviews on Amazon detailing the same thing. I sent an email to Alcatel support asking if they would be addressing this issue. I am still deciding if I want to keep the phone.
Last couple of days I have had more instances of misses with this than I had the first couple of days. But still I feel I have had better luck with the double-tap.... than many others over here so far. Usually a firm tap, with your fingers bent and the fingernails almost hitting the glass, works pretty well. But at times, even a firm tap will not work, and I have noticed that un-setting the option ( in Settings -> Gestures ) and then setting it back again gets it going again. This and the lag with loading apps may be related , and I hope Alcatel release a 5.1 update soon.
I've only had an issue with this once and a reboot fixed it. I think in some cases people are not hitting the screen firmly and quickly. Also the may not be hitting the same spot as well. I have seen other phones that use the knock unlock gesture but with a knock code and maybe some people thought they could hit the screen where ever they wanted between the 2 knocks. I'm just guessing here.
steavis00 said:
Is there any secret to making this work better to wake up the phone. I cannot seem to hit it right to get it to unlock. Sensitivity adjust?
I like the phone otherwise.
Click to expand...
Click to collapse
what i did was disable the two incoming call option in gesture, now doubletap with no problem.
Turning off "Turn Over to Mute" seems to help with tapping to wake screen, but not tap to shut off screen.
Borghi said:
Turning off "Turn Over to Mute" seems to help with tapping to wake screen, but not tap to shut off screen.
Click to expand...
Click to collapse
in my phone wake and shut off works perfectly fine,and i have turn off mute and the alarm.
goseup said:
in my phone wake and shut off works perfectly fine,and i have turn off mute and the alarm.
Click to expand...
Click to collapse
I believe I have found the root cause of the problem. Right after I got the phone I installed Nova Launcher. I started playing around and tried switching back to the stock launcher. Immediately the double tap feature started to work consistently. Hopefully it will STAY working and Nova will update their launcher to support the double tap feature fully.
Borghi said:
I believe I have found the root cause of the problem. Right after I got the phone I installed Nova Launcher. I started playing around and tried switching back to the stock launcher. Immediately the double tap feature started to work consistently. Hopefully it will STAY working and Nova will update their launcher to support the double tap feature fully.
Click to expand...
Click to collapse
I doubt if the launcher is the issue. When the screen is off the launcher is not in control of the phone, the OS is in control. Also, I use Nova Prime and have only had 1 problem with Double Tap To Wake in the past 8 days.
Shodan5150 said:
I doubt if the launcher is the issue. When the screen is off the launcher is not in control of the phone, the OS is in control. Also, I use Nova Prime and have only had 1 problem with Double Tap To Wake in the past 8 days.
Click to expand...
Click to collapse
I partly agree with your statement. As I understand Nova Prime includes support for double tap. The free app does not. Using the free app I can double tap to wake the phone, but not to sleep. Using the stock launcher, both functions work perfectly. I tried installing the Google Now launcher and it was the same as the free Nova launcher. No double tap to sleep.
I am new to Xda (or forums in general), but I had tons of issues with the double tap to wake feature not working. This was a shame because everything else I loved about this phone (only other thing I would change is a slight processor boost; a Snappy 801 would be perfect). Anyways, I finally got around the issue by performing these steps:
1-In Settings, navigate to Gestures and make sure 'Turn over to mute' is unchecked and 'Turn over to activate' is disabled.
2-Don't know if this is mandatory, but I also disabled the Func shortcuts in the Lock Screen Settings as well.
3-Reboot the device and don't touch these settings again
For some reason, I think Alcatel's software was not appropriately tested with all of these functions enabled. I am not sure, I just know I am having much higher hit rates (works almost every time) after performing the above steps.
Hope it works for you guys.
Lastly, if the double tap starts having issues again, just run a reboot and it should fix it (I just had to reboot after 30+ hours of standby).
goseup said:
what i did was disable the two incoming call option in gesture, now doubletap with no problem.
Click to expand...
Click to collapse
YAY, THIS THING WORKS FOR ME, NOW IT DOESN'T LAG, D2W AND D2S, USING STOCK LAUNCHER, tried using other premium launchers, problem is smart lock doesn't work
THANKS
---------- Post added at 09:50 PM ---------- Previous post was at 09:43 PM ----------
works well now, the only thing we need is ROOT, unlocked bootloader is easy to achieved on this phone.
Borghi said:
I believe I have found the root cause of the problem. Right after I got the phone I installed Nova Launcher. I started playing around and tried switching back to the stock launcher. Immediately the double tap feature started to work consistently. Hopefully it will STAY working and Nova will update their launcher to support the double tap feature fully.
Click to expand...
Click to collapse
Nova has it's own double tap gesture. If you want it to turn off the screen then you will have to have it call a program like "screen off" to accomplish that. DT to wake is still handled by the lockscreen.
believe me i been looking for a way to make this double tap in look screen to work better, by accident i find out that tapping very lightly wake the phone all the time.
Double-tap not working for me. Running all stock, stock launcher.
Same here I can't get the double tap to work for anything, I tried turning off the features and func but nothing, my phone has its days where it works fine and other days where it just doesn't.
Sent from my 6045I using XDA Free mobile app
My original suggestion to fix the double tap was to reboot, but I found a much quicker way. Go under gestures and turn it off and on again. Seems to work every time it gets wonky.
i notice that D2W work almost perfect while the phone on charger ...so it may be power saving mode that make the digitizer off after several minutes???!!!
Hey all. I've been trying to use the new Quick Launch gesture (in advanced settings within the Wear app on my phone). I'd really like to use the gesture to quickly activate the flashlight when needed. Unfortunately the triggering Quick Launch with the "knock knock" gesture is hit or miss (mostly miss). Are any of you able to use this successfully and reliably? And, if so, do you have any suggestions or tips on how to consistently execute it? Thanks.
It says that you have to do it within 5 seconds of waking up the screen, maybe it's because of that? I can get it to work almost everytime
dumbdeniz said:
It says that you have to do it within 5 seconds of waking up the screen, maybe it's because of that? I can get it to work almost everytime
Click to expand...
Click to collapse
I swear I had been keeping that in mind every time and it just wasn't working consistently for me. Just turned it back on and tried again and now it seems to be working every time without fail. Thanks
It will only work right after you're screen turns on (within 5 seconds). It's useful if you need to launch something quick hands free. Best to use directly after your screen turns on from a lift to wake gesture.
It works from time to time for me. I have noticed it does not want to work especially when the battery is below 40%. I need to restart the watch and it starts working again. I also tried turning it off and then on again to see if this helps, but it did not.
I am so used to my OnePlus 9's AOD that I'm kind of surprised how terribly it seems to be implemented here and I'm hoping it's just being buggy...
First off, the AOD doesn't seem to work at all if I don't choose to have it displayed all the time (which is the first hint that this may be a bug as even the preview for tap or lift seems to suggest that the AOD should be popping up, not the lock screen as is happening right now).
Second, if I do have it displayed all the time, incoming notifications bring up the lock screen. My OnePlus shows a preview of that one specific notification while still on the AOD screen and it seems silly that Google isn't utilizing something similar. It is extremely handy to have a text come in, say with a 2FA code, and have the entire screen black besides a large preview that shows you that code. The way that it is working now, it wakes the lock screen, which is fine, except the message gets truncated so it often requires me to interact with the device even further to be able to see the full message.
I also tried turning off wake the screen for notifications to see if that triggers the AOD and... it just adds an icon to the AOD...
This is a huge downgrade in user experience if this is the normal expected behavior. I could have sworn my 3 XL handled it better than this but I haven't used it for awhile and I'm not at home where I could check it. Maybe I'll have to look into third party options.
Im not quite sure and your whole post. I as well had the Oneplus 9 pro. My Pixel 7 pro AOD works just fine. I double tap screen and goes directly to the AOD, which displays the Date(top left corner), the time that is big, the fingerprint icon and battery percentage. a tap of the screen brings up the lock screen. Face unlock and pin works directly to the home screen. Now I do have to say im using Nova Launcher as i can't stand that the dat and google search bar can't be removed.
schmeggy929 said:
Im not quite sure and your whole post. I as well had the Oneplus 9 pro. My Pixel 7 pro AOD works just fine. I double tap screen and goes directly to the AOD, which displays the Date(top left corner), the time that is big, the fingerprint icon and battery percentage. a tap of the screen brings up the lock screen. Face unlock and pin works directly to the home screen. Now I do have to say im using Nova Launcher as i can't stand that the dat and google search bar can't be removed.
Click to expand...
Click to collapse
Thanks. Sounds like I have a bug after all right now.
When you get a text or something, does it show an AOD notification with a preview like the OnePlus did or does it just show the lock screen?
I turned off screen on with new notification, I will have to check
Without screen on with new notification, I still get the notification and AOD stays on. Lock screen does not come on. So in other words, AOD works as it should.
EtherealRemnant said:
Second, if I do have it displayed all the time, incoming notifications bring up the lock screen. My OnePlus shows a preview of that one specific notification while still on the AOD screen and it seems silly that Google isn't utilizing something similar. It is extremely handy to have a text come in, say with a 2FA code, and have the entire screen black besides a large preview that shows you that code. The way that it is working now, it wakes the lock screen, which is fine, except the message gets truncated so it often requires me to interact with the device even further to be able to see the full message.
Click to expand...
Click to collapse
The AOD on my Pixel 4a works just like you describe the OnePlus AOD, it stays on the AOD but displays the message at the center for a few seconds, sounds like a bug (unless this changed on the 7 and 7 pro for some reason).
Interesting. Thanks to both of you. Hopefully it gets resolved at some point. I'm in no mood to factory reset and set everything up again so I'll just deal with it for now.
EtherealRemnant said:
Interesting. Thanks to both of you. Hopefully it gets resolved at some point. I'm in no mood to factory reset and set everything up again so I'll just deal with it for now.
Click to expand...
Click to collapse
Yeah Im trying to adjust to not having Recent Apps, home and Back buttons on the screen! lol
schmeggy929 said:
Yeah Im trying to adjust to not having Recent Apps, home and Back buttons on the screen! lol
Click to expand...
Click to collapse
You can get those back if you want. Settings > System > Gestures > System navigation and change back to 3-button.
Do you have the wake screen setting toggled? It's possible that's why
EtherealRemnant said:
You can get those back if you want. Settings > System > Gestures > System navigation and change back to 3-button.
Click to expand...
Click to collapse
Thanks, I literally just found it as I was getting your reply notification!
bosox284 said:
Do you have the wake screen setting toggled? It's possible that's why
Click to expand...
Click to collapse
I have tried messing with all four settings in all sorts of configurations to see if I can get it to work properly and have been totally unsuccessful. It seems I have just stumbled on some kind of bug.
EtherealRemnant said:
I have tried messing with all four settings in all sorts of configurations to see if I can get it to work properly and have been totally unsuccessful. It seems I have just stumbled on some kind of bug.
Click to expand...
Click to collapse
Hey, I do have the same bug. Did you manage to fix it ?
I am rooted + I use Kirisakura kernel
I don't think this would be the cause but we never know ...
Repear88 said:
Hey, I do have the same bug. Did you manage to fix it ?
I am rooted + I use Kirisakura kernel
I don't think this would be the cause but we never know ...
Click to expand...
Click to collapse
It was resolved after I did a factory reset and restored only SMS and apps (but not settings) from my Google backup.
EtherealRemnant said:
It was resolved after I did a factory reset and restored only SMS and apps (but not settings) from my Google backup.
Click to expand...
Click to collapse
Thx ! Damn it ...
I didn't restore anything ... I'll try before resetting (it's been only 2 days I have it ready XD)
schmeggy929 said:
Im not quite sure and your whole post. I as well had the Oneplus 9 pro. My Pixel 7 pro AOD works just fine. I double tap screen and goes directly to the AOD, which displays the Date(top left corner), the time that is big, the fingerprint icon and battery percentage. a tap of the screen brings up the lock screen. Face unlock and pin works directly to the home screen. Now I do have to say im using Nova Launcher as i can't stand that the dat and google search bar can't be removed.
Click to expand...
Click to collapse
Don't know if I understand you correctly. Do you have enabled AOD all the time (always show time and info)? If not, you double tap to show AOD and it's working fine? Do you have any other settings enabled (tap to check phone, etc)?
I have disabled AOD (always show time and info) and when I tap, it goes straight to lockscreen. Not sure but that change may have been introduced in one of the latest updates.
@EtherealRemnant same question to you
In my case as it works right now:
When I enable AOD (always show time and info), it is showing all the time. When I disable that, it's not. When I tap on the screen (when AOD is disabled), it goes straight into lockscreen. When I receive a notification, AOD shows for a short moment.
What I would like to achieve (dunno if that's possible) would be to have tap to show AOD instead of lockscreen (with AOD not showing all the time).
I understand what you would like to do( tap the screen to have AOD appear first. I cannot find anything like( temp AOD) in settings. The show time and info toggle is basically the master AOD switch. Either AOD all the time or disabled completely, nothing in between.
Same for me, after reading topics on reddit, I was thinking I wasn't a bug and I might misunderstood what op was saying.
@trawel to add to your statement, if you move slightly your phone, like lifting one side, the AOD should come, most of the time (sometimes screen stays black)
But yeah I also would like to be able to "tap to show AOD" so it won't unnecessarily unlock when it sees my face.
AOD = Always On Display...it's in the name...ALWAYS ON. I understand what you're looking for but then it would NOT be called AOD, but SOD = sometimes on display.
jaseman said:
AOD = Always On Display...it's in the name...ALWAYS ON. I understand what you're looking for but then it would NOT be called AOD, but SOD = sometimes on display.
Click to expand...
Click to collapse
We get the semantics but the point is that the AOD used to function differently. You used to be able to tap to get the AOD to come on and lifting the device used to always go to AOD FIRST. When I made this thread, I was not seeing the AOD at all most of the time. A factory reset has set it to such that if the phone gets barely moved, the AOD comes up, but tapping or picking it up quickly will almost always go to the lock screen (but then sometimes it will go to the AOD too when picking it up quickly) so it's clearly bugged somehow as the behavior is inconsistent, whichever way that Google intended for it to actually be.
Going beyond that, the AOD is pretty useless anyway. Any incoming notifications light up the lock screen. Why can't they just make it like my OnePlus where the notification shows up on a black screen with a full preview when AOD is enabled? This is so much more useful, not to mention battery friendly.
I need some advice on troubleshooting this one.
Brand new P7P, turned on Tap to Wake and "Always show time and info" on the lockscreen. It only ever works after a reboot *before* I log in the first time. Once I log in,that's it,screen is black when I lock it and it won't tap to wake.
I've removed the screen protector in case it was messing with the proximity sensor. I ran the phone in safemode and both *do* work in safemode,so I suspect it's an app on startup causing this.
What I need help with is how can I whittle down the culprit without removing all the apps one by one? Is there an app that will allow me to stop apps starting up at boot time and add them one by one?
dunetails said:
I need some advice on troubleshooting this one.
Brand new P7P, turned on Tap to Wake and "Always show time and info" on the lockscreen. It only ever works after a reboot *before* I log in the first time. Once I log in,that's it,screen is black when I lock it and it won't tap to wake.
I've removed the screen protector in case it was messing with the proximity sensor. I ran the phone in safemode and both *do* work in safemode,so I suspect it's an app on startup causing this.
What I need help with is how can I whittle down the culprit without removing all the apps one by one? Is there an app that will allow me to stop apps starting up at boot time and add them one by one?
Click to expand...
Click to collapse
@zetsumeikuro wait,I don't get what's so funny?
Mine works on every part of my lock screen.
Any chance you're using lift to wake? Besides that, I have everything else on the same as you.
Edit: Just reread your post. Do you have a lot of apps? You could force stop every single one of them and test to see what happens to be sure that it's an app.
Curiousn00b said:
Mine works on every part of my lock screen.
Any chance you're using lift to wake? Besides that, I have everything else on the same as you.
Edit: Just reread your post. Do you have a lot of apps? You could force stop every single one of them and test to see what happens to be sure that it's an app.
Click to expand...
Click to collapse
Yeah I have quite a few,but I think I'd rather try this first than start uninstalling and reinstalling the lot.
Not fixed,but getting somewhere. This is related to Bluetooth in some way.
If I turn off Bluetooth and reboot the phone,AOD works. I unlock the phone,it still works.
If I turn on Bluetooth AOD immediately breaks again until I turn off Bluetooth AND reboot.
I thought it might be my fitness band so disconnected and uninstalled the app, but the problem persisted. I have no other devices permanently using Bluetooth, so I'm starting to think this is a Bluetooth bug rather than a specific app now
dunetails said:
Not fixed,but getting somewhere. This is related to Bluetooth in some way.
If I turn off Bluetooth and reboot the phone,AOD works. I unlock the phone,it still works.
If I turn on Bluetooth AOD immediately breaks again until I turn off Bluetooth AND reboot.
I thought it might be my fitness band so disconnected and uninstalled the app, but the problem persisted. I have no other devices permanently using Bluetooth, so I'm starting to think this is a Bluetooth bug rather than a specific app now
Click to expand...
Click to collapse
If the fitness band allows you to take pictures remotely, it is possible that it recognizes it as a keyboard and that this interferes due to some bugs
PaulBW said:
If the fitness band allows you to take pictures remotely, it is possible that it recognizes it as a keyboard and that this interferes due to some bugs
Click to expand...
Click to collapse
Good point. This is why I tried to uninstall the app and disconnect the fitness band entirely,just to rule it out. Unfortunately,even once uninstalled,after a reboot with BT off AOD worked,but the moment I turned BT on AOD broke.
I can't think of any other apps using the BT at the moment but having a think. Will post more info if/when I get it.
Finally figured it out thanks to the hint by LaNy_6. This *is* down to Android Auto, but it’s not immediately obvious how or why.
To fix I went to Settings > Apps
Select See All Apps
From the top right overflow menu select Show System
Scroll Down to Android System
Select Notifications
Ensure Car Mode is selected
When I did this, I saw LaNy_6’s screenshot for the Android System notification that says “Driving App is running – tap to exit driving app” in my notification shade.
After doing this, AOD/tap to wake/lift to wake all suddenly work as expected.
Please note that upon rebooting the Driving App notification shows again and you have to tap it to go away. Again,no idea why.
I have no idea why, but I’m guessing every reboot the phone was put in to driving mode. I have never connected it to a car, there’s no reason for this to happen, but because I didn’t see the notification it never got exited from it seems. There’s no other indicators that it’s in driving mode, the phone works as normal other than the AOD problem.