Make ConnectPanReceiver a child of ConnectProfileReceiver, check if a
profile proxy is null before trying to connect. Change log output in
bluetooth. Remove some oververbose parameters from test runner. Make
the setup for the tests more consistent (delete pairings, etc).
Most of this work has been done to facilitate the tests created for
trade federation.
Change-Id: I7350d308b5d09c2052e0a3f3308a69c564ba4d74
Bug http://code.google.com/p/android/issues/detail?id=14786
Empty spans are affecting the text before and after them. See the
comment in TextUtils.removeEmptySpans for details.
Change-Id: I40376c32fd56a17efde6219f9b2593e4b4ab1ba1
paths of code getting the mCacheLock and DB locks in different
orders.
The philosophy I followed for this was to ensure that the
DatabaseHelper is only ever accessed from within a
synchronized(mCacheLock) block. I also renamed a bunch of
methods to make it easier to know if a given method should
be called from within this synchronized block.
Bug: 3404506
Change-Id: Ia48f95e77b77647d0717f70f1d8364da3719cc13
Before the IPackageDeleteObserver only knew whether the deletion
succeeded or failed, but not the reason why.
Bug: 2520191
Change-Id: I1f0d7c04f06c539660b6e17e7e133defb0f61b5b
Add test cases for AudioManager.startBluetoothSco() and
AudioManager.stopBluetoothSco()
Bug: http://b/3292864
Change-Id: I743c8d732270262fbaaff79a53d43cedcd5de528
Don't hold locks while running create or remove callbacks. That gets a bit
ugly because it means a create could be unwanted by the time it returns.
Change-Id: I14b2b3ed41a446750f8ee5a7e35cb8d801c4ce6d
http://b/3461302
bug:3444147
1. Now that the spans with CSS data are included in the accessibility
events, such that a client can parse them, the tests are doing so.
Change-Id: I574c68d27a95cd8226dd7634b00a7d404ae387fe
bug:3421690
This change is related to change:Idfec7e6a
1. Added tests for cases in which the previous
implementation was not behaving as expected.
2. Refatered the tests to be intrumentation tests
since the code under tests uses the DOM element
dimensions to determine visibility and if the
the WebView has no size i.e. not attached to
ViewRoot the size of all DOM elements is zero
forcing all tests to fail.
Change-Id: Ib4c01af8feb09f2b2a6b9d906e08bfaaa9e9bc74
PackageManagerService shouldn't check features that a package declares
that it uses because this will cause problems in the future when we add
more features that older phones didn't explicitly declare. We must rely
on markets to know about phones and filter them for us to avoid this
situation.
Bug: 3409434
Change-Id: I419a5b936be3572b83a485081a6c81b2f1c8741c
1. Added tests for the new code added by change:I5a796aef
2. WebCore thread now calls the UI thread to set the cursor to
the current position enabling the user to interact with
the content that is being selected on the page.
3. Removed the code that changes the selection on movement of the
cursor ring. We are dropping the "default web view behavior"
as granularity of reading the document since with this change
a user can freely access inputs/buttons/links.
Change-Id: I7a3f6677eff0bc95e8127973d07cec78e3465c7b
AppCacheTest was multiplying two integers that were too large for
devices that had more free space than 32-bits could represent.
Hopefully no one releases devices with 1TB soon.
The testAppCacheClear test doesn't work currently because it has an
"imax" attribute that doesn't allow the disk to be filled up entirely.
It only writes a couple hundred MB before it gives up.
Bug: 3216419
Change-Id: Ie371f42211bab65f2c767b36d9837ce76922501e
Tests were giving false failures when they should instead be skipped.
Forcing an install to an SD card on a device without one shouldn't count
as a failure. It's expected behavior.
Bug: 3216422
Change-Id: Ia523861d1331e74c76b434f7ba73b642d474a9cc
The finalize() call did not clean up completely, this eventually
caused the android.process.acore to crash since it ran out of fds
and GREF to increased above 2000 if an application forgot to close
its cursor objects. A warning was also added when this happens so
that application developers can correct their mistake. The
included test case tries to verify that the finalizer works as
expected by creating a bunch of Cursor objects without closing
them (without this fix the acore process crashes after about 400
iterations and the test case ends with "Process crashed").
Change-Id: I11e485cef1ac02e718b2742108aa88793666c31d
The required features check was in an null check for usesLibraries, so
it wasn't checking for required features when an application did not use
a library.
Bug: 3331713
Change-Id: I96d366ba00d4962b84f3796be97e2b622eb331a5
