yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, the theory works, which is proved by this:

The problem is, that if you do this in one command:

"\Program Files\TouchLockPro\TouchLockAction.exe" EnableLockTouchPanelOnly LockScreen DisableLockTouchPanelOnly

There is no synchronization between TouchLockAction and TouchLockPro. So the registry settings have been changed already by TouchLockAction, while TouchLockPro is executing LockScreen :mad: So there must be some handshake between TouchLockAction and TouchLockPro, to achieve what you want. A pause/sleep in between the commands would also help, but there is no guarantee that TouchLockPro is already ready.

I will think about a handshake possibility, because a sleep is not a nice design.
[Touch Diamond, MDA Compact IV Themes and Apps] oruam57:
I do not know the architecture of your program but I suppose that actions requested using HKCU\Software\ZuinigeRijder\ActionSettings are executed immediately by TouchLockPro.exe without interaction with TouchLockAction.exe. In that case maybe the sequence "EnableLockTouchPanelOnly LockScreen DisableLockTouchPanelOnly" would work as expected. This would only require the capability to execute EnableLockTouchPanelOnly and DisableLockTouchPanelOnly by values under HKCU\Software\ZuinigeRijder\ActionSettings (or a single value to execute the combination of the 3 actions).
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi,

Seems to me it's possible to change the behaviour of the buttons (using AD Button +), so perhaps it will be possible to turn them off during incoming call and back on once call answerd/end ?

I don't know what HTC developers are thinking, but to me it's kind of non sense to have a "slide to answer" solution and at the same time activated answer/end buttons.

I've never been able to get LightSensor to unlock the phone, neither on incomming call nor with screen ON button.

BR
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Here is the log file.

Hope you can help to fix ths light sensor not working on my HD with TLP 2.5.4

Registry : HKCU\ControlPanel\Backlight\AutoSensor = 1(DWORD decimal)

In TLP settings the light value is moving while passing the finger above the sensor.

BR
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see that you did lock via the Stylus Out/In method.

19:38:26 -1941727118 NotificationStylusOutIn()

When the lock is triggered by yourself, like the Stylus OUT/IN, it will not unlock on light sensor. It will only unlock by light sensor, when there is a power on, without being locked by yourself.

If you press the Power button to just let the device go to suspend and later the device is awakened, it will lock automatically and then it will unlock by the light sensor.

See also this post. explaining this use case.

You did disable AutoLockOnPowerOn, why?
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
there is definitivelly something I don't understand...

If I want the phone to unlock when I turn ON the screen or receive a call I've to disable the Stylus option ?

When I press the Power button, the screen turn off but the device doesn't suspend (lock), even with the lockOnPowerON activated, because to have the phone available I must have the stylus OUT.

With stylus IN, the device is corectlly locked when I power ON.

Why do you diferentiate the two ways of locking the device ?

Why cannot we have both ?

I would like to be able to have the device lock/unlocked with the stylus, and also with the power button, but for the later only unlocked when there is enough light to avoid unwanted pocket actions.

When I receive a call, the phone is in the pocket, the screen turn ON, but the device stay locked until I take the device outside of my pocket.

If there is not enough light, I use the stylus to unlock.

Then, at the end, I've the choice to losck/suspend with Power button or stylus.

Would be perfect for me.

Will also solve the problem of device unlocked when I make/receive a BT call in my car.

I'll also love to use my device with finger when I press the power ON button just to quickly check something without to have to release the stylus.

I've not enabled the AutoLockOnPowerOn because of that.

As I always use the stylus to lock/unlock it's totally useless for me.

BR
[Touch Diamond, MDA Compact IV Themes and Apps] paalkr:
Hi!

First of all I would like to say thank you for a great application. Second I would like to know if there are any news on the possibility to unlock the Diamond2 by using the zoom bar? This would be like a hardware slide to unlock action, that I think would be really great.

regards,

PK
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
As stated in this post, I do not have a foreground window, so that is not possible, unfortunately.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Most of the Touch HD (as I know of), just use the default settings, so lock on power on and let the phone unlock by the light sensor. This is in most of the cases ok, only in dark conditions this will not work. Then they fallback to the GSensor (configure an easier unlock sequence than the default one) or Stylus out.

