• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Software Update for Infuse 4G?

I just did another manual update check. Failed. But instead of staring at the darkened screen that says "Checking for software updates...," like I usually do, I just pushed the home button. When the connection failed box appeared again, I pressed Home again. That let the device management arrows come back to check again, with no success, of course. That happened one more time in addition to this time, back to back (displayed that error message both times).

I tried battery pulls before I tried checking, but that had no effect at all. Still the same message.

But here's my thesis/theory: When I left my Wi-Fi on and connected to check for updates, the H+ indicator kept appearing and disappearing; this happened several times and it always happens when I don't turn my Wi-Fi off when checking for the updates. And the arrows always appear, no matter what network you're connected to, albeit they appear a few seconds later if you have your Wi-Fi on and connected.

This indicates that the phone is indeed connected to the DM servers. On top of that, there is always sporadic upload activity on the H+ icon, sometimes accompanied with download activity (but that's kind of rare). It indicates that the phone is querying the server to check for the updates. The connection failed response may just be a "euphemism" that it's not yet your turn to get the update.

Well, that's my thesis/theory I developed today. I of course could be wrong, so I'll welcome any corrections to this and my other post above.
 
dlee1001,
In my last conversation with ATT they did say the phone connects to ATT servers all the time, and that was in direct response to my question as to whether the phone connects to ATT servers for other than doing updates. Based on their response (I don't know who knows what when you talk to them) my concerns were eased somewhat. As you point out, and I was told as well, the connection error message is because you are not due for the update yet. It is "rolled out." I told them that I thought that was not the response we should be getting under these circumstances. If we are not in the queue for the update then tell us that. A connection failure could imply a bigger problem. Also, I have never seen a message indicating the update is available, which they said I should see when it is my turn, and since I have not seen that message it has not yet been rolled out to my phone. I was told more than once that the update is OTA and at least while talking to them they wanted me to turn off wifi. I really think that should not be necessary, but I did it. I was also told that I probably wouldn't get the update if the phone is connecting to 2G (Edge, I think they called it), which I do see from time to time. But I have been many places where it was connecting to H+ and I had 4 or 5 bars.

Of course, these are the things I was told. I'm not sure what to make of it. If it hasn't rolled out to us, when will it? At what point has it been too long? I've run through my mind reasons why we may not have gotten the update, or gotten it yet. Does it have to do with when we purchased the phone? I bought my phone just days before the release. Is the software version on our phones actually different in some way and therefore doesn't require the update. I realize that's a stretch, but I am beyond believing there is something wrong with the phone. There is something else going on. I'm hoping that 2.3, or some other major update to the firmware comes soon so we can see if it is just a problem with the minor update. In other words, does the system think we are already up-to-date? That wouldn't be the case with a major release.
 
It's now been exactly one month since the update itself was released. And we still haven't gotten it. Well, at least I haven't. What about you? I just checked again and it said that same euphemism that requires either some interpretation (on our part) or some rewording (on Android's or AT&T's part). I prefer the latter. It's just illogical for it to say that the connection failed when everything else works flawlessly, as you imply.
 
If I recall it correctly, I think the update only changed the Baseband version to I997UCKE3. Is that what yours shows?
 
Egidio, as I mentioned earlier, I have not received the update yet. How did you get yours? When you tried to check for updates, did you get any kind of connect failed messages? When you got the update, what kind of notification did you get? A text message or an icon on the top left of the screen?
 
Egidio, as I mentioned earlier, I have not received the update yet. How did you get yours? When you tried to check for updates, did you get any kind of connect failed messages? When you got the update, what kind of notification did you get? A text message or an icon on the top left of the screen?

My update came automatically. I always turn off my phone every night. So, the day after the update was released, when I turned on my phone, I got an AT&T notification (notification bar, top left) saying there was an update. There was no error and got the update installed at the first try.
 
I have not received the update.

The baseband version I have ends with D5 (I think the build version also changed in the update, might be wrong).
 
My update came automatically. I always turn off my phone every night. So, the day after the update was released, when I turned on my phone, I got an AT&T notification (notification bar, top left) saying there was an update. There was no error and got the update installed at the first try.

What can I do to get such a minor update? I've tried calling AT&T which had mixed update.

Various approaches were tried in order to get the update, including doing battery pulls/rebooting, clearing data for Device Management and then doing a battery pull/reboot, connecting and disconnecting from my Wi-fi while checking for updates, and even restoring to factory settings. Not one method worked.

What do you think somanyapps and I should do, Egidio? Should we wait until the Samsung KIES software comes out for the Infuse 4G? Will that let us update our firmware to E3 and get Android OS updates?
 
If there is a problem it should be resolved, but frankly I'm not worrying about it. Other than this particular issue I have no complaints about the phone, and no reason to believe there is anything wrong with it. This is my second Infuse and it is exhibiting the same behavior as the first one regarding this update. It will come when it comes, or not, but hopefully will get the next major update. It was implied to me that this update really isn't all that important. However, my concern is less about this update and more about whether it would be able to get any update. We'll see. One thing that bothers me more than the fact I haven't gotten the update is the fact there doesn't appear to be any other way to get it, no manual process, no way to install from a file on your PC, or something like that, at least not until Kies works. And even if it never got an update, by the time it mattered, if ever, my commitment would probably be over, or close to it. Again, not saying it shouldn't be fixed if the cause is identified and a fix can be implemented, but I am saying, I'm not going to assume the phone is the problem and go out shopping for a new one that might have its own issues.
 
If there is a problem it should be resolved, but frankly I'm not worrying about it. Other than this particular issue I have no complaints about the phone, and no reason to believe there is anything wrong with it. This is my second Infuse and it is exhibiting the same behavior as the first one regarding this update. It will come when it comes, or not, but hopefully will get the next major update. It was implied to me that this update really isn't all that important. However, my concern is less about this update and more about whether it would be able to get any update. We'll see. One thing that bothers me more than the fact I haven't gotten the update is the fact there doesn't appear to be any other way to get it, no manual process, no way to install from a file on your PC, or something like that, at least not until Kies works. And even if it never got an update, by the time it mattered, if ever, my commitment would probably be over, or close to it. Again, not saying it shouldn't be fixed if the cause is identified and a fix can be implemented, but I am saying, I'm not going to assume the phone is the problem and go out shopping for a new one that might have its own issues.

You're right. My concern was and is not so much about the current UCKE3 update, but the future OTA updates that may take place from time to time; the concern I have is focused on the "connection failed" message and the 24-hour waiting period. I always have to clear data to check more than once a day.
 
dlee1001, I agree with somanyapps. It is strange, though, that you get the "connection failed" message. It sounds like you're not getting through. Perhaps if there are no updates the message should be different. When I manually run an update check on my phone, I get the standard message saying everything is up to date.
 
dlee1001, I agree with somanyapps. It is strange, though, that you get the "connection failed" message. It sounds like you're not getting through. Perhaps if there are no updates the message should be different. When I manually run an update check on my phone, I get the standard message saying everything is up to date.

The message you're getting that says you're up to date is true; it's probably because since you have the newest version installed, the phone does indeed tell you that explicitly. Plus, you said you got yours via a notification on the day after the update was released, so when they rolled the update out to the first batch of customers, you were part of that batch. somanyapps and I weren't.

But for those of us who have not gotten it yet may be getting the connection failure response as a result of poor word choice by AT&T or Android. If everything on the phone including the data connection works perfectly, then there is no reason for any kind of defect within the phone to cause this error message to appear. Like somanyapps and I have mentioned, it may just not be our turn yet to get the update. This information was confirmed when AT&T called me today. They said that Samsung rolls the updates out in sections and that I should contact them to try and solve the problem, which I will do. I'm going to try and get them to force the update to my phone. If that's not possible, I'll at least ask them when the next one will be rolled out and see whether it's possible that I can get it then. If even that's not possible, then I'm going to ask them about the KIES software for the Infuse.

Yes, I'll keep you updated on this information. I've also been checking the downloads page for the Infuse on Samsung's website, seeing the exact same thing every day. I hope KIES comes out real soon so it can fix all our problems. I strongly recommend you, somanyapps, that you check the downloads page for the phone every day, if you can and if you have time. If the previous generation phone (supposedly the SGH-I897) has KIES available for download, there's no doubt our Infuses (SGH-I997) will have it available soon.
 
So I contacted Samsung today and they said that AT&T does everything related to the updates.

Consequently, I contacted AT&T again to get this problem fixed. The technical support rep was very helpful and looked into my phone's information (SIM card, IMEI number, etc.). He didn't find any obvious conflicts with any of that. So he filed a troubleshooting ticket so that the network techies could look into my phone and see what's preventing me from connecting the the AT&T servers.

Yes, you read it right. There's nothing wrong with the phone or the account you're tied to for two years. There's something that AT&T did wrong which prevents the phone from connecting to get the update. The network techies will look into my phone and see what the preventing factor(s) is/are, and once that/those gets/get removed, the tech support said, I should be ready to proceed with the update. I'll receive a call or some kind of message letting me know about that too.

Let's hope that this will work.
 
dlee1001,
ATT opened a "case" for me when I called about issues I was having with the phone connecting to phone network for data. The problem finally got resolved during a subsequent call to tech support after not hearing from the engineers about my case. I never did hear from the engineers. That was not specifically about the update problem, but my network problems began after I asked the salesperson to verify that the phone info they had in my account was correct. One complicationg factor in all this is that I'm on my second phone, and I wonder if that has confused things. I also wonder if I had just waited a little longer with the first phone maybe I would have received the update. However, it was ATT who suggested I exchange the phone. I'm tired of talking to support and having to re-explain my problem each time. I will just wait and see. I will check the download page.
 
dlee1001,
ATT opened a "case" for me when I called about issues I was having with the phone connecting to phone network for data. The problem finally got resolved during a subsequent call to tech support after not hearing from the engineers about my case. I never did hear from the engineers. That was not specifically about the update problem, but my network problems began after I asked the salesperson to verify that the phone info they had in my account was correct. One complicationg factor in all this is that I'm on my second phone, and I wonder if that has confused things. I also wonder if I had just waited a little longer with the first phone maybe I would have received the update. However, it was ATT who suggested I exchange the phone. I'm tired of talking to support and having to re-explain my problem each time. I will just wait and see. I will check the download page.

Speaking of the download page, when I contacted Samsung yesterday, I asked them about the KIES software for this phone. They of course said it wasn't available. When I asked them when it'd be available, they replied the way Apple would have; they said that they don't have the exact info on future releases. But a possibility is a possibility, so who knows?
 
not sure if you all are still having problems with this, but i just wanted to offer some information on how it is SUPPOSED to work (i think), as it seems that none of you have even come close.

when i go to menu -> settings -> software update, it takes me to the "device management" screen.

from there, i have 2 options: "check for updates" and "continue update" - but "continue update" is always greyed out.

when i select "check for updates," i get a new screen that reads: "Software update process will not delete any personal data on your phone. Check the AT&T server for a new software update?"

then, there are 2 buttons at the bottom: "OK" or "cancel"

when i hit the "OK" button, i get a message that says: "Current software is up to date you may check again in: 24 hours 4 mins."

a little background - i have had the infuse for 9 days now - i ran the software update pretty much as soon as i opened it, and although it did take a while, it eventually updated my baseband version to the 1997UCKE3 that has already been discussed in this thread. i rooted the phone and now use infused ROM - the software update process still acts exactly the same.

i believe this is what is supposed to happen, since i did receive an OTA update right when i purchased the phone and tried to update for the very first time. if your update checker times out and doesn't do anything close to what mine does, and if you cannot get sufficient answers from AT&T or Samsung - then i personally would take the phone back, as amazing as it is. while this OTA update may not be very "important," as others have stated, there will eventually be some "important" OTA updates, and i would not want to risk missing out on those!

hope this helps a little bit, if anyone is still checking this thread/having this issue.
 
mfpearson,
There is another thread that discusses this as well, but in a nutshell there appeared to be a problem with a number of us (me included) not receiving the update. Instead, we were consistently receiving an "unable to connect to ATT server" response after waiting 3-5 minutes. Further comparison of our experiences showed that the one consistent fact among those of us reporting the problem was that we were all located in the MD/DC/VA area. It was also discovered that some who had not been able to receive the update got it when they traveled out of the area I described. For example, traveling to NC or PA.

We did contact ATT and Samsung, multiple times, without success. Regarding your comment about taking it back, I did that. The new phone behaved exactly the same way. Based on our collectiove experiences it was pretty evident to us that it was unlikely to be a problem with the phone itself, and that has proven to be true.

In any event, whatever the problem or issue was it seems to have been resolved as of yesterday. Whether there was actually a problem fixed, or something in the order in which the update is rolled out, I don't know. But I received the update yesterday after not being able to receive it since its release in early June.
 
mfpearson,
There is another thread that discusses this as well, but in a nutshell there appeared to be a problem with a number of us (me included) not receiving the update. Instead, we were consistently receiving an "unable to connect to ATT server" response after waiting 3-5 minutes. Further comparison of our experiences showed that the one consistent fact among those of us reporting the problem was that we were all located in the MD/DC/VA area. It was also discovered that some who had not been able to receive the update got it when they traveled out of the area I described. For example, traveling to NC or PA.

We did contact ATT and Samsung, multiple times, without success. Regarding your comment about taking it back, I did that. The new phone behaved exactly the same way. Based on our collectiove experiences it was pretty evident to us that it was unlikely to be a problem with the phone itself, and that has proven to be true.

In any event, whatever the problem or issue was it seems to have been resolved as of yesterday. Whether there was actually a problem fixed, or something in the order in which the update is rolled out, I don't know. But I received the update yesterday after not being able to receive it since its release in early June.

yeah, i just came across the main thread discussing this. glad you all got it worked out, and don't have to take the phone back! that would be a shame, since this phone is truly incredible.
 
not sure if you all are still having problems with this, but i just wanted to offer some information on how it is SUPPOSED to work (i think), as it seems that none of you have even come close.

when i go to menu -> settings -> software update, it takes me to the "device management" screen.

from there, i have 2 options: "check for updates" and "continue update" - but "continue update" is always greyed out.

when i select "check for updates," i get a new screen that reads: "Software update process will not delete any personal data on your phone. Check the AT&T server for a new software update?"

then, there are 2 buttons at the bottom: "OK" or "cancel"

when i hit the "OK" button, i get a message that says: "Current software is up to date you may check again in: 24 hours 4 mins."

This is exactly what I do - and I get exactly the same message returned. "Current software is up to date....." The only difference it that is says my phone's Build Number is UCKD5. I got the phone the first day it was available. I haven't rooted or anything like that. I'm on the West Coast.
 
artbytes,
That message you are getting is what you see if it has been less than 24 hours since you last checked. You can get around that by going into Settings->Applications->Manage Applications->Running, look for Device Management, select it and Clear Cache.

Have you ever gotten the "unable to connect to ATT server" message? As previously described, the problem some of us were seeing (related in this forum and at least one other) was the apparent inability to connect to ATT's server. We would see the message you describe only if we tried again too soon after the last attempt and didn't clear the cache. Once up-to-date you should get a message saying that. Might be something else going on with your phone, assuming others in your area are able to get the update.
 
That message you are getting is what you see if it has been less than 24 hours since you last checked. You can get around that by going into Settings->Applications->Manage Applications->Running, look for Device Management, select it and Clear Cache.

Once I did the above, I turned off my wireless (Continously hung during Download) I used the H+ to retrieve the download and it finally completed. i am now showing the current Version as UCKH1.
 
I had not yet been notified it was available, but based on the postings here I checked for the update. Unlike the problems some of us had getting the previous update I had no problems with this one. I too am now at H1.
 
Back
Top Bottom