Phone calls not working after new firmware - T-Mobile Samsung Galaxy S 4

After upgrading to the FOH3 firmware and then flashing on TWRP and Cyanogenmod 12.1 nightly, my phone worked great for days. One day for no apparent reason I could no longer transmit audio when making phone calls on the default phone app. It will connect, and disconnect if the other party hangs up. My speaker, mic, and 4g are working.
I wiped everything TWRP lets me besides MicroSD.
I tried a firmware double-flash and using clean stock install.
I went as far as T-mobile support can.
I'm looking to see if there is a more comprehensive wipe I can do. Perhaps the error exists in an area TWRP doesn't reach. Please give me any ideas.

Related

[Q] Camera and headphone jack don't work despite updating radios and switching ROMs

This happened all of a sudden, and I'm really not sure why. The camera is just a black screen, which can only be minimised by pressing the home button. The headphone jack recognises nothing.
At first I thought it was the ROM (LeeDroid 2.2f), so I wiped the data/cache/dalvik cache and reverted to Pinky's 1.8. I've also tried AuraxTSense 8.1.4 with no luck. All ROMs work perfectly fine except this issue.
After looking it up, everyone seems to jump at the radios. I flash radios by picking the zip file whilst in recovery (clockwork), installing, rebooting and having it write the image, not touching my phone while it boots up, and having it show the new flashed radio in the options/bootloader sections.
I have tried the specific radios linked to in the OP of each of the ROMs, and I have tried the latest ones. I've been through about 5 at least today on multiple ROMs, with no luck.
I really want my camera and headphone jack back. Please help.
Try going back to stock rom. If that doesn't solve it, then I think you have a hardware problem.
I'm currently trying a rooted version of 2.10.405.2 including radio from this thread. Is that sufficient testing of going back to stock (because my backup software requires root) or does it have to be RUU?
Edit: That rooted stock ROM has the same issue -_- will try RUU.
Edit 2: The flash LED no longer works either. For example the torch application.
The camera app is still just a black screen. No menu, no way to quit except terminating the process.
The headphone socket is still dead. The halfway-in trick doesn't work either.
These parts are all very close to each other, so I'm leaning towards hardware. However the phone can still make/receive calls, messages, wifi, 3G, etc... everything apart from camera, rear LED and headphones.
This seems to happen a lot according to Google. Will think twice about getting another HTC phone.

Plenty of problems

