Closed iamkroot closed 3 years ago
I have the same issue with 0.21.8
Worked around by switching to webm.
For me, it got fixed when I moved to a different custom ROM (SparkOS). So probably some codec error?
Maybe. I thought the codecs are supposed to be shipped with NewPipe
Is this fixed now?
In my case, I still encounter the error with any codec.
@iamkroot Stated earlier:
For me, it got fixed when I moved to a different custom ROM (SparkOS). So probably some codec error?
Looks like a OS problem. I don't think we can do much on app side here...
I thought the codecs are supposed to be shipped with NewPipe
No. These are shipped with the device / OS: https://developer.android.com/guide/topics/media/media-formats
Also take a look at the exoplayer requirements:
If those are conditions are not met then we can't guarantee anything from the app side.
Well, some LineageOS bug, probably.
How can I get any logs for "Unrecoverable Player Error occurred", so that I can report codecs issues to LOS?
People are asking so much for that I now create a Gist for it 😆
Use logcat which is shipped with ADB
There are a bunch of manual online available, e.g:
https://gist.github.com/litetex/ab061f158aeba824713e9a558e8e98ff
Thanks. I'm more or less familiar with logcat, the problem is it generates like 100 events per second. Any hint what I should look for in logcat? Searching for newpipe
in logcat just doesn't return any results.
Hmm I usually - when a problem occurs - I checkout the NewPipe repo (in Android studio) and debug the app via the integrated emulator/on my real device (via USB) as it's much easier to debug 😄 So I don't know the pure commandline tool relatively good.
Maybe the documentation helps: https://developer.android.com/studio/command-line/logcat#filteringOutput
Note also that release builds are usually minimized. I think stuff like debug logging is disabled there.
Note also that release builds are usually minimized. I think stuff like debug logging is disabled there.
Indeed. @homocomputeris Please check the logs of the RC in the pinned issue and see if you get any useful information.
@homocomputeris try filtering logs by pid. Do like logcat --pid=$(pgrep -f org.schabi.newpipe)
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.
Checklist
Steps to reproduce the bug
Actual behaviour
Expected behavior
Logs
Did not get any Error Report page.
Device info