Fix bluetooth search result no-op
Bluetooth fragment was manually setting intent information, which meant that the result didn't fire an intent properly. This type of regression or mistake will be caught in the fix for b/77921040. Change-Id: I49f87f40acbfc3f74ea2e97835f2644d443169e2 Fixes: 80317645 Test: robotests
This commit is contained in:
@@ -109,17 +109,10 @@ public class BluetoothDashboardFragment extends DashboardFragment {
|
||||
final List<SearchIndexableRaw> result = new ArrayList<>();
|
||||
|
||||
// Add the activity title
|
||||
SearchIndexableRaw data = new SearchIndexableRaw(context);
|
||||
final SearchIndexableRaw data = new SearchIndexableRaw(context);
|
||||
data.title = context.getString(R.string.bluetooth_settings_title);
|
||||
data.screenTitle = context.getString(R.string.settings_label);
|
||||
data.screenTitle = context.getString(R.string.bluetooth_settings_title);
|
||||
data.keywords = context.getString(R.string.keywords_bluetooth_settings);
|
||||
data.intentTargetPackage = context.getPackageName();
|
||||
data.intentTargetClass = BluetoothDashboardFragment.class.getName();
|
||||
data.intentAction = new SubSettingLauncher(context)
|
||||
.setDestination(ScanningSettings.class.getName())
|
||||
.setSourceMetricsCategory(MetricsProto.MetricsEvent.BLUETOOTH_FRAGMENT)
|
||||
.toIntent()
|
||||
.getAction();
|
||||
data.key = KEY_BLUETOOTH_SCREEN;
|
||||
result.add(data);
|
||||
|
||||
|
Reference in New Issue
Block a user