I'm not opting on *excluding* hostmode charging from blue_led scripts. I'm suggesting, that forcing every user to use it (or modify scripts) is bad idea - as opposed to allowing using it by executing two simple commands from xterm (boostoff && charge.sh), or even creating one script, that, upon execution, invoke those 2 commands - for lazy ones . Calling charging from xterm by 1/2 short commands seems reasonable for script, that works from xterm anyway. Forcing user to *always* do charge.sh, or modify scripts itself to get rid of it, isn't fun. Nor it resemble the "ideological" Open/Linux way of doing things. Of course, if it gets implemented as "force to use it", I can live with that, and modify script / fork it if others would be interested in using such version (like it was for a long time with backupmenu, and backupmenu-multiboot - while, t was very easy to implement one version working for all). After all, final decision belongs to blue_led. Still, I don't think it's good idea, to *force* such commands on user. Not to mention complications on script-side (determining, when it should do boostoff/charge, or not - trying that without external power source would break hostmode), but that's different topic. /Estel