yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] longice:
I don't think so. Backlight is in windows settings set to turn off after 30 seconds, screen off after 60 secs. In TLP, SuspendTimeOutPowerOn is set to 60000 ms.

It goes straight from backlight ON => screen OFF. That's what made me wonder...! It hasn't been like this before. I can't understand...
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
thanks - i have attached the zip file

PS i set key 8 being back key on hardware buttons to unlock

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] tatarasi:
I apologize, the reason is, as stated, because the solution is related with TLP, and maybe others would like to know the answer, too.

I did open a new thread
[Touch Diamond, MDA Compact IV Themes and Apps] AndrewASB:
Blocked alarm screen

Hi,

I unlock my HTC Touch HD with light sensor only.

But I have unlocking problem with G-Alarm (http://www.ageye.de/index.php?s=galarm/about). I can't unlock device when alarm starts:confused:.

Alarm screen blocked (white TouchLockPro indicator, but I can't get original screenshot - device is blocked ):

Yesterday I tried within 10 minutes unlock my device in all ways accessible to me (soft resets etc.).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Aha, you did set:

LockTouchPanelOnly = 1

So the keys are not locked and also the unlocking does not work then.....:rolleyes:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The logging does not give me a clue, so I do not know why it behaves now like this :cool: Did you have other programs installed, who can give this behaviour :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, there is a problem which I will solve in a next version. Normally, G-Alarm tries to unlock TouchLockPro, but TouchLockAction.exe is no longer located in \Windows path. So you can copy TouchLockAction.exe to \Windows. Maybe you also need to configure somewhere in G-Alarm that you want to unlock TouchLockPro.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi ZuinigeRijder

addition to post 2685:

i noticed that when the screen is locked during a phone call - if i tap the area on the top of the screen, where the rows of icons are located - the screen is suddenly unlocked. Is this a BUG - or a feature ?

thanks

Nolan

BTW it a strange thread structure - isnt it possible to create separate threads with different topics - i cant find this anywhere? several questions are posted and replied to within the same thread :-)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Yes, the right part is sensitive to touches, but if you set DoubleTouchPanelLock = 1, then this is no longer the case. But some people have problems with this setting. It will not unlock though, or it must be the other sensors, e.g. light sensor.

All the questions related to TouchLockPro are asked/answered in the same post, because otherwise a lot of new Threads would be created and people cannot learn well enough from questions of others. So you have to look for answers to your questions (and subscrie to this Thread via the Thread tools). I actually solved the mystery of why the keyboard unlocking does not work a few posts back.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

ok ZuinigeRijder, thanks a million for your answers - i understand.

But if i set LockTouchPanelOnly = 0 key 8 still do not unlock :-(

And if i set double touhpanel lock = 1 it cannot lock...

any idea?

Attached logs

best regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, for some people touchpanellock = 1 does not work, so apparently it does not work for you too. The right area pressing can not do harm, so you have to live with that (it will not unlock by that).

In the logging I see now the following keys detected by TouchLockPro:

21:56:45 -1379807874 LLKeyboardHookCallbackFunction hooked: 237

21:56:46 -1379807874 LLKeyboardHookCallbackFunction hooked: 117

21:56:46 -1379807874 LLKeyboardHookCallbackFunction hooked: 92

So it looks your phone gives different keycodes. 117 is probably Volume Up, 237 I do not know, this is the same as Hex ED.

OEMs should make special note of the VK key ranges reserved for specific OEM use: 2A, DB–E4, E6, and E9–F5.

Maybe 92 is Back?
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Thanks,

unfortunately neither of 92 or 237 are related to the hardware buttons - or at least they dont unlock - strange since you see them in the log. What could be the reason - it seems illogic ?

You wrote; The right area pressing can not do harm, so you have to live with that (it will not unlock by that). but actually thats not what i see. I see that if right area is pressed, the screen is actually unlocked - i can use touch panel and that is a problem cause screen is active in the pocket. Any solution ?

If i activate HTC lock API in section "keyboard"

and check double touch panel lock=1 - the device suddently CAN lock. Whats the explanation for it working only if i choose HTC lock API ?

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] gjeremie:
request

hi

First, thanks for your soft, I use it since the start and It is very useful.

But i have only one request : allow more customization on battclock

at present I use a 480*52 black rectangle with the time and date for battlock config (which hide my topbar and inform me the phone is locked).

and for better look i would use a picture (with a padlock or other) instead of my black rectangle

It its related to this item which is in the todo list :

-Add notification icon possibility instead of BattClock

Do you think this is possible?

thanks
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Some people have a problem with the standard Windows Mobile TouchPanel lock. But newer HTC phones have another possibility to lock the phone, HTCLOCKAPI=1. This is where TouchLockPro started with, but has the disadvantage it will only work on HTC type of phones and also some features will not work, like unlocking via keys.

But for HTC phones this HTCLockAPI = 1 is a reliable way of locking, all keys are locked. And you can still pick up the phone with Bluetooth, without unlocking. Wen you want to unlock, you need te other sensors, like light sensor, Stylus sensor, keyborad sensor or GSensor. Looks like this on is the better choice on your phone.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I did loose a bit of interest in adding features, because I do this in my free time, and although I get now and then donations (thanks for those who support me :)), I now concentrate on making the current version better.

