I want to use Android-x86 to test and debug my App.I tried other versions of Android-x86 before successfully,but there is an erroe in about android-x86-4.2.So I ask my question here because it may be happen for others:
I installed oracle VM virtualBox on Win7 32-Bit,then I downloaded android-x86-4.2-20121225.iso from Android-x86 - Porting Android to x86.After I installed Android x86-4.2 on VirtualBox from iso and creating fake SD Card for it,I tried to run it,but when I started it I saw these lines in console:
Detecting Android-x86... found at /dev/sda1
ANDROID root#x86:/ #
And no thing else,even I waited more than 20 minutes and nothing happen!I tried that some times but result is the same.How I can solve this problem?
I asked same question in superuser and I found the way to start it. The correct answer is:
From the install/live CD, you just need to change the value of "androidboot.hardware" parameter
in the grub command from "Android_x86" to "x86". You can do this by
pressing "Tab" in the boot menu or by editing "isolinux.cfg" file on
the installation ISO Image.
If you installed Android-x86 on hard drive,you have to select desired boot option and press e to edit grub command.
I don't know about the project Android X86 - Porting Android to X86. I see in the web, this emulator has a complex installation. I think, if you want to try a fast Android emulator and install easily, debug faster, you can try project AndroVM. It is easy to install it to Virtual Box by downloading the image file and import to Virtual Box .
For what I understand of Linux (which it isn't a lot, but enough I'd say) you're logged in into the system and waiting for you to type some command. If I'm right, you should launch the X server but on an Android environment I don't really know how.
UPDATE:
For what I read here, it's just what I said: it boots and after that it prompts the command line. Two solutions that appear on the link are:
Type start.
Select VESA option before the boot process (I can't help you out in this one, because I don't have the .ISO to try right now).
Please, check them.
The best way to run android x86 on pc is to format a partition in ext3 format.Then install android on it.It will allow androidx86 to run easily.
I have HP430 Laptop with win 7. I had the same problem. But I figured out the solution.
While booting the computer with win7 I entered BIOS menu. There was a option to optimize pc for virtualization.I selected it. After that every thing ran smooth.
Later I noticed in virtual box that, in system settings the acceleration type was VT-x AMD, Nested Paging,PAE/NX. This was different before optimization.
Hope this gives some idea.
Related
I used to launch and debug Android Studio apps on emulator without problems. However, recently I am constantly failing to start the emulator. Updating the SDK and system images did not solve the problem. Updating qemu-system-* did not help either.
System info: Linux Fedora 25 (x86_64), Android Studio 2.2.3
It turned out that the problem was due to the same old NVidia driver problems with Linux. To fix the crash, I opened AVD Manager from Android Studio (Tools->Android->AVD Manager), and then opened the virtual device settings. Then in the Emulated Performance section, next to Graphics, I selected Software rather than Automatic or Hardware. This does the trick and no more crashes occur for the emulator, though it seems considerably slower, than it used to be when Emulated Performance presumably used Hardware by default. The following screenshots will hopefully give a better hint on the solution.
Have you tried running AVD Manager from a terminal?
Control the Emulator from the Command Line
Here you will probably have more details of the errors that make the emulator not work fine.
Delete in your Android SDK the directory "libstdc++" in the directory "emulator/lib64". The emulator will use the system libraries now.
I was fiddling around on an issue like this on Fedora 32 for a couple of days.
I had to to make system unload the free nouveau graphics driver and install/load the non free nvidia driver.
Very useful:
https://rpmfusion.org/Howto/NVIDIA
To check which driver is loaded I used:
lshw -c video
It is difficult to grab the correct rpm package from rpmfusion.
If nvidia is not loaded, then you can check:
more /var/log/messages | grep nvidia
It told me which driver series to use.
After successful install of nvidia driver, I can use HW graphics option in AVD manager.
Sometimes killing the qemu process and then relaunching AVD solves the problem.
killall qemu-system-x86_64
I know this is an old thread but the answer that helped me is not in this page:
The problem was that my mother board had the parameter "CPU virtualization" disabled. After I turned it on, the emulator started working.
I had this problem and I discovered that I did not have enough memory to run my avds. To check this, it is best to try run the avds through the terminal:
First: Check the avds you have installed by changing directory (cd) to the tools folder under the Sdk folder in the Android folder:
//to cd to the tools directory from your home:
cd Android
cd Sdk
cd tools
Once in the tools folder, check the avds installed:
$ ./emulator -list-avds
To launch an emulator listed under your installed emulators:
$ ./emulator #complete_name_of_avd
If you have enough memory, you should be able to start your started avd successfully. If not due to memory issues, you will get the information through your terminal. Free up enough memory from your device to ensure you are able to run the avd successfully.
Also, you might want to reconsider testing an app from the virtual emulator as it drags the machine so much. A physical device connected via USB will be much better to use. just ensure that you have enabled debugging on that particular device and you will be able to identify it among the list of options you have for deploying your application.
None of above helped me. For versions 2021.* and 2022.* just disable ipv6. I have no idea what if you really need ipv6 but only this action solved the problem for me.
Check your Linux distro manuals for details how to disable ipv6.
This is driving me absolutely crazy and I can't find any help. I'm fairly novice when it comes to emulators, and even more so when it comes to Android Studio. Here's my problem: I installed Android Studio. Downloaded the SDK updates, including the HAXM one, and set up my own AVD. Upon trying to start up my AVD, or even the starter AVD that was already there, I get an error stating that "emulator: ERROR: x86 emulation currently requires hardware acceleration!"
I've done some googling and tried to finish the install of HAXM using the install file in the Android/SDK folder. I was promptly told that the installation failed and that my CPU didn't allow for Intel Hardware Acceleration, or something like that. I read somewhere that the only way I can use Hardware Acceleration on AMD is if I were on Linux, with which I have no experience with. So I tried giving up. Now I can't figure out how to disable Hardware Acceleration entirely in Android Studio. I haven't even begun learning how to write in android because I can't get an AVD up and running.
Does anyone have any tips for a complete Android noob? I thought this would be something fun to try since I was at once point fairly good with C++ and I have always been a huge fan of android. However, I've avoided doing anything GUI related until now, and I'm not finding it very fun at the moment.
I'm running an AMD system with 8GB of ram. More specifically, I'm using an AMD FX-4130 Quad-Core Processor on a GIGABYTE GA-970A-DS3 Motherboard.
Unfortunately AMD's virtualization technology AMD-V is not compatible with Intel HAXM. Your only choices are to either get familiar with Linux or use a ARM-based AVD, which doesn't require virtualization.
You can find instructions for Linux on Android Developers' document on Using the Emulator.
You can use Genymotion instead of default one. Its faster than the default one. And this emulator is compatible with both Intel and AMD. Genymotion just uses Virtualbox to run Android in VM.
Here's a link to Genymotion .
Genymotion , Genymotion user guide
it may help you.
Take an android phone with its USB cord then follow these steps:
1. plug in phone to computer.
2. on the phone goto: settings>about device scroll to find build number
3. press build number 7x (this enables developer mode)
4. go back to settings press developers options select usb debugging, include bug reports, verify apps via usb, and GPU force rendering.
5. Check for device connection on the computer
6. add in build.gradle under "buildTypes{" write this
debug { debuggable true }
then when you run your project you should be able to see your phone in the avd selection then select it. Your phone will awaken automatically with your application running except it will be a little semi-efficient boot process.
Also do not forget to remove the debug code from your gradle file when you app is finished.
I searched for days to find a way to start programming android applications however I failed every single try.
First I installed Android Studio on my Windows 7 computer, everything went fine.
After installation I tried to start a project and debug it and appeared my first error that you can see in the link below.
http://i.stack.imgur.com/q9BlJ.png
Then I searched here on stackoverflow and I searched on every single website that is related to this error. What did I learn?
I need to install an Intel package on SDK Manager
I also need to install an executable present on appdata android studio directory
I MUST disable or uninstall hyper-v to install the exe file I spoke on the step before
I searched on how to get this hyper-v out of my computer and I found many ways however when I tried this ways and then tried to install the exe file, it shows this message:
http://i.stack.imgur.com/gQjON.png
I don't know if my computer has hyper-v, the only way I can't do is going to my BIOS and disable it because I don't know the keys I need to press to show my computer BIOS (on the startup it doesn't show any label about the BIOS keys).
My computer model is Sony VAIO VGN-NS11Z_S, if someone knows the BIOS keys please tell me.
I can't use the emulator to try out my app so I gave up from Android Studio and I started with Eclipse and the ADT Plugin.
My problem is still the same, I don't if it is because hyper-v but the android emulator don't work.
Everything is fine but I can't test my app so I can't develop them too...
I really appreciate any help, I want to create Android apps so much, please give me an alternative or a way to fix my problems.
Thank you
You can try using Genymotion. It also needs some sort of hardware acceleration but give it a try.
It can't be that hard to find out the keystroke for your BIOS (EDIT: okay, it can be obviously for some devices). Just google for "your mainboard manufacturer + bios". I found this thread, one post even mentions Hyper-V.
Android Studio and Eclipse have nothing to do with the Emulator. The Emulator is part of the Android SDK which is identical for both IDEs. Throw away Eclipse (at least for Android).
As a last resort, run the Emulator with an ARM image instead of the i86 one, I think it runs without HAX and without hardware acceleration. It's damn slow though.
If you want to do serious Android development, there's no way around a real device. There's plenty of cheap options. That's just a little heads up though, I understand though that you still need an emulator for development.
Here's an interesting link on Sony's website about a BIOS update that may help (disclaimer: BIOS updates are not guaranteed to be safe, install at your own risk and make sure it's the exact right one for your computer):
http://www.sony.co.uk/support/en/content/cnt-dwnl/prd-comp/EP0000208387_4486/VGN-NS11Z
But also within that link it mentions to press F2 to get into your BIOS. Does that work for you?
Programming newbie, just getting started with all of this...
I have searched around, but I haven't found anything relevant to my problem
So here it is,
So I'm trying to build a simple hello world application for android, but I wanted to test run the AVD just to check things out.
But I get this problem:
(it just shows "PANIC: Cannot create AVD", no further info)
I have tried creating virtual devices based on 4.2 and 2.3.3, but none of these start up.
I have sdk up and running, no problem.
I also have all the files required (like the system images etc)
Eclipse 64-bit also runs fine (had some errors, but solved them using search)
Any help?
I run windows 7 64bit, 500gb hdd, 4gb ram, i3#2.4ghz
SDK, Java, Eclipse and all other tools are 64bit based.
Please help.
If the emulator takes up too much time to load or getting lags then you should try this. Called as Intel Virtualization Technology with HAXM.
I know this is not the answer of your question but that might be helpful for you. :) It can greatly increase emulator speed.
You can check : Here
If you are on windows, make sure that the amount of RAM the AVD will have access to is 512MB or less. It doesn't matter how much RAM your computer has, this is a bug.
What happens when you run the following from shell/command prompt? This should give you more information when the emulator is launching and should help diagnose the issue.
emulator -verbose -avd <name of emulator>
Okay, I seemed to have solved my problem
What I did was copy the default .android folder (it was auto generated in D:.android) to C:\Users\Administrator
Although this just works for one launch
For every subsequent avd launch, I had to re-copy the folder and replace only the edited files
Thanks everyone for trying to help!
You must establish (from security or from the advanced properties of your PC) the local variable ANDROID_SDK_HOME to your docs folder.
I wanted to try my hand at programming android devices, so I followed the directions from the android website, installed the sdk, the java sdk, and eclipse. My computer is Windows 7 64-Bit, but I have the 32-bit Java SDK and Eclipse installed since hearing that there are issues with the 64-bit versions.
I am running the most recent version of the Android sdk, 4.0 R15.
I believe followed all of the instructions for installation, but when I load up a sample (Lunar Lander in this case), it loads the emulator, but will not install the app to it. ADB does not show the emulator listed when I use "adb devices", the DDMS perspective in eclipse does not detect any device either. In the emulator I have activated the USB debug setting in the developer area.
I have tried restarting the adb server, and have reinstalled a few times.
I even copied what one guy did on a youtube tutorial for a hello world program, and it still would not load to the device.
Does anybody have any idea how to get the emulator and eclipse talking so I can actually run and debug programs?
Try to adb kill-server and then do adb command like adb devices which will start adb again.
It helps in my case.
Best solution I found is this:
Open DDMS(Window->Open Perspective->DDMS)
In DDMS in the left side there is a Devices tab, a little below there is a list of items, choose little triangle called View Menu, under it find Reset adb and launch it.
After that I get my emulator detected.
Create new AVD following Window->AVD Manager->New (Give a name to your device & select the target) -> Create AVD.
Select the AVD that you created and Click Start to launch the devie.
Only on launching, the device is displayed under adb devices.
For starters, I think you can try the 64 bit versions of Java and Eclipse for Windows. I've Windows 7 64-bit edition, 64-bit java and eclipse versions and all work very well, without any glitches. I however have a question. Where exactly have you installed Android? I mean, using the installer that's available in the Android Developer website. If you've installed it in C:\Program Files, then try re-installing it in C:\ directly instead of Program Files directory. I had faced issues when the directory was C:\Program Files and then I changed it to C:\ .
I noticed that if you allocate a lot of memory to the device it can "freeze" when starting, if frozen for a sufficient period it disappears from the adb devices list. Try reduce the memory footprint of the application?