Posts by dtech

Quote from vasonline

Why not put 576i wdescreen in there? hmm.

Is the 576i not the same as the 720x576i50? Because its ratio is still 4:3.

The correct resolution for 16:9 would be 1024x576i50 if we do not reach the height value, but I don't think it will provide a signal with this resolution on CVBS. A try will tell you.

Quote from oceanzhang

I’d like upload ap6335e_nvram.txt late. Hope it will be hopeful

Thanks, but the file is already included in the brcmfmac_sdio-firmware-all-aml package as well.

I'll check it out, but I would ask you for a little patience, because an HDD from the RAID1 array died on my server yesterday.

Until it is replaced and re-synced, I don’t want to build a new image.

(It will still be an emergency intervention, mainly because of the virtual machines and I don’t want data loss.)

At the same time, I predict to everyone that http://http//libreelec.dtech.hu/ and my LE repo will not be available for a couple of hours on Saturday.

Quote from vasonline

Confirmed with a LCD TV using the composite input. It is the same. We have a 4:3 output on 16:9 TV.

Well, I may not have anything to suggest.

I have tried to look for this error here in the forum or on the internet only in relation to Kodi, but I did not find anything relevant.

Quote from oceanzhang

Okey, Try this dmesg.txt

That's good, thank you. I noticed something...

The image for M8S+ uses a different nvram configuration (ap6335_nvram.txt) than datrh's X8-H Plus image (ap6335e_nvram.txt).

However, my X8-H Plus image statically loads "ap6335e_nvram.txt", so I don't really understand why it freezes.

Quote from oceanzhang

Okey, this dmesg from datrh version.dmesg.txt THX

Unfortunately, startup events are now completely missing from this log.

The first line is this:

[  665.570576@0] remote_send_key sleep:0

Please send one immediately after start-up, before pressing any buttons on the remote control.

Quote from Ionman

I don't suppose your build would include the SPDIF multi-channel audio device (last seen in official LE in 8.2.5); [8.95.3 Wetek Core] Missing multichannel audio output ????

My build is based on 9.0.2, so if it didn't work there, my image probably won't work either.

But I never had a WeTek Core, so I can't test it. I made the image on request, but it seemed to be a waste of time.

oceanzhang

I would also like a dmesg from the datrh version.

vasonline

Unfortunately, newer LG OLED TVs no longer have any analog inputs installed, so I can't try it now.

But this weekend I will also try the CVBS output with another TV. (16:9 LCD with composite input)

Quote from bumerc

It is only a help for those who want to restore their device. Fantasies about advertising are superfluous here my friend.

Okay, but then I don't understand that if we already have a working firmware specifically for this box (KI PLUS S905D 1G 8G DDR3 LR), why would you suggest another one that was made for a completely different box?

At the moment, it seems that there is something wrong with the USB A-A cable and not the firmware is causing the flash error under USB Burning Tool.

I think the firmware you are proposing should remain Plan B for now, and let's not start with that first. At least that's how it makes sense.

Quote from hudyj

Amlogic burning tool still showing error with all images, also yours.

[0x10105002]Romcode/Initialize DDR/Read initialize status/USB Control setup error.

in UART unchanged : GXL:BL1:9ac50e:a1974b;FEAT:ADFC318C;POC:3;RCY:0;EMMC:0;READ:0;CHK:AA;SD:0;READ:0;CHK:AA;USB:8;

I think you should get a factory USB A-A cable instead of a DIY cable.

Quote from bumerc

The ATV ROM I posted already includes the correct WiFi driver and fw. 1g eth has nothing to do with installation for the time being, the TV box would also work without eth.

I don't care which firmware can hudyj flash to the device, the point is that EVERYTHING should work on the box. (Ethernet too!)

Quote from bumerc

He could try to install this FW first via the sdcburn method, it is for lpddr3 devices. At least the bootloader should be running. I could add 1G dtb later..

Please keep in mind that this is the LibreELEC forum, so this is not the place to advertise your own Android creation.

Quote from hudyj

same, many loops.....

Now you just plugged in the UART and got this output, or did you even manage to flash the image I linked earlier?
Because what you copied from letter to letter is the same as what creited copied in the first post.

Quote from bumerc

try this FW

I don't think the image for the KI Pro would work because KI Pro has Gigabit Ethernet and Broadcom/Ampak wlan chip.

If the PCB ID is the same (KI PLUS S905D 1G 8G DDR3 LR), it should work with my image (KI_PLUS_S905D_v4_OTA-REPACK-20180815).

Quote from oceanzhang

finally I got wifi working with datrh‘s LibreELEC 9.0 / Kodi 18.X for Minix X8,X8H,X8H+ .

Would you please take a look device config ? THX

Okay, but you linked a topic, not an image.

I'll be honest, I've never encountered a widescreen CRT television in my life.

Try setting the standard mode to expert in the Kodi settings, as some new options may appear.

It is possible that this can only be solved by stretching the 16:9 aspect ratio image first vertically with Kodi and then horizontally on the TV, but this will definitely cause image distortion.

(Has there ever been a standard widescreen analog resolution?)

What resolutions did you put in the disp_cap file? Can you copy the contents of the file to a code box?

Quote from oceanzhang

thank you for your quick reply

a. I set le work at 1080@50p, and then I play a 4k@24p video. On the tv, input source is 1080@24p. Odd

b. dmesg.txt

Also, I tried different img

MXIII+ no wif

H8X+ random frozen after wifi connected (ap6335?)

Display More

Under Meson8, handling UHD resolution is not really properly resolved. I'll be honest, I didn’t really struggle with 4K either.

Since HDR10 is not supported by the SoC, I didn't see the excessive sense of dealing with it.

Unfortunately, I can't suggest anything for WiFi instability.

However, it is worth noting that the M8S+ and 3rdParty images use different broadcom drivers.

Quote from vasonline

Question: Would you be so kind to make a version for the Amlogic 905D with 1G ram / 8Gb eMMC too?

I didn't really plan to create more images on the 905x device branch.

The biggest problem is that Mecool's "M8S-Plus DVB" device has a WiFi chip (SCI 9082C) that was never released a driver by its manufacturer, so support for this chip is not resolved from the open souce side.

The other thing is the tuner, in which I’m also not sure it works perfectly.

However, you can try my image for KI-Pro from an SD card by replacing the dtb with this:

gxl_p231_1g_dvb.dtb

Quote from oceanzhang

a. when play a video, auto rate change work, but not resolution switch automatic

b. wifi connection unstable (ap6335)

a. What is the resolution and cadence of the video you are trying to play and what is the currently set resolution and frequency of the device?

Note that Kodi does not change the resolution downwards, so it will play 720p video at 1080p if the currently set resolution is 1920x1080.

However, playback will be cadence correct, so the frequency will be the same.

b. Can I request a dmesg?

Quote from oceanzhang

After 100 times test. It has most function work. But I can't switch resolution, no matter I change to 720p/1080p, TV still shows input source 1080@60hz

Do you have any idea? Thank you

Try to add manually supported resolutions:

Thread

how to work without EDID ?

If I will activate CEC with my wetek play + AVR + TV, then avr and TV will switch on after wetek load. And resolution from wetek will be not correct 720p) because wetek couldn't read edid from TV and use 720p as default resolution. How to write in any config files that the default resolution should be 1080p@50 Hz ?

Goga777

September 12, 2016 at 7:13 PM

I see two mistakes on your photos:

• The 3.3V pin of the device is never connected, especially not for the 5V pin on the TTL adapter side.
  This pin is only used to power the TTL adapter, but it is actually already gets it from the USB port.
  However, it can be dangerous for the device if 5V is applied to pin 3.3V of the UART.
  (See illustration in post #6 -> the 3.3V pin is not connected.)
  Solution: Please desolder the red wire from the KII Pro.

• The Windows driver installed for the device is not compatible. (See the yellow triangle.)
  There are a lot of fake Prolific TTL adapter ICs that are not supported by the official driver.
  Solution: You must install the driver recommended by your seller, or if it does not exist, you must request one.

But, if the IC is a real one, the exact type is also important. Please download the PL2303 CheckChipVersion tool and check your chip ID.

For example, mine is:

Quote from jim_p

In order to make the mxq's remote work, I had to "install" some configuration (?) file for it. I can't remember its name or where I found it. Do I have to do it again after the upgrade?

The update does not affect the user files, all your own changes remain untouched, only the kernel and the system file (squashfs) have been replaced.

Quote from oceanzhang

OK, mkbootimg_tools can make it work.

Okay, I hope it really works. I almost reacted to your previous answer, but in the meantime you modified it.

I hear this sadly, I hope your other devices have not suffered harm.

I looked at the pictures taken from the PCB:

[v7.5] Aidan's ROM [S905X] [ATV 7.1.2] (Lag & Bloat Free, Pre Rooted, Samba & Miracast) [TV NETFLIIX] 2021 Update! | Page 31 | XDA Forums

This version has 4 x 256MB of memory, which is relatively rare solution. (The 2 x 512MB solution is the most common.)

Most likely this is why most bootloaders are not good for this specific model.

We should look for stock ROMs that have the same 4 x 256MB layout.

The functionality of the MAX232 IC can be tested by connecting the RX and TX pins together and typing a character into the terminal.

If the typed character does not appear or only noise is displayed, then the reasons may be as follows:

• the power line is broken: Vcc is missing or GND is floating (broken wire),
• the voltage is unstable or lower than +5V,
• the Maxim IC is faulty.

If the MAX232 receives Vcc voltage (+5V) and the GND pins are also connected between the power source (such as USB port) and the other devices (RS232 pin 5 and the GND on the UART port of the box), the converter power should be OK.

If the bootloader has been overwritten (or just erased its area), I have a strong suspicion that we will not get anything through UART.

But I have never met one like this before, so I don't know for sure. I think chewitt has more experience with this.

At what percentage does the USB Burning Tool stop?

Quote from 'Amlogic Platform USB Burning Tool V2 User Guide - Revision 1.0.pdf'

Progress bar percentage:

• 0~2%:
  During this stage:
  1) If erase_bootloader is selected, then erase Bootloader and reboot.
  2) Initialize burning environment and get the icon resources etc., from burning package.
  ! If burning fails and stay at 2%. It means flash initialization fails!
• 2%~5%:
  This stage is for flash initialization. If erase_flash is selected, it will also erase flash.
• 6%~94%:
  This stage is for burning the data partitions except for Bootloader. If the progress bar stops here, it means partition burning fails.
• 96%~98%:
  This stage is for burning bootloader.
• 100%:
  Burn successfully.

Display More