yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Sad to here this. However, I think the unlocking is not due to my program. Of course, when the screen goes on, my program will unlock using the Light sensor. With the problem you described, I think it is best to disable the auto-unlock, by setting the registry setting:

UnlockOnLightSensorTime = 0

And enable the suspend on backlight off.

SuspendOnBacklightOff = 1

Is there some other program running in the background, which wakes up the phone once per 3 minutes......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is for me a mystery, especially because my program cannot harm the device programmatically. Looking at what is not working:

AutoLockOnPowerOn=1 - not working

SuspendOnBacklightOff=1 - not working

Vidrate=1 - not working

I expect some program is making sure the phone will never suspend. That is possible by a program, because it can set the minimum power requirement.

That the vibrate is not working, can be also related, because when the setting is LockIndicator=1, it will only vibrate when it gets locked and the screen or backlight is off.

Another reason can be that the power button is not working anymore correctly or another hardware key is not released, so the backlight goes never off.

Do you see the backlight going off?

The only thing I can do, is give you a version with debug logging enabled, so you can see what my program sees as external events. Please let me know if you need this.

Hope you can solve this nasty phone problem.
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
i have both of these settings, if you see my other post i have been experiencing some rather strange problems, and tonight i had it crash on me, and something called:

gwes.exe

crashed after touchlock.exe.

i really dont know whats going on!!

MG
[Touch Diamond, MDA Compact IV Themes and Apps] Pietje_1985:
You're welcome mate! not a big deal...I also didn't know from the beginning how it would be possible for the program to work with an empty registry ...hehehe:D (now I know)

Cheers!

Jeroen

At this moment v1.1 works the best for me...

I have the option AutoLockOnPowerOff added in the registry +0 because I had some calls and during the call my device locked and I had to unlock it before I was able to hang up...since that registry entry

NO PROBS anymore....

for this moment I will stick with V 1.1:D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Version 1.4

I have just posted the improved version 1.4. See post #1 for the improvements.

Hope you enjoy this version :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There is someone else with a CDMA device, who says it is partly working.

See post 199. Maybe you should contact each other.

I uploaded version 1.4, which has debug logging possibilities (see post #3), so you can try to enable it, to see what TouchLockPro sees as events. You can post a log file, so I can have a look.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I uploaded version 1.4. There you can enable debug logging, to see what TouchLockPro tries to do. But maybe the disabling of the TouchPanelOnly is not working on the Sprint :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
How did it go further with your phone. Do you still have problems?

Anyway, I uploaded version 1.4, which closes the light sensor when the screen is off and did other improvements.

Also debug logging can be enabled, so you can see what actually happens from TouchLockPro point of view.
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
Three things to report:

1.) The capacitive 3-touch is working WAY BETTER!!! It's almost too sensitive. But I can unlock it very easily. Yeah!!

2.) The program sometimes gets confused after a phone call. Here's what happens:

a.] Call comes in so I unlock using 3-touch to answer.

b.] Call ends so I hang up but immediately touch screen to keep unlocked.

c.] Program displays that it is locked via battclock at top, but its unlocked.

3.) I can still answer calls when locked via lock TouchPanelOnly. In fact, I did a lot of testing and it appears that its not limited to incoming calls. If I repeatedly tap the panel I can still launch programs from the shortcuts on my Today screen or even on the Start menu by tapping the Win icon.

With regards to #3 above, I disabled ALL of my Today plugins and stopped all other programs such as Voice Command, TouchPanel and Quick Menu, and it still does not lock the touch panel 100%. Repeated taps still allow me to open the Start Menu even though it is locked.

Attached is a debug log file if you would like to look at it. I had to zip because of the size.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I knew the touchpanel is not 100% waterproof. What is the experience with locking everything, so also the hardware keys (LockTouchPanelOnly=0)? Is that working?

Looking at the log file, you see that it tries to disable the touchpanel regularly:

