yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
Still the same

I have upgraded to 2.10.4 but still same problem.

The screen switches off, during a call, when phone is in potrait mode (ie Doing InCallTweak) IN SPITE of the fact that the phone was on charging (ie NOT ON BATTERY)

See attached log file
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
I would prefer following setting:

Unlock with proximity like now with light sensor.

While locked and pressing a button, check proximity-status. Proximity detected --> no unlocking, screen should stay off

If pressed button and no proximity --> unlock device.

So no more unlocking or screen on while in the bag.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Can you post the log file \TouchLockPro.log.txt as zipped attachment, after reproducing the problem, because that one contains the interesting information. ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think it is unrelated to button press. It should do this while locked or at power on and when the status changes. Indeed the same as with the light sensor.
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
Log File

Please find attached
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks.

The logging shows:

2010-01-30 21:23:22 1697240634 NOTIFY_CALLSTATUS_CONNECTED

2010-01-30 21:23:22 1697240634 Skipped InCallTweak: on power

2010-01-30 21:23:22 1697240634 IsConnectedCall(true)

2010-01-30 21:23:22 -2065246598 IsConnectedCall(true)

2010-01-30 21:23:22 -2065246598 IsConnectedCall(true)

2010-01-30 21:23:22 1697240634 IsConnectedCall(true)

2010-01-30 21:23:23 1697240634 IsConnectedCall(true)

2010-01-30 21:23:23 -2065246598 IsConnectedCall(true)

2010-01-30 21:23:23 -2065246598 IsConnectedCall(true)

2010-01-30 21:23:23 1697240634 IsConnectedCall(true)

2010-01-30 21:23:23 -2065246598 IsConnectedCall(true)

2010-01-30 21:23:23 1692850254 HandlePowerNotifications()

2010-01-30 21:23:23 1692850254 PBT_TRANSITION

2010-01-30 21:23:23 1692850254 PBT_TRANSITION POWER_STATE_IDLE

2010-01-30 21:23:23 1692850254 ========================POWER_STATE_IDLE: SCREEN_OFF==========================

So the screen off is not due to TouchLockPro, but due to another cause. My guess is that it is just the light sensor, which is used while in a call, a feature of the HTC Diamond. There is a setting to disable this screen off tweak by HTC.

See this post:

However, I see also another thing in the logging:

2010-01-30 21:23:28 -2065246598 SetOrientation: Portrait

2010-01-30 21:23:28 -2065246598 IsConnectedCall(true)

2010-01-30 21:23:28 -2065246598 =====InCallTweak======IDLE

2010-01-30 21:23:28 -2065246598 Execute(): !IDLE

That one is cause by TouchLockPro. Found the problem. I will fix that in a next version.
[Touch Diamond, MDA Compact IV Themes and Apps] Chainfire:
Let me just share the info then, these are the relevant keys to use the proximity sensor:

HKLM\Software\HTC\Proximity\ProximityDetectStatus

HKLM\System\State\Phone\PSensorStatus

The first shows the current state, the second controls whether the sensor is on or not.

There is nothing special about this, and I'm surprised it is not better known. Note that making/ending a phonecall may reset the second key so you have to turn it back on.

The only real trickery to using the proximity sensor on HTC devices is turning off the default behaviour, i.e. screen on/off depending on proximity, and enabling it's use in unattended mode without side-effects.

As for your e-mail to me and my response, that part of my SensorLib code is not something I am willing to share, but also as stated, I will make an API available for it soon.

The reason why I will not share that part of SensorLib are varied. First it took a long time to figure out. Second, it has to do with injecting into the sensor driver and temporarily overwriting/modifying code paths at runtime. Third, if this trick is performed by several different libraries they really need to know about eachother. If not, if you have two apps running using the functionality, either neither or only one of them will work. The solution is to only have single API provide it - not sharing that code to some extend prevents incompatibilities between different programs.

