Another flow which I had to strip before publishing: It records package mutations, resulting from installing, uninstalling and updating packages. It can also display those recorded mutations.
One line per package/event is written, containing time when mutations took place, type of mutation, name of application. Once a day, a seperating day line is written.
types of mutation shown are:
+ (app installed)
- (app removed)
^ (app updated)
To be able to show app names of removed apps, rather than the package name, its own package name to app name base is maintained. It will be populated only with newly installed or updated apps. For already installed apps which are getting removed, no app names will be known, and the package names will be recorded instead, unless you're willing to populate that base yourself (a shell script would do).
path of the directory, and name of file recorded to, are specified in the first expression condition. file should reside in the directory specified there, otherwise exception based directory creation will get confused.
The parts removed from the flow pertain mostly to NAS storage, depending on additional support, like rsync, custom ethernet MAC for WoL, RSA keys, geolocation and hardlinking files to a directory on a volume supporting hard links, altogether too environment specific for publishing, What remains is supposed to run without any of those dependencies.
The flow provides multiple triggers. Bind the shortcut trigger to a gesture or launcher object of your choice. Nothing will be displayed before an arbitrary package mutation has taken place.
http://automagic4android.com/flow.php?i ... 21d9f125f8
package mutation listing
Moderator: Martin