How to force an app (Cleantube) to keep active in back ground?

Hi all!
I’m running a Pixel 7a with /e/ 2.9 (android14).
My problem: I use Cleantube app to listen to music, and unfortunately the app stops playing if it is not in foreground. I already tried basic settings, but now I’m stuck…

Please help :frowning:

I don’t know how to keep that app runing on background, but have you tried Newpipe app? It keeps playing even the screen turned off.

I’ve used it but the app is really crap compared to cleantube…

What basic settings have you tried?

No restrictions on battery usage in background, for example.
Does not change anything.

Maybe ask the developer but if you get lucky some who uses cleantube might be able to answer it.

Could also be possible that the app can’t run in the background.

Maybe caffeine can be used as a workaround:
“caffeine” is a tile in Android’s pull down quick settings menu that prevents the display from going to sleep.

Check of CleanTube on exodus Report for com.sgebrelibanos.aderaser 7.4 - εxodus reveals these:

10 permissions
We have found the following permissions in the application:
ACCESS_NETWORK_STATE view network connections
ACCESS_WIFI_STATE view Wi-Fi connections
CHANGE_WIFI_MULTICAST_STATE allow Wi-Fi Multicast reception
FOREGROUND_SERVICE run foreground service
INTERNET have full network access
POST_NOTIFICATIONS
READ_EXTERNAL_STORAGE read the contents of your shared storage
RECORD_AUDIO record audio
WRITE_EXTERNAL_STORAGE modify or delete the contents of your shared storage
BILLING

The icon indicates a ‘Dangerous’ or ‘Special’ level according to Google’s protection levels.
Permissions are actions the application can do on your phone. Learn more…

Did you find how to give the permission FOREGROUND_SERVICE ? Also I note Billing is required and Network / Wi-Fi must not collapse.

2 Likes

I didn’t find anything corresponding to this…

How can one authorize this on /e/OS??

This FOREGROUND_SERVICE is a bit beyond my experience. From a simple search of the term it seems that this is not a user controlled permission. What I really don’t know is if there is a reason or way in which /e/OS might not cooperate with the app’s request for foreground service.

I guess @SylvainM that one should test with all Advanced Privacy toggled off.