yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] creed:
Hi, thanks for all your hard work on this great program! It's very useful. I have a question about the new proximity sensor settings on my HD2.

I would like to have TLP remain locked and disregard the proximity sensor BUT I would like the screen to lock when the proximity sensor is activated. Is this possible to configure?

And I am not sure I understand what the Proximity Use Unlocked setting actually means. Could you clarify that please?
[Touch Diamond, MDA Compact IV Themes and Apps] La_Globule:
Hello,

I've new information concerning my problem : the InCallTweak option works properly when I receive an incoming call : the screen goes off in portrait and goes on when face up.

The problem ONLY occur when I place a call.

May be you don't manage the phone state identically for incoming and outgoing calls...

I hope this will help you.
[Touch Diamond, MDA Compact IV Themes and Apps] madbird:
hi,

first let me say thank you for this helpful piece of software. i think i will switch to touchlock and forget about the rest :).

i have a question, is it possible to have an 'delay' option on the proximite unlock. i ask because somtimes when i pull the device out of my pocket the proximite unlock the device before i have it completly out, and so i press buttons or the screen accidently.

regards mad

did you set 'Proximity Use Unlocked' option to on?. for me it works with this option set to on.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
I want the original function from the htc rom back.

What is the difference between "Proximity Use Unlocked" and " Proximity Screen Off"?
[Touch Diamond, MDA Compact IV Themes and Apps] madbird:
hi

tested it now a little more, you are right. when i quit touchlock pro the sensor is working fine when a call is in progress. when tlp is running i have to switch the "Proximity Use Unlocked" on to make this work. but that is only a temporary workaround, because then the sensor is working all the time, and not only when a call is in progress.

regards mad

*EDIT*: somthing like the 'InCallTweak' option form TelefoneAPI panel, but using proximite instead of gsensor would be the solution i thing.
[Touch Diamond, MDA Compact IV Themes and Apps] Slide:
Hi ZuinigeRijder,

can you please update TouchLockPro with new BattClock Version 1.8.

Thanks.

Greeting

Slide
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am working on that. Hope to have a new version soon :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Indeed the Proximity Use Unlocked will disable the sensor when the phone is got unlocked. It looks like we need a setting "Use Proximity at Call", for people only wanting to use it for unlocking AND while in a call. I will add this in a next version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
"Proximity Use Unlocked" will disable the sensor when not checked and the phone is unlocked. So thereafter the Sensor will no longer work (also not in a call).

"Proximity Screen Off" works only when the sensor is enabled, so in combination with above you can choose the behaviour, screen off when not unlocked (in your pocket) or also screen off when proximity detected while unlocked.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did not add this at the first place, because I did not think it was needed. So you want the proximity unlock time configurable, like the light sensor time :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The design is to handle them the same. But maybe I did overlook something. You can help in providing a debug log file with the scenario of calling, so I can have a detailed look what is going wrong. And also note and mention the time you did place the call.

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, so you want a setting to not unlock by Proximity sensor. How do you want to unlock then? With other sensors? Is there a special reason you want this?

On HTC devices it will disable the proximity sensor when not checked and the phone is unlocked. For Samsung users the notification is stopped.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, mostly people ask for auto-unlock, you ask the opposite ;)

I suppose you want a setting in combination with Proximity only? Because otherwise this does not make sense?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is because you did not check "Use Proximity Unlocked" I suspect.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
With the setting HTCLockAPI = 1 it should lock on Touch Pro. The other approach, keyboard/screen hook will not work because they probably use the same approach.

You loose some functionality, like unlocking via keypresses and ZoomBar not working, but it should lock then with HTCLockAPI = 1.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hope it keeps locked now. I need to give in my SIM-pin at boot before TouchLockPro is started and wait till TouchLockPro BattClock is visible, otherwise it is also possible on my phone it will not lock.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not know how to trap those keys with the keyboard hooking. I know it is on phones possible to overrule key action by changing the lnk file. However, I never did myself, so maybe others can advise?

