2012-01-22, 19:07
1. First of all, a question for kitlaan - you say: "The PPA has been updated for oneiric, no need to hold the package any more; sorry about that".
I'm not sure what you mean by that? Do you mean that there are unncessary steps in my posting from "2011-12-30, 16:08", or what?
2. I've been looking at the remote control power consumption. With mine, on standby the remote control draws 0.12 mA.
Then if you press a button on the remote control it establishes the bluetooth connection and the consumption goes up to about 14 mA.
However the timeout doesn't seem to work.
The power consumption goes back to standby when you unplug the Bluetooth dongle, power down the mythbox or issue 'sudo service bluetooth stop'.
But if you press a button and just leave it, the consumption stays at 14 mA.
I set:
IdleTimeout=30
(and restarted the bluetooth service) but it doesn't time out after 30 seconds - in fact 40 minutes on it's still drawing 14 mA.
I tried running it in debug mode by issuing the following:
sudo service bluetooth stop
sudo bluetoothd -nd
The debug messages show when a key is pressed and released, but there are no timeout messages, etc.
Does anyone have any suggestions about this?
Thanks very much - Vaughan
I'm not sure what you mean by that? Do you mean that there are unncessary steps in my posting from "2011-12-30, 16:08", or what?
2. I've been looking at the remote control power consumption. With mine, on standby the remote control draws 0.12 mA.
Then if you press a button on the remote control it establishes the bluetooth connection and the consumption goes up to about 14 mA.
However the timeout doesn't seem to work.
The power consumption goes back to standby when you unplug the Bluetooth dongle, power down the mythbox or issue 'sudo service bluetooth stop'.
But if you press a button and just leave it, the consumption stays at 14 mA.
I set:
IdleTimeout=30
(and restarted the bluetooth service) but it doesn't time out after 30 seconds - in fact 40 minutes on it's still drawing 14 mA.
I tried running it in debug mode by issuing the following:
sudo service bluetooth stop
sudo bluetoothd -nd
The debug messages show when a key is pressed and released, but there are no timeout messages, etc.
Does anyone have any suggestions about this?
Thanks very much - Vaughan