yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have read somewhere that this problem of the answer key not locking was about the ROM version number. Other locking solutions had the same problem. Version 1.48 did not have this problem, I believe.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think this is more related to the ROM. If the ROM does not support the sensors, TouchLockPro cannot do anything on it.

Did you use/try [14/12][rom][wm6.5.3]build 28014 for htc diamond :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
Hello, ZuinigeRijder!

How can I update the translation? Since my translation (v2.7) appeared already many new words ...

Vadim,

your Russian translator :)
[Touch Diamond, MDA Compact IV Themes and Apps] i_m_jughead:
LED number for TP2/Rhodium

I love this applicaiton. I am trying to get some falshing LED indication when the phone is locked i tried numberous LED numbers but none works for me. Can anybody who has Touch pro 2 or Rhodium give me a wroking LED Number?
[Touch Diamond, MDA Compact IV Themes and Apps] abello00:
Remove triple tap feature

I am not sure if the triple tap feature is working properly on my touch pro 2. When the phone is locked (not on AC power, stylus is in), If I triple tap something on the screen (say the Camera or All Contacts links on the bottom left and right, respectively), the phone will open the camera (or contacts) and still be locked. Is there anyway to disable to triple tap feature.

Also I thought triple tapping was supposed to unlock the phone, am I doing something wrong ? (I've tried triple tapping everywhere)
[Touch Diamond, MDA Compact IV Themes and Apps] infantilo:
Sadly i'm one of those german users, so the roms in GER are rare.

FlipIt works fine and also the auto-lite adjustment.

Before flashing to another rom, is there any other solution i could try. would a log file help?

Thanks for fast reply!!!!
[Touch Diamond, MDA Compact IV Themes and Apps] jasring:
at first tnx for this great program.

i have a problem with touchlockpro and some custom roms. sometimes my phone will completely lock when it is in standby only the reset button will work. when this is happened once it happens more and only a hard-reset will help.

what can i do?
[Touch Diamond, MDA Compact IV Themes and Apps] creed:
Any way to stop hardware buttons turning on screen?

I really like this piece of software but I have an issue with it. Is there a way to prevent all but the power button from activating the screen? The screen and buttons all seem to be locked but the screen backlight will still come on if any of the 5 buttons at the bottom of my HD2 are touched. The volume keys are ok and do not respond. Its only a small thing but the backlight keeps coming on even in my pocket because any of those 5 buttons will activate the screen. If it was just the power button that would happen far less.

One other thing is that the buttons aren't locking when I have an incoming call. I wish to use only the slide to answer feature but after selecting keysonly in the TAPI menu the hardware answer button still works.
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
I have a problem with the latest version. I can not go into the settings.

Mi pda is a Diamond
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, you are not the first one, so there is something wrong in TouchLockAction. However, I do not have a clue yet, what would be wrong.

Can you do me a favor, change the setting HKCU\Software\ZuinigeRijder\LockSettings\LogDebug into 1 with a registry editor like PHM Regedit. Soft reset your phone, wait till TouchLockPro has been started, try to start TouchLockAction again and thereafter post the debug log files TouchLockPro.log.txt and TouchLockAction.log.txt. Maybe that gives me a clue.

This post describes how to make TouchLockAction responding again, but you need to reapply settings thereafter:

See this post for a solution, removing registry tree

Sorry for the inconvenience :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hi Vadim,

good that you are willing to update the Russian translations again. Great :)

See the current russian translations as attachment. You only need to translate the .Text translations in English. See this post for more detailed explanation.

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I only know about the LED numbers for Diamond, which are described here.

Hope that TP2/Rhodium users react.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Probably you mean the problem shown in this video.. I do not know a solution for that problem (yet).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Does it not unlock when put on (USB) power?

If it happens regular, you can enable debug logging, wait till the problem appears and after a soft reset post the debug log file \TouchLockPro.log.txt. Maybe that gives me a clue.

However, it does not need to be the fault of TouchLockPro, it can be also due to your ROM.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There is a Windows Mobile setting, that it will awake on any button. Maybe you enabled this setting. Mine is located as (I have a dutch ROM so tried to translate):

