yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] hoimeo:
Hi, I got crash of Opera when using TLP. After I open and exit Opera,when I touch on the Nav then the crash appeared (the device was in unclocked condition).

I figured it out that when I set CapacitiveCommandsWhenUnlocked=0 in Nav Sensor setting then the problem is solved but I had to accept to lock the device by using G Sensor instead.

I'm using Diamond Touch Rom 1.93
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, because I also use Opera in combination with the NavSensor.

Which version of Opera do you use?

Is it reproducable? Can you describe the exact scenario to reproduce?

Can you enable debug logging (logdebug=1 and logdebugdetailed=1) and reproduce the scenario and post de log file \TouchLockPro.log.txt. Please note the exact time when it occurs. Maybe that gives me a clue?

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is already solved locally, as part of solving Also execute CommandCallEnded when the incoming call is not answered

So wait for the next release for this solved.

I think double tapping will even more easily trigger nav sensor commands. Also this can interfere with the unlocking sequence. So I do not feel this is an improvement. But, of course you can couple more commands to the nav sensor.
[Touch Diamond, MDA Compact IV Themes and Apps] hoimeo:
I'm using Opera version 9.5 b2745. (updated from the original version 9.5 b1522, overwrite Opera9.exe, OperaL.exe and OperaPreL.exe)

The file was crashed is Opera9.exe so I go to Windows folder again to run it then open the Opera browser -> exit Opera browser -> touch the Nav downward to function the lockscreen -> Opera9.exe crashed.

The error information detail requires to be sent to Microsoft. I could see the error detail but couldn't understand anything within and I don't know where it was stored.

This is the debug log file was zipped. The time when it occurs was 22/04/2009 at 16:22:50
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I see the Nav Down at this time:

16:22:20 -957813482 SetCapacativeGesture(): Capacitive Gesture RightDown

16:22:20 -957813482 Execute(): !LOCKSCREEN

and

16:22:21 -957813482 SetCapacativeGesture(): Capacitive Gesture RightUp

16:22:21 -957813482 Execute(): !UNLOCK

and

16:22:49 -957813482 SetCapacativeGesture(): Capacitive Touch Right

In between I see nothing strange.

I also could not reproduce. I have HTC Dutch 2.03 ROM with the default Opera. Looks more like a bug in Opera, because it also uses the NavSensor for zooming.

Are others have the same problem?

Is the problem also there with the original Opera?
[Touch Diamond, MDA Compact IV Themes and Apps] evolution100:
Hi,

i install the TouchLockPro Version 2.4.1 but my HTC Diamond didn't lock!

All settings are default.

When i push the off button and then the on, my phone didn't lock

After a reset, the same problem

Can anyone help me? How can i activate the lock?

In the othersettings menu is the autolockonpoweron is active

Thans for your help

Mark

HTC Diamond with the original T-Mobile Rom 1.93.x.x Windows Mobile 6.1
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hi Mark,

it will not lock when e.g. the stylus (sensor) is not detected or when on AC/USB power. Some people have a problem with the Stylus hardware sensor.

You can enable debug logging, by setting logdebug=1 and logdebugdetailed=1 in TouchLockAction and post the debug log file in the root of your phone memory, \TouchLockPro.log.txt.

That will give me a clue what is wrong, but I expect a stylus problem.
[Touch Diamond, MDA Compact IV Themes and Apps] evolution100:
Hello,

here are the logfiles. I hope you can help me

Mark
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Indeed the log file says that the Stylus is out:

22:19:10 -1507989482 SetLocked cancelled, stylus out

I assume you did not loose your Stylus or that it was not in :rolleyes:

This is an occurring hardware problem, which is reported by others too.

You can try to gently clean the Stylus sensor or check if the Stylus Sensor is not too far away from the Stylus. Remove the battery, blow away gently the dust in the neighbourhood of the Stylus. Maybe that solves the problem.

If you cannot fix the hardware problem, you can disable the Stylus sensor usage in TouchLockAction. But, this means you cannot unlock by the Stylus and also your phone will not awake when taking out the Stylus. The latter is a function unrelated to TouchLockPro.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
scrolling bug maybe? Windows Mobile 6.5 + SPB + Touch Lock Pro = weird scrolling

