yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Great to hear that you figured out a solution yourself :)

I also use OziExplorer now and then. You can just press the power button and it is locked (the same effect as TouchLockAction.exe LockSuspend). Also you can take out the stylus and put it back in within 1 second to lock it.

Or do I not understand your question correctly? Seems to me a difficult way to achieve the same? Or is pressing the power button not what you want and you want just by using your voice suspend the device (so you have your hands free)?

Do you want to share how you use OziExplorer? Maybe others (and I) can learn from it :confused:

Anyway, enjoy the software :D
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
i've been using 2.2.2 since you launched it.

and i must say that my main problem (autolockonpoweron=0) seems to have disappeared. Not completely, but maybe it works as expected 90% of the times.

capacitive area works fine (100%). ( i've uninstalled my purchased copy of gscroll to see what happens for some days, i will install it again tomorrow to see how TLP capacitive area responds)

i've not used too much gsensor because as the capacitive area works fine, i don't have to unlock it using gsensor.

the only problems i have is that when receiving a call, the battclock is usually (50%) hidden under the phone skin of iconsoft phonex (i'm testing this SW too see if i finally decide to get it). Would ClockLockActiveTime, if set with a low value, help me with this problem?

And the other problem, is that each time i end the call hanging the phone, my device wakes locked. (100%)

i've just installed 2.2.3 to see how it runs...

i keep you tunned.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Are all these problems still there with version 2.2.3?

My approach is indeed to have the possibility to disable the sensors you do not need, so you can use as less as resources possible. This is already possible and described in the settings screen. There is not a toggle setting for it, but using the time:

* UnlockOnLightSensorTime = 0

* UnlockOrientationTime = 0

* CapacitiveToggleTime = 0

I assume the the memory effect and battery effect will not be noticeable, especially because it will only be used when LOCKED and SCREEN ON, but of course disabling something you do not use, is always better :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I hope this problem is solved with 2.2.3.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I hope the crash is solved with version 2.2.3.

For the config screen, probably one of the values is out of range. You can reset the settings in the first settings screen (middle bottom button) and start again. I checked that the value 99999999 did not give a problem.

But putting in that value with the SIP is not so easy, so you can easily get a larger value :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The -1, -2, -3 are the GSENSOR orientation changes.

However, I noticed myself that the orientation changes are not returned as expected. It looks like the GSENSOR gives back wrong values and does not distinguish the orientation changes correctly. I will dig into this deeper.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the screenshots. I think this will be solved with 2.2.3.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Currently I do not detect if bluetooth is used. I can set it on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmm, I would not expect that it works with the Omnia, at least with respect to the sensors, because they are specific for the HTC?

Probably the settings screen is not usable, but you can use a registry editor to configure the settings. See here for more details, but be carefull, do it on your own risk!!

Can you post a debug log file (logdebug=1 and logdebugdetailed=1) and post the debug log file \TouchLockPro.log.txt as zipped attachment. Maybe that gives a clue which sensors are working :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I fixed the x problem first. I have also looked for how to see if the foreground window lost focus, but it was more important to have a fix for the larger problem ASAP.

Probably I am too fast (for your phone with your programs installed?) with creating the windows. Possibility could be to wait a bit longer, but others will complain it will not unlock fast enough, who do not have this problem.

Maybe I must make this then configurable :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, fine that the autolockonpoweron=0 is now working better. But still not perfect :cool:

That the BattClock is hidden, is because the phone skin is making sure it will be the topmost foreground window. So only once per 5 seconds the BattClock will be shown shortly :mad:

If I change my program to do the same, then they will compete continuously for the foreground. Then my program will interfere with running applications and that I do not want. So I do not have a good solution. has version 2.2.3 the same problem?
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
The hidden battlock doesn't annoy me too much, at least if it doesn't afect any unlocking mechanism. so don't worry about it.

i don't expect to receive calls this night but tomorrow i will test it for sure and keep you tunned. (My girlfriend is reclaiming me during now, i don't think she would understand if i call myself using her mobile) ;)
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
@ ZuinigeRijder: i am a little bit confused. since i installed v2.2.1 i had problems with unlocking via touch.

with the older versions i had no problems, everything worked fine.

but now i can install each version of tlp and the phone doesn´t unlock.

so what do i have do delete, to have it completly uninstalled?? so i can reinstall it on a clean device.
[Touch Diamond, MDA Compact IV Themes and Apps] Kater Karlo:
Unfortunately it's not :(. But I just realized that I can press the Home button on the Diamond and then the PIN pad suddenly appears. So it is now less of a problem as I do not have to reset the device :). It's just a little annoying.

Greetings K
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Just tried version 2.2.3, and here are the findings so far: -

Clock automatically updates when locked - Fixed!

X only appears while locked, disappears when unlocked - Fixed!

Capacitive sensor seams to work well, however I have only been testing a few hours - Fixed!

Things that might be broken:

Once unlocked the device feels slow and unresponsive for a few seconds.

Is it me or is this version using more memory?

Thanks for the hint I have changed the time settings on the ones that I not used.

Another question / recommendation / comment...

Would you at some point (less urgent) consider changing the GUI for the settings screens? I know it’s hardly ever used, but it’s very difficult to decipher what each of the names means and it’s not finger friendly. Moving over to the S2U2 configuration screen might be a better approach. And if say you disable the keyboard option, then anything related to it automatically gets disabled.
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Thanks for the fix, seems to work for the black screen and cross. :)

Regarding the time parameters it still crash everytime, IMHO could be great to simply have an on/off checkbox, something like :

It will also solve the crash.

I've also experienced something really annoying today, blutooth goes off after a short period time when connected to my car phone... :mad:

It's not good at all as it happens while I was driving......

ANother thing, could it be possible when we have a call to only turn off(and back on) the screen with the light sensor ?

I'm pretty sure that when we put the phone on or away of the ear that the light sensor can detect that change.

BR
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Very strange. Deinstalling removes normally whole TLP and reinstalling overwrites. So I do not think this is the problem. You can remove the registry key tree HKCU\Software\ZuinigeRijder. And check if Program files\TouchLockPro directory is empty. Also \Windows\TouchLockAction.exe should not exist anymore. But as said, I do not expect that is the problem.

You can check with proof of concept CapacitiveFingerLock if the capacitive touches still work.

If not, it is something wrong with your phone (hardware or software), and maybe a hardreset will help then. But of course, this is the last thing you would want.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
For solving the problem of capacitive touches of the newer ROM's I now subclass the foreground window, which will probably have the effect you describe. Make sure you switch to 2.2.3, because this solves another bug in 2.2.2.

I think I cannot do much about this inconvenience, but as always I will try if I can find a solution.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It uses a bit more memory, 38 Kb, but this is peanuts compared to the rest what is running :rolleyes: I cannot explain the slow device, maybe because of a new ROM?

I have already on the wish list improving the settings screen. I will look around what is handy :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you post a debug log file (logdebug=1 and logdebugdetailed=1) with the settings when it goes wrong and post the debug log file \TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue what is causing the trouble :confused:

Is this bluetooth problem away without TLP? Maybe my new foreground subclassing is causing the problem?

Turning off with the light sensor is in principle possible, back on is not possible, because the lightsensor does not work with the screen off. So therefore I have an option to do it when a call is connected, irrespective from the light sensor.
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
capacitiveFingerLock works well.

i´m not able to uninstall tlp. i removed it by uninstalling, but when i want to install another version, my phone wants me to uninstall the previous version. when i click ok, it says unable to uninstall tlp. install it anyway??

and then there is no entry to uninstall tlp from windows.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparently the registry is corrupted.

Hmmm, maybe others can give advice what to do in such cases?

I have a dutch phone, and TLP is installed in these places (assuming you did install it on the phone memory):

\Windows\Opstarten (Startup in English)

\Windows\Programmabestanden (Program Files in English)

\Windows\TouchLockAction.exe

\Windows\Startup\Programmabestanden\TouchLockPro.lnk

\Windows\Startup\Programmabestanden\TouchLockAction.lnk

Try to remove by hand and soft reset.

But I expect the registry is corrupt for the TouchLockPro installation, somehow. I do not know how to repair (only by hard reset) :mad:

Anyone?
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi !

I've experienced this issue with v2.2.2, after uninstall the issue went away.

The issue happens around 19:00 from memory, I've attached the log.

Tonight with v2.2.3 installed I haven't had the issue :) cross fingers

v2.2.3 seems to work really well

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] angusmears:
I'm having the same problem, when the windows mobile enter password screen displays it is black with the word password top left corner. unfortunately pressing home doesn't work for me. the only option seems to be to remove the stylus which causes the password entry screen to display. Not practical when driving though.

Have had to revert to using 2.2.1 for the time being.

Angus
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Not too worried about the increased memory and I can live with the sluggishness after unlocking as it is only for a couple of seconds.

I don’t think it’s the ROM because before installing TLP 2.2.3 it was fine, and when uninstalled it is fine too, like I said its just a minor annoyance rather then a problem.

I am curious about what your program does after unlocking. Does it exit, or poll something or what? Maybe it’s just a symptom that while unlocking your utilising a significant amount of processor cycles hence the device is unresponsive.

Anyway, I appreciate your hard work to make your application useable with the newer ROM’s. I also agree with your principle of keeping the app small and simple, there are a lot of people here that would like to see more functionality added that would no doubt bloat the software. This happens so much in the windows world, glad to see your resisting it.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I posted the source code of version 2.2.3.

I do not much:

* I enable input of course

* destroy the locked window

* destroy the capacitive window

* close gsensor (to not drain battery when unlocked)

* close capacitive sensor (to not drain battery when unlocked)

Probably the last 2 take time, but probably the destroy of the subclass popup window of the foreground window is the one which causes the real difference?

Is the same problem there with 2.2.1? Because that did not yet have the subclass of the foreground window.
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
Error in Init Form

Problem solved
[Touch Diamond, MDA Compact IV Themes and Apps] Kater Karlo:
Black Password Screen

I appreciate everything you have done already. Version 2.2.3 is the version I am using and also the version I was reporting about.

Greets K.
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Nope, 2.2.1 was fine, so it must be the closing of the subclass window or the method used.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have asked the author of Gscroll and Dredger97 if they use another method. Hope this gives a positive answer for another way to achieve the same :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, it must be related to the x problem. So let me know if it occurs again with version 2.2.3.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you share what the problem was?

Another value out of range?
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
When changing from settingscreen 3 to 4 I got a separate window with "Error in Init Form". When prssing ok screen 4 was shown. Then I changed StylusOutInToggleTime to 999999 and left the settings. When entering settings again the value was on default (1000) again. I deinstalled an installed 223 and 222 several times and then I got a crash every time I tried to get from screen 3 to 4. So I deinstalled everything and now I am back to 192. Here everything works fine.

Perhaps even if the application is completly deinstalled the variables which are altered are not reseted to default. Can you think about a solution for that (If you think that could solve the problem).

Anyway, great application and thanks for your time spending on that project.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Well... after testing TLP 2.2.3 some days and fine tweaking a couple of settings of TLA, i've got a close to 100% working as expected config for TLP:

My old known problems were:

1.- AutoLockOnPowerOn=0 but device always woke up my device in a locked state.

2.- locks in a middle (when talking) and after (when hanging) of a call.

3.- Capacitive area didn't recognize my taps most of the times.

4.- Gsensor sometimes worked sometimes not.

What have i done?

1.- I installed the last version of GScroll and using memmaid, I changed the startup applications order to first launch TLP, and at the end of all the startup processes, launch GScroll. ( before i used first version)

