Database Info

[Q] Will Gingerbread be optimized for the Galaxy S phones?

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 ..

[Q] Samsung Captivate Source Code Now Open?

I think I just made a mess in my pants. Can someone confirm this??? Here is the letter:
Dear _____________,
You can download the source code of SGH-I897 on this site in Mobile Category, SGH-I897 model.
Thank you.
Weighing in at about 161 megabytes, the code should assist developers wishing to work on custom Captivate ROMs. Samsung Captivate owners have been eager to see their first custom builds as the device has sold thousands already since its nationwide launch at AT&T on the 18th.
In particular, there is one mod that Captivate owners are excited about the most: the “mimocan external SD card lag fix.” The fix promises to double Quadrant benchmark scores as the application data is moved to the external memory. Right now, the Samsung Galaxy S series outperforms every processor in every phone in every category except for the I/O benchmark in Quadrant. The Galaxy S scores so poorly because of Samsung’s implementation of the internal memory, but mimocan’s lag fix remedies this problem and raises Quadrant scores to new heights around 1750.
With Android 2.2 just around the corner for American Samsung Galaxy S owners, Captivate users could be seeing benchmarks around 2000-3000 with the JIT compiler and mimocan lag fix.
So, what are you waiting for? You can download the open source code below or at Samsung’s Open Source website.
Download SGH-I897_Opensource.tar.gz
Click to expand...
Click to collapse
Originally Posted Here

Google is your friend https://encrypted.google.com/search...s=org.mozilla:en-US:official&client=firefox-a this letter is from last summer. Now go clean up and put on some new pants.

Every time they officially release a firmware, they are required to release source code. So, yes, captivate source code has been available for JF6 and JH7 for a while.
And with Rogers already released 2.2 firmware, they will have to release source code to Roger 2.2 as well.
Mind you, not everything is released in source code. For most part, drivers are not open source released.

Someone just posted over in the dev forums, the Rogers 2.2 Source is live (just downloaded this morning) so hopefully we'll see some nice updates on the ROMs in the next several days...

pinoymutt said:
Someone just posted over in the dev forums, the Rogers 2.2 Source is live (just downloaded this morning) so hopefully we'll see some nice updates on the ROMs in the next several days...
Click to expand...
Click to collapse
these have all been out for a while

[Q] (Q) I9000 2.3 kernel for the cappy?

Is there an JV1 or other gingerbread kernel from 19000 for the cappy, or is there someone working on it. CM7 isnt that great with battery and many other things i figer the I9000 kernels for 2.2 kernels work as well if not better for cappy.
was hopeing to try I9000 gingerbread on my cappy.
thanks pm or post here.

the source code for the i9000 gingerbread has not been released yet since there hasn't even been an official release of the i9000 gingerbread. without the source code, the kernel cannot be reoriented to have the buttons working and the correct headset logic.
Sent from a phone, playing a phone, disguised as another phone.

I see this makes sence, so its a waiting game still! thanks

you can remap the buttons after you flash the rom and disable auto rotate, that will fix the ui stuff but you will not be able to use your headphones.
if you want to try it, people were doing this with with i9000 roms since day one, there are fewer active people that are experimenting now but it should still be possible. i would if i had a second device but i like haveing music on my headphones.
if i feel up to it i might do it this weekend to write an idiot proof procedure and post it in general section but i doubt ill keep it.
it is a shame we dont have the source because from the benchmarks i see with cm7 it seems that the hummingbird responds very well to gingerbread, this chip keeps getting better as android catches up, infact in a few ways it is faster than some dualcore platforms, maybe not overall but there are areas that the hummingbird is untouchable. forget that omap chip in the driod x and the snapdragon. the hummingbird excells in areas that are not measured in market apps, but still holds its own against everything else in other areas, and beats them when matched with gingerbread.
it is funny that every time i see a benchmark that shows the strength of the hummingbird in a tech article someone brings up quadrant and the omap chip and say that the benchmark is inacurate but if you pay for quadrant you see that the droid x only beats hummingbird in areas that dont involve the cpu! dumb asses dont know when they are beat. i hate motorola and there dishonest advertising. hummingbird is weak in floating point operations and that's about it.

