Re: How to force a protocol on a specific BT device?

In data lunedì 18 giugno 2018 16:48:21 CEST, Anton Aylward ha scritto:
> On 18/06/18 10:37 AM, stakanov wrote:
> > BT fails with me since years to pair correctly with BT audio devices when
> > they have also a phone hands free function.
> 
> Well, no, and   yes.
> 
> My problems with BT & binding to my devices happens at conferences and the
> like when there are so many other BT devices around, all manner of devices
> that my co-attendees are using.  You'd think that my decides know each
> others 'names'? Well yes, but the amount of RF traffic on their bands seems
> to force disconnects and confusion.  Looking around at faces and people
> shaking their pones and stuff, I suspect I'm not alone at these times.
With my situation: 1 BT device, e.g. JBL GO BT box. 
Automatic pairing: TW no problem
Leap: problematic, fails many times. But although it claims "failed" then it 
results connected and can be given trust. 
TW: you can set HFP or A2DP. In 50% of the time the setting is accepted. In 
the other 50% it behaves like Leap: failure to accept the A2DP. 
Leap: you can select HFP or A2DP. But settings have no effect, once done "ok" 
the settings are held on A2DP (on the window) but sound is HFP. When one 
closes the settings, reopening it shows the association is again on HFP. 

So this seems to be a Leap problem (maybe KDE related because maybe the 
version has a fix upstream?) or just a bug in settings for which the setting 
is not accepted / held. 
So that is the point where I would like to put the iron in and try to force 
the profile. Helas I do not know where that is to be done. 




_________________________________________________________________
________________________________________________________
Ihre E-Mail-Postfächer sicher & zentral an einem Ort. Jetzt wechseln und alte E-Mail-Adresse mitnehmen! https://www.eclipso.de


-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]