Database Develop

[POLL] What ROM would you recommend to people?

This thread is for people like me, who don't know what ROM to choose from a list of many ROMs from many great chefs.
I am keeping my poll options empty for the time being as I have only played with a few ROMs without any guidance. I will begin to populate them as I start to see a few specific ROMs appearing consistantly.
I would like to ask the community of xda-developers to come by and help populate this thread with simple comments
and/or recommendations on what ROM(s if you have multiple devices) you use on your Rhodium/Touch Pro 2/Tilt 2 device.
Also, please also add what kind of user your are, or how/why you use your phone with 'said' ROM.
Additionally beneficial would be letting users know what ROM you recently used prior to your recommendation and the offsets you experience in general.
ie. ROM A is the one I recommend. However, ROM B does a few things a bit better, although ROM A is the one I would recommend to people who like smooth, quick eyecandy filled ROMs.
I also ask for intelligent, constructive critique on what you think about the ROM that you are commenting upon.
No one needs to know about what piece of profanity you would like to tack on 'user A' for saying '10101' about 'ROM B' or vice-versa.
This is meant to be a resource for new users to xda-developers, like I was, and to new owners of the HTC Touch Pro 2/Rhodium, Windows Mobile phone.
Candidly, I would like to have the moderator's support in keeping this a clean thread to have an easier (and more pleasant) navigation throughout the thread.
I would like to start off with creating a list of ROMs organized by chef name and OS/TouchFlo 3D version.
Underneath each ROM and their links (I will either find the ROM myself, or if you can be so helpful enough to link it onto your post
within this thread), I will be adding the pros and cons that are mentioned here, and that I have found as well.
To let you know a bit about my bias, I am looking for the following items;
-Speed
--Not only operating speed, going from interface to interface, but also how it handles multitasking.
--I usually do these three together; GPS, music, web browsing/text messaging
-User Friendliness
--From first stepping into the ROM, to using it for a couple of days and seeing it's inevitable and understandable flaws and offsets.
--Customizing settings on the ROM, and the ease to have certain things.
-Miscellaneous
--Other things such as the way the ROM will handle things such as the
unsightly error of TouchFlo 3D 2.5 and it's lack of Landscape viewing ability.
--These items will account for my general accountability on the topic of
"Would I (highly) recommend to my friend, who may be the same as, or a completely different user than, me."​
My history with phones;
I have first used Motorola phones, starting with the t220 (apparently one of the first camera phones) moving to the RAZR V6 MAXX
(quite a glam, nice looking phone with great features, but poor connectivity issues with network and bluetooth) and a few years ago
Sony Ericsson phones such as the W810, K850 and the Sony Ericsson XPERIA X1a.
Most recently;
I have late last year, used a BlackBerry BOLD 9000, and in the past 3 months, trialed the Sony Ericsson XPERIA.
Without much ROM customization, the stock ROM was fun to play with, but lacked the easy access and user interface speed that
I have become accustomed to with the BlackBerry BOLD 9000. However, in seeing the Touch Pro 2 and purchasing it, I can now fully indulge in customizing
it with ROMs to fit my needs, though I am still painfully without hardware keys to have quick access to my browser, music or GPS.
However, I suppose the full 5 row keyboard makes up for the lack of hardware buttons elsewhere on the body.
Currently, I am using my Touch Pro 2, mainly as a resource device. What do I mean by this? I am using it with a SIM Card that only has data services.
I have installed programs such as Japanese dictionaries, phrase banks and linguistic aids to help in my study of the Japanese language.
I also use this for school (I am currently in grade 11, high school) using this device as my quick access to the internet (even though I have my blackberry).
I suppose having new devices is an obsession for me, as with a few others on here.
I'm looking for ROMs that will allow me quick and easy access to the programs that I frequent the most such as my Japanese programs, GPS,
music, web browser, notes, M-Soft Word and also allow me to freely multitask with them.
I know that this is mainly hardware dependent, but I have learned that some ROMs take up less RAM space, as to free up some more coasting speed for programs to run on.
Posting Format​​
Please include the following;
Recommended ROM?
ROM used before recommended ROM?
Your network provider, phone (is it from/branded T-Mobile US, AT&T, Telstra, Sprint, TELUS)?
How/What do you use your phone? (Business, personal, school // As your main device, just as a (conference) phone, just as a mini internet tablet, etc...)
The pros & cons you noticed coming onto this ROM?
Who you think would benefit from using this ROM?
​
ADDITIONALLY;
I want to invite Chefs to either PM me, or post what (and who) they desire their ROM to be (for),
so that TP2/Rhodium users/owners can have a one-stop place to take a look at which ROM has what to offer (and to whom).
I will be adding the Chef's words beneath the ROM(s) they wish to comment upon.
The following post will before the ROM listings.​

ROM Listings!
Chef NRGZ28
He builds his ROMs with four main goals.
* Eye candy
* Speed !!!
* Smoothness, consistency and good aesthetics
* Stability through private beta testing before public release
Click to expand...
Click to collapse
★ EnergyROM "Leo" (Build 23016) [Updated Oct 7]
Runs Windows Mobile 6.5 WWE & TouchFlo 3D/Manila 2.5
------------------------------------------------------------------------------------------------------------------------
Comments;
-Stable
-Fast
-Good Looking
------------------------------------------------------------------------------------------------------------------------
Great for;
★ EnergyROM "Photon, formerly GENESIS" (BUILD?) [Updated Oct 7]
Runs Windows Mobile 6.5 WWE & TouchFlo 3D/Manila 2.1
------------------------------------------------------------------------------------------------------------------------
Comments;
-Bug-Free
-Great aesthetics
------------------------------------------------------------------------------------------------------------------------
Great for;
Chef Monx
"ONLY THE BEST FOR ALL XDA-DEV MEMBERS"
Click to expand...
Click to collapse
ROMeOS³ v1.20 (Build 23016)
Runs Windows Mobile 6.5 WWE & TouchFlo 3D/Manila 2.5 + HTC SENSE (beta)
------------------------------------------------------------------------------------------------------------------------
Comments;
-Fun and easy to customize to personal tastes
-Works great "out of the box"
------------------------------------------------------------------------------------------------------------------------
Great for;
Chef b16b
AthineOS v2.0 OEM Style (Build 21054)
Runs Windows Mobile 6.1 & TouchFlo 3D/Manila 2.1
------------------------------------------------------------------------------------------------------------------------
Comments;
-Works great "out of the box"
-Very stock/OEM like ROM without all the carrier's unneccessary confectionery
-Easy to use, being that it is a simple ROM
-Quick and fast
------------------------------------------------------------------------------------------------------------------------
Great for;
-Those who are looking to keep their stock ROM without carrier branding or excessive programs
-Great for business users to retain that 'corporate' look
[MORE COMING]

MISC 1 -----

MISC 2 -----------

im so glad you have this up. i also have a hard time choosing.
pretty useless comment lol

You might be wasting your time since a mod most likely will close this thread...

How come?
If I'm making a bit too bias (on what I'm looking for) then I won't include my own opinion. That's fine.
But I want to have something like what the Kovsky/Sony Ericsson XPERIA forum has.
A ROM index, but enhanced with things such as recommendations, and owner/users & chef comments.

SleepiTyme said:
How come?
If I'm making a bit too bias (on what I'm looking for) then I won't include my own opinion. That's fine.
But I want to have something like what the Kovsky/Sony Ericsson XPERIA forum has.
A ROM index, but enhanced with things such as recommendations, and owner/users & chef comments.
Click to expand...
Click to collapse
I am not sure why, the last few times someone asked which ROM was best the mods closed the thread. They claim it cuases flame wars and such.
Personally, I dont mind, like the idea and I was just giving you a heads up. Maybe you should ask a mod before your proceed further.

I would say this poll would avoid other threads like "what do you think is the best rom" or "can you advise me some rom"
So thumbs up

the best way to keep one thread like this is :
take one benchmark.. and test all the rom.. and post all result here
like topaz one
otherwise will locked soon

