Huawei Watch 2 Sport - all sensors are dear after latest Wear OS update - Huawei Watch 2

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 .

Related

dead camera....twice

Dear all,
A few days ago, my N5's camera stopped working and none of the usual solutions (reboot, clean data and cache of camera app, even complete wipe and change of ROM) did anything to fix the problem. So I went on ebay, and bought a replacement back camera, fitted it and all was well...for a day!!! It looks like after just one day (and nearly no use at all) the new camera has already stopped working. Is anyone aware of what may be causing it, and of a way to fix it? or is it time for a new phone?
Thanks for your help!!
Is it possible the camera connction on the motherboard is a bit flaky?
audit13 said:
Is it possible the camera connction on the motherboard is a bit flaky?
Click to expand...
Click to collapse
Thanks for your reply. I thought that too after the second camera went wrong. I re-opened the phone and checked the connection, and from what I can see it seems quite solid. I am not sure what could possibly be going wrong that causing 2 camera modules to go bad in quick succession though. While the rest of the phone works perfectly.
Maybe it's just coincidence. I guess you could try a third camera to see what happens.
Can't connect to camera
My camera quit working the day I updated to 6.0.1
At first it would work for a few hours after a fresh boot. Now it won't work at all. I replaced the camera module with a working one and it worked for a few hours then died. Now all I get is "can't connect to camera". I'm convinced its related to the marshmallow update.
Safe mode doesn't help. Factory reset doesn't help. Third party apps still let me use the front camera but the rear is dead. I think I've reached the end of the road buying nexus devices and beta testing OS releases.
Maybe it because of your sd card
dixie600mhz said:
My camera quit working the day I updated to 6.0.1
At first it would work for a few hours after a fresh boot. Now it won't work at all. I replaced the camera module with a working one and it worked for a few hours then died. Now all I get is "can't connect to camera". I'm convinced its related to the marshmallow update.
Safe mode doesn't help. Factory reset doesn't help. Third party apps still let me use the front camera but the rear is dead. I think I've reached the end of the road buying nexus devices and beta testing OS releases.
Click to expand...
Click to collapse
Initially I thought this may be a normal issue of age of the phone, but the fact that a few of us are bumping into this so shortly after the marshmallow upgrade makes me think maybe the 2 things are related.
I suppose I could try and install a lollipop rom and buy yet another camera module.
The only component that should face problems in a persons lifetime would be the battery. It is a shame that companies and people treat this stuff as disposable.
OP and others who cannot fix this through software, or a small hardware change, this must be a hardware issue. Something on the mainboard is messing with the camera. Others are running stock marshmallow fine, to rule out any software issues, wipe all and flash new (manually wiping and flashing each partition from fastboot would be best). Report back.
wangdaning said:
The only component that should face problems in a persons lifetime would be the battery. It is a shame that companies and people treat this stuff as disposable.
OP and others who cannot fix this through software, or a small hardware change, this must be a hardware issue. Something on the mainboard is messing with the camera. Others are running stock marshmallow fine, to rule out any software issues, wipe all and flash new (manually wiping and flashing each partition from fastboot would be best). Report back.
Click to expand...
Click to collapse
Thanks for your reply. Done, but to no avail. Infact when you flash from fastboot the camera app is not even installed and the torch does not show up in the notification bar.
It is definitely a hardware issue, which is not resolved by simply replacing the camera module, as that seems to break again in a short amount of time. Not sure if I feel investing in a new mainboard and a new camera module.

[HELP] Light, heart rate, gyroscope sensors not working

Hello everyone,
I bought some days ago a second hand galaxy S6 (G920F), I checked if everything was working and then updated to official Marshmallow, installed TWRP 3.0, and finally moved to a custom ROM (Pure Stock ExtraLite Rom 4.1).
The problem is that I figured out I had a lot of sensors that were not working anymore like light sensor, gyroscope sensor (so also accelerometer etc...), the heart rate sensor seems only partially working, I didn't try the proximity sensor yet. Here is a screen of the sensor page after a *#0*#:
I already tried to clear cache, wipe everything with clean install, flash back official MM rom, tried to make a calibration using GPS status and toolbox (which shows there is a problem with almost every sensor), but absolutely nothing worked.
Right now I am out of clues and I need your help !
Thank you!
So were the sensors working when you got the device?
My S6 Edge had the same issue - all sensors would stop working (and the IR blaster) for a few days/weeks and then eventually they would work for a while again. In the end though, they stopped working completely. I also tried absolutely everything software related first but it turned out to be a fault with the mainboard. I sent it to Samsung who claimed it was caused by liquid damage and refused to repair it (I'm almost certain it wasn't liquid damage because I haven't got it wet) so ended up claiming on my insurance.
Sadly I didn't take the time to check the sensors before upgrading, so I have absolutely no idea about the sensors before I updated the system...
I saw some people talking about this kind of problems being liquid damage related, but I have no idea what happened to the phone before I got it...).
I hope I will be luckier than you were !
my sensors were working fine in 5.0 and then i officially upgrade my s6 to 6.0.1 and eventually all sensors died.
i make a factory reset and everything fine now

SM-365 Firmware Overheating issues

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

Auto rotate / accelerometer seems to be faulty :(

I have tried reinstalling the os, root and unroot. Before the newest update I could get into the debug menu, *#808#, there I could see that the accelerometer is giving faulty data. After the update I can't even get into that menu again.
Seems to be a faulty sensor and something with the software. My facking phone is 2 days old........
Anyone else having this problem? Any ideas?
Yeah autorotate sucks for me. Anytime I'm on YouTube and try to watch in landscape it's hit amd miss and i have to keep moving phone to get it to work
hallo dare said:
Yeah autorotate sucks for me. Anytime I'm on YouTube and try to watch in landscape it's hit amd miss and i have to keep moving phone to get it to work
Click to expand...
Click to collapse
Damn. Sounds bad too.
I noticed this while playing Asphalt8 using the accelerometer to steer. It would work for a bit then get stuck trying to drive me into the side of the road!!!
Thinking it may be a bug in the game, I looked at the raw sensor data using Physics Toolbox Suite and saw the same thing. The sensor outputs sensible data for several seconds, maybe even a couple of minutes. Then the values stop changing for about 12 seconds. The length of time the sensor works for is random but the 'dead time' is always about 12 seconds!
Has anyone found a solution to this? Even a hint as to whether it's a software or hardware problem so I can decide if I should send the phone back or wait for an update.
Thanks
Okay thank God someone else has the same issue. I was wondering what was so wrong for the longest time ?
Extremely annoying issue.
It's a software issue. Confirmed.
When I reboot the phone the issue dissapears. Meaning there is something wrong in the OS that tilts the gyroscope readings. At least there is a workaround... Hope OP fixes it soon
I used an OnePlus 5 for 2 years. Now I bought a 7 Pro. I'm wondering doing a downgrade due to this issue. Incredible how a company like oneplus and a premium phone has a software bug like this and there's still no update yet. Months without an update...
The fingerprint sensor also has a bug... Sometimes it simply doesn't work. The touch stops...
OnePlus! Where are you?

Xperia 1 Fingerprint status test

Open the dialer app, and type *#*#7378423#*#* to open the Service Menu, from there go to Service Tests and scroll down until you find Fingerprint test.
Please post the results here with your device model number (J8110, J9110, J8170), device build number (55.x.x.x.x), age of your device and whether or not you have issues with the fingerprint scanner.
Trying to figure out a pattern and it seems like XDA is more active (in comparison) than other forums for Sony devices.
Thanks.
J9110 flashed with J8170.
On 55.0.A.10.26 (pie), used to say "PASS"
On latest 55.1.A.0.748, now says fail. but fingerprint sensor works fine.
I'm guessing it's just a software issue.
iArvee said:
J9110 flashed with J8170.
On 55.0.A.10.26 (pie), used to say "PASS"
On latest 55.1.A.0.748, now says fail. but fingerprint sensor works fine.
I'm guessing it's just a software issue.
Click to expand...
Click to collapse
Yeah I wish I had more time to test on Pie but I upgraded to 10 almost immediately and the fingerprint has been hit or miss from the start, but for the past day it's been quite bad.
Now it won't unlock unless I completely wipe down the sensor and make sure it's 100% clean, after which it unlocks just fine, but after that it won't unlock till I clean it again.
Quite frustrating, but judging from what I've read, it seems like Sony messed up big time with the Android 10 update for the X1, so I can imagine me and many others are eagerly waiting for a new update.
By the way, do you have any issues on a 'converted' device? Anything not working as intended? And do OTA updates work or do you have to flash every new build manually?
MeltdownSpectre said:
Yeah I wish I had more time to test on Pie but I upgraded to 10 almost immediately and the fingerprint has been hit or miss from the start, but for the past day it's been quite bad.
Now it won't unlock unless I completely wipe down the sensor and make sure it's 100% clean, after which it unlocks just fine, but after that it won't unlock till I clean it again.
Quite frustrating, but judging from what I've read, it seems like Sony messed up big time with the Android 10 update for the X1, so I can imagine me and many others are eagerly waiting for a new update.
By the way, do you have any issues on a 'converted' device? Anything not working as intended? And do OTA updates work or do you have to flash every new build manually?
Click to expand...
Click to collapse
It works 90% of the time for me. Especially after I "trained" the fingerprint sensor. Basically open up the fingerprint settings, then constantly tap your finger, moving your finger slightly with each tap to cover your whole thumb.
IMO the update is fine! Well at least for me. I did a software reset after updating.
OTA updates fine Haven't tested out the dual sim, but I'm assuming it won't work. The only time I had to flash a new build was when I updated from Pie to 10, because I usually do a full wipe during a major update.
I'm using J9110 with latest stock EU firmware. The sensor does not work at all. Even weirder, there is no option to test the sensor in service menu and I cannot find fingerprint scanner in device options. Out of the box the sensor worked great, but gradually started failing after 1 year of use.
Update: I took some screenshots and compared them to other Sony device with working FPS - there is clearly something fishy going on.
The third screenshot is what happens when I launch Fingerprint Manager with Activity Launcher app and try to register a new fingerprint.
@kot5nik exact same issue, mine is entirely missing. Worked at first, gradually started breaking and was intermittent in functionality, then just gone.
b1nly said:
@kot5nik exact same issue, mine is entirely missing. Worked at first, gradually started breaking and was intermittent in functionality, then just gone.
Click to expand...
Click to collapse
Same thing as mine, it is completely dead and no longer works.
Already try repair with sony companion but nothing work
@kot5nik exact same issue
J9110
build 55.1.A.9.127
Worked perfect for 11 months then all the FPS manager simply disappeared suddenly 2 days ago...
Can't test it in Service menu as it's no longer there
LoneWolfL4rs said:
@kot5nik exact same issue
J9110
build 55.1.A.9.127
Worked perfect for 11 months then all the FPS manager simply disappeared suddenly 2 days ago...
Can't test it in Service menu as it's no longer there
Click to expand...
Click to collapse
You update to 11? Otherwise I think you backup and flash with 12.28 to get it back.
problem is same, fingerprint menu is gone.
J9110
build 55.1.A.12.28
anyone solved this problem? please share ..
Since new firmware 55.2.A.4.47, fingerprint works for 1hour, then just start detecting ton of wrong prints even without finger on the sensor, and shut down completely until the phone is restarted. FingerprintTest showing "NOT OK" at this time. FingerprintTest showing OK after a restart.
I'm so sad I'm not able to get Flashtool working to go back to previous firmware. The fingerprint was working really great for the last 10 months (first months were really hit or miss tho).
if u are on Android 11 now u can't downgrade to Android 10 anymore...u can but it's not working well anymore.!
i tried many times going back to Android 9 after updated to Android 10.
after flashing older Android 9 fw Gyroscope sensor isn't working anymore on lower version of Android
I succeed to revert back to Android 10, but it didn't solve the issue with the fingerprint. If you got some issue with another sensor, I will guess that the "drivers" for the sensor can be changed by an update but are not rolled back correctly, thus the creating issue or not solving mine since the faulty "driver" for the FP reader stay the same.
After a day of not even having the fingerprint management in the security options, Support asked me to do a forced reboot (volume up + power) to see if it solves momentarily the reader, there is a well known issue and they are working on a fix. It did solve the issue momentarily so I guess my FP reader is not completely dead (it was my conclusion seing it was still an issue once reverted to Android10) and I just have to wait for a fix.
thehumble1 said:
You update to 11? Otherwise I think you backup and flash with 12.28 to get it back.
Click to expand...
Click to collapse
Sorry for really late answer. Yes I updated to 11 right after it came out.
To prove the theory of update bricking it I bought a replacement sensor from AliExpress (when it arrived, it was clearly a new one, in OEM packaging) and it didn't work either.
In the process of replacement I accidentally broke the screen (because was really hard to replace, at least with my experience, way harder than battery, motherboard, etc.). So I really don't recommend trying this to anyone.
Now there is no point to downgrading, heh.
And no, on 11 firmware shutting the phone down completely or force reboot does not help. I tried everything I could before going for replacement, including full data wipe and disconnecting the battery with inside connector for some time.
Been having the same issue but I can get the fingerprint sensor to work sometimes after booting into safe mode and then booting normally, read that from another post somewhere but can't seem to find it. Mine also keeps disconnecting from LTE and drops to H+ and has been doing that a lot recently I hope that they will update some of this soon getting pretty frustrated with it, any of you been seeing that in addition to the fingerprint issue?
My fingeprint sensor on XPERIA 1 is there in menu but it is not working at all. Can't recognize my finger at all. Resset didn't help as well as restart to safe mode. I gess it is dead. Or is there something else wrong?
The fingerprint on my Xperia 1 is notice with "Could not read fingerprint", because "Fingerprint enrollment time limit reached" (like image attached)
vantrung1_2 said:
The fingerprint on my Xperia 1 is notice with "Could not read fingerprint", because "Fingerprint enrollment time limit reached" (like image attached)
View attachment 5431097
Click to expand...
Click to collapse
Same issue, tomorrow I'll send the phone to a xperia repair center to see if it is a hardware or software problem
Elysiumx said:
Same issue, tomorrow I'll send the phone to a xperia repair center to see if it is a hardware or software problem
Click to expand...
Click to collapse
So, the warranty on mine was over and they asked me 335 euro for "REPLACEMENT FRONT COVER WITH FINGERPRINT READER" (also change the internal fingerprint reader module)
According to them so it is a hardware problem, but at that price certainly not worth it to repair it.

Categories

Resources