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:
There seems to be a dead spot on the touchscreen near the top. It's there on the stock ROM and on custom roms (both AOSP and ROMs based on LG's UI). Do you guys have the same issue?
http://i.imgur.com/4fKjQmG.jpg
Tried that on quick memo. I dont have it luckily.
Sent from my LG-D802 using xda premium
Tried it also. No problem for me too.
Sent from my LG-D802 using Tapatalk
My first one developed that after some time, same place too. Went to verizon, showed them that, and they replaced it with a "certified like-new" which thankfully seems to be new as far as i could tell.
UberMario said:
There seems to be a dead spot on the touchscreen near the top. It's there on the stock ROM and on custom roms (both AOSP and ROMs based on LG's UI). Do you guys have the same issue?
http://i.imgur.com/4fKjQmG.jpg
Click to expand...
Click to collapse
Saw it already reported here before. But I do not have it.
It's been reported several times here, in 99% of the time an update fixed that.
Which version do you have?
robogo1982 said:
It's been reported several times here, in 99% of the time an update fixed that.
Which version do you have?
Click to expand...
Click to collapse
I have the LG-D801 aka T-Mobile US version. The software version on it is D80110C_00. I used the LG flashing tool and flashed a .kdz file named "T-Mobile USA D80110C_00.kdz" since I bought it from craigslist and wanted it back to 100% stock (guy sold it for $80 since he rooted it and then did the OTA which caused him to go into that recovery boot loop issue and only way to fix it was to flash that .kdz file)
I'm not rooted and I am not using a custom recovery. I guess I'll do the OTA update the phone was bugging me to do.
EDIT; Installed the latest OTA. The issue is still there but it did decrease the dead zone. The biggest problem is that I can't press "install" for apps in the play store since the button is right in the dead zone.
Getting the same problem here on my device, suddenly. I updated to the new Kit Kat update (I'm on Sprint) but didn't seem to make a difference. How annoying this suddenly happened and my phone was not dropped or damaged or anything. My other friend with a G2 had the issue and it went away on its own over time somehow. i'm noticing the bar where I have trouble is aligned exactly with the power button on the back, so I wonder if that has something to do with it, in the hardware.
Hi I have the same problem too, affects where the install open button area on Play Store near the top right. I am running CloudyPro 2.1.
Did you manage to fix this problem?
randomvector said:
Hi I have the same problem too, affects where the install open button area on Play Store near the top right. I am running CloudyPro 2.1.
Did you manage to fix this problem?
Click to expand...
Click to collapse
This is very weird, same thing happened to me today around noon, phone was fine all morning, then dead zone in same area, wth is this, is At&t or LG doing something ota that we do not know about.
edit: just wanted to add, I am on the D800
I'm don't think so as I'm on a custom rom. I've heard from some on xda the update fixes it but I've used the stock KitKat Rom and no luck there. I'm now using cloudy flex 2.2 still the dead zone is there.
Sent from my Nexus 4 using Tapatalk
Same issue here too. Stock Verizon G2 on Kitkat. Can't click on install button when in play store. Turned on the 'show touch' in developer mode and it doesn't recognize the install button when on an individual app in the play store, it shows as touch above or below it. It also skips the button when i run my finger across the screen.
coreygator said:
Same issue here too. Stock Verizon G2 on Kitkat. Can't click on install button when in play store. Turned on the 'show touch' in developer mode and it doesn't recognize the install button when on an individual app in the play store, it shows as touch above or below it. It also skips the button when i run my finger across the screen.
Click to expand...
Click to collapse
Funny how this happened to me right after the ota as well...
Dead zone in the same spot ..
And well in order to fix it( the install button atleast) is to change the DPI to 330
I called lg and they gave me an authorization to send it in for repair.
Call and see what they tell u guys
This happened to me this week as well, unfortunately in Canada none of the carriers will replace my device for me, LG says its user damage and are gonna charge me 125 dollars to fix it. I'm gonna see what the local repair shop says and hopefully theyll just fix it for me. It seems like this is an increasingly common issue, it's a shame that LG don't recognize that we didn't damage our phones, they sold us defective units. I'm very unhappy with LG's customer service, we should raise awareness of this and hopefully LG will come up with a solution for us
Yep. VS980 Stock Kit kat rooted with TWRP 2.7.0.0
Same exact issue. Same exact spot. Can't hit install on the play store. Haven't tried taking it to Verizon yet. I bought my phone through Target though I hope Verizon will replace it if it is in fact a hardware issue. I'm not gonna try and take it in until after I try a couple different ROMS to make sure it is a hardware issue.
I am on D800 was on CloudyFlex when it happened so it has nothing to do with OTA exactly, I returned to fully stock At&t 4.2.2 and it was still there. I am getting a replacement under warranty. Something weird is definitely happening if so many have seen this issue. It is almost like a timer going off in phone coding and bam that part of screen is deactivated. Whatever it is, this will be my last LG phone. Never had an issue with my iphone or galaxy s2 skyrocket.
Same problem here, VS980. It started happening right after I tried the newest build of CloudyStock with knock on support. I've been browsing through multiple CloudyROM threads and I'm seeing identical problems, (including the exact area of the dead spot, around where the install button is on the Play Store). I can't post in any of them because a. I don't have enough posts, b. Cloudy in his FAQ states that the VS980 is only for testing. I've tried flashing different AOSP and Stock roms including the latest PA and XDABBEB builds and the problem crosses over after full wipes. Has anyone figured out a way to fix this yet other than returning the phone for another?
To be clear: This phone has no damage to it whatsoever. No scratches anywhere including the screen, etc. I'm worried about how Verizon will take a warranty seeing as there's an "UNROOTED" flag in the bootloader.
Has anyone tried to update touch firmware?
Sent from my LG-D803 using XDA Premium 4 mobile app
jester12345 said:
Has anyone tried to update touch firmware?
Click to expand...
Click to collapse
I've read some people do it to no avail, but I'd like some confirmation on that. The service menu still hasn't been discovered on the VS980 from what I've read. It's not the same code with a different model number at the end like the D802. For example, Every other model of the G2 is 3845#*XXX#, but the Sprint model is 5689#*980#. 3845#*980# for the VS980 doesn't work.
Dang. Now im worried to update.
Sent from my LG-D803 using XDA Premium 4 mobile app
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]
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.