New info about the upcoming "update"

[dishe]

Originally Posted by 2kmy477

The BT problem still exists,which is BT just keeps disconnect my BT headsets(I have the Jabra 8010 & Moto H500),if I put the phone to standby,when I wake it up,70% of the time my BT headset was disconnected,also if I listen to streaming music through my BT Jabra 8010 and a call comes in,half of the time BT got disconnected,I've tried all custom ROMS out there,DCD 1.67 seemed to be a little better over all others,the stock 2.16 & 2.17 were the worst of all.I went back to the stock 2.09,solved the BT disconnect issue.but I sounded choppy at the other end.

This is a problem that started in 2.14 and 2.16 (disconnects and random BT shutoffs). I can say with confidence that 2.17 fixed it (as did our custom one released before it), and I've cooked many roms based on 2.17 that work consistently as expected. You're either doing something wrong, have faulty hardware, or basing your experience solely on 2.16.

[2kmy477]

Originally Posted by dishe

This is a problem that started in 2.14 and 2.16 (disconnects and random BT shutoffs). I can say with confidence that 2.17 fixed it (as did our custom one released before it), and I've cooked many roms based on 2.17 that work consistently as expected. You're either doing something wrong, have faulty hardware, or basing your experience solely on 2.16.

After I flashed the ROMS,I did not install any apps(not even a single one)just paired my BT headset,then put the phone in standby,waited about 20-30 mins,turned the phone back on,as i said earlier,80 % of the time,I found out that my BT headset was disconnected.Also,I don't beleive i have a faulty hardware,cause when i went back to the stock 2.09,i did not have this problem.

[supark]

Originally Posted by dishe

This is a problem that started in 2.14 and 2.16 (disconnects and random BT shutoffs). I can say with confidence that 2.17 fixed it (as did our custom one released before it), and I've cooked many roms based on 2.17 that work consistently as expected. You're either doing something wrong, have faulty hardware, or basing your experience solely on 2.16.

Bluetooth works just as poorly on my mogul with the 2.17 ROM as it did with the 2.09 - low volume or nothing at all on my end and the person on the other end says I sound like I'm talking underwater

[dishe]

Originally Posted by JimSmith94

"All" the Bluetooth issues are resolved"? I have tried the official 2.17 upgrade and am currently running DCD's 1.6.7 kitchen based on version 2.17. BT itself works fine, but as far as I know, everyone still has the voice confirmation issue with MS Voice Command.

The only way to get my PPC-6800 to dial with MS VC is to turn confirmation off. Even then, the "redial" and "call back" commands still ask for confirmation, and thus don't work. All of this worked fine on my PPC-6700 with Helmi's WM6 kitchen.

If this too has been fixed for the Titan, I must have missed it, and would appreciate a link to this fix.

Haha... are you serious?

This is NOT a BT problem! Its a software problem, specifically with the way voice command tries to access the sound hardware. If you did your homework, you'd know that the current version of VoiceCommand has this problem with all devices using this new chipset (Kaiser, Mogul, Vogue, etc).
Knowing this, Sprint chose to bundle a different voice application (Cyberion, or something) that IS 100% compatible with the hardware.
You can't seriously expect Sprint to be working on a fix for a specific peice of software that they have no responsibility to support (and has known issues with the hardware you purchased), do you?

Look, I use VC. Even with its incompatibilities, it works better than other options. But, this is a limitation of the software, and all we can do is hope that a new version of VC will eventually come out that is compatible with the newer hardware (the current version is kind of old already).

So, once again, why is everyone still ratting on Bluetooth?

[cykococo]

Originally Posted by JimSmith94

"All" the Bluetooth issues are resolved"? I have tried the official 2.17 upgrade and am currently running DCD's 1.6.7 kitchen based on version 2.17. BT itself works fine, but as far as I know, everyone still has the voice confirmation issue with MS Voice Command.

The only way to get my PPC-6800 to dial with MS VC is to turn confirmation off. Even then, the "redial" and "call back" commands still ask for confirmation, and thus don't work. All of this worked fine on my PPC-6700 with Helmi's WM6 kitchen.

If this too has been fixed for the Titan, I must have missed it, and would appreciate a link to this fix.

Thats an issue with VC and not the phone. Microsoft tech support won't even touch this issues for WM6. Funny because on all the websites that sell it they advertise it as WM6 capable.

[mstevens]

Originally Posted by JimSmith94

everyone still has the voice confirmation issue with MS Voice Command.

If you'll check Microsoft's Voice Command blog, you'll see that they acknowlege that this was a problem with poor design of VC and plan to fix it in future versions.

[JimSmith94]

Originally Posted by mstevens

If you'll check Microsoft's Voice Command blog, you'll see that they acknowlege that this was a problem with poor design of VC and plan to fix it in future versions.

This is the only MS blog about VC I could find, is this the one you're referring to? http://blogs.msdn.com/windowsmobile/...03/524289.aspx If so, it was locked in June, 2007.

After a quick perusal, they seem to be saying that VC doesn't work at all over BT because BT microphones sample at 8 kHz instead of 16 kHz. This is obviously not true, as all the features worked fine on my 6700 over BT. Could the VC confirmation problem on the 6800 be due to the way it handles the BT microphone frequencies?

[InvincibleLiving]

no rom will ever be the master 'fixer' we're all looking for. In order to remain in business they (all businesses) need some carrot to dangle for the consumer... stop falling for the hype machine folks. notice the timing of the chatter about WM6.1 just in time for christmas season when your consumerist juices are at their peak. They plant the seed, let it grow for a while (say, 3 months wow just in time for CES) and then roll out an unfinished product with 'some' of the promises fulfilled... then WM7 will roll around and start the process over for a new generation...

They will never, NEVER deliver a 100% fully working-bugs-ironed out ROM, device, or product because it would not be beneficial to their business model.

Cell phone carriers are not in the business of selling phones, phones dont even account for 20% of their business, they sell subscriptions, calling plans and al a carte add on features.

I never get disappointed by the updates, rom revisions ect because i've lowered my expectations to what i know they can REALLY deliver: a decent network to make calls on, and decent handsets. I dont expect perfection in any step of the process, not in customer service, not in billing, not in upgrades, not in the phones they sell. Instead i make them compensate me for their short comings with service credits, discounts, and phone swaps.

[gguruusa]

Originally Posted by nautica2450

no rom will ever be the master 'fixer' we're all looking for. In order to remain in business they (all businesses) need some carrot to dangle for the consumer... stop falling for the hype machine folks. notice the timing of the chatter about WM6.1 just in time for christmas season when your consumerist juices are at their peak. They plant the seed, let it grow for a while (say, 3 months wow just in time for CES) and then roll out an unfinished product with 'some' of the promises fulfilled... then WM7 will roll around and start the process over for a new generation...

They will never, NEVER deliver a 100% fully working-bugs-ironed out ROM, device, or product because it would not be beneficial to their business model.

No, you'll never get a 100% fully working rom because that's an unreasonable expectation of a device that has to connect to 3rd party equipment, run 3rd party software, run in completely unmanged environments, and all the while doing so for such a wide range of customers that what's right for one person is half the time wrong for another.

[fumanchu182]

Take the Mogul and just throw it against the wall, my suggestion... Or wait till the updates are out and then watch it breathe in new life.