yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
If you do not notice the missed call, then the next call you might accidently reject, when taking out of your pocket, or you are sending bogus calls.

But you can couple a command to the CALLENDED event, to automatically unlock it:

CommandCallEnded = "\Windows\TouchLockAction.exe" Unlock Exit

But I think it is not wise.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The phone is not always reliable, earlier ROM versions often a soft reset was needed. So if TouchLockPro is the one causing the behaviour is the question :confused: But, of course, you never know.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
ok, good idea, i will.

for sure, touch screen and HW buttons didn´t react, and if i power off/on again maybe then it appears again.

yes, exactly the way i like your fab tool.

i´m sorry, i will try to be more concrete the next time, i will take some time to reproduce all the errors and write the exact time of the different errors.

let me a couple of days to give back to you my experiences with TLP.

yes, it is true i realized it after my post. my command is touchlockaction.exe -unlock and i will try touchlockaction.exe -unlock -exit to see if it works.

next time i will be more concrete, give me a couple of days and i will reproduce all the errors and write down the exact time they ocurred.

thanks again and Merry Christmas ZuinigeRijder!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe it is a bit confusing, but the - must not be there (it are not options).

So it should be:

touchlockaction.exe unlock exit
[Touch Diamond, MDA Compact IV Themes and Apps] mspace00:
Not via Bluetooth, I just usually can hit the button outside of my pocket. It doesn't require anything more than hitting either vol button (when unlocked) to mute so its pretty easy.

-Space
[Touch Diamond, MDA Compact IV Themes and Apps] haustin:
Keyboard position

Sorry, I was unaware of the ancient posts! The key is (0/1):

HKLM\System\CurrentControlSet\Keypad\IsSlideOut

Hope this helps. -hea

<EDIT>

Tell your wife to grab her coat... There's another cup of coffee in town. :-)

</EDIT>
[Touch Diamond, MDA Compact IV Themes and Apps] haustin:
Stripe at odd times

I've experienced the locking stripe appearing out of nowhere and staying until I suspend and unlock the phone. The phone isn't locked, but the LockIndicator=0 stripe is persistently there. And, it has happened at least once several minutes after unlocking the phone while actively using the device. Unfortunately, it seems random and I haven't yet caught it while I had debugging turned on. :-(

-hea
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
your are right ZuinigeRijder, i used "touchlockaction.exe unlock", not "touchlockaction.exe -unlock". bad memory i have...

i need to test my problems a bit more but for now i can assure that the crashes is because after running touchlockaction and exit tool, in fact the TLA does not exit and stays running as a hidden process, then if trying to unlock it using the command line´s shortcut associated to Gscroll action when tabbing sensitive area, then it appears the problem of the crash when trying to write to the log file locked by the running hidden in memory touchlockaction process. 100% sure. if I manually kill it then there are not more crashes. Sometimes it exits and sometimes don´t.

maybe meanwhile you could have a look to see why TLA doesn´t always exits when clicking in the exit button.

another problem i´ve found is that sometimes TLP does not inmediately locks device, i can touch screen for some seconds until TLP locks it. it has made me answer 2 calls by accident this afternoon when walking through the streets of Berlin doing the last minute christmas buyings!

but as i said, i will try to closely examine the problems with concrete times and send you the logs to see if they can help you improve this fab tool.

merry christmas for everybody!
[Touch Diamond, MDA Compact IV Themes and Apps] gobmonster:
Regarding backlight off on my phone

Sorry to go newb on you, where/how can i find the debug logfile?

And like said, the backlight on my device never cuts off anyways, it just dims to the lowest setting. I think its a htc/winmo problem.
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
Odd behaviour

There are times when the phone is off and I receive an incoming call. Of course my phone wakes and TLP is there locking the device. I currently have it configured to only lock the Touch panel, so I should be able to answer using the hardware key. BUT I CAN'T. Some how TLP is also locking the hardware answer button, so I am forced to unlock the phone using 3-touch and then the hardware key works again. Has anyone else experienced the same? :confused: It only happens occasionally but it is a real pain in the butt! :(

