HELP,
yesterday, I was using my nexus 7 for normal use, wasn't playing game, just browsing with chrome. the battery was 8 percent when I last saw it. I then proceed to charge it, but the thing suddenly just shut down itself. I thought I misread the battery percentage, so I charge it anyway. about an hour later, i checked on my nexus 7, turn it on, got to the boot screen, got to the home screen, use it for about 15 minutes, and suddenly, the screen black out, it was flickering like crazy, and making some white noise ish sound. I panicked so I hold down the power button and turn it off. I turn it on again, and after about 30 seconds, the same thing happened again. I was using motley's kernel with 520 GPU, and I thought, maybe my nexus 7 cant handle the GPU OC. So I went to recovery, tried playing with recovery for about a minute or so, but the screen didn't flicker at all on the recovery. So I flashed the 484 GPU version of motley's kernel. When I reboot to system, the same thing happened again. So I thought, maybe if I restore to my old backup, it would not be like this any more. so I wipe the data, dalvik, and cache, and I restore my old backup. But the same thing happened again, only this time, after I turn it off, it make a high pitched sound.
I waited for about 6 hours, and now when I turn my nexus 7 on again, it works normally.
So, what has happened to my nexus 7?
bump
I'd say it is the overclock. Graphic cards do some weird stuff when overclocked. You can burn up your GPU doing that and cause it to forever freak out. I always shied away from GPU overclocks.
Sent from my Nexus 7 using xda premium
would that cause any permanent damage?
keni.mardira said:
would that cause any permanent damage?
Click to expand...
Click to collapse
It should be ok if you reflash back to stock rom to make all the hardware back to reset mode. A warning always given when we try to flash rom with oc created.
i also experienced this one, also received a battery warning and then suddenly screen went blank. then same weird thing happened as the one above. I'm on paranoid android rom and i'm quite sure it's not overclocked or something. Was only able to get back to normal by holding the power button for around 15-20 seconds...
Happens to me
This will happen to me a lot when my nexus 7s battery dies, I plug the tablet in and then immediately try to start it up. It will work for around 30 seconds then look like an old TV without a signal. I am on stock everything, no rooting or custom Roms (yet). I always thought it had something to do with battery calibration being off and the tablet not having enough power to run, because it always works fine when I charge it before attempting to boot.
I have also noticed that every once in a while the screen will have a vertical line of pixels flicker.
Same thing happened to me yesterday...
I got the "low battery" warning and after some time the screen started flickering in many colors and there was a weird static noise.
I pushed the on/off button, but it wouldn't turn on again. After a few minutes of charging, I could turn it on again.
This isn't normal behaviour, is it? Shouldn't the N7 perform a regular shut-down when the battery has no juice left?
I'm on the rooted stock rom btw.
androidswagz said:
This will happen to me a lot when my nexus 7s battery dies, I plug the tablet in and then immediately try to start it up. It will work for around 30 seconds then look like an old TV without a signal. I am on stock everything, no rooting or custom Roms (yet). I always thought it had something to do with battery calibration being off and the tablet not having enough power to run, because it always works fine when I charge it before attempting to boot.
I have also noticed that every once in a while the screen will have a vertical line of pixels flicker.
Click to expand...
Click to collapse
+1 bro. I am having the same problem. what do we need to do ? it is same with all nexus 7's . should we claim the warranty or just neglect it ? wat say ?
Aditya88 said:
+1 bro. I am having the same problem. what do we need to do ? it is same with all nexus 7's . should we claim the warranty or just neglect it ? wat say ?
Click to expand...
Click to collapse
I faced the same problem. I dont know when the battery might have drained out, but on starting the tab on low battery, it suddenly started showing black screen with little grains and suddenly stopped with a noise. I charged, started the tab again while charging, and the battery reading stuck at 21% even after charging for 20 mins. Within 5 mins, it happened again. Now after 35 mins of charging, I start it again, it boots normal, and now its reading the battery percentage in an incremental value (started with 22%) and now its again stuck at 23%
Is this a HW related issue? Or do you think it is more of SW related issue? If it is more towards the HW side, we better have it replaced. Mine is C70 model.
bump
just happened to me... it may have run out of juice... didn't turn on when I tried, so I guess it did... then I put it on the charger, tried booting it, went away for a sec and when I came back I also got this black screen with some flicker and a static noise...
will now try to charge it over night before trying again...
Nexus 7/Google problems
I received my Nexus 7 on Aug 21 after hearing the rave reviews. It didn't come with app for a camera, so I downloaded one.
The camera didn't work. I re-booted it & it worked this time. Downloaded Skype - whole reason for getting the tablet - to stay in touch with family that is far away. Tried to Skype - camera wouldn't work. Rebooted - worked this time again (getting tired of having to reboot for something I want to use to work). On Sept 2, sent message to Google inquiring about camera & app I downloaded. Only response - "thank you for contacting...blah, blah, blah - check out Q&A." All along, the tablet would shut itself down & reboot randomly (battery fully charged sometimes). On Sept 13, I shut it down & charged it. After a full charge, I tried to power it back on. Tried again several times that night & then the next morning. Called Google (who I bought it from). Told them I didn't want a piece of junk that wouldn't work. He told me it was past my remorse period. (The only remorse I have is buying their piece of crap instead of a reputable one.) I finally did get it to come back on, but camera hasn’t work since even after a complete factory reset. Any way – in order to get this one fixed, I have to “buy” a new one, then send back the old one & be reimbursed. Is this a legitimate business practice?
hi,
since today i have the same issue. did nothing special, just swichting from g currents to chrome. stock rom, no modifications, not rooted, everything original
n7 suddenly had a black screen(battery was at 28%). nothing worked, no powerswitch(10-30 secs). when connected to original power supply and cable, it boots up.. google logo .. glowing X.. lockscreen. then, approx. 30 sec later it turns off again(screen black). usb cable still connected. after some time it comes up again.. and repeats the procedure. after some cycles it stops, and when i reconnect the usb calbe it starts over again. sometimes, before it turns black, it shows a flickering screen and sometimes fizzling sound.
any suggestions?
I had this same issue right after the 4.2 ota update, after leaving it on charge overnight it seems fine now after a couple of discharge / charge cycles
Its like after the update it was over estimating the battery level
Sent from my Nexus 7 using xda premium
Same thing!
I have a completely stock Nexus 7, and the EXACT same problems are happening to me too! The first couple of times it happened my tablet would reboot normaly. But now, my tablet won't boot up at all. Any suggestions on what I should do? Also, remember, I have no mods installed.
Happening to me too.My N7 shut itself down because of low battery a couple hours ago and I haven't been able to get it to boot since. When I plug it into the charger it shows a flickering screen like a tv with no signal but with less white flickers. I've tried multiple chargers and cables but I could only get it to boot up a couple times and both times it did not show that it was charging even though it was plugged in and the battery was at 0% so as soon as it boots up it shuts itself down again because of low battery.
So now I've got it on the charger, screen all a'flicker, waiting for it to get a charge but I've got a feeling its not even charging because, like I said, the few times it has booted it showed the battery at 0% and not charging.
I guess I'll try to leave it alone for a while and see if it will start up after being plugged in for a bit.
EDIT: I let it sit there and charge for about an hour or so (with the screen flickering) and I was finally able to get it booted. It said it only had 3% battery but now it seems to be charging as fast as usual.
devhen said:
EDIT: I let it sit there and charge for about an hour or so (with the screen flickering) and I was finally able to get it booted. It said it only had 3% battery but now it seems to be charging as fast as usual.
Click to expand...
Click to collapse
Yup... I've let mine sit there turned off and charging over night... helped!
Just had a problem with the Nexus 7 not charging when battery was likely fully depleted. Putting a charge cable in was automatically booting the Nexus 7 up and wouldn't charge shutting down right after. Loops going on and off. What I did was plug a charge cable in and hold power+both volumes and now I believe I am charging at the bootloader screen. It stays on so I will leave it like this and if it doesn't resolve the issue I will try recovery once it is charged.
I've just started having the same issue. Has happened twice when battery gets to 8%, suddenly jumps to 0, shuts down, then after a few seconds restarts itself. Gets to home screen for a few seconds, battery showing 8, then jumps to zero, switches off and has flickering blocks on screen with static noise. This keeps repeating, only way I have found to solve it is to load into bootloader, then select power off. Device charges normally then and once charged works fine. I am unlocked and rooted but running stock 4.2.1, think I'll just have to return it for a warranty claim.
Based on what you experienced, the lesson here is your device can't handle the GPU over clock of more than 446mhz or it will do some crazy stuff.
Sent from my Nexus 7 using xda app-developers app
hi all, today when my nexus 7 left around 15% battery, it showed the warning sign to ask me charge it, so i thought of finish download 1 small apps before charging it. just before i hit the install button, the screen suddenly turn off and whole device was power off.
i tried to on it back (press for 30sec) but no use. so i go and charge it, after trying many times, i finally managed to on it back, but just after few minutes, the screen appear many lines ( just like those old tvs) and it turn off again...then, i tried many times only i managed to on it back.
after that, i continue to leave it there to charge. but after almost 4 hrs( and still counting), the battery only 45%.
wat had happen to my nexus 7? previously i had no such issues, and normally i can fully charge it within 3 hrs. i just got it for 1 week, can anyone tell me what happened? will it damaged my device?
thanks.
no people facing same issue as me?
hey there, im facing the exact same issue and symptoms as you!
the sudden off, the old screen tv effect and shuts down again.
a battery logo appeared though and im leaving it to charge now. strangely it was showing 18%
im running cm10, what about you?
I've had the same issue for first 2 times I charged the Nexus, then it went away. Seems to be battery related, faulty battery?
Same thing happens to me as well. Happened on stock 4.1.2 and happens on stock 4.2 as well. I never try to let it reach below 20%, just to be on the safe side.
Me too!
ynrozturk said:
Same thing happens to me as well. Happened on stock 4.1.2 and happens on stock 4.2 as well. I never try to let it reach below 20%, just to be on the safe side.
Click to expand...
Click to collapse
It happens to me too
Not sure if it's battery related but it happened twice and this is what my battery graph looks like.
Anybody with more info?
I am also on CM10 using setCPU app to control CPU speed when the power is low.
There is one other thread talking about this:
http://forum.xda-developers.com/showthread.php?p=34878700#post34878700
I placed my info there too.
Edit: It's actually happened the last 3 days now ... I'm going to exchange it today.
I get a message "shutting down, low battery" I used to get message telling me to connect to charger. Before I could finish what I was doing now I have no choice. Seems to happen after update 4.3
fix
somehow the battery calibration is out. only fox is to leave it charging for about 20 mins before trying to turn it on. as by then only will the 'x' logo appear. OR if you cant wait popout the back cover, remove/unplug the battery it works. another longer fix is to. turn in back on after it is able to, go to battery settings refresh it, plgg and unplug your charger. the shutdown logo should appear again and when you look to the top, the battery % will revert to its correct amount of 0% try to do this as soon as it is able to be turned on.
Here is my problem. I have a Nexus 4 that constantly powers off. And by power off, I mean as soon as the Nexus 4 boots up into the OS, the phone starts the power off sequence.
What I've tried so far was:
- in recovery did a factory reset, wiped both the data and cache partition.
- tried reloading the official nexus 4 firmware. Tried the 4.4.4 and 4.4.3 image
- used fastboot to load up a custom recover only to realize there is no rom on the phone itself to install from so that's out of the question pretty much.
- I tried the adb sideload but the computer doesn't see the nexus 4. the computer however sees the phone when it boots into the OS but the phone starts the shutdown operation as soon as it loads the start screen.
If it's hardware issue, then I guess there's no point in trying to fix it. But if it's only software related I want to at least try to see if it can be saved. lol
Any suggestions?
Well I know this happens when you have 0% battery
maybe your battery isn't charging?
Try booting with your N4 plugged and leave it plugged so 5 minutes, check your battery status and if it's ok unplug it and cross your fingers.
Roastmeat said:
Well I know this happens when you have 0% battery
maybe your battery isn't charging?
Click to expand...
Click to collapse
I thought about that at first. but according to twrp the battery life was above 70% and can run on battery perfectly fine. The phone doesn't actually belong to me. She gave up trying to fix her problem and got a new phone. I just got curious and want to find out what is causing the issue.
danmen2 said:
Try booting with your N4 plugged and leave it plugged so 5 minutes, check your battery status and if it's ok unplug it and cross your fingers.
Click to expand...
Click to collapse
I left the battery charging all of last night just to try it regardless of what the status said. It was hovering at around 70-80% according to TWRP before I plugged it in. It actually made progress today. The phone booted up. So I put in LPV just for the fun of it. The first time it booted up into LPV, it was doing the shut down process as well. Plugged it back into the wall for 5 mins, unplugged it and turned on like normal. Went through the set up process.
Left it sitting there for about an hour. Then decided to shut down the phone and restart it to see if that issue would return. Didn't return until Play Store started doing updates. The phone shut down. Powered it back up and it was fine. lol. Battery life right now is sitting at 78% and battery widget reborn is saying the temperature is 39C. So it coule very well be the battery. But my friend said the guy she brought the phone for repairs supposedly changed the battery. lol. So I don't know.
Espada04 said:
I left the battery charging all of last night just to try it regardless of what the status said. It was hovering at around 70-80% according to TWRP before I plugged it in. It actually made progress today. The phone booted up. So I put in LPV just for the fun of it. The first time it booted up into LPV, it was doing the shut down process as well. Plugged it back into the wall for 5 mins, unplugged it and turned on like normal. Went through the set up process.
Left it sitting there for about an hour. Then decided to shut down the phone and restart it to see if that issue would return. Didn't return until Play Store started doing updates. The phone shut down. Powered it back up and it was fine. lol. Battery life right now is sitting at 78% and battery widget reborn is saying the temperature is 39C. So it coule very well be the battery. But my friend said the guy she brought the phone for repairs supposedly changed the battery. lol. So I don't know.
Click to expand...
Click to collapse
Yeah, sounds like a possible bad repair. Try another thing, flash a kernel not based on stock, like hell's doctor or hell's core. After 4.4.4 there are several issues like boot loops and shutdowns with kernels based on stock.
danmen2 said:
Yeah, sounds like a possible bad repair. Try another thing, flash a kernel not based on stock, like hell's doctor or hell's core. After 4.4.4 there are several issues like boot loops and shutdowns with kernels based on stock.
Click to expand...
Click to collapse
Well it's running Android L Preview port so it's not running 4.4.4 based rom. At least to my knowledge. I'm going to see how long this last. I suspect they didn't really replace the battery or it could be an issue on the motherboard side not detecting the proper charge level on the battery? But battery life so far on the phone seems pretty crappy. 13% in the last 45 minutes on airplane mode with wifi on.
So someone called me about 3 hours ago, and my phone just outright died. Couldn't turn it on - no signs of life, even though I had received a call just fine this morning, 2-3 hours before the random crash. Now I couldn't turn it on, and my first guess was that the battery was the culprit, though it was on charge through out the whole night.
So I pugged it into my powerbank, the phone turned on, but kept kinda bootlooping - where the "relock your bootloader pls" message would come up for half a second, followed by the phone restarting again to continue the cycle. This was without the battery charging animation - straight into booting.
After 20 or so tries to turn on it actually did, and I was able to discharge it past the point at which it crashed - most likely excluding the battery as the issue for now.
What could this be? Could it be a chip that's on its way out (as in about to brick my phone)? Anyone have any ideas as to why this is happening? Or maybe an app to check system stability / hardware test?
Edit: thanks to firefox, for saving the progress of this write up as my phone did the exact same thing after I locked it. My pebble watch vibrated to indicate that the connection is lost and I wasnt able to turn the screen on.
Had to plug the my 6P into my power bank again for it to turn on. Though it didn't do the glitchy bootloop this time.
My phone was acting normal until now. Today after completely draining the battery I went to plug it in at home. The usual battery charging picture appeared and I thought nothing of it. Then when I tried loading the phone, it loaded as normal till it got to the lock screen, where it showed the battery at 0%. If you leave the phone for a while, it goes back to booting and does the Android Animation for a long time before going back to that lock screen, showing 0% and repeating itself. If you try and login, by the time you get in, it will go back to the booting Android Animation.
I can't seam to get beyond this point. I tried turning off the phone completely, then turning it back on. I tried clearing the cache. Nothing. I am stock standard, not unlocked bootloader. I am on Android 8.1.0 Security Patch January 2018.
Any help would be appreciated.
Update:
Just letting you know it is.. 'fixed'. After unplugging the phone and letting it bootloop few times, it finally registered a battery level that wasn't 0%. It was 96% and as such ran like normal again. That being said, I am worried about this happening again, so I hardly think this is fixed, but just leaving this here for anyone else that comes across this problem. Also would love to hear any suggestions to possible fixes. Incase this was related to the other bootloop issues that cropped up last year, I have set my phone for OEM unlocking.
Save yourself the trouble and just unlock your bootloader now.