Android Nougat V170612 Rom Release


#1

Here release the Android Nougat ROM

Check Firmware Page to download the ROM.

ROM Infos:

  • ROM version: Vim_Nougat_Root_170612.7z

  • MD5SUM: 2016d6fa96664e931dd1b0feb0d9d024

  • The ROM is for EMMC installation only

Change Log

  • Enable I2S bus(PIN29/30/31/32) as default
  • Fixup the issue of 4k video playing not smooth
  • Setup logo
  • Add the support for IR mouse mode
  • Update the GAPPS

Upgrade guidance:

Enjoy!


#2

Have two questions before flashing this rom.

  • does hardware decoding work with latest stable Kodi 17.0.3?
  • does this u-boot support ext4load ? because without it, users who use only one partition on micro SD can not boot that microSD

#3

Yes, it work on new rom.

Yes, it supports for that


#4

Yes confirmed that work, but there is weird info when loading uImage from microSD. Part type is for sure not DOS, it is an ext4 and it boots from this card…

kvim#setenv bootargs "console=ttyAML0,115200 root=/dev/mmcblk0p1 rootwait=1 rootdelay=2 rw ipv6.disable=1 init=/usr/bin/init"
kvim#ext4load mmc 0:1 ${loadaddr} /boot/uImage
card in
init_part() 278: PART_TYPE_DOS
[mmc_init] mmc init success
21760576 bytes read in 4677 ms (4.4 MiB/s)
kvim#ext4load mmc 0:1 $dtb_mem_addr /boot/dtbs/amlogic/meson-gxl-s905x-khadas-vim.dtb
19699 bytes read in 27 ms (711.9 KiB/s)
kvim#ping 8.8.8.8
Speed: 100, full duplex
Using dwmac.c9410000 device

Abort
ping failed; host 8.8.8.8 is not alive
kvim#bootm ${loadaddr} - $dtb_mem_addr

  1. can you push local changes of u-boot to nougat branch? because in github repository I dont see where ext4 was enabled

#5

Which Kodi apk to use with this ROM release? I don’t wont to sign-in in Play store just to install Kodi…


#6

@terry there is a big issue within this rom. I am not sure why but it did break the permission on microSD card which I have had for boot ArchLinuxArm. No data lost but owner is changed to something from Android.
I am not sure if I have had microSD durning flash of eMMC but in any way the ROM and ROM boot process should not change this. I know that i saw information that Android found microSD and if I would like to (brows, eject or setup the storage). I selected browse, which did not work. So i guess there is something wrong in image.

Now I need to recreate this microSD…

prove (i dont have 1023 as user or group in my ArchLinuxArm installation):

[root@khadasvimpro /]# ls -al
total 72
drwxr-xr-x 18 1023 1023 4096 Jun 13 09:03 .
drwxr-xr-x 18 1023 1023 4096 Jun 13 09:03 …
drwxrwxr-x 3 1023 1023 4096 Jun 13 09:03 Android
lrwxrwxrwx 1 1023 1023 7 Apr 1 03:33 bin -> usr/bin
drwxr-xr-x 3 1023 1023 4096 Jun 13 08:27 boot
drwxr-xr-x 15 root root 3020 Jun 13 09:01 dev
drwxr-xr-x 41 1023 1023 4096 Feb 1 02:09 etc
drwxr-xr-x 3 1023 1023 4096 May 27 23:09 home
lrwxrwxrwx 1 1023 1023 7 Apr 1 03:33 lib -> usr/lib
drwx------ 2 1023 1023 16384 May 25 15:41 lost+found
drwxr-xr-x 2 1023 1023 4096 Apr 1 03:33 mnt
drwxr-xr-x 3 1023 1023 4096 Jun 10 00:30 opt
dr-xr-xr-x 130 root root 0 Jan 1 1970 proc
drwxr-x— 3 1023 1023 4096 Jun 13 09:01 root
drwxr-xr-x 17 root root 480 Jun 13 20:33 run
lrwxrwxrwx 1 1023 1023 7 Apr 1 03:33 sbin -> usr/bin
drwxr-xr-x 4 1023 1023 4096 Apr 1 03:33 srv
dr-xr-xr-x 12 root root 0 Jan 1 1970 sys
drwxrwxrwt 9 root root 180 Jun 13 20:33 tmp
drwxr-xr-x 8 1023 1023 4096 Jun 13 08:30 usr
drwxr-xr-x 12 1023 1023 4096 Feb 1 02:09 var
[root@khadasvimpro /]# ls -al Android/
total 16
drwxrwxr-x 3 1023 1023 4096 Jun 13 09:03 .
drwxr-xr-x 18 1023 1023 4096 Jun 13 09:03 …
drwxrwxr-x 3 1023 1023 4096 Jun 13 09:03 data
[root@khadasvimpro /]# ls -al Android/data/
.nomedia com.google.android.gms/
[root@khadasvimpro /]# ls -al Android/data/


