Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Progress on Running Android-x86 #224

Closed
boramalper opened this issue Aug 27, 2018 · 32 comments
Closed

Progress on Running Android-x86 #224

boramalper opened this issue Aug 27, 2018 · 32 comments
Labels
guest-os-support

Comments

@boramalper
Copy link

boramalper commented Aug 27, 2018 •
edited

It is clearly indicated in the readme -"No Android version seems to work, you still get a shell."- that Android doesn't run on v86, yet.

I wanted to submit a new issue for tracking the progress of running Android-x86 on v86, to share with each other

  • why it doesn't run
  • what can be done
  • what is being worked on and by whom

This is especially interesting/exciting since if we manage that, we can run Android as a progressive webapp (PWA) on Mobile Safari on iPhone and iPad; not that it will be necessarily useful but surely fun! =)
@boramalper
Copy link
Author

boramalper commented Aug 27, 2018 •
edited

android-x86-4.4-r5

  • Memory size: 512 MB
  • Video Memory size: 64 MB

Checkbox Flags:

  • cpu
  • bios
  • fpu
  • mem
  • rtc
  • hpet
  • io
  • acpi
  • apic
  • vga
  • mous
  • sb16
  • pci

ACPI: disabled

Browser: Firefox Quantum 61.0.1 (64-bit) on Ubuntu 16.04
v86 commit: 89f3a1c

  1. I can see the bootloader, and I choose "Live CD - Debug Mode" to continue

    a1

  2. I get this glitch after /kernel and /initrd.img has been loaded:

    a2

    Edit: Setting vga parameter to 786 seems to remove the glitch (instead shows the bootloader as you've pressed enter). See GRUB VGA Modes for all possible values.

  3. I get BUG: unable to handle kernel paging request at ... which results in Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009

    a345

@BelleNottelling
Copy link
Contributor

Look at this: https://sites.google.com/site/twisteroidambassador/android-x86/kitkat-non-sse3-build
It seems android x86 needs SSE3 (and other SSE instructions) which v86 doesn't emulate

@boramalper
Copy link
Author

boramalper commented Aug 27, 2018 •
edited

@BenNottelling I'm downloading the image now, and will let you know the results soon. Thanks!

P.S. My download speed is horrible, not sure if I can finish downloading tonight...

@BelleNottelling
Copy link
Contributor

Well, it seems it fails with a similar error.
nope

@copy
Copy link
Owner

copy commented Aug 28, 2018

I did get Android working once (I believe android-x86-1.6-r2.iso), but it was so slow (taking one hour to boot) that I didn't bother pursuing this further.

Still would be worth fixing that panic. Contributions are very welcome.

@BelleNottelling
Copy link
Contributor

I wonder why Android x86 is so slow

@boramalper
Copy link
Author

boramalper commented Aug 28, 2018 •
edited

I did get Android working once (I believe android-x86-1.6-r2.iso), but it was so slow (taking one hour to boot) that I didn't bother pursuing this further.

@copy Can you guess what might be the reason (or rather do you think it’s fixable)?

@BelleNottelling
Copy link
Contributor

if you first install android-x86-1.6-r2.iso to a hdd image with qemu it boots MUCH faster within v86

@boramalper
Copy link
Author

@BenNottelling Maybe it's relatively much faster but I still found it quite unusable, speed-wise. How was your experience?

@BelleNottelling
Copy link
Contributor

@boramalper it was pretty unuseable lol

@omerjerk
Copy link

omerjerk commented Sep 8, 2018 •
edited

I have a doubt. Why not try to emulate normal Android on a arm emulator (probably this - https://github.com/ozaki-r/arm-js) instead of trying to emulate Android-x86 on an x86 emulator?

Just want to know what I am missing here.

@niansa
Copy link

niansa commented Sep 10, 2018

You are missing, that There is no Android build for ARM Computers with Bios (MBR)… But probably it would be possible.

@BelleNottelling
Copy link
Contributor

BelleNottelling commented Oct 22, 2018 •
edited

Hey here's a mini update for you! I found a build of android froyo (2.2) for VM's on the android X86 source forge page, and I believe it will work in vesa mode , but I haven't waited to see if it would yet. you want the froyo-vm-20100812.iso file

https://sourceforge.net/projects/android-x86/files/Testing/

@omerjerk
Copy link

I can try running it. 😅
Will post my experience.

@omerjerk
Copy link

Hi,

I got time to test the image today. It's definitely some progress. I can see the Android shell getting opened and working all fine.
screenshot from 2018-10-28 21-04-36

Before reaching this screen, I did see some errors like "Not a virtual machine?" and some function not found on the current system.

I tried running the same image in VirtualBox. In VirtualBox, the above shell appears and after this the actual GUI of Android appears all fine.

@BelleNottelling
Copy link
Contributor

I'm pretty sure you can run all versions of Android x86 in virtual box

@omerjerk
Copy link

I mentioned VirtualBox to make the argument that the image is correct at least.
And I assume that this is probably the only image which at least opens the Android shell, no?

@BelleNottelling
Copy link
Contributor

No, I believe most reach the shell.

@omerjerk
Copy link

Oh. Okay. I can try getting the GUI.

@BelleNottelling
Copy link
Contributor

Good luck sir!

@m25160618
Copy link

Sorry iam late to this issue #224 I have followed Copy directions to setup local debug.html and have downloaded the Android froyo iso attached are the proof of pudding

Step1
Step2
Step3
Step4
Step5
Step6
step7

The next step is finding how to reduce the booting time of the android ? Any ideas how to achieve this are welcomed

@pitust
Copy link

pitust commented Mar 30, 2020

How do you get the GUI?

@SomeDevHere SomeDevHere mentioned this issue Dec 2, 2020
Closed
@copy
Copy link
Owner

copy commented Jan 2, 2021 •
edited

I added android-x86-1.6-r2.iso to the website: http://copy.sh/v86/?profile=android. Takes about 6 minutes to boot, a significant part of that is downloading cdrom sectors. It's scripted to auto-select VESA mode. If you see the A N D R O I D # prompt it's still loading.

Screenshot_2021-01-01_22-10-28

@m25160618
Copy link

m25160618 commented Jan 5, 2021 via email

@m25160618
Copy link

m25160618 commented Jan 5, 2021 via email

@m25160618
Copy link

m25160618 commented Jan 5, 2021 via email

@ethanaobrien ethanaobrien mentioned this issue Jan 29, 2021
Closed
@proxy-m
Copy link
Contributor

proxy-m commented Apr 19, 2021

Looks like you can rebuild Android-x86 without SSE3 instructions for 4.3 (or 4.4) similar to this:

1. The patch will disable the dalvik JIT.

2. Change the busybox initrd and installer to older version (install_2.2 & initrd_2.2).

3. Recompile 
   # make -j4 iso_img TARGET_PRODUCT=android_x86 TARGET_CPU_SMP=false ARCH_X86_HAVE_SSE2=true
ARCH_X86_HAVE_SSE3=false
ARCH_X86_HAVE_SSSE3=false  TARGET_KERNEL_CONFIG=/path_of_your_kernel_config_file/kernel_config.config

Source:

  1. https://groups.google.com/g/android-x86/c/c-IeOvIK-ek?pli=1
  2. https://sites.google.com/site/twisteroidambassador/android-x86/kitkat-non-sse3-build

@foxsouns
Copy link

Hey, any luck with this? I don't have a phone, and I wanted to run a fork/port of this to 3DS, which ends up needing an Android with at least 4.4. I don't have anything to compile with (well, unless you count the community computers, with a liveusb or somethin'), so I'm hoping some progress is goin on.

@SuperMaxusa SuperMaxusa mentioned this issue Oct 29, 2021
Closed
@BelleNottelling
Copy link
Contributor

Hey, any luck with this? I don't have a phone, and I wanted to run a fork/port of this to 3DS, which ends up needing an Android with at least 4.4. I don't have anything to compile with (well, unless you count the community computers, with a liveusb or somethin'), so I'm hoping some progress is goin on.

Sorry to say, but you should probably look for another option

@copy
Copy link
Owner

copy commented Sep 13, 2022

Let's close this as working.

@copy copy closed this as completed Sep 13, 2022
@m25160618
Copy link

m25160618 commented Sep 21, 2022 via email

@foxsouns
Copy link

@m25160618: if you just want python3, try https://replit.com/; if you really need an Android phone to "pintest" then buy a 20 dollar one at your local megastore of choice (wal-mart namely, if you happen to live in the states); and quit necroposting!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
guest-os-support
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
9 participants
@copy @omerjerk @boramalper @proxy-m @BelleNottelling @niansa @m25160618 @pitust @foxsouns