android: remove preferences menu item for now.

The preferences activity doesn't work, so easiest not to try to use
it until it is properly implemented.

Change-Id: I4b4195f6dcafa3c99dbef1ae3044ea18ab173c21
Don't keep the LibreOfficeKit pointer in a global variable

It is invalid in case lo_destroy() has been called.

Change-Id: I45533b66d32fc650e48748da8ea1d2f2aaa381e0
The 'bInitialized' state needs to be global, and unset in lo_destroy()

I assume, for lo_destroy() to be useful at all. Not that I know for sure what
the exact intended semantics of lo_destroy() and lo_initialize() are. But I
assume that the idea is that after lo_destroy() has been called,
lo_initialize() can be called again.

Change-Id: I2dea26db150d19ed438427e1c119a5297b9bc9c3
Call DetachCurrentThread() in the AndroidSalInstance destructor

As we call AttachCurrentThread() in the constructor, it seems logical to call
DetachCurrentThread() in the destructor. Some warning messages in the logcat
indicated that DetachCurrentThread() hadn't been called for a thread that
died.

Actually I would prefer to call both AttachCurrentThread() and
DetachCurrentThread() in the actual thread function, instead of somewhat
haphazardly and imlicitly in the AndroidSalInstance constructor and
destructor. Do we know for sure that the lifetime of the AndroidSalInstance
singleton (is is a singleton, right?) is 1:1 coupled to that of the LO "main
thread"?

Change-Id: Ifcc0e0b9af88b19389c416c5646499d44ad0e941
If loading a document fails, try restarting the 'main loop' and try again

Does not work, though, we end up with a crash that is hard to debug thanks to
the rubbish tool-chain.

Change-Id: Ie1954e35e649fac8dd106f0ccbc6951c4a6c1c63
Reduce log verbiage

Change-Id: I0da75df61d129aaaf03ac546fcf1e5dbcff9d404
Use maximum logging verbosity while attempting the restart

Change-Id: I3e3162474db1edef3b92e252b249fe373dedbbfd
Add a SAL_INFO

The "bootstrap" errors tend to end up being displayed in some error dialog
attempt which of course does nothing on mobile platforms, and that crack seems
to crash on Android even, so this should give us some chance to get some idea
at least what the code thinks is wrong...

Change-Id: I070b017baf042ff692766d1efd1511e1addb6ecf
android: Stopgap: _exit() is better than a hang

Change-Id: Iaada020e85a8d2557e270f7d1514f2260ffb2af0
Log time since object creation, not since epoch

Change-Id: I43c7725b88c9326e269abc277f42e47c08acefb5
Cosmetics

Change-Id: I4d819f59ecb2462aee5998628ad034657bf3b0f9
Bin duplicates

Change-Id: Ie6347ed6b9c1b8bee7a08950d5c67d4a2039fba5
SAL_INFO how long parseXcsXcuLayer() and parseResLayer() took

Change-Id: I1e71b8a6348301cd5b3fed0ae8b3346ae3e07d8e
Log parsing time of each xcd file

Change-Id: I290e2c84b17b9b5063139c6027b72f6cd3a78a99
Try to be less eager

Change-Id: I83a395c628b00b6ca96c93d5d5362ea750e57b2b
Add (commented-out) invocation of mobile-config.py

Change-Id: I379601099bda928b9eeeaeb29030bc009e3cbbf2
Beware of modifying a list being iterated

Change-Id: Ib9cf1a47eb20bd28d954ddcded89f67cf6865f1c
Ignore exceptions when getting the background color configuration

We are experimenting with a pruned configuration database in the desktop case,
and letting the exception propagate here killed the document loading.

Change-Id: I59e5d016617c17c2bc36de2fd69c6691bfa6b135
Avoid automatic toolbars in the non-desktop case

Change-Id: I9e5bff735b0035c147e10ae066da3a4873d66749
Don't prune org.openoffice.Office/UI

It apparently contains color schemes and stuff that the code wants access to
here and there.

Change-Id: Ie3f0de5e3846df99a02a2693156679cc6c010d10