yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] erkme73:
Odd - I thought I already posted this but perhaps I never submitted it...

I have discovered that if the windows mobile STANDARD dialer is used (instead of the default HTC dialer skin), TLP gets tripped up. If I am on the dial pad display, and suspend, when it wakes up, the stripe will not go away when touching the screen or the capacitive buttons. The buttons themselves still work - as does the stylus/slider unlock triggers.

When using the standard windows mobile dialer, the volume control and bluetooth icon don't work either - so I think this is a general compatibility issue.

It explains why sometimes my TLP seems to lock up - but it's just waking up on the dialer screen. This also plays havoc with answering calls.

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

Now, separate issue. When I'm on the today screen when the phone wakes up, sometimes (usually after it's been sleeping for a while) the task manager icon will disappear for about 1-2 seconds, then reappear, then disappear for maybe another half second, and then stay on. During this cycling, TLP will not unlock with the capacitive touch. It only happens 1 of 5 times or so. It's almost like the task manager icon is refreshing in slow motion. It may be completely unrelated to TLP, but it could explain why sometimes hitting the capacitive buttons immediately after a wake-up does not unlock the phone.
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
I have .NET 3.5 as well. I reinstalled it just to be sure. Same result.

The TouchLockAction screen comes up in about 3-4 seconds for me. The settings screens all take about 15-17 seconds the first time I open them. It takes about half that time for the screens to open after the first time, but never in 3 seconds...

I reinstalled 2.2.4 and I got the same result. I'm thinking there is another issue with my device causing this. Not sure what it could be though. I wouldn't invest too much energy on this, since I seem to be the only one having it and it's not really a big deal.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
That is the GSENSOR seeing orientation changes. If I remember correctly, I saw in your debug log file, you still had the older value 8888.

http://www.zuinigerijder.com/Settings.html#4.4

UnlockOrientationSequence = 343

The correct GSENSOR orientation sequence changes are counted and if the configured sequence is reached within the specified time, the phone will unlock. The orientation sequence for unlocking can be configured, including combinations of orientation changes. The following orientation changes are supported by the TouchLockPro:

1. LANDSCAPE

2. REVERSE_LANDSCAPE

3. PORTRAIT

4. UPSIDE_DOWN

5. FACE_DOWN

6. FACE_UP

7. LANDSCAPE or REVERSE_LANDSCAPE

8. PORTRAIT or UPSIDE_DOWN

9. Any of the above

So you can do your own orientation gesture which suits you the best for unlocking. The default sequence is 343 (so the sequence Portrait-UpsideDown-Portrait will unlock). Note that you should not do the moves too fast, because the standard polling interval is about 300 ms for detecting the orientation changes. In the battclock, a negative number will be shown as the number of orientation changes, till then.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Great. Keep me tuned, when the behaviour changes, because others report it suddenly changes into misbehaviour. I hope that will not be the case in your situation :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Very strange behaviour, especially because a soft reset does not help. So it must be some registry corruption. And TLP is not writing to the registry, except the version number.

I can imagine that subclassing takes some time the first time locking a foreground window and maybe starting the gsensor. But is should not be noticeable, hmmm.

I did not change something to the capacitive mechanism.

Maybe the subclassing makes it a bit slower.

I only poll once per second for the light sensor, so I do not expect that is a problem.

I am now in in decision how to go on. Looking at the poll results till now, there are too many people experiencing problems with 2.2.7. ANd TLP is then also always in between the WndProc (which may slow down the device a little bit).

My current feeling is to leave the subclassing route because it is too delicate if something goes wrong. Because the capacitive sensor was not working with the newer ROMS always too, I am going to see if I can poll myself the capacitive sensor in RAW mode (of course only when locked/screen on). So I do not need to subclass myself. I also go to see if I can better poll the GSENSOR myself.

The side effect is that I cannot hunt the new locking of hardware buttons, because that also makes use of the subclassing.

I will await the poll results till the weekend, before I make the decision. But it looks like I need to leave the subclassing approach....because I do not want that people experience problems/missed calls with TLP, even if this does not affect everyone.
[Touch Diamond, MDA Compact IV Themes and Apps] gjeremie:
vibration on unlock problem

i have a problem with vibrate on unlock,

on version 2.2.1 each time my HTC HD is unlocked with light, phone vibrate correctly, but on version 2.2.7 sometimes phone not vibrate when unlock (especially when phone is switched on when it is in very bright room)

maybe it's related to modifications made for this feature :"No longer vibrate/beep when lock/unlock when there is an incoming call, to avoid stopping vibrate from call coming in" (version 2.2.4)

thanks
[Touch Diamond, MDA Compact IV Themes and Apps] AlexR_78:
Thanks for the great app. I have one question. Is there a possibility not to lock a device on switching on using Power button? Like when taking out a stylus. But that a device was locked on other events such reminders, messages, etc. I think that probability to accidentally press Power button isn't so big so I woud like to immediately begin to work with device without need to unlock it every time.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think this has to do with the subclassing. Probably I step away from that design. I am currently trying another approach.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately I can not detect the cause of the wake up due to power button press.
[Touch Diamond, MDA Compact IV Themes and Apps] ajm144k:
thanks for this app- i like all the different ways to unlock.
[Touch Diamond, MDA Compact IV Themes and Apps] erkme73:
I think my TP is just too under powered. I don't know if it's my Flexmail or other applications, but when it wakes up, the phone is so sluggish (even normally) that it takes forever for TLP to get priority. My Flexmail checks for mail immediately upon waking, and I suspect it takes priority over the unlock. Same with incoming phones.

If I'm on the normal windows dialer screen when a call comes in, the only way I can get it to unlock is by opening the slider or pulling out the stylus. if I open the slider as the phone is ringing, it all but locks up - taking a good 5-6 seconds to switch from landscape to portrait mode. All the while, i can't answer the phone.

Bottom line form me, great program, but underpowered phone. Is there a way to assign highest CPU priority to TLP so the first thing it does is unlock??
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am busy with a different approach for capacitive and gsensor unlocking, which does not need a wndproc anymore and also no subclassing anymore. So I can poll for capacitive touches and gsensor, independent of the Window Thread. This should improve the performance drastically from TLP perspective. However, some CPU cycles need to be spent on polling.

This should also solve the problems some people (according to the poll 40% :eek:) experience with TLP 2.2.7. I advise people which have problems to use an older version, e.g. TLP 2.1.
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
I never tried version 2.2.7 as 2.2.5 is fairly stable for me.

I was wondering do you know what impact on battery life this new method of unlocking will have (polling).

Also will it only be polling while the screen is on and locked? (i.e. not polling when device is on standby or when device is unlocked(

Finally, the user doesn’t use a specific unlocking method will the polling method for that sensor be disabled to reduce processor loading / increase battery life?
[Touch Diamond, MDA Compact IV Themes and Apps] mclaser:
Locking Function goes away

v2.2.3 Sprint ROM on vzw Diamond

Thanks for the cool app. Everything seems to work as expected for me except on two occasions I have experienced an inability to LOCK the device. I haven't determined what causes it; however, I think that removing the stylus and reinserting seems to reestablish normal operation. I hope this gives a clue.

When it happens, pressing the power button (AutoLockOnPowerOn=1) or pressing the lock icon from your app does NOT lock the device; neither the lock indicator appears, nor are the keys/icons actually locked. Softreset and stop/starting TLP does not reestablish normal operation. Frustrated, I removed the stylus and reinserted it and that seemed to fix it. I think that may be what I did the 1st time to fix it but I tried a bunch a things and can't be sure. I'll be sure to try it and report back if it happens again. One truly understands how valuable this app is once it stops working! :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe the stylus sensor did not react correctly, which may be a hardware problem. See also this post.

So TLP thinks the Stylus is out and it will not lock.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not think this will cost extra battery.

I also poll only when locked and the screen is on.

But I will try myself first for some time, to see how much CPU it uses and make sure battery is not drained.

You can disable those unlocking features, so it will not poll in that case (as always :D))
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Coupling "TouchLockAction.exe" unlock to a hardware button

This is BY FAR the best locking program I have ever tried. I love it!

I do have one question.

I would like to couple the command TouchLockAction.exe unlock to a hardware button on my Touch Pro.

Since you say this can be done, can you (or anyone else) explain how to do this?

I can go into the Button settings and choose TouchLockAction for the only button listed but I do not know how to add a parameter to send to the exe and without that parameter it just opens the options window.

TIA

SOLVED: HKLM\Software\Microsoft\Shell\Keys\40C6\Default = "\Windows\Start Menu\Programs\TouchLockAction.lnk" unlock
[Touch Diamond, MDA Compact IV Themes and Apps] erkme73:
ZR,

I downgraded from the 2.2.7 to the 2.2.1. From then on the display would no longer unlock with the capacitive buttons (even though the buttons light up when I touch them). The levels are set to 3000 for the timer, and 4 for the touch - just as before.

So I uninstalled, and figured I'd wait until the next fix. However, upon ending phone calls, I now get a dialog box that pops up "Cannot execute repllog.exe". Is that related to the TLP program?
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Hi ZR, i haven't post too much around here since a week ago because i'm very busy.

Since TLP 2.2.7 i also have a lot of problems, no more Gscroll related crashes but still a lot of different problems due bad behaviour of TLP. BTW as i am so busy i can not post the logs for it, maybe in a few days. Or maybe i will wait for a new TP release becasue i wouldn't know from where to start to log right now. Continue the good work ZR!
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
i´ve got another problem with tlp. unlock with capacitive touch is driving me crazy. sometime it workes, and sometimes not. so i have to pull the stylus to unlock.

then i run the taskmanager of batterystatus and kill all listed applications, put the stylus back in the device and then it is possible to unlock with capacitive touch until next power-off and on.

i tried version 2.2.7 and 2.1. same error on both versions.
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
Similar problem here. Most of the time, I can only bypass [unlock] TLP by pulling stylus even though capacitive touch is enabled. :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In version 2.2.1 one touch was not possible, so you have to configure 44.

It is indeed better to wait till the next version and for the time being using an older version, if you have problems with 2.2.7.

No, this is not related to TLP.

But more non-TLP users have this problem:

cannot execute repllog.exe
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I propose you use an older version which was working for you better. I am busy with a new version, which should solve all those annoying problems. I try to make that available as soon as possible.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In the new approach I am accessing the capacitive touches directly, so I am not longer dependent of the annoying quirks of using it on a Windows Thread. So I hope that will definitely solve this problem. So have a bit patience, till the new version is available. Till that time, use the version which works the best for you.
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
This is the 32 process limit.
[Touch Diamond, MDA Compact IV Themes and Apps] quicksite:
I don't know nuthin' bout birthing babies, but I did read a thread recently at XDA re someone requesting a way to kill "Active Sync" from constantly activating, even when no computer is attached. The answer was "remove the repllog.exe file, and that will kill it, but it also means when you INTEND to run active sync you will have to manually activate it on your device".

So, the above may be useful or useless info, i don't know.
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
If you are close to the 32 process limit, then the problem is much "deeper" than just killing repllog.exe.
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
suggestion

Hey, I was just wondering - ZR, will it be possible/easy for you to display somewhere the number of current running processes? Like you do with the date, time, battery status. I know this is against your philosophy for TLP (the "KISS" approach :) ), but I just thought to bring it forward, maybe you find the suggestion useful. I have the same issue with different .exe error popups and I have to admit I suspected TLP at some time (they started appearing roughly the same time I installed TLP).

