March 2004 - Bluetooth-dev - lists.apple.com

Re: How are incoming connections handled?
by Eric Brown 11 Mar '04

11 Mar '04

On Mar 11, 2004, at 1:09 PM, Crichlow, Eric wrote: > Okay, > > The combination of the Bluetooth system software not being thread > safe > and the "fact" (as far as I can tell, never got any confirmation or > denial > of this from anyone) that the rfcommChannelData callback doesn't get > called > while the app is running in NSEventTrackingRunLoopMode has caused me > to go > back to the drawing board and totally re-architect my app. > I'm filing a bug report that the current API doesn't provide a mechanism to control the run loop modes that the incoming Bluetooth events are handled in. It sounds like that would have helped you here. > Now I'm at another sticking point where things don't seem to work > as > expected, but maybe my expectations are just incorrect. > > I have any number of Bluetooth devices that may attempt connection > to the > computer. > > I handle this by initially starting a secondary (to my main > application) > app which sets up a Bluetooth service and then registers for > notifications > when a device initiates connection to that service. Once a connection > is > completed, the process unregisters from getting further notifications, > and > tells the main app to launch a new instance of the secondary app, which > registers itself for any future incoming devices. > > The problem is, as soon as the next secondary app instance is > launched > and registers for a notification, it immediately gets called. But it's > getting notified of the incoming device that already got handled > (connected > to) by the last instance of the secondary app. > > Once a device initiates connection to the computer, and an > application > completes connection to it, shouldn't the system NOT generate an > incoming > notification to any app that registers for such notifications AFTER the > connection was completed? > > The problem is that in a number of cases, you need a mechanism to both determine what devices are already connected and be notified about new ones. Instead of providing separate APIs to handle this, a single API was provided to do both. This also gets around a race condition where if you asked for the existing connections, then registered for new device notifications, you could miss one if one came in at just the right time. In that case, you'd have to register the notification first and then ask for the existing connections possibly resulting in the same device being reported twice. The current API doesn't have that limitation. When the initial notification is registered, the caller is notified about all existing connections. Then as new connections are established, new notifications are sent. - Eric [demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s] _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Massive Latency in a Headset device?
by Chilton Webb 11 Mar '04

11 Mar '04

