yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ephestione:
hehe, you're understanding it in quite a complex way :D

And it was my fault for not making it clear enough... I actually like how in the call screen the proximity sensor is activated by my ear, I want to keep that... I just would like touchlockpro to have a setting to put the phone in standby with proximity sensor only IF the device is locked. Touchlockpro shouldn't check the proximity status at all when the device is not locked.

As I said it's for when buttons get pressed when the phone is in the pocket, I'd like the proximity to immediately put the phone back to standby and shut off the display.

In other words, if we have to make the parallel with exidler's program, checking http://xdaforums.com/showpost.php?p=5471076&postcount=1 I would like your touchlockpro to also have an option like:

"ActiveOnlyIfLocked = dword:0 - Activate Proximity sensor only if Phone locked." ;)

I hope I was clear enough this time

EDIT: Wait, maybe I'm getting the hang of it, don't reply to my post yet :D Will report in here ASAP

EDIT2: Played with it a little, didn't understand where to put "!PROXIMITYDISABLE", but I cleared the value from "Not Near". Strange behaviour, after that I can't unlock the deivce anymore, since it won't recognize my touches on the unlock slider. Then I put !UNLOCK back on "Not near" and the unlock slider worked again.

Overall, this is what happened: I tried putting !PROXIMITYDISABLE on "Near", and it seemed not to be locked when the device was already "active" (like I wanted), then I pressed the power button to lock the device, and put a finger on the proximity sensor to simulate the phone being in the pocket, and I repeatedly pressed buttons, for several times the program turned the screen off immediately, but then after some time the proximity sensor wasn't reposnding, the screen stayed on, and I couldn't unlock it with the slider, had to manually reset

EDIT3: headaches. turns out I was using a not so updated version, the *.5, I just installed the *.8 which in the changelog says has a fix for proximity... well, tested it with my previous settings and the phone "died", that is the screen was off, I pressed the power button and the buttons lighted up but the screen was always off, had to manually reset again :D I am not a guy suited for testing as I get tored pretty soon, so for now I will be using only BattClock. But I will try and send here some other guys that are active on exidler's thread, they should be more than happy to participate in the development of an actively updated utility :D
[Touch Diamond, MDA Compact IV Themes and Apps] sumflipnol:
Here are the debug logs.

I hope you can solve this for me. I really like unlocking via the Volume Down + Volume Up key sequence.:o

Thank you!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see the following keys hooked in the logging:

2010-04-13 19:23:15 501028250 LLKeyboardHookCallbackFunction hooked: 114

2010-04-13 19:23:15 501028250 LLKeyboardHookCallbackFunction hooked: 237

2010-04-13 19:23:16 501028250 LLKeyboardHookCallbackFunction hooked: 91

2010-04-13 19:23:16 501028250 LLKeyboardHookCallbackFunction hooked: 92

2010-04-13 19:23:18 501028250 LLKeyboardHookCallbackFunction hooked: 133

And there is one key unhooked:

2010-04-13 19:23:16 501028250 LLKeyboardHookCallbackFunction unlocked: 117

According to Microsoft, the numbers for the keys I know:

91 = Home: VK_THOME = 0x5B

114 = Talk: VK_TTALK = 0x72

117 = VolumeUp: VK_TVOLUMEUP, 0x75

According to this page of Microsoft there are other key codes, but I cannot guess which one it is, because I do not know which key you pressed when :rolleyes:

My first guess would be 92.....

And of course, you can configure another key unlock sequence.
[Touch Diamond, MDA Compact IV Themes and Apps] sumflipnol:
You'll find this weird: I did some tests with combinations of the hooked keys for the HD2:

91 = Start

92 = Back

114 = Volume Up

133 = End/Power -- Doesn't work well since it's the Power button.

237 = Talk/Send

So for HD2 users who want to use a hardware key lock sequence, these are the key codes for our devices.

*117 can be either the Home or the Volume Down. Since it's unhooked, I can't test it.

*The order I pressed the keys during the Log Debug was: Volume Down, Volume Up, Talk/Send, Home, Start, Back, End/Power.

My new unlock sequence is now 91,92. Thank you very much for the help!:):)
[Touch Diamond, MDA Compact IV Themes and Apps] elgar:
I am trying this app for a few days already. Still can't understand how to disable proximity sensor when the phone is unlocked (the sensor is too close to the Start menu). Especially it is annoying when in landscape mode (almost not possible to use the device, as it keeps locking because of my left hand over the proximity sensor).

Anyone figured it out? Thanks a lot for any help.
[Touch Diamond, MDA Compact IV Themes and Apps] ephestione:
+1 on the request ;)

I tried several configs, including the addition of !PROXIMITYDISABLE into "Near", but had incostant results
[Touch Diamond, MDA Compact IV Themes and Apps] elgar:
same with me. Kinda strange. This app should be quite flexible if you look at the settings.
[Touch Diamond, MDA Compact IV Themes and Apps] kulek:
Settings for I8000

Hi. Very nice program, but have wrong initial settings for I8000.

With G-sensor enabled and call in progress, screen light on and off. To solve this change Tapi/InCallTweak to 0.

Second problem is Proximity sensor, when is enabled the phone is not ringing on the pocket. When phone is sleep, in bag or something and call is incoming, phone try to ring, but Proximity Sensor make it sleep again. To solve - change Near parameter to !LOCKSCREEN. The phone will be calling when something is near the screen. I lost a lot of incoming calls before I realized what going on =]
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparently the !PROXIMITYDISABLE does not work. Can you enable debug logging, reproduce the scenario, note the exact time when it does not work and post the debug log file in the root of the phone memory \TouchLockPro.log.txt

Do you also want the Proximity disabled, when in a call?
[Touch Diamond, MDA Compact IV Themes and Apps] elgar:
Basically, what I want is when I unlock the phone manually, I want the proximity sensor to stop working (so that I can use the device without sending it to sleep, accidentally triggering the proximity sensor. But when the phone rings, I want the default windows behavior (for the sensor to work).

When I send the phone to sleep, I want the sensor to start working again.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I understand. That should already be the case with the default settings. But apparently it does not work as expected. Because I do not have a Proximity sensor to experiment with, can you post a debug log file with the default settings and reproduce the scenario.
[Touch Diamond, MDA Compact IV Themes and Apps] elgar:
Ok, I'll try that
[Touch Diamond, MDA Compact IV Themes and Apps] kulek:
Try this:

Near !LOCKSCREEN

Not Near !UNLOCK

Lock !PROXIMITYACCEPT

Unlock Call !PROXIMITYIGNORE

Unlock No Call !PROXIMITYIGNORE;!PROXIMITYDISABLE
[Touch Diamond, MDA Compact IV Themes and Apps] Rayy:
Sourceforge is down..

Any mirrors for latest version?

@thx for this app! Have been using it for quite awhile ^__^
[Touch Diamond, MDA Compact IV Themes and Apps] sumflipnol:
ZuinigeRijder--

Alright, so I changed ROMs and the unlock sequence no longer works... Those 'hook' entries in the log don't exist, either!:eek:

Would you know what the issue is?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparently the keyboard hook did not succeed, because there is already another program using the Keyboard hook? There can be only one keyboard hook in the system.

010-04-18 00:11:24 -73961470 KBHook(true)

2010-04-18 00:11:24 -73961470 KBHook: KB SetWindowsHookEx

2010-04-18 00:11:24 -73961470 KBHook: Could not create Keyboard Hook

Did you have other programs installed, which could uses a keyboard hook?
[Touch Diamond, MDA Compact IV Themes and Apps] sumflipnol:
Not that I know of. I installed the same programs as I did with my previous ROM. Since I'm using a completely different ROM now (from a different chef), I'll ask if the chef cooked in anything that might be using a keyboard hook.

Thanks for the response!
[Touch Diamond, MDA Compact IV Themes and Apps] igal_f:
IncallTweak

Hi,

In my phone bluetooth is on all the time.

So, i don't need to turn bluetooth on when i get into my car and the connection to headset is immediate.

can you, please, set an option to turn incalltweak on/off with no exceptions

and with another option depending on Ac power or bluetooth set it off/on.

Thank's.
[Touch Diamond, MDA Compact IV Themes and Apps] padvou:
Greek translation

Nice work, thank you for your efforts.

A small contribution: I added greek language translation to the excel spreadsheet.

Bye!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks. I will include it in the next update.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You mean, you want an option of no InCallTweak when on AC power or bluetooth active?
[Touch Diamond, MDA Compact IV Themes and Apps] igal_f:
No, i mean that i want InCallTweak on even if bluetooth is on because i keep my bluetooth on all the time.
[Touch Diamond, MDA Compact IV Themes and Apps] mafesama1:
Irregular behavior....

I don´t quite understand it, but the behavior of TouchLockPro is irregular.

Sometimes works well, other times it does not.

HD2

SO 5.2.21869

Manila 2.5.19211619.0

ROM 1.48.412.2 (71294) ESN

And I think perhaps the instructions are to be modified...

When you say, for example, "unlock on light sensor" I think you mean

"allow unlocking on light sensor", AS THE CLOCK WILL NOT UNLOCK ON SENSING LIGHT but will allow you to slide so as to unlock if light is sensed above a given threshold...Isn´t it?

Thank you.
[Touch Diamond, MDA Compact IV Themes and Apps] wez89:
Amazing work thanks, the lite application i needed for locking the device

i have it set up perfect, only way of unlocking is to turn the screen upside down and back again
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Hi,

which standby is this, when i press the startmenu-button "ZZ" (TLP Toggle)? The same like i press Hardware-Power-Button on HD2?

If i use a gps-app and i press Hardware-Power-Button, GPS-Fix gets lost. If device goes into standby after timeout (e.g. windows-mobile device-lock), then GPS-Fix is still alive.

What function is TLP Toggle?
[Touch Diamond, MDA Compact IV Themes and Apps] neverland13:
I found i small bug:

when i restart my phone (htc Tytn ii/ att tilt) if the phone goes to sleep for less than 2 min TouchLockPro is not working - it stop locking the screen. If i keep alive the phone for more than 2 min everything works perfect.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will add it on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you be more specific what is not always working? Which settings/sensors? Or is it not always locking?

No, actually it should unlock by the light sensor, when there is enough light for the configured period of time.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It executes the !TOGGLELOCK command, dependent on the lock status:

unlock/backlight on OR locksuspend

So the device will go into a deep sleep when it is not prevented by another program.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro waits 60 seconds before really starting. This gives you time to enter you SIM pin when you have configured it. And yes, you need to wait till the BattClock is visible, before powering down the phone, otherwise it may not lock correctly (although the battclock indicates it is locked).

On my phone, if I do not enter the SIM pin before TouchLockPro is started, it does also not always lock correct thereafter. I need to do a soft reset then.
[Touch Diamond, MDA Compact IV Themes and Apps] 71Cuda:
Was there ever a solution for this? I tried what you suggested in a subsequent post (i.e. CmdUnlockCall ="!PROXIMITYACCEPT" or blank and CmdLock = "!PROXIMITYACCEPT;!LOCKSUSPEND"), but it didn't fix the issue.

First, let me say that I absolutely love TLP and it is NEARLY a perfect locking solution for me, with the exception of the above issue. That one issue makes it unusable for me. I will describe more specifically what is happening for me...

As paalkr reported, the proximity sensor makes the screen turn off when you put the phone to your hear on the in-call screen - the first time. When I take the phone away from my ear, the screen turns back on - as designed normal behavior. But then as soon as the screen turns back on, TLP locks the device (with the screen on). It then quickly unlocks the screen because there is nothing covering the proximity sensor. At that point, the proximity sensor no longer responds and the screen does not go off when I put the phone back to my ear. This is basically exactly what paalkr reported, only I added the details about TLP locking and unlocking the device on the first removal from the ear because that's what seems to trigger the fault. I have also tested this functionality with my phone plugged into the USB cable to my computer - and the PS continues to function correctly throughout the call. TLP does not lock the screen when I pull the device away from my ear (I have UnlockOnACPower checked - although I don't know if this affects this particular function).

I am using a TMOUS HD2 and have all of the PS settings in TLP as the default (although I've tested a lot of other combinations without success).

I've attached Debug Logs, but I'm not sure I did everything right (I'm not experienced with debug logging). For the unplugged with error rile, I placed two calls. The first call acted different than usual, with the phone locking while by my ear (I could tell be cause I have it set to vibrate on lock and unlock). The screen then didn't come on when I pulled the phone away. The second call acted like described above. I then created a new file with the phone plugged in, where I placed a call and the screen acted as desired with no locking/unlocking by TLP.

I hope this helps and you can help. Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] mikefaliro:
hello,

i use touchlock pro and i am facing a curius problem!!!when i istalled it, it worked properly but someday i press the "power" button and the screen wasnt locked!!!

it was always locked when i pressed it and i used to use the combination of the decrease/increase volume to unlock both screen and buttons...!!i reistalled the programm but it didnt make any diference and i cant understand what happend...

any help pleeeasse???;)

thanks !!!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you install other programs or switch to another ROM? Because if another program is using the same locking method, it is indeed possible TouchLockPro cannot lock.

In my case, I always need to enter my SIM pin first and make sure TouchLockPro is started (after 60 seconds), before I power off my phone after boot/soft-reset. Otherwise it will also not lock always.

You can enable debug logging and post the debug log file, maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the detailed explanation. That really helps in trying to solve the issue. Unfortunately I do not have a phone with a Proximity sensor, so I can only look at the debug log files and the findings.

A question. Is the problem also there when you are already connected to a call?

In the logging I do not see any call (incoming and outgoing), so I am wondering if the problem is only when there is no call? Because normally TouchLockPro will not lock when in a call :confused:

And because you talk about connected, it looks like the debug log files are not the correct ones? Hmmmm.

I see you did configure not to use TAPI:

010-05-08 01:18:10 993073402 GetSetRegValue(): UseTAPI

2010-05-08 01:18:10 993073402 ==DEFAULT VALUE====: 1

2010-05-08 01:18:10 993073402 ==OVERRULED VALUE==: 0

So this means that the Proximity is done as default, so without being aware of in or out a call.
[Touch Diamond, MDA Compact IV Themes and Apps] 71Cuda:
It happens the first time I put the phone to my ear and take it away during any part of the calling process, whether it is dialing, ringing, or the call has already been answered. I did some more testing. It seem's the phone recognizes that a call is active whenther it is dialing, ringing, or connected and uses the proximity sensor to turn the screen off when proximity is sensed. It is when the screen comes back on that TLP locks and then unlocks the screen - again regardless of the stage of the call. If I end the call and then place another call, the proximity works again once before it's somehow disabled by TLP locking and unlocking. So it seems that TLP locking and unlocking deactivates the HTC's in-call use of the proximity sensor for turning off the screen just for the remainder of the call.

As I said, I'm not experienced with debug logging. So if I sent the wrong ones and you can explain to me how to obtain correct ones, I will try again.

It seems that something about the screen turning back on is triggering TLP to lock the screen. If I could somehow figure out how to stop that behavior, I think the problem would be fixed. Again, it doesn't have this behavior when the phone is plugged in to power - only when unplugged.

Thanks again for your help.
[Touch Diamond, MDA Compact IV Themes and Apps] vico2004:
Hello, I think TLP has problems with WKtask(task manager).

Especially with Nav sensor.

Can someone recheck this?
[Touch Diamond, MDA Compact IV Themes and Apps] mikefaliro:
i think that i have found what was going wrong!!!when i swiched on my phone after loading windows i didnt enter my SIM pin for about 10min and i understand that this was my fault ;)!!!now that i enter the SIM pin on time everything works properly ;)

thanks a lot tochlockpro is just great!!!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, in the debug log I see you have configured NOT to use TAPI:

2010-05-08 00:49:03 1540488530 GetSetRegValue(): UseTAPI

2010-05-08 00:49:03 1540488530 ==DEFAULT VALUE====: 1

2010-05-08 00:49:03 1540488530 ==OVERRULED VALUE==: 0

And you have configured to disable the proximity sensor when unlocking when no call is active:

CmdUnlockNoCall: !PROXIMITYIGNORE;!PROXIMITYDISABLE

Normally, I would expect you would configure to use TAPI and then the other unlock would be executed:

CmdUnlockCall: !PROXIMITYIGNORE

Is there a special reason you did disable TAPI?
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
I have the same problem like 71Cuda but i have useTAPI=1 and the rest of settings same like 71Cuda.
[Touch Diamond, MDA Compact IV Themes and Apps] 71Cuda:
Frankly, I disabled TAPI because I had no clue what it was. I was trying to simplify the usage as much as possible and I figure if I didn't know what it was, then I probably didn't need it. So what is it exactly? What settings should I be using in TAPI?

I've tried it with TAPI enabled and it does change the behavior a bit. It has definitely helped, but I still got the lock and unlock problem a couple of times. I'll do some more testing to determine patterns and look for consistent behavior and I'll report back what I find.

I have done one little test and this is something interesting I noticed. TLP seems to be behaving properly now while the call is connected, but still has the same issue when the in-call screen is active and the call is not connected. For example, if I dial a number and cover the sensor, the screen turns off. If I uncover it before the call connects, the screen comes on, TLP locks, unlocks, then the screen won't turn off again with proximity. This is a bit annoying but not a big issue because I don't often need to pull the phone away before it connects - maybe only just to check if I dialed the correct number. It's usually an issue after connection when I need to use the keypad to join conference calls or interact with an automated system. So if it works consistenly as it did in my recent test, its useable. But I think (not sure) it has locked once or twice while in a call since I enabled TAPI. So I need more testing
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The TAPI indeeds detects your call status and influences which unlock command to use:

CmdUnlockNoCall: !PROXIMITYIGNORE;!PROXIMITYDISABLE

CmdUnlockCall: !PROXIMITYIGNORE

So actually, always the first one was executed, so when unlocking the proximity sensor was disabled.

There is still a problem, when you are placing a call yourself, it may not be connected yet and if put to your ear it will also lock and disable the Proximity sensor.

Of course you can change the command to unlock if no call is active to:

CmdUnlockNoCall: !PROXIMITYIGNORE

But then it may also make your screen off when your finger is in the neighbourhood of the sensor (e.g. using Start Menu).

I do not have a good solution (yet) to prevent the ProximityDisable when you are actually start calling someone else. Make you could couple a GSENSOR move to enable the Proximity sensor via !PROXIMIYENABLE :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] thierry2064:
Hello,

I used Battlock before and liked it, I am now testing TouchLockPro. One feature would be nice : to have a larger sign showing that the phone is locked, so that you do not uselessly try something before unclocking (change background color, invert colors, background picture...). Would this be possible ?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro reverts the foreground and background color when the phone is locked. But make sure that the BattClock area is not over the TouchLockPro area if you use both.
[Touch Diamond, MDA Compact IV Themes and Apps] bluezor:
Thanks

Thanks for the great program! :p

Locks well so I don't need the pin now.
[Touch Diamond, MDA Compact IV Themes and Apps] worwig:
I have a request.

What would it take to read a column of pixels, say a column just to the left of the first column, or even the first hidden column if possible. Then spread that single column out for the entire width of the clock display for the background.

I have a color gradient and the clock looks odd with the a solid color background. If TouchlockPro read the color, then spread that out under the clock, it would look much better.

Thanks for the great program BTW.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can specify a background image which exactly matches your taskbar.

In the newest BattClock it is possible to specify a pixel to be used as background. See Detect Background.

It also has the possibility to use a gradient color, see G (ClockBackgroundRight = ClockBackGround)

But then I have to incorporate these changes into TouchLockPro. Something I was planning to do anyway. But I am first concentrating on adding more possibilities to BattClock and improving there, before including it in TouchLockPro.
[Touch Diamond, MDA Compact IV Themes and Apps] worwig:
A gradient color would be nice. A row of pixels would be better. :D

Thanks.