Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Background activity launch (BAL) privileges" in Android 15 #223

Open
24kris6 opened this issue Nov 7, 2024 · 8 comments
Open

"Background activity launch (BAL) privileges" in Android 15 #223

24kris6 opened this issue Nov 7, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@24kris6
Copy link

24kris6 commented Nov 7, 2024

https://developer.android.com/about/versions/15/behavior-changes-15#secured-bal

I believe this Android 15 change pretty much breaks apps like Paperize. The wallpaper doesn't change automatically on time, I have to open the app manually for the wallpaper to change itself.

@24kris6 24kris6 added the bug Something isn't working label Nov 7, 2024
@Anthonyy232
Copy link
Owner

Love Android! \s

I'll take a look at this relatively soon, thanks for pointing it out!

@Anthonyy232
Copy link
Owner

Can I ask what device and OS version you have by the way? (I'm assuming Pixel 9 with Android 15, but just to be clear)

@24kris6
Copy link
Author

24kris6 commented Nov 7, 2024

Can I ask what device and OS version you have by the way? (I'm assuming Pixel 9 with Android 15, but just to be clear)

My bad, I should have specified it in the OP.
Current device is a Vivo X200 Pro running OriginOS 5 (Android 15).
Normally, enabling "high background usage" instead of "smart control" in the settings is enough to prevent the China ROM from killing app in the background, but in Android 15 it doesn't seem to do the trick anymore.

I had Paperize working perfectly on an Oppo Find X7 Ultra with Android 14, so while it's not the same phone, I just assumed something changed in Android 15.

@stephanzwicknagl
Copy link

stephanzwicknagl commented Nov 8, 2024

(I'm assuming Pixel 9 with Android 15, but just to be clear)

I've been having this issue on my Pixel 9 ever since I updated to Android 15.

@Anthonyy232
Copy link
Owner

Anthonyy232 commented Nov 10, 2024

I'm not able to replicate this on my API 35 Pixel emulator even after closing the app. Most likely, emulators don't capture an accurate power behavior. Are any of you guys able to extract logs either with some on-device log app or using Android Studio? I believe it if it some sort of system error, it should show in the logcat.

I have a Samsung and we are still on Android 14 (SDK 34) so unfortunately I don't have an Android 15 device to test with.

image

Just to clarify though, what version of the app are you guys running? Can I get the version number?

@24kris6
Copy link
Author

24kris6 commented Nov 12, 2024

I was on 2.3.0. Just updated to 2.3.2, we'll see how it goes

How would I go about extracting a log using Android Studio? It's a bit overwhelming. It does recognize my device, however I can't find any logs pertaining to Paperize.

@Anthonyy232
Copy link
Owner

You click the button on the side
image

Then you select the device (so your phone I assume), and then type in crash or error, and juts skim the results to see if any of them mention Paperize.
image

You would do this when the app is about to change wallpaper because the logs aren't kept for very long. It's okay though if it doesn't work! It's my job to fix this anyways :D

@Anthonyy232
Copy link
Owner

Anyone able to test a build for me to see if this occurs? Seeing as I can't reproduce this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants