Windows Mobile Team sorry for A2DP delay

[Lucas0511]

Off the record, background info from Windows Mobile 5 Team member for all of us waiting for A2DP for our Prophets:

Quote:
"A2DP is a very processor intensive operation. You start with an MP3 or
a WMA, do a lot of work to decompress it into audio, and then need to
turn around and recompress it into the A2DP format to send it.

What we found is that our A2DP implementation just barely works on a
200MHz processor. From the OEM's standpoint, it's our fault for not
writing something that takes less cycles to work. We certainly tried to
make it work, though. Maybe other people will do a better job and show
that we really are at fault. Or maybe no one will be able to and will
show that it's just not possible to do reliably on that processor.

We do know that A2DP works great on WM devices with faster processors. It works sometimes on 200MHz devices, just not reliably enough to ship."
Unquote

My 5 cents: The message is "we TRIED to make it work", but we don´t know if you ever gonna get it for your Prophet...

[vsc]

My 2c on the subject. They have a TI 55xx DSP core sitting right next to the ARM core on the OMAP. They should be shipping the audio frames over to the DSP to offload the work from the ARM. It is really silly to employ the ARM in a signal processing roll where there is a better, faster solution sitting right on the same die.

I hope someone from Microsoft reads this...

Off the record, background info from Windows Mobile 5 Team member for all of us waiting for A2DP for our Prophets:

Quote:
"A2DP is a very processor intensive operation. You start with an MP3 or
a WMA, do a lot of work to decompress it into audio, and then need to
turn around and recompress it into the A2DP format to send it.

What we found is that our A2DP implementation just barely works on a
200MHz processor. From the OEM's standpoint, it's our fault for not
writing something that takes less cycles to work. We certainly tried to
make it work, though. Maybe other people will do a better job and show
that we really are at fault. Or maybe no one will be able to and will
show that it's just not possible to do reliably on that processor.

We do know that A2DP works great on WM devices with faster processors. It works sometimes on 200MHz devices, just not reliably enough to ship."
Unquote

My 5 cents: The message is "we TRIED to make it work", but we don´t know if you ever gonna get it for your Prophet...

[Lucas0511]

Thanks mate, I will make sure they get the message! Any more suggestions I could relay to them? Let´s make this a team effort, and as you see from their initial feedback they care for us, just do not seem to have a solution found yet... :-)

[27]

"A2DP is a very processor intensive operation. You start with an MP3 or
a WMA, do a lot of work to decompress it into audio, and then need to
turn around and recompress it into the A2DP format to send it.

What we found is that our A2DP implementation just barely works on a
200MHz processor. From the OEM's standpoint, it's our fault for not
writing something that takes less cycles to work. We certainly tried to
make it work, though. Maybe other people will do a better job and show
that we really are at fault. Or maybe no one will be able to and will
show that it's just not possible to do reliably on that processor.

We do know that A2DP works great on WM devices with faster processors. It works sometimes on 200MHz devices, just not reliably enough to ship."

I don't understand O.

Who is this message from? Microsoft?

[Lucas0511]

@27 From a member of the Win Mobile development team - but not an official response from Microsoft.

[27]

@27 From a member of the Win Mobile development team - but not an official response from Microsoft.

So this person works at Microsoft?

Will we have A2DP on the Prophet or not? From what I read, there are no problems with the A2DP ROM on the Wizard. It works reliably enough to ship.

http://forum.xda-developers.com/viewtopic.php?t=45069

[ericlin0122]

This is bs.....
M$ just need a better programmer, not many programmers.

[Sgt_Strider]

Can you post the source in where you got the comments from?

[Urban Strata]

This is b.s...

A2DP is already working on the HTC Star Trek, which also uses the same TI OMAP 200MHz processor as the Prophet and Wizard. Furthermore, a beta ROM for the Wizard has A2DP working, albeit in a buggy, pre-release version.

If Lucas0511 did, in fact, hear this from a member of the Windows Mobile dev team, his source is either mistaken or basing his information on old information. The issue is not the processor's speed, it is bugs in the A2DP implementation. That is the reason is got pulled from the AKU 2.0 release, not issues with speed.

[jwzg]

This is b.s...

A2DP is already working on the HTC Star Trek, which also uses the same TI OMAP 200MHz processor as the Prophet and Wizard. Furthermore, a beta ROM for the Wizard has A2DP working, albeit in a buggy, pre-release version.

If Lucas0511 did, in fact, hear this from a member of the Windows Mobile dev team, his source is either mistaken or basing his information on old information. The issue is not the processor's speed, it is bugs in the A2DP implementation. That is the reason is got pulled from the AKU 2.0 release, not issues with speed.

Is Windows Mobile Smartphone Edition much less processor intesnive than the full Windows Mobile?

[victorlam]

Whom know when AK2U patch will be released by Microsoft or PDA Phone supplier like Dopod, O2, ....

[ericlin0122]

Whom know when AK2U patch will be released by Microsoft or PDA Phone supplier like Dopod, O2, ....


I guess it will be released by xda :D

[raskal]

Whom know when AK2U patch will be released by Microsoft or PDA Phone supplier like Dopod, O2, ....

is no matter if dopod, o2, qtek, or mda, all of them we are talking about are one and same hardware HTC PROPHET and as they wrote, since prophet have a 200 mhz cpu, there are still not solved problems, so no one knows...

[skidoo]

I wonder if there's any update to this

[cidriver]

Still waiting!!!

[Urban Strata]

Guys, what are you still waiting for? The A2DP hack for the Prophet is out and it works. I have it installed on my Qtek S200 and paired with Plantronics Pulsar 590A headphones -- it works beautifully with no skips.

Whoever told Lucas0511 at the beginning of this thread that A2DP is "just not possible to do reliably on that [TI OMAP 200MHz] processor" is either misinformed, lying or just plain dumb. :roll:

[J.Walker]

+1, Tornado path works well. Well, Microsoft can't do something that other can do well, once again...

[Lucas0511]

@Urban Strata
The Win Mobile team is quite large, and one team member had asked for me his peers in charge on this issue. I know that regardless of remarks re the Dopod, MS had released the A2DP to all ODM´s, for them to decide to include it or not. Fact is that the Win Mobile Team is really happy that we got A2DP working on our HTC Prophet devices, and hence enjoy our Win Mobile 5 experience.