* Right now, the user has to set the toggle on and off to actually get
the setting set to "off", since the underlying default value is "on"
* Make sure to send an "off" initially right at the beginning of SuW
Change-Id: Iec2fd05ea341351f3e6d4b195a1a385f9d88d4f7
(cherry picked from commit 29e77749c5)
The captive_portal_server setting is deprecated, and hard-wiring it as a
string is also probably a bad idea. Since it's deprecated, this code
will miss an override via the modern settings. This also hard-wired a
slightly different fallback than ConnectivityService, and simply
adjusting it here wouldn't stop that from happening again. It's best to
just use the privileged API for obtaining the proper value. The choice
of LOCAL_MAC_ADDRESS as the permission for this is a bit strange, but
that's what is required, probably because a better fit didn't exist.
Change-Id: I78d07d5ff96598cebf6d4ed032fe1516791836fe
* Generic, handles both face and fingerprint
* Works the same as before for fingerprint
* Works the same as fingerprint for face
* What else could one ask for?
Change-Id: I9ddd7b46548c8107239fdec457bbaae6b12876e6
We were using the SubBaseActivity class for two different kind of
activities:
(1) "Wrapper" activities, where we define an activity that on
start simply launches another one
(2) "Interactive" activities, where the user has to manually
trigger the start of the subactivity, or skip the step.
When the subactivity ends, only in case (1) we want to finish our
activity as well, since we wouldn't have anything to show.
Change-Id: I1a3ae51f6146ac32b5e7542d9a18b0b032efe144
Set slide animation by default and use it in all pages.
Fix wrong/missing slide animations on various transitions like WiFi
and the backup subpage.
Change-Id: I78c87f38eb615379d39c89b43a016ed2ffb98695
The current handling results in the followup activity to ignore it for
backtracks which means when going from Location -> LineageSettings -> Fingerprint
the move backwards from Fingerprint leads up in Location and not the expected
LineageSettings.
The custom handling is necessary to process the result in the Google SUW,
so it has been fixed to properly work now.
Change-Id: Ifae5dc8fda07b61bd0271da1d1589059ab40cd39
This sets the partner customization flag to allow adding hooks
later if necessary.
Change-Id: Ie8dcb0f2eae8916ef00f812ea85661c020dce53b
(cherry picked from commit 68b11675e1)
LOCATION_MODE_HIGH_ACCURACY, LOCATION_MODE_SENSORS_ONLY and
LOCATION_MODE_BATTERY_SAVING are deprecated.
Take one further step and refactor the entire logic to call
LocationManager#setLocationEnabledForUser(boolean, int) instead
of setting location mode and LocationManager#isLocationEnabled()
to check if location is enabled.
Change-Id: Ibe1930902f6bfff99eb2c2d852ab600620e25f08
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
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
* 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
