Related
Well everyone, since my KANG thread in the development section has become a discussion thread since official CM nightlies started again, I've decided to redirect the discussion to here. I'm going to ask the thread in the development section to be closed, so it can stop taking up space there...instead we'll take up space here! Lol. But anyways I want this to basically be a continuation of the old thread...you can talk about your G2X questions, comments, problems, etc. here. This will be especially geared toward CM-related problems, but all G2X-related topics are welcome here I hope that everyone will continue to help each other out, and of course I'll monitor the thread to help as much as I can and research things if necessary. Enjoy!
This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.
Kalm_Traveler said:
This isn't necessarily CM-related but I guess it is in a way. I have been trying out EB's build 1 of ICS and honestly for the most part it works great already. The only big glaring issue (that actually made me revert back to Gingerbread today) was the incoming call problem I've seen reported elsewhere that when you try to answer a call, your ringtone restarts and it doesn't appear to actually pick up.
As for the G2X in general, I'm a firm believer that most common issues have been strictly software-based, which makes the resources we have here on XDA something like miracle workers if you think about it.
Click to expand...
Click to collapse
Ya I couldn't stand that answer my phone wait for it to ring after I select answer was surely a big annoying thing that and wifi calling issues but other then that VERY usable can't wait for newer builds and development on 4.0.3..
I'm on his GB CM7 build and love it great great battery life only at 90% with descent use today.
Sent from my LG-P999 using xda premium
Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??
j.d.r said:
Quick question, if I am already running Arcee's ICS ROM would I need to do a full wipe and loose the way I have my phone configured or can I just wipe cache/dalvik cache and flash on top of Arcee's??
Click to expand...
Click to collapse
As it is always said, it is best to do a full wipe. You never know what issues may stick behind or get caused by not doing a full wipe, but give it a shot and report back and hopefully you don't have issues.
Sent from my LG-P999 using xda premium
Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk
I believe Hellfire sandwich is the most updated and closest to everything working build. But there's lots coming down the pipeline thanks to our AMAZING DEVS!!!
Sent from my LG-P999 using xda premium
What's the best source for finding out the status of official Cyanogen 9 work on the G2X? I am not interested in kangs or spin-offs.
joeyxl said:
Ok, so after reading the last comments in the CM thread, arcees rom is not been updated in awhile. What have people found the most stable, working ics ROM is atm? I'm using sk3, but will upgrade if there is better.
(btw, People get jealous of my now ICS powered phone )
Thanks!
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
I haven't tried any of the other ICS roms, but been using HFS since the initial release. Obviously it's not perfect, but I've been running it everyday and don't have any major complaints
CM Nightly 226/Unnamed & Kernels
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
I've used Faux123's UV/OC kernels, but seem to have lost my copy of his v0.4.3 (long term CM7.1.0.1 support). So, the newest v0.4.8 and T15 or ELF Trinity's won't work with mine. I know chip's vary, but mine seems to not like even the ELF Trinity kernel (which has worked for a few peeps running CM7.1.0.1).
Anyway, the breakdown of my ramblings are:
1. Anyone try CM Nightly 226/Unnamed?
2. Anyone happen to have a copy of Faux123's v0.4.3 kernel (CM Battery Version, not the DS driver) lying around? Or a compatible Trinity (preferred, actually)?
Eh, I know #2 is more wishful thinking. I'm mostly interested in anyone's experience with Nightly 226/Unnamed.
Ah, good to be back on XDA and CM, at that. I rolled on MIUI for way too long. Nice GUI & the customization was awesome, but man is that sucker a memory hog! Not to mention the random reboots and screen freezes... I should have never left my good ol' CM. Hindsight and all...
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
long story short, i have a wiped g2x. power button is a ***** to turn on to the point that my finger tips are sore from trying to get it to boot into recovery since last night. i can only seem to get 2 different screens trying to do this:
a) the lg boot animation which promtly freezes as the phone has been wiped & i probably haven't held the volume down button
b) the s/w screen used for flashing a recovery, etc
the phone is not mine but trying to help someone out. is there a timing to releasing the buttons? seems that when it goes to the s/w screen, lg appears for only about a second and then straight to that one. any help would be appreciated.
edit: posted it here only because i'd been following the old thread which led me to this one. i was trying to update to the latest while this happened. i started a similar thread in q&a so if it doesn't belong i''ll remove it, thanks
I've been in a loop like this before. Make sure you have done a battery pull. I think the key is not to hold the volume down button so long, and then be patient for recovery to load, it takes longer than expected in this situation.
Good luck.
Nightly #225
my_former_self said:
Recently transitioned back to CM from MIUI. Anyone try out the newest 226 (unnamed) Nightly yet? I'm still rocking the CM7.1.0.1 Stable, but for kernel flashing purposes, I'm trying to decide on a nightly.
Click to expand...
Click to collapse
Ah, you want to talk to me! I just went from CM7.1.0.1 Stable to #225. More stable, much faster than CM7 Stable, #225 really should be CM7.2 Stable.
#226 seems to have a bug with the lockscreen PIN. Go get #225 and don't look back.
azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.
dmwOtis said:
I've seen in other threads that the app getril fixes the low mic problem. This app matches the radio layer to the baseband.
Click to expand...
Click to collapse
Lots have stated the same thing doesn't work for most some say it did. Worth a try if you haven't yet, no go for me
Sent from my LG-P999 using xda premium
Where is this getril app?
Sent from my LG-P999 using XDA
azyan said:
The only issue that I ran into with cm7/cm9 is the low microphone. I know this has been brought up in the past, but has been ignored as well. Some users claimed that it only happen to certain phone, but I'm almost certain that the issue lies within the rom. I do hope someone can shed some lights on this, cause i do miss using CM7.
Click to expand...
Click to collapse
I agree, this is by far the most annoying bug and the only "show stopper" I can think of on CM7. I do not think it's a 'phone-by-phone' thing, because if I flash to stock or Weapon G2X, my mic volume is fine. It's only on CM/CM-based ROMs, such as MIUI. I can't count the number of times where people have told me to "speak up" until I'm practically yelling into my phone. I think there's a bug with noise cancellation that causes it to be quieter than it should be.
Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA
imoumni said:
Learn somethg new everyday just downloaded it... I had v21c when it expected v21e any idea why i didn't have the latest?
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
GetRIL went the other way for my phone (Wind Canada P999), recommending v11h. Any notes re: the different builds?
Hi,
Firstly, want to thank the dev for this great rom. I recently switched back from ICS because I couldn't take the lag/wanted a fully functioning operating system.
The main problem I' having with this rom is that when I'm listening to music/audio files they'll stop for no apparent reason. The only thing I can think of is that maybe they're stopping when I go in and out of service. When I either unlock and press play or switch apps and press play they start again with not problems. I've found this to happen in multiple audio player (Poweramp and BeyondPod being the two main ones I use).
Any help would be greatly appreciated as this is incredibly frustrating.
Thanks very much for your hard work.
btw: the reason I didn't post this in the related dev forum is that I don't as yet have enough posts to do so...so no flaming please).
Nobody is gonna flame you for posting a question on the questions forum.. (unless you didn't search first)
I've had this happen to me as well with different ROM's. I don't believe its ROM specific. My problems were related to some of my notification settings. I also switched from the standard player to UberMusic. It's old but does the job well.
New2my8125 said:
Nobody is gonna flame you for posting a question on the questions forum.. (unless you didn't search first)
I've had this happen to me as well with different ROM's. I don't believe its ROM specific. My problems were related to some of my notification settings. I also switched from the standard player to UberMusic. It's old but does the job well.
Click to expand...
Click to collapse
Can't be too careful when it comes to flames.
I thought it might be my notification settings but I've tried pretty much every permutation of those. Can't really bring myself to switch from PowerAmp (paid) and BeyondPod(free) is the best podcast player I've found to date...I might try reinstalling the rom, maybe I didn't wait long enough before using it?
sellless said:
Can't be too careful when it comes to flames.
I thought it might be my notification settings but I've tried pretty much every permutation of those. Can't really bring myself to switch from PowerAmp (paid) and BeyondPod(free) is the best podcast player I've found to date...I might try reinstalling the rom, maybe I didn't wait long enough before using it?
Click to expand...
Click to collapse
Does the problem exist if you were to use Google Music? If it does, then it's most definitely a problem with the ROM. Try a re-install and if that doesn't clear it up, you might want try out a different ROM to see if it's the ROM or not.
New2my8125 said:
Does the problem exist if you were to use Google Music? If it does, then it's most definitely a problem with the ROM. Try a re-install and if that doesn't clear it up, you might want try out a different ROM to see if it's the ROM or not.
Click to expand...
Click to collapse
Sadly, or happily as I love PowerAmp, it does occur with Google Music too. Never had this problem on eaglseblood gb (which I mainly used before trying a few ICS roms) but switched as their GB rom is no longer maintained. Will try re-flashing. Hopefully that helps.
Thanks for your suggestions.
sellless said:
Sadly, or happily as I love PowerAmp, it does occur with Google Music too. Never had this problem on eaglseblood gb (which I mainly used before trying a few ICS roms) but switched as their GB rom is no longer maintained. Will try re-flashing. Hopefully that helps.
Thanks for your suggestions.
Click to expand...
Click to collapse
Yeah, i just recently discovered this issue too, and it kind of bugs me.
Still haven't found a way around this. Tried reflashing the rom which didn't help. Just tried flashing faux's 49b1 to see if that helps. The dalvik cache is being very slowly rebuilt. The newer kernel (the one included in hellfire 2.3) has a MUCH faster loading time (at least upon first load). Will post if this helps with the sound issue.
sellless said:
Still haven't found a way around this. Tried reflashing the rom which didn't help. Just tried flashing faux's 49b1 to see if that helps. The dalvik cache is being very slowly rebuilt. The newer kernel (the one included in hellfire 2.3) has a MUCH faster loading time (at least upon first load). Will post if this helps with the sound issue.
Click to expand...
Click to collapse
Well. I'm still having this problem. I've tried multiple kernels, multiple roms and even completely formatted my phone (all partition including boot sector). No luck. Truly aggravating because aside from this issue, I love this rom. Very smooth/fast and stable. Not sure I can live with this audio problem though as it's incredibly frustrating.
If anyone else has encountered this problem and found a solution, please post. Thanks,
I just dl the old music player apk here see if it helps. https://play.google.com/store/apps/details?id=com.jrtstudio.music
Also does it occur both when using headphones and not? I had issue with a set of headphones with a break in the wire, which would make the phone appear as though the headset was unplugged and plugged back in, which stopped playback constantly.
Let me know if this helps any.
Sent from my LG-P999 using xda app-developers app
Thanks for replying.
I'd wondered if that might be the reason too. I know it gains with different headphones as I've tried four different pairs. I'll have you try it without any and see. I did try disabling the setting for stop playback upon removal of headphones with no success. I'll try without headphones in and see. I'll have to flash the Rom again as I've been trying a few others out.
Sent from my LG-P999 using xda app-developers app
sellless said:
Thanks for replying.
I'd wondered if that might be the reason too. I know it gains with different headphones as I've tried four different pairs. I'll have you try it without any and see. I did try disabling the setting for stop playback upon removal of headphones with no success. I'll try without headphones in and see. I'll have to flash the Rom again as I've been trying a few others out.
Sent from my LG-P999 using xda app-developers app
Click to expand...
Click to collapse
Did you get it figured out?
justjackyl said:
Did you get it figured out?
Click to expand...
Click to collapse
Sadly, no. I've tried playing music without headphones attached and the same problem occurs. Random stops. I go into whichever application (it happens in everyone single one I've tried) was playing an audio file and it starts up right where it left off when I press play.
It's worse now actually in that it occurs with whatever all roms. So now I'm left wondering if there's a micro fracture in the headphone sensor that only started acting up at the exact time I put Hellfire Phoenix 2.3 on my phone or if, somehow, it corrupted some base setting on the phone that even reformatting it can't get rid of.
Terribly aggravating. Debating taking it in for service but I need to find a Wind factory rom before I can do so. Think I saw one in the forums a few months ago. hopefully the link's still active.
Loathe/love technology.
justjackyl said:
Did you get it figured out?
Click to expand...
Click to collapse
I've reinstalled my phone's stock rom (WIND Mobile).
This seems to have sorted out the issue. I'm going to try reinstalling Hellsfire Phoenix in a few hours if it doesn't happen again (I'm playing music nwo and will continue for a couple hours to make sure).
I'm now wondering if maybe this was some sort of error caused by downgrading from an ICS build (hadn't occured to me previously but that's when I started having this issue and it didn't matter which GB rom I tried after that)? Hopefully this will be the end of these problems and I can enjoy Hellsfire Phoenix as it was great aside from that issue.
I'll post in a couple days if all goes well....or if it doesn't.
sellless said:
I've reinstalled my phone's stock rom (WIND Mobile).
This seems to have sorted out the issue. I'm going to try reinstalling Hellsfire Phoenix in a few hours if it doesn't happen again (I'm playing music nwo and will continue for a couple hours to make sure).
I'm now wondering if maybe this was some sort of error caused by downgrading from an ICS build (hadn't occured to me previously but that's when I started having this issue and it didn't matter which GB rom I tried after that)? Hopefully this will be the end of these problems and I can enjoy Hellsfire Phoenix as it was great aside from that issue.
I'll post in a couple days if all goes well....or if it doesn't.
Click to expand...
Click to collapse
That's so odd. I'm curious to see what happens if you go from stock to HFP v2.3.
Sent from G2x running BuROM v0.2 (root; mod stock 2.3.4) w/ faux's GB kernel 014b2-ext4.
justjackyl said:
That's so odd. I'm curious to see what happens if you go from stock to HFP v2.3.
Sent from G2x running BuROM v0.2 (root; mod stock 2.3.4) w/ faux's GB kernel 014b2-ext4.
Click to expand...
Click to collapse
Well, sad to say that I still had that problem after trying HFP 2.3 again. So I went back to stock. This time it happened on stock too so I have to assume it's a hardware problem. I guess I just lucked out (well, poor luck in this case) that it went for four hours Friday without halting playback.
Better take it in for warranty service while it's still covered.
At least it seems unlikely that any rom/kernel combo was to blame now.
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
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
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.