Develop Bugs

[Q] ICS alarm clock not responding

Two days in a row my alarm on my VZW GNex has not woken me up for work. When I look at my phone it says "Clock has stopped Responding."
This is kind of a big deal and rather a large annoyance, because well lets face it, I cannot be late for work everyday, and I use my phone for my alarm.
My trusty old DInc never had a problem setting off the alarm.
Any ideas or thoughts? Anyone else have this problem on their Verizon Galaxy Nexus? Oh and also, my GNex is unlocked and rooted, but on the stock Rom. I want to wait for CM9 to put a Rom on this phone.

No one has any ideas? my alarm worked this morning. but i feel like this would be a random occurrence, and i want to figure out how to make it never happen again.

hell my alarm isn't going off at all figure that one out and i have 3 of them set and yes they are enabled it shows me the next alarm time and is correct

Try going to settings > apps > clock and clearing data/cache.. all I can think of
Or you both might try an alarm app from the market if that doesn't work
Sent from my Galaxy Nexus using xda premium

Got the same problem.
When I enter to Clock application, switch do Alarm tab and tried to set any alarm, application hung up with ANR message.
Also I figured out, when I entered Settings -> Sounds -> Volumes, it's freezes same way.
Clearing data & cache for Clock application only not fixed problem, I managed, it's Media storage problem (both apps - Clock and Sounds - requires access to media storage to choose ringtone ?) - so I cleared it's data too.
Rebooted phone and voi'la. Clock are now working again. (But all alarms are gone, but that's no tragedy)
Hope this helps

Phones freezes for 2 second then reboots, once a day, immediately after waking up

I've had this problem sometime over a month now, can't remember if I did anything to make it like this. I made a post somewhere about it happening the 17th of May, so it started somewhere before that.
My phone will freeze for 2 seconds and then reboot itself.
It started while I was on stock 4.0.2 and now I'm on stock 4.0.4 IMM761. I have a GSM Galaxy Nexus.
It only happens just after the phone has been woken up and something is started. The most common (as it's my go-to-way of forcing it, to see if it's still there) is after waking up the phone, sliding down the notification bar and pressing "settings", which doesn't open but the phone freezes and reboots itself. I first discovered this when I wanted to go in there to change screen brightness. It's also happened when I went into the notification bar and pressed a battery app there. It doesn't matter if I'm doing it in the lock screen or after the lock screen.
It's also happened when I wake up the phone and enter the camera through the lock screen.
It also regularly happen if I set an alarm in the morning. When my alarm is suppose to play it freezes and reboots, and when it's rebooted, the alarm has been cancelled without ever playing.
It doesn't need to wake from deep sleep to do this, I've had it happen mere minutes after trying to see if it's there.
I don't know if it has something to do with this, but the 21st of April I tried to do the "clear google services framework" trick to force 4.0.4 ( I was on yakjuxw), but it did not work and I remember my phone acting janky and I was scared it messed something up, but I seem to remember it getting better. I can't remember what exactly it did though.
I've read that 4.0.4 would fix the reboots that a lot of people were having (don't know if it was the exact same kind of reboots as mine) so I did this to make my phone a yakju (translated from Danish):
http://translate.google.dk/translat...at-modtage-opdateringer-til-din-galaxy-nexus/
I did that the 8th of June, and it worked flawlessly and I was on 4.0.4 IMM761 in no time. Unfortunately it did nothing to stop these reboots.
As part of the process of making my phone a yakju I, of course, did a complete factory reset, although I did make a copy of my entire SD and transferred everything over again after the process.
These past two weeks I've tried the following to fix it:
Clear cache partition in recovery.
Clear google services framework.
Clear media storage.
Tried to uninstall many apps, 2-3 a day, to see if they were causing it, re-installing them when I still had the same problem. If it's an app causing this I've yet to find it, but I find it weird that an app could be causing this.
It happens once a day, but never close to each other. It seems that some time has to pass before it can happen, and it only ever happens just after the phone is woken up, either by my alarm or by me opening the notification bar and pressing something there.
Please help me, this is unbearable.

Another thing, yesterday I tried to let it run without me pulling down the notification bar and pressing "settings", which would set off the freeze-reboot. I found that my phone would not freeze-reboot but very often it would "reload" app icons and widgets when I went around my homescreens. Where I can only see my wallpaper for half a second and then the icons/widgets appear. It would do this very often throughout my 1day 5hour uptime, and a couple of times I would try to force the reboot (by pressing "settings" in the notification bar), after the icons/widgets did the invisible/load thing and it didn't reboot. This must have something to do with it?

hi,
experienced this on my nexus s back then what i did is from recovery>mount and storages>formatted system, boot, and everything else except sd card.then it was all gone.btw you will have to flash your rom and kernel again as this is a full wipe.hope i helped and do this on your own risk
daff

bump

did it cure your reboots?
daff

dark06 said:
did it cure your reboots?
daff
Click to expand...
Click to collapse
I haven't tried that yet. I'm trying a "RAM booster" app to see if that helps, but that doesn't sound too stable even if it does.
I'm going to do a full factory reset and installing nothing, or moving anything to the SD, and just let it run like that to see if it works.

