yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

i see you have a HTC touch Pro 2. During a phone call and when the monitor is turned off (eg by you pressing the on/off button) what happends if you press the area left of the HTC logo - is the screen turned back on again ? Could you test - that happends for me - strange

thanks

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I uninstall my InCall Tweak to use your version :D

Now, when I put it on my ear, it turn the scrren off, but it does not want to turn it back on. Even when I press the power button durring a call, the screen keeps turning itself off :confused:

Please help...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will add the reverselandscape in a next version. I think the original InCallTweak did also not have this, but I can understand this one is also handy.

The light sensor unlock is independent of the InCallTweak. So it will unlock the same as before. So e.g. you can configure not to unlock via light sensor when bluetooth is active.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I cannot see anything strange in the logging, except that it looks like indeed not always the GSENSOR orientation is sensed.

Are you using TF3D? I know there are problems sometimes with the navsensor in combination with TF3D, maybe the same is true for GSENSOR?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear you like the software :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks :) I still try to improve step by step. I am now busy with configuration setting to switch to HTCLockAPI = 1 when Bluetooth is active and to the other locking method when no bluetooth is active. Then you can get the best of both worlds.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
What sort of phone do you have, a CDMA kind?

Because it looks like the locking method does not work for (some) CDMA devices. But some others also have sometimes this problem.

So for now you will have to do with the default locktouchpanelonly = 0 setting.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
What do you have for powersettings, as described in post #250.

Apparently, some devices and due to some settings the LockTouchPanelOnly sometimes works and sometimes not. Actually, the design I needed to do is also not so nice. Frequently disabling the power of the touchpanel. And then still, rarely touches will reacted on.

So I think you can best stick to the default LockTouchPanelOnly = 0.

I will write a summarize/brainstorm post.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The 5 seconds looks like the light sensor is unlocking your phone. Maybe you have a very sensitive light sensor. Mine is by all means not sensitive.

Can you enable logdebug = 1 and logdebugdetailed = 1 and post the logfile as attachment? So then we know what the cause of unlocking is.

If it is related to the sensor, you can tune the sensitivity with the setting UnlockOnLightMinimumValue (See post #3)

Or you can disable the light sensor via setting UnlockOnLightSensorTime = 0 as already replied.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Summarizing LockTouchPanelOnly = 1

Apparently LockTouchPanelOnly = 1 is not working on CDMA devices. On other devices it is working for some people and for others not.

Conclusion:

- be careful with this setting, because it can give strange results, missed calls, etc.

- if it works fine for you, you may use it on own risk

However, the design of setting "LockTouchPanelOnly = 1" is not 100% fool proof. I have to disable the power of the touchpanel regularly to keep it locked. This will also have effect on the battery/CPU, I guess.

So ultimately, the only reliable and good method is locking the hardware keys and touchpanel. That is also the default setting and I am also using this. Especially, because you can also press hardware keys when in your pocket and/or pouch.

But......there are also inconveniences, when also the hardware buttons are locked:

1) you always have to unlock first, before you can answer/reject a call. So this takes some time

2) When the phone is locked and you want to suspend immediately (you do not want to wait for the BackLight Off), you first need to unlock and then press the Power button to go to sleep.

3) when answering a phone call the screen goes off and when you want to end the call, the hardware keys are locked

Maybe there are other inconveniences with this setting, please let me know, so we can make the list of inconveniences complete.

Brainstorm

With version 1.5 it is now quit easy to unlock via the triple touch. Also the light sensor can unlock within 5 seconds, if there is enough light. And taking out the stylus is an option. So in practice 1) and 2) is less a problem, although you need to do too much actions. Less is better.

The real problem lies currently in 3), I guess. Because you want to end the call and that is not possible with the screen off and the hardware keys locked. A possible solution could be, to detect that a call is answered, and the result of that is that the screen goes off. This state must then be remembered "once" by TouchLockPro, so then the hardware keys must NOT be locked.

Hmmmm, wait a moment, in the current TouchLockPro 1.5 version I enable the hardware keys when the screen goes off and autlockonpoweron is set :rolleyes:

I only disable them again at power on. So actually you should be able to end a call via the hardware buttons, as long as the screen is off :)

So only when the screen goes on and you are still in a call, TouchLockPro should not lock the hardware keys/touchpanel. Do I miss something in mine brainstorm :confused:

Maybe others want to contribute to the brainstorm :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] Bäcker:
ptravelalarm

hi

love this program - seems to work quite nice.

only one problem with ptravelalarm. The alarm activates, and your program resuspends the phone after some seconds so the alarm stops.

without touchlockpro ptravelalarm seems to prevent windows from going into suspend

Is there a solution to exlcude a certain program or sth like that?
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
ZuinigeRijder,

