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 - Battery Issue? #645

Open
yaronyg opened this Issue Mar 18, 2016 · 0 comments

Comments

Projects
None yet
2 participants
@yaronyg
Member

yaronyg commented Mar 18, 2016

There is a bug we ran into on Android where on some devices if we try to publish service data via BLE we will get a 'too long' error even though we have checked what we set 10 ways from Sunday and it appear to meet the length requirements and the identical code works fine on other devices. @tompaana came up with a work around which is that if a device gives him an error when setting service data then instead he will publish using manufacturer's data. Service data advertises a service while manufacturer's data advertises the existence of a piece of hardware.

The only potential problem with this approach is that now everyone has to scan for Thali clients using both service and manufacturer data. What we aren't clear on is - what are the battery implications? Do the phones do any kind of hardware hand off of the scanning for either or both of these?

@yaronyg yaronyg added the 0 - Icebox label Mar 18, 2016

@yaronyg yaronyg added this to the V1 milestone Aug 3, 2016

@yaronyg yaronyg added 1 - Backlog and removed 0 - Icebox labels Aug 4, 2016

@yaronyg yaronyg added the Android label Sep 1, 2016

@yaronyg yaronyg added bug and removed 1 - Backlog labels Oct 6, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment