after second reboot within 5 minutes the accessibility service does not start up

[evil-raider]

Have you checked if an issue already exists for this bug?

• Nobody else has reported this bug before

Have you tried restarting your device?

• I have tried restarting my device and that did not help

What happened that you did not expect?

I reboot my device, do some quick work (1-2 minutes), and reboot again. After the second reboot, I get a "expert mode stooped unexpectedly" "not auto restarting because last auto started less than 5 minutes ago"

notification and the service doesn't start.

What did you expect to happen?

I expect the application to correctly detect not a service crash, but a correct termination due to a reboot, and after a correct quick reboot, within 5 minutes of another reboot, it will start correctly

What would the developer need to do to reproduce the bug?

Reboot the device with the key mapper running

Wait for the key mapper to load

Reboot the device 1-2 minutes after the previous reboot

The service fails to start, displaying a notification in the notification area

App version

4.3.0-foss 257

Android version

android 16, nothing os 4.1

Device model and manufacturer

nothing phone (3a)

Extra info

• My device is rooted

[sds100]

How come you are only booting your device for a few minutes and then shutting down again? I tried to keep the logic simple even though this situation could happen

[evil-raider]

Simple is cool, but it shouldn't be stupid, and a simple timer isn't appropriate here.

as i said, I do my own thing. I didn't say I was rebooting for fun. 😊 For example, I test Tasker profiles and need clean boot for testing autostart, or enable kernelSU modules after a catched bootloop (or just enabling new\disabling old), or reboot to flash the clean init_boot image for OTA update.