Dalvik debugging expressed via live machine: - android

DDMS in the Android Eclipse plug-in used to have a Run menu that looked exactly like the Java window Run menu, with a "Run Configurations..." that took the user to the exact same launch tabs used to start an app under development.
I liked using it through the DDMS because--once an under dev. app was originally installed on a handset--I could rewite that application and test it immediately on the same live handset simply by launching the app through the DDMS. When the run was finished, that APK had in the process been updated directly on the handset--without me ever having to first remove the app from the hardware and reinstall the new version.
Something seems to have changed in the newest Android plug-in from last September (or later). The DDMS-side Run menu no longer looks like the Java-side Run menu. Instead the DDMS Run now has something called "External Tools," with a "Run As" and and "External Tools Configurations..." inside of it, neither of which allows me anymore to select my hardware Device in the upper left pane of the DDMS and Run it directly through there using the stuff I'd just written in the Java window.
Is there no way to do that now?

This bugged me for a long time too. It seems that if you have a java file open in your Java perspective and then switch to DDMS perspective than that run menu will be available. If you have e.g. an XML file open before switching to DDMS then the menu isn't there.

Related

Change default Android emulator when debugging Xamarin.Forms app?

I installed VS2017 a few days ago, created the simple app Build your first Xamarin Forms App, and now I want to debug.
I am having issues with the default Android emulator created by the VS2017 installation (Android_Accelerated_x86_Oreo) so I created a new emulator. This is the screenshot.
How can I change the default so it debugs in the newly-created emulator?
I wanted to point out that I'm new to all of this, so I would like to run it without having to install anything else. I would like to see something run before I install anything else.
I also wanted to point out that I've tried clicking on "Start" on either one of them when not in debug mode, and I get Could not start emulator. Unable to load DLL 'DismApi' error.
The only way it automatically starts is if I hit F5 and the emulator window pops up. Then I go to Tools > Android Device Manager and the default emulator says "Stop" (it's running). If I click on "Stop" and then press "Start", I will get the same error again: Could not start emulator. Unable to load DLL 'DismApi'.
Where you launch the debugger just click the arrow pointing down to open the dropdown. Then select you new device. It will stay as you default device. Please see the image for reference:
Note: You may have to restart Visual Studio for your new device to appear.

How to change target emulator in Android Studio?

I have several genymotion emulators for different API levels. The problem is this:
I run the app on a single emulator with the option 'same device for future launches' checked.
I open another emulator.
I run the the app again.
After this, the app only runs on the first emulator and I can't figure out how do I show the dialog (select target) again to run the app on both emulators.
Click Run → Edit Configurations...
Then uncheck Use same device for future launches
As mentioned by #B-GangsteR, you can also launch your app on multiple devices at the same time. To do this, select targets using ctrl key.
Note that even if "Use same device for future launches" is unchecked, you can't launch app on other device while it is still running on first device. So you've got to
terminate app on first device before running on another device,
or kill adb process (it will restart),
or run your app on multiple devices at the same time from the start (when choosing target, select multiple targets using 'ctrl' button or 'ctrl' + A)
In Android Studio 3.5 or above, the "Deployment Target" part of the configurations dialog has moved into the main toolbar.
Click Edit config beside run app.
Close the existing running app in all emulators to have this option even if the problem persist after doing configuration changes
You can change profiles by going to "Run" -> "Run..." -> "1.app" (click on the arrow) -> "Profile", then choosing which device (virtual or physical) you'd like to run on. This took me a while to find and I couldn't find anything like it in the answers above, so hopefully, I help someone out.
You can hold ctrl to select multiple devices (mentioned by #B-GangsteR).
In Android Studio 3.5, need to click on the Emulator name which is the left option of Run 'app' button.
You can select specific Emulator of your choice or multiple Emulator as well.

AVD Manager window blocks Eclipse window on Mac

I'm a complete newbie trying to learn how to write an app. I'm trying to run Hello World using the emulator in Eclipse on my Mac. I launch and unlock the emulator. Android Training then implies that I should click the Run icon in Eclipse. But the ADT Manager window is in front of the Eclipse window and Eclipse is disabled. If I minimize the ADT Manager window it just quits the ADT Manager, and then I must close the emulator window.
I did discover that I can run the app with the Run button without starting the emulator as a separate step, although that takes a long time to get going.
Another Answer implies that I can just rerun the app by clicking the run button again, but I can't do this because the Eclipse window is disabled.
I'm used to being able to use the IDE while a program (Yes, I'm an old programmer) is running. What am I missing?
Duncan
You're right - simply hitting run on the application cold turkey takes forever because the emulator has to initialize. When you click on your AVD Manager (where you can create, edit, and customize the android emulator you'd like to use), Select the emulator you'd like, then click Start.
After waiting for the emulator window to popup, just wait until the UI loads (when you can unlock the emulator).
At this point, it appears that the AVD Manager is still necessary (due to the "loading" type green bar along the bottom seemingly feeding the emulator), but you can just close the window, and the Eclipse window will become clickable again.
Now, you can just leave the emulator running. I typically leave it running for hours at a time (even overnight) and I can usually just click Run as Android Application and everything works perfectly.

