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

***Official Samsung Fascinate 2.2 Speculation Thread***

Status
Not open for further replies.
If this rumored ROM being worked on by independent devs comes out before the official release, will those who use it be able to be updated to the official 2.2 when it emerges? I'm sure the official release would (or should) be more stable with all the months Samsung has had. (Right?)
 
If this rumored ROM being worked on by independent devs comes out before the official release, will those who use it be able to be updated to the official 2.2 when it emerges? I'm sure the official release would (or should) be more stable with all the months Samsung has had. (Right?)

It could be more stable. But if anyone wants the official update then they can just flash back to stock DL09 and then update from there. That's what we all did for DL09 when it came out.
 
If this rumored ROM being worked on by independent devs comes out before the official release, will those who use it be able to be updated to the official 2.2 when it emerges? I'm sure the official release would (or should) be more stable with all the months Samsung has had. (Right?)

Wrong. Taking an ota is taking a chance I don't care how long sammy and V have their hands on it, there are always still the chance of bugs. The devs actually care about what they are doing ;)
 
If this rumored ROM being worked on by independent devs comes out before the official release, will those who use it be able to be updated to the official 2.2 when it emerges? I'm sure the official release would (or should) be more stable with all the months Samsung has had. (Right?)
You have this exactly backwards.

Going root and custom ROM is *more* stable -- as we saw with DL09, our devs put out not only an earlier and unbloated package, but one that didn't bork SD card mounting. And you don't end up having to wait because somebody will always upload a deodexed OTA before or the day of any actual update.

You see it every time: poor sods jumping through hoops to put themselves back to stock to get an "official" version of a ROM that you could Clockwork in with more security. And *every time* you get some folks getting bricked (or semi-bricked, because people this happens to don't generally know about assembling a jig) because of whatever magic sauce was in the exact same update coming from Verizon, or T-Mo, or Rogers instead of xda.
 
You have this exactly backwards.

Going root and custom ROM is *more* stable -- as we saw with DL09, our devs put out not only an earlier and unbloated package, but one that didn't bork SD card mounting. And you don't end up having to wait because somebody will always upload a deodexed OTA before or the day of any actual update.

You see it every time: poor sods jumping through hoops to put themselves back to stock to get an "official" version of a ROM that you could Clockwork in with more security. And *every time* you get some folks getting bricked (or semi-bricked, because people this happens to don't generally know about assembling a jig) because of whatever magic sauce was in the exact same update coming from Verizon, or T-Mo, or Rogers instead of xda.

yeah, unless you have to...i dont really see the point in unrooting or removing cwr or whatever and going back to stock for an inferior ota....never made sense to me :o
 
You have this exactly backwards.

Going root and custom ROM is *more* stable -- as we saw with DL09, our devs put out not only an earlier and unbloated package, but one that didn't bork SD card mounting. And you don't end up having to wait because somebody will always upload a deodexed OTA before or the day of any actual update.

You see it every time: poor sods jumping through hoops to put themselves back to stock to get an "official" version of a ROM that you could Clockwork in with more security. And *every time* you get some folks getting bricked (or semi-bricked, because people this happens to don't generally know about assembling a jig) because of whatever magic sauce was in the exact same update coming from Verizon, or T-Mo, or Rogers instead of xda.
Good post and I very much agree. I'll take xda devs everyday of the week and twice on Sunday
 
I was on Facebook and im a fan on the SGS line and they always post news etc about US SGS well apparntly 2.2 for the Fascinate was leaked and is in the hands of Punkkaos whose a hacker. I hope this is great news the release is near or at least there working on it.!!:D
 
I was on Facebook and im a fan on the SGS line and they always post news etc about US SGS well apparntly 2.2 for the Fascinate was leaked and is in the hands of Punkkaos whose a hacker. I hope this is great news the release is near or at least there working on it.!!:D
Yeah its real and yeah they have been working on it since before this made news yesterday. Both Kaos and jt have alpha ROM builds based off .29 kernel. This leak, which we also learned was one of many can and will only help
 
I just realized that TW (Samsung) 2.2 won't have BLN or Voodoo Sound for months, until source is released.

Need... CM6/7... nao...
 
I just realized that TW (Samsung) 2.2 won't have BLN or Voodoo Sound for months, until source is released.

Need... CM6/7... nao...

depends how quick samsung releases source...worst case i think the mesmorize is scheduled for early march...and sammy lately has released source quickly...dl09 source was up a week after ota i believe

so we ll see
 
On twitter punkkaos said the leak doesn't really matter because cm6 > touchwiz.

again thats all about preference...on other phones many still choose oem-skin based roms over aosp

plus you still need source to really work with kernels...its very possible that voodoo support cant be enabled for the kernel leak without samsung releasing .32 kernel source...i mean its not impossible...but much tougher anyway
 
Well there wasnt an existing thread on this as well and I didnt wanna make one this prematurely but. Exciting times in the land of 2.2 and the SF. As we know there are pre-existing alpha ROMs for CM6 and AOSP, there is the TW 2.2 leak and MIUI is booting now by its dev-porter. None of the above is of course dialed in correctly, as kernel source is still missing. However, 4 flavors of 2.2 will surely give something for everyone.
 
I just updated my Dad's Vibrant to 2.2. It runs very smooth. Vib folks are reporting better battery life too. Flash works great as it should and such. It'll be nice on the SF.
 
I just updated my Dad's Vibrant to 2.2. It runs very smooth. Vib folks are reporting better battery life too. Flash works great as it should and such. It'll be nice on the SF.
I will say this for my experience thus far. It seems stock TW 2.2 is a lateral move from a fully tweaked out 2.1 experience. So Im a tad underwhelmed frankly but this was a tad expected. Speaking as a voodoo user I very much am noticing the difference being voodoo free for the 1st time in many many weeks. Anyone on stock TW 2.1 will surely notice a difference on stock TW 2.2. But for those dialed in on 2.1 we'll need custom kernels to give us a more noticeable upgrade feel
 
We need multi exchange support. I don't think any amount of tweaking is going to get that on 2.1 configuring a second account in touchdown is the only thing close.
 
307ynlv.jpg


All of those poor kittens....
 
Man, I wish some more Froyo ROMs for this phone would hit, or dare I say, an OTA update. The kernel I'm on now has developed a sluggish accelerometer (strangely not in games, just in apps that flip the screen.) And alarms don't work. Clearing the caches including the davlik, doesn't seem to do any good either. Calls, texts, camera, apps, etc, all work fine, just not alarms. It's unfortunately kind of inconvenient, and even a little alarming. (hehehe, couldn't help it.)

Anyways. If I'm going to wipe and throw something new on there, it would be nice for some froyo action....

This thread is ridiculously long, and has been around for a ridiculously long time. February tomorrow and still no 2.2. T-Mobile has it. European models have it. The frakking Nexus S has 2.3 (same screen and CPU and a lot of other stuff...) This is beyond ridiculous.

Edit: Just for kicks and some lovely nostalgia I had to go back and dig up this old article:

http://www.cnet.com/8301-19736_1-20016105-251.html

Almost six months running an OUT OF DATE OS on the most powerful phone you can get.
 
I'm so pissed off at both Samsung and Verizon. Samsung for imposing their idiotically unnecessary TouchWiz that is almost certainly holding up the show and Verizon for locking me out of my phone's settings so I'm forbidden to delete three screens of deactivated trial apps and use BING to search.

Here's my philosophy on phones, or really any piece of hardware I own: I paid for the phone, it's MY phone which belongs to me because I purchased it, therefore I want to run whatever software I please on it and how dare anyone suggest that I can't!

I've gotten my phone rooted and installed ROM manager, but there are no instructions anywhere on how to get ClockWorkMod running with a Mac (all instructions are for Windows, and they involve downloading drivers and a bunch of crap that I don't want to partition my Mac and dual-boot in order to fail at). ClockWorkMod has a built-in option specifically for Fascinate but as far as I can tell it simply doesn't work. Since the day I purchased this phone until now I have encountered nothing but frustration at how inadequate Google's management of its ecosystem has been. Google should force carriers and manufacturers to meet certain deadlines for their users when it comes to releasing updates or else revoke their licenses. I think that'd clear up the custom UI/crapware issue pretty neatly.
 
Will the DX get Gingerbread before the SF gets its FroYo? Sadly, it's entirely possible/likely.
Nope. Not officially or unofficially. I mean some peeps already have unofficial froyo on the SF. The OTA will be out in Feb no DX OTA for GB in Feb at least.
 
Status
Not open for further replies.
Back
Top Bottom