I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Need 2.2 source code...
2.1 is a dead horse--why bother when 2.2/2.3 are out?
The reason to bother is to at least get AOSP running. Once its on 2.1, it'll be easier to get 2.2 AOSP running on it. But claiming 2.1 is a "dead horse" is the wrong path ... the real question still stands: after 9 months on the market their still are no AOSP ROMs.
MIUI
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
sarim.ali said:
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Click to expand...
Click to collapse
Except, the 2.2 source for the Vibrant has not been released. The SGH-T959D that shows Froyo sources on Samsung's site is for the Canadian Fascinate, not the US T-Mobile Vibrant. Samsung has yet to release the 2.2 sources.
oka1 said:
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
Click to expand...
Click to collapse
Except the so-called "custom ROMs" are just modifications on the stock theme, a replacement kernel and a change of some of the supplied applications.
There is nothing close to a full "custom ROM" such as CyanogenMod or MIUI because we don't have Samsung's sources. What is passing for a "custom ROM" for the Vibrant are just repackaged files. It is akin to the "ROM cooking" that took place for the WinMo phones, not a truly ground-up build from source that is possible with Android.
EDT/Devs4Android has the MIUI build. From Source.
TW has a 2.2.1 in testing.
EDT has a 2.2.1 Beta released.
TW has a 2.3 AOSP in testing. From Source.
EDT has 2.2 AOSP in testing. From Source.
What you want is out there for you.
Watch the forums and reply when a call for Alpha testers is posted.
Hopefully it won't be long before you see a full TW/EDT/Devs4Android collaboration!
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
mattb3 said:
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
Click to expand...
Click to collapse
Yes, this is more towards what I was getting at. We do not have Samsung's kernel sources for 2.2. And, we do not have a Samsung provided vendor overlay.
When we receive these two pieces, then a true AOSP build will be possible. However, we do have the 2.1 kernel sources, so why wasn't a true AOSP build possible then? What was missing, and can we actually expect Samsung to release the overlay that's needed?
Actually, that's true. I know it was old but why didn't anyone build a 2.1 cyanogen or aosp rom? (Not to say its easy.)
Sent from my SGH-T959 using XDA App
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Where have you been?
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
For probably the same reason that many phones with non AOSP firmware running 1.5/1.6 did not bother with AOSP 1.5/1.6 when they were released around the time 2.1 source hit. Why bother developing at all for what is essentially an "out of date" OS.
The only people it seems who actively continue to develop for existing (as opposed to new) firmware are manufacturers and carriers. This stupidity should be left to the manufacturers who still do this.
One of the larger snags way back then (sits in his rocking chair on the porch) was a lack of understanding of the phones proprietary aspects and how to work around them. But we have a fairly clear understanding of Samsung's boot process now, and RFS can now easily be turned into a distant memory.
I would wager a guess that the apathy towards 2.1 will not repeat itself once we have 2.2 source widely available and the low level similarities between 2.2 and 2.3 should have Gingerbread being more than the experiment it currently is. It's been barely more than a week since Eugene's little present manifested and there are already proper and stable kernels available.
Keep in mind that the devs we do have, have done a phenomenal job of cleaning up, speeding up, and drastically enhancing our existing 2.2 release. And perhaps to the point where many will not really care, though I know many would still like to see CyanogenMod6/7 properly on this phone.
Master&Slave™ said:
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
Click to expand...
Click to collapse
Um, that's not quite true. The CyanogenMod.com website lists 0 files available for download for either experimental or stable files. The CM6.1 you must be running is not a true CM build.
Also, CM is not AOSP, but rather AOSP with modifications.
phrozenflame said:
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Click to expand...
Click to collapse
The vendor overlay tells the AOSP build system which proprietary files are needed from the device that are not available in source form. This includes things like GPS and video drivers, baseband firmware for wireless radios, &c.
hi everybody !
a month age i decided to compile a new rom for my Galaxy S absolutely from AOSP source ( branch 2.2.1_r1 ) after some compile-time problem and many painful steps to resolve ,eventually the rom successfully built and can boot it up flawlessly on emulator.
i create a nandroid backup of current rom and installed the compiled one. but i am facing new problem :
1- the phone successfully boots but after short while screen began
flicking several time and the phone go in deep sleep and never wakeup
( power button or menu button does not do any thing )
2- touch screen works only for some second that I can unlock the
phone
3- there is no network available
4- I have downloaded samsung opesource package for GT-I9000. it
contains a folder named 'platform' but when i merge these files to
AOSP , the compile process stops and fails again. if there any one can
help me which files from samsung source should i merge and how ? if
you now the answer and dont have spare time then some internet link or
online document is really useful .i have no problem studding and
reading and searching . reaching to target is my only hope .
I am really disappointed why there is not a good and complete step2step tutorial to compile an AOSP rom for galaxy s (GT-I9000) !!
such docs is available for phones like dell streak , desire , dream , magic , .... . i really want to to active these aspect on XDA forum and with help of all you ( mods and masters ) try to create such tutorial that any one in world can use to refer . i think XDA is the only reference on net to collect and create such help and document. please help me and leave PM or comment to agree ot disagree and from where can i start ?!! thank in advanced .
edit :
there is a google groups post that i send my question in Android-platform . if you prefer please join this group and active that post to ask any question related to 'galaxy s compile from source ' .
post located at http://groups.google.com/group/android-platform/browse_thread/thread/da5d6f18f3bd3c9b
You guys are aware right that Erik Hardesty a.k.a. dalingrin is wokring on ICS for touchpad and has promised (citation needed) to deliver before CM9? Now, I want to know if he indeed delivers, then will his work to taken to make the CM9 build faster and then will he be included in the official CM team. I am asking this because I have a Moto Defy and before CM7, Quarx, Epsylon and others compiled it and I think they are now in the CM team. Just curious on how it works.
He is already a part of the CM team, he is the CM maintainer for the Nook Color.
That's news.. well for me! But if there is someone else in his place who is ot in the CM team then what happens?
abhi.eternal said:
That's news.. well for me! But if there is someone else in his place who is ot in the CM team then what happens?
Click to expand...
Click to collapse
Then its not a CM9 build. Basically the CM team are a bunch of developers on different devices. In the case of ICS each developer will build their versions and it will be pushed and integrated into the CM9 list when CM9 is ready to launch. However, in the case where a CM team member's build is ready to be tested before CM9 is ready then they will most likely post them as a under a different title because its not integrated as a CM9 device yet.
In the case that another developer releases an AOSP ROM into the wild then he can do whatever he wants with it and it has nothing to do with the Cyanogenmod team whatsoever.
Samsung Galaxy S Captivate ICS CM9, Glitch Kernel | HP TouchPad CM7 Xron Beta 2.9.1
@iamsamsamiam: I get your point but if that is the case then how come Quarx and Epsylon (for Motorola Defy) are in the official CM team now (I think they are [citation needed!]). If you are not aware, CM7 had no love for Defy for a very long time and that gap was filled by Quarx at first. Afterwards, when we had a almost complete working rom based on CM7, these devs were included in the official list. I just want to know is this how it happens?
abhi.eternal said:
@iamsamsamiam: I get your point but if that is the case then how come Quarx and Epsylon (for Motorola Defy) are in the official CM team now (I think they are [citation needed!]). If you are not aware, CM7 had no love for Defy for a very long time and that gap was filled by Quarx at first. Afterwards, when we had a almost complete working rom based on CM7, these devs were included in the official list. I just want to know is this how it happens?
Click to expand...
Click to collapse
And there are still a ton of devices out there without any Cyanogenmod ROM at all. I guess its more like a developer who wants to code for a particular device and wants to put a CM flavour to the ROM and gets permissions from the CM team to use it and builds a CM ROM and I guess they would become part of the team as a de facto point since they continue to support their build. Remember there are a ton of other ROM developers out there that don't use a CM base and does things their own way.
Cyanogenmod isn't always going to be the "best" ROM out there for every device, but they're trying to support many devices out there. The devices that get support are reflected upon the community and the more popular the phone the larger the community. And developers come out of said communities and maybe one of those developers wants to make it into a CM build.
Samsung Galaxy S Captivate ICS CM9, Glitch Kernel | HP TouchPad CM7 Xron Beta 2.9.1
That made sense!
Hi,
Can someone make clear to me as a noobie what are the differences between "cores" of the ROMs?
I see there are most favourite ones like "XWLP9" and "AOKP" - what are the differences between them? I see AOKP has more updates from kernel and maybe some other things in addons? Besides XWLP9 seems to me more stable but I only observe rom peoples comments and replys so can someone tell me which ROM core I should be focused on when choosing ROM? Some advices, experiences what you have with them - ADVANTAGES and DISADVANTAGES maybe or something ... I see there are roms like these two from what I want to choose:
http://forum.xda-developers.com/showthread.php?t=1436817
http://forum.xda-developers.com/showthread.php?t=1513150
Thank you for all your advices ...
Drahy said:
Hi,
Can someone make clear to me as a noobie what are the differences between "cores" of the ROMs?
I see there are most favourite ones like "XWLP9" and "AOKP" - what are the differences between them? I see AOKP has more updates from kernel and maybe some other things in addons? Besides XWLP9 seems to me more stable but I only observe rom peoples comments and replys so can someone tell me which ROM core I should be focused on when choosing ROM? Some advices, experiences what you have with them - ADVANTAGES and DISADVANTAGES maybe or something ... I see there are roms like these two from what I want to choose:
http://forum.xda-developers.com/showthread.php?t=1436817
http://forum.xda-developers.com/showthread.php?t=1513150
Thank you for all your advices ...
Click to expand...
Click to collapse
Google is your friend.
XWLP9 is the latest stock/official ROM version from Samsung for the SGS2 (GT-I9100).
So, these kind of ROMs are based on Samsung stock ROMs ... with some customizations (e.g. rooted, some removed bloatware, some custom themes/mods, etc.).
The other kind of custom ROMs have AOSP (Android open source project) or ASKP (Android open kang project).
So, they are either on pure Google Android OS or Linux. Usually there is a team of developers who share their parts/versions in binaries and as source code.
The kernel is kind of "core" of the firmware.
Every ROM contains its own kernel, as this is a basic part of the firmware ... and the phone can't work without it.
You can also flash other (custom) kernels on a ROM.
But not every kernel is compatible with every ROM.
OK thank you I read about these two a lot i needed some experienced opinion and clearing it up for me.
What I basically needed was opinions about these two versions from experienced users. If non oficial and trully open made ROM is better and in what ways or is it better to stay on oficial ones etc. This is what i wanted most from this thread ...
I am planning to buy a Nexus 5 (my first android/smartphone) and root it. I have some question...
Which ROM is good if I want to avoid Google services? (don't need to sync contacts/calendar/call records)
AOSP is, I guess, the pure ROM which everybody later modifies to add features. I am looking for a ROM closest to AOSP (or even AOSP for Nexus 5) KitKat 4.4.4.
Also, I looked at Paranoid Android ROMs and the size of them is ~170MB. Is Android OS this small in size? Because I have heard iOS 7+ is 1GB+. Or is there something more to it, which is not Open Source?
Thank you kindly.
Hello, I should be buying a Swift 2 Plus soon, and as a complete noob, I don't know what the death of Cyanogen is going to do to my device. Obviously it won't instantly brick it, but how am I gonna get future Android updates without installing a custom rom?
have a sexy christmas
Please, read my post here, and the (unconfirmed) Wileyfox's response to Cyanogen move here. It should be enough to clear your doubts
linuxct said:
Please, read my post here, and the (unconfirmed) Wileyfox's response to Cyanogen move here. It should be enough to clear your doubts
Click to expand...
Click to collapse
One thing relating more to the custom ROM area. So some of the CM team (not COS) are rebranding as lineage OS right. And they are continuing off the codebase of CM however we don't have a build of CM so how will and developer , from lineage or anywhere else, build a custom ROM without code from CM or AOSP. Unless Cyanogen Inc release the source code for our phone which I'm not sure they will. (Sorry if this is a noob question)
person123321 said:
One thing relating more to the custom ROM area. So some of the CM team (not COS) are rebranding as lineage OS right. And they are continuing off the codebase of CM however we don't have a build of CM so how will and developer , from lineage or anywhere else, build a custom ROM without code from CM or AOSP. Unless Cyanogen Inc release the source code for our phone which I'm not sure they will. (Sorry if this is a noob question)
Click to expand...
Click to collapse
You're absolutely correct. We can't start with the development with no sources. However, I don't think Cyanogen would do that at the moment, and, after seeing Wileyfox's response to Cyanogen moves, I think (and actually hope) they'll switch to an AOSP-based ROM with Android N 7.0 upgrade, and if that happens I'm really sure they'll have no problem on releasing the source code (remember Wileyfox devices tend to be quite developer-friendly). From that, we can work on bringing Lineage...