Hey,
I have a ticwatch pro 3 and one of the reasons i bought it were the long battery life and for alarms so i wouldnt wake my partner with an alarm in the morning.
After setting up the watch and configuring essential mode to start and end automatically when i am asleep i have noticed that when essential mode ends in the morning wear OS does not actually start unless i unlock the watch screen which is not ideal as the alarm will not go off unless i unlock screen first.
Is there some way around this? I basically still want essential mode to start and stop but also have my alarm go off without having to unlock the watch to start wear OS.
Appreciate any help
GrimEire said:
Hey,
I have a ticwatch pro 3 and one of the reasons i bought it were the long battery life and for alarms so i wouldnt wake my partner with an alarm in the morning.
After setting up the watch and configuring essential mode to start and end automatically when i am asleep i have noticed that when essential mode ends in the morning wear OS does not actually start unless i unlock the watch screen which is not ideal as the alarm will not go off unless i unlock screen first.
Is there some way around this? I basically still want essential mode to start and stop but also have my alarm go off without having to unlock the watch to start wear OS.
Appreciate any help
Click to expand...
Click to collapse
I read this on another forum, so please consider bringing watch up from essential mode after your alarm wakes you:
"I've tested this and already work on TicWatch Pro 3
Seriously, I've recorded it
All set alarms ring normally on ESSENTIAL MODE, waking me up as usual"
toncheee said:
I read this on another forum, so please consider bringing watch up from essential mode after your alarm wakes you:
"I've tested this and already work on TicWatch Pro 3
Seriously, I've recorded it
All set alarms ring normally on ESSENTIAL MODE, waking me up as usual"
Click to expand...
Click to collapse
Ok weird looks like i have some testing to do why it doesnt work for me.
thanks for the help and video.
I have the same issue...
i tested and no luck. I tried the exact same thing @toncheee video does and the alarm does not go off when in essential mode and instead goes off about a minute after i take the watch out of essential mode.
@toncheee @quack3d may i ask what version your watch is on mine is on
Code:
wear: OS 2.31
Home app: 2.51.0.398500942
Google Play store services: 21.36.14
system version: H MR2
Android Security Patch Level: March 5, 2021
@toncheee if you set an alarm and you go into essentials mode and then out of essential mode what happens if you have screen lock enabled. As that my main issue. watch comes out of essentials mode about 30 mins before alarm goes off but i need to unlock watch for wearOS to start and alarm to go off.
here is a video of me. sorry about the moving of the camera.
ticwatch-alarm
Watch "ticwatch-alarm" on Streamable.
streamable.com
Same versions as you except for: Google Play services: 21.36.55. Thread on the issue here too: https://forum.mobvoi.com/viewtopic.php?f=76&t=57963
quack3d said:
Same versions as you except for: Google Play services: 21.36.55. Thread on the issue here too: https://forum.mobvoi.com/viewtopic.php?f=76&t=57963
Click to expand...
Click to collapse
thanks it looks like its not just us with the issue, hopefully they will fix it soon as this is essential for me and other.
Related
Hello all!
I wonder if its possible to have an alarm on the phone when turned of. Ive searched everywhere for some answers.
I want to shut down the phone at nights and I want the phone to start up and wake me up hehe
I just tried it 2 times , and it doesn't seem to work with klaxon.
Sorry mate i think you should keep it on if you don't want to be late tomorow
Its hilarious that a phone this new doesnt support that kind of alarm. All of my other phones works that way....
It's not a phone, it's a smartphone, pretty much a small PC...
So if you poweroff your desktop, usually not much it can do
That's the same, workaround is to use PlaneMode (along WirelessTime freeware in example)
This way, it wont be off at all..
Like for PDA, you usually never power off this kind of system. You put it in standby mode instead (either automatically or manually)
And the alarm works well with the HD is in stanby mode. It will wake up and ring.
Note that the usual phone are in some kind of standby mode, not fully powered off otherwise the alarm wouldn't work either !
you can switch off the phone part in standby mode and it will give you busy signal though reminders and alarms will work.
i all
I have a LG G watch R, i have had this around 10 months, its paired with my Nexus 5.
Over the past year there has been a few occasions where suddenly the "mute phone alerts and calls" option has suddenly stopped working! *Half way through the day all of a sudden id still get the message on my watch but my phone would make a noise too!
Usually i fixed this by uni stalling android wear, resetting the watch back to factory setting and re pairing them..this usually solved the issue until next time....however!
This time it happened again and no matter what i do it wont work! i have the option to mute phone call and alerts but the phone still makes a noise and is not muted! when i toggle the volume bar it used to say before "muted by android wear" but now it does not.
My phone was updated to android 6.0 last week but for the past week its been fine so i doubt it related to that as like i said its done this before on lollipop.
Few more things to note that may be related, if i swipe down in my notifications box it used to say "android wear connected" but thats no longer there, and if i go into the watch and go into settings and bluetooth devices it does not say anything it just says scanning for nearby devices, and i notced once it said nexus 5 disconcerted??
I must stress that i am connected to my phone as all my notifications come through on my watch fine.
Anyone had this or know a fix?
Thanks
Chris*
Did you find a solution?
Same problem here. I have moto x play (no developer edition) unlocked bootloader/rooted/lollipop 5.1 and LG G watch R.
In my case it seems related to Moto Display (Motorola'app similar to ambient display). If I disable it, mute comes back.
I tried to uninstall android wear app, and then installing 1.3 version. No fix.
On reddit I read that it should be the last update of Google play service instead: user restored his phone fixing the problem. I tried to uninstall play service (no factory reset)...no fix
EDIT: Ok I have just found a middle-solution. I downloaded a module for Xposed (True silent Mode), after activation you will not able to receive any vibrations or sounds on your phone, but you'll receive a vibration on your watch instead. It's similar to android wear function, the difference is if you disconnect your watch you have to disable the silent mode on your phone manually. Hoping Google (or Motorola in my case) fixes it soon in the meantime...
Looks like we are not alone: https://productforums.google.com/forum/#!topicsearchin/android-wear/mute
https://productforums.google.com/fo...context-place=topicsearchin/android-wear/mute
I see other reports and see the issue myself where android wear often says that the watch isn't connected anymore while the watch says it is. And voice commands etc. on the watch still works (I guess they go directly through GMS not involving the android wear app itself).
Maybe there is a bug between android wear and the detection of the connected watch that keeps thinking android wear that no watch is connected and then not muting the notifications on the phone.
Do you have the cloud sync enabled? It's in "privacy & personal data". I have.
Hi still have the same issue, and yes my watch thinks it's not connected also
I have tried both cloud synced and un synced
Try putting your watch on charge, then taking it off
It worked for me, you will notice when on charge the ph is connected but notifications are not muted
I think the ph must think the watch is charging...
The latest wear app version fixed it for me.
http://www.apkmirror.com/apk/google...-wear-1-4-0-2470307-gms-android-apk-download/
Hasn't for me
So I have been using Timely for quite a while on my HTC One m7 and Nexus 5, but ever since I started using my Nexus 6P as my daily phone, I have noticed that the alarm is hit or miss. I tried the suggestions from here, but that does not seem to have made much of a difference. I have also tried going to the stock Clock app, it seems to be a bit better, but not by much.
What I have been noticing is that the alarm I have set for 5:30AM it will either go off or it will just not go off at all and I will get a notification that the alarm was missed at 5:30AM. If the alarm does go off, I usually hit snooze and just lay in bed until it goes off again checking email or something on my tablet (so the phone should still be locked). When I realize that I have been awake longer than 10 minutes, I look at my phone and there is a notification that the alarm for 5:30AM was missed... So it realized the alarm should have went off, but didn't.
I also have 2 later alarms (9:35AM and 10:20AM) and both of them are still in Timely and they work just fine, so maybe there is something with the deep sleep in Marshmallow?
I am running the stock image, updated to 6.0.1 via OTA, no root, no custom kernel, nothing that IMO should be affecting the operation of this type of stuff.
Just wondering if anybody else is having similar issues or if somebody can recommend an alarm app that is not suffering from this issue.
It seems that any alarm other than stock has issues. I see the post you referenced mentioned adding exceptions for those apps to prevent battery optimization. Did you try that with no luck? I don't know if there has been much luck other than just using the stock alarm if you really need to depend on it to wake up for work or other important events. I have never had stock alarm not go off, but I don't use any other apps.
fury683 said:
It seems that any alarm other than stock has issues. I see the post you referenced mentioned adding exceptions for those apps to prevent battery optimization. Did you try that with no luck? I don't know if there has been much luck other than just using the stock alarm if you really need to depend on it to wake up for work or other important events. I have never had stock alarm not go off, but I don't use any other apps.
Click to expand...
Click to collapse
I did try turning off optimizations for Timely, that did not seem to help much. The funny thing is that the stock alarm is also having similar issues, so either I am that heavy of a sleeper or maybe I just need to try flashing the factory image back to it, which, like I mentioned, I do not think I did anything to cause this type of issue, but it is an OS after all, so who knows what could anger it.
I did just tonight try setting the auto dismissal time to Never as well as maxing out the volume (it was down by about 10%), so maybe that will wake me up.
I'll see what happens tomorrow morning and will report my findings a little later. In the mean time, if anybody can think of something that I could try, it would be greatly appreciated, although a restore is not the end of the world, I would like it if I didn't have to spend the time restoring the apps and accounts and what not.
Does this apply to you?
gotzaDroid said:
Like Red said, you need to have an alarm set first. AND... Any automatic "do no disturb" settings like, "every day from xx : xx to xx : xx" will override the "do not disturb until next alarm". So if you have the phone automatically do not disturb until 8am every day, but you need to wake up at 6am and set the do not disturb to until next alarm before your usual rules kick in... at 6am, do not disturb will not automatically turn off with the alarm. It'll stay on until 8am. Just FYI.
Click to expand...
Click to collapse
Sent from my Nexus 5X using Tapatalk
I'm on 6.0.1 stock and I use Timely, have no issues at all...
For what it is worth, after I set it that the Stock Clock Alarm Never gets dismissed and made sure the alarm volume was set to 100%, it has been going off like... umm, clock work. I tried doing Timely last night and made sure I had another alarm setup just in case, I noticed the Stock Clock alarm went off on the other device, but my 6P with Timely, did not go off.
I'm just going to give up on Timely for now, maybe they will release an update and I will give that a shot, but for now, Stock it is.
The new doze mode will impact any alarms apps that are not updated for android M to use GCS etc. that's why your alarms are not firing.
For now you have to use the stock google alarm which correctly works with doze mode.
Hello,
I have activated energy saving mode on my phone and I have also installed Alarm Clock Plus from the play store. I noticed that when the energy saving mode is on the alarm rings whenever it wants to but always after the set time. Sometimes it rings 5 minutes later and some others 20 minutes later. The stock alarm works correctly.
On my Xperia Z2 there was an exception list that you could use to add apps that would be excluded but I dont seem to find it on S7 Edge.
As long as I deactivate the energy saving mode, then the alarm works correctly. Any ideas for a solution? Thanks in advance
There is a setting under Battery. You can choose applications to not be included in energy saving features.
If you don't mind me asking, why don't you just plug your phone in at night and you won't need energy saving mode.
By the way, I've been using Alarm Clock Extreme for 3 years and it's never failed to go off. Plus the option for solving math problems to dismiss is great. It keeps me from turning the alarm off while I'm still half asleep.
Thanks for your answer. Indeed that was the case. I missed that "Information" button a bit lower. I tried it and it now works correctly.
Coming from an exceptional device (battery-wise) as the Z2, I was used to not charge my phone for 2-3 nights so I want to see if I can do something similar on this one as well. Been using ACP since the LG Optimus 3D era back in 2008 so I am used to it. It also offers math problems and thats what I'm using . That said I'm open to suggestions so I might try ACE as well.
I use Timely as my timer for my breaks at work. Also I use it as my alarm to wake up. At first I couldn't get the countdown timer to show in the notifications or update as it counted down.
After going into power managagement and turning off all power saving policies, I could see the timer countdown but only until the phone locks. Once locked it won't show the timer at all. The alarm I set is the same way it didn't go off or wake up phone, but as soon as I hit the power button to turn on the lock screen then alarm went off.
I've tried turning off smart power-save all together as well with no luck. I use smart lock so my phone shouldn't even lock when I'm at home but still didn't work.
Any other ideas or features to that I could try ? I've been using Timely for the past couple years on multiple android devices and never had this issue before. Any help would be appreciated.
I use Timely without any issue and it wakes me up every morning . What device are you using? What ROM? root? Xposed? Any battery saving app?
Yep.
Yes, I've been using Timely on every Android for the past 3 or 4 years. It miserably failed on the Axon 7. Every measure I took came to no avail. Uninstalled. Anyway, they stopped updating it on February 2015. Using "Alarm Clock Xtreme Free" currently.
Yurik46 said:
I use Timely as my timer for my breaks at work. Also I use it as my alarm to wake up. At first I couldn't get the countdown timer to show in the notifications or update as it counted down.
After going into power managagement and turning off all power saving policies, I could see the timer countdown but only until the phone locks. Once locked it won't show the timer at all. The alarm I set is the same way it didn't go off or wake up phone, but as soon as I hit the power button to turn on the lock screen then alarm went off.
I've tried turning off smart power-save all together as well with no luck. I use smart lock so my phone shouldn't even lock when I'm at home but still didn't work.
Any other ideas or features to that I could try ? I've been using Timely for the past couple years on multiple android devices and never had this issue before. Any help would be appreciated.
Click to expand...
Click to collapse
ohc1492 said:
Yes, I've been using Timely on every Android for the past 3 or 4 years. It miserably failed on the Axon 7. Every measure I took came to no avail. Uninstalled. Anyway, they stopped updating it on February 2015. Using "Alarm Clock Xtreme Free" currently.
Click to expand...
Click to collapse
I have the Axon 7, stock with b29 software, not rooted. I'm going to give Alarm Clock Xtreme a try tonight and see what happens.
I use Timely and it's randomly off by as much as 8 minutes. Usually it's 4 minutes late when the alarm goes off. And no I'm not sleeping through 4+ minutes of an alarm, my alarm is a song and I wake up right from the start of it. This is annoying since it forces me to set my alarm to earlier to make sure I'm not late, but then sometimes it does work on time so I've woken up a little early for nothing.
It's always been like this for me, before bootloader unlocking, before root, before Xposed or anything. Now I'm BL unlocked, rooted, with Xposed, etc, installed and I'm still having the exact same issue. B29 of course, prior versions had the same issue.
Alarm clock Xtreme did work for me last night with no issues. Woke the phone right up even with Smart power save enabled, and allow deep sleep in the power management features turned on. (That's how it was configured at install, and I didn't change anything)
I will miss some of the features of Timely, but I guess it's time to move on if they're no longer supporting it.