yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
Just what I was searching for! :)

Dear Rick,

Please accept my BIG THANK YOU and my PP donation for your program - it makes our lives (with our phones) a whole lot better! :cool:

I was looking for a program like yours for quite a while. I read countless pages about many different other programs trying to achieve the same goal, but just 2 days ago I found TLP v2.0 and I quickly decided to install it. Man, this is the real deal! :) Many, many thanks for such a well thought and effective tool!

I've been using it for 2 days now and I must say I am very, very happy with it. Please forgive me if somebody else already asked you this (I haven't read all the 93 pages of the thread), but I am wondering about several potential improvements:

1. Do you think it's possible, at least in theory, to add g-sensor support for unlocking and/or extra buttons emulation using the capacitive areas? Do you have any plans to do so? That would be awesome! A killer-application! :cool:

2. Is it possible to enable just the power key even if everything else is still locked? The reason is that once you press the power key to turn on the phone you have to actually unlock TLP before being able to use the power key again to turn it off again immediately. (Yes, I know I could wait for 30 seconds for the phone to turn itself off, I'm just curios if I can do that quicker)

3. What about adding some short descriptive labels under the TouchLockAction icons? I think that would be a very quick win (I remember the first time I saw the 6 icons I was really confused and had to search and read the documentation.)

4. Sometimes unlocking the phone using taps on the capacitive area no. 2 (middle button) fails for quite some time (e.g. the first 5-6 seconds after the phone wakes up). Even though I tap very carefully no taps at all are registered on the BattClock icon. Then after several seconds it suddenly starts registering taps and unlocks. This happens even when using other capacitive areas (1, 3, 4). Do you have any idea why? This happens only now and then, not always. Can it be somehow related to static electricity or something like this?

Thanks again for the program, continued support and an admirable attitude towards everyone! PayPal donation sent to your Gmail address (please note however that the NoScript add-on detects the "Donate" link on your web site as an XSS attempt).

Best regards,

Dan
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Hey Dan,

Check out his Wish/TODO list on his site:

http://www.zuinigerijder.com/#9

Looks like he has a few of your suggestions on there at least in some fashion or another. I too would love to be able to specify which physical buttons are locked or not (power & answer) especially at certain phone states.

For now I check the LockTouchPanelOnly option to avoid my 'OCD power on to check calls/time then power off quickly' tendency and my 'throw the F'n phone out the window cuz I can't pull the phone out of my pocket & unlock to answer the call in time' desire. :o lol

Don't get me wrong, TLP is the closest to perfect solution I've found so far so I'm definitely not knocking it. Keep up the good work ZuinigeRijder, one day it will be perfection! :)
[Touch Diamond, MDA Compact IV Themes and Apps] momyc:
Hi Zuinige ,

I join Dan74(buna ziua Dan) and other posters to thank you for this nice app.

Dan has few good points to which I agree.

Also the issue from his point 4 , it happens on my HTC Diamond (Rogers ROM 1.93) few times, but I cannot say if it’s a specific pattern.

I’d like to add a request : on a earlier version it was an option to setup the no of touches in order to unlock the device. Can we get that back ? I was setting that to 2.

Kind regards,

Catalin
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
I second that! It might go along well with locking only certain things in certain phone states: asleep, just woke up, woke up with certain app running, incoming call screen, etc. The trick is implementing an options list to do it and if it is even possible to code things like lock all keys EXCEPT power, etc.

My ideal would be:

sleeping: screen & capacitive & all keys except power locked

just woke up: screen & all keys except power & capacitive locked

incoming call: screen & all keys except power/answer/end & capactive locked

Maybe it is more easily conveyed like old school INI file:

[Sleeping]

Locked=Screen,All Keys,Capacitive

Unlocked=Power

[Awake]

Locked=Screen,All Keys

Unlocked=Power,Capacitive

Timeout=5

[IncomingCall]

Locked=Screen,All Keys

Unlocked=Power,AnswerCall,EndCall,Capacitive

For you you might set:

[Awake]

Locked=Screen,All Keys

Unlocked=Power,Capacitive

Apps=WindowsMediaPlayer,MP3Player

[WindowsMediaPlayer]

Unlocked=Screen

[MP3Player]

Unlocked=VolumeUp,VolumeDown

Obviously that is very rough but hopefully it shows the thought process for phone/app state conditional locking/unlocking. :)
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Hi Catalin,

You can do that now. Change CapacitiveTouchSequence to 44 for 2 touches anywere in keypad area or set it to 11 for 2 touches on Home/Answer area or set it to 3333 for 4 touches on Back/End area etc etc. Not very intuitive at 1st but MUCH more powerful than the old '# of touches' method with the same ability possible by setting # of #'s. ;)

Hope that helps.

