yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the reaction.

Just to be sure, the capacitive touches will only react, when the BattClock has input focus, therefore it is recreated in the configured time.

Just make sure you have configured ClockLockActiveTime = 5000 or 4000, so it is recreated more regular.

But of course, it sounds like a bug in TouchLockPro.

I do not have this experience, but I do not get much incoming calls.

I am already busy with version 2.0, and the only thing I can think of now, is that the incoming call is coming before the power on event and/or the power on setting is set too early and that gives the problem. But because I could not reproduce, it is just a guess.

You can help, by enabling debug logging (logdebug=1 and logdebugdetailed=1) and post the logfile in the root of your phone memory \TouchLockPro.log.txt as zipped attachment, when it occurs again. Please make sure you write down the time when it occurred, so I can better analyze the log file.

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] hhspiny:
I changed the

ClockLockActiveTime to 3000 and enabled log, and will see if I can help trouble shooting it.
[Touch Diamond, MDA Compact IV Themes and Apps] yawpk:
ZuinigeRijder,

TLP v1.92 is good. Now with the sequence capacitive lock especially setting the last to touch the area 2 is fantastic on my touch pro. For a whole week testing, the TLP only unlocked itself 2 times accidentally in my pouch. This statistic is considerably better as compared to the v1.8. However the sensitivity at area 2 is not consistent and sometimes i do miss a call because i could not get it unlock in time.

To try to achieve 100% save from unlocking accidentally and unlocking for use, may i suggest to include a press key on area 2 (OK button) as a mechanism to unlock.

(1) to solve the delay in unlocking when incoming call, an option to unlock by pressing the "OK button" as an option to unlock (like unlock with stylus out), this can also be an option for people who do not like sequence unlocking mechanism. Only the capacitive panels can be touched and OK button can be pressed when the system waits up. Since my point of view comes from my touch pro in mind, the OK button on ohter pda may not be the best button to unlock. If it is not much of the trouble in programming, maybe a choice of a button can be selected as a unlocking button.

(2) if pressing the OK button can be part of the unlocking choice. it will be fantastic to be able to include that in the sequence locking mechanism. .e.g. 245 .. 5 is to press the ok button. Hopefully with such a complex unlocking sequence, the phone will no longer be unlock itself in the pouch anymore.

Hope this will help to improve the TLP coming versions.
[Touch Diamond, MDA Compact IV Themes and Apps] dgduris:
I am having the exact same issue on my Fuze.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear that 1.9.2 is better now. I think that the SuspendTimeOutPowerOn will help you, because it will suspend always after the specified time in your pocket. But of course I want to strive to 0% missed calls. Unfortunately, I cannot control which hardware keys are locked, so the suggestion of the ok button cannot be implemented. However, I am busy with the "Shake to unlock", which would be a very good alternative to the capacitive touches. The advantage of the "Shake to unlock" is that you do not need input focus, so the unlocking can be done always.

For the mean time, I have some alternative settings for you (maybe you already have them):

1. I most cases unlocking via the light sensor will work (only not in too dark conditions). Set UnlockOnLightSensorTime = 1500, so it unlocks earlier, when there is enough light

2. Because your phone apparently wakes up frequently, it is an option to lower the value to suspend after power on to e.g. SuspendTimeOutPowerOn = 10000. Of course you must then also unlock within 10 seconds if there is an incoming call (or you have to power on again).

3. To avoid the capacitive touches unlock too easy in your case, configure a 4 touches sequence, e.g. CapacitiveTouchesSequence = 2121

4. Make the time to unlock via capacaitive touches shorter, e.g. CapacitiveToggleTime = 1500. Of course you have then less time to unlock and maybe you have to restart the sequence more often.

5. In case the unlocking takes too long (via 1 or 3/4), just take out the stylus in those cases, to have no missed calls.

Hope this helps in the mean time.

Happy New Year!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Originally Posted by m4j2t