If you use Bluetooth, you can just pick up the phone with bluetooth, without unlocking.

You approach/preference is different. The Stylus locking is also used in other situations (maybe not by you), so you can lock the device (e.g. GPS) and do not want to unlock by the light sensor. So that is the reason from TouchLockPro perspective.

Probably people having a Touch HD should react how they use TouchLockPro.
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
HI. I have installed the last update and ma very happy with it (especially the bluetooth option). There is still one problem/bug afflicting me and a few minor suggestions I like to report below and I hope you will have time to implement in one of your future releases.

Problem/Bug:

In the TAPI options if I place a checkmark on UnlockWhenConnected it doesnot execute anymore the CommandCallXxxx commands. Is there a reason why it is not allowed to have both? I would like the phone to unlock on incoming calls (because there is already another slide to unlock mechanism), to lock again if I missed the call and to stay unlocked during the call. This is very important because otherwise it is a nightmare to use the keyboard or just close the call. What happens (if UnlockWhenConnected is not checked) is that upon taking the phone to the hear the screen goes off and the phone gets locked. Then I need to turn it on and unlock it before I can use the keyboard or the keys again. Would it be possible to have both options working at the same time?

Other improvements:

1. It would be nice if it was possible to filter what the capacitive nav sensor reacts to while locked. I have assigend some commands to the various sweep actions but those are accidentaly triggered while the device is locked. I would like to be able to set an option to not react to anything but the !UNLOCK command while locked. Best would be to have a cechbox for each sweep setting allowing to enabel or disable that command when locked. That would allow me to implement sweaps to unlock or turn off the screen while locked but disable other commands.

2. Would it be possible to implement actions as well for the the left, middle and right touch?

3. Would it be possible to mantain the poweroff button (on the top left of the Touch Pro) active also when locked? I would like to not have to unlock to turn the device or the screen off.

Thanks a lot for a fantastic utility.
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
"The Stylus locking is also used in other situations (maybe not by you), so you can lock the device (e.g. GPS) and do not want to unlock by the light sensor. So that is the reason from TouchLockPro perspective."

Okay, that's why I suggest to unlock by light sensor only on incoming call and power ON ;-)

Perhaps a new TAPI action like !LIGHTUNLOCK could be a solution that could made everybody happy :-)

And a new "Force unlock on power ON" option under Light sensor settings could also do the trick and provide full flexibility to fulfill all purpose.

"If you use Bluetooth, you can just pick up the phone with bluetooth, without unlocking."

Yes, but as you know the BT as it's implemented today doesn't fulfill my needs as I've BT always ON.

BR and thanks for this nice tool :-D
[Touch Diamond, MDA Compact IV Themes and Apps] stefanjadex:
Hi Zuininge,

I started using your program. It's very good, congratulations.

I have an ideea for you: could you add schedule options?

The point is like this: (by example) during the night in the dark the light sensor is not working, to take out the stylus is unhandy, to use the g-sensor take some time... And of course there also another examples.

Why not let us disable the TLP on some predefined time schedule.

Best regards and kep it working.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In your case I would expect you disable/uncheck DetectBluetooth (till I have figured out if I can detect bluetooth connection). I suppose you will have the phone in your pocket, and you can just pick up the phone with Bluetooth. And when you take the phone out of your pocket, it will unlock by the light sensor, also with bluetooth radio on. Or am I missing something :confused:

I ask myself, why I disable unlocking by light sensor when bluetooth is on. Because then it will be in the pocket and will not sense light anyway. So DetectBluetooth should maybe only not execute the TAPI commands :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can still have missed calls then, when you are in the evening. So the added value does not seem to be big. I know this problem is only there for Touch HD and Touch Diamond2, because these do not have the capacitive sensor.

I think a better approach would be to have the DredSensor approach for locking the hardware keys and unlock by detecting middle button press. So there is another unlocking method added. I do not know if DredSensor is working on the Touch HD?

Can people check/confirm that DredSensor approach is working on Touch HD and Touch Diamond2? If yes, this would be a good unlocking addition:

* first lock with the current approaches

* make sure to subclass the foreground window and catch hardware keys with dredsensor approach

