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.
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.
Is anyone else having issues with the other party hearing you in call? I have a case, and no matter if I have it on or off, the other party can't hear me unless I talk louder than normal. I don't recall having to talk that loud on my iPhone to be heard. Was happening on CM7 and latest UnNamedROM.
I've encountered the same issue. I've been running unnamed since the day I got my phone, and am ocrrently on 2.2.1. I've read of others having this issue as well. I've also read somewhere that disabling the noise canceling feature supposedly helps. I've done so, but not sure if or how much it helps, as I can't hear myself from the other end. Perhaps someone else can chime in with advice regarding this topic.
So I was doing some more tests. It seems I might be holding the phone away from my face when I speak in an effort to not get face grease on the screen. Will have to do more testing to verify.
Sent from my SAMSUNG-SGH-I777 using XDA App
I too have this issue whenever I use the UCKK6 modem after the OTA update. Whenever I was on the UCKH7 firmware + modem, I had no problems and when I use the UCKK6 firmware + UCKH7 modem, I also don't have problems.
When using the UCKK6 modem though, I get a LOT of people complaining that they can't hear me and will sometimes even hang up on me because they think my call dropped (I'm still there though and can hear them perfectly).
It sounds like your mouth is being muffled or like you are underwater- or like you are randomly teleporting yourself across the room, while leaving your phone in one place.
I have done several tests myself by calling my house phone with my cell and putting the house phone on mute (to prevent echo). I then hold both phones to each ear and basically talk to myself. One test even involves me saying the alphabet. I have done these tests several times using both modems.
My tests gave me the conclusion that the K6 modem is buggy, but is especially unusable with the noise suppression turned on. When on, certain syllables seem to get cancelled out by the noise suppression, as though it thinks that part of it is background noise. However, even with the noise suppression off, I still get the occassional fading of my voice, but it is extremely occassional compared to when the noise suppression feature is on, where it is almost every couple words or so.
With the H7 modem, I notice no problems whatsoever, whether the noise suppression is on or off.
So, I recommend doing one of the following if you are experiencing these issues:
1) Revert completely back to UCKH7 firmware and modem if you want/need the noise suppression.
2) Use the UCKK6 firmware with the UCKH7 modem if you want/need the noise suppression.
3) Continue using UCKK6 firmware and modem, but turn the noise suppression off.
1 and 2 are sure fire ways to not have any issues at all. 3 may still give you problems, but it may happen once every few minutes with noise suppression off (still there, but not nearly as noticeable), while once every couple syllables with the feature on (very freaking noticeable!).
Sent from my SAMSUNG-SGH-I777 using XDA App
So I started having this issue a couple days ago.
I've tried going back to the KH7 modem and still not working. I even tried restoring to stock.
Mic works fine in speakerphone mode, but I get absolutely no sound otherwise (I can shout into the phone and the other side hears nothing). Noise suppression toggle doesn't do anything.
Thoughts?
I guess I'll try taking the phone into ATT this weekend.
^
That sounds like hardware issues, so yeah, bring it back to ATT.
Sent from my SAMSUNG-SGH-I777 using XDA App
dragon_99 said:
So I started having this issue a couple days ago.
I've tried going back to the KH7 modem and still not working. I even tried restoring to stock.
Mic works fine in speakerphone mode, but I get absolutely no sound otherwise (I can shout into the phone and the other side hears nothing). Noise suppression toggle doesn't do anything.
Thoughts?
I guess I'll try taking the phone into ATT this weekend.
Click to expand...
Click to collapse
If it works fine in speakerphone mode that means it isn't a hardware problem -_-
Try this. Open up your phone and...
Type this in: *#*#197328640#*#*
Click on [5] AUDIO
Click on [8] AUDIENCE SETTING
Click on [2] AUDIENCE DISABLE
then try out a test call and see if it works
Problem with mic and in call volume too low
shishir95 said:
If it works fine in speakerphone mode that means it isn't a hardware problem -_-
Try this. Open up your phone and...
Type this in: *#*#197328640#*#*
Click on [5] AUDIO
Click on [8] AUDIENCE SETTING
Click on [2] AUDIENCE DISABLE
then try out a test call and see if it works
Click to expand...
Click to collapse
The above code does not work on AT&T version, I guess. At least it did not work for me. Don't know if root makes any difference, yes I can have booster apps. But again people have reported that this does not seem to work.
I happen to read in International s2 forum that opening the phone and making a bigger hole for mic helps. Or even cutting a slice of the white protective casing around the lower micophone seems to help as well. I did not want to tamper with hardware at the moment, as I am just 10 days past my warranty period.
Let me know if someone knows some funky codes to get this fixed. I am running 2.3.4 stock ROM and not rooted yet.
- Thanks
androidarena said:
The above code does not work on AT&T version, I guess. At least it did not work for me. Don't know if root makes any difference, yes I can have booster apps. But again people have reported that this does not seem to work.
I happen to read in International s2 forum that opening the phone and making a bigger hole for mic helps. Or even cutting a slice of the white protective casing around the lower micophone seems to help as well. I did not want to tamper with hardware at the moment, as I am just 10 days past my warranty period.
Let me know if someone knows some funky codes to get this fixed. I am running 2.3.4 stock ROM and not rooted yet.
- Thanks
Click to expand...
Click to collapse
I'm on AT&T and the code worked for me, however I'm still having the issue. I don't necessarily think messing with the hardware by cutting or slicing will fix it because (for me at least) the problem is intermittent. Sometimes I'll go afew days without the problem, then I can have 3 calls back to back where the person doesn't hear me at all. It can happen both when I initiate the call or answer and it doesn't always happen in the same point of the call. This is pretty frustrating, I really hope there's a fix because I don't want to have to convert to stock and deal with AT&T.
I had this issue. Mine was not intermittent, the mic just stopped working. No amount of flashing or resets from ATT could make it work again.
Strangely enough the speakerphone worked fine and that just screams software issue, but AT&T chose to replace my hardware.
The problem seems to be intermittent for me too.... I don't know how the code works for Griffon23, as AT&T has disabled that on our model. I have not updated to 2.3.6 as the firmware ushers in loads of problems.
I really hope there is a fix, I am just being lazy to flash new roms and stuff, as I might have to return this piece of S#$#t due the low volume and poor mic. Such a shame that expensive phone like this has issues with basic functionality, voice calls.
I also tried good in ear headphones, that solves the problem of low in call volume but not microphone, which simply points that there is some internal problem. May be hardware or may br firmware. And May be ICS update can fix this for us. Fingers crossed.
Thank you Samsung!
spexwood said:
I too have this issue whenever I use the UCKK6 modem after the OTA update. Whenever I was on the UCKH7 firmware + modem, I had no problems and when I use the UCKK6 firmware + UCKH7 modem, I also don't have problems.
When using the UCKK6 modem though, I get a LOT of people complaining that they can't hear me and will sometimes even hang up on me because they think my call dropped (I'm still there though and can hear them perfectly).
It sounds like your mouth is being muffled or like you are underwater- or like you are randomly teleporting yourself across the room, while leaving your phone in one place.
Click to expand...
Click to collapse
THIS. I was having a similar problem a while back. People were telling me that my voice was cutting in and out a lot. Not even looking for it, I found this thread and flashed the UCKH7 modem. I also read somewhere that it helps battery life too as that's what I was searching for.
Anyway, It's now been several weeks now and I had forgotten about the problem until I saw this thread again. I guess I'd have to say that the UCKH7 modem definitely solved my problems as I can't remember the last time someone complained about my voice cutting in and out.
Since this is the only thread similarly related to my issue, I'll continue this one instead of starting a new one. So I've tried the above listed suggestions and the dial code for the audio does not work for me, as a matter of fact, none of the dial codes work for my phone, I get a "Invalid MMI code or no connection" error. I Have not been able to make a call on speakerphone since I flashed my phone for the first time back when I first got it. I've switched around from different ROMs and I get the same issue. The main issue is that no one can hear me when I'm on speakerphone, but I can hear them. I can make regular calls just fine. I've even flashed back to stock and the issue still persists. Are there any suggestions? I am currently on the latest AOKP build of ICS.
If you've been flashing different ICS roms, there's a chance you flashed one of the mic-swapped kernels. Try the AOSP/AOKP version of NEAK. Make sure to wipe cache and dalvik before flashing.
EDIT: Didn't read your post closely enough, if regular calls work, the kernel shouldn't be the problem. Maybe the modem? UCKH7 is what most people report with good results, depending on area.
Have you ever been able to use the speakerphone? Do you know for certain that it works?
AoN
Sent from my SAMSUNG-SGH-I777 using XDA
I just came across this thread after a long time. I was surprised to see how much it has grown!p and how many people haod similar issues as me!
Well, I kind of wanted to give an update and suggestion for those who still have issues.
First my update. Since having these issues in UCKK6 and ICS leaks, I actually gave up on ATT's firmware and moved on to custom ROMs. Currently- and loving it- I'm on a ROM called Mystic's Pride (will be going to Mystic's Glory, a more advanced version- once it is out of Beta testing). Mystic's ROMs are ported firmwares from the international SGS2, but they use the latest ATT modems since the international version's will not work on our phones.
Using a custom ROM will NOT fix the call quality issue. That is all linked to the modem.
Now the suggestions. While running UCKK6, I discovered that you could use the UCKH7 modem with it. So for a while (until I noticed excess battery drain issues), i was using the UCKK6 firmware with the UCKH7 modem.
NO MATTER WHAT VERSION FIRMWARE YOU ARE USING (Gingerbread OR ICS), YOU CAN USE THE UCKH7 MODEM!
As I stated in my update, I am running a custom ROM now, which is Android 4.0.4. Im still using the UCKH7 modem and my calls are super clear and I am not having any issues with people hearing me.
You may be asking, "If you are now on ICS, then why not just use the latest ATT ICS modem?" The answer is simply that after all of my experiences with horrible call quality using official ATT modems, I simply do not trust them anymore. I know of one modem that works, so I have stuck with it without issues. I plan to test out the newest ICS modem though... just to see how it compares with UCKH7. If no good, then its back to KH7.
So, if you are still having issues, then try flashing the UCKH7 modem to your phone. You do not need to be rooted in order to do this. All you need is Odin and to boot into Download mode.
If you flashed the KH7 modem and still having issues, then you most likely have a hardware problem.
Another thing I noticed while still using UCKK6 with its corresponding modem is that by turning off the Noise Suppression, you can get better quality calls. However, using UCKH7 modem may make your calls clearer, but will allow you to use Noise Suppression.
I hope this helps somewhat. I have NOT sent my phones in for repairs/replacement for this issue and my calls are just as clear as the day I bought my phone.
Ill try to pop in here to answer questions, etc if needed.
Sent from my A500 using xda app-developers app
Lol spexwood, I know you're trying to be helpful, but I gotta let you know your post is way old news. It's been common knowledge for a long time that you can flash any ATT I777 modem with any firmware, using ClockworkMod Recovery. It is useful (to me at least, didn't know this before) to know you can also use Odin to flash modems if you don't have CWM, but most I777 users around here have it because they use custom kernels and ROMs. There's a whole thread which contains every single modem in CWM-flashable zips, and it also contains a Google map with notes about which modems users have reported working best for them in their respective locations; this might be helpful to you if you didn't know about it beforehand.
tl;dr - try all the different modems to see which one gives you the best speeds and call quality in your area, they are interchangeable. Use this thread to help you out.
This is one problem I've had when completely stock, ics, and jb. And it mostly occurs when I have ear phones plugged in
Sent from my SGH-I777 using XDA Premium App
Spxewood, all of what you said is common knowledge. If you're going to necro a thread, please only do so for new information
Sent from team Pirate! Using Tapatalk 2
Well EXCUSE ME for thinking that I WAS posting new information and for only trying to help people out!!!!
If you didn't like it then just ignore it!!!!!
Sent from my A500 using xda app-developers app
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 don't remember when exactly it all started but I've been experiencing random and frequent data drops on my thunderbolt.
I tried flashing every possible radio, kernel and rom combination and finally came to conclusion that call master app is causing this.
does anyone has a recommendation for a radio/rom that actually works with call master? or at least a real call master alternative? I tried many call blockers and none of them come close to call master.
please help, I'm going crazy about this issue!
P.S. If someone has older version of call master, could you please send it to me so I can see if that fixes my problem. I have purchased the key, I just believe that newest update screwed my data.
thatsonlyme said:
I don't remember when exactly it all started but I've been experiencing random and frequent data drops on my thunderbolt.
I tried flashing every possible radio, kernel and rom combination and finally came to conclusion that call master app is causing this.
does anyone has a recommendation for a radio/rom that actually works with call master? or at least a real call master alternative? I tried many call blockers and none of them come close to call master.
please help, I'm going crazy about this issue!
P.S. If someone has older version of call master, could you please send it to me so I can see if that fixes my problem. I have purchased the key, I just believe that newest update screwed my data.
Click to expand...
Click to collapse
same problem here. i am running liquid smooth...
I don't know about call master but I know that it has been reported by several members, including myself, that there have been frequent data drops. It has been happening over the course if a month in different areas. So it could be in fact a Verizon thing. I am running eternity r248 with the latest radios and have been pretty steady as of lately.
Sent from my ADR6400L using xda premium
Mine recently started dropping in and out too but it didn't start until about a week after others reported it. I switched to the 605.9 radios and it helped for a couple of days but it started back up again. I'm going to assume it's a verizon issue at this point.
Sent from my ADR6400L using Tapatalk 2