I am getting the following error when I try running my program in the emulator:
emulator: ERROR: the user data image is used by another emulator. aborting`
View 1 Replies
Finally strace gave me this:
CODE:................
And several other attempts to call "link" that also fail (sshfs does not support hard links).
Is it possible to change the emulator's behavior to create lock files somewhere in /tmp (using some hash of image path as lock file name)? I am OK to try this myself: which repositories from https://android.git.kernel.org/ are necessary to rebuild the emulator alone, and where in the sources is the code responsible for image locks?
I need to run several emulator instances to test my application. When i try to run instances using emulator -data <path> option, the emulator crashes.
I got a MS Visual Studio window informing that emulator throws a "unhandled win32 exception".
The exception message in the debugger (MS Visual Studio 2008) is: "Unhandled exception at 0x77c4706c in emulator.exe: 0xC0000005: Access violation reading location 0x03216848"
The emulator runs normally without "-data" option.
I created a sqlite database to store playlists for a media player I am developing because of extended feature (rather than using the Content Provider). It works perfectly on the 1.6 emulator but FCs on anything higher than 2.0... what has changed that I need to know about as far as opening databases in SDK 2.0+? Here is the logcat.
CODE:.............
Here is the dbhelper class
CODE:................
why can't stackoverflow just use tags like a normal syntax highlighter.
Unable to play youtube videos on SDK 1.5 emulator - but playing well on SDK 1.0 emulator. Can you update the source....
View 7 Replies View RelatedIs there any 1.5 image going around for the emulator? I would like to try my apps with onscreen keyboard. Maybe someone is actually making nightly builds but I can't find any.
PS: Not sure if it's appropriate to ask in this list.
Is there a way to reload an Android application in the emulator without closing the emulator, saving any code changes, and running the emulator again? If I make even a simple change to the layout, it takes about 30 seconds by time I run it in Eclipse and Android "boots", and I can unlock the emulator to run the application. Is there any way to shorten this time when making changes, or is it something I just have to deal with?
View 3 Replies View RelatedI downloaded the most recent version of Android for linux (android-sdk_r05-linux_86.tgz). I was trying to use the the Android Ant task(s) for packaging, building, and deploying my code. I should mention that I'm running AMD64, but have the 32-bit libraries installed. The Android Ant tasks are all broken.
First, the start-emulator task never gets the emulator running. It does get past starting adb, but then just sits there.
Second, the SDK is missing the aapt binary in the tools directory. So, the example notepad sample application will not even package correctly.
I have all the dependencies configured for Android. I can run it from the command line just fine.I assume the Ant code is out of sync with the recent SDK updates. Can anyone shed some light on this problem? At this point, I'm considering writing my own Python scripts to interact with the Android SDK. Ugh.
I'm running Leopard. I create an avd without problem, but when I run it I get a bus error. I've tried to run the emulator both with and without adb running first. Eclipse (w/ ADT) is not yet running. Any ideas?
View 6 Replies View Relatedwhen i am running the project in eclipse. at finally showing this message. ActivityManager: - exec '/system/bin/sh' failed: Bad address (14) - app is installing but not starting first time automatically.
View 7 Replies View RelatedI am running into a problem creating an android emulator from the command line. When I run the android command the messages below output.
Starting Android SDK and AVD Manager
SWT folder 'libx86_64' does not exist
Please set ANDROID_SWT to point to the folder containing swt.jar for platform
I've already:
Execute SDK Setup.exe and brought down the android packages
Modified my environment variables to point to the tools folder
Verified that the SWT.jar was in fact located in libx86_64
I've already successfully set this up on my primary development unit. The system I am installing on now runs 64-bit Windows 7 (same as my other development unit).
I have removed all Input Managers that were added, but it's still happening. Any ideas?
Process: emulator [460]
Path: /usr/local/dev/android/android-sdk-mac_x86-1.5_pre/tools/emulator
Identifier: emulator
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: bash [275].....................
Whenever I start the application it keeps force closing citing the log below. Is this a CPU overload issue or memory management issue? I really don't understand how to resolve this? I am running Eclipse v 3.5.2 and Android SDK 0.98 and AVD is Froyo (2.2).............
View 1 Replies View RelatedWhen we insert images or media files to sdcard, how we can see this in emulator, means in which folder, i inserted some images and checked in "pictures", but i cant see anything there, just blank only --"No Pictures found" displaying. For media i checked in "Media scanner" under 'Dev tools", there also cant see anything.Can anybody guide me in this issue.
View 5 Replies View RelatedThe emulator screen does not show up with new zImage... The steps I followed are: 1) Downloaded the android kernel from "git clone git://github.com/CyanogenMod/cm-kernel.git" 2) extracted config file from config.gz from /proc/config.gz in emulator 3) copied config file to .config in "cm-kernel" directory 4) export CCOMPILER=${HOME}/android/system/prebuilt/linux-x86/ toolchain/arm-eabi-4.4.0/bin/arm-eabi- 5) make ARCH=arm CROSS_COMPILE=$CCOMPILER oldconfig make ARCH=arm CROSS_COMPILE=$CCOMPILER menuconfig make ARCH=arm CROSS_COMPILE=$CCOMPILER
View 5 Replies View RelatedLet me first tell u that i have already searched for how to load an png image into the android emulator I couldnt come up with any clear cut thread that explains the procedure.... that is why, i am creating a new thread here.can some1 please describe it?
View 5 Replies View RelatedAs far as i know, Android emulator doesn't have a camera. To capture a live image we have to use the web camera. I have seen code in this web site to use the web camera in the android emulator to capture an image, but I don't know how to use this code.
View 2 Replies View RelatedIs it possible to run the android image distributed with the SDK using the standard qemu executable (instead of the emulator executable)?
View 2 Replies View RelatedI have developed an application in Rhodes framework and deployed the application in an Android emulator. When I try to access the application i get the following error, SD card error, Application can't access the SD card while it's mounted.Please unmount the device and stop the adb server before launching the application. I have tried to unmount the SD card in the emulator but I am unable to do that.
View 1 Replies View RelatedAfter reinstalling Eclipse and the Android development components I am getting the following error upon running the emulator on a virtual device:
qemu: fatal: exponent 255 too big
CODE:............
I suspect that some configuration file in the project is hosed but cannot figure out which.
I downloaded android and followed the instructions provided in this website ( http://source.android.com/download )! but i am unable to launch the android emulator. please find the following error
laptop:~/bin/out/host/linux-x86/bin# ./emulator emulator: ERROR: You did not specify a virtual device name, and the system directory could not be found.
If you are an Android SDK user, please use '@<name>' or '-avd <name>' to start a given virtual device (see -help-avd for details). Otherwise, follow the instructions in -help-disk-images to start the emulator. Am i looking at the right executable? can any one please help me figure this out.
I read about in the google documents that the 3 folders corresponds to different screen types and that android would select the image from different folders automatically according to the screen type. I read that WVGA will load from drawable-hdpi and HVGA will load from drawable-mdpi. When I tested with 2 emulators both running 2.1, each with HVGA and WVGA. It turns out that they are both reading the image in mdpi. If I deleted the image in mdpi then they read from hdpi. Can someone answer why emulator with WVGA is reading from drawable- mdpi?
View 4 Replies View RelatedI'd like to use a 1x1 size Nine-patch image from Android drawable resources. When I'm trying to display it with <ImageView> in my layout xml file, this one is never showing up on the Android emulator device. Here's the xml code below. Code...
View 1 Replies View RelatedSpent the whole day on this and still cannot find a solution for this. Here's my short code:
super.onCreate(savedInstanceState); setContentView(R.layout.videoview);
SurfaceView v = (SurfaceView) findViewById(R.id.surface_view);
holder = v.getHolder(); player = MediaPlayer.create(this, R.raw.psa);
player.setScreenOnWhilePlaying(true); player.setDisplay(holder);
try { player.start(); } catch(Exception e) { e.printStackTrace();}
The video itself is in raw directory. When the application starts I can hear the video's sound but no image is displayed. I've tried using 1.5, 2.0 and 2.1, same thing. I've tried this with different videos, tried converting them using ffmpegX and "Videora Android Converter", nothing helps.
I just download a cupcake branch of source code and build it. I configured Eclipse for a new SDK, and appear the things is works great, EXCEPT emulator. 1. I configured a new AVD as parameter i pointed my old sdcard.img then loaded and do not see my sdcard 2. then I back and configure another AVD with a parameter to create a new sdcard.img, when the emulator loaded I still not seen sdcard in emulator. 3. then I try to something like: emulator -avd myavd -sdcard mysdcard.img and there is still no sd card.
How can I restore my sd card in emulator.
I am trying to do is read a contact off of my emulator and display it to the screen. I can't seem to resolve this error. Both of my packages (com.msi.ibm.tutorial and .MobileServiceCallContacts) have the permission READ_CONTACTS set in their manifest xml files. So any ideas as to what I've got wrong? Here is the error message from eclipse console if it helps, it's not helping me, but I'm a little rusty at this and completely new to Android development.
MobileServiceCallContacts]Starting activity com.msi.ibm.tutorial.MobileServiceCallContacts on device
MobileServiceCallContacts]ActivityManager: Starting: Intent { cmp=com.msi.ibm.tutorial/.MobileServiceCallContacts }
MobileServiceCallContacts]ActivityManager: java.lang.SecurityException: Permission Denial: starting Intent { flg=0x10000000 cmp=com.msi.ibm.tutorial/.MobileServiceCallContacts } from null (pid=-1, uid=-1) requires android.permission.READ_CONTACTS
I wonder if anybody has ran into the issue where a running emulator would lose network connection all at a sudden for no obvious reason. And I am sure the computer running the JVM is still online.Restarting the emulator seems to fix the issue but it's been a major PITA for me as it interrupts the work flow.I am using 2.1 SDK 7.
View 5 Replies View Related Problem Event Name: APPCRASH
Application Name: emulator.exe
Application Version: 0.0.0.0
Application Timestamp: 4c79ab54
Fault Module Name: ntdll.dll
Fault Module Version: 6.1.7600.16559
Fault Module Timestamp: 4ba9b21e
Exception Code: c0000005...................
i am running in eclipse gallileo for the 2.0 sdk, though i have tried others
I have a simple test code for testing SimpleDateFormat. This code works well on Eclipse and Android 1.5 emulator, but it failed at Android 2.0 emulator. Does anyone know why? Thanks.
public class TemplateActivity extends Activity {
/** Called when the activity is first created. */
@Override
public void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
TextView tv = new TextView(this);..........................
I have seen a lot of posts about this, and it seems like the code below should work. I have created an SD Card image and added it to the emulator (and that works fine).
Intent intent = new Intent(Intent.ACTION_PICK);
intent.setType("image/*");
//intent.setAction(Intent.ACTION_GET_CONTENT);
startActivityForResult(intent, 1);
It does launch and allow selection of images, but when I click on an image, everything exits and the emulator returns to the home screen, not back to my app. My onActivityResult is never called either. What am I missing?