Database Info

NEED HELP!!!! phone won't stop powering off

My inspire keeps powering off at ranodm times and has gotten worse. If its plugged into a power source it will stay on, but the second its pulled off theres a huge chance that it will just randomly power off. I've wiped the battery stats, factory rest a bunch of times, tried multiple roms and radios and can't find a solution. ANY HELP WOULD BE GREATLY APPRECIATED!!!!

See if ATT will give you a new battery.

Tx Redneck said:
See if ATT will give you a new battery.
Click to expand...
Click to collapse
I know it sounds like he's being an ass, but I think he's right. I have the exact same problem. Used CoreDroid, MIUI, & HoneySense 4 & 5 and they all randomly rebooted. I noticed that after I powered back on, the battery level would be significantly different. It got progressively worse as the battery level drops. Once I get to about 23%, it just turns off when I try to do anything. I speculate that the sudden increase in battery drain from the screen getting bright & the radio draws more current than the battery can provide.
To test, I got my phone to the point that it would turn off every time I booted it. It would show the homescreen & say that it had 18% battery. I then plugged it in to the USB charger & it works fine. I'll be replacing the battery ASAP.

this happend to me on CM7 and MIUI twice and the first time i just flashed off of CM7 and it stooped and on MIUI i just rebooted the phone while connected to the charger then when it was completely booted up i unplugged it and it was fine after that but that time it was caused by letting my battery die down and then i kept booting up my phone to completely deplete the battery and did this about 20 times and it wouldn't die so i just changed out batteries and when i booted and it would immediately power down like the battery was dead so thats when i plugged it in and powered on and it worked, and i know its not the battery because i have 4 batteries

cordell507 said:
this happend to me on CM7 and MIUI twice and the first time i just flashed off of CM7 and it stooped and on MIUI i just rebooted the phone while connected to the charger then when it was completely booted up i unplugged it and it was fine after that but that time it was caused by letting my battery die down and then i kept booting up my phone to completely deplete the battery and did this about 20 times and it wouldn't die so i just changed out batteries and when i booted and it would immediately power down like the battery was dead so thats when i plugged it in and powered on and it worked, and i know its not the battery because i have 4 batteries
Click to expand...
Click to collapse
Ok then, you "know" it's not the battery - so what is your speculation? Until I get the spare batteries I ordered today, I won't be able to fully test the battery theory. I can only say with certainty that the phone doesn't shutdown while plugged in.
I could also go along with another theory - The Thunderbolt got a recent OTA update that makes them randomly shutdown. Is it possible that a piece of that code made it into the new Gingerbread ROMs? I didn't note the issue running CoreDroid 6.4 (a GB build but the last to use EXT3 instead of EXT4 and was also released before the TB OTA update), but only after upgrading to 6.5. Could it be some finicky problem with EXT4?

meatrocket said:
Could it be some finicky problem with EXT4?
Click to expand...
Click to collapse
Actually, forget this part. I forgot I used HoneySense 4.0 with EXT3 & still had the random shutdown problem.

with it plugged in do a nandroid backup and then restore to stock then restore back with only restoring system and data

I know its not the battery because it will stay in CWM for several minutes and much longer than it does on without any random shutdowns. Going to try the return to stock and reflash method and post back.

Ok, so that I get this right, the test plan is to: flash back to stock, re-root & then reflash to a new ROM such as Coredroid 6.8? If that's what one of you are going to do, then I'll do it also so we can see if we get the same results.

Well, I actually downgraded to RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed, went through Bubby's One Click and the damned phone shutdown upon boot to the first image of Bubby's. I figured MAYBE something was wrong with Bubby's One Click as I had originally used the ACE hack kit.
I reverted back to RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_26.06.04.06_M_release_166557_signed again & decided to use it for a minute to see if it shutdown and it DID!
There is either (A) a problem with my battery or (B) a problem with the charging system on my phone. This IS NOT a firmware/radio issue! It may be different for you, but I'm positive about my phone now. I'm going to wait until my new batteries come in on Wednesday and if it acts the same, I'll be replacing my phone under warranty. I should also note - I've never overclocked this phone, so I don't want anyone fear-mongering the N00BS about "see what overclocking will get you"!

Does yours stay on when its plugged in?

samftw said:
Does yours stay on when its plugged in?
Click to expand...
Click to collapse
Yes. I noticed the shutdowns started about 1½ to 2 weeks ago. It got more frequent as time went on. The phone is practically unusable now unless I leave it plugged in. I suspect that if it is indeed the battery, it may even start shutting down when plugged in since the phone will turn off if you remove the battery when it's plugged in. Just a hunch.

