-
Notifications
You must be signed in to change notification settings - Fork 0
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
GPS #3
Comments
It seems at least the translation from hci to /data/gps/brcm_gps_unix_socket is trivial:
apart from So:
|
Actually, in the response, checksum is unlikely, since it's always 0x10. Maybe some id? |
turning location off seems to have no effect at this level. how reassuring... |
Only opening this to make it clear that GPS is NOT working on the ROM, and to document the current status.
The situation on our tablet appears to be the following: the tablet has a combined Bluetooth/GPS chip, which communicate over the same interface. What they did on the stock ROM is hack Android's Bluetooth implementation (
bluetooth.default.so
) to additionally provide a communication channel for the GPS implementation (located at/data/gps/brcm_gps_unix_socket
). Without this change, there is no way the (also proprietary) GPS implementation can communicate with the chip.Normally changes like these should be made in the device specific hardware implementation (HAL), but for some reason they decided to hack it into Android's Bluetooth implementation directly. Because of that, it is pretty much impossible to port this to newer Android versions - with each major update the Bluetooth implementation is also updated with new features and other changes - the old version wouldn't work at all on newer Android versions. Bluetooth (and GPS) is entirely broken when trying to use it on Nougat.
This does not only affect our tablet, but also some other smartphones from ASUS, e.g. the Zenfone 5.
With that said, it's unlikely that GPS will ever be working on this ROM, at least not unless ASUS releases the necessary source code for this setup. And this is likely never going to happen.
The text was updated successfully, but these errors were encountered: