Huawei Watch 2 not counting steps - Huawei Watch 2

My Huawei watch 2 has stopped counting steps on the watch face. It appears to still be counting them in the background but not on the watch face. How can I fix this!?

Sianlouisenicol said:
My Huawei watch 2 has stopped counting steps on the watch face. It appears to still be counting them in the background but not on the watch face. How can I fix this!?
Click to expand...
Click to collapse
Restart? Swap face for another one and then swap back? Mot sure which watchface you're using but they're a bit glitchy sometimes.

Lolpoppa said:
Restart? Swap face for another one and then swap back? Mot sure which watchface you're using but they're a bit glitchy sometimes.
Click to expand...
Click to collapse
Apologies I should have stated. Have tried multiple watch faces and done multiple restarts and even factory resets and it's still not working. Huawei customer services we absolutely useless so no joy there either!

Use the new User complication and choose Fit data for this.

I am facing the exact issue. We're you able to resolve this somehow?

Related

Exercise app turns off early

I'm having an intermittent issue (1 in 20 times) whereby the exercise app I use just turns off before I'm done. I've used the same app for years without issue, but notice its on Mate-9 or Android-7 as an issue? Any suggestions please? I've tried other apps and same has happened on this device so I'm thinking not an app issue.
I am having the same issue with some gaming apps
Sent from my MHA-L29 using Tapatalk
OK, now its happened 3 times in a row. Anyone know a solution please?
palatkik said:
OK, now its happened 3 times in a row. Anyone know a solution please?
Click to expand...
Click to collapse
It could happen when you're using old-api application and internal task-killer preferred to unload your app from memory.
Press square button to get recent apps and press icon with lock to hold app always in memory.
5[Strogino] said:
It could happen when you're using old-api application and internal task-killer preferred to unload your app from memory.
Press square button to get recent apps and press icon with lock to hold app always in memory.
Click to expand...
Click to collapse
Thanks for that idea. I tried it and so far so good. I will continue this method for next few weeks to see if it solves the problem 100%.
palatkik said:
Thanks for that idea. I tried it and so far so good. I will continue this method for next few weeks to see if it solves the problem 100%.
Click to expand...
Click to collapse
5[Strogino] said:
It could happen when you're using old-api application and internal task-killer preferred to unload your app from memory.
Press square button to get recent apps and press icon with lock to hold app always in memory.
Click to expand...
Click to collapse
No luck I'm afraid. I tried three times successfully using this method then the forth time it was back to the usual rubbish result of app stopping early during the exercise with the lock to hold app in lock position.
I'm open to other ideas please? As it stands the Mate-9 has proved useless to monitor fitness routines. I've written to Huawei support about it (in London UK) and they just say to wait for an o/s update in future!
I suggest you to give up on it. Huawei phones can't work correctly with sports tracking app for YEARS. Probably all their phones have same issues. Just google it and you will find other suckers like us.
Also, Mate 9 is completely inaccurate during the time it tracks (pre-crash). It must be related with different problem - GPS sucks too. Look for GPS thread in this forum to keep you updated.
Last version of Strava app shows in-app alert which says that their app can't work correctly with my device (Mate 9). It still allows me to use it. So, they gave up on us.
My suggestion is to get some old/backup phone and use it for tracking. E.g. I'm using my good old faithful Samsung Galaxy S4.
goranimo said:
I suggest you to give up on it. Huawei phones can't work correctly with sports tracking app for YEARS. Probably all their phones have same issues. Just google it and you will find other suckers like us.
Also, Mate 9 is completely inaccurate during the time it tracks (pre-crash). It must be related with different problem - GPS sucks too. Look for GPS thread in this forum to keep you updated.
Last version of Strava app shows in-app alert which says that their app can't work correctly with my device (Mate 9). It still allows me to use it. So, they gave up on us.
My suggestion is to get some old/backup phone and use it for tracking. E.g. I'm using my good old faithful Samsung Galaxy S4.
Click to expand...
Click to collapse
This phone is looking worse and worse every day I wonder if it will support at least MiFit and Mi Band fitness tracker? Can't crash there, right?!
Anyone found a solution to this yet please? On my Mate-9 - now build B189 the problem seems to be that my exercise app using GPS stops working anytime after about 70 minutes of exercise (I cycle outdoors). If I interact with the app during exercise (such as pause - resume) every hour I can continue recording the exercise for full duration, otherwise after around 70 minutes my apps stop without notice. On other devices same apps work. Seems to be an issue with my Mate-9, anyone else notice this and or fix it?
palatkik said:
Anyone found a solution to this yet please? On my Mate-9 - now build B189
Click to expand...
Click to collapse
Since Huawei updated me to Android 8 the problem no longer exists. Its taken a year to get to love this phone. I still cannot get myself to like the Mate-10 so will stay with this as I now for the first time since owning the Mate-9 have no issues at all with it.
palatkik said:
Since Huawei updated me to Android 8 the problem no longer exists. Its taken a year to get to love this phone. I still cannot get myself to like the Mate-10 so will stay with this as I now for the first time since owning the Mate-9 have no issues at all with it.
Click to expand...
Click to collapse
Nope, problem is not fixed in Oreo. At least with Strava. It still crashes during longer pauses.
goranimo said:
Nope, problem is not fixed in Oreo. At least with Strava. It still crashes during longer pauses.
Click to expand...
Click to collapse
I use a bike computer but was having issues with Strava live tracking, I think I have it resolved but not totally sure.
For some bizarre reason there are two places to exclude apps from power management:
Settings/Apps & notifications/Apps/Settings/Special access/Exempt from battery optimization/*Drop Down* All apps/*Allow/Don't Allow*
&
Settings/Battery/Launch/*Toggle On/Off*
Mate 9: 567/360

New Features coming with Tizen version 3.0

https://www.sammobile.com/2017/10/21/5-reasons-why-tizen-3-0-for-samsungs-smartwatches-rocks/
"With Tizen 3.0, you can turn off the bezel wake function to prevent the ring from waking up the screen." ?
Watch only mode.
I would be very interested to know how accurate the S3 would be in watch only mode.
Presumably, in watch only mode, the device would have no phone or network connection so would not be able to auto-update itself?
I thought the interval setting (e.g. Permanent) for pulse measurement is also included in Tizen 3? At least on Gear Sport and Fit2 Pro it's included.
bobsie41 said:
I would be very interested to know how accurate the S3 would be in watch only mode.
Presumably, in watch only mode, the device would have no phone or network connection so would not be able to auto-update itself?
Click to expand...
Click to collapse
I don't understand what new functionally the watch only mode brings. The S3 can be put in airplane mode. This turns off cellular, WiFi, and BT, thus making the watch an island unto itself. It's not completely dumb, apps not requiring connectivity still work (ie. stopwatch, HR monitor, calendar, S Pay) and previously inputted data is still available. In this mode, the battery will last for several days. The biggest drain will be the watch face.
BTW, auto updates can be turned off. It's a setting in the Gear Manager app.
we are still waiting tizen 3
IMHO we have to wait longer...
Not expect too "soon".
If we have luck then maybe as Xmas "gift" in late December.
Best Regards
I'm not launching nuclear missles or solving the national debt so most of the upgrades don't impact me. Mine does what I want it to do now and I'm afraid an "improvement" will screw up a good thing. A new OS is a risk just to get rid of the little clock on the top when I'm in Standalone.
afblangley said:
I don't understand what new functionally the watch only mode brings. The S3 can be put in airplane mode. This turns off cellular, WiFi, and BT, thus making the watch an island unto itself. It's not completely dumb, apps not requiring connectivity still work (ie. stopwatch, HR monitor, calendar, S Pay) and previously inputted data is still available. In this mode, the battery will last for several days. The biggest drain will be the watch face.
BTW, auto updates can be turned off. It's a setting in the Gear Manager app.
Click to expand...
Click to collapse
In watch only mode, the watch can last for several weeks, not just several days.
unfortunately they forgot to mention a terrible new feature: notifications are instantly dismissed by the sleep gesture.
the watch has a "wake up" gesture which wakes the screen when you turn your wrist to look at it, but enabling it would already force the inverse on you as well.
turning your watch away from your face(or towards you while not in an upright standing position, which is why it's such a failure) will make it go back to sleep.
this was annoying enough before version 3, but now this will also dismiss notification pop-ups.
this means the watch now frequently keeps marking new notifications as read and dismissing them before I even get a chance to read them.
so I receive a notification, I turn my wrist to look at it, and I'm presented with my watchface with no notification or unread-marker.
so now whenever I receive a notification I have to rotate the bezel or swipe into the notification history to see the notification, when I should just be able to see it instantly.
I was under the 2.3.2.4 version. I am to go under the 2.3.2.3 version and the miracle the update 3.0.0.1 came fast in case for information
Not yet rollout to my s3. Just curious If the whatsapp notification issue is fixed or not.
getter1 said:
Not yet rollout to my s3. Just curious If the whatsapp notification issue is fixed or not.
Click to expand...
Click to collapse
If you mean reading last messages...
No, it's not fixed.
Sent from my HTC 10 using XDA Labs
UA Record issue with Tizen 3
It also broke UA Record app. After update UA started, pause button worked (used for my rest between set of exercises performed in gym) but when I tried to use Resume button - application stopped and I had back again my watchface. No exercises recorded. So I decided to reinstall app and what? App is freeezing on it's start screen and after few minutes I have ma watchface back again. Till now it was the only app used by my so often and now it's a sh...t. Does anytime Samsung have to spoil good working things?
Update. Wow. today is working. However another issue - I tried to add new widget in a Quick panel and what? I have message "Installing ... " since two hours and nothing more
watch is lagging after 3.0.0.1 update, any fix coming
Maik268 said:
If you mean reading last messages...
No, it's not fixed.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Sad... thanks!
Maik268 said:
If you mean reading last messages...
No, it's not fixed.
Sent from my HTC 10 using XDA Labs
Click to expand...
Click to collapse
Why are they so ignorant about this issue? Havent any of the engineers at samsung tried to actually use this watch on daily life?! I am so bored of using another app to fix samsung's fault

A bug of Tizen 3 - watchmaker&facer?

Hi guys,
after the update of my gear s 3 frontier (non LTE version) i'm unable to set any watchface correctly - only those which are from Samsung's store.
scenario:
you try to setup a watch face from watchmaker, after a reset the app unable to set the watch face and sets up the default watch face (same with face).
some of my walktrough to isolate the problem:
i've manage to check that if it's a digital watch face (on watchmaker) it will do the problem, if not, it will work normally,
on facer it's happening with no matter what watchface.
i've tried to hard reset my gear s3, delete the watchmaker and Facer app from my phone and reinstall it,
there was no difference.
Thanks for youre help
some one?!
WebsGhost said:
scenario:
you try to setup a watch face from watchmaker, after a reset the app unable to set the watch face and sets up the default watch face (same with face).
Click to expand...
Click to collapse
I have been noticing this also, after rebooting the watch it goes back to the default watchface. It is a minor pain to reset the watchface I want everyday but I guess its something we need to deal with until they fix it, or stop using WatchMaker.
the problem is that i cant use MR.Time or Facer to, each app with its own issues, so i dont know what to do
WebsGhost said:
the problem is that i cant use MR.Time or Facer to, each app with its own issues, so i dont know what to do
Click to expand...
Click to collapse
Try clearing the cache and deleting all data associated with the apps ( Facer, gear app, etc.). Then delete them and clear your phone cache by turning off your phone and doing the volume up, power, and home button combo (I think thats it). and clear your phones cache and reboot. After that reset your watch. Reinstall apps and see if this works. I did that and it worked.

Question when in ODA mode, screen stops updating, so time's wrong when I glance at the watch

What ridiculously simple thing am I missing? Thanks!
apologies, meant AOD!
I have never experienced that problem and I always use AOD and several different watch faces. Perhaps reboot your watch and/or choose a different watch face?
I've tried that, on a Watch 3 in addition to the 4, will experiment more per your suggestion.
I appreciate it, thanks!
I use AOD also, and no watchface issues. Try rebooting and other watchface's as mentioned above...
craignewmark said:
apologies, meant AOD!
Click to expand...
Click to collapse
Ya know, you could edit the thread title to fix that...just sayin'.
Much thanks! Didn't occur to me to check, fighting too many fires at the time...

Question AOD Freeze solution?

Hi, i got the watch yesterday. I updated it and started to notice that all 3rd party face apps ( watchmaker, facer, etc) freezes while on AOD. Minutes just don't move until I awake the watch. Also the usual ways to awake don't work reliably... only the ugly-childish samsung provided faces work as they should.
I have searched and it seems I'm not the only one and it's an update "feature"... So it seems it's not a faulty watch.
It's there any workaround to this?
I have been long gone from smartwatches. Can we rollback?
Thanks
No Rollback yet....
As you need Firmware for this...
From Samsung side...
They are working on new Bugs ehm """Watch Faces"""...
Code:
R8.0XXU1FVB1
This could take again weekS or monthS...
Maybe meanwhile good idea to use good old methods to take Logs... with ADB:
adb logcat...
Or check *#9900#
3d Party Developer need to make new compatible Versions... for EVA8...
But maybe some ON OFF workaround possible...
BUT you need to search for it.
Good Luck.
Best Regards
I've noticed the same thing since the latest big update. I have to tap multiple times to get the AOD to change to the actual watchface. Using Watchmaker Premium myself. It's quite annoying. Hopefully we'll get some kind of fix soon.
Same problem here. For now, I'm avoiding AOD on Facer, etc.
I highly doubt AMOLED anti-burn-in is active when the screen is frozen like that. So, better safe than sorry I guess.
Found this... not tested...
Third-party Watchfaces AOD Lösung
Ich habe eine Lösung gefunden wie die third party watchfaces im AOD Modus wieder funktionieren. Öffnet die Wearable App, geht in die Uhr Einstellungen, öffnet den Reiter Apps, sucht dort das entsprechende Programm über das euer Watchface läuft und aktiviert den Schalter Hintergrundaktivität...
eu.community.samsung.com
I hope with Screenshots possible to manage...
Only as info...
Best Regards
Funny comments from Devs:
What the..... Why... AOD
I applied an update after the Galaxy Unpacked event and did not have any of the issues reported. Someone asked me to check and make sure I had the latest and there was another update. After applying that the AOD did not work. It may work for a few minutes up to 15 then it freezes the time. I...
forum.developer.samsung.com
Only as info...
Best Regards
I really hope they fix this soon. It is destroying my enjoyment of this device.... the recent update ruined it. I never know what the time is now, and sometimes I have to press the screen or button and wait several SECONDS for it to wake up and respond. This morning I pressed it about 10 times in a futile attempt to "unfreeze" the AOD display.
If you have a Samsung Galaxy Watch 4
and 3rd party Watchmaker app installed
there is a workaround.
Wearable app/Settings /Apps /Watchmaker..... enable "allow background activity"
Been using AOD for few days like this AID working ok like this.
See Screen shot
According to this report
(about 53 seconds into video, a new update /fix (for the AOD) has been released
I finished the EVB4 update.
When I go into those settings, I see the "allow background activity" setting, but it is off and greyed out for Watchmaker, so it cannot be turned on. It can be turned on for OTHER apps, though. I tried to force stop Watchmaker, made no difference. Not sure what to do...
UPDATE: Ug, after I force-stopped Watchmaker in the attempt to allow that setting, I lost all my WM faces on the watch AND on the phone. And I don't think I have a backup for the one I use daily and heavily customized (Pulsar Neo). So I rebooted both and then have the watch face back on the watch, but it is not showing in the phone app. Checked version of WatchMaker, it is 7.2.7 (I noticed in your screenshot yours is 7.2.8, but there are no updates for WatchMaker, I just checked on Play). Checked app settings, still unable to allow background activity.
crxssi said:
I finished the EVB4 update.
When I go into those settings, I see the "allow background activity" setting, but it is off and greyed out for Watchmaker, so it cannot be turned on. It can be turned on for OTHER apps, though. I tried to force stop Watchmaker, made no difference. Not sure what to do...
UPDATE: Ug, after I force-stopped Watchmaker in the attempt to allow that setting, I lost all my WM faces on the watch AND on the phone. And I don't think I have a backup for the one I use daily and heavily customized (Pulsar Neo). So I rebooted both and then have the watch face back on the watch, but it is not showing in the phone app. Checked version of WatchMaker, it is 7.2.7 (I noticed in your screenshot yours is 7.2.8, but there are no updates for WatchMaker, I just checked on Play). Checked app settings, still unable to allow background activity.
Click to expand...
Click to collapse
I believe the problem with my lost watchfaces was due to my phone being upgraded to Android 12 just last week. But I am not sure. At least I was able to find the original face and modify it again, and it works.
In any case, I am still unable to find out why I can't set "allow background activity" on WatchMaker. I went though every app, and none of them allow the setting except for "Wear Wiki Reader" and "MyRadar." Further, I can't find anyone else with a similar problem, no matter how much I search. Has anyone else been able to change that setting? Or is it just me??
crxssi said:
I believe the problem with my lost watchfaces was due to my phone being upgraded to Android 12 just last week. But I am not sure. At least I was able to find the original face and modify it again, and it works.
In any case, I am still unable to find out why I can't set "allow background activity" on WatchMaker. I went though every app, and none of them allow the setting except for "Wear Wiki Reader" and "MyRadar." Further, I can't find anyone else with a similar problem, no matter how much I search. Has anyone else been able to change that setting? Or is it just me??
Click to expand...
Click to collapse
firstly ,im on the beta version of Watchmaker
Sorry about watchfaces you lost .
Here's a tip for securing watchfaces ......
(this is what i do .)
On my phone Watchmaker app /My Watches /select you watch face etc /select Export
You will on pop up notification location where you "backup " is stored .
On my phone i use Total Commander ,file manager ,(free version )
Total Commander - file manager - Apps on Google Play
Android version of the desktop file manager Total Commander (www.ghisler.com).
play.google.com
i will then, via Total Commander ,go to my internal storage /Android/data/watchfrenzy/ files /export .....and copy my exported watchfaces from Android data to a safe loacation ...eg laptop ,external hardrive .
If you delete /lose you watchface all you have to do is copy them back to Android/data watchfrenzy/files/export and import into app .
Further tip you can also do this with fonts ...copy .ttf fonts into the fonts folder .
I Google around for reasons "background activity greyed out "
There can be various reasons .
I see some of my watch apps is greyed out ,some is showing ....some greyed out ?
Not sure why ?
Personally, i think the buggy Samsung watch update has something to do with it ?
as not all my watch installed apps are showing on Watchmaker .
eg .Previously my sideloaded Google Assistant ,showed up in Watchmaker
app ,now it does not ...yet in the Samsung Stock watched /apps shortcut ,
it still shows !
See some results and reasons ...
My Google search link....you might get some idea ,as what your reason is ?
background activity greyed out - Google Search
www.google.com
See some screenshots that might give you better idea to explain my above post .....sorry the order is a bit mixed ,but i'm sure you can follow ?
other just asked again
Good luck
I have no problem exporting or importing from the WatchMaker app, the problem was that it had no faces in it. They were still on the watch, but not the phone. From what I can tell, there is no way to suck them back off the watch. But your tips will be handy for others! I only wish I had exported them before they were lost (only 1 matters to me, and I have re-created it).
How did you obtain the beta (and why did you)? It sounds interesting, although I doubt the version is the cause of my problem, since I have seen other users' screenshots with using the same version as I am but without the greyed out button. Are you using a Samsung phone with Android12?
One thing I haven't tried is removing and re-installing WatchMaker. I wonder if that would matter?
Firstly,
I currently have about, +- 30 different, beta programs /apps. on my phone.
Yes, i have a Samsung Note 20 Ultra 5g
So as I'm overall a Android Themer (at heart) wherever it's KLWP theming or Samsung Theme Park or Watchmaker etc
i will join /subscribe to beta versions.
I agree with you, that the beta or stable versions, is not the cause.!
I cannot advise you to uninstall and install Watchmaker................ but personally i would
have tried it.!
(I would have kept my favorite watchfaces safely in another folder to copy/import back. into Watchmaker.
When the latest Wear O S broke 3rd party, Watch theme apps
I was totally lost without, my favorite Watchmaker creation, working correctly in AOD mode.
Just to note....
I've noticed that some of the apps that i cannot toggle is a mixed between system apos and 3rd party apps.
And again.... some if those that i can toggle
is also a mix of system and 3rd party apps.
Good luck
crxssi said:
I really hope they fix this soon. It is destroying my enjoyment of this device.... the recent update ruined it. I never know what the time is now, and sometimes I have to press the screen or button and wait several SECONDS for it to wake up and respond. This morning I pressed it about 10 times in a futile attempt to "unfreeze" the AOD display.
Click to expand...
Click to collapse
I now know what others were talking about when it comes to the AOD and display brightness problem with this last update. Another aspect of just how totally Samsung ruined AOD with the last update.
I was a passenger in a dark car. My AOD watch face was way too bright in ambient mode- and very distracting. I would try to wake it up, which could take pressing a button several times and waiting. Once it woke up, it immediately adjusted the ambient brightness correctly for the dark setting. But 30 seconds later, when it went to ambient mode, back to high brightness again. And it would stay that way. Just for giggles, I tried several other watch faces, including the stupid Samsung ones (that we can't uninstall). Every single one of them did the same thing.
Interestingly, I got so angry, I rebooted the watch,and then it started acting normally again, even with my WatchMaker face. How long would that last? I can't say. But it did at least for that night. (I don't often wear the watch at night).
crxssi said:
Interestingly, I got so angry, I rebooted the watch,and then it started acting normally again, even with my WatchMaker face. How long would that last? I can't say. But it did at least for that night. (I don't often wear the watch at night).
Click to expand...
Click to collapse
Seems kinda random. I just rebooted now it because it was driving me crazy. First time I pressed the lower button, it took 9 seconds to respond. Second time 8 seconds. Then later, it was instant. Maddening. What is taking Samsung so long to react to this??
OK, it has been several days since the April R870XXU1FVC8 update. Ever since, I have no longer experienced the problem with the AOD ambient mode freezing (not updating time/display), nor the problem with AOD ambient display ignoring wakeup (press button, touch, etc has long delay before waking). So I might regret saying it, but I think it might actually be fixed in the update.
The one remaining AOD problem seems to be it gets confused with the auto-brightness. When awake, the brightness seems to always be correct. But sometimes it doesn't update brightness correctly when entering ambient mode or while in ambient mode. It requires waking the watch and then it immediately corrects the display brightness.
So, finally, my watch is a watch again.
No update for over 6 weeks for my sim-free LTE Watch 4. The AOD screen update issue continues. Have any other LTE owners had the update that fixes this?
New watch 4 classic owner here (on verizon). I'm still having issues with the display freezing even after allowing background activity for watchmaker. Sometimes it works, sometimes the faces freeze for 30 seconds or so before updating and starting to show the seconds hand.
Anyone else still having issues or have another solution?
lunari said:
New watch 4 classic owner here (on verizon). I'm still having issues with the display freezing
Click to expand...
Click to collapse
LTE uses don't have the recent update yet.
crxssi said:
LTE uses don't have the recent update yet.
Click to expand...
Click to collapse
Well that would explain it I'll rock it with AOD off for now and hope the LTE update drops soon.

Categories

Resources