Database Info

Evo then Droid... get off your ass Samsung

Can you please get Froyo to the Galaxy S owners!?!
http://www.engadget.com/2010/08/11/motorola-droid-android-2-2-froyo-ota-updates-are-go/

I'd be willing to hold off on 2.2 if they would fix the gps, the app lag, and the craptastic battery life.

I'm willing to bet that at&t are the ones holding this up, adding their "software."
Sent from my SAMSUNG-SGH-I897 using XDA App

behrouz said:
I'm willing to bet that at&t are the ones holding this up, adding their "software."
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Have to agree, AT&T probably needs to add it's crapware before releasing this.
Sent from my SAMSUNG-SGH-I897 using XDA App

Didn't they already announce that it wouldn't be available till September for the international GalaxayS?

Are you kidding me?
Captivate has been out 3 weeks... and you think it should have Froyo already?
I can wait. Let Samsung get it right first.

Froyo will be out in sept for I9000. We then have to wait for At&t to update and release it. If a froyo kernel is leaked for the captivate we can use the I9000 froyo rom.

joeybear23 said:
Are you kidding me?
Captivate has been out 3 weeks... and you think it should have Froyo already?
I can wait. Let Samsung get it right first.
Click to expand...
Click to collapse
That is what I was thinking. A lot of people think it takes a couple of minutes to crank out the new update to froyo for the Galaxy S phones. It takes time and a lot of coding and debugging to ensure maximum compatibility and stability with the new Froyo update. I prefer to wait and make sure the kinks get worked out.
At least we know they are working on updating to froyo since we have seen various I9000 froyo leaks, so now the best thing to do is wait and make due with what we have.

I have to agree with the concesus here, this phone is already blazing fast and its going to take time to port froyo to operator specific phones. Motorola just needs to deal with verizon whereas Samsung is dealing with 8 carriers ALL with different hardware... Not something that is easy.
Best thing you can do turn off live wallpaper and install LauncherPro and call it a day. Increase battery life and speed... Done and Done!

slider2828 said:
Motorola just needs to deal with verizon whereas Samsung is dealing with 8 carriers ALL with different hardware... Not something that is easy.
Click to expand...
Click to collapse
Make that 110 carriers. However, the core functionality of all these phones are almost the same. I'd say (just a guesstimate) around 95% of the hardware are similar. The software side maybe more different as pre-loaded software have to be considered.

OMG, Why don't we just go find the old threads for the blackjack and blackjack II WiMo upgrades. Do a little find and replace, paste the results here and stop wasting our time having this conversation again.
It will be realeased when it is released. Samsung is notorious for slow updates so we have to deal with it. After all we are all here on XDA which means almost every last one of use will flash a Froyo ROM long before the official update is released.

I was at the mall yesterday went to ATTto ask if they new when update is coming out. He said GPS will be end of Aug and Froyo is coming Mid-Sept.

ViniD said:
I was at the mall yesterday went to ATTto ask if they new when update is coming out. He said GPS will be end of Aug and Froyo is coming Mid-Sept.
Click to expand...
Click to collapse
And if you call ATT I bet they will give you some type of date. I will then gaurantee you that date will come and go with no update. This is par for the course when waiting for samsung OS updates on the ATT network. I think it was the blackjack I was waiting on. There were several dates, all confirmed by an ATT Rep. It took well over 6 months from the first date before we saw the update. So don't hold your breath.

So, I'm running JI6 and I just got this notice...

So, I'm running JI6 and I just got this notice...
"AT&T is providing a free update for your phone. When asked to install the update, please select OK."
Shouldn't this only appear when running 2.1 builds?

did you install it to see what it was?

DOAlaboratories said:
did you install it to see what it was?
Click to expand...
Click to collapse
That would sure be interesting to know...thinking just the crappy JH7 update, but the hopefull in me is very curious...

I actually got the same thing today but I'm avoiding it like the plague.
No chance in hell the ATT can provide me something as amazing as cognition2.2

Heh...
So, I got the same message from AT&T as OP a few hours ago, and I just noticed a "Could not connect to the server" window. I'm guessing that by running Cog2.2 on my phone, the server won't push the update to it given that it isn't running an official build.
Oh well

