* Luxemburgish (lb) was accidentially mapped to "lu" for all of the
non-AOSP projects.
* Since the next sync will download "lb" now, just remove "lu"
Change-Id: I1911df5cec057fd61126109ecacd70f198d0decf
If an activity is re-created, its result launchers that were registered
during instantiation are not available, so register those in onCreate
instead and unregister in onDestroy.
Change-Id: I7fd2a61ddbb056e0bf761b6918dc371db8ddbe33
Make sure the prior activity (NetworkSetupActivity) knows that back was
pressed - as it must have been - when the user returns to it. Otherwise,
the wizard gets stuck on a "Just a sec" page forever.
Change-Id: I35f7a78c4decc13b9dee267bfaf195fb2241395d
windowShowWallpaper behaves unexpectedly with transitions as of 14 QPR3.
As a result, the changes of "Revamp outro animation" were causing the
transition into the final page of the wizard to instantaneously have
a transparent wallpaper background, even before the animation finished.
This was jarring and odd, so now we use a regular theme until we are
ready to start our animation, at which point we recreate the activity
with the EdgeToEdgeWallpaperBackground (windowShowWallpaper) theme
before running the animation.
Change-Id: Ib19918d7d2a615aff44a48066b17ec9d2f04bac6
* Rename or eliminate methods that could be easily confused for AOSP
methods due to the reuse of AOSP names.
* Separate out the handling of results for subactivites and for the
next action (intent), each using its own activity launcher and
callback.
* Add a StartDecoratedActivityForResult contract to ease the launching
of activities without the caller needing to add SUW-related extras.
Change-Id: Iffaba4c51b2c90c42b8b243874a62cdea9e0c793
Check the availability of biometrics when we need to know, waiting until
then to decide the presence of ScreenLockActivity, rather than checking
once during initialization and permanently disabling pages of the setup
wizard. Otherwise, a race condition may cause the system to report that
the hardware is unavailable, even though it will be ready when needed.
Reorder pages such that biometrics comes first, allowing screen lock
to act as the fallback.
Issue: calyxos#2544
Change-Id: I654ce25569b983035f1df453623c7a4acd54931d
When exiting, all activities are finished and therefore no longer in recents. For the work profile, we want users to be able to come back to it
Issue: calyxos#2020
Change-Id: Id236c193e5822568dc445ea561fe18a4664e73cc
* Properly allow the user to go backwards to prior to the SIM Missing
page, if it had ever appeared and then a SIM became available.
* Ignore the activity result. Wizard remains on SIM Missing page until
user chooses to leave or returns to wizard with SIM present.
Change-Id: I3edac6cbb03d76c66b04673d6104e98189ce365c
Currently, we hardcode TRANSITION_FADE_THROUGH because it is the default
as of now and it is also what Settings uses. It appears to match stock's
transition animations, too.
Issue: calyxos#1743
Change-Id: Iffe19e5b4fd552aab6c5a93bc3788a27b5eba00b
This matches the behaviour prior to the Lineage suw revamp on 21.
Setupwraith hooks things in a completely different manner to the mobile
gms suw. The Lineage suw should not run at all when atv gms is present,
but the apk still needs to be available should the tvsetup intent hooks
get implemented.
Change-Id: Ic4943e8fd55d30fbd2856dc5eadc5a0ce6282f29
Extend the current Ethernet connectivity validation to check
if network is active (can receive and send data).
Change-Id: I1017df7740000774acc713a419c8572ee4ea588f
NetworkCapabilities#hasCapability tests for the presence of a
capability, not of a transport. Use the proper method to fix the
Ethernet connectivity validation.
Change-Id: I7e1828cca420e9a84080ede51807ab12ec9eedcb
Do not let SetupWizard crash in case the WiFi service is not available,
which can happen in case of devkits without built-in WiFi support.
Change-Id: Iba72e941b5e4995e865c70cb6c2b6be9a721addc
Devices with a hardware back button, such as atv remotes, can press back
on the welcome screen and trigger a transition to a waiting screen then
back to welcome. This should not be allowed.
Change-Id: I2273d0d74fb1ef018074d4facc8e3793e7470f6f
* Intentionally not touching this for secondary users
so that it doesn't look different from the main user.
* We don't explicitly support that, but let's also not
go out of our way to break something like this.
Change-Id: I374b45feb7d6dd17e5d03d0f7fbaf6d9e22f1d55
