Petee

Members
  • Content Count

    68
  • Joined

  • Last visited

About Petee

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    Time

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you. Understood. Thought for a bit that increasing the size of the boot partition would make the updates work better. Yes this one here is still running at 1 Gb after updating. I did have errors on the second or third update and froze the build. I was able to utilize the 5XX builds with Wireless / Bluetooth running but not Gb Ethernet.
  2. Well posting out loud here figured it out. 1 - bios serial port settings were off. Here there are 4 serial ports out and none were enabled 2 - PFSense baud rate was incorrect All is well now. Apologies for the fuss.
  3. Hardware: 1 - NEO-8M GPS Satellite Positioning Module for Arduino STM32 C51 $7.49 USD on Ebay. NOTE it is using TTL output. Validated USB GPS connection to work fine. 2 - Uxcell a14041500ux1216 MAX232CSE Transfer Chip RS232 to TTL Converter Module COM Serial Board for $7.37 USD (Amazon) I connected PPS pin to Pin #1 on RS-232 interface. Using Linux connected USB port and RS-232 port to laptop. I see GPS chit chat fine on two serial intefaces. Using this for a new PFSense box QOTOM Mini PC. Transport ==> USB power coming from QOTOM Mini PC and RS-232 coming from GPS/TTL converter. NOTE: PFSense is BSD. I see only one serial interface using command line /dev: cat cuaU0 $GNTXT,01,01,02,u-blox AG - www.u-blox.com*4E $GNTXT,01,01,02,HW UBX-M8030 00080000*60 $GNTXT,01,01,02,ROM CORE 3.01 (107888)*2B $GNTXT,01,01,02,FWVER=SPG 3.01*46 $GNTXT,01,01,02,PROTVER=18.00*11 $GNTXT,01,01,02,GPS;GLO;GAL;BDS*77 $GNTXT,01,01,02,SBAS;IMES;QZSS*49 $GNTXT,01,01,02,GNSS OTP=GPS;GLO*37 $GNTXT,01,01,02,LLC=FFFFFFFF-FFFFFFFD-FFFFFFFF-FFFFFFFF-FFFFFFF9*50 $GNTXT,01,01,02,ANTSUPERV=AC SD PDoS SR*3E $GNTXT,01,01,02,ANTSTATUS=OK*25 $GNTXT,01,01,02,PF=3FF*4B This is coming from the USB serial connection (and power). I have the RS-232 9 Pin (from TTL to RS-232) plugged in to Quotom serial com port #1. I do not see this port using command line where as I saw this in Linux. If I power the GPS externally I see chatter from the RS-232 connection fine with Linux but not in BSD. Any suggestions? I am currently using a Sure GPS with a PPS modification on another PFSense box and it is working fine.
  4. I have left it running now for a few weeks and it runs fine. It did error out on one update and I rebooted it and updated it again and it is fine. NOTE: this is only for the T95Z Max S912 TVBox. Thinking though of freezing the updates now on it.... _____ ___ ____ _____ ____ ___ _ ____ |_ _/ _ \| ___|__ / / ___|/ _ \/ |___ \ | || (_) |___ \ / / \___ \ (_) | | __) | | | \__, |___) / /_ ___) \__, | |/ __/ |_| /_/|____/____| |____/ /_/|_|_____| Welcome to ARMBIAN 5.73 stable Ubuntu 18.04.2 LTS 3.14.29 System load: 1.45 1.29 1.22 Up time: 18:57 hours Memory usage: 10 % of 2733MB IP: 192.168.244.250 CPU temp: 35°C Usage of /: 29% of 29G [ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ] Last login: Wed Jul 3 20:46:17 2019 from 192.168.244.232 root@HS3-ATL:~# Note that I updated the release version to indicate that it is a S912 as it kept going to showing a Rock64 on the update. I also found that I had a bad SD card running for a while which caused me much grief. This box is running Home Assistant, HomeSeer, Node Red, Mosquitto, Leviton OmniLinkBridge (MQTT) and testing with a Digi 8 port edgeport. So in addition it is running a connection to a UPB controller, ethernet ZWave, RFID. I am testing a LoRa RFID connection via two transievers with a range of 8 Km. I do not know what dtb file it is using cuz it is not in the uEnv.ini file such that it is using defaults. root@HS3-ATL:/boot# ls aml_autoscript fan.sh aml_autoscript.zip hdmi.sh armbianEnv.txt Image armbianEnv.txt.out initrd.img-4.4.182-rockchip64 armbian_first_run.txt.template s905_autoscript boot.cmd s905_autoscript.cmd boot.scr System.map-4.4.182-rockchip64 config-4.4.182-rockchip64 uEnv.ini dtb uInitrd dtb-3.14.29.old zImage dtb.old root@HS3-ATL:/boot# cat uEnv.ini bootargs=root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyS0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 mac=${mac} It just works fine as an Ubuntu server for automation. I have no keyboard, mouse or HDMI monitor connected to it. Note that the kernel is old: root@HS3-ATL:/boot# uname -a Linux HS3-ATL 3.14.29 #26 SMP PREEMPT Sun Jul 29 11:26:15 MSK 2018 aarch64 aarch64 aarch64 GNU/Linux It is only for this model TVBox S912. Rest of the S912 boxes are running with newest kernels just fine. IE: when trying a new kernel on this one the Gb NIC wasn't working and only wireless and bluetooth worked. Download and install this build for this box to work. (note that I never tried WLAN or Bluetooth with it and do not need it). It is listed as Armbian_5.44_S9xxx_Ubuntu_bionic_3.14.29_server_20180729.img.xz dated 07292018. Going to kernels 4.X and 5.X did not work for me with this specific device. Never did boot it to Android or even looked. Maybe my approach was wrong? Any guidance on updating Android and extracting DTB file for use with Armbian would be appreciated. Just purchased a second BeeLink BT3 Pro here. NOT for TV rather just for Automation. Got the first one new for $65 and second one for $100. It is not worth the $150 that Amazon is selling them for. I do now see a similiar to BeeLink BT3 pro with an SSD card slow underneath for around $100. For KODI use have settled on using CoreElec with an old kernel just for the HD 4K features. For server use and no video have settled on currently posted kernel. Still liking the footprint versus the RPi (even the RPi 4).
  5. Seeing that CoreElect running: Linux ICS-X9T 3.14.29 #1 SMP Sun May 12 15:03:58 BST 2019 aarch64 GNU/Linux Old kernel decided to try Armbian_5.44_S9xxx_Ubuntu_bionic_3.14.29_server_20180729.img.xz. Interesting that it booted right up and ethernet interface is working fine now. I understand that the kernel is old but really all I want is this box to run Armbian Ubuntu Server. Not interested in using the wireless and or blue tooth interface at this time. ____ ___ / ___|/ _ \__ ____ ____ __ \___ \ (_) \ \/ /\ \/ /\ \/ / ___) \__, |> < > < > < |____/ /_//_/\_\/_/\_\/_/\_\ Welcome to ARMBIAN 5.44 user-built Ubuntu 18.04.1 LTS 3.14.29 System load: 1.14 0.78 0.34 Up time: 4 min Memory usage: 4 % of 2733MB IP: 192.168.244.250 CPU temp: 38°C Usage of /: 4% of 29G [ 0 security updates available, 202 updates total: apt upgrade ] Last check: 2019-06-21 09:52 Last login: Fri Jun 21 09:49:18 2019 from 192.168.244.232 root@HS3-ATL:~# ethtool eth0 Settings for eth0: Supported ports: [ TP AUI BNC MII FIBRE ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supported pause frame use: No Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised pause frame use: No Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Link partner advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Link partner advertised pause frame use: Symmetric Receive-only Link partner advertised auto-negotiation: Yes Link partner advertised FEC modes: Not reported Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: external Auto-negotiation: on Supports Wake-on: ug Wake-on: d Current message level: 0x0000003d (61) drv link timer ifdown ifup Link detected: yes Now I can move on to installing Docker and Home Assistant. It would be nice if this box's ethernet interface worked with current released kernel.
  6. Here for two S912 boxes and current version of KODI TicTid X9T Pro - S912 - 3Gb - Gb NIC TX9 Pro Amlogic S912 - 3Gb - Gb NIC Went to using CoreElec mostly for HD 4K playback and that is using the old kernel. ############################################## # CoreELEC # # https://coreelec.org # ############################################## CoreELEC (official): 9.0.2 (Amlogic.arm) ICS-X9T:~ # uname -a Linux ICS-X9T 3.14.29 #1 SMP Sun May 12 15:03:58 BST 2019 aarch64 GNU/Linux ICS-X9T:~ # I did get HD video using the latest builds via VIM2 BUT that was a virtual HD video emulation and did not provide me with HD 4K playback. IE: this one is currently configured as a server and can see the desktop fine but it is an emulated video and does not do HD 4K playback .. and can't get NIC port to work on it.... T95Z Max S912 uname -a Linux HS3-ATL 5.1.0-aml-s905 #5.89 SMP PREEMPT Mon Jun 17 13:01:39 MSK 2019 aarch64 aarch64 aarch64 GNU/Linux
  7. Thank you amirul will give meson-gxm-q200.dtb a try. Odd thing is that for server mode on all of the other S912 boxes (3Gb, Gb NIC) the meson-gxm-khadas-vim2.dtb works great. IE: TicTid X9T Pro - S912 - 3Gb - Gb NIC TX9 Pro Amlogic S912 - 3Gb - Gb NIC It is only on this box (T95Z Max) that I cannot get the network ethernet running. I prefer to connect these boxes used as servers via their ethernet connection over their wireless connection. BTW Wireless is working perfectly. ifconfig eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether c4:2a:fe:36:11:32 txqueuelen 1000 (Ethernet) RX packets 579 bytes 79088 (79.0 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 eth0:avahi: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 169.254.5.7 netmask 255.255.0.0 broadcast 169.254.255.255 ether c4:2a:fe:36:11:32 txqueuelen 1000 (Ethernet) device interrupt 20 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 880 bytes 65120 (65.1 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 880 bytes 65120 (65.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.244.252 netmask 255.255.255.128 broadcast 192.168.244.255 inet6 2601:244:4000:dc3:55cc:f13:e04e:f6a8 prefixlen 64 scopeid 0x0<global> inet6 2601:244:4000:dc3:3553:1ac8:be38:3e25 prefixlen 64 scopeid 0x0<global> inet6 fe80::944c:1fa5:37b0:bab2 prefixlen 64 scopeid 0x20<link> ether 6c:21:a2:4e:68:d8 txqueuelen 1000 (Ethernet) RX packets 3273 bytes 4687586 (4.6 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1123 bytes 110440 (110.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 Seeing the same with meson-gxm-q200.dtb file.
  8. OK got ethernet sort of working on the T95 Z Max TV Box (S912 - 3Gb - 1Gb NIC) using meson-gxm-q201.dtb. /boot# uname -a Linux HS3-ATL 5.1.0-aml-s905 #5.89 SMP PREEMPT Mon Jun 17 13:01:39 MSK 2019 aarch64 aarch64 aarch64 GNU/Linux eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether c4:2a:fe:36:11:32 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 20 eth0:avahi: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 169.254.5.7 netmask 255.255.0.0 broadcast 169.254.255.255 ether c4:2a:fe:36:11:32 txqueuelen 1000 (Ethernet) device interrupt 20 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 loop txqueuelen 1000 (Local Loopback) RX packets 551 bytes 50590 (50.5 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 551 bytes 50590 (50.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.244.252 netmask 255.255.255.128 broadcast 192.168.244.255 inet6 2601:244:4000:dc3:55cc:f13:e04e:f6a8 prefixlen 64 scopeid 0x0<global> inet6 fe80::944c:1fa5:37b0:bab2 prefixlen 64 scopeid 0x20<link> inet6 2601:244:4000:dc3:b85c:6eb8:c6a2:531f prefixlen 64 scopeid 0x0<global> ether 6c:21:a2:4e:68:d8 txqueuelen 1000 (Ethernet) RX packets 13082 bytes 2254470 (2.2 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1727 bytes 296907 (296.9 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 No DHCP address comes up for eth0...but I can ssh into the eth0:avahi port which doesn't make sense to me. I have read that there is an issue with eee and if I disable it that may fix my problem here. ethtool --show-eee eth0 EEE Settings for eth0: EEE status: enabled - active Tx LPI: disabled Supported EEE link modes: 100baseT/Full 1000baseT/Full 1000baseKX/Full 10000baseT/Full 10000baseKX4/Full 10000baseKR/Full Advertised EEE link modes: 100baseT/Full 1000baseT/Full 1000baseKX/Full 10000baseT/Full 10000baseKX4/Full 10000baseKR/Full Link partner advertised EEE link modes: 100baseT/Full 1000baseT/Full 1000baseKX/Full 10000baseT/Full 10000baseKX4/Full 10000baseKR/Full
  9. Tinkering a bit with changing DTB file I can get a mac address but no IP right now....T95Z Max S912 - 3Gb - Gb NIC
  10. Trying newest firmware Ubuntu Disco Desktop on a S912 3Gb Gb NIC TVBox. All looks to be OK except that the NIC card doesn't start. Wireless works fine. Jun 18 01:31:35 HS-ATL kernel: Linux version 5.1.0-aml-s905 (root@vbox) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f Jun 18 01:31:35 HS-ATL kernel: Machine model: Khadas VIM2 2x VTV Jun 18 01:31:35 HS-ATL kernel: dwc3 c9000000.dwc3: Failed to get clk 'ref': -2 Jun 18 01:31:35 HS-ATL kernel: meson-gx-mmc d0074000.mmc: no support for card's volts Jun 18 01:31:35 HS-ATL kernel: mmc1: error -22 whilst initialising MMC card Jun 18 01:31:35 HS-ATL kernel: mdio_bus 0.2009087f: MDIO device at address 0 is missing. Jun 18 01:31:35 HS-ATL kernel: phy phy-d0078080.phy.3: unsupported PHY mode 5 Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: PTP uses main clock Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: no reset control found Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: User ID: 0x11, Synopsys ID: 0x37 Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: DWMAC1000 Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: DMA HW capability register supported Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: RX Checksum Offload Engine supported Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: COE Type 2 Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: TX Checksum insertion supported Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: Wake-Up On Lan supported Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: Normal descriptors Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: Ring mode enabled Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet: Enable RX Mitigation via HW Watchdog Timer Jun 18 01:31:35 HS-ATL kernel: meson8b-dwmac c9410000.ethernet (unnamed net_device) (uninitialized): device MAC address c4:2a:fe:36:11:32 Jun 18 01:31:36 HS-ATL kernel: brcmfmac: F1 signature read @0x18000000=0x15264345 Jun 18 01:31:36 HS-ATL kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Jun 18 01:31:36 HS-ATL kernel: usbcore: registered new interface driver brcmfmac Jun 18 01:31:36 HS-ATL kernel: Bluetooth: Generic Bluetooth SDIO driver ver 0.1 Jun 18 01:31:36 HS-ATL kernel: brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.khadas,vim2.txt failed with error -2 Jun 18 01:31:37 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: Could not attach to PHY Jun 18 01:31:37 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) Jun 18 01:31:37 HS-ATL kernel: Adding 1048572k swap on /dev/zram1. Priority:5 extents:1 across:1048572k SSFS Jun 18 01:31:37 HS-ATL kernel: zram0: detected capacity change from 0 to 52428800 Jun 18 01:31:37 HS-ATL kernel: EXT4-fs (zram0): mounted filesystem without journal. Opts: discard Jun 18 01:31:38 HS-ATL kernel: brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 Jun 18 01:31:38 HS-ATL kernel: brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4f Jun 18 01:36:38 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: Could not attach to PHY Jun 18 01:36:38 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) Jun 18 01:40:49 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: Could not attach to PHY Jun 18 01:40:50 HS-ATL kernel: meson8b-dwmac c9410000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19) Jun 18 01:31:41 HS-ATL kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3 root@HS-ATL:/sys/class/net/eth0# sudo lshw -c network *-network:0 description: Wireless interface physical id: 3 logical name: wlan0 serial: 6c:21:a2:4e:68:d8 capabilities: ethernet physical wireless configuration: broadcast=yes driver=brcmfmac driverversion=7.45.154 firmware=01-4fbe0b04 ip=192.168.244.250 multicast=yes wireless=IEEE 802.11 *-network:1 DISABLED description: Ethernet interface physical id: 4 logical name: eth0 serial: c4:2a:fe:36:11:32 capabilities: ethernet physical configuration: broadcast=yes multicast=yes This is going to be an automation server and will remove desktop once it is working. Any suggestions?
  11. Here just built a second PFSense box and testing out a new mini GPS (Arduino style) that has built in RS-232 and PPS signal. It is around $7 USD with free shipping on Ebay. My primary GPS / PPS is a modded Sure GPS. Tiny box DIN mounting this box. I know this doesn't have much to do with the TVBox / Armbian rather just a NTP time source for my home network.
  12. You are making me paranoid. All I do is run MS SAPI on the Windows 7 embedded. 5 voices as I collect SAPI voice fonts (multiple languages). I prefer to keep the voice TTS in house versus using the Amazon Alexa for TTS (although I am tinkering with it).
  13. @jianchunchen I wrote the image to an SD card, booted pressing the reset button and I was good to go. Specifically it was the server version: VIMs_Ubuntu-server-bionic_Linux-4.9_arm64_SD-USB_V20190604.7z I used Etcher to write the SD card on my Ubuntu 18.04 laptop. The above said one T95Z Max has turned out to be a "dud". It started to overheat a couple of weeks ago and when it is hot it doesn't work. Rather than open the case (break the seals) I have returned it. The other T95Z Max is running CoreElec and doing fine. The other two S912 TVBoxes have been working fine running in server mode / CoreElec and multitasking 24/7 with no problems. I like the power button on one of the S912's. Also now tinkering with the BeeLink BT3 Pro (Intel) computer. It's not an optimal TV watching box BUT it is a great tiny Ubuntu box running Ubuntu 18.04 and W7E (Oracle VB)
  14. Testing X9T Pro (S912 3Gb RAM Gb NIC) today with ARMBIAN 5.86 user-built Ubuntu 18.04.2 LTS 5.1.0-aml-s905 and using meson-gxm-vega-s96.dtb. Also tested desktop version. Boots fine. Network comes up. Looks like it talks IP6 just fine except that it cannot get to the armbian site on update using IP6. Wierd stuff with SSH. Reconfigured it and sometimes it just disconnects me. Disabled IP6 via armbian-config. Rebooted. Boot up got stuck in boot directory. Cold booted and it was OK and accessible via SSH. Using armbian-config installed desktop except that root ssh got locked. Redid the ssh config. Rebooted from console. Keep having issues with root and user ssh access. IE: disconnects randomly. Not sure what the issue is right now. For headless server use only care about the network connection. What is not needed is bluetooth or WLAN.
  15. Wanting to build a new Armbian server from a TV Box. Video is not a requirement here as the device will be headless. Just a quickie picture relating to the size of this box. I am impressed. It will be mounted inside of a security panel (Leviton Omni Pro 2) and serve as a console to said security panel using automation software. Ideally though want: - Gb NIC - 32 Gb eMMC - 4 Gb RAM Bluetooth and WLAN is nice to have but not necessary for my use. Been only tinkering here with Octocore ARM CPU TV boxes but not necessary. I am currently wanting to add a firewall (2nd NIC) and am familiar mostly with BSD PFSense and OpenWRT on a variety of devices. Currently doing this with a hardware modified micro router (NEXX) running OpenWRT. It is so small I can really just leave this device in place. Goal here is to install TV box inside of a combo automation / security media panel. The firewall would face current home LAN and may run a VPN server. Checking out Amazon see: 1 - Android 9.0 TV Box, 2019 H96 Max X2 4GB DDR4 Ram 32GB ROM 4K Smart TV Box Amlogic CPU HDMI 2.1/H265 /Dual WiFi 2.4G 5.0G/100M Ethernet/BT/USB3.0 Set Top Box (no Gb NIC) - S905 chipset 2 - ZYX 4GB 32GB Android TV Box - MX10 Android 8.1 Smart TV-Box Streaming Media Player H.265 64bit Supporting Wireless, 4K (60Hz),3D, RK3328 Quad Core Set-Top-Box - no Gb NIC - RK3328 3 - Android 8.1 TV Box with 4GB RAM 32GB ROM,GiMiBOX T9 Android Boxes Quad- Core 64 Bits Support BT4.1/ H.265/ 3D /5G WiFi/USB 3.0/ UHD 4K Smart TV Box with Remote Keyboard - RK3328 4 - H96 max X2 Android 8.1 TV Box, 4GB RAM 32GB ROM Amlogic Quad core Support WiFi 2.4G+5G/4K/3D Smart TV Box Streaming Media Player - no GB NIC The list goes on and on. What would you guys recommend me to get?