My N10 started to automatically power off a few months ago when the battery indicator showed 10%, and that power-off number gradually increased over the past few months. Two days ago it automatically powered off when the battery was 25%. But the trouble now is that, when plugged in with a power adaptor, the battery does not seem to get charged even though it shows charging when I push the power button. I tried to power it on once, but it automatically powered off again.
Is it an indication that the battery is dead?
Also, when I was trying to remove the battery, I broke some piece around the pins on the orange ribbon cable on the left. What is this cable for? Digitizer? Can this cable be replaced somehow?
Mine started doing the same thing. It only does it if I leave it on standby for a few days. When I start using it, it will say 25% left but it will auto power down immediately. If you plug it in and turn it back on, it says 0%.
Sent from my XT1585 using Tapatalk
Mine started having an issue of not charging, even though it says it is. The battery is currently stuck at 66%. It doesn't shut down on me though. But I powered it off until I could find a solution. I don't think it's a software issue that would be fixed with a factory reset since I tried turning the tablet off overnight and charging it. Still stuck at 66%. When plugged in, it's not discharging. But it doesn't seem to be taking a charge either. Or at least not enough to charge it any higher. My guess is that the battery needs to be replaced. They go for about $30-$40 on ebay. So it looks like that's going to be my best option. I just hope the battery is the issue and I'm not buying a new one for nothing.
After I disconnected the battery for a short while and cleaned the USB port with alcohol, now the battery can be fully charged. However, the orange ribbon cable (under the guy's left hand thumb in this picture http://www.powerbookmedic.com/wordpress/wp-content/uploads/2012/11/nexus10-takeapart-006.jpg) on the left side is broken when I tried to remove the battery. Anyone know what is the cable for? I couldn't find it anywhere (ebay or anywhere else) to buy.
Hi, I had the same problem when did an update to latest cm versions, something around 23.8. And later. I did a rollback to 16.8. CM and charging works, so I am really suspecting latest CM updates for nexus 10 are a root cause of this behaviour. But not tested intensively. Could you try to install older CM versions?
Edit: i havent noticed months ago, I thought few days ago, so my comment is not valid
mark.l said:
Hi, I had the same problem when did an update to latest cm versions, something around 23.8. And later. I did a rollback to 16.8. CM and charging works, so I am really suspecting latest CM updates for nexus 10 are a root cause of this behaviour. But not tested intensively. Could you try to install older CM versions?
Edit: i havent noticed months ago, I thought few days ago, so my comment is not valid
Click to expand...
Click to collapse
I updated my N10 with the August 24 version of CM. Maybe you're right that the battery could be caused by the recent CM version.
mark.l said:
Hi, I had the same problem when did an update to latest cm versions, something around 23.8. And later. I did a rollback to 16.8. CM and charging works, so I am really suspecting latest CM updates for nexus 10 are a root cause of this behaviour. But not tested intensively. Could you try to install older CM versions?
Edit: i havent noticed months ago, I thought few days ago, so my comment is not valid
Click to expand...
Click to collapse
I'm running CM as well. I'll try flashing the newest version. If that's the issue, maybe they have fixed it. If not, I'll try rolling back to an older version and see if that does it and report back. To roll back, do you just simply flash an old version over the existing one? I've never had to go backwards before.
Coming back in here to confirm that my issue was indeed Cyanogenmod. Went back to the last Snapshot and it charged up again.
So I can reinstall Cyanogenmod again without it messing up ?
BackDaws said:
So I can reinstall Cyanogenmod again without it messing up ?
Click to expand...
Click to collapse
Yeah, just flash the latest snapshot. I think the date is 8/20
jsgraphicart said:
Coming back in here to confirm that my issue was indeed Cyanogenmod. Went back to the last Snapshot and it charged up again.
Click to expand...
Click to collapse
How to report it? I am not sure what version does not have this issue. Still running on older version. When having time, Ill try September's version.
mark.l said:
How to report it? I am not sure what version does not have this issue. Still running on older version. When having time, Ill try September's version.
Click to expand...
Click to collapse
Go check out the Nexus 10 cm13 thread. There's a lot of talk about it already
jsgraphicart said:
Go check out the Nexus 10 cm13 thread. There's a lot of talk about it already
Click to expand...
Click to collapse
Hi, thanks, found it and the yalready have JIRA issue for tracking the fix
so we can close this thread I assume as all of us are happy that CM caused drainig our batteries
Related
I've was using 5.2.3 for the last several weeks and to begin with, it worked wonderfully.
Until around 10 days ago, I'd never suffered any rapid battery drain problems, then all of a sudden one morning, I woke up and the phone was at 10% charge despite being left on charge overnight.
I figured there was an issue with the ROM and decided to reboot. This seemed to work fine for a day. Then the same charge problem was back.
I thought the ROM was now failing so decided to install the latest version 5.2.6 directly over 5.2.3 but the problem still persisted so the problems didn't seem to be ROM related but could be due to the unwiped areas but this seemed unlikely.
Just as a final test I decided to change the cable. I normally use the cable provided by HTC as it seems pretty sturdy. Turns out it was the cable all along.
The phone is now charging fine with a different cable and it's running fine again.
So, if you're having problems with overnight power drain when your phone is on charge, try changing the cable.
Edit: There is no visible damage to the cable and it has never been stressed in anyway as I take great care not to stress the pressure points.
Thanks for the info mate. Probably not in the right the right section though.
Your response to that post is probably in the wrong section. Oh, wait..! [email protected]*!t now this post is probably in the wrong section, see what you started.
Sent from my Inspire 4G using xda premium
My cable just stopped working yesterday. Or well, it worked before flashing ARHD 5.2.6 and after it stopped working. I didn't believe it had anything to do with the rom and not sure that I still do, but still an interesting coincidence.
Sorry for posting in the wrong thread everyone. I don't create new threads very often so I wasn't thinking clearly.
Diffler said:
My cable just stopped working yesterday. Or well, it worked before flashing ARHD 5.2.6 and after it stopped working. I didn't believe it had anything to do with the rom and not sure that I still do, but still an interesting coincidence.
Click to expand...
Click to collapse
I'm not saying the cable problem was caused by the ROM - I was just explaining how I identified that the ROM I was using wasn't the cause of the battery drain.
Cables breaking are very rare - happened once to a phone cable once after engineers had been called out to check the fax machine about 6 times before someone gave the cable a try.
Update - After 2 months I couldn't take it any more so I sold it and actually got a rating of "good". The other solution involved a sledge hammer. I can't believe they didn't notice the 1 hour battery life. More proof that quality control worldwide is going down hill. Apologies to who ever gets mine as a refurbished unit or parts from it.
Screenshots
http://forum.xda-developers.com/album.php?albumid=6825
Battery Life from 100% to 0%
ICS .11 & .17 - 6 to 8 minutes (Pic 1)
ICS .21 - 35 to 52 minutes (Pic 5)
ICS .24 - 50 to 65 minutes (Pic 11)
Bug count
RR & Boot Loop - once on may 14th after 2 months on ICS
Battery meter stuck at 100% - 4 times
Irregular charge and discharge cycles - lost count
Battery meter continues to go up a few % after charger is unplugged - lost count
Screen flickered - 8 times
Screen unresponsive / no input - 11 times
No sound what so ever - once
Irregular charging ping sound - lost count
ICS .24 - Finally got over 1 whole hour of battery life from a full charge.
ICS .21 - Since the 9.2.1.21 update I had it 4 times total, it's been alternating with another bug where it goes from charged to zero battery and shuts down the second I unplug the charger. The infinite power bug must only be triggered by OTA update because I tried reinstalling the .21 firmware. The zero battery "bug" could be the result of the infinite power bug allowing the tablet to actually stay on long enough to completely drain the battery. Since .11 update the charging ping sometimes stutters and sometimes plays half a ping and stops. Just had a new bug of no charging ping. The tablet and the sound was on at the time. Battery was at 82% and icon changed to charge mode but no ping sound.
ICS .11&.17 - battery drain from 100% to 0% in about 7 mins and charges up in about the same amount of time. Had this bug for over a month from march onwards. I first got the infinite power bug after upgrading to ICS, it's where the battery meter stays at 100% for hours on end without being plugged in for charging.
My TF101 is from the B30 batch.
I do not have the dock.
I haven't used the camera since HC and I just noticed there is dust on the INSIDE of my case after the "repair". There's no way to clean it except to open it myself. The trim is also now separating a bit from the main body on the top left and bottom left. When I got it back from the repair center it was just a little on the left side only.
Things I have tried
Downgrading to HC, but method was very old and likely not a complete downgrade as it did not work. Battery status wipe, Reboots, factory data resets, cold boots, changing various settings, etc. I sent it in for repair which was a waste of shipping costs. Emailed ASUS twice, response time is longer than 1 week. Calling is much faster but same results no one knew if it was hardware or software problem. After sending it in for repair the left side of my TF101 looks like it had been spudged open so they could have already check the hardware. Dragging around a 12FT extension cord is still currently the best solution I've come up with.
Thanks for making a dedicated thread!
Suggestion: Throw a couple more keywords in the title to help others find it. Eg: based on your symptoms, maybe add something like "battery meter issues, shutdown when unplugged from charger" or something similar.
did you try wiping the device?
I managed to pre order my TF101 a full week before the official release date. Now it's come back to bite me in the rear end cause my warranty is up today. I have the service number and RMA from march so maybe they will still honor it if it turns out to be a hardware issue.
Nullinvoid said:
did you try wiping the device?
Click to expand...
Click to collapse
That would probably be my first step as well, if we assume it's not a hardware problem.
knoxploration said:
That would probably be my first step as well, if we assume it's not a hardware problem.
Click to expand...
Click to collapse
Do you guys mean the factory data reset cause I tried that at least about 25 times by now in the span of a month.
yanbo2012 said:
Do you guys mean the factory data reset cause I tried that at least about 25 times by now in the span of a month.
Click to expand...
Click to collapse
Yep. Have you tried doing a reset and supplying a brand-new Google account, so that it doesn't immediately copy any old data to the tablet? (Or even just not supplying an account or connecting to WiFi / Bluetooth at all, so it's 100% stock)?
Has it ever had a custom ROM or been rooted?
knoxploration said:
Yep. Have you tried doing a reset and supplying a brand-new Google account, so that it doesn't immediately copy any old data to the tablet? (Or even just not supplying an account or connecting to WiFi / Bluetooth at all, so it's 100% stock)?
Has it ever had a custom ROM or been rooted?
Click to expand...
Click to collapse
The bug occurs even if no account is entered. Wifi, gps, bluetooth on or off it still happens. I had it rooted to overclock on android 3.2.1 I rolled back to 3.0.1 to unroot and get ICS, quite regretting that decision as it ran fine except for a few browser crashes which doesn't seem like a big deal now. I also tried downgrading to 3.0.1 from ICS, still had the bugs. It's running stock ICS right now and the browser rarely ever crashes.
did you try up up down down left right left right b a start?
Sorry, couldn't resist....
gee one said:
did you try up up down down left right left right b a start?
Sorry, couldn't resist....
Click to expand...
Click to collapse
If it had a game controller attached I would have tried that also.
yanbo2012 said:
The bug occurs even if no account is entered. Wifi, gps, bluetooth on or off it still happens. I had it rooted to overclock on android 3.2.1 I rolled back to 3.0.1 to unroot and get ICS, quite regretting that decision as it ran fine except for a few browser crashes which doesn't seem like a big deal now. I also tried downgrading to 3.0.1 from ICS, still had the bugs. It's running stock ICS right now and the browser rarely ever crashes.
Click to expand...
Click to collapse
How did you downgrade? It's my understanding that some methods leave the kernel Asus shipped with ICS in place, and hence aren't truly 100% downgrading...
knoxploration said:
How did you downgrade? It's my understanding that some methods leave the kernel Asus shipped with ICS in place, and hence aren't truly 100% downgrading...
Click to expand...
Click to collapse
That's most likely why it didn't work. I had the link to that guide saved but since it didn't work I deleted it. I'll have to wait for an official release or a better more complete method of downgrading.
I had a similar issue with my phone at one point. I went into cwm and wiped battery stats and it seemed to clear my problem up. I'm sure if it would work in this instance but it couldn't hurt to try.
headbangerkorn said:
I had a similar issue with my phone at one point. I went into cwm and wiped battery stats and it seemed to clear my problem up. I'm sure if it would work in this instance but it couldn't hurt to try.
Click to expand...
Click to collapse
Tried that too, twice.
I really don't think this is an ICS issue as you are the only one reporting it (that I've seen). Sounds more like a hardware problem to me....
Sent from my Transformer TF101 using Tapatalk 2
jtrosky said:
I really don't think this is an ICS issue as you are the only one reporting it (that I've seen). Sounds more like a hardware problem to me....
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
I have sent it in for repair, no change. The left side looks spudged open so they could have checked, but no one can tell me if they actually did check the hardware. They ask me to send it back for repair again. If they did replace it with andother TF101 it could be a refurbished one that has other kinds of bugs and be scratched and in worse condition than mine. If they gave me a brand new one it could also still have these or other issues. I am waiting on official or better unofficial way to downgrade to HC.
If anyone knows more about the hardware for the TF101 please post your thoughts on what could be going on with these bugs.
Could your battery not just be simply shagged?
cspiby said:
Could your battery not just be simply shagged?
Click to expand...
Click to collapse
A few days before ICS update I had 7 hours of use out of one full charge. I always shut down instead of sleep. Normal battery life is usually 6 and half to 7 hours and 15 mins. The combined total hours of use during the 100% power bugs after .21 was 4-5. If it is really the battery then ASUS is the stingiest company in the world cause they should have replaced it at the repair center when I sent it in.
has anyone suggested to clear your battery stats in clockworkmod (assuming you have it)
Sent from my Transformer TF101 using Tapatalk 2
My Nook is suddenly taking about 12+ hours to charge, with the OEM cable and plug. I couldn't get it to charge at all at first. I did finally get it fully charged, and it instantly jumped from 78% battery power to 30%. I had tried to clear the battery thing in recovery mode, which might have made things worse.
It doesn't appear to be going into sleep mode, either, as after the 30% jump, I turned off the screen, and the next morning, it was completely drained. Am I looking at a dying battery?
Using one of the latest CM7 nightlies. The problems started after a few weeks of it working fine with the new ROM.
How old is your nook and is it one of the version 1 or version 2 releases?...I had a version 1 doing the exact same thing. Luckly I was still under Warranty and was able to get a replacement, which is the version that was released mid may of 2011 I think. And it had the 5gb data 1 gb media partition...its bwwn working fine and I'm running the cm 7.2 kang w/ mirage kernel.
Sent from my R800x using xda app-developers app
Clear battery stats
d00med said:
My Nook is suddenly taking about 12+ hours to charge, with the OEM cable and plug. I couldn't get it to charge at all at first. I did finally get it fully charged, and it instantly jumped from 78% battery power to 30%. I had tried to clear the battery thing in recovery mode, which might have made things worse.
It doesn't appear to be going into sleep mode, either, as after the 30% jump, I turned off the screen, and the next morning, it was completely drained. Am I looking at a dying battery?
Using one of the latest CM7 nightlies. The problems started after a few weeks of it working fine with the new ROM.
Click to expand...
Click to collapse
Let it completely discharge (screen shuts off and Nook is non-responsive) and then charge it up fully. Any battery problems come after flashing and this method always fixes things.
brsingr said:
How old is your nook and is it one of the version 1 or version 2 releases?...I had a version 1 doing the exact same thing. Luckly I was still under Warranty and was able to get a replacement, which is the version that was released mid may of 2011 I think. And it had the 5gb data 1 gb media partition...its bwwn working fine and I'm running the cm 7.2 kang w/ mirage kernel.
Sent from my R800x using xda app-developers app
Click to expand...
Click to collapse
It's about two (?) years old and version 1. Doubt it's under warranty anymore.
unibroker said:
Let it completely discharge (screen shuts off and Nook is non-responsive) and then charge it up fully. Any battery problems come after flashing and this method always fixes things.
Click to expand...
Click to collapse
Trying that. Thanks.
d00med said:
It's about two (?) years old and version 1. Doubt it's under warranty anymore.
Trying that. Thanks.
Click to expand...
Click to collapse
Hmm ok, well let us know.
Sent from my R800x using xda app-developers app
Im having the VERY SAME prob., my nook is the version 1 with original and non-original Wall & Car charger, got it not to long after it came out, since no one posted more info i will try to have the battery dead as a knob and post the results
meantime any other ideas........ my prob started 2 months ago, been running CM7.2/CM9 Dualboot but gonna just change over to CM 7.2 now.
to run the battery fully down im going to just use the Nook Color Stock
Help people, I have the nexus 4 for over 3 weeks and great but a few days ago when it was nearly full battery (around 80% or so) suddenly shutted down and I couldn't turn it back on until after 1 min or so plugging in. I did not care about it the first time ... But today, after having it charging about 2 or 3 hours I disconnected the cable to use the phone and the battery dropped from 90%+ to 8%, so I connected the cable and put it back to 100%, used it for 1 hour and it suddenly dropped back to 2% from 80% and then shutted down instantly.
Here are some screens.
Help please, and yes I have used the search function, but didn't find the solution on other posts.
tacwold said:
Help people, I have the nexus 4 for over 3 weeks and great but a few days ago when it was nearly full battery (around 80% or so) suddenly shutted down and I couldn't turn it back on until after 1 min or so plugging in. I did not care about it the first time ... But today, after having it charging about 2 or 3 hours I disconnected the cable to use the phone and the battery dropped from 90%+ to 8%, so I connected the cable and put it back to 100%, used it for 1 hour and it suddenly dropped back to 2% from 80% and then shutted down instantly.
Here are some screens.
Help please, and yes I have used the search function, but didn't find the solution on other posts.
Click to expand...
Click to collapse
What apps have you installed lately, maybe there is a rogue one. Install BetterBatteryStats for app behaviour and Cpu Spy for deep sleep issues.
Are you rooted? Custom rom or kernel? Undervolted or overclocked?
gee2012 said:
What apps have you installed lately, maybe there is a rogue one. Install BetterBatteryStats for app behaviour and Cpu Spy for deep sleep issues.
Are you rooted? Custom rom or kernel? Undervolted or overclocked?
Click to expand...
Click to collapse
I'm not rooted, all at stock. I didn't touch the voltages, I didn't do anything. I installed some games (vector, pudding thd, order and chaos) evernote, mega manager, pulwifi.
I'll install betterbatterystats and cpuspy, thank you.
Edit: look what happened to the battery now...
Also I attached a pic of the cpuspy, I can't install betterbatterystats because it costs 2 dollars
tacwold said:
I'm not rooted, all at stock. I didn't touch the voltages, I didn't do anything. I installed some games (vector, pudding thd, order and chaos) evernote, mega manager, pulwifi.
I'll install betterbatterystats and cpuspy, thank you.
Edit: look what happened to the battery now...
Also I attached a pic of the cpuspy, I can't install betterbatterystats because it costs 2 dollars
Click to expand...
Click to collapse
I think there is a free version of BBS on XDA , here http://forum.xda-developers.com/attachment.php?attachmentid=1240843&d=1344068311. Consider buying it on Play in the future if it benefits you.
Battery levels can be inconsistent at times, especialy after deep sleep.
gee2012 said:
I think there is a free version of BBS on XDA , here http://forum.xda-developers.com/attachment.php?attachmentid=1240843&d=1344068311. Consider buying it on Play in the future if it benefits you.
Battery levels can be inconsistent at times, especialy after deep sleep.
Click to expand...
Click to collapse
Here it is, and thanks for the replies.
Look in Partial Wakelocks for the biggest consumers.
gee2012 said:
Look in Partial Wakelocks.
Click to expand...
Click to collapse
I looked but I don't know what does that mean, sorry I'm a little noob. Is there anything wrong with it? I though that was just the sound cause I had it at max while I played after that happened.
Edit: I ordered it by count and the RILJ thing is the one at the top. (its not the attached pic)
tacwold said:
I looked but I don't know what does that mean, sorry I'm a little noob. Is there anything wrong with it? I though that was just the sound cause I had it at max while I played after that happened.
Click to expand...
Click to collapse
I see nothing abnormal on usage, just use the phone and see if this behaviour continues. If it does better do a factory reset or reflash the latest factory image.
gee2012 said:
I see nothing abnormal on usage, just use the phone and see if this behaviour continues. If it does better do a factory reset or reflash the latest factory image.
Click to expand...
Click to collapse
Okay I'll uninstall the latest apps I installed and will use the phone normally, if this happens again I'll do a factory reset and if the problem continues I'll call google. Thank you :good:
I wish I could be more help but I had the exact same issue. I could not figure out what was wrong with it but I had previously broken the screen and sent my N4 back to LG for repair. Since it was still under limited warrenty from that repair I sent it back to them again. They said they replaced the charger connector. I got it back and it seems to work fine now.
My issue started after I updated to 4.2.2 I believe. I don't know the root of it but my advice would be to do what you said and call Google or LG.
stones1313 said:
I wish I could be more help but I had the exact same issue. I could not figure out what was wrong with it but I had previously broken the screen and sent my N4 back to LG for repair. Since it was still under limited warrenty from that repair I sent it back to them again. They said they replaced the charger connector. I got it back and it seems to work fine now.
My issue started after I updated to 4.2.2 I believe. I don't know the root of it but my advice would be to do what you said and call Google or LG.
Click to expand...
Click to collapse
Thank you anyway
Similar issue here - I've been using the same apps since I first installed them after N4 purchase (meaning no new apps/games installed in the last few days and no settings changed). Took a nap for a couple of hours and woke up to see N4 completely dead - 0% batt. Charging it now and looking at partial wakelocks etc, havn't seen anything out of the ordinary. Hopefully it doesn't occur again but in the meantime still looking for a reason why this would suddenly happen.
Are you guys using the stock chargers? And charging through mains?
Rizy7 said:
Are you guys using the stock chargers? And charging through mains?
Click to expand...
Click to collapse
Yeah, am on stock JB 4.2.2, unlocked and rooted though, no other change like new roms flashed or anything. I use the stock charger and charge through mains.
I think there have been a few threads with this issue and nexus4s even prior to 4.2.2 and supposedly it was hardware. I called support while talking it through she had heard a few similar cases and it seems to be a hardware/software design issue. My wonder is how can I enforce 'never deep sleep' because my kernel doesn't seem obey.
I woke up this morning with the indicator light on but phone dead requiring reset (charged though - if not overly so). Just now it died again while sitting on my desk at 80% charge and deep sleeping again.
---------- Post added at 06:24 PM ---------- Previous post was at 06:13 PM ----------
Guiding.God said:
Yeah, am on stock JB 4.2.2, unlocked and rooted though, no other change like new roms flashed or anything. I use the stock charger and charge through mains.
Click to expand...
Click to collapse
I've read in a few places today the stock charger has been causing a lot of the charging issues and plan to switch to my old g2's charger tonight
Just RMA'd my nexus for powering off for no reason - would do it a few times a week (and extremely buzzing earpiece - which I was living with), never had a problem putting it back on though or had issues by battery levels being eratic) did quite a bit of testing over the space of a few weeks and found it continued to do it after wiping/fomatting everything and on Stock 4.2.2 non rooted and locked BL. As far as I am concerned if its still doing it with the stock out of the box set up its a hardware fault.
Mine has powered off unexpectedly twice in 30 days. Should I get it rmad?
Sent from my Nexus 4 using xda premium
gamepr said:
Mine has powered off unexpectedly twice in 30 days. Should I get it rmad?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Dunno about that its up to you mine was doing it 2-3 times per week. I would wipe everything including userdata, reflash stock rom and monitor before going through the rigmorole of the RMA to make sure its deffo a hardware fault. Biggest problem with the RMA is the fact they put a hold on your credit/debit card for the price of the phone. So basically if you don't have the funds available you are shafted (I think you would have to send off to LG in that case).
I got the same problem ..just that my n4 back cracked while was charging :-\
maybe you should try to flash other kernel and rom if you cant solve this issus. if your N4 is unrooted then just bring it to LG store, you got warranty rite ?
Hi guys, I have bought a nexus 6P secondhand but I'm dealing with the problem of random shutdowns. After that it won't boot unless it is hooked to a charger. Some facts that I think might be of some influence or what I have tried:
- I bought it with Cyanogenmod 14.1, first day flashed back to stock 7.0 but kept my bootloader unlocked;
- Today I flashed an OTA update to 7.1.1;
- It happens random while using the phone, but I manage to reproduce the failure when using Google Camera and take pictures very rapidly (don't really know what the phone activity is at that moment)
- I've got a new battery on the way, might that be the issue?
- Battery status (percentage etc) doesn't make a difference. Might as well happen at 100%
- It doesn't happen while on the charger;
- It didn't happen in safe mode (didn't test this for too long though, but the fast camera action didn't kill the phone;
Does these descriptions make any bells rinkle? For me it looks like a defective battery but I'm happy to hear some expert about this
Thank you all for reading!
Yup, mine does the same thing. I believe it is supposed to be fixed with the new 7.1 release. Its the most inconvenient thing ever. I rarely takes pics now because nobody has a usb-c charger to get my phone turned back on. I'm running stock 7.0. It's not your battery.
Well that would kinda suck, I just updated to 7.1.1 and the problem is still there. Do you have a source for this thing?
I had the same random reboots.
I too suffered from random reboots in 7.1.1 dp2. They increased in frequency gradually. One night, it stuck in bootloop. Couldn't even boot into recovery. Browsed through threads here and reddit posts. All said the only solution was to RMA as without recovery nothing is possible. Huawei is replacing the motherboard as it's under warranty.
I just updated to 7.1.1 and I also can still confirm it's happen. I called huawei and they told me it was a software issue and it's not resolved and there is no fix other than to load 6.x on the phone. So basically, I we have a turd of a phone and nobody seems to want to fix it. Google told me it was a hardware issue and now Hauwei tells me it's a software issue. Maybe it's time for a new phone.
Just curious but have any of you flashed the official release images directly from Google through ADP with the FlashAll.bat command that it includes? Keeping your bootloader unlocked, but flashing everything to make sure your device is 100% stock and as fresh as it can be?
Messing with OTA's and other stuff like CM, I would definitely flash it this way and test it bone stock before venturing back into the Custom Rom land as major OS changes (from 6.0 to 7.0, etc) always seem to have residual glitches just like this.
IM0001 said:
Just curious but have any of you flashed the official release images directly from Google through ADP with the FlashAll.bat command that it includes? Keeping your bootloader unlocked, but flashing everything to make sure your device is 100% stock and as fresh as it can be?
Messing with OTA's and other stuff like CM, I would definitely flash it this way and test it bone stock before venturing back into the Custom Rom land as major OS changes (from 6.0 to 7.0, etc) always seem to have residual glitches just like this.
Click to expand...
Click to collapse
I loaded the image directly from google. I've never rooted or loaded a rom on this phone. I've only run factory images. I don't have the time to tinker like I used to.
Well that is downright strange then. There really doesn't seem to be any device that doesn't at least have a small share of mystery in some of it's problems is there? Lol.
Well that was how I reverted from CM to stock 7.0, by using the flash-all function (even though the flash all didn't work, had to flash the seperate files, but result was the same). The 7.1.1 upgrade was with a OTA flash using ADB sideload because I was rooted and TWRP recovery was active, so the OTA update didn't work for me. To be honest, I don't think my problem is a software issue. Is there any 'deeper' software than the complete rom? Is the kernel flashed seperately?
IM0001 said:
Well that is downright strange then. There really doesn't seem to be any device that doesn't at least have a small share of mystery in some of it's problems is there? Lol.
Click to expand...
Click to collapse
This fiasco has been happening for tons of people for weeks now, including me. Mine was just 2 weeks out of warranty, both google and huawei are pointing fingers at each other and nobody cares. I have tried all the methods possible, to flash different versions of pure factory image, nothing worked.
What charger did everyone use to get it backup a running?
Mine just shutdown this morning and using the USB A-to-C cable on a computer/car/wall outlet it didn't even recognize it was plugged. Google wants to RMA it (third one in 14 months of ownership) and I'm fighting over their 5 days delivery time for a new one.
also face this problem previously and Huawei replace battery. just 1 week before the warranty run out
Sent from my Nexus 6P using Tapatalk
rmoney said:
What charger did everyone use to get it backup a running?
Mine just shutdown this morning and using the USB A-to-C cable on a computer/car/wall outlet it didn't even recognize it was plugged. Google wants to RMA it (third one in 14 months of ownership) and I'm fighting over their 5 days delivery time for a new one.
Click to expand...
Click to collapse
Every charger worked for me. Now even carry a powerbank with me for when it lets me down outdoors I can get it powered on again. Plugging it in the PC also works just fine. Even a standard samsung charger (with micro-usb -> usb C adapter) works.
hah! Mine just started doing this!
I got the phone back from huawei for the 15% battery issue.. and it came back with this issue after going to 7.1.1
Strange! Mine doesn't seem to be related to any firmware state. It had this with CM14.1, stock 7.0 (factory image), and 7.1.1 (OTA flash). The only thing that is in common is that the bootloader is unlocked. Can this have any influence?
Hafidel36 said:
Strange! Mine doesn't seem to be related to any firmware state. It had this with CM14.1, stock 7.0 (factory image), and 7.1.1 (OTA flash). The only thing that is in common is that the bootloader is unlocked. Can this have any influence?
Click to expand...
Click to collapse
Mine is locked, on 7.0 I didn't have this issue.. on 7.1.1 It started.
on developer previews for it wasn't an issue either..
This is the absolute worst. Phones dying consistently at 15%. Sometimes it'll even shut down at like 30-40%. Absolutely ridiculous. I'm getting a new phone.
andrewnelson23 said:
This is the absolute worst. Phones dying consistently at 15%. Sometimes it'll even shut down at like 30-40%. Absolutely ridiculous. I'm getting a new phone.
Click to expand...
Click to collapse
That seems to be another know defect, you should look it up on here. Plenty of people are having that problem, but it is different from this thread.
I am having the same problem too! I was trying to raise this for two times on both XDA and reddit and no body seemed to care until you came up with this!
Mine randomly happens when taking photos with HDR+ and with the battery less than 50% (based on my observation). I replaced the battery by myself not long ago though.
Huawei says going back to 6.0.1 will fix the issue... and is blaming google, saying their pixel devices have this issue on 7.1.1 too.