Develop Bugs

[Q] Galaxy Nexus keeps crashing randomly

Hey guys, i need some advise here!
For weeks, i anxiously waited for the mailman to bring my my GNex and for a few days im very happy with it. Unfortunatly, the major plus of android, it never freezes, isnt true for my brand spanking new Gnex!
Seeming randomly, the phone freezes, refusing all input from the screen and the On/Off button. This happens about every 20 hrs.
Ususally i advise people with this problem to exchange their phone with a different one, but im afraid i wont get a stock 'yakju' build back in return, so want to try to fix (or at least determine) the problem first.
Can you guys give me some tips on how to get to the bottom of this?
Thanks in advance!
Info:
Model: Galaxy Nexus (GSM)
Android version: 4.0.1
Smalbandversion: I9250XXKK1
Kernel: [email protected] #1
Build: ITL41F (yakju)
And again, it's all stock

...
i had a lot of problems with the 4.0.1 fw, have you tried updating the phone to 4.0.2 it solves a lot of bugs!

I tried to update the phone through the system update menu in the settings, but it listed my phone as 'up to date'. I find this is odd, since i have a Nexus ánd the Google build
Is there a way of updating the phone without a lot of hassle?

I looked into it, in the Netherlands the 4.0.2 update should roll out in a few days. If it isn't, I'm going to flash it myself! Were your problems with 4.0.1 similar to mine e.g. crashes and freezes?
Sent from my Galaxy Nexus using XDA App

In my experience most of the time when that happened was caused by 3rd party apps that weren't ics optimized.
Sent from my Galaxy Nexus using XDA App

Well freezes and crashes maybe, but the whole phone unresponsive? Isn't there a try/catch somewhere which prevents this kind of 'dirty code' to crash the whole OS, anyway there should be.
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Sent from my Galaxy Nexus using XDA App