Benchmark?
"How does Benchmark?"
I think.. by emulating the ROM's speed and multitasking capabilities and such?
I want to know, not by computer, but by people why 'said' ROM is great.
Honestly, this is my story here;
I heard that ROMeOS's ROM for the Rhodium was great, although I had first saw Athine OS (both the light and Titanium builds with 2.1 and 2.5 Manila, 6.1 and 6.5 WinMo) and saw the pictures of the interface were just completely amazing.
So I downloaded them, but saw that they ran.. just the same as my stock ROM (at quite the same speed), though it was much cleaner than my Telstra stock ROM which was confuddled with many apps and things that I didn't need. And the light blue theme just didn't do it for me.
So then I just recently (actually last night) installed the ROMeOS ROM on my TP2 and found it so fun to have so much control upon things such as background wallpaper (both for lock screen and home screen tab). Also things such as backlighting, edit tabs, set up bluetooth, set up data, ringtones, message notifications ALMOST EVERYTHING customizable (that you would usually have to go in and out of menus for on the stock WWE ROM, and sometimes the Athine ROM) was located in one simple tab. Neigh, a simple section within a tab that had even more customization for other things on the phone.
THAT! That was most likely made this ROM popular, and it really did get into my good books quickly... until I found out that Manila 2.5 doesn't support Landscape.
I feel like I should either.. move onto another ROM, or just live with it.
I'm using Gyrator 2 along with my ROM, and it DID have the event action NOT to have auto rotate in Manila.. even though.. I want it to...
This above.. I'm looking for comments such as this, except from other, MORE experienced users with better opinions. Who hopefully can dumb it down so that people like me and many others, still fairly new to Windows Mobile, xda-developers and the HTC Touch Pro 2/Rhodium alike, can understand.
I believe.. that this should be something like a collaborative blog.
Just reading back up on my post right now, it's almost as if I were reading someone's story.
Many users might not want to go through that, and others may just want to write something to have their experience heard.
What I want to do is sift through all of that, and just have the comments, positive or negative, tacked onto each ROM in a list.
My ROMs Listing post.
Right by each description from each Chef.
Maybe it'll be reason enough for mods to keep this alive, maybe it won't be.
But... saving the effort of going through each ROM (there are about... 6-10, give or take 5^x) in which said thread for said ROM has 10+ pages of posts, usually around the vicinity of 30-50.
That is A LOT OF READING.

useless information
personally, this is useless information and i don"t go by polls. The best information is based on users" signature. I also take time to read, instead of relying on polls.

SleepiTyme said:
Benchmark?
"How does Benchmark?"
I think.. by emulating the ROM's speed and multitasking capabilities and such?
I want to know, not by computer, but by people why 'said' ROM is great.
Honestly, this is my story here;
I heard that ROMeOS's ROM for the Rhodium was great, although I had first saw Athine OS (both the light and Titanium builds with 2.1 and 2.5 Manila, 6.1 and 6.5 WinMo) and saw the pictures of the interface were just completely amazing.
So I downloaded them, but saw that they ran.. just the same as my stock ROM, though it was much cleaner than my Telstra stock ROM which was confuddled with many apps and things that I didn't need. And the light blue theme just didn't do it for me.
So then I just recently (actually last night) installed the ROMeOS ROM on my TP2 and found it so fun to have so much control upon things such as background wallpaper (both for lock screen and home screen tab). Also things such as backlighting, edit tabs, set up bluetooth, set up data, ringtones, message notifications ALMOST EVERYTHING customizable (that you would usually have to go in and out of menus for on the stock WWE ROM, and sometimes the Athine ROM) was located in one simple tab. Neigh, a simple section within a tab that had even more customization for other things on the phone.
THAT! That was most likely made this ROM popular, and it really did get into my good books quickly... until I found out that Manila 2.5 doesn't support Landscape.
I feel like I should either.. move onto another ROM, or just live with it.
I'm using Gyrator 2 along with my ROM, and it DID have the event action NOT to have auto rotate in Manila.. even though.. I want it to...
This above.. I'm looking for comments such as this, except from other, MORE experienced users with better opinions. Who hopefully can dumb it down so that people like me and many others, still fairly new to Windows Mobile, xda-developers and the HTC Touch Pro 2/Rhodium alike, can understand.
Click to expand...
Click to collapse
How does one know which is best if they do not try them all? You mentioned two ROMs but have not mentioned the others. Can you give valid opinion on which you think is best without trying them all? Everyone has different tastes.
Those are just some of the things the mods may say and have said.
Like what I said, I don't mind a thread like this and wish there was a way to do this in a way that was more subjective.
Maybe there needs to be an official ROM judge
Edit
Well that won't work either.
The only for you to know what ROM is best for you is to try them all until you find one that you like for yourself.

Ut0p1a said:
personally, this is useless information and i don"t go by polls. The best information is based on users" signature. I also take time to read, instead of relying on polls.
Click to expand...
Click to collapse
Then.. maybe not polls?
What other way would be the best to;
1) save you time from reading a couple dozen to a couple hundred posts everytime you got a new device (though we're only talking about the Rhodium, and if you've read all those posts, I suppose you're a lost cause that I want to avoid being like, and want to help others avoid being as such as well)
2) Get you the accurate information on what are the highlights of the ROMs
2b) Without all the different ways that each chef sets up their forum posts to explain what their ROM does
2c) And have it all in one common format
3) Not many people post their ROMs on their signatures. I just saw it around as a growing
@At0mAng
Thank you for your opinion at this time of night.
Yes, did only mention (actually it was) three roms.
However, that is just only my input.
I've yet to trial the Miri ROM(s) and the Energy ROMs, just to name a few.
But mainly, I want simple, quick or concise comments on which ROMs a good/great and for what reason. Is it some part of the ROM? Does it perform better in the way that you've explained that you are using your TP2? Etc?
Yes.. everyone has different tastes, but they can mention what they like about 'said' ROM and help people become objective by the comments made here, and the quick pros and cons that have been tabulated onto the second post of this forum for quick reference as to which ROM does what best, or includes which great feature.
Edit;
This thread isn't here to decide Which ROM is the NUMBER ONE (for YOU)?!
It's to help guide newcomers to xda-developers, the HTC Touch Pro 2/Rhodium and Windows Mobile (all together) choose which ROM to pick.
I mean.. for new people, they have probably heard of ROMs, but don't know what to do with it.
What the heck is a HardSPL and flashing it?
Or, naturally after coming from the HardSPL resource sticky, one does suddenly freeze up and get stuck before spending 3-5 hours reading posts and choosing which ROM to pick and install, only to find out it doesn't really meet their requirements and move on to another one with a HUGE amount of wasted effort.
This here is to help people like that make more objective decisions, much quicker with the pros and cons of each ROM outlined and defined.

ROM Review template?
At0mAng said:
I am not sure why, the last few times someone asked which ROM was best the mods closed the thread. They claim it cuases flame wars and such.
Personally, I dont mind, like the idea and I was just giving you a heads up. Maybe you should ask a mod before your proceed further.
Click to expand...
Click to collapse
Completely agree with At0mAng and I like this idea. I don't understand the fear of flame wars either. Just ban the people who start flaming and can't have a normal discussion.
As for this thread, maybe we could all post reviews of a ROM in a certain template. E.g. give grades for speed, apps, stability, eye candy, etc... Some people look for speed and clean ROMs, others just for the most fully apped ROMs. With a review template, you could have a quick overview of what a ROM performs best on and make your pick.

It's Right!
There is NO Best ROM !
Every Cooker has his "touch and taste" in his ROM...
I love to work with you all, guys...
All the cookers here are talented!
Work AS a TEAM get us a BETTER results!!
Continue all, in the great progress...
We will "knock out" HTC software at a glance...

TheAgent1982 said:
There is NO Best ROM !
Every Cooker has his "touch and taste" in his ROM...
I love to work with you all, guys...
All the cookers here are talented!
Click to expand...
Click to collapse
It's not the point of this thread to find THE best ROM, but to find the most suitable ROM that fits your needs, at a glance...

Normally these threads are just closed as At0mAng said, but that would be unfair to the OP who's invested a fair old bit of time in this. It isn't the usual format and could be beneficial.
I've said before, that there isn't a forum rules preventing these threads, they are just closed because most of the people who create them are lazy noobs. If this threads is successful, then it "should" lead to less new threads.
I'm now subscribed and will monitor it, if it does degrade in to pretty much a Chef A vs Chef B thread, then I'll close it.
Thanks
Dave

Hi,
I'd like to take the opportunity to try to find a ROM which fits my needs: is there any Rom out there with WM 6.5, quicker than the stock ROM (if one can compare), with as few bugs as possible, still keeping Manilla 2.1 ? By the way, I am not interested in aesthetics, nor in software when the cab is available to install by myself. I only tested EnergyROM Genesis up to now, which is excellent, bug free as far as I can tell, but with many applications, very good aesthetics, maybe speed could improve with lighter graphics... Is there any quicker ROM here ?
On a side note, I find that the virtual keyboard of the TP2 is slow, e.g. changing from alpha to numeric takes too much time (then the first digit you type is ignored), does any ROM (or cab) improve this ?

Recommended ROM
I agree with the moderator that this poll (purely on the basis of statistics) is an interesting experiment and should not be stopped. It is vital though that people who vote have tested a significant number of the roms available.
I tested all the roms available on the 20-25 Sep period (7-8 of them) and I ended up using NRGZ28's Leo Manila 2.5 ROM as the most stable, fast, good looking. Essentially I encounter no bugs in every day use and I would recommend this rom to any TP2 user.

DIR ROM ? - Do It Right ? /Quality Control ?

What I miss at this forum, is a ROM with a honest, complete list of known bugs/non-working stuff.
Would like to see some quality-control, and know what I install - before I do.
Everybody is cooking ROM's (and that's nice) but there's no way to know how they will work before trying.
-its impossible to read thru >200 posts and figure out which of those are about the current version.
-recent posts are sometimes about earlier versions too...
Please: I hope some of you that des this nice job will focus on information about quality, and keep a "buglist" for each version..

AlCapone said:
What I miss at this forum, is a ROM with a honest, complete list of known bugs/non-working stuff.
Would like to see some quality-control, and know what I install - before I do.
Everybody is cooking ROM's (and that's nice) but there's no way to know how they will work before trying.
-its impossible to read thru >200 posts and figure out which of those are about the current version.
-recent posts are sometimes about earlier versions too...
Please: I hope some of you that des this nice job will focus on information about quality, and keep a "buglist" for each version..
Click to expand...
Click to collapse
I agree 100% Buglists are a must. Roms shouldn't be released with alot of bugs unless stated by the op.

husker91 said:
I agree 100% Buglists are a must. Roms shouldn't be released with alot of bugs unless stated by the op.
Click to expand...
Click to collapse
I think the point you're missing is that the bugs only become apparent after others flash the ROMs and do some testing.....

cr1960 said:
apparent after others flash the ROMs and do some testing.....
Click to expand...
Click to collapse
nope - the author/or a helper is in the ultimate position to read the feedback, verify, and make a list in the first article containing these bugs.
i did not say that the cook should know about every bug before releasing.
maintain a list, and verify it against next version.
-the only way to have some quality control...

I agree with the sentiment - for those of us who only flash their phones maybe once a month, it would be nice to know a ROM is ultra stable and all known bugs / oddities have been sorted. (or if not, then a comprehensive list of things that are broken, with any workarounds etc) Reading through thousands of posts takes hours and not everybody has the time or inclination for that.
For instance both WM and Manila (and others) are under very active development, there are always new versions coming out. While it would be unreasonable to expect the beta WM builds (23xxx, 28xxx) to be 100% stable, it would be nice for a cook or two to say "right, this combination of components is stable, I'm going to stick with these for a while" instead of always following the very latest cutting edge "LOOK, SHINY TOYS!" at the risk of stability.
As for stability I am currently on JoshKoss's latest (1.7) and have yet to experience a single error, crash or hang. And Josh's seem to be the fastest ROMs, definitely of the ones I have experienced anyway. There are a few minor inconsistencies but these are in no way critical. If you want stable I would not even consider Manila 2.5 or any of the "start menu at the bottom" ROMs.

Have you tried AthineOS ROMS? Very fast, very stable. The current Leo 2.02 based ROM is the fastest Sense 2.5 ROM I've tried (and I've tried them all) and stable enough for hassle-free day to day use.

Guyz As far as my experience goes no cook likes to hide the bug list, rather they work to bring more in the light. Users like us are expected to give our submissions. Thats how it works. Things like quality control is not what we have seen here since its not GM factory but a place to share & experiment & success & failure is part of that place.

AlCapone said:
nope - the author/or a helper is in the ultimate position to read the feedback, verify, and make a list in the first article containing these bugs.
i did not say that the cook should know about every bug before releasing.
maintain a list, and verify it against next version.
-the only way to have some quality control...
Click to expand...
Click to collapse
I completely disagree. At the rate new builds are released, and with so many new tweaks and items going into ROMs, I think it would take forever for the chef and a select few beta testers to try and figure out all or most bugs in a ROM. I use Arrups ROMs, and he discloses everything that he can, but ultimately its not the chefs responsibility to create a "perfect" rom for Al Capone is it? Everyone uses different applications which can affect the stability of a ROM completely-for example Opera beta 10. I think its much more efficient to have them release the ROMs and let lots of people try and break them, then come back and fix it. And when bugs arise the are put on a "bug list" to be fixed.
We would never see new ROM releases for months if we waited for chefs to perfect stuff. So the people who just flash and leach ROMs cant help out a little?
Since you are so anxious about having a perfect ROM, why dont you have a go at it? Or is *****ing easier?

MadBeef said:
As for stability I am currently on JoshKoss's latest (1.7) and have yet to experience a single error, crash or hang. And Josh's seem to be the fastest ROMs, definitely of the ones I have experienced anyway. There are a few minor inconsistencies but these are in no way critical. If you want stable I would not even consider Manila 2.5 or any of the "start menu at the bottom" ROMs.
Click to expand...
Click to collapse
X2, This is a very stable ROM. I have been running it close to 2 weeks with no real issues & haven't had to soft reset because of a glitch or hang up.

I have to chime in here and agree with the sentiment of this thread. The application of it is much more difficult that it seems. I have been down this road before, trying to get the chefs to post a comprehensive bug list for their ROMs and while they are willing to do it, it is VERY difficult to tell what is a real bug and what is OE (operator error), confusion caused by loading some application, etc that really isn't a bug or a real bug.
For example, I have been running Sergio76's EVO 3 ROM for sometime now, and have absolutely nothing bad to say about it. Stable as hell, fast, good memory, good battery etc. But some of the other users of the same ROM find 'bugs' mostly caused by putting different shells on, or trying to icon sets.
So, my point is BRAVO! this needs to be done, but let's have a good discussion of how to categorize what is a bug, what is an incompatibility, etc. Because, if we simply list all these things as bugs then we run the risk of scaring folks off of flashing a potentially GREAT ROM all because one or two guys muck it up by hacking the registry and it gets put on a bug list.
I would also like to see a 'standard' way all the chefs list bugs, etc.
Russ

iceman4357 said:
why dont you have a go at it? Or is *****ing easier?
Click to expand...
Click to collapse
bit harsh tbh

MadBeef said:
bit harsh tbh
Click to expand...
Click to collapse
I was actually holding back a lot. Unfortunately 90% of people on here dont contribute anything and just expect stuff to happen perfectly. If its so easy, then instead of creating an entire thread to talk about problems, why not make a "perfect" Rom and contribute.

iceman4357 said:
Since you are so anxious about having a perfect ROM, why dont you have a go at it? Or is *****ing easier?
Click to expand...
Click to collapse
your own *****ing certainly does not help.
read my lips:
-I do NOT ask for a "perfect" ROM
-I just ask for the cook/helper to browse thru the reply-posts, and add known bugs they can confirm, to the first post - the one that contains the ROM
-So any ROM can have a list of known errors, (the the author confirms)

AlCapone said:
your own *****ing certainly does not help.
read my lips:
-I do NOT ask for a "perfect" ROM
-I just ask for the cook/helper to browse thru the reply-posts, and add known bugs they can confirm, to the first post - the one that contains the ROM
-So any ROM can have a list of known errors, (the the author confirms)
Click to expand...
Click to collapse
So the chef should worry about reading the 200 posts that you were worried about reading instead of working on ROMs? I am sure that chef mailboxes are full of people reporting bugs on a daily basis.
There are people other than the chefs that have a good deal of experience that help within the thread posts, that free up the chef to continue experimenting and cooking ROMs.
A lot of "common" bugs are specific to builds, such as the landscape issues vs touchflow(sense), or GPS lag which take a lot of time and programming to figure out. These are commonly known across ROMs and builds.
A lot of smaller bugs are from individual customization errors like with S2U2, Opera Beta, lack of knowledge, or custom tweaking.
Chefs, in my opinion, are here to provide a decent platform ROM for us to costimize individually; not to help each individual person with each custom problem they have.

x2
Montea said:
X2, This is a very stable ROM. I have been running it close to 2 weeks with no real issues & haven't had to soft reset because of a glitch or hang up.
Click to expand...
Click to collapse
can u link me up with the x2 rom u speak about?thanks

oyebee said:
can u link me up with the x2 rom u speak about?thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=572938
We were on about JoshKoss's ROMs.
I've said this for years, something like bugzilla would be good. Not that I have ever used it but something with a bit of structure you know? Flag bugs by component (ie. Manila footprints tab, lock screen, or whatever) then by ROM so the system will know already if it is ROM specific or not. But it still relies on people adding good data, as the saying goes, "Garbage In Garbage Out". An automated config dump tool would be a good step towards that. (an end-to-end "report bug" app would be awesome) After all I don't know what point release of Manila I'm running (1921? 1922??) because I don't really care unless it breaks, or a newer version has more shiny.
Anyway I said this a while ago and we are still "*****ing" about ROMs at a fairly disorganised level, and yet the cooks continue to work their magic, so it can't be all that bad
From another guy who comes on here with not very much to offer yet continues to leech a new ROM once a month or so

Stop the Madness...
Oh Geez....
Yes, I am one of the lurkers here at XDA, having been flashing my phones for years and not really contributing much to the community.
I have made a New Year's resolution to change that, so I am posting more now.
But look at some of the most popular ROMS....
Within hours of a Chef releasing a new version, there are hundreds of posts about it.
From what I gather, 95% if not more of these guys/gals cook up these ROMs in their spare time. They do it because they like to do it. I don't think anyone here is getting rich cooking up a ROM for my TP2. They all have lives and when there can be 40+ pages of posts within a couple days after they release a new version, I don't expect them to read every single one. Especially where a vast majority are people asking how to flash the ROM, how to change the theme or other posts that a simple search would provide the answer.
Most Chefs do post what was fixed, what was improved and a lot of them post issues in their ROMS.
I have spent hours reading page after page trying to figure out an answer to a issue I have had...knowing I was probably not the only one having it.
Do some Chef's not post as much info as I would like? Yes.
Am I going to berate those Chefs for not doing so? No.
Some of the responsibility has to be on the users. Period.
For example, I was and am a fan of the Energy ROMs. But I SMS an insane amount and the newest Leo interface with the HTC messaging client sucked, period. Not to say NRGZ28's ROMs sucked, quite the contrary, they are great. But did those ROMs fill every need that I specifically had? No.
So, I did some research, and I found in a thread where Agent_47 suggested his ROM because he didn't even cook in the HTC SMS messaging client. So, I looked at his thread, flashed the ROM, and realized that I have had no issues with it and am very happy. Stable, works and I don't have to wait 7 minutes sometimes to send a text to someone!
We are all very lucky to have XDA. We are all very lucky to have the Chefs that spend their own time, and a lot of it, to cook up these excellent ROMs for us to flash.
Instead of complaining about the lack of 'bug lists'...perhaps you could create a tool or set something up to help the Chefs better manage those said lists?
That is the spirit that has and continues to make XDA great, if there is something you want, something that you see lacking, then create a tool to fill that void.
If you don't want to do that, then I suggest getting an iPhone, where you are locked into your OS and a slave to Apple and their constant updates and static interface. Cool device, granted, but I prefer the freedom of flashing, the excitement of trying new interfaces, experimenting with new features and lastly, the great folks here at XDA.
\.end rant

Spankmeister said:
I suggest getting an iPhone
Click to expand...
Click to collapse
Let's not get silly

What is the most stable / bugfree ROM available

I use my phone constantly and find even the AT&T stock ROM is not stable. I reboot nearly every day which in itself wouldn't be a problem if I could just reboot in the morning and forget it. However, randomly the ROM gets very very slow and I have to reboot and nearly always just when I need it. I don't need a lot of flash or extras though a little speed boost would be nice. I can install the few extra applications that I need. What I really need is a good, stable ROM.
Any suggestions?

There are lots of good ROMs here. But everyone uses their phone differently. Try one out and see how it goes for you.

verge said:
I use my phone constantly and find even the AT&T stock ROM is not stable. I reboot nearly every day which in itself wouldn't be a problem if I could just reboot in the morning and forget it. However, randomly the ROM gets very very slow and I have to reboot and nearly always just when I need it. I don't need a lot of flash or extras though a little speed boost would be nice. I can install the few extra applications that I need. What I really need is a good, stable ROM.
Any suggestions?
Click to expand...
Click to collapse
Mod seem to close these questions very quickly.
But I like to say that I have tried them all and seem to always revert back to Josh's 1.7 (with Sense 2.1) which can be found here....
http://f1ip.net/Downloads/RhodiumFiles/Roms/Joshkoss/1.7_Full_Final.7z

Thanks but ...
I appreciate your input steviewevie but I am doing something not everyone here does ... actually looking for some opinions.

Josh 1.7 Or Jackos OldSchool

I've tried pretty much every GSM ROM out there for my TP2. The most stable with the most available RAM and fastest speed goes out to Jackos Old School 1.1 ROM without a doubt.

I think there should be a new monthly thread poll open for the 1st week of every month with this exact question.
I can understand how the veterans get sick of this and clutter up things.
On the other hand, I can appreciate having the information available. It is frustrating to search and only find locked threads.
Please mods, take me up on this idea, or at least some version of it.
I wish I had time to flash 10 different ROMs to see which is most stable and fits my needs. Let's leave that up to the people that have time, and allow them to summarize their findings via a regular poll.
Thank you

I find my ROM to be quite stable.
I should release it one of these days.
Would you like to be my exclusive BETA tester?

Deep Shining very good.. Ive tried them all
Deep shining is a very good ROM.. I've tried em all .

I have tried just about every cook and i would have to say eras2r makes the most stable ROM for the rhodium.
http://forum.xda-developers.com/showthread.php?t=585403
This is the only ROM that i have flashed that never crashes or freezes EVER. i have been using bug free windows mobile for almost a year now

Personally, I find EnergyROM to be my favourite. I know you don't want loads of extras but EnergyROM is very very smooth and looks very nice and then you have those extras to play around with when you get bored!

I have been using Energy with Cookie HomeTab 28th May 2010 verison, and works very well.
Very fast rom, even loads and runs Copilot8 without issues, which is more than the HTC 6.5 rom did.

I agree. Mods, why not put up a mini site with a list of ROMs available - such as a "marketplace" and then let users rank and comment with feedback. I've spent a week searching through all of this trying to figure out which way to go. I can't just flash a ROM, get it all customized, then 2 weeks later do it again. I actually have to use the phone to work. At the very least this would allow people to rule out certain ROMs based on their needs.

Ranking a ROM is so objective... Some users expect features, others speed and all the all business users a reliable ROM is a must. Maybe there should be a "stars-voting" system that allows the user to vote for speed, stability, futures, eye-candy etc.?
Anyway I think that a pinned thread with a ROM index would be enough. Just a basic info + developers comment.

Jackos said:
Ranking a ROM is so objective... Some users expect features, others speed and all the all business users a reliable ROM is a must. Maybe there should be a "stars-voting" system that allows the user to vote for speed, stability, futures, eye-candy etc.?
Anyway I think that a pinned thread with a ROM index would be enough. Just a basic info + developers comment.
Click to expand...
Click to collapse
I'm not sure that would help, each entry would be the same:
Content: "list of contents"
Comment: "Best ROM out there - ever"
The contents would change, but the comments wouldn't!

Yeah, because people are too cocksure. I would never call my rom "better" or even "the best". I thought about the chief description as a short note what are goals for each rom.
Ach, and one screenshot would be nice too.

Jackos said:
Yeah, because people are too cocksure. I would never call my rom "better" or even "the best". I thought about the chief description as a short note what are goals for each rom.
Ach, and one screenshot would be nice too.
Click to expand...
Click to collapse
My comment was tongue-in-cheek, but honestly, wouldn't you want the Chef of your ROM to be working on having the absolute best ROM out there? Otherwise he/she would not have very much motivation. Think about it:
"Yup, my ROM is OK, but not the best"
Not a ROM I would try...

