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

Maybe your Proven ROM has same issue as Dutty's new v4:

http://xdaforums.com/showthread.php?p=3165842#post3165842

Assuming you have the task manager shortcut in upper right, try touching it 2x in a row when TLP has it locked to see if you can then touch the capacitive area..

Also, you can't be surprised if there is conflict between TLP & Gscroll since they both read in touches from the background & could easily do so at the same time. ;) Maybe it is designed for multiple apps to read the sensor concurrently, I'm not sure. Or if not polled maybe they use events & they can both be notified or just 1st or last or.. Lots of possibilities. Perhaps simple check is remove Gscroll & soft reset to test & see if it really is TLP problem..

Bill
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
i custom cooked this rom taking out the task manager! so i can't.

BTW the capacitive area taping used to work good most of the time using 2.0 releases. but i will check it turning gscroll off to see...

And Gscroll detects tapping in left & Right Top & Down capacitive areas, TLP is configured for the centered capacitive area that seems to be ignored by Gscroll.
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Hmm Bummer! lol Maybe you can just run the exe or find a cab to test..

Well the capacitive touch issue with Dutty v4 happens with 1.8 & 2.0 TLP for me but I'm guessing the problem has always been there it just happened to show up or get worse with recent rom updates. I recall that before sometimes the touches wouldn't unlock but rarely & can partially be contributed to the fact touches in areas you were touching when powering on do not register (like if you had your thumb touch End key area holding it to power on) but there were even more rare times where I was certain I wasn't touching the front at all & TLP didn't register.. Are you sure you're not touching the front when the phone wakes up?

If none of those are the case I'd say gscroll is fighting with TLP so let us know if removing it helps.
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
I have the same issue.

Do you happen to run PhoneAlarm or some other program that controls the vibrate function? I thought maybe PhoneAlarm was interfering with the vibrate function on mine.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The settings are indeed stored in the registry, below: HKCU\Software\ZuinigeRijder\LockSettings

Note that TouchLockPro does not remove these registry settings during deinstallation/installation. So if you upgrade TLP, it will keep the already defined settings. Only if there are new settings, they will be added. Also, when the default settings are changed in a newer version, still the old setting is picked up. If you want to make sure you use all the default settings, press the middle button at the bottom of the first settings screen.

So the settings will only be lost, when you hard reset the device. Of course you can export/import the settings with a decent registry editor and keep it in a safe place.

Hope this helps and clarifies things.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, so summarizing: if you press the task manager in the upper right of the touchpanel, it looks like TLP regains mostly capacitive focus.

However, this will only work, when you did NOT lock the hardware buttons, because then also that area is blocked. So this is only a solution for people using LockTouchPanelOnly=1. But then you can also couple a unlock command to a hardware button. Hmmm, maybe I can simulate presses on the task manager location, when TLP is locked :rolleyes:, this would even work when the TouchPanel is locked (including hardware keys).

Unfortunately I did not get an answer from GScroll about the question I did ask on the forum.

About locking the touchpanel only and the task manager can still be touched. I basically reused the code from sensorlock, where this issue is described in that forum.

My tryout of a different way of locking the hardware buttons did not succeed. The idea was to use G(ame)API for getting the hardware input (GXOpenInput() and GXCloseInput()), but unfortunately this does not work when I am not the main window :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The HD does indeed not have the capacitive touches (as I know), so unlocking will not work via that way.

Also the light sensor is not so sensitive, so in even not too dark lighting conditions, it will still not see light. So this is a hardware restriction, not the software. So then indeed the Stylus is the most reliable way to unlock the Touch HD, in those cases it will not unlock via the light sensor. Another option, is only to lock the touchpanel (LockTouchPanelOnly=1) and not the hardware keys. You can pick up the phone with the hardware buttons and you can couple a command to a hardware button to unlock: "TouchLockAction.exe" unlock