* unlock the hardware keys with the current approach, so you can unlock by middle button and also the power button can be used when locked
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, according to the source code it should unlock when connected, and it executes the CommandCallConnected command. Both, unless bluetooth radio is on. Can you post a debug log file and reproduce the scenario, so maybe that gives me a clue :confused:

Good suggestion, I will put it on the wish list. Actually, you can then double the capacitive swipe commands possibilities, when locked and when unlocked.

In principle this will not be difficult. But those commands will also be triggered when pressing the hardware keys. So I do not know if this is really practical.

See my response of the previous post, about the DredSensor approach. That would make it possible to unlock the power button.....still locking the other keys.
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
In fact what I dream of is rather simple.

Lock/unlock(suspend too) with stylus (it's working perfectly actually)

Unlock when power ON or incoming call

only

when there is enough light.

That's all :-)

That way, I can use the stylus like today, or, press ON and use my fingers.

On incoming calls with my phone in the pocket, it won't unlock because there won't be enough light, that should solve the unlock during calls through BT in my car.

But, when I take the phone out of my pocket, the phone will be ON after a while and it will unlock automatically because of light. That will also prevent the issue of pressing buttons while taking out the phone from the pocket.
[Touch Diamond, MDA Compact IV Themes and Apps] MacCool:
Great program! Thanks!

I have a question though.

Is there a setting to only unlock the screen during an incoming call (eg keep keys locked)? Because there is a slide to answer function with the HD.

If that is not possible yet, would it be difficult to implement this?
[Touch Diamond, MDA Compact IV Themes and Apps] Die Bruine:
Zuinigerijder,

Sunday I bought a Diamond and installed Shaks v4.2 on it (WM6.1). Sometimes my capactive sensor does not work anymore. I've configured the stylus so I can still work. After a reset it starts working again. Haven't thought of unloading TLP yet. Will try that the next time and post my findings. I did however try to reconfigure it, but that did not help.

BTW, I have never had any problems on my Pro running ROMeOS then, and RRE 6.5 v2.1 now.
[Touch Diamond, MDA Compact IV Themes and Apps] ugumba:
Slide to unlock on touch panel?

Hi! Thanks for a great program - I've used it for 6 months on my HD, but only for the Battclock (which is excellent). On the HD, I'm afraid none of the available unlocking mechanisms are practical enough:

- light sensor is too unreliable

- pulling out the stylus is pointless and time consuming if I don't need it (which I rarely do)

- G-sensor is too unreliable (it very rarely works on the first attempt)

Wish 1: Would you consider adding support for traditional "slide to unlock", i.e. using the normal touch panel? I.e. similar to LockMeLite (I don't want a background image), PocketShield (too slow) and CSDevCtrl (too slow, unreliable). If you added this, TLP would be the only locking program on my HD! :-)

Wish 2: A color coded battery icon (instead of the percentage) beneath the clock would look fantastic. (Much like Ariel battery monitor.)

Wish 3: Please fix unlock on incoming call - I can't get it to work either.

Cheers,

ugumba
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
OK. I am posting the log file but I am getting unstable results. To make sure to not confuse things I have disabled lightsensor unlock and bluetooth unlock. LockonPowerON is enabled. I have setup the TAPI section as follows:

UseTAPI=1

UNlockWhenCOnnected=1

ScreenOffWhenCOnnected=0

LockWhenIncoming=0

DetectBluetooth=0

Incoming=!UNLOCK

Connected=!UNLOCK

Ended=!LOCKSCREEN

Then I run the following 3 tests (not anser, answer, intitiate call and drop) twice:

No answer test (1)

1. Turned the phone off

2. Ring the phone up

2a. The phone wakes up and unlocks. CORRECT

3. The caller hangs up

3a. The phone autolocks. CORRECT

Answer test (1)

1. Turned the phone off

2. Ring the phone up

2a. The phone wakes up and unlocks. CORRECT

3. Answer the call and hangup with the red button

3a. The phone does not lock again. WRONG

4. Power the phone off

Initiate and terminate call (1)

1. Turned the phone off and on. Manually unlock

2. Call a number. The phone goes dark. Turn on by the power button.

2a. The phone is still unlocked. CORRECT

3. Hangup with the red button

3a. The phone does not lock again. WRONG

4. Power the phone off

No answer test (2)

1. Turned the phone off

2. Ring the phone up

2a. The phone wakes up but doesn't unlocks. WRONG

3. The caller hangs up

3a. The phone was already locked. N/A

Answer test (2)

1. Turned the phone off

2. Ring the phone up

2a. The phone wakes up and unlocks. CORRECT

3. Answer the call and hangup with the red button

3a. The phone does not lock again. WRONG (actually it locked but after a long time 5-10 seconds)

4. Power the phone off

Initiate and terminate call (2)

1. Turned the phone off and on. Manually unlock

2. Call a number. The phone goes dark. Turn on by the power button.

2a. The phone is still unlocked. CORRECT

3. Hangup with the red button

3a. The phone does not lock again. WRONG

4. Power the phone off

Brilliant! Even a better solution. I can't wait for it! :-)

I see. I agree that it is not practical if it cannot be differentiated. I thought that G-Scroll could do that, but maybe it uses double tapping as a measure to avoid it. I haven't tried it.

Uhm, I couldn't find the post you refer too. I wouldn't want to install more software on the TouchPro (if that is the solution). I rely on TLP as being very stable and small footprint :-)

Thanks.

Alessandro
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, in the next version I will also unlock on light, when bluetooth is on. Also I will make it possible to configure commands to the different stylus movements (Stylus launcher). For the movements Stylus OUT, IN, OUT-IN and IN-OUT. So you can also configure !LOCKSUSPEND.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is not possible yet. The HTC API I use for locking the hardware keys, also locks the TouchPanel.

However, I am going to try DredSensor approach, like described in this post..

But I do not know if DredSensor is working on Touch HD and Touch Diamond2.

Can people try if it works on those phones? If yes, this is an extra reason to introduce this possibility (if it only works on Diamond or Touch Pro, this is less important). Can people try if DredSensor works?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe this is the famous HTC TF3D bug, that is introduced in the newer HTC ROM's. See also the setting TF3DWorkaround (TF3DWorkaround = 1). When unlocked and you move to another TF3D tab, the capacitive sensor is going to work again. That is why I do a tab left-right, if the phone is still not unlocked after some time and TF3D is the foreground window.

Is maybe this the case :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Sad to hear that the unlocking is not reliable on your Touch HD. You must not move the phone too fast, for letting the GSensor unlock. You can make the unlocking sequence more sensitive, e.g. 43 or even 93, to make it easier to unlock.

Wish 1:

I do not want to go into the route of a foreground window. But I want to try the DredSensor approach. But I do not know if that is working on Touch HD. Can you test if DredSensor works in your Touch HD?

Wish 2:

I know Ariel battery monitor. But currently I am not planning to introduce this one, because there is not enough space. I had the idea to have a stripe, and the length of the stripe is the left battery percentage. And the stripe has a different color, dependent of the amount of battery left. But till now I did not implement this and I do not know if people find this a good idea.

Wish 3:

Can you post a debug log file, where you tried to reproduce the problem. So I can have a look what goes wrong :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I just wanted to test if DredSensor approach works on the Touch HD. After testing it, you can deinstall it again. If it does not work on the Touch HD, I do not have to introduce this approach. Can you test if the DredSensor approach works

1.

8:37:49 -1363647358 PBT_TRANSITION POWER_STATE_SUSPEND

2.

8:38:03 -1363647358 =========================POWER_STATE_ON============================

2a.

8:38:03 -305894406 NOTIFY_CALLSTATUS_INCOMING

8:38:03 -305894406 Execute(): !UNLOCK

3.

8:38:19 -1363647358 SetCallStatus(CALL_ENDED): 1

8:38:19 -1363647358 NotificationCallStatusEnded()

3.a

8:38:19 -305894406 NOTIFY_CALLSTATUS_ENDED

8:38:19 -305894406 Execute(): !LOCKSCREEN

1.

8:38:28 -305894406 POWER_OFF_REQUEST

2.

8:38:52 -305894406 NOTIFY_CALLSTATUS_INCOMING

8:38:52 -305894406 Execute(): !UNLOCK

3.

8:39:01 -305894406 NOTIFY_CALLSTATUS_CONNECTED

8:39:01 -305894406 Execute(): !UNLOCK

3a.

8:39:24 -305894406 Execute(): !LOCKSCREEN

8:39:24 -305894406 LockScreenRequest()

8:39:24 -305894406 ClockWndProc(WM_TIMER): 5

8:39:24 -305894406 LOCK_SCREEN_REQUEST

8:39:24 -305894406 LOCK_SCREEN_REQUEST: nothing to do

This last message, means that TouchLockPro thinks the power is still off:

if (!pS->IsPowerStateOn()) {

LOGDEBUGDETAILED("LOCK_SCREEN_REQUEST: nothing to do");

break; // nothing to do

}

A moment later the power state on is set (too late).

8:39:25 -305894406 SetPowerStateOn(true)

What me puzzles, is that the logging shows the phone is busy with the POWER_ON_REQUEST:

8:39:24 -305894406 POWER_ON_REQUEST

And that is on the same (windows) thread as the lock_screen_request.

That is not possible, to execute 2 things at the same time in the same Thread :confused:

Hmmm, I must think about this one very deep. So I come back on this one and the later logging :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ugumba:
I can appreciate this, and I would not want a *visible* foreground window. If it could be transparent, and allow you to capture a swipe, I think TLP would become the most versatile locking utility available.

I tried configuring DredSensor against Opera on my HD, but as soon as Opera was active, I kept getting "error: couldn't find entry point" messages.
[Touch Diamond, MDA Compact IV Themes and Apps] ddd333ddd333:
Can I download it free? How to do?
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
I'm afraid that won't improve anything in my case.

Stylus is working great for me, I just would like the light unlock on power ON and incoming call, something that's not working today when stylus is used.

BR
[Touch Diamond, MDA Compact IV Themes and Apps] heckmeck:
Actual error and wish for future

Hi!

At present I am testing your great software on a Diamond with AZTOR X2 GER. Basically TouchLockPro works very fine besides one issue: The screen is only really locked if option LockTouchPanelOnly is unchecked. If checked it displays the BattLock icon but screen is NOT locked!?

One feature I am missing really:

Unlocking with central-button

. On the diamond this button can't be pressed unintentionally so from my point of view this would be the best option for unlocking (much better than the capacitive sensor stuff)!

Thanx in advance and please let me know if did something wrong in the settings!
[Touch Diamond, MDA Compact IV Themes and Apps] paalkr:
Hi!

The ZoomBar is not on the touch screen, it's a hardware sensor below the touch screen. I guess that the sensor is in some way comparable with the nav/scroll sensor on the Diamond1.

Regards,

PK
[Touch Diamond, MDA Compact IV Themes and Apps] jbrady33:
how to lock the hardware button - during placed call?

Love your software but have a config question.

What I want to do:

1. Place call (Outgoing - not incoming, using headset & screen), once connected - press power to lock EVERYTHING and put back in case/pocket. Phone should stay locked until case is opened and light sensor kicks in.

2. Place call (Outgoing - not incoming, using headset & voice dialer) without ever unlocking the device or taking out of case. hang-up with headset button.

Problem I am having: The green/red place/hangup hardware buttons are not locked if I initiate the call, so they can hang up the phone if they get pushed. The bluetooth option doesn't help much as the radio is always on.

Settings that migh matter:

LockTouchPanelOnly is NOT checked

UnlockWhenConnected NOT checked

LockWhenIncoming NOT checked

Will adding "!LOCKSUSPEND" command to the Connected line in the Telephone API page lock the hardware buttons also? If it is out of the case would the light sensor unlock then unlock the phone 1 second later, or would I have to push the power button? (I hope I would have to push the power button - I guess I am rambling now, I'll try this)

Thanks

PS: The light sensor lock/unlike is very slick - great job on that.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
So it looks it is *NOT* working on the Touch HD. So a no go :mad:

As far as I know you can have a transparant foreground window, *BUT* the windows below will not be updated on Windows Mobile, so a no go too :eek:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, DredSensor is free. But the previous post indicates it is not working on Touch HD :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I will fix that too.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
If someone donates me a Diamond2, I can figure it out :)

Or someone must give me working code how to do that :rolleyes: