This past week, I purchased a 2014 Note 10.1 off Craigslist. I did check it out before buying it, and the device is in pristine condition, including the screen. It booted fine, and I went partway through the setup (the guy had factory reset it) before closing the deal. It is the wifi-only model, 3G RAM, 8-core Exynos version. It's white if that matters.
Anyways, a while later when playing with it some more, completing setup, etc, it just died on me. I wasn't home, and didn't have a place to charge it until I got home, but just figured that despite the device having said the battery was 99% charged, the guy keeping it unused for a long time might have thrown off the battery calibration. My understanding is that a Li-ion battery has one or more cells, plus circuitry that protects against overcharging and undervoltage conditions, as well as tracking the current charge state. With lengthy non-usage, the circuitry's idea of the current charge can get out of sync with reality, so I figured a few charge-discharge cycles would get it back in shape.
However, the situation after I got home turned out to be a little more complex. If I plug in the device to a power source with enough current (like the charger it came with, or my 2.1A USB outlet by my bed), it will run just fine while plugged in. However, upon unplugging, it would die quickly. Naturally, I assumed the battery was probably shot, so resigned myself to spending $50 on one. This is where it started to get a little weird. It seemed that when I booted into either fastboot or Odin mode, it would stay on much longer than normal, while unplugged. I'm talking hours, rather than between several seconds and several minutes while booted into the OS proper.
This lead me to believe that perhaps it wasn't my battery itself, but rather a glitch in the OS that was causing it to shut down. When I say shut down, I mean an immediate full-off state, not a nice shutdown or one preceded by low battery warnings. It just clicks off like a light that's been turned off. However, trying several different firmwares, including a couple custom ones, has not yielded any improvement. The issue remains.
The device was stock 5.1.1 when I bought it. I tried flashing KitKat (various images downloaded from SamMobile), but for some reason, it would still say it was running 5.1.1. I tried xKat, as in this thread. That results in 4.4.2 with the associated customizations, but the shutdown issue remains. I tried CyanogenMod 13, as instructed here. It works fine, notwithstanding the same issue. In between the stock firmwares (pushed to the device with Odin) and the custom ones, I would do a full wipe through TWRP.
I've popped the back off, disconnected the battery, waited a bit, and reconnected it.
Now my question: does anyone have any idea what's going on? If it's a dying battery, then why does the device say it's got a nearly full charge, and why no low battery warnings? Why would Odin mode or recovery (TWRP now) seem to keep the device powered up so much longer? Sure, they draw less power, but hundreds of times less power? I doubt it. If it's some hardware issue with the chipset/motherboard/etc, then why does it only manifest when running on battery, or a low-current USB connection? If it's an issue with Android itself, then why does nobody else seem to have this issue (googling revealed nothing that matched my symptoms), and why did several different versions exhibit the exact same problem?
I really don't want to spend money on a new battery and wait a few weeks for shipping if there's something else I'm missing that could get my device functional for free and a lot faster.
My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off. I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again. For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing. For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Sent from my SM-P600 using XDA Premium HD app
Thanks for your reply.
siralsmooth said:
My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off.
Click to expand...
Click to collapse
That's a bit different from my issue. Even when the device reports full charge, if I unplug it, it usually dies within seconds, and always within 2-3 minutes.
siralsmooth said:
I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again.
Click to expand...
Click to collapse
I don't think that's going to make a difference for me. From what I was reading, all it does is delete the batterystats.bin file (hence the root requirement), which doesn't have anything to do with calibration for most devices. It just contains the stats for how much battery drain various things have caused, during this 'running on battery power' session. It's also reset every time the device is charged. Read here for more info.
Furthermore, even if this were not the case, I'd conclude that wiping the system partition (indeed, all partitions except recovery) would have cleared this data.
Still, that said, it's conceivable (though exceedingly unlikely) that some of these calibration apps might do something else, such as talk to the battery circuitry at a low level. Since I've got nothing to lose, I will probably give a few of them a shot. Do you happen to know which one it was that you tried?
siralsmooth said:
For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing.
Click to expand...
Click to collapse
In my case, the values seemed to track pretty closely, and with numerous freshly-flashed versions exhibiting the same issue, I'm pretty sure at this point it's not a software glitch. I've resigned myself to ordering a new battery. I just wish I was certain that it would fix the issue.
siralsmooth said:
For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Click to expand...
Click to collapse
My understanding is that the bootloader doesn't change with flashing. I might be wrong though; is there a way to check the version?
Just a heads up. I ordered a new battery, which arrived yesterday. It seems to have completely solved the issues I was having.
My guess is that Android itself monitors the battery more diligently, and takes a more conservative approach to preserving battery life by shutting down when the voltage drops too low, while recovery mode would just let it run down completely flat (not good for Li-ion cells).
It's a moot point now, because it all seems good.
Related
Hi all,
I have been running my Z1 Compact on 4.4.4 for the longest time, mainly due to sound issues after updating to Lollipop.
Recently, the battery has been dropping randomly from 60 odd percent to 3 or 4 and then shutting down all within a few seconds. The last time it did this, I tried charging it when I got home but the charging light would not stay on, thus it was not charging. All typical signs of battery failure due to age.
Having already replaced the battery successfully on my Z1, I bought a replacement original Sony battery and replaced it. The problem persisted. On first boot, the phone got to the blue waves then black screen, and power off. Charging screen just showed the battery at about 40%.
I risked it and flashed the latest software with Flashtool, having done a complete wipe. The result of this proved no better, but I did get a different message on the charging screen, a message saying the phone had shut down due to overheating. Picture is attached.
The phone is in no way overheating and I've even booted it while sat on a shelf in the fridge to help dissipate any heat generated but with no luck.
So, the old battery maybe did overheat and caused the phone to shut down, I'll accept that as a probability. It may have even damaged something, but I don't think that's likely.
After changing the battery, I would have expected the problem to resolve itself, but it seems like some kind of hardware 'flag' has been raised that is now not allowing the phone to boot in case it overheats again.
Does anyone know of any way to resolve this, reset the 'flag' per se, other than going to Sony? The phone is definitely out of warranty due to its age, never mind me taking the back off lol
It is a shame because it has been a great phone over the years, and I would like to fix it if possible, even if to give it to one of the grandkids. I have my Z3 still (which I won't part with for anything) and I have an XZ too and both are great phones. I would just like to save the XZ1c if I can.
The phone is not, and has never been modified in any way, no rooting, no bootloader unlocking. Only stock roms have ever been flashed, and then only once or twice, to put it back on 4.4.4.
I have tried reflashing just the kernel, or just the system too, to no avail.
In desperation I even left it in the fridge for a few hours in case the temperature sensor was on the fritz, but that did nothing at all.
I just feel like there's nothing actually wrong with the phone, apart from this trigger that won't reset.
Any help greatly appreciated of course.
Thanks,
Mick
Maybe theres lot of consideration:
1. Rom Bugs
2. The Kernel not supported well
3. Battery Issues (But you already change it right)
There are two temperature sensors afaikin our phone. One in the SOC and another one in the battery (hence three pins).
The battery is probably the one giving the high temp report. Try yet another battery.
A bad battery normally heats up very fast inside and the battery temp sensor stops the battery from charging and/or working to protect the phone and the battery.
I changed my battery before when it had symptoms like yours 100-90-0 drop and after replacing with a battery from eBay it was OK. I gave it a full charge then complete discharge and then complete charge to full cycle the battery once and let the phone Guage its full capacity. one year later now my battery is acting funny again (not charging past 30%) and getting so hot when charging it triggers overheat control service in Android.
Any luck?
Apologies for the necro. But did you ever fix this issue, having the same problem
Karter Ires said:
Apologies for the necro. But did you ever fix this issue, having the same problem
Click to expand...
Click to collapse
No, I never did figure it out. I've been loathe to spend more money on another battery when I've got other much newer phones. I really have no idea why it would not reset once the battery was replaced, maybe it's the replacement battery.
Have you tried changing the battery?
I've tried flashing different stock roms, Kit Kat, Lollipop, and it doesn't help.
Short of going to Sony, I'm not sure what else to do.
I know. I've seen the threads for battery drain and such, but I don't think there's a problem with "drain" so much, as perhaps a bad battery altogether.
I'm using my old M8 for my daughter, but after RUU, and setting up latest TWRP and all, then trying to install a custom ROM whether Stock or AOSP, when I boot into recovery, it goes from 100% within the ROM, to show 80% in recovery.
If off the charger, there does appear to have some battery drain, but I chalk that up to normal first usage.
However, it then shuts off @ 30%, but when I put it on the charger, it says @ 60%.
I've done the calibration method (hold all buttons for 2 minutes) trick, but there appears to be no help for the erratic battery readings.
Does anyone know if my suspicion is correct?
I'm on Sprint's last RUU.
mcwups1 said:
Does anyone know if my suspicion is correct?
Click to expand...
Click to collapse
Ive seen so many posts now that refer to the exact thing you mention. Phones turning off at 20-30%. Its claimed that this is due to a faulty battery and a replacement has fixed it. I do not have this problem, however, I did get a replacement 12 months ago.
That's what I'm afraid of.
Did you replace it yourself, or have a tech do it?
mcwups1 said:
That's what I'm afraid of.
Did you replace it yourself, or have a tech do it?
Click to expand...
Click to collapse
I replaced mine just Yesterday, with both speakers, chraging portero AND buttons, its not that hard AND not easy, you Will nerd a razor blade, AND see a few videos first, one thing to have in mind Is that i put a m9 battery on my m8, AND the phone works, but the phone doesnt recognize the aditional 240mamps,. AND the battery temp always shows 25C, but besides that everything is ok, waiting for the battery yo settle.
Hi everyone,
I'm not sure if this the right place to be but I have had my robin for about 1.5 years now.
I think near January I started having issues with battery with the stock firmware (like instantly dying at 15% and such)
So I had decided to unlock and root my robin.
I've tried three different Custom ROMS:
Resurrection Remix
Hexagon
Another rom which I don't recall.
They are all 7.1 or 7.1.2.
Currently on Hexagon.
But all of the have the same issues.
My phone dies at 50% battery (or sometimes less if I'm lucky) for all three roms and I wouldn't be able to boot the firmware.
But I would be able to boot to recovery and see that there is still 50% battery and the battery would be able to discharge until 0.
Can anybody please help me?
I tried battery calibration apps, but it didn't help.
*edit* Also wanted to add, my phone lasts about 30 mins before it reaches the 50% threshold (while reading articles and such) before it crashes sometimes at 50%, 40% or 30%.
Thanks!
atomicduelist said:
Hi everyone,
I'm not sure if this the right place to be but I have had my robin for about 1.5 years now.
I think near January I started having issues with battery with the stock firmware (like instantly dying at 15% and such)
So I had decided to unlock and root my robin.
I've tried three different Custom ROMS:
Resurrection Remix
Hexagon
Another rom which I don't recall.
They are all 7.1 or 7.1.2.
Currently on Hexagon.
But all of the have the same issues.
My phone dies at 50% battery (or sometimes less if I'm lucky) for all three roms and I wouldn't be able to boot the firmware.
But I would be able to boot to recovery and see that there is still 50% battery and the battery would be able to discharge until 0.
Can anybody please help me?
I tried battery calibration apps, but it didn't help.
*edit* Also wanted to add, my phone lasts about 30 mins before it reaches the 50% threshold (while reading articles and such) before it crashes sometimes at 50%, 40% or 30%.
Thanks!
Click to expand...
Click to collapse
This also happens to me under the same conditions. The phone will power off around 30-40% for no reason, though the phone won't power off until 0% while in TWRP. I'm currently on Omni but I'm going to flash AOSIP soon. This issue also happened on LOS and LOS based ROMs such and Hexagon and RR.
It can't be a hardware issue can it? Unless voltage is the issue. Not sure
Oh yeah!
the other ROM I had used was OMNI.
Yesterday I tried factory resetting and installing stock ROM.
But the same thing happpened.
It's either software OR somehow our battery is old and has a flash drop in voltage causing the OS to shutdown.
I had another occurence yesterday.
After the shutdown at 50%, I kept it running to about 45% in recovery and then it would be able to turn back on until maybe 30%, where it would shutdown and no be able to boot anymore but had 30% battery in recovery.
Got tired and right now using my Nexus 5 back up phone.
atomicduelist said:
Oh yeah!
the other ROM I had used was OMNI.
Yesterday I tried factory resetting and installing stock ROM.
But the same thing happpened.
It's either software OR somehow our battery is old and has a flash drop in voltage causing the OS to shutdown.
I had another occurence yesterday.
After the shutdown at 50%, I kept it running to about 45% in recovery and then it would be able to turn back on until maybe 30%, where it would shutdown and no be able to boot anymore but had 30% battery in recovery.
Got tired and right now using my Nexus 5 back up phone.
Click to expand...
Click to collapse
I am quite sure it's voltage yes, that can only be fixed with a new battery sadly. Might have to buy a new phone D: Honestly can't be bothered replacing the battery as I don't want to damage the phone.
DECHTECH said:
I am quite sure it's voltage yes, that can only be fixed with a new battery sadly. Might have to buy a new phone D: Honestly can't be bothered replacing the battery as I don't want to damage the phone.
Click to expand...
Click to collapse
Thanks! I was hoping it wasnt :/ lame.
So then now the question I'm wondering is how come the battery for nextbit degraded so fast when my 3-4 year old nexus 5 battery is still pretty good. :/
I was a kickstarter backer but now I think I'll be off Nextbit/Razer unless, I get the phones for free I guess.
I've been thinking, would there be a way to trick the phone into thinking it's being charged but in fact it isnt?
maybe a USB solar powered patch...it would not be enough to charge the phone but it should be enough to trick it into no going into 0 voltage.
atomicduelist said:
I've been thinking, would there be a way to trick the phone into thinking it's being charged but in fact it isnt?
maybe a USB solar powered patch...it would not be enough to charge the phone but it should be enough to trick it into no going into 0 voltage.
Click to expand...
Click to collapse
Is there anyone who can advises me for quick charger for my Nextebit Robin , the official one is unavailable so , can you tell me if they are any replacement charger
RaiZProduction said:
Is there anyone who can advises me for quick charger for my Nextebit Robin , the official one is unavailable so , can you tell me if they are any replacement charger
Click to expand...
Click to collapse
https://www.amazon.com/AUKEY-PA-T9-...xus-6p-LG-G5-Qualcomm-Certified/dp/B018RR30TK
Same issue with my phone. It's so bad now I can get it to power off even at 90% depending on what I use like record video. And I mean power off and not a force close as it will give me the pop up stating as such.
Anyone know of a third party company that will replace the battery or some trick to where my phone doesn't to do this anymore? I was also a backer and would like to enjoy my limited edition phone a bit longer.
imutau said:
Same issue with my phone. It's so bad now I can get it to power off even at 90% depending on what I use like record video. And I mean power off and not a force close as it will give me the pop up stating as such.
Anyone know of a third party company that will replace the battery or some trick to where my phone doesn't to do this anymore? I was also a backer and would like to enjoy my limited edition phone a bit longer.
Click to expand...
Click to collapse
Oddly I can get the phone to last longer by watching YouTube or Netflix, I have no idea why. Once or twice I managed to get the phone all the way to 0%, only then it turned off.
I've tried many things from battery calibration and flashing all sorts of roms and tweaks, even flashing older roms based on marshmallow. Nothing seems to work.
I seriously doubt you can find a third party company that'll replace the battery for you (Though if you find anything, LET US KNOW), considering that replacement batteries on themselves are pretty scarce. Plus the phone isn't the easiest of phones to tear apart without damaging it, sadly.
I hope you find a way to keep this awesome phone lasting a little longer.
I've tried Lineage, Carbon and just loaded up Paranoid. They all die at around 40%. It's been demoted to a tinker toy now. Maybe Nextbit can push out that almighty battery software upgrade they announced months ago...
tryfe said:
I've tried Lineage, Carbon and just loaded up Paranoid. They all die at around 40%. It's been demoted to a tinker toy now. Maybe Nextbit can push out that almighty battery software upgrade they announced months ago...
Click to expand...
Click to collapse
It's not a software problem. And Nexbit/Razer no longer push out updates or give support anymore AFAIK.
The only way you can fix this problem is to replace the battery, or buy a new Robin.
I had the same problem. My Robin started to shut down at around 45% suddenly. Unfortunately, I can't find replacement battery on eBay or Taobao...
Lordcolus said:
I had the same problem. My Robin started to shut down at around 45% suddenly. Unfortunately, I can't find replacement battery on eBay or Taobao...
Click to expand...
Click to collapse
I ended up purchasing a new phone and it's doing well. My old midnight robin and my Mint one now have the same issue. My midnight robin doesn't even charge anymore. I looked for battery replacements but even if you did find one there is a high chance you'd break the phone taking it apart/putting it back together.
DECHTECH said:
I ended up purchasing a new phone and it's doing well. My old midnight robin and my Mint one now have the same issue. My midnight robin doesn't even charge anymore. I looked for battery replacements but even if you did find one there is a high chance you'd break the phone taking it apart/putting it back together.
Click to expand...
Click to collapse
The battery issue is so annoy and it lead me to buy a new Pixel 2 instead. It's just a shame that I only own Robin lesser than a year.
I too recently started facing this problem it would shut down between 20-30%. I am on Carbon ROM.
UPDATE :
Something very odd happened.
I flashed OmniROM last weekend.
Its been a week and my battery issue i.e. shutting down randomly between 20-30% has gone.
I plugged in the charger at 2%.
/root said:
UPDATE :
Something very odd happened.
I flashed OmniROM last weekend.
Its been a week and my battery issue i.e. shutting down randomly between 20-30% has gone.
I plugged in the charger at 2%.
Click to expand...
Click to collapse
Weird. I'm on CarbonROM and haven't experienced this yet. Did you dirty flash to OmniROM or clean flash? And did you ever dirty flash from another ROM to CarbonROM? Just curious and looking for a possible cause so the rest of us can avoid it.
Sent from my Robin using XDA Labs
marvelljones said:
Weird. I'm on CarbonROM and haven't experienced this yet. Did you dirty flash to OmniROM or clean flash? And did you ever dirty flash from another ROM to CarbonROM? Just curious and looking for a possible cause so the rest of us can avoid it.
Sent from my Robin using XDA Labs
Click to expand...
Click to collapse
Nope always did a clean flash, total 100% wipe through TWRP.
I was on AOSP, clean flashed to Carbon and now clean to Omni.
While on AOSP, all was fine never had sudden shutdown at XX% it would only shutdown if I try to check twitter or read on pocket or text or maps below 5-8% which I think is normal.
On Carbon it was working fine at first, 2-3 days later at 20% it just shut down in 2-3 minutes of just texting (no images, no videos, just text) This happened for few more days then I cleared the cache & dalvik and it didn't help, later it became worse. Instead of shutting down at 20% it started shutting down anywhere around 25%.
Most people said its the battery issue and it needs replacing. Some said its battery calibration issue. I assumed the worst and thought its battery issue and stayed cautious.
Now I switched to Omni and suddenly its all fine. So I assume its the battery calibration issue? Clean flash did that too maybe? I don't know but I am just assuming that happened.
Update, @/root? Has your battery remained functional under Omni?
While waiting for a replacement SIM card for my HTC 10, I had fully charged it then powered it off. The next day, I wanted to check something on the phone, so I powered it up. The battery level wasn't 100% or in the 90's... it was a shocking 65%.
I've owned 4 different Android cellphones prior to this one. None of them ever exhibited this kind of power drop while shut down. Most lose just a couple of percentage points when in standby. Clearly something is wrong with this phone...
Does anyone know if there's any kind of parasitic drain on the battery of the HTC 10 even while completely off? It's running Oreo. Either this, or the battery is somehow worn out enough that it can't even hold a charge when sitting idle. Any ideas?
Hi, maybe your battery is not so healthy anymore.
Still you can try this:
''Power off phone.
Plug phone into HTC charger and charge for two minutes or more
While charging, hold down volume up+volume down+power button and continue holding
Phone will turn on and off repeatedly every 15 seconds or so while continuing to hold all three buttons
Keep this going for 2 minutes, then release buttons when phone is ON
Now, let phone charge fully normally (with phone either on or off--doesn't matter) and battery level reporting, charging and battery life should be normalized.''
Supposedly it's the recommended procedure by HTC.
^ Yes, I'm very familiar with that procedure and had done it several times. And then was fully charged after that. And by the way, I said 1 day but it was actually 12 hours later, which is even worse!
I conducted another experiment... with the phone battery level at 77%, I first put it in Airplane mode and then shut it down completely. Well, about 18 hours later, guess what? Battery level showed 76% upon boot up! Remarkable. If the phone is SHUT DOWN, I can't understand how there would be any possible parasitic drain difference between normal mode and airplane mode. There should be NOTHING running. Or, instead of parasitic, this may just be happenstance of what cells inside the battery itself were taxed. I'll have to try this again from 100% charge, just to be sure.
battery
cytherian said:
^ Yes, I'm very familiar with that procedure and had done it several times. And then was fully charged after that. And by the way, I said 1 day but it was actually 12 hours later, which is even worse!
I conducted another experiment... with the phone battery level at 77%, I first put it in Airplane mode and then shut it down completely. Well, about 18 hours later, guess what? Battery level showed 76% upon boot up! Remarkable. If the phone is SHUT DOWN, I can't understand how there would be any possible parasitic drain difference between normal mode and airplane mode. There should be NOTHING running. Or, instead of parasitic, this may just be happenstance of what cells inside the battery itself were taxed. I'll have to try this again from 100% charge, just to be sure.
Click to expand...
Click to collapse
I have what may be a similar problem , I charge phone to 100% let it sit , it drops to 43% when I pick it up it reboot and continues to reboot, boot recovery now it shows 1%, plugin phone boot up and it shows 43%.
pbazw said:
I have what may be a similar problem , I charge phone to 100% let it sit , it drops to 43% when I pick it up it reboot and continues to reboot, boot recovery now it shows 1%, plugin phone boot up and it shows 43%.
Click to expand...
Click to collapse
I think that when you charge it to 100%, it's not really 100%. The phone may be displaying that figure, but the battery isn't fully charged. And if your battery has suffered deep discharge a number of times, it could have a very diminished mAh capacity at this point. This is why the phone continues to reboot. The operating system starts and it thinks there's enough power to start up, but the battery is actually down to 1%, so the battery protection circuitry kicks in and forces a shut down. The operating system doesn't register this as a normal shutdown, so it goes into reboot mode. And thus, pattern keeps repeating until you plug in the phone to a power source.
Well, I did another test. I charged the phone up to 100%, put it in airplane mode, and then shut it down. A little over 12 hours later, I turned it on and battery level showed 98%. That was curious. Did airplane mode really make a difference? Didn't make sense... until I decided to reboot the phone, just to be sure. And guess what it showed after that? 61%. So my theory was right -- there is no parasitic drain really. It's the battery having some kind of problem. I rebooted again... 59%. Rebooted again 59%. Then I held down all 3 buttons for 5 cycles and rebooted. 59%. So that is actual.
When I charged up the phone, I had done the 3 button hold-down a couple of times and recharged until rebooting stayed in the upper 90 percent. So, the phone most definitely should have been fully charged. This battery is damaged... and given what I learned from the previous owner, who simply never let it drop down below 50% (always recharged when between 50~60%), and pristine external condition, this is just a prime example of the substandard battery and/or battery management firmware.
cytherian said:
Well, I did another test. I charged the phone up to 100%, put it in airplane mode, and then shut it down. A little over 12 hours later, I turned it on and battery level showed 98%. That was curious. Did airplane mode really make a difference? Didn't make sense... until I decided to reboot the phone, just to be sure. And guess what it showed after that? 61%. So my theory was right -- there is no parasitic drain really. It's the battery having some kind of problem. I rebooted again... 59%. Rebooted again 59%. Then I held down all 3 buttons for 5 cycles and rebooted. 59%. So that is actual.
When I charged up the phone, I had done the 3 button hold-down a couple of times and recharged until rebooting stayed in the upper 90 percent. So, the phone most definitely should have been fully charged. This battery is damaged... and given what I learned from the previous owner, who simply never let it drop down below 50% (always recharged when between 50~60%), and pristine external condition, this is just a prime example of the substandard battery and/or battery management firmware.
Click to expand...
Click to collapse
I experienced something like that last week, where I left it in airplane mode for like 8 hours. I went out did things, came back later and it was litterly being reported at the same thing. Like 68%. It was really weird. Then I had started using the device for like an hour. And it only dropped like 1 or 2%. It was the exact opposite of what we are used to seeing. I was doing youtube, playing a game. Not normal. Then finally the drainage started up again.
Today the device dropped pretty quick to around 35% so I plugged it in to charge. Came back like 15 minutes later and it was reported around 69%. I thought that was way too quick for 15 minutes. Granted it was a quick charge 2 charger, but still, I've never seen that quick of a charge on the 10 or my V20.
I'm really at a loss what to think as far as calibration, what the battery is telling us. I'm thinking of unlocking, throwing on Leedroid and Elemental kernel. I just don't have the time to go through all that yet. Glad I have my backup phones.
My 10 is also like yours in pristine condition. Granted I didn't ask how the seller how tye used the battery before me, but I also never researched problems with the 10 before buying. I was under the assumption since I've been an HTC customer from the M7 and M8, that the 10 would also have a good battery. Same or maybe better than my V20. Especially since they both use the 820 chipset. I guess I'm paying for my ignorance now.
gustav30 said:
My 10 is also like yours in pristine condition. Granted I didn't ask how the seller how tye used the battery before me, but I also never researched problems with the 10 before buying. I was under the assumption since I've been an HTC customer from the M7 and M8, that the 10 would also have a good battery. Same or maybe better than my V20. Especially since they both use the 820 chipset. I guess I'm paying for my ignorance now.
Click to expand...
Click to collapse
Same as you... great value from HTC phones up until the HTC 10 (having skipped the M9).
I'm in a pre-return mode right now with the seller. She has given me the OK to do a return. But I'm going to see if she might welcome the opportunity to do a partial refund. Because if she takes back the phone I don't know if she's going to try reselling it or give it to a family member to deal with. It's a hassle selling a phone that has problems. My thought is, if I can work out a good price (like half the cost of a typical charge--got two quotes for $140 and $150), I'll go ahead and try to do the battery change myself. But then... I'm a little unsure about jumping down that rabbit hole. It may work fine, but I usually keep a new (to me) phone for at least 2 years. If I'm having battery trouble 12 months from now, I'll be pretty PO'ed at myself. I've already wasted too much time on this debacle.
The other option is going with a Google Pixel. I'm frustrated, because I missed that recent Woot! deal on the Google Pixel that ran a few days ago. They all sold off in less than a day. Refurbished Pixel phones with 32Gb ($200) and 128Gb ($244) sizes. I'd have sprung for the 128Gb. But the Pixel isn't free of issues. There's a dreaded screen burn-in that happens on some models. Unpredictable. And when it does, it's a PITA to replace the screen, almost as bad as the HTC 10.
Lastly... I might just say screw-it and stick with my M8 for the next couple of years, until 5G phones with solid electrolyte lithium batteries are available. Phone companies are starting to do customers a disservice with this "sealed in" battery fiasco. Next thing you know, they'll be revoking the Micro SD memory card slot, like Apple.
cytherian said:
Same as you... great value from HTC phones up until the HTC 10 (having skipped the M9).
I'm in a pre-return mode right now with the seller. She has given me the OK to do a return. But I'm going to see if she might welcome the opportunity to do a partial refund. Because if she takes back the phone I don't know if she's going to try reselling it or give it to a family member to deal with. It's a hassle selling a phone that has problems. My thought is, if I can work out a good price (like half the cost of a typical charge--got two quotes for $140 and $150), I'll go ahead and try to do the battery change myself. But then... I'm a little unsure about jumping down that rabbit hole. It may work fine, but I usually keep a new (to me) phone for at least 2 years. If I'm having battery trouble 12 months from now, I'll be pretty PO'ed at myself. I've already wasted too much time on this debacle.
The other option is going with a Google Pixel. I'm frustrated, because I missed that recent Woot! deal on the Google Pixel that ran a few days ago. They all sold off in less than a day. Refurbished Pixel phones with 32Gb ($200) and 128Gb ($244) sizes. I'd have sprung for the 128Gb. But the Pixel isn't free of issues. There's a dreaded screen burn-in that happens on some models. Unpredictable. And when it does, it's a PITA to replace the screen, almost as bad as the HTC 10.
Lastly... I might just say screw-it and stick with my M8 for the next couple of years, until 5G phones with solid electrolyte lithium batteries are available. Phone companies are starting to do customers a disservice with this "sealed in" battery fiasco. Next thing you know, they'll be revoking the Micro SD memory card slot, like Apple.
Click to expand...
Click to collapse
Yeah, I'm thinking to hold on to the device. Thought same that I'd try to sell it, but a hassle. Plus I'm still not convinced its hardware yet. I still kind of feel like its something to do with latest Oreo firmware. Possibly Nougat as well. I'm starting to research downgrading via S-on to Nougat or Marshmallow and just leave it that way if the battery returns somewhat normal. While its a pain to do downgrade, its something I'd consider when I have more time. However, if this was my only device, or main device, then I'd probably cut my losses with it.
Tell you one thing, certainly makes me appreciate the M8 much more than i did!
gustav30 said:
Yeah, I'm thinking to hold on to the device. Thought same that I'd try to sell it, but a hassle. Plus I'm still not convinced its hardware yet. I still kind of feel like its something to do with latest Oreo firmware. Possibly Nougat as well. I'm starting to research downgrading via S-on to Nougat or Marshmallow and just leave it that way if the battery returns somewhat normal. While its a pain to do downgrade, its something I'd consider when I have more time. However, if this was my only device, or main device, then I'd probably cut my losses with it.
Tell you one thing, certainly makes me appreciate the M8 much more than i did!
Click to expand...
Click to collapse
Marshmallow has been a decent version of the Android O/S. You can really spruce it up nicely with different themes. I recently revised the theme on my M8 and it's super. It's just a very dependable phone. And when you get used to that, it's a shock to run into the mess of other phones. Pretty stunned to see all the troubles that the Pixel encountered. Apparently the Pixel-2 has some pretty serious challenges as well, like screen burn-in. I'd never even thought of rolling an HTC 10 back to Marshmallow. Is that really possible? It may not be necessary... as it could all come down to the kernel Go S-OFF and load up a replacement like ElementalX.
So I did a complete factory reset on the phone as I prepped it for returning to the seller. What a pain in the butt... having to wait for the initialization. Took over an hour to complete. Anyway, I made the mistake after initialization and before configuring an account to do the 3-button power cycle. Apparently that wipes all preparation cache, so it had to go through it yet again. After that, I did the cycling 3 times from 99% and it dropped only 1% each time. Baffling. I rebooted several times after that, expecting to see a repeat of that 35~40% drop. Stayed in the high 90's. So with that mystical "recovery" I ran the HTC battery test... and it did just as poorly as before. Definitely something out of whack between the O/S and battery.
I really wish there was a definitive explanation for this. If battery replacement was guaranteed to eliminate it, then I'd feel more comfortable going with a battery change. Would just hate to get burned 12 months later, finding the same issue repeat.
cytherian said:
I'd never even thought of rolling an HTC 10 back to Marshmallow. Is that really possible? It may not be necessary... as it could all come down to the kernel. Go S-OFF and load up ElementalX.
Click to expand...
Click to collapse
You can, also flash a kernel..... WITHOUT being s-off, s-off has never been needed to change kernel. Please elaborate and stop giving false info.
Thank you.
cytherian said:
Marshmallow has been a decent version of the Android O/S. You can really spruce it up nicely with different themes. I recently revised the theme on my M8 and it's super. It's just a very dependable phone. And when you get used to that, it's a shock to run into the mess of other phones. Pretty stunned to see all the troubles that the Pixel encountered. Apparently the Pixel-2 has some pretty serious challenges as well, like screen burn-in. I'd never even thought of rolling an HTC 10 back to Marshmallow. Is that really possible? It may not be necessary... as it could all come down to the kernel. Go S-OFF and load up ElementalX.
So I did a complete factory reset on the phone as I prepped it for returning to the seller. What a pain in the butt... having to wait for the initialization. Took over an hour to complete. Anyway, I made the mistake after initialization and before configuring an account to do the 3-button power cycle. Apparently that wipes all preparation cache, so it had to go through it yet again. After that, I did the cycling 3 times from 99% and it dropped only 1% each time. Baffling. I rebooted several times after that, expecting to see a repeat of that 35~40% drop. Stayed in the high 90's. So with that mystical "recovery" I ran the HTC battery test... and it did just as poorly as before. Definitely something out of whack between the O/S and battery.
I really wish there was a definitive explanation for this. If battery replacement was guaranteed to eliminate it, then I'd feel more comfortable going with a battery change. Would just hate to get burned 12 months later, finding the same issue repeat.
Click to expand...
Click to collapse
Looks like you can downgrade to Nougat or Marshmallow based on this thread here. Can do it remaining S-On.
https://forum.xda-developers.com/htc-10/how-to/how-to-rollback-oreo-to-marshmallow-s-t3787101
Sent from my HTC 10 using Tapatalk
Mr Hofs said:
You can, also flash a kernel..... WITHOUT being s-off, s-off has never been needed to change kernel. Please elaborate and stop giving false info.
Click to expand...
Click to collapse
It wasn't my intention to give false info. I had the impression from what I'd read that making changes at that level required it. But you've obviously got a tremendous amount of experience so I'll revise my understanding. Thank you.
Hi all,
I have a VZW P3XL (required for work, otherwise I'd have the unlocked Google version) that's been suffering a LOT of crashes in the last few weeks. Usually it's while the phone is idle with the screen off, but it's occasionally happened while I'm actively using it, too. When it's happening while I'm using it, whatever app I'm in freezes completely; if I press the power button the screen turns off and then it's entirely unresponsive until I hold power to reboot. It's not seen by adb in this state. Once or twice when this has happened I've gotten a "SystemUI keeps not responding" message, but usually there's no message. When it happens while I'm not using it, it's just unresponsive with a black screen until I hold power to reboot. The issue has persisted through a factory reset/OTA sideload, which is about all I could think to do with a locked bootloader.
Anyone have any thoughts/suggestions for troubleshooting?
Pixel troubleshooting chat wasn't much help, not that I expected it to be. It's out of warranty so they're directing me to ubreakifix, saying they can "guarantee" it'll be fixed.
Oh, and they had me boot into safe mode and it happened again immediately.
I wonder if the battery's going bad? I've noticed that it tends to happen when the charge level is in the 60s or lower, and I don't think it's happened while plugged in (though I could be wrong about that). I wonder if there could be some sort of inconsistent voltage or something? Kind of a wild-ass guess.
chinly43 said:
Pixel troubleshooting chat wasn't much help, not that I expected it to be. It's out of warranty so they're directing me to ubreakifix, saying they can "guarantee" it'll be fixed.
Oh, and they had me boot into safe mode and it happened again immediately.
I wonder if the battery's going bad? I've noticed that it tends to happen when the charge level is in the 60s or lower, and I don't think it's happened while plugged in (though I could be wrong about that). I wonder if there could be some sort of inconsistent voltage or something? Kind of a wild-ass guess.
Click to expand...
Click to collapse
Battery is a good point and probably the best conclusion from the things you observed... (there where similar issues on the Nexus 6 iirc, after certain wear off the battery the OS got unstable as battery could no longer provide the amount of energy the CPU needed in specific demanding situations, replacement was the only option to get rid of the problem...)
It would help to check what's left from the design capacity of your battery, if it's near 70% of the original design capacity it's most likely the source for your issues and replacing it would most likely help, if you get a good quality replacement battery, otherwise it will do more harm than good...
Get AccuBattery from PlayStore, even the base version of the app gives you reliable information on your battery wear out, again the magic number is around 70% but there's plenty of information on the app itself regarding this matter!
Sent from my Google Pixel 3 XL using XDA Labs
Thanks for the advice, Sam; I'm trying, but it deteriorated further overnight and now only will stay on for 30 seconds at most, usually shorter, unless it's plugged into my laptop (and it doesn't pull enough voltage to charge in that case, it just drains more slowly). Either way, I appreciate the reply.
This must be a battery issue, it can't take a charge whatsoever now. 28% left until it's forever dead, 4XL arrives today.