i set it, set the max volume, then hours later when it goes off it pretty low, at about 60%....i go to check the volume and it is lowered in the alarm setting....any idea why is this happening? i almost overslept for work and am not happy about it :/
I keep getting this issue, I'm trying to eliminate what could be causing it but i think it may be when i mount the sd card to my pc. The reason i think this may be it is because when i unmounted it I lost all my facebook details for my contacts for about 10-15 mins
My earlier suspicions were correct it is the mounting of the as card that causes the errors I've described in my earlier post.
probably all pc connections, i use it for tethering, set the alarm after i was done and this morning all was ok....does HTC have a bug report site?
Related
Hey guys,
I have been running this version of DCD's ROM for a very long time now basically because it has worked well and been stable for me, but the other day I noticed an anoying thing happen that I wonder if anyone has seen and maybe solved. I use my unit as my primary alarm clock and have set 1 of the 3 alarms to 9:00PM to get me up for work, another for 9:00AM for a daily conferance call, and the 3rd for 10:00PM to be sure I do not sleep too late for work. From time to time I have changed times and text titles for the alarms and all worked well until the other day when I set it to go off at 2M just for 1 day to get remind me of a phone call I had to make, which it did nicely, but then when I changed that alarm back to it's old settings it assumed the identity and time I set for it, but now every day at 2:00PM that alarm still goes off and I can not make it stop doing that because the entry is no longer there. Also I told it to stop the 9:00PM work wakeup alarm and it still goes off at 9:00PM even if I set that entry totally different. I have even shut off all alarms and set the sound to another sound, but still they persist. I have looked in the registry and found the clock utility and where it stores the 3 alarms and they change like they are supposed t, and there is no listings for these rouge alarms anywhere in the entire registry. Anyone seen this ?????? Thanks. I will continue to tweak on it and let yoy know if I find or fix it.
Are you running Home Customizer? This happened to me about two months ago and I re-installed the HC and the mystery alarms went away.
Hey Forums,
I'm having a rather strange occurance on my phone. Every day, my media sounds seem to get disabled somehow, and I cant adjust the media volume. A reboot fixes it, but im wondering if there is something someone knows about any settings to get this resolved?
My device is rooted, but im not sure if it was occuring before I rooted. I'm hoping to avoid reflashing with odin and clearing the data on my phone, but if I have to then I have to.
I had a similar issue that when I set the ringer to vibrate only, the media volume was turned off and the volume controls didn't work.
I can't recall where I found it, but someone mentioned that some apps could be causing this. In my case, it was Tiny Tower. If I killed TT then the media volume started working again. Don't have any good idea why, but try killing apps until the media starts working again to see if that might be the cause.
uwflatlander said:
I had a similar issue that when I set the ringer to vibrate only, the media volume was turned off and the volume controls didn't work.
I can't recall where I found it, but someone mentioned that some apps could be causing this. In my case, it was Tiny Tower. If I killed TT then the media volume started working again. Don't have any good idea why, but try killing apps until the media starts working again to see if that might be the cause.
Click to expand...
Click to collapse
Thanks Uwflatlander,
Didnt think that was the issue. Seems to be HappyBay (probably more, but i force stopped HappyBay) and i could adjust my media volume again.
My alarm clock does not go off as it should in the morning. The alarm begins to go off, and within the first two seconds, it stops without any user input. The only way I can reproduce the behavior is by letting the phone sit without any user input for ~5 hours. If I set an alarm for 30 minutes from now, it works as expected.
I've done a complete restore of the phone, and the issue went away for a while but eventually came back after a few weeks. I didn't make any changes between the last day it was working and when it stopped working properly. This is kind of a major issue given that I use the alarm clock as my only alarm.
Notes:
1. I am using Beans ROM v6 and would post to that thread except I'm new to posting on XDA so unable to do so.
2. This issue occurred when the phone was 100% STOCK, so I know it is not related to the ROM.
3. Using a third party app is a workaround, not a solution. I want a break/fix resolution for using the stock alarm. Ideas?
Thanks in advance.
jdustinb said:
My alarm clock does not go off as it should in the morning. The alarm begins to go off, and within the first two seconds, it stops without any user input. The only way I can reproduce the behavior is by letting the phone sit without any user input for ~5 hours. If I set an alarm for 30 minutes from now, it works as expected.
I've done a complete restore of the phone, and the issue went away for a while but eventually came back after a few weeks. I didn't make any changes between the last day it was working and when it stopped working properly. This is kind of a major issue given that I use the alarm clock as my only alarm.
Notes:
1. I am using Beans ROM v6 and would post to that thread except I'm new to posting on XDA so unable to do so.
2. This issue occurred when the phone was 100% STOCK, so I know it is not related to the ROM.
3. Using a third party app is a workaround, not a solution. I want a break/fix resolution for using the stock alarm. Ideas?
Thanks in advance.
Click to expand...
Click to collapse
I am having the same issue. I am on 100% stock.
Bump, having same problem
does not sound like hardware, but it cannot be in your system as long as you didn't do a dirty flash, have you tried formatting your internal and external sd cards?
Morkai Almandragon said:
does not sound like hardware, but it cannot be in your system as long as you didn't do a dirty flash, have you tried formatting your internal and external sd cards?
Click to expand...
Click to collapse
I have restored back to stock by formatting both internal and external storage, and while this resolves the issue temporarily, the issue creeps back up after a period of time. I read somewhere that this may be a stock kernel issue, which makes sense given the first time I hit this issue was before ANY modifications were made to the phone.
I am having the same problem as well. Alarm stopped yesterday right after the first couple of tones. Then my wife's Galaxy S3 did the same thing today. Both phones are completely stock.
I am just setting multiple alarms now.. I know not the greatest solution but decent temp
Hi there,
First post and I'm not overly tech savvy so I hope I get this right. I recently bought a Oukitel U2 running Android 5.1. There are several issues I am trying to figure out but the main one made me sleep in this morning so it's my priority.
The phone is rooted and the bootloader unlocked. I'm not exactly sure when the problem started or if it's been there from the start as I don't reboot the phone that often. However, it has come to my attention that if the phone is in vibrate or silent mode and I turn up the alarm volume it works just fine. On rebooting the phone though the alarm is muted. This doesn't occur when using other audio profiles. But occurs consistently on a reboot.
I have tried resetting all the audio profiles, starting in safe mode, and restarting from safe more, and using a different alarm clock app. But always the same result.
Maybe this is what is supposed to happen, but if after a reboot the alarm is muted and I switch to the general audio profile the alarm volume is restored. If I then switch back to the vibrate profile without rebooting it does not mute the alarm.
But I've spent hours reading about all the priority settings etc and nothing seems to work.
Has anyone got any thoughts?
Thanks
I have a Pixel 3 with the latest Android 10 update. When I set an alarm to 8:15 am, it goes off at 8:00 am. When I set it to 9:30 am, it goes off at 9:15 am.
This started happening recently and I have no idea what's causing it. The device is not rooted and has no customizations. It is is extremely annoying, not to mention it keeps robbing me off morning sleep time, and I'd like to fix it. Please don't suggest working around the issue by setting my alarm 15 minutes late, because if the bug disappears on its own, then I will be 15 minutes late, so I'd rather figure this out.
Nexusoid said:
I have a Pixel 3 with the latest Android 10 update. When I set an alarm to 8:15 am, it goes off at 8:00 am. When I set it to 9:30 am, it goes off at 9:15 am.
This started happening recently and I have no idea what's causing it. The device is not rooted and has no customizations. It is is extremely annoying, not to mention it keeps robbing me off morning sleep time, and I'd like to fix it. Please don't suggest working around the issue by setting my alarm 15 minutes late, because if the bug disappears on its own, then I will be 15 minutes late, so I'd rather figure this out.
Click to expand...
Click to collapse
It seems to just be a bug within the app. Backup your current data (skipping the alarm data and settings) and try a factory data reset then restore said data
0
I don't know if it's related to the issue, but the screen also turns luminescent red when the morning alarm goes off. That didn't use to happen. I could have sworn I turn that option on in the settings but can't find that setting anymore.
Edit: I just remembered that setting was in the Bedtime tab, but this is not a Bedtime schedule alarm. This is a regular alarm that repeats 7 days a week, and Bedtime is turned off. Strange that the screen still goes red. For Bedtime alarms, it's supposed to start changing colors 15 minutes before the alarm, but the actual alarm is not supposed to sound off until the designated time.
My solution to this problem was to go back to the old version of the Clock app by uninstalling all updates via the Play store. I don't have the "Bedtime" tab or any other new features anymore, which is not ideal but much better than losing 15 minutes of sleep every morning.