same exact story here totally bummed right now but at least i work for at&t so getting anew battery shouldnt be an issue. still a huge pain in my ass

samftw said:
same exact story here totally bummed right now but at least i work for at&t so getting anew battery shouldnt be an issue. still a huge pain in my ass
Click to expand...
Click to collapse
Well, bummer dude. I called AT&T and they said that the battery was covered under warranty & they'd be happy to send me one right out. The only problem was that they didn't have any in stock! They offered to credit my account with whatever I have to spend on replacing the battery myself. When I get the 2 batteries from Amazon & make sure they work, I'll get the credit for them applied to my account. It was only $25 for 2 batteries & charger shipped.
I called my local AT&T Corp stores to see if they had any batteries for the Inspire & they didn't either. Me thinks this widespread shortage of batteries could be indicative of a bigger problem.

WoW! Here's the feel-good part of this story....
As I posted earlier, AT&T service didn't have the battery to send me. I couldn't find a battery anywhere - I called the 2 AT&T Corp strores, BestBuy and Batteries +.
I went to the AT&T Corp store where I bought the phone & signed in for help. The girl came over to help as I was explaining to her what was happening & telling her that I wanted to take the battery out of her demo phone to make sure it was the battery. If it wasn't, then I could call service back & have them ship me a repalcement phone instead of having to wait until the batteries I ordered off of Amazon arrived.
She told me that she didn't want me to mess her floor phone up & offered to go in the back & get a phone to test with. She came back with a new battery still in the plastic. I popped it in and sure enough, it has been the battery! I told her thanks and that I felt a lot better knowing that it was indeed the battery.
She insisted that I keep the new battery since there were none to be found & she would "adjust" the phone she took the new battery from. I assume "adjust" is speak for "send it back as defective". I'm really positive about the whole experience, especially since she didn't have to do that at all. You can bet I'll be going back to that Corp store & buying from that rep when I'm ready to get my Samsung Galaxy S II!

I'm having the same problem I don't know why it's doing this
Sent from my HTC Inspire 4G™ using the XDA App.

King Askaba said:
I'm having the same problem I don't know why it's doing this
Sent from my HTC Inspire 4G™ using the XDA App.
Click to expand...
Click to collapse
Uh...did you read ANY of the thread or just post a reply? It seems rather obvious that there's a battery problem. Maybe you could do some of the same or similar testing we did to see if you have similar results?
The only thing I didn't say in all of this is that I got my phone on 2/14/11. So I've had it almost exactly 4 months before the problem really came up.

Ns4g ics battery charge

I'm trying to figure out if this problem is just my phone or an actual issue. I just got this phone 2 days ago from craigslist after being with the evo for almost a year. As soon as I got it, I rooted it n tried flashing ics roms themed and original leaked update. On every rom I flashed, the phone wouldn't recognize the charger or usb or it would tell me its charging but it would take 6 hours to gain 6% more battery? I also tried turning the phone off to charge but that didn't work either. Anyone know anything about this n what I did wrong or didn't do?
Sent from my Nexus S 4G using xda premium

I've had the exact same problem, i bought a NS4g from craigslist that wouldn't charge or turn on without a charger being plugged in. Long story short, i eventually got it back from Samsung with the warranty being voided due to water damage. So i opened it up and found some oxidation resudue and cleaned it off by scrapping it off. Luckily it worked!!. For you it might just be the battery since it actually says 6%, try to replace with another battery or place the battery in the freezer for 5 mins and try it again.

I flashed the unofficial leak rom again n it charges now but it doesn't say its charging on the lock screen or on the battery icon, but in the system info it says its charging? I have never ran into this type of issue before?
Sent from my Nexus S 4G using xda premium

Exact Same Problem
I was given ICS 4.0.4 via OTA update by google... It worked fine for like 2 months then exactly the same problem arises with my Nexus S i9023 (unrooted).
1. It's doesn't indicate on the lock screen that it's charging nor it indicates on the battery icon, however it does tells me that the battery is charging when I check the battery in the settings. This issue exists on both wall chargers and usb cable.
2. It doesn't asks me to mount mass memory of my Nexus S and my windows 7 machine says it cannot recognize the device..
I strongly suspects it's a bug in the ICS...
I would appreciate any help that I can get on this issue... but to be honest I read many threads here and I can't understand half of what people are trying to say, so I request to keep things a bit simple because I know nothing about how to root or flash or doing any other super geeky stuff ...
thanks

