Newer build sud fix this. -Dan
On Mon, May 10, 2010 at 7:29 AM, frankentux <cfarrell1...@googlemail.com>wrote: > The same problem seems to be detailed here: > http://forum.samdroid.net/threads/598 > Looks like SPP is completely broken on the i5700 - possibly because of > the Broadcom BCM4325. > On the positive side, that chip has a FM module :-) > > On May 3, 6:56 pm, frankentux <cfarrell1...@googlemail.com> wrote: > > http://stackoverflow.com/questions/2661932http://pastebin.org/199621 > > > > could also be interesting > > > > On May 2, 2:32 am, DonFrench <dcfre...@gmail.com> wrote: > > > > > Nexus One. No experience with spica. > > > > > On May 1, 6:35 am, frankentux <cfarrell1...@googlemail.com> wrote: > > > > > > My device is a i5700 Samsung spica. The stackoverflow links and the > > > > logcats i pasted to pastebin.com (again, see my last post above) all > > > > relate to the issue on the spica. Do you have a similar issue with a > > > > spica? > > > > > > On 1 Mai, 00:13, dan raaka <danra...@gmail.com> wrote: > > > > > > > is the device being referred here Spica (i5700)? > > > > > > > -Dan > > > > > > > On Fri, Apr 30, 2010 at 12:10 PM, DonFrench <dcfre...@gmail.com> > wrote: > > > > > > I am not sure if it is the same issue but it sounds related. My > app > > > > > > was eventually able to connect to the device I was having trouble > with > > > > > > but only after I manually unpaired it. I never deliberately > paired it > > > > > > in the first place and I was never asked for a pin during the > time it > > > > > > was failing to connect. The device had apparently been > automatically > > > > > > paired by Android when it was first detected, as are other nearby > > > > > > laptops and phones and PDAs. After unpairing it, I did not > re-pair > > > > > > through the Android utility but ran my app again and attempted to > > > > > > connect to it, at which time I was prompted to enter the pin and > to > > > > > > pair. This request to pair did not come directly from my code > but > > > > > > resulted from a call to BluetoothSocket.connect( ). At this > point it > > > > > > successfully connected and continues to connect. So it seems > like the > > > > > > automatic pairing does something that prevents later connection. > I > > > > > > wonder if once it is automatically paired without a pin, future > > > > > > attempts to connect recognize that it has been paired but doesn't > > > > > > recognize that no pin was ever requested and so fails for lack of > a > > > > > > valid pin. Just a guess. > > > > > > > > On Apr 29, 9:21 am, frankentux <cfarrell1...@googlemail.com> > wrote: > > > > > > > Is this related to: > > > > > > > > > > http://stackoverflow.com/questions/2661932/problem-with-bluetooth-on-... > > > > > > > > > http://pastebin.org/191806http://pastebin.org/191824http://pastebin.o... > > > > > > > > > It sounds like the same issue... > > > > > > > > > On Apr 29, 2:09 am, DonFrench <dcfre...@gmail.com> wrote: > > > > > > > > > > (sorry, premature Send of previous message) > > > > > > > > > > As I was saying, the two devices have the same name but > different MAC > > > > > > > > addresses. Whether this was related to the problem I am not > sure. > > > > > > > > But simply unpairing the device that would not connect solved > the > > > > > > > > problem. It re-paired the next time my code tried to connect > and from > > > > > > > > then on I could connect to either device without doing any > more > > > > > > > > unpairing. > > > > > > > > > > On Apr 28, 5:03 pm, DonFrench <dcfre...@gmail.com> wrote: > > > > > > > > > > > Update to this problem: I discovered that the device that > could not > > > > > > > > > be connected to had been paired at some time in the past. > Both > > > > > > > > > devices have the same name but different MAC > > > > > > > > > > > On Apr 24, 4:30 pm, DonFrench <dcfre...@gmail.com> wrote: > > > > > > > > > > > > There is an apparentbugin theBluetoothservice discovery > code, as > > > > > > > > > > has been mentioned by several people on several forums. > The upshot > > > > > > is > > > > > > > > > > that the BluetoothSocket.connect( ) method consistently > fails to > > > > > > > > > > discover a valid SPP service on some devices that are > discoverable > > > > > > > > > > with non-Android devices while it consistently succeeds > to discover > > > > > > > > > > the SPP service on seemingly identical devices. > Obviously, the two > > > > > > > > > > devices are not identical but the fact is that I > manufacture two > > > > > > such > > > > > > > > > > devices and there is nothing obviously different about > them. I can > > > > > > > > > > consistently connect to both devices from a Windows > Mobile app. I > > > > > > > > > > hope thatGooglewill address thisbugin the very near > future. I > > > > > > > > > > will be willing to test any trialbug-fixes on my devices. > > > > > > > > > > > > Here is the relevant log output from the failed attempt: > > > > > > > > > > > > 04-24 15:23:33.268: INFO/ActivityManager(82): Starting > activity: > > > > > > > > > > Intent { cmp=com.thegadgetworks/.DeviceListActivity } > > > > > > > > > > 04-24 15:23:33.308: DEBUG/DeviceListActivity(8055): > doDiscovery() > > > > > > > > > > 04-24 15:23:33.318: ERROR/BluetoothEventLoop.cpp(82): > event_filter: > > > > > > > > > > Received signal org.bluez.Adapter:PropertyChanged from > > > > > > /org/bluez/7766/ > > > > > > > > > > hci0 > > > > > > > > > > 04-24 15:23:33.318: > VERBOSE/BluetoothEventRedirector(4213): > > > > > > Received > > > > > > > > > > android.bluetooth.adapter.action.DISCOVERY_STARTED > > > > > > > > > > 04-24 15:23:36.608: ERROR/BluetoothEventLoop.cpp(82): > event_filter: > > > > > > > > > > Received signal org.bluez.Adapter:DeviceFound from > /org/bluez/7766/ > > > > > > > > > > hci0 > > > > > > > > > > 04-24 15:23:36.638: > VERBOSE/BluetoothEventRedirector(4213): > > > > > > Received > > > > > > > > > > android.bluetooth.device.action.FOUND > > > > > > > > > > 04-24 15:23:40.368: ERROR/BluetoothEventLoop.cpp(82): > event_filter: > > > > > > > > > > Received signal org.bluez.Adapter:PropertyChanged from > > > > > > /org/bluez/7766/ > > > > > > > > > > hci0 > > > > > > > > > > 04-24 15:23:40.368: ERROR/BluetoothService.cpp(82): > > > > > > > > > > stopDiscoveryNative: D-Bus error in StopDiscovery: > > > > > > > > > > org.bluez.Error.Failed (Invalid discovery session) > > > > > > > > > > 04-24 15:23:40.408: > VERBOSE/BluetoothEventRedirector(4213): > > > > > > Received > > > > > > > > > > android.bluetooth.adapter.action.DISCOVERY_FINISHED > > > > > > > > > > 04-24 15:23:40.418: ERROR/BluetoothService.cpp(82): > > > > > > > > > > stopDiscoveryNative: D-Bus error in StopDiscovery: > > > > > > > > > > org.bluez.Error.Failed (Invalid discovery session) > > > > > > > > > > 04-24 15:23:40.428: ERROR/BluetoothEventLoop.cpp(82): > > > > > > > > > > onCreateDeviceResult: D-Bus error: > org.bluez.Error.AlreadyExists > > > > > > > > > > (Device already exists) > > > > > > > > > > 04-24 15:23:40.448: > VERBOSE/BluetoothEventRedirector(4213): > > > > > > Received > > > > > > > > > > android.bleutooth.device.action.UUID > > > > > > > > > > 04-24 15:23:46.448: > VERBOSE/BluetoothEventRedirector(4213): > > > > > > Received > > > > > > > > > > android.bleutooth.device.action.UUID > > > > > > > > > > 04-24 15:24:14.168: ERROR/BluetoothService.cpp(82): > > > > > > > > > > stopDiscoveryNative: D-Bus error in StopDiscovery: > > > > > > > > > > org.bluez.Error.Failed (Invalid discovery session) > > > > > > > > > > > > And here is the log from when it successfully connected: > > > > > > > > > > > > 04-24 16:09:02.337: INFO/ActivityManager(82): Starting > activity: > > > > > > > > > > Intent { cmp=com.thegadgetworks/.DeviceListActivity } > > > > > > > > > > 04-24 16:09:02.437: DEBUG/DeviceListActivity(8230): > doDiscovery() > > > > > > > > > > 04-24 16:09:02.457: ERROR/BluetoothEventLoop.cpp(82): > event_filter: > > > > > > > > > > Received signal org.bluez.Adapter:PropertyChanged from > > > > > > /org/bluez/7766/ > > > > > > > > > > hci0 > > > > > > > > > > 04-24 16:09:02.477: > VERBOSE/BluetoothEventRedirector(4213): > > > > > > Received > > > > > > > > > > android.bluetooth.adapter.action.DISCOVERY_STARTED > > > > > > > > > > 04-24 16:09:05.079: ERROR/BluetoothEventLoop.cpp(82): > event_filter: > > > > > > > > > > Received signal org.bluez.Adapter:DeviceFound from > /org/bluez/7766/ > > > > > > > > > > hci0 > > > > > > > > > > 04-24 16:09:05.117: > VERBOSE/BluetoothEventRedirector(4213): > > > > > > Received > > > > > > > > > > android.bluetooth.device.action.FOUND > > > > > > > > > > 04-24 16:09:08.567: ERROR/BluetoothEventLoop.cpp(82): > event_filter: > > > > > > > > > > Received signal org.bluez.Adapter:PropertyChanged from > > > > > > /org/bluez/7766/ > > > > > > > > > > hci0 > > > > > > > > > > 04-24 16:09:08.567: ERROR/BluetoothService.cpp(82): > > > > > > > > > > stopDiscoveryNative: D-Bus error in StopDiscovery: > > > > > > > > > > org.bluez.Error.Failed (Invalid discovery session) > > > > > > > > > > 04-24 16:09:08.607: > VERBOSE/BluetoothEventRedirector(4213): > > > > > > Received > > > > > > > > > > android.bluetooth.adapter.action.DISCOVERY_FINISHED > > > > > > > > > > 04-24 16:09:08.617: ERROR/BluetoothService.cpp(82): > > > > > > > > > > stopDiscoveryNative: D-Bus error in StopDiscovery: > > > > > > > > > > org.bluez.Error.Failed (Invalid discovery session) > > > > > > > > > > 04-24 16:09:08.877: ERROR/BluetoothEventLoop.cpp(82): > event_filter: > > > > > > > > > > Received signal org.bluez.Device:PropertyChanged from > > > > > > /org/bluez/7766/ > > > > > > > > > > hci0/dev_00_0C_84_00_72_D2 > > > > > > > > > > 04-24 16:09:09.167: > VERBOSE/BluetoothEventRedirector(4213): > > > > > > Received > > > > > > > > > > android.bleutooth.device.action.UUID > > > > > > > > > > 04-24 16:09:14.647: > VERBOSE/BluetoothEventRedirector(4213): > > > > > > Received > > > > > > > > > > android.bleutooth.device.action.UUID > > > > > > > > > > > > Please fix thisbug! Thank you. > > > > > > > > > > > > -- > > > > > > > > > > You received this message because you are subscribed to > theGoogle > > > > > > > > > > Groups "Android Developers" group. > > > > > > > > > > To post to this group, send email to > > > > > > android-developers@googlegroups.com > > > > > > > > > > To unsubscribe from this group, send email to > > > > > > > > > > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com><android-developers%2Bunsubs > cr...@googlegroups.com> > > > > > > > > > > For more options, visit this group athttp:// > > > > > > groups.google.com/group/android-developers?hl=en > > > > > > > > > > > -- > > > > > > > > > You received this message because you are subscribed to > theGoogle > > > > > > > > > Groups "Android Developers" group. > > > > > > > > > To post to this group, send email to > > > > > > android-developers@googlegroups.com > > > > > > > > > To unsubscribe from this group, send email to > > > > ... > > > > read more ยป > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to android-developers@googlegroups.com > To unsubscribe from this group, send email to > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
