yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I looked into the log file and I see the ZoomBar touches are recognised:

2009-12-29 06:15:04 1840878374 SetCapacativeGesture(): Capacitive Touch Middle

...

2009-12-29 06:15:04 1840878374 SetCapacativeGesture(): Capacitive Touch Middle

...

2009-12-29 06:15:06 1840878374 SetCapacativeGesture(): Capacitive Touch Middle

...

2009-12-29 06:15:07 1840878374 UnlockRequest()

However, looking into my code, I do not see in the logging:

UNLOCK BY CAPACITIVE SENSOR

So I expect it is unlocked by the ZoomBar swipe and not by the Triple touch.

Hmmm, you did also set:

2009-12-29 06:14:33 1297194942 GetSetRegValue(): CapacitiveToggleTime

2009-12-29 06:14:33 1297194942 ==DEFAULT VALUE====: 3000

2009-12-29 06:14:33 1297194942 ==OVERRULED VALUE==: 0

So, it means it will never unlock via triple touching the Zoombar :rolleyes:

You can just keep it at the default 3000, so you can also unlock by triple touching the Zoombar.

However, I did not see an incoming call in the log file, so I cannot see what is going wrong there. Did you try an incoming call, part of the log file? If yes, that could be the problem, because I did not see that in the logging.

In the log file I also see only:

2009-12-29 06:17:50 1297194942 LockWhenIncomingKeysOnly: 0

So at least in the log file, it will not lock the keys only at incoming call.

Note that for the ZoomBar to unlock you need a swipe left or right big enough (currently 10), so if the swipe is not wide enough, it will also not unlock. Maybe that is why it does not always recognise the ZoomBar swipes :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] piannetta:
Yes, I did receive a call during the log time. I have done it again and resent the logfile for your perusal. Very odd. The call was received at 9:16am.

What's also odd is this setting you say I have set to zero. I'm not aware of such a setting or that I have changed it, how do I set it back to the default value - I can't find it anywhere in the config menus?

I hope the new log file makes more sense.

Cheers,

Pete
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, so it looks like the TAPI commands are not recognised! Because it does not show up again in the log file. Normally there should be "CTAPIDevice" in the log file.

* Can you softreset/reboot the phone with debug enabled, so I can see if there goes something wrong at startup of TouchLockPro?

* Is there something changed with your ROM recently?

* Is version 2.8.2 showing CTAPIDevice in the log file?

About the setting for the Capacitive NavSensor, you must not disable the "Use Nav Sensor", this will set "ToggleTime" back to 3000.
[Touch Diamond, MDA Compact IV Themes and Apps] piannetta:
I've reset the device and attached the updated log file. I'm using my stock ROM, not modified in any way. And I'm not sure about your last question...sorry.

Thanks for the tip on the Nav Sensor, it was disabled so I've re-enabled it. Thanks. Looking forward to your next reply...

Pete
[Touch Diamond, MDA Compact IV Themes and Apps] Slide:
Hi ZuinigeRijder,

can you make it possible to unlock the device (HTC Leo) with the Proximity Sensor?

That would be great!

Greeting

Slide
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, now I see TAPI debug messages.

2009-12-29 10:11:38 -339640354 CTAPIDevice::lineCallback()

2009-12-29 10:11:38 -339640354 LINE_APPNEWCALL=(0, 832D90, 2)

2009-12-29 10:11:38 -339640354 CTAPIDevice::lineCallback()

2009-12-29 10:11:38 -339640354 LINE_CALLSTATE=(10, 0, 0)

2009-12-29 10:11:38 -339640354 CTAPIDevice::lineCallback()

2009-12-29 10:11:38 -339640354 LINE_CALLSTATE=(200, 0, 0)

2009-12-29 10:11:38 -339640354 CTAPIDevice::lineCallback()

2009-12-29 10:11:38 -339640354 LINE_CALLSTATE=(100, 1, 0)

2009-12-29 10:11:38 -339640354 Bearer mode: 524288

2009-12-29 10:11:38 -339640354 Media mode: 16

2009-12-29 10:11:40 -339640354 CTAPIDevice::lineCallback()

2009-12-29 10:11:41 -339640354 LINE_DEVSPECIFIC=(107, 200, 0)

2009-12-29 10:11:44 -339640354 CTAPIDevice::lineCallback()

2009-12-29 10:11:44 -339640354 LINE_DEVSPECIFIC=(107, 100, 0)

