Progress on Running Android-x86
boramalper opened this issue · 32 comments
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! =)
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
-
I can see the bootloader, and I choose "Live CD - Debug Mode" to continue
-
I get this glitch after
/kerneland/initrd.imghas been loaded:
Edit: Setting
vgaparameter to 786 seems to remove the glitch (instead shows the bootloader as you've pressed enter). See GRUB VGA Modes for all possible values. -
I get
BUG: unable to handle kernel paging request at ...which results inKernel panic - not syncing: Attempted to kill init! exitcode=0x00000009
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
@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...
Well, it seems it fails with a similar error.
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.
I wonder why Android x86 is so slow
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)?
if you first install android-x86-1.6-r2.iso to a hdd image with qemu it boots MUCH faster within v86
@BenNottelling Maybe it's relatively much faster but I still found it quite unusable, speed-wise. How was your experience?
@boramalper it was pretty unuseable lol
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.
You are missing, that There is no Android build for ARM Computers with Bios (MBR)… But probably it would be possible.
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
I can try running it. 😅
Will post my experience.
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.
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.
I'm pretty sure you can run all versions of Android x86 in virtual box
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?
No, I believe most reach the shell.
Oh. Okay. I can try getting the GUI.
Good luck sir!
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
The next step is finding how to reduce the booting time of the android ? Any ideas how to achieve this are welcomed
How do you get the GUI?
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.
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:
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.
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
Let's close this as working.
@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!