Start -> Settings -> System -> KeyLock -> Lock all keys except Power buttnon

The problem of not locking the answer button looks like an issue which is solved by ROM 1.48 or later, as I answered already. But maybe other HD2 users can confirm that with their phone the answer key IS locked.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, providing a log file will show why it is not working.

I assume you know how to make a debug log file, otherwise look at other posts.
[Touch Diamond, MDA Compact IV Themes and Apps] jasring:
will try it next week
[Touch Diamond, MDA Compact IV Themes and Apps] creed:
Can't find KeyLock on my phone

Hmmm I am running the TUR 1.61 ROM but I cannot find the KeyLock setting anywhere on the phone!
[Touch Diamond, MDA Compact IV Themes and Apps] edbolor:
Anyone has problems with hardware keys on TP2 not working? Everything works fine till screen times out and goes black (or till i press power button), then none of the keys will work. Only way I can unlock TouchLockPro is pull out stylus or connect AC to phone (I have other unlock options unchecked)... I anyone had same problem, please help me with a solution, otherwise I'd hate to uninstall such a great program...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you configure HTCLockAPI = 1 and EnableInputAtSuspend = 0 :confused:

Because that would explain the behaviour.

You can enable debug logging (LogDebug=1), reproduce the scenario and post the log file \TouchLockPro.log.txt as zipped attachment. Note the time when the problem occurred, so I know where to look :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe this post helps, it talks about a registry key. :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] r00sick:
Hi, ZuinigeRijder!

Thank you for your great app.

I've just read "API-spec1.2.1.pdf" (my PDA is I900). What do you think about using "Orientation API" instead of "Accelerometer API" (or as an additional option)? I think it would be interesting and it will make Omnia with TouchLockPro functionally closer to HTC devices (now Omnia should be shaked to execute an action by G-Sensor).

And sorry for my english
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
I did what you said. I upload log file, I hope you serve something.
[Touch Diamond, MDA Compact IV Themes and Apps] edbolor:
thanks for reply

i have those setup like you said... still no luck

enclosing my log, help please
[Touch Diamond, MDA Compact IV Themes and Apps] Mursidus:
Hi, how to make this on htc diamond:

At an incoming call to block only the screen (keys will stay unlock), and in other cases (on power On) to block all?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The HTC Sensor API also uses the accelerometer API to compute the orientation. Earlier version I used the HTC orientation readings, but these are not better than computing it from XYZ Vector. The advantage of using XYZ is also you can do nice other things, like shake to unlock. That I plan to add in a next version.

Anyway, do you have problems with the orientation (you can see them in the GSENSOR settings screen) showing incorrect results :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for providing the log file.

I see the following strange value:

2010-01-07 15:51:41 112858302 hasPhoneTypeSet: 10

The PhoneType must be a value between 1 and 8, so in one way it is possible to select/set a value outside the ones possible. Maybe that is the fault.

I will check my code.

If you remove the key tree HKCU\Software\ZuinigeRijder it should be possible to configure from start.

Sorry for the inconvenience, but at least I have now a hint where the problem might be. Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I see you did configure:

HTCLockAPI = 1

EnableInputAtSuspend = 0

It should be:

HTCLockAPI = 1

EnableInputAtSuspend = 1

Is there also a special reason you want the HTC locking way. Because most people use:

HTCLockAPI = 0

Or do you have another problem then?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, there is at the moment no configuration option for that.

Don't you have a slide2answer solution? Because then you can configure KeysOnly, so you can slide2answer for answering an incoming call.
[Touch Diamond, MDA Compact IV Themes and Apps] el_zizzo:
Great work!

Thanks for the great app. I love it. Everything works fine for me. I will donate for sure ;)
[Touch Diamond, MDA Compact IV Themes and Apps] r00sick:
Only one. When i write down "656 !LOCKSUSPEND", I have to "Shake face up, shake face down and shake face up" to lock and suspend my device. But I wanted just turn device on 180 degrees and turn it back. I've tried "61516" too: now I have to shake 5 times. Sorry, I keep testing, that was my software conflict.
[Touch Diamond, MDA Compact IV Themes and Apps] brezuicab:
Problem on HTC Touch PRO 2