I am not sure why the TAPI commands were not shown previously. I assume you did not soft-reset/reboot your phone already for a long time and in one way or another TouchLockPro did not get notified for incoming calls. But a mystery why.

I assume the setting KeysOnly (LockWhenIncomingKeyOnly = 1) works now at incoming call, so you can slide2answer to answer a call too. And did you try the tripple touch the ZoomBar to unlock? Because I saw that not in the log file.

It is not so wise to unlock the phone at incoming call, because you can accidently reject the call then. So I would advise the above setting.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately HTC is not so generous (like Samsung) exposing their API's.

So if someone knows the Proximity Sensor API, I am glad to hear, so then I can implement that. I will set it on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thinking about it, maybe there is a registry key, like the Stylus Sensor, because the Proximity Sensor of Samsung API just returns a boolean, I have read.

So exporting the registry with and without Proximity sensing and comparing the differences could give a clue. I do not have a Touch Pro2 (it has also a proximity sensor I read) or HD2 (HTC Leo), so if someone could try to figure this out. It is a wild guess of course, but worth to give a try.

By the way, this is the Samsung API:

bRetVal = SmiProximitySensorIsObjectNear(&bObjectIsNearby);
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Which brings up a good potential item for the wish list

You could do a lot more with the zoom bar, probably enough for its own settings page.

You could have an indicator that counts as you slide so you can have a visual confirmation of what the program is seeing. Probably on the BattClock.

With that in place you could set up a swipe unlock pattern like: 5, -2, 7, or just a simple 10 | -10 would make it work as it does now. Others may like 7 | -7 better. Others may like 12 | -12.

You could configure commands to be executed while locked or unlocked, however, you also would need to keep in mind that other programs, like Opera, will also be reacting to the swipes in their own way...

The possibilities keep growing

Do you think more options might be on their way for the zoombar?
[Touch Diamond, MDA Compact IV Themes and Apps] Slide:
Hi ZuinigeRijder,

this is the only entry in the Registry. (HD2)

Greeting

Slide
[Touch Diamond, MDA Compact IV Themes and Apps] piannetta:
Thanks ZuinigeRijder, I reset my device every night after it performs a backup.

I set the LockWhenIncomingKeyOnly = 1 and it now works in that I can slide to answer or reject (so I assume this is all I had to do in the first place - sorry about that!) but I'm still somewhat confused. I assume that if I didn't set this or the LockWhenIncoming variable that I should still have been able to answer calls by sliding or pressing a button, and yet that is still not the case. So whilst you've given me a workaround, I still feel that this feature isn't working as expected.

It helps me now, not sure if you want to investigate further the original "fault", but thanks so much for your help and support.

Cheers,

Pete
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
If you set LockWhenIncoming=0 that does not mean it should "unlock" when incoming, it just means it wont "lock" on incoming. Meaning if it is locked it will stay locked and if it is unlocked it will stay unlocked - basically it wont do anything if it is set to 0. So unless I misunderstand the expectation, this feature works as it should.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Cobaltikus correctly writes the expectation. This behaviour is also stated (at least I tried to describe it) in the documentation of the setting:

LockWhenIncoming (LockWhenIncoming = 0)

Default it will NOT lock when there is an incoming call, because the default setting AutoLockOnPowerOn = 1 avoids already accidently missed calls. If you do not want the additional behaviour that it will be always locked at an incoming call (even when the phone was still on), overrule this registry key with "LockWhenIncoming = 1"

To make it more clear:

- if you set AutoLockOnPowerOn = 0 and LockWhenIncoming = 0, it will not lock at inconing call (if it was not locked yet), but also no longer at power on

- if your phone is already on and have set LockWhenIncoming = 0, then it will NOT lock when there is an incoming call coming while screen is on and it was not locked already

There is currently no setting to unlock at incoming call, but you can configure Incoming (CommandCallIncoming = !UNLOCK). But I would not advise that, because you can press the buttons then and reject the call accidently. Therefore I advise KeysOnly (LockWhenIncomingKeyOnly = 1), when you have a slide2answer solution.

I will see if I can make the documentation more clear, to avoid the confusion. Sorry for the misunderstanding, English is not my native language ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Probably the moves are not accurate/precise enough, but maybe I can differenatiate between a short swipe and large swipe on the zoombar. In combination with swipe left and swipe right and in combination with ZoomBar touch, you can have then a ZoomBar sequence to couple commands too, e.g. likeyou can configure GSENSOR orinetation moves. I think about it and put it on the wish list,
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, is ProximityDetectStatus changing from 0 to 1 when you move something in front?

[HKEY_LOCAL_MACHINE\Software\HTC\Proximity]

"ProximityDetectStatus"=dword:00000000

"PSensorDebounceTime"=dword:000000AA

I do not know about the debounce time, does that change too? Or is it just a setting?
[Touch Diamond, MDA Compact IV Themes and Apps] Slide:
No unfortunately not :(

Greeting

Slide
[Touch Diamond, MDA Compact IV Themes and Apps] piannetta:
No apology needed and thanks for your help. I'm happy with how it works right now. I have got the !UNLOCK on Incoming set but this isn't working anyway. As I said, it's working as close to what I was hoping now. I'm good with that.

Cheers,

Pete
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Too bad luck. But....

This post is saying it IS changing for TP2.

So possibly ProximitySensorOn should be set to 1? Or a program started that enabled the Proximity Sensor :confused:

This post contains a cab file for enabling the Proximity Sensor for TP2.. Do not know what it does, so I asked for that in that Thread.

PSensorDebounceTime is not mentioned, though.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Happy New Year with a *NEW* TouchLockPro version 2.10 supporting Samsung SDK

:) Happy New Year :)​

I made a new version of TouchLockPro, which supports now also a large number of Samsung phones having a Light Sensor and GSensor:

SGH-i900 Omnia

SCH-i910 Omnia

GT-I8000 Omnia 2

SCH-m490/m495 T*Omnia

Omnia Pro

GT-B7620 Armani

GT-I8000 Omnia II

SCH-i920 Omnia II

Note that I do not own a Samsung, so I could not test myself. I only tested that the non-Samsung users are not affected by the (small) changes and reviewed my own changes as good as possible. I hope that Samsung users can confirm it is working :cool:

Samsung made it difficult for developers, having different SDK redistributables for different phones and Windows Mobile 6.1 or 6.5. TouchLockPro supports both Samsung SDK redistributables. See Downloads for the Samsung SDK redistirbutables. Of course those need only be installed by people having an appropriate Samsung PhoneType.

People interesting in the Samsung API Specs and details of phones supported, see these documents under version control:

API-spec.2.1.0.pdf

API-spec1.2.1.pdf

Programming Guide.2.1.0.pdf

I have updated the TouchLockPro source code as such, that it is not needed to install the Samsung Windows Mobile SDK, if you want to compile TouchLockPro yourself.

Now hope this version is really working for Samsung users :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] tigro11:
You can have a MUI translated into Italian for this fantastic program?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am glad to add Italian, but I need help for that.

See this post how someone can provide translations.

Unfortunately, almost nobody contributed the Settings translations, only Russian is available and not complete at the moment. I myself did the Dutch language.

Note that the start TouchLockAction screen *IS* translated into much more languages (not sure if they all make sense, because I translated them mostly myself).
[Touch Diamond, MDA Compact IV Themes and Apps] tigro11:
I downloaded the sources in Iglesia, once implemented then what should I do to get the Italian?

Perhaps it would be easier to create MUI with different languages, then everyone if he wants if the translates.

Example italliano door as the name of the MUI 410 English 409, etc. ..
[Touch Diamond, MDA Compact IV Themes and Apps] tigro11:
sorry double post
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro is already Multiple Language UI, only the TouchLockAction start screen is translated in 32 different languages.

The easiest way is using the Resource editor approach. With the ResEditor you can open/save the resx files. See the latest language files in the attachment of this post. It also has the ResEditor.

Steps to do:

1. Start ResEditor and open a resx file to translate (File -> Open)

2. Scroll down to the bottom and only translate the String entries ending with .Text (the right part of the screen). Do not translate Strings starting with >> and do not add/rename entries.

3. Save the resx file

4. Do all the resx files

5. Post the translations as zipped attachment in this support group and also mention the language!

I will then update this in the next version
[Touch Diamond, MDA Compact IV Themes and Apps] seVen1O:
I cant get the touchlockaction.exe screen to display correctly on my omnia910 (240x400). The pngs are cutoff and none respond to touch. Once the screen comes up only a soft reset will get me back to my homescreen. I would like to comfigure the settings thru the GUI. Looks like a very handy app! Thanks for your Omnia support!

