yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
What command have you configured to unlock? !UNLOCK

That should unlock immediately. Maybe you can post a debug log file and reproduce the scenario, so I can have a look what goes wrong.

Unfortunately, I do not have a a good way to only lock the other buttons, because I do not have a foreground window. DredSensor did something by subclassing. Maybe I go experiment with this, but then I must reintroduce subclassing, something I left after the problems with version 2.2.7.
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
I am not using any command to unlock. I just check the checkbox that says "Unlock on incomings calls". SHouldn't that be enough?

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, I am confused, because I do not have a checkbox "Unlock on incomings calls" :confused:

I have UnlockWhenConnected and LockWhenIncoming, but both have another meaning.

I would expect you configured the command !UNLOCK for

Incoming (CommandCallIncoming = !UNLOCK)
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
Yes sorry that was "UnlockWhenConnected " I meant. What is the difference then?

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This setting is meant in combination with ScreenOffWhenConnected.

See for more details Settings.html#4.8

So this setting is when having answered a call.

As mentioned earlier, you need to specify the command !UNLOCK at Incoming for your behaviour. But then the hardware keys are also unlocked, so you can still miss calls (by accidently pressent the reject hardware button).

Most people use the light sensor and other means for unlocking.
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
... but if it did, what would you use to do that (re-activating the nav sensors)?

thank you again for your quick answer
[Touch Diamond, MDA Compact IV Themes and Apps] Koffein Schluck:
Bug in version 2.4

Lock TouchPanelOnly setting is not working any more correcly!!!

After enabeling it TouchLockPro is not locking anything anymore! :O
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Probably the stylus sensor is not working. Can you post a debug log file?
[Touch Diamond, MDA Compact IV Themes and Apps] varden:
I have tried !LOCKSUSPEND but it does not suspend at all.

At 8.51 is !LOCKSUSPEND without AC power

At 8.54 is "TouchLockAction.exe" locksuspend with AC power

Please check
[Touch Diamond, MDA Compact IV Themes and Apps] interceptor77:
hi ZuinigeRijder. first of all, many thanks for this great software. i´m very satisfied with this. i only have one last wish. for the reason you can see in the quotation it would be great, if there could be a command like "!UNLOCKSCREEN". So in combination with PhoneCanvas it should be nearly impossible to miss calls by pressing hardware buttons or simple display buttons by mistake. Is it possible in future versions or do you see another solution for this? Unlocking only by light sensor or in combination with other things is not the best solution for me.

best regards,

interceptor
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Currently the HTC API I use locks the hardware keys AND the TouchPanel. I can also only lock the touchpanel, but I cannot lock only the hardware keys.

The problem is that I do not have a foreground window, so catching the hardware buttons only is a problem. There is a way, like DredSensor, by subclassing the foreground window and then intercept hardware buttons.

The latter would be the solution for you (and others). However, I had bad experience with subclassing. A lot of people reported problems with version 2.2.7. I even opended a poll here.. One third reported problems. So I left the subclassing approach.

Maybe I should try it again, because this could also solve the capacitive navsensor and GSensor problems with the TF3D home screen on newer ROM's........
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see that !LOCKSUSPEND does not work, when a call is ended. I have a mechanism, that after a call it will not suspend within 5 seconds. I will see if I can remove this, when executing !LOCKSUSPEND. So that is a feature/bug from my side.

I miss the logging at 8:54 in TouchLockPro.log.txt.

So probably half of the logging is copied. Best is to stop TouchLockPro (via Programs folder), before copying the file. Can you post a new debug log file?

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] interceptor77:
@ZR: many thanks for your quick answer. so i will look on your future releases.

regards, interceptor
[Touch Diamond, MDA Compact IV Themes and Apps] DomSim:
using TAPI when call is ended i have set !LOCKSCREEN this works but does not obey the suspendtimeoutpoweron which is set to 10 seconds. when the call ends the screen locks but stays on forever. i can set it as !LOCK or !LOCKSUSPEND and the screen turns off, but it turns off instantly which i would prefer to avoid. if !LOCKSCREEN when call ended obeyed the time out that would be greatly appreciated.
[Touch Diamond, MDA Compact IV Themes and Apps] varden:
This file should be OK.
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
Hi, ZuinigeRijder

