Android-x86 5.1.1 custom builds

[JJ Meijer]

Hello everybody,

Here are some builds: https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE

About the latest build android-5.1.1-x86_kernel-4.1.14_mesa-10.6.X_intel-pci-drm_iso

Includes:
Kernel 4.1.14 (Long-term supported kernel, https://github.com/meijjaa/linux/tree/android-longterm) fast and stable
Mesa-10.6.X (stable, thanks to Mauro and Chih-Wei) https://github.com/maurossi/mesa/tree/10.6.X_lollipop-x86_06-dec-2015) this fixes Google Maps freeze issues
libdrm 2.4.65 (added to easily switch to Intel UFO driver)
libpciexpress (old source from android-ia, to be able to build libdrm... maybe I should upgrade this to the latest source, dunno what's going wrong here)

Extra feaures:
Adaptive back-light option (needs ambient light sensor (ALS) and some luck)
No more SIM-card messages (noril = yes in init.x86.ro)
cm-gapps
Google Maps works

+ All the stock Android-x86 goodness and HW support


Have fun! :)

[Povilas Staniulis]

Any chance of getting a 64 bit version ?

--
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 https://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/d/optout.

[Jon West]

Is there any chance you could post your changes to github so we could at least build a 64 bit version ourselves? Pretty please?

[JJ Meijer]

No problem, I will give it a go tomorrow. I'm curious about the performance results but I'm not sure what apps would benefit from x64.

All the sources are available, please let me know how I can make it easier for you.

[Jon West]

Sorry, a suggestion would have helped... Possibly a link to the other items you cherry-picked ;)

[JJ Meijer]

Haha, it was a real question ;)

Here are some missing links:
Back-light patch: https://groups.google.com/forum/#!searchin/android-x86/backlight/android-x86/Tid3J41lrFE/W-k3cPW9BwAJ
Local manifest: https://drive.google.com/open?id=0B9vJ9JSuyPijZDlaQjIwZmJQZWs

Also pushed the stuff needed to build the kernel for x64 now. New build will be ready soon.

Op dinsdag 15 december 2015 01:57:09 UTC+1 schreef JJ Meijer:

[spin877]

As usual I am a bit unlucky . :-(

does not work.

I my tablet and a baytrail

I/SurfaceFlinger( 1865): SurfaceFlinger is starting

I/SurfaceFlinger( 1865): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...

D/libEGL  ( 1865): loaded /system/lib/egl/libGLES_mesa.so

W/EGL-DRI2( 1865): fail to get drm fd

W/libEGL  ( 1865): eglInitialize(0xb6867400) failed (EGL_NOT_INITIALIZED)

W/gralloc ( 1865): FBIOPUT_VSCREENINFO failed, page flipping not supported

W/gralloc ( 1865): page flipping not supported (yres_virtual=800, requested=1600)

I/gralloc ( 1865): using (fd=11)

I/gralloc ( 1865): id           = inteldrmfb

I/gralloc ( 1865): xres         = 1280 px

I/gralloc ( 1865): yres         = 800 px

I/gralloc ( 1865): xres_virtual = 1280 px

I/gralloc ( 1865): yres_virtual = 800 px

I/gralloc ( 1865): bpp          = 32

I/gralloc ( 1865): r            = 16:8

I/gralloc ( 1865): g            =  8:8

I/gralloc ( 1865): b            =  0:8

I/gralloc ( 1865): width        = 203 mm (160.157639 dpi)

I/gralloc ( 1865): height       = 127 mm (160.000000 dpi)

I/gralloc ( 1865): refresh rate = 60.00 Hz

W/hwcomposer( 1865): getting VSYNC period from fb HAL: 16666667

D/hwcomposer( 1865): Intel hwcomposer module

I/SurfaceFlinger( 1865): Using composer version 1.0

W/SurfaceFlinger( 1865): no suitable EGLConfig found, trying a simpler query

F/SurfaceFlinger( 1865): no suitable EGLConfig found, giving up

--------- beginning of crash

dmesg http://pasted.co/274c44a2

logcat http://pasted.co/8c450dfa

in the past I tried bulding ConsoleOS ( shit :-) ) with driver mesa 11.0.3 and " strangely "

worked on my tablet

https://github.com/iConsole/Console-OS_external_mesa

https://github.com/iConsole/Console-OS_hardware_drm_gralloc

You can make another ISO for me :) ? 

I can do beta testing thanks

[stavros daliakopoulos]

why is this build only 266 megs compaired to the others (349, 348) ?

[Jon West]

Thanks JJ :)

[JJ Meijer]

I might have forgotten gapps in that build, will check it out for you.

[JJ Meijer]

How does stock Android-x86 work for you? It's currently on MESA 11.0.7. I also have a Bay Trail tablet and it works fine over here.

http://sourceforge.net/p/android-x86/external_mesa/ci/3cff49188fd251c4b2be5d0366d0bb7a0e48b680/log/?path=/VERSION

Op dinsdag 15 december 2015 11:20:07 UTC+1 schreef spin877:

[Jon West]

On my SP3, there are only a couple things that I wish would work better like rotation, light sensor and better CPU management, other than that, everything works pretty well. I saw your CM based build as well, how is that running?

[Zeeshan Ahmed P]

The iso that is linked works, boots up and works fine.. But I didn't any difference from the 5.1 iso
And the iso doesn't have gapps
And I really wanted the cm build to work but unfortunately it doesn't boot.. Maybe I'm executing the wrong commands for boot from grub.. But it just loads the video module and then suddenly restarts showing a lot of error messages...
I used the grub.cfg file from the other iso that I had... Is that causing problems..?

--

[spin877]

for rotation  I have changed

in file iio-sensors.cpp

        int ret = SensorBase::readEvents(data, cnt);

        // TODO: read orientation from the properties

        for (int i = 0; i < ret; ++i) {

-               data[i].acceleration.x = -scale * read_sysfs_int("in_accel_x_raw

-               data[i].acceleration.y =  scale * read_sysfs_int("in_accel_y_raw

+//             data[i].acceleration.x = -scale * read_sysfs_int("in_accel_x_raw

+//             data[i].acceleration.y =  scale * read_sysfs_int("in_accel_y_raw

+               data[i].acceleration.y =  scale * read_sysfs_int("in_accel_x_raw

+               data[i].acceleration.x =  scale * read_sysfs_int("in_accel_y_raw

+

invert axes xy e rebulding.

[stavros daliakopoulos]

anyone notice that gmail is now obsolete? Inbox works much better as gapp. 

[JJ Meijer]

Op dinsdag 15 december 2015 11:20:07 UTC+1 schreef spin877:

As usual I am a bit unlucky . :-(

does not work.

I my tablet and a baytrail

I/SurfaceFlinger( 1865): SurfaceFlinger is starting

I/SurfaceFlinger( 1865): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...

D/libEGL  ( 1865): loaded /system/lib/egl/libGLES_mesa.so

I/SurfaceFlinger( 1865): Using composer version 1.0

W/SurfaceFlinger( 1865): no suitable EGLConfig found, trying a simpler query

F/SurfaceFlinger( 1865): no suitable EGLConfig found, giving up

--------- beginning of crash

It looks like ro.hardware is not set. Please add: androidboot.hardware=android_x86 to the kernel cmdline and it should work.

@ Povilas Staniulis
I noticed there is a boot deley with 32-bit kernels, did you wait long enough? The x64 kernel boots straight away so I'll try to get an image together.
 

[spin877]

I'm sorry.
I am stupid.
I had to discover it by yourself .
I've wasted your time.


OK now it works . happy .... :-) ) ) ) )

P.S.
1 ) the rotation of the screen is not in phase. please fix iio-sensors.cpp
2 ) in the kernel there are no wifi driver rtl8723bs please fix  https://github.com/hadess/rtl8723bs

