yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am wondering if the percentage is the TouchLockPro battery percentage and the clock is the Windows Mobile 6.5.1 clock.

The first one seems to cover the second one :confused:

And that is because the icons are smaller on your device, so I think you need to adjust the clock size and fontsize in TouchLockPro :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
New version: TouchLockPro 2.8

I just uploaded TouchLockPro 2.8, which has GSENSOR improvements.

See for more details: changelog and find the *FREE* version here.
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
In both imagens, clock is rhe wm 6.5.1 clock.

On a first image, percentage battery is from touchlockpro and it is adjusted. But when are 2 digits in hour of clock, icons move to left but touchlockpro icon is not move.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro BattClock is not an icon, but is just drawn in the configured position. Apparently, the Windows Clock is moving all icons to the left :confused:, but that is hard to say by me, but just a guess. If you make the BattClock a bit smaller, it would no longer overlap.

You can also position the BattClock at the left side, so you do not have problems with the overlap and have more space too to make the BattClock wider. But maybe this does not look so nice.
[Touch Diamond, MDA Compact IV Themes and Apps] peacock93:
I had to go back to 2.7.6 because I was having the below problems with 2.7.8.

I'm running a WM6.5.1 ROM by NRG on a Sprint Touch Pro.

1) I mostly use the slide up on the right touch pad to do my unlocking. There has always been times when I had to try 2 or 3 times to get it to unlock but with 2.7.8 it is almost impossible to unlock.

2) After I get it unlocked it will sometimes relock itself without me doing anything.

3) I have it set to vibrate 1 time on lock and 2 times on unlock. When I power off it will vibrate 3 times. Then, when I power on it will be unlocked.

I use the light sensor, the touch pad and the slide out keyboard to unlock. I also have the TAPI set to lock the key pad on a in coming call and unlock once connected.

I hope this all makes sense but let me know if you need more information. 2.7.6 has always worked and is working correctly right now.

peacock93
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Added setting HTCLockAPIWhenBluetoothActive to use HTCLockAPI when bluetooth is active, so you can use the general keyboard hook locking method when no bluetooth is active.

I have an HTC Touch Pro, and I do not understand this setting. It was causing me to miss call... Is it suppose to detect when if I have a connected device?

I unpicked it, and now I'm back to normal :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for reporting the problems.

1) I cannot explain, for me it is working. Bot maybe this is a side effect of the other mentioned problems.

2) and 3) could be related to the added feature of locking when switching from screen off to screen on. Possibly the determination of screen on is not correct. I am looking into my own logging and source code if I can deduce the problem from there.

However, you would help me a lot, if you can enable debug logging and note the exact times when the problems occur. Thereafter post the log file \TouchLockPro.log.txt as zipped attachment. Hope I can solve this problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Indeed this setting is only used when there is a bluetooth connection active. With the general keyboard hooking, pressing the bluetooth answer key will be blocked, because TouchLockPro does not see the difference between the answer key of the phone or via bluetooth. With the HTCLockAPI it is possible to answer with the bluetooth key. But then you cannot use the slide2answer option.

I assume you did have a bluetooth connection, but did not answer via the bluetooth answer key:confused: If you answer via the phone itself (e.g. slide2unlock), you indeed need to disable this setting.

Was this your use case :confused: Or did I guess wrong.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.8.1

Because of the 2 reported problems, I uploaded version 2.8.1:

1) Made HTCLockAPIWhenBluetoothActive = 0 the default, so only the people who want to answer with the bluetooth answer button can enable it.

2) Disabled feature, till further investigated: change from screen off to screen on as power on and lock appropriate

I will investigate further the second issue, so I hope I can reintroduce it in a next version.
[Touch Diamond, MDA Compact IV Themes and Apps] peacock93:
Here is the log file you requested. I hope this helps. I did forget to keep track of the time it occurred but if you can follow when the device is powered down in your log file thenthat is when it locks and unlocks.

