GmsCore
GmsCore copied to clipboard
microg
Wishlist: com.google.android.gms.wearable
It would be nice to have a free implementation of the APIs necessary for Android Wear.
com.google.android.gms.wearable.NodeApi com.google.android.gms.wearable.MessageApi com.google.android.gms.wearable.DataApi
I would love to have this working also. I'm currently only using my smartwatch for timekeeping since I cannot sync it with my phone.
Gadgetbridge may be able to be used at the Android Wear client with microg implementing the transport API since it already has the required code to handle notifications, calls, etc and send them to a wearable API. See this issue: https://github.com/Freeyourgadget/Gadgetbridge/issues/158
It's a pity that I have no use for my android wear device at the moment without gapps. It would be really nice to see this happening.
I seem to have a little progress by using Android Wear v1.4.0 and Google v5.13.31
EDIT: Had
I know that a 15$ bounty is not much, and laughably little when looking at the large amount of work this is likely to require, but I hope this helps :) (and maybe motivates others to post bounties too)
I would love this. Android Wear is the only app that keeps me from switching to microG.
I would love this as well. After discovering that microG doesn't support Android Wear, I'm completely discouraged from switching to it.
Hello all, i also hope for a support in the near future :-) Thx for your work so far!
Well no one is working on this issue. It is a bit out of my scope. Hopefully it'll happen one day
Perhaps it's better if we focused on helping https://asteroidos.org/ instead
How the bounty "program" works? I really would like to have the possibility to use my smartwatch with microG.
Using most recent Nanodroid (which uses microG). While I could pair my watch using Wear OS (formerly Android Wear), it'll stuck at "Getting your watch details" phase. One can just force stop the Wear OS and restart it, and you'll be greeted with the main screen as if the watch's been set up (though it won't be able to actually connect to the watch).
It's completely possible to use Android Wear 1.5 without a proper setup (just that Google related stuffs won't work anyway), but for Android Wear 2.0 this is impossible as the phone needs to go past the "Copy your Google account" phase, which would return a response to the watch so the setup could complete.
@benpro It's powered by bountysource.com, the URL for this issue is https://www.bountysource.com/issues/6460438-wishlist-com-google-android-gms-wearable
@robinvd To add something to the bounty you have to go to that site and add it there
Has there been any progress with this? So far it's the only thing stopping me from switching all at once. Though is it possible to use WearOS with MicroG?
@SolAZDev in commit 3c5e68404b92d6732082a8c42351809f93dad2be Marvin added some more Wear code, I'm testing it now with my Moto 360 gen 1 (Android Wear 1) and LineageOS with MicroG v0.2.9.
So far it doesn't seem to be working unfortunately. The initial setup is hanging. I might create a pull request if I can fix it.
@DynaSpan There is no Bluetooth code in microG's Wear implementation yet, it's just able to connect to an emulator via adb.
For Bluetooth functionality, One first need to record the Bluetooth connection of a original Google setup and then implement it in microG. The protocol should be mostly the same as via adb, just a different transport layer.
So I received my new battery for my Moto 360, so I can now test & develop properly, as it didn't last longer than 5 minutes on the original battery.
@mar-v-in I saw you had some information in Gadgetbridge/#158 and also pointed to WearableServiceImpl.java & wearable.proto. So I'm guessing these are most of the things I need to implement in Bluetooth.
I might have some spare time tomorrow and Sunday and would like to give it a try :). If you have any other resources I could use that would be great.
One last question: what about the use of Kotlin? Can I use it or should I stick to Java?
@DynaSpan @mar-v-in Sorry for the terribly late reply. I can volunteer for recording the process of registering if desired. But I'd need to know when and how to start recording. Although you can technically set it up once and then pair it up to another device without resetting but I'm not sure if that's part of the process you want to record.
That aside, does the adb connection work with devices? (amusing it's over wifi)
I would also be interested in this feature and willing to help. I have programming experience, but little experience with bluetooth. I have a wearos smartwatch, a rooted phone with play services and a phone with microg, so I can create bluetooth traces and test stuff. (I already have created a bluetooth trace of the pairing process, but I'd rather not post it publicly, as I don't know what personal information it contains).
I just added another $25 to the bounty for anyone that wants to work on this :smile:. The bounty is now up to $135
+1 for this. It's really sucky to have a half functional watch because I want to keep my privacy. Ive tried using the chinese WearOS companion in combination with the gms cache hack people have mentioned to get it to work and it almost does, but I keep having weird issues...
I'm tempted to look into implementing it myself but I don't even know where to start.
+1 for this. It's really sucky to have a half functional watch because I want to keep my privacy. Ive tried using the chinese WearOS companion in combination with the gms cache hack people have mentioned to get it to work and it almost does, but I keep having weird issues...
I'm tempted to look into implementing it myself but I don't even know where to start.
Hey can you send some link of that mentioned hack?
Well i looked into this and probably it goes something like this:
- Statically analyse the gms apk seeing the wearos API endpoints or dynamically analyase apps communicating through the wear os API.
- Then write these java classes and functions communicating with your specific watch HAL.
- It may be somewhat similar with all other watches but there may be some idiosyncrasies. (You can just analyse the traffic through wireshark)
You can probably go into the matrix chat of asteroidos.org they may have some insights into this.
+1. Would love to help. I have a wear os samsung smartwatch sitting right now.
I've noticed that I can set up a Pixel Watch using the trick with the global Wear OS app and the chinese Wear OS app and then using the Pixel Watch app. So it seems like the APIs are still compatible and this would probably add support for more modern watches and the Pixel Watch as well.
I've noticed that I can set up a Pixel Watch using the trick with the global Wear OS app and the chinese Wear OS app and then using the Pixel Watch app.
It's a tricky workaround, but with new WearOS, any vendor can use any app to bind, meaning, Google APIs might no longer be required at all(?), which should open the doors for some projects like Gadgetbridge to add general WearOS support.
which should open the doors for some projects like Gadgetbridge to add general WearOS support.
Finally, this would be interesting as it'd make those devices far more usable with microg and even Linux phones, if there could be open source implementations. :D
Could you please comment this at the Gadgetbridge repo as well? I think their devs would liketo know. :)
Did so (crossposting) now via https://codeberg.org/Freeyourgadget/Gadgetbridge/issues/3257
