yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for pointing me to the right direction. Your analysis really helped me to find the problem. As usual, I was thinking in the wrong direction :rolleyes: It was not wrong in the SIP API I called, but I just filled in only the first match of a name (if else if else if), while enumerating the SIP's :mad:

Hope this attached new test version 2.4.1 solves the problem now really.

Sorry for the inconvenience :cool:
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
yeap seems to work :)
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
Hmmm.... Don't know :) It would be nice if it was keeping it unlock. But, usually this situation does not happen often.

The problem I also have is the sensitivity of the capacitive sensor, so this is why I get frustrated when I end a call waiting call. But, if it happens when it's not dark, then the light sensor does the job.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.4.1 bug fix release

Thanks for testing. I uploaded this version as official bug fix 2.4.1.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked into the difference between 2.3.4 and the later versions for the GSensor. There was a bug, that an unknown orientation change was handled as LANDSCAPEorREVERSE_LANDSCAPE.

I know only the following GSensor orientation changes of the HTC GSensor:

LANDSCAPE=0, REVERSE_LANDSCAPE=1, PORTRAIT=2, UPSIDE_DOWN=3, FACE_DOWN=4, FACE_UP=5

But there is another value, 6, which I do not know where it belongs too. Anyone knowing what this gesture means?

In 2.3.4. This was treated as LANDSCAPEorREVERSE_LANDSCAPE within TouchLockPro. So now it behaves according to my documentation. I still have to find out what the unknown value 6 means. I am planning to make a GSensor Test mode, so you can see the values which belong with which GSensor move. I even think on recording gestures.

About the swipes and external commands. I would expect you use double quotes around commands, when there are spaces in it, e.g. "\program files\TCPMP\TCPMP.exe". If a command is in the Windows directory you can leave out the path, e.g. camera.exe.

But, starting/loading the programs take time, so I expect that is the case. The builtin commands do not need an external program to be started, so they are fast. Also make sure, with the capacitive swipes, you do not swipe the middle button area. And the lenght of the swipe must also large enough, to be detected as swipe. Also here I want to make a test mode Settings screen.

But be patient, I do this in my spare time :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The Stylus is then the fastest way to unlock, when the other unlocking does not work good enough. I will make a test settings screen for the capacitive sensor, so you can practice ;) But if the TF3D bug of HTC is active, I cannot do much about that (still searching for a solution).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I uploaded a bugfix version 2.4.1 for the SIP.

The intention was indeed to have maximized settings screens and the taskbar should not go on top of that. So I am confused that is not working for the index screen. Maybe I switch back to having still the taskbar visible in a next version, but then I will probably remove the Setting screen names, to have more space. Because I do not want scroll bars when operating in landscape.
[Touch Diamond, MDA Compact IV Themes and Apps] hefman:
SIP changer seems to be working now. Thanks!

I use Wisbar Advance 3 (WA3), which probably thinks it needs to show the taskbar on that screen. It usually doesn't do that in other full-screen programs though.

It's not a big deal. It's just a minor annoyance. The index screen is the only one that's sort of a problem, since I can't see the text on the top 2 buttons. I can still press those buttons though (the bottom part is visible). I wouldn't worry about it unless you get more complaints.
[Touch Diamond, MDA Compact IV Themes and Apps] ecard:
From the beginning, I disable the unlock with the stylus, because it was not always detecting the stylus in.

The test setting screen, that is a great idea :)

I do have the TF3D bug workaround tick on, should I turn this off?

Thanks, Eric
[Touch Diamond, MDA Compact IV Themes and Apps] peterbonge:
Yes, it really seems to work now. Thanks!
[Touch Diamond, MDA Compact IV Themes and Apps] sikes:
Stylus Sensor Problem

I cannot lock my HTC Touch Pro, if the stylus is not in, although I disabled the "StylusOutDisablesLockMode". :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
When the Stylus is out, it will never lock, or you must disable the stylus sensor.

