Database Info

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.

OTA Update?

Anyone else get an update text message from AT&T? I am running Assonance 2.0
Sent from my SAMSUNG-SGH-I897 using XDA App

Yea I got a text running perception 5. Not sure its froyo or a really late text for jh7.

I've been getting them for the last few days, though I'm not willing to flash to find out lol....

I got it shortly after flashing to cognition 2.3b6 - checked for new OTA updates and didn't get anything.

Just tried and failed to connect to server.. though it's probaly nothing. Been a lot of posts about people getting texts to update (I haven't gotten one, I'm running stock JH7). I think it's just AT&T trying to get everyone to update to JH7.

From androidforums.com:
"This has been happening for a while now. People who are running anything other than Samsung/AT&T firmware have been getting these notices."

Stock
JimmehDean said:
Anyone else get an update text message from AT&T? I am running Assonance 2.0
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Nope. Stock.

1. AT&T doesn't know what firmware you are running. They are STILL sending out general update notifications to remind people to update to JH7.
2. There are two other threads in the forum, on the front page discussing the same topic...LOL. Come on guys.

For whatever it's worth, I spoke with three AT&T techs today, from common answerer, all to UPPER LEVEL WIRELESS TECH, and the answers I got from all three, screwed my thinking, which at times, AT&T does well. The OTA to side-load they been speaking of, IS NOT A SOFTWARE UPDATE, as I thought it had to be, but online instructions, on how to make am adjustment, Menu, then Settings, to stop BLOCKING the install of NON MARKET APPS, like from Amazon. I thought the OTA, was a software 'patch' that would fix the blocking of apps not from the Market, but they all told me, that the OTA, was really a set of steps, that showed you how to make the MANUAL ADJUSTMENTS, on my Captivate. Maybe I'm the only one feeling like an idiot over this, but that is how I was left feeling. They sent not one, but two different text mess., that for some reason, didn't do a thing, so the upper level tech, tried walking me through the adjustment, his own self, but he flat failed to tell me how. He finally suggested, that since it was Amazon's appstore app I was trying to install, and my Captivate still was BLOCKING the install, to ask AMAZON for help, in case THEY KNOW how to make the adjustments on the Captivate, or better, to ask SAMSUNG, since it's their phone. The guy was nice..., but why do I feel shafted for paying outrageous premiums for service from AT&T, but when I ask for help, I get shoved along to someone else, for them to help me?
Has anyone heard, that the OTA, is NOT SOFTWARE, but actually instructions, to make in your phones settings? If anyone could give a rational explanation of this to me, I'd appreciate it. My AT&T Samsung Captivate, is a great phone, to me, but AT&T, leaves a lot to be desired. Any suggestions?

Please don't hijack threads.
Anyways if it is instructions then they will need to push out an ota to even enable the option. They removed the option to prevent people from enabling it to begin with.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

AT&T updates
JimmehDean said:
Anyone else get an update text message from AT&T? I am running Assonance 2.0
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Last night my wife's phone completely hung. Had to use 3-button combo to get into recovery and reboot. After reboot, Device Management was running endlessly. Tried to kill it but it wouldn't stop. Tried to use TIBU to freeze it but TIBU wiuldn't open. Finally killed it by clearing Device Management data. Went into TIBU again and froze it. Unbelievable. Her phone is stock 2.2 but rooted. 2 hours later, I noticed on my phone that Device Management was running (notification bar). Went through the same sequence to kill it and freeze it. I will never defrost this!!

On my stock 2.2 not rooted cappy it was enabled just by turning the phone off and back on a couple of days ago.
Sent from my SAMSUNG-SGH-I897 using XDA App

ffman2152 said:
For whatever it's worth, I spoke with three AT&T techs today, from common answerer, all to UPPER LEVEL WIRELESS TECH, and the answers I got from all three, screwed my thinking, which at times, AT&T does well. The OTA to side-load they been speaking of, IS NOT A SOFTWARE UPDATE, as I thought it had to be, but online instructions, on how to make am adjustment, Menu, then Settings, to stop BLOCKING the install of NON MARKET APPS, like from Amazon. I thought the OTA, was a software 'patch' that would fix the blocking of apps not from the Market, but they all told me, that the OTA, was really a set of steps, that showed you how to make the MANUAL ADJUSTMENTS, on my Captivate. Maybe I'm the only one feeling like an idiot over this, but that is how I was left feeling. They sent not one, but two different text mess., that for some reason, didn't do a thing, so the upper level tech, tried walking me through the adjustment, his own self, but he flat failed to tell me how. He finally suggested, that since it was Amazon's appstore app I was trying to install, and my Captivate still was BLOCKING the install, to ask AMAZON for help, in case THEY KNOW how to make the adjustments on the Captivate, or better, to ask SAMSUNG, since it's their phone. The guy was nice..., but why do I feel shafted for paying outrageous premiums for service from AT&T, but when I ask for help, I get shoved along to someone else, for them to help me?
Has anyone heard, that the OTA, is NOT SOFTWARE, but actually instructions, to make in your phones settings? If anyone could give a rational explanation of this to me, I'd appreciate it. My AT&T Samsung Captivate, is a great phone, to me, but AT&T, leaves a lot to be desired. Any suggestions?
Click to expand...
Click to collapse
What is with all of the commas? Load a rom and don't worry about any ota from AT&T!
This is my Captivate. There are many like it but this one is mine

