Posts by balbes150

Version MXIII_Plus (20170606). Please test the 4k resolution TV.

I see that many may not know about additional features all the images LE.

1. You can install in the internal memory without using SSH. Enough after verification KODI from external media (if you are satisfied, all the necessary functions and hardware works as it should), choose off menu item "Reboot Install to eMMC". When you restart will automatically install LE in the internal memory (all erase /dev/system and /dev/data).

2. Can be placed in the root of the FAT partition (on external drive) the desired file to the remote control or rename existing (remote.conf). To test the system with these settings remote. If you then run setup (from the menu item "Reboot install to eMMC"), the system will automatically include this file settings remote control the setup process in eMMC.

Pay attention to the old staffing installation options using the SSH, and the location of the settings file remote saved and you can use those modes, which is used to.

For those who want to support the project LE, you can do it on the official site community Lebreelec.

mark2

Do I understand correctly that the image version Minix 20170605 in the list set visible and available WiFi hotspot ? If you try to connect to Wi-Fi TV box hangs ? You can connect to the LE via SSH and run multiple commands ?

To All

Pay attention - check to run when you run "clean" system (when running from external media). If you try to run through the upgrade of an existing system, very often the old settings interfere to determine exactly where the error is.

Added test image for Minix H8 Plus. There is only one change - applied the patch on the dtb. Surprisingly this version also works with WiFi and BT on my Tronsmart MXIII Plus. Please, Minix H8 plus check for this option (catalogue MinixH8XPlus\20170605).

I changed the settings and the files for WiFi and BT. Please to those who use image version MXIII_Plus to check the work WiFi and BT. I'm interested in the changes in their work (running or not). The image in the directory 20170605.

Quote from itsmeedoofer

What is the best way to update to the latest build, can I just add the image to .update ? Or is more needed because of the change to aml_autoscript

If you have version 17 with KODI you can use a normal update file .tar. Update multi-boot with need for those who have problems running from a USB (when you have to disable all USB devices for the successful launch of LE).

The test version for H8X_plus.

Yandex.Disk

Quote from smashi

minix x8-h:

Have you tried the option LAN100 ?

Quote from xbmcking

Should we also update s805_autoscript to resolve above issues ?

The script does not affect the work LE, he is responsible only for running external drives. So the update will not help.

Have you tried to start the system from external media (which would not interfere with the old settings) ?

Questions to the owners of Minix H8Plus (s812)

1. Do I understand correctly that when running on Minix version (20170602) MXIII_Plus wired network works, sound and video works, WiFi doesn't work. What with BT , working or not, the adapter is enabled in the settings ?

2. How the system behaves from the image LAN1000 on Minix that works in this manner (wired LAN, BT, WiFi) ?

Similar questions for owners of the model Minix H8 (s802).

You need to activate the new option of multi-boot (using the files that are included in your new way). Now you have enabled the old scheme, which can only run older images.

bootcmd=run startfromext; run storeboot

This line should look like this

run start_autoscript; run storeboot

LibreELEC.tv/aml_autoscript.src at Amlogic-Krypton · 150balbes/LibreELEC.tv · GitHub

Quote from ilikenwf

Nope, doesn't work on the bcm4335 model. Multiboot works in that LE tries to start, but mmcblk0p1 isn't being mounted as /flash (something else is) and so the SYSTEM image isn't available automatically.

1. What is your model of TV box ?

2. Show me the output of fw_printenv from a running LE system (console of SSH).

3. What version of Android was used (from which firmware version 4.4 or 5.1 you have u-boot) ?

Now I use the day time to help work on porting the kernel 4.x for S812 . Perhaps then I can return to the issue of support for WiFi in Minix. The main problem in this issue - I don't have that model so have to do everything at random and without verification.

Quote from James Greystone

2- Minix X8-H Plus with MXIII_Plus was getting random system lockups, LAN1000 for last 6 hours no freezes and no lockups. Strong and steady

Thanks for the hard work on these builds.

Have you tried the latest image MXIII_Plus ?

Quote from ilikenwf

balbes150 so, I've built your latest 17.3 and now have gotten it to partially work with my bcm4335 S812 M8S. I am using a patch that adds the dts file from the stock android.

Steps:

