yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
lol...yeah...I just read about it. Still, I'm more worried about my update not working than I am about the universal search. The universal search can probably be worked around via software or an app but hardware that won't update is simply broken.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Crap. I guess will have to find another way to update or maybe Kies will get the update later
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Did you figure out how to fix this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Did you try force stop AT&T software update and clearing data and then checking for update?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bfaber:
I tried that. It lets you check again but the update still fails.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lbarb2133:
people just exchange phone i did and have no software issues the phones were probably flash wrong
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
Just tried through Kies and it doesn't see any updates. Will be exchanging the phone tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
So this is very strange - I flashed the rooted stock room and it went fine. However, I still get the communication failed error. This means it's something specifically on my phone that's causing this and not a bad flash. Not sure what it could be.

Will try re-enabling all apps and clearing some data. Any suggestions? Anybody flash the stock i747 ROM and have an issue with updates?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bfaber:
I was hoping to see if anybody flashed stock.

I wonder if there's some super-odd tie-in with some app that's loaded, or the sim card? (Actually, no, I tried to flash after a hard reset, with nothing loaded on the phone but stock.. that didn't work either).

No idea...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
I just tried switching the SIM with the one that came with GS3. Made no difference. I've flashed stock and still no go so not sure what else to do. I refuse to believe it's not some stupid bug that's causing this.

@bfaber, what apps if any do you have disabled? Doubt that's it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bfaber:
Actually I checked again. I told the phone not to resync with google on reset, so while it did update, it only updated those apps that were on the phone.

I had previously disabled AT&T Navigation, but that's back.

I'm with you.. I can't, for the life me, understand at all what would cause this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tyshemi:
I told you guys what Samsung told me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
yeah, I'm going to the store tomorrow and see if they'll exchange it for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drwx:
Turn off wifi and try again. I got this same message in my captivate (before i abandoned the stock firmware)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
I've tried with wifi on, wifi off, LTE on, LTE off, tried from home, tried at work, tried where there is no wifi available at all (and had wifi turned off), etc..etc... Nothing worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
What the ****? I just swapped my GS3 for a brand new one and the new one has the SAME ****ING ERROR. Oh well, I'm going to manually update to the OTA since it's a new phone anyway and hope they fix it. Ridiculous

I hope this phone doesn't have any hardware problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
Man that sucks. I wonder if there's even a point exchanging mine then. On another thread someone mentioned that they've had a few different samsung phones and all of them had this same problem at first and then it fixed itself and magically started working. I saw the post on manually updating the rom -- thanks for that info -- but I was hoping to be able to fix the problem so I wouldn't have to wipe the phone in the process of updating it.

---------- Post added at 05:43 PM ---------- Previous post was at 04:56 PM ----------

I emailed them about this issue and according to them, it is not a known issue. I even pointed them to this thread so at this point I'm not sure how they can say it's not a known issue since they are definitely aware of it. But like most companies who release products with problems, their first course of action is usually to deny that the problem exists and keep denying it until they are forced to do otherwise. It wouldn't surprise me if that's what's happening here. I hate to sound cynical but I've seen this way too many times. In the cellphone industry, Apple is notorious for this. I am hoping Samsung isn't the same. I'll need to see it before I believe it though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Did you end up exchanging your phone ? Given my experience I don't think it's even worth the hassle if your current phone runs fine otherwise. What region are you in ? It could be a regional thing since they probably direct you to a server based on your geographical location. Only thing I can think of since I've now tried two different SIM , and two different phones. Also flashed stock ROM and even OTA so no way it's hardware or software unless I'm super unlucky right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
Haven't exchanged it yet. Have the box in the car so I'm ready to go to the store but like I've mentioned, I absolutely hate exchanging and returning things unless there's a very good reason. A phone that can never get updates is definitely a good enough reason but if there's a fix for it, I'd rather fix it and avoid the hassle of exchanging it. The phone has some other problems too but I can probably work around those or fix them. The update issue is the biggest headache right now though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
I'd hold off because if it is a software or hardware problem the phones currently in stores will be from same batch so might be best to wait. I thought about this just now but whatever, I have warranty and worst case can root and flash updates that way. I hate exchanging phones too and I'm done for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
I wonder if I can go to the store and have them test a new phone before I exchange mine? If the new phone works, I'd take that, if not, I'd keep mine....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bfaber:
Question: How did you manually update and did it require root?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
http://xdaforums.com/showthread.php?p=28648604
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] morechoff:
Issue with Software Update Gone

I had the same issue (getting an error message) when I did a Software update right after buy the phone this weekend. However a 3 or 4 days ago it went away (I kept trying every 24 hrs). Basically said no updates which is the correct message. Yesterday I successfully updated the phone with the OTA update. I dont think it is a hardware or software issu,e but an issue at ATT with the servers. Might be some verification going on that fails.