Eclipse Android Emulator not working on Microsoft Surface Pro

I cannot get an Android Virtual Device to launch on my Surface Pro. I have had no problems on Windows XP, 7, or OS X.
I have tried launching from the AVD Manager, it opens the option dialog and when I select launch it acts like it is working, however the emulator never shows up.
When I select Run As Android Application from a project it acts like it is starting, once again nothing ever shows up.
Either way I get no error messages in the console.
I have tried disabling UAC.
Thanks for your help.
Right-click the program's icon and choose Properties.
When the Properties dialog box appears, click the Compatibility tab and then click the Run Compatibility Troubleshooter button.
Windows 8 tries to guess what version of Windows your program needs, and then it applies the changes. If the program begins working, you're through.
If the program still has trouble, though, move to Step 3.
In the Compatibility Mode section, select the Run This Program in Compatibility Mode For check box and select the program's desired Windows version from the drop-down list.
http://www.reddit.com/r/Surface/comments/1ael60/surface_pro_and_dj_software_also_android/
Please refer to my question and answer here:
< Android Emulator and AVD will not run on Surface Pro >
As it turns out you can run the Android Emulator and AVD on the Microsoft Windows 8 Surface Pro.
You will need to rollback the graphic drivers:
< http://answers.microsoft.com/en-us/windows/forum/windows_8-hardware/latest-graphics-driver-update-makes-bluestacks/1f67d99f-3626-4110-aa22-773856b226cb > Method 1: I would suggest you to roll back to the previous driver.
a) Press Windows key + X on the keyboard.
b) Click Device Manager.
c) Double-click on Display Adapters.
d) Double-click on your Graphic Card Drivers
e) Select the Driver Tab
f) Click on Roll Back Driver.
I still recommend using Bluestacks as an alternative method for Android Emulation.

Start two Android emulators with different locale

Most of the idea is in the title, I just would like to know if it is possible to start 2 emulators at the same time with 2 different locale (to test the I18n of my app). If there was a way of doing it in Eclipse, that would be greater...
Something like
If you click the Button for starting the emulator in Eclipse (the litlle mobile phone) Eclipse should open a dialog that lets you choose which android virtual device (AVD) you want to start. You can create a second AVD in this dialog and then start them both after each other.
Now you have to change the locale of one of the emulators to the wanted language. The emulator should save this settings so you have to configure this only once.
In Eclipse, this is easy to do. Use the Android Virtual Device (AVD) manager to set up as many emulators as you want. Depending on whether you've updated to the latest version of the Eclipse plug-in, the button to launch the AVD manager will either be a black phone or the Android Robot's head above a black square with an arrow in it. Either way it's in the toolbar near the shortcuts for Save, Print, etc.
In the AVD you can create various emulators with different Android versions (download other SDKs in the 'Available Packages' menu in the left). Once you've created the emulators, start them with the button on the right. You can have multiple emulators running at the same time if you want. The emulators have a program installed on them already called 'Custom Locale' that lets you change their location information. You can't do this while creating the emulators, but it's saved when you do in the emulator so you don't need to do it every time.
After that, to choose which emulator your program will run on, change its run configuration Target to manual. This is done by clicking on the more options arrow next to the green 'Start Program' button, selecting Run Configurations, the Target tab, then selecting manual. You can also do this by right clicking on your project in the project browser (list on the left), and the option is under 'Run As' -> Run Configurations.
To connect adb to a particular emulator or device, use one of the options "-e", "-d" or "-s " as documented for the ADB tool.
http://developer.android.com/tools/help/adb.html
In general the documentation is a great place to start.

Categories

Resources