This demos the phone-export scripts new in version 1.2--and more.

Export mode switches dataflow order (content moves from phone to
PC), but config-file settings work unchanged. 

Really, this is a comprehensive demo of the system in 1.2.  In
order, it runs the following on a small content folder:

    - An initial copy to the phone
    - A synch of 4 changes to the phone
    - A verify of the phone's content
    - An export of 4 more changes from phone back to PC  


TEST DETAILS

The PC here was a 2020 MacBook Pro running macOS Catalina, the phone
was a Galaxy Z Fold4 running Android 12L, and the proxy was a Samsung
T5 external SSD.  The 4 changes on both PC and phone were edits to 
two files, addition of a copied file, and deletion of the file copied.

The phone's content copy was located in Android shared storage, and 
it was zipped and unzipped in the same place by the scripts (though 
app storage is generally faster and preferred for zips).  Exports 
must zip phone content and ask for it to manually copied to proxy, 
because Python scripts cannot access USB directly in Android 11+.

The Termux wakelock was held for all phone-side scripts to keep
scripts running on screen blanks.  Though irrelevant for this demo,
this matters for larger content.  This lock is acquired and released
automatically by the Termux widget shims added to this package in 
version 1.0, and changed to background lock calls in 1.2.

This demo uses the same configs and test data as basic-shared-storage/
(copy this folder's configs, and restore them from configs-originals/).
Filenames were run through the fixer script during the initial-copy
step to make them portable; Android shared storage is restrictive.

This demo was run in command lines on both PC and phone (see runs/),
but scripts can also be launched by icons, shortcuts, and aliases on
PCs, and home-screen widgets and shortcuts on phones.  See the main 
_README.html usage guide for more info.


RESULTS SUMMARY

The runs here export phone content after it was processed by
an initial copy, on-PC changes, and on-phone changes.

All reported differences were valid: the 3 mixedmodes diffs reflect
3 symlinks, which cannot be stored in Android shared storage, morph
into simple stub files there, and overwrite symlinks on the PC on 
export - an unavoidable byproduct of symlinks' nonportability.
See CAUTION in the part 1 export script for more info, and use
Android app-private storage if you must care about symlinks.

For more fidelity, see the test content's starting and final states
in folder _content here.

The _etc folder also has results of a 1.2 Windows fix for too-long
paths.  This is unrelated to exports, yet could find no better home.