Doc change: updating lib links

Bug # 7038255

Change-Id: I702aeaed5fcbf7a9cb46b2ccd0e7baff53e48dab
app launch test fixes and improvements

* fixed NPE when specified app name does not exist
* force stop package before starting, because some names may
  resolve into the same package
* ensure app is launched in the order as sepcified in command
  line
* fixed time recording: it should have been 'thisTime' as
  reported by ActivityManager, to be consistent with previous
  harness

Change-Id: I411a568580feef21821dcbe6ec15884f697af6fd
Doc change: remove old version of gcm javadoc and misc files.

Change-Id: Icbc0345e04432af97fb859be8787741b7e979c1b
docs: update reference links and misc revisions

Change-Id: Id198d04a4feaf9a3bdee82f1093edabed1c561d2
docs: add javadocs for gcm

Change-Id: I6c4c0990f1a9eec51cc2bf0fd857607b90ac184e
docs: add sdk manager launch info for eclipse

Change-Id: I91f23456fd57afa3cf55cba6ed63d746fb94f2fd
docs: update location/maps doc with info for maps api

Change-Id: I793f47791883efe88ff0d6c8effe0787d9654a88
Show alarm tile for the current user.

We were already refreshing the tile on user switch, but we
were only pulling the information (and observing changes)
for the owner.

Bug: 7596329
Change-Id: I33959af405bc79037b5b1321631d993bea65772f
Import translations. DO NOT MERGE

Change-Id: I3ebc7310e109d45facea00213daacf9d10e22285
Auto-generated-cl: translation import
docs: update dashboard for 12/1, plus misc fixes

Change-Id: I7f06b6c66476aee2bd69b8017b5707c483b252b7
BT is still on after enable flight mode, and reboot the DUT

bug 7275625
Change-Id: I4f8952a06152eb5f5775c1f616f6383e4f20e352
docs: refresh gms and gcm javadocs

Change-Id: I5532eb9f87e2ab87488884e70102e8b4cbadf255
docs: udpate for google service landing page and capitalize GPS in titles

Change-Id: I8cff9c5bc6eee7a60bc5db88763ad57eb63c7e7d
Fix remote views cache to avoid lockscreen widget crosstalk

Bug: 7660973

RemoteViewsAdapter will now store the userId as part of the cache key
when caching remote views to optimize for orientation changes.

Change-Id: I7c4e52b3995d4f56ebfa35aa9516327e182ad892
Fix issue #7649590: Background windows sometimes not being hidden for secondary users

There are two things going on here:

(1) In secondary users, some times theme information such as whether
the window is full screen opaque was not being retrieved, so the window
manager didn't know that it could hide the windows behind the app.
This would just be a performance problem, except that:

(2) There appear to be a number of applications that declare that they
are full screen opaque, when in fact they are not.  Instead they are
using window surfaces with an alpha channel, and setting some pixels
in their window to a non-opaque alpha level.  This will allow you to
see whatever is behind the app.  If the system happens to completely
remove the windows behind the app, and somebody is filling the frame
buffer with black, then you will see what the app intends -- those
parts of its UI blended with black.  If one of those cases doesn't
hold (and though we have never guaranteed they would, in practice this
is generally what happens), then you will see something else.

At any rate, if nothing else than for performance reasons, we need to
fix issue #1.

It turns out what is happening here is that the AttributeCache used
by the activity manager and window manager to retreive theme and other
information about applications has not yet been updated for multi-user.

One of the things we retrieve from this is the theme information telling
the window manager whether an application's window should be treated
as full screen opaque, allowing it to hide any windows behind it.  In
the current implementation, the AttributeCache always retrieves this
information about the application as the primary user (user 0).

So, if you have an application that is installed on a secondary user but
not installed on the primary user, when the AttributeCache tries to retrieve
the requested information for it, then from the perspective of the primary user
it considers the application not installed, and is not able to retrieve that
info.

The change here makes AttributeCache multi-user aware, keeping all of its
data separately per-user, and requiring that callers now provide the user
they want to retrieve information for.  Activity manager and window manager
are updated to be able to pass in the user when needed.  This required some
fiddling of the window manager to have that information available -- in
particular it needs to be associated with the AppWindowToken.

Change-Id: I4b50b4b3a41bab9d4689e61f3584778e451343c8
docs: revisions to GPS Setup page w/ note about emulator

Change-Id: I19400813a0220892654e38fa5142d9f8526a639c
Fix ring volume issue by addressing focus regression in keyguard.

This fixes a regression where ring volume can be changed in keyguard.
Because KeyguardHostView is now being re-created in onScreenTurnedOff(),
it loses focus and the volume keys get handled by the fallback handler.

The fix is to ensure at least one child under KeyguardHostView has focus
whenever we re-create it.

Fixes bug 7546960

Change-Id: I34b7db402401a824f463d35d7546c05dc2979243

Conflicts:
	policy/src/com/android/internal/policy/impl/keyguard/KeyguardHostView.java