72 replies to this topic

[ZuinigeRijder]

nap_rz, on Jan 5 2010, 12:09, said:

...
now how do I use slide to answer?

  
You can lock only the keys at incoming call, so you can answer if you have a slide2answer solution on your phone.
TelephoneApi Setings screen:

KeysOnly (LockWhenIncomingKeyOnly = 1)

[nap_rz]

Snow02, on Jan 5 2010, 21:02, said:

I turned off the "In Call Tweak", because like you said, the prox sensor takes care of turning the screen off when it's close to your face already. It was kind of redundant, and locked the screen more than necessary, i.e. when away from my face.

thank you, I just tried it (turning off the in call tweak) but it still locked out my phone after the screen automatically turned off

and another thing, apparently I also had to unlock the phone first when I get incoming call after the screen turned off; and I currently don't have slide to answer kind of app is there an easy workaround for this?

Quote

You can lock only the keys at incoming call, so you can answer if you have a slide2answer solution on your phone.

no other solution if I haven't have slide2answer app yet?

and where can I find slide2answer because I cannot find it on xda.... anything other than slide2answer?



edit 2:

and I see this app does have somekind of slide2unlock using diamond (exclusive) capacitive nav panel

can you somehow make a substitution for that feature for other phones that don't have nav panel? for me, I'm not really a fan of pressing hardware button(s) everytime I want to unlock the phone since

a. I usually turned off the screen quickly after using the phone to save battery -and thus many times had to unlock the phone-
b. pressing hardware button(s) many times could damaging the button(s)

but I like this lock app since it's very small and resources friendly.




edit 3: sorry for this editing spams but I tend to forget posting things...

I have a suggestion, can this app somehow make the display back to today screen after wake up (and of course, after it being locked up)? or is there a way of doing that already?

Edited by nap_rz, 05 January 2010 - 02:32 PM.

[intrados]

Hello, i really like TouchLock pro. Thanks. Unfortunately I still have light sensor not  working on my omnia pro with version 2.10.2. the log is attached. Could you please investigate for me.
BRGRDS rado

Attached Files

•  touchlockpro.log.txt   231.27K   18 downloads

[ZuinigeRijder]

intrados, on Jan 5 2010, 23:29, said:

Hello, i really like TouchLock pro. Thanks. Unfortunately I still have light sensor not  working on my omnia pro with version 2.10.2. the log is attached. Could you please investigate for me.
BRGRDS rado

I see in the logging:
2010-01-06 00:10:28 -946456470 GetLightSensorValue skipped

That means that he light sensor could not be loaded.
I see GSENSOR detection. So that is apparently loaded correctly.

Can you make a log file from start, so enable debug logging and soft reset your device. Because there I can see maybe what is not going Ok (error messages).

[ZuinigeRijder]

nap_rz, on Jan 5 2010, 15:16, said:

thank you, I just tried it (turning off the in call tweak) but it still locked out my phone after the screen automatically turned off

TouchLockPro will not lock when connected and the screen goes off, but it will when the connection is finished.
Can you enable debug logging, soft reset the phone, reproduce the scenario and post the log file \TouchLockPro.log.txt, maybe that gives me a clue.

nap_rz, on Jan 5 2010, 15:16, said:

and another thing, apparently I also had to unlock the phone first when I get incoming call after the screen turned off; and I currently don't have slide to answer kind of app is there an easy workaround for this?


no other solution if I haven't have slide2answer app yet?

and where can I find slide2answer because I cannot find it on xda.... anything other than slide2answer?

  
I would expect in most of the cases it would just auto unlock via the light sensor. You can set the time shorter for the light unlock, default it is 1500, but many people can set it to 500. So out of your pocket it just unlocks in most cases. There maybe slide2answer solutions for the Omnia, I do not know.



  

nap_rz, on Jan 5 2010, 15:16, said:

edit 2:

and I see this app does have somekind of slide2unlock using diamond (exclusive) capacitive nav panel

can you somehow make a substitution for that feature for other phones that don't have nav panel? for me, I'm not really a fan of pressing hardware button(s) everytime I want to unlock the phone since

a. I usually turned off the screen quickly after using the phone to save battery -and thus many times had to unlock the phone-
b. pressing hardware button(s) many times could damaging the button(s)

but I like this lock app since it's very small and resources friendly.

The NavSensor is one of the sensors of the Diamond I exploit, also the ZoomBar for Diamond 2 and Touch Pro 2 users. These are not available on your phone type.
You can however configure an easier unlock GSENSOR move for unlock and one for lock.
Actually you can configure SensorLock like GSENSOR move, see this thread. The same GSENSOR move can be used for unlock and lock.

nap_rz, on Jan 5 2010, 15:16, said:

edit 3: sorry for this editing spams but I tend to forget posting things...

I have a suggestion, can this app somehow make the display back to today screen after wake up (and of course, after it being locked up)? or is there a way of doing that already?

A next version has this possibility. A lot of new features have been implemented already, BUT I need to do a lot of testing though.....

A peek preview of the expected/added features:

#  Stylus launcher
# Prevent errors from running 2 instances of TouchLockAction simulatenously
# 16 NavSensor swipes, 8 when locked, 8 when unlocked, doubling the possibilities
# 8 GSensor commands, 4 when locked, 4 when unlocked, doubling the possibilities
# Make TF3D Workaround work with *NEW* hardware key locking
# Made TouchLockAction also suitable for different resolutions (240x320, 240x240, 320x320, 480x480, 480x640)
# Automatically determine the BattClock settings dependent of the screen resolution, so it works also for other resolutions out of the box
# Possibility to Export/Import TouchLockPro settings in the About screen
# Automatically determine the BattClock colors, from Taskbar color and text color, so the right color is chosen the first time or after default settings
# Made Power off fallback, when PowerOffWarning.exe does not exist on phone, to be compatible with more phones
# Added !HOME command: add option to automatically go to the home screen when locked (Security)
# Added !UNLOCKSCREEN command
# Added !SOFTRESET command
# Added !POWEROFF command
# Added !UP command
# Added !DOWN command
# Added !LEFT command
# Added !RIGHT command
# SensorLock like GSensor move for lock/unlock
# Added Shake as GSensor orientation move (Shake to Lock/Unlock)
# Add notification icon possibility instead of BattClock
# Possibility to start a program at lock/unlock/poweron
# Setting backlight low when locked for saving extra battery
# Option to let TouchLockPro lock at boot/soft reset
# Possibility to lock at backlight off
# BattClock click action configurable
# More control over BattClock content
# Possibility that length of Stripe shows the battery percentage left
# Show in BattClock when an unlock KEY sequence is detected (like capacitive touch and GSensor orientation)
# Visual Stripe feedback when an unlock sequence is detected (key, capacitive touch, GSensor orientation)
# Exceptions list to not lock when some app is running and/or in foreground

[intrados]

ZuinigeRijder, on Jan 5 2010, 22:40, said:

I see in the logging:
2010-01-06 00:10:28 -946456470 GetLightSensorValue skipped

That means that he light sensor could not be loaded.
I see GSENSOR detection. So that is apparently loaded correctly.

Can you make a log file from start, so enable debug logging and soft reset your device. Because there I can see maybe what is not going Ok (error messages).

Hi thanks for prompt reply. Here is the updated log. I also have HTC sensor emulator activated.  Could this be a reason? I noticed in the SDK guide that version 2 is not supporting light sensor on B7610. The log file is also indicating it. Strange, might be for omnia pro B7610 separate api is available this phone has a light sensor.
Thanks in advance.

Attached Files

•  touchlockpro.log.txt   53.81K   29 downloads

[ZuinigeRijder]

intrados, on Jan 6 2010, 06:27, said:

Hi thanks for prompt reply. Here is the updated log. I also have HTC sensor emulator activated.  Could this be a reason? I noticed in the SDK guide that version 2 is not supporting light sensor on B7610. The log file is also indicating it. Strange, might be for omnia pro B7610 separate api is available this phone has a light sensor.
Thanks in advance.

