Develop Bugs

Nexus Rebooting Randomly

Its happened twice that i can remember now.
This morning in bed I grabbed the phone, deleted some emails, opened the browser and the screen went blank with the sound of a slight crackle. It then instantly revooted (google logo popped up etc).
Im concerned the phone is faulty. Is it likely just one of those things or does it sound more sinister?
Hope somebody can advise.

Mine rebooted once the other day. I don't necessarily think that the phone is faulty, it just has bugs that need ironing out.
Sent from my Galaxy Nexus using XDA App

it's just the apps
it can happen with any android device
just keep an eye on which app is causing it
you can pull out the logs and scan through it

I've been having the same thing as the OP. I get "Android is Upgrading" when it restarts, too.
In additiona I've seen (several times now) that when I press the power button to turn the screen on, it wont accept any input. After 30 minutes or so it spontaneously restarts and goes to the "Android is Upgrading" message when it restarts.
I'm on the verge of RMI'ing the thing as some of the other guys in the office who have it have not had the same problems.
I'm running vanilla sim free version, no operator tat installed.

L60N said:
Its happened twice that i can remember now.
This morning in bed I grabbed the phone, deleted some emails, opened the browser and the screen went blank with the sound of a slight crackle. It then instantly revooted (google logo popped up etc).
Im concerned the phone is faulty. Is it likely just one of those things or does it sound more sinister?
Hope somebody can advise.
Click to expand...
Click to collapse
Are you running a totally unmodified stock rom or have you flashed a custom rom/kernel/radio to it? Kernels are still being worked on and arent perfect yet.
Also Android 4 is still very new and alot of apps are not fully compatable and subject to crashing or crashing the system.
Everything will be ironed out in time
Mark.

[Q] Big problem after volume fix!

Hi all,
I purchase my Samsung Galaxy Nexus from 3 (Three) UK Store last Thursday. It has been faultless bar the odd hang which taking the battery out has resolved. Im using it on Orange.
However, this morning I picked up my phone and was notified I had the volume bix fix update.
I downloaded and installed the update and all was well for about 20 minutes.
Then my phone started going crazy!
I think its something to do with the screen as it keeps popping up the google search bar and flicking through some options, then the screen stops responding.
Sometimes the phone flicks between home screens partially and make them jiggle!
Locking and unlocking the phone gives me 5-30 seconds of normal use, then the phone goes crazy or just doesnt respond.
Ive turned the phone off and on, removed the battery and even reset it this evening.
It doesnt do it ALL the time, and whenever I try and do it on queue, it doesnt!
Luckily tonight I got video of the phone going crazy.
Can anyone help?
The phone is bog standard, ie no roms/roots etc.
Should I take it back or is there something I can do?
Also, since ive just reset the phone, ive had to set up my mail. Once the phone behaved I put in my account details and then it started popping up the menu button at the top of email, ie to change folders or accounts etc. Deffinately seems to be something with the top of screen.
Thanks
you tube.com/watch?v=x3Lf1IozPpw&hd=1
Please check the video out.

Maybe download the original shipping rom from Google and fastboot the image onto the phone and see if the behaviour continues.

braingravyuk said:
Maybe download the original shipping rom from Google and fastboot the image onto the phone and see if the behaviour continues.
Click to expand...
Click to collapse
This.
There's links to the original roms with or without the volume fix in place which can be found on the development section. I used this to update my gun and its working just fine. I'm also on Three UK and the reason I did this is because even though the volume bug doesn't affect us three users I still like being 100% up to date.
Rik.
Sent from my Galaxy Nexus using Tapatalk

[Q] Help Dealing with Unresponsive Screen/Buttons (Probable Water Damage)

On Friday night, My phone was in the breast pocket of a blazer that got very damp in an unexpected downpour. The phone continued to work on Friday night as far as I recall (I wasn't using it much, but I'm pretty sure I did use it some). When I woke up on Saturday morning, it appeared to be off and wouldn't turn on. I pulled and replaced the battery and still got nothing. I put it on the charger, but I had to run out, and I ended up being gone all day.
When I came home, the power button still wouldn't turn on the device. I pulled the battery and replaced it, and the Google screen came on, then the CM10 boot animation. When it got to the pin screen, however, the screen wouldn't respond to me entering my pin. Then, after a minute, the screen turned off, and the power button wouldn't turn it back on. I did a battery pull. Again, replacing the battery brought up the google screen, the CM10 boot animation, and the pin screen. But, again, the screen was unresponsive, and the power button did nothing when the screen went off.
I took it apart and left it alone all day Sunday. On Monday morning, I tried again and got the same results. I went and picked up a bag of white rice yesterday and left it in there last night and all of today. Still, I've got the same outcome. Buttons and screen are unresponsive.
So I'm left with a couple of questions:
First, is there anything else that can be done? This seems to me to be water damage. Does anyone have any suggestions for possible solutions?
And second, I keep getting text messages. Is there any way to pull those messages using the Toolkit or adb or anything (I'm pretty inexperienced with adb)?
Any help would be great. I'm stuck in China without a phone right now, which is a pain in the butt. I'd like to revive this, and I don't want to go track down a new phone until I know this one is sunk. Thanks for your help.

install android-sdk
run adb server on the host
connect your device to pc (feed it naked drivers manually found on dev section, if you're on windows and device manager shows unknown device)
type: adb devices
q: do you see your device listed? (should be lots of numbers and letters)
if it doesnt even recognizes that it has been plugged in, then your usb connection went down the drain, nothing else you can do

My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2

ejchis said:
My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)

bk201doesntexist said:
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)
Click to expand...
Click to collapse
And you would expect this to resolve the screen and buttons being unresponsive? This is interesting. Is it possible to pull my messages beforehand?
Sent from my Nexus 7 using Tapatalk 2

