balbes150

New image 20170828  kernel 4.12.9.
In this way there is support for USB on the platform S905X. You can run the system from SD cards and USB flash drives. Changed the activation system monitor, now it is built into the kernel itself. To change the screen resolution, you need to use standard tools from control monitor on a desktop. The resolution changes on the fly (directly on desktop). Not working yet WiFi. There are problems with the dtb files (requires the edit and debug under different models). For s905x recommend to use a file meson-gxl-s905x-nexbox-a95x or meson-gxl-s905x-khadas-vim1. For the model s905 - meson-gxbb-odroidc2.

Image Yocto with kernel 4.12 (for S905X).  (v20170825)
To download the image. Unzip. To record on the SD card. Rename the /boot partition file of the dtb to the "dtb.img". To download the script s905_autoscript. Add on the SD card in the /boot partition. On TV Boxing should be informed (with other images) is activated multiboot. Connect the SD card to TV box. To turn the power on. After running the screen is in hibernation (from your watch) for desktop display you have to press a key on the keyboard or moving the mouse.
 
https://yadi.sk/d/f5HsAL913HYksf
 
 
USB works in the kernel 4.12.9 (kernel source Neil Armstrong).

Perhaps in the future it will be. Now it is not.

Image Yocto with kernel 4.12 (for S905X).  (v20170825)
To download the image. Unzip. To record on the SD card. Rename the /boot partition file of the dtb to the "dtb.img". To download the script s905_autoscript. Add on the SD card in the /boot partition. On TV Boxing should be informed (with other images) is activated multiboot. Connect the SD card to TV box. To turn the power on. After running the screen is in hibernation (from your watch) for desktop display you have to press a key on the keyboard or moving the mouse.
 
https://yadi.sk/d/f5HsAL913HYksf
 
 
USB works in the kernel 4.12.9 (kernel source Neil Armstrong).

modprobe dhd
 
or
 
modprobe wifi_dummy
 
 
PS
In order to better understand the features of these images Armbian (they have a number of differences from the official versions), I recommend to read the latest pages of the topic.
 
 

Version update to 5.32 (20170820).
In connection with the transition to a new version of an Assembly environment, there are different bugs (which are not yet discovered).

Update. Version 20170808. The main change is the updated function of installation to the internal memory and replaced the script nand_sata_install a link to the installation script /root/install.sh. Now you can install using two commands : 
 
/root/install.sh 
 
or
 
nand_sata_install.

Update images 20170803.
Added support for remote control. To use it you need to add the correct file "remote.conf" in the /boot directory or /etc/amremote. By default, a part of the image includes several predefined files (in the /boot directory). To use it you need to rename one of the files in "remote.conf". Additionally uploaded the site to the directory the deb package "amremote.deb" , which can be installed in the old system (do not download the whole image). After installing this package you need to run service "amlogic-remotecfg" and add (rename) the correct file 'remote.conf".

Update images 20170803.
Added support for remote control. To use it you need to add the correct file "remote.conf" in the /boot directory or /etc/amremote. By default, a part of the image includes several predefined files (in the /boot directory). To use it you need to rename one of the files in "remote.conf". Additionally uploaded the site to the directory the deb package "amremote.deb" , which can be installed in the old system (do not download the whole image). After installing this package you need to run service "amlogic-remotecfg" and add (rename) the correct file 'remote.conf".

How long are you waiting after turning on ?
What kind of monitor is connected to the TV box ?
 
As far as I know, no s805 trigger activation, multi-boot and run the system with the USB.

For those of you using kodi. Here is a little script I made to auto switch terminals (tty1 then tty7) on exit. This way you won't be stuck on a black screen.
sudo nano /usr/local/bin/kodi-auto paste the following
#!/bin/sh kodi-standalone sudo chvt 1 sleep 2 sudo chvt 7 ctrl+x to save, then hit y to confirm. Then go ahead and make it executable.
sudo chmod +x /usr/bin/local/kodi-auto You will need to add the chvt command to your suedors file, so you can use it without being prompted for password. 
su nano /etc/sudoers Paste in the following at the bottom of the file.  Be sure to replace "YOURUSERNAME" with your user name.
YOURUSERNAME ALL=(ALL) NOPASSWD: /bin/chvt Then if you want, update your kodi shortcuts to use the new script.
Shortcuts are stored in "/usr/share/applications".
sudo nano /usr/share/applications/kodi.desktop Just change the "kodi" Exec to "kodi-auto".
 
 
 
Edit 1: Also a question. My wifi is very very unstable. What dtb are a95x 1GB S905 user's using? The included a95x S905 dtb does not work. I have been forced to try the gxbb_p201.dtb, which is not working all that well. Note, this is a SD install. I have not flashed to nand yet, as I wanted to get the wifi stable first. I would like to test a realtek 100M 1GB version if possible.
 
