• Content Count

  • Joined

  • Last visited

Reputation Activity

  1. Like
    feliscatus12 got a reaction from jaum20 in MXQ Pro 4K 5G (Allwinner H3) running Armbian originally for Beelink X2   
    First of all, I should mention that the TV box we got was probably a clone one. Original MXQ Pro 4K 5G has an Amlogic chipset. We got an old Allwinner H3 which to my recent knowledge is very old now. This was our first TV box purchase and yeah, admittedly, we should have searched deeper before purchasing anything. Luckily, we got the box dirt cheap.. around $20 only. It runs Android 7.1.2 which is good for media playback, but hella laggy even for light multitasking or even light web browsing. We bought the TV box hoping my siblings could seamlessly use it for their remote learning. I heard Beelink X2 has an H3 and used to have official Armbian support, so I grabbed the image file with desktop environment from https://archive.armbian.com and tested it on our box and to my surprise, everything works near perfectly! Here are a few things I am hoping that would be fixed:
    1. Incorrect RAM readings - Beelink X2 originally has 1/8gb configuration. My box in particular has 2GB of RAM and 16GB of eMMC storage. How can I safely configure the ROM to recognize my 2GB RAM? I have checked the board and it has 4 512gb RAM modules. I tried modifying the /boot/boot.cmd file (despite the bold warning not to edit it, stupid I know lol), then I end up breaking the boot sequence and had to reflash the image back to the sd card and start again.
    2. Laggy video playback (YouTube on Firefox) - I do have some basic understanding as to why implementing support for GPU could be difficult, but did anyone here managed to get decent video playback? Would installing OpenGL drivers help video playback? https://forum.armbian.com/topic/1420-opengl-on-mali-gpu-bananapi-orangepi-pc-etc/ I tried this and was able to build stuff. I am stuck on step 3 though specifically "-configure your kernel to allocate memory for the GPU" I think that involves similar steps in configuring uboot which admittedly I am clueless. Can anybody point me to the right direction?
    3. No WiFi - I don't really mind this much as the box will be stationed somewhere connected via ethernet cable. I am interested in fixing it though. Would I need to extract the WiFi drivers from the original Android ROM? How do I go about this?
    4. No HDMI sound - Again, not that important. We could use a USB Sound Card. Is there a fix to this though?
    In my experience, browsing is much faster with Firefox than with Chromium. I am currently running version 81. To optimize the experience, I disabled smooth scrolling. Also, to force desktop mode, I added this at about:config -> (left) general.useragent.override, (right) Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:81.0) Gecko/20100101 Firefox/81.0
    Our PK-635M webcam works out of the box, no additional setup needed. Firefox detects the microphone and the webcam. Calls and video calls via Facebook Messenger works. Google accounts could sign-in (unlike in Chromium). Google Meet and Zoom have yet to be tested though..