Closed flossgeek closed 1 year ago
You need a patched version of Bluez, available from https://build.merproject.org/project/show/home:piggz:harbour-amazfish-dev until probably SFOS 4.5
Your newest build however is for version 4.4.0.58 while I'm on 4.4.0.64. Can I still use that one?
Yes, it should be fine (tm)
I followed your instructions to patch Bluez from another issue (https://github.com/piggz/harbour-amazfish/issues/225#issuecomment-1120291369), but when I run zypper up bluez5
, it says that the highest available version is already installed.
@piggz any updates? I really want to use this app!
Have you tried zypper dup instead? if you search with zypper se -s bluez5 it will list all available version, make sure mine is listed, and try specifying the full version number to zypper
I don't think yours is listed. For clarity this is the list of bluez5 packages:
S | Name | Type | Version | Arch | Repository
--+-------------------------------+------------+--------------------------+---------+------------
i | bluez5 | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5 | srcpackage | 5.58+git4-1.7.11.jolla | noarch | jolla
| bluez5-configs-mer | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-cups | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-debuginfo | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-debugsource | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-doc | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-hcidump | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
i | bluez5-libs | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-libs-devel | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
i | bluez5-obexd | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-obexd-tools | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-obexd-tracing | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-test | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-tools | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-tools-hciattach | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| bluez5-tracing | package | 5.58+git4-1.7.11.jolla | aarch64 | jolla
| droid-config-xqau51-bluez5 | package | 0.1.24.1-1.6.1.jolla | aarch64 | adaptation0
i | droid-config-xqau52-bluez5 | package | 0.1.24.1-1.6.1.jolla | aarch64 | adaptation0
i | kf5bluezqt-bluez5 | package | 5.24.0+git18-1.5.1.jolla | aarch64 | jolla
| kf5bluezqt-bluez5 | srcpackage | 5.24.0+git18-1.5.1.jolla | noarch | jolla
| kf5bluezqt-bluez5-debuginfo | package | 5.24.0+git18-1.5.1.jolla | aarch64 | jolla
| kf5bluezqt-bluez5-debugsource | package | 5.24.0+git18-1.5.1.jolla | aarch64 | jolla
i | kf5bluezqt-bluez5-declarative | package | 5.24.0+git18-1.5.1.jolla | aarch64 | jolla
| kf5bluezqt-bluez5-devel | package | 5.24.0+git18-1.5.1.jolla | aarch64 | jolla
The newest version, according to my system (5.58) is already installed for me.
Hello guys I am completely new and I encountered the same problem...zypper cannot see the repo at all...or the packages! I went a little bit differently and it solved the problem...probably not the nicest way...but it might help. Please thell me if I did anything silly!
I did it with zypper ar
devel-su
after that I was able to simply zypper up bluez5
(with some pop up warnings about packages not signed and stuff)
after all this I paired my watch and did the appearance line in the info file...but my watch still won't connect properly. I have a Amazfit GTR2 e ...should the work the same way as the GTR2?
Is there any other ideas what I could try?
I hope the zypper ar thing will help you flossgeek.
Same here. I've followed the instructions of CoffeeMan82 and could then install the bluez5 version of piggz. Rebooted, but still Amazfish could not finish connecting to the watch: it connects via bluetooth, but the circle arrow on the watch icon spins for a while and then stops. Both the bluetooth and watch icon then disappear. This process repeats when Amazfish tries to reconnect.
Perhaps I have a similar issue as CoffeeMan82: I try to connect a GTS2e watch (no, not the GTR2e version ;) ).
Please if anyone has any ideas? This is literally the only thing what keeps me on Android....and believe me...I don't want to be there! :-)
I have exactly the same problems with my GTR2. @CoffeeMan82's instructions worked perfectly for installing the repo (although I had to ignore three unsigned packages), but after pairing the watch does not want to connect.
GTR2E is unsupported currently. I imagine the daemon picks the wrong backend to use. I will try and add it.
Thank you very much!!!
@piggz then do you have an explanation for why it doesn't work with the GTR2 either?
@flossgeek can you provide logs? journalctl | grep amaz
Yes, I'll post the logs from the moment I tried to connect to the watch:
Jul 12 18:58:58 Xperia10II-DualSIM i[6699]: [D] unknown:0 - Database is: "/home/defaultuser/.local/share/harbour-amazfish/harbour-amazfish/amazfish.kexi"
Jul 12 18:58:59 Xperia10II-DualSIM i[6699]: [W] unknown:82 - file:///usr/share/harbour-amazfish-ui/qml/pages/FirstPage.qml:82: ReferenceError: txtMessage is not defined
Jul 12 18:59:10 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:10.421 : Notification category "service" does not exist
Jul 12 18:59:10 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:10.503 : no notification service, buffering notification
Jul 12 18:59:15 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:15.005 : DeviceInterface::onRefreshTimer
Jul 12 18:59:15 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:15.007 : AbstractDevice::reconnectionTimer
Jul 12 18:59:15 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:15.011 : Lost connection
Jul 12 18:59:15 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:15.011 : QBLEDevice::disconnectFromDevice
Jul 12 18:59:15 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:15.015 : QBLEDevice::connectToDevice
Jul 12 18:59:16 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:16.749 : virtual void HuamiDevice::onPropertiesChanged(QString, QVariantMap, QStringList) "org.bluez.Device1" QMap(("Connected", QVariant(bool, true))) ()
Jul 12 18:59:16 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:16.750 : void AbstractDevice::setConnectionState(const QString&) "connected"
Jul 12 18:59:16 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:16.750 : DeviceInterface::onConnectionStateChanged "connected"
[root@Xperia10II-DualSIM defaultuser]# journalctl | grep amaz
Jul 12 18:58:31 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:58:31.119 : Close notification 16 2
Jul 12 18:58:31 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:58:31.119 : but it is not found
Jul 12 18:58:58 Xperia10II-DualSIM i[6699]: [D] unknown:0 - Database is: "/home/defaultuser/.local/share/harbour-amazfish/harbour-amazfish/amazfish.kexi"
Jul 12 18:58:59 Xperia10II-DualSIM i[6699]: [W] unknown:82 - file:///usr/share/harbour-amazfish-ui/qml/pages/FirstPage.qml:82: ReferenceError: txtMessage is not defined
Jul 12 18:59:10 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:10.421 : Notification category "service" does not exist
Jul 12 18:59:10 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:10.503 : no notification service, buffering notification
Jul 12 18:59:15 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:15.005 : DeviceInterface::onRefreshTimer
Jul 12 18:59:15 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:15.007 : AbstractDevice::reconnectionTimer
Jul 12 18:59:15 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:15.011 : Lost connection
Jul 12 18:59:15 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:15.011 : QBLEDevice::disconnectFromDevice
Jul 12 18:59:15 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:15.015 : QBLEDevice::connectToDevice
Jul 12 18:59:16 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:16.749 : virtual void HuamiDevice::onPropertiesChanged(QString, QVariantMap, QStringList) "org.bluez.Device1" QMap(("Connected", QVariant(bool, true))) ()
Jul 12 18:59:16 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:16.750 : void AbstractDevice::setConnectionState(const QString&) "connected"
Jul 12 18:59:16 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:16.750 : DeviceInterface::onConnectionStateChanged "connected"
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:47.454 : virtual void HuamiDevice::onPropertiesChanged(QString, QVariantMap, QStringList) "org.bluez.Device1" QMap(("Paired", QVariant(bool, true))("ServicesResolved", QVariant(bool, true))) ()
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:47.455 : void AbstractDevice::setConnectionState(const QString&) "paired"
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:47.455 : DeviceInterface::onConnectionStateChanged "paired"
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:47.469 : virtual void Gts2Device::initialise()
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:47.470 : void GtsDevice::parseServices()
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:47.474 : Resolved services...
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:47.475 : <!DOCTYPE node PUBLIC "-//freedesktop//DTD D-BUS Object Introspection 1.0//EN"
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: "http://www.freedesktop.org/standards/dbus/1.0/introspect.dtd">
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: <node><interface name="org.freedesktop.DBus.Introspectable"><method name="Introspect"><arg name="xml" type="s" direction="out"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: </method></interface><interface name="org.bluez.Device1"><method name="Disconnect"></method><method name="Connect"></method><method name="ConnectProfile"><arg name="UUID" type="s" direction="in"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: </method><method name="DisconnectProfile"><arg name="UUID" type="s" direction="in"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: </method><method name="Pair"></method><method name="CancelPairing"></method><property name="Address" type="s" access="read"></property><property name="AddressType" type="s" access="read"></property><property name="Name" type="s" access="read"></property><property name="Alias" type="s" access="readwrite"></property><property name="Class" type="u" access="read"></property><property name="Appearance" type="q" access="read"></property><property name="Icon" type="s" access="read"></property><property name="Paired" type="b" access="read"></property><property name="Trusted" type="b" access="readwrite"></property><property name="Blocked" type="b" access="readwrite"></property><property name="LegacyPairing" type="b" access="read"></property><property name="RSSI" type="n" access="read"></property><property name="Connected" type="b" access="read"></property><property name="UUIDs" type="as" access="read"></property><property name="Modalias" type="s" access="read"></property><property name="Adapter" type="o" access="read"></property><property name="ManufacturerData" type="a{qv}" access="read"></property><property name="ServiceData" type="a{sv}" access="read"></property><property name="TxPower" type="n" access="read"></property><property name="ServicesResolved" type="b" access="read"></property><property name="WakeAllowed" type="b" access="readwrite"></property></interface><interface name="org.freedesktop.DBus.Properties"><method name="Get"><arg name="interface" type="s" direction="in"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: <arg name="name" type="s" direction="in"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: <arg name="value" type="v" direction="out"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: </method><method name="Set"><arg name="interface" type="s" direction="in"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: <arg name="name" type="s" direction="in"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: <arg name="value" type="v" direction="in"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: </method><method name="GetAll"><arg name="interface" type="s" direction="in"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: <arg name="properties" type="a{sv}" direction="out"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: </method><signal name="PropertiesChanged"><arg name="interface" type="s"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: <arg name="changed_properties" type="a{sv}"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: <arg name="invalidated_properties" type="as"/>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: </signal>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: </interface></node>
Jul 12 18:59:47 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:47.481 : 1 nodes
Jul 12 18:59:49 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:49.516 : virtual void HuamiDevice::onPropertiesChanged(QString, QVariantMap, QStringList) "org.bluez.Device1" QMap(("Connected", QVariant(bool, false))("ServicesResolved", QVariant(bool, false))) ()
Jul 12 18:59:49 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:49.516 : void AbstractDevice::setConnectionState(const QString&) "disconnected"
Jul 12 18:59:49 Xperia10II-DualSIM harbour-amazfishd[6078]: 2022-07-12 18:59:49.516 : DeviceInterface::onConnectionStateChanged "disconnected"
@piggz my bluetooth is also behaving very irregular since the change. Headphone controls don't get passed through at all or with minutes delay. Is the zypper ar
method from CoffeeMan82 sufficient or not?
My bluetooth is working ok since the zypper ar thing! :-)
I reverted back to the Jolla version of bluez5.
I think I have a clue as to why it doesn't work. When ignoring the unsigned packages, they probably don't even get installed, so no surprise it doesn't work. Probably parts of the old (or the entire) bluez5 stack remain intact. The only options for the unsigned packages are "Abort, retry, ignore". Retry results in the exact same error, so there seems to be no way out.
@piggz as I understand it correctly, all these problems should be solved with the release of SFOS 4.5? If so, waiting for that release seems to be the best option right now. When can we expect it?
@piggz: Where can you see if your bluez change/patch/PR for SfOS is added/merged to the OS (for the next release)? Currently the Sailfish OS Forum is posting more about merged changes in the OS, but your bluez patch has not been mentioned (or I did not find it yet)...
I can confirm that unfortunately the same has happens (or at least to me?) on the 10III. CoffeeMan58's suggestion didn't work for me. Maybe i need to double check.
However, I don't have access to zypper, I did things via pkcon.
Edit: I installed zypper and it seems I have the latest version from the repo.
I believe to be stuck here as well - even though when looking at the journalctl
output on my X10 II, it seems to be able to connect - but whatever it tries to do afterwards seems to fail hard and leads to a disconnect.
Versions in use:
[root@Xperia10II-DualSIM defaultuser]# rpm -qa | grep bluez
bluez5-obexd-5.63+git1+use.cached.appearance.20220405092430.1.ga06796ad7-1.2.1.jolla.aarch64
droid-config-xqau52-bluez5-0.1.24.3-1.7.1.jolla.aarch64
bluez5-libs-5.63+git1+use.cached.appearance.20220405092430.1.ga06796ad7-1.2.1.jolla.aarch64
bluez5-5.63+git1+use.cached.appearance.20220405092430.1.ga06796ad7-1.2.1.jolla.aarch64
kf5bluezqt-bluez5-declarative-5.24.0+git18-1.5.1.jolla.aarch64
kf5bluezqt-bluez5-5.24.0+git18-1.5.1.jolla.aarch64
[root@Xperia10II-DualSIM defaultuser]# rpm -qa | grep amaz
harbour-amazfish-2.0.8-1.3.1.jolla.aarch64
[root@Xperia10II-DualSIM defaultuser]# ssu re
Device release is currently: 4.4.0.68
Device: Amazfit GTS 2 Firmware: v4.4.1.1
I'm not sure whether that is relevant or not: When trying to pair the device, I commonly see a Amazfit GTS 2 - 411C
which is not having the same MAC address than shown when getting the auth-key
. I had to rescan many, many times until that address showed up - as Amazfit GTS 2
(as in, without the "-411C"-suffix).
So here's what I did to end up here:
Appearance=0x0192
line in [General]
and restarted bluetoothhuami_token.py
I get a bluetooth symbol and a watch symbol showing up. But I cannot do anything. And then it suddenly is disconnected again.
For reference, I tried to run a build on my Desktop box running Fedora Linux 36 and see whether there it would work After @piggz fixed an issue that may or may not have been Fedora specific, I can now also find and select the GTS 2 for pairing - but I'm stuck at about the same spot: I can't do anything and after a while the device disconnects.
Interesting observation: If I use a completly random auth key the perceived behavior is identical. So maybe it's something with the auth prozess? Maybe they changed something here for the latest version of their firmware?
Additional side note: I tried pairing with an android (lineage OS 19.1) device using Gadetbridge. It works there.
At least on my Desktop when checking journactl
's output, I see bluetoothd
throwing an error when pairing:
Sep 17 15:48:25 ..... bluetoothd[4216]: src/device.c:new_auth() No agent available for request type 2
Sep 17 15:48:25 ..... bluetoothd[4216]: device_confirm_passkey: Operation not permitted
Sep 17 15:48:55 ..... bluetoothd[4216]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error
I believe to have seen this "unlikely error" part on my Sailfish device as well..
What bluez version do you have? I actually had to get a change into bluez for this, and you have to manually set the device type in a bluez config file. See the readme on the front page.
# rpm -qa |grep bluez
bluez-5.65-1.fc36.x86_64
bluez-libs-5.65-1.fc36.x86_64
bluez-obexd-5.65-1.fc36.x86_64
bluez-cups-5.65-1.fc36.x86_64
kf5-bluez-qt-5.97.0-1.fc36.x86_64
I did set the Appearance=0x0192
into the corresponding file in /var/lib/bluetooth/...../info
and also, for the just in case, added it to the cache entry. I also restarted bluetoothd as well as the amazfish daemon prozess.
I'm no longer getting the "no agent available" error but the UI behavior is still the same: I can select connect, it does show as if connected, nothing can be done, and then it suddenly is disconnected.
I keep getting
Sep 17 22:56:27 ..... kernel: Bluetooth: hci0: Opcode 0x 401 failed: -16
Sep 17 22:56:44 ..... bluetoothd[1712140]: profiles/deviceinfo/deviceinfo.c:read_pnpid_cb() Error reading PNP_ID value: Request attribute has encountered an unlikely error
whenever i tell amazfish-ui to connect. Not sure if that points at what you mentioned regarding having a patched version of bluez being required?
It seems that the aforementioned patch is included in 5.65. ( https://git.kernel.org/pub/scm/bluetooth/bluez.git/log/?h=5.65 )
@theseer can you send logs from the daemon, also, can you check if it possible to pair using eg kde, and to browse the services with qdbusviewer?
Sure, will do later today when I'm back home.
Okay, played around with things again on my Laptop. Basically reset everything to square one and re-did everything step by step, Particularily adding the Appearance=0x0192
line to the info file as well as restarting bluetooth (systemctl restart bluetooth
).
I don't know what's different now, but now after some short waiting time, I can now confirm I can connect and fetch data from my GTS 2 using my Fedora 36 based Laptop. Of course the UI isn't optimized for this type of display so some things look a bit odd but that's fine and a different story.
In preparation to do what I've been asked, I also made the watch connect to the Laptop to have a "standard" bluetooth pairing. As it showed up with a mac address that's different from the one used by the Zedd App when registereing, I removed it again from the bluetooth pairing. Not sure if that had any side effect to make it now work.
I also get a notification "Amazfish connected" on the watch.
I since repeated this process various times now and it works every time.
Now if it only worked on my Phone ;-)
Success! Also can connect with my Sailfish phone now.
Not sure why, but it appears that the Appearance=0x0192
line gets removed / the info file rewritten. I have added the line, restarted bluetooth and it didn't work. I checked the file again, finding despite having added the line before and verifiying it's in there before restarting, that very line was gone.
Adding it yet again and restarting bluetooth once more, I now can connect and get data transferred.
Great, glad its working. Ive seen other users have the appearance line disappear, but it always seems to work for me! :)
@flossgeek can you check it works for you, and if its ok to close this issue? thx
Is there already a way to connect the GTR2 e?
@flossgeek can you check it works for you, and if its ok to close this issue? thx
Nope, it still does not work. It does connect successfully via bluetooth, though when the app tries to load the actual firmware it stops and fails. I don't have the Appearance line disappearing after restarting bluetooth either.
@kkoenders How did you revert back to the Jolla version of bluez5? I am still on the old 5.58 version and can't upgrade, because I'm using the patched version of piggz. I guess this may be the bottleneck, as it works for theseer on version 5.65.
Anything I can help? There must be something different anyhow ;)
Anything I can help? There must be something different anyhow ;)
@theseer yes, please. How did you update the bluez5 version? I'm stuck on 5.58, and while I did remove the repo of piggz, my version does not update when running zypper ref
and zypper up bluez5
again. Do you have any idea how I can upgrade to your version (5.65)?
Edit: so after removing piggz's repo and adding it again my bluez5 version updated to 5.65 and the watch finally connects!
What strikes me now though is that the tools menu of the watch is completely gone. Before connecting there was a menu with a ton of tools (like the timer) and also the settings app when clicking the upper button. Now I only get a black screen when going there. Is this expected? How can I get back those options again?
Did you do any firmeware updates on the watch? Because I didn't use amazfish for that (yet) - in case it actually would work with that model.
I do have the tools menu (swipe from top of screen). Did you try resetting the watch? Maybe it just crashed ;)
Did you do any firmeware updates on the watch? Because I didn't use amazfish for that (yet) - in case it actually would work with that model.
I do have the tools menu (swipe from top of screen). Did you try resetting the watch? Maybe it just crashed ;)
No, I haven't done that either. Do you also have the other menu that you get by pressing the top button at the right of the watch?
I don't have that button, as I own a GTS 2:
Pushing the "only" button i have on the right gets me to a working menu though.
I have the same issue with my GTS now: no settings menu anymore. It is not in my watch when I scroll through the menu items and it is not available in the Huami Display Items in the app either (so it not disabled)
@flossgeek : I do not remember exactly how I reverted back to the original bluez of Jolla, but I think it was via zypper. I googled it just now and I found this could work: zypper in -f <package-with-version>
. You could try something like zypper in -f bluez5=<jolla version>
(I don't know if the bluez version of Sailfish changed since July). I'm not sure if this was what I did, though. Sorry ;(
I am talking about this menu by the way:
Yes, that's the menu on the GTS is opened via the single button on the right. It works like charm for me.
Hm, that's odd that it disappeared here then. Did you do anything else after pairing the watch? (like connecting to the Zepp app again)
Steps I've taken:
Sadly the watch icon keeps loading when I'm trying to connect to the watch (and eventually doesn't connect). What am I missing here? Is it necessary to flash additional firmware to be able to use the watch with Amazfish?
Additional info: