Posts by dtech

Quote from elecplay

Hope that gives you some more clues, dtech.

Well, I'm more clueless right now than I used to be.

Quote from elecplay

Let me know if you need anything else from me, dtech!

Okay, this is really an AP6210, interesting.

Could you also send a dmesg from my 9.2.6 build? I wonder where it gets stuck.

Quote from jim_p

Can I use that too on my mxqpro 4k (device tree gxb_p200_1g)?

Omg, I feel like Obelix asking for a sip of the magic potion

Dear Obelix,

You can use it, but the signal strength of your wifi won't get better.

However, if we are already here... With kszaq's 8.2.3, what was the signal strength of your wifi? Better or similarly bad?

The question also applies to the S905 and S805, of course only if you have tested with this version before. If not, consider it irrelevant.

Gammeto

The new 9.2.7 image is ready for the test: LibreELEC-MXQ-4K-Pro_2G.arm-9.2.7.img.gz

Please use the previously linked dtb and remote.conf for this image.

Quote from elecplay

Thanks for the new MXQ-S805 build, dtech!

Unfortunately, bluetooth still doesn't work with this build on the MK808B+. Any other ideas?

Okay, I need a dmesg under 8.2.3 because now I'm not sure you have an AP6210 in your device.

And then, one more thing ...

cat /sys/class/net/wlan0/device/vendor
cat /sys/class/net/wlan0/device/device

Quote from Gammeto

This is really true now the remote is working, thank you dtech

Will you make a device tree for RTL8723BS wi-fi ?

The reason for the non-working wifi is not the dtb, because this driver is basically missing from the image.

I will include it in the next release (9.2.7), but it’s a good question when I can make it, because I should solve the Widewine issue before I release it for S905.

Edit: restore previously removed wifi drivers and firmwares · dtechsrv/LibreELEC-AML@aeb4c61 · GitHub

RTL8723BS Wireless LAN 802.11n Network Adapter

We are moving forward.

Quote from jim_p

Oh ok. I am staying at the previous image because my mxq is indeed all black.

I will try to update the Realtek WiFi drivers later, but now unfortunately I am struggling with the Widevine CDM issue.

I successfully migrated version 9.2.7 (officially released exclusively for RPi devices) to 32-bit only S8X2 devices, but for some reason it doesn't really want to work on the 64-bit S905 branch.

Quote from jim_p

I already have a working (and configured) installation of le 9.2.6 on my (s805) mxq from your images here.

Index of /S805/

Is it worth doing a fresh install from the images you made today? I assume I can back up my current configuration and restore it when the new image is installed. I am interested to see if it solves the the wifi connection issues I have (message 74).

This image is not made for the MXQ "all black" boxes (HD18Q/m201d), it is for the MXQ-S85 (which has a red "MX" stripe and a button on the top) and the MK808B+ only.

Otherwise, this image only affects Broadcom wifi/bluetooth drivers, so unfortunately this may not solve the signal strength issues with Realtek chips.

Quote from elecplay

Thanks for looking into this, dtech!

If you need a hint, kszaq's MXQ 8.2.3.1 build has bluetooth working for the MK808B+. See RE: [8.2.3.1] LibreELEC 8.0 for S805

I made a new image that already has the correct remote control config.

I restored the original wifi/bluetooth stack so this version should be checked to see if it works:

Index of /3rdParty/S805-LE-9.2.6/MXQ-S85/

Quote from Gammeto

Hi dtech - the dmesg log - Untitled in plain_text (s35bms77qe) - PasteCode.io

Please notice and remote control, because I have problem with remote too, I try to make own remote.conf but when I press a key nothing is logged with "dmesg –c"

Unfortunately, dmesg doesn’t tell us anything about the wlan interface.

Please try this under LE 8.2.3:

lshw -C network

... and this:

cat /sys/class/net/wlan0/device/vendor
cat /sys/class/net/wlan0/device/device

However, dmesg revealed the configuration of your remote control.

You need this: remote.conf

Quote from Gammeto

Thank you dtech i tried with this tree, the box starts, but have only wired /lan/ network, wifi and remote control don't work. I copied remote.conf from http://remote.conf/4040-m8s and paste into storage/.config folder, but the remote doesn't work.

When I use build 8.2.3 of Libreelec with the same device three have not problems with wifi and remote control.

Can you give me advice or help me. Thank you in advance.

If you still have LE 8.2.3, I would need a dmesg.

Somehow I should identify the wifi because it could easily be that you have a wifi chip that is missing from the image.

Quote from elecplay

Just to confirm, I rename this file to dtb.img and copy it to my SD card right?

If so, when I go to "LibreELEC - Bluetooth" - it says "No bluetooth adapter found." So it didn't work for me on my MK808B Plus. Let me know if you want me to try again with another dtb file.

Okay, I'm investigating this because I don't know which wifi/bluetooth chip is in the MK808B+ device.

Quote from mega-samu

