SteeMan

I would say this problem is common with the s905x2 and s905x3 boxes. I have this issue on my boxes as well. I don't know of anyone that has tracked down the root cause.

There aren't any kernel headers for the balbes150 tv box builds.

Start by reading the following FAQ entry in the TV Box forums FAQ: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first

Moved post to the correct forum area for TV box questions.

I think you and I are having trouble communicating. You keep referencing things I am not talking about. What your are stating doesn't make sense if you are following the instructions I keep pointing you towards. When I say the instructions in the FAQ I am talking about this: https://forum.armbian.com/topic/17106-installation-instructions-for-tv-boxes-with-amlogic-cpus If you are following these instructions, the box should not boot at all if you don't have a valid u-boot.ext file in place (which therefore leads me to believe since you say it boots correctly without a u-boot.ext file that you are or have followed other instructions and/or used older builds that the one linked to in the instructions I am pointing you towards.) Note I said this earlier, but will repeat with more detail here, if you have used other instructions and/or attempted to install other builds, you will need to reflash your android firmware to start from a known clean starting point in order to attempt your install. The way these builds work is by changing the boot environment stored on emmc. How this is done has changed over time in incompatible ways (and builds by others do it differently as well). But once the uboot environment is modified, you don't know what it is trying to do and the only way to ensure you are successfull is to start from a clean unmodified android environment that the scripts expect to modify (i.e. the scripts aren't smart enough to undo other incompatible changes to the boot environment). Again I suspect this is the case in your situation because if you are using the latest balbes150 build the box should not boot without the u-boot.ext file in place (whereas earlier builds didn't use the u-boot.ext file). So it sounds like you have a u-boot environment installed from an earlier incompatible build that is possibly preventing your box from booting with the u-boot.ext file that should fix the color issue. . To sumarize, you should reflash your box to a clean android firmware. Then follow the instructions in the FAQ post I linked to above. Do not attempt to use any other information found in various places in the forum or in other places at this point. If you are successful at this, then you can try to filter through the other information on the forum to try to get things working better (better dtb settings that your specific box may require). . After all of the above you may or may not get a working box, since balbes150 never supported (or had a s905x3 box to work with) and he has now long ago stopped working on amlogic cpus altogether. But I have a TX3 box with an s905x3 that works for me (minus wifi, bluetooth and gig ethernet). So the final balbes150 build does work for at least some s905x3 boxes.

You say you followed the FAQ steps, but then you say you copied dtb files. There are no steps in the FAQ instructions that talk about copying dtb files. Also, you have meson-sm1-sei610-2.dtb in your extlinux.conf file. There is no such file in the balbes150 build. So clearly you are doing more than simply following the FAQ instructions. Can you please tell me what instructions/tutorials you are following. Clearly I don't know the steps you are doing as they are not part of the instructions in the FAQ. You mention a u-boot.ext from NicoD - again I don't know what this is as this is not in the FAQ instructions. . I guess I would recommend starting from scratch (preferably from a reflashed android firmware so you really are starting from a known point). Then following the steps in the FAQ (not trying to merge steps from other locations, tutorials, etc.

You will need to provide some more information for others to help you, as some of the information you provided does not seem to make sense. You stated that the latest balbes150 version can boot successfully. And I am assuming you are following the instructions in the TV Boxes FAQ. Which would mean that you have chosen a dtb to use (but you do not state what dtb you are booting with), and if following the instructions you have renamed a file to u-boot.ext (which one/ones). You go on to state that the colors are off. You then later state that you can't get it to boot with u-boot.ext. But this doesn't make sense as you stated that you can boot with the balbes150 image which requires the u-boot.ext to boot. So I am not following your explanation of your problem. Could you help explain the problem and the steps you have taken in a bit more detail.

You apparently didn't read the FAQ post carefully as this is addressed: Note2: If you have previously run other distributions on the box such as coreelec the below installation will not work. You will need to restore the original android firmware before attemping the install. coreelec changes the boot environment in ways that are incompatible with these armbian builds.

An external usb wifi adapter should generally work. The key being that the linux kernal has the required driver/module to support that usb driver. Generally any common wifi adapter will have linux kernel support. I would avoid trying to get the cheapest usb wifi adapter you can find, as those are more likely in my experience to not have linux support. Making sure that I am providing a complete answer to your question, the lack of support for the internal wifi on TV boxes is unrelated to support for any specific usb wifi adapter.