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
happened on two different roms (RR and LOS)
battery < 10%
plug phone in to charge overnight (wall outlet)
find the phone bootlooping in the morning (probably after 4-6 hour charge) maybe not bootlooping, but stuck on boot animation
unplug, hold power to turn off and turn on
phone boots, but all app data has been wiped
really annoying problem that i hadnt had in over a month with RR as daily driver. switched to LOS and just happened again
I have a feeling this is hardware related now... and not necessarily related to the low battery state when plugged in... seems like battery charges up and then this occurs, but im unsure how to diagnose the issue... google has failed me on this one :crying:
Finally figured this out, hopefully helps someone else
After phone has rebooted on its own and is stuck on the boot animation, unplug the USB adapter. It will eventually boot and then reboot again on its own. Once it does boot the second time, it will be fine
The wiping was happening because I was holding down power to force the reboot. Should not do this
Very surprised that I am the only one reporting this on this device and that no one else has even heard of this. But ok
TLDR: are there any diagnostics I can do to verify that my battery needs to be replaced?
A few days ago, I turned on my phone to check the time and a half-second later it suddenly and instantly shutdown. I was not able to restart it at all. When I got home and plugged it in, it began a continuous boot loop, with only the motorola splash screen displaying, then nothing for a few seconds, then back to the splash screen over and over.
Fortunately, I was able to get to the"AP Fastboot Flash Mode" menu. I couldn't do anything from there on the phone itself though; every option just went into the boot loop again. I was able to get a fastboot connection with my PC and so reflashed the phone successfully.
After reflashing, it went into the boot loop again. I began looking for more solutions online and wasn't paying attention, but sometime in the next 5-10 minutes it made it to the login screen! I re-set up my phone and all seemed to be working fine!
Until the next day. I tapped an app and instead of opening, the phone immediately shutdown and went dead again. Took it home, plugged in, and it went into the boot loop again.
Anyway, I've read a few threads on here and elsewhere that the culprit may be the battery. I would like to have more than just a hunch before I shell out the money and time to replace the battery -- is there any way I can verify that the battery is indeed the problem? I didn't seem to be having any battery problems before - charging and usage seemed fine. I did drop the phone rather hard a few weeks ago, but didn't seem to effect anything (short term at least).
Also, could using a non-Droid Turbo 2 charger affect battery life? I actually got the phone used and didn't get the official charger with it, so I've been using just a random leftover one for ~6 months.
TIA!
walter77d said:
TLDR: are there any diagnostics I can do to verify that my battery needs to be replaced?
A few days ago, I turned on my phone to check the time and a half-second later it suddenly and instantly shutdown. I was not able to restart it at all. When I got home and plugged it in, it began a continuous boot loop, with only the motorola splash screen displaying, then nothing for a few seconds, then back to the splash screen over and over.
Fortunately, I was able to get to the"AP Fastboot Flash Mode" menu. I couldn't do anything from there on the phone itself though; every option just went into the boot loop again. I was able to get a fastboot connection with my PC and so reflashed the phone successfully.
After reflashing, it went into the boot loop again. I began looking for more solutions online and wasn't paying attention, but sometime in the next 5-10 minutes it made it to the login screen! I re-set up my phone and all seemed to be working fine!
Until the next day. I tapped an app and instead of opening, the phone immediately shutdown and went dead again. Took it home, plugged in, and it went into the boot loop again.
Anyway, I've read a few threads on here and elsewhere that the culprit may be the battery. I would like to have more than just a hunch before I shell out the money and time to replace the battery -- is there any way I can verify that the battery is indeed the problem? I didn't seem to be having any battery problems before - charging and usage seemed fine. I did drop the phone rather hard a few weeks ago, but didn't seem to effect anything (short term at least).
Also, could using a non-Droid Turbo 2 charger affect battery life? I actually got the phone used and didn't get the official charger with it, so I've been using just a random leftover one for ~6 months.
TIA!
Click to expand...
Click to collapse
Try the apps such as Ampere which shows battery info.
I don't think so Non-Turbo charger can lead to affect the battery life but using a cheap charger does.
my S7edge, with Stock ROM, never flashed or hacked it.
was working perfectly fine.
Last software update package was a week or 2 ago.
Today, the phone suddenly froze while I'm using it, then restarted and kept rebooting automatically in an endless loop.
I tried to force it to go to recovery mood... it would go to a blue screen saying : "Installing updates" and nothing happens.
kept rebooting into safe mode or recovery/download mode until it suddenly just went totally off.
The charger wires were a bit cut lately, so it would give a broken charging lately, not sure if that caused any kind of problems to the battery or mother board.
Since then, I am not able to turn it on again in any mode.
It also doesn't show any indications when a charger is connected.
So right now it is just dead with no signs at all. non responsive to any force power ON nor to charging.
I left it for more than 5 hours now without charging, nothing changed.
Update:
So I left it overnight. In the morning, I connected the charger and indeed it drained to 0% and started being responsive to charging again.
As soon as it charged to 20% I powered it on. It loaded into recovery, giving the no command screen. Then I went on and selected system reboot.
Then it rebooted and Android started, as soon as I tried unlocking it, it froze and started again into an endless rebooting loop until it blacked out again. Now again not responsive.
I will leave it to drain again. Does anyone know what I shall do when it gets to that endless rebooting sequence. It is obvious that Android had a malfunction... not sure what as I didn't do anything new last week..
Is there a way to get it through without factory reset?
Thanks
s0000007a said:
my S7edge, with Stock ROM, never flashed or hacked it.
was working perfectly fine.
Last software update package was a week or 2 ago.
Today, the phone suddenly froze while I'm using it, then restarted and kept rebooting automatically in an endless loop.
I tried to force it to go to recovery mood... it would go to a blue screen saying : "Installing updates" and nothing happens.
kept rebooting into safe mode or recovery/download mode until it suddenly just went totally off.
The charger wires were a bit cut lately, so it would give a broken charging lately, not sure if that caused any kind of problems to the battery or mother board.
Since then, I am not able to turn it on again in any mode.
It also doesn't show any indications when a charger is connected.
So right now it is just dead with no signs at all. non responsive to any force power ON nor to charging.
I left it for more than 5 hours now without charging, nothing changed.
Click to expand...
Click to collapse
Bro flash latest stock rom
Solved !
It was already on stock ROM.
After lots of troubleshooting, rebooting in safe mode without the SD card worked fine. I then rebooted in Recovery mode, wiped the cashe, rebooted again normally with no SD card. Then inserted the SD card after.... got a message that SD card is not supported (seems it got corrupted somehow).
Anyways, now it's fine... let's see for how long...