I tried 4 different builds today. formatted my sd card and ran the files. when i get to the lockscreen my phone vibrates and than turns itself off. What am i doing wrong. I tried different roms and radios and its the same result.
it happened to me when i used the extended battery. If you are then that's the cause of your problem.
I have the same issue when connected to my car charger. All Froyo roms seem to have this problem. Weird behaviour, still looking for a solution.
HOw Do I identify it it is a stock battery or extended battery?
what's the diff between these 2?
the extended battery is very thick... the one i have is the official HTC one which is not supported by any kernels currently. The phone shuts off after boot because the battery temp. sensor readings is too high (which in reality is not).
Is that manufactured by HTC or some chinese company?
So android builds wont work with chinese batteries? im starting from scratch and seeing if i can catch the problem
It appears to be an overheating problem, even though my battery temperature is not getting higher than 36 degrees when it crashes.
This issue is not specifically related to Chinese batteries. I have the same problem when connected to my car charger or USB charger and run Google Maps for a while or Daily Voyager (camcorder app). Without a charger, and thus less heat, all works fine.
I tried all radios and still the problems persists. Now I'm going back to MCR r3.1 too see if that solves it. If not, it might be a hardware issue on the board.
EDIT 1: Problem also there in MCR r3.1 (Android 2.1 / Eclair). Further investigating...
EDIT 2: It appears to be an issue with GPS while the device is charging. Whenever I have GPS on and in use by i.e. Google Maps/Navigation or another app like DailyRoads Voyager, it will crash a few minutes later (sometimes within a minute). When I keep GPS disabled there is no problem at all.
Can anyone confirm my experience?
Try starting "clrcad.exe"
Solved the same problem by starting "clrcad.exe" before "haret.exe"
[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
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
My Motorola Defy MB525 is experiencing strange battery drains. It usually drains itself regardless of usage or power state. Even in a shut down state, the battery still continues to discharge. The strangest of all is that after each charge I'm able to use the device for about 36 - 40 hours, regardless of none, low, mild or heavy usage. For about 2 years, the battery lasted around 3 - 7 days.
At first I though, it was the battery. However, after I've purchased a new original Motorola battery, the issue still persists.
In addition, the first signs of this issue arose right after a CM11 change from the stock Android 2.2.2 and continued even after I've reinstalled the Android available .SRT file over RDS Lite for the 2.2.2 version.
I've tried different suggestions and tutorials (for example - CPU Deep Sleep, WiFi power management, Baseband Change, etc.) available on the forum, but without any use.
Thus, my only question :
Even tough the device works without any major glitches, as expected from such a device. Does the above mentioned issue relate to a Motherboard or Power Management/State Chip failure?
Btw...I've took the device apart to check if there are any signs of shorted elements or short-outs. Sadly, nothing of sort.
Any help and/or suggestion would be appreciated.
Hi, maybe try another CM11 nightly or another custom ROM to see if the same problem persists?
this [http://forum.xda-developers.com/showthread.php?t=1778492 thread] goes in-deep on battery problems, but, knowing a lot about electronics, I think in your case is just that inside the phone, there is a small switching-mode power supply, and it have a (fairly) large capacitor that can leak some current. When capacitors age they became more of a resistor... and that's why most of modern electronics break up. I would blame hardware in this case.