Yeah, I'd second that, talking to n>3 devices has been pretty tough
for me. With 2.2 I was barely able to get 3 to connect most of the
time, extremely difficult, and very unreliable. Pushing it to four
was possible perhaps once, though extremely unstable?
As for your rfcomm question, I'm unsure,
Hi,
I can't confirm it is just 2.2 but I have had similar experiences & I
have not been able to get more than four phones to connect via
bluetooth reliably on any version of Android in a single server many
clients arrangement. I have not tried a daisy chain configuration
where each phone just conn
Neil,
My original implementation used a pool of 7 UUIDs, but since thats a
nightmare to manage if you don't make activity limiting assumptions, I
tried re-implementing based on a single UUID. My tests showed that I
got the same behavior with 1 UUID or 7, so I ripped out the UUID
management stuff.
I'm doing the same, extended the Bluetooth Chat example in a similar
way to you.
Not tried with 4 devices yet, your experience is worrying!
Any updates?
Are you doleing out from a Collection of 7 UUIDs?
My Asus EeePad or Nexus One can't sustain a Bluetooth audio stream at
the same time as one o
4 matches
Mail list logo
