-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for AsteroidOS watches #284
Comments
From the documentation https://wiki.asteroidos.org/index.php/BLE_profiles it seems they are using different bluetooth services then was implemented in amazfish. Basically only battery service is the same. In theory, the libasteroid could be adjusted (and it doesn't look that difficult). In real world, some device is needed to debug it. I am not able to help with that unless you want to donate some device. |
as little contribution from my side I would like to point out that asteroidos support has been implemented in gadgetbridge and that code from there possibly could be used: https://codeberg.org/Freeyourgadget/Gadgetbridge/pulls/3013 |
I've got a spare device, if you're somewhere I can get it shipped without spending more than the thing is worth. (The watch lives in USA right now.) Lemme know if interested. |
I am in Czech Republic (EU). Please contact me at [email protected] |
I have first step of implementation here https://github.com/jmlich/harbour-amazfish/tree/asteroidos However, I am not able to debug it without device. There is only Battery Service right now, so don't expect too much. I even don't know if this works properly. |
I could test this, but I don't know how to install it. IS there a compiled rpm package or only the source available? |
I am making builds just for Ubuntu Touch. Currently, I don't have SailfishOS SDK installed. I guess some CI may help in that area #313 |
RPM packages are here |
I installed armv7 on my device, but cannot connect to watch (sturgeon with asteroidos). What is the correct order of doing the pairing? Or isn't this supposed to be working yet? |
Its blind implementation. There should be just pairing and battery service (it should show charge level on first page only). And I am not able to verify if this works properly Recently, I was checking the pairing mechanism, and there is a filter of device name on the device pairing page which hides all devices without expected name (which is now set to AsteroidOS). Workaround is to click back to device selection and reopen the pairing page (it is probably bug, but now it is convenient - see #315). It seems all asteroid devices (bass, sturgeon, dory, ..) must be added to list separately. I have created new commit to improve this filtering. See |
I installed the rpm and now was able to connect to my watch, but it disconnected immediately. I couldn't see if the battery service worked, because I don't know where I have to watch. Could the disconnect be related to an too old version of asteroidos on the watch? I didn't update at least for one year. Also the watch strangely thought it was connected to my PC and not my phone. |
I have no idea. You have to check logs. I expect I will be able to check it next week my self. |
There were number of errors. Please try newer version. I am not sure about pairing process, the smart watch shows pin, which is not handled by system agent. I was able to confirm pin using system wide bluetooth pairing in Ubuntu Touch. Is is not ready to use, but provides interface for future development. |
I'm super excited to be finally be able to use my asteroidos watch with sailfish. When will this be released? |
If you're brave --as in willing to do a local install -- and eager to try it out now in its current state (which is "working" IMO) see @jmlich 's earlier post for the RPMs built with sfos support:
|
Dear Adam,
Could you please add support for AsteroidOS watches to Amazfish ?
https://asteroidos.org
I tried https://github.com/AsteroidOS/starship but couldn't find a binary compatible with Sailfish OS 4.5 on aarch64.
Best regards,
Samuel
The text was updated successfully, but these errors were encountered: