yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
If the locking of the "TouchPanel only" is not working for you for unknown reason, then the only way is to use HTCLockAPI = 1. And yes, then you must unlock first via one of the many available methods on the Diamond. Normally it will automatically unlock on the light sensor and manually via triple touching the middle button (you can even configure less touches).

If you do not want to unlock first, then I am afraid you need to look for another locking solution. www.zuinigerijder.com is mentioning a lot of other solutions.
[Touch Diamond, MDA Compact IV Themes and Apps] galerio:
Please, don't misunderstanding me, I'm trying several option, not only the "TouchPanelOnly", I'm also trying to lock all the phone and other things, but it appears to not work anymore. Some times and versions ago it was functioning, but now no. So I want to know if there is a way to really reset all settings.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can go to the About screen and press "Reset settings to defaults". If you want to have the behaviour of versions before version 2.6, you must set "HTCLockAPI = 1"

One often occurring problem of not locking is that the Stylus sensor is not giving back the correct value, due to dust or malfunctioning. Also make sure you put back the Stylus IN when soft resetting, because HTC has a bug that then the Stylus is not detected anymore, when putting it back in.

Hope you can find the problem. You can also post a debug log, when doing the above is still not working. Maybe I can see what is going wrong.
[Touch Diamond, MDA Compact IV Themes and Apps] galerio:
Now that I have turned on the debug mode, it appears to function better, but I have always the main problem: during a call it blocks my hard keys even if I have setted !UNLOCK on Incoming and Connected and LockWhenIncoming=0 and UnlockWhenConnected=1. Then it turns off my screen even if I have "ScreenOffWhenConnected=0" .

Here are my logs
[Touch Diamond, MDA Compact IV Themes and Apps] qcar123:
How can I using on my Xperia?

I try 2.6.3 & 2.6.4 can't lock/unlock by Light Sensor.

But it can lock when the other side pickup the call.

Is it my setting problem?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In the log file, I see that the screen goes off, while not yet connected. The design of TouchLockPro is to already lock at power off. However, that is not so practical when there is an incoming call. Probably the screen goes off, by the HTC builtin method of the lightsensor no longer sensing light.

I will upload version 2.6.5 today, so it will not lock when there is an incoming call in this situation and you have configured "UnlockWhenConnected".
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Fine you tried TouchLockPro on the Xperia. The light sensor is only used for unlocking.

On a general Windows Mobile with TouchScreen, the unlocking methods are restricted. This table gives the features which work on a general Windows Mobile phone. So you must configure a key sequence for unlocking, e.g. 91;8 (Home/Back key).

Because HTC developed the Xperia, some sensors may work. You can check which sensors work, by going to the different Settings screens. The light sensor unlocking may work, and maybe the Stylus sensor on the Xperia. I do not know, because I do not own an Xperia.

But on a general Windows Mobile phone, the lock/unlock is easy:

- lock by pressing the power button

- unlock by pressing the unlock key sequence

If you have a slide 2 answer solution builtin on your Xperia (I do not know if that is the case), than you can consider not locking the TouchPanel at incoming call (KeysOnly = 1).

You can enable debug logging (LogDebug = 1) and post the log file \TouchLockPro.log.txt in the root directory of your phone memory, so I can have a look which sensors work.
[Touch Diamond, MDA Compact IV Themes and Apps] qcar123:
Thanks so much!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I checked the log files.

It appears the Stylus is not working, because the following registry key is not available (and is read by TouchLockPro):

HKCU\\ControlPanel\\Keybd\\StylusOutStatus.

So unfortunately no Stylus sensor on Xperia.

I also see that the GSensor is not working, because it cannot load HTCAPI.dll.

I see that the Light Sensor loading (HTCSensorSDK.dll) is working. But I see repeatedly in the log file "LightSensorOpen() finished", so it looks like opening the light sensor is not working.

So it looks like ony the general Windows Mobile features are working for the Xperia. Because the unlocking methods are limited, I am busy with a Security lock foreground window, which you can use as an additional method for unlocking. But for now, unlocking via the key sequence seems to be the one you have to life with, for now.

I did not see a UnlockKeySequence configured in your log file. Does this mean you did not try or is it not working for you :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] qcar123:
How can I test the Light Sensor under TLP?

Sorry, I did not try UnlockKeySequence. I'm looking Light Sensor can auto lock / unlock the screen when during call.

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] muhlatte:
a little question: would it be possible to make a lock indicator for stripe mode? In my mind a colorchange (red yellow green) or a stripe that becomes thinner (4px, 3px, 2px) or something like that :D I use stripe mode because i already have a percentage battery icon (twosen taskbar) and this one does fit alot more in the taskbar icons :D

Certainly other ideas ware welcome ;)
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
I've got a strange feeling that 2.6.5 has a regression comparing to 2.6.3 with respect to the following simple use case:

- power off

- power on

-- the lock indicator is shown (in my case a stripe)

-- the touch panel is *not* locked (though expected to be), means it reacts on tap on any area

Attaching the logs.

I reinstalled 2.6.3 and now it looks ok.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for pointing out the problem and providing the log. I found the problem, it was a logic error in my code :mad:

I will upload a new version 2.6.6 now :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
According to this post the light sensor API is different. So unfortunately, this will not going to work, until someone finds out the light sensor API for Xperia. So you must use the key sequence unlocking, if you want to use TouchLockPro.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I had the idea, that the stripe mode length is giving the percentage battery left. In combination with a color change, that would give a good indication how much battery left. So a full stripe is 100% left. Almost empty is only a very small stripe in length.
[Touch Diamond, MDA Compact IV Themes and Apps] galerio:
Thanks, it works perfectly now and I can end a call without unlocking the phone!!
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
Thanx, it works now ;)
[Touch Diamond, MDA Compact IV Themes and Apps] muhlatte:
k this is already available (if you don't know it: http://xdaforums.com/showthread.php?t=478468 ), have install this together with touchlockpro :-D works perfect, i have the stripe indicator over the memory strip.

What i mean is that when you tap on the navsensor, the battery display goes 1, 2, 3, but stripe mode doesn't really have something like this, so i thought the color or thickness could be change, but length would also be nice :-D
[Touch Diamond, MDA Compact IV Themes and Apps] qcar123:
I found other forum someone said G-Light can't support Xperia also.

"Re: G-Light on Sony-Ericsson Xperia X1i

by fai » Fri Apr 10, 2009 8:44 pm

I had the same problam with my Xperia X1. In previous thread: HTC Touch Pro: HTCSensorSDK.dll is not found => no G-Light, I downloaded the Diamond2 G-Sensor + app regs.cab and then installed this. Now I don't have error when starting G-Light and it's not at 100% anymore."

Can I change Diamond2 G-Sensor + app regs.cab to test TLP?

But I don't know how to do that...

Thanks a lot!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, I do not know if you will screw up your Xperia, so be prepared to a hard reset.

What I do not understand is, that TouchLockPro is finding HTCSensorSDK.dll on the Xperia (loading), but cannot open the light sensor successfully. Did you copy those files yourself already on a Xperia?

Here is a link for the Omnia, maybe that works?

You must just copy the DLL's to the Windows folder.

But, try out at your own risk :eek:
[Touch Diamond, MDA Compact IV Themes and Apps] qcar123:
I can't found HTCAPI.dll in Xperia.

I try overwrite HTCSensorSDK.dll & install TLP one more time. But still have same problem...

Attached the log files.

Thanks again!
[Touch Diamond, MDA Compact IV Themes and Apps] ftibbling:
TouchLockPro on WM6.5?

Hi guys,

I couldn't find any post about TouchLockPro on WM6.5.

Does anyone know if the built in WM6.5 slider would work, or does this app require a key sequence?

Using:

[ROM WM6.5][WWE][Build 21815][18/6] BsB 6.5L Black
[Touch Diamond, MDA Compact IV Themes and Apps] ftibbling:
Found no way to use the built in WM6.5 slider to unlock. Maybe i missed something :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] fwt:
Here is one ;)

As far as i can see it's on the "Wish List"
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I know someone else use WM6.5 and TouchLockPro was working on it.

I understand that WM6.5 has a builtin Slider to unlock. If that is shown at incoming call, you can configure:

KeysOnly = 1, so you can answer via the slider. TouchLockPro will automatically unlock when connected.

If the builtin slider to unlock is also shown, when there is no incoming call, you indeed need to unlock TouchLockPro first via the different possibilities. If the unlock sensors do not work on your phone type (which phone do you have?), then a key sequence for unlock is the only possibility now.
[Touch Diamond, MDA Compact IV Themes and Apps] ederhj:
Lock on Bluetooth connection

You said, that it will be possible, that die phone will be locked immediately when the phone is connected wie a bluetooth headset/car kit an will be unlocked whren the connection ist closed.

Now my question:

What flag do I have to set or what do I have to do, so that the programm is doing so?

Thank U
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It is a little bit different, it will not unlock when there is a bluetooth connection if you enable/set DetectBluetooth = 1. With the default settings, it will lock already at power on, so in combination with the above mentioned setting, the phone is kept locked.

I do not have a bluetooth headset, so probably others can also react how they use it in combination with bluetooth.
[Touch Diamond, MDA Compact IV Themes and Apps] golightlygl:
This is how it works:

When a bluetooth headset connection is active, the screen stays locked, even with an incoming call and impervious to light. An incoming call wakes the screen but keeps it and the HW keys locked irrespective of light levels. A stylus remove will unlock the screen (I don't have other unock methods so don't know about those).

With the bluetooth headset disconnected but still with bluetooth enabled and on, the system will unlock with light as normal.
[Touch Diamond, MDA Compact IV Themes and Apps] ederhj:
OK.

But I don't want the phone to lock in any way.

Only when bluetooth is on, the the phone should be locked.

When bluetooth is off, the the phone should be unlocked.

The reason for this is:

I have my phone in my trousers, when I driv in my car. But whenI call someone, then the phone wakes up with unlocked screen. So I can accidently do anything. But I dont want do anything "in my trousers". When the phone is locked no mistakes can be made.

And when the phone sleeps again, then only with the powerbutton it's possible to wake up the phone again.

That's all I want.

Can you help me?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, so you never have the phone in your pocket, while bluetooth is not active? Ok, then the above makes sense.

Ok, then you need to set the following settings:

AutoLockOnPowerOn = 0

DetectBluetooth = 1

LockWhenIncoming = 1

CommandCallIncoming = !UNLOCK

The trick, is that at incoming call the phone is locked and unlocked immediately by the above settings. But when bluetooth connection is active, the !UNLOCK will not be executed.

I cannot try it myself, but in theory it should work.

Let me know if it works ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ederhj:
I'll try.

But, as I said:

Only when bluetooth is connection is on, the the phone should be locked.

When bluetooth connetcio is off, the the phone should be unlocked.

That's a bit different.
[Touch Diamond, MDA Compact IV Themes and Apps] golightlygl:
Your requirement is quite unusual since don't want the phone to lock at all except when bluetooth is on.

It is testimony to the flexibility of ZuinigeRijder's code that his suggestion should do what you want to achieve. What he has suggested will effectively use the program to lock the phone when a call comes in. However, it will immediately unlock by using the !UNLOCK command. However, if there is a bluetooth connection then the !UNLOCK command won't be issued so the 'phone will stay locked.

However, consider this. The program is designed to help when the phone is in your pocket at any time. If you are walking along with bluetooth off and the phone rings in your pocket, then you could still accidentally answer or reject it. If you use the program as intended, then it will lock when the call comes in so that you can't accidentally answer it.

If you set the light sensor to 0 lumens and 0 time, then as soon as you remove the phone from your pocket, the phone will unlock allowing you to use it normally. If you take it out of your trousers in a very dark room then you will have to use another method to unlokc (such as removing the stylus) but from my expereince since using the application, I rarely have to resort to this.
[Touch Diamond, MDA Compact IV Themes and Apps] ederhj:
OK.

Now I understand.

Well, I will try this, too.

Thank U.

I will post the answer.

Bye
[Touch Diamond, MDA Compact IV Themes and Apps] paclep:
some bugs

I haven't seen it reading the document on http://www.zuinigerijder.com, so I post here.

I have a lot of problem using this app, looking very good overwise.

- When I lock the screen, sliping up on the right nav sensor, sometime it switch off the screen, espécialy when i'm using some others apps (GPS...)

- sometime when I wake the phone with power button, the batclock is showing that it's locked, I can use the screen sensor. Sometime it's effectively locked.

I can register and send a log if you think it's usefull.

Thank you !

Pac
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There can be two things I can think of.

If you do a lockscreen withing 30 seconds after power on, then TouchLockPro will automatically suspend after the 30 seconds is reached (SuspendTimeoutPowerOn)

Or you execute accidently !LOCKSUSPEND (swipe right or left). You can configure a different command, if that is the case.

One known issue is, that after reboot/soft reset, you need to enter the SIM code, before the first time locking TouchLockPro. Maybe there are other situations, that I am not aware of. You can post a debug log file, and note the exact time when it occurs, so I know where to look.
[Touch Diamond, MDA Compact IV Themes and Apps] hgrimberg:
Key lock

I upgraded to version 2.6.6, installed in the device memory of my Diamond and uninstalled S2U2 as the installation instructions were saying.

Now when I choose the setting from WM "Lock all buttons except the Power button, and after turning off the screen, Touchlockpro blocks the screen, locks the 2 hardware buttons on the right (the back key and the end key) but it leaves unlocked the 2 buttons on the left (the home key and the call key). (I set the center key to be always unlocked by typing 134). Before, when I had S2U2 installed, Touchlockpro 2.6.6 was locking all buttons but it was never locking the screen as it does now.

What is happening?

Now I am writing again after doing a soft reset. Now things are different. Now all hardware keys are locked but the screen is not locked anymore. I've seen that there was a known issue that after reboot/soft reset it is needed to enter the SIM code... I never clicked on "Require PIN when phone is used", so everytime I soft reset, I don't have to enter my PIN again. (I suppose that the SIM code is the PIN). Then why is not locking the screen anymore after a soft reset?

Ok, now I tried a different thing: I clicked on HTCLockAPI = 1 and now it locks the screen but it locks all hardware keys, even the center key that I supposedly left unlocked by typing 134 on the Touchlockpro settings. I went to WM settings/Key lock and clicked on "Lock all keys except the Power button" and now it locks all hardware keys and leaves the center key (134) unlocked. So, now everything seems to be fine, and the screen is also locked, but it is impossible to unlock using the center key (134). So it is posible to wake up the screen with the center key but then it is impossible to unlock the phone by clicking again the center key.

Any ideas?

Thank you very much.
[Touch Diamond, MDA Compact IV Themes and Apps] ederhj:
Locking with bluetooth-settings and light-sensor is working.

But now I have a problem:

The software shows, that the device is locked, but only the hardware-keys are locked.

I've nothing changed in this way.

What ist the/my fault?
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
Do you have 2.6.5 installed? I have had the same (or at least similar) issue and it was solved in 2.6.6
[Touch Diamond, MDA Compact IV Themes and Apps] ederhj:
no.

I'Ve alread 2.6.6 installed
[Touch Diamond, MDA Compact IV Themes and Apps] aamonster:
Nice piece of software :-)

A question: is it possible to tune program to such behavior:

1. Device in suspend mode (suspended by power button or by timeout)

2a. I press power button - device must be unlocked.

2b. Device turns on by itself in my pocket (incoming call or pressed 'play' button on a2dp handsfree) - device must be locked.

?

All I could to set up - AutoLockOnPowerOn=1 + UnlockOnLightSensor=1 - it's ok for 2b, but for 2a device locks for 1.5 seconds (it's uncomfortable), then unlocks...

Maybe it's possible to check lock conditions immediately after power on?

P.S. Sorry for my bad English... and thanks to software author.
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
For long time I hoped to just get away with Touchlockpro, but I must admit I love the way gscroll handles the capacitive panel as well as the built in task switcher. SO I was wondering if it is possible to make those cohexist.

What I am interested in would be to have Touchlockpro holding exclusive access to the capacitive panel when the device is locked so that I couls still sweep to unlock but gscroll would not react to touches and sweeps so that I would not launch applications by mistake when I take the phone out of my pocket. Counterwise Touchlockpro should release the capacitive panel to gscroll when unlokced.

Right now when I run both seemes that gscroll has always access to the capacitive panel.

Is this a posisble scenario (now of in the future)? Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] waverbob:
I have the same problem after installing the last version 2.6.6

I don't know how to save a log

Thank You

Roberto
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
Oh its simple. Go to "Other", tick the "Debug Log" checkbox, reproduce the problem.

Switch off "Debug Log" (otherwise the log files will still be locked and you may face problems copying them).

Under the very root of your device you will find two log files, zip them together and attach.
[Touch Diamond, MDA Compact IV Themes and Apps] paclep:
- It's not within the 30 second after poqer on

- It occurs mainly when I'm using Tomtom, so I don't think it can be this solution

It's not after booting, I'll make this log file and send it.

Thank you !
[Touch Diamond, MDA Compact IV Themes and Apps] golightlygl:
Set AutoLockOnPowerOn=0 (so power on button works normally)

Set LockWhenIncoming=1 (so stays locked when phone call comes on)

Set UnlockOnLightSensor=1

UnlockOnLightSensorTime = 500 (half a second instead of 1.5 seconds)

UnlockOnLightMinimumValue = 12 (or other low value so low light is OK)
​

Set DetectBluetooth = 1 (keeps phone locked when bluetooth is connected to a headset)

Set DetectBluetoothLightUnlock = 1 (if you want the phone to unlock when out of your pocket and bluetooth is on)

That should do it for you:)
[Touch Diamond, MDA Compact IV Themes and Apps] paclep:
log

Here is the log for a first problem :

when I lock the screen, a few second after, it shuts down.

This issue don't happen every time, but when i did the test it happen every time.

The 3rd text file contain my live comments. Times can be a little wrong, cause I can not test my phone and enter text in the file at the same time.

Another problem I have seen, but not registered in this log, is that I can click the "task manager" even when the screen is locked.

Thank you again.
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
Hi, I am appealing to the good soul of somebody reading this post, to help me get this application to work for me. All I want is for it to lock the screen and the buttons when somebody calls.

I used to know how to program this application, I am using it since the version 1.8, or even earlier. Now, I can only use it to show the battery percentage on the upper bar, and the nav-pad launcher.

I would really love to be able to have the screen and buttons locked when a call is coming. For unlocking, I used to use the 44 sequence, touching the capacitive areas.

Please help me :)
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
I asked the question before, try to look up in the thread. Essentially it is a standard behavíor of the Windows screen lock; if you wanna avoid this, use HTC lock.
[Touch Diamond, MDA Compact IV Themes and Apps] xda-kungfu:
Touch 3G

Has anyone got this to work on a Touch 3G?

It locks OK but I can only get it to unlock by connecting external power.
[Touch Diamond, MDA Compact IV Themes and Apps] The Missing Link:
Unlock on reminder - logfile

I attached a logfile; had it run for less than a day. Not sure how many reminders I had that actually unlocked the system. It's a huge logfile; I'm sorry. If this is impossible for you to process I can understand; tell me what you would like to see and I'll get it. What I see is a lot of activity during the night... nothing happened, first activity should be around 8 AM again. I almost never use the PDA to phone or SMS (and I didn't during the log-period)

Does this help in any way?

You said "you can enable HTCLockAPI = 1. But then you cannot use some new features like unlocking via a hardware key or only lock the hardware keys.". All I want is to press the on/off button (upper right top of my HD) and with that either lock or unlock the unit. I'm not using any other (un)lock mechanism.

What happens when I do receive a phone call? I don't want the device to unlock while it's in my pocket.