Swordfish II
Advanced Member
- Joined
- May 20, 2015
- Messages
- 1,175
Might be to late to suggest, but it would be nice to be able to shut down at the log in screen
That requires patching slim (the login manages), not something I'd want to do.Might be to late to suggest, but it would be nice to be able to shut down at the log in screen
Same here for configbutton. You could try asking @slaeshjag (the author), but he hasn't touched it for some years now.If we are doing requests, well i have one being able to switch mode between "lid close screen off < - > lid close low power mode" with a mini-icon setting in the task bar instead of having to go in the menus. (because this is something i do very often).
Same here for configbutton. You could try asking @slaeshjag (the author), but he hasn't touched it for some years now.
That requires patching slim (the login manages), not something I'd want to do.
Cool. Not as quick as clicking a button, but possibly good enough (I don't really shut my Pandora off unless I won't be able to charge it for a while). I will test it out later. Thanks a lot for sharing this.OK no big deal
Edit: wow, was looking up slim and found this. I tested and using halt and the password works. I had no idea.
Cool. Not as quick as clicking a button, but possibly good enough (I don't really shut my Pandora off unless I won't be able to charge it for a while). I will test it out later. Thanks a lot for sharing this.
No need for that. As best I can tell, all that the the hypothetical configbutton plugin would actually need to do is write either "brightness", "lowpower" or "shutdown" (without quotes) to ~/.lidconfigChanging op_lid.sh shouldn't be that hard
No, it's not controllable.Is there any Way like a Kernel Hack or near to get more Power on the USB OTG Port for some more Devices?
That may be possible, but it may overload and burn the hardware, so I don't really want to add such a feature.Or maybe to disable that Power rekognize Error?
There is no software control over how much the USB port can output, it's connected to a switch, then power regulator and then directly to the battery. You should check dmesg, it's probably some different issue.Maybe something has changed because I had problems with my 802.11n wifi dongle too while it worked perfectly before. This was on the regular USB port though, not the OTG one.
Maybe, need to write OE recipe for it first...Might be too late for suggestions, but would it be worth putting f3write/f3read into the default OS? They seem like something everyone should have on an SD-card-oriented system, and PNDs are not so good for tiny command-line programs. (They compiled easily, to <100k between them.)
http://oss.digirati.com.br/f3/