I knew about the issue before I bought the phone so I tried the demo phone at ATT and it worked fine. Mine I tried at ATT and it error-ed on the update but I decided to wait it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Mine still errors out but I'm already on the new update so it should just say that I'm up to date instead of erroring out all the time. As long as its fixed by the next update then I'm perfectly happy.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] racerex:
I still get the error on my bone stock phone....

----------------------------------

Communication failed.

The server is currently unavailable.

Your device will automatically check for an update within the next 48 hours.

----------------------------------

Anyone have any updates as to what might be going on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
It must be a server issue they will need to fix. I'm on brand new phone and still have same issue.

Btw what phone did you have before the SGS3 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
I emailed Samsung. They claim it's not a known issue.

That said, it may very well be an ATT issue and have nothing to do with Samsung.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Looks the idiots finally turned on the server. Did you try today ? I already have the update but this is the first time I've not had the error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
I tried earlier during lunch and got the error message. Tried again right after and got the message that I couldn't check again for another 24 hours. So I changed the date on my phone to tomorrow and tried again, and got the server communication error again. Then it said I could try again in 48 hours...so I changed the date up one more day. Now it says I can try again in 67 hours. lol... at this rate I won't be able to check for updates until next Easter! This is ridiculous.

But if it's working for you, maybe I'll sit tight and wait till Monday and try again. My exchange period ends next weekend so I still have a little time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
You can skip this. Force stop and clear data for the Software Update in Applications and then reboot. When the phone comes back up it should check and reset the timer.

By the way changing the time might break the update process if the server and client use current time as a way to authenticate
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
Cool, thanks. That solved that annoyance. Tried it again a couple of times and still getting the error message though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Second day in a row and no error so I hope I'm in the clear. This time I did it over WiFi and still no error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] faulkton:
still getting error.. pretty lame now that an update is available.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
Same here. I've tried everything. Monday morning I'm calling ATT to try to talk to someone in their data support dept to see if they can help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidLonghorn:
I kept getting an error everytime i tried to update. It would say it failed to communicate with at&t's server. I got fed up on Saturday and killed AT&T Software Update in application manager, and I cleared the data on the app. I clicked on update. It said it was downloading, and after a few more minutes it finished downloading. In my testing, I had also force closed FWupgrade just to be on the safe side.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
I've tried that several times. No dice....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidLonghorn:
I should add that this was my 2nd galaxy s3 to not update. I did a factory reset hoping it would fix the issue. It didn't. I called att customer care for help b/c I was thinking maybe they just set up my account incorrectly when I first got the phone. Nothing else really makes sense. They said they couldn't help and take it to the store. I took it to an att store, and they said they don't actually do any software troubleshooting, so they just exchanged it for a new one. I tried doing the update there, it failed, so I took it home, and I closed all the update apps, cleared all their data, and it worked as soon as I hit update. There may be nothing else you can do except take it in to an att shop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Funny it started working on my 2nd device too. Could never get it to work on the first one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
So am I pretty much the only one still having this problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
At this point it seems you need to swap out the device. I tried again yesterday and it worked again so it does appear to be working right now for me when on my first phone it never did no matter what I tried.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] forz.A:
You are definitely NOT the only one still having this problem. The only time I don't get the communication error is when I try updating again before the 24 or 48 hour clock is up - but all it says is to try again once it's up. I've tried all of the tips and tricks listed, but still no luck. It's just a hunch, but it really seems like it's server issue on AT&T's end... regional servers affecting only certain people. Who knows. I'll go in this week if it doesn't change.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
Glad I'm not still the only one. I'm actually on hold with samsung right now. This is like a comedy of errors. I called ATT and talked to their data support and they couldn't figure it out and transferred me to samsung. The tech at samsung then tells me that the S3 does not receive OTA updates at all and that no one has released an update for that phone yet. I insisted that this was not correct and he transferred me to the next level support. That rep also told me that there were no updates for the phone yet and I then pointed him to a couple of the threads here discussing the updates, one of them even showing screenshots which showed the different kernel versions. His response was "well, everyone who received that update was rooted....and we don't have any updates out so basically there are no updates..."

:mad:

Good god.... First, not everyone who received the update is rooted. Second, that would not make any difference. Third, there is obviously no communication between ATT and samsung since neither seems to know anything about anything and Samsung insists there are no updates for the S3 yet despite my having pointed them to these threads. This is really frustrating!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Signia:
I am also having the problem. I am in St Louis, MO. I have tried all of the suggestions here but no luck. Samsung told me to get my device "reflashed" at and AT&T device support center. Dont see what good that would do unless there was a problem in their initial ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tyshemi:
That's what my friend who works there told me. I just got a replacement and it works fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
Wow, it's a parade of idiots this morning! So I call ATT back and ask for data support. The rep asks to confirm the problem so she can get me to the right people. I explain...again....about the software update and she tells me that I don't need data support and that I should be glad that my phone is broken and can't get updates because the "gingerbread" update has been hosing a bunch of android phones of all different models and it's better that I don't install it anyway. Oy vey!!!! I started to explain that this has nothing to do with my problem, she puts me on hold and transfers me to.................................the collections department!!! lmao. So I ask for data support, she says ok I'll transfer you, and I promptly end up being transferred to the main customer service number again. Holy @#$@@#!!!!

