yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I only poll when the the phone is locked AND the screen is ON. And the polling is not often, only once per second. So in practice it polls only 5 times :eek:
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
since i started using 1.3, i have noticed that the battery is going down rapidly decreasing.

in 30 minutes my battery drained from 60% to 15% no wifi or bluetooth, and the device wasnt used at all.

has anyone else had this?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you use LockTouchPanelOnly = 1?

Because then I need to disable the input regularly. Maybe I do it now too often? You can try to disable hardware keys AND touchpanel, because then it is not needed. And because the unlocking is now so simple via the light sensor, it may not be needed to lock only the touchpanel......l
[Touch Diamond, MDA Compact IV Themes and Apps] jodeltje:
no it doesn't sense light... I even taped over it to be sure.

I'm trying 1.2 now....

EDIT: guess my phone was having a bad day (or 2) or something, what happened after installing 1.2 and 1.3 again for six billion times had to have been my phones fault.

all is well now, It locks every time, it reacts quick and it keeps locked when I fiddle around with my headset-buttons.

THANKS AGAIN FOR A GREAT APP!!
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
yes i have LockTouchPanelOnly=1, ill try disabling it and see what happens.

can i also ask, now that you managed to hide the battclock properly with

LockIndicator = 0 , when this setting is applied does the capacitative lock work?

in v1.2 i had LockIndocator=0 and the capacitative lock worked, it seems in v1.3 that is no longer working!

thanks for your help
[Touch Diamond, MDA Compact IV Themes and Apps] Pietje_1985:
incorrect lock/unlock status on batterybar

Hey guys!

I'm also using version 1.3..

I noticed that the lock is working correctly, except sometimes the device seems to be locked but then it's unlocked f.e. when I take out stylus and put it back in, the device will unlock but the battery will remain white and when I lock and unlock again, it wil be black (unlocked)....:confused:

Somebody get my point??

Do I need to explain better??

I just wanted to report this....

Cheers

Jeroen
[Touch Diamond, MDA Compact IV Themes and Apps] kd372a:
I too have noticed this behaviour as Pietje_1985 mentions. This also happens in version 1.2.

Basically when the stylus is removed to unlock the phone the BattClock appear Black but the phone is still locked. If the stylus is reinserted and removed the phone is then unlocked.
[Touch Diamond, MDA Compact IV Themes and Apps] Pietje_1985:
So luckily i'm not the only one.....eventhough it's still an amazing app and for me the best locking solution for the diamond so far.....

Hope I can still give a donation to ZuinigeRijder because he's worth it....:rolleyes::D
[Touch Diamond, MDA Compact IV Themes and Apps] kd372a:
Totally agree, by far the best app to lock these HTC touch screen phones. I'm currently using version 1.1 does everything I need, but would like to be able to use the later versions too!
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
along with this behaviour, i have noticed another weird problem when using the light sensor to deactivate the lock.

here is what happens, im using my device for eg txt when i finished i press the power button to turn of my device, which automatically engages the lock and gives me 2 vibrations, and i place the device on my desk next to me with no case/pouch, it is just sat on the surface.

after 2-3 minutes i feel a single vidration to tell me that the device is unlocked again, even though i have not touched it - i know this is what the light sensor is supposed to do but it is an incorrect time for this to happen.

the light sensor is supposed to detect change in light for a specified amount of time, but in this case the luminocity is constant, the device is just unlocking with no change in light.

and i still get really bad battery drain, with v1.2 i have 100% charge at 9am ariving at work, and at 7pm arriving home i have around 40-45%. Today i had 100% at 9am and 22% at 6:50pm, that is an extra loss of 22% just for the light sensor!

is this just me?

I have also been trying to give a donation but i cannot find a link!!!

@ZuinigeRijderhow can we donate? i feel bad constantly getting new builds and solutions to issues i post and not giving anything in return!

Take care

MysticGenius
[Touch Diamond, MDA Compact IV Themes and Apps] Pietje_1985:
Donations!

