yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The power on button can indeed only be used for activating again after some time, sometimes it is 20 seconds or more. Now I unlock the phone before suspending, to avoid the power button problem. But it appears that the HTC API for locking the hardware keys, also when unlocked, introduces this behaviour.

When the power is put on, the locked BattClock has to be created and the capacititve sensor is opened. The latter takes unfortunately 1 or 2 seconds (yeah, not my code, but from HTC :p). Also I need to recreate the locked BattClock regularly, to keep the capacitive events coming in (if another application gets the foreground, I cannot get the touches anymore). This is now done once per 8 seconds when on.

This depends normally on a Windows Mobile System setting, I think Start -> Settings -> System -> Keylock

There you can lock all the hardware buttons except the power button, or you can there configure to also unlock by pressing any other hardware button.

I checked with another setting, and without StylusLock, you can indeed bring the phone alive by pressing any hardware button. When TouchLockPro is installed, this is not working. Apparently, the HTC API of lock all hardware keys does not take into account this setting.

You can try the LockTouchPanelOnly setting, because that does not use the above API (it just disables the power of the touchpanel).

I just use the battery life percentage I get from the Windows Mobile API. But I only poll for that once per 4 minutes (or when I get them automatically by an event), to avoid battery/CPU drain. So yes, it is not accurate within 4 minutes. In my experience the battery does not drain too hard within 4 minutes (only about 1 % or so), and I assumed a battery could last 400 minutes :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you uninstall also other locking programs?

Is touchlockpro.exe or another locking program still running (check with a task manager)?

Is there still a shortcut in your Windows startup folder?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
When you have a foreground application, it will hide the covered information of other windows. So in a full screen app, only the full screen app will be visible. In a non-full screen app, the start bar will still be visible (and the BattClock, when placed there). If you place the BattClock to the bottom bar, it will more often be hided, dependent on the application.

That was also the main problem I needed to solve, for getting the capacitive touches. I need a form in front :mad:

So I came up with a WS_POPUP child form of the taskbar, for the locked BattClock. And I regularly recreate that one (once per 8 seconds), to be sure it will go to top and it will get capacitive touches. You can check this too with a full screen application, like opera. If the TD is locked, you will see once in a while getting the clock coming in front.

So it is not a bug, but necessary to get the capacitive touches working....

Good to know for others too, my TouchLockPro can be tweaked to the needs :eek:

I rely on the HTC capacitive dll, and because HTC did not describe the API, others found out how to access it by reverse engineering. I posted source code for a proof of concept (see post #1) and now integrated this in TouchLockPro, in a real working application. unfortunately I do not think the sensitivity can be changed. Maybe we can think of other unlock strategies using the capacitive touches.
[Touch Diamond, MDA Compact IV Themes and Apps] raspdeep:
Having a 8 second timer is too long making it is unreliable. Can you have a check to respawn WS_POPUP using 1 second timer (or make it configurable via registry)? I double it will drain more battery because it only takes a few seconds to unlock the phone. Once the phone is unlock, you can disable the timer? From my testing, it seem once spawned, it stays on top but there may be scenario where it can go to the back.

I recalled you said the software captures the event when screen is on so perhaps you can enable the timer only on-screen event?
[Touch Diamond, MDA Compact IV Themes and Apps] Texandan:
Is it possible to "wake up" the capacitive sensors quicker when starting up the phone by pressing the power button? As it is now I have to wait in worst case for about 5 seconds until the capacitive sensors are recognizing my tappings.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am integrating unlocking with the light sensor. While doing that, I saw some improvements, to start the capacitive sensor more quickly. I also discovered some unexpected problems, so I am finding the cause of that. Hope that I can make the loading of the capacitive sensors quicker in the coming version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I will make it configurable in the next version.
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
Hi,

been using v1.2 for a few days now, it seems to be working really nicely, other than the sensors for tapping taking a while to wake up.

you have done a really good job, how is the action screen going? im itching to have a blast on that!!

take care
[Touch Diamond, MDA Compact IV Themes and Apps] peterbonge:
Difficulties: None, but it needs a lot of space.

To get it: Just have a search on "NETCFv35.wm.armv4i.cab" to get the CAB file directly (size should be 2707308 bytes). Or you can read some detailed information here (German):

http://subsembly.com/de/netcf.html
[Touch Diamond, MDA Compact IV Themes and Apps] Mr_Q:
Download it here
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
And read that topic too :

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

Regards
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
not really why you say that
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.2.6

I just uploaded TouchLockPro 2.2.6, see changelog for the (extra) fixes.

Hope no serious problems are found :rolleyes: fingers crossed :D
[Touch Diamond, MDA Compact IV Themes and Apps] peterbonge:
It needs about 6.4 MB space and compared to most programs I've installed so far this is much space.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can install it on the SD card.
[Touch Diamond, MDA Compact IV Themes and Apps] djkasmic:
@ ZuinigeRijder: could you please tell me how to unlock the phone via g-sensor and the sequence 343?? i am not able to unlock it.
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
Hi,

I am sorry to disappoint you but the stylus doesn't work. The files are attached. As you can see after accepting the 99999999 the next time entering the settingmenu without changing the value - the value is set back to 0. Even if I don't enter the settingmenu a second time the stylus in/out dosn't work.

21:05:44 NumericUpDown2Int: [99999999]

21:05:44 Result: [99999999]

21:06:05 stylusOutInToggleTime=99999999

21:06:07 NumericUpDown2Int: [0]

21:06:07 Result: [0]

Edit: 999999 (6 digits) results in 16959
[Touch Diamond, MDA Compact IV Themes and Apps] Weisan:
ZuinigeRijder nice app.

could it be possible to unlock with a single click of middle button?
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Nice request... I second that.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I just installed 2.2.6 and, but it shoes 2.2.5 in the about windows :)
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
Mine shows 2.2.6
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I did the upgrade with AppToDate! I will try again...
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
I don't think so. If the cab is so big, doesn't mean the files on the device get that space.