Edit 2: I figured out how to get my remote to work. You will need the following files from a libreelec install.
/usr/bin/remotecfg /etc/amremote    //just copy the whole folder. /storage/.config/remote.conf  
Then it was just a matter of copying, fixing permissions and running "remotecfg ~/.config/remote.conf" on boot.

1. To install in eMMC you need to use another command "/root/install.sh" (before running you need to switch to root "su -"). In this thread it was discussed many times.
2. Try to connect SD card with Armbian and run with it. If the system can be run in multi-boot mode, you can either completely erase the internal memory and then you can earn program the firmware via USB. Either you will be able to immediately perform the correct installation of the system in eMMC.

If You are still running on the Debian version 8, I see no reason to rush to upgrade (when there is no access to the device).

Version 20170705. Changed algorithm activation HDMI. It now runs in two stages. Pay attention, changed the kernel image to be installed in the internal memory. In the image name removed KODI, as all desktop images by default with KODI.

Test Assembly for s912.
https://yadi.sk/d/HWf1_w123KhtER

And what hinders to try existing images ?
You do not make any changes in the contents of the internal memory and try to start Armbian from SD card.
To capture the image and rename the file s905_autoscript in aml_autoscript (to replace existing). To connect to the TV box and use the toothpicks. At startup the system will attempt to run an external Armbian (without enabling multi-boot).

Image update Mate\XFCE+KODI 20170630 (bug fixes). For those who already have images 20170628 you can only refresh the kodi package (download from the directory the deb on the website and install via "dpkg -i"

Image update Mate\XFCE+KODI 20170628. Updated libs. Now has less to hang.

As far as I know, Alsa is not able to output sound via BT. So Pulseaudio is part of my images.

Image update Mate\XFCE+KODI 20170628. Updated libs. Now has less to hang.

Module "dhd" the same behavior ?
Have you tried to configure and connect, wait 5 minutes after enabling the module ?
 
 
To ALL
Error found in latest version of Armbian+KODI (20170623) and images that can be repaired without downloading a new image (in which these errors are corrected).
1. Freeze sound. To resolve is to edit the file /etc/pulse/default.pa the line load-module module-udev-detect (remove the tsched=0).
2. In a lengthy video playback in the main system turns on the screensaver and artefacts to video. The solution is to disable or uninstall the screensaver. Or use a separate graphics desktop and launch KODI. To do this, remove the package "nodm", install package "lightdm". This will allow at the entrance of the system to choose which system to run Mate\XFC or KODI. In the upper right corner of the login screen (lightdm) there is a button to select Mate or KODI. To run KODI you need to choose the second option in the menu.

I can confirm that kodi works as expected.
All kodi functions worked for me ( scanning my samba shares, adding my videos to collection, etc )
Playing 1080p and 720p videos was a pleasant experience.
The only thing ( unrelated to kodi ) is that my wifi died after 10-15 minutes again, and kodi started buffering for ever.
Since then the system become extremely laggy and unresponsive and took me about 10 minutes to get out of kodi without unplugging the power cord.
Eventually it did manage to get out of kodi, and the system is almost usable again, but with one core to be 100% and no internet/network access again.
So the biggest problem in my system seems to be wifi stability.
The image as i said before is the same Armbian_5.27_S9xxx_Ubuntu_xenial_3.14.29_mate_KODI_20170623.img  and the box is MiniM8S.
Anyone else had better luck with this image?

found a solution with the wifi issues:
i made /etc/network/interfaces like this:
user@amlogic:~$ cat /etc/network/interfaces
source /etc/network/interfaces.d/*
# Local loopback
auto lo
iface lo inet loopback
user@amlogic:~$ 
Now is connecting without problems...
In fact i'm writing this message straight from the box.
I'm in the 6th forced reboot by unplugging the power adapter.

Tested the latest image with kodi Armbian_5.27_S9xxx_Ubuntu_xenial_3.14.29_mate_KODI_20170623.img
Results:
Wifi sees the networks but is not connecting ( also no edit available in wifi settings ( network settings in general )). Playing the videos in desktop with mpv causes the system to hang after a few 10-20 sec with audio looping the last sec of two. The system is not rebooting or shuting down ( always loops back to desktop ). Bluetooth is not working ( not tested very well ) Kodi starts and seems ok but not tested any video ( all my videos are in samba shares ). Closing kodi you have a black screen, you need to switch terminals to fix this. To close the system you need to pull out the power adapter ( no other way of convincing the system to shutdown ) The dtb i tested was gxbb_p200_2G
Hope this helps.