Database Info

bluetooth and Audi A6

I have a new 8125 from Cingular (I think that's the same as a Wizard), and I tried to pair it with my 2005 Audi A6. The 8125 doesn't even see the car. Has anybode had a similar prolem, and so, is there a solution?

Hi Mike,
Just to let you know I have an Audi A4 with GSM prep and Bluetooth.
It works fine on my MDA Vario (wizard), but was crap on my old Sony Ericsson P900!.
If you look at www.audi-forums.com, a few people there have had Phone/Bluetooth problems with A6's which have been resolved by a firmware update from Audi.
Let me know how you get on.
Markee

My 8125 (TMO carrier) works perfectly with my 2006 A6 which has the technology package. Not only are calls clear and the connection fast, the car sucked all my contacts from my phone. Pretty darn neat.

Thanks for your help. I was able in the meantime to pair the phone with the car. I don't really know what changed, but after a few tries, the phone connected.
I tried to click on Markee's link, but it gave me an "unknown URL". Any alternative way to get to the forum?
@rambo6: My phone now pairs and I can use it, but I don't see the signal strength on the indicator in the car, nor do I get my contacts transferred. I noticed that my phone connects to the car in "handsfree" mode. Is there a setting that I am missing?
mike

Poor 3G Reception

Treo 750v very Poor 3G reception in buildings and on trains around London.
I have now changed job and work in central London and I have noticed on my route to and from home to central London I loose reception a number of times in various spots but on my TyTN which I took to test had no issues.
I have two Treo 750v and they both are doing it one installed with vodaphone and one Cingular rom. The lady next to me thought I was going mad two mobiles one in each hand and my eyes fixed on the reception bars all the way to London at 6:40am yesterday morning. I have not really noticed any issues with reception before this as around home it works flawlessly and I know it is not related to T-Mobile UK. I missed two calls also and whilst at work, phone on all day I got 3 voicemails. Various reviews on the internet have also said reception is poor on these phones and now it is starting to become a reality the more I use it in different areas.
I tested on the way home I rung my two land lines and spoke to my children and girlfriend on the TyTN and 750v the treo cut out 5 times whilst the TyTN held the connection from start to finish. Testing the 750v set to GSM today the phone cut out 2 so slight improvement I don't know if there will be a fix of some sort i.e. (radio or rom upgrade like the TyTN) over time fingers crossed, There is no difference for reception on the Cingular rom vs. vodaphone. But like anything it could be a hardware problem. I am sure if the treo had an antenna it would be better. First attempt for an antenna less Treo it is a good start. I hope they do a new revision of this Treo or this fault does gets fixed as I love the form factor of this phone far better than the TyTN imo.
Reception set to GSM is far better under band selection, I loose the fast browsing speed abilities of UTMS but call quality is much better overall.
Does anyone else suffer from reception issues related to 3G?
Tmobile
Vodaphone
O2
Sim cards tested in both phones.

I am also experiencing problems on 3G here in the Netherlands. I have some bad reception during calls and also alot of dropped calls when on the move and the phone is trying to fall back from UMTS to GSM.
I am also having some Bluetooth stack problems: the Bluetooth sometimes crashes, even in the middle of a conversation on the carkit. The audio connection gets lost with the parrot carkit.

mkoster007 said:
I am also experiencing problems on 3G here in the Netherlands. I have some bad reception during calls and also alot of dropped calls when on the move and the phone is trying to fall back from UMTS to GSM.
I am also having some Bluetooth stack problems: the Bluetooth sometimes crashes, even in the middle of a conversation on the carkit. The audio connection gets lost with the parrot carkit.
Click to expand...
Click to collapse
The issues you are having are just like mine, Not having any bluetooth issues like you mention though. UTMS to GSM is a big problem with the phone it is like it gets confused and then freaks out.
The reception part is really starting to get to me as my main phone it is not doing to well if you know what I mean. I only hope that a software upgrade can fix the issues. I am sure the bluetooth issues will get sorted with an update.

Same here (Italy). Bad 3G reception (Vodafone network): sometimes the 750V switches to GPRS and the call quality is fine, sometimes it doesn't, and it's a pain... I noticed a slight improvement when I upgraded from the original Vodafone ROM to newer Cingular's. Hope this means it's a software-related issue, and can be solved via a ROM upgraded in the future. After all, the 750V is made - like the TyTN - by HTC, so the reception should be more or less the same in both the devices.
Bye,
F.

xxnoelziexx said:
Treo 750v very Poor 3G reception in buildings and on trains around London.
I have now changed job and work in central London and I have noticed on my route to and from home to central London I loose reception a number of times in various spots but on my TyTN which I took to test had no issues.
Click to expand...
Click to collapse
With my TyTN (radio 1.16) I get reception on a dead spot where I couldn't get reception with several other phone's (Nokia, SE, Motorola). Much better then with the standard radio 1.03 which didn't work there also. The Palm's reception is somewhere in between, and probably software-related too.

xxnoelziexx said:
The issues you are having are just like mine, Not having any bluetooth issues like you mention though. UTMS to GSM is a big problem with the phone it is like it gets confused and then freaks out.
The reception part is really starting to get to me as my main phone it is not doing to well if you know what I mean. I only hope that a software upgrade can fix the issues. I am sure the bluetooth issues will get sorted with an update.
Click to expand...
Click to collapse
I've got the same problem. Fixed it by changing the band selection from "automatic" to "gsm". I'll have to change it back whenever I want to access the internet, which is a pain, but at least it's now usable as a phone.

HTC Touch Dual (NIKI+NEON) & Fuze problems w/ ATT EP-5632 Bluetooth cordless phone

HTC Touch Dual (NIKI+NEON) & Fuze problems w/ ATT EP-5632 Bluetooth cordless phone
Hey all,
After searching in google & the XDA built in search for days I'm throwing in the towel & asking for help here. For some reason both my Touch Dual's (NIKI100 & NEON300) have a weird bluetooth 'drop' problem with my AT&T cordless phone which acts like a headset.
I've had an AT&T EP-5632 cordless phone system that links to a cell phone via Bluetooth for about a year & 1/2 now & it has served me well in my home office allowing me to keep my cell plugged in and gives me the ability to use any of my 4 cordless phones to talk on the cell and/or my vonage line. It has had its issues (such as sometimes the Bluetooth link breaks & I have to either turn off & back on Bluetooth on my cell, reboot my cell or power cycle the base) but that happened pretty rarely & wasn't a huge deal. My original phone I used with it was the AT&T 2125 (HTC Tornado) with WM5 & with it I rarely had any problems. After about a year I upgraded to an HTC S710 VOX that came with WM6 and although it fought me hard to do the original link and had the above 'vanishing cell' problem more often than the 2125 overall it was stable enough for me to use it daily making & receiving numerous calls. A few weeks ago I got a Touch Dual (NIKI100) with WM6 thinking I'd prefer a touch screen over full QWERTY to find it lacked the 850 GSM band & 850/1900 3G band AT&T uses but alas it was a new toy so I played with it anyway since we have some 1900 towers around. It too fought to link mostly because the keyboard was defaulting to characters not #'s so I was entering spaces not 0's for the password. lol Once linked I was happily using it with my EP-5632 cordless system via Bluetooth for a few days. One day I was on a cell call & another cell call came in. I was in the middle of a conversation so I let it go to voicemail. BIG mistake! As soon as the ringing stopped I was not able to hear the person I was talking to nor were they able to hear me even though my cordless still showed me as if I was connected (call timer running & not on home screen) & the cell screen showed me connected with call timer running so I quickly picked up the cell phone & they were there! We could talk fine so I hit the OFF button on my cordless to find it hung up my cell call! (So the ATT cordless was still connected via Bluetooth & controlling the cell but the voice portion was no longer being routed to my cordless but rather only on the cell) I quickly dialed the person back with the cordless to find we could not hear each other! I hung up & dialed directly with the cell to find the same thing.. After we tried calling each other a few times unable to hear each other he sent me a text message saying "What happened I can't hear you, can you hear me?" I ended up having to power cycle my Touch Dual to be able to talk to anyone (even directly on the cell not over Bluetooth) & once I did I could use the cordless or my cell AS LONG AS no one called me & I let it go to voicemail. (Tell me that's not odd!) I had already ordered a Touch Dual US NEON300 which arrived that same day so I moved my SIM over & linked it to my ATT to find it does the exact same thing! My 1st thought is that it is either a Touch Dual problem or possibly a WM6.1 problem since my S710 worked & had 6.0 which wasn't as good as my WM5 2125 but worked well enough to use. But both Dual's are worthless with this phone system unfortunately!
I broke down & bought a Fuze thinking that was an AT&T phone (I know, still made by HTC) but I assumed it would be more likely to work figuring AT&T would surely test it with their own AT&T branded cordless phone system, right? WRONG! I found a very strange thing. Even though the Fuze has WM6.1 on it, it does not do the same thing the Dual's do! If a call comes in it doesn't 'disconnect' the audio. WOO! The problem is that if I end a call then try to make or receive a call too quickly after it does the same thing as the Duals where the AT&T cordless initiates or connects the call via the Fuze but I can't talk to them on the AT&T! I have to pick up the Fuze & talk on it.. But unlike the Dual's I don't have to reboot anything to get it working again. I just have to wait like 20 seconds after a call completes before making another call. Inconvenient I know but not nearly as nasty as the problem I was having with the Dual's.
I searched & searched & found various people with odd Bluetooth issues linking with cars that sounded similar and many said the problems started when they upgraded to WM6.1 (either upgraded their ROM or bought a new phone with WM6.1) but some said WM6.0 had issues too although WM6 worked for me. Many people blamed Microsoft's Bluetooth stack, others blamed HTC because it seemed it was only HTC made phones that did it.
So my question is can these problems be fixed?
Perhaps with a patch from Microsoft or HTC?
Maybe by installing a different Bluetooth stack?
Maybe there are Bluetooth registry settings that are different (remember 2125 with WM5 works fine, S710 with SM6 works OK, Touch Dual NIKI100 with WM6 does same freaky thing as Touch Dual NEON300 with WM6.1 where the Fuze with WM6.1 mostly works, at least better than either Dual which makes me think it is NOT the WM version)
Could it be the radio version?
Maybe there is a cooked ROM I might try on either Dual or the Fuze that might fix it?
Maybe the issue has to do with the 2125 & S710 both being smartphones vs the Dual's & Fuze being WM Professional touch screen devices?
Perhaps it is some hardware incompatibility like Bluetooth chipset on the phones?
Sorry so long but I wanted to be thorough in case any of the minor details could help figure out the issue. I realize the problem could very well be a crappy Bluetooth implementation in the EP-5632 but from what I found I am not the only one with odd Bluetooth issues especially with HTC's running WM6.1 so even if someone else doesn't have these particular phones or the same ATT cordless system perhaps something useful to many others will come of this.
Thanks in advance for any input or possible solutions.
Bill

Quick follow up:
I did hard spl on my NIKI100 & flashed with "RUU Nike Radio 1.58.21.23S Modded" & "Tom_Niki_Project_v2.1.3_WWE" ROM & it FIXED the Bluetooth problem with my AT&T EP-5632! That is good news & bad news. The good news is obvious, it is fixed! The bad news is however that I'm selling that phone because it doesn't support the 850 GSM band or AT&T 3G (850/1900 bands). Btw for anyone searching on upgrading their NIKI to add the missing 850 band, of all the radios & ROM's I tried no combination was able to add the 850 GSM band so I assume the hardware is not there as has been noted in various places but not absolute so I had to try. I never expected it to add ATT 3G but like my Touch Diamond (yup I bought one of those last week to see how it worked with my ATT cordless phone & it acts just like my Fuze & I tried a few ROM's) I had hoped it would at least add the GSM band to give me better coverage around here but it was a bust. Guess bad news to anyone else searching on the subject.
So my dilema now is how do I do fix my NEON300? I suspect it was the ROM not the radio that was the fix but I can't say for certain unless I try others & I already put it all back to stock to ship out to the buyer tomorrow. (I had tried "RUU Nike Radio 1.71.09.01K" too but the phone went wacko & I couldn't make calls for long enough to test & didn't try others with this particular rom)
I noticed on the Niki Project thread there are a few mentions of Bluetooth changes:
* Bluetooth FTP 1.2.33281.9 Diamond [NEW]
* Bluetooth 1.6.5.0 Diamond [NEW]
* Bluetooth patch included
* Best Bluetooth A2DP settings
* Bluetooth DUN support
I suspect one of those is the magic fix that I am hoping I can apply whatever that was to my NEON300.. I'm hoping someone involved with the Niki Project can shed some light on what those updates are or do but perhaps I need to ask in that thread instead.
I'm also interested to hear back from anyone else who is having Bluetooth issues with the Dual (such as integration with cars I read so much about) to see if this radio/rom combo solves their problems or not.
Thanks in advance,
Bill

[Q] Static reception on Samsung Captivate

I have a Samsung Captivate from ATT with Froyo (Android 2.2). I am using a T-Mobile prepay Sim Card with the phone (no 3G/data plan). I have rooted and unlocked the phone, and initially (for several days) the phone worked perfectly without problems.
I took a trip from the US to Vancouver, and while in Vancouver, I texted back and forth a few times to the US and made one phone call (Rogers Network) without problems, using data roaming. When I returned to the US, my problem began. I can still text without problems, but when I make a phone call, my reception consists of mostly or all static through the earpiece, speakerphone or earphones. The person on the other end can hear me perfectly, but I receive static. I also receive static when I dial up voice mail. My earpiece and earphones work OK with music and voice recordings.
There have been a couple of occasions where the static went away and I do not know the reasons for this (the static later returned). Other than the static, I have no other apparent problems with the phone.
I have tried a factory reset and that did not correct the problem. I also installed the simcard from my husband's iphone, and the problem was the same (static on reception). I was wondering what else I could try to correct the problem. Should I reinstall Froyo? How would I do that with a rooted and unlocked phone?

T-Mobile 1+ 7 Pro call quality issues

Am I the only one out there experiencing severe call quality issues? My phone (T-Mobile OnePlus 7 Pro) is suffering from severe call quality issues.
I seem to be having the issue with the following configurations in an attempt to narrow down / in on the issue:
Galaxy Buds (BT Headset) = Calls on Wifi Calling, Regular LTE and WhatsApp calls. Broken audio (stuttering)
Direct Phone microphone (on handset) = Calls on Wifi Calling, Regular LTE and WhatsApp calls. Broken audio (stuttering) / Drop-outs
Purchased USB-C to 3.5 mm adapter to wired headset = Severe Echo on Wifi Calling, Regular LTE and WhatsApp.
I've tried driving into range of another tower and experience these same problems. I picked up my daughter's iphone X and on the same towers and wifi network, these problems don't exist. The call quality is pristine.
On my Note 8/9 (can't remember what the current one is, but I own it), the problems don't exist in these same configurations. The problem is clearly local to the OnePlus 7 Pro. I've done the "clear cache, reset networking, reset wifi" solutions and they don't seem to help. At this point, I'm wondering if it's a bad phone or just bad software.
I'm at my wit's end and pretty much feeling buyer's regret right now, because I so wanted to love this phone, but it's caused me more heartache than ever. Obviously, the phone is up to date on the most recent version of T-Mobile firmware, but I can't possibly imagine a phone could be so bad at doing what a phone does and pass the certification lab for the carrier and get the amazing reviews that exist on the web.
I'm a few minutes away from just going back out to the store and buying a new Galaxy S(whatever is the most recent)+
**frustrated** and **confused**
Lol..

Incredible cell reception and call quality here, on international stock, the weird part for me is it sounds worse on VoLTE and Wifi calling. Regular voice calls are outstanding.
But if you have both of those disabled and the call quality is that bad, I would exchange/return it.
Sent from my GM1915 using Tapatalk

percykwong said:
Am I the only one out there experiencing severe call quality issues? My phone (T-Mobile OnePlus 7 Pro) is suffering from severe call quality issues.
I seem to be having the issue with the following configurations in an attempt to narrow down / in on the issue:
Galaxy Buds (BT Headset) = Calls on Wifi Calling, Regular LTE and WhatsApp calls. Broken audio (stuttering)
Direct Phone microphone (on handset) = Calls on Wifi Calling, Regular LTE and WhatsApp calls. Broken audio (stuttering) / Drop-outs
Purchased USB-C to 3.5 mm adapter to wired headset = Severe Echo on Wifi Calling, Regular LTE and WhatsApp.
I've tried driving into range of another tower and experience these same problems. I picked up my daughter's iphone X and on the same towers and wifi network, these problems don't exist. The call quality is pristine.
On my Note 8/9 (can't remember what the current one is, but I own it), the problems don't exist in these same configurations. The problem is clearly local to the OnePlus 7 Pro. I've done the "clear cache, reset networking, reset wifi" solutions and they don't seem to help. At this point, I'm wondering if it's a bad phone or just bad software.
I'm at my wit's end and pretty much feeling buyer's regret right now, because I so wanted to love this phone, but it's caused me more heartache than ever. Obviously, the phone is up to date on the most recent version of T-Mobile firmware, but I can't possibly imagine a phone could be so bad at doing what a phone does and pass the certification lab for the carrier and get the amazing reviews that exist on the web.
I'm a few minutes away from just going back out to the store and buying a new Galaxy S(whatever is the most recent)+
**frustrated** and **confused**
Lol..
Click to expand...
Click to collapse
Call quality is excellent for me as is reception. TMO on TMO Rom. My only issue is DUO freezes the person on the other end for me. Its only been to the same person so far but that is my only issue

You have done soft reset, but try to do a hard reset(erase everything instead of clearing cache). That helped with some crackling noise but.

Call quality not even in the same ball park as my tmobile note 9.

I also had issues with my OP 7 pro. Specifically on speakerphone wife could not hear me at all. I was on the international variant + T-Mobile. I ended up sending it back. Bought the OP 7 and have the exact same issues. I sold me OP 6T tp upgrade to the 7 series. I ended up finding a used OP6T in offerup. Popped the SIM card in. No call quality issues and people can hear me just fine when in speaker phone and driving. I usually have my phone placed in the center console in my car. So for me this is the primary way to talk. It sad that the OP 7 series has these issues. I was really hoping they would fix this in a software update. Still handing on to the OP 7 praying for a fix. But I may just end up selling it on swappa.

Have you guys tried to get a replacement? I don't have any problem with call quality. I use Bluetooth headset or reg phone on ear way most of the time, and rarely on speaker.

I had that problem on the T-Mobile variant and when I converted it to the international firmware it doesn't have that problem now

My call quality is really good sometimes. Some times, it'll have weird moments where I get muted or the other person does. Speaker phone mic sucks real bad though. I hate using speaker phone if I need both hands to do something, so I ordered a bluetooth headset.

Apocalypse487 said:
My call quality is really good sometimes. Some times, it'll have weird moments where I get muted or the other person does. Speaker phone mic sucks real bad though. I hate using speaker phone if I need both hands to do something, so I ordered a bluetooth headset.
Click to expand...
Click to collapse
I primarily use the speakerphone for calls so this is kind of a show stopper for me. Desperately looking for a fix. Might have to sell mine on swappa.
---------- Post added at 02:35 PM ---------- Previous post was at 02:32 PM ----------
atn0716 said:
Have you guys tried to get a replacement? I don't have any problem with call quality. I use Bluetooth headset or reg phone on ear way most of the time, and rarely on speaker.
Click to expand...
Click to collapse
That's probably why you aren't experiencing the issues we are seeing. Its mainly on the speakerphone. I am currently using a op 6t until I can find a fix. I don't have any issues on the 6t.