Windows: Application doesn't launch
We have 2 possible issues: - On some systems the launcher script does not find where Java is installed. Workaround is to set a variable indicating the location of Java [b/55281]:
- Open Start menu > computer > System Properties > Advanced System Properties
- In the Advanced tab > Environment Variables, add new system variable JAVA_HOME that points to your JDK folder, for example C:\Program Files\Java\jdk1.7.0_21.
- Another issue we found is that the launcher script uses an option that is unknown to Java on some system [b/55267]
- Open the installation folder of Android Studio (e.g. C:\Programs Files\Android\android-studio, or C:\Users\<username>\AppData\Local\Android\android-studio) and find the "bin" directory in there.
- Open a "cmd.exe" (command prompt), cd to the android-studio\bin folder and run "studio.bat". You will most likely see an error: for example b/55267 is about the option -XX:+UseCodeCacheFlushing not being recognized. Report the error, remove the line from the studio.exe.vmoptions or studio64.exe.vmoptions and it should now work.
Apologies for this weak launcher.We know 0.1 is pretty rough and we're working actively on getting things better.
Tools R20
SDK Manager
- If you have Tools 20.0.1 and don't see the latest 20.0.3 update, a simple solution is to open SDK Manager Tools 20.0.1 and use the menu Packages > Reload. You will then see the Tools 20.0.3 update.
- Explanation: The SDK Manager in Tools 20.0.0 now has a cache mechanism -- it keeps a local copy of small manifest XML files to perform a faster start when opened. There's also a mechanism to automatically update the cache. However in Tools 20.0.0 and 20.0.1, that refresh is broken and in some conditions the manager will not show new tools that are available unless a reload is performed. Clearing the SDK Manager cache or manually forcing a reload forces the manager to get the latest manifest.
Tools R15
SDK Manager
- When using the command-line interface to install packages, system-images are not installed. [See issue for a workaround:
21880]
Tools R14
Emulator
- Fixed in r15. Wipe data is broken. Manually remove userdata-qemu.img from the AVD folder under .android/avd/<avdname>.avd/ (Mac/Linux: in ~, Windows XP: C:\Documents and settings\<user>\, Windows Vista/7: C:\Users\<user>).
- Snapshot support is not completely working for Android 4.0 system image for now. After loading a snapshot, some hardware features (sensors, gps, camera) will be broken.
- Loading earlier snapshots (created with tools version < 14) is broken. Symptoms include emulator failing to boot or crashing. We will improve version detections to more gracefully handle incompatible snapshot format, but for now, you’ll need to delete them and recreate them.
- Fixed in r15. Some linux users are reporting crashes when launching the emulator and have figured out that trying to access the webcam is the culprit. [Issue:
20952]
You can disable the webcam by editing the AVD ini file and adding hw.webcam.count=0 in it.
Note that you can also add this through the AVD Manager. Edit the AVD and in the hardware section, click add, find "Number of emulated web cameras" in the drop down and add it to your AVD.
Build System
- 9-patch issue in Library. If the 9-patches located in library don't look like 9-patch (they appear as stretched bitmap) in your application, try to refresh the library project and do a clean build of the application. Changing your workspace to refresh automatically will help as well (in Preferences under General > Workspace). We will be improving this to not require forced refreshes.
- Fixed in r15. Renderscript fails to compile application targeting 11-13. This is due to the build system passing older headers to the compiler. [Issue 21006]
Workaround: Replace <SDK>/platforms/android-[11|12|13]/renderscript with the version located at <SDK>/platforms/android-14/renderscript
- AAPT crashes on Windows in some cases when the build output is set to verbose.
The workaround is to set Eclipse>Preferences>Android>Build>Build Output to less than Verbose, e.g. Normal.
We have a fix, which will be available in tools 16. [Issue 20395]
- AAPT crashes when a <style> (in a resource XML file) contain an <item> with a "+@id/..." reference.
AAPT should either ignore this or report an error since this is not the place to create a new id.
The workaround is to not use the +, write the reference as "@id/...". [Issue 20479]
DDMS/ADT LogCat View
Fixed in r15. On certain machines, the logcat view will stop scrolling to show the latest received log message. Moving the scroll bar manually to the end should trigger the view to auto scroll, but it stops again after a short time.
SDK Manager
When updating Platforms Tools, the log displays an error: 'adb kill-server' failed -- run manually if needed’. The error is benign, please ignore it -- in fact it just means ADB isn't running, so it can't be stopped. [Issue: 18868]
AVD Manager
ADT
- Projects don't show the Project Libraries container with the library jar files.
This can happen when starting Eclipse. Closing and opening the offending project should properly populate it again with the library jar files.
- Fixed in r15. The SDK Manager and the AVD Manager windows cannot be resized. On Linux, behavior is a bit odd -- the window can be shrunk but not expanded. [Issue: 20939]
Testing
Fixed in r15. ant test fails with Syntax error: Bad substitution.
A last minute change introduced this error in the Ant rules file. The workaround is to edit <SDK>/tools/ant/build.xml, line 318 and to change ${manifest.package} with ${tested.manifest.package}. [Issue 20979]
Tools
Fastboot.exe is missing from the tools folder. It will be added later in tools 16. In the meantime it can be found in the tools 13 windows archive. [Issue 21115]
Tools R13
SDK Manager
- "Help, I'm using the SDK Manager and don't see any old SDK, I can't update anything except SDK Tools 14".
This
is expected if you're using the SDK Manager from ADT 13 or earlier, or
the tools 13 or earlier. We had to change the XML schema used by the
download site to support some new features. Please first update the
tools to Tools 14, or your ADT to version 14. You'll be then able to
install all the SDK platforms and packages as usual.
- On Windows, updating the tools may result in the following error:
Updating SDK Manager.exe
Error: The process cannot access the file because it is being used by another process.
There are 2 easy workarounds:
- Open an Explorer on the SDK tools folder and manually launch android.bat from there.
- Open a cmd.exe, cd to your SDK and type "tools\android.bat".
[Issue 11989]
|
|