tnx

[JJ Meijer]

New builds are uploaded:
android-5.1.1-x86_kernel-4.1.14_mesa-10.6.9_intel-pci-drm_cgapps_iso
android-5.1.1-x86_64_kernel-4.1.14_mesa-10.6.X_intel-pci-drm_cgapps_img


and
CM12.1-x86_kernel-4.1.14_mesa-10.6.X_intel-pci-drm_cgapps_img

I created a new image because the images on Google Drive are very hw specific. This build includes an extended kernel configuration and hw detection (thanks to the Android-x86 project).

The boot script of this CM build is somewhat different, all hw detection is done before starting Android because there is no hotplug detection. Also different parameters need to be passed:
androidboot.hardware=omni
DEV= the device where the system.img and data are stored
DIR= path to system.img and data
DATA= if empty it will expect a directory called data at the DIR location, also a *.img filename van be passed
optional to go to a shell before Android starts: DEBUG=2

Grub example with all files stored on a partition labelled "android" on the device /dev/sda2 in the directory cm12.1:

menuentry "CM12.1-x86 USB" {
    set DIR=/cm12.1
    search --no-floppy --set=root --label android
    linux $DIR/kernel CMDLINE androidboot.hardware=omni DEV=/dev/sda2 DIR=$DIR
    initrd $DIR/initrd.img
}

[Povilas Staniulis]

Links ?

[spin877]

Il giorno mercoledì 16 dicembre 2015 02:11:35 UTC+1, Povilas Staniulis ha scritto:

Links ?

https://drive.google.com/folderview?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE&usp=drive_web#list 

[Mauro Rossi]

About the latest build android-5.1.1-x86_kernel-4.1.14_mesa-10.6.X_intel-pci-drm_iso

