yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
I have a Touch Pro 2 and I use BT and zoom bar just fine.

If you want to use the zoom bar then you absolutely must set HTCLockAPI = 0.

If this blocks your bluetooth buttons then you can try adding the BT button codes to the unlocked keys list in Keyboard Settings and see if that works.

If you need help determining your BT button codes, enable debug logging, reproduce the issue where you press your BT button and nothing happens, then either look at the log file yourself and see where button x was blocked or post the log file here (zipped) and someone can determine the codes from that for you.

This happened to me once but only with a certain ROM I was using. Other than that one ROM, BT codes were never blocked for me.

I looked at the log files you uploaded and it appears that in both scenarios you were using HTCLockAPI=1. Change this to 0 and recreate the log files and post them again.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

thanks that sounds promising - i have uploadad again - can you tell me what keys for BT to exclue ?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Can you upload the touchlockpro log file? (the one you attached was the touchlockaction log file)
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Sorry, here attached ;-)

That would reallly sove my problem. I think you are on the the solution, because if i check "locktouchpanelonly". i can piuckup calls with BT. So it appears that its the hardware key for picking up calls via my geadset that i have to release, just as you say

thanks

Nolan♠
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
@Nolan

The only thing in the log file you uploaded was:

2009-12-21 07:13:25 -850671082 ERROR loading HTCAPI.dll
2009-12-21 07:13:28 -850671082 ERROR loading HTCAPI.dll
2009-12-21 07:13:40 -850671082 ERROR loading HTCAPI.dll
2009-12-21 07:13:45 -850671082 ERROR loading HTCAPI.dll
2009-12-21 07:13:48 -850671082 ERROR loading HTCAPI.dll
2009-12-21 07:13:48 -850671082 ERROR loading HTCAPI.dll
2009-12-21 07:13:52 -850671082 ERROR loading HTCAPI.dll
2009-12-21 07:13:58 -850671082 ERROR loading HTCAPI.dll
2009-12-21 07:14:03 -850671082 ERROR loading HTCAPI.dll
2009-12-21 07:14:11 -850671082 ERROR loading HTCAPI.dll
2009-12-21 07:14:16 -850671082 ERROR loading HTCAPI.dll

I'm not sure how to help cuz I've never seen this before.

ZR might know more - I'm going to download his latest source code and will let you know if I think of anything that might help - but for now - I'm not sure what to suggest.

sorry
[Touch Diamond, MDA Compact IV Themes and Apps] LordDeath:
Hi,

are there any plans to add this zoombar unlock feature to the Touch HD? Its four hardware buttons at the bottom can be used as this, too.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

strange i upload again this time data are correct

thanks

Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] fuorionda:
Incall tweak problem. Why the screen go off in reverselandscape and not in landscape? i think it's better to go off in both cases :)
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
According to your log file, the only button press detected was 114 and it was hooked meaning blocked.

2009-12-21 15:30:20 -924897534 LLKeyboardHookCallbackFunction hooked: 114

Try adding 114 to your unlocked keys list and see if that enables your BT.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The idea behind it, is that if you hold the phone to your ear when in a call, it is likely to be portrait or reverse landscape, because the phone speaker and microphone is then in hear/talk position. Does not make sense to have the phone in landscape to your ear, because then you would talk into the speaker :rolleyes:

Also you want to be able to see information when flat or landscape, I think, instead of screen off, e.g. for taking notes.

Is there a special reason you want it also off in landscape :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] Punga:
Hi ZuinigeRijder,

Unfortunately this isn't the case with incoming calls on my HTC Touch Pro.

This is the situation:

- Device remains inside pocket (dark), display was switched off

- Incoming call starts

- Device wakes up and shows the incoming call

- TouchLockPro keeps the device locked due to darkness

- Device is pulled out of the pocket - into the light (tested below a bulb)

- TouchLockPro still keeps the device locked

- 15 seconds later, incoming call stops but TouchLockPro even keeps the device locked

