input: LibInputTouch: Switch to get_seat_slot() to fix single touch device input by superna9999 · Pull Request #14400 · xbmc/xbmc · GitHub might be the same issue you're seeing with the touchscreen crash. If yes it will be included in the next Alpha release which is being brewed. No idea about the reversed axis .. or how to configure libinput things (sorry).
Posts by chewitt
-
-
Kodi 18 only just reached beta, so it will be a while before all the skins catch up. Most skin developers wait until beta releases start before they do any real work to support the new version; before then you're chasing a moving target.
-
You have a large number of banned piracy addons/repos installed so I'm not surprised that you have reboot issues (as crap addons are the most likely cause). No further support will be provided until you provide a debug logfile that shows a clean system.
-
"journalctl -b 0 --no-pager | paste" after a clean boot and share the URL here
-
No log = no problem
-
I did but those are all Img files, I need a Tar file to update as I'm away right now. So i thought Millhouses's would
work ??
LE supports update from .img and .img.gz as well as .tar files.
-
Read the Alpha blog post(s) on the front of our website for download URLs
-
It's tested in vmware Fusion, Workstation and ESXi, e.g. the 'real' vmware apps. Player is not a fully featured vmware app and nobody on staff uses it so I'd make an educated guess that's where the issue lies. To be crystal clear.. we create the OVA for dev/test work only. If it happens to work for anything more that's nice but we don't provide any end-user support for it.
-
PEBKAC. Import the OVA to a vmware app (other than player, which will not work) and set RAM and CPU configuration to what you desire. Then expand the disk to whatever you want (8GB is enough) and power the VM on. If you forgot to expand the disk (so /storage is stuck at 500MB) just trash the VM and start over.
-
It was some local issue at your end (bad SD card, odd PSU weirdness, etc.) .. the installer script has been used millions of times; we are very confident there are no problems with it.
-
Start by telling us which hardware you have. We hate guessing..
-
any suggestions.
I suggest you tell us what hardware you have. If not we have a 1:16 chance of guessing the correct tar file you need.
-
pavuucek The OS updates cross-arch on the same hardware without issues, but binary addons might cause some warning/failure messages until they update to newer versions. So first boot after the main upgrade might have issues, but leave it a couple of minutes for secondary updates to happen and then all should be fine again. I'd recommend making a backup though .. in case things go south for some unforeseen reason.
-
The pvr.hts "failure to connect" warning is normal when there is no local tvheadend sever and you didn't configure the client to point to a server yet, but everything else half-visible in the screenshots just looks like a screwed up install; and considering it's an untested/unsupported platform that doesn't surprise me. There's a load of OpenGL related warnings .. maybe more. If you want a cheap HTPC device go purchase a Raspberry Pi for $30 and do things properly (seriously..)
-
"it works for me" .. i.e. the mirror is up and browsing libreelec.mirror.digitalpacific.com.au returns a file listing.
-
Please do not post the same question to multiple places in the forum. Once is enough. Be patient.
-
You installed the TVH client (pvr.hts) and it cannot connect to the local host (127.0.0.1). Did you install the TVH server addon?
Also be aware that the vmware image is not supported for production use (only test/dev work) and probably hasn't ever been tested in vmware player (only ESXi, Fusion, Workstation which staff have). YMMV.
-
Most of the work kszaq did was ported to our main repo before he retired so should be present in the current alpha images. There might be a few bits missing; if true I have no idea what they are. You'll also find quite a few packaging differences between K17 and K18 so if trying to 'backport' those to his repo codebase you'll also hit challenges. As there's no clear "this is the correct approach" .. just have a crack and see what fails
