Related
Hi all,
I've just done a search on this and have found a few posts but none with a conclusive answer to my problem.
I have upgraded to Schaps 4.x ROM and all has been fine for a good few weeks, then without [knowningly] changing anything, the phone has stopped ringing or vibrating no matter what ring tone/type I select. I still see the pop-up of the name/number of person calling but no sound whatsoever.
When I play the sample tones (using the play button in sounds & notifications) the ringer plays fine. Also other notifications (SMS, Email, etc) seem to be fine.
Anyone experienced this and found a solution?
Many thanks.
Now thats a coincendence as I'm seem to have extactly the same problem.
Not all the time thou and I have recently flashed my phone with Farias new rom.
I couldn't be bothered to diagnose the problem any more than I have already have so just did a hard-reset and finished installing my apps. I forgot to create a working back-up before and will do one this time!
It would still be good to know if this problem does get resolved.
yes, i have the same problem with
Shamanix`s WM6 Ultimate v2, which is based on Schaps 4.x ROM i presume.
so it looks like a bug in the OS itself, or maybe something in Schaps Advanced Config Tools.
because sometimes Vibration starts working (sometimes for a couple of hours, sometimes just until the next call, sometimes for a couple of days) and then it doesnt work again.
frod.mrv said:
yes, i have the same problem with
Shamanix`s WM6 Ultimate v2, which is based on Schaps 4.x ROM i presume.
so it looks like a bug in the OS itself, or maybe something in Schaps Advanced Config Tools.
because sometimes Vibration starts working (sometimes for a couple of hours, sometimes just until the next call, sometimes for a couple of days) and then it doesnt work again.
Click to expand...
Click to collapse
Actually, sorry, my mistake in my original post, I used to have the Schaps ROM but then changed it to Shamanix one too- based on Schaps though like you've mentioned.
Anyway, I got just a bit annoyed with it and like I said, did a hard-reset. I re-installed all the same apps and no problems so far. Not sure what triggered the problem though.
the same problem exactlly, I flashed Faria - the last -I think it is a 6.1 error
Phone ringer resets itself to silent.
Just to be clear about the problem I am having, my phone periodically turns off the ringer and vibrate and goes to silent without any prompting.
I first noticed this when I flashed to a Faria's first 6.1 rom. It was suggested that the Home "profiles" tab had something to do with this. Apparently the "Auto" switch in the profile tab is supposed to turn off the ringer during appointments. I have not ever used the profiles, and in fact I usually disable the profiles tab in HTC home. Also at that time, I found that the ringer would be randomly turned off even when there were no appointments scheduled.
I switched to a 6.0 rom and continued to have the same issues. I have flashed a OEM rom and reflashed the newest Faria 6.1 rom and I am still having the ringer turn to silent, however now it does seem to be primarily when an appointment is scheduled, though I have never set it to "Auto" in the profiles.
Does anyone have any suggestions on how to stop this? It is frustrating to be missing calls every day.
seems it is a very old problem:
http://forum.xda-developers.com/showthread.php?t=279920
maybe it is something with Hermes hardware problem?
another thread about it:
http://forum.xda-developers.com/showthread.php?t=288728&highlight=mute;+no+sound
mostly everybody who has this problem start having it NOT after flashing\updating software, but after sometime of just using a device. so it SEEMS to be a hardware problem with some contacts, which brake\disconnect cuz of vibrations and\or just oxidation\corrosion.
I have the same problem, and I don't think the above threads are the same thing. The ringer just doesn't work for incoming calls, regardless of which ringtone I use. I have it set to ring and vibrate, and up until a couple days ago, it would at least vibrate, but no ring. I was ok with that, but now it won't vibrate. I do get the voicemail notification sounds, and I get sound for incoming text messages. Vibrate also works with text messages and such.
And now that I'm typing this, I just received a call, and the phone vibrated! It was set to ring and vibrate, though. At least it's vibrating again, but I miss my ringtones!
I'm running K's rom version 1.31 right now, but I'll be installing K's final rom as soon as the download finishes. I also plan on installing all my programs one by one and soft resetting in between. Hopefully if it's a software conflict causing this, I can narrow it down that way.
xviiivx said:
I have the same problem, and I don't think the above threads are the same thing. The ringer just doesn't work for incoming calls, regardless of which ringtone I use. I have it set to ring and vibrate, and up until a couple days ago, it would at least vibrate, but no ring. I was ok with that, but now it won't vibrate. I do get the voicemail notification sounds, and I get sound for incoming text messages. Vibrate also works with text messages and such.
And now that I'm typing this, I just received a call, and the phone vibrated! It was set to ring and vibrate, though. At least it's vibrating again, but I miss my ringtones!
I'm running K's rom version 1.31 right now, but I'll be installing K's final rom as soon as the download finishes. I also plan on installing all my programs one by one and soft resetting in between. Hopefully if it's a software conflict causing this, I can narrow it down that way.
Click to expand...
Click to collapse
same here.. i already try installing a few diff rom.. but it still cant fix the mute problem.. can anyone else help us? hmm
I got K's final rom installed, and I finished installing all of my crap. My ringtones work fine now. I have to say, I wish I would have installed this rom earlier; it's much faster. I think I'm going to backup my registry now, so if the ringtones do quit working again, I can at least prove whether or not the registry had the problem. I'll update if I learn anymore about this.
Like I mentioned in a earlier thread, I installed Shamanix`s WM6 Ultimate v2 ROM which was about 5 weeks ago; ringtones were working perfectly and all of a sudden they stopped.
I'm not sure if I did 'something' by accident to cause this problem. But having reflashed using the EXACT same ROM and apps, the ringtones are working fine again.
f I'm on a call already and a new one comes in, no matter what happens, the caller on the other line cannot hear me even though i could hear them. several hard resets dont seem to work. has anyone had the same problem or a solution for it?
thanks
your not the only one, ever since i switched to my current rom, i been experiencing this problem. perphaps its bug in the rom.
Does it drop, or can they just not hear you any more?
I upgraded to Radios .77 and .91 with no serious change. As soon as the "Missed Call" notification comes in, the other party can't hear me any more.
[ Edit: Fixed --- Apparently, the Volume Leveling bits are still buggy. ]
Settings -> Personal -> Phone -> Advanced
"Reduce noise in phone calls" : Never
Hmmm, I have the same issue, but not the option in phone menu, as you have. Any ideas where to seek in registry for that?
I can only assume you guys are talking about Energy roms? If not then just go and download his latest rom and it fixes that issue. It's been discussed at nausium in the energy thread.
You are right, its Energy ROM.
Hell I didn't want to hear to that. All the settings and stuff again ;(
Hi, just want to start out saying that the Evo is such an amazing phone!
But.... there is this issue.
Sometimes (less then %10 of the time) and at random as far as i know, when i am making and receiving a phone call I only hear my voice in an echo. Like when you have 2 phones, you call one, and talk and listen to both at the same time. I can NOT hear anything else except my own voice, when obviously the person on the other end is talking. I have to hang up and try again. One time, this happened 4 times in a row, but usually its just once.
When I'm at home, Im connected to the Airave. Im not sure this has anything to do with it as I dont specifically remember having this issue when Im not connected to it. Ill try to remember if this happens again when im not on the Airave.
Anyone have this problem?
I am rooted and am running a Sense based rom (something thats almost pure stock Sense).
Also, on another note, is there someway to fix the calling lag? what i mean is: someone calls me, on their end it rings 3-4 times before my phone actually starts ringing. (with the GV integration it was worse, it would ring 5-6 times, sometimes go to voicemail and my phone would either just start ringing or just a voicemail notification would pop up)
If nothing can fix this, can I at least change the number of rings? Im think 10 would work.
Thanks!
Every phone I've ever had, and I've had a lot of them, at some point would ring zero to one time on my end while the caller has heard several rings. The same thing can be said about the echo. I assume there are a number of reasons why those things occur including but not limited to roaming, cell handoff, signal strength & fluctuation and network problems. If you are experiencing the things you mentioned on a frequent basis, you may want to notify Sprint.
posting & replying via the XDA Premium app.
oh i forgot to mention that the echo problem never existed on the HTC Hero I had.
there was a call lag/bug (on the hero), but that was a 2.1 issue that was solved with a software update. By the time the update came out, I was already on cyanogenmod, so those issues didnt effect me.
Im thinking of trying out some gingerbread roms that have the updated Sense rom for the Evo. I havent seen one that i like yet (tbh, i havent really looked yet).
Could be this modified Sense rom? i dunno. Maybe I can find where I got it. It was included in a root method i used back in December.
I used to have echo on my evo until I upgraded to the newest radio found here...
http://forum.xda-developers.com/showthread.php?t=715485
Of course flashing a radio is dangerous so follow instructions thoroughly
tim
is it the kind of echo im referring too? were you only hearing yourself until you retried the call?
I get the echo, on my us cellular phone for work, a razor. It must just be a cellular thing.........
this echo has never happened on any other phone before. this leads me to believe that its software based on my phone. hardware would almost always repeat the problem. one of these days im going to flash another rom and see if that fixes it.
Hi guys i have a really weird problem with my one plus 3 ever since i got it, it only worked well for a few days then afterwards i had this annoying issue
the issue is that when i receive a call i cannot see who is calling the caller id is hidden under all of my notifications and at times the screen does not even turn on
it is annoying as i cannot see who is calling or even able to pick up my calls
thank is going on
everything else is functioning properly
Some screenshots then maybe able to help you
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.