yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
Wow! So many news :)

Hi!

So many news (and versions!) since I last visited the thread! I'm so happy about the G-sensor stuff! :) Congratulations for including it!

I would like to bring 3 "issues" to your attention:

1. The G-sensor unlocking works fine *except* when the phone receives a call and it's ringing *and* vibrating - then it has a really hard time trying to detect orientation changes. Unfortunately this is probably just the moment when you're most concerned about unlocking your phone asap (I had the phone locked and ringing in some important meetings - you should have seen me trying to unlock it so that I could mute it! :) )

2. The G-sensor unlocking (in its default setting of 8888) can be easily fooled - for example turn the phone ON in a dark room while keeping it perfectly still, face up & "portrait" and start walking fast (one step at a time it's even better) - TLP wil start counting -1, -2, -3 and unlock even though the phone "orientation" never changed! Really nasty if you walk a lot :( (LE: I settled on 5353 for G-sensor unlocking - it's a much more natural move for my hand than 8888 and it also doesn't get fooled by walking)

3. The little "X" on top of HTC Task Manager icon flashes every ClockLockActiveTime msecs before TLP unlocks (I guess it just gets recreated with the window). Not really annoying but I wanted to let you know nevertheless in case you have large values for ClockLockActiveTime and you didn't notice it yet :)

I am using v2.2.3. BTW, I saw you just posted on this thread the new v2.2.4 - can you please let us know what it is supposed to fix from v2.2.3 (in addition to the bug with the autolockonpoweron=0)? Thanks a lot!

Cheers!

Dan
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
Hi 4cc!

Since you're already using both programs on your phone can you please let us know how TLP and Gscroll work together? I would like to buy and use Gscroll (I'm interested in getting the new additional emulated "buttons", but also in using the tilt scrolling). However I wouldn't like to install Gscroll and lose TLP functionality :D

Thanks a lot!

Dan
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
thanks ZR as always, i will give it a try. (crossed fingers)
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
HiDan74,

they work well together. Sometimes the capacitive area for TLP is not responding perfectly becasue Gscroll hijacks it, i guess...

BTW what you should do is to disable the "tilt" feature that must be activated with a tap in the center button in Gscroll and associate this center button tapping to TLP using "CapacitiveTouchesSequence=2" that means one tap in center button. That's all
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can mute by turning the face down (not something of TLP but from HTC). Thereafter you can unlock. Normally the light sensor will do in most of the times the unlocking in not too dark lighting conditions. In real hurry, taking out the stylus is the fastest way to unlock.

Yeah, I also see sometimes 'strange' notifications of the GSENSOR. I will see if I can find out why that is (and if I can influence that).

I need to recreate the BattClock to get them on top of full screen windows, otherwise you will not notice the BattClock. For example in Opera, when it is full screen. So that gives the effect. But it is gone when unlocked.

Apart from:

* solved a bug with autlockonpoweron=0 in combination with outgoing call and screen off/on

I do no longer make a popup child window of the foreground window but just subclass it (own wndproc in front of it). This should solve the following problems:

* reported problem of the password screen disappearing after some time not used (black screen)

* waking up the device by pressing the power button the TF3D clock does not update until the device is unlocked

* PhoneAlarm running on SecondToday today screen, TLP is freezing repeating alarms.

So this should make TLP not interfere with other programs. But of course, I do not know for sure it is solved, so I asked to test. Therefore I first did put version 2.2.4 here, before promoting it to the downloads section :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
The problem is caused by the value of StylusOutInToggleTime. When I set it to 999999 (so that the diamond locks when I put the stylus back in) and leave the setting menu and the reenter after leaving the setup completly the value is 16959 (?).

When I enter 99999 I get the "Error in Init Form" when switching form setting 3 to 4 and the StylusOutInToggleTime is set to 1000.

I think it is the same problem as described in Post 1240/42/44.
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Exactlly, it's the same issue that I've.

What about my suggestion to simply have a checkbox to enable/disable the time constraints ?

Another "bug" I've discovered yesterday, when I put stylus in the phone lock and the screen turn black, it's perfect, but if I press the power button to turn on the screen I can't turn it back off with the power button again, I've to remove and reinsert the stylus to turn off the screen again.

Tested also with v2.2.4, same issue.

Thanks for the support

BR
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
Hello!

I never thought this is available out-of-the-box from HTC (I thought I have to install additional G-sensor software to get it). Now that I found this out I think this is the reason TLP has a very hard time detecting orientation changes when the phone is ringing - they probably both compete for the G-sensor :(

True, and I rely on the light sensor most of the time for this. Can't wait for the sunny summer to see how it works (will there be too much light available while the phone is in its "holster"?)

Maybe when the phone is swiftly accelerated on any axis it temporarily gets confused about up, down, left, right, front, rear? Just my 2 cents :)

You mean you stop recreating the window when the phone is unlocked? That's super! (I thought TLP constantly recreates the clock icon just to stay on top of other windows)

Actually the TF3D clock updates in the short time you recreate the window :)

(I clearly saw that last evening)

I have a small suggestion - will it be possible to use colors instead of -1, -2, -3 etc. to confirm orientation changes? On Raphael's screen is pretty difficult to see the very small -1, -2. -3 etc.

I am thinking about something like:

1. when you turn on the phone the clock icon is white

2. at the first correct orientation change the clock icon turns yellow

3. at the following correct orientation changes the clock icon turns gradually darker - e.g. green, blue, etc.

I bet that would be easier to "read" on a glimpse.

So what do you think?
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
it seems to run perfectly at last!

let me test it a bit more, but the UnlockOnPowerOn=0 bug seems solved forever.

my problem about the device locking in a middle of an unanswered call seems solved too.

I've had a strange behaviour when receiving a call ut maybe it is not TLP related, let me test it a bit more.

edit: after testing it for some hours, only once (1%) the device have woken up locked when turning it on. It seems that the autolockonpoweron=0 bugs are solved ZR, do you listen? you did it!
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Hi ZuinigeRijder,

2.2.4 Has fixed pretty much all of the problems that I was experiencing apart from the vibrate issue that I mentioned earlier.

The X is no longer visible at all - Fixed

The clock updates normally - Fixed

The device is no longer sluggish on unlock - Fixed

The only remaining problem is the vibrate issue. I don’t like the visual feedback from the clock, so rely on the vibration feedback to confirm that the device has actually been unlocked.

The vibrate on unlock from TLP interferes with the normal windows incoming call and vibrate and so only the TLP one short vibration is felt rather then the consistent vibrate of the windows incoming call, as such calls are missed.

This happens if you have “TouchLockAction” Unlock set for Incoming calls in TLP.
[Touch Diamond, MDA Compact IV Themes and Apps] e.gammieri:
I have founded another bug: I need to lock screen after ending a call, so I set the "TouchLockaction.exe" Lockscreen on the config dialog in the page of call event handling but it don't work! if I set the "TouchLockaction.exe" LockSuspend it work fine, but is'nt what I want!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The problem is that I cannot reproduce the problem with setting the StylusOutInToggleTime into 999999. So for me it is a mystery. I use .NET 3.5, but that should not make a difference.

Can you enable debug logging (logdebug=1 and logdebugdetailed=1) with the default value and then try to set it to 999999 and reproduce the problem. Because for me it is a mystery :confused:

Or am I the only one who does not have this problem?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
See my previous post. I cannot reproduce myself, so for me it is a mystery.

Can you post a debug log file, so maybe then the mystery can be solved?

The other problem reported is not a bug, but a feature, the locking of all the hardware keys, locks also the power key. I cannot do something on that, although I am searching for another reliable way of locking hardwaqre keys, without the power button.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think my default setting 8888 is wrong, any changes from not-portrait to portrait will be an orientation change :rolleyes:

So I will change the default into 343....."portrait - upsidedown - portrait" to unlock.

There is already so much to configure. People get scared with all the possibilities and tuning. And then you want it also with the capacitive touches. So I think I will not provide this possibility. When it is working well, you do not care too much about colors too (note that the number of capacitive touches and orientation changes is variable too).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Great. Thank you for the effort of reproducing and providing the logs. I am happy you did not decide to leave TLP as it was :) because of those problems. Your logging really helped to find the bug, although it was really difficult to find in my code.

I will post the official version 2.2.4 soon.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Sometimes small steps/improvements make a major difference. I am happy with all the comments and help from everyone. This makes in the end TLP better and better :D I hope people do not get scared with all those new versions with some of the bugs fixed. On the other hand, some of the bug fixes are only applicable in certain situations.

Ok, I decided to not vibrate/beep anymore when there is an incoming call, for lock and unlock. That should solve your issue. I will post that official version 2.2.4 soon.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is because of the check that it will not lock when a call is ended within 5 seconds. This is for making sure it does not get locked in other uses cases, when the phone awakened after the call was ended.

Can you explain the use case what you want to achieve?

Why do you want the screen on and locked?
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Thanks to you ZR, for the great effort you have done to improve TLP and to give us this incredible support.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Official version TouchLockPro 2.2.4

I just uploaded TouchLockPro 2.2.4 (there were some intermediate versions posted). See changelog for the bug fixes and the downloads section for the official version.

Thanks in helping to make TLP better and better.:)
[Touch Diamond, MDA Compact IV Themes and Apps] dan74:
You're right that "When it is working well, you do not care too much about colors". Finally I got it working as I like, but yesterday evening I was just testing the Gsensor unlocking and it was really hilarious how I tried to turn the phone in all directions and struggle to see the -1, -2, -3 etc :D

BTW, you've done a very good job with the new 2.2.4 - it also got rid of the "x" thing :) Keep it up!
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
I hope I’m not stepping on ZuinigeRijder toes here but could your power button issue be the following?

Start > Settings > System > Key Lock > Select ‘Lock all buttons except Power button

Let us know if that solves your problem.

Imran
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
ZR :D, i think that now is time to add the option to only lock certain buttons (if you find the way to program it) and then be able to unlock device pressing the "deeper" center button.

And also to be able to automatically change sip keyboards depending on keyboard & stylus states.

http://xdaforums.com/showpost.php?p=3198270&postcount=1121
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
I think it’s you that deserve the thanks finding bug’s is relatively easy when you have a large user base resolving them is the hard part!

Can’t speak for everyone, but I think having those incremental builds was not a problem, in fact it was very positive and showed that you were responding to people’s problems for which a lot of people will be grateful for.

However having three versions of 2.2.4 is confusing! You should have just increased the build number...

Thanks again, Imran
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
I attached the log-file and hope you can find something. I did it exactly as discribed in #1305.
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi, I've already posted the log on this post :

http://xdaforums.com/showpost.php?p=3249561&postcount=1242

And screenshot on this one :

http://xdaforums.com/showpost.php?p=3250145&postcount=1244

I also use .NET 3.5 as default.

I don't have this option on my phone (HTC HD)

BR
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
You might have something similar, have a look through the settings page...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I looked into the logging, and it says:

15:59:39 689411114 GetSetRegValue(): StylusOutInToggleTime

15:59:39 689411114 ==DEFAULT VALUE====: 1000

15:59:39 689411114 ==OVERRULED VALUE==: -7937

15:59:39 689411114 StylusOutInToggleTime: -7937

So this is the problem. I do not know why this negative value is in the registry. I cannot reproduce this one :confused:

When I put in 99999999 I see in the registry:

0x5F5E0FF or 99999999 decimal.

In the logging I see:

StylusOutInToggleTime: 99999999

When I put in the registry -7937, I get the value: 4294959359

This is more than the maximum 99999999.

So I expect you did put the wrong number inside the settings screen. Sometimes it is difficult to see what large number has been typed in with the SIP, especially removing numbers is not so nice visible.

What happens when you set in the registry StylusOutInToggleTime = 99999999

So I cannot explain the wrong number, than that it was typed in wrongly.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
That setting is for the built in lock. The API I use will lock all keys, also the power button. I have also set the setting you described, not to lock the power button. But still the HTC API I use locks all buttons (and touchpanel), including the power button.

Check yourself. When the phone is locked, the power button will not react....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately, the log file does not show the settings, so I expect only part is shown? Can you post a log file from the beginning, with first the default setting and then changing it into 999999 and then reproduce the problem?

You must stop TouchLockPro (via Programs) when copying \TouchLockPro.log.txt.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yeah, now those nasty bugs are solved I can try for the next improvements. I have a hunch for another way of locking the hardware keys, but if I loose focus, I still have to fallback on the old method.

I have searched how to detect lost focus on an elegant way, but did not find a clear answer with Google. So probably I have to experiment with GetFocus() and WM_ACTIVATE :eek:

I will also look into the SIP thingy, because this is something I want also automatically ;)
[Touch Diamond, MDA Compact IV Themes and Apps] lynxy:
How to Unlock only hardware answer/end buttons on incoming call and leave touch screen locked?

Could you please make only answer(send) and end buttons unlocked while all over buttons and screen locked.

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
Simply Great to hear this, take your time and let me test your future releases, i will do my best to find all the bugs :)

What a pity that pocketshield is not an open souce program, if so you could take a look at the code they use to lock some buttons and leave unlocked other ones.

If some day this feature is available, i would unlock power, center button & volume buttons and configure the center button to easily unlock device when an incoming call to avoid any possibility of bad interaction with Gscroll. BTW since 2.2.4 or maybe before, TLP seem to easily unlock device taping the capacitive area center button without any kind of bad behaviour due Gscroll presence.

TLP 2.2.4 works so fine now, i'm so happy with it. It is strange that no more people is using this great SW. Maybe the reasons could be because they simply wanted an incoming call locking SW, and due the famous but now solved autolockonpoweron=0 bug they decided to leave it, or maybe becasue a lot of people find TLA settings not very descriptive to quickly understand which kind of behaviour produce to the lock/unlock mechanisms of TLP. I perfectly understand all the settings but i remember at the beginning, i really found TLP very difficult to set up. After some testing and RTFM several times, i understood all the settings and then i was able to set it to fit my needs. But you know people use to don't like RTFM and they prefer to leave it and go for a more easily configurable program such as pocketshield (that i don't like at all) or other ones.

BTW thanks a lot again for bringing to us TLP.
[Touch Diamond, MDA Compact IV Themes and Apps] Icepick66:
Anyone else notice on touch pro, the capactive touch area will not work if you press it too quickly after turning on, you have to wait 1 seccond till the screen loads, if you accdently press it before that, you have to wait untill the touch pro's ring light dims again for the capacitive area to work again, when trying to pick up calls, this can be incredably annoying, obiously theres other backup options now which make this less of an issue.

EDIT: Upon further exploring the G sensor also has this issue, if the phone is 'busy' when turning on and you change orentation the counter gets stuck on -1 and wont increase till it resets, then you can do the gesture, maybe a application piority issue?

I've used sensorlock for many months now, and it doesent have this issue, so it is fixable...somehow :)

How to re-create, turn off -> on -> unlock (repeat), this kinda forces the phone to slow down, but when call is incomming the phone is busy and this is where the problem really shows.

also is there any way to increase the polling speed of the gsensor to make it as speedy as sensorlock?

+finnaly, capture screen orentation by keyboard pullout, if keayboard is replaced under x ms then the screen wont rotate and lagg.

+ and 1 moree, about your orentation problem, gyrator shows an "intermediate" level of orentation between face up and the 2 landscapes, meaning there is a midpoint and another set of orentations :)
[Touch Diamond, MDA Compact IV Themes and Apps] fourcc:
i think in advanced config or diamond tweak you have the option to change poll interval from default's 200ms.
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
If I put 9999 (four 9) in prefs I see 0x270F(9999) in registry

If I put 99999 (five9) in prefs I see 0xFFFF869F(4294936223) in registry -> CRASH

If I put 999999 (six 9) in prefs I see 0x423F(16959) in registry

If I put 9999999 (seven 9) in prefs I see 0xFFFF967 (4294940287) in registry -> CRASH

If I put 99999999 (eight 9) in prefs I see 0xFFFFE0FF (4294959359) in registry -> CRASH

If I put 99999999 in the registry I see 0 in prefs

I've attached the log file while I was playing around with these 9.

Seems you don't like the idea to have a simple checkbox to enable/disable the time constraints :(

BR
[Touch Diamond, MDA Compact IV Themes and Apps] DomSim:
this may have been covered already but im posting from my phone so please bare with me. i am loving this program now and have ditched s2u2 for it. i just have a few issues. most important is that the device unlocks when i recieve a text or email. i thought it was the light sensor so i set my phone face down and sure enough it still did. i would wait for 1 minute after getting then text then turn the phone over and it would be unlocked. second, after a call when using a bluetooth handsfree, it unlocks. lastly is, it still seems very sensative with gesture unlocking. thank you in advance for your response and keep up the good work.
[Touch Diamond, MDA Compact IV Themes and Apps] nuttsp:
Hi,

I like this program but I only want it to lock the phone when I turn it on. I already have a built in lock and curtain with my rom. I have tried lockwhenincoming = 0 but it still locks the phone when I get a call. Am I doing something wrong? I have a HTC ATT Fuze.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You should just have the default settings (autolockonpoweron=1) and on top of that:

CommandCallIncoming = "TouchLockAction.exe" unlock

See for more details settings screen 1

This way it unlocks at an incoming call. But be careful:

Yes, but the newer ROM's (e.g. official HTC ROM 2.0.3) have already an "Slide to Answer" window in front when there is an incoming call?

That does help somewhat, but the hardware keys are not locked, so when taking out the phone out of your pocket/pouch, you can still accidently press the reject key. Also when there is another event which does wake-up the phone (SMS, email, accidently pressing power button, etc), the "Slide to Answer" window will not pop-up, leaving the TouchPanel and hardware keys vulnerable for presses. TouchLockPro will still prevent bogus calls in these cases. Actually, TouchLockPro can nicely work together with "Slide to Answer" solutions, because it has a possibility to automatically unlock when there is an incoming call (but then also the hardware keys are vulnerable)..
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
1. Maybe it is the gesture which is way to sensitive. In version 2.2.4 I switched the default gesture from 8888 into 343, because any change back into portrait could easily unlock the phone. Although I changed the default, probably you will still have the setting 8888, so change this into UnlockOrientationSequence = 343.

2. I do not detect bluetooth, and default it unlocks when connected: UnlockWhenConnected = 1

If you use bluetooth more regularly, you could consider setting it to UnlockWhenConnected = 0.

3. Make sure you change your settings into UnlockOrientationSequence = 343 or something like that. Now it is not so sensitive anymore (bad thinking of me with the previous default 8888 :cool:)
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
The power button is only disabled if the screen is on and locked. If the screen is off and the device is locked the power button works fine! doesnt seem to be a problem to me, or am i missing something?
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Wouldn’t an alternative be to enable ScreenOffWhenConnected so if the device is in your pocket and you receive a call the device will lock the screen once connected as the light senor will not pick up any light.
[Touch Diamond, MDA Compact IV Themes and Apps] johnlara:
Where to download?

Where's the download link for the latest version? I can;t find it. Thanks - John