yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Some people reported the ZoomBar was not working, maybe Tilt 2 does not have the ZoomBar software builtin, although the hardware resembles closely Touch Pro 2?

Note that when using HTCLockAPI = 1, the Zoombar is also not working.

QuickStart and Features shows the different phones and the supported features. And also the Touch Pro 2 is listed:

6 = Touch Pro 2 (XDA Rhodium), Sensors: Light Sensor, GSensor, Stylus Sensor, ZoomBar, Proximity Sensor, Keyboard Sensor
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparantly the speedstep technology makes the GetIdleTime report 100% when idle. It makes sense, because the CPU speed is lowered to accomodate only the used processes.

Maybe somewhere theres is a registry key showing the current CPU speed? Because that is then a more reliable predicition of the used CPU?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You did set:

GetSetRegValue(): ProximitySensorTime

2010-02-21 10:42:37 -1553078670 ==DEFAULT VALUE====: 1500

2010-02-21 10:42:37 -1553078670 ==OVERRULED VALUE==: 0

So this means it will no longer detect a proximity change. A previous version it was 900 (milliseconds), so if you want to have the proximity sensor to work, you must set it greater than 0.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately some people have problems with the locking of the keyboard hook and touchpanel hook sometimes. That makes this locking method useless for you.

The only other way is to use HTCLockAPI = 1, but then you loose other functionality, like unlocking via a (secret) key sequence. You can use the GSENSOR moves as (secret) unlocking method. But this is not so comvenient when there is an incoming call and you want to answer quickly. Taking out the Stylus or opening the keyboard slider is an option, but not a real secret.

Because of the reported problems with not locking by keyboard hook and touchpanel hook, maybe TouchLockPro is not the tool you are looking for.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
The field proximity time was empty by default.

Now i set it to "1000". But it worked with "0" in it, too.

But still only screenoff - not going to idle (standby) when device locked, proximity covered and power-button pushed.

How to disable proximity sensor while not locked? I can´t use my HD2 anymore, when in landscape, because i cover proxmity all the time.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Please can you answer my question?

Which command do i have to fill in? I want to go my HD2 to standby, if device is unlocked and i push the power-button while proximity is covered.

Do i have to fill in !IDLE, !SUSPEND or something else?

Is !IDLE and !SUSPEND the same?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
When you want the proximity to be disabled, when getting unlocked by Proximity, you have to fill in:

Not Near (CmdProximityNotNear = "!UNLOCK;!SCREENON;!PROXIMITYDISABLE")

Hmmm. However, if it is unlocked by other means, this will not be executed. Looks like I need to provide a command possibility at LOCK and UNLOCK.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
If you want to disable the proximity sensor, when going to IDLE, you can configure:

Near (CmdProximityNear = "!IDLE;!PROXIMITYDISABLE")

Note that TouchLockPro will enable the proximity sensor again when it is locked.

SUSPEND is a state which will go into a deep sleep earlier than IDLE.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Still only screen off and not going to standby/idle.

Disable proximity sensor while not unlocked also doesn´t work.

EDIT: First time after reboot it works like it should do. But after first lock/unlock it doen´t work anymore.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmm, I think I do not understand fully what the problem is. I cannot test much myself, because I do not have a phone with proximity sensor.

Can you elaborate more on what you want to achieve?

And post a log file with the settings mentioned, so I can have a better understanding what is not working?

Thereafter you can switch back to 2.12.1 while the problem is figured out.

Sorry for the inconvenience.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
I want to have my phone locked while in my bag. If i would accidently push the power-button, then the proximity sensor is still coverd.

--> my phone should not wake up and stay alive with only screen dim

--> i want my phone directly go back to sleep/standby/idle - not only screen off - i want really sleep/standby/idle

--------------

Now if i push the power-button accidently while phone is in my bag (proximity covered) my phone wakes up and after 1 second the screen dim - but phone still alive (for the time i have set).

---> i don´t want this behaviour. I want the behaviour from above.

---------------------

phone not locked:

While the phone is not locked, i don´t want my phone to dim the screen when covering the proximity sensor. I only want to dim the screen/lock phone/standy when i push the power-button.

I will post a log file later.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Here is my log-file.
[Touch Diamond, MDA Compact IV Themes and Apps] ahlok_hk:
I just installed the latest version 2.12.2 and turn on the proximity sensor option, then empty all action. Then do a reset of hd2. Afterward when I cover the sensor it turn off the screen immediately, even I have cleared all actions at "Near", "not near" and "on bluetooth".

Is it possible to turn on the proximity sensor but do nothing when the sensor is triggered? This is because I just want to read the sensor value but don't want to lock the screen.
[Touch Diamond, MDA Compact IV Themes and Apps] ahlok_hk:
My HD2 behavious the same, too. Seems link the proximity sensor lock function is not fully controllable by the touchlockpro yet.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The screen off is a function part of the proximity sensor/HTC functionality, not by TouchLockPro. So enabling the Proximity sensor apparently gives this behaviour.

If someone nows how to disable this HTC functionality.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, I only see the first command executed, so although you have specified multiple commands they seem not to be executed.

I will try to debug my code.

About the !IDLE, that will indeed do the screen off and backlight off only. If you want to go directly to sleep, you need to give command "!SUSPEND". Note that this is still a request, another application can keep still the phone alive. I will debug this scenario too.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I will debug this scenario, because it looks like multiple commands are not executed.

That means in practice disabling the Proximity when unlocked.

I need to add a setting for that, so that this is possible. In the previous version there was a setting for that, I need to reintroduce this in one way or another.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Thank you, while i make a call, proximity should work - like without TLP.
[Touch Diamond, MDA Compact IV Themes and Apps] gigitek:
I was very excited at first... when saw the video. I have a HTC Diamond.

With the latest version installed batclock says it's locked, but i can do anything... Using navsensor, right down, I unblock. batclock changes it;s background color, informing that it's unlocked. I lock the devices using the power button, but still i can do anything i want.

- When TPL is running, sometimes, device doesn't mute when incomming call and turned FACEDOWN. => sometimes it does sometimes it doesn't, don't see a rule here...

- Gsensor active , In call tweak active -> when i make a call, when holding the phone at the ear light goes off; If someone else is calling when holding the phone at the ear light DOESN'T goes off.

- nav sensor gesture sometimes works sometime it doesn't, with or without the TF3DWorkaround

I've attached a log file, written while batclock indicated locked but i could navigate through the menu.

:confused:
[Touch Diamond, MDA Compact IV Themes and Apps] madbird:
1 fixed, 1 to go :)

hi, with the settings,

proximity sensor:

proxi sensor on

proxi time 500

near !SUSPEND

not near !UNLOCK;!PROXIMITYDISABLE

and under,

other settings:

autolockonpoweron

suspendonbacklightoff

i managed to make the proximite work on the hd2. the screen stays off (or at least only flash up for a second) when the sensor is covered.

the only problem left is that the proxy sensor is still working when the device is on. that happens after unlocking the hd2.. so the screen goes off when your finger came near the sensor. and i have no idea what to configure to stop this.

regards mad.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
I can confirm this fix/setting works (by madbird).

Another little issue:

When phone is locked and wake up by power-button but proximity still covered, the screen comes up only a second, but sometimes i press accidently on the screen in just this second (screen is not locked in this short time).

Is there a chance to lock the screen while the screen comes up for this very short time? On other sensors the screen is locked.
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
Hello, ZuinigeRijder!

My colleagues at 4pda.ru write to me:

;)

How can I update the translation most quickly?
[Touch Diamond, MDA Compact IV Themes and Apps] madbird:
hi,

sorry for making so much work to you, but the programm is simply to good to just leave it. i made a logfile this morning. it shows:

1. device is switched off and the p.sensor is covered, then pressing a hardwarekey 3 times. everything works like expected. screen is switching on for a second then shutsoff. after uncovering the p.sensor the device display switches on.

2. the device is switched on. i put my finger to the p sensor, 2 times only for a short time (more like flicking over it). so the screen switches off and back on. the last time i wait until tlp shuts off the device.

so i hope this is usefull in finding out what makes point 2. happen, because config says p.sonsor disable after unlock. so screen should stay on all the time.

thanks in advance mad

ps. config is still like this:

proximity sensor:

proxi sensor on

proxi time 500

near !SUSPEND

not near !UNLOCK;!PROXIMITYDISABLE

and under,

other settings:

autolockonpoweron

suspendonbacklightoff
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
I have same settings like madbird.

If i make a call, screen shuts off while phone near my head. If i remove the phone from my head, the screen is still shut off.

Why don´t the screen turn on automatically when uncovering the proximity sensor?

So now i have to push the power button to make some settings while in a call - thats not good.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I also have a HTC Touch Diamond and I must make sure to enter the SIM pin before TouchLockPro has started. Also make sure you disable other locking solutions and also do not use the original Windows lock! Make sure to do a soft reset, and try out if it locks correctly after that, by powering off and on, after TouchLockPro has started.

The keyboard and touchscreen hooking works only if not another application uses the same approach. So I do not know if you have the 'standard' things installed or extra's. Another option is to use HTCLockAPI = 1, because that locks everything in another way. You loose some functionality, but on the Diamond there are enough sensors for unlocking.

