MIB - Mandriva International Backports

since i updated from kde 4.10.5 to 4.11.1
then
at pc start up the dongle is no more atcivated

bluedevil says it is activated !

i found a workaround

i put in /etc/rc.local file the statements

hciconfig hci0 down
hciconfig hci0 up

what a progress !
same workaround with my current distrib installed on my pc the 2010.3 !

Thanx for reporting! Today I'll update bluedevil to latest version to see if it helps.

Can you please try latest versions of libbludevil and bluedevil? See comment #2 for ABF build lists with containers:

http://bugs.rosalinux.ru/show_bug.cgi?id=2712#c1

P.S. Container is just a mini repository.

after updating bluedevil

bt dongle is not activated at startup : no progress

i activate the bt dongle with hciconfig
then
send file from phone , from pc : all ok
with dolphin explore phone , copy ferom phone , copy from pc , delete files : all ok

if i ask to bluedevil to unactivate the bluetooth then bluedevil crashes and disappears (it's new)

the sole way to have a functional bluedevil again is to restart pc

it not normal since i discovered pb with bluetooth with my 2010 switching to kernel >= 3.1.6 there is always pb

every distrib has this pb : mageia , opensuse , rosa , om , archlinux , mint . i tested so many !

i fear the days when they will switch to bluez 5 according to support new bt 4 .

opensuse 13.1 will come with bluez 5
i test it till this day bt does not work . they promess it will work with 13.1 rc1 ; wait and see


till now i stay with my 2010.3

promeneur wrote:the sole way to have a functional bluedevil again is to restart pc
it not normal since i discovered pb with bluetooth with my 2010 switching to kernel >= 3.1.6 there is always pb
every distrib has this pb : mageia , opensuse , rosa , om , archlinux , mint . i tested so many !

Sounds bad. I asked other ppl if they have bluedevil working fine and looks like it's a hardware-specific issue, it affects only some devices.

the ref of my bt dongle :

Kensington Bluetooth usb micro adapter

Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

today a bluetooth dongle has a lower price.

i can change for a new one but what mark and model , what chipset to be sure it works with linux ?

it's time to change it for a bt 4 compatible one .

promeneur wrote:today a bluetooth dongle has a lower price. i can change for a new one but what mark and model , what chipset to be sure it works with linux ?

This one is known to work with no issues:

[20:59:23] <aburmashev> Bus 004 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
[20:59:25] <aburmashev> https://uk.hama.com/00104890/hama-nano- ... edr-class2

thanks but i have a cambridge silicon radio chipset !

in ubuntu help they say since a version of ubuntu (kernel ?) cambridge silicon radio are known to have pb

and

if i change i prefer a bt 4 compatible because my new smartphone uses bt 4

this autumn opensuse will be compatible with bt 4 with bluez 5 .

it would be a good thing rosa switches to bluez 5 ; but it is a big pb .
the api of bluez 4 and 5 are not compatible and many apps use bluez 4

from opensuse dev "bluedevil dev works to supply a new version compatible to bluez 5 in time for opensuse 13.1" . wait and see .

I would be interested to know if the product # after ID (0a12:0001) is the same in your output of lsusb:
or if Cambridge Silicon only makes one bluetooth chip?

promeneur wrote:it would be a good thing rosa switches to bluez 5 ; but it is a big pb .
the api of bluez 4 and 5 are not compatible and many apps use bluez 4

Well, Rosa will switch to Bluez5 one day for sure but not very soon, maybe in late 2013 or early 2014. It requires a lot of work (to make sure all applications build and work with new Bluez with no regressions). It's hard to say for sure now when it will happen.

@rolf

Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

i assume in my case something is wrong with kernel bt part or usb_hci .

perhaps when executing hciconfig hci0 down then up this reset something about usb_hci then the dongle is activated

with my 2010.3 i don't use hciconfig but "bluetoothd stop" to activate the dongle

Thanks for the info. Bluetooth has always been hit or miss for me. I only use it once in a while with my ancient Treo 755p.