1,234
edits
Changes
→telnet
package:com.android.development
</pre>
== monitor ==
This is a replacement for the old ddms command. You can use this to graphically read the logs (and filter them), monitor memory and CPU usage, download and upload files.
== telnet ==
OK
</pre>
= Android Studio =
In the last lab we installed Android Studio but we haven't used the application itself. The package you used for installation included:
* Android Studio, an IDE specifically designed for Android development. It's based on IntelliJ IDEA. A replacement for Eclipse.
* All the command-line tools we've used so far.
* An Android SDK.
* A version of the Android system image to run your app in the emulator.
* An AVD using that image.
Biggest change from Eclipse is move from Ant/Make-based build system to one using Gradle. Another very big change for some types of development is the lack of support for the NDK.
You can use Android Studio as your main IDE for developing an Android app, including:
* Managing all your source files and directories.
* Editing Java, XML, Gradle, other text type files.
* Graphically editing layout XML files.
* Building, deploying, and debugging your apps.
* Using version control.
* Working with the SDK manager, AVD manager, and the Android Device Monitor.
The only downside to it is it's not very stable. Google releases new versions often and they're not backwards compatible, so you may have to relearn how to do some things. Gradle build files are particularly bad when it comes to that. Often you'll find instructions online that simply don't work at all - it's possible the reason is you have a newer version of Android Studio or one of the tools it's using.
Android Studio can update itself to the newest version. Just go to Help/Check for update.