I can test this later as i have flashed back to stock 2.1, after testing JI6, and experiencing issues with key apps i use on a day to day basis. but i am curious to see about this update. I mean the most harm it could do is a software related "brick" right?
Sent from my SAMSUNG-SGH-I897 using XDA App

Furthermore, it states on my JH7 build that no user data would be lost - is this an over the air Froyo? I'm running 2.1 and already did the first update for JH7, so what is this?

GarciaM25 said:
Furthermore, it states on my JH7 build that no user data would be lost - is this an over the air Froyo? I'm running 2.1 and already did the first update for JH7, so what is this?
Click to expand...
Click to collapse
You're running JH7 and got this message? Interesting...
Sent from my SAMSUNG-SGH-I897 using XDA App

CLShortFuse said:
You're running JH7 and got this message? Interesting...
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yep, and the bad news is....... I can't say what the hell the update was for considering it sat "preparing" it for a while, then failed to update, not unlike the issues others were having when putting on JH7 (mine updated right away, but my girlfriend's did not) - just tried to roll it a day forward to trick it, and it showed no update available! Will keep working on it, but there can't be just TWO of us who have seen this message when waking up this AM....

It will be the same JH7 OTA. AT&T just started sending out SMS to random Captivate owners. Nothing new. There is no way, nor AT&T cares, for AT&T to know you have updated to other firmware or not via SMS. They probably picking you out of the ppl who haven't tried to do OTA update.