Oh well, have fun :)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thans for sharing the information, but of course I did already know 1 day eralier :rolleyes: Problem with a lot of these sensors is that those are not documented and sometimes people have found out and shared the approach. How did you find out of the Proximity Sensor registry keys? Just by looking at the registry changes? Or other resources?

I only have a Touch Diamond (poor me ;)) so finding out myself is difficult. Anyway, I can now add support for the Proximity sensor, for HTC and Samsung (Samsung does document their API via the Samsung SDK).

Thanks:)
[Touch Diamond, MDA Compact IV Themes and Apps] Chainfire:
I knew you know, just to make it complete for the other readers. Not allowing the sharing of a few registry keys is utter nonsense.

I myself figured this stuff out by debugging the relevant drivers. With hindsight, it would have been figured out faster with a registry compare, however sensors are generally not enabled/disabled or used through the registry so it wasn't the first thought that popped up. To fix the default behavior and overriding it required debugging the driver anyways, so not much time was lost...
[Touch Diamond, MDA Compact IV Themes and Apps] almico:
Giving up :-(

Hello. I tried for several days to get TLP to work on my HTC HD2 with stock Italian ROM, but with ugly results. Sometimes it seems to be working. Some others not. The first issue I faced was that if I rejected a call using the slide2answer standard facility of my phone, then the phone was blocked for ever. I had to plug the USB charger to regain control of my HD2. I have BattClock installed. Right now I can see BattClock with its WHITE background, which should mean that the phone is locked, but I can do everything. Right now I'm disabling LOGDEBUG and will try to upload the zipped log.

From a software point of view it looks like the internal state of TLP isn't in sync with events, but I must admit that I might have missed something very simple. I tried to uninstall both BC and TLP and to remove the whole registry tree. No improvement.

I'm sure this is the perfect application to suit my needs and I really hope to manage to understand how to properly configure it.
[Touch Diamond, MDA Compact IV Themes and Apps] Chainfire:
Seriously, that is what the SetPowerRequirement call is for, you should not ever set these registry keys manually unless there really is no other way!

Note that on some Samsung devices you need to do this for both ACS1: as well as ACC1: or it doesn't work. (Just always doing both is fine)
[Touch Diamond, MDA Compact IV Themes and Apps] r00sick:
Why not? :)

Omnia have no built-in device, that named ACC1:
[Touch Diamond, MDA Compact IV Themes and Apps] Chainfire:
I am assuming here you want a solution built into TouchLockPro and not just tinker with it yourself.

Because what happens if multiple programs try to do this?

Say you have TWO programs that do this:

A starts and set registry value because it needs sensor data with screen off

B starts and set registry value because it needs sensor data with screen off

A exists and resets registry value because it doesnt need sensor data with screen off anymore

B doesn't work with screen off anymore!

So how to solve? You could let them NOT reset the value, but then the sensor would always be on drawing power! Bad idea.

This is specifically where the SetPowerRequirements API call is for... You won't have this (and other similar) issue.

No, the pre-2009 line of Samsung devices use ACS1: and the 2009-and-newer line of devices use ACC1:

So for a generic solution you'd use both.

That being said I see you state you have an original Omnia. I've had some problems with using that in unattended mode (screen off but CPU on) getting stuck on invalid values. You need to force reset the driver's power in that case.
[Touch Diamond, MDA Compact IV Themes and Apps] zhongzw:
Hi ZuinigeRijder

What's the download link of Chinese Traditional version?

I didn't find it on www.zuinigerijder.com.

Thanks a lot, ZuinigeRijder!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There is not a special version to download, version 2.10.4 contains all the available languages (I replaced it with the Chinse Traditional fix, without updating the version number) and removes the languages not matching your regional language, the first time TouchLockAction is started. So there is no additional disk space occupied for non-needed languages.

So make sure your regional language is set correctly, when you install TouchLockPro and start TouchLockAction the first time.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Sad to hear it did not work for you.

