Google shuts down the dream of a dark mode for Android
Keen mechanical man users who’ve been following a somewhat obscure Google Issue hunter thread from November of last year celebrated associate degree exciting new development these days. The thread, within which a user asked a few dark mode to enhance battery life on mechanical man phones with OLED screens, had been marked “fixed,” with a Google worker language the mechanical man engineering team had another this feature which it might “be obtainable in a very future mechanical man unleash.”
Unfortunately, Google currently says that was a slip. “Unfortunately, this bug was closed untimely because of a miscommunication with the team that handles AOSP problems,” the corporate same in a very statement given to mechanical man Police. “What we've got another in a very future mechanical man unleash could be a developer-facing setting (via Developer Options) to toggle the -night UI mode qualifier, which can build it easier for developers to make and take a look at apps that implement night mode.” Google another that “if it’s any consolation, area unit going to} additionally not be adding Hot Dog Mode (where all UI parts are yellow and red),” that is clearly not any consolation in any respect.
Users had suffered the initial thread sky-high, with several praiseful Google ofr finally implementing a system-level night mode feature. the sole choice now could be the restrained dark mode that, up till last October, was exclusive to the pel two. That feature permits users to vary from a lightweight to dark theme supported their phone’s wallpaper, and it came to the initial pel with mechanical man eight.1, as noted by AndroidPolice. Hopefully Google decides to expand that, or probably take into thought the quantity of users WHO square measure hopeful for a stronger UI resolution for bright screens and battery life conservation.
Update at 8:03PM ET, 2/23: another statement from Google informative that a dark mode for mechanical man isn't actually on its means, which the corporate miscommunicated it on the initial Google Issue hunter thread.