So make sure you never try my roms
I think that a rom is a personal combination of programs/skins that fit the chief. But that's just my thought
I saw a guy that said something like that: "Asking on xda what's the best rom is like going to a bar and asking with beer is the best". Different persons, different ROM experiences All about taste.

Jackos said:
So make sure you never try my roms
I think that a rom is a personal combination of programs/skins that fit the chief. But that's just my thought
I saw a guy that said something like that: "Asking on xda what's the best rom is like going to a bar and asking with beer is the best". Different persons, different ROM experiences All about taste.
Click to expand...
Click to collapse
Myself, I always look for the ROM that "Taste's great, less filling".

toadlife said:
I find my ROM to be quite stable.
I should release it one of these days.
Would you like to be my exclusive BETA tester?
Click to expand...
Click to collapse
Toadlife? You're alive and you have a TP2??? Hahah, I remember when you released your kitchen for the Wing, those were the days

Rom Port Team Effort - Let's bring a diversity of roms to our P880.

Rom Port Team Effort
Hello P880 community.
This post has the purpose to put together a group of users / developers, who are willing to participate into bringing a different set of roms into our community.
These set of roms that I'm thinking, can range from complete Sense ports to more customized and maybe less popular roms (like ColorOS, LiGux, FlymeOS, FluidUI, etc..).
What's valid on this thread:
- CM / AOSP (any base we already have) themed (like Samsung TouchUI, Optimus, Blur, etc..). So you can grab any rom (with author authorization), theme it (i mean, not just shove an apk as default theme, I mean neat theming ).
- Ports from other devices (evert port needs to have clear authors permission to port it).
- All users are very welcome, everyone can participate, users with porting / developing skills are needed as well.
The idea is simple, we're not going to use this thread to post the work, this is just a thread to talk about possible projects.
We can start by listing which devices are hardware compatible and the port is "easily" possible.
Roms that can be used as a base for eventual future ports.
CM10.2 - thanks to laufersteppenwolf for compiling this build promptly for this purpose
http://goo.im/devs/laufersteppenwolf/CM10.2//cm-10.2-20140305-UNOFFICIAL-p880.zip
- - - - -
I strongly recommend the use of MultiRom for testing ports and other roms. That way you can maintain your working rom and whenver feeling adventurous you can without going through the hassle of backup / restore / yada yada yada that we are all too familiar with.
http://forum.xda-developers.com/showthread.php?t=2655988
- - List of Devices with hardware similar / close / identical to the 4X - -
- HTC One X
- HTC One X +
- More ??
- Possible roms to port:
Right now would be nice to see a OEM rom, such a touchwiz or Sense
Work in Progress
N/A available
(awaiting sugestions
So, what do you guys think? ? Any users with good porting skills ? I know we have good developers! Ideas? Sugestions?
Write away
A few guides from XDA - They may not be all you need to get the job done, but a LOT of important information is written here. Don't forget to thanks their authors
Guides / Tutorials
How to Port Roms by @saywhatt
How to Port Manufacturer Rom. by @GalaxyUser
How to port Stock/GB/CM7/CM9/ICS/CM10/JB Based ROMs by @Peteragent5
PS - Every work that is possible to port and if someone decides to invest time in it, it needs explicit authors permission.

Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also

JoinTheRealms said:
Sure if a few people want a particular rom i can bring it to our device, but i would much prefer helping first time rom builders do this own their own then they can maintain it also
Click to expand...
Click to collapse
Well, I though about some sort of "voting" to bring a "specific" rom.
Personally, I'd love to have Sense on our device. I had two HTC's before and I miss that Sense interface :b
But far as I'm aware, isn't an easy thing to port.
About your offer, this thread stands mostly with learning. The idea is everyone being able to contribute and more users start bringing roms as their first times. So, thank you so much for lending your help and know how, I'm sure we'll have a fine list of possible ports and then we can talk about how to port them over
Everyone can ask for help and the idea is to everyone who is able to - help.

I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right

laufersteppenwolf said:
I like the idea of this thread, but what would also be quite usefull is a list of available ROMs and their maintainer(s).
Also the list should include ROMs someone is working on ATM, so it cannot happpen that 2 devs are working on the same ROM
However, your idea is good, but porting a ROM not from sorce is quite hard, and might need some smali "hacking" in order to resolve bugs.
But well, we're a community, and I guess we can help each other if needed, right
Click to expand...
Click to collapse
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device

Oh yes finally, have been waiting for a thread like this for a long time me as well would love to see a sense rom on this phone
cm/aosp roms are not that hard to port most of the time u only need the same screen resolution for it to work. (ported a nexus s touchwiz rom over to my old lg optimus 2x) but would have loved to see some oem roms ported over as well, even though it would be a lot harder to port over. but as a wonderful community as this is we might be able to pull it off

MidnightDevil said:
That's correct! :good:
The main point is to learn helping each other who knows in a month or so, today's whiners are tomorrow's contributors
Jokes aside, the first post will be edited in order to structure and add information.
I'm gonna start with compatible devices (the ones that allow porting in a easy way). Ideas? Besides the HTC One X ? I'm guessing the grouper (N7 2012) besides having the same soc, doesn't have the same screen...
PS - (this would be better with an experienced porter) - Maybe we could start with a easy one, and go on from there
I know we have "how to port" threads all around xda ,but each port is different so we can't use "one hat to fit them all" ... or a ring to rule them all, so we should treat each port differently.
However.. I'm gonna put some xda links about porting to bring some light into the matter for who is "new" on this subject... or for whom's feeling adventurous and can't wait to have "their" rom on "our" device
Click to expand...
Click to collapse
You can add the HOX+ to the list as well
About porting, you need to seperate it in two halfs, porting from source, and "winzipping". TBH, I'm no fas of winzipping at all, but some stuff (like sense or TW) can only be winzipped...
BTW, if you need a 2nd/3rd post, just let me know

Personally, I'd like to see a GFlex or even better, a G2 (/mini) ROM for our phone (KitKat, of course )

This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app

Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on

DeHuMaNiZeD said:
This thread has potential
I'm new to this forum,so i dont know whats going on about roms,i see there are few devs working full time.
I think this is the best way to go: Port ALL open source roms,such as we have already,but we need them all.
Second,make a badass kernel,with all features and customizations,possibly 3.4.
Third,and just a suggestion,Make a community ROM?
I really like this thread,and i even more like this OX4 community,you all get along,and i've missed that,i was on a forum that has no frendly people whatsoever.
And,about the roms,the idea is awesome,but i always think of the clash of clans rule,max everything out before going on a higher level.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
MidnightDevil said:
Regarding stock roms, it's an interesting thing, but I'm guessing stock roms are more trouble to port comparing to AOSP or CM.
I remember on the HTC Sensation forums the headaches sense brought to many developers and porters, the bunch of files that needed to be edited, kernel changes (aosp kernel is different from stock / sense kernel in that case).. so Stock roms are maybe harder to port fully.
Right now we have some apks from the G2 (lock screen, messaging, etc..), maybe someone will port some things from the Flex, but the whole base.. hum
@DeHuMaNiZeD , thanks for your reply
The other roms based of AOSP and CM, in my opinion, unless they're different (modded, themed, customized - etc..) but if not, if they are "clean" roms with no changes, then - we have them already I believe you'll agree. (Unless the idea is to test something).
A 3.4 kernel would be something, but perhaps a developer can shed some light here - what benefits would we have from a 3.4 kernel ?
A community rom is indeed long due. This thread is a different subject because it's about *several* roms, ports and tutorials, maybe you would like to create a thread here on General about that? You can start with votes (i believe it's a proper way to do it) with which base should we use (Cm, AOSP, Stock, etc..), included apps (or not), possibly aroma maybe and so on
Click to expand...
Click to collapse
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck

laufersteppenwolf said:
Well, this sounds quite good, but the real problem is: this is a hell lot of work. Also, it needs resources. The sourcecode of a ROM is ~25-30GB. When it's compiled it's about double the size, and takes my PC (8 cores @ 4GHz) about 75Min to compile. Not to mention the time 'til the sources are Downloaded. My 500GB HDD is near to its limit very soon, so sooner or later I will need a new HDD, then I might be able to get another ROM ported, but right now, hard...
Also, why do you need a 3.4 kernel?
For stock ROMs to work, it's your best bet to use AOSP as your base, and then look for what's missing/broken. This, however, means you need an AOSP base first to work with. And AOSP is not always the easiest thing to get properly running.
About the benefits of an 3.4 kernel: None IMO. All you get is a higher version-number, and that's it. We actually already have some 3.4 features backported, and also tweaked the 3.1 kernel quite a lot. So the actual benefits are all in your head (well, except you count bugs as benefits )
Community ROM? Meh, what for? We have so many ROMs already, so everyone should find the one that suits him/her best
BTW: Thread stuck
Click to expand...
Click to collapse
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app

DeHuMaNiZeD said:
Why dont you set up that build server,i think they're cheap atm,or someone could borrow you? It would take a lot less time and effort. that's why i think offical rom support is important,once it's merged to the build bot,its their responsibility.
Sent from my LG-P880 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's not as easy as you might think
I do have access to a buildserver, however I only have 100GB as it's a shared one, so this is genious for official builds, or quick tests/ports. But it isn't ideal for the long terms.
Also, having it official doesn't mean you're done you need to update it, and also fix it when it's broken. 'cause when it's broken, it can mess up the whole build process of the buildbot
But in general, you're right, having it official does help a lot

{fd}ware said:
Does anyone of you have a link to the latest CM10.2 (Android 4.3) for our device?
It seems like it's not anymore on get.cm and I wanted to start porting a TouchWiz (Note 3) ROM to our phone when I have free time
Click to expand...
Click to collapse
I can't find them either, but I'm on a tablet so I can't look properly. 
 @laufersteppenwolf, do you have any *spare* 4.3 build?

MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now

laufersteppenwolf said:
LOL, no, I do not, but gimme a few hours and I'll have one
Syncing right now
Click to expand...
Click to collapse
Thank you

