Chrome OS has displayed low-battery notifications for years. See https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/docs/battery_notifications.md.

If you're not seeing them for some reason, please file a feedback report the next time you see the issue and comment on this bug with the account you used.

Yes, I approved of this. The current notification could be revamped. 👍

I submitted a feedback report about this last night under the username alyosha.be@gmail.com.

For what it's worth, this time I did see a low battery notification - less than a second before the computer shut down. I think the notification was for 1% battery, but I'm not sure. It seems like at least in some cases these notifications don't come early enough to be of use.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Todd, mind checking out powerd.PREVIOUS (I assume) from the feedback report to see what happened here? (I don't have access at the moment.) The last few battery readings should be informative. Thanks!

No idea what hardware this is referring to, but issue 890067 may be related.

Device is a samus (pixelbook 2015).  Last few readings are interesting indeed,

[0115/210458:INFO:daemon.cc(750)] On battery at 10% (displayed as 6%), 0.773/7.801Ah at 0.735A, 44m45s until empty (26m41s until shutdown)
[0115/210528:INFO:daemon.cc(750)] On battery at 10% (displayed as 6%), 0.762/7.801Ah at 1.186A, 44m38s until empty (26m21s until shutdown)
[0115/210534:INFO:daemon.cc(750)] On battery at 0%, 0.001/6.951Ah at 1.592A, 3s until empty (0s until shutdown)

Goes from 10% to nearly zero (1mAh) in 6 seconds.

Also appears battery is showing signs of fatigue via power_supply_info

  full charge (Ah):        6.951
  full charge design (Ah): 9.515

Based on those numbers battery can only hold 73% of its original capacity.

Looks WAI given the batteries quick loss of capacity.  Going to close.

Optimally I'd recommend getting a replacement device if possible.

Thanks for checking on the readings.

I'm not likely to get a replacement device since this laptop works perfectly otherwise.

I think a lot of people similarly don't want to (or can't, for financial reasons) buy a new device just because the battery isn't what it used to be.

Perhaps it would be better to allow the user to adjust the low battery notification threshold?

I'd like to think this case is fairly isolated as I've not seen too many similar reports and hopefully thats because the battery's BMU should be factoring in battery aging as part of its capacity remaining calculations. 

Adding user config to set low battery notification comes with its own perils & implementation cost as well.  If you feel strongly I'd recommend filing a new bug to explore that possibility.

There's no way that UX is going to support adding a setting for the threshold for the low-battery notification, so I'd recommend skipping filing a bug. :-P

Todd, while it won't help here, is it possible that this sort of thing may be handled better in other ECs? Even if the battery's capacity has gone down, it seems pretty weird to see the reported charge drop like that. Is that something that you've seen before? I haven't heard of it and am wondering if it's a samus-specific thing.

I haven't seen it before on any particular CrOS device outside a rare one-off like this.  

Might be some UMA data slicing we can do to look for increase in shut-down reason == low battery across battery health == [70, 80, 90, 100] to see if there a higher incidence.