Database Users

Solution for One Potential Cause of Rapid Battery Drain

I've was using 5.2.3 for the last several weeks and to begin with, it worked wonderfully.
Until around 10 days ago, I'd never suffered any rapid battery drain problems, then all of a sudden one morning, I woke up and the phone was at 10% charge despite being left on charge overnight.
I figured there was an issue with the ROM and decided to reboot. This seemed to work fine for a day. Then the same charge problem was back.
I thought the ROM was now failing so decided to install the latest version 5.2.6 directly over 5.2.3 but the problem still persisted so the problems didn't seem to be ROM related but could be due to the unwiped areas but this seemed unlikely.
Just as a final test I decided to change the cable. I normally use the cable provided by HTC as it seems pretty sturdy. Turns out it was the cable all along.
The phone is now charging fine with a different cable and it's running fine again.
So, if you're having problems with overnight power drain when your phone is on charge, try changing the cable.
Edit: There is no visible damage to the cable and it has never been stressed in anyway as I take great care not to stress the pressure points.

Thanks for the info mate. Probably not in the right the right section though.

Your response to that post is probably in the wrong section. Oh, wait..! [email protected]*!t now this post is probably in the wrong section, see what you started.
Sent from my Inspire 4G using xda premium

My cable just stopped working yesterday. Or well, it worked before flashing ARHD 5.2.6 and after it stopped working. I didn't believe it had anything to do with the rom and not sure that I still do, but still an interesting coincidence.

Sorry for posting in the wrong thread everyone. I don't create new threads very often so I wasn't thinking clearly.
Diffler said:
My cable just stopped working yesterday. Or well, it worked before flashing ARHD 5.2.6 and after it stopped working. I didn't believe it had anything to do with the rom and not sure that I still do, but still an interesting coincidence.
Click to expand...
Click to collapse
I'm not saying the cable problem was caused by the ROM - I was just explaining how I identified that the ROM I was using wasn't the cause of the battery drain.
Cables breaking are very rare - happened once to a phone cable once after engineers had been called out to check the fax machine about 6 times before someone gave the cable a try.

KindleFire with Energy ICS ROM not turning on.

I installed the Energy ROM from this thread http://forum.xda-developers.com/showthread.php?t=1528024 a few hours ago and everything worked well. I used the kindle a little and decided to charge it up, so, I plugged in the AC adapter and let it charge for like 1 hour.
When I come back, the adapter is all hot, like unusually hot. The led was red, which means the kindle was charging. Now I unplug it and hit the power button and nothing happens! Nothing, like no led, no nothing. I long-press it and still nothing. I press and let go a couple times and still nothing!
What does this mean? Is my Kindle fried? Because of a ROM!? What can I do now? Please help me
EDIT:
Ok, I fixed the problem. It looks like the Kindle Fire was overheating while connected to the AC adapter. So, I let it lay down a fan for a while and I tried to turn it on and it did. Very dangerous ROM that one, I think I'm going to get CM7 or something until this issue gets fixed.

Unfortunately for now all ICS ROMs have the potential to have that happen if you leave your KF on for extended periods of time when you aren't using it. The widely held solution to that is to shutdown when you know you won't be using it for a while such as while charging or when you go to bed.

If it's fried I don't believe that depends of a rom.... I think it was the fault of the AC adapter...try to charge the KF with another adapter...

