Database Info

[Q] ASOP Sidekick 4G ROM?

Am I the only one who is unhappy with the slim pickings of ROMs that are available for the SK4G?
Does anyone know anything about an ASOP ROM?

It's AOSP (Android Open Source Project) and you're not the only one not happy with the current SK4G options. I personally want MIUI or CM7, but seeing as we're currently stuck with Froyo, we'll have to see what the devs can cook up.
Sent from my SGH-T839 using XDA App

For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.

sduvick said:
For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.
Click to expand...
Click to collapse
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App

ayoteddy said:
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
And so anticipation had set in, i can't wait ayoteddy. im very excited. SMX was great, and SMGC was awesome, and now with this? whewwww. think i better go lay down, lol.

I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.

Thank you for joining the Sidekick 4G section , & we welcome you but if you want you could pause the game's for the ROM if anything & Question 1 is a no & Question 2 no cause they have to be compiled with the 2.3 kernel .
- Said by Sduvick
jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse

Revolution, thanks for relaying my responses.
jmpz, I tried building the source before, but was unable to build it completely, but that was possibly because of some errors with my dependencies. The kernel compiles fine from source, you just need to pull initramfs, or you can get it from Dr. Honk's github.

Thank you for your answers.
So, can anyone enumerate the list of drivers which we should extract from kernel?
I can name these:
1) Keyboard
2) Mic
3) 2 speakers
4) buttons
5) front camera
6) rear camera
7) trackpoint
8) lcd
9) digitizer
10) 3.5 jack
Please correct me and add missing
If I understanding it rightly the key problem is getting proprietary drivers from the kernel. Right?

nope, the key problem is trying to build the system entirely, without any errors, which may be easier with someone following a stock designed build environment. I don't use Ubuntu which is what has the listed dependencies for every tutorial I can find. You can get the drivers out of Dr. Honk's voodoo kernel ramdisk here: http://forum.xda-developers.com/showthread.php?t=1145139
There shouldn't be any problems if you just set up a build environment following the directions in any of the tutorials, then add the platform from the samsung source.

I'm a linuxoid - so these tutorial are for me. Thank you for the link.
By the way, drivers are in Linux Kernel, so I don't think that I need to use Samsung Platform from the source. Instead I wanna use platform from AOSP or Cyanogen. Correct me if I'm wrong.
I think that grabbing drivers from kernel source from samsung would be enough to build the rom.

jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse
I 100% support your efforts. I want Cyanogen on the SK4G badly, but I'm not sure what kind of help a non-programmer like me could do, but do have some experience with flashing phones and such, so if there is anything you need let me know.
If you do get rolling heavily on this, I'd be willing to donate monetarily to your efforts.

If anyone can get CyanogenMod 7 on the Sidekick they would definetely get a donation from me. Id be thrilled. Glad to see its going to be worked on.
Sent from my Sidekick 4G using XDA Premium App!

Jelly Bean released !!! Possible to port Nexus ROM ?

Hello respected Developers ,
Jelly Bean is released today with some new and important features. Nexus ROM is already available for download. Since Jelly Bean brings updated UI and few new features only it may be possible to port Nexus ROM.
Kindly consider its possibility and reply
Thank you all !
Here is direct download link
http://goo.im/roms/fabolous/maguro/bigxie_JRN84D_rooted_busybox_deodexed.zip
Hmm...so I was right. It can be ported.
Jelly Bean ported to HTC One X http://forum.xda-developers.com/showthread.php?t=1737736

I hope so.
I'm not a Developer, but I hope so :good:

nothing will be done until the source code is released (google said mid july)

Guys, chill. It is best we wait until ics is fully developed with the kernel 3.x before we talk about this. I am sure that this needs ICS as base. I have been researching about this jellybean update the whole day. it is somewhat a small update to the ICS with automatic widget resizing, GoogleVoice (commandable just like siri) and also less lag... this is just like a froyo to gingerbread update as they said in vid reviews.

now our future is on the 3.X kernel:good:

Hi
Did anyone noticed that kernel for jelly bean port on HTC one x.
It is 2.6.xxx
Sent from my GT-I9003 using Tapatalk

neil05 said:
@vishal
You are not the moderator in this forum. So don't act like a mod
Cheers:beer:
Click to expand...
Click to collapse
No, but I am
Thread moved and cleaned. Development section is only for roms/kernels, etc. being worked on with some kind of bootable image. This is not. (First hint was the title ends in a question mark)
Keep it polite guys.
---Jay--- From the Nexus

The porting Guide can be found here
http://forum.xda-developers.com/showthread.php?t=1739561

