yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] d.joris:
My Problem with 2.3

Every Time, i will start TouchLockPro, i have to set on HKCU>ControlPanel>Keybd the string "StylusOutStatus" from 1 to 0. After every soft reset the string is 1. But that´s not the big problem. version 2.2.7 runs without a problem.

But version 2.3 doesn´t run. I can use the Capacitive Swipes only one time. I feel the unlock-vibra and the status changes, so as if it is unlocked. But there is also locked. After that, i must do a softreset. Nothing else functions.

which wrong I make? Please help me...

d.joris

___

HTC Diamond, Rom: MossisROM V2.8, 2.03.407.2 GER; Radio Rom: 1.10.25.25
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Try

"TouchLockAction.exe" LockScreen

Including the quotation marks at both ends...
[Touch Diamond, MDA Compact IV Themes and Apps] jznn:
command line parameters

...same error unfortunately. :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, can you enable debug logging (logdebug=1 and logdebugdetailed=1), reproduce the scenario and post the log files \TouchLockPro.log.txt and \TouchLockAction.log.txt as zipped attachment.

I expect a typo somewhere in your command, the logging will help to pinpoint the problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The StylusOutStatus is not related to TLP, but is more the hardware sensor of the Stylus.

For the other problem, can you enable debug logging (logdebug=1 and logdebugdetailed=1), reproduce the scenarion and post \TouchLockPro.log.txt as zipped attachment. maybe we can find the problem then :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
That is currently not possible.

I can add a setting that it disables lockmode (like Stylus and Slider) when on AC/USB power (and make that the default).

I think the new version is not a battery eater. I do not poll when the screen is off. And when the screen is on, the battery usage from the polling is neglectable to the display and other battery consumption.

Having my phone on the whole night, I had 10% battery less on my Touch Diamond, which is as normal.

Maybe it is a perception thing :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see in the logging you configured a wrong command:

0:13:11 -312139774 ==DEFAULT VALUE====: !UNLOCK

10:13:11 -312139774 ==OVERRULED VALUE==: !LOCK

10:13:11 -312139774 CmdRightUp: !LOCK

This should be !LOCKSUSPEND or !LOCKSCREEN

But that is not your problem.

In the logging I see it unlocks due to:

10:13:56 -1938100314 SetGesture(): 2

10:13:56 -1938100314 Execute(): !UNLOCK

10:13:56 -1938100314 UnlockRequest()

That is an unlock by gesture LeftUp.

Apparently your left touches seem to indicate a left up swipe.

You can practice to make more gentle touches, but that is not always possible, dependent on your fingers.

If you only want to unlock using the middle button touches, you should disable the default swipe commands, by making the commands empty for:

CmdLeftUp

CmdLeftDown

CmdLeftRight

CmdLeftLeft

CmdRightUp

CmdRightDown

CmdRightRight

CmdRightLeft

Hope this helps.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe this is too much info to put in the BattClock (1 character more).

But I will put it on the wish list.

G-Alarm added support for TouchLockPro, so it automatically unlocks TLP.

Maybe it is not working or you use an older version of G-Alarm?

In the first case, you should report the issue to the author of G-Alarm.

The exception list is already on the wish-list.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, because the vibration mechanism is not changed in all the TLP versions. Maybe it has more to do with the newer ROMS?

I did test myself this situation and it looks like the settings are not picked up correctly immediately after the change (especially when the length is made smaller). I expect the settings are picked up correctly after a softreset?

I will test myself better. At least it is a TLP bug that the settings are not automatically picked up correctly.

I will make a setting you can configure only to poll when locked (separate setting for GSensor as for Capacitive sensor). But of course you cannot use commands when unlocked then.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Currently it uses only one-thousand of a CPU cycle, so this is neglectable (0,1% CPU)

I do not have the experience it drains battery. I only poll when the screen is on, so the battery usage is neglectable compared to display and other battery usage.

Of course, when you can disable either G-Sensor or Capacitive sensor totally (why use 2 unlocking methods) or both.

Nevertheless I will make a setting to only poll when locked for both sensors, but then the commands when unlocked are not available.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I only poll when the screen is on. I do not have the experience that it drains battery. Last night I had only 10% less battery (8 hours), which is as normal.

The accuracy of the battery is not so good, so maybe it is also a perception thing....

Of course you can disable one of the 2 poll methods (G-Sensor or Capacitive sensor) if you have both sensors. Basically, the G-Sensor is primarily meant for Touch HD users, because they do not have the capacitive sensor.

But as said, I have both sensors enabled and I do not see extra battery drainage. I hope it is a perception thing, and not a TLP problem.

Anyway, I will add a setting so that you can configure it will only poll when locked (but than you can not use the configured commands when unlocked).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
See my previous post, I do not have this experience.

The battery indicator is not really good, so I hope this is more or less an incident and perception thing. Sometimes when I reset my device the battery percentage is shown very differently.
[Touch Diamond, MDA Compact IV Themes and Apps] jznn:
command line parameters

Please see the attachment….
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There seems to be a double quote at the end of the command, which is causing the trouble:

13:35:47 Main argument: LockScreen"

13:35:47 Error: Unknown action: LockScreen"

Be sure to configure the command exactly as shown, including the space and without the double quote at the end:

"TouchLockAction.exe" LockScreen
[Touch Diamond, MDA Compact IV Themes and Apps] gjeremie:
Even after a soft reset, my settings are not picked up correctly.

so i'll wait that you test this better.

Ok thanks, it's what I want.
[Touch Diamond, MDA Compact IV Themes and Apps] antjmon:
Thanks for the reply, I haven't run app2date recently so I was unaware of galarm's modifications. I'll give it a try, thanks again.
[Touch Diamond, MDA Compact IV Themes and Apps] jznn:
Many Thanks,

I never had issue creating shortcuts with TatalCommander until now.

With Resco It works flawlessly.

Thanks again
[Touch Diamond, MDA Compact IV Themes and Apps] dinfinity:
Of course, I've tried every combination of stylus related settings and none of them has resulted in the behaviour I prefer.

I've used virtually all versions of TLP up until 2.3 and have _never_ been able to insert my stylus into my Touch Pro without the WinMo long press end key lock (Unlock + *) being enabled.

This is also the case when I reinsert the stylus _a day_ after having taken it out.

I have the following settings:

UseStylus: true

SuspendOnStylusIn: false

StylusOutDisablesLockMode: false

StylusOutInToggleTime: 1000

Interestingly, with the SuspendOnStylusIn set to on, nothing different happens in comparison to having it turned off.

ZuinigeRijder, could you comment on this?
[Touch Diamond, MDA Compact IV Themes and Apps] KRiZ-R:
Hi, I've been using TLP for some time now and it worked like a charm.

I've been away for a while since it did not work with the AZTOR X2 rom.

Since the last few updates it worked again, but now with 2.3 update, again it doesn't respond to the capacitive area anymore.

After install it works for a short time, but some later it stops working, only the G-sensor, attach power and Stylus will unlock the phone.

I have attached the log files, I hope these can help you.

(I had it on USB, pulled USB out, turned on phone, tried swiping/touching the panel, wich didn't work, put it back on USB)

Groetjes,

KRiZ
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
I do not see this either. I've been running in standby with 2.3 for several hours today and I'm still at 95%...
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
I never use the lame WM locking, so that's probably why I don't see this issue. I'm not sure what events trigger that locking. I wonder if you checked StylusOutDisablesLockMode if it would behave any differently. That's the way mine is set. Anyway, I suppose ZR will have to comment on this.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The following settings will assure the stylus will never lock TLP when putting the stylus back in:

UseStylus: true

SuspendOnStylusIn: false

StylusOutDisablesLockMode: true

StylusOutInToggleTime: 0

But this is unrelated to WinMo long press end key lock (Unlock + *) being enabled.

So there is some other thing, outside of TLP, which triggers the WinMo lock. Do you have other programs installed, where a command is coupled to the Stylus in event? E.g Gyrator or something else?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear that my assumption that it does not drain battery is confirmed from your side. Especially, because people are afraid when someone says it drains battery, then at a sudden everyone is going to believe it (some people posted they wait for a version which does not drain battery) :cool:

People now hesistate to install version 2.3, while it is more stable, more responsive and having more handy possibilities. So just try this better version :D

Version 2.3 does not drain battery.
[Touch Diamond, MDA Compact IV Themes and Apps] lexluthor:
I'm having a problem with 2.3 where, after a while, I lose the battclock.

It's happenend 3 times so far.

The battclock is still there when locked, but unlocked, it just shows the default battery meter on my TP.

The only way to get it back is a soft reset.

Anyone else?

I never had this issue prior to 2.3.
[Touch Diamond, MDA Compact IV Themes and Apps] d.joris:
my logfile

Please see the attachment….

But, without setting HKCU>ControlPanel>Keybd the string "StylusOutStatus" from 1 to 0, there is no lock functions. Perhaps, i have a hardware-problem? until jet, i haven´t any stylus-out-function...

if i set stylusoutstatus=0, the locking/unlocking functions, but the touch screen is locked. then, only way is softreset.

Thank you for help...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have added some code for destroying the clock, when TLP exits. Maybe another app is just sending a destroy to the BattClock :confused:

Hmmmm, I think I just remove this destroy and make sure the closing of the other parts is done, when really exiting TLP.
[Touch Diamond, MDA Compact IV Themes and Apps] KRiZ-R:
After some testing, it does seem to work on an incoming phonecall.

After having hung up and turn of and on the phone, it doesn't work anymore. Seen in the log by pulling out the stylus when capacitive doesn't work.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
When I look into the zip with StylusOutStatus=1, then I see that always the lock is cancelled, due to stylus out.

21:59:33 -442693362 SetLocked cancelled, stylus out

When you set StylusOutStatus = 0, then TLP thinks the Stylus is always IN.

So you have definitely a problem with the Stylus sensor. More people have problems with the Stylus sensor, sometimes the sensor is too far away from the Stylus, so I does not sense if it is in or out. Or it sometimes senses the stylus. You can remove the backcover and battery and see if the stylus sensor is loose or there is dirt on it. Someone else cleaned it with air and thereafter it functioned again.

You can disable the Stylus within TLP by using useStylus=0. But then you need to unlock via the other means (GSensor, capacitive sensor). I see the GSensor working in the logging, the capacitive sensor not.

What phone type do you have? Touch HD? Because that does not have a capacitive sensor.

You can also consider to lock only the touchpanel and couple a command to a hardware key to unlock.

LockTouchPanelOnly=1

and couple a command to the hardware key:

"TouchLockAction.exe" Unlock

But of course, it will be better that you get also the stylus sensor working again......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see a lot of capacitive gestures. Can you pinpoint the time when it does no longer work, because I do not know where to look for now. Because I see a lot of Stylus Out notifications.

I see something strange in the logging:

20:16:05 -986332174 CCapacitiveTouchSensor::Enable()

20:16:05 -986332174 InvalidateClock()

20:16:05 -986332174 ===== DestroyLockedWindow() ======

20:16:05 -986332174 ClockWndProc: 71

20:16:05 -986332174 ClockWndProc(): 71

20:16:05 -986332174 InvalidateClockRequest()

20:16:05 -986332174 ClockWndProc: 275

20:16:05 -986332174 ClockWndProc(WM_TIMER): 23

20:16:05 -986332174 INVALIDATE_CLOCK_REQUEST

20:16:05 -986332174 InvalidateClock()

20:16:05 -986332174 SetBatteryLifePercentage(): -1

20:16:05 -986332174 InvalidateClock()

20:16:05 -986332174 SetPowerStateOn(true)

20:16:05 -986332174 CCapacitiveTouchSensor::Enable()

Looks like I enable the capacitivetouchsensor, while the power is not yet on. Maybe this gives a race condition? I need to check my code for that (not by hand now).
[Touch Diamond, MDA Compact IV Themes and Apps] peterbonge:
That would be nice.

I think you are right. I have the new version running for more than one hour now and the battery level didn't changed a single %.

But now I have a (maybe) new wish: it would be nice if the clock could be displayed as HH:mm and not as H:mm.

And when you'll start to change the optical "issues"? Things like:

- Different (and maybe "better") icons for both shortcuts. I suggest to use a common resource file (DLL) to keep the EXE files small.

- A more common/windows like settings dialog. Maybe with tabs or a softkey menu to switch the different pages. If you just want to change something on the last page the current settings dialog is really a pain. And some of the current pages are too crowded.

- Skinning of the action screen or at least an option to show a text below each symbol.
[Touch Diamond, MDA Compact IV Themes and Apps] KRiZ-R:
Hi!

I have made a new log. Same happens here again.

23:45	phone is off, incoming call then unlocked OK with capacitive

23:46	ignored the call, then turned phone off with powerbutton

23:47	turned phone on, cap unlock did not work anymore

phone turned off by itself

23:48	turned phone on, tried cap sensor, did not work, then unlocked with stylus

23:49	locked via menu, still no cap unlock

I hope this can help you helping me ;)

Greets, Chris
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
+1 for these suggestions... when you have time. I especially don't care for the white background on the TouchLockAction screen. Would love to be able to skin that with a semi-transparent PNG or at least a different color... :D
[Touch Diamond, MDA Compact IV Themes and Apps] imranbashir_uk:
Yes please that would make the behavior similar to 2.2.5 / 2.2.7, which would be perfect...
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
@ZR.... It worked perfectly now to my liking. I hope I wont face anymore issue later on.

I have also changed CmdOrientationSequence1-4 to empty and changed the CapacitiveTouchesSequence to 222; I want to try 2222 later on.

To suspend the device I still use the power button.

Thanks for your help and THANKS for the great apps.

Rgds

illi
[Touch Diamond, MDA Compact IV Themes and Apps] schnuti:
First of all thx for the great app and the time you spend on it.

Version 2.2.7 worked fine on my diamond but 2.3 gives me headache..

I cant get the capacitive touch to work, it even seems that the only method to unlock the phone is pulling out the stylus.

Installed on main memory, settings not changed....

Do you have any suggestions for me?

THX
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, maybe you have the same problem as someone else with the AZTOR X ROM. What phone and ROM do you have?

Can you post a debug log file (logdebug=1 and logdebugdetailed=1) and post the log file \TouchLockPro.log.txt as zipped attachment?
[Touch Diamond, MDA Compact IV Themes and Apps] schnuti:
Hi, I am using comec rom V6.1 GER based on 2.03 HTC Rom.

I will post a log later cause i am at work right now.

THX for your super fast respond...
[Touch Diamond, MDA Compact IV Themes and Apps] schnuti:
Just reeinstalled the app for the 5 time to make the promissed logfile and now it works fine...

Will keep you informed on further behaviour..

THX anyway...:)
[Touch Diamond, MDA Compact IV Themes and Apps] dinfinity:
D'oh! I never thought of that one (Elite RC2 ROM has Gyrator preinstalled) and kind of assumed it would be TLP related (considering the 'core business' of both apps).

So, problem solved.

Thanks, man!
[Touch Diamond, MDA Compact IV Themes and Apps] eclipse6220:
My debug files. I have problems with Capacitive Sensor
[Touch Diamond, MDA Compact IV Themes and Apps] bent_e:
I too have experienced problems with capacitive locking/unlocking in version 2.3. Sometimes the TLP 2.3 will not respond to capacitive touches. I have set unlocking by the light sensor, so I have been able to unlock it that way. Then, some moments later everything works OK again.

I think I will revert to version 2.2.7 which worked fine for me.

My rom version is the latest official rom for my language, 2.03.403.2 DAN.

Bent
[Touch Diamond, MDA Compact IV Themes and Apps] aadadams:
I've experienced this as well. I do not have light sensor set, so i have to remove stylus for access. I to, am considering reverting back to 2.2.7.
[Touch Diamond, MDA Compact IV Themes and Apps] schnuti:
I can copy that!