1. Rename s805_autoscript to aml_autoscript
2. Manually mount /dev/mmcblk0p1 and then mount SYSTEM to sysroot (how do I automate this? I'm not new to Linux but am new to LE), exit, and then boot

Playback and wired networking appear to be working perfectly, wireless networks did not appear in the setup menu but the interface appears to be working, which is strange...

I also need to get the remote.conf from my stock android as the volume buttons don't currently work as well.

Video and audio quality appear to be be better (much better) than they were in Android. The strange thing is that these boxes' dts files say they are 1G devices, but then the android kernel shows 2GB at boot - think it may be some kind of Chinese knockoff thing there? My only other guess is that perhaps half of that is saved for vram?

Help me get the boot mounts setup and I can put in a pull request.
Work in progress: this seems to add proper working support for the bcm4335 m8s, mostly,… · ilikenwf/LibreELEC.tv@c05fc84 · GitHub

Also, hypothetically, if I wanted to get the retroarch stuff working, is it just pulling that stuff into the build, or does it go deeper than that?

Thanks for all your work!

Display More

If you used my GIT, you do not need to rename the script s805_autoscript. Leave it as it is. Activate the multi-boot and the system should normally be run by itself. Pay attention, the activation may be performed once and necessary SD card. Ie You need one time to record your image on the SD card. Use the update mode from Andoid or method of a toothpick. Once you upgrade bootloader, you can use to embed LE any USB flash drive or SD card.

An updated version of the image MXIII_Plus 20170206. Pay attention, changed the numbering of the images. Changed the script activate the multi-boot and system start up. The new script allow you to start the system in the presence of simultaneously connected multiple USB. For new scripts, you must re-activate the multi-boot using the new script aml_autoscript and use the new script s805_autoscript. These scripts can be used with old images. Updated the script activate the multi-boot boot.src Minix Neo H8.

Quote from doggyofone

thanks for updating the S812 with Krypton. A question for you, I am running an MXIII-G with Wilro's LE 7.0.1c. His install method included a step where his aml_autoscript was flashed and enabled multi-boot. Dual booting works well with his script.
This was the original post for his rom - http://freaktab.com/forum/tv-player-supp...mart-mxiii
The question is will I be able to flash your LE rom via the toothpick method using his aml_autoscript, or should I go through the process of flashing your aml_autoscript and aml_autoscript.zip?

Need to reactivate the multi-boot.

Quote from Arcee

About the Wi-Fi issue on the Minix X8-H Plus, why not check this (old) forum with a discussion on how to get Wi-Fi working on this box?
http://www.minixforum.com/threads/openel...plus.3342/

From what I read there, the Minix X8-H Plus has:

WIFI CHIP
Broadcom AP6330

There are also some links to drivers. Too technical for me, but maybe of use?
Based on that discussion, a working OpenElec build for the Minix was compiled.

Thanks for the links, I will look at them.

Quote from James Greystone

I turned off the box inserted sd card then put a paperclip in the reset.
Turned on box and when green logo appears released the power button then released paperclip.

The box then booted normally and the next time I turned it on if the sd card is in the slot it boots to the liberlec from sd card.

If I remove the sdcard it boots from internal memory.

The image from May boots no problem, but the newer images give the error.

I have tried to get a usb to boot with the same method but it will not.

I have tried both USB slots, but it always boots from internal memory.

Display More

You created on the SD card the /boot directory, and suffered in his boot.scr ?

Quote from atomizasser

Yes.
I'be tried different SD and it doesn't boot. After minix logo stuck in a black screen and not loading.
I've tried a MXIII plus image and start fine, but wifi is not stable: sync clock but i cannot connect to kodi respository.

The latest version of the Minix image behaves the same (does not start) ?

Quote from James Greystone

Playing around wit this I discover that if I take the Kernel image from the working image from April and use it on the images from May the boot proceeds.

This may not work because the kernel may not have the overlay of the last patches (which may be invoked by other components).

Quote from atomizasser

I've tested on Minix X8H-Plus and it doesn't boot. Appears a message saying "filesystem is corrupted" and turn off after 120 seconds.

Are you using SD card ?

1. Updated test image for Minix (20170514).
2. Question to those who uses the image MXIII_Plus, please compare how it will work the way LAN1000. Is there a difference in behavior. I want to leave one of these options. I have both work the same.

Quote from James Greystone

Unfortunately I haven't been able to get this Minix to boot from USB, and had a lot of different suggestions to try.

That is why I bought the sdcard which seems okay. The 04 file boots okay though. Odd

Write what steps you did to activate the multi-boot.

Quote from ilikenwf

Just an FYI, I can't get anything except the n200 AP firmware to work...

n200 and n200C a different platform

Quote from mark2

i opened system folders and the Minix bcm is showing as bcm 4339 not 4335

Then it turns out You module 4339 this WIFI module AP6335 (bcm4339) ?

Quote from James Greystone

Tried the new 05/13 file. unfortunately same error when booting starts then says corrupted file.

Use a USB flash drive.