Ok I'm not a complete newb but I can't figure this out and its been driving me nuts for over a week now...
SGH-1337M (Rogers)
Up until last week I'd been running the nightly builds of CyanogenMod and loving it, the phone was fast had lots of functionality then I did a nightly upgrade and my phone stopped working. Incoming calls would ring but when I picked up the call I couldn't hear the caller and they couldn't hear me. After much frustration I ended up flashing back to stock. This fixed the problem but the phone was useless as far as I was concerned for everything but making phone calls. It was laggy, I couldn't listen to music (it was staticy) and just generally full of all of the extraneous crud that Rogers seemed to think I should have on my phone. (I honestly couldn't suggest the phone to anyone who was going to run it as a stock device if this was how it came out of the box!)
Now On Sunday I decided to try again and after setting everything back to defaults I reloaded Cyanogen and at first it seemed that things were working properly... until last night. Again I got a call and when I answered it there was no audio.
I can't figure it out, I'm running the correct radio now after flashing to stock (I337MVLUAMG1) but I just can't seem to get it to work and stay working. Besides Cyanogen I'm only running two other "root" apps Fantastic audio installer and AdAway.
Any suggestions would be great, I just can't go back to stock on this phone...
Any ideas?
I think I have the problem figured out...
Seems like it was a combination of a bad build of CM and the "Fantastic Audio Installer"
Beware of compatibility issues with apps like this...
Related
I'm having major call issues. Everybody keeps saying that my voice is changing or something over the phone. And there is a lot of static. How do I fix this? I am running Cyanogen Mod 6 RC2
My voice went through some changes you describe when I was younger, don't worry, it will pass.
Seriously though, I've noticed the quality Change once or twice in the calls, not sure if people on the other end picked up any changes or not.
Lol good one..yeah but I ended up installing cyanogen again thru recovery and it seemed to have fixed it. Hopefully I don't run into the same problem.
Hey guys... Yesterday I upgraded the baseband to 2.15 from the original stock 1.0 I was running one of the CM nightly builds and also did the unrevoked forever root method to install it. After I did that I installed CM6 RC3 and later I realized I cannot hear out of the headset while making a call or receiving. So I then installed Skyraider and I still get the same thing. I can turn on speaker phone or connect to bluetooth and it works fine... but nothing through the handset.
Today I reverted to an old backup to see if that would help/work and still nothing. I guess my questions are can I fix this? Or do I have to downgrade to 1.0 baseband again and is that even possible?
Any help would be great, just a little annoying having to talk on speaker phone.
You have to revert to 1.0 radio. This happened to a few of us, it seems fairly isolated my replacement will be in tomorrow so I will know soon just how isolated.
I see.... well that sucks...
What did you say to get a replacement sent to you? Because obviously saying that I updated the baseband probably won't go over too smoothly.
I've been having this problem where I can't hear anyone on the handset. When the person answers the call, I can hear maybe two or three seconds worth, but it's completely garbled and broken up, as though I'm in a bad reception area, and then it goes silent. But I can hear them perfectly fine if I switch to speakerphone or use the handsfree headset! The people on the other side can hear me too.
It all started a few days ago. I had just installed the Phoenix kernel for MIUI. It was working fine for a while, and then all of a sudden this started happening. At first I thought maybe it was something to do with the Phoenix kernel, so I just reflashed MIUI. No factory reset yet. Just wanted the original kernel back. Still the same. So then I thought maybe I'll try a different ROM altogether and went to CM7. Same problem. Finally, I put in a stock recovery and went to stock 407. Same problem there as well!! DSC v1.0, same problem!! Now I'm back to CM7, and yes, same problem! Not sure what else I can try. I seriously hope it's not some hardware issue. Any suggestions as to what to try next would be appreciated!
Hi all, I really hope you can help me with this...
I can't stand TouchWiz, so I very quickly replaced it with CM 10.1, which sort of works. However, I find it very annoying that it lacks stuff like PIE (yes I know I have hardware buttons, but I still would like a proper menu, and LTM is just not quite there). I therefore tried Paranoid Android (had no phone, camera worked very badly) and then I discovered ReVolt! I must say ReVolt is a marvellous rom - but with one, massive caveat: I loose sound in the phone app, and indeed the phone seems to go rather bonkers (fails to actually call etc). I did see this somewhat on CM too (failed to place calls - timed out and hung up), but with ReVolt it's consistent.
This is what I did: I reloaded my nandroid backup of stock, checked that the phone worked (it did). I then flashed June 15th (or 14th - it doesn't quite agree) nightly of ReVolt. No sound in phone (but it could call). No ringer sound (on outgoing), no sound either way during the calls. Call in does ring, and it can be answered, but there is just no sound. No errors shown, no nothing. Putting it on speaker, adding headphones - nothing works.
I reloaded the stock rom, then installed latest CM10.1 nightly, and phone works as expected.
Both run on the same baseband (I9505XXUAME2), and they are both based on CM. Any ideas (I'm not allowed to post in the ReVolt thread - I don't have enough posts yet it seems).
Any help is greatly appreciated.
/R
I recently installed CM 10.1 on a Defy+.
For some reason - if I call someone (or they call me) - they cannot hear me, and I cannot hear them. Even if I put on the loudspeaker I still cannot hear them.
Phone is working normal apart from that, speaker seems to work fine so not convinced it is a hardware issue.
Only happened after flashing the ROM. It *was* working for some time. Any ideas what could have caused this? From reading about CM on other phones, people recommend flashing different kernels. Any ideas which kernel to flash?
Thanks.
Ok looks like this is an issue with BlueTooth being on. I turned it off and it worked fine.
Seems to be an issue with all CM 10.x that I was unaware of. I flashed this ROM on my wifes Defy+ to improve the speed and reliabilty of her phone. Needless to say she is not happy.
Maybe I should have flashed 7.2??
sterankin said:
Ok looks like this is an issue with BlueTooth being on. I turned it off and it worked fine.
Seems to be an issue with all CM 10.x that I was unaware of. I flashed this ROM on my wifes Defy+ to improve the speed and reliabilty of her phone. Needless to say she is not happy.
Maybe I should have flashed 7.2??
Click to expand...
Click to collapse
I guess 7.2 is good and stable enough for a non power user. That bug is known and it's not yet fixed.
Like @hotdog125 said, it's a known bug, and happens sometimes even when bluetooth is not used at all. I never use bluetooth and it happens to me quite often; rebooting your phone fixes the problem.