The settings StylusOutDisablesLockMode = 1 is for disable lock, so when putting the stylus back in, it will not lock.
[Touch Diamond, MDA Compact IV Themes and Apps] NLS:
...which is perfectly logical, since you have your pen out to use it on your screen (or some people to scratch their ear - but TLP is not for them)...
[Touch Diamond, MDA Compact IV Themes and Apps] texasez:
I have been using version 2.2 and was having trouble with the touch pro locking all the time. It worked sometimes but not all. I upgraded to 2.4 and it would not work at all and when I powered on the phone the screen would rotate between the tab to the right of the one that was open when you shut the phone off and then to the correct tab. Two screens would open before the correct screen open. I then tried 2.4.1 and it works the same way.

All i want the program to do is to lock when the backlight goes off, lock on incoming call, and then unlock when i press one of the buttons.

What do i need to do?

Larry
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I assume here you start with the TouchLockPro defaults (go to "About" settings screen and press "Reset settings to defaults").

Because you do not want to TF3D workaround (the tab right-left), you need to disable this one:

NavSensor settings screen: TF3DWorkaround = 0.

You only want the phone to lock when the backlight goes off or on incoming call:

Other Settings screen: AutoLockOnPowerOn = 0

Other Settings screen: SuspendOnBacklightOff = 1 (note this will not lock the phone, but you can put the phone on with power on)

Other Settings screen: SuspendTimeOutPowerOn = 0 (but you can consider to keep this setting, because it can be used in combination with backlight off)

Telephone API screen: CommandCallIncoming = !LOCKSCREEN

For unlocking, you can configure a capacitive touch (assuming you do not have a Touch HD) to the middle center button:

Nav Sensor screen: CapacitiveTouchesSequence = 2 (you can consider 2 or 3 capacitive touches, if you find unlocking too easy). But because you disabled the TF3D, this may not always work and then you must use the other unlocking possibilities (e.g automatically by light sensor or taking Stylus out).

Let me know if this is working for you ;)
[Touch Diamond, MDA Compact IV Themes and Apps] texasez:
Still not working.

I used the default settings and then unchecked the G sensor and light settings. I set the other settings as you suggested and still it will not lock.

When I uncheck the light sensor settings, the unlock on ligh sensor allways comes back checked after reset.

On the API screen, should the registry setting be "!LOCKSCREEN"?

Larry
[Touch Diamond, MDA Compact IV Themes and Apps] Slide:
Hi ZuinigeRijder,

can you make please an option to unlock by press the middle round button?

Greeting

Slide
[Touch Diamond, MDA Compact IV Themes and Apps] TheAI:
Thank you very much!

TheAI

Ps. Have somebody reported the bug that after upgrading touchlockpro the ver. number is still the previous ver. ?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, but I discovered this myself too. I forgot to update the version number to 2.4.1 in one source file :eek: I will makle sure the next version shows it correctly again.
[Touch Diamond, MDA Compact IV Themes and Apps] pzlmg:
ZuinigeRijder，thanks for your great work!!

There's only one thing, I'm using TLP on Touch Pro, when I used "At0mAng 03-20-2009 Touch Pro Manila" ROM and some other ROMs, I can use hardware key other than Power Button to wake up screen. But when I flashed to "At0mAng 03-20-2009 Rhodium Manila"(TP2 Manila), I can't do that. Pressing the hardware button, only light up the button's back light. How should I do?

(Sorry for my English :))
[Touch Diamond, MDA Compact IV Themes and Apps] VG.Shteinfeld:
Hi ZuinigeRijder,

I prefer your program !

But could you pls advice me about the settings for light sensor or may be other my mistake (mobile Diamond).

The main problem for me is to don’t push any button (accidental) during incomming call when mobile is in the cover.

In my opinion I my use for this task light sensor with time delay. But if I change UnlockOnLightMinimumValue for example for 10 – no changes. When I check this parameter again I see 1 (default value). May ó I have to change any other parameter?

Could you pls indicate me correct parameters for this task.

Thank you in advance.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The UnlockOnlightMinimalValue is for the sensitivity of the light sensor. Best is to keep that on 1, because the sensor is not so sensitive.

