yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] meirionwyllt:
Hi, thanks for your reply ZuinigeRijder.

Yes, the settings above are what I have too.

I also have the 'Incoming' event set to !LOCKSCREEN. Is this the right thing? When I receive a call I want the screen to turn on but want it to be locked until I unlock it with the NavSenor (!UNLOCK function). I don't have the 'slide to answer' and 'slide to reject' on my phone.

ZuinigeRijder, I REALLY like the NavSensor functions - they're great! The only thing, when I run Tomtom and want to lock the screen, I do a RightDown slide which does the !LOCKSCREEN function (red line appears at top of screen). However, this doesn't actually lock the screen - the screen can be touched as normal. Is there a way around this? No-one else on this thread seems to have reported this problem.

Also, when I press the power button, the red line appears (i.e. screen locked) for about 1 second. Is there a way to remove this, so that I can use the touchscreen after instantly after pressing the power button? I know this is nit-picking, but it's a bit annoying having to wait a little bit before being able to use the screen.

Many thanks for a great piece of software.

P.S. A search on XDA lead me to the Reg key 'DisableSMSWakeUpEvent' - thanks for the tip.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The !LOCKSCREEN on incoming event is superfluous, because it is already done by the other settings. But it cannot harm.

Probably TomTom uses ther same locking mechanism of the screen, so TouchLockPro does not get a chance to lock the screen, when TomTom is running. However, there is a second locking possibility, DoubleTouchPanelLock = 1, which does work for most people. But also some people report having a problem, when enabling this setting. I do not have this problem on my Diamond. But I decided not to make it the default setting anymore, because some people encounter a problem with this setting. Maybe then it locks the screen :confused:

Indeed, the first thing I do at power on, is lock the screen and then I compute if I need to lock, yes or no. This of course, to prevent touches. So this takes a few hundred milliseconds, dependent on your phone and what becomes active at power on. I think I cannot do much about it, because I always want to go on the safe side ;)
[Touch Diamond, MDA Compact IV Themes and Apps] golightlygl:
TLP randomly locking even with AutoLock off

As you can see from my settings (log attached) I have TLP set up to only lock hard keys on incoming call. As I understand it, this means that from a phone off position the following should happen:

Screen off, phone locked.

Incoming call powers on phone

TLP sees that AutoLockOnPowerOn=0 so prepares to unlock

TLP sees there is an incoming call and checks what to do

TLP sees LockWhenIncoming = 1 and LockWhenIncomingKeysOnly =1 so unlocks screen and leaves keys locked.

However, sometimes I find that the screen locks on regular power on regardless of the status of incoming calls. To be more specific, the behaviour is a little more complex as follows:

Power On

Lock indicator comes on (in my case red stripe)

Screen remains unlocked and keys remain unlocked

Screen powers off either manually or via SuspendTimeOuPowerOn

When power on again screen and buttons is "properly" locked

remeber that AutoUnlockOnPowerOn=0 at this point.

I have captured a log (attached) but it is very difficult to find a pattern as to whne this happens. At first I found it so difficult to capture a log that I thought it only happened when LogDebug=0! One thing I can say is that it is more likely to happen if the screen has been off for a while (say more than 1 minute).

I have rolled back to 2.67 and still find the pattern. But fom memory this did not happen with 2.6.4/5/6. I ahve some old betas of these and will try them out and see, but whislt I'm doing that myabe the logs will help you figure out what's going on.

Incidentally, although SuspendTimeOuPowerOn=0 in this example this was just a test I set. The same thing happens if I leave this at the default of 1500
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked into the logging and searched for:

POWER_ON_REQUEST

23:31:13 -336538618 POWER_ON_REQUEST

It locks due to an incoming call and this one is not answered.

23:31:31 -336538618 POWER_ON_REQUEST

There is a power off and immediately (withing 3 seconds) a power on and it locks

23:31:31 -336538618 SetDisabledPanelAndButtons(true)

23:31:31 -336538618 SetDisabledPanelOnly(true)

23:31:31 -336538618 HookTouchPanel(true)

Strange thing is, it also locks the TouchPanel, and you have the setting to only lock the keys.

I will need to check my source code, to see how it decides to lock the TouchPanel. My there is a bug in the determination to lock or not. Need more time to investigate that :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] golightlygl:
Maybe we've found the issue right here. There was no incoming call at that time. The power-on event was caused by pressing the Power button.:confused: I have doubled check the 'phone's call history to make sure and there was definitiely no call, incoming or outgoing, answered or not answered. How does TLP check if there is an incoming call?

I have been running 2.6.4 all day. A small difference. Yes the machine still locks at every power-on, but this time I never get a TouchPanel lock, only a keys only lock. So again, TLP must incorrectly think there's an incoming call but if it helps you to debug the code, at least it's locking the phone properly:)

Let me know what testing I can do to help you.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I use Telephone API interface for detecting incoming calls.

The following events lead to an incoming call:

1. LINE_APPNEWCALL

2. LINE_CALLSTATE

For LINE_CALLSTATE I only see it as incoming call, when

BearerMode is LINEBEARERMODE_VOICE or LINEBEARERMODE_SPEECH

and

MediaMode is LINEMEDIAMODE_INTERACTIVEVOICE or LINEMEDIAMODE_AUTOMATEDVOICE

For LINE_APPNEWCALL I do not do this and I do not know if this is possible. At least I have not seen this in examples while searching for how to use TAPI.

Looking in the log file, I see that every 5 minutes there is a LINE_APPNEWCALL. So I think you check if there is mail every 5 minutes :confused: And that is why TouchLockPro thinks there is an incoming call.

When mail is synchronized, I think the phone is no longer in a deep sleep. I do not know if the display is still off and if key presses would be detected. So maybe you can check that.

I do not detect the close connection call of the synchronization, so that is where TouchLockPro is maybe wrong. And dependent of the question above, maybe TouchLockPro should see synchronizing data not as incoming call.

So my analysis is that the problem is there when you power up the phone while it is synchronizing or power is still on.
[Touch Diamond, MDA Compact IV Themes and Apps] garyf:
Locking out headset calling

Is is possible to disable the headset dialer when in lock mode?

Somehow when I move my phone in some slight way, definitely without pressing the call button on my headset, my phone begins to make a call. It seems as if the redial sequence button being triggered inadvertently, or somehow the handset is made to believe the redial sequence has been triggered.

I'd love the headset buttons to be disabled also when the phone is locked or off. Is that possible?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
If you have a newer HTC phone, you can set HTCLockAPI = 1, then all the buttons are locked, including the power button when the screen is on. However, some other features, like unlocking via hardware keys, are then not available. So you need to unlock via the other sensors.....
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
error log

Hi,

Seems to be not a big thing :), nevertheless I wanted to discuss the topic: today I just browsed my device and I have found a log file by the TLP (attached).

The point is, the debug logging in TLP is switched off and in principle everything works fine, so I do not really understand the necessity for debug trace...

Maybe I overlook something and the things really go wrong?

Seems that the records get added on every softreset.
[Touch Diamond, MDA Compact IV Themes and Apps] licht77:
Hi there!

Are there any known bugs in relation to WM 6.5? I am using a cooked Wm 6.5 ROM and somehow the app doesnt what i want it to what is in a first step just to lock/suspend (to force entering WM PIN code) the device when i turn its face down.

What i did: Had a look into the "man page" and this very long thread, deactivated Lightsensor, Stylus, NavSensor, Slider, TAPI and added vibration to Lock/Unlock state for better feedback.

On Gsensor, I changed sequence 353 and 656 to "!LOCKSUSPEND" and Time to 4 sek (4000).

I produced some logs - but that doesnt really makes me smarter :)

Any hints are highly appreciated - thanks!

Update: To complete confusion, sometimes the Gsensor says "0:Unknown" - sometimes i saw correct readings there. During the time the attached log were recorded, the configpage said "0: Unknown" for the Gsensor - but nevertheless an actionlog has been produced...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
These are the error messages, you see.

