I think this started happening after I flashed CM 11, however I've gone back to the original rom and it still doesn't work. Can anyone help me with this?
I've already tried updating to the latest CWM and then the latest TWRP. I also tried factory reset and then fixing permissions with no success. BTW, all that was tried on the stock rooted rom.
I figured out how to fix but I'm not sure how it happened. Basically to fix the problem I simply disabled google voice to my cell phone number at www.google.com/voice.
Just thought I would mention just in case someone else has a similiar issue.
Fixed.
I figured out how to fix but I'm not sure how it happened. Basically to fix the problem I simply disabled google voice to my cell phone number at www.google.com/voice.
Just thought I would mention just in case someone else has a similiar issue.
Related
After installing Radio 2.05.00.06.11 (dinc_ota.zip), my handset speaker audio disappears. Speakerphone and bluetooth work fine, but no luck with the internal speaker.
Heres the kicker:
Once I restore the 1.0 Radio, the internal speaker starts working again.
After lots of searching, this seems to be a very intermittent problem. I've only found two other people experiencing the same issue. Unfortunately I have not found a solution.
Does anybody have any idea as to what my next step should be to try and solve this?
Thanks!
I have the same problem...
heega1 said:
After installing Radio 2.05.00.06.11 (dinc_ota.zip), my handset speaker audio disappears. Speakerphone and bluetooth work fine, but no luck with the internal speaker.
Heres the kicker:
Once I restore the 1.0 Radio, the internal speaker starts working again.
After lots of searching, this seems to be a very intermittent problem. I've only found two other people experiencing the same issue. Unfortunately I have not found a solution.
Does anybody have any idea as to what my next step should be to try and solve this?
Thanks!
Click to expand...
Click to collapse
Try downloading a fresh copy of the update and running it again?
It's working just fine for too many people for it to be a problem with the update itself.
douger1957 said:
Try downloading a fresh copy of the update and running it again?
It's working just fine for too many people for it to be a problem with the update itself.
Click to expand...
Click to collapse
updating the radio twice will brick the phone! same one that is.
zeke1988 said:
updating the radio twice will brick the phone! same one that is.
Click to expand...
Click to collapse
not exactly. but, this radio isnt a image, its a patch. and a double patch is not the same thing... there is no error checking. dont do it!
I've tried re-installing the update 3 times from three sources. At first I thought it was the Froyo update so I went back to my nand backup and that didn't help, but once I downgraded the baseband it magically started working again.
So I tried it again. Re-downloading all the tools and packages. Only for it to happen again right after the Radio update. So I reverted back, cleared everything to factory, did a fresh install, then did the upgrade once more.... Still same problem.
Since it is such an intermittent issue, I'm thinking that maybe the hardware is to blame. The particular handset that I have is a warranty replacement from Verizon (blown speakers on first one). Maybe that has something to do with it.
Anyone have any other theories?
Thanks!
So I'm stumped. It's a pretty straightforward process, and I can't see where I'm going wrong.
Next Step: Warranty Replacement. We'll see if that helps. I'll be sure to record the serial number and other details of the phone before I send it back. Maybe we can find a pattern.
It will be a couple days before the new phone arrives. If you have something I can try, please suggest away!
Thanks!
I am having the exact same problem. I have tried both 2.x radios and both have the same effect. I want to use froyo but the only way to is to use speakerphone or a plugged in headset. I tried to take it in yesterday but the tech at verizonwireless told me to wait it out until 2.2 comes out to see if that fixes my problems. ( went in stock told them I was having the problem on stock radio) final problem being is when official does come out and it kills my headset speaker is it going to be too late to root my phone knowing the replacement I get will already be loaded with the new software.
Chicken and Egg
Unfortunately, unrEVOked has not developed a S-ON patch. This means that you will either have to take stock 2.2 which will be unrootable -or- you will patch forever, have S-OFF, get stock 2.2 and not be able to return the phone if the problem doesn't clear up.
Please keep that in mind when making your decision.
The replacement phone worked...
Not sure what the problem was, but it confirms my method for installing 2.2 wasn't flawed..
Thanks for all your help!
-j
I am trying to get verizon to send me a new one. They are not being very helpful right now. They said the audio issue is a software issue that should be fixed with the new update but might send me a new phone due to number of dropped calls. I have to stop in store tomorrow
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
robertlewisca said:
I am having an issue with updating a Red AT&T Galaxy Siii OTA. I am not rooted (and have never been rooted on this phone), running stock ROM, currently on baseband I747UCLG1. Everytime I try to update OTA manually, I get an error that says, "Communication Failed. The server is currently unavailable. Your device will automatically check for updates within the next 48 hours."
I have also noticed a few others in the update thread having the same issue, but I haven't seen a solution posted. That thread is mostly about issues with updating on a rooted phone, so I thought I would start a new thread focused on this issue.
I have tried the following:
1. Tried on more than one wifi network to eliminate possibility that there is any issue with my network.
2. Cleared the AT&T Update application cache and tried again - multiple times.
3. Did a full factory reset, and tried again.
None of these has resulted in me being able to update OTA. Are there any others out there like me? Has anyone found a solution yet?
Click to expand...
Click to collapse
I was having the same exact problem. I even changed phones thru warranty. The new phone did the same thing. New SIM card didn't help. I had a guy at tech support to push the update to me.
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
IDK, co-worker with a Skyrocket has had the same issue, but he doesn't care about the update, so he hasn't bothered to get it resolved.
If I didn't have a red GS3, I could goof around and tell you that is what the problem is...
Actually, if it were me having the issue, I'd walk into AT&T and have their guys mess around with it. No telling why some have more issues than others.
robertlewisca said:
I am having mine replaced under warranty as well. I hope it ultimately fixes the problem. What I don't want is to have to contact AT&T tech support every time there is an update and ask them to 'push' it to me - then have to explain the entire issue over again, and be forced to go through their trouble-shooting again which includes them insisting I do a factory reset.
Is there anyone else out there having this issue? I would like to get a sense for whether this is pretty isolated, or whether it's a bit more common.
Click to expand...
Click to collapse
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Not really a solution but you could install this http://forum.xda-developers.com/showthread.php?t=1902178 to be fully stock LH9 with Root. Or use the OTA zip from here http://forum.xda-developers.com/showthread.php?t=1896773.
aboveusonlysky said:
i had the exact issue went to att yesterday and tried a new sim card, but that didnt work. i tried everything you did with no suck luck. the want to warranty out my phone but im not dealing with them again so i just rooted and flashed it. i also have the red one... maybe its just this color since it came out later with a different baseband version?
Click to expand...
Click to collapse
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
78c10 said:
No, It's not just because it's red, regardless of their original baseband versions.
Otherwise, I wouldn't have been able to update.
Click to expand...
Click to collapse
You mention in your signature that your phone is rooted. So, did you update OTA then root, or did you update after rooting through some other method? The challenge some of us are having is that we are not rooted, and cannot update OTA because of the 'server error' it gives us everytime we try.
Problem Solved - for me at least
Well, the problem is solved for me, and I thought I would share what I found out here in hopes it helps someone else.
First, I had the phone replaced under warranty. It appears to be a brand new phone. When I received the new phone, I started it up, went through the normal startup stuff - entered my Google account information, it backed up my info and settings. Before I loaded any apps, I went straight to the update screen, and tried to check for an update. I again got the 'communication failed' error. Bummer.
So, then, I did a factory reset on the new phone, but this time instead of entering the initial Google account info on the startup screens, I skipped through all of the initial screens, got to the home screen, then went straight to the update screen - and this time it worked! So, it must be something to do with the initial screens, and entering Google account information that caused the problem.
Then, I got to thinking - perhaps this might work on my old phone too. Since I just got the warranty phone today, I still had my old phone (which needs to be sent back). So, I did a factory reset on it, skipped all of the initial screens where it asks for Google account information, and it still didn't work on the old phone. So, I'm not sure what the original issue was.
By the way, after the update installed on the new phone, and I went through and entered all of the Google account settings, and then checked for the update again, and there was no error.
So, perhaps this might be helpful for others?
Hello,
i've been experiencing troubles making calls since upgraded to 4.2, tried 4.1.2, hangs up immediately call log says 0 seconds.
there is a topic about it at google issues, but i thought if i'll bring it here it will get some more attention. it seems that removing the SIM and re-inserting it, fix it, but after restart, problem restore.
only few service provider seems to suffer from this issue.
here is the topic: code.google .com/p/android/issues/detail?id=39904
thank you!
Taufik15 said:
Hello,
i've been experiencing troubles making calls since upgraded to 4.2, tried 4.1.2, hangs up immediately call log says 0 seconds.
there is a topic about it at google issues, but i thought if i'll bring it here it will get some more attention. it seems that removing the SIM and re-inserting it, fix it, but after restart, problem restore.
only few service provider seems to suffer from this issue.
here is the topic: code.google .com/p/android/issues/detail?id=39904
thank you!
Click to expand...
Click to collapse
Try factory reset and pull the battery for a few minutes then put it back
Sent from my Galaxy Nexus using Tapatalk 2
Sorry for the delay,
I tried this and same issue appearing..
any other suggestions?
Bump....
Download a stock ROM from Google Developer, and flash the new ROM.
^^^xdabilly said it.
I just did this recently myself having gone 4.0.3 to 4.1 to 4.2 via ROM wipes and flashes only. My phone doesn't misbehave anymore since I completely wiped it and flashed Google's official image and then went on about rooting from there and now back to Purity ROM.
Hey everyone,
after trying to keep my root from the OTA I caused some problems and fubar'd my phone. so I did a full restore because i didn't even have a phone app anymore.
I re-installed all my apps and even got Nova Launcher back without root. but now whenever I make or recieve a call. I can't hear anything and the other person cannot hear me. (i found a similar issue on youtube with a Nexus 4 and he updated the baseband)
I think it may be a baseband issue like in that video above, BUT, I do not know what baseband I should have on my Gnex.
Any help?
thank you!
-EDIT- Booting into recovery and whiping Dalvik seems to have fixed the issue. I also let the phone flash the stock recovery (if that matters) but I don't think that has anything to do with my baseband -/EDIT-
still FUBAR
BioHazard92 said:
Hey everyone,
after trying to keep my root from the OTA I caused some problems and fubar'd my phone. so I did a full restore because i didn't even have a phone app anymore.
I re-installed all my apps and even got Nova Launcher back without root. but now whenever I make or recieve a call. I can't hear anything and the other person cannot hear me. (i found a similar issue on youtube with a Nexus 4 and he updated the baseband)
I think it may be a baseband issue like in that video above, BUT, I do not know what baseband I should have on my Gnex.
Any help?
thank you!
-EDIT- Booting into recovery and whiping Dalvik seems to have fixed the issue. I also let the phone flash the stock recovery (if that matters) but I don't think that has anything to do with my baseband -/EDIT-
Click to expand...
Click to collapse
well, no I have sound when using speaker phone, BUT no sound in normal headset operation. HELP!!
I've got a rather strange problem... I'm running stock due to this issue... I'm running mm right now... Anyways, every time I root this phone, I lose my dialer program menu for example, *#0*#. I figured it was a rooting issue so I just flashed back to stock and then flashed only twrp and then flashed a mm rom. Well it still did the same thing. Anybody else having this issue or know of a fix? I need to be able to access the calibration menu for my compass for work..
Nobody has this issue? Ik I can't be the only one...