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.
Related
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
Getting tried of watching my phone reboot. If going back to stock would resolve the issue I would do it. I called big red today and the pinhead I spoke to acted like it was the first time anyone had called about the TB rebooting on it's own. I'm looking at going to a different phone. I really think at this point it is a software issue that they need to correct. Just like with most businesses things are not addressed until they become a problem. So my thought is we should set a date when every one calls in to report their rebooting phones. We do this every week until we get a resolution. Anyone with me?
Wait... You are rooted and getting reboots? Are you on gb? Did you root or install your rom properly? What kernel?
Stock I had no issues. Non-Gb I've had mostly no issues... Some kernels less reliable than others, of course. But to be honest it sounds more like a user issue than a tb issue
Sent from my ADR6400L using XDA App
Sent from my ADR6400L using XDA App
Are you near a Verizon store? Verizon is usually very easy to convince that you need your phone replaced. (Although I think they will only replace it with the same model. But I'm not sure.) My Thunderbolt never reboots on its own but I know it is a problem that many Thunderbolts are experiencing, so maybe yours (and many others) is/are defective. I'm 99% sure if you go into a Verizon store and tell them that it randomly reboots all the time, they'll replace it for you.
I reverted back to stock and haven't had a single reboot or loss of data on three days. Just sayin'.
Sent from my ADR6400L using XDA App
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Funny how VZW is changing their stance on it, almost as if it never has happened. About a month ago I went into a store and they told me that Im not the only one experiencing problems and that there will be a fix within 2 months.
I called VZW tech support and they told me that no one else is having reboots.. . . . I dont get it.
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
sethschmautz said:
Can you specify what you mean when you say "both"? I have been getting reboots too - approximately 1 per day - but is there a process to flash each radio independently?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
No, but each flash has two radios
Sent from my ThunderBolt using XDA Premium App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
Any issues with tethering or gps using the old radios?
Sent from my ADR6400L using XDA App
Silvus said:
Try flashing your radios, I put both of mine to .6 and the reboots stopped.
(there is a thread in teh development forum, with the packages)
Click to expand...
Click to collapse
I still had reboots with both at .6, currently trying cdma.7/LTE.6.
Sent from my ADR6400L using Tapatalk
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
satseaker said:
It is a hardware issue,that's where the few pricked phone came from,my original bolt had the reboot loop on stock but no one seems to want to hear that,it is a series of phones having the trouble and they are or have replaced most of them,as far as most of the other reboot go that is self made misery by not following directions or not reading to find the fix, this bolt I have now has no reboot issues and it has a mat finish to it,the other one and a few I have seen that had issues had a smooth glossy finish.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I would love to think its a hardware issue, but my phone was solid from day one. Then I took the update and get these random reboot.
Sent from my ADR6400L using XDA App
It is not a hardware issue. It is a problem with the update and how certain phones installed it. Verizon is in the process of making a new update and has been working on it with HTC for a little while now & expect to have it going out this month. For some reason the software does not talk to the towers properly with some models & the hardware does not get the proper info which causes the reboots. Exactly how to tell which phones are affected, I don't know. My friend is trying to find out for me.
I can say that I ran my phone with rooted stock & moved up to the rooted update when it was available which I am still on and I have not had any issues at all besides the low recorded video audio which the update seems to have fixed for me.
My phone is:
Rooted stock & radios w/update
Adrynelynes 4.47 Kernal
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
I didn't do the update over the air on my other bolt, I downloaded it from HTC and it killed the phone,but the same download is on this phone and it works just fine,not one reboot, and its still stock and not rooted. The other one was dated Dec
10 and this one is dated Feb 11, I would just about guess they tweaked the update to weed out the bad phones faster,makes sense to me.
Sent from my ADR6400L using XDA Premium App
satseaker said:
I am telling you what HTC said they admit that a certain series is defective hence the snappy replacement. Just cause one Rom works and another doesn't isn't always the Roms fault,ever had a CPU that would run one OS and not another or RAM that worked fine on xp but not win 7 once the defective hard hits its limit it will fail. I have seen hardware work fine overclocked and the exact same hardware crash with half the settings,or a motherboard run suse fine but put Windows on it and it dies a week later. I didn't say they all were defective just one series of them and when they did the update a lot of the phones started to fail and some didn't,so does that tell you hardware or software,if one can run fine and the other fails its either a bad flash or bad hardware. Take your pick
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I wasn't aware of HTC stating there was some defective hardware. Never saw any references to it. If thats the case then glad they acknowledged it.
It's definitely not a hardware issue. Its a radio/ signal issue. Verizon does know about it, and is working on getting a new update out there. I know this, for a fact.
Sent from my ADR6400L using XDA App
jett2314 said:
I have read posts where people who are not rooted are getting reboots after they took the update. Have never had an issue with my phone until I took the update. Am going back to stock for a week or so to see if that clears things up.
Click to expand...
Click to collapse
My TBolt is not rooted and before the update I had no problems at all but after the update the random reboots started. Battery life is acceptable but could be allot better.
Called Verizon yesterday and they acknowledge the problem and actually said HTC is aware of the problem and are working on it but have no expected date as to when it will be fixed. I believe it is definitely is a software issue and will be fixed when the official Gingerbread is released. Just my 2 cents.
I've been reading up on this and I'm to the point where I'm contemplating having Verizon send me a nightmare... I mean refurbished device.
How many people are having loud static in calls (randomly)? I'm not talking about a bad signal or something that's only happened to you once. I'm saying a straight up 90% of your calls your ear drum is about to explode because the static just suddenly pops up and is 5x louder than the conversation you're having with the person on the other line.
If you're experiencing this, have you been able to fix it?
I read/tried
-New radio
-New 4G SIM card
-Min CPU to 200mhz
-and more that I cant even remember off the top of my head
Basically I'm trying to see if people are experiencing this across the board, or if I might get lucky with a refurb from Verizon (as this is my absolute LAST resort, seeing as I've never received a working Verizon refurb).
I too have this problem. No solution yet.
Yeap, known issue with the phone. I recently contacted Vzw about the issue and they told me that Samsung knows about the issue and there currently isn't a fix available.
They offered me a completely different replacement device.
I voted no. I have heard it before, but it's not a common occurance, and I haven't had it at all in the last two or three leaks.
Never once had it
Sent from my SCH-I510 using xda premium
I have it. I'm currently on humble 5.0. Although its not as often as other gb leaks, it does happen. I find it to occur when screen dimms during call or if I pull the phone away from my ear and the screen turns on. The only setup the static noise did not occur is stock froyo.
I think many of us with this issue are waiting for the official update. If the static noise continues then I will contact Verizon for a replacement.
Oh and this charge is a refurbished phone that was exchanged for my crappy fascinate.
Sent from my SCH-I510 using XDA App
I had never thought of the screen turning off being the issue. My Touchpad has an issue with sound when the screen goes off. Hrmm... Maybe something to force the screen to stay on would resolve it.
I've narrowed this problem down.
Using GB Roms prior to EP4 this always happened, even with EE4 Radio. It also happened with EP4 radio but EP1/2/3 Base.
Therefore the problem is isolated to the EP1/2/3 base software.
I then isolated it to the dialer application itself. The fault occurs in Dialertabactivity or phone.apk.
If you pull the phone.apk or dialertabactivity.apk from stock EP4, this will go away for most phones.
Hmm want to see if anyone else has tried this.
Umm if you do this you will not be able to dial and utilize the phone. So yeah it will get rid of static because you won't be able to make a call hahab
cmdrfrog said:
I've narrowed this problem down.
Using GB Roms prior to EP4 this always happened, even with EE4 Radio. It also happened with EP4 radio but EP1/2/3 Base.
Therefore the problem is isolated to the EP1/2/3 base software.
I then isolated it to the dialer application itself. The fault occurs in Dialertabactivity or phone.apk.
If you pull the phone.apk or dialertabactivity.apk from stock EP4, this will go away for most phones.
Click to expand...
Click to collapse
Sent from my SCH-I510 using XDA App
Incorrect. You can push the ep4 versions of the apks using adb and it will work. I've tested.
Sent from my SCH-I510 using Tapatalk
I think there must be a bunch of defective phones out there doing this. I have never once had this happen to me, but I do way more texting than actual talking on the phone.
The business owner where I work is the exact opposite however. He is one of those guys who walks around with his phone constantly glued to his ear (he has 4 Gorilla batteries) & it has never happened to him either.
I asked him about it yesterday & he had no clue what I was even talking about.
~John
What I've noticed isnt so much a blaring of static as the other person im talking to sounding like they are trying to talk through a muffled microphone. Something like they have the microphone on their phone wrapped in a sweater and they are trying to talk through it. I cant understand half of the people I talk to.
I had this problem but the recent leaked OTA update: http://forum.xda-developers.com/showthread.php?t=1364298 fixed it for me. It's the first time anything gingerbread has been on my phone without the issue. A 15min call to my gf after the update produced a clean call with no deafening static/popping/crackling. I was worried for a second though cause she started unwrapping xmas decorations that were wrapped in tissue paper. There's a full odin of the EP4D release here: http://forum.xda-developers.com/showthread.php?t=1365376 should resolve the issue for those not running stock EE4 (though I haven't tested this yet, if you do use it report back if it works).
Also check out this thread for not only a cwm version of the OTA ep4d but also a modem updater file that can patch your modems to EP4D - they just need to be EE4 prior to flashing.
So I used the odin of the debloated/deodexed/rooted ep4d (the one I posted in my original response above, created by danalo) last night, first call I make today I get the static.
Sucks!!
mhemu said:
So I used the odin of the debloated/deodexed/rooted ep4d (the one I posted in my original response above, created by danalo) last night, first call I make today I get the static.
Click to expand...
Click to collapse
Sent from my SCH-I510 using XDA App
I went back to stock, going to see if the over the air works. So far the only resolution is to go back to stock and the manually run the update to ep4d.
Sent from my SCH-I510 using XDA App
mhemu said:
I went back to stock, going to see if the over the air works. So far the only resolution is to go back to stock and the manually run the update to ep4d.
Sent from my SCH-I510 using XDA App
Click to expand...
Click to collapse
So, got the static after going to stock and doing the manual update...wtf. Decided to go back to stock and see if the OTA was ready...it was...got static...wtf.
Looks like I will be getting in touch with Verizon and see what my options are, sounds like some other people with the issue have had verizon admit there's an issue and have been compensated. I won't go into the details of what others have done, but I will say I don't plan on giving them more money than I already did for this phone. I'll report back when I have a resolution.
Ya its allot better but definitely still there. I was really hopping this would get fixed and at first it seemed good but after a few calls I got the static. I'm not sure what to do with it now. I've gone back to completely stock and took the update and it's still there.
Sent from my SCH-I510 using xda premium
Hey guys, I've had my HTC One S for T-Mobile and ive had it for about 1 week and it has rebooted on me twice so far. not sure why. the first time it was in my pocket and i heard the T-Mobile boot up animation sound go off in my pocket and pulled it out my phone to see it was just booting up for some reason. then today i was going to look at my friendstream widget (on my home screen) and my phone locked up for a second and then rebooted itself. i'm not happy about it since i once owned a g2x which rebooted like crazy. i'm hoping it stops randomly doing this crap but i reported it to HTC since it gave me the option once it rebooted. my HTC one s is rooted with the stock rom with bloatware removed and carry IQ removed. i just wanted to see if i'm the only one having this issue.
It happens to me too :/ sometimes i wake up in the morning and i see the HTC error message. Maybe a software issue?
coronangel said:
It happens to me too :/ sometimes i wake up in the morning and i see the HTC error message. Maybe a software issue?
Click to expand...
Click to collapse
not sure why it does this. i just wanted to make sure i wasnt the only one having this issue. but i do hope its a software issue. i keep reporting it to htc when it ask me to send them the error or whatever it says. maybe htc will fix it
I had like two reboots, but then I updated the phone and the problems disappeared. Have you updated to the latest firmware ?
Sent from my HTC One S using XDA
Habarug said:
I had like two reboots, but then I updated the phone and the problems disappeared. Have you updated to the latest firmware ?
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
i dont think there is an update for the tmobile htc one s.
Two days since I bought it and already rebooted two times when exiting the mail client while network was switching from H to 3G. I upgraded it to the latest firmware OTA just after putting the SIM card into.
My son had a problem with random reboots. After enabling Best Wifi Performance in Wifi, advanced settings, they went away. This is on a TMOUS version. Could be totally unrelated to your issue, but worth a try. I've noticed that the wifi has some weirdness to it, like hanging on to a connection long after it's out of range. I hope there is a software update soon.
Sent from my HTC VLE_U
well i hope htc can fix this issue. it hasnt happened again yet. i also have the tmobile htc one s.
s10shane said:
i dont think there is an update for the tmobile htc one s.
Click to expand...
Click to collapse
I don't have tmob version and mine is on 1.78. It was that update which fixed it, it seems. You did an update search right?
Sent from my HTC One S using XDA
Habarug said:
I don't have tmob version and mine is on 1.78. It was that update which fixed it, it seems. You did an update search right?
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
Mine is also on 1.78 but had 2 reboots.
Habarug said:
I don't have tmob version and mine is on 1.78. It was that update which fixed it, it seems. You did an update search right?
Sent from my HTC One S using XDA
Click to expand...
Click to collapse
yeah i guess here in the US we havent got an ota update that i know of. i kept checking for updates but it said my one s is up to date.
Another reboot this morning. This time I received a txt thru Facebook Messenger. I saw it on my desktop and ear, exactly at the same time, the HTC One S rebooting. This might be app related this time.
My One S specs:
- EU edition
- Stock ROM, 1.78 OTA
- Wifi disabled
Yes my H1S reboots about 3 times a week, or the "Loading ..." window is seens 3 or 4 times a week as well.
one more time... I'm gonna consider switching to another ROM in a very near future.
rebooting on 1.78 stock and other custom roms too
Hi guys, I had this issue with stock rom on 1.78 and previous too, so it is probably a radio issue. If I am connected to my wifi network at home, then I go out, the phone switches to hsdpa (as it should) and then I come back home,the reconnection to the wifi network causes the phone to reboot.
I had this issue on all roms I used, both stock and trickdroid 3.1 / 4.3.
My wifi direct is already disabled, my location is Italy. I have seen also that people on the US T-mobile support webpage are complaining about something very similar, wifi related.
Thanks
I'm on tmous and have had two of these reboots since I got the phone on US release day.
As others have said, mine have only happened when I'm on the very edge of my WiFi coverage. It's like the phone can't decide which network to grab on to and freaks out. I don't have the issue when it's just normally switching from WiFi to data like when I go out and then come home. It only seems to happen when I'm right on the edge of WiFi for a few minutes.
Not a huge deal, since its only happened a couple of times. If I remember when I'm off this week, i'll try to get a logcat because I should be able to reproduce it at the edge of my back yard
that would be great, as it sounds like it is the same issue. I always found tricky to save logcats due to amount of information in them and spotting the exact reason for crashing.
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.