If anyone has a similar box, or knows where to get a 100% identical one, please let me know.
Posts by dtech
-
-
Broken something when reassembling heat-sink, board won't boot, have to check if fixable in the spare time.
Can't test the image right now.
Oops, that's not good news. I hope there was no short circuit or similar.
-
I think that's behind the marketing idea: bigger is better...
I think the manufacturer simply has a bunch of empty MXQ boxes that they haven't sold before. By the way, the "5G" label on the box is also strange because the RTL8723AS only works on 2.4GHz. So it's the usual Chinese industrial scam again. I haven't been surprised by this in a while...
Meanwhile, I found an obvious error in the driver that I hadn't noticed before. I fixed this, please try this new snapshot version:
Index of /snapshots/20230515_rtl8723as_67db88d/
You should probably boot successfully with this image, but even if the wifi is working or not, I would ask for a journalctl | paste output.
-
Well, the manufacturer saved a lot of space, the PCB is quite small compared to the size of the box.
How to access the uart? there are pins on the PCB?
The unsoldered 4-pin header behind one of the Jack connectors looks similar, but I'm not sure it really is.
-
I just enabled passthrough but nothing changed. The GUI volume has always been set at 100%
If passthrough is active and the correct output and currently used encoding are enabled, it doesn't matter what volume is set under Kodi, because then the incoming bitstream is passed directly to the output without processing.
Edit: Okay, wait a second...
^ You didn't set this to 100%, did you? Because this is only the volume of the system sounds, not the master volume.
You can adjust the master volume of Kodi using the +/- buttons on the number pad.
Of course, with passthrough, this will have no effect, unless you only send basic PCM audio.
-
Thanks, it is AS and not BS. I have misunderstood vid and pid, now I've checked the chip by removing the heat sink.
Could you send some photos of the PCB?
Testing the provided image I've found that Kodi starts in safe mode ...
That doesn't look promising, it usually happens after several unsuccessful boot process. It's a shame I would have asked for some kernel log, but that way you could only extract anything meaningful from the UART.
-
Please try this snapshot image:
Index of /snapshots/20230512_rtl8723as_9b693a0/
Bluetooth probably won't work, but wifi should hopefully start with this driver.
Changes:
-
Just found that wifi is not working, the wifi chip is an RTL-8723BS, (024c:8723), tried modprobe on r8723bs but getting
modprobe: FATAL: Module r8723bs not found in directory /lib/modules/3.10.108The RTL8723BS is supported (module name: 8723bs.ko, without the "r" at the beginning), but it seems to me that the wifi chip you indicated is an RTL8723AS, which unfortunately I don't know too much about, but I'll try to look it up. I would like to ask you for a little patience.
-
Good news for users stuck on Leia (Kodi 18) is that an external developer (JimmyS83) backported the changes to this version.
This is also currently in alpha7 stage, but since the developer didn't make a zip for testing, I made it instead:
-
-
-
mount: mounting /dev/system on /tmp/system failed: Invalid argument
Could the file system on the eMMC be corrupted?
Ok, then let's try to fix it and copy the necessary file there:
Codemke2fs -F -q -t ext4 -m 0 /dev/system mkdir /tmp/system mount -o rw /dev/system /tmp/system cp /flash/SYSTEM /tmp/system sync umount /tmp/system
(As usual, I would like to get the output of these commands, if possible...)
Then restart.
-
The only thing I want to know is how to rename the dtb for the beelink gt1 ultimate. the page that you tell me does not say it clearly
We assumed that looking around in the /dtb directory at the root of the SD card, you will find the one with the same name as your box.
But according to them, it didn't succeeded. Don't worry, here is the answer to your question:
-
I'm not sure if the current modifications will be permanent, because the previous unmodified Kodi add-ons have been working again for a few days now. Including the Leia Youtube add-on, which has not received any updates (and probably will never be officially released).
Unfortunately, the experience was that it works -> it doesn't work -> it works again -> it doesn't work again -> it works again and it goes round and round. This has been going on for weeks now. (I would be happy if Google finally decided what they wanted now.)
-
It had been connected to it from mid July of 2021 until last Friday.
Your description is quite vague to me. Have you tried to connect to another router? And the classic question: are you 100% sure that you entered the WPA key correctly? By the way, it would be nice if you could send us a log, because without it we're in the dark.
-
Any ideas about the wireless issue I posted about yesterday? As it seems, our posts happened at almost the same time, so you may have missed it.
You actually posted it 1 minute earlier than I replied to a previous comment, so I really didn't notice.
Unfortunately, my answer to your question is that I have no idea. I have not yet tried to connect to a hotspot that requires authentication under LE. In general, a browser is also required to complete the authentication, which is not available on the box.
I've got an S805 OTTO TV box (MXQ 5g) ---
Pairing the S805 with 5G seemed a bit odd, so I looked it up. The Chinese have created again and built a box in 2022 with a 2014 SoC.
OMG!
However, I don't know how the RTL8723AS fits with "5G", because it is only a 2.4 GHz wireless chip. Ok, let's move on...
I'm only using it as an audio endpoint. Currently running with a snapclient, but I will probably add Kodi if I only want to listen to audio in that room (or more the point if my wife does... I'm okay with muting the other systems)
I've got Libreelec on 2 TV systems, and would be happy to swap out armbian for this image - BUT I want to know if the snapclient plugin is supported on this version - and if it includes the newer improvements that when the Kodi audio player starts it allows that to take over, using ALSA not Pulse - I had issues with that on another system)
The Snapserver/Snapclient addons are available, but the factory version in LE9.2 is v0.15, which has not been updated since then.
Unfortunately, I don't use this addon, so I can't answer your question. But the easiest thing is to take an SD card and try the image.
-
after this i reboot whitout the SD and i get: error in mount_flash: mount_common: could not mount /dev/system
Okay, now you should try to mount the system partition under the system running from the SD card:
Codemkdir /tmp/system mount -o ro /dev/system /tmp/system md5sum /tmp/system/SYSTEM md5sum /flash/SYSTEM
If it was successful and the two SYSTEM file checksums match each other (expected value: 23bec528ae6e75828fa5126c8663b6e1), then we continue in another direction, but if we do not get the expected result, then we have the cause of the problem.
-
Impossible to install on MXQ pro S805 with 2gb (m201C_AP).
Please i need help
On the one hand, it is new information for me that an MXQ Pro box was manufactured with an S805 SoC at all, especially a 2 GB one. I think some part of the information is wrong in this sentence.
On the other hand, if you followed my description, which I also described in the first post of this topic, then exactly at which point did you get stuck? And which image did you even try?