Default it will fall asleep after 30 seconds when not unlocked within that time. So you can shorten that setting:

SuspendTimeOutPowerOn = 30000

But make sure you cover the Proximity sensor with your finger ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
At end call a screen on is done, because normally that is the behaviour you want (e.g. you can see how long the call was). Hmmm, so you do not want that behaviour with bluetooth on?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will change into !IDLE in a next version. Note that InCallTweak also uses !IDLE, so it should not be a problem.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
When i check "Proximity Use Unlocked" and "Proximity Screen Off" is checked or unchecked, it´s the same.

So i see no difference between "Proximity Screen Off" checked or not checked.

The Screen goes off even when i´m not in a call. So with current version there is no setting for only screen off while in a call?
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
hi

i would like to screen off after a call, could you implement that ?

I thought that was what the command "Locksuspend" at "end call" did ?

(to save battery life) and on BT i would not want PS to do anything (TLP is much better to control what should be done directly)

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] La_Globule:
Thanks for your answer. Here is the log file and the scenario.

I made the outgoing call at about 21:52.

The screen switched off when the call was established (with a little vibe).

I put the phone in portrait then face up. Nothing happened.

I pushed the windows button to switch the screen on and I tapped on the "Keyboard" button. The screen went off.

I pushed the windows button again to switch the screen on and I tapped on the "2" button. The screen went off.

I put the phone in portrait then face up.

I pushed the windows button to switch the screen on and I tapped on the "Terminate call" button. The screen went off and then on at the end of the call.

Note that there are many "ERROR loading HTCAPI.dll" messages in the log file.

Thank you for your help.
[Touch Diamond, MDA Compact IV Themes and Apps] khaytsus:
How are people with Rhodium using this software? Personally, I don't want to use G-Sensor, Proximity Sensor, Light Sensor, Keyboard or Stylus. That leaves hardware and zoom.. Zoom does nothing for me (because I've configured it to scroll I suspect?) sliding or tapping... Only way that remains to unlock it is via hardware keys, which I've left at vol down/up.

I really like S2U2, but it uses 2 (sometimes 3?) processes which are *tight* on the Tilt 2, plus the ram it uses.... It's pretty, but I could use something that works similarly without the resources. Just, eh, seem confused on how to quite do it without all of the stuff I excluded above. :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Is there a special reaon you do not want to use the hardware sensors? Because they will not eat battery.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Probably it is an auto function of the proximity sensor. I just activate/deactivate the HTC sensor. The Samsung sensor might behave differently.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I will check my code, to see if I can do something about it, when configured locksuspend at end call.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
looks like the difference at incoming call is, that the incoming call is keeping the phone more alive. When you call yourself (another dialer) the !IDLE command seems to shutdown the GSENSOR and not when there is an incoming call :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] La_Globule:
I'm not sure that the G-Sensor is the only one involved in the problem : the screen goes off as soon as the the outgoing call is established in any position of the phone.
[Touch Diamond, MDA Compact IV Themes and Apps] markoz1973:
I installed GScroll yesterday evening and TLP stopped working. I had to uninstall both and reinstall TLP again to have it working.

Anyway TLP is perfect.

Marcin
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
The proximity sensor seems to be working fine on HD2. Two strange observations:

It seems G sensor is now working on my HD2 too. It has not been working 90% of the time until now.

All sensors fail at the same time at times! The following two scenarios are rather repeatable on my Leo (I think the two scenarios are related).

Use 3-5-6 G sensor sequence to suspend phone (now that I can use the G sensor :) ). Press end call to wake up. Phone stays locked indefinitely. Light sensor is not working, proximity sensor is not working, G sensor is not working. I revive the phone using volume down-up (a trick I just learned a few days ago).

Sleep the phone using the End Call key. Wait 5 seconds or more. Press End Call to wake up. Same behaviour as above (all 3 sensors refuse to unlock). However, if now I press End Call a third time to put it back to sleep, and immediately press End Call a fourth time to wake to it, it usually unlock after 2 seconds (because of the light sensor).

