• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

All Things Froyo

>>> Have you considered Assonance?

Yes, I have. It was this post on 12/14 from CrimsonPride that made the difference:

"Ive made my way around the roms, cognition, perception, tried assonance for 2 days. i moved back to cog today. i liked assonance, seemed to have a little custom touch but it was nice, until my phone random shutdown this morning and i nearly missed a final. i have had 0 shutdowns owning my phone and i wasnt ready for that, so as soon as i got home i moved back to what has been the most stable to me and that is cog."

>>> Let me know when you do it and report on how it goes!

Will do.
 
The only thing I know for sure is the more time passes, the more I want to distance myself from relying on Samsung for anything. They're so far removed from their customers as to almost create an us vs. them mentality. So, other than the technical aspects of entertaining a custom ROM, it's become a matter of principle.

I couldn't agree with this more. I love my phone, but I don't think I will ever buy another Samsung phone. I read horror stories about some of their previous phones and updates, but I figured this was their "flagship phone" so things would be different. Obviously not.

The fact that I can rely on developers not associated with samsung is great. But I shouldn't have to. I do not want to be in this position with my phone again.

I had 3 iphones before this phone. I am a happy android user right now. But I would like to see the same kind of customer support/respect with my Android phone. Hopefully LG or HTC or Motorola will provide me with that respect in the future.
 
Have you considered Assonance? I haven't followed Cog because I kept seeing people with issues - then again, it may be so popular that there would be a wider base to read about problems (most seem to be self-induced). Let me know when you do it and report on how it goes!

I have used many of the Cog and Perception versions. I had zero problems with the Cog Roms and from what I have read, it does seem that many of the problems were user induced.

Even now, if you read the perception thread, so many people are making the same mistakes over and over and blaming it on the ROM. I think user error, mistakenly reported as bugs, causes a lot of people to stay away from custom roms. I am not saying that any of them are perfect, but neither i stock eclair with touchwiz lol.
 
If they only communicated with us. That would significantly dilute negative vibes.

Froyo. When?
Delayed? No problem. 'Til when? Why?

Gingerbread. Yes or no?
If yes, when? (within one quarter)

And so on.

Yes, Jack Nicholson, I can handle the truth.
 
Good to know, guys. I'll poke into the Cognition thread over on XDA and familiarize myself with that one, too. I am intrigued by the January mentions, with the holidays and all, I'll probably wait until then to do anything.
 
Good to know, guys. I'll poke into the Cognition thread over on XDA and familiarize myself with that one, too. I am intrigued by the January mentions, with the holidays and all, I'll probably wait until then to do anything.

A quick FYI. Some folks have been less than happy with 2.3b7 and have reverted to the more satisfactory 2.3b6.
 
Also, the latest tweets from Samsung say that they are "collaborating with the carrier to ensure quality of release".

So hopefully, soon.
 
It really is amazing at this point that there is no official word. Other Galaxy S phones already have froyo. What is the problem with getting out an updated status report for US users?

At the same time, earlier this week I read a few posts by designgears over on xda regarding gingerbread. He apparently has a source that said samsung was going to sip froyo for the US and go right to gingerbread sometime in January or February.

I have no idea if this is true or not. It could account for all of the secrecy about froyo coming to our phones. Obviously this is a very optomistic view.

Regardles, we KNOW that our phones can support gingerbread. We have very similar specs to the nexus S. How hard would it be for samsung to say we are getting gingerbread?

My fear deep down is that the Captivate is not getting gingerbread at all. Maybe samsung is keeping quiet in order to sell as many galaxy s phones as possible. If they came out and said we are not getting gingerbread, what semi-knowledgeable user would buy the phone?

Hopefully the nexus s is close enough to the captivate to allow for custom roms.
 
A quick FYI. Some folks have been less than happy with 2.3b7 and have reverted to the more satisfactory 2.3b6.

I think that had to do with the over clocking. I don't remember if 2.3b6 had over clocking or not. But I saw the same thing about 2.3b7.
 
He makes it sound like rooting is a threat and this is on Google to fix.

