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

    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.com
    Content 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)

    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

    any 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 :D

    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.

    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

    Code
    Connecting to VPN profile /storage/.kodi/addons/service.vpn.manager/ExpressVPN/New Zealand (UDP).ovpn
    18:02:05.675 T:140683507648256  NOTICE: VPN Mgr : (common.py) Received connection info from ipinfo.io, IP 221.121.135.68 location Auckland, NZ, ISP AS45671 AS45671 Network Operation

    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.

    Code
    12: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 id

    If 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.