Hi, I'm curious about a latency I'm seeing with a BlueTooth headset device. When audio is transmitted from it to the Mac (a 12" AlBook), there's a lag of about half a second or longer. Anything I can do to reduce that? Thanks, -Chilton _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

How are incoming connections handled?
by Crichlow, Eric 11 Mar '04

11 Mar '04

Okay, The combination of the Bluetooth system software not being thread safe and the "fact" (as far as I can tell, never got any confirmation or denial of this from anyone) that the rfcommChannelData callback doesn't get called while the app is running in NSEventTrackingRunLoopMode has caused me to go back to the drawing board and totally re-architect my app. Now I'm at another sticking point where things don't seem to work as expected, but maybe my expectations are just incorrect. I have any number of Bluetooth devices that may attempt connection to the computer. I handle this by initially starting a secondary (to my main application) app which sets up a Bluetooth service and then registers for notifications when a device initiates connection to that service. Once a connection is completed, the process unregisters from getting further notifications, and tells the main app to launch a new instance of the secondary app, which registers itself for any future incoming devices. The problem is, as soon as the next secondary app instance is launched and registers for a notification, it immediately gets called. But it's getting notified of the incoming device that already got handled (connected to) by the last instance of the secondary app. Once a device initiates connection to the computer, and an application completes connection to it, shouldn't the system NOT generate an incoming notification to any app that registers for such notifications AFTER the connection was completed? ...Thanx... ...Eric... _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Re: Getting Apple to support a phone in iSync?
by Garth Cummings 10 Mar '04

10 Mar '04

Hi Steve! How are things in Chi-town? On Mar 8, 2004, at 3:20 PM, Steve Klingsporn wrote: Hello - Would an Apple employee please get back to me about what I need to do to either get Apple to support a new cell phone with iSync, or how to go about getting some form of iSync support? File an enhancement request using the online bug reporter page: <http://developer.apple.com/bugreporter>. Bug reports go straight into our bug tracking system and are routed to the team responsible for the specified system component. You do have to be a member of the Apple Developer Connection to use that page, but you can easily sign up for the (no charge) Online membership. Good luck, --gc _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Re: Privilege violation...
by Alex Eiser 10 Mar '04

10 Mar '04

Hey carl, Say hi to Jeff Long for me! I was working on something similar to this around Christmas. I didn't get quite as far as you, but I was using a very different approach. I tried modifying the sample code for the chat server to function with l2cap, and more recently to do cross linux- mac communication over RFCOMM (using the sample app again). The l2cap chat program worked well for me on multiple Macs, and even supporting multiple simultaneous connections... sortof. I noticed in your code your calling the openL2CAPChannel and then setting a delegate.. might be better to try and use the openL2CAPChannelSync Call. I also found that the chat client sample code wasn't to bad to work with. I can send you my adapted for l2cap stuff if you want. (Although I yesterday I moved my linux mac into the lab where I am testing the work I am doing.. so I can't try the code out.. or clean it up.) Working with RFComms on linux and the mac is not to bad. The only problem, is that the linux standard RFCOMM listener seems to repeat all the data sent on the channel back to the sender one character at a time. For my uses this didn't matter since I only wanted a one way channel. Did you set up an SDP record on the linux box for your service? Best of luck! Alex On 8-Mar-04, at 2:42 PM, Carl Norum wrote: > Hi there! I'm trying to get some simple bluetooth apps working. I've > written an L2CAP based text chat program for linux using the BlueZ > stack, and now I'm trying to write a Mac OS X client to connect to it > as well. > > At the beginning everything works fine; I can connect to the linux box > using the following code: > > NSAutoreleasePool *mainPool; > > int main (int argc, const char *argv[]) > { > IOBluetoothDevice *dev; > BluetoothDeviceAddress btAddr; > IOBluetoothL2CAPChannel *channel; > IOReturn err; > ChatDelegate *interface; > > mainPool = [[NSAutoreleasePool alloc] init]; > > interface = [[ChatDelegate alloc] init]; > > IOBluetoothNSStringToDeviceAddress(@"00:04:76:C8:40:B0", &btAddr); > dev = [IOBluetoothDevice withAddress:&btAddr]; > > err = [dev openL2CAPChannel:kBluetoothL2CAPPSMRFCOMM > findExisting:FALSE newChannel:&channel]; > NSLog(@"openL2CAPChannel: 0x%08x", err); > if (err != kIOReturnSuccess) > exit(0); > > [channel setDelegate:interface]; > > [[NSRunLoop currentRunLoop] run]; > > return 0; > } > > The ChatDelegate code looks like this: > > - (void)sender:(IOBluetoothL2CAPChannel *)channel > { > IOReturn err; > senderPool = [[NSAutoreleasePool alloc] init]; > char buffer[BUFFER_SIZE]; > > do { > fgets(buffer, BUFFER_SIZE, stdin); > err = [channel writeSync:buffer length:strlen(buffer) + 1]; > NSLog(@"Return: 0x%0x String: %s", err, buffer); > } while (strcmp(buffer, ".\n") != 0); > > [channel closeChannel]; > [senderPool release]; > [mainPool release]; > exit(0); > } > > - (void)l2capChannelData:(IOBluetoothL2CAPChannel*)l2capChannel > data:(void *)dataPointer length:(size_t)dataLength > { > NSLog(@"Data received"); > printf(dataPointer); > if (strcmp(dataPointer, ".\n") == 0) { > [l2capChannel closeChannel]; > [senderPool release]; > [mainPool release]; > exit(0); > } > } > > - > (void)l2capChannelOpenComplete:(IOBluetoothL2CAPChannel*)l2capChannel > status:(IOReturn)error > { > NSLog(@"Channel Open Complete: 0x%x", error); > if (error == kIOReturnSuccess) > [NSThread detachNewThreadSelector:@selector(sender:) > toTarget:self withObject:l2capChannel]; > } > > > The connection appears to work successfully - I get my @"Channel Open > Complete" message fine, and the linux box prints out "Connection > Accepted" after the accept() call returns. However, data sending and > receiving appears not to work. Anything I type in on the linux box > causes a successful return from send(), but nothing shows up on the > Mac via l2capChannelData:data:length. Likewise, anything entered on > the mac (from sender:) doesn't get sent - I get an IOReturn error > indicating kIOReturnNotPrivileged. Why does this happen? Any > thoughts, ideas, better ways to do this? I'm just getting started > with bluetooth, so I may be making terrible errors. > > Thanks everyone! > > -- > Carl J Norum > Academic Director, IEEE NSS Student Branch > Final Year Electrical Engineering/Computer Science Student > University of Saskatchewan > Saskatoon, Canada > > http://norum.homeunix.net/~carl/ > _______________________________________________ > bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com > Help/Unsubscribe/Archives: > http://www.lists.apple.com/mailman/listinfo/bluetooth-dev > Do not post admin requests to the list. They will be ignored. [demime 0.98b removed an attachment of type application/pkcs7-signature which had a name of smime.p7s] _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Re: Try this Apple feedback website
by Steve Klingsporn 09 Mar '04

09 Mar '04

Thanks, Christian! I tried this yesterday - waiting to see if I hear anything. Steve On Mar 9, 2004, at 2:49 AM, Christian Lichtenvort wrote: Hi Steve, try this Apple feedback website: http://www.apple.com/feedback/isync.html Maybe they would contact you - insert your contact info in the text field -- Mit freundlichen Gruessen, Best regards, Christian Lichtenvort _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored. _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Getting Apple to support a phone in iSync?
by Steve Klingsporn 08 Mar '04

08 Mar '04

Hello - Would an Apple employee please get back to me about what I need to do to either get Apple to support a new cell phone with iSync, or how to go about getting some form of iSync support? I have talked to the folks at Mark/Space, who say Apple is generally pretty good at supporting new phones. I am not a member of the developer program, but the Chinese startup involved is willing to join a developer program if necessary to get this information or development work done. I hope that I don't have to join them into the developer program just to talk to someone who can tell me the developer program wouldn't be helpful. I don't believe there is any public API for iSync integration at the moment. We are talking to them about supporting their phone in Mac OS X. It's a very neat phone, and it would be ideal to have Apple support it. I believe they sync using SyncML, which iSync is supposed to support. They want to sync via USB cable. Thanks in advance, Steve Klingsporn (312) 316-2501 cell steve(a)buzzlabs.com _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0

Privilege violation...
by Carl Norum 08 Mar '04

08 Mar '04

Hi there! I'm trying to get some simple bluetooth apps working. I've written an L2CAP based text chat program for linux using the BlueZ stack, and now I'm trying to write a Mac OS X client to connect to it as well. At the beginning everything works fine; I can connect to the linux box using the following code: NSAutoreleasePool *mainPool; int main (int argc, const char *argv[]) { IOBluetoothDevice *dev; BluetoothDeviceAddress btAddr; IOBluetoothL2CAPChannel *channel; IOReturn err; ChatDelegate *interface; mainPool = [[NSAutoreleasePool alloc] init]; interface = [[ChatDelegate alloc] init]; IOBluetoothNSStringToDeviceAddress(@"00:04:76:C8:40:B0", &btAddr); dev = [IOBluetoothDevice withAddress:&btAddr]; err = [dev openL2CAPChannel:kBluetoothL2CAPPSMRFCOMM findExisting:FALSE newChannel:&channel]; NSLog(@"openL2CAPChannel: 0x%08x", err); if (err != kIOReturnSuccess) exit(0); [channel setDelegate:interface]; [[NSRunLoop currentRunLoop] run]; return 0; } The ChatDelegate code looks like this: - (void)sender:(IOBluetoothL2CAPChannel *)channel { IOReturn err; senderPool = [[NSAutoreleasePool alloc] init]; char buffer[BUFFER_SIZE]; do { fgets(buffer, BUFFER_SIZE, stdin); err = [channel writeSync:buffer length:strlen(buffer) + 1]; NSLog(@"Return: 0x%0x String: %s", err, buffer); } while (strcmp(buffer, ".\n") != 0); [channel closeChannel]; [senderPool release]; [mainPool release]; exit(0); } - (void)l2capChannelData:(IOBluetoothL2CAPChannel*)l2capChannel data:(void *)dataPointer length:(size_t)dataLength { NSLog(@"Data received"); printf(dataPointer); if (strcmp(dataPointer, ".\n") == 0) { [l2capChannel closeChannel]; [senderPool release]; [mainPool release]; exit(0); } } - (void)l2capChannelOpenComplete:(IOBluetoothL2CAPChannel*)l2capChannel status:(IOReturn)error { NSLog(@"Channel Open Complete: 0x%x", error); if (error == kIOReturnSuccess) [NSThread detachNewThreadSelector:@selector(sender:) toTarget:self withObject:l2capChannel]; } The connection appears to work successfully - I get my @"Channel Open Complete" message fine, and the linux box prints out "Connection Accepted" after the accept() call returns. However, data sending and receiving appears not to work. Anything I type in on the linux box causes a successful return from send(), but nothing shows up on the Mac via l2capChannelData:data:length. Likewise, anything entered on the mac (from sender:) doesn't get sent - I get an IOReturn error indicating kIOReturnNotPrivileged. Why does this happen? Any thoughts, ideas, better ways to do this? I'm just getting started with bluetooth, so I may be making terrible errors. Thanks everyone! -- Carl J Norum Academic Director, IEEE NSS Student Branch Final Year Electrical Engineering/Computer Science Student University of Saskatchewan Saskatoon, Canada http://norum.homeunix.net/~carl/ _______________________________________________ bluetooth-dev mailing list | bluetooth-dev(a)lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/bluetooth-dev Do not post admin requests to the list. They will be ignored.

1 0