Bill
[Touch Diamond, MDA Compact IV Themes and Apps] momyc:
Thanks Bill ,

It worked !
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
Greetings!

If you decide to go this way maybe a default "policy" would also be useful, like:

[Sleeping]

Default=Locked - default state for everything not explicitly defined below

Locked=Screen,All Keys,Capacitive - methods explicitly locked

Unlocked=Power - methods explicitly unlocked

Cheers!

Dan
[Touch Diamond, MDA Compact IV Themes and Apps] drjim:
good thoughts on simplifying

Thanks, bill48105. I appreciate the warning about calls in darkness. Let's say I check Lock Touch Panel Only and I get a call in the middle of the night and press the Call button. Will my phone then turn on completely?

Also, I usually press the Power button to lock my phone before I put it in my pocket, but that's a pain. If I check UnlockOnLight sensor, when I put my phone in my pocket, will it automatically lock? If not, can I set it as such?

Much appreciated.
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Hey Dan,

Yeah you get the idea. :D Since it is a locking program I assumed LOCKED was the default but I still specified them in the locked list to be explicit. But yeah it could definitely be expanded & would likely be better done in XML but to me INI style is easier to read for discussion. Of course I'm not the author so I can only make suggestions. :)

Will be interesting to see if others would find this or similar 'lock/unlock depending on state/app' method useful or not.

Bill
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
No problem. I hadn't really even thought about it myself until you mentioned disabling all methods & I was like 'WHOA! Don't wake up to a fire and need to call 911!'

An incoming call wakes the phone like usual & you have to get the phone unlocked in order to answer it which can be a pain. That is why I keep the 'Lock Touch Panel Only' option checked so I can at least quickly hit the physical Call button to answer which works well but sometimes I hit volume or other keys on accident. Some newer roms have a slide to answer mechanism (check out Dutty's v4 rom http://xdaforums.com/showthread.php?t=411707 ) so you can set it to unlock the screen on incoming calls since there is no chance of answering on accident with that but you could still touch other areas on accident (such as Start menu). Of course that assumes you use HTC's dialer. I tried the super lite Microsoft built-in dialer and found that incoming calls show in a bubble at the bottom (like missed call or voicemail notifications) vs the full screen version you see in all the screenshots. Took me awhile to figure out what happened because when I think DIALER I don't think ANSWERER. lol
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Oops, sorry I forgot to reply on your 2nd part. Not that I know of, I am pretty sure you have to press the power button to put it to sleep again at the moment. Not sure the light sensor is sensitive enough for that but even if it was consider as your phone enters your pocket you are likely to touch something on accident before it gets in far enough to be dark enough to trigger the sleep. ;)

Unlock as you take it out of your pocket, lock as you put it back in.. You want the phone to read your mind! lol
[Touch Diamond, MDA Compact IV Themes and Apps] drjim:
cool, but

Can you answer my second question from the post? See below:

Also, I usually press the Power button to lock my phone before I put it in my pocket, but that's a pain. If I check UnlockOnLight sensor, when I put my phone in my pocket, will it automatically lock? If not, can I set it as such?

Oh, and I read that the UnlockOnLight sensor has a 1.5 sec. response time. Can that be adjusted in the settings?

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
I did, look up to previous post. Our posts just crossed. :D

I haven't seen the 1.5 sec thing, maybe you mean it defaults to 1500ms now? (The old default was 5000 which seemed like an eternity waiting & likely caused people to think it wasn't working.) I have set it lower to 500 (1/2 second) on the 4th config page but it still seems to take at least 1 second to unlock so I am thinking 1500 is minimum possible..
[Touch Diamond, MDA Compact IV Themes and Apps] drjim:
posts crossed

Got it.

Many thanks!

Over and out...at least for a while.
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
Don't let this turn you off - I though the same ("this is taking too long"), but just because I was *testing* it. When I started *using* the phone it felt just right :) (because it takes at least a second or so to reach for the phone and get it close enough that you can read the display etc.).
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Yeah I hear ya. I am glad default was dropped from 5000 because even in use it was not quick enough to be useful to me for answering calls. On old version the 1st thing I did was set it to 1000 but even that was not ideal because often the lighting was not strong enough to trigger the unlock & by time I realized it I missed the call. :mad: So unless I want to keep a flashlight in my pocket (hehe) for now I disabled light sensor unlock, set touch sequence to 44 (2 touches to any area) & lock only the screen. I find that the most useful way for me especially as a long time windows smartphone (no touch screen) user who still prefers trusty old buttons. As I said in earlier posts I'd love to specify WHICH buttons to lock/unlock (ie stupid volume buttons that stick out & are too easily pushed) but so far this is the most ideal app & config I've found to my liking. :)
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
Salut Catalin! :)

