yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Aha, so the problem is really different. Does the phone freeze (as reported in the GScroll forum with version 2.2.5), or is it that GScroll still executes commands, while it is not supposed to do that (because TLP is on the exclude list)? But TLP will be running continously, so the exclude list will not help.

Currently, TLP is not a foreground window (actually it never has been). The BattClock recreation (default, once per 5 seconds) is only meant for showing the BattClock for a small moment in FullScreen applications. So that is not an option.

What you need, is a way to disable GScroll while locked by TLP. This could be something supported by GScroll or by TouchLockPro or a combination. Like G-Alarm has added support for TouchLockPro, maybe GScroll can do the same. If I need to change something to TLP, I am willing to do that, of course.

There are 2 scenario's I can think of now:

1) TLP writes a registry key when locked/unlocked, so an external application knows when it is locked and can read out/monitor the registry key and GScroll can then disable itself temporarily.

2) TLP is able to execute a configurable command at lock and unlock. One of the commands can be to disable GScroll (kill? or neat stop) at lock and start GScroll at unlock.

2) Is partly possible now, via CommandCallIncoming and CommandCallEnded. But separate command configuration for lock/unlock is better and more flexible. I do not know if it is possible via the commandline on Windows Mobile to kill a process? Or that GScroll has a neat way to temporarily disable itself?

Probably there are more possibilities, maybe GScroll author has a better idea :confused:

Anyway, it looks like it can be solved only in joined effort :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, I have a Touch Diamond with Dutch 2.03 ROM and do not have problems with TF3D and normal Today screen.

Can you post a debug log file (logdebug=1 and logdebugdetailed=1), reproduce the scenario and report the time when the capacitive touches are not detected. Post the debug log file \TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
You've got it -- GScroll still executes commands. I've never seen any lockups with TLP.

I was actually thinking of your reqistry key scenario as well. I like that idea better than killing/restarting the process, although, like you said, it would have to be a joint effort.

GScroll does have a registry key that can enable/disable the program(HKCU>ControlPanel>GScroll>"Disabled"). I wonder if it might be possible for TLP to disable GScroll on lock and then re-enable on unlock, using that key? I don't know if it's cool to tweak other programs' registry entries, but just a thought...

UPDATE: Strange, but 2.3.1 seems to have fixed this (I hadn't installed it yet, since I figured it would be the same). I'll continue to monitor...
[Touch Diamond, MDA Compact IV Themes and Apps] cancar:
I reproduced the undetected touches after wakeup with power key at 08:16

after unsuccessful touches I used the stylus to unlock

I hope the log can help.

View attachment touchlock.log.zip
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
@ZR

I use only the middle button to unlock my device. The response was a bit slow and I have missed a few calls. Now with v2.3.1 the response is much better.

Thanks ZR for putting 200% into this apps.
[Touch Diamond, MDA Compact IV Themes and Apps] George obama:
i like that
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I'm trying to use the CaptiveCommands, but not successful! It does not work!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I hope you do not have a Touch HD, because capacitive is not working for that phone. Can you post a debug log file, see if I can see capacitive presses in the logging. Also try touching the middle center button, because others indicate that is working better, or after touching the middle center button.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I have a Touch Pro, not the HD. I tried after touching the middle center button, and nothing :(

I copied the same command to all the possibility and connot make it work :(

After reading the logs here what I found:

9:52:19 169381850 SetCapacativeGesture(): Capacitive Gesture RightDown

9:52:19 169381850 Execute(): "\Program Files\PocketPlus\AltTab.exe"

9:52:19 169381850 CreateProcess failed: 2

Find attached the full log.

Thanks for your help.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparently the capacitive is working:

9:51:52 169381850 SetCapacativeGesture(): Capacitive Touch Left

9:51:53 169381850 SetCapacativeGesture(): Capacitive Touch Middle

9:51:53 169381850 ==================UNLOCK BY CAPACITIVE SENSOR==========================

9:51:56 169381850 SetCapacativeGesture(): Capacitive Gesture RightRight

9:51:56 169381850 Execute(): "\Program Files\PocketPlus\AltTab.exe"

9:51:56 169381850 CreateProcess failed: 2

9:51:57 169381850 SetCapacativeGesture(): Capacitive Gesture RightDown

9:51:57 169381850 Execute(): "\Program Files\PocketPlus\AltTab.exe"

9:51:57 169381850 CreateProcess failed: 2

9:51:57 169381850 SetCapacativeGesture(): Capacitive Touch Middle

So the command configured goes wrong.

Possibilities:

- 32 process limit

- Must double slashes be used? "\\Program Files\\PocketPlus\\AltTab.exe"

- Is AltTab.exe stored on the internal storage instead of phone memory?

Anyway, error code 2 means: ERROR_FILE_NOT_FOUND The system cannot find the file specified.

Hope this helps you to find the problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I only see once a capacitive touch:

8:12:40 -997733642 SetCapacativeGesture(): Capacitive Touch Left

Which programs do you have installed?

Is also the middle center button touch not working?

I also see that you have coupled actions (registry actions):

8:12:42 -454558890 CActions::HandleActionsNotification()

8:12:42 -454558890 CActions::HandleActionsStatus()

8:12:42 -454558890 LockScreen: 3

8:12:42 -454558890 LockScreenRequest()

Did you make shortcusts for that?

Maybe the vibration will interfere with the capacitive touches?

Does it work when no vibration configured?

I also do not see the light sensor giving light back? was it dark when you tested?

A lot of questions, because I do not have a clue.

Is a previous version of TLP working?
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I tried OperaL.exe, I tried double backslashes, no success. I even tried to have OperaL.exe running and be able to switch to it if it was already running (thinking it would bypass the 32 processes limit).

12:25:44 -1943122122 SetCapacativeGesture(): Capacitive Gesture LeftUp

12:25:44 -1943122122 Execute(): "OperaL.exe"

12:25:44 -1943122122 CreateProcess failed: 2

I'm confuse :confused: I really want this to work :)
[Touch Diamond, MDA Compact IV Themes and Apps] KRiZ-R:
Hi, with the new version I still have problems with capacitive touch.

It seems that it works while recieving a call.

I have made a log where I tested that, maybe you can see something irregular.

Greets, Chris

17:55:32 turned phone on and I tried to unlock the phone by capacitive, that did not work

17:56:02 phone turned of by itself.

17:56:07 I called my phone, so phone would wake up again.

17:56:12 while the phone was ringing, the unlock worked by capacitive touches

17:56:38 hung up the call and turned phone off

17:56:45 turned phone on again and tried to unlock again, didn't work anymore

17:57:02 Incoming call

17:57:07 touches are working again.

17:57:17 hung up phone

17:57:33 turned phone off

then connected to usb for logfile transfer
[Touch Diamond, MDA Compact IV Themes and Apps] cancar:
Some answers:

main sw that potentially may interfere:

touchpal

phone alarm

pocket informant

magicall

gprs monitor

middle center not working too (sequence defined 444)

no shortcuts defined

vibration: tried vith vibration disabled same result

tried in dark to avoid light unlock when i was trying with the capacitive touch.

please note that I always try on the main page of manila to be repetitive. any other page except today screen seems not to have this problem even the program folder.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I have figured it out. My program expects that when you use double quotes, parameters are specified.

So if you do not have parameters, you must leave out the double quotes:

\Program Files\PocketPlus\AltTab.exe

I will fix this in a next version, so both give the expected result.

But for now, leave out the double quotes, when you do not have parameters.

Hope it now works.

Sorry for the inconvenience.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Because it is only on the manilla screen, I expect one of the other installed programs is the problem. You can try to deinstall all the mentioned programs, and install one by one, till the capacitive touches no longer work. Especially because it is working with a lot of people.
[Touch Diamond, MDA Compact IV Themes and Apps] JoeSchmoe22:
This is a very cool feature, but I'm wondering if this is causing another problem that I'm having. Every so ofter, I turn on the device, TLP unlocks [I think] because the Lock disappears BUT the screen is still locked and the hardware buttons still work. If I turn it off and then back on and unlock TLP then the screen begins working again. Currently I have TLP to lock everything, not just the screen.
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
I have more problems with Capacitive Sensor in the last version (2.3.1)
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
YES ! It works :D

Thanks...
[Touch Diamond, MDA Compact IV Themes and Apps] cyberjaya:
Cloudyfa WM 6.5 ROM with v2.3.1

So far so good on the capacitive sensor running WM 6.5 ROM. Somehow version 2.3.1 capacitive sensor works much better in this ROM compare with Dutty 2.03 ROM I used previously. Will report back if capacitive sensor lost it's magic touch on this WM 6.5 beta ROM :)
[Touch Diamond, MDA Compact IV Themes and Apps] bent_e:
I still have problems with version 2.3.1 and capacitive touches. As I reported before, suddenly they don't work and I have to unlock by the light sensor or stylus. Then if I try to duplicate the error, they work again....

I have the official 2.03 DAN rom and the only programs I can think of that can influence TLP is G-Alarm and SmileySMS. Also I use TF3D and always unlock from the home screen.

I have reverted to version 2.2.7 which works just fine.

Bent
[Touch Diamond, MDA Compact IV Themes and Apps] schnuti:
I again must copy that statement.

Went Back to 2.2.7 aswell.:(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.3.2 testversion

I have a test version for the people who have problems with the capacitive touches in combination with the manilla TF3D today screen.

It is a long guess, but probably TLP is so efficient, it starts the sensors too early, especially in combination with Manilla. I do not have the mentioned problems, probably because I do not have much programs installed.

In this test version I wait 1,5 seconds before starting the gsensor and 2 seconds before starting the capacitive sensor. The other parts just go on immediately.

Please let me know, for the people experiencing problems, if this helps.

If not, I also want to know if the problem is also there with the standard Windows Mobile Today screen.

I really do not know if this could be the issue :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to see also also positive posts, because it often looks like it is only working for myself ;)
[Touch Diamond, MDA Compact IV Themes and Apps] Sobakawa:
Just installed 2.3.1 and after a fresh install, the capacitative strokes and touches works. Howeve, after changing the settings for the capactative strokes and touches, it will not work. Only taking out the stylus will unlock the phone. I will then need to power off and power on the phone before the settings take effect. Soft reseting if i remember correctly won't help too. Anybody facing this problem?
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
Whit the test version I dont have problems with the Capacitive Sensor. In 2 seconds the capacitive sensor works always. If this time can be less, would be perfect.

Sorry for my english, I am from spain

EDIT: After receiving a call, the capacitive sensor not to run again. I reboot diamond and it does not work too
[Touch Diamond, MDA Compact IV Themes and Apps] schvun:
I have tested version 2.3.2

After installing TLP capacitive touch does not seem to work, I have TF3D and home tab is active. If I slide to another tab it works there. I then slide back to the home tab or press the home button it now works there to. I open a program from the start menu and it works there but when I press the home, back or x/ok button it stops working. If I start a program from the program tab and then press the home, back or x/ok button it still works. If I start a program whith the soft buttons in TF3D or from swiping TLP-stile and then press the buttons it stops working.

Version 2.2.7 works for me thow.

HTC Touch Diamond

HTC Original ROM 2.03 swedish
[Touch Diamond, MDA Compact IV Themes and Apps] cancar:
2.3.2 tested

hi,

now the capacitive unlock from standard today screen is ok.

Unfortunately the problem still persists from manila screen. Only once during my tests the counter showed 1 touch before becoming unresponsive but in general it is not working.

Important info:even the gestures from the capacitive sensor do not work with manila as first actions after resume and unlock via stylus.

Only if i change tab in manila or start a program they start to work. I seems that after resume on manila only when I change tab the capacitive sensor is released to touchlock.

Hope it can help..
[Touch Diamond, MDA Compact IV Themes and Apps] alese:
I have similar problems as the others - capacitive touches just don't work or just sometimes.

I have made some tests, first with 2.3.1:

- Fresh after reset capacitive unlock works OK (I have no additional programs running)

- Then I got a call - I could unlock and answer, but after the call if I'm on TF3D I can't do capacitive unlock

- Unlock with stylus works

- If I'm not on TF3D unlock works...

With 2.3.2:

- Things are similar - it works after reset no problem

- I get a call - works OK

- After the call, if I'm on TF3D home screen I can't unlock (the only other app that runs is Batty that shows the battery on top of the screen)

- If I unlock with stylus and go to some program (I use MortButtons for my launcher) I can unlock, but back on TF3D unlock doesn't work again.

What I see, but I can't confirm 100% is that if something runs in addition in memory then capacitive unlock on TF3D doesn't work, Phone application stays in memory, also my applications that I use - MortButtons, Fitaly and Batty all have some "startup" applets that usually start after reset and by the look of it interfere with capacitive unlock.

Most of the times (but not all) I think MortButtons is the main problem in my case.

Just some additional info - if I disable TF3D and install old BigHTC Home Today plugin then the unlock works fine most of the time even with additional residential programs active, but it's not 100%.

Also I had problems unlocking with capacitive unlock with previous versions too, but never that big.

I'm using latest AZTOR ROM - it's 2.03 based with some tweaks but no big changes.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Today I had the first time the reported problems myself. But the problem also disappeared. I am going to combine the subclassing of the manilla home screen with the current approach. Till then use aversion which works the best for you.

Sorry for the inconvenience. I really want to solve this problem.TF3D with the newer ROMS has changed something introducing this problem
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
Cheer up!

Your work is fantastic, thank you to share it with all of us
[Touch Diamond, MDA Compact IV Themes and Apps] X2D:
This is AWESOME, thank you for adding the lower touch support that makes it so much better.

Keep up the fantastic work.
[Touch Diamond, MDA Compact IV Themes and Apps] jdogg4000:
Well i believe i have found the unlock-lock solution for me. I had only needed the following features:

1. Fast Unlock (Preferably faster than the iphone)

2. View missed calls, text messages, and emails

3. Compatibility with the most programs

4. Small memory footprint

After trying s2u2, pocketshield, sensorlock and g-locker, the simpleness of touchlockpro seems to have solved my 1 month headache. For all the features i needed to work i did have to use version 2.2.7 of TouchLockPro as i did have problems with 2.3.1. on duttys v4 rom but nonetheless i am so happy that i can go day to day with a better unlock solution than the iphone now. Thanx
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
Hi ZR,

I am having some problems with the capacitive touches, too (Ver. 2.32). The problem occurs when using the Swipe Up/down or Swipe Left/Right. Sometimes this works, sometimes not. I don't have any problems with unlocking through triple touch the capacitive hardware area. I have the 1.93 ROMs and .net 2.0. Hope that helps.
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
I am rebuilding my device with ROM 5.05. I am not sure if I'll reinstall TLP. I like this app and certainly appreciate ZR's attempt to make such a nice program.

I am trying to cut down on processes that run all the time. Darn 32 process limit.

TWO things would help me reinstall this (and both are to the advantage of TLP and TLP users anyway):

- If ZR finally includes the functionality to switch SIP method depending on pen and physical keyboard state (which are both polled anyway in TLP). Should be simple really.

- If ZR considers transforming TLP to a service instead of the process. This is what EVERY program that runs at all times should be. Please consider it.

In fact for this second thing, I am planning to open a discussion, an "initiative" let's call it, that will help rebuilding all our favourite "running at all times" apps to shift to being services (that have no limit). Yes it involves some extra complexity (for example you don't just "quit" a service) but it is the way to go. SPB has done it, so why not you.
[Touch Diamond, MDA Compact IV Themes and Apps] gjeremie:
hi,

First, thank you, because settings for g-sensor are correctly picked up now with 2.3.1.

i have a small request: would it be possible to add an option to lock only harware keys on incoming call?

I have a "Slide to Answer" on my phone (HTC HD), so for fast unlocking I choose to set : commandCallIncoming: "TouchLockAction.exe" unlock. But hardware keys must still be pressed in my pocket.

thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] the_scotsman:
I was about to install this on my Diamond, until I read this.

Does it not allow the hardware buttons only to be locked on incoming call?

I need something to stop me being able to accidentally pressing "reject" button in my pocket.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The HTC API which locks the hardware keys is also locking the TouchPanel. So as long I have no other way of locking the hardware keys, I cannot offer this option. TouchLockPro has no foreground window and as such it is diffcult to have another (default) Windows Mobile locking approach.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, by default it locks the hardware buttons and touchpanel on incoming call or awake.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The SIP is the highest on the list, after I have sorted out the problems some people have with the capacitive touches in combination with the TF3D home screen (on other screens it seem to work).

I will have a look at the Service approach. I did not know about that one, so it is interesting to have a look at it.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange that the capacitive touches work, but not the swipes.

Can you post a debug log file?

And indicate when the swipes do not work, but the triple touch do work?
[Touch Diamond, MDA Compact IV Themes and Apps] zweet16:
Hi, I installed touchlockpro and after awhile I decided not to use it.

But after uninstalling it from my fuze, now my battery indicator always reads 20% when it is fully charged!

I've tried draining the battery and then charging it up all the way and still the same thing.

If I go to Settings > Power, then the power bar is accurate in there. But in my Today taskbar, the battery % is wrong! It starts at 20% and slowly goes down to 0.

HELP!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TLP does nothing with the battery driver, it just uses standard Windows Mobile API for getting the battery percentage.

Which software is now displaying the battery percentage?

It can't be TLP, because you did uninstall it.....and also I assume a softreset, just to be sure it is no longer running.

I think this is unrelated to the deinstall of TLP.
[Touch Diamond, MDA Compact IV Themes and Apps] zweet16:
Oh, but it was immediately after I uninstalled it that I noticed the battery % being "red" even though it was fully charged.

I am using TF3D and Advanced Config.

Yes, I unstalled and did a softreset.

Do you have any idea what is wrong?! It is really frustrating.
[Touch Diamond, MDA Compact IV Themes and Apps] muhlatte:
After an incoming call, i can't unlock my device by the capacitive sensor! Can solve the problem when i go through the preferences and then close it! The stylus unlock works!

adit: seems not to be solved by the preferences gotrough!

maybe it's a known bug, but i was to lazy to read the thread :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have a standard Touch Diamond and I do not have a battery percentage and also it does not turn into red.

Do you have a custom ROM or is this part of the 'standard' fuze.

Maybe you have installed a battery indicator tool, which reports the wrong value. And you did not notice earlier, because the BattClock of TLP was on top of the battery indicator?

Anyway, it is not a TLP problem, so maybe others can help you?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There is a problem with capacitive touches when on the home screen of TF3D for some people. I am trying to find a solution for that.
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
Thanks for both. I hope you give a really hard look to TLP becoming a service.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Next test version, TouchLockPro 2.3.3

For solving the problem with the TF3D Home screen, I have the following solution:

- when no incoming call and when on TF3D Home screen, I simulate a left key press, so the TF3D programs screen is shown

This should solve the problem of the capacitive touches, because it only occurs on the Home screen.

But, of course you will not see the TF3D clock, so you need to unlock (by capacitive touches or another method) and press thereafter the Home button, or start a program from the programs screen.

It is a bit of a hack, but can people life with that solution?

Of course it will only be done when the capacitive sensor is enabled (CapacitiveToggleTime > 0).
[Touch Diamond, MDA Compact IV Themes and Apps] schvun:
TLP 2.3.3

Well, it works but it´s not elegant.

I suggest that you simulate right key press after the left one. Yes you end upp back on the TF3D home screen but the capacitive touch still works. It seems that it just need to dip it´s toes on another tab to get it´s mojo back.

Hope you solve it because I like TLP. :D

Diamond Original Rom 2.03 swedish
[Touch Diamond, MDA Compact IV Themes and Apps] peterpan911:
Hi ZR,

attached you'll find the logfiles. I tried some times and suddenly it works. Strange. I was not on the homescreen.