yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I think I remember you had a Sprint TouchPro, so you have a keyboard slider. So actually, it should also work to unlock the phone by taking out the Stylus or opening the keyboard slider. Now you have disabled both, so it will not unlock by that means (that maybe also fine with you).

When you set UseSlider=0 and UseStylus=1, is it then also working OK?

When you set UseSlider=1 and UseStylus=0, is it then also working OK?

I expect indeed that the slider reading is not correct.

Can you check if the registry is showing the correct values for:

HKLM\System\CurrentControlSet\Keypad\IsSlideOut

It should be 0 when Slider IN and 1 when Slider out.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for helping in finding the problem.

Looking into the log file, it seems that my measures were not enough.

I have a new version you can try, which has additional measures.

Can you try version 2.0.1?

You do not need to deinstall 2.0, version 2.0.1 can just be installed over version 2.0.
[Touch Diamond, MDA Compact IV Themes and Apps] Lawliet:
Thanks for the reply. I've tried that already and by doing so, the battclock covers the "speaker icon" which allows for control of the phone's speaker volume.

Any other alternatives?

And I have a suggestion: Allow for a setting to unlock the phone when a call comes in. I recently installed the diamond curtain canvas and wouldn't mind if the phone was unlocked when a phone call comes in.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Although the speaker icon is below the BattClock, you can also press the icon to the left of the speaker icon, then there is another dialog to go to the speaker info (at least at my Touch Diamond).

Alternatively, you can position the BattClock over the logo of the Start. You can still open the Start menu, by touching the "Start" text.

And of course, you can configure a stripe or even stealth mode, if you do not like the BattClock.

This is already possible. More people are using the phone canvas, and therefore you can configure CommandCallIncoming = "TouchLockAction.exe" unlock

Note that you must use double quotes.

This you can configure also in TouchLockAction screen, named Incoming.
[Touch Diamond, MDA Compact IV Themes and Apps] bjevers:
I haven't fully tested this version yet, but one thing it is doing I see is the stripe disappears for a second every five seconds, then comes back on. Like it is flashing slowly every 5 seconds.

Hmm, now I can't reproduce it. I'll have to do some more testing today when I get a chance.

EDIT: Ok, turning the phone on with the power button causes the stripe to flash on and off every 5 seconds. It unlocked the phone for me on incoming call, but the stripe didn't disappear. I've attached a log file. Call came in at 11:46am.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
WOW! for me this 2.01 works perfectly ( until now):

no more delay ( or at least very minor) until it gets locked.

no bad interaction with Gscroll, i can unlock device using double tap in center button as i wanted to do without any weirdness or bad interaction with Gscroll. (btw one tap doesn´t seem to work but two taps is ok for me)

keyboard sliding is also nice to have it as unlocker.

i love this tool and it is becoming better and better in each new release.

Thanks a lot ZuinigeRijder!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see something strange in the log:

11:46:22 221476670 ClockWndProc(WM_PAINT)

11:46:22 221476670 No lock indicator, no WM_PAINT

I would not expect that the ClockWndProc(WM_PAINT) is shown in the log, with the Stripe settings. So that causes the problem, in combination with the setting that the BackgroundColor is equal to the ForegroundColor.

Also I noticed, while debugging, that when the settings via TouchLockAction.exe are changed from BattClock to Stripe, the Stripe appears also when unlocked. This is because the unlocked BattClock has focus and that is drawn then with the color which looks like it is locked.

Normally, when stripe is set, also the LockIndicator is set to 0. In that case the unlocked clock is created as non-visual BattClock. However, in other places I make it topmost and visible sometimes. And on 1 place I forget to check for GetLockIndicator().

So there were 2 problems, my theory is:

1) When the settings are changed via TouchLockAction, TouchLockPro was in the wrong state and restarting or soft-resetting would solve this problem

2) In one place, the unlocked BattClock could get visible, so it got WM_PAINT requests, drawing a white stripe, where it should not.

