Android Studio 3.1 does not showing 'android' option under Tools menu - android

I am using android studio 3.1 for some development.
But Its does not showing android option under Tools menu. Whereas Android studio 3.0 doesn't have this problem.
Here is the screenshot of android studio 3.1 Tools menu:
See missing the android option.
I think this is some configuration related problem as it doesn't exist in android studio 3.0. Basically I need Enable ADB Integration option. Is there any way to show the option in Tools menu?

If you're looking for a way to fix the buggy connection to a physically connected USB device without restarting Android Studio, this might help:
Preferences > Build, Execution & Deployment > Debugger
Then check or uncheck the box Use libusb backend

Google has officially removed the Memory Monitor tool in the Android studio 3+ and brings new Tool that is Memory Profile.
From the documentation for the tool:
To open Memory Profiler, follow these step:
Click View > Tool Windows > Android Profiler (you can also click Android Profiler in the toolbar).
Select the device and app process you want to profile from the Android Profiler toolbar. If you've connected a device over USB but don't see it listed, ensure that you have enabled USB debugging.
Click anywhere in the MEMORY timeline to open the Memory Profiler.
See the Google's Official Statement.

Can u find the android in the Help>action?
like shown below.
click on Find Action or Ctrl+Shift+A
After that try searching"Android" in the search bar.

From the android studio 3.1, android option menu is deleted and you can read it from the documentation : https://developer.android.com/studio/profile/monitor.html
if you want to open it, open from the android-sdk/tools/ directory then run monitor.bat
hope this help you guys

In my case, after update android studio separated that field from tools and located it at bottom-right corner.

I have faced the same issue after many tried I found the solution. In Android Studio 3.1.3,
Click File> Settings > Debugger > Uncheck Kill the debug process immediately and apply then again check it.

Probably because the Android options are already there, provided without an additional sub-menu.
Here is what there is under the Tools menu in Android Studio 3.0, all options are same, just grouped together:
EDIT: There are some missing items such as 'Enable ADB Integration', for these you can always use the Help > Find Action... where you type in the search, it will look like this:

adb seems to be deprecated in android studio 3.1. On Ubuntu I can run adb from the command line using Android/Sdk/platform-tools/adb and I can run the Device Monitor using Android/Sdk/tools/monitor. More information may be available at https:/developer.android.com/studio/profile/monitor.html

You can use Android Profiler if you want to measure app performance and inspect activity for CPU, RAM and Network instead of using ADB Integration.
For more Info. check this out Measure app performance with Android Profiler

Add navigation folder inside res and add a file like below file. In this file, we have two activities that are UI will show in this navigation file.
<?xml version="1.0" encoding="utf-8"?>
<navigation xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:id="#+id/nav_graph"
app:startDestination="#id/mainActivity">
<activity
android:id="#+id/mainActivity"
android:name="com.noman.navigation.MainActivity"
android:label="activity_main"
tools:layout="#layout/activity_main" />
<activity
android:id="#+id/oneActivity"
android:name="com.noman.navigation.OneActivity"
android:label="one_activity"
tools:layout="#layout/one_activity" />
</navigation>
you can also add this navigation via right click in res folder and section add a new resource.
By this, you will be able to see navigations on UI.

In my case, Android Studio 3.5.2, the location of the NDK bundle was not set in Preferences. To set NDK location, File -> Project Settings -> SDK Location then look for second field Android NDK Location. Once I provided the folder location for NDK bundle, Android Studio synced gradle again and built the app and showed all Android options under Tools.
link to image -- https://imgur.com/2yZVi0y

You could perform the following below steps to check memory usage.
Click View > Tool Windows > Profiler (you can also click Profile in the toolbar).
Select the device and app process you want to profile from the Android Profiler toolbar. If you've connected a device over USB but don't see it listed, ensure that you have enabled USB debugging.
Click anywhere in the MEMORY timeline to open the Memory Profiler.

I got the same problem.
Check you don't have any errors on the bottom of android studio. I got one with sdk build. If you got the same click on the link in error log.
Next go to file -> settings -> Appearance&Behavior -> Menus and Toolbars
Roll up Main menu -> Tools.
Choose Android.
Click on 'Apply' button and 'OK'.
Wait for a while (gradle progress-bar on the bottom).
I hope that I solve your problem.

Related

Android Studio Emulator Doesn't Open Seperate Window and It Doesn't See Emulator

