Just in case someone else runs into this issue.
My alarm (default app) would get snoozed immideately after going off, thus becoming useless.
I have discovered that if I disable the "OK Google" detection from any screen option, the alarm functions fine.
Hope it helps someone not to miss any important appointments.
The ok google from any screen feature also kills the video camera. You get a "can not record while on a call" warning.
GRRemlin said:
Just in case someone else runs into this issue.
My alarm (default app) would get snoozed immideately after going off, thus becoming useless.
I have discovered that if I disable the "OK Google" detection from any screen option, the alarm functions fine.
Hope it helps someone not to miss any important appointments.
Click to expand...
Click to collapse
Glad I happened to see this post ... For the past week I've been trying to figure out what was automatically dismissing my alarm ... Uninstalled and reinstalled so many apps and xposed modules and never figured it out. Thanks!
Sent from my LG-LS980 using XDA Premium 4 mobile app
iDoc21 said:
Glad I happened to see this post ... For the past week I've been trying to figure out what was automatically dismissing my alarm ... Uninstalled and reinstalled so many apps and xposed modules and never figured it out. Thanks!
Sent from my LG-LS980 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Gald I could help. Also, at least I know that it's not only happening on my phone.
I wonder if the bug has to be submitted to Google or LG?
GRRemlin said:
Gald I could help. Also, at least I know that it's not only happening on my phone.
I wonder if the bug has to be submitted to Google or LG?
Click to expand...
Click to collapse
Running in to a similar issue. But instead of the alarm snoozing. I get a pop up message stating "Alarm/Clock has stopped working" and then a flashing notification light. The problem started just this week. I uninstalled the latest Google update and also turned off OK Google" detection from any screen, but that doesn't seem to have had any impact. Odd that I've had no problems with Google Now up until this past Tuesday.
dafever said:
Running in to a similar issue. But instead of the alarm snoozing. I get a pop up message stating "Alarm/Clock has stopped working" and then a flashing notification light. The problem started just this week. I uninstalled the latest Google update and also turned off OK Google" detection from any screen, but that doesn't seem to have had any impact. Odd that I've had no problems with Google Now up until this past Tuesday.
Click to expand...
Click to collapse
I was unable to replicate your issue. I only get the "Snoozed" notification.
However, I moved to Timely alarm app since and it works just fine.
Thank you for the response. I was hoping I'd be able to figure out what's the issue is and continue to use the stock app. But looks like I'll have look into a third-party app.
Thanks again.
dafever said:
Thank you for the response. I was hoping I'd be able to figure out what's the issue is and continue to use the stock app. But looks like I'll have look into a third-party app.
Thanks again.
Click to expand...
Click to collapse
The recent Google Search update seems to have fixed my issue.
Related
So here's a weird one: I'm running stock 4.1.2, and after the update I noticed the alarm going off when I set it... but only for about a second before turning itself off. It doesn't happen consistently - it only seems to happen when I leave the phone charging overnight. If I set the alarm for a minute from now, it goes off as it should. Anyone experience this? Any ideas?
I've tried setting the alarm to repeat weekly, clearing the clock app's data, and, yes, doing a full factory reset. The issue returned. Sometimes I think it might have to do with whether Google Now or Aurora (alpha Firefox) have recently added something to the notification bar, but that's pure speculation.
Don't want to install an app to rectify this, but I suppose I will if I must.
Thanks
P.S. - This thread appears to be nearly identical regarding a GSIII, but even if disabling the lock screen is a work-around, I can't do it.
P.P.S. - Any chance Samsung will be issuing any further updates (bug fixes), or can we expect this most recent update to JB to be the last?
Bump
Nobody else has this issue!?
Nrbelex said:
Bump
Nobody else has this issue!?
Click to expand...
Click to collapse
I have had it from time to time. Haven't found a fix for it.
Sent from my SPH-D710 using xda premium
graydiggy said:
I have had it from time to time. Haven't found a fix for it.
Click to expand...
Click to collapse
Well at least I'm not going crazy. I encourage you and anyone else having this issue to star it on the Android bug tracker: http://code.google.com/p/android/issues/detail?id=43430
Hello guys,
Got my SGS6 Sat and the most recent OTA is installed. I notice and you can see in my screen shot that I have my DND setup correctly, but yet my "favorites or all contacts" if anyone call or text during the hrs it should notify me, it's all on silent mode, but when I turn DND off it rings or vibrate.
I have it setup to DND M-S from 11pm to 5:15am but yet yesterday and today people been texting outside of my hrs specified and yet I don't get notified.
Is anyone having the same issue or have their DND working?
philly0128 said:
Hello guys,
Got my SGS6 Sat and the most recent OTA is installed. I notice and you can see in my screen shot that I have my DND setup correctly, but yet my "favorites or all contacts" if anyone call or text during the hrs it should notify me, it's all on silent mode, but when I turn DND off it rings or vibrate.
I have it setup to DND M-S from 11pm to 5:15am but yet yesterday and today people been texting outside of my hrs specified and yet I don't get notified.
Is anyone having the same issue or have their DND working?
Click to expand...
Click to collapse
I've reported a similar issue on my Note 4 (http://forum.xda-developers.com/note-4/help/disturb-schedule-longer-t3100842). Did you ever find cause or solution?
EP2008 said:
I've reported a similar issue on my Note 4 (http://forum.xda-developers.com/note-4/help/disturb-schedule-longer-t3100842). Did you ever find cause or solution?
Click to expand...
Click to collapse
My solution after working with sprint and samsung was to d/l a 3rd party version in the market called do not disturb and that seems to be working well.
philly0128 said:
My solution after working with sprint and samsung was to d/l a 3rd party version in the market called do not disturb and that seems to be working well.
Click to expand...
Click to collapse
[emoji23] I just installed it, but I'd love to solve the issue so I don't have the redundancy of an app + built-in feature. It was working fine up until last night ?
Sent from my SM-N910U
EP2008 said:
[emoji23] I just installed it, but I'd love to solve the issue so I don't have the redundancy of an app + built-in feature. It was working fine up until last night
Sent from my SM-N910U
Click to expand...
Click to collapse
I would have loved to get mine working without a 3rd party but even when I had samsung connect into my phone they still didn't now what was up, they told me maybe an update would fix it.
philly0128 said:
I would have loved to get mine working without a 3rd party but even when I had samsung connect into my phone they still didn't now what was up, they told me maybe an update would fix it.
Click to expand...
Click to collapse
Did the DND schedule ever work for you or was it broken only after that update?
It's getting old having to use 3rd party apps for something that should just be working on the phone. Marshmallow upgrade messed up my phone big time.
The app itself might have Settings you can go into to turn off notifications. That's what I did and FINALLY I'm free!
I've been smashing my head over this to no avail. Prior to side loading 8.1, when my phone rang the caller and swipe up/down would appear on the lock screen, now it rings, but nothing on the lock screen till I wake it with the fingerprint sensor. Did I miss something? Was this changed? I've been through the settings and still can't see anywhere that I missed. This a security feature so no one can see who's calling till you hit the sensor? Any feed back would be appreciated.
I agree surprised more are not annoyed...lol
Doublecore said:
Well it seems it's only happening when connected to Bluetooth. I hadn't noticed since I'm connected to my headset all day at work. Disconnected from Bluetooth and had my wife call me...screen popped right on. So it's another Bluetooth bug I guess.
Click to expand...
Click to collapse
I tested incoming phone calls with and without bluetooth, and came to the same result. Since it's very annoying for the screen to not turn on, I ended up making a macro with Macrodroid to turn the screen on when a call comes in. This workaround will be sufficient for me until Google fixes the bug.
I posted on this same issue last week. It's the last update to Google Phone app that broke this. I don't have the time to report it to them...so hopefully it gets fixed!
https://forum.xda-developers.com/pixel-2-xl/help/google-phone-update-bug-t3718424
*Edit- To fix(?), uninstall the phone app and it will remove the update. Should work then. Of course you won't be able to use Duo for video calling within the dialer...but I couldn't care less about that.
I just had this happen yesterday. Here is a work around with Tasker and Secure Task to wake screen on incoming call.
Import it in Profiles tab in Tasker and make sure you have Secure Task and have it configured with adb.
5150jpd said:
I've been smashing my head over this to no avail. Prior to side loading 8.1, when my phone rang the caller and swipe up/down would appear on the lock screen, now it rings, but nothing on the lock screen till I wake it with the fingerprint sensor. Did I miss something? Was this changed? I've been through the settings and still can't see anywhere that I missed. This a security feature so no one can see who's calling till you hit the sensor? Any feed back would be appreciated.
Click to expand...
Click to collapse
This may be related to the Proximity Sensor bug introduced with 8.1. Do you have a screen protector on your device? Does it cover the PS?
Nope.. No protector on phone at all.
v12xke said:
This may be related to the Proximity Sensor bug introduced with 8.1. Do you have a screen protector on your device? Does it cover the PS?
Click to expand...
Click to collapse
It started for me on the Google Phone update to version 15 on Dec. 14th. I never had this issue on 8.1 that I did the OTA sideload when I got my phone on Dec. 4.
My proximity sensor is fine. Even with always on display, AOD goes off in pocket and turns back on when I pull it out. On a phone call the screen blanks when I put it to my ear and wakes when I pull it away from my head.
Yep -- I just ran into the problem today as well. I've got 8.1.0 on my Pixel 2 XL, and I get this behavior (display not waking up for incoming call) when connected via Bluetooth -- to my car, headphones (Sennheiser PXC 550) or to my Jabra Speak 710 BT speakerphone.
I considered trying Drupe or Truecaller, but then I read that packet sniffing tests show them sending your contacts data off their servers...so I think I'll wait for a fix from Google. Really annoying. There are a couple of threads on this in Google's product forums / Pixel User Community:
https://productforums.google.com/fo...QEn6fH0OI;context-place=forum/phone-by-google
https://productforums.google.com/forum/#!topic/phone-by-google/hdmLGWSMhSM;context-place=topicsearchin/phone-by-google/category$3Adevice-performance%7Csort:relevance%7Cspell:false
So far, Google doesn't appear to be weighing in with any useful commentary. The only "fix" for now seems to be "uninstalling" the phone app (which just reverts back to the OEM installed version) and then not accepting updates to the app. But I've read that this can spin up other issues.
jonstrong said:
Yep -- I just ran into the problem today as well. I've got 8.1.0 on my Pixel 2 XL, and I get this behavior (display not waking up for incoming call) when connected via Bluetooth -- to my car, headphones (Sennheiser PXC 550) or to my Jabra Speak 710 BT speakerphone.
I considered trying Drupe or Truecaller, but then I read that packet sniffing tests show them sending your contacts data off their servers...so I think I'll wait for a fix from Google. Really annoying. There are a couple of threads on this in Google's product forums / Pixel User Community:
https://productforums.google.com/fo...QEn6fH0OI;context-place=forum/phone-by-google
https://productforums.google.com/forum/#!topic/phone-by-google/hdmLGWSMhSM;context-place=topicsearchin/phone-by-google/category$3Adevice-performance%7Csort:relevance%7Cspell:false
So far, Google doesn't appear to be weighing in with any useful commentary. The only "fix" for now seems to be "uninstalling" the phone app (which just reverts back to the OEM installed version) and then not accepting updates to the app. But I've read that this can spin up other issues.
Click to expand...
Click to collapse
Have you tried the tasker profile from post #7 by Pkt_Lnt? That fixed it for me.
JimSmith94 said:
Have you tried the tasker profile from post #7 by Pkt_Lnt? That fixed it for me.
Click to expand...
Click to collapse
Thanks. If this issue goes on much longer, I'll probably try that. Oddly enough, despite having played with custom Android ROMs and modding over the years, I never used Tasker -- concerned that having the add'l service(s) running in the background around the clock would be more of a battery drain.
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
EMcTx said:
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
Click to expand...
Click to collapse
Thanks for the info. My phone app updated too, so I'll disable the Tasker profile and see if it lights up without it for me too.
Is there a xposed module to disable the stupid proximity sensor? I'm having some issues with it. It does not wake my screen up when I pull it away from my face.
EMcTx said:
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
Click to expand...
Click to collapse
JimSmith94 said:
Thanks for the info. My phone app updated too, so I'll disable the Tasker profile and see if it lights up without it for me too.
Click to expand...
Click to collapse
Reports on G+ state it fixes the issue. I've not seen v.16 yet.
https://plus.google.com/u/0/+ArtemRussakovskii/posts/byEHovfFbMj
My last name starts with "S" too, not sure why Jim gets priority over me. I always get updates late, which is why apk mirror is bookmarked. :good:
Pkt_Lnt said:
Reports on G+ state it fixes the issue. I've not seen v.16 yet.
https://plus.google.com/u/0/+ArtemRussakovskii/posts/byEHovfFbMj
My last name starts with "S" too, not sure why Jim gets priority over me. I always get updates late, which is why apk mirror is bookmarked. :good:
Click to expand...
Click to collapse
Oops, mine was still on v15 so thanks to you, I just installed v16 from your link. See there, you're still da man! :good::highfive:
JimSmith94 said:
Oops, mine was still on v15 so thanks to you, I just installed v16 from your link. See there, you're still da man! :good::highfive:
Click to expand...
Click to collapse
I can confirm V16 fixes the phone app and resolves this issue. It's being rolled out gradually, in waves. If you don't see the update on the Play Store, you can download it from APKmirror. Start here:
https://www.apkmirror.com/apk/google-inc/google-phone/
My issue is the exact opposite..
I answer a call on my bluetooth headset while the phone is in my pocket and buttons start being pressed so I have to take the phone out to lock the screen.
Any quick fixes on this issue?
I'm late to the party, but I fixed this on a Pixel 2 XL in our household. In the system's app settings I force stopped the phone app and cleared the app cache, then I disabled the "Flip to Shhh" feature in the phone app settings. If that fix works for you, please leave a reply so we can validate.
About every few months it seems that for no reason what so ever my notifications stop working on my watch and I have to reset it. Does this happen to anyone else? It's very frustrating.
Never happened on my LTE model...
steelersmb said:
About every few months it seems that for no reason what so ever my notifications stop working on my watch and I have to reset it. Does this happen to anyone else? It's very frustrating.
Click to expand...
Click to collapse
i kind of have something similar but instead of stopping, it can take 5 to 10mins to get them.
i believe it has something to do with battery optimization where something related to the galaxy wearable app gets dozed or something. so to me i think its on the phone side and not the watch.
Happened to me
Yes this just happened to me too. Very frustrating.
bryansjames said:
Yes this just happened to me too. Very frustrating.
Click to expand...
Click to collapse
i believe it maybe the galaxy wearable app. for about a week now i don't get any email notifs, only texts. everything was working well for a while there.
Check the app on your phone. I had same issue and looked into notification settings and some were changed. I wonder if app update changed my settings.
Theater Mode
jnralp00 said:
Check the app on your phone. I had same issue and looked into notification settings and some were changed. I wonder if app update changed my settings.[/QUOTE
Somehow "Theater Mode" got turned on my GWA. I turned it off & notifications came back like before. I am not sure if this was just a coincidence.
Click to expand...
Click to collapse
Brand new phone from Google less then a week old. It came with November .36 update. Havnet unlocked or rooted yet. Only installed a few apps.
Issue 1: Alarm keeps getting set to whatever it wants whenever it wants.....if I tap the phone to see the screen, more often than not, there will be an Alarm set for 5-10 minutes into the future. However, I did NOT set any alarms. AND, the alarm never actually rings. If I go back, the Alarm will be for 5-10 minutes into the future.....and this just keeps happening.
Issue 2: This just started yesterday, the Google App is coming up empty of information, cant seem to get it back....
cmh714 said:
Issue 1: Alarm keeps getting set to whatever it wants whenever it wants.....if I tap the phone to see the screen, more often than not, there will be an Alarm set for 5-10 minutes into the future. However, I did NOT set any alarms. AND, the alarm never actually rings. If I go back, the Alarm will be for 5-10 minutes into the future.....and this just keeps happening.
Click to expand...
Click to collapse
That sounds familiar. I haven't had the issue but I know others have reported something similar with a simple fix. Might want to use the search box limited to the P6P section only for "alarm" and you should find the posts about it.
cmh714 said:
Issue 2: This just started yesterday, the Google App is coming up empty of information, cant seem to get it back....
Click to expand...
Click to collapse
Tried rebooting? I haven't had the issue.
roirraW edor ehT said:
That sounds familiar. I haven't had the issue but I know others have reported something similar with a simple fix. Might want to use the search box limited to the P6P section only for "alarm" and you should find the posts about it.
Tried rebooting? I haven't had the issue.
Click to expand...
Click to collapse
Thanks for that, will search a bit for Alarm. And yes, have rebooted, didnt help. Havent wiped cache yet, but probably give that a try too! Thx!!!
Ok, Found a post saying Tasker was the cause.....so gonna play with the Tasker settings but I had that setting to Never so should be working......
Ok, now found my error on the Google app.......I tweaked the setting off called "Discover" and thats what makes it all disappear. Seems to me that if you have that turned off then whats the point of the Google app?!?! Anyways, my own error.....
Awesome, glad you were able to fix it.