Actually if you check the brightness sensor output, you’ll notice the sensor is rather limited, it cuts off way too soon, on both sides (dark and bright), thus erroneously reporting total darkness or full sunlight when it shouldn’t. It also has quite a steep response curve (resolution too low?).
If the proximity IR sensor is of similar built (or even the same part!) I am not surprised it reacts violently to passing tree shadows: Its output must be reporting a change from full light to total darkness with each shadow passing…
I actually can’t, because I don’t have the order number for the smartphone. I can’t even activate my warranty, since I don’t have the original receipt. I wish I could somehow get the order number from the IMEI.
Independet from environmental lightning conditiones after a random operating time (0-30 minutes) the display will dimm down to approx. 30-50% brigthness. Too less, to read comfortabely or see what e.g. car-navigation at a sunny day shows. After an additional random time (minutes, houres) suddenly the brightness will return to full brightness. I could not find any correlation to a specific app or operating mode. Seems to be compleley random when and how long the display will become dimmed down.
Is there a correlation do Android 12 - Update? When will bugfix be available?
SW-Bug in FP4?
Random brightness changes: Just for the record, I got some too yesterday. I was reading something on the phone in a not very brightly lit room, without moving (nothing to change the amount of light the brightness sensor receives), and yet, all of a sudden, it got brighter. Then, a couple seconds later, it dimmed back to the previous level.
I moved the phone a little to see if I could trigger it again, to no avail. Go figure.