Skip to content


Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Commits on Apr 13, 2013
  1. @kruton @Whitehawkx

    Correct executable bit for source files

    kruton authored Whitehawkx committed
    Many media files and source code files were marked as executable in Git.
    Remove those.
    Also a shell script and python script were not marked as executable.
    Change-Id: Ieb51bafb46c895a21d2e83696f5a901ba752b2c5
    Signed-off-by: Chirayu Desai <>
Commits on Mar 27, 2013
  1. FM Radio: Add support for FM Radio in Android

    Anurag Gupta authored Gerrit Code Review committed
    Creating interface and framework for using FM Radio
    RX and TX from different vendors.
    Signed-off-by: Christian Bejram <>
    Change-Id: I1a71aed01bfffdddfabf1cdfbfa3707cb1ed016b
    Signed-off-by: ChampionSwimmer <>
Commits on Feb 15, 2013
  1. @KhasMek

    Merge tag 'android-4.2.2_r1' into HEAD

    KhasMek authored
    Android 4.2.2 release 1
    Change-Id: I51bd81ff324c692d8c3e463b032270f53fc691f1
Commits on Feb 8, 2013
  1. @robertly

    am e60b602: Merge "makefile changes for gcm javadocs" into jb-mr1-dev

    robertly authored Android Git Automerger committed
    # Via Android (Google) Code Review (1) and Robert Ly (1)
    * commit 'e60b6023ae4fdea932d0effc553dddc38117d235':
      makefile changes for gcm javadocs
Commits on Feb 7, 2013
  1. @robertly

    makefile changes for gcm javadocs

    robertly authored
    Change-Id: I5653eb710f13f0a097cb1cf447469c4da7342fe2
Commits on Feb 1, 2013
  1. @ddougherty

    am 2aa47b3: Merge "Doc change: remove htmlified samples from docs bui…

    ddougherty authored Android Git Automerger committed
    …ld for now. Samples are still downloadable thorugh SDK Manager." into jb-mr1-dev
    # Via Android (Google) Code Review (1) and Dirk Dougherty (1)
    * commit '2aa47b336227a5d2bd1ee91f8fb4bd84be7e97f0':
      Doc change: remove htmlified samples from docs build for now. Samples are still downloadable thorugh SDK Manager.
  2. @scottamain

    am 4b7161c: docs: switch devsite doc build to use templates-sdk

    scottamain authored Android Git Automerger committed
    # Via Scott Main
    * commit '4b7161cbd44f64537d2c661e87868ea2689dd126':
      docs: switch devsite doc build to use templates-sdk
  3. @scottamain

    am e75cd4b: docs: add hdf bool for deviste, used to change aspects of…

    scottamain authored Android Git Automerger committed
    … the templates
    # Via Scott Main
    * commit 'e75cd4bfd176fbb1483ec5e17edfbd993adce40f':
      docs: add hdf bool for deviste, used to change aspects of the templates
  4. @ddougherty

    am 7b32d32: Merge "Add build rule for ds (devsite) online docs." into…

    ddougherty authored Android Git Automerger committed
    … jb-mr1-dev
    # Via Android (Google) Code Review (1) and Dirk Dougherty (1)
    * commit '7b32d32bd38b423dd141e7ead89205b9b7929497':
      Add build rule for ds (devsite) online docs.
Commits on Jan 29, 2013
  1. @ddougherty

    Merge "Doc change: remove htmlified samples from docs build for now. …

    ddougherty authored Android (Google) Code Review committed
    …Samples are still downloadable thorugh SDK Manager." into jb-mr1-dev
  2. @ddougherty

    Doc change: remove htmlified samples from docs build for now. Samples…

    ddougherty authored
    … are still downloadable thorugh SDK Manager.
    Change-Id: I9cfa53e605f476daf6cf914f256df600e1d77f89
  3. @scottamain

    docs: switch devsite doc build to use templates-sdk

    scottamain authored
    Change-Id: I933cbafa0712de47b4bcf72d2a7c4f99bf18f930
  4. @scottamain

    docs: add hdf bool for deviste, used to change aspects of the templates

    scottamain authored
    Change-Id: I6ad24252f10211a88d1f98e356bc9da97442f91c
Commits on Jan 28, 2013
  1. @ddougherty

    Add build rule for ds (devsite) online docs.

    ddougherty authored
    Change-Id: I4f1d099995402613f58401a506ba272abfb563ba
Commits on Dec 10, 2012
  1. @KhasMek

    Fix space/tab confusion.

    KhasMek authored
    Change-Id: Ib90fcc6573fefc178592d8bb16377c18501498b5
Commits on Nov 29, 2012
  1. Remove unused IExtendedNetworkService

    Makoto Onuki authored
    It was used in the cupcake era for docomo.  Is not used anymore.
    Bug 7633569
    Change-Id: I2ec826fc9a70d261a340957a937ed4c9f8e67c5c
Commits on Nov 22, 2012
  1. @xoomdev

    Commit themes to AOKP:

    xoomdev authored
    Squashed commit of the following:
    maniac103: Allow theming of framework UI elements - a528877173
    rmcc: SimUnlockScreen: Explicitly register themeChange receiver - 8da5dd0a5
    rmcc: Fix theming of the Shutdown Thread - 0d6dea4e2f
    rmcc: Merge branch 'themes-4.1.1' into cm10 - 5a35f209e
    Change-Id: I16fff820fcf74394ce2884106887f8e284ffe235
Commits on Sep 28, 2012
  1. @scottamain

    add api level 17 to javadoc filter and update version number

    scottamain authored
    Change-Id: I278f796b3390e57f4309f215e4f37359a80f0e83
Commits on Sep 16, 2012
  1. More multi-user stuff.

    Dianne Hackborn authored
    - New public APIs to find out when a user goes to the foreground,
      background, and is first initializing.
    - New activity manager callback to be involved in the user switch
      process, allowing other services to let it know when it is safe
      to stop freezing the screen.
    - Wallpaper service now implements this to handle its user switch,
      telling the activity manager when it is done.  (Currently this is
      only handling the old wallpaper going away, we need a little more
      work to correctly wait for the new wallpaper to get added.)
    - Lock screen now implements the callback to do its user switch.  It
      also now locks itself when this happens, instead of relying on
      some other entity making sure it is locked.
    - Pre-boot broadcasts now go to all users.
    - WallpaperManager now has an API to find out if a named wallpaper is
      in use by any users.
    Change-Id: I27877aef1d82126c0a1428c3d1861619ee5f8653
Commits on Sep 7, 2012
  1. Screen magnification - feature - framework.

    Svetoslav Ganov authored
    This change is the initial check in of the screen magnification
    feature. This feature enables magnification of the screen via
    global gestures (assuming it has been enabled from settings)
    to allow a low vision user to efficiently use an Android device.
    Interaction model:
    1. Triple tap toggles permanent screen magnification which is magnifying
       the area around the location of the triple tap. One can think of the
       location of the triple tap as the center of the magnified viewport.
       For example, a triple tap when not magnified would magnify the screen
       and leave it in a magnified state. A triple tapping when magnified would
       clear magnification and leave the screen in a not magnified state.
    2. Triple tap and hold would magnify the screen if not magnified and enable
       viewport dragging mode until the finger goes up. One can think of this
       mode as a way to move the magnified viewport since the area around the
       moving finger will be magnified to fit the screen. For example, if the
       screen was not magnified and the user triple taps and holds the screen
       would magnify and the viewport will follow the user's finger. When the
       finger goes up the screen will clear zoom out. If the same user interaction
       is performed when the screen is magnified, the viewport movement will
       be the same but when the finger goes up the screen will stay magnified.
       In other words, the initial magnified state is sticky.
    3. Pinching with any number of additional fingers when viewport dragging
       is enabled, i.e. the user triple tapped and holds, would adjust the
       magnification scale which will become the current default magnification
       scale. The next time the user magnifies the same magnification scale
       would be used.
    4. When in a permanent magnified state the user can use two or more fingers
       to pan the viewport. Note that in this mode the content is panned as
       opposed to the viewport dragging mode in which the viewport is moved.
    5. When in a permanent magnified state the user can use three or more
       fingers to change the magnification scale which will become the current
       default magnification scale. The next time the user magnifies the same
       magnification scale would be used.
    6. The magnification scale will be persisted in settings and in the cloud.
    Note: Since two fingers are used to pan the content in a permanently magnified
       state no other two finger gestures in touch exploration or applications
       will work unless the uses zooms out to normal state where all gestures
       works as expected. This is an intentional tradeoff to allow efficient
       panning since in a permanently magnified state this would be the dominant
       action to be performed.
    1. The window manager exposes APIs for setting accessibility transformation
       which is a scale and offsets for X and Y axis. The window manager queries
       the window policy for which windows will not be magnified. For example,
       the IME windows and the navigation bar are not magnified including windows
       that are attached to them.
    2. The accessibility features such a screen magnification and touch
       exploration are now impemented as a sequence of transformations on the
       event stream. The accessibility manager service may request each
       of these features or both. The behavior of the features is not changed
       based on the fact that another one is enabled.
    3. The screen magnifier keeps a viewport of the content that is magnified
       which is surrounded by a glow in a magnified state. Interactions outside
       of the viewport are delegated directly to the application without
       interpretation. For example, a triple tap on the letter 'a' of the IME
       would type three letters instead of toggling magnified state. The viewport
       is updated on screen rotation and on window transitions. For example,
       when the IME pops up the viewport shrinks.
    4. The glow around the viewport is implemented as a special type of window
       that does not take input focus, cannot be touched, is laid out in the
       screen coordiates with width and height matching these of the screen.
       When the magnified region changes the root view of the window draws the
       hightlight but the size of the window does not change - unless a rotation
       happens. All changes in the viewport size or showing or hiding it are
    5. The viewport is encapsulated in a class that knows how to show,
       hide, and resize the viewport - potentially animating that.
       This class uses the new animation framework for animations.
    6. The magnification is handled by a magnification controller that
       keeps track of the current trnasformation to be applied to the screen
       content and the desired such. If these two are not the same it is
       responsibility of the magnification controller to reconcile them by
       potentially animating the transition from one to the other.
    7. A dipslay content observer wathces for winodw transitions, screen
       rotations, and when a rectange on the screen has been reqeusted. This
       class is responsible for handling interesting state changes such
       as changing the viewport bounds on IME pop up or screen rotation,
       panning the content to make a requested rectangle visible on the
       screen, etc.
    8. To implement viewport updates the window manger was updated with APIs
       to watch for window transitions and when a rectangle has been requested
       on the screen. These APIs are protected by a signature level permission.
       Also a parcelable and poolable window info class has been added with
       APIs for getting the window info given the window token. This enables
       getting some useful information about a window. There APIs are also
       signature protected.
    Change-Id: Iec93da8bf6376beebbd4f5167ab7723dc7d9bd00
Commits on Aug 30, 2012
  1. Merge "Start implementing concept of "running" users." into jb-mr1-dev

    Dianne Hackborn authored Android (Google) Code Review committed
Commits on Aug 29, 2012
  1. Add initial multi-display support.

    Jeff Brown authored
    Split the DisplayManager into two parts.  One part is bound
    to a Context and takes care of Display compatibility and
    caching Display objects on behalf of the Context.  The other
    part is global and takes care of communicating with the
    DisplayManagerService, handling callbacks, and caching
    DisplayInfo objects on behalf of the process.
    Implemented support for enumerating Displays and getting
    callbacks when displays are added, removed or changed.
    Elaborated the roles of DisplayManagerService, DisplayAdapter,
    and DisplayDevice.  We now support having multiple display
    adapters registered, each of which can register multiple display
    devices and configure them dynamically.
    Added an OverlayDisplayAdapter which is used to simulate
    secondary displays by means of overlay windows.  Different
    configurations of overlays can be selected using a new
    setting in the Developer Settings panel.  The overlays can
    be repositioned and resized by the user for convenience.
    At the moment, all displays are mirrors of display 0 and
    no display transformations are applied.  This will be improved
    in future patches.
    Refactored the way that the window manager creates its threads.
    The OverlayDisplayAdapter needs to be able to use hardware
    acceleration so it must share the same UI thread as the Keyguard
    and window manager policy.  We now handle this explicitly as
    part of starting up the system server.  This puts us in a
    better position to consider how we might want to share (or not
    share) Loopers among components.
    Overlay displays are disabled when in safe mode or in only-core
    mode to reduce the number of dependencies started in these modes.
    Change-Id: Ic2a661d5448dde01b095ab150697cb6791d69bb5
Commits on Aug 28, 2012
  1. Start implementing concept of "running" users.

    Dianne Hackborn authored
    The activity manager now keeps track of which users are running.
    Initially, only user 0 is running.
    When you switch to another user, that user is started so it is
    running.  It is only at this point that BOOT_COMPLETED is sent
    for that user and it is allowed to execute anything.
    You can stop any user except user 0, which brings it back to the
    same state as when you first boot the device.  This is also used
    to be able to more cleaning delete a user, by first stopping it
    before removing its data.
    There is a new broadcast ACTION_USER_STOPPED sent when a user is
    stopped; system services need to handle this like they currently
    handle ACTION_PACKAGE_RESTARTED when individual packages are
    Change-Id: I89adbd7cbaf4a0bb72ea201385f93477f40a4119
Commits on Aug 22, 2012
  1. Remove obsolete variables.

    Ying Wang authored
    Bug: 6987838
    Now emma is only enabled for apks.
    Change-Id: Id8d198467076a8dff705195a8e051f3fb00d5660
Commits on Aug 12, 2012
  1. User Manager service to manage users and query user details

    Amith Yamasani authored
    Moved a bunch of methods from PackageManager to UserManager.
    Fix launching of activities from recents to correct user.
    Guest creation APIs
    Change-Id: I0733405e6eb2829675665e225c759d6baa2b708f
Commits on Aug 10, 2012
  1. Location overhaul, major commit.

    Nick Pelly authored
    Themes: Fused Location, Geofencing, LocationRequest.
    API changes
    o Fused location is always returned when asking for location by Criteria.
    o Fused location is never returned as a LocationProvider object, nor returned
      as a provider String. This wouldn't make sense because the current API
      design assumes that LocationProvider's have fixed properties (accuracy, power
    o The fused location engine will tune itself based on the criteria passed
      by applications.
    o Deprecate LocationProvider. Apps should use fused location (via Criteria
      class), instead of enumerating through LocationProvider objects. It is
      also over-engineered: designed for a world with a plethora of location
      providers that never materialized.
    o The Criteria class is also over-engineered, with many methods that aren't
      currently used, but for now we won't deprecate them since they may have
      value in the future. It is now used to tune the fused location engine.
    o Deprecate getBestProvider() and getProvider().
    o Add getLastKnownLocation(Criteria), so we can return last known
      fused locations.
    o Apps with only ACCESS_COARSE_LOCATION _can_ now use the GPS, but the location
      they receive will be fudged to a 1km radius. They can also use NETWORK
      and fused locatoins, which are fudged in the same way if necessary.
    o Totally deprecate Criteria, in favor of LocationRequest.
      Criteria was designed to map QOS to a location provider. What we
      really need is to map QOS to _locations_.
      The death knell was the conflicting ACCURACY_ constants on
      Criteria, with values 1, 2, 3, 1, 2. Yes not a typo.
    o Totally deprecate LocationProvider.
    o Deprecate test/mock provider support. They require a named provider,
      which is a concept we are moving away from. We do not yet have a
      replacement, but I think its ok to deprecate since you also
      need to have 'allow mock locations' checked in developer settings.
      They will continue to work.
    o Deprecate event codes associated with provider status. The fused
      provider is _always_ available.
    o Introduce Geofence data object to provide an easier path fowards
      for polygons etc.
    Implementation changes
    o Fused implementation: incoming (GPS and NLP) location fixes are given
      a weight, that exponentially decays with respect to age and accuracy.
      The half-life of age is ~60 seconds, and the half-life of accuracy is
      ~20 meters. The fixes are weighted and combined to output a fused
    o Move Fused Location impl into
    o Refactor Fused Location behind the IProvider AIDL interface. This allow us
      to distribute newer versions of Fused Location in a new APK, at run-time.
    o Introduce, to refactor code used for run-time upgrades of
      Fused Location, and the NLP.
    o Fused Location is by default run in the system server (but can be moved to
      any process or pacakge, even at run-time).
    o Plumb the Criteria requirements through to the Fused Location provider via
      ILocation.sendExtraCommand(). I re-used this interface to avoid modifying the
      ILocation interface, which would have broken run-time upgradability of the
    o Switch the geofence manager to using fused location.
    o Clean up 'adb shell dumpsys location' output.
    o Introduce config_locationProviderPackageNames and
      config_overlay_locationProviderPackageNames to configure the default
      and overlay package names for Geocoder, NLP and FLP.
    o Lots of misc cleanup.
    o Improve location fudging. Apply random vector then quantize.
    o Hide internal POJO's from clients of
      (NLP and FLP). Introduce wrappers ProviderRequestUnbundled and
    o Introduce ProviderProperties to collapse all the provider accuracy/
      bearing/altitude/power plumbing (that is deprecated anyway).
    o DELETE lots of code: DummyLocationProvider,
    o Rename the (internal) LocationProvider to LocationProviderBase.
    o Plumb pid, uid and packageName throughout
      LocationManagerService#Receiver to support future features.
    TODO: The FLP and Geofencer have a lot of room to be more intelligent
    TODO: Documentation
    TODO: test test test
    Change-Id: Iacefd2f176ed40ce1e23b090a164792aa8819c55
