yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Ok these are VERY old post but perhaps still applies:

http://www.pocketpcdn.com/sections/input.html

(The one titled "QA: How can I handle hardware keys in my application?" might be the most useful & includes sample code. The MSDN link is dead..)

As I said before the idea was instead of using the lock functions (that seem to lock all keys) to instead capture & map the keys so they do nothing when pressed when TLP is 'locked' then release or map back when 'unlocked'.. If the trick works it should allow for locking/unlocking of individual keys. :D

Very interesting info & key table but not sure how the mappings correspond to the Diamond yet (but will soon enough as I'm trying them now hehe)

http://comptec.kearney.net/jornada/reg.html

I'm off to dig some more..
[Touch Diamond, MDA Compact IV Themes and Apps] thabolous:
is it possible to immediately lock the phone when not answering a call (e.g. i don't notice someone is calling)?

i can't get my phone to do this :(
[Touch Diamond, MDA Compact IV Themes and Apps] Kater Karlo:
Stylus and Capacitive do not work

Hi,

first of all, many thanks for this great tool :)

On my phone (Diamond with the newest official german rom 2.03) two of the sensors do not work in TochLockPro. One is (at least most of the time) the capacitive sensor to unlock the phone. This one seems to be known.

The other sensor is the stylus. I can put it out, or put it back in during the specified time. Does neither lock, nor unlock the phone. :confused:

Any suggestions?

Thanks K
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, TouchLockPro is doing this by default, by AutoLockOnPowerOn.

Any event which makes the device screen on (SMS, email, incoming call, pressing the power button, external event) will lock the phone.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is indeed the case when you use TFL3D. I am testing a solution, so whenever this is successful, I will post this fix. The solution is to subclass the foregroundwindow, instead of a subwindow of the taskbar.

I know more people have a problem with the Stylus sensor, which is a HARDWARE problem. The stylus sensor is too far away (got loose) from the stylus. Some people even put a piece of paper between the sensor and the stylus, to avoid waking up the phone. If you remove the back and the battery, maybe you can see if the stylus sensor on the right place.

You can check if the Stylus sensor is working by checking the registry key:

HKCU\\ControlPanel\\Keybd\\StylusOutStatus

1 = out, 0 = in

if this is the case, the stylus sensor is working. Then you can post a debug log file (logdebug=, logdebugdetailed=1) and post the debug log file \\TouchLockPro.log.txt as zipped attachment.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Hi ZR, i know that i still have to send you my logs, i haven't done it until now because i'm super busy.

TLP is not running very well for me. basically the unlockonpoweron=0 but device screen wakes locked when turning it on, also the capacitive area usually doesn't detect my touches and the gsensor also doesn't detect any of my movements (8888) since some days ago, it used to work fine (perfect) the first two days but not since some days ago.

I will try to find time to make logs for you. Meanwhile i will wait for an upcoming release with the improvements related to what the Gscroll developer told you.

BTW, thank you very much for the continuos support you offer us in this threed, i hope someday your tool will work perfect.
[Touch Diamond, MDA Compact IV Themes and Apps] Kater Karlo:
Stylus and Capacitive do not work

Thanks for the reply ZR. Currently I think that it might be a problem with the sensor or the new 2.03 ROM. I can trigger the sensor manualy and do hear the clicking sound. But nothing happens neither in the registry nor in gyrator which I installed now for testing :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] mxl180:
Is it possible to unlock hard key combo?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
yes, use LockTouchPanelOnly=1
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
i've reflashed my device, and restored Sprite backup image, and tlp seems to work fine for at least 3 hours, i will update this info later when having more info about it. Conclusion, it seems that TLP bad behaviours is not TLP fault, maybe it is related to other apps installed.

edit:

gsensor works sometimes (59)

continue the locking on turning it on when autolockonpoweron=0

capacitive area seems to work well (2)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Version 2.2.2 fix for TF3D capacitive touches

