Found an Issue with adaptive brightness not really being adaptive. Indoors it’s at 13% and outside it’s at 100%. Refuses to learn preferences for brightness and dimms/raises to above mentioned values again a few seconds after adjusting brightness.

Related discussions

For Beta should we do buck reports like normal: Under System>Feedback?

Rob ⚡️

Dear Nothing Team,

After updating to Beta 1 of Nothing OS 2.5.1, I encountered several bugs and issues that I’d like to bring to your attention:

1. The Atmospheric Wallpaper effect consistently reverts to a normal wallpaper.

2. The theme color does not apply uniformly across all OS departments. For instance, selecting a monochrome color may not change the notification panel color to match the chosen wallpaper.

3. The pedometer occasionally registers extra steps, counting more than the actual steps taken (e.g., registering 5 steps for a two-step walk).

4. The double-tap lock feature sometimes gets stuck and behaves as if the system is hanging.

5. The music widget occasionally appears blank.

6. During sleep mode, the phone takes an extended time to wake up.

Additionally, I have a few suggestions and tweaks to enhance the overall aesthetics and functionality of the operating system:

1. Include an option to adjust icon size in the customization section.

2. Add an adaptive brightness icon to the notification panel for quick access.

I hope you find this feedback helpful in further improving the user experience of Nothing OS. Thank you for your attention to these matters.

Best regards,

Manoj Barwar

    The volume controls don’t follow “Material You” (system) colors, instead they are black and white.

    Rob ⚡️

    Rob ⚡️

    The battery backup is terrible and it is worse than last update. It has never been good on Phone (1) but this is even worse.

    And the ram management sucks honestly. It keeps closing background apps again and again and resetting phone wallpaper and themes.

    This is due to the atmospheric wallpaper feature.

    Another major!!!! Issue is with 5G. It can’t handle 5G anymore. Battery drains like it’s the flash and phone get’s extremely hot. I can’t even hold it.

    My SOT is 43 mins. This is absolute madness. All the battery drain was from 5G.

    suggestions to add some critical basic features before stable release of in 3.0:

    Auto DND when screen recording so we didn’t accidentally record any notifications.

    Bits instead of bytes as an option for the internet speed meter.

    Can’t see which devices are connected to hotspot but only number of devices. Add a list to allow or block them as in all other ROMs.

    Option to disable bottom bar with the hide keyboard and change input options as it takes too much space.

          I have a question, I have a question about how stable the beta is to be able to update. Is it that the nothing OS is giving me errors, because I don’t have Android 14?

          After replacing the icon pack, the desktop was replaced successfully, but when I cut to the background, it changed to the original icon.

          brajbliss My phone is always on 5G, and 120Hz display. Screen operating time is about 7 hours.

            AmanAnsari Ended up doing this and landing with the “My phone is broken please fix it” side of the support team instead of Beta bug reports.

              Been with the beta for a couple of days now, no major bug noticed other than 1 / 1.5 seconds intermitent lag when interacting with different apps.

              Just passing by to say thanks for the effort the team made to bring a14 to this phone. I understand day by day new devices are releasing on the market, but one year and a half later phone 1 has shown it’s potential. I hope the team keeps improving the device till the last day

              when is the release of 2.5 from 2.05 for nothing 1 or 2, so far “NOTHING”

              Hello, I installed the beta, but I haven’t had any updates since. Should I do something specific for future updates? A new update exists?

              and, if I want to revert to 2.0.5, I get an error “error code -2: pre-build-incremental is different from ro.build.date.utc.” what to do?

              THANKS

                marcopolo_s if you sideloaded the closed beta, you’re screwed. You won’t get updates anymore and you will NOT be updated to stable. The only thing you can do is to unlock the bootloader and reflash an old version of the firmware. And then you’ll be able to do OTA updates to get to stable version 2.0.5. From there you can install the OPEN beta.