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.
Related
I have a problem that more people seem to have, according to the search. I couldn’t find the “audio” tab in my Bluetooth-settings, so that didn’t help me.
The problem is as follows. After 1 day the sound on my compact III mutes, including vibration. Sometimes it's after 12 hours, sometimes after 2 days, there's no distinct pattern to be recognized. Also, it doesn't seem to matter if you use the phone or not, since it sometimes is alright at night and the sound is muted the next morning. This is for all sound-events (warnings, incoming call notifications, messages, mp3 etc), however, you can make a call without any problems and hear what the other person is saying. Once you’ve hard-reset the device everything is back to normal.
It does get annoying however, since I regularly miss calls due to this bug.
I had the same problem on my Vario in the past. So I’m guessing it’s somewhere in the software I use, but apart from Total Commander and TomTom6 I haven’t installed any third-party apps.
Yup i've been having a slight problem with the sound. I thought it was like the endless knackered M500's that orange used to send me which had speaker failure after about 10minuites! (Swear they kept sending me the same 2 faulty phones - I had 5 in 5 days once!) But a play in the bluetooth seems to get it working again.
The other annoying thing is that if you leave the power management at the default settings then occasionally the screen blanks without being able to get the backlight on again - so now I have to manually turn of the screen. Stil aint much of a problem - ive had a normal days use, 2 hours of radio play, bluetooth and wi-fi on all day and still have 35% battery - wehay!
Hopefully there'll be a patch soon to sort out he glitches.
I forgot to mention I had the exact same problem on my mda Vario also. I always thought it was a problem with that specific piece, but apparantly not.
Could it be the vibrate.cab that I'm using to produce vibrations when you use the phonepad? Or should I really do some further research in the bluetooth-department?
Same problem here.
Phone becomes completely silent after 9 hours in standby mode.
I need to reset it to get back sound
Does someone know what is going on here ?
Please advise. Thank you.
I seem to experience no problems the past couple of days (fingers crossed). I used the 'speed up your WM5' tweak where you set the Glyphcache to 32768. After I reduced it to 16something the problems seem to have disappeared.
I noticed that this problem happens when for example email is automatically checked during night. If email comes in (and is not read immediately) the phone will start notifying in background.
Notifications are kept and only a program like "check notifications" will delete them manually. But still if you delete them, the phone then needs a reset
to work properly again.
This is not a memory issue, it has to do with the notifications.
I do not know how to solve it.
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.
Hi,
It's been now 3-4 months since i stopped receiving any notification from calls.
Whenever my phone receives a call, i never get notified on the watch, never (nothing happens on the screen). I correctly receive all the other notifications from my phone, but never the most important one (calls).
I've had this issue for a very long time, and with 2 different phones and roms (nexus 6p with purenexus first, and now oneplus 3t with stock). So it's definitely a problem with the watch. I've done many factory resets, etc... but never found a solution.
I was waiting for 2.0, but since it's taking an eternity i'd like to at least find a temporary solution.
Thanks
Any ideas ?
I can't be the only one to have this problem...
This might not be the answer you want to hear, but I am on the official AW2.0 DP5 from the Google site and I have never had a problem. The last I heard was that AW 2.0 has been delayed and I believe it may arrive after April now.
It was working just fine. I was listening to YouTube while I was doing other things over a Bluetooth device. Stopped YouTube, put it in my pocket, and ate dinner. Went to walk my dog, and it wouldn't play any audio. When I went to call someone to check, I only had "Speaker" as an option along with Bluetooth. I tried my Bluetooth stack by toggling it off, and rebooting the device. When stock Android 11 came up, got at System UI error after unlock. Hoped it was a glitch and turned on Bluetooth, it reconnected, but no audio, and mic doesn't pick up volume. Turned it off, did a reboot and had the headphones turned off also. got the System UI error and it doesn't show any option for audio on call for anything but Speaker. Thought crap, did a Factory format, same. Reinstalled via ADB the same version, same issue and still had the System UI crash on unlock.
Did a wipe back down to 8.0, and I didn't verify the phone worked first, but no system UI crash. Installed 10.0, and no crash on System UI, but only had speaker. Updated to latest 11.0 with the updates, and it got the System UI errors each time. I'm rolling back to 8.0 right now to verify, but I am flummoxed. Everything else works, but I have no phone option and get system UI Crashes. When I call, it vibrates, but no audio when I pickup or when I speak into the mic (used a land line to verify). Since it is Out of Support I had been considering getting a new phone, but this was still viable until today (wish Google had released a 5XL). I'm going to go back to 8.0 and test, also going to test a ROM (not sure what would be recommended, been happy with vanilla for a while, but loved Paranoid Android way back in the day on my Samsung stupid long named Nexus powered by Sprint).
But in the event that 8.0 does work, does anyone have any ideas on how to get audio to work again on a more modern android?
Sorry for the ramble, but I'm seriously confused, and it is late.
An issue like yours, that suddenly appears and persists regardless of the version of Android installed is not a good sign. In general, if it were a firmware issue you were having it should disappear upon a clean install of Android. Thus, assuming Android 8.0 doesn't work, and I don't think it will, the only answer left from my perspective is a hardware problem.
As for wishing there was a Pixel 5 XL, the 4a with 5G would fill the bill. Its screen is larger, albeit only 60Hz, and in day-to-day use it's going to sound better than the Pixel 5. The 5 taking a page from the Sharp Aquos and vibrating the entire screen to produce sound isn't something you see every day, and there's a good reason for that.
Ever since I got my Oppo Find X2 Pro, it's never remembered my ringtone/notification settings. Whether I choose an inbuilt option or do the 'Select From Files' thing, within minutes it's always reverted to Calm as the ringtone and Emerge as the notification sound.
Despite having just received the new Android 11 OTA update (CPH2025CPW_11_C_57), this problem still persists.
I reported it to Oppo many months ago, so am dismayed that it's not yet been resolved.
Are other users experiencing the same issue? Am I missing something simple? It might sound trivial, but it's not. Apps that allow me to select their notification sound work fine, but I'm missing calls and notifications because Calm and Emerge just blend into the background in noisy environments.
Help please!
John N G said:
Ever since I got my Oppo Find X2 Pro, it's never remembered my ringtone/notification settings. Whether I choose an inbuilt option or do the 'Select From Files' thing, within minutes it's always reverted to Calm as the ringtone and Emerge as the notification sound.
Despite having just received the new Android 11 OTA update (CPH2025CPW_11_C_57), this problem still persists.
I reported it to Oppo many months ago, so am dismayed that it's not yet been resolved.
Are other users experiencing the same issue? Am I missing something simple? It might sound trivial, but it's not. Apps that allow me to select their notification sound work fine, but I'm missing calls and notifications because Calm and Emerge just blend into the background in noisy environments.
Help please!
Click to expand...
Click to collapse
Hi, I've had the same issues. Only factory reset helped me. Since that all good.
Even I myself have no problem there are not all the functions presented I have resumed but Ulla I called Oppo answer that in Europe they are not yet present perhaps it is not convenient to spend so Even I myself have no problem there are not all the functions presented I have resumed but Ulla I called Oppo answer that in Europe they are not yet present perhaps it is not convenient to spend so much money For an incomplete device
hunhool said:
Hi, I've had the same issues. Only factory reset helped me. Since that all good.
Click to expand...
Click to collapse
Thank you - I was trying to avoid that because, however well I backup as much as possible, do screenshots of all my home pages etc., it still seems to take several days to get everything set up properly again. Thank goodness for password managers!
Anyway, I bit the bullet, did a factory reset and now everything is working as it should.
same problem from indeed if you notice even after the update the phone and even lowered on the ringing sounds and also on the hands-free call I reported everything but you see that Oppo does not have the to correct immediately this is why in the future I will not take any Oppo more they are very far from Samsung, Huawei, and Xioni I believe that Oppo will have a bad end in the European market