LE8 alpha - screensaver + bluetooth "enable standby" issue

**bite_your_idols** · August 31, 2016 at 10:08 AM

Hi!
In the couple last alpha releases I noticed some issues with screensaver activation... Finally I discovered that if I plug in my USB bluetooth device into my RPi2, the system does not enter in screensaver state, it is active everytime. I see the dongle's red led blinking everytime eventhough I disable bluetooth service from libreelec config tool...

If I unplug the usb dongle, then the screensaver works great.

**bite_your_idols** · September 5, 2016 at 11:02 PM

I have found how the issue is happening:
- I pair a bluetooth gamepad, Sony Dualshock 3
- If paired gamepad is on, everything is working ok and screensaver activates after time I set
- If paired gampad is off (because I didn't use it that day or after auto deactivation with LibreELEC settings) bluetooth dongle is blinking (I supouse looking for paired device) and screensaver does not work. Also if I go to settings> Interface> screensaver> preview it does not work.

Please, can anybody check if it is happening only to me?

**bite_your_idols** · September 7, 2016 at 10:30 PM

I don't know if this is something that is only happening to me, but I think it is important...

I have dig into the problem and I discovered something else: The problem is the "Enable Standby" setting for paired device in LibreELEC config.

- After pairing a device (my DS3) if I activate "Enable Standby" when screensaver starts (and the gamepad is suppoused to deactivate) the system blocks the screensaver and never starts, also the gamepad never deactivates.
- If I reboot, even I don't switch on the gamepad, the issue happens.
- If "Enable Standby" feature is off, the screensaver works ok, but the gamepad still on, comsuming battery.
- If "Enable Standby" feature is off, the screensaver works ok, also when the gamepad has been not connected.

I dont know if I explain myself clear, but the issue is with that feature...

jaykass · September 25, 2016 at 1:05 AM

I am having a similar issue with regards to bluetooth and the screensaver. RPi3. Using 8bitdo SNES30 BT controller on escalade's community build. However, the issue does not appear to be due to his packages.

At any rate. I get the following error in my log file when the screensaver activates if I have bluetooth enabled in LibreELEC (whether or not anything is connected). If I disable bluetooth then the screensaver activates as it should. That is my current work around.

Hopefully this will aid in tracking down the root cause.

Log:

Code

16:52:07 58523.289062 T:1651213232   ERROR: ## LibreELEC Addon ## bluetooth::dbus_error_handler ## ERROR: (Method "Disconnect" with signature "" on interface "org.bluez.Device1" doesn't exist
                                            )
16:52:07 58523.289062 T:1651213232   ERROR: None
16:52:07 58523.296875 T:1960408080 WARNING: SplitParams("Bluetooth error", "Method "Disconnect" with signature "" on interface "org", 5000, "/usr/share/kodi/addons/service.libreelec.settings/resources/skins/Default/media/icons/bt.png") - end of string while searching for ) or "
16:52:20 58536.210938 T:1822421936  NOTICE: Register - new joystick device registered on addon->peripheral.joystick/1: 8Bitdo SNES30 GamePad Joystick
16:52:27 58543.722656 T:1651213232   ERROR: ## LibreELEC Addon ## bluetooth::dbus_error_handler ## ERROR: (Method "Disconnect" with signature "" on interface "org.bluez.Device1" doesn't exist
                                            )
16:52:27 58543.722656 T:1651213232   ERROR: None
16:52:27 58543.730469 T:1960408080 WARNING: SplitParams("Bluetooth error", "Method "Disconnect" with signature "" on interface "org", 5000, "/usr/share/kodi/addons/service.libreelec.settings/resources/skins/Default/media/icons/bt.png") - end of string while searching for ) or "
16:52:35 58551.117188 T:1814033328   ERROR: AddOnLog: Joystick Support: ScanEvents: failed to read joystick "8Bitdo SNES30 GamePad Joystick" on /dev/input/js0
16:52:35 58551.976562 T:1822421936   ERROR: Previous line repeats 61 times.
16:52:35 58551.976562 T:1822421936  NOTICE: UnregisterRemovedDevices - device removed from joystick/peripheral.joystick/1: 8Bitdo SNES30 GamePad Joystick (0000:0000)
16:52:37 58553.652344 T:1651213232   ERROR: ## LibreELEC Addon ## bluetooth::dbus_error_handler ## ERROR: (Method "Disconnect" with signature "" on interface "org.bluez.Device1" doesn't exist
                                            )