Does anyone know a work around?

SPB Mobile Shell 3 + Windows Mobile 6.5 + Touch Lock Pro 2.4.1 = weird scrolling

I have gone through multiple roms to figure out why I was having this scrolling issue with SPB Mobile Shell when none of my friends with Touch Pros and SPBMS and Windows Mobile 6.5 were.

Then I figured out, after a lot of testing, that it was TouchLockPro 2.4.1 that was making it scroll weird.

By scroll weird I mean, you finger scroll your contacts down, it scrolls down fast like normal, you put your finger on the screen to stop it but it keeps scrolling down. you finger scroll your contacts up but it keeps scrolling down. it slows on its own to a stop. then it accepts the touch to stop that happened a few seconds ago. then it accepts the finger scroll up that happened a few seconds ago and starts scrolling up fast. you try to stop it again and again it does not recognize the touch until after it has slowed to a stop on its own.

As you can guess this is very annoying and very hard to find a specific contact. But I LOVE Touch Lock Pro and no other locking program will suffice. And I love SPB Mobile Shell and I don't know of anything else I could use as an equivalent replacement.

I have not tried this on anything other than windows 6.5 but I have tested this with multiple roms including Juicy 7, MightROM5, JD's 52x, SSK 1.8, starROM, all with the same results.

Scrolling in SPB Mobile Shell 3 is perfect until after Touch Lock Pro is installed and starts up.

Does anyone know a work around?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you try to disable the different sensors one by one of TouchLockPro, to see if one of the sensors is giving this weird result. After disabling via TouchLockAction, be sure to soft-reset the device, so the sensors are not initialized. Maybe it is the NavSensor?

You can post a debug log file (logdebug=1 and logdebugdetailed=1) \TouchLockPro.log.txt, maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Thank you for the awesome app, the quick response, and the suggestions! I will do this and post my resutls.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
SPB Mobile Shell Conflict

Problem: SPB Mobile Shell does not scroll correctly with Touch Lock Pro 2.4.1 installed.

As requested, here are my testing results. Please let me know what you would like me to do as far a logging goes. A step by step would be nice. Or I could turn on logging, do everything below, and then send you that. Just let me know.

Juicy 7 rom with SPB Mobile Shell 3 installed from a cab downloaded from spbsoftwarehouse.com – tested scrolling in SPB contacts – all is well

Fresh install of Touch Lock Pro 2.4.1

Waited for TLP to start up and the battery icon to show up

Tested scrolling in SPB – glitch is present

Reboot

Tested scrolling – glitch

Unchecked all boxes on the NAV Sensor settings page, tapped “Next” until I was out then tapped the top right icon

Tested scrolling – glitch

Reboot

Tested scrolling – glitch

Made sure TLP settings were still intact as I had set them, they were

Unchecked EVERYTHING in TLP settings

Tested scrolling – glitch

Reboot

Tested scrolling – glitch

When I went back into the TLP settings, even though I know I unchecked everything, the following were still checked

UnlockOnLightSensor

BattClock

So I unchecked UnlockOnLightSensor and BattClock again but this time checked Stealth and then “Next” until I was out and then the top right icon

Tested scrolling – glitch

Reboot

Tested scrolling – glitch

Start > Settings > Remove Programs – Removed Touch Lock Pro

Tested scrolling – and it is working perfectly again
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, this means that it has nothing to do with the sensors.

Then it must be that the BattClock gets a lot of updates due to the scrolling and as such slowing down the operations. Can you enable debug logging and post the debug logfile and reproduce the problem.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I still miss a lot of translations :mad:

So far we have the following translations:

English

Dutch

Spanish

Polish

German

Chinese (simplified?)

Romanian

Greek

Make sure the TouchLockAction screen is also translated in your language. Please provide the texts for the following:

Lock

Suspend

Exit

Settings

Reset

Off
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
SPB Mobile Shell Conflict

reinstalled TLP

