Hi Ytai, ioioUser,
I tried with another beefier power supply 9V…but unfortunately doesn’t change
anything.
It seems there another problem of application of IOIOActivity.
Cause when I use your reference IOIOapp it’s working perfectly…but not with my
app. : (
Tell me if it is right cause I’m a bit desperate to get something working one
day ...
First, I have one superclass called mapViewer extending IOIOActivity
this class is not referenced in the manifest file but in this class I added
@Override
protected IOIOLooper createIOIOLooper() {
return super.createIOIOLooper();
}
This class is used to get a map view.
Second, I have another « working » class called mapViewerActivity extending
the super mapViewer class.
this class is referenced in the manifest file with , single task, usb launcher
etc, like just below
<activity
android:name=".MapViewerActivity"
android:configChanges="keyboardHidden|orientation|screenSize|layoutDirection"
android:label="@string/app_name"
android:launchMode="singleTask"
android:screenOrientation="portrait"
android:theme="@android:style/Theme.Holo.Light.DarkActionBar" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
<intent-filter>
<action
android:name="android.hardware.usb.action.USB_ACCESSORY_ATTACHED" />
</intent-filter>
<intent-filter>
<action
android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" />
</intent-filter>
<meta-data
android:name="android.hardware.usb.action.USB_ACCESSORY_ATTACHED"
android:resource="@xml/accessory_filter" />
<meta-data
android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"
android:resource="@xml/device_filter" />
</activity>
All the loop class and implementations are in the mapViewer class.
So the only difference with IOIOapp reference, is that I’m not extending
directly from IOIOActivity
In my case, I’m extending a supertype that extends IOIOActivity.
Does it make a problem ?
In your opinion, what could be changed to get it functional ?
Avoid the intermediary superclass ?
Thanks for help.
Lo.
Le 22 juil. 2015 à 01:27, Laurent Turnauer <[email protected]> a écrit
:
> Ok I’ll try it.
> Thanks for advice.
>
> Lo ; )
>
> Le 22 juil. 2015 à 01:25, Ytai Ben-Tsvi <[email protected]> a écrit :
>
>> Are you able to test with a beefier supply or at least higher voltage? I'm
>> concerned that as soon as the Android attempts to charge itself (which might
>> be a few seconds after having been plugged in) it draws a current spike that
>> your supply can't handle well, resulting in a momentary drop in voltage and
>> loss of the USB connection.
>>
>> On Tue, Jul 21, 2015 at 4:20 PM, Laurent Turnauer
>> <[email protected]> wrote:
>> 800mA on 6V.
>>
>> Le 22 juil. 2015 à 01:19, Ytai Ben-Tsvi <[email protected]> a écrit :
>>
>>> I don't know what's in those jar files. Currently, the IOIO libraries are
>>> distributed as source files + eclipse projects. I'm soon moving to
>>> distributing archives and a Gradle-based build system, but that's not
>>> happening immediately.
>>> What's the current rating on your power supply?
>>>
>>> On Tue, Jul 21, 2015 at 4:15 PM, Laurent Turnauer
>>> <[email protected]> wrote:
>>> Hi,
>>>
>>> Yes current CHG at max position.
>>> and I’m using 6V regulated for prototyping.
>>>
>>> How can I use the librairies from master branch ?
>>> I don’t know how to do it cause I’m used jar files.
>>>
>>> Lo.
>>>
>>> Le 22 juil. 2015 à 01:13, Ytai Ben-Tsvi <[email protected]> a écrit :
>>>
>>>> AND is the "CHG" pot on the IOIO all the way clockwise?
>>>>
>>>> On Tue, Jul 21, 2015 at 4:12 PM, Ytai Ben-Tsvi <[email protected]> wrote:
>>>> I'm curious to see what you find with the new library. Also, what power
>>>> supply are you using? Could we be seeing a dropout resulting from a power
>>>> dip?
>>>>
>>>> On Tue, Jul 21, 2015 at 10:28 AM, Laurent Turnauer
>>>> <[email protected]> wrote:
>>>> Re Ytai,
>>>>
>>>> Thanks for answer…and sorry for mine a bit late...
>>>>
>>>> 1- So, I tried with your Hello IOIO precompiled freshly installed apk app.
>>>> I checked in app manager and the Hello IOIO is not started. (Force stop
>>>> button is unavailable)
>>>>
>>>> 2- I restarted the phone.
>>>> I rechecked in app manager and the Hello IOIO is not started. (Force stop
>>>> button is unavailable)
>>>>
>>>> 3 - Ok, then, plugged usb cable and Hello IOIO launched as it has to do
>>>> mentioning default launching behavior
>>>> IOIO is connected...Great it works, I’m playing with button, the state led
>>>> responds perfectly…
>>>>
>>>> 4 - Then back pressed button, going to desktop.
>>>> Check in app manager and the Hello IOIO is started. (Force stop button is
>>>> available but I don’t press it)
>>>>
>>>> 5 - Then I relaunched the same Hello IOIO app… Toast tells me "IOIO is
>>>> connected" …wait 3 seconds…and then "IOIO disconnected"
>>>> I mention also I haven’t removed or unplugged the usb cable. The cable is
>>>> connected only once at point 3.
>>>>
>>>> 6 - Then back pressed button once, the app is either relaunched
>>>> automatically or go back to desktop,
>>>> If the app is relaunched automatically, it’s redoing the cycle « IOIO
>>>> connected » then « IOIO disconnected » maybe 2 or 3 times, then the
>>>> Hello IOIO app is working.
>>>> Or sometimes, Android tells me « Hello IOIO has stopped ».
>>>> If I relaunched the app manually it also works.
>>>>
>>>>
>>>> So, it seems, there is another behavior but quite not so far of mine.
>>>>
>>>> With my app, I plugged usb, ioio doesn’t work, than restart the app…and it
>>>> works.
>>>> Or
>>>> With your Hello IOIO app, I plugged usb, ioio works firstly fine, and then
>>>> if relaunched, it has some issues of connection…but finally after some
>>>> attempts and relaunch it works.
>>>>
>>>>
>>>> Like you said, I will try your fixes of OpenAccessory.
>>>>
>>>> But normally I was used your jar files created from another ioio users,
>>>>
>>>> how can I do it in other way with the master branch ?
>>>>
>>>> Thanks for help.
>>>> Lo.
>>>>
>>>>
>>>> Le 10 juil. 2015 à 23:47, Ytai Ben-Tsvi <[email protected]> a écrit :
>>>>
>>>>> Two things to look at:
>>>>> 1. Do you see this behavior occurring with the precompiled example
>>>>> applications? If not, what is different about you app that causes the
>>>>> problem?
>>>>> 2. There were a bunch of fixes to OpenAccessory mode recently that are
>>>>> not yet included in the release package, but have been published to the
>>>>> master branch on GitHub. You can give them a try.
>>>>>
>>>>> On Jul 10, 2015 1:04 PM, "Lo" <[email protected]> wrote:
>>>>> Hi Ytai, ioio users,
>>>>>
>>>>> I recently bought at sparkfun my IOIO-Otg board to make some stuffs with
>>>>> external sensors.
>>>>>
>>>>> I spent several days to understand a little the android's
>>>>> world...waw...It wasn't so easy.
>>>>>
>>>>> Whatever, now I used the template simple app in my root class activity
>>>>> extended by IOIOActivity.
>>>>>
>>>>> ....and IOIO Board is always connecting when I plug the usb... Great ...
>>>>>
>>>>> BUT... I'm facing to an always disconnection issue when usb is plugged...
>>>>> After the usb is plugged, I absolutely need to restart my app.
>>>>> And then it's ok.
>>>>>
>>>>> Samsung Galaxy III GT19300
>>>>> Android Version 4.3
>>>>>
>>>>> IOIOLIB: IOIO0504
>>>>> Appfirm : IOIO0500
>>>>> Bootloader: IOIO0400
>>>>> Hardware: SPRK0020
>>>>>
>>>>> To explain my small issue
>>>>> ----------------------------------
>>>>>
>>>>> 1 - App is compiled and installed from Android Studio.
>>>>> 2 - Then my phone is manually restarted. (or not whatever)
>>>>> 3 - RePowering the IOIO board with 6V regulated. (or not whatever)
>>>>> 4 - Plug usb between the two devices
>>>>> 5 - My app is auto activating by default by the open accessory and launch
>>>>> my main activity containing a small led blinking loop.
>>>>> 6 - Then it works... but it stays connected only 3 seconds...
>>>>> 7 - So I press the phone's BackButton to return to android desktop (The
>>>>> board is still plugged with phone and not removed)
>>>>> 8 - I restart my app...and then it stays correctly connected without auto
>>>>> disconnecting.
>>>>>
>>>>> So I needed to restart the app twice to work fine...and then only the
>>>>> loop is no more broken...
>>>>>
>>>>> If someone has facing the same behavior ?
>>>>> Is there a trick I miss somewhere during initialization or in manifest
>>>>> file ?
>>>>>
>>>>> Maybe it's the thread that check the connection, when board connected,
>>>>> thread is sleeping...or destroyed by android.
>>>>>
>>>>> I also noticed that into the AndroidManifest.xml
>>>>> I absolutely necessary to add ...
>>>>>
>>>>> <intent-filter>
>>>>> <action
>>>>> android:name="android.hardware.usb.action.USB_ACCESSORY_ATTACHED" />
>>>>> </intent-filter>
>>>>> <intent-filter>
>>>>> <action
>>>>> android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" />
>>>>> </intent-filter>
>>>>> <meta-data
>>>>> android:name="android.hardware.usb.action.USB_ACCESSORY_ATTACHED"
>>>>> android:resource="@xml/accessory_filter" />
>>>>> <meta-data
>>>>> android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"
>>>>> android:resource="@xml/device_filter" />
>>>>>
>>>>> ... these intent-filter inside the first activity that contains :
>>>>>
>>>>> <intent-filter>
>>>>> <action android:name="android.intent.action.MAIN" />
>>>>> <category android:name="android.intent.category.LAUNCHER"
>>>>> />
>>>>> </intent-filter>
>>>>>
>>>>> If not, when I plug usb, android will notify that it doesn't know any
>>>>> application that will use ioio board - IOIO Standard Application
>>>>> But in that case, I doesn't need to restart my app to get the loop
>>>>> functioning. It works fine the first time.
>>>>> But I need to fight with android notification to cancel it several
>>>>> times...
>>>>>
>>>>> Then, I think I will continue to use the open accessory protocol to auto
>>>>> launch my app when board is plugged to the phone...
>>>>>
>>>>> But then I need to find a way to restart twice the app... Kill the first
>>>>> instance and relaunch a new one.
>>>>>
>>>>> Do you know a way to do that ?
>>>>>
>>>>> Thanks for help.
>>>>> Lo.
>>>>>
>>>>>
>>>>> --
>>>>> 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 http://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 http://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 http://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 http://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 http://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 http://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 http://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 http://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 http://groups.google.com/group/ioio-users.
For more options, visit https://groups.google.com/d/optout.
