very well, with civility;

@ GeneralAntilles: As I have said, I am not a programmer, I have no programming skills... you know... for some reason I don't like you... You will say it's because you poke holes in my logic or some such nonsense... but really I have to point out you have posted some things that have been terribly useful... but when you reply to other's posts, you seem arrogant... it's really annoying... I guess it's just a taste of my own medicine.

@ Johnx: I am fairly confident I have an understanding as to why we don't have a2dp available for the Internet Tablets...

I BELIEVE there are several mitigating factors: for starters, A2DP is not the only issue. First the sound has to be decoded into wave and then re-encoded into either mpeg (1, 2, 3, OR 4), AAC, or SBC (for A2DP friendly encapsulation) then the output has to be encoded and encapsulated then transmitted via bluetooth networking to a receiver (the headphones) which then decodes the packets and plays the sound... the simple act of decoding and re-encoding (though necessary for universal compatibility) is incredibly process intensive. Hence the huge processor load when apps like mplayer are set up to use A2DP (and that even happens on regular laptops and desktops much like the one I am using now) this load is far more limiting when it comes to SMPCs like the Internet Tablets.

Now I am fairly positive that the reason A2DP was initially planned for on the hardware side but removed before release is simply due to the fact that implementation would hamper the device so critically during normal use that Nokia did not feel comfortable letting it out into the wild.

Now that being said, I also recognise that Nokia did build the Internet Tablets (the n810 at least) with a separate sound processor (known as the DSP). The given reasoning for this was to offload audio decoding to a desperate processor. however; you and I know that this can be done on die (on the main processor) with little to no impact to performance. so the more likely purpose of the DSP would be for decoding and re-encapsulation for Bluetooth audio profiles, such as A2DP or GAVDP. Weather or not this was genuinely their plan, we don't know but can only speculate.

All this said, the final reason for a lack of A2DP support is simply this: the OSSO software available (for ANY platform) simply has not properly implemented A2DP, much less any other Bluetooth profiles other than networking (such as LAP, OPP, SPP, and PAN) heck even HSP is not implemented where it needs to be, but it is such a simple profile that it CAN be done on die with little to no impact to operation.

No, for PROPER implementation of A2DP, or any other "high end" bluetooth data profile, it must be done by the kernel. this IS beeing looked at but we cant expect any significant progress untill next generation of kernels (if even then).

It appears that the kernel dev teams have been focusing more on hardware compatibility than data link layer encapsulation.

If I am wrong in ANYTHING I have said here, please let me know... as I am seriously interested in your take... but know I am taking the stance that until the kernel properly implements a2dp support, Nokia will not include it... and until Nokia supports it on the base device, I see it as not viable.