The default settings are already, such that on power on due to any event the phone will lock. Also the light sensor is already configured, to auto unlock when there is enough light. So nothing to do for that, just the default settings. You can reset to the default settings via TouchLockAction -> Settings -> About screen -> Reset settings to defaults.

Just power off your phone via the power button and it will lock on power on.

If you want to unlock earlier by the light sensor, than the default 1.5 seconds (UnlockOnLightSensorTime = 1500), you can lower this value below 1 second, e.g. 500. Then it will unlock within 1 second when sensing light (not faster).

If there is not enough light, you need to unlock using the other means (e.g. Stylus out).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There is a Windows Mobile setting to enable all hardware keys to wake up the phone:

Start -> Settings -> System -> Key lock -> Do not lock keys (or something like that, I have a Dutch Windows Mobile).

But of course, then your phone will wake up very easy. But you are apparently already familiar with that.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Do you have a Touch Diamond or a Touch Pro? Then you can couple a capacitive touch to the middle button to unlock:

NavSensor settings screen: CapacitiveTouchesSequence = 2

If you have a Touch HD, this is not possible (No Nav Sensor). Because TLP is not the foreground window, I cannot catch keys. DredSensor has a mechanism, by subclassing the foreground window, but because I had problems with this approach earlier, I hesitate to go into that route again.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, the Incoming command must be !LOCKSCREEN without double quotes.

There is also a setting, LockWhenIncoming, which does the same. This is faster too, so I advise to check this setting in the TAPI Settings screen, and make the Incoming command empty.

That the unlockonlightsensor always comes back, also when you have unchecked "Use Light Sensor" is confusing. But the light sensor will not be used anymore when the first setting is unchecked.

I checked it worked with LockWhenIncoming checked.
[Touch Diamond, MDA Compact IV Themes and Apps] VG.Shteinfeld:
Thank's a lot for the information, but with the same settings mobile mostly allready unlock BEFORE removing it from the cover and timely any button is pushed and call is started. In this case could you please recommend me any settings for unlocking mobile during incomming call ONLY after I remove it from the cover. Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, that is strange, I expect another problem, e.g. a Stylus Sensor hardware problem.

Can you enable debug logging (logdebug=1 and logdebugdetailed=1) in the Other Settings screen and reproduce your problem. Thereafter post the debug log file in the root of your phone memory, \TouchLockPro.log.txt as zipped attachment. Maybe that gives me a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
Hello !

Just installed the latest version on my HTC HD and I'm facing a small issue :

The setup screens are cropped at the top.

I've also not always the same behaviour during a phone call, sometimes the screen goes black, sometimes not, not reproductible....

Did you consider my request to avoid unlocking and unsuspend when receiving a call over blutooth ?

Appart these small details it's a really great app, nice work ;-)

Best regards
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you post screenshots from the cropped setup screens. Possibly it has to do with other screen resolution?

There is a setting ScreenOffWhenConnected in the TAPI screen. What is the behaviour you want? There is also a mechanism of HTC, that screen goes off, when the light sensor does no longer senses light (phone at ear). There are tweaks to enable/disable that.

I will add a convenience option in a next version, to enable Bluetooth mode, so you can quickly switch from normal locking use to bluetooth mode and visa versa.
[Touch Diamond, MDA Compact IV Themes and Apps] texasez:
My setup screens are also cropped at the top by the power and clock icon line.

I have gone back to a version I used the end of January and it works fine. I cannot get 2.4.1 to lock the screen. I will try again when you issue updates again.

I am using touch pro.

larry
[Touch Diamond, MDA Compact IV Themes and Apps] Alkerion:
YES, once my PC is back to normal I'll post one.

I want the screen not to turn off while I'm calling my mailbox as I've to always use the keyboard, for other calls it's nice to turn it off.

I don't understand... :-(

What I want is the phone not to unlock and unsuspend when I receive a call when connected in blutooth (in my car), I don't want to have to manually change anything, I would like the prog to identify when I'm connected to a BT earphone (the BT icon change when connected to a earphone).

BR
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can help finding the problem, by posting a debug log file (logdebug=1 and logdebugdetailed=1) and reproduce the problem. Post the debug log file on the root of the phone memory \TouchLockPro.log.txt as zipped attachment.

In that way I can try to solve the problem, otherwise there is a great chance nothing will be changed in a new version. Hope you help to make TouchLockPro better.

Thanks for the effort.
[Touch Diamond, MDA Compact IV Themes and Apps] Cetin:
Hi,

even with new version I cannot use touchlock on my Touch Hd, because I have issue unlock by lightsensor. I want to use it but even if I cover the sensor with my finger it will unlock immidiately by himself.

Unchecking lightsensor didn't effect, unchecked box will check again again by himself. Adjusting lightsensor by using some higher values than 1 didn't effect too. These settings cannot be stored like the most settings in touchlock.

It's very sad not be able to use this nice tool.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think there is somewhere else a problem.

Can you enable debug logging (Other Settings screen: logdebug=1 and logdebugdetailed=1), and reproduce the scenario. Also change the light minimum value, so I can check that too. Thereafter post the debug log files on the root of your phone memory, \TouchLockAction.log.txt and \TouchLockPro.log.txt as zipped attachment.

Maybe that gives me a clue?
[Touch Diamond, MDA Compact IV Themes and Apps] astromark:
I like this, mostly for the light sensor functionality, but while it works fine in daylight I'm discovering that this is sadly not sensitive enough to use at night. I'm using it on a Touch HD.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In those situations, you must use the GSensor or Stylus for unlocking.

You can consider to make the unlocking via the GSensor easier, e.g. change from Portrait-UpsideDown-Portrait into UpsideDown-Portrait, by changing 343 into 43.
[Touch Diamond, MDA Compact IV Themes and Apps] astromark:
Thanks ZuinigeRijder. Since all I want to do is prevent pressing the screen should it wake up in my pocket, I've enabled light sensor (so removing it from my pocket wakes it up) and as you suggest GSensor.

I've simply set the Gsensor to use sequence 99 and !unlock. That way pretty much any movement once it's out of the pocket will wake it up. All the turning it over or rotating it 180 degrees was too much - if I'm down the pub I'll drop it trying to do that!

I have had to set unlockonlightsensortime to 500 because 1500 was too long, but I have to do it in the registry otherwise it forgets the settings I've done through TouchLockAction.

Does the power button have to be locked? That's one thing that on the Touch HD I am unlikely to press by mistake - if that could be used to unlock (once the device is on but locked) that would be a good option too.

Great app anyway by the way. I love the way it cleverly uses the sensors to make life easier.
[Touch Diamond, MDA Compact IV Themes and Apps] texasez:
I am enclosing a log file. Currently version 2.4.1 works part of the time but will not always lock the screen on backlight off. the screen has locked on me once and I had to softrest to get it working again. I have unlock set to one touch (2) but it still requires two touchs on center button. I do not use light sensor or movement to unlock. Any help would be appreciate.

Larry
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you also post TouchLockPro.log.txt, because that contains the interesting information.

Thanks for the response!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I found the bug in TouchLockAction. The light sensor settings screen was not calling AutoSave :mad: Will fix that in the next version.

Unfortunately, the HTC API I use does not let me keep the power button the only button not locked.
[Touch Diamond, MDA Compact IV Themes and Apps] texasez:
I cannot currently lock the screen.

Larry
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
battery consumption

Hi, I have a quick question - using the G-sensor function for Unlocking and for launching different programs, would excessively drain the battery?

I noticed that today it went from 100% to 15% in 6 hours, with 3 short phone conversations, and a couple of soft-resets.

Yesterday I installed WkTask, but I know that it has a very small CPU usage (120-125kb), and also I programmed a few applications to be launched using the Capacitive Areas and the G-Sensor options of Touch Lock Pro.

... or, maybe is the spring coming... :)

thanks
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, iTouchLockPro does not drain battery at all, you should not notice difference in battery consumption. Also when the screen is off, all the sensors are not used anymore, so then NO battery consumption. The battery consumption is mainly when the screen is on, by the LCD display.

I have all sensor on always, and do not experience battery drain (and also others do not report that). Actually, I think TouchLockPro is *THE* locking application which does not consume extra battery, in contrast to e.g. S2U2.

Soft-resetting is known to use a lot of battery. Also the battery indicator is not a good indication. What is known, is that when you are in a bad reception area, the radio is constantly seeking for reception, which drains battery a lot.

When I keep on the phone at night, max 10% of the battery is drained in 8 hours (due to radio), others reported 5%.

Also make sure, you charge your battery for 100% (and keep charging half an hour more), to have accurate measurements.

Hope this gives you confidence and it was an incident ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I see the screen is locked and not the hardware buttons (LockTouchPanelOnly) several times. And it is unlocked by a capacitive touch by the middle button.

But you report that the screen is NOT locked :confused:

Does the touchpanel never lock?

Note that when you use TouchPanelOnly, the small upper right part is not locked (where the task button is located), that is a feature of the locking method of Windows Mobile. Other parts should be locked. Is that the case?

Will have a detailed look in the logging later...in the mean time it would help if you can clarify some of the questions.
[Touch Diamond, MDA Compact IV Themes and Apps] jodeltje:
thank you VVEEERRRRRRRRRRRRRRYYY much!!!!

don't have to use s2u anymore :)...

1.3 is even better, was questioning my tapping skills (turns out it wasn't activated quick enough)... all is fine now.

just one minor thing: when my headphones are connected and I press play/pause the lock turns off, so it would be great if you could fix that the lock only turns off when I triple tap... because now i start pressing stuff in my pocket after I paused my music...

anyway thanks A LOT!:D
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
Nice idea, ill be trying that right now!!

I did some reading a week or 2 ago, which pointed to the fact that the light sensor wasn't very efficient at detecting different levels of light and that it only seemed to react/register a change every 20% increase/decrease in luminosity.

so effectively reading light at 0%(dark), 20%,40%,60%,80% and 100%

but another thing that was pointed out was that even when shining a light directly into the face of the phone the device never registered 100%

hope that helps some how

Also is there a way to turn off the light sensor? surely polling the light sensor continually will use alot of battery?! can it be deactivated like the capacitative touch?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I know that Bluetooth users can still pick up the phone. But that it unlocks is new to me. Especially, because the unlocking mechanism only listens to:

- stylus

- capacitive

- light sensor

- USB/AC power

Does the BattClock still show that it is locked (white background), but the hardware/touchpanel is unlocked?

Did you lock both hardware keys and touchpanel?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am not interested too much in the level, the default value is 1, so that if it detects any light, it will see it as light sensing.....

And because the sensitivity of the light sensor is very low, it does not see light when there is plenty :cool:

The range you can get back is 0 to 255, when it is above 0 then there is light. And that is the only thing I was interested in :)

And yes, of course you can disable the light sensor, as described in post #3.

But I only poll once per second, only when the phone is locked and the screen is not off.......so no real battery/CPU usage!!!

Did you also think of putting black tape over the light sensor, for temporarily disabling it :D
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
The light unlock is pretty cool!

i locked my device and put it on my desk and 5 seconds later it unlocked!

just what the packet says!!

can i ask, once the light sensor has unlocked the device, does it stop polling until the device is locked or is it a continual polling of the sensor?

have you experienced any battery usage?
[Touch Diamond, MDA Compact IV Themes and Apps] jodeltje:
no it shows unlocked after about 10 seconds...

the phone awakes when I press play/pause and then it shows white/locked....wait a few seconds (without pressing anything) and it turns black/off.

and I don't lock hardware AND softkeys... just soft.

hope you can help me figure this out!:confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Do you have the phone in your pocket, so it does not sense light?

Because the new light sensor will auto-unlock when seeing light for about 5 seconds. Or was this problem already there with version 1.2?