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

I also suggest to allow user to select language.

A few corrections for French below:

BR

Yves
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will fix those translations in a next version.
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hi !

Ok, the Proximity sensor settings seems to solve 99% of the issues I've had with the phone unlocking itself.

Issue now during phone call, the screen refuse to turn on once turned Off :-(

BR
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Does it also not turn on when you push the power button?

Or not anymore by Proximity sensor?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It looks like TouchLockPro indeed does not do the InCallTweak. I see several times:

2010-07-27 19:52:02 -1510740302 Skipped InCallTweak: on power

Actually, InCallTweak is never triggered in the log file. Removing InCallTweak feature is not needed, if you do not want this behaviour at all just disable this option.

So it looks the standard Diamond feature is doing it.

Did you try to disable the Diamond feature?

http://xdaforums.com/showthread.php?t=398265

Option:

8. Prevent screen switching off during phone call
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
Issue still present

i have tried the above tweak but it seems that TLP interferes with it even when InCallTweak is disabled in TLP.

Same is the problem when I use TLP with TCIST. ( TCIST works well if TLP is not installed but when I also install TLP, even with InCallTweak Option disabled, I still have the issue of screen not staying ON.)

Could this be because of some reg entries created by TLP, and this registry being present even if the option of InCallTweak is disabled?
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
this might help

ZR

For Info regarding above issue of InCallTweak

This Info might help you to understand what is happening:

I installed this .cab on my diamond and the screen stayed ON during call. Then I installed TLP (InCallTweak=Disabled) but now the screen did not stay on even when the phone was being charged (in portrait mode).
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
As I understand this (Skipped InCallTweak: on power) was a FEATURE introduced by you on my request in version 2.10.4 and later fixed in version 2.11..................but this is not working because TLP does not have the option of= Ignore First Screen Off. This option is necessary as our Touch Diamond switches screen off when a call is connected........this option is present in TCIST.

If somehow this can be added in TLP.............FANTACTIC :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did have another close look at the provided logfiles.

2010-07-27 19:51:36 1180404246 SetCallStatus(CALL_INCOMING): 0

- Here you had the incoming call.

2010-07-27 19:51:39 1180404246 PBT_TRANSITION POWER_STATE_BACKLIGHTON

- And the backlight goes on

2010-07-27 19:51:46 1180404246 SetCallStatus(CALL_CONNECTED): 1

- And you answered the call

2010-07-27 19:51:50 1180404246 ========================POWER_STATE_IDLE: SCREEN_OFF==========================

- and here the screen goes off

I looked also closely to the TLP source code and it does not look like the screen_off is triggered by TLP.

So to be sure, the last Screen Off is the problem (4 seconds after you answered)? And this is the default behaviour of the Diamond?

So actually, you want the same functionality of TCIST, an option in TLP to do a screen on after first screen off or prevent the first screen off.
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
This would be ideal.

Exactly.:)

Preventing first screen off would be better as this ensures that the running window (e.g. Tom Tom) stays in foreground. But I am sure sure that we can live with the other option as well (TLP to do a screen on after first screen off)

In fact the most ideal situation would be if TLP can turn screen ON every time its switched OFF during a call when device is on Power.......no matter what the orientation is. I am saying this because this would be full proof.

Is this possible?:confused:

And thanks for your consideration.:D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will give it a try, I have a Diamond too, so I should see the same behaviour. It is a good idea to have the option to keep the screen on when on power. Normally you can set the minimal Power Requirement. Maybe you even do not want the backlight off when on power?
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
thanks in advance

yes. i do not want the backlight off when on power
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Not really, it's always a big stress to have to turn the screen on during a phone call.

BR
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
This program is very good.

Caltweak option doesn´t work good, in my case."Touch InCall Screen Tweak" has more options and with these options always work perfect. You could introduce more options in "calltweak"?

Thanks for the program.
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
TICST is good but TLP will be 'BETTER'

ZR is working on it (see this) and I think once this is done it will be PERFECT............. atleast for me :)
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
any update on 'keep screen on during call, when on power' issue

It seems ZR is busy with BattClock. Please do not forget TLP :D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Currently I have 2 codebases in 1 archive. So I want to incorporate the BattClock improvements into TLP first, to have a better overlap. So yes, I am planning to work on the mentioned issue. But it takes some more time.
[Touch Diamond, MDA Compact IV Themes and Apps] new2020:
Hey,

Thank you for such nice application. It is a great lock program as it can be used to lock screen on any active software running (sorry for my bad english).

But I found many new users got frustrated using this program due to less detail explanation and some default values. I also stopped using this because of some weird behaviours , but once I understood, it was fine for me to change the settings.

Here are some sugestions which may help new comers (especially non-technical) to overcome first time difficulties (advanced users can change the settings later):

By default, settings should be:

1. Disable all types of locking except Stylus, Nav sensor, TAPI

2. in BattClock, enable Stripe, lock indicator; desable battclock, clickable, stealth

3. in TAPI, incoming value: !unlock

4. in other settings: deselect UnlockOnACPower, SuspendTimeOutPowerON=0 (otherwise, new users cant understand why their screen goes black 3 sec. after power on or Media player is off)

Is there any settings so that for incoming call, screen is unlocked (sometimes I miss calls trying to unlock the screen and press answer key)?

Programmers normally use ! sign for negative meaning (so, !unlock may mean NOT unlock). So, can you change this command symbol or explain details.

include a help or pdf manuals
[Touch Diamond, MDA Compact IV Themes and Apps] braunie:
Diamond does not lock ...

I can do what I want my Diamond keeps unlocked.

If I start "TouchLockAction" and touch "Lock", nothing happens and the device is still unlocked?

Who has a glue? :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you disable other locking solutions?

Do you use another program which uses the same Keyboard hook approach?

Is your phone on Power when locked?

Is your stylus out, or is your stylus reported as been out (you can check in the Stylus Settings screen)?

The last thing is often a problem, because of dust between sensor and Stylus.

You can also post a debug log file, so I can look why it does not lock.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the good suggestions. Other people will appreciate it.

It is often difficult to have one solution which fits all. But I agree, this makes configuring more complicated. I could add a Wizard like option to configure, but still you need a good description. Other approach would be to leave out a lot of options, but that will limit the functionality for some people.

Sometimes it is difficult to do it all myself, writing a good program, design a good configuration User Interface, document clearly the possibilities. I am more a technical guy :( and my time to spend is limited too.

So if people would like to write clear documentation, I am very glad. Actually, the language is sometimes already a hurdle, especially for people not understanding well English.
[Touch Diamond, MDA Compact IV Themes and Apps] braunie:
It seems that, if the device is on the power supply, locking does not work. But without power supply it seems to work (I lock with the nav sensor).

Could I change the preset touch sequence in nav sensor-settings?

Your tool is very comprehensive, but it's difficult to setup.

I just want to lock the device by touching the nav sensor "6: RightDown" and unlock with "7: RichtUp". The other settings and lock procedures I don't need.

Thank you for your help.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Indeed it does not lock when on Power, because that does not make sense. You can remove the other NavSensor commands you do not need.

I also have a fallback for unlocking via the GSENSOR, because sometimes the NavSensor does not react on the RightDown or RightUp (a HTC problem). So I disabled all GSENSOR commands, except for one:

1 343 !UNLOCK

Of course you can choose your own move.

If you like the SensorLock way, configure:

1 656 !TOGGLELOCK

That way turning the phone in your hand (FACE_UP, FACE_DOWN, FACE_UP), it will toggle the lock.
[Touch Diamond, MDA Compact IV Themes and Apps] braunie:
Thank you, now it seems that everything works fine.
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
Suggestion

@ZR

Any chance of you adding "Fingerprint Unlock" similar to Fake FingerPrint LockScreen but with vibrate?

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] gulluwing:
I setted touchlock to unlock my device pushing the button with the windows logo but I discovered that if I press for 3 seconds the "call" button touchlock unlocks my pda: can I disable this action? I only want to unlock my device pressing the button with windows logo.

thank you
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do see this more as a gimmick than actual functional. It would be great if I could use the builtin camera to make a photo of your finger and only unlock if it matches ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Which PDA you use?

I do not understand what your are saying. The screen should be locked, so pressing the Windows Logo (I suppose it is the screen) should not unlock :confused: Or do you mean the proximity/nearby sensor of Touch Pro (2)?

I also do not understand the 3 seconds pressing the call button will unlock? Can you enable debug logging (LogDebug), reproduce the problem and post the debug log file in \TouchLockPro.log.txt.
[Touch Diamond, MDA Compact IV Themes and Apps] gulluwing:
my device is an htc touch2.

I use mobile shell interface and I placed the TLPToggle icon in today so when I want to lock my pda I push it. To unlock the device I push the button with windows logo (in my device there are 5 buttons: the halfway button). And this is all ok. Two day ago I put the phone in pant pocket and inadvertently started a call so I controlled as it did to unlock and I discovered that pressing for 3 seconds the talk button, the device unlocks.

can you help me?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you also post the log file TouchLockPro.log.txt, becaue the one you posted is less interesting.....
[Touch Diamond, MDA Compact IV Themes and Apps] gulluwing:
excuse me, now I send you the log file
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see in the logging it unlocks due to pressing key 91:

2010-08-28 18:20:10 1290554406 LLKeyboardHookCallbackFunction: 91

2010-08-28 18:20:10 1290554406 LLKeyboardHookCallbackFunction unlock key sequence: 91

2010-08-28 18:20:10 1290554406 ==================UNLOCK BY UNLOCK KEY SEQUENCE==========================

Did you configure this key to unlock on purpose?

Because I think this is why it unlocks :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] gulluwing:
yes I configured the key 91: it corresponds to the middle button of my device, the button with the windows logo. In this log I used the call button to unlock device: I pressed it for 3 seconds
[Touch Diamond, MDA Compact IV Themes and Apps] gulluwing:
you are right.

I changed the 91 with 117 volume up and now this problem disappeared. I don't understand why the key 91 corresponds to 2 button:I assure you that to unlock the device I pressed the middle button.

thank you and excuse me
[Touch Diamond, MDA Compact IV Themes and Apps] sirduffy:
I installed touchlockpro on my htc touch2 and I would like that the answering call slider (see the image above) was not blocked at incoming call: is it possible? how to set touchlock?

thank's
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In the TAPI Settings screen, set:

KeysOnly (LockWhenIncomingKeyOnly = 1)

Default it will default lock everything (so including TouchPanel). If you only want the keys locked at incoming call (e.g. you have a Slide 2 Answer and want to take the phone via the slider), you can enable this setting.
[Touch Diamond, MDA Compact IV Themes and Apps] BestAlways:
Bug on TouchLockPro 2.12.8

Whenever the phone restarts and the phone is not touched until TouchLockPro is executed, TouchLockPro will not be able to lock the phone. But if you restart the phone again and touch the screen (say the Windows Start button) before TouchLockPro is executed, then TouchLockPro will work normally. I hope this info would help fix the bug.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the tip. I always thought it had to do with the SIM PIN not yet filled in. Then of course you also touch the screen :eek:

I will investigate further and see if I can simulate a keypress or so.
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
Interesting finding

1. This is not working :(. See the log files.

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

2. The other thing is that I had been requesting for this but now I have found a solution myself :cool:.

I have install NoSleep and it works flawlessly with TLP.

I have enabled InCallTweek in TLP and then installed NoSleep.cab.

Now when the phone is on battery the InCallTweek works 'as it should' (except the minor :confused: issue that: 'screen is ON in landscape mode' as well................as I mentioned above) and when the phone is on AC Power the InCallTweek is automatically disabled/skipped and the screen stays ON in ALL ORIENTATIONS including portrait :D. [see attached log file.....the first part is when the phone is not on power the later part is when phone is on power. Sorry for the rather long log file :o]

Now when I use TomTom (along with myCarProfile) while driving and I get a call......the screen does not turn off (as phone is on charging) and hence TomTom is NOT MINIMISED and when the call finishes the TomTom window 'pops up' itself. No need to press any buttons :)

ZR= I would appreciate if you could look in detail at the attached log files and see if this makes sense. Also it would be great if the issue '1' which I described above can be addressed. Thanks :) Please do let me know what you think of this.
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
related to above post

would it be possible to make/release a version for right handed people (& current one being for left handed people). So when InCallTweek is enabled- (in right handed version) the screen is ON when phone is in ReverseLandscape and OFF in Landscape.

The benefit is when you are lying in bed :D :) ............it is not possible to see screen when phone is 'face up'.
[Touch Diamond, MDA Compact IV Themes and Apps] BestAlways:
Maybe an initialization of the "variable for touching the screen" would do the trick.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did not have time to look into the issues, I hope I get time next week. Actually I want to take over BattClock features and embed them in TouchLockPro too. So the codebases are aligned again.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, my idea was that it should be Off in Landscape AND ReverseLandscape. I will see if I can keep the screen on when phone is 'face up'. You know that it is dangerous to make a phone call in bed, like it is driving :D
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not think that is the case. Or did you spot the fault in the source code :confused:

I have just to simulate a screen touch. But do not know if that helps. I need to test it.
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
Clarification + Request

I think you got a bit confused by my earlier post. Let me clarify: There is nothing wrong with 'face up' orientation.

What I really wanted to tell is this:

2010-09-23 21:37:37 1174266758 IsConnectedCall(true)

2010-09-23 21:37:37 1174266758 Landscape XYZ 702,692,237 AngleXY 224,138

2010-09-23 21:37:37 1174266758 SetOrientation: Landscape

2010-09-23 21:37:37 1174266758 IsConnectedCall(true)

2010-09-23 21:37:37 1174266758 =====InCallTweak======SCREENON

2010-09-23 21:37:37 1174266758 Execute(): !SCREENON

2010-09-23 21:37:37 1157713258 HandlePowerNotifications()

2010-09-23 21:37:37 1157713258 PBT_TRANSITION

2010-09-23 21:37:37 1157713258 PBT_TRANSITION POWER_STATE_ON

2010-09-23 21:37:37 1157713258 PBT_TRANSITION POWER_STATE_PASSWORD

2010-09-23 21:37:37 1157713258 PBT_TRANSITION POWER_STATE_BACKLIGHTON

2010-09-23 21:37:37 1157713258 =========================POWER_STATE_ON============================

2010-09-23 21:37:37 1157713258 IsConnectedCall(true)

2010-09-23 21:37:37 1157713258 SetBackLightOff(false)

2010-09-23 21:37:37 1157713258 ======================== Change from screen OFF to screen ON ==============

2010-09-23 21:37:37 1157713258 SetScreenOn(true)

2010-09-23 21:37:37 1157713258 IsConnectedCall(true)

AND what I want to happen is the opposite i.e.

Screen OFF in Landscape AND Screen ON in ReverseLandscape

The reason is: I am right handed and I want screen to switch off when phone is next to my ear while its being held in right hand........the orientation is Landscape in this case.

I also want screen to 'switch on' when phone is in ReverseLandscape so that if I am in bed while making call, I have the option of looking at the phonepad/screen by tilting the phone into ReverseLandscape.

That is why I requested you to release a version for Right Handed People.

PS: Touch Lock Pro is my favorite software. Thanks to you.
[Touch Diamond, MDA Compact IV Themes and Apps] JediMaster:
Hi ZuinigeRijder and thanks for this great piece of software.

I own a Samsung i8000 and I want to use proximity sensor to lock/unlock phone: I've installed Samsung Mobile SDK v2.2 and all sensors are working, but when I set to use proximity sensor to lock/unlock it only works once.

When I unlock phone and put it for the second time in my pocket it remains unlocked.

What am I doing wrong?

Thank you in advance for support.

Bye.
[Touch Diamond, MDA Compact IV Themes and Apps] john_smith:
hi from Spain, anyone can say me the key code of central button of a omnia 2 i8000 , for configure the unlock, because i´m testing and i cannot unlock when i have a mistake, on my old omnia i900 it recognizes the gestures and i can unlock this but ion the new i8000, only run keys, not light or gsensor, i don´t know why.

thanks for all

Andres
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok. That would mean that I need to make it possible to configure the landscape or reverse landscape (or even all orientations) for InCalltweak. And the configuration of TouchLockPro is already so difficult :cool:

I have to think about it.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you enable debug logging, reproduce the scenario and post the log file TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
When you enable debug logging and reproduce the scenario, you will see in the TouchLockPro.log.txt logging which keys are hooked. You can post the debug log file as zipped attachment, if you want help about which keys are hooked. Maybe I can also see why the light and gsensor are not working. Did you install:

Omnia Pro, GT-B7620 Armani, GT-I8000 Omnia II, SCH-i920 Omnia II:

# smi_wm_pro_sdk_redist_2_1_0.cab with Windows Mobile Pro 6.5
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
Request (Continued)

NO. You do not need to do that. Just release a version which has the OPPOSITE settings built-in. :)

If you do not want to do this, then, atleast ensure that screen is OFF in both Landscape & ReverseLandscape.;)
[Touch Diamond, MDA Compact IV Themes and Apps] JediMaster:
Thank you for answer, I've solved my problem: I think it was a bad installation of Samsung Mobile SDK, now all is working like a charm.

I use unlock by proximity "not near", but also movement and light sensors are correctly registered in TouckLockPro.

Only one question: when I forget to lock screen by pressing button, should TouckLockPro automatically lock on proximity "near"? If so this is the only thing not working, let me know.

Thank you very much.

Bye.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear the problem is solved.

You can configure the command what to do by "near". But by default it does not lock, because in general this would be cumbersome I think.
[Touch Diamond, MDA Compact IV Themes and Apps] BestAlways:
I don't have the source code :)

It is definitely the first screen touch that makes the difference. Without it, locking won't work after a reset. I always do it whenever I turn on my device :(
[Touch Diamond, MDA Compact IV Themes and Apps] omek07:
did someone find what happend with G-alarm and doesnt wake up the phone ????

I have problem with that i have late to my work 2 times i dont know what to do ....

Please help
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
i am using g-alarm with touch lock pro without any problems :)
[Touch Diamond, MDA Compact IV Themes and Apps] omek07:
What version of G-Alarm my friend ????
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you check if the Volume is on highest ;)

Can you reproduce it (e.g. setting G-alarm a few minutes to the future) :confused:

Does the problem reproduce with and without TouchLockPro?

Why do you think it is a problem of TouchLockPro and not a G-Alarm problem?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am going to look if I can provide a solution. For now just touch the screen, like you are doing already ;)
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
finding

i have not noticed this problem :)

tlp is best
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
[q]

to ZR

any thoughts on this?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, I will first go for screen off in both landscape as reverse landscape. And I will think about the other proposal.
[Touch Diamond, MDA Compact IV Themes and Apps] omek07:
Volume OK

Without TouchlockPro i dont have this problem

I dont know my friend which program has the problem, i am searching it but i can not find what happen....

i test it and when is the time to ring the phone it doesnt... When i open the screen with power button then the Alarm is ring.

Without Touchlockpro the phone is wakeup and ring ....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, if you can reproduce it, maybe debugging logging gives me a clue.

Enable debug logging, reproduce the scenario (and make sure to post the exact time when the alarm is going off) and post the debug log file TouchLockPro.log.txt in the root of your phone.