This is a set of changes to allow for splitting off the Profile
concept in the Contacts Provider into a separate database:
- Removed the ALLOW_PROFILE parameter, as it is no longer possible
to combine profile data with contacts data in a single query.
- Added profile sync state as a separate table.
- Clarified status update API usage to indicate that profile updates
need to either be done for a specific data ID or using a new
profile-specific URI.
- Added constant and API for determining whether an ID falls within
the profile ID-space.
Bug 5204577
Change-Id: Ia0f8c6b490845100dd6d44e5e01a3b27346f077e
Account name and account type are being retrieved from the
cursor for the contact, but account dataset, which is the
3rd value to uniquely distinguish an account is missing.
Bug: 5210676
Change-Id: I85f93b3fa19839734e4e22928382e0f786ed8ee2
These settings can never be written to by engines and apps
anyway, and reading them does not serve any useful purpose.
The only code that needs to read these settings are the framework
TTS classes.
bug:5149036
Change-Id: I1f95977d241eb6b550105f45d29fee889da3fbd1
These columns store additional information about the contact associated
with a call log entry and are needed by the new functionality present in
the call log.
The information is used only internally by the call log, so these column
do not need to be part of the public API.
Bug: 5101753
Change-Id: Ie2160a157497f10ba5fc95c5fcf3b4095a99753a
When restricting background data, show ongoing notification to give
easy access to re-enable. Deprecate getBackgroundDataSetting() API
to always return true, since NetworkInfo.isConnected() is new source
of truth. Handle upgrade path by reading from existing secure value,
and kick one last broadcast when changing value. Remove background
data code from ConnectivityService.
Remove warning alerts, since they push ifaces into restricted list;
should only happen when iface has limit.
Bug: 5163559, 5129421
Change-Id: I0064d9d643656a4d32aaae51d4a58bce49fe295f
- Switch from resource ids to names to prevent breakage on package upgrade
Bug:5135277
- Add SYNC1...SYNC4 columns to StreamItems and StreamItemPhotos
Bug:5119385
- Remove ACTION, ACTION_URI from Groups, StreamItems and StreamItemPhotos
(this reduces db size and prevents click intercepting)
Bug:5135808
- Add some raw-contact fields to the StreamItem query
Bug:5134081
Doing those changes in one block to prevent too many db upgrade steps
Change-Id: I5618e210206e0315b91f5883e6b6b386dccb5881
This is needed for an upcoming change in call log that will show only
unread calls in the "new" section.
The field "new" will henceforth only be used for notification.
Bug: 5141185
Change-Id: Id24f815994ce90c89f5907c919ce95043a5d6217
Content provider does not directly use this intent. But it is fired by
the contacts app to request the voicemail source to fetch voicemail
audio of a single voicemail message.
The constant needs to live in the contracts file to serve as a common
definition between contacts and voicemail source apps.
Bug: 5114261
Change-Id: Ibf7b2a4c871d3561d2ca50d03f8182352fadd3ab
Since computing the geocoded location is an expensive operation, add the
geocoded location once and for all when inserting in the call log.
Bug: 5129581
Change-Id: I6017c993a52b461eed395ce5e5a9373018e2087a
Because changes to the route tables take time to propagate
we add a delay when sending out change notifications. This allows
applications, such as GTalk, to create sockets without encountering
a 3 minute timeout.
Bug: 5008488
Change-Id: I0eefb03a5d6358a58ea6ae5b4f697ff302b5511d
Combined volume panel only in tablets. On phones show active volume.
Added dummy assets for ring+notification icon.
Deprecated the NOTIFICATION_USES_RING_VOLUME. Now they are always
tied together. Audio manager changes still required to ensure that.
Initialize all feedback sounds to true.
Change-Id: I3ad7890c9be9334eedb5f3b709a4b6995fe24638
Fixes problems introduced with bulk insert support
Bug: 5092877
Change-Id: If3c0c9054d5effe0a1d7a75e85635b41ba1591f5
Signed-off-by: Mike Lockwood <lockwood@android.com>
1. Update the database creation/upgrade code to take care of the new setting
to enable touch exploration.
2. Made the tocuh exploration settings persistent to the cloud.
Change-Id: Ie24e9184b4a21869432d11d207cb6464fadbac3b
This was added to simplify some logic in the provider and app, as
there are places that can simply compare the concatenation of the
account type and data set.
Also added a DATA_SET extra for contact creation, to allow for this
value to be passed around via intents.
Bug 5077096
Change-Id: Ia0634cfcf4590fd90ccb5cb99360c38c86f08d25
We had initially decided to merge the NEW field (from the call log) and
IS_READ field (from the voicemail contract) into the single NEW field
already present in the call log.
However, it turned out that the meaning of the two fields is slightly
different: NEW means the items has just been inserted (and the user is
not aware of it) while IS_READ represents whether the user has read this
specific message (or heard, in case of voicemails).
This change makes the IS_READ field public, as well as deletes the NEW
field from the voicemail contract, since it is no longer needed there.
The NEW field in the voicemail contract (in fact the entire voicemail
contract) has never been released (this feature is new in ICS).
Bug: 5036195
Change-Id: I740c51c1a8e6d2460050eaab9943fb38b1565058
