twice now yesterday and this morning i didn't hear my phone got to bed late, so i didn't hear it so i wake up after it had ring like half an hour or and hour or more, and than i can't access the app, i kill the service and go in again it normally the alarm starts kicking off, and like 10mins after my phone automatically reboots on it's own.
is there a way to fix this problem?
Related
This all started yesterday morning. I had my alarm set, woke up later than I needed to with a notification on the phone that said Alarm Turned Off After 10 Minutes, telling me the alarm had gone off for 10 minutes and was automatically turned off.
I thought it was weird so I did some digging and it turned out that NONE of my sounds were working. The volume was up, silent mode was off, but I was getting nothing whatsoever from the phone speaker. Even speaker phone wasn't working. Headphones worked fine. It seemed my speaker had blown.
Well, later in the day (as I was preparing to take it back to Verizon) it just randomly starts working again. All sounds now seem fine.
So I set my alarm this morning. And this time, it didn't even go off, at all! I woke up 5 minutes after it was supposed to go off, and when I unlocked my phone, THEN the alarm started going off. It's almost like it isn't coming our of deep sleep to sound the alarm.
Are these two issues related; the sound issue yesterday and the alarm issues both days? Has anyone else experienced this? It seems to be random...sometimes I can replicate it, other times I cannot.
There's another thread about this somewhere...try a search for "alarm". It's happened to me often enough that I can't rely on my Gnex as an alarm clock...I have to use my old SGS instead. I've also had loss of sound occasionally, but a reboot always fixes it.
Wish someone would figure out a solution, it's pretty annoying to have a bug like this in the alarm. Even the cheapest, crappiest dumbphone you can buy comes with a reliable alarm app, but my expensive smartphone does not? (and yes, I've tried other alarm apps besides the stock one...they all fail to go off intermittently.)
Sent from my Galaxy Nexus using XDA
Thanks for the input. I use my alarm daily and this is the first time I've had this issue.
As an aside (but perhaps related issue?), my gmail app has uninstalled itself and I can't get it reinstalled. Looks like it's time for a reflash.
cmcfalls said:
Thanks for the input. I use my alarm daily and this is the first time I've had this issue.
As an aside (but perhaps related issue?), my gmail app has uninstalled itself and I can't get it reinstalled. Looks like it's time for a reflash.
Click to expand...
Click to collapse
Yes I would reflash before you miss a flight or the interview to your dream job!
One thing I miss about my old blackberry is the alarm. Put it in the cradle and the time would dim, all notifications would turn off and the alarm would fire every time, every when the battery had been drained and switched off. Pity everything else sucked...
I've yet to have a problem.
Maybe you're getting SOD's (or close-to) in the middle of the night and the phone is having trouble waking itself up?
Try adjusting your governor and turn your undervolts up if they're enabled.
I am, however, fairly OCD about my alarms...
I reboot my phone before opening the alarm app and ONLY the alarm app...
Make sure the alarm is enabled...
And turn the screen off.
I've done this since my OGDroid days.
I also have the trusty DX as a backup...set 10 minutes later; just in case.
Hello,
My problem with the alarm is that when I set it on, it doesn't always go off.
If the phone is standing in the dock everything works fine.
If it just lies on the table it sometimes goes off and sometimes not. After I wake up late for my studies and unlock the screen I see some random hour in the middle of the night which quickly refreshes to current time. My guess is that the phone clock freezes due to some problem.
I don't have any task killers. I'm currently running Xperia NXT 1.1 rom.
As I said it is random. Sometimes it can properly go off. If the phone is charging it always works fine. Any help would be appreciated
Hi all,
My Nexus has been doing something a bit weird the past few days... The display is set to go to sleep after 30 seconds of inactivity (and yes, I've triple checked it) though recently it has just been staying on the whole time until I press the power button. I tried a few things, like switching the inactivity time to 15 seconds, or trying it whether plugged in or not, but it still stays on. It's a bit annoying because I'm concerned for privacy if I leave it on my desk (in a college dorm room) while I'm out for a few minutes and it doesn't go to sleep, or for battery if I put it in my pocket and never turns off. Anybody have similar problems or solutions?
Thanks
To me, it sounds like an app is misbehaving, and thus keeping your phone awake... have you tried removing all of your apps except the essentials (gapps) and see if this problem still persists?
Yes so I just turned it off and back on; working better now thanks!
All, i'm having a huge problem. beginning last weekend, whenever I wake up I find my phone clock has become nearly 5 minutes slower.
Because of my sleep schedule on the weekdays, its always 5 minutes late by the time i wake up. strange thing is, within 10-15 min of my phone being "awake" I assume the auto clock sync corrects the wrong time and by the time i'm i'm driving to work the clock's time is right.
i tried turning off wifi one night i think a couple days ago to see if it was some type of strange wifi issue and i found that with wifi turned off, my phone was almost 20 minutes off on the time.
This has affected strangely my alarm clock as well and sometimes it doesn't even go off and i naturally wake up and check and it shows the screen where the alarm clock is running, asking me to "dismiss" or "snooze"
This is super cumbersome, is ANYONE else having this issue with the hox? my only conclusion is while i am sleeping and my phone is on standby for many hours something isn't quite doing its job. maybe something like the phone time being off, i don't know, like 30 seconds an hour or something. I'm still on 1.73.
during the day while my phone is turned on every 30 min to an hour, my clock is perfectly sync'ed.
please help.
turn off auto updating and manually set it - does it still happen?
it could be a conflict between phone time and network time, and the phone stops checking when asleep?
phil112345 said:
turn off auto updating and manually set it - does it still happen?
it could be a conflict between phone time and network time, and the phone stops checking when asleep?
Click to expand...
Click to collapse
that's a good test to try. will do that tonight, turning off network sync and leaving it on manual. will report back tomorrow AM
chillsen said:
All, i'm having a huge problem. beginning last weekend, whenever I wake up I find my phone clock has become nearly 5 minutes slower.
Because of my sleep schedule on the weekdays, its always 5 minutes late by the time i wake up. strange thing is, within 10-15 min of my phone being "awake" I assume the auto clock sync corrects the wrong time and by the time i'm i'm driving to work the clock's time is right.
i tried turning off wifi one night i think a couple days ago to see if it was some type of strange wifi issue and i found that with wifi turned off, my phone was almost 20 minutes off on the time.
This has affected strangely my alarm clock as well and sometimes it doesn't even go off and i naturally wake up and check and it shows the screen where the alarm clock is running, asking me to "dismiss" or "snooze"
This is super cumbersome, is ANYONE else having this issue with the hox? my only conclusion is while i am sleeping and my phone is on standby for many hours something isn't quite doing its job. maybe something like the phone time being off, i don't know, like 30 seconds an hour or something. I'm still on 1.73.
during the day while my phone is turned on every 30 min to an hour, my clock is perfectly sync'ed.
please help.
Click to expand...
Click to collapse
Are you using a custom kernel? Some kernels can have time slew issues. Most people don't notice it. I use Clocksync from the market to keep synced.
Sent from my HTC One X using Tapatalk 2
Evil-Dragon said:
Are you using a custom kernel? Some kernels can have time slew issues. Most people don't notice it. I use Clocksync from the market to keep synced.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
i've only rooted it for titanium back up. kernel is factory. i am definitely going to look into clocksync as well after tonight's test. thank you.
i can confirm after i turned off network clock sync that it indeed was not the problem and that there is something inherent in the software that is slowing down my clock on my phone overnight. thing is i don't have any crazy apps. this is so strange.
anyways i have downloaded ClockSync and seeing if this will fix the problem. thanks
Hello, I have a problem with my G3. My battery life in general is quite normal, but once I am under 50% of battery, the phone tends to restart itself or turn off completely randomly. Not quite randomly, it always happens when something battery-consumptive happens. For example, when I am recieving a call, taking photos, or using apps like Google Snapseed, etc.
If I am under 50% or so, it happens sometimes. The phone starts ringing and sometimes I don't pick up the phone in time and it just restarts (automatically shows LG logo, etc.). Even more frustrating is that the missed call is not in the call history, so if I do not have a clear view of the phone screen I do not know at all who was calling.
If I am under 30% the phone is technically unusable. I can browse web, facebook or text via messenger without any problem, but I can't recieve a single call. The phone starts ringing, and in two seconds it restarts. The same happens with camera, once I am under 30, the phone restarts always, when I take a photo.
Sometimes the phone turns off completely, and the only way to turn it back on is to 1) take out the battery or 2) plug in to a charger.
I was assuming this was a battery fault, so I bought a brand new one (original LG G3 battery), but the problem persist.
Do you have any tips on how to fix this? Thank you very much