yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thank you for the kind words to me and all the other developers here.

I looked into the HTC Herald, and it does not seem to have the hardware sensors. I do not know if the Stylus is even detected by your phone.

You can try to see if that is the case, by checking registry key:

HKCU\ControlPanel\Keybd\StylusOutStatus

0 means Stylus in, 1 means stylus out.

If that is the case, you can use TouchLockPro, without the other sensors, but control via the Stylus. But of course, this is not so convenient, one-handed.

Not yet in the need of a new phone :D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do normally not use lock indicator stripe. Others are reporting this too. So I will have a look at my source code and test myself.

Hmmm, that looks like a bug.

Can you reproduce it?

Can you post a debug log file in that situation?

The CapacitiveToggleTime is unrelated to the ClockLockActiveTime, BUT I switch to the normal clock 1 second, after the ClockLockActiveTime is expired and thereafter I recreate the locked clock. During that time, no capacitive touches are recorded.

Thanks for the donation, my wife will be glad to drink with me a cup of coffee in the city :)
[Touch Diamond, MDA Compact IV Themes and Apps] Mr_Q:
It seems you have overlooked this post, or did not reply on purpose. :p

It seems that if I set the clock width to 640 my problem is solved. Although, it would be nice for users who turn there screen to landscape (by sliding the keyboard or manual using some program) that it automatically detects the width of the stripe/clock is shorter than the screen res.

A solution might be to use the height of the phone (when not in landscape) as width for the clock, when clicking 'stripe'.. Just some thoughts..
[Touch Diamond, MDA Compact IV Themes and Apps] Mr_Q:
I have had some strange behaviour of TouchLockPro too, sometimes (I can't reproduce it cause it just happens) the screen goes off and the backlight of the buttons are on..

The power button doesn't work and three times hitting the unlock-sequence doesn't work either, the only thing that worked for me was taking out the styles and the screen showed up again.

As soon as I found out when this problem causes, I will post it here (with the log).

[EDiT]

Is it possible to keep using the old unlocking behaviour regarding the capacative-finger unlock?

I'm pointing at using all the 3 area's for unlock, instead of just one.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange that it does not sense touches in the center middle button.

Just to be sure, it will only sense the button touches, not around the button. Maybe I will relax that in a next version.

Indeed the default value registered is 222, so if you like another area or less touches, just configure that.

You can check with CapacitiveFingerLock.ProofOfConcept.zip, (just extract the exe inside and run on your phone) which values are reported in the "last Where" box.

Maybe on your phone there will be different values :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The only thing I can think of, is the addition of the TAPI support is causing this trouble. You can disable TAPI, setting registry value "UseTAPI=0" do a soft reset and see if that problem still persists :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you check the last Where values with the program mentioned in post #722

In the previous version 2 touches was the minimum. One touch is very easy to unlock. Actually, inside a pouch also touches can be sensed, as someone else reported. So 1 touch seems not so a good idea.

But I will see if I make 1 touch possible in the next version.

Ok, that seems a bug. I will test and fix it.

Good to here that this version works better than 1.8.

Can you check what "last Where" is giving for values for the center button? Hope we can then solve this problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 1.9.1 Bugfix release

I just posted bugfix release 1.9.1.

It appeared that the incoming/connected/ended administration was wrong when there was an outgoing call, causing TouchLockPro not locking anymore.

Some other minor issues/improvements have been done, see history.

Please keep posting comments/problems, to make TouchLockPro even better.
[Touch Diamond, MDA Compact IV Themes and Apps] mspace00:
I am experiencing the issue of no TouchFlo3D when using v1.9.1. I am also using IMAP Pusher, which takes a while to load, and seems to load before TouchFlo3D. Is there a way to make the start up delay user configurable? :)

-Space

EDIT: Also with no TAPI setting enabled, when the phone is in suspend and a call comes in, it does not wake up, only flashes the leds and I cannot answer :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro sleeps already for 30 seconds now, so I do not think that is the cause. Or is it because of IMAP Pusher that TouchFlo3D is not loading?

Or is it more a general question?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is now available in version 1.9.2, the number 4 means any area.....
[Touch Diamond, MDA Compact IV Themes and Apps] haustin:
Re: v1.9 issues

It's consistently 17 for the middle button, 68 (rarely 69) for the area above and below the button.

I would agree about 1 touch being too easy for the left and right zones (and around the button), but the button itself is slightly lower than the surrounding bezel.

In another post you mentioned relaxing the constraint for zone 2 to include the area around the button... I'd request that you make that a different zone. As a matter of fact, I'd suggest a HEX numbering scheme so you can "OR" the zones:

1 = left

2 = button

4 = right

8 = area around button

Then, three taps of the middle button would be hex "222", but three taps on or around the button would be "AAA"; three taps anywhere would be "FFF". Instead of dividing by 10 as you're doing now, you'd divide by 16.

-hea

P.S. I've also had they keypad lights stay lit (until power-on + re-lock).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There was a problem that it would no longer lock, when there has been an outgoing call. Does version 1.9.2 still have this issue?

If yes, can you post a debug log?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Version 1.9.2 has fixed the middle button problem (17 is included).

And for any area, you can now specify 4.

I do not have yet made a different zone for the area around the middle button, I will consider this for a new version, including your suggestion.
[Touch Diamond, MDA Compact IV Themes and Apps] gorillaguzzler:
Is anyone else having a problem with voice command being activated at strange times when using touchlockpro? I never had this problem with the other versions but since installing 1.9.2 everytime i put my phone in the case with it turned off voice command activates. when i uninstall touchlock it quits happening.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for reporting this. I now made the Stripe setting in TouchLockAction to set the height resolution of the phone.

So it will also show the whole width in landscape mode.

I will post also a message in the HTC Touch Pro thread.....
[Touch Diamond, MDA Compact IV Themes and Apps] mspace00:
v1.9.2 seems to have fixed both issues! I will test further :D

-Space
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This could be because of the added TAPI support.

Does it also happen when you disable TAPI by UseTAPI = 0?

Can you post a debug log file, when it is going wrong?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I implemented your suggestion in version 1.9.2. Thanks for helping in this.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I saw in one of the log files you did set: EnableInputAtSuspend = 0.

This may cause the power button problems, just set it to 1.

When there is a call coming in, there is a setting to set the screen off, also when the stylus is put back, when LockMode is set. In that case the

backlight of the buttons will still be on for some time, but at my phone it goes off after some time.

And the old locking behaviour is now possible in 1.9.2, use 4 for any area.
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
I know I've mentioned this before and maybe I'm being petty, but couldn't you make the installer remove the add/remove entry for the previous version when you upgrade.

Every other program I have does that.
[Touch Diamond, MDA Compact IV Themes and Apps] gorillaguzzler:
OK i disabled TAPI and the behavior stopped. I reenabled it and now it does not seem to be happening that way either. It was doing it every time before so disabling it seems to have fixed the problem. but i cant post a log file with the problem because now i cant recreate it.

I really like this program by the way thanks for working so hard at it.
[Touch Diamond, MDA Compact IV Themes and Apps] groofoo:
if i install an update, will the setting remain from the old version or will it be overwritten?
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
It keeps all of your settings (which are in the registry) intact.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, I think the previous program is not removed, but overwritten.

Actually, TouchLockPro is also installed at the same place. But I think it is because there is a version nuumber in the installation.

Now I have in version 1.9 onwards AppToDate support and the version is shown in the debug log and the TouchLockAction screen.

So I think I will remove the version number in the installation, so then you do not need to deinstall a previous version (only when this version does not have a version number either). Till that time you need to deinstall the previous version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, let me know if the problem keeps away, also after some time (and soft-resets/boot).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Indeed, it keeps the registry settings.