UPDATE: I think I may have figured out what is happening. If I accidentally tap the capacitive area before attempting to press the end hardware key, TLP thinks I'm trying to unlock the phone and interfere with the ability to use the key to end the incoming call. Give it a try, you'll see what I mean.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will see if I can find another way of locking the hardware buttons, but because I know that the BattClock does not always have input focus, it may not work. I will set this on the wish list. I expect this requires more programming effort and "Shake to Unlock" is higher on my wish list.

I can make a setting, mute after an number of seconds have been elapsed when locked, so you have the chance to hear/feel an incoming call and e.g. after 10 seconds it is automatically muted (dependent of the configuration of course). Something like "AutoMuteTimeOut=10000". Probably this is much easier to do and would do for the mean time.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
That is why tripple touch the capacitive hardware area is added, as another unlocking method......
[Touch Diamond, MDA Compact IV Themes and Apps] elladb:
can you put a function that will unlock the TP when the wired headphones connect?
[Touch Diamond, MDA Compact IV Themes and Apps] lparee:
Great project ...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not know of an API to detect this. Anyone?

But I think, in general you want to wear the TD in your pocket, while listening music, and you just want the phone locked.....
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
Hi,

i have installed the new version (v1.1) and the power button to turn the screen on and off doesnt work, also i cant answer calls with hardware keys when touchlock is enabled.

also i have found that the triple tap doesnt work, no matter where i press on the screen, even over the battclock nothing happens, although i did notice that for some reason when i press the power button fast, the battclock was registering presses, but only 2, it will count 1,2,1,2,1,2 but will never register 3.

thanks for your work.
[Touch Diamond, MDA Compact IV Themes and Apps] thingr:
great stuff! bedankt for making it happen, ZuinigeRijder :)

now where was that donate link again?
[Touch Diamond, MDA Compact IV Themes and Apps] snufkin:
Thanks ZuinigeRijder. I tried ver1.1 but found similar problem: if autolock is set for power off, I can't use capacitive area to unlock. The only method is to pull out the stylus.

anyway, thanks for your great work...
[Touch Diamond, MDA Compact IV Themes and Apps] shattering:
You can't answer calls with hardware keys because when the touchlock is enabled you have to unlock it first. When touchlock is enabled, all the hardware keys is locked. Also, if the touchlock is enabled, you can only use the power button to wake from sleep mode. You can't use it to turn the screen off if the touchlock is enabled.

You don't touch the screen, touch the sensitive part of the hardware buttons. I think ZuinigeRijder already posted which area to be touch on the 1st page. You need to touch on the same position 3 times. And the last number (number 3) won't be shown, instead the battclock will return to a black background and white foreground and the touchlock will be unlocked

Hope this helps.
[Touch Diamond, MDA Compact IV Themes and Apps] shattering:
You can actually. You just have to wait for a few seconds. When you just activated the lock, you can't immediately touch the sensitive area to unlock. From my experience, I have to wait about 2-3 seconds before I can touch the sensitive area to register the touch.

I think this is the only problem.

But still, this is a great software. Thx ZuinigeRijder.
[Touch Diamond, MDA Compact IV Themes and Apps] snufkin:
Thanks for your advice. BTW, I figured out more the problem scenario:

- activate lock (either by power off/tapping BattClock)

- leave the phone so that the screen off automatically (i've set in Settings to screen off after 30 sec)

- can't wake up the phone anymore even pressing power button unless pulling out the stylus

Any suggestion?
[Touch Diamond, MDA Compact IV Themes and Apps] shattering:
I tried the same thing as you did, and from my diamond, sometimes it turns on and sometimes it doesn't. I haven't tried this method before, since I always locked by pushing the power button on the device.

The same kind of problems (the device won't turn on) occurs when I'm using a headset only when I'm using a headset.

But I notice this only happens if I try to switch the power back on immediately after the device is lock.

Maybe you could try to wait for a few seconds before pushing the power button again. This make sense because why would you want to turn the device back on if you just turn it off...

UPDATE: It happens on random now.. And I notice it happens more when I'm listening to music from the TF3D. I don't know if this is related. Yesterday when I was still using 1.0, I never had this kind of bug.
[Touch Diamond, MDA Compact IV Themes and Apps] shattering:
Could explain, what does it mean with "go to suspend"? Do you mean the app will suspend? For more efficient battery usage?

And I think you made a miss on the "autolockonpoweroff". I think it should say "If you don't want to have it locked automatically at power off....."
[Touch Diamond, MDA Compact IV Themes and Apps] 12345:
Could you may (KINDLY PLEEAS) add 2 options " DONT LOCK HARDWARE KEY"

and "DONT LOCK HARDWARE KEY ON INCOMMING CALL"

- touching 3 times on area by frozen fingers ( european autumn) isnt nice :)

and question

why I must wait 2 s after power off to power ON ?

Pressing power twice, not make NO----OFF phone, I have to wait 2 seconds

OFF --- presing power not wake device after 2 s pressing power working OK

thanx
[Touch Diamond, MDA Compact IV Themes and Apps] triakom:
Congratulations.

Very nice program.

I have waited long time for it.

The only problem I found is with SuspendOnBacklightOff = 1, so I turned it off.

I have the following problem:

When I call somebody and the screen goes automatically off during the conversaition, the phone locks and I can't turn it back on even with the power button.The only way to end the call is to get out the stylus - very uncomfortable.

Otherwise works fine. Thank you.
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
not really, as i was requesting that the same functionality from styluslock be implemented with this lock.

firstly, why would i want to take out the stylus to answer a call? i dont i want to press the answer call button, like in styluslock, similarly i would like to hang up with the end call button.

While talking about the hardware buttons, imagine this scenario, driving, txt arrives, with the lock currently as it is nothing can be done, whereas with styluslock i could hit the power button, press the right button twice, read my txt and then hit the power button.

There is no way, at the moment with touchlock, this would be possible!!

secondly, why lock the power button? this is the only way to turn the screen on and off. for example it i want to quickly check the time while driving then turn the screen off i cant, i have to turn the screen on, look at the time, pull the stylus out, press the power button then put the stylus back in.

Quite a ball ache i think!!

and lastly, i really hate that battclock thing, i spent ages customizing the icons on my taskbar with nice graphics, then that gets pasted over the top, i think is should be removed to a separate application, if you want a lock download touchlock, if you want the battclock thing download that.

i think if you look at the posts previous to this one, the general feeling is that hardware buttons should not be locked!!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange. I know that it is not possible to switch on with the Power button for about 20 seconds, when powered off. I do not experience this problem till now. Anyway, you can always turn the screen on, via taking out the stylus.

I will do some extensive testing, if I can reproduce.

I will also double-check my code.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It will ask for a WM_POWER_SUSPEND, resulting in the fact that the screen goes completely off and the phone is in suspend state. Just as if you pressed the Power Off button. Most of the running applications will free resources and use less battery (e.g. GPS is switched off).

The second one is indeed wrong. I will correct the description.

Thanks for pointing out.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think this has to do with the 20-second problem of the power off. See my previous post.
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
I know this is completely off topic, but where is your donate button?

i said i was going to, but i cant seem to find how!!

thanks for your work, and look forward to future updates
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I agree that people want to choose between using the hardware buttons or not. Till now, with the capacitive touches, it appears the StylusLock approach does not work any longer. So now giving that option, would mean 'sense of protection of accidently presses' which will not be there. So, I need a solution which will work, before I can introduce it.

So I will search for a (alternate) solution. But this is not an easy problem....

SensorLock also has abandoned this approach. I will look into the other solutions, how they did it now.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Excellent, thanks for figuring out.

I will add this in the next version of TouchLockPro ;)

