Getting now ICS 4.0.3, very very slow download.
What??? Same version? Good to know they tried so hard to fix the bugs...
Sent from my Nexus S using Tapatalk
I take it you're referring to the stock ROM? I wonder if the rollout has restarted or if you're just in a test region. Shame it's still 4.0.3 though, I would have thought they would have incremented the build if they have incorporated all the fixes required...
Ics 4.0.3 MR1
MR1 is the build that was originally pushed out and then paused...have Google fixed anything at all?
This is a pretty poor way to treat Nexus owners, by definition we're all either devs or early adopters yet they still fail to keep us up to date or even issue a statement about what the problem is for weeks.
The update server was turned back on yesterday for both the Galaxy Nexus and Nexus S. So far nothing new has rolled out. The same versions that were on the server before they shut it down are what is being rolled out.
Same version or not, hopefully the 9020a's and 4g's of the world get something this time.
Do you have still "battery drain"
My idea is that they have pushed the OTA just because the OTA server is just one for both the nexus.....the different phone will recive they're own firmware as well.
wolf230 said:
My idea is that they have pushed the OTA just because the OTA server is just one for both the nexus.....the different phone will recive they're own firmware as well.
Click to expand...
Click to collapse
Well, this would be a nice joke
Let know for battery drain, 73% of download
I wonder...
TheManicGibbon said:
MR1 is the build that was originally pushed out and then paused...have Google fixed anything at all?
This is a pretty poor way to treat Nexus owners, by definition we're all either devs or early adopters yet they still fail to keep us up to date or even issue a statement about what the problem is for weeks.
Click to expand...
Click to collapse
Is it possible that the update version is still the same. Kinda like what happened when they release GB 2.3.6?
PhoenixIce22 said:
Is it possible that the update version is still the same. Kinda like what happened when they release GB 2.3.6?
Click to expand...
Click to collapse
It's still build IML74K so it is the exact same release.
Yeah if it was different in any way, it would have a different build number. The update that is rolling out OTA is EXACTLY the same as the one before it was paused.
Wouldn't it be nice if Google would bother to make a statement regarding weather they found a problem with 4.0.3 or not. Instead of just turning the servers back on and making everyone guess. It's not like they need a press conference, they could have just posted something/anything on G+ or Twitter.
Why choose to leave your customers in the dark constantly, especially as the main owners of the Nexus S are dev's for Google's Android community.
Sometimes you have to wonder what the **** Google is thinking.
bozzykid said:
It's still build IML74K so it is the exact same release.
Click to expand...
Click to collapse
yes, IMLK74
KERNEL 3.0.8 gb55e9ac [email protected]#1
petrochemicals said:
Why choose to leave your customers in the dark constantly, especially as the main owners of the Nexus S are dev's for Google's Android community.
Sometimes you have to wonder what the **** Google is thinking.
Click to expand...
Click to collapse
Complitely right
petrochemicals said:
Wouldn't it be nice if Google would bother to make a statement regarding weather they found a problem with 4.0.3 or not. Instead of just turning the servers back on and making everyone guess. It's not like they need a press conference, they could have just posted something/anything on G+ or Twitter.
Why choose to leave your customers in the dark constantly, especially as the main owners of the Nexus S are dev's for Google's Android community.
Sometimes you have to wonder what the **** Google is thinking.
Click to expand...
Click to collapse
I completely agree....I think if enough people ask them about it on G+ and twitter we may get an answer
So what was the point about pausing the OTA if it's the same build again?
AskingBen said:
So what was the point about pausing the OTA if it's the same build again?
Click to expand...
Click to collapse
good question!
I believe Google said that they paused the OTA to monitor feedback NOT to fix bugs, so how are they leaving us in the dark??
SupaDupaFly24 said:
I believe Google said that they paused the OTA to monitor feedback NOT to fix bugs, so how are they leaving us in the dark??
Click to expand...
Click to collapse
So far I know, Google said nothing. No official statements. Only thing was one post in helpdesk forums, when they said the OTAs can be on hold for specific region. No official cause was stated why or if it is on hold. That was a crowd created story.
Sent from my Nexus S using Tapatalk
Related
Seems like if Gingerbread is suppose to be official before the end of the year, something should have leaked by now. An early test build, some screenshots, maybe some video? All we have seen are a couple of shopped screenshots that show 3.0 as the build
Someone out there must know or have seen something Throw us a bone here!
It hasn't been leaked because you touch yourself.
Because people don't like breaking NDAs and losing their jobs?
Google will release it when they release it.
+1 to the poster above.
And judging by Froyo experience, I guess Nexus users will see "semi-official" test builds way before the official release, once these builds make it to beta stage.
x986123 said:
It hasn't been leaked because you touch yourself.
Click to expand...
Click to collapse
Ah, that's probably my fault then.
I'll stop for an hour or two and see if Gingerbread appears...
Jack_R1 said:
+1 to the poster above.
And judging by Froyo experience, I guess Nexus users will see "semi-official" test builds way before the official release, once these builds make it to beta stage.
Click to expand...
Click to collapse
Well that's what I'm saying. When Google showed Froyo at Google IO, it didn't OTA until almost 2 months after that. I was assuming that we would see a Gingerbread OTA before the end of the year. If timetables are similar that won't happen.
It just seems like we got more leaks and now its dried up lol
b0dge said:
Ah, that's probably my fault then.
I'll stop for an hour or two and see if Gingerbread appears...
Click to expand...
Click to collapse
best response i have seen here for ages
ROFLMAO
I don't think that anybody's even said that the next release will be version 3. It could be 2.3 or 2.5....
The only thing we've actually seen is some chicken little claiming that it would take a modern supercomputer to run it -- and THAT has been refuted.
... and time has PROVEN that EVERY chicken little making claims about the future of android is always wrong 100% of the time.
This year? lol, we won't see 3.0 until next year. IF we're lucky, Q1.
lbcoder said:
I don't think that anybody's even said that the next release will be version 3. It could be 2.3 or 2.5....
The only thing we've actually seen is some chicken little claiming that it would take a modern supercomputer to run it -- and THAT has been refuted.
... and time has PROVEN that EVERY chicken little making claims about the future of android is always wrong 100% of the time.
Click to expand...
Click to collapse
I personally like the "completely revamped UI!" bull**** you see floating around. My contact at Google confirms this is 100% fabricated bull****.
mortzz said:
I personally like the "completely revamped UI!" bull**** you see floating around. My contact at Google confirms this is 100% fabricated bull****.
Click to expand...
Click to collapse
You just killed everyone's mood. Thanks.
mortzz said:
I personally like the "completely revamped UI!" bull**** you see floating around. My contact at Google confirms this is 100% fabricated bull****.
Click to expand...
Click to collapse
There definitely is a change of some sort, you can see from the difference between the original voice search and the recent update.
x986123 said:
You just killed everyone's mood. Thanks.
Click to expand...
Click to collapse
and b0dge resumed his.... business....
Gingerbread doesn't begin until honeycomb is finalized.
JCopernicus said:
Gingerbread doesn't begin until honeycomb is finalized.
Click to expand...
Click to collapse
That makes no sense.
Rellikzephyr
Sent from my Nexus One using Tapatalk
JCopernicus said:
Gingerbread doesn't begin until honeycomb is finalized.
Click to expand...
Click to collapse
You do know that G comes before H, right?
a google campus recruiter was at my university today. he was playing with a nexus one so i told him that i have one also. he said his was different so I asked him why and peeked at his screen and he suddenly pulls down the notification bar and says "oh it has at&t". this seemed like a silly reason so i asked what build he was running and he told me he couldn't say. I asked if it was gingerbread and he said yes. i asked him if he could tell me about new features and he said no.
i got some google chapstick and a google pen though.
I have been hoping leaks would start soon considering Gingerbread is supposed to be unveiled in mid October. I expect to see devices in the latter part of Nov.
Just like when 1.0 was unveiled and 2.0 was unveiled. They were followed by a device about a month after.
nellyspageli said:
a google campus recruiter was at my university today. he was playing with a nexus one so i told him that i have one also. he said his was different so I asked him why and peeked at his screen and he suddenly pulls down the notification bar and says "oh it has at&t". this seemed like a silly reason so i asked what build he was running and he told me he couldn't say. I asked if it was gingerbread and he said yes. i asked him if he could tell me about new features and he said no.
i got some google chapstick and a google pen though.
Click to expand...
Click to collapse
Hmmm, interesting.
nellyspageli said:
a google campus recruiter was at my university today. he was playing with a nexus one so i told him that i have one also. he said his was different so I asked him why and peeked at his screen and he suddenly pulls down the notification bar and says "oh it has at&t". this seemed like a silly reason so i asked what build he was running and he told me he couldn't say. I asked if it was gingerbread and he said yes. i asked him if he could tell me about new features and he said no.
i got some google chapstick and a google pen though.
Click to expand...
Click to collapse
Cool story bro..
I know I am not the only one... man, when Froyo came out it was OCD.
As far as I know, gingerbread isn't even out yet. Just the sdk.
twflys said:
I know I am not the only one... man, when Froyo came out it was OCD.
Click to expand...
Click to collapse
Naw not really
Pretty sure Google wants to have the Nexus S come out first on the 16th and then OTA the update to us on the 17th or so
Yeah, ask again next Thursday. No reason to believe we'll see it before then.
pfmiller said:
Yeah, ask again next Thursday. No reason to believe we'll see it before then.
Click to expand...
Click to collapse
Unless the famous Football has anything to do with it. If I don't see a leak for the nexus by next wednesday, I'd be surprised
I'm pretty wrapped up in senseui 2.0 right now, gingerbread can wait
What's the point of waiting just for the next day to release the ota for n1? There's no real gain in that for google.
I suspect we'll have to wait longer than 1 day.
geemaan said:
What's the point of waiting just for the next day to release the ota for n1? There's no real gain in that for google.
Click to expand...
Click to collapse
How about they sell more Nexus S devices because geeks can't wait to get their hands on Gingerbread so they rush out to buy the phone anyways? Surely we all know it's coming to the Nexus S but look at the thread title, people are going nuts for Gingerbread as it is! LOL
Surely they could just do what Apple does and release the update the day before for the older phones but i guess we'll see
geemaan said:
What's the point of waiting just for the next day to release the ota for n1? There's no real gain in that for google.
Click to expand...
Click to collapse
There is a good reason to wait.
Now when the SDK is out all the developers can test their apps against the Gingerbread and fix all the bugs and incompatibilities.
What do you think would happen, if goog realeases their 2.3 update and some popular apps don't work anymore? This forum would literally explode with screams like "fix this immediately or else", "I hate google", "gingerbread killed my cat" and so on. Why google would do that to themselves?
Jw but how is doing the dial in update thing different from the check for updates in the settings?
Sent from my Nexus One using XDA App
There is no check for updates in the settings, that's how.
skunz35 said:
Jw but how is doing the dial in update thing different from the check for updates in the settings?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I'm sure he's doing both just in case one yields different results. Supposedly I've heard that the Settings Updater doesn't always check, but caches the answer for an allotted time. Doing a "checkin" actually goes out and pings google (or wherever) and comes back with a result after a few seconds. The Settings app just flat out tells you no.
@Rusty is says there is under the about phone section
Sent from my Nexus One using XDA App
skunz35 said:
@Rusty is says there is under the about phone section
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
No there isn't. That section doesn't 'check' for updates, it tells you the result of the last system check for updates, which is done automatically, or forced through the dialer.
Going to that part of the settings does not force a check.
Damn, beat me too it Clarky
geemaan said:
What's the point of waiting just for the next day to release the ota for n1? There's no real gain in that for google.
Click to expand...
Click to collapse
The point would be so that the Nexus S can be marketed as the first phone with Gingerbread.
Yeah they will probably either delay it to just after Dec 16th or release it some time next week. I'm betting on just after though.
pfmiller said:
The point would be so that the Nexus S can be marketed as the first phone with Gingerbread.
Click to expand...
Click to collapse
True, but its not like they would lose any buyers anyway.
The N1 is only sold as a dev phone. And how many ppl have a N1? compared to SGS or others...
Also, like when they released froyo...many apps didnt work with 2.2 and had to be updated.
There are alot of devs out there with a N1 as a devphone. Giving out 2.3 before the NS release thus giving time for the devs to update their apps before launch would give android better publicity. And happier customers
I dont know if this is an issue with 2.3 though...
(I know the SDK is out)
I was referring to 1 day vs 1 week or more. More seems more appropriate, as you all say.
The only place I'll be "checkin" with is the Development section chef's.
@Jqueru just tweeted update to AOSP is underway. Confirmed on android-build.
Just did a checkin, and checked, nothing and im in GB.
Too many people get the kicks outta saying random things like this on twitter.
No, this time it's real:
http://groups.google.com/group/android-building/browse_thread/thread/91172a81604c8a0
http://twitter.com/jbqueru/status/15825129372131328
mattinglis said:
Just did a checkin, and checked, nothing and im in GB.
Too many people get the kicks outta saying random things like this on twitter.
Click to expand...
Click to collapse
I think you've completely misunderstood what AOSP and OTA are. AOSP is basically the source code which ROM cookers (Paul O' Brien, Cyanogen etc) use to build their own ROMs. OTA is an update from, in our case Google, which updates a stock ROM to Gingerbread. Also the person who said this is in charge of the Android AOSP project so he's hardly some random person
mattinglis said:
Just did a checkin, and checked, nothing and im in GB.
Too many people get the kicks outta saying random things like this on twitter.
Click to expand...
Click to collapse
aosp isnt ota. checkin is useless for aosp.
mattinglis said:
Just did a checkin, and checked, nothing and im in GB.
Too many people get the kicks outta saying random things like this on twitter.
Click to expand...
Click to collapse
No, too many people don't understand what they're reading. Building GB in AOSP is the first step. That has to happen before any kind of OTA is even built, much less tested and pushed out to devices. So doing your checkin is rather pointless, because they're at step 2 or 3, and you're at about 8 or 9. And the Tweet is from an official, confirmed Google staffer.
So again, too many don't understand what they read and want to sound like they're somebody.
My bad, i do know what im doing, i just didnt read the original post properly.
thought it was another person claiming to have recieved the OTA.
mattinglis said:
My bad, i do know what im doing, i just didnt read the original post properly.
thought it was another person claiming to have recieved the OTA.
Click to expand...
Click to collapse
its ok. lots of folks here are qucik to tell others off, but im used to gherjing my sdfse. just the other day i werufs the ,smbfd but not before i did a bit of sdler to my sdjgfe3. with that being said, lets all sfjher our sdgyer from the sd3fn8 servers (damn blackberries)!
SoberGuy said:
No, too many people don't understand what they're reading. Building GB in AOSP is the first step. That has to happen before any kind of OTA is even built, much less tested and pushed out to devices. So doing your checkin is rather pointless, because they're at step 2 or 3, and you're at about 8 or 9. And the Tweet is from an official, confirmed Google staffer.
So again, too many don't understand what they read and want to sound like they're somebody.
Click to expand...
Click to collapse
what? google can send out an Over-The-Air update for gingerbread whenever they please. they already have the source code so why would they have to release the source to the public before the compiled rom?
nexusonemeover said:
aosp isnt ota. checkin is useless for aosp.
Click to expand...
Click to collapse
Wouldn't that be cool? Check out the latest code on your phone, compiles, installs..
greenlime812 said:
what? google can send out an Over-The-Air update for gingerbread whenever they please. they already have the source code so why would they have to release the source to the public before the compiled rom?
Click to expand...
Click to collapse
Becase that's the route they've chosen to go this time. Do they have to? No. They didn't with Froyo. But with GB they're doing AOSP first.
My guess is they've got a GB device already, and don't need early OTA releases to build hype.
Sent from my Sexy Nexy, courtesy of the fine developers of Tapatalk
Does this mean that we will have a working rom for Nexus One soon?
macsim said:
Does this mean that we will have a working rom for Nexus One soon?
Click to expand...
Click to collapse
Yes and no, lol. Google will push an OTA out to N1 devices at some point. We all know that. It could start today, it could start next week. No one really knows.
Now that the source is in AOSP, ROM developers here (and elsewhere, I suppose) will begin using the source to compile custom ROMs. You may start to see those before an OTA, you may see an OTA first.
As for what works? LOL, hopefully they all do, and hopefully they'll be bug-minimalized. (Is there such a thing as bug-free??)
It means you can build your own stock ROM
Sent from my Nexus One using XDA App
Zynon said:
It means you can build your own stock ROM
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Question about this:
Do you not need at least a leaked ROM to extract the necessary "proprietary files" before building? Sorry if this is a noob question. Just curious.
It means they not going to waste their time with the nexus one and let us build our own rom. That mean OTA for nexus user, no time soon. We'll see a custom rom first before we see a OTA. Nexus S is their baby now not Nexus one.
Imho even a vanilla AOSP rom would be great waiting for official OTA...
inconceeeivable said:
Question about this:
Do you not need at least a leaked ROM to extract the necessary "proprietary files" before building? Sorry if this is a noob question. Just curious.
Click to expand...
Click to collapse
No, I don't think the proprietaries are platform-dependant
stonec11 said:
It means they not going to waste their time with the nexus one and let us build our own rom. That mean OTA for nexus user, no time soon. We'll see a custom rom first before we see a OTA. Nexus S is their baby now not Nexus one.
Click to expand...
Click to collapse
+1
cheers
Hell Yeah!
http://www.engadget.com/2012/03/15/confirmed-ics-coming-to-the-nexus-s-in-the-next-few-weeks/
OTA for all countries or 4.0.5???
Hopefully it's more stable than 4.0.3 was.
Sent from my Xoom using Tapatalk
climhz said:
http://www.engadget.com/2012/03/15/confirmed-ics-coming-to-the-nexus-s-in-the-next-few-weeks/
OTA for all countries or 4.0.5???
Click to expand...
Click to collapse
What do you mean what is it? It will be ICS finally rolling out after all these months to all the variants. And yes, it will be a bug fix release to the T-mobile version that partially rolled out too.
Can wait for a DEV out there to get it hands dirty with it!!!
Some reliable sources say this time its the real deal.
obsanity said:
Some reliable sources say this time its the real deal.
Click to expand...
Click to collapse
That's what they always say. Not impressed.
Engadget shoulda have more specific details, e.g., the version. I have been rocking ICS since the stock ICS OTA rolled out to T-Mobile, and now AOKP.
Sent from my Nexus S using xda premium
063_XOBX said:
That's what they always say. Not impressed.
Click to expand...
Click to collapse
Engadget wouldn't post that information unless it was from a source inside of Google. Unlike some of these crack pot bloggers, they actually have real sources.
bozzykid said:
Engadget wouldn't post that information unless it was from a source inside of Google. Unlike some of these crack pot bloggers, they actually have real sources.
Click to expand...
Click to collapse
They used to....
obsanity said:
They used to....
Click to expand...
Click to collapse
If it was from an external source, they would tell you their sources. Since they didn't, then you can be almost 100% positive it was from someone inside of Google.
obsanity said:
They used to....
Click to expand...
Click to collapse
Myriam Joire is the real deal man. She has great sources, and I've yet to ever hear her say anything that hasn't been reliable, credible, and ultimately proven true.
Sent from my Nexus S using Tapatalk
Even I can estimate like this lol.
Sent from my Nexus S 4G using XDA
uansari1 said:
Myriam Joire is the real deal man. She has great sources, and I've yet to ever hear her say anything that hasn't been reliable, credible, and ultimately proven true.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Myriam is a guy.
karnoff said:
Myriam is a guy.
Click to expand...
Click to collapse
Uhh, no, Myriam is a woman according to her Engadget bio page. Yes, she may look like a man (all joking aside), but she is not.
I wish, it would have better battery life
Sent from my Nexus S using xda premium
The reason there is such a delay this time around has to deal with the fact google has removed the support from cdma devices officially. This means in order to supply updates, we have to wait for sprint. Currently Sprint is bitter about the who deal. We are the ones who will suffer in the long run.
Same for why the gnex for sprint isn't out quite yet.
lithid-cm said:
The reason there is such a delay this time around has to deal with the fact google has removed the support from cdma devices officially. This means in order to supply updates, we have to wait for sprint. Currently Sprint is bitter about the who deal. We are the ones who will suffer in the long run.
Click to expand...
Click to collapse
The release was pulled from T-mobile and never existed for AT&T. So unless you are saying those are CDMA carriers as well, your theory makes no sense. All 3 device types currently are waiting for an ICS update. Google is surely working to make that happen. But Sprint isn't holding up the release (at least not yet) because it doesn't even exist. And Google removing CDMA from ASOP has no bearing on the speed at which they provide the update. The process is the same. The problem is the lack of understanding of why CDMA was pulled from ASOP and the sensationalist articles spewing incorrect information has probably confused you.
Tired of waiting..
I think Google takes too long to release an OTA!
bozzykid said:
The release was pulled from T-mobile and never existed for AT&T. So unless you are saying those are CDMA carriers as well, your theory makes no sense. All 3 device types currently are waiting for an ICS update. Google is surely working to make that happen. But Sprint isn't holding up the release (at least not yet) because it doesn't even exist. And Google removing CDMA from ASOP has no bearing on the speed at which they provide the update. The process is the same. The problem is the lack of understanding of why CDMA was pulled from ASOP and the sensationalist articles spewing incorrect information has probably confused you.
Click to expand...
Click to collapse
I guess you work with stuff on a daily basis? This is a google phone, if you don't think GSM variants are not affected by google move to drop cdma support your mistaken. There is alot more that goes on behind the scenes the push code > compile > update. Countless documents, this need to get removed, shuffled and put back into order once again. Instead of google being about to push updates with the help of carriers, google and the nexus s is now fragmented. To ensure a proper release cycle it will take longer then expected. Pulling a phone from official support isn't like dropping your kids off at school.
lithid-cm said:
I guess you work with stuff on a daily basis? This is a google phone, if you don't think GSM variants are not affected by google move to drop cdma support your mistaken. There is alot more that goes on behind the scenes the push code > compile > update. Countless documents, this need to get removed, shuffled and put back into order once again. Instead of google being about to push updates with the help of carriers, google and the nexus s is now fragmented. To ensure a proper release cycle it will take longer then expected. Pulling a phone from official support isn't like dropping your kids off at school.
Click to expand...
Click to collapse
Actually, Google didn't drop support for the CMDA variants except in ASOP. So there is no change in the way they rolled out updates. So you are saying they pulled the buggy release because they anticipated dropping CDMA months later? I guess the AT&T version didn't get the release in December because they were dropping CDMA support several months later? I feel like you are drawing conclusions that aren't even there.
Just got the OTA notice today. Keep in mind I'm on the dev channel for OTA updates, but this means its pretty close.
I would post screens but I don't have enough posts yet...
jakesteed said:
Just got the OTA notice today. Keep in mind I'm on the dev channel for OTA updates, but this means its pretty close.
I would post screens but I don't have enough posts yet...
Click to expand...
Click to collapse
By the way, it's still super slow. This Tab is in dire need of some Jelly Bean butter...
please take a nandroid backup (with CWM5), and send me system.ext4.tar and boot.img.
thx!
youre ****ting me right? haha
VZW said they hadnt heard a word about this yet when I talked with them on Tuesday
Wonder when the 7.7 and 8.9 will be graced. I'm tempted to flash to 3.2 and spam system update.
Sent from my SCH-I815 using xda premium
Strange to hear that it is slow as colleagues from 7500 forum are really excited with the speed of ICS update (and I believe that firmwares should be almost the same). Have you done full wipe?
Anyone else get this?
I'm one OTA behind, the incremental one that came in about a month ago never installed on my tab.
Thinking of going back to bone stock in order to OTA up to ICS and get the necessary files over to Pershoot but not going to do that if this OTA isn't really rolling out yet.
freeman_g said:
Strange to hear that it is slow as colleagues from 7500 forum are really excited with the speed of ICS update (and I believe that firmwares should be almost the same). Have you done full wipe?
Click to expand...
Click to collapse
Yeah, about that--first boot left it somewhat sluggish when scrolling through homescreens & widgets, launching TouchWiz apps and responding to touches. But subsequent reboots seemed to fix that. Browsing in Google Chrome is a VAST improvement over the stock browser in 3.2.
pershoot said:
please take a nandroid backup (with CWM5), and send me system.ext4.tar and boot.img.
thx!
Click to expand...
Click to collapse
@Jake: were you able to send this info to pershoot?
Looking forward to pershoot's implementation
eXiled Killah said:
@Jake: were you able to send this info to pershoot?
Looking forward to pershoot's implementation
Click to expand...
Click to collapse
I had checked with Pershoot on saturday and he hadn't heard from jake . . based on jake's past postings I chalk this up to someone being close to Samsung or Verizon development who's unable to share specifics but wanting to leak out a hint of info. Basically confirmation we'll get an update but still no ETA. I for one appreciate the heads up and will continue to wait it out as patiently as I can. Would love to be wrong though, and to find out that he is in fact able to send files off to pershoot. That would be fantastic.
muzzy996 said:
I had checked with Pershoot on saturday and he hadn't heard from jake . . based on jake's past postings I chalk this up to someone being close to Samsung or Verizon development who's unable to share specifics but wanting to leak out a hint of info. Basically confirmation we'll get an update but still no ETA. I for one appreciate the heads up and will continue to wait it out as patiently as I can. Would love to be wrong though, and to find out that he is in fact able to send files off to pershoot. That would be fantastic.
Click to expand...
Click to collapse
Wow. Ok. Was hoping... Heading back to my corner of the room with my LTE while I wait. Thanks for touching base with Pershoot.
I too am just going to sit in the corner...
This corner is starting to get a little crowded.
Very crowded
Now that the ICS for the 7510 has been released, I'm like a crack head constantly clicking "Check Now". Wonder how long before Verizon puts out an update.
eejimen said:
Now that the ICS for the 7510 has been released, I'm like a crack head constantly clicking "Check Now". Wonder how long before Verizon puts out an update.
Click to expand...
Click to collapse
I am still in the corner...
its gettin a bit smelly here...
evilz51 said:
I am still in the corner...
its gettin a bit smelly here...
Click to expand...
Click to collapse
Sorry, I had a burrito for dinner.
eejimen said:
Sorry, I had a burrito for dinner.
Click to expand...
Click to collapse
haha... well light a match at least jeez!
eejimen said:
Now that the ICS for the 7510 has been released, I'm like a crack head constantly clicking "Check Now". Wonder how long before Verizon puts out an update.
Click to expand...
Click to collapse
We're all strung out, waiting on the same dealer:silly:
This thread makes me cry.
Sent from my SCH-I905 using Tapatalk 2