I think I've read that the biggest problem with CM7 on the captivate is the kernel. If samsung releases the 2.2 source for the captivate will that aid in bringing 2.3 due to the fact that its not that big of an upgrade? Or is it a dumb question and too soon to tell?
Sent from my SAMSUNG-SGH-I897 using XDA App
No... and the issue is drivers.
Also, we already have the 2.2 source for the Captivate. We have the Rogers JL1 source.
just we must go right way: not try to build from scratch, but build kernel over 2.2 source to make 2.3 run on it! that's the way froyo was brought to Samsung Spica! look @ samdroid.net
Related
Forgive me if this is a completely stupid question, since we're able to hack/root/whatever the nook color, why can't we install the latest android OS on it?
Check the dev thread. They are already booting an alpha version of froyo.
Sent from my SAMSUNG-SGH-I897 using XDA App
The latest is Gingerbread (2.3), not Froyo (2.2). The problem is that it is only officially released as source and the Nexus S. There's little developed driver support yet. As more official and user developed Gingerbread builds get released, there's a lot more to work with.
I think it's cool that they are working with Froyo, rather than Eclair though!
Hey guys I have searched and searched for a plain vanilla android rom for the captivate an can't find one. Can someone help me out? Thanks
Sent from my SAMSUNG-SGH-I897 using XDA App
It doesn't exist.
Yet.
Check the Gingerbread thread in the i9000 forum. Once it's up and running fully, then it'll be a hop, skip, and a jump from Captivates. As is it already runs beautifully. They just need to nail down the stability and Camera/Network/GPS.
http://forum.xda-developers.com/showthread.php?t=877800
A few people tried to do a vanilla 2.1 when the cappy was released but it didn't really get far.
Sent from my GT-I9000
The closest you'll get to a stock rom is the gingerbread rom in dev right now
The Gingerbread ROM is from the Nexus S, so it will be as vanilla as it gets.
Sent from my Samsung Captivate using XDA App
Samsung has never released Source - so no way to do a Vanilla ROM.
BUT.. like the above posters have said there is the Source for the Nexus S and they are making great headway... it will be the closest we get to a "Vanilla" ROM for our phones.
Hello everyone,
I was just curious how all these gingerbread ROMs for the Captivate are being released, and Cyanogen 2.3 for the Capitivate, having been worked on for months, is still only in pre-beta. I am not trying to be impatient, I know the devs are working hard to get cyanogen out ASAP, I was just curious why this was.
Thank you.
rcllcr said:
Hello everyone,
I was just curious how all these gingerbread ROMs for the Captivate are being released, and Cyanogen 2.3 for the Capitivate, having been worked on for months, is still only in pre-beta. I am not trying to be impatient, I know the devs are working hard to get cyanogen out ASAP, I was just curious why this was.
Thank you.
Click to expand...
Click to collapse
simply put CM7 is being written and developed from "scratch" and the jvb jvh roms are ported.
Not to mention that the CM7 for captivate is running 2.3.4 so technically "we're" behind CM7
betadan said:
Not to mention that the CM7 for captivate is running 2.3.4 so technically "we're" behind CM7
Click to expand...
Click to collapse
Not for long Most of the Devs are already working on JVH
AOSP is the way to go in the long run as more Samsung drivers get ported over. 2.4.x will probably never be ported to the Galaxy S phones by Samsung, but unless there are major kernel changes, upgrading CyanogenMod to 2.4 will happen relatively quickly.
nkrick said:
AOSP is the way to go in the long run as more Samsung drivers get ported over. 2.4.x will probably never be ported to the Galaxy S phones by Samsung, but unless there are major kernel changes, upgrading CyanogenMod to 2.4 will happen relatively quickly.
Click to expand...
Click to collapse
I see, so once it is caught up with the other cyanogen supported phones, it will be on the same update cycle, and therefore be more sustainable when it comes to new releases of android?
Frankly cm7 is actually being developed, where as the other ginger bread releases are being cooked/tweaked. Samsung did 80% of the work then xcal kicked in the next 15%.
So to answer your question, the reason it is "behind" is because they are not using a pre optimized build, and they are developing from the ground up.
Sent from my SGH-I897 using XDA Premium App
Hello there, I'm just wondering how long does it take to make a custom ROM? Say for example you make a ROM from the captivate GB sources vs the ICS sources that were just released? I don't mean to be one of those annoying people asking about when an ICS ROM is coming, I'm just curious as to the process of it all :-D
Sent from my Rogers i896 running CM7!
Using ICS current sources can take a while - 2 or 3 months to build a proper ROM that will work with the Captivate since the ICS source is not geared toward it. The kernal build is mostly likely going to be the biggest pain.
Using 2.2 or 2.3 Captivate sources build a proper Rom can take minutes to a few days depend on what you want out of your rom.
dohboy15 said:
Hello there, I'm just wondering how long does it take to make a custom ROM? Say for example you make a ROM from the captivate GB sources vs the ICS sources that were just released? I don't mean to be one of those annoying people asking about when an ICS ROM is coming, I'm just curious as to the process of it all :-D
Click to expand...
Click to collapse
Be patient my friend. The CM team will have a CM9 nightly before you know it.
Sent from my SAMSUNG-SGH-I897 using XDA App
I though HP released all source?
Sent from my Galaxy Nexus using xda premium
I believe the one they released was for Gingerbread or Honeycomb, not ICS. The kernel in ICS is basically being built from scratch.
The mysterious Touchpads that shipped with Android had Froyo on them and I believe everything wasn't even working on Froyo. I'm guessing Android was chosen as a test OS. By the time HP released the source work was being done on CM9 so Froyo source wasn't really helpful.