2009-08-31, 08:07
Asure Wrote:I had a similar problem, simply use the init patch to use correct version of bluetoothd on bootup. Also, unplug the BT stick, and reboot the whole box after fixing the init.. When the box is still booting plug the stick back in. I think some sticks don't like warm boots. Mine keeps blinking even if i stop bluetoothd for example
(Side not: Blueman no longer works, but the ps3 remote is correctly paired after boot/timeouts/etc.)
i figured out why it timed out so fast - the /etc/bluetooth/input.conf file specified 30 for the idle timeout. the comments in the file leave you to believe the unit is in minutes, but clearly its in seconds.
i got that crazy situation where blueman will no longer admin the hci0 anymore after reboot also. not sure why. guessing its because im starting the wrong version of bluez at startup.
thanks for the tip. i will look into this tonight. what init patch are you refering to though?
are you suggesting i patch it manually?
i assume you are refering to /etc/init.d/bluetooth ?
cheers.