In any case for a device with so much on-board storage even 6.4 for a SYSTEM extension is not much.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Downloaded 2.2.6 from your web site, installed. I just tested to see if I would miss a call, and I still missed the call. The phone shows unlock, but none of the hardware or software buttons worked.

Am I missing something? What would be the suggested parameters?

Thanks,

Eric
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Removed 2.2.6

Unfortunately, version 2.2.6 has a serious bug, so I removed it from the download.

When using Internet, this will be seen as connected call. As a result it will not lock correctly :mad:

I will post 2.2.7 soon.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Ok! I had that issue, but couldn't figure it out !

Thanks for your great support :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, just uploaded version 2.2.7.

Hope this locks :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
If you have a Touch Diamond or Touch Pro, you can configure:

CapacitiveTouchesSequence = 2

With a touch of the middle button it will unlock then......

But e carefull, also in your pocket there is a (very) small chance that the capacitive touch is also triggered while in your pocket.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, the writing part I did workaround the .NET 2.0 bug.

However, also a bug is in assigning a value to a numericUpDown box.

Work around for that one is now in 2.2.7, hope no more .NET bugs are in :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, the normal way it would be portrait-upsidedown (so pointing to the ground)-portrait. Do not move too fast, because the default poll interval is 200 ms.

In version 2.2.5 I noticed it would not always react on gestures immediately. I do not know why that is :confused: When I touches the capacative area, then the gestures were noticed :eek:

In version 2.2.7. I therefore start/stop the gsensor when recreating the BattClock. For me it is working, but of course I am not sure for other phones.
[Touch Diamond, MDA Compact IV Themes and Apps] Weisan:
i already done that, that was why i made that suggestion. the capacity touch is way more sensitive than a single press in the middle since the middle button is "protected" by the capacitive panel.

first i used the 3 touch but sometimes i ended up touching 4-5 times cuz the first touch not always count.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am trying to find another way of locking the hardware buttons, and then I maybe can use a hardware button or combination for unlocking. This will be my next feature I am trying to find a solution for. Hope no serious bugs are found beforehand.
[Touch Diamond, MDA Compact IV Themes and Apps] erkme73:
Hi ZR...

This is a GREAT program. It was working flawlessly on my HTP Touch Pro (CDMA) for the first few days. But, even with periodic reboots, it became progressively slower to respond to unlock triggers. On a whim, I'm turned on detailed logging, and found that I get 600kb of this:

This just repeats non-stop. The "..." is my way of skipping to variations in the log. I'm sure I messed something up, but could you provide some guidance?

The symptoms are when I turn wake the phone up, the screen is unresponsive for the first 5-10 seconds - sometimes not responding at all unless I do a sleep-wake cycle a few times.

Also, just before it became unusable, I noticed that it behaved as though the phone was 'connected'. In other words, it would not lock anymore upon waking up as long as the "UnlockWhenConnected" option is on. It was almost as thought it thinks my phone is in use.

I'm sorry if this has already been discussed in the 140+ pages of this thread. I tried finding it, but my head started to spin. Let me know what I need to post, and I'll do it right away. Running the detailed log for just 1.5 hrs generated a 650k file.

I'm running V2.2.6. *NOTE* Just installed 2.2.7 and will give this a go. Waiting for the log to fill a bit before viewing it.