Never quite seen anything like this before!!!

Anyway, after another parade of idiots and 3 hours on the phone between ATT and samsung with ATT telling me it's samsung's problem and the geniuses at samsung telling me that I'm imagining things because they are 100% positive that there are no updates for this phone, then calling ATT again, now ATT is trying to tell me that the problem is that their servers are too busy so that's why I'm getting the error. Well, I've tried at all hours of the day and night so that's definitely not the problem.

This is almost comical.....almost. :laugh:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
I only hope you don't swap your phone so we can all keep reading your updates. Comedy gold I tell ya!:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
I'm tellin ya!!!!! The guy told me to keep trying between now and 5 pm and they would call me after 5 to see if it finally worked. At this point I'm really curious to see what their next guess will be as to why it didn't work. I tried about 4 or 5 more times during lunch. Of course, same error.

BTW, I noticed something....could be nothing....but in the application manager there's an app called FW Update that someone else mentioned. They said they cleared the cached data and force stopped it. I noticed that on my phone, that app never has any cached data to clear. Can anyone check their phone to see if when they to a check for software updates, the FW update ends up with some cached data?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Signia:
My FwUpdate does not have any data cache
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
Ok so that's probably not related.

btw, I'm still desperately trying to not exchange my phone. My battery life issues are pretty much resolved, not sure if it just required the battery getting conditioned, but I'm now getting normal battery life -- today going on 8 hours on battery, 3 hours screen time, and battery is at 65%. Over the weekend I got almost 2 days of light use. The GPS issue is strange but it hasn't happened again. I've tested it a couple of times and it has worked ok so I'm thinking it could have been an anomaly. So now that the phone is more or less working right, I'm reluctant to exchange it for one that might have other problems. Hopefully ATT can figure out this update problem within the next day or two.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Signia:
FYI I exchanged my phone and bought another S3 and both worked the first time for the software update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
So here's the latest..... spent about 40 minutes on the phone with ATT this morning.and their current guess is that the software update hasn't been rolled out to all phones or all locations yet and that eventually it will get to mine. Sounds like a crock to me but I'm willing to wait and see. They're supposed to call me back on Friday and the guy said that if it's not working by then, he'll find me a local store that has an S3 in stock and will arrange for me to go and exchange it.

At least ATT is aware that there is an update for the phone, unlike Samsung who even after I showed them these threads still insisted that it was my imagination and that no one has released any updates for this phone yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PhoneLine:
I'm getting the communication failed message here in Brooklyn, NY. What are some people's locations? If we find people in the same area and some are getting the update and others are not, then this would be easy to say if its possible or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
I'm in Miami.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
I was thinking this too originally but then why would changing my phone make the update start working ? I'm so paranoid about this stupid thing now I check for update every 24 hours to make sure I don't get the error. So far every time it seems to work and I know I really should stop. Lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
What message do you get when you check after having installed the update? Does it just tell you that there are no updates?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Yes it takes a second and you see data activity happening and then it says "Your software is up to date"

That's it. When I used to get the Communication Error it would happen faster and I never saw "Your software is up to date" by itself like that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] faulkton:
really dont want to have to replace my phone.. i wish ATT actually knew something about this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
I guarantee you that someone there knows exactly what's causing it and how to fix it but the problem is that when you call their tech support, the person you are speaking to has no clue about any of it, the best they can do is follow their flowchart script, and you will never be able to speak to an actual tech there who knows how to fix problems like this. If it's not in the CSR's script, forget it.

So basically, instead of them having a real tech spend 10 minutes on the phone with you and fixing your problem, they'll waste hours upon hours of the script jockey's time and then have you exchange your phone, thereby wasting your own time and costing them a $600 phone which they end up trashing. It's a pretty ridiculous system, imo.

But as I mentioned earlier, at least ATT knows they have a software update out for the phone. That's a start. Samsung insists there is no such thing, even after I pointed directly to these threads.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Based on the logs I've seen the update fails on your phones (assuming it's the same thing) because the client fails to authenticate. I'm willing to bet it's a server issue since I even flashed my last phone with a system image and it didn't do it. Also when I got the new phone and tried for first time it failed. Then second time and every time after that it started working.

One other thing you can do is a. Call them and make sure they have the right IMEI in their system , for me they still had my OneX which blew my mind. b. Try using the SIM card that came with the phone or a new one.

I really don't think it's the phone itself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BonesHopkins:
Yeah, it's not the phone. It's the fact that the phone is not registered properly in their system and as a result isn't authenticating on the update server. I did have them check the IMEI and it's right but the guy I talked to yesterday said about that it looked to him like the phone wasn't showing up properly in the system and that he tried putting it in but he wasn't able to. Very strange, imo.

And the sim card in the phone is the one that came with it. I wonder if I could put my iphone's sim in it?