@walidham Sorry, it worked now seems like I did not format data.

Let me know what I need to test for you. It was a phone lying around so I'd like to help.

@walidham Thanks for the TWRP file, very easy to apply. :smiling_face_with_smiling_eyes:
I installed it but even then I'm getting "Failed to boot".

@walidham
I'm using stock Android (8) as a base and installed everything according to the documentation and your post.

The device is popping up in the device list but the name is "Failed to boot". I guess the image was made for Android 9.. so wrong base? Which should I use?

@SteveDx I have been working on moving the existing port to focal but I don't have any experience so there are a bunch of issues... I can share the code if you are still interested.

@Lakotaubp Still wanna work on it. I just don't have a Pinetime currently. Mine broke down a while ago. And at the moment it's hard to find the time to.

@sandworm88 Here you go, that version should work again in xenial: https://gitlab.com/jiiho1/uwatch/-/jobs/3377320141/artifacts/download?file_type=archive

After pairing the watch via system settings, disconnect it and disable auto connect. Gatttool can't enter existing connections. The app will connect to the watch automatically.

@sandworm88 As I wrote in my last post, I can bring back gattool support. But the functionality will be limited.

If you take a look at the CI builds, then you'll notice that one (the working one) is a build from the branch for xenial. The other one (not functional one) is for focal and therefore won't work at all on xenial.

@arubislander Even though I understand the decision, I was hoping the updated version would stay.

In the long run probably/hopefully not at all. I expect that we'll have a new version in focal which would make it work as I'd expect it to.

For xenial I can bring back support for gattool to at least make it work again, but it is old and already deprecated. There would also be a bunch of limitations by how it works.

@sandworm88 I'm sorry, I should have added it to the first post also.
With the updated BlueZ version in the Dev (and I think RC) channel, I stopped using gattool, as it made things a lot more difficult.

Instead I'm using bluetoothctl. Unfortunately the current BlueZ version in stable is not able to use GATT commands to fetch the information. This includes paired devices.

I just added automatic sync to the app and I'd like to get some feedback, if anyone is interested. To sync in the background, disable suspension with UTTT.

Build: https://gitlab.com/jiiho1/uwatch/-/jobs/3214702902/artifacts/download?file_type=archive

If everything works as expected, then I'd like to submit it as a beta app to the app store.

@equareo Could you please try this one: https://gitlab.com/jiiho1/uwatch/-/jobs/3199676376/artifacts/download?file_type=archive

I added a progress bar to display the initial sync (firmware version should then automatically update). Before that, could you delete the app data via UT Tweak Tool to get a clean state?

Only after the firmware version synced successfully will you be able to sync the rest of the data. (Battery status is currently broken as BlueZ can't fetch that attribute)

@equareo It should not matter if it is interpreted as a mouse :D... after the first connect, it will try to sync the firmware version of the watch (restart the app if the sync does not work at first). You can manually sync by swiping down.

@equareo Sure, here you go https://gitlab.com/jiiho1/uwatch/-/jobs/2982616820/artifacts/download?file_type=archive

@martijntje Thanks for trying out the app.
The pairing is currently broken it that version of the app. You can pair the watch via the system settings and then try again. That should add the watch as an "already known device".

With the BlueZ update in the devel channel I was able to rebuild the back end and let the pairing process (and automatic reconnect) be handled by system settings.

This should make the whole process smoother and overall faster (I hope). In case you think of using the development channel (or wait until the change hits stable), feel free to try out this new version: https://gitlab.com/jiiho1/uwatch/-/jobs/2982595472/artifacts/download?file_type=archive

However, there currently is a drawback: It seems that with this new version, BlueZ is not able to fetch all necessary services from the watch. Because of that the battery level can't be read and you will most likely get an "impossible" value back.

@phiibuntu Sorry, I don't know. The app itself uses Bluetooth Low Energy to sync the data. So the watch needs to support this.

I've implemented default values that are based on the official documentation. So as long as a watch uses BLE with these values, SOME data can be synced.

If that's not the case but the watch uses BLE then the BLE GATT values need to be added to the app.

@lakotaubp Thanks for the advice. You are right, it might be a good idea to submit the app, when I think it is ready as a beta.

@keneda It's difficult to define what the beta state is... How much should the app be able to do to be understood to be in beta.

But besides that, I haven't implemented an appropriate error management yet.

@phiibuntu You can download build artifacts from here: https://gitlab.com/jiiho1/uwatch/-/pipelines

You'll be able to download a ZIP file that contains the click package. You can install it either with UTTT or opening it with the Open Store.

Beware however... I am currently rewriting a huge part of the backand in 'movetojs'. So make sure to download the artifact from 'main', because some things are not yet working in 'movetojs'.

If needed I can also build a package for you.

@lakotaubp Sorry, I moved to project to a group in GitLab (to have all UT apps in the same place).

You can find the latest builds here: https://gitlab.com/jiiho1/uwatch/-/pipelines

The latest build (a few minutes ago) should be one last one you already have (with clickable 7 build).

A lot more changes are currently happening in the branch "movetojs", however not everything is working in there yet.

@lakotaubp Sorry for the late reply. (And missing news in general)

To be honest I ran into some problems with the current version of bluez.
Pin verification will be made mandatory in Infinitime at some point. As this functionality is already included in the System Settings, I wanted to use it, to pair and verify the watch and then use it in the app. That would also provide an easy way to automatically connect to the watch. Gatttool however is not able to enter existing bluetooth connections and the implemented version of bluez is not able to handle GATT very well or at all (never actually got it to do what I want).

So to work around some things, I started to rethink the backend and am currently working on that.

Also I want to see what I can do with the upcoming 20.04 base as hopefully the bluez version will be able to handle the requests way better.