yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] maardiweb:
Hi Zuinigerijder,

I have been using TLP for a month and I like it very much! Especially because of the low memory usage compared to S2U2.

There is only one issue I encountered and it's starting to annoy me:

Using G-Alarm, the phone wakes on time, unlocks and plays the alarm as expected. However, after snoozing the alarm the phone locks down (G-alarm function) but doesn't unlock at the next wake of the device, so I will need to unlock the device before I snooze or exit G-Alarm. In addition to that: After 20 seconds the devices turns off again because it's not unlocked, making the alarm stop without turning it off myself. When I wake up the device afterwards, the alarm continues playing.

Unfortunately, sometimes that makes me wake up too late :P

It might me a phone dependent problem, and I did not search through earlier posts either. But maybe you could provide some feedback about this problem? If the device unlocks properly at wakeup after snoozing, the problem would be solved I guess :)

Thnx in advance!

Sorry for my poor English btw..
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
I have the same problem with G-Alarm on my HD2. First wake up-Alarm all works fine (phone will be unlocked), but if i snooze the alarm and the alarm goes off again 5 minutes later, the phone is locked.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It is possible that G-Alarm only the first time sends the command to unlock TouchLockPro? Or something else?

Can you enable debug logging, reproduce the scenario about the second alarm not unlocking and 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] markoz1973:
Hi,

Seems this is the best locking application.

But, installed, battery indicator shows locked device - ... and nothing is locked. Why?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you try to do a soft-reset? And does it not lock thereafter too?

The default locking of keys is using a keyboard hook. If other programs use the same approach, then the keys may not be locked.

The screen is also locked with a hook. On my phone (Touch Diamond) I need to enter the pin before TouchLockPro is started/locking, otherwise it also will not lock correctly. So therefore there is a delay of 1 minute at boot before TouchLockPro is really started.

For the newer HTC devices there is also another locking approach, HTCLockAPI = 1, but then you loose some functionalty, e.g. like unlocking via keys, the power button is locked while locked. Dependent on you phone type you could try that too.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro Proximity test version

Hi,

I have a test version for people having a Proximity sensor.

Samsung and HTC are supported.

Because I do not have a phone with a proximity sensor, I hope that people can test. See attachment. Note that I could only test if it does not harm if not configured. And of course closely reviewing my own code.

Use Proximity (UseProximity = 0)

Default, the Proximity sensor will not be used. If your phone has a supported Proximity Sensor, you can overrule this registry key with "UseProximity = 1" When enabled, the phone will be unlocked if nothing is detected nearby.

Use Proximity Unlocked (UseProximityUnlocked = 0)

If you want the proximity sensor also to be used unlocked, you must check/enable this setting. Note that for the HTC Proximity sensor, the registry key HKLM\System\State\Phone\PSensorStatus will be reset to 0, so the Proximity sensor is disabled.

Use Proximity ScreenOff (UseProximityScreenOff = 0)

If you want the screen to go off when the proximity sensor detects something nearby, you must check/enable this setting. Note that other programs can also react on Proximity changes, so they can conflict.

Use Proximity Disable on Bluetooth (UseProximityDisableOnBluetooth = 0)

If you do not want the Proximity sensor to be used when Bluetooth is active, you must check/enable this setting. Note that for the HTC Proximity sensor, the registry key HKLM\System\State\Phone\PSensorStatus will be reset to 0, so the Proximity sensor is disabled.
[Touch Diamond, MDA Compact IV Themes and Apps] markoz1973:
Hi,

Thanks for your prompt response.

Great piece of software, great support!

Yes, I softrested my TD.

I am a new TD user as well as not a programmer - what is a "keyboard hook"?

--

Marcin
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

i just tested it, it does not make any difference which setting i choose - the proximity sensor is always active and the screen is lid up when touching area near the proximnity sensor

The value is shown -1 - can you use that info for something?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you enable debug logging and post the debug log file. Because there will be one or more bugs in my code :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Sure uploaded

thanks - really appreciate solving the proximity sensor thing

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you upload the log file TouchLockPro.log.txt, because that contains the interesting information. Note that when you disable debug logging, that file will be removed. So you should stop TouchlockPro before copying the log file and not disable debug logging before copying.

Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Sorry - here it is

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, a keyboard hook is a Windows Mobile way of trappin the key presses. However, Windows Mobile has the restriction there is only one active. So it is dependent of your programs running, if this is possible or not. Which homescreen do you use? TF3D?

I am not sure if you still have the problem. If yes, you can enable debug logging in the TouchLockAction Other settings screen, reproduce the scenario and post the log file \TouchLockPro.log.txt in the root of your phone as zipped attachment.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the log file. That gives me insight. You disabled the Proximity Sensor, so it will also not disable it at bluetooth on:

