yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The problem lies in the fact, that TouchLockPro sees this as an incoming call:

18:42:42 1305685522 ===== ClockWndProc(WM_TIMER) power ON change ======

18:42:42 1305685522 GetLight(): 0

18:42:42 1305685522 Light OFF: 0

18:42:42 1305685522 ClockWndProc(WM_WINDOWPOSCHANGED)

18:42:42 1305685522 InvalidateClock()

18:42:42 1305685522 InvalidateClock()

18:42:42 1305685522 Clock Time update

18:42:42 1305685522 InvalidateClock()

18:42:42 1305685522 WinMain: 15

18:42:42 1305685522 ClockLockedWndProc(WM_PAINT)

18:42:42 1305685522 ClockPaint()

18:42:42 1305685522 BattClock RECT Portrait Left:0 Right:480 Top:0 Bottom:2

18:42:42 -1389825650 CTAPIDevice::lineCallback()

18:42:42 -1389825650 LINE_APPNEWCALL=(0, 325760, 2)

18:42:42 -317810070 SetCallStatus(CALL_INCOMING): 0

18:42:42 -317810070 NotificationCallStatusIncoming()

18:42:42 1305685522 ClockWndProc(WM_TIMER): 19

18:42:42 1305685522 NOTIFY_CALLSTATUS_INCOMING

18:42:42 1305685522 Execute(): !UNLOCK

18:42:42 1305685522 UnlockRequest()

18:42:42 1305685522 ClockWndProc(WM_TIMER): 8

18:42:42 1305685522 UNLOCK_REQUEST

Why did you configure !UNLOCK for incoming call?

I do not know for sure, I did look at the correct time. It will help me when the exact time is mentioned when the problem occurs.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
KeysOnly (LockWhenIncomingKeyOnly = 1). I do not understand that you want to configure !UNLOCK at incoming call. I would expect the above setting, which will lock the keys at incoming call (so not the TouchPanel).

For me the light sensor time is working correctly. Can you be more specific what is wrong with that setting?
[Touch Diamond, MDA Compact IV Themes and Apps] ramblon:
operation of this program

I read the instructions several times, still dont get it. Go ahead call me what you want. All i want is for the phone to lock when its in my pocket. I have it on lock now, sowhen its in my pocket and rings, i cant get it out of lock without figeting with some buttons and lossing my call. Im usin mighty rom reborn. When a call comes in how do i answer without lossin the call. I dont know what those values mean even after i read it sorry. i like the screen off thing when talkin but just want a simplified approach to lockin this ***** without all kinds a buttons goin off when its in my pocket. The slide to answer thing doesnt respond to answering. can i fix that with a setting? sorry if i confused you with my confusion. Thanks for this program. just need some extra guidance.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Version 2.6.2

I just uploaded version 2.6.2, see changelog for details.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
The log I gave you only contains the test... But why do I unlock on incoming call ?! Good question :confused: I turned that off! When it's dark, now I need to unlock before answering, but kind of make sense. I will give it a try.

I would like to make a suggestion, would it be possible to a separate SuspendTimeOutPowerOn for incoming call? I tried a smaller number 5 seconds (5000), so when I receive a SMS the device goes back to suspend after 5 seconds, but it's not useful with incoming calls.

Thanks,

Eric
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
With the default settings, it will lock at power on or awakening.

So you must unlock the phone first, before you can answer the phone.

Possibilities for the Sprint Diamond:

- auto unlock by the light sensor (if there is enough light)

- unlock by triple touching the capacitive middle button

- taking out the Stylus

- using the GSensor (portrait-upsidedown-portrait)

- configure the middle button to unlock: UnlockKeySequence (UnlockedKeySequence = 134)

Especially, the last one has been added recently, but you need to configure that one with the TouchLockAction Keyboard setting screen.

If you have a Slide2Answer solution (default in HTC 2.01 ROM onwards), you can also configure KeysOnly (LockWhenIncomingKeyOnly = 1), so that only the hardware keys are locked and not the TouchPanel, so you can answer via sliding the Slide2Answer.

Hope this helps.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hi Eric,

I thought it was possible to disable the wake on receiving a SMS with some registry tweak (Advanced Config?). I do not want to add another setting, because this scares people. It does not seem practical to go to sleep immedately after wakeup. So you need to find a tweak to disable awakening of SMS or take the small battery drain, because it is 25 seconds longer awake.

What I still want to add, is BackLight control. If this is implemented, and if there is no light sensed, the backlight can go off, saving battery power in that case (while in your pocket). But this is still on the wish list......
[Touch Diamond, MDA Compact IV Themes and Apps] nljuggler:
I assume that 'Ontgrendel bij verbinding' should be checked, right? If so, I can reproduce it.

Here's the log file you requested.

TIA

PS. I reverted all settings to default and then changed the following:

- Disabled pen sensor

- Disabled G sensor

- Unchecked TF3D problem workaround

- Disabled most nav sensor commands, but GestureRightUp and GestureRightDown are still working

- BatteryClock settings reduced to just the stripe

- Added SIP entries

- Set lock and unlock vibration both to 1
[Touch Diamond, MDA Compact IV Themes and Apps] mspingeld:
Trouble with last 2 versions

When I turn on the phone it should be locked. The lock indicator shows it's locked but it DOES respond to screen touches and the home button works. The phone-off hook button does not respond. Removing the stylus or plugging into AC power removes lock indicator. Logs attached.
[Touch Diamond, MDA Compact IV Themes and Apps] dwgibson:
V2.54 Suspend

It appears that when I load any version higher than this version, when I am attached to the PC, (using mymobiler) if I select "suspend" the phone screen stays on. With v2.54 and lower when I select "suspend" the phone screen goes out and I can use my Mobiler w/o having the phone screen always on. Maybe it's a setting that is not set correctly........ Any ideas?

Thanks in advance for any assistance!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to see there are also Dutch language :)

Ok, I see some nice programs as capacitive swipes:

12:28:54 94216526 CmdLeftUp: \Program Files\BTToggler\BTToggler.exe

12:28:54 94216526 CmdLeftDown: !\Program Files\Actionscreen\Wifi_ON-OFF.exe

Here is the log analysis:

12:29:10 -2070413838 SetCallStatus(CALL_CONNECTED): 1

12:29:10 -2070413838 ========================POWER_STATE_IDLE: SCREEN OFF==========================

12:29:10 94216526 POWER_OFF_REQUEST

12:29:10 94216526 ==========================DisableInput()==============================

When there is a connected call, the screen goes off, and the input is disabled, so you cannot press the wrong keys. ALso there are keys pressed:

12:29:17 94216526 LLKeyboardHookCallbackFunction hooked: 115

12:29:19 94216526 POWER_ON_REQUEST

12:29:19 94216526 IsConnectedCall(true)

12:29:19 94216526 IsConnectedCall(true)

12:29:19 94216526 =======================EnableInput()============================

12:29:23 -2070413838 SetCallStatus(CALL_ENDED): 1

When the call is ended, the power goes on.

So at power on, the phone should be unlocked.

But, because of the Screen off, at that time the phone is locked.

However, the setting UnlockWhenConnected, should not lock the phone. So that is a bug. I will see if I can solve that in a next version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
That the home button works, is known, I cannot block that one. That the TouchPanel is not locked, is a problem for some people. In the log I see the following errors:

14:41:18 -1566163006 Error in registering m_LockedWindow

14:46:31 -1566163006 Error in registering m_LockedWindow

15:49:41 -1566163006 Error in registering m_LockedWindow

15:52:59 -1566163006 Error in registering m_LockedWindow

16:11:07 -1566163006 Error in registering m_LockedWindow

16:24:31 -1566163006 Error in registering m_LockedWindow

16:40:20 -1566163006 Error in registering m_LockedWindow

17:12:46 -1566163006 Error in registering m_LockedWindow

17:58:39 -1566163006 Error in registering m_LockedWindow

18:06:29 -1566163006 Error in registering m_LockedWindow

21:15:03 -1566163006 Error in registering m_LockedWindow

21:15:23 -1566163006 Error in registering m_LockedWindow

