Develop Bugs

[Q] Galaxy Nexus keeps turning OFF

I have a problem with my Galaxy Nexus turning OFF at night.
I goto bed at night and open the clock app and click the screen to dim it. When I wake up in the morning the phone is OFF. I have to pull the battery in order to boot. The battery is fully charged.
I returned the phone after this happened twice and received a brand new one. I have the same problem with this new device. I have changed the power socket and the charger yet still the problem persists.
Is anyone else experiencing similar problems?
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.

Try it without any off your apps installed. If the problem goes away you know it's an app causing the problem. Then start adding them back in batches until the problem re-occurs. Eventually you'll narrow the issue down to one app.

mark_w said:
I have a problem with my Galaxy Nexus turning OFF at night.
I goto bed at night and open the clock app and click the screen to dim it. When I wake up in the morning the phone is OFF. I have to pull the battery in order to boot. The battery is fully charged.
I returned the phone after this happened twice and received a brand new one. I have the same problem with this new device. I have changed the power socket and the charger yet still the problem persists.
Is anyone else experiencing similar problems?
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.
Click to expand...
Click to collapse
This is happening to me too.
At random times, the phone will refuse to wake from sleep.
Nothing but a battery pull will fix it.
I don't have skype installed.

Have a look at this:
http://forum.xda-developers.com/showthread.php?t=1360880&highlight=sleep+of+death

Mine started today. Really hope this does not keep happening or I need to return this right away. Missed a few phone calls today and didnt realize until I looked down any my phone was just simply black. Will not wake up or do anything at all. You have to pull the battery. Right before this happened my data was dropping non stop about every 5 minutes for an hour.
I'm trying to stay calm because I love this phone, but between the data drops and the phone turning off im loosing patience quick.

This is happening to me as well. With TWO different phones. The first one I returned to Verizon and now its happening on the second one.
Phone will power off while doing random tasks. The two I've noticed is browsing on the stock browser and texting on the stock texting app.

I'm having the same problem. It's happened twice in the 3 days I've had the phone. It hasn't happened while I'm using it, both times it was when the screen was already off -- it just wouldn't waku up. Nothing short of pulling the battery, letting it sit, then powering on would work.
Couldn't have come at a worse time either, my daughter is in the hospital and I get updates from the surgeons via phone. So now I have to check every 5 minutes and make sure the phone is still on.
Phone is bone stock, out-of-the-box.
Sent from my Galaxy Nexus using Tapatalk

i just had my first turned off this morning... my friend's SGN happened 5 days ago too. very unreliable....

I had that happen to me as well. Turns out I forgot that I had an app scheduled to do a backup at like 3 AM.
Sent from Galaxy Nexus
CodenameDroid 1.2 cdma & Franco 14.4

My sgn turned off every night now. Anyone got any ideas why? I turned my verizon backup already.

reboot durring skype call
mark_w said:
I have Skype installed and running which maybe the cause. I will keep it OFF for the next few nights to see if this has a positive effect.
Click to expand...
Click to collapse
it does it when i have skype running too. also i have other other audio apps open. (power amp, tunein, pandora) It's happened twice to me and each time it has been during a skype call while the other apps were running. (in widget form)

shock sensitive in the area right below the camera?
My device just "randomly" switches off (sometimes several times a day). After a long search for a reproducible cause, it seems safe to say that at least some devices seem to be extremely shock sensitive in the area right below the camera (on the back of the device). Even minuscule shocks to this area switch these devices off. Youtube-user 'jardinepatten' demonstrates this problem nicely in a video called "Galaxy Nexus Turning Off".

question about smart covers

I just got my MoKo case for this. The smart cover is great and turns the screen off and on without having to mess with the power button all the time. But when the cover is closed for any long period of time, the screen does not turn on when the cover is opened. Why is that?

This has come up in a few threads. For me, it seems to be correlated with having no wifi connection. I've never seen the delay when wifi is operational, only when I've either turned off wifi or am no longer in range of the wifi I was connected to. At home, where I always leave wifi on, I can have it off overnight and it still comes on instantly when I open the case the next day.

