When I do from adb am switch-user 10 (user 10 or any user), my Moto X Play with Android 5.1.1 crashes and I have to restart it. It is not exactly a freeze because I can see notification poping in the background. But the "Switching to ..." stays eternaly on the middle of the screen.
How to fix this ? I need multiple users, so it's very annoying.
Thank you
Related
I had an application program on Android 8.1.0 and my problem is:
After running this app about 15 minutes and go back to home screen and kill the app.
The screenshot of my app keep blink on my devices but can not interactive with this screenshot ( its show about 0.5s - 2s and disappear).
My app has some services running in the background but I had re-check the current running services on my devices nothing belong to my app is running after I kill it.
Please help me solve this case.
Thank you!
I'm using eclipse for Android development. Often I have several emulators (and devices) running in order to test my app.
LogCat magically switches to the log from the device I just launched the app on. This is fine most of the time, but sometimes I want to switch back to a different device without restarting an app.
I can't figure out where to select which device LogCat is showing. Where can I change it?
I'm using Eclipse Juno on OS X, if that makes any difference. Here's what my LogCat window looks like:
Go to Window -> Show View -> Devices.
Now you'll have another devices tab present, and in that you can select which device you want to see in the LogCat, as well as the running apps on that device in debug mode.
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.
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.