yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
De log file you can find in the top of the phone memory \TocuhLockPro.log.txt. But because it is working now, there is no need for the log anymore.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmm, normally I use the HTC lock API, which also locks the TouchPanel on top of the other way of locking the touchpanel. So you would only see this happening with LockTouchPanelOnly = 1. With the new hardware key lock, only the touchpanel hook should lock the touchpanel.

When it occurred on my phone, I even debugged the code if all the steps were correct. And everything was going as it should do, BUT it did not lock the touchpanel correctly. Even older versions had the same problem, so it was not a new programming problem. So I was really confused and I think there is then something inside Windows Mobile wrong.

I am interested to know how you repair this problem. Just full power down and power up again?

I will see if it occurs again with me too. But it looks the TouchLockPro code is correct :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] Slide:
Hi ZuinigeRijder,

the problem is now back:-(

Here is my log file.

Greeting

Slide
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, a side-step first. I see you did unlock the middle button and also use the middle button as unlock sequence. Note that you do not need to unlock the middle button, to have it as unlock sequence. This means, still actions with the middle button can be done, while locked. Did you have a special purpose for that?

In the logging I see:

13:31:19 1709823678 HookTouchPanel(true)

...

13:31:25 1709823678 SetUnlockedRequest()

Where this unlockedrequest is coming from, is unclear for me. I suspect the Keyboard hook, but there is no key logged. So I expect it was just the middle button press. I will add some logging in version 2.6, but the logging looks ok at first sight.
[Touch Diamond, MDA Compact IV Themes and Apps] Slide:
No, only for a test.

Greeting

Slide
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.6 with *NEW* hardware keys locking

I just uploaded version 2.6 with the *NEW* hardware keys locking.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
One word WOW :D

I like the LED effect, now I wonder if I still need the red stripe. I like the idea of using a hard button to unlock. I also tested the problem I had with bluetooth calls, fixed :) Have you made some code improvement, I find it unlock more quickly?

On small thing, the DetectBluetoothLightUnlock = 1, I had to untick it, to make it unlock on light sensor. Is it possible it coded wrong? Or, I just don't understand :rolleyes:

Thanks, Eric
[Touch Diamond, MDA Compact IV Themes and Apps] NeoXTC:
a long time s2u2 user here, finally decided to give this a try and I love it compared to s2u2. It's simple and it works. Great work man. s2u2 RIP :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Indeed you can consider the stealth mode. But the LED's will only controlled when the lock is activated after power on. So if you manually lock the phone after using it form some time (e.g. more than 30 seconds on), it will not control the LED's. This is for people who want to use this in combination with GPS. They want to have the screen on and still locked. And then the LED's behaviour is less nice I think.

I improved the keyboard hook a bit, so I only check for key up for the unlocking sequence. Is that what you meant with it unlocks more quickly?

You are right about the DetectBluetoothLightUnlock, the condition in my source code is wrong (the opposite). I will fix that in the next version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for trying out :)

I think s2u2 is more popular, because it can be used on any phone. And it has a sexy look. Till this version, TouchLockPro was only really usable on the newer HTC phones. But now it must be usable on other types of phones, because of the *NEW* hardware key locking. And the option to lock only the hardware keys at incoming call in this new version, makes it easy to use in combination with Slide 2 Answer solutions.

Of course each solution has its advantages and disadvantages. So everyone has to choose its own beast. I want to keep TouchLockPro small in memory, 0.0% CPU usage and still powerfull. From battery perspective, I think TouchLockPro is the best solution.

I experienced lately a doubling of the downloads, because I asked freewarepocketpc to update the version to 2.5.4. So it is also a matter of people knowing TouchLockPro exists......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not know how it can happen it does not lock the touchpanel anymore, even after power down or soft reset. This is a mystery for me too.

You can enable the HTC Lock API, because that locks the TouchPanel too in a different way. But then you cannot use the added features of the new version 2.6 and the hardware keys are locked too.