Indeed the logging indicates the light sensor is not working:
2010-01-06 07:16:29 709326074 SamsungMobileSDK_2.dll loaded
2010-01-06 07:16:29 709326074 Samsung LightSensor API not supported: 2
Indeed the API doc of Samsung does not support the light sensor for omnia pro B7610. Strange, if it has a light sensor. Maybe the light sensor is not API compatible and therefore they left it out. Maybe you could ask on Samsung Mobile Innovator, why the light sensor is not supported for the Samsung SDK 2, while it has a light sensor.
Or does it NOT have a light sensor, but Proximity sensor only? Hmmm, is also not ticked in the API doc.

[nap_rz]

ZuinigeRijder, on Jan 6 2010, 05:56, said:

TouchLockPro will not lock when connected and the screen goes off, but it will when the connection is finished.
Can you enable debug logging, soft reset the phone, reproduce the scenario and post the log file \TouchLockPro.log.txt, maybe that gives me a clue.


  
I would expect in most of the cases it would just auto unlock via the light sensor. You can set the time shorter for the light unlock, default it is 1500, but many people can set it to 500. So out of your pocket it just unlocks in most cases. There maybe slide2answer solutions for the Omnia, I do not know.



  

The NavSensor is one of the sensors of the Diamond I exploit, also the ZoomBar for Diamond 2 and Touch Pro 2 users. These are not available on your phone type.
You can however configure an easier unlock GSENSOR move for unlock and one for lock.
Actually you can configure SensorLock like GSENSOR move, see this thread. The same GSENSOR move can be used for unlock and lock.

but here touchlockpro still locked my phone when the proximity sensor turned off the screen while I use the phone even when I set the in call tweak off

basically here is what I want with touchlockpro, can you guide me for the setting?

1. I want the phone locked after I turned off the sceen
2. I only want to use hardware button to unlock the phone, no light sensor, no gsensor
3. I want the phone not locked when I use the phone to call

that's all...how do I configure that?

[intrados]

ZuinigeRijder, on Jan 6 2010, 08:46, said:

Indeed the logging indicates the light sensor is not working:
2010-01-06 07:16:29 709326074 SamsungMobileSDK_2.dll loaded
2010-01-06 07:16:29 709326074 Samsung LightSensor API not supported: 2
Indeed the API doc of Samsung does not support the light sensor for omnia pro B7610. Strange, if it has a light sensor. Maybe the light sensor is not API compatible and therefore they left it out. Maybe you could ask on Samsung Mobile Innovator, why the light sensor is not supported for the Samsung SDK 2, while it has a light sensor.
Or does it NOT have a light sensor, but Proximity sensor only? Hmmm, is also not ticked in the API doc.

HI I have checked, but not clear answer when and why. The device has a sensor, but it is not supported. The only support for Omnia pro light sensor is available here : http://forum.xda-dev...ad.php?t=447119.
Hope that this works
BRGRDS
Rado

[ZuinigeRijder]

intrados, on Jan 6 2010, 15:48, said:

HI I have checked, but not clear answer when and why. The device has a sensor, but it is not supported. The only support for Omnia pro light sensor is available here : http://forum.xda-dev...ad.php?t=447119.
Hope that this works
BRGRDS
Rado

It is based on the HTC Sensor API. It has indeed another direct access to the light sensor. But I do not know if it works in that way.

Quote

It looks like the way this is done is by reading the backlight intensity value, rather than actually reading the light sensor. The Omnia sets the backlight value based on that reading.

Maybe you can try to find some program using this API in combination with the light sensor. I believe G-Light uses it.....
If that works, I can make a special setting to use this approach, instead of the Samsung SDK approach.....

[ZuinigeRijder]

nap_rz, on Jan 6 2010, 10:41, said:

but here touchlockpro still locked my phone when the proximity sensor turned off the screen while I use the phone even when I set the in call tweak off

basically here is what I want with touchlockpro, can you guide me for the setting?

1. I want the phone locked after I turned off the sceen
2. I only want to use hardware button to unlock the phone, no light sensor, no gsensor
3. I want the phone not locked when I use the phone to call

that's all...how do I configure that?