I am having a new power button issue. When I suspend the device with the power button, if I receive a text message or email notification, the device will not wake up with the power button. The touch pad blinks that I have a message, but I can not wake the phone with out removing the stylus.

Ok, I assume you are using 1.9.2, because the reported problem is already old?

Can you enable debug logging (logdebug=1 and logdebugdetailed=1), reproduce the problem and post the log file \TouchLockPro.log.txt as zipped attachment?

Hope we can find the problem.

Happy New Year!
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
I finally installed this.

I think I have two issues...

First I configured to show a small bar (one pixel thin) RED... but still shows white.

Second... I don't think it really locks when I power on. It vibrates once (as I have configured it when it locks) ok, but BEFORE unlocking (it vibrates two times for that and the small bar disappears - btw I suppose it unlocks because it sees light?), if I manage to click something on my screen (for the brief few seconds when the device is supposedly locked), the screen is NOT locked!

Anybody cares to explain what is happening?

Stock EU TP. Should I log something?
[Touch Diamond, MDA Compact IV Themes and Apps] serphinox:
Hi Dudes,

I've tried different combination but how do you disable lock when there in an incoming call?

I tried Disable TAPI, which did not work. Then i tried Enabling TAPI. LockWhenIncoming is always unchecked.

Also tried AutoLockOnPowerOn Unchecked.

Still no luck. Once it is locked, it is locked.

The reason why i need it unlock upon an incoming call is because I installed slide to Answer PhoneCanvas.

Great software by the way! THANKS!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for daring to try out

That is a known issue, already reported in this thread. Actually, the settings are written by TouchLockAction to the registry, but TouchLockPro uses a cached color. I have fixed this already in the upcoming version 2.0.

For now, do a softreset or stop/start TouchLockPro.

Someone else has posted this behaviour too, that sometimes it does not lock immediately. However, I cannot reproduce. Anyway, I lock the phone before doing other things. However, I also set the power on yes, so my other parts are also continuing at the same time, so that can be a cause that it sometimes does not lock immediately. That I have fixed also in the upcoming version 2.0. But if the vibration of locked has been done, it is already locked. So I assume in your case, that the light sensor already did unlock your phone? You can check by disabling the light sensor or putting your finger on the light sensor.

If this is a reproducable scenario, you can help by posting a debug log (logdebug=1 and logdebugdetailed=1) and add the file \TouchLockPro.log.txt as zipped attachment. Maybe I can find something, which I did overlook till now.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There the following option was meant for:

CommandCallIncoming

Here you can configure a command to unlock, e.g.:

"\Windows\TouchLockAction.exe" Unlock Exit

However, I have found out this is not working with version 1.9.2 (something technically, but I did not convert right between wide characters and char and vice versa). This is fixed in the upcoming version 2.0.

So till then you have to wait.....I hope to post that version next year :mad:

But of course next week is also next year :)
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
Thanks for your reply.

Keep up the good work, have good New Year's eve (it is 23:38 right now in my timezone).

BTW both issues seem to be ok now.

We'll see.
[Touch Diamond, MDA Compact IV Themes and Apps] yawpk:
ZuinigeRijder,

"SuspendOnStylusIn" option not working for touchpro

with options UseStylus=1 and StylusOutDisablesLockMode=1

i set to vibrate when lock(1x) and unlock(2x)

notice that if i pull out the stylus after phone wakes up, vibrate will respond(2x). If i pull out the stylus at sleep mode, phone unlock immediate at wake up but no vibrate.

when i put back the stylus, nothing happens.
[Touch Diamond, MDA Compact IV Themes and Apps] NTPRO.net:
Sprint htc pro

Have a htc pro sprint most functions dont work or work at all. Sorry about being neg but tried for a couple of hrs must be this model by comments of others i can leave more info jan 1
[Touch Diamond, MDA Compact IV Themes and Apps] serphinox:
Hi ZuinigeRijder,

Followed your commands and didnt help on my Touch Pro either. Guess I'll have to eagerly wait for the new release that fixes this

