So my XL keeps powering off on an over night charge and requires the cable to be disconnected for around 30seconds then plug back in and attempt to power it on with vol down and power key.
This happens on the H and V builds for the XL regardless of running stock kernel or a custom one or rooted and regardless of charger official one that came in the box or any third party charger using a type c to type c or a type a to type c.
I have re-flashed and factory reset this device twice now and it constantly does this every night without fail.
Any ideas ?
Further testing here resulted in no change :
However it appears the phone is crashing as you have to hold the the power button for 10 seconds to reboot it.
So I have gone back to the stock kernel and uninstalled any apps installed in the last week ( including TB ) i have enabled battery saver mode fully disabled DND and enabled battery optimisation on all apps ( this was disabled )
I'll be sticking with the V build ( November 5th update ) and shall only test with the supplied charger and C to C usb lead.
have captured a bug report and will dig into this and see if anything shows up
solved this turns out it was titanium backup app causing the issue
Related
Dear all,
I'm using this ROM cm-12.1-20151102-UNOFFICIAL-endeavoru.zip (nightly build by milda25), which I found when I came across this thread http://forum.xda-developers.com/htc-one-x/orig-development/rom-htc-one-x-cyanogenmod-12-1-t3169751.
The ROM is fine for me for daily usage (so, nothing special).
However, it has one big problem on my phone: The battery won't charge when I plug in the charger. Short description:
- I used several different AC/DC chargers and USB cables.
- When I boot into recovery, the battery charges fine.
- I tried rebooting, playing around w/various power saving settings, no luck.
- Since my phone is encrypted, I tried the following: Check the charge status by pluggin in and out and observing the battery light during the individual boot phases
a) HBOOT/Recovery: charging (no light, but displayed by TWM info)
b) CM12.1 spash screen: possibly charging (but no light)
c) CM12.1 password dialog (where you enter the encryption password): charging (light switches on and off when (un)pluggin)
- One strange observation is, that the phone "remembers" the charging status.
- When I plug in the charger in step (c), enter my pw to decrypt the phone, unlock the SIM and then unplug the charger, the phone stills shows "charging". Even the battery circle stays animated...
Maybe some of you guys has a similar experience and can give me a hint how to solve?
Thank you very much and best regards,
Celphis
So I'm planning on installing a nexus 7 2013 (FLo) in my car. I've been trying to use timur's kernel for 6.0.1 MOB30X in fi mode, as soon as i disconnect the usb y power my dac turns off and tablet goes in suspend which is the intended behaviour, but the problem is when i connect the power again to the usb y cable, the tablet resumes but my dac doesn't come back on. This also happens with elemental X kernel on the same android version, but i tried cm12.1 with elemental x and it works just like it should, as soon as i connect the power, the usb dac is on. I would use cm12.1, but the standby power usage is a little too high even with tasker profiles, deep sleep and greenify, also the booting up time is around 50seconds so turning it off is not a solution. And that's why i am determined to figure out why i have problems on stock firmware mob30x, but i've been stuck for the past 5 days.
Update: Now fi mode stopped working completely after reinstalling the firmware and kernel, also in non fi mode it seems to work without problems.
Hi
I flashed lineage 14.1 OS over the manufacturers stock ROM about 3 weeks ago. The Lineage ROM had issues BUT the battery was still charging normally. (Worth noting that the battery was also charging perfectly fine on when the manufacturers Rom was still installed). Seeing as Lineage 14.1 had a host of other issues, I then flashed AOKP's version of Pie with GAPPS Micro. At first, the battery would charge until 53%. However after it drained to 0%, it has not charged properly since. (6 days or so).
A) Battery is about 6 months old, so relatively new
B) non-charge problem started with installation of AOKP version of Pie
C) I have used a couple of battery health apps,which reveal the following:-
c.1) Battery health is fine
c2) Voltage 3.5V (essentially 0% charge)
c3) amperage averaging around 30mA
c4) Battery Manager and other apps state that the battery is "connected but not able to charge"
D) I have tried deleting the batterystats.bin file, which had no affect
E) I have tried using recalibration apps off Google Play Store with no affect.
F) I have cleaned the USB port and tried different cables, also with no affect.
I'm going to try flash another OS shortly. Other than that my last idea is to purchase a new battery. HOWEVER just thought I'd ask if anyone has any other bright ideas as to what might have happened to a perfectly functional battery? Another thing worth mentioning is that the power button on this device doesn't 'click' anymore. So one cannot feel that the button has been pressed, you have to press harder to ensure that the device powers on. It was like that for a long time before this battery problem started but thought I'd mention it. Can a faulty power button be causing a massive power drain on the battery OR be stopping it from charging?
EDIT - when the phone is off and plugged in to the charger, the battery icon shows it as "charging". However if I leave it for a few hours and switch the phone on again, it still reflects as 0% charged and only switches on with the power cable attached. Also I cannot get into recovery mode, after shutting down, unless I leave the phone plugged in and "charging" for a while. It's like recovery mode needs at least some power from the battery.
Debcal said:
Hi
I flashed lineage 14.1 OS over the manufacturers stock ROM about 3 weeks ago. The Lineage ROM had issues BUT the battery was still charging normally. (Worth noting that the battery was also charging perfectly fine on when the manufacturers Rom was still installed). Seeing as Lineage 14.1 had a host of other issues, I then flashed AOKP's version of Pie with GAPPS Micro. At first, the battery would charge until 53%. However after it drained to 0%, it has not charged properly since. (6 days or so).
A) Battery is about 6 months old, so relatively new
B) non-charge problem started with installation of AOKP version of Pie
C) I have used a couple of battery health apps,which reveal the following:-
c.1) Battery health is fine
c2) Voltage 3.5V (essentially 0% charge)
c3) amperage averaging around 30mA
c4) Battery Manager and other apps state that the battery is "connected but not able to charge"
D) I have tried deleting the batterystats.bin file, which had no affect
E) I have tried using recalibration apps off Google Play Store with no affect.
F) I have cleaned the USB port and tried different cables, also with no affect.
I'm going to try flash another OS shortly. Other than that my last idea is to purchase a new battery. HOWEVER just thought I'd ask if anyone has any other bright ideas as to what might have happened to a perfectly functional battery? Another thing worth mentioning is that the power button on this device doesn't 'click' anymore. So one cannot feel that the button has been pressed, you have to press harder to ensure that the device powers on. It was like that for a long time before this battery problem started but thought I'd mention it. Can a faulty power button be causing a massive power drain on the battery OR be stopping it from charging?
EDIT - when the phone is off and plugged in to the charger, the battery icon shows it as "charging". However if I leave it for a few hours and switch the phone on again, it still reflects as 0% charged and only switches on with the power cable attached. Also I cannot get into recovery mode, after shutting down, unless I leave the phone plugged in and "charging" for a while. It's like recovery mode needs at least some power from the battery.
Click to expand...
Click to collapse
Does anyone know of a battery app/ software that one can run in recovery mode OR prior to booting? I'm wondering if this battery problem is software related or hardware related.
Debcal said:
Does anyone know of a battery app/ software that one can run in recovery mode OR prior to booting? I'm wondering if this battery problem is software related or hardware related.
Click to expand...
Click to collapse
Now, it appears, I cannot even boot into TWRP recovery. I suspect the non-charging battery is the problem.
Debcal said:
Now, it appears, I cannot even boot into TWRP recovery. I suspect the non-charging battery is the problem.
Click to expand...
Click to collapse
You won't believe it!!! After trying every solution known to man, turns out that the battery just doesn't sit snugly in the phone, so it doesn't make good contact. ???*♂??
Charging now that I manually pushed it up against the contacts.
I'm having peculiar behavior with frequent reboots on the Fold 3 when it's fully charged and I leave it in a fast charger overnight.
Originally I thought some rogue app or module was misbehaving.
Now I've noticed the reboots only seem to occur when charging. I left it in a high speed charger overnight – it rebooted every cca 40 minutes.
Also, yesterday I had a reboot right after plugging in a powered HDMI monitor hub – before starting Dex. That was a single occurrence – on the charger it keeps rebooting. Tried three different chargers – same behavior.
Now, 6 hours since the morning, not plugged in – no reboot. Can this indicate anything – any ideas anyone?
Try clearing the system cache.
Try a hard reboot (simulates pulling the battery).
Has the OS been upgraded without a factory reset afterwards?
It shouldn't be rebooting by itself. A hardware failure seems most likely explanation.
Overheating will cause a auto shutdown but not a reboot. If it's returnable, do so.
Otherwise it will likely need repair service.
Check
Device Care -> 3-dots -> Automation -> Auto restart at set times
I used this to set the phone to reboot at 3am.
Narrowing down the issue with my Pixel 2 XL. Long story short, when the phone is unplugged and the screen turns off, it freezes and the only remedy is to hold the power button for 15+ seconds until it reboots.
But here's the weird thing... after this happens, the USB port only works for power - not data. But I found a way to get data back. If I power off the device, then plug it in via USB-C to the computer (Macbook Pro) and hold volume down while starting, it goes into Fastboot mode as it should. If I then boot to TWRP and then boot the device, USB data works again.
Tried:
Multiple full factory zip flashes to both slots, wiping all data
Multiple ROMs - LineageOS, Arrow, Pixel Edition with updated partitions, CalyxOS (Googleless ROM), Stock (Android 8 - 11)
With or without Magisk
The only thing I haven't tried is multiple versions of TWRP. Currently I'm using TWRP 3.6.0_9-0.
I've experienced similar screen-off freezing issues on this device and my Nexus 6 when using a kernel that has too low frequencies. But not sure if that's an indication of components going bad or what.
Some additional background on the issue here:
Anyone have their P2XL die out of nowhere?
I gave my P2XL to my wife about 6 months ago when her P2 had battery issues. She wakes me up in the middle of the night last hight to tell me the phone died. Won't turn on, won't charge, just dead. I've never had a phone do this before. Tried...
forum.xda-developers.com
Any similar issues or suggestions?
Narrowing things down a bit more...
It seems to only happen once the screen has been off (or AOD turns on) for 1m to 1m 15s. Not sure if this is when Doze kicks in or what.
Is there any way to prevent the phone from deep sleep? I know some kernels have in the past by accident, but is there a way to do it on purpose? Since I only use this phone as a media device, I'm not concerned about battery life. But not being able to turn off the screen is an issue.