I tried to solve both issues in 2.0.2.

Note this is only for solving the Stripe issues, for the rest it is functional the same as version 2.0. Note that indeed there is a flashing behaviour when locked, because for one second I do not show a stripe.

Can you test again (pffff, this was finding a needle in a haystack, I hope I got it right now).
[Touch Diamond, MDA Compact IV Themes and Apps] bjevers:
Is there a reason you don't show a stripe for that one second? On some locked screens it has the side effect for redrawing the whole screen. This can be annoying. This happens if using BattClock too. To see an example of what I am talking about, go to Start, Programs and launch TouchLockAction from there. Then choose lock (hold your finger over the light sensor) and watch it redraw all the program icons every 5 seconds.

This did indeed fix the stripe display on incoming call for me. The only other weird thing that happened is I manually locked from TouchLockAction once and it would not unlock from the light sensor or the capacitive touch. I had to take the stylus out to unlock it. I was not able to reproduce this again yet, so I am not sure what caused it.

Thanks again for a great app!
[Touch Diamond, MDA Compact IV Themes and Apps] noreboy:
Couple of question using 2.0

First off, great program! I use to use S2u2 on my Mogul, but this is a good alternative that I'm trying out on my TP.

Issue/Concerns:

First thing is my phone doesn't auto lock after turning the phone on as per the 'AutoLockOnPowerOn' box being checked. I don't know if I'm the only person having this problem.

Is there a real purpose of the beep function? If so, it doesn't work on my phone. Though I have the function checked, my phone never beeps whether locking or unlocking the phone. My system ringer is on the loudest setting.

What does TAPI mean?

Why is the optioin for 'UseStylus', 'SuspendOnStylusIn', etc. listed twice on the second configuration screen?

Maybe I missed this somewhere, but I didn't see an explanation on how to change the combination to unlock the phone as per the site suggests the program can do.

Suggestion:

I would like to suggest the option of actually using up the strip area to display things like battclock, lock indicactor, count, etc., rather than just a lock indicator. On that same note, I would suggest increasing the size of the area to 640x20, making things on the strip visable. If this could be built in a way that the strip doesn't over lay the content on the screen (ie. signal indicator, battery indicator, valume, etc.) but instead push everything down, even better!
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
when i turn my phone off in standby mode by pressing the power button, the screen turns off.

then i press and hold the powerbutton, the display turns on an the phone asks me to completly shutdown.

is this a bug??

sometimes i turn the phone on it wants me to shutdown...
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
It seems like with this 2.0 version, my touchlockpro battery meter is showing -1 for a long longer than it was with 1.9.2. Sometimes could be like that for many 30 seconds. Also, even while it was on the charger, I saw -1. Maybe -1 = fully charged too? I'm not sure.

It's definitely showing it longer than the last version though.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The redrawing is due to the changes I invalidated the whole screen sometimes. But that was not the problem, when searching the needle. So I will make a version where I will not do that anymore.

I need to recreate the BattClock/Stripe once in so much time, to get focus for the capacitive touches. So I destroy and recreate the locked stripe. I have tried to create it immediately after destroying, but that does not work. And there is also a delay when i recreate it in the Destroy callback. I will see if I can make a version that then the other stripe is showed for 1 second (that is also done when showing the BattClock), so the flashing behaviour is not there.

I will post that version when I have finished that (takes me somewhat more time).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It will not lock, when the Stylus is OUT or the Slider is OUT or on AC/USB power. Also it will unlock really fast with the light sensor, if there is enough light. Is one of these the case?

But you say you have a Mogul?

I did not hear if TouchLockPro is working on that phone type. Does it have the sensors which are available on the Touch Diamond, Touch Pro and Touch HD?

And maybe the locking API for locking the hardware keys and touchpanel is not working. Locking only the TouchPanel is more or less standard Windows Mobile, so maybe only LockTouchPanelOnly=1 will work for you?

