Exoplayer about 10 or 15 minutes the application closes when the screen turns off

It was not a radio application but it differs only by one. The file is not on the device. Exoplayer is the best for playback, also for files from the Internet.
Therefore, this problem also applies to radio applications.

If you want to test. Link:

https://mega.nz/#!atgAwCoR!FAA5zN-dYWp5wkcJjcIHSSkPXfjne8ksu58RYBgS37c

Only small info, the application is only in Polish.

I do not give a link to the google store because I set the download country there and the link in other countries may not be available

On my Samsung S8 running Android OS v9.0 I get the exact same results as you did.

2 Likes

I tested your apk on physical smartphone with android 6 and on AVD with android 9. With the WAV files the application was not closed and the audios continued without problem. As you say, the problem is with ogg audios.

I have now tried an ogg file and another wav, I have left them playing at the same time. It has endured without closing. It may also work on your devices that when the screen is in sleep mode stops sounding … You can try.
ExoTest.apk (7.9 MB)

I had already tried this (by placing a 1 sec silent WAV file to ExoPlayer3.Source, ExoPlayer3.Volume = 0, ExoPlayer3.Loop = true), but unfortunately that doesn’t change the fact that the sound (OGG file) starts to stutter after 50 -60 seconds after the device goes into sleep mode.

1 Like

Kodular is currently using ExoPlayer version 2.8.2 (2018-06-06)
I got a hint from @Boban how to find this after decompiling the APK:

grafik

The current ExoPlayer version is 2.11.3 (2020-02-19): ExoPlayer/RELEASENOTES.md at release-v2 · google/ExoPlayer · GitHub

I really hope @Kodular updates the ExoPlayer to this current version soon, because the ExoPlayer version 2.8.2 is completely unusable due to the issues in background / standby (sleep mode).
As long as this has not happened, I must continue to use the TaifunPlayer (for gapless looping) and otherwise the Player component.

4 Likes

I’ve opened an issue to track this:

6 Likes

See also here:

4 Likes

It’s nice that there exist a library version which contains bug fixes.
The bad thing:
All new exoplayer lib versions use android x.

We still dont use android x.
Means we can not use the newest lib from exoplayer.

2 Likes

Which means we have to wait until Kodular targets Android Q (API 29):
compileSdkVersion = 29
targetSdkVersion = 29

True? If so, when will that happen?

No.
This have nothing to do with this.
Iam talking about “Android X” as library system.

We still use android support libs.

Ok, thanks.

Are you planning to use the new AndroidX library?
Or is there any other solution for the ExoPlayer? It would be a shame if it could no longer be used. Because it is currently completely unusable.

4 Likes

@Kodular it might be a good idea to add the version into the documentation for the exo player component as well as for other components, which use other libraries…

Taifun

5 Likes

Humm, there’s no way to do it without tricks
I’ll think about something by this week

6 Likes

Yes, good idea, but unfortunately that doesn’t solve the problem … :sob:

3 Likes

but it will reduce detective work for the next time… :wink:
Taifun

6 Likes

And use version 2.9.6? I think it’s the last one without androidX. I don’t know if it would solve the problem.

5 Likes

Yes, there were many bugfixes between version 2.8.2 and 2.9.6, maybe one of them fixes this problem. ExoPlayer/RELEASENOTES.md at release-v2 · google/ExoPlayer · GitHub

3 Likes

This problem is related to the doze mode of Android 6 and later
Please do and test what you said in this video carefully
لطفا کارهایی که توی این ویدیو گفته رو با دقت انجام بدید وتست کنید

Hi.
There already exist a topic about it.
Please search first. Thank you