Doesn't covers all possible apps nor makes sense as lot of
android core system apps are developed by Google. Users should
blacklist apps manually which they don't want to be updated instead.
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
They only apply to updates as we try to show all available apps in
installed and blacklist fragment to be clear about all possible apps
aurora store can check updates for.
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
* Show default device on top under different category
* Remove spoof configuration when default is selected
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
Merge updates checking logic into UpdateWorker and move trigger
methods to UpdateHelper class, similar to how DownloadHelper works.
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
* Always generate GSF ID on device regardless of login type
* Switch to new method for building AuthData
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
No need to check connectivity as soon as URL is set as SplashFragment will
only let you login when a valid connection is available.
Use a modern dialog and EditText to do set the URL with minimal verification.
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
Filters should persist for a single search only to ensure users can view all available
apps when starting a new search
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
We have multiple checks implemented at this point in splashFragment to ensure
proper validation and navigation. If a user logs out and hits back button, he still
gets to browse Aurora Store which is an unintended behaviour.
Instead of handling same logic twice everywhere, make AccountFragment minimal and only
handle logging out here.
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
We are not an expedited nor in foreground, no need to have foregroundInfo method
with an ongoing notification.
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
* This makes onboarding minimal and only required screens are shown
* SessionInstaller is the recommended choice, user who needs a different can configure in settings
* Instead of showing minimal list, show installer fragment that contains more information
* Also show all installers like before
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
SessionInstaller can commit silent installs if the app is device owner. Implemented on
request of users.
This still needs user to set the app as device owner manually using ADB (only possible
if the device has no accounts setup yet).
Co-authored-by: Syuugo <pub@s1204.me>
Signed-off-by: Aayush Gupta <aayushgupta219@gmail.com>
