Network error

[zecm]

Checklist

• I am able to reproduce the bug with the latest version.
• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
• This issue contains only one bug.
• I have read and understood the contribution guidelines.

Affected version

0.25.0

Steps to reproduce the bug

I can't reproduce it when I want to, but there's no need to because it happens like once every 10 minutes and I have to restart my phone every time to watch a video.
Most of the times it happens when I enter full screen: the video stops and the error notification appears and I can't play the video anymore.
It happens a lot on peertube (like every video), and on YouTube once every 10-20 m

Expected behavior

Play a video

Actual behavior

The video stops and I can't start it anymore, without rebooting the phone first

Screenshots/Screen recordings

https://streamja.com/W40zL

Logs

Exception

• User Action: play stream
• Request: Player error[type=ERROR_CODE_IO_BAD_HTTP_STATUS] occurred while playing https://peertube.uno/videos/watch/7b569074-9d25-488c-aef2-15d71eb7f509
• Content Country: US
• Content Language: en-US
• App Language: en_US
• Service: PeerTube
• Version: 0.25.0
• OS: Linux Android 13 - 33

Crash log

com.google.android.exoplayer2.ExoPlaybackException: Source error
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleIoException(ExoPlayerImplInternal.java:632)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:604)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loopOnce(Looper.java:201)
	at android.os.Looper.loop(Looper.java:288)
	at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: com.google.android.exoplayer2.upstream.HttpDataSource$InvalidResponseCodeException: Response code: 404
	at com.google.android.exoplayer2.upstream.DefaultHttpDataSource.open(DefaultHttpDataSource.java:404)
	at com.google.android.exoplayer2.upstream.DefaultDataSource.open(DefaultDataSource.java:258)
	at com.google.android.exoplayer2.upstream.TeeDataSource.open(TeeDataSource.java:52)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.openNextSource(CacheDataSource.java:786)
	at com.google.android.exoplayer2.upstream.cache.CacheDataSource.open(CacheDataSource.java:599)
	at com.google.android.exoplayer2.upstream.StatsDataSource.open(StatsDataSource.java:84)
	at com.google.android.exoplayer2.upstream.DataSourceInputStream.checkOpened(DataSourceInputStream.java:99)
	at com.google.android.exoplayer2.upstream.DataSourceInputStream.open(DataSourceInputStream.java:62)
	at com.google.android.exoplayer2.upstream.ParsingLoadable.load(ParsingLoadable.java:174)
	at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:412)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1137)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:637)
	at java.lang.Thread.run(Thread.java:1012)

---

Affected Android/Custom ROM version

ArrowOs 13.0 Vanilla version

Affected device model

Redmi Note 10 Pro

Additional information

I'm on ArrowOs Vanilla Build (without gapps)
It happens on Libretube too, but not on Google's YouTube.
VLC has some problems too, but Just (video) player hasn't.
I've tried all other similar bug reports, noting works.

[opusforlife2]

Try another OS than Arrow.

[zecm]

That's what I did when the same thing happened on crdroid.
Maybe the problem is that I don't have Gapps?
I will try with Obsidianrom tomorrow

[opusforlife2]

crDroid is a known bad ROM. Arrow might be similar. Try another ROM, yes.

[AudricV]

Response code: 404

Note that unless you have something on your network which filter requests and return 404 HTTP codes, the issue you reported cannot be fixed from our side.

[zecm]

I realized the error I got from peertube is different than the one I get on YouTube.
On YouTube I get unrecoverable player error:

Exception

• User Action: play stream
• Request: Player error[type=ERROR_CODE_DECODING_FAILED] occurred while playing https://www.youtube.com/watch?v=6NlqaE9hvPw
• Content Country: US
• Content Language: en-US
• App Language: en_US
• Service: YouTube
• Version: 0.25.0
• OS: Linux Android 13 - 33

Crash log

com.google.android.exoplayer2.ExoPlaybackException: MediaCodecVideoRenderer error, index=0, format=Format(299, null, null, video/avc, avc1.64002A, 4836657, null, [1920, 1080, 60.0], [-1, -1]), format_supported=YES
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:566)
	at android.os.Handler.dispatchMessage(Handler.java:102)
	at android.os.Looper.loopOnce(Looper.java:201)
	at android.os.Looper.loop(Looper.java:288)
	at android.os.HandlerThread.run(HandlerThread.java:67)
Caused by: com.google.android.exoplayer2.video.MediaCodecVideoDecoderException: Decoder failed: OMX.qcom.video.decoder.avc
	at com.google.android.exoplayer2.video.MediaCodecVideoRenderer.createDecoderException(MediaCodecVideoRenderer.java:1590)
	at com.google.android.exoplayer2.mediacodec.MediaCodecRenderer.render(MediaCodecRenderer.java:813)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.doSomeWork(ExoPlayerImplInternal.java:989)
	at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:490)
	... 4 more
Caused by: android.media.MediaCodec$CodecException: Error 0x80001001

---

[opusforlife2]

Different issue. Let's focus on the Peertube 404 here.

[zecm]

The YouTube issue was system based, I've changed to AncientOS four days ago and it hasn't happened since.
The network error still appears on most peertube videos.
I tried Thorium, a peertube android app, to check if it was again a system error, but on Thorium everything works perfectly

[ghost]

Tbf Peertube has always had problems with NewPipe. Try using a different mirror in the meantime.

[kubo6472]

sorry for necroposting, this, or #8318 just occurred to me on YouTube (not peertube) but on a custom ROM (lineage) so I have no idea which of these already open issues is a better representation of what am I experiencing.

[opusforlife2]

Different issue. Let's focus on the Peertube 404 here.

Hence. Also, find out exactly what HTTP response code you're getting. This is HTTP 404, the issue you've linked is HTTP 416.

[kubo6472]

Different issue. Let's focus on the Peertube 404 here.

Hence. Also, find out exactly what HTTP response code you're getting. This is HTTP 404, the issue you've linked is HTTP 416.

finally replicated, getting 403 😅

[opusforlife2]

Then that's a different bug entirely. I don't think you need to open a new issue. It'll have been reported already.