Cheers!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You too, a happy New Year.

You know, you can also configure the red stripe of 1 pixel at the bottom of the screen: ClockY=639
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The SuspendOnStylusIn will only be done if the device is locked.

With option StylusOutDisablesLockMode=1, the phone will unlock when taking out the stylus. So you should set StylusOutDisablesLockMode=0.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It is ok to be negative, especially if it looks it does not work for you. Can you be more specific what is not working? Often it is something simple, sometimes it is even hardware related. For example, when the stylus is out, it will not lock. Someone had a problem with the Stylus Sensor and that gave bogus values back. Of course hard to guess what is wrong without much description, I would expect it works on your phone type.

Can you enable debug logging (logdebug=1 and logdebugdetailed=1) and post the debug log file \TouchLockPro.log.txt as zipped attachment with a description what is not working?

Hope we can find the problem what is not working.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, I knew it would not work for 1.9.2. I will test this time your scenario first, before uploading version 2.0.
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
this would not work for landscape (or the other way round)

the correct solution, should be to allow for negative numbers (as in ClockX)

anyway I "solved" it by using the top bar, but positioning it right below my battery bar with one pixel height - works ok

happy new year
[Touch Diamond, MDA Compact IV Themes and Apps] Designator:
Hey,

I just stumbled upon your software and I´m really impressed because my Touch is feeling fast again. So thanks for that.

But this is bothering me, too. I hope we get a fix real soon :cool: :D

Anyway, keep up the good work =)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Version 2.0.

I just uploaded version 2.0, which fixes some (small) issues and added some features. See version history.

Happy New Year :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I uploaded version 2.0, where the commandCallIncoming can now be configured correctly. For the unlock when there is an incoming call:

"TouchLockAction.exe" unlock

Note that the double quotes are necessary to separate the command from the parameters. I tested it, and it works on my TD.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The just uploaded version has keyboard slider support. Because I do not own a Touch Pro, I could not test. I hope it works. Let me know if it unlocks when sliding the keyboard out.

And yes, the cups of Coffee were excellent :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think I have solved this problem in version 2.0.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Now the extra exit is no longer needed and I only set the power on setting, after I disabled the input. Hope this helps to solve the reported problems.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Just uploaded version 2.0, having the exec possibility.

Example: Exec "command;parameter1 parameter2". Note the punt-comma ";", for separating the command from the parameters.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Added configuration option in version 2.0 to show time (ShowTime), show battery (ShowBattery) and/or date. Now it is possible to choose also date and battery percentage or only 1 or none of the three. Also the font size (FontSize) can be chosen.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I decided not to add the HEX encoding, but added 5 as being area 1 OR area 3. I also removed the area around the button, so it is not sensitive in your pockets, when you use the middle button.

This is available in version 2.0.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I removed the version number from the installation and this solves this problem. However, once you need to deinstall manually the version before 2.0. Thereafter you can just upgrade (auto-deinstall).
[Touch Diamond, MDA Compact IV Themes and Apps] hibby50:
yo great work zj. love ur work. however i cnt get 2 to lock...
[Touch Diamond, MDA Compact IV Themes and Apps] serphinox:
Hi ZuinigeRijder,

Just to give you an update, ive tested the command on a Romeos rom with a Touch Pro and it worked flawlessly! Great Work! :) Do take note that is a "" double quote and not a open/Close inverted commas found in your Symbol's section on SIP diamond Keyboard .

I couldnt get it to work earlier because i used the wrong symbol
[Touch Diamond, MDA Compact IV Themes and Apps] yawpk:
Hi ZuinigeRijder,

i tested TLP 2. After a few hours with the new TLP 2.0 in my touchpro, here is what I found.

(1) the battclock is not always display at its place anymore. after a few lock and unlock testing with 3 ways (poweron button, stylus out and keyboard out) with no order in mind. Usually after using any stytlus or keyboard locking/unlocking then proceed to use poweron to unlock, the battclock just disappears after unlocking. if i put pda to sleep and on again, the battclock reappear but will also disappear after unlocking.

