| 95cb226c1a4ff47531da65ef2617ade0dea5c9b8 |
|
11-Jan-2017 |
Hugo Benichi <hugobenichi@google.com> |
IP connectivity metrics: cleanup obsolete code
This patch cleans obsolete code related to IP connectivity metrics:
- remove @SystemApi on android.net.metrics: now that metrics events
are processed and serialized in the frameworks only, event classes
should not appear in the system apis.
- remove obsolete Logger classes: ConnectivityMetrics app was the
unique user of ConnectivityMetricsLogger until nyc-mr1. From nyc-mr1
the app started using dumpsys to get metrics for IpConnectivity and
Telephony, which made ConnectivityMetricsLogger obsolete.
- simplifications in MetricsTestUtil
Test: - runtest frameworks-net
- manually verified $ adb shell dumpsys connmetrics
Bug: 30054585
Bug: 32648597
Change-Id: I85ef65f7f69eb9299e4636cc7af54067201d9daf
/frameworks/base/core/java/android/net/ConnectivityMetricsEvent.aidl
|
| d1cb256b3efd2c00f1c44541b5589c2ea17b3cb8 |
|
01-Apr-2016 |
Pavel Zhamaitsiak <pavelz@google.com> |
ConnectivityMetricsLogger: Switch to "pull" model
If subscriber is in external app, its process can be killed. This would
lead to loss of events. To avoid that, we will be storing events in the
logger service. Clients can periodically pull data from it.
Another option for client apps is to register PendingIntent which will be
sent when certain number of new events has been received.
If events are logged at unexpectedly high rate from particular component,
then throttling mechanism will activate and new events will be blocked for
some time from that component.
Change-Id: I710409626eb5a42bcd3fe8126eac6b756fa1ab8b
/frameworks/base/core/java/android/net/ConnectivityMetricsEvent.aidl
|
| 02b3e6bfc5bbd5f1a8ce1ce68976e59142073b6f |
|
03-Feb-2016 |
Pavel Zhamaitsiak <pavelz@google.com> |
Add Connectivity Metrics Logger service
This service can be used to pass events to metrics collection service
Change-Id: I213874300693cd121f2c8676f70893315de4c4c0
/frameworks/base/core/java/android/net/ConnectivityMetricsEvent.aidl
|