When I start the emulator in Android Studio, it opens as a tab. I want to open it in a seperate window.
Additionally, my Visual Studio Code doesn't see this emulator.
Also, Android Studio, (and VSCode as well) doesn't see the emulator too. It isn't listed in select device.
I didn't use to have these kind of errors. I needed to delete Android Studio. I reinstalled it and things changed.
To resolve the issue, go to: File > settings > tools > emulator.
After that, untick "launch in a tool window" option.
Note:
Restart the program if you couldn't launch the emulator if instead you get a message that it's already launched.
With the new update it's possible to open the emulator as a new window clicking on settings icon -> view mode, there you can choose what's the best for you, maybe it can help.

Device Monitor is not showing in Android Studio 3.1 [duplicate]

I just upgrade Android Studio from 2.2 to 3.1. I am unable to find Gradle console and DDMS. Under Tools menu, there is no Android submenu that allow me to get DDMS
I tried solutions that I can find online in stackoverflow
1) File => settings => Menus and Toolbars =>Main menu=>Tools => Android.
I find under Android, there shows --------, no DDMS tool is listed, and
also the Apply button is grayed.
2) Help=> Find Action then type android for search. the screen display android
menu, under it displays AVD manager and SDK manager only.
Anyone gets same problem? anyone find the DDMS and Gradle console in version 3.1?
Under Tools menu, there is no Android submenu that allow me to get DDMS
They removed that menu. All supported tools are directly in the Tools menu. This is covered in the release notes.
no DDMS tool is listed
DDMS is deprecated. Most of its functions are now in Android Studio itself. You can still run the Android Device Monitor outside of Android Studio via the monitor tool, but you cannot have it and Android Studio 3.1 open at the same time, it appears. See the documentation for more.
anyone find the DDMS and Gradle console in version 3.1?
They removed the Gradle Console. There is the Build tool. By default, it gives you a tree version of the Gradle output. However, the second toolbar button down from the top, on the tool strip inside the Build tool, switches you from the tree view to raw Gradle output.
So, here is the Build tool in its default mode:
And here is the Build tool after toggling the toolbar button that I point to via the red arrow:
As you can see here (https://developer.android.com/studio/profile/monitor.html) DDMS is now deprecated. So you can use a new Android Profiler tool instead

How to open AVD manager in Android Studio 3.0 version?

after I update Android Studio from 2.3 to 3.0 version. I can not find AVD Manager in Tools/Android/AVD Manager.
I just did a fresh install and had the same issue. Solved by:
Click "Install missing platforms(s)..." in the highlighted error:
Then after the download/install, click "Intall Build Tools...":
Then after the download/install, you will see Android under Tools menu
If you have never used Android Studio Before, and do not have a Project
..Opening the AVD Manager is even trickier!!
For example, if you are installing it to use an emulator for a create-react-native-app project., but aren't otherwise using Android Studio to write or manage your app.
Here is how you can gain access to the AVD Manager.
AVD Manager is required to set-up your emulators.
Android Studio Documentation does NOT tell you how to gain access to AVD Manager. It starts at Open the AVD Manager!
I Just Need the emulator (and manager).
But I did not even have the window the OP refers to.
Nothing in the Configure menu, not Preferences (even Preferences -> Tools) gave me access to AVD Manager.
So in my case it was even more confusing to have No Direct Access AVD Manager !
Nor did I have an android folder in my create-react-native-app app, so hamdi's answer above did not work for me.
All I had was a new folder/git repo from:
create-react-native-app
My Solution
On the Android Studio Startup Screen, I choose:
Import Android Code Sample
Then choose any sample. (I choose the first example listed).
Then (after a bunch of downloading/building..), then brought up the window the OP refers to.
I then had to update gradle, as mentioned by user1449542's post above.
At that point, Muhammad Hannan's answer above was helpful !!!
I clicked the icon from the bottom image in his post -- vioa!
( Alternatively from the menu bar choose: Tools -> AVD Manager )
Better Solution:
I have since realized that the Startup Screen Option:
Start a new Android Studio Project
also works and is even quicker (less to download/build), and might not even need gradle file updates (mentioned by another post) that I had to do when I downloaded a sample project.
Just use the default settings to create a dummy project in the default location, and choose
Add No Activity.
Android Studio will "build" this dummy project, and set it up, then open the Window you need to access said icon, and/or menu bar.
In the future, this dummy project will appear on the left of Android Studio's Startup Screen.
Just click on that dummy project to re-open the window you need to access AVD Manager.
Then, as before, click that icon (or from the menu bar choose: Tools -> AVD Manager) to create/edit AVD emulators.
If you're using React Native (create react native app), you can start an emulator from the command line, once you have created an AVD emulator, and probably won't need to open Android Studio itself. (see notes below).
Be sure to start the emulator before choosing a (from the terminal window that's running your app via yarn start).
Additional Notes for reference:
To start the emulator from the command line:
emulator -avd <avd_emulator_name>
To list what emulators have been configured:
emulator -list-avds
AVD_Nexus_6P_API_23
AVD_Pixel_2_XL_API_27
AVD_Pixel_XL_API_25
So, for example, I can do this:
emulator -avd AVD_Pixel_2_XL_API_27
Additional Information
I also had to add the following lines to my .bash_profile
export JAVA_HOME=`/usr/libexec/java_home -v 10`
Note: the value between the back-ticks is what the JAVA install from my terminal replied. If you type that part into terminal by itself, it spits out the location Java was installed. If you have an different version of Java installed, just replace 10 with your version.
I then got the following path from:
- Android Studio Startup Screen -> Configure -> SDK ManagerPreferences
- Appearance & Behavior -> System Settings -> Android SDK
- Android SDK Location: /Users/sherylhohman/Library/Android/sdk
and used it as the value for adding the following line
export ANDROID_HOME=/Users/sherylhohman/Library/Android/sdk
Though I chose to write it as the following instead:
export ANDROID_HOME=$HOME/Library/Android/sdk
Finally I added:
PATH=$PATH:$ANDROID_HOME/emulator
PATH=$PATH:$ANDROID_HOME/tools
PATH=$PATH:$ANDROID_HOME/platform-tools
PATH=$PATH:$ANDROID_HOME/tools/bin
PATH=$PATH:$ANDROID_HOME/platform-tools/adb
export PATH
I may not have needed the ...adb or 1 or more of the last PATH entries.
This was a cumulation of many internet searches, many conflicting solutions. The major missing key was accessing AVD Manager (OP's question), which finally solved the problem. This just happens to be the items I had already added to my .batch_profile along the way trying to get the android emulator working inside my create-react-native-app App!.
I found this just under the toolbar in Android Studio (v3.2):
Go to the "Event Log" tab in the bottom right corner.
There will probably be some error messages. It will provide information and links to resolve the problem. Then the buttons will not be greyed out anymore.
I'm using Android Studio 3.0 on Ubuntu I have AVD under Tools > Android > AVD . And also on the right upper corner of the screen.
EDIT :
Go to Settings and search for AVD.
If you encountered the problem when using React Native, you are probably trying to include the whole project in Android Studio. You only have to include the android folder from the React Native project. After this process, Gradle will be synchronized and AVD Manager will come back.
I had the same problem.
If you get this message: "Frameworks detected: Android framework is detected in the project" then click on it and add Android.
After that, the icons should be enabled now.
you can find SDK manager,AVD manager TOP right side on android studio version more than 3.2.0.
and if you want to run via commmand promat you can go to
cd Library/Android/sdk/tools/bin
./avdmanager list
I had the same issue in Windows 10 and saw this solution in another post ... It worked for me.
Set-up the System Environmental Variables ANDROID_HOME and ANDROID_SDK_ROOT
To do this ...
Click the windows key and start typing System.
Select it when it pops up in the menu.
Click advanced system settings
Select the advanced tab
Click Environmental Variables at the bottom
Under system variables, click new
Enter the variable name
For value, enter the the path to the Android SDK, which will most likely be: C:\Users[username]\AppData\Local\Android\Sdk
Use the same path for both variables
In Andriod Studio 3.5 its here
Following the event log to install resolves the issue
Hit ctrl+shift+a and search avd and click on it
I was not able to find AVD manager in android studio easily for Android studio version 3.1.2.In order to launch AVD manager, i had to create a sample project and then launch it from there.
I have documented all my steps here, in case any one wants to get benifitted.
How to launch AVD manager on Android Studio 3.1.2

Visual studio can't debug Android Xamarin app

I've started with Xamarin and Android using Visual Studio 2013.
When I start debugging the android app, it builds, deploys to device and then debugging in Visual Studio stops. I can't hit any breakpoint. App is working in device, but I cannot debug it.
Am I missing something?
I've tried various emulators and a physical android device but debugging doesn't work in any of them. It just act like I have stopped it.
Debugging the same solution in Xamarin Studio works, I just can't get it working in Visual Studio.
I was having the same problem and I found this workaround with Hyper-V in Xamarin's documentation: https://developer.xamarin.com/guides/android/deployment,_testing,_and_metrics/debug-on-emulator/visual-studio-android-emulator/
TL;DR; Open Hyper-V Manager -> Go to settings on your emulator -> Go to processor settings -> Select Compatibility -> Mark the "Migrate to a physical computer with a different processor version" checkbox -> Done! (At least for me) VS is now debugging my Android App
Another reason why Visual studio can't debug Android Xamarin app with a Hyper-V is due to you donĀ“t have 'Deploy" option check in android project.
Steps: 1) Enter in "Solution properties" 2) Select "Configurarion Properties" 3) Check "Deploy" in Android project.
Make sure you are running on Debug mode (on target).
Then, check the Properties of the App Project and see if it's using the Xamarin debugger instead of the VisualStudio Debugger.
Enter in "Solution properties"
Select "Configurarion Properties"
Check "Deploy" in Android project.
Open Hyper-V Manager
Go to settings on your emulator
Go to processor settings
Select Compatibility
Mark the "Migrate to a physical computer with a different processor version" checkbox
This will also happen if you don't have any activity marked as your main launcher activity:
[Activity(
...
MainLauncher = true,
...)]
public class MainActivity ...
Easy mistake to make if you're shifting code in from a prior project and the prior project is using a splash activity and your new project is not yet doing so.
Go to property of app project then click android option and checked checkbox in debugging section.then run again.
For anyone who might still need help. Also make sure the build and deploy checkbox's are checked in the configuration manager. .
In my case, after some investigation, I saw I was having this warning: "Failed to read .android.dll' with debugging symbols. Retrying to load it without it. Error details are logged below. 2>Mono.Cecil.Cil.SymbolsNotMatchingException: symbols were found but are not mathing the assembly"
The solution was to disable linking:
Right-click the Android Project -> Properties -> Android Options -> Under "Linker properties", set Linking to None (see image below)
Got this from TedFalasco's answer on this post.
Hyper-V manager can't be installed on Windows 7 (only the management tool gets installed) so if you get this problem, following those steps don't help.
Here is the thing that worked for me and it's mentioned here as an answer but hasn't been marked up or marked as an answer. This is actually the best and easiest solution. nothing else worked for me.
In Visual studio, make sure you choose the solution file (not project files) in the solution explorer. Then go "Project > [project]properties"
in the left pane choose "Configuration Properties > Configuration"
Now check the Deploy feature if possible. Only deployable projects have the option.
This saved my life and I almost gave up on Xamarin. I really hope this helps others like me.....
In my case, the warning was self-explanatory:
Set the debugging information to Portable in the Visual Studio project property pages or edit the project file in a text editor and set the 'DebugType' MSBuild property to 'portable' to use the newer
In other words: Right click on project => properties => build => click on advanced => set the debugging information to portable.
I have tried every answer and none of them worked.
Here is what I did to make it work again:
Plug your physical android device to the computer. Android device must have Developer options enabled.
Choose your android device in Visual Studio.
Run app in Debug mode. Your app should appear on your android device.
Unplug your android device from computer.
Try running your app in android emulator. For me Debug option starts working again.

Android Device monitor disabled

I'm just getting started with Android development and was setting up Android Studio on my mac. (Following the instructions here)
When trying to run a simple hello world application and trying to learn my way around the IDE, I noticed the "Android Device monitor" disabled. Any ideas how I can fix this? This should be important when debugging apps hence the question.
I'm not sure what other info might be important for this question. I did make a few changes in the SDK manager, but they were just installing more components on top of what was already installed.
Once you open a valid project, the buttons become enabled.
Note that, even if the option is disabled, you can still bring up the Device Monitor by running the monitor.bat file in the tools directory of the Android SDK. (On Windows you can just double click the file or run it from a cmd shell.)
This problem occurs to me today. And I just click the button on the pic.
Problem solved.
and If this didn't work ,you can check this list in your Android Studio
1.Tools->Android->Enable ADB Integration
2.If you open DDMS, CLOSE it .
If these didn't work too, check the official file.
https://developer.android.com/studio/profile/am-basics.html

Categories

Resources