It will we alsmost the same code as the Stylus detecting, only the registry key is different. So from programming effort this is not so much effort.

I put is on the TODO/wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe I have a clue what can be the cause, but it is of course just a guess.

Currently I have 2 windows/BattCLocks.

I switch between them, when unlocked/locked.

However, with the stripe setting, only the locked clock is shown.

I do no longer paint the locked clock, when it is destroyed (from TouchLockPro perspective).

I will check my source code if this can be the case, so I can fix this in a next release.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, if you double click the BattClock, it will start TouchLockAction twice. I will see if I can detect in TouchLockAction itself, that another instance of TouchLockAction.exe is already running.

I do already an Application.Exit, but this was not the case when via a commandline, only in case of Exit action provided.

I disable the input on the main thread, because I did experience problems when doing it immediately in the power on thread. I did get sometimes the message that it wanted to power off the device. Of course, if another program is blocking the windows thread (bad program), the lock will be done only after TouchLockPro gets chance to do something in the Main thread.

But maybe the cause is that I set that is has already power on, before disabling input, so also TouchLockPro is doing maybe already stuff in the windows loop.

I will also try again, to disable input immediately in the power on thread, if this still is a problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, just to be clear, the setting "SuspendOnBackLightOff" only suspends when the phone is locked by TouchLockPro.

The backlight off setting is working at the Touch Diamond.

You can enable logdebug and logdebugdetailed in the settings screen of TouchLockAction. The logging is written in the root directory of your phone: \\styluslockpro.log.txt

LogDebug = 0

Default there will be no debug logging written. When changing the setting to 1, it will write debug logging in the root of your phone: \\styluslockpro.log.txt

This is handy for reporting problems. Please report the problem description and at which time it occurred and upload the log file. Note that the size of this file can grow big, so normally do not enable this setting or only for a relative short time.

LogDebugDetailed = 0

See above. Even more detailed debug logging is written. Note that the size of this file can grow big, so normally do not enable this setting or only for a relative short time.

Hope we can find the cause of your problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, I would not expect they interfere. But maybe it is because the BattClock gets the input focus, so the hardware keys are no longer received by the other program.

You could try to disable the capacitive touches, to see if that solves the problem:

CapacitiveToggleTime = 0.

But of course, then you must unlock by another means.

Maybe you can couple a command to another hardware key:

"\Windows\TouchLockAction.exe" unlock exit

I will also check your setting, if I can reproduce and if I can do something about it.
[Touch Diamond, MDA Compact IV Themes and Apps] haustin:
TLA command line

Would it be possible to add an "exec" command to the TouchLockAction command line? It would be handy for assigning multiple programs to the same hardware key. For example,

short_PTT.lnk -> "\Windows\TouchLockAction.exe" unlock exec "\Windows\rotatescreen.exe" exit

In this example, not only would a short-press of my HTC Fuze's PTT button switch between landscape and portrait, it would make sure that the phone was unlocked as well!

Just a thought. -hea

P.S. Creating a shortcut called \Windows\short_PTT.lnk is how you assign programs to the Push-To-Talk button. long_PTT.lnk maps a program for a long press (hold) of the PTT button.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did not know about those short_PTT.lnk and long_PTT.lnk. Is this only working on the Fuze, or is this working on any TD and TouchPro?

The problem with the exec, you have to specify the end command too and if the directory in the commandline contains spaces, we should somehow delimit those. But I will set this feature too to the wish list, because it makes TouchLockAction much more versatile/extensible.
[Touch Diamond, MDA Compact IV Themes and Apps] haustin:
Re: TLA command line

I don't know which phones other than the Fuze (AT&T version of Touch Pro) have a Push-To-Talk (PTT) button. I would presume that the same mechanism would work for other HTC phones that do have a PTT. More detailed instructions can be found at http://www.fuzemobility.com/?p=598.

I'm glad it's on the wishlist! I would recommend nested quotes ("such as 'this' for example"). The other old standby that's trivial to implement is doubling up quotes to escape them ("like ""this"" for example"). Either mechanism requires character-by-character lexical analysis, but I think the former method is far more readable than the latter.

-hea
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Wish/TODO list

I just posted the current Wish/TODO list on my site. Hope I did not oversee things.
[Touch Diamond, MDA Compact IV Themes and Apps] texasez:
is there not an option anymore for number of touches to unlock in version 1.9.2?

Larry
[Touch Diamond, MDA Compact IV Themes and Apps] haustin:
It's built in to the CapacitiveTouchesSequence: 444 is three touches anywhere, 44 is two touches.

Hope this helps. -hea
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, but it is part of CapacitiveTouchesSequence. If you want 2 touches, this can be configured too, even 1 touch is possible. Default it is:

CapacitiveTouchesSequence = 444

Defines the capacitive touches sequence to unlock using area 1 (left area), 2 (middle center button), 3 (right area) or 4 (any area). You can also define your own secret sequence for unlocking, e.g. 1321. The touches sequence can be up to 8 touches. If you want to use this as a Security pin, make sure you disable the other locking features (UseStylus, UnlockOnACPower, UnlockOnLightSensor) and of course configure a Windows Mobile password. Note that capacitive touches do not work on a Touch HD.
[Touch Diamond, MDA Compact IV Themes and Apps] lynxy:
Nice program, but:

For me UnlockWhenConnected=0 doesn't work

When I have an incoming call the screen is on, but all buttons and touch screen are blocked.

How can I do like it was in 1.8 version, I had call - screen locked, buttons unlocked, so I could answer the call without unlocking the device.

I have ATT Fuze with NATF 3.2 ROM

Thanks

P.S. Reinstalled program - have black rectangle without clock or battery available. Tried to change color - doesn't work
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think you have the same problem as reported in post 785.

You can disable the capacitive touches, as described in that post, see if that helps.

You can also disable TAPI: UseTAPI = 0.

Then it will not unlock......
[Touch Diamond, MDA Compact IV Themes and Apps] lynxy:
I tried CapacitiveToggleTime = 0 - still buttons and screen are locked.

I found a kind of solution:

LockTouchPanelOnly = 1

Now I have buttons unlocked all the time.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, but the problem you have is a bug, so I will investigate the original problem further.
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
You may want to consider making the backlight level configurable. Some people may not want the backlight totally off. Instead they may want the lowest level or a notch or two brighter. ;)
[Touch Diamond, MDA Compact IV Themes and Apps] lynxy:
Thank you for support, awaiting for new version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did try to reproduce, and now I am a bit confused, because in your post, you said: UnlockWhenConnected=0

When there is an incoming call, the power will go on and the phone will be locked. This is the same behaviour as version 1.8.

Normally, you should set UnlockWhenConnected=1, this will enable the input, so you can press the hardware keys. In combination with ScreenOffWhenConnected=1, you cannot press accidental the TouchPanel and you can still end a call.

So actually, I think this is not a bug, or I did not understand well enough or I could not reproduce.

This is a small bug. You must indeed restart TouchLockPro (or softreset) to make the changed colors effective. I will solve this in a next version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did try to reproduce, but I could not.

I also checked my source code and this does not gave me a clue.

Do you still have this problem once in a while?
[Touch Diamond, MDA Compact IV Themes and Apps] hhspiny:
I think I also have this problem. when there is incoming phone call, I can't use the capacitive touch to unlock the phone!!. the entire phone just locks up. I can still use the stylus to unlock it.

it seems to me that when there is incoming phone ring, the phone is busy and TLP does not have enough cpu left to interpet the capacitive touch and stays there. very often, I can't unlock it anymore after the incoming call even after the incoming call has ended.