Provide blank or transparent or hiding option for top status panel
I am trying to reduce the chance of unintended tapping a top row Locus button while performing a single wave gesture to toggle the display on & off. On my phone the IR proximity detection only works reliably with an object very close to the screen - close enough that a tap may also occur by accident. I have "given up" full screen mode as this places all buttons closer to the IR/ proximity sensor, and I have moved all my user defined buttons from the top to the right side. I then had to move all custom dashboard fields from (original) right side to left side. Of course, this results in wasted space, but I really want to use the single wave gesture control while cycling instead of having to press the tiny power button while wearing gloves. I don't need any info displayed in the top panel (screen cap below), for me it is wasted space, so my suggestion is to provide a 9th option in the list: blank or transparent, or alternate method to hide this auto-sizing panel completely.
I like this idea 
Some results with the Sony Xperia Z1 IR (proximity) sensor and Sony's own diagnostics app. Distance above IR sensor for detection of an object:
10mm is as close as
touching. When riding I can't "hover" my hand precisely & reliably 10mm above the
surface (to avoid tapping). Best I can do is briefly grip or rest hand on the top/ left corner near the sensor.
Some results with the Sony Xperia Z1 IR (proximity) sensor and Sony's own diagnostics app. Distance above IR sensor for detection of an object:
10mm is as close as
touching. When riding I can't "hover" my hand precisely & reliably 10mm above the
surface (to avoid tapping). Best I can do is briefly grip or rest hand on the top/ left corner near the sensor.
This video shows that sometimes gesture works, and sometimes it doesn't ;-(
This video shows that sometimes gesture works, and sometimes it doesn't ;-(
Hello Andrew,
I'm playing with Z1C device I have at home (expect it will use exactly same sensor as your Z1).
Agree that it do not work always on 100%. Wave is quite hard to detect sometimes. I personally found a lot better simply cover sensor with hand (not fingers). For "turn screen off" it works for me on 100%. Turn on seems to be worst, but here is not a problem to cover sensor completely without worry of touching.
So what is your problem here? In case you try to turn off screen, you also by accident tap on any button in top toolbar? Same happen when you use palm and just cover sensor?
Hello Andrew,
I'm playing with Z1C device I have at home (expect it will use exactly same sensor as your Z1).
Agree that it do not work always on 100%. Wave is quite hard to detect sometimes. I personally found a lot better simply cover sensor with hand (not fingers). For "turn screen off" it works for me on 100%. Turn on seems to be worst, but here is not a problem to cover sensor completely without worry of touching.
So what is your problem here? In case you try to turn off screen, you also by accident tap on any button in top toolbar? Same happen when you use palm and just cover sensor?
Hi Menion. In your testing are you riding a bike with gloves on? When the phone is just on the table it's not hard to just touch the correct part of the phone, of course. And a whole hand? More likely to accidentally tap the screen.
Until now while cycling I've used my right hand for the "wave" gesture. I just find it
easier taking right hand off handlebars. BUT it does cross over the screen
& I now see it increases chance of a false tap. So
tomorrow I will try & train myself to use my left hand. And rest my hand
on the top of my phone cradle just above the screen. Will see how it goes.
>you also by accident tap on any button in top toolbar?
YES! exactly the problem
So I've tried to move the virtual buttons further away from the IR sensor, as described (no full screen, move top buttons to right side), but it's also a waste of valuable screen space. One other possibility as described in the forum is to ignore any tap for short period after screen is turned on from gesture.
Hi Menion. In your testing are you riding a bike with gloves on? When the phone is just on the table it's not hard to just touch the correct part of the phone, of course. And a whole hand? More likely to accidentally tap the screen.
Until now while cycling I've used my right hand for the "wave" gesture. I just find it
easier taking right hand off handlebars. BUT it does cross over the screen
& I now see it increases chance of a false tap. So
tomorrow I will try & train myself to use my left hand. And rest my hand
on the top of my phone cradle just above the screen. Will see how it goes.
>you also by accident tap on any button in top toolbar?
YES! exactly the problem
So I've tried to move the virtual buttons further away from the IR sensor, as described (no full screen, move top buttons to right side), but it's also a waste of valuable screen space. One other possibility as described in the forum is to ignore any tap for short period after screen is turned on from gesture.
Andrew, (mobile now, so sorry for typos).
I was looking at that example video. As actual Locus Beta Proximity detection is by the trailing edge method I do think you are tapping too fast between 2 screen on/offf sessions.
I suppose such fast tapping sequence screen on/off session in real use only rarely would happen. No ?
By actual Beta 3.20.1.8 Locus test system you have to wait for at least 2 a 3 seconds between another screen switch action trigger to be performed succesfully.
Only if using that superior (IMO) more interactive faster method by the leading edge detection technique, such fast (test)sequences would be succesfull as well.
I've tested such very fast switches by leading trigger system in some example video's, already presented in some previous comments in Locus discussion forum.
But well, has only 3 views...anyway have a new look at this video, see the Locus map view from 00:30 to end = A fast enough screen switch on/off sequence I do suppose ;-) https://youtu.be/QiA38m6EEgs
Andrew, (mobile now, so sorry for typos).
I was looking at that example video. As actual Locus Beta Proximity detection is by the trailing edge method I do think you are tapping too fast between 2 screen on/offf sessions.
I suppose such fast tapping sequence screen on/off session in real use only rarely would happen. No ?
By actual Beta 3.20.1.8 Locus test system you have to wait for at least 2 a 3 seconds between another screen switch action trigger to be performed succesfully.
Only if using that superior (IMO) more interactive faster method by the leading edge detection technique, such fast (test)sequences would be succesfull as well.
I've tested such very fast switches by leading trigger system in some example video's, already presented in some previous comments in Locus discussion forum.
But well, has only 3 views...anyway have a new look at this video, see the Locus map view from 00:30 to end = A fast enough screen switch on/off sequence I do suppose ;-) https://youtu.be/QiA38m6EEgs
Hello,
hmm testing just home on a desk, as usually ;).
> YES! exactly the problem
Understand, but you suggestion with disabled touching for a while when screen is turned on, does no help here, because this accidental tap happen when you turn screen off, as I asked, right? Or this happen also when you use this gesture to turn screen on?
I'm really thinking about finding some usable solution for these cases ...
So generally ...
turning screen on
- is here any problem? Are you tapping any button by accident when you turn screen on by gesture?
Turning screen off:
here I can imagine, that some buttons are pressed by accident (like we talk here), solution should be:
- using button that allows to turn screen off: http://help.locusmap.eu/topic/add-power-off-button-on-screen
- using shorter timeout till screen goes off automatically, or by timeout defined in Locus itself
Hello,
hmm testing just home on a desk, as usually ;).
> YES! exactly the problem
Understand, but you suggestion with disabled touching for a while when screen is turned on, does no help here, because this accidental tap happen when you turn screen off, as I asked, right? Or this happen also when you use this gesture to turn screen on?
I'm really thinking about finding some usable solution for these cases ...
So generally ...
turning screen on
- is here any problem? Are you tapping any button by accident when you turn screen on by gesture?
Turning screen off:
here I can imagine, that some buttons are pressed by accident (like we talk here), solution should be:
- using button that allows to turn screen off: http://help.locusmap.eu/topic/add-power-off-button-on-screen
- using shorter timeout till screen goes off automatically, or by timeout defined in Locus itself
Replies have been locked on this page!