What helped me to get it locking the TouchPanel again, was:

- deinstall TouchLockPro

- power off the phone completely

- power on

- install TouchLockPro

But currently I do not have a clue what the cause is of this.
[Touch Diamond, MDA Compact IV Themes and Apps] powerbar2:
Some feedback for the new version on my Diamond:

- TouchPanel wasn't locked, too. After deinstallation, softreboot und installation, everything works.

- The new Hardwarebutton lock is superb! Finally I can lock everything but the power button to check the time and for my meetings.

- And the TouchPanelOnly function for calls is also very usefull, so on any newer HTC Rom, you can use the build-in slide-to-answer function. (But still with HW Buttons locked, i love it :D )

- There is one problem left: the capacity sensor won't work correct in TF3D Homescreen - and i think in the new version, the workaround is broken? At least it doesn't work for me. But this really was just a nasty thing, isn't there any chance for a real fix? Any clue where the problem is located? (for you information: in my case, it didn't depend on the TF3D version, i used exactly the same with ROM 1.93 and 2.03 (both german o2). Only in 2.03 the bug exists :(

Thank you, the new version is really improved (love the new HW button lock), but still, I can't unlock my HTC Diamond the great way (= with NAV buttons).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for taking the time and effort to give positive feedback on your first post :) Indeed I think this is a major enhancement to TouchLockPro.

Yes, the TF3D Workaround will send a key right and key left, which is intercepted by the *NEW* hardware key hook :rolleyes:

If you unlock the key left and key right, it will do the TF3D workaround after 5 seconds or so. I really do not know how to really solve the NavSensor problem, I still think that HTC did screw up something, because it is working on older ROM's, like you say.
[Touch Diamond, MDA Compact IV Themes and Apps] NeoXTC:
this is weird.

I have the htc diamond with shaks 4.3 Lite ROM (got spb mobile installed) In version 2.5.5 everything seems to work correctly in version 2.6. Just then it says my phone is "locked" but I can still use everything.

This morning i had "areset manager" to reset at 2am, when I woke up it's locks (yes this is fine) but when I tried to unlock it with the NAV sensors, didn't seem to work. I had to pull the stylus out. the NAV sensors didn't work anymore until I had to soft reset.

I'll try uninstall, power off completely and reinstall and see if it works like 2.5

Cheers for the great app.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Awesome!

I can't wait for the 2.6 source code!

Excellent work ZuinigeRijder!
[Touch Diamond, MDA Compact IV Themes and Apps] hgrimberg:
Problems with 2.6

I tried to install version 2.6 on my HTC Diamond but a window pops up saying: "Failed to disable Touch lock Pro" and then it says Installation was unsuccessfull. I previously had version 2.5.5 which I uninstalled before trying to install this new one.

Thank you very much.
[Touch Diamond, MDA Compact IV Themes and Apps] NeoXTC:
Hmmm I've tried installed 2.6 again but yeah it doesn't seem to lock properly....It says "locked" but then I can still use all the keys and stuff.

Process I did: uninstall touchlock

turn off power

turn on power

install touchlock 2.6

reset

It seems to lock pretty good for awhile, but I think I noticed it not locking after I plug into pc and got activesync. After I remove it form activesync doesn't seem to lock...

I'll try more test this weekend. I'll go back to 2.5.5 for now.

Cheers
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have created a project on SourceForge.net. I am awaiting approval (can take 3 days). So from then on, the source code is available there, via there (subversion)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Sorry for the inconvenience. I myself use mostly ActiveSync via Bluetooth. Maybe via that means the problem is less? I will try out also with 'normal' ActiveSync myself, because it is an annoying problem.

I will recheck my code and add logging. Maybe there is somewhere a race condition. What I do not understand, is that the problem persists, even after power down or reboot. Only deinstalling TouchLockPro power off and installing again seems to solve the problem (sometimes).

Anyone having Mobile Programming experience having an idea of this weird behaviour? Somewhere a cache?

Instead of going back to 2.5.5, you can also enable HTC Lock API in 2.6. That will lock the TouchPanel also in a different way.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Is the directory %Program Files%\TouchLockPro empty?

After deinstalling there should be only a language directory/file for TouchLockAction.exe. You can remove that directory (if there is no TouchLockPro.exe in that directory) and try to install again.
[Touch Diamond, MDA Compact IV Themes and Apps] Kraize:
I have a question. Since this is such a great locking app, I have no requests to add a locking feature! but more of a standby feature. Just like s2u2 and pocketshield. Think you could add a screensaver sort of thing? That maybe goes away after you unlock? That would be nice to see for notifications and such! :) I mean it could just be a picture screensaver that displays until you unlock your device. That might up memory usage a bit, but it would look nice and protect people from even looking at my phone.

Or do you think integration with s2u2 is possible? I use it for notifications and music as well as locking :) I think that touchlockpro has some cool features that I need as well, but it doesn't play as nicely with s2u2 as i would think possible. I second the motion to make a notification icon rather than battclock :D + integration with the new wm6.5 lock would be nice because it has new notifications capabilities and it's basically a slide to unlock :P (Bet they ripped it off s2u2 anyways).
[Touch Diamond, MDA Compact IV Themes and Apps] NeoXTC:
No need for the apologies. You're doing great work, I'm a developer myself so I know what's it like to have bugs and stuff :) Thanks for the effort u putting in to give us this program :)

I'll give 2.6 another play and try that htc lock api and do more testing for ya. It's always good to have heaps of testers so you can reproduce the problem so you can fix it :)

Cheer man. and keep up the good work.
[Touch Diamond, MDA Compact IV Themes and Apps] NeoXTC:
Ok 1st test. (oh sorry for leading you on the wrong track b4 I don't think it's to do with activesync)

Device unlock

I've suspend the device by clicking the power button.

press a hardware key button to wake up

a red stripe up to (to show that it's locked)

but It's not really lock. I can still scroll, touch, use hardware button etc.

I can't lock the device anymore, using either nav sensor, or running the app and pressing lock.

I'll try playing with the config settings to see what I can come up with.

Cheers
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, thanks for the testing effort so far, I appreciate that.

Does this mean you have set the Windows Mobile setting to awake on any key? Because I normally do not use this setting (only awake on power button).
[Touch Diamond, MDA Compact IV Themes and Apps] NeoXTC:
Yup I've got wake up on any key.

Want me to disable wake up on any key and test it with power button?

On another not, putting htc api checked, everything seems to be working normal again for me like 2.5.5. so it seems like the new hardware button lock is the culprit.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The HTC Lock API does also lock the TouchPanel. There were always 2 mechanism active, but because also the HTC Lock API was active, nobody noticed this problem of locking the TouchPanel in the second way.

At suspend, the TouchPanel hook was active (and not the HTC Lock API), so the power button was unlocked (EnableInputAtSuspend). At power on, immediately the HTC Lock API was done. But there was a very small chance that the TouchPanel was pressed, before the HTC Lock API was called. Therefore the second way of locking the TouchPanel. But apparently this is not reliable always *sniff*. And this mechanism was active for those who did NOT use the hardware key locking (LockTouchPanelOnly = 1).

So I think it is not the new hardware key locking, it is TouchPanel hook which was not working always for a long time :eek: With the new hardware key locking I solely rely on the TouchPanel hook :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ugumba:
Thanks for a great update! Finally, I can start using TLP as the only locking utility on my Touch HD. (As earlier stated, my top wish is a slide to unlock method, without overlay, like CSDevCtrl.)

I've enabled "triple-hangup" as the unlock sequence for the time being.

The touch panel is properly unlocked during an incoming call, so I can slide to answer or ignore. This part is now the leanest, meanest I've experienced to date!

However, the touch panel remains unlocked after I've ignored the call. Is this intentional? The keys are locked at this stage, and the BattClock is inverted (indicating a locked state).

The quick fix is to suspend with power key - when I resume afterwards, everything is locked properly.

Edit: I now received a call which I answered, and the panel seemed to lock a few seconds after I hung up the call. Maybe there's an issue with just ignoring the call?
[Touch Diamond, MDA Compact IV Themes and Apps] paalkr:
Hi!

Tanks for this new version 2.6! To me this non HTC locking mechanism is great. I would like to suggest an additional feature though, and that is to override the light sensor unlock at an incoming call (in the same way as if bluetooth is connected), so that the hardware buttons stays locked (even if the light sensor unlock is enabled).

Regards,

PK
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
My fault ;) I indeed enable the TouchPanel at incoming call, but forgot to disable it again at end-call, when it is still locked. I will fix this in the next version.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Test version: 2.6.1

