Donations: https://paypal.me/piggz
Companion application for Huami Devices (such as Amazfit Bip, Cor, MiBand2/3 and GTS and GTS), Pinetime Infinitime and Bangle.js.
This application requires several supporting packages. Until Aug 2021, these were available on openrepos for the latest SailfishOS release. Updating these libs is a big pain, so they have now moved to SailfishOS::Chum. If you dont know what that is, read this https://build.merproject.org/project/show/sailfishos:chum:testing
To install Amazfish, first install the "chum" repository from the link above and "pkcon refresh" then install Amazfish.
I apologise about thie extra step, but it makes updates much easier. Pacakges in chum are automatically built for each SailfishOS release and instantly available. In the future, Amazfish may also be distributed this way, but for now, it can still be installed from here, for the current SailfishOS release.
If you already have Amazfish installed, and need to update, you will also need chum, but you may have to drop to a command line and "zypper dup" and accept and changes to the package vendor.
There are 3 tiers of supported devices:
These are devices I have, have tested and will try not to break any functioanlity for an include:
* Amazfit Bip
* Amazfit GTS
* Pinetime Infinitme
* Bangle.js
These are devices which are properly implemented in the application, but I do not have and are tested by the commuity, and include:
* Amazfit BipS
* Amazfit Bip Lite
I do not promise not to break funcaionality in these, but will fix where I can
These are devices which use a protocol that is close to another suppored device, and so is treated like that device. Your mileage may vary with these devices.
* MiBand 2/3/4
* AMzfit Cor
* Amazfit GTR
Amazfish needs to be built on OBS against a defined set of libraries. Becuase there is a delay between a Sailfish release and that release being available on OBS, there will be a delay to supporting the latest versions.
For releases of the current version built against other Sailfish releases, use the repositories at :
https://build.merproject.org/project/show/home:piggz:harbour-amazfish and
https://build.merproject.org/project/show/home:piggz:kf5
The new sport display feature requires the MapBox component. The easiest way to get this is by installing PureMaps from rinigus repository.
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 and GTS, 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 fotn (.ft) and 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 font and resource sent. Just wait for the app to connect again, then send the font and resource.
The following types of file exist:
firmware, resource, a-gps data, fonts
So, to re-iterate, the firmware flashing order is:
The newer devices (GTS, BipS etc) requires a server-side pairing key which requires inital pairing with an android device. To get the key, follow the instructions here and enter into Amzafish when prompted, WITHOUT 0x at the beginning.
See https://codeberg.org/Freeyourgadget/Gadgetbridge/wiki/Amazfit-GTS
AGPS Download/Transfer
The official amazfit app can download and transfer the AGPS files to the watch automatically. The amazfit web site limits download of the files to those with accounts. A python script has been developped that can download the AGPS files, these can then be transferred to your phone, and downloaded to the watch using the normal "Download File" option.
Pairing Issues
Pairing works for myself, sometimes I have to try twice. If pairing doesnt work at all, then try:
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
Todo
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.
Bip and GTS notify when the watch button is pressed. This is captured by amazfish which allows running actions on theses presses. An action can be ran on 2,3 or 4 presses. To confiure the actions, goto Settings > Application > Button Actions.
A custom script can be used, the script must be called harbour-amazfish-script.sh and be in the home folder. Example which sends a OTP code to the watch as a message:
#!/bin/sh if [ "$1" == "4" ]; then CODE=`python3 -c 'import pyotp;totp = pyotp.TOTP("XXXX Authenticator code here XXXX");print(totp.now())'` dbus-send --session --print-reply --dest=uk.co.piggz.amazfish /application uk.co.piggz.amazfish.sendAlert string:'' string:'Google OTP' string:$CODE boolean:true fi;
Source: https://github.com/piggz/harbour-amazfish
Credits to:
2.0.3
2.0.2 - Now for 4.1
2.0.0 (incl unreleased 1.9.9)
1.9.8
1.9.7
1.9.6
1.9.5 (includes unreleased changes for otehr distros)
1.9.0
1.8.7
1.8.6 (not release for sailfish)
1.8.5
1.8.2
1.8.1 - Includes 1.8.0 which was skipped
1.7.1
1.7.0
1.6.8
1.6.7
1.6.6.
1.6.5
1.6.1
1.6.0
1.5.6
1.5.5
1.5.1
1.5.0
1.4.5
1.4.0
1.3.1
1.3.0
1.2.0
1.1.3
1.1.2
1.1.1
1.1.0
1.0.0
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
Branja
Thu, 2019/12/05 - 10:33
Permalink
Amazing! I know it's a noobish question but, how can I do that?
edit: I successfully connected Mi Band 2 but I still can't connect BIP Lite. It says authfailed. I read about it online a little bit (on the Gadgetbridge wiki) and it turns out that all the newer devices, including BIP Lite, need an official app in order to pair because they require a server-based pairing. Now, there is an easy way to obtain a pairing key on an Android-based phone via a cracked Mi Fit app. Is there a way that You can implement pairing keys into your app or should I sell my BIP Lite and order an original BIP watch? p.s. Sorry for bothering you and demanding certain things. I am just a noob who feels love for this kind of technology. I will help you out however I can.
piggz
Thu, 2019/12/05 - 14:18
Permalink
ive just read up on server based pairing, and i should be able to implement it, but you will have to expect to wait a little while.
Branja
Thu, 2019/12/05 - 15:16
Permalink
Not a problem, kind sir. I will wait as long as it takes. Please, let me know if I need to test something out.
alex000090
Sun, 2019/11/24 - 09:37
Permalink
Good morning!
I try flash new firmware for watch, but when I open FW.latin file (first), the program write "Invalid" in type string. I use last version of the program.
Branja
Tue, 2019/11/19 - 22:46
Permalink
Guys, I am planning to buy a Sony Xperia XA2 and an Amazfit BIP Lite. Can somebody confirm that these two will work together?
jpn9s
Fri, 2019/11/22 - 09:42
Permalink
I can confirm that Amazfit Cor with Amazfisf app works quite well in my XA2 Sfos 3.2.0.12. I suppose Cor might be quite near Bip, but I do not know Bip Lite.
Branja
Mon, 2019/12/02 - 12:32
Permalink
Thank you for your reply. I am a bit worried because I read that those new devices (BIP Lite, Mi Band 4, Amazfit GTR) require a server-based paring at first. This means that one needs to pair either of these devices with a Mi Fit app and then obtain a pairing key (at least, that's the case on Android). I ordered an Amazfit BIP Lite, and I want to buy an Xperia XA2 and to run Sailfish on it. I would be hugely disappointed in case I cannot do that, and that I need to return to Android.
foffo
Wed, 2019/10/02 - 22:06
Permalink
ronny_b
Mon, 2019/09/30 - 20:34
Permalink
I no longer get my AmazfitBIP paired. Amazfish runs on the XperiaX with Sailfish 3.1.0.11. The clock is displayed in the Bluetooth settings under paired devices. It is also found by the app and the following text is displayed:
Connecting to watch...
/org/bluez/hci0/dev_F0_1A_...
pairing
That's all there is to it.
What have I already tried...
- Switch Bluetooth off and on again
- In the settings of the "Stop and Start Service" app
When I connect the clock in the shell via bluetoothctl, I get the following:
[Amazfit Bip Watch]# info F0:1A:...
Device F0:1A:... (random)
Name: Amazfit Bip Watch
Alias: Amazfit Bip Watch
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Vendor specific
Besides, the clock now shows connected, only the app unfortunately does not.
Here is an excerpt from the journal:
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - BluezAdapter::stopDiscovery
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - BluezAdapter::StopDiscovery: ""
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - BluezAdapter::matchDevice:looking for: "Amazfit"
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - Found: QVariant(QString, "Jolla-xxx")
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - Found: QVariant(QString, "Xperia X")
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - Found: QVariant(QString, "Amazfit Bip Watch")
Sep 30 19:07:19 Sailfish i[5258]: [D] unknown:0 - BluezAdapter::deviceName:looking for: "/org/bluez/hci0/dev_F0_1A_..."
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - DeviceInterface::pair: "Amazfit Bip Watch" "/org/bluez/hci0/dev_F0_1A_..."
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - DeviceFactory::createDevice: requested device of type: "Amazfit Bip Watch"
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - QBLEDevice::setDevicePath
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - true
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - AbstractDevice::pair
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - DeviceInterface::onConnectionStateChanged "pairing"
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - DeviceInterface::onConnectionStateChanged "pairing"
Sep 30 19:07:19 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - QBLEDevice::pair
Sep 30 19:07:19 Sailfish i[5258]: [D] pair:102 - Pair result:
Sep 30 19:07:19 Sailfish i[5258]: [D] expression for onConnectionStateChanged:202 - pairing
Sep 30 19:07:19 Sailfish i[5258]: [D] expression for onConnectionStateChanged:202 - pairing
Sep 30 19:08:00 Sailfish harbour-amazfishd[5654]: [D] unknown:0 - DeviceInterface::onRefreshTimer
What else can I try? On the PC with Android emulator and "Gadgetbridge" it can be connected without problems.
Thanks Ronny
piggz
Wed, 2019/10/02 - 22:46
Permalink
Does the device mac address match in all cases? You could try fully resetting the application with
dconf reset -f /uk/co/piggz/amazfish
ronny_b
Sat, 2019/10/05 - 17:41
Permalink
Thanks for the answer. I reserve that as my last option.
I have tried pairing the phone with another device. After I have removed this connection, the Amazfish app connects automatically. Unfortunately, the activity data does not arrive completely in the database. After about 25 hours no more lines are created in the Kexi-file and nothing is displayed in the diagram. In the home directory 7.4GB are still free.
So I probably can't get around it...
Ronny
piggz
Sat, 2019/10/05 - 19:39
Permalink
Yeah, i have a known issue with how times are saved for the last sync, ill be working on it soon
EEvnos
Mon, 2019/09/30 - 20:06
Permalink
This is amazing software and works VERY well.
The one issue I'm having is that when setting the Distance Unit to Imperial (under Device Settings) it does not seem to save the settings.
The settings on the watch don't change and the app is defaulted back to Metric when going back into the settings.
piggz
Wed, 2019/10/02 - 22:43
Permalink
Thanks for the feedback. Could you you rasie an Issue on github?
localhorst
Thu, 2019/09/19 - 09:33
Permalink
mugshot
Mon, 2019/09/16 - 13:48
Permalink
The sleep data seems to be not working... Claims I've slept from 15.9. to 24.9. ~14 hours each night and today is 16.9...
Okerampa
Wed, 2019/08/07 - 16:34
Permalink
Hello, I have a strange issue where I factory reset the watch, then update with mii (latest version), then amazfish seems not to connect... So I removed the pairing and tried again.
But then, the phone is in a loop (seems infinite) when I try to pair with bluetooth settings... And in amazfish, even if I unpaired it tries to connect to the watch, not seeing there is nothing paired.
Is there a way to force remove the watch in amazfish ? Or is it linked to paired devices and I have a bug with sailfish last version (I'm on 3.1 on xperia X)
Thanks...
slava
Sun, 2019/07/28 - 19:52
Permalink
slava
Mon, 2019/07/29 - 00:25
Permalink
I mean, if I spent a bit more time on it, I would probably find rpm providing libKDb3.so.4 or even built one myself but it would be so much friendlier if everything (which is not part of the platform) necessary to build and install the app would be in one package and one git repo... And if I could build and debug this thing myself, it would be so much more likely that I would contribute something. When I tried to build this thing in OBS it gave me
nothing provides kdb-devel >= 3.1.0, nothing provides kcoreaddons-devel >= 5.31.0"
. Bummer!piggz
Mon, 2019/07/29 - 17:21
Permalink
Lets talk in #sailfishos!
carmeloferso
Sun, 2019/07/28 - 16:34
Permalink
Can't install on XA2 running 3.1.0.11, log below:
carmeloferso
Thu, 2019/08/01 - 20:17
Permalink
app installed on 3.1.0.11 after:
pkcon refresh && pkcon install zypper
zypper refresh
Mariusmssj
Fri, 2019/07/19 - 17:59
Permalink
For those strugling to connect to the watch after a reboot what seems to work for me is:
nobodyinperson
Thu, 2019/07/18 - 08:36
Permalink
Yes, that seems to be the case:
https://together.jolla.com/question/8589/proper-bluetooth-le-support/?an...
Maybe you could put a little warning in the Amazfish description that it doesn't work for the Jolla 1 for now. With Mi Fit being uninstallable, the Bip rather degrades to a „dumbwatch” with a Jolla 1. Well, at least battery life will be at max :-)
nobodyinperson
Wed, 2019/07/17 - 22:30
Permalink
Is this supposed to work with a Jolla 1? No matter what I do, my freshly bought and via Mi Fit updated Amazfit Bip (FW 1.1.5.56) just won't show up even in Jolla Bluetooth settings... :-(
piggz
Wed, 2019/07/17 - 22:57
Permalink
i would giess the J1 doesnt support BLE if it doesnt even show in the BT settings .
timeral
Fri, 2019/07/12 - 15:10
Permalink
Great work.
Any plan for amazfit verge lite?
aerique
Thu, 2019/07/11 - 15:28
Permalink
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
Mon, 2019/07/01 - 10:29
Permalink
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
Mon, 2019/06/17 - 22:03
Permalink
Is support for Mi Band 4 planned?
Pages