This point no. 4 is driving me nuts lately :(

I can't seem to be able to figure it out and 5 seconds can seem like an eternity when the phone has already been ringing for 20 seconds

ZuinigeRijder, any suggestion... please? HTC Touch Pro with stock everything here :p

Cheers,

Dan
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Hey Dan,

I hear ya on the frustration of not being able to answer a call!

Have you tried turning off TF3D from the Today screen just to test? Maybe that has long been an issue & just recently got much worse with recent updates. I recall seeing somewhere that TLP needs focus to register the touches so maybe some program running is stealing that focus & making it not work.

If it happens again note what programs are running in task manager but for me ever since I disabled TF3D I haven't had the problem once. Or try touching TLP icon 1st then capacitive area. Not ideal but might narrow down the cause.

Bill
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
SNAP! Guess what I just realized? If you are touching a capacitive area when you press the power button to wake it up that immediate area doesn't register touches right! :eek: Try it! The more area the touch the less area that reacts to touches to unlock. VERY strange. I bet the same thing happens if you are touching it when a call comes in. It is like it is self calibrating for accidental touches during handling vs true touches.. Wonder if that is something that can even be fixed or if it is by design..

I guess the short term fix at least is to touch a different area if your touches don't register.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Big thanks for helping each other

Great to see people helping each other in all the options, problems and advices, especially because the options and possibilities sometimes look overwelming. helping each other is how it should be! This way I do not need to answer all the questions. However, if I can add things to what is already mentioned, I will surely do.

Thanks for helping each other :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro working on non HTC phones (without using the sensors)

Someone is trying it out on a HTC Wing, which does not have the sensors and is not an VGA device:

See post #904

See post #916

Basically, besides the sensor unlocking stuff and the way the locking of the hardware keys is done, it should work on Windows Mobile phones with touchpanel. Maybe keep an eye on the Thread or even better, try yourself. Keep in mind the advices I gave in the mentioned posts.

If I need to change some things to get it also work on non HTC devices, I am willing to do that. Of course the unlocking methods are very limited.

Great that it appears to be working on LG KS20. I will consider an option to hook buttons for unlocking the TouchPanel when LockTouchPanelOnly=1 is specified. However, I have to find out what is possible and if the Power button is one of them (put it on the wish list).

It would be great if you post a screenshot of how it looks on your QVGA device (the BattClock and also the TouchLockAction screen) on the TouchLockPro forum.

I will consider to revisit TouchLockAction settings screens, so they can also be operated on QVGA screens (wish list too).

I am going to post this reply also in the TouchLockPro forum of XDA, so others know also about this one.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I will put this one on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
G-Alarm added support for auto unlocking of TouchLockPro G-Alarm thread

http://www.ageye.de/index.php?s=galarm/changelog

1.2.4 (2009/01/09)

* [ADDED] Better support for TouchLockPro

* [ADDED] Advanced option: Turn backlight off during an alarm

* [ADDED] Alarm option: Pause between the files

* [ADDED] "Vibration off" to the context menu of the snooze button

* [FIXED] Closing of some locking tools at midnight

* [FIXED] No playback after 1st snooze

* [UPDATED] Languages: english, german, spanish, italian
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
i use to have only LockWhenIncoming set. I only have activated AutoLockOnPowerOn during this testing process to have more chances to get bad TLP behaviours to report them to you.

I yet realized it but i think it wasn't when trying to copy the log. it was another situation that now i can't remember. To copy the logs first i disabled TLP.

I don't understand you. I'm a bit confused. Shouldn't the light sensor unlock device when detecting light condition in the middle of an incoming call (LockWhenIncoming)

i will during this weekend , now i can't because i'm upgrading my ROM and then i can't list the usual running processes that i have. That I must say that they are not a few ones. :) BTW i will try to isolate them to see which one is the CPU eater. BTW it is strange, i don't have battery draining issues although i have lots of small tools like the yours in windows/startup folder.

Glad to hear this!, and it was a really annoying bug!

Your tool is nearly to be a bug free application. Because the long delay locking bug it is not related to your tool, maybe another running process that i still have to investigate.

I think that there is a typo. it should be 2.0.4 i guess. or am i wrong? OH God you were talking about G-Alarm. LOL!

As always thanks a lot for your great support!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, it will.

I hope to upload version 2.1 monday evening. If you cannot wait, you can consider reverting to version 2.0, for the time being.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is because the battClock needs input focus, to get the capacitive touches. If another program is taken the input focus over, you have to waut till the BattClock is recreated.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The light sensor is only for unlocking, not for locking. When you press the power off button, the phone is automatically locked. When the screen is off, the light sensor does not sense light anymore, and TouchLockPro is not using the light sensor when the screen is off or suspended. So the light sensor will then not unlock your phone. Actually, TouchLockPro will immediately lock when powering on.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
May thanks for the donation. That keeps me going for improving TouchLockPro.

The problem with that, is that I have to provide translations. I agree, you must get used to it the first few days, but after a while you just know what icon means what. So I prefer to keep it like it is.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The log was indicating, it was unlocked by the light sensor.

You described your problem as:

7-1-09

styluslockpro1.log.txt

22:25 no lock but i can make a call

So it was unlocked by the light sensor.

Or did I misunderstand the problem :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
no sorry, let me explain better the problem i detected:

i had set AutoLockOnPowerOn. This day, I turned on my device to make a call, but before getting my device locked by TLP (as it should), i was able to start my outgoing call, that means 2-3 finger touches in some seconds before my device was really locked by TLP becasue of the AutoLockOnPowerOn setting i had enabled. After locking the device after some seconds of being it yet turned on, and with time enough to start a new outgoing call, maybe the light sensor unlocked it again (as it should be) meanwhile the outgoing call was in process, but now i don't remember well if the story ended in such a manner. BTW, TLP didn't lock the device after turning it on so i was able to do some clicks, even starting an outgoing call before device was locked by TLP. IF TLP later unlocked the device due to light conditions, now i'm not really sure becasue i don't remember it.

It was the same problem that "no lock at first & i can do some clicks until it gets locked" cases but this time having enough time to start an outgoing call. Sorry for not having been enough clear in my description.

This is a common delay i have but as you said in a previous post it seems related to another process that maybe is eating the CPU time. I will try to list for you my BG running processes when i end upgrading my device to a new ROM and then i will also try to isolate my BG running processes to detect which of them is the CPU eater that doesn't let TLP do its job.

Hope now my problem is clear.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I am testing a solution where I keep the TouchPanel locked or lock when suspending/screen off/power off, and only unlock the hardware keys. Then the problem of the TouchPanel not locked in time should be away. So it is combining the 2 locking mechanism I have.

But, the delay of locking of the hardware keys will still be a problem......that will not be solved with my new approach :mad:

I will try to give TouchLockPro more priority.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
don't worry, your tool is yet fantastic, and you can't control the other BG running process that doesn't let TLP do quickly its job. it's our fault, that we like to have several tools being launched at start that produces these inperfections in the locking mechanism of TLP.

The fact you have found the "can't unlock until i take out stylus" bug cause is a big improvement for your tool.
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Hi ZuinigeRijder,

This is the first time I used your application. I recently upgraded to Duttys V4 ROM from Elite 3.0. I took the opportunity to go through and upgrade my apps.

I like the concept of your app but can’t seem to get it working properly. It does not seem to register any touches on the capacitive sensor. It did at one point but I turned the clock off and set it to Stealth Mode and after that it stopped working and I never got it to work again.

I’m not really running anything else in the background that could be affecting it. The stylus unlocks the device fine. As does when ac power is applied.

I have attached the log file for you to look through...

Would appreciate any advice you could provide.

Edit: Just found this so it mught be a Dutty V4 thing rather then TLP, that said the Capacitive sensor works fine in the camera?! so maybe a team effort...

http://xdaforums.com/showpost.php?p=3141912&postcount=925
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
i tried other double qoutes but it doesn´t work for me. so i´ll post a log-file later
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
[APP][Updated 11-01-2009] TouchLockPro version 2.1

I just uploaded TouchLockPro version 2.1. Hope this version is again more perfect.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I think it has more to do with the new Dutty ROM, because on a previous ROM TouchLockPro was just running fine. Also the same sort of problems are reported on AZTOR X rom. Another indication, it has to do with the ROM, is that people are saying that if TouchFlo3D is disabled and just using the Windows standard Today screen, everything works ok. Of course it can be something in TouchLockPro, you never know, but I doubt it.

Probably it is best to post some questions on the Dutty and AZTOR forum about the problem of the capacitive touches. Maybe they can find the problem in the ROM?

In the log file, I see that TouchLockPro opens/closes the capacitive sensor, e.g.:

0:04:13 1160795422 CapacitiveTouchSensorOpen() finished

0:04:15 1160795422 CapacitiveTouchSensorClose() finished

However, I miss some information, I would also expect some other debug logging. Did you not enable LOGDEBUG=1?

Because it looks like I see only the LOGDEBUGDETAILED messages?

Can you enable that too, so maybe I can see something in the logging?

I also miss the start of the logging (settings), but that is probably also because of missing LOGDEBUG=1.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Version 2.1 fixes this bug (just uploaded). And it locks now already the TouchPanel when screen off/suspend, so at least the TouchPanel cannot be touched anymore at power on. I increased the priority, so maybe also the hardware keys are locked sooner at power on.