But how unlock then, if the sensors are not available on your phone?

You can enable a debug log file (logdebug=1 and logdebugdetailed=1) and post de file \TouchLockPro.log.txt as zipped attachment, so I can see in the logging what sensors are working.

This is an audible feeback, when you do not like the BattClock and use it in Stealth mode. Most people use the vibrate in that case. For the beeps, you need to enable the Windows Mobile alerts. I have a dutch Windows Mobile, but you can configure something like:

Start -> Settings -> Personal -> Sounds and alerts -> Check System events

Telephone Application Interface. This is used for detecting incoming calls, connected calls and ended calls. If you do not need that functionality, you can disable it, so you do not use the resources for watching this.

I think you misread, because these are the Stylus and Slider settings. So the second one are settings for the keyboard slider, but the options are alike.

That is on almost the last configuration page:

CapacitiveTouchesSequence = 444

Defines the capacitive touches sequence to unlock using area 1 (left area), 2 (middle center button), 3 (right area), 4 (any area) or 5 (area 1 or area 3). You can also define your own secret sequence for unlocking, e.g. 1321. The touches sequence can be up to 8 touches. If you want to use this as a Security pin, make sure you disable the other locking features (UseStylus, UnlockOnACPower, UnlockOnLightSensor) and of course configure a Windows Mobile password. Note that capacitive touches do not work on a Touch HD.

Pushing everything down cannot be done, because it is an overlay. The size of the Strip you can control, but there is not much space to put it, without overlaying important information.

You can also choose to show only the BattClock or Stripe when locked (LockIndicator=0), so only when locked it is overlaying information. Also the Fontsize can be controlled now, if you want bigger information.

Because the space is limited and I do not want to interfere with other programs, I keep the information to a minimum.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Older version of TouchLockPro had this problem sometimes. Which version are you using?

When you power off the phone, it takes some time before it goes completely to suspend (first only screen off after some seconds it goes to really suspend). If you press and hold down the power button, it will react the same as when the screen was on.

If you turn on the phone and also hold down the power button, it will see it as a power off request.

Unfortunately there is a difference in the power button, some phones it is easy, some phones difficult to operate (even for the same brand).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Between version 1.9.2 and 2.0 nothing is changed in this respect. -1 means I get from Windows Mobile battery percentage UNKNOWN back. If -1 is given back, the next time I need to redraw the battclock, I will ask again for the actual percentage. I will check my source code if there is a problem in there.
[Touch Diamond, MDA Compact IV Themes and Apps] noreboy:
I think my post got misunderstood. I own a Mogul, but I am using this program on my TP, not on the Mogul. Now that I've upgraded to the TP, I no longer use the Mogul.

Also, I have all of the extra options turned off (Stylus OUT, Slider OUT, AC/USB power, light sensor, etc.), so this is not the issue. Even still, my stylus is in, keyboard closed, and the phone is not on a AC/USB charger when I reset the phone, so it doesn't matter.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, can you post a debug log file, so I can have a look.

I did not get complaints from other TP users, so it should just work.

Maybe we can solve the mystery, if you post the debug log file.

Note that it takes 30 seconds before TouchLockPro really gets started.
[Touch Diamond, MDA Compact IV Themes and Apps] noreboy:
Don't know how to do that. Don't even know where to retrieve the log file from.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
As I already stated in my previous post:

You can enable a debug log file (logdebug=1 and logdebugdetailed=1) (almost last Settings screen in TouchLockAction) and post de file \TouchLockPro.log.txt (the top directory of your phone memory) as zipped attachment, so I can see in the logging what sensors are working.

Hope we can solve the mystery.
[Touch Diamond, MDA Compact IV Themes and Apps] Flintz:
I flashed my Diamond to a new rom yesterday (AZTOR X, a 2.03 based rom).

Now I cannot unlock the Diamond by tapping at the area underneath the display. It unlocks correctly by pulling out the stylus or via the light sensor.

