I have no idea what happened. I was using it normally just yesterday, today every time I turn on a VM, it keeps going on with the loading animation (upwards of 10 minutes). The VMs were never slow on my pc (Core i7). In under two minutes, it would completely load with all the applications installed. I don't have any errors because it either ends up crashing completely or the VM loads but is immensely slow` ,such that I would get messages similar to :
Virtual Machine has stopped responding.
EDIT: I tried turning it on again. After 30 minutes the VM loaded with a blank screen. Then when I tried to click on a button in the keypad, it went back to the loading screen.
EDIT: It turned on now but it is slower than anything I have ever experienced before. My AVM was NEVER this slow. I unlocked the phone and this message popped up: "Process system is not responding." I have two options "wait" or "ok". After I clicked Wait, I could interact a bit with it, but then a second message popped up "Unfortunately the launcher has stopped." and I'm back on the main screen.
I found the answer. I accidentally deactivated the high-performance mode on my laptop. I re-activated it and now it seems to be back to normal.
Related
My Android emulator crashes whenever I press keys on the pc keyboard or hit the emulator side buttons. the only part that works is the emulator mobile screen. This doesn't happen to just one device but to all emulators I use. This is really annoying cause whenever I press any key on the keyboard while the emulator screen is active it will instantly crash. But keystrokes won't crush it when text input is active on the emulator screen. The operating system I use is ubuntu but Windows fix is also useful.
I need help from someone who has managed to solve this problem before.
I'm pretty sure I got this error before too. Whenever I pressed a button, the emulator would just say "Saving State..." and just closes. The only solution I found to fix this was to delete the emulator and create a new one. It's not the most effective solution, but I couldn't find any other solutions.
Currently developing an Android app for my company.
Everything was fine, till my last debugging session on my test-device (tablet attached to android via adb).
When I try to run or debug my app, the "Run App" log simply shows:
Error: Activity not started, unknown error code 5
There is no further information, no stack trace, no nothing...
I tried to figure out, what I changed since the last time, but nothing seems to fix this.
Has anybody else had this error code 5 before and can help me?
Long story short: Unknown error 5 means (at least in my case), there is a lock (meaning a pinned app) on the device, so no other app can be started.
After a bunch of things I tried, I finally figured this out.
My app uses startLockTask() to pin it (so you can't accidentally press one of the navigation buttons).
The problem was, that this lock seemed to be active, even though the app wasn't running. I only realized that, after I tried to push the home button on my tablet (it already showed the android home screen, so it didn't occur to me, to try that...).
Once I released the lock (pressing both Back and Overview at the same time), I could start the debugging again, with no problem.
Restarting the device fixed the problem
I have an app that works perfectly fine after tons of testing, but when I exit out of the app (hit home screen) and let it sit for a while and come back to the app, I just have a black screen. I have tried to reproduce this, but have been unable to, because it is only when I let the phone sit for a while...I have tried exiting out on each activity and even opening memory intensive apps on top of my app, then going back to my app, but it always works fine. Unless I wait a while with the screen turned off then come back...black screen. Any ideas? Im not overriding onresume or onstart, should I be?
I've never seen this issue before but here are some tips you could try:
Check your LogCat to see the results of what's happening after letting your phone sit for a while
Are you able to reproduce this on the emulator?
Just curious, what type of phone are you testing this on? What Android version are you using?
I am having a problem in hadling the galaxy tablet emulator whenever I'll run my application and the tablet launcnh then it will not shown any option to open my appliction or goto the menu! It will shows the normal home not having any menu kind of option. I am sending you the screen shot of emulator.Plz help I try a lot to handle this but no clue how to use.....
Android Galaxy Tab Emulator
edit after looking at picture: Wait--first of all. You know you have to drag that slider thing across the screen to get started, right? After that--
I'm not sure about that specific one, but I did notice some general weirdness with the Android emulators. I found a pattern that makes them work--be patient and deliberate.
First restart all your stuff--heck restart your computer to be safe.
Launch eclipse. Start a debug session with the emulator. wait. WAIT... wait... Might be 30 seconds, might be 3 minutes, who knows.
Eventually the emulator should come up and, behold, maybe it works!
If so--here's the trick--never ever shut it down. Leave it up the whole time you are debugging. It will load your app in seconds and run it like a champ. Shut it down and you will have to restart eclipse to get it to work correctly again.
Between the long wait time and that bug I've seen people extremely frustrated (including myself).
If this isn't your problem--sorry, worth a shot.
I am going through the Android tutorials and at some point an app won't load. The last message on the console is "Installing RelativeLayout.apk..." and it just stays there forever, instead of going on to the "Success" message. Visually, what is happening on the emulator is that it starts with the "A N D R O I D" phase, goes on to the chrome "android" phase, goes on to the home page, and then the little animating battery icon stops moving. After that we go back to the chrome "android" and just stay there forever. Quitting the emulator and rerunning the app doesn't help.
Looking at the log, using the adb tool with logcat, at one point the log lists service after service that died. This occurs right after this log message:
D/Zygote ( 32): Process 59 terminated by signal (11)
When I run adb logcat and have the emulator window visible at the same time, I can see that the battery icon stops animating just about when this message appears. No idea what this means.
I can fix the problem by going to Window --> Android SDK and AVD Manager which has a list of the AVD's if you click on "Virtual Devices" on the left. What I discovered to work is to quit the emulator, then in this window to select the AVD I'm trying to use, click "Start..." on the right, then in the Launch Options box that comes up, check Wipe user data, then hit Launch. The emulator will run until the home page shows up, then I can run my tutorial just fine.
What's causing the problem? What am I doing wrong? I blogged about this in my Into Apps blog and I'd like to be able to post the solution to the mystery as well.
What is your app doing? specifically, are you doing any CPU intensive work that could be stalling out the emulator? If you are, it could be you have a service that doesn't shut down properly, or a run away thread.
If not, i would say just uninstall your SDK and everything to do with the emulator and reinstall a fresh copy. Could just be that there is something screwy with your integration.