LightBlog

vendredi 4 août 2017

Touch Support is Coming to AOSP Recovery

If you frequent our forums, it's not very likely that you are too fond of the AOSP recovery. Indeed, we are often too quick to jump on our TWRP custom recovery in order to get our custom ROMs, kernels and mods up and running on our new device. However, it's still a very useful tool for anyone needing to get out of trouble.

Of course, it's still quite beneficial to use TWRP regardless of whether you have files to flash — the recovery itself is quite attractive, with design changes in recent years making it aesthetically pleasing and more functional. Custom recoveries like TWRP and the old CMW have also had touch support for a while,  allowing you to glide through folders and files (and confirmation sliders) with ease. Additionally, multiple OEM ROMs have included touch support in their custom recoveries as well. And, if your touchscreen is unresponsive, you can still use the volume and power keys to navigate through these interfaces.

Sadly, if you are just using one based on the AOSP recovery, you are confined to such keys whether you like it or not. Or at least for now, given a commit made to AOSP yesterday reveals that Google is adding touch support to the AOSP recovery. For now, we don't know why they are doing this so late in the game — it might be that they want to add more control options, or that they'll be adding more features that will better take advantage of touch controls, similarly to how TWRP handles confirmation prompts. Either way, it's nice to see that they are revisiting the good ol' recovery in AOSP for what look to be, at the very least, some quality-of-life improvements.

While most flashaholics will see no real need or use for these changes, it might also help mainstream customers who need to restore or reset their devices, yet are put off or confused by the outdated user interface and navigation scheme.


What do you think about touch support coming to AOSP recovery? Let us know in the comments!

Via: Android Police
Source: AOSP



from xda-developers http://ift.tt/2wfC3tM
via IFTTT

Aucun commentaire:

Enregistrer un commentaire