s-petersen

yes, there may be a different program that behaves differently, I've never used vnc

Is there a different program you can try?

Let me know if this solves the issue?

I've read the processor may be overheating because the heatsink is not designed for the workload the chip is doing under Armbian, perhaps that is the reason mine failed. It may help to increase the size of the heatsink, maybe try it with the cover off for a test?

As far as I could see, there was no way to change the resolution, both Android and Armbian were stuck at the same 1920x1080 resolution. I changed font size to get it where i could work with it.

Can you point to a more recent place to find files that may work?, I know you are one of the most knowledgeable people on this topic. I had trouble finding the files that made my box work also, I know the files are old, but this category of hobby type equipment is not something I would even care if it were compromised, as it is a "toy" for experimentation. My goal was for a jukebox if it didn't fail, a replacement for a Raspberry Pi. Thanks for your efforts, so we have a place to start tinkering with these boxes!

You can try here, but I am not positive it is a safe site https://androidfilehost.com/?w=search&s=Armbian&type=files&sort_by=name&sort_dir=DESC

I will try to find the other files, I know that I have seen them recently

My box used a S805 processor, but the 905 is supported by other files pretty well I believe. Does your box lock up on boot?

My MXQ TV box died today, I was running Armbian stretch, and I had been listening to Mplayer playing Mp3s for several hours as background music, when the player stopped because it ran through the list, I went to change directories, but there were none found( I was running off the SSD), so I tried the root directory, also no files found. I closed the terminal window, and tried to restart, which just resulted in a boot loop. Thinking the file system was corrupt, I disconnected the SSD,and tried to boot the Android system from the internal Nand? which also resulted in similar behavior, I tried a different monitor, and removed all peripherals , Android partially booted, then died again, it seems like a video or memory issue. I had an interesting time getting everything working, and also the ability to get GPIO working with a USB GPIO was feeding my Raspberry Pi withdrawal problem. After all of this, I don't feel I will buy a newer TV box, There is no real support, and most of the officially supported boards cost much more than a Raspberry Pi Zero, and are not nearly as flexible. Raspberry OS Or Raspian just works, and the GPIO requires very little fiddling to get working. I would have gladly contributed if some TV boxes were supported, but it was made clear that would never happen, I am sincerely happy that balbes150 and SteeMan put the effort in all those years ago, and got my box to a usable condition, I only wished I had joined when the TV boxes were supported back then. Thanks for the memories...

Maybe PM peppezic directly and ask him?

I'm also trying to learn more about the boot process, I currently can boot from a USB SSD unless anything else is plugged in to any USB port except a powered hub, if anything is plugged in that powered hub, it will not boot also. If I put the fatload mmc 0 entry last in the s805_autoscript.cmd file will that fix it? It seems to be an addressing issue, rather than a power issue. I am using stretch 310.108 with no DTB selected, and everything works except the Mali 450

How can I find out the boot sequence, and also I never picked a dtb file to use, is there a way to find which one it is using? last question, is the Mali 450 driver included in stretch 3.10.108? Everything works, except video acceleration

So, there is a strange problem, if I have any other usb devices other than a hub plugged in, it will not boot via usb. If just the hub and the SSD plugged in, it will boot just fine, If I plug anything into the hub, it will not boot either, so it's not a power problem, it seems to be something about discovering other devices during the pre boot that is causing the issue. If I only have SSD during startup the SSD will blink a few times, then blink continuously for the entire boot, with other devices connected the drive blinks a few times, and stops, then boots the original android software.

I am not sure how it is working, I just formatted the SSD with Balena Etcher as though it was a SD card, and it boots, as long as I don't start it with the keyboard and mouse connected. It may be that the SSD draws too much current, but if I plug the keyboard and mouse in after boot, it works fine