Related
I just got my tab 10.1 16gb.
Noticed it had twice went to sleep and didn't wake up (it also failed to charge during that "deadzone" time).
It turns on while holding the power button for 10+ secs.
I read somewhere that factory reset works ... Since its new and hadn't done anyhting on it, I gave it a try. Will report back.
However I wanted to know if you guys faced that issue to? I wish to root/rom it and i wanna make sure I use my warranty if neede.d
This is similar to transformer's sleep of death and I saw a similar thread in iconia a500 forums. I think this is related to honeycomb or tegra. At least that's what these devices have in common. I am planing of getting a tab next week and thought that it is unaffected by this issue. Now I am worried...
sent from my CM7 nokia 3210
So I've made a factory reset. Had it on charge for 8 hours (same as before).
Came back - device woke up.
Gonna keep it off charge till next morning and check again. looks promising.
Ok. Crap.
Had it off charge for the night, after not doing anything special (browsing and stuff). Closed the screen, set it a side.
At morning I tried opening it. It took one click (not even a long one) to show Galaxy Tab logo, and then Samsung logo .. we all know what that means - Device was shut down and just made a cold boot.
So I guess factory reset didn't set things straight.
IN FACT, I noticed battery dropped to 39% from 98% last night! And no special services were running.
Only thing I can think of is something in the device makes it go into application loop. Could be OS, could be some hardware malfunction (like in WIFI antenna).
Will make more tests during the weekend but next week this is definitely going back to store.
advocator said:
Ok. Crap.
Had it off charge for the night, after not doing anything special (browsing and stuff). Closed the screen, set it a side.
At morning I tried opening it. It took one click (not even a long one) to show Galaxy Tab logo, and then Samsung logo .. we all know what that means - Device was shut down and just made a cold boot.
So I guess factory reset didn't set things straight.
IN FACT, I noticed battery dropped to 39% from 98% last night! And no special services were running.
Only thing I can think of is something in the device makes it go into application loop. Could be OS, could be some hardware malfunction (like in WIFI antenna).
Will make more tests during the weekend but next week this is definitely going back to store.
Click to expand...
Click to collapse
i have nearly the same problems. heavy battery drainage over night, devices powers itself off....
if i charge my device, and it's fully charged, then it shuts down too. don't know why...
hebbe said:
i have nearly the same problems. heavy battery drainage over night, devices powers itself off....
if i charge my device, and it's fully charged, then it shuts down too. don't know why...
Click to expand...
Click to collapse
have you tried hard reset?
are you on stock unrooted?
So, I went back to Samsung and told these guys - "I got this on Thursday, same day it got problems. What'cha gonna do about it?"
Well, they started telling me that procedures force them to examine the device for 24 hours etc etc. I didn't accept it as I dont buy malfunctioning hardware just for it to lay around for 24 hours in a lab.
I got my money back, and bought a new Tab 10.1 from a different reseller. Surprise surprise, its awesome.
Recently I notice my I717 is shutting down randomly, and experiencing battery issues. For example I can be running any app or browsing the web or whatever and the phone fully shut down without notice. In the past I recalled the phone least prompting me with a message a saying phone powering off. It also take 2-3 tries of holding power button phone vibrate before come back on. when I finally get phone to power on it say 15% battery life. This where it get strange, reboot phone again, and it now say 87% charge. WTF is what I'm thinking, it jump 72% battery life after reboot. Also its not my ROM cause I try 3 different 4.2.2 custom roms, and went back to an 4.0.4 custom rom. Still same problem, any insight would be helpful thanks in advance.
I think I may have gave her Whiplash the way I pulled my Big Black.........GALAXY NOTE out!
Signature is uncalled for ........but maybe try wiping your phone completely ...internal and android secure ....and do a CLEAN install
RooT -[]D[][]V[][]D- BeeR
Battery dead.
Remove your battery and check if it´s deformed, like thicker than the original battery.
Replace it and your good. You don't need to waste your time on clean install etc.
I have had same problem in two differet phones. In both occasions the reason was dead battery.
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
FriendlyNeighborhoodEnt said:
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
Click to expand...
Click to collapse
I would tend to agree odin the full wipe stock image back and start over
FriendlyNeighborhoodEnt said:
There's no need for n extensive backstory because rooting, flashing, etc I am pretty familiar with, having first rooted the old HTC Thunderbolt.
Now here's what happened:
I have quite a few roms for the S4 but the BoneStock 1.1.4 rom by Andybones always kept bringing me back. I pretty much settled for that one as my dail driver and kept it so for at least 2 months.
Recently in the past week i started getting notifications on my internal sys memory almost out. So i check and realize that my Google Play Music is almost at 6 gb, so I decide to wipe my entire phone just to give it a fresh new flash. Flash goes well, fresh install. I hardly have the time to let my phone die, so I usually just charge it regardless (I have a 5200 mAh extended battery) but this time I decided to let it die. Once it did, i put it to charge immediately and thats when i noticed something was wrong. It was stuck at the battery logo, the animated one that charges while your phone isn't on yet? Well the circle that spins and sort of 'detects' how much battery is left is stuck there. Even if i disconnect my charger it stays there.
So i did what's natural and battery pulled. Did that, reconnected my phone, still the same thing. Now i tried multiple times to get it to turn on and what not but it won't. It gets stuck at the samsung boot logo, no idea why.
So i've decided to call it a night (3 am here, work in the afternoon) and hopefully this thread gets seen by someone who knows how to deal wth this.
TL;DR Clean re-flash of the same daily driver (BoneStock 1.1.4) and let my phone die because I realize I never let it die. Once it does, it get stuck at both the Samsung boot logo, or the animated battery charge circle. I tried accessing recovery, and while I see the little blue message top left hand corner, it just seems to shut itself off, and boot back up only to be stuck again. I have no idea what happeend, I never mess with system functions or any thing of that sort.
The only real solution I see if restoring to stock firmware through Odin? Hopefully that will work, but anyone else experience this before? or something similar and can shed some light on this weird situation?
Thanks in advance!
EDIT: I apologize for the bad grammar, I've been trying to figure this out for the past 2 hours, and it's very late right now.
Click to expand...
Click to collapse
When you see the blue text for recovery do you continue to hold the buttons down until you see the recovery screen? If you take your fingers off it will do what your describing. If you can get into recovery reflash your ROM.
Sent from my Nexus 7 using XDA Premium 4 mobile app
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
Hello!
Had my N9 for almost 4 years now! About a year in, I started experiencing the white-static-screen-high-pitched-screech issue that many of you have described, but disconnecting and reconnecting the battery connector solved the issue. As of late, I have been running stock Android N.
Recently, I have been starting to experience the issue again, as well as trouble booting up. The problem has gotten much worse over the past two weeks or so, to the point where I cannot fully start up -- the Google logo shows, the start-up animation starts playing, but usually doesn't make it very far before the animation freezes and the screen goes black. I can access the boot menu and Recovery mode though. Going into Recovery mode and explicitly "powering down," letting it sit for a bit, and then starting up sometimes makes it all the way to the OS, but it shuts down by itself shortly after. I cleaned and reconnected the battery connector, but that did not help. I just tried a factory reset, but that doesn't seem to have fixed the issue -- my device is wiped, but if I can get into the OS, it just shuts down as before. If I don't explicitly "power down" and let it sit, the battery does run down, which makes me think that rather than crashing when it freezes, it's still running, or trying to.
Any suggestions? Thanks!
weirdo16 said:
Hello!
Had my N9 for almost 4 years now! About a year in, I started experiencing the white-static-screen-high-pitched-screech issue that many of you have described, but disconnecting and reconnecting the battery connector solved the issue. As of late, I have been running stock Android N.
Recently, I have been starting to experience the issue again, as well as trouble booting up. The problem has gotten much worse over the past two weeks or so, to the point where I cannot fully start up -- the Google logo shows, the start-up animation starts playing, but usually doesn't make it very far before the animation freezes and the screen goes black. I can access the boot menu and Recovery mode though. Going into Recovery mode and explicitly "powering down," letting it sit for a bit, and then starting up sometimes makes it all the way to the OS, but it shuts down by itself shortly after. I cleaned and reconnected the battery connector, but that did not help. I just tried a factory reset, but that doesn't seem to have fixed the issue -- my device is wiped, but if I can get into the OS, it just shuts down as before. If I don't explicitly "power down" and let it sit, the battery does run down, which makes me think that rather than crashing when it freezes, it's still running, or trying to.
Any suggestions? Thanks!
Click to expand...
Click to collapse
Have you tried replacing the battery with a new one?
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Have you tried replacing the battery with a new one?
Click to expand...
Click to collapse
Thanks! I've considered it, but the battery seems like it's OK -- it holds a charge when powered off, and the voltage still seems pretty high (~4.1v) Are there any other ways to tell if the battery might be bad, how do you tell? Has anyone determined if the white-screen-screeching issue is caused by the battery itself, or the battery connector?
weirdo16 said:
Thanks! I've considered it, but the battery seems like it's OK -- it holds a charge when powered off, and the voltage still seems pretty high (~4.1v) Are there any other ways to tell if the battery might be bad, how do you tell? Has anyone determined if the white-screen-screeching issue is caused by the battery itself, or the battery connector?
Click to expand...
Click to collapse
I have the same issue on my n9 but put it out to pasture so I never tried to replace it. I have seen others on here who have and it seemed to work. But, it also seemed that they couldn't find a real good replacement and the replacement battery didn't last that long.
Sent from my [device_name] using XDA-Developers Legacy app
I'm having the exact same problem. No matter what I flash it always get stuck at the bootanimation. Sometimes it doesn't even get past the initial Google logo bootscreen. I can never fully boot to the OS, though.
redsmith said:
I'm having the exact same problem. No matter what I flash it always get stuck at the bootanimation. Sometimes it doesn't even get past the initial Google logo bootscreen. I can never fully boot to the OS, though.
Click to expand...
Click to collapse
Have you tried updating to the lastest factory images from Google? They include additional pieces of firmware than just the OS and many ROMs are built with certain factory builds in mind. The firmware and ROM need to match. The kernel also needs to match. And if you're going to a completely different ROM, you need to factory reset. Or at least, it's a good idea to. Not all ROMs will boot without a factory reset.
gk1984 said:
Have you tried updating to the lastest factory images from Google? They include additional pieces of firmware than just the OS and many ROMs are built with certain factory builds in mind. The firmware and ROM need to match. The kernel also needs to match. And if you're going to a completely different ROM, you need to factory reset. Or at least, it's a good idea to. Not all ROMs will boot without a factory reset.
Click to expand...
Click to collapse
Yes, I flashed the latest factory image. I even flashed the first one (5.0). No matter what I try, it always get stuck at the bootanimation. Same thing with custom ROMs. I suspect something's wrong with the data partition, but not even wiping and formatting does the trick.