yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you explain this a little more. Because when TLP unlocks, it unlocks immediately. So I expect this 3-5 seconds lag are unrelated to TLP. How do you unlock? Which ROM are you using? Probably others can also respond if they have the same experience. Because I cannot confirm this behaviour.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I thought it was clearly mentioned in the changelog of 2.3.4. Currently I do not have a any idea how to solve this elegantly. I a next version I make it possible to disable this workaround, but then it is possible that sometimes you cannot unlock via capacitive means (dependent on the ROM you use and if you are on the manila Today screen).
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I just did some testing with and without TLP

Without TLP:

Called my Phone, when it starts ringing, I can answer the call immediately with hardware button or the green answer button.

With TLP:

Called my Phone, then I have to wait until TLP unlocks (it unlocks with TAPI option + Incoming "TouchLockAction.exe" unlock) unlock on incoming calls. But, before it reacts and unlocks, it takes almost 5 secs.

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

I did more testing :) I think I found the problem. Or, my problem :)

TLP locks after the power on. So, it takes 1 secs to lock, then TLP has to detect the incoming call to unlock, I then loose another 2-3-4 secs, depending.

But, now, if I power on the phone, then TLP launch and lock the phone, then I let turn itself off while it's locked. Now I understand that TLP is already lock with power off. Now when I get the call, it does not have to lock, and it detects the incoming call, unlock, and I can answer the call almost immediately.

So, is it possible to lock when it goes on standby? So when it turns on, it's already lock?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, with unlocking via CommandCallIncoming = "TouchLockAction.exe" unlock it takes some time before TouchLockAction is started and has executed indirectly the unlock. So that explains the delay :mad:

Fortunately, the newer versions of TouchLockPro have now builtin commands. So now you can also configure: CommandCallIncoming = !UNLOCK

Now you should not experience delay anymore :)

Note: builtin commands are described here.

* UNLOCK

* !LOCKSCREEN

* !LOCKSUSPEND

* !SUSPEND

* !BACKLIGHTOFF

* !BACKLIGHTON

I will update the TAPI settings screen, so it is also clear that those commands can be used there.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
WOW!!!!!!! It's now super fast !!!

It's hard to keep up with all your new improvements :D
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
Just a note... FIRST APPLICATION MODIFIED TO WORK AS A SERVICE SUCCESS STORY!!!

(it is even just a click in the program options if you want to switch it back to being a process)
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Is !UNLOCK available in 2.2.5 or 2.2.7?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, it is available in 2.3 onwards.
[Touch Diamond, MDA Compact IV Themes and Apps] cairel:
ZuinigeRijder thank you very much for yor program. I have been using for some days and I am really happy with it. I would like to do some comments on what I have observed and sugestions:

- If you try to unlock with CMDOrientation and you fail to do the right movements the HD comes locked again BUT the powerbuttom does not work anylonger. I do not know what happens if this is the only unlock method configured. In my case I have to use stylus. (Edited: selecting EnableInputAtSuspend solved it)

- If you select AutoLockOnPowerOn it is unlocked by the light sensor (is there is light, of course). I understand that right behaviour would be that in that case it should not be unlocked by the light sensor at that moment, since you are doing something to lock the HD. Probably it should wait untill light goes off to activate that response so next time light goes on it unlocks the HD.

- Something similar happens in relation with the ScreenOffWhenConnected. Id there is light screen does not come off.

- In the CmdOrientation page would be nice to have a 'try' button to be sure.

- A kind of 'help' button for the list of orientation's codes and available commands.

- At selecting orientations or commands maybe woulb be easirr just to tick in a scrollable list

I hope these comments helps. Thank you again :)
[Touch Diamond, MDA Compact IV Themes and Apps] Sian:
Any chance of throwing in a feature to customise the gesture (g-sensor) to lock/unlock screen? I'm using it to lock screen when watching video (esp by my little girls, who tend to press the button or screen accidentally). Find the default gesture a bit hard to carry out.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The gestures can be configurd:

Settings.html#4.4

The default configured ones are chosen that they are not too easy to do, but of course you can make the gestures shorter.

e.g. face_down (5) for lock and face_up (6) for unlock.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the comments.

Unfortunately I cannot unlock only the power button with the HTC API I use.

There is also an orientation to unlock. But in general I would expect that on a Touch HD you use lightsensor, stylus and GSENSOR for unlock. Of course you can make the orientation changes to lock/unlock easier than the default configured.

Currently, when you lock the device via the command !LOCKSCREEN, then it will not unlock via the light sensor. So that is what is the expected behaviour, I think. So probably I do not understand your problem?

The screen off when connected, is working independent of the light sensor (it justs suspends). So I am a bit confused? What is not working?

I know the current settings are not so convenient for configuring. Especially, because I would not expect it is changed so often, I see it more or less a little bit more convenient way of configuring than using the registry.

But it is true, the Settings screen could be more handy. Now it is more technical. Improvements are on a wish list, but they are not the highest importance at the moment. So for now, the Help is at http://www.zuinigerijder.com/
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
I am getting a weird issue and COULD be related to TLP (it happens to at least one more guy). ZR tell us if it is possible this comes from TLP:

When I switch on my Touch Pro, the screen switches to my second tab (favourite people) and then back to home, really fast (maybe in 1-2").
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
Expected... This is the workaround ZR added for the TF3D issues some people were having. I think he said he's going to make that configurable in a future version.
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
OH PLEASE make it configurable.

So it is mentioned in this thread? Where to look?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
#1583

#1596

#1599

#1617

When I make it configurable and you disable it, you may have chance that capacitive touches and swipes are sometimes not working......
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
Ok... we can try when you do. :)

First see if you can make it a service... Daniel Herrero gave some guidance in the appropriate thread ...and secondly see if you can add the SIP switching.

(yes I am talking about the two things *I* care for the next version :P :P :P)
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Just for your info :)

:( This morning with 2.3.5 I missed a call, I was not able to answer using hardware or soft button. It shows unlock, but I couldn't answer :( It looks like the old bug!
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi,

Could be nice to be able to avoid phone to unlock when connected on blutooth headphone.

Every time I receive a call while driving the phone unlock in my pocket, quite annoying at the end.

Regards
[Touch Diamond, MDA Compact IV Themes and Apps] cairel:
I can not get the screen blocked when I connect a call. I have activated: UnlockOnLightSensor, AutolockPowerOn and ScreenOffWhenConnected. Even I add !LOCKSCREEN in Connected (and 'User TAPI'=1). However, everytime I connect a call (either incoming or not) the screen keeps on.

You are right that is not related with UnlockOnLightSensor since I try with it activated and not obtaining the same result.

Just in case it helps you I observed that once connected I get the volume level bars on the screen, then they are increased always -without doing anything- one step and in a few moments they dissappear and show the phone UI again (with unlocked screen)
[Touch Diamond, MDA Compact IV Themes and Apps] kingi:
I like 2.3.4 or 2.3.5 the new function.

Unfortunately, the phone hanged either installed 2.3.4 or 2.3.5

now I still using 2.2.3, it's normal.

Hopfully can solved the hanged problem.

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] George obama:
I love that!!!!!!!!!!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, not so nice. I think I saw earlier debug logging and there it did not show anything strange, it looked like it was unlocked like expected. Maybe another program or HTC app is freezing the phone? It can be TLP, but it can also be another app.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Which settings did you set/try?

I think when you set UnlockWhenConnected = 0 it will not unlock automatically. But I have no bluetooth, so you have to try yourself.

See also Settings.html#4.2
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The service will be on the wish list, the SIP switching in the next release.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You should also set: UnlockWhenConnected = 0 when you do not want it unlocked when connected.

I expect another program is doing something with the volume level, or the volume buttons are pressed?

I try to suspend, with setting ScreenOffWhenConnected = 1, but if another App is keeping the phone awake (or volume press), this will not help.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is the first time I hear this problem.

What phone type do you have?

I added the TF3D left-right to version 2.3.4 and 2.3.5, so maybe that is related.

Is the same problem there, when you use the standard Windows Mobile Todat Screen?

Can you post a debug log file for the hanging situation (logdebug=1 and logdebugdetailed=1) and post the file \TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
New Touch Diamond ROM and Touch Diamond2

There is a new (Dutch) HTC Diamond ROM,

moving from:

2.03.404.2

into:

2.03.404.3

Apparently there are some fixes done, because it was not so stable. Has anyone experience with that? Maybe this solves also the problem with the capacitive touches, so I do not need to workaround that problem?

I also read in the SensorLock Thread, that the GSensor of SensorLock was not working on the new Touch Diamond2. Anyone with the Diamond2 having experience with TouchLockPro?
[Touch Diamond, MDA Compact IV Themes and Apps] kingi:
Thanks for reply.

I am using Touch Diamond.

Yes, I tried serveral time . the results were the same --- hanged.

Sometime, I slide from Homepage to Programs, and hanged @ program

Sometime, I slide the new function to unlock and unlock in the right side ( arrow and hang down button), then hanged again.

After hanged, I re-installed back the 2.2.3 and back to normal.

Fine, I installed 2.3.5 now

Now I found the TouchLockPro is normal, but the touch panel no function;

Power button no function;But I still can use slide up and down to turn backlight on/off and lock/unlock function.

I only way to reset the phone again since the screen stopped at "program" page but all program icons did not show on.:(

Please find the attached zip file.

I hope you can solve that problem. I thought 2.3.5 is more efficiency and I like it.
[Touch Diamond, MDA Compact IV Themes and Apps] cyberjaya:
Could be related to the "ordering" of TF3D tab. From what I could recall on previous post the version 2.3.4 and 2.3.5 would switch to 2nd tab which is defined as "Contacts". Certain cook ROM like the Morna 1.8 I'm using default the 2nd tab to something else. I've tried that v2.3.5, by using TF3D config to swap the "Contacts" tab to 2nd tab. Somehow that seems to resolve the hung issue. But the capacitive sensor seems not working well. Have no time to do further test. Now temporary reverse back to v2.2.4.
[Touch Diamond, MDA Compact IV Themes and Apps] kingi:
Yes, you are right. I re-ordering the TF3D tab.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for figuring out this problem.

I a next version I will make it configurable the right-left simulated press of the TF3D today screen. I still have not a good solution for the problem, that when on the home screen, sometimes capacitive touches/swipes are not working. Damned HTC screwed up something :mad: Maybe the newest ROM 2.03.x.3 do not have this problem. Earlier ROM's also had not this problem too.
[Touch Diamond, MDA Compact IV Themes and Apps] cyberjaya:
Don't mention it. We all should thank you instead for creating this nice apps :).

Not sure what I did earlier... Had reinstall back v2.3.5 (with Morna 1.8 ROM "Enhanced" version) and found that capacitive sensor are working fine so far. I recall few things I've done earlier,

- uninstall Lumoz (not sure if this is the correct spelling, software that help to auto adjust backlighting to save battery)

- tweak some performance registry via Advance Config 3.3

- ....... can't recall what else i've done...
[Touch Diamond, MDA Compact IV Themes and Apps] phliberato:
Mapping hardware Keys

Hi,

Could you show me the code to mapping hardware keys?

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] cairel:
ZR I use UnlockWhenConnected = 0 as well.

I do not know there is any software that manage the volumen when I connect an incoming call.

Anyway when an outgoing call is connected the screen does not go off either (in this case there are not volumen bars)
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
Hi, ecard, I experience the same thing as you did, but I didn't find any "CommandCallIncoming" on any of the pages of the menu, in order for me to put there the "!UNLOCK" setting.

I did find that command on the registry, though.

could you please tell us details of what you did to get rid of that delay?

thanks

EDIT: sorry, I searched some more and I found it (hidden) :) on the second page. However, if I write "!UNLOCK" on the "Incoming" box, the screen will not be locked at all when a call is coming! That would defeat the purpose of this wonderful application.

Unless, I am probably doing something wrong.

Please help. :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There are people who use the slide to answer screen for unlocking, so they want TouchLockPro not to lock when there is an incoming call. There is a large BUT, then the hardware buttons are unlocked, so you can still accidently reject/answer calls. I use both mechanisms, lock with TouchLockPro in combination with slide to answer.

In general the light sensor will unlock the phone automatically, when there is enough light. And otherwise there are the other means of unlocking (GSensor, NavSensor, Stylus, Keyboard). When unlocked by TouchLockPro you can just answer with the hardware buttons or use "slide to answer".

But it is a personal choice how you like it, and how safe you want to be.

Hope this helps to make a choice ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro asks Windows Mobile to suspend, but apperently an Application is preventing the phone to suspend.

Which applications do you have installed/are running when calls are done?

You can also enable a debug log file (logdebug=1 and logdebugdetailed=1), reproduce the problem and post the log file \TouchLockPro.log.txt as zipped attachment. At least I can see then that TouchLockPro is trying to suspend in the log file. Please also indicate when (exact time) the screen did not go off.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear it is now working. Sometimes the phone is a mystery and normally it is not the fault of TouchLockPro. Hope it keeps working :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I assume you mean coupling (TouchLockAction) commands to hardware keys.

post #1020

using shortcut creator: post #1043

Hope this helps :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] phliberato:
C++ code

I mean c++ code.. Is it possible?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think it will be possible, but I have no C++ code for that.

That is where other tools for mapping hardware buttons are for.

So you should ask in other forums....
[Touch Diamond, MDA Compact IV Themes and Apps] phliberato:
C++ Code

How do you do this? Wich are this tools?
[Touch Diamond, MDA Compact IV Themes and Apps] Sian:
I recently installed the Diamond2 Sensor thingy on my Touch HD.. seems like this has impact on TouchLock Pro. I can't seem to perform the lock screen using gesture. Can check?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
So this looks like the GSensor API has been changed, as already indicated in this post.
[Touch Diamond, MDA Compact IV Themes and Apps] d.joris:
clock.exe <> G-Alarm

I use Diamond also as bell. Had G-alarm installed with TouchLockPro. Unfortunately thereby battery consumption is immense. over 20% at one night. I´m now again back to S2U2 and the standard bell Windows clock.exe. Hereby only 5% battery consumption at one night.

I'm sorry - TLP is actually better and there ist no battery consumption.
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
I have some problem with capacitive touches in the last version (2.3.5).

I upload my log files.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked into the log files, and there appears to be capacitive touches/swipes in the logfiles. There is a problem, that sometimes, when on the TF3D home tab, capacitive touches are not sensed with the newer ROM's. Therefore I have the workaround to move to another tab and back at power on/screen on.

Can you be more explicit what is not working? Because there are capacitive swipes in the log :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
Hi, d.joris, what do you mean by "Had G-alarm installed with TouchLockPro" ?
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
If I do not move the tab, the next one that I power on does not work capacitive touches and I unlock the daimond with stylus.

In my rom, doesn´t work the move to another tab.

Sorry for my english.
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
Question for ZuinigeRijder: considering the above, is there any way to eliminate that delay and still use your application as a locking tool when an Incoming Call is arriving?
[Touch Diamond, MDA Compact IV Themes and Apps] Magus:
Hello ZuinigeRijder, great and useful app!!!!

I have a problem with the capacitive touches.:(

Since i flash the rom of my htc diamond (now have 2.03), capacitive touches the stopped functioning, now only unlock using the stylusout.

I think	can be incompatibility with rom version. because it worked before with my old rom.

there is any solution?

Thanks a lot!!
[Touch Diamond, MDA Compact IV Themes and Apps] d.joris:
Sorry for my bad english...

I have TLP installed and G-Alarm. And so, the battery train is over 20% at one night (6 hours). After deinstalling G-Alarm, the battery train is 5%.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, others reported too that moving to right tab and moving back to left tab was not working on their ROM.

Reordening the tabs may help. See the following posts:

http://xdaforums.com/showpost.php?p=3414288&postcount=1651

http://xdaforums.com/showpost.php?p=3414355&postcount=1652

http://xdaforums.com/showpost.php?p=3414562&postcount=1653
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In the newer versions, you can couple the command !UNLOCK to Incoming call. So this will unlock TLP immediately, but then also the hardware keys are unlocked.

Better is, to just unlock TLP by the available methods first, so also the hardware keys are kept locked, because otherwise you can still have missed calls, while pressing keys in your pocket or while taking out of your pocket. Slide2Answer solutions do not prevent this.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear that TouchLockPro is not using extra battery, as designed :) A pity that G-Alarm does use extra battery though.
[Touch Diamond, MDA Compact IV Themes and Apps] VETTEPC123:
touchlockpro clock moves

every once in a while when i turn the screen back on the clock which i have placed over the start windows symbol will move back and forth between where i have it placed and the middle of the top bar. it continues to move till i unlock it and then stays wherever it was when it got unlocked. if it is in the middle it wont move back to the far left where i want it unless i slide out my keyboard then slide it back again. any ideas. ps i have a att fuze with stock rom. thanx for any help.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Do you have positive numbers for the ClockX? Because otherwise it will compute the clock position from the right, which is another position when in landscape.......Because you want it over the Start Windows logo, the ClockX value needs to be positive. This position will be the same for portrait and landscape, so it must be computed from the left.

If the number is positive, can you enable debug logging (logdebug=1 and logdebugdetailed=2) and try to reproduce the scenario? Note the exact time when it occurred and post the debug logfile \TouchLockPro.log.txt. Maybe I can find a clue.....
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
thank you very much for your quick answer, I'll try that
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
thank you for the clarification. I have also, both of them installed, but I didn't notice any excessive drainage. I'll pay more attention.

However, I am using TLP for quite a while now and I noticed that it doesn't affect the battery.
[Touch Diamond, MDA Compact IV Themes and Apps] Mandragore:
Hi ZR, I've watched your progress from the beginning. But only today I've finally tried TLP :o

I'm testing if it can replace or improve on PocketShield. And I could definately use the extra sensor features. So far I'm impressed, as most features work right out of the box! The orientation took some reading and practice before I could benefit and I'm still finetuning. But it looks promising. Tips on other best practice settings and gestures are most welcome, though!

You are already aware of the slightly unreliable initial capacative touch with Manila on 2.03 ROM. Apart from that, nice! Could be the ROM, but maybe it's the Manila that came with 2.03. Older or newer Manila's on 2.03 could prove more reliable. I have 1.2.35590.0.1813.6. Can other versions users share their experience? Could be useful when the TLP workaround is optional in the next version,

Now, what I still don't understand after some searching, reading and testing is why I can't get my device to wake up with hardware buttons, if it isn't suspended with with "TouchLockAction.exe" locksuspend? What did I mess up?

Never had this before installing TLP, but I'm not 100% sure it's TLP related. Anyway, non TLP suspends by QuickMenu, ChangeScreen or power settings for example, force me to soft reset. Because the screen stays black. Doesn't matter what hardware buttons I press. Or how hard ;)

Shall I post a log and give some more info on other software and power settings?
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
@ZuinigeRijder: is it possible to unlock tlp by the light sensor but only on an incoming call??