Thanks Jay
And apologies for posting in wrong section. Everyday we learn something new
Thanks !

Maybe...
I'm not a developer and i don't know how to port a ROM. However, I think porting an I9000 Jellybean Rom will be easier since I9000 and I9003 has similar specs.:laugh:

chung1213 said:
I'm not a developer and i don't know how to port a ROM. However, I think porting an I9000 Jellybean Rom will be easier since I9000 and I9003 has similar specs.:laugh:
Click to expand...
Click to collapse
an i9000 stock rom is impossible because samsung wont release one. and jb code is not out until mid-july. let's wait for cm10 to start
Sent from my Transformer Prime TF201 using xda app-developers app

NEXUS S got the jelleybean working
http://forum.xda-developers.com/showthread.php?t=1738756
Galaxy s are on there way to port jellybean.

Vasishta Reddy said:
NEXUS S got the jelleybean working
http://forum.xda-developers.com/showthread.php?t=1738756
Galaxy s are on there way to port jellybean.
Click to expand...
Click to collapse
i9003 will follow, once kernel 3.0 + ics is completely ported and good for day-to-day basis ^^

Everytime it happens that when we work on perticular version of cynogenmod then suddenly new version of galaxy device releases or new version of android releases then current development looks old to us. So we leave it in incomplete stage & we move forward to achieve new things of new cynogenmod but again everytime same story repeats & thats why we have so many incomplete cyanogenmod roms.
I want to suggest that if the developers are working on ICS cm9 then they must work on first to achieve kernel 3.0 & get stable cm9. People now should not rush to achieve JB leaving behing cm9 work incomplete. "One time one task"

vishal24387 said:
Everytime it happens that when we work on perticular version of cynogenmod then suddenly new version of galaxy device releases or new version of android releases then current development looks old to us. So we leave it in incomplete stage & we move forward to achieve new things of new cynogenmod but again everytime same story repeats & thats why we have so many incomplete cyanogenmod roms.
I want to suggest that if the developers are working on ICS cm9 then they must work on first to achieve kernel 3.0 & get stable cm9. People now should not rush to achieve JB leaving behing cm9 work incomplete. "One time one task"
Click to expand...
Click to collapse
K bro,why to waste time in partially working ports lets wait for source code's release .

Vasishta Reddy said:
K bro,why to waste time in partially working ports lets wait for source code's release .
Click to expand...
Click to collapse
Source code of jelly bean is of no use for us until we get kernel 3.0. Because building jelly bean rom or cm10 based on 2.x kernel is again a waste of time & again one more incomplete rom

vishal24387 said:
Source code of jelly bean is of no use for us until we get kernel 3.0. Because building jelly bean rom or cm10 based on 2.x kernel is again a waste of time & again one more incomplete rom
Click to expand...
Click to collapse
You're right on that one bro.

Regarding porting Jelly Bean, it's another challenge for our great developers. And it is possible since it has already started coming on many devices. Another point is that JB does not introduce System level changes like ICS but a major update over it. So JB should easier than ICS.
Regarding Incomplete ROMs, each and every developer has his own set of skills and can't do what other can do and we must respect this. What dhiru can do is not necessarily doable by others too. But this should not come as deterrent for some quality work like MIUI and AOKP. If we would have kept waiting for 'Perfect and Complete' ICS then we would never have these great ROMs. These guys are working within known limitations and doing a great job. So i would always encourage new challenges, innovations, ideas, development and ROMs. We again might have many things not working on JB Ports but that's what fuel the developers to take up challenge and win it. Remember the first ICS and MIUI Ports ? And look today Thankfully Lolation, Frank, UT36104, Vurrut did not get discouraged by current limitations and went on to port these great ROMs and fix bugs. Thank You guys
Take every new thing as a challenge and give your best with whatever you have in hand instead of crying of what's not there or what will come someday
Good Day guys

