February 2003 - Bluetooth-dev

Misc Bluetooth Questions
by Lawrence E. Bakst 11 Feb '03

11 Feb '03

1. Is it possible to use PacketDecoder2 to observe a conversation between two devices, not connected to a Mac? [The answer seems to be no.] 2. Do 'X' characters in the trigger for PacketDecoder2 mean don't care? [Seems like you need to specify a single BT_ADDR/MAC address] 3. Does the Broadcom chip used in the D-Link DWB-120M allow for some kind of promiscuous mode like with Ethernet, 802.11b, and Firewire so that all packets can be snooped? Do other chips allow this? 4. I have a T68i and Motorola Bluetooth Headset (MBTH). They work pretty well together. The T68i has a caller name feature where the name of the caller is announced (if you have recorded the name for voice dialing) based on caller-id. It even works (almost) with the MBTH However, sometimes (often) the caller's name is partially truncated by a ring tone. Has anyone else tried the T68i with other headsets? In particular has anyone tried this with any of the Ericsson Headsets like the HBH-10, HBH-15, HBH-30, or HBH-60. 5. I can use the Address Book to dial my T68i phone. However when I do that I can't use my MBTH. Is this a know bug? If so, this is too bad as it was one of the goals for Bluetooth, the so called "Ultimate Headset". Again, has anyone tried with Ericsson headsets? Best, leb -- Lawrence E. Bakst pleb(a)iridescent.org _______________________________________________ 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: Bluetooth Preview 2
by Stephen Martin 07 Feb '03

07 Feb '03