3.- Set Gscroll to disable Tilt (BTW i've always had this disabled since the beginning)

2.- In TLA:

Set CommandCallConnected = "TouchLockAction.exe" Unlock

Set CommandCallEnded = "TouchLockAction.exe" Unlock

Set UnlockWhenConected= 1

Set ClockLockActiveTime= 100 ( something low to reget focus quickly)

Since then TLP is really close to work perfectly, i only have some small issues:

the most annoying one:

1.- when doing a call before any answer, and also after hanging too (before any answer), if screen turns off and I turn it on again, device is locked.

It only happens if the call is outgoing and doesn't get an answer.

If the call gets an answer, then device is not locked in any case: in the middle of the call and at the end, either.

Maybe the way to solve this issue would be to make think TLP that when doing an outgoing call, it shouldn't lock device although device is waiting for an answer (connected state). Because if you don't get an answer you won't never be "connected". I know that with AutoLockOnPowerOn=0 , device should not lock, but it does ( this is the only case that it locks device when turning it on , the other old known cases seems solved, crossed fingers)

and the small problems i sometimes still have:

2.- sometimes i must tap in capacitive area (2) several times until TLP get it and unlocks device. ( Gscroll could be the case, btw since it is launched at the end of the startup processes it seems to occur less times, placebo effect? )

3.- Sometimes Gsensor unlocking mechanism is difficult to make it unlock device but maybe my combination (5-9 FACE_DOWN - Any of the above) is not so easy to achieve it with precition. Maybe i could try 999 or 69 or somehting like that, i will try it later...

and attached the logs of the problem number one and a readme description with the times the problems occurs, really annoying!

and also some snapshots of my TLA config windows if they can help someone to solve some of the issues i used to have.

and my ZuinigeRijder Registry keys:

edit: and thanks a lot again ZR for your great tool, work, time and support, TLP should be included in any rom , XDA's ones, and Officials too!
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
OK I found a repeatable bug, if you want me to create a log file I will do if not, it’s simple enough to try on your own phone.

Firstly the settings used: -

Vibrate:	Unchecked

Lock:	0

Unlock:	1

LockWhenIncoming:	Unchecked

Incoming:	“TouchLockAction.exe” Unlock

Stealth:	Checked

The phone is set to Vibrate and Ring on an incoming call through normal Windows Settings Page.

The problem:

The phone is on standby when someone calls, the phone is automatically unlocked, and I feel the usual one short vibration. After this I feel no more vibrations from the ringing. This did not happen in 2.2.1

If I set the Vibrate Unlock to 0 the problem goes away. If the phone is already unlocked and on when a call is recieved again i dont have a problem. It’s almost as if the interruption from TLP vibrate when unlocked stops the normal windows vibrate when ringing.

Possible solution might be to somehow disable vibrate when Incoming: “TouchLockAction.exe” Unlock is used. Or maybe its apart of the same subclassing issue...

Imran
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
I had this same problem in earlier versions. Did not test in 2.2.1, but happened before. I love the unlock + vibrate option, but it kills the ringer vibrate that I need.

Would love this to be fixed in a future release! :D
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
Yes (# 1.), the clock is still frozen to the last time that it went to sleep until it is unlocked. The moment I unlock it, the time updates.

Furthermore, I believe that since I also use SecondToday with PhoneAlarm running on my SecondToday today screen, TLP is also freezing my repeating alarms.

When I use TLP to lock my device, after several minutes by repeating alarms stop. The moment I wake my device and unlock it, the alarm sounds. When I disable TLP, I don't have problems with my alarms. FYI, this does not happen with first time alarms such as a new SMS or voicemail, only the repeating alarms for these items if I don't clear the alarm.

Let me know if a log file will help. :(

Thanks for the hard work! :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The author of GScroll gave me this answer:

Ahh so we have a different definition of subclassing. What you are doing is parenting the foreground window to yours. Subclassing is essentially overriding the WNDPROC of the window. So basically what you do is get the foreground window HWND, then calls SetWindowLong(GWL_WNDPROC, SubClassedWndProc).

SubClassedWndProc is a function you define which is a replacement wndproc for the window. Just pass any non touch messages on to the base wndproc and everything will be fine.

You do not need to create your own windows.

You can try the version in the attachment. Does this solve the problem of the alarms and frozen clock?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, this problem I did not know about till now.

I do the vibration on a background thread (like sensorlock).

See if I can find another solution :o
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for sharing the info, interesting for others too, if they like the same setup.

1. I will need to have a closer look to the log files. You have now really pinpointed when it is going wrong (thanks for that), so I can probably reproduce myself now.

2. Set ClockLockActiveTime= 100 ( something low to reget focus quickly)

This will open/close the capacitive sensor each second, so there is a great chance there will be missed touches. Better is to give it a larger value, once per 3 seconds (3000)?

3. The recreate of 2. above also closes/opens the gsensor, so then you will miss also sensor changes when having such a small clocklockactivetime. I am also not so pleased with the orientation changes I get from the gsensor, they are not correct always :mad: So I have to look into that, or I need to poll myself.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I tried to reproduce myself, but I could not. So I expect another value was out of range. The first settings screen has a reset to default button:

the middle button at the bottom.

Can you post a debug log file, when it is going wrong again?
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
The Autolockonpoweron=0 problem comes again. (not only when doing an outgoing call that doesn't get an answer) it also hapens when manually turning screen on.

it is crazy, there isn't any pattern that make it come back. Yesterday i thought i completely eliminated it but suddenly it appears again.

i will try 2.2.4 to see if it runs better

(i will increase the clocklockactivetime too, thanks for the tip)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think I found the bug with the autolockonpoweron=0. I did forget to reset the callStatus to CALL_NONE in the use case 1.

See a NEW version 2.2.4 as attachment (so this has the same version number!). Hope this solves really your annoying issue 1.