GitLab

Change-Id: I0326914821f68d789cb26767518ead1292d87db0

Change-Id: I17944c557970ed35e1bc67f6f3e3372ff88651ad

Merge "Avoid stripping empty screens if the workspace is still loading (issue 12523285)" into ub-now-lunchbox

Deal with WallpaperManager.getBuiltInDrawable() returning null.

Bug: 13109487
Change-Id: Ib5665a0eb947e9784cdcd0e8dfab1a01b4deca82

-> This appears to be what may be causing data loss in some users during update.
   A certain (seemingly) rare combination of life-cycle events and package events
   seems to be the culprit (potentially why it's seen at update time).

Change-Id: Iea4f8aef012ba80b7ba568e0df264edb9284efbe

Bug: 13219313
Change-Id: I4961c6724a1550dbae126f97e45dc166cbe9a565

Bug: 13153542
Change-Id: I4312ebd200e8e652ef841f54301981c2a486b726

This reverts commit f3a8e8c0.

Bug: 12978354
Change-Id: I11f1eeaab4fad9a2e4acf835144f0b0dc6fac54b

Merge "Updating Read/Write settings permission protectionLevels. (Bug 11372484)" into ub-now-lunchbox

Bug: 12953091
Change-Id: Idc640532e2c2c6143d49d330bd541682eca64ac5

Change-Id: I2b7248218fe16856a9721b8b9169700977f19d00
Auto-generated-cl: translation import

-> Also removed the db-created as a criteria for showing the clings
   (this was a bit problematic in some cases and going forward)
-> Instead, we use database upgrade as a signal to not show the clings.
   This is used instead of the above criteria (to prevent old users from
   seeing the migration cling and losing their data.)
-> Stripped some old code related to custom clings that's no longer used.

Change-Id: Ib5e5285e5ddbc60e69eb998ee9fd092ae879150d

am 9594e887: (-s ours) am 37fe7d2b: (-s ours) am f42cf7de: (-s ours) Import translations. DO NOT MERGE

* commit '9594e887':
  Import translations. DO NOT MERGE

* commit '37fe7d2b':
  Import translations. DO NOT MERGE

* commit 'f42cf7de':
  Import translations. DO NOT MERGE

Change-Id: I4fb41af97a881f6669af15ddd6db1af4f3429765
Auto-generated-cl: translation import

Bug: 10778992
Change-Id: Ie430a6587d49dc0d78b87b81582c0cef7c281017

Bug: 11578157
Change-Id: I116cef5f30e9028348cd028eaf46038d9d79bdd3

Bug: 8912132
Change-Id: Id81889a133e56461df2e20599c4b40020818ba18

* commit '57251be2':
  Import translations. DO NOT MERGE

The workspacescreens table is updated in LauncherModel.updateWorkspaceScreenOrder
and that the operation to remove all screens, then reinsert the new list of
screens in not inside a single transaction, so if the app is updating or
crashes between ContentResolver.delete and ContentResolver.bulkInsert then
the data will be lost. This CL makes it all happen inside 1 transaction.

Bug: 12523285
Change-Id: I409dbc9f48fa9c8bd4bf3b1453204a4daac1689a

Change-Id: Icb76bf81b4253215543f7e384efac9eb23e0c432
Auto-generated-cl: translation import

Change-Id: Icfe6248a812a2aa103c830a9fabe22de9ff228bb
Auto-generated-cl: translation import

When dropping from all apps, accept drop was returning true if the item
was above a folder, however, when it came time to complete the drop,
the folder wouldn't accept the item. This can be prevented by increasing
the criteria in acceptDrop.

Change-Id: Ib644ec45984e8366c33bb674f3d3a76e22ed5160

Bug: 10778992
Change-Id: I3293d8bab8ae0ef49fc5554531bba5bd6f70932c

am 6033ceb4: Ensure we don\'t call getLayoutDirection() for devices not running JB MR1+. (Bug 12906355)

* commit '6033ceb4':
  Ensure we don't call getLayoutDirection() for devices not running JB MR1+. (Bug 12906355)

Change-Id: I06b7bc7f7f0e01696cb9670b8385e5148593e3e0

Change-Id: I25115b9529c21d3079f50bc26bad8f846a6fcd3e

Newer nanoproto compiler discourages the use of this.

Change-Id: Ic27a6d15f2892bb49df3100147c086a2bce20fd4

Bug: 12524591
Change-Id: I2bc0c4d206214d994c9a9e1bd13b42f2e53dba9f