22:22:01 -1566163006 Error in registering m_LockedWindow

11:43:36 1644956078 Error in SetWindowLong: 1400

11:59:06 -485374030 Error in registering m_LockedWindow

So that is why the TouchPanel is not locked.

What phone and ROM do you have? Because the code should just work.

For now, the only thing you can do, is enable HTCLockAPI = 1. This falls back on the old locking mechanism, locking all hardware buttons and TouchPanel. But you cannot use the nice new hardware key features then.

I do not know how to solve this problem (yet) :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] mspingeld:
Touch Diamond with ROM: 2.03.831.2 WWE
[Touch Diamond, MDA Compact IV Themes and Apps] nljuggler:
Yep, the Dutch language works. Because I have an WWE Diamond, so no Dutch version, I assume you base this on the regional settings. For currency, time, decimal symbol etc. obviously I prefer the dutch settings, but for programs like your I prefer the English language. Unfortunately I can't set it manually... or can i?

You caught me there! I reran the test after I actually reset the default settings, but the result was the same so I didn't create a new log file.

The last command is already disabled (hence the exclamation mark), because it happened too often that the WiFi connecting went on unrequested.
[Touch Diamond, MDA Compact IV Themes and Apps] bent_e:
I think I have figured out under what circumstances the phone locking does not work:

When I reset my phone and it boots, the screen to enter my sim pin number appears brifely and then disappears again. This only happens when I do not use TouchFlo - somehow TouchFlo manages to get the pin screen brought to the front again. When I have disabled TouchFlo, the pin screen appears shortly and then disappears when the Today screen appears. This means that I have to manually press the Network icon at the top, choose "settings" and the I am presented with the screen to input my pin.

With the 30 second TLP startup delay I did not have time to get to the pin input screen before TLP starts. In this case TLP enters the state where it shows the phone is locked, but it is not.

With TLP 2.6.2 and the 1 minute delay, I have time to get to the pin input screen before TLP starts. Whe I manage to do that, TLP works fine and locks the phone. If I do not go to the pin input screen before TLP starts, it enters the state where it shows the phone is locked, but it is not.

I do not have an explanation to this though....

Best regards,

Bent
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The regional settings are indeed taken by .NET Framework for detecting the language. You can get rid of the Dutch language, by removing the directory %Program Files%\TouchLockPro\nl, after installation and running once TouchLockAction. Then it falls back to English.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Wow, you have the reproducable scenario. I tried it on my phone, and also when I do not get to my pin screen, before TLP is started, it does also not Lock the TouchPanel :cool: The hardware keys are locked (except the known buttons, like Home).

If I stop TouchLockPro (via Programs) and start again, after having entered the PIN, then it still does not lock. I really have to soft reset and enter the PIN before TouchLockPro starts.

Hmmm, the good thing it is reproducable now, the bad thing, I still do not know what to change in my code, to circumvent this problem.

But people having the problem of the TouchPanel not locking:

- be sure to enter the PIN before TouchLockPro starts after boot/reset :eek:

Note, that I press the Call button, to get the PIN window.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
The hack does not work on my device :)

But I like your BackLight idea...
[Touch Diamond, MDA Compact IV Themes and Apps] ramblon:
Thanks for you quick reply.

Thank you for the further clarification.
[Touch Diamond, MDA Compact IV Themes and Apps] paalkr:
EDIT! Sorry, I was to fast. Unfortunately it does not solve the soft key issue. I have finally uploaded a video to YouTube illustrating the problem. Link to video: http://www.youtube.com/watch?v=lB52J0pekIo

As you can see the batclock lock indicator shows that the phone is locked all the time. First I tap and touch randomly on the screen to show that the screen is locked, then I hit the left soft button once, and nothing happens. Then I triple tap the left soft button, and the assigned application (thumbcal) launches. Inside thumbcal you can see that the touch screen is locked (gestures not working), except for the "soft button ribbon" in the bottom, which is still active even when the device is locked. In the end of the video I unlock the phone by triple clicking the send button, and as you can see all of the touch screen is unlocked and gestures works properly.

Hi!

Entering the pin before TLP starts after a soft reset seems to fix the not locking soft button issue on my diamond2 as well, and that is great news. How will this "bug" affect returning the phone from flight mode? In that case the device is not newly "waked" but TLP has likely been running for a long time, before the phone radio is turned off and then back on again.

Regards,

PK
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
Hi ZuinigeRijder,

I have just installed the new version and wanted to follow up with you on few things.

1. In a previous post we discussed doubling the commands available to the capacitive panel by distinguishing commands to be executed when the phone is locked and when it is unlocked. Are you planning to do this in a near future (certainly hope so!)

2. I cannot answer at all with the wired headphone unless I first unlock the phone.

3. If I turn the DetectBluetooth on but the bluetooth device is off it starts to behave herratically (both when I answer calls or if initiate the call). Even though it shows that the device is unlocked I cannot do anything as both screen adn keyboard are completely dead. The only way to get out of it is to turn on the bluetooth headphone and close the call.

I am attaching a log file where this happened twice (towards the end of the log) both receiving and making a call.

Basically I think that the DetectBluetooth option would not be necessary if you could achieve the standard behaviour that when a call is answered by the bluetooth or wired hedphone (if you can detect this events) the the phone should just stay in the same state as it was (locked if locked or unlocked if not).

I have my settings as follows:

UseTAPI = 1

UnlockWhenConnected = 1

ScreenOffWhenConnected = 0

LockWhenIncoming = 0

LockWhenIncomingKeyOnly = 1

DetectBluetooth = 1

DetectBluetoothLightUnlock = 0

CommandCallIncoming = ""

CommandCallConnected = ""

CommandCallEnded = ""
[Touch Diamond, MDA Compact IV Themes and Apps] ohyaknow:
ok so i for the life of me cant figure out where to dl this program at? do i have to donate or wha? can someone please link me to the download site or w/e thank you in advance

-ohyaknow
[Touch Diamond, MDA Compact IV Themes and Apps] fwt:
Do yourself a favor and read the first post carefully.

There is a hidden link with a very small text saying: "All the details and downloads of TouchLockPro you can find here: http://www.zuinigerijder.com"

On that page scroll down a bit and take a look at Point 7.

Maybe this could be useful ... hm ... what do you think?
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Doe anyone experimenting answering delay. The phone does not let answer. It unlocks but even when you press answer on the screen it does not answe. The screen responds. You endup missing the call.

I've been getting this a lot lately, and cannot figure what is causing it. Is it an HTC issue?
[Touch Diamond, MDA Compact IV Themes and Apps] varden:
I've changed the ROM and TouchLockPro ceased to work. It does not suspend after call anymore.

I include the log.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the Youtube Video. I think I cannot do much about it with the current locking approach of the TouchPanel. And the number of alternatives for Diamond 2 are limited, when the HTC LOCK API is used, you can then only unlock by the light sensor and Stylus.

Because TouchLockPro is now also suitable for non-HTC phones, with the new hardware key locking approach, the best thing I can think of, is a simple Foreground window as option, which you can unlock via a Touch Sequence. And if you have a slide2answer solution, this window should not be shown, in the other situations it should. I will think about it. Good suggestions are welcome.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is still on the wish list. Priority was given to the new hardware key locking. And I want to always fix problems first before introducing new features. Now I think an optional Foreground window is more important. Note that I do this in my free time, I do not earn much with it (a few cup of coffees), so be patient. I do this for fun, but I now sometimes do not have the energy to add new features. Especially, because often you only hear the things NOT working and you do not hear people for which it is working fine. Also answering the questions and problems takes much time......

Was this in earlier versions possible? I would expect not.

What keys are sent (you can enable debug logging to see those in the logging, when the phone is locked).

I did look into your log file and also tried to reproduce myself. But for me it was just working. So I do not have a clue what is wrong.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not have this problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see that you use version 2.5.2.

In the logging I see:

17:54:07 1233822742 POWER_ON_REQUEST

17:54:07 1233822742 NOTIFY_CALLSTATUS_ENDED

17:54:07 1233822742 SetCallStatus(CALL_NONE): 0

