| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This is no longer used.
Change-Id: Ifd8eaa1d9d1f156dbfa4fdf278f95213ee32271e
|
|
|
|
|
| |
Issue-id: YAM-145
Change-Id: I06394c4fcfca5978b50a4186935ac6bda7b94b16
|
|\
| |
| |
| |
| |
| |
| |
| | |
https://android.googlesource.com/platform/frameworks/base into cm-13.0
Android 6.0.1 release 22
Change-Id: I0d31899b234156a91accb61e0a7fb3d8d16d5062
|
| |
| |
| |
| |
| | |
Bug: 25900899
Change-Id: I420a7c590d72ba10f3e466d15dccfdbb520e810a
|
| |
| |
| |
| |
| |
| | |
Issue-id: YAM-140
Change-Id: I3c296c645281509b7860e54d4e32790881d30ed6
(cherry picked from commit 3c1279528e3a6017ff42f2d7aa436be88c9022fa)
|
| |
| |
| |
| |
| |
| | |
This reverts commit faf68427a20c930acf5e2a1fda892eeeb21de43a.
Change-Id: Ia26899db93d22975147a29b99ff43b0ea0696d68
|
| |
| |
| |
| | |
Change-Id: I327696a8cfb2a25ed7ef6adf65d36981253e2866
|
| |
| |
| |
| | |
Change-Id: I9e2c1efdfabc0ffa0e9cf44cee31781f15e8894a
|
|\ \
| | |
| | |
| | |
| | |
| | | |
git://codeaurora.org/platform/frameworks/base into cm-13.0
Change-Id: I008f052e4e27b44457c8343d20f6e1ba943c8e1f
|
| |/
| |
| |
| |
| |
| |
| |
| | |
1. Add an item into default configuration so that user can overlay it
2. Enable captive portal detection by default
CRs-Fixed: 822072
Change-Id: I10c58a58c5b79dd2d7ea081a71f3752dd9928868
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Lights with Screen On
* LEDs Brightness
* Multiple LEDs
Change-Id: Ife49a2f8077e9361f56990fb4b0b49e1c44bdd5e
Signed-off-by: AdrianDC <radian.dc@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This moves all Settings.Global.* settings, that were added to
CyanogenMod and not used in boot classpath, to CMSettings.
* WAKE_WHEN_PLUGGED_OR_UNPLUGGED
* BLUETOOTH_A2DP_SRC_PRIORITY_PREFIX
* POWER_NOTIFICATIONS_ENABLED
* POWER_NOTIFICATIONS_VIBRATE
* POWER_NOTIFICATIONS_RINGTONE
* ZEN_DISABLE_DUCKING_DURING_MEDIA_PLAYBACK
* WIFI_AUTO_PRIORITIES_CONFIGURATION
Change-Id: I5a23971b278d150c633d2b4ade49a143c4423c26
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This moves all Settings.Secure.* settings that, were added to
CyanogenMod, to CMSettings.
* KEYBOARD_BRIGHTNESS
* BUTTON_BRIGHTNESS
* BUTTON_BACKLIGHT_TIMEOUT
* DEV_FORCE_SHOW_NAVBAR
* ADB_NOTIFY
* ADB_PORT
* DEVICE_HOSTNAME
* KILL_APP_LONGPRESS_BACK
* PROTECTED_COMPONENTS
* LIVE_DISPLAY_COLOR_MATRIX
* ADVANCED_REBOOT
* POWER_MENU_ACTIONS
* DEFAULT_THEME_COMPONENTS
* THEME_PREV_BOOT_API_LEVEL
Change-Id: I49e9160177ffc727b20008817ac2b5ce5e89ead5
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Implement the support of a multiple LEDs settings.
The setting is deactivated by default
and will be ignored by the unimplemented phones.
Current LibLights will simply not use the new variable.
Changes includes :
frameworks/base
hardware/libhardware
packages/Apps/Settings
Change-Id: Ie8712c13e43f823996f10ca83b4a9f95fb750e96
Signed-off-by: AdrianDC <radian.dc@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Implement the support of an overall brightness control for the LEDs.
The setting is deactivated by default
and will be ignored by the unimplemented phones.
Current LibLights will simply not use the new variable.
Changes includes :
frameworks/base
packages/Apps/Settings
Change-Id: I1c0de01b1c6a2a2cf1432028a2e69f90b2373b2c
Signed-off-by: AdrianDC <radian.dc@gmail.com>
|
| |
| |
| |
| |
| | |
Change-Id: Icd5e47051554a7b2464e4fbdaac868aafda7b853
(cherry picked from commit 6bfea6065178a29d4622a89e2944c16e086923b1)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Ports "protected SMS" from CM11:
* Add API for protected SMS receive broadcasts.
Change-Id: I5dfeb94832eefac9607070e9fb29db589bac7a57
* SettingsProvider: fix load protected sms setting logic
Change-Id: I7d03821c5f5ac5d24445e5c03f7911c3a81c16dd
Change-Id: Ifd31eb9558e397bf92f4cdb87f9e2056bc71d22f
|
| |
| |
| |
| |
| |
| |
| |
| | |
Add a default entry for Settings.Global.SEND_ACTION_APP_ERROR so that it
can be overlayed elsewhere if needed.
Change-Id: Ieffc2f4a1ad8ad0df04a9e33b575150a680478af
Signed-off-by: Roman Birg <roman@cyngn.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Original commit info:
[1/2] Power connect/disconnect notification support
part 1/2: frameworks/base PowerUI and Settings
http://review.cyanogenmod.org/#/c/35241/
part 2/2: packages/apps/Settings Sound settings
http://review.cyanogenmod.org/#/c/35242/
V-Old_Change-Id: I36a6b9f924d2cd52191a8e83a744745b37c5b068
OldChange-Id: Ib865e1c296cb8e1d957b2a48616c88ceaba5c008
Change-Id: I5db20ef23bdb644e2af06e8dcbc8fbd0cf7ce321
Signed-off-by: STELIX <ssspinni@gmail.com>
|
| |
| |
| |
| |
| |
| | |
* Port from CM11
Change-Id: Id9d0954acffd00bdb470b9eccbdb3b45fbd995c1
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds the framework support for enabling the Navigation bar
on devices with hardware keys. It is toggled from Settings, and
depends on device-specific support for the KeyDisabler hardware
control
Change-Id: I88fecb2ca1e8613591c327a93f53909b00239cd8
wm: Nullify hardkey function assignments if enabling the navbar
This caused erroneous (and sometimes duplicate) events being generated
due to the regular key function assignments. The navbar does its
own action management, so don't try to derive from the actions
usually present in hard keys.
Change-Id: I82866e24547f8145cac4f07820ae90aacce09281
Update DEV_FORCE_SHOW_NAVBAR constant.
Change-Id: Ie5b4317162c514d22276956f81007e064a3d0f32
Settings: Move DEV_FORCE_SHOW_NAVBAR load to loadSecureSettings.
Change-Id: I6ac53b8c9f7fce6f9ca6b4ad7bf31a1c1e896863
|
|
|
|
|
| |
Bug: 22756856
Change-Id: If97e0faead995fb95893a128c1890b61bbe86ce5
|
|
|
|
|
| |
Bug: 16875464
Change-Id: Ic1ad910dd38acbc68ef040b2acdf3696ec2c2e4e
|
|
|
|
|
| |
Bug: 17684570
Change-Id: I64a9c9c0620049cdfcca0150648fa201281f7178
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Added a new SLEEP_TIMEOUT setting which governs how long the device will
remain awake or dreaming without user activity. By default this
value is set to -1 which maintains today's existing behavior.
We basically represent the time we are allowed to be dreaming as a new
kind of user activity summary state called DREAM, similar to BRIGHT
and DIM. When the sleep timeout expires, the state is cleared and
the dream ends.
Bug: 17665809
Change-Id: I59aa7648dcec215f1285464fc1134934a09230e5
|
|
|
|
|
| |
Bug: 17490408
Change-Id: If1cc25a341eed4e41a7bf170bab077203fa19d15
|
|
|
|
|
|
| |
b/17428259 | Change device name to default to model name
Change-Id: If9f0a30f2362574d32fc69c0880c01ec7a3edb9f
|
|
|
|
|
|
|
|
| |
Add a notification for those users that teaches them how to re-enable
the notifications.
Bug: 15934899
Depends-On: Ie0bcc207c4f331def207e588bbad36b8986fe114
Change-Id: I4a169e268042cfcaa4ad80cdf205904f9c90e76d
|
|
|
|
|
| |
Bug: 16840500
Change-Id: I73fbe5c2cff665ccb637abb9039d57f377d9df53
|
|
|
|
|
| |
Bug: 15331132
Change-Id: Ia80ccb2cfdf60116bd50601e60ff131619eafcc5
|
|
|
|
|
|
|
|
|
|
|
| |
Setting for controlling if guest is enabled on the device.
Setting to hint to apps that they should skip showing first use clings.
User switcher handles creation and deletion of the guest user.
Some tweaks to the user switcher to show some feedback and make the icons
circular.
Change-Id: I187dc381d2ee7c372ec6d35e14aa9ea4dfbe5936
|
|
|
|
|
| |
Bug: 15137158
Change-Id: I171c3269a7a16a00083e16e1cc4c7c1c2b98c05e
|
|
|
|
|
|
|
|
| |
A new global settings to name a device. This will centralize the notion
of device name/nickname and should be used by Cast, Bluetooth, TV Remote and other
advertising applications/services.
Change-Id: I2294deb5c0d1002fb2fc158f62a2d5643d90d749
|
|
|
|
|
| |
Bug: 13208692
Change-Id: I3682ecb30c6997c578b76a578b79a8d13a6e6323
|
|
|
|
| |
Change-Id: I849d4def1dcf220c226349f1591a8ba00b603854
|
|\
| |
| |
| | |
Change-Id: Ib286d5194f68c55cfd2e5c17a5eb89ea32add574
|
| |
| |
| |
| |
| |
| |
| | |
To be able to customize the "WiFi scan always available"
setting we need to set a default value.
Change-Id: I3673f2613ab9b6a947aed7e29d4cc876140c2180
|
|/
|
|
|
|
| |
packages
Change-Id: I2fac06cbe3321d7384278d875c91128bcc15d629
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Battery sounds will always play when the screen is on, and
then for Settings.Global.LOW_BATTERY_SOUND_TIMEOUT
milliseconds after the screen goes off. After that, low
battery alerts will be pushed out the airlock until the
screen comes back on again.
If battery sounds are suppressed via this mechanism you'll
see a log line like:
V/PowerUI ( 3161): screen off too long (5779ms, limit
5000ms): not waking up the user with low battery sound
The default value of LOW_BATTERY_SOUND_TIMEOUT is a settings
provider resource: R.integer.def_low_battery_sound_timeout.
Bug: 10487557
Change-Id: Iddd42038aa630631dc8f1833f20fcc5a0c646681
|
|\
| |
| |
| |
| |
| |
| | |
dock audio"
* commit '53d998368c6c6107c6d18de945f4dfee482e6f91':
Setting the default value for dock audio
|
| |\
| | |
| | |
| | |
| | | |
* commit 'b2d3904b0d0f02b3eddef1d228724b99962cba56':
Setting the default value for dock audio
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There was no default value for parameter "dock_audio_media_enabled"
in global settings and because of that it couldn't be obtained before
Settings app first start and improper actions, such as FORCE_NONE
sending to AudioSystem instead of FORCE_ANALOG_DOCK, were taken.
This patch sets default value to 'true'.
Change-Id: Idbe343519db15f806f3a237e8b39f8420b9edde1
Signed-off-by: Dmytro Dubovyk <dmytro.dubovyk@ti.com>
|
|\ \ \
| |/ /
| | |
| | | |
Change-Id: I51dedcc5ee521e62ad6101c0b09e4f881b8c4bf0
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Only plays a tone if the battery level is below 95% which
is the same heuristic used when determining whether to turn
the screen on.
Use new low battery and wireless charging sounds on Mako.
Bug: 7371658
Change-Id: Ia4527ec398d024ee418a4287e1fcbf0ec83bcc24
|
|/
|
|
|
|
|
|
| |
Optimize for updating mNetworkPreference according to device's networkAttributes
setting from overlay config.xml when connectivityservice start.
Change-Id: I90286332d4f453038f1ddac7dd9d1265d96b4859
Signed-off-by: Jianzheng Zhou <jianzheng.zhou@freescale.com>
|
|
|
|
|
|
|
|
|
| |
So that:
- the values can be shared (to fix assoc bug)
- the values can be customized in product overlays
Bug:7373284
Change-Id: I37f037082523a3d975f6014f36afa28c60117372
|
|
|
|
|
|
|
|
|
| |
Existing primary users were never being marked as complete,
causing things that relied on this (e.g. showing the quick settings panel)
to break.
Bug:7282088
Change-Id: I9c8622f3cd0fb99a44477946d3db22fa2cbbc6fc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add a setting to globally disable Wifi display.
Fixed a bug where the wifi display broadcast receiver
was running on the wrong thread.
Removed the wifi-display QuickSettings dialog, all functionality
has been moved to Settings.
Bug: 7178216
Bug: 7192799
Change-Id: I9796baac8245d664cf28fa147b9ed978d81d8ab9
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change is the initial check in of the screen magnification
feature. This feature enables magnification of the screen via
global gestures (assuming it has been enabled from settings)
to allow a low vision user to efficiently use an Android device.
Interaction model:
1. Triple tap toggles permanent screen magnification which is magnifying
the area around the location of the triple tap. One can think of the
location of the triple tap as the center of the magnified viewport.
For example, a triple tap when not magnified would magnify the screen
and leave it in a magnified state. A triple tapping when magnified would
clear magnification and leave the screen in a not magnified state.
2. Triple tap and hold would magnify the screen if not magnified and enable
viewport dragging mode until the finger goes up. One can think of this
mode as a way to move the magnified viewport since the area around the
moving finger will be magnified to fit the screen. For example, if the
screen was not magnified and the user triple taps and holds the screen
would magnify and the viewport will follow the user's finger. When the
finger goes up the screen will clear zoom out. If the same user interaction
is performed when the screen is magnified, the viewport movement will
be the same but when the finger goes up the screen will stay magnified.
In other words, the initial magnified state is sticky.
3. Pinching with any number of additional fingers when viewport dragging
is enabled, i.e. the user triple tapped and holds, would adjust the
magnification scale which will become the current default magnification
scale. The next time the user magnifies the same magnification scale
would be used.
4. When in a permanent magnified state the user can use two or more fingers
to pan the viewport. Note that in this mode the content is panned as
opposed to the viewport dragging mode in which the viewport is moved.
5. When in a permanent magnified state the user can use three or more
fingers to change the magnification scale which will become the current
default magnification scale. The next time the user magnifies the same
magnification scale would be used.
6. The magnification scale will be persisted in settings and in the cloud.
Note: Since two fingers are used to pan the content in a permanently magnified
state no other two finger gestures in touch exploration or applications
will work unless the uses zooms out to normal state where all gestures
works as expected. This is an intentional tradeoff to allow efficient
panning since in a permanently magnified state this would be the dominant
action to be performed.
Design:
1. The window manager exposes APIs for setting accessibility transformation
which is a scale and offsets for X and Y axis. The window manager queries
the window policy for which windows will not be magnified. For example,
the IME windows and the navigation bar are not magnified including windows
that are attached to them.
2. The accessibility features such a screen magnification and touch
exploration are now impemented as a sequence of transformations on the
event stream. The accessibility manager service may request each
of these features or both. The behavior of the features is not changed
based on the fact that another one is enabled.
3. The screen magnifier keeps a viewport of the content that is magnified
which is surrounded by a glow in a magnified state. Interactions outside
of the viewport are delegated directly to the application without
interpretation. For example, a triple tap on the letter 'a' of the IME
would type three letters instead of toggling magnified state. The viewport
is updated on screen rotation and on window transitions. For example,
when the IME pops up the viewport shrinks.
4. The glow around the viewport is implemented as a special type of window
that does not take input focus, cannot be touched, is laid out in the
screen coordiates with width and height matching these of the screen.
When the magnified region changes the root view of the window draws the
hightlight but the size of the window does not change - unless a rotation
happens. All changes in the viewport size or showing or hiding it are
animated.
5. The viewport is encapsulated in a class that knows how to show,
hide, and resize the viewport - potentially animating that.
This class uses the new animation framework for animations.
6. The magnification is handled by a magnification controller that
keeps track of the current trnasformation to be applied to the screen
content and the desired such. If these two are not the same it is
responsibility of the magnification controller to reconcile them by
potentially animating the transition from one to the other.
7. A dipslay content observer wathces for winodw transitions, screen
rotations, and when a rectange on the screen has been reqeusted. This
class is responsible for handling interesting state changes such
as changing the viewport bounds on IME pop up or screen rotation,
panning the content to make a requested rectangle visible on the
screen, etc.
8. To implement viewport updates the window manger was updated with APIs
to watch for window transitions and when a rectangle has been requested
on the screen. These APIs are protected by a signature level permission.
Also a parcelable and poolable window info class has been added with
APIs for getting the window info given the window token. This enables
getting some useful information about a window. There APIs are also
signature protected.
bug:6795382
Change-Id: Iec93da8bf6376beebbd4f5167ab7723dc7d9bd00
|
|
|
|
|
|
|
|
|
|
| |
Framework changes to store and read a secure setting for package verification.
Default is on/true.
This setting will be turned on/off via the Settings app.
Bug: 7082362
Change-Id: I6f93d3136add8af0dbbdc664f0473c5f5b7e3fee
|