What is the Android strategy for low battery?

Question

I would like to know which modules to “disconnect” and “disconnect”, and in which order, when the device’s battery is low.

I am particularly interested, for example: let's say my application works, and on the field. Now I run the intention to launch another application. Can the battery run out so that another application does not start?

I would also like to know if I can somehow control what will scream first, and what should remain active until the device is rich to almost 0%.

my application is not market-based, it is intended for certain devices that are controlled from the MDM system, so if it’s possible, it’s legal to manage settings

TIA

Answer 1

AFAIK, Android shares do not implement a "low battery arrester." Some modifications of the vendor (HTC and, possibly, others), but there is no clear standard. They usually covered the blue tooth, GPS, WiFi and, finally, data and, possibly, reduce the screen. If you focus on certain devices, you should work with the one who created the firmware for those who understand what exactly he is doing (if at all).