Merge commit '2a3188672ab2b65c0ce7c9c598a463e382c47696'
* commit '2a3188672ab2b65c0ce7c9c598a463e382c47696':
rename a few files to camel-case, add copyright notices
Merge commit '85dfec8c35d4e3216591bd2e534bbebd6338b969'
* commit '85dfec8c35d4e3216591bd2e534bbebd6338b969':
Added bugreport collecting mechanism in case of crashes.
Merge commit '5de674e1cbd6e43b6d7954ccacf5cd709b30265d'
* commit '5de674e1cbd6e43b6d7954ccacf5cd709b30265d':
Adding missing callback onJsConfirm to dismiss any confirmation dialogs
fix a bug in GL lighting where the specular component could be ommited when vertex material was disabled.
Merge commit '3e8950c0c73f9c1574ce3388c754009edf6bc930'
* commit '3e8950c0c73f9c1574ce3388c754009edf6bc930':
Added new parameter to enable a manual pause between pages
Before, the variants of MemoryFile.MemoryInputStream.read() would throw
IOException or IndexOutOfBoundsException if EOF was encountered
before the requested number of bytes was read. This violates
the contract of InputStream.read().
This patch makes read() return the number of bytes available, if any.
If already at EOF, -1 is returned. The patch also adds new tests,
which checks cases where MemoryFile.MemoryInputStream.read()
should throw IndexOutOfBoundsException or return -1. several of these
tests failed with the old code and pass now.
This fixes http://b/issue?id=1881894
This allows content providers to use in-memory data to implement
ContentProvider.openAssetFile(), instead of just normal files
and sockets as before.
To test cross-process use of AssetFileDescriptors for MemoryFiles,
a test content provider and a client for it are added to
AndroidTests.
Fixes http://b/issue?id=1871731
Merge commit '7322c96cc0c2524d399fb43fb406fb6324a795c8'
* commit '7322c96cc0c2524d399fb43fb406fb6324a795c8':
Fixed issue where code for extracting scripts was eclipsed by runTest method.
Merge commit 'c665349543b481b14e423ea9e7e2b368569ae311'
* commit 'c665349543b481b14e423ea9e7e2b368569ae311':
support more minor cdms sms bearer data subparameters
Merge commit 'b56736b666dd906a214639e24b624ec368e383f5'
* commit 'b56736b666dd906a214639e24b624ec368e383f5':
Fixed bug where test status is not marked "DONE" when completed
* changes:
- create a new generic ISyncAdapter implementation, SyncAdapterNew - change the applyBatch to take an ArrayList rather than an [] - change Entity to be a final flass that contains ContentValues - remove the ability to update/insert Entities by a ContentProviderOperation
- change the applyBatch to take an ArrayList rather than an []
- change Entity to be a final flass that contains ContentValues
- remove the ability to update/insert Entities by a ContentProviderOperation
Merge commit '892771ab81f79a6b0cf9735701760c5a12d6ab85'
* commit '892771ab81f79a6b0cf9735701760c5a12d6ab85':
Rename WRITE_SDCARD to WRITE_EXTERNAL_STORAGE in browser test app
Merge commit '50566b3554f440d6b84a696875147d8d21682b10'
* commit '50566b3554f440d6b84a696875147d8d21682b10':
Update reliability test code. Use a separate activity with simpler calback mechanism.
Merge commit '181fafaf48208978b8ba2022683ffa78aaeddde1'
* commit '181fafaf48208978b8ba2022683ffa78aaeddde1':
Retool the backup process to use a new 'BackupAgent' class
Backups will be handled by launching the application in a special
mode under which no activities or services will be started, only
the BackupAgent subclass named in the app's android:backupAgent
manifest property. This takes the place of the BackupService class
used earlier during development.
In the cases of *full* backup or restore, an application that does
not supply its own BackupAgent will be launched in a restricted
manner; in particular, it will be using the default Application
class rather than any manifest-declared one. This ensures that the
app is not running any code that may try to manipulate its data
while the backup system reads/writes its data set.
Bug 1883998: We only support sending 8-bit references for now.
Bug 1885080: Also fix the GsmAlphabetTest, which started failing when SmsHeader
was re-worked.
Merge commit 'a5f50b8f49cc9b34b1de462e11498d92c692b978'
* commit 'a5f50b8f49cc9b34b1de462e11498d92c692b978':
Modify the base gestures API to use streams instead of files. Adds new wrappers to easily load/save gestures from files, resources, etc. Do the same for the letters recognizer.
As reported in http://b/issue?id=1398215 MemoryFile did not
munmap(2) the ashmem region after closing it. This
causes the process to leak virtual address space.
This change fixes the problem by calling munmap(2) in
close(). The unmapping is done by a helper method deactivate().
The change also replaces the use of an int for the
file descriptor with a FileDescriptor object to
make sure that we keep track of when the file descriptor
has been closed. I chose to implement it this way because I
will need decativate() and a FileDescriptor object in an
upcoming change that allows sending MemoryFile file
descriptors between processes.
The change also adds a number of tests for the behavior
of close(). The testCloseRead() and testCloseWrite() fail
with the old MemoryFile implementation, and testCloseLeak()
causes a segfault. They all pass now.
Merge commit '82392e84b9bcf618d1c41730ec14fb8dab841990'
* commit '82392e84b9bcf618d1c41730ec14fb8dab841990':
Cleanup Gestures API and make it easier to use in 3rd party apps. Also fix the events processing in the gestures overlay mechanism. Give better control of the various properties of the overlay through XML attributes.
