[BUILD][03-Sep-2016][SP2] Android-x86 / Remix OS

[rootsuperuser]

How-To

Here to download a Testbuild for Android 5.0.2 from Google Groups from rgb
https://groups.google.com/forum/#!topic/android-x86/3xClAbl5D_w

Info:
If an microSD card is inserted the boot process will fail, because the microSD replaces the SSD to be the hd0 device.
Solution: change the grub.cfg entry from hd0 to hd1 and also do the mod in the loopback cfg
[EDIT]: sinc latest UEFI Firmware update, booting from microSD isn't working anymore

gapps can be used from any place, just copy the contens of the .zip file to there correct places.
atm I use a small gapps package from paranoidandroid (PA)
http://d-h.st/o72

WiFi:
I compiled a build on my Ubuntu intallation and extract the files for you, hope copy the files works also on the downloadable iso.
Please give me feedback if the files are working for you.
usb8797_uapsta.bin replaced in /lib/firmware/mrvl/
mrvl folder replaced in /lib/modules/3.10.58-android-x86+/kernel/drivers/net/wireless

Touch/Type Cover 2:
hid folder replaced in /lib/modules/3.10.58-android-x86+/kernel/drivers/

THANKS!

 

[pmw188]

Thank you

Thank you
I have question . Is it work on sp3?

Thank you

 

[dinohunter117]

Has anyone tried DuOS? I have been running it on my Surface Pro 1 for about a week now and I have yet to find anything wrong with it. Its a virtual machine inside windows and it runs flawlessly.

 

[sandman01]

Thank you
I have question . Is it work on sp3?

Thank you

I can not test it on a SP3 but users here and on Google groups reported boot issues with the standard android-x86 images.

Sent from my D6503 using XDA Free mobile app

 

[sandman01]

Has anyone tried DuOS? I have been running it on my Surface Pro 1 for about a week now and I have yet to find anything wrong with it. Its a virtual machine inside windows and it runs flawlessly.

Interesting but as far as I know and tested nothing comes close a android build that runs natively.

Sent from my D6503 using XDA Free mobile app

 

[slashdevnull]

Info:
If an microSD card is inserted the boot process will fail, because the microSD replaces the SSD to be the hd0 device.
Solution: change the grub.cfg entry from hd0 to hd1 and also do the mod in the loopback cfg
[EDIT]: sinc latest UEFI Firmware update, booting from microSD isn't working anymore

Hi Sandman,

that's interesting. I've got the surface pro 3 with Docking Station, installed android x86 (EFI Image: "Android-x86 4.4-r2 EFI image") on microSDCard, the kernel starts to boot, but I'm having trouble with the root-partition.

Partitioning of my microSDCard:
sdb1: 120 MB, FAT16 ->EFI stuff
sdb2: 12G, ext2 -> Android x86

I copied the EFI stuff from live Image to sdb1, including kernel and initrd.

There's a grub.cfg inside efi->boot-dir, where I set root to (hd1,gpt1), but that didn't work...(hd1,1) didn't either, since it's not for EFI.
I'm almost there, but I don't know how to Access the root-partition (sdb2) on my microSD.

I already tried creating GPT Partition table on the microSD, but with that I couldn't install Androidx86 at all, the partitions weren't recognized.

Can someone help me with that?

P.S.: Running the LiveSystem from USB works perfectly well with the known issues (no WiFi).

 

[sandman01]

P.S.: Running the LiveSystem from USB works perfectly well with the known issues (no WiFi).

Sounds good but please change your partition type to an EXT4 partition to avoid issues with gapps

The grub entry on the efi image is used for booting from the USB Drive
I had also an grub2 bootmanager from my ubuntu installation (where I build the images)

the grub2 bootmanager is installed on my local ssd and there I include the code to boot from my ssd Partition

e.g.

set root='(hd0,8)'
linux /android-2015-03-04/kernel root=/dev/sda8 androidboot.hardware=android_x86 SRC=/android-2015-03-04
initrd /android-2015-03-04/initrd.img

 

[slashdevnull]

Sounds good but please change your partition type to an EXT4 partition to avoid issues with gapps

The grub entry on the efi image is used for booting from the USB Drive
I had also an grub2 bootmanager from my ubuntu installation (where I build the images)

the grub2 bootmanager is installed on my local ssd and there I include the code to boot from my ssd Partition

e.g.

set root='(hd0,8)'
linux /android-2015-03-04/kernel root=/dev/sda8 androidboot.hardware=android_x86 SRC=/android-2015-03-04
initrd /android-2015-03-04/initrd.img

Hi,
thanks for your reply.
I've got Arch Linux running on my Surface's internal SSD, but I didn't want to shrink my partitions any further, so I wanted microSD-boot.

I don't think that

set root='(hd0,8)'

will work on the surface3, since there's no "normal BIOS mode" available, EFI only.
As I mentioned before,

set root='(hd1,gpt1)'

didn't work.

 

[sandman01]

Hi,
thanks for your reply.
I've got Arch Linux running on my Surface's internal SSD, but I didn't want to shrink my partitions any further, so I wanted microSD-boot.

I don't think that

set root='(hd0,8)'

will work on the surface3, since there's no "normal BIOS mode" available, EFI only.
As I mentioned before,

set root='(hd1,gpt1)'

didn't work.

that code is working on my SP2 (EFI only, disabled secure boot)
btw if you are using grub2 you can also get a little help by the "e" key to get into the editor during the boot process
in the editor set the cursor to the x hdx and press "TAB"
At the bottom you will see available options (e.g. hd0, hd1, hd2)
The same works for the partition after the comma, the grub editor will show you available options

This helps me to find out which hd number and partition number I need to implement to get my android installations booting

 

[slashdevnull]

