yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the log file.

I do not know how often the screen turned off and when.

I looked into the log file, and see the following occurences of !LOCKSUSPEND:

2009-11-12 22:56:48 -2049674038 SetCapacativeGesture(): Capacitive Gesture RightLeft

2009-11-12 22:56:48 -2049674038 Execute(): !LOCKSUSPEND

....

2009-11-13 12:41:47 -1546836574 SetCapacativeGesture(): Capacitive Gesture RightRight

2009-11-13 12:41:47 -1546836574 Execute(): !LOCKSUSPEND

....

2009-11-13 22:51:28 -2050709294 = GSENSOR ORIENTATION MATCH =: 2 numberOk: 3 numbersequence: 5 orientation: 5 FaceDown

2009-11-13 22:51:28 -2050709294 ==================COMMAND BY GSENSOR ORIENTATION==========================: 2

2009-11-13 22:51:28 -2050709294 Execute(): !LOCKSUSPEND

So I do not know how often it happended?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You use HTCLOCKAPI = 1, so then the power button will indeed be locked, when you lock the phone, without suspending.

You also set EnableInputAtSuspend = 0. With this setting the power button will not be unlocked, when going to suspend. So then there is a chance you cannot awake the phone with the power button. Better is just to set EnableInputAtSuspend = 1.
[Touch Diamond, MDA Compact IV Themes and Apps] xuyong:
maybe I find a bug

HTC Softbank X04HT

History of ROM Refresh:Never

OS:6.1

Language:JP

.NET:CF 3.5

TouchLockPro 2.8.2

I think I find a bug of the App with my diamond.

When my diamond is not used for a long time,the Capacitive NavSensor of the App will not work.

for example,every morning.In the time,I must reset the App or reset my diamond.

I am working.So I can not upload the log of the App now.

If MR.ZuinigeRijder need see the log, I will upload it when I back home.
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
Another log file. I disable many options and I have the same problem with the screen, screen turns off sometimes.
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
Suggestion

Would it be possible to add a new lock feature using the default LockScreen.

(Sorry I cant explain well - Please see attached png)

Unlock device by sliding the lock icon a number of times; either to the left or to the right or any combination of it.

Just my 2 cents:D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I assume you have TF3D on your phone and this is the problem.

Currently the TF3DWorkaround setting is not working with the global keyboard hook (HTCLockAPI = 0), because the workaround is blocked by the keyboard hook.

The following is already in the Settings described:

TF3DWorkaround (TF3DWorkaround = 1)

Enable/disable the TF3D workaround (tab right - tab left at power on and when on the TFD Home screen) for the HTC bug of capacitive sensor not always working when on home screen of TF3D. The workaround is only triggered, if the phone is still locked after 5 seconds and when the TF3D is the home foreground screen. One way or the other, TF3D Today home screen in the newer HTC ROM's (i.e. 2.03) is blocking the capacitive touches sometimes. But not always. Non TF3D users will not see any difference. If you use an older ROM (e.g. 1.93), then you can disable the workaround. If you do not like the workaround, you can disable it, but there will be a chance that the capacitive touches are not working. You need to unlock then via the other solutions (e.g. Stylus out is the quickest then). I am still searching for a better solution for the problem introduced by HTC.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have played around with this idea. The problem is that I need to have a foreground window then, and the other active programs cannot be seen (transparency is not really possible in Windows Mobile). I did not give up that idea yet, it is still on the wish list:

Foreground window when locked
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked into the log file and do not see anything strange, but of course I do not really know when the problem occurs. It would really help me when you write down the exact date/time when the problem occurs, so I can more closely look into the log lines when the problem occurred. Now I am looking for a needle in the haystack :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] xuyong:
Yes,I have TF3D on my phone.

And the ROM is 1.73.762.15 JPN.
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
Thanks for keeping this wish list alive:)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You do not have to reset your device to make the capacitive touches work.

When you unlock your phone via other means (light sensor, GSensor or stylus) and then do a tab left, followed by a tab right on the bottom of the screen in the TF3D home screen, the sensor should start reacting again. This is also what the TF3D Worakaround does. Apparently TF3D blocks the sensors and HTC screwed up something, because in earlier TF3D versions this problem was not in.

I have already solved the TF3D workaround locally, but I need to do a lot of testing, because I have implemented a lot of wishes.

This is a peek preview of the implemented things in the upcoming version:

Made TouchLockAction also suitable for different resolutions (240x320, 240x240, 320x320, 480x480, 480x640)

Automatically determine the BattClock settings dependent of the screen resolution, so it works also for other resolutions out of the box

Automatically determine the BattClock colors, from Taskbar color and text color, so the right color is chosen the first time or after default settings

Added !TOGGLELOCK command

Added !UNLOCKSCREEN command

Added !SOFTRESET command

Added !POWEROFF command

Added !HOME command

Added !UP command

Added !DOWN command

Added !LEFT command

Added !RIGHT command

Make TF3D Workaround work with *NEW* hardware key locking

Made Power off fallback, when PowerOffWarning.exe does not exist on phone, to be compatible with more phones

Added !HOME command: add option to automatically go to the home screen when locked (Security)

Prevent errors from running 2 instances of TouchLockAction simulatenously

16 NavSensor swipes, 8 when locked, 8 when unlocked, doubling the possibilities

8 GSensor commands, 4 when locked, 4 when unlocked, doubling the possibilities

Stylus launcher

And the following are also planned:

Possibility to Export/Import TouchLockPro settings in the About screen

Possibility that length of Stripe shows the battery percentage left

Show in BattClock when an unlock KEY sequence is detected (like capacitive touch and GSensor orientation)

Visual Stripe feedback when an unlock sequence is detected (key, capacitive touch, GSensor orientation)

Unfortunately, I am currently rather busy on my work and doing some related interesting stuff in my free time, so I do not have much spare time to spent on the new version of TouchLockPro. So be patient.
[Touch Diamond, MDA Compact IV Themes and Apps] wmjan:
Do not forget to add the following two functions: Backup Settings and Restore Settings！！！
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
That is the same as this one:

- Possibility to Export/Import TouchLockPro settings in the About screen

So it is on the list ;)
[Touch Diamond, MDA Compact IV Themes and Apps] worwig:
I think I'm missing something. This is pretty much the best lock program I have encountered yet, but I had a couple of problems.

First, I had a problem where when it was locked, it would still often open the contacts or calender. The softkeys basically stayed live. Once it opened contacts I then often got accidental touches that tried to delete a contact or something nasty like that. I tried to set "Double TouchPanel Lock" and I nearly needed to do a hard reset to get the PDA out of the lockup (luckily iLauncher has a safe boot mode). I've currently got "HTC Lock API" set and that works, except the button to put the unit in and out of standby tends to freeze up often now. I have 'EnableInputAtSuspend" set.

Second, often, the unit powers up and unlocks in about 2 seconds, in the dark. I have tried disabling every possible unlock method (leaving at least one enabled of course), and it still often unlocks on power up after a couple of seconds. Is there a timer or something that tells it to unlock if it hasn't been off long enough?

This is on a stock Verizon Touch Pro 2.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It is the same issue as http://xdaforums.com/showthread.php?p=3913271&highlight=paalkr#post3913271

See also the related youtube video:

http://www.youtube.com/watch?v=lB52J0pekIo

So indeed, now the only option is to use the HTCLockAPI = 1. And yes, when the phone is powered on and it is locked, the power button cannot be used to put the phone off again. You need to unlock first (or use a GSESNOR move to power off, e.g. couple !LOCKSUSPEND to a face down orientation move)

I still planning to have a foreground window, but I personally do not find this a good design, because the real info is obscured. Probably it will be an option in a future version.

This one is strange, this should not occur. Can you enable debug logging and note the exact time when such a problem occurs. Then post the logfile \TouchLockPro.log.txt. Maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] slickker:
When BackLight Off....

Hi, I re-visit and re-write my question.

First, I appreciate your app "TLP".

TLP lock the device when entried Suspend Mode, well.

(Other->AutoLockOnPowerOn)

But doesn't lock when entried BackLight Off Mode.

Please, I wanna lock the device when entried BackLight Off Mode..

Thank you.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, so you want to have an option to lock at backlight off.

Do you only want lock or you actually want locksuspend :confused:

Can you also explain more your use case, when/how you want to use it?
[Touch Diamond, MDA Compact IV Themes and Apps] worwig:
I'm guessing that you are saying that only a foreground window can block the softkey input. Bummer, I hate foreground windows that block the screen. I would stick with the HTCLockAPI myself.

As for the second issue, I believe I have tracked it down. I thought I had eliminated this earlier but apparently not. It appears to be the light level sensor. I had to bump it up to level 3. Even in total darkness, when it comes out of standby, the sensor thinks there is some light. The level 3 is only a slight annoyance, so I'm good there. (and around the same time my stylus sensor has gotten flacky and often indicates OUT when it is IN.)

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, it is strange that for the Touch Diamond 2 the notification icons are reacting. Apparently, HTC has something special for those, because normally they would be locked by the general screen lock. I personally also not like the idea of a foreground window, so for you you can indeed better stick to the HTCLockAPI.

Good to hear you did find the probable cause of the unlocking. If your stylus is not reacting correctly, you can try to gently remove the battery and blow away dust around the Stylus sensor. Maybe that helps. And of course you can disable it, but it is often a good way to unlock too.
[Touch Diamond, MDA Compact IV Themes and Apps] slickker:
Thank you for your response

Thank you for your response.

I wanna just lock in BackLight Off Mode, not locksuspend.

Because I use Touch Diamond by Music Player.

Device entry BackLight Off Mode when pushed suspend button maybe while music is played.

In this situation, Device doesn't be locked using AutoLockOnPowerOn option in other settings.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will add this option in a next version.
[Touch Diamond, MDA Compact IV Themes and Apps] volumax:
perfect

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] jaliscojorge:
Screen not locking after soft reset

Here is my problem, I have a US 3G Diamond, If I do a soft reset and let the phone fully boot up without touching it and activate the screen lock or locksuspend commands the battclock shows that it should be locked but it's not. If I touch the screen before the phone fully boots up especially before TLP activates then the screen lock just fine. I've had the same results with different versions of TLP and different roms all with the same problem.

I tried doing a thread search for that problem but couldn't find any post relating to it. Also with V.2.82 if I do a locksuspend the only way I can unlock the phone is to pull out the stylus because the power button and navsensor do nothing at all. On the prior version I had installed 2.7.6 if I hit the power button when suspended the phone would wake up then I'd unlock with navsensor. And I have it set to !LOCKSCREEN after call ends but it's a hit and miss when it does. Any body else having these issues?
[Touch Diamond, MDA Compact IV Themes and Apps] thangkls:
Could any one make a video to demonstrate how TLP work ?
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
Where are you going to get a new version of your program?

If I can help you testing a beta version you can tell me
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I tried the same scenario, but could not reproduce it. I use a normal Today screen and not TF3D. Maybe the scenario I tried is different :confused:

Anyway, it looks like the touch screen is not initialized and therefor TouchLockPro cannot lock it at that time. I do not know how I can solve this one.....

Hmmm, I assume you use the default locking and not HTCLockAPI = 1 :confused: Can you enable debug logging, reproduce the scenario and post the debug log file \TouchLockPro.log.txt. Maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I had started in making a video, but the result was not so good. So I have to restart this exercise. But that will take some time then.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am still developing new wishes. This time I am adding a lot of new features, instead of adding smaller ones. So it will take longer.......

Yesterday I added GSensor Shake to lock/unlock and also the SensorLock gesture to Lock/Unlock.
[Touch Diamond, MDA Compact IV Themes and Apps] jaliscojorge:
not locking

Sorry I forgot to mention I am using SPB SHell 3.5, I previously used 3.0 but had the same problem at boot up.

What do you mean by default locking and not HTCLockAPI=1

I will reinstall 2.8.2 and turn on debug logging.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
HTCLockAPI = 1 is another locking setting. I will see when you post your debug log file.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro Youtube video

