Rockbox Technical Forums

Support and General Use => User Interface and Voice => Topic started by: Vkins on January 25, 2013, 04:30:30 AM

Title: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: Vkins on January 25, 2013, 04:30:30 AM
Hey. I didn't think this would fit in the dev thread, so I decided to post this in Support/General Use

First of all, great work on the build so far. It has some small issues but it's pretty stable nonetheless. Thanks!

Currently, the Fuze+ wakes up as soon as something touches anything. (Hardware buttons/touch pad)
The touch pad is very sensitive and responsive (which is a good thing) but it also causes some problems. The player wakes up very often when I'm carrying it around in my pocket since the pad even reacts to touches when there's a layer of fabric between skin and the pad.

Personally, I would like an option to restrict waking up to hardware buttons...what do you guys think? It'll probably increase the running time when the display isn't on so often.
Title: Re: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: wodz on January 25, 2013, 05:57:45 AM
IIRC there is soft lock function in WPS (It is associated with power button if I read keymap file right). This should do the trick.
Title: Re: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: Vkins on January 25, 2013, 08:55:50 AM
It indeed has a soft lock, but the display wakes up as soon as you touch the pad, even when the device is "locked". It turns on to display "Buttons Locked" or no message, depending on the Wake up setting.
Title: Re: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: blackshard83 on March 20, 2013, 01:53:13 PM
Hello all, new to the forum, but long time lurking.

I completely agree. The player should not show "Buttons locked" message on touchpad hitting, since it will turn on the screen even when it is soft-locked. IMHO, when the player is locked, it should just be not responsive at all except for the unlock key.
Title: Re: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: gevaerts on March 20, 2013, 02:51:39 PM
IMHO, when the player is locked, it should just be not responsive at all except for the unlock key.

This will confuse people and make them think the player has crashed.
Title: Re: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: monoid on March 20, 2013, 05:56:12 PM
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.
Title: Re: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: halonachos117 on March 24, 2013, 04:04:33 PM
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).
Title: Re: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: [Saint] on March 24, 2013, 05:07:55 PM
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]

Title: Re: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: blackshard83 on April 19, 2013, 02:40:24 PM
IMHO, when the player is locked, it should just be not responsive at all except for the unlock key.

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

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...
Title: Re: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: apolyonn on April 28, 2013, 08:53:37 PM
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.
Title: Re: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: lee321987 on May 02, 2013, 08:54:58 PM
Just want to say I would really like to see this lead to something.
There is no "Backlight On Hold" setting on the Fuze+!
Screen constantly turns on in my pocket while on hold.
Huge waste of battery.
Rockbox is awesome!
Title: Re: [Fuze+] Option to restrict wakeup to hardware buttons
Post by: Vkins on June 16, 2013, 08:00:30 AM
Just want to say I would really like to see this lead to something.
There is no "Backlight On Hold" setting on the Fuze+!
Screen constantly turns on in my pocket while on hold.
Huge waste of battery.
Rockbox is awesome!

I think the issue with that option is that the Fuze+ has no button which doesn't change its status when locked. The button hold thing only works for device that got a dedicated hardware slider assigned to the lock function. (Think Sansa e200 with it's slider on the top or the iPods.)

Some other thought I had was that it may be easier to simply set the brightness to 0 (similar to what iPods do) when the keylock is enabled. (Probably wait until the splash message disappears) When the power button is pressed again to release the keylock, LCD brightness is set to its original setting...