If you want to have the default values as defined by TouchLockPro, then you can press the middle-bottom button in the first Settings Screen, to reset to the defaults. That will rewrite the registry with the default values.
[Touch Diamond, MDA Compact IV Themes and Apps] Mr_Q:
Thanks for your bugfixes / information through the forum and e-mail.

As I suggested you in my last e-mail, I would like to see an option to set the backlight-brightness (or atleast be able to check an option for full screen brightness / minimum screen brightness) when locked.

Something like the original lock from Windows Mobile.
[Touch Diamond, MDA Compact IV Themes and Apps] mspingeld:
With TAPI enabled the hardware button for end call would function causing me to hang up on people with the phone in its case. With TAPI disabled everything works perfectly.
[Touch Diamond, MDA Compact IV Themes and Apps] mspingeld:
With TAPI enabled the hardware button for end call would function, while using bluetooth, causing me to hang up on people with the phone in its case. With TAPI disabled everything works perfectly.
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
Is it possible that TAPI or anything else in 1.9 is eating up a lot more battery? My battery was pretty bad yesterday, but maybe it was just one day or maybe it was something else. Trying today with TAPI disabled.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think that is a good idea, to have backlight off when locked as configuration setting. I will add this to the TODO feature list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The intention is that it unlocks only, after you have connected a call. But the next post, says you are using bluetooth, so then it is indeed better to disable the unlock.

Actually, I would not disable UseTAPI, but uncheck "UnlockWhenConnected".

Then your screen will go off in your pocket too after connected (ScreenOffWhenConnected), saves some battery.

Also make sure you use 1.9.2, because 1.9 and 1.9.1 has some problems, especially it would not lock after an outgoing call and slow device when UseTAPI was disabled.

Thanks for the donation.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, see my previous remark.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am quiet confident with version 1.9.2, I had the feeling the battery usage was even better than 1.8.

But of course, all is dependent of the usage pattern.

Just make sure to use 1.9.2 and not 1.9, because there was a nasty bug, that it could happen that after an outgoing call it would no longer lock and slow device when UseTAPI was unchecked.
[Touch Diamond, MDA Compact IV Themes and Apps] gobmonster:
After having played with this program, i am very pleased with it, and i would like to make some request that i think could make it that much better

1. When the lock is activated, i want the option to have it go to the today/home screen. This is because i like to have it stealth locked. Also a look on device on would be good (from a fresh restart, not sleep... that way no one can use it with out the look combination)

2. When a headset is attached, i want different settings to take place. When im listening to music with my phone in pocket (touchpro), touching the screen is the worst, so i like having the lock on the screen and not the buttons, but eventually my timer interferes and cuts the device off. Plus, its annoying having to switch the profile over everytime i want to listen to music, id like it to be automatic. So how bout a back light off option instead of sleep when the headphones are attached.

Summed up, headset settings for 1. Backlight mode 2. Enable hardbuttons 3. No device off

3. I noticed that my device does not lock on backlight off, maybe theres a problem conflict somewhere? These devices never cut off anyways (backlight wise), but touchlockpro doesnt lock my phone on the device dimming.

Thats all i can think off. This is a great program that i was hesitant to try due to there not being any user friendly settings, but now that ive tried one of the later versions, im very happy i did. Thank you!
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
thanks a lot ZuinigeRijder, your app is becoming better and better than ever.

1.9 didn´t work well. but 1.92 is working nearly perfect.

after 24 hours using it, at first it worked perfectly for many hours but now it is producing 2 problems: one is that when having a 50 pixels height stripe at the bottom of the screen when incoming a call, stripe sometimes disappears (it is not the clocklockactivetime setting) or it simply never appears. i can live with it but the second problem is worse.

I have Gscroll also running and i know that it interferes with TLP so i decided to set one of the Gscroll actions to launch TLP in command line mode to unlock the device but it doesn´t work, it can happen two things: or TLP crashes with the typical .Net compact framework error or it simply doesn´t become unlocked.