I currently am running the latest Hotfire (4.4.2) rom, but do not believe my issues are from it because I have run at lease 8 different roms, and am having issues with them all, basically when I flashed the latest firmware (4.3), and the latest modem (UVUEMJC).
With this rom, I am having problems making calls, either through wifi, or network. On network calling, it says connected, but I don't have any sound coming through the headset or speaker. When I try to make a wifi call using either Talkatone or grooveIP, I get the same issue except using Talkatone, there's a pop up error message saying it cannot initialize the call. The app then resets itself, but then the phone reboots.
I am also having issues where when I try to drop down the status bar (I'm using the latest Nova Prime launcher), it won't drop, nor can I make it or the dock disappear. I can move from page to page, though only a few times. Then the phone completely freezes, and I have to do a battery pull.
I did not encounter these issues until I flashed the latest firmware and modem. Now, even roms I used before that were completely stable, are no longer reliable. I have tried to Odin a couple times, redownloading the firmware & modem to make sure I had stable files, but have the same issues. I have also did an Odin, then reinstalled my apps one at a time without data, then put the data back one at a time. No luck.
Any thoughts or help with this would be appreciated.
Forgot to mention I am running tmo S3.
Sent from my Xoom using a Starfleet secured channel
I was having weird problems once. I actually formatted the whole system using the stock android recovery (i think that's what I used). Internal storage and all before I Odined and re-rooted. Hope that gives you some ideas. Good Luck.

[Q] Cyanogenmod Glitches

I am currently running Cyanogenmod 10.2.1 on my Sprint GS3. I am running into a few issues, of which I have had over many builds. For one, my phone will random reboot when using it, while it happens rarely, it seems to do it at the most inconvenient times and I am left waiting for it to reboot for no reason. The next, and definitely most annoying glitch, is the "disconnect reconnect" issue with PCs. When connected to a PC, it repeatedly disconnects and reconnects and never stops this loop. I hear the disconnect/connect sound over and over until I actually disconnect the phone. Because of this, I am unable to add new music, photos, etc. At first I thought it was just the current build, but after updating to 10.2.1 from 10.2.0, and so on, nothing has really changed. I'm not sure what to do at this point other than just go back to the factory ROM. If any of you have any idea why this may be happening, let me know. Thanks in advanced.
hotelmariofan said:
I am currently running Cyanogenmod 10.2.1 on my Sprint GS3. I am running into a few issues, of which I have had over many builds. For one, my phone will random reboot when using it, while it happens rarely, it seems to do it at the most inconvenient times and I am left waiting for it to reboot for no reason. The next, and definitely most annoying glitch, is the "disconnect reconnect" issue with PCs. When connected to a PC, it repeatedly disconnects and reconnects and never stops this loop. I hear the disconnect/connect sound over and over until I actually disconnect the phone. Because of this, I am unable to add new music, photos, etc. At first I thought it was just the current build, but after updating to 10.2.1 from 10.2.0, and so on, nothing has really changed. I'm not sure what to do at this point other than just go back to the factory ROM. If any of you have any idea why this may be happening, let me know. Thanks in advanced.
Click to expand...
Click to collapse
That's an interesting experience, which I haven't had so far.
Did you dirty flash the rom or completely wiped your phone before installing?
Which modem version are you on?
Robbie Doo said:
That's an interesting experience, which I haven't had so far.
Did you dirty flash the rom or completely wiped your phone before installing?
Which modem version are you on?
Click to expand...
Click to collapse
I don't format the phone between cyanogenmod updates, but I do when installing a completely different ROM (factory -> Cyanogenmod). As far as the modem version goes, as of now, I am running LJ7. I believe that was on there by default, although I may be wrong. I did try others before (If I remember right) installing the original. I tend to have horrible reception in KC (everywhere actually), so I was hoping to fix it that way.
hotelmariofan said:
I don't format the phone between cyanogenmod updates, but I do when installing a completely different ROM (factory -> Cyanogenmod). As far as the modem version goes, as of now, I am running LJ7. I believe that was on there by default, although I may be wrong. I did try others before (If I remember right) installing the original. I tend to have horrible reception in KC (everywhere actually), so I was hoping to fix it that way.
Click to expand...
Click to collapse
You're right, there's no need for completely formatting the phone between nightlies. However, your modem seems to be an older version. I believe the CM 10 based on MD4 and the CM 11 is based on MK3. You can verify this in their respective forums though.
My suggestion would be to download the latest modem and the CM 11 onto an external card. Format your phone completely. Install the modem then install the CM 11 + KK Gapps.
Let us know how it went if you go through it.

[Q] CM11 No Sound/Mic, Force Closes, Etc

Hello fellow XDAers,
I recently went through the flash dance for my Sprint Blue L710 S3 16GB to switch it from some old version of CM 10(.2?) to the latest nightly of CM11. I essentially followed this guide to get my phone up to the latest and greatest and flashed pa_gapps-modular-micro-4.4.4-20141110 to give the the level of GApps I'm comfortable with.
Now I tried to follow the same guide with my wife's Sprint "White" S3 32GB L710. Right off the bat the phone wouldn't boot after the oneclick flash - it got stuck on the loading screen (I waited 30 minutes on the boot screen before giving up... twice). Only after I flashed Philz 6.5.14 recovery was it able to properly boot into the OS (potentially a PIT problem, but all 32GB PIT files seem to be removed from the web). In the stock ROM, phone mic, sound, voice dialer, and Google Search all worked (and I tested this several times during recovery attempts). It noticed it hadn't taken advantage of all 32GB available on the phone, so it decided to expand the partition itself (bonus?). Then I flashed the latest nightly CM11...
Once booted, I cannot get the dialer to behave correctly. I installed the GApps after booting up the ROM once (and tried again on a fresh install by installing it prior to first boot). Immediately after boot, using the Phone app and dialing a number the screen turns to a blank (black) screen. The phone dials fine, but once connected to the number being dialed, there is no sound or mic. When I open the Sound Recorder app, it says "internal application error" and "microphone may be in use". When I try to do "OK, Google", it acts like the microphone isn't able to be accessed. When I open Apollo to listen to anything, DSP Manager force closes. It's as if the hardware can't be accessed by the ROM. SMS, cell network, WiFi, and GPS all work. It seems familiar to this CM thread, but the same steps aren't working for me.
I've flashed a few ROMs based off of AOSP (Slim and AOKP mainly), but none of them seem to allow me to utilize the mic and speaker of the phone. Only ROMs based directly off of sto k ND8 let me "phone out". For instance, stock ND8 works as well as Wicked-X.
I've flashed multiple ways, cleaned/formatted several times, and tried all sorts of tricks to get this to work on my wife's phone. I'd like to believe I've done enough research to feel like coming to the community is my last resort. As a software developer myself, I know there's probably something simple I've missed, but can someone please help me figure out why my "blue" L710 is working but not my wife's "white" 710?
Thank you very much in advance.

Problems with audio in calls from handset since changing to 5.0gpe

sorry if this is abit long winded,
hey everyone, not sure whats going on here. this is the tmob variant but i had moved over to a gt-i9505 rom dandroids stock gpe 5.0 back almost a month ago, this was upgraded from jamals 4.4.4 gpe which was working great. i installed the googly 1.2.3d kernel and that was also working well. i noticed that i forgot to fully reset all my storage and noticed jamal brought out a 5.0 rom so i swaped to that and wiped everything about a week ago and at first didint notice any issues.
then i recived a call and answered it on the handset and for the first few mins it was working fine all of a sudden something glitched and i had no audio like the call droped i hung up called back no audio. reset the phone same thing. just a day before this happened i updated the kernel to 1.2.5 googly for gpe5, so i figure this is it so i reflash and reset storage and no change. oddly this entire time there have been no problems with calls when using my bluetooth headset.
long story short i have installed and wiped one about 3 different roms including the dandroid that was working ok. i am now all the way back to the 4.4.4 jamal rom that i was on before i started and the problem is persisting. when i call someone the other party hears a high pitch squealing sound but only via the handset the "ok google" is working fine. i have not restored the nandroid backup yet.
baseband is m919uvufnb4
i have the current version of the twrp as what i have been installing everything from.
happy to provide more info. i know im still on the pre knox bootloader
and when i get home im going to try my wife sim see if that changes anything.
Update
Wife's sim changed nothing
Also wanted to say that I also read about a apn reset trick that was supposed to help. I did fix it one time but it recurred again and and since stopped working
Having that same issue gpe 9505 5.0 no audio in calls unless I'm using Bluetooth no handset no speaker
You guys Ned to update your bootloader and everything will be fixed.
You can only get so far with ancient bootloaders before the wheels come off.
Pp.
How do you do that
You need to Odin the latest version NK2, you can find it in general section, ShinySide has a mega link to download firmware.
Follow instructions and you will have a S4 that works properly.
You can use chainfire's auto root in original development to root.
Pp.

Categories

Resources