restored the default settings

checked both debug logging options

exited the settings

went to the contacts section in SPBMS

finger scrolled down

tapped to stop but it kept scrolling down

finger scrolled up but it kept scrolling down

SPBMS Contacts stopped scrolling on its own when it hit the bottom of my list

SPBMS Contacts then started scrolling up because of my attempt in Step 8

Unchecked both options in TLP Settings

This is consistent with my previous experience

Attached are the two log files I found in the root directory of my Touch Pro.

Please let me know if there is anything further I can do to help.
[Touch Diamond, MDA Compact IV Themes and Apps] Aizek!:
I install the TouchLockPro Version 2.4.1 but my HTC Touch HD didn't lock :)

New Rom version

RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship

with new touch.dll. May be problem in this dll?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I see the following sequences:

12:45:40 -870624390 ClockWndProc(): 32

12:45:40 -870624390 WinMain: 512

12:45:40 -870624390 ClockWndProc(): 512

12:45:41 -870624390 WinMain: 281

12:45:41 -870624390 ClockWndProc(): 281

32 means:

#define WM_SETCURSOR 0x0020

512 means:

#define WM_MOUSEFIRST 0x0200

#define WM_MOUSEMOVE 0x0200

218 means ??:

TouchLockPro does nothing with these callbacks.

I had earlier a problem with a slowing down device, when one of the events I did subscribe was not there. But that was solved.

Maybe I should add some logging, to see if this could be something similar... I will see if I can post a special test version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe the same problem with the Stylus Sensor as here. . You can post a debug log file, to see what is wrong.
[Touch Diamond, MDA Compact IV Themes and Apps] Aizek!:
Yes, if stylus sensor is active - lock not work :(

If checked LocIndicator only - his not show on screen

If I lock device manually from menu, i can't suspend it from power button. EnableInputAtSuspend is enabled

P.S. Capacitive Nav Sensor very need :)
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
I am curious. Why does TLP affect the functionality of the touch screen while the phone is not locked? I would think that TLP would have no effect at all on the touch screen while the phone is not locked.

I am a programmer and would really like to write a program that is fairly similar to yours. But I haven't done much with Windows Mobile (mainly just windows, database, and web stuff, just a tiny bit with Windows Mobile) and would like to get started but may need a push in the right direction if you have any advice.

My ideal screen lock program would do this:

When the screen turns off, either by pressing the power button or the timeout occurring, NOTHING can turn it back on except pressing the power button. Even if you get or make a call, the screen would stay off until you press the power button.

And that is all.

ALL screen lock programs, except for yours, fail to lock screen correctly when it comes to phone calls - either incoming, outgoing, or both. Yours is perfect, plus more. I'm just not sure why in this particular case it affects the functionality of the touch screen while the phone is not locked.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Power On Source Detection Question

ZuinigeRijder,

In the code for TouchLockPro, when you're handling an event like the screen turning on, can you tell what caused that event?

For instance, can you tell if the screen came on because the user pressed the power button as opposed to the screen coming on because an incoming call was received?

Thank you
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You are one of the unlucky ones with a stylus hardware sensor problem:

8:45:05 -1445391734 SetLocked cancelled, stylus out

I see also, that you tried to disable the Stylus (UseStylus = 0) and then it locks. You can try to gently clean the Stylus Sensor, by removing the battery and blow away dust around the Stylus/Sensor. Or maybe the Stylus Sensor got lose.

If that does not help, the only way is to keep the Stylus disabled, from TouchLockPro perspective.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am also puzzled about the problems you describe. Although the BattClock receives those events, it will not do anything with it and this should not slow down the device. So I have no idea why this behaviour is there in the combination of software you described and Window Mobile 6.5.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Unfortunately, I cannot detect the cause of why the screen/power came on.

If you look at the power.cpp, you see the detection of power on in method HandlePowerNotifications(). This is a standard Windows Mobile event. I cannot detect what the cause of the power on is :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] Aizek!:
i was clear sensor and his work correctly... unlock and lock when stylus sensor is on is worked. thanx!

but i have problem with g-sensor. all settings is default, g-sensor is not work :(

Russian translation:

Lock: Блокировать

Suspend: Усыпить

Exit: Выход

Settings: Настройки

Reset: Сброс

Off: Выкл.
[Touch Diamond, MDA Compact IV Themes and Apps] QWERTY99666:
sorry for stupid question, but how do I lock the device using the Gsensor?

it says -GSENSOR orientation changes (e.g. Portrait-Face Up-Face Down), no need to press the power button! -

but this works 1 in 100 times for me...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In a next version, you can see/test the GSensor orientation changes in the TouchLockAction settings screen.

The defaults are chosen, that they are not triggered too fast. Also the GSensor polling is not too fast, so you have to move not too fast, to activate the orientation changes.

http://www.zuinigerijder.com/Settings.html#4.4

If you want easier locking/unlocking, change the sequences for locking and locksuspend, e.g. 43 and 35. Even more sensitive would be something like 93 and 95.
[Touch Diamond, MDA Compact IV Themes and Apps] MadMax1978:
Aebutton plus 2.6.3

Hey great programming man!

Really like it, i tried several locking tools but yours totally rules above the rest! i like the custom time to set before powering down again,that when you lock the device you have the option to use all the hardware keys and the minimal system impact(cpu and memory)

really like the capacitive unlock function (move up on right part of the capacitive area), never had any problems with that btw!!!

But i have one small problem:

I use Aebutton plus to map several functions to alle the buttons on my phone.

Somehow the volumebuttons mappings do not work anymore(one time pressing of volume up or down still functions as volume up or down but pushing twice or triple or holding doesn't work anymore).

It happens at random, so not after a specific command, once after a lot of usage(so using different programs) or after not using it, some time after a reboot!!

I don't know if other people also have this problem?

I hope you can help me solving this problem!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not lock the buttons, when unlocked. . But it appeared that hooking the TouchPanel can give glitches in scrolling.. Together with me, Cobaltikus did the hard work :), we found out that the problem disappeared when we handled the touchpanel hooking different.

Maybe this also has a side effect of the volumebuttons? Or is it just a malfunctioning of the hardware :confused:

I will post version 2.5 soon, so you can check if it is solved with this different hooking mechanism.
[Touch Diamond, MDA Compact IV Themes and Apps] varden:
It's Aebutton issue. You have to check or uncheck something with the volume in the settings (sorry but I don't remember exactly)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Microsoft Deployment Problem of different localization resources

I came across a .NET Visual Studio Deployment bug. I did put all different translations inside the CAB installer. Now the translations are not picked up correctly, due to a Microsoft bug :mad:

This is a known issue, according this post.

If I copy the needed translation by hand, it does work. The CabWizard just takes the same resource file for all languages :eek:

Hmmm, maybe I need to make a separate installer, which only installs the actual needed translation. Or I rename the resource files, to make the names unique and I move them into the right place. Damn, I hate those workarounds. Actually, I even can remove the not needed resource files, although they are now really small.

Hmmm, I go think about it. Someone else a good idea for installing the translation resources? Because I will not be the first one encountering this problem. I do want it to be easy for a user to install their language, without hassling around. A separate installer is often too much for a user :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] MadMax1978:
It's no malfunctioning of the hardware, because this problem started after installing touchlockpro...

But i will see what happens with the 2.5 version...

Thanx!!!!
[Touch Diamond, MDA Compact IV Themes and Apps] MadMax1978:
I checked the aebutton plus settings and found the checked option:restore volume slider -> during phone calls was checked,

so i unchecked and will see if this helps, i will report back after some days of testing...

I don't know if i accidently activated this option...

Thanx!!
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Stylus Out Detection

ZuinigeRijder, Or anyone else who may know,

Do you know if there is any way to check the status of the stylus (in or out)

without

checking the registry?

It seems the registry is only updated when the status changes while the device is running. This is why we have the issue of the phone not locking after a soft reset. If you soft reset with your stylus, then your stylus is out and the flag is set to say it is out and the lock is disabled. Then the device turns off and on again. You replace the stylus THEN the OS loads. And even though the stylus is in, the registry still says the stylus is out, thus disabling the lock.

