yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Normally, it will not lock the Home key and Back key. Did you change the order of the keys by some tool? Also if some other program is using the same hook procedure, then the first one will win.

From 2.6 onwards there is another locking method, before it was HTCLockAPI = 1. So if you want the same behaviour as before 2.6, configure that, but you miss some new features. Why the TouchPanel is not locking for some people, I do not know. The only thing I know and can reproduce is when you do not enter the SIM PIN code before TouchLockPro locks after boot or reset. And when this is not done, it will not lock till you reboot again and enter the SIM PIN code. I do not know why it does not lock when you do not have a SIM PIN code configured or the Windows Mobile password lock.

For people having this problem, we must look for the simularities/pattern, to see why it is not locking. Have all those people no password lock and SIM PIN configured? Which programs installed. Using TF3D or not? Using another mobile today screen? Having Flight mode enabled? Bluetooth enabled at boot?

Anyway, for now, I can only advise to use HTCLockAPI =1 for people having this problem AND having a newer HTC phone. For people having a generic Windows Mobile phone and also having this problem, TouchLockPro is not the solution for them, till a solution is found. And yes, please post as much as information, so maybe we see a pattern?

With HTCLOckAPI = 1 you miss some features, so you cannot unlock via a hardware key sequence. The only way is to configure capacitive touches via the middle button (default triple touch), if you have a Touch Diamond or Touch Pro for unlocking.

If you disable "Lock all keys except the Power button", you can wake the phone by any hardware key.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can configure CapacitiveCommandsWhenUnlocked = 0.

TouchLockPro is also writing its lock status in the registry, so gscroll could make use of it, for your request. But that you must ask the gscroll author.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, I see this in the logging:

19:14:44 103166994 LOCK_SCREEN_REQUEST

..

19:14:44 103166994 SetLockScreenRequest(true)

..

19:14:45 103166994 ============================Suspend=================================

I checked my code, and it looks like these lines are calling Suspend:

if (!unlockedAfterPowerOn && (powerOnTickCount > 0) && (pS->GetSuspendTimeOutPowerOn() > 0)) {
if ((currentTickCount - powerOnTickCount) > pS->GetSuspendTimeOutPowerOn()) {
powerOnTickCount = 0;
Suspend();
}
}

Seems that unlockedAfterPowerOn is not set correctly, when unlocked. So a think you spotted a bug. Will try to solve this in the next version.

For now, you can configure !KEEPALIVE;!LOCKSCREEN, that should not suspend the device.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It is possible that you have a not working Stylus Sensor, so TouchLockPro will not lock, because of Stylus out. There can be dust between the Stylus and sensor, the sensor can be broken or you did a soft reset and kept the Stylus out, You can check in the TouchLockAction Stylus settings screen the stylus position. If it is reporting out, while it is in, you can try to gently clean the stylus sensor, by blowing away dust.

If you want the old behaviour for locking TouchPanel and keys, just configure HTCLockAPI = 1.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
See this post
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The first time TouchLockPro locks the phone is at:

8:00:36 1296207114 Lock(true)

8:00:39 1296207114 ========================UNLOCK BY LIGHT SENSOR=============================

12:06:50 1296207114 Lock(true)

12:06:50 1296207114 NOTIFY_AC_POWER

12:06:50 1296207114 Lock(false)

17:10:08 1296207114 Lock(true)

17:10:10 1296207114 ========================UNLOCK BY LIGHT SENSOR=============================

19:49:55 1296207114 Lock(true)

19:49:55 1296207114 NOTIFY_AC_POWER

These are also only the occasions of a power on request. So I think TouchLockPro did just its work.

Is this also when the reminder appeared?

When you use HTCLockAPI = 1, the power button is locked, when the phone is locked. But normally the light sensor will automatically unlock. For Touch HD the other options are taking out the Stylus or a GSensor gesture.

With TouchLockPro it is not possible to lock/unlock by pressing the power button, because it cannot detect the difference in power on via power button or other external event.

But probably HTCLOckAPI = 0 is more convenient, if the TouchPanel and hardware keys are locking correctly. You can configure a unlock key sequence, to unlock the Touch HD, when the light sensor is not automatically unlocking. And if you have a slide 2 answer solution, you can configure KeysOnly = 1, so you can still slide to answer/reject the phone at incoming call, so you do not need to unlock via a key sequence in those situations.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Probably there are no sensors for unlocking on your phone, so you need to configure a unlock key sequence. Only the functionality of a general Windows mobile phone are available to you, as described in QuickStart and Features.
[Touch Diamond, MDA Compact IV Themes and Apps] aamonster:
UnlockOnLightSensorTime = 500 - already done. It's better than 1500, but not good enough.

LockWhenIncoming=1 - ok

DetectBluetooth=1 - is not good enough: when I press "play" button at a2dp handsfree - device powers on (not locked).

Anyway, thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro cannot detect power button presses, and so cannot distinguish between power on press and power on by another external event.

So the only possibility is to use AutoLockOnPowerOn and unlock via the different possibilities.
[Touch Diamond, MDA Compact IV Themes and Apps] aamonster:
I see.

But is it possible to check conditions (orientation != upside down) immediately after power on?

Now I tuned

AutoLockOnPowerOn=1

CmdOrientationSequence1=4, CmdOrientation1=!UNLOCK (unlock when go to portrait)

CmdOrientationSequence4=6, CmdOrientation4=!UNLOCK (unlock when go to face up)

UnlockOnLightSensorTime=500

- but I need to wait 500 ms after pressing power or bow device back-forth (to change orientation and return it back to portrait/faceup)

For me, ideal behavior - like MobileMagic with "keep screen off" setting (screen cannot be turned on before device turned portrait). But MobileMagic have tendention to power drain - so I prefer your app :-)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Problem is that not on all phone types the GSensor is not working, so limiting the general behaviour you want. And before having a reliable GSensor result, will also take 500 ms. Beside that, if you have a slide 2 answer, you can configure KeysOnly, so you can still pick up the phone, and then it unlocks too.
[Touch Diamond, MDA Compact IV Themes and Apps] ederhj:
Hello again,

now I have appended my Customizing of TouchLockPro and dthe log.

With the version 3.6.3 all function was good, that means locking works. Now not any more.

Please help.

Thank U.

The other 4 files are the the next post.
[Touch Diamond, MDA Compact IV Themes and Apps] ederhj:
Please help
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The logfile looks normally.

Is the problem away, if you switch back to 2.6.3?

Probably it is the same problem as here:

http://xdaforums.com/showpost.php?p=4029610&postcount=2354

If people try to give as much of information, which programs installed, which today screen, which phone, which ROM, which settings, etc, maybe we can find a commonality in the people who experience this problem.
[Touch Diamond, MDA Compact IV Themes and Apps] paclep:
Another log, during which my Diamond seems to be locked but I was able to use the touch panel, not the hardware keys.

I log during one or two minute, and I repeat the same issue (If it is one) some times. Without changing any setting, sometime this happen, sometime not.

If it can help...
[Touch Diamond, MDA Compact IV Themes and Apps] ederhj:
I've installed 2.6.3 again.

Now locking works, but if bluetooth is activated, the phone is always locked.

I only want the phone to be locked, if a bluetooth connection is active.

So what is the difference between 2.6.3 and 2.6.6 in the bluetooth and locking behavior.

Ist it possible to upload the Version 2.6.4 and 2.6.5 to your site, so I can test this versions.

If you want me to list you my programms please say me how I can tell it to you, because I don't want to do it in this forum.

Thank U
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I have uploaded version 2.6.7, which lock the touchpanel now at power on and not at power off, when EnableInputAtSuspend = 1.

I could now not reproduce the scenario, when no PIN was entered before TouchLockPro locked the TouchPanel. Now the TouchPanel was locked :eek:

I do not know if that also solves your scenario, hope so, fingers crossed :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange that 2.6.3 is working and 2.6.6 not. The in between versions where test versions, 2.6.5 was not locking the TouchPanel too. However, they are available as attchment in this forum (test versions).

