Original Change-Id: I21565b82199394622ce4113b42174277c0248998
See first comment for doc stage location.
bug:22069078
bug:23341937
Change-Id: I5fec5599faacdca58e36694809b2e5a8365c7f5b
This is small and straightforward--a summary paragraph didn't clearly
explain the process (which was properly documented further down)--
so I'm going to just go ahead and +2 it myself.
Also fixed a couple of broken anchors while I had it open.
bug: 20719615
Change-Id: I8cc806007168adcd3a674b7b30e7aa397b471cc0
- Added Studio 1.3.2 release notes
- Added Studio 1.3.2 download link information
- Added ADT 23.0.7 release notes (catch up from 8/17)
Change-Id: I930059d9bf85f7063eb3f55e0c77d46a064c75b0
(cherry picked from commit 0b4d170beeaf1ce0826bdd90504d54114c6368fa)
docs: Fixed adb shell commands for setting/getting the inactive state of an app.
bug: 23372372.
Original Change-Id: I4fc846018189761d00111e196e5de9214009e6ad.
Change-Id: Id1d9c45200abec339bbc330ba9988349dcd19473
This change depends on the following change to the script that loads the platform name...
https://googleplex-android-review.git.corp.google.com/#/c/752776/
Change-Id: I7c9962f58d09d7a7f40dc6faa63014385b296498
(cherry picked from commit 3c2dc05e3da3fdf2d19bb8793c12411a46eb8d15)
Original change-Id: 4276a8fb25071aa0e471a5afc0764987db79cc49
Docs incorrectly said the method returns a boolean. In fact,
it (like the framework version) returns an int constant.
See first comment for doc stage location.
bug: 23331110
Change-Id: I2b4ccdc56dc0cff414c4d21e3916e8e7a0b0e909
(cherry picked from commit 4276a8fb25071aa0e471a5afc0764987db79cc49)
Also describe NoteOn more clearly.
Bug: 23303608
Change-Id: I35f88022c854c2eb16ec606e58f28e06c52d18b7
Signed-off-by: Phil Burk <philburk@google.com>
(cherry picked from commit bda0caf07b786633381a029f782b9d2e1caa8a3f)
List of issues from https://code.google.com/p/android/issues that are fixed by this CL: 183476,183249,183248,183241,183222,183142,183093,183329,182385,182311,182193,182019,73149,181589,179740,179384,178322,178189,178086,178020,177169,176312,175138,172322,172030,171820,170647,167288,163574,161580,161041,159199,151347,144290,136137,132505
Change-Id: I2e96f7444048abd2f666c75bd6ab9640019afb75
Bug: 21721463
Training module and related API-reference documentation. This is new
material for Android Wear D(iamond) release.
Change-Id: I9959bca50fd96812abd7cfb693139986bc59b133
To help MediaProvider uniquely identify storage devices, pass through
the UUID of the underlying private storage volume.
Bug: 23329611
Change-Id: I22ee7ea98fcb208d7797310acb3396a3f074f09b
The the android.telecom.Call.Details class provides its own equals
implementation. Recently added in M is to also check if the mExtras
and mIntentExtras are different. Unfortunately, Bundles do not implement
equals. As a result when Telecom calls are parceled and sent to the
InCallServices, this means that the internalUpdate method will always
assume that the Details of a call have changed, even if they have not.
This was causing a LOT of extra calls to onUpdate in the InCall UI (2x the
amount). Although there is still room for improvement in the number of
callbacks from Telecom, this fix prevents a pretty significant regression
on that front.
Bug: 23218195
Change-Id: I128e996faf60376ed3df1dc848a97c4a7b0482ee
Requests without NET_CAPABILITIES_INTERNET and just the default network
capabilities should not be marked restricted. Without this fix apps
can hit permissions exceptions if they inadvertently make requests
without NET_CAPABILITIES_INTERNET.
Bug:23164917
Change-Id: I4c7136821315bcb05dfc42ffbc505a5d4f6109e6
When the unbind request came in before the service was actually
bound, we dropped the unbind request because mPrewarmBound was still
false. Fix that by tracking whether a bind is pending and if a unbind
event comes in during that time, set another flag to unbind it
directly again when the service is actually bound. In addition, don't
allow binding again if any of the previous events are still pending.
Bug: 23143748
Change-Id: I2b8ace86e35479a9848668a3462a2ce687835413
This isn't specific to work profile. When multiple user
deletions happen in sequence, a race causes a dying user
to lose permissions prematurely. This fix delays removal of
user state until the user is completely cleaned up and all the
processes have been killed.
Bug: 23178833
Change-Id: I1636bc2022416359a25f19a3f65d113c05289cd3