Develop Bugs

[Q]How to wake up w/o battery removal?

How to wake up the phone without battery removal? I have Virtuous 1.0.1 ROM with advanced kernel and from time to time I have wake up issue. I would like to avoid removing battery because I have otterbox case on my phone.
Do you know any other way to wake up yhe phone?

Well if you can't wake it up with the button on top it is a problem. Are you overclocked? Try lowering it.
Sent from my T-Mobile G2

Open the keyboard....lol
Sent from my HTC Vision using XDA Premium App

wake up
I have seen the same behaviour with the stock htc latest (1.82.whatever).
top switch -- othing
opening kbd -- noting.
only a removal of the battery seems to help.
Of course it hasn't happened in a convenient place e.g. to see if I can still access it or if charging works etc.

If u installed trackpad wakeup, it seems to distort virtuous roms and keep the device from waking up all together.....there are posts about it in the developers forum
Sent from my HTC Vision using XDA Premium App

Also in some cases this is caused by underclocking with a screen off profile. I actually gave up on virtuous untill that problem gets solved. I havnt tried the latest version though.
Sent from my HTC Vision using XDA App

There are 2 distinct "screen on" issues with slightly similar symptoms.
One is the "screen wake issue" what is common with Virtuous, and typically caused by certain combinations of overclocking, and screen off profiles.
The screen wake issue is very well discussed in the Virtuous thread, and commonly/easily solved with the proper screen off settings.
http://forum.xda-developers.com/showthread.php?t=967153
But the screen wake issue, as far as I have experienced, manifests with screen sometimes flickering on for a second, and sometimes responding to multiple presses of the power button, or by opening the keyboard. There is a different issue, some have called "SOD" (screen of death) where the phone seems completely dead until you pull the battery and reboot. This seems to be more what you are describing, but I'm not sure. The cause of the SOD has not conclusively been discovered, and there is currently no known surefire solution. But it may be hardware and GPS related, maybe kernel related. Personally, I've experienced this across several custom ROMs (Virtuous, CM7), kernels, as well as stock. The only luck I have had, is that the stock DZ ROM with the Godspeed kernel is the only combination which seems completely free of SODs. One person sent his phone into HTC due to SODs, and they said it was caused by a faulty GPRS module, and fixed it by replacing the mainboard. Another person send this phone in, and it was returned untouched, with the same problem still present.
http://forum.xda-developers.com/showthread.php?t=857584&highlight=pulling+battery
http://forum.xda-developers.com/showthread.php?t=908095

shortlived said:
Also in some cases this is caused by underclocking with a screen off profile. I actually gave up on virtuous untill that problem gets solved. I havnt tried the latest version though.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Why people still do this just boggles my mind. All current kernels drop the processor down when the screen is off. There's no need - at all, for a screen off profile. It creates a wakeup issue as you can tell since SetCPU has to refresh the phones state then switch profiles in order to allow the processor to move into a higher state. That takes a lot of time (in computer time) thus creating this 'bug' that doesn't actually exist. The OC bug however does exist and is present no matter what you do aside from keeping it at 1.1GHz or less.

KCRic said:
Why people still do this just boggles my mind. All current kernels drop the processor down when the screen is off. There's no need - at all, for a screen off profile. It creates a wakeup issue as you can tell since SetCPU has to refresh the phones state then switch profiles in order to allow the processor to move into a higher state. That takes a lot of time (in computer time) thus creating this 'bug' that doesn't actually exist. The OC bug however does exist and is present no matter what you do aside from keeping it at 1.1GHz or less.
Click to expand...
Click to collapse
I had the screen wake issue on Virtuous, with NO screen off profile and OC'ed to 1 GHz. Making a screen off profile, but leaving a wide range for the CPU speed (not underclocking it) and interactive governor solved the issue in my case.

That might work better since most people I've seen tend to use the conservative or powersave gov. in their screen off profile. I'll correct myself too, what I said was from a CM standpoint since I've yet to use Virtuous.

Yeah, the screen wake issue on Virtuous is different from the one on CM7. If I remember properly, on Virtuous, using the advanced kernel results in screen wake issues for everyone or most people, unless you make some SetCPU/CPU Tuner setting adjustments.

