been struggling to get some "normal" battery life on my #nexus4 since 4.2.1 and now I heard from everyone about 4.2.2 gives improved battery life but not to me.
is there anyone that can help me with analyzing how I can improve my battery life?
the current 4.2.2 battery life shows no improvement at all comparing to my 4.2.1 battery life (was on MiNCO and Faux 123 kernel with the same kernel setup during 4.2.1)
Current 4.2.2 setup:
PA 3.0+
Faux 123, 07b1 (for 4.2.2), Intellidemand. Eco Mode off, Max1512 Min384, UV-150 across
battery dropped from 100% to 80%
7h50m (while I sleep) on battery on 3G data connection ONLY (screen cap attached, please ignore the subsequent charging time)
2 minutes screen on time
Deep sleep 86% as shown on CPU Spy (screen cap attached)
Partial wakelocks kind of minor as shown on BetterBatteryStat (screen cap attached)
Kernel wakelocks msm_hsic_host wakelock 42m, improved from 4.2.1 (screen cap attached)
Good signal (screen cap attached)
All Syncs on, Google Locations everything off except Location History
This is mainly a test comparing to previous 4.2.1 setup and battery consumption seems no improvement at all from 4.2.1 to now 4.2.2, as opposed to everyone's comment out there.
Anyone care to comment? Why I can't see any decent battery life as compared to 4.2.1? and as compared to users who have the same setup PA+Faux?
After comparing the CPU Spy screenshot (over 50m not sleeping) and Betterbatterystat (Other) screenshot (awake 59m), it seems like most of these wakelock came from msm_hsic_host (42m). Is it true that this msm_hsic_host wakelock will keep the phone awake independent from any app's wakelock? In other words, even if I have nothing installed, the phone will still wake up if I have this msm_hsic_host wakelock?
schizophrenia said:
been struggling to get some "normal" battery life on my #nexus4 since 4.2.1 and now I heard from everyone about 4.2.2 gives improved battery life but not to me.
is there anyone that can help me with analyzing how I can improve my battery life?
the current 4.2.2 battery life shows no improvement at all comparing to my 4.2.1 battery life (was on MiNCO and Faux 123 kernel with the same kernel setup during 4.2.1)
Current 4.2.2 setup:
PA 3.0+
Faux 123, 07b1 (for 4.2.2), Intellidemand. Eco Mode off, Max1512 Min384, UV-150 across
battery dropped from 100% to 80%
7h50m (while I sleep) on battery on 3G data connection ONLY (screen cap attached, please ignore the subsequent charging time)
2 minutes screen on time
Deep sleep 86% as shown on CPU Spy (screen cap attached)
Partial wakelocks kind of minor as shown on BetterBatteryStat (screen cap attached)
Kernel wakelocks msm_hsic_host wakelock 42m, improved from 4.2.1 (screen cap attached)
Good signal (screen cap attached)
All Syncs on, Google Locations everything off except Location History
This is mainly a test comparing to previous 4.2.1 setup and battery consumption seems no improvement at all from 4.2.1 to now 4.2.2, as opposed to everyone's comment out there.
Anyone care to comment? Why I can't see any decent battery life as compared to 4.2.1? and as compared to users who have the same setup PA+Faux?
After comparing the CPU Spy screenshot (over 50m not sleeping) and Betterbatterystat (Other) screenshot (awake 59m), it seems like most of these wakelock came from msm_hsic_host (42m). Is it true that this msm_hsic_host wakelock will keep the phone awake independent from any app's wakelock? In other words, even if I have nothing installed, the phone will still wake up if I have this msm_hsic_host wakelock?
Click to expand...
Click to collapse
Give Harsh's Kernel a try
It seems you have android apps running in the background. That could be your main battery life issue.
Sent from my Nexus 7 using Tapatalk HD
schizophrenia said:
Is it true that this msm_hsic_host wakelock will keep the phone awake independent from any app's wakelock? In other words, even if I have nothing installed, the phone will still wake up if I have this msm_hsic_host wakelock?
Click to expand...
Click to collapse
Yes, AFAIK it's a bug in the baseband (even with 4.2.2). That wakelock is much reduced when on wifi. My msm_hsic_host is often 20% when on 3G :/
as I said, after trying different roms and kernels, it's come down to almost a conclusion that my bad battery life comes from the darn msm_hsic_host wakelock which prevent my phone from sleeping.
Wifi battery life has been very reasonable.
thanks everyone.
Conclusion is, even if I uninstall all possible culprit apps, as long as I have such msm_hsic_host wakelock going on my phone won't deep sleep
I still haven't got a clue how to remove such wakelock.
battery drain investigation
did some testings with [email protected]
Test:
- ran both phones (under different carriers, different roms, same kernel) Nexus 4 on 3G data for a certain window of idle time and we both got around 2.4% an hour battery drain.
- we both got minimal app wakelocks (not 0, but negilgible) but our phones were not deep sleeping the whole time. Why? we both got 1/8 to 1/10 time of msm_hsic_host wakelock
preliminary conclusion:
- even if we install minimal amount of apps which do not cause anyway wakelock, the phone won't go 100% deep sleep as long as we have this signal/radio related kernel wakelock msm_hsic_host wakelock. we also do not know how to get rid of it
- unsolvable atm. seems like a radio/kernel issue that no one can fix (region specific?)
- so it was never about rogue apps that caused my battery drain.
Try others combo's with fresh installs
The msm_hsic_host wakelock is because the 3G modem is connected to the phone as an external USB device controlled by the hsic host controller. When the modem wakes up for any reason (apps sync, location, tower ping, etc...) the wakelock is requested. The problem is that the hsic host controller doesn't go back into suspend mode properly, this is a problem with the kernel. The result is that because the hsic host controller isn't asleep the phone wont enter deep sleep while it waits for the hsic host to suspend.
There is the additional issue that if your signal is poor the operations that caused the wakelock in the first place take longer to complete thus lengthening the time the wakelock is held.
The issue is significantly reduced on WiFi for obvious reasons, all the data is transmitted via WiFi so the 3G modem doesn't need to wake up nearly as often, it still wakes up to deal with tower checks and that sort of thing to ensure that it has voice connectivity, but those events are much rarer.
There are kernels available that attempt to solve this problem, Harsh kernel as suggested by another user has fixes in it along with a lot of other changes, the fixed kernel I'm working on is stock with these changes as well, either should help, it's not possible to eliminate this wakelock completely without shutting down the 3G modem which would of course prevent data and voice use of the phone, but they will reduce the wakelock and may help with your battery life.
thracemerin said:
The msm_hsic_host wakelock is because the 3G modem is connected to the phone as an external USB device controlled by the hsic host controller. When the modem wakes up for any reason (apps sync, location, tower ping, etc...) the wakelock is requested. The problem is that the hsic host controller doesn't go back into suspend mode properly, this is a problem with the kernel. The result is that because the hsic host controller isn't asleep the phone wont enter deep sleep while it waits for the hsic host to suspend.
There is the additional issue that if your signal is poor the operations that caused the wakelock in the first place take longer to complete thus lengthening the time the wakelock is held.
The issue is significantly reduced on WiFi for obvious reasons, all the data is transmitted via WiFi so the 3G modem doesn't need to wake up nearly as often, it still wakes up to deal with tower checks and that sort of thing to ensure that it has voice connectivity, but those events are much rarer.
There are kernels available that attempt to solve this problem, Harsh kernel as suggested by another user has fixes in it along with a lot of other changes, the fixed kernel I'm working on is stock with these changes as well, either should help, it's not possible to eliminate this wakelock completely without shutting down the 3G modem which would of course prevent data and voice use of the phone, but they will reduce the wakelock and may help with your battery life.
Click to expand...
Click to collapse
thanks a lot... these are really helpful information.
thracemerin said:
The msm_hsic_host wakelock is because the 3G modem is connected to the phone as an external USB device controlled by the hsic host controller. When the modem wakes up for any reason (apps sync, location, tower ping, etc...) the wakelock is requested. The problem is that the hsic host controller doesn't go back into suspend mode properly, this is a problem with the kernel. The result is that because the hsic host controller isn't asleep the phone wont enter deep sleep while it waits for the hsic host to suspend.
There is the additional issue that if your signal is poor the operations that caused the wakelock in the first place take longer to complete thus lengthening the time the wakelock is held.
The issue is significantly reduced on WiFi for obvious reasons, all the data is transmitted via WiFi so the 3G modem doesn't need to wake up nearly as often, it still wakes up to deal with tower checks and that sort of thing to ensure that it has voice connectivity, but those events are much rarer.
There are kernels available that attempt to solve this problem, Harsh kernel as suggested by another user has fixes in it along with a lot of other changes, the fixed kernel I'm working on is stock with these changes as well, either should help, it's not possible to eliminate this wakelock completely without shutting down the 3G modem which would of course prevent data and voice use of the phone, but they will reduce the wakelock and may help with your battery life.
Click to expand...
Click to collapse
by the way, would you happen to know if franco kernel has such fix?
I use his kernel because i do feel the fluidity and smoothness of the kernel plus I have his app for the customizations (including color controls).
I tried Faux but I just can't get the same speed.
EDIT: trying Harsh kernel at the moment
schizophrenia said:
I have tried removing almost all apps except the normal google ones ....
and coinciding with this, another user from US also reported that his hsic wakelocks are a lot higher when he travelled to Taiwan and Hong Kong and his thought is it may be due to the fact of highly congested data traffic
Click to expand...
Click to collapse
I decided to respond here instead of cluttering franco's kernel thread... because many of the possible culprits are not kernel related.
Unless congestion is causing re-transmissions, other ppl's traffic shouldn't affect your phone -- certainly not waking it up. Even with retransmits, you would think that there would only be one single but longer wakelock. (The phone really shouldn't wake every 12 seconds on average.)
However, you do have a high concentration of towers there. Perhaps there is more handshaking with towers? I use llama to automate tasks based on cell towers, and sometimes I see a -1:-1:-1 tower -- followed 1 second later by a real tower. So I assume that would have been 2 back to back wakelocks for me. (I'm going to try St. Murray Cell Connectivity Tracker to have a look.)
If it helps, I can tell you that I disable notification/checking on apps such as Play Store and I freeze many pre-loaded gapps -- currents, play books/mags etc., google+, network location, talk, news&weather and I don't use FB/xda apps. And I use gmail servers to poll my imap and then have any mail pushed to my phone.
From your prev screen caps, the one app I would freeze as a test is your VoIP / texting app (line.jp?)
schizophrenia said:
by the way, would you happen to know if franco kernel has such fix?
I use his kernel because i do feel the fluidity and smoothness of the kernel plus I have his app for the customizations (including color controls).
I tried Faux but I just can't get the same speed.
EDIT: trying Harsh kernel at the moment
Click to expand...
Click to collapse
hows harsh?
iammudd said:
I decided to respond here instead of cluttering franco's kernel thread... because many of the possible culprits are not kernel related.
Unless congestion is causing re-transmissions, other ppl's traffic shouldn't affect your phone -- certainly not waking it up. Even with retransmits, you would think that there would only be one single but longer wakelock. (The phone really shouldn't wake every 12 seconds on average.)
However, you do have a high concentration of towers there. Perhaps there is more handshaking with towers? I use llama to automate tasks based on cell towers, and sometimes I see a -1:-1:-1 tower -- followed 1 second later by a real tower. So I assume that would have been 2 back to back wakelocks for me. (I'm going to try St. Murray Cell Connectivity Tracker to have a look.)
If it helps, I can tell you that I disable notification/checking on apps such as Play Store and I freeze many pre-loaded gapps -- currents, play books/mags etc., google+, network location, talk, news&weather and I don't use FB/xda apps. And I use gmail servers to poll my imap and then have any mail pushed to my phone.
From your prev screen caps, the one app I would freeze as a test is your VoIP / texting app (line.jp?)
Click to expand...
Click to collapse
I did a very simple test about tower handshaking by turning off GPS and go to map and i can see my location, under 3G data, jumps back and forth every 10s to 20s. Does that mean the handshaking is not good?
LINE is one app that I have to live with even though it is one of the drainer because i need this app.
anyway I will revisit this later a bit as it's kind of late now. thanks a lot for your analysis and it's very beneficial to me
calanizzle said:
hows harsh?
Click to expand...
Click to collapse
Harsh yields low hsic wakelock
and after franco merged the fix, now r85/r86 yields as few as Harsh.
schizophrenia said:
I did a very simple test about tower handshaking by turning off GPS and go to map and i can see my location, under 3G data, jumps back and forth every 10s to 20s. Does that mean the handshaking is not good?
Click to expand...
Click to collapse
Unlikely that it indicated anything related to your battery.
Llama learned about 12 towers within my cell. I would expect much more in HK so I was only exploring what happens when you have so many towers within range -- whether the phone constantly have to handshake with every tower in range or only react to changes with the current tower. St Murray shows many changes (e.g. signal strength or location changes) but that doesn't cause an usually high wakelock count for me. So maybe there is only a wakelock on a handoff.
schizophrenia said:
LINE is one app that I have to live with even though it is one of the drainer because i need this app.
Click to expand...
Click to collapse
That's what I assumed... but it's worthwhile freezing it for 20 minutes and decide what to do if it turns out to be the culprit.
iammudd said:
Unlikely that it indicated anything related to your battery.
Llama learned about 12 towers within my cell. I would expect much more in HK so I was only exploring what happens when you have so many towers within range -- whether the phone constantly have to handshake with every tower in range or only react to changes with the current tower. St Murray shows many changes (e.g. signal strength or location changes) but that doesn't cause an usually high wakelock count for me. So maybe there is only a wakelock on a handoff.
That's what I assumed... but it's worthwhile freezing it for 20 minutes and decide what to do if it turns out to be the culprit.
Click to expand...
Click to collapse
i will try freezing a few apps and see
man. thanks a lot for the constant help.. although some of them i do not understand but i can see you are trying to help
appreciate it
schizophrenia said:
i will try freezing a few apps and see
man. thanks a lot for the constant help.. although some of them i do not understand but i can see you are trying to help
appreciate it
Click to expand...
Click to collapse
iammudd, check this out
freezed: LINE, Whatsapp, all Sync, Zooper Widget (different time frame as I did not have 7 hours for that)
Yes sure the battery got better a bit
it's quite likely it's LINE which caused the difference
let me try one more time by just freezing LINE maybe tomorrow or something
thoughts?
schizophrenia said:
freezed: LINE, Whatsapp, all Sync, Zooper Widget (different time frame as I did not have 7 hours for that)
Click to expand...
Click to collapse
Yes, those apps had some effect but not as much as I had hope. You're still getting 1357 msm_hsic (1 in 15 sec).
In the kernel wakelock screen, PowerManagerService shows you the total of partial wakelocks. You want to google the top items in partial wakelocks screen and see what's causing them. During sleep, I DON'T have sidekick_trafficintentservce, signalcollector nor rilj
Did a quick search and it seems like sidekick is related GoogleNow (which have been reported as a power hog since it uses gps and then keeps searching for nearby stores, etc.) The other 2 seem to be from location reporting. I don't have any of these 3 enabled if that helps so try disabling gps and location reporting in settings (and freezing gNow, latitude, fb reporting, etc)... You can decide what you want to keep later. (FB has also been reported to be bad for batt. Ppl use the web interface instead.)
You may also want to check out this tutorial on BBS http://www.alliance-rom.com/community/wiki/better-battery-stats-guide/ Also, I was referring to these apps to check cell towers:
https://play.google.com/store/search?q=llama and https://play.google.com/store/apps/details?id=org.stmurray.CellConnectivityTracker
iammudd said:
Yes, those apps had some effect but not as much as I had hope. You're still getting 1357 msm_hsic (1 in 15 sec).
In the kernel wakelock screen, PowerManagerService shows you the total of partial wakelocks. You want to google the top items in partial wakelocks screen and see what's causing them. During sleep, I DON'T have sidekick_trafficintentservce, signalcollector nor rilj
Did a quick search and it seems like sidekick is related GoogleNow (which have been reported as a power hog since it uses gps and then keeps searching for nearby stores, etc.) The other 2 seem to be from location reporting. I don't have any of these 3 enabled if that helps so try disabling gps and location reporting in settings (and freezing gNow, latitude, fb reporting, etc)... You can decide what you want to keep later. (FB has also been reported to be bad for batt. Ppl use the web interface instead.)
You may also want to check out this tutorial on BBS
http://www.alliance-rom.com/community/wiki/better-battery-stats-guide/
Click to expand...
Click to collapse
thanks for the info
I have freezed FB when screen off already. and I have turned off "all" location reporting/history etc. but I did have Google Now enabled.
Well, with you help at least I know I can achieve close to perfect idle drain IF I disable LINE and Google Now etc. But nevermind as I need these 2 apps to run. Still, as I assumed, my wakelocks would still be somewhat higher than in other countries.
i am undervolting 1 step at this moment. it helps a tiny bit. ha
Did you see a reduction in idle drain when you switched to Franco r85/86? I saw a reduction in msm_hsic_host wakelock but no reduction in battery drain (still 3%/hour).
zouden said:
Did you see a reduction in idle drain when you switched to Franco r85/86? I saw a reduction in msm_hsic_host wakelock but no reduction in battery drain (still 3%/hour).
Click to expand...
Click to collapse
on r85/86, for me personally, the hsic wakelock has been reduced together with battery drain.
but r90 the battery drain came back even though the hsic wakelock is still low
Related
Im currently on XXJVS with Semaphore 1.7 kernel, but i have experienced the same behaviour the last weeks (or maybe i just started noticing recently): traveling starts a battery drain
Update: see post #22
Some background:
I suffered from the Android Process battery drain up to XXJVR. Flashing XXJVS seems to have improved things (after numerous reflashes of XXJVR and XXJVQ which didnt help. My phone's cpu keeps between 1% and 3% when sleeping, but i have noticed that Cpu rockets to like 30% as soon as i leave my house to go to work, or leave work to go home. Its as if the phone keeps trying to connect to some network all the time, but only while in motion (and trying to lock in from tower to tower?). The problem is however that Systempanel nor the log give great clues where to look.
Examples:
In this first example, my phone is hooked to the charger during the night, and the alarm clock is running (hence the steady 10% cpu load). As soon as the phone is disconnected, cpu drops to low levels. On the exact minute i leave home, cpu rockets. And yes,i arrived at work around 07:50.
Home environment:
- connected to wifi
- good 3G coverage
- 3G, Bluetooth,GPS enabled
- no Bluetooth profiles present
Work environment
- wifi network present but not connected
- average 3G coverage
In this second example, i'm at work, hardly using the phone. Without touching the phone, stepping into my car and driving off, the cpu kicks in again. Notice there is no Device Usage whatsoever at the moment the CPU climbs. Bluetooth profiles active at this point and paired & connected to the carkit.
This last screenshot shows the typical clues (or lack thereof) that SystemPanel shows: just the System process using the most CPU.
Also the logcat doesn't provide much clues (or too many maybe) either. I have found that some applications couldn't contact GoogleAnalystics because i have AdFree installed, so i uninstalled those apps.
Frankly, i don't know where took look further. The damn android 'System'process just doesn't give enough clues. I have formatted internal & external SD, deleted cache & Dalvik cache, flashed & factory resetted to no avail. I'll try to have a log running tomorrow morning just before leaving the house to see if i can find what log entry corresponds to the system process kicking in. In the meantime, has anyone ever seen this behaviour, or any hints where to look?
adb bugreport > c:/report.txt
look there maybe
Install System Tuner pro it has option to record processes(+analyzer ) better than System Panel.
..try freze Maps or turn off network localization -Uncle Google likes to locate phone very often .
Sent from my GT-I9000 using xdapp
Hi,
Same phone and ROM, same problem.
Keep us updated!
Hmm, I have heard Galaxian kernel is battery sucker too...
Regards
wingg said:
Install System Tuner pro it has option to record processes(+analyzer ) better than System Panel.
..try freze Maps or turn off network localization -Uncle Google likes to locate phone very often .
Click to expand...
Click to collapse
in short words - bull****
i have not touched (freezed/deleted) any app
yet still i have not noticed a drain, any kind of drain
let him determine what app is causing the 100% cpu usage first
prior to advising him to freeze or delete anything - that is wise you have to agree
also localization service would not provide such high cu usage
think please
Hi,
It might be facebook 1.7.1. There are several complaining comments that "upload manager" process is running in the background and prevents phone from going into deep sleep mode.
i got data connection active all the time with all apps syncing (gmail, twitter, facebook)
and phone got no problem sleepin =)
pwhooftman said:
Im currently on XXJVS with Semaphore 1.7 kernel, but i have experienced the same behaviour the last weeks (or maybe i just started noticing recently): traveling starts a battery drain
Some background:
I suffered from the Android Process battery drain up to XXJVR. Flashing XXJVS seems to have improved things (after numerous reflashes of XXJVR and XXJVQ which didnt help. My phone's cpu keeps between 1% and 3% when sleeping, but i have noticed that Cpu rockets to like 30% as soon as i leave my house to go to work, or leave work to go home. Its as if the phone keeps trying to connect to some network all the time, but only while in motion (and trying to lock in from tower to tower?). The problem is however that Systempanel nor the log give great clues where to look.
Examples:
In this first example, my phone is hooked to the charger during the night, and the alarm clock is running (hence the steady 10% cpu load). As soon as the phone is disconnected, cpu drops to low levels. On the exact minute i leave home, cpu rockets. And yes,i arrived at work around 07:50.
Home environment:
- connected to wifi
- good 3G coverage
- 3G, Bluetooth,GPS enabled
- no Bluetooth profiles present
Work environment
- wifi network present but not connected
- average 3G coverage
In this second example, i'm at work, hardly using the phone. Without touching the phone, stepping into my car and driving off, the cpu kicks in again. Notice there is no Device Usage whatsoever at the moment the CPU climbs. Bluetooth profiles active at this point and paired & connected to the carkit.
This last screenshot shows the typical clues (or lack thereof) that SystemPanel shows: just the System process using the most CPU.
Also the logcat doesn't provide much clues (or too many maybe) either. I have found that some applications couldn't contact GoogleAnalystics because i have AdFree installed, so i uninstalled those apps.
Frankly, i don't know where took look further. The damn android 'System'process just doesn't give enough clues. I have formatted internal & external SD, deleted cache & Dalvik cache, flashed & factory resetted to no avail. I'll try to have a log running tomorrow morning just before leaving the house to see if i can find what log entry corresponds to the system process kicking in. In the meantime, has anyone ever seen this behaviour, or any hints where to look?
Click to expand...
Click to collapse
i think you should go out and do some thing better with your life then watching what a battery uses
i think its a waste of space to quote WHALE post
and well if he got battery drained overnight it is important to determine why
it should not happend
Just a quick question, where is the phone when you are in the car? I have noticed that if I keep my phone in my trouser pocket while driving, I loose signal frequently, shown on Bluetooth unit, and over a 3hour journey I can loose 30% battery, but if I put the phone in my shirt pocket I do not loose signal and my battery loss is about 20%.
My theory is that the phone signal finds it easier to penetrate the glass windows of the car rather that the metalwork.
Similarly to Geryatrix, when I leave my phone beside my bed (=~~, best place for alarm), my battery drains because the phone stays with a very low network signal and keeps searching for better antennas, I guess. But then at "Battery Usage" I could see that "Cell Standby" was eating my bat, not the "Android System".
battery drains from wifi staying connected in idle state - thats a bug in my opinion from samsung - it should not use such ammount of energy
data connection in idle is almost unnoticable in battery use
When I had facebook 1.7.1 installed, "Android System" was consuming 20% battery.
After I uninstalled facebook 1.7.1 and the problem is gone, "Android System is back
to normal, about 4%.
got-petrol said:
i think you should go out and do some thing better with your life then watching what a battery uses
Click to expand...
Click to collapse
I think you should learn not to quote an entire long message for the sake of making 1 stupid remark
Start post will be updated in a few minutes with some new information.
seems like one of apps you use is trying to connect somewhere
have you made bugreport - i think you will find the culprit there
Have you tried disabling fast dormancy? Maybe these wakelocks are caused by incompatible 3g cell.
Use *#*#9900#*#* to find option to disable it.
Sent from my GT-I9000 using xda premium
$omator said:
think please
Click to expand...
Click to collapse
No comment...
Sent from my GT-I9000 using xda premium
wingg said:
No comment...
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
and what is your problem to start oftop whining?
use report button if you do not like my post or tone of it
and freezing/deleting apps is not and never will be an issue solver
system works perfect with none of stock apps touched
using memory killers and altering system with such freeze options
is on the other hand source of 9 on 10 problems
$omator said:
battery drains from wifi staying connected in idle state - thats a bug in my opinion from samsung - it should not use such ammount of energy
data connection in idle is almost unnoticable in battery use
Click to expand...
Click to collapse
Hi,
I have opposite experience. Keeping Wifi enabled causes almost no battery drain for me, keeping 3G enabled does big time. My Galaxy Tab 10.1 Wifi version is set to never let the wifi connection sleep, and still battery drains no more than 1% or 2% a day is the tablet is not used.
I tested today with Wifi disabled. Still the Enter Dormancy messages appear each 5 seconds, altough the CPU hit is less. The Fast Dormacy messages seem purely cell-tower related, and wifi-unrelated. The Dormancy messages start as soon as i start moving, and stop when i'm home. I will update the startpost agan tonight.
---------- Post added at 06:55 PM ---------- Previous post was at 06:52 PM ----------
Kurre said:
Have you tried disabling fast dormancy? Maybe these wakelocks are caused by incompatible 3g cell.
Use *#*#9900#*#* to find option to disable it.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Hi,
I entered this Sysdump menu, the button read ""Enable Fast Dormancy" so i guess that means it was disabled all along. I enabled fast dormancy and will continue to test.
I monitor battery use carefully and freeze apps that cause unnecessary drain. I use 2g only. I use Better Battery Stats to identify wakelocks. Everything in my phone seems set up properly but I cannot figure out how to deal with battery drain due to a poor signal in my area. I have tried using airplane mode but this results in exchange/email, friendcaster, and gmail (among others) wakelocks. I have no issues with wakelocks on the two tablets I use when wifi is turned off but turning off data on the Vibrant seems to offer no battery saving benefits. Even when I turn off syncing completely, I run into wakelock issues. I'm using bionix right now but I have had this issue with many ROMs.
Bottom line: If I leave data activated, I get significant battery drain due to a poor signal. If I turn data off, I get significant battery drain due to wakelocks. How do you guys handle this problem?
Hi...
In my opinion,
1. you try diffenrent modem for optimal signal fetching....
2. Try Juice defender like apps that prevents unncessary battery drain to a greater extent, if it is PRO version, then it is worth like anything.....
3. Try some CPU slide or voltage control to reduce the battery drain...
After sincerely trying this for about one or two days stick on to the optimised parameters, definitely you will be get rid of battery drains.....
Dont mind me if it not much useful....
All the best...
Are you running the original Bionix?? That's old school stuff. You can try different modems to get better signal, but a bad signal will drain the battery no matter what phone you have. At least it has with every one of my phones. I would start at fixing permissions under ROM manager, reboot into CWM, repair permissions in there, reboot and see what happens. That has fixed app issues for me before.
But really, if you are still on Bionix, I would recommend updating to Fishmanmod's updated version of Bionix with a clean wipe. Could give and ICS rom a try, also.
dpaul007 said:
Are you running the original Bionix?? That's old school stuff. You can try different modems to get better signal, but a bad signal will drain the battery no matter what phone you have. At least it has with every one of my phones. I would start at fixing permissions under ROM manager, reboot into CWM, repair permissions in there, reboot and see what happens. That has fixed app issues for me before.
But really, if you are still on Bionix, I would recommend updating to Fishmanmod's updated version of Bionix with a clean wipe. Could give and ICS rom a try, also.
Click to expand...
Click to collapse
I'm using fishman's mod of bionix.
I think I found a solution to my problem. Jakub Klos' email fix prevents wakelocks when data is shut off. You can find the file and info here:
http://forum.xda-developers.com/showthread.php?t=1253583
Are you sure it's a signal issues? Maybe it's an application that's causing the drain. Have you tried reflashing?
iynfynity said:
Are you sure it's a signal issues? Maybe it's an application that's causing the drain. Have you tried reflashing?
Click to expand...
Click to collapse
I believe so. Even when all my accounts were set to manual, when I left data on during the day at work, the drain was out of control and there were no significant wakelocks. The email app I had been using was also causing battery drain when signal strength was poor. I used the aforementioned email.apk all day today with exchange set to push. I turned data off when I didn't need email or when my signal was poor (most of the day) and the email app didn't cause any wakelocks (it did before). After 13 hours (1 hour of display time), I have 65% of my battery left. BetterBatteryStats shows no significant wakelocks.
[Q] Battery life terrible, despite trying all the supposed "fixes", hardware problem?
I got my N4 a bit less than a month ago by this point. I've rooted and tried most ROMS from stock to CM10.1 to PA, etc. However, my battery life is consistently not so good. Coming from a One XL on CM10, I was used to bad battery life, but I expected the N4 to be better.
I don't have any screenshots, but here are my averages:
Time on Battery: 10-14 hours
Screen on: ~1.5 hours (usually, never have gotten over 2.5)
Android OS kept awake: ~1-1.5 hours
I know I'm among the group of people with the problem of Android OS keeping the phone awake, and I see all of these kernels attempting to fix the msm_hsic_wakelock issue, but I'm still having that as well.
I'm always on auto-brightness, Google sync on (calendar, chrome, gmail), Google Now enabled, etc. I'm also always on data, usually 2 bars + (the signal never gets worse than yellow on the battery graph.
Lastly, on wifi, all of these issues are gone. My idle battery drain is also phenomanol on wifi compared to data or even no wifi + no data. In about 8 hours I drained ~8% even with the data off.
Any ideas? I'm getting really frustrated. I see people claiming 2+ hours screen time or 20+ hours on battery on stock phones! I'm nowhere near the average battery times.
I know I'm among the group of people with the problem of Android OS keeping the phone awake, and I see all of these kernels attempting to fix the msm_hsic_wakelock issue, but I'm still having that as well.
Click to expand...
Click to collapse
Android OS is not keeping your phone awake. It's one of those crappy apps you have installed that are causing a wakelock causing the phone not to deep sleep.
Download: http://forum.xda-developers.com/showthread.php?t=1179809
Use it to debug partial and kernel wakelocks (primarily partial wakelocks). Check CPU states using that app or download CPU Spy from play store.
It needs to be deep sleeping.
Google Now: Disable cards that you dont use.
Turn off auto brightness and adjust it to your liking (CM10.1 has a feature if you long press on status bar it will adjust its brightness so you can do it like that).
Use Franco Kernel r23 (it's the most stable one, if you want to experiment you can try r26).
Google Maps: turn off Google Maps Latitude and its automatic reporting of your location and uncheck auto reporting in your location.
https://play.google.com/store/apps/...xLDEsImNvbS5iaWdleWVzMHgwLnRyaWNrc3Rlcm1vZCJd use that app with Franco Kernel (or buy his app) to adjust its kernel settings.
http://zephik.com/upload/Screenshot_2012-12-14-19-05-58.png is a screenshot from last month. Pretty good battery overall for me.
Press the thanks if I helped. Will reply back if you have any questions or follow ups.
I've been on CM10.1 nightly 1231 for 3 days now and I can happily say that my battery is much better than before.
I've averaging 24-28 hours with 3 hours screen on with data only and usually charging at around 10%.
Always Enabled:
All Location Services
Google Sync
Always Disabled (except when needed):
Google Maps/Latitude location settings
Bluetooth, WiFi, GPS
Google Now cards that I don't normally use
Some things I've noticed:
- When I flash a new ROM and restore my TiBu (flashable zip or regular restore) I find that my battery life is average at best.
- When I flash a new ROM and fresh install my apps from the Play Store my battery life is good to great.
- Third party kernels can sometimes be wonky on this phone. I haven't tried Faux or Franco kernel since flashing 1231 because I've been getting great performance on CM kernel.
- When my kernel CPU is set to "ondemand" the performance is average at best. Changing it to "interactive" has helped improve my battery life... with no other kernel tweaks involved.
Apps like Facebook and Facebook Messenger seem to cause issues with my battery life also. When I was on CM10.1 nightly 1223 I had Facebook Messenger installed and my averages were 12-14 hours off battery. So by eliminating a few apps on fresh ROM installs I've been able to see the different effects they've had on my battery life. Basically any app that uses GPS can potentially be a battery hog even when the phone is not in use.
So from my points above are also some of my takeaways. Try a fresh install and watch what apps you install. Try a few different kernel governors (esp if you're on a custom ROM). You can improve performance by trial and error!
Good luck.
EDIT: zephiK's points above are also valid and I can confirm they've helped my battery life also.
asawoszc said:
I've been on CM10.1 nightly 1231 for 3 days now and I can happily say that my battery is much better than before.
I've averaging 24-28 hours with 3 hours screen on with data only (WiFi disabled) and usually charging at around 10%. All Location Services (with exception of Google Maps/Latitude) are enabled and as well as Google Sync.
Some things I've noticed:
- When I flash a new ROM and restore my TiBu (flashable zip or regular restore) I find that my battery life is average at best.
- When I flash a new ROM and fresh install my apps from the Play Store my battery life is good to great.
- Third party kernels can sometimes be wonky on this phone. I haven't tried Faux or Franco kernel since flashing 1231 because I've been getting great performance on CM kernel.
- When my kernel CPU is set to "ondemand" the performance is average at best. Changing it to "interactive" has helped improve my battery life... with no other kernel tweaks involved.
Apps like Facebook Messenger seem to cause issues with my battery life also. When I was on CM10.1 nightly 1223 I had FB Msgr installed and my averages were 12-14 hours off battery. So by eliminating a few apps on fresh ROM installs I've been able to see the different effects they've had on my battery life.
So from my points above are also some of my takeaways. Try a fresh install and watch what apps you install. Try a few different kernel governors (esp if you're on a custom ROM). You can improve performance by trial and error!
Good luck.
EDIT: zephiK's points above are also valid and I can confirm they've helped my battery life also.
Click to expand...
Click to collapse
I agree 100% with Facebook. The facebook app sucks your battery life HARD, especially if you plan to have it refreshing intervals. The app continues to request GPS location, so therefore because of that I disable the GPS on my phone completely (its that bug where if u have GPS globally on your phone you see it on the top left of your screen, and it doesnt go away). I leave FB all notifications off and manually sync it by pulling up on news feed. It's either that or check FB via mobile webpage.
Another thing I forgot is your refresh intervals. Make sure your apps don't have it on like syncing every 5/10/15/30/45/60 minutes. Set it to a couple hours more. using a twitter app? instead of having it sync in the background, just manually do it so you get all the missing tweets all at once. No reason to have it sync in the background randomly.
+1 on interactive. on Franco kernel it uses Interactive as it's default governor and it includes a lot of the latest interactive patches that really help out. It also includes qualcomm fixes with msic (not 100% but its better than stock), and newer drivers that will most likely be included in the next OTA.
Thank you for the replies everyone. In regards to all of the fixes you've suggested, I've tried all of them in the past week or two based on hours and hours of reading. This problem even exists on a freshly installed ROM with the bare minimum apps.
Now that I think about it, I wonder if there may be a problem with the radio in my phone. I live on a farm with an AT&T tower, yet I'm only getting "ok" signal, when I should be getting perfect signal. Called Google and just ordered my RMA, seeing as this battery problem has persisted from the day I first loaded up stock 4.2.1 on the phone upon receiving it.
If you constantly have a low signal, that will drain your battery a lot, because it has to boost the signal and that needs a lot more power.
Sent from my Nexus 4 using xda premium
nosenuggets45 said:
Now that I think about it, I wonder if there may be a problem with the radio in my phone. I live on a farm with an AT&T tower, yet I'm only getting "ok" signal, when I should be getting perfect signal.
Click to expand...
Click to collapse
This would have been useful in your original post. Obviously "worse" signal is going to cause more drain on your battery. Hopefully it's just a flaky radio for you but if the replacement has the same issues then it's something else and you should keep at it until you figure it out! That's half the fun with these phones.
My only concern was that he said android os was up there, so that means he has a app preventing his phone from sleeping.
personally i wouldnt take a RMA on poor battery life but as a result due to signal.... but yeah signal does play a huge factor in your battery life
I've had my N4 since the day it was released and the battery has been generally acceptable.....until I upgraded to 4.3 (stock, rooted).
BetterBatteryStats is indicating the suspend_backoff wakelock is rampant. WakelockDetector is showing I'm only getting 20% deep sleep on days I'm only lightly using my phone. On Android's Battery screen "Android OS" is listed as the top culprit, consuming 40% or more of the total battery.
Google/XDA searches indicate suspend_backoff is related to Chrome, but I'm convinced this is somehow a wifi connectivity problem as this wakelock ONLY happens when connected to my work wifi. On the weekends when not working my battery is fine and I don't see suspend_backoff. If I don't connect to my work wifi while at work suspend_backoff does not show up at all and I'm deep sleeping at 80%.
Unfortunately at work I don't have the capability of configuring/swapping wifi hardware/settings, so I'm limited to finding a solution on my end. Hopefully the solution isn't to have to sit on mobile data all day long instead of connecting to my work wifi.
Any suggestions?
hfuizo said:
I've had my N4 since the day it was released and the battery has been generally acceptable.....until I upgraded to 4.3 (stock, rooted).
BetterBatteryStats is indicating the suspend_backoff wakelock is rampant. WakelockDetector is showing I'm only getting 20% deep sleep on days I'm only lightly using my phone. On Android's Battery screen "Android OS" is listed as the top culprit, consuming 40% or more of the total battery.
Google/XDA searches indicate suspend_backoff is related to Chrome, but I'm convinced this is somehow a wifi connectivity problem as this wakelock ONLY happens when connected to my work wifi. On the weekends when not working my battery is fine and I don't see suspend_backoff. If I don't connect to my work wifi while at work suspend_backoff does not show up at all and I'm deep sleeping at 80%.
Unfortunately at work I don't have the capability of configuring/swapping wifi hardware/settings, so I'm limited to finding a solution on my end. Hopefully the solution isn't to have to sit on mobile data all day long instead of connecting to my work wifi.
Any suggestions?
Click to expand...
Click to collapse
In Settings, Wifi, Advanced Settings turn Network notification and Scanning always available off and see if it helps. Drainage can also be an issue when the Wifi signal is weak, but it can be Google Now! related among other things, Now! likes to give you fresh cards like traffic, news, nearby things and weather, turning Now! off entirely (voice search still works) could still be help. Also using other apps than Google. I know, hardly a real soluton but I replaced as many as I can.
No, wifi scanning is irrelevant since OP wants to use wifi.
What radio are you on OP? I'm assuming .84?
Yep, .84 radio, Google Now is disabled
Anybody?
rom kernel info? screenshots of the issue?
Back in the Galaxy S II days it was related to Google Chrome with the tilt scrolling. I always disable it though.
Sent from my Nexus 4 using Tapatalk
I am experiencing the same issue starting from yesterday, God knows why. The most common advice is to disable tilt-scrolling in Chrome but as far as I could see the Development Tools option has been removed from teh settings. Any other ideas?
could it be because you're using Touch Control for S2W or D2W?
Your work's wifi may have a combination of 2.4 and 5 GHz signals. I would get this wakelock if I allowed android to choose automatically which band to connect to, but if I forced either 2.4 or 5, the wakelock would let up.
Lookas a kernel bug, which has been fixed in teh latest Franco's release.
For a month or more I'm facing totally unexplainable battery drain.
As seen on the screens below, the phone is awake, but it is not detected anywhere - not by android nor by GSam. In any case the battery draws faster.
I have one observation tho - this happens after I make phone calls. Not every time, but once per 2,3 days.
Any ideas?
Spo0f said:
For a month or more I'm facing totally unexplainable battery drain.
As seen on the screens below, the phone is awake, but it is not detected anywhere - not by android nor by GSam. In any case the battery draws faster.
I have one observation tho - this happens after I make phone calls. Not every time, but once per 2,3 days.
Any ideas?
Click to expand...
Click to collapse
You have this problem
http://forum.xda-developers.com/note-4/general/explanation-horrible-note-4-battery-t3004274
I'm pretty sure that I don't have this issue. Yes, the percentage in GSam maybe high, but I don't believe this reflects what is happening.
First of all - I don't have bad battery life. Usually my over night drain is less than 1%/1h.
Second - the issue appears sporadically.
Third - in the provided thread I don't see the issue appearing in stock battery monitor, while mine appear.
At last - my battery drains faster only while the issue is present and before I restart. After that it is back to normal ...
@Spo0f
Just some suggestions maybe you're using 3g I always have that turned off and switch it on when I use it my guess is that some apps are causing your drain after a call maybe like you said if you're not fimiliar with greenify I suggest you use it to stop all those apps and system apps also uninstall all those bloatware you don't need or at least freeze them if you don't mind lower the resolution to 1080p with nomone app use power save or disable dvfs and use an app to lower and raise the CPU to save juice when not needed....
Thanks for the suggestions, but as I said - this problem appear sporadically - home when using WiFi as well as outside when using 3G.
All of the rest is done - I'm no newby
Spo0f said:
Thanks for the suggestions, but as I said - this problem appear sporadically - home when using WiFi as well as outside when using 3G.
All of the rest is done - I'm no newby
Click to expand...
Click to collapse
Oh sorry mate well I don't use much 3g so I can't help you there but if you're having drainage when you're using WiFi in general then maybe you should reconsider investigating the post above with the link I don't have so much drainage on connectivity with 3g or WiFi....viewing the pics you uploaded it seems suspicious.... Maybe an app? I don't know...
Use wakelock detector
Spo0f said:
I'm pretty sure that I don't have this issue. Yes, the percentage in GSam maybe high, but I don't believe this reflects what is happening.
First of all - I don't have bad battery life. Usually my over night drain is less than 1%/1h.
Second - the issue appears sporadically.
Third - in the provided thread I don't see the issue appearing in stock battery monitor, while mine appear.
At last - my battery drains faster only while the issue is present and before I restart. After that it is back to normal ...
Click to expand...
Click to collapse
My overnight drain was also very low, but that was because the faulty device on the network was asleep at night too (my desktop).
If you're not rooted, use the PC version of Wakelock Detector at the end of your day and post screenshots of your highest drainers for the various categories. In my case, the device was being woken up by something on the network and it showed.
Bear in mind that actively downloading something in the time period will also raise wifi power used but more stats will help.
The fact that you're still experiencing a lot of drain even when outside suggests it might be a rogue app
One phone call today and after it the phone stayed awake.
Because I had issue with the PC WLD the screen shots are from 11 minutes after one of the disconnects. The device was awake all of them.
Spo0f said:
One phone call today and after it the phone stayed awake.
Because I had issue with the PC WLD the screen shots are from 11 minutes after one of the disconnects. The device was awake all of them.
Click to expand...
Click to collapse
I also checked out my battery behaviour this night and was very disappointed. Although my phone was in flight mode and every peripherals and services shut down, today morning my phone was crying for energy. So I made a quick investigation in my power diagram and found out, that "Android OS" requested a wakelock during the whole power-on time. So I installed "CPU Spy" to check in which states the phone was really over the whole charging period. I couldn't believe my eyes. Although the kernel should do it's job good, cause most of the CPU times are in lower freqeuncy states, the deep sleep mode was never activated.
Therefore I installed an app called "Wakelock Detector" to check out which apps could cause that. I found out, that S Health had a big amount of wakelocks and also active-time, so the first thing was to disable S Health. After some minutes I checked back, but nevertheless still no deep sleep time in "CPU Spy".
So I searched around and found another one arguing about the wakelocks and that they could be the products of some programming issues concerning WiFi. The should be gone, after turning off WiFi and rebooting yout phone. And it seems that he was right. I waited some time and hooray, "CPU Spy" listed the phone state "Deep Sleep" the first time as an active state and also with the major active-time. So at least that was some step ahead. (I have to remark, that S Health was already unfrozen at this time, so S Health should not be responsible in any way.)
The next step was to reactivate WiFi, leave it on and set the phone on standby. After some time I checked back again the phone showed even more deep sleep time. So that was an improvement. I reactivated everything and waited some time... Deep Sleep all over the time. Can't figure out for now, if it was S Health, WiFi, or anything else that caused the wakelock for sure. At least the reboot helped. I'll check that out on a long-term test, maybe I get some further conclusions.