The IOIOBridge should be able to connect to the IOIO regardless of whether the emulator is on or not. I suspect that that *-*IOIO0 on the command line as opposed to /dev/IOIO0 is what's causing the problem.
On Fri, Feb 26, 2016 at 4:09 AM, Ilan Tal <[email protected]> wrote: > Ytai, > I did do the comment on the src/main/AndroidMainifest.xml. Last time it > told me that the changes wouldn't be saved. Today it doesn't complain. In > any case it makes no difference. Killing the line by commenting it out > achieves the same effect as deleting it. > There were always 2 emulators running, one which was disconnected and > another one. That always confused me. Finally I found an answer. > > ilan@ilan-Desktop:~/Documents/ioio/ioioBridge$ ./ioiobridge -IOIO0 > adb server is out of date. killing... > * daemon started successfully * > IOIO Emulator Bridge, V1.00 > Press Ctrl-C at any point to exit > > Connecting to IOIO... > > The line immediately following the ioiobridge command says adb server is > out of date. killing... > That is leaving behind a dead thread. > I confirmed this is the case because I would wait for the emulator to come > up and then turn on the ioiobridge. The second I got the command of the adb > server being out of date I would have 2 choices of emulators to connect: 1 > disconnected and 1 apparently alive. I would always connect to the alive > one but I couldn't figure out where the dead one came from. > > Since it still doesn't work, i.e. do anything useful, I tried to put in 2 > break points > > @Override > protected void setup() throws ConnectionLostException { > showVersions(ioio_, "IOIO connected!"); > led_ = ioio_.openDigitalOutput(0, true); > enableUi(true); > } > > /** > * Called repetitively while the IOIO is connected. > * > * @throws ConnectionLostException > * When IOIO connection is lost. > * @throws InterruptedException > * When the IOIO thread has been interrupted. > * > * @see ioio.lib.util.IOIOLooper#loop() > */ > @Override > public void loop() throws ConnectionLostException, InterruptedException { > led_.write(!button_.isChecked()); > Thread.sleep(100); > } > > > One in the setup() and the second in the loop(). It never hit either one, or > at least I never got an indication that it hit a breakpoint. > > If you verified that commenting out those 2 compile lines, then it should > work. I assume I've got the emulator with the ioiobridge attached but I have > no independent way to verify it. It has stopped giving me the error but it > does no useful work. The log looks like > > 02-26 12:07:03.560 27767-27767/ioio.examples.hello W/System: ClassLoader > referenced unknown path: /data/app/ioio.examples.hello-2/lib/x86_64 > 02-26 12:07:03.930 27767-27767/ioio.examples.hello > I/IOIOBaseApplicationHelper: Using IOIOLib version: IOIO0505 > 02-26 12:07:04.040 27767-27767/ioio.examples.hello D/IOIOConnectionRegistry: > Successfully added bootstrap class: > ioio.lib.impl.SocketIOIOConnectionBootstrap > 02-26 12:07:04.140 27767-27769/ioio.examples.hello W/art: Suspending all > threads took: 50ms > 02-26 12:07:04.140 27767-27767/ioio.examples.hello D/IOIOConnectionRegistry: > Bootstrap class not found: > ioio.lib.android.accessory.AccessoryConnectionBootstrap. Not adding. > 02-26 12:07:04.140 27767-27767/ioio.examples.hello E/BluetoothAdapter: > Bluetooth binder is null > 02-26 12:07:04.210 27767-27767/ioio.examples.hello D/IOIOConnectionRegistry: > No runtime support for: > ioio.lib.android.bluetooth.BluetoothIOIOConnectionBootstrap. Not adding. > 02-26 12:07:04.210 27767-27767/ioio.examples.hello D/IOIOConnectionRegistry: > Bootstrap class not found: ioio.lib.android.device.DeviceConnectionBootstrap. > Not adding. > 02-26 12:07:04.270 27757-27757/? E/memtrack: Couldn't load memtrack module > (No such file or directory) > 02-26 12:07:04.270 27757-27757/? E/android.os.Debug: failed to load memtrack > module: -2 > 02-26 12:07:04.270 27757-27757/? I/Radio-JNI: register_android_hardware_Radio > DONE > 02-26 12:07:04.480 27767-27769/ioio.examples.hello W/art: Suspending all > threads took: 40ms > 02-26 12:07:04.510 27767-27797/ioio.examples.hello D/IOIOImpl: Waiting for > IOIO connection > 02-26 12:07:04.510 27767-27797/ioio.examples.hello V/IOIOImpl: Waiting for > underlying connection > 02-26 12:07:04.510 27767-27797/ioio.examples.hello V/SocketIOIOConnection: > Creating server socket > 02-26 12:07:04.510 27767-27797/ioio.examples.hello V/SocketIOIOConnection: > Waiting for TCP connection > 02-26 12:07:04.540 27757-27757/? D/AndroidRuntime: Calling main entry > com.android.commands.wm.Wm > 02-26 12:07:04.560 27757-27757/? D/AndroidRuntime: Shutting down VM > 02-26 12:07:04.580 27767-27767/ioio.examples.hello D/gralloc_goldfish: > Emulator without host-side GPU emulation detected. > 02-26 12:07:04.730 1353-1372/system_process I/ActivityManager: Displayed > ioio.examples.hello/.MainActivity: +1s530ms > > Do you see any hints here? > > Thanks, > Ilan > > > -- > 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. > -- 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.
