yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange that HTC did not incorporate that battery driver by default. Good to hear that there is a solution for you (and others). I just rely on the battery driver.

Actually, reinstall would not help. Because the registry settings are retained, so when you upgrade to a newer/other version, those will stay. I always try to keep the settings upwards compatible. So if you want to go to the default settings, you have to do that indeed via "Reset to defaults".

This problem is there already a few years, and nothing is provided out of the box. There are other locking solutions, but I decided to make my own one. Because I wanted to keep it simple, small, efficient and work together with other programs.

Actually, BattClock has been started with a separate program with only date/time/battery% possibilities. Over time things have been added, with efficiency in mind. I knew I cannot make "one solution which fits all", so I provided a lot of possibilities, so everyone can choose to their liking. Although it takes some time to invest in make your own personal likings.

You can put over the Window Logo and Start text. Pressing that area still opens the Start menu. However, because the control over the width of the cells is not so fine grained, choosing a long text means also you are limited currently in the number of items to display then.

So you could make 3 rows with e.g. a width of 240 pixels.

You can also decide to split the long date/time in individual pieces and put them in the cells, e.g. 2 rows x 5 columns.

I am working on the possibility to have 6 separate BattClock areas, so you have even more control.

Every stripe (you have 6 of them), can be individual placed. Vertical stripes when height is bigger than width. See: BSettings.html#4.7

In dark circumstances the light sensor will not work as expected. So in those cases you need a fallback, e.g. unlock via Volume Up/Volume Down keys. My Touch Diamond also has a default "Slide to Answer", so I can set KeysOnly (LockWhenIncomingKeyOnly = 1) in the TAPI settings screen.

This is a little bit dependent of the bluetooth device you are using and how it sends the accept button. But HTCLockAPIWhenBluetoothActive (HTCLockAPIWhenBluetoothActive = 1) should in general work for your phone.

TouchLockPro locks at power on by default (when lock at power on is set). So you should not be needed to disable SMS notifications and such.

I use them also both, I did put the BattClock info over the Windows Logo/Start menu for the extra items. And of course the stripes.

I do not have experience with such programs, so maybe others can advice.

I also did not know how to program Windows Mobile for 2,5 year ago. I just started with it, with this as a result. For me it was fun to learn programming for Windows Mobile, find out how to control all the sensors. And it deepened my knowledge of C++ and C# for Windows CE/Windows Mobile.

Unfortunately, Microsoft has left Windows Mobile where it was, and switched to Windows Phone 7. I regret that step and think this will be the end of Windows Mobile :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] omek07:
Hello again

I have this "Solved problem of screen off after call ended (InCallTweak related)" problem on version 2.12.8 , i have Omnia 2.

What can i do for this ????

Can we do the Program Power Off the device 2-5 sec after call ended or after unanswered call????
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you enable debug logging, reproduce the scenario and psot the log file as zipped attachement (in the root of your phone: TouchLockPro.log.txt).

Please note the exact time the problem occurred, so I can easier find the relevant logging.
[Touch Diamond, MDA Compact IV Themes and Apps] omek07:
There you are !!!!

I have done 2 missed calls on my phone at 13:32 .

look and tell me what you see ....

Thanks you

And 1 more question if i disable the BattClock on TouchLockPro and install the ORIGINAL (http://xdaforums.com/showthread.php?t=612083) BattClock how i can recognize that the device is LOCKED ????

I wand to install the BattClock 3.3 because i NEED the new functions of this APP...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
2010-12-31 13:32:13 1724342526 SetCallStatus(CALL_INCOMING): 0

....

2010-12-31 13:32:13 143381130 Execute(): !UNLOCK

I suspect that this is due to the setting:

2010-12-31 13:31:59 143381130 GetSetRegValue(): CommandCallIncoming

2010-12-31 13:31:59 143381130 ==DEFAULT VALUE====:

2010-12-31 13:31:59 143381130 ==OVERRULED VALUE==: !UNLOCK

2010-12-31 13:31:59 143381130 CommandCallIncoming: !UNLOCK

Why did you set this? Because the purpose is to unlock only, when it is no longer in your pocket. This way you will get missed calls. Otherwise use of TouchLockPro does not make much sense.

2010-12-31 13:32:17 1724342526 SetCallStatus(CALL_ENDED): 1

2010-12-31 13:32:17 143381130 ExecuteRequest(): !UNLOCK

Also at end call you have configured:

2010-12-31 13:31:59 143381130 GetSetRegValue(): CommandCallEnded

2010-12-31 13:31:59 143381130 ==DEFAULT VALUE====:

2010-12-31 13:31:59 143381130 ==OVERRULED VALUE==: !UNLOCK

2010-12-31 13:31:59 143381130 CommandCallEnded: !UNLOCK

I also see the following:

2010-12-31 13:32:21 1724342526 HandlePowerNotifications()

2010-12-31 13:32:21 1724342526 PBT_TRANSITION

2010-12-31 13:32:21 1724342526 PBT_TRANSITION POWER_STATE_SUSPEND

2010-12-31 13:32:21 1724342526 ========================POWER_STATE_SUSPEND==========================

So 4 seconds later your phone goes to power off.

Quoting the problem you reported:

In the logging I do not see InCallTweak triggered.

The first one (screen off) could be related to a Windows Mobile setting to go to power off in 4 seconds? Or at least after the screen goes on the first time? Because from the logging I do not see TouchLockPro is issuing the suspend.

The second question: there is a possibility to suspend after power on:

SuspendTimeOutPowerOn (SuspendTimeOutPowerOn = 30000)

Defines the time in milliseconds, to suspend the device again when it is still locked. In previous versions it was only possible to couple the suspend to the SuspendOnBackLightOff setting. Now you can configure this independent via this setting. If you do not want this suspend behaviour, overrule this registry key with "SuspendTimeOutPowerOn = 0"

That is not exactly what you are asking for, because this is a general setting, not related to end call. And so you need to unlock in that amount of time, otherwise it will do a screen off automatically.

There are several possibilities. The easiest one is to make sure the BattClock area does not use the same area as TouchLockPro, e.g. over the start menu.

And another possibility is to configure in TouchLockPro to use a stripe when locked, but also then you must make sure not to overlap BattClock stripes wuth the TouchLockPro locked stripe.....
[Touch Diamond, MDA Compact IV Themes and Apps] omek07:
Ok if i understand i have wrong values on the touchlockpro , i am right ???

I dont have done anything for Windows Mobile setting to go to power off in 4 seconds

HOW I CAN CHANGE THIS AND WHAT VALUES I HAVE PUT

suspect that this is due to the setting:

2010-12-31 13:31:59 143381130 GetSetRegValue(): CommandCallIncoming

2010-12-31 13:31:59 143381130 ==DEFAULT VALUE====:

2010-12-31 13:31:59 143381130 ==OVERRULED VALUE==: !UNLOCK

2010-12-31 13:31:59 143381130 CommandCallIncoming: !UNLOCK

Why did you set this? Because the purpose is to unlock only, when it is no longer in your pocket. This way you will get missed calls. Otherwise use of TouchLockPro does not make much sense.

2010-12-31 13:32:17 1724342526 SetCallStatus(CALL_ENDED): 1

2010-12-31 13:32:17 143381130 ExecuteRequest(): !UNLOCK

Also at end call you have configured:

2010-12-31 13:31:59 143381130 GetSetRegValue(): CommandCallEnded

2010-12-31 13:31:59 143381130 ==DEFAULT VALUE====:

2010-12-31 13:31:59 143381130 ==OVERRULED VALUE==: !UNLOCK

2010-12-31 13:31:59 143381130 CommandCallEnded: !UNLOCK

I also see the following:

2010-12-31 13:32:21 1724342526 HandlePowerNotifications()

2010-12-31 13:32:21 1724342526 PBT_TRANSITION

2010-12-31 13:32:21 1724342526 PBT_TRANSITION POWER_STATE_SUSPEND

2010-12-31 13:32:21 1724342526 ========================POWER_STATE_SUSPEND======= ===================

What do you mean with this

There are several possibilities. The easiest one is to make sure the BattClock area does not use the same area as TouchLockPro, e.g. over the start menu.

And another possibility is to configure in TouchLockPro to use a stripe when locked, but also then you must make sure not to overlap BattClock stripes wuth the TouchLockPro locked stripe.....

Please Can you please give me the exact steps that i have to do ???
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
For my phone it is below (I have a dutch phone, so maybe I did not translate correctly):

Start -> Settings -> System -> Energy -> Advanced tab

But it could also be another application you have forcing the power off.
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
or you can try this

You can try NoSleep.cab
[Touch Diamond, MDA Compact IV Themes and Apps] cduck:
Lock toutch pabel only

The new versions, option Lock toutch panel only doesn't work!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, the new version is already old ;)

Can you provide more details about your phone, ROM and settings.

Enable debug logging, reproduce the scenario and post the debug log file TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue.

Probably it is a configuration error.
[Touch Diamond, MDA Compact IV Themes and Apps] Huthus:
I tried this app for the first time yesterday and it's really working great! Many thanks!

But I wasn't able to find an answer for my short question, how it is possible to teach the phone to wake up if there is a notification (SMS, alarm, reminder) on the screen. Is there an option for this?

I know it is helpful, if the device does not unlock in this case, but I want to use the standard alarm and this morning it didn't stop ringing because screen was locked... ^^
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
suggestion

try g-alarm.......much better and it can unlock TLP itself
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not know what phone type you have.

If you have one with a Stylus sensor or Keyboard sensor, you can put away the phone with the Stylus out or Keyboard open, so it will not lock. Or you can put it on the charger.

Indeed G-Alarm does support TouchLockPro by unlocking it.
[Touch Diamond, MDA Compact IV Themes and Apps] Huthus:
Is an idea to solve that problem, thanks!

But there is no option to get the screen unlocked by the wm-notifications? Like I said it would be nice, if I can use the wm-alarm like ever... :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro cannot distinguish the reason why the phone awakened, so this is difficult to implement. An option would be to detect the foreground window and unlock for the window names a user specifies to unlock. But that is not part of TouchLockPro currently. Actually I am not planning updates for TouchLockPro anymore :o
[Touch Diamond, MDA Compact IV Themes and Apps] christopherwoods:
Calling all people who've had success with the zoombar and the proximity sensor!

I've got a new TP2, currently running Jackos 01/01/2011 Full and with only a couple of other apps (CorePlayer, GSPlayer and Total Commander). However, I can't get either the zoombar or the proximity sensor unlock features to work; even with the TF3D workaround enabled the zoom bar always behaves ... as a zoom bar, and the proximity sensor seems to be ignored by TLP even though it functions fine during calls (and I've tested this).

I posted about it in a new thread but I was recommended by the author to repost here :) I'm going to try some other ROMs tonight to see if it's a ROM-related issue, but has anybody else who's had these problems - and solved them - got any advice for me?

Cheers

Chris
[Touch Diamond, MDA Compact IV Themes and Apps] Huthus:
Thanks for the answer! So I'll try one of the other advices, but great app anyway! :)

I have the TP2 too and unlock it with the zoombar. Works good! Currently I'm using Jackos new S3 ROM, so how can I help?

In options I activated only "use nav sensor" and "use zoombar", not the other two lines.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Previous answer says that the Zoombar works with Jackos new S3 ROM. For the Proximity sensor to react, it must be enabled. This is a bit tricky to configure, I must admit.

Debug logging could help if it is a configuration error.

You can enable LogDebug in the Others Settings screen, reproduce the scenario (trying to use the sensors) and post the log file TouchLockPro.log.txt in the root of your phone memory as zipped attachment. Maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] yesod7:
Touch Pro 2 unlocks in belt holster

