It is there
LibreELEC:~ # which irexec
/usr/bin/irexec
LibreELEC:~ # /usr/bin/irexec -h
Usage: /usr/bin/irexec [options] [config_file]
-h --help display usage summary
-v --version display version
-d --daemon run in background
-n --name use this program name
LibreELEC:~ #
But simple stopping of kodi does not turn off hdmi
How exactly are you stopping kodi with irexec?
I had a go a while ago but gave up.
Thanks Troggy
Is this the latest TWRP - TWRP 3.0.2-0 Released and do i just put it on an SD card with the stock firmware???
No idea, sorry. I've restored with the TWRP from the Freaktab thread I linked to, so I know it works. Not needed it since, hopefully never will.
All we need is to make kodi to ignore its "power" button (I think this controlled by /usr/share/kodi/system/keymaps/remote.xml), and use irexec to execute system command like this: "systemctl start/stop kodi.service"
There's no Lirc and hence no irexec in these builds, so maybe not that straightforward.
Hi guysCould someone please point me in the right direction for the TWRP software that I can put on my SD card to then add my Beelink Mini MXiii original ROM should I ever wish to go back to android?
I have been on the TWRP website but they don't have a download for the Amlogic s905 or Beelink Mini MXiii.
Many thanks
I used the twrp from this thread to restore android a few months ago - worked fine:
Freaktab
Edit: saying that the original firmware is up on the beelink site...
Here.
All I'd say is 1GB sounds a bit on the small side - might cause you some problems in the future (thumbnails folder could end up filling that on its own), and it'll almost certainly cause issues with updates and / or backups not having enough space at some point.
I use small (eg 1GB) partitions for testing, but I'd want at least 4GB (my arbitrary limit) for a 'proper' install.
There shouldn't be an issue with mixing your media (films / music) with libreelec data in 1 big usb partition - the partition even comes with folders for exactly that by default (made on first boot).
Fair enough. But what files do you have to move on the USB stick?(...me going to check the other forum...)
If you want to move your current install you could stick the formatted usb in the running pi, copy all files from storage (on the sd card) to the usb, shut down, change cmdline.txt on your pc and re-start.
Or use the built-in backup add-on to back up your current install, then poweroff, change cmdline.txt, boot with the usb inserted (which gives a fresh install) then restore from the backup.
Either of the above works (and there are plenty of other ways). All you're doing is copying what's in 'storage' on your sd card to the usb stick.
This is guide is for openelec but works with libre as well:
How to install OpenELEC on USB stick for Raspberry Pi?
It's really not that complicated.
Quoting myself from an openelec forum thread:
It's really straightforward to do.
Format a usb stick to ext4, give it a name / label.
Use that label in cmdline.txt on the sd card.
eg if you call the usb 'openelec'...boot=/dev/mmcblk0p1 disk=LABEL=openelec quiet
I prefer not to use 'storage' as a label, because that's the default - but it doesn't matter what you call it as long as there's no other partition with the same name.
I don't like using the uuid because if you copy to a different drive you have to change it.
If it's just the skin that's resetting then yes, switching skins will keep your settings. That's down to kodi not shutting down properly.
The problem you describe in the first post sounds like something different - so it's just skin settings not saving?
I'll be receiving my 2gb/16gb MiniMXIII T95N tomorrow can't wait to install this and test it out.I also agree with ant_thomas, it would be great to be able to use standard IR commands from our MCE & harmony remotes. Been using these remotes since the OG Xbox (xbox media player) days to current builds.
Sent from my SM-G935V using Tapatalk
There's nothing to stop you using a Harmony.
If you have SSH access you could fire up putty and:
systemctl stop kodi
mv /storage/.kodi/userdata /guisettings.xml /storage/.kodi/userdata /guisettings.xmlbak
systemctl start kodi
That would restart into the default skin (but not reset aeon nox).
You can reset aeon nox manually by deleting the contents of /storage/.kodi/userdata/addon_data/skin.aeonnox (foldername might not be right, it's a guess) when the skin's not running.
Samba / remote not working doesn't sound promising though.
Wow that was fast.ok try to explain, in my setups I always split up the image and wright only the bootfiles on the sd as rpi need the sd card to boot.
Then all the system files goes to the usb.
The OSMC image tool for their system does just that.So why? you might wonder? becouse you just pop in a new usb to start a fresh (test) install no need to wright anything as the boot is on the sd and all systemfiles will wright to the new test usb.
// Richard
If you're doing that - which sounds like a good idea - why not just write to sd as normal, use it on the sd card and if you want to test something adjust cmdline.txt and pop a usb stick in?
Ask where you got the addon from.
You do realise that kind of stuff is banned here (and at the kodi forum)?
Good luck. The only thing that can really go wrong is you stick the wrong remote.conf in. And all that means is your remote won't work, so no change.
Right a get you now lol will give it a try but once question how would i get it on to libree using ( putty ) or is there a easier way of doing it lol
Easiest way if you'r on a windows pc:
Open windows explorer.
Put
\\192.168.x.xx
in the address bar (with the real IP of your box).
A bunch of stuff pops up - the default smb shares from your box. Click on 'Configfiles' and you're looking at the contents of /storage/.config.
Paste remote.conf into there.
Reboot.
Cross fingers.
Good comment but that's not it. Already set to "there are no power buttons on my original remote " and if that had been the cause it would have been the same on Windows.
Apparently on RPis there is a "config.txt" where commands relating to HDMI-CEC can be entered but on my machines that file is not present.
You won't have CEC on a bunch of random x86 machines, so that's not it - if it was a pi or amlogic it would sound like a cec issue, I agree.
I'm not convinced just setting "there are no power buttons on my original remote " is enough to get the Harmony to do what you want though - they can be tricky little sods!
If you turn the tv off with the original tv remote does that power down libreelec?
If it doesn't it can only be the Harmony.
My guess is it's a Harmony issue.
You could test this by opening the Harmony software, then look at any devices that work with Libreelec and the ehome receiver. In my case that's ' MicrosoftWindows Media Center SE ' but it could be MCE keyboard, or more than one device.
Try setting the power buttons for any such devices to 'A button on the remote for On, and a different button for Off ' - use power toggle or power on for the on button and 'none' or a random key for power off.
Update remote, test.
Yep, because you had the remote.conf in android.
So now you need to find it again (or worst case re-install android to get it).
You need the correct remote.conf for your box. If you still have android on the box you can copy it from there, otherwise it's search / ask / last option re-install android.
Once you get the remote.conf stick it in /storage/.config, reboot and it should work.
