Bluetooth sounds terrible after new ROM - Tilt, TyTN II, MDA Vario III General

I'm currently using Dutty's Hybrid ROM released April 1 and using the default radio that comes with it. The BT is really bad sounding. Lots of crackling and pop's. I'm using the Z9 BlueAnt and it sounded fine on the stock ATT and Duttys March 28 release 5.2.19199. I've updated the Z9 firmware and it still sounds poor.
Can this be fixed by trying a dif radio? And if so, can anyone recommend a good radio?
Sorry if this has been answered before but i've been searching and not really finding anything.

What radio are you currently using?
Also there is a bluetooth audio fix cab out there somewhere that might help.

Currently using Radio 1.64.08.21 w/ [Apr 01 Updated] Dutty's WM6.1 Hybrid UC RTM ROM.
I'll try looking for this cab you speak of.
Edit: Its not volume, to me the volume is fine. It just sounds like old timey long distance phone call's on my fancy state of the art gizmo.

Related

Updates: Feedback on BT3900, radio 1.06.02, Wlan patch

There are a couple of standalone updates around but not too much information about any improvements or otherwise with the Blue Angel variants. So lets post our results and see if these updates are worth upgrading to. My XDA IIs is running
latest rom 1.31
bt patch 3900
radio 1.06.02
Bt upgrade seems to have made minimal changes, maybe a touch louder but thats all, no other changes noticed
Radio 1.06.02; cant say i notice any changes here as i didnt have any calling problems with ver 1.02. I upgraded cos of a problem with wifi which is still there
Anyone have anything to note about the wlan patch? If there are any other patches i missed please post what they are and what effects it has had
Hi.
I have spent a while looking for the patches. Can you point me in the right direction?
I actually went back to the Dangaard BT stuff...version 3500 and patch. This worked better for me with my Logitech BT Headset.
I upgraded the radio also to 1.06.02...can't really say it made a difference, but hell, it didn't hurt either...
BT Build 3900
Hi.
Upgraded to Build 3900 from 3500, found on the FTP server.
Only dif. is that my SE HBH 300 is now faster do disconect a call when pressing the on/of switch.
I was fooling around alot with my BA the day i installed the Build 3900, and right after installing the patch i tested it without a Soft Reset. I got a perfect connection without any crackling noise and a really good distance.
After a Soft Reset it was back to the old crackling noise and poor distance.
And i just cant recreate the scenario i had that day
Radio, dont know. Dident have any troubbles with the old one.
Wlan patch, wating for others to tell.
I upgraded my radio rom to 1.06.02 and BT Stack 3900 and found the Bluetooth still crackled on my old jabra bt 200.. just bought a BT800 today and it appears to work better even the caller display works.. with the radio stack upgrade i have had quite a lot of problems connecting to known wifi access points even when all the correct details were in. I also could not connect to BTOpenzone when standing under the access point (and yep i do have an account on it) so I re flashed the radio rom back to 1.06.00 and bluetooth 3900 with high quality audio patch and it all back to normal with abit mor BT Stability :roll:
Jabra BT800 worked straight out the box with no patch needed and has good loud audio 8) and a range of 10 meters ish still a bit crackly at 5 meters though
Marqnet said:
... so I re flashed the radio rom back to 1.06.00 and bluetooth 3900 with high quality audio patch and it all back to normal with abit mor BT Stability :roll:
Click to expand...
Click to collapse
So what you are saying is that radio version 1.06.02 interferes with WiFi somehow....that is interesting... :shock:
Do you remember what happened with your WiFi strength when you turned of BT, or have you not tried that?
Cheers,
HappyGoat
Hi as far as i am aware so far there has been no real issue with the Bluetooth and wifi interfering with each other or should i say i have not experienced any problems. the i ssue was just around using wifi and its connectivity problems i have had with open and unencrypted access points and encrypted ap,s the radio could see them but not connect. my xda came with 1.06.00 as standard and i was curious to see what the latter radio rom would offer. so as i didnt work for me i decided to go backward on step and all seems weel now. will agree interesting one and after trying a number of different 1.06.02 files as i thought the first was corrupt i just decided to revert back to a known to me working rom.
radio version difference
what is the difference in radio version 1.02 v 1.06?

ROM 2.08/2.87 for Cingular 8125....How Well Does It Work?

I have a Cingular 8125 currently flashed to the 2.17 ROM. I am mainly wondering if anyone has installed the 2.08/2.87 (whichever you prefer) ROM. I just wanted to see how the well the ROM performance is compared to 2.17...are there any problems in it that aren't problems in 2.17? Is it worth upgrading to?(when I have a stereo headset obviously)....thanks
Re: ROM 2.08/2.87 for Cingular 8125....How Well Does It Work
Centurion said:
I have a Cingular 8125 currently flashed to the 2.17 ROM. I am mainly wondering if anyone has installed the 2.08/2.87 (whichever you prefer) ROM. I just wanted to see how the well the ROM performance is compared to 2.17...are there any problems in it that aren't problems in 2.17? Is it worth upgrading to?(when I have a stereo headset obviously)....thanks
Click to expand...
Click to collapse
Stick with 2.17 unless you need A2DP. 2.08 (honestly I don't know why folks report 2.87 since on mine it reports properly as 2.08) is based on a pre-release AKU2 update (which is essentially a beta service pack) but people who want A2DP are ok with that and I haven't heard any complaints about the core OS.
Depends
I was definitely a fan of 2.17. Very fast, all the great AKU2 goodies (except a2dp). But once I got my Moto HT820 bluetooth headphones, I had to go with 2.08. 2.08 I not as fast as 2.17, but it has A2DP and it works GREAT! It's really amazing how good the audio sounds. One thing I noticed is when using my HT820 headphones and watching a windows media VIDEO, audio and video sync was messed up, due to performance hits from A2DP. But with good old overclocking through OmapClock, no more out of sync audio and video. MP3 playback with Windows Media and using A2DP was smooth and great sounding. I don't notice any faster battery draining, as long as the screen is off.
BTW, thanks SUMMITER! Your work on bringing us those Cingular Roms is much appreciated.
Re: Depends
apaje said:
I was definitely a fan of 2.17. Very fast, all the great AKU2 goodies (except a2dp). But once I got my Moto HT820 bluetooth headphones, I had to go with 2.08. 2.08 I not as fast as 2.17, but it has A2DP and it works GREAT! It's really amazing how good the audio sounds. One thing I noticed is when using my HT820 headphones and watching a windows media VIDEO, audio and video sync was messed up, due to performance hits from A2DP. But with good old overclocking through OmapClock, no more out of sync audio and video. MP3 playback with Windows Media and using A2DP was smooth and great sounding. I don't notice any faster battery draining, as long as the screen is off.
BTW, thanks SUMMITER! Your work on bringing us those Cingular Roms is much appreciated.
Click to expand...
Click to collapse
Just curious, which clock speed gave you good results w/ A2DP? Was 240 sufficient?
Does the 2.08 ROM include AVRCP? I really appreciate the comments, I wanted to make sure I wasn't going to jump into buying the Moto's for no reason...but thanks for the overclocking tip, I probably wouldn't have thought of that.
Summiter, I'm sure you've hear it 1000+ times, but thanks for releasing these ROM's...There are only so many people here who know how to make them, so thanks for being an active contributor.
Overclock speed for good A2DP
I just tried several clock speeds and it seems like 228 is the minimum speed for me. The videos I am testing are WMA9 videos. I think 240 is probably a better speed as I saw a few occasional hiccups at 228. Also, I tried Real media player and had a similar issue with out of sync audio and video at the default clock speed using A2DP. When I was using the 2.17 ROM, I used BlueCast to send normal headset audio through when watching WMA9 videos and didn't notice any hiccups at the default clock speed, so A2DP definitely is resource intensive. Anyone out there know how to really benchmark how much CPU process or memory A2DP uses?
i keep having to correct people on this.
the ROM is actually the 2.8.7 rom, where as the IPL/SPL IS 2.08. apparently in software they like to add 10 or higher in build numbers. so 2.16/2.17 is higher than 2.8.7. if you actually look at the rom version, it reports:
2.8.7.1
Where the 2.16/2.17 rom will show 2.17.
i don't know why people call it the 2.08 rom when that's the IPL/SPL version. sigh.
Re: ROM 2.08/2.87 for Cingular 8125....How Well Does It Work
Centurion said:
I have a Cingular 8125 currently flashed to the 2.17 ROM. I am mainly wondering if anyone has installed the 2.08/2.87 (whichever you prefer) ROM. I just wanted to see how the well the ROM performance is compared to 2.17...are there any problems in it that aren't problems in 2.17? Is it worth upgrading to?(when I have a stereo headset obviously)....thanks
Click to expand...
Click to collapse
Just loaded 2.08 because i needed a2dp for my bsh-100 anycom stereo headset. Headset works beatifully. No problems to report.
apparently you don't know how to read....
middler
I have the same Headset , but sound drops out permanently.
have you really no problem with the Anycom Headset?
darkjedi...I think by this point people have been calling it the 2.08 ROM for so long that it just makes it easier to refer to it as that....Is it wrong? Yes. But who cares?........2.08, 2.87, it's all the same...its got an 8 and it has A2DP...what else matters?
Oh, one more question...So I have the 2.17 ROM...and if I were to downgrade/upgrade(?) to the 2.08 ROM, how would I go about doing that? Unlock my phone both ways using lockiwiz and then run the 2.08 rom on the FTP? If I'm wrong, please tell me before I create a cool looking brick. 8)
sigh, people's ignorance and lack of intellegence really astounds me. why don't we just shorten EVERYTHING because we're too damn lazy to do anything about it?? start everything with u and r and 2 and 4. it really shames me at how many people have murdered the english language because they are too damn lazy to say the real word. i'll excuse foreigners as they don't know the language too well; but seriously, people born in this country have gotten ridiculously more retarded as the years have passed. and really, saying 2.08 and 2.87 is the exact same thing, have the exact same number of digits, so why is it so damned hard to say 2.87 when that's what it actually is? maybe everyone should start saying 1+1 = 6 just because they want to.
duri
Been using for two days, and has worked flawlessly.
duri
Been using for two days, and has worked flawlessly.

newest version of htc audio manager

does anyone know what the newest version/build of htc audio manager is that will work with the kaiser. i've search for the different builds, and the only thing i can find is 1.02 build (409.721), and i'm starting to wonder how updated it is because i know i downloaded this one months ago. just curious because i dont know if it is because of wm 6.1 on my tilt, but it was extremely buggy today w/ my bluetooth headset (worse than with wm6)

Need software patch or tweak for Jawbone problem

I've looked everywhere on this site and maybe I meissed it but I have a jawbone 2 and this is actually my second jawbone through warranty , when I call someone or when someone calls me my jawbone headset brakes up and sounds like im out of range, when I put the jawbone a inche from my tilt then it works perfect .... I need a software patch or something and if this is a subject that has already been resloved please send me the link.
Hope this helps..
I have a newish kaiser and a jawbone2. I flashed several roms, several radios, always ended up finding an issue somewhere, the most recent being the exact persormance issues you've mentioned with the bt/hset.
I'm now using the following, with absolutely zero problems and wonderful quality hands-free, even whilst driving the car @ 70mph with music playing.
Setup:
-rom version: 3.28.61.0. wwe
-rom date: 05/02/08
-radio: 1.65.28.25
-protocol: 25.98.40.07h
It's an updated version of the stock orangeuk rom which came with the device.
Good luck.
Im new to all of this how do I get that on my device?
I'm not comfortable enough with it to explain it myself, so I'll leave it to the experts.
Try here:
http://forum.xda-developers.com/showthread.php?t=433835

No bluetooth handsfree with cooked roms

When I flash my HD with a 1.56 cooked rom, I'm unable to connect with my handsfree. I can pair with the handsfree through bluetooth but I can not hear or speak to anyone.
If I flash with the stock HTC 1.56 rom, I can pair and talk through the handsfree.
Is there a fix for this? I've tried several cooked roms and the outcome is the same.
Thanks!
backstep said:
When I flash my HD with a 1.56 cooked rom, I'm unable to connect with my handsfree. I can pair with the handsfree through bluetooth but I can not hear or speak to anyone.
If I flash with the stock HTC 1.56 rom, I can pair and talk through the handsfree.
Is there a fix for this? I've tried several cooked roms and the outcome is the same.
Thanks!
Click to expand...
Click to collapse
I have DavidEuck 8.5 running and the bluetooth handsfree with my JVC carkit works fine. Can you try to pair with another bluetooth handsfree set and see if thats works fine? I would recommend at least upgrading to the latest radio.
backstep said:
When I flash my HD with a 1.56 cooked rom, I'm unable to connect with my handsfree. I can pair with the handsfree through bluetooth but I can not hear or speak to anyone.
If I flash with the stock HTC 1.56 rom, I can pair and talk through the handsfree.
Is there a fix for this? I've tried several cooked roms and the outcome is the same.
Thanks!
Click to expand...
Click to collapse
i have the same problem with most of the cooked roms specilly some times i can not hear the voice of other party this problem arrises with Miri's rom that i like it and Duty's rom that is very famous
for me stock roms and kwbr rom works fine
i have tested 3 devices Motorlla car kit, the expensive new Nokia sterio bluetooth headphone and sony erecsson sterio bluetooth head phone they all have problem with some cooked roms; i hope i can find a wm 6.5 rom that does not have this problem specially with good memory management like miri and kwbr that doesn't eat lots of memory.
Me, too. I am using daviddeuck v6. After 3 weeks sometimes it works and sometimes I cannot hear the other party.
I tried 2 jabra models with the same results.
Same issue
I had the same issue with my parrot 3200LS and Dutty's extreme 2.2/ Laurentius26's L26_THDV2.2_Ultimate Roms.
I even tried JETware Hands-free Extension for Windows Mobile phones (http://www.jetwaremobile.com) --supercool program btw!
But all to no extent.
Reflashing back to Laurentius26's L26_THDV7.5_WWE CE OS 5.2.20769 (Build 20769.1.4.5 L26) ROM "solved" the problem for me.
Now I get my phone's ringtones through my parrot (and thus my car-hi speakers ). Hope the problem is solved in newer roms...
(Btw, great job with your ROMs guys!! )
Y
Happens to me to.
ROM:
dutty v3.4
perhaps we could make a List of working/not worling Roms.
For me it's an essential feature for ROM choice.
Epecially bought a Radio for this feature...
Almost same for me.
Duttys v 3.4 ROM
Ford Car Kit (just talk, no music) connects and works without any problems.
iTech Clip R35 (A2DP, AVRCP) will not pair at all.
(I don't know if the profiles mean anything. Just remembered that there was a lot of talk about supported profiles in the R35 manual.)
brgds
Royan
Use Onkologs Lite-Rom and it works perfect.
I found i couldnt pair my phone with a few handsfree devices i was testing in a shop - seems there is a problem with the bluetooth stack and the newer roms. Odd this hasnt been reported sooner
i feel there is a problem with the configuration between windows and manilla some where or the driver for blue tooth is not complete that is why it loses the connection somewhere for most of the cooked roms
I agree, there must be something wrong with the bluetooth stack.
When I use a 1.14 ROM, I can hear and speak to people through my hands-free. But, when I flash a 1.56 ROM all I get is "dead air" when I answer a call through my hands-free.
I've tried flashing to Dutty's, Miri's, Laurentius26's, Topix's and a few other rom's, with the same result, I am unable to hear & talk to the other person on my hands-free.
I also tried updating to the 1.14 radio and I've tried older radio's and I still have the same problem.
Starting July 1st, my state will require drivers to use hands-free devices when dialing and driving.
backstep said:
I agree, there must be something wrong with the bluetooth stack.
When I use a 1.14 ROM, I can hear and speak to people through my hands-free. But, when I flash a 1.56 ROM all I get is "dead air" when I answer a call through my hands-free.
I've tried flashing to Dutty's, Miri's, Laurentius26's, Topix's and a few other rom's, with the same result, I am unable to hear & talk to the other person on my hands-free.
I also tried updating to the 1.14 radio and I've tried older radio's and I still have the same problem.
Starting July 1st, my state will require drivers to use hands-free devices when dialing and driving.
Click to expand...
Click to collapse
after trying almost all the new roms i returned back to the latest stock rom (28-4-2009) Bluetooth and every thing works absolutely perfect and it has got excellent memory management (only 32% with full loaded program), i use this rom when i want to rely on my HD.
by the way i think all the kwbr roms also works fine with bt. i wish i can find a 6.5 rom that works fine with blue tooth and has got good memory managemt, just waiting may be miri will do something, his rom got good memory management that is very imprtant for me
After the "SD card not shown", this is another weird report by using cooked ROM
has anyone got bluetooth devices to pair with a cooked 6.5 ROM ?
if not this is a pretty major problem ??
Yes I have.
I just got Miri's V15 pairing with my factory fitted Range Rover bluetooth kit and it works perfectly including giving access to the address book.
Previously I was using WM6.1 and many of Dutty's ROMs and I had intermittent drop outs with the car and phone.
Miri's ROM has upgraded my radio so I can't be sure if WM6.5 fixed the problem or if it was the new radio, but for the first time in 6 months I actually have a working hands free kit in my car
Royan said:
Almost same for me.
Duttys v 3.4 ROM
Ford Car Kit (just talk, no music) connects and works without any problems.
iTech Clip R35 (A2DP, AVRCP) will not pair at all.
(I don't know if the profiles mean anything. Just remembered that there was a lot of talk about supported profiles in the R35 manual.)
brgds
Royan
Click to expand...
Click to collapse
Well, that's me fixed...
Both car and iTech Clip works with Duttys 3.7/2.1 ROM.
And I'm ashamed to say; that the clip didn't connect earlier was my fault...
I used default code 0000 as stated in iTech's documentation, not the real default code of 8888...
Once I used the correct code, all was well...
brgds
Royan
I am using now Laurentius 2.1. My bluetoothheadset that suports only handsfree talking works properly. With my Jabra BT8010 only stereo music works, handsfree is a game of luck.
Hope any ROM expert will fix this in the future. For me it is one of the most important features of my TOUCH HD.
working!
Hi,
yesterday I flashed to Duttys 3.9 Turbo - and I love it!
BT works as A2DP & Handsfree!
beside it's very fast - what else we need
frottage said:
has anyone got bluetooth devices to pair with a cooked 6.5 ROM ?
if not this is a pretty major problem ??
Click to expand...
Click to collapse
Using Energy's 6.5 june 16th version.. Works PERFECT with my brand new Nokia BH-904 (which also is great)
it works in miri's rom as well plus you have lots of free memory when you really need it

Categories

Resources