Still no idea on what could be causing this.
Jönke, could you elaborate further on what exactly you've done to make your remote work?
Posts by lusephur
-
-
Would you have any idea on what else should be supplied? (logs, btmon etc - although as pointed out the remote connects, but no input is accepted by kodi)
debug log
https://paste.libreelec.tv/choice-orca.log
Noticed this
Bash
Display MoreNov 28 14:40:47.120799 LibreELEC kernel: hid-generic 0005:5A44:5A44.0004: input,hidraw3: BLUETOOTH HID v0.00 Keyboard [Remote-V12] on 7c:5c:f8:f2:37:4d Nov 28 14:40:47.123996 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'one': Invalid argument Nov 28 14:40:47.124030 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'two': Invalid argument Nov 28 14:40:47.124039 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'three': Invalid argument Nov 28 14:40:47.124046 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'four': Invalid argument Nov 28 14:40:47.124054 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'five': Invalid argument Nov 28 14:40:47.124061 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'six': Invalid argument Nov 28 14:40:47.124068 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'seven': Invalid argument Nov 28 14:40:47.124076 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'eight': Invalid argument Nov 28 14:40:47.124083 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'nine': Invalid argument Nov 28 14:40:47.124090 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'zero': Invalid argument Nov 28 14:40:47.124141 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'repeat': Invalid argument Nov 28 14:40:47.124149 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'volume_mute': Invalid argument Nov 28 14:40:47.124157 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'period': Invalid argument Nov 28 14:40:47.124168 LibreELEC (udev-worker)[1457]: event10: Failed to parse key identifier 'leftquote': Invalid argument Nov 28 14:40:47.129394 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'one': Invalid argument Nov 28 14:40:47.129417 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'two': Invalid argument Nov 28 14:40:47.129426 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'three': Invalid argument Nov 28 14:40:47.130524 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'four': Invalid argument Nov 28 14:40:47.130554 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'five': Invalid argument Nov 28 14:40:47.130564 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'six': Invalid argument Nov 28 14:40:47.130571 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'seven': Invalid argument Nov 28 14:40:47.130580 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'eight': Invalid argument Nov 28 14:40:47.130588 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'nine': Invalid argument Nov 28 14:40:47.130596 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'zero': Invalid argument Nov 28 14:40:47.130629 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'repeat': Invalid argument Nov 28 14:40:47.130639 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'volume_mute': Invalid argument Nov 28 14:40:47.130647 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'period': Invalid argument Nov 28 14:40:47.130657 LibreELEC (udev-worker)[1506]: event11: Failed to parse key identifier 'leftquote': Invalid argument -
and the bizarre thing is, when I run evtest, and accidently press the power button on the remote, libreelec powers off.
So, the device is clearly seeing the remote, but Kodi is refusing to play along.
Could the bluez stack used be causing issues
Oh, I'm running nightlies on my device too -
managed to run bluetoothctl and evtest on libreeelc, results are posted here
External Content pastebin.comContent embedded from external sources will not be displayed without your consent.Through the activation of external content, you agree that personal data may be transferred to third party platforms. We have provided more information on this in our privacy policy.So, while the remote does connect, and my chromebox/pc does indeed see the inputs, there seems to be no input received by kodi.
-
Alas, tried both and still no response.
Devie is a chromebox running libreelec, it sees the remote, and connects. But it doesn't want to interact
bluetoothctl - info
info 25:04:27:11:28:95
Device 25:04:27:11:28:95 (public)
Name: Remote-V12
Alias: Remote-V12
Appearance: 0x0180 (384)
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: yes
WakeAllowed: yes
LegacyPairing: no
CablePairing: no
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Battery Service (0000180f-0000-1000-8000-00805f9b34fb)
UUID: Human Interface Device (00001812-0000-1000-8000-00805f9b34fb)
UUID: Public Key Open Credent.. (0000fff0-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (a8253f01-0c51-4000-b84f-1500068fb5a3)
Modalias: usb:v5A44p5A44d0000
ManufacturerData.Key: 0x03e0 (992)
AdvertisingFlags:
06 .
Battery Percentage: 0x64 (100)
hci0 type 7 discovering off
hci0 type 7 discovering on
[CHG] Device 35:A0:F5:CC:36:10 RSSI: 0xffffffb3 (-77)
[CHG] Device 03:3E:33:CF:9F:9E RSSI: 0xffffffb3 (-77) -
Yeah, I've gotten that file from coreelec a while back.
I've placed it in .storage/hwdb.d
but alas, no response. -
Trying to set up and use the zidoo v-12 remote. It connects via bluetooth, but the device does not seem to respond to inputs
Code
Display Morecat /proc/bus/input/devices I: Bus=0019 Vendor=0000 Product=0001 Version=0000 N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input0 U: Uniq= H: Handlers=kbd event0 B: PROP=0 B: EV=3 B: KEY=8000 10000000000000 0 I: Bus=0019 Vendor=0000 Product=0006 Version=0000 N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=3e000b00000000 0 0 0 I: Bus=0003 Vendor=1997 Product=2433 Version=0101 N: Name=" AirMouse" P: Phys=usb-0000:00:14.0-2/input0 S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/0003:1997:2433.0001/input/input2 U: Uniq= H: Handlers=sysrq kbd leds event2 B: PROP=0 B: EV=120013 B: KEY=1000000000007 ff9f207ac14057ff febeffdfffefffff fffffffffffffffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=1997 Product=2433 Version=0101 N: Name=" AirMouse" P: Phys=usb-0000:00:14.0-2/input1 S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:1997:2433.0002/input/input3 U: Uniq= H: Handlers=mouse0 event3 B: PROP=0 B: EV=17 B: KEY=1f0000 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0003 Vendor=1997 Product=2433 Version=0101 N: Name=" AirMouse System Control" P: Phys=usb-0000:00:14.0-2/input1 S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:1997:2433.0002/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=13 B: KEY=c000 10000000000000 0 B: MSC=10 I: Bus=0003 Vendor=1997 Product=2433 Version=0101 N: Name=" AirMouse Consumer Control" P: Phys=usb-0000:00:14.0-2/input1 S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.1/0003:1997:2433.0002/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=1f B: KEY=33eff 0 0 483ffff17aff32d bfd4444600000000 1 130c730b17c000 267bfad9415fed 9e168000004400 10000002 B: REL=1040 B: ABS=100000000 B: MSC=10 I: Bus=0003 Vendor=4842 Product=0001 Version=0201 N: Name="HAOBO Technology USB Composite Device Keyboard" P: Phys=usb-0000:00:14.0-3/input2 S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.2/0003:4842:0001.0003/input/input6 U: Uniq=8545124150344E37 H: Handlers=sysrq kbd leds event6 B: PROP=0 B: EV=12001f B: KEY=33eff 0 0 483ffff17aff32d bfd4444400000000 1 130ff38b17c007 ffff7bfad9415fff febeffdfffefffff ffffffffffffff fe B: REL=1040 B: ABS=100000000 B: MSC=10 B: LED=1f I: Bus=0003 Vendor=4842 Product=0001 Version=0201 N: Name="HAOBO Technology USB Composite Device" P: Phys=usb-0000:00:14.0-3/input3 S: Sysfs=/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.3/0003:4842:0001.0004/input/input7 U: Uniq=8545124150344E37 H: Handlers=mouse1 event7 B: PROP=0 B: EV=17 B: KEY=70000 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:03.0/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0001 Vendor=10ec Product=0283 Version=0001 N: Name="HDA Digital PCBeep" P: Phys=card1/codec#0/beep0 S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input11 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=40001 B: SND=6 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=10 I: Bus=0000 Vendor=0000 Product=0000 Version=0000 N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci0000:00/0000:00:1b.0/sound/card1/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0005 Vendor=5a44 Product=5a44 Version=0000 N: Name="Remote-V12 Keyboard" P: Phys=7c:5c:f8:f2:37:4d S: Sysfs=/devices/virtual/misc/uhid/0005:5A44:5A44.0008/input/input18 U: Uniq=25:04:27:11:28:95 H: Handlers=sysrq kbd leds event14 B: PROP=0 B: EV=12001f B: KEY=33eff 0 0 483ffff17aff32d bfd4444600000000 3ff 130ff38b17c007 ffff7bfad9415fff febeffdfffefffff ffffffffffff fffe B: REL=1040 B: ABS=100000000 B: MSC=10 B: LED=1f I: Bus=0005 Vendor=5a44 Product=5a44 Version=0000 N: Name="Remote-V12 Mouse" P: Phys=7c:5c:f8:f2:37:4d S: Sysfs=/devices/virtual/misc/uhid/0005:5A44:5A44.0008/input/input19 U: Uniq=25:04:27:11:28:95 H: Handlers=mouse2 event15 B: PROP=0 B: EV=17 B: KEY=1f0000 0 0 0 0 B: REL=903 B: MSC=10any advice on what should be created re: udev rules etc would be most welcome.
-
I have been using this great addon with Leia builds (Coreelec 8.95.0) and it is working fine.
Coreelec doesn't make a intel version of their firmware, so I'll give the latest libreelec beta/alpha a try out.
Did you need to do anything special to get this addon to work?
(As in,did you update Coreelec to 8.95.0 with openvpn already installed or did you update and install afterwards?Scratch those questions.
Libreelec alpha works fine.
I do admit it was a year since I last updated to kodi leia and the openvpn addon did not work then. It does now. Sorry for any inconvenience or annoyance caused.
You're doing fine work Zomboided, keep it up
-
Aye, there seems to be a dearth of information concerning to new changes. And yes it looks like an awful lot of addons will indeed be broken when kodi 18 RC or PR gets released.
From what I've been able to gather the change occurred last year in the alphas, and there has been no change since.
Hopefully they will publish the relevant documentation in usual spaces.
Cheers for getting back to me.
Edit;
Guidelines are published here, best of luck. -
Understandable.
Although, I wasn't referring to the standard/default skins settings, I was referring to how the changes in leia's addons' settings are laid out. (See [settings] change XML format of setting values by Montellese · Pull Request #12277 · xbmc/xbmc · GitHub )
As it stands, your vpn's settings page will not open in kodi beta 18, hasn't been able to for months. It was brought up before, and you stated you did not deal with alpha builds, and for good reason.
Just curious if that policy changes now that that particular change in kodi has been more or less finalised. -
Now that Kodi Leia has entered beta, will this addon be updated to work with the new settings layout?
-
zoogvpn (uk server 4) and VPN unlimited both work with VPNmanager and iplayer is accessible. (zoog requires manual set up.)
Windscribe have a dedicated server for uk and us netflix. But it seems to be only available for their android app, not seen it pop up on ios or in the download files. -
Yeah, I see it now.
There are no errors in the changelog. It looks like the issue lies with ExpressVpn and the UK server you're using.
Does ExpressVpn have only one UK server? (Other providers have 3 or four servers, some even have dedicated servers for bbc iplayer and netflix.) -
Are you sure you are connecting to a London server?
In the log you supply you are connecting to New Zealand, using a New Zealand ovpn file -
I wonder if you read through that link. The solution is there.
Or if you're too lazy, it's here
The version originally included with libreelec gave me nothing but aw snap errors too. The BBC iPlayer was unusable. But, the version of chromium in that link works perfectly fine.
If only it can work with flash correctly on the channel 4 site. -
Any idea what I'm doing wrong?
At a guess, not reading the forum. Go back a page or two.
#post69377 -
On Milhouse nightlies for libreelec 9 since june 4th builds, vpn manager seems to be causing homescreen-blank screen loops, basically, it looks like kodi.bin is being killed.
The end of the debug file reads the following.Code12:32:38.072 T:139954648073984 WARNING: CAddonSettings[service.vpn.manager]: trying to load setting definitions from old format... 12:32:38.074 T:139954648073984 WARNING: CAddonSettings[service.vpn.manager]: ignoring old setting definition of type "text" without idIf I remote access my device and delete the
service.vpn.manager folder in ~.storage/kodi/addons everything works fine. Until I download and install vpnmanager again.
Hopefully this is just some trivial problem that can be easily rectified.