#7

I will update the github repository in this a few days

You can download the Kodi-17.3-Krypton


#8

I did and I enabled PVR addon pvr.vdr.vnsi which connect to VDR running in same Network. But LiveTV in HD is lagging/skipping frames with Khadas VIM Pro (using Ethernet). Watching same LiveTV in HD over Windows notebook (same Kodi version and PVR addon) is working without glitches.

As I live in Europe i changed Android resolution to 1080p@50Hz. There were so many force close of Resolution settings up that I could not count them. Do someone Test this image before release?

If you have any suggestion how to make this better let me know to test it. Otherwise this image isn’t working here.
Not to mention this problem with changing owner of microSD which break my ArchLinuxArm resolution @terry I hope i will get answer about this topic.


#9

@terry regarding changing owner when microSD is inserted. Does this code below do this? I marked the serial console output with command “chown” which is for changing ownership, but the rest of command I don’t understand.

@terry or someone from Khadas Support can you check this and fix?

kvim:/ $
kvim:/ $
[ 7882.485012@2] [aml_is_card_insert] card IN
_ 7882.588031@2] normal card in
[ 7882.588157@0] [aml_is_card_insert] card IN
[ 7882.589425@2] [aml_is_card_insert] card IN
[ 7882.949410@0] sd: new high speed SD card at address b368
[ 7882.949612@0] sd: clock 50000000, 4-bit-bus-width

[ 7882.960534@2] mmcblk1: sd:b368 2GU2M 1.87 GiB
[ 7882.968588@2] mmcblk1: p1
[ 7883.091302@1] EXT4-fs (mmcblk1p1): Ignoring removed nomblk_io_submit option
[ 7883.106308@1] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=remount-ro
[ 7883.193189@1] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data mode. Opts: (null)
[ 7883.372979@3] type=1400 audit(1497527060.020:36): avc: denied { getattr } for pid=6312 comm=“chown” path="/mnt/media_rw/521cd3fe-82e3-4bab-8dd2-f67aed5cca15/var/mail" dev=“mmcblk1p1” ino=35432 scontext=u:r:vold:s0 tcontext=u:object_r:mnt_media_rw_file:s0 tclass=lnk_file permissive=1
[ 7883.392919@3] type=1400 audit(1497527060.020:37): avc: denied { read } for pid=6312 comm=“chown” name=“mail” dev=“mmcblk1p1” ino=35432 scontext=u:r:vold:s0 tcontext=u:object_r:mnt_media_rw_file:s0 tclass=lnk_file permissive=1
[ 7883.412404@3] type=1400 audit(1497527060.020:38): avc: denied { setattr } for pid=6312 comm=“chown” name=“mail” dev=“mmcblk1p1” ino=35432 scontext=u:r:vold:s0 tcontext=u:object_r:mnt_media_rw_file:s0 tclass=lnk_file permissive=1
[ 7905.254675@3] type=1400 audit(1497527081.910:39): avc: denied { getattr } for pid=6317 comm=“sdcard” path="/mnt/media_rw/521cd3fe-82e3-4bab-8dd2-f67aed5cca15/var/log/journal/16b3c3b801d545908ec203cd7f7fd2dc/system.journal" dev=“mmcblk1p1” ino=29077 scontext=u:r:sdcardd:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=1
[ 7978.058849@3] type=1400 audit(1497527154.710:40): avc: denied { read } for pid=6335 comm=“MediaScannerSer” name=“gnutls-client-server-use-case.png” dev=“mmcblk1p1” ino=8090 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:mnt_media_rw_file:s0 tclass=file permissive=1
[ 7978.078365@3] type=1400 audit(1497527154.730:41): avc: denied { open } for pid=6335 comm=“MediaScannerSer” path="/mnt/media_rw/521cd3fe-82e3-4bab-8dd2-f67aed5cca15/usr/share/info/gnutls-client-server-use-case.png" dev=“mmcblk1p1” ino=8090 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:mnt_media_rw_file:s0 tclass=file permissive=1
[ 7978.107581@3] type=1400 audit(1497527154.730:42): avc: denied { getattr } for pid=6335 comm=“MediaScannerSer” path="/mnt/media_rw/521cd3fe-82e3-4bab-8dd2-f67aed5cca15/usr/share/info/gnutls-client-server-use-case.png" dev=“mmcblk1p1” ino=8090 scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:mnt_media_rw_file:s0 tclass=file permissive=1


