yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] sjanos:
TouchLock vs Xperia X1

Hi ZuinigeRijder,

Yes it has sensors, just the API not known. It has light and sliding keyboard only ;)

The main purpose to screenon is to eliminate one plus button (powerbutton) press after a call if I want to initiate another one.

My phone usually is in 2 places, in my pocket or in a car holder with power. (BT always on) This is the reason why I can live with it right know (since 2.8.2 released).

But nowadays it happened often that I had to make a lot of calls each after and in this case I have to press the power button to wake up the phone after unlock and call. One more thing, if I say no for an incoming call, but I would like to call back, it is easier if the screen stay on.

Thanks a lot for this fabulous utility!

Brgs,

/Janos
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the logging.

I see that both commands are executed:

2010-02-25 23:28:34 -1685950506 Execute(): !UNLOCK;!PROXIMITYDISABLE

2010-02-25 23:28:34 -1685950506 UnlockRequest()

2010-02-25 23:28:34 -1685950506 CProximity::Disable(true)

2010-02-25 23:28:34 -1685950506 SetProximityEnabled(false)

A few seconds later the power state goes to unattended:

2010-02-25 23:28:39 -1154474106 ========================POWER_STATE_UNATTENDED====================

resulting in a lock:

2010-02-25 23:28:39 -1685950506 ==================================Lock=============================(true)

And which enables the Proximity sensor again:

2010-02-25 23:28:39 -1685950506 SetProximityEnabled(true)

2010-02-25 23:28:39 -1685950506 SetProximity: -1

2010-02-25 23:28:39 -1685950506 SetPSensorStatus: 1

The last one is because you want to be able to unlock via Proximity.

The problem is, that the phone is locked already at power off and not at power on. Hmmm, looks like Proximity enable should only be done at power on, to avoid this situation.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
So you want the command !LOCKSCREEN to work. You said this did not work. Can you be more precise what is not working then? It does not lock? And is that working with debug logging on? Can you post a debug log file with the !LOCKSCREEN, so maybe that gives me a clue what goes wrong?
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
But my unlock command comes after the lock is gone.

1. --> power off => lock phone

2. --> power on => unlock phone and after that disable proximity

3. --> normal use - proximity should now be disabled, but it is enabled

I don´t understand what´s wrong here...
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
How did you conclude that? It is not corresponding to what I see in the logging. Or look I at the wrong part (I looked at the end of the log file) or did I oversee something?

Currently what TouchLockPro does:

1. --> power off => lock phone AND enable Proximity sensor

So the second part is the problem, I think, this can give side effects, like enabling the screen again by another application. I will see if I can fix that, to enable the proximity when power on......

Also I think you are not precise enough for scenario 2:

2a. --> power on + nothing near + no incoming call => unlock phone and after that disable proximity

2b. --> power on + nothing near + incoming call => unlock phone and TouchLockPro should not react on proximity changes (keep enabled for phone canvas)

2c. --> power on + near => suspend the phone
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
What i think is:

Phone is unlocked if proximity not covered --- after that disable proximity sensor

So why could this be like you explained or like it is in my log-file?

Here is another logfile. I did 3 times covering the proximity sensor while phone is on (in short time), maybe you can find this in the logfile.
[Touch Diamond, MDA Compact IV Themes and Apps] maesus:
TouchLockPro to triggle WM6.5 Lockscreen

Is there a way to configure TouchLockPro to lock via WM6.5 Lockscreen instead? ie whenever TouchLockPro locks, WM6.5 lockscreen popup. Or is there a command like !LOCKSCREENWM65 to bring out WM6.5 lockscreen?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think I found the bug.

The sensors are opened (when not already the case) when the phone is not locked. Part of opening the sensors is:

if ((pProximitySensor != NULL) && pS->GetUseProximity() && pS->GetProximityAccept()) {
pProximitySensor->Enable();
}

So the proximity sensor is opened, when the phone is unlocked and ProximityAccept is active. So !PROXIMITYDISABLE is not enough :eek:

Probably it works as you want when you configure:

CmdLock: !PROXIMITYACCEPT

CmdProximityNotNear: !UNLOCK

CmdUnlockCall: !PROXIMITYIGNORE

