| 161977998feebf0a855ea56558464470877040cf |
|
04-Nov-2014 |
Jeff Davidson <jpd@google.com> |
Rename BROADCAST_SCORE_NETWORKS to BROADCAST_NETWORK_PRIVILEGED.
This is necessary/desired for two reasons:
1. UX around network scoring shipped with L despite lacking underlying
platform support. We do not want network scoring applications to
trigger this UX on L devices, and therefore we must break the contract
of what defines a network scorer so that apps build against the new
contract don't trigger the old UX.
2. As a start towards generalizing the term "score" for a potentially
broader role in the future, though that role is very much undefined.
Bug: 18160480
Change-Id: If228977513e32e45bc44dbeda24aa18436fdfca6
/frameworks/base/core/tests/coretests/src/android/net/NetworkScorerAppManagerTest.java
|
| b6646a8987a8ce6abd34cc05d9ca0193a6d7bea9 |
|
28-Jun-2014 |
Jeff Davidson <jpd@google.com> |
Allow network scorers to provide an opt-in activity.
A candidate scorer may have an activity registered to listen for the
ACTION_CUSTOM_ENABLE intent action. If so, when the user attempts to
select this scorer as the active one, this custom activity will be
launched and will be responsible for requesting that the framework
activate the scorer. This is to enable more complex opt-in flows prior
to becoming the active scorer.
Scorers which do not specify this activity will default to using the
framework switcher (currently ActiveNetworkScorerDialog, though this
may change).
Note that all switches must still go through the framework switcher;
the opt-in activity simply allows scorers to first show another screen
and perform the framework switch on their own terms.
Bug: 15775314
Change-Id: I3847e5d3161a8fcc9622abc03218795697c32778
/frameworks/base/core/tests/coretests/src/android/net/NetworkScorerAppManagerTest.java
|
| c741553644f8b19c63938ab9e36af1721c2cfa34 |
|
24-Jun-2014 |
Jeff Davidson <jpd@google.com> |
Use/expose the receiver's label as the scorer name.
Allows scorer apps to set a custom name for the scoring functionality,
even if the app has other non-scoring responsibilities, in which case
the application's label would be too generic.
Bug: 15775300
Change-Id: I61a7d1966742d463508e6801b7845ced8392db84
/frameworks/base/core/tests/coretests/src/android/net/NetworkScorerAppManagerTest.java
|
| 6a4b220f1263d95fdefe6361c2bc87bbb04bbed0 |
|
17-Apr-2014 |
Jeff Davidson <jpd@google.com> |
Initial implementation of NetworkScoreManager's backing service.
This service will ultimately be responsible for propagating scores
down to lower-level network subsystems. For now, it just keeps scores
in memory and exposes these for debugging purposes via "adb shell
dumpsys network_score".
This change also adds provisioning of a default scorer. When
NetworkScoreService is first initialized, it checks to see if it has
ever set a default scorer; if not, it reads a package name from a
build config property and attempts to set it as the default.
Also add autogenerated equals/hashCode methods to all parcelables.
Bug: 14111427
Bug: 13786258
Change-Id: I02271171653d42e12acd240b73b9e23950744f6b
/frameworks/base/core/tests/coretests/src/android/net/NetworkScorerAppManagerTest.java
|