So I am thinking about keep supporting a FREE version and a trial/shareware version, where I will add new features. For people who did donate, that will be also free. Others may register, after a trial period. So maybe that will keep me going on....introducing new features. But I am not sure yet, if I really want to go into that route....
[Touch Diamond, MDA Compact IV Themes and Apps] stefanjadex:
Problem using wired headset

First I want to thank to ZuinigeRijder for this very good program. :)

:confused: I have a problem using TLP 2.7.3:

I frequently use the wired headset on my Touch HD and I discovered that I cannot answer calls using the button of the headset. The only command accepted is the long-press of its button - launch the Voice Dial application. :confused:

If I close TLP, I can answer calls by pressing the headset button.

So, I suppose that even I am not making a right setting of TLP, even the software is not detecting my wired headset.

Does anybody have the same problem like me and know the answer?

Thank you in advance for your kind help,

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

with the limitations tha tyou described above i choose unlock with G sensor and stylus. But there is a bug unfortunately - would be great if you have time to look at this: eventhough i chose to lock the hardware keys too (by not tickinc "Lock touch panel only" in "other settings" - i can sometimes close a call by pressing the end button, further sometimes the home button is active

Any solution ?

thanks

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] Cobaltikus:
http://www.codeguru.com/cpp/g-m/multimedia/article.php/c1569/

If you scroll down about half way down the page there is a link labeled "Download demo project - 15 KB" which will give you "volume_manipulation.zip"

I just now found that so I'm not sure if it is exactly what you would need but it looks promising.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

i tested again the result is: even with DTP=1 the area is touch sensitive it appears - the screen awakes (is lid up) but the screen is still locked it seems. EDIT: it appears not only to be the small right area but any area in the top area causes this. I have attached a log file

Can i make some setting that the screen is now woken up again when touching it ?

Should i check in the registry or some ini setting file to check if the settings entered via the GUI og TLP is actually stored ?

thanks

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Normally, with HTCLOCKAPI = 1, it would lock panel and keys already. I think the combo with DoubleTouchPanelLock = 1 gives a problem with your device. So I advise to set DoubleTouchPanelLock = 0, then your phone should be locked.

You cannot unlock via the TouchPanel, because it is locked. So you need to unlock via the other available sensors, like the light sensor. I see in the logging that the light sensor is working.

I also thought you used Bluetooth, so I would expect you enable detection, so you can still answer via bluetooth.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked at the source code and it looks this example is not specifically meant for Windows Mobile.

I found the following code:

int WINAPI WinMain( HINSTANCE hInstance,
HINSTANCE hPrevInstance,
LPTSTR lpCmdLine,
int nCmdShow)
{
unsigned long iStereoVol, iLeftVol;//, iRightVol;

// get current volume
waveOutGetVolume(0, &iStereoVol);
iLeftVol = iStereoVol & 0xFFFF;
//iRightVol = (iStereoVol & 0xFFFF0000) >> 16;

// increase the volume value
iLeftVol += 0x1000;
if (iLeftVol > 0xFFFF) iLeftVol = 0xFFFF;
iStereoVol = iLeftVol | (iLeftVol << 16);

// set mixer to new volume
waveOutSetVolume(0, iStereoVol);

return 0;
}

I do not know if this will raise the volume for incoming call or the general system volume, because it assumes there is only one sound device. I did not yet try myself, but maybe you can try something ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
With HTCLOCKAPI = 1 this would not be possible. So I advice not to set DoubleTouchPanelLock = 1.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Only answering with bluetooth is currently possible, in combination with HTCLockAPI = 1.

The wired headset is just sending the same keys as the Answer/Reject button. So they will be blocked. And with HTCLockAPI = 0, you can unlock the answer/reject buttons, but then you can also accidently press those buttons on the phone itself, when in your pocket.

I cannot distinguish between which keys are pressed, the ones on the wired headset or the ones on the phone.

See also this post.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

no that do unfortunately not make any difference - i just tested it. Hardware Keys are still not locked.

Further i think you misunderstand the problem about the touch screen awakening during receiving a call, because this is what happends:

when locked and a call is coming in, the screen awakes briefly and turns off again (the screen is locked during this though ) but if i unintentionally touch the upper part of the screen (to the left and ABOVE the "normal screen - i mean next to the HTC logo - which i thought was not part of the touch screen - seee attached picture) ) during call (the screen is supposed to be black and locked) the screen suddently turns on again (and i of course dont want that during a call) - although the screen is still locked. Something fishy is going on here with TLP and HTC touch Pro 2 - what is wrong and can you fix it ?

also, when enabled "detect bluetooth" the only thing that happends is that the signal is send to BT but i cant pick up the call, ie it doesnt make any difference it detect bluetooth is checked or not. (I can pick up call via BT only if "htclockapi" is checked - but then checking detect BT does not make any difference)

Its correct - i use BT

Do you need me to upload any logging ?

thanks

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, apparently, Touch Pro 2 has, besides the zoombar also another sensitive area on the upper left above the screen :confused: It is the first time I hear this.

Yes, Bluetooth pickup is only working with HTCLockAPI = 1. DetectBluetooth is about not unlocking in some circumstances, when Bluetooth is active.

However, I think the problem is maybe related to the specific settings you have, especially your attempt to have the screen off after call ended.

I see you have configured:

CommandCallEnded: "!SUSPEND"

Can you check if the same problem persists, without this setting?

And before doing that, can you delete TouchLockPro.log.txt, so I see only the new relevant loggingpart :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

attached log. It did not make any difference. This may help you analyse: if i slide out the slider keyboard - and i suspend the screen - then th euppe rleft part of the screen do NOT awake the screen. But if the slider is is - then it does. Strange. I looked to see if it was the upper part of the phone that presses the keys on the slider down, but that is not the case - it really appears that this is because of touching the screen.

Could it make any difference regarding my other settings - eg the time settings etc ?

Have you heard from other pro 2 users if TLP works like that with their device ?

BTW; why is there in the log messages that CreateProcess failed: 2 and Invalid remarks ? What do these mean?

I really hope there is a fix for this somehow - as i really need complete lock of phone during a call.

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I know TouchLockPro is working for Touch Pro 2 users. Very weird, also that with the slider out it does not react. I hope that other people with a Touch Pro 2 can check too if they have the same behaviour.

The CreateProcess failed is probably trying to start TouchLockAction twice (pressing twice the BattCLock?)

The InvalidateClock is about refreshing the BattClock, so that is normal behaviour. The time setting cannot cause the mentioned problems.

I see the logging, that during a call there is a Suspend action, with the effect that TouchLockPro is unlocking at that moment. And this is due to the fact that you configured: SuspendOnBacklightOff = 1.

So you can try (again) without the default setting SuspendOnBacklightOff = 0. Hope this solves your problem.

Another possibility would be to introduce a new setting, not to unlock when bluetooth is active. But than you can only answer/reject calls and nothing else.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi again

i didnt even press the Battclock once so that cant be that.

I tried to set the SuspendOnBacklightOff = 0 (ie uncheck it) i can still easily wake up the screen by touching the left part of the screen above the ordinary screen - ie it didnt make a difference. This applies ONLY during calls. I tried to disable TLP - and here again i can wake up the screen when touching this part of the screen - but ONLY during calls. I have attached the log - does that show something new ?

Have you tried contacting another pro 2 user making him test if he can awake the screen during call the same way?

Could you specify what settings would be optimal for me if i only want to lock screen and hardware buttons during call ? I will the try to set all these - that workes for other pro 2 users as you mention - to eliminate causes

You wrote; "Another possibility would be to introduce a new setting, not to unlock when bluetooth is active. But than you can only answer/reject calls and nothing else."

but that would be fine, because if locked i can unlock simply by eg tilting the device (using G sensor), and i would hav eassumed that this was already the case - user would want lock to stay locked untill eithe ruser decides otherwise or eg the light sensor interacts to unlock - is it not like this already today ?

PS the HW buttons occasionally responds on pressing - making it possible to end call during call

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
What I think, is that the suspend is giving the problems in your case.

I see you have also configured:

SuspendTimeOutPowerOn: 4000

CommandCallEnded: "!suspend"

When TouchLockPro issues the suspend call, it also unlocks the device, because otherwise, in a deep sleep, you cannot unlock the phone via the power button (e.g. with HTCLockAPI = 1).

21:20:23 226417410 POWER_ON_REQUEST

21:20:23 226417410 ==========================DisableInput()==============================

...

21:20:27 226417410 ============================Suspend=================================

=======================EnableHardwareKeyInput()============================

Can you try with the settings:

SuspendTimeOutPowerOn: 60000

CommandCallEnded:

I still hope Touch Pro 2 users react, if they have the same problem.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
hi

Thanks for hanging in here - i think you solved one of the issues this time,

I have attached the log again with your specification ( i have set time to 40 sec instead of 60 as suggested though - increasing from 4 sec to 40 sec seems to solve the problem with HW buttons locked - now they appear to be locked). EDIT: they are indeed locked as long as windows mobile is in the phase where the display is dimmed (set to 30 sec) when windows shut off the screen after 1 minute (the screen is black) then pressing the HW buttons suddenly lights up the buttons (they did not do that in the dim period they were kept dark when pressing). When buttons light up they sometimes are active. Does that tell us anything of the reasons for this behaviour?

Still the strange phenomenon about touching left part left of the HTC logo - light up the screen during call. Strange. Is it a "secret" touchable part of the screen - if so can it be locked ?

Any solution to this ?

You wrote; "Another possibility would be to introduce a new setting, not to unlock when bluetooth is active. But than you can only answer/reject calls and nothing else."

but that would be fine - is it not supposed to be like this already today ?

thanks

regards Nolan
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, the logging confirms what I suspected. When TouchLockPro suspends, it enables the hardware input. And when the phone is not going into a deep sleep (e.g. because still inside a call), the mentioned problems occur.

21:34:40 171330518 =========================POWER_STATE_ON============================

21:34:40 171330518 SetCallStatus(CALL_INCOMING): 0

21:34:40 -1921159578 ==========================DisableInput()==============================

...

21:35:20 -1921159578 ============================Suspend=================================

21:35:20 171330518 ========================POWER_STATE_IDLE: SCREEN OFF==========================

21:35:20 171330518 resumeSeconds SCREEN_OFF: 164120

21:35:20 171330518 PowerOffRequest()

21:35:20 -1921159578 ClockWndProc(WM_TIMER): 7

21:35:20 -1921159578 POWER_OFF_REQUEST

21:35:20 -1921159578 =======================EnableHardwareKeyInput()============================

21:35:20 171330518 PBT_TRANSITION POWER_STATE_USERIDLE

21:35:20 -1921159578 ===== ClockWndProc(WM_TIMER) power OFF change ======

So it looks like TouchLockPro should not enable the hardware key input at screen off or power state useridle......

I need to investigate this more, if I can enable the input only at real power off. I have had a setting EnableInputAtSuspend, so maybe I need to reintroduce this one, e.g. in combination with bluetooth detect.

I do not know of an API to prevent this. So maybe it is also a capacaitive sensor, like the Zoombar. But also that one I cannot control, because HTC did not give this API to the community......

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.

So in principle this is not needed with your settings, because the effect is the same (e.g. you did set UnlockWhenConnected=0). The idea is that you can set settings like UnlockWhenConnected=1, and only when bluetooth is active and set, those settings are not taken into account. This is handy for people not always use the phone via bluetooth.

Currently the bluetooth detection is thus limited, it will ignore, when active:

- setting UnlockWhenConnected=1

- not unlock by light sensor (when DetectBluetoothLightUnlock = 0)

- not execute !UNLOCK commands coupled to TAPI changes
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
Hi

ok were getting closer - i will wait untill you have had the time to investigate further - looking forward to your results ;-)

PS it would be very interesting to hera from other pro 2 users about the strange thing with screen wake up touching left of logo

Thnaks

regards nolan
[Touch Diamond, MDA Compact IV Themes and Apps] shagratt:
BUG REPORT: On Touch HD (with wm6.5 from Dutty v14) if I set it to show battery in % it show the correct value (half battery rightnow) but when i choose stripe, it shows always the full stripe as if battery is at 100% :(

FEATURE REQUEST: Instead of choosing date / clock / bat. allow a custom text to be shown: so users can type what they want and variables get replaced by its value

default will be something like: %d\n%b (that means %d = date ,\n = new line, %b = batery)... With this method not only allow greater customization but add lot of use to the stripe cause on high resolution displays a small stripe of 8 pixels can show lots of text and information ... I can set time, date, battery and more in just that line.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is not exactly a bug, but a feature request, which I am busy with implementing, including other wishes. So be patient.....

Also here there are some wishes already have been asked, like the format of date, time, etc. I will take your request into account and see if I can implement this too. The problem is that it also gets more complicated/technical to configure, but on the other hand you have more freedom.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro version 2.7.4

I just uploaded TouchLockPro version 2.7.4, which fixes some bugs. Hope I did not introduce new ones :cool:

Unfortunately a serious problem has been found. Do not use this version but 2.7.5.
[Touch Diamond, MDA Compact IV Themes and Apps] nolannolan:
hi

sounds great

i will test and see if it solved some of the touch pro 2 problems

ZuinigeRijder which settings with the new version would you recommend to solve my issues?

An uninstall is not needed to install new version - it can be installed over the previous version ?

regards nolan