yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
Love the software. Phone rings & vibrates much sooner than when using S2U2. Want to use it but it appears that there is a small bug. It may have already been documented, but I didn't see it in the thread.

When TLP v1.3 is set to lock touch panel only, it will not lock the on screen soft keys for an incoming call. In other words, I can still answer an inbound call by touching the screen. This is a problem if I have my phone in my pocket. This happens when I use the WM5 skin or even the HTC Diamond phone skin.

If I use the lock all keys, sometimes I miss a call because the captive tap seems way to sensitive. Meaning that if I tap a 1/2mm off it doesn't recognize the tap in the same area so I need to start again. Is there a way to widen the area? This would be much better especially since I have fat fingers. ;)

In addition, if I lock all keys, then I have no way to mute an incoming call without first unlocking the phone and then tapping the volume key, the End key or the power key. A few times in a meeting I just couldn't unlock the phone using the 3-tap and the ringer played for a good 20 seconds [I was holding my bag, coffee or laptop in the other hand]. Boy that way embarrassing! :eek:
[Touch Diamond, MDA Compact IV Themes and Apps] kabronsete:
Please consider adding 2 features:

1.- Command line options to: LOCK, UNLOCK and TOGGLE LOCK: this is very easy to add and is for me the best way to lock (a direct access to a lock program).

2.- Display your icon only when phone is locked (in this way you can get the focus you need) and not display icon when phone is unlocked (so we can use our own battery icons). Also you can change the icon for a CLOSED LOCK to be more descriptive.

Thanks in advance.

Best Regards,
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
I completely agree with this, remove the clock/batt thing, many people are customizing the taskbar and using their own icons, also, there is a MASSIVE clock on the manilla home screen, so why have a really big clock, and then the clock that TouchLock adds, and everyone has a watch (well if you have one of these devices i would assume you would own a watch!!!)

as kabronsete said, having an icon displayed in the taskbar would be much better, firstly you would gain focus and the capacititive touch would work better there would be no delay, all of the registry settings for the clock/battery meter could be removed as they would be redundant.

I really liked the lock symbol you had on StylusLock, couldnt that be used?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am not familiar with cdma diamond, but I found a review here.

Is there an error message, when installing TouchLockPro?

I got also a PM request from a Touch HD user, to make TouchLockPro available for that device too. There it could not load the capacitive sensor library, and TouchLockPro exits. For the Touch HD I will make a version, so the capacitive sensor can be disabled, so you can still use the other cool features (Stylus, Light sensor, etc). I do not know if the light sensor library is available on the Touch HD, but that can already be disabled.

For the CDMA I need to know what the problem is. Apparently the program does not exit, but also does not lock. So there are a few questions:

1. Is Stylus(BattC)lock 1.6 also not working on the CDMA?

2. Check if the Stylus changes are written in the registry, as described here

3. Is the BattClock changed to locked, but it does not lock?

It is possible that the locking API I use from HTC, is not available in the CDMA version and that is the problem. If the BattClock shows it should be locked, I know at least where to search......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, I disable the whole TouchPanel (power off), so it is a bit strange that

the softkeys are not locked (and the rest is). I will test this behaviour.

I have good experience with unlocking using the area 1 or 3, as described in post #2, even one handed. The only thing I can do, is change the algorithm, so it does not reset to 0, when another area is touched. In practice, it means I have to remember the touches for all the 3 areas.

In principle you could use the HTC built-in mechanism to mute phone on face flips, see e.g. disable-and-switch-off-mute-call-on-phone-flip-face-down-feature-in-htc-touch-diamond/
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This will be part of my upcoming separate action screen program. But because I first integrated the light sensor and I want to have the bugs fixed first, this is a bit delayed :p

This should be possible already, with version 1.3.

Just use: LockIndicator = 0

See for more details: post #3