2010-02-12 16:04:21 222322486 UseProximity: 0

2010-02-12 16:04:21 222322486 UseProximityDisableOnBluetooth: 1

So the second setting will have no effect. You should set also: UseProximity = 1. So it will also unlock due to proximity sensor when no bluetooth is active. Currently there is not a setting to disable only the sensor when bluetooth off. I also do not know if that will work, because it is possible another program tries to start it again too.

I see however some logging of Proximity keys changed:

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneNotification()

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneStatus(false)

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneNotification()

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneStatus(false)

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneNotification()

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneStatus(false)

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneNotification()

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneStatus(false)

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneNotification()

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneStatus(false)

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneNotification()

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneStatus(false)

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneNotification()

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneStatus(false)

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneNotification()

2010-02-12 16:04:41 -1428461846 CProximity::HandleProximityPhoneStatus(false)

So this means indeed the sensor will not be disabled.

You need to set: UseProximity = 1

No one tried if the unlocking via Proximity Sensor is working :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

i just tried to set use PS = 1, it did not difference - sensor is still active and as always awakes the screen if hand moved nearby during call

uploaded log again

PS i can try unlocking via PS when TLP can controll the PS, it seems it cant now?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks Nolan, for the testing effort.

Hmmmm, the logging still says:

2010-02-12 16:04:21 222322486 UseProximity: 0

You are sure you checked that setting?

Maybe something wrong in my code?

Or am I looking into the wrong log file, because I believe your time zone would mean it is too early?
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
I think there are other places in registry that need to be handled besides the ones you have identified - i tried to manually set "0" in the registry where PS are placedin registry as you pointed out (as far as i can see) and it didnt make the PS disabled either. I wonder if other registry settings have to be changed too?

Eg a DLL has to be considered too ?

PS im sure i did the setting in TLP correct ;-)

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] La_Globule:
Tapi G-Sensor problem on Diamond 2

Hi,

And thank you for this wonderful piece of software.

I have a big problem with my Diamond 2 with the version 2.11.

I've activated the InCallTweak option and when I place a call, the screen goes off as soon as the connection is established in any position of the phone (face up, face down, ...).

If I want to put back on the screen, I've to push the power button.

The phone is unlocked and when I tap on the screen (to display the keyboard for instance), the screen goes off.

Then I power on the phone again and the keyboard is displayed.

And so on...

It's very annoying when you have to dial a number or a password for example.

It's not a problem of G-sensor because on this phone, the G-sensor lock and unlock functions work perfectly.

Do you have an idea to solve this problem ?

Thank you.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I going to test myself. Although I do not have a Proximity Sensor I go to simulate it with the Stylus Sensor (Nearby yes or no) and Capacitive Sensor (enabling/disabling Proximity sensor) ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Too bad. It looks like the GSensor is not working anymore with the screen off :confused:

Can you enable debug logging, reproduce the problem with the InCallTweak and post the debug log file \TouchLockPro.log.txt as zipped attachment. See if that gives a clue :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] La_Globule:
Thank you for your reply.

Here is the log file.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Looks indeed the GSENSOR is no longer responding:

2010-02-13 19:25:20 -1359208410 ReverseLandscape XYZ -54,41,-41 AngleXY 42,31

2010-02-13 19:25:20 -1359208410 SetOrientation: ReverseLandscape

..

2010-02-13 19:25:23 1275412890 SetCallStatus(CALL_CONNECTED): 0

2010-02-13 19:25:23 -1931889174 =====InCallTweak======IDLE

..

2010-02-13 19:25:35 1275412890 =========================POWER_STATE_ON============================

2010-02-13 19:25:35 1275412890 IsConnectedCall(true)

2010-02-13 19:25:35 1275412890 SetBackLightOff(false)

2010-02-13 19:25:35 1275412890 =====InCallTweak======IDLE

I do not see any GSensor orientation anymore, so it looks the GSENSOR is not responding anymore :mad:

My assumption is that the GSENSOR is deactivated with the screen off. You did not tweak the GSENSOR to be off with Screen off somehow? Because normally it should also with screen off (so not in a deep sleep), keep operating.

Other people having a Diamond 2 having the same problem :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] La_Globule:
About the G-Sensor on the phone, the only settings are Auto-rotate and Calibration.

I've tried another software named "Touch InCall Screen Tweak" which does exactly the same as the option InCallTweak and it works.

May be this prog switchs off the light without putting the device in sleep mode.

What do you thing of that ?
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Here is the log-file while g-alarm is unlocking my device.

The first time it is unlocked by g-alarm. Then i snoozed the alarm. Five minutes later at the next alarm the device was locked and only unlocked by the light-sensor.

First alarm 20:26 or 20:27

