[maemo-users] Windows Mobile Phone detected as a PDA - can't set as Phone

From: Ivan N. Zlatev contact at i-nz.net
Date: Fri Sep 14 20:03:35 EEST 2007
On 9/14/07, Acadia Secure Networks <acadiasecurenets at aol.com> wrote:
> Ivan,
> your question led me to submit a query to Google which came up with the
> an explanation available at the www page whose url is
> http://blogs.msdn.com/windowsmobile/archive/2007/04/17/why-did-we-remove-bluetooth-dun.aspx

I am aware of this blog post. It was one of my first hits when I was
googling for a solution to my problem a few days ago.

*** snip ***
> Here is the text of the blog post where that decision is indicated
> (highlighted in boldface type by me):
> >     Actually, Microsoft did not remove Bluetooth DUN completely.  We
> >     still ship this technology to our OEMs.  It is included in an
> >     optional package that OEMs and operators can decide to ship on a
> >     per device basis.  Internet Sharing is also in an optional
> >     package.  We did change one thing though.  Internet Sharing is
> >     included by default and Bluetooth DUN no longer is.
> >

This only makes me wonder how MS defines an "optional package"
compared to an "included by default optional package". :-)

> I suspect that  Microsoft was also getting pressure from  some carriers,
> who do not want to have their mobile handsets being used as layer  1
> devices (modems). In my own case the CD that shipped from Verizon
> Wireless with my Windows Mobile 5.0 Smartphone (an XV6700) does have the
> wmodem.exe app on it. It so happens that the handset, as shipped to me
> had the application installed but hidden. I am currently running with an
> OS version that has the AKU2 feature set.
> There may be a similar workaround for getting Bluetooth DUN to work on
> your particular Windows Mobile 5 handset but to get you started here is
> the url to a www page (one of many) that has an "how-to" thread on the
> subject for the XV6700.
>     http://www.howardforums.com/showthread.php?t=827559
> In case you have difficulty figuring out which AKU is running on your
> handset, here is the url to an article at the msmobiles.com www site
> that may be helpful:
>     http://msmobiles.com/news.php/5857.html
> And here is the url to an article that maps the AKU# to the OS version
> number ranges for that particular AKU#.
>     http://modernnomads.info/wiki/index.php?page=OS+Versions

Thank you for taking your time. I will investigate further, but as far
as I can tell I do not have wmmodem.exe and the solutions I found were
mostly about flashing the device with some hacked Windows Mobile 6
ROM, which I am not keen on doing.

> Best Regards,
> John Holmblad
> Acadia Secure Networks
> Ivan N. Zlatev wrote:
> > I own a Windows Mobile 5 Phone device (HTC Trinity) and a N800. My
> > issue is that the device is detected as a PDA and not a Phone (via
> > Bluetooth), so I am unable to set it as the phone in the control
> > panel. Any ideas on how this can be resolved? Do I have to file a bug
> > and how to get debug information?
> >
> > Also does someone have a clue how can I express a vote for the
> > Bluetooth PAN support mentioned here
> > https://bugs.maemo.org/show_bug.cgi?id=1195. I seem not to have access
> > to the actual proposal here -
> > https://maemo.org/community/wiki/bluetooth_pan_proposal.html.
> >
> > Regards.
> >

Ivan N. Zlatev

Web: http://www.i-nZ.net
"It's all some kind of whacked out conspiracy."

More information about the maemo-users mailing list