- Unlocking now will show the "unlocked" indicator, although LockIndicator was set to "0"

My settings different from default:

SuspendOnBacklightOff = 0

LockIndicator = 0

BTW: Is there any setting to make TouchLockPro only lock the device on incoming calls but not if the power switch was used manually (maybe AutoLockOnPowerOn)?

Cheers

Punga
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I tested myself with your settings and on my phone it is working.

Can you enable "logdebug = 1"and "logdebugdetailed = 1" as described in post #3 and post the zipped log file in an attachment, so I can have a look at the logging?

Currently, TouchLockPro is not specific for any application. That is also the great advantage, it works also for non-incoming calls. So it is not specific designed for locking only for incoming calls. Other solutions exist, which do that only, like answerkeys disabler. Those are designed only for incoming calls.

If you overrule the setting with "AutoLockOnPowerOn = 0", it will be locked when an incoming call comes in or the power button is pressed or an event wakes up the phone, only when it was locked at screen off/suspend. If it was unlocked before screen off/suspend, it will be unlocked too when an incoming calls comes in or the power button is pressed or an event wakes up the phone.

In that sense you are in control then, but you must also take care that you leave the phone in the correct state according to your wishes. If you forget to put it in the locked state and put it in your pocket, you still may miss calls by accidently pressing keys/touchpanel with setting ÄutoLockOnPowerOn = 0"

Hope this explains what you asked for.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
why is PAYPAL not working for you? What goes wrong?
[Touch Diamond, MDA Compact IV Themes and Apps] jdivic:
Lock delay

Hi,

Am I the only one facing this problem? I have Touch Pro and I'm very satisfied with this utility, but it bothers me that when device is turned on there is a small time period of about 0,5 to 1 second while device is unlocked, and then device locks itself and displays the time and battery status icon on topbar. Does anyone experience problem like this?
[Touch Diamond, MDA Compact IV Themes and Apps] MartijnRasenberg:
Same here!

The hardware button - activation does not work on the HD unfortunately and unlocking only works good removing the styles...the other ones are not really stable.
[Touch Diamond, MDA Compact IV Themes and Apps] jdivic:
Unlocking works fine here, but locking is not done at the moment of turning on but it has delay of about few tenths of second... and yes touchscreen respond during that period (you have to be really fast but if you touch the screen just after turning device on your touch will be accepted meaning device is not locked...)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, of course it has to do with the time my app gets after notification of power on. I try to lock immediately, when I get that event.

Can you enable "logdebug = 1" and "logdebugdetailed=1" setting and add the log file as attachment to the post. So I can have a look.

If you overrule the setting with "AutoLockOnPowerOn = 0", it will be locked when an incoming call comes in or the power button is pressed or an event wakes up the phone, only when it was locked at screen off/suspend. If it was unlocked before screen off/suspend, it will be unlocked too when an incoming calls comes in or the power button is pressed or an event wakes up the phone.

In that sense you are in control then, but you must also take care that you leave the phone in the correct state according to your wishes. If you forget to put it in the locked state and put it in your pocket, you still may miss calls by accidently pressing keys/touchpanel with setting " AutoLockOnPowerOn = 0"
[Touch Diamond, MDA Compact IV Themes and Apps] Pietje_1985:
No haha:p

it's not going wrong....it's just the fact that I dont have creditcard....:D

Hope you'll understand....

Regards

Jeroen
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hope you have a not bankrupt bank-account, because then you can just register for free at PayPal and donate via your bank account with PayPal in-between. But the software is *FREE*, you do not need to donate ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Google Translations

I added Google translations for all the supported translation languages of Google, because often people are not so good in English in post #1

Probably the translations will not be well, but maybe it gives enough extra insight in the flexibility of TouchLockPro and answers some questions.
[Touch Diamond, MDA Compact IV Themes and Apps] GriFolle:
Hi Zun...this is my logdebug file.

Please note that (after the last uninstalltion) I've just did theese steps:

-reinstalled TouchLock

-tryied (and verified) the presence of the mentioned bug (battclock display locked but it's really not)

-overruled settings for light sensor (disabled)

-reset

-tryied (and verified) the presence of the mentioned bug (battclock display locked but it's really not)

-activated the detailed logdebug

-reset

MY TEST WITH LOGDEBUG ENABLED:

First test...

1) poweroff the device

2) after about 20 seconds power on: all was ok, touchpanel locked, hardkeys locked

Second test...

1) poweroff the device

2) after about 20 seconds power on: bug!

PS: all successive tests will like the second one...

TIA
[Touch Diamond, MDA Compact IV Themes and Apps] sandsage:
Great App!

This is the best Lock App for the Diamond that I have tried. Keep up the good work! Bedankt
[Touch Diamond, MDA Compact IV Themes and Apps] Happy1602:
I have a little bug!

If i change the clockbackgroundcolor to ff0000 (red) it is not red all hexcodes for red are blue!

Can anybody help me to make the backgroungcolor red?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I used in my code COLORREF.

As you stated correctly, it is not as described in my settings page.

http://msdn.microsoft.com/en-us/library/ms532655(VS.85).aspx

When specifying an explicit RGB color, the COLORREF value has the following hexadecimal form:

0x00bbggrr

The low-order byte contains a value for the relative intensity of red; the second byte contains a value for green; and the third byte contains a value for blue. The high-order byte must be zero. The maximum value for a single byte is 0xFF.

So the order is BBGGRR, instead of RRGGBB.

Sorry for the wrong information provided. I will update post #3.

So your value must be FF00.
[Touch Diamond, MDA Compact IV Themes and Apps] Happy1602:
If i use ff00 it is green!

Sorry is not for background is for foreground!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I made a typo in my reply, bbggrr means you need to set FF.
[Touch Diamond, MDA Compact IV Themes and Apps] Happy1602:
THX!

Now i understand it!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I will disable the input already at power off in the next version, when AutoLockOnPowerOn is set. Just to avoid the small chance described.
[Touch Diamond, MDA Compact IV Themes and Apps] Latty:
Is there a way to make the BattClock show 12Hr time?
[Touch Diamond, MDA Compact IV Themes and Apps] iulian_2007:
great ap, thank you for sharing with us. I have tho a problem:

-the phone is locked in my pocket

-somebody calls me

-the phone is still locked

-I have to wait about 5 seconds to unlock so I can answer (touch and also keys are locked).

Is it possible to have the keys unlocked when somebody calls me?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I have read posts about the ZoomBar working on the HD. So there seems to be hardware available doing that. I do not own a HD, so I cannot test. Currently TouchLockPro subclasses a Window with the name HTCSmartTouchDll. I do not know if that dll is available on HD and if it is loaded? Apparantly it is not working out-of-the-box with TouchLockPro.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
114 is also the normal TALK button, so it is possible then you answer a call while in your pocket. So I am not sure if he tried the bluetooth button or that it is the same as the talk button :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Cobaltikus you are brilliant !!! That solved my problem - with these settings TLP 2.9 finally comprised all my wishes, couldnt be more happy.

A BIG thanks to you ;-)

In gratitude

Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Multitouch is of course great, but because TouchLockPro does not have a foreground window, it might be a problem detecting gestures. But maybe the initial journal method of Cobaltikus gives me a way to detect a gesture when locked. But there is a good chance, with the touchpanel locking method nothing is given back of course, otherwise the panel would not be locked :cool:

I understood from another post in another Thread that the TouchLockPro works with the Light Sensor and GSensor available on HD2. Can you confirm that and the above questions :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

yes you are right i just checked. Is this a non-solvable problem ? I mean will pickup from BT always be identical to pressing the talk button on the phone ?

@cobaltikus: do you have the same experiance on your system ?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
not any more. I try lots of different roms for my Touch Pro 2 and only one had this problem. I have noticed that some roms have different key codes for the buttons than other roms. The problem could be that with your current rom, bt buttons are translated to match the hardware answer/end button - OR - it could be your BT ear piece is sending the same key codes as these hardware buttons.

