Develop Bugs

Battery Problems (After Bricking??)

Alright so I've been doing research online this week and haven't been able to fix it so I'm coming to you guys. I'll give you a little background to hopefully help speed up this process.
So about 3 weeks ago I rooted my Sprint LG Optimus G after having it for almost a year to get some better performance and battery life out of it. After getting it all setup, I noticed a huge difference and was even able to watch the movie Flight and two episodes of Family Guy off Netflix and my battery still lasted 9 hours that day.
Well last weekend after uninstalling some Google apps I soft bricked my phone. Thanks to the help of sawdey21 on the IRC I was able to get it back up and running with LGNPST. After getting it running, I switched launchers (from Holo to Nova) and also unlocked mine phone via FreeGee with TWRP. Since then, my battery life has been terrible. To give you a reference it took my phone 8 hours to fully charge last night while it was off (although since I unlocked it I have a new charging animation and after a few seconds of the animation, instead of shutting the screen off like it use to it now just goes to a black screen but is still on as you can see the brightness. It never shuts off). After unplugging it, an hourly later I was down almost 15% after just listening to music and after 4.5 hrs its at 30% and I just plugged it in. Today I have done nothing but listen to music and just period check/browse my phone.
Is it possible that the bricking messed up my battery? Or the unlock? I switched back to the previous Holo launcher I was using before and it made no difference. I've also unistalled several apps I downloaded since the bricking I thought could be causing it.
Has anyone ran into this or could help? My next step is to boot back into Download Mode and try LGNPST again. I would post pics of Battery Settings, WakeLocker and BetterBatteryStats but I can't since I'm a new comer.
Thanks!

Different roms use a different amount of power...
Sent from my GT-P3100 using xda app-developers app

xSTUDDSx said:
Alright so I've been doing research online this week and haven't been able to fix it so I'm coming to you guys. I'll give you a little background to hopefully help speed up this process.
So about 3 weeks ago I rooted my Sprint LG Optimus G after having it for almost a year to get some better performance and battery life out of it. After getting it all setup, I noticed a huge difference and was even able to watch the movie Flight and two episodes of Family Guy off Netflix and my battery still lasted 9 hours that day.
Well last weekend after uninstalling some Google apps I soft bricked my phone. Thanks to the help of sawdey21 on the IRC I was able to get it back up and running with LGNPST. After getting it running, I switched launchers (from Holo to Nova) and also unlocked mine phone via FreeGee with TWRP. Since then, my battery life has been terrible. To give you a reference it took my phone 8 hours to fully charge last night while it was off (although since I unlocked it I have a new charging animation and after a few seconds of the animation, instead of shutting the screen off like it use to it now just goes to a black screen but is still on as you can see the brightness. It never shuts off). After unplugging it, an hourly later I was down almost 15% after just listening to music and after 4.5 hrs its at 30% and I just plugged it in. Today I have done nothing but listen to music and just period check/browse my phone.
Is it possible that the bricking messed up my battery? Or the unlock? I switched back to the previous Holo launcher I was using before and it made no difference. I've also unistalled several apps I downloaded since the bricking I thought could be causing it.
Has anyone ran into this or could help? My next step is to boot back into Download Mode and try LGNPST again. I would post pics of Battery Settings, WakeLocker and BetterBatteryStats but I can't since I'm a new comer.
Thanks!
Click to expand...
Click to collapse
I'm not 100% sure but it is possible the bricking messed with the battery. LGNPSTing back to stock could have affected it, anytime you flash a new rom it takes a couple of days to "settle in" but you said last weekend so it should be settled by now.
But from your info, it may be the way you are charging it. There is a common misconception that every so often you are supposed to let your battery drain fully and then charge to 100%. This is only true for nickel based batteries, ours is lithium so this is in fact quite detrimental. Lithium batteries are built to be charged often and you should never let it dip too far into the red. Doing so decreases the life and performance of your battery significantly. 5% is as low as I'll let my battery dip before charging and even that is pushing it imo. There is an app in the play store called battery calibration that actually tells you to do this, but like I said, it's only useful for nickel based rechargeable batteries. Also this same app's function is deleting the batterystats.bin file in order to "recalibrate" the battery. This is also completely false as that file has nothing to do with how well your battery performs.
I wouldn't turn the phone off to charge, just charge it while it's still on so the screen actually shuts off. Checking your wakelocks and using greenify on power hungry apps will go a long way. I also turn my capacitive buttons off because I don't need to see them to know left, right, center and what they do. And if I'm not using it, it is always off, sync, gps, brightness when inside, etc. But as I said, it may have been the way you were charging it, it might not affect the battery for months, then all of a sudden your battery doesn't perform as well because it's dying due to improper charging techniques. And when you LGNPSTed back to stock, your system tries to start fresh which is why it may have happened immediately afterwards.
I hope some of this helps you - if using greenify doesnt show improvement you may want to buy a bigger capacity battery and start fresh. Installing the new battery is tricky however, there are youtube videos on how to do it, but it may not be for everyone.
Good luck and I'm sorry if I assumed too much or misread your info!
EDIT: You may also want to try flashing a different stock kernel(I use Viper1.1, my signature has a link to the thread) and using trickstermod to undervolt the cpu. The improvement is minimal but every little bit helps. On average I get a full 24 hours in between charges and usually charge once it hits 10-15%. And it only takes about 60-120 minutes to fully charge.
However the lgog is also very fickle, what works for one may not work on another, even if it's the exact same model. Many people have reported the same security bootloop soft brick after deleting google apps for instance, but I deleted(not frozen or disabled) google apps just fine. The only ones I have on my phone are play store and google search and I'm still on stock zvc.

