paul73 I've been lurking in this thread for a while. I ordered the T95 box you recommended previously.
Are you running it off the internal drive or an SD card? I could never get it to install to the internal drive so I'm running it off an SD card.
Does yours backpower your mainboard/display? If I shutoff my printer the display stays on unless I disconnect the USB cable from the T95
i should have documented my steps on t95, my fault. when i had to do a second box it took some time to rediscover the america again, so, here it is.
first of all - yes, the usb power backfeed is there, so, just put printer and t95 power supply on the same powerstrip and kill the switch on the strip to turn off it all. easy enough.
now on t95 boxes. there is a swarm of them on amazon and ebay, but they are nothing alike inside, so, we will consider you got EXACTLY the one from the link i posted. it is very important.
if you did that, then you just had to follow step the step the guide i also posted:
The T95 Mini is an android TV box. Be careful when sourcing one as there are a lot out there that actually use the H616 processor and currently the android tv boxes using this processor don’t…
3dpandme.com
now, of what is NOT in the guide.
so, you need first to get raspberry PI imager and flash the 2gb quadra image to the SD card.
i think card should not be larger than 32gb for all this to work, i used a 16gb card.
to be able to flash this box you need to make sure NOTHING is plugged in into it. only the power cord. if hdmi cord is connected - it will not flash.
you do not press nothing at all also, you unplug the power cord and all else, put in the card, then put back power cord alone.
then it remains black for 20-30 sec, then the red led should lit and stay lit for the flash duration, around 5 min i think or bit more - then it will turn blue.
then you need to unplug the power cord after that.
THEN.
this shit by default comes with the absolutely retarded graphic UI the name of which i always forget, looking for it now on the box. 'lightdm'.
you will need to disable it - 'systemctl stop lightdm','systemctl disable lightdm' - later.
so, after you flash it - if you connect ethernet cord to the box, you get zilch UNTIL you connect it to the monitor with the hdmi cord, mouse and keyboard, and login this shit into its quadra account via this lightdm interface. only AFTER that it initializes network interfaces and connects to the network. a complete idiocy.
ALSO - adding it now - if you just connect hdmi cord after it is already turned on and booted - it will also not work. you need to unplug power, connect hdmi cord to the box and monitor, then turn it on, only then it will produce video output. keyboard and mouse are better to be plugged in initially too. first box was sensitive to usb power drain - the keyboard i used first had some backlit LEDs on it, and i think it overdrained the usb, so if box blinks its blue led and then reboots suddenly - it means you drain too much from the USB port and provided power supply is insufficient. use a different keyboard.
frankly the ethernet cord is not needed, as after you plug power cord and see something on the monitor finally and then login into armbian - you just run 'passwd' first to alter 'quadra' user, then change root password, then run 'nmtui' to conenct to wifi.
THEN.
those boxes have a nasty glitch - armbian has a glitch, really, as every time you reboot it the wifi gets different mac address and it produces different dynamic IP.
you need to set it on a manual IP address. to do that on those boxes on that flash - you need to alter the file that will be created under
/etc/NetworkManager/system-connections
with the name of your wifi network after you run the 'nmtui' command. you just need to edit the [ipv4] section in it, do not do nothing else.
[ipv4]
address1=192.168.10.123/24,192.168.10.1
dns=8.8.8.8;8.8.4.4;
dns-search=
method=manual
after that disable service for lightdm, and it should be able to reboot and get connected to the network so you can manage it remotely.
install klipper as the guide says - it is super easy with:
./kiauh/kiauh.sh
i think only step they also skipped in the guide was the mjpg-streamer-service install, you need it for the camera. i got it done with 'snap' - also super easy way, so it handles it as:
/usr/bin/snap start mjpg-streamer.mjpg-streamer-service
forgot the steps, i think it was from here:
Get the latest version of mjpg-streamer for on Ubuntu - UVC webcam streaming tool
snapcraft.io
PS. if this thing does something else to you of what i did not cover above - post the details here.
PPS.
I knew i will forget it. for the camera - more steps are needed. and i think i had lost them , AGAIN.
you need to install the 'v412-ctl' tool and all required support files, so the command:
v4l2-ctl -d /dev/video1 --list-ctrls-menus
would give you a list of what your web cam can do.
ok, what does my command history say... all to be done from under the quadra user - not from root.
sudo apt-get install git -y
sudo apt install python3 python3-pip python3-dev python3-setuptools python3-venv git libyaml-dev build-essential libffi-dev libssl-dev
sudo apt-get install libjpeg8-dev imagemagick libv4l-dev
sudo ln -s /usr/include/linux/videodev2.h /usr/include/linux/videodev.h
sudo apt-get install cmake libjpeg8-dev
sudo apt install snapd
sudo snap install mjpg-streamer
/usr/bin/snap start mjpg-streamer.mjpg-streamer-service
then you need to alter the 'config' startup file for the streamer at
/var/snap/mjpg-streamer/current$
mine reads now as:
INPUTOPTS="input_uvc.so -r 1920x1080 -f 12 -d /dev/video1"
PORT="-p 8080"
DAEMON="true"
you generally need to add the device to it - the '-d /dev/video1' part. it will unpredictably come to /video1 or to /video0 - you need to use the v412-ctl utility to see where it is.
also you need to flip daemon option to 'true' so it would autostart upon reboot.
a correct camera output looks like:
root@inovato:~# v4l2-ctl -d /dev/video1 --list-ctrls-menus
brightness 0x00980900 (int) : min=-10 max=10 step=1 default=0 value=0
contrast 0x00980901 (int) : min=1 max=32 step=1 default=16 value=16
saturation 0x00980902 (int) : min=0 max=20 step=1 default=10 value=10
hue 0x00980903 (int) : min=-5 max=5 step=1 default=0 value=0
white_balance_temperature_auto 0x0098090c (bool) : default=1 value=1
gamma 0x00980910 (int) : min=100 max=200 step=1 default=180 value=180
power_line_frequency 0x00980918 (menu) : min=0 max=2 default=1 value=1
0: Disabled
1: 50 Hz
2: 60 Hz
white_balance_temperature 0x0098091a (int) : min=2800 max=6500 step=1850 default=6500 value=6500 flags=inactive
sharpness 0x0098091b (int) : min=0 max=10 step=1 default=7 value=7
exposure_auto 0x009a0901 (menu) : min=0 max=3 default=3 value=3
1: Manual Mode
3: Aperture Priority Mode
exposure_absolute 0x009a0902 (int) : min=156 max=5000 step=1 default=512 value=512 flags=inactive
root@inovato:~#
an incorrect one:
root@inovato:~# v4l2-ctl -d /dev/video0 --list-ctrls-menus
Codec Controls
h264_profile 0x00990a6b (menu) : min=0 max=4 default=2 value=2
0: Baseline
1: Constrained Baseline
2: Main
4: High
hevc_sequence_parameter_set 0x00990cf0 (unknown): type=120 flags=has-payload
hevc_picture_parameter_set 0x00990cf1 (unknown): type=121 flags=has-payload
hevc_slice_parameters 0x00990cf2 (unknown): type=122 flags=has-payload
hevc_scaling_matrix 0x00990cf3 (unknown): type=123 flags=has-payload
hevc_decode_parameters 0x00990cf4 (unknown): type=124 flags=has-payload
hevc_decode_mode 0x00990cf7 (menu) : min=0 max=0 default=0 value=0
0: Slice-Based
hevc_start_code 0x00990cf8 (menu) : min=0 max=0 default=0 value=0
0: No Start Code
it is NOT a camera device.
