• Content Count

  • Joined

  • Last visited

Everything posted by mb16

  1. Yes, I did not work further on this, as it fits my basic needs. Btw. i'm quite happy with the device, works stable and without severe issues for me.
  2. Thank you for looking into this, I think you are right. I made a test, disabling the error check in the source - then the firmware gets uploaded to the chip but does not work. Now, I found that there are patches to support the 8723cs bluetooth in the kernel ( https://patchwork.kernel.org/patch/10771231/ ) and found the related firmware files in /lib/firmware/rtlbt but I'm by far not brave enough to get stuff like that working. So, I guess I'll just wait and use an usb dongle for bt meanwhile.
  3. Congrats, thanks for sharing! Unfortunately this does not work for me by now. May be a device-tree/wiring issue with my board or because there is an 8723cs in my case. The basic uart/hci communication seems to work, see attached file. But the BT-Adapter still does not show up. Could you upload hciattach.txt for comparison? hciattach.txt
  4. Sorry for that wdtz, i really honor your very helpful comments, but in my case, running literary "adb root" did work for me.
  5. I think there are a hand full of reasons but a major point might related to the "chosen" node.
  6. Agree. Getting to the Android .dts took me some time, as many of the proposed procedures did not work for me. My workflow: Have Android running on the box, developper mode active. In the settings I had a strangely named checkbox like "Internet debugging", switched on Have Android studio installed Could use adb to connect to the box, even without usb, just via lan/wlan adb root worked out of the box, devices like this one seem to be rooted by default? used adb to download the device-tree directory (have android not at hand now, should not be to hard to find
  7. Glad to read I seem to have created something useful. My box is a scishion ai one alike one, MXQ pro max labeled box. The board is labeled TX-RX4B-V02. My workflow: Used adb to read the device tree directory from the box running android. Converted to android.dts file using dtc. For armbian used the ...box.dtb because the device could boot using that one. Converted dtb to dts using the "sorted" option of dtc for comparison (a). Converted dtb to dts without the "sorted" option for optimization (b). Used a merge utility (meld) to compare
  8. I made a few adjustments to the device tree for my XT-RX4B-V02 based box. The intermediate results look promising: wifi (RTL8723CS) basically works memory perf: armbian@rk3328:~$ dd if=/dev/zero of=/tmp/testfile bs=1M count=1000 1000+0 records in 1000+0 records out 1048576000 bytes (1.0 GB, 1000 MiB) copied, 1.70386 s, 615 MB/s ... this was within an x11vnc session, on multiple tests I constantly get values greater than 550MB/s (The board has 4GB DDR3/1600 ram) Notes I never experienced stability issues. As the mounted "heatsink" is more than dubious,
  9. Should that be 'sudo make modules_install'? Very helpful, thanks a lot!
  10. Thank you for all these details! I can connect adb and have root. Lets see, what I can get, will take me some time.
  11. Big thanks to Balbes, perfect work! I own a MXQ PRO max. This box looks like SCISHION AI ONE / RX4B. (rk3328, 4gb ram, 32gb emmc, 100mbit lan, 2.4ghz wlan, bt) Goal: Use box as thin client (vnc, rdp,...) using armbian/ubuntu desktop istalled on emmc. With Balbes newest image and jeanrhrum hints (https://forum.armbian.com/topic/8082-armbian-for-tv-box-rk3328/?do=findComment&comment=68975) i am able to make the box boot armbian from sd card. (SD card booting is not reliable. In many cases the box ignores the sd and boots Android. After a number of restarts