On Monday, September 18, 2017 at 6:07:13 PM UTC-7, kinsell wrote:
On 09/18/2017 02:54 PM, wrote:
Sorry to hear the IOIO does not prevent USB glitches. And I thought it was the OTG Y-cable method that was to blame. But does the IOIO actually need the main device to run in OTG mode (i.e., being the USB host)?

I believe the Nook does need to run as Host, but it does receive power
over the bus for charging. So it's a true OTG device.

I set up a Kobo Mini for a friend with a Y cable, AFAIK it's been solid.
I think the flakiness is either in the Nook USB chip or the driver for
it. On rare occasions, the Nook has booted in a bad state such that
nothing short of rebooting was able to clear the problem.

-Dave





If you like an older version of Tophat better, you can still use it. I keep the old .apk files just in case. Of course you do then give up some improvements done in the more recent versions.


On Friday, September 15, 2017 at 6:41:12 PM UTC-4, kinsell wrote:
On 09/15/2017 02:40 PM, moshe wrote:
A third way is via an "IOIO box" but that seems overkill to me.

Compared to buying a $1000 phone to try to get enough brightness, seems
like a terribly minimalist solution to me. I'm using IOIO-OTG and have
a secondary input wired to give a big PF display. Worked great for a
while, then TopHat dropped the capability out of current releases for
some reason. Maybe XCSoar still has it, but never liked their UI.

Reliability of the system is marginal, usually takes a couple
unplug/replug cycles of the usb to keep things running on a long flight.

-Dave

Ditto with Nook- did not like it.
Top Hat runs solid with the Kobo Mini and I even like it better on the Kobo Glo