Just tested 8.0-8.0.1h with gxm_q200_2g.dtb on a Nexbox-A1 and all seems fine, including my IPTV subscription. I'm happy to have a functional, inexpensive box on which to run a second instance of LibreELEC. Will keep checking in here hoping for a release with the 'real' Mali-T820 libs but have to give props to kszaq for finding a way to get this done!
Cheers ...
Kodi should not boot loop ever. Try the "wait for network" option before you dismiss it.
Yeah - I have tried the wait for network option before - that's how I discovered Kodi would boot loop (at least on my installation) until the WAN was available. However, that was some time ago and probably when I was still using OpenELEC. I'll try again and also test by pulling power from my home router to see if I can reproduce a Kodi restart loop (just to be clear it is not LibreELEC rebooting, but only Kodi restarting, just as it would if I typed 'systemctl restart kodi' from the command line).
Do you have the 'Wait for network' option enabled?
No because sometimes my home router loses its WAN connection and needs rebooting to prevent Kodi from going into a reboot loop until the network is operational. Even though that is just an inconvenience, I'd prefer some other solution. As a long time linux user I understand init scripts and application load order. This is sometimes needed to satisfy dependencies. In the LibreELEC build of Kodi, there seems to be no such consideration - all apps seem to compete for network bandwidth as soon as the network becomes available.
I don't know enough of the LibreELEC internals to even guess if application load order is possible - if it is, it could be a place I'd contribute.
Wondering if there is any way to delay the loading (say for 10 seconds or so) of a specific addon (Stalker client) when Kodi starts up. I always get authentication failures with this, then success on a retry - it seems to try to authenticate before the network is completely ready (dhcp static IP). And occasionally I get Kodi restarting (not a LibreELEC reboot) and wonder if this may be related.
Does anyone know where/how i can resolve this? On boot VidoeoInfoScanner tries to process my TV Shows folder with this result:
07:32:19 T:139935260600064 NOTICE: VideoInfoScanner: Starting scan ..
07:32:19 T:139935260600064 WARNING: Process directory '/var/media/TOSHIBA EXT/TV Shows/' does not exist - skipping scan.
But the folder does exist and this appears to be a problem with spaces in the folder names. From the command line interface, I can tab out the path, ie:
LibreELEC:~ # ls /var/media/TOSHIBA\ EXT/TV\ Shows/
and of course if tried this, it fails:
LibreELEC:~ # ls /var/media/TOSHIBA EXT/TV Shows/
ls: /var/media/TOSHIBA: No such file or directory
ls: EXT/TV: No such file or directory
ls: Shows/: No such file or directory
Can I change the path(s) somewhere in Kodi and add the appropriate escapes?
[hr]
Found what works for me and that is to edit /storage/.kodi/userdata/sources.xml, adding escapes to the paths with spaces, eg changing:
<source>
<name>TV Shows</name>
<path pathversion="1">/var/media/TOSHIBA EXT/TV Shows/</path>
<allowsharing>true</allowsharing>
</source>
to:
<source>
<name>TV Shows</name>
<path pathversion="1">/var/media/TOSHIBA\ EXT/TV\ Shows/</path>
<allowsharing>true</allowsharing>
</source>
It's odd that actual TV show names containing spaces appear to be processed, so this might be a linux platform bug - don't have a Windows machine but afaik spaces in paths are never a problem on WIN platform. Also not sure whether it matters that the device being referenced (TOSHIBA\ EXT) is a USB attached external drive formatted as ntfs.
Tbh I'd just image your sd card (just in case) with eg win32diskimager or usbit (assuming you're using windows) and then not worry about it until it happens. I'm pretty sure marshmallow won't convert an sd card without a user input telling it to.
As it turns out, on booting the android system, it notifies me every time that the external sd card is corrupt, even though it mounts the LibreELEC system
(vfat) partition, but not the ext4 partition. So it also offers to 'fix' the external sd card by formatting it. Apparently it sees the partition as not ending on a cylinder boundary:
# fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 31.1 GB, 31104958464 bytes
4 heads, 16 sectors/track, 949248 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 * 33 16417 524288+ c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 16449 949248 29849600 83 Linux
Partition 2 does not end on cylinder boundary
That's a bit of a nuisance but of course the solution is to remove the external sdcard.
As an aside I would imagine I can safely delete the 'Android' and 'LOST.DIR' folders (I think) the android system wrote to the external sd card. See below:
# ls -l /storage/10D4-E16E/
total 135336
drwxrwx--x 4 root sdcard_rw 8192 Dec 31 2014 Android
drwxrwx--x 2 root sdcard_rw 8192 Dec 31 2014 LOST.DIR
-rwxrwx--x 1 root sdcard_rw 129531904 Oct 15 12:49 SYSTEM
-rwxrwx--x 1 root sdcard_rw 48 Oct 15 12:49 SYSTEM.md5
-rwxrwx--x 1 root sdcard_rw 1033 Oct 15 12:49 aml_autoscript
-rwxrwx--x 1 root sdcard_rw 159744 Oct 15 12:49 dtb.img
-rwxrwx--x 1 root sdcard_rw 37648 Nov 1 19:59 dtb.img.new
-rwxrwx--x 1 root sdcard_rw 8790016 Oct 15 12:49 kernel.img
-rwxrwx--x 1 root sdcard_rw 48 Oct 15 12:49 kernel.img.md5
-rwxrwx--x 1 root sdcard_rw 2492 Oct 13 15:48 remote.conf
-rwxrwx--x 1 root sdcard_rw 668 Oct 15 13:49 s905_autoscript
I'm actually a unix/linux guy and don't run windows. But I do run rsync over ssh backups of my installed systems to an external backup drive. Have been using OpenElec for a while on a more robust HTPC (Zotac ID91), recently moved that over to LibreElec. Rec'd an android TV box and discovered it would run the AmLogic port, so jumped in. Don't really care much for android (or for Google's control of the platform), but didn't want to remove it right away - there's always an opportunity to learn something. Thanks.
Maybe so - will have to check. Android 6 on a tv box is not so intuitive as on a phone since there isn't a touch screen interface and notifications can't be handled with a finger swipe. Seems I was able to dismiss the notice, but it may reappear since all I did was dismiss. Trying to use an airmouse is a little wobbly, but better than the infrared mouse included with the box. Anyhow your answer that I can choose to treat it as removable storage is what i will look for next time.
I would recommend a generic (ie. low cost) TV box with S905(optionally X) SoC that has 2 G ram and 16 or more G rom. The extra ram is cheap. It should have at least 2 external USB ports as you may want to use one for a wifi remote (I like the mini format, backlit type that come with a full keyboard and touchpad), audio out port (preferably SPDIF), sd card slot, gigabit ethernet port and optionally, wifi capability. These can be had for around $US 50. at amazon.
Have a fresh install of kszaq's LibreElec for Amlogic S905X on android device external sd card which works very well and which I may writetointernal. My question is how to prevent android 6.1 from modifying the sdcard if/when I reboot to android. It wants to treat the card as internal storage and as such offers to format the card. Of course this isn't wanted. Anyone know how to prevent this via system settings or otherwise? Thanks!
Ok. When looking inthere is an archive called gpu-2016-08-18-fe6d7b1d1b.tar.gz which seems to include some stuff for building for T82x and T83x support, but I'm not sure if that's what you are talking about?
This .pdf mentions support for S912 and Q200 board:
The easier way was to just drop the update .tar file into the 'updates' samba share on the OE box and reboot. Clean reinstall doesn't achieve much if you dirty it up straight away by restoring everything from the backup
I should also have asked whether the /flash partition has increased much in size from 0E 6.0.3? I'm currently using 77% of a 230Mb /flash which probably should have been larger when I originally installed. I know I can resize, but there is always risk. Thanks!
/dev/sda1 230.4M 174.0M 52.3M 77% /flash
The easier way was to just drop the update .tar file into the 'updates' samba share on the OE box and reboot. Clean reinstall doesn't achieve much if you dirty it up straight away by restoring everything from the backup
Is it just as simple to to revert to OE 6.0.3 if one finds issues? Have invested a lot of time in the setup of addons, so cautious about an upgrade. Thanks!
