yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
question for ZR:

is it possible that a part of the gestures combination, you have changed the gestures sensivity from 2.2 to 2.2.1?

i found 2.2 too much sensitive, instead i find 2.2.1 too little sensitive.

can you confirm it?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, the sensitivity has not been changed, but of course the orientation sequence has been changed into 8888.

If you want the same behaviour as 2.2, you must configure UnlockOrientationSequence = 999.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I assume you used version 2.2.1.

Which UnlockOrientationSequence did you configure?

With the default 8888, you must really make a portrait-upsidedown-portrait-upsidedown-portrait move.

And are you sure it does not unlock by the light sensor?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, there is a check if it is within 5 seconds. Maybe it is a bug, introduced in the effort solving your bug. Just post a debug log file, may that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] DomSim:
i turned the light sensor unlock off when testing to make sure it was the orientation that was infact disarming it. i had it set to 3 only for unlock so when it moved to portrait it would unlock. i tried setting it as 93 but still it would unlock at just a slight angle. or even by just jiggling it a bit.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
93 means from that it will unlock any position to portrait. Sometimes the difference between landscape and portrait is just small (also in Opera it switches sometimes to Landscape, where it is just a small angle change). Therefore I configured a greater orientation change as default, portrait or upside down. So instead of 93 I would configure then 88 or 888, or 43, dependent how you put the phone in your pocket.

I did go for the safe side, 8888...
[Touch Diamond, MDA Compact IV Themes and Apps] Kraize:
No. You didn't understand what I meant. I meant that instead of it locking the device on power on, make it lock the device on suspend instead.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, I think I new what you meant.

TouchLockPro can detect a power off/suspend/screen off indirectly (external, by TLP itself, power off). Although TLP does not know which of the direct event it was initiated, it locks the TouchPanel already at suspend.
[Touch Diamond, MDA Compact IV Themes and Apps] Samohtrelhe:
Program failure

Hi ZuinigeRijder

I wonder if you have a solution for this;

After upgrading from 2.0 to 2.1 I cannot go beyond page3 in the configuration?

The TouchLockAction program freezes totally!

Only way out is a quick press on the "home button" and then quickly shutdown TouchLockAction via the "Running programs" overview...

I tried removing, restarting and then reinstall, to no avail :-/

Do you by any chance have some kind of registry cleaner so that it's possible to start from scratch??
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
probably a value is out of range. Just remove the registry tree zuinigerijder with a registry editor
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
I must say, that when installing 2.2 & and also 2.2.1. it happenned exactly the same to me just after installing TLP. It happenned only the first time. the next times everything went smoothly. Curious.
[Touch Diamond, MDA Compact IV Themes and Apps] ice2big:
hi guys may i know how you can unlock using g sensor? :) am using touch hd but i can seem to unlock it using g sensor :P i tried it fast, slow, even configuring it with "99" so that am sure any movement will trigger it stil i cant :(

other than that tis a great program :)
[Touch Diamond, MDA Compact IV Themes and Apps] asci:
I've been using this app since 3 days on my HTC HD and I'm really satisfied of it. The only thing I still can't set properly as I'd like is the lock status on incoming call. When I receive a call, the device light up and remain locked. The light sesnsor is too slow to detect the ambient light and unlock the device, so the most of time I loose my incoming call becouse I can't answer. Who can suggest me the best configuration in order to not loose any call???

THX so much
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not have a Touch HD, but I assumed there was a GSENSOR in it, but maybe that is not the case?

I just subscribe to registry changes to registry key HKLM\Software\HTC\HTCSensor\GSensor\EventChanged

And start/stop the GSENSOR.

You can enable debug logging (logdebug=1 and logdebugdetailed=1), and post the log file \TocuhLockPro.log.txt as zipped attachment. Maybe that gives a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No thanks, hope it suits your needs.
[Touch Diamond, MDA Compact IV Themes and Apps] giovag7:
I like your policy to make this program lightweight and not with a lot of functions. This is the reason because i don't use s2u2. I like too the action screen that you are making. A consideration: this action screen must be very fast to open because if i want lock or power off the phone, a long delay would be unacceptable. For example i am using PsshutXp to sleep the phone, with a link in the left softkey, and it opens quickly. Your action screen has similar speed?

Thank you for your work.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, it will be fast. And if you feed it via command line parameters, it will not show the UI, it does it job and exits. And you do no longer need pshutxp....

I did also fix the power off problem with the original pshutxp......
[Touch Diamond, MDA Compact IV Themes and Apps] shattering:
I can confirm that I can't switch the power back on if I'm using a headset and listening to music via the TF3D. So I have to take out the stylus just to turn it on. This is the only time I can't switch the power back on. And I know it never happens on TouchLock v1.6.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think I have a solution for the Power button problem. The idea is that I no longer lock at power off, but immediately after power on. So the power button problems should be gone then.

I also have tested yesterday at late night (my wife gets :mad:) a solution for only locking the TouchPanel. And it seems to work now.

But I have to find free time for further testing this, without giving too less time to my family. So be patient....
[Touch Diamond, MDA Compact IV Themes and Apps] nazimster:
a Question

Is it Work on HTC p3450 Touch ELF?......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, I do not think so. That does not have the magnetic stylus and its sensor and also does not have the capacitive hardware area.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have uploaded version 1.2, which has the possibility of LockTouchPanel = 1.

But be careful, I do not know it will work in all situations. But maybe it is good enough for incoming calls :confused:

Anyway, the triple touch must be done without touching the other areas in between. In version 1.2 I also changed the timeout of the clock into 8 seconds locked, 1 second unlocked.

My personal experience is that you can best press the area 1 or 3 (see post #2). That area seems more sensitive and the advantage is that it can be done one-handed too.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro used by Touch Pro users?

Is it working as expected, also for the capacitive sensor?

One addition, especially for Touch Pro users, would be the detection of the keyboard slider. However, I do not own a Touch Pro.

I asked for information about this in this post: http://xdaforums.com/showthread.php?t=442472

I did not get a reaction. If someone is interested in this, I would like that someone is trying to find out if this can be detected by a registry key or API.
[Touch Diamond, MDA Compact IV Themes and Apps] snufkin:
I have just downloaded v1.2. BTW, I have two problems:

- batt drains very fast in this version. I have 22% of battery remained before the installation and after playing for 5 min, it dropped to 14% :(

- the capacitive unlock responded very slowly and only the "back" key is responsive. all other areas are very very non-responsive. that was not the case for v1.1.

- the power on button can only be responsive after power off for some times, say 30 sec.

Anyway, keep up your good work. This concept is now I think the most "logical" locking tools for me.
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
Thankyou muchly, i will install right away and start using!!

Thanks again for addressing the issue SO fast!!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I myself do not have that experience. Are you sure some other applications is draining the battery (e.g. ActiveSync, bluetooth, Wifi)?

Did you use the standard settings, or did you use the TouchLockPanel only = 1 overrule. The latter consumes a bit more CPU, because it has to power off the touchpanel regularly and on event basis, when the display is on.

Check with a Task manager how much CPU is used, you will see it is neglectibale......
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
OK,

Installed and locktouchpanelonly works, but there is something weird happening with the battclock, it is not displaying correctly, it is displayed and a black rectangle with white artefacts over it in a random pattern, see screen shot, it is as if it is trying to hide!!

(Maybe you have stumbled on a way to hide the clock?) Is there any settings i can use to make it appear "not there"?

I have the following settings:

AutoLockOnPowerOn=1

Beep=0

LockIndicator=0

LockTouchPanelOnly=1 <--THANKYOU SO MUCH!!! :):)

StylusAlwaysControl=0

StylusOutInToggleTime=700 (2dc hex)

SuspendOnBacklightOff=1

UnlockOnACPower=1

Vidrate=1

I can also say that the capacitive touch is much better with the longer time.

Thankyou also for allowing the use of the power button when the lock is enabled!!

Hope this helps
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, I tried to make a transparent clock, when LockIndicator=0.

But I did not test all the improvements, so this is one which did not improve :mad:

You can still make the width and the height of the clock small, or 1 pixel, to let it disappear on a neat place.

Anyway, we need a form of at least 1 pixel.

Probably I am going to revert the changes for making the locked clock invisible in a next version. Or I must find a better solution.
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
Would it not be possible that when LockIndicator=0, the clock is automatically changed to a 1 x 1 (i.e a single pixel) and placed in the red circled area in my attachment? as this would still allow capacitive touch, and also hide the clock.

(out of curiosity, what would the reg settings be to have the clock as i describe? because it would be a perfect "quick fix" personally i think the area at the top-right would be the best area for the pixel, what do you think?)

Thanks for you help

EDIT: Changed Screenshot
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
See post #3 and #25

You can also overrule the default foreground and background color.
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
would i be correct in these settings:

ClockX=478

ClockWidth=2

ClockHeight=5

ClockBackground=0

ClockForeground=0

this would give a 2x5 black strip @ 478pixels across?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yep. But you will not see when it is locked, when the background of your startbar is also black.......