#10

I gave up on Ubuntu until gpu drivers become available, i did flash Nougat yesterday, i still receive message “system ui has stopped”.

I did receive it with Nougat version from april, i hoped to avoid it with your latest build, because i didn’t have such issues with Marshmallow.

Problem is that the message repeats every few seconds, it won’t stop until i reboot or shut down the device.

It happens on daily basis, sometimes it works for few hours without showing up, and i can’t figure out what can be the cause of this, i tried looking in the settings, but i don’t see a solution.


#11

You can modify some files
###1. Modify the file ‘system/sepolicy/vold.te’

diff --git a/vold.te b/vold.te
index 8cea0c3..04ef95f 100644
--- a/vold.te
+++ b/vold.te
@@ -47,6 +47,7 @@ allow vold sdcard_type:file create_file_perms; # TODO: depreca
 # Manage locations where storage is mounted
 allow vold { mnt_media_rw_file storage_file sdcard_type }:dir create_dir_perms;
 allow vold { mnt_media_rw_file storage_file sdcard_type }:file create_file_perm
+allow vold mnt_media_rw_file:lnk_file { getattr setattr read };
 
 # Access to storage that backs emulated FUSE daemons for migration optimization
 allow vold media_rw_data_file:dir create_dir_perms;

###2. Modify the file ‘system/sepolicy/sdcardd.te’

diff --git a/sdcardd.te b/sdcardd.te
index 846c59b..073d608 100644
--- a/sdcardd.te
+++ b/sdcardd.te
@@ -31,6 +31,7 @@ allow sdcardd vold:fifo_file { read write getattr };
 # Allow running on top of expanded storage
 allow sdcardd mnt_expand_file:dir search;
 
+allow sdcardd unlabeled:file  { getattr };
 ###
 ### neverallow rules
 ###

###3.Modify the file ‘system/sepolicy/priv_app.te’

diff --git a/priv_app.te b/priv_app.te
index 85516a6..8176210 100644
--- a/priv_app.te
+++ b/priv_app.te
@@ -40,6 +40,7 @@ allow priv_app recovery_service:service_manager find;
 # Traverse into /mnt/media_rw for bypassing FUSE daemon
 # TODO: narrow this to just MediaProvider
 allow priv_app mnt_media_rw_file:dir search;
+allow priv_app mnt_media_rw_file:file { read open getattr setattr };

#12

Did you receive message “system ui has stopped” when you flash the latest nougat rom(V170612)?


#13

Yes, it happens with latest Nougat, it is very annoying.


#14

Can you provide the android log and kernel log for me when it happens?
Thanks


#15

@terry I am not sure what does this with “You can modify some files” help me? Can you explain it a bit more.

In my opinion no OS should change owner/permission of an medium from which is not booted (in my case with micro SD card), so this is for me Android Nougat bug in image you use to be able to read this micro SD card. I am not sure if does this with Marshmallow to.


#16

How can i provide these logs, i have never done that?


#17

You can follow below method to take the log

adb connect IP-ADDR-OF-YOUR-DEVICE
adb shell dmesg > kernel.log
adb shell logcat > android.log

#18

I am not sure if i will do it today, but can you tell me where will i send it, by e-mail or shall i paste it here?


#19

You can share the download link for me in this post


#21

Thanks for your feedback. I will have a test for it and will reply for you.