Disable Default 60hz Framerate Not Working As Intended NOS 4.0

Womey

Since updating to Nothing OS 4.0, the “Disable default frame rate (60 Hz)” Developer Option no longer behaves as it did previously on NOS 3.2

I am seeing this consistently across multiple devices:

CMF Phone 1
CMF Phone 2 Pro
Phone 3a

Prior to NOS 4.0, this toggle reliably allowed many games to exceed 60 Hz. After updating, behavior is inconsistent. Some apps briefly report 120 Hz, others remain locked to 60 Hz.

Observed behavior (reproducible):

Display runs at 120 Hz when idle
Any touch input immediately drops refresh rate to 60 Hz
Refresh rate returns to 120 Hz once input stops

This occurs in:

Dead Cells
Old School RuneScape (OSRS)

The issue persists even with:

Force peak refresh rate enabled
Battery saver disabled
Min/peak refresh rate forced via ADB

Device: CMF Phone 2 Pro

OS: Nothing OS 4.0

Build: Galaga-B4.0-251218-2326

Is this a known NOS 4.0 issue, or has Nothing changed how high-refresh behavior is handled for games? The interaction-based drop to 60hz feels like a regression compared to pre-4.0 behavior. Why can you not disable this hard 60hz cap?

Would appreciate confirmation if others are seeing the same.

S.H.Jyoti

Womey Is it also on the CMF 2 pro?

Sriansh

Womey yeah 4.0 stable caused this

Womey

S.H.Jyoti

Yes I have it running NOS 4.0 and there is no fluidity to frame rates within applications. Developer toggle for removing 60hz cap does not work as intended.

Womey

Sriansh

Yeah.. I downgraded a device to NOS 3.2 and 120hz worked instantly. No more touch input 120hz degradation.

And yeah.. still not fixed In latest 4.0 build for 3a, unfortunately. Hopeful, as they have acknowledged it and the NOS Launcher updated as well, so feel they are prepping for 4.1 on 3a devices. Anyways, here’s to a little shine of hope mate. Cheers 😎

Sriansh

Womey by “acknowledged it” are you referring to the responses they gave via email or did they address it recently?

Womey

Sriansh

2 different support responses from technical teams reproducing the issue and acknowledging this is a regression, to be addressed as such, to come in a later patch. So I am hopeful for this to come in NOS 4.1 update. Curious for those who have a 4a now if this is occurring on those devices?

Edit: added the emails from support I received

johnlattanzio98

Womey I have reported this issue three times on three different os versions, and each time they tell me to wait for a patch. Well, I’m done. New update came out today, still not fixed. This is getting old, they said it would be fixed like almost a year ago at this point. It isn’t fixed in 4.1, and I guarantee it won’t be fixed in 4.2, like what happened with the last three (four now) updates. Sorry to burst your bubble, but there’s no chance that this ever gets fixed now.

Womey

johnlattanzio98

Hey, please DM me. I have a workaround you can try.

GodKarma

Womey I was reading your comment, and I’m having the same issue on the Nothing Phone 4a Pro. It can’t be forced; in games, it runs at 60 FPS. It shows 120 Hz, but as soon as you touch the screen, it automatically drops to 60 Hz, and when it’s idle, it goes back to 120 Hz. I’m having this exact issue.

I also read your comment where you said there was something we could try that might work. What is that “something”?

AgentY

Womey Would you mind sharing the workaround? I’ve had this issue on my np 2a since beta of 4.0.

Womey

AgentY @GodKarma

Hey there! If you are familiar with ADB, pair your device, open a terminal, and run:

“adb shell cmd game set –fps 120 [app package name]”

An example using Old School Runescape that I run, “cmd game set –fps 120 com.jagex.oldscape.android”

Please note there are TWO dashes, Nothing Community shows up as one dash used, while I have typed two side-by-side in the comment boxes here. Should be “- -” no space before fps not a single dash.

The last part is the app’s package name. Long press the app, select App info, and scroll to the bottom to find it.

This unlocked my phone above 60 FPS in most apps where the game and device allow it. Some games still have their own internal FPS cap (ex: Wuthering Waves), and you may need to run the command again after restarting your phone. Higher FPS may also use more battery and create more heat.

Happy to help break it down further if needed!

GodKarma

Womey

Thank you so much! It worked! I can finally get above 60 FPS on my Nothing Phone 4a Pro. Really appreciate you sharing this workaround! 🙏🔥

AgentY

Womey It worked, thanks🙏

Womey

GodKarma

You are so welcome!! If you want to get more in the weeds, as this will reset with every phone restart. You can get on the Play store Macrodroid and set the code to run as a script on device reboot and many many other ways so it will always run at 120hz, the games of your choosing.

Otherwise, one last thing I noticed I wanted to add originally but forgot till this comment. If you don’t have “Unlock Games Above 60hz” toggled in Developer settings, the screen (without input for ~20 seconds) reverts back to 60hz. Toggling this on and running the code line in ADB keeps it at 120hz always even without active input (touch screen presses). Cheers! 😎

AgentY

Womey May I ask you how did you manage to make the script run at startup using macrodroid because all the methods I find require root so maybe I am missing something.

Womey

AgentY

You are so welcome! Glad it worked nicely for you 😎

ShantaMajumder_v7ZKDfHShA

Same here

Womey

AgentY

Hey mate! Apologies for the delayed response.

I have not rooted my device, nor am I recommending rooting here. I paired Shizuku through Wireless Debugging and granted MacroDroid access to it, which allows the command to run without root.

In MacroDroid, I set:

Triggers:

• Device Boot

• MacroDroid Initialised

Actions:

• Wait 25 seconds

• Shell Script

For your Nothing Phone, paste the following in Shell Script when you select the option:

cmd game set –fps 120 [insert package name example:] com.jagex.oldscape.android

When setting up the Shell Script, select Shizuku. I tried the standard Non-Rooted option for my gaming apps and could never get it working.

The main caveat is that Shizuku must already be running. On an unrooted device, you generally need to start Shizuku again after every phone restart, so the boot automation is not always reliable for me. If it fails, start Shizuku, then long press the macro from MacroDroid’s main screen and select “Test actions.”

You need Wi-Fi when starting Shizuku through Wireless Debugging, but the macro itself does not require you to remain on your home network.

Also, this cannot override a game’s own internal limit. OSRS still refuses to reach 144 FPS for me, even when set to Unlimited. Jagex! 👿 Also the delay of 25 seconds allows me to see the fps change occur to ensure it worked so you can jump back to your gaming app and see it run live if you want to!

I’ve attached screenshots showing my setup. Hopefully this helps? If you find a more reliable startup method, definitely share it. Cheers! 😎