yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I am currently adding a lot of wishes to TouchLockPro, I will see if I can add this one too in the next major release. Anyway, I put it on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] daigut:
Thanks for this convenient piece of software, which makes my life with my touch pro2 much better!

1 suggestion, would be great if the phone unlock when I plug my headphone cable into the phone, so that I can use the hardware buttons on the remote control headphone cable to control the music player!

Thanks!!!
[Touch Diamond, MDA Compact IV Themes and Apps] ROB_LAMOREAUX:
I can understand wish lists and how they can grow to be unmanageable. Thanks for adding this to the list.

Rob
[Touch Diamond, MDA Compact IV Themes and Apps] hgrimberg:
Feedback

I tried the new 2.7.1 version on my Diamond and when I set the option from WM of "Lock all keys except the power key", it only locks the keys from the right side; the ones on the left (Home and Call) stay unlocked (when Touch Lock pro is active) I have my settings to always keep alive keys and to leave 134, the center button, always unlocked.

Actually the first time you lock and suspend the phone, all keys are locked, but the second time you do it, it only locks the right side keys.

The other thing I see, is that when using the Home screen of the program. when you click on Lock or Suspend, it just does nothing, it just makes the Home screen disapear.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think I saw this registry key, while investigating the bluetooth registry key.

Would you always want the phone unlocked, when the headphone is connected :confused: Because I can expect you want it locked, so you can listen to the music without pressing keys/TouchPanel......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is very strange, because normally only the Home and Back button are unlocked. You did not switch hardware keys via a program?

Maybe you also have problems with DoubleTouchPanelLock = 1 setting, you can try to set it to 0, because it does not suspend.
[Touch Diamond, MDA Compact IV Themes and Apps] daigut:
sorry I didn't explained clearly, my headphone was with a Wired Remote (official accessory from HTC RC-E100) with several buttons (play/pause, vol up/down, next/pre, etc.), not a bluetooth one; since I set to lock all hardware buttons, when I connected the Wired headphone to my TP2, those on the Wired Remote also locked, so I could not use those buttons, I was thinking if there was an option to unlock buttons when the Wired Remote was plugged, it would be very convenient for me. Thanks for your reply!!!
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
You can specify only certain buttons (or keys) to be unlocked at all times. The only problem is you have to know the numerical code that corresponds to those buttons. You could use trial and error to find these out, but that may take a while, and I know I remember seeing program somewhere that would display the numerical codes associated with any button you press, but I don't remember what it's called.

That could be a good addition to the TLP keyboard settings page, there could be a Test[\] button that would wait for you to press a button, and then it could tell you the numerical code.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did understand you did not have a bluetooth but a wired headset. You could try to use HTCLockAPI = 1, maybe that will not catch the buttons on your wired headset, because with bluetooth these are also not catched. But I cannot test myself.

Another option would be only lock the touchpanel, when you use the wired headset. Unfortunately I do not detect the headset, so you have to manually switch or use the TouchLockAction commands EnableLockTouchPanelOnly and DisableLockTouchPanelOnly.

More convenient would be a setting, where TLP can do this automatically, when a headset is detected. I will put this on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
That could be a nice enhancement for the settings screen. I mentioned the codes on the website and the links to the Microsoft page. You can also enable debug logging, enable the hardware key lock, press the keys and lookup the sequences in the logging for the time being.

I will add this enhancement to the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] Sky Forever:
Device change)))) HTC MAX 4G ---> TouchPro2)))) Works perfectly!))))

Only one wish)))) Date in taskbar "dd-mm" ---> "dd.mm"))))) How can I change it? )))))
[Touch Diamond, MDA Compact IV Themes and Apps] Asphyx:
I am having some issues with this working on my TP (Caulkin Kit 21052 with TF3D2.0)

I'm sure it just something I'm doing so I will read the thread to try and work out my issues.

Seems the phone must suspend at least once before the capnavs work...

But What I am posting about is I would rather configure the commands instead configuring the keys.

IE:

I want to be able to select the lock function, make a gesture on the Nav buttons and have TL set the right gesture for that function....

Almost like a learning remote.

