Has anyone else been experiencing issues where the P6P's screen is slow to wake?
I think it has something to do with deep sleep, and occurs whether tapping on the screen, or lifting to wake the device, it just seems to be stuck for a few seconds and then the screen comes on. I've been trying to isolate if an app or setting etc is causing it, but I haven't found the root cause yet.
I've only noticed it after updating to January.
Any thoughts? Suggestions?
P6P, Rooted, Kirisakura kernel
Thanks!
Noticed this as well, only rooted ATM
Ask to your kernel dev maybe
I'm on Px 6P rooted device stock kernel without problem
Good call, this might be related to the kernel as I'm now testing without altering any kernel settings via EXKM and the issue hasn't occurred for a few hours.
pcriz said:
Noticed this as well, only rooted ATM
Click to expand...
Click to collapse
Are you also using the Kirisakura kernel?
Rodimus8402 said:
Are you also using the Kirisakura kernel?
Click to expand...
Click to collapse
So I noticed it before I loaded the kernel but I am currently on the kernel again. It's only been an hour since I flashed so I don't have anything useful to report since flashing it. I'll let it go for a day but I wanna say I even had this issue on Proton
pcriz said:
So I noticed it before I loaded the kernel but I am currently on the kernel again. It's only been an hour since I flashed so I don't have anything useful to report since flashing it. I'll let it go for a day but I wanna say I even had this issue on Proton
Click to expand...
Click to collapse
I think I found what's causing it, seems to be using Zygisk in the latest version of Magisk.
If I have that disabled, I'm able to use EXKM to change any and all kernel options.
Rodimus8402 said:
I think I found what's causing it, seems to be using Zygisk in the latest version of Magisk.
If I have that disabled, I'm able to use EXKM to change any and all kernel options.
Click to expand...
Click to collapse
So it was preventing you from changing kernel options and causing the slow wake?
The denylist won't work without it though right? I felt like I read somewhere in the forum that you could configure the list then turn off zygisk
pcriz said:
So it was preventing you from changing kernel options and causing the slow wake?
The denylist won't work without it though right? I felt like I read somewhere in the forum that you could configure the list then turn off zygisk
Click to expand...
Click to collapse
I believe it's just causing slow wake, as I was able to test and changing kernel options no longer seems to be affected.
It's a strange issue for sure that's only popped up after upgrading to January.
I tried but you can't disable Zygisk and keep enforcing on
I've had the same slow wake issue on stock January update randomly...not all the time
redskykiter said:
I've had the same slow wake issue on stock January update randomly...not all the time
Click to expand...
Click to collapse
Are you rooted?
Rodimus8402 said:
Are you rooted?
Click to expand...
Click to collapse
No
redskykiter said:
No
Click to expand...
Click to collapse
Weird, seems to be affecting rooted, non-rooted, stock and not.
The one constant seems to be the January security release
I reset adaptive brightness last night. It seems to have fixed it for me on stock. Working good all day
redskykiter said:
I reset adaptive brightness last night. It seems to have fixed it for me on stock. Working good all day
Click to expand...
Click to collapse
Nice, what do you mean by resetting adaptive brightness?
Today I upgraded to Magisk 24101, and it hasn't happened for hours now
Having issues with Google Pixel's adaptive brightness? Here's how to fix it
Is the screen brightness on your Pixel not working properly? Here's an easy way to fix adaptive brightness on the Google Pixel on Android.
9to5google.com
Related
I've only noticed this since running the August security updated and its happened across three ROMs so far (Screwed, Pure Nexus, LOS (No gapps)). Sometimes the screen takes for ever to power up. Once it is up the lock screens responsiveness varies greatly. Not always in the same instance as the screen issue but when unlocking the device it will momentarily freeze. Sometimes locking itself again..
Curious if anyone has seen anything similar.
How are you restoring your apps when you flash a ROM? If you restore them from a Google cloud backup you could be restoring corrupted data that is causing the problem. I had that happen when a utility app completely screwed up the scrolling on my phone. I did a factory reset but restored my phone from a cloud backup and the problem came back exactly the same. The next day I did another factory reset but set up the phone as new and manually downloaded my apps from the Play Store. This time the problem was gone.
jhs39 said:
How are you restoring your apps when you flash a ROM? If you restore them from a Google cloud backup you could be restoring corrupted data that is causing the problem. I had that happen when a utility app completely screwed up the scrolling on my phone. I did a factory reset but restored my phone from a cloud backup and the problem came back exactly the same. The next day I did another factory reset but set up the phone as new and manually downloaded my apps from the Play Store. This time the problem was gone.
Click to expand...
Click to collapse
I'm restoring from tibu.
pcriz said:
I'm restoring from tibu.
Click to expand...
Click to collapse
I'm not sure if that could cause the same problem but presumably you are restoring app data along with the apps so it might be possible. Have you tried using the phone in safe mode to see if the problem still persists? It seems unlikely that what you are experiencing is a known issue with the August security update since we are more than halfway through the month without anyone else reporting a similar issue.
jhs39 said:
I'm not sure if that could cause the same problem but presumably you are restoring app data along with the apps so it might be possible. Have you tried using the phone in safe mode to see if the problem still persists? It seems unlikely that what you are experiencing is a known issue with the August security update since we are more than halfway through the month without anyone else reporting a similar issue.
Click to expand...
Click to collapse
It's happened without any apps installed as well. I haven't tried safe mode yet no
are you using immersive mode?
diabl0w said:
are you using immersive mode?
Click to expand...
Click to collapse
On screwed rom I was but I am getting it on PN and I don't run that rom in immersive mode.
pcriz said:
On screwed rom I was but I am getting it on PN and I don't run that rom in immersive mode.
Click to expand...
Click to collapse
I run the O preview and immersive mode causes that for me... I'm sure the custom roms are pulling commits that include this bug
diabl0w said:
I run the O preview and immersive mode causes that for me... I'm sure the custom roms are pulling commits that include this bug
Click to expand...
Click to collapse
Yeah that would make sense if you are seeing the same thing. I may jump back to a known good build and see what happens
I had a very similar issue with tremendous lag in screen on and unlocking.
It turned out to be Kernel related, I was using Kirisakura Harmony Kernel, while it was happening to me, I flashed Franco R8 kernel and all is well.
pTeronaut said:
I had a very similar issue with tremendous lag in screen on and unlocking.
It turned out to be Kernel related, I was using Kirisakura Harmony Kernel, while it was happening to me, I flashed Franco R8 kernel and all is well.
Click to expand...
Click to collapse
Thank you, I'll try that!
diabl0w said:
are you using immersive mode?
Click to expand...
Click to collapse
So I was experiencing REALLLY SLOW screen turn ons. Like it could take 30+ seconds. But the phone was awake as my LED was on, and fingerprint haptic feedback.
When looking for solutions, I found this post. I use Auto Hide Soft Keys, to hide my status bar and nav bar when I dont need them. When disabling (and even after re-enabling), the problem was fixed (for now anyways)
Can you elaborate on this post? Do you have some experience with nav bar hiding causing slow screen turn ons?
p1r473 said:
So I was experiencing REALLLY SLOW screen turn ons. Like it could take 30+ seconds. But the phone was awake as my LED was on, and fingerprint haptic feedback.
When looking for solutions, I found this post. I use Auto Hide Soft Keys, to hide my status bar and nav bar when I dont need them. When disabling (and even after re-enabling), the problem was fixed (for now anyways)
Can you elaborate on this post? Do you have some experience with nav bar hiding causing slow screen turn ons?
Click to expand...
Click to collapse
Check this thread. ?
https://forum.xda-developers.com/pi...e-problems-t3666479/post73629247#post73629247
I'm not sure what changed, but active display with start off on, then disappear. A reboot didn't help
Edit: double tap to wake also stopped working
Sent from my Pixel 2 XL using Tapatalk
Sounds like it could be a proximity sensor issue. Maybe it's somehow covered by your case or screen protector so the phone thinks it's in your pocket all the time? Just a thought.
murso74 said:
I'm not sure what changed, but active display with start off on, then disappear. A reboot didn't help
Edit: double tap to wake also stopped working
Click to expand...
Click to collapse
Sounds like a software glitch. Bout all I can suggest is a factory reset, or flash the factory image. Was this a result of an ota or did you update it?
same happens to mine. It happens when the battery is low, but at "random" times too. It's like the AOD app in dozing.
Badger50 said:
Sounds like a software glitch. Bout all I can suggest is a factory reset, or flash the factory image. Was this a result of an ota or did you update it?
Click to expand...
Click to collapse
Nope, no new programs, no updates. Seems to be back to normal now.
Sent from my Pixel 2 XL using Tapatalk
Does anyone with this issue use battery saver? I noticed when battery saver is on it doesn't work.
Fe Mike said:
Does anyone with this issue use battery saver? I noticed when battery saver is on it doesn't work.
Click to expand...
Click to collapse
Hence, battery saver must be working ?
Badger50 said:
Hence, battery saver must be working
Click to expand...
Click to collapse
I was not posting that I have an issue with aod, but rather help those with it to trouble shoot and resolve their issue.
Nope I don't use battery saver. Another issue I noticed that started with 8.1 is that my AOD will rotate to landscape sometimes. I've been having other issues recently too, may try for an RMA soon. My sketchy GPS is getting on my nerves
Sent from my Pixel 2 XL using Tapatalk
SOLVED. See my last post.
No notification or anything. It turned on with Benzo rom and now I am on fresh stock with a custom kernel and it still turns on. How do I monitor the device to determine what might be causing it to turn on? It started with March update. I didn't have this issue on the January update.
Is there an app I can install to see what turns the display on or is this something I must do on a pc?
b4u2 said:
No notification or anything. It turned on with Benzo rom and now I am on fresh stock with a custom kernel and it still turns on. How do I monitor the device to determine what might be causing it to turn on? It started with March update. I didn't have this issue on the January update.
Is there an app I can install to see what turns the display on or is this something I must do on a pc?
Click to expand...
Click to collapse
Which custom kernel? And try safemode to see if problem still persists. If safemode fixes it it is an app
shagbag913 said:
Which custom kernel? And try safemode to see if problem still persists. If safemode fixes it it is an app
Click to expand...
Click to collapse
I'm using Holy dragon Kernel.
I put the device in Safe Mode for most of the day and never saw the display turn on like before. So it must be an app. How would I go about narrowing down which app is causing the problem?
b4u2 said:
I'm using Holy dragon Kernel.
I put the device in Safe Mode for most of the day and never saw the display turn on like before. So it must be an app. How would I go about narrowing down which app is causing the problem?
Click to expand...
Click to collapse
If you could get a logcat I might be able to go through it for you.
shagbag913 said:
If you could get a logcat I might be able to go through it for you.
Click to expand...
Click to collapse
Would that be an app or by using ADB?
b4u2 said:
Would that be an app or by using ADB?
Click to expand...
Click to collapse
To grab logs you can use either just make sure if you use an app you grant it root permissions
Here are two screenshots I took after the screen turned on with no notifications present. I have no clue what to look for. Hopefully this helps. Is the whole log needed? I turn Matlog on and then turn the screen off until the "error" happens. Then I turn screen on and do the screenshot.
b4u2 said:
Here are two screenshots I took after the screen turned on with no notifications present. I have no clue what to look for. Hopefully this helps. Is the whole log needed? I turn Matlog on and then turn the screen off until the "error" happens. Then I turn screen on and do the screenshot.
Click to expand...
Click to collapse
That is exactly what you should've done. I will have a look and maybe we can find the problem. A list of your apps would make it quite a bit easier too
Here are some more that hopefully caught whatever is happening.
b4u2 said:
Here are some more that hopefully caught whatever is happening.
Click to expand...
Click to collapse
Do you have an app like an image downloader? Also does campmobile sound familiar?
shagbag913 said:
Do you have an app like an image downloader? Also does campmobile sound familiar?
Click to expand...
Click to collapse
I have Avairy, Collage maker, Image editor, Layout, Snapseed? No clue what campmobile is.
I uninstalled a bunch of apps that I don't use on a daily basis. I removed all of the above plus Verizon message, Allo, Duo, Tapatalk, Forest river forums, NFL mobile, NFL network, ESPN, and maybe a few others Display still randomly turns on.
This is so annoying that I can't figure out what keeps turning the display on.
Are you using any custom kernel settings that don't get set in safemode? Set on boot etc..
DR3W5K1 said:
Are you using any custom kernel settings that don't get set in safemode? Set on boot etc..
Click to expand...
Click to collapse
Honestly not sure. I just use the settings that come with the kernel.
We'll that could potentially be the problem. Try it with the stock kernel for testing?
DR3W5K1 said:
We'll that could potentially be the problem. Try it with the stock kernel for testing?
Click to expand...
Click to collapse
So just flash the stock zip on slot B?
b4u2 said:
So just flash the stock zip on slot B?
Click to expand...
Click to collapse
The best way to try it without losing anything imo.
Just "fastboot flash-all.bat" after you open the .bat and editing out the "-w".
DR3W5K1 said:
The best way to try it without losing anything imo.
Just "fastboot flash-all.bat" after you open the .bat and editing out the "-w".
Click to expand...
Click to collapse
I just did that and will now wait to see what happens.
Update: Display still turns on what's my next step?
Well that sums it up only a factory reset to try now.
If it still persist then your phone is fubar.
DR3W5K1 said:
Well that sums it up only a factory reset to try now.
If it still persist then your phone is fubar.
Click to expand...
Click to collapse
I did a full wipe last night. So far so good but it's early yet.
Four hours and still no sign of display randomly turning on. I installed magisk and my custom kernel. So far I only turned on/logged into apps I needed right now.
My cheek/ear selects things on touch screen while taking calls. Proximity sensor problem?
This is a new issue today stock with magisk 19 beta
Notcho/custom nav and adaway installed was not a problem with all apps and root just started happening any one know why and is there a fix?
I have had a similar problem recently, was using elemental kernel.
Only thing that fixed it was to flash Kirisakura-Kernel.
I've had the same issue for months and been on Kirisakura for months as well. Double Tap to Wake is off, too. Pretty sure it's not this kernel or Magisk.
weird
newkydawg said:
I've had the same issue for months and been on Kirisakura for months as well. Double Tap to Wake is off, too. Pretty sure it's not this kernel or Magisk.
Click to expand...
Click to collapse
yes i switched and its fine now
kentek said:
yes i switched and its fine now
Click to expand...
Click to collapse
Switched what? I still have the problem...
No I spoke to soon I still have the issue I have tried everything turned off always on display disabled double tap to wake and in the kernel still don't know what to do with it
Sent from my Pixel 3 XL using Tapatalk
I've used the AOD since April without any issues, but after updating to 12.5.6 the time randomly stops and the display stops repositioning the clock. The time never seems to be more than an hour off even overnight.
I'm using the stock global ROM and it's not rooted. I can't find any new or related settings and tried switching from Balanced to Performance battery mode, but it still happens. Anyone know what's causing the problem?
festor said:
I've used the AOD since April without any issues, but after updating to 12.5.6 the time randomly stops and the display stops repositioning the clock. The time never seems to be more than an hour off even overnight.
I'm using the stock global ROM and it's not rooted. I can't find any new or related settings and tried switching from Balanced to Performance battery mode, but it still happens. Anyone know what's causing the problem?
Click to expand...
Click to collapse
Hello
I have the same problem with the update from 12.5.3 to 12.5.6 on my Poco F3, i have already report this issue in this forum, but until now, no solution! I made the update with 466MB by OTA, after that I made a hard reset and instal the all ROM 12.5.6, but the problem continues. I don't have any other problem but this is anoiing.
Agreed, I use AOD for notifications and I also don't want burn in. I already loose some app functionality to unavoidable aggressive battery management even when "No restrictions" is set so I hope that's not also to blame here.
The AOD app version is 2.9.752-07052042 and has no battery management options just like other system apps. I hope there is an app fix and we don't have to wait for a MIUI update.
festor said:
I've used the AOD since April without any issues, but after updating to 12.5.6 the time randomly stops and the display stops repositioning the clock. The time never seems to be more than an hour off even overnight.
I'm using the stock global ROM and it's not rooted. I can't find any new or related settings and tried switching from Balanced to Performance battery mode, but it still happens. Anyone know what's causing the problem?
Click to expand...
Click to collapse
Same issue I'm facing with MIUI 12.5.6 update. New updates always take time to get stable.
zcaldeira said:
Hello
I have the same problem with the update from 12.5.3 to 12.5.6 on my Poco F3, i have already report this issue in this forum, but until now, no solution! I made the update with 466MB by OTA, after that I made a hard reset and instal the all ROM 12.5.6, but the problem continues. I don't have any other problem but this is anoiing.
Click to expand...
Click to collapse
Problem solved with the update for 12.5.7
zcaldeira said:
Problem solved with the update for 12.5.7
Click to expand...
Click to collapse
Can confirm, no issues since the update a few days ago