Is there a way to tell if you dropped a call? I drop one a week but idk if its my friend with his new headset or what. Is there a way to tell? Before lately I don't think I've had a dropped call in 2 mo since I had my cappy. Last few weeks I've been running ultimate rom v 5 something. Before cognition 2.6 and above. All help is appreciated. And how often do you guys drop calls? And this is inside my house. Lots of windows. Oh and one more thing. I have noticed texts coming a minuet before or during the few drops if I remember right. But I have also texted myself and had some1 text spam me on the phone and nothing happened.
Thx
Sent from my GT-I9000 using XDA App
???
Sent from my GT-I9000 using XDA App
JJ133169 said:
Is there a way to tell if you dropped a call? I drop one a week but idk if its my friend with his new headset or what. Is there a way to tell? Before lately I don't think I've had a dropped call in 2 mo since I had my cappy. Last few weeks I've been running ultimate rom v 5 something. Before cognition 2.6 and above. All help is appreciated. And how often do you guys drop calls? And this is inside my house. Lots of windows. Oh and one more thing. I have noticed texts coming a minuet before or during the few drops if I remember right. But I have also texted myself and had some1 text spam me on the phone and nothing happened.
Thx
Click to expand...
Click to collapse
Unfortunately, I can't help with a method to see what calls have been dropped.
I have been experiencing dropped calls since upgrading to the official ATT 2.2 build. In the last week I've had almost all of my 'long' calls drop on me. Looking at my call log, it appears that anytime I have a call that lasts >20 minutes it gets dropped.
Lots of dropped calls here too after 2.2 (Cognition 4 & 4.1). Rarely had A problem before.
Sent from my SAMSUNG-SGH-I897 using XDA App
Yes. I am running the stock ATT 2.2 rom. Loaded it the day it came out. Since then, I have had several (8 - 10) dropped calls. Before that, none. I am fairly sure it is my phone because it can occur reguardless of who I am talking to or what time of day. Length of the conversation doesnt seem to matter either.
I am experiencing this as well. Frequent dropped calls recently.
Thanks guys. This helps, my gf just got a captivate, 11XX build with 2.2 pre-installed. So I'm going to root it and either put in a new modem or a new ROM all together because she likes it but doesnt due to "lack of signal" and "dropped calls" so sounds to me like the KB1 modem isnt all that good....
Another question here, JW in keis can you go from 2.2 stock to 2.1 stock? or does it not let you downgrade ? ( I know you can with oden, Just wondering if there is a AT&T supported way of downgrading...?)
since i flashed the ugjl2 modem i haven't had any more problems
kingmurry said:
since i flashed the ugjl2 modem i haven't had any more problems
Click to expand...
Click to collapse
What ROM and kernel are you running with that modem??
thanks!
if it's happened after a flash, you may be running an incompatible modem.
Me and my girlfriend, both on our stock froyoed Captivates, constantly have calls dropped by our phones since the upgrade. We have both done a factory reset and rooted after the upgrade. Any help or explanation is appreciated.
Also, her random shutdowns unfortunately continue...
Sent from my SAMSUNG-SGH-I897 using XDA App
ruger94 said:
What ROM and kernel are you running with that modem??
thanks!
Click to expand...
Click to collapse
firfly 2.6 suckerpunck #59
Related
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
brandon827 said:
Yep, happens to me all the time. Internet doesn't always work either. I "fixed" the problem by setting it to GSM only mode. Now I only have EDGE internet.
Click to expand...
Click to collapse
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
sliderocket22 said:
Are you on the same rooted stock rom, or something different? I don't seem to remember having this problem when I was just on pure stock AT&T with no root. Somewhat annoying, as I'll have to place a call 3 or 4 times to get it to go through, but what's really annoying is that it is so sporadic I can't gauge when it'll happen!
Click to expand...
Click to collapse
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
homeslice976 said:
I've noticed this at multiple times, but haven't been able to narrow down what's causing it. I was running Revolution 1.15, and I think it started when I applied the .16 performance patch. It got so bad last night I couldn't make/receive calls for hours. I did a full wipe an reinstalled 1.15 and all has been well the last 24 hours. I just flashed the 2.1 patch but we'll see what happens. Note: Not only can you not make calls when this is happening you won't be able to receive calls either. It does appear to most often happen when bouncing between networks (HSDPA, UMTS, Edge, etc)
Click to expand...
Click to collapse
Man, I'm glad I'm not the only one having this problem. I thought my phone was defective at first, and now I don't feel so crazy anymore. My sister was furious with me, I had to pick her and her boyfriend up from DIA yesterday to take her to Copper Mountain to snowboard with my girlfriend and myself, and she called me 4 times and I didn't receive a single one. I wonder if it has anything to do with HSUPA being enabled on the phones, but at this point I'm just ready to give up root and go back to stock. I don't make tons of calls, but I'd like to be able to when I need to, and for my phone to not hang up on me in the middle of one. I have noticed though it's particularly bad for me when I'm on bluetooth.
I was also having those problems
I am using Revolution 4G 2.1. I'm in the process of trying to get the problem figured out. Stock rooted rom had problems for me because you couldn't set it to GSM only, and that's the only way I've found to make the phone reliably work as a phone.
If anyone can figure it out, I'd love to know what causes it. I've been poking around myself, but haven't come up with anything worthwhile. I suppose I'll flash a different rom and try that.
Sent from my Desire HD using XDA App
Anyone found any clue as to why this happens? I've searched the dev forums but nobody seems to mention this, which makes me wonder if most people have this problem.
Sent from my Desire HD using XDA App
I have never had this problem. Running a rooted stocker.
Sent from my Desire HD using XDA App
It happened to me again last night. Still had data but lost the ability to make/receive calls. I switched network to GSM only, the data switched to EDGE, and i was able to make/recieve calls. Turned back to GSM/WCDMA, no calls. Rebooted, no calls. Turned back to GSM only, calling functionality returned. I did another full wipe, installed AR 2.1, sound fix, apache 1.6 kernel, and calling is restored when connected to HSDPA/WCDMA. Has been working fine for the last 12 hours. I'll keep you updated. I don't know why it's doing this, and it doesn't make sense as to why a wipe would fix it. The first time this happened I was runing the stock radio. Last night when it happened i was running the recommended radio in the AR thread (M2). I've now switched back to stock this time...let's see what happens
Edit: I am also glad to know I'm not the only one having these issues...maybe someone a LOT smarter than I am can figure it out. It's annoying to have to have a slow data connection to have a reliable voice connection. The last Android I had (LG GW620 Eve), also did this from time to time, but I just blamed it on the fact that it was a POS. My voicemail actually went like this "This is Greg. I probably have no idea you called me just now, so please leave a message and I'll get back to you"
Edit: mike1986 (android revolution developer) just chimed in in his thread and stated these issues should be fixed in version 3.0 set to be released soon. Is anyone else that's having these problems NOT running Revolution?
sliderocket22 said:
I recently flashed the stock rom that is rooted with hsupa and sideloading enabled onto my Inspire, and over the last 2 days I've noticed that sometimes when I try to make a call, my phone just hangs up. It's weird, because text and data works perfectly fine, it's only when I make phone calls. Anyone else notice this problem with a rooted rom, stock or not?
Click to expand...
Click to collapse
I had this problem when I first rooted (running Inspire 4G Stock Rom w/Root, HSUPA, and Sideloading from the development section) I installed Android Revolution 2.1 and it went away.
I know from my captivate days that sometimes a ROM just hiccups and a fresh flash can fix the issues. I don't know if this is the same with HTC, but it's all android so It's plausible.
Something very weird just started happening with my SamChg.
When I am a few minutes into a phone call (about 3 - 4 minutes), all audio drops out on both sides of the call. The call is still connected, but neither side hears anything anymore.
I did a factory reset on the phone, but it didn't make a difference.
What can be causing this? If I can't use my smartphone as a phone, I'm screwed!
are you running any special ROM or anything because its happening to me as well
I have been having the same problem for almost a month now. I was rooted when this started happening. I went back stock still happened. New 4g card still happened. Another phone still happened. I have been getting the runaround from verizon the whole time they have no clue what is going on.
On a side note asked a friend that works at a little vzw store if they have seen this problem and sure enough she had. She told me that they had a customer go through 4 phones and she started making calls and was told by Customer Support that it was a known thing and there was a software update coming out for that.
After hearing this I called good ole *611 yet again and they were clueless and said they knew nothing about it. *sigh*
¿GotJazz? said:
Something very weird just started happening with my SamChg.
When I am a few minutes into a phone call (about 3 - 4 minutes), all audio drops out on both sides of the call. The call is still connected, but neither side hears anything anymore.
I did a factory reset on the phone, but it didn't make a difference.
What can be causing this? If I can't use my smartphone as a phone, I'm screwed!
Click to expand...
Click to collapse
What rom ???
Yorto said:
What rom ???
Click to expand...
Click to collapse
Umm can't even remember now was a month ago LOL. But my 2nd phone I didn't put one app on or anything left it bone stock and still had the same problem. Same as the customer my friend had they would mess up right out of the box.
probably weak antenna
no you don't lose signal call keeps running you lose Audio.
chiahead52 said:
are you running any special ROM or anything because its happening to me as well
Click to expand...
Click to collapse
Yorto said:
What rom ???
Click to expand...
Click to collapse
Yes, I am running a custom ROM, but it's basically a stock rooted & voodoo'd EE4 ROM (by danalo1979, I think). It's got all the yucky poo-brown colors and all the bloatware.
Same issue here. I'm running completely stock right now, non-rooted. Sometimes the audio will drop at the onset of placing a call (I won't even hear ringing) and sometimes it will happen a few minutes into a call. Other parties do say they can hear me though.
Personally, I've noticed that this problem only happens when I am also connected to a Wireless Network. If I'm running 4G/3G, sometimes I hear echos of my voice, but the audio won't drop out.
Weird, but glad to know others are having this issue and that VZW is aware it's happening.
What should we do? Personally, I'd like to wait for the SG2 to arrive before I start complaining. My plan would be to basically flip out explaining that I need my phone to work like a phone, etc. Then flip out that I paid for 4G and my decision was battery based (so I don't get stuck with a Thunderbolt). I bet I could talk my way into a new SG2 over this... Just saying.
KarateExplosion6 said:
Weird, but glad to know others are having this issue and that VZW is aware it's happening.
Click to expand...
Click to collapse
Well they do not tell me they know what is wrong they tell me they have no clue. I even explained to them somebody there does know as they have explained the issue to someone else that has had the problem but I still get they you just need another phone speel.
I don't have this problem watch as soon as I try to make a call the audio drops...
Sent from my Droid Charge running GummyFroyo 1.9.1
kvswim said:
I don't have this problem watch as soon as I try to make a call the audio drops...
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
same, don't have this problem but i probably just jinxed it.
I've had this happen a couple times too...hard to pinpoint consistency. The other thing I've encountered more than once, is that my mic seems to go off mid-conversation, e.g. I can still hear the person on the other end very clearly, but they can't hear me. Anyone else experience this?
Edvard_Greig said:
I've had this happen a couple times too...hard to pinpoint consistency. The other thing I've encountered more than once, is that my mic seems to go off mid-conversation, e.g. I can still hear the person on the other end very clearly, but they can't hear me. Anyone else experience this?
Click to expand...
Click to collapse
I've experienced that. But I'm not so sure I'm not just covering the mic with my finger.
I was on nluetooth, with the phone in the cupholder... Don't think my finger was involved.
Sent from my SCH-I510 using XDA App
Well 2nd Fru and as I told them it would. It does the same thing. Bone stock. *sigh*
One thing that seems odd to me is that I seem to see this problem more when calling another mobile phone vs. a landline.
Maybe it's just my imagination, but I always see problems when calling my wife's mobile phone. Last night, I called a landline for over an hour without any problem.
same here I can talk to customer service for 1hr+ but mobile to mobile most Ican get is maybe 15 min.
I drive around as part of my job and today I tested a call out to my wife who has a charge as well and we were able to talk for over 20 minutes with no issues. That same area I drove through a few days ago caused 3-4 drops in audio before. So in my opinion its a network related issue and hopefully its get fixed 100% cause most of us need our phones to work solidly
To the people losing audio during their calls, can you post your location?
The reason why I ask this is because on the Verizon forums there is an eight page post about this issue. Seems like a lot of people in Arizona are experiencing this. I'm in Chandler, Az and have this issue, especially when calling other VZW people in AZ.
Can't post links yet but check the VZW community forum for the Charge.
So I just got a Nexus S 4g on Monday and my dad and I already rooted the phone and have been trying different roms. He actually rooted it and swapped out the stock rom before I even knew I was getting it.
So with both of the roms I have tried, whenever i recieve an incoming call the speakerphone automatically activates and I have to manually turn it off.
We already tried reflashing the rom and we have also tried replacing a lib***.so file (forget which one) and neither fixed the problem. I cant find any sort of setting for this.
Anyone else having this problem? Is there a fix available that someone can guide me? Very new to Android so I'm still learning the tricks of flashing etc.
Just curious...did you test the phone before it was rooted.
Sent from my PC36100 using XDA Premium App
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
webhead1994 said:
I received the phone on monday evening and my dad had the phone all day and routed it etc.
I never handled the phone with the stock rom. Its not too big a deal since I don't use it for much calling but a fix would be greatly appreciated.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Well it seems like you don't know if this problem has always existed or if it is a result of flashing a custom rom. Best bet would be go back to completely stock and see if you still have the problem.
Sent from my PC36100 using XDA Premium App
Just flashed the new miui rom and it fixed the problem. Now I just have to redo my launcher lol.
Sent from my Nexus S 4G using XDA App
I'm having the same problem running a stock version of Android.
I started to have the same problem few days ago and my phone is all original stock, ,,
my wife just started experiencing this today. completely stock nexus s. we may try uninstalling the last few apps that had updates and see if we can trace it to one of those.
edit: are any of u using go sms (specifically version 3.66)? other users are complaining that recent update is causing this issue. im sending my wife a backed up version i have of 3.65 to see if its resolved
edit 2: rolling back to 3.65 did not resolve the issue, but rolling back to 3.64 did. good thing i have appmonster pro.....
I just started to have this problem today too. I did try to activate GoogleVoice yesterday but the calling issue did not begin until today. Running MATR1X v.6 and CM7 nightly #83. Didn't have this problem during stock.
Go sms's latest update is the culprit. The August 29 th update is responsible. Just uninstall that and put some other sms app.
Should solve it, It fixed my phone.
it happened to me twice yesterday, I answer the phone the screen went black and the sound routed to the speaker..can't go back to turn it off during the call as the screen has nothing. (stock rooted)...will uninstall GoSMSPro and see how it goes
If anyone needs/wants the 3.64 version of GO SMS, dm me you're email addy. (i'm assuming this would be ok on XDA since the app is FREE in the market?)
They (GoSMS) just released an update 3.66 to fix the problem
vennstrom said:
They (GoSMS) just released an update 3.66 to fix the problem
Click to expand...
Click to collapse
Its still exists on 3.66. My wife was using this version and it had the problem. We had to roll back to 3.64 before it went away.
u were right, Go SMS was the issue, they released an update today and solved the problem!
cheers everyone!
Glad I saw this thread... my G2 started doing this after not changing the ROM in months, at least now I know what caused it. I got my Nexus S yesterday and haven't answered any calls without the headset yet, lol, so I thought it was just my G2.
This is going to make me go back to GB. Custom ROMs and stock ICS, when I receive a call, it will display the number, but no name for a second to 10 seconds.
Why does it take ICS so long to query the contacts to match. Is there a fix for this?
There is a super annoying friend of mine that has several numbers and so help me if I accidentally pick up his call again, Im throwing this phone.
Ive stood behind my Nexus S and android, still want to love it, but ICS is just crap for now.
i noticed that too in SGN
blackhemi4x4 said:
This is going to make me go back to GB. Custom ROMs and stock ICS, when I receive a call, it will display the number, but no name for a second to 10 seconds.
Why does it take ICS so long to query the contacts to match. Is there a fix for this?
There is a super annoying friend of mine that has several numbers and so help me if I accidentally pick up his call again, Im throwing this phone.
Ive stood behind my Nexus S and android, still want to love it, but ICS is just crap for now.
Click to expand...
Click to collapse
x2, I thought it was just my phone...
I get the same thing on my phone. Never got the delay using Gingerbread.
Sent from my Nexus S using Tapatalk 2
I'm having this delays too!
But they usually don't exceed 2 seconds, nothing like the 10 seconds waiting time up there...
More often then not, its within a couple seconds for me, but a few times a week, it will just not display. And thanks to this issue, I had to talk to this person for over an hour.
I would love to know why this delay exists and if there is a fix. It happens on other phones too, not just the nexus s.
blackhemi4x4 said:
And thanks to this issue, I had to talk to this person for over an hour.
Click to expand...
Click to collapse
I always let the call go straight to voice mail if I don't recognize it. That's funny to read though.
Sent from my Transformer TF101 using Tapatalk 2
yeah it really is a PIA
Same here, thought last ISC update might have fixed it a bit but delays still happen. In fact my nexus S is much slower with ICS. With Gingerbread I never experienced any lags of any sort.
Same here.... Pretty annoying ****
Sent from my Nexus S using xda premium
Ever since day one (start of August or so) I've been having a few problems with this phone. At first, I thought it was just the network or maybe the recipient's network. Then I realize it may very well be the Blaze itself.
The problem I'm facing is this...
Almost every time I try to make a phone call I can't hear anything. No dialing sound audio. No person on the other line... just nothing. The phone does go through, but I can't hear anything. I don't use any BlueTooth device. I have to wait several minutes or reboot my phone several times in order for the calls the work properly. This issues has been going on from GB (stock, no root) to ICS (stock, no root) until now that I'm flashing the phone to see if I can fix it (currently using PA's latest version as ROM). I thought the updated radio from ICS would fix it but to no avail. Goes to say, this issue happens to my father, too (same phone, got them for free when we started the contract).
This has caused an annoyance for both me and for friends.
Anybody else experiencing this? Any ideas as to why this happens?
IDK if this helps but I'm from Puerto Rico.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Same here!!!! I'm in California and on stock rooted ICS
Sent from my SGH-T769 using xda app-developers app
---------- Post added at 08:22 PM ---------- Previous post was at 08:13 PM ----------
It happens to me but not my brothers who have the same phone... They are on stock GB tho
Sent from my SGH-T769 using xda app-developers app
Tell you what, I have been having the same problem. Make sure you call tmobile and complain! They are telling me that this is not a known issue and there are no complaints on it. I had a detailed complaint filed. I sent my phone back, got another one and it is worse than the first with this issue! Another strange thing is that it will suddenly make doubles of my custom ringtones and one of the files doesn't work. It defaults to generic ringtone. Very glitchy. Sometimes, will still show that the custom notification tone is selected but will play default tone. I am sending this one back too. I am really bummed to hear that rooting did not fix the issue on the phone calls. I was actually considering doing this next...... Really hope the next phone doesn't have this issue. I like the Blaze and don't know of another tmobile phone that is comparable to replace it with.
ditto
I have the same problem I believe. I currently dorm near the Bay Area, California. I haven't been able to hear or reply through my calls even though they connect to the other person's phone. This isn't exactly a signal problem because the phone still has bars and I can still tell when someone is trying to call me. I still receive texts, use wifi, and sound is working perfectly fine. I am glad I am not the only one with these problems.
edit: This whole "unable to hear or speak" into the mobile phone problem began around November 22nd (thanksgiving overload?).
I am using CyanogenMod 9, rooted of course.
edit2: So I just tinkered around with the sim card and battery by taking it out and waiting for a minute or two before putting it back in. Voila! I can now hear my voice mail.
Sounds like Handset issues with me... send them back and have them send you new ones... that's some BS if it is doing that Stock.
Just my opinion... being through a lot of phone and that is what it sounds like. just one mans opinion... cheers
anoontm said:
I have the same problem I believe. I currently dorm near the Bay Area, California. I haven't been able to hear or reply through my calls even though they connect to the other person's phone. This isn't exactly a signal problem because the phone still has bars and I can still tell when someone is trying to call me. I still receive texts, use wifi, and sound is working perfectly fine. I am glad I am not the only one with these problems.
edit: This whole "unable to hear or speak" into the mobile phone problem began around November 22nd (thanksgiving overload?).
I am using CyanogenMod 9, rooted of course.
edit2: So I just tinkered around with the sim card and battery by taking it out and waiting for a minute or two before putting it back in. Voila! I can now hear my voice mail.
Click to expand...
Click to collapse
I live in the Bay Area too and I have the same problem. It has been gone gone since before Thanksgiving though. Any help would be great thanks.
Sent from my SGH-T769 using xda app-developers app
I would be better off getting a new, better phone, it seems. It is quite annoying. Either way I voided my warranty by flashing. I don't suppose I can actually return it back to stock (like, literally returning to stock and unrooting and wiping and formatting every data) so I can still give it back... can I?
PS: Thanks for the replies.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
DarkDragonPR said:
I would be better off getting a new, better phone, it seems. It is quite annoying. Either way I voided my warranty by flashing. I don't suppose I can actually return it back to stock (like, literally returning to stock and unrooting and wiping and formatting every data) so I can still give it back... can I?
PS: Thanks for the replies.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
See the 'return to stock Odin thread' in the dev section. You will also need to flash the flash counter reset from the themes section.
Sent from my SGH-T769 using xda app-developers app
eggytoasty said:
Sounds like Handset issues with me... send them back and have them send you new ones... that's some BS if it is doing that Stock.
Just my opinion... being through a lot of phone and that is what it sounds like. just one mans opinion... cheers
Click to expand...
Click to collapse
I got my third phone from tmobile the other day (all Blaze) and my very first phone call it happened on. To add to what someone else said. The phone shows plenty of signal strength and in fact, if I hang up and call right back the call goes through as it should. This from sitting in the exact same spot. I can't figure out what's going on? I had thought on this and realized that I had been turning off apps on the phone that I don't use (pre loaded junk). On the off chance that had something to do with it I turned them all back on. Still does it. I'd say it is a good 30-35% of my calls that this happens on. Very frustrating. I really like this phone but it won't function as a phone for me. I guess now they have to give me a different phone if I return this one too but I don't know what phone is comparable in size and function. I picked this phone specifically for the size. My wife got an s3 and I was not interested in it at all due to how big it is. This sucks.
I have to chime in. i just bought the blaze for my g/f, and i've using an sgh-t989 (galaxy s2), having the same issue you are describing. stock radio, stock ROM, just rooted.
Such a shame considering it is such a great phone for the price it is offered at. Safe to assume it is a hardware problem?
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
NetrixTardis said:
I have to chime in. i just bought the blaze for my g/f, and i've using an sgh-t989 (galaxy s2), having the same issue you are describing. stock radio, stock ROM, just rooted.
Click to expand...
Click to collapse
Are you saying that you are having this problem with the blaze or the s2? Both?
Both phone are having this behavior. new SIM used in both phones aswell.
Yeah, I went down and switched out my sim card as well. My wife has an s3 and has no problems so I don't know what's up? Shows signal but calls won't connect properly. Hang up and call back, it works. Huge pain when I am driving or short on time though.
Any fix this problem found? I talked to samsung and t-mobile today, samsung was no help at all and t-mobile asked me to master reset it. Once that didn't work they offered a warranty exchange. Any one have luck correcting the issue?
So far? No. But my phone seems to be behaving for the past few days (3). Which is weird. I'm probably jinxing it right now.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Restart during a call, the handset will not send sound.
Maybe they got a bad batch of Blaze 4G's. NOT making an excuse for them but I know it's happened in this business and others.... If I were u I wouldn't keep on dealing, hats to your patience. Let know where you're at. I've flashed to CM 10 nightly 20121207 and my Blaze is just damn sexy lmao, "figure of speech" good luck brought cheers
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
DarkDragonPR said:
So far? No. But my phone seems to be behaving for the past few days (3). Which is weird. I'm probably jinxing it right now.
Sent from my SAMSUNG-SGH-T769 using xda app-developers app
Click to expand...
Click to collapse
Same here
NetrixTardis said:
Both phone are having this behavior. new SIM used in both phones aswell.
Click to expand...
Click to collapse
Whas ROM are you using? ICS and gingerbread have a call preference switch in settings. Set it to data preferred. Cm 10 has a lte switch in settings use it. Battery apps can cause delay in data connect. Try these and let me know how it works.