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

Just a bit cumbersome, I updated all the resx file. Please check it.;)

PS

My mobile phone is HTC Touch Diamond.

1. I set beep lock/unlock is 1, but I can't hear any voice.

2. Sometimes TLP abnormal: can not be locked or touchpanel cannot be locked.

Sometimes TLP is ok after reboot mobile.
[Touch Diamond, MDA Compact IV Themes and Apps] surfnet:
Hi,

I just started using touchlockpro, and it is great!;).. I have one small issue,

When I lock the screen and put it in pocket .. and bring it out again, it is in landscape mode. When I locked it, it was in portrait mode.

Is there a way to turn off screen rotation when the phone is locked?

thanks!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
You can use MyMobiler, so you can copy the command from the Settings html pages on your desktop and paste them in your phone.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparently you have another program active which does the screen rotation. I cannot stop that program doing that.......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
For 1. You need to enable sounds on your phone.

Alternatively you can choose vibrate.

For 2. If another program use the same hooking (touchpanel or keyboard), then this is indeed possible. I need to enter my SIM pin after boot/reset, before TouchLockPro becomes active. You can use HTCLockAPI = 1, but then you miss some features.

Thanks for the translation updates. I made it easier for people providing/updating translations. See my next post.
[Touch Diamond, MDA Compact IV Themes and Apps] tcc13:
Wow, thanks ZuinigeRijder. :)

Does TLP also allow other apps to unlock it (i.e. G-Alarm)?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Translations made easier: Excel spreadsheet

Because providing translations was cumbersome, including updates, I made an alternative.

Now all texts and languages are in one Excel spreadsheet, see here.

From there one I can generate back the language resx files :)

I hope people get inspired and update/add their language :D

This is the list of languages fully translated:

Chinese (Simplified)

Chinese (Traditional)

Dutch

Russian

This is the list of languages almost fully translated (not up-to-date):

Norwegian

Italian

This is the list of languages where only the TouchLockAction screen is translated:

Arabic

Bulgarian

Czech

Danish

German

Greek

Spanish

Finnish

French

Hebrew

Hindi

Croatian

Hungarian

Indonesian

Japanese

Korean

Polish

Portuguese

Romanian

Slovak

Slovenian

Serbian

Swedish

Thai

Turkish

Ukrainian

Vietnamese

Hope people take the time to provide translations now :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
G-Alarm does support TouchLockPro, so it unlocks TouchLockPro when the alarm goes off. However, people reported, when snoozing and the alarm goes off again, G-Alarm does not unlock TouchLockPro anymore. Apparently G-Alarm does only unlocking the first time :(

But if you put your phone on a place where no object is near (face up), it will also unlock by the proximity sensor, so you are not dependent of the other tool for unlocking :)
[Touch Diamond, MDA Compact IV Themes and Apps] surfnet:
double post.. sorry
[Touch Diamond, MDA Compact IV Themes and Apps] zhongzw:
That's great!

I have checked the translations xls file again and fixed "CHS" "CHT" a little lack.

Look forward for the new version!
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
Hi,

i have an issue:

I didn´t set up incalltweak (all fields empty) - i only have some settings in proximity-section.

If i get a call and speak with the other person, display dims and device will not lock. This is normal behaviour of HD2.

If i make a call and the call is connected, the same like above.

BUT: If i want to make a call, and while the phone is connecting but connection isn´t established yet and i put the phone to my head, then phone screen dims AND phone is locked. If i remove from my head, phone unlocks und screen goes on. But now when i´m speaking with the other person, phone won´t dim anymore. Screen stays still on - no proximity support anymore when covering the sensor.

On next call, all is working regularly (except the last situation, this behaviour appears allways).

Any idea?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I think that it will unlock, and because it is not yet connected, it disables the Proximity sensor. You can enable debug logging, reproduce the scenario and post the debug log file \TouchLockPro.log.txt. Note the exact times for the scenario you test, so I can better find the problem.
[Touch Diamond, MDA Compact IV Themes and Apps] vityea:
I'm new to this. I used HTC Touch Pro2. Now my phone is locked which I have configued with GSensor. I didn't change anything beside tick two option then go back to index and press lock.

