New android-x86-6.0-20160127

[Christian]

cant make boot stick with this iso?

[Jayaprakash nasam]

The file is corrupted file size less than it mentioned

[Christian]

I think so too, 247.9 MB can´t be completed.

[jonathan]

在 2016年1月28日星期四 UTC+8下午8:39:57，Christian写道：

> I think so too, 247.9 MB can´t be completed.
>
> Am Donnerstag, 28. Januar 2016 12:53:45 UTC+1 schrieb Christian:
> cant make boot stick with this iso?

download address,please?thanks

[Christian]

seems to be removed by admin

Am Donnerstag, 28. Januar 2016 12:53:45 UTC+1 schrieb Christian:

[Chih-Wei Huang]

2016-01-28 20:06 GMT+08:00 Jayaprakash nasam <nasam.ja...@gmail.com>:
> The file is corrupted file size less than it mentioned

Sorry for that.
It seems the SF uploading service is unstable.
It usually told me '100% Done' but the file is not
completely uploaded.

Anyway, I uploaded another android-x86-6.0-20160129.iso
sha1sum: 43c38e1472cf5b4c269ac698da8b0aa510a4b6c3

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

[Christian]

checked your newest upload without success, reboot before it will start.

[Stefan Svensson]

Thanks! 

Is this 32-bit or 64-bit?

[Jayaprakash nasam]

 only black screen after detecting androidx86

.

[youling 257]

32 bit kernel，and 32 bit Android Platform？64 bit kernel，32 bit Android platform，will nice . 32 bit & 32 bit，64 bit kernel & 32 bit，xposed can work well on 6.0.1 

64 bit Android platform，xposed can't work，we needn't x86_64 Android platform ，needn't lib64.

[dls314]

Using this new ISO with VirtualBox, I have mixed success.

1. I can boot the and other debug live options to an android desktop

2. When I install to the VM's disk and reboot, I have errors and can't boot any of the installed options

FWIW, the marshmallow-x86 latest repo builds and works better for me in VirtualBox at the moment; just experiencing a problem with the built in browser there.

[Bruno A. Vieira]

Greetings,

Firstly, sorry for my English is not very good.

I can not run the Android 6.0.1 20160129 in VirtualBox, with 768 MB of RAM and 10 GB of HD, dynamically expandable. I created two partitions with cfdisk, a 2 GB swap and other ext3 with the remaining 8 GB. After installing the system, it loads up to GRUB, but the screen doesn't expand and Android does not start. The boot sequence displayed is bellow:

Trusted GRUB now booting 'Android-x86 6.0-rc1'

Progress: early console in decompress_kernel
input_data: 0x0151c101
input_len: 0x004b411e
output: oxo1oooooo
output_len: 0x009bef7c
run_size: 0x00a76000

Decompressing Linux... Parsing ELF... No relocation needed... done.
Booting the kernel.
[0.842794] Failed to find cpu0 device node
Detecting Android-x86... found at /dev/sda2

A N D R O I D root@x86:/#

When try debug, it shows several processes errors and doesn't starts.

And I emphasize that I have not had this problem with Android 4.4.4 r4.

As I just think misinformation, I would like your help if possible.

[Chih-Wei Huang]

2016-01-30 0:58 GMT+08:00 dls314 <smith....@gmail.com>:
> Using this new ISO with VirtualBox, I have mixed success.
>
> 1. I can boot the and other debug live options to an android desktop
> 2. When I install to the VM's disk and reboot, I have errors and can't boot
> any of the installed options

The iso is built with kernel 4.4.
It's a known issue that uvesa is broken.
Uvesa is the default framework driver
used by VM currently.

To workaround it, choose the second boot item:
VESA mode. (The debug mode also chooses VESA by default)

> FWIW, the marshmallow-x86 latest repo builds and works better for me in
> VirtualBox at the moment; just experiencing a problem with the built in
> browser there.

[Joan R. Serra]

Please, can you upload an UEFI image to test it ?

Many thanks !!!

Congratulations by  the excellent work !!!

[Chih-Wei Huang]

2016-02-01 16:35 GMT+08:00 Joan R. Serra <joa...@gmail.com>:
> Please, can you upload an UEFI image to test it ?

The iso supports EFI.

[Joan R. Serra]

ok, that's right !
I have installed it on hard disk on my asus F550C (I have kit kat 4.4 also)
All correct !

When it boots: Failed to find cpu0 device node

When I am inside Android 6.0 all correct, but I am not able to download anything from play strore: error 963 (after delete data, cache play store, the same for download administrator ... )

