Related
just wondering can t-mobile create a patch to basically make all of our phones that are rooted to not work???? just wondering if anyone knows
<object width="746" height="413"><param name="movie" value="http://www.youtube.com/cp/vjVQa1PpcFPHXdWXcI3UX249crg0AFXgtzoow3h6oaI="></param><embed src="http://www.youtube.com/cp/vjVQa1PpcFPHXdWXcI3UX249crg0AFXgtzoow3h6oaI=" type="application/x-shockwave-flash" width="746" height="413"></embed></object>
You cant put vids on this forum
Ace42 said:
You cant put vids on this forum
Click to expand...
Click to collapse
yeah kinda sucks lol but this forum still rocks you know anything about what i posted????
VoLoDaR1 said:
yeah kinda sucks lol but this forum still rocks you know anything about what i posted????
Click to expand...
Click to collapse
Kind of. The tmo servers have a checkin service that is like win update on windows.Test keys are used for roms so they can receive OTA updates theoretically but they can tell diff from unrooted phone and rooted phone. Tmo apps dont work like myfaves but i doubt tmo cares since only a small fraction of customers are aware of rooting not too many people.
Ace42 said:
Kind of. The tmo servers have a checkin service that is like win update on windows.Test keys are used for roms so they can receive OTA updates theoretically but they can tell diff from unrooted phone and rooted phone. Tmo apps dont work like myfaves but i doubt tmo cares since only a small fraction of customers are aware of rooting not too many people.
Click to expand...
Click to collapse
ok cool thanx for the answer
According to SamsungMobileUK - Froyo is official now (again?). Everyone will have it by End of Month. Is that USA too?
From twitter:
https://twitter.com/#!/samsungukmobile/status/29684769499
Froyo starts rolling out today; everyone will have it by the end of Nov. To prepare, get the latest version of Kies http://bit.ly/cfjJDa
I think we should see it by Christmas. That way when we get it earlier, it will be that much more exciting!
Samsung has been quick to point out that when SamsungUK says 'everyone', they mean 'everyone in Europe'. They have consistently said 'By the end of the year' for us Yank's.
ScottyNuttz said:
Samsung has been quick to point out that when SamsungUK says 'everyone', they mean 'everyone in Europe'. They have consistently said 'By the end of the year' for us Yank's.
Click to expand...
Click to collapse
yes, but they have not really qualified when that really is - it could also be in November. One rumor site claims all of us by the 11th of November.
For a multinational company, they have terrible communication skills. We are left to infer what they mean. But you are correct - previous communication has been region specific.
I have already installed the Froyo version available here: http://forum.xda-developers.com/showthread.php?t=797282
After Froyo is released officially in the US for AT&T, does anyone knows if there would be a way to upgrade to the official version?
* Update: Nevermind my question... there is a thread about this here: http://forum.xda-developers.com/showthread.php?t=821480
According to this:
https://twitter.com/samsungukmobile/status/535769122865153
They say that there have been some fixes to the GPS in Froyo. Let's hope so because I am tired of this unreliable GPS which I can't really use.
PixelPerfect3 said:
According to this:
https://twitter.com/samsungukmobile/status/535769122865153
They say that there have been some fixes to the GPS in Froyo. Let's hope so because I am tired of this unreliable GPS which I can't really use.
Click to expand...
Click to collapse
True
Sent from my SAMSUNG-SGH-I897 using XDA App
has anybody got this and updated that can give some feedback?
http://english.chosun.com/site/data/html_dir/2010/11/15/2010111500961.html
This says Korean Galaxy S users will get official Froyo on Monday night...
Nothing? Nobody had installed the official update and has an opinion...This is disappointing as this thread now only has 9 replies where the thread about a Mysterious update text that 5 people got has 127....
soon to be US hoepfullly!
what i dont get is why is gingerbread coming out like in a week or 2 and we are getting 2.2? shouldnt they have just used this past month or 2 to make gingerbread work instead? Its obviously been available for sometime if its being released.
jc2470 said:
what i dont get is why is gingerbread coming out like in a week or 2 and we are getting 2.2? shouldnt they have just used this past month or 2 to make gingerbread work instead? Its obviously been available for sometime if its being released.
Click to expand...
Click to collapse
Especially when you consider that Samsung had access to the Gingerbread source for the Nexus S (the first Gingerbread phone to come out). At this point I am just hoping we get Froyo soon. If we are lucky, the Nexus S will help make an official update to Gingerbread come sooner; or if not, if the hardware is similar enough we may get unofficial gingerbread updates soon after the Nexus S sources become available.
Thank you for your feedback on the Milestone XT720; due to limited resources, we can confirm that this device will not be receiving software updates.
Mark
Motorola Mobility US Facebook Support
Click to expand...
Click to collapse
http://getsatisfaction.com/motorola/topics/froyo_for_xt720#reply_5739472
Remember, in Motospeak: "updates"==2.1 bugfixes, "upgrades"==2.2 or higher. Motorola already announced we won't get any upgrades.
The final question: what is Cincinnati Bell smoking and can I have some?
Mioze7Ae said:
http://getsatisfaction.com/motorola/topics/froyo_for_xt720#reply_5739472
Remember, in Motospeak: "updates"==2.1 bugfixes, "upgrades"==2.2 or higher. Motorola already announced we won't get any upgrades.
The final question: what is Cincinnati Bell smoking and can I have some?
Click to expand...
Click to collapse
What CB smoking i don't know, maybe they have some voluenteurs(sorry, bad english, huh=)) that works on our phone.
Can someone on FB ask that "limited resourses" guys to open our bootloader or give as non locked bootloader, if they droped our phone like this?
Cause we have resources, and will gladly work on our phone.
P.S. moto, thats why you are in such crysis...
gingerbread for xt720 in korea
According to a site, someone has been testing out the gingerbread on a motoroi xt720 from korea, if its possible, can we port it to our Motorola Milestone XT720?
pavithren said:
According to a site, someone has been testing out the gingerbread on a motoroi xt720 from korea, if its possible, can we port it to our Motorola Milestone XT720?
Click to expand...
Click to collapse
Do you believe this http://www.venusvenera.com/2011/05/upgradeupdate-motorola-milestone-xt720_1978.html ?
khalpowers said:
Do you believe this http://www.venusvenera.com/2011/05/upgradeupdate-motorola-milestone-xt720_1978.html ?
Click to expand...
Click to collapse
I think that site is fake. They have many other articles similar to that in their site. But in my screenshot, you can see that someone has actually used a xt720 with 2.3.2 from korea.
pavithren said:
I think that site is fake. They have many other articles similar to that in their site. But in my screenshot, you can see that someone has actually used a xt720 with 2.3.2 from korea.
Click to expand...
Click to collapse
Exactly. That someone has uses 2.3.2 from Korea and that's totally different from that fake site.
Yea im pretty sure this things never gonna be upgraded, updated, or unlocked. i had to return my phone for repairs yesterday (had about 100 dead pixels out of no where) and when i went in to Cincinnati bell they had no idea what i was talking about when i asked about them about an update, and he said " I think they are just gonna wait and upgrade it to 2.3" but i know thats not happening. and when i called and talk to motorola to get the shipping info the guy said "hey we have the same phone" so i said "are they ever gonna unlock it or upgrade it" and surprise surprise he said "no its gonna stay on 2.1" and some other stuff i couldnt understand. so atleast we have some awesome people here at xda that can get right what motorola cant.
easye420 said:
Yea im pretty sure this things never gonna be upgraded, updated, or unlocked. i had to return my phone for repairs yesterday (had about 100 dead pixels out of no where) and when i went in to Cincinnati bell they had no idea what i was talking about when i asked about them about an update, and he said " I think they are just gonna wait and upgrade it to 2.3" but i know thats not happening. and when i called and talk to motorola to get the shipping info the guy said "hey we have the same phone" so i said "are they ever gonna unlock it or upgrade it" and surprise surprise he said "no its gonna stay on 2.1" and some other stuff i couldnt understand. so atleast we have some awesome people here at xda that can get right what motorola cant.
Click to expand...
Click to collapse
I talked to the CBW guys downtown in Career Tower (sub contracted, not corporate store) about the elusive upgrade they are supposedly working on and you would have thought I was the 2nd coming. He was excited but had no idea what I was talking about. I mentioned the Facebook page thinking b/c he is not corporate that he might know more backroom stuff and he had no idea about it. Thank you for xda, b/c CBW's right hand doesn't talk to its left hand b/c it is dolling out money to Motorola for exclusive contracts to outdated or locked phones.
And always remember, even a broken clock is right twice a day.
Nothing surprising here...
Hopefully we get some success with the CM7 soon... Also hope CB does actually come through with that update -but it has been two months+ and we still haven't seen anything...
I just wish Motorola would unlock the freaking bootloader. That's seriously the least they can do... unfortunately that's probably not going to happen.
This very strange because my bell contract told me that they considering going to 2.2.3 I have seen their 2.2.1 update but not the 2.2.3 I don't trust bell but I also here motor is holding them up.
Sent from my XT720 using XDA Premium App
News from CBs Facebook page...
Cincinnati Bell
UPDATE on Motorola Milestone XT720 2.2 OS upgrade: We have scheduled to release the 2.2 OS upgrade in July pending internal approval. We will post more on this when we have new information to share.
http://www.androidcentral.com/asus-says-bootloader-unlock-tool-coming-gps-hard-yall
so, I know I personally am absolutely 100% enraged to read about this, since we still haven't heard anything about an official ota for NS4G.
Google is ****ing up big time, and they may lose a LARGE chunk of nexus users over this. I may be one of them, too, if they can't fix this problem asap!!
Ya, it is a bit disturbing.
Well, the work week just started back up for them, so maybe we will hear something in the next couple days?
hp420 said:
http://www.androidcentral.com/asus-says-bootloader-unlock-tool-coming-gps-hard-yall
so, I know I personally am absolutely 100% enraged to read about this, since we still haven't heard anything about an official ota for NS4G.
Click to expand...
Click to collapse
Sprint says we'll be "among the first" to updates, not "the first".
hp420 said:
Google is ****ing up big time, and they may lose a LARGE chunk of nexus users over this. I may be one of them, too, if they can't fix this problem asap!!
Click to expand...
Click to collapse
I'd be amazed if this is Google's doing.
Sprint's website says "It runs Android™ 2.3 (Gingerbread) the latest version of Android for smartphones." They're the ones that are clueopenic, not Google.
Don't get me wrong: I'm plenty annoyed at not getting OTA ICS. It's just that I don't actually expect Sprint to live up to their promises, since this is not something they've ever tended to do in the past. Sprint users go through this with every software update for every platform on every phone.
mstevens said:
Sprint says we'll be "among the first" to updates, not "the first".
I'd be amazed if this is Google's doing.
Sprint's website says "It runs Android™ 2.3 (Gingerbread) the latest version of Android for smartphones." They're the ones that are clueopenic, not Google.
Don't get me wrong: I'm plenty annoyed at not getting OTA ICS. It's just that I don't actually expect Sprint to live up to their promises, since this is not something they've ever tended to do in the past. Sprint users go through this with every software update for every platform on every phone.
Click to expand...
Click to collapse
The update does come directly from Google. Sprint works with Samsung to create proprietary hardware drivers that contain everything you need to access Sprint's cell phone network. These drivers are then made available in binary only form to Google. Google then adds these drivers to their official build. The final product is then delivered directly from Google to your Nexus S 4G phone.
Click to expand...
Click to collapse
this quote came from sprint community forums. http://community.sprint.com/baw/message/380145#380145
Sprint does NOT provide our update...google does. Google is falling behind, and they need to be held accountable for their screw-ups. Just because they didn't say "NS4G will be the first" does not make it acceptable for 3rd parties to get an update before they can even get off their lazy asses just to push a button for their OFFICIAL FIRST-PARTY USERS. Everything we need is on their server for download, and if devs here can get off their asses top compile this rom, google sure as hell can do the same!!!
No. Google is waiting on Sprint, not the other way around.
In addition to providing CDMA drivers, Sprint has to approve the final package that is pushed, and they haven't yet done that.
mstevens said:
No. Google is waiting on Sprint, not the other way around.
In addition to providing CDMA drivers, Sprint has to approve the final package that is pushed, and they haven't yet done that.
Click to expand...
Click to collapse
Source or GTFO. And we've already got the drivers, I'm using ICS on my NS4G right now. 4g and everything.
mstevens said:
No. Google is waiting on Sprint, not the other way around.
In addition to providing CDMA drivers, Sprint has to approve the final package that is pushed, and they haven't yet done that.
Click to expand...
Click to collapse
lol...is that why every single file needed to build a FULL ics rom is already on the server??
I'm not saying you're wrong, but in my opinion, it does not look like it's sprint's fault. It looks like Google is either lazy about releasing it, or they are too dumb to build a rom that's working properly so it's stuck in pre-release testing. However, this is just my opinion....but as far as actually building/releasing the OTA, that is 100% on google's end. whether or not the authorization is coming/has to come from sprint is another story entirely....the point is, if that is the case, google isn't doing their jobs and telling them to screw themselves so they don't look like the bad guy in this!! It's not sprint who will have the damaged reputation after this is all said & done.
jesusice said:
Source or GTFO. And we've already got the drivers, I'm using ICS on my NS4G right now. 4g and everything.
Click to expand...
Click to collapse
<shrug> it's the way it's always worked.
This worked in our favor earlier when Sprint okayed deployment of Google Wallet on our devices and GSM users were foaming at the mouth to get it. In those cases, too, it wasn't Google (which has excellent reasons for getting Wallet into as many hands as possible) but the carriers which held up release.
---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------
hp420 said:
lol...is that why every single file needed to build a FULL ics rom is already on the server??
Click to expand...
Click to collapse
No.
What is the connection between having all the files on the server and Sprint's approval of a final release version?
In your earlier quote lifted from another site, the poster was saying the updates are pushed from Google's servers, not Sprints. That's correct. However, they can't just start pushing updates without carrier approval. This is why, for example, T-Mobile got ICS before ATT.
mstevens said:
<shrug> it's the way it's always worked.
This worked in our favor earlier when Sprint okayed deployment of Google Wallet on our devices and GSM users were foaming at the mouth to get it. In those cases, too, it wasn't Google (which has excellent reasons for getting Wallet into as many hands as possible) but the carriers which held up release.
---------- Post added at 02:02 PM ---------- Previous post was at 01:59 PM ----------
No.
What is the connection between having all the files on the server and Sprint's approval of a final release version?
In your earlier quote lifted from another site, the poster was saying the updates are pushed from Google's servers, not Sprints. That's correct. However, they can't just start pushing updates without carrier approval. This is why, for example, T-Mobile got ICS before ATT.
Click to expand...
Click to collapse
that was a result of carriers' investment in other companies that developed very similar software to google wallet....exactly the same as when the GN was delayed for verizon because google wanted wallet on their official device and verizon had a coronary about it because they had already backed another company's software that does exactly the same thing.
as for carrier approval, google can only wait so long before they just snap and push the update anyway. carriers can not make the rest of the world wait for an update just because they don't want it released to their devices yet. Google needs to just ***** slap sprint, tell them to shut the hell up, and push the update before this damages their reputation any more than it already has. Like I said, it won't be sprint whose rep is damaged from all of this, just like no one looks towards verizon for the GN delay...the world will blame google, and they aren't even standing up for themselves.
hp420 said:
lol...is that why every single file needed to build a FULL ics rom is already on the server??
Click to expand...
Click to collapse
Sure, they could build ICS for the NS4G but the 4G radio wouldn't work. Drivers aren't part of AOSP.
Also, didn't Google pulled the ICS update for the (tmobile) Nexus S? If that's still true, they're clearly working out the issues with ICS before releasing it to the NS4G, etc.
It is most likely *not* Googles doing. I don't know where half of you get these crack pot ideas from that Google or any other OEM is in control over how and when they push an update.
- OEM builds ROM
- OEM submits ROM to carriers (i.e. Sprint branded phone would require Sprint to approve the update).
Carriers can be total dicks about updates and providing OTA. I've seen it all first hand from when I had a Motorola Milestone (Motorola telling us the 2.1 has been built and has gone through testing but they are waiting for carriers to approve them on their networks) we had to waiting months for the updates due to some carriers.
nside said:
Sure, they could build ICS for the NS4G but the 4G radio wouldn't work. Drivers aren't part of AOSP.
Also, didn't Google pulled the ICS update for the (tmobile) Nexus S? If that's still true, they're clearly working out the issues with ICS before releasing it to the NS4G, etc.
Click to expand...
Click to collapse
Driver binaries are on Google's servers for nexus devices. 100% built from source and 4g works just fine.....
Sent from my Nexus S 4G using xda premium
we are waiting for sprint to approve the new radio that will come with the ota. That is what causes the holdup.
Sent from my Nexus S 4G using xda premium
maybe Google is still fixing what does not go to ics now and then....maybe xD we can see ics on all nexus ^^
hp420 said:
that was a result of carriers' investment in other companies that developed very similar software to google wallet...
Click to expand...
Click to collapse
Precisely. I'm glad you finally see my point that Google can't just push out an update because they want to, but are hampered by needing carrier approval.
---------- Post added at 02:33 PM ---------- Previous post was at 02:28 PM ----------
hp420 said:
carriers can not make the rest of the world wait for an update just because they don't want it released to their devices yet.
Click to expand...
Click to collapse
When did this start being true?
It's absolutely true that carriers CAN prevent official release of an update for any reason, or for no reason. They've done it many times before and they'll do it again. Sprint has a long track record of doing exactly this.
hp420 said:
Google needs to just ***** slap sprint, tell them to shut the hell up, and push the update
Click to expand...
Click to collapse
You have an awfully lot to learn about how contracts work.
If I run a massive business and another massive business violates my contract with them (for example, pushes an unapproved update to what I think of as "my" devices irrespective of the beliefs or desires of my subscribers), many lawyers are going to be fed and I will expect a massive transfer of assets from that other company to mine.
mstevens is dead on. Sprint will not allow the push of an ota until they can be sure this update won't toast peoples phones, and for the people in the world that have a nxs4g and don't do modding, if the update is broken, they can't just fix what Google's update did. My brother has the GSM version, and received the update, and honestly were not missing anything. The user made roms are already becoming superior builds anyway. We will eventually get the update, I for one am glad sprint said no at the moment though, I would hate to waste my time on a broken ota lol
Sent from my Nexus IcS 4G using xda premium
lol...too many people to quote you all, so I'm gonna do my best to answer everyone
Ok, I understand how contracts work. My point is this: yes, google has a contract with sprint (or any other carrier, for that matter) to provide radios, wimax drivers, what-have-you, and I understand that if sprint won't sign, there's not much the manufacturer can do...I get that. But my biggest concern with all of this is that google is not flexing their muscles. They have made a guarantee to their customers (not explicit, but still implied) that they would provide ALL NEXUS UPDATES in a timely manner. Sprint is now holding google back from seeing this implied promise carried through, and the fact that other manufacturers are already pushing full ota updates now makes google look bad (grounds for a lawsuit).
I understand that if google were to break that contract by circumventing sprint by releasing the update anyway, they could be sued...I get that. However, google could also counter-sue for making customers wait an unreasonable amount of time for an update that is, by all rights, a "god-given right" to all nexus users prior to anyone else getting it.
Now let's talk about how many people use an NS4G to develop software that they get paid top develop. By sprint not releasing an official update, they are now inhibiting developers from doing business, and therefore they are taking money out of people's pockets. Yes, I know this last example is far-fetched a little bit, but honestly, it's really not all that far off. Yeah, people can just compile aosp themselves, and if they are truly developers, they should know how to do that....but let's say they are working on one particular app that is exclusive for sprint users, and they want to make sure it will run properly on sprint's network via an ICS handset....oh, wait...they can't because sprint are a bunch of lazy pieces of **** who won't sign. This is grounds for class-action, IMHO.
I may not be a lawyer, but it's blatantly obvious to me that if sprint holds out long enough, they are absolutely 100% vulnerable to class-action suits...and maybe even a suit from google, as well. Let's face it, no one but sprint & google execs really know the terms of the contract, but for all we know, it IS in the contract to provide timely updates. If this is the case, I hope someone gets sued like a SOB for this delay, because it's unacceptable!!!!!
hp420 said:
Google is ****ing up big time, and they may lose a LARGE chunk of nexus users over this. I may be one of them, too, if they can't fix this problem asap!!
Click to expand...
Click to collapse
I suggest that this LARGE chunk of nexus users may be better served by one of the many other smartphone mfrs who provided a pure ICS update (i.e. no BS extra UI layer and no bloat) over the holiday. Which one will you choose? Oh, wait.
hp420 said:
I hope someone gets sued like a SOB for this delay, because it's unacceptable!!!!!
Click to expand...
Click to collapse
Really. You want a lawsuit, because a bunch of software developers wouldn't work at your whim over the nation's biggest holiday?
The111 said:
I suggest that this LARGE chunk of nexus users may be better served by one of the many other smartphone mfrs who provided a pure ICS update (i.e. no BS extra UI layer and no bloat) over the holiday. Which one will you choose? Oh, wait.
Really. You want a lawsuit, because a bunch of software developers wouldn't work at your whim over the nation's biggest holiday?
Click to expand...
Click to collapse
actually, since the drivers, kernel, etc. was all pushed to google's update servers WELL over a week before christmas, they wouldn't have been working during the holiday at all to get it pushed to NS4g...they just had to click a few buttons....something I've done a few hundred thousand times in the last 5 minutes.
BTW, no need to be a smartass about it. if I want to switch from nexus to get a pure android ui, I can always just root and modify the ota to have a stock theme. So now what do you have to say about that, smartass??? Oh wait...
tool.
hp420 said:
actually, since the drivers, kernel, etc. was all pushed to google's update servers WELL over a week before christmas, they wouldn't have been working during the holiday at all to get it pushed to NS4g...they just had to click a few buttons....something I've done a few hundred thousand times in the last 5 minutes.
Click to expand...
Click to collapse
You're making multiple assumptions. You assume that by the existence of particular source files on a particular server, you know what Google's stance as to the public release candidacy of a compiled package is. Please explain why you believe this. There are only two ways we could know such a thing:
1) Google publicly declares it (i.e. this compiled package IS ready for public use... or vice versa)
2) Google actually pushes the compiled package (in the absence of such an action, the logical assumption to make is that they are not ready to do such a thing yet, for their own reasons... i.e. there is still something else they need to do. NOT that they are "too lazy/stupid to push a few buttons")
hp420 said:
BTW, no need to be a smartass about it. if I want to switch from nexus to get a pure android ui, I can always just root and modify the ota to have a stock theme. So now what do you have to say about that, smartass??? Oh wait...
Click to expand...
Click to collapse
You're right, the sarcasm is 100% optional. It's an option that I quite enjoy though. I won't, however, stoop to personal attacks.
How about this. Sarcasm removed for you, I will ask the question that was clearly evident in my last post. If you decide to "leave Google" because of your discontent, which handset vendor will you turn to? Who do you believe is a better option? Who will give you a pure Android update in a shorter timespan? I am genuinely (no sarcasm) interested!
As Galaxy S owners, we are all united. As Android users we are all united. As far as Samsung is concerned we are all NOT created equal. Our device, the Vibrant (SGH-T959), is now being left to the wayside for any future updates from Samsung even though our core specs are extremely similar to the Google Nexus S, which has already received the ICS update. The CyanogenMod team has left us due to the on-going issue of 911/e911 and the lack of the proper code from Samsung to alleviate a potentially fatal result of a custom ROM. It is our intentions to serve Samsung with a petition asking for the update to ICS, which will in-turn, alleviate the 911/e911 issue as well.
We are asking all Galaxy S users to sign this petition to get Samsung to reconsider giving all top end Galaxy S devices the ICS update. Please help us with our goal and sign the petition. If you are on a Galaxy S phone, this affects you too.
Thank you for reading this and please see this link for more details and this link to sign the petition.
Ok, since it was explained a bit better to me, I'm allowing this to be reopened, however, I'll be keeping an eye on it. Keep it civil.
Thank you, Ann.
thanks for the update..hope things look up !!
I plan to sign this petition, but I'm a bit confused about how it includes all SGS devices. The entire letter speaks specifically to the Vibrant. Is a new letter still being written? Or how is it being conveyed that all SGS owners are signing this?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
The issue with the 3rd paragraph about how the Vibrant was released with 2.1 and then we fought for 2.2 only to be denied GB/ICS is in there to paint the picture of how consumer support has failed. It is specific to the Vibrant but the picture is for all Galaxy S users.
The CM team portion leaving the Vibrant is a problem (911/e911) that effects us all. For some reason they just dropped ONLY the Vibrant from their supported devices list b/c of this issue.
Still, we want to thank you for your support and help with this and hopefully they will at least listen to us.
Links to Samsung Twitter/Facebook/Google+:
Twitter:
- twitter.com/samsungtweets
- twitter.com/samsungmobileus
- https://twitter.com/SamsungJohn
- https://twitter.com/DigitalTrends
Facebook:
- www.facebook.com/SamsungUSA
- www.facebook.com/SamsungMobileUSA
Google+:
- https://plus.google.com/114303379611712597260/posts
let's be honest guys. Samsung did a logical thing by NOT giving us ICS update. I mean come on now.. even if they do decide to give us ICS, chances are it will be buggy as gs1 doesn't have enough memory to have ICS and TW... so really there is no point in giving us ICS, not only Samsung won't make any profit from doing this they might get flamed even more for making the phone slower buggier .. etc and
some people are saying they want stripped version of ICS on gs1 then why don't you just go buy yourself a nexus phone? Why would people buy nexus over galaxy when they're the same thing ? I could go on and rant about how samsung would have to meet terms with google, service providers and etc but ill stop here
Gingerbread from Samsung has been released. Rogers released it AGES ago.Gingerbread from AT&T has NOT been released.
your problem for Gingerbread is with AT&T. NOT SAMSUNG. Samsung released gingerbread to the carriers.
and to the post above, its not about buying an SG1 over a nexus, its about ALREADY OWNING SG1... and not enough memory for ics and touchwiz?? thats a propaganda lie. it would run fine. touchwiz consists of a launcher and a second (TW)framwork-res.apk and a few code changes to other system files. every rom has a laucher, so no loss there, wow extra 7mb framework... ohhh.. noo!
POST 3000!!!!!!
xriderx66 said:
Thank you.
Click to expand...
Click to collapse
Signed even though I don't own one. you guys should get updates too!!
Sent from my Nexus S using xda premium
TRusselo said:
Gingerbread from Samsung has been released. Rogers released it AGES ago.Gingerbread from AT&T has NOT been released.
your problem for Gingerbread is with AT&T. NOT SAMSUNG. Samsung released gingerbread to the carriers.
and to the post above, its not about buying an SG1 over a nexus, its about ALREADY OWNING SG1... and not enough memory for ics and touchwiz?? thats a propaganda lie. it would run fine. touchwiz consists of a launcher and a second (TW)framwork-res.apk and a few code changes to other system files. every rom has a laucher, so no loss there, wow extra 7mb framework... ohhh.. noo!
POST 3000!!!!!!
Click to expand...
Click to collapse
Just curious how do you know Samsung released GB to the carriers? Any sources?
EDIT: it is just me who finds big size fonts very irritating and irrelevant?
viny2cool said:
Just curious how do you know Samsung released GB to the carriers? Any sources?
EDIT: it is just me who finds big size fonts very irritating and irrelevant?
Click to expand...
Click to collapse
All carrier control the release of the updates, manufacturers create the updates for the phone, except for the Nexus line which is controlled by Google. The new exception to that might be the Verizon Nexus. The evidence is that the I-896 and I897 are the exact same phone, except one says ATT on the front.
Can someone explain this 911 issue? I mean how can you dial 911 and it won't work? IT seems like any number would work! I'm a bit confused by it, am I missing something? Thats seems like a phone being unable to dial, well Pizza hut, I dunno. It doesn't make sense.
Oh and I signed the petition.
Cor-master said:
Can someone explain this 911 issue? I mean how can you dial 911 and it won't work? IT seems like any number would work! I'm a bit confused by it, am I missing something? Thats seems like a phone being unable to dial, well Pizza hut, I dunno. It doesn't make sense.
Oh and I signed the petition.
Click to expand...
Click to collapse
I think its related to dialing 911 when u don't have any network. I mean when u don't have sim card you can still make emergency calls.
sent from my cappy rocking ICS
popfan said:
All carrier control the release of the updates, manufacturers create the updates for the phone, except for the Nexus line which is controlled by Google. The new exception to that might be the Verizon Nexus. The evidence is that the I-896 and I897 are the exact same phone, except one says ATT on the front.
Click to expand...
Click to collapse
I agree that they control it. But we don't know if Samsung actually gave it to ATT yet. Also there is no need of those kind of statements like in the post above my first post. No one is forcing him to sign the petition.
sent from my cappy rocking ICS
GB update (using KIES) for captivate:
http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00024051&fm_seq=24219
viny2cool said:
I agree that they control it. But we don't know if Samsung actually gave it to ATT yet. Also there is no need of those kind of statements like in the post above my first post. No one is forcing him to sign the petition.
sent from my cappy rocking ICS
Click to expand...
Click to collapse
I support this, samsung should definitely take some initiative in regards to their previous devices.
Signed!
Sent from my SGH-I897 using xda premium
I will always be your side.But is it useful?