Includes:
Kernel 4.1.14 (Long-term supported kernel, https://github.com/meijjaa/linux/tree/android-longterm) fast and stable
Mesa-10.6.X (stable, thanks to Mauro and Chih-Wei) https://github.com/maurossi/mesa/tree/10.6.X_lollipop-x86_06-dec-2015) this fixes Google Maps freeze issues

Hi JJ, 

latest mesa 11.0.7 should have the same meta DSA optimizations, because my 10.6.X branch was created by merging all meta related optimizations present in 11.0 branch, including correction of hazi font bug for X3100 and X4500MHD

Did you experienced Maps crash with latest mesa 11.0.7  in lollipop-x86 branch?

 

libdrm 2.4.65 (added to easily switch to Intel UFO driver)

libdrm should be updated to 2.4.65 in lollipop-x86, but http://cgit.freedesktop.org/mesa/drm has some recent intel related additional commits

libpciexpress (old source from android-ia, to be able to build libdrm... maybe I should upgrade this to the latest source, dunno what's going wrong here)

Do you mean libpciaccess?

This is updated in lollipop-x86 branch, except for the latest commit to solve a problem when building for Linux OSes

http://cgit.freedesktop.org/xorg/lib/libpciaccess/commit/?id=c1de5dc0541e58372dcddc5120e1e68e03f4f619

but I never encountered this building error with Android-x86

Extra feaures:
Adaptive back-light option (needs ambient light sensor (ALS) and some luck)
No more SIM-card messages (noril = yes in init.x86.ro)
cm-gapps
Google Maps works

+ All the stock Android-x86 goodness and HW support

Interesting I'll have a look at the links you posted.

Thanks a lot!

Mauro

[JJ Meijer]

Hi Mauro,

 Thanks for your reply. I did some testing:

If i try to compile libdrm from freedesktop against libpciaccess from android-x86 I will get:
make: *** No rule to make target `out/target/product/x86/obj/SHARED_LIBRARIES/libpciaccess_intermediates/export_includes', needed by `out/target/product/x86/obj/SHARED_LIBRARIES/libdrm_intel_intermediates/import_includes'.  Stop.

If i try to compile libdrm from freedesktop against libpciaccess from android-IA it builds fine.

If i try to compile Intel UFO against libdrm from android-x86 I get errors.

If i try to revert to MESA 11.0.7 from Android-x86 Google Maps will freeze again. Strange since I understand from you the differences are not that big compared to 10.6.X.

I guess there is some difference with the Android.mk from libpciaccess?

Op woensdag 16 december 2015 03:09:57 UTC+1 schreef Mauro Rossi:

[paul17]

Which one to download?
I'm confused
Sorry for stupid question
I want CM12.1
Dell Inspiron 3521 dual booting windows 10 and android 5.1 RC1

[stavros daliakopoulos]

I tried to do a "frankenstein" update,

I tried to install android-5.1.1-x86_kernel-4.1.14_mesa-10.6.X_intel-pci-drm_cgapps_iso.tar over the 5.1-rc1 official install on my laptop, but it hung on the hardware detection.

Somehow I managed to exit and I thought that the installation was succesfull.

Then I booting into android and after adding my account I saw that the space

on the drive was only 2 GB, so I was actually on the pen drive lol .

Τη Τρίτη, 15 Δεκεμβρίου 2015 - 2:57:09 π.μ. UTC+2, ο χρήστης JJ Meijer έγραψε:

[JJ Meijer]

Regarding libdrm and libpciaccess, it turns out in the Android-x86 it was chosen to be compiled static while libdrm at freedesktop is expecting it to be shared :o).

diff --git a/Android.mk b/Android.mk
index 790a2e4..a7cf673 100644
--- a/Android.mk
+++ b/Android.mk
@@ -17,7 +17,6 @@ $(PCI_IDS_GZ): $(LOCAL_PATH)/$(PCI_IDS) | $(MINIGZIP)
 
 LOCAL_MODULE := libpciaccess
 LOCAL_MODULE_TAGS := optional
-LOCAL_MODULE_CLASS := STATIC_LIBRARIES
 LOCAL_ADDITIONAL_DEPENDENCIES := $(PCI_IDS_GZ)
 
 LOCAL_SRC_FILES := \
@@ -49,4 +48,4 @@ LOCAL_C_INCLUDES := \
 
 LOCAL_SHARED_LIBRARIES := libz
 
-include $(BUILD_STATIC_LIBRARY)
+include $(BUILD_SHARED_LIBRARY)

You should use this build for CM12.1: https://drive.google.com/open?id=0B9vJ9JSuyPijMUdJVGdRTldHNkk it still needs some work but it's already quite usable imo.

Op woensdag 16 december 2015 03:09:57 UTC+1 schreef Mauro Rossi:

[paul17]

Alright
Thanks a lot
To you and the whole team behind Android-x86
Love the good work :)

[paul17]

How do I install it?
Sorry for giving so much trouble
But its not an iso file
i extracted the file and found the system, initrd and kernel images

On Thursday, 17 December 2015 00:18:07 UTC+5:30, JJ Meijer wrote:

[JJ Meijer]

The easiest way is probably to get an official Android-x86 build and replace those files.

Another way would be to create a bootable USB stick:

• Add a fat and a ext4 partition.
• Install Grub on the fat partition and add those files with an empty data directory to the ext4 partition.
• If you add the label android to the ext4 partition and put those files from the previous point in a directory called cm12.1 you can use my Grub entry straight away.

Please Google everything you don't understand about my very short explanation ;)

Op woensdag 16 december 2015 20:41:41 UTC+1 schreef paul17:

[Povilas Staniulis]

Can't get backlight working on my T100.
Kernel patch needed.

[cwm9]

Could you incorporate the Surface patch for Surface/2/3/4/Book covers/touchpads?  https://groups.google.com/forum/#!topic/android-x86/wFd5qvMwFpU

