Related
Hi everyone!
Has anyone tried the Android 2.2. aka Froyo! Was released yesterday and Google claims it's 5x faster!!!
Also has 20 new tools and a new Javascript engine, 3x more powerful!!
rsoares8 said:
Hi everyone!
Has anyone tried the Android 2.2. aka Froyo! Was released yesterday and Google claims it's 5x faster!!!
Also has 20 new tools and a new Javascript engine, 3x more powerful!!
Click to expand...
Click to collapse
Thanks for info! I think nobody here know about that!
lol... sorry, I bet you all do, but wanted to share anyway, for the ones as distracted as I am.
http://developer.android.com/sdk/android-2.2-highlights.html
rsoares8 said:
lol... sorry, I bet you all do, but wanted to share anyway, for the ones as distracted as I am.
Click to expand...
Click to collapse
yeh...whats 'google'?
adam18488 said:
yeh...whats 'google'?
Click to expand...
Click to collapse
ah nothing like a bit of satorical sarcasm. lol
wonder how long it will take the first 2.2 ROM to come out? a week maybe?
or do we need it on a phone before it can be cooked into a rom?
g1 already has roms, running the sdk 2.2
but we need to wait till the asop comes out before they get stable
What's a cell phone?
g1 already has roms, running the sdk 2.2
but we need to wait till the asop comes out before they get stable
Click to expand...
Click to collapse
Well let's hope we get some gsm hero ones at top speed lol
-------------------------------------
sent through psychic projection
I got it on my G1 right now. Kinda sucks with no Google, but it's ight.
I've got Froyo on my N1.
Android 2.1 cm506: 8 mflops
Android 2.2 stock: 41 mflops
JIt enabled in 2.2
new V8 javascript engine 3x faster.
Android 4.5x faster.
waiting for asop source code to get a 2.2 ROM !!
leonnib4 said:
I've got Froyo on my N1.
Android 2.1 cm506: 8 mflops
Android 2.2 stock: 41 mflops
JIt enabled in 2.2
new V8 javascript engine 3x faster.
Android 4.5x faster.
waiting for asop source code to get a 2.2 ROM !!
Click to expand...
Click to collapse
The browser is the only thing thats really faster in day to day use. Yes the cpu is tons faster but I dont think 2.1 even maxed the cpu on the n1. I thought getting froyo would keep me from getting the evo 4g but i just pre ordered my evo 4g.
Now Froyo is supposed to be a major milestone with Android, but, frankly, I think the same thing was said about Android 2.1. I don't care much for the USB tethering (because we already have that), wifi hotspot feature (because I'm not going to use it), and so on, but there are a few major points of things I'm hanging on.
Notably, the supposed performance improvement being 2-5x greater than Android 2.1 That is a big claim and, if true, then the Captivate will be completely lag free on stock. If so, the usability on this phone will just shoot straight up. The smoother transition and animation should also help this greatly.
I'm not too concerned about having Flash 10.1, but Froyo is also supposed to come with numerous other improvements. I know the browser is being updated to support some hardware features, but I hope Google is also improving the general usability of the browser. As it is now, it kind of sucks. Additionally, I also hope the Youtube app is also updated.
Nonetheless, even if all the others remain nothing more than a dream, I, at the least, hope the improvement performance/transitions/animation turns out to be something of substance.
Well, here's to September.
The Captivate has plenty of cpu power... it seems that most of the lag we are expeirencing comes with the filesystem Samsung has chosen to use and it's poor I/O performance. I'm not sure if Froyo will help too much - but I would expect that once 2.2 hits the custom ROM scene will really kick off, and hopefull somebody will implement YAFFS or whatever some of the other phones (Nexus 1, etc) are using.
We may see better battery life if the system needs fewer CPU cycles to accomplish the same tasks it's doing now.
Don't forget - we'll also receive the new kernal which should double the available RAM from 256mb in 2.1 to 512mb in 2.2 - though the system seems to currently report there is currently 325mb aviable. In either case, it will be a big increase - though I'm not really having any memory issues at the moment.
I'm trying not to get too excited for it, but it does make some impressive promises.
^ Well, Samsung does have its own customized version of Android. I'd imagine that the one they're rolling out in September will contain an improved filesystem (as I've heard that Samsung is currently aware of the issue) and, in combination with Froyo's own improvements, should do a lot to help Android perform better.
I wasn't aware of the kernel thing. I don't see how is that possible, though. The Captivate has a total of 512MB RAM, so wouldn't it need a part of that in order to operate normally?
The new kernel in 2.2 has HIMEM support and supports more than 256mb, which is what 2.1 is limited to. I'm not sure if Samsung tweaked the kernel to support the 325mb we have now or how that figure is derived, but right now we can't use all the RAM that the Captivate packs.
^ I looked up info on 'HIGHMEM' and I see what you mean now. The updated kernel supports devices with RAM greater than 256MB RAM. I thought you actually meant that the kernel will make all 512MB available for the user.
Alright, that sounds good. I guess the additional support may be why there is supposed to be increased smoothness and animation.
8525Smart said:
Now Froyo is supposed to be a major milestone with Android, but, frankly, I think the same thing was said about Android 2.1. I don't care much for the USB tethering (because we already have that), wifi hotspot feature (because I'm not going to use it), and so on, but there are a few major points of things I'm hanging on.
Notably, the supposed performance improvement being 2-5x greater than Android 2.1 That is a big claim and, if true, then the Captivate will be completely lag free on stock. If so, the usability on this phone will just shoot straight up. The smoother transition and animation should also help this greatly.
I'm not too concerned about having Flash 10.1, but Froyo is also supposed to come with numerous other improvements. I know the browser is being updated to support some hardware features, but I hope Google is also improving the general usability of the browser. As it is now, it kind of sucks. Additionally, I also hope the Youtube app is also updated.
Nonetheless, even if all the others remain nothing more than a dream, I, at the least, hope the improvement performance/transitions/animation turns out to be something of substance.
Well, here's to September.
Click to expand...
Click to collapse
I totally agree with you. I couldn't care less about tethering, hotspot or Flash. I never used them and never will. I just don't need them.
The only thing I care about is the speed improvement. I don't really believe it will have 2-5x improvement boost because, well, every claim is exaggerated. But I am expecting something.
That said, I am not too optimistic though. I have tried several Droid 2 in Verizon stores. It's very disappointing. It feels rather sluggish and laggy. Even worse than the Captivate now. And apparently Engadget reviewer agrees with me.
So as much as I welcome the birth of 2.2, I am not as optimistic as others.
And final words, I don't think we'll get the update in Sept. I think Samsung will (hopefully) release it in Sept, but it will take AT&T another month or two to load their crap.
I wish I am wrong.
mwxiao said:
And final words, I don't think we'll get the update in Sept. I think Samsung will (hopefully) release it in Sept, but it will take AT&T another month or two to load their crap.
I wish I am wrong.
Click to expand...
Click to collapse
Since the test roms that have come out are from Samsung and they already have AT&T crap on them, I believe its safe to assume that Samsung is making the roms for AT&T. So, there should be no extra step for AT&T to load their crap...it should come directly from Samsung.
Considering 2.2 has gotten a ton of praise from other phones that are already using it I'm sure our Froyo will be a worthwhile upgrade as well. Sure, Samsung might screw the pooch on some things again, but overall it will be better.
This isn't Windoze, how can an upgrade be disappointing?
Bring on the Froyo!
cappysw10 said:
This isn't Windoze, how can an upgrade be disappointing?
Click to expand...
Click to collapse
I am sure an update is always good. But if it doesn't meet the high expectations, it will be a disappointment. And I think the expectations are pretty high.
mwxiao said:
That said, I am not too optimistic though. I have tried several Droid 2 in Verizon stores. It's very disappointing. It feels rather sluggish and laggy. Even worse than the Captivate now. And apparently Engadget reviewer agrees with me.
Click to expand...
Click to collapse
Whoa, looks like I was a bit outdated. I actually hadn't realize Motorola's Droid 2 was using Froyo already (I still thought the Nexus One was the only phone that had it ).
Regarding the September release, I actually thought it was taking until September because Samsung is currently modifying all of their Froyo ROMs for each individual smartphone/carrier. After all, Froyo has technically been released already, so why else is Samsung taking until September to officially release it to all of their handsets?
glio1337 said:
Considering 2.2 has gotten a ton of praise from other phones that are already using it I'm sure our Froyo will be a worthwhile upgrade as well. Sure, Samsung might screw the pooch on some things again, but overall it will be better.
Click to expand...
Click to collapse
That's just the thing, though. As I said, prior Android releases have garnered praise too. Eclair has gotten praise and was said to improve hardware performance, have a better browser UI, improved virtual keyboard, and so on. Of those three, I think the only one I would agree has truly improved is the virtual keyboard (I think the Android keyboard works very well on Eclair). The other listed improvements? Not so much.
Of course, Froyo will be better overall, but I just hope it's actually a milestone release with the proclaimed changes making a big difference instead of just steadily updating the platform with people telling me afterwards to wait for Gingerbread.
When reviews from places like Gizmodo, Engadget, Boy Genius etc say that they think 2.2 is a worthy step up from 2.1, I tend to take it as truth.
Regardless of any of that, all of the goodness from 2.2 is dependent on Samsung/ATT because they have the power to muck it up badly as they did with 2.1.
glio1337 said:
When reviews from places like Gizmodo, Engadget, Boy Genius etc say that they think 2.2 is a worthy step up from 2.1, I tend to take it as truth.
Regardless of any of that, all of the goodness from 2.2 is dependent on Samsung/ATT because they have the power to muck it up badly as they did with 2.1.
Click to expand...
Click to collapse
Really? I find engadget and gizmodo to be awful at everything but aggregating news. Their opinions are always so uninformed and seem to be governed by whatever the fashionable opinion at the time.
Their product reviews are pretty good, or at the very least talk about the things most people would care about.
8525Smart said:
After all, Froyo has technically been released already, so why else is Samsung taking until September to officially release it to all of their handsets?
Click to expand...
Click to collapse
Samsung needs to customize it for its hardware and put on Twisted-Wiz UI. It's slow.
That's just the thing, though. As I said, prior Android releases have garnered praise too. Eclair has gotten praise and was said to improve hardware performance, have a better browser UI, improved virtual keyboard, and so on. Of those three, I think the only one I would agree has truly improved is the virtual keyboard (I think the Android keyboard works very well on Eclair). The other listed improvements? Not so much.
Of course, Froyo will be better overall, but I just hope it's actually a milestone release with the proclaimed changes making a big difference instead of just steadily updating the platform with people telling me afterwards to wait for Gingerbread.
Click to expand...
Click to collapse
I don't believe a 0.1 upgrade will be considered as milestone. We will definitely see speed improvement. But it's normal for every update. You always wait for the next update. It's always snappier.
glio1337 said:
When reviews from places like Gizmodo, Engadget, Boy Genius etc say that they think 2.2 is a worthy step up from 2.1, I tend to take it as truth.
Click to expand...
Click to collapse
Of cause it's gonna be a worthy update. It's always worthy to upgrade to the next version. The question is, is it going to be as dramatic as they claimed? Personally, I don't think so.
cappysw10 said:
This isn't Windoze, how can an upgrade be disappointing?
Bring on the Froyo!
Click to expand...
Click to collapse
Gotta love windows haters...
Any way, I cannot wait for froyo because I want to be able to move apps to the SD, to use flash without having to use Skyfire and using the extra memory should help too.
Plus I am expecting a TON of ROMs when it comes out so slowly but surely they phone would be maximize.
shaolin95 said:
...be able to move apps to the SD...
Click to expand...
Click to collapse
Quoted for truth
I am more looking forward to an official lag fix and GPS fix moreso than Froyo.
I just read somewhere that JIT was written for the snapdragon processors and that while it may give us a little performance it wasn't really written for the hummingbird processor in our phones...so the chances of Samsung rewriting it just for us is probably very slim
The claims of 2-5x performance increase do seem hard to believe, but I believe these figures came from actual testing on the Nexus One running 2.2. Of course, I think we all know how reliable benchmarks are...
September is only a few hours away... where is our Froyo!!
Would the community rather have 2.2 by tomorrow, with no indication or promise of future updates, or 3.0 almost as soon as it comes out? I'm curious to see the community opinion.
Good question. I know a lot more about 2.2 right now, and the JIT compiler, developer push notifications and Flash in the browser are pretty good things.
I really don't think we're getting 3.0
Without knowing how it runs on our phone or using it, who would sign up for it? This is a loaded question - wait for some reviews then ask the question.
And when you say "when 3.0 is released" - I assume you mean Mid October even though it is not possible for a port to hit our phone for months?
The only logical answer is to say 2.2 now - 3.0 is an unknown - when will it be available and how will it run on our hardware? What features does it add? etc.
And in the end, everyone would say give me 2.2 now and still complain later when they can't update to 3.0.
k2snowboards88 said:
I really don't think we're getting 3.0
Click to expand...
Click to collapse
That is correct. Samsung has only committed to one major update and that is FroYo.
Everyone knows how much Samsung hates giving software updates so you can bet the house that Gingerbread is not coming to Galaxy S. They'll be on to their next big thing by then. They refuse to waste software engineers on putting out updates once they already have your money.
derek4484 said:
That is correct. Samsung has only committed to one major update and that is FroYo.
Everyone knows how much Samsung hates giving software updates so you can bet the house that Gingerbread is not coming to Galaxy S. They'll be on to their next big thing by then. They refuse to waste software engineers on putting out updates once they already have your money.
Click to expand...
Click to collapse
If that was honestly the case I'd never buy another Samsung product again. I'm locked into this phone for at least two years, it should last at least 4. This thing had better get 3.0 at least. I'll give them the benefit of the doubt for now, I haven't had too many samsung experiences in general.
From the little I've read, it sounds like 3.0 is more intended for larger devices.
brandonb81 said:
If that was honestly the case I'd never buy another Samsung product again. I'm locked into this phone for at least two years, it should last at least 4. This thing had better get 3.0 at least. I'll give them the benefit of the doubt for now, I haven't had too many samsung experiences in general.
Click to expand...
Click to collapse
Samsung is notorious for not giving software updates. Once they have your money they dont care about you.
Ask anybody else who's had a samsung smartphone. Especially anyone with a Samsung Beam, they just announced yesterday 2.1 is as far as its going and its a pretty new phone. Samsung Moment did get one update from 1.6 to 2.1 but thats as far as its going and that phone is still pretty new, its was only released less than a year ago. Other samsung phones never even got a single update they're still on 1.5/1.6.
brandonb81 said:
If that was honestly the case I'd never buy another Samsung product again. I'm locked into this phone for at least two years, it should last at least 4. This thing had better get 3.0 at least. I'll give them the benefit of the doubt for now, I haven't had too many samsung experiences in general.
Click to expand...
Click to collapse
I would have to agree. Not only would I never buy another Samsung product but I'd tell anyone that would listen not to buy one either.
jdsemler said:
From the little I've read, it sounds like 3.0 is more intended for larger devices.
Click to expand...
Click to collapse
Thats not true. The next version is certainly designed for phones. Google was bragging about Gingerbread at their last conference.
The carrier is just as responsible for software updates as the manufacturer. If the carrier has no interest, then Samsung won't build it.
cappysw10 said:
I would have to agree. Not only would I never buy another Samsung product but I'd tell anyone that would listen not to buy one either.
Click to expand...
Click to collapse
I agree that they should be legally required to give you updates for however long your contract is. But they dont. Samsung has already stated they are going to give us one major update, and that is from 2.1 to 2.2. They'll give maintenance updates but thats it.
I think we will receive 3.0 - the only logical reason we wouldn't would be if another wave of Galaxy S phones came in that were twice as powerful.
Currently we are boasting a 1GHz processor, 512mb of RAM and a 4" AMOLED screen. Top of the line as smartphones are concerned. Now If a 2GHz, 1GB Ram phone came out then I could see us possibly not getting 3.0.... but I personally think it's the reason why Samsung has been so quiet about our 2.2 questions.
The Original Motorola Droid was on 2.2 before the Droid X! - sometimes pre-existence is better ;D
We have the exact recommended specs for gingerbread. Google released them a few weeks ago. I don't see a point release (2.1 - 2.2) as being a major update. Granted, its a nice bump in terms of upgrades and additions but is not what I would consider major.
I would like to see 2.2 as soon as possible, and then maybe 3.0 if Samsung bothers to get it done (which I would only give a 50% chance of occuring).
It's important to get 2.2 onto these phones so the developers can use it as the base for their modifications and ROMs. I think the chances of getting 2.2 in late october or mid november are pretty good, but I wouldn't expect 3.0 to land until next year (if it happens).
I'm really looking forward to 2.2, but I want the newest version of Swype even more urgently. I can't believe I have this device that says "look at me I have swype," but doesn't even have any way of getting the newest version with the text input button. Heck, I would even pay a few bucks to get the latest version, but there's simply no way at all to get it.
Is seriously doubt we'll get 3.0. I would be happy with a GPS fix and 2.2.
gtg465x said:
Is seriously doubt we'll get 3.0. I would be happy with a GPS fix and 2.2.
Click to expand...
Click to collapse
This. Just make this phone actually work and I'll be happy.
I would be happy as hell with ASOP 2.2, anything that has no touch wiz.
Sent from my HTC Dream using XDA App
gtg465x said:
Is seriously doubt we'll get 3.0. I would be happy with a GPS fix and 2.2.
Click to expand...
Click to collapse
I would imagine, though, that with Cyanogenmod having brought Froyo 2.2 to the T-Mobile G1, we will get a version of 3.0 on our Captivates even if it is not from Samsung.
elgo said:
I would imagine, though, that with Cyanogenmod having brought Froyo 2.2 to the T-Mobile G1, we will get a version of 3.0 on our Captivates even if it is not from Samsung.
Click to expand...
Click to collapse
I guess maybe I'm just a pessimist, but what would make you think that cyanogen would bring 3.0 to the Captivate? They havent even brought 2.2 to it yet?
Im sure most of you have seen this buy now, but I figured, no harm in posting it. Lucky nexus users......
http://www.engadget.com/2010/11/08/open-handset-alliance-member-confirms-android-2-3-is-gingerbread/
Yup.
Saw it here too
http://www.informationweek.com/news/smb/mobile/showArticle.jhtml?articleID=228200423&itc=ref-true
This makes Samsung look lazy..
mymansionisabox said:
This makes Samsung look lazy..
Click to expand...
Click to collapse
Gingerbread landing on Google's own developer phone prior to every other handset makes Samsung look lazy?
hawkeyefan said:
Gingerbread landing on Google's own developer phone prior to every other handset makes Samsung look lazy?
Click to expand...
Click to collapse
Because Samsung has yet to launch 2.2 on their own "premiere" Galaxy S line of phones.
Of course, this is my opinion.
2.2 has been released officially since May 2010.
Droid X was released July 15th, with Android 2.1
Android 2.2 was pushed OTA to Droid X on September 22, 2010
Samsung Captivate was released July 18th with Android 2.1... still no Froyo
I'm not complaining. I'm stating my opinion...
And now.. 2.3 is coming out and I think most of us would agree. If the N1 can handle 2.3, so can the Captivate, the whole Galaxy S line.
So yes.. lazy.. because now they will have to start working on a release for 2.3 and they haven't even finished a 2.2 release. You and I already know Motorola is on top of this.
Maybe lazy isn't the best choice of words.. but.. whatever. I think you get my point.
Ah, in relation to Froyo, gotcha. I agree to a certain extent.
I highly doubt we will see an official 2.3 release...
Sent from my SAMSUNG-SGH-I897 using Tapatalk
hawkeyefan said:
Ah, in relation to Froyo, gotcha. I agree to a certain extent.
Click to expand...
Click to collapse
Yeah haha. I mean I'm not bashing Samsung. I'm just in fear that they might be a bit over their heads now.
They basically are going to have to stay in constant development with this.. They haven't finished 2.2 yet and now 2.3 is about to be released.
I fear that our phones will be left behind FAR before they really should be.
Idk.. I'm a pessimist a guess.
mymansionisabox said:
Yeah haha. I mean I'm not bashing Samsung. I'm just in fear that they might be a bit over their heads now.
They basically are going to have to stay in constant development with this.. They haven't finished 2.2 yet and now 2.3 is about to be released.
I fear that our phones will be left behind FAR before they really should be.
Idk.. I'm a pessimist a guess.
Click to expand...
Click to collapse
That's strange...last few time I talked with the Galaxy people at Samsung..it was told to me that 2.2 has been finished at all of the Carriers for some time..This makes this very confusing for me to say the least. Is it really Samsung at fault...or the carriers that are at fault with all of the delays of releasing the 2.2 update stateside ? Is it the us based carriers that are adding to it to be able lock the phones down and change things around on it..or Samsung ?
I can understand where folks are saying Android is fragmented if the carriers are causing this, but I don't understand why there can't be unified coding across all manufacturers lines when it comes to the os of Android.After all isn't it based off of ASOP and Linux and isn't that supposed to be all open source..? I do understand the differences in the various hardware requirements between all of the Android phones..but the core os should be the same shouldn't it ? So...who is at fault..the carriers..or Samsung..or both ? Who is really causing the delays..? Who is going to make the determination if any future development happens..the carriers or Samsung ?
Mac
mymansionisabox said:
Motorola is on top of this.
Click to expand...
Click to collapse
ROFL. Motorola is on top of nothing. Bottom maybe with VZW on top. If not for VZW, I don't know that Motorola would EVER push out updates. Just look at what they did with the cliq/backflip/dext/cliqxt/devour... it took FOREVER, and most parts of the world aren't even officially getting it (2.1).
Probably buying HTC from now on. They get cyanogen and sense, and somewhat timely updates
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Flash one of the great leaked 2.2 ROMs......problem solved. A Gingerbread based custom ROM will likely follow at some point.
Personally I do not even believe we will see a official release of 2.2 much less 2.3. Unlikely that we will ever see a GPS fix either at&t has their handsfull with the new windows phone. I also think that at&t is to blame.
Sent from my SAMSUNG-SGH-I897 using XDA App
larmor19 said:
Personally I do not even believe we will see a official release of 2.2 much less 2.3.
Click to expand...
Click to collapse
And why don't you believe 2.2 will be released? Do you know that the Android developers for AT&T aren't the same ones that work on the Windows phone?
tbong777 said:
Flash one of the great leaked 2.2 ROMs......problem solved. A Gingerbread based custom ROM will likely follow at some point.
Click to expand...
Click to collapse
It will be difficult without source from SAMSUNG
Sent from my SAMSUNG-SGH-I897 using Tapatalk
larmor19 said:
Personally I do not even believe we will see a official release of 2.2 much less 2.3. Unlikely that we will ever see a GPS fix either at&t has their handsfull with the new windows phone. I also think that at&t is to blame.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Hmmm... obviously, Samsung is working on a 2.2 release. We have already gotten two leaked builds. The official release will be coming. Now with regards to 2.3. I don't think it's going to happen. It seems as though Samsung is focusing their efforts to push new products rather than support old ones.
"Old Ones?" this phone isnt even 6 months old yet and it'll be obsolete soon. if not for the geniuses here at XDA it would already be obsolete. i love my captivate but i think its getting ready to get left in the dust. hope i get proven wrong though.
Left in the dust? How so? 2.3. Is not even out yet. At least we have leaked versions of froyo...which will still be better then an official one. All we need is the source. The devs can handle the rest from there otherwise the devs spend there time unlocking all the crap that Samsung and att locked down
Sent from my SAMSUNG-SGH-I897 using XDA App
This is what I don't like about Android (well not Android itself, but the Android market)...while N1 owners will be playing with 2.3 I will be stuck with 2.1.
F Samsung/Motorola whoever and their heavily modified ROMS. I don't need your Touchwiz/MotoBLUR/etc...just give me the stock ROM so that you save yourself the headache of upgrading and us too.
Samsung originally released their 2.2 back in late September/October to Europe - then was promptly pulled due to it being complete junk.
Now they are re-distributing it this month with a probably still junk release of 2.2. They screwed up so bad due to all the crap they half-assed into these phones (touchwiz, rfs file system etc...)
Samsung really needs to re-evaluate their development team and decide if they are going to be serious about the software side or farm it out to a third party that can program. Because.... their development department is probably the worst out there when it comes to android development.
I mean... there are probably Kirf teams in China that can code better!
Lazy.. no, greedy and not caring about the consumer and not taking pride the end result? Sure I can go with that.
PixelPerfect3 said:
This is what I don't like about Android (well not Android itself, but the Android market)...while N1 owners will be playing with 2.3 I will be stuck with 2.1.
F Samsung/Motorola whoever and their heavily modified ROMS. I don't need your Touchwiz/MotoBLUR/etc...just give me the stock ROM so that you save yourself the headache of upgrading and us too.
Click to expand...
Click to collapse
This exactly.
Android is supposed to be this huge open source project, and while we can root and mod and flash all we like, we should also have the option of just being able to go to google and get the newest version ourselves.
The fact that not only the carriers (which is to be expected) but the manufacturers feel the need to bloat up the software is frustrating and annoying!
Now that Gingerbread has been written by google for a Galaxy S phone that is very similar in specs to the Galaxy S line, will it be fully optimized?
Will we see big jumps in benchmarks like the Nexus One did when it received Froyo? Is the reason why the Nexus One and its variants received a big benchmark boost was because Android wrote Froyo for it?
I dont think 2.3 will come to captivate....And also, would the GPS been fixed??? Im going to sell my captivate and buy some HTC....
That is ridiculous situation...we are a several months waiting for 2.2 and so far nothing...We are several months waiting for some GPS fix...and so far nothing yet....
AT&T does not care about the customers if they are confortable with the 2.1 only or not....Neither Samsung....WE ARE LOST....hurt me to say that...
But thats how i feel...IM FEEL LIKE A FOOL...
sorry, dont get me wrong....
I doubt with Samsung's record of slow updates and bug fixes we'll ever see an official port of Gingerbread to the Galaxy S. Custom ROM's much more likely but I guess they will be a while.
As for speed increase... Don't hold your breath. I've got the official Froyo 2.2 running on my UK Galaxy S and it boosted my Quadrant benchmark score from 800+ (Eclair) to only 900+ (Froyo) (Nexus One with Froyo 1250). Custom ROM's apparently give better scores. Problem? Samsung again... they use a different file system on the Galaxy S (and I believe the American equivalents) than the official Android one and this slows the device and causes most of the lag problems on it. Watching the Quadrant benchmark the Galaxy flies through the graphics and CPU tests and grinds to a halt when it tries to complete the write to memory test... Froyo didn't help and I doubt an official Gingerbread update would either. I'm afraid flashing an unofficial ROM is the only way to get speed. It can be risky though...
Fizzig said:
I doubt with Samsung's record of slow updates and bug fixes we'll ever see an official port of Gingerbread to the Galaxy S. Custom ROM's much more likely but I guess they will be a while.
As for speed increase... Don't hold your breath. I've got the official Froyo 2.2 running on my UK Galaxy S and it boosted my Quadrant benchmark score from 800+ (Eclair) to only 900+ (Froyo) (Nexus One with Froyo 1250). Custom ROM's apparently give better scores. Problem? Samsung again... they use a different file system on the Galaxy S (and I believe the American equivalents) than the official Android one and this slows the device and causes most of the lag problems on it. Watching the Quadrant benchmark the Galaxy flies through the graphics and CPU tests and grinds to a halt when it tries to complete the write to memory test... Froyo didn't help and I doubt an official Gingerbread update would either. I'm afraid flashing an unofficial ROM is the only way to get speed. It can be risky though...
Click to expand...
Click to collapse
Quadrant is a poor indicator of overall performance, which is why an ext2-loopback lagfixed rom will show astronomical scores (2300+) in Quadrant - because it is essentially telling quadrant exactly what it wants to hear. The score is artificial and doesn't reflect how the device will actually perform (not to imply that the lagfixes don't make the phone more responsive or anything, simply making the point that quadrant is a poor benchmark).
The differences you'll see between 2.1 and 2.2 are an increase in processing power and battery life due to the JIT. It's a bit difficult to test this due to outside battery-eating variables (things syncing over the network in the background, quality of reception and radio power levels, etc.), so your ability to notice a difference may vary depending on your phone usage style and environment.
Also, you can use linpack to get an idea of the processing power increase. You'll notice that it doubles between 2.1->2.2. I should warn you that it's not really comparable to the Nexus One, simply because the cpu architecture is different and linpack is geared to take advantage of it - the n1's snapdragon has a 128bit simd fpu whereas the hummingbird has a 64bit fpu, so the increase in speed will show up as 4x-5x for the n1 between 2.1->2.2. Again, this does not translate into a 4x increase in real world performance. I only mentioned linpack to demonstrate the relative speed increase between stock 2.1 for the galaxy S and 2.2, and to show that the JIT is indeed boosting the processing speed.
SlimJ87D said:
Now that Gingerbread has been written by google for a Galaxy S phone that is very similar in specs to the Galaxy S line, will it be fully optimized?
Will we see big jumps in benchmarks like the Nexus One did when it received Froyo? Is the reason why the Nexus One and its variants received a big benchmark boost was because Android wrote Froyo for it?
Click to expand...
Click to collapse
To my understanding, 2.3 is essentially a more optimized 2.2. I doubt that the results of the optimizations will be as large as the introduction of the JIT was in 2.2, but every little bit helps - and look on the bright side, it won't be any slower than 2.2.
I don't think we'll really know how well the Nexus S roms will run on our phones or how easy they'll be to port over until we actually get our hands on an NS rom (still don't know what filesystem it uses or how big of an obstacle the filesystem will present). However, since the fundamental architecture is so similar, I don't really expect many problems and I expect the 2.3 builds to run great.
Edit: I don't expect Samsung or ATT to release 2.3 for our phones. I actually wouldn't be surprised if ATT refused a gingerbread update for our captivates, even if Samsung offered it. What I meant above was that I expect whatever custom roms we cook up based off of the NS builds to run great.
When do we start speculating about Honeycomb?
alphadog00 said:
When do we start speculating about Honeycomb?
Click to expand...
Click to collapse
When someone in our family (Galaxy S Line) gets it, which will definitely be the Nexus S.
SlimJ87D said:
When someone in our family (Galaxy S Line) gets it, which will definitely be the Nexus S.
Click to expand...
Click to collapse
Why wait... it is all guessing anyway. I think anything we say about Honeycomb has an equally good chance at being accurate as what we say about Gingerbread.
alphadog00 said:
Why wait... it is all guessing anyway. I think anything we say about Honeycomb has an equally good chance at being accurate as what we say about Gingerbread.
Click to expand...
Click to collapse
I don't think you really understand my question.
The nexus one was a developer phone that had a snapdragon in it. Google, the creator of Android, directly engineered their software to be optimized on the device because it was their developer device.
Now that a Galaxy S phone is a developer phone, I was wondering if anyone knew anything about the software engineering side to the Nexus one to guess if google built 2.3 from the ground up for the Nexus S, or can/could heavily optimized the code for it.
Now you're question is to speculate about Honeycomb, speculate what? There's nothing to discuss about it, but my question is legit from an engineering stand point. So I'm still left wondering if this is the case or not, I wonder if there is anyone that can enlighten me.
Would be a nice pipe dream for an offical update.
Sent from my SAMSUNG-SGH-I897 using XDA App
SlimJ87D said:
I don't think you really understand my question.
The nexus one was a developer phone that had a snapdragon in it. Google, the creator of Android, directly engineered their software to be optimized on the device because it was their developer device.
Now that a Galaxy S phone is a developer phone, I was wondering if anyone knew anything about the software engineering side to the Nexus one to guess if google built 2.3 from the ground up for the Nexus S, or can/could heavily optimized the code for it.
Now you're question is to speculate about Honeycomb, speculate what? There's nothing to discuss about it, but my question is legit from an engineering stand point. So I'm still left wondering if this is the case or not, I wonder if there is anyone that can enlighten me.
Click to expand...
Click to collapse
And you don't understand my point: No one knows. We might as well speculate about honeycomb. The Nexus S has a different momory mudule iNand not moviNand. What impact will this have? No one knows until they have phones in hand.
Sent from my MB520 using XDA App
alphadog00 said:
And you don't understand my point: No one knows. We might as well speculate about honeycomb. The Nexus S has a different momory mudule iNand not moviNand. What impact will this have? No one knows until they have phones in hand.
Sent from my MB520 using XDA App
Click to expand...
Click to collapse
What about the CPU though? The memory for the Nexus One and Droid Incredible were different, but yet because they shared the same CPUs they received similar benchmark scores in that department.
What does it matter everyone is going to flash custom ROMS of Gingerbread when/if it ever somehow leaks for our phones.
Sent from my axura phone with Gingerbread keyboard.
Fizzig said:
As for speed increase... Don't hold your breath. I've got the official Froyo 2.2 running on my UK Galaxy S and it boosted my Quadrant benchmark score from 800+ (Eclair) to only 900+ (Froyo) (Nexus One with Froyo 1250). Custom ROM's apparently give better scores. Problem? Samsung again... they use a different file system on the Galaxy S (and I believe the American equivalents) than the official Android one and this slows the device and causes most of the lag problems on it. Watching the Quadrant benchmark the Galaxy flies through the graphics and CPU tests and grinds to a halt when it tries to complete the write to memory test... Froyo didn't help and I doubt an official Gingerbread update would either. I'm afraid flashing an unofficial ROM is the only way to get speed. It can be risky though...
Click to expand...
Click to collapse
This is one of the things that I am optimistic about. Android 2.3 adds support for devices with large internal storage capacities - my understanding is that it was Samsung's poor attempt to hack that support into 2.1 that introduced the issues you mention above. I'm hopeful that this means 2.3 would eliminate the need for lag fixes, and that the better support for some of the cutting edge hardware in the Galaxy S Phones being built into Gingerbread will make it much easier for Samsung to push 2.3 out for our phones.
AdamPflug said:
This is one of the things that I am optimistic about. Android 2.3 adds support for devices with large internal storage capacities - my understanding is that it was Samsung's poor attempt to hack that support into 2.1 that introduced the issues you mention above. I'm hopeful that this means 2.3 would eliminate the need for lag fixes, and that the better support for some of the cutting edge hardware in the Galaxy S Phones being built into Gingerbread will make it much easier for Samsung to push 2.3 out for our phones.
Click to expand...
Click to collapse
Can you elaborate? Coz AFAIK RFS has nothing to do with Samsung's attempt to make a pitiful 16 GB work as internal sd card..
From what I understand, the movinand flash which Galaxy S , when used in RFS performed horribly when doing sync operations (I think I got it from the thread ryanza posted), so, the new flash might as well be Samsung's attempt to correct that error, instead of replacing the (seemingly crap) RFS ..