Related
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.
I've searched the forums and have not seen anything quite like my problem, so if I missed an important thread, I'm sorry.
Over the weekend, I plugged my Captivate (using a stock battery) into the official Samsung charger and overnight my roommate semi-dislodged the charger. When I woke up and grabbed my phone it only registered a few hours of charging yet still had almost full battery. Upon rebooting the phone, I was sent into a bootloop. Not at the ROM, not at the Kernel, not even at the bootloader. It goes so far as to show the white loading ring at the center of the screen which never moves. At one point, a thin pink line appears halfway through the screen as it shuts down and reboots, never making it any farther. If I plug the phone in, it will boot normally though it does not accurately report battery levels or charging.
Other oddities: after 5 minutes of a phone call, the phone hard crashes. Not FC's, but just goes black. Upon a reboot, I get stuck into the same boot loop. If I plug the phone into the wall charger without a battery, it will go into the turned-off charging animation and show a 100% charged battery. Furthermore, my other roommate has a brand new i9000 so I tried that battery (again, stock Samsung) and it continues in the same bootloop. I have tried flashing other ROMS and going back to stock, but that does not seem to help.
Other info: I was running OneCosmic's ICS 3.1 with no overclock and light undervolting at the time. It was perfectly stable for the few days until the charger dislodged. I am also out of warranty and am not eligible for a hardware upgrade so repairing my Captivate would be ideal. I also have a usb jig if that is of any use to this scenario.
Has anyone experienced anything remotely like this? If not, what debugging steps should I attempt?
What I would suggest is using one of the ODIN one clicks and flash back to stock
Sent from my SGH-I897 using xda premium
I've flashed back to Rogers 2.2 stock. Doesn't help. It actually made it harder for me to get the phone started though I have yet to make a phone call from it.
Have you had the phone for less than a year? if so call at&t(or rogers) and they'll replace it for you.
then try factory reset
then try using odin or rom manager to flash back to stock
When all else fails, flash to cm7. that will completely wipe everything and start from scratch.
if that STILL dost work.... than you can be sure that its a hardware problem :/ theres nothing you can do except replace and sell for for parts.. sorry
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Skoffer said:
You may want to try clearing the battery stats. Something in there may be telling the phone that the battery is completely dead and it shuts the phone down in the middle of the boot. Just a guess, though.
It sounds to me like the phone might have gotten confused aobut how much battery life it actually has. You might also try getting it loaded up and then letting it drain the battery completely down. Reset the stats and then fully recharge the phone.
Click to expand...
Click to collapse
I have exactly the same problem, I did the reset of the battery stats and still not working.
Did you solve the problem?
thanks
Martin
Thanks to everyone for their suggestions, however, no amount of battery calibration could get it to work. Furthermore, a bad flash has made the situation even worse. Now Im bootlooping even when plugged in and when unplugged my jig is of no help. I have declared my Captivate dead.
Best of luck toominds, if you get it to work, let me know. I'd love to have a spare phone sitting around.
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
Well, if you were having this issue before the rooting took place, this very well may be hardware related. There are a few things I recommend before the dreaded unroot and send back to manufacturer route (assuming the phone is under warranty still). It's been proven or at least shown that battery calibration (the whole charge to 0Ma and then fully discharge and then recharge) is a pipe dream.
I would first say find out if the CM7 ROM you're using is OCing or UVing, while you may see some people OCing to 1.3 or higher and UVing -75, not all phones are created equal in capabilities and some phones will randomly freeze/turn off if they don't like your OC and UV settings. I would also suggest flashing a different ROM to see if this problem persists. Cleardroid is what I recommend just to get an idea if it is in fact a OC or UV problem as I believe cleardroid is set up to default stock settings.
You can also try a new battery, I have heard/read/seen that bad batteries can cause reboots. Again though if this was an issue you were sometimes experiencing before, you may have hit the tip of the iceberg on a hardware issue and its finally starting to show now. Hope this helps.
spcclark said:
Hey everyone, thanks for looking at this and hopefully helping me out. I'm new to rooting my phone and installing new roms and stuff, but I researched about as much as I could for about a week before I even rooted.
Now I've moved on and installed a new rom (CM7). Before installing I used clockwork and formated the /system, /data, /cache, and dalvik. At first everything was ok, but after about 15 minutes it turned off. I read up on battery problems, so kept my phone plugged in all weekend (got up to 4.196V-ish, with 0mA in or out) then deleted the battery file, rebooted, unplugged the phone and let it drain completely (even while it still had a charge it would turn off randomly but I figured it would be ok). After it was completely drained I completely charged it again and it still randomly turns off.
At first I thought maybe it was just the rom, but no one else seems to have the same problem as me (that I can find), so I downloaded an ICS rom to try that. Same problems. So far I have done the following to try and find out WTF is going on...
Installed Elixr to see battery drainage (sitting at main screen doing nothing its roughly -8mA, but right after boot or opening a program it jumps to -300mA to -480mA)
Done NUMEROUS battery pulls (with and without deleting the battery config file)
Switched ROMS
Any help would be amazing
PS: Before rooting or flashing a new mod my phone would shut off on its own, but only once a week, maybe. Now it turns off as soon as I unlock my sim card. However, it doesn't turn off at all if I have it plugged in.
Click to expand...
Click to collapse
I guess the issue is with the battery itself. Try getting a new battery. I heard some guys experiencing the same and sorting things out replacing the battery....
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Agoattamer said:
Leave the charger plugged in. If it doesn't reboot then that will let you know most likely it is the battery.
Click to expand...
Click to collapse
That was my thoughts exactly. However, if the ROM or kernel or whatever is set to shut off the phone at a certain reading of discharge from the battery, ie -500mA, this could also be the problem.
I thought it could have been a problem with the phone as well, but before it would shut off on its own MAYBE once a month. 90% of those I attributed to overloading the phone, closing facebook, opening the internet, starting to load a webpage then open a new txt I just recieved while the phone was still vibrating type things.
Now it still feels like it's just quitting on me, it never turns off while the screen is locked or while its charging. So far after the new ROM it has shut off when I place a call, when I receive a call, clicking on a notification, opening the messaging app, clicking download in the market, and my favorite when I unlock it from sleep.
I will download a different rom right now and try it. Just to double check this is what I've been doing to install a new rom... I boot my phone into recovery (vol- and power), go to recovery from the boot screen (opens clockworkmod), scroll down to mounts and storage, have it format /system, /data and /cache, go back to wipe data/factory reset, then install zip from sdcard, select the rom and go... I know some roms require inspiremod, should I still install this if I'm USING an inspire??
Thanks for the input guys, I really appreciate it
If it does turn out to be the battery or you just decide to get a new one to test it out. I recommend these, they are awesome and the only thing anyone should try besides HTC factory replacements. Good luck and I hope this works out for you.
Anker Batteries
i only skimmed this. but cleaning battery contacts can help also check the side door, sometimes that can cause issues as well. air can out everything and clean metal contacts with rubbing (ipa) alcohol.
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
If it doesn't do it when its chargeing then it is the battery. I had bought my inspire from someone and it was having those issues ordered a new HTC stock battery from newegg for like $12 and has been working perfectly since then and honestly if you want the best battery rom absolution is the rom you should check out. It's a non sense rom but again I'd just buy a new battery. I had mine timed it'd reset at 92% 74% and 49% xD
Sent from my Inspire 4G using xda premium
spcclark said:
So I installed cleardroid. Once again everything worked fine for the first 10-15 minutes and then the shutdowns started again, always when making the phone do something (unlocking, clicking a notification, opening a program, etc) but never when the phone is charging.
I'll clean off every bronze or gold contact I can find but I think I might be fighting a lost cause lol. Three different ROMS, all with the same problem leads me to believe its a hardware issue. Since all the chips in these phones are all small and use multilayer boards I won't be able to replace anything myself so I see a new phone in my near future.
Thanks guys!
Click to expand...
Click to collapse
hmm, I would say try a new battery before getting a new phone. Worst case scenario is that you spent $15 to learn you need a new phone as opposed to spending $100+ on a new phone...this is of course assuming you want to keep the inspire and not just looking for a reason to get upgrade ahaha
I agree. It still sounds like a battery issue.
I would agree this definitely sounds like an internal short in the battery. Sounds like it's shutting off whenever it gets a significant load on it. Try a new battery first.
I had a similar issue though I was tweaking the CPU. Learned my lesson.
Sent from my Inspire 4G using XDA App
Yeah, Id bet money that its a bad battery. I had this same exact issue with my Inspire. If it shuts off more in low reception areas but it isn't shutting off when plugged in, its definitely the battery. I would try to find someone with an Inspire and try switching them batteries and see if it stops.
If I tried to use the flash with my camera, the phone would shut off. My phone would randomly reboot or turn off. ATT told me they had "some" bad batches of batteries. My phone was still under warranty so ATT sent me a new battery. All the problems went away!
The battery door on the Inspire becomes wonky the more you open it, I was having a problem like yours, new battery and new door has me going good.
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.
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: