New Topic

Locus Map - help desk Topic Problem Locus Map (Android)

This object is in archive!

Category Locus Map (Android)

Tags Gesture control.

Comments 12

Subscribers 3

Votes 2

Gesture Proximity sensor Locus problem using THL phone.

0709 shared this problem ago

Not a Problem

Locus Set: Continuous screen on by Gesture by "config.cfg" edit.

Samsung Ace(1cm)/ Ace2(5cm). Android 2.3.6. Locus 3.5.3 (1 sec delay between 1 x wave and Screen action)

Screen On/Off Ok. Independent on settings. Location service on/off, GPS auto on/off, GPS fix or not. Perfect !

THL 4000(1cm). Android 4.4.2. Locus 3.7.1 (1 sec delay between 1x wave and Screen action expected).

Screen Off: Ok.

Screen On normal, if using GPS continuously On.

Screen On unreliable: When using function: "Disable GPS when screen turns off". Screen On delay sometimes several seconds. Probably system waits for GPS (fix?) before a Screen On action. User not observing wave confirmation by too long delayed Screen On time, mostly results in randomly waving over the sensor. ;-)

The same problem 0

Replies (3)

0709 ●

More info: It seems that a gps-(or no) fix is not the causing the problem. And to be 100% sure that proximity sensor is ok tested THL4000 using DTSO app.

https://play.google.com/store/apps/details?id=com.enlace.doubletap

Locus setup:

"As service" "Control by Gesture off". "Always Screen on". "Disable lock screen".

DTSO setup:

Wake: Proximity Unlock: Enable - Options: Flipcover mode: Disable - No of clicks to Unlock: 1

Sleep: Proximity Lock: Enable - Options: Unset Power Saving Mode - No of clicks to Lock: 1 - Lock immediately: Disable - Lock After: 2 sec.

Usage:

Screen on: Moving hand over proximity sensor: Screen On.

Screen off: Holding hand over proximity sensor for about 2 seconds: Screen Off.

Conclusion: Using Locus function "Disable gps when screen turns off" is no problem.

Willy.

URL

Menion ●

Hi 0709,

this will be harder. I'm checking code around gesture handling and there is no delay except small "wait" time till you finish gesture (around one second as you mentioned).

So few seconds delay will be probably some speciality of THL device. One what you may try, is to create for me a log. Maybe there will be any useful information from system, why there is so big delay.

Unfortunately I have no other idea, what I may do with this, when it is really basic function (from developer point of view) without any possibility to modify it.

URL

0709 ●

Report: After update (phone) retested locus gesture control on THl . OK !

Perfect !

URL

Menion ●

So issue was really in version of Android on your device? These news I like most, thank you :).

URL

Andrew Heard ●

I've had no luck getting this feature working. I really wish I could because then Locus would be completely "hands free" while I am cycling. The manual doesn't make much mention of this feature, just the obvious, so I would expect it is pretty simple to get going, but no. Not working on my phone or tablet, both KitKat 4.4. Someones, very rarely the screen turns on, but seems unrelated to any change in light level by waving my hand in front of light sensor. The GPS Status app shows the light level fine, so not a simple sensor issue. I note @0709 mention "Locus as a service", this made no difference, I've never had this setting enabled before. "ordinary" display on/off control in navigation mode works fine. Any other trouble shooting tips most appreciated. For example is this feature independent of all other Locus settings? I couldn't get the DSTO app working either, weird.

URL

Menion ●

I had also some problems with getting this working. Try another approach - just not a wave before sensor. Instead of this cover your sensor with your hand for a second and then move hand away. It works for me a lot better then waving ...

URL

Andrew Heard ●

Thanks but I had tried that too. All sorts of combinations. No luck.

FWIW using GPS Status the "lux" when covered is 0, and uncovered (room with 100W LED light, not sunlight) is 26 (Sony Xperia phone), and 36 (Samsung Galaxy Note tablet).

URL