But of course, this has also the danger that in you pocket you press the hardware buttons. Maybe I should make a setting to unlock the hardware keys only at in incoming call.

The not yet implemented option "shake to unlock", using the GSensor could be the fallback, which would solve me some pain, because the GSensor can be read out without having focus (like the light sensor), whereas the capacitive touches it needs focus. So you have to wait till that is implemented, and till that time use the Stylus.

That there is a time displayed in landscape mode, I had that too on my Touch Diamond. But with the advanced config tool I could configure to show the battery indicator and not the time. Then the BattClock is nicely overlapping the battery icon.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can export/import the registry key tree HKCU\Software\ZuinigeRijder\LockSettings with a registry editor or another automatic tool.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There is a compatibility mode for older behaviour, which makes it more difficult to configure. This what is documented:

Vibrate = 0

Default it will not vibrate when switching to locked with the backlight off or screen off. If you do want vibration, overrule this registry key with "Vibrate = 1" There are 2 different vibration schemes: 1) LockIndicator = 1: only vibrate/beep when locked AND the backlight is not ON 2) LockIndicator = 0: vibrate/beep twice when locked, vibrate/beep once when unlocked The idea behind it is that vibration also consumes battery and if there is a visual lock indicator, you do not need the vibration (only when the screen/backlight is off).

VibratesLock = 0

If you want a different number of vibrations when locked, you can change this value. Possible values: 0, 1 and 2.

VibratesUnlock = 0

If you want a different number of vibrations when unlocked, you can change this value. Possible values: 0, 1 and 2.

So the first setting makes it react differently. You should configure Vibrate = 0 and then the number of vibrates for lock and unlock. That should give the result you want. The VibratesUnlock and VibratesLock take then precedence over Vibrate = 0.

Let me know if it works with the setting Vibrate = 0
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Hi ZuinigeRijder,

Rather than tell you what features to add to TLP, how about I try and explain what I want to achieve and then you tell me if TLP can do it or if it is a feature you’re considering implementing. I know most of what is said below TLP already can do however I have included it for completeness.

When I press the power button, I want the device to go into standby.

The device then does not come out of standby unless I press the power button or remove the stylus (i.e. deliberately turn on the device).

When there is a predefined period of inactivity the device goes into standby.

The device then does not come out of standby unless I press the power button or remove the stylus (i.e. deliberately turn on the device).

Both of the above are standard Windows Mobile features and do not require the use of TLP.

If the device is in standby and: -

There is an incoming call the device comes out of standby and is totally unlocked including hardware buttons or partly unlocked (touch screen is unlocked along with call and answer buttons).

If the device is in standby and: -

It comes out of standby for any other reason apart from an incoming call or pressing of the power button or removing the stylus, then the device is locked including hardware buttons with the exception of the centre action button (or another button) which is unlocked so that it can register presses.

If the device is in standby and: -

A Klaxon alarm event is triggered the device comes out of standby and is totally unlocked including hardware buttons or partly unlocked (touch screen is unlocked and the centre action button (or another button) which is unlocked so that it can register presses).

If the device is NOT in standby and is locked either partly or fully with the exception of the centre action button (or another button) which is unlocked so that it can register presses. The device can be unlocked by either removing the stylus, touching the capacitive screen in a predefined method, pressing the centre action button (or another button) a predefined number of times.

To achieve minimal ram usage I do not require the use of the light sensor or the clock or battery percentage monitor. What settings would you recommend on each page to achieve the above if at all possible.

P.S For others wondering why I want the screen unlocked when receiving a call it is simply because Dutty’s V4 ROM includes the Slide to Answer / Ignore canvass as such accidently answering or rejecting a call is much more difficult.

P.P.S apologies for the long winded post...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Probably it is a bug, introduced by my latest improvements, including locking the touchpanel at power off. Ok, let's look into the log file:

10:33:32 -1938049398 AutoLockOnPowerOn: 0

10:34:26 1271410654 SetCallStatus(CALL_INCOMING): 0