Mostly unlocking via the light sensor works, the capacitive swipes work well when not using TF3D, you can make an easier GSensor move and you can always use the Stylus approach for unlocking.

You did post the TouchLockAction log file, but the touchlockpro.log.txt contains the most important information. If you do not want to use HTCLockAPI = 1, you must indeed make sure it locks correctly, otherwise TouchLockPro is useless. And then you need to look to another locking solution :o
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, that means an option to keep the proximity sensor active, but TouchLockPro should not react on it, when a call is connected.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
When the screen goes off and on in a short time, the phone will not be locked. So there must be an option added related to the fact the phone is unlocked and then you do not want the Near actios to be executed anymore.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, there must be possible to specify that you do not want to use Proximity anymore when unlocked. I will add this in a next version, I am still thinking how to add this feature/setting......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is because while in a call, TouchLockPro should ignore the Proximity sensor. In a next version I will make a setting for that, still thinking how to do that the best.......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In the meantime the BattClock improvements have come in (whole restructuring) and the Proximity sensor. I first want to make a new version (with 2 extra settings) and then I will post the translation files. So till then a little patience ;)
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
How to tell between a screen off vs standby? Doesn't they look the same?

I'm using 2.12.1 on HD2. The proximity sensor seems to be normal. With Use Unlocked cleared, it doesn't do anything when the phone is unlocked.
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
Where can I learn how to do this type of configurations? I don't find it on the settings web page.
[Touch Diamond, MDA Compact IV Themes and Apps] gregwee:
I installed TLP 2.12.1 on my HD2, but encountered a problem.

The normal HD2 behavior for the proximity sensor is to blank the screen during a call when you put the phone near your face. This is to prevent your face touching the screen from activating things. However, If I set the proximity sensor to disable when unlocked in TLP, the sensor does not work at all during the phone call, and the screen will remain on during the call. How can I fix this?
[Touch Diamond, MDA Compact IV Themes and Apps] khaytsus:
Is it possible to use the Proximity Sensor to do screen off, but not lock, and most importantly, not to unlock the device coming out of suspend? I basically want it to turn off the screen and affect nothing else.

So if I suspend, and hit the power button, I want it to stay locked until I hit my key sequence.

If the proximity sensor is used, !SCREENOFF, when it's uncovered, !SCREENON. But with this configuration it locks the screen when it turns the screen back on, which I don't want.

If I leave the it at the default, !SCREENON;!UNLOCK it also automatically unlocks the phone any time I resume (unless the sensor is covered of course).

Probably possible, just confused with the settings, and the settings are sooooooooooooooooooooooo slow it's painful to experiment.
[Touch Diamond, MDA Compact IV Themes and Apps] madbird:
hi, and thats the difference, the actual version (used by bib and me) is:

Version 2.12.2 (20-2-2010)

see first post here. especialy in the proxymite sensor settings are a lot of changes. the 2.12.1 has some other problems with the proximite settings, you can read about a few pages earlier.

regards mad
[Touch Diamond, MDA Compact IV Themes and Apps] FlashT:
I cant get it unlocked by volume keys on HTC Touch Diamond... only unlock that works is stylus...
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
unlock during incoming second call

Hi

i use version 2.12.2 on htc touch pro 2. It locks during call but when a second call is incoming the scren is turned on again and phone unlocked

see att log

regards nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, you did use Volume Down, followed by Volume Up?

You did not change the settings?

You did not use HTCLockAPI = 1, because then you cannot unlock by key sequence.

You can enable debug logging, reproduce the scenario and post the debug log file, so that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You have to wait till a next version, where you can specify not to disable sensor while call is connected. You can also use the InCallTweak, which uses the GSensor for screen off while in a call.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
When a next call is coming in within 5 seconds, TouchLockPro still finds it an connected call. The 5 seconds delay has been added, otherwise the phone could be immediately locked, when a call is ended. Now you still have 5 seconds to press hangup keys or power up the phone. So this is a side-effect. Removing the delay will give other problems.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
If i only use screenoff, then screen will be on again iv the proximity coverage is gone.

If i use suspend or standby, then the screen will still be shut off.

That´s why i want to have suspend/standby.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

its okay that the screen lights up, but its not good that it is unlocked, if that happends in the pocked the first call may be enden by accident - could you implement that it stays locked ? If screen is lighted up its easy to unlock by user by several otehr methods

Thanks

Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
In other words, what you need is to lock by proximity, and stay locked even when proximity is "away". But wouldn't that contradict with the design that the phone unlocks when proximity is "away"? It seems we need two different criteria: when to lock and when to unlock. I need the "unlock by proximity" so that when I pull the Leo from my pocket, it unlocks even in dim lighting, while you need the "lock by proximity", so that you can lock the device by waving near the sensor.
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
BattClock Position

ZR

I dont seem to be able to position the BattClock at the same location while device is in landscape mode. Please see attached.

Your help appreciated.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
I want to unlock my HD2 only by power-button (and there is no proximity when i press it at this time).

I often pull out my device from my bag and put it to the table, without power on the device. In your case, my phone would always come on power and would brighten for the time i have set for timeout.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The landscape settings became different settings. So you can take over the same settings for landscape, but you can also configure landscape separate.

So you need to start the BattClock configuration while your phone is in landscape, adjust the location and sizes according to your will. Advantage is that you will see the end-result immediately.
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
Purrrrrrrrrrrrfect! Thanks so much:cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
New version with more Proximity control and BattClock improvements

Version 2.12.3 (25-2-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor

- Added command !PROXIMITYIGNORE, so the Proximity sensor keeps in the state it was, for other applications. TouchLockPro wil not react anymore, till !PROXIMITYACCEPT command is used.

- Added command !PROXIMITYACCEPT, so Proximity commands are accepted from then on.

Changed the defaults for better use of Proximity (note that those will only be overruled if not already set or by reset to defaults):

- Proximity Sensor Time (ProximitySensorTime = 700)

- Near (CmdProximityNear = "!SUSPEND")

- Not Near (CmdProximityNotNear = "!UNLOCK")

New settings:

- Lock (CmdLock = "!PROXIMITYACCEPT")

- Unlock Call (CmdUnlockCall = "!PROXIMITYIGNORE")

- Unlock No Call (CmdUnlockNoCall = "!PROXIMITYDISABLE")

Incorporated BattClock 1.9 improvements:

Show Battery percentage, temperature and Current above the top bar.

- Possibly to show the info in columns instead of rows (option Divide Horizontally)

- Added option to show Battery Temperature (updated once per minute)

- Added option to show Battery Current in mA (updated once per second), great to see power consumption

- Show CPU also if it getidletime is greater than 100
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Hi, works great now!

EDIT:

Screen still shut off when phone is not locked and i cover the proximity sensor.

I tested following settings:

not near: !UNLOCK

and

not near: !UNLOCK;!PROXIMITYDISABLE

and

not near: !UNLOCK;!PROXIMITYIGNORE

Same behavior - still allways shutting off.

So if i play a game and often cover the proximity sensor accidently, screen always shut off.

How can i disable proximity sensor while phone is on and not locked?
[Touch Diamond, MDA Compact IV Themes and Apps] sjanos:
TouchLock vs Xperia X1

Hi,

I am using a cooked Xperia ROM, and the most musthave utility is this. Unfortunately Xperia doesn't have sensors, so what I am using is BattClock and TAPI, specially the TAPI function is why I chose TPL.

So, what I need is to off the screen during a call and lock it when ended.

My setting is:

UseTAPI

UnlockWhenConnected

Incoming: !UNLOCK

Connected: !LOCKSUSPEND

Ended: !LOCKSUSPEND;!SCREENON

The problem is with the "Ended" commands, when set at the fist time it is working, after second time and so on the "!SCREENON" never executed. But if I set to debug, it is always working!

If I replace "!LOCKSUSPEND;!SCREENON" to "!LOCKSCREEN" it is never working again.

It is on v2.9, after upgrade to any newer version, any setting in "Ended" will not lock my device.

I can live with it, but I would prefer to lock and screen on after a call.

Any advice is very welcome!

Brgs,

/Janos
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Here the the latest english translation files are available. As said before, the BattClock settings have been changed a lot and the Proximity has been added.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to see that TouchLockPro is also used for phones not supported by sensors. Are there really no sensors in the Xperia X1 or are just the API not known ;)

There is a delay of 5 seconds after end call where the phone will not be locked. So I expect that is the problem. Probably I must overrule this behaviour, if this is forced via a command. Because LockScreen should work then too. But that does not explain why it is working with debug on, hmmm.

Why do you want to execute screenon after locksuspend?
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Hi ZuinigeRijder,

please can you tell me the setting for disabling proximity sensor while phone is on?

If i use my phone (e.g. playing) i often move my finger near the sensor and the phone everytime goes off.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Use command !PROXIMITYDISABLE.

You can e.g. couple this to a GSensor command or make a shortcut to TouchLockAction with as parameter !PROXIMITYDISABLE
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
I want this behavior all the time when phone is on.

I tested:

not near: !proximitydisable

----> no more unlocking by proximity sensor

not near: !unlock;!proximitydisable

----> unlocking, but screen off when covering sensor

It seems that only the first command will be executed.

I changed to: !proximitydisable;!unlock and unlock-command was not executed.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did debug my code the previous time and then they were executed. Can you post a debug log file, with this scenario :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Here it is...