Related
Greetings my nexus brothers.
I post here today to inquire of a strange phenomenon that has befallen my device.
You see, when I try to make calls... I don't hear anything from the earpiece unless i plug in my headphones.
But before you jump to conclusions, I too thought it was a simple earpiece hardware failure however, when I made calls through the vonage app the sound came through the earpiece like normal.
I am currently running the device on android 4.2.2 with the ParanoidAndroid rom and mako kernel.
Does any of you have a clue as to what might be the issue?
ketonkss4 said:
Greetings my nexus brothers.
I post here today to inquire of a strange phenomenon that has befallen my device.
You see, when I try to make calls... I don't hear anything from the earpiece unless i plug in my headphones.
But before you jump to conclusions, I too thought it was a simple earpiece hardware failure however, when I made calls through the vonage app the sound came through the earpiece like normal.
I am currently running the device on android 4.2.2 with the ParanoidAndroid rom and mako kernel.
Does any of you have a clue as to what might be the issue?
Click to expand...
Click to collapse
what about trying an other kernel...?
regards
did you update your radio? you cant use the old one with 4.2.2 roms. you absolutely must update to the 4.2.2 radio.
molesarecoming said:
did you update your radio? you cant use the old one with 4.2.2 roms. you absolutely must update to the 4.2.2 radio.
Click to expand...
Click to collapse
you are absolutely right when it comes to the older 33 radio. but ive had a few people report that the even older 27 radio is working with 4.2.2 roms. i havent tried, so i cant confirm it myself.
It seems strange however, that a radio problem would cause an earpiece issue... because I am still able to make calls, but I cant hear out of the phones earpiece unless i make internet calls
at any rate im going to try to reflash paranoid android and if this doesnt work I will try the radio suggestion
ketonkss4 said:
It seems strange however, that a radio problem would cause an earpiece issue... because I am still able to make calls, but I cant hear out of the phones earpiece unless i make internet calls
at any rate im going to try to reflash paranoid android and if this doesnt work I will try the radio suggestion
Click to expand...
Click to collapse
i dont think that its as much a radio issue as it is a driver issue. this started happening when the rest of the 4.2.2 drivers were released last week.
simms22 said:
i dont think that its as much a radio issue as it is a driver issue. this started happening when the rest of the 4.2.2 drivers were released last week.
Click to expand...
Click to collapse
You must be right... I tried reflashing Paranoid Android (Latest Version), Tried the Franco kernal, and flashed the 33 radio img.. but its still the same behavior... phone makes calls but earpeice is silent.
Do you think i should reflash the drivers?
ketonkss4 said:
You must be right... I tried reflashing Paranoid Android (Latest Version), Tried the Franco kernal, and flashed the 33 radio img.. but its still the same behavior... phone makes calls but earpeice is silent.
Do you think i should reflash the drivers?
Click to expand...
Click to collapse
no. try the 27 radio, i hear people have luck with it and 4.2.2 roms. if not, then youll need the 48 radio http://forum.xda-developers.com/showthread.php?t=2087227
ketonkss4 said:
It seems strange however, that a radio problem would cause an earpiece issue...
Click to expand...
Click to collapse
those that had old radios all reported they couldnt make calls anymore. they could not hear the other person speaking. sounds awfully familiar, right? when aosp 4.2.2 was released and the kernel was still 4.2.1 the radio even caused stuff like autobrightness to fail - so you never know how deeply it affects your system.
point is, you just cant use your radio anymore, they're obsolete. some people on xda have suggested that google has deliberately made the 4.2.2 compounds mandatory to make you abandon the lte capable radios. so you basically have the choice now, stay for ever on 4.2.1 or update.
molesarecoming said:
those that had old radios all reported they couldnt make calls anymore. they could not hear the other person speaking. sounds awfully familiar, right? when aosp 4.2.2 was released and the kernel was still 4.2.1 the radio even caused stuff like autobrightness to fail - so you never know how deeply it affects your system.
point is, you just cant use your radio anymore, they're obsolete. some people on xda have suggested that google has deliberately made the 4.2.2 compounds mandatory to make you abandon the lte capable radios. so you basically have the choice now, stay for ever on 4.2.1 or update.
Click to expand...
Click to collapse
...Yeah I think you make a good point. Damn, and here I was trying to hold out until t-mobile rolled out their LTE so I could finally make use of the LTE chip.
I suppose ill just have to upgrade the radio... I could always go back right?
Well hopefully Google releases a LTE capable, 32 gig Nexus 4 and stops toying with us... lord knows I would give so many things for that.
Hello,
Apparently since I flashed my LG G2 int. on CM11, I have a echo problem . The people online with me have a voice return in their phone (they hear their voices back)
Do you have any idea how to solve this problem?
berurier1 said:
Hello,
Apparently since I flashed my LG G2 int. on CM11, I have a echo problem . The people online with me have a voice return in their phone (they hear their voices back)
Do you have any idea how to solve this problem?
Click to expand...
Click to collapse
judging by the fact that the kernel from wootever and the PA kernel don't have this issue i would say the issue is with the kernel used on CM11 however both wootevers and the PA kernel are not compatible with the official cm11 builds and result in a strange bootloop screen flicker.
Echo
berurier1 said:
Hello,
Apparently since I flashed my LG G2 int. on CM11, I have a echo problem . The people online with me have a voice return in their phone (they hear their voices back)
Do you have any idea how to solve this problem?
Click to expand...
Click to collapse
I've had this problem on both CM11 and PA4. I heard that this is a bug on almost all AOSP 4.4 roms. The latest CM nightly (12-10) actually fixed it. I have the ATT version so I'm not sure if it's fixed on your variant.
Something even more annoying for me has been that I'm hearing touch sounds during voice calls. I like the new touch sound but I don't want to hear it while I'm talking to someone on the phone. Anyone else experiencing this?
Thank you for your answer.
I'm on the latest CM11 nightly (20131209) for LG G2 int.
I think I'll still stay on CM11 and wait until a fix.
No problem. I'm sure the fix will be included in the next build.
Have you heard that weird noise during voice calls? I have only seen one other person mention it. If no one else has the problem I may swap out my phone for another one before my return period expires.
No it does not tell me anything.
Sorry
JBiBBs5 said:
No problem. I'm sure the fix will be included in the next build.
Have you heard that weird noise during voice calls? I have only seen one other person mention it. If no one else has the problem I may swap out my phone for another one before my return period expires.
Click to expand...
Click to collapse
I'm having the exact same problem. People say they have all kinds of crazy feedback while on the phone with me, and I also hear touch sounds in phone calls. I have the VZW model, so this confirms that it's a nightly bug. I'll just wait for a fix :good:
Yea the echo bug is annoying. I'm trying out the 801 Carbon Rom and it doesn't have the bug. Its JB but has a lot of options.
Sent from my LG-D801 using Tapatalk
I see some people say the echo issue is fixed on some Roms but I still have it. Guess I'll go back to a stock Rom for now.
Sent from my LG-G2 using Tapatalk
sweets55 said:
I see some people say the echo issue is fixed on some Roms but I still have it. Guess I'll go back to a stock Rom for now.
Sent from my LG-G2 using Tapatalk
Click to expand...
Click to collapse
I am on stock rom and do have this issue. Reducing the volume during a call solves the problem for the other party.
But you need to reduce to almost a minimum.
the echo problem is persistent. it obviously is not a kernel issue because ive tried about all the roms there is for the d800 and they all have the echoing,even the roms like Mahdi that say echo fix.
i've been to AT&T a few times for the issue,even returned a phone because of it,tried swapping out sim cards and nothing.
it seems more of a software or hardware issue.
i only have the echoing when calling people that are on the same carrier as me. every other carrier seems to be clear and no echo.
maybe its AT&T???
bukmba said:
I am on stock rom and do have this issue. Reducing the volume during a call solves the problem for the other party.
But you need to reduce to almost a minimum.
Click to expand...
Click to collapse
I've never had the echo on a stock Rom but do on most of the KitKat Roms. Turning the volume down does nothing for me.
podagee said:
the echo problem is persistent. it obviously is not a kernel issue because ive tried about all the roms there is for the d800 and they all have the echoing,even the roms like Mahdi that say echo fix.
i've been to AT&T a few times for the issue,even returned a phone because of it,tried swapping out sim cards and nothing.
it seems more of a software or hardware issue.
i only have the echoing when calling people that are on the same carrier as me. every other carrier seems to be clear and no echo.
maybe its AT&T???
Click to expand...
Click to collapse
I have the 801 build and Mahdi does get rid of the echo for me. I think he's trying to figure out exactly how to fix the issue and once he's done maybe that will fix it for everyone. Or we might just have to wait til audio drivers or whatever it is, is updated. If I see one 801 user say echo in any Rom I won't flash it.
Oh god i been through this with the galaxy s2. I sure hope it's not hardware. But our issue was with the noise reduction. I just noticed 4.4 roms doesn't have that issue. If i remember it was a combination with noise reduction and radio.
podagee said:
i only have the echoing when calling people that are on the same carrier as me. every other carrier seems to be clear and no echo.
maybe its AT&T???
Click to expand...
Click to collapse
the echo issue seems to be out of control. happens to a lot of modern phones too it seems all across the carriers.
D801 T-Mobile stock rooted here and people on the other hand on the same carrier hear the echo. strangely enough, there's no echo whatsoever when using wifi calling. not sure what to do about it.
Sent from my LG-D801 using Tapatalk
I never have echoed or distorted voice unless traversing bands or super low signal.
I have also the echo bug on all cm11 roms. Only the latest Mahdi have solved this problem. But what is the issus? On strock or stock custom roms i dont have a echo.
its a big known issue come on devs n mods please help us:crying:
Im running the latest CM11 mod with KK 4.4.4, and Im facing trouble with the call quality. The voice of the other person is very low .. even on loudspeaker.
Does any one know what could be done about this? I've checked the settings and found nothing useful there.
Thanks
idr3s said:
Im running the latest CM11 mod with KK 4.4.4, and Im facing trouble with the call quality. The voice of the other person is very low .. even on loudspeaker.
Does any one know what could be done about this? I've checked the settings and found nothing useful there.
Thanks
Click to expand...
Click to collapse
Could it be, that it's the fault of the other persons phone?
Tkkg1994 said:
Could it be, that it's the fault of the other persons phone?
Click to expand...
Click to collapse
I'm going to test it properly and get back to you on this ..
Though since I had this ROM I've have noticed some call quality probs with different people. For example the loudspeaker volume isnt loud enough at max volume.
idr3s said:
I'm going to test it properly and get back to you on this ..
Though since I had this ROM I've have noticed some call quality probs with different people. For example the loudspeaker volume isnt loud enough at max volume.
Click to expand...
Click to collapse
Did you check CM thread before asking? I'm not being rude, but this bug is listed in the first post and and discussed along the thread. There is also the available workaround over there.
Well I didn't check the thread.. but I definitely went through the first post to get instructions for installing the rom and I don't think I've seen anything there for this.
Though I guess I'll take a second look if you say they've already posted something there.
Thanks.
idr3s said:
Well I didn't check the thread.. but I definitely went through the first post to get instructions for installing the rom and I don't think I've seen anything there for this.
Though I guess I'll take a second look if you say they've already posted something there.
Thanks.
Click to expand...
Click to collapse
Good idea just to help you, it's right after the instructions for installing the ROM, where it says know bugs. There is only this bug listed: random voice in call quality. You can flash the Chinese modem, it will fix, but it could cause more wakelocks. And if you had the 4.2.2 touchwiz rom before flashing CM, you will not be able to make call again if you decide to restore the 4.2.2 TW ROM without flashing a recently modem. New modems have a different imei code mode that overwrite the old one.
Let's see .. Dont feel so comfortable doing all this but might have to later on.
Thanks for the info [emoji1]
So in the past I've mention that OnePlus One had issues if you try to charge it while it's turned off, the charging led(red) isn't on and I went here to tell my story:
https://forum.cyanogenmod.org/topic/114705-oneplus-one-charge-when-turned-off-charging-and-led/
Well not much people got interested in this so I still persuit this and open a case in the "famous" jira cyanogenmod reporting system and open this thread:
https://jira.cyanogenmod.org/browse/BACON-4187
So even since CM12.1 this issue exist and maybe from previous android versions, now I saw today that it's been solved, so I update my phone to the latest official "cm-13.1-ZNH2KAS1KN" and check it out ...guess what, no resolve so I tried to post on JIRA Cyanogenmod that the ZNH2KAS1KN still has the issue
When I figure out that the "RESOLVED" from "Pat Erley" which was assigned to fix it was to make my account "inactive" - great resolve
P.S. When I open this issue one of the cyanogen guys told me "I can't add votes and I'm not going to advertise the issue (and I would rather you not either). The activity would have been me assigning the issue"
He didn't want to "advertise" the issue, why? ...why he wanted this to be quiet? (this is visible from the jira cyanogenmod link I've mention in the second link
P.S.2 Share this to as many OnePlus One users possible, cyanogenmod jira is useless(and they mute you if they don't like what you are saying)
evronetwork said:
So in the past I've mention that OnePlus One had issues if you try to charge it while it's turned off, the charging led(red) isn't on and I went here to tell my story:
https://forum.cyanogenmod.org/topic/114705-oneplus-one-charge-when-turned-off-charging-and-led/
Well not much people got interested in this so I still persuit this and open a case in the "famous" jira cyanogenmod reporting system and open this thread:
https://jira.cyanogenmod.org/browse/BACON-4187
So even since CM12.1 this issue exist and maybe from previous android versions, now I saw today that it's been solved, so I update my phone to the latest official "cm-13.1-ZNH2KAS1KN" and check it out ...guess what, no resolve so I tried to post on JIRA Cyanogenmod that the ZNH2KAS1KN still has the issue
When I figure out that the "RESOLVED" from "Pat Erley" which was assigned to fix it was to make my account "inactive" - great resolve [emoji14]
P.S. When I open this issue one of the cyanogen guys told me "I can't add votes and I'm not going to advertise the issue (and I would rather you not either). The activity would have been me assigning the issue"
He didn't want to "advertise" the issue, why? ...why he wanted this to be quiet? (this is visible from the jira cyanogenmod link I've mention in the second link
P.S.2 Share this to as many OnePlus One users possible, cyanogenmod jira is useless(and they mute you if they don't like what you are saying)
Click to expand...
Click to collapse
The build released in July when he closed the issue ticket is ZNH2KAS254. Check by flashing that build first if it's actually fixed. I don't personally ever charge with screen off and I'm on Omni right now so can't confirm for you at the moment.
Renosh said:
The build released in July when he closed the issue ticket is ZNH2KAS254. Check by flashing that build first if it's actually fixed. I don't personally ever charge with screen off and I'm on Omni right now so can't confirm for you at the moment.
Click to expand...
Click to collapse
Flashed ZNH2KAS254 (same issue) also the newer fix ZNH2KAS2X1 (same issue )
Did the flashes but forgot to update it here ...the issue exist and never beeing fixed since CM12.1(or maybe earlier I'm not sure when this started but it was there since CM12.1 for sure)
P.S. In omni as in CyanogenMOD the charging experiance while turned off is even worse, in Cyanogen you don't have red led lit but the screen has a BIG battery, the CM, omni etc etc have a tiny tiny small white battery that reminds me of the year 2000 ...also no red led lit(same issue)
I'm using the cm nightlies and it lights up fine when charging while powered off. No percent number but the light is there. I stopped using the official software months ago because of bluetooth spotify audio stuttering which also no one cared about to fix. Nightlies are running fine but without gimmicks like slow shutter and raw (but slow motion is there)
evronetwork said:
So in the past I've mention that OnePlus One had issues if you try to charge it while it's turned off, the charging led(red) isn't on and I went here to tell my story:
https://forum.cyanogenmod.org/topic/114705-oneplus-one-charge-when-turned-off-charging-and-led/
Well not much people got interested in this so I still persuit this and open a case in the "famous" jira cyanogenmod reporting system and open this thread:
https://jira.cyanogenmod.org/browse/BACON-4187
So even since CM12.1 this issue exist and maybe from previous android versions, now I saw today that it's been solved, so I update my phone to the latest official "cm-13.1-ZNH2KAS1KN" and check it out ...guess what, no resolve so I tried to post on JIRA Cyanogenmod that the ZNH2KAS1KN still has the issue
When I figure out that the "RESOLVED" from "Pat Erley" which was assigned to fix it was to make my account "inactive" - great resolve [emoji14]
P.S. When I open this issue one of the cyanogen guys told me "I can't add votes and I'm not going to advertise the issue (and I would rather you not either). The activity would have been me assigning the issue"
He didn't want to "advertise" the issue, why? ...why he wanted this to be quiet? (this is visible from the jira cyanogenmod link I've mention in the second link
P.S.2 Share this to as many OnePlus One users possible, cyanogenmod jira is useless(and they mute you if they don't like what you are saying)
Click to expand...
Click to collapse
Try latest nightly, charging led is Woking in or while powered off.
Sent from my A0001 using Tapatalk
Abhinav_Rakesh said:
Try latest nightly, charging led is Woking in or while powered off.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Currently on COS13.1.1 ..and issue the report based on COS not CM(had CM in the past but there still was this issue while the phone was turned off - didn't check CM for a while as I'm on COS since COS13)
It's unacceptable the official rom for this device to have a broken rom, charging led works if the phone is on but that's a different matter
evronetwork said:
Currently on COS13.1.1 ..and issue the report based on COS not CM(had CM in the past but there still was this issue while the phone was turned off - didn't check CM for a while as I'm on COS since COS13)
It's unacceptable the official rom for this device to have a broken rom, charging led works if the phone is on but that's a different matter
Click to expand...
Click to collapse
You do realize CM Nightlies are months ahead development wise than COS. It'll get to official COS after some months so just have to be patient. I checked and it works on latest nightlies as the other user mentioned
Renosh said:
You do realize CM Nightlies are months ahead development wise than COS. It'll get to official COS after some months so just have to be patient. I checked and it works on latest nightlies as the other user mentioned
Click to expand...
Click to collapse
You do realise that I reported this since COS12 right?
Do you understand, your problems been fixed, just flash a damn nightly. No one at Cyanogen is gonna apologize to you or say you were wronged. Get over it and flash a damn nightly.
xdiable said:
Do you understand, your problems been fixed, just flash a damn nightly. No one at Cyanogen is gonna apologize to you or say you were wronged. Get over it and flash a damn nightly.
Click to expand...
Click to collapse
Problem not fix with the OFFICIAL rom, I really don't care about nightlies or made by papajohn ReMixERrSZzz or whoever, currently I don't feel like playing with roms, I do have a simple root in my COS(look what I wrote, CyanogenOS aka Cyanogen)
P.S. Try to be more polite, everyone can talk badly without even trying - It's unacceptable the official rom to have such a huge bug since COS12(or maybe even before that while I've mention it)
evronetwork said:
Problem not fix with the OFFICIAL rom, I really don't care about nightlies or made by papajohn ReMixERrSZzz or whoever, currently I don't feel like playing with roms, I do have a simple root in my COS(look what I wrote, CyanogenOS aka Cyanogen)
P.S. Try to be more polite, everyone can talk badly without even trying - It's unacceptable the official rom to have such a huge bug since COS12(or maybe even before that while I've mention it)
Click to expand...
Click to collapse
Official Nightlies are the same code made by the same guys who make the stock OS, COS just has some closed source apps and comes bundled with gapps. Can't wait to see your dumb comments when you realize you'll never get Nougat COS update but people using CM Nightlies will
evronetwork said:
Problem not fix with the OFFICIAL rom, I really don't care about nightlies or made by papajohn ReMixERrSZzz or whoever, currently I don't feel like playing with roms, I do have a simple root in my COS(look what I wrote, CyanogenOS aka Cyanogen)
P.S. Try to be more polite, everyone can talk badly without even trying - It's unacceptable the official rom to have such a huge bug since COS12(or maybe even before that while I've mention it)
Click to expand...
Click to collapse
Why don't u just charge with the device turned on? Airplane mode on and plug in charger there you go. I wouldn't be happy to wait for a boot every morning.
I have searched all the custom rom threads but can't find the answer to one major question before I pull the trigger on installing a custom rom (usually lineage or RR for me, but I'm open to any stable rom). How is the call quality? I'm so frustrated with the stock ROM lack of updates and the low volume in phone calls. If it makes any difference I'm on a US at&t sim. Any and all opinions are welcome.
The stock call quality issues are thought to be caused by a bug in nnoise cancellation system app. Maybe try search XDA for a newer version of the stock ROM, I heard they fixed the microphone issue in some update ( not sure if the US version of Moto g5+, tho).
Thanks for the information and reply, but that's my point. I'm on the retus stock ROM with no updates at all, even the tiny security patch update that some are getting. I'm on the January patch still along with the call quality issue. I just want to know if any custom roms have the same issue of low volume or if the call quality is exceptional. Thanks again.
I am using Resurrection and call quality Is excellent.
I never would have known there was a problem with low call volume if you hadn't mentioned it. Running Pure Nexus. It gets uncomfortably loud if I turn it up more than halfway.
Thank you. On my 137_33 build, if that makes any difference, the in call volume is so low I have to turn on the speaker and then adjust the volume so it's not too loud. The volume for music, notifications, etc is plenty loud. I know of numerous threads over on the Lenovo forums that complain of it but so far it had not been fixed and there is no cure but a system update, as far as I know. I just want to know if a custom rom is the cure or not.
Matej101 said:
The stock call quality issues are thought to be caused by a bug in nnoise cancellation system app. Maybe try search XDA for a newer version of the stock ROM, I heard they fixed the microphone issue in some update ( not sure if the US version of Moto g5+, tho).
Click to expand...
Click to collapse
Can you please confirm which months' update was it fixed? I am on March update of the Debloated Stock ROM and still have this issue
Shonilchi said:
Can you please confirm which months' update was it fixed? I am on March update of the Debloated Stock ROM and still have this issue
Click to expand...
Click to collapse
I do not know when it was released, but I am quite sure it is the -67 update.
Shonilchi said:
Can you please confirm which months' update was it fixed? I am on March update of the Debloated Stock ROM and still have this issue
Click to expand...
Click to collapse
I updated with the latest version *35-5 for my US 1687 and the call volume is still low. There is a new update *43(?) for Verizon that might fix it but I am waiting on that one. The *67 update is for retin users so I don't know if that fixes anything. Sorry I don't have more info.