yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, I hope the changes will solve your problem.

Now a screen off is not seen as power off, so the sensors keep working, and important for your use case, it will keep the phone in the same (un)locked state.

Now the (lock)suspend should also work for incoming call and while in a call, the screen will be off and the phone is still locked, which will save some battery in combination with bluetooth.

Also, if you enable detectbluetooth, it automatically (lock)suspends at end call.

EnableInputAtSuspend is also reintroduced, for people who use HTCLockAPI = 1 and do not want the (power) button to be unlocked. However, the locking of the power button, while really off, is dependent of the phone. My Touch Diamond does not lock the power button when not enabled, but some other people have this behaviour and some even want to use this as feature (Security).

For your use case I would set, after reset to the default settings in ther About screen:

HTCLockAPI = 1

DetectBluetooth = 1

DetectBluetoothLightUnlock = 0

And you can consider and test, if you mainly use bluetooth:

CommandCallIncoming = !SCREENOFF;!KEEPALIVEOFF

CommandCallConnected = !SCREENOFF;!KEEPALIVEOFF

But you can also set the windows mobile settings for backlight off and phone off relative short....
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

thanks ill try it out, but the suggestions for setup:

HTCLockAPI = 1

DetectBluetooth = 1

DetectBluetoothLightUnlock = 0

are no new or changed features ? so they wont make any difference/not solve the problems (these were my some of my "old settings")?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
HI