I already tried to load the default settings to avoid a misconfiguration by me, no effect.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, can you post a debug log file (see previous post). Maybe that gives a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
with 2.0.2 release & 2.0.1 too, (i jumped from 1.92 to 2.01 first and later to2.0.2, i still notice this long delay before locking the device, a while ago you answered this to me. the problem is that sometimes PDA stays on for too many seconds (3-5) before it is locked from a power on and also in an incoming call.

do you think that posting what is running in my device could help you see what is making TLP wait its turn to lock the device an in such a manner improve this behaviour? this delay is a bit annoying but in the other hand everything else is running perfectly.

BTW i haven´t received anymore the TLP.log in use crash using the integrated unlocking mechanisms of TLP, i´ve only received it when trying to unlock device using a GSCROLL shortcut ( touchlockaction.exe unlock exit)associated to a double tap over the red hang button. But as since 2.0 the TLP unlocking mechanism of tapping on the center button, works perfectly without any bad interaction with Gscroll, since 2.0 i only use this method to unlock the device so no more crasher due TLP.log is in use.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I have made a version, which does the DisableInput not at the main thread but on the power on notification thread. To avoid problems, I wait 100 ms before disabling the input (if needed). At least it should now not take 3-5 seconds, because the main thread is maybe blocked by another nasty application.

I also improved over intermediate version 2.0.2, so the stripe is not flashing anymore (See post #864 of bjevers)

And as last improvement is to check every second for the battery status, when it is -1 (See post #863 from lexluthor)

Please try this version and let me know the results.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
I install it in a few seconds and tell you something tomorrow after testing it. thanks for this build.
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
Much better. Good thinking on how to solve that minor issue!
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
I spoke too soon. I just picked up my phone and hit the power button to awaken it from standby and it showed -1 for a good 30 seconds. Then it came back and showed 30%. Then I didn't touch anything, it went back to sleep. Two mins later, I hit power and it showed -1 for about 10 seconds.
[Touch Diamond, MDA Compact IV Themes and Apps] noreboy:
That didn't answer the question. I know how to turn on the debug and log option. My question is, where does the log file generate for me to even retrieve? I've had the option checked from before, now what? That's what I need to know.
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
i am using version 2.0 actually.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, then it is something specific for your phone (type) in combination with the battery and maybe even the driver in your ROM. It is known that for some battery drivers, it takes some time before the percentage can be read out.

As already mentioned, I have always immediately the battery percentage on my Touch Diamond. Probably you should compare it with other Touch Pro users and maybe even the same ROM version. I assume you have the standard battery, because I did read that others had problems with larger batteries.

Unfortunately I can not do more for you, I tried to improve, but apparently there was nothing to improve from my side. On the other hand, it is a minor issue. Maybe you should just live with it :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I thought I was clear enough in my post: post de file \TouchLockPro.log.txt (the top directory of your phone memory)

But to be more specific:

The log file is written in the top directory of your phone memory (so not on your Memory Card). Just enable the debug logging, try to reproduce the problem and then disable TouchLockPro (click the TouchLockPro program beside the TouchLockAction finger-print icon in the Programs menu):

So not the finger-print icon, but the one without icon.

With ActiveSync or Windows Mobile Center copy the file \TouchLockPro.log.txt to your computer, zip it (you can also use RAR for creating ZIP files) and post it as attachment.

Hope it is clear now :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] Flintz:
I've attached the requested log file for my problem with the capacity area below the screen.

Oh and I noticed that when G-Alarm wakes up my phone, unlocking by tapping works. O_o

Do you plan to implement a exception list, for example for G-Alarm? Would be handy if I don't have to unlock my phone first before I can disable the alarm ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I checked your log file.

I do not see messages in the logging, that the capacitive area are touched:

ClockLockedWndProc(WM_HTC_TOUCH)

So no touches at all are registered/notified :eek:

I also do not see an error message when loading the capacitive sensor:

21:12:31 1169867678 CapacitiveTouchSensorLoad()

21:12:31 1169867678 CapacitiveTouchSensorOpen()

21:12:31 1169867678 CapacitiveTouchSensorOpen() finished

So I think it has all to do with the ROM you are using (AZTOR X, a 2.03 based rom). Also many other programs had problems on that ROM, I saw in that thread. Was it working before you moved to this ROM?
[Touch Diamond, MDA Compact IV Themes and Apps] Flintz:
I usually use the stripe mode because I don't like the clock and battery option. Just now I switched back to clock to see if it recognises any taps and it worked :eek: Switched back to stripe and it still worked.

Now 3 mins. later it doesn't work again. Not in stripe and not in battclock mode. Doesn't recognise a single tap.

I am sorry that I can't give you better information.

Before rom upgrade I used Duttys 3.6b rom and Touchlock 1.9.2 and it worked flawlessly. Now I am using AZTOR X and Touchlock 2.0
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not think it has to do with the version of TouchLockPro. I expect TouchLockPro 1.9.2 is giving the same problems and it is more the ROM what causes the real problem. Of course you can try, by just installing TouchLockPro 1.9.2.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Hi ZuinigeRijder,

i´ve been testing 2.03 for 24 hours and i must say that i really don´t notice too much difference with the previous ones, from time to time (not always) i still able to click 2-3 times before device gets locked. Usually it works fine (quick lock) but sometimes it stays 3 seconds unlocked before being locked.
[Touch Diamond, MDA Compact IV Themes and Apps] mspingeld:
Using 2.0.3. Often when turning on the phone by a short press of the power button I get the message: "Warning-Power will be turned off, and you may lose data..." as if I did a long press to turn off the power. It's not a major problem-I just respond "no" and all is well but it is new with this version. Locking function work correctly.
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
Question:

Before TLP, my device did time-out and suspend based on the proper setting in WM settings. Also when programs required to keep the device non-suspended (eg. GPS software), they did manage to do it PLUS return to previous state (time-out suspend) after I quit them.

With TLP and setting:

SuspendTimeOutPowerOn

...this function was messed up. Device suspended after the above (TLP) time out even on programs that should NOT allow suspension.

I disabled the above setting (entered 0), does this mean that I am back to my WM settings? (ie. suspend on WM setting time-out, except if a program requests to not suspend the device?)

(hopefully)

(else please fix TLP to not ignore requests to keep the device waken up)
[Touch Diamond, MDA Compact IV Themes and Apps] yawpk:
ZuinigeRijder,

After using TLP 2.0 for a week, i find it is not so friendly to use anymore like TLP 1.9.2. The TLP 2.0 is not so responsive and as mentioned especially touching the area 2. The battclock will also disappear sometimes after several instances of locking and unlocking by different ways. When i run debug, it never happen for quite some time. When i switch off debug to save battery, occasionally, the problem comes back.

So, i switch back to TLP 1.9.2 for the time being because i had been getting more missed calls as i could not unlock in time (insensitivity in area 2).

I wish the coming version could make the area 2 more sensitive to touch and more consistent.

Thanx ZuinigeRijder, nevertheless TLP 1.9.2 still able to meet my needs although TLP 2 has more refinements that i would like to have for touchpro especially the slider keyboard.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
What a pity, because the changes I did made were meant for avoiding this. Can you enable debug logging (logdebug=1 and logdebugdetailed=1) and when it occurs again that it is not locked, write down the time when it occurs and post the debug log file \TouchLockPro.log.txt as zipped attachment.

Maybe this will give a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is probably due to the changes I did made for the problem of fourcc (see previous post). Previously I did this locking on the main thread to avoid such problems. Probably I need to revert those changed (and keeping the other improvements).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, you must set indeed SuspendTimeOutPowerOn = 0

AND check SuspendOnBackLightOff (see Settings screen below).

This last setting is the old behaviour, dependent on the WM setting time-out.