Thanks...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Version 2.2.6 was buggy and I have removed that from the site and uploaded 2.2.7.

The logging you see is from the 1 second TIMER I use. But I see not one log statement per second, but much more. Maybe this has to do with my bug in 2.2.6, maybe not.

If the problem is still in 2.2.7 just post a debug log as zipped attachment.
[Touch Diamond, MDA Compact IV Themes and Apps] Erazor2k8:
Hi all,

I've a question about this great plug-in. After i reached a call the Mobile Phone will not lock after set the device on "standby" (push the power button short).

Is this a error or how i can set up my device that it locks after finishing a call?

Thanks a lot in advance

Erazor
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
With the default settings, it should do that out-of-the-box.

Note that there has been shortly a 2.2.6 downloadable, which was not correct.

So make sure you use 2.2.7.

If this does not solve your problem, please enable a debug log file (logdebug=1 and logdebugdetailed=1), reproduce the problem and post the debug log file \TouchLockPro.log.txt as zipped attachment.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
With 2.2.7 I'm still missing call.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Please enable a debug log file (logdebug=1 and logdebugdetailed=1), reproduce the problem and post the debug log file \TouchLockPro.log.txt as zipped attachment.

Also describe in detail what is not working (unlocking via?).

Is the older version 2.1 also not working for you? Becuase that one did not yet have the gsensor and other way of subclassing.
[Touch Diamond, MDA Compact IV Themes and Apps] Ddriver:
Me to, if I become a call, then I dont heart nothing. :-(

I have default settings with the 2.2.7 and Diamond.
[Touch Diamond, MDA Compact IV Themes and Apps] erkme73:
Hi ZR...

The log with my WM_Timer entries is attached. For clarity sake, I deleted the original log files, uninstalled and reinstalled 2.2.7. So the log only contains entries from this morning. Thank you again.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
&^$%^#&^, last night before going to bed I tried it. It was not working :(

This morning, you ask me to debug, now it's working :confused:

I did a soft reset, and still working :confused:

I'm still sending you log....

Also, a problem I had before, is when using Bluetooth, I had to unlock before using the hands free voice command. My phone was not responding to the bluetooth command.

Thanks,

Eric
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, with setting LockTouchPanelOnly=1 I have a timer 4 times a second.

In previous versions, sometimes the locking of the TouchPanel was not fast enough. So therefore I do it more regularly in this case.

Later I added the locking touchpanel already at power off, but only in case of setting AutoLockOnPowerOn=1 or already locked.

So this logging is not alarming anymore, only gives more logging.

The debug logging was also not meant for running continously, so you need to remove the log file after a few days, or disable debug logging when all runs fine.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, sad to hear. I also have a Diamond with default settings and do not have this problem :eek: Which version did work for you? because I expect it is introduced lately?

Are more people having this problem? Or 2.2.7 is working as expected?

This information is important, because I must decide if I continue with the approach till now, or I must go for an alternative solution. After all, it does not always be a TLP problem, but of course it looks like it *IS* a TLP problem according some people :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] erkme73:
Thanks. So this:

21:29:09 1857904598 InvalidateClock()

21:29:09 1842930978 WinMain: 49157

The invalidate clock is not a bad thing?

I've turned off the logging to see if the performance improves. Is it possible that the problems came from a bad install? All the settings appear to be kept when I uninstall and reinstall the latest version. How do I clear everythign to go back to default - i.e. starting from scratch?

BTW - with the CDMA (Sprint) version of the TP, and TPL 2.2.7, I receive calls just fine. I turned the logging off, and the responsiveness seems like new. Perhaps that was tripping up the 2.2.7? I'll report back by the end of the day (US).

Thanks!
[Touch Diamond, MDA Compact IV Themes and Apps] aadadams:
I receive calls fine on the Fuze version on ATT and I am using 2.2.7 since release.
[Touch Diamond, MDA Compact IV Themes and Apps] momyc:
ZR ,

Confirmed also , missing calls with 2.2.7.

Also “TouchLockAction.exe” Unlock , doesn't seem to unlock the touch panel.

For some resons the 2.2.1 is working well for me.

I'll still keep trying the new versions.

Thanks,
[Touch Diamond, MDA Compact IV Themes and Apps] iago_00:
I wanted to use only the function that would turn screen off when I put the phone near my ear and turn the screen on during phonecall when I take the phone away from my ear?

Is that possible?
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
I'm on a Touch Pro and I don't have this problem with 2.2.7. I'm also trying it with GScroll and haven't had any of the previous call answering issues or lockups yet (although I haven't received too many calls since I started using both again). I should also mention that I use PhoneAlarm, which takes control of the notification sounds -- not sure if that might help me.

As for GScroll, there also does still seem to be cases where TLP and GScroll are both registering taps, but I can't seem to reliably reproduce that.

I am seeing one strange issue with this version: The settings screens are VERY slow. It takes about 15-20 seconds for each screen to render on my device. The screens were slow on previous versions, but not nearly this slow. I may try a clean wipe of the install and see it that improves it.

EDIT: Uninstalled and removed all the registry settings. The settings screens are still painfully slow after reinstalling. Disabled all sorts of stuff, but no help. I may have another conflict, but I can't imagine what it could be. This is not a big deal, since I don't access the settings, but it would be nice if it were quicker...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro version 2.2.7 problem poll

To get more insight in the problems some people experience with TouchLockPro 2.2.7, I opened a TouchLockPro version 2.2.7 problem poll.

Please vote (multiple selections are possible), so I get some insight.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The InvalidateClock is just a call TouchLockPro makes for updating the BattClock. So this is normal.

You can reset to the defaults by pressing the middle bottom button on the first TouchLockAction Settings screen. Or you can remove the registry tree HKCU\Software\ZuinigeRijder\LockSettings and restart TouchLockPro.

Normally, debug logging will not slow down the device very much. But of course, no debug logging is faster, because it does not need to write.

I do not know why it is now responsiveness. Maybe, that there is something which makes the responsiveness slower over time, somewhere a hidden bug, which only shows up over a while. Hope this bug does not reappear.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
When the screen is off, the light sensor is no longer working, so this is not possible.

But with TLP you can disable all locking features (like autolockonpoweron=0) and have the following settings to achieve the screen off:

* ScreenOffWhenConnected=1

The screen goes on when the call is ended with TLP.

Note that HTC has already a possibility to put the screen off when put to your ear (using the light sensor).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I added more debug logging in the TouchLockAction screens. And of course I workaround the .NET 2.0 bug with numericUpDown. But both I would not expect will cost much time :confused:

Is it also slow when no debug logging is enabled?

Do you have .NET 3.5 installed (because that does faster screen updates)?

I have a Touch Diamond and with debug logging enabled, times are approx:

* start TouchLockAction: 3 seconds

* first setting screen: 3 seconds

* next screen: 2 seconds

* next screen: 3 seconds

* next screen: 3 seconds

* next screen: 2 seconds

I use .NET 3.5.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you post a debug log file (logdebug=1 and logdebugdetailed=1), reproduce the scenario (call yourself with another phone) and post the debug log file \TouchLockPro.log.txt as zipped attachment.

Which ROM are you using?

Using TF3D?

Which applications installed?

Maybe that gives me a clue?
[Touch Diamond, MDA Compact IV Themes and Apps] Ddriver:
I dont know why, but now its function. 8-O

I make same softreset and 2 call outgoing befor.

ROM: 1.93.407.1 GER with TF3D with the 2.2.7 TouchLockPro
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
Hi,

thanks a lot, the stylus in/out is working with 2.27. I sometimes notice another strange behaviour. When locked and exposed to light the counter in the battclock counts backwords to -1 -2. But this is only sporadically. Someone else has this?

Anyway zuinigerijder this is a great app.
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
I love this app, but I have experienced the following problem twice in the last 2 days after installing 2.2.6 first and then 2.2.7 second [same problem with both versions]. All of a sudden TouchLockPro just stops working, for no reason that I can tell. Even after a soft reset it still doesn't work. When I go into the app to check the settings, I find that they have all reverted back to either all of the default settings [2.2.6] or to mostly default except that battclock is in a "stipe" setting [2.2.7]. Once I exit the settings screens, it starts working again.

Another thing that I notice with 2.2.7 is that it takes between 250 to 750 milliseconds to lock after a power ON. In prior versions, the moment I turned on the device I saw battclock or within 250 milliseconds, never longer. Now it takes a split second for battclock to load. Basically it seems a little slower. Settings were the same in the new version and the earlier versions.

I don't use the stylus or gsensor. I use either the light sensor the touch area to unlock. It seems that 2.2.7 is NOT as touch sensitive as in earlier versions. I think it was version 2.2.3 or 2.2.4 where you did something the touch sensitivity and it worked GREAT! Now it is a little more difficult to unlock.

Lastly I also use Lumos to control the backlight on my Diamond. Now this could just be my imagination, but since upgrading to version 2.2.7, it seems that Lumos takes longer to adjust for the ambient lighting in the room or outside. In the past Lumos would adjust my backlight in about 1 1/2 to 2 seconds, now it might take 5 seconds before it adjusts. Could the light sensor polling in TLP be affecting this? :confused: