I've been trying hard to avoid the Epic update, since my phone was working great. I was getting almost 20 hours battery before being asked to charge, using about 30 minutes phone calls, 1 hour "display on" time, bluetooth/wifi off, GPS only when needed.
The nagging update available message would always pop up, and I'd always tell it to install later.
Somehow, I must have accidentally selected update while getting out of the car today, since I saw the phone installing firmware and then reboot.
After the reboot, my Sprint Hotspot stopped working. Now when I activate it, it turns my 3G radio off. Prior to this, I could activate (and use) Sprint Wifi tethering even though I am not specifically subscribed to it. Now, it still "activates" but shuts down my data connection.
Even worse, when I try to activate 4G, it just hangs the phone. I tried factory resetting, which did not solve the problem. Still no more 4G. Also, I noticed my battery getting really hot, and the smell of smoke inside the case. The battery went from 50% to 9% within a minute!! I don't have any explanation on how the update caused this.....
This update fried my phone! I'm going to try the Odin method back to DG27. If that doesn't work, the phone is going back!
DO NOT UPDATE if you can avoid it!!
that sucks
I'm having a really really hard time believing the ota update had anything to do with anything you described.
Sent from my SPH-D700 using Tapatalk
styckx said:
I'm having a really really hard time believing the ota update had anything to do with anything you described.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Me too, but I don't know what else could have caused it. Just tried Odin, still can't get 4G to work.
I don't think there's much else I can try. The phone just hangs when I enable 4G. Tried factory reset, Odin back to DG27. No luck.
Any ideas?
Dont listen to this guy -- you want the DI07 update on your phone. It has vital improvements to the radio and kernel. It doesn't break 4G or ruin battery life.
it has happened to many of us,including me..i also started a thread in the development forum..i talked to a service rep and they instructed me to do a msl reset,which required a msl code the give and no luck..this happened to me last week.since then i swapped my phone for another unit an was weary of updaing again,but i did and everything works fine now.im guessing a bad batch of phones or bad dowload/install of update ota.return it for another
Sent from my SPH-D700 using XDA App
Before the update, I was getting about 14-15 hours of battery with my average daily use. After the update I'm swapping batteries every 6 or 7 hours. I started tracking power consumption a few days ago with Spare Parts. I flashed back to stock with odin, and installed the DI07 update. The only apps I installed were Battery Indicator Pro and Spare Parts. I noticed right away that the running time was always close to 100%. That means that the phone is not sleeping. Under "Partial Wake usage", Android System is running almost the same amount of time the phone is powered on. It's not spiking the CPU, but running just enough to create a partial wakelock. This behavior is consistent on every boot. Normally, Android System should only keep the system awake about 3 or 4 minutes per hour of uptime at most. I think they botched something in the update.
Tonight I reverted back to DG27 and the problem is now non-existent. I only have one Epic to test, so I'm curious to see if anyone else gets different results. If it's just my Epic, then I will be returning it for another.
Anyone feel like experimenting?
I'm going on 18 hours now since I reverted back to DG27 and I'm still on the same battery. I would be on my third battery right now if I was still running DI07. I don't think I'm gonna be updating till Sprint releases another fix. Other than Media Hub and the loss of battery life, I noticed no changes while running DI07.
Sent from my SPH-D700 using Tapatalk
I'm getting over 18hrs since update. It maybe just like the HTC phone when you flash the rom the battery life goes down for the first few full charges then after that it's fine. Maybe I'm just lucky because I'm not having all the drama you guys and others are having.
infamousjax said:
Dont listen to this guy -- you want the DI07 update on your phone. It has vital improvements to the radio and kernel. It doesn't break 4G or ruin battery life.
Click to expand...
Click to collapse
Any why should we listen to you? Can you describe your source of knowing how this update has "vital improvements" to the radio and kernal? What are the nature of these improvements?
Thanks
-Everyone
Not sure what the particular improvements are... but check your phone info and you will see that the baseband was changed, which means a new radio was implemented. Also, in the release notes it specified that there were some "Qualcomm Updates", and since Qualcomm engineers the radio in our phones, it doesn't take much brain capacity to put 2 and 2 together.
I've updated and have experienced none of these problems. (As I suspect is true of most of the people here.)
infamousjax said:
Dont listen to this guy -- you want the DI07 update on your phone. It has vital improvements to the radio and kernel. It doesn't break 4G or ruin battery life.
Click to expand...
Click to collapse
It ABSOLUTELY ruins battery life. If it doesn't ruin your battery life specifically, then your one lucky sun of gun. It cut my battery life in half. I used to be able to go to 11pm and never even get a battery warning! Now, my phone completely shuts down by late afternoon while I'm still at work. DI07 is a horrible update. I don't know what Samsung/Sprint did, but my screen is dimmer, battery life took a major dump, and the phone does not seem any faster, actually slower if anything. My phone also seems to be hot all the time, even after it's supposedly been asleep for hours. With DG27 it was always felt cool when pulling it out of my holster and not hot like it is now.
Testing...testing
After running DG27 for almost 24 hours with great results, I decided to give the DI07 update another shot. But first I made a Nandroid backup in CWM before I accepted the update. After about two hours on DI07, it was clear the phone was not sleeping again when the screen was off.
So now I'm gonna try another experiment. I've done a system restore from my Nandroid backup to DG27. Except that the Baseband(radio) is still DI07 because Nandroid doesn't touch the radio. I'm thinking that this will tell us if the new radio is the culprit, or if they just botched something in the DI07 ROM.
Dev's, let me know if I'm off base here. I will report as soon as I have any relevant results.
compujock said:
It ABSOLUTELY ruins battery life. If it doesn't ruin your battery life specifically, then your one lucky sun of gun. It cut my battery life in half. I used to be able to go to 11pm and never even get a battery warning! Now, my phone completely shuts down by late afternoon while I'm still at work. DI07 is a horrible update. I don't know what Samsung/Sprint did, but my screen is dimmer, battery life took a major dump, and the phone does not seem any faster, actually slower if anything. My phone also seems to be hot all the time, even after it's supposedly been asleep for hours. With DG27 it was always felt cool when pulling it out of my holster and not hot like it is now.
Click to expand...
Click to collapse
Heres what will help:
Run the root script, delete all sprint bloatware, and keep track of all the services running on your phone. I'm getting 20 hours of battery with heavy usage on the DI07 update.
Also, try the bump charging method which has helped me a lot. Turn the phone on, let it fully charge, unplug, let it fully charge, turn back on.. rinse and repeat. It helps.
The update is not what is causing bad battery life. The screen dimming is part of the auto-brightness setting and/or power saving setting which should be helping the battery more than killing it.
Get System Panel/spare parts or any kind of task manager to MONITOR (not kill) processes running on your phone.
Here's a post from another forum, so I'm not the only person with a dead 4G radio. I believe it was temporally related to the update, but reverting back to DG27 didn't fix it.
Link: http://forum.androidcentral.com/sprint-epic-4g/36985-4g-doesnt-work-after-di07-update.html
"I have been out of town in a non-4G area since applying the DI07 update. Got home earlier today and just went to turn on 4G and it no longer is working!!
When I enable 4G (through the pull-down or the settings menu) now it just says "On..." and then "Unknown..."
Anyone else that has applied the update and lives in a 4G area seeing similar behavior?? I am currently backing up me SMS messages so I can do a hard-reset to see if that will fix it."
infamousjax said:
Heres what will help:
Run the root script, delete all sprint bloatware, and keep track of all the services running on your phone. I'm getting 20 hours of battery with heavy usage on the DI07 update.
Also, try the bump charging method which has helped me a lot. Turn the phone on, let it fully charge, unplug, let it fully charge, turn back on.. rinse and repeat. It helps.
The update is not what is causing bad battery life. The screen dimming is part of the auto-brightness setting and/or power saving setting which should be helping the battery more than killing it.
Get System Panel/spare parts or any kind of task manager to MONITOR (not kill) processes running on your phone.
Click to expand...
Click to collapse
Infamous,
These are all good suggestions for basic power management under normal circumstances, but for some reason this update has introduced an issue that causes the Android System process to prevent the phone from sleeping. Why it's not affecting everyone I don't know. Some people had to take their phones back to the Sprint store after the update because they got so hot and would not cool down unless turned off.
Anyway, if you are getting 20 hours on heavy use, you obviously don't have the bug. But to anyone who thinks they might, you can check using Spare Parts.
First, if you've just rebooted, turn the screen off and let it sit for a few minuets. Open Spare Parts and click Battery history. By default it displays 'Other usage'. If your 'Running' percentage is 100% or close to it, and your 'Screen on' percentage is anything other than your 'Running' percentage, then your phone is not sleeping when the screen is off.
Next change the top tab from 'Other usage' to 'Partial wake usage'. This will show you what is preventing it from sleeping. You can click on whatever is at the top of the list to see its partial wake time. If it's 'Android System', the partial wake time should not be any more than about 1 minute per hour of system uptime. For example, if your phone has only been on for 10 minuets, and 'Android System' has a partial wake time of 2 minutes, you have a problem.
Found more info here.
http://forum.androidcentral.com/sprint-epic-4g/37034-those-batt-issues-after-upgrade.html
This is great info, according to Spare Parts and your info, I have a severe problem. I have just killed DRM
The update went through automatically Sat night, battery has dived at least
50%. Reboot at that time.
Battery History
Total in all Time Since Reboot (2 days)
Running 30.5% 99.7
Screen On 16.7 18.3
I see the problem, don't know if DRM dead will fix, is there anything else I can do?
I am rooted (or at least I was, I stayed stock and added Wireless Tether, it is broken). So not happy there either.
I will charge and check this tomorrow to see what changes or if there are any other suggestions.
Thetwo apps running none stop are I! Agent Service in Android System and GTalkService in Goggle, using over 10 mb ram
Other usage is still almost 100%, Screen time has gone down, but Wifi On is same as Running and I have it turned off every which way I can find as with nothing showing on top bar.
Partial Wakelock: Andoid System is on 113 hrs of25 since boot.
I was previously running andybones' rom from 2.41.605.12 base, then found my way to resurrection remix, great rom, but some update last month killed my battery life and my ability to quick charge, phone was also in constant awake state, but I do not believe the issue was ROM specific. Either way, ran a battery stats report and it appeared that my motion sensors were keeping the phone awake. I completely wiped everything and RUU'd back to 1.19.605.9 (launch firmware), battery drain went away, rapid charging came back, phone would sleep. Performed some OTA updates and everything was fine until it got to the final version of MM 1.85.605.9, rapid charging gone, battery drain back, updated all the way through nougat and nothing changed, still draining.
I am currently back on 1.19.605.9, rooted, twrp installed. Rapid charge and no excessive drain.
What could possibly be causing this? Is anyone else dealing with this?
Here is my post with my last battery stats log
I'm currently dealing with the same thing.
Update: Ran an RUU of 2.41.605.36, then did a full wipe and installed santod40's [ROM][STOCK] 2.41.605.36, chose full wipe, unencrypted install, did some debloating of vzw software... and somehow, I have rapid charging and no wakelock drains...
I have ruu'd before and never resolved the issue. I am not sure what changed in the last RUU for me, but it worked.
...and it's back... lol
rcharliesam said:
...and it's back... lol
Click to expand...
Click to collapse
So I can't see the full log on my phone, but my phone is having a similar issue. I'm wondering if it's the same as yours. Under partial Wake Locks for BetterBatteryStats it shows NfcService:mRoutingWakeLock runs ALL of the time so my phone never goes into a deep sleep.
sublimesed said:
So I can't see the full log on my phone, but my phone is having a similar issue. I'm wondering if it's the same as yours. Under partial Wake Locks for BetterBatteryStats it shows NfcService:mRoutingWakeLock runs ALL of the time so my phone never goes into a deep sleep.
Click to expand...
Click to collapse
To be honest, I didn't even bother getting too deep in to it this time, I ruu'd back to an mm version that I know I don't have this trouble on. 1.85.605.8, and then used santod's debloated 1.85.605.9 after wiping and formatting data. The first time I had the issue, it appeared to be the accelerometer that wasn't allowing the phone to go to sleep... When I looked at the battery stats this time, it didn't seem to be my issue.
If you're s-off, you can downgrade. As much as I would appreciate certain features of nougat, it's not worth it if I have to be attached to a charger all day.
Not sure if it's an issue that carries over with my Google backup, next time I try, I might just do a fresh start and install apps one by one to see if/when it starts.
So, I have been using the Moto G4 Plus ( Indian Variant -XT1643 ) for a quite few months. Then 1-2 months ago, I rooted it, first with superuser and then replaced it with Magisk. I am using ElementalX kernel. But then after some days , the battery started acting weirdly. It drains very quickly. Also if I charge the phone fully and then reboot in bootloader , it drops to 15-16 . Sometimes the phone switches off at 10% battery. Even in idle, the battery drains very fast. When charged to 100%, the battery page of settings shows something like 45-55 mins left and that too varies. Currently on 56% it's showing 51 mins left. It's just 1 hour ago when I charged my phone to 100%. Is it time to replace the battery or is it a software issue as it drops to 15% in bootloader even if fully charged. Any help is appreciated. Thanks in advance.
I have the same problem but only with magisk, wih SuperSU everything is ok ?
Alright, I will try with SuperSu and update you. Thanks for the help.
Its software issue, may be ex kernel, magisk, supersu or any other app is draining it. Use better battery stats or similar like it and see who is sucking your battery juice.
And as you have already rooted your phone then try any custom rom as they dont have its problem (some may have also). And if wanna stick to stock rom then reset your phone and root it and then use for a while you will get the difference from before and now.
DgnrtnX said:
Its software issue, may be ex kernel, magisk, supersu or any other app is draining it. Use better battery stats or similar like it and see who is sucking your battery juice.
And as you have already rooted your phone then try any custom rom as they dont have its problem (some may have also). And if wanna stick to stock rom then reset your phone and root it and then use for a while you will get the difference from before and now.
Click to expand...
Click to collapse
Ok. Its good to know that it's a software issue. I already tried factory reset but it didn't help. Strangely, the battery is fine now. I drained it completely and charged to 100%. Maybe that might have reset the battery stats or something. Anyways , if the problem still persists I will try custom ROM. Thanks a lot.
Niketan Gulekar said:
Ok. Its good to know that it's a software issue. I already tried factory reset but it didn't help. Strangely, the battery is fine now. I drained it completely and charged to 100%. Maybe that might have reset the battery stats or something. Anyways , if the problem still persists I will try custom ROM. Thanks a lot.
Click to expand...
Click to collapse
Hmmm, I never had battery drain issues while using ElementalX kernel rooted with Magisk (14.0).
At least not while using Motorola stock Nougat with the above.
Maybe your battery just lost its calibration as you assumed.
Hi.
Yesterday I was using my Nubia z17s as always and before going to bed I decided to charge it, since battery was at around 20%.
When I connected the charger, the screen went off and it didn't wake up, no matter what I did, although I could feel the fingerprint scanner vibration when I used any of the registered fingers. So I decided to hard reboot the phone by keeping the power button pressed.
To my surprise, when the phone booted again, the battery percentage showed 3%. I left it charging overnight and now it's working but the battery percentage is stuck on 3%. I'm pretty sure it's more than that, since I've been using the phone for more than 6 hours and the battery percentage hasn't dropped a bit, and the phone is working (I've made an received a few calls).
A guy at work suggested letting the battery drain completely until the point the phone shuts itself down, and then charging the phone up to 100% while off, so the battery is calibrated and the percentage is fixed. But I've always heard that it's not a good idea to let a battery drain so much. Another problem is that I fear not being able to charge the phone again once the battery gets below 3%.
Any ideas? The phone is running latest Mokee 9 Premium.
Thanks in advance.
Remove "batterystats.bin" in the System folder
Tomcar said:
Remove "batterystats.bin" in the System folder
Click to expand...
Click to collapse
I had already tried that. But deleting that file just resets the battery usage statistics. It has nothing to do with the battery percentage
It seems to me that you will have to make a full data backup and perform a factory reset.
ps and which firmware in use?
Hi, I forgot replying.
I finally got the phone up and running again, and the issue seemed to be firmware related.
I was running the phone on Android Pie based Mokee ROM. I finally let the phone discharge until it shut down and charged it while off. Battery got up to 100% and the phone seemed to work fine. But, a few weeks later, something similar happened again, so I reverted to the stock firmware (still stuck at Android 7.1.1) and the battery issues went away.
I recently tested the Android 10 based Mokee and found that it reports battery level very differently than the stock firmware. Before flashing TWRP and the Mokee ROM, the phone was showing 88% battery left. Just after booting Mokee, the phone had apperently dropped to 78% and I also felt quite a huge battery drain. And it had only taken me around 5 minutes to install the recovery and firmware. So I guess the Mokee firmware doesn't handle the battery very well on Nubia z17s. It's a pity, since all the rest works very well, and I quite liked the Android 10 experience. On the other side, I was unable to make Magisk work under Android 10, and Google Pay is a must for me now, so I once again went back to stock firmware.