+1 I totally agree with MysticGenius
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Fine that it now works. I found it strange that it automatically unlocks by TouchLockPro after 10 seconds.....but the reason of the mystery is unclear.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It should work, but I did not try myself, because testing all those combinations takes some time. I will try tomorrow.
[Touch Diamond, MDA Compact IV Themes and Apps] ctrlaltdel:
set only unlock with capacitive sensor and sip change

Hi,

I am wondering how can I can set to use only capacitive sensor as the unlock method while keep use of other sensors (stylus and slider) to work with SIP change only.

I have try disable all other sensors, only left capacitive sensor enable and setup all the SIPs but this will lead to SIP change not work.

then i have enable back stylus and slider sensors and disable all lock and unlock settings related to these two sensor so that i would expect no lock/unlock will be happened when i pull out/push in the stylus and slide out/in the keyboard.

With this setting, the SIP change works. However, now every time i pull the stylus out, it will auto unlock the device and when i put it back it will lock the device, same as the keyboard slide.

I don't want to lock/unlock using either stylus/keyboard, I just want the device unlock by capacitive sensor and the SIP change function work. Is there any way to make this happen?
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
Thank you very much, ZuinigeRijder: as always, a quick and documented answer.

all the best to all
[Touch Diamond, MDA Compact IV Themes and Apps] texasez:
With the same settings, the screen will lock on backlight off for a period of time and then it will quit working so that the touch screen is always unlocked.

The touch screen now will lock every other time when power button is pushed (backlight off). The indicatior at the top show the screen unlocked. I cannot unlock screen with captive touch on middle button. How is that for wierd?

I am enclosing the log file that should show what has been happening.

Larry
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, it is not possible to disable the stylus sensor and keyboard sensor and still use the SIP changer. This is because the Stylus and Keyboard sensor always report IN, when disabled. Of course this can be programmatically changed. But on the other hand, I do not see any use for it.

When you take out the Stylus or open the Keyboard, it does not make sense to keep the phone locked. So what is your use case, keeping the phone locked? Is is a Security thingy :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the description and log file.

Ok, I normally do not use myself only locking the TouchPanel. I tried with exact the same settings, to see if I can reproduce myself. No luck, though.

Still hard to find the problem in a relative large logfile. Looking backwards, I see a couple of times:

8:20:20 1836737706 SetLocked cancelled, stylus out.

8:18:53 1836737706 SetLocked cancelled, stylus out

8:18:51 1836737706 SetLocked cancelled, stylus out

8:18:28 1836737706 SetLocked cancelled, stylus out

8:15:48 1836737706 SetLocked cancelled, stylus out

8:13:29 1836737706 SetLocked cancelled, stylus out

18:16:09 1300179454 SetLocked cancelled, stylus out

18:00:46 762130286 SetLocked cancelled, stylus out

17:43:26 -310668134 SetLocked cancelled, stylus out

I assume, your Stylus was really out?

You know it will never lock, when the Stylus is out?

Or are you one of the people, who sometimes has the famous hardware problem that the Stylus Sensor not always sees the Stylus? Some people have the problem that the Stylus is too far away of the Stylus Sensor, or that there is dust between the Stylus and Sensor?

Of course, you can disable the Stylus Sensor in TouchLockPro, if that is the problem. You can also try to check the Stylus Sensor, by removing the battery and carefully cleaning the Stylus Sensor.

But maybe that is not the problem. So maybe it is a problem of TouchLockPro, but currently I do not have a clue what is wrong then :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] texasez:
At the end of the log file, the screen would be locked and the unlocked on consecutive back light off touches. The battery indicator showed the screen was always unlocked even though the screen was actually locked. The stylus was in. I have taken the battery out and blew the dust if any off the sensor. I will see how that works and let you know. If i can reproduce the problem consistenly I will resent the log file.