Just writing an update for anyone googling themselves here with the same problem, I had it resolved.
I found out that if I didn't force the reboot (by turning on the phone and quickly pulling down the tray and pressing something there) it could last a long time with just the launcher resetting, but it would lead to complete freezes (anywhere I was on the phone) and would require a battery-pull.
My plan was to wait for jelly-bean before doing another factory reset, I got the JB update and it completely removed the problem. I still don't know why the problem suddenly started or what caused it, all I know is that the JB update fixed it, and the update is fantastic, my phone's never been better.

[Q] Apps crashing since Kit Kat OTA update

I checked for OTA update on 2/6, 8:47pm and 4.4.2 was found and 'successfully' installed: HTC6500LVW_3.11.605.1_R2-2.10.605.1
Ever since, apps have been crashing on the phone like crazy. "Unfortunately, ____ has stopped." The apps that crash most often are Maps (about 5-10 sec after opening each time), Sense 5.5 and Gmail, but others that I don't use as often have done the same. The phone also now reboots itself frequently (5+ times a day).
Two other issues I've noted are (1) when returning to home screen after closing an App, it sometimes takes around 10 sec for icons to appear (possibly Sense restarting?), and (2) when I wake the phone up, the screen turns on and then I try to swipe down from the top to check notifications and the screen goes blank.
Has anyone else seen this type of instability with HTC One and KitKat? Any suggestions?
I've tried searching for a new update hoping they've fixed some of these bugs, but it tells me I'm up to date.

Have you tried clearing the cache and data for the apps that are crashing? There are no bugs like that in kk. It sounds like some data just got corrupted during the update. If wipimg the individual apps data dosent work you may have to do a factory reset or an ruu.

cmlusco said:
Have you tried clearing the cache and data for the apps that are crashing? There are no bugs like that in kk. It sounds like some data just got corrupted during the update. If wipimg the individual apps data dosent work you may have to do a factory reset or an ruu.
Click to expand...
Click to collapse
I'll try clearing the caches. Should I clear it for Sense though? I figured out the screen going blank when I go to swipe it, it seems to be a proximity sensor sensitivity issue. If I approach with my finger from the right (opposite the sensor), there's no issue. So it's just the sensor now picking up my finger passing over to swipe and thinking it's me putting my phone up to my face maybe?

Yeah you can clear it for sense too, but if you clear data it will wile out all the apps settings. For sense that means all the settings in the settings menu. But i dont really see what else you could do, other than a factory reset, or ruu, which will wipe everything.

[Q] Settings menu all fubard

As my title states, no idea what happened to my settings menu.
I'm "stock" rooted. (Did it back in December with odin flash - 4.3)
Firewalled, Greenified, and TitaniumBackup to Freeze useless apps.
Everything has been great, then all of a sudden I was getting 3 errrors.
Google Text to Speech, Maps and Settings all quit working. (The whole, unfortunately *blank* has stopped working)
I removed Text to Speech, but Settings still crashes and refuses to work and now Maps took it's place (T2S).
Removed Maps and still Settings does not work and will randomly crash in the background.
I have done nothing new from what I described I have already done above.
Nothing was newly frozen. I have never uninstall any stock apps, just freeze them.
Last thing I uninstalled was a GoSMS theme I no longer use. Uninstalled it through ROM Toolbox Pro as I saw it was running in the background.
Everything else appears to be working fine. Camera, Chrome, Texting, Calling and my various daily apps.
Just something with the settings "app" has gone all wrong.
It also appears it's not the entire settings. Like if I go to about phone, it's all good. If I go to display part of the settings, *crash*
Two other odd issues pertaining to this as well:
My assistive light widget no longer works. So I know this happened within a 24 hour period as I use that light nearly every day.
And when you get into the settings part of the phone, all the text / font is screwed up. (Pic attached to see what I'm talking about)
Assistive light widget shows the same messed up text as well.

Data corruption. It will spread. The easiest and most successful solution is to wipe data, system, cache, and Dalvik cache, then re-flash the stock firmware, then re-root.
If you don't want it that successful you can do the wipes and restore a backup, but there is always a chance that there was corruption saved in the last backup and in a few days it will be as it is now.
What caused the corruption? It could be anything from a bad USB cable to a nearby flash of lightening, but more likely it's whatever you do that you need root for.
Frank

I would believe that was the issue if it was more wide spread.
Or I was having stability issues in daily usage.
The phone only gets charged via usb, I have not hooked it up to a computer for some time.
No storms or surges recently either.
As far as root usings, nothing has changed or updated recently. And none of what I do hard changes anything.

Reflash. Much faster and easier than wracking your brain trying to track down what exactly little thing went wrong.

Um...okay

So yeah, rooted my M8 switched to ART and it's running beautifully. Then I wanted to change my sounds since it reset to default. Nope. Can't even bring up the sound selection screen, for messages going into settings and choosing the sound option it tells me that messages has stopped working. Awesome. I thought maybe it was ART, switched back to Dalvik, same issue. So I'm thinking it's an issue with root. Anyone else had this issue or know how to fix it?

Unrooted, issue persisted, between ART and Dalvik, I'm going to try a factory restore.

Yeah.....so you know how you sometimes do stupid things? Turns out I disabled the sound picker app. Yep...