I didn't take that from the article, although I read it pretty quickly. It sounded to me like the carriers consider rooting a threat and they are trying to either get google to fix before the carriers will agree to bring it to their phones, or they are trying to fix themselves.

Both oclf and z4root have been removed from the market last I checked. Seems possible that was due to pressure from the carriers to make the phones more difficult to root.

Edit: I am so bad at quoting lol
 
I didn't take that from the article, although I read it pretty quickly. It sounded to me like the carriers consider rooting a threat and they are trying to either get google to fix before the carriers will agree to bring it to their phones, or they are trying to fix themselves.

Both oclf and z4root have been removed from the market last I checked. Seems possible that was due to pressure from the carriers to make the phones more difficult to root.

Yeap - I hear you.

Here's the threat of rooting:
  • You can remove carrier-inspired bloatware
  • You can remove the "product differentiating" look and feel and replace it with something rational that you like
  • You can wirelessly tether

Of the three - why do you think they're locking down the handsets in the first place?

Hint - the carrier is not requiring the Nexus S to be boot-loader locked, the Nexus is easy to root, and the carrier is not calling that out as an unacceptable security hole to Google.
 
Sign that US galaxy S phones might get Froyo before Christmas... I have seen several tweets by Samsung now that point that way:

GalaxySsupport: @Clonetrooper12 Hi Clonetrooper, thanks for reaching out! Froyo would sure be nice to have under the Christmas tree, however, ^Sab
Original Tweet: Twitter / Galaxy S support: @Clonetrooper12 Hi Clonetr ...

Froyo would be nice. That doesn't mean Froyo will arrive before then. I can just imagine...2 days before my contract expires AT&T will finally release froyo for the captivate. Too bad I'll be buying a nexus three running android 4.x "JavaJuice" (Or something to that effect) by then :cool:
 
Maybe it's me..but it seems like many folks who flash a custom 2.2 rom seem to have a need to post how cool it is..like they are justifying their decision to move from stock..I could be wrong..but ifrett in post #175 put it quite well. The Captivate is an excellent device out of the box.

@segfault, post 181: Pls explain why google maps 5.0 is "gimped without Froyo"?

Wow, this thread moves fast. Google maps 5.0 uses multi-touch to orient the map. You use two fingers to move from a straight up and down view to viewing at angle which makes the 3d building view useful. You also use two fingers to rotate the map on the screen. From what I understand you need Froyo to this at all. With eclair you can just navigate around the map just like on earlier versions of google maps.

Its from here:
Touchscreen Gestures Supported Devices - Google Mobile Help

Rotating gestures require Android OS 2.2 or later.

They added that note later because of all the fully supported phones, the Galaxy S is the only one stuck on eclair.
 
So there are two articles on the front page right now. One of them comments on how the Froyo release for the Vibrant has been pulled due to technical issue. One of them is about how HTC has released Froyo for the Aria in SE Asia.

Anyone want to wager on whether the AT&T Aria gets Froyo before the Captivate?
 
Also, the latest tweets from Samsung say that they are "collaborating with the carrier to ensure quality of release".

So hopefully, soon.

Yea, I keep up the with GalaxySSupport Twitter account. It's interesting at the transition. A couple weeks ago they were like "by the end of the year, by the end of the year!!". Now its "collaborating with the carrier to ensure quality of release". I don't think it'll be out officially in 2010 on all four carriers. :o
 
Yeap - I hear you.


Here's the threat of rooting:
  • You can remove carrier-inspired bloatware
  • You can remove the "product differentiating" look and feel and replace it with something rational that you like
  • You can wirelessly tether
Of the three - why do you think they're locking down the handsets in the first place?

Hint - the carrier is not requiring the Nexus S to be boot-loader locked, the Nexus is easy to root, and the carrier is not calling that out as an unacceptable security hole to Google.

I was just checking out the market and OCLF is back. BUT...it no longer roots your phone. You have to be rooted already to use OCLF. It definitely appears google is making a concerted effort to make it more difficult to root in order to appease the carriers.
 
Back
Top Bottom