| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
See b/213625234.
Test: Built API documentation
Signed-off-by: joneckenrode <joneckenrode@google.com>
Change-Id: Icb2eb3eb13c291dca9fc6857db3a8657a23856f7
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Clarified that Context.bindService() returning true only indicates
that the system has found a service to bind to the client and that
ServiceConnection.onServiceConnected() might not be called if the
service encounters an error, such as crashing during startup.
Test: make ds-docs
Bug: 63118511
Change-Id: I0906de76abf4124d74f7f4f80ac0eab3cbf94f7e
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Historically, if a service returns null from onBind(), the binding app
gets no information about the outcome: the ServiceConnection is never
invoked. We now introduce a new connection callback, onNullBinding(),
for apps that need to detect this situation. When the service rejects
the binding by returning null, the onNullBinding() callback in the
associated ServiceConnection is invoked instead of onServiceConnected().
onNullBinding() has an empty default implementation, so there is no
binary-compatibility impact of this new interface method.
Bug: 67377345
Test: atest android.app.cts.ServiceTest
Change-Id: I224512c118f7d6e5c1c2bb69eca1902882e73594
|
| |
|
|
|
|
|
|
| |
Renamed.
Test: booted and ran.
Change-Id: Ic21f7ef66d43fb6db9f7ebbc833f28c09474ea59
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(Finally) introduce a new ServiceConnection callback to
tell you when the binding has died. This allows you to robustly
have a weak service monitoring, and also is an easy way to find
out about breakages due to app updates etc.
Also clean up some debug output.
Test: moved to own suite and ran them.
Change-Id: I526cc00816c384fa9eb1312b92406f38085cbff9
|
| | |
|
| | |
|
| |
|
