yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
More people report this problem. I do not have a clue why this is, it seems related to the HTC locking API I use. The only thing you can help with, is enabling "logdebug = 1" and "logdebugdetailed = 1" (see post #3) and post the logfile with the eact time it did not react (and for how long). Maybe I can find similarities for the people who have this problem. But I think it maybe well an external setting which has the effect mentioned.

The capacitive touch can only be read out, when the BattClock has focus. That is why I recreate the BattClock once per 8 seconds. Dependent of the application running, it can try to be the top-window. Maybe you must lower the value of 8 seconds to something like 4 seconds, so the locked BattClock is created more often.

Another reason can be that backlight is off and in version 1.5 I destroyed the locked BattClock. In version 1.6 I do this no longer. Maybe that also helps.

Yes, this is something which is not so handy with TouchLockPro. So probably I have to do soemthing special when there is a phone answered and in progress. As long as that is the case, it should not lock. I will think about this one, because this is a bit cumbersome.

For now, the best you can do is take out the stylus.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockAction, see post #4

Probably you have seen this already:

Version 1.6 is out with the TouchLockAction screen. See post #4 for more details

So now we need a discussion what can be added in subsequent version of TouchLockAction. At least a Configuration screen is something which makes configuration easier.

We should also discuss how far we are going in adding things, because a lot of functionality is also available via other programs, e.g. Communication Manager. And of course we have the programs folder, with all tools. So why do we need another mechanism.

So should we just focus on the lock functionality :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] DomSim:
trying 1.6 now after deleting all registry keys and uninstalling 1.5 to start fresh. hopefully will avoid the locking on power off. on a side note, have you thought about apptodate support?
[Touch Diamond, MDA Compact IV Themes and Apps] DomSim:
well still locks on power OFF instead of power ON but i think i figured out what is causing it but do not have a solution. if i suspend the device by pushing the power button it works correctly and lock on wake up. but i typically do not suspend the device in this manner. i use gyrator to to suspend my device anytime it is in reverse portrait with the stylus in so when i put it in my pocket it suspends on it own. when it suspends in this manner it causes issues with touchlockpro. there are two ways that gyrator can invoke suspend. directly and by simulating a keypress. i have tried both methods and both have the same reaction :( any ideas what can be causing this conflict or a way to fix? ive attached my debug info which i turned on touchlockpro, rotated the device upside down, gyrator suspends device, immediately after touchlockpro activates and i then pulled the stylus to wake up and turned of touchlockpro so the log is short and only contains one locking event. hope you can help because if it wasnt for this, your program would be perfect for me.
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
I totally agree, here is what i think:

1: I dont like the fact that the exe for the action screen is in the Windows dir, it should be in its own dir in program files, also useful if point 3 is possible

2: Buttons: i think the top row is fine, but on the bottom row i dont see the point in the suspend button.

surely this is achieved by pressing the middle button on the top row? or by pressing the power button (which is actually alot faster than loading the action screen then suspending)?

i think the suspend button should be lost and replaced with the configuration screen button. (just my opinion, as i know now i would never use that button, if i knew i was going to suspend my device, i would finish doing what i was doing, replace the stylus (enabling the lock) at the same time as hitting power button - jus habit not i guess!!)

a suggestion about the config screen, you said that you were going to remove the need for reg keys so the program could be changed on-the-fly. would doing this add any extra functionality? or would it just be more work for you?

we all know that applying the changes in the current method works, so why not have the config screen just apply the reg changes and offer a soft reset? or since the lock is disabled when the action screen is showing the config screen could unload/disengage fully touchlock, apply the reg changes and then restart the app? (or is my suggestion harder to do than your idea?:confused: ignore it if it is a bad one :D)

now as for the icons, they pretty bad :p, ill try and have a set for you tommorrow (possably later tonight) what size did they have to be? and you do want them as *.ico.

EDIT: i found the size 64x64 and in ico or png

3: a question about the png's, if they are in png format, im guessing they could be totally customisable if they were read from a directory? what i am thinking is if the exe from the actionscreen is in:

program files\touchlockaction

then the png could just go in the same dir and get read from there. so if they followed a number fashion mentioned earlier (1a 1b 1c 2a 2b 2c) we could do what we wanted with the icons?

if you could pm me your email so i can send them to you when i have them.

MG
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
I have icons for you.

and a report of the actionscreen not working:

1a: not work

1b: not work

1c: work

2a: work - but when i suspend, the device doesnt lock

2b: work

2c: work
[Touch Diamond, MDA Compact IV Themes and Apps] aadadams:
I use the vista hide battery meter that runs across the top of the screen. It is three pixels tall and 480 pixels wide. It would be great if i could make the BattClock shift down to the fourth row of pixels. I read of moving things from left to right but I don't think I saw an answer to this. Any help would be greatly appreciated.
[Touch Diamond, MDA Compact IV Themes and Apps] superpc:
everything works fine for me, unlocking mechanism is much easier than 1.5

starting "touchlockaction" could be faster thou

and yea if it's possible, pls reskin the icon :p

thanks for the great program
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yeah, apptodate support is on the wish list, but is was not high enough on the list :D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can change the ClockY setting, this is the number of pixels measured from the top (default 0). See post #3 for details.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I also not, but starting TouchLockAction from within TouchLockPro was a problem. Especially, because the "Program Files" can be named different in other languages (in Dutch it is "Programmabestanden") and where you store it (phone memory or SD card). I will look if I can move it to another place, where TouchLockPro can still find it easily.

You are right that the power button can also be used for the SUSPEND. But the power button already has overtime, so this could be an alternative, although two touches instead of one press. Dependent on the lock settings, the SUSPEND my be the same as LOCK AND SUSPEND (AutoLockOnPowerOn), so in that case it is a duplicate function. But there are people who tweak differently....

What do others find?

Using a registry editor is cumbersome. Not a problem, when you do only need to configure it only once. But, I foresee also different needs, dependent of the function you are executing. You have a default locking method, e.g. suspend on backlight off, but now you want to temporarily to overrule that. Examples are:

- Using the photo camera

- Using GPS for walking

So you want to be able to quickly change the settings temporarily.

Providing this does not seem too difficult, I just write the registry keys from TouchLockAction and give a SettingAction to TouchLockPro to reread the registry settings. Actually I did provide this functionality already, but it was not fully finished/tested. So I kept this quiet for now.

Yeah, the icons where nicer, but I had to manually change them, because they had a transparent background. I wanted a black background, because I do not paint the background, so you still see the underlying window (although no longer updated). But I look forward to receive better icons :)

Probably I want them in the executable. But maybe I can make a overrule setting to the location/directory where the alternative icons could be read....

And you can overrule the ones you want to be replaced.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear that unlocking is better than in 1.5. This has probably to do with the backlight off, in 1.5 I destroyed the locked BattClock, so you could not unlock then.

I am open for other icons, MysticGenius is going to provide some.

TouchLockAction is written in C# and uses the .NET Framework 2.0 (so you are not forced to install .NET Framework 3.0). .NET Framework is part of Windows Mobile 6.1, so this works out-of-the-box. Apparently, starting takes some time :mad:

I now indeed start TouchLockAction each time again (and exit the program thereafter), so it uses no memory. An alternative would be to minimize TouchLockAction, because it is not so big anyway, so it is in standby mode. And it uses no CPU either then, only a tiny bit of RAM. I will experiment with this.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You do not need to deinstall TouchLockPro, you can stop it via Programs menu. Install BattClock and see what it shows in your scenario. Thereafter deinstall BattClock (and start TouchLockPro).
[Touch Diamond, MDA Compact IV Themes and Apps] JimSmith94:
Okay, BattClock acted the same as TouchLockPro. I may have something else going on with my phone, as I noticed at least once that when I unplugged my phone from the charger, it jumped up to 100% for a minute or so, then rapidly went back to what your battery status was showing. Maybe yours is right and Batti and the phone itself are wrong, although that doesn't seem logical to me.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, that is not logical.

I checked the BattClock code.

Oops, I see that BattClock code has the same approach as TouchLockPro. Sorry that I did let you try to see the difference. I was really in the understanding that BattClock did not have the notification part. So it can still be that the Microsoft notification API gives back the wrong numbers :eek:

I will see if I can use only the second approach only without asking too often for the battery driver value.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Statistics:

Join Date: 13th June 2008

Total Posts: 2000

# Posts Per Day: 3.04​
[Touch Diamond, MDA Compact IV Themes and Apps] zhongzw:
Hi ZR,

What's the different between "TLPToggle" program and "TouchLockAction.exe !LOCKSUSPEND" command?

Thanks very much!
[Touch Diamond, MDA Compact IV Themes and Apps] zsunsun:
Thanks for making free lean and mean software.

I've been using touch lock pro ever since I had Touch pro 1, and now I'm using with TP2 but I have one problem that annoys me all the time.

