Mr Steel 🦾 Again, I think the use case here is different, and that’s really the main point.

You’ve been using Android phones for 15 years, but almost every Android phone you’ve used has given you a low-battery warning pop-up. That’s not a coincidence. It’s a basic system-level warning that exists because users have different usage patterns and because the phone shouldn’t simply reach 0% and die without giving you reasonable notice first.

If you’re someone who rarely uses your phone and does most of your gaming and entertainment on other devices, then obviously this probably isn’t something you would be concerned about. But that doesn’t mean everyone uses their phone the same way.

I still have my OnePlus 6 running LineageOS + NetHunter. I rarely use it now; most of the time it acts as a Wi-Fi hotspot. Even then, I appreciate the low-battery warning it gives me. AOSP itself has these warnings. Even if you’re only keeping a phone around as a hotspot, you’d still want the phone to warn you that the battery is getting low so you can plug it in before it dies and your hotspot disappears.

Letting a phone completely die because of low battery is frustrating, and repeatedly doing that isn’t something you want for the battery either. Maybe you charge your phone at night, use it throughout the day, have relatively low SOT, and never find yourself in this situation. That’s fine. But you can’t expect everyone’s usage pattern to be the same as yours.

And regarding the part you quoted… I think you misunderstood what I meant by “it gives you a heads-up to cool off, take a break.”

The point isn’t that the low-battery warning should force me to stop using the phone. If I get the low-battery warning, I’ll plug the charger in, let it charge for a while, and then resume whatever I was doing once it has enough charge. It gives me some headspace and enough time to wrap up whatever I’m doing instead of suddenly letting the phone die and potentially losing my progress.

Digital Wellbeing doesn’t accomplish that.

If I set a timer on Digital Wellbeing, it simply locks me out of the app once I reach the limit. It doesn’t tell me that my battery is low and that I should charge the phone now before I lose whatever I’m doing. Those are two completely different use cases.

The low-battery warning is about giving the user advance notice about the device’s battery state. Digital Wellbeing is about limiting screen time/app usage. One isn’t a substitute for the other.

And that’s why I find it strange that we’re still discussing whether something this basic is worth implementing. Low-battery warning pop-ups have existed for decades. AOSP has them. Other Android ROMs have them. This isn’t some new experimental feature that needs to be designed from scratch.

If we’re saying that adding something this basic is too difficult for the backup/development team, then after five Nothing OS iterations, something is definitely off. I’d even call the developers lazy at this point, because from the outside it genuinely looks like they’re prioritizing gimmicky features over basic, useful ones.

If the argument is that there’s little impact because not many people use the feature, then I’d make the same argument about Essential Space. Not everyone uses Essential Space either. Some people don’t find it useful, and some probably don’t want to give it access to their entire gallery. Take pretty much any YouTube creator’s review of Essential Space and you’ll see that its actual usage/impact isn’t necessarily huge either.

Yet Nothing is still allocating time and resources toward developing it.

So if they can allocate development resources to something like Essential Space, I’m pretty sure adding a standard low-battery warning pop-up can be done too. It’s a matter of priorities.

I’m just saying that “I personally have never needed it” isn’t really a good argument against the use case. Your usage is different from mine, and mine is different from someone else’s.

Anyways, there’s no point in arguing about this in a community thread. The official support itself isn’t THAT useful, especially when the response is AI-generated text instead of someone actually taking the time to read the issue and respond to it properly. They don’t even seem to have the time to properly read and respond to the feedback themselves, so would they even read and pay attention to community reactions? I don’t know. I don’t think so.

I only hope that people in the community who read this understand the use case and report the same thing through the official feedback channels. If enough people report the same basic issues, maybe those features will eventually get implemented.

Arguing with you or anyone else isn’t going to accomplish that. I’m not trying to win an argument here. I’m just trying to explain my side of things, that’s all. ✌🏼