silentvisitor said:
Regarding porting Jelly Bean, it's another challenge for our great developers. And it is possible since it has already started coming on many devices. Another point is that JB does not introduce System level changes like ICS but a major update over it. So JB should easier than ICS.
Regarding Incomplete ROMs, each and every developer has his own set of skills and can't do what other can do and we must respect this. What dhiru can do is not necessarily doable by others too. But this should not come as deterrent for some quality work like MIUI and AOKP. If we would have kept waiting for 'Perfect and Complete' ICS then we would never have these great ROMs. These guys are working within known limitations and doing a great job. So i would always encourage new challenges, innovations, ideas, development and ROMs. We again might have many things not working on JB Ports but that's what fuel the developers to take up challenge and win it. Remember the first ICS and MIUI Ports ? And look today Thankfully Lolation, Frank, UT36104, Vurrut did not get discouraged by current limitations and went on to port these great ROMs and fix bugs. Thank You guys
Take every new thing as a challenge and give your best with whatever you have in hand instead of crying of what's not there or what will come someday
Good Day guys
Click to expand...
Click to collapse
I completely agree. People learn by doing hands on, and what I mean is building roms. Discouraging them just because you want them to complete a rom is very selfish, everybody has to start somewhere. Not everybody has sufficient knowledge in android programming to help with completing roms, i believe people feel a sense of accomplishment after building their first rom, only to be struck down by others that want a complete rom. I just want to say guys, don't discourage new roms please, think about other people's feelings. Thanks.
Cheers
Sent from my GT-I9003 using xda app-developers app

bscraze said:
I completely agree. People learn by doing hands on, and what I mean is building roms. Discouraging them just because you want them to complete a rom is very selfish, everybody has to start somewhere. Not everybody has sufficient knowledge in android programming to help with completing roms, i believe people feel a sense of accomplishment after building their first rom, only to be struck down by others that want a complete rom. I just want to say guys, don't discourage new roms please, think about other people's feelings. Thanks.
Cheers
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
Its not about discouraging new rom development. Its about how well we concentrate on each thing to complete it. I am not saying that we should stuck to only one perticular rom development. But remember guys that google will not take a pause for us so that we can complete current cynogenmod rom. New versions of android will contineously come out by google but we must have to think whether we should run behind new roms or should we first build a base kernel 3.x without which every future development will remain incomplete...???

CyanogenMod

Hey guys when official CyanogenMod for ChaCha will be relesed?