SetDisabledPanelOnly(true)

Note that I have tried to see if the touchpanelonly it is working on my TD. I could no longer get touches via the touchpanel when locked (tested with Opera). So I cannot also be something special for the Sprint CDMA Diamond.

How are others experiencing the LockTouchPanelOnly=1 :confused:

Because I normally do not use this setting.

Looking at the log-file, it is nice to see some other alternative usage, that is Ok :D

* UnlockOnLightSensorTime: 0, so you disabled the light sensor

* LockIndicator(false) You will only see the lock indicator when it is locked

* ClockX: 185 Another postition

* ClockForeground: 16777215 Another background color when locked
[Touch Diamond, MDA Compact IV Themes and Apps] kabronsete:
I've found a problem:

My settings:

"LockIndicator"=dword:00000000

"SuspendOnBacklightOff"=dword:00000000

"UnlockOnLightSensorTime"=dword:00000000

"LockTouchPanelOnly"=dword:00000001

"ClockX"=dword:00000000

"ClockY"=dword:00000000

"ClockWidth"=dword:000001E0

"ClockHeight"=dword:00000003

"ClockBackground"=dword:00000000

"ClockForeground"=dword:000000FF

"ClockClickable"=dword:00000000

"ClockLockActiveTime"=dword:00001F40

"LogDebug"=dword:00000000

"LogDebugDetailed"=dword:00000000

-When phone is LOCKED and backlight goes off the 3 pixel red bar showing that phone is closed dissapears, it must be displayed also when backlight is off (I have SuspendOnBacklightOff=0).

These 2 has relation with ClockLockActiveTime=8000 :

-Every 8 seconds the red bar is erased and redrawn.

-When I start the bar is not drawn until some seconds (may be 8) later.

This soft covers all my need except for the command line program to LOCK, UNLOCK and TOGGLE_LOCK (the last one is the best for me), please add it soon.

Best Regards,
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
I am having so many problems with this lock now:

ClockHeight=1 - working

ClockWidth=1 - working

ClockX=479 (1df) - working

LockTouchPanelOnly=1 - not working

UnlockOnLightSensorTime=1000 -Dont Know

Vidrate=1 - not working

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

LockTouchPanelOnly - it works initially when the stylus is replaced, but after a few seconds it is no longer locked, but the lock is still showing as being engaged by the white pixel in the corner of the screen.

UnlockOnLightSensorTime - i dont know as i am sat in a dimly lit room!!

Vidrate - there is no vibration to say the device is locked or unlocked.

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

along with the ones not working above, the following is not working:

SuspendOnBacklightOff = 1 - when the back light goes off, or i press the power button, the device does not lock.

also when i lock the device with the stylus and turn the screen off sometimes there is a single vibration, i dont know why, but when i check the device, the white pixel is showing in the top corner of the screen to say the device is locked but when you touch the touch panel, it is working and usable.

i got so frustrated with this, i actually flashed my device tonight thinking i had a bug or virus or something, but on a fresh install it is doing exactly the same thing.

im going to bed!!!:mad:
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
To answer your question, when I lock EVERYTHING, it works GREAT! My only problem is that since I don't wear a watch, I check the time on my device many times a day. If I lock everything, I have to unlock the device just to turn it off or wait 1 minute for the backlight to shut off. If only you could figure a way to leave the power button active. If you could do this then great! I would lock everything. The other problem has to do with silencing incoming calls quickly. By leaving the power button active, I could simply press it once to silence the call.

It may appear that the touch panel is locked on your device when using LockTouchPanelOnly=1, but try repeatedly tapping it for 10 seconds and see if its really locked. You may be surprised. :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I had this approach also a time ago. But I switched to the current polling approach, because the BattClock needed to have focus. So it was not working all the times. When locked, it was normally (I recreated the locked BattClock for that), but when unlocked this did not work always. So I go not into that route again.

The current polling approach works also in the background, only sometimes not in manilla.

