RN52 doesn't disconnect properly on Win 10 Phone

[dasquiddi]

I've an issue with my Lumia 650 and hope somebody can help.

1. Paired Lumia with BlueSaab (Displays connection for calls and music)
2. On disconnect command from BlueSaab the calls connection remains
3. Reconnect with music playing won't work due the remaining connection.
 -> if i disconnect manualy on my Lumia the reconnect works like a charm.

[Karlis]

I believe it's because of the profiles Windows Phone negotiates for usage with BlueSaab. That is strange. BlueSaab is instructed to "present" itself as being capable of working with A2DP and SPP profiles only. "Calls" are part of HFP profile which BlueSaab is programmed to ignore (for now).

Here's what I think happens:

1. When pairing to BlueSaab, Windows Phone accepts BlueSaab's A2DP and SPP profile connections and for some reason adds "Calls" (HFP) as well.
2. When disconnecting, BlueSaab switches off A2DP and SPP profiles only, thus having HFP hanging in the air.
3. Next time BlueSaab tries to connect to Windows Phone, the latter reports, that there's already an "idle" profile connection in place, hence the connection fails.

Long story short - something happens during initial Windows Phone pairing sequence. I'm not quite familiar with that OS, but maybe there is a way to force it not to use BlueSaab for "calls"?

Hope this helps.

[Karlis]

Another thing that you should check is the SD and SK settings on your RN52 chip. They stand for "discovery mask" and "connection mask" values. Those should be set to "06". If it's not the case, change them to 06 accordingly and that should fix the issue.

Instructions on how to program RN52 can be found here

[Karlis]

Have you been able to resolve the issue?

[dasquiddi]

I've somehow messed it up ... it won't even boot up anymore. Lets hope i'll find it out.