Try xrandr command.
xrandr won't work with Amlogic.
Posts by kszaq
-
-
The new firmware worked better with 2.4GHz (slower but still usable) , but with 5GHz the performance was much worse to the extend of unstable SSH.
My tests with 802.1ac 5GHz WiFi, device standing 15cm from the router, iperf3 over TCP to a wired NAS:
- new firmware, old driver: ~50Mbps
- new firmware, new driver: ~180Mbps download, ~110Mbps upload
Can I use the micro sd card that is in my x96 box in the mini m8 boxes because it has the same specs (905x 2gb/16gb 100mbit) or will this not work?
Yes, you can. Even if you have a bit different device you should only replace device tree and it should work. I am doing this all the time.
Just one question - how can I emulate the sms type letters behaviour on the remote keypad (e.g. pressing "2" gives ABC) as I find this invaluable when scrolling through my several hundred ripped movies.
I don't know, maybe better ask at general support or Kodi forum? The letters work with full-screen keyboard, not sure about movies list.
-
You can extract recovery image from ZIP file with Android firmware.
-
After a new boot via toothpick and SD with correct dtb I've tried to fix but now the box doesn't start neither with SD and toothpick method and displays always "no signal". Any idea? I don't want completato format the box.
If even the first logo doesn't show I'm afraid you can only bring the box back to life using USB Burning Tool.
Today I downgraded to 8.1.2 and have not experienced these issues since. I suspect the updated WLAN firmware in 8.1.3 to cause these problems in my setup.
Maybe you could revert the update in the next build (I don't know if anything important is included in the new firmware). If there is anything I can do to help, let me know (I was not able to spot anything in the logs (kernel nor kodi)).
Hm, the updated firmware is indeed slower but certainly not unusable. I will try to fix this and I'mm revert if unfixable.
Edit: It looks that the updated firmware works much better with an updated kernel module. I will include it in 8.1.5.
I installed on an Odroid C2 and could successfully install a custom splash screen (LE splash, not KODI), but how does one do it for a 905x android tv box? Any instructions for custom splash for the same? Cant see anything that I can change in the 'libreelec' partition.
There is no "file" with logo on other boxes, there's a dedicated partition with logo in custom Amlogic format. Try to look it up at Freaktab forum.
Also, the oem remote that came with the box seems to be working and powers on and off the box too. Is it safe to shut down the box this way without selecting 'Shutdown' in Kodi?
Yes, pressing the button does the same thing.
-
^
just a quick one, in terms of licensing why is s905(x) different than s912? because s905 seems to be fully supported by LE.
S905(X) has an older generation GPU with supposedly simpler licensing terms.
-
Device trees folder is always linked in release thread below system image links.
-
All S905(X) devices use the same driver ("adapter"), there is no possibility that one of your devices needs something different.
Things to check:
- device tree
- HDMI cable
- you can try using one of my builds
It's also possible the board of your box is broken. Does CEC work in Android?
-
gxl_p212_2g.dtb is embedded in SD card image, so there's no need for replacement at this point. You will need the device tree later - when advised to use it during an upgrade.
-
No changes in video playback between 8.1.3 and 8.1.4. For any playback issue you have to provide a sample.
-
8.2 builds use Amlogic Nougat kernel which basically means better HDR and fractional frame rate support. There is a note in 8.2 thread what you need to do to make it work if you're upgrading (hint: device tree!).
One more thing: 8.0.x will not be updated.
-
I tried to update from 8.1.4 to 8.2 test and i'm stuck on the LibreELEC screen and it doesn't boot.
The latest test version has not been compiled for the C2,
-
Ok, so basically if I run once an SD with Libreelec, the boot process is modified such the SD is always the first boot medium, even if I "reboot from internal" is selected, or if I am running Libreelec installed on internal, right?
"Reboot from internal" option is there to bypass booting from SD one time. After you perform LE "installation" (reboot with toothpick etc.), boot order is as follows:
- Look for kernel.img at SD card and boot it if present. Use dtb.imb from SD card or /dev/dtb (internal memory) if not present on SD card.
- Look for kernel.img at USB drive and boot it if present. Use dtb.imb from USB drive or /dev/dtb (internal memory) if not present on USB drive.
- Boot from internal memory.
Source script for this: LibreELEC.tv/aml_autoscript.src at libreelec-8.2 · kszaq/LibreELEC.tv · GitHub
Sorry to bother you, but one extra question: when the SD is looked for first boot, also a recovery.img (like TWRP) is launched if present, or only dtb.img and kernel.img?
No, this is done if you press "reset" button or choose "reboot recovery". Basically the same procedure as above except that u-boot looks for recovery.img and aml_autoscript before it. Example source (note that manufacturers tend to modify it): u-boot/gxb_p200_v1.h at Nougat · khadas/u-boot · GitHub
Is this 3D fix test build teh 8.1.4 version with the 3D fix by the way ???
Yes, you can safely use it as a daily driver. The fix will be included in 8.1.5.
So grateful to you kszak. As I now have a few coffee beans in, I am just about to send you a nice well deserved cuppa.
Thank you so much - as always.
I really don't known where NAND crept into the AML S905/S905X thread because most S9xx devices actually use the faster eMMC storage.
Yet there are still devices using NAND. I wish there weren't, I'd be able to drop the NAND driver blob.
Where can I check which resolutions the TV report?
cat /sys/class/amhdmitx/amhdmitx0/disp_cap but this info might not show this resolution. I've added the patch to test it later myself, not sure how it works (yet).
-
If you play HDR content with a hardware that doesn't support HDR you shouldn't expect it to look properly.
-
As far as I understood, the a905x uboot boots from SD only when the board is reboot in recovery mode
So, if you install Libreelec in internal NAND, you actually are exiting from recovery mode, so uboot will always try to boot from the internal NAND (application partition and not recovery partition where you have the original recovery or where TWRP will get installed eventually).
Not true. You need to make your box boot once into recovery/update mode to execute aml_autoscript that modifies "normal" boot procedure and makes the box go back to "normal" mode. The script makes your box look for kernel and dtb on SD card before booting from internal. If you install LE to internal, the box keeps doing that, so if anything goes wrong with internal installation, you can still boot from SD card (unless you reset uenv). I will try to add this explanation to HOWTO at some point.
kszaq do you have any docs explaining in the details the boot sequence of the a905x as implemented in these Android TVs?
None that I know of.
I'm not sure how I do that. Does it require soldering something to the board?
You don't have to solder - I am using a "pogo" cable to connect a USB-to-Serial adapter:
-
Hi. not sure if that patch was to fix the issue I was having with it hanging on the Mecool logo but it hung again on the second boot after flashing.
Open a new thread and attach a log from serial console.
-
I am not acquainted "in-depth" at all what the installtointernal procedure actually does,
and if LE installation is overwritting the Android recovery partition,
but, according to section from the [HOWTO + FAQ] Install community builds on S905/S905X/S912 device
for the revert procedure you'll need the Android recovery image, so I guess it does.
Probably, for the revert procedure - you can use the TWRP image, instead of the "original" ROM recovery one...
No, my builds don't replace recovery. They replace device tree, that why you need recovery + dtb on SD card.
-
I will test it when I will come back home, I have a TV with the native resolution of 1360x768, actually where I also have the no splash issue
1360x768 support is only added in Kodi to confirm whether it works or not, 1360x768 splash resolution is not yet supported.
But I can only check if it fix the problem, when I upgrade starting from this build right? If so, can I test upgrading from this build to itself?
Upgrade from any other build.
kszaq Can you please also help me with a question I placed yesterday: if I have a box without the reset hole, how can I recover from SD if I semibrick it loading a corrupted or buggy image in internal NAND?
I don't know.
-
Bruur This WiFi chip (SSV6051) is not supported in my builds.
