Improve Bluetooth Input Stream Handling for Large Data Packets#19
Open
Benjith wants to merge 4 commits into
Open
Improve Bluetooth Input Stream Handling for Large Data Packets#19Benjith wants to merge 4 commits into
Benjith wants to merge 4 commits into
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.
This update enhances the ConnectedThread in the flutter_bluetooth_classic plugin by:
Replacing the small 1024-byte buffer with a larger ByteArray buffer to accommodate bigger payloads.
Using copyOfRange() to safely extract only the received bytes before sending them to Dart.
Adding clear debug logs for received byte count and UTF-8 string representation. (see the commented lines)
Removing the messageBuffer logic, which was unsuitable for binary or large payloads.
This fix resolved issues where fragmented or heavy data (like sensor streams or long messages) were not reliably processed on Android. The previous buffer and message-building logic lost data.