Found the solution!
You have to edit menu.lst file. Here is how:
boot in debug mode (usually the second option in boot menu)
when booting stops (for me it just hangs there with flashing cursor and without any prompt) enter mount -o remount,rw /mnt
enter cd /mnt/grub
enter vi menu.lst
right under the first boot entry find the line starting ...
If you have adb set up, it's a one-liner at the shell prompt:
$ adb shell "getprop ro.product.cpu.abi"
In this example, the device asked answered that it has a 64bit ARM V8a CPU (second line).
Note: You can also run the quoted command in a terminal emulator running on the device / emulator. In there, it's just getprop ro.product.cpu.abi.
It all depends on the device where you're going to install this Android port.
If you access the download page of the Android-x86 Project, you'll find a short description for every available ISO to point you out onto the proper download.
Assuming that you're out to try the latest, Android-x86 4.0-RC1 live and installation iso:
for AMD Brazos platform
I'd like to extend and improve @Jay Smith answer based on personal experience.
He is right in the core thing that the cause of the issue is VGA resolution used by Android, but he is wrong in his assumption it is disposable fix and should be typed at each boot.
It can be made persistent, and should be! And I show you how:)
First of all, install the Android ...
This is a community wiki, you can extend it.
According to Phoenix Studio forum (translation) and other sources:
both are based on Android 5.1 Lollipop,
both support Legacy BIOS and UEFI boot methods, but sometimes Phoenix OS Legacy mode does not boot, unlike UEFI,
Remix OS lacks adjustable windows and some of them can only be maximized or minimized,
This solution worked for me.
Just enter the following command in a terminal (change PROXYIP:PROXYPORT )
iptables -t nat -A OUTPUT -o eth0 -p tcp --dport 80 -j DNAT --to PROXYIP:PROXYPORT
I had too tried all your commands without success. I was stuck behind a proxy trying to setup ...
It looks like there are no Android 4.4 images ready yet for this. In the download area of the Android X86 project you can find a couple of images and more, starting with Android 1.6 (Donut) and currently reaching up to Android 4.3 (Jelly Bean), and also other useful resources. Might be worth checking there again later, as I would expect they add 4.4 as soon ...
The one thing that sticks out from your question is that /sda3 is NTFS-formatted
on /sda3 (NTFS partition created in Windows 7)
and thus the Android's Linux kernel panic's due to not understanding NTFS.
Add to the above answer; from what I found while testing both OSes:-
Phoenix OS is now x86 only platform, while Remix is x86/Arm
Phoenix OS supports window transparency.
File manager in Phoenix OS makes more sense in use.
Settings panel of Phoenix OS is more well-organised.
Phoenix OS still lacks of Ethernet support. (major drawback).
Phoenix OS doesn't ...
I suggest you try the latest 4.0 release candidate.
See the release notes and try the closest matching. I was lucky and my unsupported Netbook ran it. YMMV though. It's a question of CPU, GPU, chipset and screen resolution.
It's a live CD so you can just try without installing it first.
The answer for questions 1 and 2 is that some apps on Android are compiled purely in Java/Dalvik bytecode, and others are compiled as native C/C++. Since Dalvik bytecode is not native, it has separate interpreters for different architectures. However, since C/C++ native apps and libraries are compiled for a specific architecture, they can be run only on the ...
Some progress here, but not the real thing. The following allowed me to boot Android x86 6.0 under VirtualBox correctly - but only once:
1) When booting the installation image, the initial screen gives you four options. Move the cursor to the last one: Installation - Install Android-x86 to harddisk".
2) Press the [Tab] key for edit options.
3) Immediately ...
I also had problems with Android x86 vitual box on a Windows 7 Pro x64 AMD machine. I suppose we are all going to have slightly different issues depending on our architecture/hardware but they all seem to be similiar root causes. I think more emphasis should be on the architecture/hardware then the host OS. Try 32bit without/with EFI set in System, leave ...
At first I had the same issue. But I changed the Display settings and now it works.
Go to the VM settings's
Go to Display settings
Check the Accelerate 3D graphics
Set the graphics memory to 1GB (if possible)
Start your VM!
I'm not sure why all the answers are giving you the run around, it's very easy to download the source and get the iso generated.
Here it is : https://drive.google.com/file/d/0B4VR-WNTOX0qVnkyWExEZHdLTms/view
I'm using the very same setup with NAT mode. To connect via ADB:
in VirtualBox Manager, right-click on your VM and select "show log"
press Ctrl-F to initialize a search, type "DHCP". You will find several lines stating something like NAT: DHCP offered IP address 10.0.2.15 – that's your IP, write it down ;)
select the "gear icon" in the same context menu to "...
Your device isn't listed in the list of supported notebooks, so it's not surprising that it doesn't work. You'll have to wait until it's supported.
Remember that the Android-x86 project is made by volunteers, so support for particular hardware depends on someone with the necessary skills having that hardware and an interest in making it work. You might be ...
Thanks to eldarerathis comment.
Indeed, I was able to set needed resolution by modifying kernel boot parameters. Instead of video=-16 in kernel boot options I use video=uvesa UVESA_MODE=1024x768 and all is working in native monitor resolution!
More detailed description is here (in Russian language).
I was able to install Android-x86 on my Debian 9 box with no real problem. Following are my system details, the articles I followed, commands I used and lastly the settings info of the VM itself.
Desktop Environment: Gnome 3.22.2
Operating System: Debian GNU/Linux 9.1 (stretch)
Kernel: Linux 4.9.0-3-amd64
As it was mentioned in the comments above, there is reference for Android X86 – mouse support in Oracle VirtualBox linked in this answer. AFAIK I had not to install additional packages like vbox-guest-utillities. As you can see the following list is empty:
$ dpkg -l | grep virtualbox-guest
$ dpkg -l | grep vbox-guest
I only had to change the "Pointing ...
You can have a look at Servers Ultimate on Play. The SSH server itself works on all devices and command line works on ARM and x86.
That's not a Play Store compatibility error that you're getting on your device, that's an install error which says that it's having problems installing the app on your device. The Play Store only checks some basic specs of your device (like OS versions, screen size, RAM size, whether or not there's a camera, etc) it can't tell remotely whether or not there's ...
If you go to www.androidx86.org and click on releases, it will direct you to a list of releases that can be downloaded. http://sourceforge.net/projects/android-x86/files/Release%204.4/ is where the Android x86 4.4 RC2 ISO is one such link that androidx86.org will direct you to.
so as to run it in VM
Why not use the SDK emulator? It has Android 5.0 images for Intel x86 and even x64 architectures.
Dowload the SDK from here and extract it to a folder you like. Now launch SDK Manager and add the Lollipop images.
You will also need Intel® Hardware Accelerated Execution Manager driver if you will be using the x86 emulator. Get it ...
Since your virtual machine doesn't have a battery, it uses a fake battery sensor to provide the required battery information to the OS. While it's possible to make it read any amount of charge, and to change over time, it's convenient to use a fixed amount somewhere in the middle of the range, since values close to 100% or 0% can cause the Android OS and ...
The Google Play Store automatically filters your application to devices with compatible CPU architecture. E.g. if you have a library which is only compiled for ARMv5, your app will only show up for devices with ARMv5 and ARMv7 processors. Your device should show you only apps that are compatible to your device.
Source: Android Developers - Filters on Google ...
Houdini is a library provided by Intel to convert ARM NEON intrinsics to the corresponding SSE instructions at run-time. It appears that cocos (or your game) is still using NEON even though you're compiling for x86 now.
It may be as simple as doing a full rebuild to make sure all object files are recompiled respecting your change to the ABI:
ndk-build -B &...