Hot answers tagged

41

The HowToGeek has a set of instructions on how to Run Android on Your Netbook or Desktop here. It uses the Android builds from Android-x86.org but I don't know how active that project still is? However if you just want to try Android out you're probably far better off just using the emulator on your PC.


11

Nothing like that exists yet since the apps are not run natively in the OS, but they use Dalvik Virtual Machine instead (Wikipedia). It's somewhat comparable to Java in the sense that it uses bytecode and creates a separated environment for each app. So unless the Dalvik environment is ported to other platforms, they can't be run on normal hardware. There ...


9

Checkout Bluestacks or GenyMotion


7

http://www.android-x86.org/ This is the only android distribution for Intel/AMD processors that I am aware of. It has little support, but is actively maintained. The latest version is a release candidate for Android 2.3. Obviously hardware support is hit and miss. For what it's worth it runs very well on my EEE PC. You can install the ISO to a USB drive ...


7

I bought an Acer Aspire netbook, and it has Windows 7 and Android 2.1 pre-installed.


6

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


5

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


5

There are many ways to run android on PC Using Official Android Emulator BlueStacks YouWave AppSurfer (run Android app in browser) Android-x86 Project Windroy Genymotion


5

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.


4

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


3

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


3

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. http://www.android-x86.org/releases/releasenote-4-0-rc1 It's a live CD so you can just try without installing it first.


3

I came across another way to install Android on a PC from MakeUseOf via this Android Enthusiasts question, and thought I'd post it as an alternative answer. It's a live CD called, appropriately enough, "Live Android."


3

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


3

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


2

I recommend using the Android emulator if you want to experiment with Android without buying a device. LiveAndroid isn't supported by Google and it hasn't been updated in quite a while. It could be that your video card is not supported. I'd also recommend using VMWare Player instead of VirtualBox if you really want to use LiveAndroid.


2

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. https://play.google.com/store/apps/details?id=com.icecoldapps.serversultimate


2

According to this thread, this is possible and it is as easy as adding the following line to /etc/vold.fstab: dev_mount sdcard /mnt/sdcard auto SDCARD=/dev/sda7 But I haven't tried it myself.


2

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


2

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 Source: https://groups.google.com/forum/#!topic/android-x86/XfIRyHQ5nmk I had too tried all your commands without success. I was stuck behind a proxy trying to setup ...


2

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


2

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


2

Did you check with netcfg within Android that both are really up? If, e.g., eth1 is down, enable it with netcfg eth1 dhcp up.


2

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


2

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.


2

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


2

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


2

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


2

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


1

Most likely this is a problem with the Android-x86 image you've downloaded, or else that the virtual hardware you've set up in Virtualbox doesn't match the configuration the image is expecting. Check which image file you've downloaded, and make sure the configuration matches what's described in the setup instructions.



Only top voted, non community-wiki answers of a minimum length are eligible