CmdUnlockNoCall: !PROXIMITYIGNORE;!PROXIMITYDISABLE

Note that you did configure:

CmdProximityNotNear: !UNLOCK;!PROXIMITYDISABLE

In that way the Proximity sensor will also be disabled when there is an incoming call. Is there a special reason you did that? Because !UNLOCK will trigger one of the unlock commands......

Rationale for the above settings:

1) you only want to use the Proximity for unlocking (or other sensors)

-> CmdLock: !PROXIMITYACCEPT

2) When nothing is near you want it to be unlocked

-> CmdProximityNotNear: !UNLOCK

3) This will trigger one of the unlock commands (also when unlocked via another means)

3a) You do not want to interfere with Proximity sensor used by Phone canvas

-> CmdUnlockCall: !PROXIMITYIGNORE

3b) You do not want to use the Proximity sensor when unlocked and not in a call, so you can disable it

-> CmdUnlockNoCall: !PROXIMITYIGNORE;!PROXIMITYDISABLE;

Hope it is clear and it works now with those settings, because I could only determine by theory.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No unfortunately not (directly). However, the lock status is written in a registry key:

HKCU\Software\ZuinigeRijder\Status\IsLockedStatus

So you can have an application monitoring that key, e.g. mortscript, and couple action on that to activate WM6.5 lockscreen.

I do not know how to activate WM6.5 Lockscreen? Do you know an API or a way to trigger that?
[Touch Diamond, MDA Compact IV Themes and Apps] sjanos:
Hi,

Here are 2 logfiles, with 2.9 and 2.12.3 both with lockscreen and locksuspend settings.

2.9 behaviour:

- lockscreen doesn't work

- locksuspend with screenon works in debug always, but if no debug at first works but after the screenon never work

2.12.3 behaviour:

- lockscreen doesn't work

- locksuspend with screenon works in debug after 5 sec, but never if no debug

lockscreen from action menu always working

hope it helps to figure out something

Brgs,

/Janos
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Still not working. First time after softreset it worked, but after first lock, there is again screen off when using phone and proximity covered.
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
Russian translation v. 2.12.3
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, first looking why !LOCKSCREEN does not work.

version 2.12.3:

2010-02-27 18:35:48 226600934 ==============================PBT_RESUME===============================

2010-02-27 18:35:48 226600934 PBT_POWERINFOCHANGE

2010-02-27 18:35:48 226600934 SetBatteryLifePercentage(): 255

2010-02-27 18:35:48 226600934 SetBatteryLifePercentage: do not set battery percentage above 100

2010-02-27 18:35:48 226600934 PBT_POWERINFOCHANGE

2010-02-27 18:35:48 226600934 SetBatteryLifePercentage(): 79

2010-02-27 18:35:48 -310290726 LINE_DEVSPECIFIC=(107, 20, 0)

2010-02-27 18:35:48 -310290726 CTAPIDevice::lineCallback()

2010-02-27 18:35:48 -310290726 LINE_DEVSPECIFIC=(107, 20, 0)

2010-02-27 18:35:48 -310290726 CTAPIDevice::lineCallback()

2010-02-27 18:35:48 -310290726 LINE_DEVSPECIFIC=(104, 5, 0)

2010-02-27 18:35:48 -310290726 CTAPIDevice::lineCallback()

2010-02-27 18:35:48 -310290726 LINE_DEVSPECIFIC=(107, 20, 0)

2010-02-27 18:35:48 -310290726 CTAPIDevice::lineCallback()

2010-02-27 18:35:48 -310290726 LINE_CALLSTATE=(4000, 800, 0)

2010-02-27 18:35:48 -310290726 Bearer mode: 1

2010-02-27 18:35:48 -310290726 Media mode: 4

2010-02-27 18:35:48 226600934 SetCallStatus(CALL_ENDED): 1

2010-02-27 18:35:48 226600934 NotificationCallStatusEnded()

2010-02-27 18:35:48 1295947818 ClockWndProc(WM_TIMER): 22

2010-02-27 18:35:48 1295947818 NOTIFY_CALLSTATUS_ENDED

2010-02-27 18:35:48 1295947818 IsConnectedCall(true)