Ok, first let me be clear, TouchLockPro includes the BattClock, so you should not use/install both at the same time, because the settings are shared. And if you only install BattClock only, it will not lock.

Hard to say what is wrong. You uploaded TouchLockAction.log.txt, but \TouchLockPro.log.txt is the interesting log file. Normally, it should do its work already with the default settings. Was that not working? Can you reproduce the scenario where it does not lock and post the debug log file \TouchLockPro.log.txt. Maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] zhongzw:
I see. Thanks very much!

My touch diamond is Chinese simplified, so after I installed TLP, the interface is English. :)

I would translate to Chinese simplified , please tell me how to do it .
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Of course, others would be glad if you can help in translation.

See attachment of the files which need translation.

For convenience I added both translation files, Chinese Traditional and English. So dependent which one you like to translate from.

The easiest way is using the Resource editor approach. With the ResEditor you can open/save the resx files. See the latest language files in the attachment of this post. It also has the ResEditor.

Steps to do:

1. Start ResEditor and open a resx file to translate (File -> Open)

2. Scroll down to the bottom and only translate the String entries ending with .Text (the right part of the screen). Do not translate Strings starting with >> and do not add/rename entries.

3. Save the resx file

4. Do all the resx files

5. Post the translations as zipped attachment in this support group

I will then update this in the next version
[Touch Diamond, MDA Compact IV Themes and Apps] zhongzw:
ok, I just do it now.

But what is the attachment file?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Sometimes the attachments are not saved, when you press the wrong Submit button. I uploaded the files again in my previous post.
[Touch Diamond, MDA Compact IV Themes and Apps] zhongzw:
Thanks!

please upload "resource editor".
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
ResEditor.exe is in both of the zip files.
[Touch Diamond, MDA Compact IV Themes and Apps] zhongzw:
yes, i got it!

:)
[Touch Diamond, MDA Compact IV Themes and Apps] zhongzw:
Chinese (simplified) is ok!

Chinese (simplified) is ok!

:)
[Touch Diamond, MDA Compact IV Themes and Apps] tigro11:
Telephone API settings, on call set ended, I set the parameter! screenoff call ended but the display remains lit.

The Light setting function that has?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro version 2.10.5 with Chinese Simplified translations

Ok, I just uploaded version 2.10.5 with the Chinese Simplified translations.
[Touch Diamond, MDA Compact IV Themes and Apps] Liffan:
Black background

Hi!

I can´t get the background on clock/batt black, just dark grey.

Anyone that can tell me how?
[Touch Diamond, MDA Compact IV Themes and Apps] old_man:
Hi there!

Is it possible to lock all hardware keys except 'Power ON' with TLP, when the HD2 aka LEO is powered of?

Locking the hardware keys not only, when receiving an incaming call, but generell?

Thanks

old_man
[Touch Diamond, MDA Compact IV Themes and Apps] onkel_neme:
unlock via zoombar

for all people who has problems to unlock TP2 via zoombar.

i have install a new manila 2.5 rom.after this tochlockpro doesn´t work to unlock by the zoombar.

i have try many setings and so one.

then i remember tat i have installed zomads fpr scrolling in some programms, but also doesnt´t work to unlook.after many times i found in forum search a small tool names and i rememeber i have installed last time on my old rom.

and thats it.

after install the unlock via zoombar work perfekt !

sry for my bad school englisch, but ist long time ago ;-)
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Bug in version 2.10.4 on HTC Tocuh Pro 2

Hi

i use HTC touch pro 2 with WM 6.1 and version 2.10.4 of TLP doesnt work as supposed: I set TLP to lock and suspend when i turn the phone downwards, but this doesnt hapen. Further the screen awakes if i touch the area left of the HTC logo (that wasnst a big problem with version 2.9 because the screen remained locked even with light sensor active) and the phone unlockes. I have set light sensor active.

i went back to version 2.9, but any idea why this bug occurs between version 2.9 and 2.10.4 ?

