Closed GoogleCodeExporter closed 9 years ago
Am I right that the added BT device disappears after you hit disconnect?
Please clarify bullet 4.
Original comment by bonifaz....@gmail.com
on 23 Jun 2010 at 9:43
At step 4 device is still in the bt devices list but not visible if you go into
add devices.
I observe that successfull connects have the device still shown in the bt
connect screen.
The device itself is still discoverable and connectable but the phone Amarino
app will not connect.
Original comment by jgcrouch...@gmail.com
on 23 Jun 2010 at 10:45
I look into it.
Original comment by bonifaz....@gmail.com
on 30 Jun 2010 at 11:13
[deleted comment]
- Which BT module do you have?
- Can you verify if disconnect works properly, or does it just not disconnect.
- Is there a indicator light on your BT module which tells you the state of
your connection?
Original comment by bonifaz....@gmail.com
on 30 Jun 2010 at 11:17
Using SURE BT module, cannot easily tell at the BT module if disconnect worked
properly. A couple of undocumented pins change voltage at connect and do not
change back - so that may indicate disconnect not working.
Assume it is an Amarino fault because resetting at phone end fixes issue.
I note you have another issue open where disconnect does not work - also HTC
Desire!
Original comment by jgcrouch...@gmail.com
on 1 Jul 2010 at 10:44
Indeed, it seems to be the same issue.
Could you try the latest Amarino version 0.5 and check if your issue is still
remain.
Original comment by bonifaz....@gmail.com
on 1 Jul 2010 at 10:50
Issue 1 has been merged into this issue.
Original comment by bonifaz....@gmail.com
on 1 Jul 2010 at 10:52
@jgcrouchley: if version 0.5 doesn't fix the issue, could you please send the
log from your phone to me right after your tried to disconnect and reconnect.
You could use "SendLog" which is downloadable for free on the Android market or
the Android SDK tool DDMS to get access to your phones log (logcat).
Original comment by bonifaz....@gmail.com
on 1 Jul 2010 at 10:56
Log sent to bonifaz@media.mit.edu.
I tried connecting to the BT device with my PC - no problems connect, send
data, disconnect repeatedly. By observing I note that pin 28 goes high when
connected and pin 30 goes low. The PC appears to disconnect properly.
Amarino does not disconnect properly - the pins stay in the connect state.
Original comment by jgcrouch...@gmail.com
on 1 Jul 2010 at 2:02
Version 0.5 installed
Sent the phone log.
My step :
1. Using test event, connect all is OK
2. Disconnect
3. attempt to connect again (Device IS present on device screen)
4. The connect button change to gray and say Connecting and hang (return active
after screen lock/unlock)
5. Stop bluetooth on phone
6. kill Amarino and restart
7. connect - all is fine again
Note : Sparkfun Bluetooth Mate (BT-Serial-Bridge)
Original comment by vaddavv...@gmail.com
on 1 Jul 2010 at 2:31
Attachments:
Following findings so far.
HTC Desire disconnects fine, but a reconnect triggers an error: Cleaning up
failed UUID channel lookup
Various people have reported that the HTC Desire has issues connecting to SPP
Bluetooth devices. I am not sure if I can find a workaround for it, since it
seems to be a HTC Desire firmware bug.
But as I said, hopefully I find a solution for it anyway. It is just not simple
without a HTC Desire device in my hands.
I uploaded already a newer version of Amarino (0.52) maybe this does the job
already.
Original comment by bonifaz....@gmail.com
on 1 Jul 2010 at 3:25
Here is the corresponding issue within the Android open source project.
http://code.google.com/p/android/issues/detail?id=8382
http://groups.google.com/group/android-developers/browse_thread/thread/e8c16aff1
10ebbd5
and other people having the same issue which is not Amarino related, but a bug
in HTC Desires Bluetooth implementation. I think they will fix it when Android
2.2 will be shipped to the Desire.
I tried the workaround calling the undocumented method mentionend in that
discussion. It is implemented in Amarino v.0.52
Original comment by bonifaz....@gmail.com
on 1 Jul 2010 at 3:34
Original comment by bonifaz....@gmail.com
on 21 Jul 2010 at 5:15
Original issue reported on code.google.com by
jgcrouch...@gmail.com
on 23 Jun 2010 at 2:41