Posts by Bubba2017

Hi king322,
I am not an expert, but the guys here gave me instructions (plus I added some that I felt might be helpfull)
thread-7152-post-43818.html#pid43818

If you get stuck let me know.

As a side note I programmed all my remotes at the same time in the same file. That way if my wife has the tv remote she can start or stop a move and fast forward and my remote can do the same

Quote from DaVu

Then your best bet might be reporting at this thread.

Thanks DaVu,

That's why I am here

Ok,
For user friendliness it might be good to include the restore boot image.
I thought I damaged 2 USB sticks before I thought that something was going on and spent some time to look into fixing my issue.

My thoughts were that the program shouldn't induce heart attack that the creator damaged my drive. (when it didn't, it just did something that windows can't normally handle).

So could this be fixed if the creator had the restore boot sector option and a Notice (to new users) that you can restore your USB sticks full capacity by ?....

If it helps I had to try several things outside of the forum before finding the diskpart solution. I didn't think it was the creators that had originally caused the problem.

Have tried Milhouse build at one point. And the Official 8.0.1

This is the version I am currently using ===> thread-302.html

(Don't know how to compile)

Windows doesn't know how to work with partitions on a USB stick.
You can't just format it. It will only format the visible partition.
The larger partition not accessible. Even in DiskManager. It is visible, but DiskManager is unable to do anything such as remove the partition.
One must use DiskPart (which is not noob/commoner friendly)

Is there another way that the USB-Creator could make a USB stick without partions in the first place? Could mounting eliminate the need to partition?

Using DiskpartYou might overwrite any hard disk on the computer.
If at some point you are not sure about the disk number, stop proceeding.

• Make sure that the USB stick or SD card that you want to reset is unplugged.
• Click on the Start button, and choose All Programs ▸ Accessories ▸ Command Prompt, to open the Command Prompt,More help on how to start the Command Prompt
• Execute the diskpart command, to start Diskpart.
• Execute the list disk command to obtain information about each disk in the computer.For example:
  
  
  Code

  Diskpart> list disk Disk ### Status Size Free Dyn Gpt -------- ---------- ------- ------- --- --- Disk 0 Online 80 GB 0 B

• Plug the USB stick or SD card that you want to reset. Run the list disk command again.A new disk, which corresponds to that device, appears in the list.For example:
  
  
  Code

  Diskpart> list disk Disk ### Status Size Free Dyn Gpt -------- ---------- ------- ------- --- --- Disk 0 Online 80 GB 0 B Disk 1 Online 4 GB 0 B

  
  Make sure that its size corresponds to the size of the device that you want to reset. Note down the disk number assigned by Diskpart to the device.

• To select the device, execute the following command: select disk=number. Replace number by the disk number of the device that you want to reset.
• Execute the clean command to delete the partition table from the device.
• Execute the convert mbr command to create a new partition table on the device.
• Execute the create partition primary command to create a new primary partition on the device.

Why does the the USB-SD Creator need to make a partition on the USB stick or SD card when run from windows.
It doesn't appear that Windows is capable of working with partitions on these types of devices.

To make the tool user friendly could the windows USB-SD Creator tool be programmed with the abillity to reclaim the USB stick or SD card for use in windows (i.e. unpartition for dummies)

I have noticed that every video I play results in the Free Memory shrinking. Play a movie/tvshow from the library or from USB HD and just skip to 10 min in then end, go check free memory in the System Info and the amount drops.

Eventually my PC crashes

Full hardware specs (GPU is most important): Acer ES1-511-C35L with Mesa DRI Intel Bay Trail GPU and N3530 CPU, 4GB ram, 3TB usb3 HD on usb3 port
The LibreELEC version you are running ('latest' is not a version number): Community build devel-20170410

• In most cases a full debuglog: VJEV
• Tell us the complete steps how to face the issue, so we can try to reproduce: mentioned above. Play a video i.e. 1080P Hevc 8bit skip to 10min, stop, check memory and repeat
• Informations about the Kodi video and audio settings (maybe a screenshots from both): Monitor HDMI1 (4K Vizio TV in 1080P 60Hz and blank other screen with limited colours) Audio is ALSA:HDA Intel PCH,VIZ E55-E1 on HDMI with 2.0 channels optimized output.
• If possible a mediainfo from that file/container: Various formats from x264 to x265

Ok thanks HiassofT

Will there be changes in 9.0? It's too bad that there wasn't a simple addon to setup program and configure a remote without having to make all the files and read dozens of web pages and a noob who is non-linux in nature could figure out. The tutorial above did the trick, but it's far from user friendly.

I am still struggling to get my games to work. Some do some don't.
I have 2 Wii games... able to get them to run, but can't figure out the wii remote things. with lots of digging was able to get them to sometimes connect automatically, just not work in the games.

It's a work in progress. I am learning lots.

I am using the community build with retroplayer integrated.

Just run the update from the LibreElec addon?
How do you want me to test?

I have all my remotes currently working. Do you need me to test without the autostart.sh line?

Quote from HiassofT

Thanks for the feedback!

It's odd that you needed to add that command to autostart.sh, the system should pick up .config/rc_maps.cfg automatically on boot.

Could you please run the following commands and post the URL you got from the last one?

Code

udevadm control -l debug
udevadm trigger --action=add -s input
journalctl -a | paste

so long,

Hias

I ran the commands as asked as I currently have it setup.
Here is what the results were --> LcGV

I too am seeing the same symtoms as kobrawerde.
Fast forward jumps like 5 minutes.
Accessing SMB for videos results in loss of networks access.

I moved my HD to the usb on the computer directly and now FF works correctly and videos don't stop causing loss of network access.

I wouldn't know how to submit a log or what data you would need.

The version is Community build (with EMU's) LibreELEC-Generic.x86_64-8.0-devel-20170410 (upgraded to from previous 20170409)

I am running Libreelec on a laptop and have the same problem. Am able to shutdown the system, but not wake it.

Quote from escalade

Drag & drop to the update folder is hard?

I believe there are ways to add custom update channels, but I'd need to research how to do that and probably change my hosting. Don't see much gain from doing so

No problem, Just thinking of noobs like me. Allows to see that there is a new version without searching the forum.
Your doing a great job.

Still haven't figured out how to get wii remotes to work in the Wii emu

Is there a custom Update url that can be put in the LibreELEC app to make updating easier?

I have one for Milhouse builds.

Question,

If you already have #!/bin/sh in the Autostart.sh file at the top, do you need to put it again just before the new items you added?

Quote from daweze

Configured this for a buddy.

Hey Thanks daweze,

I don't know what to do with the files you provided.

I was able to program my remote using the method Hiassof provided.

Thanks though.

Quote from HiassofT

Since the remote is supported by the kernel it's best to create an ir-keytable file instead of using userspace lircd.

First stop eventlircd and kodi so they don't interfere:

Code

systemctl stop kodi
systemctl stop eventlircd

Then we need to find out which protocol the remote is using. To do that we need some info about the IR receiver which we can get with "ir-keytable". The output should look like this:

Code

LibreELEC:~ # ir-keytable
Found /sys/class/rc/rc0/ (/dev/input/event1) with:
Driver (null), table rc-dib0700-rc5
Supported protocols: rc-5 nec rc-6
Enabled protocols: rc-5
Name: IR-receiver inside an USB DVB re
bus: 3, vendor/product: 2040:7060, version: 0x0100
Repeat delay = 500 ms, repeat period = 125 ms

The important things are the supported and enabled protocols. Since you already got scancode output from "ir-keytable -t" you only need to test within the "Enabled protocols", otherwise you'd need to go through all "Supported protocols" (except "lirc", which isn't a real protocol).

Now test with each protocol if you get scancode output. Run the following command (change the protocol after "-p") and press buttons on your remote.

Code

ir-keytable -p nec -t

If you get no event output try the next protocol.

If you set the correct protocol the output should look like this - note the EV_MSC events with "scancode = ..."

Code

LibreELEC:~ # ir-keytable -p nec -t
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
1491293447.763188: event type EV_MSC(0x04): scancode = 0x847908
1491293447.763188: event type EV_SYN(0x00).
1491293448.029412: event type EV_MSC(0x04): scancode = 0x847908
1491293448.029412: event type EV_SYN(0x00).
1491293448.351181: event type EV_MSC(0x04): scancode = 0x847908
1491293448.351181: event type EV_SYN(0x00).

(BTW: the output above is with a WDTV live remote which I happened to have sitting in a box)

Now that we have determined the protocol we can create a keytable file for the remote in /storage/.config/rc_keymaps/ - let's name it "wdtv-live". Open another ssh session and start an editor (keep "ir-keytable -t" running in the other session, we need that to get the scancodes).

Code

nano /storage/.config/rc_keymaps/wdtv-live

In the very first line we have to put a header with the name of the table (the actual name is not important, better avoid blanks in it but you can name it anything you like) and the protocol (after "type: "). The protocol is the important thing here. The header should look like this:

Code

# table wdtv-live, type: NEC

Now we have to map the buttons. Press a button on the remote, record the scancode you got from ir-keytable (the 0x... code after "scancode = ...") and add it to the keytable file together with the key name. Note: you have to use the official linux keynames as listed in linux/include/uapi/linux/input-event-codes.h - Elixir - Free Electrons

When you're done the keytable file should look like this:

Code

# table wdtv-live, type: nec
0x847905 KEY_UP
0x847900 KEY_DOWN
0x847907 KEY_LEFT
0x847909 KEY_RIGHT
0x847908 KEY_OK
0x84791b KEY_BACK

CTRL+O to save and CTRL+X to exit when done

Save the file, stop "ir-keytable -t" and test if the keytable file is correct. Run the following command (it clears the current kernel keytable, loads your newly created one and then starts test mode) and press keys on the remote. Note that you should now also see EV_KEY events with the keycodes:

Code

LibreELEC:~ # ir-keytable -c -w /storage/.config/rc_keymaps/wdtv-live -t
Read wdtv-live table
Old keytable cleared
Wrote 6 keycode(s) to driver
Protocols changed to nec
Testing events. Please, press CTRL-C to abort.
1491296520.391503: event type EV_MSC(0x04): scancode = 0x847907
1491296520.391503: event type EV_KEY(0x01) key_down: KEY_LEFT(0x0001)
1491296520.391503: event type EV_SYN(0x00).
1491296520.644387: event type EV_KEY(0x01) key_up: KEY_LEFT(0x0001)
1491296520.644387: event type EV_SYN(0x00).
1491296522.156906: event type EV_MSC(0x04): scancode = 0x847908
1491296522.156906: event type EV_KEY(0x01) key_down: KEY_OK(0x0001)
1491296522.156906: event type EV_SYN(0x00).
1491296522.431047: event type EV_KEY(0x01) key_up: KEY_OK(0x0001)
1491296522.431047: event type EV_SYN(0x00).

Display More

To make this permanent create a rc_maps.cfg file in /storage/.config/

Code

nano /storage/.config/rc_maps.cfg

Insert the following line to automatically load your keymap (on any ir receiver with any kernel default keymap):

Code

* * wdtv-live

Save the file, then run the following command to test if everything's setup correctly:

Code

LibreELEC:~ # ir-keytable -a /storage/.config/rc_maps.cfg
Old keytable cleared
Wrote 6 keycode(s) to driver
Protocols changed to nec

systemctl start kodi allows starting kodi and testing.
so long,

Hias

Display More

Thanks this did work.
I needed to add

ir-keytable -a /storage/.config/rc_maps.cfg

to the autostart.sh file to make it work after rebooting.
I added in red things that might help others who are noob like me.

Trying to setup my Infrared remote control on LE community deve-20170401 Generic.x86_64 (Acer Aspire ES1-511 laptop HTPC)
I was able to see my codes (below).
irrecord doesn't seem to create the Lircd.conf

I don't know what to do. I have searched and tried many guides. Please help.

Testing events. Please, press CTRL-C to abort.
1491257390.801027: event type EV_MSC(0x04): scancode = 0x847912
1491257390.801027: event type EV_SYN(0x00).
1491257399.664019: event type EV_MSC(0x04): scancode = 0x847906
1491257399.664019: event type EV_SYN(0x00).
1491257400.588036: event type EV_MSC(0x04): scancode = 0x84790c
1491257400.588036: event type EV_SYN(0x00).
1491257402.081120: event type EV_MSC(0x04): scancode = 0x84790d
1491257402.081120: event type EV_SYN(0x00).
1491257402.874016: event type EV_MSC(0x04): scancode = 0x847902
1491257402.874016: event type EV_SYN(0x00).
1491257403.579841: event type EV_MSC(0x04): scancode = 0x847904
1491257403.579841: event type EV_SYN(0x00).
1491257404.217898: event type EV_MSC(0x04): scancode = 0x847901
1491257404.217898: event type EV_SYN(0x00).
1491257405.010623: event type EV_MSC(0x04): scancode = 0x84791f
1491257405.010623: event type EV_SYN(0x00).
1491257405.541018: event type EV_MSC(0x04): scancode = 0x84790a
1491257405.541018: event type EV_SYN(0x00).
1491257406.006006: event type EV_MSC(0x04): scancode = 0x84791e
1491257406.006006: event type EV_SYN(0x00).
1491257406.865089: event type EV_MSC(0x04): scancode = 0x84791b
1491257406.865089: event type EV_SYN(0x00).
1491257407.439106: event type EV_MSC(0x04): scancode = 0x847905
1491257407.439106: event type EV_SYN(0x00).
1491257407.969629: event type EV_MSC(0x04): scancode = 0x84791a
1491257407.969629: event type EV_SYN(0x00).
1491257408.675564: event type EV_MSC(0x04): scancode = 0x847907
1491257408.675564: event type EV_SYN(0x00).
1491257409.293317: event type EV_MSC(0x04): scancode = 0x847908
1491257409.293317: event type EV_SYN(0x00).
1491257409.888005: event type EV_MSC(0x04): scancode = 0x847909
1491257409.888005: event type EV_SYN(0x00).
1491257410.484134: event type EV_MSC(0x04): scancode = 0x84794c
1491257410.484134: event type EV_SYN(0x00).
1491257411.036439: event type EV_MSC(0x04): scancode = 0x847900
1491257411.036439: event type EV_SYN(0x00).
1491257411.523377: event type EV_MSC(0x04): scancode = 0x847903
1491257411.523377: event type EV_SYN(0x00).
1491257412.239423: event type EV_MSC(0x04): scancode = 0x84794d
1491257412.239423: event type EV_SYN(0x00).
1491257412.762019: event type EV_MSC(0x04): scancode = 0x847941
1491257412.762019: event type EV_SYN(0x00).
1491257413.380251: event type EV_MSC(0x04): scancode = 0x847914
1491257413.380251: event type EV_SYN(0x00).
1491257413.933137: event type EV_MSC(0x04): scancode = 0x847915
1491257413.933137: event type EV_SYN(0x00).
1491257414.573441: event type EV_MSC(0x04): scancode = 0x847916
1491257414.573441: event type EV_SYN(0x00).
1491257415.125630: event type EV_MSC(0x04): scancode = 0x847917
1491257415.125630: event type EV_SYN(0x00).
1491257415.766033: event type EV_MSC(0x04): scancode = 0x847918
1491257415.766033: event type EV_SYN(0x00).
1491257416.341035: event type EV_MSC(0x04): scancode = 0x847919
1491257416.341035: event type EV_SYN(0x00).
1491257416.959202: event type EV_MSC(0x04): scancode = 0x84790e
1491257416.959202: event type EV_SYN(0x00).
1491257417.687310: event type EV_MSC(0x04): scancode = 0x84791c
1491257417.687310: event type EV_SYN(0x00).
1491257418.349617: event type EV_MSC(0x04): scancode = 0x84791d
1491257418.349617: event type EV_SYN(0x00).
1491257418.924109: event type EV_MSC(0x04): scancode = 0x84795e
1491257418.924109: event type EV_SYN(0x00).
1491257419.586404: event type EV_MSC(0x04): scancode = 0x84795d
1491257419.586404: event type EV_SYN(0x00).
1491257420.204615: event type EV_MSC(0x04): scancode = 0x84795c
1491257420.204615: event type EV_SYN(0x00).
1491257420.823185: event type EV_MSC(0x04): scancode = 0x84795f
1491257420.823185: event type EV_SYN(0x00).
1491257421.507479: event type EV_MSC(0x04): scancode = 0x84790f
1491257421.507479: event type EV_SYN(0x00).
1491257422.333597: event type EV_MSC(0x04): scancode = 0x847911
1491257422.333597: event type EV_SYN(0x00).
1491257423.053271: event type EV_MSC(0x04): scancode = 0x847910
1491257423.053271: event type EV_SYN(0x00).