Some people have had luck just cleaning the USB port with a dry toothbrush and a can of compressed air. Might just be dirt. Worth a shot.

thanks mate,
Yeah, tried cleaning it with a brush... still no luck..

Randomly shutting off

For some reason my sensation appears to have gotten into the habit of randomly turning itself off, and I can't figure out why.
It's rooted, and was using InsertCoin's GB rom for a bit until ICS roms got more stable. I've tried InsertCoin's ICS rom and also Virtuous Inquisition, and had been using the 3.24 firmware. I'm also using an anker battery that's three months old.
I first noticed the random shut downs on the ICS InsertCoin rom, but I'd been using it for a few weeks before it started happening, no apps had been changed or updated at around that time, it simply started shutting off. No menus or dialogs, just an instant loss of power, and could happen at any time, in my pocket when sleeping, in a call, or otherwise active in my hand. Totally random. I could turn it back on, but more often that not it'd just die again within a few seconds of finishing the bootanimation. It appeared to happen most when the battery level was below say 50%. The only thing that seemed to stop it at the time was plugging it into a power source, as then it'd be fine.
Thinking it could have been down to the rom's power management stuff (and me getting sick of the frequent sense reboots anyway), I then tried another rom, Virtuous Inquisition. And as soon as I'd flashed that and set all my apps up again (backups created while using the ICS InsertCoin rom right before flashing the new rom), it ran perfectly for weeks. So that seemed to suggest it was the old rom to blame.
Except recently the random shutdowns have started again, exactly the same behaviour as before. I then thought it could have been the SebastianFM undervolted kernels if my phone didn't like being undervolted, but flashing the regular ones made no difference either. I then found the new 3.30 firmware was available a few days ago, so flashed that. The phone instantly ran a bit quicker and had better mobile and gps reception, and it didn't seem to shut down randomly again. Until today that is.
What the hell could it be? It can't really be software because I've tried different roms, though they're probably based off the same leak. But if it was the rom, why haven't more people reported this issue? I've also tried different kernels and firmware, which haven't helped stop it shutting off either. I've checked the battery terminals and there isn't a loose connection, but could it be the battery itself at fault? Thinking about it, I fitted the anker battery before this started happening, but I'd had it a few weeks before the shutdowns started happening. I've not tried putting the standard battery back in yet as I quite like my battery lasting a day, but I suppose it's worth a shot if for some reason my anker is a dud. Is there any way I could check it?
What are your thoughts? I really want to get to the bottom of it...

StuartTheFish said:
For some reason my sensation appears to have gotten into the habit of randomly turning itself off, and I can't figure out why.
It's rooted, and was using InsertCoin's GB rom for a bit until ICS roms got more stable. I've tried InsertCoin's ICS rom and also Virtuous Inquisition, and had been using the 3.24 firmware. I'm also using an anker battery that's three months old.
I first noticed the random shut downs on the ICS InsertCoin rom, but I'd been using it for a few weeks before it started happening, no apps had been changed or updated at around that time, it simply started shutting off. No menus or dialogs, just an instant loss of power, and could happen at any time, in my pocket when sleeping, in a call, or otherwise active in my hand. Totally random. I could turn it back on, but more often that not it'd just die again within a few seconds of finishing the bootanimation. It appeared to happen most when the battery level was below say 50%. The only thing that seemed to stop it at the time was plugging it into a power source, as then it'd be fine.
Thinking it could have been down to the rom's power management stuff (and me getting sick of the frequent sense reboots anyway), I then tried another rom, Virtuous Inquisition. And as soon as I'd flashed that and set all my apps up again (backups created while using the ICS InsertCoin rom right before flashing the new rom), it ran perfectly for weeks. So that seemed to suggest it was the old rom to blame.
Except recently the random shutdowns have started again, exactly the same behaviour as before. I then thought it could have been the SebastianFM undervolted kernels if my phone didn't like being undervolted, but flashing the regular ones made no difference either. I then found the new 3.30 firmware was available a few days ago, so flashed that. The phone instantly ran a bit quicker and had better mobile and gps reception, and it didn't seem to shut down randomly again. Until today that is.
What the hell could it be? It can't really be software because I've tried different roms, though they're probably based off the same leak. But if it was the rom, why haven't more people reported this issue? I've also tried different kernels and firmware, which haven't helped stop it shutting off either. I've checked the battery terminals and there isn't a loose connection, but could it be the battery itself at fault? Thinking about it, I fitted the anker battery before this started happening, but I'd had it a few weeks before the shutdowns started happening. I've not tried putting the standard battery back in yet as I quite like my battery lasting a day, but I suppose it's worth a shot if for some reason my anker is a dud. Is there any way I could check it?
What are your thoughts? I really want to get to the bottom of it...
Click to expand...
Click to collapse
Hi,
Do you have any apps on your sd card?
Apparently,this can cause problems.
Go to settings-->apps-->on sd card and untick anything there...

