yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] AboveTheBULL:
Ah, I see. I was overwhelmed when looking at the log before (LOL), but now I understand. I will make a much bigger log and see what I can find in there...

Ah, so is there a way HTCLockAPI can be used only during an incoming call when bluetooth is on? The way it is now, if "HTCLockAPIWhenBluetoothActive" is set to "on", then HTCLockAPI engages *everytime* bluetooth is enabled, but not just during an incoming call. This means if I turn off screen with power button, then try to turn it back on myself, I cannot with power button. I also miss out on other TLP features that HTCLockAPI kills.

So... is there a way to make a setting to only engage HTCLockAPI during an incoming call if bluetooth is active?

Yes, I tried DoubleTouchPanelLock=1 and I get the evil freezing. I wish I had an extra TP2 -- I would send it to you and let you work with it to iron out the current incompatibilities. But alas, I only have this one!

Maybe there's a way to disable TLP intercepting Zoombar commands for unlocking? Turning off all settings in Nav Bar menu does not do this. Or am I overlooking some setting?

Finally, I've enclosed my new log file. What I did in it was suspend/lock the phone with the power button, then a couple moments later, turn on screen with power button. Then I used swipes to zoom bar to unlock, even though Nav Bar entries in TLP settings are disabled. I did it this way 4 or 5 times to be sure to get consistent results...

Then, I left the phone awake and unlocked, and called it with my house phone. Pressing bluetooth button answered phone perfectly. Then I try it with phone suspended. Bluetooth button sends audio to ear, but I use finger to slide on-screen WinMo slider and answer phone. Then finally, I try with phone suspended and bluetooth button sends audio to ear. Pressing again hangs up still-ringing phone. And since it's still locked, I use zoom bar swipes again to unlock screen.

Now we have much more info, I hope.
[Touch Diamond, MDA Compact IV Themes and Apps] khaytsus:
Does anyone else have trouble with the automatic speakerphone capabilities on the Touch Pro 2/Tilt 2? I have to unlock TouchLockPro, then it'll automatically go on speakerphone when I place the phone face-down.

At first I thought this was a problem when using the G-Sensor portion but I disabled that and the problem remains.
[Touch Diamond, MDA Compact IV Themes and Apps] Jesse Buck:
I do have those settings. Here is the log file you requested. Thanks for the awesome app and great support.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ok, I see the problem. The default setting is (when you do a reset-to-defaults):

2010-03-09 09:14:24 1328837162 ==DEFAULT VALUE====: !PROXIMITYIGNORE;!PROXIMITYDISABLE

2010-03-09 09:14:24 1328837162 ==OVERRULED VALUE==: !PROXIMITYIGNORE; !PROXIMITYDISABLE

2010-03-09 09:14:24 1328837162 CmdUnlockNoCall: !PROXIMITYIGNORE; !PROXIMITYDISABLE

So your overruled setting contains a space after the ; :mad:

TouchLockPro is lazy and just expects, when multiple commands are used, there are no spaces. The result is that TouchLockPro thinks it is an external command:

2010-03-09 09:14:37 1328837162 Execute(): !PROXIMITYIGNORE; !PROXIMITYDISABLE

2010-03-09 09:14:37 1328837162 SetProximityAccept(false)

2010-03-09 09:14:37 1328837162 ExecuteRequest(): !PROXIMITYDISABLE

2010-03-09 09:14:37 1328837162 PushCommand: !PROXIMITYDISABLE

2010-03-09 09:14:37 1328837162 ClockWndProc(WM_TIMER): 26

2010-03-09 09:14:37 1328837162 PopCommand: !PROXIMITYDISABLE

2010-03-09 09:14:37 1328837162 EXECUTE_REQUEST: !PROXIMITYDISABLE

2010-03-09 09:14:37 1328837162 Execute(): !PROXIMITYDISABLE

2010-03-09 09:14:37 1328837162 CreateProcess failed: 2

2010-03-09 09:14:37 1328837162 CreateProcess command: !PROXIMITYDISABLE

