From 45478db795c29a0311a25ee18589f95396f4d8f0 Mon Sep 17 00:00:00 2001 From: Nick Alexander Date: Fri, 29 Aug 2014 11:51:46 -0700 Subject: [PATCH] Bug 1058160 - Make o.m.g.BrowserApp LAUNCHER activity default and high priority. r=bnicholson In order to launch in response to the MAIN activity (via |adb shell am start -a android.intent.action.MAIN org.mozilla.fennec|, for example), the activity must have category default. That is added automatically to elements that have category LAUNCHER, but apparently not to elements. This patch adds it manually. In general, are prioritized by their order in the manifest file. To avoid future confusion, this patch bumps the android:priority of the existing filter. --HG-- extra : rebase_source : 021da06af2f3e41fc0f38eee7fc33360797f64b0 --- mobile/android/base/AndroidManifest.xml.in | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/mobile/android/base/AndroidManifest.xml.in b/mobile/android/base/AndroidManifest.xml.in index 07e034934eb1..8a2a163d320c 100644 --- a/mobile/android/base/AndroidManifest.xml.in +++ b/mobile/android/base/AndroidManifest.xml.in @@ -129,10 +129,14 @@ - + + +