I realize you have an already full to-do list, on top of an already busy personal schedule, however, I found something that it might get TouchLockPro become an even better and reliable piece of software, than it already is.

We agreed that sometimes the swipes stop responding, and on the later versions, this operation is even less consistent.

I tested my sensors with NavDbgTool.exe, on the moments when the swipes stopped responding, and I noticed that the sensors ARE, in fact, SENSING the finger touches.

That would mean that it is actually the

connection

between the sensors and TouchLockPro which is not active anymore.

Nothing else than Power off/Power on is able to re-activate this connection.

Something happens inside TLP when the phone is powered on, and I am sure that you know exactly what it is. That something is "getting loose" for some reasons, and once you find why that happens, I am sure that fixing that will make a lot of people, including yourself, much more happier :)

all the best
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In other situations, people do not want that it suspends after 30 seconds. For example, you have a GPS application running, you want to lock the screen and do not want to suspend (because then the GPS will stop too).

Is there a specific reason, you want the screen locked, but still want it suspend after some time?

You can also enable SuspendOnBacklightOff (SuspendOnBacklightOff = 1). So then it will suspend automatically when the backlight goes off......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, this one does contain the logging :)

Summarizing the problem:

I see that !LOCKSUSPEND does not work, when a call is ended. I have a mechanism, that after a call it will not suspend within 5 seconds. I will see if I can remove this, when executing !LOCKSUSPEND. So that is a feature/bug from my side.

Thanks for the logging. This helped me to find out what is going on.

I see in the source code that LOCKSUSPEND indeed tries to lock and suspend, also when on AC Power.

The question is, of course, do we always want to skip locksuspend when we are on AC power. Or do we only want this when configured this as TAPI command?

Locking will not be done (because it is on AC power). But suspend will now be done always. So probably it is safe to assume you do not want to locksuspend when on AC power, because you just can press the power button when you want to power off the phone.

I will add this in a next version.
[Touch Diamond, MDA Compact IV Themes and Apps] varden:
Precisely. Waiting for the next version. Thanks for the help
[Touch Diamond, MDA Compact IV Themes and Apps] DomSim:
why i want it is so the screen locks after i hang up a call so if the phone is in my pocket and i am using bluetooth, it doesnt leave the phone unlocked in my pocket. i want it to be delayed though so if i have the phone in my hand, not using bluetooth, and i hang up the call the phone doesnt instantly turn off. that way if im still using it it doesnt turn off on me. locking is fine as it should then unlock due to light sensor or orientation or capacitive letting me continue using the phone.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In a next version I add bluetooth support, so when bluetooth radio is on, it does not unlock. Probably that is what you want too, so that the request of you is not needed.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Was it so simple, then I would have found a solution already. Other programs using the capacitive NavSensor have the same problem. So HTC has screwed up something, which was working alright earlier. :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] DomSim:
yes, bluetooth detection and support would solve my problem. thank you very much. keep it up!
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
I still can't get the TAPI settings configured properly. Now I am almost there but still got one problem left. I have configure it to autounlock when a there is an incoming call as I have the slide to answer screen buitl into my rom and don't want to have to do a double unlock before I can answer a call. I also let the TouchLockPro lock the screen again after disconnetting. However if a call comes in and I don't answer it then the phone remains unlocked in my pocket :-(

I have the following setup:

UseTAPI = 1

UnlockWhenConnected = 0 (if I check this it will not lock again after the call)

ScreenOffWhenConnected = 0

LockWhenIncoming = 0

Incoming (CommandCallIncoming = ) = !UNLOCK

Connected (CommandCallConnected = ) = !UNLOCK

Ended (CommandCallEnded = ) =!LOCKSCREEN

Is there anything I can do to make it lock again after a missed call? I think this should really be supported as it is a main scenario when used in conjuction with another slide-to-answer mechanism.

