The watch will receive the Wear Os H update?
Probably no (99.99%). Only the few last Wear watch have Android plateform H (since september 2018 ?). The oldest is certainly the Ticwatch Pro.
Related
I just got a brand new Gear 2 from my wife who upgraded to the Gear S2.
I know that development is lite in terms of this device, but I'm wondering what everyone uses in terms of a rom - Tizenmod 3 or Wear.
Is there a checklist of all the things that work/don't work on Wear? Will the pedometer and HR monitor work? I know that camera and speaker won't.
I use the fitness apps mostly, plus watch. Don't really use the watch camera, don't use it for calls and don't listen to music on it.
Would Wear be a good choice? I understand that software suggestions are ultimately left to the user - just looking for some pros/cons here.
Thanks!
I using Tizenmod 3 before on my gear 2. Found out it same as original Tizen except some mod added.
I hate Tizen because when I installed watch face more than 30 then I will get force close issue on my phone and my gear 2 no longer able to connect with phone.
Giving up then I try Android Wear, basically what I found out huge different between Tizen and Android Wear is battery and apps support. I happy with Android Wear now.
What I can say is battery life in Android Wear is short. Roughly 20 hours with heavy use. If u can accept this then why not give it try.
U will find out market apps support more than Tizen. . More fitness apps support with continously heart rate measuring.
As u said, camera and call feature won't work on Android Wear.
Sent from my SM-N9005 using Tapatalk
Just one month ago my huawei watch 2 LTE model suddenly start to crash if the always on is activated as in the attached photos
The watch is on the last update of the OS with Oreo android system
anyone have any idea how to fix this?
Is this problem related to last wear OS update or watch HW. I'm trying to contact Huawei for that problem but facing difficulties as I purchased it from italy and I'm at KSA.
abo3bdo said:
Just one month ago my huawei watch 2 LTE model suddenly start to crash if the always on is activated as in the attached photos
The watch is on the last update of the OS with Oreo android system
anyone have any idea how to fix this?
Is this problem related to last wear OS update or watch HW. I'm trying to contact Huawei for that problem but facing difficulties as I purchased it from italy and I'm at KSA.
Click to expand...
Click to collapse
I have the same issue. To me it looks like a hardware issue. If I leave the watch off for a couple of days, it does not happen. The bight line, however, is always shown just before the watch goes to ambient mode.
I have not approached Huawei about this issue. It started a few months ago, so now I only use the watch for exercise. I'm waiting for new WearOS watches with the new 3100 chip.
I was able to successfully get my bricked watch back to life and to avoid the up mentioned problem I just turned off always on mode and the watch is working probably.
I got my S3 classic more than a year ago from S. Africa, last six months it was parked on its charger as I was away for a job.
It is model SM-R770, Tizan ver 3.0.0.2, software R770XXU2CRH1, Knox ver 2.2.0 and SE for Tizen 1.0.0.
Presently is paired with a Blackberry Key2.
Frequently the watch is freezing for few seconds and then the screen is becoming black. Buttons could trigger a reboot or even a reset but nothing is completed unless the watch is back to the cradle.
I have try reboots, master resets but nothing is fixing my problems.
I have seen that there is a tizen ver 4 out there, which could rectify my issues but my watch couldn't fetch it as it did before with previous updates.
What do you think? hardware issues? software error?
Should I wait until Tizen 4 will be available in my area (Greece) or should try oddin-something update?
Thanks
I would use netOdin.
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
Tizen 4 Firmware DSA1 is here:
https://forum.xda-developers.com/smartwatch/gear-s3/rom-tizen-4-odin-files-sm-r765t-sm-t3892404
Choose CORRECT Firmware for SM-R770.
Maybe you have something similar like him... in this Thread:
https://forum.xda-developers.com/smartwatch/gear-s3/help-att-s3-frontier-resets-setup-t3898321
Best Regards
So I purchased two pocox3 NFC phone at once, both can at once, so a Mr and Mrs have both the same phones, we have used for a few weeks. Now we noticed a big difference between the two phones. See image. Any help be great
It's normal that some are factory updated while some may be from a older batch. Since you're on the NFC Europe version you obviously have access to Android 11 while the other device probably has an update waiting. Just check for updates and both phones will be on Android 11 (12.0.6).
As far as the navigation buttons...those can be disabled/enabled on Full Screen Display - Show Buttons.
Over about the last week my Watch4 Classic (SM-R890) went from lasting about 2 1/2 days on a charge to well less than a day. I could not figure out what was going on. I ended up resetting my watch and uninstalling/reinstalling all software on phone. After this I could not setup/sync watch to phone. I did everything I saw on-line to resolve this issue. No luck. My watch is unusable. I saw some reports on-line that there are issues with Watch4 and Android 13. It then occurred to me that I started having the battery issues about the time I updated my phone ( Pixel 6 Pro) to Android 13. Is anyone else here having battery/sync issues since updating to Android 13?
So I was able to setup watch finally. Surprisingly I was able to setup watch correctly when I disabled wifi on my phone. I have no idea on why this worked. After resetting my watch and uninstalling/reinstalling all software on phone I sill have battery issues. Definitely well less than a day. Last night as I slept I lost about 50% battery and I had bedtime mode on. Two weeks ago I would lose 5 - 8% overnight with bedtime mode. Other people are having this issue:
https://www.reddit.com/r/GalaxyWatch/comments/wqo3iu
https://www.reddit.com/r/GooglePixel/comments/x6fb76
I'm not running Samsung health on phone. This is apparently probably not a watch software or watch hardware issue. This is being reported with multiple wearos devices across manufacturers (Like TWP3). It appears to be related to Android 13.
Is there anyone here that has Android 13 on their phone who is not having battery issues?
Not that anyone cares based based on replies but apparently the Sept. Android 13 update addresses Bluetooth issues.
https://9to5google.com/2022/09/06/android-13-pixel-september-update/
I'm in US on Verizon. Apparently Verizon updated yesterday (9/12) the Pixel 6 Pro (TP1A.220905.004.A1). I keep checking for update, not yet. It is definitely Bluetooth issue with Android 13. I turned off Bluetooth on my phone and battery on watch is same as before Android 13 update. Hoping update fixes....
Sorry bro for no replies, it's just that we don't have Android 13 yet.
I am on the Android 13 beta on my Samsung S22 Ultra with the Watch 4 Classic. The watch has the latest load on it since I was on the watch beta. I have had no issues with my watch not lasting at least a full day. I have seen no difference from Android 12 to Android 13.
I received the Android 13 Sept. update (TP1A.220905.004.A1) and sadly this does not fix the issue. Such a bummer. You would think that Google would get this fixed. Given this is an issue with other wearos watches I wonder if this will impact the Pixel Watch...
Fixed issue. After trying many things ultimately it ended up the issue was related to updating from Android 12 to 13 instead of clean update. When I factory reset my phone the watch's battery life is back to normal. It was not Google Assistant or Samsung Health.
Android 12 battery & watch syncing has been working good for me. I have not tried 13 yet....
GW4C and A13, no issues at all..
Sorry people weren't replying and showing you love princess.