I just tried and not, the Bluetooth does not work.

Please try with this DTB: m8b_mxq.dtb

Quote from Gammeto

Dtech = thank you for answer, but for the older build of Libreelec I used device tree gxbb_p200_2G_100M_RealtekWiFi because the lan of my Mini M8S is 100 mbit, if I use S905-LE-9.2.6/MXQ-Pro-4K_1G may be I will have problems with network, if it is possible can you tell me where I can download device tree gxbb_p200_2G_100M_RealtekWiFi for this new release.

gxbb_p200_2G_100M_RealtekWiFi.dtb

Sorry for the late reply, I'm pretty busy lately. I will try to answer the questions raised.

Quote from Gammeto

I try to install this build on Mini m8s, but the network and remote control doesn't work, can you give me an advice which build to use for my tv box ? Chipset is s905

You need to try this one: Index of /3rdParty/S905-LE-9.2.6/MXQ-Pro-4K_1G/

If you find your own remote control among these, you can install it according to the description:

Index of /remote.conf/

Quote from jim_p

TIL that this command returns the device tree for used by each device.

Code

cat /proc/device-tree/amlogic-dt-id

...

Are they correct?

This command reads the ID from the header of the loaded DTB, so if a bad DTB is loaded, it will also read the wrong ID.

So unfortunately it does not tell you exactly the type of device.

Quote from elecplay

If the H18Q build doesn't support bluetooth, then perhaps dtech can make a build that supports MXQ, I read an older LE8 MXQ build has bluetooth working: RE: [8.2.3.1] LibreELEC 8.0 for S805

I didn’t say Bluetooth isn’t supported, just that the HD18Q doesn’t have a Bluetooth chip. You should test to see if it works because Bluetooth support is present in the build.

Quote from ElecUY

Hello dtech, thanks for this image to revive my M8s box after so long. I tried it and everything seems to work normal except the remote control which is not one of the most common but I can live without it. I also did not test the ethernet but it probably does not work because my box is a 10/100 and the image is for the M8s + that has 100/1000 but the wifi works correctly. What I am interested in is installing emulators but they are not available when I go to install them for games, the only options that appear to me are Independent games, controller profiles and game providers. Can this be corrected? Sorry about my English, I had to use the translator. Greetings

99% that your Ethernet works, even if it's only 10/100.

My own set of remote controls can be found here, maybe yours is among them: Index of /remote.conf/

Unfortunately, the games were not included in the support because they take up a lot of space during code compilation, so I was forced to skip them. If you need games, unfortunately you have to compile it yourself from my GitHub repo.

Quote from Kekq

Thank you so much for this,

Revived my first tv box, an Amlogic s805 that I could not find working roms for!

Thank you for your feedback.

Quote from jim_p

On the box, when I try to install almost anything, e.g. a skin or an addon from the main repo, I always get the message that downloading failed after a while.

It was my fault, I forgot to add the device to the list in the repo, so you couldn't even query the file list of the LE's repo. I've fixed this, I'm sorry about that.

Unfortunately, I have no idea about the instability of wifi yet, but at least it already means something that works at the kernel level.

Quote from jim_p

Don't ask me where the wifi card is

Okay, then it is not USB, so I need a dmesg if it is possible.

Edit:

I created an image with multiple Realtek wifi chips enabled:

Index of /3rdParty/S905-LE-9.2.6/MXQ-Pro-4K_1G/

Quote from jim_p

Wifi is a major issue for me Hdmi cec seems to work on that one, installation on the rom does not (as you mentioned, I have not tested it and I am not willing to) so what else shall I test?

Ce on the 905 works as it should with no major issues, but I hesitate to install it on the rom.

So, now I ask the question:

Are you interested in an LE image that can be installed on NAND on your MXQ Pro 4K (which also has working a wifi driver) or not?

Because if not, then I'm not going to struggle with the image, and in that regard, I will leave the fight with your stuff and move on.

However, if you are interested, then I need an "lsusb" output under CE, because we still haven’t clarified exactly what wifi chip is in your S905.

Quote from jim_p

So I found an sd and tried your build of le 9.2.6 that you mentioned. And as you predicted, wifi was not available at all.

What can I do? Maybe use a different device tree?

No, this is not a DTB issue as most Realtek wifi chips are connected via USB, so those are like external wifi interfaces.

I previously removed support for these from my S8X2 and S905 images to make the disk image smaller, but I didn’t really gain much with it, so I’ll be back on them soon.

However, did you find any other problem with the image besides the wifi issue that will be fixed soon?

cecconfig=cec0

This "0" in your uboot config for CEC means that is turned off.

You need to try this:

fw_setenv cecconfig cec1f

... and then reboot.

If that doesn't work either, make sure your TV has CEC enabled on the input source you are currently using, or try another HDMI cable.

After that, a solution may be to go to Settings/System/Input/Peripherals/CEC Adapter -> "Reset above settings to default" and reboot again.