No worries Ytai - thanks for the response -

Because it's an always on application (car dashboard) I need more than 
500mA through the USB port as using full brightness/gps/data logging/GPU. 
With a fastcharge capable ROM I can enable USB fast charge (which gets 
about 600mA on the Nexus 5), and then I change a value on the phones 
charger chip via kernel value to change the fast charge current up to 
900mA. This second value is reset every time a new USB device is detected - 
so I write the value every time the IOIO connects. This sometimes causes a 
USB data glitch which knocks the IOIO out, but the instability also seems 
present when using "normal" USB fast charge - just less prevalent. If i 
completely disable the USB fast charge, I cannot replicate the failure 
easily (but have still had occasional failures when testing for a day or 
so).  It seems to just be a glitch in android's USB comms that knocks out 
the IOIO, and perhaps I'm causing a glitch more often with the high current 
mode.

I use an OTG Y cable to supply 5V direct to phone - which avoids problems 
I've had when using the IOIO regulator (think it's the current limiting 
circuit which often sags below 5V, the charge rate is incredibly sensitive 
to voltage drop) The problem is present with the onboard reg too though

James



On Tuesday, January 12, 2016 at 11:30:28 PM UTC, Ytai wrote:
>
> Sorry for taking long to respond and thanks for reporting the issue and 
> looking into possible causes.
> I believe I've seen this issue in the past on an N7, but wasn't able to 
> reproduce. I'm interested in having this case diagnosed and fixed.
> What did you mean exactly by "linked the instability to using USB fast 
> charge"? And why/how did you bypass the IOIO on-board regulator?
>
>
> On Wed, Jan 6, 2016 at 8:30 AM, James Warner <[email protected] 
> <javascript:>> wrote:
>
>> Further troubleshooting has linked the instability to using USB fast 
>> charge - ( before anyone asks the voltage source is stable (and not 
>> supplied via the IOIO regulator)
>> Maybe not the IOIO at fault, but it would be good to enable the IOIO to 
>> auto recover when the connection does break - as once the IOIO goes into 
>> the failed state, it doesn't matter what phone you connect - it needs a 
>> power cycle
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "ioio-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected] 
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/ioio-users.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"ioio-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/ioio-users.
For more options, visit https://groups.google.com/d/optout.

Reply via email to