jlocohustler said:
I installed the Energy ROM from this thread http://forum.xda-developers.com/showthread.php?t=1528024 a few hours ago and everything worked well. I used the kindle a little and decided to charge it up, so, I plugged in the AC adapter and let it charge for like 1 hour.
When I come back, the adapter is all hot, like unusually hot. The led was red, which means the kindle was charging. Now I unplug it and hit the power button and nothing happens! Nothing, like no led, no nothing. I long-press it and still nothing. I press and let go a couple times and still nothing!
What does this mean? Is my Kindle fried? Because of a ROM!? What can I do now? Please help me
EDIT:
Ok, I fixed the problem. It looks like the Kindle Fire was overheating while connected to the AC adapter. So, I let it lay down a fan for a while and I tried to turn it on and it did. Very dangerous ROM that one, I think I'm going to get CM7 or something until this issue gets fixed.
Click to expand...
Click to collapse
Don't go flaming a ROM when it is a great rom, that is a good way to run a dev off from our community. I have been running the rom since it came out with no issues other than the standard HWA and other listed bugs. Many people have had the same results as me and most of the people who haven't it was because of a bad download and/or a bad flash. The rom is no more dangerous than the general process of rooting and customizing is. Did you get a log cat of what happened at all? Or do any sort of searching for a solution of what caused the issue so on the very slight chance it is a bug it could be fixed?
---------- Post added at 01:36 PM ---------- Previous post was at 01:32 PM ----------
BluesHawk said:
Unfortunately for now all ICS ROMs have the potential to have that happen if you leave your KF on for extended periods of time when you aren't using it. The widely held solution to that is to shutdown when you know you won't be using it for a while such as while charging or when you go to bed.
Click to expand...
Click to collapse
It shouldn't overheat, just freeze and force a hard restart (hold power button for about 20 seconds then turn on). If it is overheating there is something else going on like the AC adapter or some sort of major malfunction from a bad flash. Most likely the AC adapter though.

dnathan13 said:
Don't go flaming a ROM when it is a great rom, that is a good way to run a dev off from our community. I have been running the rom since it came out with no issues other than the standard HWA and other listed bugs. Many people have had the same results as me and most of the people who haven't it was because of a bad download and/or a bad flash. The rom is no more dangerous than the general process of rooting and customizing is. Did you get a log cat of what happened at all? Or do any sort of searching for a solution of what caused the issue so on the very slight chance it is a bug it could be fixed?
Click to expand...
Click to collapse
I believe there's some misconception here. I didn't flame or try to hurt the reputation of the dev or anything. I just posted about an issue and I'm sure, like any other issue, more people must have encountered it. Most people come to find solutions on forums, so, I believe I did the right thing by starting this thread.
Did you even read my OP? I posted an update long before you replied...
EDIT:
AC adapter is fine. Used it just fine on stock ROM before flashing to the new ROM.

jlocohustler said:
I believe there's some misconception here. I didn't flame or try to hurt the reputation of the dev or anything. I just posted about an issue and I'm sure, like any other issue, more people must have encountered it. Most people come to find solutions on forums, so, I believe I did the right thing by starting this thread.
Did you even read my OP? I posted an update long before you replied...
EDIT:
AC adapter is fine. Used it just fine on stock ROM before flashing to the new ROM.
Click to expand...
Click to collapse
Yes I read the op where you claim... "very dangerous rom that one" that is the part that I would say is harsh.
Many people have been running the show rom for days with no issues, but one or two people claiming it will overheat and kill their fire is all it takes for everyone to start bashing a rom and make a dev want to leave.
Sorry I came off as a jerk I just get upset when claims are made based on one bad experience that could have been caused by a number of things (bad flash, left over bits of stock conflicting with rom, lack of knowledge of ICS issues about screen timeout, kernel issue ratjer than rom issue although related, etc...)
Sent from my SPH-D700 using xda premium

No over-heating problems at all for me -- I installed Kang ICS ROM three days ago.

Battery Drain while Charging, tried almost everything, need help!

