Database Info

Verizon CM10 Nightlies

Installed the most recent nightly Jellybean for Verizon. Seems stable but I notice what seems to be degraded sound quality on phone calls. Anyone else having that issue?
Can someone more experienced recommend a better (or preferred build)?
Thanks,

Stormer1981 said:
Installed the most recent nightly Jellybean for Verizon. Seems stable but I notice what seems to be degraded sound quality on phone calls. Anyone else having that issue?
Can someone more experienced recommend a better (or preferred build)?
Thanks,
Click to expand...
Click to collapse
You can't expect nightly builds to be stable- they will and do have issues with various things.
The vast majority, if not every single AOSP ROM for the SGS3 uses all of (or a good chunk) of CyanogenMod's code, which is why you see so many of the same bugs between builds that are rarely fixed until someone submits to CyanogenMod's Gerrit.
I can't comment on your specific issue, just posting some food for thought.

A lot of people have posted about echoes or low volume on the CM10 builds. I don't make many phone calls so I don't know if this affects every phone running CM10. But I'm sure it does to various extents. They will work it out in the coming weeks as they work toward a stable build.
Sent from my SCH-I535 using Tapatalk 2

the echo seems to be gone in the 8/31 build
use this thread to ask questions about it
http://forum.xda-developers.com/showthread.php?t=1840414&page=140

Preferred Build
Is there a stable build other than the nightlies? If so where would I find it?

Stormer1981 said:
Is there a stable build other than the nightlies? If so where would I find it?
Click to expand...
Click to collapse
I'd check the development forum or the nightly thread.
Sent from my Galaxy S III

ripken204 said:
the echo seems to be gone in the 8/31 build
use this thread to ask questions about it
http://forum.xda-developers.com/showthread.php?t=1840414&page=140
Click to expand...
Click to collapse
Agreed
Sent from my SCH-I535 using Tapatalk 2

No echo here. I just flashed to the 9/1/2012 nightly from stock.
Did you try playing with the call settings? I have noise suppression enabled and voice privacy disabled.

I actually have a similar problem (can't post on official thread yet).
I have trouble with my headset volume.
If i plug it in DURING a call, I cant hear anything and can't do anything to adjust the volume.
If i plug it in BEFORE a call, it's fine.
Any clues as to whats going on or any suggestions on how to fix it?

Paranoid android Sept 2nd build seems to work nice, i think it works better than the CM10 builds even though its based off it. You can also mess around with tablet mode!

Let's get the echo fixed and the roaming issue fixed and the forum will flock to these roms. Till then I would beware.
Sent from my SCH-I535 using xda premium

I just flashed CM10 09/04 nightly and I am still getting the 3 second In call delay, I am still getting echo on speaker phone and I am still getting my voice navigation only say " in a half mile" Nothing else, No one seems to even mention this in the official CM10 forms. and No its not a half mile from my house to the end of my street , its like less than 1000 ft. Everything else seems to work good but the delay and the echo are very annoying so I am going back to the build that worked best for me cm10 08/22

Defragger51 said:
I just flashed CM10 09/04 nightly and I am still getting the 3 second In call delay, I am still getting echo on speaker phone and I am still getting my voice navigation only say " in a half mile" Nothing else, No one seems to even mention this in the official CM10 forms. and No its not a half mile from my house to the end of my street , its like less than 1000 ft. Everything else seems to work good but the delay and the echo are very annoying so I am going back to the build that worked best for me cm10 08/22
Click to expand...
Click to collapse
Same results here for 904. The other forum mentions that an unofficial build has the incoming call delay fixed, though, so I'm hoping the fix shows up when the official 905 ROM comes out.

Headphones with mic not working
I'm running the 9/2 build and when I plug the stock headphones with mic into the phone I cannot talk or hear phone calls through it. No issue with music. Screen flickers when using keyboard (Swiftkey). Volume control in call doesn't seem to work. There is also a 5 second delay when I answer a call to when I can hear the other person or they can hear me. Same delay with speaker phone.
At least the damn echo is gone though :good:

Can anyone confirm whether or not the dock audio is working on recent CM10 builds? I've tried searching the thread and have done everything short of just flashing it to see.
Thanks for your replies!

The dock audio was still not working for me on the CM10 from 9/5.

landtuna said:
The dock audio was still not working for me on the CM10 from 9/5.
Click to expand...
Click to collapse
You are correct. Just tried it myself. This is the main thing holding me back from CM10. I'm going to attempt to add it in myself. We'll see what happens.

9/5 build seems to be very solid. No data issues or call issues. Cannot comment o no the dock audio though. Make sure you aren't doing dirty flashes, there have been tons of issues with dirty flashing.
Sent from my SCH-I535 using xda app-developers app

This is why I switched to ParanoidAndroid. It is Jellybean and far more stable than the current CM10. If you want Jellybean right now~ I highly recommend PA. If you really like CM, still, try PA~ it will help you wait for the official CM10 release. I actually don't see a need to go CM10 tbh. PA is wonderful.

Krystalmyth said:
This is why I switched to ParanoidAndroid. It is Jellybean and far more stable than the current CM10. If you want Jellybean right now~ I highly recommend PA. If you really like CM, still, try PA~ it will help you wait for the official CM10 release. I actually don't see a need to go CM10 tbh. PA is wonderful.
Click to expand...
Click to collapse
I'm going to give PA a try... I am still having serious issues with CM10, hope they will be fixed with PA

Phone Dials but no Sound

I have an occasional issue where my phone is dialing a number but I cannot hear the ringing, and once it connects there is no sound either way.
Sometimes if I reboot the phone will work again - but other times I need to reboot several times before it seems to start working again.
Obviously this is a huge problem as I use this phone for business...any suggestions on how I can diagnose this?

lirong said:
I have an occasional issue where my phone is dialing a number but I cannot hear the ringing, and once it connects there is no sound either way.
Sometimes if I reboot the phone will work again - but other times I need to reboot several times before it seems to start working again.
Obviously this is a huge problem as I use this phone for business...any suggestions on how I can diagnose this?
Click to expand...
Click to collapse
Which version of which build are you using? There was a well-documented (and very annoying) bug in CM for a while that affected in-call audio. This has been addressed in more recent builds and seems to have been eliminated. A little more information will make it easier to help you.

mrfeuss said:
Which version of which build are you using? There was a well-documented (and very annoying) bug in CM for a while that affected in-call audio. This has been addressed in more recent builds and seems to have been eliminated. A little more information will make it easier to help you.
Click to expand...
Click to collapse
Thanks...sorry for that ommission.
I am using vincom's Superlite CM10.

lirong said:
Thanks...sorry for that ommission.
I am using vincom's Superlite CM10.
Click to expand...
Click to collapse
I've had this problem with all kinds of roms (stock, custom, aosp, etc). Sometimes it happened more often sometimes less. I've even had this happen to me on three different phones (SE x8, i9100 and i727r). Most often it happens with CM7, CM9 and CM10. But it did and does also happen with official roms. I'm on the Rogers JB now and it still happens, but relatively rare. This has been discussed before and with no result. Apparantly this is a common android issue..
Same issue talked about here:
http://forum.xda-developers.com/showthread.php?t=2164921
http://forum.xda-developers.com/showthread.php?t=2168656

I had such problem too and hadn't found the reason.
Anyway, after I flashed UXUMA7 radio, I haven't experienced it any more.

I just had this issue today. I've been running cm 10.1 m snapshot since Friday using the phone no problems. Last hour of work my wife calls no audio during call. I then wiped the cache partition and devik cache nothing. Came home did a full wipe and now its fine. I don't know don't know what happened. I think I may find a different ROM if this happens again
Sent from my Nexus 7 using xda app-developers app

livefree79 said:
I just had this issue today. I've been running cm 10.1 m snapshot since Friday using the phone no problems. Last hour of work my wife calls no audio during call. I then wiped the cache partition and devik cache nothing. Came home did a full wipe and now its fine. I don't know don't know what happened. I think I may find a different ROM if this happens again
Click to expand...
Click to collapse
The last m release that I know of (I haven't been on straight CM for a few weeks) was released before a commit that fixed the no in-call audio bug. I'd read through the thread and look to see which nightly has been the most stable, if I were you. If you do decide to switch to another ROM I can personally vouch for Sons of Android or Slim Bean (onlychevys has an unofficial build out).

I have since switched to Embryo and, so far (hope I didnt just jinx myself) I have not experienced this issue.

lirong said:
I have since switched to Embryo and, so far (hope I didnt just jinx myself) I have not experienced this issue.
Click to expand...
Click to collapse
Embryo is tw, doesn't have the issue
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

[Q] Screen becomes unresponsive upon calls, help?

So to start, my phone is rooted and the bootloader is unlocked. I should also have the latest modem flashed. The problem is that the screen will freeze upon some calls, not all of them, and prevents me from doing anything. I can still hear everything that's coming through but the screen itself is just unresponsive. At that point, I usually just pull the battery and reboot and make the call over again. It hasn't happened to me immediately after a battery pull yet.
This problem has occurred to me on multiple roms. I initially noticed it on LiquidSmooth's 3/16/13 stable build and so I re-flashed it making sure to do a clean install. It kept on happening so I kept switching roms and am now on Carbon Rom and it hadn't given me any problems until just now (been on Carbon for over a week). All of my rom installs are done with clean flashes so I really don't know what's going on at this point.
Any help would be absolutely fantastic!

it's a known issue on AOSP roms

Try using the latest Official CM10.1 nightly. Best to do reset, clean install. That issue has pretty much been squashed on the latest builds.
Sent using Tapatalk

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

I had no idea about it being a problem on aosp ROMs since it hasn't occurred for me on them until recently. But I'll definitely cm10.1 a try! Thanks!
Sent from my SCH-I535 using xda app-developers app

kupnooduls said:
I had no idea about it being a problem on aosp ROMs since it hasn't occurred for me on them until recently. But I'll definitely cm10.1 a try! Thanks!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I am currently using Paranoid Android which is based off cyanogenmod, and I get the same thing. Phone freezes mid call. I was having general freezing problems across the board until I installed PA, I kept thinking is was my launchers, etc, but I am bare bones right now and it still does it periodically, and have once had it do it directly after a battery pull.
When mine does it, the call drops.

Two things..
First, I have been having the same phone freeze issues as everyone else, tried different roms, the dummy file fix, all kinds of different things going through this forum. I wanted to do everything I could possibly do before posting about it.
I am using Paranoid Android. I noticed the cyanogenmod version listed in the phone info is [email protected]#1 Tues March 19
Is this just a PA version number or actually the kernel number? What if I was to flash the newest stable kernel to my PA?
ALSO
I noticed when my phone does its freeze up thing, the battery has been at 53-57%. It does not seem to do it any lower or higher battery percentage. Is it possible that its actually a problem with the battery or the battery percentage programming??? It just seemed odd that it always seemed to be around the same % when it happened.
Any thoughts????

[Q] PA 3.60 Phone Calls Not Working

I downloaded the new PA 3.60 6/11 build from notta yesterday with KT747 Kernel and RErick universal setup. After using for a while, without attempting to call, I was more than happy. At work today I called my girlfriend and in the middle of our conversation the call dropped. Ever since then whenever I try to make a call I get a "com.android.phone has stopped" message or it will connect, close phone screen but keep call in status bar, show that same message, then drop the call. Sometimes it says "Mobile network not found" after trying to call then will reload my bars after. Can't receive calls either but my network shows I have bars and every IMEI & numbers alike are there. Restored nandroid and calls worked.
Thought it might be kernel combo so tried to wipe everything and reinstall but problem persisted. Any ideas on how to fix?
Thanks in advance!

Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium

andrewk7750 said:
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I've flashed the 6/10 gapps both times I flashed the ROM, unfortunately. Maybe bad download? I don't know at this point.
Its RErick's from Team Kernelizers setup for the KT747 kernel. Can find him on the TK Mod thread. Great battery life supposedly but didn't get to try it for too long since calls didn't work.

I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.

antiseen said:
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
Click to expand...
Click to collapse
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app

kenbrownstone said:
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Since I've been having so much trouble with any rom I haven't used a custom kernel since my thunderbolt days. I run whatever kernel the rom comes packaged with.
But like I said, it's probably my phone. It has defective bluetooth that I didn't figure out until well after I purchased the phone. It's got constant loud crackling and popping on stock (ironically, non existent on aosp roms). I doubt that's related but just illustrates the weird differences between phones.

Had the same problem less than an hour ago when i really needed to make a phonecall. Had to restore to my backup i made before flashing PA. Hell of a time for it to stop working.
Sent from my SCH-I535 using xda app-developers app

Well after first believing it was just my phone, after reading these comments as well as the PA thread I've come to the assumption that its something with the ROM and how it behaves with the phone app. Hopefully the details will get resolved soon cause I was really enjoying the new PA. Until then, sticking with hyperdrive.
Thanks guys.

had this problem since upgrading to the 6/11 build.
i could make calls out as long as i didnt press the ok button to dismiss the process stopped message.
i could not receive calls hwoever. it does ring like it should, but it does not allow me to answer.
using latest gapps package.

I've had this problem on both 6/12 and 6/14, using the 6/10 gapps.
Any chance anyone has come up with some way to resolve this?

for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.

ddurandSGS3 said:
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
Click to expand...
Click to collapse
Good suggestion. Really liked PACman for a while, but eventually my call got dropped and I ran into the exact same issue from that point on. At this point I've just decided to go with a TW based rom. With hyperdrive you can still have pie and download Floating Notifications app that is practically the same thing as halo but also has themes available too.
Until that bug can be fixed, going to stick with Hyperdrive. Sweet rom anyway.

Cyanogenmod/Carbon Rom call problems on Galaxy S3 I9300

Hi all,
As im new here i couldn’t post this on the development posts so have had to drop this here for now. I know there have been other related threads like this but my situation seems to be more unique and more annoying :crying:
After rooting my galaxy s3 I have had numerous call problems on both cyanogenmod and Carbon Roms. It started with cyanogenmod 9.1 stable and experienced problems where there was no sound at either end of the call, sometimes I could hear the other person speaking but they couldnt hear me. Other times when i answered the phone I would hear them speak but there voice would be distorted, sounding more like a robot. Theses problem would usually be fixed by either me or them calling back.
Thinking this had been fixed on a cyanogenmod nightly I tried them... however this seemed to make no difference, even on the newer versions.
Fed up I moved onto carbon Rom (despite this being cyanogenmod based) and have had the same problems with even the very latest build thou the distorted sound just became more common, even after a whole month of use.
I have now moved onto the liquid smooth Rom in hope i wont have the same problem... if this fails then its back to the old stock Rom
Has anyone else had the same problem or heard of this before??? Any feedback would be appreciated =)
Many thanks

Distorted sound on liquid smooth to.... =(

Yes! I have been having the same problem I think. I have looked everywhere and haven't been able to find a solution let alone another person describing the problem. About one in every 6 or 7 calls has a bubbly distorted sound but the person on the other end can hear me OK. I'm running CM 10.1 on a GS3 i747m. Did you find a solution or find anyone else with a similar problem?

alex2207 said:
Hi all,
As im new here i couldn’t post this on the development posts so have had to drop this here for now. I know there have been other related threads like this but my situation seems to be more unique and more annoying :crying:
After rooting my galaxy s3 I have had numerous call problems on both cyanogenmod and Carbon Roms. It started with cyanogenmod 9.1 stable and experienced problems where there was no sound at either end of the call, sometimes I could hear the other person speaking but they couldnt hear me. Other times when i answered the phone I would hear them speak but there voice would be distorted, sounding more like a robot. Theses problem would usually be fixed by either me or them calling back.
Thinking this had been fixed on a cyanogenmod nightly I tried them... however this seemed to make no difference, even on the newer versions.
Fed up I moved onto carbon Rom (despite this being cyanogenmod based) and have had the same problems with even the very latest build thou the distorted sound just became more common, even after a whole month of use.
I have now moved onto the liquid smooth Rom in hope i wont have the same problem... if this fails then its back to the old stock Rom
Has anyone else had the same problem or heard of this before??? Any feedback would be appreciated =)
Many thanks
Click to expand...
Click to collapse
If this is any help and I know its late, but carbon ROM is based on many cyanogenmod parts (the MMS app, many features and I'm sure the phone app). If you are having problems going to on cyanogenmod the problem is likely to ocurr in carbon, AOKP or Paranoid android are less likely to have the same problems though.

You have to go back to stock rom .. eliminate binnary status.
and then take it to a Samsung service center.
I think the galaxy s3 is no damage on the hardware you
sorry i use translate.google

I can't agree. I have the same problem and need to reboot each time. I've flashed about 10 different ROMS. This problem only exists on cyanogenmod. I have no clue, but I've been looking for an answer for some time now.