liviucristian17 said:
Hey guys when official CyanogenMod for ChaCha will be relesed?
Click to expand...
Click to collapse
well, first of all this would depend on which -version- of cyanogenmod you're referring to. there is currently both a CM7 build out as well as a CM9.
And the current Cyanogenmod being worked on is CM10(although unfortunately nobody has started a port for the ChaCha with CM10 yet)
the next thing it depends on is when the builds become stable. most custom CM based roms out currently have a few major bugs(for example, the CM9 port doesn't yet have the front camera working)
and lastly, it depends on the developers of these ports to submit their source to the cyanogenmod community/team and for the cyanogenmod community/team to accept it as a stable and official build.
so "when" really depends on the developers, and the stability. so, likely not anytime soon.(especially based on the slow development for most roms for this phone lately)

kronflux said:
well, first of all this would depend on which -version- of cyanogenmod you're referring to. there is currently both a CM7 build out as well as a CM9.
And the current Cyanogenmod being worked on is CM10(although unfortunately nobody has started a port for the ChaCha with CM10 yet)
the next thing it depends on is when the builds become stable. most custom CM based roms out currently have a few major bugs(for example, the CM9 port doesn't yet have the front camera working)
and lastly, it depends on the developers of these ports to submit their source to the cyanogenmod community/team and for the cyanogenmod community/team to accept it as a stable and official build.
so "when" really depends on the developers, and the stability. so, likely not anytime soon.(especially based on the slow development for most roms for this phone lately)
Click to expand...
Click to collapse
I'm talking about CM7(official)!On their website on ,,get.cm" I don't see htc chacha/status tab!If you know where to download official CM7 pls tell me!

liviucristian17,
there's no Official and i think liviucristian17, CM7 still lacks the front camera?

Request for Collaborators: Merging the CM11 ROMs into one "official" one

Hi,
I see at least 3 different CM11 roms based on kitkat:
* http://forum.xda-developers.com/showthread.php?t=2524961 [ROM] CyanogenMod 11.0 | Android 4.4.2 KitKat [KANG] [May-6]+[NIGHTLIES]
* http://forum.xda-developers.com/showthread.php?t=2530073 [ROM][STABLE][Android 4.4.4] CyanogenMod 11 with 3.0.16 kernel [July 25, 2014]
* http://forum.xda-developers.com/showthread.php?t=2692278 [UnORom][3.4Kernel] CM-11 Android 4.4.4 [Stable v2.0][29 July][Final]
All more or less unmaintained as far as I can see - please correct me if I'm wrong!
What are the remaining difficulties to get a official CM11 ROM out of these? Then a lot more infrastructure from CM could be used - e.g. development tools, build machines & downloads. If the problem is to get a build machine on which 3-5 persons could would together over the Internet - I'll spend a vserver on my own dedicated server if there is a serious effort to bring up an official CM11 ROM.
If there are rather tiny things I could try(!) to help - I have almost no experience with android system development, but with Linux and development (C, Java, embedded devices,...) in general.
Two links for the rough procedure:
* http://wiki.cyanogenmod.org/w/Doc:_porting_intro - the hard part, but luckily almost done (isn't it?)
* http://wiki.cyanogenmod.org/w/Doc:_Submitting_A_Port - the final
Wiki-entry: http://wiki.cyanogenmod.org/w/Pyramid_Info

+1 for uptodate pure CM11 rom for sensation. I hope someone will join to you.

I think Flemmard's variant of CM is ready to be official!

official CM11 to Sensation!!!! We need it

+1

+1 It would be great thing for senny to so see official CM11 because many developers left us.

I don't think it's possible to make an official CM11 for our phone. IIRC, to be official it can't use legacy drivers and for the CM11 to work on our phone, I think we are using drivers from ICS because that's until where our drivers are updated, I'm not sure.
And "official" one in other hand would be amazing, I tried PA and etc but I always return to CM.

scanferr said:
I don't think it's possible to make an official CM11 for our phone. IIRC, to be official it can't use legacy drivers and for the CM11 to work on our phone, I think we are using drivers from ICS because that's until where our drivers are updated, I'm not sure.
And "official" one in other hand would be amazing, I tried PA and etc but I always return to CM.
Click to expand...
Click to collapse
Flemmards CM use KK drivers.

+1 for me too.

It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?

Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
That's not true... Team Venom also left us
For now we have official slimkat builds and maybe bilal liberty still develops for senny.
That's sad. We had many great developers and suddenly many of them left us. It will be great to see official CM builds.

Thats very sad, why they all leaving, i dont understand that. How's Ivanich latest 08/27 rom? Better than Sultan 07/25?
greetz

macicgangsta said:
That's not true... Team Venom also left us
For now we have official slimkat builds and maybe bilal liberty still develops for senny.
That's sad. We had many great developers and suddenly many of them left us. It will be great to see official CM builds.
Click to expand...
Click to collapse
bilal don't support our device anymore.

Inf1n1te said:
...Ideas?
Click to expand...
Click to collapse
The good thing is that all the great developers left us with good ROMs.
I think it is difficult to replace the devs. I can't fix the bugs they didn't fix until now, but I would like to try to keep at least one of the Cyanogenmod ROMs updated with upstream. I think in a month or two I will have time to start with that (if no one else is doing it until then).
@mifritscher: I think the lack of a build (or at least download-) server was a problem for devs here and then. So yes, your offer could be very helpful! Thanks for that!

Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
Sensation is a 3 year old device. i think as the devs have moved on to other devices, so should we. though our sensation has a lot of potential, i dont think devs will work on an android L port or making CM11 official. though there is hope with ivanich & bilal_liberty

Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
[....]
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
I can give storage space and bandwidth if it's useful, please contact me to discuss the details.

I can build but i dont know how to make a device tree so if someone can do the device trees i can do the builds

I don't know if we have everything working as on stock, also I don't know if the rom would pass cts.
But even if everything works, I don't think there's anyone around who has enough time to maintain an official build.
But at this point there's only one cm which is still updated and that's ivanich's one. Where's the difference in having an official build?

Where to go from here?
I'm just a casual user looking for a ROM. Going through these threads is confusing and so many links are dead.
What available for the sensation right now?

cynamun said:
I'm just a casual user looking for a ROM. Going through these threads is confusing and so many links are dead.
What available for the sensation right now?
Click to expand...
Click to collapse
Except for official slimkat all available and maintained roms are part of DevB so just click here in forum in the dev:db bar on roms.

Question about custom roms vs CM12S/Oxygen

Hey guys,
Just a quick question that I'm hoping someone can clear up for me. I have been flashing phones since the Vibrant and I seem to recall back then (and other phones I've had after such as the Sensation) devs would use the source of the firmware released from the manufacturer to create more stable roms and until that source was released there would be the possibility of the bugs.
I am coming from a Nexus 5 which I just used the stock rom since I wanted the OTA updates so it's been a while since I've flashed custom roms.
My question is, is the OPO the same way in the sense that in order to have more stable roms the source has to be released by CM in order to be more stable or is this a whole different beast where that isn't a necessity?
Thanks.

CM11S/CM12S is derived from the CM11/CM12 nightlies, all current ROMs are based on those CM sources, so all current ROMs are up to date. If you're flashing CM12 nightlies there's nothing extra that you need to do because firmware and modem is built in, but if you're flashing another custom ROM you need to flash the appropriate firmware and modem before flashing the ROM.
Oxygen is the exception to the above information, in the sense that it isn't based on CM. Flashing Oxygen will automatically flash the appropriate firmware, but if you want to revert back you need to flash the correct firmware/modem first.
Transmitted via Bacon

timmaaa said:
CM11S/CM12S is derived from the CM11/CM12 nightlies, all current ROMs are based on those CM sources, so all current ROMs are up to date. If you're flashing CM12 nightlies there's nothing extra that you need to do because firmware and modem is built in, but if you're flashing another custom ROM you need to flash the appropriate firmware and modem before flashing the ROM.
Oxygen is the exception to the above information, in the sense that it isn't based on CM. Flashing Oxygen will automatically flash the appropriate firmware, but if you want to revert back you need to flash the correct firmware/modem first.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, I did not know that but it does clear some other things up.
One other question, when a Samsung (for example Galaxy S5) rom is leaked, developers will use the latest leak to update their roms but typically a rom won't be "stable" until it is based on the source that is released.
Is the OPO like that as well where the custom roms need to have a source released in order to do that (is this the google android source or CM source?), I guess I'm trying to find out the stability of the roms versus a stock rom and whether there will be more bugs in one or the other.

sahil04 said:
Thanks, I did not know that but it does clear some other things up.
One other question, when a Samsung (for example Galaxy S5) rom is leaked, developers will use the latest leak to update their roms but typically a rom won't be "stable" until it is based on the source that is released.
Is the OPO like that as well where the custom roms need to have a source released in order to do that (is this the google android source or CM source?), I guess I'm trying to find out the stability of the roms versus a stock rom and whether there will be more bugs in one or the other.
Click to expand...
Click to collapse
That's what I answered in my last reply. The CM nightlies are the source, all ROMs are built based on those nightlies (except for a couple). This phone is nothing like a Samsung or an HTC where the stock ROMs are different from the aosp ROMs or CM based ROMs. The stock ROM for this phone is the CM ROM. The stock source is always released, every single day.
Transmitted via Bacon

timmaaa said:
That's what I answered in my last reply. The CM nightlies are the source, all ROMs are built based on those nightlies (except for a couple). This phone is nothing like a Samsung or an HTC where the stock ROMs are different from the aosp ROMs or CM based ROMs. The stock ROM for this phone is the CM ROM. The stock source is always released, every single day.
Transmitted via Bacon
Click to expand...
Click to collapse
Got it! Thank you!!

timmaaa said:
That's what I answered in my last reply. The CM nightlies are the source, all ROMs are built based on those nightlies (except for a couple). This phone is nothing like a Samsung or an HTC where the stock ROMs are different from the aosp ROMs or CM based ROMs. The stock ROM for this phone is the CM ROM. The stock source is always released, every single day.
Transmitted via Bacon
Click to expand...
Click to collapse
Not exactly true. CM is AOSP BASED, but modified - sometimes quite a bit. In the case of CM12S - this is a ROM specific to the OnePlus One. It isn't the same as CM12. It is only for this specific phone, and has some features in it that are specific to this phone.
I'm not sure why anyone would want to install Oxygen OS, unless they have just been brainwashed by OP that CM is now bad. Well that and the fact that CM still hasn't released 12S, nor am I convinced that they ever will. They seem to be pretty terrible when it comes to keeping up with the commercial side of things... Very amateurish.

mhannigan said:
Not exactly true. CM is AOSP BASED, but modified - sometimes quite a bit. In the case of CM12S - this is a ROM specific to the OnePlus One. It isn't the same as CM12. It is only for this specific phone, and has some features in it that are specific to this phone.
Click to expand...
Click to collapse
I know that CM is essentially aosp, and CM11S/CM12S is 99% CM11/CM12, with just a couple of fancy apps thrown in on top to make it seem a bit different. It really is just like a milestone release of the main CM branch, a stable release.

Not Exactly.
Heisenberg said:
I know that CM is essentially aosp, and CM11S/CM12S is 99% CM11/CM12, with just a couple of fancy apps thrown in on top to make it seem a bit different. It really is just like a milestone release of the main CM branch, a stable release.
Click to expand...
Click to collapse
Not really. There are no apps of which I am aware that that put in the "S" release. But there are features specific to the needs of that device and to that user community that add value.

mhannigan said:
Not really. There are no apps of which I am aware that that put in the "S" release. But there are features specific to the needs of that device and to that user community that add value.
Click to expand...
Click to collapse
CameraNext, the custom lockscreen. Both apps that are unique to Cyanogen OS. I'm sure there are more but I don't run that ROM so I can't check. You can believe it or not, but Cyanogen OS is just CM with a few extra apps/features. Your lack of belief in it doesn't stop it from being true.