16:52:37 58553.652344 T:1651213232   ERROR: None
16:52:37 58553.664062 T:1960408080 WARNING: SplitParams("Bluetooth error", "Method "Disconnect" with signature "" on interface "org", 5000, "/usr/share/kodi/addons/service.libreelec.settings/resources/skins/Default/media/icons/bt.png") - end of string while searching for ) or "
16:52:41 58557.191406 T:1651213232   ERROR: ## LibreELEC Addon ## bluetooth::dbus_error_handler ## ERROR: (Method "Disconnect" with signature "" on interface "org.bluez.Device1" doesn't exist
                                            )
16:52:41 58557.199219 T:1651213232   ERROR: None
16:52:41 58557.203125 T:1960408080 WARNING: SplitParams("Bluetooth error", "Method "Disconnect" with signature "" on interface "org", 5000, "/usr/share/kodi/addons/service.libreelec.settings/resources/skins/Default/media/icons/bt.png") - end of string while searching for ) or "
16:53:08 58584.839844 T:1583346608 WARNING: CSkinInfo: failed to load skin settings
16:53:08 58585.000000 T:1960408080   ERROR: Control 1000 in window 13000 has been asked to focus, but it can't
16:53:16 58592.386719 T:1651213232   ERROR: ## LibreELEC Addon ## bluetooth::adapter_info ## ERROR: (DBusException('The name :1.16 was not provided by any .service files',))
16:53:16 58592.386719 T:1651213232   ERROR: Traceback (most recent call last):
                                              File "/home/trondah/LibreELEC.tv/build.LibreELEC-RPi2.arm-8.0-devel/LibreELEC-settings-17315f4/.install_pkg/usr/share/kodi/addons/service.libreelec.settings/resources/lib/modules/bluetooth.py", line 150, in adapter_info
                                              File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 70, in __call__
                                              File "/usr/lib/python2.7/site-packages/dbus/proxies.py", line 145, in __call__
                                              File "/usr/lib/python2.7/site-packages/dbus/connection.py", line 651, in call_blocking
                                            DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.16 was not provided by any .service files
16:53:16 58592.386719 T:1651213232   ERROR: ## LibreELEC Addon ## bluetooth::menu_connections ## ERROR: (TypeError("int() argument must be a string or a number, not 'NoneType'",))
16:53:16 58592.386719 T:1651213232   ERROR: Traceback (most recent call last):
                                              File "/home/trondah/LibreELEC.tv/build.LibreELEC-RPi2.arm-8.0-devel/LibreELEC-settings-17315f4/.install_pkg/usr/share/kodi/addons/service.libreelec.settings/resources/lib/modules/bluetooth.py", line 425, in menu_connections
                                            TypeError: int() argument must be a string or a number, not 'NoneType'

Display More

jaykass · September 30, 2016 at 6:08 AM

OK, so I was able to resolve my issue. I had some devices listed to standby in
/storage/.kodi/userdata/addon_data/service.libreelec.settings/oe_settings.xml due to copying over my .kodi/userdata file from an earlier installation. As shown in the code below, I removed the devices and no longer have any setup for standby. After making this change, I was able to have bluetooth enabled and have my screensaver working. I was able to activate the screensaver with the controller powered on (leaving the controller connected) or off. I was even able to enable standby from the menu and have the screensaver activate and disconnect the controller at activation. Just for additional testing, I then disabled standby again through the menus and everything continued to function properly.

Code

<bluetooth>
<standby></standby>
</bluetooth>

So...the solution to this issue...appears to be one of validation before disconnecting. I see two options and a combination of the two might be the best way to handle.
1) Clear bluetooth standby settings on a new installation...since the data is in the kodi userdata folder, it would not be unexpected for a lot of people to copy over old settings to a new installation. I do not know how this could be handled logically, but maybe something as simple as having a menu option to clear bluetooth settings.
2) Enable validation in service.libreelec.settings/src/resources/lib/modules/bluetooth.py standby_devices. Currently, the function checks that a bluetooth adapter is present and also checks for devices to be listed in the standby settings but doesn't check to see that those devices are actually connected. So it attempts to disconnect something that isn't even connected and thus throws errors.

