Okay, this is potentially a really stupid question...but here goes.
I'd installed CM7.1 on my Fascinate as soon as I got it (was running a Vibrant with CM7) and immediately started seeing the weird issues like:
-data connection disappearing
-"double ring"...ringer ringing away during a call, requiring an end and re-dial to have a clean conversation
-call volume being ear-piercingly loud
As a result, I've started ROM hopping. However, the ROMs I've tried all seem to have the same issues.
Not trying to flame anyone, or bag on any of the ROM authors/maintainers, but are all the Fascinate ROMs out there a copy/modification of the CM ROM? Or are these issues I'm seeing (as others are too) a common failing of anything other than the stock ROM that came on the phone?
im running cm7.1 and have none of those issues.
What modem do you have? The ringing you are experiencing is called the phantom ring. I thought it was a known issue in all mtd roms, but I haven't used one in awhile. I remember having the call volume the same way. You have to press vol down once.
Sent from my SCH-I500 using XDA App
droidstyle said:
im running cm7.1 and have none of those issues.
Click to expand...
Click to collapse
I was running pool party and loved it except the WiFi kept dropping. I need a reliable network connection. I would have continued using it if not for that. TSM resurrection has been my more stable second choice.
Sent from my SCH-I500 using xda premium
uzumaki82 said:
What modem do you have?
Click to expand...
Click to collapse
I flashed Evil Fascinate over the weekend and I'm running DL09.
However, this doesn't answer the deeper question as to if the issues I saw in CM7.1 are pervasive in the other ROMs for this phone, as I've already experienced them in Evil, and it's been three days in use.
I'm not sure if I should simply accept the issues and find a ROM that I like, or if there's a different ROM out there that doesn't have the CM7.1 issues.
I am having the issues with the volume but, pressing volume up or down works to clear that up. I have also gotten complaints of the other end having an echo. This is on all calls with multiple carriers from other people. Anyone having this issue as well and know how it can be resolved? It doesn't echo on my end. Just the person I am talking too. Also I am running modem Baseband EDO5. I was running EBO1 and still have the same issues with each. I have tried MIUI as well and still the same. I flashed to stock fascinate as if you were to get it from Verizon and all of that seemed to go away. When I flashed back to CM 7.1 all of these issues arose again.
thedoman said:
I was running pool party and loved it except the WiFi kept dropping. I need a reliable network connection. I would have continued using it if not for that. TSM resurrection has been my more stable second choice.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
my wifi never drops...sometimes I have to toggle it off/on after a reboot but thats it.
I have had that problem on all my android devices that I have had. Sometimes hardware just freezes up and you have to do a reboot. They are basically little computers anyway but, if you are constantly having to reboot to get something to work. It is more than likely a problem with the mod.
Related
Does it happen to you?
You are talking on a call (on your Froyo'ed Eris), and you feel your phone vibrate twice; you can't hear the other party, so you look at your screen, and sure enough, it says "call lost" (or similar). So you go to redial, but then after a few seconds, you realize: the other party is still on the line!
If you were using the speakerphone toggle, it will have been turned off.
I really don't yak on my phone much, so the fact that I've seen it a few times leads me to think it is pretty common.
My phone has been solid as a rock since Drop Day (Nov 6th), and I never experienced this on 1.5 or 2.1 stock, or any 2.1 dev ROMs, but I've seen it on both Tazz V6 and Kaos V29.
Has it happened to you?
bftb0
[SIZE=+1]Edit 2/15/2011 - A very likely fix for this problem has been identified. See this post:[/SIZE]
http://forum.xda-developers.com/showthread.php?t=956091
Edit 9/14/2010 - see diagnostic information in post #27
bftb0 said:
Does it happen to you?
You are talking on a call (on your Froyo'ed Eris), and you feel your phone vibrate twice; you can't hear the other party, so you look at your screen, and sure enough, it says "call lost" (or similar). So you go to redial, but then after a few seconds, you realize: the other party is still on the line!
If you were using the speakerphone toggle, it will have been turned off.
I really don't yak on my phone much, so the fact that I've seen it a few times leads me to think it is pretty common.
My phone has been solid as a rock since Drop Day (Nov 6th), and I never experienced this on 1.5 or 2.1 stock, or any 2.1 dev ROMs, but I've seen it on both Tazz V6 and Kaos V29.
Has it happened to you?
bftb0
Click to expand...
Click to collapse
I believe with Froyo it auto reconnects dropped calls, this happens all the time to me and I actually like it.
the vibrations are in your settings
one buzz = call connected
two buzzs = call dropped
jrozga said:
I believe with Froyo it auto reconnects dropped calls, this happens all the time to me and I actually like it.
the vibrations are in your settings
one buzz = call connected
two buzzs = call dropped
Click to expand...
Click to collapse
I poked around a little and couldn't find any mention of it as an official feature of 2.2; do you have a link?
Does it seem to happen to you about as frequently as you were getting plain ole' dropped calls on 2.1 or 1.5, or more frequently?
bftb0
Never had a call dropped =\ can't say, sorry.
this happens to me all the time
im on tazz v8 froyo
I get one buzz then the lost call sound but after like one or two seconds i can hear the person on the other side
It happens frequent
carycooke said:
this happens to me all the time
im on tazz v8 froyo
I get one buzz then the lost call sound but after like one or two seconds i can hear the person on the other side
It happens frequent
Click to expand...
Click to collapse
Does it happen more frequently than the rate at which you used to get dropped calls when you were on 2.1 (or 1.5) ROMs?
I don't know whether it is a bug or not - if jrozga is correct, then it should happen about as often as plain-ole dropped calls occurred with 1.5 or 2.1 ROMs. (Or maybe to be fair, as often as dropped calls occur with stock 2.1 phones with the July 2010 OTA - they have the same radio as most rooters are using)
I still haven't found anything on line from "official" sources that mention that this is expected behavior in Android 2.2 phones. The last time it happened to me, I questioned the other party on the line, and they said "I heard one buzz for about half a second". (They were on a land-line, so it eliminates their end of the connection as the source of the trouble.)
That's a little bit bizarre if they heard the first of the two vibrations on my Eris - it means my Eris had decided that the call had terminated even though it had not. That alone inclines me to believe it is a bug, not a feature.
bftb0
I get it on about every call since installing 2.2
Sent from my FroyoEris using XDA App
I'm running celb 2.1 and today made a phone call in a poor signal area and still made it all the way thru without dropping or anything is it a radio problem per chance?
tburns said:
I get it on about every call since installing 2.2
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
That's exactly why I think it is a problem with the current batch of developer 2.2 (Froyo) ROMs.
As I said, I don't make that many calls, so I don't really know how often it happens - but given that it has happened to me a couple of times now (given the small amount of calling that I do), it makes me think it is not just a signal reception issue.
Which ROM and Radio firmware are you using BTW?
I've used kaos for about a month and been on celb for almost a week and have not had such an issue. I use my phone frequently for work, too. I have had the current radio from the july update since a week after it was available.
Sent from my ERIS using XDA App
Bump.
We now have 15 people on XDA (in the Eris forums) reporting the symptom:
bftb0: Tazz V6; Kaos Froyo V29 [Froyo]
jrozga: (unknown) [Froyo]
carycooke: Tazz V8 [Froyo]
tburns: ??? [Froyo]
mcook1670: "All Froyo ROMs" [Froyo]
punkxdead: CELB [CyanogenMod]; CELB Froyo [Froyo]
Macrodroid: Kaos & Tazz [Froyo]
droiderisuser: ??? "2.1"
danwguy: CELB 2.7 cyamogenmod 5.0.8-DS firmware 2.1-update1 [CyanogenMod]
pablocasiano: WW4.6, KaosFroyo V29
crax0r: KaosFroyo V29
tjthebest: CELB 2.8-CM5.0.8
mistaj: CELB 2.8-CM5.0.8
npong: CELB 2.8-CM5.0.8
mflane: CELB 2.8-CM5.0.8
Some of them say "it happens all the time"
And 10 more people over in the AF Eris forum reporting the same oddity - on different Froyo/AOSP ROMs:
erisuser1: Tazz V6; Kaos Froyo V29 [Froyo]
snozzcumber: Kaos Froyo V?? [Froyo]
TJTHEBEST: CELB 2.9 [CyanogenMod]
MrBojenglz: Buufed v???
BlueDC2: CELB v?, Kaos V?
rick311:
BellaSkye: Kaos V32
Kaessa: Kaos V32
tpatnoe: Kaos V30
rc346: Kaos V34
funkyfender: "CM6"
john58543: KaosV30
So far, only one user has said "this also happened to me on a 2.1 ROM" - droiderisuser
[ Edit ]: At least two people have reported this on older radios, and and also on non-Froyo (but CyanogenMod ROMs)
If it happens to you, and you have the SDK set up on your PC, and it is convenient to do so, try to make a note of the time when it happens, and then when your call is complete, dump a "logcat" to your PC, and post up the log during that same minute here.
Code:
C:\blech> [B][COLOR=green]adb shell logcat > strange_call_reconnect.txt[/COLOR][/B]
[I](wait about 30 seconds and then hit ^C (Control-C) )[/I]
I've had it happen on all Froyo roms. I work for the FDOT so I'm on the highway 8 hours a day. I don't know if its the phone changing towers or what. I always have a good signal because the towers are next to the highway. Not sure what it is but its annoying
Sent from my ERIS using XDA App
Houston, we have a problem.
TJTHEBEST over on AF indicates he experienced the same problem using an older radio firmware on CELB
I have not found any evidence to support or deny jrozga's claim that this is a Froyo "feature", rather than a bug. I'll try to poke around a little and see if I can find anything further.
bftb0 said:
Houston, we have a problem.
TJTHEBEST over on AF indicates he experienced the same problem using an older radio firmware on CELB
I have not found any evidence to support or deny jrozga's claim that this is a Froyo "feature", rather than a bug. I'll try to poke around a little and see if I can find anything further.
Click to expand...
Click to collapse
I also had this problem with CELB with the 2.41.04.02.02 radio. I switched to CELB Froyo after it 'matured' (hoping to resolve it) and still had the issue. I have since switched to KaosFroyo v29 and the latest "July" radio. The issue is still present.
BTW Heres a quote from my post in the CELB Froyo thread awhile back:
punkxdead said:
I have had this problem with ErisLightningBolt and CELB Froyo, (and KaosFroyo when I tested it). I never had this issue in a Sense based ROM (PlainJane), only in the AOSP/Cyanogen based ROMs. I live in a city with great 3G coverage and never experience the issue while at home, however I travel alot for work. When driving through rural areas it happens to me all the time. My call "ends" screen goes away, phone beeps and vibrates (like when you end a call), audio drops out, 5 secs later, screen comes back, call resumes. The caller on the other end always assumes I had another call/call waiting beep, etc. I believe the phone is switching from 3G to 1x in the process causing this, but I can't be certain. I have been patiently searching/working to find a solution but to no avail. Just thought I'd post since I'm finally hearing of others with this issue.
Click to expand...
Click to collapse
Never happens to me, and I make phone calls about twice per day.
punkxdead,
Thank you for that detailed report. Very useful information
Turns out that TJTHEBEST from AndroidForums experienced the problem on 2.1 CELB, which is not Froyo - but I guess it is a CyanogenMod build. That further corroborates your experience.
So far, nobody has reported this in a Sense-based ROMs. I'm a little fuzzy on the genealogy of the kernels in the various roms, although I suppose the problem could also be occurring in "rild" or it's supporting libraries.
It's not a show stopper by any means, but it is annoying; it would be nice if we could figure out how to get it fixed, since it seems to appear in lots of different dev ROMs.
If you are able to do the 'logcat' thing to see if we can find some more info, please give it a try; I will do likewise.
bftb0
punkxdead said:
I also had this problem with CELB with the 2.41.04.02.02 radio. I switched to CELB Froyo after it 'matured' (hoping to resolve it) and still had the issue. I have since switched to KaosFroyo v29 and the latest "July" radio. The issue is still present.
BTW Heres a quote from my post in the CELB Froyo thread awhile back:
Click to expand...
Click to collapse
I can confirm the 3g to 1x theory. This has happened twice on my phone, several times on my wifes since,we loaded tazz v8. It also happens on kaos. Not on any of the 2.1 roms ive used. Each time, the phone,is,in the 1x data state. I've had it on speaker amd watched this happen each time. When 3g comes back, so does the,other caller. I think it may have something to do with network selection in froyo.
I have recently changed mine from automatic to home only... So far, no bug yet (only been a couple of days, though..).
Sent from my Froyo Eris using XDA App
Macrodroid said:
I can confirm the 3g to 1x theory. This has happened twice on my phone, several times on my wifes since,we loaded tazz v8. It also happens on kaos. Not on any of the 2.1 roms ive used. Each time, the phone,is,in the 1x data state. I've had it on speaker amd watched this happen each time. When 3g comes back, so does the,other caller. I think it may have something to do with network selection in froyo.
I have recently changed mine from automatic to home only... So far, no bug yet (only been a couple of days, though..).
Sent from my Froyo Eris using XDA App
Click to expand...
Click to collapse
Hmmm. Interesting. I think EVDO (3G) and CDMA Voice are mutually exclusive (simultaneously, anyway - a fundamental technical limitation of the way EVDO is implemented as an overlay in CDMA networks). I suppose it could be that if the ROM thinks that the voice call has ended, the "3G" icon appears right away. So it's not too surprising that you would see something changing in the display at the moment the call is "temporarily lost".
bftb0
bftb0 said:
Hmmm. Interesting. I think EVDO (3G) and CDMA Voice are mutually exclusive (simultaneously, anyway - a fundamental technical limitation of the way EVDO is implemented as an overlay in CDMA networks). I suppose it could be that if the ROM thinks that the voice call has ended, the "3G" icon appears right away. So it's not too surprising that you would see something changing in the display at the moment the call is "temporarily lost".
bftb0
Click to expand...
Click to collapse
I'm not really sure what the network option really would do. I do know that froyo isn't an eris os, so maybe it's something related to how it interacts with our phones... Either way, i'm waiting to see if the bug comes back on home only. Still love froyo, regardless!
Sent from my Froyo Eris using XDA App
Not sure if this helps but I have an Eris and pre Froyo when I was using Plain Jane I believe it was not sure precisely but It was a 2.1 rom for sure I had this happened to me quite frequently. So I would assume it is not just a 2.2 issue.
Is this happening for everyone? Does anyone know how to fix it?
I am running ZenDroid 2.1.1, but it also happened on the previous versions, and apparently users on other roms have similar problems...
I moved to a new house with terrible cell reception, and I really need this to work. Any help appreciated. Thanks!
Sent from my SGH-T959 using XDA App
I have the same issue
Got fed up with this issue today and saw your threads. I have multiple routers. I seem to really have bad echo for people who have Sprint. Anyway, I have tried various settings on my routers to no avail.
turn the volume down on your earpiece. This is what seems to be reported as the fix, on the numerous threads about the wifi calling "bug".
I don't use it but, I do read around these fora
Sent from my SGH-T959 using xda premium
I know this thread is a bit old, but I'm also having this problem. I'm currently running Bionix-V 1.3.1 Fishman Mod V3 (Bali kernel). I don't think I had the wifi calling echo problem when I was using the regular Bionix-V 1.3.1 with the regular froyo kernel... can't really remember now, though.
I have yet to try turning down the volume on the earpiece as previously suggested, but that doesn't seem like a "fix" to me, only a way to "cover up" the problem. Going throughout the day turning down/up my earpiece volume as I use/don't use wifi calling is silly. Call me crazy, but I like things to just work. That's one of the reasons I chose the Bionix ROM over others.
Finally got cm7.1 stable working consistently on my phone. Data hand off between 3g and wifi seems to be a standard problem around here and for the most part the answer seems to be just to deal with it.
It's been a few months since the stable was released, so I'm wondering if anyone has found a work around. Is there a tasker program or something in the nightlies that addresses this?
Also I've been getting frequent bootloops when cm crashes and forces reboot such as the constant vibration using navigation and switching between camera/camcorder. Eventually the whole thing crashes and bootloops forcing me to restore. Are these common as well?
On stable w/ glitch v13 oc 1.4Ghz -100mv EC09 Thanks
alphax_0 said:
Finally got cm7.1 stable working consistently on my phone. Data hand off between 3g and wifi seems to be a standard problem around here and for the most part the answer seems to be just to deal with it.
It's been a few months since the stable was released, so I'm wondering if anyone has found a work around. Is there a tasker program or something in the nightlies that addresses this?
Also I've been getting frequent bootloops when cm crashes and forces reboot such as the constant vibration using navigation and switching between camera/camcorder. Eventually the whole thing crashes and bootloops forcing me to restore. Are these common as well?
On stable w/ glitch v13 oc 1.4Ghz -100mv EC09 Thanks
Click to expand...
Click to collapse
no I'm not experiencing those issues. there is no fix for data hand off issue yet. just leave either data on or wifi, not both.
droidstyle said:
no I'm not experiencing those issues. there is no fix for data hand off issue yet. just leave either data on or wifi, not both.
Click to expand...
Click to collapse
I see a few commits on JT's githhub that say they semi fix it...also I haven't experienced the problem really at all aside from rebooting with wifi on since I came back to MTD Roms.
I see. It's just sometimes my 3g/wifi will be colored and still won't be receiving signal every so often even when I disable the other data method. Oh well
sendan said:
I see a few commits on JT's githhub that say they semi fix it...also I haven't experienced the problem really at all aside from rebooting with wifi on since I came back to MTD Roms.
Click to expand...
Click to collapse
same here...but quite a few report the same issue as op. I seen a post where chopper said to only leave one on or the other. just passing the info along.
Hmmm, it may have to do with the radio. I've seen a few people mention that the handoff is better with the eh03 radio; coincidentally that's what I've been using since I came back to MTD.
Sent from my SCH-I500 using xda premium
Hello gentlemen!
First of all, I want to thank neobuddy and everyone that he worked with on the ICS Passion ROM. I find it excellent and have been using it for the past week or so.
I do have a slight issue, though, and as I am not yet familiar with mobile development, I am not sure if the problem stems from my hardware or the software. I bought this Vibrant used, though in excellent condition. As soon as it arrived, I rooted it and installed ICS Passion on it. Therefore, I never actually used the stock software, and that is why I am unsure if this issue stems from the ROM or from the phone itself.
Anyway, my problem is that sometimes during a call, my voice will cut in and out very frequently. This occurs with various people and in various places, so it doesn't have anything to do with signal strength. I can hear the other person just fine. It also seems to only occur when I receive a call. Once I hang up and call the person back, they seem to be able to hear me just fine.
I suspect that this has something to do with one of the following:
1) Sound filtering and normalization. The way that the software handles the data that it receives from the microphone. If it was the microphone itself, I would expect this issue to be much more consistent.
2) Which network the phone uses during phone calls. I've gathered that H is for data transfer and 3G is for phone calls (for the most part). Is it possible that ICS Passion somehow fails to switch to the proper network when a call is received? This seems unlikely as I searched through the ICS Passion thread in the dev forum, but couldn't find an issue similar to mine.
Any insight would be appreciated, although I suppose if no one can help out I can just flash the stock and see if the problem persists. If it does, then I can only assume it's the phone.
Thanks!
try v 10 or v 10.6
Mute and then unmute your call. We've had this problem since cm7
Sent from my SGH-T959 using XDA App
bfranklin1986 said:
Mute and then unmute your call. We've had this problem since cm7
Click to expand...
Click to collapse
Sweet, good to know, thanks. Do you know of a more permanent solution?
LDKnight said:
try v 10 or v 10.6
Click to expand...
Click to collapse
I'm afraid to upgrade to v10 because some people have been experiencing issues with their phones rebooting several minutes into the call. I may try it anyway, though.
Do you know if your problem is with incoming calls only?? That's where the issue seems to be, that the mute/unmute fixes. I put 10 on about a week ago, and am loving it. Put 10.5 on yesterday, and 10.6 today, so they are working on it. I think 10.6 might have fixed it for me, so I'm so happy. Thought Bionix was going to be the end of the line, I tried a couple of gingerbread roms, and had issues!
ProfessorKazuki said:
Sweet, good to know, thanks. Do you know of a more permanent solution?
I'm afraid to upgrade to v10 because some people have been experiencing issues with their phones rebooting several minutes into the call. I may try it anyway, though.
Click to expand...
Click to collapse
Been on v10 for a week and have not had the reboot problem. I've heard 10.6 has some problems but yeah the mute/unmute bug isn't that bad you get used to it
Sent from my SGH-T959 using XDA App
kenrb said:
Do you know if your problem is with incoming calls only?? That's where the issue seems to be, that the mute/unmute fixes. I put 10 on about a week ago, and am loving it. Put 10.5 on yesterday, and 10.6 today, so they are working on it. I think 10.6 might have fixed it for me, so I'm so happy. Thought Bionix was going to be the end of the line, I tried a couple of gingerbread roms, and had issues!
Click to expand...
Click to collapse
That's what it seems like. I have not had a single "you sound like you're underwater" issue for outgoing calls.
Thanks for the responses, everyone. I'm glad to find out that the problem isn't with the phone because I can't afford to replace it for a while. I guess I'll just wait a bit and hope that these slight issues get resolved in a more stable iteration.
I posted a thread yesterday about how when i made a call the person on the other line couldn't hear me but i could hear them, when someone called me i could hear them but they couldn't hear me, i resigned myself to the fact that i would have to bring it in for repair as it was a hardware issue, flashed the 3 Ireland stock ROM, decided to try once more, made a test call and the person could hear me, got them to call me and i could hear them and vice versa so i put it down so maybe corruption in internal SD card or something.
I rooted again, flashed CheckRom and Franco kernel and set the phone up again as it was, called a friend earlier and he couldn't hear me, got him to call me and i could hear him but he couldn't hear me so im dumbstruck as to what the problem is here, i initially thought it was the microphone which was the problem but then after flashing the 3 Ireland stock ROM no problem, it was only after flashing CheckRom and Franco kernel (which i always use) the problem reappeared, so has anyone any ideas as to what might be causing this, everything else works as normal, texts, Internet,etc it's just calling someone they cant hear me and that's probably the most important thing about having a phone.
Id sooner not bring it into Fonemenders as ive heard some bad reports about this company, it's still under warranty with 3 Ireland and this is the company they use for repairs.
Phone has been fine up to this and i haven't dropped it or anything.
Cheers
84 views - no one got any ideas?
It will be a wrench if i have to stay on the stock ROM for the sound in my calls to work but i am dumbstruck as to how this has happened as it never did previously, is it remotely possible that 3 Ireland may have changed some settings whereas the sound in calls only work with their stock ROM, unlikely i know but im looking to explore all avenues before i bring this in for repairs.
Well posted problem all over the board in custom roms etc for starters .LFB Modem or something like it .
jje
JJEgan said:
Well posted problem all over the board in custom roms etc for starters .LFB Modem or something like it .
jje
Click to expand...
Click to collapse
i haven't seen anyone post an issue like this on here yet (unless i missed something)
i am gonna revert back to Stock ROM and test it again, then ill root and flash a kernel and see what happens.
Truly bizzare this is
WORKING AGAIN
Flashed Android Revolution out of curiosity to see what happens, made a call to a friend and he could hear me fine, got him to call me and likewise so im now sure it isn't actually the mic which is faulty it must have something to do with ROM and / or Kernel but im fu*ked if i know what it is as ive been using CheckRom and Franco kernel for a good while now without any issues, isn't there anyone else on here who has had similar issues like this?
I'm just setting up my phone again, i hope this problem doesn't come back.
I have the same problem, only that not only on checkrom... I have tried several other roms and I have the same problem, with an exception... i always hear them and they can't hear me but is not continously... 15-20 seconds is ok then 10-15 they can no longer hear me... this is on checrom v3 with lbf modem... ANY OTHER ROM, kernel or modem no sound what so ever. It seems there are too few of us in order for devs to look into it... unfortunately
Sent from my GT-I9300 using xda premium
Devs don't get paid to look into stuff .
Multiple call sound posts many ref LBF modem.
jje.
Sent from my GT-I9300 using xda premium
daniel_cassian said:
I have the same problem, only that not only on checkrom... I have tried several other roms and I have the same problem, with an exception... i always hear them and they can't hear me but is not continously... 15-20 seconds is ok then 10-15 they can no longer hear me... this is on checrom v3 with lbf modem... ANY OTHER ROM, kernel or modem no sound what so ever. It seems there are too few of us in order for devs to look into it... unfortunately
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
FINALLY someone else with the same issue, basically when i call someone i could hear them but they couldnt hear me,when they called i could hear them but they couldn't hear me, the problem appears to have been (hopedully) resolved now ive flashed Android Revolution, ill have to avoid CheckRom which is unfortunate as it's always been my fav ROM but the problem appeared to come back after i flashed back to stock ROM then back to CheckRom,
Hi I have the no sound in call when I remove system apps or freeze apps I was use the unofficial aopk ROM I'm now using the cm10 preview and still have the same problem I've tried loads of different modems with no luck it
Sent from my GT-I9300 using xda premium
There are a lot of reports with different roms of the same thing and so far all I've seen have been modem issues. I saw some people said they've tried different ones which seems weird, I'm running Checkrom 3.5 and Siyah kernel 1.4 with the new XXLG8 modem and have no problems. I was using LFB and had issues and LF3 worked as well.
It's definitely not a mic problem is using stock fixes it so don't send it in for repairs, just try some of the newest modems. I hope that helps.
Sent from my GT-I9300 using xda premium
I never previously had a problem running check rom and franco kernel but ive no idea what happened , i do freeze stuff in Titanium Backup but only stuff wgich people have already tested and it's safe to freeze so it's quite baffling what caused this problem but since flashing Android Revolution everything is fine it's a superb ROM too close to stock which is what i want and everything works 100%, ive no real interest in CM10 too many bugs for my liking ill just wait until the official Jelly Bean code is released for the Galaxy S3.
dantheman122 said:
There are a lot of reports with different roms of the same thing and so far all I've seen have been modem issues. I saw some people said they've tried different ones which seems weird, I'm running Checkrom 3.5 and Siyah kernel 1.4 with the new XXLG8 modem and have no problems. I was using LFB and had issues and LF3 worked as well.
It's definitely not a mic problem is using stock fixes it so don't send it in for repairs, just try some of the newest modems. I hope that helps.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Yeah i agree mate it's definitely not a mic problem im not 100% what caused it but i do believe it might be LFB modem or something related to this.