But that maybe what you want. In that case I would set the Width and Height to 1 pixel.
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
Using the setting i posted earlier, 2x5 is a nice size for the indicator, but for some reason it is not showing as black, it is displaying grey! (which it better than earlier

Even through using styluslock i never had the indicator showing, as i always have my device locked when in pocket because of the pouch i use!

thanks
[Touch Diamond, MDA Compact IV Themes and Apps] devrard:
Touch HD

Hi,

I've tried v1.2 on my Touch Hd, and it gives me the following error message: 'unable to load HTC API DLL'. I need to remove the stylus to unlock and then execute the program again to disable.

Something you can fix ?

tx
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In case it does not unlock fast enough, just take out the stylus.
[Touch Diamond, MDA Compact IV Themes and Apps] asci:
Uhm not comfortable...

THX anyway...
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Hi. Yeah I had the same issue with TLP & to me the light sensor isn't too useful so I disable it. (Sometimes it unlocks when you don't want & sometimes won't unlock when you do so not real reliable.)

For me I also set LockTouchPanelOnly since when the phone is asleep none of the hardware keys (except power) do anything anyway to accidentally press so as long as I lock before putting in my pocket the only risk is while phone is ringing in my pocket & I take it out ringing. During that time I sometimes press volume on accident (wish I could lock just those but not end of the world) but it is very hard to accidentally press the front keys since I grab phone from top & those keys are flat & require more of a press than the volume keys. Then I just press answer or end key as required & I never miss calls because of lock. :)

That setup also works well for dialing *recent* (in/out/missed) people too without full unlock.. I press power to wake it up then press the talk button then down arrow to the person & press talk again. I can also end it without unlocking. Of course if I want to dial a certain # or person not in my call history I have to unlock the screen & dial it but 95% of the time the person I am calling is right there waiting.

I have messed with gsensor unlock & it does seem more reliable than capacitive touch (unless direct works better later) but it is still more cumbersome than I really want to deal with when hurrying to answer a call so for now disabled light sensor & LockTouchPanelOnly is how I run it.

Hope that helps.

Bill
[Touch Diamond, MDA Compact IV Themes and Apps] Martinvhv:
HTC Touch hd and slider function in error ?

I'm having the touch hd for 1 week , and just tried to have an unlock situation when having an incoming call (and use slider function) with touchlockpro.

Settings used for;

- CommandCallIncoming = TouchLockAction.exe

I tried 0 and 1 settings for;

- Lock when incoming

- Autolock in power on

Problem;

The HD unlocks (inversed battery sign goes off)when call comes in, but slider is still not in function and touchlockaction screen pops up > can not reply on call.

Question;

What settings should I use for "Lock when incoming/Autolock in power" ? Or is there a must for other settings for having the correct function ?

Thank you !
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
CommandCallIncoming = TouchLockAction.exe is causing the popup.

If you want automatically unlocking at incoming call, you should configure:

CommandCallIncoming = "TouchLockAction.exe" unlock

But mostly, people just use the AutoLockOnPowerOn=1 and just let the light sensor unlock. If there is not enough light, you can take out the stylus. If that is not convenient, you can consider only to lock the touchpanel: TouchPanelOnly=1. You can then pick up using the hardware keys (but also accidently rejecting calls).
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Hey ZuinigeRijder,

I think it is easy to misunderstand the notation of showing example settings like "TouchPanelOnly=1" vs the command line option for CommandCallIncoming like "TouchLockAction.exe" unlock especially since values are stored in registry & not an INI config file.. I am very experienced in computers & WM phones & it threw me at 1st (thinking "now how do I edit the file to put those?") but didn't help when you put wrong options on your site. :P (Your site still shows CommandCallConnected example with lock when lock is not a valid option. hehe)

Hey also, I was wondering something & your comment about accidental call reject reminded me of it. I recall you said you currently cannot lock certain keys (like unlock power & answer but keep volume & end keys locked for example) but perhaps would it be possible to instead re-map those keys instead of locking them? On my old WM5 phone I could make special shortcuts that made different programs run depending on the key I pressed (like short press on camera button toggled the screen brightness & long press brought up camera app) but what I found is if I mapped to a program that didn't exist it would in essence lock the key because pressing it did nothing.. I don't think WM6.1 works the same way but I assume there is way to map keys to 'nothing' when you want them 'locked' then map them back to what they are supposed to do when you want them 'unlocked'. (Or maybe if the key was mapped so you could read the presses that would allow unlock with key presses like hold down for 2 seconds release then press briefly within 1 second or such) Anyhow just a thought. I'm going to dig into some key mapping programs & see what I can do with which keys to play a bit.

Thanks,

Bill
[Touch Diamond, MDA Compact IV Themes and Apps] ice2big:
i have a g-sensor i can find it in the setting->system.

also following HKLM\Software\HTC\HTCSensor\GSensor\EventChanged

i have the number "2"

by the way here's all the date under here maybe will help :)

CheckingTime 500

DeviceAvialability 1

Eventchanged 2

Faceupanglethreshold 30

faceupasportrait 1

faceuptolandscape 0

faceuptolandscapethreshold 47

kbdslideout_to_stop_gsensor 1

landscapeanglethreshold 35

landscapetop0threshold 40

