TSExtractor.readOnePacket(): bad sync byte -- should report error state

[fougere-mike]

This issue has only been seen once, so I believe it may have been a networking hiccup. However, this did not propagate through any on*Error() methods -- it simply left my player stalled in the buffering state.

Low level errors which cause player stalling should be reported through appropriate listeners.

08-20 15:55:13.920: D/HLSSampleSource(2974): opening http://192.168.1.140:80/stream/segw.ts?AYvvv7IZ0g6e9nuJkRw5PQ
08-20 15:55:14.110: E/HLSSampleSource(2974): extractor read error
08-20 15:55:14.110: W/System.err(2974): com.google.android.exoplayer.ParserException: bad sync byte: 0
08-20 15:55:14.110: W/System.err(2974):     at com.google.android.exoplayer.parser.ts.TSExtractor.readOnePacket(TSExtractor.java:357)
08-20 15:55:14.110: W/System.err(2974):     at com.google.android.exoplayer.parser.ts.TSExtractor.read(TSExtractor.java:397)
08-20 15:55:14.110: W/System.err(2974):     at com.google.android.exoplayer.hls.HLSSampleSource$ChunkTask.doInBackground(HLSSampleSource.java:596)
08-20 15:55:14.110: W/System.err(2974):     at com.google.android.exoplayer.hls.HLSSampleSource$ChunkTask.doInBackground(HLSSampleSource.java:1)
08-20 15:55:14.110: W/System.err(2974):     at android.os.AsyncTask$2.call(AsyncTask.java:288)
08-20 15:55:14.110: W/System.err(2974):     at java.util.concurrent.FutureTask.run(FutureTask.java:237)
08-20 15:55:14.110: W/System.err(2974):     at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:231)
08-20 15:55:14.110: W/System.err(2974):     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
08-20 15:55:14.110: W/System.err(2974):     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
08-20 15:55:14.110: W/System.err(2974):     at java.lang.Thread.run(Thread.java:811)