Removing the stylus and putting it back in fixes the symptom. But if there is another way to check the stylus status it may good to use that other method at least when TouchLockPro checks the status the first time. Then depending on how efficient that other method may be, you could continue to use it or switch back to checking the registry.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, that explains the symptom some people have. I am not aware of a direct HTC API for the Stylus sensor. Maybe HTCUtil.dll has a function in it?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
1000 posts: [APP][Updated 29-04-2009] TouchLockPro version 2.5

I reached my post 1000!

Here some statistics:

Join Date: 13th June 2008

Total Posts: 1000

Posts Per Day: 3.12

You can read here, how it started..

As a special gift, you can find a new version of TouchLockPro: version 2.5, with again a lot of tiny improvements.
[Touch Diamond, MDA Compact IV Themes and Apps] varvocel:
Thanks ZuinigeRijder,

Great application and interesting blog.

Best wishes :)
[Touch Diamond, MDA Compact IV Themes and Apps] DomSim:
holy huge update! downloading now :)
[Touch Diamond, MDA Compact IV Themes and Apps] bugeyes:
congrats on your 1000th post!

small problem with the light sensor unlock though, as per your fix, the settings are now saved upon exit, but even directly under a light the screen wont un lock with it set to unlock at level 3.

sorry to be the first to find fault! :o
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Maybe it is not a fault. There can be several reasons. There is Bluetooth support added, so it will no longer unlock on light sensor when this is enabled and the bluetooth radio is on. Also it will only unlock by light sensor when the phone is locked at power on. Also the light sensor is not sensitive, so on a lamp it often does not give a good readout. What value gives the light sensor in the TouchLockAction setting screen?
[Touch Diamond, MDA Compact IV Themes and Apps] peterbonge:
First: Here I don't have a problem with unlocking with light level 3.

Second: The scrolling problem with Spb Mobile Shell seems to be solved.

Now some problems:

- Every time I open the settings and go to BattClock the app resets my settings.

- Often I get the battery popup instead of the action screen when clicking on the clock.

- The texts on the action screen should be centered.

- One of the German texts is too long. Maybe it would be better if the texts would be shown double spaced.

Maybe it would also be a good idea to use simple text files as language files. So we could adjust and test the translation by ourselves.

Otherwise please change the following at the German translation:

"Zurücksetzen" -> "Neustart"

- I'm not sure, but it seems that the app now uses more CPU power, even if unlocked and idling. I think before it was up to 0.1% and now it is up to 0.5%. That doesn't sound much, but over the time it will suck the battery.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
I use the strip to show that it's lock. Now when I receive a call, the strip goes from red to grey, and stays grey (unlock). The problem is gone once lock and unlock.

Also, sometime the white leds stays on!! I have to turn it back on, and hope they turns off by them self! Any idea on this one?

Thanks.... I really need to send you some money :D
[Touch Diamond, MDA Compact IV Themes and Apps] HerM3s:
rom miri 6.5 v.81 detect stylus but can't lock or unlock when in/out

(TouchLockPro 2.5)
[Touch Diamond, MDA Compact IV Themes and Apps] Slide:
Hi ZuinigeRijder,

thanks for the new Version!

I have the same problem with BattClock settings.

And "SuspendTimeOutPowerOn" does not work anymore.

Greeting

Slide
[Touch Diamond, MDA Compact IV Themes and Apps] procop:
Nice job. Will see this one
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hello !

Nice to see a new version with so much new features :)

Saddly, "TouchLockAction.exe" unlock doesnt work on incoming call anymore.

I'll check if bluetooth work as expected, that's my favorite new feature :)

BR
[Touch Diamond, MDA Compact IV Themes and Apps] Aizek!:
Please in next version correct translations

Reset: Перезагрузить

Off: Выключить

sorry, various translating depending on a situation :)

g-sensor work correctly, big thanks

in parameter "Other->SuspendTimeOutPowerOn" edit box very small and does not contain all figures...