Commits on Jul 26, 2012
  1. Add display manager skeleton.

    Jeff Brown authored
    The purpose of this change is to remove direct reliance on
    SurfaceFlinger for describing the size and characteristics of
    This patch also starts to make a distinction between logical displays
    and physical display devices.  Currently, the window manager owns
    the concept of a logical display whereas the new display
    manager owns the concept of a physical display device.
    Change-Id: I7e0761f83f033be6c06fd1041280c21500bcabc0
Commits on Jul 17, 2012
  1. Non persistent adapter service

    fredc authored Android (Google) Code Review committed
    Change-Id: Ib13d5c77416e58161df0e04d7a15ec0dddbde8b5
  2. Initial Health Profile implementation

    Matthew Xie authored Android (Google) Code Review committed
    Change-Id: I22f35073ceb131d84df6b233d1b63d20fa1b4451
  3. Initial implementation of HID, add IBluetoothInputDevice idl

    Matthew Xie authored Android (Google) Code Review committed
    Change-Id: Iadc79a425b4b6e12329d86dd2ac0782adcb0174d
  4. Framework changes for HFP and A2DP profile implementation of the new …

    Matthew Xie authored Android (Google) Code Review committed
    Add IBluetoothHeadsetPhone.aidl for a small service in Phone to get
    phone state changes
    Change-Id: I1015e4a69720c4e9cd18ae4236ccd0dbff2e1b2c
Commits on Jul 16, 2012
  1. Removing a workaround for incorrect window position on window move.

    Svetoslav Ganov authored
    1. The window manager was not notifying a window when the latter
       has been moved. This was causing incorrect coordinates of the
       nodes reported to accessibility services. To workaround that
       we have carried the correct window location when making a
       call from the accessibility layer into a window. Now the
       window manager notifies the window when it is moved and the
       workaround is no longer needed. This change takes it out.
    2. The left and right in the attach info were not updated properly
       after a report that the window has moved.
    3. The accessibility manager service was calling directly methods
       on the window manager service without going through the interface
       of the latter. This leads to unnecessary coupling and in the
       long rung increases system complexity and reduces maintability.
    Change-Id: Iacb734b1bf337a47fad02c827ece45bb2f53a79d
Commits on Jul 11, 2012
  1. Create telephony-common and mms-common

    Wink Saville authored
    These have been created to reduce the size and complexity
    of frameworks/base.
    mms-common was created by moving all of
    telephony-common was created by moving some of
    Change-Id: If6cb3c6ff952767fc10210f923dc0e4b343cd4ad
Commits on Jun 22, 2012
  1. @scottamain

    update make file with 'since' tag for api level 16, update version nu…

    scottamain authored
    Change-Id: I30d04dcde5cd505959d94c274634018b3602cb26
Commits on Jun 20, 2012
  1. Remote volume handling in MediaRouter

    Jean-Michel Trivi authored
    Extend MediaRouter.UserRouteInfo to enable setting playback
     information, which includes volume. When the user route instance
     has a RemoteControlClient, forward any playback information to it.
     Enable specifying a callback to be notified of volume events
     on the route.
    Extend MediaRouter.RouteInfo to enable retrieving playback
    Update RemoteControlClient javadoc to reflect which parts of the
     API are not intended to be made public.
    Change-Id: I59d728eb61747af6c8c89d53f0faeb07940594c3
Something went wrong with that request. Please try again.