Android m3-rc37a

m3-rc37a
Build of Android 1.x
Am3rc37ahome.png
Architecture
Compiled2007-12-14
Works in

Android m3-rc37a is the third M3 experimental build of Android, released on 14 December 2007.

Changes[edit | edit source]

Emulation[edit | edit source]

  • The emulator skin has been changed from QVGA-L (320x240) to HVGA-P (320x480) by default.

Fixes[edit | edit source]

Emulation[edit | edit source]

  • Fixed an issue which caused the emulator to not support non-QWERTY keyboards.
  • Fixed an issue which caused the emulator to run off-screen in Windows.
  • Fixed an issue which caused the emulator failing to start when using the -useaudio in some environments.
  • Fixed an issue which caused the emulator console listens for connections on non-local ports 5554-5587.
  • Fixed an issue which running multiple emulator consoles on Windows can result in unexpected behaviour when simulating incoming telephone calls.

Terminal[edit | edit source]

  • Fixed an issue which caused adb shell fail to connect when used for the first time.

Bugs and quirks[edit | edit source]

Applications[edit | edit source]

  • In certain circumstances, icons for newly installed applications do not display as expected.

Emulation[edit | edit source]

  • On Mac OS X 10.5, the Eclipse plugin's Run Dialog may sometimes fail to show the option to select the Android Launcher.
  • On Mac OS X 10.4, the emulator may hang if started in the background (i.e. ./emulator &).

Terminal[edit | edit source]

  • adb, and also by starting from the command line, will emit warnings about deprecated API use when first used on Mac OS X 10.5.

SDK[edit | edit source]

  • The dmtracedump and traceview tools are not available in the SDK.
  • Using activityCreator with the --ide intellij option creates IntelliJ scripts with incorrect documentation location specified. To fix this, change the value for the <JAVADOC> element in the generated .ipr file from file://.../docs/framework to file://.../docs/reference.

Browser[edit | edit source]

  • The focus ring shown in the browser may sometimes not properly wrap links.

Maps[edit | edit source]

  • Extremely rapid or prolonged scrolling in MapView or this application will result in application errors.

Phone[edit | edit source]

  • Unanswered incoming calls placed from the emulator console will result in an unfinished call UI if the user presses the call back button.