- 17 Dec, 2017 6 commits
- 16 Dec, 2017 1 commit
-
-
Max Lv authored
Implement direct boot awareness
-
- 15 Dec, 2017 7 commits
-
-
Mygod authored
-
Mygod authored
-
Mygod authored
-
Mygod authored
To do direct boot, important files need to be moved to device storage (i.e. not as safe storage). The only thing sensitive is user credentials (server settings in each profile) and the config file passed to libss-*.so. In order to implement direct boot, at least the active profile has to be moved/copied to device storage. This commit keeps profile information (and temporary data used by ProfileConfigFragment) and Shadowsocks config in credential storage and move everything else to device storage. In order to make direct boot work, active profile is also copied into device storage and Shadowsocks config file is created in device storage during direct boot. Cleanup of those information is also implemented. Fixes #1457. NB: * `android:directBootAware` can't be used on application element. That seems to be used by system apps. * Works fine with multi-user; * Old GSM files are not migrated (see App.kt) to device storage.
-
Mygod authored
-
Max Lv authored
-
Max Lv authored
-
- 14 Dec, 2017 12 commits
- 13 Dec, 2017 4 commits
- 11 Dec, 2017 1 commit
-
-
Max Lv authored
-
- 10 Dec, 2017 2 commits
- 09 Dec, 2017 5 commits
- 08 Dec, 2017 2 commits