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 wrote:
> There is an apparentbugin theBluetoothservice discovery code, as
> has been ment
(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
Is this related to:
http://stackoverflow.com/questions/2661932/problem-with-bluetooth-on-android-2-1-samsung-spica-i5700-where-pairing-works-b
http://pastebin.org/191806
http://pastebin.org/191824
http://pastebin.org/191830
It sounds like the same issue...
On Apr 29, 2:09 am, DonFrench 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 con
No, it is the AutoMate robot from The Gadget Works (http://
www.TheGadgetWorks.com).
On Apr 30, 3:13 pm, dan raaka wrote:
> is the device being referred here Spica (i5700)?
>
> -Dan
>
> On Fri, Apr 30, 2010 at 12:10 PM, DonFrench wrote:
> > I am not sure if it is the same issue but it sounds rel
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 wrote:
> is the device being referred here Spica (i5700)?
I may have accidentally replied to only Dan, so here's the bugreport
info I referred to:
-- VERSION INFO --
currenttime=Sat May 1 21:31:48 CEST 2010
kernel.version=Linux version 2.6.29 (r...@se-s611) (gcc version 4.3.1
(for S3C64XX Samsung Electronics AP Development Team) ) #2 Sat Mar 13
Nexus One. No experience with spica.
On May 1, 6:35 am, frankentux 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?
>
http://stackoverflow.com/questions/2661932
http://pastebin.org/199621
could also be interesting
On May 2, 2:32 am, DonFrench wrote:
> Nexus One. No experience with spica.
>
> On May 1, 6:35 am, frankentux wrote:
>
> > My device is a i5700 Samsung spica. The stackoverflow links and the
> > logc
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 wrote:
> http://stackoverflow.com/quest
Dan,
what is the build id that you mean? Can you elaborate on what the fix
is?
Ciaran
On 14 Mai, 01:12, danraaka wrote:
> Newer build sud fix this.
>
> -Dan
>
> On Mon, May 10, 2010 at 7:29 AM, frankentux
> wrote:
>
> > The same problem seems to be detailed here:
> >http://forum.samdroid.net/t
I updated my firmware to the latest available version from
http://samsung-firmwares.com and bluetooth spp (as checked with the
HxM heart rate monitor) worked out of the box.
Ciaran
On May 16, 7:01 pm, frankentux wrote:
> Dan,
>
> what is the build id that you mean? Can you elaborate on what the
So if I want to connect and read from a bluetooth stream on an adp2
phone running 1.6, I need to wait for some kind soul to write a
backport from 2.2 to 1.6 and publish it so I can compile with the
backport jar? Or patiently wait for some kind HTC employee to work on
a 1.6 to 2.0 port, then a 2.1 p
is the device being referred here Spica (i5700)?
-Dan
On Fri, Apr 30, 2010 at 12:10 PM, DonFrench 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 n
can you paste the build fingerprint of your device ?
-Dan
On Sat, May 1, 2010 at 6:35 AM, frankentux 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 hav
Newer build sud fix this.
-Dan
On Mon, May 10, 2010 at 7:29 AM, frankentux 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 c
This issue is fixed in newer binaries/builds for this device.
-Dan
On Sun, May 16, 2010 at 10:01 AM, frankentux wrote:
> Dan,
>
> what is the build id that you mean? Can you elaborate on what the fix
> is?
>
> Ciaran
>
> On 14 Mai, 01:12, danraaka wrote:
> > Newer build sud fix this.
> >
> > -
17 matches
Mail list logo
