Since Android studio 2.1 update DDMS won't open - android

I've update my android studio to 2.1 and also downloaded the new Android N Preview.
Since this I can't open Android Device Monitor(DDMS).
It seems it has been deleted from my PC or it can't be located because it's moved or something?
I don't even get any error messages! When I click on Android Device Monitor it just does nothing.
I am using a 64bit Windows 7 machine with JDK 8u72
Has anyone encountered the same problem?

I've got DDMS back by doing the following things:
By removing Android SDK Tools, Android SDK Platform-tools and the Android N preview
Installing Android SDK Tools and Android SDK Platform-tools
I haven't yet tried to reïnstall the Android N preview, so I don't know if that will give the problem again.

Related

Android Studio is unable to find ADB, yet I'm able to deploy to my device

The exact error I'm getting is "java.lang.Throwable: ADB not found"
I haven't found anything online matching my problems. I have already (manually) reinstalled the platform tools multiple times. And they work. I can connect to my phone, even Android Studio is able to run the project on my phone. Yet it throws that error and locks some of the features like Logcat (I can use Logcat via the shell just fine). I've also tested Android Studio 3.3 additionally, but it didn't change anything.
The google USB driver is installed too.
The ADB tool is originally installed on .../android-sdk/platform-tools/platform-tools/ and Android Studio doesn't recognise the tool inside this location. After tried all the other suggestions, the only solution that worked for me was to copy the adb file from this folder to the parent folder: .../android-sdk/platform-tools/. It worked like a charm.
Some particularities of my system:
OS: macOS Catalina
IDE: IntelliJ IDEA CE (the same occurred when I tried to work with Android Studio)
SKD installation method: installed trough Homebrew with the cask android-sdk (the same occurred when I tried to install from within Android Studio)
It seems like you installed adb drivers externally and not via Android Studio and hence they are not present inside the platform tools of the Android SDK. I would recommend installing it using Android Studio's inbuilt SDK Manager.
Steps
Open SDK Manager in Android Studio (you can find it at top right
with android logo and downward arrow and also in the Tools Menu at
the top).
In SDK Manager click on SDK Tools tab and checkmark the
Android SDK Platform Tools
Apply changes and your issue should be resolved.
I hope this helps.
I am attaching a Screenshot for your reference:-
When I opened Android Studio today, it randomly worked.
The whole "whole App chrashing on startup"-thing was a bug I introduced.

Android Studio 3.2 for Windows wrong repository

today I tried to install Android Studio 3.2 in Windows 10 and I received a lot of errors. When I tried to correct I observed that download is getting WRONG MACOSX sdk and tools. Anyone know how can I correct it?
You can manually download SDK for Windows here and extract it: https://dl.google.com/android/repository/sdk-tools-windows-4333796.zip
Then you go to Android Studio settings and point Appearance & Behavior -> System Settings -> Android SDK to extracted folder.

Why am I getting: "No system images installed for this target"

I'm having trouble with the Android emulator.
I am running on Windows 10, and here is my environment:
Microsoft Visual Studio Professional 2017
Version 15.5.6
VisualStudio.15.Release/15.5.6+27130.2027
Microsoft .NET Framework
Version 4.7.02556
Xamarin 4.8.0.760 (fc93f3f5b)
Visual Studio extension to enable development for Xamarin.iOS and Xamarin.Android.
Xamarin Designer 4.8.188 (c5813fa34)
Visual Studio extension to enable Xamarin Designer tools in Visual Studio.
Xamarin.Android SDK 8.1.5.0 (HEAD/75f8c6838)
Xamarin.Android Reference Assemblies and MSBuild support.
Xamarin.iOS and Xamarin.Mac SDK 11.6.1.4 (db807ec)
Xamarin.iOS and Xamarin.Mac Reference Assemblies and MSBuild support.
My Android SDK Platform looks like:
and the SDK Tools is:
In my emulator screen, no matter what device I choose, I get the error:
"No system images installed for this target".
I clearly have installed the Google ARM System Images.
I don't understand why I'm getting the error message.
Any help will be greatly appreciated.
Charles
Update 2
I would like to thank York Shen, and Jon Douglas for their help. The Device Emulator now works... well almost.
I installed the Intel HAXM Emulator Accelerator. My console script was:
I also selected the Accelerator from the SDK Tools:
When I try to define a new device using the Emulator Manager, I now get:
Obviously, I still have a problem with HAXM. By the way, if you tell me I have to change my computer's BIOS to make HAXM work, I will give up on Android.
I tried to run a default emulator, and it warned me that I could continue, but without any acceleration. A simulator appeared but my application did not run. My application only runs on iOS and UWP.
I'm going on five days in trying to get the Android Emulators to work. No cigar. I contrast this to my experience with the iOS Emulator. That one took me about 1/2 an hour to get running. It was very clean and simple. I'm thinking seriously about abandoning all software development for Android.
Why am I getting: “No system images installed for this target”
As #Jon Douglas said, you are using a deprecated version of the AVD Manager, you could refer to the docuemnt:
As of Android SDK Tools version 26.0.1, Google has removed support for their UI-based AVD and SDK managers in favor of their new CLI (Command Line Interface) tools.
You could refer to my answer for a more detailed answer about how to solve this issue:
Xamarin with Visual Studio not detecting CPU/ABI system image for emulator, even though system images are installed
Update:
If you use the Xamarin SDK Manager and Xamarin Android Device Manager, you need update to Android SDK Tools 26.0.1 and later (which is required for Android 8.0 Oreo development).
You could read this: Requirements. In your situation, upgrade your Android SDK Tools version to 26.1.1:
Update 2:
You need Installing the Xamarin Android Device Manager, then you could start the Device Manager by clicking Tools > Android Emulator Manager:
To help anyone scratching their heads as to why when they install a new version of Visual Studio 2017 the emulator looks different to York Shen above, its because Visual Studio didn't bundle the latest version of the AVD Manager into Visual Studio 15.6.6 (as of 23rd April)
I followed #York Shen - MSFT's answer until I hit a snag on the update of the Android SDK tools. I simply downloaded them from https://developer.android.com/studio/#downloads (Command line tools only, sdk-tools-windows-4333796.zip).
Copy the contents of the tools folder into C:\Program Files (x86)\Android\android-sdk\tools

Xamarin - disconnected from layout renderer

I just downloaded xamarin studio. I get an error message "disconnected from layout renderer please close the file and try again" whenever i open a axml in the layout folder. I can view the source but can't go to the design tab to add controls. Closing the filed does not work.
I'm not sure how to find what version of xamarin.android i'm using but I just downloaded last night. When I go to the SDK manager it tells me my Android SDK Tools are version 23.0.4.
I found this old thread on the same topic. I tried renaming my tools folder and downgrading but that didnt' work either. It told me I need tools of at least version 22.
http://forums.xamarin.com/discussion/14344/disconnected-from-layout-renderer-error-after-updating-android-sdk-tools-to-version-22-6
I've tried uninstalling Xamarin Studio and reinstalling and that didn't help. I do have Visual Studio 2013 with update 3 installed too. But then I also tried installing Xamarin Studio on another laptop with Visual Studio 2012 and got the exact same problem.
Note: this error displays in both Visual Studio and Xamarin Studio.
I really hope I can get this resolved as i'm evaluating Xamarin for 2 companies. Any help is greatly appreciated.
-Randy
The solution is here: http://forums.xamarin.com/discussion/comment/51784/#Comment_51784
Only this time, you need to downgrade from 23.0.4 to 23.0.2.
Just found this out the hard way.
Cheers
Thank you Balint! You made my weekend!!! Here is a direct link to the tools version that works.
http://dl-ssl.google.com/android/repository/tools_r23.2-windows.zip
I recently had this same issue when trying to open the main.xaml in Xamarin Studio for Mac OS X. Here are the steps I took to resolve the problem:
Open the Android SDK Manager in Xamarin Studio and delete the Android SDK Tools.
Re-download the SDK Tools from [https://developer.android.com/sdk/index.html?hl=i]. Revision 23.0.2
Make sure the downloaded SDK is unzipped in the path /Users/username/Library/Developer/Xamarin/android-sdk-macosx
Then I launched the SDK Manager from the Terminal using cd library/developer/xamarin/android-sdk-macosx/tools ./android
When the SDK launches, make sure the Android SDK Tools is not selected, else it will update it to 23.0.5 which appears to currently be broken.
After the SDK Manager updates and installs all the packages, re-open Xamarin Studio and go to Preferences -> SDK Locations -> Android and chose the path for the Android SDK.
After following these steps I was able to successfully open the main.xaml files for Android on OS X.

Eclipse crashes on Android SDK and AVD Manager

I tried to install Android SDK plugin on my existing Eclipse Classic 3.6.0 (Helios). I managed to do everything else, but when I try to add components using Android SDK and AVD Manager in Eclipse, whole Eclipse just crashes.
Anyone have any idea what's going on?
Eclipse Crash Log on pastebin.com
NOTE: there is NO date shown on this page( Currently 2010 Nov )
This page states,
http://developer.android.com/sdk/requirements.html
System Requirements
Supported Development Environments
Eclipse IDE
Eclipse 3.4 (Ganymede) or 3.5 (Galileo)
Caution: There are known issues with the ADT plugin running with Eclipse 3.6. Please stay on 3.5 until further notice.
ALSO NOTE
looking at your pastebin.com post
you PATH variable is corrupt
As of Feb 2013, using Android Dev Tools (Android SDK and Eclipse), build v21.0.1 - the AVD Manager crashed repeatedly using JDK v7x. Using JDK v6x resolved the issue, able to setup virtual devices now.

Categories

Resources