Every Captivate user will receive this text message once, regardless of what version they are on. AT&T can't see what version of Android OS you are running. What they are doing is sending a text message to all users that are showing a Captivate on file in chunks. I haven't received that message yet, but even though I'm running Froyo via Cog 2.2, I'm still gonna get this message at some point.
Just ignore it unless you really want to play with their over the air update (which apparently bricks phones if you've ever altered it from stock in any way, even if you Odin back to JF6....)
Personal opinion? Ignore it. CL, continue the great work you are doing on the Jupiter.xml edits / development. I read into your posts at least every other day.
Thanks folks,
-h8

h8rift said:
Every Captivate user will receive this text message once, regardless of what version they are on. AT&T can't see what version of Android OS you are running. What they are doing is sending a text message to all users that are showing a Captivate on file in chunks. I haven't received that message yet, but even though I'm running Froyo via Cog 2.2, I'm still gonna get this message at some point.
Just ignore it unless you really want to play with their over the air update (which apparently bricks phones if you've ever altered it from stock in any way, even if you Odin back to JF6....)
Personal opinion? Ignore it. CL, continue the great work you are doing on the Jupiter.xml edits / development. I read into your posts at least every other day.
Thanks folks,
-h8
Click to expand...
Click to collapse
That's right.. this is the forced JH7 official OTA update that it detects you haven't received it.

h8rift said:
Just ignore it unless you really want to play with their over the air update (which apparently bricks phones if you've ever altered it from stock in any way, even if you Odin back to JF6....)
Click to expand...
Click to collapse
It doesn't brick the phone, it just will fail during install, that's all. So your phone will remain in the same state since nothing will have been installed.
Sent from my SAMSUNG-SGH-I897 using XDA App

himmelhauk said:
It doesn't brick the phone, it just will fail during install, that's all. So your phone will remain in the same state since nothing will have been installed.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
For most, your phone will stay in quasi state: neither JF6, not JH7. And probably will never be able to upgrade again via either OTA or Kies. You have to Odin it.
For some, it actually bricks their phone, i.e. can't boot pass the logo screen.

foxbat121 said:
For most, your phone will stay in quasi state: neither JF6, not JH7. And probably will never be able to upgrade again via either OTA or Kies. You have to Odin it.
For some, it actually bricks their phone, i.e. can't boot pass the logo screen.
Click to expand...
Click to collapse
I have heard of very few people who have bricked there phone doing the OTA Update. For almost everyone the update fails and the phone boots into you previous ROM and gives you a message that no changes have been made to your phone.
Brick is a strong word to use. Brick indicates the phone has no hope of being used again. You can almost always ODIN your phone if all else fails.

KewlRobD said:
I have heard of very few people who have bricked there phone doing the OTA Update. For almost everyone the update fails and the phone boots into you previous ROM and gives you a message that no changes have been made to your phone.
Click to expand...
Click to collapse
Actually, from what I read here, most failed update will show your phone is already at JH7 but none of the JH7 features are there. So, no, it does not boots into previous ROM.

So I called Samsung about the OTA firmware failing on my Captivate. I had to use ODIN at one point, so that's why it failed supposingly. Samsung said that there was an issue with v1 of the firmware update and there is now a v2, however Samsung couldn't tell me baseband version and they told me to call AT&T.
I called AT&T and asked them about this v2. They said that firmware I897UCJH7 has been released to fixed various bugs, some other items, and she specifically said GPS. So, I'm not sure what Samsung was meaning by v2, unless they meant this JH7 was v2 and what came on the phone out of the box was v1.
While I had AT&T on the phone I thought I'd ask about Android 2.2 and when it was going to be released. The AT&T rep said, "Hang on while I Google that for you." I was like WTH, really? This is where AT&T gets their information I guess... HA

Alot of times they google my questions. They do it for most questions that don't involve can't receive text and whatnot. Feature phone, they can help, smart phone, no way in hell.
From a phone on an app

I'm running stock 2.1 with root and I have the message. I will back up and reflash later tonight to see if I can download it and put it up for y'all. But currently, it fails the same way op described.
Sent from my SAMSUNG-SGH-I897 using XDA App

gk527 said:
So I called Samsung about the OTA firmware failing on my Captivate. I had to use ODIN at one point, so that's why it failed supposingly. Samsung said that there was an issue with v1 of the firmware update and there is now a v2, however Samsung couldn't tell me baseband version and they told me to call AT&T.
I called AT&T and asked them about this v2. They said that firmware I897UCJH7 has been released to fixed various bugs, some other items, and she specifically said GPS. So, I'm not sure what Samsung was meaning by v2, unless they meant this JH7 was v2 and what came on the phone out of the box was v1.
While I had AT&T on the phone I thought I'd ask about Android 2.2 and when it was going to be released. The AT&T rep said, "Hang on while I Google that for you." I was like WTH, really? This is where AT&T gets their information I guess... HA
Click to expand...
Click to collapse
The OTA update of JH7 is a special diff version with scripts in order to minize the download size (12 MB vs 120+MB). Obviously, the original script doesn't work very well. So, Samsung probably changed it so that it won't fail so easily. That's what Samsung means by v1 and v2. The final result, JH7, will be the same and you can easily do it via Kies Mini instead of playing Russian Roulette with OTA update.

[Q] Anyone try the new LG/Tmo update?

http://phandroid.com/2011/12/06/t-mobile-g2x-gingerbread-update-ota-resumes/ points to a new OTA from Tmo/LG. I think its the July update, but I'd like to confirm that there isn't anything more to it. Anyone know?

So that means NO ICS!!!! Time to shop for another phone possibly?? How could a phone so great be in so much hot water?

XMarinE said:
So that means NO ICS!!!! Time to shop for another phone possibly?? How could a phone so great be in so much hot water?
Click to expand...
Click to collapse
Huh? LG already stated they would make an ICS update for us. Plus CM9 has already been made for this phone. So we're getting ICS either way.

tmonews reported this update as a re-roll out for anyone who missed the OTA update from July. Has nothing to do with any future ICS eligibility and there's probably nothing new.

So this update is nothing different than the one that was released in July?

This is a little bizarre.
Sent from my LG-P999 using XDA App

tidewaterns said:
So this update is nothing different than the one that was released in July?
Click to expand...
Click to collapse
Yes it's the same. I remember calling t-mobile in the first week of August because I never got the ota, and I checked everyday since its release. They told me back then that I could be put on a list and wait to receive the ota once they decided to roll it out again, or use the lg updating software on the lg site. I went with the latter.
I can't believe it took them this long for the re-roll out! They are moving these ota's at a snails pace. In conclusion if you don't have a nexus then you know the word OTA is just a damn over-hyped buzz word.

I never got an OTA. Just some speal about the LG updater.
OTA = bricking your G2x using the LG Updater tool and getting repaired = Bada Boom!
G2x - 2.3.7 CM7
Transformer - 3.2 Revolver OC/UV

Software Update Service Unavailable

Just got my Galaxy S III on Friday. It's on 4.0.4 right now, and I'm just checking to see if there's an update available and I get this message:
Service unavailable
Check for System Updates under Settings > About device when service is available
If it helps, I've disabled most of the Verizon apps that are included on the phone, but I don't think that would affect anything. *I enabled all of the apps that I disabled, but it's still giving me the same message when I try software update.
I also reset my phone to factory and it still did it.
If there wasn't an update, it would say something like "You are up to date" Right?
Thanks

Depends on which verizon apps. The software update comes from verizon.
Sent from my SCH-I535 using xda app-developers app

Disabling stock software can definitely stop an OTA update from installing.

Ok, I re-enabled everything and tried software update again and it's still saying the same thing... :/

Can anyone help, is this a fault with my phone?
I want to find out before my 14 day return/exchange policy is up :/

Josh...my wife has a thunderbolt and is getting the same thing...her phone booted into boatloader today which I thought was funny since she is straight stock...its not your new phone its them.
Sent from my SCH-I535 using xda app-developers app

jcandrew said:
Josh...my wife has a thunderbolt and is getting the same thing...her phone booted into boatloader today which I thought was funny since she is straight stock...its not your new phone its them.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I hope so! Would suck to not be able to update to Jelly Bean...whenever Verizon lets it come...

I'm in the same dilemma. I called Best Buy where I upgraded my phone last Friday and they said they've never heard of this. Chances are I might try to have them replace it with a phone that will update.

nike_air3 said:
I'm in the same dilemma. I called Best Buy where I upgraded my phone last Friday and they said they've never heard of this. Chances are I might try to have them replace it with a phone that will update.
Click to expand...
Click to collapse
Had my phone for a while and i get no such message... mine shows ....................No new software update available.........just did software check a cpl of of times to see if i would get your message and no.

crazydad said:
Had my phone for a while and i get no such message... mine shows ....................No new software update available.........just did software check a cpl of of times to see if i would get your message and no.
Click to expand...
Click to collapse
I think its their server. I just wiped clean all the way back to the original stock image and then tried to get the OTA, and was getting the same message. It worked on monday night...not sure what happened to them since. Oh well, I was going to make a nand backup of my phone with the OTA.

josh995 said:
Just got my Galaxy S III on Friday. It's on 4.0.4 right now, and I'm just checking to see if there's an update available and I get this message:
Service unavailable
Check for System Updates under Settings > About device when service is available
If it helps, I've disabled most of the Verizon apps that are included on the phone, but I don't think that would affect anything. *I enabled all of the apps that I disabled, but it's still giving me the same message when I try software update.
I also reset my phone to factory and it still did it.
If there wasn't an update, it would say something like "You are up to date" Right?
Thanks
Click to expand...
Click to collapse
i have the same issue. i checked on my GNEX and no issue. move the sim to my S3 and cant check for updates.WTF...not sure what the deal is. i have gone as far as restoring using ODIN back to the ROM that was shipped with the phone and same result. I know i have had some odd issues with this phone...its been locking up, GPS causes the phone to reboot (not all the time tho). im ready to go back to VZW and swap it out. Im back on stock, NO ROOT,NO NOTHING, just pure stock.

I just recently started getting the same error too. You are not alone my friend.
Sent from my SCH-I535 using xda app-developers app

josh995 said:
Just got my Galaxy S III on Friday. It's on 4.0.4 right now, and I'm just checking to see if there's an update available and I get this message:
Service unavailable
Check for System Updates under Settings > About device when service is available
If it helps, I've disabled most of the Verizon apps that are included on the phone, but I don't think that would affect anything. *I enabled all of the apps that I disabled, but it's still giving me the same message when I try software update.
I also reset my phone to factory and it still did it.
If there wasn't an update, it would say something like "You are up to date" Right?
Thanks
Click to expand...
Click to collapse
thanks you for healing Q?

Same error for me today. I'm totally stock and have been since I bought the phone. I'm not going to worry about until there's an update.
Sent from my SCH-I535 using xda premium

I'm in the same boat, I'm not rooted and get the same Service Unavailable error. That's some BS.

Please read forum rules before posting
Questions go in Q&A
Thread moved
FNM

Just to let you all know I wound up having to get a new phone. The guys in the store all tried telling me that nothing was wrong with my phone, and that the update would come to me 'eventually.' Kept telling me I don't need a new phone.
I had only had the phone for 6 days, and the return/exchange policy is 14, so I demanded they give me a new phone. They said "The new phone's gonna do the same thing dude."
So I get a new phone, and the first thing it does when it's powered up and set up...."UPDATE AVAILABLE!"
I said "Gee, imagine that."
Don't take no for an answer.

Anyone know what controls updates? I cleared data for "sdm" which is part of the check but I don't know what else is. It's pushing and pulling data when checking for an update but always comes back with service unavailable. If this doesn't work when I the next ota comes out I guess verizon is giving me permission to root and install a custom recovery
Sent from my SCH-I535 using xda premium

Are verizon customers able to update via Kies or is that international only? That might be a way around this problem?
Google says yes.... Should have check that first.... Sorry.
Sent from my SCH-I535 using xda premium

Mine has been saying the same thing.
Sent from my SCH-I535 using Tapatalk 2

Update rolling out Soon

I spoke to a rep the other day regarding Jelly Bean. Long Story short he said it is rolling out to their systems now (computer support info) so we should have it very very VERY soon.
Sent from my SCH-I535 using Tapatalk 2

Your title gives the impression that it'll be JB
Edit : you edited your post.
Sent from my SCH-I535 using xda premium

blestsol said:
Your title gives the impression that it'll be JB
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!

First mistake is assuming the reps have a clue about what they are talking about. They are lucky to dress themselves for work every morning. If I had a nickel for every time a rep told me an update is coming, I'd be a thousandaire.

ddurandSGS3 said:
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
Click to expand...
Click to collapse
I think when he says a small update he is describing his post as a small update to here. No the actually Verizon update.
Of course the next Verizon update will be JB. They do not need to make our phone ready for JB, it is ready and the leak we have also says it is pretty ready to go.....

Yes to Jellybean. Sorry for the confusion.
Sent from my SCH-I535 using Tapatalk 2

ddurandSGS3 said:
actually, it implies the opposite. his post in sort of confusing though.
hopefully a small update is making the phone ready for the update. anyone whos waited before trying jb will be happy!
Click to expand...
Click to collapse
I'm familiar with your posts in other threads. Carry on.
Sent from my SCH-I535 using xda premium

Never trust verizon reps....

I know a bunch of people who work for Verizon corporate.
I tell THEM when builds/phones are coming. I just updates their store model M to JB on Friday. They had no idea
Sent from my SCH-I535 using Tapatalk 2

Delete.
Sent from my Galaxy Nexus using xda app-developers app

The leak seems more stable than the ICS official to me...
I think these delays are more of a marketing strategy of sort rather than a real technical time to get it ready.... I might be wrong but...

Well VZW is going to have to do something either right before or same day the Note 2 comes out.
Sent from my SCH-I535 using Tapatalk 2

It seems more of a marketing strategy because t mobile released theirs after the note 2 was released.
Sent from my SCH-I535 using xda app-developers app

Verizon lies to there customers. When I bought the galaxy nexus I had 2 weeks to return the device. Signal was terrible but, loved the phone otherwise. I contaced them and they said and update when be comming out that would fix the problem but it would be after the 2 weeks of me being able to return the phone....no update acctually for several months then I was stuck with the useless phone.
Sent from my SCH-I535 using xda premium

Well that depends, what's their definition of "soon".

Terry_blair said:
Verizon lies to there customers. When I bought the galaxy nexus I had 2 weeks to return the device. Signal was terrible but, loved the phone otherwise. I contaced them and they said and update when be comming out that would fix the problem but it would be after the 2 weeks of me being able to return the phone....no update acctually for several months then I was stuck with the useless phone.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Same kind of thing happened to me. I wasn't getting an OTA even though one had come out. I went back to the store to exchange and he was like "it takes a while to get to everybody" so I went home and called Verizon and he advised me to go back and demand replacement.
I went back and demanded a new phone and he was like "fine I'll give you a new phone but the new one is going to do the same thing."
Well, he gives me a new phone, same sim card, and what do you know... first thing to pop up on the screen???
UPDATE AVAILABLE!
I laughed to his face and told him I would never be doing business with his store again.
Sent from my SCH-I535 using xda app-developers app

josh995 said:
Same kind of thing happened to me. I wasn't getting an OTA even though one had come out. I went back to the store to exchange and he was like "it takes a while to get to everybody" so I went home and called Verizon and he advised me to go back and demand replacement.
I went back and demanded a new phone and he was like "fine I'll give you a new phone but the new one is going to do the same thing."
Well, he gives me a new phone, same sim card, and what do you know... first thing to pop up on the screen???
UPDATE AVAILABLE!
Click to expand...
Click to collapse
Did you manually check for an update not long before you got the new phone?
From recent discussion, it seems there is a counter being kept for each account that notes when the last query for an OTA was made and it does not allow for a new check after a certain timeframe (seems anywhere from 2-4 weeks) after the most recent manual pull attempt. If your phone is not yet in the active queue for an active OTA push, the prior attempt will naturally return no new updates . . . but subsequent checks won't actually determine if you are in the OTA queue or not until the timeout period, even if your account was placed into the OTA queue by that time. My understanding is that this helps them balance load of the OTA downloads to some extent. Eventually, the OTA will be pushed to your phone, regardless of manual check attempts. It takes patience to wait.
However, this is bound to your account info, so changing a SIM card in the phone can make it seem as if the phone and/or SIM was the problem, because your prior, manual attempt was made when you were not yet in the active OTA queue, subsequent manual checks will not actually perform a check for the OTA for a period of time since the prior manual check - even if you were recently added into the active queue, and then a new SIM essentially resets the counter in your account and performs a true check for the OTA: if you were placed into the queue while unable to actually perform a check just before the new SIM, the OTA will now download and look like a miracle.
So, it does take patience. I experience the above symptoms exactly as described for the prior OTA and merely waited for the OTA to be pushed onto my phone - they gave me a timeframe for that and they were correct.
- ooofest

ooofest said:
Did you manually check for an update not long before you got the new phone?
From recent discussion, it seems there is a counter being kept for each account that notes when the last query for an OTA was made and it does not allow for a new check after a certain timeframe (seems anywhere from 2-4 weeks) after the most recent manual pull attempt. If your phone is not yet in the active queue for an active OTA push, the prior attempt will naturally return no new updates . . . but subsequent checks won't actually determine if you are in the OTA queue or not until the timeout period, even if your account was placed into the OTA queue by that time. My understanding is that this helps them balance load of the OTA downloads to some extent. Eventually, the OTA will be pushed to your phone, regardless of manual check attempts. It takes patience to wait.
However, this is bound to your account info, so changing a SIM card in the phone can make it seem as if the phone and/or SIM was the problem, because your prior, manual attempt was made when you were not yet in the active OTA queue, subsequent manual checks will not actually perform a check for the OTA for a period of time since the prior manual check - even if you were recently added into the active queue, and then a new SIM essentially resets the counter in your account and performs a true check for the OTA: if you were placed into the queue while unable to actually perform a check just before the new SIM, the OTA will now download and look like a miracle.
So, it does take patience. I experience the above symptoms exactly as described for the prior OTA and merely waited for the OTA to be pushed onto my phone - they gave me a timeframe for that and they were correct.
- ooofest
Click to expand...
Click to collapse
Well I had been manually checking for like a week, however, I wasn't receiving an update that had been out for months. The phone was 2 updates behind!
The new phone with my same SIM updated instantly after it was set up. I didn't even have to manually check. And then it updated again. So I honestly believe there was something wrong with the phone. Very strange to not get an update that had been out for months, you know?
Sent from my SCH-I535 using xda app-developers app