diff --git a/android/phoenix/res/layout/faq_games_are_slow_with_rewind_why.xml b/android/phoenix/res/layout/faq_games_are_slow_with_rewind_why.xml
deleted file mode 100644
index 74ed7b330c..0000000000
--- a/android/phoenix/res/layout/faq_games_are_slow_with_rewind_why.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-android:text="Enabling rewind will double the system requirements of a core (conservative ballpark figure here). It is NOT recommended that you turn on rewind with any core unless you know your device is capable of running said core at twice (or more) its full (realtime) speed.\n\n " />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_how_do_i_run_cave_story.xml b/android/phoenix/res/layout/faq_how_do_i_run_cave_story.xml
deleted file mode 100644
index ac0dd06c63..0000000000
--- a/android/phoenix/res/layout/faq_how_do_i_run_cave_story.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="NOTE: The original version of Cave Story/Doukutsu Monogatari was released as freeware back in 2004.\n\nGo to this repository: https://github.com/libretro/nxengine-libretro\n\nDownload the entire 'datafiles' directory there and copy it to your device. Select 'NXEngine (Cave Story)' from the 'Select a Libretro Core' screen and select 'doukutsu.exe' (this file should be in the root of the datafiles directory that you just copied over). On first boot-up it will extract needed files from the EXE file to disk - this will be a one-time procedure and will take slightly longer than all subsequent boots. After this is done you can play." />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_how_do_i_run_prboom.xml b/android/phoenix/res/layout/faq_how_do_i_run_prboom.xml
deleted file mode 100644
index a6d08b9efa..0000000000
--- a/android/phoenix/res/layout/faq_how_do_i_run_prboom.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="NOTE: To run Prboom, you need to load a Doom WAD file. However, to run any Doom WAD file with Prboom, you'll also need a special WAD file in that folder called prboom.wad\n\nGo to this repository: https://github.com/libretro/libretro-prboom\n\nCopy the prboom.wad file to your device and put it in the same directory as the Doom WAD you're trying to play." />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_neo_geo_game_doesnt_work.xml b/android/phoenix/res/layout/faq_neo_geo_game_doesnt_work.xml
deleted file mode 100644
index b94cc64df1..0000000000
--- a/android/phoenix/res/layout/faq_neo_geo_game_doesnt_work.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-android:text="Neo Geo games should be played with the Final Burn Alpha core. To run any Neo Geo games, you will need a BIOS file placed in the same directory as the game you want to play. The name of the BIOS file is 'neogeo.zip'. If it still doesn't work even with this BIOS file placed in the same directory, then either your ROM files are outdated or your Neo-Geo BIOS file is." />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_neo_geo_game_in_fba_shows_video_ram_err_why.xml b/android/phoenix/res/layout/faq_neo_geo_game_in_fba_shows_video_ram_err_why.xml
deleted file mode 100644
index 0bafbd49e8..0000000000
--- a/android/phoenix/res/layout/faq_neo_geo_game_in_fba_shows_video_ram_err_why.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-android:text="If Neo Geo games start up with a 'VIDEO RAM ERROR', then this indicates that rewind is enabled. Neo Geo games with the Final Burn Alpha core can't currently be played with rewind enabled. If you have the Rewinding option enabled, disable it in the Settings menu and then try the game again." />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_pce_cd_game_doesnt_work.xml b/android/phoenix/res/layout/faq_pce_cd_game_doesnt_work.xml
deleted file mode 100644
index 2e8a11ae93..0000000000
--- a/android/phoenix/res/layout/faq_pce_cd_game_doesnt_work.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="NOTE: To play PC Engine CD games, you will need a BIOS file called 'syscard3.pce' placed in the same directory as the game you want to play."/>
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_ps1_core_looks_bad_on_my_tegra_2_why.xml b/android/phoenix/res/layout/faq_ps1_core_looks_bad_on_my_tegra_2_why.xml
deleted file mode 100644
index 1286c4f0eb..0000000000
--- a/android/phoenix/res/layout/faq_ps1_core_looks_bad_on_my_tegra_2_why.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="Tegra 2 CPUs don't have NEON SIMD capabilities. Because of that, PCSX ReARMed will use an 'inferior' graphics plugin that doesn't look as good as the NEON GPU plugin. Nothing can be done about this other than get yourself a newer device so that you can enjoy the NEON version of PCSX ReARMed. Note - the NEON version of PCSX ReARMed is only shown in the list on devices that have a CPU with NEON support."
-        />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_ps1_game_doesnt_work.xml b/android/phoenix/res/layout/faq_ps1_game_doesnt_work.xml
deleted file mode 100644
index 510dfcc0bf..0000000000
--- a/android/phoenix/res/layout/faq_ps1_game_doesnt_work.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-android:text="If a game doesn't work with the PS1 emulator (PCSX ReARMed), you should be aware that there are two modes of operation -\n\n* HLE BIOS - If you do NOT have any BIOS files placed in the same directory as the game you're trying to load, then PCSX ReARMed will be in this mode. In this mode, you don't need a BIOS but game compatibility will be lower and some games will simply not play.\n\n* REAL BIOS - If you have BIOS files placed in the same directory as the game you're trying to load, then PCSX ReARMed will be in this mode. With a real BIOS, most games that previously didn't work before or had problems should work properly.\n\nNOTE: The BIOS files that it looks for are:\n\nscph1001.bin\n\nscph5500.bin\n\nscph5501.bin\n\nscph5502.bin\n\nscph7502.bin" />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_sega_cd_game_doesnt_work.xml b/android/phoenix/res/layout/faq_sega_cd_game_doesnt_work.xml
deleted file mode 100644
index 2eea4ee4a6..0000000000
--- a/android/phoenix/res/layout/faq_sega_cd_game_doesnt_work.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="NOTE: To play Sega CD/Mega CD games, you will need to have BIOS files placed in the same directory as the game you want to play. They should be named as follows:\n\n* bios_CD_E.bin\n\n* bios_CD_U.bin\n\n* bios_CD_J.bin\n\nIn case it needs any explaining, bios_CD_E.bin is the Mega CD EU BIOS, bios_CD_U.bin is the Sega CD US BIOS, and bios_CD_J.bin is the Mega CD Japanese BIOS."/>
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_sound_choppy.xml b/android/phoenix/res/layout/faq_sound_choppy.xml
deleted file mode 100644
index 2c8686fbb1..0000000000
--- a/android/phoenix/res/layout/faq_sound_choppy.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="There can be a couple of reasons for this:\n\na) Either your device is not powerful enough to run the core you've selected at fullspeed.\n\nb) The refresh rate of the screen that your device reports is wrong. More on b) below.\n\nc) Just turn on 'Threaded video' to save yourself all the trouble of trying to get static syncing to work right on your device.\n\n== REFRESH RATES AND RETROARCH ==\n\nUnlike other emulators, RetroArch does not use frameskipping. To get smooth gameplay and sound that are remotely close to the original hardware, RetroArch Android uses static synchronization. If you notice any skipping music or 'jerkiness' - rest assured it's not our code - it's likely that your device reports a wrong refreshrate to the OS (Android in this case). For instance, certain devices like the Note 2 have refresh rates below 60Hz.\n\nTo get any decent audio and video out of any application, you will have to synchronize the game's refresh rate with that of your screen - if the refresh rate cannot be properly synchronized, you will get bad audio pops and video glitchiness.\n\nThe problem is that a good many Android devices 'report' the wrong refresh rate to Android. The Samsung Galaxy S3 is known for doing this - it reports a 60Hz refresh rate when it isn't (the Note 2 for instance has a 58Hz screen but at least reports it correctly). So, because it 'reports' a wrong refresh rate, RetroArch will not yield good results.\n\nIf you experience any audio pops on cores that should be running fullspeed on your device, you should go with manual synchronization. To do this, you can start by calcuating your screens refresh rate with the 'Calibrate refresh rate' setting. This option can give a good guess, but for best results you should edit the value it returns in the 'Forced refresh rate (Hz)' option and set it manually - start at the value it returns and if it still audio pops/crackles, raise or lower the value (0.01 intervals is a good place to start) until you hit a sweet spot.\n\nIf you think  your device reports the correct value, you can use that instead by selecting the 'Set OS-reported refresh rate' option instead.\n\nWith a bit of experimentation you can get this right easily - I am running games on a single-core Cortex A8 device (1.2GHz - Allwinner A10) and I get no sound pops or any video glitchiness at all in most cores. So this is entirely a refresh rate issue that you can overcome easily on most devices by doing what I state above." />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_supported_pads.xml b/android/phoenix/res/layout/faq_supported_pads.xml
deleted file mode 100644
index 78e2880609..0000000000
--- a/android/phoenix/res/layout/faq_supported_pads.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="The following pads have been added to the autodetection list:\n\n* Logitech/Logicool Rumblepad 2\n* Microsoft Sidewinder USB (ISSUE - diagonals not working).\n* Microsoft Xbox 360 Wired/Wireless.\n* PS3 Sixaxis/DualShock 3 (using either USB or Dancingpixelstudios' IME app)\n* MOGA (using either 'root' gamepad mode or official IME app)\n* JXD S5110\n* Snakebyte idroid\n* Logitech Dual Action\n* Mayflash Super Joy Box 3 Pro\n* RetroUSB SNES RetroPort\n* RetroUSB NES RetroPad\n* Buffalo SNES Pad\n* Elecom PS1/PS2 to USB\n* Archos gamepad\n* Xbox 1 (Titanium X-Joy Converter) (ISSUE - diagonals not working).\n* Red Samurai (IME app Bluetooth or gamepad mode)\n* Xperia Play\n* Trust Raptor\n* Logitech F710\n* DragonRise USB\n* Madcatz PS3 fighting stick\n* iControlPad (HID joystick profile or SPP profile in tandem with Bluez IME)\n* iPega (gamepad mode, select it in iCade profile)\n* G910 (gamepad mode, select it in iCade profile)\n* PC2JAMMA-USB (TODO - TEST)\n* Genius MaxFire G-08XU\n* Zeemote Steelseries\n* Saitek Rumblepad\n* Super Smart Joy\n* Groupwise PS2 to USB converter\n* Toodles 2008 Chimp\n* Sega Saturn USB pad\n* Mayflash Wii Classic\n* Mayflash PS2 to USB\n* Nintendo Wii (using ccpcreations.WiiUse IME app)\n* Nyko Playpad Pro\n*Nvidia Shield" />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_what_is_a_libretro_core.xml b/android/phoenix/res/layout/faq_what_is_a_libretro_core.xml
deleted file mode 100644
index 07a218e6b7..0000000000
--- a/android/phoenix/res/layout/faq_what_is_a_libretro_core.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="In layman's terms, a 'Libretro core' is something you use to either:\n\na) Play games meant for a specific 'simulated' system (i.e. an emulator)\n\nb) Play games meant for a specific game engine (ie. Doom [Prboom], Cave Story [NXEngine]).\n\nLibretro cores will not play any games by themselves - just like how a games console needs a DVD or a cartridge to play a game, so too does a Libretro core either need 'ROM files' or a 'CD ISO' image in order to play games with it." />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_where_are_the_games.xml b/android/phoenix/res/layout/faq_where_are_the_games.xml
deleted file mode 100644
index f888e8146d..0000000000
--- a/android/phoenix/res/layout/faq_where_are_the_games.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="RetroArch Android is not a 'game'. What it is, however, is an 'engine' that allows you to run emulators and game engines.\n\nEmulators can play games that were made for the systems the emulator tries to simulate. For example, a SNES emulator can play SNES games in the form of files that are commonly referred to as 'ROM images'.\n\nDue to legalese, RetroArch Android does NOT come with ROMs or copyrighted material of any kind. Said material must be provided by yourself. DO NOT REQUEST WHERE TO GET ROMS. ANY E-MAILS RE: ROM REQUESTS WILL BE IGNORED.\n\nGame engine ports allow you to play specific games - for instance, prBoom is a game engine for the DOOM games, while NX-Engine is a game engine that can play Cave Story. To play these games, you must often provide the original datafiles of the game or else they will not work. The instructions as to how to play these 'game engines' differ per core." />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_why_are_the_shaders_so_slow.xml b/android/phoenix/res/layout/faq_why_are_the_shaders_so_slow.xml
deleted file mode 100644
index 48055cf93c..0000000000
--- a/android/phoenix/res/layout/faq_why_are_the_shaders_so_slow.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="All these shaders came from the RetroArch versions on PlayStation3, Xbox 360 and PC. Compared to those systems, the GPUs in Android devices are very, very weak.\n\nThis problem will solve itself as Android devices will start getting more powerful GPUs."/>
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_why_does_prboom_have_no_music.xml b/android/phoenix/res/layout/faq_why_does_prboom_have_no_music.xml
deleted file mode 100644
index 54331db3a8..0000000000
--- a/android/phoenix/res/layout/faq_why_does_prboom_have_no_music.xml
+++ /dev/null
@@ -1,57 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="NOTE: Prboom only supports MP3 soundtracks right now. To have the game use MP3 files, the files must be correctly named and should be placed in the same directry as the WAD file.\n\nHere is a listing of the files that are looked for by Prboom when trying to playback music in-game.\n\n== FOR DOOM 1/ULTIMATE DOOM ==\n\ne1m1.mp3\n\ne1m2.mp3\n\ne1m3.mp3\n\ne1m4.mp3\n\ne1m5.mp3\n\ne1m6.mp3\n\ne1m7.mp3\n\ne1m8.mp3\n\ne1m9.mp3\n\n
-e2m1.mp3\n\n
-e2m2.mp3\n\n
-e2m3.mp3\n\n
-e2m4.mp3\n\n
-e2m5.mp3\n\n
-e2m6.mp3\n\n
-e2m7.mp3\n\n
-e2m8.mp3\n\n
-e2m9.mp3\n\n
-e3m1.mp3\n\n
-e3m2.mp3\n\n
-e3m3.mp3\n\n
-e3m4.mp3\n\n
-e3m5.mp3\n\n
-e3m6.mp3\n\n
-e3m7.mp3\n\n
-e3m8.mp3\n\n
-intermid1.mp3\n\n
-intro.mp3\n\n
-bunny.mp3\n\n
-victor.mp3\n\n
-\n\n
-== FOR DOOM 2 ==\n\n
-stalks.mp3\n\n
-runnin.mp3\n\n
-countd.mp3\n\n
-betwee.mp3
-doom.mp3\n\n
-the_da.mp3\n\n
-shawn.mp3\n\n
-ddtblu.mp3\n\n
-in_cit.mp3\n\n
-dead.mp3\n\n
-romero.mp3\n\n
-messag.mp3\n\n
-ampie.mp3\n\n
-tense.mp3\n\n
-openin.mp3\n\n
-evil.mp3\n\n
-ultima.mp3\n\n
-read_m.mp3\n\n
-dm2ttl.mp3\n\n
-dm2int.mp3"
-/>
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_why_doesnt_it_autodetect_my_gamepad.xml b/android/phoenix/res/layout/faq_why_doesnt_it_autodetect_my_gamepad.xml
deleted file mode 100644
index e107766193..0000000000
--- a/android/phoenix/res/layout/faq_why_doesnt_it_autodetect_my_gamepad.xml
+++ /dev/null
@@ -1,21 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="Most likely reason is that it hasn't been added yet to the autodetection list. You can help us out with this by doing the following steps:\n\n
-        1. Go back to the main menu, bring up the popup menu. Select 'Settings' and go to 'Input Settings'.\n\n
-        2. Make sure that 'Debug Input Reporting Enable' is disabled.\n\n
-        3. After that, start up a game with any emu (doesn't matter which). The first thing I need to know exactly is the message that appears when you first press a button on the pad. It should say something like -\n\n'HID %somename here%'\n\n
-        3b. IF 3 FAILS - Another way you can give us the name of the pad is to do 'adb logcat' on the commandline from your PC (or for developers, use Eclipse). Connect a USB/BT/whatever device and it should show something like this (example here with a Rumblepad 2:\n\nI/EventHub( 175): New device: id=6, fd=106, path='/dev/input/event2', name='Logitech Logitech RumblePad 2 USB', classes=0x80000141, configuration='', keyLayout='/system/usr/keylayout/Generic.kl', keyCharacterMap='/system/usr/keychars/Generic.kcm', builtinKeyboard=false\n\nI/InputReader( 175): Device added: id=6, name='Logitech Logitech RumblePad 2 USB', sources=0x01000511\n\n
-        4. (EXTRA STEP IN CASE YOU ARE USING A BLUETOOTH PAD) - Go to the main menu, bring up the Popup menu and click on 'Report IME'. Write down what it says in the dialog box. We will be needing this information from you.\n\n
-        4. Enable 'Debug Input Reporting Enable'.\n\n
-        5. The next few things I need to know is the keycode that each button on your pad will now report 'onscreen'. Every time you press a button, it will show you a message onscreen with the keycode for each button.\n\n
-        6. Send your results to libretro@gmail.com. MAKE SURE THAT YOU HAVE FOLLOWED ALL PREVIOUS STEPS. If you have provided all the information we need, somebody can then add it to the autodetection list.\n\nIn the meantime, in case your pad is not added yet to the autodetection list, you could try manually setting up controls. To do this, you will need to disable 'Configuration Autodetect' in Settings -> Input Settings." />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_why_doesnt_the_ps1_core_show_up_in_the_list.xml b/android/phoenix/res/layout/faq_why_doesnt_the_ps1_core_show_up_in_the_list.xml
deleted file mode 100644
index e24ef2f961..0000000000
--- a/android/phoenix/res/layout/faq_why_doesnt_the_ps1_core_show_up_in_the_list.xml
+++ /dev/null
@@ -1,14 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="If the PS1 emulator [PCSX ReARMed] does not show up in the Main Menu, then chances are that your Android device has an MIPS or x86-based CPU. PCSX ReARMed is exclusive to ARM-based Android devices (which happens to be the vast majority of all devices out)."
-        />
-</LinearLayout>
diff --git a/android/phoenix/res/layout/faq_why_is_gba_so_slow.xml b/android/phoenix/res/layout/faq_why_is_gba_so_slow.xml
deleted file mode 100644
index 8a603721ad..0000000000
--- a/android/phoenix/res/layout/faq_why_is_gba_so_slow.xml
+++ /dev/null
@@ -1,13 +0,0 @@
-<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
-    android:layout_width="match_parent"
-    android:layout_height="match_parent"
-    android:orientation="vertical" >
-
-
-    <TextView
-        android:id="@+id/textView1"
-        android:layout_width="match_parent"
-        android:layout_height="wrap_content"
-        android:layout_margin="40px"
-        android:text="VBA Next is an emulator that is based on VBA-M. This is a more accurate emulator than most, but it's also much slower. Unfortunately, while VBA Next seems to run very well even on a Nintendo Wii, it seems that as of this minute even medium heavyweight Android devices can't compete with a Nintendo Wii in terms of runtime performance." />
-</LinearLayout>
diff --git a/android/phoenix/res/xml/help.xml b/android/phoenix/res/xml/help.xml
deleted file mode 100644
index e3055543a0..0000000000
--- a/android/phoenix/res/xml/help.xml
+++ /dev/null
@@ -1,68 +0,0 @@
-<?xml version="1.0" encoding="utf-8"?>
-<PreferenceScreen xmlns:android="http://schemas.android.com/apk/res/android"
-    android:title="Help" >
-    <PreferenceScreen android:title="Where are the games?" >
-       <PreferenceCategory android:title="Where are the games?" android:layout="@layout/faq_where_are_the_games" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="What is a 'Libretro core'?" >
-       <PreferenceCategory android:title="What is a 'Libretro core'?" android:layout="@layout/faq_what_is_a_libretro_core" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="Why do games sound choppy on my device?" >
-       <PreferenceCategory android:title="Games sound choppy on my device?" android:layout="@layout/faq_sound_choppy" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="Why are the shaders so slow on my device?" >
-       <PreferenceCategory android:title="Why are the shader so slow on my device?" android:layout="@layout/faq_why_are_the_shaders_so_slow" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="Games are slow with rewind. Why?" >
-       <PreferenceCategory android:title="With rewind enabled, games are slow. Why?" android:layout="@layout/faq_games_are_slow_with_rewind_why" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="Why doesn't it autodetect my gamepad?" >
-       <PreferenceCategory android:title="Why doesn't it autodetect my gamepad?" android:layout="@layout/faq_why_doesnt_it_autodetect_my_gamepad" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="How do I run Prboom/DOOM?" >
-       <PreferenceCategory android:title="How do I run Prboom/DOOM?" android:layout="@layout/faq_how_do_i_run_prboom" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="How do I run NXEngine/Cave Story?" >
-       <PreferenceCategory android:title="How do I run NXEngine/Cave Story?" android:layout="@layout/faq_how_do_i_run_cave_story" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="Why does DOOM have no music?" >
-       <PreferenceCategory android:title="Why does DOOM have no music?" android:layout="@layout/faq_why_does_prboom_have_no_music" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="Why doesn't my Neo Geo game work in Final Burn Alpha?" >
-       <PreferenceCategory android:title="Why doesn't my PS1 game work?" android:layout="@layout/faq_neo_geo_game_doesnt_work" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="Neo Geo game in FBA shows Video RAM error. Why?" >
-       <PreferenceCategory android:title="Neo Geo game in FBA shows Video RAM error. Why?" android:layout="@layout/faq_neo_geo_game_in_fba_shows_video_ram_err_why" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="Why doesn't the PS1 core [PCSX ReARMed] show up in the list?" >
-       <PreferenceCategory android:title="Why doesn't the PS1 core [PCSX ReARMed] show up in the list?" android:layout="@layout/faq_why_doesnt_the_ps1_core_show_up_in_the_list" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="PS1 core looks bad on my Tegra 2, why?" >
-       <PreferenceCategory android:title="PS1 core looks bad on my Tegra 2, why?" android:layout="@layout/faq_ps1_core_looks_bad_on_my_tegra_2_why" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="Why doesn't my PS1 game work?" >
-       <PreferenceCategory android:title="Why doesn't my PS1 game work?" android:layout="@layout/faq_ps1_game_doesnt_work" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="Why doesn't my Sega CD game work?" >
-       <PreferenceCategory android:title="Why doesn't my Sega CD game work?" android:layout="@layout/faq_sega_cd_game_doesnt_work" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-    <PreferenceScreen android:title="Why is VBA Next/Game Boy Advance so slow compared to other emus ?" >
-       <PreferenceCategory android:title="Why is VBA Next/Game Boy Advance so slow compared to other emus?" android:layout="@layout/faq_why_is_gba_so_slow" >
-        </PreferenceCategory>
-    </PreferenceScreen>
-</PreferenceScreen>
diff --git a/android/phoenix/res/xml/input_preferences.xml b/android/phoenix/res/xml/input_preferences.xml
index 3aa031c2f5..1babd1cd83 100644
--- a/android/phoenix/res/xml/input_preferences.xml
+++ b/android/phoenix/res/xml/input_preferences.xml
@@ -28,9 +28,6 @@
             android:summary="@string/config_autodetect_desc"
             android:title="@string/enable"
             android:disableDependentsState="true" />
-        <PreferenceScreen android:title="@string/list_autodetected" >
-            <PreferenceCategory android:title="@string/autodetected_pads" android:layout="@layout/faq_supported_pads" />
-        </PreferenceScreen>
         <ListPreference
             android:entries="@array/icade_profiles"
             android:entryValues="@array/icade_profiles_values"
diff --git a/android/phoenix/res/xml/main_menu.xml b/android/phoenix/res/xml/main_menu.xml
index 355975ec98..f339f4316a 100644
--- a/android/phoenix/res/xml/main_menu.xml
+++ b/android/phoenix/res/xml/main_menu.xml
@@ -37,13 +37,6 @@
           android:targetPackage="com.retroarch" />
     </PreferenceScreen>
 
-    <!-- Help -->
-    <PreferenceScreen android:title="@string/help">
-       <intent
-          android:targetClass="com.retroarch.browser.HelpActivity"
-          android:targetPackage="com.retroarch" />
-    </PreferenceScreen>
-
     <!-- About -->
     <PreferenceScreen android:title="@string/about">
         <PreferenceCategory android:title="@string/websites">
diff --git a/android/phoenix/src/com/retroarch/browser/HelpActivity.java b/android/phoenix/src/com/retroarch/browser/HelpActivity.java
deleted file mode 100644
index 6791bd41f4..0000000000
--- a/android/phoenix/src/com/retroarch/browser/HelpActivity.java
+++ /dev/null
@@ -1,20 +0,0 @@
-package com.retroarch.browser;
-
-import com.retroarch.R;
-
-import android.os.Bundle;
-import android.preference.PreferenceActivity;
-import android.preference.PreferenceManager;
-
-/**
- * Basic {@link PreferenceActivity} responsible for displaying the help articles.
- */
-public final class HelpActivity extends PreferenceActivity {
-	@SuppressWarnings("deprecation")
-	@Override
-	public void onCreate(Bundle savedInstanceState) {
-		super.onCreate(savedInstanceState);
-		addPreferencesFromResource(R.xml.help);
-		PreferenceManager.setDefaultValues(this, R.xml.help, false);
-	}
-}
\ No newline at end of file