(2) There was one occasion where my screen totally gone funny after sliding in and out the keyboard. I tries a few more times to reproduce with the debuglist but unlikely it did not happen.

(3) i find that area 2 is very hard to be detected with the new capacitive setting. I set sequence as 542. It is just too difficult to get to get unlock now.

(4)If i want to use back TLP 1.9.2, do i need to uninstal the TLP 2 first?
[Touch Diamond, MDA Compact IV Themes and Apps] Kraize:
Yay! v2.0 is a functional version for me :D Now I can actually use this. Except I see that the battery is draining faster than the usual for touchlockpro. like about 2-4 percent in 1.5-2 hours.
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
stylusdisableslockmode doesn´t work for me. unchecked the box, but when the stylus is out the phone will not be locked any more with powerOn etc...
[Touch Diamond, MDA Compact IV Themes and Apps] bjevers:
Stripe stays on

Using this on a Fuze with RRE 3.3 Hybrid rom. Here are a couple of things I noticed. If my phone is on AC power, and I choose the lock from the TouchLockAction screen, it shows the device is locked, even though it isn't (and it shouldn't be, it's plugged into AC, you may need a check for whether to show the lock indicator in this situation). I am only using Stripe for lock indication.

I have the CommandCallIncoming set to "TouchLockAction" unlock. It does unlock my phone, but the lock indicator (stripe in my situation) does not disappear.

Thanks for a great app...Brian
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am not sure what problem you report. You mean area 2 (middle button) to lock? The capacitive touches are only for unlocking, not locking.

How to lock?

Prerequisite: Stylus is IN, not on AC/USB power

* Press the power button (AutoLockOnPowerOn)

* Pressing the BattClock (or start TouchLockAction via another means) and choose one of the Lock option in the TouchLockAction program

* Take OUT the Stylus and putting it back IN within 1 second

Also the light sensor will unlock in the specified time (default 1500 milliseconds), so when there is enough light it may unlock pretty fast.

Can you be more clear about the problem you have?
[Touch Diamond, MDA Compact IV Themes and Apps] texasez:
I would like to donate. do you have a English donate link?

Larry
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There is nothing changed, which could affect battery life. However, the battery percentage given back by Windows Mobile is not really accurate. So you have to judge over a longer period. I am confident TouchLockPro does not drain battery. But of course, you never know. So if this is still the case after using it for more time, please let me know.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparently the language of the button was set to Netherlands.

I have fixed the button (I hope), so it is shown in English now.
[Touch Diamond, MDA Compact IV Themes and Apps] hibby50:
Sorry for the poorly written post, I was on my Pro. I have been using this on my Sprint TP since 1.5, and without any settings being changed at all it will not lock when I power off and power back up. Also I did uninstall the previous version (1.9.2) and deleted all the reg. entries.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, does not matter, for most people English is not their primary language.

Are you sure it is not unlocked by the light sensor?

You can try to disable the light sensor or hold a finger on top of it.

Can you also post a debug log file (logdebug=1 and logdebugdetailed=1), and post \TouchLockPro.log.txt as zipped attachment, so I can have a look why it is not locking?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Very strange. Are you sure the setting LockIndicator is checked?

Can you post a debug log file (logdebug=1 and logdebugdetailed=1) and reproduce this. Please note the time, so I can better analyze the debug log.

Strange too, although the unlocking by the slider is added by version 2.0.

I removed the area around the middle button, because otherwise it unlocks too easy. It appears that this is even possible in the pocket. With the middle button it is less likely, because it is a bit lower than area 1 and 3. Only 2 positions are now sensed as middle touch: 17and 81.

You can check with CapacitiveFingerLock.ProofOfConcept.zip what your phone is giving back as touches. Put the exe in the zip on your phone and just execute it. See what values are given back (lastWhere) when you press the middle button.