I just uploaded a TouchLockPro Youtube video.

Youtube video

Youtube is still processing it, so the quality should improve within a half hour or so.

Have fun watching ;)
[Touch Diamond, MDA Compact IV Themes and Apps] Mandragore:
Well done. A nice video demonstrating great software!
[Touch Diamond, MDA Compact IV Themes and Apps] thangkls:
@ZuinigeRijder: Thanks for video !

Now I know how to use Gsensor to lock - thanks you so much !!!

1. How can I configure TouchLockPro to make it work as SensorLock ?

2. Your lock icon is not good. I disable battery/time icon but they still display on taskbar.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
SensorLock is just turning around the phone while lying horizontally on your hand. So it would be something like:

CmdOrientationSequence3 = 656 (FACE_UP, FACE_DOWN, FACE_UP)

And you can couple the command to toggle the lock (switch between lock/unlock):

CmdOrientation3 = "!TOGGLELOCK"

TouchLockPro does not use a lock icon. It just draws the battery/time over the rectangle location specified. So if you disable the BattClock display (e.g. use Stripe or Stealth in the BattClock Settings menu), the ugly Windows Mobile battery is shown :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] jaliscojorge:
Debug File

Here is the debug file. Hope you can find something.

I turned off HTCLockAPI because it didn't make a difference to my original problem and when activated sometimes "not always", if I swiped the navsensor for !LOCKSUSPEND the phone wouldn't stop vibrating unless I pressed the power button to wake it up. So it's not included in the log file. Thanks for your time!!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for providing the log file. For clarity, I repeat the reported problems.

Apparently nothing I can do about programmatically. I hope you can live with this issue, because after boot touching once the Touchscreen is not a real issue. As reported earlier, I could not reproduce it.

I looked at the !LOCKSCREEN after call ends, and it appears it is working from the log file:

2009-12-05 11:48:09 1144989882 SetCallStatus(CALL_ENDED): 0

...

2009-12-05 11:48:09 -1519544694 Execute(): !LOCKSCREEN

...

2009-12-05 11:48:29 73297922 SetCapacativeGesture(): Capacitive Gesture RightUp

2009-12-05 11:48:29 73297922 Execute(): !UNLOCK

So it looks it was working, at least at this occassion.

I also think the problem with the locked power button is not there when using HTCLOCKAPI=0. You did also set EnableInputAtSuspend: 0, this will cause the problem with the power button locked, in combination with HTCLOCKAPI=1. You use HTCLockAPIWhenBluetoothActive: 1, so it is better to set EnableInputAtSuspend=1
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Hello, can you update your tool, so that it works with the new HTC Leo / HD2 with WM 6.5-ROM?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have seen some code for accessing the GSENSOR code of the new HTC Leo. This is indeed different than the current GSENSOR code. Are you referring to that functionality which is not working? Or is there more not working :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
I haven´t tested it yet.

Here some users write something about your tool - it shouldn´t work properly.

If you can read german... http://www.ppc-welt.info/community/showthread.php?t=147828

Can you include a functionality for the proximitry sensor of the leo? Perhaps unlock the phone, when the sensor isn´t covered any more? So the phone will be locked while in the bag and unlock when you put it out. Light sensor isn´t such a good idea, because when you are in a dark room or at night it won´t unlock.

Is it able to use the touchscreen of the leo for unlock? The touchscreen should only work when you use your finger - fingernails or other things will not work on the capazitive display.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro does not have a foreground window, so you have to unlock via other means (unlock key sequence, stylus, light sensor, gsensor, etc.).

Ok, I have read the forum, I can read german well. I saw you did react already on that forum, to ask what is not working for TouchLockPro.

What I read is that the following is not working for HTC Leo:

- unlock via Volume Down/Up (maybe they can try to configure another unlock sequence?)

- GSENSOR unlock

If HTC Leo has other GSENSOR code (I saw some code on this forum), I can add that to TouchLockPro, but cannot test. I am still planning to add Omnia light sensor and Omnia GSENSOR to TouchLockPro. Also that I cannot test, because I do not earn enough money by donations with TouchLockPro :o

