Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 2 years ago.
Improve this question
I am developing a Wear OS app. Now for my graduation presentation I would like to record the screen of the emulator to demo the app. But the problem is that my emulator is stuck at this screen.
Sometimes the changes and the volume buttons work, but the rest is completely stuck. At that point is doesn't seem to receive 'touch' input.I also have a square emulator that works fine, but I am personally not a big fan of the square look.
I tried the following:
Restart emulator (also cold boot)
Wipe emulator
Completely delete emulator folder and reinstall
Restart computer
I updated the emulator to the latest version. It works now.
Related
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 2 years ago.
Improve this question
I'm making a Xamarin.Forms application with Visual Studio Enterprise 2017 and when I want to debug my app, the application launch but the screen stay white, as loading.
The thing is, I don't have the issue on emulator but my coworker do, and if I launch the app manually after (without the debugger then), it behaves normally.
I already tried cleaning and rebuilding the project, closing and restarting Visual Studio, my device and my laptop, but the problem persist.
I checked with the debugger, and my application does makes the same path on the emulator (and the screen shows) than on the device (where it doesn't)
Do you have any idea ? Thank you !
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 7 years ago.
Improve this question
hello I started android and I am working with android studio.
my laptop is a surface pro 4 and when I try to run my emulator it takes forever, I tried to wait for over 10 hours but it didn't work. The emulator runs perfectly and the picture of the phone shows up but it doesn't go to the main page. I have also installed the "HAXM" but I think the problem is that my computer is weak so I wanted to see if you guys have any ideas for me on how to fix this problem.
Make sure you have all emulator updates installed. Try enabling hardware acceleration, and devote more RAM to the emulator. Try using the Intel x86 Atom image. Your computer should be able to run it.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
I've installed CyanogenMod on my Samsung Galaxy S3 about a month ago using the CyanogenMod Installer, it is using Android 4.4.2 now...
My question is: when the CM with 4.4.4 is made available on http://download.cyanogenmod.org what should I do to get this update? in other words:
Should I expect to receive a system notification like a 'system update via OTA'?
Or
Will I need to use the 'CyanogenMod Installer' and do it all over again, including a letting the device being factory reset?
Confirming...Cyanogenmod OTA updates work, see the screenshot.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
While debugging application, emulator always get minimized while clicking on eclipse debugging environment, so its hard to see whats happen in emulator, and every time i have to maximize emulator see result of debugger, i want to know if there is any way to keep emulator on top of the screen so i can see whats going on screen while debugging the application.
There are three additional good ways to fix this other than the comment (which is also perfectly reasonable) above:
Have two monitors, eclipse running on one and the emulator on the other
If you only have one monitor and you're on Windows 7, then it comes with a great window stacking feature. Just press the 'window' button and the left arrow and the highlighted window will stack to the left. Press the 'window' button and the right arrow and the highlighted window will stack to the right. So you can stack eclipse on one side and emulator on the other.
If you only have one monitor and are on a mac, download the small and free app called cinch. Once it's installed, simply drag the eclipse window to the left and it'll stack it a-la windows 7, drag the emulator to the right, it'll stack it to the right.
Problem solved?
A possible workaround is to develop on a Linux-based environment. Most Linux distributions use window managers that allow you to set any window to be always-on-top.
I also recall reading somewhere years ago that the emulator performs better on Linux environments because it's based on QEMU? Not sure how true that is / still is, though.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question appears to be off-topic because it lacks sufficient information to diagnose the problem. Describe your problem in more detail or include a minimal example in the question itself.
Closed 9 years ago.
Improve this question
I am trying to run this app, but it works fine in the emulator, but on the phone it force closes when I click the speak button on it, it goes straight to a force close. What are the possible factors contributing to it not working on my phone?
the problem must be with your default TTS speach engine ,,,Check the following Link u may get suugestion
Android not acknowledging TTS Engine
There are multiple reasons why your app crashes.
Your device might be running Android that is before your app's SDK target.Check your logs, search for that method or object see if it is part of the device's OS version. Fragments are compatible with preHoneycomb devices using the compatibilty library.