Any thoughts?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am busy in making a version which also supports lower resolutions. But that takes more test time.

Currently the Texts are also shown below the pngs in TouchLockAction. If you press on the Text, does it then not go further/respond?
[Touch Diamond, MDA Compact IV Themes and Apps] seVen1O:
I have tried to use the 4way directional to highlight the "settings" function (which works) but when i press to select nothing happens (no settings page displays) also no functionality of other features on touchlockaction.exe screen.

EDIT: When using 4way directional pad: there IS function of "lock" "suspend" "exit" and "reset" however the reaction is very sluggish! ("off" creates a program exception) i am also noticing that when the device gets locked by touchlockpro the default volume up/down action occasionaly responds to unlock. however this reaction is also VERY sluggish..(if/when it responds)

EDIT: DOWN then UP seems to respond instantly to unlock! (was previously trying UP then DOWN)
[Touch Diamond, MDA Compact IV Themes and Apps] tigro11:
I translated as much as possible in Italian
[Touch Diamond, MDA Compact IV Themes and Apps] abello00:
TLP won't start on my Touch Pro 2

I had it working for about 3 days. Then I power cycled the phone and now it doesn't work. It loads up because I see the Battclock Icon on the top right, however I cannot seem to get my device to lock. I tried pressing the power button (which used to work) and I also tried going to the TLP menu and tapping the Lock button with no success. I am running the stock rom with a couple of extra apps installed.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Someone else also had the problem the Settings screen did not react.

You can stop TouchLockPro via the Programs menu and with a registry editor (I use PHM Reg edit) and remove the key and subkeys:

HKCU\Software\ZuinigeRijder

Thereafter start again TouchLockPro and the default registry keys are made. Maybe that helps.

Note that there is a new version 2.10.1, which solves the problem that the Light Sensor was not working on the Omnia. See Downloads.

Indeed it is Volume DOWN and then UP to unlock. In normal cases, the light sensor should already unlock in the most cases, when there is enough light. Make sure to have version 2.10.1 though.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks, I will add the Italian translations in a next version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It will not lock when on (USB) power or when the Stylus is reported as OUT?

Maybe that is the cause?

You can enable debug logging (LogDebug=1), reproduce the problem and post the log file \TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
New version TouchLockPro 2.10.2

New version 2.10.2 is available with Itialian translations and some bugs solved and an extra feature to see when on (USB) power.
[Touch Diamond, MDA Compact IV Themes and Apps] TRoN_1:
Hi. Seems like a great app but I can't get it to install on my Omnia II i8000. I installed SDK Pro for wm 6.5(smi_wm_pro_sdk_redist_2_1_0.cab with Windows Mobile Pro 6.5) from your website. When I try to install TouchLockPro, it says it was unsuccessfull.
[Touch Diamond, MDA Compact IV Themes and Apps] seVen1O:
Thanks! that seems to have done the trick :)
[Touch Diamond, MDA Compact IV Themes and Apps] TRoN_1:
Anyone else have the same problem as me?
[Touch Diamond, MDA Compact IV Themes and Apps] abello00:
Not on AC power and Stylus was in. I also disabled the Gsensor, and the light Sensor as I only want to unlock via zoombar or stylus. The program randomly started working again today but gave me the same trouble after a soft reset and continues to not lock. This is the activity that I did after I enabled the log file:

- Enabled log file

- Performed soft reset (through the icon on the TLP menu)

- Waited until BattClock appeared

- Turned Screen off by tapping power button (this is where it should have locked)

