Handle driver-related errors and crashes more gracefully
Currently, charging-sdl brings to a high-power "bootloop" when partially incompatible devices, such as Nexus 5 (hammerhead), get plugged in. The issue behind this seems to be that the lack of a proper battery driver leads charging-sdl to a crash with no error log given, or any other kind of display, and it boots straight to the kernel, which in this (and many other) cases may freeze at boot in a high-power state, thus leading to enormous power consumption almost preventing devices with broken kernels or drivers from charging at all.
Possibly relevant quote from @MartijnBraam on the issue:
I think it's partially because the battery level thing in SDL2 is shit [...] and SDL doesn't support all batteries the kernel supports
Relevant quote from @dolphinchips:
nice quote heh