Ok, I have uploaded version 2.6.7, which locks the touchpanel now at power on and not at power off, when EnableInputAtSuspend = 1.

I could now not reproduce the scenario, when no PIN was entered before TouchLockPro locked the TouchPanel. Now the TouchPanel was locked :eek:

I do not know if that also solves your scenario, hope so, fingers crossed :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Locking TouchPanel solved in version 2.6.7?

I would like to know, if people who did have problems in locking the TouchPanel (e.g. Start button was not locked) if they still have problems with the new version 2.6.7:mad: Or do no longer have this problem :)
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
Thanks, I actually had found out that :-)

TLP + GScroll it's a fantastic couple. I have set up TLP to unlock by sweeping (and nothing else). As soon as I sweep and unlock it, gscroll takes over (I don't know why but it works) and I can double and triple tap to do actions (I have mapped the OK and Close apl. commands) and activate the Task Switching option built in in G-scroll.

The only problem I have at the moment is that sometime the normal panel buttons stop responding (not the capacitive tap or sweep which alway works fine). I can't pickup, close calls or go back to the home screen using the hardware keys but only using the touch screen. I have had this problem since I have upgraded to 2.6.3 as I need to use the new way of locking hardware keys.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmm, strange that the panel buttons do not respond. Maybe you can post a debug log file where the problem occured. Please note the exact time when it occurred and describe the keys you tried to press......
[Touch Diamond, MDA Compact IV Themes and Apps] ederhj:
Hallo,

now with 2.6.7 all works now.

One question: I don't know any more, if it was in your software: Ist it possible not to suspend the backlight during speaking with another person over the phone?

Tank U
[Touch Diamond, MDA Compact IV Themes and Apps] SiGeatd:
The problem with the lack of lock on the touch panel is still there (in version 2.6.7) Most crashes when loading if unlocking is disabled when an external power supply (UnlockOnACPower (UnlockOnACPower = 0). A few times when they happened after the reset pin when you write off the screen. (I have the HTC Touch Pro T7272; Final Operator: 31.190.9.694; ROM: 1.90.69.4 with PLK 09/24/08, Radio: 1.02.25.19, Protocol Version: 52.33.25.17H

I greet and congratulate the talent :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Great that the TouchScreen now also locks for you. I think it was a timing issue, with the fact that the power of the TouchScreen was already off, when locking at suspend. Anyway, locking now at poweron, has solved the problem :)

You can configure UnlockWhenConnected = 0 in the TAPI settings screen. But HTC itself also has a mechanism to let the display go off, dependent of the light sensor sensing light. So you must disable that, if you do not want that feature.

For the Touch Diamond, the tweak is described here:

8. Prevent screen switching off during phone call
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, because ederhj reported it is working now. Maybe it is an unrelated thing. Was the BattClock showing that it was locked and the TouchPanel was not :confused:

Can you be more specific of the crashes?

Can you enable debug logging (LogDebug=1) and post the log file in the root of your phone memory, \TouchLockPro.log.txt, as zipped attachment. Please note the exact times when problems occcurred, maybe I can find the reason :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] SiGeatd:
Hello again :)

Here are the logs are created when the problem occurs (after the boot screen and reset input pin when the phone turns off the screen. When you turn on the phone but a device to block the lock does not work, you can enter the PIN and device locked to the normal operation. Does not lock works to the next reset the device.

Greetings I hope that this helps. :D

There are 2 logs in the first there are any prior information as to the time I tried to log a feature:)
[Touch Diamond, MDA Compact IV Themes and Apps] geenyous:
same issue with the touchpanel

Hi,

Tried TouchLockPro way back, must say I am impressed by all the new features!

However, I have the same issue with the touchpanel, not locking on power on...

tried various settings, no effect.

log attached.

Thanks for looking into this!

Geen
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Great that you tried again TouchLockPro after some time.

You have configured EnableInputAtSuspend = 0, so that means that the TouchPanel will be locked already at suspend. For some people this gives problems. Maybe EnableInputAtSuspend = 1 will work for you, because then it will immediately lock at power on.

Hope it locks then :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, I could not see in the log why the TouchScreen does not lock. You can use the HTCLockAPI = 1, because that uses a different locking strategy. But some features are not available then, like unlocking via a key sequence. But because you have a Touch Pro you can unlock via capacitive touches and all the other sensors....
[Touch Diamond, MDA Compact IV Themes and Apps] bluefisher:
Hello! I can't lock now.

First, I want to say This software is so great! :)

Since I changed My os From 2.06 19981 to 2.09 21052, it couldn't lock when I touch the TouchPanel( I didn't set up the PIN, cause I don't like input them when every time the power on^-^).

I tried to install the cab from 2.4.1 to 2.6.7, it also occurs.

Here are the logs are created when the problem occurs ,and i didn't set up the PIN again( I don't know if it's the matter).

Greetings I hope that this helps.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I tested with your settings. I did some improvements, but I could still very rarely get reactions on touches on the TouchPanel.

I also solved (yeah, I never used this setting):

* Removed the flashing behaviour when using LockIndicator = 0

Can you test if version 1.5 WIP is better for you, with setting LockTouchPanelOnly = 1?

See post #6
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, I did not recreate the locked window anymore when the backlight was off. I removed this behaviour.

You can try version 1.5 WIP, available in post #6

Please let me know if this solves your problem:confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I tested the vibration, and it works with me.

But did you not make a typing error: Vidrate=1, it must be Vibrate=1

Yeah, other report too LockTouchPanelOnly = 1 is not working.

You can try version 1.5 WIP, as described in post #6

You can also post a debug log file, so I can look into it further.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Version 1.5 WIP

I did some improvements, as result of reports related to version 1.4.

Because I cannot test all combinations, I decided to put a test version in post #6.

If enough people try this one and find it better, I can officially release a new version.

Thanks for the testing effort ;)
[Touch Diamond, MDA Compact IV Themes and Apps] Kessler:
I'm the guy with the CMDA diamond. I'm not sure what changed but 1.4 works perfectly. Thanks! You really need a paypal donation button on your first post. Can you send me your paypal e-mail?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have ordered a PayPal account and I am awaiting that the procedure is finished (can take 5 to 7 days). So yes, I am going to provide a donation button in not too long time. Just be patient :)

For now, just enjoy TouchLockPro :D
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
this was a typo on the site here not in my reg settings!! my reg setting is:

Vibrate=1

but it doesnt work

ill try 1.5 now and see whats going on and post the debug file
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
Using v1.5WIP and nothing has changed:

ClockHeight=1 - working

ClockWidth=1 - working

ClockX=479 (1df) - working

LockTouchPanelOnly=1 - not working

UnlockOnLightSensorTime=1000 -Dont Know

Vidrate=1 - not working

LogDebug=1 - working

LogDebugDetailed=1 - dont know, see attached log, only ZuinigeRijder will be able to tell!

-----------------------

LockTouchPanelOnly - it works initially when the stylus is replaced, but it seems that the original problem with locktouchpanelonly is back!

UnlockOnLightSensorTime - i dont know as i am sat in a dimly lit room!!

Vidrate - there is no vibration to say the device is locked or unlocked.

-----------------------

SuspendOnBacklightOff = 1 - still not working but, when i press the powerbutton, i get a single vidration (should be double to say locked), but when i touch the screen it is unlocked.

one last suggestion, the sensorlock.log.txt should be stored on internal storage so save messing around when uploading!!

please find attached my log and i look forward to hearing from you

thanks
[Touch Diamond, MDA Compact IV Themes and Apps] kabronsete:
Yes, with this 1.5 WIP the problems are fixed.

Regards,
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the log file.

Ok, the mystery of the vibrate is solved.

Within StylusLock (yes, the version before TouchLockPro) I had 2 different vibration schemes:

