Database Users

Niefs Rom Comparison

additional details on test:
The first part of the table is to test the rom with the stock kernel.
The second part is to see how well it performs oc/uc.
This is supposed to show how well a ROM performs by itself and how well it works while oc/uced since a lot of us do use custom kernels.
On all of the tests, there should be no widgets or apps installed that didn't come preset with rom(excluding setCPU, fps2d,quadrant, and linpack). This should help eliminate variability of what apps different users have.
On all the test (performance or battery) if the rom has preset profiles they can use them as long as it doesn't require a reboot or any 3rd party apps. all these profile should be mentioned though in additional notes.
I said no profiles on the battery test, meaning no setCPU profile due to variability of profiles.
All ROMs will be using sense except CM6
Update 8/6: Updated the spread sheet and put it up and google docs Niefs Rom Comparison
There are now explanations of the tests and I am going to start testing today. Also, looking for testers.
I have posted my scores for part of Fresh.
update: 8/12
Most ROMs are completely filled out under features
Most performance test have been ran
Few battery tests
http://i996.photobucket.com/albums/af90/nief1313/test.jpg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I think it will be a great idea... google docs might be a good way to let people collaborate, otherwise some kind of wiki.
Might be easier to organize by features such as "stripped of sprint apps" or "added X app" vs things like battery and performance which can sometimes be highly variable by device. Also, if you run performance I would maybe do a baseline of 998mhz (since we all know we can hit this clock) and then another showing oc'd (since some people can barely OC one tick).
I think there are enough people across all the roms that if the spreadsheet were public you'd gather a lot of data. I also have NAND backups of a few of the froyo roms so it wouldn't be hard to boot into recover, reflash a nand, run the benches, then reflash back to whatever i was on.
The battery ones will be a little tough #1 cuz i'm not sure how many people wanna completely lock up their phone for several hours waiting to see how long it lasts. #2, depending on how some people's batteries are calibrated and what they're running in the background, MMV.
Great idea tho!!! I think the ultimate key is thinking of a good way for everyone to easily submit their data. Anyone have suggestions?

u could add it to our wiki and update it like monthly. idk just an idea

Looking forward to it
This is a great idea, and i look forward to seeing this list grow. This could really help someone new to Android like me.

toastcfh said:
u could add it to our wiki and update it like monthly. idk just an idea
Click to expand...
Click to collapse
I think adding it to the wiki would be really nice. I will try to come up with a spread sheet that only a few can edit(I don't want one person to delete or mess up all the data). I rather have were people pm there scores and other data so i can add it in.
I will finish tweaking on how to tests and how the spreadsheet will look tomorrow.

You should add 2 additional categories:
Does WiFi Tethering work with 3G speeds Y/N
if yes, which version of Wifi Tethering
Does WiFi Tethering work with 4G speeds Y/N
if yes, which version of Wifi Tethering

rek410 said:
You should add 2 additional categories:
Does WiFi Tethering work with 3G speeds Y/N
if yes, which version of Wifi Tethering
Does WiFi Tethering work with 4G speeds Y/N
if yes, which version of Wifi Tethering
Click to expand...
Click to collapse
I have just added that to the spreadsheet, the versions will be written down in the additional notes. Also, i just posted the link to the spreadsheet in the OP. I will be looking for testers if anyone is interested to help.

nief, im running EViO 2 V1.0.2
ill post results for you later.

nenn said:
nief, im running EViO 2 V1.0.2
ill post results for you later.
Click to expand...
Click to collapse
Sweet thanks for the help.

Which version of CM6 were you going to test? RC1 is getting pretty old, a lot of us are using nightlys. RC2 should be out soon though.

OgremustCrush said:
Which version of CM6 were you going to test? RC1 is getting pretty old, a lot of us are using nightlys. RC2 should be out soon though.
Click to expand...
Click to collapse
I was planning on testing RC1... at least until RC2 has been released.
if some one wants to do the tests for a nightly build, i will gladly add another row

I noticed you had an over clocked set to test performance but for battery you have it set not to test profiles for example in battery. this can be a huge disadvantage for some roms (ie DC has profiles for performance and battery that can make a huge difference int here DConfig.) also the kernels can greatly affect these. If we wanted to actually test the rom shouldn't we be testing these with either 1 the same kernel for all or their stock kernels?
for example someone using the stock Fresh kernel may have vastly different results then someone using netarchy's kernel. this would provide skewed results for the rom test.
Same goes for Baked Snacks since there are several kernel options. if using the performance kernel for the performance test then switching to battery saving for battery saving test you will get results showing unachievable results.
I think this is a great idea but if this is going to happen i think "guidelines" should be used so that the data is as close to comparable and accurate as possible. what do you think?
something like
1) for testing purpose you should use the stock kernal with the rom for all tests.
2) with the exception of the OC tests you can not be running setCPU or any other under/overclock programs.
3) the following settings should be used. <list some basic settings>
4) if your rom has built in profiles settings that do not require a reboot or flashing anything you CAN use them.
5)etc
6)etc
If we dont have guidelines i think the results will very greatly on settings and kernel.
Even with doing the above you will still have a decent variance from usage/apps/widgets but at least this would make it as close to a level playing field and testing of the rom itself rather then the kernel/settings/who has what in setcpu

omegasun18 said:
I noticed you had an over clocked set to test performance but for battery you have it set not to test profiles for example in battery. this can be a huge disadvantage for some roms (ie DC has profiles for performance and battery that can make a huge difference int here DConfig.)
Click to expand...
Click to collapse
I agree. Using performance profile for the performance test and then battery profile for the battery test will lead to skewed results. Perhaps what should be done is to test each profile against all tests. So you might have DC/Performance Profile and DC/Battery Profile with results for every test. This would tell you how well the battery performs under the performance profile or how well the rom performs under the battery profile.

omegasun18 said:
I noticed you had an over clocked set to test performance but for battery you have it set not to test profiles for example in battery. this can be a huge disadvantage for some roms (ie DC has profiles for performance and battery that can make a huge difference int here DConfig.) also the kernels can greatly affect these. If we wanted to actually test the rom shouldn't we be testing these with either 1 the same kernel for all or their stock kernels?
for example someone using the stock Fresh kernel may have vastly different results then someone using netarchy's kernel. this would provide skewed results for the rom test.
Same goes for Baked Snacks since there are several kernel options. if using the performance kernel for the performance test then switching to battery saving for battery saving test you will get results showing unachievable results.
I think this is a great idea but if this is going to happen i think "guidelines" should be used so that the data is as close to comparable and accurate as possible. what do you think?
something like
1) for testing purpose you should use the stock kernal with the rom for all tests.
2) with the exception of the OC tests you can not be running setCPU or any other under/overclock programs.
3) the following settings should be used. <list some basic settings>
4) if your rom has built in profiles settings that do not require a reboot or flashing anything you CAN use them.
5)etc
6)etc
If we dont have guidelines i think the results will very greatly on settings and kernel.
Even with doing the above you will still have a decent variance from usage/apps/widgets but at least this would make it as close to a level playing field and testing of the rom itself rather then the kernel/settings/who has what in setcpu
Click to expand...
Click to collapse
I agree with a baseline but there should also be a performance test done where you have it maxed to the peak and state the battery life you'd get with those settings and numbers.
......
now that I think about it....
Really in the end we are speaking real world examples here and itd be best to just have the results state what rom, what kernel, and what settings you had to get "X" results and then go form there.
I dont care if DC is better on stock kernal and settings than BS. I'd rather know what settings in BS yield what results for people and the same for any other rom.
With the number of changes the dev's put in the roms doing baselines against them is kinda pointless as they might each take advantage of certain things differently. It'd be best to just notate the results for each post and state the changes made to yield the results so people can get more real world conclusions.

sgt. slaughter said:
I agree with a baseline but there should also be a performance test done where you have it maxed to the peak and state the battery life you'd get with those settings and numbers.
......
now that I think about it....
Really in the end we are speaking real world examples here and itd be best to just have the results state what rom, what kernel, and what settings you had to get "X" results and then go form there.
I dont care if DC is better on stock kernal and settings than BS. I'd rather know what settings in BS yield what results for people and the same for any other rom.
With the number of changes the dev's put in the roms doing baselines against them is kinda pointless as they might each take advantage of certain things differently. It'd be best to just notate the results for each post and state the changes made to yield the results so people can get more real world conclusions.
Click to expand...
Click to collapse
The thing is if you do what you suggest .. you arent comparing each roms performance really. If this is supposed to be used as a sort of guide for people to compare the roms themselves then what you said doesnt make sense since it adds a large a mount of varibales tot he "tests". Now if we are trying to compare complete packages and find what works best sure i agree with you completly. however i would not consider that to be comparing roms. which is what the origonal intent LOOKS to be.
When you are trying to compare things to get the most accurate results you compare them in as close to the same conditions and set up as possible. The more you differentiate the things you are comparing the more aspects can influence the results and the more skewed or inaccurate the results are.
If you have extremely random results based off a wide variety of conditions then the results lose there usefulness. In this case if we are trying to test ROMS then we should try to single out the roms and get them as close tot he same footing as we can so we can compare the ROMS and not the tweaks everyone can do. Maybe having another table or thread comparing different settings and tweaks and kernels would be helpful as well?
By stock kernel i mean the stock kernel that comes with each rom. The devs tweak these and make changes to give better performance/battery. I dont mean the stock as in the original froyo kernel. I also disagree that this isnt real world examples. I think it is exactly what it is however it takes out individual tweaks from the user and tries to keep everythign as close to level as possible to yield the best TEST results

Still going to say these will be nice but not what people will be looking for. So what if BS beats out DC outa the box in terms of bat life and performance. Thats nice and all but if you could show that with a few tweaks with set cpu and other things included in the rom that that DC greatly outperforms BS then its completely different.
What really needs to be done is what we both are saying. one done stock with the included kernel with the rom(or whatever the developer suggests using), and then one where users can make there tweaks and post those results.
If I just knew that one rom had better battery life stock and didn't know that I could possibly use a different rom that with a few tweaks gets better battery life and performance I'd rather use the later. Some roms perform differently than others with regards to tweaks being done by the user.
I'd stress that two tests be done, one with stock rom with stuff loaded form the dev's page only, and then one done with tweaks by the user and state the results so we can really get an idea what rom is best at what performance wise at least.

I was wondering if there would ever be something like this!! Great job!!! ...just on the side note, is there anyway to put the features working on the left side closer to the rom? i know a lot of users who care more about working features than technical stuff (linpack etc). I too would love to see this on the wiki!
**edit: also, maybe consider adding kernel box so we can see which kernel is being used w/ which rom and working features etc.

The first part of the table is to test the rom with the stock kernel.
The second part is to see how well it performs oc.
This is supposed to show how well a ROM performs by itself and how well it works while oced since a lot of us do us custom kernels.
On all of the tests, there should be no widgets or apps installed that didn't come preset with rom(excluding setCPU, fps2d,quadrant, and linpack). This should help eliminate variability of what apps different users have.
On all the test (performance or battery) if the rom has preset profiles they can use them as long as it doesn't require a reboot or any 3rd party apps. all these profile should be mentioned though in additional notes.
I said no profiles on the battery test, meaning no setCPU profile due to variability of profiles.

adeyo said:
I was wondering if there would ever be something like this!! Great job!!! ...just on the side note, is there anyway to put the features working on the left side closer to the rom? i know a lot of users who care more about working features than technical stuff (linpack etc). I too would love to see this on the wiki!
**edit: also, maybe consider adding kernel box so we can see which kernel is being used w/ which rom and working features etc.
Click to expand...
Click to collapse
There is a kernel box already there, its to the very right. THis is the custom kernel used during the oc test.

nief1313 said:
The first part of the table is to test the rom with the stock kernel.
The second part is to see how well it performs oc.
This is supposed to show how well a ROM performs by itself and how well it works while oced since a lot of us do us custom kernels.
On all of the tests, there should be no widgets or apps installed that didn't come preset with rom(excluding setCPU, fps2d,quadrant, and linpack). This should help eliminate variability of what apps different users have.
On all the test (performance or battery) if the rom has preset profiles they can use them as long as it doesn't require a reboot or any 3rd party apps. all these profile should be mentioned though in additional notes.
I said no profiles on the battery test, meaning no setCPU profile due to variability of profiles.
Click to expand...
Click to collapse
Thanks for clearing up what your vision for this is.
sgt slaughter. I agree with a lot of your points. I think 2 sets could be done to better show a variety of results. I was simply arguing the merits of doing a rom specific test comparison vs a complete setup specific comparison. You are right that different roms react differently to different tweaks that was the point. BUT not only do different roms act differently, different evos with the same everything react differently to different tweaks and settings. Thus just because user A get these results doesnt always mean User B will too. that's why i thought baseline would be a better gauge on the roms themselves.

SGS2 ROM Shoot-out and comparison

Hi All
We have decided to build a comparative list of Rom for comparison. ROM's will be measured by the testers on 5 categories and hopefully we could get a honest opinion from the testers and not just a 5/5 for everything because they are a fanboy ...
ROM's will also be divided into 3 specific categories. Stock (Stock ROM provided from Samsung via update in Kies), Custom Original (Original ROM's by Dev's), Kitchen (Custom Original ROM's cooked and tweaked to perfection by a other Dev)
When providing us feedback on the ROM's please do so in the format below so we could add them to the corresponding list and add them to the graph that will follow in the 3rd Post.
Please try to be as Objective as possible. No point in having everything score 5/5
ROM Name goes here - By Tester
Version of ROM:
Android Version:
ROM Date:
Rom Type:
UI flexibility:
Common Bugs:
General user Experience:
Browser "html5test.com":
Browser Experience:
Link to ROM:
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed:
Setup:
Connectivity:
Look and feel:
Theme'ing:
If you feel the information provided is not accurate please just specify witch ROM you are referring to and what information is not correct as below and then a reason as to why you say so.
Stock Rom
Version: Actually 2.3.5
Reason for Edit: Made a typo when I submitted the rom information
This will help us to update the list timeously and accurately.