I'm curious to know:

what phone do you have (I have the Sprint Touch Pro 2 [CDMA])

what rom are you using (I am currently using Calkulin's latest rom)

what bt ear piece are you using (I'm using plantronics voyager 510)

... and I no longer have that problem and do not need to specify any key codes to unlock
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi Cobaltikus

i have a HTC touck Pro 2 model T7373, the rom is the latest downloaded original HTC (of WM 6.1) rom 1.19.403.3 (51489) rom date 30 June 2009, BT version 2.1. My BT ear piece is a Plantronics voyager 520.

1. Is your ROM version the same ? If so, the explanation must lie some where else i guess?

2. What are your settings maybe the explanation lies there ?

3. thinking of it; how can it be that is is possible at all to accept calls via Bluetooth - i would have thought that the phone would always interprete this action to be identical with pressing the talk button on the phone ?

How should the phones software determine any difference between BT acceptance and pressing call button ?

4. If pressing BT button on ear set and we assume this is identical to talk button on phone, how come that pressing the BT ear set button again terminates the call ?

This would in this case be identical to pressing the call button again on the phone - which does not end the call. The end call button on the phone is locked by the way.

I hope someone cal help me identifying the reason and solution to this

I just wonder

5. Further what is the effect of DetectBluetooth = 1 (here TAPI is disabled autoantically i understand) if user cannot answer incoming call ?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] zoot600:
not working the screen is not locked

double lock
[Touch Diamond, MDA Compact IV Themes and Apps] Martinhdk:
A VERY nice app. For me the most important is missing though.

The old SENSORLOCK for Diamond had one very unique feature: To be able to configure how to lock/unlock the screen by using G-SENSOR.

It had a nice and easy gui and that feature is in my opinion a very needed feature to make TLP a superior lock app.

Could that be on the Roadmap for TLP? (And for more devices?)

:)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You are right that currently the GUI for configuring the GSensor moves is not so nice. It is already on the wish list:

- Record mode for GSensor orientation changes, for easier configuration

Note that if you want the same default unlocking/locking method of SensorLock, you can configure this as described in this post.
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
No, I'm using:

Calkulin's Touch Pro2 28014 Manila 2.5 ROM (v1.2) 6.5.5

http://forum.ppcgeeks.com/showthread.php?t=99598

I'll get back to you on this one - don't currently have it installed due to development and testing

A BT earpiece sends different commands to the phone based on when and how you press the button. If you are not currently connected to a call and the phone is ringing it will send the answer command. If you are on a call it will send the end command. If you hold it down it will send a command to the M$ Voice Command program (if you have it installed).

ZR might be better to answer this - I never use TAPI - I don't want anything to automatically lock or unlock - That is actually why I love TLP, no other lock program has this option - the ability to stay locked until you unlock, and to stay unlocked until you lock it.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Indeed the following commands will not be executed, when DetectBluetooth is configured:

* Incoming (CommandCallIncoming = )

* Connected (CommandCallConnected = )

* Ended (CommandCallEnded = )

DetectBluetooth (DetectBluetooth = 0)

With this setting enabled, you can keep the phone locked when Bluetooth radio is on, do not unlock by light sensor and do not execute TAPI commands. By default this setting is disabled, if you want the bluetooth detection, enable this setting.

The idea behind it, is that you then do not want additional commands to be executed, when bluetooth is on. Is there a special reason you still want to execute one of the above commands?
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
@nolan

my settings

Light Sensor - Everything is unchecked

Stylus Sensor - Everything is unchecked

GSensor - Everything is unchecked

Nav Sensor - Everything is unchecked

Keyboard - Everything is unchecked - but I have 38,40,117,118 unlocked so I can change the volume 117 and 118 are volume up and down and 38 and 40 are up and down (not necessarily respectively) - depending on your rom/vol control app you may or may not need 38 and 40