btw if you are using grub2 you can also get a little help by the "e" key to get into the editor during the boot process
in the editor set the cursor to the x hdx and press "TAB"
At the bottom you will see available options (e.g. hd0, hd1, hd2)
The same works for the partition after the comma, the grub editor will show you available options

doing this it just gives me the EFI directory, but no other partitions available.
I'm wondering if this could be a problem of Androidx86 not being able to install on a microSDCard with GPT partition layout ?

 

[sandman01]

doing this it just gives me the EFI directory, but no other partitions available.
I'm wondering if this could be a problem of Androidx86 not being able to install on a microSDCard with GPT partition layout ?

I will give it a try when I'm back home from work and repartition my 32G microSD and format it with GPT and 2 partitions
lets see if I can get it working.
but I don't think it would run as smooth as directly from ssd

 

[sandman01]

A little bit frustrating.

After the latest Microsoft SP2 firmware uptade I'm not able to boot directly from MicoSD any more.

Msdos Partition table allows me to install android from installer directly but I can't force my grub loaded to boot from it.

Gpt partition table and the android installer didn't find the MicroSD any more and also booting via grub do not work.

Seems that there is more magic to be done to boot from MicroSD.

Sent from my D6503 using XDA Free mobile app

 

[stickshift88]

I can definitely agree duOS is fantastic. Been running it on my SP2 for a few months no problems and it handles gaming very well

Sent from my LGLS990 using XDA Free mobile app

 

[slashdevnull]

A little bit frustrating.

After the latest Microsoft SP2 firmware uptade I'm not able to boot directly from MicoSD any more.

Msdos Partition table allows me to install android from installer directly but I can't force my grub loaded to boot from it.

Gpt partition table and the android installer didn't find the MicroSD any more and also booting via grub do not work.

Seems that there is more magic to be done to boot from MicroSD.

Sent from my D6503 using XDA Free mobile app

Hi,
my experiences last night were similar to yours:
I tried to use the partitioning tool provided by the installer and it says "Unsupported GPT (GUID Partition Table) detected. Use GNU Parted.", but the latter is not available with the install medium. I created a gpt disk with two partitions (using gparted), but the partitions are not recognized by the installer.
Another thing to try would be dd-ing the EFI-Image to microSD and try to boot from that. If that's working, it's definitely a problem of the AndroidX86 installer. I also saw, that it doesn't really offer an option for formating in ext4, ext2+3 only.

So...to conclude our experiments...: The Android X86 Team should add support for installing on gpt partition layout, especially on external media like (micro)SDCards...this is not a Problem we can fix.

 

[sandman01]

Hi,
my experiences last night were similar to yours:
I tried to use the partitioning tool provided by the installer and it says "Unsupported GPT (GUID Partition Table) detected. Use GNU Parted.", but the latter is not available with the install medium. I created a gpt disk with two partitions (using gparted), but the partitions are not recognized by the installer.
Another thing to try would be dd-ing the EFI-Image to microSD and try to boot from that. If that's working, it's definitely a problem of the AndroidX86 installer. I also saw, that it doesn't really offer an option for formating in ext4, ext2+3 only.

So...to conclude our experiments...: The Android X86 Team should add support for installing on gpt partition layout, especially on external media like (micro)SDCards...this is not a Problem we can fix.

This is why we still need the How to from the first posts because formating the partition with EXT4 and the GPT partition table is currently not supported.
btw. there are allready discussions ongoing on google groups to implement EXT4 capability to the intaller

 

[slashdevnull]

This is why we still need the How to from the first posts because formating the partition with EXT4 and the GPT partition table is currently not supported.
btw. there are allready discussions ongoing on google groups to implement EXT4 capability to the intaller

According to the first post one possible "workaround" would be:
Install to USB-Stick with msdos Partition layout, create GPT on microSDCard, config EFI stuff on microSDCard, copy partition from USB-Stick to microSDCard.

...might be worth a try

 

[sandman01]

Status Update

Since yesterday I got Android 5.1 up and booting

- new GApps required
- Kernel 4.0 up and running
- Wifi is broken at the moment (authentification problems)

 

[sandman01]

lollipop 5.1 link in OP for testers

 

[mrfishball]

install apps from play store

has anyone tried installing apps from the playstore. a lot of apps are incompetible . i played around with the build.prop file,no luck. downloaded the clash of clan apk directly from the playstore but package installer wont install the app. anyone?

---------- Post added at 07:25 PM ---------- Previous post was at 07:06 PM ----------

i came across this line in the nexus 9's build prop "wifi.interface=wlan0" which didn't exsist in my surface pro's build.prop (lollipop 5.0.1) so i took the liberty of adding that in myself last night. since then i haven't experienced any wifi connectivity drops nor connectivity issues. i'm not sure if that helps as i'm still experimenting. you can find the build.prop file under /system. right now my biggest concern is installing apps from the play store as many apps are incompatible or missing

 

[MarkusP87]

Hello,

i've got a Surface Pro 2 and tried the 4.4 KitKat, 5.0 Lollipop and the newest 5.1 Lollipop.

Both the 4.4 KitKat and 5.0 Lollipop works surprisingly well, W-Lan and Orientation at 5.0 Lollipop and W-Lan at 4.4 Kitkat.

Unfortunately the 5.1 Lollipop Image with both 3.XX and 4.0 Kernel doesn't even boot, it's just a black screen.

Is this image for Surface Pro 2 also ?

Wifi is broken at the moment (authentification problems)

I've gotten the same Authentification Problems (Getting IP/Connecting...) when playing around with the system folder and it's permissions.
The Solution at least on my Problem was to set the system folder's permission (chmod -R 655 /system) after that the W-Lan successfully connected.

Thanks for working on our beloved Tablets, they deserve Android

greetz,
MarkusP