Support and General Use > User Interface and Voice

[Fuze+] Option to restrict wakeup to hardware buttons

<< < (2/3) > >>

monoid:
That is probably true.  :(

But, the problem with the device reacting to any touch, and it reacts even if one does not touch it directly, is quite big. It wakes up if one aproach it sufficiently close. If one has it in a pocket of throusers, it may be on all the time.

I would like following setup if it is locked:
- no reaction to touchpad
- reaction to volume (the both switch on the display and change the volume) keys and on/off (short - switch on the display, long - unlock)

I understand, that normally volume keys should not work if the device is locked, but Fuze+ must be locked most of time (it is main operational state), otherwise it "randomly" react to any movement near by touchpad. So, I think in case of Fuze+ this diversion from "golden rule" has sort of sound roots.

halonachos117:
Perhaps there's more than one way to go about solving the issue. As it stands, users are given options as to how long the screen stays on when plugged in, or when unplugged. Perhaps one could add a two more options: how long to stay on when locked, while plugged in or unplugged. Users could set it to zero if they want, or they can set it to a maybe 5 seconds or so, just long enough to know the device is locked (as opposed to frozen).

[Saint]:
We already can do:

Backlight
Backlight (While Plugged In)
Backlight On Hold

If I understand you correctly you also want:

Backdrop On Hold (While Plugged In)

Is this correct? Having read, and re-read your post - I still can't say I'm too aware of what use this would be in determining if the device has hung or not. It is quite possible for the device to hang and leave some threads running, ie. backlight responsive, but UI locked.


[Saint]

blackshard83:

--- Quote from: gevaerts on March 20, 2013, 03:51:39 PM ---
--- Quote from: blackshard83 on March 20, 2013, 02:53:13 PM ---IMHO, when the player is locked, it should just be not responsive at all except for the unlock key.

--- End quote ---

This will confuse people and make them think the player has crashed.

--- End quote ---

Will it? I mean, on my sansa e250 if I set it on hold it just doesn't react to any physical key I push until I unhold it.
Also how could people think the player has crashed if music is (most probably)  playing? You can't even hold the player on any other screen except playback screen.

It would be nice if it could react on a simple touchpad gesture (for example, sliding top-to-bottom or left-to-right...), but not on random touch...

apolyonn:
In response to the original post, I don't think it would be a problem to have this as a user-defined option (probably not a good idea to be a default setting though).  So, the people who are aware of the touchpad-sensitivity issue will know that their player hasn't crashed.

Navigation

[0] Message Index

[#] Next page

[*] Previous page