Hi Guys,
Been following XDA for a long time but never had to post anything as everything had already had an answer to my question.
I know there are a lot of threads about battery drain but for some reason, everything I have tried has seemed to help minimally.
Here's the rundown.
I have a Galaxy S5 G900I running G900F custom rom, Resurrection Remix 5.6.7 Marshmallow.
Previously I was running the lollipop version of Resurrection Remix and battery was fine.
The phone is over a year old, but I have tested the battery with another S5 my wife has and it is perfectly fine. It charges fairly quick when the power is off on the phone and still fast enough while it's in use. Even if I am to open up a game on my wife's phone with my battery or hers, the battery continues to charge slowly while in use.
On my phone however, switched with both batteries, the drain is astronomical. I tested playing a game and I would lose practically 1% of battery per minute while in game.
What I have done so far is, installed Xposed, I have Amplify running following various guides which has slowed down the drain of my battery, I have installed Greenify which has also helped. I've turned off the scanning of wifi and bluetooth in locations. I have tried going back to stock rom which does help but it doesn't help me figure out the issue I want to fix.
I have tried switching power points in the house, changing usb cables, changing chargers, all of which do not help my phone with either battery, but on my wives it is fine.
I have also set CPU profiles in Rom Toolbox to lower CPU usage in idle, lower than 15% battery, while on charge. As of today, even while using the phone, I have limited the max CPU usage.
Prior to this latest updated Rom with Marshmallow, I could use my phone and have it plugged into my USB 3 on my PC and it would charge while in use unless playing a game or using a high demanding application, in which case, it would slowly drain. If in a power point adapter it would charge regardless.
Now, even in idle, on my PC, it drains while charging, and charges extremely slow on a power point.
I have searched for over a week trying to find any sort of guide or help with this problem and I have certainly minimized some of the drain but this is ridiculous.
If anyone has any idea's on what it could be, please let me know. I have tried cleaning all the dirt and gunk out of the charging point, the only thing I haven't done is pull apart the phone to see if its a hardware problem (Which I am starting to think it might be.)

have u tried with another usb cable?

lawong said:
have u tried with another usb cable?
Click to expand...
Click to collapse
Yes, I have tried various USB cables on various USB chargers, even non USB chargers I had laying around. And as I said, I have also switched the batteries into my wife's phone and they charge fine there.
The problems only started once I upgraded to Marshmallow.
It also persists when the phone is switched off and charging. It's just slow.

Ven942 said:
Yes, I have tried various USB cables on various USB chargers, even non USB chargers I had laying around. And as I said, I have also switched the batteries into my wife's phone and they charge fine there.
The problems only started once I upgraded to Marshmallow.
It also persists when the phone is switched off and charging. It's just slow.
Click to expand...
Click to collapse
Do they persist while on L? Could possibly be a conveniently timed hardware failure.
Sent from my SAMSUNG-SM-G900A using Tapatalk

Ven942 said:
I have a Galaxy S5 G900I running G900F custom rom, Resurrection Remix 5.6.7 Marshmallow.
Click to expand...
Click to collapse
Your default CPU 1900.0 MHz (8-core) this now running at 2400 MHz, you are lucky that the phone did not permanent damaged up to date.
Find S5 G900I compatible ROM and not what ever ROM.

try to factory reset your device 1st. if its only started after MM update then must be software issue.

lawong said:
try to factory reset your device 1st. if its only started after MM update then must be software issue.
Click to expand...
Click to collapse
Done that. Had a previous ROM installed and the battery was better. But I want to know how to fix the issue, I don't want to revert back to older software.
I know its possible because even with the same rom installed, before I bricked it and forgot to back it up, I had better battery life.
Kiriakos-GR said:
Your default CPU 1900.0 MHz (8-core) this now running at 2400 MHz, you are lucky that the phone did not permanent damaged up to date.
Find S5 G900I compatible ROM and not what ever ROM.
Click to expand...
Click to collapse
First thing I did was cap the cpu usage at 1900mhz.

Go back to stock lollipop and check if u still have the problem

Ven942 said:
First thing I did was cap the cpu usage at 1900mhz.
Click to expand...
Click to collapse
It seemed that you did that unsuccessfully, OR you battery gets old and needs replacement.
At about 400 charging times, the battery this is now at 80% capacity or less.
In my S5 I have permanently activated basic power saving mode, this clocks the CPU always lower than Max.
The phone seems happy, and I am too.

By using one Qualcomm App I discovered how low is low with basic power saving mode on.

Flash a custom Kernel and you can set it more or less as low as you like

S5 this is a very complicate device, I am trusting only Samsung about it.
If this was an old tablet with out ROM support from anywhere, in this case I would.

*Detection* said:
Flash a custom Kernel and you can set it more or less as low as you like
Click to expand...
Click to collapse
Having trouble finding a custom ROM that's a stable build that runs on S5 and on Marshmallow. Would you happen to know any in particular that I could use?

consider buying a new battery

Ven942 said:
Having trouble finding a custom ROM that's a stable build that runs on S5 and on Marshmallow. Would you happen to know any in particular that I could use?
Click to expand...
Click to collapse
I use a stock MM port G900FXXU1CPD7-BTU
But you could just flash a compatible custom Kernel and then have control over the CPU/GPU clocks

*Detection* said:
I use a stock MM port G900FXXU1CPD7-BTU
But you could just flash a compatible custom Kernel and then have control over the CPU/GPU clocks
Click to expand...
Click to collapse
Sorry, I meant to say custom Kernel, not rom.

Ven942 said:
Sorry, I meant to say custom Kernel, not rom.
Click to expand...
Click to collapse
This one looks like it supports stock TW 6.0.1 MM for the G900F
http://forum.xda-developers.com/gal...kernel-phoenix-kernel-v7-marshmallow-t3340407
But like always, do your own research before flashing
EDIT - Actually it looks like the dev has left out OCing from this Kernel, not sure about downclocking/under volting - maybe request it in his thread

Huawei Nexus 6P random shutdown and won't boot without charger

