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

Re: Characteristic notification on iPad
by Alexey Grechaninov 11 Mar '13

11 Mar '13

Thanks for confirmation! Please let know: 1. Did you submit this bug to Apple? 2. Did you checked it with 6.1.3 beta 2 ? (Unfortunately I have no additional hardware to test...) 10.03.2013, в 22:09, Arvydas Sidorenko <asido4(a)gmail.com> написал(а): > On Sun, Mar 10, 2013 at 8:37 AM, Alexey Grechaninov <alex(a)beetsblu.com> wrote: >> I'm working on notification of changed characteristic and noticed that CBCentralManager running on iPad 3 simply does not getting notifications from CBPeripheralManager running on iPhone 5. > > I had the same issue and I was told that notifications/indications do > not work until at least iOS 6.1 beta 4. > The solution for now could be a periodic polling. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Characteristic notification on iPad
by Arvydas Sidorenko 10 Mar '13

10 Mar '13

On Sun, Mar 10, 2013 at 8:37 AM, Alexey Grechaninov <alex(a)beetsblu.com> wrote: > I'm working on notification of changed characteristic and noticed that CBCentralManager running on iPad 3 simply does not getting notifications from CBPeripheralManager running on iPhone 5. I had the same issue and I was told that notifications/indications do not work until at least iOS 6.1 beta 4. The solution for now could be a periodic polling. _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Characteristic notification on iPad
by Alexey Grechaninov 10 Mar '13

10 Mar '13

Hello, I'm working on notification of changed characteristic and noticed that CBCentralManager running on iPad 3 simply does not getting notifications from CBPeripheralManager running on iPhone 5. Both updated to 6.1.2. Issue appears only in ONE direction - from iPhone to iPad. Moreover, I've checked this issue using demo app BLE Transfer from Apple. I has the same issue... Transfer iPad 3 -> iPhone 5 works pretty fine, but transfer iPhone 5 -> iPad 3 simple does nothing. Alexey _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Peripheral dealloced while connecting under ARC?
by Rick Mann 10 Mar '13

10 Mar '13

On Mar 9, 2013, at 01:29 , Andras Kovi <allprog(a)gmail.com> wrote: > Anyway, there are probably well founded reasons why the framework does not retain the peripheral object and we have to live with these decisions for now. If you feel like this is a great pain in the neck, then you can always submit a bug to Apple. It's those reasons I was hoping to understand. -- Rick _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Peripheral/Slave serving multiple Central/Masters
by Etan Kissling 09 Mar '13

09 Mar '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Peripheral/Slave serving multiple Central/Masters
by Chip Keyes 09 Mar '13

09 Mar '13

_______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Peripheral dealloced while connecting under ARC?
by Andras Kovi 09 Mar '13

09 Mar '13

Yes, but if you release your instance, then a new instance is created automatically. If you are connected to multiple peripherals, then this can cause significant overhead and lots of mem allocations. I'm not completely sure but I can imagine that this new instance is not going to have the same state as the old one had; however, this statement has to be checked but I don't have the means to do it now. Anyway, there are probably well founded reasons why the framework does not retain the peripheral object and we have to live with these decisions for now. If you feel like this is a great pain in the neck, then you can always submit a bug to Apple. Regards, Andras On 2013.03.09., at 10:12, Rick Mann <rmann(a)latencyzero.com> wrote: > > On Mar 9, 2013, at 00:18 , Andras Kovi <allprog(a)gmail.com> wrote: > >> The problem with requiring the system to retain the peripheral is that once you receive the callback you wouldn't be able to determine which peripheral's interaction initiated the callback. You could say the UUID would be enough. But then having the peripheral stored alongside is not a huge addition. It's annoying and not well documented but can be circumvented easily with some tricks. > > Not sure I understand what you're saying here; the peripheral is passed to the callback. > > -- > Rick > > > _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Peripheral dealloced while connecting under ARC?
by Rick Mann 09 Mar '13

09 Mar '13

On Mar 9, 2013, at 00:18 , Andras Kovi <allprog(a)gmail.com> wrote: > The problem with requiring the system to retain the peripheral is that once you receive the callback you wouldn't be able to determine which peripheral's interaction initiated the callback. You could say the UUID would be enough. But then having the peripheral stored alongside is not a huge addition. It's annoying and not well documented but can be circumvented easily with some tricks. Not sure I understand what you're saying here; the peripheral is passed to the callback. -- Rick _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Peripheral dealloced while connecting under ARC?
by Andras Kovi 09 Mar '13

09 Mar '13

I've also had my rant on this a while ago. For me it was a bigger problem that CBPeripheral does not indicate the connecting and disconnecting states. However, I get a warning/error if I release the peripheral in any of these states. I had to come up with a custom solution, a pretty control layer on top of CB. Maybe once I have some time I'll share it on GitHub. The problem with requiring the system to retain the peripheral is that once you receive the callback you wouldn't be able to determine which peripheral's interaction initiated the callback. You could say the UUID would be enough. But then having the peripheral stored alongside is not a huge addition. It's annoying and not well documented but can be circumvented easily with some tricks. Have a nice day, Andras On 2013.03.09., at 3:50, Rick Mann <rmann(a)latencyzero.com> wrote: > > On Mar 8, 2013, at 18:35 , Roland King <rols(a)rols.org> wrote: > >> You have to keep a reference to the peripheral if you want to connect to it. > > Thanks, Roland. Any idea why? It seems like, in passing the peripheral to the connect call, the system should keep a reference until the callback (did connect or did fail) returns. Basically, so long as I've started an operation on an object in Core Bluetooth, it should be retained until the callbacks complete. > > Otherwise it adds a burden on me to keep track of it, and let go of it if I determine it's not the one I want. > > > -- > Rick > > > > > _______________________________________________ > Do not post admin requests to the list. They will be ignored. > Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) > Help/Unsubscribe/Update your Subscription: > https://lists.apple.com/mailman/options/bluetooth-dev/allprog%40gmail.com > > This email sent to allprog(a)gmail.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Peripheral dealloced while connecting under ARC?
by Rick Mann 09 Mar '13

09 Mar '13

On Mar 8, 2013, at 18:35 , Roland King <rols(a)rols.org> wrote: > You have to keep a reference to the peripheral if you want to connect to it. Thanks, Roland. Any idea why? It seems like, in passing the peripheral to the connect call, the system should keep a reference until the callback (did connect or did fail) returns. Basically, so long as I've started an operation on an object in Core Bluetooth, it should be retained until the callbacks complete. Otherwise it adds a burden on me to keep track of it, and let go of it if I determine it's not the one I want. -- Rick _______________________________________________ Do not post admin requests to the list. They will be ignored. Bluetooth-dev mailing list (Bluetooth-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/bluetooth-dev/site_archiver%40lists… This email sent to site_archiver(a)lists.apple.com

1 0