yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for pointing out. I pointed now to the Quickstart and Features on my website in the first post, because that is better readable. And I do not need to keep 2 tables up-to-date.
[Touch Diamond, MDA Compact IV Themes and Apps] GTx-M.M:
Thanks for amazing software
[Touch Diamond, MDA Compact IV Themes and Apps] NeoXTC:
Hi Zui,

I tried what you did but didn't seem to work. (I did have HTC Api enabled and TF3D workaround)

Please find attached is the debug info. This is copied right after I tried calling it and didn't work (ie I can't slide2answer )

Thank you.
[Touch Diamond, MDA Compact IV Themes and Apps] bluefisher:
Thanks a lot!

I've downloaded the vision the 2.7 to install, and it's all working now! thanks again!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You configured the non-default HTCLockAPI = 1, where it is not possible to only lock the hardware keys (this API locks the hardware keys as well as the TouchPanel).

So you need to configure HTCLockAPI = 0 to have the possibility to only lock the hardware keys and have the slide2answer possibility. With HTCLockAPI = 1, you always have to first unlock via the available sensors/means, before you can continue.

With TouchLockPro version 2.7, the only disadvantage of HTCLockAPI = 0 is that the Home and Back key cannot be intercepted. And if there is another application which uses the same keyboard hook, than HTCLockAPI = 0 will also not work.

Is there a special reason you want to use HTCLockAPI = 1 :confused:

Anyway, you have to choose what is the most convenient for you, both options have their restrictions.
[Touch Diamond, MDA Compact IV Themes and Apps] NeoXTC:
Hi Zui,

Thanks for the awesome support :) The reason why I have the htcapi there cos I was just playing around.

But there's a bug when I turn it off (I think anyway)

Like I turn it on, turn off the phone, call my phone. yes I'm able to answer it by slide2answer. But after that if I lock the phone, it won't unlock anymore UNLESS I pull out the stylus. Cannot use the navsensors. have not tried to use g-sensors cos I never use gsensor (tried it once and didn't work that well for me)

Once again your program kicks ass :)

Btw I'm using a Diamond as in my signature

[Edit] upload debug trace
[Touch Diamond, MDA Compact IV Themes and Apps] ederhj:
Most time software works

Hello,

software works, but not always.

The screen shows, that the screen ist locked, but it isn't.

How can you help me?
[Touch Diamond, MDA Compact IV Themes and Apps] NeoXTC:
dude........ummm do some pre-lims test first maybe? exact steps? Seriously cos he may help you or he may not.....:cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you have the problem with the latest version 2.7 :confused:

If so, enable debug logging, reproduce the problem, note the time and post the debug log file \TouchLockPro.log.txt as zipped attachment.
[Touch Diamond, MDA Compact IV Themes and Apps] peetx:
with new version my device freezes when typing and had to deinstall to use again. too it freezes when device was locked/unlocked twice or three times with stylus. when not frozen at that time no further lock is possible!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, is there a special reason you disabled the light sensor?

I see UnlockOnLightSensorTime = 0.

You should set it to 500, so it unlocks normally when there is light sensed.

If I remember correctly, you use TF3D, so there is a known issue (call it a HTC bug), that sometimes the NavSensor is no longer reacting. But the TF3DWorkaround is not working with the new hardware key locking, because the tab right-ledt is also catched :cool:

Also the GSensor is usefull for unlocking, but you need to make the unlocking more relaxed. By default I do not want it unlock too easy. But you can consider from any position to portrait, e.g. CmdOrientationSequence1 = 93.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, I use it already for a few days without problem.

Can you enable debug logging (LogDebug = 1), reproduce the freeze, note the exact time and post the debug log file \TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] burningwheels:
I would like to say this is the best and versatile locking program i have encountered so far. It beats all the others S2U2, PocketShield etc...

May I suggest a new feature? I would really like to be able to draw a text or an image on the screen when the phone is locked. I don't really use the icon. I would like to make the line/streep as big as the top start bar and put a text inside it that says "phone locked" for example. I downloaded the project from sourceforge to try to add this feature myself but I can't seem to open the solution.

I'm sure this feature won't be to difficult to implement.

An option to choose the text, font/size and color would be great.

Also i had one problem with the new version 2.7 on my diamond2. By default the option "Double Touchpanel Lock" is checked. With this option checked the lock function stops working. Also I hear no beeps. Maybe you can check it out.

Thanx for a great application
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the compliments :) Of course the other solutions have also their advantages, like some nice counters/looks and so on. I keep focussed on letting TouchLockPro lean and mean and still very versatile.

Indeed this should be not too difficult. Currently you can already configure the size of the BattClock/Stripe. And also the font size can be configured already. But you want to have different settings for the BattClock when the phone is unlocked and locked. And of course you want to configure a Text or Icon or Image to display when locked or unlocked. The icon was already on the wish list.. I will put this one on the wish list too. Probably the easiest to do is to configure just an overlay image as an option, with the left upper location and do not fiddle around with texts and font sizes.

You should be able to just open the solution. Note it is a Visual Studio 2008 solution, so maybe you tried to open with Visual Studio 2005? Or you did not have installed Windows Mobile 6 Professional SDK :confused:

I do have a Diamond, so for me it is difficult to test on a Diamond2 ;) Strange that the double lock is NOT working on a Diamond2. Because I added as addition, the power off of the TouchPanel, via a standard Windows Mobile API. Can you enable Debug logging (LogDebug=1), reproduce the problem with double locking and post the debug log file \TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] Noonski:
Only 318 Downloads,

Damn shame for such a nice app.

Hulde!

Let's see how well it configures, hoot.
[Touch Diamond, MDA Compact IV Themes and Apps] burningwheels:
I've added the log file for you. I will verify that i have the SDK installed and try to open it again in in Visual Studio. Bedankt!
[Touch Diamond, MDA Compact IV Themes and Apps] burningwheels:
I can now open the solution in Visual Studio. I am a c# developer not c++ could you tell where in the code the line/streep is drawn to the screen?

Thanx!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
File: clock.cpp

Method: void ClockPaint(HWND g_hClockWnd)

See method calls DrawText
[Touch Diamond, MDA Compact IV Themes and Apps] mikes666:
If I want to use the Nav Sensor in order to lock/suspend my HTC Diamond device I firstly have to press on BattClock icon and then command the Nav Sensor.

Why am I not able to use Nav directly without pressing on BattClock?

Is this normal? .. or maybe I've missed a setting somewhere...

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] mikes666:
Reading above I can see there are issues with 2.7 on latest ROMs for capacitive sensor. Probably I'm having the same issue here.

Anyway.. with or without a fix for my little problem here.. this application is really awesome.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually it are the number of AppToDate Users. The download count is more than 50.000 times.

freewarepocketpc reports alone already more than 22000 downloads.

Bedankt! ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I only see once it wants to lock:

8:57:35 1317050810 Lock(true)

And then the settings was:

8:57:28 1317050810 DoubleTouchPanelLock: 0

I only see several attempts to unlock, apparently, becayse the TouchLockAction is running?

8:57:46 -385661994 GetActionStatusString(): Command

8:57:46 -385661994 ==value====: !UNLOCK

8:57:46 -385661994 Command: !UNLOCK

8:57:46 -385661994 ExecuteRequest(): !UNLOCK

8:57:46 1317050810 ClockWndProc(WM_TIMER): 26

8:57:46 1317050810 EXECUTE_REQUEST: !UNLOCK

8:57:46 1317050810 Execute(): !UNLOCK

So I am a bit confused, did this log not contain the problem that DoubleTouchPanelLock was not working :confused:

It is best to start with a empty TouchLockPro.log.txt, soft-reset your device with the setting DoubleTouchPanelLock =1, and then reproduce the scenario, so I can better see why DoubleTouchPanelLock does not work for you.

Hope we can find together the problem :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, for TF3D users, the navsensor sometimes stops working. The TF3DWorkaround does not work, because the simulated presses are blocked by the new keyboard hook. I need to fix that. But then, still it is possible the navsensor does not always work in TF3D, because HTC screwed this up :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi,

I just installed V2.7 and I can't remember how to setup the app to have the touch screen enabled on incoming call and this without the touch keys enabled.

Actually it's locked until light detected, so I can't answer quickly if not enough light and miss some calls :-(

BR

SOLVED: Enabled "Lock on incoming" and "Key only"
[Touch Diamond, MDA Compact IV Themes and Apps] treqq:
for QVGA Htc .....

any hope to have a QVGA version? ( for htc polaris as well?) :p

many thanks bye
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
KeysOnly (LockWhenIncomingKeyOnly = 1)

With the new version, I also advice to have a key unlock sequence. On my Touch Diamond, the middle button works well: UnlockedKeySequence = 134
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Previous versions were only usable on newer HTC phones, which were VGA or better. Now indeed it should work on general windows mobile phones. It is much work for making TouchLockAction in QVGA. For now, you can just use a registry editor for making your changes (not so nice, but it works). I assume this is your main interest.

I actually do not know how many people are using it on non-HTC phones. And because I do not have a QVGA phone myself, it is difficult to see how it looks in QVGA (I can only use the emulator). So for me it is still a question if I want to spent the effort. I hope someone can help, because the source code is available on sourceforge. That would be cool :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] treqq:
.... For QVGA HTC ...

absolutely yes :)

no problem to change the registry but... does someone know what are these changes?

I try to read the thread ( a little long :p ) but I didn' try any indication...

currently I'm using S2U2 but I have some little problem....

thankssss

p.s. great work anyway
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
See Settings page, which is mentioning:

It is also possible to overrule the default settings via registry: HKCU\Software\ZuinigeRijder\LockSettings Please use a registry editor to create the DWORD values, e.g. PHM RegEdit. A value of 0 means No and a value of 1 means Yes. The default DWORD value is also mentioned. Please make sure to do a soft reset after adding the appropriate overrule settings via a registry editor. You only need to define the values you want to overrule.

For all the settings, the registry key is mentioned with the default value and the explanation onwards. TouchLockPro has created the default keys when started, so you only need to change the values you want to change.

Probably you want to configure a key unlock sequence: UnlockedKeySequence = ....

Probably the sensors will not work on your phone, but TouchLockPro will detect that, so you do not need to disable them.
[Touch Diamond, MDA Compact IV Themes and Apps] honekr:
HTC Touch Pro

TouchLockPro 2.7 don't work with my HTC Touch Pro2. I installed it and I tried various settings, but TouchLockPro doesn't works.

I use TF3D, TP2 ROM version is 1.19.401.0, TP2 is localized into Czech.

I don't know what I should try more.
[Touch Diamond, MDA Compact IV Themes and Apps] MaxLaw843:
TouchLockPro 2.7 work on Palm Treo Pro?

Does the TouchLockPro 2.7 work on Palm Treo Pro, which has a 320 x 320 screen? :confused:

I installed it and ended up with either a larger black spot or a black spot with numbers (two rows--neither of which was readable) in the area at the top of my screen, where my battery and time are located. Tried altering the setting on TouchLockPro 2.7 to eliminate battery indicator, but it would not work for me. Thus, I uninstalled due to this.

Good concept, but did not work for my phone, which is made by HTC but obviously does not carry the HTC name.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I know from the Diamond2, that only a few sensors work, so I expect the same for the Touch Pro2. So probably you need to configure a key unlock sequence, e.g. volume down/up, UnlockedKeySequence = 118,117

What is not exactly working?

Is the BattClock not saying it is locked after power on?

Or is the TouchPanel and/or hardware keys not locked at power on?

You can enable LogDebug = 1, reproduce the problem and post the log file \TouchLockPro.log.txt as zipped attachment. In combination with the answers of the above question, that can give me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The default settings are for a VGA screen. I expect with 320 x 320 screen there are less pixels available for the BattClock.

I did run it on the Windows Square QVGA emulator, which shows this.

So yes, with the default settings, it looks not nice.

I believe the correct icon size for your phone is 36x36, so you have to change the defaults, via the registry:

HKCU\Software\ZuinigeRijder\LockSettings

And change the following values (all numbers are decimal):

