You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found that in the Galaxy(android 9 series) accepts packets with data loss without skipping them.
As far as I've checked, IsochronousStream Class can't skip the problematic frame.
The reason seems to be the lack of defensive code to detect frames.
In IsochronousStream class, the current header length, flag, and data length are only detected,
So frame detection is improved by adding FID and EOF, but skip is not perfect.
The text was updated successfully, but these errors were encountered:
I experimented some time ago on this behavior, but wasn't able to solve it.
Any help would be welcome to solve this issue.
Ehm, this issue could be solved, by an analysation of the bytes of each frame.
A normal frame's bytes looks different to each other (the bytes were displayed for example in the testrun button under "set up the device" menu.
I'll think a problematic frame lists a lot of bytes in the same value (hex from 0 x00 to 0xff).
Hi, Peter-St
I found that in the Galaxy(android 9 series) accepts packets with data loss without skipping them.
As far as I've checked, IsochronousStream Class can't skip the problematic frame.
The reason seems to be the lack of defensive code to detect frames.
In IsochronousStream class, the current header length, flag, and data length are only detected,
So frame detection is improved by adding FID and EOF, but skip is not perfect.
The text was updated successfully, but these errors were encountered: