Floating Buttons don't like my phone (weird behavior)

[ReiWei]

I'm sorry if this has been discussed, I searched and couldn't find anything.

This is seemingly a phone issue, but it'd be super cool if I could fix it.

I have a Galaxy Z Fold 3, if that matters.

So, quite simple but weird problem; when I make a floating button that does anything at all, it takes literally ~1 second (which, in practice, is a very long time if your doing something repeatedly) for the button to reset to an unpushed state. If I hit it many times without waiting, it has like buffering problems... it sometimes works, sometimes doesn't, but acts funny and weird the whole time. Like will continue to push it several times after I've stopped.

So, basically, it gets overloaded and tries to catch up. That's understandable, the question is, why in the world does this phone take a full second to stop "pushing" the button?

I thank any and all helpers in advance.

 

[ReiWei]

TLDR, I have a 2-3 second delay for floating buttons and a 4-5 second delay attempting to and then failing at reading the screen, after the most recent update; and it seems at least partially due to a proximity screen off state.
___________________________________

Okay, so the new version release (5.43.6) has exacerbated this issue two to three fold. It now takes a minimum of two seconds, and often more, for a button to reset and be usable again. This means that I have to wait two to three seconds to be able to do anything else in the macro. Every subsequent action gets queued and then bogs down my phone and I can't do anything until they all finish.

But, the even more troubling development that's popped up is that reading the screen now has a major issue. It's basically broken...

Here's my setup, I'm on android 13 on a Z Fold 3. For years I have used a proximity screen off app that mimics how the screen turns off during a phone call. The screen doesn't turn off like normal, as soon as the proximity sensor is cleared, it pops back on. No need for unlocking or anything, as it was never truly off. And most importantly, the phone behaves as if the screen is on. So I can read the screen and do ui clicks and whatnot when the screen is off like this. (BTW, it'd be super cool if Macrodroid implemented this ability, so I didn't have to have another app running just to accomplish this screen "off" state. )

One other thing that might play a role, Samsungs apparently don't have a real proximity sensor, they have a virtual one. I can't use any Macrodroid proximity sensor triggers normally and no other sensor test app registers the proximity sensor on my S10e or this Fold. (I'm really not a fan of Samsung it turns out, but I didn't know that before I got the Fold, and I can't give up it's coolness , and the S10e is my work phone so I can watch TV on my xreal glasses. )

But, I can "trick" the sensor to start working by placing my palm on the phone, as there is a completely useless feature (seriosuly, who besides my being forced to would use this? ) to turn off the screen by placing your whole hand on it. So, everytime I restart the phone, I have to put my hand on the screen for it to turn off, and then after that, the proximity sensor starts registering like "normal" (it's still a bit hit or miss, and takes a second sometimes to register, and is kinda dependent on light, also... It's all around silly) A very very weird issue, but whatever, I have a phone that folds finally after 30 years of wanting one (back then, phones weren't on my radar, I just wanted some sort of display that folded that I could watch TV on or something )

Okay, I'm very sorry for that extremely long backstory...So the prox screen off and then using Macrodroid to read the screen worked perfectly up until the new version. Now, it is almost completely broken. The screen read action usually (but not always) works like normal when I restart my phone, or restart Macrodroid, but the very first time I use the prox screen off, it breaks totally. It then takes 4 to 5 seconds to try to read the screen, and then ultimately fails, every time. And, this continues even when the prox sensor is cleared and the screen turns back on. And persists until either the phone or Macrodroid is restarted (usually, sometimes it's still broken)!

This is very sad, as I do so much that relies on reading the screen, and it's basically borked on my phone.

So...

Any ideas?
Pretty please, I'm fairly desperate.

 

[ReiWei]

Okay, so... All of that proximity screen off stuff mlght have been a case of incorrect correlation.

I believe the screen reading issue was down to my phone getting bogged down by reading a notification from a speedometer app every time it updated.

So like every second, or so, the notification trigger went off and updated a few variables. This worked perfectly up until the recent update, though, so there is still some bug in this version that doesn't like my phone. And the floating buttons still take 2-3 seconds to reset, which is worse than last version.

 

[MacroDroidDev]

Please use report a bug in the troubleshooting section and include the relevant macro. Without seeing the exact macro configuration I can't speculate on what the issue might be.

 

[ReiWei]

I don't think this is a bug, I think my phone is just stupid. I know this is just a form reply, but there isn't any "relevant macro". Every single floating button I make, no matter what it does (even if it does nothing) takes one to two seconds or more to "reset". The button greys out when you press it, and it takes that long to go back to normal. So if I just make a macro with a button that causes a blip vibration. And I press the button several times quickly, the vibrations will happen one after the other with about a second between them and continue for some time after I stop pressing the button. This only happens on this phone, Z Fold 3.

 

[Endercraft]

Most likely means your phone is slow. I've had this happen when I have a lots of MacroDroid elements on screen, it usuallys takes a bit to update.

 

[ReiWei]

I mean, it's a Galaxy Z Fold 3. It's not a 5, but it's also not slow.

I can turn off every macro I have and terminate all running apps, and make one single macro that has a floating button with any action at all: no action, vibrate, anything. And it takes 1-2+ seconds to return to unpressed and usable state.

There's something going on with my phone that's not normal. I guess maybe this is the wrong place to ask, I just thought you guys are smart and know MacroDroid, and this type of thing only seems to happen with specifically floating buttons.