danascape / danascape/SetupWizard
Updaterecovery
Open
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
- In the UpdateRecoveryActivity, if a device doesn't support this, it properly skips the activity (invisible to the user), but when going back afterwards (from LineageSettingsActivity) , it just continuously loads until you go back once more. Seems like the activity is never actually disabled. Might look into it more later and push a fix, but figured I'd mention it here since other people are working on SUW at the moment.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing UpdateRecoveryActivity and its transition back from LineageSettingsActivity, focusing on how unsupported devices skip or disable the activity. Reproduce the return flow on an unsupported device and verify that it no longer loads indefinitely while the activity remains invisible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100