Nothing OS 5.0 | Open Beta Feedback

Zac 🛸 · 2026-08-26T12:26:00+00:00

Hey everyone, ⚡️ The Nothing OS 5.0 beta is rolling out, and if you’re on it, you’ve probably already got thoughts. This thread is the place to share them. 💬 Whether you’ve come across a bug, found a feature that you want to share, or just want to hear what others are experiencing, jump in. The more people comparing notes, the easier it is to work out what’s a widespread issue and what’s a one-off. A few things worth discussing: Bugs you’ve encountered and how much they’re affecting day-to-day use Surprising features and how you are using them Anything that’s actually working better than anticipated What you’d want addressed before the stable release 🚨 While this thread is a great place to discuss, the official feedback channels are still the most reliable way to get issues in front of the team, so if you’ve found something reproducible, make sure it’s logged there too with the following steps right on your device. ⚙️ Settings > System > Feedback.

itc_c

Cavax I guess that is the only option for me. As tapping on Build number doesnt show the usual message that developer settings is open now. Instead i dont get anything and dev options arent enabled. tried restarting multiple times.

its odd that something so basic breaks.

anirudh_hoon

hi guys basically what is happening on my nothing phone 2a background apps are like they are getting automatically closed after not using them for a whole night after i go to sleep and when i wake up all the recent background apps are being cleared
but i don’t know about it and how to fix it basically if someone knows please help me to figure it out

itc_c

Another important point to note (not of concern), I have Phone 3 , 16GB RAM and the memory consumption has increased from 40-50% for my usage to 60-69% after moving to NOS5. I dont mind it using more RAM cause most of it is available but wanted to highlight it if its occurring for any one else and is expected.

RiyanR

zazalondaridze visit nothing store😂

SuviseshaKumarRajaguru

Zac 🛸 Hi, I’m using Nothing Phone 3. I have updated the OS to the 5.0 beta version, but after 1 week, all browsers crashed and won’t open at all, and many applications aren’t responding, and several are taking time to open as well.

DJ

SuviseshaKumarRajaguru To fix the browser issue. Enable developer options and reboot your device.

gechenhui

DenkLaut I found a way to solve this problem,keep the screen unlocked,use another phone to dail ur nothing phone, when it’s ringing,u wll see pin screen overlay,then press power button one time,that’s it! No need to restart.

ChrisJ_Joseph_P1NpRo6vMr

Device : Nothing phone 4a pro

OS : Build number

FroggerPro-C5.0-260902-1559-IND

I don’t know if this is a bug but , if you notice at the bottom you can see the essential voice pill overlapping the quick settings (don’t mind me fidgeting with the volume slider😅)

ken_s

Open Chrome, and it gets stuck. Even trying to open “Developer Mode” doesn’t help. It’s been a long time, and it’s so common, why hasn’t it been fixed yet??

TechDepthStudio

ken_s There should be a pattern that makes this issue to occur. I have upgraded from 4.1 to 5.0 beta by directly installing the update zip and not through OTA. The first thing I did after the reboot was to enable the developer options and I have never experienced any issues with the browser. No crashes with any apps so far. The software experience so far feels smoother than Samsung Z Fold 8 Ultra stable build.

My device’s build number: Metroid-C5.0-260819-1642-EEA

anirudh_hoon

anirudh_hoon ??

grepGander

anirudh_hoon

anirudh_hoon my nothing phone 2a

miha36

Bug report — Nothing OS 5.0 Open Beta (Phone 3)

Title

System-wide UI freeze and app launch failure, triggered by Chrome / Android System WebView

Device information

Device: Nothing Phone (3)
Model number: A024
Nothing OS version: 5.0 Open Beta
Android version: 17
Network: 4G, Bluetooth earbuds connected
Storage: sufficient free space (checked, not full)

Summary

After installing the Nothing OS 5.0 Open Beta, the device enters a progressive system-wide unresponsive state. The trigger is reliably Chrome: as soon as Chrome is launched (or fails to launch), the failure cascades to every other app on the device, including system apps such as Settings and the Phone (dialer) app.

The behaviour strongly suggests an Android System WebView crash loop, since every affected surface is WebView-backed and the cascade begins at the browser.

Steps to reproduce

Boot the device normally.
Open Chrome. It either fails to open entirely, or opens but web searches never load.
Attempt to open any other app (Settings, Phone, etc.).
Apps now open very slowly or not at all. The degradation persists until reboot.

Expected behaviour

Chrome opens and loads pages; other apps remain unaffected regardless of Chrome’s state.

Actual behaviour

Chrome fails to open, or opens but cannot load any page.
After that, the failure spreads system-wide: all apps become slow or fail to launch.
The Phone (dialer) app stops opening entirely — the device cannot place calls.
Settings becomes unresponsive and must be force-closed.
Settings freezes reliably and specifically when opening Settings > Apps > Show system apps > Android System WebView. The screen locks up and Settings has to be closed.
The state only clears with a full reboot, then recurs.

Impact / severity

High. The device is not usable as a daily driver:

No web browsing.
No outgoing calls when the state is triggered.
System settings cannot be reliably accessed.

Troubleshooting already performed (all without resolution)

Verified free storage — not full.
Full power-cycle reboot — problem recurs.
Cleared Chrome cache — no effect.
Cleared Google Play Services cache — no effect.
Ruled out network causes: Private DNS disabled, no VPN active; other network activity is unaffected while the browser fails.
Checked for a newer beta build — none available.
Checked Play Store for Chrome / WebView updates — none available.
Safe mode: problem still occurs. Third-party apps are therefore ruled out; this points to a system component.
Could not uninstall Android System WebView updates: Settings freezes on that exact screen, and the stable “Android System WebView” package is not listed in the Play Store on this device (only Dev / Canary / Beta variants appear).

Additional notes

Developer options cannot be enabled on this build: tapping “Build number” seven times in Settings > About phone > Android version produces no response and no counter toast, and “Developer options” does not appear under Settings > System. This also blocks USB debugging, so no adb logs could be collected manually — please rely on the logs attached automatically by the Beta Hub.
The inability to enable developer options may itself be a separate bug in this build.

Requested outcome

Investigation into the Android System WebView / Chrome crash loop on this build, and a fix in the next Open Beta release.

(the report was made by claude just to save time)

TheoBlanca

Ok , so I have really bad experience right now with OS 5.0…

Hi everyone,
I’m reaching out to see if anyone else is experiencing severe app launch delays and browser freezes on Nothing OS 5.0, along with a very strange performance behavior.
The Issues:
-App Launch Delays & Hangs: Frequently used apps—like Google Pay—take an unusually long time to launch or hang on load, despite being on a solid 5G connection. Weekly-use apps are experiencing similar opening delays.
-Chrome is Completely Broken: Chrome is currently stuck and unresponsive when loading websites. It hung so severely during authentication that I almost got locked out of one of my accounts.

-Brave has also shown similar behavior where pages fail to load.
The Strange Behavior (Why I Can’t Report It via Feedback):
Every time I attempt to reproduce this to submit a bug report via Settings > Feedback > Record Screen, the device suddenly runs flawlessly:
Apps that were hanging (like Brave and daily-use apps) open instantly at normal speeds the moment screen recording starts.
It appears that triggering the feedback screen recorder temporarily wakes the CPU governors or boosts clock speeds out of an aggressive throttle state, masking the issue entirely.

But once i stop recording after sometime the app open delays starts again.

Because the system may speeds up during recording, I cannot capture the actual freeze/delay to attach to a bug report. Chrome remains completely unusable otherwise.
Has anyone encountered this CPU throttling/scheduling anomaly or found a workaround for the Chrome freezing on Nothing OS 5.0? Any help or suggestions would be appreciated!

miha36

TheoBlanca
Partial workaround: since Chrome is the reliable trigger, disabling it keeps the
system stable. Long-press the Chrome icon → App info → Force stop → Disable, then
reboot. This route avoids Settings > Apps, which freezes on this build.
For browsing in the meantime, Firefox works: it uses its own Gecko engine instead
of Android System WebView, so it is unaffected by the crash loop. All other
mainstream browsers (Edge, Opera, Brave, Samsung Browser) are WebView-based and
hit the same issue.

TheoBlanca

I understand this will work but what about those stuff which requires Chrome as default….. There are stuff like opening link in gmail which are unable to open in mozilla and some stuff still seeks default Chrome browser or chrome page, that won’t open at all then.

miha36

TheoBlanca Fair point, but it splits into two different cases.

Normal links (Gmail, messages, etc.): these are just http/https intents. Nothing
actually requires Chrome specifically — Android routes them to whatever browser is
set as default. Install Firefox and set it as the default browser
(Settings > Apps > Default apps > Browser app, or accept the prompt Firefox shows on
first launch) and links from Gmail open normally. Firefox also supports Custom Tabs,
so apps that open pages “in-app” still work.

In-app web screens (embedded WebView): these are the ones that genuinely break —
in-app login flows, OAuth screens, help pages rendered inside an app. But it’s worth
being clear about why: those run on Android System WebView, not on Chrome.
They are already broken on this build regardless of whether Chrome is enabled or
disabled. Disabling Chrome doesn’t cost you anything there — it just stops Chrome
from triggering the cascade that takes down the rest of the system.

So it’s a partial workaround, not a fix: it buys back a usable phone (calls, apps,
Settings) and normal browsing, but anything WebView-backed stays broken until
Nothing ships a fix.

anirudh_hoon

grepGander bro but my is nothing os 4.1

TheoBlanca

anirudh_hoon is it happening in 4.1 version also?!

anirudh_hoon

TheoBlanca yes bro

« Previous Page Next Page »