thanks

Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] xuyong:
Yes, the App is very nice, so so many Chinese peaple are using it.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think the HTC Logo contains the proximity sensor, so that one is active causing the behaviour. I am going to add proximity sensor to TouchLockPro, but for now it is the HTC behaviour.

Why it does not lock and suspend by GSENSOR is hard to say without log files. Can you reproduce the scenario with debug logging on and post the log file \TouchLockPro.log.txt as zipped attachment?
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

what i want it to is:

autolock on power on and incoming call, but unlock on light sensor, but NOT if a call is in progress. That was possible in version 2.9 (by an error?) but not in ver 2.10. I cant find any setting that makes this possible. I would assume its fairly easy to implement ?

because the screen is sometimes awakened during call (by touching by accident the proximitysensor by the way i dont even have to touch just move my finger close to the area?) this is a problem that phone is unlocked during call.

It would be a great help to disable the proximity sensor when om bluetooth, its the proximity sensor that is causing the problem with awakening screen during call when sensor is close to something. Thars a real problem because phone is unlocked by accident during call

thanks

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

can i disable the proximitysensor on my tp2 ? It is on when on bluetooth and i dint want that?

thanks

Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] jlmwrite:
Hi --

OK, I must be having an extremely dense day. I'm using TLP 2.10.5 on a Tilt 2 with a stock ROM. I have no weird or funky things running in the background (like GScroll or anything else).

I can't get my phone to unlock using the zoombar. Heck, I can't even find a single setting in regards to the zoombar.

What am I doing wrong?
[Touch Diamond, MDA Compact IV Themes and Apps] aadadams:
I have not been able to get v2.10.x to even lock my Tilt2. I loved the app on my Fuze and really wanted to run it on my Tilt2, but there are very few Tilt2 details in the thread. Until this is detailed, I have regressed to an iphone-esque solution that I am not very happy with...
[Touch Diamond, MDA Compact IV Themes and Apps] ugumba:
Hi! Here's a bump for the request for unlocking the Talk (green) key at incoming call, when a wired headset is detected (HKLM/System/State/Hardware/Headset).

This would allow us to answer using the wired remote, while locked. Maybe even the HTC remote can be detected? The risk of accidentally hitting the Talk key on the phone under all these conditions, is a risk I'm willing to take!

Thanks again for a fantastically flexible, yet unobtrusive locking solution!
[Touch Diamond, MDA Compact IV Themes and Apps] krex:
Hello Zuinige,

I've tried this version, but I have a problem. TouchlockPro works well, but after start the camera (no need to take a pic) and exit, then Touchlockpro stops. I checked the gsensor too in the Settings, and the sensors are stuck in a given position. After a SR until I don't start the camera Touchlockpro works again.

I attach the logs, I hope maybe you can help...

thanks in advance
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.11

Just uploaded TouchLockPro 2.11.

Note that the site has been moved to:

http://touchlockpro.sourceforge.net/

Version 2.11 (7-2-2010) for all Windows Mobile touchscreen phones

* Fix: Do not do InCallTweak when not on battery or Bluetooth is active

* Take over BattClock 1.6 and 1.7 standalone features in TouchLockPro

* Added option to show info divided into 3 lines

* Added option to see free memory

* Date and Time color separate configurable

* Option font color to be dependent on the battery/memory status

* Add icon possibility as background and draw info on top of it, good for people having not a solid color or nicer looking icon alike

* Added settings BattClockInfo1, BattClockInfo2, BattClockInfo3, BattClockVersion, MemoryIndicator, LowThreshold, MediumThreshold, LowColor, MediumColor, HighColor

* Fontsize per info line configurable, text room is divided dependent on fontsize settings.

* Option to show free memory in MB instead of %

* Make BattConfig more finger friendly

Please let me know if you have problems with downloading.
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
G Sensor not working

Am I the only one? I can't unlock by G sensor. When I am watching TV, the room is dim and there is no way to unlock my HD2.

