Is anyone else using 10.1.3 RC2 or the stable version?
If i switch my sleep settings to anything above 15seconds, the screen will not sleep but it will dim. Sometimes i found my phone hot for no reason when it is not being used, and i think that is due to my screen constantly being on. I do not recall this issue in 10.1.3 -RC1. I don't mind using 15 seconds right now but the timer is not exactly at 15 seconds, it hard to read something on my phone when i have it set to 15 seconds because the screen keeps going into dim mode and sleep after 5-7 seconds.
Screen off animation and day dreaming settings are set to off at this point.
Android 4.2.2
Kernel 3.4.53
10.1.3 -dt2mo
Please feel free to recommend any other rom that is better than CyanogenMod.
peacesam said:
Is anyone else using 10.1.3 RC2 or the stable version?
If i switch my sleep settings to anything above 15seconds, the screen will not sleep but it will dim. Sometimes i found my phone hot for no reason when it is not being used, and i think that is due to my screen constantly being on. I do not recall this issue in 10.1.3 -RC1. I don't mind using 15 seconds right now but the timer is not exactly at 15 seconds, it hard to read something on my phone when i have it set to 15 seconds because the screen keeps going into dim mode and sleep after 5-7 seconds.
Screen off animation and day dreaming settings are set to off at this point.
Android 4.2.2
Kernel 3.4.53
10.1.3 -dt2mo
Please feel free to recommend any other rom that is better than CyanogenMod.
Click to expand...
Click to collapse
I had this issue once, I ran a Fix Perms and then rebooted, no problems since.
DJ_SpaRky said:
I had this issue once, I ran a Fix Perms and then rebooted, no problems since.
Click to expand...
Click to collapse
I just ran the permission fix and tested out on sleep after 30 seconds but no dice. I will play around with it...thanks!
peacesam said:
I just ran the permission fix and tested out on sleep after 30 seconds but no dice. I will play around with it...thanks!
Click to expand...
Click to collapse
OK, have you checked for Wakelocks? Such as G+ Location Reporting.
DJ_SpaRky said:
OK, have you checked for Wakelocks? Such as G+ Location Reporting.
Click to expand...
Click to collapse
I will give it a shot, right now it needs to collect more battery data first. I tried one minute as well, the screen becomes dimmed instead of sleep. I don't know what was difference really..i updated from rc1 and ever since then, rc2 and stable 10.1.3 hasn't been good.
peacesam said:
I will give it a shot, right now it needs to collect more battery data first. I tried one minute as well, the screen becomes dimmed instead of sleep. I don't know what was difference really..i updated from rc1 and ever since then, rc2 and stable 10.1.3 hasn't been good.
Click to expand...
Click to collapse
Weird, I only had the problem right after flashing, once all of my apps loaded and I ran Fix Perms then rebooted, no issues since.
Do you have a 3rd party lockscreen or widget on the CM lockscreen? I turn the lockscreen off (set screen security to none)
DJ_SpaRky said:
Weird, I only had the problem right after flashing, once all of my apps loaded and I ran Fix Perms then rebooted, no issues since.
Do you have a 3rd party lockscreen or widget on the CM lockscreen? I turn the lockscreen off (set screen security to none)
Click to expand...
Click to collapse
I do have a widget and it's called HD widget. I have been using that for my home screen clock and date. I would like to have lockscreen on as a security purpose tho.
peacesam said:
I do have a widget and it's called HD widget. I have been using that for my home screen clock and date. I would like to have lockscreen on as a security purpose tho.
Click to expand...
Click to collapse
For testing purposes, disable it then reboot and see if that fixes it.
DJ_SpaRky said:
For testing purposes, disable it then reboot and see if that fixes it.
Click to expand...
Click to collapse
That didn't work .
peacesam said:
That didn't work .
Click to expand...
Click to collapse
Yikes. Not sure where to go from here. I would backup your data,then wipe everything then redownload the ROM & GApps, then reflash, and then see if it happens before you load your data/apps back.
DJ_SpaRky said:
Yikes. Not sure where to go from here. I would backup your data,then wipe everything then redownload the ROM & GApps, then reflash, and then see if it happens before you load your data/apps back.
Click to expand...
Click to collapse
I think i will try that again. I did a full wiped, and i think since the issue was there after a fresh start so i restored everything back to normal.
Thanks for the help , i will post an update if i figured out the problem.
I switched to CyanFox! So far so good..i don't have any issue i got from 10.1.3 and 10.2.
Related
I'm new to rooting, installed MIUI and loving it so far. My hw is 003. Everything is working so far but i have a few questions -
1. Do you use the default kernel or replaced it? I've seen screen tearing a few times and battery life could be better so I'm thinking of trying a different one. Read a number of threads in the root section.
2. Did you replace the lockscreen? I'm asking because I love its look, but if you enable security there's no slide to unlock and its not so useful.
3. How often do you update the MIUI build - I read it comes out every Fri, do they have major changes?
#3, the official build is done on friday, porting to individual phones is on/around sunday
1. I'm on the 1.1.28 build and using the kernel that came with it. Savage 1.6. It is by far the best kernel I have ever had the pleasure of flashing and I have no reason to use anything else. When I update to a newer build, I will most likely flash this kernel over it.
2. Still using stock lockscreen. I agree that the pattern lock could have been implemented better.
3. What elegantai said.
2 more issues I noticed -
1. Back button is now killing apps. The only way to fix it is turn off 'long press kills app', reboot, and turn it back on.
2. When in a call the notification bar cannot be dragged down.
Both are minor issues, just wondering if they are common.
1. That's not an issue at all, it's supposed to do that, and I think that's an awesome feature. If you just tap back it won't kill the app, and you can set how long the long press needs to be.
2. Never really noticed that before. Can you pull it down with a Sense ROM? It's been so long I can't remember. You can always hit the home key while in a call and pull the bar down from there.
ECrispy said:
2 more issues I noticed -
1. Back button is now killing apps. The only way to fix it is turn off 'long press kills app', reboot, and turn it back on.
2. When in a call the notification bar cannot be dragged down.
Both are minor issues, just wondering if they are common.
Click to expand...
Click to collapse
I actually have the same problem with the app killing. Great feature yes but it always kills the app regardless of how long or short I press it lol. Changing the duration didnt seem to help.
Sent from my PC36100 using XDA App
_MetalHead_ said:
1. That's not an issue at all, it's supposed to do that, and I think that's an awesome feature. If you just tap back it won't kill the app, and you can set how long the long press needs to be.
.
Click to expand...
Click to collapse
It kills the app even when I just tap back, that's the bug. When its working yes, it only kills after a 2s tap.
ECrispy said:
It kills the app even when I just tap back, that's the bug. When its working yes, it only kills after a 2s tap.
Click to expand...
Click to collapse
That's odd, it works perfectly for me. What MIUI build are you on?
_MetalHead_ said:
That's odd, it works perfectly for me. What MIUI build are you on?
Click to expand...
Click to collapse
Latest - 1.2.11
I dunno, maybe it's a bug with that build.
from my observations the back tap close program happens only when a program is lagging. if you dont have too many things going on at once it shouldnt be a problem
yeahh it is a problem occasionally for me. I normally skip and flash every other week. This week im gonna flash again though, because it seems slow.
Hi everyone,
I've looked for a solution all over the net, but seems like no one had this problem before (guess i'm a special girl...):
The vibrate feedback when touching the screen just stopped working, in spite of the settings under "settings -> sounds -> vibrate on touch".
It started after an update to AOKP rom - milestone 5 (based on ICS 4.0.4) + Franco kernel nightly r151, but effects all the other roms. Maybe one untouched system file damaged.
I've tried everything: restore from previous nandroid backup, another rom (CM9), another kernel, another launcher, I even wiped everything and flashed new and clean rom-stock from google developers' page. And yet - no vibrate feedback.
The wired thing is that the haptic feedback is working in few specific applications, like the build-in ICS keyboard and the dialer Dialer-One, so it probably not some hardware failure.
All this time there are five softkeys that still have haptic feedback: the buttons of the nav-bar, the button that opens the applications drawer and the google-search widget.
I've tried using "KickBack" instead, but it's too aggressive and very uncomfortable.
PLEASE, PLEASE - Help me!
Same thing happened to me. I had the exact same setup and the haptic feedback went away after I flashed the kernel. Since I've had lots of issues when trying custom kernels, I just restored a nandroid and went back to the kernel included with aokp.
Sent from my Galaxy Nexus using XDA
Restore fixed my issue, so I'm not sure exactly what to tell you.
Sent from my Galaxy Nexus using XDA
taappel said:
Restore fixed my issue, so I'm not sure exactly what to tell you.
Click to expand...
Click to collapse
I've seen some ppl's msgs that even simple reboot fixed their vibrate problem.
Didn't work for me, unfortunately
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I'm also using Franco kernel, but I don't think this is the problem because i've tried some other kernels and none of them fixed my haptic.
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
nich0145 said:
Hi TaliKa
I've just had this problem myself but it happens long after I flashed aokp m5 + franco r152 (too) so I'm not exactly sure what caused it. However after I went to clear my cache and dalvik cache, everything seems fine again.
Click to expand...
Click to collapse
Thanks guys, but as I wrote in the first msg, those actions didn't help.
Is there any pro here who can offer a profound solution that I didn't tried before?
Which system file responsible for the haptic feedback?
Guess I'll have to stuck without haptic feedback...
Sveke said:
Some kernels have haptic adjustment, see pic for kernel does.
I'm running Franco 152 and mines fine.
I know trinity kernels lower it
Click to expand...
Click to collapse
How can I adjust the haptic feedback feature in Trinity kernel?
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
takomar said:
+1
just wanted to say...exactly the same thing happened to me (started with aokp milestone 5 and vibration gone afterwards...)
im trying several things to get it back...i use it alot (at work and most of the time..its on vibrate)
hopefully we'll find a solution
Click to expand...
Click to collapse
Dacian said:
Yeah this just happened to me too. It was working fine for awhile on AOKP and then all of a sudden it stopped. No idea what happened exactly. I tried whiping everything and restoring CM9 but that didn't work either. I thought maybe hardware but the phone vibrated on boot so it isn't that. Hopefully we find a fix...
Click to expand...
Click to collapse
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
im starting to believe its a hardware issue (well at least for me) i mean i dont even get a vibration upon booting or turning off the phone...and i even went back to full stock...same thing
maybe it might have been some software issue that led to the overburning of the motor(doubt that though)
what is weird though is that the same scenario happened to us so im lost...
maybe i should start talking to samsung for my replacement
meanwhile...im very open to suggestions that might help my case
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
takomar said:
hope we find something soon...u guys, does it vibrate at all?when u turn on ur phone?turn off? unlock ?
Click to expand...
Click to collapse
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
TaliKa said:
Yes, it vibrates at boot and also when using application with it's own vibrate settings, like "dialer one" for example.
Did you try using KickBack just to check the hardware?
if it's some hardware issue, maybe you can apply to your warranty supplier about that, just flash stock rom and relock your device before.
Click to expand...
Click to collapse
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
takomar said:
thats what im gonna do i guess...such a sad day...
i couldnt find KickBack, its not available in my accessibility menu nor in my market (i live in France)
i tried googling an apk but nothing for android 4.0
do you have a link for it?
Click to expand...
Click to collapse
I couldn't find it in play store either, but i download it from here:
http://code.google.com/p/eyes-free/downloads/detail?name=kickback-v1.1.1.apk
works fine for me.
TaliKa said:
unfortunately I didn't get any solution yet. Realy depressing.
I promise to update about any progress, and hope you'll both do the same...
Just don't give up! it isn't hardware thing, so there must be solution somewhere.
Click to expand...
Click to collapse
Good to know. I went ahead and flashed the base image and it restored vibration, then I rooted and flashed AOKP again. It worked for about that day and then this morning when I woke up the vibration is gone again. I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Dacian said:
I'm almost positive it's AOKP's software. I'll test another ROM (Android Revolution) for a day and see if it happens again.
Click to expand...
Click to collapse
Which kernel do you use? and did you set the quite hours on?
If you succeed to restore the vibrate, i'd like to hear exact instructions how to do that, including links to download the boot image, if you plesae...
I have stock (rooted then unrooted) JC with APEX launcher. It sounds crazy but my phone screen doesn't turn off by itself.
There are several times I woke up in the morning to find out my phone screen was on overnight (screen must have turned on when I plugged in the charger). Right now, I turned on my phone just to see if the screen would turn off at 1) lock screen 2) apex home screen. neither works.
I tried all these with different timeout settings (15 sec, 30 sec, 1min, etc.).
Anyone having the same problem? Anyone with solution?
kg1128 said:
I have stock (rooted then unrooted) JC with APEX launcher. It sounds crazy but my phone screen doesn't turn off by itself.
There are several times I woke up in the morning to find out my phone screen was on overnight (screen must have turned on when I plugged in the charger). Right now, I turned on my phone just to see if the screen would turn off at 1) lock screen 2) apex home screen. neither works.
I tried all these with different timeout settings (15 sec, 30 sec, 1min, etc.).
Anyone having the same problem? Anyone with solution?
Click to expand...
Click to collapse
Had that issue with siii, reboot fixed it, have you tried reboot?
mattsm said:
Had that issue with siii, reboot fixed it, have you tried reboot?
Click to expand...
Click to collapse
Yes rebooting always solves the issue but can i get a permanent fix? It's kinda annoying. I'm on GT-N7100 JB4.1.2 and i've never rooted.
Kinda glad i wasnt the only one having this issue. Happened to me yesterday. Kinda freaked me out as i dont want anything wrong with this phone.. reboot worked for me yesterday.
On a side note.. every once in awhile my youtube app goes to **** and it refuses to play videos.. it says network error yet i can do everything else... reboot fixes that too.
Sent from my big big BIG iphone killer.
morbiddevil82 said:
Kinda glad i wasnt the only one having this issue. Happened to me yesterday. Kinda freaked me out as i dont want anything wrong with this phone.. reboot worked for me yesterday.
On a side note.. every once in awhile my youtube app goes to **** and it refuses to play videos.. it says network error yet i can do everything else... reboot fixes that too.
Sent from my big big BIG iphone killer.
Click to expand...
Click to collapse
Yeah no kidding. I really don't want anything to go wrong with my phone. But unfortunately it has been kinda buggy from day one. A minor issue with the stock keyboard was solved after the 4.1.2 update. But the weird error with the Quick Commands thingy ain't getting sorted out, even after the update. Of course, reboots also never help.
Oh someone please tell me what's wrong with my phone The screen timeout thingy ain't working An unattended message or missed call means my display stays on till I turn it off manually A reboot would solve the issue but then it would come back again. Any permanent fix? Please help I've never rooted my phone.
Sent from my GT-N7100 using xda app-developers app
Uninstall any apps that keep your screen on or go through the apps list and kill everything individually. imediashare keeps my screen on after I'm done using it cause it still wants to stay running.
w7excursion said:
Uninstall any apps that keep your screen on or go through the apps list and kill everything individually. imediashare keeps my screen on after I'm done using it cause it still wants to stay running.
Click to expand...
Click to collapse
Lemme try doing that
Sent from my GT-N7100 using xda app-developers app
---------- Post added at 09:48 PM ---------- Previous post was at 09:06 PM ----------
w7excursion said:
Uninstall any apps that keep your screen on or go through the apps list and kill everything individually. imediashare keeps my screen on after I'm done using it cause it still wants to stay running.
Click to expand...
Click to collapse
Went through the 124 apps that had WAKE_LOCK permission. (Used Permission Explorer). If I count out the recently installed apps before which the problem had originally started, I guess there aren't any suspicious apps. Oops Aren't there any apps that forces the display to go off? ^_^
Sent from my GT-N7100 using xda app-developers app
I'm just throwing it out there by maybe go into recovery and fix permissions? Clear the cache? Factory reset if all else fails I guess.
w7excursion said:
I'm just throwing it out there by maybe go into recovery and fix permissions? Clear the cache? Factory reset if all else fails I guess.
Click to expand...
Click to collapse
I didn't want to do a factory reset Anyways, thank you Lemme see what I can do
Sent from my GT-N7100 using xda app-developers app
kg1128 said:
I have stock (rooted then unrooted) JC with APEX launcher. It sounds crazy but my phone screen doesn't turn off by itself.
There are several times I woke up in the morning to find out my phone screen was on overnight (screen must have turned on when I plugged in the charger). Right now, I turned on my phone just to see if the screen would turn off at 1) lock screen 2) apex home screen. neither works.
I tried all these with different timeout settings (15 sec, 30 sec, 1min, etc.).
Anyone having the same problem? Anyone with solution?
Click to expand...
Click to collapse
Hi. Having the same problem... However, i believe it has to do with the feature that prevents screen from turning off if you are looking at it. Try to turn it off and on. Perhaps it will help.
If you continue to have problems, just disable that feature... it is a good adon, but having the screen turn off tose battery is more important.
Hope it helps.
Let us know if it worked out
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
joooe said:
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
Click to expand...
Click to collapse
It is a common issue with custom kernels right now. It is due to a bug in the source. We have to wait for Google to fix it. For the meantime use a stock kernel or anything close to stock like 007 kernel
Sent from my Galaxy Nexus using Tapatalk 2
joooe said:
I'm now on CM10.1 official, but tried stock, Cataclysm and a couple of other roms and kernel combinations.
I always end up with BSOD (black screen of death) at some point. The screen just turns off and doesn't comes on again, even if it receives a call (it does ring though).
Last BSOD was on today's CM10.1 already. I had to remove the battery.
It's not a usual thing to happen, but it ends up happening sometime.
Don't know if it's my new Mugen 2000 mAh battery, or some program I restore using TitaniumBackup. Never had a BSOD in 4.1 roms.
Click to expand...
Click to collapse
deeren said:
It is a common issue with custom kernels right now. It is due to a bug in the source. We have to wait for Google to fix it. For the meantime use a stock kernel or anything close to stock like 007 kernel
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
the same issue with stock kernels too(unrooted and rooted).
btw, its not called bsod, its called sod(sleep oif death)
It's probably not kernel related. Did you turn your animations off in developer settings? Try turning them to .5. Helped me and several others. Running mmuzzy with tiny kernel.
klobkelosh said:
It's probably not kernel related. Did you turn your animations off in developer settings? Try turning them to .5. Helped me and several others. Running mmuzzy with tiny kernel.
Click to expand...
Click to collapse
Will try that.
Thanks everyone.
I have the same BSOD/SOD issue... will try the 0.5 animation trick and report back. I would hate to go back to 4.1 roms.
I found new love for my SGN with the 4.2.1 smoothness.
Did it help?
I am experiencing SOD / BSOD on my Nexus 4 + latest CM10.1 nightly from time to time... (stock kernel).
In developer settings there are actually three settings regarding animations - are all to be set to .5?
Best regards,
ww
For me it did, yes.
No more BSOD.
I put them all to x.5
I've been diagnosing this for some time and I feel fairly confident that it is only the animation duration setting that triggers the sod. I have the other two settings set to 0 and duration set to 1 and no sod. But, it will not turn off that pesky crt animation.
who in here looked at logcat/dmesg when that happens?
do you have daydream ON? do you use an adblocker?
i've had one on 4.2.1, WITH AN ADBLOCKER installed. no adblocker, no bsod. full stock (rooted, unrooted, tried them both, doesn't matter), default settings (only enabled usb debugging)
just had another SOD / BSOD: I connected the charger and realized after 15 minutes, that the clock was unchanged (still 15 Min prior) - I tried to open an app and got a timeout. After I switch the screen off and on again I just saw a black screen (a little bit lighter than actually off) - but no homescreen anymore... damned.
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