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
Initially we had exposed NEW in the voicemail provider instead of the
IS_READ field. However, NEW is already used in the call log to represent
a missed call for which a notification needs to be shown to the user.
On the other hand, voicemail need both be shown in a notification and
retain their own read/unread state, which is determined by whether the
user has opened the details of the voicemail.
This change introduces the IS_READ field for voicemails and exposes it
also via the call log content provider.
The NEW column in the voicemail content provider will be removed in a
follow-up.
Bug: 5036195
Change-Id: I2f8c04685a82cbf77f4778cf057ff62c7da1256a
1. Upon registration of an accessibility client the latter received only
the accessiiblity state and waiting for the touch exploration state
to be sent by the system in async manner. This led the very first
check of touch exploration state is checked a wrong value to be reported.
Now a state of the accessibility layer is returned to the client
upon registration.
2. Removing the dependency on talking accessibility service to be enabled
for getting into touch exploration mode. What if the user wants to use
an accessibility service that shows a dialog with the text of the touched
view?
bug:5051546
Change-Id: Ib377babb3f560929ee73bd3d8b0d277341ba23f7
Bug: 4176026
This CL inherits https://android-git.corp.google.com/g/112600
Spec of TextServiceManager
- Chooses the most applicable TextService(e.g. SpellCheckerService, WordBreakIteratorService..)
for each locale
Spec of SpellCheckerService
- Returns whether the given string is a correct word or not
- Returns Suggestions for the given string
Change-Id: Iaa425c7915fe70767ad0b17bf6c6fbcd2a1200b2
Also moved customizable settings into Settings.Secure and
added listeners for setting changes into the state machine.
Change-Id: Ia6859c71f7edae13062685867959adc423af4643
The Autofill server is now configured as a system setting. Add
that setting and a method to be called over JNI from the chrome
stack to retrieve it.
See also external/chromium change I3a22ae42402f52207eee2d0d9df64700cb7c9f45
Bug: 4515820
Change-Id: I0aa85c5bef834b1120baaabdc2dd2e4e607a63b6
- Social stream photo updates should use the new photo storage
system instead of storing the image content in BLOBs.
- Package names need to be text, not numbers. The status update
documentation was incorrect.
- Social stream photos will include a URI the caller can open to
get the photo content.
- Removed the max photo bytes from the stream item limit query,
as we'll do appropriate resizing with the photo storage system.
Change-Id: I103ee1340c1a3772ae37add3684b0658c241a49c
This should fix a bunch of problems introduced in the original bulk insert implementation
Also reverted two changes that are no longer necessary:
Revert "MediaScanner: Add virtual NO_MEDIA column to fix support for .nomedia files"
This reverts commit 92e1314ad9.
Revert "MediaScanner: fix breakage in updates"
This reverts commit 45aaa2a345.
Change-Id: Ibed66393467761c2c1ce48deb09bcac505b7d221
This is a new content provider implemented to add visual voicemail
support in android.
Voicemail content provider is the central repository for storing
voicemails inserted by various voicemail sources. The content provider
also exposes a status table to let the voicemail source application
convey its current status to the system.
The primary application that reads from this content provider is the phone app.
The phone app shows voicemails along with other call entries within the
call log and optionally any relevent message about the voicemail source
status.
The implementation of this content provider can be found at
https://android-git.corp.google.com/w/?p=platform/packages/providers/ContactsProvider.git;a=blob;f=src/com/android/providers/contacts/VoicemailContentProvider.java
Change-Id: I8ad46aec20c70684f7bfa45530bbb90dd841d81a
1. Seperated touch exploration to be a seperate setting rather being
magically enabled by the system of accessiiblity is on the there
is at leas one accessibility service that speaks enabled. Now
there is a setting for requesting touch exploration but still the
system will enabled it only if that makes sense i.e. accessibility
is on and one accessibility service that speaks is enabled.
2. Added public API for checking of touch exploration is enabled.
3. Added description attribute in accessibility service declaration
which will be shown to the user before enabling the service.
4. Added API for quick cloning of AccessibilityNodeInfo.
5. Added clone functionality to SparseArray, SparseIntArray, and
SparseBooleanArray.
bug:5034010
bug:5033928
Change-Id: Ia442edbe55c20309244061cd9d24e0545c01b54f
In the process, I created a second overload to the function that returns
the photo to allow returning either the high-res or the thumbnail version
Bug:5033899
Change-Id: I7be257eb54b296445e20561d318a70c382d6ade9
This adds support for storing larger, hi-res photos in the contacts
system. Thumbnails continue to be stored in the Photo.PHOTO column
as BLOBs, while hi-res versions of the photos are stored in the file
system and referenced via a photo file ID (with metadata stored in
a new table).
See go/large-photo-design for details.
Change-Id: Ie182eaa6a0330e2eca0a732f201f20a91e4dc584
This provides a way for multiple sync adapters to exist for a single
account type. Internally, for example, we can use these new columns
to support separate sync adapters (and sourced data) for Focus,
Emerald Sea, and Latitude.
Change-Id: I1b8dfd79e9fb2dfcee6ac6d4adb947093f5c2324
Uses NTP server and timeout from secure settings, or fallback to
defaults in resources. Update various system services to use cached
NTP time when fresh enough, or force updates as needed.
Bug: 4517273
Change-Id: Ie1c4c4883836013d02ca0bbd850cf8949f93b34b
This exposes the set of apis necessary to unbundle the Calendar
app and sync adapters as well as allowing third party developers
to officially access the calendar provider. This is the current
final set of apis to expose, though changes may occur if we
discover new issues. The documentation and CTS tests are still
in progress.
Change-Id: If77f9a1d49a26725b44b1014e8d088be7ffbc707
No one should now be using these fields. SOURCE_CONTENT_URI was not
marked deprecated, but following a recent change in content provider
this field is also no more in use.
Change-Id: I58bb7872ba2f6cec169499d1a01d755232dde2f0
- Add one more column in MediaStore to indicate whether a
media file is drm-protected.
- Remove old DRM code from Ringtone
- Use the new DRM code in RingtoneManager
Change-Id: I1311fd1c04841c2cd47df6c901589966cf55a692
Moved constants/methods specific to Voicemails and Status table under
respective classes.
Marked currently used constants as deprecated, which will be deleted
once the apps using it is modified.
Change-Id: I122439c32ac62e9ae83c4c8468f5160a79743335
This change adds support for a richer API supporting social status
updates.
The new API supports providing multiple status updates (stream items)
to be associated with a single raw contact, and for multiple photos
(stream item photos) to be associated with each stream item. A
limited number of stream items will be stored - callers can query for
the limit to optimize calls. Any inserts beyond the limit will
result in expiration of the oldest item.
Change-Id: Ib46fdf8864472d4a1be250b9051e7d37ec32c089
Move the constants from the contacts provider implementation to the
framework.
These constants will remain hidden as currently only the system is
allowed access to the voicemail, protected by a signature permission.
Change-Id: I7cdb0fe217603b3d755238067a877f4209f4c26c
Basiaclly two changes included:
- Let CallLog use new data usage feedback API, so that
ContactsProvider2 is able to figure out what type of contact
method is used when a person is contacted.
- introduce phone_only parameter for strequent uri, which enables
Contacts app to obtain a contact list for recently phone-called
contacts.
markAsContacted() isn't used anymore, as nhe new API takes care of
old counters (TIMES_CONTACTED/LAST_TIME_CONTACTED) too.
Bug: 4371572
Change-Id: Ie193bb91ee49b18f4a546a1f52be780bb514301d
