Amazfit Bip - Firmware 1.1.5.02 #1324

Closed
by FreeTheTech101 opened 3 years ago · 19 comments
FreeTheTech101 commented 3 years ago (Migrated from github.com)
Owner

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:

Amazfit Bip

Your android version is:

9.0

Your Gadgetbridge version is:

0.31.0

#### Before opening an issue please confirm the following: - [X] I have read the [wiki](https://github.com/Freeyourgadget/Gadgetbridge/wiki), and I didn't find a solution to my problem / an answer to my question. - [X] I have searched the [issues](https://github.com/Freeyourgadget/Gadgetbridge/issues), and I didn't find a solution to my problem / an answer to my question. - [X] If you upload an image or other content, please make sure you have read and understood the [github policies and terms of services](https://help.github.com/articles/github-terms-of-service/#1-responsibility-for-user-generated-content) #### 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: Amazfit Bip #### Your android version is: 9.0 #### Your Gadgetbridge version is: 0.31.0
FreeTheTech101 commented 3 years ago (Migrated from github.com)
Poster
Owner

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.

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.
arocketguy commented 3 years ago (Migrated from github.com)
Owner

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.

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.
Owner

Thanks for the report! We will have to fix gpx then

Thanks for the report! We will have to fix gpx then
arocketguy commented 3 years ago (Migrated from github.com)
Owner

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.

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.
2Napoca commented 3 years ago (Migrated from github.com)
Owner

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

GPXFiles.zip

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.

I'm confirming the same issue. It's related to altitude / <ele> 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: <ele>468.000000</ele> in the new firmware is: <ele>4076.000000</ele> [GPXFiles.zip](https://github.com/Freeyourgadget/Gadgetbridge/files/2560577/GPXFiles.zip) 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.
Pepe404 commented 3 years ago (Migrated from github.com)
Owner

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.

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.
2Napoca commented 3 years ago (Migrated from github.com)
Owner

So far except for GPS/Elevation I noticed no other problems.

So far except for GPS/Elevation I noticed no other problems.
Owner

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.

@2Napoca
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 :/

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. @2Napoca 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 :/
Owner

I think it is fixed in master now

I think it is fixed in master now
Owner

Fixed. And the Firmware is whitelisted. Closing

Fixed. And the Firmware is whitelisted. Closing
2Napoca commented 3 years ago (Migrated from github.com)
Owner

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.
GPXFile.zip

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. [GPXFile.zip](https://github.com/Freeyourgadget/Gadgetbridge/files/2564822/GPXFile.zip)
Owner

@2Napoca
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 3.5.4.1, but then remember to record a new track.

@2Napoca 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 3.5.4.1, but then remember to record a new track.
Owner

@2Napoca
Just to be sure you compiled 0.31.1 yourself?

@2Napoca Just to be sure you compiled 0.31.1 yourself?
2Napoca commented 3 years ago (Migrated from github.com)
Owner

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.

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.
Owner

@2Napoca
0.31.1 is the fixed version and should appear on fdroid shortly. As always we have no influence when that will happen. But normally it is 1-2 days.

@2Napoca 0.31.1 is the fixed version and should appear on fdroid shortly. As always we have no influence when that will happen. But normally it is 1-2 days.
2Napoca commented 3 years ago (Migrated from github.com)
Owner

Thank you. I will wait for it to appear then remake all my tests with the new version and let you know.

Thank you. I will wait for it to appear then remake all my tests with the new version and let you know.
ktau221 commented 3 years ago (Migrated from github.com)
Owner

Thanks, i will test it too.

Thanks, i will test it too.
arocketguy commented 3 years ago (Migrated from github.com)
Owner

I compiled the new version and I can confirm it fixes my GPS track issue. Thank you!

I compiled the new version and I can confirm it fixes my GPS track issue. Thank you!
2Napoca commented 3 years ago (Migrated from github.com)
Owner

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.

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.
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.