Hey Guys,
Flashed the leaked Tmoble 6.5 ROM just to see how it looks which also changed my radio to 4.49.25.57. I think its since then I have had this problem. I was using the latest Cell Pro 9.5 till then, so I flashed back. I install all my softwares and tweaks and use it without any problems for a full day or two.
Then the next day or night when I try to make a call, it goes from "dialing" to "connected" without any ring or any other indications, I cannot hear anything on my side. I learned that the person on the other side receives the call but after accepting the call he/she cannot hear anything. This has happened to me trice and every time I thought it was the ROM so reflashed...works fine for a day or two and the cycle repeats. I tried flashing other tmoble radios from the radio thread before flashing a new ROM and no luck.
Any help will be appreciated. I am just tired of flashing again and again, mainly the task of installing all the softwares, email setup etc etc.
Same but Different
I have had similar issues to yours. Same symptoms, but different ROM and I'm on Verizon. I don't think it has anything to do with your radio. Whenever I have had this issue, I did a hard reset (no ROM change) and it fixed the issue. I think that it is an issue with using some tweak. I am currently trying to isolate the issue. I have suspicions of some settings in Advanced Configuration.
Are you using Advanced Config?
Not on the Cell Pro 9.5, it comes with HD Tweaks and Rhodium Setting (or something). Thanks for the feedback.
Related
hi,
from time to time I experience the folowing:
Suddenly, soemone call me to other phone becuase he's trying to contact me. I see my artemis and it's OK, switched on and signal bars at 90%. I dont know why when someone try to call me appears like the phone is switched off.
I make a soft reset and strat to receive missed calls + sms's.
I have Vanilla 4.02 ROM and I use very often the wifi connection....
br.
im with you there, this is the reason why i went back to my aging nokia 6280. ive tried about 10 different roms and it would never pick up the signal unless rebooted. what happens with mine and a few of my friends was on london underground you would lose the signal obviously underground, when you came out the phone would pick up the signal but never recieve a call or sms. also the gprs wouldnt connect unless it was rebooted. ive had a few htcs in the past but because of this poor show i wont ever purchase another one.
my phone done this from day one of ownership, tmobile told me that firmware upgrades would fix this annoying problem, but it never did.
maybe you should try updating your radio ROMs
flashing different ROMs wont help
done half a dozen of them as well on my phone.
audiobookman said:
done half a dozen of them as well on my phone.
Click to expand...
Click to collapse
Even, I had the same problem, but since I moved to Radio version 3.21.XX, everything is just fine, no problems since then. Even 3.24.XX is out now, you should definitely give it a try. Hope it works for you!!
Cheers!
Same problem
Thanks for posting. I have the same problem with the same ROM. I'll change radio rom.
Radio Rom changed
Radio Rom changed 3.34.90 . No problems and good quality
I have tried to do a number of searches and am not finding any relevant information. If this is a known bug, please forgive me.
I am using a red MyTouch 3G Slide, running Cyanogen 6.1.1. I have already flashed back to engineering, down every wipe I see available, and then flashed back to C6.1.1, and the problem persisted. Unfortunately, I was not able to test for it while on the eng build; I'd rather avoid flashing back to that or any stock ROM (having trouble finding a untouched stock ROM, to be honest) but of course if that seems like a good place to start with trouble-shooting I can do it.
This is my first Android phone, and I don't know my way around everything, nor all the lingo yet.
The problem I am encountering is that, seemingly strictly on out-going calls, in some instances upon connection the person I am calling is greeted by heavy distortion of my voice. Switching to speakerphone and then back to handset resolves the issue for the duration of that call. To make things trickier, the contacts affected by this are ALWAYS affected by it; I have to switch to speakerphone and then back, and suddenly the call is crystal clear.
This has been verified with multiple independent contacts who do not know each other; they are not conspiring to prank me. Furthermore, I have noted the problem affects both land-line and mobile contacts. However, it does not affect all of my contacts.
This does not seem to affect incoming calls.
Any ideas?
Borteeo said:
I have tried to do a number of searches and am not finding any relevant information. If this is a known bug, please forgive me.
I am using a red MyTouch 3G Slide, running Cyanogen 6.1.1. I have already flashed back to engineering, down every wipe I see available, and then flashed back to C6.1.1, and the problem persisted. Unfortunately, I was not able to test for it while on the eng build; I'd rather avoid flashing back to that or any stock ROM (having trouble finding a untouched stock ROM, to be honest) but of course if that seems like a good place to start with trouble-shooting I can do it.
This is my first Android phone, and I don't know my way around everything, nor all the lingo yet.
The problem I am encountering is that, seemingly strictly on out-going calls, in some instances upon connection the person I am calling is greeted by heavy distortion of my voice. Switching to speakerphone and then back to handset resolves the issue for the duration of that call. To make things trickier, the contacts affected by this are ALWAYS affected by it; I have to switch to speakerphone and then back, and suddenly the call is crystal clear.
This has been verified with multiple independent contacts who do not know each other; they are not conspiring to prank me. Furthermore, I have noted the problem affects both land-line and mobile contacts. However, it does not affect all of my contacts.
This does not seem to affect incoming calls.
Any ideas?
Click to expand...
Click to collapse
That is a very strange issue. First step is to get CR_Mod OTA from the development section here, and flash that through clockwork recovery. See if it happens on that. CR_Mod is just the rooted stock ROM with wifi tether and superuser app, that's it. If it still happens there, then I would try getting a replacement SIM card from t-mobile, it MIGHT be a bad SIM, although that seems less likely.
Thanks mate! Actually, I'm running it on Wind Mobile in Canada. Currently a friend is borrowing the phone to test; if he encounters problems then I'll try the ROM you have suggested and report back, otherwise it's fresh SIM time. Thank you for responding.
I've been seeing this problem for a few weeks now, with several different ROMs, including the original rooted stock ROM now. In nearly all of my recent calls, I get disconnected one or more times with the message "Call disconnected" and a "Dismiss" button. I'm thinking that this is because of my EVO and not the other side, since usually if they accidentally hang up or something the call just ends without a message box. As far as I can tell, I have good reception (at least according to the bars), and this is happening at home, where I've not had the problem before.
Does anyone know what could be causing this? My wife's EVO is not rooted, and she does not seem to be having this problem. But then again, I've not had the problem until fairly recently either. I've tried updating my profile and PRL with each new ROM, but it doesn't seem to have made a difference. Anyone have any suggestions as to how to stop this from happening?
Go into the settings menu andbupdate both your PRL and your profile. That *should* help with reception related issues.
posting & replying via the XDA Premium app.
Unfortunately, I've tried both of those things. I just did some testing today, and it seems that my phone is unable to stay connected during a phone call for more than five minutes before disconnecting, even if I don't touch the phone and just leave it sitting on a table.
Any other ideas? As far as I know, I haven't ever flashed my radio away from its default (2.15.00.11.19), and I'm currently using the leaked stock gingerbread ROM (build number 4.12.651.1 CL41771 release-keys and kernel 2.6.35.10-gaa602b7 [email protected] #1).
Maybe it's time to unroot and contact Sprint?
You can try downgrading from 2.15.00.11.19 to 2.15.00.09.01. You can download it from http://www.mediafire.com/file/jyedjkp1bm5amwm/EVO_Radio_2.15.00.09.01.zip
Afterwards, go into recovery, wipe cache & dalvik cache then flash the zip. You will be taken to the radio update screen and appear to hang. don't worry or get impatient. After it is finished, you will reboot into recovery and see the words "clearing cache" at the top of the screen. Simply select reboot and then you will boot to your homescreen. The initial boot will take a tad longer since it will be rebuilding the dalvik.
Hmm... I'm hesitant to downgrade my radio because my wife has an EVO with the same radio version number and hers doesn't have this problem. Granted, she is not rooted...
I understand. I've downgraded and upgraded everything several times for testing purposes and troubleshooting purposes and have never had a problem. The only hing about flashing radios is patience and not to pull the battery. Anyway, you can always call Sprint and see if they can troubleshoot it for you from their end.
posting & replying via the XDA Premium app.
I would contact sprint @ 877-809-6696 (advanced tech supp). Ask them to push a full reprovision to your device. See if that helps any. I was having issues when when on the airave, I was unable to receive incoming calls. This corrected it. I did try all the other steps listed above without any success.
This is interesting. I unrooted to test things out before calling Sprint, and the problem went away. I was able to stay connected for an hour (where before I couldn't last longer than 10-15 minutes). Yay, fixed, right? So, I rooted again and didn't install any ROMs or anything, just rooted, and the problem came back.
So, I have a solution, but I don't like it very much because it means I need to stay unrooted. Anyone have any idea why simply rooting the phone with Unrevoked 3 (and doing nothing else) could cause calls to disconnect? I'd love to be able to root again, but I can't deal with a phone that randomly disconnects all the time.
I am interested in this as well as I am rooted using unrevoked and get disconnected as well. I do find that it mainly happens though talking to people who have service on AT&T.. Quite wierd. All I hear is a beep then disconnected. This happens when I first place a call and it rings once or twice then beep, disconnected...
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
KingFunderberk said:
This may not be related to rooting. I'm still communicating with Sprint about this issue, and along they way they replaced my phone entirely, and the problem is still happening. Very frustrating, but it makes it very clear that the problem actually has nothing to do with the hardware. I'm pretty sure there is some network configuration problem on their end now. I'm waiting to root my new phone until this issue has been resolved. It is killing me!
Click to expand...
Click to collapse
So whats the final call on this ..?
Is it Rooting , Is it network .. i am too getting psyche with this .
I'm pretty sure it is not rooting. But I don't yet know for certain what it is. Sprint thought there might be something wrong with the antenna on my phone, but they had already replaced the phone, so I think that is unlikely. They gave me a femtocell range extender to use in my house. Basically, I plug it into my broadband connection, and it is like having a mini cell tower in my house, giving me a very strong connection. Sure enough, when connected to that, I haven't had any calls drop. However, my phone still sometimes doesn't connect to the femtocell and instead connects to some other tower for some reason. My wife's phone doesn't do this, so I still think there is something wrong with my phone. I may contact Sprint again about this. ...sigh...
What is your area some area evo don't work properly like on rahim yar khan in this time connection don't work properly some signal drop and some time up i sure after few day signal work properly then problems will be solve.
My phone EVO is doing this now as well. Has anyone heard/read a solution?
greg_99 said:
My phone EVO is doing this now as well. Has anyone heard/read a solution?
Click to expand...
Click to collapse
I am having the same issue, out of the blue. No problems up until a few days ago. I'm wondering if it is maybe an issue with a certain version of the Evo. I have a version 002. Thoughts?
Greg_99 any progress on what might be causing this issue?
New user, first post, if I am missing info then I apologize.
I have the tmobile galaxy s 3 SGH-t999.
Started looking around at different roms, etc, ended up with trying the cyanogenmod 10 first.
Did the required steps, used oden to load the clockworkmod recovery.
Wiped/factory reset, then loaded up the rom. Seemed to work pretty well other than some issues with the cam crashing (seperate issue which I researched and believe I have the answer to). But overall the problem was that intermittently the inbound audio on calls sounded robotic, and reverberating. Also dealt with 4 hour battery life. Tons of info to address later when this issue is corrected however.
Have been digging around on forums, and see this issue, but no articles yet (that i have found) addressed for the SGH-t999.
Ended up re-wiping the phone and put on the liquid smooth rc9 (d2tmo).
So far it appears i am having basically the same exact issues that occurred in cyanogenmod. If I reboot the phone, it will continue. Then for whatever reason the next few calls or so later that are sent or received it sounds fine. Then back to robotic.
End user can hear me fine. The audio issue is just for inbound voice.
Tried to factory reset again, still the same issue.
I have installed the google pack to be able to use play store, etc. Perhaps this is causing the issue?
I did try to get the log cat, but could not replicate the issue while running it, so I am not sure if it would be of any use or not.
Also, this issue does not make a difference whether bluetooth is enabled or not. Am not doing wifi calling, have not tested that yet.
Again very sorry if this article is incomplete.
Thanks in advance for the help!
Resolved
tsm233 said:
New user, first post, if I am missing info then I apologize.
I have the tmobile galaxy s 3 SGH-t999.
Started looking around at different roms, etc, ended up with trying the cyanogenmod 10 first.
Did the required steps, used oden to load the clockworkmod recovery.
Wiped/factory reset, then loaded up the rom. Seemed to work pretty well other than some issues with the cam crashing (seperate issue which I researched and believe I have the answer to). But overall the problem was that intermittently the inbound audio on calls sounded robotic, and reverberating. Also dealt with 4 hour battery life. Tons of info to address later when this issue is corrected however.
Have been digging around on forums, and see this issue, but no articles yet (that i have found) addressed for the SGH-t999.
Ended up re-wiping the phone and put on the liquid smooth rc9 (d2tmo).
So far it appears i am having basically the same exact issues that occurred in cyanogenmod. If I reboot the phone, it will continue. Then for whatever reason the next few calls or so later that are sent or received it sounds fine. Then back to robotic.
End user can hear me fine. The audio issue is just for inbound voice.
Tried to factory reset again, still the same issue.
I have installed the google pack to be able to use play store, etc. Perhaps this is causing the issue?
I did try to get the log cat, but could not replicate the issue while running it, so I am not sure if it would be of any use or not.
Also, this issue does not make a difference whether bluetooth is enabled or not. Am not doing wifi calling, have not tested that yet.
Again very sorry if this article is incomplete.
Thanks in advance for the help!
Click to expand...
Click to collapse
Ok, after 4 different roms, and lots of testing, I finally figure it out.
Using Voxer caused the issue. As soon as a voice message is sent using voxer, the problem starts immediately, and is correct by a reboot. Issue immediately returns once Voxer is used.
Any idea of how to work around this, besides the obvious? =)
Hello there. I have a major problem which is makeing me consider going back to stock. When someone calls me or I call someone the call connects but I cannot hear the person on the line and they cannot hear me. I do not have this problem when I use Csipsimple to make voip calls. Its only when I use the actuall line. I am useing P.A.Cman True All in 1 ROM with the UVLI1 radio. Can someone please help me. This is a major game breaking feature. I have tried two differnt roms and a differnt radio. It will work intermittently for a bit but then stop. Some times a reboot will work. Some times it wont. Please help before I buy a different phone
I've had that issue before and its annoying. ROM related or maybe just how u flashed it. I would reflash with a clean wipe if u insist on sticking with that ROM. If not then I would recommend using slim star 2.2 ROM. That I can guarantee will not have this problem. If perhaps u still do however, then I would have to say you have a bigger problem....hardware even perhaps....but I highly doubt it...
So yeah try slimstar2.2 just to troubleshoot then go back if you want and ull see if its just the ROM. I'm not advocating slimstar over PAC allinone I'm just picking it cuz its what I have now and I can confirm u won't have that issue. Good luck
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Had this problem on most Roms with a bunch of different radios. Thought it might be a hardware problem. I flashed the new UVLI4 and not only am I receiving calls where I never received them before but I'm not getting my 2 phone calls a day with no one on the other end. Only about 4 days into it, but no empty phone calls yet. Actually took me 2 days to realize it, kinda nice.
I've had a similar problem intermittently on several ROMs. My first suggestion is to reflash the radio - often this will fix the issue. If that doesn't work, you can contact tmo customer service and have them reset your phone on the network by "purging your HLR or BLR on the network (source: http://forum.xda-developers.com/showthread.php?p=35585027), That's worked for me also. hope that helps.