I have found a problem in opening the sensors, so maybe that helps. I am not sure, however, if this solves the manilla problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It does not hurt to have a youtube video, but I am more interested in other types of phones, Diamond, Touch Pro, Touch HD, do they also have the problem the soft keys are not locked? Anyone?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I meant the capacitive NavSensor, available on the Diamond and Touch Pro.

You have to await the next version, for the SCREENON feature in combination with the unlock key sequence.
[Touch Diamond, MDA Compact IV Themes and Apps] bent_e:
Hi ZuinigeRijder,

First of all, thanks for a great program. I am using ver. 2.6.1 and with the new locking method, I can now use "3 x middle button press" on my Diamond (official 2.03 rom) to unlock my phone.

However, when I do a softreset of my phone, the phone no longer locks. TLP will show that the phone is locked (white battclock and blink the LEDs), but neither the touchscreen nor the keys are locked. To remedy the problem I have to uninstall TLP, softreset and reinstall TLP. Then it works as expected, until I softreset....

Best regards,

Bent
[Touch Diamond, MDA Compact IV Themes and Apps] cichy3000:
And it will be a great move :)
[Touch Diamond, MDA Compact IV Themes and Apps] Whistle_Master:
I've got a problem with the last version of TouchLockPro (v2.6.1) and HTC Touch Diamond.

I've configured the LED setting with 256 (Pulse center repeatedly)

When the phone is locked and on, the center light pulses repeatedly. When I swith off the phone, the center light goes off. Until there, nothing wrong :p

The problem is when you connect the phone to AC power, the center light also pulse to show that the phone is in charge.

You can try yourself:

1) Phone is off

2) Plug-in AC power

3) Phone goes on

3) Center light starts to pulse

4) Center light stops to pulse

Another one:

1) Phone is on

2) Plug-in AC power

3) Center light starts to pulse

4) Switch off phone

5) Center light stops to pulse

I think that it should have an option to not take in account the light setting when the phone is on AC power.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
I was pretty sure my method was working without being the foreground window. I am creating it as a disabled pop up (3rd parameter = WS_POPUP | WS_DISABLED) and no window is visible on the screen. Maybe I am wrong - need to test more I guess - but it does seem to solve the Manila issue.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
This is a known issue and is because you are soft reseting with the stylus. The "stylus out" flag is only changed when the "stylus out" status changes while the phone is on. Therefore, if you reset with the stylus, you have taken the stylus out, setting the flag to "out", then the phone turns off, you then replace your stylus before windows starts up and the "stylus out" flag remains set to "out" even though it is in.

There is a known way to get around this for CDMA Touch Pros (and Diamonds), but for reasons beyond my knowledge it does not work in GSM Touch Pros (and Diamonds).

GSM and CDMA Workaround:

Pull out the stylus and put it back in after you soft reset.

CDMA Only Workaround:

If you have a CDMA Touch Pro or CDMA Diamond you can install nueSIPStylus found at http://www.nuerom.com/BlogEngine/page/nueSIPStylus.aspx

There is an option to "Query stylus position at boot" which will set the "stylus out" appropriately - thus fixing the issue in TouchLockPro

Again - THIS FIX DOES NOT WORK IN GSM PHONES
[Touch Diamond, MDA Compact IV Themes and Apps] bent_e:
I am afraid that is not it. I just tried to softreset with the stylys in using TLPs softreset function. The problem appeared again - TLP shows the phone is locked but it isn't. If I go into TLP settings it also correctly shows the stylus sensor as in.

Best regards,

Bent
[Touch Diamond, MDA Compact IV Themes and Apps] jbrady33:
If anyone gets the button assignment for the middle button on a TouchPro (Verizon if it matters) please post, would love to get double or triple click on the center button to unlock working.