**bite_your_idols** · September 30, 2016 at 8:18 AM

Quote from jaykass
OK, so I was able to resolve my issue. I had some devices listed to standby in
/storage/.kodi/userdata/addon_data/service.libreelec.settings/oe_settings.xml due to copying over my .kodi/userdata file from an earlier installation. As shown in the code below, I removed the devices and no longer have any setup for standby. After making this change, I was able to have bluetooth enabled and have my screensaver working. I was able to activate the screensaver with the controller powered on (leaving the controller connected) or off. I was even able to enable standby from the menu and have the screensaver activate and disconnect the controller at activation. Just for additional testing, I then disabled standby again through the menus and everything continued to function properly.
Code
<bluetooth>
<standby></standby>
</bluetooth>
So...the solution to this issue...appears to be one of validation before disconnecting. I see two options and a combination of the two might be the best way to handle.
1) Clear bluetooth standby settings on a new installation...since the data is in the kodi userdata folder, it would not be unexpected for a lot of people to copy over old settings to a new installation. I do not know how this could be handled logically, but maybe something as simple as having a menu option to clear bluetooth settings.
2) Enable validation in service.libreelec.settings/src/resources/lib/modules/bluetooth.py standby_devices. Currently, the function checks that a bluetooth adapter is present and also checks for devices to be listed in the standby settings but doesn't check to see that those devices are actually connected. So it attempts to disconnect something that isn't even connected and thus throws errors.

Now, in LE 8 alpha 6 is even worse... If I have connected to bluetooth my dualshock, no matter if enable standby is activated or not, the screensaver does not run... I need to manually swith of the device from LE settings>Bluetooth.
I tried what you said and it does not change anything...

Are you using a Pi2 with an USB BT dongle? I wonder if this happend also with RPi3 and built in BT...

jaykass · September 30, 2016 at 3:04 PM

I am using a pi3 with built-in BT

jaykass · October 1, 2016 at 12:39 AM

What's in your oe_settings.xml?

**bite_your_idols** · October 1, 2016 at 6:06 AM

Quote from jaykass

I am using a pi3 with built-in BT

I thought if I get a Pi3 the problem will solve but I see it will not...

Quote from jaykass

What's in your oe_settings.xml?

XML

<?xml version="1.0" ?>
<libreelec>
	<addon_config/>
	<settings>
		<system>
			<wizard_completed>True</wizard_completed>
			<KeyboardLayout1>es</KeyboardLayout1>
			<Channel>LibreELEC-8.0</Channel>
			<ShowCustomChannels>0</ShowCustomChannels>
		</system>
		<connman>
			<wizard_completed>True</wizard_completed>
		</connman>
		<services>
			<wizard_completed>True</wizard_completed>
		</services>
		<about>
			<wizard_completed>True</wizard_completed>
		</about>
		<libreelec>
			<wizard_completed>True</wizard_completed>
		</libreelec>
		<bluetooth>
			<standby></standby>
		</bluetooth>
	</settings>
</libreelec>

Display More

I don't know why no one cares about thisi ssue...

jaykass · October 1, 2016 at 7:39 PM

