Ability to read large data from offsets if requested from device#39
Open
brett-lynnes wants to merge 1 commit intonettlep:masterfrom
Open
Ability to read large data from offsets if requested from device#39brett-lynnes wants to merge 1 commit intonettlep:masterfrom
brett-lynnes wants to merge 1 commit intonettlep:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I encountered problems reading a 220 byte string on iOS. It worked fine on Android, and after debugging I found out that BlueZ is returning some pParameters in the Method callback, mainly "offset" appeared.
This is just a simple method to look for the "offset" parameter and also a piece of example code of it being applied. You should only need to call getOffsetFromParameters() if the data being returned (either byte array or c-string) can be pretty large. afaik iOS is the only OS that actually breaks reads up like this (at 184 byte intervals), everything else just uses the HCI automatic packet chunking (even my Galaxy S6 worked on data over 4Kbs).