I'm embarrassed to have done this, but here it is. 
Was working on a macro that took several actions if the screen triggered on while the phone was locked. In the course of troubleshooting, I disabled the "phone locked" constraint on the "Screen on" trigger. I made the desired changes to the macro and then saved it. BUT... I forgot that I had disabled the trigger constraint. As a result, I now have a situation where the phone is locked and the macro is (apparently) acting like T='Screen on' and the first action that satisfies the IF loop is "screen off"! The lock screen comes on when I tap the power button, but of course, doesn't stay on long enough to enter my PIN. The only way I can get the screen to stay on is if I tap the screen while it is off; this displays the clock (ambient mode?) but I can't do anything useful from there. If I swipe up, the lock screen flashes on for a moment. Trying the power button is no help either. On this phone, the power button doubles as a fingerprint sensor; touching but not pressing the power button (IOW, fingerprint unlock) brings up the PIN screen, while pressing brings up the lockscreen with the wallpaper background.
Some things that may be relevant:
I can't boot into Safe mode or Recovery mode, because they both require the phone to be off first. Thing is, I can't access the power menu (long-pressing the Power button just flashes the screen on momentarily). The only thing I can think of is to let the battery drain down to 0% and then power up in Safe mode, and then delete the macro causing the problem. But that could take days, since the screen is off. I'm hoping someone has an idea I haven't thought of.
Was working on a macro that took several actions if the screen triggered on while the phone was locked. In the course of troubleshooting, I disabled the "phone locked" constraint on the "Screen on" trigger. I made the desired changes to the macro and then saved it. BUT... I forgot that I had disabled the trigger constraint. As a result, I now have a situation where the phone is locked and the macro is (apparently) acting like T='Screen on' and the first action that satisfies the IF loop is "screen off"! The lock screen comes on when I tap the power button, but of course, doesn't stay on long enough to enter my PIN. The only way I can get the screen to stay on is if I tap the screen while it is off; this displays the clock (ambient mode?) but I can't do anything useful from there. If I swipe up, the lock screen flashes on for a moment. Trying the power button is no help either. On this phone, the power button doubles as a fingerprint sensor; touching but not pressing the power button (IOW, fingerprint unlock) brings up the PIN screen, while pressing brings up the lockscreen with the wallpaper background.
Some things that may be relevant:
- Phone is Motorola Razr+ (known internationally as RAZR 40 Ultra); OS is Android 13
- Smart Unlock is enabled. This prevents having to unlock when at home (I'm at home now). I used another macro that locked the phone when flipped over. This was convenient for troubleshooting the first macro, since it only required a flick of the wrist to lock, versus having to dig into Settings to disable Smart Unlock and then re-enabling it when done. BUT... locking it this way uses device admin, which requires a PIN even though I'm home.
- The power menu (to restart or power off) is accessed by long-pressing the Power button
- I tried an incoming phone call to see if it acted differently. It didn't, but I was able to swipe up and answer the call before the screen went off. The call was normal, but the screen stayed off, so it was no help.
- I have ADB enabled, but the screen flashes on/off as soon as I plug in the USB cable.
I can't boot into Safe mode or Recovery mode, because they both require the phone to be off first. Thing is, I can't access the power menu (long-pressing the Power button just flashes the screen on momentarily). The only thing I can think of is to let the battery drain down to 0% and then power up in Safe mode, and then delete the macro causing the problem. But that could take days, since the screen is off. I'm hoping someone has an idea I haven't thought of.
Last edited:
