Closed vasyugan closed 3 years ago
@fredldotme what do you think, what would be a good UX for that?
Here's how this looks in the wild #1071
Aargghh, if I just didn't miss the notifications. Alright, so the device unlock UX I'm not sure we can do easily without implementing a lot of things in the installer, so I would recommend hinting on the requirement in the device config, let that surface to the user in the installer UI and link them to a new forum thread I could set up specifically to guide the user.
I'm always a fan of automating as much as possible, if it's just a matter of passing the key for the oem-unlock, i'm happy to implement a UI for that. If you have ideas on how a note could look, could you send a PR to the config?
I noticed we already have a guide for TA backup, unlocking etc. on suzu's devices.ubuntu-touch.io page, we could show that one after showing the hint about the Android 8 requirement.
Manual downloads for flashing the oem partition are included in 0.5.6-beta. If someone wants to add it to the config files where it's needed, i'd be very appreciative. See the notes for developers on the release for usage documentation.
Opened #1479 to track those new-fangled unlock requirements. For the rest, i'll update the config accordingly.
the easiest way to add unlock code to the "fastboot oem unlock..." command is to ask in the UI and/or add an option in the config file, because there is already an option in the ubports-installer to view/edit the selected config file...
@robiwan1 we're going to have an ui, that's being tracked in #1479
At the moment, the installer is dysfunctional for suzu:
I think that therefore when the installer detects a locked bootloader it should stop and provide a link to the instructions, I have written them down here and I would think they should be on the device page, because that's obviously the place where you look first.