Not international, only US?

Looks like the infuse (SGH-i997) may only be a US phone? Basic google searches didn't reveal anything obvious like I would expect, for example the i9000 (galaxy s).
I know a lot (not all of course...) of the great innovations in terms of lag fix, rom/kernel dev work came from people working on the international i9000. I wonder if this will limit the diversity in kernels, roms...
Mine is on the way anyway

schahr01 said:
Looks like the infuse (SGH-i997) may only be a US phone? Basic google searches didn't reveal anything obvious like I would expect, for example the i9000 (galaxy s).
I know a lot (not all of course...) of the great innovations in terms of lag fix, rom/kernel dev work came from people working on the international i9000. I wonder if this will limit the diversity in kernels, roms...
Mine is on the way anyway
Click to expand...
Click to collapse
well im not saying you can interchange with a galaxy s. that is not true. but many methods when applied to the infuse sources will have little difference from the galaxy s in implimentaion. so in a way this may develope faster than the sgs2 or the sgsplus or the sgs2mini which all have much more major changes.

Dani897 said:
well im not saying you can interchange with a galaxy s. that is not true. but many methods when applied to the infuse sources will have little difference from the galaxy s in implimentaion. so in a way this may develope faster than the sgs2 or the sgsplus or the sgs2mini which all have much more major changes.
Click to expand...
Click to collapse
I hope so too. Really sucks that they didn't release it w/ 2.3 out of the box. Samsung CAN do it, look at the nexus s. Hopefully only a minor setback and they'll release the update OTA... yeah right

schahr01 said:
I hope so too. Really sucks that they didn't release it w/ 2.3 out of the box. Samsung CAN do it, look at the nexus s. Hopefully only a minor setback and they'll release the update OTA... yeah right
Click to expand...
Click to collapse
well they need the sgs 2 to look that much better. they fear we are too stupid to know what a dual core chip is. they need this to look good for the money and the sgs2 to look better. samsung did get the first 2.3 update out and the first 2.3 phone out that was not a google dev phone so cut them some slack. they are working hard on there flagship models. this will come later. google says they will work with manufacturers to get all capable handsets updated to 2.3 or 3.1, probably to keep android from getting too fractured. they will put pressure on them for updates and the manufacturers will get less ambitious with changes.
samsung also announced the north american sgs line will get 2.3 but did not indicate a timeline. unfortunately this is not being called a sgs so that statement is not a garentee but i think att has more concerns about updating the infuse than the captivate so if samsung says the captivate gets an update i think att will push for the infuse to get an update beforehand.

A little hope to be official.

The CyanogenMod team will be dropping support for devices with the older processors including the Nexus One & the Bravo (many more, too).
I think this means The CyanogenMod team will start focusing one more devices with dual-core processors. I think.. including the Blaze 4G. What do you guys think.?
Sent from my bathroom.

Not unless we get a SGS4G in the hands of a dev, or convince one of them to grab it over something else.

Didn't know the S3 chip is old lol. My brother has a Galaxy S3 and honestly in everyday performance this phone does not fall behind and often surpassed the S3. I tested both phones in a bunch of games and tasks. The number of cores on a phone is a bit overestimated.
Sent from my SGH-T769 using xda premium

i don't think we will get an official update from the cyanogenmod team!
http://wiki.cyanogenmod.com/wiki/Samsung_Galaxy_S:_FAQ

while the CPU for our phone came out almost 2 years ago, it's capable of running ICS just fine... the T989 is proof of that, it's virtually identical to ours. What we need is the kernel sources for this phone for ICS and that can only come from Samsung. Once that is released, setting up ICS should be easy. Hell, we could just copy the majority of the T989 (T-Mo SGS2) source tree for CM.

dr4stic said:
while the CPU for our phone came out almost 2 years ago, it's capable of running ICS just fine... the T989 is proof of that, it's virtually identical to ours. What we need is the kernel sources for this phone for ICS and that can only come from Samsung. Once that is released, setting up ICS should be easy. Hell, we could just copy the majority of the T989 (T-Mo SGS2) source tree for CM.
Click to expand...
Click to collapse
sounds good!! hope we get it soon!!