Ok, I made a test version 2.6.1 to find/solve the following problems:

- Disable TouchPanel after end call

- added error logging for TouchPanel (errors will be logged now, regardless of debug flag)

- improved TouchPanel hooking (but do not know if it helps :confused:)

- DetectBluetoothLightUnlock condition reversed

Hope we can find the problem better with sometimes no TouchPanel lock.
[Touch Diamond, MDA Compact IV Themes and Apps] paalkr:
Hi!

Quick "deliverable" as usual :)

Regards,

PK
[Touch Diamond, MDA Compact IV Themes and Apps] hgrimberg:
There is no TouchLockPro directory under any Program Files, nor on the Internal storage, nor on My device. Nothing was left after uninstalling the previous version...

Thank you for your help.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Where did you find the LED control functions? I am mainly interested in that part at the moment.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, so it should just install.

Apparently version 2.5.5 installs but 2.6 not. Very strange.

You can try to remove the registry tree: HKCU\Software\ZuinigeRijder

And then install version 2.6.1...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, it is very simple, if you know it. I tried searching on LED1: and found then the clues.

This is the relevant code, that is all:

// LED control
HANDLE hLED = NULL; // handle to the LED control
struct SLedSet {
DWORD	ledNum;
DWORD	ledState;
};
void OpenLedControl() {
if (hLED == NULL) {
hLED = CreateFile(L"LED1:", GENERIC_READ | GENERIC_WRITE, 0 ,0 , OPEN_EXISTING, 0, 0);
}
}

void SetLedControl(bool on) {
if (hLED == (HANDLE)-1) {
return;
}
DWORD ledNumber = pS->GetLedNumber();
if (ledNumber == -1) {
return;
}

DWORD ledState = (on ? 1 : 0);
SLedSet s = {ledNumber, ledState};
DeviceIoControl(hLED, 0x8002001C, (LPBYTE) &s, sizeof(s), NULL, NULL, NULL, NULL);
}

void CloseLedControl() {
if (hLED != (HANDLE)-1) {
SetLedControl(false);
CloseHandle(hLED);
}
}
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
YeS! ThAnKs!
[Touch Diamond, MDA Compact IV Themes and Apps] Slide:
Hi ZuinigeRijder,

here is the Log File from Test-Version 2.6.1.

The problem always comes back :(

Greeting

Slide
[Touch Diamond, MDA Compact IV Themes and Apps] ugumba:
Touch panel active in certain cases (when locked)

Here's a nice bonus feature (I'm on 2.6.1): Open all SMS messages (the classic WM messaging app), then suspend+lock with power button, then resume with power button again.

TLP appears locked (white icon), no buttons work except Home (which is a fantastic touch, by the way - I can always check sms/mail/calendar without unlocking!).

Now, with the messaging app open and locked, slide finger down the message list, and the list scrolls! :-)

The same seems to happen in any standard WM window with a scroll bar: touch scrolling is enabled even when locked. It works in Orneta Notepad (when SIP is off), but not in PIE (nor Opera).

If you you did this on purpose, ZR, you're a genius. Since only scrolling is enabled (no context menu or other "clicking"), it should be without risk in practically all cases. You may want to add an option to enable/disable this behaviour, just to play it safe.

If you didn't do this on purpose, this "bug" should really be turned into a feature. It's excellent, and on par with being able to use the Home button while locked.

If this was a feature, I'd wish for it to work with more apps/windows/lists.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked into the log files, and I do not see anything strange. The touchpanel hook reports exactly what was expected. I must say, I did have this problem only twice. And with version 2.6.1 I did not encounter it anymore.

But you have this problem :mad: And I expect more people too, sometimes. To avoid this problem you must use the HTC Lock API, but then you cannot use the nice *NEW* hardware key features.

If we can pinpoint the exact situation when it occurs and is introduced, we may find a solution. But for now I do not have a clue. Hope others, who also have this problem sometimes, can help in finding the cause.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, I knew the TouchPanel locking method was allowing the task bar and scroll bar to be active. But because the HTC Lock API *also* locks the TouchPanel, so people who locked also the keys (and that is the majority) could not use this feature.

Now, when the *NEW* hardware key locking is selected, indeed the right part of the TouchPanel is still sensitive, so you can scroll. The hooking of the TouchPanel approach has this feature, I did not do anything special for it, I got it for free :)

So yes, be happy :D with this new feature. You can even configure to unlock the left/right/up/down key, so you can even do more, while locked. Because, I think you cannot do harm by having the cursor keys unlocked (bogus calls).
[Touch Diamond, MDA Compact IV Themes and Apps] paalkr:
Hi!

I have the same issue from time to time, shall try to pinpoint when it happens ;)

BTW: Any news on the overriding the light sensor unlock on incoming call feature request?

Regards,

PK
[Touch Diamond, MDA Compact IV Themes and Apps] paalkr:
Hi!

Anyway of turning this off, and lock the touch panel completely?

Regards,

PK
[Touch Diamond, MDA Compact IV Themes and Apps] cichy3000:
Hi,

First of all I'd like to say that You've created great application ! I think that's the one and only fully customisable locker / unlocker and it's still soi 'light'

week ago I was thinking about making locker / unlocker program supporting keys... and now You've made it... great !

I've got a question... is it possible to set keys combination for unlocking purpose - bringing phone to 'life' from lock&suspend ? (I'm using HTC Diamond) (when my phone is in Suspend and Lock mode without backlight) I would press for ex. center key and then home key (or any other combination) and then phone would be unlocked, screen goes to normal (backlight ON and NO suspend)... is it possible in this version ?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The light sensor unlock disable at incoming call, I will put on the wish list.

What do you do to get rid of the problem, when it occurs? Desinstall, power off, Install?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, with the TouchPanel hook, this is not possible, as I know of.

The only way to do this, is to have an own foreground window......

Maybe I must make an option to have a foreground lock window, for people having problems with the TouchPanel lock or the hardware key lock or want a complete touchpanel lock.

The problem will be, that this will cover other windows, so the information behind is not visible. I can make a transparant look, so the background is shown just before the lock window is put on top, but real transparancy is not possible in windows mobile :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
If the phone is really suspended, it is not possible to wake it up by software (all software is standing still, consuming *NO* CPU cycles). However, you can configure in Windows Mobile to power on on *ANY* hardware key press. But this is not practical too, because in your pocket it will awake too often, because the hardware keys are pressed too easy in your pocket.

TouchLockPro has 2 commands (backlight, screen), keeping the device awake, see here.. So if you do a !LOCKSCREEN first and then a !SCREENOFF, I think I can detect button presses (you can check by enabling debug logging and see if those key presses are blocked). And if I can detect them, I can also do a screen on :rolleyes: But this will cost more battery, because all programs keep running (using CPU) in the background, although the screen/backlight/sensors are off.

Can you check this scenario, if keypresses are detected above :confused: