Custom ROM bugs - ZTE Axon 7 Questions & Answers

Hi,
There are many custom ROMs for our beloved Axon 7.
Do these ROMS still have deal-breaker bugs?
If you think they do, please post the ROM and the deal-breaker bug(s).
If you don't, please refrain from posting (unless someone posts a bug that does not exist (anymore)).
Thanks!

Deal breaker is a relative term. You would need to have a list as to what would prevent you from going to a custom ROM. Most people thought the speaker bug was too big of a deal to move. Others (like myself) dealt with it because we wanted to get away from the stock offering. Best to define what a "deal-breaking bug" is and then go from there.

Waancho said:
Hi,
There are many custom ROMs for our beloved Axon 7.
Do these ROMS still have deal-breaker bugs?
If you think they do, please post the ROM and the deal-breaker bug(s).
If you don't, please refrain from posting (unless someone posts a bug that does not exist (anymore)).
Thanks!
Click to expand...
Click to collapse
I wonder why you don't just try the dual boot patcher... That way you can actually use the ROM and see for yourself. The bugs that made me want to go back to stock were specific of my device. One that probably wasn't though, was app compatibility on LOS, especially games, and 3d games even more so. But not on RR for example.

Related

Which ROM is Good for me?

Hi guys, I'm a little new to this ROM thing and I would like to change mine because it keeps freezing. How do I know which ROM is the best for me and how do I know whats different between them. Sorry for the ignorance but I've read a few of the posts adn feel confident that I can do it I would just like a little help/ insight before I actually just go throwing something on here. Thanks Nyne!
Nyne's said:
Hi guys, I'm a little new to this ROM thing and I would like to change mine because it keeps freezing. How do I know which ROM is the best for me and how do I know whats different between them. Sorry for the ignorance but I've read a few of the posts adn feel confident that I can do it I would just like a little help/ insight before I actually just go throwing something on here. Thanks Nyne!
Click to expand...
Click to collapse
Well, first thing, I think this post belongs over in the General Forum. This is the place for Chef's to post their ROMs. But we'll let a Mod decide that and since I'm not a Mod...
The great thing about flashing ROMs is that there are so many to choose from. I can't tell you from week to week which one is my favorite, but then I do a weekly flash just to stay on top of the latest stuff
If your phone is freezing due to the well-known SMS bug, you can either find a ROM that replaced the HTC Messaging with something more stable.
If you are like me, you will probably pick your first ROM based on looks, and then from there you may end up flashing different ones that satisfy your current needs.
I've never heard of anyone breaking their phone by flashing too much, but you still want to be careful and only flash ROMs that have positive feedback in the comments. At least, at first.
After you get some experience, you may just decide to start going crazy and make your own
Best approach is to read the first few posts of the roms you are interested in, map them against any requirements you have and try a few. Read the various stickies and tutorials carefully first.
Closing this thread now.
WB

Devs, Please don't hide your Known Issues

I really don't want this to come across wrong, but I just have to say it.
Developers, I appreciate all your hard work. I understand this is all beta/test/etc. I understand it is free of cost, even to those who did donate to one dev or another. You do it because you want to, not because you have to.
But please, for the love of all that's good - keep an updated list of Known Issues!
It sucks having to read 50 pages of posts to try to figure out if a particular release is reliable or not, to find out if there's a key feature broken or buggy. What makes it worse is you can't tell when reading these threads which users are on which release, because many still post issues after they've been resolved. Others post things that aren't really "issues" but user error.
You know what your issues are, you read the threads and you fix the issues. But trying to find a decent rom to flash is very, very difficult when your OP says "No known problems" and the thread that follows show that to be very untrue. It generates a lot of extra posts with people posting things you already know about, and it generates a lot of bad will when someone flashes something only to find that there are a number of game breaking issues.
All it takes is to update a post, say #2, in your thread, with KNOWN ISSUES. Once you confirm a bug, whether you intend to fix it on your next release or not, add it to that thread. It helps you, as a dev keep track of the bug, and it helps potential downloaders know what bugs have been confirmed and make an educated decision as to whether they want to install your release.
Hiding known issues is something I don't think anyone does intentionally, but it feels that way sometimes. It feels like devs are in a popularity contest, and any admission of flaws in their particular ROM is a weakness. Well, to tell the truth, I and many others are sick of installing something that was CLAIMED to be working perfectly, only to have glaring problems that have been there for many versions.
For a civil and productive development community. Please. Be honest with your known issues. It will go a long way in building trust with the people who you're providing ROMs to, and will mean fewer posts for YOU to wade through of users reporting known issues, without having read 500 posts first.
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
They don't care to list them. It's beneath some of them.
Maybe AirBus should list "midair exploding engines" as a known issue too...
kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
Click to expand...
Click to collapse
+1. Hell, at work I run a $100,000.00+ software suite and even that company won't do what the OP suggests!
If you have a problem with them stop using their roms go back to stock and see how much better theirs is even with a few bugs, not one of you has any right to complain. They do damn good work for free with some donations that do not come close to what they should be paid for it but they do not whine at all.
The problem I find is the "spammy" and useless comments average and pretentious users make which is both hard for the developer and the end user to read the threads. A dev releases a ROM and there is a guaranteed "Oh I can't wait to flash this" comment that will pop up. And there are some issues that are minor and are sometimes not related to the release that are posted and some pretentious loser who extends his ego by trying to make simple matters complicated. This forum didn't much of this problem before and I could quickly flash ROMs easily since I could clearly grasp the status on the ROM project.
I wish they would start a new thread with new releases. It's a pain to try to read through a 500 page thread, and you comments about this or that, and you have no idea which version the person is talking about. I gave up on custom roms and just using the leaked tmo 2.2, thanks for that Eugene
kponti said:
Since the developers here are NOT getting paid (NO your $20 donation is not sh*t for the time it takes to make one of these roms), yes WE will have to bear the brunt of testing these roms out and letting them know what bugs if any are in them
The other issue is the people flashing these roms, coming from Eugene's to Whiskey to the ASOP roms may generate some ghosts in the software that the developers cannot duplicate themselves. I know that when I went with the TW 2.2 roms I had plenty of issues, more issues than I have had even when I was stock. Odining back to stock and reflashing the 4.2 TW fixed ALL my problems. Dont know what caused it but since I have flashed a couple of roms prior to that (no problems), I will assume there were some ghosts in my system. This is an example that unless a TW team member is holding MY phone and working on it, they may not be able to duplicate
Click to expand...
Click to collapse
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Update: Here is the link for the WIKI page.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
swehes said:
Posted a new Thread in Dev section for the purpose of reporting issues. So if you have an issue please shoot it to me and I will post it in that thread.
Click to expand...
Click to collapse
You are in a heap of trouble, a lot of people don't read, and you are gonna get 1000000000000000000000000000000000000000000000 repeats of the same issue.
"OMG! MY SD CAR DONES"T MOUNT< HELP ME!11!!111"
chui101 said:
I have a hard time believing that most devs actively hide them. Most of the time it's probably just a bit of laziness. But, yes, it would be helpful when comparing roms if the descriptions had a well-maintained list of active bugs.
Click to expand...
Click to collapse
The issue here is really that a forum is not the ideal place to manage software releases. A list of bugs emerges from community testing, but there's nowhere to "post" that list of issues, or attach it to a specific release. Since there's no way for the community to add such documentation, it falls on the ROM builder, who probably has other priorities.
This kind of project could be well served by using a real software project management software solution, such as say google code, which has an issue tracker and other useful features. But XDA does already give us a better tool than the forum - the XDA wiki!
I wish people would use the XDA wiki more extensively. This would be a good place to keep updated documentation such as this, without requiring the OP to keep a forum post updated with the latest findings. All the OP needs to do is link to the wiki page, and other people can help maintain it.
OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
swehes said:
OK. Looking into Google Code.
(Update) So looking into the Google Code. What Licensing agreement are the ROMs under? Is it GPL v2 or v3 or another license?
Click to expand...
Click to collapse
Depends on the project. The Linux kernel is GPLv2, so any kernels fall under that license. AOSP as a whole uses both GPL and apache code.
The issue with ROMs is that unless they're AOSP derived (like cyanogenmod) they often include binaries for which the license situation is murky at best, so google code isn't really an ideal fit for a "ROM" that's only ever released as a binary.
Really I was throwing google code out there as a well known example, there are tons of other ways to track issues. There are dedicated issue tracking systems such as trac, bugzilla, etc, but they require hosting. Most of the freely available hosted services require that you're running an open source project, which isn't necessarily true for the ROMs here.
IMO a serious project could very well benefit from such tools, but just using an XDA wiki page which community members can freely update is a great first step.
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.
Stargazer3777 said:
Not to be the "Spelling Nazi", and I am not even sure if you can change it, but it is "Kernel" not "Kernal". Also, the Dev on Team Whiskey is Sombionix, not Symbionix.
Otherwise, that looks like a great idea, and possible way of tracking things!
EDIT - I guess I could go ahead and make those tweaks, with it being a wiki and all couldn't I....
EDIT EDIT - Fixed it.
Click to expand...
Click to collapse
Thanks. On both accounts.
Maybe this should be a post to Microsoft
To quote "there are known, unknowns and unknown, knowns and and even sometimes unknown,unknowns............but.........
Developers ----develop they do not become a bookkeeper of their development.........that is coordinating work...........good luck getting any developer in ANY Specialty to do that............. reporting bugs........
---Maybe this should be a post to Microsoft---
N8ter said:
A $20 donation is not worth the risk of bricking a $550 phone just because they got "lazy" and didn't notify donators/downloaders of [a] potentially show-stopping issue.
Click to expand...
Click to collapse
I have yet to see a REAL (completely dead) "bricked" vibrant from flashing a released Rom alone. I have seen a lot of user error cause boot loops or "soft-bricks" & HWL phones become unflashable because the end user didn't take the time to research though. As far as devs being "lazy" I dont really see that when the developer is coming here for us to tell him what else we find wrong. They are coding, you flash, you report back with a logcat. This is how development is made to my understanding. If ppl are to lazy to JUST do this then why shouldn't the developer discount long winded post or something they are not experiencing? If they know there is a bug its in the OP.
If you guys can change the interwebz & how 500 post per update are made completely useless please feel free to do so....
swehes said:
So looked into the Wiki for the Vibrant and have updated some information. Let me know what you guys think. Is this the way to go?
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S_SGH-T959#ROMs
Click to expand...
Click to collapse
I think it's a pretty awesome start for sure
As a matter of personal taste, I think having an individual wiki page per ROM (with the known issues and other detailed info) might be nice, although I'm not sure what the policy on new pages is with the XDA wiki.
Speaking from professional experience, the most challenging aspect of any documentation system is always convincing people to use it. It's great to compile the information, but unless ROM builders and devs post a link to the wiki in the forum threads nobody will ever see it. Having good, community based documentation is a benefit to everybody though, so hopefully people will recognize the utility of it and encourage its growth!

ROMs ROMs and more ROMs

Can someone tell me whats up with the 50+ ICS ROMs? It's a bit concerning that all this effort seems to be put into reproducing the same exact thing. I think the community would benefit from cooperation rather than competition... But I feel like I must be missing something here, I am new to the Nexus S but not to Android, is there something about the Nexus S community that I'm not getting?
Not complaining at all, or should I say, I'm not trying to complain. I also want to point out that I appreciate the developers who pour their time and effort into our devices and help us to get the maximum value out of them.
(Want to note, I am running AOSP's ICS build and loving it.)
joenathane said:
Can someone tell me whats up with the 50+ ICS ROMs? It's a bit concerning that all this effort seems to be put into reproducing the same exact thing. I think the community would benefit from cooperation rather than competition... But I feel like I must be missing something here, I am new to the Nexus S but not to Android, is there something about the Nexus S community that I'm not getting?
Not complaining at all, or should I say, I'm not trying to complain. I also want to point out that I appreciate the developers who pour their time and effort into our devices and help us to get the maximum value out of them.
(Want to note, I am running AOSP's ICS build and loving it.)
Click to expand...
Click to collapse
Hey Man, I am much similar to where you are right now. I am not new to Nexus S or Android, but I feel that the abundance of ROMs is a good thing.
Having so many ROMs shows that the device is still running very strong: Something Android phones NEED to have behind them.
On the other hand I dislike it. To all the developers out there, I think you guys are amazing and genius no doubt. So take the following lightly...
What people don't like to see when browsing for a ROM is a dozen ROMs that are all identical. We need something new and fresh, hence why I like MIUI.
What I think should be done is as you said, have co-operation to make one master ROM because we have hundreds of people in the Nexus S community ready to help.
Speaking on my behalf I HATE SO MANY ROMs Because I simply cannot decide which is best because they are all similar in many ways, and I don't have time to try each one out as much as I want to. I do like having these ROMs but when it comes to choosing one its a big choice for me.
Any feedback on this?
I agree with a not so great abundance or ROMs. But most are not devs. They are simply "chefs" because they never actually developed anything. They just price and scrap things from source to mods. Cm9, ASOP, Peter A(because of his radios and kernal) are devs. We have lots of chefs.
I made brickROM just because of this situation. Its never been done, but the community wasn't ready for it yet.
Either way you can tell what rom has Is "real" I would say there's about only 5
And its sad for new Android users that come here get presided by a catching slogan and rob themselves from using a much better rom
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
What would you do if you don't like any of the existing ROMs? May be one is missing a feature you need, another just has too many features you don't want? The answer is simple -- create your own ROM, or modify an existing one... I think most devs just make the ROM they want to use as their daily driver and simply share it here (i.e. what's going on is not about competition, at least from my point of view)
It sounds good to gather all devs to create a ROM that suits everyone's needs, but IMHO it is nearly impossible to do that
suksit said:
What would you do if you don't like any of the existing ROMs? May be one is missing a feature you need, another just has too many features you don't want? The answer is simple -- create your own ROM, or modify an existing one... I think most devs just make the ROM they want to use as their daily driver and simply share it here (i.e. what's going on is not about competition, at least from my point of view)
It sounds good to gather all devs to create a ROM that suits everyone's needs, but IMHO it is nearly impossible to do that
Click to expand...
Click to collapse
But these futures found in everyone's ROM are just mods that you can flash. I flash 8 zips with every rom update but I know that a personal mix so I have no need to share it.
I'm capiale of changing my waklppaer
I flash custom font, and inverted apps with some tyranny Widgets and kernal. With gnex sounds. No reason to "cook" it. This is not development.
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
Reserved
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
suksit said:
It sounds good to gather all devs to create a ROM that suits everyone's needs, but IMHO it is nearly impossible to do that
Click to expand...
Click to collapse
The CyanogenMod team pull it off quite well, all that is needed is a bug tracker and patch review system and boom! instant cooperation.
Maybe we have too many "chefs" in the kitchen
joenathane said:
The CyanogenMod team pull it off quite well, all that is needed is a bug tracker and patch review system and boom! instant cooperation.
Maybe we have too many "chefs" in the kitchen
Click to expand...
Click to collapse
I am agree with you CyanogenMod need a bug tracker for CM9.
Here is an interesting fact in case anyone didn't know but MR. Cyanogen himself is rocking a Nexus S http://twitter.com/#!/cyanogen/status/153353404159234049
I wonder what build of ICS he is running, probably from his own private reserve...
joenathane said:
The CyanogenMod team pull it off quite well, all that is needed is a bug tracker and patch review system and boom! instant cooperation.
Maybe we have too many "chefs" in the kitchen
Click to expand...
Click to collapse
I will be honest here and say that I personally dislike Cyanogen Mod for the most part. True that they are the gut best in performance, but if the only ROM I had was Cyanogen, I would not be very happy with it. I just think that for my favor, Cyanogen focus' so much on power, yet takes the look of the ROM as a after thought. The modified music on Cyanogen ROMs and the overall execution of his work lacks style and design, as if he first said "Make it fast, then maybe make it look ok" MIUI on the other hand has a great deal invested in how it looks which gives a very effective illusion of performance.
I think that the problem is we have so many chefs in that small kitchen and they have all made so many great dishes that sooner or later they will have eventually all used the same spices by some point, so we are beginning to lose that uniqueness in each one.
LGIQEXPO said:
I will be honest here and say that I personally dislike Cyanogen Mod for the most part. True that they are the gut best in performance, but if the only ROM I had was Cyanogen, I would not be very happy with it. I just think that for my favor, Cyanogen focus' so much on power, yet takes the look of the ROM as a after thought. The modified music on Cyanogen ROMs and the overall execution of his work lacks style and design, as if he first said "Make it fast, then maybe make it look ok" MIUI on the other hand has a great deal invested in how it looks which gives a very effective illusion of performance.
I think that the problem is we have so many chefs in that small kitchen and they have all made so many great dishes that sooner or later they will have eventually all used the same spices by some point, so we are beginning to lose that uniqueness in each one.
Click to expand...
Click to collapse
The only problem with that is Miui uses CyanogenMod code as a base(http://en.wikipedia.org/wiki/MIUI#Development) and CyanogenMod 7 has the theme chooser integrated for easy themeing(check the last three links in my signature to see some themes I created for it).
I don't think any mod team have contributed more to Android than the CyanogenMod Team, they certainly have my respect for that.
I agree about the spices, all these chefs cooking the same exact entree and now which on to choose...
joenathane said:
The only problem with that is Miui uses CyanogenMod code as a base(http://en.wikipedia.org/wiki/MIUI#Development)
Click to expand...
Click to collapse
It's a fact, not a problem.
Back on topic,
LGIQEXPO said:
I think that the problem is we have so many chefs in that small kitchen and they have all made so many great dishes that sooner or later they will have eventually all used the same spices by some point, so we are beginning to lose that uniqueness in each one.
Click to expand...
Click to collapse
I believe at some point the community will decide which dishes live and which will die. I don't think people will keep posting ROMs if nobody uses it.
suksit said:
It's a fact, not a problem.
Back on topic,
I believe at some point the community will decide which dishes live and which will die. I don't think people will keep posting ROMs if nobody uses it.
Click to expand...
Click to collapse
This^^ plus one thing, good all these chefs are popping up, that's showing a swell in number of people interested in development, in the end it can only have a positive outcome. Let em dev.
Sent from my Nexus S 4G using Tapatalk
suksit said:
It's a fact, not a problem.
Click to expand...
Click to collapse
I obviously didn't mean problem in that sense, I meant it as in the 'problem' with his argument not the problem with CyanogenMod or Miui, I'm not sure how you interpreted it the way you did...
suksit said:
I believe at some point the community will decide which dishes live and which will die. I don't think people will keep posting ROMs if nobody uses it.
Click to expand...
Click to collapse
what about the "noobs" who are instantly confronted with 20+ ICS ROMs and not a clue to which is worth its weight in salt?
joenathane said:
I obviously didn't mean problem in that sense, I meant it as in the 'problem' with his argument not the problem with CyanogenMod or Miui, I'm not sure how you interpreted it the way you did...
Click to expand...
Click to collapse
Sorry if I interpreted it wrong (English is not my native language anyway ) I thought you're trying to imply that "since MIUI is based on CM, @LGIQEXPO shouldn't compare them together" or "if you like MIUI, it means you already liked CM." Just wanted to say that it is not a problem if one wants to compare those two.
joenathane said:
what about the "noobs" who are instantly confronted with 20+ ICS ROMs and not a clue to which is worth its weight in salt?
Click to expand...
Click to collapse
Occasionally I'd see a thread titled "Help me decide which ROM is best" and the most popular answer would be "Why don't you try them all?" Yeah it would be madness to try all 20+ ROMs in a row, but I don't think anyone will do that.
Before flashing a ROM, I'd (suggest them to) read everything in the first few posts by the OP, and take a look at the screenshots (most of the time I can decide if I will like this ROM or not by these two factors) If those "noobs" are not too ignorant I believe they'll have a small list of ROM(s) they want to try (may be 4-5 choices, which is reasonable.)
I know it is on the same code, but I more so meant the apps that MIUI re-did for their ROMs, and how they offer a nice end user appeal.
What would be amazing is if all the known devs of these ROMs would just once come together to use their own strengths, and make a mast ROM out of it. MIUI Design and style, Cyanogen tweaks and speed, Peter A. stability, the overclocking everything! (I can't wait for that hahah )
you want fewer rom, get a ns4g. Although we only have a fraction of the roms found in the other forum, they all seem to have their own distinct character.
i was using an SII before this so i was a frequent on that part of xda.. they do have a separate page for original development and another one for development (being kitchen products)
Hey,
Just wanted to add my opinion in all of this that there are so many "equal" roms.
I as some mentioned on another thread am a chef to rom developing, and I don't mind.
Why I do this is because I don't have the time or knowledge to create Android source apps so I take what I think is the best from each rom and create my own.
For example for me CM9 is way to bloated with too many configurations and options I prefer a more real cleaner AOSP, something like Peter Alfonso (buglessBeast), but I do like the T9 dialer from CM9, so I cherry-pick that from CM9 and add it to a PA base.
Also for the notifications power menu I liked TeamKang one so I added that. That way I'm making my own custom rom to my liking and also I don't have to be flashing 20 zips every time there is a new update or wipe my phone
I just thought on sharing it just if some one has the same likes in roms I'm no asking for anything in return. Also I do this in my little free time.
Sent from my Nexus S 4G using XDA App
mandaman2k said:
Hey,
Just wanted to add my opinion in all of this that there are so many "equal" roms.
I as some mentioned on another thread am a chef to rom developing, and I don't mind.
Why I do this is because I don't have the time or knowledge to create Android source apps so I take what I think is the best from each rom and create my own.
For example for me CM9 is way to bloated with too many configurations and options I prefer a more real cleaner AOSP, something like Peter Alfonso (buglessBeast), but I do like the T9 dialer from CM9, so I cherry-pick that from CM9 and add it to a PA base.
Also for the notifications power menu I liked TeamKang one so I added that. That way I'm making my own custom rom to my liking and also I don't have to be flashing 20 zips every time there is a new update or wipe my phone
I just thought on sharing it just if some one has the same likes in roms I'm no asking for anything in return. Also I do this in my little free time.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Thanks for adding your voice to the discourse.
If I was asked to offer an opinion on what you do, this is what I would say....
I think what you do is okay for you, but the problem is when you release it. There is a problem because as you state, you cherry pick features and/or "code" from other ROMs, and that can/will lead to issues for your user base. Lets take for example the T9 dialer, what happens when security bugs are found and fixed and optimizations make it into an update of the T9 dialer? Well that would mean you would need to update your ROM, but what if you're busy with your job or just with life and are too busy to get around to it? Well now your users of your ROM are without those security, bug fixes and optimizations, and multiply that by all the other pieces of the ROM that you cherry picked from other sources.
My point here to be clear is that due to the nature of your ROM, it will always lag in patches to security issues, bug fixes and optimizations and I think that is ultimately a disservice to your user base.
There is a value that you create, so I guess the question here is, does that value of bringing all these pieces into one convenient package outweigh the negatives of the lagging patches/fixes?
I mean no offense, and I hope this isn't taken as such, I just want to encourage some discourse on these things...

Best ROM

hi all,
i might be getting a new s2 soon, so i was wondering what rom would you recommend
thanks
Try some and decide.
This question is subjective, has been asked too many times, pisses the mods off and may well be locked by a mod.
No short cuts unfortunately.
There's no best rom. Because nobody uses their phone the same, nobody's phone is setup the same and because no two phones come out of the factory the same.
I can almost guarantee you won't have the same experience with a particular rom or kernel for those reasons.
If you do get an SGS2, try out a bunch of roms until you find one that has the features you want & works well for you.
There should be a dedicated thread which we can link to whenever we see a post regarding 'best rom'. As people have said you need to try them as everyone has there own views.
I normally end up trying 3 or 4 before deciding and well worth reading the rom thread before trying.
How many of these Stupid Best Rom Posts do we have to DELETE before they get the message Jeez
THREAD CLOSED

[Q] What rom do you prefer?

Tell me a little about what rom your prefer and why? List some pros, cons, notes, anything that may be helpful.
I myself am looking for a rom with lots of features, free ram, regularly updated, little/no bugs. But I'm very curious to see what you guys have to say and what the community prefers.
I'd be careful with this topic it can be seen as best/better rom thread which is frowned upon
xstokerx said:
I'd be careful with this topic it can be seen as best/better rom thread which is frowned upon
Click to expand...
Click to collapse
Yes I know, I'd like to know what people are using and what they prefer. When talking about roms the word 'best' is usually subjective which is why I'm looking for preference
I'm also very interested in this too, I've been out of the loop for a really long time now, and I don't even know where to start at all. So I'd love to hear peoples' input on which (lollipop specifically) roms are good/well rounded/most stable.
Numerics said:
I'm also very interested in this too, I've been out of the loop for a really long time now, and I don't even know where to start at all. So I'd love to hear peoples' input on which (lollipop specifically) roms are good/well rounded/most stable.
Click to expand...
Click to collapse
Maybe someone will chime in and tell us what they have and if they like it
I've used a variety of ROMs and I'm personally partial to cyanogenmon based ones. Lots of customizing options and much faster than TouchWiz.
But then again I'm probably one of the few with a MDL bootloader.

Categories

Resources