I want to test antutu and compare with kit kat 4.4 ...

Thanks !!!

[dls314]

That worked, thank you.

[Scoo Ter]

Am Freitag, 29. Januar 2016 15:59:30 UTC+7 schrieb Chih-Wei Huang:

Anyway, I uploaded another android-x86-6.0-20160129.iso

android-x86-6.0_20160129.iso
Intel Baytrail tablet, broken Wifi, but did work with "non" 4.4 Kernel, it also works with JJ.Meijers CM 13.0
Dual Band Wireless AC 3160, REV=0x164

dmesg | grep wifi
[    8.461917] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[    8.469743] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-3160-17.ucode failed with error -2
[    8.469789] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-3160-16.ucode failed with error -2
[    8.469824] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-3160-15.ucode failed with error -2
[    8.469860] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-3160-14.ucode failed with error -2
[    8.469895] iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-3160-13.ucode failed with error -2
[    8.469900] iwlwifi 0000:01:00.0: request for firmware file 'iwlwifi-3160-13.ucode' failed.
[    8.469904] iwlwifi 0000:01:00.0: no suitable firmware found!

[Joan R. Serra]

I have achieved install firefox (moving apk downloaded from apkmirror on /data/backup from ubuntu) then Antutu Benchmark.

With kit kat 4.4 Antutu 101.773 now 123.096 !!!

Noe I try to workaround play store problem , I have installed last version but I am not able to dowload anything ...

Any idea ?

Thanks !!!

[Povilas Staniulis]

Error -2 is ENOENT, aka File not found. The required firmware files are missing from that build.
You'll have to edit system.sfs to add the needed files.

--
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.

[Scoo Ter]

Ok,
I've "borrowed" the files from CM13.0 and copied them into system.img.
Wifi works now.
But one more question: from where do I get these drivers/firmwares binaries normally (if I can't borrow them from another image)?
Or do I have to compile them myself?

[Chih-Wei Huang]

2016-02-03 14:57 GMT+08:00 Scoo Ter <reto...@gmail.com>:
> Ok,
> I've "borrowed" the files from CM13.0 and copied them into system.img.
> Wifi works now.
> But one more question: from where do I get these drivers/firmwares binaries
> normally (if I can't borrow them from another image)?
> Or do I have to compile them myself?

http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/tree/

As explained in another thread,
I need to update the latest firmwares
to match with kernel 4.4.

[Joan R. Serra]

Perhaps this is related to the 963 error on play store ? It seems play store cannot download anything ... some problem with permissions or download manager ?

I tested it with flashing  the Android 6 x86 opengapps. (but without success to avoid 963 error)

El miércoles, 3 de febrero de 2016, 8:09:06 (UTC+1), Chih-Wei Huang escribió

[Joan R. Serra]

can you confirm if play store download and update apps ?

Thanks !

[Scoo Ter]

That has nothing to do with missing firmware.
I can confirm, Play Store works without any problem.

[Joan R. Serra]

Great news !

Can you share system.img ? Or explain how to merge cm13 with system from android x86?

Many thanks !

[Scoo Ter]

I'm not really sure whats your problem is.
I've just copied four or five firmware files from CM 13 to this image.
In my case, Wifi  generally didn't work because of the missing firmware files.
Anyway, here is the way I've added files from CM 13 to this image.
On a Linux (Ubuntu in my case) mount CM13 "system.img"

mkdir system
sudo mount -o loop system.img system

Copy the necessary files from CM13.
Unmount system.img from CM13:

sudo umount system

Than unpack "system.sfs" from this image into "system.img", I did it under Windows:

7z.exe x system.sfs "system.img"

On a Linux (Ubuntu in my case) mount the unpacked "system.img" like mentioned above
Paste (as root) the necessary files into your mounted system, chmod them correctly (0644 in my case)
Unmount "system.img"

sudo umount system

test it...

[Joan R. Serra]

It's very strange ... you said play store works well. In your system.img just you have added files related to hardware wifi only  ...

I made two clean installations on my hard disk, on an ext3 partition. Before with 4.4 kit kat I have not problems and now with android 6 does not work play store: while trying to download any app first starts to download but then finish with 963 error !?

You have an Intel Baytrail laptop and I have an Asus i7 laptop, I don't undrestand why you have not problems with play store ...

Thanks !!!

[LSS]

So far this version works with nVidia video cards just like android_x86_64-6.0.1_r10-K4.4-

20160110.iso from www.android-x86.net.

However, ethernet (RTL8111E, r8169) is still not working out of box, at least in this version the link is up (was down in the above ISO).

I tried to manually set IP address and gateway using
"ifconfig eth0 <ip address> netmask <netmask>"
"ip route add default via <gateway> dev eth0"

This gives me working ping to my router's gateway and other Internet IPv4 addresses (IPv6 not working, presumably DHCP is broken both IPv4 and IPv6).
However, at this point DNS is not working, and there were no resolv.conf to modify either.
I ended up having to install it on an ext4 partition since I cannot create the resolv.conf file while running live. However, even after manually making resolv.conf with the nameservers entries needed (nameserver <dns server address>), I still couldn't make nslookup working (it keeps saying Server: 0.0.0.0, Address 1: 0.0.0.0, and no addresses associated with hostname).
Guess either android-x86 doesn't use resolv.conf or I may need to restart something... (wasn't that changes to resolv.conf takes effect immediately?)

Plus... it seems ping only works under root despite ifconfig and route showed the settings properly even without root (Network is unreachable), not to mention accessing my router's admin page using browser (ERR_ADDRESS_UNREACHABLE). Probably because I ran ifconfig and ip route commands as root shell...

Guess for some reason DHCP and DNS isn't working as intended both IPv4 and IPv6 on ethernet, as the active ethernet interface (eth0) was initially missing from ifconfig before I inserted the IP and netmask myself, and kernel route tables seemed empty, either, as the IP and gateway routes that I entered manually were the only entries. (Wifi seems to work on some users here, though)

Still, it seems installing to an ext4 partition fixed some permission issues that happened with the 20160110 ISO when testing live... I'm now looking for ways to move /data to a different partition that I created for the purpose.

EDIT: Need to know if anyone else has working ethernet, as the ethernet of that machine of mine always worked with Linux without issues...

[LSS]

EDIT: Just tried Android-x86 4.4-r5 Kitkat there and ethernet worked (both IPv4 and IPv6). However, I had to use VESA mode as nVidia card (Quadro K2200, GM107) do not work (AFAIK none of the 4.4 or 5.x builds work with that card, only since 20160110 with the new 4.4 kernel).

EDIT 2: Tried 5.1-rc1 as well. Video card not working, and using VESA was able to boot to the GUI. Ethernet worked, but somehow only IPv4 was working.
The latest RemixOS managed to get my video card booted to GUI though the shell's cursor was still blinking, but ethernet wasn't working there either, just like Marshmallow.

Sorry for pulling posts again... the lack of edit capabilities make it harder to keep things up-to-date or fix typos without making a new post...

[LSS]

An update... I got ethernet working on Marshmallow (6.0-20160129)... turned out I only have to reload r8169 (first rmmod r8169 then modprobe r8169). So it seems something wasn't right during Android-x86's boot process with this kernel, but dmesg messages during the initial boot (the first few seconds, dmesg through Terminal Emulator right after it completed booting) showed nothing unusual.

The system's mostly stable, just at rare cases it would lock-up (sometimes it would be able to recover itself and self-restart). When I tried adding to add my Google account the first time, the system froze and soft-restarted itself, after which DNS stopped functioning again (though IP address retained), and reloading r8169 made it back working again. This time I'm able to add my Google account successfully and access Play Store properly. So far no more major issues.

Regarding nVidia cards, so far this is the only official image to work with Maxwell video cards out-of-box. The latest Kitkat (4.4-r5) just released still needs (perhaps externally provided) nv117_fuc409c for those video cards, according to dmesg error messages (it kept saying it failed to load fuc409c and tried loading external firmware, and both fuc409c and nv117_fuc409c failed with error -2).

[Ego]

This version boots on my table, but only in debug/VESA mode. I have a Jumper EZPad Mini 2 (Intel Z3735F). It boots fine, but lots of hardware didn't work, mainly Touchscreen (MSSL1680/SileadTouch). I plugged in a keyboard and mouse and was able to navigate a little. Can we install or request additional drivers?

On Friday, January 29, 2016 at 12:59:30 AM UTC-8, Chih-Wei Huang wrote:

2016-01-28 20:06 GMT+08:00 Jayaprakash nasam <nasam.ja...@gmail.com>:
> The file is corrupted file size less than it mentioned

Sorry for that.
It seems the SF uploading service is unstable.
It usually told me '100% Done' but the file is not
completely uploaded.

Anyway, I uploaded another android-x86-6.0-20160129.iso

sha1sum: 43c38e1472cf5b4c269ac698da8b0aa510a4b6c3