I expect, that when you remove the space, it will work.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Current there is not a setting for that. But I can add that one as setting. I have to see if this is easy to add. In general, are there people who want this behaviour also when no incoming/outgoing call? If that is not the case, I do not need to make a separate setting, but just change the spec.

Because it is part of the TAPI setting, it makes sense to do this only at incoming call.

In the logging I see indeed several times:

2010-03-09 01:09:27 751698426 SetCapacativeGesture(): Capacitive Touch Middle

So it is not unlocked by that.

Then I see:

2010-03-09 01:09:37 751698426 UnlockRequest()

Unfortunately, I did not log the cause of this request, but looking at the code, it must indeed be the ZoomBar unlock:

Currently I do not have a setting to disable the ZoomBar unlock, because I thought the swipe gesture is not something you do by accident.

Then I see the incoming call:

2010-03-09 01:12:03 -326232790 SetCallStatus(CALL_INCOMING): 0

and I see:

2010-03-09 01:12:09 -326232790 NotificationCallStatusConnected()

What puzzles mee, is that I do not see the message in the logging:

SetBluetoothStatus

I see if Bluetooth is active, by examining the registry key changes:

HKLM\\System\\State\\Hardware\\Bluetooth

I see however, in the logging:

2010-03-09 01:11:25 -862754294 BluetoothStateCallback: 8

2010-03-09 01:11:36 -862754294 BluetoothStateCallback: 9

And the bluetooth is only reporting active, when the bluetooth callback gives a value above 9 :eek:

Maybe I miss the logging part that Bluetooth was active (before) and the logging I see is just disabling bluetooth?

I see the hooking of the talk key:

2010-03-09 01:12:49 -326232790 SetCallStatus(CALL_INCOMING): 0

...

2010-03-09 01:12:54 1842443314 LLKeyboardHookCallbackFunction: 114

2010-03-09 01:12:54 1842443314 LLKeyboardHookCallbackFunction hooked: 114

2010-03-09 01:12:54 1842443314 LLKeyboardHookCallbackFunction: 114

2010-03-09 01:12:54 1842443314 LLKeyboardHookCallbackFunction hooked: 114

...

2010-03-09 01:13:00 1842443314 LLKeyboardHookCallbackFunction: 117

2010-03-09 01:13:00 1842443314 LLKeyboardHookCallbackFunction hooked: 117

2010-03-09 01:13:00 1842443314 LLKeyboardHookCallbackFunction: 117

2010-03-09 01:13:00 1842443314 LLKeyboardHookCallbackFunction hooked: 117

117 keys means:

117 = VolumeUp: VK_TVOLUMEUP, 0x75

And then I see call connected:

2010-03-09 01:13:00 -326232790 SetCallStatus(CALL_CONNECTED): 1

The call connected is in the same second of the volume up hooking, so maybe you by accident pressed the volume key while unlocking/answering?

2010-03-09 01:13:40 -326232790 SetCallStatus(CALL_INCOMING): 0

...

2010-03-09 01:13:46 1842443314 LLKeyboardHookCallbackFunction: 114

2010-03-09 01:13:46 1842443314 LLKeyboardHookCallbackFunction hooked: 114

2010-03-09 01:13:46 1842443314 LLKeyboardHookCallbackFunction: 114

2010-03-09 01:13:46 1842443314 LLKeyboardHookCallbackFunction hooked: 114

....

2010-03-09 01:13:53 -326232790 SetCallStatus(CALL_ENDED): 1

So it looks like you need to use HTCLockAPI at incoming call when bluetooth enabled.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
I did some tests.

If i get a call, my hardware keys aren´t locked.

If proximity sensor covered or not, always unlocked.

I checked "unlock on call" and "hardware keys only". Do i have to set both? Is this right? I only want to answer a call by the slider. Hardware keys should be locked always, if i get a call.

Proximity: unlock call = !proximityignore

Are these the right settings?

I did a test with device locked. Proximity covered. Then i got a call. I pressed the power-button of my hd2 twice and the call was dropped.
[Touch Diamond, MDA Compact IV Themes and Apps] La_Globule:
What can I do / check / set on the phone to fix the problem ?

