Related
I'm having several problems with my Qtek 9090
There's a rather loud constant high-pitched noise comming from the screen whenever it is turned on (which is when the device is on!). At first I though it was comming from the speaker, but the screen is definitely the source of the noise. It doesn't matter if the backlight is on or off.
People can't hear what I say when using the phone - it makes no difference whether I use the included headphones or just speak directly into the microphone.
I haven't been able to find a BT headset that works with it. They all have the same problem; The sound scratch so much they're unusable. I tried 3 different brands that all works well with my 2020!
The GSM link often "falls out" - even though there's plenty of link the phone doesn't work (nothing happens when I try to call someone). A soft reset solves this problem!
As you can see, I can hardly use the device as a phone at all I've had the device replaced once, but all the problems persists on the replacement.
Does anyone have similar problems?
1. No, don't have this problem. Strange that it happened on the replacement too.
2. Yes.
3. I have just ordered a jabra headset in the hope it will fix problem#2.
4. Yes.
These problems with GSM are a real headache. One of the primary reasons for buying the PDA2k was to consolidate my mobile into one device. I have seen other people experiencing such problems but from what I could gather, voice over BT worked much better. Have you updated the ROM since you bought it? I should know the answer to 3 today, if DHL delivers, and I can tell you I will not be a happy man if the answer is Yes!
Try a Motorola HS810 headset... works fine for me.
harry_mb said:
1. No, don't have this problem. Strange that it happened on the replacement too.
2. Yes.
3. I have just ordered a jabra headset in the hope it will fix problem#2.
4. Yes.
These problems with GSM are a real headache. One of the primary reasons for buying the PDA2k was to consolidate my mobile into one device. I have seen other people experiencing such problems but from what I could gather, voice over BT worked much better. Have you updated the ROM since you bought it? I should know the answer to 3 today, if DHL delivers, and I can tell you I will not be a happy man if the answer is Yes!
Click to expand...
Click to collapse
I've already tried Jabra Freespeak 250, which didn't work for me
No I haven't updated the ROM as I've been told by the supplier that no new version is available yet!
outz said:
Try a Motorola HS810 headset... works fine for me.
Click to expand...
Click to collapse
I also tried both a Motorola and a SonyEricsson BT headset, but I don't remember the specific models - they both scratched immensely
i use SE 60 and it works ok
As you said, the Jabra250 is pretty much unusable!
Crackling is not constant but goes in waves, even though I do not move.
Am at a bit of a loss what to do now... the device is great apart from this.
>> People can't hear what I say when using the phone - it makes no difference whether I use the included headphones or just speak directly into the microphone
yes PBT read my other post
I have the same problem!!
it is scandalous to sel an device with this big defect!!
Sony HBH-660 works good for me.
People say that they can't hear me when I use the handset, but I don't have any crackling, etc with the headset and voice is clear. You just never know if the headset is going to connect when the phone rings though.
sound from screen
there's a rather loud constant high-pitched noise comming from the screen whenever it is turned on (which is when the device is on!). At first I though it was comming from the speaker, but the screen is definitely the source of the noise. It doesn't matter if the backlight is on or off
Click to expand...
Click to collapse
I have this problem also, I was told to use the new rom but this has made no difference, Please let me know if you have found a solution
[/quote]
Guys,
the hissing coming from the screen is a power supply problem. keep swapping phones until it goes away! I used to build switching power supply and the hissing (in a system designed to operate well above 20kHz) is only able to be heared when unstable, inductor core or cap is broken. The hissing is very 'not normal'.
It appears that the Q9090 is standing out as having more problems than the MDAIII, one is the mic volume, most of the other phones are not complaining about this so there may be something with they way the Q9090 are updated or shipped.
With the Jabra 250, don't forget to pair it pressing BOTH the volume and phone button on the headset on discovery with the 9090.(On bonding, turn off headset, turn on again pressing both buttons)
Funny thing is, I had the cracking also. I deleted the headset in BT manager and paired it again as described above. Now it works ok.
Hi,
I bought a Qtek 9090 a few days ago and I also have the same problem with volume level. People can't hear me when speaking, either with the headset or base microphone.
Using a different headset doesn't help (that's even worse sometimes) but I didn't try a BT heaset (and I don't want to as it would raise potential connection problems). I'm going to contact Qtek for support on this...
Pierre
I too am having problems with the Jabra 250 BT headset and my SPV M2000. The Jabra 250 worked fine on the XDAII but is terribly crackly on the newer model.
This is even when pairing it with the enhanced pairing of pressing Volume Up and Phone button together to pair.
Any ideas?
qtek 9090 bluetooth problem
Hi All,
I have new qtek9090 with cellink bluetooth headset. It is work normal, but i am loosing connection to headset each time qtek go to stand by mode. I need to switch off/on the bluetooth in order to restore the connection. Any ideas?
I often get a message stating:
"The Bluetooth Radio failed to turn ON due to insufficient driver momory available. You must perform a normal reset before you can turn ON the Bluetooth Radio."
Does your device also give you this message?
Is it also using the Broadcom "Bluetooth for Windows CE BT-PPC/PE Version 1.0.0 Build 2200"?
Interested to know if you have the same problems with the same bluetooth driver.
same problem
My qtek 9090 shows te same problem
This is a known problem with the Blue Angel, unfortunately, until they bring out a fix, all you can do is a soft reset.
upgrade
hi all,
how can i get updates from www.imateclub.com?
I can't register there, because I have qtek 9090 and not i-mate
thanks
O2 Sourced info on which BT headsets work
See: http://www.my-xda.com/downloads/Other_Bluetooth.pdf
Hi I'm new to the site, i had read a lot post about upgrading roms from different companys, i read people describe how good the a2dp quilty is, but the problems comes, i first upgraded the rom to T-Mobile , then i found there are a high pitch nosie, at first, i though it was just my earphone, after i changed it, it still the same, then i upgrade to the QTEK rom, the nosie still comes, the nosie comes as the singer start to sing!!! it makes my so dizzy, i had try to link my BT to my PC, but they sound much different! no nosie plus clearer sound!
the second problem is that when a phone call-in, the ringtone goes via BT rather than built-in speaker???
the third problem is if you set ur BT as both hands free/set and wireless stero, during a connected phone call, if you press any button on the dial pad, all the sound will gone, but the phone is still connected, i found this problem when i using my voice mail?!
also after i update to the non-O2 rom, my phone is no longer accept any MMS, i already config all the setting from O2, is just that i don't have my MMS acount appear on my mail box. i also try the .cab setting file too!
My A2DP BT is i-Tech S35
ROM Version: 1.30.77WWE (QTEK)
Radio Version: 1.09.00 (QTEK)
ExtROM Version: 1.13.188 WWE (O2)
Many Thanks!!!
Was it just me than having this problem???
- I've not the first problem.
- I've the second problem
- I never experienced third problem
:wink:
http://forum.xda-developers.com/viewtopic.php?t=46540
Click on the above link , download the file and run it on your phone, do not alter any of the options, just click next on everything it will fix your MMS problem
thx a ur advice coff... but it still doesn't work, plus i starting to think that the nosie might cause by my s35, due to the campasility.. (sorry can't spell)
Hi MicmiC901,
Yes, it probably is something "locally" with your phone/headset/area/etc, since I also have same experience as asci, meaning;
1. NO, don't have that problem
2. YES, I have same issue (to me this is actually OK, since when headset is connected, I WANT it to only ring in the headset)
3. NO, never experienced this problem
I use the latest Qtek ROM with AKU2 and A2DP, but have never experienced that high-frequent-noise-issue you mention with any other of the A2DP ROMs on my JasJar (TMobile Germany ROM, a custom-ROM from the forums).
so RonnyGydar, which bt headset u using @ the moment? i just try with my friends logitech bt headphone, it get worse than my i.tech, sound get Stuttering , so i think i better change a new bt, would u recommand moto ht-820?
Hi MicmiC901,
Sorry the veeery slow response...but now I have even one more BT Stereo headset...so then you get the "bonus" of even more info in my reply!
I have 3 BT Stereo Headsets, and here is a short summary of experience of them all.
HP BT Stereo Headphones (same HW as the Logitech ones as I understand).
Sound is good, clear, OK bass. Nothing exceptional, but I was very pleased with them. Sound could be a bit higher at the highest volume...if you plan to use then in noisy environments...but not really an issue...since they are quite loud.
Motorola HS820
Soundwise (clarity and bass) very simmilar to the HP ones...can't point my finger on any differences. But they seem actually a little less loud than the HP ones...so with these I struggeled to hear Podcasts when I sat on a bus going through tunnels. The HP headphones are slightly louder, I think.
Bonus of these are the excellent batterylife and miniUSB plug...plus the HP ones do not have a microphone, so the HP ones are only for music. So I would easily chose the Motorola's before the HP headphones.
One minus for me with the Motorola's are that they hurt my ears after a couple of hours of use. ...that at lack of "powerfull" bass, got me to look at the i-Tech BluePRO's...
i-Tech BluePRO
These have very good bass (and they sure look like they should have it too...pretty big earmufflers...with these, you look like you are working at a construction site or something, but the clarity of the sound is actually worse than HP and Motorola...they sound a bit fuzzy.
...but I still use these all the time...mainly for two reasons. One is the excellent bass (I like to listen to techno and trance...and then bass is important, the other is that they isolate outside sounds (due to the enormous padding), so I can have the sound as low as I prefer...and STILL hear all my music without disturbance from other sounds in the environment (like sitting on the bus in a tunnel, or at a noise Gym).
It also seems that there is quite a bit difference in how the different manufacturers implement BT profiles.
My Motorola and i-Tech BluePRO have problems with "Pause/Resume"-button on headset when used with my JasJar (Pause works, but not resume...or opposite...not sure which it was, dont have the headsets with me today)...but the HP ones does not (I tested them a couple of times, and the HP headphones worked all the time)!?
Re-connection after a time without use seems also to vary a bit. The Motorola I can turn off/on the headset, and they reconnect automatically to my JasJar. The i-Tech BluePRO's I must choose re-connect in "Bluetooth settings" on my JasJar every time I want to use them.
The "famous" "lag-issue" everybody experiences I experience with all my headphones in some situations...and it does not seem any better or worse among the headsets. It seems to also be affected by general radio disturbance, since I have a lot of problems with lag at work, but no problems at all at the Gym (which is good for me...since that is the place I am most happy with having my wireless headphones), and some issues at home.
Hope this was of any help!
actually i have the problem micmic is talking about.. it happened when i upgraded my wiz to a newer rom to get the a2dp function. eventually i do not have a bt.stereo -headset yet.. (coming in about 2 weeks) but i have the issues with the sound. it's almost like a bad bitrate or something? ..wierd it is since i remains even if i downgrade my rom. =/
Hi epluribus and MicmiC901,
Is the "stuttering" you both mentioning the same as I call "occational lag"?
IF it is...it you should certainly not have it when you do the following test;
1. Reset your JasJar/Universal (to clean memmory completely)
2. Started listening to music over headset with...
3. The Universal lying on the desk in front of you completely still 50cm from your face
4. You sitting completely still
5. No WiFi on close to you.
...this test is completely overkill...but if it STILL stutters in that "controlled scenario"...well then it must be something different with your Universal or headset HW. Cause I can walk around with my JasJar (also in areas I know there are 5-6 WiFi connections active...like my appartment), and even put the JasJar on the table and walk 5-10 meters away from it...and have no or at least nothing more than an "occational stutter"/"lag".
It seems to be two major factors affecting this "stuttering"/"lag" (from my experiences at least...I have used A2DP a lot with my Universal...couple of hours every day);
1. Universal struggling outputting(RAM/CPU...or both!?)
One help here is to apply the registry "A2DP priority" fix (found it in the forums here).
Another is to close all programs before using it (I usually do not do this...I usually only do it in hindsight when I get the problem).
2. Signal between Universal and headset struggling (obstructions between Universal and headset, WiFi nearby, so forth)
I for example get this problem if I put my Universal in my trouser pocket (I know, I must have big pockets, and walk around, I get stuttering/lag occationally. If I then take it out, and hold it in my hand farily still when I walk...no stuttering. I have found, that when I walk, it is OK to have it in my backpack/rugsack...then for some reason it very rearly stutters...so I usually do that.
But when I walk of the bus at work, and walk into the "campus" of my workplace, which is cramped with radiotransmitters (is norways largest Telecom company)...I get a lot of stuttering, and need to take it out of backpack, and hold it in my hand, at it gets a lot better.
In short: A2DP with the Universal works, but is sensitive to disturbance/obstructions/moving around...and to make it worse, it is also sometimes dependant of the Universal itself struggling with CPU/RAM.
I have BTW had the exact same problems before with Qtek2020 and Qtek9090 (which I got hold of some "A2DP patches", when I had those devices). ...but I really had a LOT more stuttering with those two...so much so, that I never used A2DP with them on a daily basis.
...so it can seem that HTC is getting slightly better on each new device...?
Hope this info can be of some use!
...but it might not...if my assumption at the beginning here is wrong, and your "stuttering"-issue is something completely different than the "lag"-issue I talk about!?
iam currently using latest rom from dopod and motorola 820, although the two earpiece have sounds it is only mono, can someone help to make it stereo? o recomend what rom to use, thanks
In order to have stereo audio on a Bluetooth device, you need a profile called A2DP, which is currently only supported by the latest Qtek Universal ROM at the moment:
ftp://xda:[email protected]_Updates/UNI_QTEK_13077_176_10900_WWE.exe
Dopod has not released a ROM supporting A2DP yet.
thanks for the help, God bless
No problem. Do let us know whether it works well or not.
it works, i have stereo sound, but need improvements, in a song the bluetoth stops 3 to 4 times when playing, the player dont stop its the motorola 820 that stops several times.
I did come across a post with a patch for the A2DP flaw the other day. It's somewhere on this site - do a search and see if you're lucky.
Found it: http://forum.xda-developers.com/viewtopic.php?t=46811&highlight=universal+a2dp
It worked for me for a little while so try it.
Hi,
I have used A2DP a lot with my JasJar the last 4-5 months, and had written a summary of my experiences with this "lag/stuttering"-issue in another thread here...I have copied the most essential of that text below...might be usefull info for you;
-----------------------------------------------------------------------------------
It seems to be two major factors affecting this "stuttering"/"lag" (from my experiences at least...I have used A2DP a lot with my Universal...couple of hours every day);
1. Universal struggling outputting(RAM/CPU...or both!?)
One help here is to apply the registry "A2DP priority" fix (found it in the forums here...and so did richardlai).
Another is to close all programs before using it (I usually do not do this...I usually only do it in hindsight when I get the problem).
2. Signal between Universal and headset struggling (obstructions between Universal and headset, WiFi nearby, so forth)
I for example get this problem if I put my Universal in my trouser pocket (I know, I must have big pockets, and walk around, I get stuttering/lag occationally. If I then take it out, and hold it in my hand farily still when I walk...no stuttering. I have found, that when I walk, it is Ok to have it in my backpack/rugsack...then for some reason it very rearly stutters...so I usually do that.
But when I walk of the bus at work, and walk into the "campus" of my workplace, which is cramped with radiotransmitters (is norways largest Telecom company)...I get a lot of stuttering, and need to take it out of backpack, and hold it in my hand, at it gets a lot better.
In short: A2DP with the Universal works, but is sensitive to disturbance/obstructions/moving around...and to make it worse, it is also sometimes dependant of the Universal itself struggling with CPU/RAM. So you can not totally get rid of the problem...but you can do a lot to minimize it...I almost never experience it now...except in the campus-area at work that is.
I have BTW had the exact same problems before with Qtek 2020 and Qtek9090 (which I got hold of some "A2DP patches", when I had those devices). ...but I really had a LOT more stuttering with those two...so much so, that I never used A2DP with them on a daily basis.
-----------------------------------------------------------------------------------
I also wrote a short post on my experiences with the different stereo headsets I have...yes, they actually act a little bit different it seems (regarding resume/pause button, and how easy/automatic they "reconnect"). You can see it here; http://forum.xda-developers.com/viewtopic.php?t=47977
Hope this is of some help for you!
RonnyGydar: I came across your little summary a little while ago and have done the registry fix, but the problem still exists! Do you think altering the value in some way would help?
richardlai,
I added the registry value manually...found a reg-file (or was it a CAB-file!?) that supposedly should add it...but when I checked later the key was still not added in the registry?
So I added it manually.
BUT, I do still have the problem...but that seems to be radio interference/distance so forth...since when I hold JasJar in my hand and don't move it around, I NEVER have an problem. ...and actually fairly rearly when I have it in my rugsack/backpack.
With 1 or 2 exceptions...where it lagged "all the time"...but then a soft-reset cured it.
So if you have this problem with your phone lying in front of you on the table...then it really sounds like it is the JasJar/Universal that IS the cause (and not interference)...and yes then the registry hack should help.
BUT I have not done any real testing of the effect of it...I am not sure how much effect it really has...all I know is that I had a "lot of problems" with lag before...and now I almost never have it.
...I hate those "diffuse" problems...when it is impossible to measure in a "scientific" way that "this cures it", and "this do not"! :-(
Sorry about the "little help" I give here...but this issue is a bit "fuzzy"...I have gotten it enough under control to that it isn't a problem any more (during a 1 hour workout, I will typically get this gap/lag 0-2 times...and that is not a problem for me...at least compared to what I experienced 6 months ago, where I was lucky if I could hear 10 seconds without any problems).
The stuttering problem seems to be permanent now... Luckily I have a HP hx4700 (which has a Broadcom bluetooth module) and works perfectly with my Jabra HT620s. Anyone using an A2DP ROM other than Qtek? I'd like to try a different ROM to see if it would make a difference.
only a second of sound
i use the qstarz bt stereo headset (http://www.qstarz.com/products/bh-q392s.aspx) and it works fine for phonecalls, but when i set it for wireless stereo and start a media player (TCPMP, WMP, Pocket Player...) i mostly only get sound for one second and then it shuts up. the players keep playing, the buttons on the headset can pause, resume and change tracks but there is no sound at all.
i get full wireless stereo playback occasionally, but i can't figure out what differs from time to time.
i applied the above patch with no success. anyone has a thought on the matter?
Ariel.
richardlai said:
The stuttering problem seems to be permanent now... Luckily I have a HP hx4700 (which has a Broadcom bluetooth module) and works perfectly with my Jabra HT620s. Anyone using an A2DP ROM other than Qtek? I'd like to try a different ROM to see if it would make a difference.
Click to expand...
Click to collapse
I use the BT620s with my Qtek 9000 without much trouble. Here's the trick:
Assuming you have paired with succes. Set headset and BT OFF before starting.
Turn bluetooth ON
wait a second or two
Turn headset ON
wait another two seconds
Now go to BT settings, and connect the headset.
Wait for the little pling sound (the activesync sound ).
Now start Windows Media Player and play an MP3.
Using this sequence has never failed me
edit:
I use the latest OFFICIAL Qtek 9000 WWE ROM. (Without the ExtROM though ) And i did not use any patches regarding A2DP or Bluetooth.
this is what i tried, many times. i get the activesync sound, sometimes from the speakers, sometimes in the headset, but almost always only one second of sound afterwards.
i found that by pairing the headset to the universal by pressing and holding the green button on the headset untill the universal recognises (doesn't take long) gives better results.
pairing it by the instructions of the headset (putting it in discover mode, and then searching for a device with the universal) will give me the one second sound almost every time.
Biffert said:
I use the BT620s with my Qtek 9000 without much trouble. Here's the trick:
Assuming you have paired with succes. Set headset and BT OFF before starting.
Turn bluetooth ON
wait a second or two
Turn headset ON
wait another two seconds
Now go to BT settings, and connect the headset.
Wait for the little pling sound (the activesync sound ).
Now start Windows Media Player and play an MP3.
Using this sequence has never failed me
Click to expand...
Click to collapse
Well, this has ALWAYS been the sequence I use (and I don't think you can do it in any other way). The real problem here is either the buffer memory or processor load.
richardlai said:
Biffert said:
I use the BT620s with my Qtek 9000 without much trouble. Here's the trick:
Assuming you have paired with succes. Set headset and BT OFF before starting.
Turn bluetooth ON
wait a second or two
Turn headset ON
wait another two seconds
Now go to BT settings, and connect the headset.
Wait for the little pling sound (the activesync sound ).
Now start Windows Media Player and play an MP3.
Using this sequence has never failed me
Click to expand...
Click to collapse
Well, this has ALWAYS been the sequence I use (and I don't think you can do it in any other way). The real problem here is either the buffer memory or processor load.
Click to expand...
Click to collapse
Then there is no A2DP problem, the only solution is to lower the overal systemload. Stop all programs you have running, disable every today plugin that need frequent updating (memory, battery meters etc.) Free up as much RAM as you possibly can. I have AT LEAST 16 mb RAM free when playing music via BT.
Yesterdaty I updated to WM6.5 and now try to get everything working again. Somehow my TP2 won't pair with my bluetooth carkit anymore. With WM6.1 this was no problem. The phone still pairs perfectly with my computer (also bluetooth connection) so I think the bluetooth connection is ok.
When parining to my carkit it finds the device, then I have to enter a password on the TP2, and after that it just sais "pairing connection failed", and it will not work. I am sure the password is not changed since yesterday. I tried it several times. I do not know what to do anymore. Could this be a setting somewhere? I get the feeling my password is not send properly but have no idea.
Meanwhile I tried pairing my carkit with another phone and no problems there. So my conclusion is: something has changed with bluetooth, updating to WM6.5 which makes it now impossible to pair my TP2 with my carkit.
Is there maybe a programm for the TP2 which give me more controll over bluetooth (like maybe go to an older standard)?
I have exactly the same problem as you
good to hear I am not the only one. Hope someone will come up with a solution for this.
I did nor observed any issues when pairing my TP2 after reflashing to WM6.5
There is another issue however - I can not hear any voice until it is charging.
Unplugging of the charger fixes this issue immediately. Horrible...
Seems, HTC guys are saving money on testing by using us as Beta Customers.
Would a custom ROM be a solution for us?
I updated to the "energy 6.5.1 rom" and guess what..............
The same problem. The rom is very nice, but my TP2 still won't pair with my BT carkit which is very big problem for me.
Is there maybe a way to downgrade just the BT part of a rom to WM6.1. I read on different forums there is something that is called a BT stack. Could this be the problem?
I have a ton of problems with bluetooth pairing now. However, I don't know whether it's the fault of 6.5 or the Tilt 2. Here is what I am experiencing...
- On car deck or headphones, the skip buttons don't do anything
- on car deck or headphones, I have to disconnect Stereo Audio and then reconnect to actually get sound. It NEVER works when it auto connects.
- Music will do a brief skip when you shut the screen off
- Stupid message about volume control every time it connects (resolved by switching to custom rom)
- SMS or any kind of alert tone now turns music way down so that the tone is the only thing you hear. Which is super awesome when I'm driving my drunk friends around and they are singing along to a song when suddenly it mutes so everyone can hear my incoming text message.
Not a single one of these issues existed when I had my Fuze.
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
orb3000 said:
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
Click to expand...
Click to collapse
No I do not think so, because I used the official WM6.5 with the same problem. Does someone know a way around this issue. I strongly believe that if only I could pair I have some options to work with it (in 6.1 it worked like a charm). If I only could pair without having to send the passkey it would be great step forward. I presume with sending the passkey, the bluetooth of the TP2 sends out other "rubbish" that confuses my carkit.
My problem is solved and guess what, it had nothing to do with my TP2. The problem was my carkit. It has a maximum number of bluetooth devices (5) it can pair to and the last one (the WM6.1 version of my phone) had been reached. So a hard reset on the bluetooth carkit and the problem was solved.
Well, at least I now know how to flash a rom to my phone and I think I learned more about the phone reading through all the forums. Thanks all for thinking with me on this problem!
Does anyone else still have this problem?? I have removed all the devices from my car and continue to have the same pairing error just after entering the passcode. Stock Spint ROM worked great, but multiple 6.5 upgrades don"t pair..............suggestions/ideas??????
bluetooth settings, advanced, enable beam data exchange,check the box
Interesting.....I actually found a fix. Instead of pairing the phone with the car, I paired the car with the phone. I didn't even know that this was possible, but it did the trick!
Hey everyone. Gotta say, i love this phone its the android device i always wanted. However, im having issues with my car bluetooth which i have not experienced before... namely, that random phonecalls sound completely digitized.
Ive come from an htc desire and htc sensation on the same car without issue and am worried i got a bad BT antenna-or its software...
Anyone out there experiencing the same thing? Any advice (other than buying a new car)?
I am having the same issues on a Verizon Galaxy Nexus V4.02. If I turn bluetooth off mid-call the earpiece sounds fine. The static only happens during voice calls, streaming A2DP sounds fine. There are bluetooth improvements listed in the 4.03 changelog, hopefully this will be resolved.
I had some problems with my BT speaker phone. I turned off the key press sounds and the screen off sounds and that pretty much fixed it.
I have an off topic question for you guys that use bluetooth streaming. Can start the car and press play from the HU to start music? I can with my old D2, but not my TB. I have to actually start the music player on the thunderbolt, then I can control it from my HU. I would like to upgrade, but I don't see a huge advantage in upgrading if I still can't start my music without having to actually take the phone out of my pocket. (Yes, I know it's stupid, but I'm lazy.)
I have this same issue in one of my cars. I ran a number of tests and the issue only occurs on my vehicle when the phone is connected to both for telephony and a2dp music. The static occurs whether or not a2dp is actually being used to stream music or not. This particular vehicle has two separate devices for music and telephony. If I unpair or disconnect the music device, then telephony works without the audio distortion. As soon as I reconnect the music device, the static is re-introduced.
v0yeur said:
Hey everyone. Gotta say, i love this phone its the android device i always wanted. However, im having issues with my car bluetooth which i have not experienced before... namely, that random phonecalls sound completely digitized.
Ive come from an htc desire and htc sensation on the same car without issue and am worried i got a bad BT antenna-or its software...
Anyone out there experiencing the same thing? Any advice (other than buying a new car)?
Click to expand...
Click to collapse
I am experiencing this issue as well and have not been able to resolve it. I've tried disabling the touch sounds, screen off sounds, etc. but to no avail.
It pretty much makes handsfree unusable while driving. What have you guys done in the meantime? Have you been able to resolve the issue yet?
Here's my specific details:
Phone: Verizion LTE Galaxy Nexus v4.02 stock/unrooted
Handsfree Car System (phone audio): Stock 2007 Audi A4
Separate A2DP Module (media audio): Dension Gateway Five connected to factory Stereo
All of my previous phones (Thunderbolt, Droid X, Incredible, OG Droid) have fully supported this setup with no issues whatsoever.
On a sidenote, my A2DP streaming is also unreliable. It first has trouble connecting to the device. If/when it does, audio constantly cuts out when streaming Pandora, Slacker Radio, Google Music... pretty much any streaming over network connection. I have not tried locally stored music yet as I don't have any currently stored on my device. Are you guys experiencing this A2DP issue as well?
I wonder how widespread this is and if it warrants opening an official issue with Google.
I used to have a Blackberry Torch, and I have a Ford Mustang. When I would connect the BT to it, if the Wifi was on, it would "interfere" with the signal. Turning wifi off, fixed the issue. This was a widely known issue with the Torch. Granted that shouldn't have to be a fix, but can any of you verify whether your wifi is on? (regardless of if its connected to anything or not). I'm wondering if the Nexus is using the same BT/WIFI chip that the Torch used.
radi0chik said:
I used to have a Blackberry Torch, and I have a Ford Mustang. When I would connect the BT to it, if the Wifi was on, it would "interfere" with the signal. Turning wifi off, fixed the issue. This was a widely known issue with the Torch. Granted that shouldn't have to be a fix, but can any of you verify whether your wifi is on? (regardless of if its connected to anything or not). I'm wondering if the Nexus is using the same BT/WIFI chip that the Torch used.
Click to expand...
Click to collapse
I appreciate the suggestion but unfortunately, I have the issue even if WiFi is off (I never use WiFi).
I'm going to try and toggle a few of the sound and haptic feedback settings a little more to see if it's pertinent to a certain on/off configuration. It's a shot in the dark but I'll try anything at this point.
ok it was worth a shot. Maybe on a whim turn off 3g/data so basically its airplane mode except BT is on? Just to eliminate any RF interference. Other than that I dont know
Spent quite a bit of time in the car today to try and pinpoint a cause and I have had no luck.
Phone audio will sound great and then all of the sudden turn digitized and distorted for a random period of time, then revert back to sounding great. One thing to note is that the distortion is both ways - the person I'm talking to also hears it when I speak and cannot understand what I'm saying. It's very frustrating not being able to use this feature.
I am on my 2nd replacement phone and ALL of them have had this issue (returned two others to VZW due to this issue and the speaker clicking issue). I am still wondering if it is software/OS releated or if it's due to poor hardware.
Quick Update (kind of):
I messed around with more settings last night. I am happy to report that after I disabled NFC last night, I made several handsfree calls in my car with perfect clarity and no issues. Also, A2DP streaming Pandora worked flawlessly! I was happy that I thought I pinpointed the issue - NFC interference.
BUT this morning, I made a handfree call and it was immediately distorted. Frownie face! A2DP Streaming Pandora still worked great. I am now trying to determine if my success last night was a fluke or if something is different with the phone this morning. The only difference from last night to this morning, that I have been able to identify so far, is I now have the extended battery in the phone. Last night's success had the standard battery. I'll switch them back at lunch and re-test.
Stowegy said:
Quick Update (kind of):
I messed around with more settings last night. I am happy to report that after I disabled NFC last night, I made several handsfree calls in my car with perfect clarity and no issues. Also, A2DP streaming Pandora worked flawlessly! I was happy that I thought I pinpointed the issue - NFC interference.
BUT this morning, I made a handfree call and it was immediately distorted. Frownie face! A2DP Streaming Pandora still worked great. I am now trying to determine if my success last night was a fluke or if something is different with the phone this morning. The only difference from last night to this morning, that I have been able to identify so far, is I now have the extended battery in the phone. Last night's success had the standard battery. I'll switch them back at lunch and re-test.
Click to expand...
Click to collapse
I've got the same issue. Even with NFC disabled. Makes listening to Pandora in the car unbearable. I've gone through the same steps as you, but hasn't exchanged the phone yet. I've had previous Androids and it was a hit/miss with the distortion, but with an iPhone or BB never had this issue. Go figure.
thanks to all the replies, will update to 4.0.3 and try out some more options.
- unplugging my music dongle had no effect on call quality
- NFC on or off had no effect
I also find that the music adapter never auto-connects and needs me to go in to the BT settings page and manually select it.
thanks all.
Hello again. So I have an update that adds to the flakiness ...
Updated to the Bugless Beast ROM and Franco's kernel. My intent was to completely reset the phone and hopefully get a new Bluetooth stack in the process.
Initially everything paired OK, but after a while my audio randomly disconnects after about 20minutes and then reconnects depending on its mood.
My phone connection is more controllable now: if the BT is enabled on my phone when I turn on the car, the sound quality is entirely digitized and unusable. If I turn on the car and THEN enable my phone, the sound quality is flawless every time.
Still not ideal, but manageable. For the music audio part, I lay the blame entirely on the Audi Music Interface BT adapter: the thing is crap and always in pair mode even with the car turned off! The telephone BT in the car head unit has seen several phones pair with it without any issues (I do mobile development so I get to play with many phones) so in that case, I can't blame anything but the Nexus.
I really hope someone at Google or Samsung reads these threads since it would be tough to troubleshoot, but there's no doubt an issue exists with general BT compatibility.
Sent from my Galaxy Nexus using xda premium
Anyone have an update on this issue? Does anyone know of a ROM with a different Bluetooth stack than AOKP? I love everything else about AOKP. I have had the same garbled bluetooth audio from stock - 4.03 with franco and faux kernels with the same result. I had similar problems with Cyanogen 7 ROM I was using on my Incredible the week before I bought the Nexus.
Update - I experimented with a couple of additional devices, and the multiple connections problem with my Nexus is limited to A2DP only devices.
I am now using a Garmin BlueTrip with "phone audio" deselected in bluetooth options. As long as the additional bluetooth device is handsfree profile capable, the A2DP functions perfectly, calls are clear, and the device reconnects after a power cycle consistently. I'm glad this appears to be a software issue and not something we will have to live with for the life of the phone. I'm sure a future update will correct this issue.
I'm also having a problem with Bluetooth calls sounding very digitized and/or choppy. It is bad enough that it can be extremely difficult to make out what the caller is saying. A2DP, on the other hand, has performed pretty flawlessly and the device consistently reconnects each time I get in the car (although it can take up to 30 seconds or so).
I'll have to do a little experimenting with some of the settings mentioned in this thread to see if they have any affect.
On a related note, I feel like sometimes calls made/recieved on the handset can sound digitized as well (although not nearly as bad as over bluetooth). Has anyone else experienced this?
My hardware is:
Verizon GNex (4.0.2)
Parrot MKi9000