Bruce; Unfortunately, the Bluetooth Technology Preview 2.1 has recently been removed from the Developer support web site ( http://developer.apple.com/hardware/bluetooth/index.html ). If you'd like to submit a "no charge" developer incident at dts(a)apple.com (for administratve purposes) I'd be happy to track down a copy. Just a reminder that Apple is improving and "growing" our BlueTooth support with the Mac OS X operating system and the "Bluetooth Technology Preview 2.1" was exactly what the the title implies ... a preview. Sincerely; Steve M. Apple Developer Technology Support Engineer ===== On Thursday, February 6, 2003, at 09:16 PM, Bruce Hopkins wrote: Dear Apple Team, I'm working on a machine with OS X 10.1.5, but the current budget situation won't allow an upgrade to Jaguar. I initially had the Bluetooth Preview 2 loaded on that machine, but I had to reload the OS due to some major problems on that box. To my surprise, the Bluetooth Preview has been removed from http://www.apple.com/bluetooth page. Is there a way that I can get this? Thanks, Bruce _______________________________________________ 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. -- Stephen R. Martin Hardware Engineer Worldwide Developer Technical Support Apple Computer, Inc. email: s.martin(a)apple.com 1 Infinite Loop, MS: 303-2T phone: (408) 974-1910 Cupertino, CA 95014 fax: (408) 974-8101 _______________________________________________ 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

Nokia Card Phone and Mac OS X
by Alberto Ricci 07 Feb '03

07 Feb '03

I don't really know where to post this, but I thought the bluetooth-dev list would be a good place. Does anybody know how to get a Nokia Card Phone working (simply as a serial port) on Mac OS X? On Mac OS 9, it didn't require any drivers, you'd simply pop it in and, after it appeared on the desktop, you'd have an additional serial port available through the Open Transport APIs. On Mac OS X, I see the card phone being recognized by the OS, and a menu appears alongside with the modem, bluetooth, sound, etc. system menus, and it lists the correct device type and manufacturer (same information is available through the IORegistry APIs). However, no additional serial port is available. Is there some way I should tell the IOKit to create a new serial port linked to the pc card? Thanks! Alberto. _______________________________________________ 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

Bluetooth Preview 2
by Bruce Hopkins 07 Feb '03

07 Feb '03

Dear Apple Team, I'm working on a machine with OS X 10.1.5, but the current budget situation won't allow an upgrade to Jaguar. I initially had the Bluetooth Preview 2 loaded on that machine, but I had to reload the OS due to some major problems on that box. To my surprise, the Bluetooth Preview has been removed from http://www.apple.com/bluetooth page. Is there a way that I can get this? Thanks, Bruce _______________________________________________ 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: RFCOMMServerSample
by Marco Pontil 07 Feb '03

07 Feb '03

Hello, It is indeed a bug in the sample. In - (BOOL)publishServiceAndWaitForConnection incomgingChannelNotification = [IOBluetoothRFCOMMChannel registerForChannelOpenNotifications:self selector:@selector(newRFCOMMChannelOpened:) withChannelID:serverChannelID direction:kIOBluetoothUserNotificationChannelDirectionIncoming]; should be changed with: incomgingChannelNotification = [IOBluetoothRFCOMMChannel registerForChannelOpenNotifications:self selector:@selector(newRFCOMMChannelOpened:channel:) withChannelID:serverChannelID direction:kIOBluetoothUserNotificationChannelDirectionIncoming]; basically the change is on the selector that should be: @selector(newRFCOMMChannelOpened:channel:) Since it looks like you have an old sample I think you should also change - (void)stopProvidingChatServices: Where you see: [incomgingChannelNotification unregister]; change it into: if (incomgingChannelNotification != nil) [incomgingChannelNotification unregister]; incomgingChannelNotification = nil; This is because stopProvidingChatServices can be called more than once. And you are also correct about ' [rfcommChannel retain]; ' that one should be a release as the comment suggests. ... Marco On Thursday, February 6, 2003, at 03:44 PM, Hussain Bandukwala wrote: Attn: Mr. Marco Pontil Hi All, I have been having some problems while running the RFCOMMServerSample along with the RFCOMMClientSample from /Developer/Examples/Bluetooth on Jaguar. Occassionally, when I start the server, messages similar to the following show up: '2003-02-06 11:47:49.216 RFCOMMServerSample[443] *** -[ChatBluetoothServerInterface newRFCOMMChannelOpened:]: selector not recognized' Once the server starts up and waits for connection, the client sees the server but is unable to connect. The following message shows up on the server side: '2003-02-06 11:44:56.553 RFCOMMServerSample[443] *** -[ChatBluetoothServerInterface newRFCOMMChannelOpened:]: selector not recognized 2003-02-06 11:44:56.554 RFCOMMServerSample[443] Exception raised during posting of notification. *Ignored. *exception: *** -[ChatBluetoothServerInterface newRFCOMMChannelOpened:]: selector not recognized' I was wondering if someone could point to me where I might be going wrong. I had another question about a particular code piece. The code is from RFCOMMServerSample - ChatBluetoothServerInterface.m [lines 180-182]: ************ '// We failed to register a listener. This is cathastrofic for a server // Releases the channel: *[rfcommChannel retain]; ' Is there any reason why the rfcommChannel is being retained here? Thanking You Kindly, Hussain ======================================================================= = Hussain H. Bandukwala, C-1116, 1189 Beall Ave., The College of Wooster, Wooster, OH - 44691. (Home) -- (330)-287-3000 (x-7107) (Cell) -- (330)-412-1980 http://pages.wooster.edu/hbandukwala "It is not the strength, but the duration, of great sentiments that makes great men." -- Friedrich Nietzsche ======================================================================= = _______________________________________________ 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

Re: How to handle requests for public Bluetooth APIs
by Michael Larson 07 Feb '03

07 Feb '03

I hope it wasn't my email about SCO that made you write this, I have filed a feature request and believe you and Craig and others have heard and know that some of us want you to support SCO. That is why I didn't send it to the list. It was in part your e-mail about SCO which prompted me to send it, but the note was not directed at any one developer in particular. Nor was the note intended to change the use of this discussion list. The main purpose of the note was to introduce Craig to the list in general, and to remind people that the list is great for reaching many people, but may not be tied into the official process for developer requests at Apple. I only sent you that email as an idea since you wanted to hear about what developers are interrested in doing with HCI. Please keep sending them to the list, we are interested in hearing about them. If you really want it and need it put in the official request through Craig as well. In fact I would suggest using the list for each request, as you may get others filing official requests with Craig. The more requests for a feature or API, the higher it will get prioritized on our todo list. No correction to the current behavior on the mailing list was intended. -larson _______________________________________________ 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: How to handle requests for public Bluetooth APIs
by Ragnar Sundblad 07 Feb '03

07 Feb '03

--On den 6 februari 2003 13:35 -0800 Michael Larson <larson(a)apple.com> wrote: There has been some discussion on the list recently about needing APIs which are not currently supported. I want to take the opportunity to clarify a couple of things: ... Michael, I hope it wasn't my email about SCO that made you write this, I have filed a feature request and believe you and Craig and others have heard and know that some of us want you to support SCO. That is why I didn't send it to the list. I only sent you that email as an idea since you wanted to hear about what developers are interrested in doing with HCI. All the best, /ragge _______________________________________________ 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

RFCOMMServerSample
by Hussain Bandukwala 06 Feb '03

06 Feb '03

Attn: Mr. Marco Pontil Hi All, I have been having some problems while running the RFCOMMServerSample along with the RFCOMMClientSample from /Developer/Examples/Bluetooth on Jaguar. Occassionally, when I start the server, messages similar to the following show up: '2003-02-06 11:47:49.216 RFCOMMServerSample[443] *** -[ChatBluetoothServerInterface newRFCOMMChannelOpened:]: selector not recognized' Once the server starts up and waits for connection, the client sees the server but is unable to connect. The following message shows up on the server side: '2003-02-06 11:44:56.553 RFCOMMServerSample[443] *** -[ChatBluetoothServerInterface newRFCOMMChannelOpened:]: selector not recognized 2003-02-06 11:44:56.554 RFCOMMServerSample[443] Exception raised during posting of notification. *Ignored. *exception: *** -[ChatBluetoothServerInterface newRFCOMMChannelOpened:]: selector not recognized' I was wondering if someone could point to me where I might be going wrong. I had another question about a particular code piece. The code is from RFCOMMServerSample - ChatBluetoothServerInterface.m [lines 180-182]: ************ '// We failed to register a listener. This is cathastrofic for a server // Releases the channel: *[rfcommChannel retain]; ' Is there any reason why the rfcommChannel is being retained here? Thanking You Kindly, Hussain ======================================================================== Hussain H. Bandukwala, C-1116, 1189 Beall Ave., The College of Wooster, Wooster, OH - 44691. (Home) -- (330)-287-3000 (x-7107) (Cell) -- (330)-412-1980 http://pages.wooster.edu/hbandukwala "It is not the strength, but the duration, of great sentiments that makes great men." -- Friedrich Nietzsche ======================================================================== _______________________________________________ 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: OBEXAgents are taking over
by Robert Grant 06 Feb '03

06 Feb '03

Well I think it is a little worse than that because vfork was failing due to the max number of processes being met. The only solution I could come up with was a reboot. Robert. On Thursday, February 6, 2003, at 05:04 PM, Bubba Giles wrote: Yes, in Bluetooth 1.0 we cause OBEXAgent zombie processes each time one is launched and quit. 1.1 takes care of this, but of course, that is not widely available. The good thing is, all they are is an extra (undeleted) entry in the process table, and should not do any harm other than making your process table printouts look bad. There seems to be some weird bug with the File Exchange program because I'm getting zombie OBEXAgents taking over my process table. My compiles were failing because of this, comments?: root 8468 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8469 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8466 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8467 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8459 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8461 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8624 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8627 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8622 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8623 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8626 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8625 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8628 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8631 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8629 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8630 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8657 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8658 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8667 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8661 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8665 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8660 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8659 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8666 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8664 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8663 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8711 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8715 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8718 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8712 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8716 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8713 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8717 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8714 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8719 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8720 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8760 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8761 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8763 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8759 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8765 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8762 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8766 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8764 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8767 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8758 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8770 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8775 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8771 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8773 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8769 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8774 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8768 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8776 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8772 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8777 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8825 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8824 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8829 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8834 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8827 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8831 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8830 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8832 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8826 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) root 8828 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 (OBEXAgent) _______________________________________________ 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. _______________________________________________ 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: OBEXAgents are taking over
by Bubba Giles 06 Feb '03

06 Feb '03

Yes, in Bluetooth 1.0 we cause OBEXAgent zombie processes each time one is launched and quit. 1.1 takes care of this, but of course, that is not widely available. The good thing is, all they are is an extra (undeleted) entry in the process table, and should not do any harm other than making your process table printouts look bad. > There seems to be some weird bug with the File Exchange program because > I'm getting zombie OBEXAgents taking over my process table. My compiles > were > failing because of this, comments?: > > root 8468 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8469 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8466 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8467 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8459 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8461 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8624 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8627 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8622 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8623 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8626 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8625 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8628 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8631 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8629 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8630 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8657 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8658 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8667 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8661 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8665 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8660 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8659 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8666 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8664 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8663 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8711 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8715 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8718 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8712 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8716 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8713 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8717 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8714 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8719 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8720 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8760 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8761 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8763 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8759 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8765 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8762 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8766 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8764 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8767 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8758 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8770 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8775 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8771 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8773 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8769 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8774 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8768 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8776 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8772 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8777 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8825 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8824 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8829 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8834 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8827 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8831 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8830 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8832 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8826 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > root 8828 0.0 0.0 0 0 con- Z 31Dec69 0:00.00 > (OBEXAgent) > _______________________________________________ > 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