I LOVE this lock!! I only need one little tweak, and it will be perfect for me! My only thing is this: when I put it into my belt holster, it unlocks. I have tried a number of different setting combinations, and double-checked the settings in the registry, but I can't get it to stop this behavior. PLEASE HELP!:confused::confused::confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
If you can reproduce it, you can enable debug logging, reproduce the scenario and post the debug log file TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] yesod7:
Debug Log

Yesterday, it wouldn't lock at all. It would come on, show the battclock, but even when I pressed "Lock" in the TLP Home Screen, it wouldn't lock. I tried resetting to default settings, I tried uninstalling and reinstalling.:confused::confused::confused:

I attached the log file; hopefully it will help! Thanks for the quick reply!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
One known issue is that when the phone starts after boot, you must touch the touchscreen, before TouchLockPro is started (so within 60 seconds). Otherwise it cannot lock correctly.

In the debug logging I see it did not lock, because the Stylus was out.

2011-03-17 07:25:16 1783781910 SetLocked cancelled, stylus out

Was the Stylus out?
[Touch Diamond, MDA Compact IV Themes and Apps] yesod7:
I don't think the stylus was out, but since I'm not sure, I'm posting another log file. I rebooted the phone, made sure to touch the screen every 15 seconds or so before TLP started, and when it started, I started the debug log; tried to lock it, didn't work.
[Touch Diamond, MDA Compact IV Themes and Apps] yesod7:
Problem solved!