17:54:07 1233822742 Execute(): !LOCKSUSPEND

17:54:07 1233822742 LockSuspendRequest()

17:54:07 1233822742 ClockWndProc(WM_TIMER): 4

17:54:07 1233822742 LOCK_SUSPEND_REQUEST

17:54:07 1233822742 LOCK_SUSPEND_REQUEST: nothing to do

17:54:07 1233822742 SetPowerStateOn(true)

The problem is, that the LOCK_SUSPEND_REQUEST is done, before the power state on was set. I would have expected, that first the POWER_ON_REQUEST was fully handled, before the next request, NOTIFY_CALLSTATUS_ENDED was executed. In a new version I have set the power state on, earlier, so probably this problem is solved when you upgrade to the latest version.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
:(

I wonder what is causing that....
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
ZuinigeRijder, I have few questions for you.

1. Do you use unlock on licgn sensing?

2. Do you have other application running using the light sensor (G-Light, etc..)

3. What are your settings for TAPI?

Thanks for your help :)
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I found my problem, it is not related to any application, and not TLP :D

But now I need to find a solution :confused:

It happens only when I have data connection active. While on data connection, if I receive a call, the phone rings, it looks like it disconnects from data connection to voice, I then get the answering screen, BUT I CANNOT ANSWER :mad: Hardware button and the soft green button reacts, but does not answer. So you keep pressing, until you hope you can answer, but most of the time (9 of 10) I miss the call :mad:

If any of you know what I'm talking about, please help me. I did some searches on the forum. But did not find any solution yet.

Thanks a lot for your help, Eric
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have the default settings (in About screen, you can press "Reset to defaults") and the following differences:

- UnlockedKeySequence = 134 (unlock by middle button)

- KeysOnly (LockWhenIncomingKeyOnly = 1) (I have a slide2answer)

- LED number (LEDNumber = 2048)

- Configured SIP panel for Stylus IN and OUT

I have a Touch Diamond and HTC ROM 2.03.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, so it is related to a data connection.

What do you mean, when you have a data connection active? You mean, an active internet access via GSM/UMTS? Or via Wifi? Or Bluetooth?

Is the problem also there when TLP is not active?
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
It happens on my Bell phone on EVDO connection, I don't know if I get it on 1X. Not wifi and not BT.

And yes the problem occurs WITHOUT TLP :D So this is not your problem :) I just query the people here since we all use same sort of phone. And I'm very desperate. My next step will be to open a tread.
[Touch Diamond, MDA Compact IV Themes and Apps] jodeltje:
my settings screen is black and so is the text in it :s

can someone help me out?/knows what to do?

using 2.6.3
[Touch Diamond, MDA Compact IV Themes and Apps] sikes:
Software Input Panel Changer

Hello ZuinigeRijder, do you plan for next versions to distinguish between "Keyboard Out" and "Landscape"? I would be glad.

I ask that, because I have a Touch Pro and when I slide on the keyboard, I want to have a NullKb, but not when I use my phone in Landscape only.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange. Nothing has been changed in this respect.

Does an earlier version of TouchLockPro have the same problem?

Did you select a different Windows theme?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I thought this was not really needed, so I did not distinguish between Keyboard Out (which switches to Landscape) and Landscape, because in both situations you have more space for a SIP. But you are right, that you do may want not a SIP when the Keyboard is out. I will put this on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] aguida:
First of all thank you a lot for all your work on this utility. I said it before but I gladly repeat, as everybody in this community are really thankful for that.

Back to the capacitive panel I think that is really on the border line with a bug ;-). The only action that really makes sense while the device is locked is to unlock. Anything else I assign to the sweep actions should happen only when unlocked. If for instance you have assigned the POweroff command to one of the sweep actions, you risk to accidentally turn off the phone while it is in your pocket without knowing it :-(

Ok, maybe it is not a bug but a really really important feature :-)

And know that I am at that I have another really nice feature. I would like an option to revert to the Home screen when the phone is Suspended eithe rby the poweron button or by the the SuspendTimeOutPowerOn setting.

Thanks a gain.