Posts by gujal

NicoLE

The 9.x image S82 will work on MX-III 2GB version.

There is no 9.x build available for the MXIII 1GB version

Quote from Compos

Thanks gujal but my box is an MXIII (not plus) S802, 1Gb and neither of those images will boot. They hang on the LibreElec boot screen as with most other images that I've found for this box.

Correct there is no 9.0 image for MXIII-1G built by Demetris, only 8.2.3 for now

Quote from Compos

Have any of you had any luck finding a Kodi 18 version which works with these boxes. I've tried all *Elec versions that I can find and none of them boot on this box. Demetris's LibreELEC-S8X2.arm-8.2.3-MXIII-1G.img is the last working image I can find.

Demetris built an initial batch of 9.0 build for MX-IIIPlus and S82 devices such a MX-III2G. He hasnt updated them for the latest LE 9.0.1 yet
You can get those builds here
StackPath

Quote from ochentay4

Damn, I need help. My box is MXIII (S802 2GB) Some time ago managed to install Remix and LibreElec 8.2.3 (S82 build, worked great), then started to play with Lakka 2.1.1 S82 and decided to install to nand. All good. Now, months later, I want to try "again" LibreElec 8.2.3 and I cant for the life of my boot from SD nor Pendrive. Flashed the IMG, put "nocompat.zip" and "remote.conf", and cant boot with the damn toothpick. If I use a SD card, it says filesystem corrupted, and if I use pendrive, it goes to recovery or boots directly to Lakka.

Could someone describe the exact and precise process to boot again from SD or Pendrive?

I also want to try 9.0... but fisrt 8.2.3

Thanks

In such cases, you need to start with Android Image again. USB Burning tool is your friend

Quote from Demetris

ok guys since my devices have updates mixed up as i flashed custom bootloaders on them i will try to revert to oem amlogic bootloader that all of you have and try again to produce working images for all people

Sorry for the mess i caused for some of you.

Will take a while though, do you want the released images removed in the mean time? Let me know.

Thanks Demetris , Please take your time and release a stable version when you are ready. To add into the mix, Kodi 18.1 is out, so please wait and build when LE upstream is ready with 18.1

I am happy with 8.2.3 for now and eagerly waiting for the LE9.x stream

Quote from Demetris

I will try to release images for only for the two devices i own

- MXIII-PLUS/MXIII-G/PROBOX2-EX-PLUS

- S82/S82B/S82H/MXIII/S89/S89H

and that's it

Please, any chance of doing it for MXIII-1GB, only if possible.

Thanks a lot, for the S82 image. Much appreciated. will try it this weekend

Eagerly awaiting Demetris to release LE9.0.0 for the S802/S812

Quote from Daaave

Because it's the only one that works properly on my M8 box. All the more recent versions have very high CPU usage at all times which affects interface speed, playback etc.

Yes, I had the same issue on the newer ones. If you connect to the box though ssh and run `top` you most probably would see a process called brcmpatch using 100% of one of the cores. To get rid of the issue I had to do a reset config in LE settings. a reboot after that, it was all fine. You will lose all your settings though including any kodi addons that you may have installed.

Quote from Daaave

Thanks very much for all your work for these boxes.

Just confirming there is a problem in recent builds for the M8 box, regarding CPU usage.

8.0.RC4 gives idle CPU usage around 3%.

More recent versions idle CPU usage is around 30-40%.

These figures are with wifi and bluetooth both disabled.

Display More

8.2.3 is the latest version and even that is from almost a year ago. Why are you using 8.0RC4?

Quote from eixel0505

Lucky I'm busy yesterday and haven't done it yet.

I run LE on my MX-III from internal emmc only. Android is completely gone but can easily be putback using amlogic usb burn tool if ever needed.

However I do not do 'installtointernal'

The way I did is by starting with Drieschel's build which gets intalled from sdcard to internal by default. And then upgrade it to Demtris' build using the standard LE upgrade procedure
Drieschel's build is from this thread

Quote from eixel0505

Hi,

I have a question. I'm loving Libreelex and want to completely replace my android installation, how to do it? TIA.

I think you do it by running `installtointernal` from command prompt

Quote from 5schatten

I added the controller file & the GUID so it should work out of the box in future builds. What games did you run for example? I only have an arcade set and this runs all games fine but there are no coleco games included.

Which games do you play and what emulator do you us

Basically try to run games in ES because the emulators tied to the systems should work. If you want to use RA check your es_systems.cfg in \\your-device\Configfiles\emulationstation to see what emulator is chosen for each platform.

I run all games under ES only. I don't start RA or any other emulator manually

I have relevant roms copied to the /storage/roms/<paltform> folder and they are sensed correctly by ES and I run from there

I have the following working correctly

Atari2600

Atari5200

Commodore64

MAME 2003

SNES

ZX Spectrum