A comment on usability (I don't know what to suggest). I am not yet used to the proximity sensor, and it is a little annoying. Everying my finger reaches for the start icon on the top left hand corner (which launches the wktask menu for me), it triggers the sensor and blanks out the screen. I have still to develop a new finger movement habit, or to move the wktask icon away (its original favorite location, the clock, is already being used by the TLP clock, so it is difficult to find yet another good location for wktask).
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
TLP is by far more functional than S2U2, i use

- detect on BT and check light

- proximity sensor use but desable on BT.

- Suspendlock on G sensor face down

- use TAPI, backlightoff on end call, lock when incoming, incoming lockscreen, connected locksuspend

- use light sensor, unlock on lightsensor

- use navsensor, touchsequence, 22

- autolock on poweron, unlock on ac power, suspendonbacklightoff

best software out there. And the speed of development is simply outstanding.

regards Nolan

htc TP2
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Great, thanks

but "Locksuspend" at "end call", what does it do? (it doesnt dimm screen, the screen is still lid up after call with this setting)

PS i changed "at end call" to "backlightoff" now it seems to be dimmed after call.

What is the diff of backlight off and screenoff (both turn off screen)?

regards nolan
[Touch Diamond, MDA Compact IV Themes and Apps] khaytsus:
No, nothing like that.. Keyboard and stylus I rarely fool with and are clumsy.. Proximity sensor is not all that reliable (I find the phone still lit while I talk on the phone quite often), I wouldn't want it to unlock based on light because that requires a specific environment, G-Sensor is just too easy to accidentally trigger and would be tedious to do every time I wanted to unlock the phone...

None of this is meant to be taken against your software or designs, they are just observations of the hardware outside of your software. What's nice is you offer the ability to generally lock or unlock or do nothing for all of these, but I still can't figure out a robust unlock method on my particular phone (Tilt 2) except for hardware buttons. If the zoom bar worked I think that'd be cool, but it either does nothing or actually activates the softkeys while locked for me. :(
[Touch Diamond, MDA Compact IV Themes and Apps] khaytsus:
The 22 navsensor sequence, you tap twice in the middle of the zoom bar and this works for you? For me it does nothing, but as I mentioned in my first post I do have something which enables scrolling via the zoom bar so that might be interfering.

The rest I'll have to tinker with some more, thanks for your configuration info. I still need to figure out a reliable unlock method except the hardware buttons.. The buttons on the front of the Tilt 2 are so tiny they're a pain to hit reliably and the volume buttons are out of the way I suppose.
[Touch Diamond, MDA Compact IV Themes and Apps] intrados:
TLP proximity sensor and Omnia Pro

Hi I was not able to enable the proximity sensor support for TLP 2.12.1 on Omina pro. the log fimr is attached. could you please advice about it.

Thanks and BRGRDS

Rado
[Touch Diamond, MDA Compact IV Themes and Apps] creed:
Yes exactly. I would like the only way to unlock my phone by the ways I use currently, either Gsensor or vol up vol dn. BUT if I put the phone in my pocket or face down on a surface I would like the screen to lock and go off except in call obviously!

My reasoning is that I don't want the screen activating in my pocket but I still want to be able to use it in the dark, so I don't want to use the light sensor to achieve this.

I hope that makes sense! :)
[Touch Diamond, MDA Compact IV Themes and Apps] madbird:
hi, yes something in that direction would be great. only a small delay to prevent my self from pressing keys/touching the screen while lifting the device out of my pocket.
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
Further observations re proximity sensor.

My HD2 G sensor works if and only if the "proximity use unlocked" option is checked.

Although "proximity screen off" box is cleared, moving my finger near the proximity sensor will turn the screen off. I have no idea why. Moving my finger away immediately turns it back on.

Actually I prefer to turn the "proximity use unlocked" off, because now every time my finger reaches for start menu icon at the top left hand corner I turns the screen off (although the proximity screen off box is cleared). However, the G sensor will stop functionning if turn this option off.