Larry
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
I have problems with the capacitive touches. I upload my log file.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, the logging shows clearly that the Stylus was out. So there is something related to the hardware Stylus Sensor. Hope your cleaning solves the problem, otherwise you can disable the Stylus in TLP (but then you cannot unlock anymore via the Stylus and also the SIP changer will not work).

I do not understand why the touchpanel is still locked. I looked again closely to the log file, but did not get the pieces of the puzzle together. It may well be a problem with TLP, in combination with the Stylus out.

Hope the logging, when it occurs again, gives me more insight :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see many many times unlocking by the capacitive touch right.

Can you be more specific what problem you have and when it occurred?

Note that here is a known problem with TF3D, that sometimes capacitive touches are not sensed in newer ROM's, e.g. HTC 2.0.3. Even the TF3D workaround does not always work. Do you have TF3D enabled? Which ROM do you have?
[Touch Diamond, MDA Compact IV Themes and Apps] atego:
posible to create autolok with backlight off

Hello, is it possible to create an autolock with "baclight off" or for ex: autolock in 15 or 30 sec ?

Thank's a lot

Atego
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, it is possible to configure AutoLock on backlight off, see:

SuspendOnBacklightOff (SuspendOnBacklightOff = 1)

Just enable the Checkbox SuspendOnBacklightOff. The time for backlight off you must configure in Windows Mobile.
[Touch Diamond, MDA Compact IV Themes and Apps] texasez:
I took out the battery, used 3m dust remover to blow out stylus sensor and everything has worked great for several days. This must have been my trouble since the start. The program work when the sensor worked but not otherwise.

Thanks for a great program.

Larry
[Touch Diamond, MDA Compact IV Themes and Apps] Icepick66:
With the new version it keeps vibrating twice on lock, even though i set the number of vibrations to 0.

Also, from upgrading from 2.2 to the 2.4 series, my media player hooked buttons no longer work, If I turn off using the power button, no buttons work, if i make the media player turn of the screen the hooked buttons work, and i can change track etc.

But if the powerbutton is accdently hit the phone power button, the phone is relocked and the buttons break again till I unlock and turn off via the media player again. Im aware this is inherent by design, but in version 2.2 this was not the case, anytime/method phone was locked the hooked buttons still functioned.

I know your bundled with 1000's of requests, but not to bloat things up, maybe figure out a way to revert to the old method and use a checkbox option?

or have an program exception list, where if in the program is in the forground the hardware buttons are not locked (this would be most usefull)

I'm tied deciding between the versions as I LOVE the SIP, but hate having to unlock the phone to change tracks every 5 minutes on a run.

Thankyou for your amazing commitment and delopment of this application :)

and thankyou even more for keeping all the old versions available for download!

hey ill even donate a few for a feature that mixes both versions :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I assume you unchecked Vibrate (Vibrate = 0) and Lock (VibratesLock = 0)? Probably you have configured stealth or stripe mode and then you must uncheck Vibrate.

Did you have the same settings for version 2.2 as 2.4. Because I would expect they behave the same? Can you post a debug log file for both versions? Maybe that gives me a clue?

The exception list is on the wish list. I understand the need.

I will see if I can add this in the next version. I am busy on my work, so I did not spend much time on TouchLockPro lately.

No thanks. I learned a lot myself about Windows Mobile programming, just by making a real useful program. Still have a lot on the wish list. And I know, always some improvements can be made, to make it more perfect.
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
The Capacitive Areas

Hi, ZuinigeRijder, and thank you again for this tool.

I have an HTC Fuze, and I am using the version 2.3.4. of TouchLockPro, for two reasons:

- I noticed (empirically, no programming knowledge) that the Capacitive Areas respond better (more consistently, reliable) on this version, comparing with the new ones (and I've read that others noted that, too - but, again, from my part, this is only an observation, nothing scientific)

- I really don't need all that SIP stuff :)

Now, time to time, the Capacitive Areas stop responding to swipes (I allocated those actions to launch a few programs), only to re-start responding again after I Suspend the phone (short press Power button), and Wake it Up again (another short press Power button).

I attached the log files - I got this behavior a few times. If you could (maybe the logs show that, I hope), notice that time to time, I pressed the Power button (so the phone Suspended), then, immediately, I pressed it again, to wake it up. Everytime, I did that because the swipes stopped responding, so maybe there is some useful info right before those "pressings of the Power button", that would tell us what causes the "unresponsiveness"

This finding might be very useful for the future versions of TouchLockPro, making it even more reliable and stable, from this perspective, also.

Really looking forward to your response

thank you very much

cezar
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hi cezar,

thanks for the findings. What happens, is that when you suspend, I close the navsensor. But if you power on too quick, this is not seen as a power on by windows mobile. That explains the behaviour you describe.

Actually, I do not need to bother about closing/opening the sensors, because they do not work anyway when in a sleep (and do not consume battery too). I will try if not closing the sensor works.

I cannot explain why version 2.3.4 is responding better to capacitive swipes. I will compare the latest version with version 2.3.4, maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
Thank you very much for your rapid answer. It seems to me that you already know what's happening. I really have a good feeling that you'll get to the end of it.

Seems that that's why the areas get activated again, because my actions to Suspend/Wake up the phone (using the Power button), actually close/open again the up-mentioned sensors.

It looks like those sensors shut THEMSELVES down (not necessarily because I would Power on too quickly), as I play with other applications, or maybe influenced by them. The only 2 applications that I installed after TLP are WkTask (http://xdaforums.com/showthread.php?t=330855) and iLaunch (http://xdaforums.com/showthread.php?t=497607).

Do you think that using those applications might shut down those sensors?

Is there any way to increase the sensibility of those sensors?

all the best and thank you very much again for all your effort

cezar
[Touch Diamond, MDA Compact IV Themes and Apps] bdemarco:
unlock via round center button

ZuinigeRijder,

Several posters have requested the addition of a feature to unlock by pressing the round center button on a Touch Pro. I second this request. I think what we'd like is to press the power button to wake up the screen, and then unlock by just pressing the center button. Pocketshield has this feature, and it's how I like to unlock my phone.

This is a great program, BTW!

Best wishes,

Brian DeMarco
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hi Brian,

you can configure TouchLockPro to unlock via the center button:

CapacitiveTouchesSequence (CapacitiveTouchesSequence = 2)

This works by the capacitive sensor, not via the key, so you do actually only need to touch the middle center button, instead of pressing. But pressing will also work, because it will be seen as capacitive touch.

Thanks for the donation :)

Rick
[Touch Diamond, MDA Compact IV Themes and Apps] bdemarco:
center button

This does work as you say, except TouchLockPro passes the center button click to the OS. So, after unlocking, the OS takes action on this click and may switch applications, etc. What would be great is if TLP unlocked via a click of the center button, hiding that button click from the OS.

Also, my Touch Pro does not always seem to register a touch on the capacitive region...so I often have to click the center button a few times. I realize that there is a workaround, but I find watching TF3D switching screens when I wake up the phone distracting. Polling for an actual click of the button should be more foolproof.

One last feature request: lock on call start and/or end only when using a bluetooth headset.

Cheers,

Brian
[Touch Diamond, MDA Compact IV Themes and Apps] bdemarco:
one more piece of info...

...I have TLP lock the screen only, so that I can use the hardware buttons to answer a call. I think that this is why the center button click is seen by the OS. Perhaps there's not a way around this, since TLP does not put a window in the foreground like PocketShield and s2u2...

And, you're welcome!

Cheers,

Brian
[Touch Diamond, MDA Compact IV Themes and Apps] varden:
First off all GREAT JOB.

I find this program almost perfect. There is some minor glitch. I use it only to suspend the device after the call (locksuspend).

Is there a way to disable it while on ac power? It would stop my device from suspending while running the nav software.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
What command did you configure? !LOCKSUSPEND

I would expect it would not suspend, when on AC power?
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
Originally Posted by ZuinigeRijder View Post, here "[APP][Updated 16-10-2008]CapacitiveFingerLock (Proof of Concept with sources) "

**I uploaded the C# source code, so you can have a look.

But in the end it is all about the NavSensor API, which gives back the following information:

WPARAM (4 bytes packed into an int)

byte Up; // 0=KeyDown,1=KeyUp

byte Where; // Where the click occurs (left pane, wheel, right pane)

byte xPosRP; // xPos for the Right Pane click

byte yPosRP; // yPos for the Right Pane click

LPARAM (4 bytes packed into an int)

byte xPosLP; // xPos for the Left Pane click

byte yPosLP; // yPos for the Left Pane click

byte WheelAngle; //Wheel click angle

byte Unknown;

I only used the Up en Where for my purpose. Actually for my algorithm I do not need to know exactly where it is touched, the only thing I need to know if it is the same area.

When we want to make more different gestures and actions, it can become important where it is clicked. E.g. 3 times clicked on left pane = action 1, 3 times clicked right pane = action 2, etc.

With my Proof of Concept program it is easily to determine which area is which Where area.

With the xPos and yPos for the right and left pane, you can even get more gestures programmed.

Also the NavWheel can be used, but I did not use this in my program.

Hope this is valuable information for others.**

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

Hi, I am not a programmer, and I wanted to ask you:

First, considering the data above, could you make the swipes on the Capacitive Areas to become more reliable (I am using those swipes as a Launcher of different utilities)? Only if it is possible and it's not too difficult. (By the way, did you consider making an application as a stand-alone Launcher using the Capacitive Areas?)

Secondly, on a previous message, I wrote that, time to time, the nav sensor shuts itself down, and I am using Power off/Power on to re-activate it. I am doing that quite often, and I am concerned about the functionality of the Power button.

Is it possible to get a small application, an "~.exe", that I could put it in Start Menu and use it for re-activating the nav sensors? Something to toggle Power off/ Power on?

again, I am not a programmer, so if my questions are weird, I apologize.

thank you
[Touch Diamond, MDA Compact IV Themes and Apps] varden:
"TouchLockAction.exe" locksuspend

It does suspend on AC power.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think the re-activating the nav sensors does not make a difference. The changes of HTC in 2.03 blocks sometimes the NavSensor (and also the GSensor). Did you not use the locking features of TouchLockPro? Otherwise you cannot press the TouchPanel? Did you not lock the hardware keys?

Probably, when you can get another application get focus (e.g. start menu, task manager, other application), I expect the NavSensor is working again. Because that is the same what the workaround is doing (tab right-tab left). So if you can start another program in the foreground, I expect the sensors are going to work again......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, !LOCKSUSPEND will be faster, because TouchLockAction does not need to be started.

I checked my code and !LOCKSUSPEND does not lock or suspend when AC power is on. ANd also your configuration should not do that.

Can you enable debug logging (logdebug=1 and logdebugdetailed=1), reproduce the problem and post the files \TouchLockPro.log.txt and \TouchLockAction.log.txt as zipped attachment? Please also provide the time when the problem occured.

Because I would expect it would not locksuspend when on AC power......
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
DOes not unlock on receivng a call

I have a TouchPro wih the latest original rom (the one with a slider to answer a call). I have set it up to react to TAPI and unlock the screen on receiving a call. HOwever most of the time when the call comes in the screen is still locked, and before I amage to unlock and answer I have last the call.

Any suggestion on what to do?

Also would it be possible in a future version to choose as an otpion to leave the power button always unlocked? I would like to be able to turn the screen off also when it is locked as well as unlock by briefly pushing the power button. It would be the quickest and most error-free way of unlocking since the power button is never pushed by accident due to the position and it is really easy to get to when you have the phone in your hand to unlock. Any chance it could be implemented? :-)

Thanks a lot. It's a fantastic program.