ClockWidth = 36

ClockHeight = 36

ClockX = -72

FontSize = 10

That gave me in the emulator the next result:

Of course you must adapt colors to your wishes.

And you need to configure an unlock key sequence, e.g. Volume Down/Up:

UnlockedKeySequence = 118,117

Hope this helps :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] Jon811:
Please, would you like to tell me,what settings am i have to do if i want, that my Touch Pro blocks by any wake up, except power key?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately I cannot distinguish if the power button is pressed or that an external event has wakened the phone. I only can detect incoming calls. If someone knows how to detect that the power button is pressed, I can add support, but with the current keyboard hook this is not possible, as I know of.

Of course you can setup your phone that it does not awake by an incoming SMS, make sure no alarms or other programs awake the phone and only lock on incoming call. But this is dependent of your usage pattern and how you like to setup your phone.

In general you must unlock your phone by one of the available means on your phone....
[Touch Diamond, MDA Compact IV Themes and Apps] zodiac:
That's just really too bad!! :(

I installed it on my diamond (2.03 stock with TF3d) for the navsensor type of locking. I wanted to use this for the extra security of using my own touch sequence to unlock.

I am using Throttlelock for this, but it consumes from 400KB to 1MB of RAM.

Touchlock pro is a lot lighter!!

But.. because of HTC's TF3D I can't use that type of navsensor unlocking. And that's just too bad!! :( :(

TouchLockPro is a fantastic concept, I really like how you kept it small and light, but still very powerful. :) But I'm going back to throttlelock right now for the 'security' :(. If the navsensor-unlocking works on my Diamond with TF3d, I'll start using TouchLockPro.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the comments.

I am going to fix the TF3D workaround in the next version.

But you can also configure a secret key unlock sequence, which is possible since version 2.6.
[Touch Diamond, MDA Compact IV Themes and Apps] zodiac:
That's great! Thanks also for notifying me of the key unlock sequence!!

Going to uninstall throttlelock and give TouchLockPro a go with this key unlock sequence. :D
[Touch Diamond, MDA Compact IV Themes and Apps] germanxdafan:
What about TF3D2? Is there also the same problem with the navsensor?
[Touch Diamond, MDA Compact IV Themes and Apps] burningwheels:
Ok I reset the phone after deleting the logfile and setting double lock to true. After the phone was started I switched off/on the phone. Nothing happened as if touchlockpro was'nt running. Normally it would go to locked state. Then I switched off double lock turned it on/off again. This time it works normally. Hope this helps. Also sometimes the program thinks the phone is locked but actually the touchpanel as wel as the hardware keys are active. I haven't found a way the reproduce this behaviour.

Thanx!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The Diamond2 has a different navsensor, a zoombar navsensor. HTC has a different API for that, which is not known (yet). If someone knows how to read out the Diamond2 Zoombar, I am glad to add support. Are there some good reverse engineering guys around :confused: That is also how the NavSensor of the Diamond is found out, HTC made also this API not public :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I see you configured pressing twice the Talk button for unlocking. Makes sense, because you do not want to accidently reject the call. See also that you configured the Home button LED to be on ;)

But now back to your problem.

I see:

23:34:46 662411174 Slider INVALID_HANDLE_VALUE

I see several times:

23:35:35 662411174 GetActionStatusString(): Command

23:35:35 662411174 ==value====: !UNLOCK

23:35:35 662411174 Command: !UNLOCK

23:35:35 662411174 ExecuteRequest(): !UNLOCK

When you did chanmge it back to:

23:36:00 -1384384294 DoubleTouchPanelLock: 0

I did not see this anymore.

So I expect a problem related to the ActionStatusString. TouchLockPro does automatically unlock, when TouchLockAction is active in the Settings screens (TouchLockAction sets the !UNLOCK command). So I expect there is something wrong.

I checked my code. I set this registry key in TouchLockAction, when I open the Settings Index screen and when I stop TouchLockAction in a normal way.

It looks like I need to reset this key at startup of TouchLockPro.

Also the slider INVALID_HANDLE is puzzling me. I am going to check my source code further.

***EDIT***

I checked the source code, the SLIDER invalid handle is expected. I will change the log message, so it is less alarming (it just ignores the keyboard slider).

I also checked the !UNLOCK, and it seems to look Ok.

I do not understand why it does not show POWER OFF messages with Double PanelLock enabled. The logfile does not give me a clue (but maybe I miss something).
[Touch Diamond, MDA Compact IV Themes and Apps] germanxdafan:
No, i still have the diamond 1 but i want to flash this rom http://xdaforums.com/showthread.php?t=521941

So i will have tf3d2 on the diamond 1.

But if the tf3d2 doesn't use the old navsensor of the diamond 1 since it was made for the new diamond 2 navsensor,

there shouldn't be a problem with your touchlock app, right?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The design of TouchLockPro is, that when a sensor is not available, it is ignored by TouchLockPro. So probably the NavSensor feature will not work after flashing that ROM, or the old NavSensor is still part of the ROM, and then it will continue to work.

I also see something about:

Gen.Y SensorSDK 3.3.18192831.1 The HTC Camera has a slight rotation issue with the new SensorSDKv4

So maybe that GSENSOR will also give problems. Hard to tell if TouchLockPro works with exactly the same amount of sensors. Maybe you can ask on that specific forum if TouchLockPro works on that ROM? And if all sensors still work?

In general TouchLockPro will work, but maybe not all features....
[Touch Diamond, MDA Compact IV Themes and Apps] burningwheels:
Indeed i use set pressing the talk button twice to unlock. The diamond2 does'nt accept the Windows key or the back button. Only the talk, hangup and the volume keys work. Otherwise I would probably go with the windows key. On the diamond2 i think there are no seperate led per button. I didn't set the Home button led to be on. The setting shows an orange led next to the phone speaker. I guess the Diamond2 is quite a bit different than the original Diamond. I hope you can find out what the problem is.
[Touch Diamond, MDA Compact IV Themes and Apps] joachim74:
Touch Pro2 not locking

It is also not working with my Touch Pro2 - it doesn't lock or suspend!

If I go to settings and click on lock or suspend, then the settings just disappear and nothing is locked :confused:

Any idea?

Here is the debugging log:

23:15:46 Main() [System.String[]]

23:15:46 Actions.ActionTLPCommand(!UNLOCK)

23:15:46 Actions.SetActionSettingsKeyValue(Command, !UNLOCK)

23:16:21 Actions.ActionTLPCommand(!LOCKSUSPEND)

23:16:21 Actions.SetActionSettingsKeyValue(Command, !LOCKSUSPEND)

23:16:21 Actions.Exit()

23:16:21 TouchLockActionActive() False

23:16:21 Actions.ActionSettingsChanged()

23:16:21 Actions.SetActionSettingsKeyValue(SettingsChanged, 13)

Because of my Exchange settings (?) the system lock (within max. 30min.) can not be switched off - might this have to do anything with that problem?

Would be great if I could use this brilliant tool!!

Thanks!

Joe
[Touch Diamond, MDA Compact IV Themes and Apps] Goondu:
Hi

I was running your wonderful application (ver 2.6.6) well in my Topaz with the TF3D switch off. The program works flawlessly on my Topaz with MS3.

Few days ago, I turned my TF3D back on and some of the functions in your program are not working.

So I installed the new ver 2.7. And now nothing works.

I tried uninstalling and soft reset. Install 2.7. Soft reset. But it doesn't work.

I get the error message after the phone boots from soft reset -something about TouchLockPro is not working.

I am running the standard ROM on my Topaz

Attached is my log file

12:38:04 166560282 ERROR Could not open registry key System\CurrentControlSet\Keypad

12:41:27 -1386512422 ERROR Could not open registry key System\CurrentControlSet\Keypad

12:43:24 117925666 Error in SetWindowLong: 1400

12:43:26 -1386512422 Error in SetWindowLong: 1400

Please help

I will try to go back to ver 2.6.6 to see if it works

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] honekr:
I can't lock my device - in no manner.

BattClock show battery status and clock, but when I want lock my TP2, it's no go. TP2 stills unlocked. After power on too. :(