LightBlog

mercredi 27 septembre 2017

OnePlus is Seeking Feedback on Potentially Revamping the Alert Slider

For years, virtually all Android smartphones and tablets primarily handled their sound profiles via software. Sure, you could press and hold the volume down button until it triggers this sound profile, but that took more time or effort than the solution found on other platforms, namely the iPhone. Not unlike its fruity competitor, OnePlus decided to incorporate a piece of hardware that was dedicated to handling these sound profiles. It is now known as the alert slider, and the company is asking for feedback on how it is currently implemented, and what can be improved.

Over in the /r/OnePlus subreddit, an employee spoke about a comment they received from a OnePlus 5 owner. In said comment, the company received some constructive criticism about how OnePlus was using the alert slider. Some people in the community feel they only need two options (vibrate and silent) while others would rather it switch between ring, vibrate, and then total silence.

It’s definitely hard to please everyone with such a feature so they decided to reach out to the community and learn how most wanted the alert slider implemented. So, if you have a OnePlus smartphone or simply want to offer your thoughts and ideas, click through the source link below to take the survey that has been created using Google Forms. Your thoughts and ideas may help transform how the company is using the alert slider on their phones.

Interestingly enough, I remember that back when the OnePlus 3 and OnePlus 3T were being criticized for their “touch latency” issues, the company had said that they were working on it. And when it was fixed, a tweet from co-founder Carl Pei read “touch latency” with a checkmark next to it followed by “alert slider”, without such checkmark. So it’s possible that OnePlus has been discussing whether or not to adjust how the alert slider works since April of this year.


Source: Google Forms



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

Aucun commentaire:

Enregistrer un commentaire