Note that I don't use the light sensor as it is too unpredictable.

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] peterbonge:
Just a very small and easy wish: If using the 24h clock it would be nice if it would show e.g. 09:00 instead of 9:00.

And a reminder: Please add an icon to the TouchLockPro shortcut. And don't forget the skinning support. Or at least change the action icons, add text to them or change the action menu to a text only menu.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Missed calls

I don't understand I'm still missing calls with the latest version. I have to keep pressing the answer button and hope I get it.... The phone is unlock but it does not let me answer the call. I had to put a lot of ring before my voice mail kicks in, otherwise I miss the call, and sometime the caller hangups thinking I'm not answering :(

I just added the log. I did a reset on my device and reproduced the problem with then logging on. Hope you can see my problem :)

Thanks for you help and great product...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am not sure (it is a time ago I checked), but when a call is not answered the CommandCallEnded is seen by my TAPI support (you can check by enabling debug logging). But the LOCKSCREEN will not be executed, for the same reason as in this post.. That will be fixed in the next version. But I am not sure, if the call ended is seen for a not answered call. Can you check?

For now, you can enable SuspendOnBacklightOff (SuspendOnBacklightOff = 1), so at least it locks after the backlight off.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will change into 09:00 in a next version.

Skinning is on the wish list, but with some less priority.

But I will see if I can add (configurable) text to the TouchLockAction screen in the next version, so it is more clear what icon means what.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you point out, at what time your problem occurred?

I assume your problem begins at:

12:29:42 767010906 Going to home screen: 2080905168

I seems that the sensors are not working at that time, due to the famous HTC bug. I also see the light sensor not reacting. Was it dark, or was this one also not working?

12:29:42 767010906 GetLightSensorValue(): 0

12:29:42 767010906 Light OFF: 0

But the GSensor (which you disabled), seems to work:

12:29:42 -1909450522 SetOrientation: FaceUp

12:29:42 -1909450522 SetOrientation: nothing to do

And you configured to unlock when there is an incoming call:

12:29:59 761340962 NotificationCallStatusIncoming()

12:29:59 767010906 ClockWndProc(WM_TIMER): 19

12:29:59 767010906 NOTIFY_CALLSTATUS_INCOMING

12:29:59 767010906 Execute(): !UNLOCK

12:29:59 767010906 UnlockRequest()

I see also something strange (several times):

12:29:59 761340962 CActions::HandleActionsNotification()

12:29:59 761340962 CActions::HandleActionsStatus()

Seems that another application is writing actions to the ZuinigeRijder actions registry keys. Is there some other app doing that, or did you configure something special?

What I also find strange, is that going to the home screen only occured once (the TF3D workaround). Or the manila foreground window changes over time?

So for now, I have more questions than a solution.
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
Thanks a lot. I am attaching the logfile. What I did was to call from anothe ohone, waiit 2-3 rings and then hang-up. I don't see a CommandCallEnded but a SetCallStatus(CALL_ENDED): 1. Not sure whether that helps. I can see the the standard screen lock built into WM6.1 operates correctly (it unlocks when a call is incoming and locks again if the calll is dropped).

Hope it iwll be posiible to correct this in the next release.

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] epiphone:
Have a irritating thing with the latest 2.4.1, just upgraded from 2.2.7.

Everytime I hit the Power button at the top of the Diamond to turn the phone off, and then again to turn it on, the screen flicks from TODAY tab to PEOPLE tab, before going back to TODAY tab again. Nothing else seems to be a problem, but this is really kinda irritating.

Still this is one great app, been with it for sometime now :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can disable this behaviour, but then there is a chance that the capacitive nav sensor does not always work.

TF3DWorkaround (TF3DWorkaround = 0)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I see in my source code that I only execute the ended Command when it was connected. I will change it, so it will also be called, when a call is not answered. So this will be fixed in the next version.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Another application? How can I test this? I will disable a couple of program using Memmaid, to see what changes.

I will get back to you.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockAction translations