after short time cap sensor wouldn't work...next everything is fine??
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not have a clue, I do not experience problems.

I am not using TF3D, but the standard Today screen.

I am currently adding logging, to make it easier to pinpoint the problem. At the same time I am removing redundant logging, so the logfiles will not grow too fast and less CPU is used (although 0.1% CPU is not much, disabling the logging goes back to 0.0%)

I will post that version, including some other small improvements as soon as that is finished. I hope with that version I can better analyze the experienced problem.
[Touch Diamond, MDA Compact IV Themes and Apps] schettj:
After several days, the battery use does seem to be ok with 2.3

I have some trouble (Touch Pro/Sprint/Stock rom) with the touch gestures getting recognized, but generally it does work OK

I have noticed that the touch sensor area seems to be non-responsive when the backlight in that area goes off... I have better luck tapping the middle of the button to "wake up" the sensor (turns on the backlight) and then doing the gesture. Maybe that's just something that makes *me* feel better :)

Anyway, still loving the app.

I have noticed very rarely if you rotate and rotate back from landscape it battclock seems to be gone - it isn't it's just Waaay off screen (still thinks its landscape. perhaps?) and toggling back and forth again will bring it back.
[Touch Diamond, MDA Compact IV Themes and Apps] gjeremie:
i made several test, but my setting of only "5" (face down) for g sensor sequence is not picked up correctly, even after soft reset.

(works correctly with sequence "343" )

and sequence "353" doesn't work even after soft reset.

maybe it's related to the "5" (face down) orientation which is not detected correctly?

any new about this bug?

thanks
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
the problem was, that TLP took the configured defaults, regardless what you configured :mad:

I will post version 2.3.1 very soon (probably this evening) :)
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
It seems the issue with GScroll accepting capacitive touches while TLP is locked has resurfaced. Actually, I'm not exactly certain the problem was ever totally gone, but it seems like it was not a problem on earlier versions of TLP (2.2.5, maybe?) and GScroll. I'm not sure on whose end this problem lies, so I'll post on both forums...

The only place it actually works correctly is when my device is on the Today screen. Manila or any other program seems to register touches, while locked. It easily registers GScroll swipes and usually taps as well. I have touchlockpro.exe in the critical processes list for GScroll, as recommended.

I suspect there may be a problem with TLP actually having "focus" while the device is locked and in certain programs, but I don't know. The problem could also be on the GScroll end. I've attached TLP logs for a short period where I locked the phone and did some GScroll gestures and taps. If you need more detail than that, let me know.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
With version 2.3 onwards I do not need focus anymore to get the capacitive touches/swipes :). Can you mention which programs it is not working with (I checked OziExplorer, Opera, CorePlayer, IGO8, Camera), because I cannot reproduce.

Is it also not working without GScroll?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.3.1

Just uploaded TouchLockPro 2.3.1.

I also uploaded the corresponding source code, hope people get inspired and also share their creations.

Have fun again :p
[Touch Diamond, MDA Compact IV Themes and Apps] cancar:
Capacitive sensor

Hello,

version 2.2.7 was solving for me the problem that after deep sleep I was unable to unlock via the capacitive sensor (touches were very often not detected); this happens when manila or today screen ar running when the phone is going to sleep. It seems that the focus is stolen. If I run other programs before sending the phone to sleep the touches are regularly detected after wake-up.

Unfortunately with version 2.3 and 2.3.1 the problem is again there.

original 2.03 ita rom and no g.scroll
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
The problem is not that TLP is not working -- it's that GScroll IS working while the phone is locked. It happens this way on every program I've tried (except the Today screen, where it works perfectly, for some reason). TLP still registers taps to unlock though. However, I do not use the TLP swipes...

The focus must be why GScroll is still getting touches, even though I have TLP as an exluded process in GScroll. This means I will always be able to perform GScroll swipes and taps while the phone is supposed to be locked. Maybe TLP has focus when I'm on the Today screen and that's why the exlude for it in GScroll works???

Any way you can "force" TLP to maintain focus when locked, as a setting or something?