Has anyone else noticed that with any of the ASOP or CM builds from time to time the screen will not turn on but the buttons light up? I have had this happen about 3 - 4 times a day no matter what build I am using that is based off of ASOP. The only way out is to hard power off and restart.
Yup. People call it SOD (sleep of death).
It's usually a kernel issue. I found that bumping up the low clock speed voltages helps a LOT. Just one notch in Trickster. The Temasek kernel (I'm using exp6) seems to help as well.
Related
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
macfan74318 said:
Hey there every one. When I am unlocking my phone I notice that it will flash the lock screen and then disappear and then immediately re appear. When you try to lock the phone sometimes it wont lock and the buttons will stay lit and will display the lock screen but the display wont sleep unless it times out.
This happens on all ROM's that I flash except CyanogenMod
I used both of the over clock methods but the results are the same.
Please Advise
macfan74318
Click to expand...
Click to collapse
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
sino8r said:
Yeah, it sucks. Theres no real way around this but disabling the lock screen helps it from happening less frequently. But then you end up draining the battery & others by the screen coming on easily by trackpad, volume keys, and power button. Its a lose/lose situation really...
Click to expand...
Click to collapse
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
seancneal said:
I bumped my minimum clock speed to 368 MHz, and I don't have this problem anymore. YMMV
Click to expand...
Click to collapse
Still happens to me when I try that. It occurs when you press the power button twice in succession.
Hi there,
anything new on this topic? I'm currently experiencing this annoying problem as described.
I've already tried to set the minimum clock to 368 Mhz but the bug still exists. Even setting CPU to standard clock (Max/Min @800) didn't solve the problem.
Is it possible that the reason is located already inside the overclocking kernel?
Greets
dktnecro
Generally if you're overclocking and you have lockscreen issues that are not present @ stock speeds, then it sounds to me like the overclock is too much and your system probably isn't stable.
Based on my experience overclocking computers, things can very well appear stable but if you do stress testing (8+ hours straight) things often crop up and show you that it is in fact not stable. This sounds like one of those things. And that's not good. Who knows what other corruption could occur during your use at that speed? I had the same lockscreen issues myself, and once I realized it was due to overclocking too much I ended up solving another issue I had where half of the calls I received were garbled to the person on the other end. No more lockscreen issues or garbled calls since backing off the o/c a bit.
If the issue doesn't happen at stock speeds then maybe it's just the kernel, and hopefully that isn't putting you at risk of any kind of corruption, either.
Keep in mind I really can't be 100% if overclocking will cause corruption on a phone, but based on a lot of time spend overclocking pc's I would have to guess that it can. I'm surprised that this isn't brought up more often on device forums.
ROM: Virtuous 1.0.2
Kernel: Virtuous Advanced 2.2.0
I'm having trouble with my screen struggling to turn on when I wake my phone if the cpu speed is anything above stock. If I push the power button once the capacitative buttons light and nothing else happens, if I push it a second time the lights turn off again and I briefy see my lockscreen flicker before my pained eyes
If I do this cycle many times over eventually I'll get lucky, but there's no pattern to the success and it's very frustrating.
The symptoms are similar to this thread: [Q] Phone unlocking screen issues. The method described there to solve the problem was to turn off on/off animations. I don't think this solution applied as I'm not using CM7.
I think the touchscreen input is recieved despite the screen itself having no picture - for example I can unlock my phone by swiping down (stock Sense lockscreen). If I touch the touchscreen in the right place to open the dialer while I've "unlocked" it in this way, when the phone finally wakes after frantic power button pushing, the phone will be in the dialer app.
I think it might be related to Sense as I tried a stock Sense from rmk - [ROM]Vision_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_12.5 0.60.24_26.08.04.16_M and overclocked using both Virtuous Advanced 2.2.0 and Pershoot's Kernel. In both cases I also had wake issues any time I tried to wake when the cpu was clocked above stock speeds (even 900MHz).
Further evidence towards a sense problem is that I don't have any issues when I'm at 1.4GHz when using CM7. I missed the sense apps too much to stay with CM7, however.
I have a workaround using CPU Tuner with a screen off profile of 246-806 Mhz, and I can then overclock freely afterwards. I can live with this but if anyone has an idea why this might be happening then I'd appreciate a solution.
As I've been lurking on XDA for a while but this be my first post, thanks to all you incredible developers who have made it possible for me to customise my phone in these fantastic ways.
Set your screen brightness to something greater than 50%. It's not a fix but a very reasonable workaround .
Sent from my HTC Vision using Tapatalk
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
The screen off issue is thoroughly discussed in the Virtuous kernel thread. I forget the exact explanation, but its got something to do with the CPU stepping while the screen if off.
The common fix is a SetCPU/CPU Tuner screen off profile, as you seemed to have discovered. But adjusting the governor type in addition to minimum CPU clocking seems to be the common solution used. I think the interactive governor seems to work best to prevent screen wake issues.
http://forum.xda-developers.com/showthread.php?t=967153
Yeah, I read that thread fairly extensively but the solutions there didn't help. I can easily replicate the problem by setting my cpu with the performance governor to anything above stock speed (i.e. the cpu will be at one single speed the entire time, I think?). The over 50% brightness solution works very well (at the expense of more noticeable battery drain)!
Atomcracker said:
Wow that worked perfectly! Thanks!
Was that fix well-documented anywhere, out of curiosity? I'd searched these forums quite heavily and didn't see that anywhere. Makes me feel silly that it was such a simple fix - I'd been flashing ROMs all night to get the same bug
Click to expand...
Click to collapse
I had seen the workaround mentioned on the CyanogenMod forums yesterday: http://forum.cyanogenmod.com/topic/20943-screen-doesnt-always-turn-on-from-sleep/
Does anyone else notice that the screen takes a longer time to turn on when on 4.0.3 roms? Its slow and sometimes it fades in instead of just coming on instantly. I'm on the CM9 kang but I noticed it on other roms
Sent from my Galaxy Nexus
Typically related to how the kernel is handling the cpu when the screen is off. If you're running setcpu or a cpu controlling app that's probably it, but i'd be surprised if the stock kernel would have that problem. Maybe try flashing another like lean kernel
Happens on every rom (currently on a cm10 nightly) ... phone is stable in just about every other way, but 1/50 (guessing) the unlock just goes sour.
It's as if the screen doesn't come on....
I tried raising my min cpu freq while sleeping- even at 512mhz it still did this occasionally.
Any thoughts?
pcguru000 said:
Happens on every rom (currently on a cm10 nightly) ... phone is stable in just about every other way, but 1/50 (guessing) the unlock just goes sour.
It's as if the screen doesn't come on....
I tried raising my min cpu freq while sleeping- even at 512mhz it still did this occasionally.
Any thoughts?
Click to expand...
Click to collapse
I've had this problem for quite some time as well, and I've read about it in the forums before. I believe that and the reboot in the camera app (try unlocking) are the two biggest issues right now. From what I've read in the android development forums these are likely kernel issues that won't be solved easily.
pcguru000 said:
Happens on every rom (currently on a cm10 nightly) ... phone is stable in just about every other way, but 1/50 (guessing) the unlock just goes sour.
It's as if the screen doesn't come on....
I tried raising my min cpu freq while sleeping- even at 512mhz it still did this occasionally.
Any thoughts?
Click to expand...
Click to collapse
CM10 has been notorious for this since day one. I haven't used a CM10 nightly in about 2 months, but I had quite a few BSOD's in ParanoidAndroid. I've been using tdmcode's AOKP41 for the past few days and so far I haven't had a BSOD, but from what I read in his thread in the development section I'm lucky.
One thing that makes it "less" of a hassle is that you can hold the power button until it reboots (around 10 seconds, maybe 15 or so) instead of pulling the battery.
I installed invisiblek's Lineage OS build from here: can't post links...just google 'invisiblek vk810' (not a recommendation, just a reference).
So far it runs great, but I get some occasional bouts of screen tearing....at least that's the best term for it. I googled 'flickering' and 'blinking' but the descriptions don't quite match what I'm seeing, and the 'tearing' results are more representative. Basically, the screen will flicker for a millisecond and on-screen items will just kinda jump around. It's as if the screen were torn from the tablet and very quickly moved to another position and then back.
The 'tearing' threads suggest enabling 'Disable H/W Overlays' but that didn't seem to make a difference. I can't reliably reproduce the glitches and I've tried disabling hardware items, factory resets and reflashing, but they keep coming back. They don't seem to happen at all during full-screen video playback, and they sometimes come in bunches (I'll read for 15 min with nothing and then I'll have several over 15 sec). The keyboard seems to be particularly problematic and it doesn't matter if it's the default keyboard or an app. This doesn't happen in twrp or any other roms (I've tried a few versions of cm 12.1). Brightness, adaptive brightness and live display don't seem to matter.
This rom is silky smooth and I'd love to stay on it, but the tearing is annoying, and I'm worried it might damage the screen. Any thoughts?
Following up...
The problem seems to be a problem with cpu throttling. I get no screen tearing as long as 2 or more cores are in use. Once it drops down to one online core, I start to see tearing. This only happens in 7+ roms. I've tried a 6.0 CM rom and 2 5.1 roms...no tearing. I've tried 4 7.1 roms and they all had tearing problems when the cpu throttles to one core (side note: there is only one (that I know of) 7.1 rom for the vk810. I flashed 3 different v500 (AOSP, crDroid, Official Lineage) roms and they all booted.. I'm probably going off-topic on my own thread, but it doesn't take much to get the vk810 running on a v500 rom).
So, I disabled MPDecision in the kernel and the tearing is gone. The only problem is that all 4 cores are always on. I've got them throttling down to 384mhz when the load drops, but I'm taking a hit to my battery life (which is good....the rom deep sleeps well). Does anyone know if MPDecision can be configured to leave CPU 0 & 1 on at all times?