Ok back to finding out why I have issues....
[Touch Diamond, MDA Compact IV Themes and Apps] Goondu:
Sorry for the late reply. been busy

2.7.1 works only if I disable the `Double Touchpabel Lock'

If that's on, no locking will occurs.

I think someone reported it earlier.
[Touch Diamond, MDA Compact IV Themes and Apps] capo56:
Hi, I have Diamond2 and have the only one reason for looking for locking app. I want to turn off my device when using GPS for tracking routes (Ozi Explorer) = turn off display and lock hw buttons.

As we know, wm has its oem locker, which can turn off our device after some time period. This unfortunetaly turns off allso gps module :(

I looking for some app, that can do "turn off my device without turning odd gps" by one of the following:

* g-sensor (touchlockpro unfortunetaly does not support this sensor in Diamond 2)

* nav sensor (touchlockpro does not support this "zooming" sensor in Diamond 2)

* 2 hw buttons combination (touchlockpro does not offer this functionality)

* power button (instead wm "complete" turning off)

Can be touchlockpro modified, or do you know about any other solutions of my problem? I dont want to use stylus sensor....

Thanks a lot
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Great.

Currently the formats are hardcoded and cannot be changed.

I will put on the wish list that you can specify the format of the date and time.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, there was already the idea of the record mode, I already have buttons for it (before the commands). But I did not implement them yet. So you need to translate your gestures into orientation changes for the time being. Note that you see the actual orientation, while doing your moves in the GSENSOR settings screen......

I will put the record mode on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, for some people the DoubleLock is needed, because it does not always lock in the other way and for some people the DoubleLock is a problem. So it is difficult to choose a decent default value :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I also use OziExplorer.

There is a possibility in TouchLockPro to keep the phone alive:

!KEEPALIVEON

With the NAVSENSOR already the following commands are of interest:

- !BACKLIGHTOFF (sensors keep working (e.g. for !BACKLIGHTON swipe), phone will be kept alive, great for in combination with e.g. GPS)

- !SCREENOFF (sensors will not keep working, GPS keeps working, phone will be kept alive, great for in combination with e.g. GPS)

You can make a shortcut to TouchLockAction <command> to one of these commands.

I am going to investigate if I can also support the GSENSOR of Diamond2. The Zoombar is somehow more difficult, as long as no API source code is put somewhere on xda developers.

I also saw some registry tweaks on xda developers, you can keep the power on for the GPS. I did not try this myself though.

Because GPS costs battery, I have configured OziExplorer not to keep the phone alive, and just now and then power the phone on. It needs to find the GPS signal then, but that takes not too much time normally.

Hope this information helps a bit.
[Touch Diamond, MDA Compact IV Themes and Apps] Goondu:
Ok

I have a question. Now I can't use the HTC `Slide to answer' function when lock.

I tried every combination, including activating `Lock when incoming' and `keys only'.

Please help

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you set HTCLockAPI = 1?

Because with that one set, you cannot lock only the keys.....
[Touch Diamond, MDA Compact IV Themes and Apps] ugumba:
I have the same problem (Blackstone) on 2.7.1.

HTCLockAPI = 0

AutoLockOnPowerOn=1

UseTAPI=1

CommandCallIncoming=!UNLOCK

DoubleTouchPanelLock=0

When the screen is off and I receive an incoming call, screen turns on, but TLP remains locked. I can unlock manually (stylus or key) and proceed normally. (See attached log)

If the screen is on, TLP is locked, and I receive an incoming call, TLP *does* unlock, and I can use the slider fine.

I tried resetting the settings, same result.

I have now tried installing each of the 2.6.x versions. 2.6.1 to 2.6.6 all work fine in the above scenario, i.e. they properly unlock on incoming call when screen is switched off. Upon installing 2.6.7 or 2.7.1, it stops working.

Hopefully, the attached log (from 2.7.1) provides some clues...
[Touch Diamond, MDA Compact IV Themes and Apps] PseudoReal:
topaz / touch diamond2

hi, I am using TLP in the latest version and do have one issue:

the phone unlocks perfectly with the lighr sensor, but when it is dark, I cannot unlock it. I have set the phone to unlock when doing "portait, landscape, portrait" but nothing happens, I do not evwn see a "G" in rhe upper corner. is there any unlocking possibility by 3 times touching rhe panel?

thx
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
Is there a way to use touchlock pro to just disable the touchpad on an incoming call?

I want the phone to never lock unless a call comes in, when the call comes in, I just want the touchpad locked, when the call is answered, I want everything unlocked.

I have use Tapi, and lock when incoming checked. I have autolock power on unchecked.

The phone now does not lock after I turn it on, but it also doesn't lock when there's an incoming call.

Is there a way to get what I'm looking for?

EDIT: Nevermind, after a soft-reset, it appears to be working.

I did add !LOCKSCREEN, !UNLOCK, !UNLOCK in the 3 boxes at the bottom of the tapi screen, is that necessary? The last one is good, though, in cases where I reject the call, it still unlocks.
[Touch Diamond, MDA Compact IV Themes and Apps] Goondu:
No, I left HTCLockAPI as uncheck.

When a call comes in and my phone is still locked, I can't use the slider function

Only when the phone is unlock, then the slider function is useable

This happens on + off.

Sometime it works well. Soemtimes not.

I have attached the log files. Hopefully it is useful to you. Look at the last few entries around 2300hrs

Can I delete away the toucklockpro.log file from my device? Do I have to replace it with an empty toucklockpro.log file?

BTW, I have gone back to 2.67. It the best version for me. As mention earlier using 2.7, the phone doesn't lock/work when doublelockpanel is set to 1.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the thorough investigation and the clear description. This helps me a lot in finding the cause.

I looked at the log file and I see that it first locks (due to power on), then it is interrupted by the incoming call, which unlocks, and then it continues with the power on, locking it again. The last one was a fix for the opposite, when people did not want to lock on power on, but wanted to lock at incoming call :eek:

So it is a bug, because in both situation it should do as requested :cool: I will see if I can fix this scenario.

However, why do you not configure KeysOnly (LockWhenIncomingKeyOnly = 1)? Because that will lock the hardware keys and not the TouchPanel, so you can answer via the slide2answer. In your scenario, you can still accidently press the answer/reject button, missing calls:confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It looks like the GSensor is not working on the Diamond2. Apparently HTC has added some things SENSORSDK4, and my code is no longer compatible, like other programs like SensorLock.

Can you help me :confused:

Can you try to run the GSensorTest program as attachment, to see if that works on your phone? Unzip the attachment, copy the files to a folder on your phone and run GSensorTest.exe.

But why do you not configure a key unlock sequence, like Volume Down/Volume Up, so you can just unlock the phone via this key sequence, in the cases it does not unlock by the light sensor :confused: Or take out the Stylus?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, so you did set:

CommandCallIncoming = !LOCKSCREEN

CommandCallConnected = !UNLOCK

CommandCallEnded = !UNLOCK

The first one is not necessary, when you set: LockWhenIncoming = 1 and LockTouchPanelOnly = 1 in the Other Settings screen.

The second is not necessary, because it is the same as the default UnlockWhenConnected = 1

The third one does not seem smart, because it will also unlock when the call is not answered. Is this what you want? The second one does unlock when connected.

You are aware of the fact that you can still press the answer/reject keys, when in your pocket? And the phone is not locked when it powers on in your pocket? Note that since version 2.6 it is possible to unlock the phone via a key sequence (e.g. one middle button press on Touch Diamond), if it does not unlock automatically by the light sensor. And that now also the power button is unlocked, so you can quickly check the time or something and just power off again via the power button, without unlocking?
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
I stopped using it prior to 2.6, so those sound like nice additions. The unlock by pushing the middle button is handy.

You have a lot of different options, so you might have people (me) using it in ways in which you didn't expect.

Yes, I want it to work exactly as it is now. I've been running without any lock for sometime now and I'm fine with that.

