BlackBerry Plug-in for the Android Development Tools

When you signed the .bar file of an app after deleting the existing signed .bar file, the resulting signed .bar file was generated with the incorrect author name and resulted in application deployment failure. (6721844)

When you deployed an application in the Android Player, you may have received the error ActivityManager: Warning: Activity not started because the current activity is being kept for the user. (6404004)

When deploying an Android application to a Wi-Fi target, the application was installed, however just after launch the error: “ Connecting <IP> to ADB failed” was thrown. (6334119)

When an Android application was installed using development mode, the Push Service for Android would not start with the rest of the Android framework. (6317491)

The Android Runtime did not start on the first attempt to Run or Debug an application from the Eclipse Plug-in when no Android applications were present on the device. (6285522)

When a project was signed, the .Isv file was not generated, so the project could not be signed more than once. (6011873)

On Windows 7 64-bit, when a signed .bar file with an error was right-clicked, there should have been an option "Sign For AppWorld" under BlackBerry Tools. Instead, there was no option. (6001326)

While using BarUtils class, when extractManifestEntries() method was called, "java.lang.NullPointerException" was thrown at runtime. (5987559)

Eclipse froze during the invocation of the context menu on an Android project. (5841679)

On Mac OS, when an application was re-launched after disconnecting a debug session, the application froze. (5841437)

The Android application was not displayed if the previously deployed application was minimized and appeared in the thumbnail. (5794136)

When an Android application was deployed from Eclipse, the screen was blank. (5753961)

The ADB connection failed after Eclipse was idle for an extended period. (5705581)

If a .bar file and the corresponding .apk file were not in the same folder, the .apk file was not verified during .bar verification. (5609074)

When a signing error was right-clicked, Quick Fix was disabled. (5501452)

When the packager was used to convert an .apk file with an icon to a .bar file, the aspect ratio of the icon changed. (5548139)

When a repackaged .bar file was installed on the target device, an outdated OS version warning was not displayed if the OS version running on the target device was earlier than 2.0.0.7109. (2897190)

If you have Java SE SDK v7.0 installed, you cannot create or load a debug token for testing.(7183296, 7020505)

Remove Java SE SDK v7.0 and install Java SE SDK v6.0.

When you launch your app in Eclipse using a run configuration with the options Android project, USB target, and Launch Default Activity, the app opens with a black screen. (6556867)

Close the app and restart it from the Navigator.

In a BlackBerry Nature-enabled project, the context menu is missing some of the project-related options. (6110730)

None.

When an Android application is deployed for the first time from the BlackBerry Plug-in for Eclipse, the application may take up to 60 seconds to deploy. In some cases it will fail to deploy. (6047053)

You can increase the default Android Runtime launch timeout value or deploy your application with the Command line Tools. Once the Android application has run once, the BlackBerry Plug-in for Eclipse will deploy and run.

When a Target password prompt is cancelled in the Android Development Tools signing page, there is a blank error. (5841959)

Save the password first.