peacock93
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
You totally guessed right :D

I always leave my bluetooth on, and most of the time, it stays connected with my car. But I did some test, and even when it's not connected, it prevents me to unlock.

Oh well, I just disabled it, and I'm happy :D
[Touch Diamond, MDA Compact IV Themes and Apps] jappchae:
First, great program, ZR - Thanks!

I had the same unlocking symptom with 2.8, and in my case I saw it was clearly related to the light sensor. It's strange because if I was in a bright spot and I blocked the light sensor right at the same time as I would lock+suspend (w/ Capacative Nav swipe), the phone would still unlock right after the screen turned off. However, if I would first block the light sensor for a second or two, and THEN lock+suspend, the phone would stay locked and I could stop blocking the sensor after a couple of seconds without an unlock happening. Just my experience, hope it helps - I went back to 2.7.6 and it's great, but I'll try 2.8.1 now for the BT functionality.
[Touch Diamond, MDA Compact IV Themes and Apps] davidgiga:
I don't know if I'm to stupid but if I use the stylus to lock the phone and I push the power button it goes on (so far everythings okay) but there is nothing locked.. it vibrates 2 times (=unlocked) but I didn't do anything.

I'm using WM 6.5

EDIT :

Found the mistake.. it didn't safed my settings for an unknown reason.. but now it's working fine :)
[Touch Diamond, MDA Compact IV Themes and Apps] JVH3:
Ran into this while searching for a solution to a different problem.

Thank you for the post of your code. It looks very well written. I work professionally as a software engineer. The stuff I do professionally has nothing to do with phones, but is allmost all C# and C++.

I haven't had a chance to play much with it.

I'm more interested in the code used to handle orientation monitoring.

It looks like I have a good reference if I decide to do some programming that uses it now.

Very nice work.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for providing the log file.

I see that the Stylus registry key is not available in your ROM, so the Stylus sensor will not work, but I that is a known problem for your ROM, I believe:

2009-10-25 11:52:57 219875554 ERROR querying StylusOutStatus with RegQueryValueEx

What I also see, is that the Keyboard hook is not working:

2009-10-27 04:39:45 -1907042946 KBHook: Could not create Keyboard Hook

Only one keyboard hook can be active, so I expect another program uses the same approach. Did you install some special programs which does something with the keyboard? So that means the keys are not protected by TouchLockPro! I expect this problem is also available with older versions, so just be aware of that.

But now back to the reported problems:

It looks like the problems have to do with the screen off to screen on detection. I expect the problems will be gone with version 2.8.1.

At the same time I am testing a version, reintroducing the screen off to on, without the mentioning side effects.

Can you test if 2.8.1 still gives the mentioned problems :confused: If yes, I would be glad to look into that log file too.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, as you see I made it not the default setting in version 2.8.1, so people can choose to activate this setting.

I do not understand that when it is not connected, it prevents you to unlock. I need this to test myself more deeply. Anyway, the code will only lock at that setting when there is a bluetooth connection active, but apperently something else is wrong. I will check/debug that.

But I am glad it is working as you like now ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I expect 2.8.1 does not have the mentioned problems. Can you confirm:confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, good to hear it is working now.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am also a professional Software Architect and wanted to learn more about Windows Mobile programming. Here you can read how things started.

I also learn from others code, so that is why I also posted my source code. To keep TouchLockPro lean and mean, the main program is written in C++.

orientation.cpp holds the code for handling the GSENSOR. But probably you did find that already.
[Touch Diamond, MDA Compact IV Themes and Apps] peacock93:
2.8.1 did the trick!! thanks for a great program and support.

The latest EnergyROM is WM6.5.1 and it has problems with the Touch Pro Keyboard. I had to load an old version of EZInput to fix the problems so that may be what your seeing.

Thanks again,

peacock93
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
Hi, ZuinigeRijder!

What you think to update the translation of your app?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
If you can provide me the translations, I can add them.
[Touch Diamond, MDA Compact IV Themes and Apps] longice:
This might be a stupid question, but how can we create a translation - which files need modification?

An idea for next release: Is it possible to make the black background in unlock state transparent? It would integrate better graphically with WM6.5.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You need the source code, Visual Studio 2008 Professional and Windows Mobile SDK when you want to integrate the translations yourself. In all the action settings screens, you need to do the following:

- open the setting screens one by one, e.g. TAPIForm.cs in TouchLockAction project

- Select the top form and change the language from "Default" to your language

- Change all the texts in the UI to the appropriate texts

- You can even make the space for text smaller/larger

- Provide the translated resource file, e.g. TAPIForm.xx.resx

But there is also another possibility, using a ResX editor.

See the attachment for the resx files, including the ResEditor.exe. With the ResEditor you can open/save the resx files. You need the .NET 2.0 framework runtime for ResEdit.exe. If not installed on your Windows machine, you can get it from Microsoft (for free).

Steps to do:

1. Start ResEditor and open a resx file to translate (File -> Open)

2. Scroll down to the bottom and only translate the String entries ending with .Text (the right part of the screen). Do not translate Strings starting with >> and do not add/rename entries.

3. Save the resx file

4. Do all the resx files

5. Post the translation in this support group and also mention the language!

I will then update this in the next version (or when a batch of translations have been delivered)

But I can understand you will not have the environment to do this all. So you can just provide the original english text and the translation for all the screens. Then I will provide the translations in a next version.

Note that the start TouchLockAction screen is already translated into 32 languages, but the further Settings screens are currently only available in English, Dutch and Russian. A long time ago I asked for translations for the detailed settings screens too, but unfortunately with not the hoped result.

To my knowledge it is not possible to have transparency in Windows Mobile, for the BattClock overlay. If it is possible, I would glad if the solution could be provided.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Here are the current Russian translations. You can update those with the ResEditor, as described in my previous post.
[Touch Diamond, MDA Compact IV Themes and Apps] Arnold_hk:
Really useful :)

btw, is it possible to add "unlock while alert", such as for alarm?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Currently there is support for G-Alarm.

The following is on the Wish/TODO list:

- Exceptions list to not lock when some app is running and/or in foreground
[Touch Diamond, MDA Compact IV Themes and Apps] muhlatte:
sry if it's somewhere in your description, but is it possible to dim the backlight when it's locked (like the original lock)? maybe also no backlight except for incoming call (because i use the nav sensor). Thank you for your support!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually this one is already on the wish list:

Setting backlight low when locked for saving extra battery

I am currently working on the long list of wishes/todo, to add the as much as possible the asked features.
[Touch Diamond, MDA Compact IV Themes and Apps] jappchae:
I'm not sure - I actually did have the same unlocking problem intermittently with 2.8.1, but then I reverted back to 2.7.6 and still had the problem intermittently, so I'm not sure if there's something that didn't uninstall properly from 2.8 that is affecting the results. Very likely that it's just my phone. In any case, I had decided I didn't want the light sensor to unlock the phone anyway so everything I want to use works perfectly in 2.8.1 which I'm running now - sorry my testing didn't produce any valuable result.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will see if I can add logic that TouchLockPro will not unlock by the light sensor when the screen is off. I am already testing a few days the screen off and screen on, and it seems to work now as I want. Not unlocking by light sensor with screen off seems a logic thing. :rolleyes: Probably also the GSENSOR should not unlock with screen off.
[Touch Diamond, MDA Compact IV Themes and Apps] slickker:
I have a Question (hearing Music using Bluetooth Headset)

Hello, I always appreciate the good software TOUCH LOCK PRO.

I have a Question.

Everyday, I hear Musing using Touch Diamond and Bluetooth headset.

But, on the way to hearing music, Locking didn't work.

When Music is stoped, Locking is work well.