I started to experiment with CSDEVCTRL and it does work well for my Sprint CDMA phone. While it is not as elegant as your solution, it does secure my touch panel. You may want to take a look at how it locks only the touch panel and allows access to the other keys even during an incoming call. Further, you could still use capacitive touch to unlock the panel. ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ardavila73:
Thank yoy

Just for you to know

This last version (1.5) is working fine to me, with the LockTouchPanel=1 functioning OK. Perfect!

Thank you very much, I´ve seen how much time and work you have spent on this. Greetings

André
[Touch Diamond, MDA Compact IV Themes and Apps] cipollino:
on the blackstone (htc-hd) works fine :)

thankyou very much

regard
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear it is working for you :)

Just enjoy the software.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Great. I suspect the capacitive unlock is not working (but maybe it is).

Can you tell what is working :confused:

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] GriFolle:
Hi Zuning!

First of all I have to say 2 big THK U: 1) For your work 2) For your help on debugging your app...

Answering your question:

No, I've got a GSM device (I live in Italy) and I'm not using anymore the LockOnlyTP feature...moreover, just to test it, I've disabled the Lightsensor too...

Results? Nothing appens: same issues in same conditions (with 1.4 or 1.5) :(

2 questions:

-Could you gently tell me how to completly remove your app to reinstall it "from 0"? Simply remove the program from WM settings and then delete its reg keys in HKCU/software/zuni.. or there are others keys/files to delete?

-I've noticed that the last version 1.5 drains a little more battery than 1.0 and 1.1...is it just my imagination or do you think that it's possible?

TIA a lot for your effort.
[Touch Diamond, MDA Compact IV Themes and Apps] Pietje_1985:
You see...

At this very moment i'm using the V1.5 without any problems...

ok ok I don´t use the locktouchpanelonly=1. but it's working fine by me, doesn't notice any batterydrain or so...or it could be just me:rolleyes::D

Neways still amazing work!

However ZuinigeRijder...I can't use PAYPAL for donating you.....:(

Regards

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

thanks for the latest update of your great application!

Just one question left for me (didn't found any answer so far): Is it like that TouchLockPro unlocks the device if I take it out of my (dark) pocket and rise it into the light while an incoming call? Or is there no automatic unlocking mechanism for the incoming call event in combination with the light sensor?

Cheers

Punga
[Touch Diamond, MDA Compact IV Themes and Apps] Bäcker:
"SuspendOnBacklightOff = 0" seems to do the trick

problem solved, hopefully :)
[Touch Diamond, MDA Compact IV Themes and Apps] igavio:
Unlock with password

Sometimes you need to leave your phone unattended and you don't want anyone to see your messages or calendar.

I wonder if it is possible to offer the option of locking/unlocking with a password. Pressing a specific key combination would engage a 'strong' lock. Unlocking the phone, would be only possible after entering the password.

This functionality seems to be so needed, that I wonder why all locking programs would not implement it...

igavio, Greece
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the testing effort from your side too.

Can you enable "logdebug = 1" and "logdebugdetailed = 1" in the registry as described in post #3 and post the log file as zipped-attachment. Then I can have a look, why it unlocks after 5 seconds.

Uninstalling is just done via Start -> Settings -> System -> Remove Programs

And you can delete the keys by removing:

HKCU\Software\ZuinigeRijder
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have asked the developer how partial locking is done in CSDEVCTRL. Hope to hear something back.

AnswerkeyDisabler is based on the same partial locking method as TouchLockPro does.

SensorLock had also the same strategy, but has changed the partial locking code from version 0.3.1 onwards. Does SensorLock work on you CDMA device?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, the default settings will unlock the phone 5 seconds after it senses light. But the light sensor is not so sensitive, so in dark conditions it will not auto-unlock and you need to do the triple touch or take out the Stylus.

So yes, there automatic unlocking mechanism for the incoming call event in combination with the light sensor. It will do this in all situations, when it is locked and there is enough light.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
That makes sense. Apparently your backlight settings are such, that it goes off rather quick in combination the alarm application.

Good to hear that this was your problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Of course, there is the default Windows Mobile password option, although this is more for startup of the phone (and protecting it only in that situation).

But unlocking with a password will be really painfull, when there is an incoming call.......before you have entered the password.....the call is ended.

So this makes only sense if there is an easy unlocking mechanism, only known by you.

Are more people begging for such an feature?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see that you disabled the GSENSOR:

cmdOrientationTime: 0

CmdOrientationWhenUnlocked: 0

The InCallTweak is using the GSENSOR orientation changes. So you need to enable the GSENSOR. If you do not want GSENSOR commands executed, you can just make the GSensor commands empty:

CmdOrientation1:

CmdOrientation2:

CmdOrientation3:

CmdOrientation4:

Currently I have programmed, that when bluetooth is active, then the screen will go off, when it goes on again (due to the InCallTweak). The question is if that is desirable behaviour, or should I only do that dependent on the GSensor orientation :confused: I was in the understanding that when bluetooth is active, you do not need to use the InCallTwake to make the screen on, but maybe I did not cover then all use cases :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
I use SPB Shell 3.5. I think the problem is that the rom that I use have G-sensor 2. But I use "Touch Incall" and it works perfect.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I asked the author of Touch InCall if he did something special to support GSensor 2 and if he can have a look at my GSensor source code and if he wants to share his GSensor related source code.....
[Touch Diamond, MDA Compact IV Themes and Apps] c0de_junkie:
i have any idea for and unlock method on touch pro2's, some type of slide on the zoom bar? what do you guys think?
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Sounds like a brilliant idea -i would like such feature too.

BTW, i see you have a Touch Pro 2: coul you check for me, when you a during a call and the screen is turned off (either via TLP of youhave pushed the on/off button) - does your screen light up again f you touch the area left of the HTC logo ? Mine does - i want to know if its a HTC TP2 thing or its just mine

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Absolutely!

This could probably also work on the Touch Pro (1) and Diamond possibly by making a circle either clockwise or counter-clockwise on the nav pad like how you zoom in and out in Opera.

Sounds like work though. God bless ZuinigeRijder for all he does for free!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
GSENSOR 2 test version

I looked at the (managed) GSensor source code of TouchInCall and I have the same logic, only in unmanaged code.

However, I made a test version, with some slight modifications:

- I now close the GSensor when going to deep sleep

- I now wait 1 second before opening the GSensor again

- I now also start/stop the GSensor service

- I added detailed debug logging og the GSensor values read out when they are different (so the logging can become huge)

Can people with the GSENSOR 2 problems test the attached TouchLockPro.exe :confused:

Steps to reproduce:

- unzip TouchLockPro.zip

- copy TouchLockPro.exe to a temporary place on your internal memory card

- stop the installed/running TouchLockPro by running TouchLockPro.exe in Programs menu

- delete \TouchLockPro.log.txt

- start TouchLockAction.exe in the programs menu and enable Debug Logging

- exit TouchLockAction

- start the copied test version of TouchLockPro.exe by clicking on it via the explorer

- wait till it is started and the BattClock is shown

- start TouchLockAction.exe again from the programs menu and go to Settings -> GSensor settings menu

- make moves with your phone, the GSensor orientation changes should be visible in the TouchLockAction GSensor settings screen

- power your phone off with the power button

- wait 30 seconds

- power on your phone and make moves again in TouchLockAction and see the orientation changes

- disable Debug logging via TouchLockAction.exe

- stop TouchLockPro.exe

- remove the test version from your internal memory card (or keep it for further testing ;)

- post the debug log file \TouchLockPro.log.txt

Hope it works or I can see what is wrong in the logging :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] Thalys:
Only lock Hardwarebuttons when get incoming call?

Hi,...

I just downloaded this little Helper, because S2U2 has some problems with SPB Mobile Shell. I want to use it only for deactivating the Hardwarebuttons when i get an incoming call, like the CallerID from S2A did, so i can only use the slider to answer the call.

All other features should be disabled.

Is this possible? And how do i config this? I tried some settings, but the hardwarebuttons were allways active :(

Many thanks in advance ... Thalys
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
With the default settings (You can revert to default settings via TouchLockAction About screen), you must change (see Settings):

AutoLockOnPowerOn (AutoLockOnPowerOn = 0)

LockWhenIncoming (LockWhenIncoming = 1)

KeysOnly (LockWhenIncomingKeyOnly = 1)

And if you do not want to unlock on light sensor, you can disable Use Light Sensor. And all the other sensors you do not need.
[Touch Diamond, MDA Compact IV Themes and Apps] VETTEPC123:
tilt 2 problems

I have the Tilt 2 with a custom ROM and i installed touchlock pro version 2.7.6. One thing i am having a problem with is that when i turn the screen on the lock sometimes takes up to 10 seconds to turn on and sometimes never becomes active at all. Other times i turn the screen on and it is locked immediately. Did i screw something up in settings or does anyone have an idea of what may be causing the delay. TIA
[Touch Diamond, MDA Compact IV Themes and Apps] VETTEPC123:
just to add to my last post, i have noticed that the locking delay happens when the screen has been off for a little while. when it is turned back on it takes a bit for the phone to lock or sometimes it doesnt lock at all. when i turn the screen off then turn it back on within a couple seconds the lock activates immediately. i would imagine it has something to do with the phone going into a deep sleep. is there a way to change a setting in TLP or the phone itself so that this doesnt happen. thanks again
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro is reacting on power on. When you press the power button, the phone does not go off immediately, but gives the programs time to react on it. So when you put the screen on again within this time, it will not lock. Probably that is the case :confused: But you can enable debug logging, reproduce the scenario, note the exact time and post the log file \TouchLockPro.log.txt as zipped attachment. Maybe that gives me enough information, to maybe improve this behaviour.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, if people have problems with GSENSOR 2, I need help to possibly solve the problem, because I have a Touch Diamond :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Potential Stylus Setting Issue Maybe

I just installed 2.7.6 - switched back to the beloved TLP after issues with PocketShield.

I have it set to unlock on stylus out, which works, but when I put the stylus back in it locks. I don't want it to do that. Is there a setting that I am overlooking? I don't remember it doing this in previous versions. I have:

UseStylus checked

SuspendOnStylusIn unchecked

StylusOutDisablesLockMode unchecked

I have tried setting StylusOutInToggleTime to 1000, 0, and 1, and that does not seem to make a difference.

I am running that latest ROM from Calkulin v4.1 on my Sprint (CDMA) Touch Pro.

The issue also exists with the sliding keyboard. Slide out unlocks (which is desired) but Slide in locks (which is not desired)

Let me know if you would like me to upload a log file.

Thanks

EDIT: More Info: If I unlock with a button (i.e. the center action button) then removing and reinserting the stylus does not lock the device, and this is good. It is only when the device unlocks with the stylus that putting the stylus back in relocks it.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Stripe Repaint and Timeout Potential Issue?

This issue may be caused by the fact that I am running a 6.5.1 rom that has the larger bottom bar and smaller top bar. There is an app (I think) that moves windows up 15 pixels or so in order to compensate for this UI difference and (I think) it is causing TLP to continually repaint the lock stripe and (I think) it is doing something to interefere with the timer to turn off the device after 30 secs when locked because when it is locked the screen never turns off by itself like it should. I have attached the log file for this.

EDIT: More Info and Correction: The timer thing is not an issue. It did not turn off the screen because it was on AC power. When I took it off AC power the timer worked perfectly and turned off the device after 20 seconds (I changed it from the default 30 to 20) - but the continual repainting still occurs - but that is not really a big deal - so .... never mind - unless you just want to look into it anyway
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is because you did set:

StylusOutDisablesLockMode = 0

So it will lock again when putting the Stylus back in.

If you set StylusOutDisablesLockMode = 1, then you should not have a problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked into the log file and see you did set the following settings:

ClockX: 0

ClockY: 35

ClockWidth: 640

ClockHeight: 10

Maybe the problem is related to setting ClockY to 35? Did you do this on purpose?
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
I guess that will do. It worked. However, I would still prefer to be able to lock regardless of whether the stylus is in or out, and just unlock when it changes from in to out. But that's not too important so I'm good with how it is.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Yes, the ClockY: 35 is on purpose. I like for the stripe to be directly under the top task bar, and in Windows Mobile 6.5.1 the top taskbar is 35 pixels tall. I have a battery gauge stripe from another program that is at the very top....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, but then I would expect a ClockHeight of 1 instead of 10
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
1 is too thin. I like 10 better because it is more noticable when it's locked. Not sure why that would make a difference.
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
How can i fix the problem with the clock on wm 6.5.1?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
If the top bar is only 35 pixels tall, I would expect ClockY = 25 with ClockHeight = 10.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I understand the task bar is only 35 pixels tall, so you should adjust the clock settings, so the height matches the height of the task bar. Within the BattClock settings screen, you can interactively change the size and position of the BattClock to match the taskbar size.

Or is there another problem :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
When is one digit in hour number, icons are in one position and when are two digits icons move.

Sorry for my english
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
apparently there is not enough space for the text.

You can make the fontsize smaller in the BattClock settings screen, e.g.:

FontSize (FontSize = 14)

Can you also post a screenshot, so I know how it looks like :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
If I did that then the stripe would cover part of my taskbar which does not look very good. It looks better under the taskbar. ClockY = 35 and ClockHeight = 10 looks good and is exactly how I like it. Unless maybe there is a way to position it at the bottom of the screen; does that functionality eixsts? Like maybe ClockY = -10 ClockHeight = 10? If not, that is fine, it looks good where it is
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, so the stripe is drawn just below the taskbar. A negative value of ClockY will indeed be computed as screenHeight + ClockY, taking care of portrait and landscape mode. However, I do not know if this is shown at the bottom of the screen (or covered by an application), but you can try.
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
I Upload two captured images.the first image is when is one digit in hour number. And the second one is when are two digits