Hi,

just tried this app on my HTC Touch Pro2 and it seemns i doesn`t work... am I the only one having issues or is it something I missed?

I really want to make this app work on my device so I wold apreciate some feedback..... pretty please even :D

Thx.

----EDIT---

After proprely reading this thread, as I should have done in the first place I managed to get TLP Action working again by resetting the settings. I will try to reset the program and activa the LOG setting maybe it will help someone debug my problem :)

Thx anyway.
[Touch Diamond, MDA Compact IV Themes and Apps] HTC_FUZE:
Installed and tested, I have 2 problem:

1. After open "Setting", it is very slow.

2. Cannot use any keys to answer/reject incoming call and Slide2Answer won't work either. i.e. all hard keys and touch screen are still locked. I use default settings.

3. Actually I prefer to unlock everthing when there is an incoming call, and I also prefer to use original WM lock. In the past, I use WM lock and Touch In Call Tweak without problem. Is it possible for you to add selection of your lock interface and WM lock interface?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
1. Strange. There is a problem that sometimge the PhoneType gets set to 10. Maybe that is the cause?

2. Set KeysOnly (ockWhenIncomingKeyOnly = 1) in the TAPI settings screen.

3. I do not know how to integrate with WM lock. Although I probably can force a lock, unlocking is the problem. Would you be served with a setting to use WM lock at power off/power on and no unlock by TouchLockPro :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I will have a look why phoneType can be out of range. Definitely a bug in TouchLockAction....
[Touch Diamond, MDA Compact IV Themes and Apps] Cool Shadow:
Hello

Well I tried for some minutes ur program, and liked it.

Great job

and then i messed something up and my phone won't unlock, so i took out the battery and started my phone again.in the time i have left till the phone gets locked i did manage to uninstall the feature.I reinstalled again and it had the same settings.then i read the manual in your site.

My question is: is there any other possibility to change these settings and that i could use your Programm in my phone without using registry editor or reinstalling my ROM or without Hardresetting??

Thank you in Advance
[Touch Diamond, MDA Compact IV Themes and Apps] r00sick:
ZuinigeRijder, I've got two more supervisions (ver. 2.10.2):

1. In the "Setting->Phone Type" every phone type take place twice (I mean 1-2-3-4-5-6-7-8-1-2-3-4-5-6-7-8)

2. Sometimes GSensor is unworkable ("0" is in the right top corner of GSensor settings). It occurs each time, when ageye's "G-Alarm" works (here is the logs, alarm clock has been established at 10:35) and sometimes, when device (Samsung I900) comes back from suspend by keypressing (I have not revealed more exact dependence yet)
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
[Q]Compatibality with TICST

Great Work. Undoubtedly the best lock application for my touch diamond.

My question is: Can I use Touch Lock Pro 2.10.2 WITH TouchInCallScreenTweek - I want to do this because it has TomTom in it's exception list. I do know that you are planning to develop this but my understanding is that the 'exceptions' in your future versions will be for lock/unlock purpose and not for 'TAPI'.

This 'TAPI' part in your programme is desirable but needs 'exceptions' as well , especially TomTom and other common navigation softwares.
[Touch Diamond, MDA Compact IV Themes and Apps] sean222:
Great locking program, DEFINITELY worth a donation. :D

My only request is a nice lock icon in the taskbar (like SensorLock) ...the white square you have is a little ugly. BUT, you do provide us with many (other) locking 'indicators'...so I really can't complain!

Other than that, no problems or bugs for me!

Thank You!
[Touch Diamond, MDA Compact IV Themes and Apps] dehell:
light sensor on HD ?

For me, the V2.10.2 doesn't work correct with the light sensor, the actual value always stays at 0 an though the phone doesn't unlock.

V2.7.2 works perfect.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can install an older version of TouchLockPro, e.g. 2.9.

With that version TouchLockAction should be able to start. There you can choose in the About settings screen, to reset to defaults.

Thereafter you can reinstall the newer version.

I have found the problem with TouchLockAction. The PhoneType can get a value above 8, when the GSENSOR Settings screen is opened more than once and you choose one of the options above 8.

I am working on a version that fixes this.

Sorry for the inconvenience :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for providing the log files.

1. I found the problem, I add the phoneTypes each time the GSENSOR Settings window is opened again. So that is why people sometimes get the PhoneType out-of-range. I am busy with a fix.

2. G-Alarm supports TouchLockPro by sending unlock command.

2010-01-09 10:34:45 1679393106 Orientation Sensor Awake

2010-01-09 10:34:45 624565098 Samsung light sensor value: 69

....

2010-01-09 10:34:45 1683431074 CActions::HandleActionsNotification()

2010-01-09 10:34:45 1683431074 CActions::HandleActionsStatus()

2010-01-09 10:34:45 1683431074 GetActionStatusString(): Command

2010-01-09 10:34:45 1683431074 ==value====: !UNLOCK

2010-01-09 10:34:45 1683431074 Command: !UNLOCK

2010-01-09 10:34:45 1683431074 ExecuteRequest(): !UNLOCK

So I think unlock is due to G-Alarm unlocking.

I see indeed only light sensor logging and no GSENSOR logging anymore after 10:34:18 :confused:

So it looks like G-Alarm does something nasty to the GSENSOR.

I just call SmiAccelerometerGetVector, and that does not return SMI_SUCCESS anymore.....so I do not know what I can do to fix that :mad:

Interesting settings you have, though ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, you can disable the TouchLockPro InCallTweak and use TouchInCallScreenTweak. While you are in a call, it will not lock again (at least that should be the case).

I will add the exception-list for TAPI to the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the compliments. The icon is already on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, because the mechanism has not been changed. Can you enable debug logging, reproduce the problem and post the log file \TouchLockPro.log.txt. Maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro Version 2.10.3 with fix that TouchLockAction not responds anymore

TouchLockPro version 2.10.3 with fix that TouchLockAction not responds anymore. PhoneType could get out of range.

Sorry for the inconvenience, if people encountered this problem.
[Touch Diamond, MDA Compact IV Themes and Apps] theGressier:
Hello,

I've tried TouchLockPro (2.10.2 and 2.10.3) on my HD2 (Rom 1.48 FR Official Bouygues Telecom) and I meet 3 problems

- I don't succeed to get the g-sensor working

- The screen is black when I use HTCLockAPI=1 and I receive a call (just the keys are illuminated)

- The green key is not locked while an incoming call altough I did set LockWhenIncomingKeyOnly=1 and HTCLockAPI=0

Thansk in advance for your response

Billy
[Touch Diamond, MDA Compact IV Themes and Apps] Andreas H.:
Hello,

last weekend I installed TochLockPro on my HTC Touch Diamond 2 (WM6.1). It's a very nice tool.

But I miss one feature! I want to have the device locked, when it wakes up due to "internal" reasons e.g. incomming call, reminder pops up etc. This works fine, when I configure "LockOnPowerOn". But the device is also locked, when I switch on the device by pressing the power button. I don't want to have this. When I switch on the device I want to use it immediately and not to unlock it first! To configure the power button to unlock the device doesn't work.

Who can help me - please!

I tried to read all the postings but its too hard to read more than 3000 postings!

Andreas
[Touch Diamond, MDA Compact IV Themes and Apps] dehell:
Solved?

Hello,

the phone type was set to Samsung and changing that to HTC HD didn't solve the problem. Now (after reinstalling 2.7.2) and a softreset and then (to get the log-file for you) reinstalling 2.10.2 again, the problem is fixed. Perhaps I have to do a softreset after czhanging the phonetype?

Thanks for your help
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, changing the PhoneType can mean a soft reset is necessary. Because if you switch to another PhoneType having other sensors, TouchLockPro needs to access the GSENSOR different. But glad to hear it works again. I will add a note in the Settings screen about the soft reset.

Version 2.10.3 solves a problem with the phonetype being out of range.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Currently I cannot distinguish the wake up due to power button press or another event. The problem with your request, is that you can also accidently press the power button, leaving the phone vulnerable. I can understand that some people want to take that risk, because the chance is less.

I do not have a good solution for detecting power button pressed. Cobaltikus has an idea about rerouting the power button to an app, using the link approach. I do not know if that works on all phones and also making the link can be tricky. But maybe others have simpler ideas?

Is the light sensor unlock (mostly it will do automatically in not too dark conditions, you can make the light sensor time shorter too) and/or Zoombar unlock easy enough?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Is the PhoneType set correctly? Also make sure to do a soft reset after setting it to your phone type.

The screen is black at incoming call, looks like the GSENSOR orientation is portrait, so the InCallTweak is activated. You can also disable the InCallTweak, if you do not want that.

The green key is the answer key, I assume. Some people have the same problem, and people with a ro of 1.48 or later do not have this. So it could be this HTC issue?

If the GSENSOR still does not work, you can enable debug logging (logdebug = 1), reproduce the problem, including blanking of the screen, and post the debug log file \TouchLockPro.log.txt.
[Touch Diamond, MDA Compact IV Themes and Apps] theGressier:
Hello,

I checked my config and InCallTweak was not activated.

For the GSensor, I succeed only one time to see it work in the touchlockaction, it was after having delete the registry settings and then reconfigure to my device Model (7).

For the answer key, it seems to be related to an HTC issue, and I know a tweak which is to create a long_send.lnk shortcut in the windows folder to avoid problem

I join my log file, I hope you will find useful informations

Billy
[Touch Diamond, MDA Compact IV Themes and Apps] Andreas H.:
Ok, I tried this and it seams to be a workaround.

Thank You very much for this fast answer.

Andreas
[Touch Diamond, MDA Compact IV Themes and Apps] jablo3:
Anybady have a polish version of TouchLockPro?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am glad to add polish, but then someone has to provide the translations. See this posts how to provide translations.
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
IDEA

One of the ways to do this would be to add the option 'KeepBacklightOnWhenPowerd' next to 'InCallTweak (InCallTweak = 1)'

I think almost all users use satnav/gps with car chargers and hence the backlight wont switch off even when in potrait when using gps.

Feel free to totaly disregard my suggestion if it's 'too much'.
[Touch Diamond, MDA Compact IV Themes and Apps] jablo3:
Do you have a files to add polish language? Please upload me it
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
Russian translation v.2.10.x done.
[Touch Diamond, MDA Compact IV Themes and Apps] Cool Shadow:
Thank You!!

Thx

about the help

i did it last night and now it works properly

I am really satisfied with this APP

it is really worthy having it
[Touch Diamond, MDA Compact IV Themes and Apps] HTC_FUZE:
here I found another problem on my HTC FUZE. When it is in landscape mode and open a program. The clock will be displayed on the title bar which is bigger than BattClock indication. See attached pictures. Could you please adjust the box size so battclock can fully overlap? If I do not open any program in landscape mode, then it is ok.
[Touch Diamond, MDA Compact IV Themes and Apps] toadlife:
There is no easy solution for this because this program simply overlays an image over the screen. You can make it wider by editing the registry settings, "ClockWidth" under [HKEY_CURRENT_USER\Software\ZuinigeRijder\LockSettings], but if you do that it will end up covering other things at times.

I've given up on having this program cover the entire time and have instead set it so that it appears over the task manager button in really tiny text.
[Touch Diamond, MDA Compact IV Themes and Apps] toadlife:
lanscape settings for battclock?

Love this app! It's the best lock app I've seen.

Would it be possible to support landscape settings (like ClockWidthLandScape) for the clock, like the standalone version of BattClock?
[Touch Diamond, MDA Compact IV Themes and Apps] r00sick:
ZuinigeRijder, hi again

2.10.3 is great for my Omnia, thanks!

But one more question:

I like to use InCallTweak so much, but i like to use G-Sensor very much. Can you make configurable orientations of InCallTweak action. I don't need screenoff when facedown (as I remember, currently InCallTweak works when "portrait", "reverse landscape" and "face down"). I like to end call by "landscape->facedown->landscape" and I can't do this.

Thank you ;)