I have searched on here for the last 20 minutes so I hope I didn't just miss something.
Anyways, onto the problem I am having... I'm currently running UnNamed 1.3.1 and last night before I went to sleep the phone got really warm. I went to place it on the night stand and missed resulting in the phone taking a minor fall ~2ft. Everything was in working order so I placed in back on the stand and went to sleep.
At some point during the night the phone died on me causing me to miss work today. Now I'm trying to charge it but all it is doing is showing the depleted battery icon for about 2 seconds and then going to a black screen and repeating. Have any of you guys heard of this issue? Is it just a defunct battery?
Thanks for the help in advance.
jcarson112 said:
I have searched on here for the last 20 minutes so I hope I didn't just miss something.
Anyways, onto the problem I am having... I'm currently running UnNamed 1.3.1 and last night before I went to sleep the phone got really warm. I went to place it on the night stand and missed resulting in the phone taking a minor fall ~2ft. Everything was in working order so I placed in back on the stand and went to sleep.
At some point during the night the phone died on me causing me to miss work today. Now I'm trying to charge it but all it is doing is showing the depleted battery icon for about 2 seconds and then going to a black screen and repeating. Have any of you guys heard of this issue? Is it just a defunct battery?
Thanks for the help in advance.
Click to expand...
Click to collapse
This sometimes happens with a severely depleted battery - after a bunch of cycles like that it SHOULD eventually stay on I think.
Otherwise you may need to give the battery just a little "juice" with a standalone charger.
Thanks I'll keep trying, was having a minor crisis when I woke up 2 hours late to work today.
I had this same issue when my battery died severely. Woke up with the phone cycling, like you mentioned and it was extremely warm.
The problem you are having is that UnNamed is running a kernal that automatically boots up the phone if it is off when you plug it in. This, combined with the fact that android turns your phone off automatically when the battery is too low, is putting you into a battery bootloop.
I just went into the AT&T store, and they swapped out my battery for free. Just don't let your phone get too low before charging it.
Hope this helps.
It's finally started taking charge thank goodness.
Anyone gave an idea as to why my battery tanked so hard. I exited out of all apps and had it plugged in through the night.
jcarson112 said:
It's finally started taking charge thank goodness.
Anyone gave an idea as to why my battery tanked so hard. I exited out of all apps and had it plugged in through the night.
Click to expand...
Click to collapse
Rage from being dropped.
Hard to say. Unless you catch it as it's draining like crazy, a logcat or bbs will only comment on how it's currently running.
Sent from my páhhōniē
Lol i just put it into download mode and charged it haha. I made it stop rebooting......
Sent from my SAMSUNG-SGH-I777 using xda premium
Can't charge battery
o i think i am having the same issue. i dont have any other charging method. it is so dead i can't even get it to get into download mode.... any ideas. PLEASE HELP
Did you put a different kernel on it? I know certain kernels cause the phone to lock into 1200MHz while charging. At that rate the phone would die even plugged in, like you saw on that battery graph. Zedomax kernel did that to my phone. None of entropy512's did that to me, but if you used a different kernel than what gtg packed it with that might be it.
Look for BetterBatteryStats, it will tell you what apps are preventing your phone from going into deep sleep. If its an app causing that issue BBS will tell you which one. It costs money in the android market, but there is free version for xda members in the android app forum.
Related
Me and my wife have the Eris. no phones were rooted.
My phone was manually updated to 2.1 and my wifes was OTA.
before i go to bed i turn off the data signal and clear out all programs running with task killer. it was 60% charged, come to wake up in the morning and find that the battery fully discharged and had to plug it in the mains to switch it on. a few days after my wifes phone is doing the same.
would like some ideas from you guys on some of the reasons this may be happening. would love to provide you with more information... just tell me what and where i can get it from.
Thanks.
mee too
the same thing happens to me but in a different manner. This started about 3 days ago as far as i could notice. While the phone is in my pocket it would randomly get really hot and most of my battery would be drained. This usually happens in the middle of the day. I have to shut the phone down and restart it and then I would not notice the problem for rest of the day. I have 2.1 V3 leak installed on my phone. any ideas as why this is happening?
vmprlrd said:
the same thing happens to me but in a different manner. This started about 3 days ago as far as i could notice. While the phone is in my pocket it would randomly get really hot and most of my battery would be drained. This usually happens in the middle of the day. I have to shut the phone down and restart it and then I would not notice the problem for rest of the day. I have 2.1 V3 leak installed on my phone. any ideas as why this is happening?
Click to expand...
Click to collapse
Wow...that is strangely similar to what is happening to mine. It just started a few days ago as well.
I got up this morning with a fully charged phone (it takes all of 10 hours to completely charge, if it does fully at all) and after looking at facebook and reading a few news articles for about 2 hours, my phone was at approx. 60%.
This happens every day now and I end up chasing a charge all days between the ac adapter and my car charger. I'm getting sick of carrying my charger with me all day but I have to.
Mine is also getting hot. I first noticed this Tuesday as I was using Tapatalk while the phone was charging via wall charger and it got hot and just died. I had to wait about 30 minutes for it to cool and then it would boot up.
Like you said, this just started recently and I am also running Leak v3. I have removed all widgets and taken off everything I don't absolutely need off of the phone (apps, that is) but no change. Just as an example, I have had mine connected via usb to my work pc since 5 pm (it's now 1:20 am) and it is still not completely charged.
It gets to about 85-90% but will not close out to a full charge for hours. I just ordered a new battery today to see if I have just "overcharged" mine, so if that works I'm gonna get a premium (1750 mah) battery maybe and try that.
Very strange. I'd say within the past few days, my phone has had considerably worse battery life as well. Usually I'm pretty good about killing apps and there was one day where I forgot for most of the day.
I recharged it to full last night and have been killing apps and keeping an eye on it all day and it is still giving me poor results. I'm rooted and running a 2.1v3 ROM atm.
try this http://forum.xda-developers.com/showpost.php?p=6137989&postcount=23
or this
Long press power/end button. Turn Airplane mode ON. Press the power/end button to put your phone into sleep. Press power/end button to come out of sleep. Turn Airplane mode off.
The cell standby percentage will/should eventually go down to 0%.
or dont use task managers / killers. there is no use for it on the phone. android has a built in task killer that is really smart.
could be cell signal as well
issue solved
Hey guys, I solved the issue, i used the *#*#4636#*#* and in my settings it was trying to search for a GSM signal, so i changed it back to CDMA auto PRL
It was very strange it would do that but still its been running like a champ now, thanks everyone.
jbroderick said:
Hey guys, I solved the issue, i used the *#*#4636#*#* and in my settings it was trying to search for a GSM signal, so i changed it back to CDMA auto PRL
It was very strange it would do that but still its been running like a champ now, thanks everyone.
Click to expand...
Click to collapse
When I do this and look at the battery history, it says
Running 100%
Screen on 9%
Phone on .6%
and my battery level is at 58% currently. Mine is already set to CDMA/Auto PRL and my battery life within the last week or so has utterly SUCKED! I get up and unplug it at 3:30 am (fully charged) and go to my first job. By the time I get to my second job at around 10-10:15, I have to plug it in because it's very low. All I use it for at my first job is to check the time every once in a while. I dont play games on it, surf the web, etc. WHY should my battery be draining this fast when Im not using it!? Im seriously thinking about trading this POS in. Im so tired of this laggy, battery sucking phone!
I have the same problem. I turn on the mobile network only when I use it. ill turn on network with a full charge and check the news for maybe 5-10 minutes and my battery is down 10-15%. I haven't always had this problem. It started maybe a couple weeks ago. I'm using Android 2.1 leaked v3. I cent wait for my phone upgrade. This phone would be perfect for me if it wasn't for the HORRIBLE battery life.
-------------------------------------
Sent via the XDA Tapatalk App
xtremeskier97 said:
Mine is already set to CDMA/Auto PRL and my battery life within the last week or so has utterly SUCKED!
Click to expand...
Click to collapse
I thought the same thing because it said cdma/auto prl when I got to like step 2 but I hadn't pushed menu and gotten the force close which then brought up the screen that did have gsm listed instead.
Just make sure you go through all the steps listed there...
Just out of curiousity, which Facebook version do you have? You have an app keeping your phone awake 100% of the time which is why your battery is draining and the 2 latest versions of the Facebook app are known to do that. If it isn't that app, download Spare Parts from the market and use it to check what is using the most under Partial Wake usage, the app and the top using the most battery will be the culprit.
Hi all. I really don't know what causes my problem, so I'll just describe it:
Epilogue:
My Legend came with some Vodafone ROM so as soon as I got it I flashed 2-3 ROMs found on XDA (all in the same day, all were 2.2) before I settled for BlaY0's. Everything was working properly. After 3-4 months I decided to try a new ROM so I flashed a 2.3.3 with HTC Sense (http://forum.xda-developers.com/showthread.php?t=987251) - didn't like it much; then I tried a Cyanogen, also 2.3 - didn't like it either. So I flashed back the BlaY0 2.2. (also, in one day)
This is when my problem started.
Usually my battery would last for a day and a half. But every evening I connect it to the charger (at about 50%). In the morning the little light turned from orange to green and the battery indicator showed 100%. This was before! Now, I connect the charger in the evening but in the morning the light is still orange and the battery indicator shows something between 70% and 85% (I don't know if this is important, but most of the times is 85%). Usually it took 2-3 to fully charge the battery.
After a while, I noticed that if I reboot the phone in the morning, after the reboot the indicator shows 95-98%.
First thing I did was to wipe the battery stats (http://forum.xda-developers.com/showthread.php?t=765656) but either I did it wrong or that was not the problem because it did'n solve anything.
Then I noticed something else. When I go to SETTINGS>ABOUT PHONE>BATTERY I can see the UP TIME and the AWAKE TIME. I'm guessing that the up time is the total time since last reboot but the awake time I'm not sure; is it the time the display was on or it is more about CPU activity? Anyways, it seems that after I connect the charger, it thinks that it is awake because in the morning I can read about 8-9 h of awake time (during the day it reaches at about 1-2 h). So it appears that something consumes the power at a higher rate messing with the charging process. If so, why does the battery indicator heals after reboot?
Thinking that an app was causing the problem I eliminated some of them: Advanced Task Killer, Llama, Watchdog. The problem persisted...
Now I'm out of ideas...so if someone has some I'd be grateful. It's not that I need to reboot in the morning, it's the not knowing that's killing me!
Absolutly same issue here.
I remember seeing a solution somewhere in the forum. Try using search. I think there're many threads revolving around this issue.
Sent from my Legend using XDA App
elk2210 said:
Absolutly same issue here.
Click to expand...
Click to collapse
I know that it's selfish but I'm glad I'm not alone
@Asovse1: I did a search before posting but I'll keep digging if you say there is a solution somewhere. Tks!
marginean.m said:
I know that it's selfish but I'm glad I'm not alone
@Asovse1: I did a search before posting but I'll keep digging if you say there is a solution somewhere. Tks!
Click to expand...
Click to collapse
There was a huge thread on this in General.
http://forum.xda-developers.com/showthread.php?t=1151450&highlight=charge
Unfortunate, until an alternate solution is found, it seems that replacing a piece of the hardware is the only way. Which sucks. I'm sorry.
When flashing a new ROM or switching between primary and secondary batteries in my wallet, I always make sure I calibrate it so the system doesn't misinterpret predefined untrue values regarding the highs and lows of the battery.
Actually, with my second battery, it takes an hour to charge from 2-60, then another one for 61-76, then the whole night til 100. It's quite horrible. The stock HTC battery excels at charging, but I digress.
It seems like a counter-solution to me, but maybe a temporary fix for you: Have you tried investing in a really cheap, secondary battery, perhaps on eBay? I bought two for around 2 dollars each, on separate occasions. My first I'm still using now, in my wallet, switches each month. My other one I bought recently, and the first time it dipped to 30%, it completely shut off. Needless to say, I threw it away, it was horrible.
@Asovse1
I read the thread...to be honest I never thought it would be a hardware issue. Anyways, replacing the motherboard isn't really a fix.
I guess your solution (having spare batteries) is the only one feasible. This kinda sucks!
Solution (see last sentence)
I have two HTC Legend phones here that both have this same problem.
I have read elsewhere that some people got the HTC Legend fully charged by charging it normally, like overnight, then powering it down and charging once more until the light turns green. Some repeated this procedure twice, i.e. pulled the charging cable, then plugged it in again.
I just tried charging with the phone powered down and got it to 100%.
But I'm still not sure whether this is just snake oil, because the indicated figure may not actually show the true charge.
Addendum: As I now know, it is snake oil. As far as I can tell, the phone charges normally. Only the indicator underreads. It does not reach 100%, it goes down rapidly, the phone keeps operating for hours with the indicator showing 3% or less.
And here is the solution.
Latest SiyahKernel with stock rooted ICS 4.0.3.
Now, this has happened twice in the last week. I unplug the phone from my charger and place it under my pillow for the alarm to wake me up, and go to sleep. I disable both data and wifi so that twitter won't update and wake me up prematurely. Then, I oversleep about two hours, and what wakes me up is the phone that's EXTREMELY hot. The alarm doesn't go off and the battery is completely drained.
I have no idea what drained the battery and why the phone was that hot (I couldn't hold the phone for more than two seconds before I started experiencing pain). I've tried searching, but there were no topics like this one. So does anyone know how I can fix this?
~November
http://cow.neondragon.net/index.php/how-to-resolve-poor-battery-life-battery-issues-on-android
Thanks for the answer, but even after doing everything there I have the same problem.
A few days ago, I was able to "intercept" the process.
I had just used the phone, and put it away. Then after no more than ten minutes, I noticed it getting extremely hot. When I tried unlocking the screen, the phone had frozen, so I had to pull out the battery to turn it off. When I put the battery back in again and turned it on, the battery level was down from around 80% to around 60%. The battery graph showed like vertical drop, so it was clear that it had happened within those 10 minutes.
Is there really noone who has had this problem before?
November13 said:
Latest SiyahKernel with stock rooted ICS 4.0.3.
Now, this has happened twice in the last week. I unplug the phone from my charger and place it under my pillow for the alarm to wake me up, and go to sleep. I disable both data and wifi so that twitter won't update and wake me up prematurely. Then, I oversleep about two hours, and what wakes me up is the phone that's EXTREMELY hot. The alarm doesn't go off and the battery is completely drained.
I have no idea what drained the battery and why the phone was that hot (I couldn't hold the phone for more than two seconds before I started experiencing pain). I've tried searching, but there were no topics like this one. So does anyone know how I can fix this?
~November
Click to expand...
Click to collapse
Try N.E.A.K ICS kernel. I had some really good results with aokp rom. It's compatible with Samsung rom as well I think. Check it out
Sent from my GT-I9100 using Tapatalk 2 Beta-5
I'd be more worried about it setting my pillow alight
Steps.you could try:
- Wipe all data (Optional maybe an app conflicting with something)
- Update kernel or change rom to CM9 or any other stock
- If none of those work try an different battery
*I believe its an well wakelock had this when i was using siyah 3.1 Rc 1-5*
~Blizz™;
I had roughly the same problem. I did a full wipe and installed a custom from and changed the kernel... everything works perfect then. One of my friends finds taking his battery out every few days works best. Try both and see what results you get.
Sent from my GT-I9100 running ics resurrection v1.4 using xda app
I would have to guess that it's either the kernel or the battery calibration. Are you using a third party battery? I think with the original samsung batteries, this must not be as much of a problem (I have never owned an original samsung battery for my S2, sadly). I know that with my fake Chinese super-cheap "2150mah" battery, which somehow is small enough to fit in the original cover which makes me think it's more like 1350mah, I have gotten horrible battery drain problems for basically no reason. But, after following the thread where it was explained to charge to 100% and then take the battery out, wait three minutes, and put it back in, I've had the phone stay at 100% for over four hours, with wifi, syncing, and all that turned on.
I should mention that I sometimes also have had this problem where it seems to be charged, then for some reason it drops to 20%.
If your battery is third party, make sure you calibrate it. I've also noticed that the more roms I flash, the worse my battery life is, so I'm trying to resist the temptation of flashing something new every twenty minutes.
Good luck.
/proc/last_kmsg
Use it.
You could try downloading Better Battery Stats and hope to identify the wakelock or app that's draining the battery. If it's not either of those and you haven't always had an issue with it under your pillow, I'd say it's time to try a wipe and new rom and if the problem persists even after that...hardware problem.
Have you been able to leave it under the pillow previously? Part of me is wondering if the overheating itself is affecting the battery and causing it to degrade though I doubt it should happen so quickly and in such an odd fashion as you're experiencing.
After a bit more tinkering and testing, I'm almost 100% certain that it's the kernel, as it was the only thing "constant" in my testing. I reflashed over and over. I also think it has something to do with the wifi, since when wifi's off, my phone is fine and doesn't get touched by the described bug. So right now, I'm waiting for SiyahKernel 3.1 to be released while keeping wifi off.
On the changelog for RC6, it says that the "battery drain issue" is fixed, and on the changelog for 3.1, it says "new wifi drivers", so I'm assuming it'll be ok once the 3.1 is released. Thanks for all your replies and help.
November13 said:
After a bit more tinkering and testing, I'm almost 100% certain that it's the kernel, as it was the only thing "constant" in my testing. I reflashed over and over. I also think it has something to do with the wifi, since when wifi's off, my phone is fine and doesn't get touched by the described bug. So right now, I'm waiting for SiyahKernel 3.1 to be released while keeping wifi off.
On the changelog for RC6, it says that the "battery drain issue" is fixed, and on the changelog for 3.1, it says "new wifi drivers", so I'm assuming it'll be ok once the 3.1 is released. Thanks for all your replies and help.
Click to expand...
Click to collapse
I had best results with Siyah RC6. You could check results on my thread and use as reference if you want. Link on my. Sig.
Sent from my GT-I9100 using Tapatalk 2
Good afternoon everyone,
I didn't see another post on this topic for this device so I wanted to see if anyone knew what might be up. A few months ago, I installed the beta of CM7 on my Droid X2. It's been working great since then and I've been extremely pleased with the improvement over the stock build.
Over the past couple days though, I've been noticing that my battery reading has been incredibly erratic. An example last night had it go from fully charged to 4% in under two hours. When I plug it in, it charges at a normal pace up through around 25%, and then jumps to fully charged.
I installed a clean install of CM7 this morning and noticed the same issue persists. At first I thought maybe installing my new software drained it more than I realized, but it jumped from around 24 to 100% again while plugged into the wall charger.
I have several screen shots of the battery activity screen that I took when I noticed it acting odd. The one from this morning is attached below. If anyone could help me figure out what might be up, it'd be greatly appreciated. I wanted to start casually looking for a new phone, but not like this
Edit: I also have this one from just before I charged and just after the battery spiked downward.
Maybe you just need a new battery.
P.S. You talk on the phone a lot. lol
jsgraphicart said:
P.S. You talk on the phone a lot. lol
Click to expand...
Click to collapse
Heh, that's one of the things that has been acting up recently. That 65% is only a 7 minute call.
Well if its a software issue, an SBF should clean it up. And if it doesnt, Id say its the physical battery. But I havent been on CM7 in a long time. I forget what issues it had. I dont think this was one of them though.
jsgraphicart said:
Well if its a software issue, an SBF should clean it up. And if it doesnt, Id say its the physical battery. But I havent been on CM7 in a long time. I forget what issues it had. I dont think this was one of them though.
Click to expand...
Click to collapse
I'll give a new battery a try then. I just wanted to check in before shelling out some money for a non-fix. I installed the 2.3.4 SBF this morning before giving 7 a reinstall and the problem seemed to reappear almost immediately.
Thanks for your help.
Try rebooting into recovery then go to advanced>wipe battery stats. Then wait for your battery to completely die before recharging it
Hey guys.
It seems like almost everyone with battery drain issues has Android OS at the top of their battery stats.
I just want to share my experiences with this particular Bug.
Maybe it will help anyone. Please share if it also helped with your problem.
I had the Android OS bug since I dropped my phone a few months ago and had the screen replaced. The guy who replaced it (official Vodafone shop employee) said that they didn't just replace the screen and that something else was also damaged (they didn't say what) so they also replaced the rest. Well, that's when the Android OS problems started. I tried many ROMs and many Kernels. Sometimes the problem went away for an hour or so, but it always came back.
Then I finally decided to use BetterBatteryStats two days ago (I really should have done this earlier, I know...). I came to the conclusion that I had some sort of the well-known "fuel_alerted" bug, since fuel_alerted was the service that kept my phone from going into Deep Sleep.
This bug should have been fixed long ago but for me it somehow still persists, even on stock JB.
It didn't only drain a lot of battery (I had 8-10h maximum without doing much), it also used up a lot of CPU time, effectively slowing down the whole system to the point that I wasn't able to use Spotify on my phone without severe stuttering.
Well. I found a solution to the fuel_alerted bug.
The procedure is: turning airplane mode on, shutting phone off, taking out battery, putting it back in after a few minutes, turning phone back on.
This solved the problem. No more Android OS draining the power. Phone goes into Deep Sleep again. Only 2% drain after an hour. Spotify runs smoothly again. Yeah!
BUT well... It seems like the problem comes back randomly for me, today I had to replace the battery 5 times...
Now I am trying to strictly follow another "rule" to keep the problem from coming back: Always waking and unlocking the phone before plugging it in or out of power. I never did this before so it could have been the cause of the bug. Now let's see how long it stays bug-free.
If it still doesn't help, I guess I have to conclude it's some kind of hardware problem, which could only be solved by Samsung...
EDIT: Nope. Problem still there. So not really a fix, but maybe still helpful for somebody.
Okay, what ROM are you on?
Sent from the little guy
gastonw said:
Okay, what ROM are you on?
Sent from the little guy
Click to expand...
Click to collapse
It's the up-to-date stock Samsung ROM I guess. See attachment for infos.
Damn, it seems like the problem just came back without me doing much. I only checked BetterBatteryStats every 30 minutes or so and recieved 1 SMS just a minute ago. Seems like the bug started 20 minutes ago, when battery was around 78%. Now it's draining battery like hell again, Spotify stutters, Deep Sleep won't work...
Guess I'll have to pull the battery again.
Since I'm pretty new to all this: What kind of information would be useful to narrow down the source of the problem?
I can provide my BetterBatteryStats screenshots and logcat/dmesg files as well as my Android Battery Stats screenshots.
Is there anything else I could post?
Yeah, screen shots of partial and kernel wakelocks.
Sent from the little guy
I just rebooted the phone, waited for a few minutes and took screenshots.
Here they are.
Okay, this is what you need to do now, drain it empty, charge it (while phone off) till 100 %. Remove the battery, wait for 90 sec or so, put it back and power on.
It's a placebo, but it might work.
Sent from the little guy
Okay, I will try and do the charging overnight. Thanks!
derSchmiddi said:
Okay, I will try and do the charging overnight. Thanks!
Click to expand...
Click to collapse
Good luck man.
Sent from the little guy
I don't know much about kernel and ROM stuff, but I was just wondering...
As far as I understand, the fuel_alerted thing turns on if the battery charge goes below a certain threshold. The old bug with it was that, when recharging, the fuel_alerted thing would sometimes still stay on, even if battery charge is no longer critical.
Could it somehow be possible that this threshold is not set to 15% for me, but something around 80% due to some horrible bug?
This would explain why it suddenly turned on at around 80% when everything was fine before.
We're trying to adjust your fuel gauge and sort of calibrating your battery.
Sent from the little guy
Okay, I did exactly what you recommended.
Everything went well for about 2.5 hours.
Then the fuel_alerted process began again, but this time only for a short while apparently.
It took about 5 minutes kernel wakelock time in a 30 minutes measurement.
Way less than usual and when I check now, it's no longer active.
So. The problem might still be there, or it might not.
Do you recommend going through a few more recharge cycles to get the gauge set properly or do you think this won't make it better?
By the way, thanks for your quick responses!
derSchmiddi said:
Okay, I did exactly what you recommended.
Everything went well for about 2.5 hours.
Then the fuel_alerted process began again, but this time only for a short while apparently.
It took about 5 minutes kernel wakelock time in a 30 minutes measurement.
Way less than usual and when I check now, it's no longer active.
So. The problem might still be there, or it might not.
Do you recommend going through a few more recharge cycles to get the gauge set properly or do you think this won't make it better?
By the way, thanks for your quick responses!
Click to expand...
Click to collapse
Not really.
Now, when it gets to 15% or so plug it in (while phone ON), get battery calibration from play store.
Run the app, when it gets to 100 % hit calibrate. Plug off the device. Turn off.
Take out the battery for 90 sec again, reinsert it and power it on.
That calibration app is another placebo but as I said before, placebos sometimes work.
Sent from the little guy
Since the battery calibration app requires Root access, I flashed a Dorimanx kernel a few hours ago. Then I did a factory reset and the battery-removal thing. 5 hours have passed now without the bug, 3h of which were without wireless access (maybe it correlates with that).
I'll now let the battery (slowly) drain below 15% and then recharge it with phone on overnight. I will use the battery calibration tomorrow and will inform you about the results later.
Thanks man!
Good to know
Sent from the little guy
I did the battery calibration. Bug is still there, no changes
Post you battery details and a couple of BBS screens.
Sent from the little guy
Okay, here are some screenshots.
From the graph you can clearly see when the bug started.
Is it normal to have >26 kworker processes running?
Something else that concerns me: >2h without or with unknown signal. The whole day I was in an inner city area where the signal should be good...
Can you conclude anything from the screenshots?
I will now try something which I also should have tried earlier
I have a spare battery (not original samsung, less capacity) which I just put into the phone.
I'll let it fully charge with phone off and then I will try if the problem persists even with the other battery.
If it doesn't, the problem might come from the battery itself...
Is this a good idea?
No it's not.
You gotta post detailed info there, we can only guess what's draining your battery.
Sent from the little guy
Okay... I posted the screenshots you asked for...
What more should I post?