| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Source: Trusted_NFC_Device_Host_AA03.01e02_google.zip code drop (23-Sep-2010)
Conflicts:
core/java/android/app/ApplicationContext.java
core/java/android/provider/Settings.java
core/jni/Android.mk
core/jni/AndroidRuntime.cpp
core/res/AndroidManifest.xml
include/utils/Asset.h
Change-Id: I62c92f4c79f5ee65126c97602f6bc1c15794e573
Signed-off-by: Nick Pelly <npelly@google.com>
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
alarm." into gingerbread
Merge commit '888bcdbeca34819c07d7dc06dc03d91207aea0c0'
* commit '888bcdbeca34819c07d7dc06dc03d91207aea0c0':
Add new Alarm provider class for setting an alarm.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The new class provides static variables for creating an intent to broadcast to
applications implementing the alarm clock. A new permission has been added and
applications are recommended to require this permission if accepting the set
alarm broadcast.
Change-Id: I7b1014acdc54371cbda19bcf9b5c395b647aa413
|
|\ \
| |/
| |
| |
| |
| |
| | |
Merge commit '1b60963c42e159aacc52d688defcac206e5ecec0'
* commit '1b60963c42e159aacc52d688defcac206e5ecec0':
Clarify the danger of READ_LOGS and DUMP permissions.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The logs inevitably contain PII, so now we are making that clear in user
strings and developer docs. Moving DUMP and READ_LOGS into the PERSONAL_INFO
group.
Note that this means we need string translations.
Change-Id: I1b5bf9d2d827ab1a31dedbdb30d0906a87c26a32
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
signatureOrSystem" into gingerbread
Merge commit '0237cf2eace5d35410e95f586fd40c3068c94582'
* commit '0237cf2eace5d35410e95f586fd40c3068c94582':
Mark MODIFY_PHONE_STATE permission as signatureOrSystem
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This permission isn't needed right now, since there aren't actually any
public APIs that require it. (There are a few calls in the ITelephony
interface that do, but they're all hidden.)
Since there's no good reason for 3rd party apps to declare it, let's
mark it signatureOrSystem for now. We can bring it back -- and probably
split it apart into multiple finer-grained permissions -- once we
finally expose full telephony APIs to 3rd party apps (see bug 1043005).
Bug: 2989096
Change-Id: Idf898d5e12d648a959f622cd815e75597195aa82
|
|\ \
| |/
| |
| | |
Change-Id: I27004dc464f5771d3205ae5757c6eccc5b16854d
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This fixes a problem where applications could ask the location
manager to do very heavy-weight things (like... say... update
location every minute), which would get accounted against the
system instead of the application because ultimately it is the
system making the heavy calls (wake locks, etc).
To solve this, we introduce a new class WorkSource representing
the source of some work. Wake locks and Wifi locks allow you
to set the source to use (but only if you are system code and thus
can get the permission to do so), which is what will be reported
to the battery stats until the actual caller.
For the initial implementation, the location manager keeps track
of all clients requesting periodic updates, and tells its providers
about them as a WorkSource param when setting their min update time.
The network location provider uses this to set the source on the
wake and wifi locks it acquires, when doing work because of the
update period.
This should also be used elsewhere, such as in the GPS provider,
but this is a good start.
Change-Id: I2b6ffafad9e90ecf15d7c502e2db675fd52ae3cf
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
is almost full." into gingerbread
Merge commit 'e75783440a55fb0a5ef75066be94a11898f652f0'
* commit 'e75783440a55fb0a5ef75066be94a11898f652f0':
Allow incoming SMS until internal storage is almost full.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix for bug 2382830: new incoming SMS should not be rejected when
running low on internal phone storage.
Testing revealed that the /data partition should have at least 256 KiB
available in order to prevent random app crashes (including system apps)
due to SQLite transaction failures. With 256 KiB free, the device should
safely boot without storage full errors. This takes into account the
36-40 KiB that the YAFFS2 filesystem reports as available even after
the partition has been completely filled. I've set the default full
threshold to 1 MiB to provide a generous safety margin.
For this bug, I changed the DeviceStorageMonitorService demon to send
two new hidden notifications for device storage "full" and "not full",
when the free space falls below the full threshold (default 1 MiB,
but configurable as a system setting), in addition to the existing
storage low/okay notifications sent when the storage crosses the threshold
of 90% full (also configurable).
The SMS code was changed to use these new notifications so that it can
accept messages until the data partition has been filled to the maximum
safe capacity rather than stopping when it hits 90% full. There should
be no negative impact on battery life because the additional check in
the storage polling service should be offset by an optimization to cache
the free threshold values which were previously being computed every time
through the loop.
While testing this change, I discovered that SMSDispatcher was being
instantiated twice, the first time in GSMPhone/CDMAPhone, and the second
time in SimSmsInterfaceManager / RuimSmsInterfaceManager. Changed the code
to pass the original SMSDispatcher to the Sim/RuimSmsInterfaceManager
constructor.
Change-Id: Ie0c6d05294778ab6ee42e0fa01313af96d824c77
|
| |
| |
| |
| |
| |
| |
| | |
Turns out this would be useful for automated testing.
Change-Id: Idd5e35a8d4a354447b17a77fe0b606f78df844d0
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
| |
| |
| |
| | |
Change-Id: I8211675e619bcc31c991296387513d07ad53ff10
|
|\ \
| |/
| |
| |
| |
| |
| | |
Merge commit '840f0fecd87357cadf4b2a0ae96d30b457f89729'
* commit '840f0fecd87357cadf4b2a0ae96d30b457f89729':
Clean up some permissions.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Note that WRITE_OWNER_DATA and READ_OWNER_DATA don't actually appear
to be associated with anything or used by anyone, so they are just
deleted.
Also deprecate the activity API to go in the foreground. I didn't
realize that was released in the SDK. It needs to go away.
Change-Id: I96f53702c2c79e4999b6b2c498abb770bd27e03a
|
|\ \
| |/
| |
| |
| |
| |
| | |
Merge commit '679ac09a5c22175354f3a04b28456b323839530e'
* commit '679ac09a5c22175354f3a04b28456b323839530e':
More native work.
|
| |
| |
| |
| |
| |
| |
| | |
Implement save/restore of state, and add native APIs for
configuration information.
Change-Id: I2a3ddc2ba605db58d7c8b2b31b9215fb323f90b5
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Usb.ACTION_USB_CAMERA_ATTACHED and Usb.ACTION_USB_CAMERA_DETACHED are sent
when cameras are connected and disconnected.
The data field of the intent contains a Uri for the camera in the Mtp content provider.
Change-Id: I814221b4f0507b309997c71edb5a041e8efc54f7
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
|\ \
| |/
| |
| |
| |
| |
| |
| |
| | |
broadcast.
Merge commit '0d929d7f094f2ea743c9ce2e17d5e40780cfe757'
* commit '0d929d7f094f2ea743c9ce2e17d5e40780cfe757':
Make android.hardware.action.USB_STATE a protected broadcast.
|
| |
| |
| |
| |
| | |
Change-Id: I84160e9342025228c1f810077f5aa25f5cc83023
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We now broadcast Usb.ACTION_USB_CONNECTED and Usb.ACTION_USB_DISCONNECTED
when USB is connected or disconnected.
The ACTION_USB_CONNECTED extras indicate the enabled/disabled state of
all USB functions.
Change-Id: I11495d039429dbe22bd738067296e39ae415befa
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Adds permission android.permission.ACCESS_USB.
This is a partial cherry pick of a change from master.
It adds the permission, but not the support for associating it
the AID_USB group.
Change-Id: If5816721a4fc88bf444141a7b717da65ea37d5f4
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We now broadcast Usb.ACTION_USB_CONNECTED and Usb.ACTION_USB_DISCONNECTED
when USB is connected or disconnected.
The ACTION_USB_CONNECTED extras indicate the enabled/disabled state of
all USB functions.
Change-Id: I919fcd5aa8d640d051cec87053f474a9843ed545
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When the default network goes down we lose the wake-on-incoming-data capability
until the new net is brought up and apps rebuild their connections. We fixed this
in Wifi, but it's a general connectivity issue, not a wifi issue so moving the
mechanism to connecitivty so other networks can use it.
bug:2734419
Change-Id: I39b5d825eb6b548bd9bb8f179b89254f4db53147
|
|\ \
| |/
| |
| | |
Change-Id: Ia4538f73d8bade9e6565835d484dcb650830feca
|
| |
| |
| |
| | |
Change-Id: I57b2d296e0d0cef0d256ae6697fffc47188d14df
|
|\ \
| |/
| |
| | |
I4a11f027,Ib2c4abf6,Id0c7ef9f,I839d7771 into kraken
|
| |
| |
| |
| |
| |
| | |
Also fix the notification to show properly when the runtime is restarted.
Change-Id: Id0c7ef9f9dc9c9df18428cbaa7db1703f085137e
|
|\ \
| |/
| |
| | |
Change-Id: Ic59db363391f73343eba32894113914ceea5a963
|
| |
| |
| |
| |
| |
| |
| | |
Only one can be running at a time, their process can not be killed,
and a notification is posted while it is running.
Change-Id: I843015723947e0c934ae63a1aeee139327c0bc01
|
|\ \
| |/
| |
| | |
Rename the Cloud to Device" into froyo
|
| |
| |
| |
| | |
Change-Id: I12ab32de393e44a499e3f9e3a0b38f4682156ff5
|
|\ \
| |/
| |
| | |
rename datamessaging" into froyo
|
| |
| |
| |
| | |
Change-Id: I583ac61c7b8fce69d60801dc76aeca9f13d250b2
|
|/
|
|
|
| |
Change-Id: Ib3dd573a5ef3950d20b21251fe7a3efad56b5c1f
Signed-off-by: Mike Lockwood <lockwood@android.com>
|
|
|
|
|
| |
Bug: b/2553489
Change-Id: I681b3f9a243777b931298cc93c9d34c8d7eae0f2
|
|
|
|
|
|
| |
Also fix bug where night mode was being used in desk dock.
Change-Id: I56c1cf3d6fe800a4f986d40cc4cb2e70b76ac261
|
|
|
|
|
|
|
|
| |
Partly reverts I6308b476ad18b1d71d7438b936c592a45365c9f0
Bug: http://b/issue?id=2535598
Change-Id: Ib488c6d4f10a87b714ecb78eef6fe58f572907c6
|
|
|
|
|
| |
Change-Id: I5e495332c45f718178486f2e07d37031e6fa5afc
Signed-off-by: San Mehat <san@google.com>
|
|
|
|
|
|
|
|
|
|
|
| |
I can't believe I let this slip through. And in the SDK no less. :(
The APIs for setting preferred activities will now throw a security
exception when used. This may break some apps, we'll see how it
goes. If it is too bad we can just make these log and not throw
anything, but I would much prefer they throw an exception.
Change-Id: I3aed434750eef8b202aa9d5bd774a0121be521c6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Extract all UI behavior from dock observer and ACTION_DOCK_EVENT.
Also introduce a desk type to go along with the car type all through
the resource system, since we now need to have corresponding high-level
broadcasts for desk dock mode. As part of that I also reworked some
of the logic for switching modes to all funnel through a single
update() call that looks all of the current state to decide what to
do next, and fixed various locking issues.
In addition I found there were bugs in the configuration change
handling causing us to only switch into the car mode config and
then never get out of it. Unfortunately now that we are actually
changing the configuration for each mode change, the transitions
between them are really crummy as we restart all kinds of
activities. :(
|
|
|
|
|
| |
Getting rid of notification dialog - maybe the entire TetherActivity.
Also getting rid of toasts - to ephemeral.
|
| |
|
|
|
|
| |
The notification is an ongoing event and can be used to get out of car mode.
|
|
|
|
| |
permission.
|
|
|
|
|
|
|
|
| |
Any package can now participate in backup/restore, without requiring any
manifest-declared permission. *Control* of the backup manager is still
guarded by the BACKUP permission, which is signatureOrSystem.
Change-Id: I116fcfcd4cd255e3c976330da1c4dea7d4faae9d
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The device mode is now called ui mode. Furthermore is the order of
precedence for the resources now in such a way that the ui mode needs
to be specified after the orientation and before the density.
The ui mode can be set, like it is done for the locale, as follows:
IActivityManager am = ActivityManagerNative.getDefault();
Configuration config = am.getConfiguration();
config.uiMode = Configuration.UI_MODE_TYPE_CAR | Configuration.UI_MODE_NIGHT_ANY;
am.updateConfiguration(config);
To allow users to disable the car mode and set the night mode the IUiModeManager
interface is used.
The automatic night mode switching will be added in a separate change.
|
|
|
|
|
|
|
|
|
|
|
| |
events (and in one case, a DropBox entry).
Add a simple intent that triggers master-clear (and toggle EFS), given the
right permissions.
Bug: 2264596
Bug: 2350452
Bug: 2264596
|
|
|
|
|
|
|
|
|
| |
This replaces the old Google-specific geolocation setting.
Fixes http://b/issue?id=2428694
Part of http://b/issue?id=2383870
Change-Id: I6308b476ad18b1d71d7438b936c592a45365c9f0
|
|
|
|
|
|
| |
StatusBarPolicy
Signed-off-by: San Mehat <san@google.com>
|