[JJ Meijer]

I will try to add support for your devices but please make my live easier and submit a pull request at my github or send me a patch, I do not have that much time to spare :)


In the meantime, here are some bench results from Antutu:

CM 12.1 kernel 4.1.14 MESA 10.6.X
http://antutu.com/qr/?c=0564987b93c4e9b69e989079e1fc0b22c10c53d7

Android-x86 kernel 4.1.14 MESA 10.6.X
http://antutu.com/qr/?c=0564987b93c4e9b69e989079e1fc0b22c10c53d7

Android-x86 kernel 4.1.14 MESA 11.0.7
http://antutu.com/qr?c=f873b1acf55ee832d8a2076c3c184f5511333ec3

MESA 11 is a bit faster on Android-x86 but for some reason CM12.1 with 10.6.X is a lot faster. All tested from the same USB stick and below kernel and libs :).


Also a new CM12.1 build over here: https://drive.google.com/open?id=0B9vJ9JSuyPijWTRpU2VLUkVhYkE
New:
kernel 4.1.15
libdrm Master branch from freedesktop (Latest Intel patches included)
libpciaccess 0.13.4 from Android-x86
earlysuspend method from Android-x86

[JJ Meijer]

I screwed up the first link, here's a screenshot.

[Jianlong Liu]

Your x86_64 builds have the same issues as mine I think, can't get terminal emulator (possibly Play Store as well) to launch (i965_dri.so or something, can't remember).

[paul17]

I already have 5.1RC1 installed on an ext4 partition? I will replace the initrd and kernel there. But how do I extract the system.img? Because when installed on an ext4 partition, the system partition isn't an img file, it's a folder there. I'll see if I can find ways to extract system.img

Thanks :)

[Chih-Wei Huang]

2015-12-17 12:53 GMT+08:00 paul17 <shri...@gmail.com>:
> I already have 5.1RC1 installed on an ext4 partition? I will replace the initrd and kernel there. But how do I extract the system.img? Because when installed on an ext4 partition, the system partition isn't an img file, it's a folder there. I'll see if I can find ways to extract system.img

You can just delete (or rename) the system folder
and replace it by an new system.img.

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

[paul17]

I did that. But it doesn't boot. It says failed to find cpu0 device node or something like that. Does this mean that cm12.1 won't work on my laptop?

[paul17]

Please help me installing CM12.1
I added your GRUB lines to the existing menu.lst in my ext4 partition
But there wasn't any CM12.1 boot option added in the GRUB boot menu
I tried using the default 'title' method it booted the kernel and initrd but at the end it gave an error

Thanks in advance

[JJ Meijer]

In grub hit e to edit the default android-x86 entry.
It's important you set:
androidboot.hardware=omni
DEV= the correct device, it won't autodetect like Android-x86. (Like /dev/sda2)
DIR= the dir it's installed into. Also make sure there is a folder called data inside.

After that it should be fine. If you still don't manage, I could check if I can make it more drop in compatible.

[paul17]

I tried that with the correct partition (for me its /dev/sda5) and DIR=/cm12.1
Didn't work
I had also added Android boot.hardware=omni

I don't think I made any mistake

Thanks for your support :) you developers are like God to me. Doing the impossible. I can't donate because I am a student and live in India. Would love to donate once I start earning

[JJ Meijer]

Haha, no problem. Actually DIR needs to be the same as SRC for android-x86. Also you should change it to omni not add it. Please also try to describe more what is happening because I'm just guessing here.

[paul17]

Sure! I'll post the whole response here in some time

[paul17]

Hey! It's running nice! i had deleted the root=/dev/ram0 thats why it wasnt booting

It doesn't detect USB storage devices. Any fix for this? My wireless USB Mouse works properly though.

Can xposed be installed?

Thanks a lot :)

[JJ Meijer]