If you set WiFi to turn off when the tablet is a sleep it will not turn back on after 15-30 minutes. I have mine set to WiFi always on and it works fine. If you want to save a little battery you can turn wifi off manually at night. Shame it doesn't work like the original Nexus 7.
Sent from my Nexus 7 using xda premium

ncguy68 said:
If you set WiFi to turn off when the tablet is a sleep it will not turn back on after 15-30 minutes. I have mine set to WiFi always on and it works fine. If you want to save a little battery you can turn wifi off manually at night. Shame it doesn't work like the original Nexus 7.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Although I don't have any of my wifi settings set to limit anything and are all set as suggested above, this was still occurring. I just tested this out with WiFi off and wifi settings don't appear to be the factor at all. With the tablet plugged in, I closed the smart cover and opened it about 45 minutes later and the screen came on fine. I unplugged it from the charger and closed the cover again for 45 more minutes and this time the screen did not turn on. Any ideas?
There is one setting that I do not have turned on and it's new to 4.3:
"Scanning always available
Let Google's location services and other apps scan for networks, even when WiFi is off"

When my Nexus is plugged in it never enters deep sleep and the auto on/off works fine.
When I changed the WiFi advanced setting to Keep WiFi awake during sleep to Always auto on/off works fine. If I turn WiFi off or set it to turn off during sleep the auto on/off will not work after 15-20 minutes.
I figure it has something to do with WiFi and/or deep sleep mode.
Sent from my Nexus 7 using xda premium

I had this issue when I was on stock. I believe the device has crashed. At this point, only option I had was to hold the power button until a full reboot.
Ever since switching to the CM10.2 nightlies, have never seen this issue again.
So my recommendation, get off of stock ASAP. :laugh:

That has nothing to do with it here, nothing is crashing. I think it's the smart cover not having the capability to waken the screen when the tablet is in deep sleep. It sounds to me like you traded crashes for something preventing deep sleep.

N7 had been closed for an hour.. I have Wifi off when screen is off... so *IF* that is the cause
- picked up the tablet, opened the cover.. did not turn on
- closed the cover
- opened again, N7 came on
so.. I ask, exactly how did the 1st failed opening wake up the Wifi (but not the tablet) if that is the culprit?
ie. if the determining failure condition is Wifi off rendering the cover unable to wake the tablet, I should be able to open/close/open the cover 100 times in a row without having it come on.

I don't know what the mechanism is, I just know it has never failed to come on instantly when it had a valid wifi connection.
It sometimes (but by no means always) has a big delay when wifi is off.
Those are the only two data points that seem consistent to me. Perhaps it does have to be off a long time and also have no wifi for the cover to not wake it immediately, but I haven't actually noticed if that is the case.

zim2dive said:
N7 had been closed for an hour.. I have Wifi off when screen is off... so *IF* that is the cause
- picked up the tablet, opened the cover.. did not turn on
- closed the cover
- opened again, N7 came on
so.. I ask, exactly how did the 1st failed opening wake up the Wifi (but not the tablet) if that is the culprit?
ie. if the determining failure condition is Wifi off rendering the cover unable to wake the tablet, I should be able to open/close/open the cover 100 times in a row without having it come on.
Click to expand...
Click to collapse
How long did you wait after the failed attempt to try the second attempt? Perhaps its just very very delayed the first time, and by the time you try the second time its "woken up" and ready to respond correctly?