[Q] Galaxy Nexus wont Fastboot

Hi all.
I have a seemingly unique problem with my nexus, one day it got stuck in the boot logo. I gave the phone to a friend to fix, he used the galaxy nexus tool kit and halfway through solving the problem the phone crashed and now wont boot. At all. I am locked out of fastboot nothing at all is displayed on the screen, the tool kit wont detect the handset. There is no response when I push any of the buttons. I tried opening the phone and shorted out the power button. the only response I get from the phone it when I plug it in to windows 8 it get the sound on my pc to know it found hardware, then immediately followed by the disconnecting sound, and a little notification flashes from the system tray, If I am fast enough I can click on it and I get this message:
(I cant post a link as this is a new account) i.imgur.com/fmkE9Ki.png
I found on another thread that someone had a similar problem, they fixed it by getting a new battery, I did this and it still didn't work. i checked with a multimeter and they're both fine anyway. I am about to use my last resort and send it in to a paid service. Is there anything else i can try? or do you think a repair shop would have a better chance?
Thanks in advance for your time.

You're internal memory might be fried, happened to my first GN, was downloading something via a torrent app and all of a sudden the screen went black, had to pull battery and restart, first time it nearly got through the boot sequence but then froze up again, pull battery again to reboot but the second time it just started with major graphic errors and did not leave to Google logo screen.. Had to be replaced, good thing was that there was no way for service center to tell it was rooted ;P
Sent from my Galaxy Nexus using xda premium

Have you tried omap flash?
Beamed from my Grouper

[Q] Bought Refurb Tab S 8.4... odd booting issues

Generally when I get refurb, I have pretty good luck, but perhaps the forces that be are saying I shouldn't have one. When I first ordered, I got one with a dead pixel. Couldn't fix it, so I sent it back. Just today I got my replacement. I was pretty excited since the tablet looks brand new (still has most of the plastic on it around the edges. I charge it for a bit, turn it on and....
It played the Samsung startup music, but the screen stayed black. Didn't show anything. Keys lit up like they should, everything sounded normal, but was just black. For a while nothing happened, then finally the screen came on. It seemed to act normal from there on. Thinking nothing of it, maybe it was just a glitch, I took a few OTA updates. Every time it reboots, the screen issue comes up. And while it was updating, it didn't show the android updating screen. Also, I can't get it to go into recovery. Perhaps I actually am, but the screen is off so I can't see. I've searched and can't find anyone with a similar issue. Since this is my second device, should I just send it back and ask for a refund or is there something I can do to try and fix it?

Racso14 said:
Generally when I get refurb, I have pretty good luck, but perhaps the forces that be are saying I shouldn't have one. When I first ordered, I got one with a dead pixel. Couldn't fix it, so I sent it back. Just today I got my replacement. I was pretty excited since the tablet looks brand new (still has most of the plastic on it around the edges. I charge it for a bit, turn it on and....
It played the Samsung startup music, but the screen stayed black. Didn't show anything. Keys lit up like they should, everything sounded normal, but was just black. For a while nothing happened, then finally the screen came on. It seemed to act normal from there on. Thinking nothing of it, maybe it was just a glitch, I took a few OTA updates. Every time it reboots, the screen issue comes up. And while it was updating, it didn't show the android updating screen. Also, I can't get it to go into recovery. Perhaps I actually am, but the screen is off so I can't see. I've searched and can't find anyone with a similar issue. Since this is my second device, should I just send it back and ask for a refund or is there something I can do to try and fix it?
Click to expand...
Click to collapse
Well to force reboot, hold and press power+home+volume up and down until it reboots. Have you tried to also factory reset in recovery?

DUHAsianSKILLZ said:
Well to force reboot, hold and press power+home+volume up and down until it reboots. Have you tried to also factory reset in recovery?
Click to expand...
Click to collapse
I was trying to say I can't get into recovery. I don't know if it actually is in recovery with the screen off, or if I just cant get to it at all.

Additionally I just tried a KIES update, and it did not take. When I plug into KIES it says the same update is available even after I just updated it. Just now doing a software factory reset. So far no change. Unless someone can provide me information on how to fix this, looks like I'll be sending it back.

You will know if you're in recovery if you type 'adb devices' into a command window with the usb cable attached.
If it returns a set of numbers you're in recovery.