Just uploaded TouchLockPro version 2.2.2:

Solved the problem with the latest roms (Dutty v4, AZTOR X, 2.0.3) have issues with capacitive touches if TF3D is enabled on the Today screen.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
What am I doing wrong... Sometime it stops working, I start the application go through all the menu, force it to lock, nothing. Sometime I change an option and.... it works.... But this does not fix it all the time !!

Now I just upgraded to 2.2.2, and it stopped working again :(

Any help? Please ?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Locking is done by just pressing the power button (or via the TouchLockAction LockScreen or LockSuspend button). With the default "AutoLockOnPowerOn=1" it will automatically lock when the screen goes on. The sensors are only used for unlocking.

For me it is not so clear what exactly the problem is?

Can you make a debug log file (logdebug=1 and logdebugdetailed=1) and reproduce the problems you have and post the debug log file \TouchLockPro.log.txt as zipped attachment? In combination with a clear description what is not working, I can maybe solve the mystery?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
From Dredger97 I got an answer, which a solution I did not expect for locking the hardware keys, which I want to share with you:

Hello,

as my source remains on professional libraries i developped for my job, i can't give you a full version of thoses sources.

But the tip for catching those key is very easy to understand and your program is "nearly" already using it:

the API I use is the same as the CapacitiveTouchSensor.

The tips is to call "pfnHTCNavSetMode" with Mode &=0x20.

That way, the hWnd you defined catches 0x04D0 messages exactly as you already catches 0x04D1 messages for capacitive touch.

wParam is 1 for key pressed, 2 for key released

lParam is one of the following:

#define TS_KEY_HOME 0x005B

#define TS_KEY_BACK 0x005C

#define TS_KEY_PHONEUP 0x0072

#define TS_KEY_PHONEDOWN 0x0073

I first used DredSensor background window as hWnd parameter for pfnHTCNavSetMode.

I works, but it seems it quickly loose the key catching on the new AZTOR's rom and similar.

It seems it works really better if you use foreground window and catch its WindowProc call by setting your own WindowProc with SetWindowLong api.

Enjoy.

So from this description it looks like there is another way of using the NavSensor, which I did not know about. So I am going to experiment with this info, so maybe this gives more flexibility then locking all hardware keys (or unlocking using a combination of hardware keys presses).

For you fourcc, it is better to use AutoLockOnPowerOn=1, because probably all the problems are related to the setting AutoLockOnPowerOn=0 (probably a bug in TLP). Hopefully I can make the locking of the hardware keys different, so it is possible to just power off the device with the power button when locked.
[Touch Diamond, MDA Compact IV Themes and Apps] cellgeek:
Network Connection fails

I searched though this thread and haven't found any mention of this issue, so I'll post it.

I noticed after installing 2.2.2 on my Fuze (AT&T ROM), that after several hours my data connection starts failing. It requires a reboot to fix it. I undid all the network related tweaks, with the exception of HSPDA and it still fails after a couple of hours. So on a hunch, I removed TouchLockPro :( and my data connection immediately started working again.

I'm not going to assume the problem is TouchLockPro, but has anyone had this issue occur. I'm running the following tweaked software:

J.S. AdvancedConfig 3.3

Montecristoff Diamond Tweak

.Net CF 3.5

HTC HTC Application Service

MobileMatt FuzeBerry 6.0.0

Sushi's Diamond TF3D Config

XDA JCEspi2005 GPS Lag Fix, Rapheal

and some other more traditional programs. . . .

Thanks in advance.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Sorry if I was not clear :)

I understand how your application works, normally as soon as I press the power button it turns the screen off. But, normally, when I turn the device on it locks then I'm able to unlock it using the light sensor, or the anything else. But once in a while, like now :) When I turn it off and on, it's not locked.

When this happens, I try to disable the TLP, re-enable it, does not work. Most of the time, I think, it comes back if I change a setting, then go through all the menu (using the right arrow), then it might start working again.

As requested, please find the logs.

Thanks for your help.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, it looks it is something with the stylus sensor:

16:30:06 -825895262 SetLocked cancelled, stylus out

16:30:15 -825895262 SetLocked cancelled, stylus out

Probably it is a HARDWARE problem with the Stylus sensor, like I did describe in post 1201, because I assume you did not loose your Stylus or had it out :confused:

See also that we are not in the same time zone ;)
[Touch Diamond, MDA Compact IV Themes and Apps] mxl180:
If I put the phone on standy (pressing power buttong). I can turn it back on by pressing the power button. Then unlock.

BUT

When phone goes on standby (due to idle X seconds). I cannot turn it back on unless I plug in a charger and then press power button.

I'm guessing it's a setting and not a bug... but I can't figure what to change?

EDIT: Fount it > EnableInputAtSuspend
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
No, my stylus is in :)

So I removed back of the phone and took my pressured air can and cleaned the phone, I also removed the stylus and inserted the pipe in and cleaned it.

And guess what? It's now working ;)
[Touch Diamond, MDA Compact IV Themes and Apps] Radimus:
I often turn on the phone just to check the time.

When I turn it on, it is locked, but then I have to unlock it so I can turn it off again.

can you allow the power button to work even while locked?
[Touch Diamond, MDA Compact IV Themes and Apps] Radimus:
btw, is it me or is apptodate erroring out trying to update the app?

Is there a possibility of having it autostart an app at poweron? like going to home screen?
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I'm experiencing the same problem.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
that's very good news ZR, hope you find the solution to partially locking the HW buttons. Meanwhile, i will try AutoLockOnPowerOn=1, to see what happens.

2.2.2 is yet installed and being tested.
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
in version 2.2.1 and 2.2.2 i cant unlock the device by touching the touchareas until i move the gsensor.
[Touch Diamond, MDA Compact IV Themes and Apps] mackam:
ZuinigeRijder

Can You add possibility to change icons on this screen:

e.g. line icons.png file to replace in program directory.

ps. big thx. for this application.
[Touch Diamond, MDA Compact IV Themes and Apps] momyc:
HI ZR ,

With the new version 2.2.2 , I have a small bug.

The top right TF3D task manager icon (like 3 horizontally lines) is overwrote with a “X” (close program), I believe from TLP , but when I tap on that the

TF3D it shuts down.

I reinstall back the old version 2.2.1 and that X is not anymore there. It happened only with the new TLP 2.2.2 .

Thanks for your nice work.
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
i have much problems with 2.2.2. it closes opera mini when the device gets locked and i cant unlock it until moving the device. so i am back to 2.1 now!!
[Touch Diamond, MDA Compact IV Themes and Apps] jodeltje:
Hi zuinige rijder,

can u make a "unlock on powerbutton" function?

I just want to block stuff when my phone wakes up in my pocket...

thanks in advance :D
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi,

Great app :)

Just a question, how can I always lock the device when I insert the stylus ?

I would like a on/off lock without the time constraint in fact.