People having a HTC Leo can help by enabling debug logging (LogDebug=1) in the Other Settings form, reproduce the scenario (e.g. pressing Volume Down/Up) and post or mail me the log file in the root of the phone \TouchLockPro.log.txt. I can also make a test version for HTC Leo if the GSENSOR is really not working.

I can read German, so that is not a problem. I can even react on the German forum if that is appreciated.
[Touch Diamond, MDA Compact IV Themes and Apps] tigro11:
beautiful for HD
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
new feature request

Hi

using HTC touch pro 2 - could you implement unlock via sliding from left to right on the zoom bar ?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
+1

ZR, have you seen any code for accessing the Touch Pro 2 zoom bar? If I could ever find the time I would probably implement something myself, but my life is way too crazy hectic these days.
[Touch Diamond, MDA Compact IV Themes and Apps] toyjeep:
ZuinigeRijder

you're apps is great but i have an issue.

Could you please tell me how i resolve?

I want only that keys being locked when a call is coming.

How can i configure HD2 to do that!

Thanks for your great work
[Touch Diamond, MDA Compact IV Themes and Apps] tigro11:
is beautiful program for HD
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately I did not see any code for accessing the Zoom Bar. Also I have a Diamond and not a Diamond 2 or Pro 2, so I cannot test/try out anything. The latter you could help with, but I do not have any idea how to access the Zoom bar. So if someone knows the API or have seen code, I am glad to look into it. But for now, no luck :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In the TAPI screen, just select:

KeysOnly (LockWhenIncomingKeyOnly = 1)
[Touch Diamond, MDA Compact IV Themes and Apps] toyjeep:
And nothing more??

I think i dont make clear.

The phone is complete unlocked, and when a call cames he activates the lock, only in the keys.

is it possible?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I did indeed not understand you did not want to lock normally, but only want to lock the keys at incoming call.

In the other settings screen, uncheck:

AutoLockOnPowerOn (AutoLockOnPowerOn = 0)

In the TAPI settings screen set:

LockWhenIncoming (LockWhenIncoming = 1)

KeysOnly (LockWhenIncomingKeyOnly = 1)

Hope this helps ;)
[Touch Diamond, MDA Compact IV Themes and Apps] toyjeep:
It dont work :(

the only way i make it work is this: http://xdaforums.com/showthread.php?t=596037&page=2

But still using your app to suspend with gsensor :)
[Touch Diamond, MDA Compact IV Themes and Apps] darfri:
problem

it only blocks hardware keys. No screen protection gets active even if you relock, restart the process etc... and it never protected gps stuff. Is it an invisible always-on-top window that gets overdriven by agressively always on top apps? I am also using wktast that seems to manage push the close/ok button thru the shield in all situations.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I looked into your previous provided log file and see the settings were already as described. And the logging shows an incoming call:

2009-12-14 22:16:25 262587634 SetCallStatus(CALL_INCOMING): 0

2009-12-14 22:16:25 262587634 NotificationCallStatusIncoming()

2009-12-14 22:16:25 2067784850 NOTIFY_CALLSTATUS_INCOMING

....

....

2009-12-14 22:16:34 262587634 SetCallStatus(CALL_CONNECTED): 1

2009-12-14 22:16:34 262587634 NotificationCallStatusConnected()

I miss however logging that it tries to lock!

I looked into the source code and this condition will only trigger from power on to incoming call:

if (
pS->GetLockWhenIncoming() &&
(pS->GetCallStatus() == pS->CALL_INCOMING) &&
((GetTickCount() - powerOnTickCount) < 5000) || (powerOnTickCount == 0))
{
SetLocked();
}

The idea behind it, is that if your phone is not off, you do not need to lock, because it is not in your pocket then. So I expect it is working when there is an incoming call when the phone is off :confused:

If you always want to lock at incoming call, you can configure in the TAPI settings screen:

Incoming (CommandCallIncoming = !LOCKSCREEN)

Please let me know if this solves your issue :cool:

If not, please try to reproduce again and post a new log file.