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

[bodymindpower (Anke)]

@xBorx

What version of exoplayer is kodular currently using?

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:

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.

[Conor]

I’ve opened an issue to track this:

Update ExoPlayer library

[bodymindpower (Anke)]

See also here:

ExoPlayer 2.11 - What’s new

[Mika]

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.

[bodymindpower (Anke)]

@Mika

Means we can not use the newest lib from exoplayer.

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

True? If so, when will that happen?

[Mika]

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

We still use android support libs.

[bodymindpower (Anke)]

@Mika

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.

[Taifun]

@bodymindpower

Kodular is currently using ExoPlayer version 2.8.2 (2018-06-06)

@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

[Diego (Diego Barreiro Pérez)]

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

[bodymindpower (Anke)]

@Taifun

it might be a good idea to add the version into the documentation for the exo player

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

[Taifun]

@bodymindpower

unfortunately that doesn’t solve the problem

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

[xBorx (Borja)]

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.

[bodymindpower (Anke)]

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

[emad_pirayesh]

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

How to WhiteList app in Doze mode Android 6.0

[Mika]

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

[DevYB (Ayoub Mounchid)]

@bodymindpower

Yes, on some Chinese devices (eg Xiaomi, OnePlus) there are looping issues (gaps) with the TaifunPlayer.

Hi @bodymindpower,
Could you describe the problem better? With player component or @Taifun player extension the song go always in loop, if we use some chinese devices?

Thank you in advice.

PS: I’m asking about it because I want to switch from Exoplayer, and I want to know if the player component and taifun player works good.

[bodymindpower (Anke)]

@DevYB

With player component or @Taifun player extension the song go always in loop, if we use some chinese devices?

I have posted on these questions several times, see e.g. here:

Playing a loop, the player adds a space between the end and the beginning of the audio

Note: You must use audio format: ogg or wav (mp3 is not loop-able, because it adds silence at the beginning & and end of a track) ogg is the only compressed audio format that is loop-able on Android see also here: [PAID] HLS Video Player Extension

[PAID] HLS Video Player Extension

I have some experience and everything tested to get perfect loops with all loop-able audio formats Android: ogg, flac, wav & iOS: ALAC, IM4A. Between ogg and wav formats, I had found no differences in the looping. However, the looping on some Chinese devices (Xiaomi, OnePlus, …) with the TaifunPlayer no longer works. This also applies to the wav (PMC) format. Post your “perfectly looped” ogg sound here, I’ll check it. PS: On iOS (Xcode, Swift 4) I never had problems with the looping.

Suggestions / request for useful (much needed) extensions

Probably these extensions are not quite simple, and are aimed at experienced extension creators. Two suggestions for new extensions: An audio player that masters seamless (gapless) looping and that also works in the background (ie when the device is in sleep / idle mode or when the current screen is not visible after pressing the device home button). Ideally, the player should also be capable of streaming. Note: The Player component does not loop seamlessly since Android 6. The TaifunPlaye…

Playing a loop, the player adds a space between the end and the beginning of the audio

The Player component does not loop seamlessly since Android 6. The ExoPlayer doesn’t loop gaplessly since Kodular Eagle, see here: (1) ExoPlayer is no longer looping gapless. (2) App crashes at ExoPlayer.Completed event try the TaifunPlayer extension which can loop audio seamlessly: App Inventor Extensions: Audio Player | Pura Vida Apps see point 3 or wait for bugfix of ExoPlayer

[bodymindpower (Anke)]

@DevYB

and I want to know if the player component and taifun player works good

See here from my 3rd link:

Note: The Player component does not loop seamlessly since Android 6. The TaifunPlayer does not loop gaplessly on specific Chinese devices (OnePlus, Xiaomi, …) anymore. (Finally I found the reason for this: these manufacturers fade out audio tracks with a length ≥ 30000ms for 165ms, which creates the gap.)

I wrote to OnePlus and explained this issue and we are still in discussion about it.