I do at the moment, but I've tried with all apps on internal memory and it made no difference, the shutdowns still happened. In fact I've found no issues with apps2sd on ICS roms whatsoever.

I had the EXACT same issue with ALL ROMS, GB and ICS. Like you it would begin when the battery was below 50% and everything:/ I just sent it to HTC the other day hopefully it gets fixed. And I doubt it was the battery because i was using the stock battery.
I was thinking about opening a thread about this were everyone would post their setup and every detail possible to get to the bottom of this. But i decided not to since it was most likely a hardware problem and would get flamed since there are already countless threads about someone complaining about this.

Well the stock battery is charging back up now anyway so I'll give it a go. I really don't want to have to send it back though given it's rooted, s-off, etc etc. I don't fancy trying to get it back to stock just to see if they might possibly fix it.

same here
Exactly same problem here with virtuous inquisition 3.5.0 and an banker battery...

A few days on with the standard battery, and no random shut downs yet. It's lasting me a day with moderate use too.

I have the same problem before. Sent back to Bell, and they can't fix it. Then I found this app called Captivate Keep Alive. It take a bit of the battery life and ram, but it solve the problem. The phone never shutdown by itself any more. Hope that helps.

Claimj said:
I have the same problem before. Sent back to Bell, and they can't fix it. Then I found this app called Captivate Keep Alive. It take a bit of the battery life and ram, but it solve the problem. The phone never shutdown by itself any more. Hope that helps.
Click to expand...
Click to collapse
damn, this is a good fix but uninstalled because the ongoing notification. I'm not buying the pro version when the developers might come up with a fix in their roms

Same problem here, the problem was more often with the anker battery than with the original battery.
Now i'm back to S-ON and stock roms, it isn't turning off anymore but the problem went over in rebooting...
Only thing i have to do is find an Vodafone RUU for the netherlands , because it was branded and then I will send it back to HTC...
Really annoying... sometimes people ask why they always get your voicemail -> phone turned off in my pocket again...

Claimj said:
I have the same problem before. Sent back to Bell, and they can't fix it. Then I found this app called Captivate Keep Alive. It take a bit of the battery life and ram, but it solve the problem. The phone never shutdown by itself any more. Hope that helps.
Click to expand...
Click to collapse
Unfortunately my issue was the other way round. Mine used to do it below 50%, not when fully charged. It also never happened when it was plugged in. It isn't down to the CPU going to sleep, as I could be using the phone at the time it happened, literally just as if the battery was pulled. Then if I turned it back on it would repeatedly shut off again, until plugged back in.
It's still fine on my standard battery by the way.

my dad on bell is experiencing this issue with his Sensation "4g" lol, with stock battery stock rom s-off stock stock stock.
constantly turning off in pocket, never heard of it happening while in use. waiting for ICS update, if it doesnt fix going for warranty.

Yup, if it's not the original battery, then that problem can happen quite often. Not just phones, it's other electronics also. I had a MacBook, I bought a battery from a third party and the computer shut off randomly. Same with an Asus laptop I bought afterwards and changed the battery.

Ok so I've been having this same problem myself since Christmas.. it started happening on my original battery and on various firmwares ,kernels and rims.. so I bought an anker battery..
It was fine then for a week or two but started happening again.. I read oh about 10 different threads on this subject and what works for me to stop this is switching 3g gsm mode from auto to 3g only.. haven't had a problem while this is switched.. coverage in my house isn't great so I hope there is a permenant fix for this soon

Exactly the same problem.. Turns off when in pocket, hand and even when kept aside .
And Everything's stock. Battery, version etc etc.
Still can't figure out what the problem is.

It can also happen with a standard battery if it's faulty. Get HTC to send a replacement.

Mine is still having it... really annoying, even with the new ICS. Everything is stock now.
I also want to send it back to HTC, but I think they are going to test it first... chance is high that it wont shut off then -> phone back and the problem is still there..... That would be an endless story

have you guys seen this thread:
http://forum.xda-developers.com/showthread.php?t=1475602
Seems kind of silly to have two parallel conversations on the same topic...

I had this exact problem on a stock battery with any rom. The fix that worked for me was changing the network settings from Auto WCDMA/GSM to WCDMA only. It was something to do with transition between 2g and 3g.
Bizarre problem and I hope there is a better fix available soon!
Sent from my HTC Sensation Z710e using xda premium

Not happy, I thought it was the battery but it's started doing it again, even with the standard battery instead.
Just had a look, and on my ics ROM I can't find the option to change the wcdma settings, so I can't try that. Not sure how that could cause it though, because it can even shut off while showing the boot animation! The only thing that seems to stop it is plugging it in, meaning it was no longer using the battery. Hence my assumption that the battery was at fault, but I've tried three different batteries on it now and it happened with any of them. Not much chance that all of them have exactly the same fault.
It can't be a loose connection since if it was I wouldn't be able to turn the phone back on in the first place, so what the hell could it be? I don't think I ever had the issue until going to ics, but I've tried different ROM's and the issue didn't go away. I've tried different kernels over time, and also upgraded the firmware and radio a couple of times too. None of which cured it, so I can't see how any of them could be the cause since it happens on all of them.
Any ideas?

[INFO]Software related charging issue on S4

Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED

minirx7 said:
Hi guys,
Had a very weird issue yesterday with my Rogers S4. I have flashed a bunch of ROMS in the past, but wanted to try the new MEA firmware based ROMS..
Well yesterday i tried Mint Jelly v2.1 (flashed via TWRP) and immediately without rebooting flashed 005 FAUX kernal to avoid boot loops. My battery was about 15% at the time. The flash took, and the phone rebooted into the ROM no issues.
Noticed that when i plugged in the charger to my S4 it was NO LONGER charging. I tried multiple 2.1amp chargers, and cables, including OEM, and it no longer charged. However it charged my NOTE2 with no issues.
This is when i was about to FREAK.. but i recall from my HP Touchpad days that sometimes if the battery dies, you need to do something special to get hte phone to charge back up again.
So what i did, was completely shut down the phone, and plug it back in the charger, and it started to charge again. But immediately booting into Android, it would still no longer charge!!.. So i let it charge up for an hour wiht the power off. Once i booted in again, the phone was able to charge again normally with all my chargers while booted in.
I thought my situation was a freak incident until i noticed another XDA member report the same issue. This is NOT a hardware issue, but something related to software.. So give my advice a shot incase you encounter this yourselves!
ED
Click to expand...
Click to collapse
Never flash anything or make major changes to your phone with a low battery (below 70%).

I may be the member he was talking about. I had a thread on this. Only difference was my phone wouldn't charge at all. When I plugged it in when it was off it would boot loop the charge screen. It was rooted and I had some bloat frozen, but the issue started after I installed Sugarsync. I had the same configuration for a few days with no problems, and my battery was about 50 percent when I tried to charge.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Just trying to help. I freaked yesterday because no matter what i did, it wasnt charging. But once i fully powered off, it started chargin!!

scott14719 said:
Never flash anything or make major changes to your phone with a low battery (below 70%).
Click to expand...
Click to collapse
I just flashed a ROM with 56%. I like to live dangerously.

AdePower said:
I just flashed a ROM with 56%. I like to live dangerously.
Click to expand...
Click to collapse
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.

scott14719 said:
It's definitely possible and usually will work just fine. There are a couple of reasons to flash on a full battery. If something goes wrong and takes a lot longer than originally anticipated, there is less chance of the battery going dead while things are being fixed. Plus, many ROMs (Kernels actually) enact different power profiles for different stages of charge. If this is the case, flashing might not go as anticipated.
Click to expand...
Click to collapse
I bricked a S2 like that. Flashed a rom adn the battery drained in the process, causing it not flash properly. phone was dead, no download mode or anything.

OnePlus One Charging Issue (URGENT)

Hi Everyone here at XDA,
I've been a keen follower of the various ongoings at XDA, ever since my first Android phone the Motorola Defy. I've had quite a few phones since then (currently rocking a yet unmodified Nexus 6P) and I've mucked about with all of them, soft bricked a couple but I've always found a way back from the dead. However, this is something that has me well and truly mystified.
My fiancé bought a OnePlus One a little over a year ago, she had some problems with the microphone during phonecalls (most likely the issue a lot of people had with the noise-cancelling mess-up) so I switched her from stock onto CyanogenMod 13, and no problems since. Phone works a charm.
But recently everything has been going south.
About two months ago the phone started charging STUPIDLY slowly, so I used an energy monitor you plug into the socket to see what was going on. Charger would pull about 2-4 watts, but if you kept plugging and unplugging the phone eventually it would pull about 8 watts, which was adequate. Then things got worse. With the phone turned on, the charger would pull barely 2 watts, turn it off, immediately it would pull 9 watts.
Now it's started to randomly reboot, sometimes getting stuck in a bootloop for 5-10 minutes before booting again. I've spent all day today flashing various ROM's and kernels, and still the issue persists.
We've tried the phone with different chargers to the same result.
Has anybody got any idea what's wrong with the bloomin' thing?
Any advice on what I could try would be massively appreciated.
Cheers in advance

danieljh10 said:
Hi Everyone here at XDA,
I've been a keen follower of the various ongoings at XDA, ever since my first Android phone the Motorola Defy. I've had quite a few phones since then (currently rocking a yet unmodified Nexus 6P) and I've mucked about with all of them, soft bricked a couple but I've always found a way back from the dead. However, this is something that has me well and truly mystified.
My fiancé bought a OnePlus One a little over a year ago, she had some problems with the microphone during phonecalls (most likely the issue a lot of people had with the noise-cancelling mess-up) so I switched her from stock onto CyanogenMod 13, and no problems since. Phone works a charm.
But recently everything has been going south.
About two months ago the phone started charging STUPIDLY slowly, so I used an energy monitor you plug into the socket to see what was going on. Charger would pull about 2-4 watts, but if you kept plugging and unplugging the phone eventually it would pull about 8 watts, which was adequate. Then things got worse. With the phone turned on, the charger would pull barely 2 watts, turn it off, immediately it would pull 9 watts.
Now it's started to randomly reboot, sometimes getting stuck in a bootloop for 5-10 minutes before booting again. I've spent all day today flashing various ROM's and kernels, and still the issue persists.
We've tried the phone with different chargers to the same result.
Has anybody got any idea what's wrong with the bloomin' thing?
Any advice on what I could try would be massively appreciated.
Cheers in advance
Click to expand...
Click to collapse
Different cables as well? The cable seriously does make or break it.
If not that, not sure what it could be... What I can say is, replacing the battery isn't terribly difficult, so if you suspect that at all, it's a fix you can do yourself and for pretty cheap.
Sent from my A0001 using Tapatalk

Elius2676 said:
Different cables as well? The cable seriously does make or break it.
If not that, not sure what it could be... What I can say is, replacing the battery isn't terribly difficult, so if you suspect that at all, it's a fix you can do yourself and for pretty cheap.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Thanks for the advice, but sadly it's not the cable. Or the charger for that matter. The readings I get from the energy meter are too consistent. After plugging and unplugging several times the phone will eventually pull EXACTLY 3.8 watts. No more, no less, irregardless of battery percentage. As soon as the phone is turned off and plugged in, starts pulling anywhere from 7 - 12 watts, which is normal pull I expect.
Hence why I suspected a dodgy kernel, but no luck :'(

Hello
Hello, I had a not that much similar problem a month ago but i'm sharing and it might help (you never know). I was on a custom CM13 based rom and phone started overheating even when not in use, charging slow. When I let it charge overnight I would find it very hot and almost always stuck and 99%. Clean flashed different roms and the same continued to happen and it really got me worried!
Than I thought before ordering a new battery or charger lets try something really stock. I installed lastest OxygenOS and viola problem went away. (be careful and follow the steps you need to flash OxygenOS, it is NOT recommended you flash it via twrp). After that flashed twrp again and custom roms and havent had that problem again.
Hope it helps

Yeah, I would say your most probable culprit at this point might just be the OS. Try a clean flash and/or a different nightly or release. Try also a different Gapps package (you never know if it's not so much the OS, but maybe an interaction between OS and other software.
Sent from my A0001 using Tapatalk

Thanks for the advice, I've finally managed to free up an evening tonight so I'll try putting the phone back to stock. Hopefully it'll work! I'll post back to let you know if I've had any luck.

Put the phone back to stock Oxygen OS, and no luck. Going to use the Tamper Reset Script and try sending it back to Oneplus. Makes me sad that I couldn't sort it myself :crying: