Closed ankitdaf closed 12 years ago
ijdoc
commented
12 years ago This usually happens when the Shield does not echo the data being sent by the Android device. We should check if the emulator has the required echoing routine (i.e., immediately writing to the BT socket any data received).
ijdoc
commented
12 years ago Seems like there is an issue with the channels used to open the socket connection with the Android device. When I tried this script on Windows, it said it was expecting a connection on channel 9 while the OS said a serial bluetooth channel was available in COM3. Maybe the channel the OS is opening is not the one actually being used by the emulator?
ankitdaf
commented
12 years ago I am not sure if that is an additional problem, but I figured out what the problem with Ubuntu Linux was.
The problem there was with the BlueZ stack that Ubuntu has in its repo.
I removed the default install and used the following versions :
bluez-4.99 obexd-0.45 bluez-hcidump-2.3 (Don't think if this is need, but anyway )
You can download these from http://www.bluez.org/
Will still have a look at the problem Jorge mentions in Windows.
ijdoc
commented
12 years ago I can confirm that the issue is resolved when the latest version of bluez is installed. We need to add this to the documentation. That is the Wiki and README
When trying to connect to the emulator from the Tecla Access app for Android, the Bluetooth connection keeps on disconnecting and reconnecting.
On the Android, the message keeps on flashing as "Tecla Shield connected" and "Tecla Shield Disconnected" alternately.
The flow never proceeds to "Accepted connection from.."
Debug log is here : http://pastebin.com/pGahPnYe