| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
Previously, it was possible for AppWidgetsRestoredReceiver to
start the restore process before work profile has finished restoring which
resulted in the work profile items being removed from the workspace.
Bug: 131315856
Change-Id: I2f295a1ca91f1996522bcc8052aa139979526e3b
|
|
|
|
|
|
|
|
| |
The autority of the provider should be set in secure settings:
launcher3.layout.provider
Bug: 127987071
Change-Id: Iccf2960aa6c0a5a8ff9621b13d8963d9daecb993
|
|
|
|
|
| |
Bug: 118140522
Change-Id: Ic8e47e71f538b0b0caff6f630566665d05a65522
|
|
|
|
|
| |
Bug: 111301511
Change-Id: I40decf4c763401c97afcc2bfa7954a1f3a03f536
|
|
|
|
| |
Change-Id: I0d28069967854357ca755bf25dec19d4979bdecf
|
|
|
|
|
|
|
|
|
|
|
| |
Favorites table is copied as a separate table name during the first grid migration.
On subsequent migrations this backup table is used if it exists, otherwise new
backup is created. The backup table is also removed if there is any insert or
delete operation on the db (outside of the migration operation itself).
Bug: 111850268
Bug: 121048571
Change-Id: I6f02f4a355c369ee99d89430971be258f7516f6e
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Removing a separate table for workspace screens. List of screens are
automatically parsed using the items in the favorites DB. Order of the
screen based on the screen id and rearranging screens is no longer
supported. In case the screens need to be rearranged, all the items
in the favorites db will need to be updated with new screen ids.
This makes backing up the DB (in the same database) easier as only
one table needs to be duplicates.
Change-Id: I8ba947a898f637d780e2f49925e78604263126e8
|
|
|
|
|
|
|
| |
that it can be easily customized using android studio
Change-Id: I17f4f4511c2af5d382727769d1b74413f233d500
Bug: 120079798
|
|
|
|
|
|
|
| |
The UI will only be shown on eng/userdebug platform builds.
Bug: 117223984
Change-Id: I27843f2d856a4a19f3fe53c4d306606eaa5714a2
|
|
|
|
|
|
|
|
| |
> Items ids were already being typecasted to int when being bound on the UI
> Using a consistent type allow better use of platform data-structures
> Adding IntArray and IntSet as a replacement for various Collection classes
Change-Id: Id3c650ed2420c2bfca3bd7671d2b705b56112371
|
|
|
|
|
|
|
|
|
|
| |
This is the first step in adding a flag toggler UI to launcher.
The change migrates a single flag (QSB_ON_FIRST_SCREEN) from a
boolean constant to a boolean method. In future, that will allow
us to return different values at runtime.
Bug: 117223984
Change-Id: I1e62c91dd941b8145166021bc0aa157733e62ea0
|
|
|
|
|
| |
Bug: 72481685
Change-Id: Ib9e52504d9513bd7fdede28f6c0798ca7873083d
|
|
|
|
|
| |
Bug: 70863722
Change-Id: Ib6bb554212da2c5d5d23a51aa0eff52bae97bce1
|
|\ |
|
| |
| |
| |
| |
| |
| | |
FIX: 73876183
Change-Id: I9d15df247eed3500c679cba085c680b75581cffb
|
|/
|
|
|
|
| |
Bug: 72481685
Bug: 73814840
Change-Id: I1e30632647ad08a08d84c49875bc7b6cac3be1fb
|
|
|
|
| |
Change-Id: I796cf758d2a25cf8fd5f9a9b78a7977fd54ca451
|
|
|
|
| |
Change-Id: I6f83d0f77045ba189f02dd465bf70ffc2a239aa1
|
|\
| |
| |
| | |
ub-launcher3-master
|
| |
| |
| |
| | |
Change-Id: I30ad1a1462a97b6bc03f8e386ae3058c7fe022e5
|
| |
| |
| |
| | |
Change-Id: I79ef0aa5d65b933f4b7f0520fc8bac26e366da2d
|
|\ \
| |/
|/|
| | |
Change-Id: I0d03e760f97c6f9984ad0bf9e8f9e8c7a8a8b5c7
|
| |
| |
| |
| |
| |
| | |
67062454
Change-Id: Ic060d3d7dba4fffe688dddf7cd04c48e4baaf813
|
|/
|
|
|
|
|
| |
target Launcher3Go without widgets support
Bug: 62353159
Change-Id: Ia03d2235a9bcf75f9ef191924f81630e63a2c684
|
|
|
|
|
|
|
|
| |
layouts."
This reverts commit c4b296a50ea50de64b377016e07ec041350489c8.
Change-Id: Ieff7873edc3cb300fe454b0ad97d6f0b4f0cb5a9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With the new Folder permutation logic, we change the position of the items
when they are added to a Folder. This means that existing Folders will
now appear in a different order than the user arranged them in.
This change makes sure that when a user upgrades, their existing Folders
will appear untouched.
Note: We decided to priotize restoring the original layout of the Folder,
as opposed to making sure the preview items remain the same. This
is less destructive of users' data (we're changing the window into
the Folder, but not the location of items when the Folder is open).
Bug: 63115141
Bug: 35064148
Change-Id: Ib0a28b4b50be089878ffc3e40bced89832e125bc
|
|
|
|
| |
Change-Id: Ibf48d6015d808f86bc79ccf64e3077eb5b6ccaff
|
|
|
|
|
|
|
|
| |
Adding a schema file for handling DB downgrade. This schema file is part of
the backup/restore set, and hence is available on a device with lower app version.
Bug: 37257575
Change-Id: I69c8ef5f28d5209be6e6679412c7459d4eeda5d0
|
|\
| |
| |
| |
| |
| | |
am: 57266aa2bd
Change-Id: Iab767b7b7c60db60322151cc5c2ab6a65706a553
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
During restore, the data can be in inconsistant state, as the
system is yet to give us the widget map. Deleting the widget during
open would cause the AppWidgetRestoredReceiver to store the widget id
after it has been deleted.
Bug: 37935101
Bug: 38029633
Change-Id: Id3b8766229718239ae784794e848dcfbc74658ac
|
|\|
| |
| |
| |
| |
| |
| |
| | |
app" into ub-launcher3-dorval
am: f436478b02
Change-Id: I0f322aeb37c7ba35b2d2f97b1802f1c657a790b4
|
| |
| |
| |
| |
| |
| |
| | |
> Also enabling add to home-to-homescreen feature based on install reason
Bug: 36588249
Change-Id: Icfc1edd4c31ed7eb50086f8ffb1a7858a9641b41
|
| |
| |
| |
| |
| |
| |
| |
| | |
> Adding SQLiteTransaction to make it easier to manage DB transactions
> Using try-with resource for better resource handling
> Defining utility method for iterating over cursor
Change-Id: I20b1a62d61798342825ecfeb971e1a0c63c9b6d7
|
|\|
| |
| |
| |
| |
| | |
am: f2d8b65775
Change-Id: I1d9b7a5a532bf504aabac69691e3f83e2f181a04
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
> A one-time DB update for removing any existing ghost widgets
> Handling widget cleanup when we bulk delete workspace items during loader
> Simplifying external delete
Bug: 35634653
Change-Id: Id0c520f57aee6d75d9c0e7bcd5786a464bf9f39f
|
|\|
| |
| |
| |
| |
| |
| |
| | |
the table schema > data update: backward compatible changes to the data" into ub-launcher3-dorval
am: d31692c0e7
Change-Id: If9b5e413401ac2b969a591acd81c8e6e1c7c2483
|
| |
| |
| |
| |
| |
| |
| |
| | |
> schema update: changes in the table schema
> data update: backward compatible changes to the data
Bug: 37257575
Change-Id: I856854ff2bffa2701f903a24fdc3baf6641175fd
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
$ adb shell dumpsys activity provider com.android.launcher3/com.android.launcher3.LauncherProvider
To see how the proto is filled: go/launcher-proto-dump
b/31772480
Change-Id: I8e0f1e5e38148a3dfeabd2fc057392193b2625dd
(cherry picked from commit 6aa3729e98502d4cffc40a7e602628b85d558edd)
|
|\|
| |
| |
| |
| |
| | |
am: ca18746163
Change-Id: Ic4c14ad1760930735a881926aac8b45efe0cdba0
|
| |
| |
| |
| |
| |
| |
| |
| | |
> This would allow developers to verify their icon designs on different
device configurations
> This settings is only visible when developer settings is enabled
Change-Id: I7e32abfede001c134f23390734dcd39c93b68b9a
|
|\|
| |
| |
| |
| |
| |
| |
| | |
the profile column" into ub-launcher3-dorval
am: 77ff9a4343
Change-Id: Ib0cd8cb8f963b78a9cd53ed896aeb6e4f6163683
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
profile column
The intent extra is not always correct as the profile id can change during backup restore.
This allows us to use a consistant behavior everywhere.
Change-Id: I004bd244204ca91758b1d42488e1fc13b0ccb998
|
| |
| |
| |
| |
| |
| |
| | |
it is easier to override one or the other
Bug: 36001650
Change-Id: I713f4f5dbcf902614ce9f6c7a73bdace7bdf1ea0
|
|/
|
|
|
|
|
|
|
| |
$ adb shell dumpsys activity provider com.android.launcher3/com.android.launcher3.LauncherProvider
To see how the proto is filled: go/launcher-proto-dump
b/31772480
Change-Id: I8e0f1e5e38148a3dfeabd2fc057392193b2625dd
|
|
|
|
|
|
|
| |
an inconsistant state
Bug: 34720697
Change-Id: I55a26d63be6c06622da6ee3395bf1990f1a58a11
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of maintaining 3 different states, each tied to a subset of data,
maintaing a single state that represents all the data. Individual subset
data is invalidated in rare cases and these invalidates are tightly tied
to the UI. This also allows us to add new data to the model, without worring
about classifying the data into a subset.
Bug: 34112546
Change-Id: Id9cb273de35b79e84a2ef8d6556fcf1e72fb4b75
|
|
|
|
|
| |
Bug: 33032833
Change-Id: I7992a5358142dde80aeaf8c6b7a6c7bfef2c8a00
|
|
|
|
|
|
|
|
| |
> This ensures that LauncherAppState is only accessed in the presence of
a valid context
Bug: 33032833
Change-Id: I955e5cb022f8bd6374681ae6c0720a2666d5b750
|
|
|
|
|
| |
Bug: 33032833
Change-Id: I09baaa6d79187b3096a2ab3a89d7dcaeaf9eee68
|
|
|
|
|
| |
Bug: 32745285
Change-Id: I62971908e3e4402941fab627bbdfd47be64473a3
|