I don't know how to unlock. Please Help!
[Touch Diamond, MDA Compact IV Themes and Apps] aadadams:
Pulling the stylus or opening the keyboard may be set to unlock. Try those to get back in a adjust your settings appropriately.
[Touch Diamond, MDA Compact IV Themes and Apps] vityea:
can't do anything. Have to remove the battery, restart and uninstall.
[Touch Diamond, MDA Compact IV Themes and Apps] JimSmith94:
I haven't noticed this mentioned before, but here is what I'm seeing with my Sprint Touch Pro. It spends most of its life in my desktop cradle, connected to my PC with MyMobiler.

Even when it is fully charged, the taskbar shows the tilde as if it is still charging (100~) instead of fully charged (100%).

Lately, perhaps since 2.12.1 but I'm not positive, sometimes while in the cradle, I see the percentage dropping on the phone, as if has been disconnected, but the charging indicator is still there (47~). If I unplug it from the cradle, the phone immediately shows fully charged (100%) and shows charging (100~) when I plug it back in.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Normally it should unlock when taking stylus out.

However, there are some settings which may freeze your phone, like DoubleTouchPanel lock. So I assume that was the case.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The tilde will be shown, when not on battery power, regardless if it is charging yes or no.

The second observation could be that the charger stops charging? I do not know, I just show the values the battery driver is reporting. So maybe those are not correct :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] redzone321:
Hello i am useing an omina 2 and lock yoru lock screen but have a big problem.

I cannot get the light sensor/gsensor to work. It was working at one point in the past but lost the version i used and dl the newest one.

I installed samsung SDK Pro 2.1 first restart then install TLP but i always get a reading of 0/1/-1 on the light sensor page.

how do i tell if its recognizing my deviece proporly?

I will post a bug log if needed.

Thanks!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Do you have Windows Mobile 6.1? Then you should install:

smi_wm_pro_sdk_redist_1_2_1.cab with Windows Mobile Pro 6.1

Do you have Windows Mobile 6.5? Then you should install:

smi_wm_pro_sdk_redist_2_1_0.cab with Windows Mobile Pro 6.5

If you did install the correct version, you can enable debug logging and restart TouchLockPro and post the log file \TouchLockPro.log.txt, maybe that goves me a clue......
[Touch Diamond, MDA Compact IV Themes and Apps] redzone321:
EDIT i lied it stopped working again. plus now for some reason my music stops when i lock my phone. this is so odd. ill include another log file soon. arg seems soo sparadic. sometimes its fine sometimes not!

ok no idea how i fixed it but light sensor works now. here is the log anyways
[Touch Diamond, MDA Compact IV Themes and Apps] neverland13:
I notice something strange - I'm using TouchLockPro and spb mobile shell with Vostradamus. When i upgrade to Vostrdamus 4.x TouchLockPro it stop locking the screen. When i downgrade to Vostradamus 3.5 it works again.
[Touch Diamond, MDA Compact IV Themes and Apps] zhongzw:
update

update

update

:)
[Touch Diamond, MDA Compact IV Themes and Apps] d4v0r:
Hi! Can anyone help me with this app? I want to set a simple rule, but whatever I do, I don't get consistent behaviour. So I'd rather have someone give me settings from scratch, than posting my log and trying to fix my settings.

I want everything to remain stock, except when there's an incoming call and phone is in the pocket. I want only screen locked until the phone gets out of the pocket (i.e. proximity is not near).

Thank you in advance. BTW, I have HD2 (Leo).
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is the log file TouchLockAction.log.txt, the interesting log file is TouchLockPro.log.txt.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Apparently the new version uses the same hooking method as TouchLockPro. The only way is then to use HTCLockAPI = 1, if you have a HTC device :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
New version with more/updated translations

Just uploaded the new version with more translations.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
My first guess would be the default settings (reset to defaults in About screen) and with changed settings:

AutoLockOnPowerOn = 0

LockWhenIncoming = 1

UseProximity = 1
[Touch Diamond, MDA Compact IV Themes and Apps] d4v0r:
Thanks for reply, but I'm afraid it's not that simple. Anyway, I've figured out what's making a problem. When AutoLockOnPowerOn is checked, everything works fine, but when I turn it off, and turn on LockWhenIncoming, screen stays locked on incoming call. Maybe it's the way it's supposed to be, maybe it's wrong order/override of instructions, or I don't know how to use it :)

The easiest solution of course would be to use AutoLockOnPowerOn (which is great because saves battery) but it induces lag in standard lock screen, even with Proximity Sensor Time reduced.

Now that my problem is more specified, I hope you can help me.

I've attached the log with the following procedure:

lock, receive call with hand over proximity sensor, remove hand, ignore call (all ok)

turn off AutoLockOnPowerOn

lock, receive call with NOTHING OVER proximity sensor > screen stays locked, have to soft reset
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Lock, receive call with NOTHING OVER proximity sensor > screen stays locked, have to soft reset

Let see what happened in the logging:

2010-03-25 22:21:37 998095866 SetProximityAccept(false)

2010-03-25 22:21:37 998095866 ExecuteRequest(): !PROXIMITYDISABLE

...

2010-03-25 22:21:39 -172757050 ========================POWER_STATE_UNATTENDED====================

2010-03-25 22:21:39 -172757050 SetScreenOn(false)

...

2010-03-25 22:21:39 998095866 SetPowerStateOn(false)

....

2010-03-25 22:21:41 -172757050 ========================POWER_STATE_SUSPEND==========================

2010-03-25 22:21:41 -172757050 SetScreenOn(false)

...

2010-03-25 22:21:51 -172757050 ======================== Change from screen OFF to screen ON ==============

2010-03-25 22:21:51 -172757050 SetScreenOn(true)

....

010-03-25 22:21:51 -172757050 SetCallStatus(CALL_INCOMING): 0

2010-03-25 22:21:51 -172757050 NotificationCallStatusIncoming()

2010-03-25 22:21:51 998095866 ClockWndProc(WM_TIMER): 11

2010-03-25 22:21:51 998095866 NOTIFY_SCREEN_ON

....

010-03-25 22:21:51 998095866 NOTIFY_CALLSTATUS_INCOMING

2010-03-25 22:21:51 998095866 SetLocked()

2010-03-25 22:21:51 998095866 SetLockMode(true)

2010-03-25 22:21:51 998095866 Lock(true)

2010-03-25 22:21:51 998095866 ==================================Lock=============================(true)

2010-03-25 22:21:51 998095866 SetLocked(true)

....

2010-03-25 22:21:51 998095866 SetPowerStateOn(true)

I checked my code and the setting:

Lock (CmdLock = "!PROXIMITYACCEPT")

is only executed when power state is on :mad:

It looks like this has to be outside the powerstateon check....so the Proxmity commands are rejected. Hmmmm.

I removed this powerstateon check. You can try the test version in this attachment.
[Touch Diamond, MDA Compact IV Themes and Apps] d4v0r:
Thank you for quick check and test version! Now it works fine. Can I use this version, or was it just quick and dirty trick for testing and you have to code it differently? I'll report if I notice any issues, or hopefully confirm that all is good.

And one question regarding power consumption. Is proximity sensor polled all the time while !PROXIMITYACCEPT, or just on incoming call? Are my settings in the log the most power efficiant for the task I want?

Thanks again!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The fix is not a quick and dirty hack. However, I test myself too for no side-effects, for publishing as official version. For your settings it does not matter anyway, because you disabled most of the sensors.

The Proximity polling is not done by TouchLockPro, but by HTC. But I expect this will cost almost no power. And when in a deep sleep, the sensor is not running too. The sensor power consumption is neglectable for all sensors, in deep sleep they do nothing and when the screen is on, the LED and CPU is the battery eater....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.12.7

Testing did not show side-effects, so I made 2.12.7 available as official version
[Touch Diamond, MDA Compact IV Themes and Apps] drjat:
just an openion

respected Sir

May I say that this fantastic and awsome application is getting more and more complicated especially since introduction of proxmity sensor functions. I hope it does not loose its original ethos of being a simple, efficient, low memory using and low battery consuming application.

Kindly disregard my comment if I am wrong in thinking on these lines. I hope this comment wont upset anyone but if it does........then apologies in advance. This is certainly NOT my intention to upset anyone. i am a noob anyway!

