i use alarm clock extreme and for whatever reason the alarm did not go off. it went off later then when i woke up on my own and starting poking with my phone.
i suspected doze, but its not supposed to doze when plugged in so.....???
anyone else have these issues?
i did not have this problem on my 6 with M.
k.electron said:
i use alarm clock extreme and for whatever reason the alarm did not go off. it went off later then when i woke up on my own and starting poking with my phone.
i suspected doze, but its not supposed to doze when plugged in so.....???
anyone else have these issues?
i did not have this problem on my 6 with M.
Click to expand...
Click to collapse
I use Alarm Clock Xtreme and I'm not having any issues.
no issue with 3p alarm. I use alarm clock plus.
Yes, I am having a similar problem on my Nexus 6P with Alarm Clock Extreme Free. This app worked fine on my Nexus 7 2013.
Omg.. Yes same problem here. I got my nexus this pass Monday and was late for twice because my alarm didn't go off until I picked up the phone or woke it up...
Alarm clock extreme paid app..
Same kind of problem here. Ended up creating an alarm in the stock clock app. After that, both alarms went off. I've left it like this cause I already was late for work 3 days last week.
Sent from my Nexus 6P using Tapatalk
Seems like an app issue. Have you guys reached out to the developer?
badboy47 said:
Seems like an app issue. Have you guys reached out to the developer?
Click to expand...
Click to collapse
i have sent them a bug, got the canned response.
this is a real annoyance because i need a math problem to wake up.
k.electron said:
...this is a real annoyance because i need a math problem to wake up.
Click to expand...
Click to collapse
I hear ya! However, I've switched back to the alarm in the stock Android Clock app, which works fine, and I'm now using an old-school clock radio as a backup. This double-pronged strategy seems to work fine for me for the time being, until the developers of Alarm Clock Xtreme address the problem with using their app on the Nexus 6P.
Related
And more specifically and as far as I can tell, if the phone is freshly booted then the functions listed above work. However, after several hours on I go to adjust the brightness and the screen does NOT change its brightness no matter whether i set auto-brightness or adjust it manually.
Let me preface this topic and let you all know that I still have my stock screen protectors attached and I've installed the light flow app if that matters.
Any ideas?
EDIT: I such at naming titles.
same here, just wiped. no clue what's causing it
Same for me I just noticed this. Hope its something fixable in an update.
Sent from my Nexus 4 using xda app-developers app
i don't have this problem, auto brightness and slider always work
Auto brightness doesn't work
I am having this problem too... Works for the first while, then doesnt work at all...
*** Ive commented on a logged issue with google, ISSUE 40378
https://code.google.com/p/android/i....2&colspec=ID Type Status Owner Summary Stars
I uninstalled ledblinker and it seems to solve the problem. Do you guys use lightflow? That might be the culprit
ceejay83 said:
I uninstalled ledblinker and it seems to solve the problem. Do you guys use lightflow? That might be the culprit
Click to expand...
Click to collapse
It doesn't make a difference if I use lightflow or not it just won't act right.
Sent from my Nexus 4 using xda app-developers app
Jefferyrbrown1983 said:
It doesn't make a difference if I use lightflow or not it just won't act right.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Have you tried wiping? I haven't had any issue since
Ugh never mind, brightness got stuck again.
Wow am i glad to have found this thread, i have been battling this problem since day one with this phone, and i have been trying to track it down with usb debugging but have been unsuccessful. What happens is that my screen will randomly shut off and be non responsive for 5 seconds and when i can turn the screen back on, i can no longer adjust the brightness and only a reboot will solve the issue. It also occurs when i am not using the phone so i think it is a hardware issue but i am uncertain.
Things i have tried to fix it:
Factory reset
Fastboot flash factory image
Flash cutom ROM & Kernel
Didn't realize it before but yes, my screen randomly turns off, then the brightness gets stuck. Thought it was timing out
---------- Post added at 03:52 PM ---------- Previous post was at 03:46 PM ----------
You guys use auto brightness? Maybe that might be it
This happens to me occasionally too, haven't been able to determine what triggers it. It's almost as much fun as the magical battery levels. Plugged in the other day, went from 4% to 100% in a nano second.
interesting...my auto and slider work just fine
ugh still getting this problem daily. does't matter if auto brightness is on
There is no solid way to reproduce the problem, so I am willing to bet its a hardware issue. I will be calling T-Mobile this week to replace it.
Sent from my Nexus S
Of the people who are experiencing it, how many have a notification drawer widget (Widgetsoid, Power Controls, et al?) and have a brightness toggle on it?
I've removed brightness from Widgetsoid to see if it's a conflict of some sort.
CMNein said:
Of the people who are experiencing it, how many have a notification drawer widget (Widgetsoid, Power Controls, et al?) and have a brightness toggle on it?
I've removed brightness from Widgetsoid to see if it's a conflict of some sort.
Click to expand...
Click to collapse
Yes I'm using power controls. Still does it even if I disable the brightness toggle
Hmmm...wonder if there's a submission on Gerrit, shall troll later.
Sent from my Nexus 4 using Tapatalk 2
CMNein said:
Hmmm...wonder if there's a submission on Gerrit, shall troll later.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Might be a hardware issue? If it was software I think a lot of people would be complaining about this.
Edit: ugh as I was typing this post, screen flashed and turned off with broken brightness. I just rebooted like 5 min ago too
ceejay83 said:
Might be a hardware issue? If it was software I think a lot of people would be complaining about this
Click to expand...
Click to collapse
Not sure. Here's one report on Google Code: http://code.google.com/p/android/issues/detail?id=40378
Edit: could just as easily be a OS issue, if it decides to stop polling the light sensor for some reason. Many people have the battery bug as well, which seems to stop polling the battery for some reason.
Hi all,
I started getting this issue recently- I'd say "Set alarm for 12 minutes" but instead of doing that my Nexus 7 would set alarm for 12 o'clock.
It worked perfectly well before, I haven't installed any updates or done any other fancy stuff either (lately).
I tried setting the language to United States (I am in UK), nothing changed.
Any idea how can I resolve this?
Thank you.
It hasn't worked for a while. I think maybe since 4.2.2? Can't recall. But there's nothing we can do to my knowledge.
The only way to work around it would be to just set an alarm instead of a timer.
Hopefully Google fix this in the next update.
Alarm clock extreme works fine.
Sent from my cell phone telephone....
MasterJ87 said:
It hasn't worked for a while. I think maybe since 4.2.2? Can't recall. But there's nothing we can do to my knowledge.
The only way to work around it would be to just set an alarm instead of a timer.
Hopefully Google fix this in the next update.
Click to expand...
Click to collapse
Aha, mystery solved. Thanks a lot MasterJ87.
I guess I will be reverting to a previous version of Android then.
As for Alarm clock extreme- I downloaded it but could not find a voice command capability.
Thanks a lot and have a good week.
Hey guys, my alarm on my n4 doesn't work (sometimes) and wonder if you guys can help me. I was late to school for this reason and has been happening for a while now ever since PSX rom Days. The bug is still present in the purity rom and my kernel is Trinity TF11 with deprima. But it's been happening ever since I switched to KK from JB. Yes the come volume for alarm is on the max as well as the alarm set on all week days. No I didn't sleep over the alarm as it didn't show in the notification bar that it didn't alarm. Hope someone can help me. Thanks.
Detailed said:
Hey guys, my alarm on my n4 doesn't work (sometimes) and wonder if you guys can help me. I was late to school for this reason and has been happening for a while now ever since PSX rom Days. The bug is still present in the purity rom and my kernel is Trinity TF11 with deprima. But it's been happening ever since I switched to KK from JB. Yes the come volume for alarm is on the max as well as the alarm set on all week days. No I didn't sleep over the alarm as it didn't show in the notification bar that it didn't alarm. Hope someone can help me. Thanks.
Click to expand...
Click to collapse
Might not solve the problem as far as the internal issue with the alarm clock, but give Timely a try.
https://play.google.com/store/apps/details?id=ch.bitspin.timely
Sent from my Nexus 7 (2013)
Berrydroidcafe said:
Might not solve the problem as far as the internal issue with the alarm clock, but give Timely a try.
https://play.google.com/store/apps/details?id=ch.bitspin.timely
Sent from my Nexus 7 (2013)
Click to expand...
Click to collapse
Well I guess that's an alternative, but do you know what the problem is? Or what causes it?
Hi all,
About two months ago I had a problems with my notifications, they suddenly stopped vibrating when one came through, this applied to both the loud and vibrate profiles, although phone calls vibrated it was just the notifications.... roll on a month later and it started happening again!
I totally forgot the settings I changed to fix the issue previously so over the last week or so I've been checking what could be the cause, I then found the culprit, for some reason the vibration intensity for notifications was set to zero, why this was set I don't know.
I've tried to replicate this problem by changing the sound profiles to see if the vibration intensity will go back to zero and it hasn't, I've manually enabled D.N.D that doesn't change it, therefore I'm puzzled what has caused this to change by itself, any ideas?
Very same issue dude, S7. Did you find a fix ?
martinburke said:
Very same issue dude, S7. Did you find a fix ?
Click to expand...
Click to collapse
I never did; it's happened several times since, normally about a month apart, at least I know how to fix it now. I'm running the nougat beta atm so will be interesting to see if it happens in this.
Sent from my SM-G935F using Tapatalk
Thanks for the reply. Appreciate it.
martinburke said:
Thanks for the reply. Appreciate it.
Click to expand...
Click to collapse
No problem!
Sent from my SM-G935F using Tapatalk
Do you know if this still happens on 7.0 or any other strange bugs showing up ?
martinburke said:
Do you know if this still happens on 7.0 or any other strange bugs showing up ?
Click to expand...
Click to collapse
I've been on Nougat for about 3 months and not had that bug at all ?
Sent from my SM-G935F using Tapatalk
That's good. I'm still holding off on 7.0 marshmallow is running smooth for me and can't find a good enough reason for update. They should have included the Google assistant.
I just got a new S7 edge 935f. I rooted it with magisk after installing twrp. I have tried a few Nougat stock roms and in all of them, my alarm clock fails to go off first thing in the morning. It will come on when I push the home button and for the rest of the day all alarms work fine. It is only the first morning alarm that fails.
I wonder if this is due to something wrong with the kernel, and if installing a custom kernel may fix this. Or is the a lib file that may be corrupt.
Anyone else experience this kind of problem? I read in a few articles and forums that it is linked possibly to a SOD (sleep of death) bug. Hoping some information can come from anyone else who knows of this.
Thanks in advance.
So a custom rom and kernel failed to fix this. In the kernel settings with mtweaks I even allowed all wake locks. Mos puzzling and even slightly frustrating...
bobfrantic said:
So a custom rom and kernel failed to fix this. In the kernel settings with mtweaks I even allowed all wake locks. Mos puzzling and even slightly frustrating...
Click to expand...
Click to collapse
Hey have you tried using a third party alarm clock so you can test if it's an isolated case or with all of them ?
jaimep01 said:
Hey have you tried using a third party alarm clock so you can test if it's an isolated case or with all of them ?
Click to expand...
Click to collapse
yes I have and all have same issue. For the first alarm I have to manually wake up the phone, all others work through the day.
Surely I am not the only one to have this trouble....
bobfrantic said:
Surely I am not the only one to have this trouble....
Click to expand...
Click to collapse
Check the battery saver app in maintanance it miht have picked up the clock app which I soubt but it is a good idea to check it.
jaimep01 said:
Check the battery saver app in maintanance it miht have picked up the clock app which I soubt but it is a good idea to check it.
Click to expand...
Click to collapse
Yes, I checked all those things... I wonder about MM 6.0.1 if the issue would remain or not. I found an app "SOD Killer" that I will test. It results in some battery being used to keep it from going into deep sleep. Have googled this and there are a lot of others with the situation but not a lot of fixes around.
bobfrantic said:
Yes, I checked all those things... I wonder about MM 6.0.1 if the issue would remain or not. I found an app "SOD Killer" that I will test. It results in some battery being used to keep it from going into deep sleep. Have googled this and there are a lot of others with the situation but not a lot of fixes around.
Click to expand...
Click to collapse
I feel my alarms fail as well from time to time, but i think the culprit is, in advance features the easy mute function have you tried turning it off ?
It might have a bug or something with the sensor.
jaimep01 said:
I feel my alarms fail as well from time to time, but i think the culprit is, in advance features the easy mute function have you tried turning it off ?
It might have a bug or something with the sensor.
Click to expand...
Click to collapse
No I haven't tried that. I have mine working now. It woke me up this morning. What did it is the app "SOD Killer" which is on google play. It increases battery useage a little but until I find out which file is keeping phone asleep, it's a small price imho.
do not "freeze" or "doze" or use any similar apps to "kill" clock app in background.
which means, clock app needs to run to have alarm working.
yaibakt said:
do not "freeze" or "doze" or use any similar apps to "kill" clock app in background.
which means, clock app needs to run to have alarm working.
Click to expand...
Click to collapse
I don't kill or freeze anything. Only thing I have to make alarm work is the SOD Killer app that keeps phone from going into deep sleep.
So a funny thing happened on the way back to Marshmallow 6.0.1 as I had just finished getting through setup and was about to start doing things on my phone, I got a notification that there was a firmware update downloading. It was taking me back to 7.0 and it upgraded my phone to the first version of Nougat for Luxembourg. Then a few minutes later another system update was downloading and I installed it and my phone now had the latest Nougat for Luxembourg. So first thing I checked was the alarm. I set one for 4 hours later, and it worked. I also tested an overnight alarm and it also worked. So now I have working alarms. Still going to downgrade back to 6.0.1 though, just feels better than Nougat to me.