Hi guys,
I have one of the early CM9 Nightlies installed on my note.
Now, I have always had the issue of a battery drain where the battery would only last less than 10 hours after a full charge, despite having very minimal usage. I have tried resetting the battery stats and calibrating the battery again, but it does not help the situation.
Lately, I have also noticed that despite the phone not being plugged into a power source, the phone reports that it is still charging. Ultimately, this prevents the phone from going into Deep Sleep. I used CPU spy to check, and it seems that the phone never enters deep sleep. I have tried pulling out the battery which removes the 'always charging' issue and allows the phone to enter deep sleep. However, as soon as I plugged in a power source and remove it, it comes back.
I have a feeling that this is the cause of my battery drain and was wondering how to fix the 'always charging' problem.
Any help is appreciated
Try cleaning your USB port
If it does not log in deep sleep then:
1. activate the flight mode (ICS settings \ Other \ offline mode)
2. turn off the notes
3. remove the battery for 10 seconds and return it
4. turn on your notes
5. expect everything to be loaded
6. remove the flight mode
7. occurs with Cpu spy if the cpu enters DeepSleep . When there's nothing to do, the CPU should go into "deep sleep" state, which means basically stopped, so it consumes very little power. Some programs can name this transition to deep sleep impossible, so the CPU remains at 200 MHz and drains the battery more than it should.
This happens for example if you are charging the phone and disconnect it from the cable while the screen is off. While charging the CPU is at 200 MHz all the time, and when you disconnect it should go into deep sleep if you're not using the phone, but this does not happen and it keeps running at 200 MHz.
Cause. Corrupt skin for the "Super clock" in Beutiful widgets app.
Solution. Use other skin
From mikhan Cause: process usbunmounter or smth like this after using usb flash drives via microusb host adapter Solution: kill the task or just reboot
From vcespon Cause: USB cable (Charging or connected to PC) unplugged while Screen off Solution 1: Reconnect USB cable and unplug with Screen ON Solution 2: Reboot phone
From handfish Cause: DirectoryBind Solution: Uninstall App
Hi guys,
If I restart the phone, the always charging problem is removed. However, at times, the always charging problem would come back and then randomly disappear.
Any ideas?
j03uen said:
Hi guys,
If I restart the phone, the always charging problem is removed. However, at times, the always charging problem would come back and then randomly disappear.
Any ideas?
Click to expand...
Click to collapse
It is a known issue with a kernel wakelock called l2_hsic search for it on question xda forum. It is a radio or a USB running system process. How it is triggered we don't know, hope Samsung devs will find it and fix it. To reproduce it try Tunein from app store, when you are listening some radio the process l2_hsic is on the wakelocks the same time with the tunein but it disappears after the use of it.
Rebooting the phone always helps.
Hope it helped you a bit. Even it leaves it unclear!
Sent from my GT-N7000 using Tapatalk 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In my case I fixed it by running a small file on the battery contacts on the device (very carefully) and on the battery. They seem pretty susceptible to moisture.
My battery was showing Over Voltage and as if the USB charger was connected when in fact it wasn't.
The above fixed it for me!
Cheers!
Rayan
Related
Does anyone have an idea as to what happened to my battery here? I'm thinking faulty battery unless someone has seen this before?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my GT-N7000 using xda app-developers app
mee too
Does this happen often???
Cuz im facing the similar problem but for me .....gigantic battery drops occur after i resart the phone.......may be we should change our KERNEL. I heard hydracore is gr8
I wouldnt say its your battery, If you look at the blue lines below you will see that there is a big gap when screen is off, Yet the phone is waking up many many times whilst the screen is off.
This says to me that there is an app causing your phone to not enter deep sleep. Your best bet would be to install Better Battery Stats (free on XDA, Paid on Play store) and/or Watchdog lite.
this will tell you which apps and proccesses are using more power than needed. Then you can take action from there.
Battery drain is an issue for most android users, and has millions of possible causes, so elimination is key to finding the culprit.
ofcourse.. this is happening because of wakelocks... power off the phone. remove the battery for a minute and pack it up again boot into recovery.. wipe battery stats and check again
aneeshprasobhan said:
Does this happen often???
Cuz im facing the similar problem but for me .....gigantic battery drops occur after i resart the phone.......may be we should change our KERNEL. I heard hydracore is gr8
Click to expand...
Click to collapse
It's only happened this once. And I think the vertical line suggests it was during a reboot?
I've dealt with wakelocks before but never seen this. I'll have a look with betterbatterystats to see for those wake events.
nokiamodeln91 said:
ofcourse.. this is happening because of wakelocks... power off the phone. remove the battery for a minute and pack it up again boot into recovery.. wipe battery stats and check again
Click to expand...
Click to collapse
I'll give this a go.
This occured to me on XXLSA Jelly bean, after researching, I found it is due to media scanner running for long time
I used Rescan media root app from play store to disable media scanner and this didn't happen again
It is worth noting that this problem would NEVER happen in CM-based ROMs - Huge battery life!
Hmm I've been running CM10 since the nightlies first appeared and tbh, whether on original battery or gold battery or my extended battery, I always get drops offs (maybe only 5 per cent) on any reboot
Sent from my GT-N7000 using xda app-developers app
I noticed battery drop after I started bluetooth my music through my car stereo.
Apparently it's a bug in a file called "media server" in Android that causes that.
The short fix is, after I stream music, if I'm not going to stream for a while, I reboot
the phone. Killing the service for media server won't stop it, you have to reboot.
I ran a battery program that showed overnight, the media server wasn't going to
sleep, kept wakelocking. After rebooting, the battery only lost 2-3% overnight,
and before, it was losing 10-20% overnight. Might be worth looking into.
full decharge (1bar,not really full) and fullbrechargr cycles might make it better. A sudden drop like this screams battery replacement. If in warrantee period get it replaced.
Sent from my GT-N7000 using Tapatalk 2
I am currently using Marvel 11, with interactive/cfq. The phone constantly is at 300mhz, and doesn't sleep. I installed Wakelock Detector app and it showed me these Wakelocks. How do I get rid of these? Battery life with my phone is terrible.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The second one is x359!
See if this help: http://forum.xda-developers.com/showpost.php?p=40825012&postcount=9
dcop7 said:
See if this help: http://forum.xda-developers.com/showpost.php?p=40825012&postcount=9
Click to expand...
Click to collapse
Thanks for the reply, but I did everything on the list, except mobile data is on. But that didn't prevent the phone from going to sleep in boype's cm7. Any other ideas?
None of those wakelocks would cause what you said in the first post, the largest is only 31 seconds.
First, make sure your cpu is scaling properly, use cpuspy, that will tell you how much time is spent in each state.
Use a diferent app for changing govenor, i've noticed strange behaviour occasionally. Reboot phone, change govenor, reset stats in cpuspy, use for a few minutes, put phone to sleep for a few minutes, then check stats in cpuspy (you may need to refresh).
Correct behaviour is most time spent at 300, then 1000. 600 and 800 should be next to nothing. Sleep should be for virtually all the time the phone is off.
If problem persists, post logs from betterbatterystats.
jason600 said:
None of those wakelocks would cause what you said in the first post, the largest is only 31 seconds.
First, make sure your cpu is scaling properly, use cpuspy, that will tell you how much time is spent in each state.
Use a diferent app for changing govenor, i've noticed strange behaviour occasionally. Reboot phone, change govenor, reset stats in cpuspy, use for a few minutes, put phone to sleep for a few minutes, then check stats in cpuspy (you may need to refresh).
Correct behaviour is most time spent at 300, then 1000. 600 and 800 should be next to nothing. Sleep should be for virtually all the time the phone is off.
If problem persists, post logs from betterbatterystats.
Click to expand...
Click to collapse
What about the x356? Doesn't matter? Also, I already use cpu spy, which tells me that my phone is mostly on 300 mhz, not on sleep when the screen is off. Lemme try using Another app to change governor...Also, I tried what you said, if the screen is off for 10 mins, 6 mins is on 300 mhz. I currently use Wakelock detector, but I'll try using batterbatterystats.
The cpu is scaling properly, also sleeping properly. You have no major wakelocks (ignore wakelocks of seconds, worry about wakelocks of hours). The screenshots you posted show only 20 minutes after charging, leave all day then check wakelocks again.
I installed betterbatterystats, restarted phone, plugged my phone in for charging overnight. I didn't know that betterbatterystats resets data when plugged in, but overnight, with no usage, look:
Maybe it's a kernel issue? Should I try changing the kernel? I'm on N00by's kernel.
ykumar00 said:
Maybe it's a kernel issue? Should I try changing the kernel? I'm on N00by's kernel.
Click to expand...
Click to collapse
In betterybatterstats it shows kernel wakelocks and partial wakelocks. In your screenshot you've got about 8 hours of wakelocks, which is serious. Partial wakelocks are apps and are the usual reason for large wakelocks, remove the app thats causing the problem. If its a kernel wakelock, you can try a diferent kernel, though I doubt thats the problem because if noobys kernel was the cause, everyone using it would be getting the same problem.
Froze Google maps, restarted, left idle for ~an hour. Suddenly seems to be fine.
Let's see how it behaves overnight. Thanks guys
I bought this phone 2 weeks ago, and soon rooted it and installed May Update via Fastboot.
While I'm generally happy with this phone, there's serious battery drain issue due to a particular wakelock called IPCRTR_lpass_rx. While there are others like RILJ etc. they are still not that severe.
I've tried Wifi on + data off, both on, both off, Only Sim 1 activated, both sims activated.
After this, I even put my mobile on flight mode for a night and there was around 20% drain overnight. In my previous mobile Redmi 3S, there would hardly be 1% drain over night on flight mode and 3-4% if Wifi was on.
I was tracking these using BetterBatteryStats, however, while tracing the root cause, i even uninstalled BBS and used the system in-built bug report and analyzed it on battery historian to track the wakelocks and all.
Then came June update. I clean flashed through the unofficial fastboot, formatted data partition as well so as to leave no stone unturned. Again the same situation. A lot of battery drain.
Here are some reports -
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please see the attached graph.
1. At around 6.30 PM (UTC) (graph times are in UTC) (12 AM IST) I kept my phone on flight mode at 50% battery and slept for 8 hours.
2. I woke up around 3.30 AM UTC (in the graph) (i.e, 9 AM IST) and checked my battery percentage. It was down to 30% from 50%.
3. Checked the main cause of wakeups, not much in Userspace wakelocks but massive amounts of kernel wakelocks from IPCRTR_lpass_rx. For the duration of this graph, there were over a million (2.3 x 10^6) wakelocks from this service, causing wakelocks every 2-3 seconds.
4. Even though phone went into full doze after some time, this wakelock continued.
Any suggestions on how to go about solving this?
Running June update, Rooted + cam2api enabled using Magisk patched boot img
Its been a month since i moved to a custom ROM, currently on Havoc OS 2.7
The severety of the bug is lesser than stock ROM, however, still quite random and causes battery drain and keeps CPU awake!
Check the wake sources, IPCRTR_lpass_rx is the number one wakelock with 10^6 wakelocks!! Thats way too huge in my opinion, and keeps my CPU awake.
At least i can prevent the wakelock to a large extent by turning off location, wifi (or both) in Havoc. It also doesn't occur during flight mode, or if it does sometimes, a restart usually solves the problem for me.
Ideally, even if i keep wifi on, battery should not drain more than 4-5% overnight (which was the case in all of my previous phones, and in my friends' phones other than Mi A2).
This is december now. And so far, the only problem i have with this device is the poor battery, intensified with software problems, poor modem and LPASS!!!
Its kind of frustrating for me.
Please see the screenshots and the attached bugreport.
rahulmanpur said:
This is december now. And so far, the only problem i have with this device is the poor battery, intensified with software problems, poor modem and LPASS!!!
Its kind of frustrating for me.
Please see the screenshots and the attached bugreport.
Click to expand...
Click to collapse
Well, i'm very satisfied with battery on this device. It could be better, but it's only 3000mah.
This ss was taken yesterday.
rahulmanpur said:
At least i can prevent the wakelock to a large extent by turning off location, wifi (or both) in Havoc. It also doesn't occur during flight mode, or if it does sometimes, a restart usually solves the problem for me.
Ideally, even if i keep wifi on, battery should not drain more than 4-5% overnight (which was the case in all of my previous phones, and in my friends' phones other than Mi A2).
Click to expand...
Click to collapse
Could you find what this Lpass wakelock mean? It occured 3720k times in 5 hours for me.
Unreal!
Hi everyone,
I'm coming to you with a random problem which I can't reproduce. Over the 2 past years, I had it about 2 times but I had to wake up at 5 am.....
Here's the explanation :
I'm putting my phone on charge, the alarm (The app AMDroid) is supposed to ring at 5 am but sometimes it doesn't. When i'm finally waking up, I'm finding the phone blocked. Black screen, no sound, no response to physical buttons (volume, power) or fingerprints. I'm forced to reboot it with the volume up + power off keys.
I really don't understand from where comes the problem. I already had when I was using the regular sony alarm app and as I said above I can't reproduce the bug which is kind of embarassing when I have to get up early...
I hope you'll be able to help me,
Thanks !
Bump !
I just had this happen to me this morning, and solved it with the same procedure.
I noticed this morning when I woke up that the device was extremely hot, potentially a temperature failsafe kicked in?
If that were the case, I have no idea what would be causing it. Presumably something has the CPU pegged at max load.
I may try to dig for logs, but I'm not familiar with how to do this on Android.
Hi Telomeres, thanks for your comment !
Two quick questions :
- do you have the fingerprint unlock feature enabled ? (do you have at least one fingerprint recorded)
- si you have the battery maintenance (i don't know the exact name in English) enabled ?
I'm trying to pinpoint the problem, so far i have those only two options..
Skwiizz said:
Hi Telomeres, thanks for your comment !
Two quick questions :
- do you have the fingerprint unlock feature enabled ? (do you have at least one fingerprint recorded)
- si you have the battery maintenance (i don't know the exact name in English) enabled ?
I'm trying to pinpoint the problem, so far i have those only two options..
Click to expand...
Click to collapse
I do have the fingerprint unlock enabled, despite being the US. My guess was that I was accidentally shipped an international version somehow? I did not go through any measures to enable this on my own.
If you're talking about "battery care" where the device slows down your charge rate to increase longevity, yes I do have that enabled.
Your information about the battery overheating is making me think about the battery care. I don't have regular schedules so this option activates kinda randomly just like the problem pops out.
I'm asking you that about the fingerprint because i saw a thread where someone said the fingerprint sensor was at fault.
Unfortunatly for us, we both have the same settings hahaha
Actually, on checking my settings Battery Care was disabled and I believe that setting persists through reboots. However, I did not have my phone charging overnight. I don't recall what percent my battery level was before bed.
Damn. So close to find a clue !
Happened again overnight last night.
I had battery care enabled this time.
I really don't understand from where comes the problem ; we both have a totally different setup and ways of use/charge our phones :/
I'm having the same issue...... I'll see if I can get get some logs..... I do use battery care and stock alarm..... Twice in the month of October ive nearly been late for work because my phone locks up, charge light remains amber but is full (no excessive heat) and I have to force reboot
I had the same kind of lockup like 5 times now in the last two month. Last lockup was tonight with the September security update.
This happened to my phone twice recently, but my phone was NOT charging.
Last time it happened, I went to bed before midnight, my phone was at about 70% battery, so I decided not to plug it in. I put the phone on a shelf beside my bed and fell asleep.
When I woke up in the morning (I don't use phone alarm, rely on my smartwatch for that), the phone was unresponsive, black screen, needed to long press VolUp + Power buttons to reset it. I'm not sure when I plugged it in - before or after the reset, but the battery was basically flat. I took a screenshot of the battery chart that morning, which seems to tell that the phone has been dead for most of the night. As you can see in the screenshot, the battery line is natural until after midnight and then it's just a straight flat line until the morning. This leads me to think maybe it's a battery problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Overnight, my phone discharged from around 40% to zero and turned off while it was in airplane mode. Confirmed aiplane mode was still active after charging up and turning back on. Samsung Galaxy S21 Ultra.
Battery info showed the app "Google" seemed to be to blame. Is there a way to diagnose what aspect of Google was messed up and confused to cause this excessive battery use in airplane mode? Or how to diagnose what other app I was using that may have been buggy and interacted with "Google" to cause this nonsensical battery usage when airplane mode was turned on?
Here is the chart showing the constant smooth line from when I went to bed and turned on airplane mode, leading to zero battery:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Take out the trash; any social media apps. Amazon and Netflix are two I'd never allow to install or run.
Google backup Transport and any apps storing in the cloud. It shouldn't be necessary to put into airplane mode at night; use do not disturb.
Try temporarily disabling Google play Services and see if that gets it. Gmail, Playstore and Google backup Transport are dependencies of it.
I normally keep it disabled unless I need it; nets me 1-2% @hr better SOT.
How do any of those apps use so much battery when in airplane mode?
I'm just confused how the phone itself is dissipating power without using the radios....?
KingFatty said:
How do any of those apps use so much battery when in airplane mode?
I'm just confused how the phone itself is dissipating power without using the radios....?
Click to expand...
Click to collapse
Constant polling trying to connect and complete a task.
blackhawk said:
Constant polling trying to connect and complete a task.
Click to expand...
Click to collapse
Why does the phone attribute their power consumption to the app "Google"?
Why does Google consume all the power?
Update: after clearing cache for entire phone, the problem no longer occurs.
Overnight, the battery percentage drops 2% when I turn on airplane mode.
The app "Google" no longer tops the list of battery offenders.
But I'm still curious why the app Google would consume power?
KingFatty said:
Update: after clearing cache for entire phone, the problem no longer occurs.
Overnight, the battery percentage drops 2% when I turn on airplane mode.
The app "Google" no longer tops the list of battery offenders.
But I'm still curious why the app Google would consume power?
Click to expand...
Click to collapse
Data conflict.
You shouldn't need to turn off data and usage at night by Google should be near zero if optimized.
As is Google is still an issue on that device.
Try temporarily disabling Google play Services at night with airplane mode off.