I've been having an odd issue with my GSM Gnex lately (probably past month or two). During a phone call, after a short amount of time (usually within 5 minutes), the outgoing and incoming audio will quickly fade away with some garbling. I can call back and have the audio return, only to die again. I don't make/take many phone calls, so I don't have a lot of data on it. I can't say if it happens on every phone call, but it has happened enough times that I know it's a problem.
This has persisted through various clean installs. I'm not sure, but I think it started with a ROM whose name I can't remember, then in CM 10.1 for a few weeks, and it just happened again tonight, after a clean install of the stock 4.3 JWR66Y image directly from Google last night. Although I did flash the newest UGLL1 radio, as well as SuperSU for rooting.
I'm thinking it's hardware, but I don't know enough to make a decision on it; I've had this phone since last summer.
Sorry for the vagueness and lack of detail. Does anyone have any ideas? Experiences? Things I could test?
Thanks in advance.
Bump.
EfemaN said:
Bump.
Click to expand...
Click to collapse
Bumping again. Forgot about this thread a while back.
Hey folks, just wanted to see if anyone else is experiencing this problem and if a fix has been found or if it's an HTC problem with the phone design. This is happening to me frequently and it doesn't matter which ROM I am running, it happens on all of them. Whenever I'm on a call, the person on the other line will complain they cannot hear me (I'll hear them just fine). This will last for anywhere from 2-3 seconds to 15-20 seconds and may happen several times on a call.
Is anyone else having this issue? I've checked the web and there seems to be several discussions and compalints on several HTC forums about this problem but no fix so far, I checked a few pages on this thread and didn't see anything mentioned here so I was wondering if anyone else is affected.
Like i said, I have tried 4-5 different ROMs to see if any gave different results but no luck. So I'm leaning towards it being a hardware or design issue. I really like this phone but if this can't be resolved I guess it's back to Sammy for an S5.
Any input would be great, thanks.
Holy crap is everyone here able to transmit clearly on every call???
Greetings all,
I tried to find this issue before posting a new thread (I did find an old thread with no solutions to the issue but I didnt want to try to revive a dead thread from a year ago) so I apologize in advance if this is a duplicate and if so please link me to the existing thread.
I have an on going issue that ATT has been useless with so I am reaching out to the XDA community now in hopes that I do not need to start using my phone as a door stop.
I have done a ton of research on this issue and it seem that it is software related but the few fixes that I have tried have not helped at all.
The issue is when I am talking on the phone the "mic" will cut out and sometimes so will the speaker. I can be talking just fine with no issues and then the person I am speaking with says its like I hung up. Some times I can hear the person fine but they can not hear me and other times it truly seems as if the phone was hung up. Some times the issue lasts 5 seconds other times its upwards of a minute. I am on my second phone, att was nice enough to replace it once but the issue persists on the new one as well. The issue occurs on the handset as well as bluetooth. Every so often I luck out and have no issues with a call (normally under 3 minutes) but typically when I use my phone as an actual phone the calls are longer than 10. The issue also occurs when speaker is turned on as well with the phone sitting next to me on a table so I do not think it has to do with any form of auto mute (like the old thread I found mentioned).
One of the things that I had found was to make a call with skype and it magically fixes it. Well sadly to say it I have tried that multiple times and it still did not fix it. I have tried running my phone just stock and the issue still occurs so i do not think its an issue with what is installed (mostly just google apps for work and a few games).
If any one has any ideas please let me know. At this point I am willing to try almost anything. Thanks
Turn off Enhanced LTE (HD Voice).I just had an AT&T rep confirm that this is their networknetwork problem. Apparently, HD Voice (VOLTE) isn't quite right, and the bugs are numerous. Turn it off, should fix these issues and maybe more.
keithfrombm said:
Turn off Enhanced LTE (HD Voice).I just had an AT&T rep confirm that this is their networknetwork problem. Apparently, HD Voice (VOLTE) isn't quite right, and the bugs are numerous. Turn it off, should fix these issues and maybe more.
Click to expand...
Click to collapse
I just reset my note 4 to stock last night. I just checked and Enhanced LTE is off and I am still having the same issues that others are reporting and just terrible signal strength in general. If I am indoors anywhere I am lucky to have 2 bars and then half the time calls don't go through. I am headed to the ATT store now to see what they say. I am on next and could upgrade but looking at the list of available phones from ATT I don't know if anything is really going to be better. I don't want to shell out the cash for a nexus 6p but I may end up doing it.
Turning off enhanced seemed to help but I still encounter the issue from time to tine. I'm just counting down the days till my 6p shows up...
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
I took delivery of a Tesla Model 3 on March 30 of this year. At the time, it was running Tesla's software 2019.5.15, but within a day it had upgraded to 2019.8.4, then 2019.8.5, then 2019.12.1 a couple of days ago, and finally to 2019.12.1.1 today. Through all of this, I've had no problems with Bluetooth connections to my OnePlus 5t phone for media streaming; however, I have had problems with placing and receiving phone calls, and the problem has gotten worse with Tesla's 2019.12.1 or 2019.12.1.1 (I'm not sure which).
I never tried making phone calls in the day or so I had Tesla's 2019.5.15, but I did with 2019.8.x, with about a 50% success rate. Sometimes it would work fine, but other times I'd get very stuttery sound, as if the connection was cutting in and out about ten times per second. Initially, I was running LineageOS 15.1; however, in part because I hoped to resolve this problem, I updated my phone to LineageOS 16 about two weeks ago. That update did not fix the problem, unfortunately, but it also did not make it any worse.
Since my car has updated to 2019.12.1 or 2019.12.1.1, though, the problem has gotten worse: Now, when I try to place a call, at best I'll hear a brief click, short series of clicks, or beep, and then I get silence. When receiving a call, the phone rings, I hear a ring tone over the Tesla's audio system, and the Tesla's screen shows an incoming call. I can answer the call via the Tesla's screen, but again, I get no audio. Worse than all of this, sometimes, on both incoming and outgoing calls, the Tesla's screen has gone completely blank a few times. This isn't guaranteed to happen, but it's happened at least four times to me today as I've been testing things.
Some of what I've tried, with no success:
Adjusting volume settings on both the car and the phone
De-pairing the phone and the car, rebooting both, and then re-pairing them
Updating the phone to the very latest LineageOS build (lineage-16.0-20190428-nightly-dumpling-signed.zip)
Using "developer mode" Android options to adjust every Bluetooth option I could find (AVRCP version, audio codec, audio sample rate, bits per sample, channel mode [stereo vs. mono], LDAC codec)
Testing with both incoming and outgoing calls
This same phone works fine with a Bluetooth headset. On my previous car (a 2017 Chevy Volt), I had few problems, although on about 5% of the calls, I did experience the stuttering audio problem that kicked up to 50% frequency with the Tesla before it stopped working altogether.
I've gone to Tesla's Web site and used their "contact us" link to file a bug report (although there was no "bug report" option, so it may not get routed correctly).
Does anybody here have any other ideas of what I could do, short of replacing my phone or installing another Android version? (I'm really trying to avoid the pain of setting everything up again!)
srs5694 said:
I took delivery of a Tesla Model 3 on March 30 of this year. At the time, it was running Tesla's software 2019.5.15, but within a day it had upgraded to 2019.8.4, then 2019.8.5, then 2019.12.1 a couple of days ago, and finally to 2019.12.1.1 today. Through all of this, I've had no problems with Bluetooth connections to my OnePlus 5t phone for media streaming; however, I have had problems with placing and receiving phone calls, and the problem has gotten worse with Tesla's 2019.12.1 or 2019.12.1.1 (I'm not sure which).
I never tried making phone calls in the day or so I had Tesla's 2019.5.15, but I did with 2019.8.x, with about a 50% success rate. Sometimes it would work fine, but other times I'd get very stuttery sound, as if the connection was cutting in and out about ten times per second. Initially, I was running LineageOS 15.1; however, in part because I hoped to resolve this problem, I updated my phone to LineageOS 16 about two weeks ago. That update did not fix the problem, unfortunately, but it also did not make it any worse.
Since my car has updated to 2019.12.1 or 2019.12.1.1, though, the problem has gotten worse: Now, when I try to place a call, at best I'll hear a brief click, short series of clicks, or beep, and then I get silence. When receiving a call, the phone rings, I hear a ring tone over the Tesla's audio system, and the Tesla's screen shows an incoming call. I can answer the call via the Tesla's screen, but again, I get no audio. Worse than all of this, sometimes, on both incoming and outgoing calls, the Tesla's screen has gone completely blank a few times. This isn't guaranteed to happen, but it's happened at least four times to me today as I've been testing things.
Some of what I've tried, with no success:
Adjusting volume settings on both the car and the phone
De-pairing the phone and the car, rebooting both, and then re-pairing them
Updating the phone to the very latest LineageOS build (lineage-16.0-20190428-nightly-dumpling-signed.zip)
Using "developer mode" Android options to adjust every Bluetooth option I could find (AVRCP version, audio codec, audio sample rate, bits per sample, channel mode [stereo vs. mono], LDAC codec)
Testing with both incoming and outgoing calls
This same phone works fine with a Bluetooth headset. On my previous car (a 2017 Chevy Volt), I had few problems, although on about 5% of the calls, I did experience the stuttering audio problem that kicked up to 50% frequency with the Tesla before it stopped working altogether.
I've gone to Tesla's Web site and used their "contact us" link to file a bug report (although there was no "bug report" option, so it may not get routed correctly).
Does anybody here have any other ideas of what I could do, short of replacing my phone or installing another Android version? (I'm really trying to avoid the pain of setting everything up again!)
Click to expand...
Click to collapse
Hello again from TMF (turok3000) . Can confirm I see exactly the same as you (lineage 16.0 + tesla 2019.12.1.1).
I would say you're best off posting here: https://forum.xda-developers.com/oneplus-5t/development/rom-lineageos-16-0-pie-oneplus-5t-t3843026
Do you happen to have tried with latest stock oxygenos ? I'm guessing not since you mention not wanting setup hassle (I'm in a similar situation).
Thanks for the suggestion of posting in another thread. I've done so, with a few updates.
I did back up the phone and tried installing stock OxygenOS as a test; however, the installation went badly -- it hung with a spinning logo on first boot. Thus, I restored my (mostly) working configuration. I may give it another try later, but there's only so much time I can invest in this sort of thing each day.
Any luck with this? I also have a Tesla Model 3 and the same exact problem as you. I'm using crDroid but it is largely based on LineageOS.
Maybe there is something I can try? I messed with all the dev options for bluetooth.
I've worked around it by re-installing OnePlus's OxygenOS. I'd prefer LineageOS or something else more open, but for the moment, switching to OxygenOS seems like the only solution. A caveat: I haven't tried any recent build (from the last month or so). It's conceivable it's been fixed and I just don't know it yet. Also, some others, using OnePlus phones other than the 5t (IIRC, the OnePlus 6 and/or 3) report that reverting to OxygenOS does not help them. If you've got a 5t, though, reverting to OxygenOS, although a nuisance, may be worth trying. There's a thread tracking the problem on a Tesla forum here:
https://teslamotorsclub.com/tmc/threads/bluetooth-problems-on-phone-calls-only.150774/
The problem is common on LineageOS for multiple phones, but it also occurs on some other phones, even including some iPhones. At least one unofficial LineageOS build is not affected; but that build may have been tweaked or rely on proprietary drivers. Overall, then, it looks like more of a Tesla problem than a phone problem, but it's hard to be sure without digging into the code and running diagnostics that I'm not competent to do.
srs5694 said:
I've worked around it by re-installing OnePlus's OxygenOS. I'd prefer LineageOS or something else more open, but for the moment, switching to OxygenOS seems like the only solution. A caveat: I haven't tried any recent build (from the last month or so). It's conceivable it's been fixed and I just don't know it yet. Also, some others, using OnePlus phones other than the 5t (IIRC, the OnePlus 6 and/or 3) report that reverting to OxygenOS does not help them. If you've got a 5t, though, reverting to OxygenOS, although a nuisance, may be worth trying. There's a thread tracking the problem on a Tesla forum here:
https://teslamotorsclub.com/tmc/threads/bluetooth-problems-on-phone-calls-only.150774/
The problem is common on LineageOS for multiple phones, but it also occurs on some other phones, even including some iPhones. At least one unofficial LineageOS build is not affected; but that build may have been tweaked or rely on proprietary drivers. Overall, then, it looks like more of a Tesla problem than a phone problem, but it's hard to be sure without digging into the code and running diagnostics that I'm not competent to do.
Click to expand...
Click to collapse
Ah well thanks for getting back. That is disheartening, as I had been using OOS since I got the phone on release day & finally thought I should try something different. It sounds like I'm gonna have to go through all the efforts to revert back to OOS.
For reference, it did not work for me using crDroid builds from 6/23/19 and 6/30/19.
I'll use Tesla's feedback system to put my "vote" in towards fixing these bluetooth issues.
My Model 3 received an update yesterday to 2019.24.4 and the Bluetooth calling works! Just thought you should know. I'll cross post on TMC.
Pretty much every person I've called says at random times I will cut out for 1-2 seconds, and I've experienced the same thing with hearing callers it will go out and be silent for a couple of seconds. This happens randomly, but it always happens. I don't know if it's the phone or ? Using stock dialer on Google Fi.
yes i have , but it happend to me in global stable , it has been fine using Arrow OS.
But anyways , it is unacceptable that such a thing happens with the stock system.