Did a search, and didn't find anything regarding this, so I'll point this out. I've noticed whenever my Kaiser (KAIS100) goes to sleep, it doesn't actually sleep, I can still press every button and the phone will "wake", screen comes on.
When I check Spare Parts > Battery History, it shows my phone's been running for 5days even though it's been on for 10 minutes actual. If I continue to put the phone to sleep that time grows exponentially.
Is my KAIS really sleeping, or is there a bug somewhere?
I'm running l1q1d's latest .32 kernel, with Fat Free Froyo build with system/data on NAND.
Battery also only lasts about 8hrs in "standby", and not even 2hrs with full use. With WinMo, I get about 36hrs standby, and about 5hrs full use.
Krazy-Killa said:
I've noticed whenever my Kaiser (KAIS100) goes to sleep, it doesn't actually sleep, I can still press every button and the phone will "wake", screen comes on.
Click to expand...
Click to collapse
Screen comes on, obiusly, but its locked right? that the way its ment to be... if you wanna check the hour or see if u got messages or missed calls... or it unlocks?
Krazy-Killa said:
When I check Spare Parts > Battery History, it shows my phone's been running for 5days even though it's been on for 10 minutes actual. If I continue to put the phone to sleep that time grows exponentially.
Click to expand...
Click to collapse
I guess its not completley implemented yet, search this forum I remember I looked something about it, or post a comment to our good friend n2rjt in that thread:
http://forum.xda-developers.com/showthread.php?t=782269
Have you modified .nbh file with atools and entered the correct value on the advanced batt capacity? (units = battery real mAh * 1.6) if you havent or if you own an old battery you'll experience a lot of batt consumption or inaccurate readings....
albertorodast2007 said:
Screen comes on, obiusly, but its locked right? that the way its ment to be... if you wanna check the hour or see if u got messages or missed calls... or it unlocks?
I guess its not completley implemented yet, search this forum I remember I looked something about it, or post a comment to our good friend n2rjt in that thread:
http://forum.xda-developers.com/showthread.php?t=782269
Have you modified .nbh file with atools and entered the correct value on the advanced batt capacity? (units = battery real mAh * 1.6) if you havent or if you own an old battery you'll experience a lot of batt consumption or inaccurate readings....
Click to expand...
Click to collapse
The phone locks like it's suppose too, but the problem I'm having is the CPU of the Kaiser isn't actually falling asleep. I'm getting the same battery consumption as when the screen is off compared to on, and sitting there (no activity on my part, just leaving the screen on for no reason )
Every so often the phone will be asleep, and the only way to bring it back on is by hitting the power button, but about 95% of the time I can press the call button, end button, OK button, IE button, hell even push down on the wheel on the other side of the Kaiser and the screen will come on showing the lock screen.
As far as the battery capacity, I have not done that, but the phone's been auto-learning my capacity, and it will get to the 2160 units, compared to the 2000 it's always set too, and sometimes reach 2377 units.
I have tried several Radio versions, down to 1.65.xx.xx version (which was the original version on my phone), and no changes, and tried different builds and no change either. DZOs kernel doesn't make a difference either, except screw up my battery meter completely. lol
uhm thats wierd.. i can only unlock through the power button, what i have experienced is that if its conected to an external power source it does reacts to any button I press.... but not on battery... maybe its a build issue... right now im using scoots CM rls 5a, dont remember if warbyte's donut behave like that...
albertorodast2007 said:
uhm thats wierd.. i can only unlock through the power button, what i have experienced is that if its conected to an external power source it does reacts to any button I press.... but not on battery... maybe its a build issue... right now im using scoots CM rls 5a, dont remember if warbyte's donut behave like that...
Click to expand...
Click to collapse
Did some more testing, and found that without it plugged into power it does only respond to the power button, but again it's only about 15-20% of the time, and even those times seem iffy as it just seems like the phone's just slow to respond.
Phone is also somewhat warm as well even when "off", and I do have the phone overclocked to 450MHz, kernel is set to 425 (running a test on speed/stability atm)
At 425MHz it's still reasonably warm, and at 450 the temperature jumps alot.
Anyone else have an issue of the tap sounds when tapping on the screen sometimes not playing? Granted phone quality is great, and GPS is working well, though Camera is broken on my end, even though it was working before.
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
n2rjt said:
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
Click to expand...
Click to collapse
by chanse wasnt weather widget? had a really bad slowdown over scoots CM because of that widget, was constantly trying to update the weather....
albertorodast2007 said:
by chanse wasnt weather widget? had a really bad slowdown over scoots CM because of that widget, was constantly trying to update the weather....
Click to expand...
Click to collapse
Yes that's the one. it needs to be removed, and can be replaced by Fancy Widget.
Sent from my Android on HTC Kaiser/Kaiser/Polaris using XDA App
n2rjt said:
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
Click to expand...
Click to collapse
Ok, I'll give it a whirl, and remove some of the widgets I have running, and see if it does help out. Right now though I'm re-installing /system as I tried messing around with the density as 110 seems to work real well with where things are placed on the home screen (no widgets are overlapping each other), but Market won't work, and the Android Keyboard keeps crashing (on-screen).
But anyways, phone's booting back up, so I'll test out the battery life here again, as I got about 95% charge right now, so should serve as a good test for battery life, and CPU Sleepage.
Having a similar issue, seems to behave ok (screen lock comes on when I press power button) but power usage on standby is similar to original poster's. About 8 hours standby. Went to bed last night and it said 66% charged (1300mAH battery) and it didn't last the night. Takes a looooong time to charge to full though so I doubt it's lying about fully charging the battery, suggesting it's using it up at a fast rate.
How do I check background tasks?
Edit: This is with WiFi, GPS and Sync OFF by the way. On the other hand I live in a low signal area (typically 1-2 bars) could it be straining to get a better signal? Used to have an old nokia that used to run itself flat in no time when there was a low/missing signal!
Edit 2 : Figured it out, turns out the ebay app has a service and a process running - even with notifications turned off! Have killed these and see if anything improves
That could very well be part of the problem, although it shouldn't kill it from 66% with just the radio. How much capacity does it calibrate itself to?
cycloid said:
Having a similar issue, seems to behave ok (screen lock comes on when I press power button) but power usage on standby is similar to original poster's. About 8 hours standby. Went to bed last night and it said 66% charged (1300mAH battery) and it didn't last the night. Takes a looooong time to charge to full though so I doubt it's lying about fully charging the battery, suggesting it's using it up at a fast rate.
How do I check background tasks?
Edit: This is with WiFi, GPS and Sync OFF by the way. On the other hand I live in a low signal area (typically 1-2 bars) could it be straining to get a better signal? Used to have an old nokia that used to run itself flat in no time when there was a low/missing signal!
Click to expand...
Click to collapse
Phone Radio really shouldn't use more power with low signal, in fact it really shouldn't affect power output at all (well except the fact that it's on). I have a 1350mAH battery, but it's reading at 2470 adjusted, so I re-flashed a new kernel with the new battery changes, now it's reading 2437units adjusted, which is over 1500mAH for the battery which is not what I own. But on the bright side, my battery capabilities are improving, and the battery meter is starting to read alittle more accurately.
Krazy-Killa said:
Phone Radio really shouldn't use more power with low signal, in fact it really shouldn't affect power output at all (well except the fact that it's on). I have a 1350mAH battery, but it's reading at 2470 adjusted, so I re-flashed a new kernel with the new battery changes, now it's reading 2437units adjusted, which is over 1500mAH for the battery which is not what I own. But on the bright side, my battery capabilities are improving, and the battery meter is starting to read alittle more accurately.
Click to expand...
Click to collapse
yes, i boutght seidio 1600 mAh, and the kernel ended up adjusting it to 3260 units... (about 2000 mAh) maybe the 1.6 factor isnt right just as n2rjt said, maybe its closer to the 2.0
Seems like ebay may have been the culprit. Killed the ebay process and application in the background and only used about 10% over night (as opposed to over 60% the night before). I'll have to leave it overnight with ebay running again for a proper scientific test next
cycloid said:
Seems like ebay may have been the culprit. Killed the ebay process and application in the background and only used about 10% over night (as opposed to over 60% the night before). I'll have to leave it overnight with ebay running again for a proper scientific test next
Click to expand...
Click to collapse
Yah, I'm starting to run into issues with certain apps keeping the phone awake and not letting it sleep. I kill some of the apps and it actually helps out the battery some.
I installed the original launcher from one of the other froyo builds, but came across with an FC with acore, so now back with ADW.Launcher or LauncherPro.
Krazy-Killa said:
Yah, I'm starting to run into issues with certain apps keeping the phone awake and not letting it sleep. I kill some of the apps and it actually helps out the battery some.
I installed the original launcher from one of the other froyo builds, but came across with an FC with acore, so now back with ADW.Launcher or LauncherPro.
Click to expand...
Click to collapse
When you install a app, take a look at its requirements, like "PREVENT FROM SLEEP". You might have a app doing just that..
daedric said:
When you install a app, take a look at its requirements, like "PREVENT FROM SLEEP". You might have a app doing just that..
Click to expand...
Click to collapse
Yep, most of the apps I download have that. But in sad news, I'm actually going back to WMO 6.5 as I can't seem to keep Android stable on my kaiser.. I've reinstall the same build twice (which I know is not corrupted, as it was working fine 2 days ago), and Market is always corrupted...... So, for now, until I have a secondary phone I can revert too, I'll be going back to WMO for the time being.
Krazy-Killa said:
Yep, most of the apps I download have that. But in sad news, I'm actually going back to WMO 6.5 as I can't seem to keep Android stable on my kaiser.. I've reinstall the same build twice (which I know is not corrupted, as it was working fine 2 days ago), and Market is always corrupted...... So, for now, until I have a secondary phone I can revert too, I'll be going back to WMO for the time being.
Click to expand...
Click to collapse
Umh... sad...
We'll wait for you! Bye bye
daedric said:
Umh... sad...
We'll wait for you! Bye bye
Click to expand...
Click to collapse
LOL! Not like I'm leaving, I'll be popping on here every so often, and still doesn't mean I'll use Haret to load up Android to test out new builds that come out, and new kernels that are released in the future.
Krazy-Killa said:
LOL! Not like I'm leaving, I'll be popping on here every so often, and still doesn't mean I'll use Haret to load up Android to test out new builds that come out, and new kernels that are released in the future.
Click to expand...
Click to collapse
Man... that's a sin! You can't do that! You'll be off from the Brotherhood!
Kiddin' ;D
I'm still learning but I know that 1min + boot times aren't normal. I'm running Synergy + God Mode.
I'm also noticing about 1% a min of battery drain. I'm assuming the drain is mostly from 2 source, 1) I'm in it debugging and exploring a lot more and 2) I'm noticing it more due to the accurate battery indicator.
But if there are any suggestions to tweak these I'd appreciate it,
Thanks again!!
Well its a big rom, and you figure 15-35 seconds at the splash screen, and maybe another 30 give or take, you can get a minute boot time, though the very first time it'll take longer cuz' it has to build the caches. Also I would recommend changing the kernel, or wiping the battery stats after the phone is charged to 100%.
yeah what he said ^^^ all the sense 3.0 roms take a while to boot and it is perfectly normal.
Thanks guys, which kernel would you recommend?
redisk said:
Thanks guys, which kernel would you recommend?
Click to expand...
Click to collapse
I'm running Freedom and it's going good, but there are three Kernels for Sense that I know of. You just have to try them until you find one you like.
Freedom Kernel
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.
So I was streaming music from MOG and all was working well until my screen went off (idle). Music started to pause/buffer and kept doing so every 10 seconds. When I turn the screen back on and stare at it, it won't do it at all and I can see it load full on the seek bar. Only happens when screen goes off and phone goes idle. I'm guessing its something with the CPU throttling maybe? Is there any way I can fix this? I'm connected on WiFi 5G and I have "keep WiFi on during sleep - Always".
This seems to be a pretty common issue (I have it myself, when connecting via WiFi with adb I need to keep my display on) and I've seen two issues on file here and here. I've yet to see a fix for it yet though
Aww crap. Well that sucks. Does it happen on custom roms/kernels?
reyes.jr said:
Aww crap. Well that sucks. Does it happen on custom roms/kernels?
Click to expand...
Click to collapse
I'm running CM9 nightly with leankernel now. Although it's happened since I've gotten the phone, and I've ran probably half a dozen different ROMs and 3 different kernels, including stock. I vaguely remember reading some posts where people either said there was a fix or they were working on it, though I'm honestly not real sure.
K thanks for the info bro.
reyes.jr said:
So I was streaming music from MOG and all was working well until my screen went off (idle). Music started to pause/buffer and kept doing so every 10 seconds. When I turn the screen back on and stare at it, it won't do it at all and I can see it load full on the seek bar. Only happens when screen goes off and phone goes idle. I'm guessing its something with the CPU throttling maybe? Is there any way I can fix this? I'm connected on WiFi 5G and I have "keep WiFi on during sleep - Always".
Click to expand...
Click to collapse
I am also facing the same issue. Yesterday, I was downloading ARHD 3.0 directly on phone through wi-fi. Surprisingly the progress was 1% completion per minute in screen-off mode. But the moment, I would turn on the screen, the rate became 3-4 times faster. i.e. 3-4% completion per minute.
Deviating from topic, I have seen similar behaviour quite some time back in iPad1.
kizuki.buy said:
I am also facing the same issue. Yesterday, I was downloading ARHD 3.0 directly on phone through wi-fi. Surprisingly the progress was 1% completion per minute in screen-off mode. But the moment, I would turn on the screen, the rate became 3-4 times faster. i.e. 3-4% completion per minute.
Deviating from topic, I have seen similar behaviour quite some time back in iPad1.
Click to expand...
Click to collapse
Well glad to know I'm not in the same boat. Have any of u tried android 4.0.4?
reyes.jr said:
Well glad to know I'm not in the same boat. Have any of u tried android 4.0.4?
Click to expand...
Click to collapse
Yeah, I'm on Liquid 1.25 (4.0.4 based ROM) and it still does it. If I run a speed test and turn the screen off, let it finish and check it; it will never go much over 5 Mbit/s. When I run the test with the screen on, I will get 10-20 Mbit/s. This was of course testing on my home WiFi network.
This is pretty annoying because I download anime torrents every week and it's enough of a battery killer already just to download the thing, but now I have to leave the screen on in order for it to even finish in a reasonable amount of time. I've also tried setting the minimum clock speed to 1200 MHz in SetCPU just to see if it was a CPU throttling/bottleneck issue when the screen turns off. But it made no difference . This can't be a hard fix for Google/Devs.
At least with popcorn and franco kernels you can do
echo 1 > /sys/module/bcmdhd/parameters/wifi_pm
to put wifi on high performance mode with screen off. They say this can enable high throughput.
reyes.jr said:
Well glad to know I'm not in the same boat. Have any of u tried android 4.0.4?
Click to expand...
Click to collapse
Yes, I am using ARHD 3.0 which is based on 4.0.4
There seem to be definite improvements and it was worth the effort to update.
As far as I know, wifi goes into a low power state with screen off to conserve power/battery life.
My command put it in normal power mode, but kernel must support it
KiNG OMaR said:
As far as I know, wifi goes into a low power state with screen off to conserve power/battery life.
Click to expand...
Click to collapse
oooo, so only on WiFi does this occur? On 4g it doesn't?
This also happen to me.. Happened in 4.0.1 4.0.2 4.0.4 so far I managed to bypass the issue with wifi keep alive its a free app from play store.. You could try and comment if that works for you
Sent from my Galaxy Nexus using xda premium
Threre is no need for any custom kernel module. Im on Stock ICS 4.04 and found an easy workaround. Actually this issue is not an android bug, but an issue of streaming apps that aren't proberly coded for honeycomb and ICS.