1

App Factory (kid apps) crash/killed on Android 12

On Android 11, works fine.  On Android 12, works fine until a day or so later, when the notification is gone and the profile won't trigger.

Using tasker and app factory 5.12.0, target Android version 26, basic permission set like LOCATION, NETWORK, WAKE LOCK, EXTERNAL STORAGE, etc. When installed it asks for location and storage permissions, and Display over Other Apps, which I grant.  I also disabled battery optimization.

The Profile conditions only check for Display On, GPS On, and WiFi connected. 

I know Android 12 has issues with killing phantom processes described here, but I've tried the fix using ADB with no change in the behavior.

I'm also following the steps to keep the app alive that you describe in your FAQ

Can you tell me how Tasker app factory kid apps attempt to run in the foreground as a service?  If it differs from how Tasker does it?  Or if you know of anything on Android 12 that has changed to break it?

Thank you

Follow

2 replies

Votes Newest Oldest
T4

Thanks João, after much trial and error (each test takes several days), I found the problem.

Only seems to manifest on Android 12 (Pixel 3).

The problem was in the task.  At the end of the task, I loop to the beginning of the task IF the profile is still active.  I can't use a profile repeating Time Context because I need it to trigger immediately on Screen On, but I want it to repeat every 5 minutes if the screen is still on.

I don't know of a way this logic is still possible, other than the way I have been doing it.  It works great on Android 11.

The only thing I can think of, is that Android 12 doesn't like it running on a loop.

Comment

Hi. Kid apps should run just like Tasker itself. They use the same code underneath.

Are you absolutely sure you didn't forget any of the steps in https://dontkillmyapp.com/ for your phone's brand?

Comment
Reply