Cheers
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
No problem. I always take care that people can configure their needs. The side effect is indeed that you can configure a lot and I can imagine that scares people. But the default settings are chosen sensible and even your phone type is automatically detected.

Anyway, if you do not want the Proximity sensor, just configure:

Use Proximity (UseProximity = 0)

The CPU and memory usage is kept very low, despite all the sensors coded in. And also there should be no effect on battery life (probably only positive effects though). Even with all sensors enabled, you will see low CPU, memory and no battery drainage.

Often other programs do not let you tweak as much as TouchLockPro and only have simpler options. I could also take that approach, but it will not make TouchLockPro smaller or more efficient. I think the opposite, for people wanting to control all the latest CPU cycles and battery usage.

But if I go the wrong way, I am sure people will complain. You did now, but I do not see directly why this makes TouchLockPro more complicated (than it was already). Although there are still some wishes on the wish list, I carefully try to choose the pieces which best fit in the original concept.

Hope that gives you an answer.

The long answer does not mean I am upset :rolleyes:

I think it is good to listen to your users. But I know also I can never make it right for everybody.
[Touch Diamond, MDA Compact IV Themes and Apps] vadim_bogaiskov:
Updated Russian translation
[Touch Diamond, MDA Compact IV Themes and Apps] madbird:
hi,

i still try to find out why the hd2 is blanking the screen, once tlp has loked/unlocked the phone. after a lot of testing i came to the point that it's not tlp that blanks the screen accidently.

its more likely that when tlp accesses the psensor once, the hd2 is starting also its buildin programm to blank the screen on psensor activity. wich is normaly used only when a call is in progress.

i disabled everything except:

proximitysensor->on,time=500/near=!LOCKSCREEN/Not Near=!UNLOCK

BattClock->BattClock/Clickable/LockIndicator

other settings->LogDebug/UnlockOnACpower/VibrateLock=1/SuspendTimeOutPowerOn=30000

if i cover the psensor for less then 500ms tlp takes no action, but the screen goes off and on as i cover/uncover the sensor. but it is not locking. i think that is what the programm does that is build into the hd2 rom to blank the screen when there is a call in progress.

maybe these guys at htc choose the easy way, and linked the start of the 'blank screen incall' programm to the enabling/disabling of the psensor.

i hope the log file is helpful. regards mad
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Exidler has provided a way to disable AutoScreenOff for HD2. I do not know if it works (I do not have a HD2), but it is worth a try. Because you can control via TouchLockPro when you want screen off, I could make a test version (when configured HD2) which does the trick of the above thread and this code:

bool Hd2ProxSensor::SetAutoScreenOffInternal(bool autoScreenOffWhenProximityDetected)
{
DEBUGMSG(1, (L"Hd2ProxSensor: SetAutoScreenOffInternal(%d)\n", (DWORD)autoScreenOffWhenProximityDetected));
HANDLE hLedDevice = CreateFile(L"LED1:",
GENERIC_READ | GENERIC_WRITE, FILE_SHARE_READ | FILE_SHARE_WRITE, NULL, OPEN_EXISTING, 0, NULL);
if (!hLedDevice || hLedDevice == INVALID_HANDLE_VALUE)
return false;

LEDMGR_CONTROLL ctl;
ctl.p1 = 0; // bit number
ctl.p2 = (autoScreenOffWhenProximityDetected ? 1 : 2); // 2 for set bit else - clear bit

DWORD dwRet;
BOOL bResult = DeviceIoControl(hLedDevice, IOCTL_LEDMGR_SCREENOFF_DISABLEDLED_IOCTL, &ctl, sizeof(ctl),
NULL, 0, &dwRet, NULL);

CloseHandle(hLedDevice);

return (bResult != FALSE);
}
[Touch Diamond, MDA Compact IV Themes and Apps] JimSmith94:
Regarding this point, I use the Batti application to also monitor my battery. When fully charged and in the cradle, its indicator is solid green and stationary. Also when fully charged and in the cradle, the front button on my phone is solidly lit and doesn't move. Yet, the battery indicator shows a constantly decreasing number, i.e. 72~, 71~, 70~, etc. As a rough guess, it goes down one number per minute or two.

Since two other indicators show that the battery is fully charged, I think you must be pulling the value from a different battery driver.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
There are 2 mechanisms in TouchLockPro for getting the battery percentage:

1. RequestPowerNotifications(m_PowerMsgQueue, PBT_RESUME|PBT_TRANSITION|PBT_POWERINFOCHANGE)

2. using GetSystemPowerStatusEx

Normally, 1. is the notification of Windows Mobile, which is shown. And to prevent polling the battery driver (option 2.) I do this only when 1. has not occurred for some time (3 minutes), to prevent unneeded battery drainage.

So I suspect that the Windows Mobile callback is giving the wrong information. BattClock is not using 1. approach, but solely relies on 2. So you can check if BattClock gives the correct value in your scenario. If that is the case, I can remove the 1. method in TouchLockPro and need to rely on 2 ;)

Can you check?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro 2.12.8 with updated Russian translations

Thanks for the update. I uploaded 2.12.8.
[Touch Diamond, MDA Compact IV Themes and Apps] y2ksatan:
look like so cool
[Touch Diamond, MDA Compact IV Themes and Apps] JimSmith94:
You want me to uninstall TouchLockPro and install BattClock to see if the behavior is different, correct? I will do that and let you know.
[Touch Diamond, MDA Compact IV Themes and Apps] nyadmin:
I looked through this thread but I don't think this was mentioned. If it was, it was mentioned in a way that I don't see it.

I have a Sprint Touch Pro with LockPro 1.5. I have a problem when I power off the phone and power the phone back on.

When I power off the phone and immediately try to power on the phone, there's no problem.

When I power off the phone and wait 3-4 seconds, I can't turn the phone back on for a good 20-30 seconds.

Is this normal?
[Touch Diamond, MDA Compact IV Themes and Apps] djmvt:
As quoted from "zuinigerijder":

This has to do with the locking of the hardware keys. It can take 20 seconds or more, before the power button reacts. Unfortunately this is related to the HTC locking API I use, so I did not find a way to avoid this HTC behaviour.

BTW zuinigerijder: bedankt voor dit programma, als ik je kan helpen met testen dan laat t maar weten ;)

dj MvT
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
Strange problem:

(If this isnt to do with the lock then i appologise and ill edit this out)

I have recently changed rom (yesterday) and i have noticed that touchlock is locking itself during phone calls.

for example, ill get a call and answer with the hardware keys (all the time) and the pixel i have in the top corner to tell me the lock is enabled, but during the call the device vibrates and locks(?) when the screen goes off. but when i actually end the call my device is unlocked (no pixel), and it relocks itself.

Is there anything i can do to give you more info?

Secondly, and im really sorry for this, i will ask the dumb (off topic) question, i know there is a reg setting out there or some way to stop my screen going off during a call, can someone point me in the right direction.

Thanks for help

@ZuinigeRijder - about the action screen, when is the alpha? jus so i know how long i have for these icons
[Touch Diamond, MDA Compact IV Themes and Apps] Pietje_1985:
Hi Mystic!:)

about your offtopic question..I can help you with a CAB file which will avoid your screen for going off:D it's working perfectly;) I don't know the exact reg key...:( sorry...
[Touch Diamond, MDA Compact IV Themes and Apps] nyadmin:
I wasn't sure that was the same issue but ok. Thanks.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
*already answered just above*
[Touch Diamond, MDA Compact IV Themes and Apps] 4D3:
Thanks for the cab, attached is a single reg entry that does the same. (better for sashimi flash)

Oh YEAH - v1.6 is out!! WOOT!!
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
This is because the screen goes off and the settings are that it locks then.

In version 1.5 I did a unlock of the hardware keys, to avoid the problems people having to get the phone react on the Power On presses. Apparently this is not helping much. In version 1.6 I do not enable the hardware keys anymore when the screen goes off.

I do not think there is a Registry key, but you can do that programmatically (keeping the device in a minimum state). TouchLockPro does this also to capture power off events and then releases this minimum requirement. I could make a setting/button to keep it in the so called UNATTENDED mode (screen off, but not suspend).

Version 1.6 with the action screen is just out, so no ALPHA version, a production version with only the features implemented till now :)