Do you have SetCPU, or another program capable of CPU clock control installed? If not, install one of them and bring the max clock down... the Advanced Virtuous kernel boots at 245min/1516max - I noticed this after a fresh install of Virtuous 1.0.1/2 and the Advanced kernel

qzfive said:
Do you have SetCPU, or another program capable of CPU clock control installed? If not, install one of them and bring the max clock down... the Advanced Virtuous kernel boots at 245min/1516max - I noticed this after a fresh install of Virtuous 1.0.1/2 and the Advanced kernel
Click to expand...
Click to collapse
Completly agree.
I am shocked and appauled that most don't seem to understand that the os and it does not matter which(I.e. android,ios,windows) or platform (I.e. smartphone,tablet,desktop,etc) when you overclock more than just ur cpu speed is changed. If u have any experiance overclocking cpus on your home computer, you know u cannot let your system hibernate because it will not wake up. All operating systems allow the cpu to completly turn of in hibernation until it recieves an electrical pulse from the board. But if ur cpu goes from off to high it pulls way to much electricity and can't process then commands because all the recouces went to waking. If you have sleep parameters set with a narrower range the system will have enough resources left to process ur intial command...when it comes to sleep to wake there are no in between frequencies.
Sent from my HTC Vision using XDA Premium App

[Q] Screen won't wake due to OC

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/

Sleep of death

Is anybody else having issues with their ET going to sleep and you have to pull the battery to get it come back up? I thought it might have been my setcpu settings. So I cleared them and uninstalled it. I tried the midnight rom and the starburst rom. I tried the stable and exp LosKernel. None of these got rid of this issue for me. Randomly through out the day I can try to wake the phone up to use it and nothing happens. After a minute or two I have to pull the battery. I am currently testing the stock kernel.

Thats weird, the only time that happened to me was when i had setcpu, and i tried putting "screen off" value to 200/200.
You should install setcpu again, and make screen off value 500/500, and if you dont have the issue, then try making the value 200/500, if you dont have the issue at this value, then leave it as is.
Sent from my SPH-D710 using xda premium

I agree it is weird and I am not sure why it is happening. If it stays okay with the stock kernel then I may wipe and try the viperrom.

Yep happened twice the other day... Im on stock rom with lost kernel..roooted i put setcpu to 200/1200 after waking my screen for a minute used google came back 3 min later and phone was either off or wouldnt wake .. I had to pull battery twice.
I setcpu up to 1200/1200 never happened again.
This is a nice phone but very touchy.. Seems alot weird things goin on for some Et users.
Worst of all for this phone is Los or just weak /radio signal in general ..which is a samsung issue.
Sent from my SPH-D710 using XDA Premium App

Why people still insist on screen off profiles amazes me. When you hit the power button to wake it - the phone is stuck at 200MHz, you do realize this? If snything else is going on while it's stuck at 200 or SetCPU doesn't sample the phones state fast enough, it never gets out of 200MHz and locks up. Just like any other processor does when you overload it.
All the background processes going on even when the screen is off and somebody thinks setting the CPU max to 200MHz is a good idea? That's just asking for it. Not to mention the screen off profile is known to cause this issue. Notice how Virtuous, Viper, Cyanogen, and many other developers don't use one in their native OC daemons? There's a reason why. The phone sleeps just fine without it, just let it do it's thing.

Don't use offscreen profiles (the kernel is smart enough) and avoid using task killers, as those are likely to be the second leading issue.

I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.

ElAguila said:
I am having the issue even with setcpu uninstalled. I still have not found out what is causing it.
Click to expand...
Click to collapse
Just wanted to throw this out there: beware mislabeling this problem. The setcpu issue causing the phone the permanently lock up and require a bat pull is one issue, yes; slow screen wake up is a different issue. Sometimes if you hit the power button, the screen will not wake up on the first try. If you wait a few seconds and push in the button again for a second or so, the screen almost always will come after. Coming from a mo-pho, I actually had the stupid no-wake problem requiring bat pulls, so I'm extremely paranoid about by e4gt doing this -- but it really has been good about eventually waking up every single time...just try my instructions and see if it works for you, too.
Again, though -- setcpu issues may be a different problem entirely.

