Related
I'm pretty new to the rooting/ROM scene. What in particular gets people so excited about CyanogenMod?
If someone could give me an in-depth explanation of its features and pros, I'd really appreciate it.
AOSP, optimized, easy updates, fast, stable...
go here and see for yourself...
http://www.cyanogenmod.com/about
then go to the screeshots...
Cyanogen is a huge figure in Android Rooting and ROMS. Generally speaking the Cyanogenmod ROMs have tweaks that others do not. They are based on open source, which is great. They tend to use some of the most up to date android source available...
Used them on my Droid. My wife prefers Sense UI, so it looks like she won't be using it on her Eris.
Cyanogen a.k.a Steve Kondik (think of him as Oprah of Android) it all that start when Android just was picking up the mainstream and he first made his ROM for G1 phone (considerably the first phone to be powered with Android). He just blew every other developer out of water, JesusFreke, Haykuro, and DudeForLife are well known but no longer in development and that's because everyone rather use either Cyanogen or Ported Hero ROM. However, about Haykuro he's really good too, unfortunately due to some drama over Hero stuff, he bailed out. Some of Dev here leave because people here just grip on issues and drop drama bomb. Cyanogen handle drama better than most of dev I've seen.
I forgot to add few things, Cyanogen have connection with folks over at Google, particularly with those who are involved with Android development.
Is there a reason why the dev community cannot get behind cyanogenmod and still get donated to? Is there some kind of politics involved that will not allow this relationship? I just think I would like to see the effort into one project that is solid, without all the themes and "personal" touches you see with everything else.
In a word it doesnt seem like much progress is being made, except for some screenshots from the dude and an alpha build from eugene. If Eugene, Som, Codeworkxs thedudesandroid, and the rest of the vibrant devs worked on a gingerbread based cyanogenmod, it would benefit everyone.
Move me, flame me, just dont one line answer me.
Yours to change and modify:
https://github.com/CyanogenMod
Ideologies differ. Work ethics differ. I think a move like this would be destined to fail.
Have you personally experienced both Macnut and Nero? Both ROMS are outstanding. I think the more fragmented the ROMS are, the more ideas, experiments, and innovation will occur. I think to push devs to a single common platform would be both stifling and detrimental to the android modding community as a whole.
Besides, all the devs have the same problem... Drivers. Until we start seeing Gingerbread leaks, all devs would have the same stumbling block anyway, whether they are working as one, or separately.
i'm fairly certain all CM ROMs have been halted and work has been pushed to CM7.0 Gingerbread based. With the Nexus S (NS) being the same thing with a few minor difference to all the other SGS phones and the NS source being openly available for people, we should see a true Gingerbread CM ROM for all the SGS phones once they figure out the necessary changes to make our variants work. This time it should be easier, thanks to all the Devs who came before and figured out Samsung's ass-backwards way of doing things.
Time and patience will reward with the greatest Android ROM the world has ever seen!
angryPirate12 said:
i'm fairly certain all CM ROMs have been halted and work has been pushed to CM7.0 Gingerbread based. With the Nexus S (NS) being the same thing with a few minor difference to all the other SGS phones and the NS source being openly available for people, we should see a true Gingerbread CM ROM for all the SGS phones once they figure out the necessary changes to make our variants work. This time it should be easier, thanks to all the Devs who came before and figured out Samsung's ass-backwards way of doing things.
Time and patience will reward with the greatest Android ROM the world has ever seen!
Click to expand...
Click to collapse
This makes me moist.
d33dvb said:
Is there a reason why the dev community cannot get behind cyanogenmod and still get donated to? Is there some kind of politics involved that will not allow this relationship? I just think I would like to see the effort into one project that is solid, without all the themes and "personal" touches you see with everything else.
In a word it doesnt seem like much progress is being made, except for some screenshots from the dude and an alpha build from eugene. If Eugene, Som, Codeworkxs thedudesandroid, and the rest of the vibrant devs worked on a gingerbread based cyanogenmod, it would benefit everyone.
Move me, flame me, just dont one line answer me.
Click to expand...
Click to collapse
my question for you, is why does it have to be cyanogenmod? Youre asking all devs to collaborate to come up with one big super-ROM, yet it will still only be under the name of one developer, Cyanogen?? This doesnt make much sense.
So basically what youre asking is, since you PERSONALLY would prefer to run cyanogenmod on your phone, you want all other Vibrant devs to concede their own projects to assist your personal favorite developer with his project??
Why doesnt CM help with a new Team Whiskey ROM?? If your answer is because CM is more popular and has more development-power in the Android world, then you have answered your own question in regards to the "politics" that may be behind it.
I feel a lot of people (not necessarily the OP) just seek the "cyanogenmod" title to their ROM, without even really knowing what it is. They just hear the name thrown around all over the place and want to feel like they are in the loop; which is just mindless, in my opinion.
Its great to have several devs, with several different projects. It gives the average user (non-dev) options, and different things to choose from and try.
If you went to a car show, and every car had the same exact engine in it, what would be interesting in that??
what a communist suggestion
I, personally, love that there are many diff ROM's to choose from. I love having that variety. I prefer <tw> ROM's, just because they theme it pretty much how I would theme a ROM (and they scream), If I was even remotely capable of Dev'ing. Eugene makes an awsome ROM too, But not to my personal taste. On my G1 I always used cm ROM's, but the way they work at this point that's not possible for a Vibrant. So I guess what I'm saying is, I'm glad they're not all concentrating on one ROM because we would still be waiting... stuck with RFS !
I just want that Cyanogen bluetooth stack on a regular (sans Touchwiz) Galaxy S rom with TV out. The Bluetoouth stack is the only reason why I am using Cyanogen outside of the speedy OS.
Sent from my SAMSUNG-GT-I9000 using Tapatalk
I get what you mean but I have to say that I love flashing different devs roms & kernels, I would hate to be slave to one idea...I could have gone iOs for that.....get it iOs 4! I kill myself sometimes...
vibrant
GingerR2JL4
TopShelf10 said:
my question for you, is why does it have to be cyanogenmod? Youre asking all devs to collaborate to come up with one big super-ROM, yet it will still only be under the name of one developer, Cyanogen?? This doesnt make much sense.
So basically what youre asking is, since you PERSONALLY would prefer to run cyanogenmod on your phone, you want all other Vibrant devs to concede their own projects to assist your personal favorite developer with his project??
Why doesnt CM help with a new Team Whiskey ROM?? If your answer is because CM is more popular and has more development-power in the Android world, then you have answered your own question in regards to the "politics" that may be behind it.
I feel a lot of people (not necessarily the OP) just seek the "cyanogenmod" title to their ROM, without even really knowing what it is. They just hear the name thrown around all over the place and want to feel like they are in the loop; which is just mindless, in my opinion.
Its great to have several devs, with several different projects. It gives the average user (non-dev) options, and different things to choose from and try.
If you went to a car show, and every car had the same exact engine in it, what would be interesting in that??
Click to expand...
Click to collapse
Agreed. It seems to be the "you want what you can't have" theory. It's going to be funny when there is finally a CM ROM and all these same ppl that wanted it are going to wonder why CM is so plain looking and isn't themed up. It's an endless cycle. CM offers support to multiple devices, which gets their name out there. But I can promise you if you've ran ROMs such as Nero + voodoo, even the best running CM isn't going to "blow it away" in performance, maybe some fun features, but that'll about do it.
I'm satisfied with TWs stuff. All I'm hoping for is that we can get drivers written to do our own ASOP roms, so we can one day have 2.3 and beyond.
im curious about this as well and being that i have no clue, i feel completely authorized to put in my .02 that i thought the primary reason we dont have cm for the galaxy was due to lack of aosp/drivers...
LOL, you sad bunch of folks think I have never flashed a rom on the vibrant? Sure I have, but they are all roms based off of samsuck files, with a theme pushed on top. This requires some skill and understanding, but it does not make you a "ROM D3V"
I am not in any way trying to push everyone to cyanogenmod, I am trying to get the "real devs" to work on things like GPS drivers and such as a whole, to benefit everyone, you think the tricks we learn as a group you cannot then use as an individual? You cannot say I am communist (lmao) because I want the devs to work together, I suppose that what people say about XDA is true, the users who are flaming me make it unbearable to have a real conversation. I mean just look there are several "FANBOY" posts already, and we are on post 13. No wonder the real devs ficking hate XDA. The sole reason I personally like cyan is because of the testing that it goes through, to make sure embarrassing bugs dont happen often. He has developed a rom for my G1, then both my Mytouch's and just miss running it on my vibrant, thats all. My G1 is sitting here running CM 6.1.0 and my phone still sits here on Ginger Clone, the best there is right now.
FYI when there was lack of drivers on the Dream/Magic someone re-wrote them, mmkay?
It has always seemed that the devs share fairly well. While they don't work together on one project, they share what is needed and form teams of likeminded people to push out better and better products. If you want to see what happens when you get everyone together and make them all focus on one big new release look at samsung itself. These small teams can operate with greater freedom to build and release mods and roms as they see fit. Xda is about sharing info and improving our machines. Would we really want to have gingerbread today without all the options and flavors that different dev teams put together. If you say yes, that's fine, but I like the variety and am happy to wait for what's next.
Sent from my SGH-T959 using XDA App
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant General
CM is not really comparable to the XDA devs' ROMs. CM is a complete ground-up build from AOSP. Nero, Macnut, etc are not; they are mods of existing unofficial Samsung ROMs. (Not to imply that Eugene/Sombionix et al's work is anything less than quality).
mindaika said:
CM is not really comparable to the XDA devs' ROMs. CM is a complete ground-up build from AOSP. Nero, Macnut, etc are not; they are mods of existing unofficial Samsung ROMs. (Not to imply that Eugene/Sombionix et al's work is anything less than quality).
Click to expand...
Click to collapse
Yeah, that's the thing. The skill set involved in getting AOSP (and the rest of CM) building properly is a different skill set than modifying a Samsung released ROM.
The approaches are almost entirely opposite - whereas most ROMs here take what the vendor provides and replace the junky bits with stuff that works better, the AOSP-based ROMs such as CM start from a bare bones google source repository that never had any of that junk to begin with.
Both approaches have their merits. As should be obvious by now, the former results in much more rapid progress since you can start right away with a working build from Samsung. The latter approach can take substantially longer, since you don't have a working base to start from (especially with a device like the SGS, which has hardware very different from most CM-supported devices).
Eugene had an AOSP 2.1 rom pretty well built. Needed some kinks worked out, but there didn't seem to be a lot of interest because all everyone wanted was froyo. I'm sure we're probably see at least a couple of AOSP efforts if/when froyo officially drops.
angryPirate12 said:
i'm fairly certain all CM ROMs have been halted and work has been pushed to CM7.0 Gingerbread based. With the Nexus S (NS) being the same thing with a few minor difference to all the other SGS phones and the NS source being openly available for people, we should see a true Gingerbread CM ROM for all the SGS phones once they figure out the necessary changes to make our variants work. This time it should be easier, thanks to all the Devs who came before and figured out Samsung's ass-backwards way of doing things.
Time and patience will reward with the greatest Android ROM the world has ever seen!
Click to expand...
Click to collapse
Yep, codeworkx and the CMSGS team have stopped worked on 6.1 and (along with Supercurio and others) are working on an AOSP Gingerbread port for SGS.
It makes sense--no point in continuing to try to build a 2.2 without source when the 2.3 source is already out.
Here's what Cyanogen said on the Official CyanogenMod Forums.
http://www.cyanogenmod.com/home/a-note-on-unofficial-ports-and-how-to-get-it-right
With this said, why don't we jump on the bandwagon and just join the CM team? Why don't we make this thing official (if we haven't tried already)? Just a thought, so don't kill me with your opinions. The Devs here are freakin' legit here and I'd like to see 'em do some of the work on the CM Team.
I trust the devs I download from because I follow their work. I don't need it to be "official". Besides, I like the personal touch and one-on-one support I get right here on the xda eris forum. And there's variety.
We could debate the politics of branding and what is CM and what is not CM. But the devs here disclose their sources, changes, known issues and brand their roms as uniquely their own while providing the support and updates. I don't think there's any confusion as to what is 'official' and what is not as the Android Police article referenced in CM's statement implies.
+1. The devs here are excellent, and the devs that base there ROMs on CM list them as "based" on CM not the official CM ROM. I'm not aware of any confusion that this has caused. I'm also not sure what creative constraints would be put on our devs if they went CM. I like the way they individualize the roms for thier personalities and their audiences. I also am not sure what benefit would come with being an "official" CM rom. Just my 2 cents.
Don't get me wrong, I'm not discrediting the Developers that cook these ROM by ANY MEANS whatsoever. They do incredible work with what they push, but here's what I'm saying. The CM ROMS are based off of Official CM Source Code, yes, but I think we'd be making it way easier on ourselves and the developers if we were an actual part of CyanogenMod. If we were a part of CM, then we'd get the CM ROMS as perfect as they can get and THEN the developers can add their own customization to a ROM based off of the Eris Release of CyanogenMod. They all are already doing the work that it would take to actually /BE/ a part of the CyanogenMod team, so why not get on with CyanogenMod so we can be official, and THEN the devs can customize and tweak ROMS they way they see fit?
Once again, absolutely NO discredit to the developers here, and I understand what it takes to keep these ROMS current and I am very appreciative of their work.
The CM ROMs that we have are either built from CM source or ported from the Hero builds already. I'm not really sure what this would give us other than maybe a "go team go" feeling and maybe a little more help than we already get. But the Eris and CDMA Hero are so similar, that doesn't matter much in my opinion as long as any Hero issues get worked out.
The CM buildbots are just building from source and posting the results, much like you would get if you ran EasyDev or did it manually. Now, there's a lot of work going on before that with the code, of course. But... That's what we use too.
I'm not against this at all. It just means that someone will have to 1) want to do it 2) have the time 3) convince Team Douche to let them in. I seem to remember that someone asked early on and the response was that we had to send them an Eris. This might have changed.
This comes up every so often. I guess one of us can find out what we would need to do at least...
Nothing would really change for the end user if we became official cm at this point. Basically one of the devs here that builds from source would submit their vendor tree to the cm source and they would be responsible for maintaining it just like we do now. The only real difference would be that it would get built by the cm build bot and nightly's would be released. I tweeted to cyanogen about getting my 2.2 tree in there along time ago when 2.2 was new but either I did it wrong(not a twitter person lol) or it just got lost in the many many tweets that go through cyanogens account. I never really pushed the issue more because of the extra time it would take me personally and it was just easier to work on my own schedule.
The only added benefit would be that maybe if there was an issue we could not fix then the cm team would take an extra look at our specific phone to help out but really since our phone is so close to the hero and it has official support they sort of fix most of our bugs anyway. I've personally always tried to give the cm team all the credit they deserve(which is alot) and I think the other dev's do the same.
Here's what Cyanogen posted up to www.cyanogenmod.com a week or so again. It looks like we'd need an interested dev here to stop by #cyanogenmod-dev on Freenode to start the process.
I think (and I use xtrSENSE, so I could be wrong) that a lot of people would like and "official" CM port for the Eris, just so they'd have "peace of mind" knowing they've got something "official."
And again, as we've seen mentioned in this post, it couldn't hurt to ask. Provided Team Douche doesn't actually want an Eris, we only stand to gain extra help on our ports.
Cyanogen said:
There’s been some recent talk about unofficial versions of CyanogenMod being created and released on sites like XDA, with large amounts of missing features and broken functionality, and I just wanted to talk about our position on this.
An “official” CyanogenMod version is one that uses our code review system, our source repository, and our mirror network. It should look, act, and feel like CM on any other device, and more importantly, it should follow our release schedules (which is a “when it’s ready” kind of thing, but we do plan our final/RC releases when we feel it’s ready). Most importantly, no major hardware functionality should be broken.
We want to see CM available for every device out there, and our infrastructure (and our developer community) is there for anyone to use. We spend a lot of time making new releases of Android backward-compatible with devices that are not ready for them, and we also spend much time making all of these (sometimes not so pretty) changes co-exist together without breaking other devices. The more eyes on your code, the better it will be.
That said, as much as we’d like it to be, the CMSGS project is not yet an official part of CyanogenMod. There are also a number of other unofficial ports out there which haven’t been submitted to us that we’d love to include. If you’re interested, stop by #cyanogenmod-dev on Freenode. If you didn’t get it from our mirror network or the CM forums, don’t expect it to be up to our standards.
The biggest thing to keep in mind when porting to a new device is to think about how your change is going to affect other devices. This is the biggest reason why we aren’t supporting Samsung devices other than the Nexus S yet. Don’t change hardcoded default values just to suit your device. Use the configuration options available, or add new ones with the original values as defaults. Do a build for another unrelated device after you make your changes (it helps to have another device to test with, of course) and verify it as well. Android was made for this, so do it right.
Like I’ve said so many times before, CyanogenMod is all about the community. And our community can help you too. I’d love to see more of these ports contributed to the project- it’s only going to make things better. We’ve grown from just a mod to what I’d call an “Android distribution” and we need to keep our standards high.
Click to expand...
Click to collapse
Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft
hallstevenson said:
Oh no, does this mean we're all running unofficial CM ROMs ?
Wait, everything is working fine though... Official, unofficial, pffft
Click to expand...
Click to collapse
+1 10 char......
A dev would have to maintain the device and be committed to building it up, like Darchstar was (is?) for the Hero CDMA. It really all depends on the Dev/Devs for the device, for example I've seen Cyanogen say in his twitter that he would also like to see the Dream/Saphhire continue to be developed for but no one has stepped up to maintain it. I can also only imagine that there are some qualifications for someone to maintain a device. Here is a list of the current maintainers for the devices
https://github.com/cvpcs/android_vendor_cyanogen/blob/gingerbread/CHANGELOG.mkdn
Yeah, I can understand that. That's all I was saying, though. If they were doing all of the same work anyway I just thought it would be nice to have. I also didn't know if anyone had pursued this in the past, but seeing as how Conap had already tried I think I'm good with that. I also have no problems running the unofficial ROMs, just so you know. Thanks, guys!
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
the way i do it is best for me,,and seems to be going fine,,, the cm7 ports have been alot better then the froyo ,, and alot faster ,, look how long it took the froyo camera to work,, gb the camera works outta the box,,
Hungry Man said:
It's not like we just want it to be official... but porting a ROM has its downsides. There's nothing to say devs couldn't take a ROM that is NATIVELY supported for the eris (and not for the hero) and do exactly what they already do... we would just be cutting out work for them and it would definitely effect the end user.
Click to expand...
Click to collapse
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)
gnarlyc said:
There is more than one definition of porting that people are using around here.
1) Porting to an unsupported device = compiling source, building a vendor tree, and getting it to work on said device (This is basically what the CyanogenMod team would do to make it an official build, although they would integrate the changes into the main source. The changes would mostly still be in a separate vendor tree in the repo. And it would be 'official'. From a practical/technical view, what workshed is doing is the same thing that the CM team would do.)
2) Porting an existing build to an unsupported device = taking an existing, already compiled ROM and making it work on said device (This is what tazz is doing with the Heroc build. This works out well when going from the Heroc.)
Anyone, feel free to correct me if I'm wrong, but I'm pretty sure that I have that right.
The only downside that I see from either of these is MAYBE not getting quite the support that we would get if the Eris had an 'official' build. I really don't think it's affecting much of anything, IMHO. It might in the future as the Heroc and Eris become more and more dated devices. But then, many of you won't really care because you're kids will be using them as mp3 players anyway while you use your fancy, new quad core HTC Destroyer 6G. (What's a Beiber?)
Click to expand...
Click to collapse
I thought it was a girl
tazzpatriot said:
I thought it was a girl
Click to expand...
Click to collapse
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0
refthemc said:
Its a dude.
http://www.youtube.com/watch?v=3zb64y6Nvs0
Click to expand...
Click to collapse
nope still a girl
http://www.youtube.com/watch?v=vwIa2S0YQs4
FYI: http://twitter.com/cyanogen/status/45246447385452544
@cyanogen said:
@Algamer we don't officially support the eris, it would be nice if someone doing the porting joined up with us though
about 8 hours ago via web in reply to Algamerhttp://twitter.com/Algamer/status/45235578886815744http://twitter.com/Algamer/status/45235578886815744
Click to expand...
Click to collapse
I think OUR devs are doing just fine. Why change now?
wildstang83
wildstang83 said:
I think OUR devs are doing just fine. Why change now?
wildstang83
Click to expand...
Click to collapse
Our devs are doing more than just fine, especially considering the amount of development we STILL have going on even though the Eris was a short-lived device that was EOL'd after like 8 months, was mid-range compared to the original Droid, and is a pretty niche device being MDPI on Verizon...
Why change now? That's a good question and I don't have a great answer. Like some have said on this post, maybe we'll get more support with bugs, etc. Additionally, a lot of the users here on XDA are looking for consistency. Since many who read and post here lack the skill set to do any meaningful ROM development themselves, they rely on the kindness of willing devs. However, devs will often add their own "personal touches" to their ROMs, which is great and well within their right to do. Having said that, many users are just looking to for something where they know, "Oh OK, so this is the base CM ROM that's officially distributed."
Personally, I don't care whether we have an "official" CM build or not for the Eris. I'm pretty reserved when it comes to ROMs for everyday use and am still using xtrSENSE as my default. The only reason I posted up cyanogen's recent tweet was to show that cyanogen himself is well-aware of the Eris development, is personally following the Eris ports, and is open to a partnership. My hope is that, by bridging communication, I am doing my part in helping to expose any possible mutual benefit (Eris XDA devs, ROM end-users, and Team Douche at CM) that could be gained by considering an "official" build. Ultimately, I understand that this is a decision that can only be made by the devs and also, not fulling understanding ROM development or having the skill set myself, I believe they are in the best position to make that decision. Like I said, I'm merely acting as a messenger, bringing this communication to light on our forum.
Hi, at the risk of starting a massive flame war, please dont, I'm just after information...
Being that the S2 stock ROM is already pretty good and we already have a number of decent ROM alternatives I am wonder what else CYANOGEN is going to bring to the party.
I have read all the spiel so I am not looking for the usual answers, what advantages exactly does it have, will it have, say over COGNITION when COGNITION Is fully working with video, games etc etc and has decent battery life. Doesn't have the CM7 messaging but I prefer K9 stock anyway.
I am also surprised that people are already using CM7 looking at the amount of DEV that still needs done.
I tried a CYANOGEN port on my old HD2 and I was left thinking what all the fuss was about, i'm probably missing something huge here, or CYANOGEN is really for advanced users or something.
Again, please keep this thread clean and calm
Please just go through the threads and read. It's all there. I won't rewrite the book. In short though, think a year from now. Cognition is based on stuff samsung released. What happens when samsung moves on? Cm7 will still be pushing the latest goodies.
Sent from my GT-I9100 using Tapatalk
I'm not going to lie I never understood the hype of cyanogen rom. I have also tried with an hd2 and wasn't blew away and didn't see anything special. I think cyanogen mod is for people looking for aosp.
I have much respect for that team though because as far as I know there roms are built from ground up. Unlike most custom roms sgs2 have are really just themed stock roms with a couple tweaks.
Sent from my GT-I9100 using XDA App
you should probably stop wasting space here and go to cyanogen's site and read what it is about. if it doesnt interest you after that you dont have to think about it ever again. no need for threads like this, it just makes you look bad because you obviously have not spent any time researching and educating yourself before asking this question.
Isn't Android reinventing the wheel? iPhone was here first, and Android is just duplicating iPhone functionality. Google should shut down the Android project immediately.
da.trute said:
i'm probably missing something huge here, or CYANOGEN is really for advanced users or something.
Click to expand...
Click to collapse
Bingo!!! Some of us don't want to use crapware installed by the manufacturer who is really not a software expert, just a hardware expert, and want to come as close to the stock Android experience as possible. For me personally, things like hold volume button to skip to next song, switch between percentage battery and analog battery anytime you want, a very advanced OS theming engine which doesn't require you to flash anything to change the theme, always being on the bleeding edge of new Android releases/bugfixes etc. is the icing on top of the cake.
However, it's really about the excitement of checking the commit logs of the nightlies everyday to see what's new.
Yeah I never understood what the hype was all about either, don't get me wrong its a great aosp Rom and I give the devs a world of credit, but it feels like a number of things are just incomplete.
It has a few features that aren't found on most roms and runs quick as Hell, but if your looking for an in depth user friendly experience I would not say that this is the best for that as it lacks a lot of simple things you might be used to if your coming from a sense or some other kind of based rom
All I can really say is back yourself up and give it a try for a day or two and if you don't like it then just go back.
CM has only just come out, and is far from stable, and only really should be used if you are willing to help debug or want to live on the bleeding edge
We want CM for when samsung have abandoned us.
Its always good to have options!
Each rom,whether its a "themed" stock rom, or a ground up one like CM7 offers something different.
The obvious advantage has already been mentioned - once SGS2 goes EOL for Samsung, CM7 will continue to support newer versions of Android till as long as the (very) capable phone hardware can handle it.
There are improvements... for some... e.g. the native Samsung bluetooth stack doesn't work with Wiimotes... for instance... i believe CM7 and know MIUI does...
Its really a case of... pick and choose... no1 charges for these... try...as many... if you like one... say thanks to the Rom maker... and possibly a small donation!!!... and stick with it...
Thanks everyone, thats pretty much what I thought, nothing special compared to a good feature packed cooked ROM but very useful in the future when sammy stop updating, I just thought I was missing something huge the way people get excited about it.
Will stick with COG for now until CM7 is looking fairly complete and then give it s roll.
yeah its all about when samsung abandons the device. in addition, it also is about running a fully open source ROM on your phone. once the cyan rom gets stable, each night it will be updated with a change log, so gives you the ability to constantly be seeing the fixes to the software actually running on your phone. something you dont like? commit to the code, and it may get merged into the repo. its about having total control over the device you are using, seeing every little feature, the code for it, how it works, and ability to modify it if you want.
of course it also has some good features too. but the above is what i think the point of cyan is.
Coming from the Epic, and then from the S3, I have noticed the fragmentation of Android with just the dilution of good development.
With that said, I acknowledge I am a user, not a Developer. I've tried to get interested in development, it is just not where my passion lies.
This is one of those useless posts you see on XDA, however, I feel like there is not much going on in this forum so maybe this is the best discussion we could have.
Take Apple, they have one product to focus on, no one to share the spotlight with. Android on the other hand has several, I have no idea how many, to share the spot light with. S3, S4, S5, Oppo, One, name your poison.
I say all this because I remember back to the Epic... It was Epic. The phone was amazing when it came out, the development was even better.
Now that I'm on the S4, while I don't want to take away anything from what the developers on this phone have done, it is not their fault, but developers will flock to where the demand is. And it just doesn't seem to be here.
Maybe this is Sprints fault? I stay with Sprint because they're the cheapest option I have. Certainly not the best, but definitely the cheapest.
Just trying to promote a discussion, not a flame war. Start now.
socos25 said:
Coming from the Epic, and then from the S3, I have noticed the fragmentation of Android with just the dilution of good development.
With that said, I acknowledge I am a user, not a Developer. I've tried to get interested in development, it is just not where my passion lies.
This is one of those useless posts you see on XDA, however, I feel like there is not much going on in this forum so maybe this is the best discussion we could have.
Take Apple, they have one product to focus on, no one to share the spotlight with. Android on the other hand has several, I have no idea how many, to share the spot light with. S3, S4, S5, Oppo, One, name your poison.
I say all this because I remember back to the Epic... It was Epic. The phone was amazing when it came out, the development was even better.
Now that I'm on the S4, while I don't want to take away anything from what the developers on this phone have done, it is not their fault, but developers will flock to where the demand is. And it just doesn't seem to be here.
Maybe this is Sprints fault? I stay with Sprint because they're the cheapest option I have. Certainly not the best, but definitely the cheapest.
Just trying to promote a discussion, not a flame war. Start now.
Click to expand...
Click to collapse
With unified builds, awesome devs are still contributing to our device! Its cool that a talented dev who builds aosp but is with verizon can build for us too. There is no shortage of great development going on, but I'll admit the sprint s4 forums are not as active as I remember the e4gt forums being.
To address your other point, sure - the sheer amount of android devices available will mean the pool of talented devs are spread more thinly across the spectrum of devices, but this community rocks and with a little google-fu (xda helps those who help themselves) I don't think development has really stalled. The forums are just a little less active. What IS a shame is that users here will drive talented devs away from releasing their work publicly on the forums by driving them insane with questions that have been answered 100s of times, petty politics, and flame wars, etc.
But at the end of the day, I would rather have an open OS with a vibrant (or dull) community than a locked down device I can never truly have full control over. But frequent upgrades have always been pushed by manufacturers, at the end of the day profits are the bottom line for them. Thats what is so great about this community, is that the devs here do work that would have gotten them a decent commission or wage elsewhere, FOR FREE. God bless :good::highfive:
All good points, and I would have to say I agree with you, especially with the shame that developers sometimes are driven away by lazy users.
mxmr said:
With unified builds, awesome devs are still contributing to our device! Its cool that a talented dev who builds aosp but is with verizon can build for us too. There is no shortage of great development going on, but I'll admit the sprint s4 forums are not as active as I remember the e4gt forums being.
To address your other point, sure - the sheer amount of android devices available will mean the pool of talented devs are spread more thinly across the spectrum of devices, but this community rocks and with a little google-fu (xda helps those who help themselves) I don't think development has really stalled. The forums are just a little less active. What IS a shame is that users here will drive talented devs away from releasing their work publicly on the forums by driving them insane with questions that have been answered 100s of times, petty politics, and flame wars, etc.
But at the end of the day, I would rather have an open OS with a vibrant (or dull) community than a locked down device I can never truly have full control over. But frequent upgrades have always been pushed by manufacturers, at the end of the day profits are the bottom line for them. Thats what is so great about this community, is that the devs here do work that would have gotten them a decent commission or wage elsewhere, FOR FREE. God bless :good::highfive:
Click to expand...
Click to collapse
I'm not a developer either (well of any roms/android mods at least). But as a long time computer power user and burgeoning programmer (3rd year comp sci major) the development on the S4 is very lack luster. We could get into comparing S4 vs development on older platforms, but I'd rather just discuss the generally bad development in the sprint S4 non-original android dev. forum. Most roms are not suited for daily drivers. I have personally tried 2-3 different versions of Sac's Rom and negalite's rom( as well as 1 try on various other roms) and none was with out major flaws.
The problem as I see it is this: The demand is for the newest rom with the most up to date android features. So as rom developers are getting closer to making a stable working version of their roms, Sprint releases an update at which point most developers switch and start working on new release with out ever making a fully functioning rom. To make matters worse most Rom's are presented as a finished product. Some have a known issues section in the first post ,but I challenge any one who disagrees with me to find a known issues section on a rom that actually contains all the know issues. It doesn't exsist. Instead each user is left to download an unfinished product and only after discovering an issue and digging though 10 pages of forums you find others have the same issue and that there may or may not be a soultion. How f'ing hard is it when a god damn issues is reported to update the orginal post?????? I understand these developers are doing this out of the good of their hearts, but anything worth doing is worth doing correctly. If it is to much work to keep an up to date list of ALL known issues, have one of the roms users do so. Not much work for one fan of a rom to keep list of issues if dev cant be bothered.
You help no one when custom roms break things working in the stock version and present it as a working rom. Custom roms used to add fucntion to a device now, it adds somethings and breaks others. Till this trend changes, the best rom is stock rooted + w/e mod a user desires. When a bunch of things dont work label your Rom alpha when most things work call it beta and only when everything works call it stable. This kind of common sense would improve everyone's experience greatly.
mysongranhills said:
I'm not a developer either (well of any roms/android mods at least). But as a long time computer power user and burgeoning programmer (3rd year comp sci major) the development on the S4 is very lack luster. We could get into comparing S4 vs development on older platforms, but I'd rather just discuss the generally bad development in the sprint S4 non-original android dev. forum. Most roms are not suited for daily drivers. I have personally tried 2-3 different versions of Sac's Rom and negalite's rom( as well as 1 try on various other roms) and none was with out major flaws.
The problem as I see it is this: The demand is for the newest rom with the most up to date android features. So as rom developers are getting closer to making a stable working version of their roms, Sprint releases an update at which point most developers switch and start working on new release with out ever making a fully functioning rom. To make matters worse most Rom's are presented as a finished product. Some have a known issues section in the first post ,but I challenge any one who disagrees with me to find a known issues section on a rom that actually contains all the know issues. It doesn't exsist. Instead each user is left to download an unfinished product and only after discovering an issue and digging though 10 pages of forums you find others have the same issue and that there may or may not be a soultion. How f'ing hard is it when a god damn issues is reported to update the orginal post?????? I understand these developers are doing this out of the good of their hearts, but anything worth doing is worth doing correctly. If it is to much work to keep an up to date list of ALL known issues, have one of the roms users do so. Not much work for one fan of a rom to keep list of issues if dev cant be bothered.
You help no one when custom roms break things working in the stock version and present it as a working rom. Custom roms used to add fucntion to a device now, it adds somethings and breaks others. Till this trend changes, the best rom is stock rooted + w/e mod a user desires. When a bunch of things dont work label your Rom alpha when most things work call it beta and only when everything works call it stable. This kind of common sense would improve everyone's experience greatly.
Click to expand...
Click to collapse
To a degree, I definitely am with you on this. I have been with this forum since the days of my old HTC thunderbolt. There are AT LEAST 5 popular daily drivers that worked worlds better than the stock rom for that phone. My particular phone glitches out on the dialer/phone app for all Original Android ROM's meaning I am automatically limited to a TW rom. I've tried everything to fix this but nothing seems to. However, there is one that works flawlessly, Triforce 5.4. It's perfect, so far as I can tell, but is starting to show its age. It may be the only perfect ROM for our phones but is almost completely without bells and whistles, unlike the Thunderbolt, which you could save multiple working images to SD and restore if you felt like using sense one day, CM the next, and I do recall a few completely custom ones loosely based on CM that worked awesome. Anyway that's my say on it. I am sad NAE firmware capabilities don't have a nice Triforce release to go with it, but the PRL and firmware seem to work great with the ROM, so I guess I'll stick to it, even if it is boring. It definitely does everything I need for it to do. Still, finding the issues with each one and helping the developers is part of the process. It's fun and part of the reason why I do what I do. Take my ASUS Transformer. That thing is old as the hills, but has multi window, android 4.4.3, windowed apps, and all manner of other things and it runs super smooth. timduru is the dang wizard of that device and refuses to let it die peacefully.
arikdahn said:
To a degree, I definitely am with you on this. I have been with this forum since the days of my old HTC thunderbolt. There are AT LEAST 5 popular daily drivers that worked worlds better than the stock rom for that phone. My particular phone glitches out on the dialer/phone app for all Original Android ROM's meaning I am automatically limited to a TW rom. I've tried everything to fix this but nothing seems to. However, there is one that works flawlessly, Triforce 5.4. It's perfect, so far as I can tell, but is starting to show its age. It may be the only perfect ROM for our phones but is almost completely without bells and whistles, unlike the Thunderbolt, which you could save multiple working images to SD and restore if you felt like using sense one day, CM the next, and I do recall a few completely custom ones loosely based on CM that worked awesome. Anyway that's my say on it. I am sad NAE firmware capabilities don't have a nice Triforce release to go with it, but the PRL and firmware seem to work great with the ROM, so I guess I'll stick to it, even if it is boring. It definitely does everything I need for it to do. Still, finding the issues with each one and helping the developers is part of the process. It's fun and part of the reason why I do what I do. Take my ASUS Transformer. That thing is old as the hills, but has multi window, android 4.4.3, windowed apps, and all manner of other things and it runs super smooth. timduru is the dang wizard of that device and refuses to let it die peacefully.
Click to expand...
Click to collapse
I just recently got off heavily modded stock and flashed Super S4 and so far it is awesome. Ktoonz's Kernel is baked in and after using recommended recovery to flash I've had no problems. It isn't heavily modded (mostly other mods baked in and some init.d tweaks) but is fast and stable and is one of the very few TW roms I'd recommend.
When I was on HTC Inspire 4G, There were easily 10 Roms (ASOP and Sense) suitable for a daily driver. For the S4 I'd be hard pressed to find 3 stable usable TW roms at a time.
I think android as a platform is changing a lot philosophically, as well. Older custom roms used to be a must have and were the main reason most users wanted root. Now everything is much more framework centric. Now root is used to add functionality through Xposed framework modules,or audio mods like Viper. Previously each and every mod had to be rom specific.