Hello everyone,
Right now, on my OnePlus One, I am unable to make calls or receive calls. I'm currently still working on building Dirty Unicorns, and this only happens on some ROMs (calling works fine on others) - e.g. CM, PureNexus work, but updateing's nougat ROM used to give me the same issue. SMS and mobile data are completely unaffected and work without any issue. I can see that a phone call is incoming and answer it, but I cannot hear the person on the other end, nor can they hear anything I say. When making outgoing phone calls, the same thing happens - neither party can hear the other (but the phone call does connect).
I've tried using audio sources (hardware/qcom/audio) from CM, DU, and sultan's cm13 (with Android N policy change patches applied), and the problem persists. I'm thinking that the issue might be in some other audio-related repo that I haven't checked yet, but I'm not sure where.
Here's a logcat of the exact issue: http://pastebin.com/2YJTDUfy. Some areas of interest are starting from line 334 onwards and from 581 onwards.
Thanks in advance.
Perhaps has something to do with noise cancelling mics. Look up microphone fixes for OnePlus One - this might send you down the right path.
If not this, try different modems.
Sent from my Pixel using Tapatalk
Related
Are there many other people having missed call notification problems with all the ROMS based on the 5.2.318 base ROM.
I have tried XM6 and TNT 2.0, and both ROMS are great. Except in XM6, all missed calls that go to voicemail were showing up as 1 second received calls. In TNT 2.0, incoming calls that I receive while on another call that go to voicemail, show up as 1 second received calls. If i press ignore or the caller hangs up before the call goes to voicemail, they show up as regular missed calls (based on my testing). I am assuming this is not a radio rom issue, as I am receiving the calls. I would just like to know if other people are experiencing the same problems with ROMs based on the 5.2.318.
Thanks in advance.
zakhir_n said:
Are there many other people having missed call notification problems with all the ROMS based on the 5.2.318 base ROM.
I have tried XM6 and TNT 2.0, and both ROMS are great. Except in XM6, all missed calls that go to voicemail were showing up as 1 second received calls. In TNT 2.0, incoming calls that I receive while on another call that go to voicemail, show up as 1 second received calls. If i press ignore or the caller hangs up before the call goes to voicemail, they show up as regular missed calls (based on my testing). I am assuming this is not a radio rom issue, as I am receiving the calls. I would just like to know if other people are experiencing the same problems with ROMs based on the 5.2.318.
Thanks in advance.
Click to expand...
Click to collapse
I haven't seen this problem, but then I don't get that many calls that overlap (though I just did a few minutes ago without any trouble)
well i was dialing a phone number, after the first ring.. I intercepted a text, and it hung up my call.
yes there is an issue with this base rom, so we will look after up to have the fixing
mattk_r said:
I haven't seen this problem, but then I don't get that many calls that overlap (though I just did a few minutes ago without any trouble)
Click to expand...
Click to collapse
Maybe I'll give Pandora 3.2 a try mattk_r, thanks.
zakhir_n said:
Maybe I'll give Pandora 3.2 a try mattk_r, thanks.
Click to expand...
Click to collapse
no promises though
Remember, GPRS is usually the biggest culprit to phone issues. Keep it off when you don't need it, and I believe you'll see better performance, regardless of the ROM you use.
I've seen this issue with XM6 and Pandora (3.1, haven't flashed 3.2 yet).
Mainly if someone calls me and I don't answer, more than 50% of the time, the call is not registered as "missed". Instead, its seen as a received call of 1 second duration.
Good point about GPRS. I use push-email, which means GPRS would be on all the time. Mind you, the other WM6 builds I've tried have been perfect in this respect (but had other issues that seem to be fixed in this build...). The more I think about it, the more I wonder if it is push-email thats causing the problem.
If we could fix this issue, this would certainly be the best build.
I installed Skype onto my rooted Galaxy SIII running 4.1.2 and ParanoidAndroid 2.56, my call quality is excellent through my cell line however trying to use Skype for video calls on my device leaves nothing but static on the other end. Even when I stay totally silent, the receiving line will not hear a peep but once I raise my voice, the white noise comes out to wreak havoc and does not stop until I mute the microphone in-call. Un-muting will only bring back the white noise. I can hear my caller just fine, but he cannot hear me. I have tried calling and receiving both ways through Wi-Fi, LTE and 3G connections to no avail.
I have also reset the dalvik cache and fixed permissions, in addition to disabling noise cancellation through the Call Settings on my phone. I'm running the kernel which came with my ROM, which I honestly cannot remember what it is. Would flashing another kernel help with a problem like this or would it only solve issues through my cell number's telephony? I have excellent call quality through my cell phone, but Skype itself leaves nothing but static even when I am not speaking. I would try to clean both my microphone holes on the bottom and the top if the static were to be on my cell telephony but it seems like it is only limited to Skype itself. I may try and back up my ROM through CWM recovery and wipe the system.
Anyone else experience an issue such as this and could give advice?
I use the Skype version found here:
http://forum.xda-developers.com/showthread.php?t=1148708
I was having the same problem until I enabled Use MODE_IN_CALL found in the Sound Section of Advanced Settings. Hope this helps!
Hi,
So I've had this problem ever since I flashed the CM 11 ROM, and its persisted even after flashing later builds.
To best understand this problem, go to Youtube: Type Atrix 2 Audio issue, and check out the first video. (Sorry! being a noob i'm not allowed to post links yet)
Issue: During outgoing calls to certain cell phone numbers, the caller gets a robotic sound of what the other person is saying. Receiver cant hear anything at all.
Also when receiving calls from certain cell phone numbers(Usually the same numbers with the outgoing problem) the above issue takes place.
I tried the In-call Call Volume app as well, it doesn't fix the issue. Also someone mentioned about switching to 2G, that didnt fix my issue either.
Any help and suggestions would be much appreciated.
Thank you ! :cyclops:
Okk mate..for the fourth time im telling this..turn data off and change network to 2g..tadaa problem solved
Sent from my MB865 using Tapatalk 2
Curious is anyone else can replicate this issue I am having. When I receive a phone call, the person on the other end of the line hears a really bad echo . It seems to only happen on incoming calls. If I hang up and call the person back, the echo goes away. I'm on Project Fi. I have weak cell signal so I stay connected to WiFi at home mostly. I'm not using hangouts or anything, just the regular dialer.
To produce the problem:
Receive incoming call over WiFi
Ask the person on the other end if they hear an echo?
If so, hang up call the person back (over same WiFi connection). Does echo go away?
Seems software related since calling the person back makes the echo go away. Thinking about factory reset unless others can verify it happens to them. I am on the most recent November security patch.
In case anyone cares, I contacted Fi support and they believe it is very likely to be a bug. I submitted a couple bug reports after making and receiving calls. Engineers are supposed to contact me back within 48 hours.
The same has happened to me when I call my friend with Discord. I haven't tried calling the person myself, that might fix the problem. I'm using unlocked with Verizon.
@bballjohn32 The same exact problem on first gen pixel (project fi).
Only when someone is calling me over wifi do they hear an echo. Also to note, when either making or receiving a call over wifi the phone says call via "unknown ssid". prior to Oreo 8.1 it used to name my wifi network name. I spent two hours with support and ended by performing a hard reset, that did not fix it either. They are issuing me a refurbished phone which I'm not too happy about...
Hey everyone,
For anyone experiencing this issue, I found a temporary fix until Google releases a patch.
First of all, you need a rooted phone for this to work. I'm NOT going to cover the details here on how to obtain root, but a quick Google search will certainly help you out on this one. If your phone is still under warranty, then this procedure is maybe not for you.
1 - Have a rooted phone that experiences the sound issue where an inbound caller hears himself in an echo.
2 - Install a free app called DeFluence from Google Play.
3 - Open DeFluence and grant Superuser rights to the app.
4 - Tap "Disable Fluency". If it was successful, you will see the message "DeFluence was granted Superuser rights".
5 - Reboot the phone and enjoy inbound calls without the echo issue.
The only drawback I can see from this is that the other person might hear some background noise of wherever you are located, but I think it's still a great temporary solution.
So all in all, this most probably means this is a software issue that slipped into Android Oreo, and hopefully Google will be able to find a solution soon.
What I believe is happening is that the mic used for noise cancellation is picking up the voice of the caller and echoing it back into the call, when it should really just act as a noise cancelling microphone and not a regular mic.
If you have any questions, feel free to ask.
I caught such a bug - during a call I hear, but nobody hears me (at all). All other apps that use a microphone perfectly worked (voice recorder, fb messenger call, skype and so on). I made 10 calls in both directions, the 'microphone' did not work. With a speakerphone and bluetooth headset nobody heard me too. So that's why I believe that was internal call bug in the firmware, not a mic problem.
It was fixed only with rebooting (off and on).
I happened with my SM-G930T with lastest firmware (G930TUVS4BQJ2). I have been using it just for 13 days, but this is a very unpleasant bug and I do not know what to do. Should I change it, or is it a rare software bug? Or maybe it is a bug only in T-Mobile firmware?
Did someone encounter the same problem?