Warning: I removed gattool support from the latest builds. This causes devices on stable to not be able to communicate to the paired watches as the current BlueZ (bluetoothctl) version is not able to send GATT commands.

Working build for xenial which includes support for gatttool: https://gitlab.com/jiiho1/uwatch/uploads/c4dd2cffae019106bebab9641f69c4b1/uwatch.jiho_0.1_all.click

What works:

• Searching and adding devices from within the app (to connect the device automatically, use System Settings)
• Sync time on the watch upon connecting
• Sync battery level
• Sync heart rate
• Sync firmware version
• Sync device name
• Sync hardware revision
• Sync steps (available in firmware version 1.7.0 and higher)
• Graphs to display synced data over time
• Automatically fetch data regularly

Things I want to implement or things I'm currently working on:

• Calculate burnt calories (will be calclated by steps per day)
• Notifications
• Music controls
• (Maybe an indicator)

Also I am currently focusing on the PineTime with InfiniTime.

Source code: https://gitlab.com/jiiho1/uwatch
uGatt: https://gitlab.com/jiiho/ugatt (GattTool for Ubuntu Touch)

@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.

I am currently working on a Smartwatch Sync App for UT, to at least be able to sync the time and get data like heart rate, steps, etc. (for now at least)

I might have an alpha version of it ready in a few days (can't guarantee that though), if anyone would be interested.

I am currently focused on supporting Infinitime.

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.

@jf002 Hi JF002! Thank you for creating InfiniTime. Using the PineTime with InfiniTime actually pushed me to try my hands on my first ever QML app. I got the opportunity to learn so much and of course I am still learning and experimenting.

I am always happy to receive feedback and help especially with the BLE part, as I am sure, I am doing many things wrong or at least not the best way.

@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.

@FP2andFP3-User I have the same device and the firmware downgrade also bricked my device.
This guide and tool did help me to fix the problem: https://www.xda-developers.com/bypass-mediatek-sp-flash-tool-authentication-requirement

THIS TIME though! Before that tablet I also had another MediaTek device I tried to unbrick... but I made the mistake of unplugging it before that tool finished.... after that... the device was totally and forever borked.... not even the correct drivers showed up in device manager.... and Ubuntu was not able to detect the device at all... the device completely malfunctioned.

The tool will basically start the device in OEM mode ... and let's you bypass everything... so you can literally destroy everything with it. It will disable protection... and while the device is still connected, run the SP Flash Tool (I used the one provided by the Lenovo Rescue tool) and flash the correct firmware...

One last warning here:
This tool is able to make the device never recoverable! Use at own risk!

@lakotaubp Very nice!
Be aware though that UT does not seem to be able to connect, if the firmware version 1.3.0 is installed.

Many things are not yet implemented, but I am getting there. OTA support and notifications will probably be the next things I'm going to implement.

@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.

@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.

@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.
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.