Asus, Samsung and Motorola have all been rolling out Android Wear 1.5. Any idea if our watch will be getting it? Supposedly the list of improvements is minor, mostly bug fixes, but includes connection stability fixes.
I know my connection drops occasionally for no reason I can figure out. I'm using Marshmallow stock on an S5 and I've got Doze disabled for Android Wear, yet too often I look at my watch and it shows disconnected, as soon as I turn my phone on or run the app on my phone, it successfully connects.
harry_fine said:
Asus, Samsung and Motorola have all been rolling out Android Wear 1.5. Any idea if our watch will be getting it? Supposedly the list of improvements is minor, mostly bug fixes, but includes connection stability fixes.
I know my connection drops occasionally for no reason I can figure out. I'm using Marshmallow stock on an S5 and I've got Doze disabled for Android Wear, yet too often I look at my watch and it shows disconnected, as soon as I turn my phone on or run the app on my phone, it successfully connects.
Click to expand...
Click to collapse
http://forum.xda-developers.com/huawei-watch/general/1-5-update-watch-3-ringtones-rollout-t3405146
Related
I've noticed recently that my Zenwatch no longer displays the correct battery level for my phone. If I edit the watchface configuration to remove and re-add the battery level it will correct the figure, but it soon becomes out of date again (i.e. overstating the battery level).
l've tried the Explorer, Illusion and a custom watchface created using the new Zenwatch Watchface Designer app, and all have the same problem
My watch is running Build LCA43, and my phone is a Galaxy S4 running an Android 5.0.1 ROM.
Hmmm....I just upgraded my phone from a Galaxy S4 to an LG G4 and I still get the same problem - phone battery not displayed accurately on the watch. Am I the only one with this problem?
itm said:
Hmmm....I just upgraded my phone from a Galaxy S4 to an LG G4 and I still get the same problem - phone battery not displayed accurately on the watch. Am I the only one with this problem?
Click to expand...
Click to collapse
I haven't had any problem with my ZenWatch 2 reporting phone battery. The first thing that I would think is that maybe your phone to watch connection is being lost, and so the watch isn't being updated. Have you had texts or anything come through while the incorrect number is still displayed? Next time it happens open the android wear or zenwatch manager apps on your phone and verify that it reports them connected (or in the case of zen manager that it is reporting numbers matching what is displayed on your watch). If you're using a watch face other than a standard android one try with either a standard android wear one or a zenwatch manager one that way you know if its connected to the watch face (or an associated app).
Android Optimizer said:
I haven't had any problem with my ZenWatch 2 reporting phone battery. The first thing that I would think is that maybe your phone to watch connection is being lost, and so the watch isn't being updated. Have you had texts or anything come through while the incorrect number is still displayed? Next time it happens open the android wear or zenwatch manager apps on your phone and verify that it reports them connected (or in the case of zen manager that it is reporting numbers matching what is displayed on your watch). If you're using a watch face other than a standard android one try with either a standard android wear one or a zenwatch manager one that way you know if its connected to the watch face (or an associated app).
Click to expand...
Click to collapse
The connection with the phone is fine the whole time this is happening - I continue to get email and all other notications on the watch. If I go into the watchface config on the phone (in Zenwatch Manager) and disable/re-enable the battery level display it resets to the correct value on the watch, but shortly afterwards it becomes out of date again (i.e. the battery level on the watchface stops decrementing).
I get this problem on all of the watchfaces that I've tried (5 different ones)
I got my Pixel XL (unbranded) earlier this month, and as much as I wanted to love the phone, two consistent issues keep happening which are making me despise it.
The first issue is my phone refuses to retrieve Push notifications while it's on standby. I will get no notifications from any app until I physically wake my phone. As soon as I pick the phone up and turn on the screen, BAM, a billion notifications. This is true even for Google apps like gmail and hangouts. I have seen lots of threads on this subject dating back years for various devices, and none of the 'solutions' fixes my situation. Battery Optimization isn't on, and even when I toggle it on and exempt all my apps, it still does it. IPv6 is disabled at my home network level. I disabled the Connectivity service. I enabled notification importances and set all apps to high. I turned off WiFi while on standby. I begrudgingly did a full reset. Nothing has worked.
The second issue is related to bluetooth. I cannot get it to stay on. It turns itself off whenever it feels like, so whenever I get into my truck and expect my GPM to start playing, all I get is "The bluetooth stereo device is not connected." I take pride in my attentive driving, which means if I forget to reconnect everything while still in my driveway, I now have to pull over just to get some tunes playing. Getting infuriating...
So, I'm at my last nerve. I turn to the Gods of XDA for your advice before I return this thing. Is there any fix to all this? I'm not opposed to rooting or using custom images. I just want my phone to work.
Thanks in advance for any info you can provide.
Google is aware if the Bluetooth issue, the Feb update caused it. They are working on a fix.
I got nothing on the notifications. Gmail doing that is quite common and goes beyond the Pixel. Never heard of anyone having issues with other apps.
You running any doze programs or task killers?
TonikJDK said:
Google is aware if the Bluetooth issue, the Feb update caused it. They are working on a fix.
I got nothing on the notifications. Gmail doing that is quite common and goes beyond the Pixel. Never heard of anyone having issues with other apps.
You running any doze programs or task killers?
Click to expand...
Click to collapse
It wasn't the Feb update. Bluetooth got bugged in the 7.1.1 update for me personally.
TonikJDK said:
Google is aware if the Bluetooth issue, the Feb update caused it. They are working on a fix.
I got nothing on the notifications. Gmail doing that is quite common and goes beyond the Pixel. Never heard of anyone having issues with other apps.
You running any doze programs or task killers?
Click to expand...
Click to collapse
No, the phone is pretty much stock. I have Skype and a couple games on it, but nothing that would interfere with network connectivity while on standby. Just to be sure, Doze is Battery Optimization in the settings, right? It's default to off, but after experiencing issues, I turned it on and exempted all apps. Didn't work, so I turned it off again.
I've never had this issue with GMail. The latest I have ever been notified of a new email from gmail is about 5 mins. Now, I go hours without them up until I wake my phone. And again, this is for all apps that have actual push notifications. I'll pick up my phone, then get a slew of new emails, skype messages, hangouts, etc...
So I have a Moto 360 gen 1 and Samsung Galaxy Edge+. I just got the Nougat update on the phone.
After the update, my watch has been draining battery like crazy. I usually got a full day out of it and charged it fully at night. Now, I can't even get to 5pm.
I reset the watch and re-synced with the phone. No change. This morning it's draining at a rate of about 20%/hour which means I will hardly make it past lunch. I also don't even get call notifications now.
I'm fiddling with Android wear and watch settings to try to disable any unneeded app (I only use the watch for basic notification and step counts).
Hello,
About Nougat and Moto 360 ... I received it on my Moto G4 a few weeks ago and I'm not experiencing any battery drain.
Watch battery behaviour is the same as before when phone was in Marshmallow.
isearchable said:
So I have a Moto 360 gen 1 and Samsung Galaxy Edge+. I just got the Nougat update on the phone.
After the update, my watch has been draining battery like crazy. I usually got a full day out of it and charged it fully at night. Now, I can't even get to 5pm.
I reset the watch and re-synced with the phone. No change. This morning it's draining at a rate of about 20%/hour which means I will hardly make it past lunch. I also don't even get call notifications now.
I'm fiddling with Android wear and watch settings to try to disable any unneeded app (I only use the watch for basic notification and step counts).
Click to expand...
Click to collapse
try uninstalling updates on Google Play Services (some app will prompt and make you update again, do that).
Uninstall and install all apps that have Wear app as well (like what apps show in Wear, uninstall the app in phone and reinstall and sync the watch in Android Wear app settings)
With such draining its just best to turn off everything unnecessary. Or turn off watch completely. With all resetting and resyncing, the watch will be dead soon anyways.. But probably it was just syncing or updating something by itself and you interrupted it by the reset so it had to do all the syncing again, draining the battery again ..
Hi, I updated to Pie last month and I'm really not seeing any significant feature updates. But I've lost some of my favourite features, including...
Swipe from top right corner to put an app into windowed mode
Voice to unlock
"Whats on my screen" in the google app.
Detailed battery usage per app.
And I can no longer have stable BT connection to my Range Rover Evoque.
So I'm strongly considering reverting to Oreo. Even though I don't like the idea of missing the security updates.
Is there any other reason I shouldn't. Is there some killer feature that I'd lose out on that I haven't noticed? Because As far as I can see, Pie and the One UI is mostly removal of my favourite features...
As to What's on my screen on Google Assistant, it shows up on my S9. Maybe a setting is off, or maybe your carrier does not have that option enabled, if it's carrier dependent.
As for battery used by a given app, go to settings, device care, tap on the battery icon. Or try using GSam.
As for the BT connection to your car, maybe pairing the phone again can help. Also, check for software updates for your car's radio if available.
I have been having this issue since updating my phone (Pixel 6 Pro) to Android 13. The battery life of my Galaxy Watch 4 Classic (SM-R890) has tanked. I used to get 2+ days of battery life with the watch and after the Android 13 update I got well less than a day. Many people on reddit have the same issue. It is not related to the watch, Other Wear OS watches are having same issue (like TWP3). This appears to be a Bluetooth issue with phone. When I turn off Bluetooth on my phone, my watch is back to 2+ days. In the Sept. update bulletin It said "Fix for issue occasionally preventing certain Bluetooth devices or accessories from connecting". I was hopeful that the Sept. update would fix this issue but alas it does not. I have the Verizon Sept. update (TP1A.220905.004.A1). I currently turn off Bluetooth on my phone so my watch's battery does not drain. It kind of sucks having a smart watch not connected to phone. Does anyone know if there is a way to resolve this issue?
I have the exact same watch and pixel 6 pro, I am not experiencing this issue. Although I do not use google assistant, which was draining my phone and the watch like crazy as you report, after stopping to use I stopped having problems. August update Android 13 galaxy watch app was draining the crap out of my phone, to the point I mostly disabled it and manually allowed the sync, again after Samsung software updates and Sept build all of this has gone away again.
August update was so crap I also did a factory reset of the phone no restore to try to fix all of this, and other issues with Bluetooth, made no difference. With September update almost all these issues have gone away.
If you upgraded from 12 -13 not factory reset I would recommend doing that.
Or backup the watch and reset it, making sure you remove the watch for bluetooth devices on the phone before, so it sets up clean as a bluetooth device.
Do you think that if I disable Assitatant on phone this could resolve issue? I use this feature very infrequently. I do not have installed on watch. I did upgrade from from 12 to 13 as apposed a factory reset. I'm fine doing phone reset though a bit more work (backing up texts, photos, etc.). I did reset of watch after A13 update but pre sept update. Do you think resetting watch now after sept update could resolve? Thanks for your help!
It's Samsung health that's draining the battery. I rolled back to the July version of Samsung health and battery is great. You can also turn off Samsung health permission to "physical activity" and that will help. The problem is the August update for Samsung Health basically keeps keeps the app running constantly on Android 13 because it's trying to sense all physical activity from your phone and doesn't allow the phone to deep sleep. It's interesting because if you roll back to the July build of Samsung Health, you can keep the physical activity permissions on and it doesn't have the deep sleep issue.
Sorry to tell you I'm not experiencing this. I get a good 2.5-3 days of battery life with samsung health and everything running as normal on Android 13 and the latest GW4 update.
shiftr182 said:
It's Samsung health that's draining the battery. I rolled back to the July version of Samsung health and battery is great. You can also turn off Samsung health permission to "physical activity" and that will help. The problem is the August update for Samsung Health basically keeps keeps the app running constantly on Android 13 because it's trying to sense all physical activity from your phone and doesn't allow the phone to deep sleep. It's interesting because if you roll back to the July build of Samsung Health, you can keep the physical activity permissions on and it doesn't have the deep sleep issue.
Click to expand...
Click to collapse
I do not have Samsung Health installed on phone.
Teet1 said:
Sorry to tell you I'm not experiencing this. I get a good 2.5-3 days of battery life with samsung health and everything running as normal on Android 13 and the latest GW4 update.
Click to expand...
Click to collapse
On your phone did you upgrade from 12 to 13 or do a factory reset?
fliptwister said:
On your phone did you upgrade from 12 to 13 or do a factory reset?
Click to expand...
Click to collapse
I upgraded from 12 but didnt have any issue. I recently did a factory reset and I still don't have this issue.
fliptwister said:
Do you think that if I disable Assitatant on phone this could resolve issue? I use this feature very infrequently. I do not have installed on watch. I did upgrade from from 12 to 13 as apposed a factory reset. I'm fine doing phone reset though a bit more work (backing up texts, photos, etc.). I did reset of watch after A13 update but pre sept update. Do you think resetting watch now after sept update could resolve? Thanks for your help!
Click to expand...
Click to collapse
Yes, absolutely, do a search for something like huge battery drain after google assistant launches on watch 4, you will see it littered everywhere and the recommendation was to uninstall it. Quick and easy test, then if it makes no difference then just install it again.
shiftr182 said:
It's Samsung health that's draining the battery. I rolled back to the July version of Samsung health and battery is great. You can also turn off Samsung health permission to "physical activity" and that will help. The problem is the August update for Samsung Health basically keeps keeps the app running constantly on Android 13 because it's trying to sense all physical activity from your phone and doesn't allow the phone to deep sleep. It's interesting because if you roll back to the July build of Samsung Health, you can keep the physical activity permissions on and it doesn't have the deep sleep issue.
Click to expand...
Click to collapse
Yes there is a number of Samsung chats, blogs about this behaviour and for the best part Samsung seemed to shrug it off
shiftr182 said:
It's Samsung health that's draining the battery. I rolled back to the July version of Samsung health and battery is great. You can also turn off Samsung health permission to "physical activity" and that will help. The problem is the August update for Samsung Health basically keeps keeps the app running constantly on Android 13 because it's trying to sense all physical activity from your phone and doesn't allow the phone to deep sleep. It's interesting because if you roll back to the July build of Samsung Health, you can keep the physical activity permissions on and it doesn't have the deep sleep issue.
Click to expand...
Click to collapse
I do not have Samsung Health installed on phone.
edit - Is it Samsung Health on phone or watch which is causing battery drain?
danw_oz said:
I have the exact same watch and pixel 6 pro, I am not experiencing this issue. Although I do not use google assistant, which was draining my phone and the watch like crazy as you report, after stopping to use I stopped having problems. August update Android 13 galaxy watch app was draining the crap out of my phone, to the point I mostly disabled it and manually allowed the sync, again after Samsung software updates and Sept build all of this has gone away again.
August update was so crap I also did a factory reset of the phone no restore to try to fix all of this, and other issues with Bluetooth, made no difference. With September update almost all these issues have gone away.
If you upgraded from 12 -13 not factory reset I would recommend doing that.
Or backup the watch and reset it, making sure you remove the watch for bluetooth devices on the phone before, so it sets up clean as a bluetooth device.
Click to expand...
Click to collapse
danw_oz, when I finally reset my phone this fixed the issue for me. Thank you! I tried multiple other things and nothing worked. For me it was not assistant or Samsung Health.