4ff5defa5328411035183b785a77db41778bc272 |
|
26-Jul-2017 |
Michal Karpinski <mkarpinski@google.com> |
Removing non-preferred activity from resolution set should not disrupt the preferred resolution We used to show disambiguation whenever the resolution set was different in any way from the preferred activity's one. Now we force disambiguation only when the new state isn't a preference-inclusive subset of the prior state. Test: manual, various scenarios with installing, uninstalling, reinstalling multiple launcher apps Bug: 38387746 Bug: 31955881 Change-Id: I60d963127bc2eb75340b47f2b54e9554549a921b
/frameworks/base/services/core/java/com/android/server/pm/PreferredComponent.java
|
57792912ee8f536f90c466db701d71a9e38c54d4 |
|
27-Jan-2015 |
Christopher Tate <ctate@google.com> |
Fix 'always' preferred app assignment In the case when some possible resolutions of a given intent are at different priorities (typically when they're intended as fallbacks when no "normal" handler for the intent exists) the check for "is this the same set of possible handlers that we saw last time?" was broken. We now ignore resolver priority entirely in that check: match set comparison should be orthogonal to prioritization within the set, and indeed the priority is dealt with separately in any event. Bug 19011225 Change-Id: I3c1658442cc88b1f4a5c5f2fe9f64472799e156c
/frameworks/base/services/core/java/com/android/server/pm/PreferredComponent.java
|
f2ac2761276e4972f6463d6818c9f5798bdc9a4d |
|
16-Aug-2014 |
Dianne Hackborn <hackbod@google.com> |
Fix issue #17082301: replacePreferredActivity is ignoring userId It was being given the argument and just... ignoring it. But the bulk of this change is to make replacePreferredActivity better about replacing -- it now detects if the request will not make a change and, in that case, just do nothing. The reason for this? It turns out that each time you install an app, the telephony system is calling this function over 20 times to set the default SMS app. This is almost always doing nothing, but before this change it means we would re-write packages.xml over 20 times...! There are definitely more improvements that can be made here (delaying write of packages.xml to allow them to batch together, reducing the amount of calls being made), but until then this is a big improvement. Change-Id: I02c4235b8ecd5c13ef53e65d13c7dc2223719cec
/frameworks/base/services/core/java/com/android/server/pm/PreferredComponent.java
|
9158825f9c41869689d6b1786d7c7aa8bdd524ce |
|
22-Nov-2013 |
Amith Yamasani <yamasani@google.com> |
Move some system services to separate directories Refactored the directory structure so that services can be optionally excluded. This is step 1. Will be followed by another change that makes it possible to remove services from the build. Change-Id: Ideacedfd34b5e213217ad3ff4ebb21c4a8e73f85
/frameworks/base/services/core/java/com/android/server/pm/PreferredComponent.java
|