Galaxy S 2.2.1 ROM? Maybe part of the delay - Captivate General

Saw this http://phandroid.com/2011/01/18/gal...es-said-to-significantly-improve-performance/ and http://androinica.com/2011/01/18/android-2-2-1-update-for-samsung-galaxy-s-now-rolling-out-via-kies/ a short while ago. Perhaps this is part of the overall delay; certainly would make sense as to why (although not as to why Samsung would not comment about it). Anyone seen this ROM to know if it is substantially different from the Canada or other recent Galaxy S Froyos?

Related

Is froyo going to happen?

I am worried about a potential Behold II situation here. This phone has been out internationally for months and we still have no custom roms of 2.2, or even 2.1 only modified versions of Sammys stock.
Are there differences structurally with samsung's programming and files structure that preclude the use of custom roms? I want one of these galaxy s phones but I am concerned that there is no development. What is going on with theses phones?
Random people around the interwebs are saying that the Galxay S should get it's 2.2 update in August sometime.
Not sure how solid their sources are. Once they get it, then AT&T has to get a hold of it and modify it, that will take a few more months I'm sure.
I do not think there is anything stopping chefs from making modified ROMs. They just need to do it. I think some are waiting for 2.2 to come out as it is a much better base for a ROM performance wise.
Some are saying the the bootloader is not locked, which makes it even easier. Now that people can reliably flash back to the stock ROM things should pick up.
I think having 512 MB of RAM is proof enough that 2.2 support will be coming. Otherwise they could have cut the RAM in half and saved money on their end.
Samsung has confirmed many times that 2.2 is coming, and I do believe that. What probably won't happen is 3.0 which this phone should be capable of handling as well (judging from system requirements mentioned to this point). That's where our guys will get to work and try to cook something up.
If someone (not Samsung) can port 2.2 to it, then it bodes well for 3.0...
I'm not worried about 2.2 (Samsung is bringing that, at least)... What worries me is 3.0
Samsung has confirmed that 2.2 is coming, well to the international version at least. They have never specifically said if its coming for T-mo or AT&T versions. In all honesty I'm more concerned with getting Gingerbread. As slack as Samsung is about releasing software updates, this has me worried a lot. Also, I'm wondering if samsung will ever even fix the GPS. Its been months and no official word yet. You read all these posts in here "samsung is aware and are workign on it." But who has said this in an official capacity, I dont want to hear opinions.
Whats stopping ROM chefs? The lack of open source info on the phone. Samsung has not released any of the driver info that is necessary to make custom ROM's. Until that happens or someone inside samsung leaks its, no custom ROM's.
There are already Captivate units in testing with FroYo and have been before release. Unfortunately, I doubt AT&T will be in any rush to approve it...
When I first got the Captivate, I thought it would be tough going back, but I haven't really missed anything. The Captivate Exchange client supports calendar sync (a big issue with my Android 2.1 Nexus One), the browser is fast enough for my needs and I really haven't noticed any slowdowns that the new JIT JVM would have helped much. The only things I really miss at all are the upgraded market app and Flash 10.1. Even those aren't that critical.

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

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.

ICS for Captivate Glide but not the Captivate

Saw this today:
android 4.0 now available to htc vivid™ customers
AT&T the First U.S. Carrier to Issue Latest Android Version via Upgrade
Update Includes Beats By Dr. Dre Audio™ and Updated HTC Sense™ Experience
Android Upgrades for Several AT&T Devices to Follow
DALLAS, March 22, 2012 – AT&T* today announced the availability of Android 4.0 (Ice Cream Sandwich) for HTC Vivid™ customers. After installing the software update, customers can now enjoy the optimized audio experience of Beats by Dr. Dre Audio™ and new and improved HTC Sense™ experience. Information about these features and more can be found at http://www.att.com/vividupdate. HTC Vivid™ will be the first U.S. smartphone to receive Ice Cream Sandwich as an update and the first to be issued by a wireless carrier. It will be followed by several other AT&T devices in the coming months:
LG Nitro
Motorola ATRIX 2
Motorola ATRIX 4G
Pantech Burst
Pantech Element
Samsung Captivate Glide
Samsung Galaxy Note
Samsung Galaxy S II
Samsung Galaxy S II Skyrocket
Samsung Galaxy Tab 8.9
Focused on bringing the power of Android to the surface, Android 4.0 makes common actions more visible and lets you navigate with simple, intuitive gestures. Refined animations and feedback throughout the system make interactions engaging and interesting. An entirely new typeface optimized for high-resolution screens improves readability and brings a polished, modern feel to the user interface.
Click to expand...
Click to collapse
I thought it was a little strange that the Glide is getting some Official ICS love but not the original Captivate.
Get used to disappointment!
Get used to disappointment!
Well it is a much newer device, you have to remember that too... Sadly AT&T sucks all around at getting updates to Android devices. I love how Apple gets to throw an update the IPhone all the time though.... makes real since, doesn't it???
Yep. Apple has a strangle hold on the carriers. Maybe as Samsung grows that can start pushing back again the carriers. I know its implausible but we all have to have a dream.
Also the iPhone has no bloatware.
Exactly because Apple specified that Att was not allowed to add bloatware
Sent from my SAMSUNG-SGH-I897 using XDA
captivate glide has its own forum area. post there.
http://forum.xda-developers.com/forumdisplay.php?f=1487
There is nothing wrong with the discussion of the Glide here in the context that it's being discussed. I'll leave it open unless I see confusion.
Thank you. This was more a discussion about the Glide getting the official nod and not the original cappy. Just curious since I never got my hands on a glide or read much about one. Is the hardware that much different?
Red_81 said:
Thank you. This was more a discussion about the Glide getting the official nod and not the original cappy. Just curious since I never got my hands on a glide or read much about one. Is the hardware that much different?
Click to expand...
Click to collapse
I adjusted the thread title to make it more appropriate for this subforum.
Red_81 said:
Thank you. This was more a discussion about the Glide getting the official nod and not the original cappy. Just curious since I never got my hands on a glide or read much about one. Is the hardware that much different?
Click to expand...
Click to collapse
Its a completely different phone... The keyboard alone makes a HUGE difference in the kernel.
Not to mention, it has a dual core tegra2 processor and double the ram.
Again.... completely different phone.
Based on what the CM9 Devs have said, our phone does not have the internal storage for ICS and TouchWiz. They had to resize the partitions to make room for ICS alone. This is also why there was talk of the "value package" thing.
Remember that unless it's a nexus, you will be getting some "flavored" version of android. It's also not unreasonable for manufacturers to do this, if they didn't then selling phones would be a purely hardware battle of who can push out the best spects. For us at xda it does not matter as much. Yet even for us going from our typical Samsung based ROMs to asop ICS there are features we had to get used to not having. For the general populous the "flavors" of android are a major factor to consider.
These flavors and the fact that apple does not have them is what allows for their "better" update record.
Also I would not be so quick to bash the carriers, there have been times when the manufacturer gave up on a phone but the carrier still pushed out updates.
But really, just accept that the phone is close to 2 years old, honeycomb was only a myth back then, and much of the visuals of 3.0 were not expected to ever come to phones. ICS is just that much of a change, so it's time to move on.
leaked from my ICS- FUSED SGS I897 contaminating you via XDA app.
Keep in mind that the Glide has a dual core processor, so that gives them an excuse to make it for the glide but not our lovely captivate
Thank you all for the additional information. Work has been hectic and I haven't gotten the chance to do as much reading lately. Now I feel like I'm somewhat caught up.
And I hope to see other "Captivate something" phones on AT&T. These folks will then come to us for help.

[Q] AOSP for Verizon s4?

Hey guys, I know it hasn't shipped out yet but I am thinking about getting the Samsung Galaxy s4 on Verizon and am wondering if anyone knows whether or not there will be an AOSP ROM for it. I currently have the Galaxy Nexus, and before that i had the first Droid so Touchwiz scares me! I have read a lot about there being so many different versions that the custom ROMs for this device might be lacking and now with the pure android version being released by Google it makes me even more worried that the Verizon folks are going to get left out of the pure Android experience on the Galaxy S4 - if that is the case I might have to pony up for the Note 2.
Even if its speculation I would love to hear your thoughts and I apologize if this has been addressed (I searched, I swear) or if I'm putting this in the wrong section

Categories

Resources