BAD NIGHT-MODE

[Mark EO]

I have a Tasker Task that works fine when ran normally on my Oneplus Nord N200 5G phone.  It is a 30 second buzzer, with my having it as 30 1 second segments in order to make in interruptable via a Scene-provided buzzer-off button, although usually I'll just let it run the full 30 seconds.  Either way, at the end it always destroys the scene as intended including the button of course at the end.  But that's got nothing to do with my problem as far as I can tell.  What's wrong is that either the sensors or internal phone processes are screwing things up at night, causing the Task to take several minutes to complete rather than the normal 30 seconds.  And it's likely nothing to do with the dark, but is likely just the fact that at night I place the phone upside down under my pillow, which is the primary purpose of the buzzer...especially for it to be under my pillow throughout the night, buzzing its little heart away.  I would simply like it to complete the task in the normal amount of time of 30 seconds each time (and I intentionally have it going off every 30 minutes), even when it is buried under my pillow.  I've been trying different things to work around this problem, but so far nothing that I've thought of has worked.  I've already used the Tasker Permissions app from my Windows computer to give the phone EVERY permission that it didn't yet have, including of the screen on/off and screen timeout controls, which DO make the screen come on with my now having selected this action, but only BRIEFLY for a couple of seconds, regardless of what I've set the screen timeout value to.  So perhaps a process in Android is wrestling the controls back away from Tasker, due to perhaps the Oneplus "Pocket Mode" program, which in Android 12 has seemingly NO way to disable it.  But if I could somehow temporarily just while the task is running for 30 seconds disable the proximity sensor, then perhaps that could solve the problem?  Either way, being that the Task always DOES complete eventually at some point, the obvious problem is more centered around the screen being OFF at the time, which I've somewhat demonstrated that when I turn it back on, it makes it run the task at a normal speed...IF I could just get it to stay on!  But the problem is that it just doesn't stick for more than a couple of seconds no matter what I've tried...the system just keeps turning the screen back off and then this slows it back down, indicating that it must be throwing Tasker into a super-low priority state/condition, as though in a super-low-priority background-running mode.  So, ultimately I probably just need to keep it in a regular normal-priority condition somehow, which is what I'm trying to figure out how to do.  And at one point I even did a screen-on action at the start of each new segment--once per second--but it quickly produces a Tasker "Error" something about the screen not being able to be turned on or something like that, which was just a seemingly nonsensical message, without it revealing what the true problem is, whatever it might truly be.  Perhaps it's competing with the "Pocket Mode" program.  Or perhaps it's just Android's own reaction to the proximity sensor with the phone being buried as it is under the pillow...I don't know.  And I'm not sure at this point if turning it face-up under the pillow might make a difference compared to my currently always having it face-down under the pillow.  And just to clarify here, the phone MUST be under the pillow for it to do what's intended of it at night.  So any clever ideas on how I might disable the proximity sensor or whatever else I might try in order to make Tasker function in a normal state at a normal speed will be greatly appreciated.  And WHY I'm doing this is because it's a method associated with lucid dreaming control, for which there are no alternative ways of doing what's needed, just in case anyone wants to know about the WHY that I'm doing this.  Thanks.   :)