Related
Hi all,
Please go easy on me here, as I have some probably pretty basic questions. I have been digging around the internet (mostly these forums) for the past two days since I got my new Mogul from Sprint running WM6. I had the PPC-6700 prior to this (as I expect most of you had) and I was fairly good at tinkering on that one, but I'm on new ground here with WM6 and a new phone.
First, I am a little confused by all the names.
For sure, I know that this phone can be called the Titan, the Mogul, or the PPC-6800. What I'm not sure of is that some people also call this the Hermes or the TyTn. I figured Titan and TyTn were the same things, but apparently not.
The main reason I'm asking is so that when I am looking for information and posts on this phone, which can I use and which should I disregard. It seems that many of the things posted under the Hermes forum are valid for the Mogul as well, but alas..I'm confused.
Once we get names settled, I'm going to start with only one other question that I have dire need for. I have looked around for answers and most are many months old, so I have to think that there are some more recent findings. My question regards Microsoft Voice Command 1.6 with a BT headset on this phone.
I have installed MS VC 1.6 and paired my new Cardo Scala 800 headset. It seems to work with the following problems:
1) BT quality is not great, including VC voice getting cut off. This is my first BT headset with this phone, and I have read that many people have poor BT quality with this phone. If that's the case, can anyone recommend a BT headset that works well with this phone (preferablly one that charges directly via mini-USB).
2) Confirmation don't work - based on what I have read this is a problem with all WM6 phones with VC 1.6. It appears the only solution is to disable confirmations completely. I have done this and it appears to be able to function. I just want to confirm that there isn't any newer data out there for this issue.
3) Last issue is that I don't get notifications. Meaning, when an incoming call comes in I get the ringing sound, but it doesn't tell me the name. In my searches I came across this posting:
http://forum.xda-developers.com/showthread.php?t=316881&page=51
It is for the Hermes (again..confused) but contains a zip file with 4 files to copy over the default VC files. When I did this and reset my phone, notifications seem to work. I want to make sure that this is the best way to get VC 1.6 working as fully as possible on this phone.
I really appreciate any feedback you can give.... I have a few more questions, but I'll wait till we get these squared away.
Thanks to all!
Well, I've not been a Mogul owner for much longer than you, and certainly have been a PPC owner less (this is my first PPC), however let me try to answer a few of your questions.
First, the "Sprint Mogul" is Sprint's name for this phone. The phone "codename" of sorts is the Titan, and model is the PPC-6800. Hopefully I got that all right. Bottom line, they all refer to the same phone. Also, different cell companies have different names for phones, so it can get a little confusing sometimes.
Now the TyTN is the same device as the Hermes, aka the 8525. From what I've gathered in my short experience, this is basically the same same phone as the Titan, however, it's the AT&T GSM version. Where we have CDMA and EVDO, it has GSM and HSDPA.
The files get tricky too, and you have to know your way around the system before you try replacing files from other phones. A lot of files (and issues) are general for WM6. That means that any device running WM6 may have these same files, behaviors, or issues. However, with that said, certain files are specific to the network. Some of the things like dialers are coded for GSM on one phone, and CDMA on another. So if you think it might have anything to do with the network, double check before you replace it from another phone that's on a different network. In your case, the voice command thing is general to WM6, so grabbing the files from the Hermes was ok.
The bluetooth? Well, that's a question a lot of us still have. The bluetooth on these phones suck. I've heard a lot of people say it's HTC's fault, and I've also heard a few people say WM6 just isn't good with BT anyway. I personally haven't gotten into what's wrong with it much yet, so I can't tell you exactly the issues, but we can only hope for a firmware and/or software update in the future that will help these problems.
I know that if you look around, I've seen lists where people have listed which BT headsets seem to work well, and which don't. The only I have, and thus have tested, is a Jawbone, and I can report, as well as tell you from reading, it's one of the better BT headsets for this phone. It's a little expensive though, so it's not in everyone's price range. Unfortunately I can't help much past that since I've never used any other, but if you search you can probably find threads like I mentioned and just get feedback from other people.
Also, I've never played with Voice Command, so I can't answer any more specific questions on that subject. Hopefully I helped clear a few things up. As I said, I'm definitely still learning myself, but I've been taking in all kinds of information. I love this phone and don't see how I've survived without a PocketPC before.
Ajerman,
Thanks for your input. Ok that makes sense regarding the AT&T GSM version. I think most of what I will want to tweak will be related to WM6 and not carriers.
Unfortunately my Cardo 800 BT headset is my first headset too, and this is the first time I'm using it with the phone. So, I too don't have anything to gauge it against. I'm probably going to return the headset however as it was advertised as having a mini-usb charging jack, when infact it has a micro-usb. I saw the jawbone, looks nice, but again, I only want a headset that uses a mini-usb jack (too many adapters to carry around).
My next questions (hopefully someone can address), is unlocking the Extended ROM for customization. I did this on the PPC-6700 WM5 with an Extended rom unlocker tool and modified the config.txt in there to automatically install certain apps upon hard-reset.
I need to assist the mobile admins at my company with setting everyone's phone up with some additional settings en masse.
Is it safe to use the same procedures on WM6? I'm probably going to try it anyway but thought someone could point me to a good primer on upgrading my skills from WM5 to WM6.
Any more input is valued!
thanks
We just bought an '08 Altima with the bluetooth option. I can pair the XV6800 with no problem, but quality sucks. It is super choppy on my end and the person on the other end can't hear me at all. I tried my wifes XV6800, same thing. I can pair my old E815 and it works perfectly, so it's not the car. I tried a hard reset, no difference.
I tried loading dcd's clean rom 1.6.7, no difference. Is the BT stack upgraded in this rom?
Is there a newer BT stack out there that I could try?
Its worth downloading and trying the Jetware BT Extensions and see if that helps....but usually it does not change quality so much as enable functionality.
http://www.jetwaremobile.com/
Brad
Thanks for the suggestion, but it didn't help.
Developer help with Infiniti/Nissan Bluetooth?
I've got the exact same issue with an '07 Infiniti G35 w/navigation. I've been doing lots of reading on the xv6800's bluetooth, have tried DCD's and Custel's roms, and was just about to start my own thread, but I'll bet our cars are the same bluetooth/rom wise.
Jetware didn't help me either.
Here's the best fix I've found and it works for me consistently.
-Whence the option's available depending on whether you're dialing out or receiving, click the "use handset" button (transfers call to the xv6800).
-Shortly after press the "phone" button (transfers call back through car).
-Should work as expected after that.
Anyway, at this point I'm hoping one of the kind devs on this forum (DCD or Custel to name just two of many) might find a sec to help us out, although I'm aware and appreciate the fact that many other users are keeping them very busy on their own projects.
I'm assuming the xv6800's hardware would be most similar to other HTC pda phones (not sure what happens between GSM and CDMA devices), so here's a list of their phones who's bluetooth does work with my car (from here). It supports the bluetooth in 144 phones total.
Kaiser (wasn't working with stock rom, but works after this patch from HTC)
Hermes
Atlas
Wizard
Apache
Magician
Harrier
HTC pda phones that don't work with my car (at least not 100%).
Vogue
Elf
Titan
The Titan DOES work with an '07-'08 Infiniti G35 WITHOUT navigation (buy more, get less ).
In addition to the stock Verizon rom I've tried DCD's 1.6.1, 1.6.7, and Custel's 1.1 with no change in the symptoms.
It's my understanding the dev community thinks modding the Vogue's bluetooth for the Titan shows the most promise. I found this thread mentioning an alternative, but it seems to have gone stale on another forum. I'd prefer not to use that forum.
I understand the Vogue's bluetooth might show the most promise for general bluetooth applications (which would satisfy the most users), but becuase I plan to use bluetooth solely through this car, does anyone know if I might be able to go an easier route given the information I've provided?
I'm using radio 1.40.00, could 1.47.01 make a difference?
Can anything be learned through HTC's Kaiser update patch?
Are there any bluetooth alternatives being tested that I haven't found?
Thanks for any help anyone can provide.
OK. I tried what you said and confirm the same results on the '08 Altima. If I switch to handset and back to Bluetooth, the sound is clear (weird). The only problem is, I can't switch until a call is in progress. This is a work around, but not a good one. We need a BT stack that fixes this. Or maybe firmware upgrade from the auto manufacturer.
I know this is going to sounds like a cheap shot, but it sounds to me like something needs to be fixed on Nissan's side. I've tried mine in an Accura without any problem, however both of your stereos are manufactured by Nissan.
A word of advice: I always found that auto makers should stick to what they do- namely, make cars. If Nissan were so great at BT stereos, you'd see nissan headsets.
I never bother with factory Bluetooth anymore- I swapped my stereo right away for a decent Sony Xplod system that supports A2DP (wireless stereo) as well as phone calls. The aftermarket stereo not only sounds great, but I play all my music from my phone without taking it out of my pocket. Last I checked, no stock car stereos supported this. Sony is good at stereo and bluetooth (been around the block a few times).
Complain to Nissan. Or swap your stereo for something decent.
My Sprint 6700 with BigJ Rom works great with the 08 Altima. In the fact the audio quality is better than the Sanyo Katana that I also have paired. I am dispointed that I cannt answer calls from both phones on the car headset without first selecting the phone that has an incoming call. Even my At&T home phone with bluetooth can do that although it does require you to select a cellphone for outgoing calls.
I was able to upload a contact entry from my 6700 to the car Download phonebook. However, I can not get that into the more usable phonebook directory. Anyone succeed in doing that?
shannl said:
My Sprint 6700 with BigJ Rom works great with the 08 Altima.
Click to expand...
Click to collapse
You might be in the wrong forum. The Titan is a 6800, not a 6700.
yes, but this thread is discussing the Altima BT stereo. Truthfully, this whole thread should go in a more general BT forum, since I don't think it pertains to the 6800 exactly.
08 altima bluetooth
Just wanted to say thanks to Park City for posting the name of the web site with the bluetooth extentions (jetwaremobile.com). I have just recently purchased an 08 Altima with the Nav system and bluetooth. I have an Tmobile MDA with a cooked ROM running WM6 and I could not get the entire outlook phone book to download to the car. Once I installed the jetware mobile extentions everything worked just fine. I even got some additional functionality I was not expecting like signal strengh and battery status on the nav srceen. As for voice quality, it's never been an issue for me. So far anyway
As I can see, they are currently testing the Mogul with both of your cars. I don't know what they mean by 'testing', but that's what is going on right now.
http://www.nissanusa.com/bluetooth/...gation+System&mfg=All+Manufacturers&x=51&y=16
http://www.infiniti.com/bluetooth/t...igation+System&mfg=All+Manufacturers&x=42&y=9
arcanecho said:
As I can see, they are currently testing the Mogul with both of your cars.
Click to expand...
Click to collapse
I saw that too, but I don't have a lot of confidence they'll be releasing a bluetooth update any time soon. That's why I was hoping the Titan's bluetooth hardware might be similar enough to the hardware in one of the devices that DO work with our cars (Kaiser, etc., list in my earlier post) that their bluetooth software could be ported "easily" to the Titan. I'm sure the devs here are trying to get the Titan's bluetooth to work as well as possible for everyone's devices, which makes sense. However, with California's new "handsfree driving" law starting July '08, I'm only concerned with getting the Titan to work with my car.
Apparently no one's too sure if that's possible.
1. have any of you verified first hand that the kaiser does in fact work?
2. could someone research and identify the bt hardware in the kaiser, and the titan?
3. has anyone run the kaiser bt fix on their titan and tried it?
i suppose i never thought to look at the kaiser's bt. mine still functions after applying that kaiser patch..
the kaiser patch is a replacement TIInit_4_2_38.bts file
this file did not exist in any titan roms prior to 2.16
2.16 introduced this file (i compared md5 and its not the same data)
2.17, htcs supposed 'fix', does NOT contain this file
all vogue roms i have seen DO contain this file, but again its different data
maybe you guys are on to something
i will throw something together tomorrow probably...drinking time.
dcd, thanks for the help, enjoy those drinks!
1. Not first hand, I'm going off this post. That thread's also why I believe the Kaiser wasn't working with the car before the patch.
2. I've spent a lot of time trying, but have come up empty on any detailed hardware specs.
3. I just ran the Kaiser patch and the bluetooth functions the same as it does without the patch.
I'm using a rom from your 1.6.7 kitchen with nothing else added (rom's working great, btw). I had the same issue with the stock Verizon rom.
Crazy thought, but if the cooked rom I'm using is based on a stock rom that didn't originally include the .bts file (2.17), could it be being ignored?
FZ1 said:
this post
Click to expand...
Click to collapse
good enough for me
Crazy thought, but if the cooked rom I'm using is based on a stock rom that didn't originally include the .bts file (2.17), could it be being ignored?
Click to expand...
Click to collapse
maybe...i dont know how the file functions and ties into the others yet
FZ1 said:
The Titan DOES work with an '07-'08 Infiniti G35 WITHOUT navigation (buy more, get less ).
Click to expand...
Click to collapse
i take it they are completely different head units?
I have a 07 G35 WITH Navi and yes, the quality is choppy when I connect my phone to it. I have been just using my Platronics Discover 640 for the BT these days... It'd be nice if someone can come up with a solution for this...
dcd1182 said:
i take it they are completely different head units?
Click to expand...
Click to collapse
They're pretty different. With nav you get a 10 gig hd it'll rip cd's to, the nav runs off that hd, the gui which controls much of the car is different, voice prompts are different, the available buttons are different (see attached pics), and you lose a cd changer. I do know first hand that w/o nav the bt works great with an XV6800 (got a loaner once). Again, I've been unable to find out what's specifically different hardware wise (even with the full service manual).
riDuh7 said:
I have a 07 G35 WITH Navi and yes, the quality is choppy when I connect my phone to it.
Click to expand...
Click to collapse
Is choppy quality your only problem? Are your symptoms different from ours in my earlier post?
FZ1 said:
They're pretty different. With nav you get a 10 gig hd it'll rip cd's to, the nav runs off that hd, the gui which controls much of the car is different, voice prompts are different, the available buttons are different (see attached pics), and you lose a cd changer. I do know first hand that w/o nav the bt works great with an XV6800 (got a loaner once). Again, I've been unable to find out what's specifically different hardware wise (even with the full service manual).
Is choppy quality your only problem? Are your symptoms different from ours in my earlier post?
Click to expand...
Click to collapse
Once connected, I get a really static noise from my end while in the conversation. Of course, it'a really not usable at all....
I'm going to try the reconnecting method that was mentioned above today. I'll come back and report the outcome. And thanks for the help BTW.
EDIT: BTW, my Wizard (Cingy 8125), Hermes (Cingy 8525), Samsung i760, and few of the Moto handsets are all fine paired to my car. MAYBE, someone can get the BT stack from Hermes to work with the Titan?
FZ1 said:
They're pretty different. With nav you get a 10 gig hd it'll rip cd's to
Click to expand...
Click to collapse
whoa, someone hook me up with a G35 to uh, test
Wizard (Cingy 8125), Hermes (Cingy 8525), Samsung i760, and few of the Moto handsets are all fine paired to my car. MAYBE, someone can get the BT stack from Hermes to work with the Titan?
Click to expand...
Click to collapse
well, peices of it maybe. i would blindly guess that the kaiser is closer to titan than hermes, but we need to exactly identify the bt chip in each. plus its still shady then, ie the kaiser has tnetw1251 for wlan same as the titan and I cannot get their newer wlan driver to work on my device.
what we really need to look at is previous bt stack modifications for other devices. i need a better understanding of tiinit_blah. I've also noticed that the devices that work have a more extensive, or a 2nd audiopara file that sets values for some bt devices. to be completely honest right now i dont know what im looking at and i need to figure out how it all fits together before i know where to start.
Well, I tried reconnect method from both phone and the car, but neither did anything at all. The quality is still crappy as heck. Man... I reallly wish this works.
EDIT: Actually my side of the speaker was complete static, and the other side could not hear what I was saying AT ALL. This efing blows.
i have a hero rom on my htc magic and everything works perfectly except the bluetooth audio,
is it possible to somehow install the original htc magic bluetooth instead of the one that comes with hero rom to get it working like before?
Bluetooth issues with Hero ROM's are a known, but they are not fixable at the moment.
So either run a ROM where it works or live with bluetooth audio not working.
Cheesebaron said:
Bluetooth issues with Hero ROM's are a known, but they are not fixable at the moment.
So either run a ROM where it works or live with bluetooth audio not working.
Click to expand...
Click to collapse
Yeah a MOD should post a big sticky at the top of this forum about it, gets asked way to often, must be a bigger deal in other countries. I can do without the slow transfer rate and battery sucking feature.
Clinton
Bluetooth audio is tremendously important if you spend a lot of time on the phone with bluetooth headsets. For me multitouch is one step more important. Now if only 2.0 would come out I could switch back to a rom with bluetooth!
So, I have searched all over these forums, and cannot find a difinitive answer or solution. I have problems with A2DP when connecting w/ the BT in my car, since installing a 2.1 ROM (currently DC 2.09.01). When connected, the music plays about twice as fast as it should, then slows down, then speeds up again. Conversley, Android 1.5 worked fine. There has been a lot of talk of BT issues, but it doesn't appear there are any solutions. Am I correct, or has someone found a solution? THanks.
ZenEXP works if you dont mind switching.
I have had those problems occasionally with all 2.1 ROMs I have tried. Usually, if I pause and then unpause it solves the problem. Sometimes I have to do it more than once.
I'm currently running ZenEXP and I've had the problem a few times, but it has been significantly less than with other ROMs. However, AVRCP hasn't been working with ZenEXP, whereas it has worked on other 2.1 ROMs, such as DC.
So, with the unrooted stock Sprint 2.1 software, A2DP works?
The Darchdroid ROM actually fixes this problem! I had the exact same problem as you with playing audio in my 2010 Mazda 3 and Darchstar's ROM fixed it for me, it's the only ROM I have found so far that fixes the bluetooth
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
I have a problem with my bluetooth headset when I'm playing music, the music stutters alot, I almost have to hold my phone a certain way with very little movement in order for it to play decently. Any solutions on that problem?
Click to expand...
Click to collapse
Turn off/disconnect headset while playing music fixes studdering for me in settings under bluetooth for the connected device. Disconnect the ' phone' while playing. Haven't really tested this on anything but my kenwood head unit.
-------------------------------------
Sent via the XDA Tapatalk App
here's a reply I received from HTC support:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Bluetooth Stack?
So is it possible for one of the developers on this site to rewrite the bluetooth stack or copy the old one from 1.5 that worked?
I have a Panasonic TH12 bluetooth home phone that worked fine before 2.1. I recently bought an AT&T bluetooth phone and it does the same thing. Will pair but not connect.
aschlect said:
Hello, I understand that you have had issues with your bluetooth since the update for your Hero. With the update, the entire bluetooth stack was updated, and thus some bluetooth devices that previously worked are unfortunately no longer compatible. While we have not heard any information about nor made announcements about any upcoming patches to address this, it is not at all out of the realm of possibility. Otherwise, you may want to try a different bluetooth headset. I do apologize for any inconvenience you may have experienced. If you have any other questions, feel free to contact us again. You can find additional support at support forums at community.htc.com. There is also a customer satisfaction survey for you to take if you are interested. Philip HTC Technical Support www.htc.com www.twitter.com/htc
Click to expand...
Click to collapse
I have to call BS on this. (Not on the post, on the reply)
Why would any company not support legacy hardware as simple as Bluetooth. Especially since most devices aren't even Bluetooth v3/v4 standard yet. And Bluetooth 2.1 is 1. Not very old and 2. What 90% of Bluetooth device still manufactured are! and its been around since 2006!
I honestly can't believe a company is going to just say "Oh its to old" instead of fixing their crap. as far as I know v3/v4 is fully backwards compatible to 2.1 because they include "Classic Bluetooth" protocols!
Not to mention I doubt the hardware in our phone is even capable of v4 stuff. I'll have to do some more research on what BT chip is in the phone. Utter BS.
Either Phillip or HTC is a moron.
CDMA Hero Specs for BT:
Supported Profiles: HSP 1.1, HFP 1.5, A2DP, AVRC, (OPP, PBA)
version 2.0+EDR / possibly upgradeable to 2.1+EDR, plus OPP and PBA profiles
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Kcarpenter said:
<snip>
2.1 FULLY backwards compatible to v1. Meaning HTC built the crappiest BT Stack allowable by law to say it includes it. May as well have not bothered.
Someone could probably redo things with AOSP and a newer bluez stack.
Click to expand...
Click to collapse
Yeah, I just bought a BT USB adapter so I could exchange files and synch and stuff. I got it to work ONE time and all it did was pass 200 of my contacts to my phone from my PC. Like it was just waiting to upchuck on me. After that, nothing.
There's three hours of my life and $8.99 I'll never get back.
Bluetooth is pretty much the #1 complaint that users have been posting on the Sprint Community Forums (here's the HTC Hero section). Nearly all of those complaints say that Bluetooth now doesn't work at all or just plain sucks on the stock 2.1 Sprint/HTC release. Which probably also means that any ROM here based on 2.1 stock will also suck it up bad with Bluetooth compatibility. Known problem, no one has done anything about it yet. It sounds like AOSP ROMs don't have this issue, so at least that's good.
I just purchased an A501, rooted it and am running the Alexander III rom, (very nice job on the rom!!!)
I was hoping I would get the bluetooth Headset HSP profile in the new rom but sadly it was not there.
A little research has shown that there is a Bluez driver plugin installed and various bluetooth libraries, my question is can I potentially just replace these libraries with bluez libraries from another rom that has the HSP profile?
I really need to get the bluetooth headset profile working on this A501, and am willing to pay a bounty for help in getting it working
Sorry to say, it doesn't work... as with most other Tablets.
Just using some libs from another ROM isn't going to work either, unless they are extremely similar... and all ROMs similar enough to try such a stunt are almost definitely broken as well.
Sorry, but you'll have to roll your own BT stack if you're desperate enough to try... I'm not gonna.
haag498 said:
Sorry to say, it doesn't work... as with most other Tablets.
Just using some libs from another ROM isn't going to work either, unless they are extremely similar... and all ROMs similar enough to try such a stunt are almost definitely broken as well.
Sorry, but you'll have to roll your own BT stack if you're desperate enough to try... I'm not gonna.
Click to expand...
Click to collapse
Still doing a little research on this. I discovered, in the Bluetooth folder, a couple of files pertaining to what Acer has deemed "black listed", which simply means, certain brands and models are not allowed to work with bluetooth. System/etc/bluetooth/
Also noted, if you modify the files, you need to make changes in a couple of other module files (android_bluetooth_ScoSocket.cpp). The info in the above files tell you where to look.
Not sure why Acer black listed those devices. Legal reasons maybe? Plain incompatibility? Who knows.
My dev skills, are not quite up to modifying .cpp files. Probably enough to muck things up really good Not to mention, I would have no way to test them. But when I get a chance, I'll see what's in them.
Of course most of this pertains to Auto pairing, so might not be of much use. As with the .so files in the Bluez folder, you'll need to de-compile them first to see what's in there.
Also, I saw some bluetooth apps onn the market that some folks had some success with getting HSP. Not the off/on widgets but an app itself. Might want to give them a try and see if you can get the headsets to connect.
Additionally, it seems bluetooth headset problems seems to be across all devices, and not just the a501, but Zoom, Transformer and Thrive as well. Hit and miss with what works. Most issues say the mic doesn't work.
I tried a couple of the apps with no joy on my plantronics earpiece but one of the widgets actually connects...for just 2 seconds...then disconnects...I think the capability is there and you are correct there is some file manipulation that needs to occur...
I have a friend in Egypt that is very good with android bluetooth, he is working on another project right now but when he finishes his current project I will send him these files...he might be able to figure it out ...