Amazfish

Rating: 
4.64865
Your rating: None Average: 4.6 (37 votes)

Donations: https://paypal.me/piggz

Companion application for the Huami Amazfit Bip and Cor

***PLEASE READ BEFORE UPDATING TO 0.9.0***

Version 0.9.0 requires sailfish version 3.0.3.8 or above due to changes in the base sailfish image

Powered by KEXI

As of version 0.5.1, actiivity data is retrieved into an sqlite database.  Becuase I think it is important to allow individuals to be in control of their own data, and that they should have the ability to analyse it themsleves, I have chosen to store data in a KEXI compatible database.  This will allow you to copy the database from the phone, and open it up inside KEXI on Linux/Windows/Mac and perform queries and reports on it.  This added ability means i link to a couple of KDE libraries, which should be installed automatically.

Firmware Download - READ FIRST - I am not liable if you brick your watch ;)

Read this for info about which files to flash https://github.com/Freeyourgadget/Gadgetbridge/wiki/Amazfit-Bip-Firmware...

App has been tested using an amazfit bip, downloading the latest (0.1.1.45) official firmware.

The firmware is split into multiple files on these devices.  With the official MiFit app, all are downloaded at once, and everything works fine.  With this app, you have to send each file individually.  The firmwares are available by extracting the MiFit apk, and looking in the assets/ folder for files named Mili_chaohu.*.  When you select a file, its type and version will be determined, and you will be prevented from sending invalid files.

The firmware (.fw) requires a matching resource (.res).  Send the firmware first, the app will send a reboot command at the end of the transfer, and the watch will boot up into a mode where it needs the matching resource sent.  Just wait for the app to connect again, then send the resource. 

The following types of file exist:

firmware, resource, a-gps data, fonts

Pairing Issues

Pairing works for myself, sometimes I have to try twice.  If pairing doesnt work at all, then try:

  • keep the app open, and pair again in the BT settings page of sailfish
  • in the sailfish BT settings page, delete all entries and try again
  • turn off/on BT on the phone
  • factory reset the watch

Check if after all this, pairing works from the sailfish BT settings page.  It should pair and connect just fine from there.  f that doesnt work, my app wont either.

Not all features currently implemented

***May not work on all devices***

Uses Bluetooth Low Energy to communicate with the watch, this is known to be problematic on some devices.  it is known to work on the Xiaomi Mido.  Probably also works on the FP2.  Official devices unknown.

Implemented

  • Pairingfrom
  • Notifications
  • Calls
  • Some settings
  • Retrieving activities
  • Heartrate Chart
  • Alarms
  • Watchface download
  • Firmware upload
  • Activity Sync

Todo

  • More Settings
  • Support other devices (maybe eg MiBand2, as it is similar)

The Cor is also claimed to be working, but as i dont have that device, i cant test it.

Tip:
On your device, create a symlink in /home/nemo to /home/nemo/.local/share/harbour-amazfish
This way, you can easilty copy the database off the phone using MTP.

Source: https://github.com/piggz/harbour-amazfish

Credits to:

  • The rockpool devs, as i borrowed the call handling code handling code from them
  • The gadgetbridge devs, which gave me a lot of hints and inspiration from theire device code.
Screenshots: 
Application versions: 
AttachmentSizeDate
File harbour-amazfish-0.1-1.armv7hl.rpm112.29 KB17/04/2018 - 23:12
File harbour-amazfish-0.2-1.armv7hl.rpm119.54 KB28/04/2018 - 00:35
File harbour-amazfish-0.3-1.armv7hl.rpm131.01 KB07/05/2018 - 23:54
File harbour-amazfish-0.4-1.armv7hl.rpm137.54 KB18/05/2018 - 23:22
File harbour-amazfish-0.4.1-1.armv7hl.rpm137.63 KB20/05/2018 - 00:15
File harbour-amazfish-0.4.5-1.armv7hl.rpm148.71 KB22/05/2018 - 22:02
File harbour-amazfish-0.4.6-1.armv7hl.rpm149.08 KB22/05/2018 - 22:55
File harbour-amazfish-0.4.7-1.armv7hl.rpm149.42 KB24/05/2018 - 00:35
File harbour-amazfish-0.5.1-1.armv7hl.rpm158.56 KB30/05/2018 - 00:22
File harbour-amazfish-0.5.5-1.armv7hl.rpm164.27 KB02/06/2018 - 22:11
File harbour-amazfish-0.5.8-1.armv7hl.rpm168.1 KB04/06/2018 - 21:07
File harbour-amazfish-0.5.9-1.armv7hl.rpm170.27 KB05/06/2018 - 22:24
File harbour-amazfish-0.6.0-1.armv7hl.rpm171.68 KB06/06/2018 - 00:17
File harbour-amazfish-0.6.5-1.armv7hl.rpm179.96 KB23/06/2018 - 11:28
File harbour-amazfish-0.6.7-1.armv7hl.rpm185.47 KB26/06/2018 - 21:55
File harbour-amazfish-0.6.8-1.armv7hl.rpm186.04 KB28/06/2018 - 21:19
File harbour-amazfish-0.7.0-1.armv7hl.rpm238.07 KB15/07/2018 - 12:13
File harbour-amazfish-0.7.1-1.armv7hl.rpm237.48 KB19/07/2018 - 16:51
File harbour-amazfish-0.7.3-1.armv7hl.rpm239.17 KB23/07/2018 - 23:19
File harbour-amazfish-0.7.5-1.armv7hl.rpm673.84 KB26/08/2018 - 11:02
File harbour-amazfish-0.8.0-1.armv7hl.rpm673.94 KB25/11/2018 - 16:33
File harbour-amazfish-0.8.1-1.armv7hl.rpm674.27 KB29/11/2018 - 00:32
File harbour-amazfish-0.8.2-1.armv7hl.rpm674.21 KB01/12/2018 - 16:29
File harbour-amazfish-0.8.5-1.armv7hl.rpm679.46 KB12/01/2019 - 18:02
File harbour-amazfish-0.8.7-1.armv7hl.rpm681.18 KB23/01/2019 - 01:38
File harbour-amazfish-0.8.8-1.armv7hl.rpm681.32 KB04/04/2019 - 20:58
File harbour-amazfish-0.8.9-1.armv7hl.rpm682.44 KB05/04/2019 - 01:11
File harbour-amazfish-0.9.0-1.armv7hl.rpm703.9 KB18/05/2019 - 00:30
File harbour-amazfish-0.9.1-1.armv7hl.rpm702.06 KB21/05/2019 - 22:37
File harbour-amazfish-0.9.2-1.armv7hl.rpm703.2 KB12/06/2019 - 23:28
Changelog: 

0.9.2
Stop notification when call answered
Fix sending weather on interval
Add more languages for watch (only works if supported by FW)

0.9.1
Fixed crash for new users
Weather UI fixes
Whitelisted some more firmware
Translation updates
Bugfixes for daemon/ui split

0.9.0
***ONLY FOR SAILFISHOS >= 3.0.3***
Daemon/UI split
Reworked some pages to streamline them

0.8.9
Add buffer for 10 notifications when watch disconnected

0.8.8
Added deep sleep value to page
Save GPX files in data location not cache location
May install on SFOS 3.0.3 when available

0.8.7
New UI layout
Sleep statistics

0.8.5
Added step summary chart showing steps over previous 20 days from the selected day
Added auto-sync of activity data which occurs each hour

0.8.2
Fixed applying settings from the UI

0.8.1
Hopefully fixed crash introduced in 0.8.0

0.8.0
Major code restructure to better allow support for other devices (devs needed!)
Whitelist new Bip frmwares
Hopefully fixed GPS issue with new firmwares

 

0.7.5
Implemented sending weather
Fixed app displaying correct status when watch disconnects
Use correct icon for depecher
Fix layout of HR button

 

0.7.3
Updated translations
Fixed user profile settings page not opening

Comments

dalas_revo's picture

No, I think your instruction is clear enough, people just have to follow it ;)
Maybe you could add a hint not to mix Latin and non-latin files, but in general I think it should be clear...

Reflashing did only work after deleting the watch in the BT section of SFOS settings, but finally flashing non-Latin font did the trick! Thank you very much!

dalas_revo's picture

Very nice app! Thank you!
Finally a usable smartwatch on sailfish :) Unfortunately I managed to bring my device into a more or less unusable state ( not bricked). First I flashed latest fw ( doesn't recognize the one with ending "latin" as fw) and res (latin), which worked very well. Afterwards I flashed latin fonts. Now the Bip always displays "Connect APP to update" and I can't get it out of this state. Reflashing firmware and ressources doesn't help.
I's there anything I can do to get it working again?
I am using it on an XA2, amazfish 0.8.1, as 0.8 always crashed at startup

piggz's picture
piggz's picture

Oh, sorry you got in such a state.  Could you try flashing the 3 non latin files, firmware, Res and font.

 

Failing that, can you use an android device to use mifit to do the flash?  I probably need better instructions on what to flash and which order!

Caluna's picture

Hi piggz,

I am also trapped in the "Connect to update" loop. Tried tore-flash different firmwares (from 0.1 to 1.1.5)  without much success. Additionally, Mi-Fit app on Android does not help as pairing fails. Do you have any other ideas?

Best

C.

piggz's picture

you need to srnd thr matching firmware and res, and.possibly font file. hopefully amazfish can still connect and send the files? all i can suggest is what is in the gadget bridge wiki, good luck

Caluna's picture

Hi Piggz,

I think, the device is bricke and stuck in a state that cannot be recovered: The files are sent in the correct order (as suggested in the wiki), but at the end of the transfer of the respective files I always end up with the message "connect to app to update" and connection to the phone is lost. I have to re-pair using Amazfish and can connect again. The connection request on the device pops up and I can agree and connection can be established. But still: the device does not "boot".  

Mi Fit on Android sends connection request, but when I agree, it says that the connection request cannot be sent.

 

piggz's picture

doesnt sound dire if you can still connect and send files. persist, try older, or try gadgetbridge

Caluna's picture

Tried a lot without any success: Gadgetbridge says, that there is a problem with transfer of metadata. "Google" provides not a real answer to this...

piggz's picture

you are trying all the non latin files,.3 of?

Caluna's picture

Yes: tried just the non-latin files, also in different order (fw first, res first gps first). FW Versions: 1.1.5.02, 1.1.5.04, 1.0.1.00, 0.0.9.40

All ends up with the same result

Caluna's picture

Finally, the problem has been solved "automatically": Somehow the firmware got stuck (I think). I had to wait till the device shut off due to low battery, load it and restart. Afterwards I had to install firmware again using official Mi-fit app on an Android deviced. Now, everything works again like a charm...

cartron's picture

One thing i just noticed: alarms are not synchronized to the watch. Actually i have one alarm which got pushed (happening on Mon, Tue, Thu, Fri) but whenever i try to add / enable other alarms, the watch shows me the other alarms as '0:00 tomorrow / disabled'
And modifying the alarm which got pushed does not work either

dalas_revo's picture

I cannot push any alarms, too. The output which is relevant here (I guess) is

[W] unknown:112 - file:///usr/share/harbour-amazfish/qml/pages/Settings-alarms.qml:112: TypeError: Property 'applyDeviceSettings' of object DeviceInterface(0xffb392f8) is not a function

piggz's picture

Ah, great, thanks for the console output, a remainder of the major restructure.

cartron's picture

Will you fix it in thr next release? :)