I have tried these three but havent got it to work yet

FBA (Colecovision, Sega 32x&Megadrive, etc)

Amiga (the whole system hangs on launching amiga roms, have to powercycle)

ScummVM (may be it is not supported on the Amlogic build as it doesnt even shows under ES)

DonkeyKong and Digdug are colecovision games but they also work under MAME, so not a issue. However megadrive (Sega Arcade) is supported on FBA which I havent got it to work as the FBA core isnt running the roms on Amlogic. Will have to see if they work on x86

hybridr

Which core are you running under, I have tried under FBA but unable to get it work at all

Quote from 5schatten

So you've got a PS4 slim & the matching controller? Thats what your system detects:

So Retroarch would look for a controller with the input_vendor_id = "1356" & input_product_id = "2508"

I have no clue why your controller is not working the because there are already 3 config files with matching IDs. Maybe it's because the name differs

So you could try to add a file Sony-PS4-DS4v2-Controller.cfg to \\phoenix\Configfiles\retroarch\autoconfig with this content hastebin which is basically this one sony-playstation4-dualshock4v2-controller.cfg with different input_device name.

You can also try this: Dualshock 4 crazy-fast, repeating controls - Lakka - Libretro Forums then you need something like WinSCP and delete the files in /tmp/autoconfig before you create your config file.

Display More

I don't have a PS4, I bought a PS4 DS4v2 controller just to use with LE RR

Okay, so I had to do two things.
1. Edit the stock es_input.cfg and insert the codes for the new deviceGUID. This makes the controller work inside EmulationStation

2. Create Sony-PlayStation4-DualShock4v2-Controller-Bluetooth.cfg file and copy it to /storage/.config/retroarch/autoconfig/udev

Restarted the box and now the controller.cfg file shows up along with all the other controller configs in /tmp/autoconfig/udev.

And the controller now works perfectly inside both emulation station and retroarch with keyboard attached.

I have attached both files (had to add .txt for attaching, please remove .txt), so you can include them in the next release if possible, so the new DS4v2 controller will work out of the box for everyone

Thanks a lot for your patience and helpful instructions, it is now working great.

PS: in FBA core I tried with 0.2.97.43 ROMs but they dont start. I am just trying a couple of coleco roms. Do I need to put any BIOS file anywhere?

Quote from 5schatten

Have you all bios files? Atari - 5200 (Atari800) - Libretro Docs

Well I guess Sony made some changes so your controller is slightly diffrent & not recognized correctly. Can you reboot your system, log into a terminal & enter dmesg | paste then upload the link? I can try to check if they changed the vendor or product id.

Here is the dmesg output

http://ix.io/1vlz

Here is contents of bios directory

EDIT : I found a /storage/.atari800.cfg file. I opened it and edited the following line and added the BIOS files there. I have only shown the lines that I edited. Atari5200 emulator works after that

Quote from 5schatten

You have to start the atari800/5200 and set it to 5200 in it's core options. Start again & it should work.

Can you disconnect your controller and run retroarch just with the kb connected to see if it this works? From my experience not input is recognized at all if the controller cfg file is wrong mapped. Can you state your detailed model number of the controller?

Thanks for the quick response

1. Yes I have setup 5200 in the core options for the particular game. It still says no os rom. Will dig further and report back

2. Once retroarch starts, i switched off the ps4 controller, then kbd starts working and I could go into the quick menu and change controller 1 to retropad-analog or kempston or vice and then turn on the controller again and then both kbd and controller work.

The model number of the Sony Controller is CUH-ZCT2E

5schatten

I have installed LibreELEC-S905.arm-9.0-RR-201847-b559485-Beta16.img.gz on a Samsung EVO 32GB MicroSD and running it on a Wechip V5 S905X based device.

It boots fine and kodi works fine

I have a Genuine Sony PS4 Bluetooth Controller and that is paired fine with LE. I also have a usb keyboard plugged in

When I start Emulationstation it finds the ROMS and lists the platforms correctly. I have a snes rom, a sinclair rom and a c64 rom installed for testing.

In Emulationstation both the keyboard and PS4 Controller work fine.

When I launch any of the roms it fires up retroarch and runs the rom correctly, the music/sound is working fine.

However both the usb keyboard and ps4 controller dont work inside retroarch.

Please let me know what needs to be done to get the controller+keyboard working inside retroarch

Also please let me know where should I put the ATARI5200 BIOS files. I put them in the /storage/roms/bios folder but it still says "Atari800/OS Emulation Halted"

Thanks

Wechip Remote keymap

All 33 keys mapped.

The 4 blue keys on top are mapped as

Play/Pause, Mute, Rewind, Forward.

The X key next to 0 is mapped as STOP

Use Kodi community keymap editor to assign functions to other buttons such as TVPower, LED, KD, Mouse, and Globe

wechip.txt