Amazfish on C2 in combination with Pine Time

REPRODUCIBILITY: 100% (always)
OSVERSION: 5.0.0.43
HARDWARE: Reeder S19 Max Pro S - s19mps - s19mps - 1.0.0.30 - aarch64
UI LANGUAGE: Deutsch (user: de_DE, os: de_DE.utf8)
REGRESSION: not specified

DESCRIPTION:

I lost my GTS Watch and took a look on the supported devices by Amazfish and in the gold category there I found InfiniTime and bought such a device. As it arrived one week ago, I installed Amazfish via Chum in the latest version and the watch has the firmware version 1.14.1 … soon after the first successfull connection the watch retrieved some data, but then it starts to lose connection or no reconnect further possible. Sometimes it reconnects maybe after some minutes, sometimes after some hours or even after reboot or deactivating/reactivating bluetooth. Im Amazfish with German localization the UI stucks sometimes and gathering and saving and displaying data from watch is not everytime exact or possibke. When the app is in background sometimes it freezes and even restarting the app don’t help and I have to reboot or wait at last 1 hour and try again starting the app.

What can I do to troubleshoot the issue?

PRECONDITIONS:

STEPS TO REPRODUCE:

  1. Install Amazfish and pairing with InfiniTime
  2. Retrieving, saving and displaying data in Amazfish not accurate and not working every time
  3. Notofications are not received by the watch everytime, sometimes even when the devices ate showed as connected

EXPECTED RESULTS:

A steady connection of app and watch and receiving notifications and saving my data like steps and heart beat.

ACTUAL RESULTS:

Undisconnected devices and in the most time no notifications as the devices are not connected

MODIFICATIONS:

  • Patchmanager: no
  • OpenRepos: yes
  • Chum: yes
  • Other: none specified

ADDITIONAL INFORMATION:

Device Owner User: defaultuser
Home Encryption: enabled

the initial version of this bug report was created using Bugger 0.9.13+git2

This I could capture now with the console and the bluez5 tools … devices were connected, than I locked the screen of my Jolla C2 and after unlocking the phone again, the connection went lost … I already have utilized mcetool command for the disabling of the power saving, which one guy mentioned here in an similiar thread with Amazfish and disconnecting bluetooth when screen is locked

I wrote a review of PineTime: PineTime experience – Jozef Mlích

They are quite well supported in Amazfish, but not everything is working.
I have also experience with connectivity outages. The amazfish communicates via bluez. Its dbus interface doesn’t provide much options to address those issues.
I have seen some smartwatch/phone compatibility matrix. It was for asteroid os, but it shown that this is common issue.

Next, you should update to recent version of InfiniTime. I have seen freezing daemon when it tries to send incompatible messges. However I am not aware of reason to stay with old firmware.

PineTime currently doesnt provide API to download steps counter nor heartrate activity log. I have tried to implement sampling of it, but it is far from perfect.

Gold category means that changes are tested before merge on it and the quality of implementation should work at least the same as before.

3 Likes

btw right place to report bugs is at https://github.com/piggz/harbour-amazfish/issues

2 Likes

Thank you very much for your respond. I wrote the bug report here because I think there is a issue even with the stability of bluetooth on the C2 as I encounter meanwhile problems even with earbuds … I updated the watch to the newest firmware 1.15.0, but nothing changed in the behaviour … I will fill a bug report on GitHub too this week … the main goal of my report here was to get some information how I can troubleshoot the problem on my own as I don’t find any logs or tools where I can dive deeper …

Probably @piggz also reads this forum, but bugs of Amazfish should be tracked in Amazfish github.

Debuging of Amazfish issues can be done as follows:

  • Daemon outputs logs to systemd. If I remember correctly the command on Sailfish OS is: journactl --user -u harbour-amazfishd
    • To count number of reconnections: journalctl --user -u harbour-amazfish --since 00:00 |grep "Lost connection"
  • UI outputs errors into stdout/stderr
  • For debuging of bluez is probably right place bluetoothctl
  • For kernel journalctl -f or dmesg, but I am not expert in that area.
2 Likes

I was trying to get histogram of disconnections on my phone. And it doesn’t look that bad:

# journalctl --user -u harbour-amazfish --since 00:00 |grep  "Lost connection"| cut -c 8-9 | uniq -c
$ journalctl --since 00:00:00 |grep harbour-amazfish|grep "Lost connection"| cut -c 8-9 | uniq -c
# count|hour
      2 03
     10 05 # I was sleeping at 5 AM btw ;-D
      2 06
      3 07
      1 08
      1 09
# there are no Lost connections between 10-17h
# I have started the script at 5 PM, hence no data after that
1 Like

I have realized that SailfishOS have old systemd so you have to run journalctl |grep harbour-amazfish to filter amazfish events. I have also updated the “Lost connection” command above.

Btw Sailfish OS Cheat Sheet | Sailfish OS Documentation says that there is some bluez5-tracing package. I don’t have idea what it does.

I have created an patch to monitor number of (re)connections. See Added a counter to track the number of reconnections by jmlich · Pull Request #462 · piggz/harbour-amazfish · GitHub

I was curious about overall stability of BLE connection with PineTime. BLE Connection stability · InfiniTimeOrg/InfiniTime · Discussion #2233 · GitHub

2 Likes