Wallet version was 1.35c at that time.

Are there any known issues with importing an Armory watching-only wallet to Android BTC wallets?
This would use the paper backup. I hope to be able to scan in the QRC. Any thoughts? Any recommendations on which Android wallet works the best?

There is a lengthy history behind this. Mostly Windows-related problems, the way it looks. I am not sure how much relevancy the details would have.
I have tried to upgrade Armory and bitcoin core on my old Windows systems - unsuccessfully. Syncing headers does not complete after launching bitcoin-qt

I also tried loading current versions of bitcoin core and Armory on a new Windows machine, used an external HD for the data directory. I ran into Windows permissions-related errors when trying to use the external drive to run bitcoin core on the PC and launch Armory to access the datadir.

In addition, I have a signed transaction from the last time I had Armory online. I was not connected to the network, though, so it was never broadcast. The file format is something besides HEX, although it does appear similar to HEX.

I have a file that I intended to send to the network. My bitcoin core was not synced at the time when I attempted it. The file format is not in a standard HEX format. How can I broadcast it to the network using the Armory SENT file?

listening on port 9001
after launching armorydb on external drive ( D: drive)

Afterward, I use - from this directory - D:\BTC datadir 96-2\Armory>
armoryqt -- datadir=d:\btc datadir 96-2\

This returns an error message referencing log file ArmoryQT.exe.log (on the d: drive)

===
See the logfile 'D:\armory 0.96.3.992\Armory\ArmoryQT.log' for details
===

My initial installation was on the C: drive, but I ran out of disk space. Added external drive, reinstalled and upgraded, and am trying to run the following on Windows 7 Home 64 bit:

online PC
armory 0.96.3.992

bitcoin core
0.14.2

Offline PC
Windows 7 Starter 32 bit

armory 0.92.3-beta

I'm thinking that I had this working 2.5 years ago. Checking file date and time stamps, it looks like log files have been changed on both drives. I have attempted to launch armory using executables and shortcuts on both drives.