Good to hear! You could try an app like stickmount from the play store for that, I have not tested anything like that myself yet...

Op donderdag 17 december 2015 18:18:47 UTC+1 schreef paul17:

[paul17]

Alright sir. I'll try it out properly this weekend and help you find out all the problems :)

[paul17]

I have another doubt
I have placed the system.img as well as the system.img file extracted into a folder named system in the cm12.1 directory
So it needs the img file or the extracted system folder? (I want to delete the one which doesn't get used, need to free up some space)

[paul17]

USB storage isn't working. Tried USB OTG Helper and Stickmount. Both didnt't work. CM12.1 build is better than the native android-x86-5.1-rc1. Display is better. Gives very nice performance as in windows. Waiting for USB Storage device fix :)

[paul17]

Camera doesn'y work though :P

[paul17]

Also, can play videos in YouTube upto 360p

[paul17]

Discovered all storage drives at /storage/emulated/0/usbStorage
sorry for the trouble
Working awesome
The only issue i face is that i cannot play videos downloaded from YouTube and camera not working
Rest all is Awesome! V4A Works better than native Android-x86-5.1RC1

[JJ Meijer]

Thanks for the feedback!

I don't know yet what's the problem with Youtube HD, it's also hitting Android-x86. Maybe it's a codec problem or some other check in the Youtube app. Could you test this patched version?

http://forum.xda-developers.com/showpost.php?p=63844721&postcount=3013

The camera issue might be a little harder to solve, did it work under Android-x86? Also please provide more details.

Op vrijdag 18 december 2015 12:16:46 UTC+1 schreef paul17:

[paul17]

I will surely try the patched version and inform you immediately
Camera was working well in Android x86
I had tried the marshmallow build, and locally downloaded YouTube videos worked fine.
I've found a video player which can play the non-playable videos: Archos Video. Neither MX Player nor VLC could play the videos. I recommend continuing CM as Android x86. CM12.1 is way better than the native one in almost all aspects.
AnTuTu benchmark on native Android x86 was around 83k
CM12.1 gave 94k

I found out another issue, games do not take any input either from USB mouse nor the touchpad on my lappy. So there's no way of interacting with the games. Games do not take input from the keyboard either. I tried only 2 games until now. Can this be fixed? I'll try out more games and report here.

The best thing I loved about CM12.1 is that I can see all my partitions mounted in the OS and I can access them without any hassles. Only the windows petition shows empty.
Also, the display is more sharp than the native Android x86. Text is more clear.

Extremely happy with CM12.1 :) (just need the games issue fixed)

Can you please make an installable iso file for the next version? I need to format the ext4 partition so that only the useful stuff remains. I tried deleting Android x86 using MiniXP (from Hiren's Boot CD) (though I can write or edit files from MiniXP)

[Jon West]

What was the setup that finally got you rolling?

[paul17]

i have trusted Grub 1.5 installed
I added these lines below the default android-x86 entry in the menu.lst file located inder 'grub' folder on the pre-installed native android-x86 5.1RC1:

title CM12.1-x86
kernel /cm12.1/kernel root=/dev/ram0 androidboot.hardware=omni SRC=/cm12.1 DEV=/dev/sda5 DIR=/cm12.1
initrd /cm12.1/initrd.img DEV=/dev/sda5 DIR=/cm12.1

Copied all the files from the .tar.gz file to a directory 'cm12.1' on the ext4 partition (for me /dev/sda5) where native android-x86 5.1RC1 was installed. I also extracted the system.img to 'cm12.1/system/'

You can try booting without extracting the system.img and please report me if it works without the extracted system

[paul17]

The cracked YouTube doesn't work. It can't play any video. With HD on, it says there was an error. Without HD, I see blackness :P

[Jon West]

Yeah, I still can't get it to work on my SP3. I am using Android-x86 installer 2.2, so it creates an AndroidOS directory on my C:/ drive, and then dumps the .img files in there and creates a data.img file. Even if I drag JJ's android-x86_64 .img files into it, it boots to the _x86_64 cursor and just keeps blinking... So I am lost now.

[paul17]

Do not use the installer. It didn't work for me at all. Try booting from USB Stick.

[paul17]

It's perfectly ok for me if camera doesn't work. I only need the game input issue solved. I tried Offroad Legends 2 today, it worked fine. I tried Minions Paradise and Thomas & Firends: Race On! these two games don't take any input. If you want me to try some other games, i will try.

Overall, this is the best! CM12.1 Build is the best ever. Just love it completely. Thanks a lot to sir JJ Meijer and the whole team behind it.

(I disabled the Media Storage app because it was making my laptop laggy and the harddisk indication light was always on because of it. Maybe because the Media Scanner was scanning the whole 500GB Internal HDD and also the 2TB External HDD)

Once again, thanks a lot! :)

