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

timeral's picture

Great work.
Any plan for amazfit verge lite?

aerique's picture

First of all: thanks for your great work!

Pairing is a pain in the ass, but once it works it's awesome.

Secondly, for me "Sync activity data every hour" does not seem to work. (This is on an XA2 device.)

Mariusmssj's picture

Hello,

Been having real issues connecting back the watch after a phone reboot, my procedure after reboot:

- Using phone settings connect to the amazfit bip via bluetooth

- Phone says connected and watch says connected

- Open the app and pull to option "Connect to watch", the "Start service" button apears for 5 seconds and then dissapears

- This is the output from journalctl:

[root@Sailfish nemo]# journalctl | grep amazfish
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - Starting amazfish daemon
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - BluezAdapter::BluezAdapter
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - amazfish-daemon: succesfully registered to dbus sessionBus
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - Registered notifications listener for device
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceFactory::createDevice: requested device of type: ""
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceFactory::createDevice: no suitable devices found, creating a Bip device as default
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - BluezAdapter::setAdapterPath: "/org/bluez/hci0"
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DRIVERS:  ("org.kde.kdb.sqlite")
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - Database is:  "/home/nemo/.local/share/harbour-amazfish/harbour-amazfish/amazfish.kexi"
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - KDbConnection object created.
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - KDbConnection::connect() OK.
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - ("mi_band_activity", "sports_data")
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - VoiceCallsChanged
Jul 01 07:34:19 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - ActiveVoiceCallChanged
Jul 01 07:35:01 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - no notification service, buffering notification
Jul 01 07:35:20 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceInterface::onRefreshTimer
Jul 01 07:36:20 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceInterface::onRefreshTimer
Jul 01 07:37:20 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceInterface::onRefreshTimer
Jul 01 07:38:20 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceInterface::onRefreshTimer
Jul 01 07:39:03 Sailfish i[7294]: [D] unknown:0 - Database is:  "/home/nemo/.local/share/harbour-amazfish/harbour-amazfish/amazfish.kexi"
Jul 01 07:39:04 Sailfish lipstick[4099]: [D] onCompleted:263 - coverActionIndicators created harbour-amazfish-ui.desktop
Jul 01 07:39:18 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - DeviceInterface::connectToDevice: ""
Jul 01 07:39:18 Sailfish harbour-amazfishd[4858]: [D] unknown:0 - QBLEDevice::setDevicePath
Jul 01 07:39:18 Sailfish harbour-amazfishd[4858]: process 4858: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed
in file dbus-message.c line 1367.
Jul 01 07:39:18 Sailfish harbour-amazfishd[4858]: This is normally a bug in some application using the D-Bus library.
Jul 01 07:39:18 Sailfish harbour-amazfishd[4858]: D-Bus not built with -rdynamic so unable to print a backtrace
Jul 01 07:39:18 Sailfish systemd[3414]: harbour-amazfish.service: Main process exited, code=killed, status=6/ABRT
Jul 01 07:39:18 Sailfish systemd[3414]: harbour-amazfish.service: Unit entered failed state.
Jul 01 07:39:18 Sailfish systemd[3414]: harbour-amazfish.service: Failed with result 'signal'.
Jul 01 07:39:23 Sailfish systemd[3414]: harbour-amazfish.service: Service hold-off time over, scheduling restart.
Jul 01 07:39:23 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - Starting amazfish daemon
Jul 01 07:39:23 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - BluezAdapter::BluezAdapter
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - amazfish-daemon: succesfully registered to dbus sessionBus
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - Registered notifications listener for device
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - DeviceFactory::createDevice: requested device of type: ""
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - DeviceFactory::createDevice: no suitable devices found, creating a Bip device as default
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - BluezAdapter::setAdapterPath: "/org/bluez/hci0"
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - DRIVERS:  ("org.kde.kdb.sqlite")
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - Database is:  "/home/nemo/.local/share/harbour-amazfish/harbour-amazfish/amazfish.kexi"
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - KDbConnection object created.
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - KDbConnection::connect() OK.
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - ("mi_band_activity", "sports_data")
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - VoiceCallsChanged
Jul 01 07:39:24 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - ActiveVoiceCallChanged
Jul 01 07:39:49 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - DeviceInterface::connectToDevice: ""
Jul 01 07:39:49 Sailfish harbour-amazfishd[7579]: [D] unknown:0 - QBLEDevice::setDevicePath
Jul 01 07:39:49 Sailfish harbour-amazfishd[7579]: process 7579: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed
in file dbus-message.c line 1367.
Jul 01 07:39:49 Sailfish harbour-amazfishd[7579]: This is normally a bug in some application using the D-Bus library.
Jul 01 07:39:49 Sailfish harbour-amazfishd[7579]: D-Bus not built with -rdynamic so unable to print a backtrace
Jul 01 07:39:49 Sailfish systemd[3414]: harbour-amazfish.service: Main process exited, code=killed, status=6/ABRT
Jul 01 07:39:49 Sailfish systemd[3414]: harbour-amazfish.service: Unit entered failed state.
Jul 01 07:39:49 Sailfish systemd[3414]: harbour-amazfish.service: Failed with result 'signal'.
Jul 01 07:39:54 Sailfish systemd[3414]: harbour-amazfish.service: Service hold-off time over, scheduling restart.
Jul 01 07:39:54 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - Starting amazfish daemon
Jul 01 07:39:54 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - BluezAdapter::BluezAdapter
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - amazfish-daemon: succesfully registered to dbus sessionBus
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - Registered notifications listener for device
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - DeviceFactory::createDevice: requested device of type: ""
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - DeviceFactory::createDevice: no suitable devices found, creating a Bip device as default
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - BluezAdapter::setAdapterPath: "/org/bluez/hci0"
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - DRIVERS:  ("org.kde.kdb.sqlite")
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - Database is:  "/home/nemo/.local/share/harbour-amazfish/harbour-amazfish/amazfish.kexi"
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - KDbConnection object created.
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - KDbConnection::connect() OK.
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - ("mi_band_activity", "sports_data")
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - VoiceCallsChanged
Jul 01 07:39:55 Sailfish harbour-amazfishd[7622]: [D] unknown:0 - ActiveVoiceCallChanged

 

 

 