Second Alarm was about 5 minutes later
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I see the first wakeup and the unlocking by G-Alarm:

2010-02-13 20:26:45 -1251715854 =========================POWER_STATE_ON============================

..

2010-02-13 20:26:46 -1251715854 CActions::HandleActionsNotification()

2010-02-13 20:26:46 -1251715854 CActions::HandleActionsStatus()

2010-02-13 20:26:46 -1251715854 GetActionStatusString(): Command

2010-02-13 20:26:46 -1251715854 ==value====: !UNLOCK

5 minutes later, there is again a wakeup, but no unlocking command by G-Alarm.

2010-02-13 20:32:05 -1251715854 =========================POWER_STATE_ON============================

..

2010-02-13 20:32:07 -1148471178 ========================UNLOCK BY LIGHT SENSOR=============================

So my theory is that G-Alarm sends the unlock command for TouchLockPro only the first time and does this no longer when you did a snooze. Maybe you can ask the author of G-Alarm if this is indeed the case. G-Alarm should also send the unlock command the second time :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Because it is working on my phone (Touch Diamond) I think it is more related to the power settings specific for your phone type. I do not set the device in sleep mode, but IDLE mode.
[Touch Diamond, MDA Compact IV Themes and Apps] darfri:
Update bugfixes

Has touchlockpro overcome focus losing issues last months? Like garminxt manages to become the topmost window so touchlockpro "lock" becomes useless
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
what are you trying to say here ?

Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro does not use a foreground window to unlock. You only need the sensors for unlocking (like light sensor) or a key sequence. Did TouchLockPro not work on your phone a few months ago?
[Touch Diamond, MDA Compact IV Themes and Apps] La_Globule:
I don't want to install the other product I mentionned in my previous post.

So what can we do to solve the problem?

Thanks for your help.
[Touch Diamond, MDA Compact IV Themes and Apps] maardiweb:
What is the difference between light sensor unlocking and proximity sensor unlocking? I'm using the omnia II and I think those 2 are the same sensors?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No, that are 2 different sensors with different API's.

I just uploaded TouchLockPro 2.12.1 supporting the proximity sensor. So you can try.....:cool:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I will see how the power requirements settings are for my diamond. Have to search where those registry keys are defined.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.12.1 with Proximity sensor support

Version 2.12.1 (14-2-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor

* Add support for proximity sensor

* Proximity sensor Unlock when no object is nearby for approximate a second.

* Proximity sensor option to do ScreenOff when detecting an object nearby for approximate one second

* Proximity sensor option to disable proximity sensor when not locked

* Proximity sensor option to disable proximity sensor when bluetooth is active

Note that I could only test myself by simulating the Proximity Sensor via Stylus Sensor and Capacitive NavSensor. Please report if it is working!
[Touch Diamond, MDA Compact IV Themes and Apps] maardiweb:
GREAT!! This feature is much more reliable than the light sensor! I like it!! :)

Another question:

How to prevent the phone from locking in a call? Is that the telephone API option? Maybe you could disable that option for Samsung phones by default, because the phone turns of the screen automatically using the prox sensor and its annoying if you have to unlock the phone when you need to press a button etc. However, using the proximity sensor for unlocking, this problem has actually been solved already :)

great update, because now the G-alarm issue should have been solved too!
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Hi, installed new version on my HD2 - works fine! Great! This was the most missing function on HD2!

Only thing which is not so good: If device is powered on / wake up, and there is proximity, the device won´t go to sleep again, it only dim the screen. Is there any chance to build in a function to select, if device should straight go to sleep again if proximity is detectet and not only dim the screen and wait the whole time to go to sleep again?

Another issue: if device is locked and you accidently press power button - the screen goes on but shut off after a second when there is proximity. But now if you press the power button again, the screen goes on and stays on, while there is still proximity. Only if you remove proximity and then cover the proximity sensor again, then screen goes off again.
[Touch Diamond, MDA Compact IV Themes and Apps] maardiweb:
Tested: G-alarm issue solved!

@ bib_x

My phone falls asleep again after 30 seconds when not unlocked? Or is that too long?
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
You can set this time here "other" --> "SuspendTimeOutPowerOn".

This would be ok, if i want to look on my device when it´s locked, perhaps looking for the time. But if i leave my device in my pocket, it would be better when it wouldn´t wait 30 Seconds or the time i set - in this case it should go to sleep immediately without waiting.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi Zuinige

you indeed solverd the proximity thing - great work ;-) It seems to disable the PS as supposed, but if i have chosen TLP to lock on incoming call - the phone is not locked during incoming (could accidentially reject call during incoming if phone in pocket), it is first locked when connected. Further when i press the on button after or during a call the phone is unlocked again - i would have supposed that it remained locked untill i actively unlocked the phone - at least duting call.

