| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
This will allow the user to select wether or not to use the
rotation settings for the lockscreen. This is dependent
upon the rotation setting being checked.
Signed-off-by: Michael Bestas <mikeioannina@gmail.com>
Change-Id: If45c13a395e0d71b7c4cdcf484a6b8cef964ee37
JIRA: CYAN-339
|
|\ |
|
| |
| |
| |
| |
| | |
Change-Id: Ie0a9eae16e8bf2ea6033a9e5e4e2c149ab4859cc
JIRA:CYAN-1531
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Tile configuration has some unusual coding, like having a
public static Map (QuickSettingsUtil.TILES) to hold all
tile information.
That map is modified directly during the execution of
QuickSettings.onCreate(), which removes unavailable tiles
from this global map. Once those tiles are removed, they
are gone for good (until the runtime decides that it must
reinitialize QuickSettingsUtil.TILES).
This patch tweaks this process a bit:
- The global TILES variable is now immutable.
- There is a distiction from disabling and removing a tile
- Removed tiles are those related to the device
capabilities, and can never be enabled, once removed.
- Disabled tiles are those related to the device state,
like the ProfileTile, which is unavailable if the user
has disabled the profile feature. Disabled tiles can
be re-enabled later.
- All code that actually removes/disables tiles is now at
QuickSettingsUtil. The results of such operations are
reflected on the TILES immutable view.
- It is possible to enable tiles that have been disabled.
This changes improve [citation needed] coding style a bit,
but, furthermore, allows one to disable and reenable tiles
when needed be. For instance, enabling Profiles or Expanded
Desktop will cause the corresponding tile to be available
for selection immediately. That would not possible to
accomplish, once those tiles were removed from the available
TILES map.
Patch set 2: Rebased
Patch set 3: Rebase, refactor
Patch set 4: Check network tile availability at every resume
Patch set 5: Sort tiles at the adapter, revoke caveats
Patch set 6: Some cleanup
Change-Id: Ifd46d81a49b0ce036e9ccd6d13b6e2251ecbf42a
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change allows to trigger a rescan of a volume with the next restrictions:
- Internal volumes if they are emulates
- Primary volumes
- Non-Removable volumes
Requires http://review.cyanogenmod.org/#/c/44585/
Change-Id: I42aebc9fc0d3530cf0a3efb4d2139b688707d43d
JIRA: CYAN-1391
Issue: https://jira.cyanogenmod.org/browse/CYAN-1391
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit changes the following
- do not show apps signed with the plaform certificate at all
(like settings, systemUI, android system etc)
IMO the user should trust the android signed apps to be save and this will
prevent weird behaviours user can get when they activate it on this packages
all other system apps (like calculator, browser) and all which are not signed with
android key are not effected.
- to go inline with AOSP disable the checkbox in detail app screen
for built in apps
cheers
SlimRoms
Change-Id: I12b5522f6e58047173778381fb7290bb1c71bab3
|
|/
|
|
|
|
|
| |
Current method of disabling camera does so for entire system, not just
lockscreen. This patchset addresses that.
Change-Id: Iba357214df36ddd8afd49a3e39abcaaba4ec808e
|
|
|
|
| |
Change-Id: I023ee587669103aa4d2a819af700ce3daa53695d
|
|
|
|
|
|
|
| |
Every time we set ourselves as the active admin, the previous states are reset.
Hence set both camera/widget states each time one of them is changed.
Change-Id: I678a8155a04ef3822b49bcfb997a248ea99c128c
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
As per https://jira.cyanogenmod.org/browse/CYAN-1243
this commit allows user to control visibility of widgets/camera on lockscreen.
Change-Id: Idab2ff4f058e355a1e5936531d9a264b1fea16a1
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Due that on the one hand a lot user are not familiar
with permissions and how to read them and on the
other user want to have a faster easy access to
setup privacy guard for several apps this small
manager assist the user to setup.
Privacy Guard Manager shows a list off all installed apps
Per default it shows only user apps which have critical
permissions privacy guard can protect.
The user can optional show in the list as well all system apps
or turn off the filter to show all apps undependent of the
permission the app has. To activate privacy guard for an
app a simple click on the entry activates it so that the user
can go fast trough the list. Longpress opens app detail page.
Initial help dialog tells the user how to use it.
Due the filter user who are unfimiliar with permissions can
fast see which apps are effected without deeper knowledge
cheers
SlimRoms
PatchSet3:
- go inline with AOSP style
- move PrivacyGuard by default into manager
- change behaviour off active icons
PatchSet4:
- change app icon size to 36dip
PatchSet5:
- string change
PatchSet6:
- add reset option to disable privacy guard for
all shown apps in the list
PatchSet7:
- Cleaned up the intro dialog a bit.
PatchSet8+9:
- cleanup
- fix alignment of top checkbox
PatchSet10:
- fix permission filter
PatchSet11:
- improve icon loading
Change-Id: I6bc886393bf90f8daed92b66d5fee1ce9e1accd0
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I736df60139f1b977838c16136c0c30198633fcb2
|
|/
|
|
|
| |
Change-Id: I7dfbb64334e0e8e7f98d38bf503c053ff1880658
JIRA:CYAN-1550
|
|
|
|
| |
Change-Id: I2766f4c89460c967e32349be008e38b3600b7e76
|
|
|
|
|
|
|
| |
I noticed that the option could remain ticked but not actually enabled
if the alert box is cancelled.
Change-Id: If9a4e88641a5e4283d6ea16c17ca4461841580e3
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Only show option when network type is GSM not CDMA
Change-Id: Ib225366c63ae928f23afd5bbe8b5f68818a4976b
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I8de198c6144e1b0194ebeaffffec084035492635
|
| |/
|/|
| |
| |
| |
| |
| | |
* Don't try to update the privacy guard flag while refreshing after an
uninstall since the PM will throw an exception at us.
Change-Id: Idadb99fefc2861e871f6206b08c844dda742fa68
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I88ab9fa0cb7791c5f9d859ab6531346f2aa55193
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
* Add toggle to InstalledAppDetails to enable/disable privacy guard flag on
a per-application basis.
* Add toggle to enable privacy guard by default for applications.
Change-Id: If03aa5319c520b6c4a78887f0f46ef1443ddaa83
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Renamed WifiTriggerFragment to TriggersFragment as it is used by
multiple trigger types
Made AbstractTriggerPreference used by multiple trigger types
Renamed some strings to make more sense
Make sure the configured triggers are shown even if type is disabled.
E.g. when Wi-Fi is disable listing AccessPoints does not work for
triggers, already configured triggers will still be shown.
Change-Id: Ife78269586aa2ab7fa94d3462582e259f9228ab2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A helper class used in LockPatternView.onSaveInstanceState() and
.onRestoreInstanceState() wasn't set, causing to NPE settings once
a configuration change would happen while displaying lock pattern
input.
This is now set on creation.
Test case:
1) Enable rotation on device.
2) Open Settings/ChooseLockPattern preference.
3) Rotate device
Change-Id: Ic8091bc92dee2a9a23f4ddebd6de4111ec8ac318
|
|\ |
|
| |
| |
| |
| | |
Change-Id: I7dac8ffa0b10abb5ff235750e90a96d801b2f919
|
| |
| |
| |
| |
| |
| | |
Add UI for configuring triggers to active profiles.
Change-Id: I4903ef64d3eced687136a7dcf4d2048ce4b7ca63
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Follow the bug fix addressed in http://review.cyanogenmod.org/#/c/43544/
This fix the issue both Home key wake and Volume rocker wake preferences will be displayed
if either of them activated in device config.
If both of them are not activated it looks fine because eventually Wakeup category
itself removed,though.
Change-Id: I28b7b45d209c3beb9559ed9e7b89612bf8df8bab
|
|
|
|
|
|
|
| |
To activate, enable bool config_show_homeWake in
device overlay/packages/apps/Settings/res/values
Change-Id: I00afe89ba5bf36d74b93a40b9d15eef2e805611f
|
|
|
|
|
|
|
|
|
| |
patch 1: fix blank space
patch 2: remove FR translation and change NegativeButton string
patch 3: improve the NegativeButton (thank you, David)
patch 4: remove create()
Change-Id: I3361d4160a7e1c4eaee094f08c7d212f71e9e0e7
|
|
|
|
|
|
|
|
| |
Tablets have orientations for portrait reversed, this commit addresses it.
Add in a few more orientation-aware safety checks to circumvent certain devices
whose default orientation does not match their device type.
Change-Id: Idc627e687ca61ab29f08433664bf77148424bd6d
|
|
|
|
|
|
|
| |
Parts were brought over from CM9 but not all of it. This completes
the port.
Change-Id: I5ebfab22e68ea34e3babfaacd9c8103e25932d3d
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Applications with the same name didn't show up in the
notification light add-app-dialog (with Facebook's "Messenager"
and Google's "Messenager" being the prominent example here).
This happend due to the fact that the list of applications
was sorted by names only and inserts with collisions were
dropped.
This commit refactor notification light settings to use packages
instead of application semantics. Further the list of packages
is now ordered by human readable name followed by package name,
which avoids the collision.
Additionally we handle situtations gracefully where a package
has more than one launcher activity (Again for example,
Google's "Messenger" and "Google+" is in the same package).
Bonus: potential race condition in the list adapter was
fixed, concurrent semantics were emphasized, unused imports
removed.
Change-Id: I87ad32f535ca866883df337432d1b0cecc9485a8
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Allow user to override nfc state via profiles
Change-Id: I2a401f17ce42b1711588242e0604997e1f5d8399
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This is the Settings application part of the
user settable activation sensitivity patch for pie controls.
For the complete message look at the commit in
frameworks/base.
Patch Set #3:
* Enabled "Very High"
* Changed title from "Sensitivity" to "Responsiveness"
* Display summary
Patch Set #4:
* "Very High" -> "Very high"
Change-Id: I99fbbc94c75b64121fd04ff5deb8f5a10a04a63b
|
|\ \ \ \
| |_|_|/
|/| | | |
|
| |/ /
| | |
| | |
| | | |
Change-Id: Icf62db26735f9ab7ad63e750a1824eb7823c3d70
|
|\ \ \
| |/ /
|/| | |
|
| |/
| |
| |
| |
| |
| |
| | |
Besides the cleanup, make sure to wait a bit between retries if upload fails for whatever reason.
JIRA:CYAN-1187
Change-Id: Ifca8364721007aadef31b328d22d764ef7cb3b0a
|
|/
|
|
|
|
|
| |
Freeze current orientation during edit mode.
Jira : https://jira.cyanogenmod.org/browse/CYAN-1117
Change-Id: I61a852855b70011291a242f3068f67336ba61131
|
|
|
|
|
|
|
| |
Uses the new system UI visibility flag to show the navbar in expanded
desktop mode.
Change-Id: Ia515b3c5a73d0741c3aad5421c9ac46d9876c177
|
|
|
|
|
| |
To keep things consistent, stats should be reported through
stats.cyanogenmod.org, not stats.cyanogenmod.com.
|
|
|
|
|
|
|
|
| |
Make layout more inline with framework.
Scale appropriately on larger devices.
Adjust columns according to orientation/device type
Change-Id: I20872a42344936b0643a7eff0007c50aaaa5fdd6
|