What am I doing wrong?

fravaccaro's picture

Is support for Mi Band 4 planned?

piggz's picture

I have designed the app to allow more devices to be supported, but without a dev with such device, or a sponsor device then I cant really add support for it 'blind'.  If you have any coding skills, feel free to dig around and ask questions though

Mariusmssj's picture

Hello, every 30 minutes or so I am getting a notification from the app saying "Phone and watch are connected". Is this normal? I never used to get it before

[EDIT:] I realised this only happens when I get far away from the phone and come back close to it, so this means that when it loses and gains back the connection to the watch it provides a notification.

piggz's picture

Yes, thats as per design. you can turn off the notification in app settings if you wish

Mariusmssj's picture

Ahhh thank you, I didn't even see that :)

Mariusmssj's picture

Is anyone else having a bug where when you asnwer thew phone call on the phone but the watch is still vibrating with call notifiation as if you haven't picked up the phone?

zepher's picture

Yep, that happens for me too. i have to press 'ignore' after answering call to stop my wrist buzzing!

Mariusmssj's picture

It's rather annoying to be honest

piggz's picture

yes yes, ive not implemented the auto-muting of the call notification, it will come.

Mariusmssj's picture

Thank's for the support and working on such a great app :)

D_R's picture

I forgot to tell: I'm using a XA2 too with last Hossa 3.9.3.10

MartiMasa's picture

I have/had exactly the same problem so I decided to completely remove Amazfish from my XA2 and then reinstall it. Reinstalling fails now due to missing ”alienaudioservice-0.3-1.2.60.jolla.armv7hl.rpm” in SFOS 3.0.3.10. So please do not remove Amazfish before this is fixed! UPDATE: I was now able to reinstall the app on XA2 after refreshing cache & restarting phone. However, the „No data to transfer” error persists but notifications, HRM and step-counts work just fine.

Mariusmssj's picture

Is anyone else having issues with getting the weather working? I tried setting the location multiple time but it doesn't seem to work.

seiichiro0185's picture

I seem to have the same Problem. Just got an Amazfit Bip, and Setting the Weather Location just resets as soon as I leave the Settings page. Also no Weather is send to the watch.

Everything else works nicely so far (after the first day of use), so thanks a lot for this great App @piggz !

Mariusmssj's picture

It is odd as it does find the city and you can select it, but once you leave the menu it just gets cleared

seiichiro0185's picture

Interesting discovery I made today: Restarting the daemon does lead to weather being send to the watch. Also the city seems to be saved in ~/.config/harbour-amazfish/harbour-amazfish/config.json The settings page is still empty though.

Mariusmssj's picture

Ahh I see, by restarting the daemon you mean just stop the service and start it again from the app?

piggz's picture

I should maybe point out that installing a new version currently doesnt restart the service, so, you should do it manually after an update for the update to take effect!

seiichiro0185's picture

@Mariusmssj: Yes, i simply stopped and started the service from the settings page, after that Weather started working on the watch.
@piggz: In my case there was no update involved. Its a new install of 0.9.2, since I just got the Bip last friday.

Mariusmssj's picture

Did you have to pair the phone again? For me after stoping and starting the service it would not connect back to the phone and I had to go through the paring process again.

seiichiro0185's picture

It didn't connect by itself, but using the "Connect to Watch" (don't know exact wording here in English, my Phone is in German) entry in the Pulley Menu was enough, I didn't have to do the pairing again. Maybe it would have reconnected by itself after some time, didn't try that.

Termitebug's picture

Can't install Amazfish to latest Hossa. Jolla is missing from 3.0.3.10 Sony-nile repository alienaudioservice package required by Amazfish .rpm

D_R's picture

I'll get always no data to transfer popup and no data in the charts.... I get only the actual value for steps. On the side with the 3 charts I get no data to transfer popup always...

zepher's picture

I am having a similar issue as D_R, the first time I connected it did update data but since that time additional days are shown mostly as blank (no data) and for one day the plots just look strange, heart rate is shown as a broad line. There are no reported errors on data transfer and phone <--> watch comms seem fine in the debug menu. I am on firmware 0.1.1.4.5

piggz's picture

The graphs work, its just not auto-downloading the data, you have to keep manually downloading until there is no data left

zepher's picture

Ah, I see. can get data now. it seems to only get heart rate for a couple of days in the last few weeks, perhaps I have set up something wrong with the heart rate recording interval. thanks for all your work on this app!

D_R's picture

I downgraded to firmware 1.1.5.12. Same behaviour : pairing and connecting is okay but the values are not shown in the charts. It seems that nothing is written or read from to the database...

Pages