Related
Within a second my Captivate Glide will suddenly go to 0% power then slowly charge back up over time..or if I charge it, it jumps back up to about where it left off. And it happens pretty much every time I turn my phone on for more then 5 mins. It seems to happen while sending or receiving text? Any ideas what could be causing this or a solution?
I keep my data off, and theres 3 apps (Stock SMS Messenger, Handcent SMS, and the Contacts+ App) that can handle SMS on my phone, and I have locker pro that displays my notifications. And I also use the Nova Launcher, but thats the only app's I keep running. Maybe a conflict with the apps or a bug with one of the apps? I don't see how that'd effect the battery that much but possibly?
I've also changed my ROM a few times, but right now I'm back on the newest ICS update and I've rooted it. Maybe I need to change it again? I can't remember if this problem started happening before I did my last change.
Or maybe just a bad battery? I don't know much about batteries but I haven't had this phone long, I don't think it'd be the battery.
If you have any more questions feel free to ask and I appreciate any help!
suret said:
Within a second my Captivate Glide will suddenly go to 0% power then slowly charge back up over time..or if I charge it, it jumps back up to about where it left off. And it happens pretty much every time I turn my phone on for more then 5 mins. It seems to happen while sending or receiving text? Any ideas what could be causing this or a solution?
I keep my data off, and theres 3 apps (Stock SMS Messenger, Handcent SMS, and the Contacts+ App) that can handle SMS on my phone, and I have locker pro that displays my notifications. And I also use the Nova Launcher, but thats the only app's I keep running. Maybe a conflict with the apps or a bug with one of the apps? I don't see how that'd effect the battery that much but possibly?
I've also changed my ROM a few times, but right now I'm back on the newest ICS update and I've rooted it. Maybe I need to change it again? I can't remember if this problem started happening before I did my last change.
Or maybe just a bad battery? I don't know much about batteries but I haven't had this phone long, I don't think it'd be the battery.
If you have any more questions feel free to ask and I appreciate any help!
Click to expand...
Click to collapse
I had about the same problem, with it working fine with a decent charge (anywhere between 30-80%), and all of the sudden it would say "battery critically low" and shut down. Putting it on the charger would often get the charge to show what it was before it freaked out.
I noticed that the battery was starting to bulge and get somewhat "mushy"....which told me the battery was probably going to explode or leak if I didn't replace it soon
I have had the phone for a year and four days, and this just showed up in the last few days...fortunately I bought an extended warranty and they will pay for the replacement battery I just picked up today.
FYI, the battery should be totally flat on both sides. Mine would wobble if I set it on a table.
Ok, TL1170, Thanks!
I already narrowed it down to my battery by the time you posted that because I factory reset my phone multiple times and changed the ROM once to see if that'd help, and it didn't..I was running out of stuff to blame it on ..
But yeah, my battery is pretty badly deformed and I just ordered a new one.
Thanks, mine is doing the same thing - about once every 2 days or so. I can see in the battery life plot that it sometimes goes from 90% almost completely vertically to 0% and then right back up to 90%. I don't see any obvious bulges or "mushiness" to it, but it doesn't seem to be completely flat when put on a table. I'll see if I can get a replacement battery, this phone was not used by it's previous owner for maybe a year or so before I bought it, maybe that might have been part of the problem.
suret said:
Ok, TL1170, Thanks!
I already narrowed it down to my battery by the time you posted that because I factory reset my phone multiple times and changed the ROM once to see if that'd help, and it didn't..I was running out of stuff to blame it on ..
But yeah, my battery is pretty badly deformed and I just ordered a new one.
Click to expand...
Click to collapse
Any time a battery is misshaped it can do the oddest things.
Pull out and visually inspect your battery. If there are any visible cracks or bulges, dispose of it carefully. Damaged lithium ion batteries are incredibly dangerous; a properly pissed off LIon will produce a sizable fireball.
If your battery looks fine, fully charge it (until your phone says "100%" or "Charged"), then fully discharge it (don't connect to the charger again until your phone shuts off for lack of power). This is to calibrate the charge estimator chip in the battery itself. Don't bother with batterystats.bin, it's completely unrelated.
If the above doesn't work, you need a new battery. If the new battery behaves the same way, you need a new phone
Happening to us too
It's been happening to my phone for a while now, but I'm usually using it while at a desk so I can keep it charging. However, it just started happening to my wife's Captivate Glide also. I checked my battery and don't notice any bulging or non-flatness... but it happens about once or twice a day now - Pretty much anytime I do anything more than make a call with the battery indicator saying it's somewhere less than maybe 90% charged. I've taken to using a portable backup battery when I'm out.
If you view the battery usage screens, you can see the cliffs where it drops from 80-90% down to zero and right back up. We've only had them for about a year, so I'm going to take it to AT&T and see if they can do anything for it... probably not.
roothorick said:
Pull out and visually inspect your battery. If there are any visible cracks or bulges, dispose of it carefully. Damaged lithium ion batteries are incredibly dangerous; a properly pissed off LIon will produce a sizable fireball.
If your battery looks fine, fully charge it (until your phone says "100%" or "Charged"), then fully discharge it (don't connect to the charger again until your phone shuts off for lack of power). This is to calibrate the charge estimator chip in the battery itself. Don't bother with batterystats.bin, it's completely unrelated.
If the above doesn't work, you need a new battery. If the new battery behaves the same way, you need a new phone
Click to expand...
Click to collapse
jester131 said:
It's been happening to my phone for a while now, but I'm usually using it while at a desk so I can keep it charging. However, it just started happening to my wife's Captivate Glide also. I checked my battery and don't notice any bulging or non-flatness... but it happens about once or twice a day now - Pretty much anytime I do anything more than make a call with the battery indicator saying it's somewhere less than maybe 90% charged. I've taken to using a portable backup battery when I'm out.
If you view the battery usage screens, you can see the cliffs where it drops from 80-90% down to zero and right back up. We've only had them for about a year, so I'm going to take it to AT&T and see if they can do anything for it... probably not.
Click to expand...
Click to collapse
If you're really desperate to get those particular batteries working, you could try cleaning the contacts, both on the battery and in the phone, with rubbing alcohol and Q-tips. But most likely you will need new batteries.
Battery( low power) Shut Down Issue Fixed
I also was having the "critical powerl level" shut down issue over the past two weeks. My phone is about two years old, and there was a few occasions in the past two weeks where i pulled it out of my pocket and it was off. Then this past week the phone (on a full charge) would go anywhere from around 90% sometimes %40, and then all of a sudden say "battery low" and shut off. It would turn back on, but would only stay on for a few minutes.And a few times it also got really hot. It wasnt doing this when plugged into the wall so i examined my battery and there was NO visible flaws or bulging of any kind, it looked fine. But as we all know just because it looks good certainly doesnt mean it is so i odered one on ebay for about $10. It arrived 2-3 days later and instantly fixed my problem. The phone is fine now and hasnt done anything wierd. It was the battery. These batteries have a limited life span, and very often the phone may say the battery is 76% charged but the capacity of the battery under load can still draw it down to 0%. You cant always trust the level the phone says its at. So if anyone else out there is having this power issue it really isnt expensive to find a good battery out there. The one i got was $9.98 and it is a Samsung battery identical to the one that came with the phone. Except the new one has a fresh date of 2013 on it. Very happy to have my phone back. Ive never been a part of any sites like this, but im posting here now because there seems to be a lot of people having this issue, and often someone will put a very complex procedure on these sites to fix an issue when its not always necessary. If you have the power/shut off issue like i've described here and your phone does the same as mine was its probably the battery, and for the price of a new one like i got, its worth trying.
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.
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.
My 2 XL is only a month old. There is no complain about charging before. It was normal. Hit 100% everytime. Until several days ago, I woke up in the morning and my phone does stuck at 99% with charging rapidly status. I've tried to drain the battery and fully charge, try to flash factory image, but the problem still exist. The phone does charge normally to 90%, then getting slow and more slow when hit 95%, it takes very long time to get to 99, then it stuck for hours. I'm using app called AccuBattery, just want to monitor the charge speed. And there it is, the phone stop the charging at 99%, charging speed shows -1 , so basically the phone cut the power input when hitting 99% although the status still not fully charged. Until I rebooted the phone then it will hit 100%.
So what happened to my phone? I'm using original charger from the box. Is it software or hardware issue? Thank you
The first image is when stucked on 99% and the charge speed show -1. After that I rebooted the phone then charge speed increasing, not -1 anymore at 99%. The second image is when the phone says fully charged at 100% and charge speed back to -1, which is normal if the phone already fully charged.
EDIT:
Solved - see my post below
What's the battery health at?
lil_ith said:
What's the battery health at?
Click to expand...
Click to collapse
The battery health is excellent, I didn't have any complain about battery life. Easily get 6++ SOT, full day usage.
fauzanskywalker said:
The battery health is excellent, I didn't have any complain about battery life. Easily get 6++ SOT, full day usage.
Click to expand...
Click to collapse
What is it at though? But on all my previous rmas, I had sometimes great issues in from charging past 98%.. I would have to turn it off for it to register that it's actually charged to 100% and more than likely it would drop to 99 as soon as I unplugged it.
lil_ith said:
What is it at though? But on all my previous rmas, I had sometimes great issues in from charging past 98%.. I would have to turn it off for it to register that it's actually charged to 100% and more than likely it would drop to 99 as soon as I unplugged it.
Click to expand...
Click to collapse
So you got replacement?
I can't asked for RMA. Pixel didn't sold in my country. I bought from local seller that handcarry the unit into my country.
fauzanskywalker said:
So you got replacement?
I can't asked for RMA. Pixel didn't sold in my country. I bought from local seller that handcarry the unit into my country.
Click to expand...
Click to collapse
Yeah I got a replacement at the time but not for that sole reason so I don't know if it would work but I don't think it's that much of an issue if you are still getting 6+h sot
lil_ith said:
Yeah I got a replacement at the time but not for that sole reason so I don't know if it would work but I don't think it's that much of an issue if you are still getting 6+h sot
Click to expand...
Click to collapse
Yeah, I'm planning to do that. I'm just uncomfortable with my phone acting weird, it supposed to hit 100% everytime normally like before. And a little afraid that this issue would make any affect in the future, broken battery or worse. If there's an explanation how this is happened and it's safe, then I might not make any complain anymore.
fauzanskywalker said:
Yeah, I'm planning to do that. I'm just uncomfortable with my phone acting weird, it supposed to hit 100% everytime normally like before. And a little afraid that this issue would make any affect in the future, broken battery or worse. If there's an explanation how this is happened and it's safe, then I might not make any complain anymore.
Click to expand...
Click to collapse
I had the same issue with my Oct 18 2 XL.
Download Accubattery and "calibrate" your battery.
It removes a file (.bin or something) that resets the batter charge percentage.
I really think the 99% thing is harmless, but if it bugs you (I get it) Accubattery will remove the file that resets it.
Good luck!
Az Biker said:
I had the same issue with my Oct 18 2 XL.
Download Accubattery and "calibrate" your battery.
It removes a file (.bin or something) that resets the batter charge percentage.
I really think the 99% thing is harmless, but if it bugs you (I get it) Accubattery will remove the file that resets it.
Good luck!
Click to expand...
Click to collapse
I currently using AccuBattery as shown on my post attachment and I didn't found any "calibrate" menu inside the app.
I've done so many methods, like drain the battery to 0% and charge it or re-flash factory image but seems none worked. So I search on the internet about delete the .bin file under root/data folder, but I didn't found any folder called data on /root (currently running android 10). I'm stucked.
So I'm thinking how if pull the battery out and put it back maybe it will reset something, but it seems impossible to do with myself. Until I found a method to hard reboot the phone with press power button + vol down for maybe 10sec. My phone was 75% at that time, after hard reboot my battery increased to 78%. Then I tried to charge the phone and voila, hit 100% normally, didn't need to unplug and replug to hit 100% anymore. It's been 3 days my phone is act normal again. Hope it will lasts forever.
So my conclusion is, seems the hard reboot method somehow force cut the power from the battery to the phone just like we pull out battery then put it back and maybe it's reset something maybe like batterystats or anything. Idk. But I'm glad nothing happened and it was just software error.
fauzanskywalker said:
I currently using AccuBattery as shown on my post attachment and I didn't found any "calibrate" menu inside the app.
I've done so many methods, like drain the battery to 0% and charge it or re-flash factory image but seems none worked. So I search on the internet about delete the .bin file under root/data folder, but I didn't found any folder called data on /root (currently running android 10). I'm stucked.
So I'm thinking how if pull the battery out and put it back maybe it will reset something, but it seems impossible to do with myself. Until I found a method to hard reboot the phone with press power button + vol down for maybe 10sec. My phone was 75% at that time, after hard reboot my battery increased to 78%. Then I tried to charge the phone and voila, hit 100% normally, didn't need to unplug and replug to hit 100% anymore. It's been 3 days my phone is act normal again. Hope it will lasts forever.
So my conclusion is, seems the hard reboot method somehow force cut the power from the battery to the phone just like we pull out battery then put it back and maybe it's reset something maybe like batterystats or anything. Idk. But I'm glad nothing happened and it was just software error.
Click to expand...
Click to collapse
When you download Accubattery, open it, it automatically 'calibrates' your battery (see pic)
Az Biker said:
[/HIDE]
When you download Accubattery, open it, it automatically 'calibrates' your battery (see pic)
View attachment 4846527
Click to expand...
Click to collapse
Oh, I just realized that. Thank you. But I think it didn't work for me. Nvm, my phone is normal now :laugh:
I had somewhat of the same issue with my phone too. Would sit around 98% then after taking it off the charger overnight, my battery would drop like a rock to around 85%. No idea if I was just imagining things but I don't remember that much battery life wasted away like that overnight when not in use at all.
I also sent mine in for RMA last Thursday and get it back later on today so hopefully the issue will be resolved.
I have also been experiencing the same issue since upgrading to Pie last year. Once it returned to normal for 1 month only and then went back to 98% charging issue until today
carelockh said:
I had somewhat of the same issue with my phone too. Would sit around 98% then after taking it off the charger overnight, my battery would drop like a rock to around 85%. No idea if I was just imagining things but I don't remember that much battery life wasted away like that overnight when not in use at all.
I also sent mine in for RMA last Thursday and get it back later on today so hopefully the issue will be resolved.
Click to expand...
Click to collapse
I would assume broken battery. Never experienced drain so much like that when not in use. My phone normally about 1-2% drop overnight (always on display off). It's great you got replacement, but check twice for screen, 2 XL known for defective screen.
jovianjm said:
I have also been experiencing the same issue since upgrading to Pie last year. Once it returned to normal for 1 month only and then went back to 98% charging issue until today
Click to expand...
Click to collapse
Check inboxes, already replied.
fauzanskywalker said:
I would assume broken battery. Never experienced drain so much like that when not in use. My phone normally about 1-2% drop overnight (always on display off). It's great you got replacement, but check twice for screen, 2 XL known for defective screen.
Click to expand...
Click to collapse
Yeah I am content with the RMA replacement it's just fine, no issues thus far. Just annoying the update breaks charging sound file and lockscreen lock/unlock sounds. But I eventually got those issues fixed too.
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.