I've actually set the max value of 21568 for StylusOutInToggleTime but it's not long enough... :(

Thanks

BR
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for pointing out the problem. I can see in the errorlog of the webserver it is searched for the correct file, but guess:

the casing is wrong, in the apptodate xml file .cab is specified, on the website it is .CAB. I uploaded a new version, which should correct this problem.

I will put it on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It was already on the wish list, but I did not yet updated it on the website.

But yes, I put it on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will have a look, if I can solve this problem. Probably it has to do with the fact that I subclass now the foreground window. I need to check if it also works if it is a child window without pop-up........because I expect that is the problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, seems to me unrelated. I will try to reproduce. I assume it is with TF3D:confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am trying to find a solution that I can lock specific hardware keys. If that is possible, I can probably detect also the power button, but I am not sure about that. But also in your pocket, you can accidently press the power button.

In my opinion the most important problem with the current "lock all keys" approach, is that also the power button is locked when screen is on and locked. You want to be able to power off the device when locked, by pressing the power button. Then you can check e.g. time and power off immediately. The unlocking possibilities are numerous now, maybe I can add a combo hardware key unlock as extra.

I hope my new lead, see post 1217 makes this all possible.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.2.2 has removed these limits for Time, so now you can configure: StylusOutInToggleTime = 99999999

Should be enough :p
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
Im experiencing the exact same thing but i need to keep the latest version as im using duttys rom
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Probably it is the same problem as the X of the task manager.

In the logging, I miss the LOGDEBUG=1 entries, I only see LOGDERBUGDETAILED=1. So difficult to analyze :o

But as said, I think it is the same problem as the X problem.

I will try to resolve that one ASAP.
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
and why can i unlock device only if i move it??

i´ll post another log...
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I don't know if it's a bug or it has already been reprted, but I know it works when TLP is disable.

I setup TLP to unlock on incoming call, but even after the device is unlock, I can only answer the call by pressing on the green answer button on the touch screen, the hardware button does not work.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you post a debug log file (logdebug=1 and logdebugdetailed=1), reproduce the problem, note the exact time and post the file \TouchLockPro.log.txt as zipped attachment. Sounds like a bug in TLP :mad:

Maybe the log file gives clarity.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, now you only enabled logdebug=1, so I miss the detailed info :cool:

Anyway, what I see now:

20:30:29 -373768618 CapacitiveWndProc(WM_ACTIVATE) = WA_INACTIVE

20:30:29 -373768618 ClockLockedWndProc(WM_ACTIVATE) = WA_ACTIVE

20:30:34 -373768618 ClockLockedWndProc(WM_ACTIVATE) = WA_INACTIVE

20:30:34 -373768618 CapacitiveWndProc(WM_ACTIVATE) = WA_ACTIVE

20:30:34 -373768618 ClockLockedWndProc(WM_DESTROY)

Looks like the capacitive window only becomes active after 5 seconds (when the locked clock is recreated). So it looks it has no focus, till the recreate.....

I will see if I can improve this, to detect lost focus and recreate earlier.
[Touch Diamond, MDA Compact IV Themes and Apps] mxl180:
ClockLockActiveTime

"Defines the time in milliseconds how long the locked BattClock will be shown, before it will be recreated. "

what is meant by "BEFORE IT WILL BE RECREATED" ?
[Touch Diamond, MDA Compact IV Themes and Apps] hkr:
I just switched from DeviceLock to TouchLockPro, as since 2.03 DeviceLock is not able to blank the screen anymore.

So, TouchLockPro offers much more possibilities, however, I just want to LockSuspend the device while OziExplorer is running.

With Cyberon Voice Command I could start TouchLockAction, but then I have to push zz to put the device in LockSuspend.

Is there a way (e.g. registry setting or .lnk file) to automate this with a single Voice Command. The Command should execute "\Windows\TouchLockAction.exe" LockSuspend ...

You guess, I'm quite a newbie regarding programming, therefore I would really appreciate your help ... Thanks guys ...

Edit: found out: Just 30#"\Windows\TouchLockAction.exe" LockSuspend in a .lnk file and put it in \windows\startmenu
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Hi Zuinigerjder,

I upgraded to TLP 2.2.2 yesterday and would like to point out a few issues that I have found so for. Most of these will be related to the new method of sub-classing that you use.

1. When waking up the device by pressing the power button the TF3D clock does not update until the device is unlocked. This is probably because TLP has focus and does not allow the home screen to update.

The time on the clock is the time when it went to sleep, that got me thinking that it could be related to the two methods you use to lock the device, as it locks when it goes to sleep therefore freezing the clock. When it wakes up the sub-classing you use stops the TF3D clock updating it self until it has been unlocked.

2. I also have the problem of seeing the x at the top right corner of the screen once unlocked this disappears if I move away from the home screen then back again on TF3D.

3. Less regularly the capacitive sensor fails to respond, and I need to wake up the device again, my current setting is 22 to unlock. I have not tried another setting, but I do not know if this area of the capacitive sensor is less sensitive then the other areas.

Finally, not to important, but maybe something to consider for your next release:

You have an option to disable using the stylus sensor.

You have an option to disable using the keyboard slide sensor.

Why not have an option to disable using the light sensor?

Why not have an option to disable using the G sensor?

Why not have an option to disable using the capacitive sensor?

That way those sensor API’s can be taken out and not loaded / used therefore reducing your memory requirement.
[Touch Diamond, MDA Compact IV Themes and Apps] Kater Karlo:
Black Password Screen

Since version 2.2.2 I have the bug that if my Diamond is not running for a few hours and the password lock of Windows Mobile comes into play I do get a black screen instead of the Windows Mobile PIN pad (only the top bar with the Start Menu and the TouchLockPro indicator is visible). The device does not freeze. I can successfully unlock the touch screen and the hardware keys with TouchLockPro but the screen remains black and i am unable to enter the PIN. I do then have to reset the device :(

This behavior has started with version 2.2.2. No other software has been installed. I only upgraded from 2.2.1 to 2.2.2.

I will start a debug log now and post it as soon as possible (might take one or two days)

Greetings K
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi,

I've the "exact" same issue of black screen, but after an incomming call.

Phone in my pocket, incomming call, I get the phone, unable to answer with the finger as the device is still locked (annoying really, does a solution exists ???), remove the stylus to unlock and answer the call, device screen goes black, end the phone call and press the on button to light up the screen.

The TF3D crash most of the time when I close the phone screen, TF3D screen is black, I've to restart the phone or TF3D to go back to normal.

I've also triedyour 99999999 tips for on/off stylus in/out lock, and it crash the config screen when I go back to config and it reset the setting to 1000 or any random other value. Error in Init Form is returned every time....

Regards

I've an HTC HD
[Touch Diamond, MDA Compact IV Themes and Apps] Kater Karlo:
Black Password Screen

And here comes the debug log (sooner than expected).

Greetings K
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Here is my log.

I just entered config, changed 1000 to 99999999, exits the config, closed the app config screen, touched the clock, entered config again and moved to the config tab again.

as always I've got a crash.

I'll let the log running and sent it again when TF3D crashes.

I just remarked something, when I've an incoming call I've seen sometimes the -1, -2 and -3 displayed on the app icon and the phone unlock, I've to figure out how this is working ;-)

Regards
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Here is the Black Screen crash log.

Regards
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
I just realized the black screen issue I'm facing is not crashing TF3D.

See the picture below:

Notice the top right cross on the icon bar.

And here is the 9999999 error message:

Hope it will help to solve these issues.

Regards
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Is it or would it be possible to have the phone to unlock on incoming call, but not stays lock when using bluetooth?

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] AbuYahya:
omnia Version

omnia has light sensor and accelorometer but is wqvga. Omnia compatibile version would be very nice to test (currently gives errors and crashes in some states)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
version 2.2.3 which should solve the x problem and crashes

Hi,

I just uploaded TouchLockPro 2.2.3, which should solve the x task manager button problem.

I still have to upload the index file, but you can download already the new version via this link.

Hope this solves the annoying problem of 2.2.2 with the x button and the crashes.
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
@ ZuinigeRijder:

what about my problem, i can unlock after 5 seconds?? should i post another logfile??
[Touch Diamond, MDA Compact IV Themes and Apps] momyc:
2.2.3 seems ok

Hi ZR ,

Yes the X thing is fixed.

Playing for few minutes now , it seems ok for me.

(HTC Diamond Rogers ROM 1.93)

I'll keep you posted.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I recreate the BattClock every 5 seconds, to make sure it appears on top of other windows (otherwise you would not see the locked BattClock, when there is a full screen program). This is also needed to get the capacitive touches (get focus).