Currently, devices that have a fingerprint prompt to add a fingerprint and
lockscreen via FingerprintActivity. However, since ScreenLockActivity is
always active, we end up with a second prompt for screen lock security.
This adds a check to see if a secure lockscreen has already been set, and
if so, just skip ScreenLockActivity.
Change-Id: I877835e8fa8628c01c96ab9732146720c1234f31
The material_light theme causes gms to crash with "Error inflating
class TextView" when attempting to do a device to device restore in
google suw. This change allows it to use the default glif_light.
Also removed the "Partner SUW Strings" comment, as the theme_type
was the only one.
Change-Id: I287f201799aba81c19869000e3aadb47ef67299b
The google suw flow has changed a little bit and added some new flow
choices in Pie, so our scripts need to be updated to match it. This
fixes the restore choice screen being shown twice.
Also reorganized the order of the wizard action results to move the
resultcode from the beginning to the end. This is a noop change that's
just to bring it inline with google's suw scripts.
Change-Id: Ia3ac9d1fdae62132c377e8ac2f767a795790d092
Google's suw handles the LOAD and NEXT actions, so this creates
duplicate tasks and crashes google suw when finish() is attempted.
Change-Id: Ifdbd9365fba7f299dc041e42ae27a91da071aa99
* Check if the value for the setting is already applied and do not
attempt to write it again. During the testing of SuW it was found out
that there can be an edgecase where softkeys don't show up neither
hardware keys work, even though the setting is applied (judging
by the status of the KeyDisabler switch).
Change-Id: I902f26fe131e508974116f7607fd0b88921395d9
* The only condition for "Use on screen navigation keys instead
of hardware keys" option to be shown is the availability
of KeyDisabler feature. There is really no need to check if the
device "needs" a software navbar (because it has no hardware keys).
Change-Id: Id716d766927f440292a6d18d8fa77bed76ad90b3
* Specify the user the broadcast will be sent to,
in order to avoid the warnings as seen in the logs:
W ContextImpl: Calling a method in the system process without a qualified user: android.app.ContextImpl.startService:1531 android.content.ContextWrapper.startService:664 org.lineageos.setupwizard.SetupWizardExitActivity.onCreate:53 android.app.Activity.performCreate:7136 android.app.Activity.performCreate:7127
Change-Id: I26a0b4ab2dc94bbe6eff065875901bf347aec85b
This change sets LOCAL_SDK_VERSION for all packages where
this is possible without breaking the build, and
LOCAL_PRIVATE_PLATFORM_APIS := true otherwise.
Setting one of these two will be made required soon, and this
is a change in preparation for that. Not setting LOCAL_SDK_VERSION
makes the app implicitly depend on the bootclasspath, which is
often not required. This change effectively makes depending on
private apis opt-in rather than opt-out.
Bug: 73535841
Change-Id: Iabb0556dc1c80c7fc7f6c76d61d5e441b03cdce0
* Common platform variant is no longer maintained.
Google advises to use common-gingerbread instead, so do it.
Change-Id: Icacb123c42a10f1813fc8189f3a6d01a86f0b0a1
* Remove unused imports
* Fix a few line length issues
* Convert a few anonymous classes to lambda expressions
* Convert a few global vars to locals
* Remove unused methods
* Add a small local method in MobileDataActivity to shorten repeated calls
Change-Id: Ia10be8b8c98ef3956949f913ddb6bddc185cf1a5
* Instead of resetting the wizard and relying on the call chain to disable
the SUW properly, call the finishSetupWizard method directly and step out
* Fixes: Upgrade 14.1 -> 15.1 without gapps looping
Change-Id: I1498a86b3c407aa32faa60c542003a1d596ce031
* We are currently passing a Boolean value while the
value should be a String ( null in our case )
Change-Id: I6bc69793485c44f2a65baeab62d7266934500038
Setupwraith from 8.0 no longer needs to be platform signed
This reverts commit e0605c03f4.
This reverts commit 092d0fa892.
Change-Id: Ic9801ee52d931e87b6568a1faa4de39b32c3629d
* Fixes:
W LineageSettings: Setting dev_force_show_navbar has moved from
LineageSettings.Secure to LineageSettings.Global, value is unchanged.
Change-Id: Id22886ea5767c6adf254618ecec84b338e11979b
Even though we disable this class when GMS is present, the
intent-filters are still active and cause an activity resolver
to be presented to the user. Disable export of this activity to
work around this.
Change-Id: I5888c71b5fdb95e59e15366b66f56e7968e51f1a
