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?
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.
Ok, so I have done quite a bit of research before posting and have yet to find someone with a similar problem. For some strange reason my Galaxy SII is automatically answering calls from an Unknown Number. It always happens in the morning while I am asleep and I have missed job interviews and woken up late on many occasions to no alarm clock but a 3-5 hour phone call from some unknown number. I have tried using the blacklist to block all unknown numbers but the blacklist doesn't even work on my phone. I have installed different apps to block the numbers as well and they seem to work during the day while I am awake. I have 2 of these on my plan and mine is the only one that does this. I was hoping someone would have some insight as to what is going on.
jagon91 said:
Ok, so I have done quite a bit of research before posting and have yet to find someone with a similar problem. For some strange reason my Galaxy SII is automatically answering calls from an Unknown Number. It always happens in the morning while I am asleep and I have missed job interviews and woken up late on many occasions to no alarm clock but a 3-5 hour phone call from some unknown number. I have tried using the blacklist to block all unknown numbers but the blacklist doesn't even work on my phone. I have installed different apps to block the numbers as well and they seem to work during the day while I am awake. I have 2 of these on my plan and mine is the only one that does this. I was hoping someone would have some insight as to what is going on.
Click to expand...
Click to collapse
What rom are you using?
I haven't installed any roms so I'm just running straight stock. I love this phone but the past couple of days it's had a mind of its own. It also keeps playing music randomly... That started today. I have had Rihanna start playing about 6 times...
exchange it
I have to be appless and sd cardless for a whole day to get it exchanged. However at least I will get an exchange!
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.
A few times a week, usually daily, the phone and SMS functions will stop working. Sometimes I'll notice it in the morning, sometimes the afternoon or evening. I'll try to make a call or send an SMS, and it will fail. When I try to make a call, after hitting the place call button, the dialer locks up.
When the phone is in that state I can't receive calls or SMS either. So I have to worry about how many hours it was like that.
A reboot fixes the problem. After a reboot, the phone is fine at least until the next day.
I've had this problem with every version of CM11 I've tried. A dozen or so builds over the course of six months to a year. A can't find any mention of anyone else having this problem.
Pixel 2 XL Issues Dialer extremely slow & Deafening notification beeps during calls
*Copy/pasted from the Pixel 2 forum. Whoops!*
Hi all,
I had a quick search on the forums but couldn't find anything related to this. I'm unsure if it's a problem with just the Pixel 2 XL or Android. I've installed all OTA updates and the phone is running 8.1.0. It had both of these errors prior to updating. I have also replaced the entire handset and tested again. Still occurring. I have a Pixel 2 also, which does NOT experience these issues. I'm also running stock, no root/roms. *edit* I went through Google support for both issues, they couldn't find any solutions. They suggested a factory reset and then replaced the handset.
The dialer:
Intermittent problem. Basically when you open the dialer or a contact and initiate a call, the app often freezes for an indeterminate amount of time. It could be 10 seconds it could be over a minute. Eventually it will move to the "call" screen and then freezes/lags again. Once more this can be any length of time up to a minute or more. All other apps work perfectly fine during this process. Eventually the call initiates and you can hear it ring, once in call everything behaves normally.
The notifications:
This one is simple. During a call receiving an SMS or other notification results in an electronic beep sound which plays at full volume. It does the same thing after the call ends. I'm not sure if it's using call or external speakers as the volume is so damn loud it doesn't matter. It legitimately causes me to throw the phone away from my ear and I cannot hear anything besides buzzing for 20 minutes. It actually hurts.
Nothing I do has stopped this except to turn on DND before I make or receive a call, which is useless. I read a few other threads about this being a new feature in 8.1.0 and "intentional". However I think those are referring to the call end beep, or notifications during a call that make the designated notification sound, not a deafening beep. The threads I read suggested removing third party apps and phone permissions, I used a brand new handset and the beeps still happened.
Please does anyone have a suggestion? I'll try anything at this point.
I have noticed a similar problem that has cropped up recently - I cant make consecutive calls. If I hang up from a call and then try to make another the phone sits there. The phone button animates but doesn't do anything. If I try 20 seconds later it will sit there for about 10 seconds and then make the call. If I wait about two or so minutes it will work. Incoming calls are different.. if I am in that "period" of time, the phone will ring and if I am not in the phone app - meaning the incoming call screen pops up - I can answer it. If its a heads up incoming call I cant answer it. I must turn the screen off and then back on to get to the full screen to answer it. I am on 17.0.186697879 which I believe is the latest.
I've had the delayed calling problem for almost 2 months. The problem also includes sometimes not being able to answer a call from the notification shade when the screen was already on. Toggling airplane mode alleviates the problem temporarily.
There's a lengthy thread in the OG pixel threads with the many users with the problem. Also a lengthy thread on one of the Google support threads. Someone there suggested it had something to do with the mlb at bat app. I think that has since been debunked. I haven't found a solution yet and Google hasn't made an official acknowledgement yet.
This issue suddenly appeared on my Pixel 2 couple of days ago. Tried all the hacks and solution, but even turning off all the knobs in the phone permissions screen didn't help.
I have android 8.1.0
Build OPM1.171019.021