muyoso said:
How long did you wait after the failed attempt to try the second attempt? Perhaps its just very very delayed the first time, and by the time you try the second time its "woken up" and ready to respond correctly?
Click to expand...
Click to collapse
I actually just got this case too well this one (http://amzn.com/B00CKA1IYU). Not sure if its the one you purchased. Mine was sitting in my office closed for about 45 minutes with WiFi off. I went over to open it and the screen turned on. I put it in my backpack later in the day and it sat there for about 30 minutes and I drove home. I got home and took it out of my backpack and set it on my desk unopened and with WiFi still off. I let it sit there for about another 30 minutes. I read this post and thought "I haven't opened the cover since before leaving work". So out of curiosity I opened it and the screen turned on.
So either my Nexus 7 isn't going into sleep with WiFi off or it actually works?
BTW: I like the case for the price! Bought 2 days ago so I paid 12.99 w/ free shipping.

Not the same but it's the same manufacturer so probably the same magnet

muyoso said:
How long did you wait after the failed attempt to try the second attempt? Perhaps its just very very delayed the first time, and by the time you try the second time its "woken up" and ready to respond correctly?
Click to expand...
Click to collapse
You have asked the magic question.
Left the N7 overnight.. got up, opened the case.. and watched... it took 10-15 seconds and then the screen came on, certainly very delayed, but as a consequence of opening the 1st time, as it should.
Just repeated the experiment after an hour.. ~9 seconds from flap open to display on.

cowabunga said:
I had this issue when I was on stock. I believe the device has crashed. At this point, only option I had was to hold the power button until a full reboot.
Ever since switching to the CM10.2 nightlies, have never seen this issue again.
So my recommendation, get off of stock ASAP. :laugh:
Click to expand...
Click to collapse
which CM10.2 nightlies are you using?
because i found there are few CM ROM in here.
thank you

prowede said:
which CM10.2 nightlies are you using?
because i found there are few CM ROM in here.
thank you
Click to expand...
Click to collapse
I run the official one from http://get.cm/?device=flo
Just get the most recent one (ie. dated 8/21 as of right now)

cowabunga said:
I run the official one from http://get.cm/?device=flo
Just get the most recent one (ie. dated 8/21 as of right now)
Click to expand...
Click to collapse
I just tried the official CM Rom today, however, the problem still exists.
I have tried different version (21, 23,24/8), still the same....
Very strange...

Problem still exists with Spet 11 build.
A pretty long lagtime for the wifi to reconnect before turning on the screen.
Turning on bluetooth is a workaround.
So smart wake waits for a wireless connection?
Wasn't the case in the old Nexus 7.

bland.life said:
Problem still exists with Spet 11 build.
A pretty long lagtime for the wifi to reconnect before turning on the screen.
Turning on bluetooth is a workaround.
So smart wake waits for a wireless connection?
Wasn't the case in the old Nexus 7.
Click to expand...
Click to collapse
For now (until there is a fix), turn on bluetooth and leave that enabled.. very little power drain, and prevents the delay turning back on.

zim2dive said:
For now (until there is a fix), turn on bluetooth and leave that enabled.. very little power drain, and prevents the delay turning back on.
Click to expand...
Click to collapse
If I have Bluetooth on and leave the cover closed for a long time and when I open the cover again the WiFi will not turn on.
In one instance I can flip the WiFi switch in Settings to on but it will revert to off, in another instance the switch simply refuse to barge.
Rebooting the device fixes it and brings WiFi back (until the next long cover closure).

bland.life said:
If I have Bluetooth on and leave the cover closed for a long time and when I open the cover again the WiFi will not turn on.
In one instance I can flip the WiFi switch in Settings to on but it will revert to off, in another instance the switch simply refuse to barge.
Rebooting the device fixes it and brings WiFi back (until the next long cover closure).
Click to expand...
Click to collapse
then you have a different/worse issue from everyone else (ie. the delay turning on after cover is opened).
I'd do a restore from a factory image, and try that for 2 days.. if it still won't turn on, you need to RMA yours.

[Q] Wifi doesn't start at boot

More often than not, when I start up my G pad, the Wifi does not turn on regardless of the way it was set before. Toggling the button on quick settings, or tying to turn it on manually in settings, does nothing; it says "turning on wifi", but it hangs. Rebooting usually fixes it, but sometimes requires more than one try.
Has anyone else experienced this? I'm hoping that it's a software glitch that will get fixed in the next ota update or when I flash my next rom, whichever comes first. If it's a hardware problem, however, I'd better return it before my rma period expires. Any ideas?
Thanks!

In the advanced setting under WiFi do you have the tablet set to keep WiFi on during sleep? I never turn mine off and do not have a problem. Using a v500 not a v510.
Sent from my LG-V500 using XDA Premium HD app

yojimboj said:
More often than not, when I start up my G pad, the Wifi does not turn on regardless of the way it was set before. Toggling the button on quick settings, or tying to turn it on manually in settings, does nothing; it says "turning on wifi", but it hangs. Rebooting usually fixes it, but sometimes requires more than one try.
Has anyone else experienced this? I'm hoping that it's a software glitch that will get fixed in the next ota update or when I flash my next rom, whichever comes first. If it's a hardware problem, however, I'd better return it before my rma period expires. Any ideas?
Thanks!
Click to expand...
Click to collapse
Yes, I've experienced it, if by starting up the G Pad you mean from it bring completely shut down, rather than sleeping. Also happens when doing a restart sometimes. As you say, a further restart sorts it out. I very rarely shut the tablet down or restart it though, usually I just let it sleep, so it hasn't really bothered me, except for the first time when I thought for a horrible moment the wireless hardware had died!

Wht if you don't want to use wifi when you boot the tablet? Then you have the wifi radio wasting battery from the start. Can't you install an app tht turns on the wifi at boot?

It took 6 reboots to get wifi working this mornino! Previously it had only taken 1-2 tries. It also had seemed on previous occasions that rebooting while unplugged would be more likely to successfully turn it on, but no luck; it failed multiple times both plugged and unplugged.
Needless to say, I will never turn the damn thing off if I can help it, but I'm not exactly happy about it.
LBJM, I rarely want to start up without having wifi enabled, but I suppose you could use apps like Tasker or Llama to turn it on or off under certain conditions.

LBJM said:
Wht if you don't want to use wifi when you boot the tablet? Then you have the wifi radio wasting battery from the start. Can't you install an app tht turns on the wifi at boot?
Click to expand...
Click to collapse
The issue isn't simply that Wi-Fi is off when the tablet first boots up, it's that it refuses to switch Wi-Fi on until it's restarted a second time, so don't think this would help.
---------- Post added 30th January 2014 at 12:01 AM ---------- Previous post was 29th January 2014 at 11:55 PM ----------
yojimboj said:
It took 6 reboots to get wifi working this mornino.
Click to expand...
Click to collapse
6 is getting a bit crazy! Thankfully a single restart worked for me on the couple of occasions it happened. I've actually ended up restarting a few times over the past week for other reasons, but haven't seen this issue occur again. I'm going to shut it down completely shortly, so will see what happens then.

I would take that in for a warranty replacement. That sounds like a dodgy network chip on the main board. I just restarted today and had no problem like what you mention.
Sent from my LG-V500 using XDA Premium 4 mobile app

I turn it off every night and in the almost couple of months that I have had my G Pad I have never had this problem.

Yeah I would RMA your Gpad. You shouldn't have to jump through hoops to turn on wifi.

Oddly, the issue has pretty much stopped - - just as well, since I was past my RMA date! I'm going to chalk this one up to some odd app interference, since it resolved with any rom updates or re-flashing.
Thanks again to everyone for their help!

[Q] Watch continues to disconnect?

Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?

Noticed the same with my 360 and Nexus 5. Both on stock latest versions.

Issue with mine is that the Moto360 constantly says Disconnected when trying to connect to my Note4. I click connect, it says connected and then quickly changes to Disconnected.
Been trying to figure it out for 3 days now.

I think I realized that the issue is in reconnecting.
I still don't know why sometimes it disconnects, but disconnecting itself wouldn't be an issue if then it proceeds to reconnect on its own.
But I realized that when I'm at home, I leave my phone by the computer and walk around. If I walk outside of the bluetooth range, then it disconnects. That's fine. But then it should reconnect when I come back into range, and it never does. It says "Connecting" and never reconnects unless I do it manually as I said in the OP.
So I guess the question becomes: why does it get stuck on "connecting" when it's in range and should be connected? Is this a Samsung issue or a Moto360 issue?

I have seen the same issue with my Moto 360 and an original Moto X. It normally reconnects but then once in a while it just won't. The easiest solution I have found is to turn bluetooth off and then on again on my Moto X. That always brings it back, a reboot of the 360 does not.

Well as I said in the OP, if I go into Android Wear, click Disconnect and then click Connect, it works. But there is absolutely no reason why it shouldn't auto-connect. If it disconnects, and I don't notice, the rest of the day I go without notifications until I realize the watch has disconnected. That's not how this should work.

Max_Pain said:
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Click to expand...
Click to collapse
Hi, i have the same problem, my watch always disconect to my phone (moto x), and then the bluetooth system never start again. When I enter in setup ---- bluetooth---- the bluetooth switch doesn t turn on again until phone reboot.

this is so annoying. and it seems like there's a few people experiencing the same thing but nobody seems to have hit a solution. I have yet to come up with one. if I do, i'll post on here.

Same happens with mine. It just prompts me with a "connect" screen on my phone once in a while. After connecting 2-3 times, it won't appear until next time I turn off Bluetooth.

I get this problem about 2 times per day...running with a Note 2 running 4.4.2 stock but rooted....

Disconnect and reconnect issues

Been use for two days now just one reconnect issues once disconnect from phone it really have hard time to reconnect by itself I must either turn off Bluetooth from phone or restart watch every annoying
Sent from my D6503 using XDA Free mobile app

paullu said:
Been use for two days now just one reconnect issues once disconnect from phone it really have hard time to reconnect by itself I must either turn off Bluetooth from phone or restart watch every annoying
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Mine disconnects if I go over 50ft from my phone but quickly re-connects when I get back in range. I love the watch!

I have the same problem: mine never reconnects automatically, i always have to turn off bluetooth and turn it back on. Maybe a Nexus 4 (LG) Problem?

paullu said:
Been use for two days now just one reconnect issues once disconnect from phone it really have hard time to reconnect by itself I must either turn off Bluetooth from phone or restart watch every annoying
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
mark2k said:
I have the same problem: mine never reconnects automatically, i always have to turn off bluetooth and turn it back on. Maybe a Nexus 4 (LG) Problem?
Click to expand...
Click to collapse
Yes, I have the same problem and it's very annoying. Every time I flash a new rom or update a rom(Vanir LP) to my phone(LG G3), I have the hardest time getting it to reconnect. I always have to reset the watch to get it to connect again.

Mine worked, connected and reconnected flawlessly and quickly the first five days that I owned it. However the last few days, it's disconnected when I wake up and I have a hard time reconnecting. Now the watch says that it's connected to the phone, but the phone (Android Wear App) can't see the watch. Very weird. I've reset the watch three times. I've un-paired and re-paired the devices in bluetooth. I've cleared cache and cleared stored data and uninstalled Android Wear App, then re-installed it. The Android Wear App just can't find the watch anymore, but the the Watch still shows it's connected. This is maddening.

mark2k said:
I have the same problem: mine never reconnects automatically, i always have to turn off bluetooth and turn it back on. Maybe a Nexus 4 (LG) Problem?
Click to expand...
Click to collapse
FWIW, I don't have any problem with my ZenWatch and Nexus 4. I've had the watch for a few weeks now, and no connection problems with it. I do notice that it doesn't maintain the connection for as large a distance as my old Sony Smartwatch did, but it doesn't have any problem reconnecting. I figure the distance issue is because of the use of Bluetooth v4 instead of v3 with the Sony.

Disconnection to Apple Iphone 5
I have the same problem. Does not reconnect. I've tried everything. The only way to reconnect is to unpair the watch which resets the watch to factory default and establish a new connection to the watch.
After software update cannot answer calls etc.
Functionality wise not very good especially to iphone.
Good looking watch though.