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
Related
is it normal that my touchscreen goes nuts sometimes? I find that sometimes (usually at night or first thing in the morning) my touchscreen on my n1 is inaccurate. I'll touch in the middle of the screen and it will click on something on the bottom of the screen. if I reboot my phone, the phone works great again.
yes its normal, its been posted here that even stock rom will get that problem now and then. Although mine has been random, not at a certain time.
Google is working on a software fix for it, and cyanogen 5053 (for my experience) has cut that problem to a minimum. I think ive experienced that problem 2 times since flashing. So a span of 3 weeks it happend twice. So i say its been pretty good.
And you dont need to reboot, just turn off the screen and turn it back on. Last i had a problem, i did that and it worked.
So as soon google fixes it im sure this board will be flooded with threads about it. And the devs are fast enough to implement it to their ROMS!
Are you holding it differently at those times? You mentioned at night or in the morning. Are you still in bed? I find I sometimes grip the phone is a way that my hand touches the edges of the screen. That throws off the touches and I've noticed it jumping down to a different icon at times. Just make sure your hand doesn't wrap around to the front of the screen.
My nexus one touchscreen will go nuts at times too. Locking the phone and unlocking does fix it though. I'm also 100% positive it has nothing to do with erroneous input from the way I'm holding it.
ya I was making sure that I wasn't holding it weird. hopefully Google makes a fix : )
p.s. thanks for the tip on turning off the screen rather than rebooting the device.
mine does this too but it seems that if I just put it to sleep and wipe it off it's back to normal
Sent from my HTC Dream G1 using the XDA mobile application powered by Tapatalk
Mine too does this w/ cyanogen 5053. sometimes it's so bad that i cannot even unlock the phone. I never noticed it this bad before on stock... but then again i only used stock for about two weeks before i rooted it.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
I'm on a non modded phone and I get it every once in a while. Hit the power button and all is well.
So I've had the vibrant freeze on me about 3 or 4 times out of the 2-3 weeks I've had it so far. It's gone black with the bottom four buttons still lit but it wouldn't shut of via the power button or respond to any other buttons either. Also, one time it froze yesterday after I did a master reset through the factory reset option. This time it froze while I was trying to do a speed test, the screen stayed on in the speed test window but buttons were once again nonresponsive. I haven't replicated it yet though. I have to pull the battery to get it restarted.
Another issue I've experienced a couple of times is the wifi would freeze when I turn it off through the power widget (my normal method of toggling wifi). It says that wifi is turning off but it stays in that state and never actually does. The green light would dim on the power widget as though it's turning off but it sticks there and under wifi info it just says it's turning off. When this happen, wifi will neither turn on nor off and just becomes unresponsive. I have to restart the vibrant to get wifi back to normal.
Anyone else experienced this or have any ideas on these problems?
Samsung Vibrant Freeze
drgnclwk said:
So I've had the vibrant freeze on me about 3 or 4 times out of the 2-3 weeks I've had it so far. It's gone black with the bottom four buttons still lit but it wouldn't shut of via the power button or respond to any other buttons either. Also, one time it froze yesterday after I did a master reset through the factory reset option. This time it froze while I was trying to do a speed test, the screen stayed on in the speed test window but buttons were once again nonresponsive. I haven't replicated it yet though. I have to pull the battery to get it restarted.
Another issue I've experienced a couple of times is the wifi would freeze when I turn it off through the power widget (my normal method of toggling wifi). It says that wifi is turning off but it stays in that state and never actually does. The green light would dim on the power widget as though it's turning off but it sticks there and under wifi info it just says it's turning off. When this happen, wifi will neither turn on nor off and just becomes unresponsive. I have to restart the vibrant to get wifi back to normal.
Anyone else experienced this or have any ideas on these problems?
Click to expand...
Click to collapse
has any solution been found for this ?? i have similar freezing issues with my vibrant .. i found one possible culprit listed on another site .. there is a way to disable the TeleNavGPS app (as you cannot uninstall) .. it is supposed that this interferes with the phone to the point of complete failure
Are you running stock 2.2 from Kies? I had exactly the same problems.
Sent from my SGH-T959 using XDA Premium App
You could try backing up and doing an ODIN flash to KA6. I've had similar lockups with some builds in the past but they are fairly infrequent. Currently running stock KB1 rooted with KA6 radio and it has been smooth for a long while now.
I've tried some of the 2.2.1 Roms, but I absolutely need wifi calling so I stick with stock.
Sent from my SGH-T959 using XDA Premium App
I have the same issue. On my second Vibrant running stock 2.2. About to send this one back for warranty as well. Mine will freeze from the lock screen, either stuck on the screen and the display stays on, or the screen wont come back on from idle.
FirefighterZ said:
I have the same issue. On my second Vibrant running stock 2.2. About to send this one back for warranty as well. Mine will freeze from the lock screen, either stuck on the screen and the display stays on, or the screen wont come back on from idle.
Click to expand...
Click to collapse
Have you tried another ROM? I thought my phone was broken with stock 2.2. Haven't had issues with Bionix.
Sent from my SGH-T959 using XDA Premium App
No other ROMs, I know there are a lot of good ones, but I shouldn't have to root my phone for it to work correctly. Within a week of this current Vibrant I was having these issues. I didn't purchase the Vibrant to flash ROMs, I bought it because of the specs to remain stock. On a side note..I was told after 3 warranty replacements within 90 days I will be able to get another phone from them.
FirefighterZ said:
No other ROMs, I know there are a lot of good ones, but I shouldn't have to root my phone for it to work correctly. Within a week of this current Vibrant I was having these issues. I didn't purchase the Vibrant to flash ROMs, I bought it because of the specs to remain stock. On a side note..I was told after 3 warranty replacements within 90 days I will be able to get another phone from them.
Click to expand...
Click to collapse
Yeah, know what you mean. It is silly that stock is just broken. Hopefully the OTA will be better than the Kies release. (Are they doing an OTA?)
Maybe they'll swap for a Nexus S.
Sent from my SGH-T959 using XDA Premium App
im rooted on android 2.2 but stock rom stock modem stock everything just root. i have had the same wif issue as the op. i just go to settings>wireless settings> wifsettings and turn on wifi that way. if you notice it will say error. 90% of the time this works and you will not have to reboot. i switch from wifi to 3g a lot. i have not figured the cause just yet but this is a work around for now.
as far as deleting the bloatware i rooted and deleted all that crap like sims, and other apps that i do not/will not ever use. there is a thread on which ones are safe to delete. be careful about deleting apps that are used by google such as google talk.
Unreal, Samsung. I wanted to sell my Vibrant, but can't get anywhere near what it's worth because of these stupid issues.
Sent from my SGH-T959 using XDA Premium App
I'm having the same problems!!!
I am now on the 3rd replacement (that's the 4th T-Mobile's Samsung Vibrant 3G!!!) and still having problems.
My phone will just be sitting on my desk at work and I'll hear it buzz a couple times. I know that buzz. It's something "Force Closing" in the background. I will pick my phone up and it will be unresponsive. It will light up the 4 buttons on the bottom of the device, but nothing else. Normally, it will then immediately start rebooting. It will go through the usual start-up screens. It will then show the status bar at the top; battery life, alarm clock, signal, 3G/WiFi, Media Scanning progress. However, the rest of the screen will be black. It will then vibrate once, then 2 more times and do it all over. It repeats this at least once for around an hour EVERY DAY!!! Other times, it will not restart on it's own and I will have to hold down the power button to manually do so.
I have also gone through ALL the troubleshooting I can imagine. All logs, history, texts, cache... EVERYTHING... has been cleared.
Please forgive me for asking, but it appears that I am to possibly root my phone for a resolution... is this true?
Also, has anyone heard of this "3 Returns Within 90 Days" policy with T-Mobile? I could easily do this with this phone. Has anyone had any luck getting them to do that?
Hi Geeks,
I think, I am having a weird problem with my Nexus7. Its been third time in a row that device gets shut down completely and abruptly at 10% remaining battery without any warnings ( The last warning that pops up is at 15% and then nothing.
When I turn it on while plugging in charger, it powers up and shows charging at 10% but as soon as I open any app, screen goes crazy like an old CRT television screen when no signal reception. Extreme flickr that can't even see anything. Also, no touch is responded I guess or don't know what happened on touch action. Then it shuts down again :[email protected]
If I left it charging for some time. It starts working fine till it goes down to 10% again.
Has anyone experienced the same or any suggestions to check before I contact support also, if device is rooted, do we get any support at all or not?
Device is rooted and boot loader unlocked.
So, before returning to Google I would need to restore the factory image on it. Can anyone please share the procedure to do that?
Thanks in advance for the help and looking forward to hear from you soonest.
Use the nexus toolkit, get stock recovery if you're on cwm or twrp. Then go to settings, security, factory restore (something like that).
Sent from my LG-P999 using xda app-developers app
I jst opened mine today and it did the same thing. Mine is not rooted so it is not the cause. At 10% bad CRT reception. I tried resetting the unit several time and noticed too that when the change is higher than 10% it goes back to work. I don't want the hassle of sending it back. If it happens, who should I call and how to send it back
perceptorz said:
Hi Geeks,
I think, I am having a weird problem with my Nexus7. Its been third time in a row that device gets shut down completely and abruptly at 10% remaining battery without any warnings ( The last warning that pops up is at 15% and then nothing.
When I turn it on while plugging in charger, it powers up and shows charging at 10% but as soon as I open any app, screen goes crazy like an old CRT television screen when no signal reception. Extreme flickr that can't even see anything. Also, no touch is responded I guess or don't know what happened on touch action. Then it shuts down again :[email protected]
If I left it charging for some time. It starts working fine till it goes down to 10% again.
Has anyone experienced the same or any suggestions to check before I contact support also, if device is rooted, do we get any support at all or not?
Device is rooted and boot loader unlocked.
So, before returning to Google I would need to restore the factory image on it. Can anyone please share the procedure to do that?
Thanks in advance for the help and looking forward to hear from you soonest.
Click to expand...
Click to collapse
Try wug's toolkit and for oem locking procedure, you can follow this youtube link http://www.youtube.com/watch?v=_uMdtjUh6Co&feature=relmfu :fingers-crossed:
redmonke255 said:
Use the nexus toolkit, get stock recovery if you're on cwm or twrp. Then go to settings, security, factory restore (something like that).
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the tip. Used Nexus Toolkit and it was breeze
fpaquin said:
I jst opened mine today and it did the same thing. Mine is not rooted so it is not the cause. At 10% bad CRT reception. I tried resetting the unit several time and noticed too that when the change is higher than 10% it goes back to work. I don't want the hassle of sending it back. If it happens, who should I call and how to send it back
Click to expand...
Click to collapse
Unfortunately my friend, I have no good news for you too I had chat with the Google Play support and they asked me to do factory reset claiming 90% of the time the issue is resolved. I performed as they said and waited for battery to drain to 10% and as soon as it hit 10%, the device shut down itself and then bad CRT. I gave them a call and they simply asked to return it. They sent me couple of emails, one for replacement order and other for logistics like UPS shipping label.
They sent me a new unit in 3-4 days and I am yet to return the old one, making sure nothing is wrong with the new one too. Its working fine so I will ship the old one back.
I am afraid, you will have to send it back too The number to reach them is: +1-855-83-63987
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.
Hi all
Anyone a clue why my screen gets on and off?
Any other screen would turn off in about 30 seconds and stays off
ya everyone will get the same. its in settings. you can modify by going into SETTINGS--->DISPLAY--->SLEEP.
Hi
I bought a Nokia 5, but every time I lock the screen the screen keeps flashing off and on. I tried going to settings - display - sleep, (but it doesn't allow me to switch it off completly, the least choice I have is 15 sec sleep, but it still keeps flashing off , on when screen is locked. Im afraid it will kill my battery faster... any suggestions.
I bought one for my girlfriend and this is the most annoying issue. I have tried everything. I thought that the screen protector is to blame, but it is not. Any other suggestions? I will send it for repair if it is not fixed.
Sent from my BTV-W09 using Tapatalk
Sorry to double post, but the issue has been fixed with the latest OTA. The screen does not turn on and off like before. No hardware reset was needed, so I guess it was a software issue fixed with the latest OTA from October. I tried contacting someone through the Support app on the phone, the solution was to either do a system reset or to send it to be repaired on warranty.