10:37:04 -1938049398 POWER_ON_REQUEST

10:37:04 -1938049398 IsConnectedCall(false)

10:37:04 -1938049398 ==========================DisableInput()==============================

10:37:04 -1938049398 SetDisabledPanelAndButtons(true)

10:37:04 -1938049398 SetDisabledPanelOnly(true)

10:37:04 -1938049398 HookTouchPanel(true)

10:37:04 -1938049398 IsConnectedCall(false)

10:37:04 -1938049398 SetLocked()

10:37:04 -1938049398 SetLockMode(true)

10:37:04 -1938049398 IsConnectedCall(false)

10:37:04 -1938049398 Lock(true)

10:37:04 -1938049398 ==================================Lock=============================(true)

10:37:04 -1938049398 SetLocked(true)

The logic in my code is:

if (pS->IsLocked() || pS->GetAutoLockOnPowerOn() || (pS->GetLockWhenIncoming() && (pS->GetCallStatus() == pS->CALL_INCOMING))) {

disableInput = true;

}

I do not see SetCallStatus(CALL_ENDED), so TLP thinks it needs to lock.

I will look tomorrow, how I can support the setting, as shown by you. Need to think about this one, how to solve this.
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Thanks ZR for taking a look at it.

Your hobby is like Sudoku is for my father. :)

Your brain won't become older if you make it work as is. ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
For completeness: is there is an external event, like incoming SMS, incoming call, alarm, other program, it will also come out of standby.

Hmmm, this would mean you can get missed calls by accidental presses, unless you have a slide to answer screen for incoming calls. But if you want to achive this, you need to configure CommandCallIncoming = "TouchLockAction.exe" unlock

Currently I cannot detect power button presses, I also cannot capture the centre action button (looked into it, but failed till now). So now you can only set AutoLockOnPowerOn = 1 and unlock via the other means (stylus out means also unlocked).

Currently I do not have a method to unlock when a specific program is active. However, maybe in Klaxon you can couple a command to unlock via TouchLockAction. GAlarm does support automatically unlocking TLP, so maybe this app is an alternative? But of course you can ask Klaxon alarm if that can also add specific unlock actions at startup.

I cannot unlock some buttons, so also not the center button. But the other methods will work.

Hmm, that would be something like:

ShowTime = 0

ShowBattery = 0

DateDDMM = 0

DateMMDD = 0

UnlockOnLightSensorTime = 0

ClockX=0

ClockY=0

ClockWidth=1

ClockHeight=1

LockIndicator=0
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
ZuinigeRijder,

A couple of more question if you don’t mind.

1. Are you able to differentiate between power on due to removing stylus, power on due to pressing the power button and power on due to external event?

2. Are you able to detect button presses if only the touch panel is locked? If yes then maybe an option to unlock the touch panel only via centre button if only touch panel is locked and device is not in standby.

Imran
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
I found an application shortcutcreator. A shortcut without a parameter works, but with the parameter lock (or -lock) nothing happens.
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
It seems you are right. If I set LockTouchPanelOnly=0 the trick doesn't work. :( I guess I should make a note of that in my previous post.. Well it may not be ideal but at least it is better than nothing. Btw, why would locking only touchpanel & not hardware buttons make that part of the screen not be blocked? I read the post you linked to & it sounds like it is by design in the call you are making but I guess I hadn't realized you screen locking differently when screen only vs screen+keys.

