11 replies to this topic

[FRLinux]

Hey guys,

First congrats to all the dev on to getting CM7 final out, nice to see many sites talking about it. I was wondering what is the plan and what's required to get CM7 officially supported on Samsung Galaxy S?

Thanks!
Steph

[Bad.boY]

I also really want to know what's preventing from the dev team to open this MOD officialy for the Galaxy s i9000 devices?
thanks.

[darkblue80]

me too

[GeekAndProud]

Too many things need fixing(take a quick look at http://code.google.c...xys/issues/list) before it can be considered as stable as other rom manufacturers releases. I think part of the reason for the time it has taken is Samsung's advanced methods regarding bootloaders etc.

Edited by GeekAndProud, 11 April 2011 - 02:21 PM.

[zsyjx32]

FRLinux, on 11 April 2011 - 11:17 AM, said:

Hey guys,

First congrats to all the dev on to getting CM7 final out, nice to see many sites talking about it. I was wondering what is the plan and what's required to get CM7 officially supported on Samsung Galaxy S?

Thanks!
Steph

I THINK IT IS BECAUSE SAMSUNG DONESN'T RELASE THE DRIVER AND THE SOURCE.SO CM ROM FIND DIFFICULTIES.

[Mitiko78]

To me, they will not succeed! then you do! Will be 3 months working there and there are more and more problems ... bah!

Edited by Mitiko78, 11 April 2011 - 02:31 PM.

[Darkstriker]

GeekAndProud, on 11 April 2011 - 02:18 PM, said:

Too many things need fixing(take a quick look at http://code.google.c...xys/issues/list) before it can be considered as stable as other rom manufacturers releases. I think part of the reason for the time it has taken is Samsung's advanced methods regarding bootloaders etc.

The bootloaders aren't much of an issue. First of all because they aren't more locked than HTCs on say the Hero (because actually, HTC has started to heavily lock down their bootloaders). The problem lies in part with the lack of some driver sources (which is also the case for some parts of HTC phones) and else in the fact that a lot of CM code is designed specifically for HTCs and not (as so many people believe) to be fully compatible with all open standards.
Best illustration of that is the issue of integrating supercurio's sound improvements. He and the maintainers of the I9000 mod tweeted about this.
And even tough CM7 may be out for the Nexus S i can bet you that it has more issues than say the G2 despite the sources for the NS being more complete than those from the G2.

[mikebeecham]

Mitiko78, on 11 April 2011 - 02:29 PM, said:

To me, they will not succeed! then you do! Will be 3 months working there and there are more and more problems ... bah!

You will find that the CMSGS team are working very hard to bring a full working CM7 asap. Yes, there are some problems with the rom at the moment, but if you take the time to install it on your phone then you will see that it is already at the "day to day" stage. Some things dont work yet, but will only be a matter of time.

[Mitiko78]

mikebeecham, on 11 April 2011 - 02:54 PM, said:

You will find that the CMSGS team are working very hard to bring a full working CM7 asap. Yes, there are some problems with the rom at the moment, but if you take the time to install it on your phone then you will see that it is already at the "day to day" stage. Some things dont work yet, but will only be a matter of time.

I know eh .....

[doublerebel]

I am running the March 18th CM7 build on my Captivate and it flies.  Google Goggles force closes... and you have to pick between usb tether and usb mount of external SD.  Otherwise, I haven't run into anything that would prevent daily use -- especially in comparison to the AT&T stock ROM.  GPS gave me a lock from cold in under 10 seconds, while I was indoors.  The list of accepted bugs is rather short -- BUT CM holds themselves to a high standard and also has a giant userbase, so they are understandably cautious.

I've been into ROM dev since before the G1 arrived, so in comparison to the past CM 7 is incredibly complete and stable.  If you consider yourself comfortable with loading ROMs, and understand the tutorial, it's very easy and straightforward.  However, is it simple and noob-friendly enough to release to the masses?  Probably not.  The masses are going to want one-click USB tether and SD mounting and will probably report a bunch of bugs that don't exist, distracting from the real problems.

Please appreciate that very few manufacturers have been able to release a Gingerbread update, so CM team has accomplished quite a task.  The best thing you can do to help a release is to learn how to debug, and how to test and report, and even get your hands dirty in some code.  Reverse-engineering drivers is very time-consuming and every bit helps.

[rogue3]

doublerebel, on 11 April 2011 - 04:37 PM, said:

I am running the March 18th CM7 build on my Captivate and it flies.

Can you provide a link to the build you are using, or one that will work on a Fascinate? When I go to the mirror network to download the build, I'm not certain which one to pick. Thanks for helping a noob.

[FRLinux]

GeekAndProud, on 11 April 2011 - 02:18 PM, said:

Too many things need fixing(take a quick look at http://code.google.c...xys/issues/list) before it can be considered as stable as other rom manufacturers releases. I think part of the reason for the time it has taken is Samsung's advanced methods regarding bootloaders etc.

Yeah saw the list (actually worked on one). Device is stable enough i found. Biggest remains the battery drain which i don't have on stock roms. Appart from that CM7 really kicks ass in my view.