Related
When ever I receive a phone call and answer it, the caller can't hear me for the first couple seconds although I can hear them. I tried it with multiple phones. But when I tried it with stock ROM, they can hear me as soon as I answer it. Does any one have this issue?
Yup. I believe is a known issue with cm7. Not a biggie for me though. I just wait a second before talking.
Sent from my HTC Glacier using XDA App
Yeah the call lag is not a biggie , but is some issue with the Incall Dialer .
What happens is that i need to dial in to Meetin place server which hosts conference calls , and you need to log in after dialing the number to connect to their server , when ever i try to log in using the in-call dialer , the screen displays the correct nos being typed, but the server gets incorrect info from it . Dont face this issue with the Stock roms or the Darky roms or any other custom rom . Faced this problem on CM7 and MIUI.
for eg - if i tyr to log in by typin 440056 the server says it received 44440656 some thing like that , any idea how to fix this , or mayb replace the phone.apk to a stock one on CM7??
A new problem has started for me and and a Google search has shown some other people have also mentioned in but no solutions have come up.
Since iv started using any Android 2. 3. 7 roms around 1once a day to once a couple of days answering a call causes phone app to freeze and the phone speaker makes a constant buzz sound that eventually stops. After the phone signal and 3g returns all is well but trying to make a call result in a full phone freeze wich needs a battery pull. Best thing I do now after this crash is reboot normally.
Also good thing is the call is not answered as far as the carrier is concerned so I can still follow up on the call with voicemail.
I'm considering I have to go back to an older nexushd2 Rom or some sense Rom wich usually has Android 2. 3. 5
Anyone know a way to fix it? Maybe flash an Android 2. 3. 6 apk or a modded libaudio ?
I had that happening to my old phone.... freezing, buzzing, battery pull.
It started happening after I overclocked the phone to 1.5ghz . And then just kept happening even when i stopped overclocking. The phone would be hot on the bottom. And sometimes wouldnt boot till it cooled off. All i can say is hopefully you have insurance bc if its anything like with mine it'll be happening more and more often with time. After 3 months of it, it was happening a couple times a day , till i got a replacement.
Visentinel said:
A new problem has started for me and and a Google search has shown some other people have also mentioned in but no solutions have come up.
Since iv started using any Android 2. 3. 7 roms around 1once a day to once a couple of days answering a call causes phone app to freeze and the phone speaker makes a constant buzz sound that eventually stops. After the phone signal and 3g returns all is well but trying to make a call result in a full phone freeze wich needs a battery pull. Best thing I do now after this crash is reboot normally.
Also good thing is the call is not answered as far as the carrier is concerned so I can still follow up on the call with voicemail.
I'm considering I have to go back to an older nexushd2 Rom or some sense Rom wich usually has Android 2. 3. 5
Anyone know a way to fix it? Maybe flash an Android 2. 3. 6 apk or a modded libaudio ?
Click to expand...
Click to collapse
This is related to the No Sound bug alright. What other apps do you have - SIP/ Viber/ any other VoIP? And do you use BT? There were a few post in the No Sound thread and Tytung's kernel thread few days back about what libaudio.so works fine for what kind of a usage.
Android 2.3.7 is just a coincidence, me thinks
ph03n!x said:
This is related to the No Sound bug alright. What other apps do you have - SIP/ Viber/ any other VoIP? And do you use BT? There were a few post in the No Sound thread and Tytung's kernel thread few days back about what libaudio.so works fine for what kind of a usage.
Android 2.3.7 is just a coincidence, me thinks
Click to expand...
Click to collapse
None of the above and I don't use Bluetooth.
Guess it ain't a coincidence. I wouldn't of posted if I thought it was part of the no sound bug.
Sent from my Nexus One using Tapatalk
I had a similar issue some time ago: for me the problem was the cpu/governor settings and i fix it with an appropriate SetCPU profile. Using another rom though.
Try to set an "in call" profile as the phone won'to go under 400 Mhz (roughly) and see if it happen again.
mi too
i using miu rom, HD2 NDT GINGER and recovery 3.0.2.4 with this i don have this problem. with any sense rom I have that problem
Sorry my bad english
Hi,
in the last days with my S3 on every call I had which went for more than 1 minute the other person suddenly couldn't hear me anymore. Sometimes it happened after a minute, sometimes after 3 minutes, but in the last 4 calls it happened every time!
Reception came back after some seconds and from then on it was really bad, the other person had hard problems understanding me.
I searched around and found this thread of GNex owners having the same problem:
http://androidforums.com/samsung-galaxy-nexus/472451-vzw-other-person-cant-hear-me.html
Then I found it in the Issues DB too
http://code.google.com/p/android/issues/detail?id=24019
Do you guys know more? it is really bad, since this is my business phone so nearly every call is an important one and it really bugs me out.
Anyone having same problems?
I hope someone can help me out.
Yes I have the exact problem. It's driving me nuts and I've tried different roms and kernels.
Sent from my GT-I9300
Have you tried to DISable the noise canceling feature?
No but I will try it and report back.
By the way I'm on stock LF6 4.0.4 in Germany (with o2 as my carrier. Unbranded. )
Is the noise canceletion buggy?
Sent from my GT-I9300 using xda app-developers app
I've read that some kernels cause issues like this.
Also, in UK, in Birmingham on Orange, I have been having issues like this, and it usually occurs when the Signal Switches over from Orange to T-Mobile, mid call, and once onto T-Mobile signal, the call breaks up or goes quiet.
Maybe an issue switching from 2G to 3G or back mid call also?
BobFL said:
Have you tried to DISable the noise canceling feature?
Click to expand...
Click to collapse
Will try also. The only reason I haven't got rid of this phone is it mostly happens on o2 calls, I am on giffgaff which is run by o2, The op is o2! Hmmm
Sent from my GT-I9300 using xda app-developers app
just yesterday I again had the issue....and my noice cancelling was off...so this is not causing it....
I'm bumping this in hope someone has a cure.
The new rom LFB is not yet published for Germany but for UK. Perhaps it makes a difference? Can somebody in UK with LFB who previously had the issue please check?
Same problem, no solution
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
the-0ne said:
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Which ROM are you using right now?
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Try this for a fix
goto settings
sound
Toggle on then off or off then on the screen lock sounds then try again :good:
the-0ne said:
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Hey,
just so you know. I am on CM9 and I have kind of the same issue. Sometimes audio is unidirectional, both ways actually, unable to recreate it so far. What always seems to work is my bluetooth headset. Switiching between the two of them makes me lose audio entirely. I have tried many things, even rebooting the phone Sometimes it helps, sometimes it doesn't. I'm guessing it has something to do with BT.
I am NOT facing the issue with losing audio in the middle of the call when the display goes to sleep. The display goes to sleep because of the ligth sensor, btw. - not because the system is idling The display is not needed once the phone realizes it's attached to your ear (lights off).
It's driving me nuts
BUT: CM9 is amazing so far. It's fast, it's open, everything works just fine. Except for the phone as a phone of course
change modem
Oomahey said:
Which ROM are you using right now?
Click to expand...
Click to collapse
Using Stock right now. OTA updates till Jun 26th.
badaeng said:
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Click to expand...
Click to collapse
Mine's currently DDLF3
winwiz said:
Toggle on then off or off then off the screen lock sounds then try again
Click to expand...
Click to collapse
I've just tried this, will report back. How do you think lock sounds affect the mic, though?
avetny said:
change modem
Click to expand...
Click to collapse
Does CM9 come with an integrated modem switcher? I don't like messing around with "packages" too much. The more you mod everything, the less stuff has got to do with each other and it is more likely to run into trouble, because as a developer you can't really consider every side effect
So if this is actually about the modem (which I doubt, because the connection is just fine, it's just the audio output and input that is kind of broken) - what modem would I use with CM9? Can I just flash a random one over the current one?
Appreciate the advice.
Andreas
I notice that as soon as I take the phone away from my ear and the screen lights up I can again be heard... Wonder if there's a problem with the light off sensor affecting the mics too... It ALWAYS goes away when I remove the phone from my ear and the light sensor allows the backlight to come on again...
Might be a crazy thought but the evidence does seem to support this. I haven't turned off the light sensor in settings yet, if I even can, but was going to try next call...
I updated to BLG8 and I will see tomorrow if it happens again. Today I already had one call which lasted 11 minutes without interruptions. I will report as soon as I got more calls to test.
I had the same prob...
I just reflashed the official firmware frm the service centre.
Sent from my GT-I9300 using xda app-developers app
Same problem here. Tried several roms, kernels and modems. Only one working for me is Checkrom v3 with xxlbf... but here also after a while some calls it reappears... I reflash modem and I am set for the next couple calls... then again
Ps: i am from Romania on Vodafone
Sent from my GT-I9300 using xda premium
I'm the OP and I now didnt had the problem for 2 months with the last stock ICS build.
It seems to be resolved.
I'm now on JB since today (XXDLIH) and will report if it comes back.
Hi everyone,
I bought my nexus 4 about a year ago, and very recently I decided to give Cyanogenmod a try. I must say this was the first custom ROM I flashed on my device, and I'm quite fond of it. I also flashed a modified version of the latest franco.kernel for CM (http://forum.xda-developers.com/showpost.php?p=53707610&postcount=459)
The thing is that I noticed that my phone doesn't vibrate when it's supposed to. In fact, it doesn't vibrate at all; no matter what I try, it just doesn't. For the record, it had been working flawlessly until a few days ago.
So far I've tried:
- Disabling/Enabling vibration in keyboard, notifications and calls
- Rebooting my device several times
- Updating to 20140723 nightly (I was previously on M8)
- Disabling quiet hours
I've been doing some reading, and some old threads advise to perform a factory reset, but it's kind of a hassle for me to re-sync all the photos and stuff. So, is there anything I should try before I do a factory reset? Should I try and flash a different kernel/go back to stock kernel?
Thanks
It's most likely a hardware issue. I'd backup the phone and then flash the factory image. If it still doesn't vibrate it's a hardware issue. It doesn't cost much to replace the vibrator. Do it yourself or find a local cell repair shop.
Sent from my Nexus 5 using XDA Free mobile app
I would rather change the kernel first and see if there is any issues.
I flashed the latest CM nightly, which also changes the kernel to CM stock. This time you can hear the little buzz when you turn on the phone, but that's pretty much all the vibration I get. Phone calls and haptic feedback still don't work. At least, I know it's not a hardware issue.
ant_cc said:
I flashed the latest CM nightly, which also changes the kernel to CM stock. This time you can hear the little buzz when you turn on the phone, but that's pretty much all the vibration I get. Phone calls and haptic feedback still don't work. At least, I know it's not a hardware issue.
Click to expand...
Click to collapse
I still think it's hardware. Roms can change the force it vibrates at. But if it's still low the vibrator is bad.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I still think it's hardware. Roms can change the force it vibrates at. But if it's still low the vibrator is bad.
Click to expand...
Click to collapse
Maybe I wasn't very clear; the vibration force is OK, but the thing it that it only vibrates on startup, it doesn't buzz in incoming calls or any of that. So that's why I think the vibrator isn't broken
If I were you, I'd wait until tomorrow or later and download the next nightly. The first CyanogenMod 12 nightly's texting and phone are broken.
Sent from my SM-G900P using XDA Free mobile app
ethomas94 said:
If I were you, I'd wait until tomorrow or later and download the next nightly. The first CyanogenMod 12 nightly's texting and phone are broken.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the heads up!
Sent from my SM-G900P using XDA Free mobile app
Is anybody else having trouble with the cyanogenmod 12 nightlies for kltespr? They released the 2nd nightly a few hours ago and the calling and texting is still broken for me, but the network still works. Hmm... If I download albinoman's Alpha release, everything works just fine, but official nightlies are broken for me. Strange.
ethomas94 said:
Is anybody else having trouble with the cyanogenmod 12 nightlies for kltespr? They released the 2nd nightly a few hours ago and the calling and texting is still broken for me, but the network still works. Hmm... If I download albinoman's Alpha release, everything works just fine, but official nightlies are broken for me. Strange.
Click to expand...
Click to collapse
Downloading now, I'll post my results after flash.
Texting and calling is working, but looks like Bluetooth is broken. It works after a reboot, but is very choppy.
Definitely not working. 2 fresh installs. Phone will ring with a different tone than normal but there is no option to answer it. When the other end hangs up, the phone keeps ringing until you reboot it.
Appears inbound texting works but the send button in the stock mms app can not be pressed. Did not bother with testing 3rd party apps.
Have not seen any commits in the changelog which may fix this, so yeah I'd definitely hold off for another day or two before heading to nightlies.
GGTheGooch said:
Texting and calling is working, but looks like Bluetooth is broken. It works after a reboot, but is very choppy.
Click to expand...
Click to collapse
Hmm, that's very strange.
magoo5289 said:
Definitely not working. 2 fresh installs. Phone will ring with a different tone than normal but there is no option to answer it. When the other end hangs up, the phone keeps ringing until you reboot it.
Appears inbound texting works but the send button in the stock mms app can not be pressed. Did not bother with testing 3rd party apps.
Have not seen any commits in the changelog which may fix this, so yeah I'd definitely hold off for another day or two before heading to nightlies.
Click to expand...
Click to collapse
This is the exact problem that I have. I can type text, but I can't press the send button. The phone acts weird and won't actually hang up when I press the hangup button. So some people have the issue and others don't. At least it's not just me.
Sent from my SM-G900P using XDA Free mobile app
Here is a new issue. I tried to connect to my Bluetooth car stereo and it errored out, but my phone started making a ringing noise. No matter what I did, or which service I stopped, it kept ringing. Reboot did not fix the issue, but a power down and power back up worked. Also, regarding the SMS issue. Same issue with the stock app, but I use Textra and it works perfectly.
I've heard that updating the recovery might fix some rom issues, so I updated to the newest TWRP. And the same problem persists. So it's not the recovery, unfortunately. I'm back to using KT TWRP 2.8.0
Sent from my SM-G900P using XDA Free mobile app
ethomas94 said:
Hmm, that's very strange.
This is the exact problem that I have. I can type text, but I can't press the send button. The phone acts weird and won't actually hang up when I press the hangup button. So some people have the issue and others don't. At least it's not just me.
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
I had the same problem with messaging. I had to download Google messenger to send texts. Calling was not working for me. I could see when my brother was calling via LTE would turn off, after he hung up it switched back to LTE. I also noticed that it wasn't recognizing the sim card in the phone. Would this cause the problem possibly? I'll post pictures.
Picture one shows that sim card isn't being recognized.
Picture two shows the LTE is switched to off when he calls.
Picture three shows that I do have LTE. (even tho it is crap signal atm I took screen shot)
Forgot to add flashed using TWRP 2.8.3 (whatever latest version is)
That's very interesting. Unfortunately, I don't know how to fix this. I'll just wait until the next nightly.
Sent from my SM-G900P using XDA Free mobile app
I looked up the changelog for tonight's upcoming nightly and it includes a few network and telephony fixes (about 4). Let's hope this is the one!
Sent from my SM-G900P using XDA Free mobile app
I'm currently using the third build of CyanogenMod 12 official nighties for kltespr and the calling/messaging problem persists. It also appears that I have lost root for some reason. That isn't a big deal, but the calling and texting issues are kinda weird. Do they just not know about it I wonder?
Sent from my SM-G900P using XDA Free mobile app
ethomas94 said:
I'm currently using the third build of CyanogenMod 12 official nighties for kltespr and the calling/messaging problem persists. It also appears that I have lost root for some reason. That isn't a big deal, but the calling and texting issues are kinda weird. Do they just not know about it I wonder?
Sent from my SM-G900P using XDA Free mobile app
Click to expand...
Click to collapse
Don't know about the phone and messaging but for root you might have to enable it in developer options. I had to do that then it was fine but I'm on a different build.
After a few mins, my external SD card disappears.
I've tried the official CM12 kltespr builds from 9, 10 & 11th.
Not even a root file explorer can see it. Have to reboot to fix,
Anyone else get this?
Hello , I have these problems I can not take pictures with flash activad ,
upgrade in today's problems with incoming calls qualms , I have no problems with messages . but the time is changed
I am on the latest build and using Textra and Hangouts Dialer, SMS/MMS and phone calls work perfectly. GPS works well, but I have not yet attempted Bluetooth. Calls with the stock dialer work, but the phone call does not hang up.
Just verified Bluetooth is still broken.
biship said:
After a few mins, my external SD card disappears.
I've tried the official CM12 kltespr builds from 9, 10 & 11th.
Not even a root file explorer can see it. Have to reboot to fix,
Anyone else get this?
Click to expand...
Click to collapse
I've actually never heard of this. This is new. The only things I can guess about it are it being bad install, of the cache/dalvik cache wasn't cleared. I might try wiping everything (even system; it's in advanced wipe in TWRP) and reflashing it.
telekata said:
Hello , I have these problems I can not take pictures with flash activad ,
upgrade in today's problems with incoming calls qualms , I have no problems with messages . but the time is changed
Click to expand...
Click to collapse
I had that too. I took off the option "automatically find time" or whatever it's called. I just found the timezone manually and it was fine.
GGTheGooch said:
I am on the latest build and using Textra and Hangouts Dialer, SMS/MMS and phone calls work perfectly. GPS works well, but I have not yet attempted Bluetooth. Calls with the stock dialer work, but the phone call does not hang up.
Click to expand...
Click to collapse
I have this problem too. I reinstalled Touchwiz and will try again later when I know Cyanogenmod has fixed the issues.