Asus M80TA cant run v8.1-r3 or v9.0-rc1

[Mydaet]

I can't manage to run latest v8.1-r3 or v9.0-rc1 on my Asus M80TA using original version downloaded from android-x86.org

The latest version I can install was v8.1-rc1.

Please advise how to make it run the latest version.

x86:/ $ su
x86:/ # cat /sys/class/dmi/id/uevent
MODALIAS=dmi:bvnAmericanMegatrendsInc.:bvrM80TA.213:bd06/27/2019:svnASUSTeKCOMPUTERINC.:pnM80TA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnM80TA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
x86:/ #

System Manufacturer: ASUSTeK COMPUTER INC.
System Model: M80TA
BIOS: M80TA.213 (type: UEFI)
Processor: Intel(R) Atom(TM) CPU Z3740 @ 1.33GHz (4 CPUs), ~1.3GHz
Display Devices Card name: Intel(R) HD Graphics
Manufacturer: Intel Corporation
Chip type: Intel(R) HD Graphics

[Chih-Wei Huang]

Have you tried the kernel 4.9 version? (8.1-r3-k49)

Mydaet <mr.anw...@gmail.com> 於 2019年12月8日 週日 上午9:54寫道：

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Anwar Sadat]

Thanks for replying. 

I haven’t try. Sorry, how to get that version of the kernel?

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/android-x86/CAKc24n06SneJ6HYRFJW6cn5Vnuq-mCgTxG0t-fZSO9z%3DZxJR-Q%40mail.gmail.com.

[Chih-Wei Huang]

Anwar Sadat <mr.anw...@gmail.com> 於 2019年12月9日 週一 下午2:44寫道：

>
> Thanks for replying.
> I haven’t try. Sorry, how to get that version of the kernel?

https://www.android-x86.org/releases/releasenote-8-1-r3.html

[Mydaet]

Sorry for not mentioning earlier; I use the 32 bit version, because never success to use 64 bit. Although in windows system it was said that the processor is 64 bit, but the UEFI is 32 bit version.

My question, is this 64-bit ISO with kernel 4.9: android-x86_64-8.1-r3-k49.iso will support 32 bit UEFI?

Thanks in advance,

[Chih-Wei Huang]

Mydaet <mr.anw...@gmail.com> 於 2019年12月9日 週一 下午5:21寫道：

>
> Sorry for not mentioning earlier; I use the 32 bit version, because never success to use 64 bit. Although in windows system it was said that the processor is 64 bit, but the UEFI is 32 bit version.
> My question, is this 64-bit ISO with kernel 4.9: android-x86_64-8.1-r3-k49.iso will support 32 bit UEFI?

Yes.
Also works in ASUS T100TA (with a similar spec).

[Mydaet]

Hi,
Thanks a lot for your support.
I installed this 64bit version with kernel 49.
It works. In fact, I replied this using this version of Android-x86 v8.1-r3 64bit kernel 49.
Still found some apps not responding, thou. May be because I used old data.img from rc1.

Additional note:
Please change line for M80TA in init.sh to line as below. It suppose to be y instead of x as in original file from installer.

set_property ro.iio.accel.y.opt_scale -1

Thanks again for your help.
Cheers.

[Chih-Wei Huang]

Mydaet <mr.anw...@gmail.com> 於 2019年12月9日 週一 下午8:25寫道：

>
> Hi,
> Thanks a lot for your support.
> I installed this 64bit version with kernel 49.
> It works. In fact, I replied this using this version of Android-x86 v8.1-r3 64bit kernel 49.
> Still found some apps not responding, thou. May be because I used old data.img from rc1.
>
> Additional note:
> Please change line for M80TA in init.sh to line as below. It suppose to be y instead of x as in original file from installer.
>
> set_property ro.iio.accel.y.opt_scale -1

I'll change init.sh. Thank you!

[netanelg]

Hello!

I have the same device and the same issue..

I have been using cm14-r3 32bit on my tablet with no big issues, and i'm trying now install android 9.0-rc1.

When I try to boot android 9.0-rc1 on my tablet it gets stuck after the detection phase ("detecting Android-x86... found at...")

I've managed to boot to debug mode and exit the shell on the first console, and get dmesg output on the second console

the whole file is attched and the last lines that I think that are relevant are:

[   77.440932] init: wait for '/dev/.coldboot_done' timed out and took 60002ms

[   77.476972] init: Timed out waiting for /dev/.coldboot_done

[   77.487506] init: Reboot start, reason: reboot, rebootTarget: bootloader

[   77.498275] init: Shutdown timeout: 6000 ms

[   77.509420] init: starting service 'blank_screen'...

[   77.520441] init: starting service 'hwservicemanager'...

[   77.531396] init: starting service 'servicemanager'...

[   77.531436] init: couldn't write 2597 to /dev/cpuset/system-background/tasks: No such file or directory

[   77.541731] init: couldn't write 2598 to /dev/cpuset/system-background/tasks: No such file or directory

[   77.542093] init: starting service 'vold'...

[   77.865552] audit: type=1400 audit(1576599639.926:79): avc:  denied  { getattr } for  pid=2596 comm="blank_screen" path="/vendor" dev="tmpfs" ino=8379 scontext=u:r:blank_screen:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=1

[   77.896353] audit: type=1400 audit(1576599639.926:80): avc:  denied  { read } for  pid=2596 comm="blank_screen" name="vendor" dev="tmpfs" ino=8379 scontext=u:r:blank_screen:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=1

[   77.926454] audit: type=1400 audit(1576599639.948:81): avc:  denied  { getattr } for  pid=2597 comm="hwservicemanage" path="/vendor" dev="tmpfs" ino=8379 scontext=u:r:hwservicemanager:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=1

[   77.957130] audit: type=1400 audit(1576599639.948:82): avc:  denied  { read } for  pid=2597 comm="hwservicemanage" name="vendor" dev="tmpfs" ino=8379 scontext=u:r:hwservicemanager:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=1

[   77.990455] audit: type=1400 audit(1576599639.956:83): avc:  denied  { getattr } for  pid=2598 comm="servicemanager" path="/vendor" dev="tmpfs" ino=8379 scontext=u:r:servicemanager:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=1

[   78.021462] audit: type=1400 audit(1576599639.956:84): avc:  denied  { read } for  pid=2598 comm="servicemanager" name="vendor" dev="tmpfs" ino=8379 scontext=u:r:servicemanager:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=1

[   78.061744] audit: type=1400 audit(1576599639.992:85): avc:  denied  { sys_nice } for  pid=2603 comm="init" capability=23  scontext=u:r:init:s0 tcontext=u:r:init:s0 tclass=capability permissive=1

[   78.095213] audit: type=1400 audit(1576599640.024:86): avc:  denied  { getattr } for  pid=2599 comm="vold" path="/vendor" dev="tmpfs" ino=8379 scontext=u:r:vold:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=1

[   78.126799] audit: type=1400 audit(1576599640.024:87): avc:  denied  { read } for  pid=2599 comm="vold" name="vendor" dev="tmpfs" ino=8379 scontext=u:r:vold:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=1

[   78.158257] audit: type=1400 audit(1576599640.040:88): avc:  denied  { getattr } for  pid=2600 comm="android.hardwar" path="/vendor" dev="tmpfs" ino=8379 scontext=u:r:hal_light_default:s0 tcontext=u:object_r:tmpfs:s0 tclass=lnk_file permissive=1

just for the fun i've tried to use the kernel and initrd.img files from cm14-r3 and then android does finish booting but with no pen & touch at very low resulotion...