The problem I'm having as well as others (which you are aware of since you participated in the other thread here about it http://xdaforums.com/showthread.php?t=414731&page=13) is that it's very easy to answer or reject the call while it's in your pocket, if the touchscreen is touched on accident. All I want is to be able to take it safely out of my pocket, look at the display and decide if I want to answer or reject the call.

Locking the touchscreen only on incoming and unlocking once it's connected or rejected (that's the need for that 3rd option) is the perfect solution for that.

Still having access to hardware keys is necessary or I couldn't answer/reject/mute the call, but it's not easy to hit those keys on accident while removing the phone from my pocket.

So far, this seems like it'll work perfectly for me.
[Touch Diamond, MDA Compact IV Themes and Apps] ugumba:
Thanks for the reply - looking forward to the fix! :)

Locking the keys isn't that crucial to me, since they are remapped with AE Button Plus:

Green tap: Open Start menu

Red tap: Open AEBPlus task manager

Green double tap: Green key

Red double tap: Red key

But you have a good point, and I'll try running with your suggestion for a while.
[Touch Diamond, MDA Compact IV Themes and Apps] PseudoReal:
it seems like the g sensor does work while in the config mode as it correctly recognizes the status. i currently cannot test as i am on vacation.

what i also discovered: when opera is in foreground, unlocking via g sensor works. it seems like the g sensor is disabled when turning on the device and only enabled if an application supporting the g sensor is in foreground.
[Touch Diamond, MDA Compact IV Themes and Apps] honekr:
Not unlock when calling

I have problem - when somebody calls me, touchlockpro doesn't unlock my TP2. I was setting action !UNLOCK for INCOMING but it doesn't work :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is the same problem as described in post #2547.

Do you have a slide2answer solution? Then you can configure KeysOnly (LockWhenIncomingKeyOnly = 1)? Because that will lock the hardware keys and not the TouchPanel, so you can answer via the slide2answer. In your scenario, you can still accidently press the answer/reject button, missing calls
[Touch Diamond, MDA Compact IV Themes and Apps] Goondu:
Hi

Any comments on my query?

Thanks mate
[Touch Diamond, MDA Compact IV Themes and Apps] honekr:
Thank you for you answer. Yes, I have slide2answer on my Rhodium. When I'm setting LockWhenIncomingKeyOnly = 1, I can answer via slide2answer. It's OK but I want to use anwer and reject button - example for reject call :)

Sorry for my bad english :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did have a quick look in the log file, but I need more time to investigate. So that will be probably tomorrow.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, it is a bug, so I need to think how to solve this one, without introducing new problems. Note that you can set LockWhenIncomingKeyOnly = 1 and set UnlockedKeys = 114,115, so the answer and reject keys are unlocked for the time being ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see in the log file that you used version 2.6.7. Does version 2.7.1 not work correctly with DoubleTouchPanelLock = 0? Is the same problem in version 2.7.1 with the above setting?

I did have a good look to your log file. And unfortunately I cannot see from the logfile why the TouchPanel is sometimes still locked. The logging looks ok.

You can just delete the TouchLockPro log file, because it takes away some of the phone memory. It is possible you cannot remove, because it is in use by TouchLockPro. Then you can just stop TouchLockPro, via the Programs menu, remove the log file and start it again.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have just uploaded version 2.7.2, which should fix the !UNLOCK command at incoming call.
[Touch Diamond, MDA Compact IV Themes and Apps] Presto80:
hi

jus installed 2.7.2,,

im overwhelmed by the number of action in nav sensor

may i know wats keepaliveon..keepaliveoff..locksuspend etc..

thanx.

wat i wan is there anyway to dun let the hp go to suspend mode..so tat my screen is always off and nt in lock mode..

previously im using 2.4 n sometimes the hp will lock in my gps prog despite the screen nt off..
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Probably this page is of interest. and this post.

!BACKLIGHTOFF (sensors keep working (e.g. for !BACKLIGHTON swipe), phone will be kept alive, great for in combination with e.g. GPS)

!SCREENOFF (sensors will not keep working, GPS keeps working, phone will be kept alive, great for in combination with e.g. GPS)

In combination with a GPS program I use the navsensor swipe to lock the screen (!LOCKSCREEN) and then I do a !BACKLIGHTOFF or !SCREENOFF. Note that both under the hood do the !KEEPALIVEON, so the phone does not go into a deep sleep.

Note that KEEPALIVE is reset, when it is unlocked or another TLP command is executed, to prevent from battery drain. Because the phone will use more battery, when prohibiting a deep sleep.....
[Touch Diamond, MDA Compact IV Themes and Apps] Presto80:
abit confused by ur explaination of backlightoff and screenoff..

wat u mean by sensor? it seems doing the same thing for both except the sensor on off which i dun understand..

when the hp is undergoing keepalive...is there any indicator.?

.keep alive means screen will stil go off?

sorry prev post i meant i dont want the screen to go off and lock..whike using the gps prog as i need to clcik on the screen occasionly while im running.
[Touch Diamond, MDA Compact IV Themes and Apps] honekr:
Version 2.7.2 is OK, thank you.

What can I use for unlock my Rhodium when I'm setting HTCLockApi=1 ? Only stylus, slider, light sensor and g-sensor? Can't I use any keys?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
With the screen off, the light sensor and navsensor are no longer working. I do not know for sure for the GSensor.

For your purpose, probably the best is to use !LOCKSCREEN followed by a !BACKLIGHTOFF, because then you can just press a key for getting backlight on again. You still cannot accidently touch the screen and hardware keys, although the backlight will go on when the hardware keys are pressed.

Keepalive does not have an indicator. I think the screen will not go off with !BACKLIGHTOFF (only the backlight) but you can try yourself ;)
[Touch Diamond, MDA Compact IV Themes and Apps] rickd26:
TouchLockAction Load Time

Thanks for TLP...it's a really great program and I love it.:)

I have a comment/suggestion and I'm not sure if this has been covered anywhere...:confused:

To lock my TouchHD, I usually prefer to use the TouchLockAction UI most of the time. However, it takes time to launch this utility (e.g. by pressing BattClock). Is there a way to shorten the load time of TouchLockAction? Or better yet, keep it alive in the background so that it will load faster?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, with HTCLockAPI = 1, you cannot unlock by hardware keys. The only way is by the available sensors supported by your phone with that setting. Probably for your phone HTCLockAPI = 0 is more convenient.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I on purpose exit TouchLockAction, to not take memory away. That is also the big advantage of TLP over other solutions, it only consumes 38 KB. What do you use mostly from TouchLockAction??
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
Hi ZuinigeRijder,

I've got a couple of questions (or maybe reports of minor issues, if you want :) ):

- it seems that TouchLockPro does not lock the red (hangup) button on my touch HD. Is it a standard behaviour of the standard WM locker or something different? HTCLockAPI is 0...

- somehow the panel does not get locked for some applications. One example is RSSFeed, which is a part of the official HTC ROM for HD (in principle it is unbranded OEM version of NewsBreak by Iliumsoft). Even when lock is set, I'm able to go forward/back with gestures (only gestures seem to work, soft keys are locked).

If you need debug logs for investigation, pls let me know...
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Bluetooth Redial

I use a Bluetooth earpiece to make all my calls. It has a standard feature that when you double press the call button quickly it redials the last person you called.

But when my phone is locked, this feature is disabled. The press and hold to start Voice Command works fine. The press to answer/hangup works fine. The volume up and down work fine.

I am thinking that if I could determine which numerical code is being sent to the phone when I double press the call button, I could enter that code into the "Unlocked Keys" section and it would work again.

Can you recommend a possible solution for determining codes like these? I used to have a program that displayed the codes for each button as you pressed them but I can't find it and thought someone here might know...

If someone has a good solution I would recommend that Zuinige Rijder add a link in the "Keyboard Sensor" section of his website http://www.zuinigerijder.com/Settings.html#4.6
[Touch Diamond, MDA Compact IV Themes and Apps] hugr:
We're Sorry....., a problem has occurred with TouchlockPro.exe

Hi,

After installation on my HTC Touch Pro2 I get continuously Microsoft problem reports: "We're Sorry....., A problem has occurred with TouchlockPro.exe". Apart from that the phone does not lock......