Related
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.
this is sux... how to fix it?
i tried to do hard reset but still the same problem.
usually it reboots when i'm listening a music but today it has rebooted when i was using simple "light" application...
Sounds like you have a defective phone if it's happening frequently while your phone is awake. I've had the same thing happen one time in six weeks, not enough to call it a problem, but if you're having it daily or more something is wrong with the phone. I'd exchange it if it were me.
Are you still stock?
rom
kernel
launcher
theme
Help us, help you...
good day.
lilirose said:
Sounds like you have a defective phone if it's happening frequently while your phone is awake. I've had the same thing happen one time in six weeks, not enough to call it a problem, but if you're having it daily or more something is wrong with the phone. I'd exchange it if it were me.
Click to expand...
Click to collapse
yeah, almost daily...
i was thinking about exchange but i waited 3 weeks for my device from germany to my country... so if i send them it back i will have to wait another 50-60 days...
chopper the dog said:
Are you still stock?
rom
kernel
launcher
theme
Help us, help you...
good day.
Click to expand...
Click to collapse
yeah, stock, no root, no custom, stock launcher
Well of course try to do a factory reset and very selectively install apps and see if something is causing it. If nothing specific is causing it you're probably looking at a defective device.
Nine times out of ten the reboots are caused by some apps that you are using or that runs in the background. If you wiped your phone and set it up again, do not install apps. DON'T. See if it crashes like that or not. If it still crashes then you likely have a hardware defect of sorts.
Of all apps, stay away from any apps that interfere with Android as a system. Battery life managing apps are by far the worst, for example.
Yeah, kristovaher makes a good point- it could possibly be a rogue app. Avoid not only battery manager apps but also task killers and any other app that supposedly increases battery life. None of them are really necessary or useful anyway.
i have done factory reset
installed only Go Keyboard, turned on unknown sources and usb debugging like i allways do.
copied all my mp3s to the device and was listening a music... and it reseted again...
p.s. btw, sometimes when i'm listening a music and screen is locked, the music starts lagging (slows down)... it plays normal if i press power off button so the screen highlight.
definitely an orange
guys do u really think i should return this?
it will take another 1.5-2 month untill it reachs the shop or return back to me.. not sure if they even will answer via e-mail when i'll ask for relace... i'm not sure but i think it started reboot much after 4.0.2. maybe new 4.0.3 will have positive effect. some people from my local forums also advised me to flash any custom ROM (some of them had such a problem and it helped them, reboots gone... liek they said)
This random reboot has happened to so many people. So please, don't tell him that he got a lemon. You can google up "galaxy nexus random reboot" and see how many complaint of similar issue have been posted. I also got random reboot every two days or so. But if the OP got it every day or more frequently than that, just exchange it.
If you want to proudly say your Gnex does not randomly reboot, EVER, then just use it for phone calls, browsing the internet, and Facebook only.
How often is it happening?
If its more than once a day its certainly defective. That is not normal behavior. If its every few days then deal with it.
It's happened twice under the same set of circumstances:
1. Streaming Pandora
2. Charging
Not sure if they're related but it started happening after upgrading to 4.0.2.
phiquantu said:
This random reboot has happened to so many people. So please, don't tell him that he got a lemon. You can google up "galaxy nexus random reboot" and see how many complaint of similar issue have been posted. I also got random reboot every two days or so. But if the OP got it every day or more frequently than that, just exchange it.
If you want to proudly say your Gnex does not randomly reboot, EVER, then just use it for phone calls, browsing the internet, and Facebook only.
Click to expand...
Click to collapse
I do everything with my gnex, and aside from adw launcher ex, have seen NO reboots in the month I have had it.
Aridon said:
How often is it happening?
If its more than once a day its certainly defective. That is not normal behavior. If its every few days then deal with it.
Click to expand...
Click to collapse
well, last 1.5 weeks after i stopped using NRG player and turned to stock google music player, i had no reboots... but few days ago it started to reboot again.. can't say every day, maybe in 2-3 days but only once per day... mostly when i'm listening a music.
phiquantu said:
This random reboot has happened to so many people. So please, don't tell him that he got a lemon. You can google up "galaxy nexus random reboot" and see how many complaint of similar issue have been posted. I also got random reboot every two days or so. But if the OP got it every day or more frequently than that, just exchange it.
If you want to proudly say your Gnex does not randomly reboot, EVER, then just use it for phone calls, browsing the internet, and Facebook only.
Click to expand...
Click to collapse
if it's mass problem then it's really sad....
why dont you flash 4.0.3 and rule out whether it's 4.0.2 or the phone... if it's the phone i'm assuming you're on GSM, cause if you weren't, you could walk into verizon, switch it out, and have a new one 15 minutes from now.
I had the same problem yesterday, I tought it was a problem with the kaspersky launcher. isn't that a problem of kaspersky?
asheg said:
p.s. btw, sometimes when i'm listening a music and screen is locked, the music starts lagging (slows down)... it plays normal if i press power off button so the screen highlight.
Click to expand...
Click to collapse
This is a known issue with certain encoding bit rates on music files. Enable the EQ music effects and it keeps the cpu speed high enough to negate lag, even when screen is off.
Almost all the complains about reboots are connected with 4.0.2 update. Letw wait for 4.0.3. When I was on 4.0.1 no reboots.
Howdy pards!
Got a rooted E4GT running Supernexus for about the last 2 months give or take.
All has been well until about 2 weeks ago (thereabouts), I started noticing my callers and I could not hear each other for about the first 10 secs of the call.
The delay is just long enough that it usually convinces caller they should hang up .
It happens a lot but not every time. I'd say half my calls.
My phone is integrated with Google Voice. That has had some delays but usually just small latencies (coudld still hear) and I haven't had that problem in a good year or two now.
Outgoing calls are fine usually. No delays like this.
Some things I have wondered is if it could be the PRL that needs to be updated?
And if it is, should try an update? Is that safe when running an AOSP ROM? (Doesn't seem like it would be so I haven't.)
(Corollary question: are there other updates that people typically do that folks like me should avoid?)
Attaching my Hardware Info screenshot.
Any ideas?
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.