I think I've got it taken care of; it seems like my keyboard/slider sensor is twitchy. That's the only setting I didn't bother to change (because why would I?)

I turned off the "slider out disables LockMode," and now everything works fine. Thank you for guiding me in the right direction!:D:D:D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good that hear that it now works.

Note that you can also try to clean your Stylus sensor. Take out the battery and try to gently blow away the dust in the Stylus compartment. Maybe that helps too. But disabling the sensor for TouchLockPro also works. But better is to do not have a defect Stylus sensor, otherwise it awakes maybe too often in your pocket/belt. If the cleaning does not work, you can search for the tweak to disable the "screen on" when Stylus is out.
[Touch Diamond, MDA Compact IV Themes and Apps] yesod7:
won't suspend on call ended

I've attached a debug log; near the end, you can see it says "Suspend cancelled, no power on" :confused::confused::confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It has been a while I looked at the code. Apparently some state is preventing the suspend. What do you want to achieve? That the screen goes off and the device gets locked after end call? Probably "!LOCK;!SCREENOFF" is a better combination.
[Touch Diamond, MDA Compact IV Themes and Apps] yesod7:
Thanks! That's perfect! I kept trying lock;suspend, but that wasn't working. lock;screenoff is perfect!:D:D:D
[Touch Diamond, MDA Compact IV Themes and Apps] eddietta:
Hi ZuinigeRijder,

I think this app is great. You're not working on it anymore? I like this app very much, however when its run on my Topaz, its a bit laggy when trying to config.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am not planning any updates, because it has proven to be stable for a long time, I also use it daily. I know the configuration can be slower, but this is due to the configuration screens is done in .NET. The TouchLockPro exe is written in C++ and is optimized for speed and size.
[Touch Diamond, MDA Compact IV Themes and Apps] eddietta:
So now I see why its that slow with the configuration.. This is a bit off topic but you've replied here so I just want to ask you a small question :p

I want to run 2 versions of the battclock (3.5.2 and 2.0.1) however, every time I try to enable 1 version, the other version will be disabled first, so I can not use them at the same time.

Can you show me how to make both of them work please? I use the zip for 3.5.2 and install cab file for 2.0.1

Thank you very much!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately they cannot be used at the same time, because they reuse the same program name for seeing if it is active. You can use BattClock and TouchLockPro together, at the same time.

The number of possibilities in BattClock are already numerous, so I am wondering if you can show even more info than with one battclock is possible?
[Touch Diamond, MDA Compact IV Themes and Apps] eddietta:
Yep. So what you meant in the homepage is I can only use one Battclock at a time rite?

Maybe you can upgrade Battclock in TouchLockPro?

Edit: I use 2 versions because I want to show info at 2 different places :p
[Touch Diamond, MDA Compact IV Themes and Apps] htcfredde:
Hi

This seems like its the solution i need :) Looks like a really nice application.

Have tried to configured this application to work with my bluetoothheadset and hd2.

Activated the promixity sensor to prevent that the touchscreen make a mess while i have it in my pocket during calls. Seems to work until i get a call, then the screen gets activated and doesnt go back although i cover the sensor. Maybe this isnt the ultimate setting for using headset?

