[Bug 268877] Re: bluetooth service does not restart after a suspend to ram

[Martin G Miller]

Chow Loong Jin wrote:
"1. Set HID2HCI_ENABLED=0 in /etc/default/bluetooth, and then manually
run
PM_FUNCTIONS=/usr/lib/pm-utils/pm-functions /usr/lib/pm-utils/sleep.d/48hid2hci

This results in no error message."

This would not give an error message as it has just switched the device
from HID to HCI mode.

Then, if you do:
"2. Set HID2HCI_ENABLED=1 in /etc/default/bluetooth, and the manually run
PM_FUNCTIONS=/usr/lib/pm-utils/pm-functions /usr/lib/pm-utils/sleep.d/48hid2hci

This results in the error message "No devices in HID mode found"."

This confirms that the HCI mode is still enabled from the previous
command, which should not be the case.


Is there any way to determine the status of the device before and after issuing the commands?  That way you could boot with HID2HCI_ENABLED=0 set and test to see that it is in fact in HID mode.  Then run the command:
"PM_FUNCTIONS=/usr/lib/pm-utils/pm-functions /usr/lib/pm-utils/sleep.d/48hid2hci"
and again test to see what mode the device is in.  I believe it is changing to HCI even though it shouldn't be.

-- 
bluetooth service does not restart after a suspend to ram
https://bugs.launchpad.net/bugs/268877
You received this bug notification because you are a member of
Bluetooth, which is subscribed to bluez in ubuntu.