If a device is too slow when logging into PTC, i might get stuck in a bootloop

[ccev]

(was told to tag @crhbetz)

The problem:

MAD will detect below screenshot as ScreenType.NOGGL, thinking it selected the wrong birthdate, causing it to reset game data and reboot the device. MAD will then try to log into the account again, detect the page as ScreenType.NOGGL and reboot the device again. And so on. The only way to stop this as the user is to make a google account or to pause mad.

I'd imagine that a similiar issue could occur when using Google as well.

Possible solutions I could think of:

• The sleep duration after pressing the login button is a hardcoded 50 seconds. Let the user define this value in the device config.
• If MAD detected a correct LOGINSELECT, PTC or (whatever the google one is called) earlier, block it from detecting NOGGL again
• Improve the NOGGL detection: No Google Button but a Niantic Kids Button? -> NOGGL. Else: sleep