[Dennis Leopold]

Please excuse my ignorance. But, I can't seem to extract these files. I can unzip them, but I cant seem to untar them. I'm using kubuntu and dolphin, I think I'm extracting the iso and img files into a folder, looks like a directory tree, but I'm not getting .iso or .img files. I'm feeling kinda dumb atm :D What would the command look like if I extracted them from a terminal?

[paul17]

I don't have knowledge about Ubuntu... You can try using 7zip or winrar or corresponding application for Ubuntu. I'm on Windows 10.

[JJ Meijer]

Actually the android-x86 builds where only ment to show and suggest some small improvements. Those were taken from my cm build on which I'm working to get it the way I want and mostly just for fun and learn something.

I will check those issues next week, also will add the requested hardware support and try to make it easier to install.

Thanks for the nice words! but realize my work is mostly based on great work from android-x86 team, the cyanogenmod team and the community who should get the respect. Haha, yes I believe Android will index all storage devices so that explains what you where experiencing.

Also some great news, I was able to get Android booted with the Intel UFO driver with and kernel 4.1.14. It's still a bit glitchy so it needs some more work. Something the console-os team wasn't able to do for $70.000... :o)

[JJ Meijer]

@Dennis, I'm not really sure what you're trying to do but iso and tar files you can just extract with the GUI compression tool or terminal: tar xvf "filename". IMG files you can mount with mount -o loop source target and than copy the files. For both cm and android-x86 you don't need to extract the system.IMG, it can use them directly.

[Dmitry Teslenko]

On Tuesday, December 15, 2015 at 3:57:09 AM UTC+3, JJ Meijer wrote:
> Hello everybody,
>
> Here are some builds: https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE
>
> About the latest build android-5.1.1-x86_kernel-4.1.14_mesa-10.6.X_intel-pci-drm_iso
>
> Includes:
> Kernel 4.1.14 (Long-term supported kernel, https://github.com/meijjaa/linux/tree/android-longterm) fast and stable
> Mesa-10.6.X (stable, thanks to Mauro and Chih-Wei) https://github.com/maurossi/mesa/tree/10.6.X_lollipop-x86_06-dec-2015) this fixes Google Maps freeze issues
> libdrm 2.4.65 (added to easily switch to Intel UFO driver)
> libpciexpress (old source from android-ia, to be able to build libdrm... maybe I should upgrade this to the latest source, dunno what's going wrong here)
>
> Extra feaures:
> Adaptive back-light option (needs ambient light sensor (ALS) and some luck)
> No more SIM-card messages (noril = yes in init.x86.ro)
> cm-gapps
> Google Maps works
>
> + All the stock Android-x86 goodness and HW support
>
>
> Have fun! :)

Does it have default kernel config patched for android? If so, it should support all hardware modern linux distros do, should it?

[youling 257]

only  4.4 r3 's 4.0.8 kernel and 5.1 rc1's 4.0.9 kernel，my device ' wifi can work .

can you build  4.0.9 kernel  x86_64 ?

[Dennis Leopold]

I think the one file was a xxx.tar.tar.gz and the other was xxx.tar.gz and the gui tool I used isn't anything I'm used to. I'll give it all another go tomorrow. Are the zipped files Bootable iso and img files? I've been away from this stuff for so long I feel like I've nearly forgotten all that I once knew :D

[paul17]

Alright sir. Credit goes to you and the whole team behind this project. Awesome work.

I don't know what happened yesterday, day before yesterday I copied some files to my partitions while being on the CM12.1 system. It worked fine. Yesterday I again booted up to CM12.1, made some doc files. Everything worked awesome. I had some work on Windows 10,so i booted to Windows 10. The files which I had copied and made on the partitions were gone. :( I booted to CM12.1 to check if they show up there. But no, in fact, none of the partitions were visible there. The partition directories were there (like /storage/emulated/0/usbStorage/sda7/) but all those were empty. Even my external HDD or pen drive wasn't showing up

Just found this bug, thought of informing you..
Everything else was awesome

P.S.: really hate Christopher and Console OS

[skythatun...@gmail.com]

在 2015年12月15日星期二 UTC+8上午8:57:09，JJ Meijer写道：

Hello everybody,

Here are some builds: https://drive.google.com/open?id=0B9vJ9JSuyPijaVNZZHNuaDJDWUE

About the latest build android-5.1.1-x86_kernel-4.1.14_mesa-10.6.X_intel-pci-drm_iso

Includes:
Kernel 4.1.14 (Long-term supported kernel, https://github.com/meijjaa/linux/tree/android-longterm) fast and stable
Mesa-10.6.X (stable, thanks to Mauro and Chih-Wei) https://github.com/maurossi/mesa/tree/10.6.X_lollipop-x86_06-dec-2015) this fixes Google Maps freeze issues
libdrm 2.4.65 (added to easily switch to Intel UFO driver)
libpciexpress (old source from android-ia, to be able to build libdrm... maybe I should upgrade this to the latest source, dunno what's going wrong here)

Extra feaures:
Adaptive back-light option (needs ambient light sensor (ALS) and some luck)
No more SIM-card messages (noril = yes in init.x86.ro)
cm-gapps
Google Maps works

+ All the stock Android-x86 goodness and HW support


Have fun! :)

Oops, somehow I found that the efi folder missing, shouldn't be... It contains 3 files efi/boot/grub.cfg efi/boot/bootx64.efi efi/boot/bootia32.efi

Where to get those files?

I've tried replaced them  with a native one, the lollipop works but cm12.1 doesn't not.

Same problem found in all your builds, sir. Any ideas?

[JJ Meijer]

Did you edit these files on your Windows or another NTFS partition? You should make sure you disable hibernation and fast reboot in Windows because it is unsafe in combination with Android / Linux.

[skythatun...@gmail.com]

在 2015年12月21日星期一 UTC+8下午4:53:53，JJ Meijer写道：

Did you edit these files on your Windows or another NTFS partition? You should make sure you disable hibernation and fast reboot in Windows because it is unsafe in combination with Android / Linux.

I don't think it can boot without the efi folder though...
Actually, as you've suggested, I have used the efi folder and files in it,

but is said "can't mount system, drop to shell"

so...any suggestions

[JJ Meijer]

I will stop doing Android-x86 builds since it's just to time consuming. New CyanogenMod builds I will be sharing over here soon: https://groups.google.com/forum/m/#!topic/android-x86/EQR7dqArcXg

[JJ Meijer]

Hi Paul,

I checked it with my x86 tablet, those games allow only Touch control, I'm sorry but I don't know how to help you with that.

Op zaterdag 19 december 2015 15:38:51 UTC+1 schreef paul17:

[paul17]

Alright :/ I might be buying a touch laptop next year. So i will surely try on that. Thanks