Same problem
Panatella said:
Also, ( I forgot to mention this in #1) the phone reboots sometimes while its active as well as when its idle. The rebooting is always paired with a loud *click*
Click to expand...
Click to collapse
That exact thing happened to me yesterday as well (running 4.0.1). I pulled down the notification bar, clicked on the email notification, and when the notifybar started collapsing again, the animation stopped, sound was caught in a loop, and two seconds later my phone rebootet with a clicking sound (I hope that it was just the speaker reacting strangely to the sudden signal loss...!)
The same day, the Nexus kind of crashed while I was streaming internet radio to my bluetooth speaker. The music kept on playing fine, but I wasn't able to turn on the screen. Even holding the vol+/- and power buttons only shut the phone down, but I couldn't restart before I removed the battery.
I really hope this is gonna be fixed with the 4.0.2 / 4.0.3 firmwares. This thing is crashing a little too often right now, for my taste

I'm getting the same problems as noted above. I've just picked up the nexus to move away from Apple's iPhones, but I'm left wondering I've made a serious mistake in doing so. An added problem is that the crash has also occurred when I've been recharging the battery while asleep- so the alarm I set did wake me.
Honestly, it's an unreliable product. I'm a customer, not a Samsung lab rat.

Got the same issue. 2 crashes in 4 days. Not a huge problem for me yet, but 4.0.3 better fix it.

Well most of my problems went away when i updated my phone. You should definitely try to update. Personalty I went straight for 4.0.3. The best ROM i've tested is definitely Android Open Kang Project :http://rootzwiki.com/topic/11455-rom-android-open-kang-project-maguro-build-13/
Everything just went so smooth and bugfree as far as i can tell. And i love the quick setting he put in notification bar.
You can see how to unlock your phone here using the gn toolkit :
http://forum.xda-developers.com/showthread.php?t=1392310

I had those kinds of crashes, too. My phone would crash maybe once every 3-4 hours on 4.0.1... doing anything. Whether it be idle, with no extra services (factory reset), or while composing messages. Anything would do it.
Anyway, I rooted the phone and I've been on Bigxie's ROM since V1 (AOSP 4.0.3) and the issue stopped, for the most part, except for an idle reboot every 18-28hrs. Suspecting it was kernel related, I swapped out the Apex kernel and threw on Franco's... since then, my phone can run for almost two days (of moderate usage) without a charge.

Any of you guys enabled 'force 2d hardware acceleration'? I don't know how relevant it is, but all my problems went away when I stopped to use this function.
Sent from my Galaxy Nexus using XDA App

Uv'ing too low can crashes also.
My grandma beat me down and took my nexus. Sent from a jitterbug with beats by dre.

Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???

dhruvraj said:
Well this is exactly what is happening to me on my phone, it reboots every 2 days or so. sometimes it becomes completely unresponsive, the keyboard doesnt open up or of it does, it doesnt accept any input
even the settings page starts crashing, i dont know what is going on
it works ok otherwise but this crashing and becoming unresponsive is really driving me crazy. i have 4.0.1 as i am in the UK and since they are not releasing 4.0.3 for such a long time here, it means the fixes available in it is not really for stability and maybe they are for LTE version available in the US
Also, I dont have the 2d acceleration checked off already, so not sure what else to do to fix it. should i return the phone???
Click to expand...
Click to collapse
U sure it's not a software u installed recently? For me changing back to the stock music player fixed the random crashing.
In general, I can say some apps are not stable at all.

I experience random crashes too, although they coincide with the sudden loss of signal, as described in these threads:
http://forum.xda-developers.com/showthread.php?t=1390816
http://forum.xda-developers.com/showthread.php?t=1387943
http://forum.xda-developers.com/showthread.php?p=20816554
I have started to make some logs to try to identify the cause of this problem. I use Log Collector for making a log and No Signal Alert to obtain a time stamp when the signal drops. What I see in the logs is that just before the signal drops I notice an entry in the log something like "process:com.lookout has died". Could this have something to do with the Lookout app I have installed or is it just coincidence that the app and a certain Android process have the same name?
By the way, does anybody know if there are websites or people who can analyze the logs I have created? Most of the content is mumbo jumbo to me and a knowledgeable person might be able to shed some more light on what happens inside the phone and what might trigger this problem.
I just upgraded to 4.0.2 on Thursday, but the problem persists.
Android version 4.0.2
Baseband Version: I9250XXKK6
Kernel Version: 3.0.8-gaaa2611
[email protected]#1
Build Number: ICL53F
ICS stock; non-rooted

Well i guess you tried already to remove the lookout app right?

My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.

b4cksl4sh said:
My GSM Nexus with stock 4.02 (unrooted) freezes randomly too.
When it occurs i cannot switch the screen on using the power button. Only thing that helps in this state is pulling the battery.
Iam starting to get extremely annoyed by Google/Android because my previous smartphone the Nexus One was also buggy ever since the Gingerbread update while beeing perfect with Froyo.
It's definately my last Android device if this will not be fixed with 4.03.
The phones are way too expensive to be a happy participant of a perpetual Google beta.
Click to expand...
Click to collapse
Are you sure it's the OS not some buggy/incompatible apps? I've had the phone since launch and it never froze even once. Stock 4.02 too.
And you should try out different OS. Then you will know what suits you.

[Q] Anyone else getting frequent disconnects (3-4 times per day)

I haven't been able to get through one day without having to do a complete reset of my 360. It will disconnect from my phone about 3 or 4 times per day and the solution is some random combination of massaging the watch and Nexus 5 through restarting the phone/watch, connecting/disconnecting in the Android Wear app, or ultimately resetting the watch and going through the whole setup again. I am using a Nexus 5 with CM11 on it. Is anyone else having this issue?

Using an ancient GS2 with CM11 and get an issue where my bluetooth turns off and can't be turned on so I have to restart, but I think my bluetooth module is damaged, your phone bluetooth doesn't turn off does it?

v3ngence said:
Using an ancient GS2 with CM11 and get an issue where my bluetooth turns off and can't be turned on so I have to restart, but I think my bluetooth module is damaged, your phone bluetooth doesn't turn off does it?
Click to expand...
Click to collapse
No, I don't have that problem.

mzimmer88 said:
I haven't been able to get through one day without having to do a complete reset of my 360. It will disconnect from my phone about 3 or 4 times per day and the solution is some random combination of massaging the watch and Nexus 5 through restarting the phone/watch, connecting/disconnecting in the Android Wear app, or ultimately resetting the watch and going through the whole setup again. I am using a Nexus 5 with CM11 on it. Is anyone else having this issue?
Click to expand...
Click to collapse
I am having a few maybe 3 or 4 disconnects but the watch reconnects for me.

I get about 1-2 disconnects a day but it reconnects immediately afterwards.

Nexus 5 CM 11 user with the same problem, well, erm, had a problem...-ish.
I've made a couple posts on the is problem and created a Log of my first day here.
I made this post here telling an XDA member how to remedy their disconnects:
When you lose connection with your 360, if you open the Wear app on your phone, does it still say connected? If so, try and reconnect with Android Wear to your 360, does it not reconnect? (This is happening to me)
Try reconnecting on Wear, your 360 may say that you've lost connection (Cloud with a slash icon). Try reconnecting again from the Wear app, if that doesn't work, try repairing your 360, that should work. (4/5 times it works for me)
Resetting does seem to work as well, I did it yesterday and went 16 hours without a disconnect, previous day was 7 in 6 hours. But this morning I walked away from my 360 with my phone and lost connection and it started disconnecting again.
Click to expand...
Click to collapse
When I did a reset of my 360, it got my through the day without any disconnects the count not reconnect. But I think I had one or two minor ones where all I needed to do was wake my phone and it reconnected.
Now, the final solution? Yesterday CM11 M10 came out and if you have upgraded, I highly suggest making a backup and doing so. It seems to of fixed the issues on my N5. I made a post here preCM10 (Before it came out) and decided it was probably a BT problem with CM, not the 360 and I think I was right.
The BT fix apparently made it into CM11 M10 and I seem to be doing alright. But Battery life kind of sucks still, I only made it 7 hours yesterday with moderate usage, so I'm starting to suspect that I'm still getting some kind of disconnect, but it's reconnecting instead of hanging, thus decimating my battery life.
My Nexus is also seeing pretty bad battery life since I started using my 360. Granted, it's never been the best at making it through the day, but it definitely seems to drain about 20% faster.

what about stock Nexus 5?
B3RL1N said:
Nexus 5 CM 11 user with the same problem, well, erm, had a problem...-ish.
[...]
.
Click to expand...
Click to collapse
I use a N5 stock Android 4.4.4
Will I have the same problem or is it linked to the CM thing?
Thanks in advance and, by the way, great graphic analysis, dude!

Galaxy S4 here
CM11 had constant connection problems. Always showed "Connected, running sync loop" in the Wear notification.
I switched to a GPE ROM and haven't had one disconnect.

I experienced 5-6 disconnects a day, at least, before the update. Afterwards, it has disconnected once, but I was in a very crowded area, and it could have simply had a lot of electronic interference. Otherwise, the update has definitely made a difference. Wear Aware is actually useful now!

Moto 360 not updated on my watch

Hey everyone!
I'm at my end here as I just exhausted my last resort which was Motorola tech support. Wow what a mess that was.
Anyway I don't know if it's just me or if this is normal, but I've yet to get any of the latest Moto 360 updates. At present I'm on software version 4.4W.2 and yesterday I discovered another update was about to go out. Most of the apps I use on the watch - especially Watchmaker and Facer no longer work so until I can get this fixed I'm pretty much stuck with a stock watch.
I've tried resetting following various different methods on the internet that some claim forces an update, but nothing works. MY phone is running stock Android 5.0.1 and Moto Connect and Android Wear are both up to date.
Thanks in advance for any help you might be able to provide me!

This is my problem. At work it always pops up with the system update. Even with watch at 70% it won't do it. I go through the day and eventually go home. Recharge watch when I go to bed. Wake up in the middle of the night and try update. Apparently it hasn't been installing. Did this a couple nights in a row. Not sure if it's because I throw it back on the charger or what. Going to have to babysit it tonight.

Mine says there is no update. Stuck on 5.0.1. Tried different devices, resetting the watch but nothing works

Bluetooth skips a LOT after Lollipop update

Am I the only one having this problem? I'm so bummed out about how choppy and horrible my bluetooth is after I updated to Lollipop. Is there any fix for this aside from the workaround I've seen people do, keep the screen on?

FuzzRaven said:
Am I the only one having this problem? I'm so bummed out about how choppy and horrible my bluetooth is after I updated to Lollipop. Is there any fix for this aside from the workaround I've seen people do, keep the screen on?
Click to expand...
Click to collapse
Try a factory data reset from the settings menu. I know it's not the most desirable option but it seems to be the fix for other problems as well. It's a good idea to reset after a major update anyways.

Just streamed for an hour and no issues here. Reset your phone if you have issues.

My Bluetooth skipped a lot before the lollipop update. I will try out the Bluetooth in the car today and let you know what I'm experiencing.

dapimpinj said:
My Bluetooth skipped a lot before the lollipop update. I will try out the Bluetooth in the car today and let you know what I'm experiencing.
Click to expand...
Click to collapse
Yep I use bluetooth headset (Back Beat go 2) and it did that when my battery was low,on lolipop right after update it was happening for few minutes ,then it was ok.
I was using iPhone 5S before note4 and did not have this issue even once.
I wonder why that happens?

I just streamed for a couple hours. No skipping. I did a factory reset when I upgraded.
Do you have any devices near the phone? My work radio interferes with Bluetooth.
On a side note the phone auto connects to my Bluetooth adapter in my car.

If you trying to start a flame war, move along. It's mostly a software glitch and is easily fixable.

Verizon lollipop pdf mentioned that the OS would be updating/optimizing apps/their data for a few hours in background after the install.
Perhaps you should wait a few hours before the system has settled.
UPDATE:
Installed updates, no problems with BT music. No reset required.

After using it for several days, not just hours my bluetooth problem has resolved on its own! Thanks guys. Had me worried about it. No reset needed.

I am having the exact same problem, have tried all of the remedies to no avail. Never happened once when I was on Kitkat. It does it all the time now with Lollipop, I really hope they get this fixed.
Going to see if my wifes Note 4 on Lollipop does the same thing tonight and I'll report back.

A friend of mine just tried out Bluetooth from Note 4 to his car. It would cut out then when it came back it would speed up the same then go back to normal. Almost like it was trying to catch back up. He is on lollipop, Bluetooth works great for me on KK.

Mines doing the same.. no matter what bluetooth device or where I am, it'll "skip" every few minutes. Never did it before 5.0.1 update. Not sure where it started cause I used it factory stock for a couple months then did all the updates at once about a month ago. I haven't tried audio through the headphone jack, but I'm guessing that's fine since playing on the phone speaker is fine as well. I'll have to try the factory reset method and see if it fixes it.
Any other options or resolutions for this since it's been a few months since the last post?

stillthisguy said:
A friend of mine just tried out Bluetooth from Note 4 to his car. It would cut out then when it came back it would speed up the same then go back to normal. Almost like it was trying to catch back up. He is on lollipop, Bluetooth works great for me on KK.
Click to expand...
Click to collapse
This is the exact issue I'm having with my Note 4 using 5.1.1. No resolution yet

Notifications not showing

Hi all
I've recently started using my Moto 360 again alaong with my HTC M8 running the Radium 1.4 ROM. I set the watch up and all was working perfectly. I then noticed the watch was not receiving any notifications, this was after I had been out for a while with the watch at home. The only way I could figure out re-enabling them was to factory reset the watch then set it up again. I don't want to have to do this every time I go out without the watch etc. I had similar problems with the watch not pairing via Bluetooth with my phone after it had already been paired. The only way I could get it to pair was again to factory reset. This issue seems to have gone away now and it's just the notifications that seem to be a problem.
Any advice would be appreciated.
Thanks

Looks like ROM issue!
Sent from my SM-N9005 using Tapatalk

nijom said:
Looks like ROM issue!
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Happens with ever ROM I've tried

stevoh84 said:
Hi all
I've recently started using my Moto 360 again alaong with my HTC M8 running the Radium 1.4 ROM. I set the watch up and all was working perfectly. I then noticed the watch was not receiving any notifications, this was after I had been out for a while with the watch at home. The only way I could figure out re-enabling them was to factory reset the watch then set it up again. I don't want to have to do this every time I go out without the watch etc. I had similar problems with the watch not pairing via Bluetooth with my phone after it had already been paired. The only way I could get it to pair was again to factory reset. This issue seems to have gone away now and it's just the notifications that seem to be a problem.
Any advice would be appreciated.
Thanks
Click to expand...
Click to collapse
Hello,
It is actually an issue with the recent Android Wear app update...just read all the comments from 360 owners. Mine will not connect either.
Cheers

Well at least it was nothing to do with my phone/watch/ROM. Must have been updated recently as it's been fine! Back on form
Cheers
jschill31 said:
Hello,
It is actually an issue with the recent Android Wear app update...just read all the comments from 360 owners. Mine will not connect either.
Cheers
Click to expand...
Click to collapse

stevoh84 said:
Well at least it was nothing to do with my phone/watch/ROM. Must have been updated recently as it's been fine! Back on form
Cheers
Click to expand...
Click to collapse
After 4 Android Wear updates they finally fixed the connection issue. I sent them several bug reports and I swear they didn't even look at them.
Cherrs
Nexus 6

I'm still having problems where my Moto 360 won't show notifications (text, email, phone calls). I've tried every recommended solution. After a factory reset it works for maybe 30 minutes and then stops. One thing I've noticed (and I don't know if it's related or not) is that the Android Wear version on my Phone (Galaxy S5) is 1.3.0.2284253 and on my Moto 360 it's 1.3.0.2166028. Shouldn't they match?

Ramer said:
I'm still having problems where my Moto 360 won't show notifications (text, email, phone calls). I've tried every recommended solution. After a factory reset it works for maybe 30 minutes and then stops. One thing I've noticed (and I don't know if it's related or not) is that the Android Wear version on my Phone (Galaxy S5) is 1.3.0.2284253 and on my Moto 360 it's 1.3.0.2166028. Shouldn't they match?
Click to expand...
Click to collapse
For anyone who runs across this at some point, I solved the problem (at least for me). I unistalled Light Manager and now I'm getting all notifications.

Arrrgh mine has started doing this again! It had been fine for a few weeks. Seriously needs sorting out

I just got a new Moto 360 2 days back, and noticed this issue soon after it updated itself maybe to 5.1.1. I restart my phone everytime i face this issue which seems to fix it. Also android wear shows an error message mentioning notification sync is not working.

aayushjoshi said:
I just got a new Moto 360 2 days back, and noticed this issue soon after it updated itself maybe to 5.1.1. I restart my phone everytime i face this issue which seems to fix it. Also android wear shows an error message mentioning notification sync is not working.
Click to expand...
Click to collapse
Still isn't resolved for me sadly and restarting the phone doesn't work. I'm just flashing a new ROM to see if that helps. My watch has randomly been saying Google Play Services isn't installed on the phone when it is. Strange happenings here!

I have exactly the same problem! Saying Google play services are not installed, no whatsapp or text notifications until I get an email then they mysteriously appear. also if I toggle notification to priority and back they appear. doing my head in

You need to restart the phone and the watch, not just the phone.
Also can try removing your phone from your watch's bluetooth pair list then also "forget" the watch in your phone's bluetooth menu, then re-pair the two. Should work no problem after that.
I find this only happens if i stray away too far from either device or one of them gets restarted for some reason.. but yeah, restarting both the phone and the watch, removing the phone and watch from both bluetooth lists, and then re pairing, has fixed it every time for me. No having to factory reset the watch or reflash rom or anything drastic like that.
Now if you're phone is always in your pocket/purse which is on you all the time and the watch is on your wrist too and it just drops connection randomly... then i'd say something is messed up with your watch or phone.