Ubuntu Touch Device turns off at 0% instead of cleanly shutting down upon hitting a critical battery level

[ShadowEO]

My Nexus 7 seems to wait until the machine dies completely rather than shutting down upon hitting a critical shutdown level. Not sure if this was intended or not, but it seems to be possibly causing file system corruption on the userdata partition.

The behavior that I have noticed is happening only after the device's battery dies a couple times, I've noticed this on two installations and reflashing fixes it temporarily for me:

I'll open Libertine and ask it to update my container, or install a package, etc. and soon enough, it comes back with read-only file system on my home directory. Upon looking at the mount table, I see that /dev/mmcblk0p30 is indeed being remounted as read only. So I rebooted into Recovery Mode and ran e2fsck on the partition. It passed, I ran it a second time to ensure, it passed again. Unfortunately, it appears that the file system is not clearing the dirty bit either, as looking in tune2fs continues to say the filesystem has it's dirty bit set.

As I said, I've noticed this behavior happens only after I let the tablet die completely, so I figured I'd report this. I can give logs or any diagnostics requested of me if needed.

[Anupam (anupam207)]

Related: bug #1317860