| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
The onUpgrade path was upgrading the database version to 65, but the
current version was marked as 64. That led to the database being
upgraded to 65 and then wiped because it didn't match 64.
This was introduced in HC change 54d068ec6af0ee6d261a135400efe6816c6f5ffe
Bug: 4319406
Change-Id: Ib6efcf34e820948d23d3a2b8ef3afc9012a93c22
|
|
|
|
|
| |
Bug: 4081954
Change-Id: I27266637c6ade0c5c8242792176d1edae0983446
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
bug:3505060
Since we want to have some settings that are used very frequently
by many applications (long-press timeout is one example) these should
be managed efficiently to reduce lookups from different processes
because in the case of a cache miss a disk I/O is performed. Now
the system manages such core settings and propagates them to the
application processes.
Change-Id: Ie793211baf8770f2181ac8ba9d7c2609dfaa32a7
|
|
|
|
|
| |
Change-Id: I50e5a8d8c35c4431f42c7483172447ba0e4e125b
http://b/3461302
|
|
|
|
|
| |
Change-Id: I223ed2a4bd90234ea7e3447f19e18c68beae2763
http://b/3184897
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Modified default volume control logic in AudioService:
1 IN_CALL volume if in video/audio chat
2 NOTIFICATION if notification is playing or was playing less than 5s ago.
3 MUSIC
Modified silent mode:
- now also affect MUSIC stream type
- entering silent mode when VOL- hard key is pressed once while selected
stream volume is already at 0 (except for VOICE_CALL stream).
- exiting silent mode when pressing VOL+ hard key while in silent mode
Play sound FX (audible selections, keyboard clicks) at a fixed volume.
Modified audio framework:
- isStreamActive() method now implemented in AudioPolicyManagerBase (previously AudioFlinger)
- iStreamActive() now specifies a time window during which the stream is considered
active after it actually stopped.
Change-Id: I7e5a0724099450b9fc90825224180ac97322785f
|
|
|
|
|
|
|
|
|
|
|
| |
Enable retrieving the default download manager settings from
a resource, when the SettingsProvider database is created
The default setting for these values is -1, which will cause
DownloadManger to not enforce a limit.
Bug: 3341145
Change-Id: I25294d0f75fb0bdf20d4bef54457056c25c31add
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug: 3365600
This doesn't affect upgrades, only new installs.
Don't backup/restore NOTIFICATIONS_USE_RING_VOLUME anymore as it doesn't
work well across device types and can wedge the device into a state
where you can never hear notification sounds.
Change-Id: I703e1db539eb4ac45b273f46ada0b4bbf3b981bb
|
|
|
|
|
|
| |
access-eng team
Change-Id: I39a303864b94a8a11b6cded9b8bb23041ad91502
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Exception when turning off acessibility and having a WebView showing content.
bug:3341772
1. Now a key in the binding is represented as a long with 32 MSB for modifiers and 32 LSB for keyCode.
bug: 3340732
1. Added check in the WebView key handling code to diable the accessibility injector/injected script in
case accessibility is been disabled after loading the content.
Change-Id: Ic3746dff16ec77ba682a5b139cec0e6afd8fc839
|
|
|
|
|
|
|
|
| |
why is settingsprovider doing getReadbleDatabase() in onCreate() method?
it shoul do getWritableDatabse() so that sqlite's WAL
feature can be enabled on it.
Change-Id: I60e46ce240a6474bbb50ab26fb1d979242b0c9ad
|
|\ |
|
| |
| |
| |
| |
| | |
Bug: 3297046
Change-Id: I92e34a85332988bb3faa1e1997ccc85abf4b5dec
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1. Added a mechanism to select the cursor ring content if accessibility is
enabled - This is achieved by sending an event to the WebCore thread
(if accessibility is enabled) to select the content of the cursor when
the latter moves. Added code in WebViewCore to select the given node
and notify the UI thread for the selection markup which is delivered
of the accessibility injector which manages sending accessibility
events. This is relevant for adding accessibility to WebView if
JavaScript is not enabled. (If JS is enabled we inject a screenreader
written in JS).
2. Fixed the event delegation to the accessibility injector since it
should be able to consume key events of interest and perform some
action which leads to sending appropriate accessibility event.
In the previous implementation it was possible that the injector
consumes the event but the latter was bubbled up.
3. Added function to scroll the selection into view while moving it
around based on user commands.
Note: This is a part of two project commmit.
Change-Id: Ibb81d0468726efbe3bf6e3add1b19c69e3206638
|
|
|
|
|
|
|
|
|
|
| |
Also modified the shortcut key handling so that it drops chorded
Search+X keys when even if no shortcut was found. Without this
change, pressing an unhandled shortcut causes the Search widget to
pop up and the character to be typed.
Bug: 3022227
Change-Id: Ic0921428bd1270604ca28caf1f8493727127f4ed
|
|
|
|
| |
Change-Id: Icf4f1896d13a4b6bf86503b16bde189f1834fdcc
|
|\ |
|
| |
| |
| |
| | |
Bug: 3165933
|
|/
|
|
| |
Change-Id: I37d479c9d6293eb57d68ad686d00838445a18890
|
|
|
|
| |
Change-Id: Ib3d5428073563d564fe45475127eb2cec177ab49
|
|
|
|
| |
Bug: 3165933
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
IWindowManager now supports two new methods,
freezeRotation() and thawRotation(), that allow a caller to
temporarily stash the device's current rotation as the
default rotation (when no other constraints are present).
The system bar uses this to implement a user-accessible
rotation lock by calling freezeRotation() and then turning
off accelerometer-based display rotation; unless overridden
by an app, the display will continue to appear in the frozen
rotation until the rotation is unlocked by the user (either
via the rotation lock icon in the system bar or by checking
"rotate screen automatically" in Settings).
Bug: 2949639
Change-Id: Icd21c169d1053719590e72401f229424b254622f
|
|
|
|
| |
Change-Id: I429632381e862b2ad1e9e22402ef17863458d88f
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
into gingerbread
Merge commit '6c48f228f10c63f83c25fc0c86a5a739266c61a9'
* commit '6c48f228f10c63f83c25fc0c86a5a739266c61a9':
Use the default SecureRandom provider.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Don't be tricky when trying to set the seed for the secure
random number generator. Setting the seed manually eliminates
the internal randomization the SecureRandom class does automatically,
reducing randomness. Just use the default seed, which is designed
to be safe.
Change-Id: I5747c2b3a10cf04e33d2202195951ed5cb82b2fe
|
| |
| |
| |
| |
| |
| | |
correct time.
Have the NITZ provider honor the new setting before updating the time zone.
|
| |
| |
| |
| | |
Change-Id: Ibb139192bae4d60fd53a7872b19c06312bb41558
|
|\ \
| |/
| |
| |
| |
| |
| | |
Merge commit '04bc807057d1c336a5d1340595b790eee4c5b372'
* commit '04bc807057d1c336a5d1340595b790eee4c5b372':
Allow Bluetooth radio to be toggled in Airplane mode.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add "bluetooth" to the list of toggleable radios. Because this string
is in the Settings DB, I had to bump the version number. Why is this in
the settings DB anyway, rather than a carrier config option?
I also discovered that the SystemUI package copied the entire contents of
res/values/defaults.xml from SettingsProvider, when I originally tried
to update the unreferenced SystemUI version of the setting. To prevent
future confusion, I removed all of the values from the SystemUI version
of res/values/defaults.xml.
Change-Id: Ib8a75c85b9db5c1963b65538ee2765d5087e67d2
|
| |
| |
| |
| |
| |
| |
| |
| | |
This can be used as a compatibility workaround for host operating systems
without MTP support.
Change-Id: If4f1856206056ca8e40c3ffbfa382f185c413598
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
introduced the other day." into gingerbread
Merge commit '603a1f59703109c89ec0fdeceb0f8d28c7cede22'
* commit '603a1f59703109c89ec0fdeceb0f8d28c7cede22':
Fix some bugs in SettingsProvider that I introduced the other day.
|
| |
| |
| |
| |
| |
| | |
BUG=2953979
Change-Id: Ic9813e0ce629c56050d626ed52de67e6ab1ab07e
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
configuration "disabled; local transport selected"" into froyo
Merge commit '384759b1c5e39d0f99fa551a369ae73197ab26c5'
* commit '384759b1c5e39d0f99fa551a369ae73197ab26c5':
Make the default backup configuration "disabled; local transport selected"
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
transport selected"" into froyo
Merge commit '02e18d4d4eed949da02fd8aa87801858d99b902a' into gingerbread
* commit '02e18d4d4eed949da02fd8aa87801858d99b902a':
Make the default backup configuration "disabled; local transport selected"
|
| | |\
| | | |
| | | |
| | | | |
selected"" into froyo
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
By default out of the box, an Android build will have the backup mechanism in
its "disabled" state and pointed to the LocalTransport test transport. We
do not want retail devices built without the Google backend to have backup
enabled out of the box; it would cause them to gradually grind away the
cache partition for no good reason. On those devices with this change,
developers would need to enable backup manually (possibly using the normal
Settings UI; more probably using the 'bmgr' shell tool), but would no longer
also have to manually configure the active transport name.
Device vendors producing Google-enabled products will simply use resource
overlays to configure the default state and transport name for their builds.
When building a product that points to the Google backup transport by default,
the "def_backup_enabled" boolean resource should still be set to 'false' --
the Google backup disclosure activity supplied by GSF will take care of
enabling the backup services if the user opts in to it. (Basically, vendors
will never have to overlay the def_backup_enabled resource -- the default
value of 'false' is correct for any retail device regardless of whether it
can use the Google backup transport.)
In the SDK build, the default transport will remain the local one, but
the default enable state overridden and set to "true". This is the ideal
situation for developers: all aspects of the backup mechanism immediately
operative with no manual configuration needed.
Change-Id: I866f8f627b023b338bc7757e61604e6d8a901a34
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
slurp settings into cache." into gingerbread
Merge commit 'd335f9a90375db18b2f77f22f62379ac2d257384'
* commit 'd335f9a90375db18b2f77f22f62379ac2d257384':
Negatively cache settings and proactively slurp settings into cache.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The settings database cache is tiny (or should be tiny) and can be
slurped into memory. Once it's in memory and we know we have it all
we can avoid going to disk at all for keys not in the cache.
This is a big percentage of the StrictMode violations & latency.
Change-Id: I649411be0c40d348f58376ccfb3eda059fd69fbc
|
|\ \ \ \
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
time as well as ro.serialno
Merge commit '36c051c717391afe12a1fe8163960286175f2f7e'
* commit '36c051c717391afe12a1fe8163960286175f2f7e':
make android_id random seed depend on time as well as ro.serialno
|
| |\ \ \
| | |/ /
| | | |
| | | |
| | | |
| | | |
| | | | |
Merge commit '0fe27cf5bd1407bc7b4eabefaa91ff535582badc' into gingerbread
* commit '0fe27cf5bd1407bc7b4eabefaa91ff535582badc':
make android_id random seed depend on time as well as ro.serialno
|
| | |/
| | |
| | |
| | | |
Change-Id: I0a48aacd8da30896d91fa05b7791335e6ed751e5
|
|/ /
| |
| |
| | |
Change-Id: I798cc041fc1d93c3e51a1598a80781453229a523
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
froyo
Merge commit '1bcb665825dc97789e8c1b892ec4298fd0b8c552' into gingerbread
* commit '1bcb665825dc97789e8c1b892ec4298fd0b8c552':
Fix issue #2834005: Android Settings.Secure bypass
|
| |
| |
| |
| | |
Change-Id: Ic4f14e2ff5c2b4f623405d30389863a9e3e82572
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
recover from the busted
state.
Bug: 2767349
Change-Id: Id0c41734e82a1256a49175a2dc6b40f0abaf4f8b
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Merge commit '5ebaf10693725c9dc48219c3c65945b84d74692f' into kraken
* commit '5ebaf10693725c9dc48219c3c65945b84d74692f':
Fix broken logic in SettingsProvider.parseProviderList.
|
| |\ \
| | |/
| |/|
| | | |
Change-Id: I2a3a06f0bd3530f9c0d3cb64ca6a87913649d64b
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We were accidentally stripping both leading and trailing commas
when removing a provider from the enabled provider list.
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
|\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
into froyo
Merge commit 'feb976e6be3a07dd31b35b35287420bba9ffbbf3' into kraken
* commit 'feb976e6be3a07dd31b35b35287420bba9ffbbf3':
Fix an upgrade bug in SettingsProvider.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Bug: 2569112
Wrong usage of local method.
Change-Id: I9d7c68baa7cf8dd2b7e4345555c1edc374de94e6
|