Proximity Sender - Some connections status ignore

[emhain]

Hi,

i'm trying WCL Proximity Sender Personnal edition, 6.7.0.0 (demo version).
During my tests many devices (phones) found return send result as WCL_E_TIMEOUT (43),
but at the same time nothing append on phone's screens : i expect a message like "would you like to receive file XX from computer XX ?" - "YES" / "NO"

- i tried change connection timeout to 60, without more success

- i tried also with "BluetoothOPPClientDemo" and when i use "connect" on phones, the result is "timeout", but the phone never react.

- then i tried with "TextBlue" app' but i got same result.

I can't make an exhaustive list of incriminated phones.
Have you got some explanations about that ?

My bluetooth driver is Microsoft stack (Enum MS Bluetooth version = 6.0.6000.16682)
The library used is "Personnal WCL 6.7.0.0" for .NET

Thank you for your answers.

[Mike Petrichenko]

Are you able to send file to your device with using standard windows BT tool?

[emhain]

I didn't try that : i'll do.

Until next test,
do you know some restrictions made by phones' constructors on bluetooth obex service ?
For example on my phone : Sony Ericson K750i i have no connection timeout problem.
For another phone like HTC H2 i have a timeout connection problem and no reaction on phone.
Another example on Acer phone (F900) it seem that i have same timeout if phone is in sleep mode, not if phone is awake (screen light on)

i'll post my next tests tomorrow.

[Mike Petrichenko]

http://forum.btframework.com/index.php/topic,925.0.html

[emhain]

Hi,

this afternoon i tried normal push object from my phone to another phone in sleep mode.
Then he didn't awake, like with wcl library, and my phone said he can't connect.

I made an update on my Windows Vista : got SP1.
Now, with wcl library (with 60 sec. timeout) i have a "Low level" error in ProximitySender app' where i had "Timeout" error before.
I read you post about "low-level driver internal error" (http://forum.btframework.com/index.php/topic,775.0.html)
But i don't know how to change manifest, when i publish debug mode (visual studio 2008) manifest is rewritten.

How could i know if my Microsoft Bluetooth drivers use widcomm or are native ?

Another question, do you know some tricks to force phone awakening before sending my files ? Maybe Obex is not the best way ?
Could it be a problem from Bluetooth version (2.1) into phones ?

Thanks a lot for previous and next anwers.

[Mike Petrichenko]

Hi,

Manifest

WidComm: Actually there is no WidComm drivers on Vista/Win7. It can be just extension for MS drivers. So it can be only MS/BlueSoleil or Toshiba.

Phone: Unfortunatly there is no way to wakeup phone from PC if phone does not support such feature.