LOL now the gears are really turning! The thing is GScroll person needs to respond because obviously they do something differently because there is no visible window with GScroll to have focus so it is almost like that is not needed with the method used in GScroll.. I didn't see your response on if it would be difficult to make a test version of TLP that pops up a window when the phone powers on to see if that helps bring in focus. Would that be difficult or worth the time to try? I know you don't like messing with TEXT vs icons because of need for translations but that might also be good place to put a emergency unlock notice too. ;) "Warning: this phone is locked & no calls can be made" "Remove stylus & press EMERGENCY while putting stylus back in to dial 911" or such.. (Was trying to make it simple but avoid accidental call to 911. lol Maybe a slider would be a better option. Heck just popup window showing 911! with arrow showing to slide to keep it simple although you need to deal with emergency # being different in different countries too.. Anyway just a thought.

Bummer sorry to hear no success with GAPI. Maybe shake/roll gsensor method will be best bet for reliable method to unlock then.. Unless you can find method to sense holding key combinations.
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Hi. Did you have quotes around the command & not around the command-line?

Like: "TouchLockAction.exe" lock as shown on his site:

http://www.zuinigerijder.com/#4.2 (CommandCallIncoming example)

Unless maybe the shortcut needs a full path? Although you said it worked without a parameter.. What shortcut tool are you using? I'll give it a try & see if there is something special needed with it.

Bill
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
Hi Bill,

I used the tool shortcutcreator. Its freeware. I didn't use "".

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

Changing the vibrate registry setting to "0" fixed it. I changed the registry to make vibrate "0" and then set lock to "0" and unlock to "2"

Now it only vibrates twice when i unlock the phone and does nothing when it

locks.

Thanks a lot for your help and this program!!
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
OK I figured it out. It was part RTFM (read the manual) and part ZuinigeRijder telling you the wrong command line parameter. :eek:

Looking at his site under command line usage I realized there is no LOCK option. OOPS! lol

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

Here is the list from his site as of now:

#

Possible actions (multiple can be specified):

# Unlock

# LockScreen

# LockSuspend

# Suspend

# PowerOff

# SoftReset

# LockBacklightOff

# EnableSuspendOnBacklightOff

# DisableSuspendOnBacklightOff

# EnableUnlockOnLightSensorTime

# DisableUnlockOnLightSensorTime

# EnableLockTouchPanelOnly

# DisableLockTouchPanelOnly

# EnableAutoLockOnPowerOn

# DisableAutoLockOnPowerOn

# BacklightOff

# Exit

# Exec "command;parameter1 parameter2"

So if you did:

"TouchLockAction.exe" LockScreen

That will lock the screen but it is still on

"TouchLockAction.exe" LockSuspend

Locks it & suspends which is likely what you want

So in Shortcut creator you'd do something like:

Shortcut Path / Name

\Windows\Start Menu (or whever you want the shortcut saved)

LockSuspend (or whatever you want to call it)

Target Path / Parameters

\Windows\TockLockAction.exe

LockSuspend (this is the action command line below path box. Not case sensitive)

I left the icon stuff blank which seems to make it use the TLP fingerprint icon

Click Save. Now Click Start menu & go to Programs & there it is. Open it & it should locksuspend. :D

Now a quicker/easier way (especially if you copy/paste) is to open notepad on your computer & paste in this line:

30#"\Windows\TouchLockAction.exe" LockSuspend

(This should work too: "TouchLockAction.exe" LockSuspend )

Do File-save Browse to your desktop or such then enter LockSuspend.lnk (or whatever you want it called just make sure to add .lnk & make sure .txt is removed) Now you should have the file where you saved it. Copy it to your phone (activesync works well because you can put it right in \windows\Start Menu or whevever you wish) Once there look for it using your phone. Should work by running it.

Btw it says you can do multiple commands but I never tried it. I assume that means something like this works:

30#"\Windows\TouchLockAction.exe" LockScreen BacklightOff Suspend

Hope that helps.

Bill
[Touch Diamond, MDA Compact IV Themes and Apps] Kraize:
[Request - New idea]

In the stripe mode, have a color (should be customizable color) bar which is the battery display and when it's locked, have it turn white :). Like when the phone is not locked the stripe will act as a battery indicator and when it is locked, the stripe will turn white to indiciate that it's locked. Or another idea could be that the stripe changes color after each touch so you know how many times you've touched in order to unlock. Tell me if that made any sense lol.

EDIT: Another Request(s)

1. Add shake to unlock capabilities. (That would make it the ultimate locking app IMO)

2. Have someone enter a pin even after they unlock the device / have someone enter a pin if they want to access the config app (in case your device gets misplaced/stolen)

3. Exclusion list
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
i want also tlp to unlock my device on an incoming call because i am using slide 2 answer.

the commandline options don't work for me to unlock the device.

another issue i've noticed is sometimes when i press power button to turn off the device and then press power button again to turn it on again nothing happens. screen is off and so i have to pull out the stylus to wake up the device.
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
@Bill

Thanks a lot. It works.

Stefan
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
I would prefer TLP to not step into the field of other better programs (for example long bar battery meter). It already went far enough by including the small battery + clock (at least now we can hide it).

The color-change-on-taps idea is definitely interesting though; although for me it's enough that I have very thin red bar just UNDER my real battery bar when it's locked and it disappears when unlocked (and vibrates accordingly) - this is enough feedback. After all I just quick-tripple-touch the central button, no need for feedback for between the touches.

As for the other three, I like those.

Sorry to criticize your ideas (after all it's only my opinion), it's the first thing you mentioned that triggered my post. I just don't want TLP to step further away from what it's name says: Touch Lock Pro.
[Touch Diamond, MDA Compact IV Themes and Apps] takethetick:
Capacitive NavSensor (not working on Touch HD)

You did a great job with this tool. When do You think the Capacitiv Sensor is going to start working on the Touch HD?

Thanks for answering!
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
I don't think Touch HD *HAS* a capacitive navsensor
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
when the device is locked and i press the power button but don' unlock it, after a few secondes the device goes to suspend again. if i press then the power button within 30sec. the device won't wakeup until i wait a few seconds and press again the power button or if i pull the stylus out.

is this an option i can disable??
[Touch Diamond, MDA Compact IV Themes and Apps] takethetick:
Is it possible to unlock the HD by touching the screen
[Touch Diamond, MDA Compact IV Themes and Apps] bill48105:
Hi. If the screen is unlocked to be able to touch then what is locked? :D

Are you wanting to have screen unlocked with just physical keys locked?? Or maybe you are thinking a slider (iphone) or touch a pattern? Sorry I am confused.. :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, I only can detect removing stylus as a cause.

Not directly by TouchLockPro, but you can couple a command to a hardware key: See postcount #975
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The hardware key locking is an API of HTC, which ALSO locks the TouchPanel. However, I have another, more or less standard Windows Mobile locking method, when you do not want to lock the hardware keys. Actually, in version 2.1 I use both methods at the same time, when LockTouchPanelOnly=0.

Unfortunately no response yet from the GScroll forum, although fourcc is also helping in getting an answer :D

Instead of the window popup trial, I am going to spent first my time on using the GSensor to unlock, because that also works on a Touch HD and is independent of having focus or not.

Yes, I spent now my time on the GSensor.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for helping out, indeed I gave the wrong command for locking:eek:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
1. Is already on the wish list, with highest priority now.

2. I have searched for how to trigger that, no lock (even asked people for a try-out in this thread, but no lock)

3. Is already on the wish list, I think.

I had the idea to have the lenght of the stripe the battery percentage left.

The number of touches should unlock really fast, so visible feedback like color change is not needed I think.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
That is because TLP is Enabling input, when it goes to suspend, which can take some seconds. So there is no option to avoid this.
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
ZuinigeRijder,

Rather than having to shake the device to unlock it, which could possibly look rather silly depending on how hard or long you have to shake it and where you are shaking it

It might be better to implement a rotate / turn through 360 degrees to unlock it. Probably much faster and doesn’t look quite as bad. It’s been implemented before by surfsmurf in his locking application called SensorLock and its freeware so you might be able to use the sorcecode from it directly have a look on: -

http://xdaforums.com/showthread.php?t=422871&highlight=rotate+unlock