|
||||
I heard the new update was suppose to allow the Sprint TV also. I know you can do it now but I can wait if it is actually supposed to happen. I keep hearing Jan. 28 as the release date.
|
|
||||
Quote:
Ok, maybe I haven't been following the latest developments in the forum lately, but did I miss something? Wasn't bluetooth fixed a while ago already? Who says there is even a problem anymore? A few of the devs here and I (DogGuy, Sfaure03, etc...) made a custom configured rom a while back that fixed all BT issues, and I made a little announcment about it, and DogGuy even based his kitchen at the time off it. Then, Sprint released an OFFICIAL update a few weeks ago, 2.17, which fixed it as well (2.16 fixed it but introduced a new problem, 2.17 fixed that problem and now all BT issues are resolved as far as I know). So, now most of us are just waiting for Rev A and the confusing promise of GPS support. Perhaps I'm missing something, but what outstanding issues are there to be resolved on this device? My bluetooth (and everyone I know who was having problems) has been working fine for the last month or so already...
__________________
Techcitement.com - I write for these guys pretty regularly. A Blog about tech that makes people excited.
Diary of a Mobile Enthusiast - My personal blog... haven't had time to update it.... *sigh* Hey, if I've helped you in any way, click the ads on my blog so I can make some $$!! |
|
||||
"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. |
|
||||
While this sounds like a genuine problem, from you description I'm not entirely convinced this could be called a problem with Bluetooth. Something that needs to be addressed, yes, but not necessarily something that can be wrapped up with the BT issues.
|
|
||||
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.
|
|
||||
Quote:
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? |
|
||||
Quote:
__________________
|
|
||||
Quote:
|
|
|
|