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.
Related
I just purchased new Honor 6x from Amazon in India. I tried watching VR videos today with Aura VR headset. The video was constantly shaking. I did not see such issue with my earlier Honor 6 (no x..). I tried to calibrate the gyroscope using a few apps I could find in the playstore but nothing helped. This is a great phone but gyroscope is really messed up. I tried using Bubble Level and the reading continously fluctuates on a flat surface from 0.2 to 0.6 on both axis.
Is there a way to fix this issue?
-Amit
Ignore this text ...
Ok. Received the replacement phone and it has the same issue.
After talking to Huawei Tech Support, I did, firmware upgrade (though I had the upgraded version already) and factory reset. Nothing seems to be working and my phone still feels earthquake on a flat stable surface.
Is there any non-rooting way to fix this issue? I am being asked by Huawei to take my one-day-old phone to service center...
Went to Service center. They did software reset but no help. They wanted to keep the phone to do hardware testing and I denied - didn't want to have a one-day-old phone opened and played with. I returned the handset. Issue still exists.
Ur phone is not defective
It is rhe problem with all honor 6x devices and not just urs maybe it will be fixed in updates.. Just to let u know Ur device is not defective sadly gyroscope is like that in all 6x
All the Honor 6x's have the same problem because huawei decided to cheap out and use the accelerometers as a virtual gyro. It sucks but i dont use gyro that much, no big deal for me.
Hi all, i bought the S3 Frontier two weeks ago, all went right until this morning. I have noticed heavy lag in the clock dial. I've disabled AOD, and when i check what time is it the second hand (as the chronometer in the chronograph default watchface) stops, and starts to work even after 15 seconds. The only one app I've installed on is the HERE navigation like 10 days ago but the smartwatch worked perfectly the same. I don't know if that problem is brought by Tizen because when i bought it i obviously installed all the updates. For me it's so annoying....
Anyone can help me? Am I the only one that have the same problem? :fingers-crossed:
Thanks a lot!!
I'm experiencing lag as well especially after the recent update. Very disappointing and makes me want to take the watch back as I just purchased it less than 2 weeks ago. I'm not sure what kind of fix there is.
Gdv92 said:
Hi all, i bought the S3 Frontier two weeks ago, all went right until this morning. I have noticed heavy lag in the clock dial. I've disabled AOD, and when i check what time is it the second hand (as the chronometer in the chronograph default watchface) stops, and starts to work even after 15 seconds. The only one app I've installed on is the HERE navigation like 10 days ago but the smartwatch worked perfectly the same. I don't know if that problem is brought by Tizen because when i bought it i obviously installed all the updates. For me it's so annoying....
Anyone can help me? Am I the only one that have the same problem? :fingers-crossed:
Thanks a lot!!
Click to expand...
Click to collapse
Gdv92 said:
Hi all, i bought the S3 Frontier two weeks ago, all went right until this morning. I have noticed heavy lag in the clock dial. I've disabled AOD, and when i check what time is it the second hand (as the chronometer in the chronograph default watchface) stops, and starts to work even after 15 seconds. The only one app I've installed on is the HERE navigation like 10 days ago but the smartwatch worked perfectly the same. I don't know if that problem is brought by Tizen because when i bought it i obviously installed all the updates. For me it's so annoying....
Anyone can help me? Am I the only one that have the same problem? :fingers-crossed:
Thanks a lot!!
Click to expand...
Click to collapse
artisticsoul79 said:
I'm experiencing lag as well especially after the recent update. Very disappointing and makes me want to take the watch back as I just purchased it less than 2 weeks ago. I'm not sure what kind of fix there is.
Click to expand...
Click to collapse
Are you both on Tizen 3.0? What's your Software version number? I'm on Tizen 3.0.0.1 with Software version CQL1 and I'm not experiencing any issues and I just bought my watch 2 weeks ago also.
Yep Tizen 3.0.0.1
Software Version - R760XXU2CQL1
It's just not fast like it should be.
We should be getting a new update soon. Hopefully this will fix some issues.
https://www.sammobile.com/news/tizen-3-0-update-with-gear-s3-battery-fix-now-rolling-out-in-europe
artisticsoul79 said:
We should be getting a new update soon. Hopefully this will fix some issues.
https://www.sammobile.com/news/tizen-3-0-update-with-gear-s3-battery-fix-now-rolling-out-in-europe
Click to expand...
Click to collapse
Doesn't this article say our current build (CQL1) is the new and latest update?
Are you fixed this issue?
I've something like you problem.
Watch hands stops after screen on. And wake up for a few secs after tap on the screen, or button press.
do you reboot the watch every day ? Tizen is bad with memory management and need to reboot often to clear memory old data.
Gear S3 memory etc. can be cleared from the Gear app on your phone
Settings >> About Gear >> Tap RAM Icon (top right corner) >> Clean Now
The Gear S app is a bit unstable and sometimes needs to relaunched to get it to work.
Clean now botton is disabled on my gear s3 app.
Hi all
Has anyone faced the following problem: my watch updated to the latest Wear OS a week ago. And after this all the sensors died - no any single of them is working.
I've googled and tried everything I can - from multiple factory resets and linking watch to another phones to manually enabling app permissions for sensonrs and dev mode.
Nothing worked. Test in Dev mode shows "Fail" for all tests related to sensors.
Any ideas/advice on how to fix this?
koladko said:
Hi all
Has anyone faced the following problem: my watch updated to the latest Wear OS a week ago. And after this all the sensors died - no any single of them is working.
I've googled and tried everything I can - from multiple factory resets and linking watch to another phones to manually enabling app permissions for sensonrs and dev mode.
Nothing worked. Test in Dev mode shows "Fail" for all tests related to sensors.
Any ideas/advice on how to fix this?
Click to expand...
Click to collapse
My Watch 2 sport (4G) got the same issue after 1 year. Sent it to service and got a replacement for free.
Probably a HW issue not related to the SW update....
rettinn said:
My Watch 2 sport (4G) got the same issue after 1 year. Sent it to service and got a replacement for free.
Probably a HW issue not related to the SW update....
Click to expand...
Click to collapse
THanks... My watch is more than 1 year old, AFAIK warranty is over
Anyway - Thanks for advice!
Got exacly the same situation, i got my hands on a LEO-BX9 BT, when i install the older firmware 7.1.1 at the start the steps appear and the heart rate works good, but then it starts making updates and loosing the sensors data, i dont believe it's HW related as lower versions of Android Wear work without a problem. already tried almost every firmware available on XDA and the only one that worked all sensors (briefly before auto update) was sawfish-OWDD.180215.018 can anyone give me some guidelines about this? i am well informed about flashing, rooting etc. but this is new to me. flashing fastboot rom and even that way not beeing able to use the sensors.
EDIT: i know this is a old thread but this is still a beautiful watch and with capabilities to perform as a daily driver.
i came from a mi band 4 looking for more functions even if it costs charging a watch every night.
Ultimate edit: it is definitly hardware, i opened up my watch, used isopropyl alchool to clean up all contacts and it worked again, all sensors are now working except barometric sensor, it seems it had been submerged more that it can handle by the previous owner so it had water damage on it, it is near the microphone and it is unrecoverable unfortunatly. but hey, now you know. if you are having error in heart sensor, acelerometer and such. opening up and cleaning the board and contacts its a good idea. time to open up the drawer and reviving a smartwatch!
dxtremez said:
Got exacly the same situation, i got my hands on a LEO-BX9 BT, when i install the older firmware 7.1.1 at the start the steps appear and the heart rate works good, but then it starts making updates and loosing the sensors data, i dont believe it's HW related as lower versions of Android Wear work without a problem. already tried almost every firmware available on XDA and the only one that worked all sensors (briefly before auto update) was sawfish-OWDD.180215.018 can anyone give me some guidelines about this? i am well informed about flashing, rooting etc. but this is new to me. flashing fastboot rom and even that way not beeing able to use the sensors.
EDIT: i know this is a old thread but this is still a beautiful watch and with capabilities to perform as a daily driver.
i came from a mi band 4 looking for more functions even if it costs charging a watch every night.
Ultimate edit: it is definitly hardware, i opened up my watch, used isopropyl alchool to clean up all contacts and it worked again, all sensors are now working except barometric sensor, it seems it had been submerged more that it can handle by the previous owner so it had water damage on it, it is near the microphone and it is unrecoverable unfortunatly. but hey, now you know. if you are having error in heart sensor, acelerometer and such. opening up and cleaning the board and contacts its a good idea. time to open up the drawer and reviving a smartwatch!
Click to expand...
Click to collapse
Thank you for your advice . I did exactly what you have mentioned and now my smartwatch is working again .
Hi All,
So I have come across a rather large issue when having the charging pins on my Samsung Gear Fit 2 Pro replaced due to corrosion(know defect :/). The watch charges, that's fine, however, upon first boot, it got extremely hot at the power button and HR sensor. Upon researching I discovered this was an issue with Samsung gear devices after roughly June 2018, so I decided to try and downgrade the firmware. I initially downloaded the stock firmware for SM-R360 (by mistake) and updated the watch. The overheating issue was gone and the watch worked fine however none of the sensors worked, which was to be expected as it was the wrong firmware for the device, which actually need SM-R365. So I then arrived at the post "SM-R365 Stock firmware and Combination firmware" by deadman96385. The technique for updating firmware is perfect, no issue there. However, upon uploading the stock firmware to the watch, the horrible overheating issue returned but all the sensors are functioning beautifully. So I am a tad confused? Is it hardware related and time to abandon this watch??
Any assistance will be greatly appreciated.
Hi ?
TRadioactive said:
Hi All,
So I have come across a rather large issue when having the charging pins on my Samsung Gear Fit 2 Pro replaced due to corrosion(know defect :/). The watch charges, that's fine, however, upon first boot, it got extremely hot at the power button and HR sensor. Upon researching I discovered this was an issue with Samsung gear devices after roughly June 2018, so I decided to try and downgrade the firmware. I initially downloaded the stock firmware for SM-R360 (by mistake) and updated the watch. The overheating issue was gone and the watch worked fine however none of the sensors worked, which was to be expected as it was the wrong firmware for the device, which actually need SM-R365. So I then arrived at the post "SM-R365 Stock firmware and Combination firmware" by deadman96385. The technique for updating firmware is perfect, no issue there. However, upon uploading the stock firmware to the watch, the horrible overheating issue returned but all the sensors are functioning beautifully. So I am a tad confused? Is it hardware related and time to abandon this watch??
Any assistance will be greatly appreciated.
Click to expand...
Click to collapse
I think it's some bug on firmware, I have similar problem with Gear Fit 2 Pro, it's overheating after detecting intensive training, like I think, and battery is discharging superfast, about 3 hours…
I think it will be fixed in new firmware version ?
D_Vovan_238 said:
I think it's some bug on firmware, I have similar problem with Gear Fit 2 Pro, it's overheating after detecting intensive training, like I think, and battery is discharging superfast, about 3 hours…
I think it will be fixed in new firmware version
Click to expand...
Click to collapse
I fixed it by disabling dynamic training detection…
Now everything works perfectly
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.