Disable the start pane

mobile/android/base/BrowserApp.java

Index: mobile/android/base/BrowserApp.java
===================================================================
--- a/mobile/android/base/BrowserApp.java
+++ b/mobile/android/base/BrowserApp.java
@@ -622,6 +622,10 @@
      * @param intentAction Intent that launched this activity
      */
     private void checkStartPane(Context context, String intentAction) {
+        // We never want the start pane to show up in Adblock Browser.

[Felix Dahlke, 2015/03/01 12:00:50]

There are two places where we can keep the start pane from showing up - here
(where it's shown) and in GeckoProfile.java, where PREF_STARTPANE_ENABLED is
initialised.

I've opted for making the cut here, since it'll keep the pane from showing up no
matter what, and since I don't need to touch existing code here.

[René Jeschke, 2015/03/01 18:27:30]

I really don't like having dead code lying around, but if you really want to fix
it this way, we should file a follow-up issue to check if we can disable this by
modifying GeckoProfile only.
If so, modifying a single line instead of adding four might also be a 'minimal'
change.

[Felix Dahlke, 2015/03/02 03:46:59]

We can change it in GeckoProfile, as I said. But the change is more messy, we
need to modify existing code rather than add some new code above it, as we can
here.

We need to change this:

// Initialize pref flag for displaying the start pane for a new non-webapp
profile.
if (!mIsWebAppProfile) {
    final SharedPreferences prefs =
GeckoSharedPrefs.forProfile(mApplicationContext);
    prefs.edit().putBoolean(BrowserApp.PREF_STARTPANE_ENABLED, true).apply();
}

Into something like this:

// Initialize pref flag for displaying the start pane for a new non-webapp
profile.
// In Adblock Browser, however, we never want to see the start pane.
if (false && !mIsWebAppProfile) {
    final SharedPreferences prefs =
GeckoSharedPrefs.forProfile(mApplicationContext);
    prefs.edit().putBoolean(BrowserApp.PREF_STARTPANE_ENABLED, true).apply();
}

That's arguably more messy. Sure, we could also just remove the code,
effectively never setting startpane to enabled. But that's also a more intrusive
change.

+        if (true)
+            return;
+
         final StrictMode.ThreadPolicy savedPolicy = StrictMode.allowThreadDiskReads();
 
         try {