[LINUX] Sony PlayStation 3 Blu-ray Disc Remote (PS3 BD) + LIRC + XBMC = SUCCESS

[LINUX] Sony PlayStation 3 Blu-ray Disc Remote (PS3 BD) + LIRC + XBMC = SUCCESS - Printable Version

+- XBMC Community Forum (http://forum.xbmc.org)
+-- Forum: Help and Support (/forumdisplay.php?fid=33)
+--- Forum: XBMC General Help and Support (/forumdisplay.php?fid=111)
+---- Forum: Linux and Live support (/forumdisplay.php?fid=52)
+---- Thread: [LINUX] Sony PlayStation 3 Blu-ray Disc Remote (PS3 BD) + LIRC + XBMC = SUCCESS (/showthread.php?tid=50717)

Pages: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73

- repvik - 2011-06-23 19:27

Would it be possible to run the bt-disconnect script when the screen dims in XBMC? That way I could avoid the remote sleeping during a movie, but the battery wouldn't be eaten in a single week either.

- kitlaan - 2011-06-23 22:29

CSB! Wrote:I'm going through a set of batteries every week... hopefully I won't have to read through 550 posts to figure it out...

What IdleTimeout value (either in the General section, or under your custom-specific device address) are you using? I use 30 seconds; haven't had to change batteries since putting out the new package...
Hmm. I see you're even using 4.69, which has been known stable-and-working for ages. There has been reports of shutting down or suspending the computer before the remote has disconnected causing power drain... Which is why the bt-disconnect script is useful.

repvik Wrote:Would it be possible to run the bt-disconnect script when the screen dims in XBMC? That way I could avoid the remote sleeping during a movie, but the battery wouldn't be eaten in a single week either.

I don't know if XBMC has a plugin trigger on dimming... I don't recall seeing one.

- CSB! - 2011-06-23 22:59

kitlaan Wrote:What IdleTimeout value (either in the General section, or under your custom-specific device address) are you using? I use 30 seconds; haven't had to change batteries since putting out the new package...
Hmm. I see you're even using 4.69, which has been known stable-and-working for ages. There has been reports of shutting down or suspending the computer before the remote has disconnected causing power drain... Which is why the bt-disconnect script is useful.

I have

Code:

# Set a custom idle timeout (in minutes) for this device

IdleTimeout=1

For my device. I copied that line and put it under general, hopefully that helps somehow... I'll know in a week.:confused2:

- repvik - 2011-06-27 22:18

I'm now getting these in my log once in a while:

Code:

Jun 27 21:57:22 Sirius bluetoothd[3924]: Input: disconnect /org/bluez/3922/hci0/dev_00_24_33_97_2C_46

Jun 27 21:57:24 Sirius bluetoothd[3924]: Hangup or error on ps3remote socket

Jun 27 22:04:27 Sirius bluetoothd[3924]: Input: disconnect /org/bluez/3922/hci0/dev_00_24_33_97_2C_46

Jun 27 22:04:29 Sirius bluetoothd[3924]: Hangup or error on ps3remote socket

Anyone know what causes this? I'm using kitlaans PPA on Natty

- kitlaan - 2011-06-29 06:13

repvik Wrote:I'm now getting these in my log once in a while:

Code:

Jun 27 21:57:22 Sirius bluetoothd[3924]: Input: disconnect /org/bluez/3922/hci0/dev_00_24_33_97_2C_46 Jun 27 21:57:24 Sirius bluetoothd[3924]: Hangup or error on ps3remote socket Jun 27 22:04:27 Sirius bluetoothd[3924]: Input: disconnect /org/bluez/3922/hci0/dev_00_24_33_97_2C_46 Jun 27 22:04:29 Sirius bluetoothd[3924]: Hangup or error on ps3remote socket
Anyone know what causes this? I'm using kitlaans PPA on Natty

That's the remote disconnecting via timeout. I guess I don't quite have the timeout cleanup done right (and the extra debugging printout)... (I get the same, and have been ignoring it until I have some time to debug. Functionally there's no problems; just the error message.)

- repvik - 2011-06-29 10:14

Ok, I'll just ignore it then Smile

- CSB! - 2011-06-30 21:59

CSB! Wrote:I have

Code:

# Set a custom idle timeout (in minutes) for this device IdleTimeout=1

For my device. I copied that line and put it under general, hopefully that helps somehow... I'll know in a week.:confused2:

Yeah, the new batteries are already dead.

http://pastebin.com/6smbhpVb

Is my config. I'm totally miffed.

- kitlaan - 2011-07-01 05:50

CSB! Wrote:Yeah, the new batteries are already dead.

http://pastebin.com/6smbhpVb

Is my config. I'm totally miffed.

If you run the bluetooth daemon in debug mode (sudo service bluetooth stop; sudo bluetoothd -nd) and use it a bit (let it try to timeout, etc) and pastebin the debug output, I'll try to debug.

- CSB! - 2011-07-01 07:05

kitlaan Wrote:If you run the bluetooth daemon in debug mode (sudo service bluetooth stop; sudo bluetoothd -nd) and use it a bit (let it try to timeout, etc) and pastebin the debug output, I'll try to debug.

http://pastebin.com/a3UcgFPE

After it wouldn't reconnect, I pulled the batteries out and re-inserted, and hit a button until it reconnected.

- kitlaan - 2011-07-02 19:50

CSB! Wrote:http://pastebin.com/a3UcgFPE

After it wouldn't reconnect, I pulled the batteries out and re-inserted, and hit a button until it reconnected.

Huh. Looks like the disconnection logic is having problems. If you want to give it a chance, try upgrading bluez (4.91 for maverick should be in my PPA). I'll still take a poke at the 4.69 code to see what's going on.