When I receive call TLP stays locked and does not unlock via proximity setting.

And also when I'm done with call and hang up TLP stays disabled.

Ideally I want TLP to behave consistently using proximity sensor no matter call is coming in or not.
[Touch Diamond, MDA Compact IV Themes and Apps] dAnTeDK:
Hi,

I just downloaded TLP, but I can't get it functioning proberly.

The only way I can unlock it is via the VolDown/VolUp or stylus out. I'd like to unlock it via the touch on the hardware keys. I tried choosing the HTC Diamond presettings you made, but that doesn't help. I also tried adding "Use Slider" under Keyboard.

My phone is an HTC Touch Diamond, running the newest TouchLockPro app.

Can you help?

Regards Michael
[Touch Diamond, MDA Compact IV Themes and Apps] neverland13:
I have issue with my phone - when i reboot sometimes TLP stop locking my screen. Buttons are locked, but not the screen. I have HTC 8900/ ATT Tilt. Any ideas?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TLPToggle executes the command !TOGGLELOCK

So it switches between locked and unlocked or vice versa.

This is more or less a convenience program, so you can also execute:

TouchLockAction.exe !TOGGLELOCK"
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I would not expect this. Can you enable debug logging (LogDebug=1), reproduce the scenario and post the log file TouchLockPro.log.txt. Maybe there is a setting wrong :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Default settings is touching 3 times the middle button. Or you can slide your finger over the right area up

that is what I normally do when it does not automatically unlock by the light sensor.

If this all does not help, you can enable debug logging (LogDebug=1), reproduce the scenario and post the log file \TouchLockPro.log.txt in the root of your phone memory.
[Touch Diamond, MDA Compact IV Themes and Apps] paalkr:
Hi!

I have installed TLP on my HD2 and the basic functions works perfect, but I have som trouble configuring the Proximity sensor to behave the way I'd like. Can someone give me som hints on how to achieve the following behavior.

Basic behavior (works):

Lock on power on. Unlock based on proximity, but do not suspend by proximity after unlock.

During a call (partially works):

1. Lock on incoming call, unlock by proximity or light sensor

2. Blank screen when close to ear during a call (I have not been able to get the InCall Tweak to function)

3. Turn on screen when removed from ear during a call without locking the device

4. If again put close to ear during a call, repeat 2 and 3

I have partially been able to achieve 1,2 and 3 but not 4. Basically the blank screen during call works once, but not repeatedly during a call.

Regards,

PK
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately I cannot test, because I do not have a Proximity sensor. What settings do you use now? The default settings?

These are the default settings:

CmdLock = "!PROXIMITYACCEPT"

CmdUnlockCall = "!PROXIMITYIGNORE"

CmdUnlockNoCall = "!PROXIMITYIGNORE;!PROXIMITYDISABLE"

But looking at what you want to achieve, it looks like the setting for unlock at a call is the problem:

CmdUnlockCall = "!PROXIMITYIGNORE"

Did you also have this setting? Because that means that TouchLockPro is not reacting anymore and is relying on the Phone Canvas/HD2 for Proximity sensing. Maybe this command must be empty to what you want to achieve or CmdUnlockCall ="!PROXIMITYACCEPT"

But then you want also to locksuspend at near:

CmdLock = "!PROXIMITYACCEPT;!LOCKSUSPEND"

Unfortunately there is no different command for locking when in a call or not in a call, so the last setting will probably interfere what you want when not in a call....

Maybe you can post a debug log file of scenario 4 and post the log file TouchLockPro.log.txt as zipped attachment. Maybe that gives me insight. And of course I like to hear other HD2 users how they use the (non-default) Proximity sensor.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
That is exactly the same issue i mentioned some time before.

During a call i want to have the proximity sensor controlled by my hd2 and not by TLP.

And second problem with this is:

I call someone and while my phone is still dialing and not connected yet, this is not "during call" - so i put my dialing phone to my ear and it will be locked. If i put my phone away from my ear, because dialing lasts too long - phone will not wake up and is still locked.

But i think there is no chance to tell the phone, that "dialing" should be same as "in call".
[Touch Diamond, MDA Compact IV Themes and Apps] sumflipnol:
I love using TLP on my TP2! Thanks for the great locking tool!

Now, I have an HD2. I want to use a hardware key unlock sequence.

On my TP2, I had Keyboard: [everything unchecked; UnlockKeySequence = 118,117] and I can unlock by pressing Volume Down and Volume Up.

On the HD2, if I use the same settings, I can't unlock using a key sequence.:(

