Lack of A2DP in MSFP/AKU2 ROM upgrade (any workarounds??)
so now they released the aku with no a2dp, and I am still baffled as to why they took this option out as I read it was for stability reasons, yet other features that do not work 100% where left in anyway. I mean really we have come to expect that with the myriad of features this phone has that 100% uptime and peformance is not really feasible, if truly there where errors why not just leave it in and if its to much for the user we will not use a2dp. I mean the beta rom for the wizard had it and even with its slower omap cpu it worked with minimal bugs at best.
Anyways anyone think it would be possible to extract the bluetooth stack files from the wizard beta rom and use it on our ppc 6700 much like the ppc 6600 had cab files that updated the bluetooth stack some of which added a2dp functionality without having to hard reset?
does the wizard use ms bt stack, or the widcomm one? some people have had success making the widcomm stack update with a2dp, but i dont think the ms one will do it. just my 2 cents from when i tried, but im no hack master.
The Wizard uses the microsoft bluetooth stack, so A2DP profiles that work one the wizard should work on the apache too. Since there are AKU2 updates out there that have A2DP included I am sure eventually we will see a hacked update. I am dissapointed we didnt get an official update though.
I feel like posting this in response because you were such an ass in the other thread.
Quote:
Originally Posted by mcq3000
this rom update aint coming for sprint. It will come with the next new phone they release. Remember 3G for PPC 6600? How did that go.
Sprint could give less than a **** about updates for their current line of phones. Lets stop daydreaming and be realistic for once. You just gotta look at their past record to see that no update to our phones will ever come out.
The Universal already has a rom update with AKU 2. MS finished AKU 2 months ago. There is nothing stopping anyone from implementing it into the current phones. NOTHING.
Ofcourse UTStarCom will tell you its coming, its coming, buy the phone now, its will be updated we promise, they will keep on saying this for the next 8 months till the new HTC Sprint phone comes out.
If you guys didnt fall for such silly tricks they would not keep on using them over and over again.
Wikipedia is a great place to find answers to questions like this:
Advanced Audio Distribution Profile (A2DP)
Also referred to as the AV profile, it is designed to transfer a stereo audio stream like music from an MP3 player to a headset or car radio. This profile relies on GAVDP. It includes mandatory support for low complexity subband codec (SBC) and supports optionally: MPEG-1,2 Audio, MPEG-2,4 AAC and ATRAC. Bluetake's I-Phono Hi-Fi Sport Headphones are an example of this profile being employed. Most bluetooth stacks implement the SCMS-T copyright protection. In these cases it is not possible to connect the A2DP headphones for high quality audio. E.g. the Motorola HT820 can be used for high quality audio only with certain versions of the Toshiba bluetooth stack.
Lack of A2DP in the Sprint ROM upgrade (any workarounds??)
Im sorry if this has been answered but is it enabled through this rom upgrade? i thought it was a no but according to sprints website on the downloads page it say it is.
This download updates the software on the PPC 6700 including new features and bug fixes. This upgrade requires the use of ActiveSync 4.1 on your computer. ActiveSync 4.1 is available as a free download from Microsoft by clicking here or go to http://www.microsoft.com/downloads and choose "mobile devices".
New features added are:
Enhanced security using Secure Multipurpose Internet Mail Extensions (S/MIME).
The Direct Push technology (Push E-Mail feature) of the Messaging & Security Feature Pack which enables you to receive e-mail messages as soon as they arrive, without waiting for your PPC 6700 to synchronize at a specified interval. Support for A2DP (Advanced Audio Distribution Profile), which allows the use of Bluetooth-enabled stereo headsets.
its been covered in the sticky thread. It appears that its just a typo on Sprints part. They had to remove the A2DP for some reason, I guess it was in the beta version, but it got cut from the final release.
It looks like Jwrightmcps got it working on his PDA and is looking for testers with a2dp devices. I don't have one, but I'm looking forward to buy one soon as it works.
Seems like he is pretty damn tech savy. I didnt finish the thread, but it looks like he rebuilt a ROM to include it. Doubtful we could test it, I thought he mentioned using OMAP core instructions.
Other carriers that have released the AKU2 update have also removed the A2DP support. The problem is at the Microsoft/HTC level and if there are serious enough problems to remove it after the description on the website has already been generated including it, my guess is that you wouldn't want the A2DP profile in its present form. If it wasn't for their non-disclosure agreement, maybe one of the Sprint beta testers could give us more information about the nature of the problem(s).
Other carriers that have released the AKU2 update have also removed the A2DP support. The problem is at the Microsoft/HTC level and if there are serious enough problems to remove it after the description on the website has already been generated including it, my guess is that you wouldn't want the A2DP profile in its present form. If it wasn't for their non-disclosure agreement, maybe one of the Sprint beta testers could give us more information about the nature of the problem(s).
ramjet73
From what I understand there was a beta version of this stack? Has anyone tried ripping it out of the beta for support in the released ROM?
Btw... I do have to blame them for OFFICIALLY listing A2DP support on their site in their featureset... *that* is incompetence.
I have an amazing idea. Why doesn't Microsoft create products like WM5 with all the things people want (like A2DP) AND get it out on time? Why does it always have to be a choice? But I know its a revolutionary concept for a technology company to be competent AND timely at the same time.
Agreed!
Actually Dale, I agree with pretty much all that you have ranted on in your past two or three posts in this thread. Just looking at A2DP, much smaller companies like Broadcom have had this functionality in their stack for two years. Other smaller developers have come up with solutions long ago, yet MS the largest software developer in the world refuses to put the resources that are needed into the Mobile Devices platform to develop this and other issues.
Look at the backwards steps we have taken with Activesync. They have removed features such as wifi syncing saying that there were security issues that could not be fixed in time to release WM5.0...again a lack of resources. They removed the abilty to do backups, so for several months we could not do a backup till developers like Sprite and SPB could play catch up. It took months to get this AKU2 update released. Most of us expected push email to work with the initial release of WM5.0, only to find out that it also needed SP2 for Exchange before it would work. So we waited. Then just as that was released we found out that our devices would need AKU2 which included MSFP. So we waited, and waited, and waited....many of us are still waiting. It has been months. There are many bugs that have been around since the first release of Pocket PC that are still present. Again we hear that the lack of resources makes it difficult to repair these bugs......A lack of resources from the world's largest software developer?? I think not. It's more like a lack of commitment.
I'm personally very tired of pushing this platform. At first I could see it as growing pains, but it is now to the point were it is pure amateur. As a one time MS MVP for Mobile Devices I quit after my first year for several personal reasons. One of them was that I was becoming very disheartened with the lackluster effort I was seeing in Microsoft put into Windows Mobile. They seemed to put in the minimum effort to keep it alive. Stability of the platform does not seem to be a high priority. Living up to time tables is even less a priority. Being upfront on some matter such as AKU2, MSFP and what was all needed to make push email work seems not to be a proirity at all. More like shading the truth about it for as long as possible in an attempt to fool people into buying their product was the real priority.
Argue with me all you want. I have sat on both sides of the fence. I feel I'm looking at this with a VERY open mind.
This is a longshot, but does anyone know where I can go to find some good resources on extending the stack? Also -- another longshot -- but can you use .NET to interface with it? That would be mighty convenient for me...
It can't be due to the processing power of the 6700. The Treo 650 has a much older OS, a slower processor and less memory and it has A2DP. There's got to be something in the MS BT stack that's royally messed up.
$%#%^#$*
Login
Panel
