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 ;)

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.

With the latest update I can install Amazfish correctly, but unfortunately it doesn't pair with the watch. I can click the 'enable service', but the 'start service' never goes away, and then the pairing process never completes.

After updating my phone to Sailfish 3.0.3.8 and re-installing Amazfish like described below, Amazfish doesn't seem to find my miband 3 anymore. From bluetooth-settings the phone will easily connect to the band, but Amazfish just seems empty. When I try to pair with the band it starts a scan, doesn't show anything and just tells me the scan stopped after a while (I can either connect it via settings-> bluetooth or not, no change in amazfish).

When I'm trying to install the application, I get the message "problem with installing", any tips on how to fix that?

My steps:

- Download the latest RPM from this page
- With "File Browser" open the downloads folder in which the RPM is downloaded
- Open the RPM-file
- Drag down the pull-menu from the top, click install
- Receive the notification "problem with installing"

I'm getting the message both on my Jolla1 and my Xa2 normal, single sim. Both updated to the latest Sailfishes. On both phones installing applications from non-trusted sources is enabled.

Hello! Thanks for the app! So I have a weird issue: I have the Bip one, I didn't change the firmwire, and an XA2. But I can connect the watch to SfOS and the app. Everything was working well. But now I cannot send the test notifications on my watch from the app. But I can still see all the debug info on the app! So looks like it's connected but can't communicate for some reason. And yeah, I don't have any notifications on my watch but the app gives me the correct number of steps though! If someone had face the issue and already figured out a solution, don't hesitate to tell me :) In any case, thanks a lot for working on this app!!!

thanks for the work!!!!! The app runs without any crash and stable. Only the weather sync is sometimes a bit strange. Sometimes the data on the watch seems to be good, another time all weather data for

actual temp

maximum temp

minimum temp

are the same and are not plausible. What weather source have You implemented? The temperatures are not the same like in Sailfish-Weather

On newest Sailfish XA2 version (3.0.1.14) I have a strange behaviour: The App connects for a first time, but if I lose Bluetooth connection (e. g. when I am out of range), the connection is not re-established. If I try to re-connect manually (Connect to watch) I gt the message, that the device is not valid and may not be supported.