Related
hello,
i have this problem with my gt-i9100.
sometimes when my phone enters deep sleep after a time I can't turn it back on. I've tried calling it, it sounds as if it'd be turned on and ringing from the caller phone, but the sgs2 does nothing, as if it'd be turned off. I can only enter download/recovery and reboot from there
I currently have neatrom xxlsj full, happens with other ics/jb roms as well.
any ideas?
Freshz24 said:
hello,
i have this problem with my gt-i9100.
sometimes when my phone enters deep sleep after a time I can't turn it back on. I've tried calling it, it sounds as if it'd be turned out and ringing but the phone does nothing, as if it'd be turned off. I can only enter download/recovery and reboot from there
I currently have neatrom xxlsj full, happens with other ics/jb roms as well.
any ideas?
Click to expand...
Click to collapse
Sleep of death. Try to change your kernel
Sent from my Nexus 7 using xda premium
so far so good, but i've tried several and all seem to have this problem.
no battery issues?
what kernels and ROMs have you tried?
gastonw said:
no battery issues?
what kernels and ROMs have you tried?
Click to expand...
Click to collapse
come to think about it, i think my phone was like 50% last night, then went to sleep and in the morning it was off and had 0% battery. I'll have to check more carefully, that might be it. Other than that during normal usage i find the battery life quite normal.
this issue happens in wanamlite/neatrom with their respective kernels
i don't remember having this issue in ressurection remix, but i found it quite laggy and even after fixing permissions/reinstalling rom i was getting force crashes while going through settings, so i didn't hang around it too much.
betterbatterystats app is good to finger whats goin on with the battery, in relation to the rom u r actually on.
you can also try cm or stock to see what happens.
from sii xda-ded
i was right, the battery drains like hell when it's in sod.
came back to stock. i'll see what happens
what's going on?
http://dl.xda-developers.com/attach...b15216/50dcdcf8/1/5/9/6/8/9/0/shot_000003.jpg
http://dl.xda-developers.com/attach...ac0520/50dcdcec/1/5/9/6/8/8/9/shot_000002.jpg
Freshz24 said:
what's going on?
http://dl.xda-developers.com/attach...b15216/50dcdcf8/1/5/9/6/8/9/0/shot_000003.jpg
http://dl.xda-developers.com/attach...ac0520/50dcdcec/1/5/9/6/8/8/9/shot_000002.jpg
Click to expand...
Click to collapse
geez, that's a hell of a drop there. Try calibrating....but your looking at a wipe & probably a faulty chip (u better hope not, it's not fun when it's not hardware).
I've seen a couple of guys with this problem, hell sometimes i unplug mine at 65 and goes up to 68 on it's own.
I recall a portugese guy that had a problem like this, he could go from 70% to 1% in a blink; he did get another battery tho.
damn, most likely faulty chip.
i'll try calibrating. either way, i still have the warranty. sucks anyway, they're slow
Hi. I have a very frustrating issue I hope someone can help with.
Over the last 3 days or so, my s2 has started to randomly shut itself down. It only appears to happen when I'm using an app, nothing specific, it can happen anytime.
The battery level has been anything from around 75% to 30%.
Sometimes when I turn it back on, the battery shows I am at 1 or 2 %, making me think it might be some kind of calibration problem, but I've tried the suggested method to no avail. I've also completely fresh installed the Rom I was on (neat Rom) and tried another (disaster Rom) but the problem remains.
Can anyone suggest what could be causing the random shut downs?
Thank you
Karf
Are you undervolting/ under clocking this can cause a sod
Hi. Nothing like that, just used neat Rom or disaster Rom as they come.
sent from my Westcrip powered S2
Your phone(battery) has insane gauge chip search for this it answer in your question(it's only for battery)
Happy new year
Paulius
Hi, thanks for the reply. I'm not sure my issue is to do with the guage chip directly, as my phone will switch itself off at any battery level. The issue designed in the other thread its having something like 56% and then having a much lower value after an intended reboot.
Shutdown it's called sleep of death( scary name) but it not death it's just sleeping forever... it problem with your kernel and battery problem is insane gauge chip...
Happy new year
Paulius
I've just charged to full charge, unplugged - and within 2 minutes, the phone froze, could not do anything - so i pressed the power button until it went off, and it booted back up again without me doing anything - when it booted, it showed i had 2% battery. Then it did the same thing, froze, i had to reboot - then it showed 37% battery.........no idea what's going on apart from maybe a faulty battery...
Buy new battery. It was here on the forum a few times.
Yes. When phone hot(sometimes not) it take battery about 50-60%(I don't know exactly) but sometimes it add battery...
If you flash siyah kernel with stweaks(5 version) you can reset it but chip do funny thing even you reset...
Happy new year
Paulius
try Battery caliberation app ...
if it doesnt work buy a new battery
What are you talking about ? It's not battery Fault it's Insane Gauge Chip.... And Battery Calibration not helping...
I decided to go the whole hog and go back to a stock unrooted ICS, after wiping everything, then CFRoot - then reinstalled Neatrom light - currently restoring apps via Titanium - fingers crossed...
I think you don't have anymore BSOD But if you have flash Syiah kernel
Try new kernel and reset fuel gage
Try installing a new kernel like siyah or dorimanx and then reset your battery log this should resolve your problem if not buy a new battery.
karfeef said:
Hi. I have a very frustrating issue I hope someone can help with.
Over the last 3 days or so, my s2 has started to randomly shut itself down. It only appears to happen when I'm using an app, nothing specific, it can happen anytime.
The battery level has been anything from around 75% to 30%.
Sometimes when I turn it back on, the battery shows I am at 1 or 2 %, making me think it might be some kind of calibration problem, but I've tried the suggested method to no avail. I've also completely fresh installed the Rom I was on (neat Rom) and tried another (disaster Rom) but the problem remains.
Can anyone suggest what could be causing the random shut downs?
Thank you
Karf
Click to expand...
Click to collapse
I think I have a very similar issue. The randomly reboots happens several times a day, it does not happen though when charging (never). By now I'm on jb leak and still have the issue. When it shuts down, the sreen dims a bit and then it's gone, the weird thing is that often I have to pull the battery or charge the phone before reboot is possible, the battery shows different values after rebooting, sometimes close to what was before (especially when rebooting on charger), and sometimes way off the values before. I came initially from slimrom with siyah or dorimanx kernel, I really hoped jb leak would help (also tried different kernels), but it didn't. It also seems to me that it happens more often with the sd card (32gb) and without the phone seems more stable, but still it happens from tme to time. Once the screen dim (only one or two steps) and shut down even happend when in CWM recovery, is it maybe hardware related? It's very hard to find the source of the problem, anybody else experience similar issues? By the way the shutdown I have is not a proper shut down, the phone doesn't show the message "is shutting down".
I've completely wiped, used Odin to go back to ics stock, installed cfroot, then installed neatrom light. Had the same issue, so I've installed siyah, and used stweaks to reset the battery fuel gauge. I've only been off charge for 10 mins so far, but normally it would have shut down by now, so here's hoping...
sent from my Westcrip powered S2
Update - battery was at 89%, and the phone shut down, when rebooted, it showed 28%, then when plugging in while it was shut down, the battery icon showed about 50%. Like a previous reply, it never happens on charge, so it does appear that the battery is knackered, time to go shopping I guess :-\
Sent from my GT-I9100
karfeef said:
Update - battery was at 89%, and the phone shut down, when rebooted, it showed 28%, then when plugging in while it was shut down, the battery icon showed about 50%. Like a previous reply, it never happens on charge, so it does appear that the battery is knackered, time to go shopping I guess :-\
Sent from my GT-I9100
Click to expand...
Click to collapse
I had the same problem - SOD several times a day. I change the batery with a fresh new samsung 2000 mA one.
Unfortunatelly SOD came back, but I found a trick: turn off WiFi. Use it only manually.
For the past 3 months I succeded to have 0 SOD's.
I know that manual WiFi is a setback but it works with those experiencing SOD.
Hope it will be usefull.
Secuence of events that happened BEFORE the problem started:
1-Had a working rom of CM7.2
2-Battery was going out too quickly (7 hours or so) therefore I tried wiping battery data
3-Charged the phone
4- Unplugged it, took a picture
Problem:
One hour later I realised it was turned off...
I turned it on again, it turned off soon afterwards
for a moment it had a problem turning on (it wouldn't go past the cm logo)
afterwards it was even worse; it turned off before even passing the first logo, I couldn't even get it to recovery mode.
Solution Attempt no.1
Tried to get it to stock rom with Odin.
I was able too... but the problem persisted in the new Rom.
Solution Attempt no.2
Tried to get another rom
My situation NOW
I'm back on stock Rom. If I leave my phone alone for like an hour or so it works for 20/30 secs before turning off... After that the problem gets worse till I cannot boot.
Any ideas guys?
How old is the battery? There are apps on playstore to check your battery, thats where I would start. It doesn't sound like a Rom problem, sounds like hardware.ie battery first. Gluck.
Sugartibbs said:
How old is the battery? There are apps on playstore to check your battery, thats where I would start. It doesn't sound like a Rom problem, sounds like hardware.ie battery first. Gluck.
Click to expand...
Click to collapse
Can't have the phone on for 1 minute, forget about downloading and using an app from the store...
I don't know if it's a hardware problem since it happen really suddenly...and just the day after I resetted the battery stats ..... Maybe it is a hardware issue but I want to be sure I tested everything first
Hey, maybe you moved on but I was having the same issue on every ROM.. stock or not. being the detective I am I investigated and inspected.
One of my battery connecting pins is loose even though it's pressed tightly in the case any moderate amount of force or impact loosens it from the contacts.
My temp solution for you would be to add something to the back cover to apply enough pressure to keep the battery still or resolder the copper connectors. The first being easier.
Hit thanks if that helps.
Invest in a new battery. Simple solution.
Sent from my SGH-T959V using xda app-developers app
Ok I've had the Moto Z for a while and its a great phone. Or it was until a few weeks ago. In the space of a couple of weeks a few official updates were sent to my phone and thinking nothing of it I updated as requested. The last update has seriously messed the phone up.
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
What I've tried to do about it:-
- I've tried running in safe mode, which makes no difference
- I've tried a full reset, which makes no difference
- I even unlocked the bootloader and installed a custom OS (Lineage). Thinking that obviously this will wipe out the new update from Lenovo and the phone would have to work properly again. But no, nothing changes, somehow Lenovo have done something beneath the OS that's causing these problems.
The question:-
Does anyone have any idea what could be causing this or have you at least seen these issues before?
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
apocalypse_bg said:
I fail to gasp what is the purpose of the topic and I don't see a question.... If you're looking for compassion, I think the internet is the wrong place.
Click to expand...
Click to collapse
The point of my post is obvious, I've got a issue with my phone and want to know if anyone has seen this issue with the Moto Z before and if they have any idea what may fix it. The question is right there near the end:
"Does anyone have any idea what could be causing this or have you at least seen these issues before?"
Click to expand...
Click to collapse
apocalypse_bg said:
If you're sure that the problems is the updates, downgrade to the latest version that worked well for you. Since you've already unlocked the bootloader, try any of the variety of roms available here to verify you don't have a hardware problem.
Click to expand...
Click to collapse
I've tried a different ROM:
- I even unlocked the bootloader and installed a custom OS (Lineage).
Click to expand...
Click to collapse
Honestly don't know how my post was unclear at all, but I've gone and tried to make it even more clear with a quick edit, hope that helps.
I have exactly the same problem. For me it occurred after updating to nougat. So fare I tried nearly everything. Disabling nearly everything to the bare minimum, custom ROMs, resetting, trying to flash only parts of the Android 6 firmware (modem, Bluetooth, DSP) since a complete downgrade is not possible, using all kinds of battery tools with a rooted device, using custom kernels... I always ended up with a constant battery drain of 3 to 8 percent per hour no matter what I did. Same in flight modus. Since under Android 6 the device didn't show this behavior I think that the problem must be somewhere in the firmware beneath the OS level. An the cruel thing is that sometimes without a reason for maybe an hour or two my moto z doesn't drain an works fine so that I do not believe in a hardware problem.
Thanks for the post. Yeah it seems like something has been changed underneath the OS. I know that sometimes memory config gets changed with newer Android operating systems (at least I think so?), but could that cause all these problems?
BTW, do you have all three of the problems I mentioned? Battery drain, sound stops working and charging stops working?
Since in this condition the Moto z is not really usable for me I switched back to my old phone and I am not using it that much as a daily device, I cannot really tell about sound or charging problems. So far I did not notice those problems.
DonnieDio said:
Problems since the update:-
- Battery drain now has the phone running out in about 10 hours. This problem seems to be intermittent, the majority of the time it happens and drains the phone quickly but not all of the time and usually its Android OS using between 25-50%. Also safe mode has no effect on the problem.
Click to expand...
Click to collapse
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
DonnieDio said:
- Phone speaker stops working. Start the phone up and its working, but after a undetermined amount of time (no more than a hour or so) the speaker no longer works. If I get a call I have to turn on speaker phone to be able to hear anyone. Reset the phone and it works normally, only to happen again soon after.
- Phone charging stops working. Again start the phone and plug in the charger and it works fine. But after its charged, again after a undetermined amount of time, charge no longer works. Plug the charger in and the phone indicates its charging with the little light coming on at the top. But nothing else on the phone indicates its charging and the battery continues to drain. Reset the phone and suddenly it chargers normally. Same thing then happens again given time.
Click to expand...
Click to collapse
None of the above ever happended to me
StarStorm said:
I feel like battery life is a bit worse than with M, but I didn't experience anything as bad as you did. I switched to a custom ROM after updating to 7.0.1
None of the above ever happended to me
Click to expand...
Click to collapse
I've never seen anything like it before. Its so random as well. I mean yesterday I rebooted and then charged the phone before I left for Football at 4pm. At about 11pm that night I heard the battery low sound (45% of the battery had be used by Android OS..). First thing I thought of was that usually the phone wouldn't still be making sounds by now. Since as I said earlier usually the speaker stops working along with charging within a hour or so of a reboot and this had been over 7 hours without a reboot. So I tried plugging it in and it started to charge. But then when I woke up this morning again the sound was disabled and it won't charge, it just took longer for the problem to occur this time..
How can we stop asking to update to this patch?
I has already disabled this on the developer preferences but still asking every 10 minutes
Any suggest please
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
doug107hk said:
Mine even worst. Battery drain fast and mobile away very warm. It suddenly reboot and shown low battery. Battery drain from 50 to 3 percent in a second! Have you guy come across this?
Click to expand...
Click to collapse
Yep I've also had that as part of my problem, though it had only happened a few times over the course of the month so I forgot about it with all the other problems I mentioned going on.
Basically my phone would be sitting on, say 40%, and after a reboot it would start up in the single digits.
I recently tried changing to a custom kernel to see if maybe that was causing the problem (I'd already tried changing OS). But all the problems are still there using the new kernel. Think my next step should be to try to go back to a 7.0 Android version. Are there any custom Android ROMs using 7.0?
It is said that the Motorola Manager can rescuer lost data even if the data has been covered on phone , is it true ?
Just curious what came of this. My Z, unrooted, has started running crazy hot and the battery life is not good. 6-10 hours. When I connect it to my Anker PowerDrive 2 in the car, the battery actually discharges faster or I get the slow charge warning.
Hi I have exactly the same problems as the op and tried resetting to no avail.Its driving me nuts.
Short update about the massive battery drain problem: like I wrote above, in the past weeks I tried everything from custom kernels to custom roms, resetting, deleting and so on. Nothing helped. So I went back to stock and didn't use the phone the last weeks. Today I read in an other thread about bluetooth problems that a fix for the not working bluetooth was to activate flight mode, restart the phone and deactivate flight mode. So I activated flight mode, pressed the power button for 10 seconds or so until the phone restarted an deactivated flight mode. And now the absolute strangest thing happened: for the last 5 hours the phone lost 0% battery in standby with wifi and lte on. Since I did all the mentioned things above without any effect I do not understand this at all but right now I think that this could be a (temporally) fix also for the battery drain problem.
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