Related
My S3 is about 10 months old, and over the last week I've experienced a problem where the screen will not wake up. The first time I thought the phone may have shut down, but then I noticed that in some cases the notification light was flashing, but pressing the home or on button didn't do anything. I tried calling it, and it appeared to ring (from the phone I was calling) but there was no tone and the screen remained off (with no missed call recorded). Only solution is to remove/replace battery and start it.
Tried to search online for a solution but all I could find is that either it's dying, or some app is causing this, with one entry mentioning chrome. Uninstalled chrome and the problem has not reappeared but it was quite random before, first happening once and then again after several days, and yesterday several times in one day, so I need more time to see if chrome was the culprit (I'm not too convinced otherwise there would be more mention of this).
If anyone has any idea please let me know. Phone in unlocked from purchase, not rooted, stock, fully updated.
This comes at a time when I want to buy a dual-sim android phone as I have 2 numbers for work/travel purposes. Annoyingly none of the top manufacturers produce high performance phones that are also dual sim. Closest I found is the Samsung Galaxy Grand Duos, which seems not bad bit lower spec than the S3 and a bit larger (S3 about as large as I'm prepared to go). Again if anyone has any advice I'd appreciate it.
just to add, I did a factory reset a short while ago as the phone felt a bit laggy compared to earlier use, and after reset was behaving better until this problem appeared
My S3 has behaved similarly 4-5 times since summer. Only removing battery helps. Few days ago it happened two times in row. Screen is off, no way to make it wake up. Removed battery, reboot. When screen went off again, same story again. Had to remove battery again. And in the night phone was making complete restart with PIN asking (usually it makes only android starting again without asking PIN code for SIM). I woke because of that Samsung starting sound. Next day phone just ate battery while being "idle". Basically from 100%-5% within workday just lying on the desk. After several reboots and charging to full battery it behaves as usual, -0,5% per hour.
tomuser said:
My S3 has behaved similarly 4-5 times since summer. Only removing battery helps. Few days ago it happened two times in row. Screen is off, no way to make it wake up. Removed battery, reboot. When screen went off again, same story again. Had to remove battery again. And in the night phone was making complete restart with PIN asking (usually it makes only android starting again without asking PIN code for SIM). I woke because of that Samsung starting sound. Next day phone just ate battery while being "idle". Basically from 100%-5% within workday just lying on the desk. After several reboots and charging to full battery it behaves as usual, -0,5% per hour.
Click to expand...
Click to collapse
Thanks, will see if the problem goes away for me also. I normally charge it fully quite often, since I usually keep it on charge overnight, and I have a second battery with a battery charger so I often swap batteries to put a fresh one in. I rely on my phone a lot for work so not sure I can afford to wait much longer, I think I'll buy the Grand and just put up with the lower specs...
Hey guys.
I have a problem with my HTC EVO 3D. I've been using it for a year and everything was fine until yesterday. I was playing Real Racing 3 when my phone suddenly restarted and then turned off before I could enter my PIN code and didn't boot up. I thought that it might have overheated or it was some crash or something, I put the phone to charging and it easily turned on (I must mention, that there were about 70% battery left). I charged my phone and didin't use it whole afternoon. In the evening, I was trying to unlock my phone (with about 70% of battery) when suddenly the same happened again - the phone restarted and before entering PIN code turned off at all. After that I wasn't able to boot my phone.
I tried charging it with original HTC AC charger and also using my laptop and even a car charger, but nothing changes.
When the phone is not plugged in to charging, it doesn't show any signs of being alive. I tried pressing volume down/up/camera buttons + power on button, taking off the battery for about an hour, charging the phone for ~6 hours. Nothing works.
However, I realised that when I connect the phone to my laptop, there is a 'new device is connected' sound, but I am not able to access my memory card or do something else. Also, when the phone is charging, the red charging light is on, which after a few hours turns to green and after some more time disappears at all. When trying to turn on the device while it is charging the red light disappears as soon as the power button is released ant comes back after about 20 seconds.
Sorry for such long story and for my bad English. I am very disappointed. I still have a warranty, but I dont want to take the phone there, because the fixing lasts at least 2-3 weeks and also since I'm unable to boot my phone, there are a lot of my personal information in it, such as passwords,messages, bookmarks and so on, left.
So, is there anything I could do or should I take my phone to service?
P.S. The phone is not rooted and never was. Everything is original and up to date.
shvogrius said:
Hey guys.
I have a problem with my HTC EVO 3D. I've been using it for a year and everything was fine until yesterday. I was playing Real Racing 3 when my phone suddenly restarted and then turned off before I could enter my PIN code and didn't boot up. I thought that it might have overheated or it was some crash or something, I put the phone to charging and it easily turned on (I must mention, that there were about 70% battery left). I charged my phone and didin't use it whole afternoon. In the evening, I was trying to unlock my phone (with about 70% of battery) when suddenly the same happened again - the phone restarted and before entering PIN code turned off at all. After that I wasn't able to boot my phone.
I tried charging it with original HTC AC charger and also using my laptop and even a car charger, but nothing changes.
When the phone is not plugged in to charging, it doesn't show any signs of being alive. I tried pressing volume down/up/camera buttons + power on button, taking off the battery for about an hour, charging the phone for ~6 hours. Nothing works.
However, I realised that when I connect the phone to my laptop, there is a 'new device is connected' sound, but I am not able to access my memory card or do something else. Also, when the phone is charging, the red charging light is on, which after a few hours turns to green and after some more time disappears at all. When trying to turn on the device while it is charging the red light disappears as soon as the power button is released ant comes back after about 20 seconds.
Sorry for such long story and for my bad English. I am very disappointed. I still have a warranty, but I dont want to take the phone there, because the fixing lasts at least 2-3 weeks and also since I'm unable to boot my phone, there are a lot of my personal information in it, such as passwords,messages, bookmarks and so on, left.
So, is there anything I could do or should I take my phone to service?
P.S. The phone is not rooted and never was. Everything is original and up to date.
Click to expand...
Click to collapse
Perhaps try a new battery or take it in and have them try one. Sounds like a battery issue.
Sent from my SlimRom jb'd EVO 3D.
aqualls said:
Perhaps try a new battery or take it in and have them try one. Sounds like a battery issue.
Sent from my SlimRom jb'd EVO 3D.
Click to expand...
Click to collapse
Thanks. I took it to service. I hope they'll repair it.
I finally got my HTC back a few days ago. They changed the motherboard and I had to buy a new battery since the old one was dead and warranty for it was only a year.
But I've faced several unexpected crashes during these few days. I think 3 or maybe 4 times when I took the phone after not using it for couple of hours and tried to unlock it, the phone didn't unlock and instead turned on. I really don't like this, because if my phone turns off whenever it wants, I may be unreachable
Does anyone knows what that means and what should I do if this keeps happening?
shvogrius said:
I finally got my HTC back a few days ago. They changed the motherboard and I had to buy a new battery since the old one was dead and warranty for it was only a year.
But I've faced several unexpected crashes during these few days. I think 3 or maybe 4 times when I took the phone after not using it for couple of hours and tried to unlock it, the phone didn't unlock and instead turned on. I really don't like this, because if my phone turns off whenever it wants, I may be unreachable
Does anyone knows what that means and what should I do if this keeps happening?
Click to expand...
Click to collapse
This happens on stock rom?
MrJyrks said:
This happens on stock rom?
Click to expand...
Click to collapse
Yes, the soft has always been and is stock.
Then it must be a hardware issue. If your warranty has not expired, take it to the warranty service.
MrJyrks said:
Then it must be a hardware issue. If your warranty has not expired, take it to the warranty service.
Click to expand...
Click to collapse
Well as I said I dont want to take it there because it takes about three weeks or more till I get back my phone.. It would be the third time in two months and it really annoys me.
Couldn't this be software issue? I mean I've been reading some similiar threads and I found out that some app might be killing the phone. So I did hard reset yesterday and after that installed only well known essential apps (Google services and some others) and after that the phone didin't crash for almost two days. Unfortunately, it did turned off a few minutes ago. I've installed only 8 Ball Pool and Smart Keyboard Pro recently, so I will try unninstalling them both and let's hope the phone won't crash again. Is there any ideas what else may I do in case it doesn't work?
shvogrius said:
Well as I said I dont want to take it there because it takes about three weeks or more till I get back my phone.. It would be the third time in two months and it really annoys me.
Couldn't this be software issue? I mean I've been reading some similiar threads and I found out that some app might be killing the phone. So I did hard reset yesterday and after that installed only well known essential apps (Google services and some others) and after that the phone didin't crash for almost two days. Unfortunately, it did turned off a few minutes ago. I've installed only 8 Ball Pool and Smart Keyboard Pro recently, so I will try unninstalling them both and let's hope the phone won't crash again. Is there any ideas what else may I do in case it doesn't work?
Click to expand...
Click to collapse
Id recommend doing a factory reset on the phone and not installing any app for at least a week to confirm its not a hardware issue, but I strongly believe it is. If it fails youll have to take it to a sprint store and hope the clerk is in a good mood and give you a new phone the same day.
try a new battery
The battery is new, I had to buy it only a week ago, because the service stated that the old one was dead.
Hey guys,
Last night I plugged in my LGOG right before I went to sleep. About seven hours later I woke up, woke it up to check the time, then fell back to sleep. When I woke up again a few hours later, my phone was completely dead. No lights go on when charging, nor does it go into the charging mode that happens when the phone is off but charging. The power button does nothing at all. Connecting it to a computer does nothing. I have tried two different wall chargers and a USB plug, and have tried different outlets. The phone is rooted and unlocked. I haven't put any new apps or anything on the phone recently, however I have had a slight overheating issue lately. I don't think that that's what caused the issue though, as when I woke up for the first time and woke it up, the phone was not noticeably hot, and seemed to work fine. Any ideas or suggestions?
Edit: As suddenly as it stopped working, it has started working again, about two hours later. The notification sound buzzed, my phone turned on, and usual on start things happened. However I'm still extremely worried about it. Now that it's on, I assume there's more I can do to figure out the issue- suggestions?
These phones are terribly buggy when charging/when they die, IMO. Worst Android device I've ever had in that respect.
Probably just a fluke, tbh.
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
miller150 said:
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
Click to expand...
Click to collapse
Reboot into recovery and wipe cache+dalvik
Maybe the rom needs a little cleaning
Sent from my CM10.2 OGE973
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
miller150 said:
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
Click to expand...
Click to collapse
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
OMGMatrix said:
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
Click to expand...
Click to collapse
Have mine 2months been careful not to let the battery shut down on its own but thirds past Monday my car charger weren't bad and the phone shut down. Would not except a charge after that. Went to att and they sent me to a service center. They could not charge it either. They replaced it, now making sure my external battery backup its always charged. Do not want to do that again.
Sent from my LG-E970 using xda app-developers app
That sounds like that could actually be the issue. On the previous iteration of carbon I almost never allowed it to go below about 10%. However the new update seemed to be harsher on battery life and it slipped into the 1% range several times...
same thing happened to me running root box with no tweaks or anything. I woke up and the phone was off, been that way for two days now. it wasn't on the charger so its definitely possible that it died. I actually found this thread because I could've sworn there was a report of someone who had to do a battery pull. I'm thinking that's my only option now.
Hi people, nexus 6P owner since 2 years now. I remember when I received the phone I could reach without worries 5 to 6 hours of Screen but then, after nougat and now Oreo, I've never achieved again that numbers.
After rooting my phone, flashing carbon rom and installing elemental X kernel, I played with governor profiles and improved my SOT a little over this year but it was getting worser and worser by every day (2 to 3 hours of screen on time and heavy idle drain). Finally, the real problem came the other day when for the first time my phone shutdown at 29% suddenly after opening the camera.
So I read internet and found in the nexus 6 (not 6P) forums that someone suggested a solution concerning a problem with how the phone meter the battery remaining, suggesting doing a series of steps of charge discharge that I will list here. This, and changing to ABC rom may have done the trick, as now I'm getting much more normal battery life (considering the degradation of 2 years, 2700mah left approximately) of 4, 4 and a half hours (yours will be better) SoT and an idle drain of less than 0,5% per hour, and apparently it didn't shutdown early anymore.
So, give this steps a try if you tried everything like I did and you still having problems with battery drain.
STEPS THAT MAY SOLVE EARLY SHUTDOWN PROBLEM:
- Charge your phone to 100% and use it until it shutdowns (look at what percentage).
- Boot to recovery by pressing power and vol - button, and once in there let it drain the battery until it shutdowns by itself (may take a lot of time so increase brightness to maximum in the recovery menu under settings to consume it faster).
- Now it has really reached 0% and if you try to power it on it won't let you by blinking red in the notification led.
- Plug the charger and leave the phone off until the battery indicator show it's full.
- Unplug it and turn it on, it should show you the battery at less than 100%, like 95%, 90% or even less depending on how bad it was calibrated (mine showed 95%).
- Plug it to the charger without turning it off until reaching 100% and only then unplug it first and then turn it off quickly.
- Plug it one more time (off) until the icon shows it is full and then unplug it and turn it on, now it should say a number closer than before, like 98% or 99% (mine was 99) or it may be 100%. If it shows 100% then you're good to go with the calibration, but if it shows less, repeat the process by letting charge until 100 and then doing the same steps as before until you turn it on without charging and finally it shows 100% battery.
Please report back if this steps worked for you, because for me I think it made the trick.
Now for the battery drain what I did was this steps,
STEPS THAT MAY STOP THE POST-NOUGAT HEAVY BATTERY DRAIN (android OS drain, etc):
-Unlock and Root the phone
- Install ABC rom (check the post here in XDA)
- Flash ElementalX kernel (also here)
- Install the app "ex kernel manager" from the play store
- Enter settings and disable printers (you still can enable them if you have to print something)
- Install Greenify from the play store and select all the apps that don't use notifications.
- Uninstall unnecessary apps that you don't use anymore.
- In the Ex Kernel manager app go to CPU -> governor options and select "load". Choose one of the following recommended profiles: Excalibur V2, Dragon Fly v1, Butterfly or DeadPool. (Or check the guide in XDA about governor profiles).
- Finally activate the run on boot option and reboot to recovery, wipe dalvik and cache and then boot into system.
If you have luck like me, your phone will run very smooth and battery life will be normal to it's current degradation. My phone now last me all day like before and I don't have to charge it twice or three times like I did and best of all, when I don't use it, it almost don't lose battery (2 to 3% overnight).
Also I've never seen again that android system process consuming the same amount as the screen!
I hope this serve someone and maybe save some phones too , I never resigned my 6p because it's a great phone with one of the best cameras out there even today and with great speakers too.
Please let me know if it worked for you! Of course I don't promise it will, but you have nothing to lose anyway! Good luck.
Pd. Sorry for my English , I'm from Argentina
UPDATE: Today my nexus shutdown at 10% but only because I opened on purpose the camera to check if that is the problem, and aparently it is. I've read that when then phone has low power, an app that consumes a lot of battery like the camera may cause shutdown to prevent the phone damaging internal components. So no fix for that at the moment, just don't use the camera with low percentage.
Hi, I don't know if this thread is still on but I'd like to say that I had the same issue. I have a Nexus 6, as you said, and I've installed on it the Resurrection Remix ROM (Neo version). After that, the phone suddenly shut down everytime it reaches 20 or 30 %. I tried two solutions they suggested me;
1) In bootloader menu, go on bootloader logs and press start button for 10 seconds more or less (when you get Google logo and the phone actually boot)
2) Try to reboot the phone in Safe mode and then back in Normal mode
I've also tried to calibrate again the battery (maybe I did it wrong); I followed a guide on it but I can't remember every step of it (if interested I'll try to find it again). Nothing worked, the phone still presents the same issue and I really don't know what to do. I'd like to try this too hoping it works otherwise the last thing I can do, I guess, try to flash again the ROM. Do you have any suggestions? Thanks so much
P.S.
The battery works PERFECTLY; before I flashed the ROM it worked so damn good so I really can't believe that it needs to be replaced, I know that the phone is really old but it always worked fine so it's more logical presume that the problem is with the flashing
Using Stock Nexus 6 Shamu Kernel, with last TWRP and RR OS
Just replace your battery - you might think it's the flashing etc, but at the end of the day my money is on your battery just having called it day, which they can do quite suddenly.
I found that once that early shut down starts it gets worse quick.
It's not that big of deal to change out on these phones anyway and if you do it yourself it's cheap (15 dollars or so). - I've just done it for the second time, not that I was having early shutdowns with my first replacement but after about 18 months life was starting to wane.
Just sharing my experience with my nexus 6p.
Early shutdown problem sure gives us headache. Already tried several methods like calibration, reflashing to factory images, downgrade to minor build or major build, none of them works.
The only solutions that works for me is replace the battery, only cost between $10 to $20 for me (it depend on type battery that you buy, mine is OEM one)
Hello, giving a try to the OP guide regarding early battery shut down. Just a quick question - how long does it take for battery to drain out while in recovery mode? Screens been on for like 2hours now, I see top right screen corner the battery % completely disappear, but recovery still usable. Just wonder, how long it will take for phone to auto shutdown while in recovery mode?
And if this does not work, I'll just replace battery, like @reintakura wrote above.
This device is a disaster. Does it really work?
I tried this the other day. The phone shut off when the low battery came on. I kept powering it up. The first few times it shut off immediately. The next time it turned on and said I had 10% left. Let that 10% run down, it powered off. I kept powering it on... it would boot. I did this maybe 50 times, every time it would boot and then shut down. Then the last time it got "stuck" on the Shutting Down screen. I let it sit like that for a good 10 minutes. It never powered off, it just was stuck on the shutting down screen. I held the power button down to initiate a hard shut down. Plugged it into the charger, device off. Screen said it was 100% a few hours later. Turned on device, device reported 100% used it until it got to 70% and then the low battery light came on and it powered off. Let it charge overnight with device off. Right now it's slowly losing battery, I'm at 76% and it hasn't shut down.
Strange stuff going on.
i was facing the same problem, two days ago i returned to 8.1 abc rom
i'm getting 4h sot and no early shutdown
I can't believe I spent $200 on this **** phone and waited 3 years to get it thinking its the best thing since fried rice, mine started shutting down at 20-30% now it shuts down anywhere from 30-85%!!!!!!!! ahahahahahaha in the end its my fault for buying refurbished, someone obviously sent this crap back already and they did nothing to fix it and conned me into buying it.
Paquinho said:
Please let me know if it worked for you! Of course I don't promise it will, but you have nothing to lose anyway! Good luck.
Click to expand...
Click to collapse
Hi, there. This reply is way late, but I've been away for years and I've only now decided to come back, so I'm necroposting on everything that's relevant to me right now. I hope that's not a serious offense.
I've had my 6P since August 2016. I bought it NOS from Google Fi at a slight discount. It worked like a charm for me for years until around winter 2018/2019, when it started shutting down in the cold. I figured that was understandable. I bike a lot, even in sub-zero temperatures, and I tended to keep my phone in the breast pocket of my windbreaker.
It didn't care too much for that.
So, I started putting it into my backpack and it stopped shutting down.
Then, this summer (2020), the battery went off a cliff. It's been dying anywhere from 80 to 10% since June. Maps and the Camera are the big killers, but the battery will plummet from literally any use.
Yet, it will idle for days if leave it alone.
I recently decided to just wipe the thing back to factory and see if that solved anything. It was quite a feeling to scuttle all of my SMS (I backed them up to my Google account, but it seems like they've gone to some mysterious corner of the Internet from which they cannot be retrieved. Alas). It was kind of a catharsis to throw it all away.
I did back up all my media, however.
The factory reset solved nothing, so I tried the OP's recommendation. I loaded into the bootloader and, instead of waiting on the primary screen, I went into (stock) Recovery (my phone isn't yet rooted) and ran the display test a bunch of times. I alternated between that and selecting "Barcodes" since the all white screen is a bigger drain on the battery than the black and green default.
Eventually, the thing died, but it took hours. This, despite that it would die at the snap of the fingers when in the OS. Strange. I charged the device while off until it said it was full. It came on at 95%. I followed the OP's guide until it turned on at 100.
Yet, it still started draining immediately.
The current culprit is "Mobile Network Standby," which is rich because this phone has no SIM, so why is it even bothering to try and futz with the mobile network? I had been keeping the device on Airplane Mode, but I'd forgotten to turn it back on. I just reactivated that mode, so we'll see if that helps.
However, if I watch a guitar repair video on YouTube (pretty staid, not like gaming or an action movie), the battery just nosedives again.
I don't think that rooting and flashing a new ROM is going to solve this issue.
I bought a replacement battery. I'm just not eager to try and install it. So I may just try root and flash, since it's easier. I guess we'll see what happens.
wedel219 said:
Hi, there. This reply is way late, but I've been away for years and I've only now decided to come back, so I'm necroposting on everything that's relevant to me right now. I hope that's not a serious offense.
I've had my 6P since August 2016. I bought it NOS from Google Fi at a slight discount. It worked like a charm for me for years until around winter 2018/2019, when it started shutting down in the cold. I figured that was understandable. I bike a lot, even in sub-zero temperatures, and I tended to keep my phone in the breast pocket of my windbreaker.
It didn't care too much for that.
So, I started putting it into my backpack and it stopped shutting down.
Then, this summer (2020), the battery went off a cliff. It's been dying anywhere from 80 to 10% since June. Maps and the Camera are the big killers, but the battery will plummet from literally any use.
Yet, it will idle for days if leave it alone.
I recently decided to just wipe the thing back to factory and see if that solved anything. It was quite a feeling to scuttle all of my SMS (I backed them up to my Google account, but it seems like they've gone to some mysterious corner of the Internet from which they cannot be retrieved. Alas). It was kind of a catharsis to throw it all away.
I did back up all my media, however.
The factory reset solved nothing, so I tried the OP's recommendation. I loaded into the bootloader and, instead of waiting on the primary screen, I went into (stock) Recovery (my phone isn't yet rooted) and ran the display test a bunch of times. I alternated between that and selecting "Barcodes" since the all white screen is a bigger drain on the battery than the black and green default.
Eventually, the thing died, but it took hours. This, despite that it would die at the snap of the fingers when in the OS. Strange. I charged the device while off until it said it was full. It came on at 95%. I followed the OP's guide until it turned on at 100.
Yet, it still started draining immediately.
The current culprit is "Mobile Network Standby," which is rich because this phone has no SIM, so why is it even bothering to try and futz with the mobile network? I had been keeping the device on Airplane Mode, but I'd forgotten to turn it back on. I just reactivated that mode, so we'll see if that helps.
However, if I watch a guitar repair video on YouTube (pretty staid, not like gaming or an action movie), the battery just nosedives again.
I don't think that rooting and flashing a new ROM is going to solve this issue.
I bought a replacement battery. I'm just not eager to try and install it. So I may just try root and flash, since it's easier. I guess we'll see what happens.
Click to expand...
Click to collapse
your battery is probably aged, I got the same problem and replacing battery is the only solution that'll work.
Sent from my angler using XDA Labs
Ata Ur Rehman said:
your battery is probably aged, I got the same problem and replacing battery is the only solution that'll work.
Click to expand...
Click to collapse
I reckon that you are correct. However, I am noticing that my phone hasn't crashed since I followed the OPs charging guide. That's something, at least.
Although monstrous battery drain is still a huge problem. I will be swapping the battery.
My question is: root first and flash something custom, just to see what happens? For evidence gathering ... in the name of empiricism.
Or just go ahead with the swap before doing anything else?
wedel219 said:
I reckon that you are correct. However, I am noticing that my phone hasn't crashed since I followed the OPs charging guide. That's something, at least.
Although monstrous battery drain is still a huge problem. I will be swapping the battery.
My question is: root first and flash something custom, just to see what happens? For evidence gathering ... in the name of empiricism.
Or just go ahead with the swap before doing anything else?
Click to expand...
Click to collapse
yeah try root and installing ABC oreo ROM if that doesn't make differ at all then replacing battery is the only solution.
Sent from my angler using XDA Labs
I have two V60s on A11 and noticed for the past two nights one of them will reboot while charging. Only way I notice is because I have to use my PIN in morning to login in instead of fingerprint and one app indicates a restart. This is a replacement V60 that I have had for two days.
Any thoughts?
Are you sure that it's a reboot? I noticed that if I leave my phone idle for a couple of hours (not sure how many, maybe 4 or more?), some kind of security kicks in requiring that I enter my pattern instead of using the fingerprint reader. Pretty sure this has happened both on Android 10 and Android 11. I don't commonly leave my phone idle for 4+ hours during the day, but it has happened just enough for me to notice it. And it definitely wasn't a case of the phone just randomly rebooting itself on me in the middle of the day. THAT, I would have noticed.
Positive it is a reboot. I actually saw it happen this morning. Phone will just shut off and T-Mobile reboot splash screen comes on. I think it is not related to fingerprint reader bug as I have disabled the fingerprint reader on my lock screen/AOD.
Actually been noticing it happens now even when the phone is not charging. I wish there was a way to see which app is causing the problem or get some kind of log to know what is going on.
Hmmm, other than trying to isolate which app is causing the problem, I'd probably suggest a factory reset.
I actually removed all apps and left with factory defaults and it still rebooted during a charge. I have sent the phone back and awaiting a replacement. (This one was the 2nd year promise replacement for a dying G8)
I had to ship the phone back and get a replacement. Everything I tried did not work to stop reboot while charging.
My LG started to freeze, then reboot several times a day, while in use as well as overnight. Sometimes boot loops directly after the logo, so not OS or app related, also without SIM or SD. I had the battery changed (still in warranty), but that behavior continued. So I got a replacement phone yesterday, since it was obviously a hardware issue (I guess it is a RAM failure).