This project is mirrored from https://github.com/LineageOS/android_packages_apps_Settings.git. Pull mirroring updated .
  1. 18 Jun, 2020 1 commit
  2. 06 Jun, 2020 1 commit
  3. 20 May, 2020 2 commits
  4. 12 May, 2020 1 commit
  5. 05 May, 2020 1 commit
  6. 29 Mar, 2020 1 commit
  7. 28 Mar, 2020 1 commit
  8. 12 Mar, 2020 1 commit
    • Mill Chen's avatar
      RESTRICT AUTOMERGE · 13cde9e3
      Mill Chen authored
      Allow LockScreenPattern to be launched in the pinning screen
      
      If work profile lock is enabled and work app is pinned, users will get a
      black/white screen on the phone. That's because Settings is prevented
      from other apps launch any pages of Settings in the pinning mode.
      
      In order to launch some pages of Settings from other apps, we add a
      condition to the preventive mechanism and allow the activity inherited
      from SettingsBaseActivity to override the condition to have the activity
      to be launched from other apps in the pinning mode.
      
      Bug: 137015265
      Bug: 135604684
      Test: manual test
      Change-Id: I8070de79a83350d1658efcb19e983669dad0e673
      Merged-In: I8070de79a83350d1658efcb19e983669dad0e673
      (cherry picked from commit 8d472055)
      13cde9e3
  9. 08 Mar, 2020 1 commit
  10. 04 Mar, 2020 1 commit
  11. 11 Feb, 2020 1 commit
  12. 10 Feb, 2020 1 commit
  13. 04 Feb, 2020 1 commit
  14. 21 Jan, 2020 1 commit
  15. 19 Jan, 2020 1 commit
  16. 14 Jan, 2020 1 commit
  17. 25 Dec, 2019 1 commit
  18. 16 Dec, 2019 1 commit
    • Mill Chen's avatar
      Prevent accounts page directly opening in screen pinning mode · 65e18e18
      Mill Chen authored
      In Settings there is no auth mechanism to prevent accounts page being
      opened in screen pinning mode. This CL makes it so that when users are
      trying to navigate to any pages in Settings from other apps in screen
      pinning mode, Settings app will directly close its page.
      
      Bug: 137015265
      Bug: 135604684
      Test: manual
      Change-Id: If26eda408a9ef6fa03ad82e5bee51bb7185950d6
      Merged-In: If26eda408a9ef6fa03ad82e5bee51bb7185950d6
      (cherry picked from commit f3242dab3546c019d4b79c502f7b8850d36123a5)
      (cherry picked from commit ad2502a9)
      65e18e18
  19. 25 Nov, 2019 1 commit
  20. 15 Nov, 2019 2 commits
  21. 12 Nov, 2019 1 commit
  22. 04 Nov, 2019 1 commit
  23. 02 Nov, 2019 2 commits
  24. 01 Nov, 2019 1 commit
  25. 29 Oct, 2019 1 commit
  26. 15 Oct, 2019 2 commits
  27. 07 Sep, 2019 2 commits
  28. 05 Sep, 2019 1 commit
  29. 03 Sep, 2019 1 commit
    • Sam Mortimer's avatar
      Settings: Prevent DataSaverBackend from overwriting uid policies · 3476e978
      Sam Mortimer authored
      * Lineage assigns additional network policy values for restrict on
        data and wlan etc.
      
      * DataSaverBackend was assuming that only allow background
        and allow unrestricted background exist and therefore could both:
        i) overwrite other uid policies and ii) incorrectly think there were
        changes when there weren't.
      
      * Change setUidPolicy to appropriate add/remove sequences and filter
        the newPolicy value in the callback to ignore everything except
        background data related policies.
      
      Change-Id: I4c81d7fa2199441674a4176eb78b29facd0b799e
      3476e978
  30. 27 Aug, 2019 2 commits
  31. 26 Aug, 2019 1 commit
  32. 25 Aug, 2019 1 commit
  33. 20 Aug, 2019 1 commit
  34. 16 Aug, 2019 1 commit