Thanks for your efforts.
[Touch Diamond, MDA Compact IV Themes and Apps] Bib_x:
New issue:

While phone is unlocked and i cover the proximity sensor, phone will not dim the screen.

BUT: If phone is connected with my computer with usb-cable, screen dims while covering proximity sensor. --> when remove usb-cable again, it works like it should do - no screen dim.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I looked at the logging and I do not see something strange.

2010-03-09 14:35:08 2079234814 NOTIFY_CALLSTATUS_INCOMING

....

2010-03-09 14:35:14 2079234814 LLKeyboardHookCallbackFunction hooked: 117

..

010-03-09 14:35:14 2079234814 LLKeyboardHookCallbackFunction hooked: 237

..

2010-03-09 14:35:15 1328736226 SetCallStatus(CALL_CONNECTED): 1

..

2010-03-09 14:35:20 2079234814 LLKeyboardHookCallbackFunction hooked: 115

..

2010-03-09 14:35:33 2079234814 LLKeyboardHookCallbackFunction hooked: 115

I am puzzled about the 237 key hooked (0xED hexadecimal). I cannot find this key in virtual tables. Aha, it is the Home button.

I am curious if InCall lock is working for you?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
It depends. I assume you did mean:

LockWhenIncoming (LockWhenIncoming = 0)

Default it will NOT lock when there is an incoming call, because the default setting AutoLockOnPowerOn = 1 avoids already accidently missed calls. If you do not want the additional behaviour that it will be always locked at an incoming call (even when the phone was still on), overrule this registry key with "LockWhenIncoming = 1"

So it depends about your AutoLockOnPowerOn setting and if the screen was off if you need to check this option.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, I do not know at this moment :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Hmmm, strange at first sight. Can you post a debug log file with this scenario. Maybe, because it does not lock, it does not disable the Proximity sensor :confused:
[Touch Diamond, MDA Compact IV Themes and Apps] Jesse Buck:
Indeed, that was the culprit. You, much like your application, are amazing. Thank you for such excellent guidance.
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
I have installed the InCall lock before, and I remember it worked in the past, perhaps before I used TLP. However, it now does nothing.

Attached is a log with InCall lock. Behavior is the same. It also has the 237 line.
[Touch Diamond, MDA Compact IV Themes and Apps] nila@ufl.edu:
I turned off all other features to try and help isolate it. Right now all I have checked besides the log is

Battclock:

LockIndicator

Stealth

TAPI:

Use TAPI

Detect Bluetooth

HTCLockAPIWhenBluetoothActive

Connected is set to "!screenoff" with no spaces or quotes

Ended is set to "!suspend" with no spaces or quotes

It's pretty hit or miss on the screen turning off after the call ends. 90% of the time the screen goes off right after the call connects, but when the call ends I haven't found a consistent pattern for when it works or doesn't. I've tested incoming and outgoing with bluetooth connected, with the headset, using the touch screen to answer/end or hard keys.

Let me know if there is anything else I can do, thanks.

Nila
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
So I think there is another program using the same keyboard hooking method (in Windows Mobile there can be only one) or it is a bug in your ROM version? Special programs installed? Using Windows Mobile lock too? Which homescreen? Which ROM?
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Looking at the logging, I see that twice the screen goes off and keeps off when a call gets connected. But once I see it going on again:

2010-03-11 11:00:25 -1908997974 NOTIFY_CALLSTATUS_CONNECTED

2010-03-11 11:00:25 -1908997974 Execute(): !screenoff

2010-03-11 11:00:25 -1446806402 HandlePowerNotifications()

2010-03-11 11:00:25 -1446806402 PBT_TRANSITION

2010-03-11 11:00:25 -1446806402 PBT_TRANSITION POWER_STATE_IDLE

2010-03-11 11:00:25 -1446806402 ========================POWER_STATE_IDLE: SCREEN_OFF==========================

2010-03-11 11:00:25 -1446806402 SetScreenOn(false)

2010-03-11 11:00:25 -1446806402 SetBackLightOff(true)

2010-03-11 11:00:25 -1446806402 IsConnectedCall(true)

2010-03-11 11:00:25 -1446806402 resumeSeconds POWER_STATE_BACKLIGHTOFF: 385225

2010-03-11 11:00:25 -1446806402 NotificationBackLightOff()

2010-03-11 11:00:25 -1908997974 ClockWndProc(WM_TIMER): 12

2010-03-11 11:00:25 -1908997974 NOTIFY_BACKLIGHT_OFF

2010-03-11 11:00:25 -1908997974 IsConnectedCall(true)

2010-03-11 11:00:25 -1908997974 IsConnectedCall(true)

2010-03-11 11:00:25 -1908997974 ===== ClockWndProc(WM_TIMER) power ON change ======

2010-03-11 11:00:25 -1446806402 CProximity::HandleProximityPhoneNotification()

2010-03-11 11:00:25 -1446806402 CProximity::HandleProximityPhoneStatus(true)

2010-03-11 11:00:25 -1446806402 SetProximityEnabled(true)

2010-03-11 11:00:25 -1446806402 CProximity::HandleProximityPhoneNotification()

2010-03-11 11:00:25 -1446806402 CProximity::HandleProximityPhoneStatus(true)

2010-03-11 11:00:25 -1446806402 SetProximityEnabled(true)

What I think is, that TouchLockPro is too quick with Screen off and the phone canvas decides to keep the screen on (or reactivates it). It is just a wild guess. You can try to configure !screenoff;!screenoff

Maybe that helps?

Another possibility would be the Proximity sensor, which will wakeup the phone (because there is nothing near).

Although you disabled the Proximity sensor for use with TouchLockPro, this does not mean that other (phone canvas) program is not acting on it. Do you want to use the Proximity sensor for incoming call? You can try !PROXIMITYDISABLE;!SCREENOFF when you do not want it.....
[Touch Diamond, MDA Compact IV Themes and Apps] alex fung:
I cannot guess which program might be. I uninstalled LMT and InCall. The behaviour is the same. The only remaining process related to keyboard is Swype (which I hope I don't need to remove). Do you think it might be the cause?

ROM:

stock 1.48.831.0 (71294)

WWE from HTC HK.

homescreen? I don't know. I am using the original Sense. I didn't install any mods. Manila version says 1.0.19211620.0. I don't know why it calls itself 1.0 instead of 2.5.
[Touch Diamond, MDA Compact IV Themes and Apps] illi:
BattClock

Hi ZR

I think it would be nice if you can add the following to the BattClock as additional optional parameters:

- Date in the format ddmmm

- Day of week in the format: MO TU WE TH FR SA SU

Thanks:)
[Touch Diamond, MDA Compact IV Themes and Apps] victorchen101:
I updated the translations files for Chinese Traditional.:)
[Touch Diamond, MDA Compact IV Themes and Apps] JamesAllen:
Strange

Edit: In "Settings" under NavSensor in the top right, the field says 0.unknown even though use navsensor is selected.

I just upgraded my ROM to the one in my sig from Energy ROM Dec 15th 21xxx Sense 2.1/Titanium. TouchLock was working fine for me on the 2.1 ROM. I could use gestures on the Nav Panel to unlock and lock the device. Since upgrading to the Sense 2.5 ROM the Nav Panel does not respond no matter the settings in TouchLock. I even went back from the most current version to 2.11 thinking that maybe the new Proximity Sensor may be a problem, but the Nav Sensor still does not work. I cannot unlock after power on, cannot lock or unlock when unlocked, nothing involving the Nav Sensor. I think it is the ROM but wanted to check with posters here.
[Touch Diamond, MDA Compact IV Themes and Apps] zsunsun:
No matter what I try, I always come back to the TouchLockPro in the end..

Though newly implemented proximity sensor support is little flaky, I can say this is the best lock software out there..

Keep up the good work
[Touch Diamond, MDA Compact IV Themes and Apps] zhongzw:
Hi ZR,

I updated the translations files for Chinese (Simplified).

:)
[Touch Diamond, MDA Compact IV Themes and Apps] Cir0w:
I used it for a short time. But the %-clock ikon doesn't fit into my custom ROM, so I've uninstalled it..

If someone really want this program translated in Swedish - I can do it for you ;) just PM me..
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
I expect it is the Swype program, because it does keyboard sort of things :eek:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In the next BattClock version it is possible to have a custom date/time format, see this post for a proof of concept.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Looks you found the answer here....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Actually, it does not use an icon but overdraws information.

Changing size and fontSize was not good enough?

Swedish translation would be nice.
[Touch Diamond, MDA Compact IV Themes and Apps] HTC_FUZE:
Hi, ZuinigeRijder:

Thanks for your advice. However, it is not just one image problem. If the phone is at Today screen, I can edit the color to almost match the background color. but when I open an application, the background of the phone changed, then BattClock back color mismatches again. I think if the back color of BattClock sets to transparent, it should solve the problem. I am not sure how to set transparent.
[Touch Diamond, MDA Compact IV Themes and Apps] Cir0w:
Oh, I didn't know that it was possible to switch place on the "icon" (the white box that contains the battery% etc). How do you do that?

Ok, I'll start with a translate into Swedish ;)
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Start TouchLockAction -> Settings _> BattClock -> Configure BattClock.

From there on you can configure size, location, fontsizes, colors, background, etc.....
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Windows Mobile does not know transparency like real windows :(
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
TouchLockPro version 2.12.5

Version 2.12.5 (15-3-2010)

- Updated Chinese Traditional (thanks to victorchen101)

- Updated Chinese Simplified (thanks to zhongzw)

- Do not use HTCLockAPIWhenBluetoothActive when no call

- Added option to disable Zoombar
[Touch Diamond, MDA Compact IV Themes and Apps] JamesAllen:
Wish I Had

No, did not find the answer. I removed the program, found that the registry entries remained in the registry so deleted those, reinstalled TLP, and still on the NavSensor screen for settings in TLP, the right top grey area says "0:unknown" and although "Use Nav Sensor" and the next 2 boxes are checked, the NavSensor will not respond when locked and will not lock with a down swipe. The light sensor, g sensor etc all work, the Nav Sensor does not. I repeated this process and installed 2.11 but that has the same problem. Don't know what I will do at this point, I have used this program for many versions and it always worked. It's almost as if the TLP cannot find the NavSensor.
[Touch Diamond, MDA Compact IV Themes and Apps] tcc13:
Hi ZuinigeRijder I really like your app but am having a bit of trouble trying to set it up the way I'd like it to perform and was wondering if you or anybody else can help me? I've figured out that I only want to use the "light" feature so I have enabled it, so if my phone is locked and in my pouch I can take it out and it unlocks.

But this is what I want to achieve with a bluetooth headset while the phone is in the pouch, locked and a phone call is coming in:

- Answer and end call with headset

- Screen remains off and buttons/keys are not functional during call

Oh, I'm using 2.12.4 :)

TIA
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
Ypu can post a debug log file, maybe that gives me a clue.
[Touch Diamond, MDA Compact IV Themes and Apps] zhongzw:
Hi ZR,

I checked the 2.12.5 Chinese Simplified version and found some little lack.

Please upload the latest English resource file, I will fix it.

Thanks for your hard work!:)
[Touch Diamond, MDA Compact IV Themes and Apps] JamesAllen:
Debug Files

Here are the debug files. No matter what I do, NavSensor settings will not "Take" and I get "0:unknown" in the top right field in the NavSensor settings screen.
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
In the logging I see several times:

2010-03-16 14:11:50 219085114 CCapacitiveTouchSensor::Open()

2010-03-16 14:11:50 219085114 ERROR opening HTCNav API

...

2010-03-16 14:12:07 219085114 CCapacitiveTouchSensor::Open()

2010-03-16 14:12:07 219085114 ERROR opening HTCNav API

And this is the code:

LOGDEBUG("CCapacitiveTouchSensor::Open()");

m_bCapacitiveExit = false;
HMODULE hHTCAPI = LoadLibrary(CAPACITIVE_SENSOR_DLL);

if (hHTCAPI== NULL) {
LOGERROR("ERROR loading HTCAPI.dll");
return; // skip capacitive sensor
}

pfnHTCNavOpen = (PFN_HTCNavOpen)GetProcAddress(hHTCAPI, L"HTCNavOpen");
pfnHTCNavSetMode = (PFN_HTCNavSetMode)GetProcAddress(hHTCAPI, L"HTCNavSetMode");
pfnHTCNavGetMode = (PFN_HTCNavGetMode)GetProcAddress(hHTCAPI, L"HTCNavGetMode");
pfnHTCNavClose = (PFN_HTCNavClose)GetProcAddress(hHTCAPI, L"HTCNavClose");

if (pfnHTCNavOpen == NULL || pfnHTCNavSetMode == NULL || pfnHTCNavGetMode == NULL || pfnHTCNavClose == NULL) {
LOGERROR("ERROR opening HTCNav API");
return; // skip capacitive sensor
}

This means that HTCAPI.dll can be loaded:

HMODULE hHTCAPI = LoadLibrary(CAPACITIVE_SENSOR_DLL);

But that the addresses for the functions which are needed to function are not in that dll, so one or more of the functions:

"HTCNavOpen"

"HTCNavSetMode"

"HTCNavGetMode"

"HTCNavClose"

So I do not know if the ROM you use only uses the dll as dummy and does not support/provide those functions.

So it looks like ROM related :cool: and I cannot do anything on it :mad:
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The translations files are uploaded. But editing those translations files again is a bit cumbersome, so I will investigate if it is possible to convert those resx files to excel, so all translations are in one excel file.

For you it is probably better to take the already posted translation files and add the wrong translations.

Note that one screen is adapted and that is about the "Use Zoombar" in the NavSetting menu. So you can take the file CapacitiveForm.resx out of translations.zip and only translate that file, if that was the only wrong file......
[Touch Diamond, MDA Compact IV Themes and Apps] ZuinigeRijder:
The problem with the light sensor is that it will not unlock in too dark conditions, so you need an alternative unlocking method, in case unlocking via light is not possible.

For incoming call and bluetooth active, the best setting is:

HTCLockAPIWhenBluetoothActive = 1

(Note that 2.12.5 has different behaviour, it does this only at (incoming) call, I expect this is also what you want, so then upgrade to 2.12.5).

This way everything is locked (all they keys, even power button) and you can still answer with your headset buttons (which may be blocked if you use the other key locking locking method).

HD2 has a proximity sensor, so you can take advantage of that too, when it is in your pouch. The default proximity settings will suspend when an object is near or unlock when nothing is near:

CmdProximityNear = "!SUSPEND"

cmdProximityNotNear, "!UNLOCK"

And it will disable the proximity sensor when unlocked:

cmdUnlockCall = "!PROXIMITYIGNORE"

cmdUnlockNoCall, "!PROXIMITYIGNORE;!PROXIMITYDISABLE"

There is another Proximity setting interesting for you:

cmdProximityOnBluetooth

This one is empty by default, but for your purpose you can take advantage of the different behaviour you want with bluetooth, e.g.:

cmdProximityOnBluetooth = "!SUSPEND"

I expect the result is the same as with the other proximity commands already described.

I think the combination of Proximity and Light Sensor would be the best combo for you.....
[Touch Diamond, MDA Compact IV Themes and Apps] zsunsun:
Simple request if you don't mind.

Can you make a list of commands available to see on the menu and copy onto clipboard?

That would make setup so convinient...

If I'm missing something please don't hesitate to let me know.
[Touch Diamond, MDA Compact IV Themes and Apps] slickker:
Problem using Windows Media Player in WM6.5

Oh,,,,Sorry,,,,

I resolve my problem myself.

Thank you.