Amazfit Bip - Firmware 1.1.5.02
Before opening an issue please confirm the following:
- I have read the wiki, and I didn't find a solution to my problem / an answer to my question.
- I have searched the issues, and I didn't find a solution to my problem / an answer to my question.
- If you upload an image or other content, please make sure you have read and understood the github policies and terms of services
Your issue is:
Just confirming that firmware revision 1.1.5.02 does in-fact work with Gadgetbridge. Battery percent, notifications, and fitness information seems to be syncing perfectly.
Your wearable device is:
Your android version is:
Your Gadgetbridge version is:
Also, according to the Wiki, call ignoring is a feature which is not yet implemented. However, I can confirm that ignoring the call on the watch does in-fact dismiss the notification, and pressing decline (not sure of the exact string name at the time) does in fact hang-up the call.
1.1.5.02 is not reading the GPS track information correctly. The Mi Fit app correctly shows the GPS track I would expect from a bike ride this morning, using GadgetBridge and GPX viewer shows a wildly different track. Exporting the GPS track and uploading to RideWithGPS also shows the wildly incorrect track.
your welcome. Just verified it works with the Notify and Fitness app if that is of any help.
Also, the plot of the track looks to be shifted like 20 miles to the east of my location. The first few data points are clearly wrong (including the starting point - which is close, but not quite right), then the remaining track looks to shifted off to the east.
I'm confirming the same issue. It's related to altitude / field in the .gpx file.
I'm attaching two logs of the same route (first before firmware upgrade, second after latest firmware upgrade).
As you can see the elevation is way off with the latest firmware (the real altitude being 468m):
in the old firmware was: 468.000000
in the new firmware is: 4076.000000
As a sidenote: in the MiFit application since the latest upgrade the red track log is not continuous anymore, it is missing some segments (I suppose because of same altitude issues). It wasn't missing segments before the firmware upgrade so I'm not sure if this is a firmware problem or gadgetbridge one.
Anyways, thanks for a great tool and keep up the good work.
No silent disconnect? No reconnection problems? In all previous versions (older GB versions and older watch firmwares), those problems finally appeared, usually after a day or two, not immediately.
So far except for GPS/Elevation I noticed no other problems.
Please keep in mind that this issue is with tracks RECORDED with the new firmware and not when syncing older tracks with the new firmware.
I can confirm your findings with elevation. When I divide that by 10 I get a sane track.
Now I need to find out how to decide whether he have to divide by 10 or not :/
Thanks for the prompt reply. Unfortunately I have made a new test with the latest gadgetbridge version and today's tracklog elevation is closer to reality but still off with about 2000 meters (instead of 450m the real altitude). I'm attaching a log with the same route made today.
Too bad :( For me an elevation of "43" looked sane here where I am.
It seems there where two bugs then - one being the altitude and another bug that caused the track being completely broken (which is fixed, and confirmed also by @danielegobbetti).
Remeber you can reset your "last fetched" date by pressing the menu button in the upper right in the activities screen. So you can re-fetch your last track without recording a new one. Then you can also fetch the tracks that were recorded with an old firmware to double check that they are okay.
Another idea would be to try firmware 1.1.5.04 from Mi Fit 22.214.171.124, but then remember to record a new track.
No, I don't know how to compile a version myself. I was using the latest compiled version: 0.31.0.
If you could be so kind and help me compile the 0.31.1 I can redo / do more tests anytime.
Thank you. I will wait for it to appear then remake all my tests with the new version and let you know.
Thanks, i will test it too.
I compiled the new version and I can confirm it fixes my GPS track issue. Thank you!
The latest version finally appeared on F-Droid and I confirm that in v0.31.1 the elevation problem is fixed.
Everything is now back to normal with the GPS logging. Thank you very much for all for your help.
Deleting a branch is permanent. It CANNOT be undone. Continue?