11-09-2016, 08:33 PM
(11-09-2016, 06:07 PM)pfeerick Wrote:i hardly ever use a battery anymore for the simple reason that the pine64 takes too long to recharge it and over time i grew tired of unplugging it in order to use a external charger. the issue i'm talking about is with a powered hub attached at all times. my main o/s is linux debian and i usually try 5.1 android for the camera and 7 android just to check how it is going. anyway, my board remains energized at all times after terminating any of the o/s mentioned. generally termination is via power down option with android and either the UI shutdown or via terminal command line shutdown now with linux. it has been discussed a couple times i know of on the forums about the powered hub feeding into the board and is generally claimed to be harmless but as i mentioned i have wondered if having it energized creates the possibility of holdover settings. the reason i wonder is because a lot of electronics manufacturers suggest unplugging electronics in order to "reset" them, allowing components to discharge any lingering currents in order to completely "zero" onboard settings.(11-09-2016, 02:01 PM)dkryder Wrote: i've wondered about that myself as if i used a powered hub for instance , the board is in a powered state of some sort as evidenced by the power light remaining on even after the o/s terminates. because of this, i've wondered if some settings remain energized for lack of better definition. i have no idea if it happens. i've just wondered about it.
Can I just get a confirmation of if this is with or without a battery connected, what OS, and what sort shutdown command used? Also, I'm presuming the hub is connected to something that then plugs into the pine64s USB port(s)?
When the pine64 is plugged into a external supply via just the microUSB or euler power connections, when I shut down linux using sudo shutdown -h or sudo poweroff the main power light goes off and stays off. If I have a battery connected as well as main power, it shuts down and immediately powers itself back up (which is annoying as it isn't what I told it to do!) - so since I have a battery connected to it most of the time, I have to pull the battery before shutting it down. If the battery only is connected, it shuts down without any issue. I didn't notice any lingering power on states when I was trying the Android 5.1.1 builds, but I didn't play with them for long. I haven't used a (externally powered) USB hub to power the pine64, but I'm guessing that some power is bleeding back via the USB host ports - whether this is keeping parts of the pine64 circuitry powered up and mucking things up I don't know.