I find related option. But, I don't know this solution.

Please, tell me how can I lock the device that hearing music.

Thank you.

p.s Sorry, my english is so bad..:)
[Touch Diamond, MDA Compact IV Themes and Apps] indian66:
is it possible to disable the Hardware Keys on incoming calls (on a HTC Blackstone/StockRom)?

I tried all combinations of settings, nothing will disable the Hardkeys
[Touch Diamond, MDA Compact IV Themes and Apps] hargibi:
Hi.

I got a touch HD with the newest topix 6.1 rom.

Ive installed TLP 2.8.1 and tried to lock the phone..

But when i press the lock button nothing hapens.. I got lock on power on enabled but that dosent lock the phone either!

What could this be? :O Ive tried to reinstall the program and reset the phone after installing..

Hmm
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you try to set HTCLockAPI (HTCLockAPI = 1).

Because the general keyboard hook may not work when another program uses the same approach. Of course then you cannot unlock via a key sequence, but with the Diamond there are numerous other ways to unlock.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
If you only want to disable the hardware keys at incoming call (not locking the TouchPanel, because you want to use the Slide2Answer), you must set in the TAPI settings screen:

KeysOnly (LockWhenIncomingKeyOnly = 1).

Note that you must set then also HTCLockAPI = 0, otherwise the TouchPanel cannot be unlocked.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Is the BattClock showing a lock status? Or is it the normal BattClock?

If that is the case, it is possible that it will not lock, because it is on (USB) power or the stylus is reported out.

You can enable debug logging (LogDebug = 1) in "other settings", reproduce the scenario and post the log file \TouchLockPro.log.txt in the root of your phone as zipped attachment. Maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] hargibi:
Stupid stupid me.. lost my stylus a while ago.. now its all fine :) Thank you!
[Touch Diamond, MDA Compact IV Themes and Apps] indian66:
I set:

LockWhenIncomingKeyOnly = 1

KeysOnly = 1

HTCLockAPI = 0 (Keyboard - there is all =0 (deactivatet)

HTCLockAPIWhenBluetoothActive = 0

But the Hardkeys are already active...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, can you enable debug logging (LogDebug = 1), reproduce the scenario and post the log file \TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
When I am calling the screen is off, but when I finished the call the screen is turned on and off.

I have one another problem too. When I talk with the bluetooth i can´t turn screen on. Becouse when I turn the screen on, turns off in 2 seconds.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The first one, is probably due to the InCallTweak. The other one is related, I think.

I will try to reproduce and check my code, see if I can solve the mentioned problems.

You can help by enabling debug logging (LogDebug = 1), reproduce the 2 problems and post the \TouchLockPro.log.txt log file.
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
My log file.
[Touch Diamond, MDA Compact IV Themes and Apps] mean_tee82:
Huge log file

Agreed that the application has a small footprint on the RAM

But why does it have a 8MB log file in the system memory?

Thats huge when every MB counts. Probably you could limit the usage.

Its a very neat app using all the sensors available but is still buggy, everytime I try to end a call, the screen keeps turning off automatically, if i turn it on, it would turn off the very next moment. Very difficult to manage.

Does anybody have a remedy for this?

By the way, I have not changed any of the default settings and I was running the latest version. Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked into the log file and it is indeed related to the InCallTweak. The CALL_ENDED event is coming later, so the InCallTweak does a screen off. I the new version, which I will upload shortly, I will do a screen on again at the end call.

The bluetooth problem should also be fixed in the new version, 2.8.2.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The huge RAM file will only be created when you enable debugging (LogDebug = 1). After usage, you can just disable debug logging and delete the log file TouchLockPro.log.txt.

I will see if I can automatically remove it at startup, when no debug is active.

The call ended event is coming later, so the InCallTweak still thinks it is in a call. Actually, there was a 5 seconds delay, so TouchLockPro thought it was still connected. In the new version, this is solved and the screen is enabled after the call ended automatically.

Probably today I will post the new version 2.8.2.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.8.2

Just uploaded TouchLockPro 2.8.2 :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] MELPHBOY:
Answering with bluetooth headset

