| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Change-Id: I034c246651fc9ae698bc32fd4af16cf14adb5314
|
|
|
|
|
| |
JIRA: CYAN-1703
Change-Id: Ie3c1cf0339d66405d27c06dba07cc80e4001d669
|
|
|
|
| |
Change-Id: I473684a9ec4763c33709d5f59a5403eff63ce97e
|
|
|
|
| |
Change-Id: Icbf706a582279b86d901fb727b58663713606521
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In addition, this commit also fixes a bug where the switch would not be
disabled on a fresh 24-hour clock install, as the preference value would
be null. This is avoided by using a higher-level method from
DateFormat to check the clock mode.
Patch Set 2: improve code styling
Patch Set 3: remove pointless application context retrieval
Change-Id: I80de938df61803649688723843439905e9909b07
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On tablets such as manta a this occurs. To reproduce go into PGM, press
the back button one time, then go back into PGM.
http://pastebin.com/N7XAybUB
Remove privacy guard fragment in onDestroyView
Change-Id: I61cebe273fa6fd514f18c86894acd176701148f6
Check if fragment transaction is empty before attempting to remove it
Change-Id: I08591c89559d33fee30ac2934fdbcc30637147da
PrivacyGuard fragment fix - change from empty check to isDestroyed check
Change-Id: I52fe44b7446cd16793df6ac9cdbe31e2ddd70210
Signed-off-by: Paul Beeler <sparksco@gmail.com>
PrivacyGuardManager: Reduce calls to getFragmentManager
Change-Id: I74f07a58b09cf0e9114d0c1c56e9a97d55ab0900
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 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
|
|
|
|
|
|
|
| |
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: I8de198c6144e1b0194ebeaffffec084035492635
|
|/
|
|
| |
Change-Id: I88ab9fa0cb7791c5f9d859ab6531346f2aa55193
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
Make layout more inline with framework.
Scale appropriately on larger devices.
Adjust columns according to orientation/device type
Change-Id: I20872a42344936b0643a7eff0007c50aaaa5fdd6
|
|
|
|
| |
Change-Id: Ia14fbb200fbc19bcdc654bd542dbe3ba15fbf6ea
|
|
|
|
|
|
| |
This is especially important when rotating the device.
Change-Id: Iaf1ceb46943e9d0a171d6a75d3d446dbec205095
|
|
|
|
|
|
|
| |
- Avoid log spamming
- Add a little margin around the grid so outer control points aren't cut
Change-Id: Idb6cd2773186f9e7011486dc62f21e2fab85e245
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changes a few things:
- Don't imply a 'bucket' type of algorithm is used by showing an ambient
brightness range for each line
- Allow manually entering the screen brightness
- Add a preview window for the cubic spline interpolation
- Add a help text
JIRA:CYAN-612
Change-Id: I64274280872b9fe4f6fdc368d654aca81e0a4e0c
|
|\
| |
| |
| | |
into cm-10.1
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For QuickSettings and Power Widget check if there is
ConnectivityManager.TYPE_MOBILE network avaialbe directly instead of relying
on a checking for the PackageManager.FEATURE_TELEPHONY permission. Some
devices like tilapia (Nexus 7 GSM) has mobile data but does not set the
telephony permission.
Patchset 2:
- Have power widget use the same logic as quicksettings to check for
mobile data
Change-Id: Ibe8059aaa5f3bd1e72e958608a34e89abfd0ad4a
Fixes: CYAN-803
|
|/
|
|
|
|
| |
Removed duplicated codes
Change-Id: Ib7d54dfc33c6a66711799bbdf44212d287221ae9
|
|\
| |
| |
| | |
into cm-10.1
|
| |
| |
| |
| |
| |
| |
| |
| | |
All settings would be disabled on devices with hardware rotation
lock due to dependency setting. Disable dependency to allow setting
swap volume and rotation degrees on those devices.
Change-Id: Iee0532902d59fa80666e17b3853db8e3d7ed5ddc
|
|/
|
|
|
|
|
|
| |
Switch over to using 2 layouts (one generic, one user tile),
just like how aosp does it. This way the tiles look similar to
their SystemUI counter part.
Change-Id: I8640c99602b056fb48b37f516c23c16555a2ba2a
|
|
|
|
| |
Change-Id: I42a7182859bd028c2e93f0c2fe0b6b5dee404cfa
|
|\
| |
| |
| | |
cm-10.1
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This commit separates the ability to configure the Expanded desktop
mode from the ability to enable the switch in the Power menu. This
will allow for the ED Tile to be hidden if the feature is disabled
and the power menu entry to be removed if the user chooses to use the
Tile instead.
Change-Id: I3d2eabde8087d25940cbb1e5262086b9c6e291f1
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add a dinamic tile for devices with dock battery
Requires http://review.cyanogenmod.org/#/c/33999
Patchset 2: Rebased
Change-Id: If6c49a5277899997717f5a3af8ed3ad5bbb30b67
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
|
|/
|
|
|
|
|
|
|
|
|
|
| |
If entering the navbar screen with expanded desktop enabled, the navbar
is not shown hence hindering the ability to use the panel
This patchset addresses that by disabling expanded desktop upon entering,
and re-enabling upon exiting if it was previously enabled.
Patchset 2 : Fix state issues
Change-Id: I2776cf971f8899d30a25c0bf6b418793153555fc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on the commit series for pie controls, this commit
makes the Navigation Bar and Pie Controls share the same
button layout.
This commit applies the changes made in part 1 to the
Settings app. For the real commit see framework/base.
This commit introduces here:
* Some setting constants changes to avoid clashes with PA.
* Removal of the pie search key setting.
Change-Id: I5b4abd6d32a3fc835466ac4cb1f0b9c851641061
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
If the user drag the progress bar below the min value, the incorrect
setting will be saved since seekBar.setProgress code path does not
return to the "getItem(pos).backlight = ..." line.
Change-Id: I4796e22ba9c44315be92de4040f6cd8451bdf153
|
|/
|
|
|
|
|
|
| |
of different packages.
Policies for older packages were being granted to the newly installed package that got the recyled uid.
Change-Id: I6c74cf6762e8da10e09d5cf5d94e9f826e47f24d
|
|
|
|
|
| |
Change-Id: I6cc653db3397074fb1cd9aa12b06511ce2cc3c9d
JIRA:CYAN-731
|
|
|
|
|
|
| |
On those devices, there are only two settings an a checkbox would fit better.
Change-Id: I394736dacf7765f7fdda47d6d743d7479bd4de7e
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Ie0e8994436bce1848f540b50bd15bce77276808d
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
without navbar
On devices without navigation bar, expanded desktop is only useful
for hiding the status bar when the apps don't hide them.
"Status bar visible" setting is a no-op.
Change-Id: I16a31ec6e10c7ed11600e3b1a1d9b631f31af55e
|
|/
|
|
|
|
|
|
|
| |
If expanded desktop is enabled while the option for expanded desktop
setting is disabled, expanded desktop will remain active and the user
will not be able to disable expanded desktop without reenabling the
setting.
Change-Id: Ia91e34e5ce9f8680f64b81e5f79c2df6f0639bb2
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the settings part of the pie commit, for the real implementation
look in frameworks/base.
Patch Set 3:
* CyanogenMod Code Style
Patch Set 4:
* Strings cleanup
* Better integration into CyanogenMod system settings UX
* Some related cleanup in SysteSettings.java
Patch Set 5 and 6:
* Rename feature to Quick controls to match AOSP terminology
Patch Set 7:
* Remove WIP
Patch Set 8:
* Revert name to Pie controls
Patch Set 11:
* Fix broken revert
* Fix spelling of search
Change-Id: I47599316273d8e46017f49ba62a02cc55a785678
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This way those devices that have a special path for
frequency caps can overlay it in the given device's
resources for Settings package.
It's defaulting to the general paths that are used
in most of the kernels.
It's usable for example in endeavoru device tree
where the max cap can only be set through
a different sys path.
Change-Id: Ic3113222580ebe8cc8e43d3dad7a15e041448c53
|