Hi, After 2 months of use, my BIP S GPS stopped working. Zepp tries to update GPS firmware every time it is started, always failing. N&F shows "?" as GPS version. If I try to update GPS with N&F, it says "The file is missing or invalid". Is this a HW failure, GPS chip bricked or else? Any help, suggestion welcome! thanks!
Related
I have an Amazfit Bip clock and it has blocked in "Activity" page.
The touch screen does not respond, the physical side button either, the Mi Fit fails to connect, ...
The clock continuously displays that "Activity" menu screen and you can not interact with it.
How can I reset it or what should I do to use the watch?
I use Mi Fit 3.0.5, FW-0.9.14
Thanks
montarelonf said:
I have an Amazfit Bip clock and it has blocked in "Activity" page.
The touch screen does not respond, the physical side button either, the Mi Fit fails to connect, ...
The clock continuously displays that "Activity" menu screen and you can not interact with it.
How can I reset it or what should I do to use the watch?
I use Mi Fit 3.0.5, FW-0.9.14
Thanks
Click to expand...
Click to collapse
Yes, it happens when BIP trying updating A-GPS data. Run MiFit, keep watch close phone and let him update. Sometimes is failed, but close MiFit, clear memory and try again until success.
Thanks a lot.
In fact, it must be something related to what you say, becasuse as soon as the clock was recovered and connected again to the Mi Fit, it began to update the A-GPS.
What I do not know is if the solution you proposed works, because while it was blocked, the Mi Fit did not recognize it (it always put Connecting ...), it did not connect and I mismatched it and then I could not find it to link it again. That is, there was no bluetooth connection between My Fit and Clock, so I do not know how I could have updated the A-GPS clock trough the Mi Fit
Fortunately, the clock went off and when I put it to charge it started well and it works.
Hi there,
since today i have got the same problem. Sadly the battery is charged 100% so waiting for discharge may take some time. Does somebody know how to reset or force reboot or force discharge the watch?
Thanks in advance!
Amazfit bip problem
Hi, i got exactly the same problem with you..
After i switched my smartphone (from huawei P9 to LG V20) My amazfit Bip suddenly updating A GPS and after that, the touch display is hardly responding, then when i long press the button, it start to displays workout session that cannot be stopped or interrupted in the meantime, Mi Fit can not sync/interract during workout session).
After spent several frustating days, finally i conclude that the main issue is the firmware.
So here is what i did :
- Let the Amazfit watch battery drain (since the activity/workout session can not be stopped, it will drain faster than ussual).
- Recharge the watch until more than 10% and re-connect it to Mi Fit app. (Don't charge it too long, because when something goes wrong you will have to take time to drain the battery again).
- Download NOTIFY & FITNESS FOR AMAZFIT" app from google playstore and connect your Amazfit with the app.
- When the Amazfit Bip paired to Notify & Fitness For Amazfit,
unpaired the watch from the Mi Fit App, then uninstall Mi Fit from your phone.
- Now you have only 'Notify & Fitness for Amazfit' app connected to your amazfit bip.
.- Go to setting section in the app, scroll down and you will find firmware update section, then update the amazfit firmware (you will find some option : english/spain/italian etc., i've choosen english version)
- There imare 3 items that you have to sequintly update one by one : firmware, recources and gps (i failed to update the gps, but all i know, it doesn't matter anyway...)
- After the update finished (sometimes it failed, but i repeat it on and on untill it's succeed), my amazfit starts to work proper and not displaying work out session anymore.
Notify & Fitness for Amazfit is my saviour!
It works better than the official Mi Fit app.
Blocked after Workout
I also had a blocked Amazfit Bip:
On my first workout (a 3 hour bicyle ride), I wanted to stop it. Unfortunately the watch always restarted the workout again.
First I thought that I had double tapped the screen after pressing the Ok (to finish) button. But I tried this for at least 30 times. It always restartet the workout.
I still got a connection from the Mi Fit App, but it told me that the watch is within a workout.
I disconnected / reconnected the MiFit App several times and somehow I was able to quit the Workout.
I immediately switched off the watch, restarted and everything was fine again. No new firmware flashing was required.
I only have it since two days.
[Firmware 0.1.0.26]
Hi all,
Since some days the AGPS data from watch is not updating anymore. I have synced several times. Does anyone else have the same problem? Any idea how to fix this? :crying:
Kind Regards
Christian
Hello ! Same problem for me since one week : AGPS is expired, and sync with Amazfit Android app doesn't fox the issue. I've already reset the app and the watch, with no change...
AGPS sync problem
slayne1 said:
Hello ! Same problem for me since one week : AGPS is expired, and sync with Amazfit Android app doesn't fox the issue. I've already reset the app and the watch, with no change...
Click to expand...
Click to collapse
Hello, I have same problem.
I have factory restarted the watch 4 or 5 times, i uninstall and install the app and still nothing!?
Since the AGPS want sync i have very bad GPS recorded running activity.
Please help?
For Android Only.
Uninstall Amazfit Watch App [3.xx]
Restart the Phone.
Install Amazfit Watch App [Downgrade to 2.7x or 2.9x by manual install APK]
Again pairing and A-GPS can update.
Have downgraded to 2.9. Will report back on AGPS status.
Did not work.
Can I ask, can people on the forum please try a manual sync? Options -> Sync? On my Stratos, it fails at 34%. Want to see if it's something at my end, or if related to the Xiaomi server issues.
I am having the same problem with the Verge China 3.0.50.0 and App 3.6.1.
I have sync like more than 20 times and it still tell me that my AGPS data has expired.
i got same problem, i did't update for a gps on amazfit pace
maybe, xiaomi server is update
Seems ok today.
When you pull down the sync you will see the sync progress (%). The the first count will go to 90% and finish. Then it will reset to 10% and count to 90% then finish.
Previously the 2nd count sync will stuck at 10% for a while and stop.
Hello
My watch has been working good for the last 3 months but lately acquiring GPS not working the first time when I enter running, I have to closecand open it again, also GPS is giving me crazy paces I am a beginner+ runner but it gives me pace of 1min 27sec / km while it should be around 5min 15sec, I tried update to firmware 2.8.5, but same issue I even tried factory reset same issue.
Can you please tell me what is the issue and how to fix ?
Anyone know if the Pace is affected from this ?
https://www.dcrainmaker.com/2021/01/gps-accuracy-impacting-devices.html
What I can say is that I'm facing "old gps data" error when start the activity. The watch is updated, connected to Wi-Fi and syncing correctly. Is there any app that could only download and replace the a-data file for gps fixing?
GPS fixes itself after 3-5 minutes when the activity has already started.
Garmin fixed the problem in a few days.
Luckely this didn't happen to the amazfit watches, it would take a few months before they fixed the isseu.
Hello all, I updated my iPhone to iOS 16 beta and my notifications are not working at all. I know there was a fix coming as an update for the Zepp app which I did (7.1.5) but I am still not able to get anything from my phone into my watch. Notifications, calls, nothing at all. I tried submitting a ticket to support but got no response.
Any help is appreciated, thanks.
Exactly the same problem here. iOS 16 (not beta) and Zepp 7.1.5 (was on Zepp 7.0.3 and it was the same). I have an old Bip in my desk drawer that I tried to activate instead of my Bip S Lite and it actually did receive notifications, until it very soon didn't anymore.
It also seems the watch disconnects itself from Bluetooth from time to time and won't reconnect until I open the Zepp app and do a sync.
I have a watch face that indicates if BT is connected or not, so that's how I know when it's disconnected.
So same problem on both Bip and Bip S Lite. And it seems those aren't the only models affected. There are reports coming from here and there.
Don MC said:
Exactly the same problem here. iOS 16 and Zepp 7.1.5 (was on Zepp 7.0.3 and it was the same). I have an old Bip in my desk drawer that I tried to activate instead of my Bip S Lite and it actually did receive notifications, until it very soon didn't anymore.
It also seems the watch disconnects itself from Bluetooth from time to time and won't reconnect until I open the Zepp app and do a sync.
So same problem on both Bip and Bip S Lite. And it seems those aren't the only models affected. There are reports coming from here and there.
Click to expand...
Click to collapse
Same thing is happening with the Bluetooth too. It gets disconnected and it does not reconnect at all.
Yeah I have seen reports from other watch users and some of them have already been able to fix it but I have tried everything so far with no success.
I have also tried factory resetting the watch(es), forgetting the Bluetooth bindings and uninstalling/reinstalling the Zepp app many times, but to no avail.
EDIT: Have now submiitted 3 reports via the Feedback function in the app. Each one more detailed than the previous.
The latest one:
Watch not receiving notifications and constantly disconnecting from BT.
iOS16, Zepp 7.0.3 and 7.1.5
-Problems started with iOS 16, I think.
-Notifications for Phone calls, WhatsApp, Gmail and SMS. None of them work.
-Watch keeps disconnecting from BT and will not reconnect until I open the Zepp app and do a sync.
-Will not reconnect BT automatically after being out of range.
-I have tried every setting in the App itself and in the phone's settings.
-I tried my old Bip watch and it did show a notification, but only once. Then it too stopped receiving them.
-I have factory resetted both watches many times and uninstalled/reinstalled the Zepp app a couple of times.
-Have made the phone forget the Bluetooth binding many times.
Don MC said:
I have also tried factory resetting the watch(es), forgetting the Bluetooth bindings and uninstalling/reinstalling the Zepp app many times, but to no avail.
EDIT: Have now submiitted 3 reports via the Feedback function in the app. Each one more detailed than the previous.
The latest one:
Watch not receiving notifications and constantly disconnecting from BT.
iOS16, Zepp 7.0.3 and 7.1.5
-Problems started with iOS 16, I think.
-Notifications for Phone calls, WhatsApp, Gmail and SMS. None of them work.
-Watch keeps disconnecting from BT and will not reconnect until I open the Zepp app and do a sync.
-Will not reconnect BT automatically after being out of range.
-I have tried every setting in the App itself and in the phone's settings.
-I tried my old Bip watch and it did show a notification, but only once. Then it too stopped receiving them.
-I have factory resetted both watches many times and uninstalled/reinstalled the Zepp app a couple of times.
-Have made the phone forget the Bluetooth binding many times.
Click to expand...
Click to collapse
I have also done all that and nothing has worked.
Mine started on iOS 16 beta before 16.1 like the update before it and it broke. First time I updated to the beta it was working fine but then the one right before 16.1 that’s where everything started.
Got an update to the Zepp app on my iPhone yesterday (v. 7.1.6) but it doesn't seem to have made any difference. Still no notifications.
I'm beginning to think the problems have something to do with how iOS16 handles Bluetooth connections. The bug is either in iOS16 or in the watch Firmware (although other Amazfit models are affected too).
I base my asumptions on the fact that the watch has trouble reconnecting to BT after being out of range or after it's been restarted. If I restart the phone, however, the watch usually gets connected.
So if it is the phone that initiates the connection, it usually works. But if the watch itself tries to connect, then it doesn't work.
But then again, the notifications do not work even if I keep the Bluetooth window open on my phone and the watch is 100% connected when a message arrives. Strange.
There is also something weird when I make the iPhone forget the BT pairing to the watch. It usually immediately rediscovers the watch and tries to pair again. This happens even if the watch is set to NOT be discoverable.
Just got another Zepp update in the App Store. 7.1.7.
Still no cigar.
There will be no more Huami watches in this household.
Don MC said:
I'm beginning to think the problems have something to do with how iOS16 handles Bluetooth connections. The bug is either in iOS16 or in the watch Firmware (although other Amazfit models are affected too).
I base my asumptions on the fact that the watch has trouble reconnecting to BT after being out of range or after it's been restarted. If I restart the phone, however, the watch usually gets connected.
So if it is the phone that initiates the connection, it usually works. But if the watch itself tries to connect, then it doesn't work.
But then again, the notifications do not work even if I keep the Bluetooth window open on my phone and the watch is 100% connected when a message arrives. Strange.
There is also something weird when I make the iPhone forget the BT pairing to the watch. It usually immediately rediscovers the watch and tries to pair again. This happens even if the watch is set to NOT be discoverable.
Click to expand...
Click to collapse
My apologies for my absence, I am not getting any notifications and honestly lost hope on this. I understand that this is something that might take time but 3 updates later, no real resolution or acknowledgment of what is actually happening.
I also believe that this issue has to do with the connection that the app has with the iOS16 beta since it started after an update. I got beta going, and everything was going smoothly, received an update and everything went south after that with no success or real connection whatsoever.
I just updated the app to 7.1.7 as you did and still the same, the only difference is that it seems the connection is more stable as it has not been disconnected yet and still shows connected without any issues.
I have not encountered the situation you are experiencing in that even if you unpair the watch the phone forces the connection again.
Indeed, I think this will be my last Huami watch. My wife is dying to update to iOS16 but I have warned her multiple times not to since it will break the connection.
Right now I just feel I have a regular watch that I have to charge in order to see the time...
It’s not the iOS beta. I was on the official 16.0 to 16.0.2 and the problem was there. Jumped on the 16.1 beta to try to solve it, but no luck there either.
Threw my Amazfit in my desk drawer and bought myself a Withings Scanwatch.
I finally am able to receive my iMessages on my Amazfit GTR4. On the Notifications in iPhone, go to Messages, and make sure in the Lock Screen Appearance-->Show Previews-> When Unlocked. Mine had changed to Never, as soon as I changed that and synced the Zepp app, now my messages are going through to my watch! Just thought I'd share what worked for me.
Seems that the Zepp app version 7.2.1 has fixed the notifications on my watch. They took their time, I might say.
...aaand then I updated my phone to iOS 16.1.1 and the watch (Bip S Lite) stopped notifying again.
EDIT: My Amazfit Bip on the other hand seems to be notifying just fine. Think I'll be using that one for now.
It definitely seems like the Bluetooth on my Bip S Lite is broken somehow. It won't automatically reconnect after it's been out of range/disconnected. I have to manually open the app to connect it again. And still no notifications.
I've contacted both the seller of the watch and Amazfit. Let's see if they have anything to say about it. I'm using the old Bip for now.
Dusted off my old Bip S Lite and paired it to my phone (or rather reactivated it, since I never did unpair it). To my surprise, it updated its firmware (to 2.1.1.86). Will try it and see if the notification issue is gone.