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
Related
hi guys, i couldnt help noticing that when i previously used nokia 6600 (symbian s60) they had few 3rd party that is able to make use of their audio mechanism during callls. for example, one software can make selected background noise for opposite callers so they think that u are at a train station for example when infact u r silently at home. another software is an on board answering machine, which after the phone rang for a few times it answer the fonecall with your automated recorded voice and recorded a msg left by the caller on the fone. this is convenient for us so we dont need to call back our voicemail and reduce cost as well as some telco charge to use their voicemail service. im surprised these kind of software have not came out for our windows mobile device when its already available for symbian. im sure it shouldnt be that hard to make it. any coder expert wanna give it a go??
cutefox, what kind of searches have you made for this software on this board? Did you have much luck?
V
i already tried commercial such as handango and pocket gear.. even freeware sites also no luck.. jus dun understand why no 1 made one yet.. shouldnt b too hard to make one.. it will be a big market to sell such a software for our ppc phone device now that more devices is coming out..
Cutefox: have you tried searching this board? Let me save you the effort, but it'll be a good idea next time. It's not generally considered possible, at least on WM2003 devices because of both hardware and software limitations. It's not that no one has thought of it before: someone seems to think of it approximately every two days... but there are many many threads on this issue.
V
Look at what I said here...
http://forum.xda-developers.com/viewtopic.php?t=9761
That sums up why we can't do it using the api's available to us now. The funny thing is the way bluetooth sends the audio stream to a headset. Obviously the data is getting there somehow but I suspect it is not (directly) via windows. Dose anyone know if the radio hardware for bluetooth is connected to the radio hardware for the phone? My guess is that if you could write a program that windows "sees" as a headset then you could get the audio that way. But thats a problem in itself.
I would love this kind of program myself. How is it that such usefull devices with so many capeabilities can be kept secret from us. We can't use the camera, we can't get the cell id on towers, we can't programatically controll the partnerships in blutooth, we cant get the audio stream of our own phone, the events on some ppc's that control brightness are secret..... the list goes on. This kind of #@!!$$ is going to hurt the future of these devices which I otherwise love.
OdeeanRDeathshead: I had read your previous posts, and as ever, very interesting and informative reading. I had the same idea regarding a "dummy" bluetooth device a while back, but mamaich put me in my place!
http://forum.xda-developers.com/viewtopic.php?p=179839#179839
V
thanks vijay555, thats what I have suspected about the hardware. What I want to do is a bit different. The bluetooth can communicate to many devices at once. If your program could appear to be a headset to the os, then the phone bluetooth hardware could transmit the audio to the headset at the same time your program uses bluetooth to receive it. Kind of like a loop out of the box to bridge the lack of functionality. This shifts the problem to how dose a hardware bluetooth headset communicate. Emulate this and we are on a winner. I don't think I have the willingness to pull my devices appart. I also do not have the money for some of the hardware (eg good digital oscilliscope) that I would need to measure whats going on. I did read that microsoft are about to expose some new api to allow control over the pairing process (but not the audio stream). I hope that we get some soon.
Is there going to be any new (for 2005) free development tools like the evc versions used today?
OdeeanRDeathshead: re eVC, I don't think so. The "express editions" are free, but they specifically omit the functionality to develop "mobile solutions".
Re the loop back. That's a good idea. I think mamaich is our best bet on schematics, I think that would be very helpful. As you "rave", it's mindboggling that Microsoft still haven't revealed or implemented a way to interact with the audio channels. It must have been one of the first things one could imagine doing once you develop a PDA with a phone stuck on the back of it.
Any idea if the bluetooth stacks could support transmitting and receiving simultaneously in this manner? I know some of the boys are working on alternative bluetooth support for the stereo headset profiles, so they might be able to shed some light on the issues involved. I guess the processor overhead could be hefty, but for the benefit it would be beneficial.
V
OK, so I have spent the better part of the last week banging my head against my desk trying to get this to work. I have tried every registry hack I can find on the 'net trying to get my bluetooth headset to work with Voice Command on my Siemens SX66 and I've gotten exactly nowhere. I actually have a second PPC Phone running WM2003 ( not the Second Edition) and the hacks to the registry work fantastic over it. So, this is not supposed to be possible in the SE version, however these forums are chock full of help for issues that were made possible by the good people here putting a little ingenuity into their software, so "impossible" is not necessarily a word in my vocabulary.
Any ideas, thoughts, feelings at all as to how this might be possible? [/u]
I hope someone is able to help me.
Okay I have the Wizard, upgraded to Wizard Mobile 6.
Shortly after, all my bluetooth devices (car kit, headset...) had their microphones die. In other words nobody could hear me when speaking through any kind of bluetooth.
I then flashed the Radio ROM to a different version, and bluetooth was repaired. But now the problem has returned for no reason.
Why does my Wizard's bluetooth audio in keep failing, yet its speaker works fine and I can hear other people?
Is there a recommended update to the Bluetooth Stack I can try?
CJSnet said:
I hope someone is able to help me.
Okay I have the Wizard, upgraded to Wizard Mobile 6.
Shortly after, all my bluetooth devices (car kit, headset...) had their microphones die. In other words nobody could hear me when speaking through any kind of bluetooth.
I then flashed the Radio ROM to a different version, and bluetooth was repaired. But now the problem has returned for no reason.
Why does my Wizard's bluetooth audio in keep failing, yet its output works fine and I can hear other people?
Is there a recommended update to the Bluetooth Stack I can try?
Click to expand...
Click to collapse
I do have exactly the same problem. After flashing XDA Mobile 6 Release 3, microphone has worked for couple of days, and then suddenly died. Interesting, microphone is working with Notes but not with phone. I went back to
XDA Mobile 6 Release 2 for some other reasons (read: 2MB more free memory for critical application) but the problem with Bluetooth microphone remains. Radio is 2.25. Any advice?
--
Pogo
There are also at least 3 people at the Wizard Mobile 6 thread with the same issue. Very surprised none of the experts here have been able to propose a fix. Makes the phone virtually worthless if you can't use it in the car etc.
As a workaround, I have found if you mute then unmute the phone volume, the issue is sometimes temporarily resolved for a short time. It always comes back though
I have been asked to join this thread. Per a PM:
We love the ROM you have provided, and are very thankful, however it was not until installing it that this issue arose. It does not seem fair to leave a number of people with a phone that is unusable for 'phone calls'.
Click to expand...
Click to collapse
(Bolding added by me)
I don't know what to tell you. If the rom doesn't work for you, then don't use it... Don't tell me its "not fair". I use MS Voice Command, and XM6r3 and have never seen this issue with my Bluetooth headset (Jawbone). I've also tested this out with a Plantronics Explorer 210 headset that I have and it has not problems with XM6r3 either. My A2DP headset (Spider) also works fine on XM6r3 with MS VC. I've stated this in the past when people have said they have BT issues on my rom. Sorry, but I can't reproduce it, so its hard for me to fix something that isn't broken for me.
Try this... Do a hardreset on your device (take a backup first if you want), then leave it as the base rom with NOTHING extra added. Run that way for a few days (how ever long it has taken before) and see if the problem happens again. If it doesn't then its not my rom but something being added to it (probably screwing with the registry someplace). If it does happen, then as I've stated before, I've seen a number of BT devices be flakey on WM6 (especially car kits). Try a different rom then. If someone with the problem can pin it down, I'll be happy to do what it takes to fix this issue if its something in the rom that is causing it.
Thanks mfrazz. What wasn't fair was not the bug, but that you had not responded to previous mentions of it, i.e. not fair to leave us with it. We love the ROM and put a lot of our life in your hands in a way, as we rely on our device so much for work and play. Hope you understand.
Now then, I have already tried a hard reset and the problem never occurs, until WM6 is put back on. Sure, 'use another ROM' is all very well, but we love yours - again, hope you appreciate the sentiment. If you're in a relationship, are you the kind of guy who tells a girl who loves you, 'find another boyfriend', or do you try to make it work
SO, I am wondering if this is related to the glitch you mention where sometimes when switching out of vibrate mode, the ring tone becomes muted. For that, your solution is to play the ringtone again, then it becomes unmuted.
Similarly, our Bluetooth devices mic's are being muted, and if we mute then unmute them again, then they become unmuted. A link that helps point you in the right direction?
Please note, this is not certain bluetooth devices being 'flaky', this is ALL devices. 4 at the latest count, including rock solid Nokia CARK7W car kits and Jabra headsets.
Some people put it down to MS Voice Command, which I have never installed. What does that program do, do you know, to cause the bug? Again I hope that might help point you in the right direction.
Please don't dump us Let's try to fix what is wrong in this relationship
BT problem solved?
CJSnet - not sure if you have resolved this. I was having the same problem and noticed people with reTouched dialer were not, so I loaded that dialer and the problems went away. I am using a Plantronics Voyager 510. Seems the problem might be with the standard dialer.
Hope this helps
CJSnet said:
There are also at least 3 people at the Wizard Mobile 6 thread with the same issue. Very surprised none of the experts here have been able to propose a fix. Makes the phone virtually worthless if you can't use it in the car etc.
As a workaround, I have found if you mute then unmute the phone volume, the issue is temporarily resolved for a short time. It always comes back though
Click to expand...
Click to collapse
Thanks, I'll give that a try. However WM6 has pretty much finished the Wizard for me, and I'm hoping to get a TyTN II soon as a replacement. Shame.
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.
Hello.
Before you tell me... I already searched the forum and I can see many posts about the problems with BlueTooth in the Hero based ROM's, but none of these posts I read (I could have missed some, of course) say what the problems are exactly, so I don't know if it can be a problem for me or not.
The only things that I need from BT are connection to the Parrot CK3000 handsfree on my car, and to send/receive files over BT. Ocassionally I will use the Magic as a 3G modem, but I can do it through USB if not working through BT.
Are these BT features affected by these BT problems on Hero based ROM's?
Thanks in advance.
Not sure if this applies to all hero roms but in the 'jacxheroskiv' rom the problem is a missing shared object (just a missing file in the filesystem)
http://forum.xda-developers.com/showpost.php?p=4479554&postcount=96
Hi There
At the moment Bluetooth is problematic on all hero roms for the sapphire or otherwise. Audio head sets (wireless headphones) seem to work ok but everything else doesn't. So unfortunately your car kit won't work. (I have the same one, it pairs but the audio is garbled) File sharing on the other hand is a problem for all the androids so far (There is an app on the market that provides the functionality but it's not as elegant as it could be) so don't expect that to work on hero roms. I haven't tried Bluetooth tethering because WiFi tether works so well. Perhaps someone else could comment.
Now for the difficult part...
So far as I can tell a willing developer, correct me if I'm wrong, could make the Bluetooth work if the source code for the hero was made available (should be available in a few months if the recent release of the sapphires source code is anything to go by) There seem to be quite a number of people who need this functionality so I'm sure one of the rom cookers will get to it but unfortunately there is no way to know exactly when. For this reason I've decided to stick to the ion roms for now. In any event, Touchflo/Sense UI will be made officially available for the magics in due course...for a price of course
On another note any support financial or otherwise is greatly appreciated by the developers so if you want to encourage a particular functionality a few bucks and a friendly message will go a long way. Please remember though that the developers do this kind of thing for the love of it and provide no explicit support for their roms. Any and all risk is taken upon yourself but in most cases caveats will have been picked up by someone before hand.
Sorry if I've mentioned some things you already knew but I thought to add some info applicable to other newcomers.
Enjoy hacking!!
Thanks both.
I guess I'll have to use a non-Hero ROM then. As for the BT file transfer, I've seen at least one Cupcake ROM with it enabled and available as an option in the BT menu. I don't know what ROM it was though, I think I saw it in a Youtube video.
P.S.: I noticed that this thread was moved to "Sapphire general", sorry for put it in "development", I did it for it was related to Hero ROM's. Thanks mods for move it.
A2DP works for my Sony Ericsson HBH-DS205 - music streams flawlessly.
However, the call feature does not work - is this another common bluetooth problem with the HEROs?