OpenFit
OpenFit copied to clipboard
jareddlc
rewrite open fit to support multiple samsung watches.
Open Fit was my first android application and I've learned better ways to implement an app. It would be nice to rewrite to make it more maintainable. It would also be nice to see support for the following watches.
- Samsung Gear Fit (owned)
- Samsung Gear Fit 2
- Samsung Gear S2 (owned)
- Samsung Galaxy Fit
I've just ordered myself a Gear Fit2. I would be happy to help test and even help with development for fit2-specific stuff if you can point me in the right places I need to look.
Oh, and you might want to add Samsung Gear S3 to the list, which was released November 18, 2016...
I tried it on my Gear Fit2. It is able to detect the g fit2, but not able to connect.
The basic work flow is
Phone send connect to GearFit, GearFit responds with a few packets, one of those packets has module and ID of the GearFit and I believe a "ready" command, after receiving the "ready" command the Phone will then try to connect to the device.
So I believe to support connection to GearFit 2, we would need to know the packets it sends on initial connection.
Sorry to resurrect a thread, but has there been any recent developments (bad pun) on Gear S2 support?
@nate2014jatc im slowly rewritting the bluetooth library, once that is complete I may create an updated Open Fit which should be able to support multiple watches
Hey man, don't stress. It's a big job and you're one guy
Sent from my Android device with K-9 Mail. Please excuse my brevity.
@jareddlc Have you been able to rewrite the library as you planned ?
I currently own a Gear Fit2 Pro and I'd really like an Open Source app to replace so proprietary Samsung Health app, and to be able to connect with Google Fit and stuff.
If you're still motivated and you need any help I'd love to participate ! Have you tried to spoof the protocol for those other watches yet ?
@bonswouar I have started, currently im working on the UI, moving over to fragments. Progress is going slow as I find myself busy with another project. But I am slowly working towards this goal. Keep and eye out on the 2.X.X branch. I do plan on adding support for other samsung watches, but havent worked on that. I do own a Gear S2 and it would be great if you could help out with the Gear Fit 2.
@jareddlc Hi, how is this task going? We have a Gear fit 2, I can help you with the development. I'd really like to see it working :D
@Gollam thanks, I currently working on another project, But I have got some work done for a 2.0.0 version (got about 90% of the bluetooth library ported). I decided in writing it in flutter, as the opens the possibility of having support for iOS. Much of that work is in a new private repo, as someone has cloned open fit and published it under a new name and new features, but when i asked if they could copy those changes over to open fit, they denied it. I would like to have me source be open source, but i do not know how i could prevent the same thing from happening. And i am open to suggestions.
If you want to force people to contribute (or at least have their changes be reciprocal) you should use a copyleft license.
But aside of that, considering the radio silence on the project.. I don't really think that's much of a concern anymore. You should just push whatever you already have to the 2.X.X branch and call it a day.
