Split GettingStartedFragment and DevidFragment into separate pieces

This will allow DevidFragment to be reused in the About page.

Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
res: Move token source strings from arrays.xml to strings.xml

Putting the strings directly inside arrays.xml makes it harder to add or
remove entries[1], because if an out-of-date localized version of
arrays.xml is used, any missing entries will not appear at all.

[1] http://globalizer.wordpress.com/2010/01/18/android-string-arrays-and-localization/

Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
Refactor "About" page

Use string arrays instead of HTML, so it is easily translatable.  Create
new MarkupFragment to construct new views from the string array.  Create
new BareActivity to easily instantiate one or more fragments via XML.
Add DevidFragment to About page, so the user still has a way to copy/email
his device ID outside of the GettingStarted screen.

Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
Replace FragActivity/HelpFragment with BareActivity/MarkupFragment

This eliminates some redundant code.  The Help screen is still blank
(for now).

Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
Initial commit of Help text

Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
Move Help/About info out of arrays.xml

Make it easier to maintain the help/about text, by doing the following:

 - Eliminate the list of strings in arrays.xml.  Instead, use reflection
to make a list of help/about strings from strings.xml, then sort the
list and display every string present.

 - Change to "about_text_000" format.  This makes it easier to insert new
lines in the middle without renumbering everything (and breaking every
translation).

Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
ImportActivity: Add support for content:// URIs from email

SDTID email attachments might show up as content:// instead of file://.
Use the same code to handle both.

Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
Initial commit of SettingsFragment

The save_pin and fg_service settings are both present, but are currently
no-ops.

Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
Implement save_pin preference

Forget all existing PINs if unchecked.  If checked, the PIN will be saved
the NEXT time it is entered by the user (i.e. PINs cached in memory will
not be immediately saved).

Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
Implement fg_service preference

Start/stop the foreground service in accordance with the preference
setting.

Signed-off-by: Kevin Cernekee <cernekee@gmail.com>