naoya_t@android RSSフィード

 Android入門記兼備忘録 since 2009.6.9



21:29 | SDKを1.5r3にアップデート - naoya_t@android を含むブックマーク はてなブックマーク - SDKを1.5r3にアップデート - naoya_t@android


Android 1.5 SDK, Release 3

Android 1.5 システムイメージのアップデート版を提供。パーミッションの修正(後述)とか、新アプリとして日本語テキスト入力IMEとか。あと、前回のSDKにも含まれていたデベロッパツール一式も提供(バグ修正と新機能をいくつか含む)


The latest version of the Android platform, deployable to Android-powered devices, includes fixes to the permissions-checking in certain areas of the framework. Specifically, the Android system now properly checks and enforces several existing permissions where it did not do so in the previous release. Because of these changes in enforcement, you are strongly encouraged to test your application against the new Android 1.5 system image included in this SDK, to ensure that it functions normally.

In particular, if your application uses any of the system areas listed below, you should add the required permissions to the application's manifest and then test the areas of your code that depend on the permission-protected services. Even if you believe your application does not use the permissions-protected services, you should compile and test your application under the latest platform version to ensure that users will not encounter problems when using your application.

The changes to permissions are as follows:

  • When an application requests access to device camera (through android.hardware.camera), the CAMERA permission check is now properly enforced.
  • When an application requests access to device audio capture (through android.media.MediaRecorder), the RECORD_AUDIO permission check is now properly enforced.

For more information, see the issue described in the oCert advisory below:


  • The SDK includes a new version of the Google APIs add-on. The add-on provides an updated com.google.android.maps external library that fixes compile errors related to certain classes such as GeoPoint. For information about the Google APIs add-on and the library it provides, see:


  • The SDK add-on architecture now lets device manufacturers specify a USB Vendor ID in their add-ons.
  • The android tool provides a new command that scans SDK add-ons for their USB Vendor IDs and makes them available to adb (OS X and Linux versions of the SDK only). The command is android update adb. On Windows versions of the SDK, a custom USB driver is included that supports the "Google" and "HTC" Vendor IDs, which allow adb to recognize G1 and HTC Magic devices. For other devices, contact the device manufacturer to obtain a USB driver, especially if you have an SDK add-on that defines a new USB Vendor ID.
  • The telephony, sensor, and geo fix issues in the emulator are now fixed.
  • When you use adb to uninstall an upgraded application, the Android system now properly restores any permissions that had already been granted to the previous (downgrade) version of the application


$ android update adb
$ adb kill-server
$ adb start-server

AdiAdi2013/01/26 22:40Android ½ ¾ ½ ¾ ³ ½ ¾ ¹ ² ¾ ¼ ¼ ¾ gsensor ½ ¾ ¾ ½ ½ , ¾ ¾ ¼ ¾ ½ ² ¾ ² ¾ ¾ , ¾ ¾ ² ¾ ½ ² ² ½ ½ ¾ ¾ ¾ ¼ ¾ ½ ¾ ³ ¾ ¹ ² , ¾ ² ³ ¾ ¾ ¾ ¾ ½ ¾ ½ 2,5 ¼ ¼ ¼ ½ ½ ¾ ² 3,5, ¾ ½ ¾ ½ ¾ ² , ¾ ² ½ ¼ ¾ ¾ SD- ² ¾ ¹ ² ¾ ¾ ¹ ... ² ½ ³ SmartQ v5 ³ ¾ ¼ ½ ¾ ½ 50 ¾ ¾ ² ¾ , ½ ¾ ³ ¾ ³ ¾ ¾ , ¾ ¾ ¼ ¾ ¾ ½ ½ ¾ Linux Win CE ¾ ½ 1080p ³ ¾ ² ¾ ¾

AlexandrAlexandr2013/01/29 18:540I'll be unlocking it when I have a need to, which will come evnlutaley. I like to run stock for at least awhile to get a feel for how things were intended and to make sure there aren't any issues with the hardware before I start doing things that could void the warranty.On my OG Droid I started getting the bug to use custom ROMs as my phone started to fill up and its little 256MB needed some crapware removed to make room for stuff I actually cared about. Cyanogen FTW!That should be less of an issue with a Nexus (very happy to finally see one on my carrier), but it is still important to me to know that I'll have the custom ROM option later when support from the manufacturer starts to dry up and in case even Google evnlutaley leaves this hardware behind.The wait for a Galaxy Nexus was excruciating and frustrating; the Razor was an awesome phone that I'd have very likely upgraded to instead, but the locked bootloader made it taboo in my book. I'm always going to be waiting for a phone that has custom ROM options down the road.

tbxtyqlcotbxtyqlco2013/01/31 08:16ACI8Hd , [url=http://yrsiexlybnsa.com/]yrsiexlybnsa[/url], [link=http://dvmwahmxyulx.com/]dvmwahmxyulx[/link], http://flntxjdnfhbg.com/

xrauabxxrauabx2013/02/02 01:43Jw5tRA , [url=http://mpbabsvprfoc.com/]mpbabsvprfoc[/url], [link=http://qovpxbsadgis.com/]qovpxbsadgis[/link], http://zitdixmszhde.com/

トラックバック - http://android.g.hatena.ne.jp/n4_t/20090719