The G sensor sometimes works. Once out of twenty. Very rarely do I see the "G1" status, hardly ever G2. When I am at the settings, I can see other indicators changing (such a light sensor chaning value), but the G sensor always says portrate no matter how I hold the HD2. Since I can play the Teeter game, my G sensor should be sensitive and working fine. It just doesn't work with TouchLockPro.

It is really frustrating the TLP does not offer a more reliable way to unlock. Such as sliding on screen, or shaking. On HD2, the only reliable way is the light sensor, but my sitting room registers a sensor level of flat zero. I need to turn on a lamp to unlock the HD2.
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
Nice release; much improved. Any chance of having the indicators on the same line. I wish to place them on top of the taskbar (pls see pic).

Thanks
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Did you set the correct Phone Type in the Settings menu? Because there is indeed no setting to enable/disable the Zoombar. Dependent of the phone type it knows if the phone has a Zoombar and automatically uses that.

If that is the case, you can enable debug logging, reproduce the scenario and post the log file in the root of your phone, \TouchLockPro.log.txt as zipped attachment.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, I thought the Tilt2 was exactly the same as Touch Pro 2. But maybe it is not. I would expect the ligh sensor, GSENSOR, Stylus Sensor, Keyboard sensor and Zoombar is working.

Can you enable debug logging, try the different sensors and post the log file \TouchLockPro.log.txt in the root of your phone memory as zipped attachment. Maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I will see if I can make an option to unlock the keys (only lock TouchPanel), when a HeadSet is detected.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked into the log file and could not detect something strange. I think it is more related to the camera code, so nothing TouchLockPro can do about. If the GSensor is not reacting anymore, TouchLockPro will not get updates anymore :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Strange, but other HD2 users should react, because I do not own a HD2. At least I did not hear about the GSensor problems on HD2.

I am working on the Proximity Sensor for unlocking, so that would be of interest for you, because HD2 also has this one.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am planning to make it possible to specify 1 customizable string to display. So then you can specify exactly the information you want to be seen, including a long one-liner. So I will put it on the wish list.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi Zuinige

great to se that you are working on the proximitysensor. Do you know by now how to disable it completely (its a real annoyance having this interfering with TLP)?

Or maybe (if promixity sensor cannot be disabled complete) have TLP neutralise proximity sensor awakening screen by checking action from sensor and immediately turn screen off?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I am planning to have a setting to enable it only when locked. Probably you want also a setting to not enable it when bluetooth is active.
[Touch Diamond, MDA Compact IV Themes and Apps] Slide:
Hi ZuinigeRijder,

is it possible to add "CPU Usage" in BattClock/TouchLockPro?

Greeting

Slide
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
GetIdleTime() could be used, but I do not know if this is supported on Windows Mobile:

dwStartTick = GetTickCount();

dwIdleSt = GetIdleTime();

Sleep();

dwStopTick = GetTickCount();

dwIdleEd = GetIdleTime();

PercentIdle = ((100*(dwIdleEd - dwIdleSt)) / (dwStopTick - dwStartTick));

I will have a try ;)
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Great! if you could disable proximity sensor when phone is on bluetooth - i would be more than happy ;-) That should solve the problem

But enabling proximity sensor only when locked would still make screen awakening when fingers are close to sensor, so that would constitute an annoyance. Why would you have that build in as a feature, ie when would that come handy?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Hi, is it possible to include cpu-speed to battclock or TLP? Would be very interesting, if HD2 really can do speedstepping and which current speed it has.
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
I've installed two different versions of TLP on my HD2 and the G-Sensor behaviour is the same. I haven't installed any other G-sensor related applications.

Yes it would be nice to be able to unlock via the promixity sensor. But how? Just by havning nothing near by? Or tapping it in a pattern?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I will investigate if there is an easy API for that.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The plan is to unlock when there is nothing nearby. I cannot test myself, so when I have a version I will ask people to test it.
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
Refer to the thread

http://xdaforums.com/showthread.php?p=5583957

Seems user experience is mixed.