So if you install to internal memory, it wipes android OS interface?
Yes. You've replaced the os.
So if you install to internal memory, it wipes android OS interface?
Yes. You've replaced the os.
When you installed libreelec you had a choice - install to sd card (or usb stick) or install to internal memory.
If you installed to sd / usb then you can either:
'Reboot to nand' - may be in your power memory if you're using the default skin;
or power off, unplug the sd / usb, power on.
If you installed to internal memory then android is gone. You'd need to reinstall.
I've used NTFS drives for media storage over the last few years with openelec and latterly libreelec - up to 5TB - without problems. Read / write access is standard. Ext4 is great if you don't use windows - for most of us not so much though.
I've got an 8 gb microsd with LE 8 on it. For the moment all source is on this disk. Then there is an empty SanDisk Cruizer 32 gb usb formatted to ext4 (it is recognized but not used at the moment).
With cmdline.txt is there a way to redirect just the storage directory to the usb or will the entire root have to be redirected?
Rather than write it again:
thread-1456-post-12362.html#pid12362
Bear in mind that will boot to an empty partition on your stick. But if you make a backup on your sd card you can restore that to your stick.
Edit: other people will tell you to use UUIDs rather than labels. Up to you, it all works.
The obvious ways are either, as vitorp07 suggests, to boot from usb (which has only recently become an option) or to boot from sd card but use a usb stick formatted to ext4 as a storage partition - that can be accomplished by editing cmdline.txt on the fat partition of your sd.
If you're using an mce remote and receiver you're probably using LIRC, so <remote> not <keyboard> is needed.
Turn on debug logging, press ok, refresh the log and you'll see what the remote is passing to kodi.
Hi, just discovered LibreELEC, I'm running it on raspberry pi3 and I must say it's brilliant. Just one problem I have though is that when using Kodi in Windows I can hold down the ok button on the Media Center Remote control to bring up the context menu. But on the LibreELEC Rpi build this no longer works, holding down ok button just repeats lots of ok presses. I'm actually using a Logitech remote with a Microsoft IR receiver, it may be something to do with that but like I say it worked fine on Windows with Kodi.
So has anyone else come across this and is there a way of fixing it? (I'm ok with Linux and editing config files etc).
Thanks
Paul
Does the 'Guide' button not bring up the context menu? That's what I'd expect to see.
As above though, you can probably* change the longpress behaviour with a keymap. You can certainly map the context menu to a separate button.
*As in you can certainly change it, and it will probably work - I've had difficulty with distinguishing longpresses with particular remotes though.
Thanks for the info, I already use Confluence and like it. When updating within the Update folder, is that for my SD card or internal NAND? I run LE from my SD card...
Thanks again
Works for both / either.
Do I just save the .img.gz download there and reboot and that's it? Can I update from 7.0.3.012i to 8.0.0c ?TIA
Yes, yes and yes. And yes.
If you're jumping from 7 to 8 I'd run a backup first, otherwise you can't easily revert - but that's your call.
I'd also switch to confluence - if you're not already using it - before updating.
Maybe I didn't read enough documentation, but I'm wondering if there's a sweet SSH command I can use to push the updates, rather than re-format and flash a fresh copy on my sd card. I'm completely fine re-formatting and restoring each update, but I'd be punching myself if there was an easier solution.I thank ANYONE in advance who replies
I'm sure you can update via ssh - I've never bothered because doing it via smb is so easy.
Download the update to your pc - either the img.gz or the .tar, doesn't matter.
Open an explorer window and navigate to your device (eg I use '\\192.168.1.42' or '\\Beelink' to see my box at that IP with that hostname).
You should see a bunch of links, one of which is 'Update' - this is a shortcut to the /storage/.update folder on your box. Paste the file you just downloaded into there. Reboot libreelec. Done.
All I did was to follow the advice in the link.
So run...
udevadm monitor -p
unplug your dongle, plug it back in, look for your vendor id and product id (they weren't named exactly that for me but they were fairly obvious). Or post the output here.
No guarantees this will work for you, obviously - I'm no expert in this. It just looks like a similar issue.
I had a similar problem with a different remote - fixed by sticking a 51-these-are-not-joysticks-rm.rules file (with the correct vendor and product id's for my remote) in the storage/.config/. udev.rules.d folder. Similar to this:
http://forum.kodi.tv/showthread.php?tid=278842&page=13
I guess you mean you're imaging the card, writing a new card, copying everything off the fat partition, writing the image back to the card, then deleting the contents of the fat partition and putting the new files on it. That would work but it's easier - less messing about - if you can find an old usb stick down the back of the sofa.
In theory it will also work when you're moving to a pi3. I've always started fresh going from pi to pi2 or pi3. But actually what you have now on the card should (I think) boot on a pi2 or pi3.
The easiest way I can think of...
Head to the downloads section.
Follow the instructions to make a new sd card with the usb-sd creator tool - using a different sd card or usb stick.
When you're done, take your old (non-working) card and wipe the fat partition (the partition you see in windows, about 500MB ish).
Copy everything from the fat partition of your new card that you've just made onto the old one.
Boot pi with the old card and it should update to libreelec.
Making a backup of the old card (if in windows using win32diskimager or usbit) first wouldn't be the worst idea in the world.
Alternatively...
Do something similar (ie make a new sd card) but this time do it using the same openelec version as was originally on your card - so from the openelec site, download an image and write to an sd card / usb stick with win32diskimager. After moving stuff across between cards your pi should boot into openelec again on the old card - you can do your backup and try again.
I took a look in install script. It search for remote.conf in various locations
But I didn't have any of those. Do you have one for MXIII ?
I'm presuming you mean Beelink minimx iii...?
#*********************************************************************************************************
#Beelink mxiii default remote
#this file is configuration for each factory remote device
# work_mode 0 :software mode 1 :hardware mode
# repeat_enable 0 :disable repeat 1 :enable repeat
#
# factory_code each device has it's unique factory code.
# pattern:custom_code(16bit)+index_code(16bit)
# examble: 0xff000001 = 0xff00(custom cod) 0001 (index)
#
# release_delay unit:ms.release will report from kernel to user layer after this period of time
# from press or repeat triggered.
#
# debug_enable 0 :debug disable 1 :debug disable
#
# SW MODE:
# bit_count how many bits in each frame
# tw_leader_act time window for leader active
# tw_bit0 time window for bit0 time.
# tw_bit1 time window for bit1 time
# tw_repeat_leader time window for repeat leader
# REG
# reg_base_gen set value for PREG_IR_DEC_BASE_GEN
# reg_control set value for PREG_IR_DEC_CONTROL
# reg_leader_act set value for PREG_IR_DEC_LEADER_ACTIVE
# reg_leader_idle set value for PREG_IR_DEC_LEADER_IDLE
# reg_repeat_leader set value for PREG_IR_DEC_REPEAT_IDLE
# reg_bit0_time set value for PREG_IR_DEC_BIT0_TIME
#*************************************************************************************************************
#amlogic NEC remote
factory_code = 0xff000001
work_mode = 0
repeat_enable = 1
repeat_delay = 130
repeat_peroid = 120
release_delay = 20
debug_enable = 1
key_begin
0x48 102 #HOME
0x01 158 #BACK
0x03 103 #UP
0x02 108 #DOWN
0x0e 105 #LEFT
0x1a 106 #RIGHT
0x07 97 #OK
0x13 139 #MENU
0x58 114 #VOL-
0x0b 115 #VOL+
0x5c 264 #FN
# 0x14 704 #POWER
key_end
repeat_key_begin
0x48 102 #HOME
0x01 158 #BACK
0x03 103 #UP
0x02 108 #DOWN
0x0e 105 #LEFT
0x1a 106 #RIGHT
0x07 97 #OK
0x13 139 #MENU
0x58 114 #VOL-
0x0b 115 #VOL+
0x5c 264 #FN
# 0x14 704 #POWER
repeat_key_end
Display More
I'm having the same configured on my Harmony "Microsoft Windows Media Center SE"
Has that worked in older versions of libreelec? I read your thread title as 'This is a new problem with 7.95.3', but maybe I've misunderstood.
What happens when you try to use it (nothing?)?
MCE which worked perfect on my NUC when I had Win10 installed
Can you be more specific? There are a few MCE devices.
eg I use ' Microsoft Windows Media Center SE '.
Hi,just thought I'll give it a try but on putty I get the error message remotecfg: not found ... any idea why? I copied your test config file without any problems ...
Best
Just to keep this thread tidy - you're on a NUC, so the guide won't do nuffin. Amlogic only.