{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
Nope, I actually never "winzipped" a ROM

Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
MidnightDevil said:
I can't find them either, but I'm on a tablet so I can't look properly.
@laufersteppenwolf, do you have any *spare* 4.3 build?
Click to expand...
Click to collapse
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
{fd}ware said:
BTW, did anyone tried to port a ROM this way? http://forum.xda-developers.com/showthread.php?t=2245786
Click to expand...
Click to collapse
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.

Adam77Root said:
Lot of things to comment on here. Very good initiative I have to admit. I'm sure I'll have more ideas as the discussion evolves.
Similar hardware: You can add HOX+ as laufer said. Very minor differences are there only.
What I would personally prefer is TouchWiz, at least Nature UX 2.0, but new S5 UI is also really awesome. I liked Sense till 4.5, but 5.0+ versions are now out of my 'inner circles'. Especially what I don't like is the UI.
Few suggestions:
FlymeOS (from Meizu MX) - I got 2.0 booting last summer, but had touchkey issues (they were freezing the device lol) and never released it. Nobody ever booted 2.0+ on other Android devices yet.
Porting LG roms might be the best start, I think porting full Optimus G system wouldn't be that hard. Just a pain in the *ss merging process.
What we mainly need is same screen size (unless you wanna resizing 100+ apps ). Similar SoC is a good extra, but that's very limited. Also, it's better to avoid Qualcomm SoCs to port from, it's extremely hard, there are a lot of code changes in low-level code which just make the device get into deep segfault cycles. :cyclops: Even Exynos is easier to port from, trust me. I got SGS3 leaked 4.2 booting on the O4X last autumn.
Big issue we have to note: In 4.2, Google radically changed graphics libraries code. We have old, 4.1.2 blobs and those need hacks in libgui.so and libsurfaceflinger.so to function properly (in 4.4+ libEGL.so, libGLES_v1_CM.so and libGLES_v2.so also need a change). Here comes the problem: Manufacturers do change these libraries, mainly adding Wi-Fi display and HDMI support code which other blobs rely on. Of course we can't just replace these libs, graphics wouldn't function that way. Either we have to guess those function signatures and reimplement some stub in the code, or use new blobs, i.e. what I did in Omni. But y'all now those are not perfect _yet_.
Regarding newer kernels: If, I emphasize, IF it's properly ported, it would cause a noticeable effect on overall performance, battery life, etc. What do I mean by proper porting: All machine-specific code must be updated to Nvidia/Google upstream, no excuses! I don't say anything for sure, I didn't check it much, but kholk didn't do this merge. His kernel still uses 3.1 files with slight modifications to be 3.4-compatible. What I mean would be a very long and painful process, but would surely benefit after all. 3.4 has no Android branch, mainline Nvidia Tegra kernel does only have Linux support, it might be even harder. 3.10 is maintained by Google for Android, issues I have found so far: No graphics driver support for T2 and T3, have to forward-port it and I didn't find core Android components like wakelocks, earlysuspend, etc. Weird.
A little related story: I initially started working on MultiROM so I can test and port different roms while I can keep a stable rom for myself and there'd be no need for reflash then. That's what I can suggest. Use MultiROM, it has so many capabilities! Maybe it's better with kernel sharing so you don't have to wait for hardboot on every reboot (which one needs a lot if porting). @MidnightDevil you could add this to the OP maybe.
Here you are! Compiled this because wanted to start porting from Note 2, but finally worked on Omni more and abandoned it.
That's way too generic unfortunately.
Quick suggestion for you port: Use Note 2 base with Note 3 features. Note 2 has the same resolution and you won't need to resize.
Click to expand...
Click to collapse
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2

laufersteppenwolf said:
Dang, you've beaten me but mine's as fresh as it could be
HERE you guys go, for all who need the newest CM10.2
Click to expand...
Click to collapse
Just don't delete the sources, you might need them in the close future.
I think we should create a schedule about what to do. As you all know, good buildings all have good grounding. So let's get started from the very beginning I say. First fix remaining bugs in MultiROM, then create a unified kernel so users don't have to choose. Very likely this is not possible as people think different so just make all kernels hardboot compatible. After these we have a solid base for starting all the work. Of course this cannot be done if not everybody is involved. Both devs and users should share a part in this magnificent journey.
(High expectations, I know. )
Sent from my OmniROM-powered LG Optimus 4X HD

Noob Friendly Q and A Help Thread

I have been on the Nexus 6 since early December 2014, and for me, as with many others, the Nexus 6 was my entry point into the pure Google experience, and my simultaneous departure from TouchWiz. From the beginning, I was a noob on this device.
So, after 4 short months, I have found that the rom threads have become congested with endless questions that are not germane to the given rom. The more popular a rom becomes, the problem intensifies.
I can imagine how frustrating it must be for a developer whom has worked hard, flung his or her creation to the xda shadowed wilds, only to return to a thread that has become a thicket of repeated questions.
Compounding the problem is that each developer has a different approach as to how he or she wishes his or her thread to be managed, which in turn can be confusing to any user. Some developers seem happy to remain ensconced in the daily comments, while others have a palpable disdain for off-topic quotes.
Irrespective, I think each has a tipping point, and thus I am sure that none is immune from becoming a bit jaded after a time.
And yet, we still have the very real phenomenon that this device has a learning curve, is available across the globe, and thus the questions still recur. Further, it is in many people's natures to either want to help or at least be cautious prior to rooting their device, etc.
So, I thought it would be fitting to provide a place for all to ask whatever they want. As the title clearly states, this is a noob friendly place, so please feel free to ask whatever you would like about this device. I am certain that all here on these forums would rather you learn what you need prior to availing yourself of the amazing array of resources in the development and themes and apps sections of these forums.
A few preliminary guidelines for this thread:
This is a noob-friendly thread, so ask whatever you like
Read the initial posts of the rom thread, as well as the last 10 or so pages of that thread, before you flash the rom you want. It will give you an idea of how the developer handles his or her thread, the tools you need before you get started, and
Please respect your fellow forum members, developers, and the moderator staff. Moderators have a thankless job, and I can assure you that it is absolutely no fun spending hundreds of hours on what amounts to a volunteer position without benefits.
Towards that end, please read the rules; they are the first post on every forum here on xda.
Thank everyone that develops, and please donate to anyone whom you believe is worthy of your extra gratitude. Donations are never required, but they do motivate those that do the hard work on these forums.
Never downgrade your bootloader. Ever.

I’ve split this into categories so that folks will have some basics right upfront.
1.First Use
1.1:You almost certainly will want to unlock your bootloader, inject root, recovery, etc.
I suggest reading the All-in-One Beginner’s Guide, where you’ll find everything you need to get started.
1.2. Learn Fastboot:
Yes, you have a Google device, and it is very easy to flash anything you want with a few simple command lines. Put bluntly, on Nexuses, the manual steps are very easy.
Hie yourself to this authoritative thread written by the prolific dev and highly respected forum member @rootSU.
1.3:Toolkits: Toolkits are a fantastic way to do all of this from the jump. There's nothing wrong with toolkits themselves; they can be great, useful tools, but please learn to do the steps manually. Why? Simple. If anything goes wrong, and it can, knowledge of fastboot will save you; no knowledge of it, you're waiting on help from others, or learning from scratch that which you should already have learned. Further, should help arrive, that person helping you is bearing two burdens, helping you first learn the basics of command line, and solving your problem. That is downright unfair. OK, onto the toolkits. You can find them in the development sections, specifically:
Wugfresh's Toolkit for Windows Operating System
Nexus One-Click Mac Toolkit for the OSX
Skipsoft Unified Android Toolkit for Windows
1.4: Decrypt or Not Decrypt:
Please note: Decrypting your device will wipe your device, so if you are going to decrypt, please do so before taking all of your time to setup your device the way you like it.
IF you want to remain decrypted, put the zip file located in this thread on your device, throw it in your cloud storage (Dropbox, &c), keep it in your pocket, think well of that file.
IF you want to remain decrypted, that zip should be the LAST file you flash before any new rom or kernel is flashed, or if you are unsure if a rom has a kernel that will force encrypt your device.
There are differing opinions as to the wisdom of decrypting, and I don’t care whether you think it is better or worse; people want to do it.
You can learn more about it here, and can accomplish the task using the link previous link or using any one of the aforementioned toolkits.
1.5: Recovery:
You almost certainly want to make a backup of your device prior to tweaking, flashing an updated nightly, or testing a new rom. Recovery for our device can be found here.
You may want to put a nice theme on that TWRP, go here. Hint: The developer whom does those themes keeps up with each iteration of TWRP, and if a new version requires a new theme, check the theme thread before you update your recovery.
1.6: Starting Over
I believe that this community owes a special thanks to @Q9Nap and @scrosler as each has provided us with amazing tools to return to stock or upgrade your device from 5.01/5.02 to 5.1, sans the need to revert to stock 5.01.
Please go to http://forum.xda-developers.com/showthread.php?t=3066052 thread for flashable zips of entire 5.1 roms or modems ,or this Android File Host page from SCrosler for flashable 5.1 modems + bootloaders...https://www.androidfilehost.com/?w=files&flid=23050
https://www.androidfilehost.com/?w=files&flid=23050

2. Choosing a Rom: Roms generally fall into four discrete categories:
2.1: Stock-Based – these are hewn from Google source, and typically come preinstalled with everything you will need to be up-and-running. Whatever tweaks, performance or otherwise, are added, the rom will most certainly similar to stock, hopefully better than stock.
2.2: AOSP-Based – these are built from the Android Open Source Project, and purists may think of them as closer to what Google intended. You will typically need to flash a Google Apps (Gapps) package separately from the rom itself. Some of these have inline kernels, or stock kernels, but they typically have everything you need baked right into the mix. There is an incredible variety of unique and wonderful roms from which to choose that fall into this category.
2.3: Original Development – Although the lines tend to blur, suffice it to say that roms in Original Development contain something original that merits a rightful place of its own, away from the crowded Development Forum. You will find kernels as well as complete roms in this section.
2.4: Hybrids – The vast majority of roms fall into this category. Much of the joy of Android is customization, and most roms in this category are feature-rich and packed with things, almost more than you will ever use.

Customization - Enhancing the Senses
Rom Customization:
Roms are popular and highly useful, but they are also fun. Instead of using a boring, stock phone laden with what amounts to another's idea of what you should have on your device, you are in control. This starts with how the phone looks. Yes, your phone can and should look exactly how you want it.
Disenthrall yourself from the madness that is a stock looking phone and apps, and stare with wonderment at beautifully themed apps.
1. Hard-Coded Themed Apps:
Anyone can run a themed app, even on a stock, rooted rom. These forums are riddled with themed app threads. Some suggestions to start:
1.1: Team BlackOut, the hardest working devs on xda are there, please go into their thread, enjoy the camaraderie and the beautiful apps they make. Be sure to thank and donate if you are so inclined. You will find themed versions of scores of apps, all available for free from their updater app.
1.2: XDA Recognized Themer @cerj has done a terrific job theming many apps on his own, and of course with the help of other themers. He is a terrific resource and a good friend. Check out his Blue DeLucia and Krome-X apps.
2. Theme Engine and Layers
Many Non-Stock Roms make use of one of these two basic tools that allow you to theme your entire phone. Suffice it to say that these are mutually exclusive means of attaining a beautifully themed rom without much hassle on your end. The CyanogenMod theme engine has its fans, and the fine devs doing the Layers app consider their work stellar (as they should); both are excellent.
2.1: Layers: If your ROM has Layers, and the app is not already on your phone, you'll need to download the free app from the Play Store. You'll find an abundance of themes in the Official MEGA RRO Layers Overlays Collection.
Special mention to one of the finest themers whom I've come to know on these forums; as RRO has had met the steep ramp-up with stunning strides, this terrific dev has been there, every step of the way.. @daveyannihilation, a tosser, wanker, and a very Gary dude, please help...I mean thank this man. He's everything and more. Please help me, inasmuch as I'm far more concerned about the degree to which I'm both a wanker, and a tosser, not to mention completely Gary.
2.2: Theme Engine: If your rom incorporates the CyanongenMod 12.0/12.1 Theme Engine, you can find a ton of beautiful themes in the Official MEGA CM12 Theme Engine Thread.
Please buy the themes you love. Free themes are terrific, but I always believe that people are more motivated to continue delivering these terrific tools if you support their hard work. Buy the damn themes, and don't be a cheapskate...there's enough whining in these forums to make most want to wretch.

Kernels and Tweaking
If you wish to flash a kernel, here are a few guidelines to get you started
Note: Most all of this was written entirely by @wrongway213.
1. Kernel Basics:
1.1: Stock Kernels: You can keep a stock kernel if that is with which you are comfortable. The stock kernel will force encryption, and there are modified stock kernels that will not force encryption.
1.2: Custom Kernels:
1.2.1: Hotplugging: Hotplugging is basically the background process going on telling your phone when it needs to bring CPU cores on and offline. This controls how much power your phone consumes - both how much battery it drains and how snappy it feels. You can use a kernel tweaker app (more below) to set all kinds of things in the kernel, including how hotplugging is done. Different kernels have all sorts of different hotplugging options.
As of 5.1, stock kernel uses all four cores online at all times as opposed to hotplugging. This is said to save power. Some kernel developers have adopted this as the default for their custom kernels, but they are still tuned very differently than stock. The user can still choose to revert back to hotplugging if they prefer it. Prior stock kernel, including 5.0X Lollipop, use something called MP-Decision to scale your frequencies. Some are of the opinion that MP-Decision is entirely too aggressive in how it handles this. It attempts to give the user a snappy and smooth experience, but in the end it mainly drains battery. The same smooth experience can be achieved via hotplugging properly on a custom kernel, and your battery will thank you for it.
1.2.2: Governors: Another awesome thing you can do when you flash a kernel is control the governor it uses. Stock kernel uses an interactive governor, which responds to user input and is generally considered to be a pretty good governor, even for custom kernels, However, it is often modified on these kernels, or at the least assisted with hotplugging in a different way than stock. This governor has been modified by @Imoseyon for leanKernel, one of the most popular kernels for our device, and a great place to start if you want to know if custom kernels are for you or not. Some prefer to use conservative, which is much less jumpy than interactive - meaning it does not scale frequencies up or online cores as quickly as interactive. This governor has been heavily modified for our device by @franciscofranco (Franco Kernel dev), so it is a much more viable option for those whom want to conserve battery and still get great performance. There are many different governors offered with different kernels - you can change your experience on the very same kernel by changing governors sometimes. Or you may find that you flash a new kernel and find a whole new set of governors that are more your style. This is all about trial and learning what you like, as none of us can know what is best for your use.
1.3. Kernel Use and Utility:
1.3.1: Wakelocks, An Example
A kernel can do many things if the kernel dev chooses to make it, or to give the user the option to avail such options, or can be omitted entirely if running stock. Though not the source of your wakelocks, kernels can disable wakelocks can control or disable them. This is a good example of the separation of a kernel's ability and a kernel's use.
1.3.2: The Domain of the Kernel:
Many kernel devs choose to leave the kernel footprint small, and allow the ROM side of things to handle as much as possible. Some kernels use the existing ramdisk that comes with the ROM instead of inserting their own to ensure they will play nice with all roms. Other kernels are highly customized and completely and totally change the feel of your device. Most are somewhere in the middle of these extremes.
1.3.3: What Your Kernel Does Not Control:
Your kernel does not control your radio, your WiFi, etc, so thus your phone calls, your data, your mms and sms messages are not impacted by flashing a kernel. Sometimes flashing a kernel may somehow cause something that is controlled by the ROM side of things not to work correctly - this is not the norm, though. If you are having these issues, you should look to your ROM first.
1.3.4: Random Reboots:
Random reboots are something that may be caused at a kernel level. If you encounter one, you should immediately on boot (ie, right after the random reboot) open your file explorer go to the folder:
sys/fs/pstore
There should be an annotated-ramoops file and a dmesg file (think of these as kernel logcats). Open the files as text, copy and paste to www.hastebin.com and send the link to your kernel developer. This will help him or her determine if it the reboot was caused by the kernel, and if it can be fixed.
1.4: Sound Practices:
1.4.1. Avoid Multiple Kernel Tweaking Apps:
The use of multiple kernel tweaking apps is contraindicated. If your rom comes with a performance app but you like to use your own instead, freeze your rom's performance app in (using the built-in App Manager, or with an app like Titanium Backup) and clear its app data prior to using your app of choice. Most kernels have an app that is either directly associated or supported by them, or recommended to use with them. Find this out in the thread before you tune your kernel, as having the right options available and interfaced correctly makes it much easier to do so. It's also good practice if you have flashed a custom kernel already to re-flash your rom before flashing another to ensure settings stick properly. This is not always necessary, but it only takes a minute and it's better safe than sorry.
1.4.2: Default Kernel Settings or Using Terminal Command Line:
Some kernels don't even require an app at all. A few of them are tuned on initial setup via Aroma installer - you set your values and can leave it at that. Others can be tuned directly via terminal emulator.
1.4.3. Kernel Tuner of Choice:
Most kernels require some sort of an app to set your values. If your kernel does not come with a particular app associated with it, there are a few options for you. A popular option has always been Trickster Mod. This app offers the basics that you need if using a kernel that does not have a whole lot of odd modifications and is good for beginners who are using a kernel with no recommended app. Advanced users often use Synapse - it is a very confusing app and definitely not for beginners, but it gives you control over basically everything your kernel has to offer. Kernel Auditor is something in the middle, as it does not allow you as much control (or confusion) as Synapse, but it can do a lot that Trickster can't. It's a great starting point for those of you using a kernel with needs Trickster does not meet, or a good place to jump to if Trickster is just getting old, but you're not ready for Synapse.
1.5: Afterwards:
To be sure, there is plenty more reading to be done, depending on which kernel you choose to flash and how advanced you would like to get with it. This is just meant to give those of you who don't know why they would want to do something like flash a kernel a starting point. The decision is yours.
Happy flashing!

Thanks for this man! I agree this needed to be done. It will be very helpful!
Войн Дух

So... If I have a OnePlus One can I use the decrypt file you posted in the second post? I'm kind of a noob... [emoji5]
In all seriousness, XDA is better for having someone like you here to help out.
Watch closely people... You might learn something.

Now I just need to get one lol
Awesome work buddy!

If you need more posts added in or want to transfer a post ownership to another person, just let the mod team know (or you can hit me up as well). Anything to reduce the number of non-essential, non-logcat-attaching posts from the Dev threads is most assuredly welcomed.
Good job and keep up the good work.

If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance

rootSU said:
If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance
Click to expand...
Click to collapse
I knew you'd pounce on that.
My apologies good sir. You will get one entire block in that section...please think of this as a beginning of things.
Sent from my Nexus 6 using Tapatalk

micmars said:
I knew you'd pounce on that.
My apologies good sir. You will get one entire block in that section...please think of this as a beginning of things.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yeah sorry I always do.
Its nothing personal. Nothing to apologise for. I just think a little disclaimer could be put in. I can draft a very small sentence if you like... Or not

Excellent idea, this thread is, Mic - thanks for endeavoring to provide a one-stop-shop resource for all. Let me know if I can be of any assistance along the way.

Very useful thread. Will be checking in to help whenever I can. Thanks @ micmars
TaPpEd FrOm My N-sIx

rootSU said:
If you're going to mention us "traditionalists" (its nothing to do with tradition) I think it only fair that you explain the reason why we dont recommend toolkits for the uninitiated @micmars, for balance
Click to expand...
Click to collapse
Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02
I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way.
Sent from my Google N6 on VZ

DebianDog said:
Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02
Click to expand...
Click to collapse
Yeah i agree. That's why it should be a disclaimer rather than an order
DebianDog said:
I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
I use folder sync as a plug in to Tasker.
Every time I close my camera app, I use bash shell to look for new files in DCIM and move them to a holding location. I then use folder sync under the same trigger, to open up an SFTP connection to my NAS at home and upload the photos immediately. There is one draw back though. I was taking 4k videos the other day and trying to push 1.5GB over sftp voa hspa is not good for battery, so I need to revise that one.
Also a run a times folder sync every couple of days syncing up my /sdcard with my NAS backup directory, over WiFi whilst I sleep.
Also every Saturday at 3am, my phone reboots, takes a nandroid then syn a that to my NAS too.
As you can imagine, I find it difficult to lose files

DebianDog said:
What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way
Click to expand...
Click to collapse
Same here. Only takes a minute.

DebianDog said:
Toolkits, like a decrypted device, are a double edged sword. I have been screwed over by tool kits in the past but I've also been saved from doing something stupid. I do like tool kits that include a command line option and are verbose enough to show you exactly what they're doing. My $. 02
I do have a newbie question though. This is my first device without SD card. In the past I was never gun shy about doing anything because I knew worst case I could recover or at least have my install zips and titanium backup to rebuild . Now a days I am sometimes scared to wipe my pseudo SDcard. What are you folks doing to protect yourself? I have been saving off data to the PC before anything major but it seems like there should be a better way.
Sent from my Google N6 on VZ
Click to expand...
Click to collapse
On the go storage, tiny little things, I know many themers, and rom devs, use the crap out if them.
I have seen these things sold at very reasonable prices, at brick-and-mortar retailers or online.
I personally back up my entire card to my computer on a weekly basis, and throw the entire thing into my Dropbox.
Sent from my Nexus 6 using Tapatalk

Let me start by saying thank you.. I recently purchased evo 3D, then flashed a nexus 6 ROM and recovery.. My question is, should my phone be this hot.. It's lethal it's so hot.. I'll wait for your trusted response..
Seriously, for all that know mic, he is a beacon of knowledge.. This thread will not only widen your vocabulary , it will contain a plethora of information and innuendo

cerj said:
Let me start by saying thank you.. I recently purchased evo 3D, then flashed a nexus 6 ROM and recovery.. My question is, should my phone be this hot.. It's lethal it's so hot.. I'll wait for your trusted response..
Seriously, for all that know mic, he is a beacon of knowledge.. This thread will not only widen your vocabulary , it will contain a plethora of information and innuendo
Click to expand...
Click to collapse
your phones cpu can get to 100C. thats when itll automatically shut down/reboot to cool off. but try as hard as you can, i bet youll never reach it. anything below is normal, depending what you are doing. now you say hot, whats your cpu temp? as feel does not give you any temperature. all feel does is tell you if something is hotter than or cooler than your hand. and if your hand is cooler, itll make the phone feel much hotter. so, when talking about being too hot, we need an actual temp to go with it. i say that because many people report a hot device, when the temp is around 40C, when normal body temps average around 37C.