In combo with that, any way to make the center button 'wake up' the phone after sleeping/locking it with the power button? Right now the only unlock I have is the light sensor and keyboard/stylus out - all of which is fantastic and working great but sometimes the room is a little too dark for the light sensor to unlock it - middle button woudl be nice for one handed wake up.

Love this software, if someone out there gets Phone Canvas (slide to answer with curtain) working for the Verizon (CDMA right?) TouchPro I will be a happy camper for as long as my short attention span allows :)
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
OK - Sorry - Thought I had it - Oh well - I'll just be quiet and let ZuinigeRijder take it from here.
[Touch Diamond, MDA Compact IV Themes and Apps] ugumba:
I've been unable to reproduce this problem on my HD. Did try quite hard.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will not control the LED when not on battery. Will include this in the next version.
[Touch Diamond, MDA Compact IV Themes and Apps] bdemarco:
Middle button code for Touch Pro

It's 134...the same as the Touch Diamond.

Cheers,

Brian
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, because when the BattClock is white, TLP thinks it is locked.

Can you enable debug logging, reproduce the scenario and post \TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I expect the same number as for the Diamond, 134.

I am busy with a version, where it is possible to keep the phone alive with the screen off, so TLP can detect the middle button press, and when it unlocks the screen will be on.

If you want to do that via the power button, then I need to introduce a KeepAlive command, so you can suspend via the power button (TLP keeps the phone alive, so the unlockkeysequence can be detected) and can put the screen on.

I will see if I can add the keepalive command in the next version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No worry, I appreciate if others try to answer questions.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, so it looks like this is something specific for the Diamond2.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Yep - you're absolutely right - further testing revealed that my method does not work if some other window steals the focus - which is why it would not work when the phone awoke because of a phone call. - but that's so strange why manila is able to screw things up using your method... maybe a combination of window and windowless capacitive sensing is the key... just a thought, maybe unnecessary overkill....
[Touch Diamond, MDA Compact IV Themes and Apps] bent_e:
Hi ZuinigeRijder,

I enabled detailed logging and reproduced the scenario. First I locked my phone by pressing the powerbutton. Then I turned it on again and confirmed that the phone really was locked and then unlocked it. I then softreset the phone (you will notice about a 1 minute gap in the log) and again locked the phone by the powerbutton. I then pressed the powerbutton again, TLP battclock was white, but the phone was *not* locked. I pressed the unlock sequence and battclock turned black indicating that TLP now also thought the phone was unlocked. There are a few other unlock's in the log-file because the phone automatically unlocked by the light sensor.

I hope this gives you a clue.

BTW, I am *not* running TouchFlo, but SPB Mobile Shell 3.0.1.

Best regards,

Bent
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Middle Touch "Sensitivity"

ZuinigeRijder,

I wanted to see if I could make TouchLockPro more "sensitive" to GESTURE_MIDDLETOUCH because it seemed to not pick up certain touches.

So I added some debugging to output startData.action while touching the middle button over and over in slightly different areas and ways.

What I found:

17 or 81 (which you already handle) come up when touching the center of the middle button with the tip of my finger.

84 or 85 come up when touching the center button with my full finger print, potentially overlapping the raised circle.

68 or 69 come up when touching the raised circle.

I thought I also saw a 21 at one point but was unable to reproduce it and hadn't yet started to log the results.

Conclusion:

I have added these numbers to my local copy and personally like the results - although others may not - who knows. You may like to leave it as is or add these numbers to make it more "sensitive" to GESTURE_MIDDLETOUCH.

I am curious to know how you came up with 17 and 81. Do you have a datasheet of some sort that says what means what? Or did you view the results of touching the middle button? Or ...?

Edit: I also found additional Left Touch and Right Touch numbers that may have been ignored previously
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked into the log file, and nothing strange from TLP perspective. But maybe it is related to SPB Mobile Shell 3.0.1 or because TLP starts too soon (there is a delay of 30 seconds now, but maybe that is not enough?)

So there are 2 things you can test.

1) See if the problem is related to too less wait time at startup

Start TouchLockPro manually, instead of automatically at startup

a) (re)move the TouchLockPro link in the startup menu

or

b) copy all the files in directory %Program Files%\TouchLockPro to another place and deinstall TouchLockPro. After soft reset and waiting some time, just start TouchLockPro.exe in the copied place.

2) See if the same problem occurs without SPB Mobile Shell

a) using TF3D

b) using Standard Windows Mobile shell

Hope this gives new clues.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The strange thing, is that it only sometimes does not work. And when it does not work, doing a tab right-left makes (if unlocked or issues by TLP) it work for TouchLockPro, without doing anything different. So Manila does something nasty, so TLP cannot open/read the nav sensor......till a tab right has been done.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have found the values by trying out, like you.

I have also the settings around the middle button as option.

6 (middle center button area 2 and area around the middle button)

But because that might be too sensitive, it is an option.
[Touch Diamond, MDA Compact IV Themes and Apps] bent_e:
1) If I remove the link to automatically startup TLP and then startup manually, TLP works OK. I am having difficulties staring up TLP though, as I have to launch the program a couple of times before it gives me the battclock.

2) Disabling SPB Mobile Shell and just starting up in the Today screen does not change anything. Unfortunately I forgot to test with TF3D.

Could you make the startup delay for TLP configurable? I could then try to set it at f.ex. 1 minute and see if that solves the problem.

Best regards,

Bent
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Do you know how to reproduce the Manila thing? Something that always causes the issue?

I have been trying, both with my altered version and your unaltered version and I can't reproduce it - the capacitive sensor never fail.

Maybe it is because of the ROM I'm on and/or the version of Manila I'm using. Maybe they fixed that "nasty" thing they were doing in older versions of Manila.

I'm using JD's latest Windows 6.5 kitchen found at http://forum.ppcgeeks.com/showthread.php?t=67568 with the Sprint Manila option checked.

Is there maybe a Manila cab you know of that works with a CDMA Touch Pro that I could install and test with? I'll look some more when I get a chance
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, it looks like the startup delay is too small. In the next version I will set the delay to 1 minute. I do not make it configurable, because at the time I delay, I do not want to access the registry yet. I am in a testing phase, so hopefully I can post it in a few days.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The problem was not there till the official 1.93 HTC ROM. I appeared with version 2.01 onwards (and ROMS based on that version). It is not reproducable. Sometimes, after a long sleep, it occurs, but not always. If I try for a few days, then it occurs sometimes. :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I just discovered a bug... When my device connects to the internet to download emails, it unlocks !! I reproduced the problem with debug on :)
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Oh No! Build 21725 + Nav Sensor = :(

EDIT: NEVER MIND - It is working again - I hard reset and reinstalled and it works again - I am way too bad at jumping the gun on reporting stuff - but I will leave this post here so you can see what happened - no clue why this happened but all is well now.

ZuinigeRijder,

Something changed in Windows Mobile 6.5 Build 21725 that has apparently affected HTCAPI.dll in regards to the nav sensor - breaking that feature in TLP so I can nolonger unlock via the nav sensor :(.

After calling DeviceIoControl, data.action is

never

0! In fact, the entire data object remains the same until you touch a different part, instead of changing when you lift your finger of the nav pad.

This means that the capacitive sensor code does not work as is because it waits for data.action to be 0 to tell when the user has finished the touch.

While debugging you can see in the output window, either from the SetMode or GetMode, a debug message that says "Data Changed!" but I don't know how to capture that. Do you? It would be very helpful.

Maybe the structure changed and now has more members maybe?

Have you seen build 21725?
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi,

Just installed V2.6.1, and I've noticed the following :

- TAPI !UNLOCK not working on incoming call (how to unlock only the touch screen on incoming call??? now only Light sensor is unlocking correctlly)

- Unlock light sensor time value not saved/retrieved correctlly

BR