meemorph's picture

On startup
harbour-amazfish
[D] unknown:0 - BluezAdapter::BluezAdapter
[D] unknown:0 - Registered notifications listener for device
[D] unknown:0 - BluezAdapter::setAdapterPath: "/org/bluez/hci0"
[D] unknown:0 - DRIVERS: ("org.kde.kdb.sqlite")
[D] unknown:0 - KDbConnection object created.
[D] unknown:0 - KDbConnection::connect() OK.
[D] unknown:0 - ("mi_band_activity", "sports_data")
[D] unknown:0 - VoiceCallsChanged
[D] unknown:0 - ActiveVoiceCallChanged
[D] unknown:0 - BluezAdapter::BluezAdapter
[D] unknown:0 - Using Wayland-EGL
library "libwlparser.so" not found
Segmentation fault (core dumped)

meemorph's picture

0.8.0 gives segmentation fault on geminipda with 3.0.0.8. Had to go back to 0.7.5-1.

piggz's picture

Are you doing anything specific to cause the crash or does it happen on startup?

marxistavegana's picture

It is giving me a segfault on sfos3.

piggz's picture

Are you doing anything specific to cause the crash or does it happen on startup?

Its working for me, but I didnt do a clean run, ie, with no pairing.  I will check that.  there were a lot of changes in 0.8.0 so i potentially missed something.

 

Can you post logs from running in a console to github?

cartron's picture

Hi, on which device? I upgraded my Xperia X yesterday to 0.8.0-1, and it works perfectly. Haven't tried yet running to see whether GPX files are OK now, but the rest works fine

cartron's picture

One cool feature I am missing from Rockpool/Pebble: the ability to select which applications can send notifications to the watch.

e.g. having Spotify sending me a notification on my wrist every time the song changes, is a bit annoying! ;)

cartron's picture

Hi @piggz, thanks for Amazfish, it works like a charm for connection with my Amazfit Bip - which I bought just because you created this software for SailfishOS :)

I was about to tell you that I had issues with the GPX from the first run I did with the Amazfit today - completely wrong, 25KM instead of the 11K I did - the overall trace is fine, but the GPX starting point is like 10 KM away from my real starting point.

I saw that you released version 0.8.0-1 today, I will update and will try it with my next run to see.

Thanks again!
Nico

piggz's picture

Thanks, let me know if it works.  Ive heard from someone else that it does.

cartron's picture

will try tomorrow! :)

anyway to try again downloading from the watch? I removed the .gpx file in ~/Laufhelden, but it seems there's a cache somewhere, as Amazfish tells me there's no more run to download

cartron's picture

@piggz i confirm GPX file is no longer corrupted, thanks!

rsw75's picture

No new features that I've seen, and the one unofficial set of release notes I saw just said 'bug fixes'. I've recorded a couple more workouts to play with this evening. Will updatel later

rsw75's picture

Possibly co-incidentally but my two runs after amazfit bip had firmware update to 1.1.5.04 have had the gpx files corrupt in the same style. Run shows going due North, then due East for about the total distance run. The route run is then captured at this mystery location. I can edit the gpx file to get rid of the extra straight lines, but the run remains in the wrong location. Any ideas?

piggz's picture

interesting, i can see how that can happen, not helped by the way the damn bip sends its data. the way the datastream works is to send an initial location/time, and all points after that are sent as offsets from the previous point. so, if the first point is wrong, they all will be.

 

 

 

is it wrong by location and time, or just location?

 

 

 

im running 1.1.1.0.0 and used the gps this weekend and it was fine. perhaps they changed something.  please test more and raise an issue on github. any other new features?

Pages