I am adding text to the TouchLockAction screen, so it is more clear what the icons mean. I am also considering Internationalization, so the Settings screens can be translated in different languages. For the short term, I would like to add the translations for the TouchLockAction screen first. Later on, the Settings screens can be translated.

I will start with the Dutch language translation for this screen:

Dutch

Lock: Vergrendelen

Suspend: Slapen

Exit: Stop

Settings: Instellingen

Reset: Herstarten

Off: Uit

Can you provide the translation in your language?
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
Spanish translation:

Lock: Bloquear

Suspend: Suspender

Exit: Salir

Settings: Ajustes

Reset: Reiniciar

Off: Apagar
[Touch Diamond, MDA Compact IV Themes and Apps] varden:
Polish translation:

Lock: Zablokuj

Suspend: Wstrzymaj

Exit: Wyjdź

Settings: Ustawienia

Reset: Resetuj

Off: Wyłącz
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I found out, what causes:

12:29:59 761340962 CActions::HandleActionsNotification()

12:29:59 761340962 CActions::HandleActionsStatus()

It is TouchLockPro itself, because it writes the IsLockedStatus to that registry key. I will move that to another subkey (Status) in the next version, which has also other status values for displaying the current sensor values. But that does not solve your problem, so I am still unknown what that problem is.

The only hunch is that this is just the HTC bug, so the sensors do not work always when on the home screen.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Translations

Thanks so far.

So far we have the following translations:

English

Dutch

Spanish

Polish

Google Analytics shows that TouchLockPro is used in 102 countries :)

So there is still a lot of translations missing. This is the top 30:

1. United States 1.520

2. Germany 1.381

3. Italy 559

4. Netherlands 521

5. China 465

6. United Kingdom 425

7. Poland 412

8. Russia 253

9. France 250

10. Japan 240

11. Singapore 202

12. Czech Republic 185

13. Spain 183

14. Switzerland 180

15. Sweden 144

16. Norway 143

17. Canada 137

18. Malaysia 136

19. Hong Kong 134

20. Austria 118

21. Romania 111

22. Australia 109

23. India 102

24. Greece 87

25. Belgium 80

26. Denmark 73

27. Portugal 67

28. Hungary 59

29. Taiwan 55

30. Ukraine 54
[Touch Diamond, MDA Compact IV Themes and Apps] peterbonge:
German translation:

Lock: Sperren

Suspend: Standby

Exit: Beenden

Settings: Einstellungen

Reset: Zurücksetzen

Off: Ausschalten
[Touch Diamond, MDA Compact IV Themes and Apps] markjhvt:
Won't lock

Since soft-resetting my device last night, TouchLockPro no longer locks the phone at all. I've tried uninstalling and reinstalling and it just doesn't do anything anymore.

The "AutoLockOnPowerOn" registry setting is set to 1. Is there anything else I should check?
[Touch Diamond, MDA Compact IV Themes and Apps] someboy:
Chinese translation:

Lock: 锁定

Suspend: 待机

Exit: 退出

Settings: 设置

Reset: 重启

Off: 关机
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
Romanian labels

Here is the Romanian translation:

Lock: Blocheaza

Suspend: Suspenda

Exit: Iesire

Settings: Setari

Reset: Reseteaza

Off: Opreste

I'm glad you finally decided to add the labels! :) (if you remember I suggested this some time ago - back in post 931)

However I think you should stick with only English labels - anyone who uses your program by now obviously knows English! :)

Best regards,

Dan
[Touch Diamond, MDA Compact IV Themes and Apps] bdemarco:
failure to lock after soft reset

I have this problem after I soft reset on my stock ROM Verizon Touch Pro. Here's what fixes it for me: turn the phone off, then on, then pull out the stylus, wait 30 seconds, and put the stylus back in. If I do this procedure, TLP then will work correctly.
[Touch Diamond, MDA Compact IV Themes and Apps] markjhvt:
Yeah, this worked...

Odd... I didn't have this problem with earlier versions.

I have a strange feeling TLP is causing Opera to crash, too, though I'm not sure that's really the case.
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
Greek:

Lock: Κλείδωμα

Suspend: Αναστολή or better Κλείσιμο

Exit: Έξοδος

Settings: Ρυθμίσεις

Reset: Επανεκίνηση

Off: Σβήσιμο
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange. Maybe something wrong with the stylus sensor (hardware)?

Can you post a debug log file (logdebug=1 and logdebugdetailed=1), reproduce the scenario and post the debug log file \TouchLockPro.log.txt as zipped attachment.

Maybe that gives me a clue?
[Touch Diamond, MDA Compact IV Themes and Apps] markjhvt:
I was wrong in my previous post...

It looks like after doing the whole stylus thing, TLP *tries* to lock the phone, but the lock doesn't work. So, the lock indicator is there, but the phone isn't actually locked.

I'll try turning on the debugging when I get a chance later today and let you know.
[Touch Diamond, MDA Compact IV Themes and Apps] markjhvt:
Well.....

I soft reset the phone in order to start from scratch after enabling the Debug settings. And it's working fine again.

So.... if it starts misbehaving again, I'll grab the logs and send them your way.

Until then - thanks for the great program and your quick response to my question :)
[Touch Diamond, MDA Compact IV Themes and Apps] markjhvt:
Another thing I've noticed....

I can't quite get the Vibrate settings to work. If I enable Vibrate, it will always vibrate twice when it's locked and once when unlocked, regardless of what I have the settings set to.

I don't know if there are some defaults that it's picking up that are left over from an old version somewhere or something along those lines, maybe...

Did you want a debug log for that? :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You must uncheck Vibrate and just select the number of vibrates when locked and unlocked. That should work, if I remember correctly.

This is a bit confusing, so probably I remove the old behaviour (checkbox Vibrate) and you must just select the number of vibrates for lock/unlock.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Cross my fingers. But I expect it is a problem with the Stylus sensor (hardware). You can clean gently the stylus sensor, by removing the battery and blow away dust, so it is sensed correctly.
[Touch Diamond, MDA Compact IV Themes and Apps] studentjunk:
i have a quick comment. I use sashimi autoinstall after I hard reset or flash my phone. Every time touch lock installs or uninstalls, it gives a message saying that it is activated or disabled. is there a way of removing that so I can install the program without prompts?
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
Thanks a lot. I have two more wishes/feedback.

1. As I wrote my configuration right now is as follows:

UseTAPI = 1

UnlockWhenConnected = 0 (if I check this it will not lock again after the call)

ScreenOffWhenConnected = 0

LockWhenIncoming = 0

Incoming (CommandCallIncoming = ) = !UNLOCK

Connected (CommandCallConnected = ) = !UNLOCK

Ended (CommandCallEnded = ) =!LOCKSCREEN

Is there any reason why Unlockwhenconnected and the CommandCallEnded are mutually exclusive? I would like that once connected it stays unlocked until the calls ends. The reason for this is that everytime the screen turns off during a call (which is as soon as I take the phone to my ear) it locks again. This is a major pain when operating services that requires to enter keystorkes to navigate.

2. I love the navigation panel sweeps, but those are sometimes to easily triggered by mimstake. Would it be posisble to implement also double tapping of the 4 quadrants?

Thanks a lot.

I'm looking forward to the next release.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will remove the following messageBoxes in the next version:

TouchLockPro will now be disabled.

TouchLockPro will now be enabled.
[Touch Diamond, MDA Compact IV Themes and Apps] Sartuche24:
I must say I really like this program. I was using S2U2 which is really nice but I wanted a simple locking program and this is it. It locks my phone and doesn't eat a lot of resources which is good since my Fuze can run through the battery pretty quickly if your not careful. I'm looking forward to your updates and awesome job on the app.
[Touch Diamond, MDA Compact IV Themes and Apps] ymukhtar:
Thank you for this nice tool:

Just one request (for a fix). -When unlocking with the stylus. TouchFlo opens the "People" tab for 2 seconds and then goes back to the "Home" tab.

Should just stay on "Home" tab when unlocking.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can disable this via setting TF3DWorkaround

In a next version I will do only the workaround when locked (and of course when the workaround is configured).