I installed and now have a huge problem: I used reset to defaults but now i cannot start touchlock actions anymore - it runs shortly and terminates. I tried to reboot and fresh install, i even tried installing old version - no solution. I have to do i hard reset :-( unless you can tell what to change (in registry ??)

thanks ill try it out, but

the suggested settings

HTCLockAPI = 1

DetectBluetooth = 1

DetectBluetoothLightUnlock = 0

are no new settings/changed settings so how can these solve the problems ?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi,

Same for me, unable to run 2.7.4 on my device.

Tried to install back 2.7.2, works much better, but cannot set it anymore to allow the slider to work on incomming call. (turn on the screen only). :-(

On Uninstall it doesn't delete the registry keys, doesn't delete all the program files and doesn't remove the entries from "all programs", I've had to remove all them manually.

HELP needed !

BR
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You do not need to hard reset.

I can also reproduce the problem, so I am investigating what is going wrong.

I removed version 2.7.4 for download.

You can desinstall version 2.7.4, delete registry tree HKCU\Software\ZuinigeRijder with a registry editor and delete \Windows\TouchLockAction.exe

Thereafter you can install version 2.7.3, which should work as usual.

Sorry for the inconvenience :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It is nornal that an uninstall will not remove the registry keys, so a next version uses the previous settings. I could uninstall TouchLockPro (see previous post) and install back 2.7.3.

I cannot explain the slider problem. Maybe because you did not set KeysOnly=1?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro version 2.7.5 which fixes a serious problem in 2.7.4.

I just uploaded version 2.7.5, which fixes a serious problem, that TouchLockAction will no longer start when reset to defaults is done.

So people who did install version 2.7.4 should deinstall it and install 2.7.5 instead.

If TouchLockAction cannot be started thereafter, you should remove the registry tree: HKCU\Software\\ZuinigeRijder and thereafter reset to defaults in the about screen of TouchLockAction.

Sorry for the inconvenience :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi ZuinigeRijder, thanks - no problem. But before testing could you elaborate on my questions from latest post - i need to understand how this version solves the Touch Pro 2 problems ? You also previous mentioned reinserting EnableInputAtSuspend as a possible solution but doesnt mention it now - why is that?

best regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Although the settings are the same, the following changes have been made:

- it will no longer unlock when only the screen goes off

From your logging I deduced this was the problem. If this is still not working for you, you can try EnableInputAtSuspend = 0, so TouchLockPro will keep the phone locked, even when in a suepnd/unattended mode/deep sleep. The problem with EnableInputAtSuspend = 0 can be that the power button is locked while screen off or in a deep sleep. So therefore I did not mention this in first place. Probably it will already work with the mentioned settings.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

i now can start touchlockaction but when resetting i get an error message and suddenly all the settings aer set to "nothing"

What to do ?

Now it appears that hardware keys can be locked, but then also the on/off button is locked. If i chooose "htclockapi" = 0, then on/off can be active but so are home and back it appears, Further i cannot pickup call with bluetooth (even though i have chosen detect BT)

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Probably TouchLockPro was not (yet) running, when you did run "reset to defaults". TouchLockPro will recreate the settings to default when the registry settings are not there at startup or when asked by TouchLockAction.

The on/off button locked, indeed indicates it is working now, with Screen off.

HTCLockAPI = 0 will also catch the Bluetooth answer/reject buttons, because that are the same keys as the answer/reject button as on your phone. So for your use case, this is not a good configuration. People with bluetooth should use HTCLockAPI = 1.

You can still wake up the phone by taking out the Stylus, in case the power button is locked (or slide out the keyboard slider). When you set EnableInputAtSuspend = 1, then it will unlock the power button when going to suspend/unattended/sleep, but not when only going to screen off (another program is keeping your phone awake, e.g. in call).
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

it was running for sure bevause i saw the battery clock symbol.

But as said i cant pickup call with BT if htclockapi=0

is there a way to have all buttons locked but not the on off??

The problem still persists about touching the area left of logo - will you work on this or how do you think?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately I cannot do anything on the on/off power button, because HTCLockAPI = 1 is something from HTC which does not allow the wanted control.

Also the area left of the logo is difficult for me. I do not own a Touch Pro 2 and probably this porprieraty behaviour cannot be influenced. I expect other locking programs have the same behaviour/problem.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
hmm, ok i understand. But shouldnt it be possible to specify key 129 as unlocked key ? I tried this but didnt work - maybe because i have chosen some other setting ? See attached my settings

I understand htclockapi =0 for this to work but then i cant pickup call with BT

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
With HTCLockAPI = 1 you cannot unlock certain keys, this only works with HTCLockAPI = 0, because then TouchLockPro has a keyboard hook in-between.

The only way to combine bluetooth with HTCLockAPI = 0 is to unlock the bluetooth answer button. I expect it is the same key as the answer key on the phone, so there is a chance you press the answer button on your phone, while in your pocket.

It should be possible to intercept the bluetooth AT commands, intercepting the bluetooth device button presses. However, I have never been looking into it and maybe is also dependent of the bluetooth implementation stack.

If someone could provide me with working source code for intercepting the bluetooth AT commands, maybe I can then detect the bluetooth answer-reject key presses......
[Touch Diamond, MDA Compact IV Themes and Apps] golightlygl:
2.7.5 cures unlock on data call - improves battery life

Just to report that the 2.74/5 updates solve the problem of the phone "locking" when a data connection is made so that when the screen is turned on during a data call, the phone would be locked.

As a result of this, battery life has improved dramatically and the unlocking performs flawlessly. I have the system set to lock keys only (on Touch HD) leaving the Slide to Answer when a call comes in and remain unlocked in all other circumstances.:)

As I see it, the application now perfectly handles the various ways of unlocking a device. It also intellugently handlers how to "lock" the device during the most complicated "wake-up" event - an incoming call.

The next challenge, should you feel up to it, is to look at other "wake up" events and give them the option of: keep screen off, lock touch screen, lock touch panel, lock h/w keys or any combination. By "wake-up" events I mean things like "reminder", "alarm", "incoming SMS", "incoming e-mail" (and ideally "power button" but I understand this is impossible!) etc. Do you think you might look into this? I can help where I can with research etc. but, as you know, I can't actually do any coding!;)
[Touch Diamond, MDA Compact IV Themes and Apps] maesus:
!UNLOCK wake up the phone? cor !SUSPEND didn't suspend at all

ZuinigeRijder,

On 2.7.5, I set G-sensor to support these commands:

"3" - !UNLOCK

"6" - !BACKLIGHTON

"5" - !BACKLIGHTOFF

"4" - !SUSPEND

(yes, I didn't use the LOCK function at all, but just want to put the phone to sleep at different G orientation)

here is what I found it acted different than previous versions.

!SUSPEND turn off the screen, all keys are disabled; (same behavior as before); but then I trigger !UNLOCK ("3" put the phone in portrait), the screen turn ON again. Previous version, the only way to wake up from !SUSPEND is by pressing the power button.

This leads me to suspect !SUSPEND doesn't work as previously, but only works like !BACKLIGHTOFF. I also tried with !LOCKSUSPEND, the result is the same, once !UNLOCK triggered, the screen turn on again. It didn't even lock the phone but merely "!BACKLIGHTOFF".

Is this a bug, or new feature in 2.7.5?
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
I see. Based on my experiences so far i now decided to make settings as follows:

1) leave all settings unchecked only checking

2) Use G sendor unlock on face up

3) htc lock api

4) battery clock, clickable, battery, lockindocator

5) use tapi, screen off when connected, lock when incoming

i would have expected that phone is unlocked all the time unless an incoming call arrives which should lock the phone.

But that does not happen - the phone is unlocked all time - ignoring to lock it when a call is incoming

why is that ?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear that the battery life has been improved and the data connection fix is working :)

I still searching if I can detect if the power button has been pressed or not. I have also on the wish list to configure commands when a specific foreground window is active at startup. So some of your needs can be fulfilled with that.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I expect your phone was not in a deep sleep, and therefore the GSensor actions are executed. Maybe because of KEEPALIVEON, which is part of !BACKLIGHTOFF :confused:

Can you enable debug logging, reproduce the scenarion and post the log as zipped attachment. Maybe that gives me a clue :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, does not immediate ring a bell. Can you enable debug logging, reproduce the scenario and post the log file :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

yes of course, i have attached log file

the screen/phone is not locked when incoming call

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, I do not see anything related to an incoming call in the logging. Are you sure the logging is complete?
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

i repeated the test and attached a new logging

The phone was unlocked prior to the call and shut off via close button. The the phone received the call and the phone was still unlocked despite the attached settings in TLP (did i miss a setting?) i terminated the call normally and zipped the log

regards NOlan
[Touch Diamond, MDA Compact IV Themes and Apps] maesus:
hi, here's my log file for your debugging on !SUSPEND issue.

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
weirdly, I still see no TAPI logging :confused:

Can you empty TouchLockPrp.log.txt, enable debug logging, do a soft reset and reproduce the problem. Maybe the TAPI has gone wrong before this reproduvtion logging :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I looked into the log file.

I see:

009-10-01 16:29:45 -829253014 = GSENSOR ORIENTATION MATCH =: 2 numberOk: 1 numbersequence: 6 orientation: 6 FaceUp

2009-10-01 16:29:45 -829253014 ==================COMMAND BY GSENSOR ORIENTATION==========================: 2

2009-10-01 16:29:45 -829253014 Execute(): !BACKLIGHTON

then:

2009-10-01 16:29:46 -829253014 SetOrientation: UpsideDown

2009-10-01 16:29:46 -829253014 = GSENSOR ORIENTATION MATCH =: 4 numberOk: 1 numbersequence: 4 orientation: 4 UpsideDown

2009-10-01 16:29:46 -829253014 ==================COMMAND BY GSENSOR ORIENTATION==========================: 4

2009-10-01 16:29:46 -829253014 Execute(): !SUSPEND

The phone is not going into a deep sleep, only screen off. So the sensors keep working (this is changed behaviour):

2009-10-01 16:29:46 623577142 ========================POWER_STATE_IDLE: SCREEN_OFF==========================

Thereafter you do an immediately !UNLOCK:

2009-10-01 16:29:47 -829253014 = GSENSOR ORIENTATION MATCH =: 1 numberOk: 1 numbersequence: 3 orientation: 3 Portrait

2009-10-01 16:29:47 -829253014 ==================COMMAND BY GSENSOR ORIENTATION==========================: 1

2009-10-01 16:29:47 -829253014 Execute(): !UNLOCK

I think I found the problem. The !SUSPEND does not go immediately in a deep sleep, but does this via the IDLE state:

SetSystemPowerState(NULL, POWER_STATE_IDLE, 0);

Apparently, the !SUSPEND needs to go to a deep sleep immediately, e.g. using

keybd_event(VK_OFF, 0, 0, 0);
keybd_event(VK_OFF, 0, KEYEVENTF_KEYUP, 0);

I will test if this gives the expected behaviour :eek:
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

i have no such file TouchLockPrp.log.txt on my unit

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
ok, typo, I mean of course \touchlockpro.log.txt
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

this was already done twice before last test and uploading

Regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, but I asked to have the logging from soft reset till reproduction, because I expect something goes wrong before you started the reproduction. Somehow the TAPI commands are not logged anymore, so listening to TAPI must been gone wrong before the logs I did get till now......
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

right did so - after a reboot it worked with lock on incoming call - but now it do not respect "ScreenOffWhenConnected" - the screen is lid up bright and only is dimmed and shut off when windows settings forces it to

uploaded log

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see in the logging that !BACKLIGHTOFF is executed. Apparently it awakes out of backlight off due to some event. I will see if I can change it into a screen off, instead of backlight off. I need some testing for that. You can also try to set CommandCallConnected = !SCREENOFF
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Here you mean set the command string !SCREENOFF in section Telephone API in "Connected" ? But if so, shouldnt that alrady have been taken care of by checking option "ScreenOffWhenConnected" ?

Hi

i will test this: EDIT tested, reult= it appears to shut off the screen but after app 2 seconds the screen lid up again, and and if i force the screen off with close button and have the command suspend after ended call the screen lights up again (as if the phone gets 2 sequentially identical commands from the OS?)

I will try to summarise, the features that i found not to work on the htc touch pro 2, can anything be done to solve them ?

1. Area next to logo will lid up the screen when touched from lock position

2. input in Unlockkeys and unlocksequence seems to be ingored

3. NAV sensor seems to be unavailable

4. commands in Incoming, Connected, Ended seems to be ignored

other functions seems to work fine

thanks