I have up grade to TP 2.8.2 and I am still not able to answer my phone using my bluetooth headset. I have HTClockAPIwhenBluetoothActive checked but, it still will not let me answer the phone unless I manually unlock the phone. Does anyone have a fix for this problem?:confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, because others using bluetooth do not have this problem. I myself do not have a bluetooth headset, so I cannot reproduce.

TouchLockPro looks for the registry key:

HKLM\\System\\State\\Hardware\\Bluetooth

A value above 9 is seen as bluetooth connected.

Maybe that detection is not working? Did you also tried to set HTCLockAPI = 1 :confused: Because normally, the answer/reject buttons on your bluetooth device will then not blocked.

Can you enable debug logging, reproduce the scenario and post the debug log file \TouchLockPro.log.txt. Maybe that gives me a clue?
[Touch Diamond, MDA Compact IV Themes and Apps] MELPHBOY:
I tried HTCLockAPI = 1 and it allowed me to answer the phone with the bluetooth headset but, I use my hardware keys to unlock my phone and with this seting I will not be able to use them. I add attachment:confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You did post the TouchLockAction.log.txt instead of TouchLockPro.log.txt. After enabling debug logging, reproduction of the scenario, you need to stop TouchLockPro (via Programs menu). Thereafter you can copy the log file \TouchLockPro.log.txt and start TouchLockPro again. Thereafter you can disable debug logging again.

Your reply gives me a clue in the misunderstanding.

The HTCLockAPI = 1 will block all keys and the TouchPanel. The only way to answer then is via the bluetooth answer button on the device itself (if it has them). So the DetectBluetooth and related HTCLockAPI is only of interest if you answer with the bluetooth answer button.

Apparently, you do not want that behaviour or do not have or use the bluetooth answer button. Then the only option is *NOT* to use the detect bluetooth (DetectBluetooth = 0). So you have the normal usage of TouchLockPro, with a bluetooth headset, but still answering as usual, after unlocking.
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
Last version works very good. But sometimes screens turns off and I haven´t touch anything.

I upload my log file
[Touch Diamond, MDA Compact IV Themes and Apps] xuyong:
It is my best selection

yestday I install the APP with my HTC Diamond.

Good, it is a good APP which I want so much.

I tried PocketShield, but so bad. I think　PocketShield is not a Commodity, because it has so much bugs in my Diamond.

Thanks again.:p
[Touch Diamond, MDA Compact IV Themes and Apps] wmjan:
Me too. Also there has been a blank log "touchlockpro.log.txt" in my phone, and can not be deleted.

This is a great work!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately the log file is empty.

When you switch from debug on to debug off, the content is with the newer version emptied. So you need to copy the log file, before you switch to non-debug log file. And you can only copy the log file when TouchLockPro is not active, so you need it to disable it first via programs menu.

I expect the problem is related to the more sensitive GSENSOR? You can empty the commands for the GSENSOR gestures having !LOCK and !LOCKSUSPEND, if that is the problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I will see if I can just remove the log file, instead of making it empty in a next version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear that it works better than PocketShield :)
[Touch Diamond, MDA Compact IV Themes and Apps] wmjan:
My GSensor settings:

Time: 3000

1 and 4: 123

2 and 3: Default

Is also very sensitive and very convenient to use, while the latest version of InCallTweak also very human.

But the default !SCREENOFF and !SCREENON all equal !LOCKSUSPEND

After locking the screen I can not press all the buttons including the power button, this problem is rather trivial occurrence.

PS: My English is very poor
[Touch Diamond, MDA Compact IV Themes and Apps] mean_tee82:
Thanks

You are one dedicated man, Cheers :)
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
This is my new log file.