Age | Commit message (Collapse) | Author |
|
Bug:23905002
Signed-off-by: Adam Lesinski <adamlesinski@google.com>
(cherry picked from commit 552a8a5d8df32f659b8d11311a244cdc6d3b7733)
Change-Id: I9b7ea859889b7697bee4165a2746602212120543
|
|
The uninitialized local variables pick up
whatever the memory content was there on stack.
This data gets sent to the remote process in
case of a failed transaction, which is a security
issue. Fixed.
(Partial manual merge of master change
12ba0f57d028a9c8f4eb3afddc326b70677d1e0c. Rest
to automerge from klp-dev)
For b/23696300
Change-Id: I704c9fab327b3545c58e8a9a96ac542eb7469c2a
|
|
If the custom sensor requires the BODY SENSOR permission, we should add
the body sensors app op for the custom sensor
Bug: 23396558
Change-Id: I132917d1bca12c76c8a9fb146e00951cba3e6d7a
|
|
Bug: 23604253
Change-Id: I480cf0a46c286badc6fd95a3b42e6cb1ed056b1b
|
|
|
|
(cherry pick from commit e3c4df96083231b519dad919fd0ed6624100b368)
- For those that are proud to call themselves logspam police
- Every time someone declares that something is too chatty, or that
they lost their logs because they were declared too chatty and
their associated logs were aggresively pruned we generally
ask them to report the logger statistics to pinpoint what software
product that is the elephant in the room.
- Every time we want to spawn a new 'stop being so spammy' bug spawned
off a bugreport collected for another purpose, we *wish* we had the
logger statistics to help add gravitas to the claim that some piece
of software is the top, or near the top, polluter.
Bug: 22351810
Change-Id: Ifae33cd21d0ae2917a3b4381502d723725b1701c
|
|
|
|
Bug: 22059484
Change-Id: I587eb7622555194f18f403da583e3b70656a530e
|
|
|
|
|
|
|
|
Previously the parsing found the next space and then added the the difference
between the current position and space to the set of tokens. This improperly
generated empty strings if there were consecutive spaces or if spaces existed at
the beginning or end of strings. To fix this, the parse is modified to use
simple stringstream parsing.
Bug: 22709246
Change-Id: I9e32c07bbf984eadccdadf1dc34437fa0c46088b
|
|
Allows the sideband layer to be passed all the way to HWC instead of
getting blocked by the updated PTS tracking code.
Bug: 22291067
Change-Id: Ic2f20a7528e276fff054e86ca35789c26873b348
|
|
This reverts commit 869eb2089ec8a6286b944bfcff57e4cbe0c7e207.
Change-Id: I4fb865e3b18bbb011fa4e4b4732336930c3a45ae
|
|
|
|
This reverts commit 869eb2089ec8a6286b944bfcff57e4cbe0c7e207.
Change-Id: I4fb865e3b18bbb011fa4e4b4732336930c3a45ae
|
|
|
|
|
|
If SensorService hasn't started when SensorManager instance is requested, keep retrying for a
longer duration.
Bug: 22529981
Change-Id: I4ba6b760608e34d79273aeb39568f0fa72fbaf9d
|
|
|
|
|
|
Fixes bug 22674557
Change-Id: I2ced132c1cb4f4b5166f9af288dd3e697fdcf92b
|
|
|
|
adding AOSP fusion sensors." into mnc-dev
|
|
|
|
fusion sensors.
Bug: 22502485
Change-Id: I3d9018649302b98004e4e216b2173e8411a08501
|
|
mnc-dev
|
|
Bug: 22512621
Change-Id: I2100b8aad0a1cf110936f4a765718ba97f3d8ce7
|
|
restorecon_data already iterates across all found users internally,
so we don't need to call it for each UID moved. In fact, this was a
bug that caused data for the owner to be relabeled when moving apps
back to internal storage.
Bug: 21813384
Change-Id: I5ba76d4f30d129365864c8a25b665f344b99a6b4
|
|
|
|
Bug: 22552826
Change-Id: I9bdfeb8c68f403301af90d4b494f0ae7166a767c
|
|
Add dalvik.vm.dex2oat-swap system property to override a default
decision.
Bug: 20658562
Change-Id: I34368c6e435d1a9ceec20a0bf1c8c6213e527f5e
|
|
|
|
|
|
|
|
|
|
Bug: 19264992
Change-Id: If48e0953b972c9d69f516906adf7c6faf67e3eb8
|
|
Bug: 22076400
Change-Id: I62129549b0681f200f40da01f53140245309ed88
|
|
|
|
|
|
Bug: 19264992
Change-Id: Idbe964a1a35c190a32f845e2a19542d54652d011
|
|
|
|
|
|
App movement now has three distinct stages: copying, scanning, and
cleanup. Previously, a battery pull late in the move process would
end up with packages.xml pointing at the old location which had been
torn down. Now, we update packages.xml to point at the new location
as the "source of truth" before we start deleting the old location.
Bug: 21831336
Change-Id: I62b8916c673265c240e2574ea968cdce5a7a0074
|
|
|
|
Some of this logic already existed, but when we optimized
SurfaceFlinger to avoid unnecessary wake-ups, we didn't carry the logic
over into the new readiness test. shouldPresentNow now returns true if
the timestamp is more than a second in the future (since it's likely a
bogus timestamp and should be ignored).
Bug: 21932760
Change-Id: Ib50970a4eb621588c0b60766c8d8d1a8bddf853b
|
|
|
|
dc3d6af9: am bb686c25: Disregard alleged binder entities beyond parcel bounds
* commit '990c54485f361d587d09952e60ab5fb608d161dd':
Disregard alleged binder entities beyond parcel bounds
|
|
bb686c25: Disregard alleged binder entities beyond parcel bounds
* commit '35851e2abbfe8f1d9c4cc7dc13a6e6e155b61664':
Disregard alleged binder entities beyond parcel bounds
|
|
alleged binder entities beyond parcel bounds
* commit '38ff2b44ad7a64768cd1bb8793ec6c45e8d1e68e':
Disregard alleged binder entities beyond parcel bounds
|