HPTesta,
Appreciate the response and all the info. To clarify a little more, I've never installed a custom ROM. Just been doing launchers from the Play Store besides having to do the LGNPST. As far as Apps I've been using greenify since I rooted 3 weeks ago as well as CPU Tuner which had both been doing great for me before this.
As far as charging goes, I generally never run my phone compleley dead. I usually charge when its getting low but last night I ran it complete lay dead to use Wake locker (read in the app store to drain bat, recharge full, and use after a couple hrs.
One thing I did find weird is that I don't remember how much battery I had when I bricked it but after doing the LGNPST I had 0 (Don't know if that's normal).
Also, never used the Battery Calibration app.

And based off what your saying would you not recommend doing LGNPOST again?

xSTUDDSx said:
HPTesta,
Appreciate the response and all the info. To clarify a little more, I've never installed a custom ROM. Just been doing launchers from the Play Store besides having to do the LGNPST. As far as Apps I've been using greenify since I rooted 3 weeks ago as well as CPU Tuner which had both been doing great for me before this.
As far as charging goes, I generally never run my phone compleley dead. I usually charge when its getting low but last night I ran it complete lay dead to use Wake locker (read in the app store to drain bat, recharge full, and use after a couple hrs.
One thing I did find weird is that I don't remember how much battery I had when I bricked it but after doing the LGNPST I had 0 (Don't know if that's normal).
Also, never used the Battery Calibration app.
Click to expand...
Click to collapse
Ok well it seems like you follow good battery techniques. Maybe try LGNPSTing back to a full stock zvc(or zvb and then updating to zvc) and charge it to 100%(let it sit at 100% while still charging for 15 mintues or so) before rerooting and unlocking. I would probably also copy your internal to your pc and wipe everything in recovery before doing LGNPST just to make sure it is a completely clean slate. I added an edit in my post above as well.
I had a strange issue a few weeks back where I tried overclocking my cpu with AK kernel - my battery was at 99%. My phone shut off and wouldn't come back on, just had a red blinking light. I later found out it was an issue with AK. I charged it for a few minutes and luckily was able to get into TWRP. The strange part was that when I did get into TWRP my battery read 0%, I did a full wipe and restored my backup, then my battery read 99% in TWRP. It's a different issue from yours but makes me think that it's possible that your softbrick and LGNPSTing affected it somehow.
---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------
xSTUDDSx said:
And based off what your saying would you not recommend doing LGNPOST again?
Click to expand...
Click to collapse
I honestly have not had or heard of any issues with LGNPST and battery performance. Anytime Ive had to use LGNPST with a full stock .bin, it essentially set my phone back to factory condition, battery performance included. However since this all happened when you did this, maybe try flashing another rom first, even a stock based one and leave LGNPST as a last resort. Just make sure you read the instructions for whatever rom you decide to test and always do a full wipe(data, cache, dalvik and system) before flashing.
EDIT: Sorry if it seems like I gave you conflicting info, if it was me I would probably be weary of using LGNPST again, personally. But if I tried flashing other things, different recoveries, roms and still had the same issue, maybe it was just a slightly messed up LGNPST flash and would try it again as a last resort.

Forgive my ignorance but I've never actually booted into twrp recovery. Its volume up and power but where do you go from their to wipe?

xSTUDDSx said:
Forgive my ignorance but I've never actually booted into twrp recovery. Its volume up and power but where do you go from their to wipe?
Click to expand...
Click to collapse
After holding volume up + power, you then will hit volume down twice and power again. Once in TWRP it is very easy, there is an install button, wipe button, etc. Hit the backup button, pick all available options and then do a backup and reboot into your OS. From there, download a rom(optimus DE is a great stock rom) to your internal and you will probably need gapps as well(depends on rom but almost all of them need gapps or you wont even have the play store - just read the install instructions of the rom). Go back into recovery, This is under the advanced wipe button in the wipe menu - wipe everything except internal storage(if you wipe internal you will lose your backup, pictures, music, etc) and then go to install, pick the rom.zip and flash that, then pick the gapps zip and flash that as well.
Also keep in mind that if you flash an AOSP or CM based rom, the file system will be different. Our internal storage is /data/media but for AOSP based it is /data/media/0. So say for instance you make a backup in TWRP of your stock then flash an AOSP rom, it will look as if your internal is gone as well as your backup. You will just have to use a root file explorer to copy the /data/media/TWRP folder to /data/media/0/TWRP and then you will be able to restore your backup from TWRP.
If you are just going to try LGNPST again then when you get into TWRP pick everything including internal and turn the phone off and put the phone into dl mode(you know what you are doing from there).
One final note, if you are using current FreeGee to unlock then you are most likely using the updated TWRP. Some people have had SEVERE issues with it, for others it works just fine. You need it to install any rom based on Android 4.4 but I personally use TWRP 2.5.0.0 which will flash stock to Android 4.3 roms just fine and it is rock solid stable. So unless you are planning on installing a kit kat rom, I would first download the TWRP 2.5.0.0 zip found here to your internal, go into twrp, pick the install button, find the .zip file and install that, then go to reboot in TWRP's main menu and choose recovery instead of system. TWRP should now read 2.5.0.0.
Sorry for the books I'm writing here but I think it's always best to be thorough!! And I haven't slept in about 30 hours so I am a bit scatter brained.

[Q] Reboot problem when not charging

I have had my P607T for a couple of months now. It is box stock no changes. Over the last few weeks I have noticed that it will reboot while using various apps. (Fliipboard, Chrome, Clash of Clans, Papyrus...) They don't seem to all be heavy graphics or network. The only symptom is that the screen starts to flash then "bang" reboot (and trouble rebooting when not plugged in). It would not be too annoying except that it will loose wifi settings and the wallpaper. I have tried different wallpapers (saw a thread blaming the live wallpapers ) Unloaded some apps (had another phone issue with FitBit and HTC blink on my N4). I stay away from CoC (my base has been raided so often now ...). Any thoughts? I am really trying to like this tablet more than my old ASUS Transformer but this reboot and reset wifi is a pain.
Thanks in Advance,
marka

manderson8898 said:
I have had my P607T for a couple of months now. It is box stock no changes. Over the last few weeks I have noticed that it will reboot while using various apps. (Fliipboard, Chrome, Clash of Clans, Papyrus...) They don't seem to all be heavy graphics or network. The only symptom is that the screen starts to flash then "bang" reboot (and trouble rebooting when not plugged in). It would not be too annoying except that it will loose wifi settings and the wallpaper. I have tried different wallpapers (saw a thread blaming the live wallpapers ) Unloaded some apps (had another phone issue with FitBit and HTC blink on my N4). I stay away from CoC (my base has been raided so often now ...). Any thoughts? I am really trying to like this tablet more than my old ASUS Transformer but this reboot and reset wifi is a pain.
Thanks in Advance,
marka
Click to expand...
Click to collapse
Have you tried a factory reset? I'd make tmobile replace it

was hoping to avoid the reset button. Tried it and still giving trouble it rebooted while restoring apps. I bought the tablet on ebay, I don't think TMO will take it back. oh well I'll keep poking about.
thanks,

I experience exactly the same problem since the update to 4.4.2 (kitkat): The screen starts to flash, suddenly the tablet reboots. I tried a factory reset multiple times, also removed the SD card and reflashed the ROM via KIES, nothing helped so far. Also, even when plugged into the outlet for several hours the tablet didn't charge at all (I think it stopped charging when the screen saver kicks in).
A couple of weeks ago I filed a RMA request (my dealer sent the tablet to Samsung), yesterday I got it back. It was charged at 60% and when I plugged it to the outlet it actually charged (even when the screen went off). But after about one hour (the battery was still > 60%) the flashing reappeared and after a while the tablet started to reboot again. Interestingly the battery now showed only 2% and the low battery warning appeared.
I think the problem might occur only when the battery runs low (which happens very fast as something seems to drain the battery), while android still shows a much higher battery level . Never experienced these problems when the tablet was plugged in so far.

Wall-E said:
I experience exactly the same problem since the update to 4.4.2 (kitkat): The screen starts to flash, suddenly the tablet reboots. I tried a factory reset multiple times, also removed the SD card and reflashed the ROM via KIES, nothing helped so far. Also, even when plugged into the outlet for several hours the tablet didn't charge at all (I think it stopped charging when the screen saver kicks in).
A couple of weeks ago I filed a RMA request (my dealer sent the tablet to Samsung), yesterday I got it back. It was charged at 60% and when I plugged it to the outlet it actually charged (even when the screen went off). But after about one hour (the battery was still > 60%) the flashing reappeared and after a while the tablet started to reboot again. Interestingly the battery now showed only 2% and the low battery warning appeared.
I think the problem might occur only when the battery runs low (which happens very fast as something seems to drain the battery), while android still shows a much higher battery level . Never experienced these problems when the tablet was plugged in so far.
Click to expand...
Click to collapse
At least I don't feel so alone with this issue... I have been paying more attention to my build up process since the factory reset. I found, the other night quite by accident, that when I logged in to Twitter the reboot started. So for the next few days I have left Twitter off the machine and it is doing better. I suspect that something is hitting the power drain (like you mention) and that causes it to have problems. In that thought I have also turned off the power saving mode and auto screen now just to add to the list of things I am avoiding.
Rgds,

manderson8898 said:
At least I don't feel so alone with this issue... I have been paying more attention to my build up process since the factory reset. I found, the other night quite by accident, that when I logged in to Twitter the reboot started. So for the next few days I have left Twitter off the machine and it is doing better. I suspect that something is hitting the power drain (like you mention) and that causes it to have problems. In that thought I have also turned off the power saving mode and auto screen now just to add to the list of things I am avoiding.
Rgds,
Click to expand...
Click to collapse
Have you considered rooting and using root apps to stop the apps from being able to do such things?

Android OS Battery Drain

Hi All,
My predicament appears a bit special. From my searches I haven't found anyone that is quite like it. My Tab S 10.5 in is brand new, I've only had it for a week. I've updated 5.02, and I don't really have any idea how the battery life was prior to that update because I updated it as soon as I got it out of the box (which to me, was a grave mistake now...).
My Samsung Tab S is draining battery, but it is draining because of "Android OS" keeping my tablet 100% awake. when I say 100% awake, I mean in the awake bar it is completely solid with absolutely no breaks. I am rooted, and have tried BBS and Wakelock detector and they give me the same information. Tablet is 100% awake, and never ever gears down to "Deep Sleep". There are absolutely zero wakelocks present, kernel or partial (which is peculiar, I don't know why they aren't showing at all, they used to show when I first installed BBS and activated root). However, a peculiar thing is this isn't 100% consistent. I've had the tablet for 6 days as of today, and only 2/6 days did Android OS do this massive drain. The latest drain was last night, where between 5:00PM and 4:00AM it drained 81% of its battery. At around 4:00AM suddenly the Tab went into "Deep Sleep". What is the problem?
Prior to going to sleep at 11:00PM~ I enabled every single Samsung app via the Application manager in settings. I suppose Samsung finally finished downloading and syncing all the bloatware and **** it wanted to do, and finally let my tablet got to sleep by 4:00AM.
How do I determine what is keeping my tablet awake? Obviously Wakelock Detector and BBS has been absolutely no help thus far. Is anyone else having this problem? I need this tablet to be more reliable. I can't exit my house at the beginning of the day, not use it at all and jsut have it at 0 percent by night.
If you are going to advise flashing a custom rom/kernel, I will be doing so in the near future (once I get something settled), but as of right now it is a no go solution. I want to exactly pinpoint what my problem is, so that one day if I do happen to remain stock I can actually deal with the drain.
Some may say it is the Google Play services bug, but I have tried using "Disable Services" app to prevent this, and no change so far.

Why not just factory reset or downgrade to kitkat?

I have a specific game that my gf was playing that needed to be cracked through the obb files.
I know I can backup the apk+save data as I've done it numerous times on my Nexus 5, but I'd rather not risk losing her save data due to corruption or whatnot.
Also avoiding 5.02 lollipop/factory reset "may" be a solution but is not guaranteed. I want to know precisely what is happening, so that if the same thing occurs along in the future I don't have to downgrade/factory reset to remedy it.

Do you have any alarms or timers set, also an syncs can stop your tablet sleeping.
Have you tried "Deep Sleep Battery Saver" it controls the cpu and forces it to sleep when you tune the tablet off, it need root to work.
https://play.google.com/store/apps/details?id=com.rootuninstaller.batrsaver&hl=en
John.

I don't recall setting any alarms/timers. BBS also does not indicate any Alarms in the alarms section.
Sync has been turned off.
I tried Deep Sleep Battery Saver already on aggressive mode, no change (at the time).
Like I said, my tablet suddenly was able to deep sleep after 8 hours... I'm just thinking of alternatives to try when the drain returns since it has visited me twice.

I would install the free watchdog app and use setup to include all processes and wait for any apps to use a lot of cpu power and it will sound an alarm, you can whitelist any games or app you dont want it to monitor.
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite&hl=en
I lost lost 30% in 3 hours while my tab was in it`s case during the night, luckily i had an battery monitor app set to check for high battery temps and sound an alarm, else my battery would of been flat by the morning.
EDIT: My 10.5 has never been rebooted or turned off since i got it, the battery manger says it`s been on for 157days.
John.

My advice is to do a full back up with twrp and titanium backup(to the sd card)
Factory reset then see how it goes. If the issue is gone you know where the problem lies. Add back your apps in gradual fashion with titty backup and see if any cause the issue.
You could always restore everything if there is no change.

EDIT : CRAP - Somebody on this forum suggested to use Helium to do a backup, never tried it, but i bookmarked it just in case i need it.
John.
QUOTE=ashyx;60323930]My advice is to do a full back up with twrp and titanium backup(to the sd card)
Factory reset then see how it goes. If the issue is gone you know where the problem lies. Add back your apps in gradual fashion with titty backup and see if any cause the issue.
You could always restore everything if there is no change.[/QUOTE]

ashyx said:
My advice is to do a full back up with twrp and titanium backup(to the sd card)
Factory reset then see how it goes. If the issue is gone you know where the problem lies. Add back your apps in gradual fashion with titty backup and see if any cause the issue.
You could always restore everything if there is no change.
Click to expand...
Click to collapse
+1 on this. Never used Helium but Titanium backup has been flawless for me. I would highly recommend that instead.

I was trying to avoid a full wipe. I've done backing up with Titianium Backup and ES File Explorer numerous times on my nexus 5.
Thanks for the input guys. I will try the Watchdog app as well.

The full wipe is just a test . It'll take only a few minutes to do a full device backup with twrp.You can then restore at will and be back to where you started. Anybody who has a custom recovery should have at least one full backup.

ashyx said:
The full wipe is just a test . It'll take only a few minutes to do a full device backup with twrp.You can then restore at will and be back to where you started. Anybody who has a custom recovery should have at least one full backup.
Click to expand...
Click to collapse
Exactly. One of the first things I do with every phone or tablet i purchase is root, install TWRP and take a full nandroid backup as well as install Titanium backup and backup everything. I know it may be a bit over the top but it ensures I can always get back to a clean slate or restore original state of apps. Highly recommend this as it will allow you to experiment and then return to last known state if you mess something up. If you do this, you really have nothing to lose.

As an update and for reference, the Android OS drain wouldn't stop. When I got home from work yesterday and unplugged @ 5:00PM battery was at 100%. With almost zero use, the battery had completely discharged by 4:00AM in the morning, and was overheating like crazy at 100% awake time. I couldn't take it any longer and had to do my wipe.
Things to note if someone could elaborate:
1) Prior to my wipe, I noticed that there was several issues with storage. I could not take screenshots due to "Unable to save screenshot due to storage space, app permissions or your organization", which none of the above is true. Why did this occur?
2) Prior to my wipe, I tried downloading a ROM via Chrome browser and the error "Download unsuccessful" appeared. I tried downloading the same ROM via Opera browser and it would download, but hang at 100% and I could not even find the file anywhere on my internal/external storages. Why is that?
3) I did a factory reset via TWRP. The first bootup after factory reset had me seriously worried as I thought my tablet had bricked. It took almost 5 minutes or so just to boot up. It was all fine and dandy - except the wakelock was still present. My tablet stayed awake for the entire 5 minute duration I tested (which is a small sample size and is a totally unfair sample, but I didn't have the patience to see my battery heat up due to 100% awake time). At this point in time, the screenshot function is now working again.
4) I proceeded to flash IronMan ROM, and wiped dalvik/cache right after the flash. What was extremely peculiar to me was that after my dalvik/cache wipe, the tablet rebooted instantly itself. I've never had TWRP do that. Every time I did a dalvik/cache wipe, it always informs me that the wipe is successful, and that I can go back to TWRP for more options. The reboot was unsuccessful as well, and hanged at the "Samsung Tab S powered by Android" logo, and wouldn't even proceed to the Samsung logo.
5) I rebooted into TWRP, did a factory reset cause I assumed there was something buggy with the IronMan ROM. When trying factory reset, an error popped up saying E/could not mount cache. The reset still proceeded though. Did a reboot after the reset finished and the same first boot took almost 5-10 minutes thinking my Tab S is bricked. It finally booted, and it appeared that the factory reset via TWRP didn't restore the tablet to Lollipop stock (which I assumed it would...). It was on IronMan ROM. Does anyone know how the factory reset works on TWRP? Should it have been Lollipop?
6) I rebooted just to check the boot time, and it rebooted in the normal 15 second span about so that's good. Screenshot function was still working. And most importantly....the tablet in just a 5 minute test deep sleeped for 4 mins and was awake for the 1st minute i was using it. Even after a 50 minute test, it deep sleeped for 45 minutes and was awake for 5 minutes. Which leads me to believe there is some sort of bloatware on the stock that Ironman removed, and is finally letting my tablet go to bed.
Can someone answer the plethora of questions in my procedure?

Phone will not wake from sleep, needs reboot, massive battery drain

So, a few things: First, I used Sunshine on my phone last Wednesday to put the newest T-Mobile firmware on my phone. Prior to doing these two things, this problem did not exist. I am on ViperOne 3.5, chose T-Mobile as my carrier and was very careful in setting things up.
First two or so times I would notice my phone was not waking up, so I held down the power button to restart and after it turned on there was a very large battery drain (30-50%). After this I decided that maybe the firmware was the issue, so I fastboot flashed a fullwipe version through fastboot (originally I had done a no wipe flash) and restored backup nandroid from TWRP. After that the problem persisted, so I thought maybe it was a rom conflict and did a clean install of Viper 3.5, thought everything would be good but while in the car it did it again. This time I caught it quick (I had used my phone maybe five minutes before and when I restarted the battery drain was less than 5%. But seeing as I've done a clean install of both the firmware and the rom now, I'm sort of at a loss for what to do.
Has anyone heard of this, or would anyone have tips on what to do? Can provide additional info if needed, just want to get this worked out. I've been lucky so far and it's done it while I didn't need power. If it were to do it during work when I can't check the phone for a while, it could lead to the entire battery being depleted.
::EDIT:: I should also add that this happened once when I was asleep, and I found that the phone would not charge when in this state, as the orange light was not on when I woke up and I had to reboot the phone. Again, extremely weird and it only started after Sunshine and firmware change, nothing else.

This "sleep of death" thing has happened to me a few times, though I have not seen the battery drain. I have not figured out what is causing it.

iElvis said:
This "sleep of death" thing has happened to me a few times, though I have not seen the battery drain. I have not figured out what is causing it.
Click to expand...
Click to collapse
I actually just caught it and tested some more out. Tried plugging it into a wall and it won't charge. Also tried plugging it into a computer and it will not recognize. The only two things I have changed are the firmware version, and running sunshine through it. I'm actually pretty worried since it won't even interface with a computer until rebooted. Also went from 90ish% to 77 in a matter of 15 or so minutes

Random Reboots (Unable to receive call, after reboot loop at boot loader) SOLVED

After having headache with this problem for last one month and lost hours of testing, i finally found a problem so lets explain symptoms, maybe it will help someone.
I am using CM since first version and as all nightly version have some bugs i had them as well. So i had random reboot from time to time and i thought it's just CM bugs.
For last 1 month reboots happen most often and always when i receive or make a call.
Phone just reboot and loop at boot loader. After removing battery for few seconds phone can normally boot.
3 days ago phone started to reboot even with some heavier app's but never if i disable network. Reboots start to happen even if phone is in my pocked and i exit elevator (drop network and get again).
I tried clean installation of CM12.1, Clean installation of CM13, Wiping internal storage, Clean installation of Cloudy ROM, Removing SIM card, removing SD card i even moved back to stock ROM.
Installed more then 30 app's for monitoring everything and noting show any error, problem etc. While doing all this, i realized that this problems never happen when phone is at charger. Again, installation of 20 apps for battery calibration, voltage monitoring, logs etc. and non of them showed any problem.
Battery was regullary fully charged but noticed that it happen only with heavier usage (have call, copy bigger file, start game).
After doing that tests for entire day, phone refused to pass boot loader with battery but boot normally with charger.
So i purshesed new battery last night, phone booted normally, there is no reboots or any issue at all. Now i can compare that new battery is better since it lost only 1% of battery over the night but old battery didnt show up any problems at all. It's normally to not be that good after 1 year of usage but I didnt had any drainings, it was regularry charged etc.
So if you have similiar problem, to go to some service where you can try with new battery before buying one.

I have the exact same problem .
It driving me crazy! I will try to get new one, and reply as soon as possible ! I hope it will work.
the phone just showed me that The battery that I was using it for one year is fake -_-

Yep, same issues, phone was rebooting sometimes (at the begin, only a few reboots, only during the launch of "big" activities like GPS, or photos) then a few weeks later
I needed to connect it to the charger otherwise, after a few seconds, the phone used to reboot in loop... Until it dies...
Buying a new battery resolved all the issues, no more reboots at all