Stock Roms
I9100XFA - By Toxicdust
Version of ROM: N/A
Android Version: 2.3.4
ROM Date: 9 Sept 2011
Rom Type: Stock
UI flexibility: Portrait only with no lag at all. Lag presents itself in the application drawer when running a custom launcher with a live wallpaper
Common Bugs: N/A
General user Experience: Everything works as intended, TW is quick as usual with no laggy transitions or any lag in the Application drawer even when a live wallpaper is present.
Browser "html5test.com": 182 plus 1 bonus point
Browser Experience: Quick browsing. Switching tabs sometimes present a bit of Lag.
Link to ROM: N/A
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed: 4.5
Setup: 3.5
Connectivity: 4.0
Look and feel: 3.0
Theme'ing: 0.1 - No built in theme support
Custom Original
Rarity Rom by lilbrat
Version of ROM: v3.85, although at the time development was halted I believe it was up to 4.2 or 4.5
Android Version: 2.3.5
ROM Date: Nov 2011
Rom Type: Custom Original
UI flexibility: Works well with both TW and after markets (currently using Go Launcher EX)
Common Bugs: none
General user Experience: Works very well and very stable though I'm an average user I haven't upgraded to any of the newer kernels or other things for me it works just fine. Battery life is ok ..average 2 days but like I said I'm an average user..few phone calls,sms..wifi and gps occasionally, Bluetooth for headset when I'm out..
Browser "html5test.com": Dolphin HD 7.3.. 182 plus 1, Firefox (Aurora) while still very new (beta with nightly updates..buggy) 318 plus 9
Browser Experience: It works well with Dolphin, and YouTube Facebook ect.
Link to ROM: Development currently has been halted..
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed: 4
Setup: 3.8 takes a while to set up..
Connectivity: 5
Look and feel: 4.3
Theme'ing: 3.5 you need to try different things out that you want to add some things work some don't..
ROM Name goes here
Version of ROM:
Android Version:
ROM Date:
Rom Type: Custom Original
UI flexibility:
Common Bugs:
General user Experience:
Browser "html5test.com":
Browser Experience:
Link to ROM:
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed:
Setup:
Connectivity:
Look and feel:
Theme'ing:
Kitchen
ROM Checkrom revoHD v4 - By adamski123
Version of ROM: v4
Android Version: 2.3.6
ROM Date: latest update feb 8th (new kitchen) v6 coming soon.
Rom Type: Kitchen
UI flexibility: stock touchwiz. Nice and smooth.
Common Bugs: None known of
General user Experience: In my eyes best gingerbread rom. Fast and stable with the option to mod and tweak via the kitchen app.
Browser "html5test.com": i got 182 but i don't recommend taking that score to seriously
Browser Experience: Standard Samsung browser, good and fast, but tab support could be better.
Link to ROM: Will link when I get near a comp.
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed: 4.8
Setup: 4.0
Connectivity: 4.0
Look and feel: 4.0
Theme'ing: 4.8
ROM Name goes here
Version of ROM:
Android Version:
ROM Date:
Rom Type: Kitchen
UI flexibility:
Common Bugs:
General user Experience:
Browser "html5test.com":
Browser Experience:
Link to ROM:
Ratings from 0.1 - 5.0 (0.1 being lowest and 5.0 being highest)
Speed:
Setup:
Connectivity:
Look and feel:
Theme'ing:

Graphs as set out as per our criteria. The values given have been converted to account for 20% in each category
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I hope you know enough to make valid comparisons.
Well done for trying

s2d4 said:
I hope you know enough to make valid comparisons.
Well done for trying
Click to expand...
Click to collapse
Well no one else will put in the effort so I will at least try. If there is any suggestions or fields that should be added please feel free to comment.
I will not personally flash to all the roms at all but will rely solely on user feedback to at least get a basic comparison going in the start.

toxicdust said:
Well no one else will put in the effort so I will at least try. If there is any siggestions or fields that should be added please feel free to comment.
I will not personally flash to all the roms at all but will rely solely on user feedback to at least get a basic comparison going in the start.
Click to expand...
Click to collapse
I see..
I was hoping that detailed comparison could be made.
Like themer roms, kanger roms, original dev roms.
Not just ppl with no clue making comments...
for instance, when jkay releases, numerous rom cooks just packages the framework-re.apk (maybe with png changes), plus add whatever other apk mods others have done, add someone's kernel, zip it up and call it a their rom.
or worse, mix and match apks between other releases and call it their own
Special mention needs to be done to differentiate all this between the good guys and the others.
For example, look at what hyperdroid v6 has done.
Without waiting for jkay, incorporated 14 toggles, added edt/ tsm tweaks, and make it play nice with the Hyperdroidparts to control it all.
Adding their own brand new red pill recovery and kernel, and even sharing the recovery with syah for a community collaboration effort.
Multidpi also came from hyperdroid.., smooth spinners tweaks,
updates to vrtheme via surgeons etc.
EDIT: You might want to remove quadrant as that only kills the credibility of the thread.

Well that's the whole thing. I want to list them but only the main players. Not the mix and match ones cause there are literally hundreds of them and they are all the same in 90% of all aspects.
I am editing the 2nd post a lot so refresh on occasion to see if there is something new.
I think I will stick with what we have now in the listed comparisons. If anyone has anything to add feel free and I will just add it to the list of Items.

s2d4 said:
You might want to remove quadrant as that only kills the credibility of the thread.
Click to expand...
Click to collapse
Any suggestions as to a bench to use that's a little more accurate? I have no idea what to use as a bench tbh

AnTuTu is a good bench.

B3311 said:
AnTuTu is a good bench.
Click to expand...
Click to collapse
-Took out irrelevant joke-
Thanks will replace quadrant with that
Anyway ... I think this is what the OP of that thread was looking for.

Sensation 2.0 rom with his own sexy theme...looks all great..and functions buttery smooth....maybe u can add in the list with other ROMS...

Lol ... I am actually trying to find some of the ROM's and cant even find the original threads as there are so many of them for different things.
If someone could link some of the ROM's we need to list or have listed it would be appreciated.

oinkylicious said:
But there's still nothing useful in here, just some vague statement about battery life on a "stock ROM" "Battery Life: 2 Days Moderate use to 5 Days minimal Use" seriously? Or was this part a joke? And no actual mention of which stock ROM the few random statements referred to (besides 2.3.4, which must be pretty old).
I'm actually against the idea of a compilation thread . Sure you might think it'll remove some of the clutter from these forums and daily "best ROM" threads (in all honesty, it won't, the people starting those threads don't read stickies or search), but it'd be quickly outdated and be full of the usual "I think x ROM is best with y kernel because of z".
For a user to get an idea of current ROMs, all it requires is an opening of the development forum(s), pressing CTRL+f, typing [ROM] and ticking "Highlight all" in whatever browser is used. Read first post for changelog/screenshots and making up own mind.
Click to expand...
Click to collapse
I was against the orginal idea too oinky, but it can work. I'll be in contact with toxicdust shortly and we'll get this done - promise.
You know your **** - help us! Send a PM.

oinkylicious said:
But there's still nothing useful in here, just some vague statement about battery life on a "stock ROM" "Battery Life: 2 Days Moderate use to 5 Days minimal Use" seriously? Or was this part a joke? And no actual mention of which stock ROM the few random statements referred to (besides 2.3.4, which must be pretty old).
I'm actually against the idea of a compilation thread . Sure you might think it'll remove some of the clutter from these forums and daily "best ROM" threads (in all honesty, it won't, the people starting those threads don't read stickies or search), but it'd be quickly outdated and be full of the usual "I think x ROM is best with y kernel because of z".
For a user to get an idea of current ROMs, all it requires is an opening of the development forum(s), pressing CTRL+f, typing [ROM] and ticking "Highlight all" in whatever browser is used. Read first post for changelog/screenshots and making up own mind.
Click to expand...
Click to collapse
Valid points. Thanks for the reply. I am using this stock rom but i should have probably added that I have the extended original 2000mah battery.
I do agree to some extent that it might get dated but when someone does a update or does review a new rom it takes 3 min to give your opinion and do a quick bench and just wrote everything down. I know it will take commitment from the community and obviously Dev's would want to boast with the Roms. There is no better way that a shootout for devs to actually go back and work on their rom to get better performance or less bugs ect ect.
Ultimately Users get better roms and there is a little bit of competition between the Devs for brag rights ofc
All in good sport I have to add.

s2d4 said:
I see..
I was hoping that detailed comparison could be made.
Like themer roms, kanger roms, original dev roms.
Not just ppl with no clue making comments...
for instance, when jkay releases, numerous rom cooks just packages the framework-re.apk (maybe with png changes), plus add whatever other apk mods others have done, add someone's kernel, zip it up and call it a their rom.
or worse, mix and match apks between other releases and call it their own
Special mention needs to be done to differentiate all this between the good guys and the others.
For example, look at what hyperdroid v6 has done.
Without waiting for jkay, incorporated 14 toggles, added edt/ tsm tweaks, and make it play nice with the Hyperdroidparts to control it all.
Adding their own brand new red pill recovery and kernel, and even sharing the recovery with syah for a community collaboration effort.
Multidpi also came from hyperdroid.., smooth spinners tweaks,
updates to vrtheme via surgeons etc.
EDIT: You might want to remove quadrant as that only kills the credibility of the thread.
Click to expand...
Click to collapse
since only the quadrant advice was taken, how are you going to differentiate the level of development by the rom makers?

toxicdust said:
Hi All
Seeing as this tread was motivated by some other trolls in a other thread I decided to take it upon myself to build a comparison list of Rom's out there and add their information to it.
This will ofc be a community effort to eliminate noob threads as some call it so for the last time share your collective knowledge and then you can refer all the noobs to this thread every single time.
If you feel the information in this topic is incorrect then please don't throw a hissy fit. Rather just correct it in a post and I will update the 1st post. If you want your rom to feature in this tread also reffer me to your roms page with all the relevant information so that I could find it there to update the tread with.
Please use the following template to Provide information for the ROM's being tested. This would help in getting them all together and tweaking them where needed.
Version of ROM:
ROM Date:
Battery:
Battery Life:
UI flexibility:
AnTuTu Score:
Common Bugs:
General user Experience:
Browser "html5test.com":
Browser Experience:
Link to ROM:
If you feel the information provided is not accurate please just specify witch ROM you are referring to and what information is not correct as below and then a reason as to why you say so.
Stock Rom
Version: Actually 2.3.5
Reason for Edit:
Click to expand...
Click to collapse
I like the effort. Here are my suggestions
1) Categorize ROMS into AOSP, Stock and Mix and compare ROMS within their respective groups. Everyone knows the limitations that AOSP has at the moment.
2) Battery life is highly subjective, your findings might be considered flawed. Rather do a control test on each ROM with a few fixed apps/push/sync that almost everone uses. Post Battery usage and graph for each. You will also have to worry about screen on time.
3) Bench marks are again dependant on kernel, governor, scheduler (Please correct me if im wrong here, but i know that using VR gives better benchmark scores). Unless they are again maintained, a comparison would not prove any point.
Again, please do correct me I am incorrect anywhere.

I am actually very impressed with whats happening here.
Respect to all of you.
*post may be removed*

s2d4 said:
since only the quadrant advice was taken, how are you going to differentiate the level of development by the rom makers?
Click to expand...
Click to collapse
That's why I need people like you to help and define what is needed so we can get relevant information.
jayerfernandes said:
I like the effort. Here are my suggestions
1) Categorize ROMS into AOSP, Stock and Mix and compare ROMS within their respective groups. Everyone knows the limitations that AOSP has at the moment.
2) Battery life is highly subjective, your findings might be considered flawed. Rather do a control test on each ROM with a few fixed apps/push/sync that almost everone uses. Post Battery usage and graph for each. You will also have to worry about screen on time.
3) Bench marks are again dependant on kernel, governor, scheduler (Please correct me if im wrong here, but i know that using VR gives better benchmark scores). Unless they are again maintained, a comparison would not prove any point.
Again, please do correct me I am incorrect anywhere.
Click to expand...
Click to collapse
1. I could split it into the 3 groups and then categorize it accordingly. @s2d4 - would this help or do you think there should be better defined sections for them?
2. Agreed. There are a lot of variables that could make the test vary in results and it is very subjective. Could you give more detail as to what we should be seeing rather then Battery life.
3. If that is true we it could still be useful to the extent of determining if the rom is high in performance or rather a battery saver. I truly think if its the fastest out there it will consume the most battery doing so as well. Although that is subjective but could be relevant.

jayerfernandes said:
I like the effort. Here are my suggestions
1) Categorize ROMS into AOSP, Stock and Mix and compare ROMS within their respective groups. Everyone knows the limitations that AOSP has at the moment.
2) Battery life is highly subjective, your findings might be considered flawed. Rather do a control test on each ROM with a few fixed apps/push/sync that almost everone uses. Post Battery usage and graph for each. You will also have to worry about screen on time.
3) Bench marks are again dependent on kernel, governor, scheduler (Please correct me if im wrong here, but i know that using VR gives better benchmark scores). Unless they are again maintained, a comparison would not prove any point.
Again, please do correct me I am incorrect anywhere.
Click to expand...
Click to collapse
Thanks for the suggestions.
Sent a PM to toxicdust, hope the hatchet is well and truly buried (and not in anyone's cranial matter either...). But he's the boss - his idea AFAIC.
1 - Agree completely. I haven't and won't try any CM9/MIUI ROMs, and am not interested in ICS before an official release. Any help/reviews/feedback would be hugely appreciated here.
2 - Agree. Too subjective to bother with, IMO. Forgot to ask toxicdust about this. If you're there toxic, what do you think? Trouble with your suggestion is the subjectivity of "apps everyone uses". For example, I'm the only person on this planet who isn't on Facebook or Twitter, doesn't use Google Maps, and I don't use e-mail on my phone - I don't want to be available to all and sundry 24/7. I'm pretty sure I don't fit a "usual user" profile.. But hey! I'm special... Suggest a list of apps that you think the majority use, and we'll try to collate battery stats from there. Good?
3 - I want to drop benchmark scores completely. Individual use etc makes it too subjective for me, and the last thing a noob needs is seeing a score - "oooohhhh! 3045060604+3 on Quadrant! This must be the ROM for me, lolz"...
Keep the ideas coming.
Gotta swallow my pride - which I do gladly - and admit that this is a damn good idea - we've just got to do it properly.
I can't theme and I can't code - but this ensures I'm doing something for the community.
I can write though
OFF TOPIC
By the way - I've got no problem with the removal of many of my posts on this thread- would just like to know who's doing it?
I realise that I'm not owed an explanation, and I'm not asking for one either - this isn't a democracy, as I've posted myself at least 40606003 times.
I'm not sending a general PM to all mods, so can the mystery mod please PM me?
Once more, I'll stress that I have no problem with you guys deleting - just curious.
Thanks.
Bets $1213256990 that I won't get a reply
---------- Post added at 08:19 PM ---------- Previous post was at 07:56 PM ----------
OmegaRED^ said:
*post may be removed*
Click to expand...
Click to collapse
Know the feeling. Mine are disappearing quicker than Lord Lucan.
I'm pretty sure it's a mod on a grassy knoll with a sidekick in the book depository. I just can't prove it yet

B3311 said:
Thanks for the suggestions....just can't prove it yet
Click to expand...
Click to collapse
To much to quote. Agree on your suggestions I will fix the 1st posts quick. I sent you a PM back.
I reported all the Posts with a "Post not relevant to topic" So that the posts could get deleted Wanted to Start this tread properly and that would just have brought everyone down in any ways

[Q] Brief discussion regarding Paranoid Android 3.1 on the Nexus 7

I looked around for a Paranoid Android catch-all or general forum and I only seem to find the threads for specific devices.
Since I'm debating whether to install PA3.1 on my N7, I thought this should be a good place to start as any.
I apologize if this thread clutters the General discussion thread.
So after watching this video of how PA3 performs on the Nexus 10;
I was really eager to install PA on my Nexus 7. Then I saw this video
and decided I could really use the collective XDA knowledge to make a more informed decision.
so here's a battery of questions.I know how entitled if sounds, but I would really appreciate any input about these questions.
Full tablet UI. I don't like the Nexus 7 stock UI in landscape with the icons on the side. I would much rather have the icons on the bottom, like the Nexus10 UI has them. Will one of the PA3.1 UI's modes enable this?
I'll pass on pie. I know it's optional, which is good because I don't really think I'll be comfortable. Actually, I've seen some videos and everybody is using the notifications on the bottom. Is this optional? I would really like to have both pull down menus remain at the top.
How's the battery life? the threads seems to praise the m-kernel in general, but I'm curious about the franco kernel and if there's any benefit over the m-kernel while on PA3.1.
Actual performance. Nexus10 with PA3.0 is blazing fast. The pinch-zoom action in the video had me drooling. Then I saw the videos of the Nexus 7 and notice it's not as fast.I know we're talking about completely different hardware, but I wanted to get a consensus. Does going from stock ROM to PA3.1 on the Nexus 7 improve performance? Apps, battery, wifi, animation smoothness, etc.
Latest "stable" version. I see that the PA3.1 thread for N7 has the "Nightly" term in the title. I'm happy to help with the Q&A process, but I would like to know on which PA3.1 version I can fall back on (even 3.0, should that be the case). Any recommendations?
again, sorry for the handholding, but I appreciate any and all input.

Yes, the icons will remain on bottom if that is the ui you choose. It is indeed solod and fast using m-kernel. As far as franco kernel, that is something youll have to test. You can get a consensus, but different people use different options. Your experience may vary. The answer you will get repeatedly is "flash it and try it out", because that is the right answer. Nandroid in twrp or cwm, and load pa and test. Personally, I use multirom because i can test all the roms without losing my functional rom.
Sent from my Nexus 7 using xda premium

Thanks.
Have you used PA? Can I put the menus at the top?
What about icon the app drawer app? Can that be repositioned to the bottom?
Sent from my GT-N7100 using Tapatalk 2

Hi Mate,
PA on the Nexus is the only ROM I've used for the last 4/5 months? (Its consistantly AMAZING) I've used it since PA 2.54 and its consistently updated and improving.
I too don't use the Pie, I keep the Stock UI (but this isn't the option you want, I never you landscape see)
I've never tried Franco but I've used Faux and M-Kernel.
Whilst Faux and PA is THE BUTTERIEST combo I've ever tried, I got bored and wanted to try elsewhere.
So I tried M-Kernel, I can say the M-Kernel just doesn't have that uber (sorry for that couldn't think of another word haha) smooth feeling, Faux is a god at kernels.
HOWEVER - Faux used to drain 1.4% an hour on standby, M-Kernel uses only 0.7/0.8%. So make your choice, M-Kernel, for great battery and good smoothness, or Faux with GREAT smoothness but a little less easy on the battery. However both kernels and PA make the Nexus 7 into a completely new device.
Hope this helps

Is this where you are talking about? :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

1. Yeah you can use the tablet ui like the n10 one and you can have the icons to the bottom (you just need to customize)
2. For the battery life, the Franco kernel is the one praised for its battery life. You can check the kernel comparison thread (I know it's 4.2.1). So far on a 6-8 hours standby, I lose 1-3%. Performance wise : buttery smooth. (nuff said )
3. As for stable version, I think the 3.0 stable is the one from early February but the nightlies are working no problem (just need to flash the bluetooth fix but it's no big deal.)
Hope it helps.
Sent from my Nexus 7 using Tapatalk HD

no..
I find that even though it looks nice... It's extremly slow for me

I'm finding the stock browser is unuseable on this rom after a few hours, constantly freezes. Anyone else getting this?
(I tried clearing cache and all browser data)

thanks to all for the comments.
I'm doing a NAND backup right now and proceeding to flash in a few minutes (man this backup takes forever).
I'll try M-kernel, since my top priority is battery life.
Quick follow re. kernels;
can I switch kernes on the fly, ie; can I keep them both on root system and then proceed to overwrite kernels between reboots?
I can't imagine a situation where I would need additional buttery smoothness on demand, but it's always nice to have the options.
Are there any precautions I should take in terms of kernel co-existence? ie, any GAPPS I should flash, version of roms that dont play nice?
@Pierre118;
thanks for the screencap, that's almost what my dream desktop; I want the N10 landscape view,
. the controls in the middle, the pulldown menus at the top. (again, no plans on using PIE, at least not until I actually get a chance to test it).
last but no least, I'm following the instructions and a few youtube videos; the file to download seems a bit light to me; only 157MB. Is this correct? Is this the only file I need (ROM) plus the GAPPS, which are another 147MB.? seems awfully small...

You can indeed flash kernels on the fly. Just wipe cache/dalvik. Yes, those are about right for file sizes. Bare minimum would be the ROM and gapps for whatever version of android. Then for kernel, its a good idea to flash ROM and gapps then do a boot before flashing a third party kernel.
The most current nightly of pa is really good and has Bluetooth working without a patch.
Edit: FYI you'll need an app like trickster mod to adjust kernel settings. If you go with mkernel start by setting up with metalice's recommended settings, good battery life and performance. Then adjust from there after you get comfortable.
Sent from my P.A.C. Man ONE S

Hobbes2099 said:
Quick follow re. kernels;
can I switch kernes on the fly, ie; can I keep them both on root system and then proceed to overwrite kernels between reboots?
I can't imagine a situation where I would need additional buttery smoothness on demand, but it's always nice to have the options.
last but no least, I'm following the instructions and a few youtube videos; the file to download seems a bit light to me; only 157MB. Is this correct? Is this the only file I need (ROM) plus the GAPPS, which are another 147MB.? seems awfully small...
Click to expand...
Click to collapse
You can keep multiple kernels in the root folder, but I wouldn't recommend you changing kernels frequently. Find one you like and stick with it. Kernel performance improves with stability i.e., multiple charge cycles. Constantly changing kernels won't get you the best performance.
And stock ROMS are light. Compared to the Sense ROM I'm using on my One X (almost 500MB), you can see how heavy skinned versions of Android really are. And that's a trimmed down Sense ROM. Can you imagine how heavy the original skin was before it was trimmed??

Installed and loving it!!!
I'll try it out for a couple days before poking around the different kernels.
So I can't seem to find the way to get my screen to look like yours.
Do I need a launcher that will allow the app drawer at the bottom rather than the side?
I won't mind giving Nova Launcher or Apex another go.
Sent from my Nexus 7 using Tapatalk 2

Try phablet (700p on system ui)... Third party launchers are great though. I use apex and would never go back to stock now lol
Sent from my Paranoid 3.1 Nexus7 running M-Kernel

I looked up the options, the screen cap I shared is my current screen at 600p.
I see these options:
Under workspace, there's only phone (360p), phablet (600p) and tablet (1000p); I'm assuming you meant 600p.
I tried using 1000p, but it sends the menus to the bottom, and the drawer remains on the side.
Back when I was Stock 4.2.2 ROM I used Apex + https://play.google.com/store/apps/details?id=nl.fameit.rotateUltimate Rotation Tool.
One of the main reasons I wanted to try PA was to get the same layout without the extra software.
Is this possible?
Sent from my Nexus 7 using Tapatalk 2

I was able to replicate what you want using apex. Not sure if it can be done on stock launcher as I've been using apex since day one of owning my n7. It's not my normal layout so not set up right, hence why it looks odd, just showing that I did get it that way.
This is in phablet mode (some apps it's 700p, system is apparently 600, sorry )
Edit: I had to adjust launcher settings to do this, not just put it in phablet mode, again don't know much of the stock launcher, check its settings to see if you can adjust them to do this. I still will always suggest apex or Nova, stock launcher sucks
Sent from my Paranoid 3.1 Nexus7 running M-Kernel

Go with Nova Launcher Prime, I'd say.
As for Paranoid Android, I love it. I've been running it with the Faux Ultimate Kernel and it is insanely good.

I already owned Nova Launcher from a Google Play sale months before. I finally went with it and haven't looked back.
I'm really loving PA.
Regarding kernels, I understand now that kernels improve with use. Should I be rebooting frequently at the beginning?
Has anyone had the impression that the kernel is great and then not so much?
I almost got 12 hours of use (actual screen time) after the first few days. Now I'm getting between 8 and 10 hours at most.
Sent from my GT-N7100 using Tapatalk 2

what's the default kernel that comes with PA 3.0?
I don't know much about kernels, but I'm eager to give m-kernel a try after I flash 3.15.
I wanted to know a bit more about kernel and thought I'd keep using this thread and keep the development PA thread as spam free as I can;
what is the default kernel I get when flashing PA 3.0 or 3.15? Is the kernel part of the ROM? is it ever with other ROMs?
how can I tell from system settings (or other system-reading apps) what kernel my N7 is currently using?

Hobbes2099 said:
I don't know much about kernels, but I'm eager to give m-kernel a try after I flash 3.15.
I wanted to know a bit more about kernel and thought I'd keep using this thread and keep the development PA thread as spam free as I can;
what is the default kernel I get when flashing PA 3.0 or 3.15? Is the kernel part of the ROM? is it ever with other ROMs?
how can I tell from system settings (or other system-reading apps) what kernel my N7 is currently using?
Click to expand...
Click to collapse
Pa uses a stock aosp kernel I believe. You can see what kernel you have under system >about
Sent from my P.A.C. Man ONE S

Hobbes2099 said:
I don't know much about kernels, but I'm eager to give m-kernel a try after I flash 3.15.
I wanted to know a bit more about kernel and thought I'd keep using this thread and keep the development PA thread as spam free as I can;
what is the default kernel I get when flashing PA 3.0 or 3.15? Is the kernel part of the ROM? is it ever with other ROMs?
how can I tell from system settings (or other system-reading apps) what kernel my N7 is currently using?
Click to expand...
Click to collapse
Some ROMs use default JB kernel, some use a tweaked version, and some include custom kernels from the beginning. Like My One X running ICJ uses NCX kernel by default. It will be mentioned in the OP/changelog if a ROM is using a custom kernel.
Two ways you can see the kernel currently on your device:
As mentioned above, go to settings > about and see under kernel version
Or if you are using Trickster Mod, it displays your kernel in the app as well.

Just Comment The Best Custom Rom for Moto G 2014 According to your Experiance

Just Comment the Best Custom Rom According to your Experiance and Uses :angel:
According to your Comments its will be easy to find out Best Custom Roms
Give Custom Rom and Base on Following Things Comment about that Rom
1. Stable
2. Battery Backup
3. Smoothness
4. Performances
5. Gamming Experiance
6. Customize Options
7. Bugs (Mention if any*)
etc..
If You want all the Deatil for Moto G 2014 Like Rom, Unlockbootloader, Recovery, Tools, Kernal, Guid, etc
visit => MOTO G 2014 Index of Threads
Note*
This forum is just for getting an information of all custom rom and not for to point any Developers for his work.
I Commit all Roms are Good and Best at there Stage:good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just Hit Like if You Find Useful

5.....4.......3.......

Still alive?

Just to not let this post die, I like pretty much Stock
Besides, every ROM have different things, and depends on the users to catch'em all! (Wild Pokémon theme song suddently appears)

I think that you'll have to compromise on battery and performance with this phone. It's hard to have both performing well. I will only run stock based roms because they offer the best compromise. Lexodus rom with Stellar kernel along with Xposed and Greenify gave me the best all around. Lexodus and Stellar alone made the phone scream but did hurt the battery performance a little.
Sent from my GT-P5210 using Tapatalk

I find Minimal OS very stable and smooth. I have been using it around 20 days and observed no FCs as of yet. Battery backup is very good. In addition, I manually set CPU governors to improve the backup. I don't play much of games, but Hay day runs very smooth on this ROM, just the way it runs on stock. Talking about customizations, this ROM supports Layers, hence you can download the Layers themes from play store and customize the ROM.
Here is the link to ROM: http://forum.xda-developers.com/moto-g-2014/development/rom-minimal-os-t3174134

that true bother
pank.dhnd said:
I find Minimal OS very stable and smooth. I have been using it around 20 days and observed no FCs as of yet. Battery backup is very good. In addition, I manually set CPU governors to improve the backup. I don't play much of games, but Hay day runs very smooth on this ROM, just the way it runs on stock. Talking about customizations, this ROM supports Layers, hence you can download the Layers themes from play store and customize the ROM.
Here is the link to ROM: http://forum.xda-developers.com/moto-g-2014/development/rom-minimal-os-t3174134
Click to expand...
Click to collapse
i have used this rom for few days its good for minimum use.
but i am using two rom in my device using multirom twrp by Luk1337 and on my internal rom am using Blisspop by vatsal becos its has much more option for customization and on 2nd rom am using official cyangenmod rom by Luk1337 with minimum tk gapps.

Cm 12.1 its good in features & battery and almost stable

pank.dhnd said:
I find Minimal OS very stable and smooth. I have been using it around 20 days and observed no FCs as of yet. Battery backup is very good. In addition, I manually set CPU governors to improve the backup. I don't play much of games, but Hay day runs very smooth on this ROM, just the way it runs on stock. Talking about customizations, this ROM supports Layers, hence you can download the Layers themes from play store and customize the ROM.
Here is the link to ROM: http://forum.xda-developers.com/moto-g-2014/development/rom-minimal-os-t3174134
Click to expand...
Click to collapse
Yes I'm also using that one and I like it so far. Haven't tried any other than stock rom though. It got all the additions I need to be happy. Except vibration adjustments.
Ps.: When I change dpi setting to a lower dpi, the font and everything gets smaller. Which confuses my brain . I mean, shouldnt lower dpi mean lower resolution therefore bigger font etc.?

knockout41 said:
Yes I'm also using that one and I like it so far. Haven't tried any other than stock rom though. It got all the additions I need to be happy. Except vibration adjustments.
Ps.: When I change dpi setting to a lower dpi, the font and everything gets smaller. Which confuses my brain . I mean, shouldnt lower dpi mean lower resolution therefore bigger font etc.?
Click to expand...
Click to collapse
nope

please do this
knockout41 said:
Yes I'm also using that one and I like it so far. Haven't tried any other than stock rom though. It got all the additions I need to be happy. Except vibration adjustments.
Ps.: When I change dpi setting to a lower dpi, the font and everything gets smaller. Which confuses my brain . I mean, shouldnt lower dpi mean lower resolution therefore bigger font etc.?
Click to expand...
Click to collapse
set screen dpi to 320 and all problem will be solved..

axays said:
set screen dpi to 320 and all problem will be solved..
Click to expand...
Click to collapse
320 is too big 240 is best

You could try sokp, its a very stable rom with tons of features and customisation options while stille being smooth. Battery backup is not the best but i get through my day with regular use. Since its aosp you can flash custom kernels made for cm12.1 and aosp. But in my experience it slowed my device down so yeah... Atm it has no xposed compatebility because it has an heavily customized ART, plus its based on android 5.1.1r10 i believe. Extra features are multi window and slim recents and a lot more. I'm realy pleased with it but it may or may not be for you .
Best of luck,
Bart
sent by a titan from an other demention

pank.dhnd said:
I find Minimal OS very stable and smooth. I have been using it around 20 days and observed no FCs as of yet. Battery backup is very good. In addition, I manually set CPU governors to improve the backup. I don't play much of games, but Hay day runs very smooth on this ROM, just the way it runs on stock. Talking about customizations, this ROM supports Layers, hence you can download the Layers themes from play store and customize the ROM.
Click to expand...
Click to collapse
I agree with you concerning this ROM overall. I used it for a couple of weeks and was very impressed with it. Compared to a half dozen other ROM'S I have tried it won hands down. However, I ran into a glitch with a critical app upon which I rely for my job and unfortunately I had to go back to AOSP. I doubt that the problem will be resolved since the app is a very specialized app that most users on this site won't ever use.
Given that, I am extremely happy with 5.1.1 AOSP and would give it my number 1 rating. It is stable, smooth, responsive and the battery life a fairly decent.. And ALL of my apps work well with it.

"very specialized app"
pastorbob62 said:
I agree with you concerning this ROM overall. I used it for a couple of weeks and was very impressed with it. Compared to a half dozen other ROM'S I have tried it won hands down. However, I ran into a glitch with a critical app upon which I rely for my job and unfortunately I had to go back to AOSP. I doubt that the problem will be resolved since the app is a very specialized app that most users on this site won't ever use.
Given that, I am extremely happy with 5.1.1 AOSP and would give it my number 1 rating. It is stable, smooth, responsive and the battery life a fairly decent.. And ALL of my apps work well with it.
Click to expand...
Click to collapse
can you please name me the " very specialized app" Name..!

axays said:
can you please name me the " very specialized app" Name..!
Click to expand...
Click to collapse
Sure! It's Jobulator, which is a substitute teacher job assignment app. I sub-teach in the local school district and all potential jobs come through that app. It is set to a given interval (by the user) to check for new jobs that teachers have posted. When a job is listed it will give an alert notification and (ideally) I can then accept or reject the job. However with Minimal OS I would get the alarm but only a blank screen, (no "accept/reject" buttons). It took a while to show up since the first two weeks of school I was able to accept on my tablet and desktop (strictly by luck). But in several instances I was away from home. Consequently I was unable to accept some jobs before another sub grabbed them. So I went back to AOSP-luk and have had no issues.
In all honesty, I have never been dissatisfied with AOSP but the fact that Minimal has less bloat appealed to me so I tried it out. I see no difference in performance, battery life or stability with either ROM, just the issue mentioned above makes AOSP the winner for me.

axays said:
Just Comment the Best Custom Rom According to your Experiance and Uses :angel:
According to your Comments its will be easy to find out Best Custom Roms
Give Custom Rom and Base on Following Things Comment about that Rom
1. Stable
2. Battery Backup
3. Smoothness
4. Performances
5. Gamming Experiance
6. Customize Options
7. Bugs (Mention if any*)
etc..
If You want all the Deatil for Moto G 2014 Like Rom, Unlockbootloader, Recovery, Tools, Kernal, Guid, etc
visit => MOTO G 2014 Index of Threads
Note*
This forum is just for getting an information of all custom rom and not for to point any Developers for his work.
I Commit all Roms are Good and Best at there Stage:good:
Just Hit Like if You Find Useful
Click to expand...
Click to collapse
Stock 5.0.2 debolated with xposed. or BlissPOP v4.0

Infinitive OS, excellent performance. Nice battery backup( 2 days of normal use, 4:30 hr of SOT, half WiFi, half 3g, it also sleeps like a baby). Only one bug, sometimes you can't wake up the phone with the block key, not a problem if you choose to wake it up with volume keys and after that block key works again. It just happens randomly.
Sent from my Transformer TF101 using XDA Free mobile app

sharique88 said:
Stock 5.0.2 debolated with xposed. or BlissPOP v4.0
Click to expand...
Click to collapse
I tried bliss pop 2-3 weeks ago and it had lots of bugs, I faced frequent FCs under settings, while viewing as well as modifying settings. Also I found battery life pretty average hence I moved away from it.
---------- Post added at 09:35 AM ---------- Previous post was at 09:21 AM ----------
I also tried Resurrection Remix. It is loaded with tons of features and customizations. It runs good but I faced some minor glitches randomly, so I would say not as smooth as Cyanogenmod or AOSP. Battery performance is better than stock, close to cyanogenmod, but not as good as AOSP. Plus, on my personal view, I feel that lots of customizations kind of ruined the overall look for the ROM. You can't get the look of stock Android on this ROM. There and bold and italic fonts are used in the ROM which hampers the overall look and visual experience, but this is actually no problem as this ROM supports Cyanogenmod theme engine. Here is the link for the thread for this ROM: http://forum.xda-developers.com/moto-g-2014/development/rom-resurrection-remix5-5-4-t3181360

EHNDROIX
1. Stable (8/10)
2. Battery Backup (10/10) (reinstalled just because of the best battery backup)
3. Smoothness (9/10)
4. Performances (9/10)
5. Gamming Experiance (I don't play sorry)
6. Customize Options (10/10 ) (colorful settings menu & lots more)
7. Bugs (Mention if any*) (there were regarding camera but I flashed camera app via zip & the bug got solved)

UI Smoothness vs Battery Life, and 3rd Party Launchers

Hey guys and gals. I've been poking around the forums here and crpalmer's unofficial CM13 has caught my eye. Many of the users in the forum praise how buttery the ROM is. At the same time, many users lament how the stock ROM achieves better battery life. I wondering, perhaps the stock ROM's lag is a direct result of aggressive battery saving protocol (e.g. cpu/gpu throttling). What do you think? If this is true, Huawei should implement a battery management switch similar to Windows (Power saving, Balanced, high performance). I'd happily sacrifice battery life for a buttery UI when I can afford it, and vice versa.
Continuing that thought, I use Nova launcher on Stock ROM and I haven't been too offended by lag. The only minor issues I have is when using Google Now search (a noticeable delay opening) and the task switcher (delay in both opening the switcher and entering a selected app). Where do you guys lag on stock ROM and does changing the launcher help?
Cheers.

JT-on said:
Hey guys and gals. I've been poking around the forums here and crpalmer's unofficial CM13 has caught my eye. Many of the users in the forum praise how buttery the ROM is. At the same time, many users lament how the stock ROM achieves better battery life. I wondering, perhaps the stock ROM's lag is a direct result of aggressive battery saving protocol (e.g. cpu/gpu throttling). What do you think? If this is true, Huawei should implement a battery management switch similar to Windows (Power saving, Balanced, high performance). I'd happily sacrifice battery life for a buttery UI when I can afford it, and vice versa.
Continuing that thought, I use Nova launcher on Stock ROM and I haven't been too offended by lag. The only minor issues I have is when using Google Now search (a noticeable delay opening) and the task switcher (delay in both opening the switcher and entering a selected app). Where do you guys lag on stock ROM and does changing the launcher help?
Cheers.
Click to expand...
Click to collapse
yes the Nova launcher helps, but the No-Swap script from @EarlyMon makes a Huge difference.

clsA said:
yes the Nova launcher helps, but the No-Swap script from @EarlyMon makes a Huge difference.
Click to expand...
Click to collapse
You mean applying the now-swap script improves performance?

fazorni said:
You mean applying the now-swap script improves performance?
Click to expand...
Click to collapse
yes the No-Swap is the key to a smooth 5X

I entered the arena a little late, but I've run almost all of the custom roms that will boot on my device. I'm currently running stock heavily modified and I'm very impressed with my $159.00 phone. I paid almost $600 for a developer model G1, but would never pay that much now, since then I've had some very good high end devices, and now the Honorable 5x, everyone I know has cast aside my device once I tell them how much I paid, sad world. My point being, the custom roms run great, but they take away the hidden treasures in this little beauty. Here's one.
PS: This is the first were I have to read how to's, I discovered by accident the the camera is a scanner, try scanning bar code or QR
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my KIW-L24 using XDA-Developers mobile app
---------- Post added at 05:20 AM ---------- Previous post was at 05:07 AM ----------
JT-on said:
Hey guys and gals. I've been poking around the forums here and crpalmer's unofficial CM13 has caught my eye. Many of the users in the forum praise how buttery the ROM is. At the same time, many users lament how the stock ROM achieves better battery life. I wondering, perhaps the stock ROM's lag is a direct result of aggressive battery saving protocol (e.g. cpu/gpu throttling). What do you think? If this is true, Huawei should implement a battery management switch similar to Windows (Power saving, Balanced, high performance). I'd happily sacrifice battery life for a buttery UI when I can afford it, and vice versa.
Continuing that thought, I use Nova launcher on Stock ROM and I haven't been too offended by lag. The only minor issues I have is when using Google Now search (a noticeable delay opening) and the task switcher (delay in both opening the switcher and entering a selected app). Where do you guys lag on stock ROM and does changing the launcher help?
Cheers.
Click to expand...
Click to collapse
blas4me said:
I entered the arena a little late, but I've run almost all of the custom roms that will boot on my device. I'm currently running stock heavily modified and I'm very impressed with my $159.00 phone. I paid almost $600 for a developer model G1, but would never pay that much now, since then I've had some very good high end devices, and now the Honorable 5x, everyone I know has cast aside my device once I tell them how much I paid, sad world. My point being, the custom roms run great, but they take away the hidden treasures in this little beauty. Here's one.
PS: This is the first device were I would suggest reading the how to's online. I discovered by accident that the camera is a scanner, just turn on light when scanning bar code or QR.
Sent from my KIW-L24 using XDA-Developers mobile app
Click to expand...
Click to collapse
Sent from my KIW-L24 using XDA-Developers mobile app

@blas4me, what do you mean by heavily modified stock ROM? Are you talking about this ROM?: http://forum.xda-developers.com/honor-5x/development/rom-b140-debloated-t3335837
Well, I haven't used any of such debloated ROM, neither I disabled swap, but I feel that EMUI 3.1 is much laggy than EMUI 4.0. The UI is laggy, openings apps takes time n all. Plus I hate it because Huawei disabled OTG capabilities in it. (Best part is they didn't even know if it works, during beta test, we were told that phone hardware doesn't support OTG. We had to redirect them to XDA post where OTG capabilities can be enabled by flashing custom kernel; and then they believed it, but never enabled in EMUI 4.0 release.).
With EMUI 4.0, Huawei shipped issues like excessive RAM consumption, all CPU cores always online, which drains your battery and also heats up your phone. This is one of the reason I moved to CM13. Plus frankly I like stock Android. I used Huawei propriety EMUI for a while but didn't like it much. I feel lack of user friendliness at some places (just look at the default clock for example, you need to keep scrolling in order to set up the alarm. Other clock apps downloaded from Play store doesn't seem to ring alarm on time. Also with EMUI 4.0, try the swiping WhatsApp notification, I am quite sure you will hate it.).
If Huawei fixes the issues with EMUI 4.0, and put some sugar on top with OTG support, then I might give a try to EMUI 4.0 again for a while

Yes, @blas4me, care to share your list of modifications? I'd like the stability of stock with some performance improvements (even at the expense of battery)

Sure, first I calibrated my battery. A old habit, anyway just use phone until dead, then fully charging in off mode would be best, but you can charge powered on, then, power off when you get to 100%, until your notification light is green. From there install battery guru, put in learning mode and that's pretty much it on that side. The phone comes with power saving features, I'm using smart mode. I also have amplify installed, an xposed module, not sure if it's playing a part in power conservation. When I say heavily modified , about twenty or so xposed modules, some custom scripts running, changed density and some other haks, craks, and work arounds, that I won't mention, but I have shared or found within the community.
PS: I have nova launcher, and animations & transitions turned off in developer options, and in nova I set all animations & transitions to fast.
Sent from my Honorable 5x using XDA-Developers mobile app

I agree with the op. The stand-by time on this rom (3.0) is great. That and the fp scanner is what is keeping me on this rom. However I choose to change the animation from .5x to 1x and it feels more smooth. I also limit to 3 background apps. I do keep it on performance mode and have am still getting great power use! The no swap script makes noticeable difference. Like others stated the only lag really is in the app switcher and google search.
Great phone for the price. I sold my nexus 6 as is was getting to bulky to carry around and I am just not using it as much as before. Only thing I miss is the new look of notifications in the preview N.

blas4me -
Was installing Xposed easy? I've done it before on Motorola devices but was hesitant to try on the Honor until I hear from others.

Yeah, you need 86, not 85. Go to xposed repo.

Why would you calibrate your battery it has a min and max voltage, it cant be discalbirated. there is no file that resets its self so its get 'calibrated'.

Just a habit from a old HTC device, but thanks for the technical advice, I'm geeky like that.