| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
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
|
| |\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
secure settings. Diable attribute for UI. Set default value to auto. Add command line interface to set install location via pm." into froyo
Merge commit 'a599469f9095532cac95a8e7600412f156b88f1c' into kraken
* commit 'a599469f9095532cac95a8e7600412f156b88f1c':
Fix 2579461
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Move install location values to secure settings.
Diable attribute for UI. Set default value to auto.
Add command line interface to set install location via pm.
Change-Id: I80e97b3d24845adad7102f40dcbe238f00efa406
|
| |\ \ \
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
timeout values." into froyo
Merge commit 'e133177980b908d183ed8fe46cf3ea33405b8bd5' into kraken
* commit 'e133177980b908d183ed8fe46cf3ea33405b8bd5':
Fix for Never not existing in latest timeout values.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Bug: 2535288
Change-Id: I15ca60c7afe58fbe57e557e6d0028dc200d8b322
|
| |/ /
| |
| |
| |
| |
| |
| | |
Removing unused features from source tree.
Please refer to Bug#2502219.
Change-Id: I879c29bfd5ffe933f64bb1082aaae7c956450a5a
|
| | |
| |
| |
| |
| |
| | |
Part of bug #2545514
Change-Id: Ic775e3b942c485252149c1b6c15c88517fa4e3e5
|
| | |
| |
| |
| |
| |
| |
| | |
unclosed SQLiteStatement objects cause finalizer warnings.
nix them by closing this object in finally block.
Change-Id: Iea86ff169f935bb743aa0c32aa4aeb0cb4fcd4ad
|
| | |
| |
| |
| | |
Change-Id: Id1a0d62dc917937fc14ccab26eb7bd2c2148137e
|
| | |
| |
| |
| |
| |
| | |
Fix finalizer error bug 2483608
Change-Id: I49c33dc68cd3f24772990a467790ecaa06e13a18
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Use constants defined in PackageHelper for user preferences
to install auto, internal, external.
Set default install location to external.
Update settings db version number
Change-Id: Ib5110c9377990e20a48cee923e55898dfddfd1e6
|
| | |
| |
| |
| | |
Change-Id: Id31e24ef0536278ccb66b22bba7ed2b47eb1a371
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On insert(), check to see if the value is redundant by checking if
it's the same value already in our cache (but without faulting it in
to check). If so, avoid hitting sqlite or spamming all the
notification listeners with such uselessness.
This reportedly is happening a fair bit.
Change-Id: If58feb3ff1d00027dd927e0900087388cbcd72ae
|
| | |
| |
| |
| | |
Change-Id: I50289ece2d7f5f50d2ea2efbacac7a0bb1483bf6
|
| | |
| |
| |
| |
| |
| | |
Bug #2460685
Change-Id: I402e342673cd8de88664a595401a141e09583e1d
|
| | |
| |
| |
| |
| |
| |
| |
| | |
This brings down Settings lookups to 0.5 ms on sholes. (down from
~10.5 ms originally, and ~2.5 ms after the ContentProvider.call()
interface)
Change-Id: Ibde7c3d21e0b0e5714714a2075f314726edfc19d
|
| | |
| |
| |
| | |
Migrate old settings to secure on upgrade.
|
| | |
| |
| |
| |
| | |
Bug: 2320026
Change-Id: Idede20701c5a3d0e60bd327a869b1adf1577db21
|
| | |
| |
| |
| | |
Change-Id: I0b21316ff890d7f3c7d4b82837bb60670724c2e8
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This permits implementing interfaces which are faster than using
remote Cursors. It then uses it for Settings & SettingProvider, which
together account for ~50% of total ContentProvider event loop stalls
across Froyo dogfooders.
For fetching Settings this looks like it should reduce average
Settings lookup from 10 ms to 0.4 ms on Sholes, once the
SettingsProvider serves most gets from in-memory cache. Currently it
brings the Sholes average down from 10ms to 2.5 ms while still using
SQLite queries on each get.
|
| | |
| |
| |
| | |
Change-Id: If2e09d6b4e65c75e7e90754adc2425fa73d2602a
|