[Q] Latest test kernels a no go on my HP2 :( - Touch Pro2, Tilt 2 Windows Mobile General

I was very pleased to here that we were getting the bottom light to work properly along with fast sleeps/wakes. Over the last few days I have tried kernels 1293, 1297 & 1300. All goes well until the promised deep sleep arrives. The issue on the initial kernels was adjusted such that after some effort it does wake, but is so sluggish that it is useless. I have the luxury of having a charger for my phone at home, in the car and at work, so the battery usage isn't the major issue for me so I figured that I would leave some items running in the background so that I never hit the deep sleep. Unfortunately, the deep sleep seems to be resistant to my efforts. I leave on my wifi, gps, background data and auto-sync yet I still achieve deep sleep. It even occurred while on the charger. Is there something else I can try to keep from hitting deep sleep short of running a serious app constantly? For now I went back to the 1276 committed kernel and will just deal with the no bottom lights and landscape start-up issues. I still achieve deep sleep with the afore-mentioned settings "off" and it wakes with pep in its step.
Mostly running Froyo X Ginger, but it is also duplicated while running FRX06. Even with these minor inconveniences android is my main OS on my Sprint TP2 - Rhodium 400. Thx to all the devs for the awesome work. You've made me love my phone again!!

Related

battery drain tips?

When I run the latest android build on my Tilt 2, it flies through battery like no other.
Are there any settings I can tweak to get at least a full day's worth of use out of it (mostly in standby anyways)?
Thanks
Regards
Smith
I'd love to hear anyone's tips as well. As mentioned here:
http://forum.xda-developers.com/showpost.php?p=7959929&postcount=7622
Setting the sleep mode = 1 doesn't seem to work for me. The processor seemingly goes to sleep and enters a coma (yes, I set the clock speed back to stock in the startup.txt).
One quick tip to the OP is set the clock speed to stock.
Edit: sleep mode = 0 seems to work (GSM phone here). However, deleting the "acpuclock.oc_freq_khz=XXX" line from the startup.txt and setting sleep=1 just might work as well.
Edit2: sleep mode = 0 seems to result in the phone functionality breaking. It stopped waking up to phone calls after a while, and calling out wouldn't work either. Damn.. Just a heads up.
1. Close every program that you don't use on startup of android. You can do this with advanced task killer.
2. Run stock speeds.
3. Turn down the screen brightness.
4. Make sure your phone goes to sleep when you are not using it (green led = sleep)
Is advanced task killer installed by default?
Also, how can I clock it to stock? I wasn't aware that it was overclocked past stock.
Screen brightness makes sense, I'll definitely do that.
So, if green is sleep, what is the orange?
Thanks
Smith
I reckon hepatic feedback would drain a little battery on its own probably best to turn that off
This is all true. I'll have to do that.
Still figuring it all out. Once I can get a solid 18-24 hour charge cycle out of it, Android will become my primary OS, easily. Simply works better, IMO
For me sometimes it's green, sometimes it's Orange - not sure how to change it back green -
I use Advance Task Killer, but then i also read that Froyo 2.2 doesn't need a task killer?
The two things that have helped battery life the most were:
-Switching to stock clock speed (the reference over the overclocked BLZN which i loved but killed the battery life)
-turning off background processes... i only turn it on when i have to (using the market, etc)
I would love to hear more tips
The colours are not that hard.
Red/orange = awake
Green = sleeping
If the LED stays red, then your device is doing something, you can either wait or try closing the programs with the task killer. That will help sometimes.
For returning to stock speeds read the faq And advanced task killer can be downloaded in the market.
Thank you guys all so much, big, big help to me!
Android is definitely going to be my full time OS shortly
Smith
Its kind of tough trying to go anywhere without a charger nearby. The battery drains quickly and on top of that the actual battery meter is off.
So sometimes that is a main issue
Sent from my MSM using Tapatalk
throwback1718 said:
Its kind of tough trying to go anywhere without a charger nearby. The battery drains quickly and on top of that the actual battery meter is off.
So sometimes that is a main issue
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
Indeed but that is something that they are working on it as we speak. Give them time
I ran a test last night before going to sleep to see how long the phone lasts.
Charged my phone fully. Ran advanced task killer and killed all the programs. Put the phone in deep sleep ( green light).
Woke up 7 hours later and phone was completely dead. I do have auto sync turned on, but only over wifi, so it should not have used any data as i have the data turned off and no widgets on my home screens that auto-update.
I'll try again tonight for a shorter time (5 hours).
Running the blazn aug 30th build.
karan1203 said:
I ran a test last night before going to sleep to see how long the phone lasts.
Charged my phone fully. Ran advanced task killer and killed all the programs. Put the phone in deep sleep ( green light).
Woke up 7 hours later and phone was completely dead. I do have auto sync turned on, but only over wifi, so it should not have used any data as i have the data turned off and no widgets on my home screens that auto-update.
I'll try again tonight for a shorter time (5 hours).
Running the blazn aug 30th build.
Click to expand...
Click to collapse
How did you 'put the phone in a deep sleep'
I turned off all auto updates.
The next day i did the test again, charged the phone to 100% and used the phone moderately for 8 hours before the battery died.
Without overclocking i can safely say i can get the phone to last 8 hours with moderate to heavy usage, which is excellent.
My main problem with the new updates are that it constantly restarts or crashes after using it for less than 30 minutes while before I could use it for several hours. Not sure whether it's to do with battery life or not as when it boots back in WM the battery is near full.
The biggest things that have helped conserve battery life for me are disabling GPS and background syncing but some apps require this to be enabled. :S
Phone seems to recover from "sleep"
FWIW, I set sleep mode = 1 and removed the overclock line from the startup.txt and the phone SEEMS to sleep and "wake up" just fine. Previously, I had problems with the phone going to sleep and when waking up, everything seemed fine, but the phone didn't work. With the overclock line removed, it seems to "wake up" with the phone working now.
Just a heads up to anyone who wants to save battery life.. might want to remove the overclocking line in the startup.txt..

FRX03...GPS...Sleep Mode...

I searched for Sleep Mode and GPS problems, and of course since those are very common words in most posts, I was having a hard time actually finding if anyone else has my problem.
I am running the most current kernel of FRX03. I have a sprint Rhod400. This problem pre-dates the current kernel, and I am not sure how long it has gone on, because I was having a lot more issues with sleep mode back in the earlier kernels anyway, as I think all people were. I am running with sleep mode set to 1.
Whenever I start a GPS program, usually it is foursquare, when I kill all the apps including foursquare using Advanced Task Killer, the phone will not go back to sleep. I have also looked at the "running services" setting and nothing is running besides Android. It seems to me the GPS stays active even though the GPS icon and all hints that it is actually running ceases to be found. I am guessing this is causing the phone not to go back to sleep. I have not really tested it out with navigation or maps to see if it happens there also, but if my memory serves me right it does.
Any suggestions on possible fixes?
Disable GPS. It's a known bug, which has already been filed on the bugtracker.
If GPS is enabled, phone will not sleep - and I don't mean enabled in that there's the GPS icon in your notification bar, I mean enabled (checked) in Location & Security. Uncheck it there, and the phone will sleep.
This is all interesting, because my RHOD400 seems to sleep just fine (much of the time) with GPS enabled!
gnnash said:
This is all interesting, because my RHOD400 seems to sleep just fine (much of the time) with GPS enabled!
Click to expand...
Click to collapse
Enable GPS, then open an app that uses it. Leave GPS enabled, but close the app. Now try to put your phone to sleep .
I've definitely seen intermittent issues with sleep and GPS. Not sure if it's every time, but I noticed when the phone doesn't sleep, I disable GPS in loc&sec and it'll go to sleep.
The only other serious sleep-related problems I've had is with rogue apps stealing processor cycles and keeping the phone awake.
I'm running NAND were pm.sleepmode = 1.
Yesterday I left my GPS enabled and I seemed to be getting better battery life? Maybe it is just a fluke... But you never know!
I will try it on my other phone running HARET.
Lmiller1708 said:
I'm running NAND were pm.sleepmode = 1.
Yesterday I left my GPS enabled and I seemed to be getting better battery life? Maybe it is just a fluke... But you never know!
I will try it on my other phone running HARET.
Click to expand...
Click to collapse
Well better battery life is probably related to usage.
However, that would be interesting if on NAND the GPS no sleep bug is non-existent...
I honestly haven't tested it in a while. No one has specifically looked at fixing it. I guess it's possible a commit happened to fix it - just usually doesn't work like that .
I use the 11/22/10 XDAndroid build from the .cab and the bug is present. LED doesn't turn from orange to green until I turn off GPS in settings and turn off the screen.
He probably thought that it was sleeping because the screen turned off (I used to think the same thing).
gallahad2000 said:
I use the 11/22/10 XDAndroid build from the .cab and the bug is present. LED doesn't turn from orange to green until I turn off GPS in settings and turn off the screen.
He probably thought that it was sleeping because the screen turned off (I used to think the same thing).
Click to expand...
Click to collapse
No I knew it wasn't sleeping. I know the purpose of the LED being on always(sleep mode debugging). I was just trying to figure out why, and if there was a fix, which there isn't. In the earlier version of XDAndroid builds it was more than just GPS that was causing sleep issues, so back then I didn't think much of it not going to sleep, as I couldn't get more than about 4 hours of battery life out of those builds anyway. Now I am getting at least 12 with heavy usage and way more than that with light usage. So things have improved indeed.
slickdaddy96 said:
No I knew it wasn't sleeping. I know the purpose of the LED being on always(sleep mode debugging). I was just trying to figure out why, and if there was a fix, which there isn't. In the earlier version of XDAndroid builds it was more than just GPS that was causing sleep issues, so back then I didn't think much of it not going to sleep, as I couldn't get more than about 4 hours of battery life out of those builds anyway. Now I am getting at least 12 with heavy usage and way more than that with light usage. So things have improved indeed.
Click to expand...
Click to collapse
Indeed! So that is the fix - disable GPS. It sucks, but it's on the punchlist of things to fix. Unfortunately I don't know of anyone looking at it specifically at the moment, but I'm sure it'll get addressed.

[Q] Sleep Battery Life

Hey everybody,
Just made the jump from the iPhone 4S and have done the custom ROM/kernel thing the past week. Things were good at the start but I feel them slowly deteriorating.
I find my battery life during sleep has become much worse than before. I mean, it still kills the 4S which would see ~25% overnight. But I'm seeing 10% overnight right now, and was ~2% earlier in the week. I normally have my phone on the charger at night, but didn't last night and I'm kinda glad I got to see this. Makes me realize why I was likely chewing through more in the day too.
You can see what I'm running below in my signature. Last night I had 5 instances where the phone woke on its own. Likely due to emails coming in.
Am I expecting too much from my modifications? Am I doing something wrong? I'm ready to toss AOKP aside because of other issues anyway, but yesterday I also read it was known to have some excessive battery drain as well. Without turning this into a battle to defend the ROM you use (like half the threads in here), if you have other suggestions, feel free to throw in a ROM suggestion. I'll attach some pictures of my battery screen so anyone willing to give me a hand can help.
Thanks in advance.
I had this problem when I was running franco too. Switched to leankernel and never looked back. I get about 4-6% drain overnight as long as I dont do something stupid like leave something running by exiting with home instead of the back button. I also have wifi on 24/7 and gps off unless im nav'in. No BT
Screwedupsmitty said:
I had this problem when I was running franco too. Switched to leankernel and never looked back. I get about 4-6% drain overnight as long as I dont do something stupid like leave something running by exiting with home instead of the back button. I also have wifi on 24/7 and gps off unless im nav'in. No BT
Click to expand...
Click to collapse
I'm hesistant to blame the kernel. I was using franco prior to AOKP without issue. I didn't make that clear in the OP. I went 4.0.4 Stock -> Stock + franco -> AOKP b31 + franco. Things were good the first two steps and I'd like to think the first few days on AOKP.
Perhaps I have some background processes chewing battery - but there's nothing with a higher battery drain than Chrome beta with 2%. My phone idle and Cell standby had huge drain though. Could a weaker than normal signal cause this? Could my radio be the culprit?
Steps to best diagnose idle battery drain.
-Install CPU Spy and Better Battery Stats.
-Charge phone to full and let it run for several hours undisturbed (easiest to charge before bed, then unplug it when you know it won't be used till morning).
-Take quick note of your % loss per hour. Around 1%, you're golden. 1-2 is pretty normal. >3 and you've got issues.
-Launch CPU Spy. Most of the time should be deep sleep (we're talking about 95%). If your phone has been awake a lot, there's either an app that refuses to let your phone rest, or an OS/Kernel issue. If it's not extreme but noticeable, you likely just need to reign in settings on some apps to keep them from syncing so often or working in the background.
-Launch Better Battery Stats. Select Partial Wakelocks from the menu. These are all cases of apps waking the phone up, sorted by length. Go look at problem apps' settings/consider uninstalling if you don't need them. Kernel wakelocks should be low too.
Keep in mind that the goal here isn't really to get all these things to zero so do not obsess over small showings. Facebook with push notifications but updates set to never keeps my phone awake for about a minute or two every night, for instance. So does Handcent SMS. If you flash a rom and your phone needs to do a lot of syncing it's likely to show up in this kind of test as well. But for a night with nothing going on, nothing should be keeping your phone up for more than a few minutes total.
myrdog said:
I'm hesistant to blame the kernel. I was using franco prior to AOKP without issue. I didn't make that clear in the OP. I went 4.0.4 Stock -> Stock + franco -> AOKP b31 + franco. Things were good the first two steps and I'd like to think the first few days on AOKP.
Perhaps I have some background processes chewing battery - but there's nothing with a higher battery drain than Chrome beta with 2%. My phone idle and Cell standby had huge drain though. Could a weaker than normal signal cause this? Could my radio be the culprit?
Click to expand...
Click to collapse
Weaker than normal signal can kill a phone battery, when I'm in lecture out in the bumfuck nowhere school I go to, I get -100 to -120dbm, which kills my battery while i'm at school. If thats your situation not much to do besides hope radios may increase your signal, but if not then your basicly as SOL as i am and may have to just charge it
JoeSyr said:
Steps to best diagnose idle battery drain.
-Install CPU Spy and Better Battery Stats.
-Charge phone to full and let it run for several hours undisturbed (easiest to charge before bed, then unplug it when you know it won't be used till morning).
-Take quick note of your % loss per hour. Around 1%, you're golden. 1-2 is pretty normal. >3 and you've got issues.
-Launch CPU Spy. Most of the time should be deep sleep (we're talking about 95%). If your phone has been awake a lot, there's either an app that refuses to let your phone rest, or an OS/Kernel issue. If it's not extreme but noticeable, you likely just need to reign in settings on some apps to keep them from syncing so often or working in the background.
-Launch Better Battery Stats. Select Partial Wakelocks from the menu. These are all cases of apps waking the phone up, sorted by length. Go look at problem apps' settings/consider uninstalling if you don't need them. Kernel wakelocks should be low too.
Keep in mind that the goal here isn't really to get all these things to zero so do not obsess over small showings. Facebook with push notifications but updates set to never keeps my phone awake for about a minute or two every night, for instance. So does Handcent SMS. If you flash a rom and your phone needs to do a lot of syncing it's likely to show up in this kind of test as well. But for a night with nothing going on, nothing should be keeping your phone up for more than a few minutes total.
Click to expand...
Click to collapse
This is what every user should use to diagnose battery problems at first.

[INFO]Improve battery life when idle

Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
I have autorotation turned on but not the face orientation sensing. I haven't noticed a significant battery loss, at 19 hours with 10 left according to battery spy, but I'll give this a try and see if it increases it any.
i'll give it a shot. i was wondering how at work it would drain 2-4% an hour but at home with a crappy signal i'd only lose 6% all night.
at work it's in my pocket and at home it's stationary.
madsquabbles said:
i'll give it a shot. i was wondering how at work it would drain 2-4% an hour but at home with a crappy signal i'd only lose 6% all night.
at work it's in my pocket and at home it's stationary.
Click to expand...
Click to collapse
I have noticed Google Talk drains batteries when your signed in. By default your phone will sign in. If you don't use TALK, sign-out of the app and you will see increased battery life. Your wont ping the internet as much which saves batteries.
Thanks viperboy I took your suggestion and so far it seems to be helping.
I haven't tried that app yet, however I have definitely noticed an improvement in battery life by disabling auto rotation. Thanks for the info.
THIS NOTE 2 IS SENT FROM A GALAXY WHERE SAMSUNG SPRINTS TO THE TOP, AND JELLY BEANS EAT APPLES!!!!
after a bit of troubleshooting i found that battery monitor widget pro was the cause of my drain. after removing it i went from 2 to 3% an hour to 3% overnight. this really sucks as i love the info bmw colleects. this is the only device i have that suffers drain from the app.
Thanks for the info. I have been losing % 15 battery every night while I'm asleep and was wondering why
...from a Galaxy Note II
-viperboy- said:
Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
Click to expand...
Click to collapse
Thanks for the suggestions. I have heard so much about the great battery life, but that has not been my experience. I had a Note 1 and I had no problems. With Note 2, the battery drains to about 1/4 after about 7 hours with limited use. I have turned off auto rotation, lowered the screen brightness, changed auto check settings for email, and don't see much difference. In addition, it seems a shame that I should have to figure out ways to use fewer functions to make battery last for phone calls, since I never had to do that before. Any ideas?
Thank you for this info. I consistently get a full days charge of of my phone but was pretty clueless when it came to what was draining my battery. I've used the rotation lock app and will report my results to see if I get even more remaining battery each day.
Sent from my SPH-L900 using xda app-developers app
Thanks for the helpful advice Viperboy! I've definitely been having wake lock issues with my phone. Hopefully these apps will help me eliminate the problems.
kat3k said:
Thanks for the suggestions. I have heard so much about the great battery life, but that has not been my experience. I had a Note 1 and I had no problems. With Note 2, the battery drains to about 1/4 after about 7 hours with limited use. I have turned off auto rotation, lowered the screen brightness, changed auto check settings for email, and don't see much difference. In addition, it seems a shame that I should have to figure out ways to use fewer functions to make battery last for phone calls, since I never had to do that before. Any ideas?
Click to expand...
Click to collapse
As viperboy mentioned, BetterBatteryStats is your friend. It really will help you figure out why your phone isn't sleeping like it should. It definitely takes some time to monitor and figure out what the readings mean to help point you to the apps or settings that're affecting your battery, but well worth it. I also like having a better understanding of how things work on my phone.
i did a double check on battery monitor widget pro and it started draining my phone again. as soon as i uninstalled it everything was fine again. this is with both cleanrom and blazer. i'll just wait til official support comes and try it again.
-viperboy- said:
Hey guys, I was getting terrible battery life when the phone is idle. I looked into it to see what was going on. First off, I am on the stock rooted deodex'd ROM that scrosler posted. The biggest problem was an app I installed called Light Flow Lite, it controls your LED. It had over 6 hours of wakelock today. Removed it, not worth it at all.
The second thing I found that was interesting was after that, the phone STILL wasn't hitting deep sleep. I poked around in BetterBatteryStats and didn't find anything in there that would explain that. I then ran a "top" (in terminal or adb shell, type top -m 5 -t). Everything looked normal, nothing crazy. But I turned the screen off and let it run for a few seconds. I got a massive spike in CPU (anywhere from 15-35%) for system_server with the thread "WindowManagerPo" (which is likely short for WindowManagerPolicy).
I did some searching and it turns out that there is a bug with auto rotation that causes this. Essentially, the sensors don't stop looking for orientation change when the screen is off. I found reports of this in the Nexus S forums, GS3 forums, etc. This leads me to believe it is a Samsung kernel issue, since that's the least common denominator when it comes to the phones that had this issue. If you don't use auto rotation, you probably aren't encountering this issue (but keep reading for some good info below!) But I use auto rotation, how can I fix this?
Download an app called Auto Rotate Auto Lock. This app will turn off auto rotation when your screen turns off and enable it back when you turn the screen back on. This looks like this should really help to combat this bug and it handy for people like me who like auto rotation but don't want to have battery life suffer from something as stupid as this. I have verified that my phone now does enter Deep Sleep easily, and it hadn't hit that all day!
I also recommend an app called CPU Spy Plus (XDA thread). This app shows some very valuable information about your processor. You never want to see "Deep Sleep" under Unused CPU States as this means your phone isn't sleeping and is wasting battery!
It would also be good to download BetterBatteryStats (XDA Thread). This will help you nail down battery drain that you won't see in the stock Battery graph found in Settings. Things or importance are Partial Wakelocks and Alarms.
Monitoring these apps can really help you to increase your battery life on your phone. If anyone else is having bad battery life when idle, please try this out. I'm sure this will help you Feel free to ask questions, I will try to answer them as best as I can!
Click to expand...
Click to collapse
Have you tried the Perseus kernel? I hear the battery life is improved with it. So may be it doesn't have the rotate issue.
I've been using cpu sleeper and I easily get about 30 hours. Looks like the new apk fixed quad core. So when the phone is off it only uses one core and shuts down the other three and lights them back up when you need them.
Sent from my SPH-L900 using xda premium
ZenInsight said:
Have you tried the Perseus kernel? I hear the battery life is improved with it. So may be it doesn't have the rotate issue.
Click to expand...
Click to collapse
I'm on it now, but I haven't looked to see if it fixed the auto rotation bug yet,
rudyrude432 said:
I've been using cpu sleeper and I easily get about 30 hours. Looks like the new apk fixed quad core. So when the phone is off it only uses one core and shuts down the other three and lights them back up when you need them.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
That app is unnecessary. Pegasusq governor already does that by default. Goes to 1 core and 200mhz when screen off, at least that's how my Note 10.1 was. I assume it is the same here since the International GS3, GN 10.1, and GNII basically share the same kernel with a few minor differences.
I think I may try the perseus kernel today to see if it improves battery.. I haven't heard it does.. I just been seeing people do that benchmark stuff with it
-TeaM VeNuM Like A Boss
Interesting... I have a script that reports on CPU freq and, when plugged into USB (maybe the wall charger too, didn't check), it appears that the kernel runs cpu0 and cpu3 all the time, even when screen off. With the phone unplugged, it went to using only cpu0 but didn't cap the freq. It was spending a good amount of time at the higher frequencies even though I had nothing running.
MiguelHogue said:
I think I may try the perseus kernel today to see if it improves battery.. I haven't heard it does.. I just been seeing people do that benchmark stuff with it
-TeaM VeNuM Like A Boss
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1959898&page=5
Post #42
I installed the app to turn the rotation off when the screen is off so far everything good but when I get a call this goes crazy because the screen goes while in call. I know this because I have an smartwatch which it has a notification app and every message that the phone has my watch vibrates with that message and I had a call few minutes ago my watch started vibrating non stop until I hang up.
Sent from my SPH-L900 using Tapatalk 2

Battery drain / no deep sleep

Long story short, I have been experiencing a severe battery drain with any ROM I try for the last month or so. Some ROMs seemed not to have it until first reboot, then the drain showed up.
Installing BetterBatteryStats showed me there was a "fingerprint wakelock" active 100% of the time. This was a bit strange, because my fingerprint sensor doesn't even work most of the time (sometimes it works after installing a ROM, sometimes after a few reboots, but it always stops working eventually for no apparent reason).
But searching around, I came across this page, where the following step is suggested:
mv "/vendor/bin/hw/[email protected]" "/vendor/bin/hw/[email protected]"
By renaming the corresponding file on my current ROM (/vendor/bin/hw/[email protected]) and restarting the device, I got rid of the battery drain and it now shows a healthy deep sleep time! I suppose that kills the fingerprint sensor, but since it wasn't working anyway, no harm done.
Just posting it for posterity and reference to whoever wants to try, I have no idea if anyone else has the same issue. (now I'll go hunt down PowerManagerService wakelocks, which seem to be the next big thing eating battery)
First, thank you for your guide. After updating from 7.1.2 to 9 i experienced a severe battery drain issue as well and this solved it. Actually, the fingerprint sensor never worked on android pie for me (crdroid 5.3). I would like to add some information that may be usefull to people.
This battery drain was caused by the fingerprint sensor and can be diagnosed by cpu spy where you will see your phone not going into deep sleep at all (interactive mode kernel, no idea for performance or gaming modes), and better battery stats showing finger print sensor being responsible for a big part of kernel wake lock when the screen is off.
Renaming the file can be done either if you are rooted on the phone or ( as i have noticed many apps like netflix refusing to work on rooted phones, making it inplactical to having your phone rooted ) using adb usb debugging to rename the files. if you are not allowed to rename the files, remount the phone and try again, remounting will automatically mount it in ReadWrite, while sometimes the first time will mount only as read.
If the problem is fixed the cpu spy app will show a much larger time spent in the lowest clock state in interactive mode and actually phone spending time in deep sleep.
PS: DO NOT hunt down the power wake locks as stated in your post, as those are active when your screen is on, and those should be on.

Categories

Resources