Apparently you do not have a keyboard slider. You can get rid of these messages, when you disable the keyboard. Now TouchLockPro tries this at each boot/soft reset.

Also sometimes you get a problem in SetWindowLong (lock the screen) and sometimes there is a problem in starting a process (I expect TouchLockAction, double press of the BattClock).
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
Right :) My question is, if the debug logging is switched off, would it be probably more understandable to suppress creating the file and writing something in there?
[Touch Diamond, MDA Compact IV Themes and Apps] garyf:
HTCLockAPI blocks the headset? (I mean the redial sequence that can be triggered by the earphones)

Also, both my stylus sensor and gsensor status give me readings of unknown. Is there anything that can cause that?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You must just power off the device via the power button, to get it locked. I do not see power off or power on in the log file. Also TochLockPro will not force the PIN. However, people use it also on WM 6.5 and it is working there.

You did set AutoLockOnPowerOn = 0, so it will never lock.

In the logging I do not see GSensor activity, so apparently that is not working on your ROM. Is there a reason you disabled all other sensors?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It is doubtfull if I should log the non-existing keyboard registry key as error, but the others are errors which indicate TouchLockPro could not do its work correctly. And to detect that only when debug logging is on, will not show these possible problems, inside the huge log. So I will remove the keyboard as error in a next verion, also write a date in the log file when other errors occur.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, HTCLOckAPI = 1 will block the earphones redial when locked.

What phone do you have and which ROM?
[Touch Diamond, MDA Compact IV Themes and Apps] o.k.:
That's fine. And BTW, I double checked, "Use slider" checkbox is *empty* in my configuration, so maybe there is no reason to check the condition at all...
[Touch Diamond, MDA Compact IV Themes and Apps] licht77:
Too bad - but thx for the info! (Ah and i disabled all others for testing reasons to eliminate interference in the config while testing the g sensor *g*)
[Touch Diamond, MDA Compact IV Themes and Apps] garyf:
I'm running Longhorn on an htc touch pro with the 21731 sys.

My stylus sensor very rarely seemed active from the touchlockpro settings screen, maybe once around when I first installed it, but through many flashes and soft resets I've never seen it register again.

My gsensor seems to register almost half the time.

I've gotten a replacement touch pro because the keyboard light stopped working and this one has the same failure to register the stylus and gsensor that the last one had, I thought for sure the stylus sensor hardware was broken on my last one, but it seems that may not be the case.

I consider these fairly minor problems anyway.

Touch lock pro is very very great software.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
When you soft reset or boot the phone with the Stylus OUT, HTC software does not detect the Stylus position correctly. So be sure to put the Stylus IN while (re)booting. Also there can be dust between the Stylus sensor and the Stylus. You can try to take out the battery and gently blow away possible dust. Maybe that solves your Stylus problem :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] golightlygl:
I had posted a reply to this but whilst checking for your comments I see that my reply neever made it to the board! Sorry if you thought I was rude.:o

I do indeed check mail every five minutes and your explanation now makes perfect sense. i.e. the apparent "random" nature of the locking was such that it locked only when a mail-check/data connection was taking place. The phone does remain locked during a mail-check though - both screen and hardware keys are inoperative. This would imply there are different levels of power-on state. Maybe TLP should only kick into action in the screen power on state (if indeed that is detectable).

It is bizarre that LINE_APPNEWCALL gets triggered by a mail synchronisation which should not be a TAPI call at all. I don't know enough about WinCE or TAPI to be able to help differentiate a vocie call from a data call but there must be a way. From what I can see in the documentation, LINE_APPNEWCALL is always follwed by a LINE_CALLSTATE. This would imply that you could drop the LINE_APPNEWCALL test, or at least still check the status of LINEBEARER_MODE even when alerted by a LINE_APPNEWCALL message.

The other issue though is why the whole screen is getting locked rather than just the hardware keys. I'm hoping this will be easily apparent from the program logic:)
[Touch Diamond, MDA Compact IV Themes and Apps] longice:
Hi,

sorry if this has already been asked, but haven't found anything about it...

I'm having some issues - again - with G-alarm and TLP. When the alarm goes off, the screen is activated and TLP is unlocked. So far everything is fine. But after somewhat 20-30 seconds (as I'm just waking up :P ), the screen is turned off while the alarm continues. To turn off the alarm, I have to turn on the screen and unlock TLP before I can turn off the alarm.

Log file attached. Any solutions?
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Need help with a setting - cant find answer

Hi

first: Thanks a million for a great tool (had to appraise your great effort :-))

i have a HTC touch pro 2 (couldnt find any solution reading setting manual that worked for pro2), and have these questions:

1. I cant get the three times tapping on the batteryicon to work - noting happens. What do i have to do to make this work on my device? (where is the capacitive sensor located on a pro 2 ?)

Alternative where is the capacitive wipe up located on this device and how to activate this feature?

2. can i make a hardware button as eg "home" button unlock ? If so what do i have to do? I have tried entering the code UnlockKeySequence in section "Keyboard" (i have checked none of the options and i have left blank the field "UnlockedKeys" - is that correct?) for each of the 4 hardware buttons as specified in the manual but it appears that all are ignored by TouchLockPro:

15 = End:

114 = Talk

91 = Home

8 = Back:

The hardware keys seems to be responsive eventhough i have not entered any addresses in field "unlockKeys" - thats not supposed to work like that ?

3. I want keep alive OFF to save battery power (i take disabling this is identical to putting device in sleep mode?) - how can i see if this is disabled ?

4. In section "Telephone API" i entered the command string "!SCREENOFF " in the fields "incoming", "connected" "ended" but it seems that the screen bounces back on again after a short OFF period - it seems to just when connection is established. This is a BUG - or am i missing some setting?

thanks Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Need help HTC tocuh Pro 2 settings

OOps - very sorry for double posting :-/

Hi

first: Thanks a million for a great tool (had to appraise your great effort :-))

i have a HTC touch pro 2 (couldnt find any solution reading setting manual that worked for pro2), and have these questions:

1. I cant get the three times tapping on the batteryicon to work - noting happens. What do i have to do to make this work on my device? (where is the capacitive sensor located on a pro 2 ?)

Alternative where is the capacitive wipe up located on this device and how to activate this feature?

2. can i make a hardware button as eg "home" button unlock ? If so what do i have to do? I have tried entering the code UnlockKeySequence in section "Keyboard" (i have checked none of the options and i have left blank the field "UnlockedKeys" - is that correct?) for each of the 4 hardware buttons as specified in the manual but it appears that all are ignored by TouchLockPro:

15 = End:

114 = Talk

91 = Home

8 = Back:

The hardware keys seems to be responsive eventhough i have not entered any addresses in field "unlockKeys" - thats not supposed to work like that ?

3. I want keep alive OFF to save battery power (i take disabling this is identical to putting device in sleep mode?) - how can i see if this is disabled ?

4. In section "Telephone API" i entered the command string "!SCREENOFF " in the fields "incoming", "connected" "ended" but it seems that the screen bounces back on again after a short OFF period - it seems to just when connection is established. This is a BUG - or am i missing some setting?

thanks Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Volume Suggestion

Zuinige Rijder,

I have a suggestion that would "fix" the issue with adjusting the volume while locked that exists with HTC Volume Control or similar incompatible volume changing apps.

Instead of unlocking keys 117 and 118, you could detect these keys and control the volume within TLP as opposed to just sending those codes through to the system. TLP would have code included to alter the volume when 117 or 118 is pressed.

This would probably need to be an option, and maybe the 117 and 118 could be variable for different phones in case it's not universal but would default to 117 and 118.

On the keyboard settings you could add:

Volume Up Key: _[u]117[/u]_
Volume Down Key: _[u]118[/u]_

Does that make sense? Seem reasonable? (I may have those switched around but you get my point I think)
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
And don't forget the workaround available for CDMA Touch Pros

CDMA TOUCH PROs ONLY!!

install nueSIPStylus

run the config tool under Start > Programs > nueTools > nueSIPStylus and set it to query the stylus position on boot - this will set the correct value for TLP to read
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
Suspend off and on again

