[Q] Overheating issues since going Franco - Nexus 5 Q&A, Help & Troubleshooting

[Q] Overheating issues since going Franco - Nexus 5 Q&A, Help & Troubleshooting

So I've had a lot of issues with my nexus 5 randomly rebooting and decided it was time to do a complete factory reset on it. Since I had been running stock, unrooted, locked bootloader since launch, I also decided it was time to unlock, root, and switch to Franco to see if it would improve things.
Now before, when I was charging my phone in my car, on my dashboard mount, while running Waze and driving in sunlight without AC (mine's dead), my phone would sometimes overheat. I'd know because it was hot to the touch, my battery widget would show overheat status, and it would stop charging. It would still FUNCTION, though.
Since my wipe/root/Franco change, though, it no longer reacts the same way. Now it simply gets so hot that it begins to freeze or fail to respond to normal functions and then eventually reboots itself, one time putting itself into a boot loop from the heat until I stepped in, forced it to the bootloader and powered it off until it cooled down.
Any idea why this change to Franco (I'm assuming it's the difference and not merely rooting, since that shouldn't change anything) would cause this, and what sort of settings I should adjust? I changed CPU temp threshold from 60 down to 52 in FKU, but that's done either nothing, or simply avoided the boot loop issue I had before. Do I need to lower that further? It's not even clear what that setting does. Anything else I can do?
Strongly considering going back to stock kernel to test further, but I know it's a slight pain to remove Franco due to all the roots, plus I wanted its improvements.

TurboFool said:
So I've had a lot of issues with my nexus 5 randomly rebooting and decided it was time to do a complete factory reset on it. Since I had been running stock, unrooted, locked bootloader since launch, I also decided it was time to unlock, root, and switch to Franco to see if it would improve things.
Now before, when I was charging my phone in my car, on my dashboard mount, while running Waze and driving in sunlight without AC (mine's dead), my phone would sometimes overheat. I'd know because it was hot to the touch, my battery widget would show overheat status, and it would stop charging. It would still FUNCTION, though.
Since my wipe/root/Franco change, though, it no longer reacts the same way. Now it simply gets so hot that it begins to freeze or fail to respond to normal functions and then eventually reboots itself, one time putting itself into a boot loop from the heat until I stepped in, forced it to the bootloader and powered it off until it cooled down.
Any idea why this change to Franco (I'm assuming it's the difference and not merely rooting, since that shouldn't change anything) would cause this, and what sort of settings I should adjust? I changed CPU temp threshold from 60 down to 52 in FKU, but that's done either nothing, or simply avoided the boot loop issue I had before. Do I need to lower that further? It's not even clear what that setting does. Anything else I can do?
Strongly considering going back to stock kernel to test further, but I know it's a slight pain to remove Franco due to all the roots, plus I wanted its improvements.
Click to expand...
Click to collapse
your phone overheating isnt cpu heating related, so changing that setting in fku will do nothing for you. its your battery thats overheating, not your cpu. its your own bahavior thats the issue actually. the battery and cpu have differing throttle/shutdown/overheating temps. the problem is that you are charging while plugged in, in the sun/heat, while using it. the battery gets warm just from a normal charging, gets hot while using and charging, but you also have it in the heat, lol.

simms22 said:
your phone overheating isnt cpu heating related, so changing that setting in fku will do nothing for you. its your battery thats overheating, not your cpu. its your own bahavior thats the issue actually. the battery and cpu have differing throttle/shutdown/overheating temps. the problem is that you are charging while plugged in, in the sun/heat, while using it. the battery gets warm just from a normal charging, gets hot while using and charging, but you also have it in the heat, lol.
Click to expand...
Click to collapse
Right... I'm not contesting that, and I basically stated most of that already. But my thread is about how this behavior has CHANGED since going Franco, and I'm looking for how to fix it. As I said, BEFORE Franco, in the same situation, my phone would get hot, stop charging, and continue functioning while it stopped charging. Now, instead of functioning and not charging, it appears to continue to get hotter and hotter until it freezes, crashes, and reboots. It didn't do that when I was stock, unrooted, locked. Now that I'm Franco, rooted, unlocked, it can't withstand this situation the way it did before. So I'm looking to improve upon that.
I'm perfectly fine with the old behavior because, as you note, this is my own "fault" by putting it in this situation (not that I have much of a choice), so I recognize I'm pushing the phone beyond what it should do. But the phone was smart enough to account for the problem and do what it needed to to stay functional, so I wouldn't lose my GPS or phone call in the middle just because I wasn't actively watching the battery meter every second, WHILE DRIVING, to see if it was overheating. It would notice on its own, stop charging, and get around the problem without crashing. I just want that behavior back, and I'm hoping a Franco setting can help me restore that since the issue seems to tie to my switch to Franco.

Then put the stock kernel back on. Get the factory image and extract the boot.img and flash it with fastboot

TurboFool said:
Right... I'm not contesting that, and I basically stated most of that already. But my thread is about how this behavior has CHANGED since going Franco, and I'm looking for how to fix it. As I said, BEFORE Franco, in the same situation, my phone would get hot, stop charging, and continue functioning while it stopped charging. Now, instead of functioning and not charging, it appears to continue to get hotter and hotter until it freezes, crashes, and reboots. It didn't do that when I was stock, unrooted, locked. Now that I'm Franco, rooted, unlocked, it can't withstand this situation the way it did before. So I'm looking to improve upon that.
I'm perfectly fine with the old behavior because, as you note, this is my own "fault" by putting it in this situation (not that I have much of a choice), so I recognize I'm pushing the phone beyond what it should do. But the phone was smart enough to account for the problem and do what it needed to to stay functional, so I wouldn't lose my GPS or phone call in the middle just because I wasn't actively watching the battery meter every second, WHILE DRIVING, to see if it was overheating. It would notice on its own, stop charging, and get around the problem without crashing. I just want that behavior back, and I'm hoping a Franco setting can help me restore that since the issue seems to tie to my switch to Franco.
Click to expand...
Click to collapse
the dynamics of the two kernels are completely different. they are so different that one or more of many many changes could be possible culprit(s).

jd1639 said:
Then put the stock kernel back on. Get the factory image and extract the boot.img and flash it with fastboot
Click to expand...
Click to collapse
...if I'm here asking for assistance on how to adjust Franco to resolve this problem, isn't it obvious I'm trying to avoid doing that? I'm here looking to see how to fix Franco so I can still use it. I know I can go back to stock, but that's not a fix, it's throwing my hands up in defeat. I'll certainly do that if nobody can offer me good advice, but I'd rather not.
simms22 said:
the dynamics of the two kernels are completely different. they are so different that one or more of many many changes could be possible culprit(s).
Click to expand...
Click to collapse
I understand, of course. I just hoped someone here had a similar experience that might help us track this down. I imagine people with more technical knowledge have put this kernel through it paces and might have an idea. PR better yet, know of a setting in FKU I can adjust to counter this.

Hi,
I've experienced the overheating issues with Franco kernel.. Have been using ElementalX kernel until i chose to try out Franco r69 kernel. Woke up in the middle of the night while phone was charging to a vibration sound that continued every 1 minute or so. Vibration was from when device is rebooting all the time. I checked the phone and it was really I mean really hot was uncomfortable to keep it in my hand. I immediately thought this could be something that a kernel might do. So I flashed ElementalX 2.05 back and tried to start it again. After the "Android is updating" window it started doing that again, heating up and rebooting. So I left it to cool home and started using my backup phone. Not sure what caused this but will research more when I come home. Hopefully phone is still good and I dont need to get it repaired.
Have been using the original charger, experienced some problems with other chargers.

Related

Pattern to my reboots - do yours have a pattern?

So over the last few days my phone seems to have settled into some sort of weird pattern with reboots. Although there are outliers, in general it always seems to reboot between 19-24h of uptime and nearly always at like 45 or 50 mins past the hour. It's the most bizarre thing in the world and why I think there's some funky software doing it. I don't have true random reboots, but I can't figure out what it is that is doing this. Very odd.
In all cases my phone is sitting with the screen off (I've NEVER had a reboot while using the phone/screen on) but it doesn't matter what radios are on, WiFi, BT, GPS (can be off or on).
Last time I ran "CatLog" a logging app from Market and had it write to SD logs and a reboot happened but it only by default writes every 200 lines so the last line in the file was probably not the last line in the log. I'm going to try again later and set it to write every line or few lines so I can see the last entry in the log before a reboot. Might shine some light on it.
Just find it very strange since it's a very stable and capable phone for about 18hrs and then it just craps on itself. Very strange.

finally. I too just think it is some weird software or driver bug because I was running EB 1.0.4 FINE for like 3-4 days and loving it... then it started resetting almost hourly. I didn't install any other apps past my initial normal set of apps.
Even CM7, seems like it is fine for a few days, then gets crazy. As long as I put a new nightly rom on it every day, it's good.
I didn't have any issues with stock though and didn't seem to have issues with CM7 for a while until lately.
The leaked GB rom causes lockups immediately out of the gate seemed hourly.
I use CM7 as my main daily driver now but I think you are on to something. We are talking about the Screen of Death right? I don't think mine ever reboots, but gets stuck at the lockscreen where the the display comes up, swiping to unlock vibrates then the phone but doesn't change screens to desktop. The buttons and click/drag widgets work even though you are looking the lockscreen.
I've never had my phone powered off in my pocket or noticed it "rebooting". Mine just has the SoD that seems to follow your pattern idea. They may be related. Stock roms may reset once it locks up, where CM7 just keeps running in its locked state.

I have a really strong sneaking suspicion that every G2X reboots but not everyone notices. Also if you naturually turn your phone off once a day or so you won't notice it perhaps or even a few days. The phone reboots pretty fast and the only way I've been noticing (except the times I see/hear it happen) is I have an uptime widget on my homescreen so it's obvious.
Same thing happened with my Droid Incredible btw...when it first came out there were all kind of random reboot issues. After a software update I would run that phone hard for 30-45 DAYS straight without a reboot.
It's annoying but I think it's just a matter of time before the G2X is the same.

I just hope that update gets here sooner than later.
Sent from my LG-P999 using XDA App

I dunno. The tmobile jingle is pretty loud and I never hear it. CM7 has a silent one so possibly there but I dunno.
I use my phone pretty often and never had the suspicious that it reboots. My phone stays very cool during my usage compared to my nexus and other phones
My uptime was 4 hours since I reset it last. I'll monitor it with results. It'll be hard not to flash but I'll keep track and see how far I can keep it online.

i have not had any reboots or waking up to a dead phone ....with the only fix is a battery pull.... ever since I started.
1) my over night charging / long term charging to 100%... only on the LG charger that it came with. Only short term...maybe. less than an hour and not to a 100% charge on a non LG charger (car charger etc...)
2) I restart my G2x every morning when I take it off the LG charger..(after I take it off..I did it once while on the charger and had an issue... (there is definitely an issue related to when it charges to/ around 100% charge)
Just my 2 cents.

Pattern to my reboots - do yours have a pattern?
Hold Power and volume up simultaneously for about 10 seconds.

I've had my phone since Friday, but the only time I had the rebooting problem was this past Saturday when it rebooted four times within 15 minutes or so. Before the rebooting began, the phone had slowed down to a crawl, so I went ahead and rebooted it. After that, I sat it down and watched it reboot a few times on its own. Luckily my iPhone 4 owning co-worker was completely unaware of this issue since we tease and bicker with each other every day over Android and iOS .

mobilehavoc said:
I have a really strong sneaking suspicion that every G2X reboots but not everyone notices. Also if you naturually turn your phone off once a day or so you won't notice it perhaps or even a few days. The phone reboots pretty fast and the only way I've been noticing (except the times I see/hear it happen) is I have an uptime widget on my homescreen so it's obvious.
Same thing happened with my Droid Incredible btw...when it first came out there were all kind of random reboot issues. After a software update I would run that phone hard for 30-45 DAYS straight without a reboot.
It's annoying but I think it's just a matter of time before the G2X is the same.
Click to expand...
Click to collapse
I can guarantee that mine don't reboot. I've had it up fire days, checked the up time and play with it constantly.if it rebooted in the middle of the night I would hear it or the uptime would be close to zero in the morning..
I have a way stable phone.running stock, rooted with bloat removed.. I love this damn stable phone.

smashpunks said:
I can guarantee that mine don't reboot. I've had it up fire days, checked the up time and play with it constantly.if it rebooted in the middle of the night I would hear it or the uptime would be close to zero in the morning..
I have a way stable phone.running stock, rooted with bloat removed.. I love this damn stable phone.
Click to expand...
Click to collapse
What bloat did you remove? I've removed most but not all of it. Can you list it?

mobilehavoc said:
What bloat did you remove? I've removed most but not all of it. Can you list it?
Click to expand...
Click to collapse
Everything other than smart share, tegra zone and qik. Of course have nova and need for speed also.
Oh also have car home froze..

Maybe jumping the gun here but I tried to let mine go as long as it could without resetting it. I kept tabs on it and it was running awesome the entire time (#33 CM7).
Last time I noticed my phone on was like 17:33:xx hours. I had like 44% battery left. Next thing I know the phone is off. I tried turning it on and a battery icon flashed and turned back off.
What I am thinking is that perhaps the faulty battery driver is telling the phone that the battery is dead and preventing it from booting up. We were talking in another thread and I said something that really makes sense: If the battery driver tells the OS that there is 0% battery then it will just reboot. The battery itself may have a 50% charge left. That would explain the random reboots too (the battery driver telling the phone there is 1% left and cutting power). Maybe a hard reset semi-corrects the problem but eventually resets again due to false information.
My weirdness/powered off occurred right around 18hours. The phone could have just died too.
Almost need a Voltmeter so someone can test the battery (or however it can be tested).

player911 said:
Maybe jumping the gun here but I tried to let mine go as long as it could without resetting it. I kept tabs on it and it was running awesome the entire time (#33 CM7).
Last time I noticed my phone on was like 17:33:xx hours. I had like 44% battery left. Next thing I know the phone is off. I tried turning it on and a battery icon flashed and turned back off.
What I am thinking is that perhaps the faulty battery driver is telling the phone that the battery is dead and preventing it from booting up. We were talking in another thread and I said something that really makes sense: If the battery driver tells the OS that there is 0% battery then it will just reboot. The battery itself may have a 50% charge left. That would explain the random reboots too (the battery driver telling the phone there is 1% left and cutting power). Maybe a hard reset semi-corrects the problem but eventually resets again due to false information.
My weirdness/powered off occurred right around 18hours. The phone could have just died too.
Almost need a Voltmeter so someone can test the battery (or however it can be tested).
Click to expand...
Click to collapse
Yes I know the battery driver is part of the problem as can be seen on CM7 builds but what's odd is my time varies so for a long time it would reboot every 17-20 hours, now all of a sudden it goes to 36 hours before it usually reboots. Looking at logs it doesn't appear to throw any major errors before a reboot which implies that it's a a kernel panic or low-level fault. At this point I've given up on trying to find the issue since it's been repeated over and over that T-Mo and LG are releasing an update. Might as well enjoy the phone and wait for that to come out

Amen. Just keep flashing CM nightlies and you'll never worry about it.

Phone shuts off all the time

Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.

spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
Well, if you were having this issue before the rooting took place, this very well may be hardware related. There are a few things I recommend before the dreaded unroot and send back to manufacturer route (assuming the phone is under warranty still). It's been proven or at least shown that battery calibration (the whole charge to 0Ma and then fully discharge and then recharge) is a pipe dream.
I would first say find out if the CM7 ROM you're using is OCing or UVing, while you may see some people OCing to 1.3 or higher and UVing -75, not all phones are created equal in capabilities and some phones will randomly freeze/turn off if they don't like your OC and UV settings. I would also suggest flashing a different ROM to see if this problem persists. Cleardroid is what I recommend just to get an idea if it is in fact a OC or UV problem as I believe cleardroid is set up to default stock settings.
You can also try a new battery, I have heard/read/seen that bad batteries can cause reboots. Again though if this was an issue you were sometimes experiencing before, you may have hit the tip of the iceberg on a hardware issue and its finally starting to show now. Hope this helps.

Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.

Agoattamer said:
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Click to expand...
Click to collapse
That was my thoughts exactly. However, if the ROM or kernel or whatever is set to shut off the phone at a certain reading of discharge from the battery, ie -500mA, this could also be the problem.
I thought it could have been a problem with the phone as well, but before it would shut off on its own MAYBE once a month. 90% of those I attributed to overloading the phone, closing facebook, opening the internet, starting to load a webpage then open a new txt I just recieved while the phone was still vibrating type things.
Now it still feels like it's just quitting on me, it never turns off while the screen is locked or while its charging. So far after the new ROM it has shut off when I place a call, when I receive a call, clicking on a notification, opening the messaging app, clicking download in the market, and my favorite when I unlock it from sleep.
I will download a different rom right now and try it. Just to double check this is what I've been doing to install a new rom... I boot my phone into recovery (vol- and power), go to recovery from the boot screen (opens clockworkmod), scroll down to mounts and storage, have it format /system, /data and /cache, go back to wipe data/factory reset, then install zip from sdcard, select the rom and go... I know some roms require inspiremod, should I still install this if I'm USING an inspire??
Thanks for the input guys, I really appreciate it

If it does turn out to be the battery or you just decide to get a new one to test it out. I recommend these, they are awesome and the only thing anyone should try besides HTC factory replacements. Good luck and I hope this works out for you.
Anker Batteries

i only skimmed this. but cleaning battery contacts can help also check the side door, sometimes that can cause issues as well. air can out everything and clean metal contacts with rubbing (ipa) alcohol.

So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!

If it doesn't do it when its chargeing then it is the battery. I had bought my inspire from someone and it was having those issues ordered a new HTC stock battery from newegg for like $12 and has been working perfectly since then and honestly if you want the best battery rom absolution is the rom you should check out. It's a non sense rom but again I'd just buy a new battery. I had mine timed it'd reset at 92% 74% and 49% xD
Sent from my Inspire 4G using xda premium

spcclark said:
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
Click to expand...
Click to collapse
hmm, I would say try a new battery before getting a new phone. Worst case scenario is that you spent $15 to learn you need a new phone as opposed to spending $100+ on a new phone...this is of course assuming you want to keep the inspire and not just looking for a reason to get upgrade ahaha

I agree. It still sounds like a battery issue.

I would agree this definitely sounds like an internal short in the battery. Sounds like it's shutting off whenever it gets a significant load on it. Try a new battery first.

I had a similar issue though I was tweaking the CPU. Learned my lesson.
Sent from my Inspire 4G using XDA App

Yeah, Id bet money that its a bad battery. I had this same exact issue with my Inspire. If it shuts off more in low reception areas but it isn't shutting off when plugged in, its definitely the battery. I would try to find someone with an Inspire and try switching them batteries and see if it stops.

If I tried to use the flash with my camera, the phone would shut off. My phone would randomly reboot or turn off. ATT told me they had "some" bad batches of batteries. My phone was still under warranty so ATT sent me a new battery. All the problems went away!

The battery door on the Inspire becomes wonky the more you open it, I was having a problem like yours, new battery and new door has me going good.

Random Shutdown..slightly different view on this problem

Update 14/09/2012
Ok, I don't think what I had in mind helped. On 13th, I had multiple shutdown while trying to use cameras and today had multiple shutdown while on the phone to someone.
Think I will try doing something with Firmware next, now have a feel it might be the cause. I have no idea what is wrong, so just going to give with anything really. Will report back soon.
Update: 13/09/2012
After a complete drain the first time, by booting into recovery and bootloader (just want to remind everyone that this is because I can't make my phone boot). Then I left it on charging for the whole night, and I did this through wall charger NOT USB. I think I read it somewhere that they recommended this when calibrating your battery. Then the next day got 1 random shutdown, then I used it until it is completed drain again. Then followed by another full charge using wall charger. Today I have been using it for 6 hours and 21 minutes, haven't had a single problem. I don't know how not doing this would cause the phone to shutdown, but doing what I did seems to be working so far. I can actually rely on it for something now, say important phone calls.
Here was my reply to elvisypi:
Just to answer your question, it would random shutdown (not so much reboot) at anytime, at any battery percentage. I could do be doing anything, using any app, sometimes when I am not even using the phone.
I don't think it's a hardware/battery/ROM/kernel problem, I tried to say that it is a combined problem caused by flashing a phone too many times maybe or too often in a period of time. Also I was just about to update saying that calibrate battery does help. I had no reboot so far and this is only the second full charge and full drain I did.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Original post 11/09/2012
After reading kushXmaster's post (click here) about how to add an object to help the battery stay in position (or get better connection), I found evidence that my issue was different. Before anyone ask, yes I have tried kushXmaster's idea, and no it did not work for me.
Ok, this is what I found. I had this problem not only with my current phone (htc sensation) but also with my previous phone (htc desire). So now thinking about it, it can't be the hardware problem. Cos the same problem happening to 2 different phones is pretty unlikely, not impossible, but very unlikely. The other thing was that my phones (both) didn't do this at the start when it was new, and it has only been like this a few months later (since I rooted it). For those who already guessed, yes I believe it's the flashing phones which is messing it up. However I don't know the reason or understand what is wrong with the phone. I have tried wipe battery stats and calibration, nothing worked, the only thing I found was when I go back to Sense 4 roms the problem seems better, but it is still there.
The last and most important reason why I am don't think this is a battery or hardware problem, is that my phone boots into bootloader or recovery with no problem (no reboot or shutdown). But when i tell it to boot normally it decides it hates me and turns it self off.
I am currently experiencing this problem, my phone is in recovery and I am waiting for battery to drain completely. Then gonna do calibration from there, hopefully this will work. I will keep you guys updated. Also if anyone has suggestions please leave a comment, and also let me know if anyone else is in the same position, good luck!

If you want to drain your device battery faster or more nicer way put screen timeout to never and like this you can still use your phone normal and drain the battery aswell just a little tip
Sent From My Sexy Sensation.

shahkam said:
If you want to drain your device battery faster or more nicer way put screen timeout to never and like this you can still use your phone normal and drain the battery aswell just a little tip
Sent From My Sexy Sensation.
Click to expand...
Click to collapse
If I could get it to turn on then I have a lot of ways to drain it quickly, but like I said it won't boot without shutting down before I could do anything. I turn it on, and I see the lock screen then bam it is shut down again.

lavafire said:
If I could get it to turn on then I have a lot of ways to drain it quickly, but like I said it won't boot without shutting down before I could do anything. I turn it on, and I see the lock screen then bam it is shut down again.
Click to expand...
Click to collapse
Ohhh sorry didn't get that
Sent From My Sexy Sensation.

To drain battery.. switch on wifi and bluetooth.. thn use 3g for 20 mins.. u will drain compltly
Sent from my HTC Sensation using xda premium

lavafire said:
After reading kushXmaster's post (click here) about how to add an object to help the battery stay in position (or get better connection), I found evidence that my issue was different. Before anyone ask, yes I have tried kushXmaster's idea, and no it did not work for me.
Ok, this is what I found. I had this problem not only with my current phone (htc sensation) but also with my previous phone (htc desire). So now thinking about it, it can't be the hardware problem. Cos the same problem happening to 2 different phones is pretty unlikely, not impossible, but very unlikely. The other thing was that my phones (both) didn't do this at the start when it was new, and it has only been like this a few months later (since I rooted it). For those who already guessed, yes I believe it's the flashing phones which is messing it up. However I don't know the reason or understand what is wrong with the phone. I have tried wipe battery stats and calibration, nothing worked, the only thing I found was when I go back to Sense 4 roms the problem seems better, but it is still there.
The last and most important reason why I am don't think this is a battery or hardware problem, is that my phone boots into bootloader or recovery with no problem (no reboot or shutdown). But when i tell it to boot normally it decides it hates me and turns it self off.
I am currently experiencing this problem, my phone is in recovery and I am waiting for battery to drain completely. Then gonna do calibration from there, hopefully this will work. I will keep you guys updated. Also if anyone has suggestions please leave a comment, and also let me know if anyone else is in the same position, good luck!
Click to expand...
Click to collapse
If you get random reboots, shutdowns, than don't even bother to calibrate the battery. It has nothing to do with the calibration. Tell us more info, how do the reboots happen, how often, what are you doing when it happens, etc. It could be a kernel/ROM problem, charger, battery, hardware. Pls give us more detailed info

shahkam said:
Ohhh sorry didn't get that
Sent From My Sexy Sensation.
Click to expand...
Click to collapse
No problem, appreciate the help :good:

elvisypi said:
If you get random reboots, shutdowns, than don't even bother to calibrate the battery. It has nothing to do with the calibration. Tell us more info, how do the reboots happen, how often, what are you doing when it happens, etc. It could be a kernel/ROM problem, charger, battery, hardware. Pls give us more detailed info
Click to expand...
Click to collapse
Thanks for the tip, but tbh if i know all that I don't really need to be asking anyone. For example, if it is a ROM problem, i just change ROM. The problem is that I don't know the cause and it seems to be everything and anything, it will shut down at different length of time, sometimes when it just starts, others 30 seconds after boot has completed. I am not looking for a solution, I am more wondering what everyone else has experienced when they say they have random reboots or shutdown, because after tones of research no one has provided anything that fixes my problem.
Just to answer your question, it would random shutdown (not so much reboot) at anytime, at any battery percentage. I could do be doing anything, using any app, sometimes when I am not even using the phone.
I don't think it's a hardware/battery/ROM/kernel problem, I tried to say that it is a combined problem caused by flashing a phone too many times maybe or too often in a period of time. Also I was just about to update saying that calibrate battery does help. I had no reboot so far and this is only the second full charge and full drain I did.

I had a same reboot problem and tried the kushXmaster's trick with the business card and did not worked for me either, at the beginning…
There was no reboot or shutdown in bootloader mode in my device either. When I flashed new firmware and ROM the problem was gone, but only for few weeks. I tried multiple ROMs also, but always with the same result. This is why I was skeptic with the business card battery fix also.
But then I read kushXmaster's thread again and put an alu foil as shown by Shreyas Jani and pulled the ground pin as described by StuartTheFish. I still do not understand what happened, but my phone is working perfectly more than a month now, without restarts and shut downs. I do not know which solution helped (not sure if I placed a business card correctly before). But I do not want to experiment with this anymore. I did not even removed a battery cover since that time and I'm glad it is all working now.
Hope this helps.

prgab said:
I had a same reboot problem and tried the kushXmaster's trick with the business card and did not worked for me either, at the beginning…
There was no reboot or shutdown in bootloader mode in my device either. When I flashed new firmware and ROM the problem was gone, but only for few weeks. I tried multiple ROMs also, but always with the same result. This is why I was skeptic with the business card battery fix also.
But then I read kushXmaster's thread again and put an alu foil as shown by Shreyas Jani and pulled the ground pin as described by StuartTheFish. I still do not understand what happened, but my phone is working perfectly more than a month now, without restarts and shut downs. I do not know which solution helped (not sure if I placed a business card correctly before). But I do not want to experiment with this anymore. I did not even removed a battery cover since that time and I'm glad it is all working now.
Hope this helps.
Click to expand...
Click to collapse
I experienced exactly what you experienced, when i flash a new ROM it is ok for a while. Then just gets to the stage where it happens again. I also tried almost every single ROM I could find, only sense 4 seemed to help but still didn't solve this problem completely.
Thanks for the help, really useful. If what I am trying now doesn't work then what you suggested will definably be my next hope. Cheers!
Edit: I know what you mean, if it works that back cover is not coming off.

same as you
I experience now typically the same problem as yours.
Did changing firmware helped? And how to do this?

[Q] 4G SLIDE strange charging issues

First, sorry if this has already been discussed somewhere, but I couldn't find a topic with a case exactly like mine.
I have a 4G Slide. From the beginning, as I don't like Android 2.3 (or whatever it was, 2.X anyway) I upgraded to 4.0 by installing Cyanogenmod 9.10 (stable release for Doubleshot). So I don't really know how it was before CM 9, but here's the issue.
First, this phone takes forever to charge it, even leaving it overnight isn't enough sometimes. However, it can reach 100%, it's just really slow. And here's the strange part. If you look at the charge graph in Battery menu, you can see the straight line going up, and at a certain moment you can notice what looks like a very slight break in it - not a gap, I mean that it's going up at a certain angle, and you see it suddenly change a bit, like the charging speed slowed down or something. So I found out that when you see this line break, you can just reboot the phone. And it shows 100% charge, the light is green! Otherwise you'll have to wait for hours until it shows 100%.
Also, changes in charge displayed on the screen are almost unpredictable. Sometimes it shows you it's holding charge well for a relatively long time, and suddenly, there's a sharp fall in the graph, and the phone shuts off. It's especially annoying during the night, as I use it as an alarm cloclk to wake up, and once I almost was late for work because the stupid thing died in the night, luckily I woke up by myself.
So my question is whether this can be fixed as I'm fed up. What I tried: changed the battery, tried different chargers, tried to clean the micro USB on the phone (the charging port), installed an updated version of CM 9 from this site. Nothing seems to help. So I'll be grateful if someone can tell me what it is, maybe you've seen this happen. Does it mean my phone has a bad charging controller? I also heard that flashing a different kernel sometimes helps, but there aren't any available for my phone.
Thank you.

RomanKasp said:
First, sorry if this has already been discussed somewhere, but I couldn't find a topic with a case exactly like mine.
I have a 4G Slide. From the beginning, as I don't like Android 2.3 (or whatever it was, 2.X anyway) I upgraded to 4.0 by installing Cyanogenmod 9.10 (stable release for Doubleshot). So I don't really know how it was before CM 9, but here's the issue.
First, this phone takes forever to charge it, even leaving it overnight isn't enough sometimes. However, it can reach 100%, it's just really slow. And here's the strange part. If you look at the charge graph in Battery menu, you can see the straight line going up, and at a certain moment you can notice what looks like a very slight break in it - not a gap, I mean that it's going up at a certain angle, and you see it suddenly change a bit, like the charging speed slowed down or something. So I found out that when you see this line break, you can just reboot the phone. And it shows 100% charge, the light is green! Otherwise you'll have to wait for hours until it shows 100%.
Also, changes in charge displayed on the screen are almost unpredictable. Sometimes it shows you it's holding charge well for a relatively long time, and suddenly, there's a sharp fall in the graph, and the phone shuts off. It's especially annoying during the night, as I use it as an alarm cloclk to wake up, and once I almost was late for work because the stupid thing died in the night, luckily I woke up by myself.
So my question is whether this can be fixed as I'm fed up. What I tried: changed the battery, tried different chargers, tried to clean the micro USB on the phone (the charging port), installed an updated version of CM 9 from this site. Nothing seems to help. So I'll be grateful if someone can tell me what it is, maybe you've seen this happen. Does it mean my phone has a bad charging controller? I also heard that flashing a different kernel sometimes helps, but there aren't any available for my phone.
Thank you.
Click to expand...
Click to collapse
ICS may just have battery stats that don't work for your batteries. Try calibrating the battery:
http://www.androidpit.com/how-to-calibrate-the-battery-on-your-android-device
https://play.google.com/store/apps/details?id=com.nema.batterycalibration&hl=en
If I remember the instructions properly, install the app, charge to full (or half hour past full), open the app to press the button, run it dry, and charge it fully with it turned off (note the LED on mine turns green at the 90% mark, so leave it plugged in and off for about an hour past the time it turns green).
I found with the app, it takes forever to get that last 1% after using it, and it takes a while before dipping below it again, but it seems to be more accurate than CM thinking I had the stock battery installed (I have a couple Ankers now). Hope this helps.

Thank you but doesn't work
Nothing helps. It's surely not related to incorrectly calibrated battery. I did 8-1-1 charge which DID help when I bought a Chinese copy of Samsung Galaxy S3 Mini (my wife is using it now, and it's working fine, battery life is very good). But my stupid phone doesn't react. Just 5 minutes ago, when I was talking to my friend, it still showed about 30% left, then it suddenly died and I even couldn't turn it on, even while it was charging, the red light was blinking. Then it turned on and showed 2%! But the most interesting thing is that now there's something else going on, which I've NEVER seen! Because when I looked at it after approximately 10 minutes, it showed 98%!!! It never did that before. What the hell is happening?????? Then I rebooted it, and now it shows 39%! How's that? I've no idea how to make it work, maybe it's the CM9 which doesn't work corectly with the battery controller, but I think that it's much more likely that the battery controller itself is faulty. Sometimes this happens, and this is a physical fault. Unfortunately, it's too expensive to fix, so I'll just probably have to get a new phone...

RomanKasp said:
Nothing helps. It's surely not related to incorrectly calibrated battery. I did 8-1-1 charge which DID help when I bought a Chinese copy of Samsung Galaxy S3 Mini (my wife is using it now, and it's working fine, battery life is very good). But my stupid phone doesn't react. Just 5 minutes ago, when I was talking to my friend, it still showed about 30% left, then it suddenly died and I even couldn't turn it on, even while it was charging, the red light was blinking. Then it turned on and showed 2%! But the most interesting thing is that now there's something else going on, which I've NEVER seen! Because when I looked at it after approximately 10 minutes, it showed 98%!!! It never did that before. What the hell is happening?????? Then I rebooted it, and now it shows 39%! How's that? I've no idea how to make it work, maybe it's the CM9 which doesn't work corectly with the battery controller, but I think that it's much more likely that the battery controller itself is faulty. Sometimes this happens, and this is a physical fault. Unfortunately, it's too expensive to fix, so I'll just probably have to get a new phone...
Click to expand...
Click to collapse
Well, I am suspecting a hardware issue, but only one way to find out ... go back to stock.
Doesn't have to be true stock, if you no longer have a nandroid of the original OS. MikTouch would work just as well, as the kernels are interchangeable. If you need a download for it, I can help out with that.

joel.maxuel said:
Well, I am suspecting a hardware issue, but only one way to find out ... go back to stock.
Doesn't have to be true stock, if you no longer have a nandroid of the original OS. MikTouch would work just as well, as the kernels are interchangeable. If you need a download for it, I can help out with that.
Click to expand...
Click to collapse
By the way, I wanted to install an upgrade - a different version of CM found here (the thread says it's stable enough) to see if a newer system can solve the problem. I found this "[ROM][Official]MyTouch4G Slide CyanogenMod 10.1 [P-21] | 2013-06-16" - but unfortunately, it doesn't work on my phone. It's getting installed, and then it says something like "Updating Android" and then "Starting applications" and just freezes. If you reboot it, it just stops at the CM10 logo. I had this before with CM 9 and wiped Dalvik cache (I think), then the problem went away. Here, no such luck. Doesn't help at all. Will go back (as I did a backup) to what I had. But it's a pity.

RomanKasp said:
By the way, I wanted to install an upgrade - a different version of CM found here (the thread says it's stable enough) to see if a newer system can solve the problem. I found this "[ROM][Official]MyTouch4G Slide CyanogenMod 10.1 [P-21] | 2013-06-16" - but unfortunately, it doesn't work on my phone. It's getting installed, and then it says something like "Updating Android" and then "Starting applications" and just freezes. If you reboot it, it just stops at the CM10 logo. I had this before with CM 9 and wiped Dalvik cache (I think), then the problem went away. Here, no such luck. Doesn't help at all. Will go back (as I did a backup) to what I had. But it's a pity.
Click to expand...
Click to collapse
Did you dirty flash, that is not wipe data before installing CM10.1? If so, that would be the cause.
If not, that's new for me. I used TBalden's CM10.1 for a year, never had a problem like that.

joel.maxuel said:
Did you dirty flash, that is not wipe data before installing CM10.1? If so, that would be the cause.
If not, that's new for me. I used TBalden's CM10.1 for a year, never had a problem like that.
Click to expand...
Click to collapse
I tried everything, including wiping data/cache/Dalvik cache, then installing the file, I even tried to install the GApps too. Nothing seems to happen. It just gets stuck in the bootloop. When you first turn it on, it stops at "Starting apps", then if you reboot it, it stops working at CM logo (bootloop). I waited for 10 minutes or more, no result. Luckily, I did a full backup so I went back to CM 9. Seems like my phone is simply incompatible with this mod. No luck for me here .

Moto G 4G freezing randomly, requires reset to power on (long/detailed post inside)

so yeah, my phone just freezes randomly at different time.
I believe it's freezing and then it just drains the power.
When I turn it back on, there's a gap in the battery life. Unfortunately, this time it must have happened really early and the battery drained to 0 and now it doesn't even power on.
This includes power + vol down with and without charger on for at least 1 or 2 mins, nothing happens. The notification light turns on when you plug it in.
I believe I do need to open it and unplug the battery then plug in the power, but I can't test it out because I don't have T5 torx around so it may take a while.
Anyways, I am not definitive on the freezing, it's just most likely scenario since phone becomes unresponsive randomly.
When it happens, plugging in power, power button, plug to usb/data does nothing. Phoning the cellphone gets user not in service. And powering back on I see the battery is drained.
This started happening like around a month and a half ago, I was using SaberRom. The rom was very stable until it this started happening.
I thought there was a bug in the Rom or something, so I made the jump to CM12. However it still continues to happen.
My only guess why this may be happening, software wise now, through the process of elimination is maybe Xposed might be doing something.
If it's not, then it could be a hardware problem, which doesnt make much sense to me since the phone is stable when I actually use it.
The freezing problem never happens while I use it, it usually happens over night or not in use in my pocket.
I started using logcat to try to keep a record, but I only have 1 record, plus 1 the most current one which I dont know if it even recorded properly since I can't turn phone on.

I personally would do a full wipe and flash stock ROM and kernel without Xposed. Until you do that you really are just shooting blind. Find out if the problem goes away and go from there.

n0ts0smart said:
I personally would do a full wipe and flash stock ROM and kernel without Xposed. Until you do that you really are just shooting blind. Find out if the problem goes away and go from there.
Click to expand...
Click to collapse
+100000²

outlook not so good
so i tried doing this
where you plug in the phone directly to power without the battery
for me, only the notification light turns on, the screen doesnt turn on

Database Info

welcome