Question regarding compliance with F-Droid rules

It does not record the results of survival attempts, but simply demonstrates them to the user by playing a sound while it is alive, and also showing running processes when the application is opened. Maybe someday I’ll add a record to the database, but for now it’s a personal testing tool. Conducting performance analysis is more difficult than simply showing the results to the user. For example, we need to know the time an application died and how quickly it restarted. But this is easiest for the user to see. For the system, constantly recording time is a burden. The funny thing here is that the app is effective on most devices with default settings. So, under normal circumstances, tracking device statistics is pointless. In other cases, the user himself creates the load, and then it is easier for him to detect the fall. For example, a user can intentionally trigger a RAM overflow or change the reboot settings on Xiaomi from the default to the most hostile and then see what happens after the RAM overflow and reboot. If we’re talking about testing individual survival techniques, this app isn’t for that; it tests them together. Maybe someday I’ll create a special mode or app for testing them individually. But individually, they’re not as effective, meaning we lose the full picture. For example, Set Exact Alarm doesn’t work without Wake Lock because the phone enters Doze.