did you reinstall a rom and try it again or did you simply just unistall setcpu and try it. I say this because I had an issue when testing setcpu and my system still kept my cpu setting even after I unistalled the app. I had to reinstall the rom after wiping to get it to run properly again.

I think I have found the issue. I did a factory reset and installed the rom but I am getting an error now that is basically saying it can't read the internal storage card. So I think there are some actual hardware issues going on that need to be looked at by sprint.

how often has the sod been happening? I think i got it yesterday, but not sure.

Do you use setcpu?
Sent from my SPH-D710 using Tapatalk

This thread seems a little slow- has there been a solution found or are we isolated cases?
I reflashed the phone back to rooted stock and then flashed Blazer 4.1.
Got 2 SODs in the past week- one just a few minutes ago.
I tried calling the phone from another line, it rings but the screen is black and thus I couldn't answer it.
Power button and vol buttons work fine.
I had to powerdown and reboot.
Getting kinda frustating.

[Q] Sleep mode/ screen off problems

Okay does any one have this same problem or am i just doing something wrong?
Every time i let my kindle sit with the screen off after about 30 minutes or so, and I assume it keeps going and getting stuck in sleep mode but the only way for me to get it turned back on is to do the whole power button for 20 seconds and then reboot. Am I not being patient enough with it or is there some trick to getting the screen back on that i haven't found yet? Because I've tried multiple different things and there isn't a disable sleep mode option in my rom just the option to extend the time, even though its pretty much useless. But can anyone help me with this?

what rom are you on?

Right now I'm on Hell Fire 1.1 but last week i was running CM9 Reloaded and it did the same exact thing.

I was going to give a long speech about how people need to READ before installing any new roms but considering the Hellfire thread doesn't list what works and what doesn't, I guess it's not entirely your fault
It's called "sleep of death" (SOD). Some ICS roms have problems with it and some don't. The same could be said about certain individual devices. You could boost your minimum CPU usage to 600Mhz or more, or try a different rom. Though, it should be noted that changing your CPU settings will affect battery life.

okay that makes sense i had no idea that most of the new roms have problems with it. but I'll probably try to up the min cpu usage i suppose the difference between 600 MHz and 300 MHz isn't going to be a true killer for the amount i use it but which rom or roms would you recommend? That don't have this problem I'd really like to try barebones but every time i try to flash it my Kindle goes crazy so i gave up on trying with it.

[HELP] Panic - CPU seems broken, I need help!

First of all, Hi everyone - chefs, users and admins!
I am writing this post with a really heavy heart now, almost bleeding experience happened to me from nowhere about 2 months ago. I feel quite an advanced "flashoholic", however I've broke up with that few years ago. In 2013 I sold my Note 2 and started "new life" with Android, bought a DSLR and engaged into photography. This year, in february I have bought a tablet as I needed really something for business purposes, and I have chosen a Tab S 10.5 LTE. I didn't ever hear about any Knox tripping or anything, and as soon as it arrived I flashed a AOSP ROM to my thingie as I love AOSP overall. Than strange things started to happen with my CPU. As I recall I have noticed it first after installing Xposed to the tablet - it started heating pretty badly. When I checked my CPU states through ROM Toolbox etc I noticed it sometimes freezes at frequencies around 1.7-1.9 GHz, and during this behavior max frequencies could even fluctuate from 1.7 to 1.8, 1.9 and so on. It looks like "something" changes max frequency setting of CPU as it wants, whenever it wants to and pushes usage to the maximum.
Now, I started to look for a fix - uninstalled Xposed, every root apps etc. Nothing stopped it. I was "pretty sure" the cause is in AOSP thing and the conflict between my hardware and custom AOSP Roms. So after 2 months of tryouts to solve the problem, I today reflashed TW to "finally" get rid if this and save my battery life. What shocked me was... the bug is still here! Even with 0 apps installed, all ROM stock and clean, my CPU goes crazy, the back is hot, and CPU monitoring apps show a hard usage of 1.9 and 1.8 GHz frequencies. At this point I started to panic.
To mention - before I posted this here, tried to search over xda, googling it and so on, but it seems noone has such problem anywhere! As long as I know I can't get my warranty back, and I feel really panic and don't know what to do. I am asking experienced devs or anyone who faced it before for some help, on my knees. This tablet is great, but pretty useless when my battery hits 20% after 4 hours!
EDIT
I snapped a screenshot of some kernel options I don't understand, however someone maybe would find any wrong input here (as I can change them thanks to the app). Thanks. PS. I have changed max fr tp 550 in order to avoid heating and battery drainage, to this moment thayt's the only way I know to stop it.
Thank you very much for any help and advices, and sorry for my bad english.
/K.Z.

Try installing Watchdog, and in the setting include phone and all other process monitoring, see if it can locate what is taxing your cpu.
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite&hl=en_GB
John.

Tinderbox (UK) said:
Try installing Watchdog, and in the setting include phone and all other process monitoring, see if it can locate what is taxing your cpu.
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite&hl=en_GB
John.
Click to expand...
Click to collapse
Thank you, I will try it. Very helpful. I'll post how it's gone.

Tinderbox (UK) said:
Try installing Watchdog, and in the setting include phone and all other process monitoring, see if it can locate what is taxing your cpu.
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite&hl=en_GB
John.
Click to expand...
Click to collapse
Hi John, it looks like that option doesn't work. I see that none of apps exceeds CPU usage over 10%, but the clock still goes on 1.7GHz etc. Sometimes it cools down, but it happens rarely.

Did you adjust the setting to monitor all phone processes, even if you have an wifi only tablet still do this.
John.
Thejungle said:
Hi John, it looks like that option doesn't work. I see that none of apps exceeds CPU usage over 10%, but the clock still goes on 1.7GHz etc. Sometimes it cools down, but it happens rarely.
Click to expand...
Click to collapse

Tinderbox (UK) said:
Did you adjust the setting to monitor all phone processes, even if you have an wifi only tablet still do this.
John.
Click to expand...
Click to collapse
Sure, but the app doesn't seem to have any options button anywhere, just 3 tabs... sorry. However I can see it is monitoring all system apps also, if it helps.

it`s been a while, i will install it on my T800
John.
Thejungle said:
Sure, but the app doesn't seem to have any options button anywhere, just 3 tabs... sorry. However I can see it is monitoring all system apps also, if it helps.
Click to expand...
Click to collapse
---------- Post added at 10:40 PM ---------- Previous post was at 10:37 PM ----------
Hold the button left of the home button down to get the settings, the left touchkey button hold it down to get settings.
John.

Thanks but umm.. nothing happens. Tried holding down task switch capacitive button for few seconds on every tab, but it just goes to task switch view.

Strange, I just hold the button down and within 2 seconds the strip along the bottom of the display appears, maybe you are in the wrong mode, there are three section on the top of the screen, you need to select the far left one called STATS.
John.

Tinderbox (UK) said:
Strange, I just hold the button down and within 2 seconds the strip along the bottom of the display appears, maybe you are in the wrong mode, there are three section on the top of the screen, you need to select the far left one called STATS.
John.
Click to expand...
Click to collapse
VERY strange. I did it on all 3 tabs, just nothing happens. Is it possible that app changes maximum frequency of my CPU? I don't believe any app has possibility to do it on it's own...

Have you tried it again with watchdog on the same screen in my screenshot then press the button, watchdog does not change cpu frequency.
John.

I used to have the same problem on AOSP roms and some Touchwiz roms! When you first flash it and set things up, CPU usage is fine. But after a few days maybe hours, CPU would do the same exact thing like yours! Then my device gets hot and drains battery.
I found this to be a problem with AOSP 5.1.1 roms. Resurrection remix, CM12, PAC ROM and yeah. Never had problems on Cm11. The only ROM that solved my heating issues and no cpu problems are AOSP roms on 5.0.2 or Liquid Smooth rom. 5.0.2 was bug free. Liquid Smooth ROM has an custom kernel which helps cool down the device and reduce the high CPU usage. Seems to be the only ROM without issues for me on 5.1.1. For Touchwiz roms, I just install skyhigh kernel and turn on hotplugging and CPU multicore power saving to solve heat issues. But really on Touchwiz roms, CPU is fine most of the time for me.
My device is SM-T800 BTW. This is what I found out from flashing many roms.
Sent from my SM-T800 using Tapatalk