When it comes to CyanogenMod, Samsung Galaxy S owners have been mostly left in the dark. Fortunately, those days may be coming to end. Some very dedicated developers over at XDA have been hard at work and have gotten a semi-working port of CyanogenMod 7 (that's Gingerbread) up and running on the Samsung Fascinate. Trust us when we say it's still a work in progress, but progress is being made nonetheless.
There are still a lot of things not working properly. Lights, camera, Bluetooth, most of the sensors, GPS, WiFi, MMS and a lot of the hardware are not functional yet, so this is probably not something you'll want to be using other than for test purposes. So, if you're daring, hit up the source link for the full download. [XDA Developers]
I love it that there will be more custom rom's availalbe in the future... however, for now, I am totally happy with my Darky Rom on my SGS :) Works like a charm and I've never seen anything faster!
What a fantastic time for me to be coming into the Fascinate world. Coming from an OG Droid, I was worried about having to give up Gingerbread, but it looks like there's still a possibility for a fully functioning version in the future.
Its things like this that make me wonder who the f*ck samsung hired to code there updates.
You can follow punkkaos on twitter for constant status updates on this port. He works quick, so hopefully we'll have most of the hardware functional soon.
There is also a MIUI port in the works you can flash. Also still in alpha.
Does that mean Stock (vanilla) android for SGS is possible by using cyanogenmod?
I still don't get the delay behind this. How can all the devs at XDA whip out one flavor or another with minor issues but the fine folks at Cyanogen can't get anything worth running on any of the Galaxys? Is it feature creep? Is this platfor just that hard to code against? Just askin...
Get the best of Android Central in in your inbox, every day!
Thank you for signing up to Android Central. You will receive a verification email shortly.
There was a problem. Please refresh the page and try again.