Related
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.
Don't get me wrong, CM7 ROCKS! I'm running the nightlies on my phone. I just remember a time when the Dev forum was full of MANY different devs with completely independant and creative builds. Now it seems like the forum is DOMINATED by various builds, re-builds, and re-hashes of CM7. I know there are still non-CM7 developments going on, but it seems like it's the exception to the norm now.
Like I said, I'm a big fan of CM... but I'm a bigger fan of competition and diversity. And yes, I see the hypocrisy.
Anybody else feel this way?
I see what you are saying but cyan is a Modding clan now. Standing the test of time. And it shows what a community is capable of when focusing a common goal.
Like Ubuntu, one of the teams ends up being #1.
Perhaps due to the recent OTA, once we'll start seeing some development. Many problems arose from aosp alone; it kept dev's away from the project.
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.
Last night, +Steve Kondik took to twitter to vent a little bit:
"CM has been getting a lot of crap lately for taking so long with a release. Guess what? It's not that easy. We don't just call something stable unless we mean it. *Also, RC1 is soon!* The most stable devices will get the RC first. The system we've put in place should allow other devices to catch up quickly. More details later this week "
Now to combat the obvious questions:
# As Steve stated, this will not be for all CM9 supported devices. The Nexus S and Galaxy Nexus can be considered safe bets, but the final list won't be available until release day.
# As always, the proper day of release is difficult/impossible to predict, but we anticipate a code freeze going in place tomorrow at the earliest.
# Yes, this means we will actively be running two separate RC phases (CM7 and CM9). Bug's should be reported to the issue tracker once the release is made, not in the comments on our posts.
# There has been a lot of talk surrounding Linaro in CM. While CM 9.0 won't ship with all the patches on gerrit, quite a few of them are already incorporated and others are sane enough that they will likely be there. There are still some issues surrounding the updated gcc used for the Linaro patches that don't play nice with AOSP.
# Nexus One: For the time being, the N1 will not be supported. We can get it to build/boot/run, but the hacks required break Google's CTS, so until that is rectified, you won't see any build with CM's official stamp of approval.
CM9 News
And from a followup a few hours later:
******
+Ricardo Cerqueira sat down with XDA recently for a developer interview
To piggy back on our comment about the N1 and CTS, Ricardo describes why we don't just shrug off that requirement.
Because it opened a can of worms that can’t be closed again. Getting it to work needed some very ugly workarounds that directly go against Google’s compatibility document for ICS. An app developer targeting ICS as a minimal version for his apps has the right to expect some functionality to be guaranteed on a device that claims to be ICS, that wasn’t (and isn’t) true for ICS builds with these hacks. That’s one the main reasons CM9 does not officially include a bunch of devices that are “working.”
...and some users understand that, but a lot don’t, and they’ll submit error reports on those apps, or they’ll rate it badly at the Play store. This is not a hypothetical scenario, it has happened whether we like it or not, asked for it or not, CM’s userbase is large enough to matter, even if you don’t count derivatives. We have a responsibility not to cause that kind of grief to app developers and we did. With all the mostly bull**** talk about fragmentation, we actively contributed to a break in the platform, no matter how small. That’s not a good thing :X People SHOULD know these builds contain hacks, but you’ve surely realized by now that they don’t
******
dookie23 said:
....so until that is rectified, you won't see any build with CM's official stamp of approval.
Click to expand...
Click to collapse
so.... is that ever gonna get rectified
charlie_su1986 said:
so.... is that ever gonna get rectified
Click to expand...
Click to collapse
I wonder what are the hacks he mentioned in the post. Was it the hboot hack, m2sd hack or swap partition...etc?
what is all the fuss about CM9 not releasing a rom officially when we have quite a few talented devs that have already given us the choice of running a near perfect ICS Rom on our nexus one?
EDIT: BCM offers CM9 features, AOKP offers us users the choice of AOKP features and texasice rom has a twist of its own features to. I do not see a problem with CM not releasing an official rom
Kannibalism said:
what is all the fuss about CM9 not releasing a rom officially when we have quite a few talented devs that have already given us the choice of running a near perfect ICS Rom on our nexus one?
EDIT: BCM offers CM9 features, AOKP offers us users the choice of AOKP features and texasice rom has a twist of its own features to. I do not see a problem with CM not releasing an official rom
Click to expand...
Click to collapse
Don't get me wrong, I love seeing the talented devs make awesome progress on kang'ing CM9 and things are coming together nicely. What I am getting at is not whether Cyanogenmod is releasing a CM9 rom officially for the Nexus One, but it's what Ricardo Cerqueira said about the hacks breaking Google CTS. This could mean that apps might not run or worse yet, FC's for no reason.
Now, the real questions are, what are these hacks Ricardo was talking about and is that gonna get rectified?
the hacks they talk about could be small stuff like ta camera fix etc since vendors do not always release new drivers.I would say that the nexus one is using a few hacks for drivers in order to make everything work better
I suspect it's a combination, both messing with HBOOT partition sizes (which is not a *bad* thing, but involves a lot more risk than just flashing a new ROM) and the nasty driver hacks that the poor dev's have had to do to try to working around the lack of a Broadcom driver, since they saw fit to release neither a driver nor sufficient documentation. It's hard to see how either could be overcome for an "official" CM9 release. I feel like it's a bit of a chicken and egg problem; with sufficient dev attention things could probably be brought into acceptable shape, but unofficial ports will never have sufficient dev attention.
Disclaimer: I really appreciate all the work that's been done by everyone on all the community ROMs. It's a hard, often thankless job, whether you're debugging mystery driver issues on an older phone or trying to coordinate a release for dozens of different devices with angry, impatient fans. While I'd love to have an official, flawless ICS ROM, at least we get more love from the community than we did from Google
decoherent said:
I suspect it's a combination, both messing with HBOOT partition sizes (which is not a *bad* thing, but involves a lot more risk than just flashing a new ROM) and the nasty driver hacks that the poor dev's have had to do to try to working around the lack of a Broadcom driver, since they saw fit to release neither a driver nor sufficient documentation. It's hard to see how either could be overcome for an "official" CM9 release. I feel like it's a bit of a chicken and egg problem; with sufficient dev attention things could probably be brought into acceptable shape, but unofficial ports will never have sufficient dev attention.
Disclaimer: I really appreciate all the work that's been done by everyone on all the community ROMs. It's a hard, often thankless job, whether you're debugging mystery driver issues on an older phone or trying to coordinate a release for dozens of different devices with angry, impatient fans. While I'd love to have an official, flawless ICS ROM, at least we get more love from the community than we did from Google
Click to expand...
Click to collapse
I agree with this post i would put the blame on google for not pushing the vendors for the broadcom drivers since android is open source after all but once again great works by our devs and thanks for letting us experience the latest versions of android on our devices
EDIT: i must admit that i have better devices to use than the nexus one but the community keeps me coming back for more
Sent from my Nexus One using xda premium
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.