Yes, you need to uninstall TLP 2 first. Also reset the settings to their default values (via TouchLockAction or removing the registry entries).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
With the Stylus Out, the phone will always be unlocked, unless you configure UseStylus=0. The StylusDisablesLockMode=1 setting is for preventing to lock again when putting the Stylus in. You did set StylusDisablesLockMode=0, which means if you unlock the phone due to taking out the stylus, it will lock again when putting the Stylus in back again.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparently the bug is not fixed, that sometimes the stripe does not disappear. It looks like this is happening on the Fuze. I could not reproduce on my Touch Diamond. I did some measures I thought which could help, but apparently that did not help.

Can you post a debug log (logdebug=1 and logdebugdetailed=1) and try to reproduce. Please note the time when the stripe is still shown, but not locked. Post the file \TouchLockPro.log.txt as zipped attachment, maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] hibby50:
here is the log. pretty sure it isnt the light

EDIT:it wont lock manually either(opening touchlockaction and pressing lock)
[Touch Diamond, MDA Compact IV Themes and Apps] bjevers:
Call occurred at 3:11pm, lock indicator did not disappear.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see that you have a very strange overrule value for the light sensor time:

15:12:34 -314123842 ==DEFAULT VALUE====: 1500

15:12:34 -314123842 ==OVERRULED VALUE==: 5

15:12:34 -314123842 UnlockOnLightSensorTime: 5

The light sensor time is in milliseconds, so this means it will unlock immediately at any light seen. I poll only once per second, so in practice it will mean it will unlock in about 1 second after sensing light. So it may be your intention, then it is ok. The default value is 1500, so it will unlock after 2 seconds after sensing the first light.

But that is not the problem.

It will not lock due to:

15:14:07 -314123842 SetLocked cancelled, stylus or slider out

15:14:23 -314123842 SetLocked cancelled, stylus or slider out

15:14:27 -314123842 SetLocked cancelled, stylus or slider out

It looks like the stylus is out, according to TouchLockPro:

15:12:34 -314123842 SetStylusOut(true)

I do not see an event that the stylus is IN?

I also do not see a keyboard slider event, so I expect this one is IN.

Can you check the registry key:

HKCU\ControlPanel\Keybd\StylusOutStatus

It should be 0 when Stylus IN and 1 when Stylus OUT.

You can also check the keyboard slider registry key (if you have a keyboard slider):

HKLM\System\CurrentControlSet\Keypad\IsSlideOut

It should be 0 when Slider IN and 1 when Slider out.

So one of the 2 is giving a wrong result according to TouchLockPro.

I expect the stylus is OUT is the problem. Is the Stylus really IN when you try to lock?

Note that you can disable both the Stylus and Slider for unlocking by using UseStylus=0 and UseSlider=0.

Hope this helps?
[Touch Diamond, MDA Compact IV Themes and Apps] hibby50:
im gonna guess it is the slider, this is because I am running 1.9.2 as I type this with no problems, will edit this post shortly. Also what do you mean about the light sensor> Yes I set it to unlock within 5 milliseconds (i dont want to wait :)) so your saying with the new version it will wait 1 second?

EDIT: YES! I disabled both and it works now! You da man!
[Touch Diamond, MDA Compact IV Themes and Apps] Lawliet:
From what I know, the battclock is just an overlay on top of the battery/clock status icon on the taskbar. I can't figure out a way to show the battery on the taskbar in places other than the today screen so that the time indicator does not "spillover" and makes things look ugly. Screenshot included. Any advice?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparently, you have configured in Windows Mobile to show the time when the Today screen is not shown. The time is wider than the standard battery icon.

You can change this in Windows Mobile (I have a Dutch Windows Mobile, so maybe the translation is not ok):

Start -> Settings -> System -> Clock and Alarm -> Uncheck "Show Clock in all programs in the task bar"

However, I had the problem that in Landscape till the time was shown. That I did change with "Advance Config":

Advanced Config -> Today -> Show on Title bar: Battery

Hope this helps.