2010-02-27 18:35:48 1295947818 Execute(): !SCREENON

2010-02-27 18:35:48 1295947818 Execute(): !LOCKSCREEN

2010-02-27 18:35:48 1295947818 LockScreenRequest()

2010-02-27 18:35:48 1295947818 ClockWndProc(WM_TIMER): 5

2010-02-27 18:35:48 1295947818 LOCK_SCREEN_REQUEST

2010-02-27 18:35:48 1295947818 LOCK_SCREEN_REQUEST: nothing to do

The last line does not lock the screen, because the screen is not on. Although just before a screen on is executed. But the screen on is set just after it (reacting later):

2010-02-27 18:35:48 226600934 =========================POWER_STATE_ON============================

Hmmm, I do not remember why I do not execute LOCKSCREEN it when the screen is off? Looks like I just remove that condition. That would solve your problem, I think. And the command should be delayed too, I think.

Probably you should configure !SCREENON;!LOCKSCREEN. I will see if I can change the execution of commands, so the delay will also be handled correctly. I have to look into this one, if I can fix this. I expect the other one is also related to the delayed screen on/power on, and with debug logging this is just enough to get that event take place :confused:

I see in my code also an potential problem though, multiple executeRequests will overwrite the previous one :eek: So I have to fix this one too.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Damned, I really thought I found the bug. Unfortunately I cannot test myself, so I need still your help. I hope you still want to help and do not give up. Can you post a debug log file with the last situation, so that maybe gives insight in the next bug :mad: The last log file with the multiple near/not near was perfect for investigation.

Thanks again.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks, I will post the translations in the next version.
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
UI Messed up

I wondered why your UI is always messed up on my Topaz; even with other ROMs.:confused:

Thank you.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Here is another logfile.

First time it worked - screen still alive while covering proximity sensor. But after first lock, screen goes off when covering proximity while in use.

I covered the proximity sensor several times, always screen goes off and on.
[Touch Diamond, MDA Compact IV Themes and Apps] La_Globule:
I've installed the new version 2.12.3 and the problem remains unchanged : when I place an outgoing call, as soon as the call is established, the screen goes off in any position of the device ; it does not occur for an incoming call.

Thanks for your efforts.
[Touch Diamond, MDA Compact IV Themes and Apps] nila@ufl.edu:
I'm having issues with the screen turning on after calls end, especially with bluetooth activated. I thought it may have something to do with the proximity sensor, as it seems to work fine with the bluetooth on if I keep the phone next to my ear.

I've tried !proximitydisable;!suspend on call end, with or without the detect blutooth settings checked, in conjunction with !promitydisable on bluetooth, still the screen either does not shut off or shuts off and then comes right back on after the call ends.
[Touch Diamond, MDA Compact IV Themes and Apps] HTC_FUZE:
Small problem for BattClock. How to use system default background color? See attached snapshot. BattClock has black back color which looks bad. I try to adjust but it is very difficult to match the original title bar color(half-transparent xxx color). It would be nice to have an option to use system color setting on title bar. Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] akhil8377:
Batt Clock 1.9

uch a nice application, however am not able to get it work with samsung Omnia II I8000 for Battery Current and Battery Temperature. Any reasons. It works with HTC Touch Diamond
[Touch Diamond, MDA Compact IV Themes and Apps] AboveTheBULL:
Hi! I have been using this excellent program for months on my Touch Pro (best locking program for it, hands down!) It really has been awesome. But now that I try it on my new Touch Pro2, bluetooth headset answering does not work right.

When an incoming call rings the locked phone, pressing the bluetooth headset's answer button no longer answers the call. Instead, it just sends the phone's audio to the headset -- e.g., the ringtone that was sounding through the phone's speakers will start playing through the headset. But the call will not be answered -- it will continue to ring. Then, if I press the bluetooth button again, ringing stops and the call is sent to voicemail (as if I hit "ignore")

To actually answer the call, I have to use the touchscreen. :( *OR* if the bluetooth headset was already off and the call comes in, I can turn on the headset, and if it pairs up with the phone in time, it will automatically answer the call through no action of mine.

I'm thinking it must be something different about the TP2's bluetooth stacks when compared to the TP's, and this difference isn't being taken into consideration by TLP. Short of using the HTC Lock API (and losing all the cool features that make this program the best), is there a way we can make this work right?

*ALSO: I notice the bottom left corner of the screen (the left softkey) has a very small live/unlocked section when the screen is on but locked. I do not mind a small unlocked area for the upper right corner (task manager), but the bottom left is the camera softkey. So sometimes, I pull my TP2 out of its pouch and it goes into "camera" mode. Is there a way to close up that live/unlocked section and keep the upper right corner one?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I do not have a clue, I have never seen this. Other people having the same problem?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the input (again).

Ok, It took some time because I was busy previous week. I solved several problems, so I believe the new version 2.12.4 should work now. Fingers crossed :rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
For me the InCallTweak is also working with an outgoing call.

Maube you have a different PhoneCanvas for incoming and outgoing calls (which takes care the sensors keeps working)?

Other people also having this problem?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The new version 2.12.4 has done some fixes in that area. So probably this is solved with that version.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You should make a screenshot from your phone/theme.

Then use a editing tool on your PC to select an area with the size of BattClock, probably an area which is not occupied but looks like it should be in the BattClock area. Than you can use that as background image.

See also this post, maybe one pixel width is good enough for you too
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparently the BatteryDriver does not support reading out these values. So I cannot do anything about it :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Probably TP2 uses another mechanism for transferring the commands to your phone, so these are blocked when TouchLockPro is locked. You can enable debug logging and see which keys are hooked and if you can unhook them. If they are the regular answer/reject keys, this is not an option, of course.

The soft buttons not locked is also related to the fact that the screen hooking is not working for that part on TP2. The only option you have now is to use HTCLockAPI = 1. I do not have an idea how to lock that area too, it should have been locked with the screen hooking, but apparently HTC did something special for that area.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
New version 2.12.4 with bug fixes

Version 2.12.4 (7-3-2010) for all Windows Mobile touchscreen phones, *NEW* Proximity sensor support for Samsung and HTC having proximity sensor

- Updated Russian (thanks to Vadim Bogaiskov) and Dutch translations (thanks to myself ;-) for BattConfig and TouchLockAction.

- Visual feedback if a button is pressed

- Do not do !SCREENON at end call when lock(suspend) command or bluetooth is active

- Some commands are now also executed when not power on/screen on (lockscreen, locksuspend, suspend) to achieve the previous point

- When multiple commands are specified, make sure to execute them via a request,so events related to a previous command are effected already (e.g. screen off).

- Fixed problem that multiple commands where only executed the first time (e.g. Proximity disable/ignore problems)

- Fixed possible problem that multiple commands could mean that an earlier one was not executed/overwritten
[Touch Diamond, MDA Compact IV Themes and Apps] Jesse Buck:
Let me start by saying that I love your application and have been using it for a while. I can't seem to set up the proximity sensor how I'd like it. I'd like to have the proximity sensor only enabled to unlock my phone. I have the settings you suggested two pages ago. I am running the current version, 2.12.4 on a cdma TP2, but it is still not giving me the proper behavior. I'd be happy to post debug file if it would help or perhaps test new versions.
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
how to lock keys?

My desired behaviour of HD2 Leo is:

when the phone rings, until the call is ended, disable all hardware keys.

Is it possible to accomplish this in TLP?

I am running 2.12.1 and I have LockWhenIncoming=1 and KeysOnly=1. When it is ringing, and I covered the sensors, I can see the phone is locked (battclock white). However, pressing the green key still accepts the call. Why? Shouldn't the keys be disabled when the phone is locked? After the phone is connected, with the sensors still covered and phone still locked, I can use either the red endcall hard button or the screen soft button to end the call. Shouldn't they be ignored while the phone is locked?

In the list of builtin commands at 4.13, where isn't there a command to lock keys? There are commands to lock suspend or to lock screen, but none to simply lock (without suspend) or to lock only the keys.

I have a related question. If I use the TAPI option LockWhenIncoming=1, when will it unlock? Will it unlock itself because of light sensor or G sensor etc? It is possible to keep it locked until end of call?
[Touch Diamond, MDA Compact IV Themes and Apps] sjanos:
Hey MAN!

That's the perfect one for Xperia!

Many thanks!

Brgs,

/Janos
[Touch Diamond, MDA Compact IV Themes and Apps] nila@ufl.edu:
Works much better on the tests I have done, thank you. There is just one or two times when the call will end that the unit will not suspend, but for the most part the screen turns off now every time I answer and end a call, which is exactly what I was trying for.

Fairly consistently with bluetooth/headset off or not in use when I answer an incoming call the screen shuts off and then turns right back on. Not a very big deal overall, but just a minor thing i noted.

I'm using !proximitydisable;!suspend on connected and !suspend on ended.

Thank you again for this great program.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you set?

CmdUnlockNoCall = "!PROXIMITYIGNORE;!PROXIMITYDISABLE"

If you also do not want the proximity sensor to be used by phone canvas, you can try to set:

CmdUnlockCall = "!PROXIMITYIGNORE;!PROXIMITYDISABLE"

I do not know if phone canvas will enable the proximity itself thereafter.

If both are not giving the expected result, please enable debug logging, reproduce the scenario and post the debug log file \TouchLockPro.log.txt. Maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Looks like the keyboard hooking is not working on your phone. Hmmm, does it also not work after softreset and locking the phone. Is the answer/reject key not locked then? You can post a debug log file and reproduce the scenario, maybe that gives me insight? But the BattClock indicating it is locked, means the keyboard hooking is not working for your phone. I also remember some people with older software had problems with locking keys. Maybe that is the case too for you?

The key locking is currently only available at incoming call as option. On the wish list is a command to lock only the keys.

When using LockWhenIncoming = 1, then it will unlock with the configured sensors or when the call is connected (if UnlockWhenConnected = 1). There is no option to keep it locked until end of call.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In your previous log file, I see:

2010-03-07 02:26:46 1831216202 LLKeyboardHookCallbackFunction hooked: 114

That corresponds to the talk key:

114 = Talk: VK_TTALK = 0x72

So it may that this was the case there too. Maybe others, having bluetooth can react?

Bluetooth devices communicate differently and the bluetooth stack will also influence that. So it can be that a key is send. Note that with HTCLockAPI = 1, HTC is smart enough to let answer/reject through in most bluetooth devices.

Look for LLKeyboardHookCallbackFunction hooked in the log file, to see which keys are blocked.

I only intercept Zoombar commands for unlocking, I cannot block them. So maybe that is the case.

There is another option, DoubleTouchPanelLock = 1, which has an additional locking possibility of the screen, so it also locks the most right part of the taskbar (and maybe the lower part?). But on some phones this mechanism does not work and TouchLockPro freezes.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can enable debug logging, reproduce the scenario: answer incoming call the screen shuts off and then turns on right back. Maybe that gives me some info who does this off/on. It could be the InCallTweak?
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
hard keys does not lock during ringing

Since I have powered off last night, I suppose it already counts as soft reseting (actually I should have soft reset dozens of times since installing 2.12.1).

Log attached. There are two calls made. First call at 14:34. I left the USB connected so phone doesn't lock, so ignore it. Second call at 14:35. Although phone is locked (BattClock white), I accepted the call by pressing the green hard button. Actually, the panel is locked so slide to accept/end cannot be done at this point of time.

(also tested separately without logging: when the phone is locked, pressing the red hard button during ringing does not drop the call).

What is strange is something I didn't notice yesterday. After connection, I can see the connection time running (00:01, 00:02 so on). When I press the red hard button, I can see the red "end call" soft button turns from red to grey. The connection time also stopped running (stays at 00:04), but the phone call panel is not going away. It continues to show the grey "end call" soft button and the 00:04 connection time. However, the phone is still connected -- I can hear via the hardset of the calling phone (I happen to notice this because the connection time on the other phone continues to run)! Pressing the red hard button multiple times changes nothing. It seems there is no way to disconnect the call from this side until the phone is unlocked.

If at this point of time I release the finger covering the sensors and unlock the phone, the panel will not work -- if I press the End Call soft key (now grey in color, instead of red), it does nothing. If I press the red hard button now, the call would be successfully disconnected.

Phone is HTC HD2 Leo. Do you need to check my versions?