1) without notification icon: vibrate/beep twice when locked, vibrate/beep once when unlocked

2) with notification icon: only vibrate/beep when locked AND the backlight is not ON

This behaviour has been taken over by TouchLockPro, if you have setting "LockIndicator = 0" it will behave according to 1), otherwise 2)

The idea behind it was that vibration also consumes battery and if there is a visual lock indicator, you do not need the vibration (only when the screen/backlight is off).

I also see in the loggng, you have set:

UnlockOnLightSensorTime: 500

The default is 5000. Your setting means the unlocking will be almost immediately when it sees any light. So if you take it out of your pocket, you must be really quick before accidently pressing touchpanel/keys.

Is it possible that it unlocks so quickly, by this setting (within 1 second)?

You can try to disable the light sensor by setting:

UnlockOnLightSensorTime = 0

Looking further into your logfile:

14:58:43 1164987122 ====== POWER ON =======

....

14:58:45 101509270 Light ON: 1

14:58:45 101509270 =======UNLOCK BY LIGHT SENSOR=======

14:58:45 101509270 ToggleUnlock()

14:58:45 101509270 SetLockMode(false)

14:58:45 101509270 Lock(false)

14:58:45 101509270 EnableInput()

14:58:45 101509270 SetDisabledPanelOnly(false)

So my assumption above is correct.

It unlocks so quickly, so indeed the TouchPanel can be touched thereafter.

My guess is that this is the problem you encounter.

About the log file, that I should not create it on the phone memory.

Because it is only for temporary debugging purposes, I choose this location, otherwise the SD card is constantly written. Also the location of the SD card is different for different languages ("Intern Geheugen" in Dutch). So I kept on the safe side.

Hope this helps you :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
I have downloaded and installed v1.5. I can confirm a noticeable improvement in locking the touch panel. If I very quickly repeatedly tap the screen I can still bypass the lock, but its much better than version 1.4. :)

The lock does NOT work at all on incoming calls. This still needs much improvement. :(

Keep up the great work!! :D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you also post a detailed debug log file with an incoming call. So I can have look into the log file?
[Touch Diamond, MDA Compact IV Themes and Apps] Dpakrawal:
is there a way to hide the lock indicator ??..

i love the program but would like the stock battery and time indicator, instead of the new one..
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There are several ways to almost get rid of the BattClock via the overrule settings in post #3.

LockIndicator = 0

ClockX = 0

ClockWidth = 480

ClockHeight = 2

With these settings there will be no lock indicator when unlocked and when the phone is locked a small band is drawn at the top of the screen to indicate it is locked. Of course other positions are also possible.

You can also make a 1x1 pixel, if you do not like a small strip and want it almost invisible. But you cannot see well the difference between locked and unlocked then. And of course you can change the colors with the settings mentioned in post #3.

Enjoy hacking TouchLockPro :D
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
OK, so if there is a lock indicator, in my case the single pixel, the only time i will get a vibration is in this instance:

device not locked with stylus, press power button, then i would get a single vibration to state the device is locked.

Now that yoo mention it that would seem like the most logical answer, the reason i kept it on was i seemed to start getting the problems when i disabled it.

I have applied the above setting and will see what happens

thanks for advice, and ill report back soon.

MG
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Indeed.

In your case, where you have a 1x1 pixel, it is logical (because it is not noticeable) to set LockIndicator = 0, then you have the old vibration as you where used to. And you can still unlock via the tripple touch.
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
so i dont need to have the pixel to unlock via triple tap?

as a side note, v1.5WIP seems to have fixed my issues, i can now disable the light sensor without adverse effects.

the vibrate is working as we discussed earlier

and all seems to be good again - touch wood! lol :D

ill disable the pixel and see what happens.

thanks for advice
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
One good reason, even a stupid one, for quoting the entire first post!!!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, the minimum must be one pixel, otherwise the capacitive touches will not work (I think). But you only need that 1 pixel, when it is locked.
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
in that case i need to have the lockindicator=1 shown. otherwise the touch will not work.

you confused me when you said this: