Skip to content
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

Android soon. When...."? #4

Open
tangous opened this issue Apr 1, 2018 · 3 comments
Open

Android soon. When...."? #4

tangous opened this issue Apr 1, 2018 · 3 comments

Comments

@tangous
Copy link

tangous commented Apr 1, 2018

No description provided.

@RomainQuidet
Copy link
Owner

RomainQuidet commented Apr 3, 2018

Hello,
I need to re-check Android to see if what is needed for this framework is now available on majority of devices.
What is your use case?
Thanks,
Romain

@Falcosc
Copy link

Falcosc commented Apr 18, 2018

GL-770 support for android would be interesting. But even more interesting would be the GL-770 protocol definition. You did already figured out how to search and communicate with this device. Would you like to share your work?

Would be very nice to have this support as part of Locus Maps. As I understand correctly your app could already provide the GPS to other apps. I'm not sure what the disadvantages are on this approach.

@RomainQuidet
Copy link
Owner

On iOS the OS prevent GPS data injection from applications (possible only with 3rd party accessories which are part of MFI program, with embedded signature chip). So the framework must be embedded in each app which want to support external GPS via LNS Bluetooth service. That's why I made this framework.
On Android, as it is a little bit more open, it is possible to inject GPS data (via developer mode, it's not that open.)... anyway, it could work as on iOS, each app needing LNS Bluetooth service support could embed a framework to do so.
I'm not an Android dev, but I know how to do. If I find some time I will try to make this lib or framework.

For the GL-770, it's a LNS service as the standard defines it, but as its sending buffer is quite short, it sends one time information about altitude, speed etc and another time the user location (lat/lon). So in order to get all information you need to way 2 posts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants