Related
Most of us here love our Nexus S phones. We love Android 2.3's speed and the neat little TV effect when we lock our screens. Since Friday morning, (Feb. 11th) my Nexus S seems to be having another TV effect: nightly "sign offs."
It does not matter if I was charging the phone or not, the phone would just stop working. The strip of touch buttons along the bottom of the phone could be lit or unlit, but the screen would just turn off and no button presses would wake the phone. If I plugged it in to a computer, you could hear a "device connect" noise and see the Android hard drive appear under the Device Manager in Windows.
All of this means that the Nexus S was powered, but not responding. It would not reboot itself, and yes, I have experienced the reboot issue. This seems to be a separate issue. This only seems to happen after midnight.
The only solution is to pull out the battery and reboot it manually.
If my Nexus S is still on when this silent crash occurs overnight, my battery could be completely drained by the time I wake up, making me plug it in AND requiring a battery pull.
Has anyone else had this issue occur? According to the Android Market, I've only updated a few programs recently, one of them being Twitter.
Some Recently Updated Programs: (most recent first)
T-Mobile My Account (to 5.0.15)
Google Authenticator (installed, 0.54)
Google Goggles (to 1.3.1)
Twitter (to 2.0.0)
Amazon MP3 (to 1.8.30)
Google Books (to 1.1.4)
System Info:
Stock, unrooted Nexus S
Launch day unit
T-Mobile USA
Android 2.3.2
Baseband I9020XXJK8
Kernel 2.6.35.7-g7f1638a [email protected] #1
Build GRH78C
When I woke up on Friday, I called Samsung and they did note the issue under my phone number. I will call them again Monday and let them know I'm still having issues.
Any help/suggestions from the XDA community would be appreciated.
Thank you!
Just checked this morning, (Monday) and I had to pop out the battery to turn the phone back on. Before I went to sleep, my battery was at 100%. When I woke up and booted the phone up, it was around 30%. A 70% drop in 8 hours. Time to call Samsung again.
No one else is having this issue?
Sent from my Nexus S using XDA App
Sounds like either a defective unit, or messed up software.
Try doing a factory reset and use don't install many apps and see if that resolves for problems for a day or 2.
Well I had a strange issue that I had never seen before... at around midnight last night both my NS and my gf's went into bootloop at the same time, it was freaky. We're both on CM7 but hers is an older build and mine has netarchy's but it's never happened before... pulling the battery and powering back on fixed both phones but it's still very weird.
I have never actually called the manufacturer before about any issues with a device. Do they do anything for you? Or help you in any way?
Sent from my Nexus S using XDA App
Samsung suggested that I do a factory reset and then if that does not fix the issue, then I'll have to send the phone into them. The tech I got on Friday was more knowledgeable than the one I got today. I'm going to backup my data and then do a factory reset, making sure not to "pull" my data from Google's servers.
Man, not doing that is going to suck.
I am also using Google Voice for my voicemail. Just wanted to throw that out there in case any running services or something is causing all of this. I'm thinking that the new version of Twitter is causing this, as it's baked into Android now and there was an update recently. Thoughts?
Here's a small update on my issue: it seems to be software-related. My Nexus S crashes during the day as well, requiring a battery pull as described above. Disabling sync does not solve the issue, so it doesn't seem like it's coming from that area. What would you guys suggest my next place to look be?
Thanks!
Well, have been having almost the same issue for the past two days. Go to bed with 57 & 63%. Get up in the morning and the phone is dead. Not sure of the exact time it.passes away, but yeah.
Can't understand why the phone has to drink while I sleep.
Sent from my Nexus S using XDA App
Same prob, only intermitant though. Im using rc1 now, with no custom kernel.
Sent from my Nexus S using XDA App
I've been having the same issue since the 13th of Feb. At first it would freeze only overnight. Now, since the 14th it freezes while asleep 4-5 times a day, and the only way to get it working is to do a battery pull. I've tried to remove recently installed apps and widgets, but that has made no difference. I really don't want to have to do a factory reset, especially after I've been reading on google forums about other users not noticing a difference after a factory reset. This is getting ridiculous.
Unrooted Nexus S
Android 2.3.2
Baseband I9020XXJK8
Kernel 2.6.35.7-g7f1638a [email protected] #1
Build GRH78C
T-Mobile US
Agreed. Mine started to freeze during the day as well, requiring a battery pull. Do you have the new Twitter installed? Do you use Google Voice for voicemail? I'm trying to pull together some common threads. It's definitely software related.
Edit: OK, now this is just stupid. It seems like I'm freezing up every half an hour by now. I pull the phone from my pocket to check on something and I push the power button. The lockscreen shows, but the screen and touch buttons don't respond. Battery pull is the only option.
Yes, I do have the new Twitter installed, and yes, I do use Google Voice.
It seems to be happening more often now for me as well. Sometimes it takes two to three times for it to fully restart and get to the home screen, or the lock screen, and sometimes it will wake and then freeze on my pattern lock which also requires a battery pull.
I've starred a few forums on this same issue on the Google support forums, I hope others do the same to show support for a quick fix.
Last night I had the battery at 90. Switched of Wifi, Data and Sync.
Got up this morning and ... no probs The battery dropped to just 88!
BTW. I have got a stock unrooted phone with no Google Voice or twitter so, could not really be a problem related to that.
I use the app addin timer to run stuff at particular times. Other apps that I downloaded are calcbuddy, barcode scanner (which I think is pointless and going to remove), pure messenger, calwidget, appbrain (again, did not like the new updated one), aTakephone, Flip4Silence, CoPilot, Fast Reboot, Docs to Go, Skype, Remote Desktop, StockIndia, Tunein Radio and Widgetsoid.
Thanks for letting me know the apps you have installed. The only common ones between us are:
Barcode Scanner
Skype
Barcode scanner is actually useful. (QR Codes, etc.) Skype may have something to do with it as it does integrate itself with data sync. Thoughts?
In order for this theory to hold water, your phone must:
Crash and require a battery pull to be responsive
Have Skype installed
Edit: My phone was crashing so much that the "first time/welcome" wizard was coming up. Swype, Facebook and GMail were crashing left and right. Time for another Factory Reset....
Edit 2: The phone has SOMEHOW survived a Factory Reset from the normal phone menu AND the Recovery menu! WHAT?!
My Nexus S is going back to Samsung for repair. *sigh* I wonder what they'll say caused the issues?
Sent from my Nexus One using XDA App
Now, today, the phone doesn't get passed the initial "Google" screen. No matter how many times I pull the battery, plug it into a charger or usb port, it does not go past the first google screen. Very disappointing.
Can you get into the bootloader menu? (Volume Up + Power)
Yes, that allowed me to get to the bootloader menu, but I couldn't do a factory reset, it just sat at the screen with the android and an exclamation point inside a triangle. I then did a battery pull, tried a normal restart and got to my home screen.
Glad to hear that you got in. By the way, once you get to the exclamation point screen, you can push Power while holding the Volume Up button to bring up a menu.
Cool, thanks for the help!!
Hi all,
I got my Nexus 7 from the Play Store a couple of months ago (one of the pre-orderers). The first time I turned it on, I noticed the screen slowly dimming and turning off during the boot animation. I would see the 'X' but it would slowly fade out, disappear totally and then reappear on full brightness. The screen then totally turned off after completing booting and I couldn't see anything. A couple of reboots later and the screen finally turned on which was great. The tablet would run anything perfectly after that except if I turned the brightness to the lowest setting which would cause the screen to turn off. This didn't bother me either since I always use it on full brightness anyway.
However, over the last couple of weeks I noticed the touchscreen becomes unresponsive after prolonged use. This made me decide to get it replaced. I called Google who said they would send me a replacement :victory:.
Here's the problem...Since I was rooted and running CWM recovery I decided to revert to the factory image for warranty purposes. So I reverted to stock and rebooted but I now have the same problem I had at the first boot. My screen won't turn on! I tried rebooting a couple of times to see if that would do it but it just happens everytime.The bootanimation completes and the screen just turns off. The problem is I can't relock my bootloader which is going to jeopardise my warranty IMO since my tablet is scheduled for return on the 12th of this month (10/12/2012).
Well finally could anyone please help? Has anyone had the same issue? What steps did you take?
Sorry for the long post. I'm just worried that I'm going to be stuck with the defective tablet which I worked hard to save the money for in the first place
BUMP. I really need any help I can get since i've got less than 48 hours to get it fully stock before the courier comes to pick it up for RMA.
Did you follow this guide to return to stock/relock the bootloader? I had this exact same problem and your best bet would be to get an RMA.
Actually I did perform all those steps but I just can't seem to enter the stock recovery. I just keep getting the Android with the red triangle. Thanks for the suggestion anyways. I'll give you a thanks just for that
Sent from my Galaxy Nexus using xda app-developers app
Sounds to me as if your auto brightness is stuck....wake it up and shine a flashlight or something on the screen. If you can see your screen, go into settings and turn off your auto brightness.
Well I did what you said and guess what IT WORKED! Thanks a million. I'm really dumb for not having thought of that..
Sent from my Nexus 7 using XDA Premium HD app
Hey XDA,
I received my 16GB Nexus 7 from Google 4 days ago. I immediately updated to 4.2.1, rooted, and then flashed franco.Kernel. I was running the latest update to franco's kernel, and had left the settings untouched from the defaults with interactive governor. Yesterday I flashed the latest nightly for Cyanogenmod.
I was using the Facebook app when my tablet ran out of battery (I intentionally let it die), and after it powered itself off, I plugged it in with the charger provided to me by Asus/Google. Because I am new to this tablet, I wasn't aware that plugging the charger in meant that the device would power on. Anyways, it did power on, and I had no plans to turn it off now that it had turned itself off. I went to turn the wi-fi off so that it would charge with less power drain, but just before I turned the wi-fi off, the device began to power down again (The charger is still plugged in, and it didn't become unhooked at any time). I begin to walk away to do other things while it turns off again, but I stop when I hear a weird grinding noise. It's hard to explain, other than it sounded like a kettle getting progressively louder and then shutting itself off when it reaches its desired temperature, only it sounded like gears and not a kettle.
A little worried, I wait a bit and then I turn it on. I'm relieved when I see the Google logo appear, and then the Cyanogenmod logo appear. After a long boot, I'm greeted by a black screen with what tiny white flashing dots randomly appearing. I turn the device off, and restart it. Same thing, only now it seems like there may be more flashing white dots than the last boot. I unplugged the device from the wall, and force shut it off (power + volume keys).
I've never heard of this happening before, which is why I'm hoping someone can give me some advice. Obvious things for me to do would be to flash stock 4.2.1 onto my Nexus 7. The reason I haven't done this is that I'm worried that my device may now be dangerous (battery melt, processor malfunction). Does XDA have any recommendations before I phone Google? I'd like to avoid Google because I've voided my warranty with them by rooting and flashing a custom kernel, so any other help is MUCH appreciated.
Thank you so much for reading my essay, and for taking the time to help,
Robert
Do your very best to revert it back to stock os and kernel and re lock the bootloader. Yes it is possible. Look for the nexus 7 toolkit. Then send it to google/asus. Best I can think of dude.
Sent from my MB612 using xda app-developers app
I have heard people with similar issues start device in bootloader and leave it there to charge to prevent the on/off loop and after a few hours when charged boot normally.
Hope this helps
Sent from my SGH-I927 using xda app-developers app
The screen with white dots has turned into what appears to be a screen with no signal like you see on tv's.
This is even happening while I'm in recovery mode, it'll just randomly happen.
What's going on?
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
BlackFire27 said:
Can you get it into fastboot? Does it still respond to adb?
Sent from my MB612 using xda app-developers app
---------- Post added at 05:05 AM ---------- Previous post was at 05:02 AM ----------
Here you go dude. It'll help. http://forum.xda-developers.com/showthread.php?t=1809195
Click to expand...
Click to collapse
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Trewyy said:
Thanks, that's actually what I'm using =) The issue I'm having is getting it into recovery mode. I am always able to do it prior to this incident, at least after two tries anyways. Now every time the Google logo displays and I hit the down volume, it just begins to boot into Android ignoring the fact I hit the volume down.
Robert
Click to expand...
Click to collapse
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
BlackFire27 said:
Make sure the device is off. Hold the volume up, down, and power for 2 or 3 seconds. Then let go of the power button while holding the volumes. That'll bring you to the bootloader. From there you can also get into recovery mode. By selecting with the power and volume keys.
Click to expand...
Click to collapse
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Trewyy said:
I'm going to leave it charging for a while and see if that will give me enough time to do what I need. I'll report back here either within an hour, or sometime tomorrow around this time.
Thanks for the help so far!
Robert
Click to expand...
Click to collapse
Anytime man! PM me if you have anything else man.
It's 4 days old. Send it back as defective.
turn it off, let it charge for long time, after tha download toolkit and revert it back to stock.
You should be good to go.
I'd bring it back, as it is possible to cause an injury to you. Better to be safe than sorry.
Its new so just bring it back (or send) and get a new one.
Sent from my Nexus 7 using xda premium
Try to relock it and flash the stock rom.
After that, phone up Google and explain what happened AND ask for a compensation. This could have harmed you, and Google/ASUS IS responsible for it. Unless, of course you have messed something up while rooting or flashing the custom rom.
Anyway, you should be able to get a compensation, maybe a 32GB version.
This is not something that should happen to a 4 days old device.
did you void the warranty by flashing? i don't actually know.
granted, this sounds like a hardware malfunction (again, i don't know, could be a kernel), but, modder beware. this is a risk we take.
I'd put it back in the box and return it if possible. Save some time. If they are jerks about it then proceed:
If you can flash anything to it through recovery, download the updated Galaxy Nexus (Samsung) JB Bootloader and flash it.
I have a Galaxy Nexus and a Nexus 7. I killed my first N7 by getting confused and flashing it to my N7. It won't even power on afterwards. That should screw up your partitions enough where it won't be recoverable without a full format/reflash.
I had this issue when my battery died. I took off the back cover and unplugged the battery and plugged it back in. Put it back together and charged it up for a few hours. All has been well since, I'm pretty sure its a common issue with N7's when the battery gets low.
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Do your best to revert it back to factory and call them up about that possible firecracker before something else can happen
keep us informed about what happens too if thats ok
Stock - and the same problem...
Hi, my N7 is two months old and worked perfectly. It's clear stock - never rooted, modded etc. Today I suddenly can't run it - it boots, battery level is 24% (on bootscreen), and after few seconds shows 1% and starts to snow - sometimes with sound. I haven't installed anything new for few weeks, so I'm sure it's not a virus, trojan etc. WTF?
PS. Sorry for my English...
djexacto said:
Had a similar issue once after letting it discharge to 0 and plugging it in and trying to boot right away. Mind you I didn't have the noise, just the snow effect. My solution was to turn it off and let it charge for a few minutes while off. After that it worked fine.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I confirm that. I had this issue already a lot of times. When the battery is completley discharged it seems that the display or the graphics hardware is not able to start as expected. I just left it powered of (or in that charging screen) for some time (>1h) without using it. Then it started normal.
But also for me, no noise, just the screen like on an old TV without signal.
Unplugged my phone this morning at 100%, went to charge it just now with factory charger and cable and nothing. Tried reboot and battery pull. Sitting at 60% right now. It's off in case I need to return to stock to exchange it. Any ideas?
Planktron said:
Unplugged my phone this morning at 100%, went to charge it just now with factory charger and cable and nothing. Tried reboot and battery pull. Sitting at 60% right now. It's off in case I need to return to stock to exchange it. Any ideas?
Click to expand...
Click to collapse
I had a bad cable, it is not the phone...damn cables were cheaply made.
Tried 2 cables. When the phone is off I get the battery icon with the circle in it, but it just loops this icon. It comes up, vibrates, turns off repeatedly. I tried to wipe cache and it said error. I'm rooted, defrosted everything I had frozen.
What I don't understand is why I'm getting an error when trying to wipe cache partition.I unrooted, so as far as I know im now totally stock. Is it safe to try to do a factory reset?
Planktron said:
Tried 2 cables. When the phone is off I get the battery icon with the circle in it, but it just loops this icon. It comes up, vibrates, turns off repeatedly. I tried to wipe cache and it said error. I'm rooted, defrosted everything I had frozen.
Click to expand...
Click to collapse
Sounds like kernel panic. Whatever rooting/custom mod/ blabla you have on that device is either buggy, badly flashed or something like that.
You need to have a good connection to Odin established, flash only stock rom (the untouched version/odexed), let it reboot normally from Odin, and wait. (it is important to have at least 50% battery left, you don't want it to quite on you in the middle of a flash)
Doesn't matter if it doesn't go all the way and setup the first time. Just pull the batter (after Odin rebooted), go into recovery, cleanup everything, and reboot.
Thank should get you back in the world of the living ...
http://forum.xda-developers.com/showthread.php?t=2261573&highlight=return+to+stock
So just do exactly what is written in this thread then? Do I have to go that far or can I try a factory reset from recovery?
Thanks BTW
Planktron said:
http://forum.xda-developers.com/showthread.php?t=2261573&highlight=return+to+stock
So just do exactly what is written in this thread then? Do I have to go that far or can I try a factory reset from recovery?
Thanks BTW
Click to expand...
Click to collapse
Easier things first, so if you haven't tried a factory reset yet then go ahead ( although that won't unroot you) try your factory reset first.
But then if your battery gets too low and still doesn't charged, you need to get it charged up first.
And yes that hotfile link is the original factory ROM dump, it is good.
That is the at&t stock file or you're on bell or rogers or ... get a samfirmware/sammobile account and download your ROM from there.
No dice on the factory reset, and I'm about 40%. I'm thinking I'm just going to exchange it. Device status says Official so I should be good, no?
Planktron said:
No dice on the factory reset, and I'm about 40%. I'm thinking I'm just going to exchange it. Device status says Official so I should be good, no?
Click to expand...
Click to collapse
you should be ok exchanging it although for most devices rooting voids the warranty
that was my main reason sending you the odin flashing route in case you wanted to exchange it but it is no big deal.
Well I'll be...
Did another factory reset from the settings menu this time, ON THE WAY to the AT&T store(while parked, of course), plugged it into the 'ol 12v and she fired right up. I agree about the kernel panic deal. I've had strange things happen before. The only thing that changed on my phone from last night until the no-charge state was the installation of SugarSync. It kept FC'ing so I uninstalled it. I think it may have changed some items deep deep in the areas of the OS that I know nothing about and it freaked out the bowels of Android.
Back when I had my Atrix 4G, I installed Dolphin Browser, and it sent my phone into a whirlwind of FC's.
Thank you for your assistance, Commodore.
Planktron said:
Well I'll be...
Did another factory reset from the settings menu this time, ON THE WAY to the AT&T store(while parked, of course), plugged it into the 'ol 12v and she fired right up. I agree about the kernel panic deal. I've had strange things happen before. The only thing that changed on my phone from last night until the no-charge state was the installation of SugarSync. It kept FC'ing so I uninstalled it. I think it may have changed some items deep deep in the areas of the OS that I know nothing about and it freaked out the bowels of Android.
Back when I had my Atrix 4G, I installed Dolphin Browser, and it sent my phone into a whirlwind of FC's.
Thank you for your assistance, Commodore.
Click to expand...
Click to collapse
That is always good to hear. thanks for reporting back.
Plus if you did reset it while you were driving, not that some people haven't ... , at&t will start making new screen stickers saying :
"don't factory reset your phones and drive ... it can wait".
Oh well. Since im a junkie and couldn't wait to re root, as soon as it charged back up I re rooted. All was well until I started freezing bloat, then it stopped charging. Got a replacement on the last day of the return period. Wish I knew what was causing this. Looks like im staying stock until we get recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
It's been a few days so I'm bringing this thread back from the grave, but I want to know if anyone else has experienced similar issues. It's really strange, what happened, and I'd like to know more about why it happened. I should have made a logcat but too late now. I'm not the type of person to experience something like that and take the easy way out with an exchange (I've experienced worse), but with my battery percent remaining an ODIN flash would have been risky at best. Like I said, everything was fine for days until I installed sugarsync.
I only froze bloat. Everything starting with AT&T, and some Samsung apps like S-Voice, ChatOn and push service.
Until I can figure this out or get custom recovery, I'm stuck stock because I'm not going to cheat again for another exchange.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2
I had exactly the same thing happen to my rooted s4. Took it back to the shop i bought it ( Unrooted ) and they replaced it.
Same here.
I get it to charge sometimes for about 10 minutes and then it'll disconnect.
USB via the PC doesn't work as well.
I think replacement is probably a safest bet.
We aren't the only ones either...
http://forums.androidcentral.com/samsung-galaxy-s4/275276-galaxy-s4-wont-charge.html
This has just happened to me. I plugged it in last night with about 19% remaining, woke up this morning and it was at 7%-- hadn't charged. I tried a couple different chargers and cables, and nothing has worked so far. The charge has since dwindled to 4%. I'm running slimrom, and I guess I can't risk flashing back to stock since the battery is likely to die completely during the process.
When I did a shutdown and then plugged it in, I got the "charging" icon, of the battery with the green bar repeatedly moving up through it. But after leaving it for half and hour, I tried to boot it, and that was the point where it had gone from 7% to 4%, so apparently it wasn't really charging. Might have to buy another battery and see if that's the problem or the charging circuit in the phone.
---------- Post added at 03:01 PM ---------- Previous post was at 02:48 PM ----------
Ok, so this is weird. I have been using some older chargers/cables that I had left over from my Captivate, and they've been working fine for a month, until now. But I went and got out the charger that came with the GS4 and tried that, and although the ROM still says "not charging/connect your charger", the battery % is increasing. Very strange.
I think u need to get back to stock rom to solve this issue..and u won't get warranty as your device is rooted even if u revert back to stock your bincounter will ramain same that's of you had flashed your device twice with custom rom your bin counter will be 2...so samsung can easily understand it by going into download mode...u can also see the number of bin counts by entering into download mode screen ....so u need to reset bin counter before taking it to customer care otherwise they will woid ur warranty:thumbup:
Sent from my GT-I9500 using xda premium
Hi,
My Nexus 4 has been acting up for some time. I had the infamous "optimizing apps" issue almost one year ago. Since then I used an app ("optimizer app fix" or something) to get around it. It's rooted, but I can't remember the details/versions.
More recently, the phone started to lose the network connection. I tried to change the setting from automatic to my home network, it did seem to help a bit, but didn't really fix the issue.
Yesterday I was using the flashlight, and just before I turned it off, the phone rebooted itself. From then on it became very unstable. If I leave it alone in flight mode, it will stay on. If I start doing anything, at some point it will shut down. If I keep it plugged to the charger, it stays on, though. So it looked like the battery is gone. I'm just not 100% sure because if I boot it into recovery mode it stays there apparently with no issues, for a long time. It could be that the current draw is not so big in that mode, though.
I have just finished backing up whatever I could, and wiped the data/dalvik/cache partitions from the TWRP recovery menu. Still not good. Did a Format Data from there too. No luck.
Given the cost and hassle and wait and the number of fake batteries in the market, I don't want to buy a new battery to revive this phone (knowing that it's likely to fail again sooner than I can expect). Is there anything else you'd suggest that I try before I go shop for a new phone? :crying:
Thanks,
VMat
vmat005 said:
Hi,
My Nexus 4 has been acting up for some time. I had the infamous "optimizing apps" issue almost one year ago. Since then I used an app ("optimizer app fix" or something) to get around it. It's rooted, but I can't remember the details/versions.
More recently, the phone started to lose the network connection. I tried to change the setting from automatic to my home network, it did seem to help a bit, but didn't really fix the issue.
Yesterday I was using the flashlight, and just before I turned it off, the phone rebooted itself. From then on it became very unstable. If I leave it alone in flight mode, it will stay on. If I start doing anything, at some point it will shut down. If I keep it plugged to the charger, it stays on, though. So it looked like the battery is gone. I'm just not 100% sure because if I boot it into recovery mode it stays there apparently with no issues, for a long time. It could be that the current draw is not so big in that mode, though.
I have just finished backing up whatever I could, and wiped the data/dalvik/cache partitions from the TWRP recovery menu. Still not good. Did a Format Data from there too. No luck.
Given the cost and hassle and wait and the number of fake batteries in the market, I don't want to buy a new battery to revive this phone (knowing that it's likely to fail again sooner than I can expect). Is there anything else you'd suggest that I try before I go shop for a new phone? :crying:
Thanks,
VMat
Click to expand...
Click to collapse
No. You need to replace the battery.
Sent from my Nexus 6 using Tapatalk
trent999 said:
No. You need to replace the battery.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That's what I thought. What a bummer.
Thanks for the reply. Happy new year, everyone!
VMat