I have uploaded log

PS i have changed setting on incoming to "lockscreen" - which was not in log - but same behaviour

Strange also if i lock the phone and send it to suspend (by turning face down - ie locking on g sensor as stated in log) thw phone is unlocked when pressing on butten again even though use light sensor is disabled - how come ?

can you enlighten me (ie have i chosen wriong settings ?)/fix this ?

thanks

Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear it is working on Samsung Omnia II :)

There is already a (default) setting it will not lock when a call is connected:

UnlockWhenConnected (UnlockWhenConnected = 1)

Default, it will unlock when connected (and 5 seconds therafter), so when the screen goes off, you can still end the call via the hardware keys or power on the phone and press the TouchPanel. If you do not want this behaviour, overrule this registry key with "UnlockWhenConnected = 0"
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Good to hear it is woking :D Especially because I could only do limited testing. Or someone should donate me a HD2 :rolleyes:

I do now a !SCREENOFF, maybe I should do !IDLE :confused:

But I do not know if the sensors keep working then.....

I can make a test version when appreciated?

Hmmm, the design is that it should also do this the second time. Can you enable debug logging, reproduce the scenario and post the debug log file \TouchLockPro.log.txt as zipped attachment? Maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked into the logging:

2010-02-14 17:07:09 -883634298 NotificationCallStatusIncoming()

2010-02-14 17:07:09 219761094 ClockWndProc(WM_TIMER): 20

2010-02-14 17:07:09 219761094 NOTIFY_CALLSTATUS_INCOMING

..

2010-02-14 17:07:09 219761094 ==================================Lock=============================(true)

2010-02-14 17:07:09 219761094 SetLocked(true)

2010-02-14 17:07:09 219761094 ==========================DisableInput()==============================

..

2010-02-14 17:07:09 219761094 Execute(): !lock

2010-02-14 17:07:09 219761094 LockSuspendRequest()

..

2010-02-14 17:07:11 -883634298 ======================== Change from screen OFF to screen ON ==============

2010-02-14 17:07:11 -883634298 SetScreenOn(true)

2010-02-14 17:07:11 -883634298 NotificationScreenOn()

2010-02-14 17:07:12 219761094 ClockWndProc(WM_TIMER): 11

2010-02-14 17:07:12 219761094 NOTIFY_SCREEN_ON

2010-02-14 17:07:12 219761094 ComputeDisableInput(true)

2010-02-14 17:07:12 219761094 ==========================DisableInput()==============================

..

2010-02-14 17:07:12 219761094 GetProximityIsNear: 0

2010-02-14 17:07:12 219761094 ========================UNLOCK BY PROXIMITY SENSOR=============================

So it locks as configured and unlocks by the proximity sensor, because there is no object near. Or is this not what you wanted?
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
This would be great. !IDLE would be better than !SCREENOFF.

Here is my log-file.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

almost, i do not want it to unlock by proximitysensor, proximitysensor shouldnt do anything i would much rather lige to control locking and unlocking via TLP alone. But i have chosen "disable proximity sensor when on bluetooth" so proximity sensor should not unlock either ?

I did some small adjustments to setttings and the combination of settings seems to be fine, but when ending a call the screen is lid up again although locked - the screen is set to suspend at end of call - but it still lights up at end of call, see attached log

best regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] maardiweb:
Hi zuinigerijder,

Still very confident with this new version!

2 requests:

- The camera button is (still) not locked when the device is locked. Is it possible to lock that button too?

- Is it possible to wake up the device with a hardware key without unlocking, and let the device fall asleep again after a defined time? I would like to be able to have a quick look at the screen to see the time or something else :)
[Touch Diamond, MDA Compact IV Themes and Apps] markoz1973:
I use TF3D.

After my last post I gave up.

Then, yesterday morning, I decided to give it one more try. To my suprise it started to work and it works so far without any doubt.

Weird.

Anyway - thanks for your support!
[Touch Diamond, MDA Compact IV Themes and Apps] darfri:
Sorry. That garmin xt is able to override the protection - it is still clickable and after closing it the next "window" is touchlockpros invisible window... so it doesn't seem to protect garmin xt.. for example. And maybe there are more. This was a reason for me to uninstall tlp... I was unable to rely on it.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Is there any setting to overrule the unlock-comand of g-alarm?

Maybe i´m out and my HD2 is in my pocket, so i don´t want to get my phone unlocked when an alarm comes up. I only want my phone to unlock when the proximity sensor is not covered, e.g. when my phone is on my bed table.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Maybe i found a little bug:

Without TLP my screen goes off incall while i move my phone to my ear. If i remove it from my ear, the screen goes on again.

Now with TLP the screen won´t go off anymore. Still stays on.

Is there a chance to get the former behavior back?