It is supposed to be the most exciting update of the year for Nothing fans. But for many owners of the Nothing Phone (3a), the arrival of Nothing OS 4.0 has introduced a particularly irritating bug that makes using the phone a headache.
Users are reporting a persistent system error that flashes on the screen so quickly it is almost impossible to read. If you have updated your Phone (3a) recently, you might have noticed a blink-and-you’ll-miss-it pop-up disrupting your usage.
According to frustrated users, a dialogue box reading “Log Tool keeps stopping” appears and vanishes in less than a second. It happens repeatedly, sometimes every few minutes, regardless of what app is currently open.
We have seen software updates break things before. Android updates are complex beasts, and bugs are part of the territory. However, this one is especially intrusive because of its frequency.
On the Nothing Community forums, user ASHILRAJ documented the issue in detail. They noted that the message flashes so fast that they had to screen record their device just to read the text.
When users try to report the crash to Nothing, the feedback tool fails to load or kicks them back to the previous menu.
Reddit has become a hotspot for these complaints. In a thread on the r/NOTHING subreddit, user bestin119 shared a screenshot of the error, asking if there was any way to fix it. Another user, Mr_Zipperface, chimed in to confirm that their feedback tool was also “bugged,” leaving them unable to send logs to the developers.
Community member AndrewHumphreys reported that for the first time, the pop-up actually stayed on their screen long enough to tap “Close app,” but even that didn’t resolve the looping crash.
While the majority of reports are coming from the OS 4.0 rollout, it might not be exclusive to the beta. User TheUnluckyThirteen noted on the forums that they are seeing the same error on Nothing OS 3.2.
If you are comfortable with more advanced tinkering, there is a potential workaround. Community member Leoth suggested disabling the log kit package entirely using ADB commands.
By connecting your phone to a PC and running adb shell pm disable-user --user 0 com.nothing.logkit, you can effectively kill the process causing the crash.
If you go this route, Leoth advises enabling it back again once an official fix lands.
You can read through the growing list of complaints yourself. We found similar reports popping up on Reddit threads here and here, as well as on the official community forums here and here. Meanwhile, reports are also surfacing on X.
I’m hoping Nothing acknowledges this quickly. When your bug reporting tool is the thing that is broken, you know you have a priority one situation on your hands. Until a patch rolls out, Phone (3a) users might just have to put up with the flickering distraction or break out the ADB tools.
Featured image credit: ASHILRAJ / Nothing Community
TechIssuesToday primarily focuses on publishing 'breaking' or 'exclusive' tech news. This means, we are usually the first news website on the whole Internet to highlight the topics we cover daily. So far, our stories have been picked up by many mainstream technology publications like The Verge, Macrumors, Forbes, etc. To know more, head here.
Dwayne Cubbins
1391 Posts
For nearly a decade, I've been deciphering the complexities of the tech world, with a particular passion for helping users navigate the ever-changing tech landscape. From crafting in-depth guides that unlock your phone's hidden potential to uncovering and explaining the latest bugs and glitches, I make sure you get the most out of your devices. And yes, you might occasionally find me ranting about some truly frustrating tech mishaps.
Follow Us