notifyapprotationmask 63

phonecallmute 0

posturechangealarm 0

rotateanglethreshold 45

rotateanglethresholdex 35

tilinganglethreshold 20

tilinganglethresholdex 35

also: when my phone is lock. I can still use the power button but yet i cant use any key meaning it is still lock. But when my phone is lock then i press "up" or "down" (volume keys on touch hd) on my phone i notice that the lock will be release but yet it wont wake up :( i mean the LCD is still off. when i press power button then will wake up and all keys are usable.so as the touch panel.

ok ill post the log files later.

thanks

edit: log files attached
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Normally, you just use the LockToucAction screens for configuring the settings, in the posts it is more easy to mention the values.

The problem with the ini file, is that it will be removed when reinstalled, the registry will stay. Also communicating via the registry between TouchLockPro and TouchLockAction is very convenient.

If you want to restore your settings, you should export/import the registry keys with a decent registry setting. I think there are even tools which can embed registry files inside a CAB, so with a new ROM or hard reset easily the settings can be restored.

I have asked Dredger97 of DredSensor how he did the locking of the hardware keys. He is hooking the hardware keys:

With the API I use, the problem is that i loose my "hooking" really often, for reasons as:

- another background app decide to use the same api

- a menu popup

- another window comes to front

- etc...

So it's not a really strong way to "lock" the keys.

Maybe it is good enough for TouchLockPro, always lock the touchpanel and hooking the hardware keys and rehooking if it is necessary. I do not have source code, but I will give it a try. If someone can provide me already functional source code :confused:, this would be great, this will save me time :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I see in the logging that orientations are picked up, so the sensors are working.

I also see in the logging that it is unlocked 4 times by the GSENSOR, e.g.:

10:08:02 200445810 SetOrientation: 1

10:08:02 200445810 ==================UNLOCK BY GSENSOR ORIENTATION==========================

The GSENSOR will only be used for unlocking, when the power is on/screen on. It will NOT wake your phone, so you need to use the Power button or Stylus (what is done too, I see in the logging) to wake up the phone.

I do not understand the behaviour of the Vlume Up/Down, because those buttons are also locked normally.

CheckingTime 500 seems to me a bit slow, I have the default 200 on my Touch Diamond.

Setting the unlocking by 99 does not seem a good idea, because it will unlock really fast, even in your pocket.

My conclusion:

- the unlocking by the GSENSOR orientation works

- maybe there is a misconception about the unlocking, it will only unlock when the screen is on.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Capacitive Touches with TFL3D on newer ROM's

I did get an answer from Nicholas of MobileSRC GScroll for the capacitive touches not working on the newer ROM's in combination with TFL3D:

Hey sorry for the delay.

I actually use a pretty simple method to get all the touches. I subclass the foreground window (works because windows mobile 5.0 uses a shared memory model) with my own wndproc and initialize the nav on that hwnd, and then intercept the messages. It is very difficult to debug, but works really well once you get it set up. If you have any other questions, let me know.

-Nicholas

So I am trying to do the same. Probably I need to re-subclass, when the foreground window changes, but that should not be a problem. I will see if I can experiment with this coming week. First I need to find how to find the foreground window. Yes, although it looks like I am experienced, I am pretty new to Windows Mobile programming :cool: But Google is my friend.
[Touch Diamond, MDA Compact IV Themes and Apps] ice2big:
ohh i thought it will also wake up from suspend :) hehehe ill explore the software more thanks :)
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Oh I definitely understand *why* you do it that way I'm just saying why I think people sometimes get confused with your examples. ;) Can't say I could come up with a better method either.

And yeah I know about export/import using regedit but the amount of time to navigate to the keys to export & save the file is almost as much time as just going into TLP config & setting the values. Heck if the delay between screens wasn't so big & the keyboard didn't block the fields I bet I could just set values quicker than export/import! :D

Hmm the DredSensor method might prove promising! I will look around for some source but I don't have any myself. I will focus on apps that remap keys as that is likely a simple method to 'lock' them by mapping to nothing although might not be possible with special keys..

Thanks!

Bill
[Touch Diamond, MDA Compact IV Themes and Apps] NotLutzik:
Is there anyway to lock buttons but not screen during incoming call ?

Also is there way to turn unlocking by light sensor during incoming call?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, at the moment the locking of the keys also locks the screen.

Why would you want to lock the buttons and not the screen?

Because you are using a slide to answer screen, and you only want to pick up using the slider?

You mean, disable light sensor unlocking during incoming call?

This is possible:

CommandCallIncoming="TouchLockAction.exe" DisableUnlockOnLightSensorTime

CommandCallEnded = "TouchLockAction.exe" EnableUnlockOnLightSensorTime

But probably you have to make the UnlockOnLightSensorTime longer, because it takes some time, till TouchLockAction is executed...