The early gingerbread release is designed to keep people happy. so they make an update happen on the 20th of June with android 2.3.3 system is complete but they aren't done with RIL, kernel and modem optimization. They fork the most stable branch of the ril, kernel, and modem from samsung source tree. They delay this release from 2 weeks to 1 month. (usually the update comes in 2 week after successfully testing it). They did it to make the span between update seem short.
I think there is another update with 2.3.4 and stable optimized stuff after 2 week in "samsung time" after the initial update to gingerbread *
* "Samsung time" may be 4x more than expected
just my 2 cents
noobnl said:
The early gingerbread release is designed to keep people happy. so they make an update happen on the 20th of June with android 2.3.3 system is complete but they aren't done with RIL, kernel and modem optimization. They fork the most stable branch of the ril, kernel, and modem from samsung source tree. They delay this release from 2 weeks to 1 month. (usually the update comes in 2 week after successfully testing it). They did it to make the span between update seem short.
I think there is another update with 2.3.4 and stable optimized stuff after 2 week in "samsung time" after the initial update to gingerbread *
* "Samsung time" may be 4x more than expected
just my 2 cents
Click to expand...
Click to collapse
meh, not buying it. more to gain by keeping on course. lots of phones doing it right now so bricks and problems are so expected that they can write it off.
I take this as a bad news!
Nice to see you back noobnl.
Since most phones are not on gingerbread yet, I'm not surprised if it is delayed.
Sent from my SPH-D700 using XDA App
He is saying we will have the gingerbread update on the 20th then another even more optimised update after that. So there's no delay. We will be on gingerbread it will just get better ppl so be happy
silver03wrx said:
He is saying we will have the gingerbread update on the 20th then another even more optimised update after that. So there's no delay. We will be on gingerbread it will just get better ppl so be happy
Click to expand...
Click to collapse
Exactly what I was reading. Sorry, for wandering off course, read it too fast.
Sent from my SPH-D700 using XDA App
I sorta agree with noobnl, if anything it makes it look like they are trying hard to keep it updated by having more updates...
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
ecooce said:
I sorta agree with noobnl, if anything it makes it look like they are trying hard to keep it updated by having more updates...
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
Click to expand...
Click to collapse
really, this isn't too bad. I wouldn't call it "... look like they are trying hard..."
I'd call it here's a 'fairly' stable build. play with it while we watch XDA for the bugs, we'll tweak the bugs, then do a maintenance release to fix the bugs
If anything this is a good thing for their PR.. they've had a bad rap over the years regarding updates.. this (so far) has been a welcomed change of pace IMO
I agree.
I accept any updates with open arms.
Sent from my perfect epic
noobnl said:
The early gingerbread release is designed to keep people happy. so they make an update happen on the 20th of June with android 2.3.3 system is complete but they aren't done with RIL, kernel and modem optimization. They fork the most stable branch of the ril, kernel, and modem from samsung source tree. They delay this release from 2 weeks to 1 month. (usually the update comes in 2 week after successfully testing it). They did it to make the span between update seem short.
I think there is another update with 2.3.4 and stable optimized stuff after 2 week in "samsung time" after the initial update to gingerbread *
* "Samsung time" may be 4x more than expected
just my 2 cents
Click to expand...
Click to collapse
Of course they'll probably release bug fixes. You made a "prediction" out of something that's more or less a truism.
However, I disagree. Aside from the camera and keyboard, the Epic is very much like the Nexus S 4g. They already have complete source for that. Aside from integrating Sprint Spyware and Touchwiz, very little has to be done from the existing Nexus S 4g. Major stability issues would exist here.
Now, the Nexus S 4G does have known bugs, which is where the truism part comes in. The Epic will be subject to any bugs the Nexus has, otherwise they would have fixed it there first. It's well known that the Nexus S 4g gets sub-par data speeds. Whether or not this will be transferred to the Epic is to be determined.
You also set your margins of error pretty wide, first saying they'll be deploying ril, modem, and kernel fixes, then in your second stanza saying they'll be rolling out "optimizations". Employing fixes in the base layers critical to stability of the platform are hardly optimizations. Further, you cite 2 weeks for this prediction, and then expand it to 2 months. This is a pretty large window.
At what point in this blathering of a post did you actually make a prediction?
Again, that's just his predictions/presumptions. Don't flamed the poor guy. Just like everyone else, all are just predictions and presumptions. When updates hit your phone, then it will. Stop flaming the dude before he goes into extinction for another few months! LOL
jnadke said:
Of course they'll probably release bug fixes. You made a "prediction" out of something that's more or less a truism.
However, I disagree. Aside from the camera and keyboard, the Epic is very much like the Nexus S 4g. They already have complete source for that. Aside from integrating Sprint Spyware and Touchwiz, very little has to be done from the existing Nexus S 4g. Major stability issues would exist here.
Now, the Nexus S 4G does have known bugs, which is where the truism part comes in. The Epic will be subject to any bugs the Nexus has, otherwise they would have fixed it there first. It's well known that the Nexus S 4g gets sub-par data speeds. Whether or not this will be transferred to the Epic is to be determined.
You also set your margins of error pretty wide, first saying they'll be deploying ril, modem, and kernel fixes, then in your second stanza saying they'll be rolling out "optimizations". Employing fixes in the base layers critical to stability of the platform are hardly optimizations. Further, you cite 2 weeks for this prediction, and then expand it to 2 months. This is a pretty large window.
At what point in this blathering of a post did you actually make a prediction?
Click to expand...
Click to collapse
As soon as you have something usefull to say, post it. Until then, just read.
Sent from my perfect epic
zanderman112 said:
As soon as you have something usefull to say, post it. Until then, just read.
Sent from my perfect epic
Click to expand...
Click to collapse
What he said.
I see a lot of facts not in evidence here, and a lot of wishful thinking. My feeling is that you're sadly mistaken if Samsung worries about the appearance of "keeping up" or that not releasing updates in a timely manor is "bad PR". I would hazard a guess that less than 5% of the Epic 4G user base hangs out here, or even spends much time thinking about what OS they run. They don't care unless it's broken, and the current version isn't.
It's easy to wish for it, and even try to project your reality onto the situation, but here's the fact - Samsung is a HUGE company and the Epic 4G accounts for probably .002% of their biz. They aren't losing sleep over what the Epic user base is thinking about. Heck, a few months ago we didn't even think that GB was in the cards for the Epic.
So I guess my opinion is that it will happen when it happens. To try and read between the lines is no better than a wild guess at this point.
ccnd8 said:
Again, that's just his predictions/presumptions. Don't flamed the poor guy. Just like everyone else, all are just predictions and presumptions. When updates hit your phone, then it will. Stop flaming the dude before he goes into extinction for another few months! LOL
Click to expand...
Click to collapse
Before people flame me, I was partially being facetious. Hence the
Not hatin', noobnl.
zanderman112 said:
As soon as you have something usefull to say, post it. Until then, just read.
Click to expand...
Click to collapse
I did post my counter-thoughts. Beyond mirroring Nexus S 4g, any future patches should be mainly stability improvements in the TouchWiz/Android integration. Gingerbread, despite being a minor update in looks, was a huge update in API. A lot of stuff is likely broken that will slip QA.
There will always be follow-up patches in any software release cycle. The Epic had 2/3(?) patches for Eclair, 2 patches for FroYo, and probably no less than 2 for GB, since it'll be the last update for a while, if ever.
I apologize for posting my counter-thoughts in his thread. Next time I will make a new one.
I also apologize for coming off as attacking noobnl. I wasn't aware he had a beer flavored schlong.
noobnl said:
The early gingerbread release is designed to keep people happy. so they make an update happen on the 20th of June with android 2.3.3 system is complete but they aren't done with RIL, kernel and modem optimization. They fork the most stable branch of the ril, kernel, and modem from samsung source tree. They delay this release from 2 weeks to 1 month. (usually the update comes in 2 week after successfully testing it). They did it to make the span between update seem short.
I think there is another update with 2.3.4 and stable optimized stuff after 2 week in "samsung time" after the initial update to gingerbread *
* "Samsung time" may be 4x more than expected
just my 2 cents
Click to expand...
Click to collapse
Well if there is anyone's 2 cents around here I would put money on its noobnl. If there is anyone who knows what goes into developing the OS and what goes into making it all work it would be noobnl or Dameon87. Two of the most recognized and respected names in Epic 4g hacking history in my own opinion. Many of the newer users in the past few months have no clue who these two people are or what they have done but if it wasn't for these guys we wouldn't have squat for the Epic 4g. Before anyone doubts what these two and others have to say they should do their studying and read up on who's names are all over OneClickRoot, CWM and many other things we use constantly in rooting and hacking with the Epic 4g.
Just my 2 cents...
zanderman112 said:
As soon as you have something usefull to say, post it. Until then, just read.
Click to expand...
Click to collapse
LOL, coming from you.
Paul627g said:
Well if there is anyone's 2 cents around here I would put money on its noobnl. If there is anyone who knows what goes into developing the OS and what goes into making it all work it would be noobnl or Dameon87. Two of the most recognized and respected names in Epic 4g hacking history in my own opinion. Many of the newer users in the past few months have no clue who these two people are or what they have done but if it wasn't for these guys we wouldn't have squat for the Epic 4g. Before anyone doubts what these two and others have to say they should do their studying and read up on who's names are all over OneClickRoot, CWM and many other things we use constantly in rooting and hacking with the Epic 4g.
Just my 2 cents...
Click to expand...
Click to collapse
Oh, I agree, Noobnl, Dameon87, and k0nane are the **** around here. This community would be largely lost without them.
They're not the best though, that title is reserved for dzo, the guy who got Android working from largely scratch on the HTC Touch (Windows phone), my old community.
I'm aware of the integration aspects of Android. I've compiled my own AOSP for the HTC Touch, built a GPS driver for the HTC Touch, and done some RIL hacking / development. Further, I was employed for 3 years as a linux developer for small platforms just like these phones. Alas, I do not have the time commitment nor the strive anymore unlike those three above.
I give my hat to them, but I am more than capable of making my own highly experienced opinion.
bigray327 said:
LOL, coming from you.
Click to expand...
Click to collapse
Wait, what is that supposed to mean? I'm very helpful lol
Related
From : http://www.google.com/support/forum...488da0ef21660d1300048994d2e4bf4c&hl=en&hltp=1
Ry Guy
Google Employee
07:03 PM
Hey guys,
Just dropping in to let you know that the FRF72 build that is floating around is not the official update. The Android team is feverishly working to get a final version out the door, but like passion-ate has mentioned this will only happen once a release candidate meets our quality criteria.
Since today is the Summer Solstice, we know things will be heating up a bit so hopefully Froyo will be on its way shortly. Thanks for your continued patience!
-Ry Guy
So… that tells us… not very much but we now know 2 things:
* FRF72, which was the latest official leaked Froyo build, was not the final version (we kind of already suspected that)
* and Froyo is still not ready
cool, thnx for the info
And so the wait continues...
Then again if the google guys think that FRF72 still doesn't meet their standards... could be a good thing.
I'm expecting the OTA'd Froyo to have the option to take over Apple's servers and Ddos them to pieces.
watch, we will have waited all this time for froyo and instead we get gingerbread. (crosses fingers and hopes)
Good to know...seems like Google is taking QA to a new level!
http://encyclopedia2.thefreedictionary.com/When+It's+Done
(jargon) When It's Done - A manufacturer's non-answer to questions about product availability. This answer allows the manufacturer to pretend to communicate with their customers without setting themselves any deadlines or revealing how behind schedule the product really is. It also sounds slightly better than "We don't know".
sandtiger said:
http://encyclopedia2.thefreedictionary.com/When+It's+Done
(jargon) When It's Done - A manufacturer's non-answer to questions about product availability. This answer allows the manufacturer to pretend to communicate with their customers without setting themselves any deadlines or revealing how behind schedule the product really is. It also sounds slightly better than "We don't know".
Click to expand...
Click to collapse
just hopefully it wont be as bad as BlackMesaSource's "When its done" this mod has taken like 3 years
lalalalala
Blueman101 said:
just hopefully it wont be as bad as BlackMesaSource's "When its done" this mod has taken like 3 years
Click to expand...
Click to collapse
Pretty sure its actually five years in the making because I've been watching for 3 years and I'm sure they started in 04-05 right after half life source came out. nothing compared to duke nukem forever
JCopernicus said:
lalalalala
Click to expand...
Click to collapse
This newb is curious, how are you tracking these things?
flybyme said:
.....nothing compared to duke nukem froyo
Click to expand...
Click to collapse
Needed a small edit, all fixed now.
funny how long its taking google when they seemed so confident at I/O that it would be out shortly. what did they discover i wonder that suddenly needed so much attention?
anyway it doesnt bother me. but i know the complainers in the main google forum arent as forgiving. i have to wonder, what do those people think, that google is holding back 2.2 on purpose? what would be the hidden motive!
RogerPodacter said:
funny how long its taking google when they seemed so confident at I/O that it would be out shortly. what did they discover i wonder that suddenly needed so much attention?
anyway it doesnt bother me. but i know the complainers in the main google forum arent as forgiving. i have to wonder, what do those people think, that google is holding back 2.2 on purpose? what would be the hidden motive!
Click to expand...
Click to collapse
I agree, its tough to be mad since we already have it anyway. But I'm with you I'm intrigued by the delay, not put off by it. Hopefully google will not be too embarrassed to announce what caused the delay.
Re: Google Officially Updates Us On Froyo Status FRF72 Was Not Final,
I'm still excited, they work hard at Goggle, I'm sure the official update its going to be great when its ready.
I think we should have stick to 2.1 till the official froyo comes up,it's good to see that Desire to N1 Roms are active again
Rodriguezstyle ROM with FRF72 us amazing already
Fastest, smoothest Android I've ever used.
Cant wait for 75
So FRF72 is not the final build. What will be in the new build. Is there a list available what items is not met yet in the FRF72 build?
All this time I always have a feeling that froyo is being delayed due to flash! My thought is that they are waiting for the final flash build to optimize froyo for it.
Adobe has released Full flash 10.1 to android androidcentral.com/adobe-releases-flash-101-partners
so dont think they are waiting on flash anymore
and whilst waiting for flash to be ready they thought. "Hey, let's watch some korean drama and worry about gingerbread later"
http://groups.google.com/group/android-building/browse_thread/thread/091172a81604c8a0?pli=1
Nexus S went on sale yesterday morning in the US, running Gingerbread.
Just like I did for Froyo, I'm open-sourcing the matching Android
platform source code, right after the first consumers get their hands
on it. I'm going to start literally right now, and the process will
take a few hours.
I'll give more details once the source code is available. However,
there are three aspects that you need to know ahead of time:
-As part of the process to push the source code, there will be some
points in time when the master branch doesn't build. Sorry about that.
If you're working on the master branch, I recommend that you don't
sync until I send an "all clear" when I'm done and things look good.
Other branches are expected to work fine as soon as their manifests
are created.
-Even though Nexus S is designed to be suitable for AOSP work, there
are some caveats. I very strongly recommend against trying to use
Nexus S for anything related to AOSP at the moment. Trying to unlock
or use your Nexus S for AOSP work could easily turn it into a Nexus B
(where B means "brick"); I have two of those, they're not very useful.
I'll send some guidelines about what is currently possible once I've
finished pushing the source code.
-Please take it easy on the kernel.org servers. They are very helpful
in hosting the AOSP source code, and I don't want to hurt the high
quality of their service with an onslaught of full Android downloads.
If you're not going to immediately work on porting Gingerbread to
devices with the intent of distributing the result to end-users, I'm
kindly asking that you wait a few hours or a few days before you
download it (just roll a 6-sided die and wait that long). In addition,
the slower the servers are, the harder it is for me to do the push.
Thanks for being patient.
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Click to expand...
Click to collapse
Yay!
Let's bombard Cyanogen's Twitter! J/K``
Hope something good for my incredible comes out of this
Sent from my ADR6300 using XDA App
Can't wait! The quicker the source is released the faster we will have Gingerbread baked into our roms
First one to get an AOSP build of 2.3 running on the G2 will be my new hero.
lol @ the software engineer having two Nexus B's already ;D
silverton said:
lol @ the software engineer having two Nexus B's already ;D
Click to expand...
Click to collapse
Hey! It happens to best of us... I've bricked a couple myself and I was a cell tech for 5 years, worked my way up department mgr., been a pc tech/network engineer for 10 years and have A+, NET+, C++, and bachelors in computer science. Also, I bricked my wife's like 6 months ago, lol! It happenes to even the most technical person...
Wowo!!!!! Can't wait! I've been on the virtous for some time now, because I really like the sense shell, but it's strait over to CM again (been there many times allready) when 2.3 comes!!!
Yeah, I've been waiting to permaroot for CM7. I was going to permaroot for CM6.1.1 this weekend, then this news broke, so I think I'll wait for 7. Or maybe I'll go ahead with 6.1.1.
Who knows!
@cyanogen
Prepare for spam!!
I just looked at aosp and I see next to nothing updated yet so I dunno
@cyanogen WILL come through quickly for the G2. I'm sure of it.
Shady Gambino said:
Yeah, I've been waiting to permaroot for CM7. I was going to permaroot for CM6.1.1 this weekend, then this news broke, so I think I'll wait for 7. Or maybe I'll go ahead with 6.1.1.
Who knows!
Click to expand...
Click to collapse
Why wouldn't you permroot now? Nearly double CPU clock, the ability to disable throttling, superuser access.
In my experience, the first implementation of new code is often quite buggy. While I can't wait for 7.0, I suspect I may end up waiting for 7.1 or 7.0.1 before I update.
tornado9015 said:
While I can't wait for 7.0, I suspect I may end up waiting for 7.1 or 7.0.1 before I update.
Click to expand...
Click to collapse
That's half the fun
Follow cmrsc on twitter for updates on compiling a blue-berry flavored gingerbread.
Sent from my HTC Vision using XDA App
sino8r said:
Hey! It happens to best of us... I've bricked a couple myself and I was a cell tech for 5 years, worked my way up department mgr., been a pc tech/network engineer for 10 years and have A+, NET+, C++, and bachelors in computer science. Also, I bricked my wife's like 6 months ago, lol! It happenes to even the most technical person...
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
I want to be just like you when I grow up
silverton said:
lol @ the software engineer having two Nexus B's already ;D
Click to expand...
Click to collapse
I was a bit skeptical about that - seeing as he's kinda high on the totem pole @ Google/Android Devs... you would think they'd have more than a few ways to debrick a device that touts their name on it. Sure the hw is made by Samsung, but I doubt the devs were submitting all revisions and rcs of GB to Samsung like - "Hey guys, could you flash this for us, I don't think we have the tools or knowledge".
Come on msm7x30 support!
Blades said:
I was a bit skeptical about that - seeing as he's kinda high on the totem pole @ Google/Android Devs... you would think they'd have more than a few ways to debrick a device that touts their name on it. Sure the hw is made by Samsung, but I doubt the devs were submitting all revisions and rcs of GB to Samsung like - "Hey guys, could you flash this for us, I don't think we have the tools or knowledge".
Click to expand...
Click to collapse
He probably has a stack of cell phones and probably tries to brick some of them on purpose. He probably just gives back the bricks to Samsung.
ctraywick1 said:
Sent from my HTC Vision using XDA App
I want to be just like you when I grow up
Click to expand...
Click to collapse
Thanks, I guess... hard to detect sarcasm in writing My point was... bricks happen!
Just flashing the proper way, epecially packed ones with a bootloader, you can brick even when you do everything correctly. I've flashed over 500 phones (may be more) and it will happen. The nice thing is though, when you are a cell tech, just pop out the board and get another one. Manufacter's warranties for carriers are surprisingly lax... so, yeah we did brick some on purpose, lol
Cyanogen via twitter:
My G2 seems to have Gingerbeard on it. How did that happen?
Click to expand...
Click to collapse
(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.
Before I get to my point I want to thank all the devs for there hard work that they do in their spare time. They do it for free and hope that some of us donate to make it a little more worth their while.
Maybe it's just me or does it seem like the development thread is slowing down. I've noticed lately that most of the stuff coming in now is ports from other phones and updates for past builds. Theres not alot of new stuff rolling out. EDT seems to stay busy, but what happend to TW? I would have put money on having a stable 2.3 rom out by now to use as a daily driver. We also lost Eugene and leaked samsung builds seem to not be coming out as often.
Is our phone entering the twilight years? Are the dev's losing interest and working on other phones. I've played around with some of the new phones like the atrix and thunderbolt and i'm sure they could be a lil more interesting to build for.
I hope i'm wrong and 5 min. after I post this a new 2.3 rom comes out. It was fun when you flashed a new trigger rom and 1 day later the new bionix came out. This is a really nice phone and you have to really try hard to brick it. It's almost like Samsung designed it to be modded. Hopefully the devs can get inspired again or some new blood comes in to give us something new.
I think we need to be patient. One day there will be a leak for gb and things will fire up again.
Sent from my SGH-T959 using XDA Premium App
just relax man every phone goes through spells of development. I see you only joined in april so just wait, Whitehawkx had a mostly working gb port working minus the gps and we have CM7 and MIUI support now as well.
Be patient this phone is amazing and im certain development will continue for it for some time.
In the mean time flash a miui beta or try out the EDT roms you wont be disappointed.
Lets not forget Simply Galaxy v3 a 2.3.3 rom. Yes still developing but stable.
Once we get a proper kernel you'll see more Gingerbread roms as for right now you have a ton of quality 2.2.1 and 2.2 roms to chose from.
Of course the OP is welcome to start developing on their own and contribute.
Sent from my GT-I9000 using XDA Premium App
u guys keep us coming back for more every day and i thank you for that! great job on all this.
explodingboy70 said:
Lets not forget Simply Galaxy v3 a 2.3.3 rom. Yes still developing but stable.
Once we get a proper kernel you'll see more Gingerbread roms as for right now you have a ton of quality 2.2.1 and 2.2 roms to chose from.
Of course the OP is welcome to start developing on their own and contribute.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Yes, but point being is that we're pretty much at the mercy of Samsung & T-Mobile to release a 2.3.
We will not have a kernel source to play with until it releases for I9K, and even then we'll have issues for a while. And we won't have one with rockin' battery life until we get a leak or source.
But yeah, there really isn't much developing coming from anyone except the guys working on kernels & people like Whitehawk, sonique, and of course Untermench who actaully modify the code. Because there's not much else to do.
Things are winding down. There are only a handful of people around who have the knowledge and inclination to roll their own ROMs.
As newer devices with more capabilities are introduced (the dual core LG G2X will be in T-mobile stores April 20th), then the older ones lose favor.
That is how it is with Android. Your 8 month old phone becomes old. After 15 months its an antique!
explodingboy70 said:
Lets not forget Simply Galaxy v3 a 2.3.3 rom. Yes still developing but stable.
Once we get a proper kernel you'll see more Gingerbread roms as for right now you have a ton of quality 2.2.1 and 2.2 roms to chose from.
Of course the OP is welcome to start developing on their own and contribute.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
I actually have tried to develop a theme to post here but there is so much involved with all the editing and i simply don't have the time. I really wish I did. Trust me I have a great respect for what the dev's do once I started playing around with just a theme. I can only imagine what a rom would take. Plus I can honestly say i'm not skilled enough to put out a quality rom any time soon, if ever. I'm really not complaining about effort or quantity from the devs, i've just noticed lately there seems to be a dull in the dev section. I was just wondering why.
Eugene is back. He said on twitter that he bought a Vibrant. You can see evidence, his newest Ginger Clone version has already had 4 updates.
Sure a lot of the development is for 2.2 and 2.2.1 roms, but I'd say we're easily WAY more active than we used to be. We've now got plenty of choices of roms, kernels, and themes. We've also got new people joining the Vibe development scene. There's an experimental Gingerbread Sense that's just started testing. We are now officially supported by the MIUI team. I see new things happening every day. Development doesn't always happen overnight, but I believe we've still got lots of good things look forward to.
Slowing down? I still remember when there was only one rom in the dev section. Now there's a new one each week, and at least one update every day.
Tarzanman said:
Things are winding down. There are only a handful of people around who have the knowledge and inclination to roll their own ROMs.
As newer devices with more capabilities are introduced (the dual core LG G2X will be in T-mobile stores April 20th), then the older ones lose favor.
That is how it is with Android. Your 8 month old phone becomes old. After 15 months its an antique!
Click to expand...
Click to collapse
I still dont understand what people are trippin on. We have some blazing fast 2.2.1 ROMs and a few gingerbread ROMs that are stable. What functionality are people looking for int he Vibrant that we dont have?
dcontrol said:
Slowing down? I still remember when there was only one rom in the dev section. Now there's a new one each week, and at least one update every day.
Click to expand...
Click to collapse
Haha yeah I remember that too. But ROMs every week != good. Most of them are ports and aren't stable.
I really wish we could have AOSP roms so we could have TRUE development going on. None of this hack and patch stuff.
regP said:
I still dont understand what people are trippin on. We have some blazing fast 2.2.1 ROMs and a few gingerbread ROMs that are stable. What functionality are people looking for int he Vibrant that we dont have?
Click to expand...
Click to collapse
They want CM lol (as do I)
Why do we keep having these threads. I rooted my phone late last year. I have been more then satisfied. I'm just glad to have a faster better phone than what I had originally. Just have some damn patience.
Sent from my GT-I9000 using XDA App
Keep in mind the psychology at work here. Most of the people who get all angsty about this are rom comsumers, and not active dev's, themers, or kangers.
It appears that what we are experiencing now is a lot of cross development, taking existing roms from the international i9000 and porting them to our universe thanks to the availability of kernel source for 2.2. So the nature of activity has changed, but the scope has actually expanded.
This phone (thanks to dev work here @ XDA) stopped sucking ass A VERY LONG TIME AGO. Gains to be had at this point are largely cosmetic, so there is the appearance that improvements are not coming at the rate they used to. The fact of the matter is that quantitative improvements are largely unnecessary at this point.
As a "consumer" myself (I gave up on linux development a long time ago, owing to my own inherent laziness) I find the current state of affairs quite amazing. Your mileage may vary. YMMV.
What's funny is that people much prefer a broken ROM that gets fixed rather than a fully working ROM out of the box ^_^
masterotaku said:
Keep in mind the psychology at work here. Most of the people who get all angsty about this are rom comsumers, and not active dev's, themers, or kangers.
It appears that what we are experiencing now is a lot of cross development, taking existing roms from the international i9000 and porting them to our universe thanks to the availability of kernel source for 2.2. So the nature of activity has changed, but the scope has actually expanded.
This phone (thanks to dev work here @ XDA) stopped sucking ass A VERY LONG TIME AGO. Gains to be had at this point are largely cosmetic, so there is the appearance that improvements are not coming at the rate they used to. The fact of the matter is that quantitative improvements are largely unnecessary at this point.
As a "consumer" myself (I gave up on linux development a long time ago, owing to my own inherent laziness) I find the current state of affairs quite amazing. Your mileage may vary. YMMV.
Click to expand...
Click to collapse
Well said. It's just like what happened when I had the N1, people started to complain because the roms were so stable there weren't many updates being released.
regP said:
I still dont understand what people are trippin on. We have some blazing fast 2.2.1 ROMs and a few gingerbread ROMs that are stable. What functionality are people looking for int he Vibrant that we dont have?
Click to expand...
Click to collapse
i dont know either...
2.3 probably WILL be faster than 2.2 (duh) but besides the speed, we have everything else.
All thats going to be different is when you go into settings about it will say 2.3 gingerbread
instead of 2.2 or 2.2.1
the rest is good.
im on miui, and i switch between cm7 and miui once in a while
im never going back to 2.2.1
birgertime said:
What's funny is that people much prefer a broken ROM that gets fixed rather than a fully working ROM out of the box ^_^
Click to expand...
Click to collapse
Very true. People want updates, but they don't know why.
If its not being updated as fast as it used to, chances are it doesn't even really NEED updating.
birgertime said:
What's funny is that people much prefer a broken ROM that gets fixed rather than a fully working ROM out of the box ^_^
Click to expand...
Click to collapse
Well said. Someone just asked on one of my 2.2.1 threads why it was so quiet and my only thought was because everything works. Here it is everything has been fixed there should be nothing left to discuss here flash and enjoy.
Sent from my GT-I9000 using XDA Premium App
thegreatcity said:
Very true. People want updates, but they don't know why.
If its not being updated as fast as it used to, chances are it doesn't even really NEED updating.
Click to expand...
Click to collapse
That's the point for me. I stopped updating at KA6. Sure KA7 came out not long after, but why? I had been updating daily/weekly until then, always fighting some bug or flaw. With KA6, I flashed the ODIN version, removed bloatware myself, added the round battery icon, power off menu, and that was *it*. More recently I've updated the Kernel to Overstock 2.x and voodoo FS, but I'm not even sure why I need voodoo. Can't tell a difference in the real speed of the phone.
I didn't take the phone apart to add FFC like so many did (and who also never use it in most cases), so I don't need improved support for that... and themes, well... I guess there is that, not much going on in KA6 themes -- but that doesn't affect the use of the phone at all.
KA6 for me has been fast, stable, and by far the best on battery life of any I've touched yet. There are few if any programs out there that require 2.3 or higher, and until that is the case, why change?
The atmosphere is totally different than it was last fall, when the rest of the world was going 2.2 and Vibrant was stuck on 2.1. At that time, there were an increasing number of programs that simply would not work on Eclair - plus Froyo had been promised as an update. Now we have everything Samsung promised, and really if you're running a lightly modded ROM, it *is* bug-free.
So... until I am forced to consider 2.3, I'm sticking with KA6.. It is nice after years of constantly flashing upgrades on the HTC Vogue (wm6), then the G1, then flashing the MT3G constantly, then constantly flashing the Vibrant, to actually pick up my phone and have it work the same way it did yesterday.
It's been bothering me that a lot of people don't think the atrix is going to get an official ice cream sandwich update.
I decided to make this thread to consolidate any discussion or questions about the future update.
The android carrier alliance promises that any device will be updated to the newest version of android for 18 months after its release (if its hardware allows it).
Three points to make:
1) Since ICS is being released in oct/nov, the 18 months portion of the agreement becomes null and void. The atrix is within the timeframe.
2) The nexus S is getting ICS, and since the hardware in the atrix is superior (dual core processor, battery, etc), the atrix can receive the ICS update.
3) With google's acquisition of MM the likeliness of the atrix receiving ICS has gone up substantially, whether or not it remains as a seperate branch under google's ownership. It also increases the chances of us getting a stock (or very close to stock) ICS build.
All these signs point me to believe that the atrix is for sure getting ICS. What're your thoughts?
Cheers
Also I think the Atrix Dev Team will be handing their CM7 build over to Cyanogenmod for nightlis and it will be an official CM device. And if that happens, when Cyanogenmod makes CM8 with ICS we'll get it the I'd guess.
4 Words...
Who gives a crap.
Didn't they announce that after the release of the Atrix ? Or does that not matter?
Sent from my MB860 using XDA Premium App
I think my thread was cooler.
I voided my warranty.
Magnetox said:
3) With google's acquisition of MM the likeliness of the atrix receiving ICS has gone up substantially, whether or not it remains as a seperate branch under google's ownership. It also increases the chances of us getting a stock (or very close to stock) ICS build.
Click to expand...
Click to collapse
I think that while Google's purchase/buyout seems like it may benefit Android users. I also feel that it will not give any benefits until long after the Atrix has passed it's sell by date. Mergers and acquisitions take time to complete. Systems have to be integrated on a large scale, and corporate policies realized in the acquired business. I think Google's initial focus will be on patents, and secondary long term focus will then be Android, and how they can take the lions share of the marketplace with smart devices (not just phones). Give it 2 years at least in my opinion before we see a big swing.
This is almost the exact same thing I said over in the Motorola Forums (or maybe I said it here, I can't remember). It seems people expect things to change immediately but probably don't realize it's not even a done deal yet as of this posting. There still needs to be an investigation and approvals and all that. Like you said, it could be a couple years before any changes (within Motorola's camp anyways) becomes noticeable.
CaelanT said:
I think that while Google's purchase/buyout seems like it may benefit Android users. I also feel that it will not give any benefits until long after the Atrix has passed it's sell by date. Mergers and acquisitions take time to complete. Systems have to be integrated on a large scale, and corporate policies realized in the acquired business. I think Google's initial focus will be on patents, and secondary long term focus will then be Android, and how they can take the lions share of the marketplace with smart devices (not just phones). Give it 2 years at least in my opinion before we see a big swing.
Click to expand...
Click to collapse
Also, it seems people forget that Motoblur exists on Motorola devices. Unless they actually convert the Blur service into a full on application platform I don't see an "Official" ICS build coming to the Atrix until at least 6 months after Google releases the code for it. Our best bet lies within the great devs we have here in the community. Which reminds me, everyone, stop complaining about updates!
live4nyy said:
This is almost the exact same thing I said over in the Motorola Forums (or maybe I said it here, I can't remember). It seems people expect things to change immediately but probably don't realize it's not even a done deal yet as of this posting. There still needs to be an investigation and approvals and all that. Like you said, it could be a couple years before any changes (within Motorola's camp anyways) becomes noticeable.
Click to expand...
Click to collapse
Here's the thing, yes Google will have a flava of it sitting around that XDA can port over.
The real question is what's the ETA with the carriers?
For instance my Motorola Milestone didn't have "Froyo" ready until the end of March this year, and it was a half-assed effort put together by Telus. Then shortly after, they discontinued the phone.
I agree that XDA users will have a port of ICS through CM7, but for OTA who knows when that will be?...
Sent from my MB860 using xda premium
Magnetox said:
It's been bothering me that a lot of people don't think the atrix is going to get an official ice cream sandwich update.
I decided to make this thread to consolidate any discussion or questions about the future update.
The android carrier alliance promises that any device will be updated to the newest version of android for 18 months after its release (if its hardware allows it).
Three points to make:
1) Since ICS is being released in oct/nov, the 18 months portion of the agreement becomes null and void. The atrix is within the timeframe.
2) The nexus S is getting ICS, and since the hardware in the atrix is superior (dual core processor, battery, etc), the atrix can receive the ICS update.
3) With google's acquisition of MM the likeliness of the atrix receiving ICS has gone up substantially, whether or not it remains as a seperate branch under google's ownership. It also increases the chances of us getting a stock (or very close to stock) ICS build.
All these signs point me to believe that the atrix is for sure getting ICS. What're your thoughts?
Cheers
Click to expand...
Click to collapse
Your first point is completely wrong. They guaranteed updates to the phone, but never specifically to the "latest version" of android released. IE you will get security/bug fix updates, but not necessarily updates to the base OS. Secondly, this only applies to phones released AFTER the agreement. Also, google is merely urging NOT requiring them. So basically, all this agreement leads to is that future devices will have a minimum of an 18 month support cycle, nothing more.
Right after we get GB, people start asking for ICS...
This even shows more proof that we, as human, will never be satisfied with what we got.
which can be both good and bad..
tian105 said:
Right after we get GB, people start asking for ICS...
This even shows more proof that we, as human, will never be satisfied with what we got.
which can be both good and bad..
Click to expand...
Click to collapse
There are no humans here, only Androids and Androids are selfish.
Sent thru a series of tubes using XDA Premium app
I read this...sounds like we are going to be seeing it next month...
http://www.pocket-lint.com/news/41975/android-ice-cream-sandwich-release-date
Mac
Mac11700 said:
I read this...sounds like we are going to be seeing it next month...
http://www.pocket-lint.com/news/41975/android-ice-cream-sandwich-release-date
Mac
Click to expand...
Click to collapse
my bday is next month lol and this would make a great gift comming from googrola
tian105 said:
my bday is next month lol and this would make a great gift comming from googrola
Click to expand...
Click to collapse
I saw this on my b-day yesterday...
Mac