https://www.google.com/search?q=ios+otg+serial+port

I think your best strategy is to take the existing code base for the BLED112 (see Hub code), and try to adapt your Java code to that. The BLED112 has sufficient buffering that it will insulate you fro

Corrected my typo in last post, OTA -> OTG,

Since AJ has the BLED112 support written, here is another approach: use an Android device that supports plugging in the BLED112 as a serial port device. The BLED112 apparently has enough buffering tha

You'd need an OTG compatible device to support the Cyton dongle. The Cyton dongle speaks non-standard Bluetooth, so is not compatible with Bluetooth 2.x, 3.x, or 4.x (BLE). Since BioEra supports FTDI

AJ Keller has the BLED112 dongle working with the GUI (Hub 1.4.2), which can be used in place of the CSR / Zadig approach. It's appears that the BLED112 has sufficient internal buffering so the host O

It seems that the built-in Bluetooth Low Energy stack in mobile devices is not designed with high speed continuous incoming packet streaming as a potential application. AJ is working on a BLED112 dong

Trying to get the Mark IV EEG up and running by connecting Cyton

You might look into what is called USB Host mode or USB-OTG for the Discovery,

Yes, that could be another idea to exploit for Android communication. I think that I'll go with the Cyton and OTG approach, and if everything works then I'll try to use the WiFi shield (is it possible

My impression is that the OTG / D2XX route with Cyton will be easier. As the example code already exists at the link you mentioned. 

thanks for your reply. I saw that thread, as well as this one about the use of OpenBCI Cyton with an OTG for Android. 

Linux has a built-in serial com port driver for the FTDI chip that is in the Cyton dongle. For example, others have been able to use the dongle with the Raspberry Linux. Be sure your USB hardware sock

May be a good one for you. This is using an OTG "on the go" adapter for your mobile device's usb socket. Such an adapter allows the OpenBCI dongle to be plugged into your phone. See,

http://openbci.com/forum/index.php?p=/discussion/279/android-apps-via-otg-cable-dongle-and-d2xx-library

the problem with the otg solution is the phone will be in a gearVR which does not expose the data connection (only the power connection)

Check these posts for info on how you can use an OTG "on the go" adapter on your Android to plug the dongle in there.

re: the OTG adapter, re-reading my original post, I think that I didn't explain the workshop idea well.  I'm wondering whether it's possible to run a workshop in which participants make their own simp

Which is why I mentioned previously, using the OTG adapter to connect your phone to an OpenBCI. Or the other approach mentioned, modifying an OpenBCI mainboard to speak Bluetooth 3.0. Which your phone

The easiest way to go may be with what is called an OTG (On The Go) usb adaptor for your smartphone. This can plug into the OpenBCI dongle, which can then talk to the OpenBCI mainboard.