It seems there is going to be yet another disadvantage to not having Windows Mobile5 on our devices:
http://msmobiles.com/news.php/4556.html
Maybe it can be back ported?
Related
http://toothing.proboards28.com/index.cgi?board=tchat&action=display&num=1078412493
technology only ever make it if somebody decide to make people relate it with sex somehow
just think about vcr, internet .......
heck these days the 3g company called 3 run comercials which border on sugesting that their video phone could be used for advanced phoneSex
lol crazy old world
Hmmm, after reading the article I now understand 'toothing' is an abbreviation of BlueToothing, but the term sounds rather disgusting to anyone not familiar with the term :?
yeah sounds like something hanibal lector would consider foreplay
Slightly offtopic, but coming from this article I found two applications designated for Bluetooth Messaging/Chat, Bluechat and ProximityMail, both are non-working on my MDA-II
BlueChat seems to incorporate a hard-coded port, and ProximityMail says it can't find a Bluetooth Stack...
So, no proper toothing for me hahaha
Is there any toothing SW working with XDAII?
Have you tried BuZZone from Handango?
Or have you found anything working on your own?
Thanks!
Chris
BuZZone
By the way...
Hello Chris,
Yes, we plan to support Microsoft Bluetooth stack software in future versions. Your XDA II Bluetooth works with this software. Current BuZZone version supports only WIDCOMM's stacks on devices like HP iPAQ, Dell Axim, Asus, Fujitsu-Siemens, etc.
Kind Regards,
BuZZone Team
any development on 2i???
What would happen if....
Hi,
I'm soon to receive an XDA IIi, and wonder what is the reason why one couldn't just stick WM 5.0 on it? What would happen, would it just refuse to boot up, or would it only not work 100%? Has anyone tried, or should I be the first guinea pig? :twisted:
Thanks,
Truthiswithin
somebody tried it on a magic and it just said wrong model id something something
and would not even begin install
roms have to be 100% the same device in order to work so the leaked
himalaya beta 2005 rom cant work
Editing the Rom?
Thanks for the reply... but I don't quite get how this all works, couldn't you just modify the ROM to work with the Magician?
Would it make a difference that the XDA IIi is so much similar to the Himalaya? How do HP and Dell propose to offer upgrades for their machines? How will they modify the ROM, or will Microsoft do it for them?
Thanks again,
Truthiswithin
HTC gets the source from ms and include all the spcefic drivers and settings for their devices
then they pass on a basic rom to tmobile and o2 and all those critters
then they add all their stuff and release it
i've yet to see anybody porting a rom themselfs even though some people were looking into it back in the early xdaIIs days to try and get 2003SE to xda2 as far as i know they dident have any success
and xdaIIi just looks like xda2 they are not all that similar under the hood
with the wifi and the different cam and different cpu and .....
Fact:
Microsoft's A2DP implementation in WM5 is incompatible with certain headsets.
Certain headsets, such as many Nokia and Logitech ones, sound incredible (as good as wired headphones), whereas others, like i.tech or Jabra, don't.
This has been a subject of much confusion to WM enthusiasts, since these headsets sound great when paired with other devices, however when used with a WM device, a high pitched ringing/hissing and slight distortion is heard when certain frequencies of sound are played.
Some Pocket PC users have temporarily solved their problem by porting the Widcomm Bluetooth stack over from the Dell Axim series, however it is generally buggy and not available for all devices.
Fact:
Windows Mobile 6 Beta was released, and had even worse A2DP than WM5
When the beta/demo roms starting floating around, many of us who experience the problem had a glimpse of hope that maybe it would be fixed.
But alas, the A2DP support had many people re-flashing back to WM5. It was even worse.
Fact:
THE FINAL RELEASE OF WM6 SUPPOSEDLY FIXED THE QUALITY BUGS OF A2DP!
There is a write up about this here:
http://forum.xda-developers.com/showthread.php?t=310438
Basically, the new devices shipping with WM6 seem to be more compatible with a wider variety of headsets than its predecessors.
Headsets with the static, popping, hissing, etc... finally sound good even with the Microsoft bluetooth stack.
Some of the new cooked Roms are starting to use this new A2DP support as well.
Problem:
WM5 still sounds bad with A2DP!
Those of us who don't have WM6 upgrades available, or don't want cooked roms or beta versions, are stuck with the poor A2DP of WM5.
Solution:
SOMEONE NEEDS TO MAKE A NEW A2DP PATCH using the WM6 drivers!
Remember when someone first made the A2DP support for Tornado available in WM5? If your device didn't have A2DP to begin with, all you needed was AKU2, and this patch would install the signed drivers and make the appropiate registry edits and like magic we all had A2DP (albeit crummy with some headsets)!
Over time, other patches were made, some using AKU 3.5 and other later releases that promised the possibility of better sound. But all of them failed.
What we need now, is for someone who has an official WM6 device (or someone who has access to a decent cooked ROM with the new A2DP support) to help make a NEW patch for those of us who need it!
Anyone out there willing to help?
Hi there,
question, I have an a2dp bluetooth headset, which I use to listen to my music on my diamond, but since I've stopped using Touchflo3d I have the following problem: the play/pause/ffwd/bwd buttons only seem to work with windows media player. even worse, If I'm listening to music with pocket player and I touch one of the buttons, it automatically starts windows media player.
How can I turn this off? is there a tool to configure which software uses my a2dp functionality??
Even though it's extremely dead, you really should post in the Condiuts forum - not here. AVRCP is problematic at best on Windows Mobile. It's one of the main reasons I'm ditching Windows Mobile entirely as soon as I can find a good phone sporting Andriod (I'm crying about HTC's decision to not provide a HD2 based Andriod phone).
Which version of Pocket Player do you use? I'm using 4.1. I think 4.0 and 4.1 are the only ones that properly support AVRCP. Even so, sometimes, as you note, it goes and starts controlling WMP. Stupid HTC caused this!
Meantime check out http://www.conduits.com/community/forum_posts.asp?TID=1785&PN=1
It talks about a new Bluetooth DLL that fixes a lot of the problems (but, unfortunately not all). This DLL is a Windows Mobile 6.5 based DLL so that may explain some of the times when it messes up.
Good luck.
defaria said:
Even though it's extremely dead, you really should post in the Condiuts forum - not here. AVRCP is problematic at best on Windows Mobile. It's one of the main reasons I'm ditching Windows Mobile entirely as soon as I can find a good phone sporting Andriod (I'm crying about HTC's decision to not provide a HD2 based Andriod phone).
Which version of Pocket Player do you use? I'm using 4.1. I think 4.0 and 4.1 are the only ones that properly support AVRCP. Even so, sometimes, as you note, it goes and starts controlling WMP. Stupid HTC caused this!
Meantime check out http://www.conduits.com/community/forum_posts.asp?TID=1785&PN=1
It talks about a new Bluetooth DLL that fixes a lot of the problems (but, unfortunately not all). This DLL is a Windows Mobile 6.5 based DLL so that may explain some of the times when it messes up.
Good luck.
Click to expand...
Click to collapse
Thanx!
*edit* I have not yet tried the wm6.5 DLL (running 6.5 at the mo, so np) downloading installing now, fingers crossed
Is anyone cooking a rom for the T-mobile HD2 that uses the Microsoft bluetooth stack instead of widcomm. I am looking to see if Microsoft Voioce Command will work properly with this stack.
yes. it would be nice to use my by keyboard and mouse again. LOL.
Subscribing to this thread, too...
Very Unhappy
I could not wait for the HD2 to be released on Tmobile. I have been with them for almost 9 years. I thought finally I can use their 3G network with the HD2. The last thing I expected was for the basic functions of the phone to not work. The phone does so much and is very advanced yet the basic bluetooth functions have been left out. I have spoken with both Tmobile and higher level support at HTC and honestly neither is going to do anything about the bluetooth support on this phone.
Well, if this is true, then it's becoming more and more clear that this is not something they just forgot to integrate - they omitted it on purpose, like the second camera (the second big fauxpas for a "high end phone"!), in order to have something left they can put into HD3 which makes people buy a new device...
I'm still wondering about the roms though - on PC I used to fight with BT stacks years ago. But it as always possible to install a different one, no matter what BT dongle I was using. Is it definitely impossible to create a rom with another stack? Is the stack somehow hard coded into the hardware?
polera257 said:
Is anyone cooking a rom for the T-mobile HD2 that uses the Microsoft bluetooth stack instead of widcomm. I am looking to see if Microsoft Voioce Command will work properly with this stack.
Click to expand...
Click to collapse
Great question...I'm hoping there is an answer.
This would be so great if anyone could make my bt mouse running again on HD2. May be there could be a sourgeforce app or a MS BT stack cracked HD2-Rom.
If I only could use my BT mouse on HD2, may be in 2012 on WM8? Would be so nice for RDP, Virtual Machines, Gaming...
Someone tried on HD2 android with blueinput? Cannot get my BT working Android Running since my new Radio semms not to fit, will test later... I changed the BT working Android to the Phone working Android that is running fine on new Radio...
holylove02 said:
yes. it would be nice to use my by keyboard and mouse again. LOL.
Click to expand...
Click to collapse
I was able to get a BT keyboard to work on my HD2 with stock rom. I never tried a mouse.