it is strange, if i have Autolockinpoweron, it usually runs fine (but not always): stripe at bottom as it should be, double tapping sensitive area associated with Gscroll also unlocks it, no crashes at all.

But if there is an incoming call then i usually suffer those problems (but not always): no stripe at bottom, crashes or it simply doesn´t unlock.

When there is an incoming call, not only device is not unlocked, none of the associated sensitive areas respond to any touch (it is Gscroll, i know) but if i simply power on the device after setting Autolockinpoweron, then all these sensitive areas respond perfectly so it seems that it is TLP related.

what do you think?

attached are my log files. at 20:47 i have the .net compact framework error i commented before.
[Touch Diamond, MDA Compact IV Themes and Apps] haustin:
suggestion

In your Version History for v1.9.1, you say you added:

How about changing it to look for ClockForeground == Clock Background?

My configuration has a ClockHeight=10 stripe at ClockY=40 with ClockForeground=ClockBackground=0xFF (red) and LockIndicator=0. This makes a nice, visible red stripe under the status icons when locked and I'd love to know that TPL is no longer invisibly writing times and battery levels. :-)

With your recent changes, I now have it set to CapicitanceTouchesSequence=12 and LockTouchPanelOnly=0 (along with the system's Owner Information screen set to display at power-on). Now I can touch the Home/Send area then press the center button to unlock and dismiss the Owner Information screen simultaneously. Beautiful. If you implement my HEX suggestion, I'd set the sequence to "52" and, while still requiring an initial touch of something other than the button, I'd be able to do it left-handed as well!

I'm starting to smell another cup of coffee brewing in the city for your wife. :-)

Thanks! -hea

P.S. I use a bluetooth headset most of the time but not always. If other folks would like to try my working config (functionality described above), here it is -- other than default settings:

CapacitiveTouchToggleTime=2500, CapacitiveTouchesSequence=12, ClockBackground=255, ClockClickable=0, ClockForeground=255, ClockHeight=10, ClockLockActiveTime=5000, ClockWidth=640, ClockX=0, ClockY=40, LockIndicator=0, SuspendTimeoutPowerOn=7000, UnlockOnLightSensorTime=4000.
[Touch Diamond, MDA Compact IV Themes and Apps] mspace00:
What would the possibility be of leaving the volume buttons unlocked coming out of sleep? That way I could still mute the ringer while in my pocket! :D

Very thankful,

-Space
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
Didn't think of that. I haven't confirmed, but yes, if it locks the phone when a call comes in, it shouldn't lock the volume. Definitely would want to be able to mute the incoming call by tapping the volume button.
[Touch Diamond, MDA Compact IV Themes and Apps] mrbelvedere:
I had these same problems with 1.9, so much so that I had to uninstall it yesterday because my phone would not wake up @ all, not with the stylus out (which I think I disabled anyway), not by pressing the power button, not by sliding the keyboard, nothing (and this happened more that once I might add)! I really want this application to work on my TP so I will try version 1.9.2 & turn on the log feature.
[Touch Diamond, MDA Compact IV Themes and Apps] haustin:
Re: suggestion

Also, it really should unlock on keyboard open. -hea
[Touch Diamond, MDA Compact IV Themes and Apps] hellcat2007:
Working like a champ. Thanks ZuinigeRijder. One thing if i may and it is probably me being to picky but is there a way for the lock to turn back off after a call is ignored or missed. You have to unlock after missing a call. If not thats fine. I am just glad it is working now.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe I can do a combi-lock, using the built in Windows Lock, which goes to the Home/Today Screen, I believe. Maybe that also forces for a PIN too? And I can unlock the Windows Mobile lock then automatically via the sensors. Actually, I asked already a time ago the developer of CSDEVCTRL how he did it.

Of course going to the home screen is probably easier.

I will set it on the wish list.

Actually, I have already made it possible to use the TouchLockAction program to enable/disable settings, but did not yet document all those actions:

Command line usage:

\Windows\TouchLockAction.exe action

Possible actions (multiple can be specified):

* Unlock

* LockScreen

* LockSuspend

* Suspend

* PowerOff

* SoftReset

* LockBacklightOff

* EnableSuspendOnBacklightOff

* DisableSuspendOnBacklightOff

* EnableUnlockOnLightSensorTime

* DisableUnlockOnLightSensorTime

* EnableLockTouchPanelOnly

* DisableLockTouchPanelOnly

* EnableAutoLockOnPowerOn

* DisableAutoLockOnPowerOn

* BacklightOff

* Exit

I will update the documentation. And I have not implemented all disable/enable settings, so that I need to complete then.

For you, that would mean you can make 2 shortcuts available in e.g. your startmenu, to change it to the mode you like. Of course it is not fully automatic, but almost.

[/QUOTE]

Can you post a debug logfile, So i can solve the mystery why the backlight off does not work at your phone?
[Touch Diamond, MDA Compact IV Themes and Apps] astrbac:
Batt indicator WITHOUT time?

Hello,

wonderful app and great work! I just have a minor observation - why is there a small time indicator where battery should be? I have an analogue clock on my screen and would really like to have only the stock battery indicator up there (the one that comes with my ROMeOS2) without time indication....

Thanx

Alex
[Touch Diamond, MDA Compact IV Themes and Apps] Ddriver:
Hello,

I installing yesterday the v.1.9.2 and let the default value.

The last night I recharge the Akku.

This morning I see, the Diamond (orig. ROM) make a Softreset. :-(

With the v.1.8 was never a problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can then better use the Stripe option in the TouchLockAction screen, which shows a small stripe when locked. Of course you can change the width and height of the clock and the position. Another option is to use Stealth mode.

I will consider a setting to show time yes/no or battery percentage yes/no.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, nice, you did actually put the stripe at the bottom of the screen.

ClockX: 0

ClockY: 589

ClockWidth: 480

ClockHeight: 51

You can consider ClockWidth: 640, so it is also nice in landscape mode.

But that does not solve your problem.

LockIndicator: 0

That means that the stripe is only shown when it is locked.

Are you sure, the phone was locked at that time?

Although it was set to lock:

LockWhenIncoming: 1

It would help if I know the exact time when it occurs, because that makes analyzing easier....

TouchLockAction.exe

IOException

The process can not access the file '\touchlockaction.log.txt' because it is being used by another process.

The error indicates that another TouchLockAction.exe is still active (the command line version?). What command and parameters do you give to the TouchLockAction program?

I saw that I did not an explicit exit in the command line version, because I expected that falling out the main, will stop TouchLockAction. But maybe this works different in Windows Mobile. You can try to add the action Exit to the commandline as last action command.

It looks like a TLP bug. When it occurs again, can you write down the exact time of your phone, and post that debug log file, so I can analyze it better?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will add configuration option to show time yes/no and battery percentage yes/no.

For now you can use CapicitanceTouchesSequence=42 so you can do it left handed also (although double touching the middle button will also unlock).

But I will put your request of the HEX encoding on the wish list, including a separate area for area around the middle button.

My wife liked the coffee very much :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
With the current locking of the hardware buttons I cannot control that, unfortunately. However, you can mute by turning around your phone, but of course not if it is in your pocket. Controlling the volume buttons inside your pocket does also not seem to be easy? Or are you controlling it via Bluetooth?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Make sure you do NOT set EnableInputAtSuspend to 0 (unchecked), because that can cause the power on button problems for some people.

But that it did not wake at all, is very very strange.

Hope you can post a debug log file, when it occurs, so we can look into this mystery.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I asked people to help on this, twice, because I only have a Touch Diamond:

http://xdaforums.com/showpost.php?p=2902578&postcount=109

Can someone find out the registry key for the keyboard position?

I would expect it below HKCU\ControlPanel\Keybd