I only need what's relevant for the development and testing. I don't need the huge "emulated" dumb bezel area mostly good for grabbing and relocating the emulator window. Even the real devices start to eliminate those bezels nowadays.
I don't need the directional clues about the device orientation it provides. Just small grabbing handle should be enough on the tool strip or in the main window.
It wastes screen real estate and makes tiling besides other useful windows hard or inefficient (even with my double monitor setup).
How can i hide or remove it?
It no longer works: if I remove the properties (using the small trash button or leaving them empty), the manager will restore them. (My version: Xamarin.Android SDK 10.2.0.100)
But I've found another solution:
Open Android Device Manager from Visual Studio.
While your device is powered off, click the "..." in the top right corner
Select "Show in explorer"
Edit the file "config.ini"
Remove the skin.name and skin.path properties and save file
Start the device!
Open Android Device Manager from Visual Studio.
While your Device is powered off Click Edit
Find the property skinname and clear the value (leave empty)
Find the property skinpath and clear the value (leave empty)
Click Save & Start Device.
Worked for me
Show in Explorer now called : Reveal in Explorer
And you can just add // before skin for example:
//skin.name=pixel_xl
Open Android Studio -> Tools -> AVD Manager -> Pencil Icon next to Your Virtual Device -> Uncheck 'Show device frame'
Related
A friend of mine (who doesn't have enough reputation to post images) is facing a problem with his emulator. It is not rendering as it should, even though the clicks are where they should be. In order to click on the Back button, he must click down in the black part of the "screen".
He already tried to restart his computer, change monitor resolutions and creating another emulator images.
He uses KDE and is using his NVidia hardware to process graphics.
My answer from this post: Android emulator screen fills up only some fraction part of actual android emulator screen
Best and simplest way to do it on Windows 10:
Close your Android Emulator if it is open
Right-click desktop
Click Display Settings
Set Scale and layout to 100%
Open Android Emulator
Revert your Scale and layout to the (Recommended) percentage
WORKS 100%
You can fix the scaling issue when using the Hardware rendering by simply making windows override the scaling setting. How?, it's very easy. Simply locate the .exe file for the emulator that you are using, (e.g. "qemu-system-armel.exe" for ARM and "qemu-system-x86_64.exe" for x86). To make sure which .exe file, just run the emulator then use task manager to locate the .exe file is running, see the screenshot. locate the .exe file using task manager
In my case it was in this location: "C:\Users[Username]\AppData\Local\Android\Sdk\emulator\qemu\windows-x86_64\qemu-system-x86_64.exe"
Now just right click on the file then click on properties then choose the "Compatibility" tab. Under "Settings" at the bottom, click on "Change high DPI settings". A new window will open. Tick the last checkbox "Override high DPI scaling behavior." under "High DPI scaling override". Then select from the drop down below it "System" (this is very important or it will not make any difference!), see the screenshot below. Now just hit OK and OK. Restart Android Studio and that's it, problem solved :)
I installed Android Studio 0.8.2
I am not able to get it working with two monitors.
If I have the main application in the left monitor, I want to be able to have the other windows like Event Log,Messages, etc.. docked together in the right monitor.
I can get the windows over to the right, but only if I check floating on the window. And when I do get the window over there to the right, when I click anywhere back on the left monitor, the windows in the right monitor disappear.
I am also not able to figure out how to dock multiple windows together in the right monitor.
I was able to do all of this very easily with Eclipse.
Should I just go back to Eclipse?
Have a look at the official documentation for Tool Windows.
In particular, you may want to refer to the Viewing Modes's Fixed / floating mode section on how to disable transparency for floating windows. Tool windows should not disappear when they lose focus, but they can become semi-transparent.
Additionally, you can have a read through this article which provides a lot of useful information for Eclipse users when switching to IntelliJ IDEA / Android Studio.
If you intent to have dual monitors run android studio.
Open the main screen of AS in your primary monitor.
Select the bar which you want to drag to secondary monitor.
Hit Right click and you should get the following options: Floating Mode, Docked Mode etc..
Select Windowed Mode & you should have a your desired in windows mode
Drag the window to secondary monitor.
Drag the debug window to another monitor, maximize and select Pinned from the settings (gear button top right).
So Pinned mode and Floating mode should be enabled.
With 3.5.0
Just drag the editor tab to the new monitor.
It should turn into a window.
Then you have the main window that holds the docked tool window(s) and a separate editor window.
For Android Studio 3.4.2
Click Window/Active Tool Window/Floating Mode
Now you can drag windows to the second monitor.
I was trying to fix my problem "hardware buttons not enabled in AVD" after an hour research
all I found was people who lead people to go to "hardware section and fix blabla"
but interestingly my AVD doesn't have this section.I actually found some of options under Device Definitions but still couldnt fix my problem nor found this menu.All screenshots I saw had Hardware section...
My specs are; MacOS , Android 4.2.2 (Api17) , Eclipse
P.S:everything else works perfectly .I am just missing this section.
The instructions you were looking at were probably from R20 or earlier versions of the Android Developer Tools. R21 is different and appears to be what you are running. You change the behavior of the hardware buttons on the Device Definitions tab for whatever device is associated with your AVD:
Change the Buttons drop-down to Software or Hardware depending on what you want the behavior to be.
After lengthy trial and error, I banished the "hardware buttons not enabled in AVD" problem by discovering that there are at least three distinct 'gotchas' that must be set properly. I am using Eclipse Java EE Juno with ADT version 22.3.0 (latest as of 2013 Nov 3).
In summary, it's a bit awkward to figure out the first time, but simple thereafter. The virtual device definition must include 1) hardware buttons, 2) the device definition must also be chosen in the AVD selector drop down field, and 3) the box must be ticked for displaying a skin with hardware controls. All three are critical. Step by step:
Window → Android Virtual Device Manager (See screen capture below) (NOTE: If not visible in menu, choose Window → Customize Perspective and tick Android SDK and AVD manager - but assume this has already been done if you have gotten far enough to get the above error message)
Click the first tab, which is Android Virtual Device, click Edit, and note the name of the Device listed in the second combo box field from the top. This is going to be either a built in default Android virtual device definition, or a custom one you have created (or will create) from scratch. Make note of this Device name and close Edit Android Virtual Device edit window by clicking "OK"
Click the second tab in Android Virtual Device Manager which is Device Definitions and select the device you remember from step #2 above from the list (Note to emulator developers - this setup step is slightly more awkward than necessary - perhaps tabs one and two could be tied together more closely to allow double clicking a device and editing it directly instead of having to close a tab then opening another). After selecting the virtual device definition, choose Edit (or Clone if the device you want to edit is a built-in definition because if it is a built-in device, it must be saved as a cloned copy once edited. Name the cloned device something memorable in the top left field of the Clone Device window, e.g. add "_hardwareButtons" to the end of the default name).
IMPORTANT: Edit the cloned device: Ensure that Buttons → Hardware is chosen on the right hand side, fourth field down, of the Edit Device (or Clone Device) window (from step #3 above under Device Definitions tab). This is critically important or the Hardware buttons will not be active. This is the most likely root cause of the above error message. It's OK to leave Input as No Nav unless you want to use the virtual DPad. Click Edit Device (or Clone Device) at the bottom right of the window to save your changes.
IMPORTANT: Inside Android Virtual Device manager, click first tab again, which is Android virtual device. Select Edit and ensure that the newly edited, created, or cloned device is selected by name in the Device field drop down combo box (second from top) of the AVD. (see top two screen captures above). It is critically important that the proper device is chosen here, because creating a newly cloned device does not automatically update, or associate it with, your AVD (see my comments to emulator developers above).
IMPORTANT: Also inside the same Android Virtual Device edit box, Make sure Skin → Display a skin with hardware controls is ticked. This is also critically important or you will not see any hardware buttons at all. Click "OK" to close Edit window.
For good measure (possibly unnecessary) I clicked Refresh in the first tab (Android Virtual Device) of AVD manager and looked to be sure that a green checkmark was in front of the AVD I just edited. If not, it's probably because the newly edited device is not yet connected with your AVD. Click Edit and again choose the proper newly edited device name. Click "OK" to close.
In addition and optional for the truly paranoid, you can click Details under AVD first tab and expand the window to look at your device definition specifics. Make sure that skin.dynamic is yes, hw.keyboard: is no (unless want keyboard) and hw.mainKeys: is yes and hw.dPad: is no (unless want dPad) and, as always, ensure that you have the proper device name chosen.
Now you should have a perfectly viable AVD defined that you can use in the RUN → RUN CONFIGURATION Eclipse menu and it will not display the dreaded "hardware buttons not enabled in AVD" error message.
In Eclipse, RUN → RUN CONFIGURATION, choose your app name from the left hand side (and make sure it also appears under Android tab) and that the newly defined AVD is ticked under the Target tab and click RUN. (or CTRL+F11 after the first run of any new configuration).
Here are some screen captures from a tablet emulator as an example:
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.
I need to take screenshots of an android application running on an emulator in Eclipse Galileo.
Is there a built-in feature for this or do I have to download a plugin of some sorts?
You can take a screenshot if you open the Android view "devices" (under Window --> Show View --> Other... --> Android --> Devices). Click on the device or emulator you want to take a screen shot of, then click the "Screen Capture" button (it looks like a little picture, and it should be next to a stop sign button). Occasionally the device won't immediately load the picture; sometimes you have to close/reopen the screen capture window.
This is equivalent to taking a picture via DDMS, but you can do it in Eclipse instead of opening another application.
Screenshots on Android Devices using Eclipse, a Visual Guide
In the DDMS perspective in Eclipse there is a "Screen Capture" button. (Make sure you have your Android SDK and Eclipse plugin up to date, not sure this was always an option). Just press that button and a screenshot of whatever device you have DDMS connected to (either a real Android device or the emulator) will be created and opened in a new window where you can save it as a png.
You load the emulator with your app normally, through Eclipse, but you take the actual screenshot from DDMS, a tool that's included in your SDK, under the "tools" folder.
In DDMS, press Ctrl+S to take a screenshot.
1-open the DDMS prescriptive,the right click on mouse.
2-there click on export screenshot.
3-then it will show you option to save your file as .png file,with whatever name you like you may save it.
I just do a control print screen, which copies the image into the clipboard, then open MS Paint then do a control Z. Then you can crop and size it to your liking. Is this ok?