Hi, I am posting this question here, because it is somehow related to TLP, and I don't know where else to wrote it.

Is there any software to suspend the device and to turn it back on immediately (all into one link, to switch off, then back on, automatically).

This would be good for re-activating the swipe areas, when they loose their receptivity. For right now, the solution I have is to press the power button twice, once to suspend, and secondly, to bring the screen back on.

If I had a software to do automatically both moves, that would make it much more easy, and no need to overuse the hard button.

thank you very much for any suggestion
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Sorry guys but why do you post new questions in my thread - i asked quite different question that will be cluttered if other new questions is posted in the same thread - make a new thread for a new question please

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will test if I can detect if it is a phone call when I receive LINE_APPNEWCALL, like I do with LINE_CALLSTATE.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I assume you copied TouchLockAction.exe to the \Windows directoy, otherwise it will not unlock correctly by G-Alarm, also not with version 2.7.3 :confused:

Ok, I see:

8:48:46 -445471926 ===== ClockWndProc(WM_TIMER) power ON change ======

....

8:48:49 57556926 ExecuteRequest(): !UNLOCK

This one could be the GAlarm unlocking, I am not sure.

I also see a strange invalid command thereafter:

8:48:49 -445471926 Execute(): ???????0??

8:48:50 -445471926 CreateProcess failed: 2

And here:

8:48:50 57556926 SettingsChangedRequest()

So here you start TouchLockAction?

So I am not sure about those 20 seconds,

Is it possible youre backlight setting is 20 seconds?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
1. Ok, you misunderstood the 3 times tapping the BattClock. Three times tapping the Capacitive navSensor is shown in the BattClock, you cannot unlock by tapping the BattCLock. Unfortunately the Capacitive NavSensor is not available on the Touch Pro 2. Touch Pro 2 has a Zoombar, but that is not supported by TouchLockPro. But the Light sensor, stylus sensor, Keyboard sensor and GSensor work.

Pressing the BattClock opens TouchLockAction, when unlocked.

2. The Home button cannot be locked by TouchLockPro, but you can use this for unlocking e.g. by UnlockedKeySequence = 91;91 for a double press of the Home button to unlock. But the disadvantage is, it will go to the home screen, so therefore I have chosen the Volume buttons as default unlock keys.

3. You cannot see if the KEEPALIVE is active. But if you not entered !SCREENOFF, !BACKLIGHTOFF or !KEEPALIVE commands, it will normally not triggered. Also at power on, the !KEEPALIVE will be disabled again.

4. Apparently, the program which handles the incoming call, enables the screen again. ScreenOffWhenConnected = 1 already does the screen off, when you answered the call. Do you not want to see at incoming call who is calling? So I think it is not wise to configure !SCREENOFF. Better is to configure !SUSPEND at end call, because !SCREENOFF will keep your phone alive and not go into a deep sleepwhen it can.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Do you have example code for controlling the Volume without sending those keys? Because if that is easy, I can indeed detect them and control the Volume in a different way. And of course it should prefereably also Windows Mobile generic.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe you can use TouchLockAction with parameters to achieve this, e.g. !SUSPEND;!SCREENON. But probably this will not work, because the commands are too fast executed after each other. So you have to try yourself. And if the phone is asleep it will not execute command anymore.

Mortscript is something you can try, because probably you need a small sleep, although I have no experience with it.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

Thanks

1. I have chosen setting "during call" = "!BACKLIGHTOFF" and at END of call "!SUSPEND" is there a risc that KEEPALIVE is active with these settings or is the phone put to sleep at end of call ? I dont want to use more power than necessary

2: i have entered 91;91 in the UnlockedKeySequence and i still cannot unlock by typing twice "home" button - i get no reaction. Do i miss some other setting somewhere else?

thanks regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
1. better is to set ScreenOffWhenConnected = 1, that would do the same without the KEEPALIVE. At end call !SUSPEND is ok.

2. Hmmm, can you enable debug logging (LogDebug = 1 in the other settings menu), reproduce the scenario and post the log file \TouchLockPro.log.txt in the root of your phone memory as zipped attachment.