what is the error in your kodi.log file when the screensaver activates or when you try to preview the screensaver?

**bite_your_idols** · October 2, 2016 at 1:42 PM

Quote from jaykass

what is the error in your kodi.log file when the screensaver activates or when you try to preview the screensaver?

Code

14:40:20 521.224670 T:1801450400   DEBUG: PushCecKeypress - received key  b duration 0 (rep:0 size:0)
14:40:20 521.225037 T:1801450400   DEBUG: PushCecKeypress - added key  b
14:40:20 521.239685 T:1961934848   DEBUG: OnKey: 11 (0x0b, obc244) pressed, action is Select
14:40:20 521.242432 T:1961927584   DEBUG: CAnnouncementManager - Announcement: OnScreensaverActivated from xbmc
14:40:20 521.243103 T:1961927584   DEBUG: GOT ANNOUNCEMENT, type: 4, from xbmc, message OnScreensaverActivated
14:40:20 521.246155 T:1961934848   DEBUG: ------ Window Init () ------
14:40:20 521.251770 T:1961927584   DEBUG: CAnnouncementManager - Announcement: OnScreensaverDeactivated from xbmc
14:40:20 521.252258 T:1961927584   DEBUG: GOT ANNOUNCEMENT, type: 4, from xbmc, message OnScreensaverDeactivated
14:40:20 521.280518 T:1961934848   DEBUG: ------ Window Deinit () ------
14:40:20 521.300110 T:1801450400   DEBUG: PushCecKeypress - received key  b duration 76 (rep:0 size:0)
14:40:20 521.300415 T:1801450400   DEBUG: PushCecKeypress - ignored key  b

Display More

jaykass · October 2, 2016 at 8:06 PM

I don't see any errors there. Does an error message pop up on screen? Or does it just do nothing at all?

**bite_your_idols** · October 3, 2016 at 6:47 AM

It just does nothing.

if "enable standby" is activated, then it switches off the dualshock fades a bit and then screen activates again. Then if I try to preview the screensaver again, it also does nothing.

**bite_your_idols** · October 9, 2016 at 8:11 PM

I guess it is something related with DS3 motion sensors... Screensaver activates but then the DS3 is sending some kind of motion/sixais data and kodi reactivates so screensaver disables...

I haven't another bluetooth gamepad to test this theory...

I imagine in OE/LE 7 this does not happen because its kodi has no gamepad support.

Dambedei · November 2, 2016 at 10:57 AM

Not sure if this is the same issue but:
When "Enable Standby" is active in Libreelec/bluetooth settings then the screensaver behaves wrong: screensaver turns on (which disables the TV in my case through CEC-settings) and then immediately screensaver turns off (which turns the TV on again).
This only happens if "Enable Standby" is ON, else screensaver works fine but obviously the remote control never turns off.

TL;DR:
screensaver doesnt work properly with standby enabled in libreelec/bluetooth settings.

Tested with LE v7.90.008 ALPHA on odroid-c2

**bite_your_idols** · November 5, 2016 at 5:00 PM

Quote from Dambedei

Not sure if this is the same issue but:
When "Enable Standby" is active in Libreelec/bluetooth settings then the screensaver behaves wrong: screensaver turns on (which disables the TV in my case through CEC-settings) and then immediately screensaver turns off (which turns the TV on again).
This only happens if "Enable Standby" is ON, else screensaver works fine but obviously the remote control never turns off.

TL;DR:
screensaver doesnt work properly with standby enabled in libreelec/bluetooth settings.

Tested with LE v7.90.008 ALPHA on odroid-c2

It is exactly the same issue. Are you using a PS3 dualshock or another bluetooth gamepad?

Dambedei · November 5, 2016 at 5:10 PM

Hi
I'm using an amazon fire TV remote

zuzzurro · November 12, 2016 at 11:49 PM

Same issue over here. Raspberry Pi 3 with ps3 remote. This is very unfortunate and I hope some dev can fix it before the final release.