Winson Chung 9fea3de8f5 Disable Launcher when starting in a managed profile ...

- The launcher package is automatically enabled for work profiles due to
  DPM interpreting it as a critical component since it does not have any
  launchable activities. Once enabled, it is possible for an explicit
  broadcast to update smartspace or assistant state to trigger the process
  to be created for the work profile user, which ends up initializing logic
  which may call into LauncherApps (which is not allowed from the work
  profile).

  As a workaround, we disable the launcher application immediately upon
  detecting that it is running in a work profile.

Bug: 120550382
Change-Id: I72c52fe598d41440a1fb59304b494a000277384b

2019-02-15 15:59:08 -08:00

..

libs

Using the new Touch dispatcher

2019-02-13 16:36:42 -08:00

recents_ui_overrides

Merge "App to home animation zooms into the app icon." into ub-launcher3-master

2019-02-15 02:05:27 +00:00

res

Import translations. DO NOT MERGE

2019-02-02 00:41:03 -08:00

src/com/android

Disable Launcher when starting in a managed profile

2019-02-15 15:59:08 -08:00

tests/src/com/android/quickstep

Quick plug to solve flakiness caused by switching QS on/off

2019-02-11 10:52:31 -08:00

AndroidManifest.xml

Moving autority definition to a separate file, so

2018-11-27 23:20:32 +00:00