Can you please tell me how to use an UnlockKeySequence with the HD2?
[Touch Diamond, MDA Compact IV Themes and Apps] ephestione:
Req: proximity ultralite version of the program

I am a happy user of your battlock utility, andI know it may not look very politically correct to ask this, anyway:

there's a little utility by exidler here on xda that just locks the screen with proximity sensor, no fancy stuff, only checks that single parameter, with a handful of registry settings to modify its behaviour. Alas it's not being developed anymore and has a couple of flaws that make it useless for certain uses, so I was hoping that, maybe, without any major work on your part, you could create a "rip" of touchlockpro that does only one thing, that is when the device is locked, and inside the pocket (proximity sensor always triggered) if by chance the keys get pressed and the screen is turned on, the utility would check the proximity status and put the device immediately to standby.

The utility would be extremely light and small, since it would only check proximity sensor, and only when device is locked, to turn the screen back off in case of accidental keypresses, and it would have the only purpose of saving battery life when inside the pocket. The advantage is obvious, it would have a resources imprint on the device that, if compared to the full fledged touchlockpro, would be unexistant.

Is it possible with a minimal effort? If not, please disregard my request :D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Indeed I cannot detect that then. Maybe it could be by detecting the window and have exceptions when the window is in front :confused: But then the phone window needs to be configured (because it can be different on different phones).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can enable debug logging, press the keys when the phone is locked and look into the logging which keys are hooked. You can post the debug log if you want to have myself a look.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, the approach of Exidler is already in TouchLockPro. And TouchLockPro is already small (34 kb in memory) and it does not use much resources/CPU, just like BattClock. It is event driven, only some sensors need polling. You can disable all the sensors you do not want to use and just enable the proximity sensor and configure it to your needs.

I do not have a HD2, so I cannot really test the Proximity sensor. I expect that the current TouchLockPro has also its problems. I am willing to spent time on it, to make it more perfect, but I need a lot of help and feedback of users then. And just by looking at the log files and good description try to make improvements.

So I think it is not worth the effort to make a stripped down version of TouchLockPro, because it only would save a little memory for an already small program. Of course, a convenience setting for easier configuring is an option. But first we must make sure TouchLockPro can fulfill the Proximity sensor needs you are asking for.

What do you mean with the Device is locked? You mean the Windows Mobile lock? Because TouchLockPro uses its own locking/unlocking mechanism, independent of the builtin Windows Mobile lock. But it is as untrusive as possible, not having a foreground window like other locking solutions.
[Touch Diamond, MDA Compact IV Themes and Apps] ephestione:
Thank you for your reply :)

And the answer was quite reassuring!

What I meant is that what I would need your application for is very simple: I need it to check for the proximity sensor status only when the device is already locked, and not while I'm using it.

This way, it will only "do stuff" when I have the phone, say, in my pocket, and if the screen gets turned on by an accidental press on the hardware buttons

EDIT: BTW I remember having already tested touchlockpro to see if I could use in the way I needed, but there was no way to set the proximity lock to be active only when the device was locked... that's the one and only feature that I need, and that exidler's utility has (evne if that generated a bug which makes it unuseable)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think this is what TouchLockPro can already do. Currently it locks itself by default at power off/on. But it looks like you want a little bit different behaviour. You want the control of locking (not at power off/screen off/screen on). The Proximity sensor is already used by default for unlocking. And when something is near (in your pocket) it will suspend. So that should work already.

So you only need a way to lock the device on your wish. There is already a convenience utility TLPToggle, which toggles between locked/unlocked. Just make a shortcut to this tool and you are in control of locking. Of course you must disable the default TouchLockPro lock behaviour:

AutoLockOnPowerOn = 0

There is one tricky part, though. HTC is using the Proximity sensor also, for screen off and screen on in their dial screen. And there is no way to keep the Proximity sensor from reacting by this program. The only thing you can do is then to disable the Proximity sensor when unlocked. Fortunately, this can already be done via TouchLockPro too, via !PROXIMITYDISABLE.

But then you must make sure, that when you lock the device at your wish, you also enable the Proximity sensor. So you can make a shortcut to the command:

TouchLockAction !LOCKSUSPEND;!PROXIMITYENABLE

Thinking about it, you must have time to put it in your pocket, otherwise it unlocks too fast, or hold your finger before the Proximity sensor when putting in your pocket. Hmmm, probably you need to experiment a bit. And maybe extra Proximity commands are needed to fullfil your needs. I will think about it.