no problem here rogers Canada ftw side loading enabled from the beginning. and as for the messages if you want them to stop just block them. and chances are if your on this site you have sideloading anyways

Help with borked wallet

No matter what i do, rom i flash, partition i wipe.... wallet force closes and does not work. i am using the nexus 4g. even if i unroot and roll back to 2.3.4 wipe everything multiple ways, accept ota updates just like i did before, wallet fails.
so ive rooted and unrooted before 2.3.7, took the ota and everything was dandy.
all i did was root a few days later and it was done. i am convinced there is some data on the nfc chip just like data was being saved on the gps when switching certain evo roms. Why would simply rooting the phone break wallet when sooo many people are running it rooted? almost wanna take it to sprint....

You need the ke1 radio for it to work on 2.3.7 without hacking it on there
Sent from my Nexus S 4G using xda premium

Rem3Dy said:
You need the ke1 radio for it to work on 2.3.7 without hacking it on there
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Yes remember this is a now unrooted sprint nexus returned to stock with all the proper radio's and all...

Bump
suggestions anyone?
tried taking it to sprint but didnt have time to stick around and wait a few hours....

Same thing happened to me, I called google wallet support they blamed it on me unlocking the bootloader and flashing a custom rom. Basically you're sol unless you can swap it out at sprint. as far as I know. Google isn't responding to this issue.
Sent from my Nexus S 4G using xda premium

rican408 said:
Bump
suggestions anyone?
tried taking it to sprint but didnt have time to stick around and wait a few hours....
Click to expand...
Click to collapse
Also, make sure you're copying the 2.3.7 versions of:
com.android.nfc_extras.jar > system/framework
com.google.android.nfc_extras.xml > system/etc/permissions.
If you know how to sign APKs, make sure Wallet and Nfc have the same signature. If you don't know how, copy over Nfc as well to system/app and wipe cache either way.
Hope that works. Good luck.

Returned the phone to sprint overnight. Wow. The sales people and techs there are completely clueless. Oh well. After me schooling them on everything, they decided to give me a new phone. It will be shipped in a few days.

rican408 said:
Returned the phone to sprint overnight. Wow. The sales people and techs there are completely clueless. Oh well. After me schooling them on everything, they decided to give me a new phone. It will be shipped in a few days.
Click to expand...
Click to collapse
You mean refurbished phone?
Sent from my Nexus S 4G using xda premium

Probably refurbished. From what I understand these phone go through more tests than new phones and still look new. I'm fine with that. If the phone continues to fail (which I doubt) then I can get a new phone.

So I got a new phone from sprint. Interesting I had to set up a new Google prepaid card. Got another 10 bucks...

rican408 said:
So I got a new phone from sprint. Interesting I had to set up a new Google prepaid card. Got another 10 bucks...
Click to expand...
Click to collapse
yea, the prepaid card is tied to the phone's meid. New phone = new meid.
Actually, the whole gw app is tired to the meid. I'm talking to the money market level 2 guys trying to figure out how I funked mine up so badly without swapping phones
Sent from my Nexus S 4G using xda premium

The key is to flash the wallet fix rite on top of the rom you flash. In the same recovery session. Works everytime.

snandlal said:
The key is to flash the wallet fix rite on top of the rom you flash. In the same recovery session. Works everytime.
Click to expand...
Click to collapse
Nope. Did not work for me. Mine was done no matter what I did.

Issues Accepting OTA

I had to reset my phone back to stock due to some issues with data/signal issues. I'm now not able to accept the ota vrlg7 every time i hit check for update it says service unavailable. I have my imei, stock,bootloader locked back. Im able to get on the internet so I know data isnt an issue as far as connectivity..

Maybe try a factory reset from inside touchwiz?

fr8cture said:
Maybe try a factory reset from inside touchwiz?
Click to expand...
Click to collapse
tried that a no go..I have a replacement coming tomorrow so i guess i could wait it out...Its my fourth one...

I had the same issue. I called support and they sent me a new sim card. Once I threw it in there and it activated the error went away. I would call or go into a store and get a new sim.

Hate to tell you but you probably need a new phone. I was getting that message with my first GS3. I took it to the store I bought it at and they tried a new sim...same message. They didn't want to, but I demanded they give me a new phone. I paid full retail price for the phone, so I didn't want it replaced with some refurb piece of junk.
I commented before reading further posts. Hope your replacement is good.
Sent from my SCH-I535 using xda app-developers app

I have this problem too. I wonder how many people have this problem and don't know it? Not everyone is as update happy as the people on this forum are..... Myself included
Sent from my SCH-I535 using xda premium

The new replacement solved the issues..but decided to get new sim as well just to make sure..I am not 100% sure but Im beginning to think that some of the peoples issues may lie within flashing certain roms and zip alterations and causing hardware issues... I could be wrong but the thought has crossed my mind

antawnm26 said:
The new replacement solved the issues..but decided to get new sim as well just to make sure..I am not 100% sure but Im beginning to think that some of the peoples issues may lie within flashing certain roms and zip alterations and causing hardware issues... I could be wrong but the thought has crossed my mind
Click to expand...
Click to collapse
I have never rooted or flashed any rom on this phone, 100% stock. This started a few days after the last update.

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