Currently I show the capacitive touches in the BattClock. So you will miss that then. And the BattClock is not an icon at all, just the text is displayed on the rectangle you can define with ClockWidth and ClockHeight. You can make a small strip on any place you like, to indicate the locked status, with the settings in post #3.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, the BattClock is not an icon, it is just an rectangle, where the text is drawn upon. Making an icon of it, would complicate things. It would not mean better capacitive touches. I will think about it. For now, the only thing you can do, is change the size to a small strip or make it a 1x1 pixel. You can put it on any place, it should still get the capacitive touches. However, I still have to try if this is now working correctly in version 1.3.
[Touch Diamond, MDA Compact IV Themes and Apps] kabronsete:
I know. But adding a command line option (/lock /unlock /togglelock) to current executable is quite fast, and will add another way to lock or unlock that is very useful.

Action screen is very good also, but in the meantime a little exe with this 3 command lines or the main .exe would be great.

I will test this again....

Thanks.

Best Regards,
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I tested today with settings LockIndicator=0 and TouchPanelOnly = 1.

It works as expected. When the phone is unlocked no BattClock is shown. When the phone is locked, the locked BattClock is shown and the capacitive touches can be used for unlocking.
[Touch Diamond, MDA Compact IV Themes and Apps] Kessler:
I will check on these things and reply. I also should have mentioned that I'm using a cooked rom. (3.4)

I'm really excited to get this working as it seems to be by far the most elegant solution.
[Touch Diamond, MDA Compact IV Themes and Apps] Kessler:
There are no error messages on install.

I just tested and it also doesn't work. Also, they both don't display battery time properly. Sometime it shows the right % and other times its stuck on 100%

I currently have 1.3 installed and the registry entry is in there. It was on 1 ( I had the stylus out :)

It doesn't lock or show as locked on the battclock. Even more interesting, it did lock for me once, when I was messing with the stylus in and out and tapping on battclock. I unlocked it by triple tapping the phone and home area. Haven't been able to get it to lock again.

If you need any other information (screenshots etc) please let me know. Thanks for your help I really appreciate it. It looks like a wonderful program!
[Touch Diamond, MDA Compact IV Themes and Apps] Diamond Geezer:
First of all good work. It's getting close but I have a few constructive gripes.

is it just me (fat fingers) or does anyone else find it hard to lock by pressing the batt clock icon ? It takes me a good few (infuriating) gos to hit it. I get either system status or task manager coming up. Maybe use 3 capacitive taps to lock as well ????

Also hitting the capacitive area 3 times to unlock whilst it is ringing seems quite random and I have missed a few calls because of it.

Why not use a two button press like we used to have on the nokias ( i'm remembering menu - star). Have it so we can choose which two buttons.

-

Cheers for the good work
[Touch Diamond, MDA Compact IV Themes and Apps] Pietje_1985:
It sounds good your opinion about the capacitive unlock procedure to change that to the 'nokia'style with menu - * , but it's not possible to press any buttons during the lock, only gently touch it.....you see that's what it's all about....:rolleyes:

ne way good thinking:D
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
Thanks for your quick response!! I tested it some more last night and still no luck. :(

First it may be important to note that I am using a Sprint HTC Touch Diamond. This is a CDMA Diamond. All functions work well except the touch panel allowing me to answer calls even though it should be locked.

As far as the rotating face-down to mute the call, that should work, but since the phone is already ringing at that moment it takes focus from the orientation of the phone. Once the call has completed, then it will go into mute mode. I tested several times on a glass table. :D
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
Today i have very bad experience with v1.3.

the light sensor keeps unlocking my device everytime i lock it and put it down. it sits there for 2-3 mins then unlocks.

why does the device do this? i havent touched it, so y it unlock?

the reason today has been bad, is when i sit at work i dont have my phone in pouch, i lock the device, put it down and carry on with what im doing, the device unlocks (and i dont notice it unlock) then i put it back into pouch and out to lunch.

during lunch, i called 6 people from my pocket with my apparently "locked" device 2 of whom were my superiors and they didnt take kindly to 5 minute voicemails of the sounds of my pocket!!

I also sent a text message to my parents landline (WTF is that about - i didnt even know you could do that!!) and my mum nearly had a fit thinking i was getting mugged, listening to a robot voice on her house phone attempting to read a txt

as i am typing this message, @ 19:09 my device has put itself to sleep, and as expected it has locked itself, brilliant!! @19:12 it has decided to unlock itself again!

VERDICT:- light sensor is a risk!! and consumes alot of power for VERY little/no benefit - At The Moment

thanks
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, set CommandCallIncoming to !UNLOCK. But then also the hardware keys will be unlocked, so you can still have missed calls.
[Touch Diamond, MDA Compact IV Themes and Apps] muhlatte:
so maybe i could set !screen on or something like that on incoming call and otherwise i could let the screen be off?!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, that is currently not possible. But you can configure TouchLockPro to suspend again at power on, via SuspendTimeOutPowerOn = 30000. If you set this e.g. to 10000 (10 seconds), your phone will go asleep within 10 seconds if not unlocked in the mean time.
[Touch Diamond, MDA Compact IV Themes and Apps] rivit:
Problem

Ok, now i got a SERIOUS problem. I upgraded to ver 2.5.2. Now when the phone should be locked (TouchLockPro signalises that too!) it isn't locked :eek:!!

I tried reinstalling, softreset, default settings; then i tried returning to ver 2.5.1 but here now the same behaviour.

Don't know where's the problem and what i should try next.

OK.. solved. After I deinstalled manually BEFORE (re-)installing touchlockpro everthing works fine again.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
So far so good... I give you my blessing with 2.5.3 :) It's working like a charm :D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro version 2.5.3

Thanks. Just uploaded version 2.5.3 :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
Using 2.5.3 now, but since, I think 2.5.1, I'm constantly losing the battclock.

I was able to replicated it, but opening the keyboard on my TP and then closing it.

Can this be fixed?
[Touch Diamond, MDA Compact IV Themes and Apps] texasez:
Touch HD unlock methods?

My wife crashed her phone and my son had a touch hd which I have tried to use touch lock pro. The only way I can get the phone to unlock is to plug into power supply. Removing the stylus does not seem to do anything, the hard buttons at the bottom do not wake up the touch screen, and the g sensor does not seem to do anything either. I am not sure if the phone has a sensor for the stylus and the g sensor.

what are the options for unlocking the touch screen? I want to have the phone screen lock on incoming call and to lock on back light off. Thanks.

Larry
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, in 2.5.3. the stripe problem is fixed. So I am puzzled about this one. Can you enable debug logging (LogDebug=1) and post the log file \TouchLockPro.log.txt. Please note the exact time when the problem occurs, so I can have a more detailed look. I do not have a slider, but I will try out myself too with portrait/landscape changes.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It should unlock by the light sensor, when there is enough light. What gives TouchLockPro as value in the TouchLockAction Light Sensor settings screen?

Maybe you have also defective Stylus sensor (dust?). What gives TouchLockPro as value in the TouchLockAction Stylus settings screen?

Also the GSensor works with the Touch HD. You can see the positions in the TouchLockAction GSensor settings screen. Is this giving orientation changes? If yes, you can make the GSensor moves easier, by configuring unlock to e.g. 43 or even 93.

You can only lock the TouchPanel (LockTouchPanelOnly=1), so you can still pick up the phone without unlocking.

You can enable debug logging (LogDebug=1) and post the log file \TouchLockPro.log.txt, so I can have a look what is working and what is not.
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
Here you go. I turned on logging, opened slider, closed slider and battclock was gone.

Can this be fixed?
[Touch Diamond, MDA Compact IV Themes and Apps] MadMax1978:
Since I unchecked this option, I never had the problem again that I couldn't use the extra functions I mapped to the volume buttons!!

Still using the 2.4 version!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for reporting this problem. I was not aware of it. I could also reproduce it now :mad:

Of course I will find a solution for this and upload a fix ASAP.
[Touch Diamond, MDA Compact IV Themes and Apps] oruam57:
I am using TouckLockPro on a Diamond2 and I like it.

Light Sensor ok.

Stylus Sensor quite ok but Diamond2 report stylus out when it is almost full extracted so SuspendOnStylusIn is not very useful and I keep it off.

GSensor does not work but I would not use it anyway.

Diamond2 has no NavSensor and Keyboard.

Unlock with a swipe on the Zoom bar would be fantastic but maybe I am asking for too much.

Phone API works as expected.

A small request: I would like to toggle between lock (screen only) and unlock status with buttons (I'am using AEButtons to map buttons to TouchLockAction.exe actions), while having full lock (screen and button) on other lock triggers. It seems to me that is not possible at the moment.

I would need and "action" as LockScreenTouchPanelOnly that combines LockScreen and EnableLockTouchPanelOnly but without memory of the TouchPanelOnly part after unlock.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.5.4

Just uploaded version 2.5.4, which should fix the problem.
[Touch Diamond, MDA Compact IV Themes and Apps] studentjunk:
no unlock on light sensor

I have noticed that my phone wasn't unlocking on light sensor with versions 2.5.3 and 2.5.4. It seems to work with the other methods. I love the new bar, the fact that the light sensor readings is now reported, and the vibrate on unlock is awesome. Attached are my log files and screenshot after being on for about 10 seconds.
[Touch Diamond, MDA Compact IV Themes and Apps] studentjunk:
working fine now. Not sure what the difference is.

For some reason it's started working correctly. I have no idea what is different. I am posting updated log files if you are interested.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You have configured DetectBluetooth. When the bluetooth radio is on, it will not unlock by light sensor (even if there is not a connection, something which is under investigation too add). Maybe that was the case?

Another reason can be, that you enabled the lock yourself, or when the phone was on, so unlocking immediately by the light sensor is not what you want. So it will only unlock by the light sensor after power on.

Sometimes you want to lock the phone with e.g. GPS on, so no keys/touchpanel is pressed. I use OziExplorer, so then you do not want to unlock by the light sensor. Recently I added even !BACKLIGHTOFF and !SCREENOFF with keepAlive, so the GPS program does not consume too much battery, while still GPS is active. But the program you want to lock must then allow to put the backlight off or screen off (not all programs allow that).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Great to hear that TouchLockPro is also working on Diamond2. Sad to hear that HTC left out the NavSensor in the Diamond2, because I find it really usefull. But Touch HD users also did not have this feature.

I am surprised, why the GSensor is not working on the Diamond2. Because I expect it has a GSensor in it? Can you post a debug log file (LogDebug=1) and post the debug log file \TouchLockPro.log.txt, so I can have a look what TouchLockPro is logging when loading the GSensor.

Because I do not have a foreground window, unlocking via the TouchPanel is not possible.

TouchLockAction recognises the following commands:

* EnableLockTouchPanelOnly

* DisableLockTouchPanelOnly

* Unlock

* LockScreen

* LockSuspend

Multiple commands can be given as parameter in one call and they will be executed in order. So you can couple a hardware key to a TouchLockAction command. Is this what you want/need :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] oruam57:
Yes, Diamond2 has the GSensor and TouchLockPro somewhat interact with it but it seems they do no understand each other well. Really, I was not very interested in this option so I gave up quite soon. I will try to find some time to generate the log.

I know I can lock (screen only) with button by combining the LockScreen and EnableLockTouchPanelOnly actions, but the last changes (or I so understood) the LockTouchPanelOnly option.

I'd like a new action to enter the lock (screen only) status as with LockScreen plus EnableLockTouchPanelOnly but without LockTouchPanelOnly option change. During this status I could use a button to unlock but after that (or any otherwise caused unlock or a poweroff/poweron cycle) the normal status (buttons ignored during lock) should be restored.

Notice that with the button I could restore the LockTouchPanelOnly option by combining the Unlock and DisableLockTouchPanelOnly actions but that would not happen with other unlock causes (let's say the stylus).
[Touch Diamond, MDA Compact IV Themes and Apps] vectorbl:
ANSWER

Do you think will be insert in this software above function? :D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, I have put it already on the wish/TODO list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am interested in the read outs in the TouchLockAction GSensor Settings screen. Are those not reliable? If yes, you can configure an easier orientation sequence to unlock, e.g. 43 or even 93. In case the light sensor does not sense enough light and you do not want to take out the Stylus.

If I understand your use case correctly, you can achieve this by this command:

"\Program Files\TouchLockPro\TouchLockAction.exe" DisableLockTouchPanelOnly Unlock EnableLockTouchPanelOnly LockScreen DisableLockTouchPanelOnly

This way, you unlock hardware buttons and touchpanel first, then lock only the touchpanel and set back the setting to disable touchpanel only. The latter will not unlock, but the next lock it will be a full lock automatically.

I did not test it, but in theory it should work.

Hmmmm, I looked at the source code and apparently I exit the TouchLockAction program after executing one command :mad:

I have to do the Exit() outside the loop.

I made a special test version for you. See attachment. You can try that one.
[Touch Diamond, MDA Compact IV Themes and Apps] dholakiah:
Hi,

I have Touch Pro, been using TLPro for a long time.I upgraded ROM to offical HTC ROM 5.05.405.1, mainly to solve Camera,Call Issues. Now, I find that BEEP command on touch lock pro not working. Vibrate on lock/unlock works, but BEEP do not work. I also checked registry,the value is 1. It used to work perfectly on older ROM.

Could it be because of my new ROM or I am not doing right settings ?

2. I am planning to flash EneryROM 2.xxxxx with Rhodium Manila this week end. Any advise? will this TLpro work on it ?

Sorry to ask too many question !

Thank you for wonderful program and your support.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It does only beep, when you configured Beep=1 and LockIndicator = 0.

But did you enable sounds in Windows Mobile settings screen, somewhere here: Start -> Settings -> Sounds and messages -> Events :confused:

I do not know if TouchLockPro does work on EneryROM 2.x, but if it just supports Touch Pro, then also TouchLockPro will run on it.
[Touch Diamond, MDA Compact IV Themes and Apps] dholakiah:
Hi,

thaks a lot. After making LockIndicator = 0 and Vibrate to 0, now it beeps.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe I should add a setting like Vibrate, so you can choose the number of Beeps independently of Vibrate and/or LockIndicator. I will set this on the wish/TODO list.
[Touch Diamond, MDA Compact IV Themes and Apps] oruam57:
I installed version 2.5.5 and tried with

"\Program Files\TouchLockPro\TouchLockAction.exe" DisableLockTouchPanelOnly Unlock EnableLockTouchPanelOnly LockScreen DisableLockTouchPanelOnly

Result: screen AND buttons locked, final status of LockTouchPanelOnly is disabled as before running TouchLockAction.

Then I tried

"\Program Files\TouchLockPro\TouchLockAction.exe" EnableLockTouchPanelOnly LockScreen DisableLockTouchPanelOnly

Result: same as above.

Then I tried

"\Program Files\TouchLockPro\TouchLockAction.exe" EnableLockTouchPanelOnly LockScreen

Result: screen AND buttons locked, final status of LockTouchPanelOnly is enabled.

Then I tried (using a script)

"\Program Files\TouchLockPro\TouchLockAction.exe" EnableLockTouchPanelOnly

"\Program Files\TouchLockPro\TouchLockAction.exe" LockScreen

"\Program Files\TouchLockPro\TouchLockAction.exe" DisableLockTouchPanelOnly

Result: screen locked, buttons UNlocked, final status of LockTouchPanelOnly is disabled (eureka!)

This would be what I need. The only problem is that I have to stare to the waiting cursor for a long long time, so a single equivalent action would be nice. Even better a registry key under HKCU\Software\ZuinigeRijder\ActionSettings because I noticed that this way to execute actions (again with a script) is quite faster than TouchLockAction invocation.

Maybe adding two keys to execute EnableLockTouchPanelOnly and DisableLockTouchPanelOnly would do the trick. May script would be somethig like that

Read EnableLockTouchPanelOnly into A

A = A + 1

Read LockScreen to B

B = B + 1

Read DisableLockTouchPanelOnly into C

C = C + 1

write A into EnableLockTouchPanelOnly

write B into LockScreen

write C into DisableLockTouchPanelOnly

About the G Sensor.

With GSensor disabled GSensor value (inside TouchLockAction/Settings/GSensor) was fixed at 0:unknown.

I enabled Use G Sensor, Use When Unlocked and LogDebug, then soft reset.

After soft reset GSensor value was fixed at 1:Landscape whatever PDA phisical orientation. Soft reset again.

After soft reset GSensor value was still fixed at 1:Landscape. Disabled GSensor and LogDebug. Soft reset again.

Here are the log files.