Lines Matching full:now
37 <li>IntentReceivers are now known as BroadcastReceivers (but still operate on Intents.)
74 <li>Network access now requires that applications obtain a permission in their AndroidManifest.xml files.
143 <li>Normal Java resources (non Java files placed in package folders) are now properly packaged in the final package, and can be accessed through normal java API such as ClassLoader.getResourceAsStream()</li>
144 <li>Launch configuration now has an option to wipe emulator data on launch. This always asks for confirmation.</li>
145 <li>Launch configuration now has an option to disable the boot animation. This will let the emulator start faster on older computers.</li>
146 <li>Installation of application is now more robust and will notify of installation failure. Also installation is blocking, removing issues where ADT tried to launch the activity before the app was installed.</li>
153 <li><span>External jar libraries are now directly supported by build.xml, just drop them in the libs directory.</li>
159 <li>The console port number of a given emulator instance is now displayed in its window's title bar.</li>
195 <li>New sample: the source code for the now-obsolete Home screen from M5 is included as an example of how to construct a Home screen replacement.
223 <li>For performance and maintainability reasons, some APIs were moved into separate modules that must be explicitly included in the application via a directive in AndroidManifest.xml. Notable APIs that fall into this category are the MapView, and the java.awt.* classes, which each now reside in separate modules that must be imported. Developers who overlook this requirement will see ClassNotFoundExceptions that seem spurious.
225 <li>Developers who use 'adb push' to install applications must now use 'adb install', since the full package manager is now implemented. 'adb push' will no longer work to install .apk files.
238 <li>More of the standard Android user applications are now included, such as the Music and Messaging applications.
246 <li>It's now much easier to add media content to the SD card and have the ContentProvider locate and expose it to other applications.
260 <li>Android now supports modules or libraries that can be optionally linked into applications; a good example is the MapView, which has been moved into such a library. However, Android 1.0 will not support the ability for third-party developers to create such libraries for sharing with other applications.
295 <li>The Android emulator now support SD card images up to 128 GB in size. The previous limit was 2 GB.</li>
305 <li>ADT now attempts to connect a debugger to any application that shows up
324 <li>AIDL files that import and reuse types is now supported by activityCreator.py and ADT.</li>
329 <li>The <a href="{@docRoot}guide/developing/tools/traceview.html">traceview</a> tool is now included in the SDK.</li>
371 <li>Now supports multiple emulators on one host computer. Please note that you need to use the <code>-data</code> option when starting secondary emulators, to allow those instances to save their data across sessions. Also, DDMS does not yet support debugging on multiple emulators yet. </li>
378 <li>Now retries to launch the app on the emulator if it fails due to timing issues when the emulator is booting.</li>
379 <li>Adds support for loading custom skins from the <SDK>/lib/images/skins/ directory. The Skin dropdown in the Emulator tab is now built from the content of the skins/ directory in order to support developer-made skins.</li>
382 <li>Eclipse console now warns if an .apk that is pushed to the device declares the same package as another already installed package.</li>
383 <li>Java classes generated by the Eclipse plugin are now marked as derived automatically, so that Team plugins do not consider them as regular source.</li>
388 <li>Now provides support for emulating inbound SMS messages. The ADT plugin and DDMS provide integrated access to
402 <p><code>adb -version</code> now returns a version number.</p>
409 <p>ADT plugin now uses a custom java editor for R.java/Manifest.java, to make those files non-editable. This is to replace the current locking mechanism which causes issues on Mac OS (preventing projects from being deleted). Note that your project must recompile at least once for the lock to be removed from the files.</p>
411 <h4>The following known issues noted in m3-rc20 are now fixed:</h4>
438 <p>The New Android Project wizard provided by ADT 0.3.1 now properly displays error messages when used with Eclipse 3.2 on Windows.</p>
441 <p>The <code>AndroidManifest.xml</code> files generated by ADT 0.3.1 now include the XML element required for displaying the associated app in the "Applications" menu. If you have applications created with ADT 0.3.0, simply ensure that your <code>AndroidManifest.xml</code> file contains the following highlighted line:</p>
452 <p>ADT 0.3.1 is now compatible with Eclipse 3.4.</p>