- Turned Screen on by tapping power button (phone didn't lock)

- Connected to usb cable to extract log file

Thanks in advance for the help.

EDIT: Read next post as I believe I figured out the problem.
[Touch Diamond, MDA Compact IV Themes and Apps] abello00:
After going through the log file I noticed that it said that the stylus was out (even though it was in). I disabled the stylus sensor and this solved the problem. The lock now works exactly as it should. I am assuming that problem is in my phone and not your program since you are simply polling the device. Either way this is a great program and you are to be commended on your work.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There are 2 thing which can be wrong.

- If you soft reset with the Stylus out, HTC does not sense the Stylus correctly and will be reported as out

- The Stylus Sensor can be broken or there can be dust between the Stylus Sensor and the Stylus. For the latter you can take off the battery cover and blow away gently dust. Maybe then it will react again......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange that it does not install, I did not hear that from others. The installation of TouchLockPro is independent of the Samsung SDK, so this cannot be the problem.

Did you copy the CAB file to your phone or memory card and then executed it on the location you did install it? I assume you did.

In principle TouchLockPro can be installed on phone memory or memory card. Are both installations going wrong?

Maybe your provider or policy has disabled the possibility to install programs without certificate/signed application?

I can provide a folder with all the files, so you do not have install it, but just copy it to your memory. And then you can make a link in the startup folder to TouchLockPro.exe?
[Touch Diamond, MDA Compact IV Themes and Apps] AndrewASB:
TouchLock pro don't work on Acer neoTouch.

Can you add Acer neoTouch support?

Light ang G sensor detects but when I ends setup I have only prorosals to report about errors in MS.
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
Sometimes I have problems, screen turns off but do nothing.

I upload my log file
[Touch Diamond, MDA Compact IV Themes and Apps] creed:
Answer call button not locking

Hi, thanks for this great piece of software. It's near perfect for me except for one thing. I can't get the answer key to lock when receiving an incoming call. I would like it if the only way to answer a call is by using the slide to answer function on my HD2 but at the moment the answer key is still operable.

On the TAPI settings page I have selected LockWhenIncoming and KeysOnly. All the keys including the Reject/End Call button seem to be locked except for the answer call button. Any idea what's happening here? If I could just configure or fix this issue it would be perfect.

Thanks

Creed
[Touch Diamond, MDA Compact IV Themes and Apps] infantilo:
Great but leaking 6.5?

HI!

Touch lock pro is the best lock-tool i've ever seen. But since there are good roms for WM6.5.3 for my diamond there will be others than me, that would like to use it in WM6.5.3.

Installation works, but light-sensor always returns 0, g-sensor always return 7. Stylus and touch area (control field) are working fine.

is there any solution???? PLZZZZZZZZZ!

Thanka a lot!!!!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Is Acer neoTouch compatible with the Samsung SDK or with HTC type of phones :confused:

Or does it have own sensor API's :confused:

What errors are shown/reported in MS?

Note that TouchLockAction (part of TouchLockPro) is dependent of .NET 2.0, but is also compatible with newer .NET frameworks.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see several times !LOCKSUSPEND

e.g.

2009-12-27 01:15:42 607264694 SetCapacativeGesture(): Capacitive Gesture RightRight

2009-12-27 01:15:42 607264694 Execute(): !LOCKSUSPEND

...

2009-12-27 13:10:29 607991142 SetCapacativeGesture(): Capacitive Gesture RightLeft

2009-12-27 13:10:29 607991142 Execute(): !LOCKSUSPEND

....

2009-12-27 02:07:54 -963910562 = GSENSOR ORIENTATION MATCH =: 2 numberOk: 3 numbersequence: 5 orientation: 5 FaceDown

2009-12-27 02:07:54 -963910562 ==================COMMAND BY GSENSOR ORIENTATION==========================: 2

2009-12-27 02:07:54 -963910562 Execute(): !LOCKSUSPEND

2009-12-27 20:03:19 1681735570 = GSENSOR ORIENTATION MATCH =: 2 numberOk: 3 numbersequence: 5 orientation: 5 FaceDown

2009-12-27 20:03:19 1681735570 ==================COMMAND BY GSENSOR ORIENTATION==========================: 2

2009-12-27 20:03:19 1681735570 Execute(): !LOCKSUSPEND

2009-12-28 02:49:20 1681735570 = GSENSOR ORIENTATION MATCH =: 2 numberOk: 3 numbersequence: 5 orientation: 5 FaceDown

2009-12-28 02:49:20 1681735570 ==================COMMAND BY GSENSOR ORIENTATION==========================: 2

2009-12-28 02:49:20 1681735570 Execute(): !LOCKSUSPEND

...

2009-12-29 00:28:59 1681735570 = GSENSOR ORIENTATION MATCH =: 2 numberOk: 3 numbersequence: 5 orientation: 5 FaceDown

2009-12-29 00:28:59 1681735570 ==================COMMAND BY GSENSOR ORIENTATION==========================: 2

2009-12-29 00:28:59 1681735570 Execute(): !LOCKSUSPEND

I assume the capacitive swipes are on purpose :confused:, but the last 4 GSENSOR moves not. You can disable the !LOCKSUSPEND GSENSOR move in the GSENSOR Settings menu (or couple other commands to it), when you never want to locksuspend via the GSENSOR.