Hi guys, I have bought a nexus 6P secondhand but I'm dealing with the problem of random shutdowns. After that it won't boot unless it is hooked to a charger. Some facts that I think might be of some influence or what I have tried:
- I bought it with Cyanogenmod 14.1, first day flashed back to stock 7.0 but kept my bootloader unlocked;
- Today I flashed an OTA update to 7.1.1;
- It happens random while using the phone, but I manage to reproduce the failure when using Google Camera and take pictures very rapidly (don't really know what the phone activity is at that moment)
- I've got a new battery on the way, might that be the issue?
- Battery status (percentage etc) doesn't make a difference. Might as well happen at 100%
- It doesn't happen while on the charger;
- It didn't happen in safe mode (didn't test this for too long though, but the fast camera action didn't kill the phone;
Does these descriptions make any bells rinkle? For me it looks like a defective battery but I'm happy to hear some expert about this
Thank you all for reading!

Yup, mine does the same thing. I believe it is supposed to be fixed with the new 7.1 release. Its the most inconvenient thing ever. I rarely takes pics now because nobody has a usb-c charger to get my phone turned back on. I'm running stock 7.0. It's not your battery.

Well that would kinda suck, I just updated to 7.1.1 and the problem is still there. Do you have a source for this thing?

I had the same random reboots.
I too suffered from random reboots in 7.1.1 dp2. They increased in frequency gradually. One night, it stuck in bootloop. Couldn't even boot into recovery. Browsed through threads here and reddit posts. All said the only solution was to RMA as without recovery nothing is possible. Huawei is replacing the motherboard as it's under warranty.

I just updated to 7.1.1 and I also can still confirm it's happen. I called huawei and they told me it was a software issue and it's not resolved and there is no fix other than to load 6.x on the phone. So basically, I we have a turd of a phone and nobody seems to want to fix it. Google told me it was a hardware issue and now Hauwei tells me it's a software issue. Maybe it's time for a new phone.

Just curious but have any of you flashed the official release images directly from Google through ADP with the FlashAll.bat command that it includes? Keeping your bootloader unlocked, but flashing everything to make sure your device is 100% stock and as fresh as it can be?
Messing with OTA's and other stuff like CM, I would definitely flash it this way and test it bone stock before venturing back into the Custom Rom land as major OS changes (from 6.0 to 7.0, etc) always seem to have residual glitches just like this.

IM0001 said:
Just curious but have any of you flashed the official release images directly from Google through ADP with the FlashAll.bat command that it includes? Keeping your bootloader unlocked, but flashing everything to make sure your device is 100% stock and as fresh as it can be?
Messing with OTA's and other stuff like CM, I would definitely flash it this way and test it bone stock before venturing back into the Custom Rom land as major OS changes (from 6.0 to 7.0, etc) always seem to have residual glitches just like this.
Click to expand...
Click to collapse
I loaded the image directly from google. I've never rooted or loaded a rom on this phone. I've only run factory images. I don't have the time to tinker like I used to.

Well that is downright strange then. There really doesn't seem to be any device that doesn't at least have a small share of mystery in some of it's problems is there? Lol.

Well that was how I reverted from CM to stock 7.0, by using the flash-all function (even though the flash all didn't work, had to flash the seperate files, but result was the same). The 7.1.1 upgrade was with a OTA flash using ADB sideload because I was rooted and TWRP recovery was active, so the OTA update didn't work for me. To be honest, I don't think my problem is a software issue. Is there any 'deeper' software than the complete rom? Is the kernel flashed seperately?

IM0001 said:
Well that is downright strange then. There really doesn't seem to be any device that doesn't at least have a small share of mystery in some of it's problems is there? Lol.
Click to expand...
Click to collapse
This fiasco has been happening for tons of people for weeks now, including me. Mine was just 2 weeks out of warranty, both google and huawei are pointing fingers at each other and nobody cares. I have tried all the methods possible, to flash different versions of pure factory image, nothing worked.

What charger did everyone use to get it backup a running?
Mine just shutdown this morning and using the USB A-to-C cable on a computer/car/wall outlet it didn't even recognize it was plugged. Google wants to RMA it (third one in 14 months of ownership) and I'm fighting over their 5 days delivery time for a new one.

also face this problem previously and Huawei replace battery. just 1 week before the warranty run out
Sent from my Nexus 6P using Tapatalk

rmoney said:
What charger did everyone use to get it backup a running?
Mine just shutdown this morning and using the USB A-to-C cable on a computer/car/wall outlet it didn't even recognize it was plugged. Google wants to RMA it (third one in 14 months of ownership) and I'm fighting over their 5 days delivery time for a new one.
Click to expand...
Click to collapse
Every charger worked for me. Now even carry a powerbank with me for when it lets me down outdoors I can get it powered on again. Plugging it in the PC also works just fine. Even a standard samsung charger (with micro-usb -> usb C adapter) works.

hah! Mine just started doing this!
I got the phone back from huawei for the 15% battery issue.. and it came back with this issue after going to 7.1.1

Strange! Mine doesn't seem to be related to any firmware state. It had this with CM14.1, stock 7.0 (factory image), and 7.1.1 (OTA flash). The only thing that is in common is that the bootloader is unlocked. Can this have any influence?

Hafidel36 said:
Strange! Mine doesn't seem to be related to any firmware state. It had this with CM14.1, stock 7.0 (factory image), and 7.1.1 (OTA flash). The only thing that is in common is that the bootloader is unlocked. Can this have any influence?
Click to expand...
Click to collapse
Mine is locked, on 7.0 I didn't have this issue.. on 7.1.1 It started.
on developer previews for it wasn't an issue either..

This is the absolute worst. Phones dying consistently at 15%. Sometimes it'll even shut down at like 30-40%. Absolutely ridiculous. I'm getting a new phone.

andrewnelson23 said:
This is the absolute worst. Phones dying consistently at 15%. Sometimes it'll even shut down at like 30-40%. Absolutely ridiculous. I'm getting a new phone.
Click to expand...
Click to collapse
That seems to be another know defect, you should look it up on here. Plenty of people are having that problem, but it is different from this thread.

I am having the same problem too! I was trying to raise this for two times on both XDA and reddit and no body seemed to care until you came up with this!
Mine randomly happens when taking photos with HDR+ and with the battery less than 50% (based on my observation). I replaced the battery by myself not long ago though.

Huawei says going back to 6.0.1 will fix the issue... and is blaming google, saying their pixel devices have this issue on 7.1.1 too.

Been trying to fix my 6p, it's not in bootloop, however

... it only reboots itself when it is NOT charged and run a heavy CPU app.
So the phone is usable. However when I run youtube without charging, it might have a chance to reboot. The phone had already changed battery few months ago and it was running fine until the Oreo patch, then it starts to reboot itself randomly. I've done the 4core patch (TWRP 3.2.1) and the phone is slow as hell (as expected). Google chrome seems to seem to use all 8 cores and cause the phone to reboot still.
So the scenairo is that if it's charging, the phone won't have any issues except for slowness. Battery is getting worst and worst everyday like the battery issue that shows up among 6p users. But this battery is pretty new.
What else should I patch this with? Maybe I never did it right?
Build - OPM.5.171019.015
Kernel - 3.10.73.9
Oreo 8.1.0
Angler -0.85
Feb 2018

foxfai said:
... it only reboots itself when it is NOT charged and run a heavy CPU app.
So the phone is usable. However when I run youtube without charging, it might have a chance to reboot. The phone had already changed battery few months ago and it was running fine until the Oreo patch, then it starts to reboot itself randomly. I've done the 4core patch (TWRP 3.2.1) and the phone is slow as hell (as expected). Google chrome seems to seem to use all 8 cores and cause the phone to reboot still.
So the scenairo is that if it's charging, the phone won't have any issues except for slowness. Battery is getting worst and worst everyday like the battery issue that shows up among 6p users. But this battery is pretty new.
What else should I patch this with? Maybe I never did it right?
Build - OPM.5.171019.015
Kernel - 3.10.73.9
Oreo 8.1.0
Angler -0.85
Feb 2018
Click to expand...
Click to collapse
What kind of battery did you replace it with? Because I read that these non original batteries cause a lot of problems.

xdamember143 said:
What kind of battery did you replace it with? Because I read that these non original batteries cause a lot of problems.
Click to expand...
Click to collapse
Grabbed it from ebay. One of the many "oem" batteries that comes from China.....
Of course I won't know if they are all fake or not since they don't make them anymore. Upon search for them again there are many of the same but older manufacture dates that I can see in photos.

foxfai said:
Grabbed it from ebay. One of the many "oem" batteries that comes from China.....
Of course I won't know if they are all fake or not since they don't make them anymore. Upon search for them again there are many of the same but older manufacture dates that I can see in photos.
Click to expand...
Click to collapse
Yes you can tell the original battery's ribbon cable is kind of fat while the newer ones are thin and it also has a temperature sensor built in the battery while the non originals don't . Here's a pic to show you what I mean left is the real original and the right is a cheap knockoff

xdamember143 said:
Yes you can tell the original battery's ribbon cable is kind of fat while the newer ones are thin and it also has a temperature sensor built in the battery while the non originals don't . Here's a pic to show you what I mean left is the real original and the right is a cheap knockoff
Click to expand...
Click to collapse
Can I have the website for the purchase of the original battery of Nexus 6P? Thank you.

navintar said:
Can I have the website for the purchase of the original battery of Nexus 6P? Thank you.
Click to expand...
Click to collapse
I bought mine on eBay awhile back but I found this one. Its a little expensive but its worth it in the long run.https://m.ebay.com/itm/Original-Bat...wei-Google-Nexus-6P-H1511-H1512-/173100893141

xdamember143 said:
I bought mine on eBay awhile back but I found this one. Its a little expensive but its worth it in the long run.https://m.ebay.com/itm/Original-Bat...wei-Google-Nexus-6P-H1511-H1512-/173100893141
Click to expand...
Click to collapse
Thanks for the pointer in regards to the temp sensor on the battery. Almost 90% of those ones are fake on ebay.
However after brainstorming some ideas and looking through some threads. I was able to root the 6p and clock down the CPU a nudge. It was already running on 4 basic cores only and had to clock them down to 960mhz. This way the phone was able to be use without charge most of today until battery hit 50%.
This is just my temporary solution. Will see if I want to put in another battery to have this last a little longer.