I've been getting complaints about static and echo from my end during phone calls. Could this be a radio issue? Am I on the latest radio?
71CH said:
I've been getting complaints about static and echo from my end during phone calls. Could this be a radio issue? Am I on the latest radio?
Click to expand...
Click to collapse
No, that's not the latest radio, they are all posted together.
I would suggest updating firmware, which includes the 1.13.41.0109_2 radio, which are also posted separately here.
I successfully updated the radio but there is still a horrible background static. My end of the conversation is fine. It's the other end that's no good. And I know it's not their phone because this is happening to everyone I talk to.
Any suggestions? Thanks.
71CH said:
I successfully updated the radio but there is still a horrible background static. My end of the conversation is fine. It's the other end that's no good. And I know it's not their phone because this is happening to everyone I talk to.
Any suggestions? Thanks.
Click to expand...
Click to collapse
Have you tried different roms to see if it is replicated on more than one? If you haven't, I'd flash a couple to see if it goes away. Or perhaps an ruu to reset.
Sent from my Lunar Ecliptic One.
If all you did was update the radio, I highly advise updating firmware as well.
It includes modem/radio related files that go with those radios.
For optimal results, you need the firmware as well as the radios, as I suggested above.
Sent from my HTC6525LVW using Tapatalk
I updated to the latest everything and I still have this problem. I did a quick google search and it seems that it could be the noise canceling software? or a faulty mic? It's weird because this issue happened suddenly.
Also, when I'm on speakerphone people say I sound crystal clear. It's only when I'm using it like a regular phone that they hear lots of static.
Does anybody have a good link to going back to s-on and stock? I might have to do an exchange. I have hoot 1.56. Thanks.
71CH said:
I updated to the latest everything and I still have this problem. I did a quick google search and it seems that it could be the noise canceling software? or a faulty mic? It's weird because this issue happened suddenly.
Also, when I'm on speakerphone people say I sound crystal clear. It's only when I'm using it like a regular phone that they hear lots of static.
Does anybody have a good link to going back to s-on and stock? I might have to do an exchange. I have hoot 1.56. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2475216
Also, graythewolf has a good video of doing it. I actually used that guide and his video when I sent mine in. Good luck.
Sent from my Lunar Ecliptic One.
I successfully got back to stock and installed all the updates. I don't seem to have the stock recovery however. When I try to boot into recovery it just turns black. Any suggestions? Thanks.
71CH said:
I successfully got back to stock and installed all the updates. I don't seem to have the stock recovery however. When I try to boot into recovery it just turns black. Any suggestions? Thanks.
Click to expand...
Click to collapse
Are you doing that from bootloader? Santod usually posts the stock recoveries...but I don't see the latest in his thread. You might want to ask someone who pulled the ota ruu.
Sent from my Lunar Ecliptic One.
brymaster5000 said:
Are you doing that from bootloader? Santos usually posts the stock recoveries...but I don't see the latest in his thread. You might want to ask someone who pulled the ota ruu.
Sent from my Lunar Ecliptic One.
Click to expand...
Click to collapse
Yes I'm trying to get in from bootloader. It goes black and then a picture of a HTC One appears with a red triangle and exclamation point in the middle.
Is 3.11.605.1_recovery.img from http://forum.xda-developers.com/devdb/project/dl/?id=3992 the latest stock recovery? I'm wondering if it should be 4.10.605.3
Thanks.
Nevermind. The red triangle IS stock recovery apparently. Thanks for all the help.
Related
Any ideas?
During a phone call it will sometimes mute my end. I can hear the other person trying to talk to me but they can't hear me. Trying to turn the screen on does nothing, it wont go back on until the call is over. This even happens if speakerphone is on and the phone sitting on a desk.
7.1 Cyan stable, standard kernel, Amon recovery.
Try updating your phone's radio.
Concordium said:
Try updating your phone's radio.
Click to expand...
Click to collapse
There are so many choices for that. What's considered the safest and most stable of the radio update files? I dont need fancy, just one that is considered working.
LordJezo said:
There are so many choices for that. What's considered the safest and most stable of the radio update files? I dont need fancy, just one that is considered working.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=715485
Download the one labeled "Latest." You always want to have the most up to date radio possible.
Also, when you are rooted and running a custom rom and run into a problem, its always a good idea to backup and flash a stock rom just to make sure it isnt a rom problem
sitlet said:
Also, when you are rooted and running a custom rom and run into a problem, its always a good idea to backup and flash a stock rom just to make sure it isnt a rom problem
Click to expand...
Click to collapse
True. But there are certain steps that should be taken before resorting to that.
I'm not sure what happened but this morning I installed Codename Android's rom since everyone's been speaking so highly of it. I immediately got reboots right after starting. The screen would freeze and then the phone would reboot. I figured there was something wrong so I formatted data/factory reset, formatted cache and even formatted /system and installed it again. No reboots but the earpiece would not work on phone calls (speaker phone does). I also noticed that the screen doesn't turn off when I hold the phone to my face (so the proximity sensor seems to be messed up too). So I installed another rom: Redemption Rom. Same problem. I installed GummyNex, same problem.
I even unrooted and relocked the bootloader and EVEN THEN the earpiece did not work.
I feel like this is a software issue because it happened after installing a rom AND the proximity sensor doesn't work which seems strange for both that and the earpiece to stop working at the same time...
Is there something else that I haven't tried yet? Any suggestions??
I've only had the phone for a couple days so it could easily be a hardware issue I suppose, but I wanted to check if anyone had anything like this happen to them.*
Thanks guys!
Codename Android....if everyone's so highly speaking of it how come I haven't heard of it?
- Which version of the phone you have? CDMA? I'm assuming?
- What kernel?
Codename Android is one of the most popular roms on Rootzwiki
HeliosAI said:
Codename Android is one of the most popular rom on Rootzwiki
Click to expand...
Click to collapse
This is XDA, not Rootzwiki. I googled it. Answer the rest of the questions.
Have you tried flashing another ROM? Flashing stock images provided by Google?
CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?
I tried a few other roms and the issue was still there as well.
HeliosAI said:
CDMA and stock kernel. I have it completely unrooted and relocked and the issue is still there which makes me think it's less of a software issue. Unless somehow the software issue carried over from the rom?
Click to expand...
Click to collapse
And you've checked the obvious that the headphones work on another device correct? Tried another headphone on the phone?
If you fully wiped the phone and tried it with another ROM then it's most likely a hardware problem. And maybe it was a coinicidence that it broke right when you flashed the ROM.
Go into your about phone and tell me what it says for "kernel version"
Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.
HeliosAI said:
Yeah I essentially tried everything. Thanks a lot. I was hoping I'd be able to fix it but I guess I have to take a trip back to the Verizon store.
And thanks for responding. I posted this on Rootzwiki and didn't get much help.
Click to expand...
Click to collapse
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.
zephiK said:
Assure you flash stock Google images. Otherwise if they see that you unlocked the bootloader at one point in time they may charge you extra for that.
Check kernel version for me real quick though.
Click to expand...
Click to collapse
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1
HeliosAI said:
Yeah I made sure about flashing the stock google images.
Kernel:
3.0.8-gaaa2611
[email protected] #1
Click to expand...
Click to collapse
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.
zephiK said:
Okay yeah that's stock Google kernel. Most likely hardware problem, just weird how flashing a ROM triggered a coincidence.
Click to expand...
Click to collapse
Yeah very weird. Thanks again man, really appreciate it.
HeliosAI said:
Yeah very weird. Thanks again man, really appreciate it.
Click to expand...
Click to collapse
Sorry I couldn't help. Good luck with your new replacement when you get it though.
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
CrfEpic4g said:
Just odin the stock tar
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
What do you mean by that? Which stock tar?
I think the latest tar we have is still Lj7 but idk. just flash the lj7 tar in odin and update to the latest ill try and find it for you
Sent from my SPH-L710 using xda app-developers app
---------- Post added at 08:50 AM ---------- Previous post was at 08:47 AM ----------
http://www.hotfile.com/dl/161492098/9fa8372/L710VPALEN_L710SPRALEN_SPR.zip.html
Theres a link to lj7 just download that flash it in odin and youll be back to stock. Then all you have to do is update to mb1.
Sent from my SPH-L710 using xda app-developers app
Saturn2888 said:
tl;dr I have a blue LED showing up in the top left of the phone and nothing showing up on the screen after the SAMSUNG logo appears. I do hear the Sprint 4G LTE music, but that's it. The screen is off.
NOTE: I'm running Sprint's stock 4.1.1 ROM rooted.
Other threads I looked at (neither is the same issue):
http://forum.xda-developers.com/showthread.php?t=581929
http://forum.xda-developers.com/showthread.php?t=1792477
I had my first OTA update appear today. When I ran the update, Clockwork showed up and upon hitting "Yes", it failed. I looked around online and found this guide to reverse my rooting: http://www.epiccm.org/2012/06/sprint-sgs3-stock-restore.html
I was able to successfully flash TeamEpic-RemoveRoot-from-Recovery-signed.zip, but I didn't hit the keys right for the next one and ended up booting into the OS.
After restarting the phone, I hit the right keys and started ODIN. I saw COM show up in blue and put the TeamEpic-Sprint-SGS3-stock-boot-and-recovery.tar.md5 file in the PDA area then hit Start. I got a green PASS and then closed Odin and waited.
The phone had a black screen with that blue LED in the top left. I waited a while and then just powered it off. Took out the battery and tried again, same thing; although, the SAMSUNG logo does show up. It turns off when the Sprint part is supposed to show and at that moment I can hear the audio but the screen turns off. In this mode, the phone gets very very hot.
I can still boot into the stock recovery, but I can't do much else.
I just wanted the OTA . Does anyone know what might be happening?
EDIT: I put Clockwork Recovery back on, and then Advanced Recovered the boot part of a backup I did before this mess. Surprisingly, that worked. Problem is, I still haven't gotten the OTA working.
Ideas?
Click to expand...
Click to collapse
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
topherk said:
Why are you so intent on taking the OTA? Freeza has a stock rooted ROM over in his thread. And if you want just update the baseband, just flash the "MB1 Firmware/modem/baseband update" file in the aforementioned thread.
If you're already rooted with a custom recovery (which you were/are), there's no reason to unroot just to flash the OTA. Freeza typically has his stock rooted ROM updated with the OTA within a week of it being released. In my area OTAs are kind of late, so he typically gets it out before I even see the notification.
So, in summary. OTAs are not required, XDA (and Freeza in particular) has you covered.
Click to expand...
Click to collapse
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Saturn2888 said:
Strange. I upgraded the ROM by flashing, everything seemed to work as I'm at 4.1.2 now, but the Upgrade notification is still there for some reason. Is there any way to tell the phone it's been upgraded?
Click to expand...
Click to collapse
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
Saturn2888 said:
I'll go ahead and give it a try then. I haven't ever had a ROM update since I got the phone in October so I figure the upgrade won't work right, and I'll need the full ROM. Currently doing a backup.
Does flashing a ROM affect all app settings? And if so, by that point I'd just wanna have another ROM. The main reason I am fine w/ the stock ROM rooted is bc all my settings and apps are already installed and configured as well as the fact that I know it will work properly. So if this removes my settings, no reason to go stock anymore aside from the fact that I've seen that CyanogenMod doesn't get as good of signal on the S III as stock-based ROMs. Do you know if this still true?
Click to expand...
Click to collapse
If you dirty flash the rom over whatever you had before, it should not affect any settings
CNexus said:
Are you on MB1 or MA6?
Just flash an updated rom, or follow the instructions in my OTA thread for how to get rid of it
If you dirty flash the rom over whatever you had before, it should not affect any settings
Click to expand...
Click to collapse
MB1 as of now. What do you mean by dirty flash the rom?
edfunkycold said:
Setting >scroll all the way to the bottom >about phone>read what it say there. If it says your on latest then it should be ok you may have to clear some things and if it doesn't say latest just edit the build prop.
Go to this thread by Cnexus and follow all instructions http://forum.xda-developers.com/showthread.php?p=39627397
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Saturn2888 said:
MB1 as of now. What do you mean by dirty flash the rom?
I think the message isn't showing up anymore bc it hasn't bugged me at all today. Device Status is and has always been "Modified" anyway.
Thanks!
Click to expand...
Click to collapse
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
CNexus said:
A dirty flash is when you flash without clearing anything, and that's why no data is lost when you do one of those. However it can lead to issues, so i would advise against it when possible
Click to expand...
Click to collapse
Yeah, last time I did that, the system wouldn't boot.
While I am in a call up to my ear, not speakerphone, I can hear the other person perfectly. However, they cannot hear me.
If I go to speakerphone they can hear me.
I am running s3rx 4.1.1
Update flashed back to stock using odin and still no luck. They can hear me on speakerphone but not when it is by my ear.....
I'm assuming this was not an issue until flashed this rom.
Did you come from a full wipe? Have you tried wiping a reflashing to see if this corrected the issue?
If you've done all the troubleshooting you can, post the issue and your fix attempts in the ROMs thread. Cheers
xBeerdroiDx said:
I'm assuming this was not an issue until flashed this rom.
Did you come from a full wipe? Have you tried wiping a reflashing to see if this corrected the issue?
If you've done all the troubleshooting you can, post the issue and your fix attempts in the ROMs thread. Cheers
Click to expand...
Click to collapse
No luck.
Still need help
is there anything (dirt, etc) in the mic hole?
xBeerdroiDx said:
is there anything (dirt, etc) in the mic hole?
Click to expand...
Click to collapse
Fixed it!
was it firt or another fix? :victory:
xBeerdroiDx said:
was it firt or another fix? :victory:
Click to expand...
Click to collapse
It was dirt, I stuck one of my girlfriends earring in the mic hole and it works.
I recently flashed an FM Radio app on my Note 3 (rooted SM-N900T w/CM 12.1), flashed without issue but ever since then I do not have sound through my earpiece. I am unable to take calls unless I use a headset or use the speakerphone. I have already wiped and reflashed, not only CM 12.1 again, but have also done a full factory reset and flashed stock as well but the problem persists. Anyone have a clue to get the sound back in the earpiece? This is driving me up the wall!
gimik28 said:
I recently flashed an FM Radio app on my Note 3 (rooted SM-N900T w/CM 12.1), flashed without issue but ever since then I do not have sound through my earpiece. I am unable to take calls unless I use a headset or use the speakerphone. I have already wiped and reflashed, not only CM 12.1 again, but have also done a full factory reset and flashed stock as well but the problem persists. Anyone have a clue to get the sound back in the earpiece? This is driving me up the wall!
Click to expand...
Click to collapse
Not sure if you've resolved the issue yet, but I'll try to help if you haven't. You could try formatting everything in recovery instead of just wiping. Format all except your external sd of course, and then try to flash a ROM. If that doesn't work you'll probably need to use Odin to flash stock firmware and re-root and so forth. That should definitely clear up the issue if simply formatting and flashing a ROM doesn't work.
For future reference, do not flash any FM apps. It probably messes up the drivers and the apps won't work correctly for us at the moment regardless. Our N900T has an FM chip but it's not active at the moment. However, our team is currently trying to find a driver to get it functioning.
Sent from my SM-N920T using Tapatalk
ludeawakening said:
Not sure if you've resolved the issue yet, but I'll try to help if you haven't. You could try formatting everything in recovery instead of just wiping. Format all except your external sd of course, and then try to flash a ROM. If that doesn't work you'll probably need to use Odin to flash stock firmware and re-root and so forth. That should definitely clear up the issue if simply formatting and flashing a ROM doesn't work.
For future reference, do not flash any FM apps. It probably messes up the drivers and the apps won't work correctly for us at the moment regardless. Our N900T has an FM chip but it's not active at the moment. However, our team is currently trying to find a driver to get it functioning.
Click to expand...
Click to collapse
Hello and thank you for the reply, this issue is still very much unresolved so your help is much appreciated! I have already tried using Odin to flash stock firmware to no avail, the problem still persists, however I will certainly try formatting everything in recovery and hopefully that'll clear things up, that didn't even dawn on me to try. Thank you for the suggestion, I will report back my results here. And absolutely will NOT be flashing any FM apps in the near future! :laugh:
gimik28 said:
Hello and thank you for the reply, this issue is still very much unresolved so your help is much appreciated! I have already tried using Odin to flash stock firmware to no avail, the problem still persists, however I will certainly try formatting everything in recovery and hopefully that'll clear things up, that didn't even dawn on me to try. Thank you for the suggestion, I will report back my results here. And absolutely will NOT be flashing any FM apps in the near future! [emoji23]
Click to expand...
Click to collapse
Ah man... that doesn't sound good if Odin didn't fix it. No pun intended. Lol
Yeah hopefully formatting will do the trick. If not it almost seems like a hardware issue and the speaker actually went out. Using Odin and stock firmware should flash back all the correct drivers.
Sent from my SM-N920T using Tapatalk
ludeawakening said:
Ah man... that doesn't sound good if Odin didn't fix it. No pun intended. Lol
Yeah hopefully formatting will do the trick. If not it almost seems like a hardware issue and the speaker actually went out. Using Odin and stock firmware should flash back all the correct drivers.
Click to expand...
Click to collapse
I had such high hopes for the formatting but unfortunately it did not work. I formatted everything in recovery and used Odin to reinstall stock but the problem persists. I can't imagine the FM app killing the earpiece as it worked prior to flashing the F'n thing but I guess I'm stuck to using a headset! If you have any other suggestions let me know. :good:
gimik28 said:
I had such high hopes for the formatting but unfortunately it did not work. I formatted everything in recovery and used Odin to reinstall stock but the problem persists. I can't imagine the FM app killing the earpiece as it worked prior to flashing the F'n thing but I guess I'm stuck to using a headset! If you have any other suggestions let me know. :good:
Click to expand...
Click to collapse
I personally don't know of anything else to do. You've gone through all the steps to fix it I believe. Like I said, it does sound like a hardware problem now.
Sent from my SM-N920T using Tapatalk