If you would help me with the ultimate settings to get it to work with my bluetooth headset, I would be very grateful.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
With BattClock you have the possibility to specify 6 different places :D

Press the Plus sign to configure the next place/BattClock area 1..6 (X, Y, W, H, Rows, Columns).

In total 12 items can be displayed, in 6 different places.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There is a setting:

DetectBluetooth (DetectBluetooth = 1)

With this setting enabled, you can keep the phone locked when Bluetooth radio is on, do not unlock by light sensor and do not execute TAPI commands. By default this setting is disabled, if you want the bluetooth detection, enable this setting.

This means that you can then only answer via the bluetooth headset button. However, some bluetooth headsets behave differently and when the send a key press instead of a pick up, it is possible the bluetooth generated keypress is blocked by TouchLockPro. If that is the case, this setup will not work for you.
[Touch Diamond, MDA Compact IV Themes and Apps] htcfredde:
The answeringbutton on the headset dont seems to work with these settings :(
[Touch Diamond, MDA Compact IV Themes and Apps] eddietta:
Thanks very much! Now I got it!

In TouchLockPro for Topaz, can I use the nav sensor and how? I couldnt figure it out.. :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can check which keypresses are blocked by TouchLockPro, by enabling debug logging, reproduce the scenario and post the log file.

With a bit of luck, it is a keypress which is not a normal answer/reject key. If not, then it is more difficult to use bluetooth.

This setting makes it possible to answer with the bluetooth answer button with newer HTC devices, like HD2. So this is also which you can try.

HTCLockAPIWhenBluetoothActive (HTCLockAPIWhenBluetoothActive = 1)

With this setting enabled, the HTCLockAPI = 1 is used when bluetooth is active and there is a call. With this setting it is possible to answer with bluetooth keys. Note that if you do not have a phone which supports the HTCLockAPI, do not pick up the phone with the bluetooth answer key or do not want this behaviour, you must *NOT* enable this setting.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
As written here:

http://touchlockpro.sourceforge.net/TouchLockProFree.html#1.4

The following sensors are supported on Topaz:

5 = Diamond 2 (XDA Topaz), Sensors: Light Sensor, GSensor, Stylus Sensor, ZoomBar

So the ZoomBar is working, not the nav sensor.
[Touch Diamond, MDA Compact IV Themes and Apps] makix13:
a question and a request

Hi ZuinigeRijder,

First of all, "incredible and amazing app", for me it's a must have app.

I've got a little issue when a I finished a phone call.

My settings are :

TAPI->

Use TAPI

Keys Only

Light

HTCLockAPIWhenBluetoothActive

Incoming !LOCKSCREEN;

Ended !LOCKSCREEN;!HOME;

When I receive a call, everything goes OK, the screen locks.

I answer the phone sliding the bar, but when I need to end the call, I press the red key on my topaz for end the call, the screen is still locked and the red button on the screen goes disable but the call is still alive.

So with my configuration it's necessary to unlock the device to end the call (pressing the red button on screen not the red key). It would be nice if the red key ended the call (in fact the red button on screen goes disable) although the TAPI option "Keys Only" is checked.

Would it be possible to add another option in TAPI section?. For me, it would be great if you can add another option Outgoing, like Incoming, Established and Ended, to be able to lock the screen when I make a call for example

Anyway i'm very happy with your tool and I recommend it to everybody

Kind Regards for you, your work and your effort.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You could configure a command when a call is connected, e.g.:

Connected (CommandCallConnected = !UNLOCK)

So then the phone will be unlocked, when you answer a call. However, I do not know how it works, when over time the screen goes off.
[Touch Diamond, MDA Compact IV Themes and Apps] jb789:
Should !UNLOCK have quotes around it like "!UNLOCK" when entered into the TAPI GUI?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, it should not have quotes around it.
[Touch Diamond, MDA Compact IV Themes and Apps] jb789:
OK, but now I don't understand your settings description:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You only need to do that when you have a command with parameters. A built-in command does not have parameters, so then you do not need to surround them. I think the documentation is not clear, as well as the example :( I will improve this in my next document update.