Search results


  1. B

    Ambient display

    Since update 11.0.4.0, the ambient display no longer works on mi 9T / redmi K20. It now behaves like a standard AOD that no longer adapts to ambient light! Whereas it used to work perfectly before! What has happened? The battery drains unnecessarily at night when I'm sleeping... and I have to...
  2. B

    Known Issues (Weekly ROM)

    Since update 11.0.4.0, the ambient display no longer works on mi 9T / redmi K20. It now behaves like a standard AOD that no longer adapts to ambient light! Whereas it used to work perfectly before! What has happened? The battery drains unnecessarily at night when I'm sleeping... and I have to...
  3. B

    New Ambient display has flaws

    Hi, Is it possible to request reactivity to the initial operation? Or is there a possible workaround? BB
  4. B

    New Ambient display has flaws

    That's not good news ! I don't understand the utility of keeping a screen on in total darkness... I'm now forced to set time slots... not very efficient. Why not as an option ? BB
  5. B

    New Ambient display has flaws

    Can anyone confirm the bug on redmi K20 / mi 9T?
  6. B

    New Ambient display has flaws

    Hi, I'll confirm. Since the 11.0.4.0 stable update, I have a problem with the ambient display. The screen no longer turns off when it is completely dark. It worked very well with the previous version (V11.0.2.0). Can anyone confirm this bug? Thanks. BB
  7. B

    MIUI 11 MIUI 11.0 STABLE RELEASE

    Hi, I just updated my mi 9T from stable version 11.0.2.0 to 11.0.4.0. I have a problem with the ambient display. The screen no longer turns off when it is completely dark. It worked very well with the previous version (V11.0.2.0). Can anyone confirm this bug? Thanks. BB
  8. B

    Ambient display

    No one has the problem or no one uses the ambient display? BB
  9. B

    Ambient display

    Hi, Since the 11.0.4.0 stable update, I have a problem with the ambient display. The screen no longer turns off when it is completely dark. It worked very well with the previous version (V11.0.2.0). Can anyone confirm this bug? Thanks. BB