Yesterday I quickly "ported" the #Rockwork daemon to Qt6 in order to get it working with my newly arrived #Pebble Time 2 (Qt6 apparently has some Bluetooth LE upgrades that are needed (also it allows me to package it for pmOS)).
It now runs, but there seems to be some protocol difference with the new watch as Rockworkd insists PebbleOS is booted to recovery mode, which is not the case. If I remove that parsing, some functions do work, so I must be on the right track.
For once I'm glad I woke up before my alarm. My #Pebble smartwatch is *40 minutes* off from the actual time!
I thought I simply forgot to enable it but the alarm to wake me up to prepare to travel today just started ringing... on the bus.
I don't know how this can be, since I run the #RockWork daemon on #postmarketOS to keep it in sync. Perhaps only the GUI (which no longer runs due to Qt5 deps) does the syncing?
I finally got Linux support for the #Rockwork #Pebble client ready for merge, and now I find out #AlpineLinux is (justifiably) phasing out Qt5 packaging, so I can't actually use it. š«
Makes senseā¦ time to port it to Qt6!
Also, my current stance on the #pebble smartwatch isā¦. š„š„š„ ā¦THAT ITS AMAZING!!
There are so many fun apps and watchfaces for it, and the UI has so much personality. Pixel miner is standing out as one of my favourites atm. Its also really cool how it uses the phone for nearly everything (internet things are done through the phone and sent back to the watch via bluetooth)
The quality is amazing (I have the steel time) and the reflective eink display works wonders outside (backlight works well inside, and you can still see without backlight quite well)
And, for the cherry on the top, the unofficial ubuntu touch app #rockwork has near full functionality (compared to android and ios)
Mat
LINux on MOBile
Daniel (CactiChameleon9)