Andrew Heard ●

Not sure if this helps at all. I installed a sensor test app on phone.

sensor uncovered:

b90a124db60d6dbd4f1b92bb92d2b4ce

sensor covered by hand:

6885ca6ce2effbe04b3a9e52a11f590c

The tablet doesn't have a proximity/ IR sensor. The Sensor Test app could determine this. If the Locus code relies on proximity (not light) sensor then a warning could be displayed if no IR sensor is detected.

URL

Andrew Heard ●

Thanks 0709 for pointing out the gesture control is handled by the phone IR sensor, not the light sensor.

Menion - on another ride today the screen turned on twice at random in 3 hours. Both related to gesture control I'm sure. What that told me is A) gesture control is possible (!) B) the IR sensor is enabled, not in some power saving mode when the display is off C) the problem I am experiencing is not related to some other conflicting app running eg. some power saving app. So this give me great hope for hands free operation.

After further testing it is clear the IR sensor only detects my hand when very close - eg. 2mm away. So when riding with gloves, you practically have to hold your hand over the sensor rather than just some friendly wave from afar. Often a close "wave" is impractical while bouncing along, you would hit the phone with you hand. After lots more practice I could get the display to turn on more often, but still quite unreliable. However turning off is totally reliable - just hold my hand over the sensor rather than wave. What exactly characterizes a single wave? What timing? So I have a few suggestions:

The detection algorithm either needs refinement, or I'd suggest a new simpler gesture - just hold hand over sensor until display turns on (Locus waits maybe 100ms for solid 0 value) - easier to perform when the gap is so small.
My tablet doesn't have an IR sensor; Locus should indicate that gesture control is not possible and why.
Provide some simple demonstration/ diagnostic on the setting screen so user can practice the chosen gesture - maybe a light globe icon - initially black, then temporarily red if turn on gesture is unsuccessful (bad timing of wave), and switch to white if 1st gesture is successful, black again if turn off gesture is successful etc.

Eventually the manual could provide more tips on getting this to work.

URL

Andrew Heard ●

Thanks again to 0709 for more suggestions. Results below...

The detection distance is consistent whether hand or glove, or other objects, yes about 3mm maximum. The value is consistent - 0 or 5, maybe using a little hardware hysteresis, so should be easy to detect a "gesture" because Sensor Test is totally reliable with the measured number, no noise in that signal during a gesture transition, very repeatable.

Using an ordinary camera I can easily observe when the proximity/IR LED is turned on.

When the phone is not running any app the IR Tx is turned off.
When I run Sensor Test the IR Tx is turned on until I close Sensor Test.
When I run Locus the IR Tx is turned on, and when Locus turns off the display IR Tx is still turned on, until I close Locus.

I cannot turn on the display using gesture control while sitting at my desk with just indoor lighting, it was only while outside yesterday with sunlight that I was able to demonstrate gesture control, and then still unreliable. Not sure of difference because Sensor Test shows the IR value as 0|5 whether inside or outside.

Unrelated to phone calls (some suggestions on other forums), I never use the phone for much calling, all testing is either at my office desk, or on bike mount.

URL

Menion ●

Hello Andrew,

thanks for a loooong test and description. Not sure if I can help here anyway.

Only what Locus do, is receiving values from Proximity sensor. And only values that Locus receive are two values from system : "FAR", "CLOSE". Nothing more!

So this whole magic behind proximity sensor is reduced to simple, "was there one FAR/CLOSE/FAR sequence during last 500 miliseconds or not"? (or "two" in case of two waves of course).

So I really do not know, how this may be improved.

URL

Andrew Heard ●

Thanks Menion. Looong test because 0709 had many ongoing suggestions over a number of days. Maybe my detailed tests help others with similar experience too because the manual doesn't help at present. Maybe my suggestion for some simple diagnostics inside Locus to help users get it working? Certainly the Sony diagnostics and IR camera tests are working so I don't know either.

URL