1. AutoLockOnPowerOn (AutoLockOnPowerOn = 1)
2. Disable Use Light Sensor and Use GSensor, default it can then be unlocked by Volume Down\Volume Up, but you can configure other key sequences (unfortunatley not the power button).
3. Default it should already not lock when a call is connected, if it does, you can enable debug logging, reproduce this scenario and post the debug log file \TouchLockPro.log.txt.

[letoubib]

nap_rz, on Jan 5 2010, 14:09, said:

help! I cannot unlock my phone after installing this program? pressing volume down up doesn't unlock it

how do I configure unlock mechanism? I tried the readme but it does not work?


edit2:

figured out how to unlock...

now how do I use slide to answer?

edit 3:

so here is another problem, my samsung dialer has screen off feature using proximity sensor, but then after I ended a conversation, the phone locked out I had to unlock it before I can end it and came back to today screen/last opened program

how can I 'fix' this?

How to unlock the device ???? the volume keys are not working ?????

[snikers]

I have problem with g-sensor in version 2.10.2. wm6.5, smi_wm_pro_sdk_redist_2_1_0.cab, and it say "0:unknown" I tried on 6.1 and it works fine.

Small question; is there a possibility to use a proximity sensor. It detect device in pocket and works in dark.

Edited by snikers, 11 January 2010 - 10:28 AM.

[ZuinigeRijder]

snikers, on Jan 11 2010, 11:16, said:

I have problem with g-sensor in version 2.10.2. wm6.5, smi_wm_pro_sdk_redist_2_1_0.cab, and it say "0:unknown" I tried on 6.1 and it works fine.

Small question; is there a possibility to use a proximity sensor. It detect device in pocket and works in dark.

TouchLockPro Version 2.10.3 is out, which fixes a problem with the phonetype. Make sure that the correct PhoneType is set in the TouchLockAction Index and do a soft reset thereafter. If it still does not solve your problem, please enable debug logging, reproduce the scenario and post the log file \TouchLockPro.log.txt as zipped attachment.

I was also searching for the proximity sensor API for HTC devices. On the newer Samsung devices the API is available, so I can add support for that. I will put it on the wish list.

[snikers]

ZuinigeRijder, on Jan 11 2010, 12:35, said:

TouchLockPro Version 2.10.3 is out, which fixes a problem with the phonetype. Make sure that the correct PhoneType is set in the TouchLockAction Index and do a soft reset thereafter. If it still does not solve your problem, please enable debug logging, reproduce the scenario and post the log file \TouchLockPro.log.txt as zipped attachment.

I was also searching for the proximity sensor API for HTC devices. On the newer Samsung devices the API is available, so I can add support for that. I will put it on the wish list.

I have installed 2.10.3 and it's the same - "0:unknown". The problem is only on WM6.5, on WM6.1 it's OK

Attached Files

•  touchlockpro.log.rar   7.8K   22 downloads

[snikers]

i've checked the log myself and i see
2010-01-11 13:46:55 1751077262 All orientation commands empty, disable GSENSOR
i add !unlock and i works

[ZuinigeRijder]

snikers, on Jan 11 2010, 16:34, said:

i've checked the log myself and i see
2010-01-11 13:46:55 1751077262 All orientation commands empty, disable GSENSOR
i add !unlock and i works

Ok, the code tries to be too smart and help people in configuring . Currently the GSENSOR is also used for InCallTweak, so there needs no GSENSOR command to be configured anymore.  So you can call it a bug I will remove that smart code in a next version.

But good to hear that the mystery is solved

[Nik1979]

Hi,

Has anyone tested light sensor for TouchLockPro successfully on B7610 with Windows Mobile 6.1?
I have installed the Samsung SDK and the latest version of TouchLockPro but the light sensor still doesnt work

cu
Niko

Attached Files

•  copy_of_touchlockpro.log.txt   37.08K   19 downloads

[ZuinigeRijder]

Nik1979, on Jan 11 2010, 21:28, said:

Hi,

Has anyone tested light sensor for TouchLockPro successfully on B7610 with Windows Mobile 6.1?
I have installed the Samsung SDK and the latest version of TouchLockPro but the light sensor still doesnt work

cu
Niko

See this post for details.

It is a mystery why Samsung does not support this on Windows Mobile 6.1.

[snikers]

hello, any progress about proximity sensor version?