regards nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In my previous post I noticed that the ScreenOffWhenConnected was done via !BACKLIGHTOFF. So I can change into !SCREENOFF, but then still an application can force the screen on again.....

Apparently the application handling the incoming/connected call forces the screen on again. Nothing TouchLockPro can do about that.

The features working for Touch Pro 2 are described in this table.

1. I do not know how I can avoid this.

2. Does only work with HTCLOCKAPI = 0

3. Is indeed not available, a zoombar is available but not supported by TouchLockPro.

4. is working, but a running application can force to do otherwise
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
hmm, ok thanks, to wrap it all up: which of all these can you do somethong about/will you try to find a solution to ?

I think its strange that the pro 2 should behave so different than eg the diamond 2 eg Apparently the application handling the incoming/connected call forces the screen on again. Nothing TouchLockPro can do about that.

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Hi ZuinigeRijder,

Ok... I'm now using the Touch InCall Screen Tweak, but now I have a problem with TLP when using with bluetooth. If I have the phone at my belt, InCall thinks it's against my ear and when I end a call the TLP unlock my phone... I read earlier in the tread that you are also using InCall Tweak, what settings (TLP and InCall) should I use to keep the phone lock when using bluetooth.

Thanks,

Eric
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi Eric,

what is the "InCall Screen Tweak" - how is this tweak set and what does it do ?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Hi Nolan,

It's a nice app that will detect when you put your phone against your ear and turn off the screen. It will will also turn it back on when as soon as you remove it from your ear.

check it at http://xdaforums.com/showthread.php?t=488991

The author explains it better :D

Eric
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I always try to find solutions ;) I keep searching....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
strange that it unlocks. Can you enable debug logging, reproduce the scenario ans post \touchlockpro.log.txt

I have the InCall Screen tweak on the wish list. I have the ingredients to do the same, TAPI support, GSensor and light sensor......
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
I tried choosing htclockapi =0 in order to avoid the problem of the on/off button cant be used when locked, but then i cant pick up call with bluetooth - even if i have chosen detectbluetooth

Enableinputatsuspend seems to be ignored too

So its not possible to combine an really good solution it appears

Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The only thing you can do now is to unlock the answer/reject buttons for htclockapi=0
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
New version with InCallTweak

I just uploaded a new TouchLockPro version 2.7.6 with a new feature: InCallTweak

Changelog

Downloads

Hope you enjoy this new feature :D
[Touch Diamond, MDA Compact IV Themes and Apps] nextpimp:
I have a feature request... Would it be possible to change the color in realtionship to battery %. I ALWAYs cover the battery icon with this wonderfull app and a lil color coded feedback would be awesome. 3 - 5 color options within xyz range... ie. 100-85% green 84-65% Yellow 64-34% orange 34-0% red. You get the idea. Id be more than happy with just 3 choices if i could set the range / colors myself
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
hmm, i hear what you say - but id rather hope that you will make all features work as supposed, so that HTC touch pro 2 users have uasge of all functions - of course except the features that are physical impossible as eg the nav sensor

tbanks regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
thanks, but where can i read about how to use the settings ?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The problem is that HTC does not publish their API's and sourcecode (like I do). So it is difficult to achieve exactly how you would expect it should be. Frankly said, it is a shame that TouchLockPro and other locking solutions are needed in the first place. The standard behaviour in Windows Mobile should have covered this already. I just try to give an alternative solution to the problem. And I am aware of the fact that I am also limited in solving the problems and cannot make everyone happy. At the end it is you who must choose which locking solution you like the best. I will keep trying to search and improve TouchLockPro, to take away problems as much as possible.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I will put this on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
As always it is described in Settings. Search for InCallTweak. Make sure you do a refresh in the browser, maybe you have a previous version in the cache.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Ok thanks, found it. But i think you need an additional rule:

Default it will put the screen off, when connected and the GSENSOR orientation is portrait,: Here you also need GSENSOR orientation is ReverseLandscape because both will be relevant when calling holding phone at ear ?

But if i have enabled light sensor unlock - does this override this ie disables the light sensor unlock ?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
I have a problem with the G-sensor. It woks a little time, a then doesn´t work.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
HI

i complete agree with you ;-)

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] derekcranson:
Excellent program.

I use this to lock all buttons as when I am at work driving my phone stays on my belt and I control it from my bluetooth earpiece.

All appears to work correctly and gives me a slightly better battery life as no screen turned on.

I update my rom (see signature) all the time. In the more recent roms htc have reverted to the old bluetooth stack or at least changed it so that Voice command now works fully from the bluetooth headset.

So thank you ZuinigeRijder for this excellent program which does everything I want it to.
[Touch Diamond, MDA Compact IV Themes and Apps] danico:
Voice recording in the pocket

This soft is excelent. It works very well and I finally find the way to use voice recorder software with the phone in the pocket.

Great job !!!