Related
Hello all,
I purchased a Galaxy S2 at the end of July, I live in the US, so it was from Amazon. The phone has been phenomenal, an amazing piece of technology.
I rooted the phone and flashed Lite'ning Rom 6.1 XXKH3. Still worked great, with no problems at all.
However, starting about a week ago, I am getting an extremely fast battery drain. Since then, I have spent hours looking at threads trying to figure out what was going on. I updated the rom to UltraToxic Rom v8.0 XWKK5, still no change.
I used Titanium Backup to freeze many widgets and app processes, still no change. I am currently using better battery stats to monitor wake locks, however after managing the wake locks, still no change.
I then bought a replacement battery thinking that the battery may have been bad, sadly, there was no change.
I have been trying to find a solution to this and had tried many other suggestions in other threads to no avail. As of now I have come to the conclusion that the device might have some type of malfunction that is causing this.
Am I going crazy or am I missing something obvious? Any help would be greatly appreciated.
Thanks
I have also re-calibrated the battery, still no positive changes.
Seeing the battery graph, you have your screen on a lot of time. Screen sucks battery a lot, so there might be one of the causes of battery draing.
Also you seem to have all day enabled 3G/WiFi, that also sucks some battery with it.
You can try JuiceDefender and see if it can help you extend a little your battery.
change kernel
Try flashing hardcore's "SpeedMod Kernel" and you will never complain about your battery life.....
After flashing this kernel my worse battery life was 1day and 12h with 3.5h screen on and wifi 85% ON.
http://forum.xda-developers.com/showthread.php?t=1182498&highlight=speedmod+kernel
AzureusPT said:
Seeing the battery graph, you have your screen on a lot of time. Screen sucks battery a lot, so there might be one of the causes of battery draing.
Also you seem to have all day enabled 3G/WiFi, that also sucks some battery with it.
You can try JuiceDefender and see if it can help you extend a little your battery.
Click to expand...
Click to collapse
Lol.... It's obvious he has some kind of battery problem, he is not using the phone much, and galaxy S 2 should have at least 5-6 hours screen on time and the phone lasted 3 hours.
Sent from my GT-I9000 using xda premium
Since I had all data on the phone backed up, I did a factory reset. I also flashed the UltraToxic Rom v8.0 XWKK5 as well as the suggested SpeedMod Kernel. When the battery was at 100%, I calibrated the battery. I tried to leave the phone idle as much as possible, I did use the internet for about 10 minutes to check e-mail, news, etc. So now the phone is essentially "empty" in terms of apps downloaded, I got rid of all widgets on all home screens.
There was still no positive change, I do really like the SpeedMod Kernel though, I do notice faster responsiveness from the phone.
I am beginning to think that the problem may be the hardware and not the software or battery.
I've got similar problems here. I am suspecting a hardware problem (I damn well hope it isn't coz i got mine from hong kong) because my phone never goes into deep sleep mode for more than 50% while the screen is off. I've tried at least half a dozen different kernels and roms and nothing helps, this is even in airplane mode i.e. with pretty much everything turned off. I've tested wakelocks and dont get anything more than a couple of seconds. I had my battery charged to full at 6:30am this morning, went to work and got home and it was dead after just under 12 hours with being idle 75% of the time. This is worrying as most people's battery lasts at least a whole day.
So I know it can't be the kernel, I know it cant be wakelocks, I know it cant be wifi or 3g data or anything of that nature so the only thing it comes down to now is hardware...
Funnily enough I've had exactly the same issue since about a week ago. Even when I take it off charge it's almost immediately down to around 80%. It's lasting around 4-5 hours, even when I'm not using the phone much, plus it gets really hot.
A couple of times Social Hub has appeared high up on the list of battery draining apps, although I don't use it. It doesn't always show up though. I switched to the CF-Root kernel and started using GO Launcher EX recently and wondered if that (or one of it's addon widgets) could be the cause.
It's really bugging me now!
SOLVED!
After days and days of trying to fix the issue of the phone not sleeping (and therefore draining excess battery whilst idling) I have finally fixed it!!!!!
First i noticed that along with the sleep problems, I was getting the problems with car mode popping up randomly, the phone going into mtp connection mode, and thinking its charging when it was unplugged. After looking into these issues (and i thought it was a longshot) I decided to do what people were saying and CLEAN THE MICRO USB PORT.
Now you're probably thinking I am a crazy man, but now im just crazy happy that I don't have to send my phone back to Hong Kong!
Instructions:
1. Get a clean, dry, soft-bristled toothbrush.
2. Take any case you have off the phone.
3. Gently insert the bristles into the port and "flick" it out softly.
4. Repeat this about 10-15 times
No matter what ROM, what kernel, what modem i tried flashing, my phone was always sitting on no more than 50% deep sleep mode when idle and had no wakelocks or "rogue apps".
I am now getting 90% - 98% DEEP SLEEP MODE!
I obviously can't guarantee that it will work for everyone, heck how it solved the issue is a mystery to me, one which probably an electronically-minded/computer systems person could answer. What I can say though is I searched high and low online for about a week. I tried different kernels, I tried different ROMs, I tried "re-calibrating" the battery, I used BBS to check for partial wakelocks. If you too have tried all this and have had no success please PLEASE try this and see if you have success!!
Thanks for reading!
....
Or if you didnt...
TL;DR: If you're having battery drain problems clean the micro USB port with a soft toothbrush.
The phone never sleeps when charging, the CPU idles at 200 MHz, whatever was in your USB port was probably making contact with the pins that tells the phone it is connected to a charger when it actually is not, so it was idling at 200 MHz and was not receiving power, that's the only explanation I could fathom
Do two things:
Install CPU spy and show us what the deep sleep percentages are,
and try disabling wifi. Also, what is the router?
I have a battery drain issue; but its kind of screwey as i will reboot my phone and lose about 20% of the phones charge. If i turn it off and leave it off for an hour the charge comes back. Its random as well; only happens once a week. I have had this problem on different roms. You might have a similar problem to me. Possible the hardware that detects battery state is knackered.
Sent from my GT-I9100 using Tapatalk
try to reduce screen brightness it might help, and when on wifi turn off data plan might help too
kamazaki said:
try to reduce screen brightness it might help, and when on wifi turn off data plan might help too
Click to expand...
Click to collapse
Since you didn't seem to realize, I thought I'd tell you. This thread was 5 months old before you posted in it...
lol
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
Can anyone help me with this problem here?
I have been trying various roms on my Vibrant, but didn't spend a ton of time on the ones before Paranoid Android because they seemed unstable. So I can't fully tell you if I was having this issue before, but I will say that the battery drain didn't seem as extreme.
I noticed that I was having extreme battery drain the night after I flashed PA (it was plugged in overnight). I was trying to charge it before I went out, and here's something weird - I was talking on the phone plugged into *AC* power (NOT usb!) and the battery drained during the call! That kind of threw me because it's never something that's happened on AC for me. By the time I went outside, it was down to almost nothing, drained about 5% in 3 minutes walking to the bus stop and died. I recharged it again, swapped in my extra battery in case it was a battery problem, and noticed that also it took a couple of hours of basically not using the phone to drain to 0. I have no signal issues in my area.
I noticed that in BBS that a wakelock ste-gps-interface was taking up a TON of time. I am not using GPS that much. I figured it may be Google now, so I actually froze the app. That didn't seem to help, so I turned of Google location services as much as I could to still use maps - basically everything short of turning GPS off itself. I still got the wakelock! This shows up in the battery settings as making "Android OS" jump to 50% when this is happening.
So since whatever is triggering this wakelock causes the phone to not go into deep sleep and idle at 100mhz, I'm getting bad battery drain. I tried several things such as updating the Semaphore kernel, reflashing the GPS data, using an AGPS app to reset the cache, and tweaking the CPU governor/IO settings. For some reason I seemed to get some relief after reflashing the GPS data once and then clearing cache/dalvik cache, but the issue has come back again.
I couldn't find any informative posts on it, but interesting the posts that I did find were Vibrant specific. If anyone has any ideas past turning GPS off completely please let me know. One thing I have not tried is kernels other than Semaphore, but I've heard that Semaphore is a good match with PA. Thanks!
Edit: I may be wrong because this seems odd, but even turning the GPS off in location preferences doesn't seem to be stopping the wakelock!
Have you calibrated your battery? You should always calibrate after flashing a new rom. I'm not sure about the wake locks you speak of since I have never flashed a PA rom. Someone else may have some insight on that, in the meantime definitely calibrate your battery. I recommend this app https://play.google.com/store/apps/details?id=com.nema.batterycalibration. You must be rooted, I'm assuming you are...
Sent from my SGH-T959 using Tapatalk 2
Thanks, but since this is a wakelock issue with CPU processes running amok I'm afraid battery calibration won't help but to get a few more seconds out of it before it dies in an hour :/
I do think I have found the issue for now, but it's confusing that it's related, so if anyone could shed some light on it, that'd be great. If not, hopefully others who search for it will be able to look for similar issues on their phone.
In the past on other phones, I used the CPU Editor mod that you can find on XDA. I was partial to it because I got good results with the battery saver profile, and unlike other apps on the market that kept a running process, this one was all on the command line. For some reason when I set the profile through the command line and exit the app, as long as it's enabled, the ste-gps-interface wakelock flares up and drains the battery in a matter of hours since the device cannot idle. It was a tough connection to make because I had even disabled GPS entirely and was still getting the wakelock, so I'm still not sure what the connection could be. I did notice that putting CPU Editor into sticky mode caused the device to bootloop, so I wouldn't suggest this script for PA in my experience.
I have since switched back to just using Semaphore Manager to handle CPU and governor settings to keep stuff simple, which I probably should have done in the first place Sort of ironic that trying to squeeze some more battery out of that device caused the wakelock bug. I'd ask the author of the script about it, but it seems to be kind of dead - yet another reason to move on. Smartassv2 is good enough for my purposes!
I'm now having problems with this as well. Rebooting doesn't help and neither does a data wipe. I've been on CM 10.1 nightlies for the last couple weeks and this started on Saturday. Won't allow phone to go into deep sleep. I tried the Greenify method but it doesn't seem to be working from another post... Anyone have any more info?
Welp, I think its a hardware problem unfortunately... The phone went into Safe Mode last weekend when it got damp from rain. Probably due to that.
I've tried everything... I've reverted to stock and wiped everything via odin and it still wont sleep. Time for a new phone! Been a good (almost) 3 years.
Did you try to full formatting to FAT 32 (by USB connection with a PC) both the sdcard and emmc?
selmandeli said:
Did you try to full formatting to FAT 32 (by USB connection with a PC) both the sdcard and emmc?
Click to expand...
Click to collapse
Just did and no go... Still occurring.
Possible Fix
Kind of digging up an old thread but since there was no solution posted, I thought I'd post this for anyone else having this issue and happen to stumble upon this thread.
I had the same issue with SlimBeans where ste-gps-interface was keeping my device awake. I just flashed the gps fix below and initial results show that my phone is going into deep sleep, hopefully this remains to be the case.
http://forum.xda-developers.com/showthread.php?t=2089338
Edit: So after a day's worth of testing, I can say that it worked for me.
Apparently the Insert Image function doesn't work as I expected... so here's a link to the image:
http://ctrlv.in/192705
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?
Hey, I've been using stock 4.1.2+ExperiencedKernel for a long time, it always worked great, but a few days ago I installed an icon pack for KKLauncher, and since then my battery consumption got really bad, around 15-20% per hour when the display is off! I've tried deleting the icon pack, but it's the same, I'm even checking BetterBatteryStats for details, but it doesn't show anything suspicious, although I'm using the app for the first time, so maybe I overlooked something. I have also reflashed the rom+kernel with full wipe, but no luck. Can anyone tell me what can cause this mess, or what should I upload from BetterBatteryStats for someone to check the problem? Thanks in advance.
btw it goes to deep sleep well, so it's not an app that wakes it up constantly (I use greenify too). also the phone itself is very hot, don't know if it's just the battery or the whole thing... but the phone functions correctly.
LilProphet said:
Hey, I've been using stock 4.1.2+ExperiencedKernel for a long time, it always worked great, but a few days ago I installed an icon pack for KKLauncher, and since then my battery consumption got really bad, around 15-20% per hour when the display is off! I've tried deleting the icon pack, but it's the same, I'm even checking BetterBatteryStats for details, but it doesn't show anything suspicious, although I'm using the app for the first time, so maybe I overlooked something. I have also reflashed the rom+kernel with full wipe, but no luck. Can anyone tell me what can cause this mess, or what should I upload from BetterBatteryStats for someone to check the problem? Thanks in advance.
btw it goes to deep sleep well, so it's not an app that wakes it up constantly (I use greenify too). also the phone itself is very hot, don't know if it's just the battery or the whole thing... but the phone functions correctly.
Click to expand...
Click to collapse
If you don't have any wakelocks keeping it awake and you've reflashed the ROM, kernel and did a full wipe and the battery drain still exists... Then I'd say your battery is failing, especially if it's getting hot. My L9 never gets hot, even under heavy use.
The only other thing you could really try is flashing back to stock and see if the problem is still there... Really though, I'm pretty sure it's your battery.
xdrc45 said:
If you don't have any wakelocks keeping it awake and you've reflashed the ROM, kernel and did a full wipe and the battery drain still exists... Then I'd say your battery is failing, especially if it's getting hot. My L9 never gets hot, even under heavy use.
The only other thing you could really try is flashing back to stock and see if the problem is still there... Really though, I'm pretty sure it's your battery.
Click to expand...
Click to collapse
Hi, thanks for your answer. The problem is, the phone gets really hot on the upper side of it, near the camera. The battery never gets hot at all. Is it possible, if it's battery problem?
LilProphet said:
Hi, thanks for your answer. The problem is, the phone gets really hot on the upper side of it, near the camera. The battery never gets hot at all. Is it possible, if it's battery problem?
Click to expand...
Click to collapse
I thought you meant that the battery was getting hot. The last time I had a battery go out, it was getting hot and it was draining fast. Shortly after that it wouldn't take a charge anymore.
It is possible that it's a hardware issue. WiFi, GPS or the camera could cause it to get hot also.
You can also try and boot the phone into "Safe Mode" and run it like that for a day or two and see if the problem still exists. If it problem disappears while in Safe Mode then you have a rogue app or something that's causing the issue.
Then to narrow it down you could try downloading Wakelock Detector and see if something is keeping it awake, making it hot and drain the battery.
Monitor it with Better Battery Stats and Wake lock Detector. Post some screen shots of BBS and Wakelock Detector here too. That way we can see if something is going on.
This is one of those issues that will take a process of elimination to figure out.
xdrc45 said:
I thought you meant that the battery was getting hot. The last time I had a battery go out, it was getting hot and it was draining fast. Shortly after that it wouldn't take a charge anymore.
It is possible that it's a hardware issue. WiFi, GPS or the camera could cause it to get hot also.
You can also try and boot the phone into "Safe Mode" and run it like that for a day or two and see if the problem still exists. If it problem disappears while in Safe Mode then you have a rogue app or something that's causing the issue.
Then to narrow it down you could try downloading Wakelock Detector and see if something is keeping it awake, making it hot and drain the battery.
Monitor it with Better Battery Stats and Wake lock Detector. Post some screen shots of BBS and Wakelock Detector here too. That way we can see if something is going on.
This is one of those issues that will take a process of elimination to figure out.
Click to expand...
Click to collapse
I've been using BBS, it shows that the phone is in deep sleep in most of its off time, no app wakes it up. Also, wifi seems to lose its signal very often, even though it's strong (there wasn't any problem with that before).
I'm using the phone now without SD and SIM cards, it doesn't seem to be that hot than it used to, but charging and draining are still very weak. I'm gonna try safe mode as you suggested, and also using the phone without wifi turned on, if that is the issue. Thanks for your tips.
So, the phone cooled down after I turned off wifi, then I rebooted to safe mode, and it became hot once again, but after the media scanning, it cooled down once again. So I guess it may be the CPU? I've been trying to get a picture of the phone's circuit board with no luck, because the phone is only warm in the upper 1/3, the other parts seem to be cooled down all the time.
I'm gonna return it to T-Mobile on Monday, hopefully they won't notice the unlocked bootloader.
LilProphet said:
So, the phone cooled down after I turned off wifi, then I rebooted to safe mode, and it became hot once again, but after the media scanning, it cooled down once again. So I guess it may be the CPU? I've been trying to get a picture of the phone's circuit board with no luck, because the phone is only warm in the upper 1/3, the other parts seem to be cooled down all the time.
I'm gonna return it to T-Mobile on Monday, hopefully they won't notice the unlocked bootloader.
Click to expand...
Click to collapse
Yeah it might be the CPU. Also if it's dropping and/or scanning a lot for WiFi, then it will definitely get hot and kill the battery quickly.
I don't think that T-Mobile will notice that it's unlocked. As long as you flash back to stock ROM before taking it in, then they probably won't notice. They would have to be purposely looking for it to be unlocked.
You might want to flash back to stock anyway and see if the problem is still there... It very well could be a ROM/kernel issue causing the problem.
xdrc45 said:
Yeah it might be the CPU. Also if it's dropping and/or scanning a lot for WiFi, then it will definitely get hot and kill the battery quickly.
I don't think that T-Mobile will notice that it's unlocked. As long as you flash back to stock ROM before taking it in, then they probably won't notice. They would have to be purposely looking for it to be unlocked.
You might want to flash back to stock anyway and see if the problem is still there... It very well could be a ROM/kernel issue causing the problem.
Click to expand...
Click to collapse
I have flashed back stock one I've been using (cwm flashable), of course I will remove root and any suspicious apps. I appreciate your help.
Sent from my LG-P760 using xda premium