Related
we all know its going to happen but how soon till we see the leaks
Leaks? It's already officially out. Nexus One's are receiving the update as we speak. As for an EVO specific leak from HTC/Sprint, who knows..I'm sure the devs will have something out soon if there aren't any major hardware changes / requirements.
SDK is out NOT a working rom its no "leaked" pushed yet to the nexus 1
This update sucks for me if it doesn't fix the CPU problem of almost maxing out when scrolling which causes scrolling to be laggy. If they don't fix this by the time my next upgrade comes up I'm switching to a Windows phone. I want a smooth interface.
CheesyNutz said:
SDK is out NOT a working rom its no "leaked" pushed yet to the nexus 1
Click to expand...
Click to collapse
I guess I'm not following.
According to Engadget, Gingerbread, 2.3, is running on Nexus One's. They've received the OTA update.
Although, they may have been wrong and pulled the article and didn't say anything, since
http://www.engadget.com/2010/12/06/android-2-3-update-now-rolling-out-to-nexus-one-owners/
no longer appears to be a valid link, but it was just a half hour ago.
I think this is what it said:
Nexus One owners feeling a little Nexus S envy can breathe a little easier -- we're hearing that Android 2,3 Gingerbread is being pushed out to the N1 as we speak. We'd imagine that all the slick new features that don't require new hardware (like NFC support) will be there, and we're definitely interested in playing with this built-in WiFi calling stack.
Click to expand...
Click to collapse
the latest ota pushed to the nexus was just a minor update i don't think it was 2.3
Sirchuk said:
I guess I'm not following.
According to Engadget, Gingerbread, 2.3, is running on Nexus One's. They've received the OTA update.
Although, they may have been wrong and pulled the article and didn't say anything, since
http://www.engadget.com/2010/12/06/android-2-3-update-now-rolling-out-to-nexus-one-owners/
no longer appears to be a valid link, but it was just a half hour ago.
I think this is what it said:
Click to expand...
Click to collapse
That might have been an old link where the nexus one got a security update and people jumped the gun on calling gingerbread
Looks like Engadget was wrong and pulled the story. Nobody can confirm that 2.3 is out it seems, though some have tried to get their N1's to update.
Way to go Engadget, wrong information with no clarification. At least post a "Oops, we were wrong" update or something.
The N1 forums are saying it will be out on/around the 16th.
Edit:
Think they heard me:
Update: Looks like our flood of tips came from people who were seeing their N1s get a different, less-interesting update -- we'll let you know when the actual 2.3 update roll out. Ah, the heady optimism of hope.
Click to expand...
Click to collapse
One of the main guys on the Android team tweeted that no ota was released for the nexus one and that the source would be released in the "coming weeks". My bet is that the first rom with working Gingerbread on it will be Cyanogen and within a few weeks of the source being released.
donatom3 said:
One of the main guys on the Android team tweeted that no ota was released for the nexus one and that the source would be released in the "coming weeks". My bet is that the first rom with working Gingerbread on it will be Cyanogen and within a few weeks of the source being released.
Click to expand...
Click to collapse
Yup, for our EVOs CM is the best bet and that will be AFTER the source (not to be confused with the Nexus One OTA) is released.
Award Tour said:
Yup, for our EVOs CM is the best bet and that will be AFTER the source (not to be confused with the Nexus One OTA) is released.
Click to expand...
Click to collapse
Any sense rom will have to wait till a 2.3 gingerbread source is released by HTC which could be a while, if ever. Cyanogen is already on 2.35.9 kernel which hopefully means that porting their work to 2.3 shouldn't be that hard to do.
drmacinyasha said:
I'm going to say this once to head off the countless sheep who will ask...
Do not ask when Gingerbread will make it to the EVO.
Seriously, how the hell would any of us know? We're not psychics, we're not secret HTC/Sprint/Google/CIA/Mafia/Former KGB/NSA employees, we can't predict the future, so why on God's green Earth would you ask us?
Shut up, sit down, twiddle your thumbs, and wait for a press release from Sprint, HTC, Google, etc. announcing that Gingerbread will or will not be ported to the EVO. If you really want Gingerbread, go help Team Douche port it to be CyanogenMod 7. That's the most guaranteed way to get it to our phones.
Click to expand...
Click to collapse
10 characters.
donatom3 said:
Any sense rom will have to wait till a 2.3 gingerbread source is released by HTC which could be a while, if ever. Cyanogen is already on 2.35.9 kernel which hopefully means that porting their work to 2.3 shouldn't be that hard to do.
Click to expand...
Click to collapse
Not sure if there's any confusion with what I think I read from your post but.. I'm talking about the AOSP source not the HTC source. That'll probably take a month or so after the Nexus One OTA to be released and then another month or so before CM releases a RC of CM7/2.3.
apollooff320 said:
This update sucks for me if it doesn't fix the CPU problem of almost maxing out when scrolling which causes scrolling to be laggy. If they don't fix this by the time my next upgrade comes up I'm switching to a Windows phone. I want a smooth interface.
Click to expand...
Click to collapse
windows phone? are you on crack?
I'm guessing you won't see a Sprint/HTC Gingerbread ROM until sometime next year. Rumor has the source code being released when the Nexus S ships which is allegedly on Dec 16. Expect AOSP based Gingerbread ROMs to start rolling out around then and an Official Sprint ROM after sometime well after that, after its been thoroughly QA'd.
For those of you wondering what phones will and will not get Gingerbread, or the tards (or just diehard wishful thinkers) that think Verizon will just skip right over FroYo and go to Gingerbread, this is an official quote from Verizon:
"Google's just-announced Gingerbread software is generating buzz in the media.
Initially, it is not available on the Verizon Wireless lineup of Android phones.
BUT ... we're working with Google as they release source code for device manufacturers to begin integration. We are also assessing which devices will get Gingerbread within the coming months.
Stay tuned - more information will be available soon."
So that means, they won't even begin ASSESSING what phones receive the updates for MONTHS. Not days, not weeks, MONTHS. So those hoping to see Gingerbread anytime soon, well, sorry to burst your bubble, but its not happening. Those thinking FroYo was delayed to bake its bug fixes into Ginger, well, they'd have to delay it for months. Lets hope this is not the case....
Don't ask where I got the quote from....'tis not your concern
No
Sent from my SCH-I500 using XDA App
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months. Either way, I say end of March would be the soonest any device would see an official update, likely going to be over half-way through the year with LTE devices being released before most have Gingerbread though.
imnuts said:
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months. Either way, I say end of March would be the soonest any device would see an official update, likely going to be over half-way through the year with LTE devices being released before most have Gingerbread though.
Click to expand...
Click to collapse
Assess how ???? There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ???? And even if they did, they won't bother working on the next build UNTIL a carrier requests for them to. They don't just start devoting resources to developing a build that may never be released....
This is unfortunately just again, hopeful wishing and you trying to justify accordingly. I don't know why I bother
I promise you, you won't see any Verizon devices with official Gingerbread builds until April/May at the earliest. They decide what phones are going to have it, then they turn it and a bug fix list over to the OEM, and they will wait for builds. Then, they get builds and start testing, which can take another few months.
At least you're not still hoping they'll skip over FroYo and straight to this....
Who really cares about gingerbread anyway. I'm very satisfied with DJ05 update, roms/kernals/themes. I can now wait patiently for froyo and... not even concern myself with when/where gingerbread will be released.
I never said they were skipping Froyo
I'm just saying there are two ways you could read their statement. A better way to word it in the manner that you are stating it would be something like "In the coming months, we will be assessing which devices will get Gingerbread".
To me, the way it is worded means more that they put their devices that are out in a line and pick which they will update and which they won't, then put a timeline on when they'd like to see the updates start coming.
To say that OEMs don't have code for Gingerbread right now, especially Samsung, seems a little naive really. We may not have source code, but I can't imagine Google not sharing it with OEM partners so that they can start working with it.
Truthfully, I couldn't care less when the update arrives as I'll probably wait to see what the developers can do with it before updating. But this doesn't say anything about when any device will receive the update and what devices won't get it. It just says that we have a few months before we are likely to see it in any official form, and I don't think anyone was expecting it any sooner, especially from Big Red.
imnuts said:
I never said they were skipping Froyo
I'm just saying there are two ways you could read their statement. A better way to word it in the manner that you are stating it would be something like "In the coming months, we will be assessing which devices will get Gingerbread".
To me, the way it is worded means more that they put their devices that are out in a line and pick which they will update and which they won't, then put a timeline on when they'd like to see the updates start coming.
To say that OEMs don't have code for Gingerbread right now, especially Samsung, seems a little naive really. We may not have source code, but I can't imagine Google not sharing it with OEM partners so that they can start working with it.
Truthfully, I couldn't care less when the update arrives as I'll probably wait to see what the developers can do with it before updating. But this doesn't say anything about when any device will receive the update and what devices won't get it. It just says that we have a few months before we are likely to see it in any official form, and I don't think anyone was expecting it any sooner, especially from Big Red.
Click to expand...
Click to collapse
Samsung has code obviously, without it, they couldn't have built the Nexus S. And I doubt Google builds the "Nexus" software because of all the little nuances of the code interacting with drivers and so forth (RIL ring a bell????), but I could be wrong, I don't work for either Google or Samsung.
I doubt the other OEM's have any builds running yet, as evidenced by the very first reference to builds, where they say that they are working with OEM's AS GOOGLE releases source code for them to integrate into their phones, but people can take it for what they wish.
I just put the quote out there verbatim. Do with it what you will.
mexiken said:
Assess how ???? There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ???? And even if they did, they won't bother working on the next build UNTIL a carrier requests for them to. They don't just start devoting resources to developing a build that may never be released....
This is unfortunately just again, hopeful wishing and you trying to justify accordingly. I don't know why I bother
I promise you, you won't see any Verizon devices with official Gingerbread builds until April/May at the earliest. They decide what phones are going to have it, then they turn it and a bug fix list over to the OEM, and they will wait for builds. Then, they get builds and start testing, which can take another few months.
At least you're not still hoping they'll skip over FroYo and straight to this....
Click to expand...
Click to collapse
Actually I don't know how many times this has been said. Google releases their OS source not so long after their press release. It is the OEMs who have to release their kernel for us to develop anything. We've had 2.3 code for awhile now but we don't have kernel. They just released Nexus One kernel like yesterday so they'll get it pretty soon. People, Google's OS code and OEM kernel are two different things. We always had code source pretty fast at hand.
The fact that I'm super-skeptical of these unsourced-but-supposedly-from-Verizon quotes aside, I think imnuts has a point here.
imnuts said:
It could also mean be interpreted as they are assessing the devices now to have the update(s) rolled out in the coming months.
Click to expand...
Click to collapse
According to the rules of grammar, he's right. The order matters: since the clause "will get gingerbread within the coming months" comes after "which devices," not "we are assessing," it refers to the former. Had the quote been "We are also assessing within the coming months which devices will get Gingerbread," then it would be the other way around.
But that aside, even more importantly, saying a process will happen "within the coming months" doesn't mean that the process won't start for months. It means something is likely to be ongoing and could be done within one month, six months, or anything in between (or longer). Ultimately, that's the kind of wording people use when they want to remain intentionally vague, and we really can't read a timeline one way or the other from it. Especially when it comes to mobile carriers and software updates.
mexiken said:
There is no source code to work with, the OEM's have not released Gingerbread builds as Googlele hasn't dropped any into AOSP yet (correct me if I'm wrong), so how would you like Samsung or Motorola to like working on builds when they don't have the source code ????
Click to expand...
Click to collapse
Well, for starters, Samsung obviously has had the 2.3 source code for quite some time considering they have a Gingerbread phone coming out tomorrow. We also know Motorola has the 3.0 code seeing as how they're working on at least one already-functional Honeycomb device. The only one we can say definitely doesn't have 2.3 is LG, because they said so (though they also said 2.3 required a 1ghz processor in the same breath, which turned out to be a complete lie, so it's hard to trust them). But clearly, AOSP gets the code just a tad later than at least some OEMs do.
(1)
I think it is insulting how Samsung released the Froyo update. This was not a mass update... this was a "lets shut the people complaining up update!"
Updating through Kies ALWAYS = people posting about problems/issues.
Why is it they could not do an OTA? I personally assume it's because it was not ready (hence the KA7 leak) and THAT will be an OTA for the masses to froyo (or an update to those who used Kies). This is my assumption.
But shame on Samsung/T-Mobile for this...
I would STRONGLY urge new people to NOT update to froyo via kies. I WOULD encourage rooting your phone and flashing the new custom roms that are based off the newest builds (even newer than KA6 which was the "official update").
(2)
I think a thread dedicated for the new ROMs in the Q&A section would be awesome. Consider it an "ask a dumb question and expect a quick answer" thread. The less crap/clutter from the development section the better.
I imagine hardly any posts in the development section are of benefit to the developer.
I feel the Nero V4 sticky is a good example. Though I feel a sticky is a bit much.
(3)
Anyone want to create a thread (or show me one) with all of the stock system apps attached? It would ne nice for those times when someone is asking for them....
(4)
Does anyone have the skills to make the dropdown "mute" button also mute Media. I hate that currently it will mute everything but media... as it inevitably always leads to me making noise when I think I am muted.
I now use Widgetsoid to mute my phone completely.
Thanks!
I don't care how they released froyo, as long as they also release source code soon since it was an "official" release.
Sent from my SGH-T959 using XDA App
dcpetterson said:
I don't care how they released froyo, as long as they also release source code soon since it was an "official" release.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
They have 60 days. Should not take that long. I just question why it was not an ota. Consider me skeptical of Samsung.
Want source? Request it: @SamsungMobileUS should work.
I agree that this was to shut people up, however, as a person who hasn't flashed a rom yet, I commend them for it. I really didn't know what I was missing, and if KA6 is laggy, I can't wait to see what isn't laggy. I'd like to root my phone next, but I have no idea if I'm hardware locked, so I'm inspired to do more reading.
Mini Kies is not difficult to use. People just don't read.
ETA: I agree that there will eventually be an OTA for fixes to KA6 and for people who did not even know about this.
mrsbelpit said:
I agree that this was to shut people up, however, as a person who hasn't flashed a rom yet, I commend them for it. I really didn't know what I was missing, and if KA6 is laggy, I can't wait to see what isn't laggy. I'd like to root my phone next, but I have no idea if I'm hardware locked, so I'm inspired to do more reading.
Mini Kies is not difficult to use. People just don't read.
ETA: I agree that there will eventually be an OTA for fixes to KA6 and for people who did not even know about this.
Click to expand...
Click to collapse
Check and make sure that your phone is hardware locked now as I know that one of the ROMs took care of this issue.
Sent from my SGH-T959 using XDA App
Isn't it that updating through kies is faster than ota? People wouldn't have to wait, unless you're a mac user. The JI6 took forever for them to send it. I waited like 2 weeks then i just flashed it through odin because i was really tired of waiting.
Sent from my SGH-T959 using XDA App
Personally, I do believe that KA6 was suddenly delivered via Kies to shut us all up.
However, I don't really mind how updates are released. They don't have to be OTA. As long as Samsung releases timely updates, even if it is via Kies, then I will be a happy customer. (Oh and they still need to fix the hardware gps flaw)
If they release Gingerbread via kies in a timely manner, I will even somewhat forgive them, but I still will not buy another Samsung made product again for a very long time if ever.
im glad atleast samsung decided to give us froyo... i mean now we can get a little bit of work on our roms since we have a official now.
but i think that "official" rom was made in 2 days, because if you notice, its laggy as hell, and the only difference is theres wifi calling and a few other apps, thats IT.
s15274n said:
They have 60 days. Should not take that long. I just question why it was not an ota. Consider me skeptical of Samsung.
Want source? Request it: @SamsungMobileUS should work.
Click to expand...
Click to collapse
I have the same opinion. I believe this was just a "shut them up" maneuver and the easier softer way for them to do it. Also from what I have read in the threads there seems to be a number of people with problems from the Keis fiasco.
xriderx66 said:
im glad atleast samsung decided to give us froyo... i mean now we can get a little bit of work on our roms since we have a official now.
but i think that "official" rom was made in 2 days, because if you notice, its laggy as hell, and the only difference is theres wifi calling and a few other apps, thats IT.
Click to expand...
Click to collapse
Well, it actually has the Dalvik Jit Compiler which somewhat improves the Hummingbird cpu performance, there is also Flash player.
SamsungVibrant said:
Well, it actually has the Dalvik Jit Compiler which somewhat improves the Hummingbird cpu performance, there is also Flash player.
Click to expand...
Click to collapse
well i guess all that lag takes away from the dalvik jit
also the flash, we've had for like months so you know,
S15274N Great Posting
I agree on your general Ideas. I really like the Idea of posting a fast Q & A
I like the Idea of Making a thread that lists all the stock apps (with apk attached etc.) for those who want that sort of thing.
And, I agree Samsung is just trying to avoid a Gun Fight with the customers. We customers Really are making it hard for Tmo and Samsung to continue their personal "*****-match"
We need to continue to Keep the Pressure on Samsung to keep them adhering to the open source licensing agreement thet agree to when installing Android.
Yeah, I was not trying to say I am upset they released froyo... but more picking on them for HOW they released it. They know 99% of Vibrant users are not even going to know it was released, and if they did, they wont bother with Kies.
Them releasing source will be huge. I hope they release it as fast as they did for the canadian fascinate once froyo was released for it. I'm still a skeptic of Samsung and expect a future release to be the next "official froyo"
s15274n said:
Yeah, I was not trying to say I am upset they released froyo... but more picking on them for HOW they released it. They know 99% of Vibrant users are not even going to know it was released, and if they did, they wont bother with Kies.
Them releasing source will be huge. I hope they release it as fast as they did for the canadian fascinate once froyo was released for it. I'm still a skeptic of Samsung and expect a future release to be the next "official froyo"
Click to expand...
Click to collapse
they'll probably release it on like the 60th day waiting till its like 11:59PM then they upload. lol.
Based off your #1 statment I can only say that this is exactly why they released the "official update". The thing is after the first rumor was released and the **** hit the fan causing multiple threads and 1,000's of post, among other things, there was a small thread and article that was covered and only happen to receive less then 50 post that stated:
The same credible source that gave the first rumor added the reason why samsung and/or tmobile haven't given the update Is because samsung is charging the carriers for OS updates. This means samsung was expecting each carrier to pay per handset sold(later to be denied by samsung).
You can have your own take on samsung or tmo, but the remainder stays the same. That is if the sites which released the rumors spoke to the same source and one rumor is true, then possibly the second Could be also. This also shows 2 other things that will forever fault the android community and the Internet alike. The mob mentality and the feeling of some type of entitlement will cloud the truth or fuel rumors and/or other things that none of use are entitled to know or understand.
One good thing that has come out of this is the fact that now samsung is responsible to release the 2.2 source.via the GPL. Going forward id say Let's try and not let this happen with the real ota, if that ever really happens... lol.
Moral of the story:
Becareful what you wish for. You might just get it... kinda.
the samsung galaxy s our phones will not get updated till mid-April claims.
@samsungsuomi :Galaxy S:n Android 2.3 -päivityksen testausvaihe on loppumetreillään. Uusi ohjelmistoversio saapuu ladattavaksi huhtikuun puolivälissä
which translates to: Galaxy S Android 2.3 update to the testing phase is a late stage. The new version of the software download arrives in mid-April,
if these sources are correct Samsung owes us all a apology as they promised march we will be getting gingerbread
or by getting gingerbread they meant leaked ?
TechKidTarek said:
if these sources are correct Samsung owes us all a apology as they promised march we will be getting gingerbread
or by getting gingerbread they meant leaked ?
Click to expand...
Click to collapse
An apology for what - all news we were receiving the past months were "unofficial sources" or rumours or "i know i guy who knows a guy who works at S", I never actually read anything official, e.g. on a samsung website.
Even though the news, which was "almost" official (samsung romania facebook), rejected an actual release date at the end of march.
Just stay relaxed, an update will come in a few hours / days / weeks / years
Kind regards,
ww
I don't know why people always think that they deserve an apology from Samsung or that they get bad software support. Does anybody here have a written (or otherwise) guarantee that Sammy is giving us GB at a specific time? I guess not...
I admit that the first Eclair ROMs were crap and the GPS could be better, but seriously stop the whining, it's like talking with little kids that want their candy! Just wait until it's done and if it takes two weeks longer to sort out some bugs, then so be it...
I agree....they should apologize for possibly not living up to "a friend of a friend said" rumors, or for changing their roadmap to suit the pronouncements off the cuff on the facebook page of a regional Samsung distributer in a small market?
Really?
Or because Tricky used what he felt could possibly be the final 2.3.3 (though from user reports if it IS final, to quote Ricky Ricardo, Samsung's got some 'splainin to do) to make a big entry into the ROM Kitchen team?
Somehow I don't think so. No apologies required, from anyone. Just patience.
To be honest, considering no source is released and there seem to be various problems/quirks with JVK, I would prefer they take a couple weeks and give us a much more ready for prime time version.
Relax, Gingerbread is coming...just be patient and enjoy your 2.2.1 Custom ROMs and be grateful again you aren't stuck with just a single flavor of iOS.
Since I'm a new user and I cant post links, I'm just going to quote. Finnish branch of Samsung has announced a press release a few hours ago through a publishing company:
Translated in Google Translate said:
Samsung Android-range success of the phone Galaxy S is updated Android 2.3. Update arrives in mid-April.
Soon Android successful Android phone is updated Android 2.3 (Gingerbread)-version of the software. The update is a welcome gift for the Galaxy S owners. Update the test phase is late stage, and the new OS version arrives users to download in mid-April.
Click to expand...
Click to collapse
Google "epressi Samsung Galaxy S 2.3" for the article and translate it through Google Translate.
I'm wondering why the press release is not on Samsung's website.
VillePie said:
I'm wondering why the press release is not on Samsung's website.
Click to expand...
Click to collapse
Until it IS on Samsung's website, or we see it in Korean, I would tend to take that with a grain of salt.
FFS...
You have Gingerbread now. It's stable and useable. This can't hold you over a few more weeks?
I swear people just like hearing themselves *****.
am now on 2.3.3
gingerbread!
why wine about waiting for kies just flash it ya self.
curls1 said:
am now on 2.3.3
gingerbread!
why wine about waiting for kies just flash it ya self.
Click to expand...
Click to collapse
Maybe because it looks like JVK is not the final release version and still has some bugs?.
The thing with these web blogs and tech news pages is they all tend to get their "exclusive" news from the same sources which 9 out of 10 times are wrong. Case in point recent news quoting Samsung Mobile Facebook page which wasn't as it was the SamsungGalaxyS Facebook page which looked remarkably similar until you read the owner info. Something you would think they would check first really. Egg face say no more.
electrotune1200 said:
FFS...
You have Gingerbread now. It's stable and useable. This can't hold you over a few more weeks?
I swear people just like hearing themselves *****.
Click to expand...
Click to collapse
I can't see why people can't use their time anticipating the new release. It's not your time, obviously. Some people want to flash their phone with a safe, official firmware and want to know some ETA when it's going to happen. It's not like people are F5'ing every Android news site. Of course, this can hold but can't there be any speculation? It's up to XDA's moderators to decide, is this topic worth of discussing.
What comes to the first post, this is good news (if true) and in my opinion most reliable newsbit so far about Gingerbread. You shouldn't take it for granted that Samsung is liable to update its firmwares and "breaks promises" if doesn't. Operating as a company, Samsung's every firmware update is giving something to us, the customers. When people buy their phones, Samsung's is not liable to update firmwares if there's nothing critically wrong with it. Froyo is good but now we are on the road towards something even better. And it's a win-win situation to us.
Tehpriest said:
Maybe because it looks like JVK is not the final release version and still has some bugs?.
.
Click to expand...
Click to collapse
you must have done somthing wrong then as I have no bugs at all been on it since saturday
I think even mid April is a tad optimistic. That's like 2 weeks.. and there's quite a bit left to fix and add. Together with the speed of which samsung works, I'm guessing May at the earliest.
frauhottelmann said:
I don't know why people always think that they deserve an apology from Samsung or that they get bad software support. Does anybody here have a written (or otherwise) guarantee that Sammy is giving us GB at a specific time? I guess not...
I admit that the first Eclair ROMs were crap and the GPS could be better, but seriously stop the whining, it's like talking with little kids that want their candy! Just wait until it's done and if it takes two weeks longer to sort out some bugs, then so be it...
Click to expand...
Click to collapse
+1
Sent from my GT-I9000 using XDA Premium App
Samsung dont owe you anything. They provide roms where others stopped. Sit back and wait for the final...
Sent from my GT-I9000 using Tapatalk
http://www.gottabemobile.com/2011/1...ist-which-phones-will-get-ice-cream-sandwich/
So where's ICS for the Shift, HTC?
We might as well start getting on them now since they held out forever on the kernel source. The shift is so under rated still.
I don't really see us "officially" getting ICS. Like Sparksco said, the Shift is severely underappreciated.
I do know we have a couple devs working on it though...
I think its a very possible we will see one because
At first I would have said no way we would get it when HTC released Sense 3.0 which only supported Dual-Core devices. That would make you think any later version after 3.0 would also be a definite no and we will never see ICS (officially for the shift) and we know HTC will have to update Sense UI to a later version for ICS
But then again now HTC released Sense 3.5 on devices which is optimized to run on Single Core phones so now if they do update Sense it leaves room to think maybe their next iteration of sense will be compatible with lower end phones to (don't take that to context to much the shift IS very powerful)
We might also see an update like the EVO got when it recieved gingerbread. It got the firmware upgrade to gingerbread but HTC still kept it at 1.0
So their is always the possibility it could be our turn for that.
and now with the Handset alliance thing which HTC is apart of I believe, part of the ruling is you have to support a device for 18 months with latest updates as long as hardware allows.
If anything we know we will be waiting longer than most devices out there anyway if we do end up getting it. The phone is underappreciated a lot, just like the article says (to be honest I was suprised they even mentioned it)
But yea its basically time to start bugging HTC as much as we possibly can for some kind of update. I know I will start
crump84 said:
I don't really see us "officially" getting ICS. Like Sparksco said, the Shift is severely underappreciated.
I do know we have a couple devs working on it though...
Click to expand...
Click to collapse
I love you crumpy but that wasn't the question!
VICODAN said:
I love you crumpy but that wasn't the question!
Click to expand...
Click to collapse
Haha.. well to answer your question.. Trololol away..
*puts on troll hat*
VICODAN said:
*puts on troll hat*
Click to expand...
Click to collapse
Let us know what they say and I'll also ask htcdev about it on twitter
Sent from my PG06100 using xda premium
sparksco said:
Let us know what they say and I'll also ask htcdev about it on twitter
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
https://www.facebook.com/htcusa/posts/231659726902311
Official response from HTC USA on Facebook:
Hey guys. If you haven't seen our latest note on ICS, you can catch it here. http://on.fb.me/vSPMMr We will be announcing more phones later so just because it hasn't been announced yet doesn't mean that it won't be in the future.
Trolling HTC is utterly useless. They're not in charge of whether or not we get an official ICS update. If you must troll someone, troll Sprint. To that end, it's really not worth it IMO. Trolling for the kernel source was warranted, because GPL requires them to release it. They're not required to release ICS and honestly, I doubt they will when they could spend that time and money on more popular phones. I love my little shifty but am not in denial of it's popularity. Who really cares if we get an official update? Most of us would end up running a custom version of it anyway and at this rate, we'll see CM9 or other AOSP builds before long. Hell, toast already says he's got a source build running great, it's only a matter of time. Why pull your hair out waiting for an official update?
HTCotta said:
Trolling HTC is utterly useless. They're not in charge of whether or not we get an official ICS update. If you must troll someone, troll Sprint. To that end, it's really not worth it IMO. Trolling for the kernel source was warranted, because GPL requires them to release it. They're not required to release ICS and honestly, I doubt they will when they could spend that time and money on more popular phones. I love my little shifty but am not in denial of it's popularity. Who really cares if we get an official update? Most of us would end up running a custom version of it anyway and at this rate, we'll see CM9 or other AOSP builds before long. Hell, toast already says he's got a source build running great, it's only a matter of time. Why pull your hair out waiting for an official update?
Click to expand...
Click to collapse
Either way we're still waiting. The G1 and other older phones have a more working funtional rom or ICS then we do.
Sent from my PG06100 using xda premium
HTCotta said:
Trolling HTC is utterly useless. They're not in charge of whether or not we get an official ICS update. If you must troll someone, troll Sprint. To that end, it's really not worth it IMO. Trolling for the kernel source was warranted, because GPL requires them to release it. They're not required to release ICS and honestly, I doubt they will when they could spend that time and money on more popular phones. I love my little shifty but am not in denial of it's popularity. Who really cares if we get an official update? Most of us would end up running a custom version of it anyway and at this rate, we'll see CM9 or other AOSP builds before long. Hell, toast already says he's got a source build running great, it's only a matter of time. Why pull your hair out waiting for an official update?
Click to expand...
Click to collapse
Useless? We got GB kernel source code fairly quickly once we started trolling them. It is important we get an official update from HTC more than you know.
GB source code was always coming, we were quite literally entitled to it (GPL). This is not the case with an ICS update. I know that getting an official update helps immensely, but we're certainly not gonna get one by trolling HTC. It's Sprint's decision.
VICODAN said:
Useless? We got GB kernel source code fairly quickly once we started trolling them. It is important we get an official update from HTC more than you know.
Click to expand...
Click to collapse
Yes your right it is important that we get a official update. A new kernel could really help a lot even if it was a sense kernel.
Sent from my PG06100 using xda premium
HTCotta said:
GB source code was always coming, we were quite literally entitled to it (GPL). This is not the case with an ICS update. I know that getting an official update helps immensely, but we're certainly not gonna get one by trolling HTC. It's Sprint's decision.
Click to expand...
Click to collapse
It's not just sprints choice. It's a partnership between sprint and htc. We just need to express that we do want a official update to htc because htc will listen to us, and might come up with something with sprint. Sprint will not listen to us about a official update because all the do is tell htc which phones are more popular and which ones they think should get the updates first, and then htc goes on it's happy way to make a update. Meanwhile they throw in some of sprints apps (big deal). Htc does most of the work. They do all the kernels, and most of the rom development.
Sent from my PG06100 using xda premium