And as I wrote earlier, all the sensors will consistently fail after a suspend.

A question about InCallTeak, which locks screen when phone is connected and the GSENSOR orientation is portrait or reverselandscape. I wonder why landscape is not included. When holding the phone with my right hand, my phone is in landscape during a call, not reverselandscape.
[Touch Diamond, MDA Compact IV Themes and Apps] NearDenver:
One small problem

First, great app. (using a TP2)

I turn off most sensors (light, G, proximity) but do like the "zoom bar" to unlock. (And the red line at the top is a great signal that the phone is locked).

Tapping on most of the screen does nothing but if you press at the very bottom of the screen (like along the bottom row of pixcels), the bottom menu items can be pressed. It would normally be hard to do but since I'm sliding my finger along the bottom to unlock, I often end up pressing one of these menu buttons.

That can be a pain. Is that a known problem (or feature)?
[Touch Diamond, MDA Compact IV Themes and Apps] aadadams:
That's a problem... I love TouchLockPro but have not been able to use it on my TP2 due to these types of issues. I applaud the effort that the developer has put into the near infinite compatibility of this app across many devices. I really want to be included too...
[Touch Diamond, MDA Compact IV Themes and Apps] La_Globule:
I confirm I've the same problem on my Diamond 2.

When the phone is locked, if I tap at the very bottom of the screen (when sliding on the zoom bar), the actions indicated by the soft keys are executed although the phone remains locked.

It's a bit weird.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
strange benaviour TLPS 2.12.1

Hi

Zuinige

i have settings as seen in log, but during call (if i have made an outgoing call) the device (htc tp2) is suddently unlocked, can you see whats happening ?

thanks

Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] JohnBecker:
I saw this mentioned before but nothing else was mentioned about it. I'm using the latest version 2.12.1 and it's been doing this same thing for the last few revisions.

I use a BT earpiece nearly constantly. If the TP2 is on my hip and I try to answer the phone when it's locked, I only hear my ringtone in my ear. It will not answer until I pull it out of the case, unlock it and then slide to answer. It's very annoying. I started using this app because I was hanging up on people when I moved around. That part works great, but I do need to answer my phone using the BT.

Any suggestions? Is it a setting I have wrong?
[Touch Diamond, MDA Compact IV Themes and Apps] JohnBecker:
sorry... the post was duplicated by the website for some unknown reason. I deleted it.
[Touch Diamond, MDA Compact IV Themes and Apps] ww2250:
Proximity Sensor Unlock Time

Hi ZuinigeRijder

Thanks for your marvelous work! It works great on my Samsung Omnia 2, but I have a request for enhancement.

Let me explain: I am using the bundled soft sleeve-type phone case, and the proximity sensor is located at the top of the phone where it would come out of the case first when I take out the phone.

The problem is when the proximity sensor senses the phone is out, it immediately unlocks the phone, for which the phone is still half way inside the case and it is very easy to press the wrong button or the screen.

So the proximity sensor is currently disabled on my device. But in my opinion, it is a far better solution than using the light sensor because it don't work in dark places.

I think it will be perfect if we have an option for "proximity sensor unlock time" - just like that of the light sensor.

Can you consider to add such a feature?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, that is the InCallTweak, which is activated, because the GSensor was working just before. But unfortunately not later on. I will try to reproduce the situation myself.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, how did you achieve pressing End Call is waking up your phone? Did you not lock all keys expect power button?

The same for getting the phone to sleep with the end key? Is this the Windows Lock? Or something different?

In the next version the Proximity sensor time will be configurable, so this gives a possibility to set the time larger (e.g. 3 seconds).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
backlight off does only disable the backlight, so the display is still on, but consumes less power. With screen off even less power is needed, because nothing has to be shown and the LCD display does not need to do anything. I think I force a screen off at end call, so I will check my code.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It is all about taste, but I recommend:

- use light sensor unlock, this will unlock most of the times (maybe even configure it shorter)

