Exclusively use qualified activities to launch apps

Do not use the `monkey` to launch apps anymore, the tool became too
verbose on Android 9 without a quiet flag.  Instead the apps are now
launched through their qualified activities, always.

Also cater for the Activity Manager verbosely warning us about
apps being already active and only brought to the foreground.

Issue: INFRA-169
Change-Id: I62b311a9163e8a8e7cda509df7961d3da8ca6c1b
1 file changed
tree: 1cf7f45d011bbefeabf1a0e1ae30816e3ce8727d
  1. settings/
  2. .gitignore
  3. .pre-commit-config.yaml
  4. deploy.py
  5. README.md
  6. requirements-dev.txt
  7. requirements.txt
  8. setup.py
README.md

SmartViser deployment

Deployment script to install and configure the SmartViser solution on devices.

Prerequisite

  • Python 3.6+

Install the required dependencies in a virtual environment:

% python3 -mvenv venv
% . ./venv/bin/activate
(venv) % pip install -r requirements.txt

Installing SmartViser on a Device

Follow instructions at https://gitlab.fairphone.software/fp/wiki/wikis/fp2/m/gms/sanity#prepare-a-device

Running Scenarios

Follow (and potentially adapt) instructions on how to run sanity check at https://gitlab.fairphone.software/fp/wiki/wikis/fp2/m/gms/sanity#run-the-sanity-check

Development

Install the pre-commit hook to setup the toolchain:

(venv) % pip install -r requirements-dev.txt
(venv) % pre-commit install

The toolchain can be run independently of the hook. On the staged changes only:

(venv) % pre-commit run

Or on all files:

(venv) % pre-commit run --all-files

Requirements

To keep things simple, and avoid installing extra software, this repository relies on standard Python tools (pip and the venv module).

The abstract dependencies are specified in setup.py while the actual dependencies (i.e. the required and transitive dependencies) are pinned in dedicated requirements files. This ensures reproducibility.