Probably wasn't clear enough in my question! I have Q10 type TV Box running Android 4.4.2 - It's also running Kodi 16.0 and has the HiMediaWapper installed and functional. I realize that Android is an OS first developed for the Phone, but it branched out [pretty quickly] to tablets and other devices [like TV Boxes].
So I purchased the Q10 type TV Box to upgrade from an aging HTPC running Windows and XBMC 11.2 - My existing library is already on two Direct Attached Raid 5 NTFS formated systems of 9 TBytes each. These Raid Boxes are stand alone, not NAS, and are auto-switching between 3 formats: USB 2.0, [an old firewire implementation I've never tried] and [Multi-port] eSATA. My problem is that as a portable device OS Android has a very quick Default timeout on USB connections [which includes the spin-down/sleep command if the USB device happens to be "spinning rust".] Now this particular device, a mutimedia player, has 3 USB connectors 1 @ v3.0 & 2 @ v2.0 plus an internal SATA connection capability so my assuming that adjusting USB parameters seems plausable. Also thinking that someone out there has run into my particular problem doesn't seem too removed from the realm of possibility.
When one is using a settings menu within most OS types usually it's an interface for writing and adjusting the configuration files which are then read during a program initialization &/or system boot. By default Android, a normally portable device OS, is going to have rather quick timeouts on potentially power hungry devices, just sitting around sucking on the battery. However the Q10 as a mains attached device, has less need for these default Android power saving settings.
And in my particular case, with my pre-existing Direct Attached RAID systems, having Android spin-down the drives while my wife is slowly choosing what to watch, only to sequentially restart the 4 drives in each box at nearly 10 second intervals in order to either start the chosen flick [or if my luck really running south, merely renewing the directory contents cache for more searching.]
So, although I realize that both a quick spin-down of attached devices and a sequential startup of reawakened drives makes total sense for a battery powered portable device OS - in this case it is not ideal - & I'm looking for anyone who may have an idea on a method for modifying the default parameters within an Android device. I realize it's likely a hand edit &/or the creation of a config file - but personally, I have simply no idea of the where,what,who or how!
Thanks!