- if in a hurry take out the Stylus as fallback

- or use the Keyboard unlock

- configure KeysOnly at incoming call if you have a slide2answer solution, so you can answer/reject the call via slide2anser.

Because the annoyance of the ZoomBar and the icons below are not locked, there is also the following possibility:

- HTCLockAPI = 1 (ZoomBar and key unlocking will not longer work, but also the icons are locked)

- use light sensor unlock, this will unlock most of the times (maybe even configure it shorter)

- if in a hurry take out the Stylus as fallback

- use GSENSOR gesture for unlock (maybe change the move)

- configure KeysOnly at incoming call if you have a slide2answer solution, so you can answer/reject the call via slide2anser without unlocking
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see the following error message:

010-02-17 14:35:35 164733242 Error in registering SmiProximitySensorRegisterOnChangeHandler: 2

So it looks your phone has no support for the Proximity sensor.

The Samsung Doc also says Omnia Pro is not supported for the Proximity sensor.

Too bad :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, strange that some people have this problems and others not. I have to think about it.

Your are right, I will add landscape too.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, it is a known issue the soft keys are not locked.

http://www.youtube.com/watch?v=lB52J0pekIo

I do not know a way to prevent that with the keyboard hooking and screen hooking. However, HTCLockAPI = 1 will lock those soft keys, but the disadvantage is that you loose some functionality, like the Zoombar and the unlocking via keyboard.

I cannot tap into this problem, because I cannot debug, I do not have those phones. I am a poor Touch Diamond user ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It did unlock by the proximity sensor:

2010-02-18 10:39:10 193685738 IsConnectedCall(true)

2010-02-18 10:39:10 193685738 SetBackLightOff(false)

2010-02-18 10:39:10 193685738 ======================== Change from screen OFF to screen ON ==============

2010-02-18 10:39:10 193685738 SetScreenOn(true)

2010-02-18 10:39:10 193685738 IsConnectedCall(true)

2010-02-18 10:39:10 -1392787094 CTAPIDevice::lineCallback()

2010-02-18 10:39:10 -1392787094 LINE_DEVSPECIFIC=(104, 5, 0)

2010-02-18 10:39:11 1295994826 IsConnectedCall(true)

2010-02-18 10:39:11 1295994826 GetProximityIsNear: 0

2010-02-18 10:39:11 1295994826 HTC light sensor value: 0

2010-02-18 10:39:11 1295994826 GetLight(): 0

2010-02-18 10:39:11 1295994826 Light OFF: 0

2010-02-18 10:39:11 1295994826 Clock Time update

2010-02-18 10:39:11 1295994826 InvalidateClock()

2010-02-18 10:39:11 1295994826 WinMain: 15

2010-02-18 10:39:11 1295994826 ClockLockedWndProc(WM_PAINT)

2010-02-18 10:39:11 1295994826 ClockPaint()

2010-02-18 10:39:11 1295994826 BattClock RECT Portrait Left:0 Right:60 Top:0 Bottom:48

2010-02-18 10:39:11 1295994826 IsConnectedCall(true)

2010-02-18 10:39:11 1295994826 IsConnectedCall(true)

2010-02-18 10:39:11 -1392787094 CTAPIDevice::lineCallback()

2010-02-18 10:39:11 -1392787094 LINE_DEVSPECIFIC=(107, 100, 0)

2010-02-18 10:39:11 1295994826 IsConnectedCall(true)

2010-02-18 10:39:11 1295994826 GetProximityIsNear: 0

2010-02-18 10:39:11 1295994826 HTC light sensor value: 95

2010-02-18 10:39:11 1295994826 GetLight(): 95

2010-02-18 10:39:11 1295994826 Light ON: 95

2010-02-18 10:39:11 1295994826 IsConnectedCall(true)

2010-02-18 10:39:11 1295994826 GetProximityIsNear: 0

2010-02-18 10:39:11 1295994826 ========================UNLOCK BY PROXIMITY SENSOR=============================