BattClock - Stripe and Lock Indicator are checked, font size is 16 but doesn't matter, ClockLockActiveTime is 5000 not sure what that means I left it alone, X = 0, Y = 36 for new 6.5 UI and 50 for old style UI, width = 800, height = 5 or 10

Telephone API - Everything is unchecked

SIP - blank

Other Settings - AutoLockOnPowerOn, UnlockOnACPower are checked. SuspendTimeoutPowerOn = 20000, beeps vibrates are 0, led number = -1

I switched to Juicy's latest rom and now half the time I cannot answer with my earpiece and half the time I can, but I don't think it is related to TLP but it is possible (haven't tested enough to be sure). When my phone rings, I press the answer button on my earpiece and it will either answer the call as it should or it will switch the sound from my ear piece to the phone or from my phone to the ear piece but still keeps ringing and doesn't actually answer. I'm switching back to Calkulin's rom soon, might try MightyROM soon as well as I haven't tried his last couple releases and his are usually pretty solid.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi Cobaltikus

thanks

interesteing what you erote here: "it will switch the sound from my ear piece to the phone or from my phone to the ear piece but still keeps ringing and doesn't actually answer" Thats exactly what i experiance too

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] Martinhdk:
Sounds great- thanks, a donation is coming up
[Touch Diamond, MDA Compact IV Themes and Apps] piannetta:
Hi, I'm using 2.9 (which I made a donation on, awesome piece of software - thank you) on a stock Touch Pro 2.

I've found that the screen is staying locked when an incoming call arrives, and the phone doesn't seem to response to swipes on the zoombar to allow me to answer the call. The only way I can answer is to remove the stylus then slide to answer using the HTC dialler.

I've tried all sorts of setting to stop this, would love to know how I can have the software not lock on incoming calls, or at least respond to zoombar swipes.

Cheers,

Pete
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
Make sure that HTC Lock API on the Keyboard settings page is not checked if you want to use the zoombar. (Was it already like that? if so I'm not sure what's wrong there.)

The Telephone API settings page has all the other requirements mentioned.

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

Make sure to note the TouchLockPro Commands (that start with "!")
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Thanks for the very good donation.

As Cobaltikus already responded, the ZoomBar unlocking is NOT working when you have configured HTCLockAPI = 1. So I do not know if that is the problem.

Which home screen do you have, TF3D?

You can enable debug logging (LogDebug=1), reproduce the scenario and post the log file \TouchLockPro.log.txt on the phone memory as zipped attachment. Maybe that gives me a clue (it also shows your settings then). I am also curious if it detects the triple touch of the ZoomBar to unlock or not.

Hope we can find the problem :cool:

Note that you also can configure KeysOnly (LockWhenIncomingKeyOnly = 1), so you can answer with the Slide2Answer at incoming call.
[Touch Diamond, MDA Compact IV Themes and Apps] piannetta:
Thanks to Cobaltikus and to yourself ZuinigeRijder for your helpful and comprehensive replies.

I have played around with thw TAPI and KeyBoard settings. Cobaltikus, HTCLockAPI was not set and I also tried different combinations of settings as per the link you gave me. At the moment, my TAPI settings are as follows:

UseTAPI=1

UnlockWhenConnected=1

InCallTweak=1

All others = 0. I also have set the Incoming command to !UNLOCK

When an incoming call arrives, the red bar at the top remains (indicating it's locked). I tried the triple tap of the ZoomBar and no response. I also tried the setting to lock the keys only but again, both the keys and the screen were locked. I did get the ZoomBar to work though but I had to swipe 2 or 3 time before it unlocked. It's not ideal though, as I then have to swipe twice to answer.

I am using SPB Mobile Shell 3.5 and I should point out that the previous version of your software worked (as in when a call came in, it was unlocked so I could answer it) so perhaps it's something to do with version 2.9, I don't know.

I have attached the action file and the debug log and hope you can help me.

Thanks again for your replies and great software.

Pete