Android-x86 5.1-rc1 release

[Chih-Wei Huang]

I'm too tired to explain more.
Just download and enjoy it.

Many thanks to Povilas Staniulis
who provided the new hosting of
dl.android-x86.org


PS. Google also released the source of
Android 6.0 marshmallow yesterday.
Will begin the porting soon.


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

[oscar bg]

Hi,

first some questions:

*seems is first build with 64bit user space, right? I say that because we have had 64 bit kernel support for a while..

Bad thing is requires the UEFI image so my PC with traditional BIOS altough CPU (Q9450) supports 64 bit can't run 64bit Android..

*today Surface pro 4 and Surface book have been announced.. do you expect that this build will run in this devices (i.e. Skyake GPU support?)

*Also seems this release ships with Mesa 11.0.2 very new, but supports OpenGL ES 3.0 on Android? things will get interesting

once we get OpenGL ES 3.1 in Mesa (11.1 this year?) hope we get also on Android-x86..

also some suggestion:

since Mesa supports full OpenGL contexts in addition to OpenGL ES contexts created via EGL API selection can you support also

full OpenGL contexts on Android similar to NVidia Shield Tablet supports..

i.e. support OpenGL in EGL_RENDERABLE_TYPE

see for example Shield Tablet gfxbench report:

https://gfxbench.com/resultdetails.jsp?resultid=hSmWKjDNbkDzGAPsqQ5d8Q

It says:

EGL_RENDERABLE_TYPE:

OpenGL_ES OpenGL_ES_2 OpenGL (77)

thanks..

Oscar.

[Chih-Wei Huang]

2015-10-07 12:17 GMT+08:00 oscar bg <rtf...@gmail.com>:
> Hi,
> first some questions:
>
> *seems is first build with 64bit user space, right? I say that because we
> have had 64 bit kernel support for a while..
> Bad thing is requires the UEFI image so my PC with traditional BIOS altough
> CPU (Q9450) supports 64 bit can't run 64bit Android..

I decided not to release the android_x86_64 iso file
(as well as android_x86 efi file)
to reduce the releasing effort.
Because the more files I've to release,
the more work I have to do.
But if more people think it's useful, I can re-consider.

You can easily derive it by copying the necessary files
(kernel,initrd.img,ramdisk.img,system.sfs,install.img)
to a bootable (legacy grub or similar) usb disk
and create a boot entry for it.
Or, you can build the android_x86_64 iso_img
from source yourself.

> *today Surface pro 4 and Surface book have been announced.. do you expect
> that this build will run in this devices (i.e. Skyake GPU support?)

I don't know.
You may check whether if kernel 4.0 and mesa 11 support it.

> *Also seems this release ships with Mesa 11.0.2 very new, but supports
> OpenGL ES 3.0 on Android? things will get interesting
> once we get OpenGL ES 3.1 in Mesa (11.1 this year?) hope we get also on
> Android-x86..

Yes, I saw ES 3.1 patches are proposed to mesa-dev list.
However I'm not sure the merging status.
We'll follow once they get merged.

> also some suggestion:
> since Mesa supports full OpenGL contexts in addition to OpenGL ES contexts
> created via EGL API selection can you support also
> full OpenGL contexts on Android similar to NVidia Shield Tablet supports..
> i.e. support OpenGL in EGL_RENDERABLE_TYPE
> see for example Shield Tablet gfxbench report:
>
> https://gfxbench.com/resultdetails.jsp?resultid=hSmWKjDNbkDzGAPsqQ5d8Q
>
> It says:
> EGL_RENDERABLE_TYPE:OpenGL_ES
> OpenGL_ES_2
> OpenGL
> (77)

I have no idea about that topic.
Patches are welcome.

[Tom Briden]

The manifest is still pointing to kitkat branches for the bluetooth/{bluez,sbc,glib} repos. is this right?

[Chih-Wei Huang]

2015-10-07 18:58 GMT+08:00 Tom Briden <tbr...@googlemail.com>:
> The manifest is still pointing to kitkat branches for the
> bluetooth/{bluez,sbc,glib} repos. is this right?

OOPS! That's not right.
I was really too tired...
Now corrected.
Thank you!

[Petr Dolak]

Hi guys, does anybody of was able to boot this on Asus T100?

android-x86-5.1-rc1.iso is not bootable and android-x86_64-5.1-rc1.img boots, but not working - kernel panic. segfault on libc.so

I tried to update bootable magic stick with 32bit version, but even then, it was not working - some flickering of linux terminal is only visible. No gui.

[IamBackX5]

T100TA-64G-Z3740... it's working like KitKat, more unstable WiFi, others things similar as for me...

iso and img also don't boot, but installed by my installer: http://www.youtube.com/watch?v=jTyTtt6pQzY it works on my T100 :D Maybe your data is incompatible?

среда, 7 октября 2015 г., 19:21:31 UTC+5 пользователь Petr Dolak написал:

[Petr Dolak]

I was impatient, during a boot. No it is up and running :-)

I tried it first without my "data" to see how it works.

As stated in release note, suspend doesn't work... Screen is only dimmed. Let me do more tests...

Great work!

[Chih-Wei Huang]

2015-10-07 22:21 GMT+08:00 Petr Dolak <dolak...@gmail.com>:
> Hi guys, does anybody of was able to boot this on Asus T100?
> android-x86-5.1-rc1.iso is not bootable and android-x86_64-5.1-rc1.img
> boots, but not working - kernel panic. segfault on libc.so
> I tried to update bootable magic stick with 32bit version, but even then, it
> was not working - some flickering of linux terminal is only visible. No gui.

I'm 100% sure android-x86_64-5.1-rc1.img
is bootable and workable on T100.
The image should just be "dumped"
to a usb disk, like

dd if=android-x86_64-5.1-rc1.img of=/dev/sdX

(or use similar tool like WinDD on Windows)

How did you use it?

[Petr Dolak]

I did it in same way... (dd ...)

This is pringscreen just before reboot.

[Chih-Wei Huang]

You booted from usb disk. Didn't you?
Why did it detect android-x86 at /dev/mmcblk0p4?
That means you have an old installation at /dev/mmcblk0p4.
Please remove it to avoid wrong detection.
Or, add ROOT=/dev/sda1 to cmdline
to force it choose the usb disk.

2015-10-08 0:51 GMT+08:00 Petr Dolak <dolak...@gmail.com>:
> I did it in same way... (dd ...)
>
> This is pringscreen just before reboot.
>
>
>

> --
> 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 post to this group, send email to andro...@googlegroups.com.
> Visit this group at http://groups.google.com/group/android-x86.
> For more options, visit https://groups.google.com/d/optout.

[Petr Dolak]

Very good point! Yes, I used USB stick, I wanted to see first how new rc behaves.

Now it make sense, I was not able to use old system image compiled for 32bit arch. as kernel is already 64bit.

Thank you!!

Looks 64bit version works good. I will try to do some tests to see how it works in general. 

As I stated before, suspend is not working, backlight is almost turned of but not completely and there still visible output on screen. No black color like on 4.4

Seems that kernel 4.2 is able to turn backlight completely. Are you planing to update it anytime soon?

And playback of video using youtube app also doesn't work. I will try to investigate it using logcat later on.

Otherwise so far so good.

[oscar bg]

Thanks for answes..

El miércoles, 7 de octubre de 2015, 9:29:35 (UTC+2), Chih-Wei Huang escribió:

2015-10-07 12:17 GMT+08:00 oscar bg <rtf...@gmail.com>:
> Hi,
> first some questions:
>
> *seems is first build with 64bit user space, right? I say that because we
> have had 64 bit kernel support for a while..
> Bad thing is requires the UEFI image so my PC with traditional BIOS altough
> CPU (Q9450) supports 64 bit can't run 64bit Android..

I decided not to release the android_x86_64 iso file
(as well as android_x86 efi file)
to reduce the releasing effort.
Because the more files I've to release,
the more work I have to do.
But if more people think it's useful, I can re-consider.

You can easily derive it by copying the necessary files
(kernel,initrd.img,ramdisk.img,system.sfs,install.img)
to a bootable (legacy grub or similar) usb disk
and create a boot entry for it.
Or, you can build the android_x86_64 iso_img
from source yourself.


> *today Surface pro 4 and Surface book have been announced.. do you expect
> that this build will run in this devices (i.e. Skyake GPU support?)

I don't know.
You may check whether if kernel 4.0 and mesa 11 support it.

thanks in that case no support may be expected.. but also related to full OpenGL support eventually LLVM version will be important to radeonsi support.. for example

tesselation shaders and perhaps fp64 support extensions new LLVM 3.7.0.. with it we get GL4.1 support  with LLVM 3.6.x we get only OpenGL 3.3 support..

can you answer LLVM version used and if it depends on a globally one set by Android source code base or you can use whichever LLVM version you want just for Mesa (in that case it's statically linked right?)..

 

> *Also seems this release ships with Mesa 11.0.2 very new, but supports
> OpenGL ES 3.0 on Android? things will get interesting
> once we get OpenGL ES 3.1 in Mesa (11.1 this year?) hope we get also on
> Android-x86..

Yes, I saw ES 3.1 patches are proposed to mesa-dev list.
However I'm not sure the merging status.
We'll follow once they get merged.

> also some suggestion:
> since Mesa supports full OpenGL contexts in addition to OpenGL ES contexts
> created via EGL API selection can you support also
> full OpenGL contexts on Android similar to NVidia Shield Tablet supports..
> i.e. support OpenGL in EGL_RENDERABLE_TYPE
> see for example Shield Tablet gfxbench report:
>
> https://gfxbench.com/resultdetails.jsp?resultid=hSmWKjDNbkDzGAPsqQ5d8Q
>
> It says:
> EGL_RENDERABLE_TYPE:OpenGL_ES
> OpenGL_ES_2
> OpenGL
> (77)

I have no idea about that topic.
Patches are welcome.

In that case I'm no expert in Mesa or Android code base.. can you point me better place to ask this question is Mesa-dev or créate new message in this mailing list or ask directly developers like Mauro Rossi?

thanks..

[Umberto Ixxo]

on tablet
CPU : Intel Atom Z3735F ok boot .
I report :
1 ) that the MP4 video and youtube app does not work you only hear the audio .
to see the video I have to use VLC . youtube to use tubermate .

2 ) orientation of the display and choir . I have to disable .

3 ) I have the random reboots de logo Andorid .

Thanks for what you do . keep it up

[jimmy hopkins]

^^^Yea same here dont know my desktop support or not this version but kitkat 4.4.4 r3 work fine.I had download and tried both version 32and64...for 32 version i got bootloop at android logo during startup livecd, my usb flashdrive stop blinking..and for 64, i cant get even boot to usb... i dont know what cause it...thanks and sorry for bad english.

This is my spec:
HP Compaq dc5850 Small Form Factor
Default System BIOS
AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ (2 CPUs), ~3.1GHz
ATI Radeon 3100 Graphics

[藤井八雲]

Question: Is that if I am using a 32 bit EIF system, I have to convent the ISO to DD image?

[Chih-Wei Huang]

2015-10-08 11:03 GMT+08:00 藤井八雲 <gggy...@gmail.com>:
> Question: Is that if I am using a 32 bit EIF system, I have to convent the
> ISO to DD image?

Use android-x86_64-5.1-rc1.img

[藤井八雲]

It works in live now and I am going to install it, thank you

Chih-Wei Huang於 2015年10月7日星期三 UTC-4下午11時18分04秒寫道：

[Kamalakar Agashe]

Works in live but installation does not work on my Lenovo Laptop. Live also reboots on trying to enter gmail account. I have added ext4 file to live to save settings.
I could get the Desktop after skipping adding gmail account.
Kamalakar

[Spirit BLACKDIAMONT]

Hi @all,

i've running 4.4 on 2 Devices without problems(yet).

i've tried 5.1 on my Asus x205ta and everything works execpt the google playstore
doesn't work, i can't download any apps ...

same on my other machine after i've upgraded it from 4.4, playstore is broken :(

is there a fix or something?
greetings
Spirit

[jimmy hopkins]

please anyone...i got bootloop forever at android logo with this 32version live mod.how can i fix this. :/

again my desktop:

[jimmy hopkins]

On Tuesday, October 6, 2015 at 6:34:44 PM UTC-7, Chih-Wei Huang wrote:

Help me ...im stuck at android logo in live mode and after installed.
Do my desktop support it?if not then please make it support for future release.thx
Test on:
 HP Compaq dc5850 SFF

[Wei Xu]

Great job. GMA500 works.

Thank you very much.

在 2015年10月7日星期三 UTC+8上午9:34:44，Chih-Wei Huang写道：

[Geek Till It Hertz]

Are both the builds 64bit, if not will the EFI .img build work in legacy boot mode? (my mother board supports efi but i just run it on legacy.)

[Marco Ziliani]

Il giorno mercoledì 7 ottobre 2015 03:34:44 UTC+2, Chih-Wei Huang ha scritto:

> I'm too tired to explain more.
> Just download and enjoy it.
>
> Many thanks to Povilas Staniulis
> who provided the new hosting of
> dl.android-x86.org
>
>
> PS. Google also released the source of
> Android 6.0 marshmallow yesterday.
> Will begin the porting soon.
>
>
> --
> Chih-Wei
> Android-x86 project
> http://www.android-x86.org

Why have I got problems to connect to git repo primery repo?

[code]fatal: unable to access 'http://git.android-x86.org/manifest/': The requested URL returned error: 503[/code]

and on SourceForge.net there isn't the Lollipo branch...

[code]fatal: Couldn't find remote ref refs/heads/lollipop-x86[/code]

Thanks,
Marco

[Petr Dolak]

Hi, today I tried to install Android 5.1rc1 on internal storage, but booting end up with this loop:

<3>[  169.239390] x_tables: ip_tables: owner match: used from hooks INPUT, but only valid from OUTPUT/POSTROUTING

<3>[  169.248169] x_tables: ip6_tables: owner match: used from hooks INPUT, but only valid from OUTPUT/POSTROUTING

<13>[  169.262371] init: /sbin/modprobe net-pf-16-proto-5

<11>[  169.291410] init: Couldn't probe module 'net-pf-16-proto-5

I tried 32bit and 64bit versions, but both behaves same. I have installed ubuntu as main OS and android 4.4 on separate partition.

This is my configuration of grub. Android 4.4 works fine.

menuentry "Android 4.4" {

set root='(hd0,gpt4)' 

linux /44/kernel quiet root=/dev/ram0 androidboot.hardware=generic_x86 acpi_sleep=s3_bios,s3_mode ROOT=/dev/mmcblk0p4 SRC=/44/ 

initrd /44/initrd.img

}

menuentry "Android 5.1 32bit" {

        set root='(hd0,gpt4)' 

        linux /51_32/kernel root=/dev/ram0 androidboot.hardware=generic_x86    acpi_sleep=s3_bios,s3_mode ROOT=/dev/mmcblk0p4 SRC=/51_32/ 

        initrd /51_32/initrd.img

}

menuentry "Android 5.1 64bit" --class android-x86 {

        set root='(hd0,gpt4)' 

        linux /51_64/kernel root=/dev/ram0 androidboot.hardware=generic_x86_64 acpi_sleep=s3_bios,s3_mode ROOT=/dev/mmcblk0p4 SRC=/51_64/ 

        initrd /51_64/initrd.img

}

And this is content of /dev/mmcblk0p4 partition:

./44

./44/initrd.img

./44/install.img

./44/kernel

./44/ramdisk.img

./44/system.img

./44/data/ <- data folder

./51_32

./51_32/initrd.img

./51_32/install.img

./51_32/kernel

./51_32/ramdisk.img

./51_32/system.sfs

./51_64

./51_64/initrd.img

./51_64/install.img

./51_64/kernel

./51_64/ramdisk.img

./51_64/system.sfs

Also I tried to convert system.sfs to .img format without any improvement.

When I booted from your prepared images, it boot up correctly.

Thank you for any advises.

[Poe Bear]

On Tuesday, October 6, 2015 at 6:34:44 PM UTC-7, Chih-Wei Huang wrote:

> I'm too tired to explain more.
> Just download and enjoy it.
>
> Many thanks to Povilas Staniulis
> who provided the new hosting of
> dl.android-x86.org
>
>
> PS. Google also released the source of
> Android 6.0 marshmallow yesterday.
> Will begin the porting soon.
>
>

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

Is it possible to request some drivers for the next RC? I have a Chinese tablet I recently picked up (Jumper EZpad mini2, Intel Z3735F based), and it boots up, but it's missing a lot: Touchscreen, rotation, bluetooth, and sound. It was originally dual boot with Android 4.4 and Windows 8.1, but due to the small SSD (64GB), I ended up wiping everything and using just Windows 10, so I no longer have access to the Android partition to get drivers. But here is what's not working, info pulled from the Windows Device Manager

Accelerometer: Bosch BMA250E, Rotation Sensor: Kionix, Audio: Intel SST with Realtek I2S codec, Touchscreen: Silead MSSL 1680, Bluetooth: Realtek RTL8723BS

I can navigate the RC live image with a keyboard and mouse, so if there's any info I can pull from there that might be helpful, let me know. Thanks!

[Mauro Rossi]

Hi Chih-Wei,

I'm getting building errors in llvm R600 modules when building iso_img for android-x86_64 target,

the errors are in the attachment and are related to generated files not found when LOCAL_C_INCLUDES is specified as a path related to $(intermediates)

The following patch, tested for x86 and x86_64 target and proposed for review, solves the problem:

https://github.com/maurossi/llvm/commit/27c7754556c81dd63b26eab951790a74b4502b07.patch

Mauro

[Chih-Wei Huang]

But I didn't see such an error.
The file are generated correctly in my tree.

$ locate AMDGPUGenMCCodeEmitter.inc
/home/cwhuang/git/android-x86-5.1/out/target/product/x86/gen/STATIC_LIBRARIES/libLLVMR600CodeGen_intermediates/AMDGPUGenMCCodeEmitter.inc
/home/cwhuang/git/android-x86-5.1/out/target/product/x86/obj/STATIC_LIBRARIES/libLLVMR600CodeGen_intermediates/AMDGPUGenMCCodeEmitter.inc
/home/cwhuang/git/android-x86-5.1/out/target/product/x86_64/gen/STATIC_LIBRARIES/libLLVMR600CodeGen_intermediates/AMDGPUGenMCCodeEmitter.inc
/home/cwhuang/git/android-x86-5.1/out/target/product/x86_64/obj/STATIC_LIBRARIES/libLLVMR600CodeGen_intermediates/AMDGPUGenMCCodeEmitter.inc
/home/cwhuang/git/android-x86-5.1/out/target/product/x86_64/obj_x86/STATIC_LIBRARIES/libLLVMR600CodeGen_intermediates/AMDGPUGenMCCodeEmitter.inc


After deeper looking I think it's a missing dependency issue.
libLLVMR600Info, libLLVMR600Desc must depend on
libLLVMR600CodeGen to ensure the *.inc
are generated first.

I'll make a correct fix later.

[Chih-Wei Huang]

I've pushed the fix.
Thank you for finding the error.

[Mahmud Baki]

> I decided not to release the android_x86_64 iso file
> (as well as android_x86 efi file)

would you please release android_x86 efi file, or give instruction how to build efi for 32 bit build. I tried following the instruction at Porting Android to x86 but keep getting error in repo sync, I know it is mentioned ther "Do not bother us with any of the syncing problem"

Is there any way i can make android_x86 efi file from android_x86 iso?

thank you

[Chih-Wei Huang]

2015-10-17 7:37 GMT+08:00 Mahmud Baki <its.m...@gmail.com>:
>
>> I decided not to release the android_x86_64 iso file
>> (as well as android_x86 efi file)
>
> would you please release android_x86 efi file, or give instruction how to build efi for 32 bit build. I tried following the instruction at Porting Android to x86 but keep getting error in repo sync, I know it is mentioned ther "Do not bother us with any of the syncing problem"

Have you tried the new git server now?
The GetSource page has been updated.
Just read the try again if you haven't done that.

> Is there any way i can make android_x86 efi file from android_x86 iso?

Yes.
You can download the 64-bit efi image and
create a bootable usb disk.
(by linux dd utility or windows equivalent tool)
The copy these files from the 32-bit iso
to the usb disk to replace the same name files:
initrd.img install.img kernel ramdisk.img system.sfs
Then modify the
androidboot.hardware=android_x86_64
to androidboot.hardware=android_x86
in the file /efi/boot/grub.cfg on the usb disk
That's all. Simple?

But I doubt whether if you need to do this.
So far I haven't heard a device has
32-bit CPU with uefi bios.
All device with uefi bios should have 64-bit CPUs.

What's your platform exactly?
If it's the notorious Baytrail tablet
with 32-bit uefi bios,
just use the android-x86_64-5.1-rc1.img.
It's 100% bootable on your device.
That's because the img also has
a 32-bit efi bootloader and our kernel
supports efi mixed mode.
It can hand over to 64-bit kernel mode
without issues.
(Note Baytrail is a 64-bit CPU)

[Mahmud Baki]

Yes.
You can download the 64-bit efi image and
create a bootable usb disk.
(by linux dd utility or windows equivalent tool)
The copy these files from the 32-bit iso
to the usb disk to replace the same name files:
initrd.img install.img kernel ramdisk.img system.sfs
Then modify the
androidboot.hardware=android_x86_64
to androidboot.hardware=android_x86
in the file /efi/boot/grub.cfg on the usb disk
That's all. Simple?

I just tried, I used  rufus-2.4 dd image writing. With 64 files, it boots normal, if I copy 32bit files, and change grub.cfg, it stuck at black screen.

Ant solution?

thank you

[Mahmud Baki]

Thank you so much!!. I will try this.

 

But I doubt whether if you need to do this.
So far I haven't heard a device has
32-bit CPU with uefi bios.
All device with uefi bios should have 64-bit CPUs.

What's your platform exactly?
If it's the notorious Baytrail tablet
with 32-bit uefi bios,
just use the android-x86_64-5.1-rc1.img.
It's 100% bootable on your device.
That's because the img also has
a 32-bit efi bootloader and our kernel
supports efi mixed mode.
It can hand over to 64-bit kernel mode
without issues.
(Note Baytrail is a 64-bit CPU)

 

I have intel i5 with asus sabertooth mb. booting is not the issue. I wanted to get root access, but want to boot independently from mb boot menu.

I have Windows, ubuntu, mac osx installed in my pc. all of them using efi boot, for Android x86, I used to create a boot entry in ubuntu and boot from there. But i would like android's boot entry itself in mb boot entry. Thats why i wanted efi 32 bit.

If 64 bit can get root access then I am ok with that too.

Thank you again!!

[Chih-Wei Huang]

2015-10-18 14:02 GMT+08:00 Mahmud Baki <its.m...@gmail.com>:
>
> I have intel i5 with asus sabertooth mb. booting is not the issue. I wanted
> to get root access, but want to boot independently from mb boot menu.
> I have Windows, ubuntu, mac osx installed in my pc. all of them using efi
> boot, for Android x86, I used to create a boot entry in ubuntu and boot from
> there. But i would like android's boot entry itself in mb boot entry. Thats
> why i wanted efi 32 bit.

I don't see how this is related to 32-bit system.

Anyway, no matter you want 32-bit or 64-bit system,
just copy the four files
initrd.img kernel ramdisk.img system.sfs
into your disk and create a boot entry for it.
If you want system to be read-write,
unpack system.sfs to system.img.

> If 64 bit can get root access then I am ok with that too.

This is fixed in the latest source tree.
(credited to pstglia)

[Stefan Svensson]

Where can I get it? Looks like the link redirects to houdini?

Thank you!

Den onsdag 7 oktober 2015 kl. 03:34:44 UTC+2 skrev Chih-Wei Huang:

I'm too tired to explain more.
Just download and enjoy it.

Many thanks to Povilas Staniulis
who provided the new hosting of
dl.android-x86.org


PS. Google also released the source of
Android 6.0 marshmallow yesterday.
Will begin the porting soon.

[Ekapol tassaneeyasin]

http://www.android-x86.org/download

[Zeeshan Ahmed P]

Just tested the build on my Notion Ink Cain 10 tablet, and its awesome. Haven't tried any build so smooth till now. Everything works except for bluetooth, camera and the tablet restarts when I detach the keyboard.

But Anyways it has everything working that I need. Keep up the awesome work and thanks a lot for the build

On Wednesday, October 7, 2015 at 7:04:44 AM UTC+5:30, Chih-Wei Huang wrote:

[stavros daliakopoulos]

I found this about net-pf 

http://www.losurs.org/docs/tips/general/net-pf-list

[Zeeshan Ahmed P]

I tested this build on my tablet acer one 10, it boots and runs smoothly, but touchscreen, bluetooth, orientation  and battery indicators do not work.

I just wish I could some how get the touch screen working. I tried finding out the touchpanel on the tablet through device manager but didnt find any luck with that.

I ran lsmod and the result is attached. Any help would be much appreciated. Thank you 

On Wednesday, October 7, 2015 at 7:04:44 AM UTC+5:30, Chih-Wei Huang wrote:

I'm too tired to explain more.
Just download and enjoy it.

Many thanks to Povilas Staniulis
who provided the new hosting of
dl.android-x86.org


PS. Google also released the source of
Android 6.0 marshmallow yesterday.
Will begin the porting soon.