This permission allows an app to use the public download manager API
to download files to the cache partition that won't be automatically
deleted when the download manager needs space.
Change-Id: Id9a5cd61c940df22765b358290b8ad8ceeff493e
I'm removing this currently unused functionality from the Download
Manager implementation, so the constant might as well go.
Change-Id: I4f0970211201881a8426b83b5275408cd14c3377
* Additions to DownloadManager to support control of broadcast intents, allowed network types, and roaming control. This includes new constants and added implementation.
* New DB columns to hold connectivity flags and one to indicate whether the download was initiated through the public API; this is used to change behavior related to broadcast intents and connectivity controls.
Change-Id: I2e8e4ce92cde7889a0f24dc43b86c596c73c0eaa
* constants for new DB table, keys for including headers in a
DownloadProvider.insert() call, and new URIs for retrieving headers
* support in DownloadManager to pass headers to the provider
First, in the download manager public API, I'm changing
COLUMN_REQUESTED_TIMESTAMP to COLUMN_LAST_MODIFIED_TIMESTAMP, a field
that already exists in the download manager. Upon inspection of
existing users of this field, it looks like there are some good use
cases -- for instance, looking at when a download completed. And if
I'm exposing that timestamp, there's no need to also expose the
requested timestamp.
Second, this change includes support for file URI destinations:
* add DESTINATION_FILE_URI for use by the DownloadManager wrapper
* make DownloadManager use it appropriately
The backend support is in a separate change (since it's in a separate
project).
Also fixing a bug with file URI construction when DownloadManager
fills in COLUMN_LOCAL_URI.
Change-Id: I5bb93a222cd23215c2a03ed9f68d7f140454f7f2
Rather than come out of the user-modifiable APN DB, the DUN APN data will
come first from a built-in resource and then potentially overriden by a secure
setting (which is gservices upgradable).
Also made the "require-dun" setting secure-setting overridable.
bug:2736390
Change-Id: I1e4644c3839f06c977b83797641f3948785146a2
Merge commit 'd1055a250c00b0c2516ec406a8cf9a5ab1c0b7ae' into froyo-plus-aosp
* commit 'd1055a250c00b0c2516ec406a8cf9a5ab1c0b7ae':
Make the NTP Cache max-age gservices-settable
* ExtendedValues' "name" and "value" columns are exposed in Entry
entity subvalues, but it is clumsy to change a value, as the _id
of the ExtendedValues row isn't also exposed. (We otherwise have to
perform a potentially slow query)
* This CL adds the _id column to the columns exposed
Bug: 2638762
Change-Id: Iaffeffed620af78439f5f73aa5f3257b0f8a0fd0
Don't use hard coded defaults - use build configs instead.
Iface is now ONLY set by config so gservices doesn't need to.
bug:2576057
Change-Id: I8f9e3bc51af3b1cdf8bb4290a43197d9c01e2a14
Rather than dispatch a message for every url in the db, send a message to the
WebCoreThread to handle the query and iteration. Update the documentation for
requestAllIcons.
Bug: 2581894
Change-Id: I8af4f87570465dff3839db4ac492883e8805b007
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
We add a variable for saving wifi state
to restore after tethering.
Bring up wifi on boot up if the state indicates so.
Bug: 2537983
Change-Id: I9c6548b93df6fcbc0cec1e6b857f7224dc6d1b2c
On keyboardful devices, it is possible to disable the system soft input
method. Something changed in eclair that caused the ime to be re-enabled
on every package manager update (packages added/deleted).
Now keep track of disabled system imes in the settings db and search
in that list before enabling a system IME on package changes.
Every time the user goes to settings to enable/disable imes, the list
is re-created.
Any new system IMEs that may be added via an OTA will get enabled if
they have a different package name.
Fix for http://b/issue?id=2539948
This public API can be called from any thread, so do not use an
AsyncTask. In a separate changelist, the caller now uses an
AsyncTask instead.
Change-Id: I646950964323f8c749f9aa2176226561c6f2b21f
Fiddle with how we go into car mode to try to ensure we get a clean
transition. Also have the system take care of remembering the night
mode setting so it will stay at what you want.
Change-Id: Icb94fdd961c7a192f7707ec71544485a1ea12455
Snoozing alarms was causing a leapfrog effect which would drop the
alert in the middle because of PendingIntent. By making each intent
unique to a given time this will no longer occur.
Change-Id: I6ca6821f7f8879a299775f4fca4e2ad0de55f1bc
Fix for http://b/issue?id=2511581
Also call delete instead of deleteHistoryWhere, since we are only
considering non bookmarks anyway.
Change-Id: I00c052db3d27d61592688e7a160e721d5f82b210
Shelling out to logcat from the system server makes me queasy,
so this is turned off by default -- it must be enabled individually
for each error type (system_app_anr, etc) via a secure settings
value (which I plan to poke into from gservices for internal use).
Even when enabled, it happens in a side thread, unless the system
server is about to die anyway (system server restart).
Change-Id: Id6d88bcd78d3625f0364a5fe9c771046601a5a14
This is part 1 of the fix for bug 2364220 "Accessibility improvements for
ending calls". This change adds a new (hidden) constant
Settings.Secure.INCALL_POWER_BUTTON_BEHAVIOR, for a setting that controls
whether the Power button hangs up the current call, or just turns off the
screen.
Bug: 2364220
Change-Id: I14d4a89b27e99cac51dc16826d217072d999b2d6
Add a new column to both the pdu and sms tables. This change just adds
the column definitions. Bug 2505620
Change-Id: I34b2794566a2900932ae34bdded4ed361d503d07
Fix issue #2493497: Stuck in the Emergency dialer - Home/Back keys doesn't work
This was another case of not updating the window focus when needed, this time
when the lock screen was hidden.
Also re-arrange the layout/animate flow to address issues where you would see
a flicker of whatever was behind the lock screen when showing a new activity that
hides the lock screen. This was because we were deciding to hide the lock screen
during the layout phase, which meant we had to do it without considering whether
it had drawn. So we could hide the lock screen before the window is shown for the
first time after being drawn. Now we can do this in the policy during animate, so
we can wait until the window is drawn and actually being shown.
The flow in perform layout is thus significantly changed, where the layout and
animate loops are both under the same repeating loop. The actual flow from this
should be the same, but it now allows the policy to request a new layout after
the animation loop is done. This actually cleans up a number of things in this
code as the complexity has increased.
Finally this includes a change to the ui mode manager when switching modes, to do
the resource configuration switch at a different time. This makes transitions
between modes much cleaner (though not yet perfect).
Change-Id: I5d9e75c1e79df1106108dd522f8ffed6058ef82b