BTW, I'm using TLP 2.2.5 and I am pretty happy with it at the moment (and so i never tried the newer versions).

Cheers!

Dan
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
I am really against such a feature. But who am I to say that. :)

Use a task manager for this man. Here is a nice (and free) one:

http://www.dotfred.net/TaskMgr.htm
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro version 2.3

Finally, TouchLockPro 2.3, which should solve the problems people experience with version 2.2.7.

I hope that people did not get disappointed and keep using TouchLockPro. Therefore, as a bonus, I added a possibility to suspend the phone, while it is locked, without using the power button. So you can e.g. quickly check the time and suspend the phone with a capacitive swipe or GSENSOR orientation sequence. Now you can configure:

* 4 GSENSOR orientation (external) commands

* 8 Capacitive swipes (external) commands

See changelog and documentation for more details.

Have fun :D
[Touch Diamond, MDA Compact IV Themes and Apps] peterbonge:
Sounds really interesting, but will the new swipe commands not interfere with GScroll? I didn't have the time to test it because it's too late now...

Something other: How do I prevent locking if I unplug the charger? Unlocking if connecting power is fine, but locking if unplugging the power is annoying.
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
I do use task manager(s), the idea is that you need to start or switch to a different application to do it whereas TLP is always visible in the upper bar. Same idea basically as for the date/time and battery info - you could obviously get that from other sources, but TLP is always there for you :) (and therefore it can let you know if you're approaching the 32 process limit.)

I guess an additional check box in the Settings Screen 3 (ClockForm) ( http://www.zuinigerijder.com/Settings.html#4.3 ) won't upset anyone. But as you already said - "who am I to say that?" :)

BTW ZR - congrats for 2.3!

Cheers!

Dan
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
I want to only use the middle button to unlock (3 touches). My settings are:

Capacitive toggle Time = 3000

Capacitive Touches Sequence = 222

I left all other settings untouch. But a single left touch unlock the device. What should be the correct settings please?

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
I tested 2.3 and it does indeed break the GScroll swipes, as well as the tap zones. I reverted back to 2.2.7, since it worked well with GScroll.

ZR, I like the idea of the new swipes, but is there any chance you could add a setting to disable that feature? I prefer the basic features of TLP, as long as it works with GScroll.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe another sensor has unlocked the phone, e.g. the light sensor?

Your settings is correct for unlocking via the middle button.

Can you post a debug log file (logdebug=1 and logdebugdetailed=1) reproduce the scenario, note the exact time and post the logfile \TouchLockPro.log.txt as zipped attachment?

Note that also Capacitive Swipes are possible now with version 2.3, so you can suspend the phone without pressing the power button, even when locked.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The capacitive touches are registered independent of each other. So as long as the capacitive touches are not conflicting (doing both different things), this is possible.

If you do not use the GScroll swipe possibilities, you can disable them in GScroll.

If you want to use the GScroll swipe possibilities, you have the following possibilities:

1) Disable the capacitive sensor use of TLP completely: CapacitiveToggleTime = 0. Note that you can configure command to GScroll to lock/unlock, e.g. "TouchLockAction.exe" unlock

2) Disable the capacitive swipe commands in TLP: empty each command for all the swipes in TouchLockAction. When there is an empty command configured, it will not be executed by TLP

