Posts by chewitt

  • Xbox One Controller - Bluetooth

    Quote from LeannLL

    Will this be integrated into LibreElec later? Why does this have to be done?

    It cannot be default bundled because the "disable_ertm" property being set is global for all USB devices; and that may cause problems for other devices owned by other users in our large userbase that don't want that to be set (hypothetical but highly-probable scenario).

    The correct fix would be to ammend the upstrem kernel driver to set the property. Then the patch can be upstreamed; we can temporarily patch our kernel sources and later drop the patch when we bump the kernel to a version that already includes it. This requires someone to create and then usptream the patch though. Any volunteers?

  • Minix Neo-U1 rebooting on USB install

    It should work in any USB port really, although I find OTG ports are more likely to be powered up properly in vendor u-boot. The SD card slot should also work fine (checked before USB normally). The main issue from your description was pressing buttons after power-on; it needs to be pressed and held before power is applied, then released.

  • Minix Neo-U1 rebooting on USB install

    The editing uEnv.ini is not optional, and do not rename files to dtb.img like for legacy kernels. Use only the neo-u1 device-tree as others will likely not work. Use only the 'box' image as others are designed for emmc booting a specific board and will 100% not work with Android u-boot. Finally.. unplug power, connect the USB to the OTG port, press and hold the recovery button, then power on the box, and release the recovery button after some seconds. I've never seen a Neo-U1 myself, but from previous testing notes (which resulted in the current device-tree file) the recovery button is on the underside of the box (could be wrong though). If boxes have a power button, it's normally only a power button.

  • LibreELEC v10.0.4/RK3288.arm/ ASUS Tinker Board - WiFi problem on startup

    Code
    cp /etc/connman/main.conf /storage/.config/connman_main.conf
sed -i s'/PreferredTechnologies = ethernet,wifi,cellular/PreferredTechnologies = wifi,ethernet,cellular/g' /storage/.config/connman_main.conf
reboot

    ConnMan "prefers" Ethernet connections by default, so if you have both Ethernet and WiFi active (connected) it will always switch the default route to use Ethernet. If you run the ^ above commands (beware the line-wrap on the second one) this will switch the preference to WiFi so that when both are active the default route will be on WiFi. Is that better?

  • Official LE11 Test Images for Amlogic (Kodi-20)

    Quote from Masutin

    Sadly, no. Sorry for troubling you. The storage seems faulty. The installation starts as usual with partition resizing, etc. A reboot brings mount errors, need to exit, more errors (Kernel panic). Kodi may appear, but setting it up ends in (a need to do) a reboot. The final series of errors is failed services and dependencies. There may also appear a request to do a repair, but to no avail.

    I have tried several systems, new and old, with similar results. Alas, the attempts have ruined a working AE installation, seemingly irrevocably. Flashing the Android image doesn't produce a working system anymore, previously not perfect but possible. I'll ask elsewhere if there can be images to flash in Android Recovery, it works.

    Thanks for your help!

    Once you boot LE we've configured (overwritten) properties in the u-boot environment for LE filenames. To return to a legacy image you will need to force recovery boot again. This makes vendor u-boot search for legacy image bootscripts that will overwrite those properties with the info needed to boot legacy images again. It's fairly simple to flip between legacy and LE images; but it's not as simple as just inserting and removing the SD card, you need to invoke the recovery process. Restoring the original Android image will also reset things to a state where any legacy image (or LE) can hook u-boot and set things correctly.

    From the description: vendor u-boot does hooks LE correctly, the initial boot/resizing of the SD card completes, and you can reach Kodi. At this point you should have a working install. To isolate further issues I would avoid immediate installation of add-ons and just reboot several times to prove the initial setup is valid. If there are failed services they are likely minor things, but I would need to see a log file from the box: enable debug mode in Kodi, then reboot and run "pastekodi" one minute later and share the URL.

    Errors involving storage are odd. The upstream kernel doesn't understand the Amlogic custom partition scheme used to create filesystems on the internal emmc storage so AMLGX kernels will see a /dev/mmcblkX device with no visible partition scheme or mountable filesystems; ergo there will be no attempt to mount filesystems (and thus no errors from them). That means errors are more likely to come from the SD card, in which case the issue may be the maximum speed of the mmc device being too high (some boxes with lower-spec components need to force it to lower speeds to avoid instability). There are two ways to test that. One is using a device-tree file that forces 50MHz (not 100MHz or 200MHz) and the other is using an old slow SD card (not a fancy fast one) or perhaps a USB key (which is not an mmc device). Any chance of that?