-
Notifications
You must be signed in to change notification settings - Fork 8
deprecated_flags
The following flags should not be used anymore and they might be removed at any time
Current state: deprecated
| flag | values | meaning | where to configure |
|---|---|---|---|
| EOS_GESTURES | can be unset, true or false
|
must be trueto enable gesture support for /e/ OS |
vendorsetup.sh |
note: Gesture support finally made it into /e/ OS so this flag is usually not required anymore.
- The current implementation is "just" a workaround and not a fix. When enabled TrebuchetQuickStep will be included as an activity recents provider as the /e/ launcher (BLISS) does not provide it. That means: when you enable this you will get Trebuchet as a Launcher in any case ON TOP of BLISS (i.e. you will have 2 Launchers in your ROM and get asked on very first start which to choose) - there is no way around it (yet). I mean sure.. there is a way: you can use another Launcher as your default launcher and use an overlay to set it hard-coded to that one but thats out of scope here and is too less flexible.
- The recents provider is implemented by an overlay which respects your home launcher. While BLISS will just work as well you could also install any other Launcher and it will work there as well.
- in order to use that flag you actually need to add this to your manifest:
<project path="packages/apps/Trebuchet" name="LineageOS/android_packages_apps_Trebuchet" remote="github" revision="lineage-<version>" />
Current state: deprecated
| flag | values | meaning | where to configure |
|---|---|---|---|
| EXTENDROM_SIGN_ALL_APKS | can be unset, true or false
|
must be true to sign all EXTENDROM APK's with your own key |
vendorsetup.sh |
- if you do not care about security: no need for this flag
- if you do not build for a locked bootloader: no need for this flag
actually 999 of 1000 will not need/want to set this.
The only reason why you want to set this to true is VERY rare and only useful when building a custom OS which you want to complete lock down to limit users. When using this flag a user cannot update any of the extendrom packages set without a new version of your OS. This can be seen as a security feature (or the opposite) as long as you provide regular OS upgrades including app updates (e.g. by OTA).
So this means: If you include F-Droid and want to update it it will be rejected as the signing keys are different.
So actually who wants to use that flag?
- when you are paranoid, your device running your custom OS has a locked bootloader and you want to prevent app updates of extendrom packages
- or you (just) do not want to allow any updates of pre-packaged APK's because ...?!
Requirements
when you enable this flag your own generated keys must be stored in the path user-keys/ and the key shared.x509.pem from within that directory will be used for all APK signing. This might change in the future to be more flexible but atm it works like that.l flags HAVE TO be exported (i.e. export <FLAG>=<value>) when using vendorsetup.sh