When you are using GScroll, it seems to best go for option 1), because then TLP has 1 separate poll thread less.
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
Very very good job. 2.3 version its very good
[Touch Diamond, MDA Compact IV Themes and Apps] gjeremie:
-> same problem with 2.3, especially when phone is powered on after a long time.

and i don't know if it's me that don't understand the new cmd orientation sequence, but in version 2.3 when i set sequence to only : 5 (face down) with command : !UNLOCK , when i put the phone face down, i can see -1 in the battclock but the phone doesn't unlock.

another question : would be possible to add a setting to disable the polling of g-sensor when the phone is unlocked (same behavior as in 2.2.7) for users who want only unlock with g-sensor. (to reduce cpu usage)

thanks in advance.
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Hi ZR,

I haven’t tried version 2.3 yet but I have a question, in this version you say that it is possible to lock / suspend the device by swiping the capacitive sensor. Does this mean that TLP is always polling the capacitive sensor while the device is on and in normal use?

If so surely this will drain the battery and use up CPU clock cycles. Is there a way of disabling this so that the capacitive sensor only works when unlocking the device when coming out of standby?
[Touch Diamond, MDA Compact IV Themes and Apps] antjmon:
@ZuinigeRijder

This is an amazing program. I've been using it for awhile now and the development has been very impressive. I particularly like the capacitive feature now with 2.3. I dont have to rely on Butler anymore (which means I can ditch TF3d if I want to!!) In any event, how difficult would it be to incorporate

(a) a customizable date other than ddmm or mmdd (I prefer the MMM-dd format myself)

(b) an exception list so that when galarm wakes the device up it would bypass touchlockpro ensuring that the phone stays awake long enouguh to pass the alarm and not requiring unlocking the phone prior to snoozing or discontinuing the alarm.

I hate to be that guy that is dropping "suggestions" when its obvious that alot of work is being put into the program but I thought I would just throw it out there. Keep up the good work, I'll be dropping a small donation sometime very soon.
[Touch Diamond, MDA Compact IV Themes and Apps] cancar:
Battery drain

Congrats great piece of sw. however 2.3 is draining the battery too much. maybe the capacitive sensor polling is enabled also when the phone is in standby. Unfortunately even if I blank the actions the drain is the same (i suppose the polling is always enabled).

I suggest to check the capacitive sensor and the light sensow only when the phone is on waiting to be unlocked.
[Touch Diamond, MDA Compact IV Themes and Apps] schettj:
I have to agree, this version seems to be burning about 7%/hour of the battery even when the Touch Pro is on standby!

It's too bad - I love the new swipe features too. Please let us know if you think you can improve battery load while retaining some of these new features.
[Touch Diamond, MDA Compact IV Themes and Apps] dinfinity:
@ZuinigeRijder:

Again, thanks for your continued efforts on this fantastic locking app!

One little request though: could you add a config-option that makes it possible to disable the WinMo locking when the stylus is reinserted?

It's kind of annoying that whenever I take out my stylus, I mentally prepare myself for unlocking the phone when I reinsert it (and of course, actually having to perform the unlocking is something I'd like to avoid as well) :-)
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
Actually, I initially tried it with option 2, but GScroll wasn't working for some reason. I reinstalled 2.3 and it all seems to be working now. I'll run it this way and see if it crops up again.

BTW, I've been trying it with the new version (1.5) GScroll, which has some nice new features, like controlling the scrollwheel... :D
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
It's already there. On page 2 of the settings, uncheck "SuspendOnStylusIn"...
[Touch Diamond, MDA Compact IV Themes and Apps] jznn:
command line parameters

For some reason I am not able to use command line parameters.

Shortcut: \Windows\TouchLockAction.exe" LockScreen

Error: Unknown Action LockScreen”

Am I doing anything wrong?
[Touch Diamond, MDA Compact IV Themes and Apps] peterbonge:
It seems that I have to repeat my question. If TLP unlocks the device while connecting AC it also locks when unplugging from AC. How do I prevent locking while unplugging from AC? Have I overlooked something?

I'm still using v2.2.7 because of the reports that the new version is a battery eater. But I think with the new version nothing was changed with the AC locking/unlocking.
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
Unlock via middle button (3 swipes)

@ZR

FYI I lay my device flat on the table when doing the swipe. Hope this helps you with my issue.

Thanks.