Several people have complained to me that, when I use the Bluetooth hands-free system for telephone calls, my voice is distorted and difficult to understand. I mentioned this to my Subaru dealer this morning when I took the car, a 2013 Impreza, in for servicing. The service representative went onto a Subaru of America website and told me that, while the SGS3 from Verizon and Sprint is listed as compatible, the AT&T and T-Mobile versions are not.
Is there something about these versions that might explain this issue?
Does anyone know anything else that might shed some light on it?
TIA
RebDovid said:
Several people have complained to me that, when I use the Bluetooth hands-free system for telephone calls, my voice is distorted and difficult to understand. I mentioned this to my Subaru dealer this morning when I took the car, a 2013 Impreza, in for servicing. The service representative went onto a Subaru of America website and told me that, while the SGS3 from Verizon and Sprint is listed as compatible, the AT&T and T-Mobile versions are not.
Is there something about these versions that might explain this issue?
Does anyone know anything else that might shed some light on it?
TIA
Click to expand...
Click to collapse
I have a 2013 Ram with UConnect. I have very different results with different ROMs. With stock I have moments where things work and some times things like messages and incoming calls don't work at all. I use AOSP 4.3 now and everything works like a dream. If you are willing to venture into other ROMs, I suggest you give others a try, both custom stock and CM10.2 etc.
Since you already have a thread about this in the TMo section with some pretty good answers, let's close this one.
Related
Hello all!
I've had this issue since I rooted my phone (with NAND unlock using Toast's method) back in the beginning of June. I noticed this issue IMMEDIATELY after rooting since my girlfriend is on AT&T. Recipients on AT&T can receive my SMS just fine, but I cannot receive theirs (I have tested multiple phones on their network)! Other carriers seem to work just fine as I have tested most of the popular ones although haven't tried T-mobile, could it be a "my phone versus GSM" issue?
I have wiped and factory reset my phone numerous times, used multiple roms including the rooted stock 1.32-1.47, OMJ's 1.4-1.7, and currently am on Baked Snack 9.6. Out of an act of desperation, I accepted the 1.47 OTA update before root with no avail. After all of this I have noticed one thing staying the same... The PRI Version 1.34. I know there is no current way to update this back to the stock 1.40, and too be honest am not really sure if this could even be the underlying cause of this issue because what does roaming have to do with receiving SMS on my home network? I've had multiple people tell me that they have had no such issues, and searching the boards shows me that this is definitely an isolated issue.
If anyone has any advice, information, or even has this issue as well please let me know! Any help will be greatly appreciated!
Call Sprint, sounds like a network issue, not a phone one.
--Swyped from my EVO using XDA App.
After over a week of dealing with Sprint...
drmacinyasha said:
Call Sprint, sounds like a network issue, not a phone one.
--Swyped from my EVO using XDA App.
Click to expand...
Click to collapse
Well, after several phone calls and tickets later, I have now found out that the AT&T messages aren't even hitting Sprint's gateway (the front door of data). It's odd because the tech rep is able to see my messages out, but not able to see the ones sent back. This leads me to believe that it is in fact a network issue, and has absolutely nothing to do with my phone. He clarified that even if my phone was broken he would still be able to see the messages at the gateway, but they aren't even getting there. There is nothing more that Sprint can do because they can't reference something that doesn't show in their systems; so I'm being forced to call AT&T... I have already gotten the run around from both sides stating, "well it's definitely an issue on their network".
I'm not really sure what else to do, it just seems so strange that the very same day I rooted my phone, I stopped being able to receive their messages. The only thing left for me to do is try and get a replacement phone? and if I do that, do I root my phone again and risk being burdened by this issue again? I know one thing's for sure, after having a rooted phone for almost a month and a half, there's no way I'm staying stock!
Getting a new phone won't help you, it's definitely AT&T's network, or whoever owns the bandwidth connecting their (AT&T's and Sprint's) networks. Simple as that.
drmacinyasha said:
Getting a new phone won't help you, it's definitely AT&T's network, or whoever owns the bandwidth connecting their (AT&T's and Sprint's) networks. Simple as that.
Click to expand...
Click to collapse
Thank you drmacinyasha on your quick replies!
I'm hoping to get my girlfriend's account information soon so AT&T will actually help me; I'm just worried that they will say the same thing Sprint has told me. I know it's as "simple as that" to state where the problem obviously lies, but I'm not sure how simple it will be to get a hold of someone who will actually be able to fix it.
My girlfriend is able to send SMS to other people on Sprint just fine, so I'm confused by the fact that this has only happened to my number.
Ok this was a blast from the past for me last night, I remember this happening on my Mogul. My evo was lying on the counter charging, the phone rang and while it was still ringing I could clearly hear the person calling talking to someone else with them before I even picked up the phone to answer it.
Does it still count against your minutes if you don't answer the phone?
I was thinking about if this was possible a couple weeks ago, I don't see why it wouldn't be, just have to activate their mic when they call.
This happened all the time on my touch pro 2 with energy rom glad no one was talking crap before I picked up.
MzChiChi»» Coming from my Evo 4g with Tapatalk Pro
That's actually kind of cool - I wonder if someone can build an app that would do this intentionally.
It's not actually that cool. This happens to me. It's quite annoying when the phone is on silent or vibrate and I'm in a meeting at work and get a call and all of a sudden you can hear people talking. Not good.
I've narrowed this down in my case to it being an issue with receiving calls from the AT&T mobile network. All the calls I've received that do this are from AT&T users or Net 10 users (which are using the AT&T network). No issues with calls from other Sprint users, Verizon, etc. As of now, Sprint hasn't been able to offer a fix.
Anyone else had this problem? Any resolution?
Oh, and I have an Evo. Bought it on launch day from Radio Shack.
I have this problem too, I guess I have to send the phone to RMA. Tried with different ROMS (official), still the same.
Well, I have flashed the 3.14 ROM official WWE and seems the problem is gone now. Check it please and reply .
Hi, I'm looking for some help here with an issue my wife and I both have with our phones. My wife and I are the Proud owners of the Samsung Galaxy S2 phones UNROOTED. I have the Data plan and she does not. In the past 2 months or maybe since the begining of Sept. we both are haiving the same thing happen. When making or receiving calls (both in Wifi and T-mobile networks) we can't hear the person on the other end. We have to hang up and call them back (with success) on the cell or house phone. They let us know, they can hear us fine but we can't hear them.
This happens on all Landlines and Cell lines that we call or get call to our cell. I have contacted T-Mobile and they can't find anything on their end. I have done a Factory Reset on Mine and it still happens.
2 weeks ago, some weird things were happening to both our phones on the same day. with this being one of them. I plugged my phone into Samsung Kies and there was a Device Firmware update. So I updated to the ANDROID VERSION: 4.0.4 BASEBAND: T989UVLH1, and after update, I Reset phone to Factory Reset Settings and that seemed to help with alot of the freezing we had. But the phone call issues still happen.
I also have noticed, that now we periodically loose the Network connection. I can be sitting on the couch with a 100% Wifi coverage and not move an inch. I would dop my connection and the call and still have wifi coverage.I will also contact Samsung to see if it has something to do with any patches or updates. But for now, I am lost for ideas.
I was wondering if anyone else is having a similar issue or the same issue..or id anyone has a fix for this?
If it's happening to your landlines too, it's definitely an issue with T-Mobile and not your phones. You either got a noob customer service rep or a tech that didn't know what he/she was talking about. I would call again and speak with a technician, they should, at the very least, reset your service!
Bluntified said:
If it's happening to your landlines too, it's definitely an issue with T-Mobile and not your phones. You either got a noob customer service rep or a tech that didn't know what he/she was talking about. I would call again and speak with a technician, they should, at the very least, reset your service!
Click to expand...
Click to collapse
Thanks for your reply!
I have, since that post, gotten a new SIM card and although I only made and received a few calls, all of them were a success so far.But it is still too early to tell as this issue happens randomly. It also has been pointed out that there are others that have this similar issue and they are blaming it on the software. Which can be found here: http://androidforums.com/samsung-ga...hen-dialing-out-sometimes-not-connecting.html
I am hoping that is was my SIM card. But if it's not, and it does have to do with something with the OS Firmware version, I might consider Reverting backwards to the original ROM of SGH-T989_TMB_T989UVLDE 2.3.6. But for now, I will continue to test this SIM card out...
I'll keep you posted!
Hi all,
I have been having the issue when people try to call me they can not hear me on their side. I can hear them fine. I would have to call back in order to talk. I've did a couple of factory resets and that didn't help. Finially I went to a Sprint store and after about two hours the phone came back that there was nothing wrong. I couldn't get a new phone with the insurance since the tests passed. Frustrated, I called Sprint and they said I could get a new one but it will cost up to $400. They suggested to go to another Sprint store and they might find out what's wrong.
I googled the issue and found many people accross multiple phones having this same issue. Some suggested to update the PRL. I tried that and it didn't work. My wife has the Note 2 also and she was on the same PRL as I was. 2000.
For the heck of it I signed on to google voice and removed my phone. Once I did, my phone came on and it updated the PRL. (Still 2000).
I had multiple people call me and everyone could hear me.
It's been two days now and all is still good.
So if anyone out there is having this issue please try the removing your device from google voice and please respond to let me know it works for you also.
Now if anyone could help me with my weak WIFI reception I would be grateful.
Randy
Several people have complained to me that, when I use the Bluetooth hands-free system for telephone calls, my voice is distorted and difficult to understand. I mentioned this to my Subaru dealer this morning when I took the car, a 2013 Impreza, in for servicing. The service representative went onto a Subaru of America website and told me that, while the SGS3 from Verizon and Sprint is listed as compatible, the T-Mobile version is not.
Is there something about the T-Mobile version that might explain this issue?
Does anyone know anything else that might shed some light on it?
TIA
RebDovid said:
Is there something about the T-Mobile version that might explain this issue?
Click to expand...
Click to collapse
No. Sounds like a load of crap to me.
You still using Dandroid? Have you tried stock or S3Rx?
Aerowinder said:
No. Sounds like a load of crap to me.
You still using Dandroid? Have you tried stock or S3Rx?
Click to expand...
Click to collapse
Still using Dandroid. Do you think it's worth trying a different ROM or kernel?
I am dead certain he lied to you might want to use stock kernel just to be sure and if it still doesn't work you could always ask on NASIOC forum which is a must have for every subaru owner like me
Sent from my SGH-T999 using xda premium
RebDovid said:
Still using Dandroid. Do you think it's worth trying a different ROM or kernel?
Click to expand...
Click to collapse
I think you should make a nandroid and try stock.
RebDovid said:
Several people have complained to me that, when I use the Bluetooth hands-free system for telephone calls, my voice is distorted and difficult to understand. I mentioned this to my Subaru dealer this morning when I took the car, a 2013 Impreza, in for servicing. The service representative went onto a Subaru of America website and told me that, while the SGS3 from Verizon and Sprint is listed as compatible, the T-Mobile version is not.
Is there something about the T-Mobile version that might explain this issue?
Does anyone know anything else that might shed some light on it?
TIA
Click to expand...
Click to collapse
Boatload of crap if you ask me. Its the same Soc 8960. The only difference is the LTE Antenna if that. But then the bluetooth antenna and LTE Radio are separate to begin with. I wouldn't blame the dealer per se. When it comes to technology, these guys are uber airheads. They are likely to parrot what Subaru has to say. So the blame if any goes to Subaru for not doing homework and publishing half baked theories.
FWIW, with a '13 Equinox, last year, Chevy dealer pulled that one too. I called GM and they actually had a speciality division that supports technology integration. They worked with me on the Bluetooth as well as other issues I had. Long story short, the automakers use cheap 1.0 Protocol compliant adaptors to save money. The S3 on the other hand uses v2.1 for simultanious transmission of phone voice comm and any music playback. The cheap adaptor in the car can do only one at a time. So in your paring, turn off the media playback option and keep the phone part alone. That will most likely fix your issue.
Perseus71 said:
Boatload of crap if you ask me. Its the same Soc 8960. The only difference is the LTE Antenna if that. But then the bluetooth antenna and LTE Radio are separate to begin with. I wouldn't blame the dealer per se. When it comes to technology, these guys are uber airheads. They are likely to parrot what Subaru has to say. So the blame if any goes to Subaru for not doing homework and publishing half baked theories.
FWIW, with a '13 Equinox, last year, Chevy dealer pulled that one too. I called GM and they actually had a speciality division that supports technology integration. They worked with me on the Bluetooth as well as other issues I had. Long story short, the automakers use cheap 1.0 Protocol compliant adaptors to save money. The S3 on the other hand uses v2.1 for simultanious transmission of phone voice comm and any music playback. The cheap adaptor in the car can do only one at a time. So in your paring, turn off the media playback option and keep the phone part alone. That will most likely fix your issue.
Click to expand...
Click to collapse
Over the weekend, I'll try your suggestion of turning off the media playback. But if that works, it would seem simply to confirm the defective nature of Subaru Bluetooth setup. I call it defective because we got the Impreza after our SGS3 phones and the ability to use the entire Bluetooth system with our phones was a key selling point.
I should add that your explanation doesn't explain why the Verizon and Sprint versions supposedly are listed as being compatible. Also, FWIW, the service rep told me that he has an S3 on Verizon, that he made a couple of calls using my Impreza's bluetooth system, and the only comment from the people he called was that it sounded like he was calling from within a box (which he attributed to calling from inside the shop).
RebDovid said:
Over the weekend, I'll try your suggestion of turning off the media playback. But if that works, it would seem simply to confirm the defective nature of Subaru Bluetooth setup. I call it defective because we got the Impreza after our SGS3 phones and the ability to use the entire Bluetooth system with our phones was a key selling point.
I should add that your explanation doesn't explain why the Verizon and Sprint versions supposedly are listed as being compatible. Also, FWIW, the service rep told me that he has an S3 on Verizon, that he made a couple of calls using my Impreza's bluetooth system, and the only comment from the people he called was that it sounded like he was calling from within a box (which he attributed to calling from inside the shop).
Click to expand...
Click to collapse
Well if its a selling point then I'd be upset as well. That sales guy should have tested your GS3 at that time so that's on him.
Anyway VZW & SPR had got GS3 way before T-Mo did. That and the fact that T-mo is the No. 4 carrier probably made subaru discount testing on D2TMO.Come to think of it, the accessories of GS3 are marketed for VZW eventhough they fit fine for T-Mo. But I degress.
RebDovid said:
Over the weekend, I'll try your suggestion of turning off the media playback. But if that works, it would seem simply to confirm the defective nature of Subaru Bluetooth setup. I call it defective because we got the Impreza after our SGS3 phones and the ability to use the entire Bluetooth system with our phones was a key selling point.
I should add that your explanation doesn't explain why the Verizon and Sprint versions supposedly are listed as being compatible. Also, FWIW, the service rep told me that he has an S3 on Verizon, that he made a couple of calls using my Impreza's bluetooth system, and the only comment from the people he called was that it sounded like he was calling from within a box (which he attributed to calling from inside the shop).
Click to expand...
Click to collapse
There simply is no explanation for why one works and one doesn't. Because it's factually incorrect. Did you try stock?