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
Related
This is a very strange problem I'm experiencing on my S3 (Verizon, 4.1.2 stock rom, rooted)
I have set up a pattern lock screen in my Security settings. When the display has been off for the 1 minute, the pattern lock screen protects the phone on the next wake. However, I also have a home screen widget (via Widgetsoid) to quickly enable/disable the Lock Screen. So for example, I turn off the lock screen when I'm driving or at home, and enable it when I'm in public. Normally this mechanism works just fine.
The problem is, when the lock screen is "Disabled", and I get a notification (such as incoming text), and I pull down my notification screen and then to click on the new notification, this immediately pops up my pattern lock screen. (even though it's supposed to be disabled).
This is not a problem specific Widgetsoid. There are other apps that also has the ability to toggle the lock screen (such as Tasker), and this behavior also happens when I use other means to temporarily disable the lock screen.
Note that this notification-triggers-lock behavior doesn't happen when the Lock Screen is enabled.
I have searched around for any thread that might show something related to this issue, but found nothing that matches the behavior I'm experiencing. Has anyone else experienced something like this, or have an idea of what might be going on here?
Wrong section. ask in the verizon of the S3
xSpeced said:
Wrong section. ask in the verizon of the S3
Click to expand...
Click to collapse
Oops sorry. Can a mod move this thread accordingly?
I have the exact same problem on my Samsung Galaxy Note 2. We can thus conclude it is not device specific.
I am running native Android, 4.1.2. I think this is an Android bug.
Same problem on Nexus 7 (Android 4.2.2).
I've also searched on several occasions but haven't yet worked out what's going on or how to work around it.
ricn said:
Same problem on Nexus 7 (Android 4.2.2).
I've also searched on several occasions but haven't yet worked out what's going on or how to work around it.
Click to expand...
Click to collapse
I can confirm I've had this same issue on both Android 4.1 (stock HTC One) and 4.2 (rooted Galaxy SII skyrocket), when used with the "No Lock" app. When locking is disabled, clicking any notification item results in the lock screen being displayed; when locking is ENabled, no issues.
I have this problem when I click a notification in the notification bar, and I know in my case its due to secure settings turning on patern lock for me.
Sent from my Unlocked Verizon Galaxy S3
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???!!!
Based on this thread:
http://forum.xda-developers.com/lg-v10/help/knock-to-wake-t3239674
So far it's only a confirmed suspicion, but it's already happened to several people including myself. Accessing the hidden menu may break the knock on feature, even without doing any modification in it.
Possible Solutions:
-Hard Reset (100% working)
-Deleting Finger Prints (I've only seen this working on 1 person in another thread)
Please report if this has happened to you and if you've done something else to solve the issue. Thanks!
I go in the hidden menu a couple times a day to change RAT selection and have only had one issue. So I wouldn't say it's a 100% the hidden menu
Sent from my LG-H901 using Tapatalk
Nope, doesn't break it. Been in the hidden menu to access Engineering Mode a bunch of times already and knock-on works fine.
Went in there to unlock the APN fields. Knock-on works fine.
Sent from my LG-H901 using XDA Free mobile app
Guys, it only breaks, as I stated in another thread, if you open the IMS Settings (which causes a crash) in the hidden settings menu. It is 100% reproducible, but *ONLY* that setting causes the issue.
toastido said:
Guys, it only breaks, as I stated in another thread, if you open the IMS Settings (which causes a crash) in the hidden settings menu. It is 100% reproducible, but *ONLY* that setting causes the issue.
Click to expand...
Click to collapse
Nope that didn't break it either
@baymon - Funny how everyone notices this until you post a PSA about it then everyone has to try to rebuke it.
If it "breaks" (turns knock on, off) you can use the anycut type app from the play store and make a shortcut to the hidden menu knock on option to toggle it back on or off if you so chose (I turned mine off so it would stop turning on in my pocket).
toastido said:
@baymon - Funny how everyone notices this until you post a PSA about it then everyone has to try to rebuke it.
Click to expand...
Click to collapse
Obviously we need more data on this issue, there could be other variables in play as well but that's why we're raising the awareness of the knock on issue.
@toastido haha it's all good.
LancerV said:
I go in the hidden menu a couple times a day to change RAT selection and have only had one issue. So I wouldn't say it's a 100% the hidden menu
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
How do you get into the hidden menu? Tried quickshortcutcreator but can't find it.
sentry07 said:
How do you get into the hidden menu? Tried quickshortcutcreator but can't find it.
Click to expand...
Click to collapse
Dial 277634#*#
I'm anxiously awaiting everyone now saying their knock on is broken ?
Didnt break mine! Thanks for the info to get into hidden menu though
nope mine still works but i do have issues with the screen in calls but thats it. but but was that way when i got it.
i think your hidden menu theory is good but my knock doesnt work but it stopped after i did a rest because the apn got messed up and it wouldnt let me add a new one. so i found this out this problem seams random as hell and if i turn knock pattern on to unlock the phone the knock works to turn the screen on but not off. i also noticed my second screen doesnt have the flash light on it when off anymore. so i will be doing a reset tomorrow unless anyone knows how to get the secound screen apps back when the screen is off. i think those apps are related to the tap on
It did break mine. Went to menu and hit apn unlock. No crash or anything. I noticed it not working immediatly. Knock code does still work.
I had the issue also, then did a reset. But I want to add to the issue that it didn't only effect knock on, but the touchscreen didn't register anything altogether when screen off. Meaning, the second screen can swipe when screen off to show the quick toggles, it did not work during that time.
joachim123 said:
I had the issue also, then did a reset. But I want to add to the issue that it didn't only effect knock on, but the touchscreen didn't register anything altogether when screen off. Meaning, the second screen can swipe when screen off to show the quick toggles, it did not work during that time.
Click to expand...
Click to collapse
mines the same no quick toggles
Mines the same no quick toggles but i found the answer with out rest on another post. i figured it out that its just something crashing the hidden menu doesnt matter what even force closing causes this problem. which is what i did seeing that the first time i used it nothing happened but the second time when the problem happened i cleared all apps and it stopped working. i'm guessing they disable it if something crashes it.
the knock on actually just gets turned off. Here's the quote for the answer make sure both knock on settings are on and it works instantly so no reboot needed.
-LBT- said:
Get yourself Quick Shortcut Maker, launch it, change the search type to 'Normal', search for 'Knock On', click on 'Settings', then on 'Try'. On the next screen, switch Knock On back and forth and see if that works.
Click to expand...
Click to collapse
clockcycle said:
If it "breaks" (turns knock on, off) you can use the anycut type app from the play store and make a shortcut to the hidden menu knock on option to toggle it back on or off if you so chose (I turned mine off so it would stop turning on in my pocket).
Click to expand...
Click to collapse
you are a genius and life saver!!! thank you.
hidden menu did break it, confirmed.
Has anyone else got this bug? After locking the phone, the screen will stay active (even though the display is off) for around a second.
I've noticed the fingerprint icon flashes once after a second at the same time.
It's quite annoying if like me, you lock it and immediately shove it into your pocket within a second, as I sometimes unlock it to find I'm in an email or an app I didn't remember being in.
jonnyguitar said:
Has anyone else got this bug? After locking the phone, the screen will stay active (even though the display is off) for around a second.
I've noticed the fingerprint icon flashes once after a second at the same time.
It's quite annoying if like me, you lock it and immediately shove it into your pocket within a second, as I sometimes unlock it to find I'm in an email or an app I didn't remember being in.
Click to expand...
Click to collapse
I have seen other people report this as well.
jonnyguitar said:
Has anyone else got this bug? After locking the phone, the screen will stay active (even though the display is off) for around a second.
I've noticed the fingerprint icon flashes once after a second at the same time.
It's quite annoying if like me, you lock it and immediately shove it into your pocket within a second, as I sometimes unlock it to find I'm in an email or an app I didn't remember being in.
Click to expand...
Click to collapse
Yeah, but you need to be quite quick to trigger something on the screen. I tried to do it on purpose and I can replicate the issue 9 out of 10 times )).
Hoping for a fix in the next update.
This is getting worse. Screen stays active around 3 seconds after locking it. I can see there is a quick refresh of the lock screen when it's really locked. It's really annoying now as I feel like I need to wait for this until I can safely put it in my pocket.
this doesn't happen when using nova launcher's gestures (double tap => lock screen). maybe works with an 3rd party app from playstore too, or custom kernel with double tap to sleep or some magisk mod?
seadersn said:
this doesn't happen when using nova launcher's gestures (double tap => lock screen). maybe works with an 3rd party app from playstore too, or custom kernel with double tap to sleep or some magisk mod?
Click to expand...
Click to collapse
What lock method do you use in Nova? Accessibility, Device Admin, or root?
ouch, now you got me... I think it was accessibility. I took the one which enabled fingerprint usage after locking via nova gesture. I think it was accessibility, jep
edit: had time to look at phone now, it's accessibility
seadersn said:
ouch, now you got me... I think it was accessibility. I took the one which enabled fingerprint usage after locking via nova gesture. I think it was accessibility, jep
edit: had time to look at phone now, it's accessibility
Click to expand...
Click to collapse
Okay. accessibility or root. I still get that delay after locking, even with Nova double tap. It's just one blink a couple seconds after locking. I notice the clock blink once. Honestly, I wouldn't have even noticed it had it not been posted here..
seadersn said:
this doesn't happen when using nova launcher's gestures (double tap => lock screen). maybe works with an 3rd party app from playstore too, or custom kernel with double tap to sleep or some magisk mod?
Click to expand...
Click to collapse
Yep, I uses Nova double tap to sleep/Accessibility and do not have this issue
+1 on using Nova Launcher. I cannot produce this problem if i tried.
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.