Hello, yes, this is normal though. Automate needs permissions to change system parameters. You don’t need to give all permissions anyway. You can check the flow diagram to verify that the flow does nothing except change brightness levels to some default level (which can be edited by the user if necessary).
The way I understand it is that the only permission that is really necessary is “modify system settings.”
Well, I gave all the permissions so the Automate Script could be installed. I put the Brightness - which is on manual since four years (except for 1 year with a working YAAB) - on minimum and started your flow. It immediately jumped up to a bit less of half of the bar and stays there now. No change if I put the phone under a lamp or put my finger on top of the sensor. I shall test it on a sunny day. I’m sure there will be at least one sunny day in the next few weeks to next few months I’m sure.
Tell me how it goes. You can tweak the default parameters by changing the percentage numbers in the flow blocks, noticing that the way Android set them up isn’t very intuitive. Just increase or decrease the numbers until you find your best set.
You can also change the “day or night” hours, “day” is currently set for 6 am to 8 pm.
Very nice that there are still FP2 users around putting energy into it.
I have the strong impression that FP3 is luring more (FP2) customers than there were to be expected. I thought the longevity and sustainability aspect would let more FP2 users keep their phone for longer. But to me now it feels reading through this forum lately, like if almost every second FP2 user had faced so many major problems that it was an urgend need to purchase the FP3 and get rid of the FP2…
My two family FP2, both running FP Open, still work quite well, and fast enough for my needs. I don’t ever think about buying an FP3 at the moment, and will probably never buy one if it can’t work with an Open OS and OpenGAPPS.
I’ll search around for a non-GAFA solution the day I really need it. It would be a pity if this solution isn’t a Fairphone, but I’m confident that by then someone will have proposed a non-GAFA solution for the latest Fairphone model.
Please understand the implications for this. Imagine you buy a brand new car and the fricken electric windows wont wind down. Producers says "thanks for telling us. Your opinion is important to us."and thats it.
Four years you sigh out in dissappoint, but you’re stuck with it. Every time you need an open window, you are sigh dissappointed.
That is over now - at least for this brightness thing.
I don’t recognize the “Device interactive?” question line on the log, have never seen it. Did something change in device’s permissions or root authorizations?
Probably a block syntax change or a change in permissions. If you find the fix, please post it here (for different reasons I can’t use the new version).
…
