Related
In the Super D thread, somebody suggested a 'ROM Hall of Fame.' I've decided to do something similar. This thread is about the ROMs that I recommend for different uses. It's difficult to explain, but you'll understand soon enough. Anyway, let's get on with it.
For Newbies/Inexperienced Users
For people who are just getting started with rooted Android, there's only really one recommendation that I can make, and that is, of course, the ever-popular CyanogenMod. This is an Android 1.6 build, and it's probably the most famous of all custom Android builds. Originally built upon JF's build of Android, CyanogenMod has now become a build in its own right. It's incredibly stable, it's fast, and it's really all that you'd ever need for your phone. If you want something that's simple, but still really good, CyanogenMod is the way to go.
For More Advanced Users
There are two builds that I can whole-heartedly recommend for the more advanced Android user. In the same way that CyanogenMod started as a modification of JF's build, these two builds are heavily based upon other popular builds of Android.
The first of these is WG-Build, a modification of CyanogenMod. This is my current everyday ROM, and I really like it. For more information on the exact changes, check out the thread, but the main difference between WG-Build and CyanogenMod is the kernel. Wes has been working hard on his custom WG-Kernel, which is the driving force behind the speed of his build. It comes in several different varieties depending on what you want. I use the CFS with RAM Hack, because CFS is more stable than the faster BFS, and the RAM hack is of great use too. WG-Build is one of the fastest builds you'll find, and it is my personal recommendation.
However, you may prefer Super D. This ROM is essentially a modification of a ROM by Dwang, although it has come a long way since then. This ROM is thought by many to be the fastest available, although from personal experience, there is little difference between Super D and WG-Build. This is more of a personal choice as to which build you prefer, so try them both. I prefer WG-Build, but you may prefer Super D. It is your choice.
Eclair ROMs
TO COME.
Hero/Sense ROMs
Again, TO COME.
Guys, is this a good idea? If you think it is, let me know, but if you think it's a waste of time, then I'll drop the idea.
Yeah man keep it up, im on cyan but if your saying the other roms are quicker ima give it a go!!
Might I add, try and link to as many pages as you can!!!
In my opinion this idea is good. There are many roms for the g1 available atm...
But i would modify it a bit:
I would prefer a kind of table or database with a quick overview about the current ROMs.
Having this, u can still make recommondations.
Example:
ROM: Eclair_2.1-v1.5 G1
dev: manup456
base: 2.1
devices: MT3G 32B
Features: Camera, LWP [...]
Issues: FC latin_ime [...]
.
.
.
In addition, we could maybe collect ratings (poll?) on facts like speed, look, stability... so that everybody can pick his rom according to his personal criterias...
Che123 said:
In my opinion this idea is good. There are many roms for the g1 available atm...
But i would modify it a bit:
I would prefer a kind of table or database with a quick overview about the current ROMs.
Having this, u can still make recommondations.
Example:
ROM: Eclair_2.1-v1.5 G1
dev: manup456
base: 2.1
devices: MT3G 32B
Features: Camera, LWP [...]
Issues: FC latin_ime [...]
.
.
.
In addition, we could maybe collect ratings (poll?) on facts like speed, look, stability... so that everybody can pick his rom according to his personal criterias...
Click to expand...
Click to collapse
Yeah, this is exactly what I'm aiming for. It's sorta similar to the ROM Database at AndroidSpin.com, but it's a different idea. I might actually ask Simon if he can help me with it.
bolmedias said:
Yeah, this is exactly what I'm aiming for. It's sorta similar to the ROM Database at AndroidSpin.com, but it's a different idea. I might actually ask Simon if he can help me with it.
Click to expand...
Click to collapse
But at androidspin there are too many details and no userrating. And it's not up2date
ATM there are daily new roms or updates, and the only way to make rom-overview useful is to keep it updated
Sounds very good and if it's kept simple and informative this will be very usefull - not only for newbies
I will keep an eye on that
Che123 said:
But at androidspin there are too many details and no userrating. And it's not up2date
ATM there are daily new roms or updates, and the only way to make rom-overview useful is to keep it updated
Sounds very good and if it's kept simple and informative this will be very usefull - not only for newbies
I will keep an eye on that
Click to expand...
Click to collapse
I'm gonna ask Simon if he's interested by this idea, just to see if he is or not. But I will try and maintain this myself, for sure.
The idea is good, but, how do you decide which way is more informative? If you settle on a "feature's list" like Che123 suggested, then you take out the actual experiences of people who've used the roms out. On the other hand, if you approach it like you first did, stating your opinion on which roms are best suited for what, then the information is narrow (limited only to the roms YOU've tried), subjective, and (some might argue) possibly skewed. A combination of both, I'm afraid, would ultimately pick up more of the flaws of either method than the benefits.
I personally believe the problem lies in the solution not being so clear-cut. There's just too many roms for all of them to be drastically different, and most often the difference between them is the availability of feature(a) against feature(b). In some cases, the only difference is the developer, or the name of the rom! (but just a few cases.)
I think an approach that might work, maybe, would be to make a list with:
ROM Name:
Feature 1: [X]
Feature 2: [X]
Feature 3: [X]
Feature .: [X]
Feature .: [X]
Feature .: [X]
Feature n: [X]
Highlights:
Opinions:
Features 1-n would be what we consider standard on roms (a2sd, compcache, swap, etc). We'd list highlights with things that actually make the rom different from others, for example, WG's kernel against CM's kernel, or X's themed rom as opposed to Y's un-themed rom, etc.
Opinions is where the meat would be. User experiences would be listed so that we know to expect force-closes, or slowdowns, reboots, or maybe just a smooth-sailing all around. Might even be a long comment section for different users and with an option to separate good opinions from bad opinions from neutral opinions so that we can read all the bad or all the good in one fell swoop rather than have to follow through the usual ranting and fighting that goes on at the forum already.
Anyway, I'm rooting for this, I just wish it were easier.
And to further add to what you suggested in your original post; another field that describes "Target Audience:" (Beginner, Intermediate, Advanced, Multimedia, Professional, Linux Power-User, etc.).
Fount this over in the Sapphire section
http://forum.xda-developers.com/showthread.php?t=618220
It looks nice so far but is still short of data...
Maybe you're interestet in collaborating with him?
jubeh said:
The idea is good, but, how do you decide which way is more informative? If you settle on a "feature's list" like Che123 suggested, then you take out the actual experiences of people who've used the roms out. On the other hand, if you approach it like you first did, stating your opinion on which roms are best suited for what, then the information is narrow (limited only to the roms YOU've tried), subjective, and (some might argue) possibly skewed. A combination of both, I'm afraid, would ultimately pick up more of the flaws of either method than the benefits.
I personally believe the problem lies in the solution not being so clear-cut. There's just too many roms for all of them to be drastically different, and most often the difference between them is the availability of feature(a) against feature(b). In some cases, the only difference is the developer, or the name of the rom! (but just a few cases.)
I think an approach that might work, maybe, would be to make a list with:
ROM Name:
Feature 1: [X]
Feature 2: [X]
Feature 3: [X]
Feature .: [X]
Feature .: [X]
Feature .: [X]
Feature n: [X]
Highlights:
Opinions:
Features 1-n would be what we consider standard on roms (a2sd, compcache, swap, etc). We'd list highlights with things that actually make the rom different from others, for example, WG's kernel against CM's kernel, or X's themed rom as opposed to Y's un-themed rom, etc.
Opinions is where the meat would be. User experiences would be listed so that we know to expect force-closes, or slowdowns, reboots, or maybe just a smooth-sailing all around. Might even be a long comment section for different users and with an option to separate good opinions from bad opinions from neutral opinions so that we can read all the bad or all the good in one fell swoop rather than have to follow through the usual ranting and fighting that goes on at the forum already.
Anyway, I'm rooting for this, I just wish it were easier.
Click to expand...
Click to collapse
I think the soloution is a mix of everything: Facts, general user rating and your recommondation.
A featurelist for the common features, like you mentioned above are a good idea too...
If we got all the features-data in a database we could also build a automatic rom-chooser
i would add following things to the list:
Base: (there are currently 1.6, 2.0, 2.01, 2.1)
Supported Devices: (there are always people flashing a wrong rom and wondering why it's not working )
and a link to the thread of course.
domenukk said:
Fount this over in the Sapphire section
http://forum.xda-developers.com/showthread.php?t=618220
It looks nice so far but is still short of data...
Maybe you're interestet in collaborating with him?
Click to expand...
Click to collapse
I wasn't really intent on doing a piece of software, and besides, it misses the point.
Jubeh, I think that you've hit the nail on the head there. What I'm thinking of with this thread was to eliminate the need for people to read through each individual ROM's thread in order to find out if there are any problems, how fast it is, basically exactly what you've suggested. It's about user experiences.
Actually doing this as a forum thread will be quite difficult, though. Any ideas on how we could do it?
which are the differences between cfs wg build and bfs wg build?
marcocrash said:
which are the differences between cfs wg build and bfs wg build?
Click to expand...
Click to collapse
Stability and Speed. BFS makes for a faster ROM, but Wes himself has said that there is an issue with memory leakage. CFS is not as quick, but it's far more stable.
This is the exact sort of question that I want this thread to answer about each ROM.
i don't really like the idea of an desktop app either.
I would like to see something web-based. But as you said: This won't be very good as forum thread. Maybe you could ask someone from xda, if they are willing to give you same webspace for this project. Maybe in cooperation with other users you could build a database for all kind of devices
Somebody could develop an app thats based on the database of the software maybe?
for afaik his software uses some sort oft sql. maybe eaven mysql. have a look web developers
http://forum.xda-developers.com/showthread.php?t=618220
Stability and Speed. BFS makes for a faster ROM, but Wes himself has said that there is an issue with memory leakage
Click to expand...
Click to collapse
Wes himself uses BFS+Ramhack, according to his signature
OpenVPN
Please add that OpenVPN works out of the box in Cyanogen ROM, just install Tunneldroid or openvpnGUI.
In Dwang, it could support it, but you need to overwrite some libraries and add openssl and crypto libraries, thou Dwang rom has TUN built into the kernel.
I have not tried OpenVPN on super-D or WG.
Hey guys,
since i'm currently a flashaholic and dont want to stick with sense rom's (i just dont like them, can't say why). I'm trying around a bit, mostly with GPe rom's.
But whats the real difference between GPe and CM based rom's?
- Which rom/version is more stable?
- Which rom/version got the better perfomance/battery life?
I know that CM based roms are having more features and looking nice (at least for some peoples).
But i want a overall good performance, stability and moderate batterylife.
Thanks in advice
kewkie said:
Hey guys,
since i'm currently a flashaholic and dont want to stick with sense rom's (i just dont like them, can't say why). I'm trying around a bit, mostly with GPe rom's.
But whats the real difference between GPe and CM based rom's?
- Which rom/version is more stable?
- Which rom/version got the better perfomance/battery life?
I know that CM based roms are having more features and looking nice (at least for some peoples).
But i want a overall good performance, stability and moderate batterylife.
Thanks in advice
Click to expand...
Click to collapse
You've to try the roms for choose which is better.
Howeve the GE have some features like beats audio and some thing from sense, and the update are from htc with the latest release of android.
The CM rom have some features like the editing of status bar and so on, and are built from developers
Well, i dont hear that much music, so beats-audio is useless, not at all, but a bit.
I'm tired of testing around
Just thought you guys can share your experience with some of your used roms
kewkie said:
Well, i dont hear that much music, so beats-audio is useless, not at all, but a bit.
I'm tired of testing around
Just thought you guys can share your experience with some of your used roms
Click to expand...
Click to collapse
The problem is that mod don't like thread as: which rom is better for you?
This rom have a better battery then this?
And questions like this
Yeah i know, but it actually isnt a thread like this
I just wanna hear some experience
Google play edition roms are built on HTC's framework, or they were when it released. AOSP roms are actually built from AOSP framework using the libs and drivers and device trees that have been custom built for the one.
So the foundation of the Google Play edition, the part the user never sees, is a lot closer to stock sense from HTC minus the interface and launcher, while CM and other AOSP roms are built from AOSP style source code (CM from their source, others from their own custom source code some of which is truly custom and some of which is modified from CM source)
There's a lot of advantages to running AOSP source code based romms if you're going for an AOSP rom, but theres also a lot of users that can't use adb or fastboot and don't want to learn how and don't care to read into a rom thread, and the google play edition stuff is nice for people who want a phone with a stock google launcher, that doesn't have the sense interface heft, and just want things to work with an out of the box type experience. You know the type, they don't do a clean install for six months and wonder why the headlights in their car blink and settings force closes when they press the volume rocker.
There are certain apps that will work with the GPE and others that will only work with AOSP source, so on and so fourth. Half the people are better suited for GPE rom's and stockish foundations and then the other chunk of the people only buy their phone so they wipe it till its raw getting HTC stuff off and get custom AOSP source based roms on instead. It all depends on the user and what's better fitted for their experience.
In your case if you're not running sense roms at all and you like to follow development from what I've seen because I've seen you on here a good bit, I'd get into some real AOSP for a bit and see how you like it. The good thing about AOSP is that it's infinitely customizable and any user that wants too could be theming in a week and compiling/merging source in a month and cooking roms for their personal use. Most people way less than that. That doesn't mean that the devs publishing roms don't have a lot of time in them, it's just much easier to compile and work with the source than the HTC source is and the senseish framework.
Thanks @CharliesTheMan Thats a pretty good answer
Well i liked CM/AOSP rom's on my other phones and never used stock-ish ones.
Well, mainly i use my phone for phoning around (no sh*t! lol), social networking, taking photos and derping around a bit.
I never used the sense-features (blink feed, zoe, beats-audio etc. - i like the gallery, but honestly.. i like quickpic much more, i like it minimalism), neither like the look of sense.
I'm just a bit scared of using an AOSP rom, i dont really now why.. maybe scared of phone-signal-breaks, quality breaks or something like this.
But to be honest, i have to test it by myself i know, like the performance, stability and battery - its stuff i have to test and figure out by myself, because everyone is using the phone not in the same way and everyone got other recommendation from a rom and i got the point you wanted to say with your post
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
I'm looking for functionality, little or no bugs, I am looking to stick as close to stock as possible with the option to customize if I wanted to. I know there are a ton of ROMs and I could spend ages scouring them for the one that might be right for me.
ghostspectrum said:
I'm looking for functionality, little or no bugs, I am looking to stick as close to stock as possible with the option to customize if I wanted to. I know there are a ton of ROMs and I could spend ages scouring them for the one that might be right for me.
Click to expand...
Click to collapse
Did you install twrp also? You will need that to flash anything... might want to back up what you currently have before flashing also. If you like the stock feel, you can always wait until xposed comes out of alpha and start your customizing with it too.... lots of good info here if your not familiar with it. As far as UI is concerned you don't necessarily have to flash a custom rom, you always try a few different launchers on for size first.... Nova is pretty popular apex is another.... I am using action 3 right now which I like...
I would suggest clean ROM for a very stock like experience and then install MCR mod pack. This is my setup and I love it.
Cleanrom and sinless. Both stockish and super stable.
Stock. If you're not going to try for yourself, then you shouldn't go sheep.
OP you should really look around the development forums, you can't expect what works for other people to work for you as well. Usually down the line, you'll have a question and you'll want to be searching for the answers, not to ask others for the answer when the answer to your question has already been answered.
Everything in life, you can't just ask for it. Similarly to your decision to purchase what car, what college you want to apply to, etc... all of that you can't just ask someone. That's something for you to determine for yourself. Except the difference here is that all ROMs and kernels are free, be adventurous and try them all out (or at least the ones you found interest into).
My recommendation to this is to look at ROMs based on the following criterias,
- Popularity... how popular is the thread? Why is it popular?
- How frequently does it get updated? Do I like to flash ROM updates daily/weekly?
- Read the last couple of pages (or skim) and see what other users have been saying about the ROM
ghostspectrum said:
I'm looking for functionality, little or no bugs, I am looking to stick as close to stock as possible with the option to customize if I wanted to. I know there are a ton of ROMs and I could spend ages scouring them for the one that might be right for me.
Click to expand...
Click to collapse
Euphoria OS
Parandroid Android
LiquidSmooth
Chroma
Bliss Pop
SlimLP
Dirty Unicorns
And there will be always the buggy Cyanogenmod :silly:
I run Paranoid Android and FAUX kernel with the recommended faux settings and love it.
Everyone will have different taste nobody is the same I use euphoria its like the best ROM I ever used since custom Roms were out
Hi guys,
I know its really hard to create a new ROM and updating it and giving to users. But since the launch of Android 5.0 Lollipop I don't find difference between all major ROMs.
If there is difference, it is of the Bugs. Some ROMs got big bugs and some with small bugs. But rest is same. The looks the feel, everything same (Except MIUI - which is not on Android 5.0).
I have tried almost all of them. Thanks to all the devs. But my question is there any ROM which is unique???
I am getting same functions in all of them with same looks Even they are same in smoothness and working.
The difference is created by Cyanogen ROMs with theme engine, but now all ROMs now include that theme engine. So we are basically using the same ROM everywhere.
At the moment I am using DirtyUnicorn and I don't want to change because all the ROMs are same.
Is there any ROM which is unique??????? Any?????
Don't say that I should change theme or launcher. It just makes the availability of ROMs a joke.
I am still waiting for MIUI or Lewa if it arrives.
gautam.is.sharma said:
Don't say that I should change theme or launcher. It just makes the availability of ROMs a joke.
I am still waiting for MIUI or Lewa if it arrives.
Click to expand...
Click to collapse
If you dont like them then by all means make one yourself. Just wait MIUI is also gonna look alot like the rest. Android is made for you to change things to make it your own. So use a launcher and a custom theme or make your own rom.
Also if you are looking for verity then you should not have gotten a nexus. Get a Touchwiz or Sense device. This way you have more options.
See I do agree with you. Most roms are pretty similar when compared to back in the days of A4.2.
What I think is more important is the choice of kernel. Allowing the ability to over/underclock and control voltages automatically and many other things. I think learning how to use a kernel and it's various governers is what will separate phones.
I dont know why so little roms have cm profiles. It's a feature that have much more benefits than any theme engine
I'm a Brazilian without English Course, sorry and be comprehensive
zelendel said:
If you dont like them then by all means make one yourself. Just wait MIUI is also gonna look alot like the rest. Android is made for you to change things to make it your own. So use a launcher and a custom theme or make your own rom.
Also if you are looking for verity then you should not have gotten a nexus. Get a Touchwiz or Sense device. This way you have more options.
Click to expand...
Click to collapse
See the second post.
I am not against devs and ROMs, but my only thought is that they are all same.
Even once we used to have great Paranoid ROMs with great features, but now it is nothing but same as all CMs.
With Android 5.0 Google has done something that is now killing Custom ROMs. The ROMs are becoming similar or I should say same.
MIUI is different because they are doing different, but all others are just mixing functions and giving you CM ROMs.
gautam.is.sharma said:
See the second post.
I am not against devs and ROMs, but my only thought is that they are all same.
Even once we used to have great Paranoid ROMs with great features, but now it is nothing but same as all CMs.
With Android 5.0 Google has done something that is now killing Custom ROMs. The ROMs are becoming similar or I should say same.
MIUI is different because they are doing different, but all others are just mixing functions and giving you CM ROMs.
Click to expand...
Click to collapse
Well first thing is MIUI is not really different. They are just coping others as well. Notice how they are still on KK? Yes many features are the Same in alot of roms and that is because users have come to expect those and Devs are working like crazy to get them moved up to 5.0 and working. As for them giving you CM roms that is where your wrong. Many have completely ditched CM roms sources due to their dumb ways of merging untested code.
I wont even talk about Paranoid android. They never came up with anything original.
Android at the base is all supposed to look the same. This is what Google Whats and got it with the nasty thing they call the Material design.
I saw your second post. My answer will still be the same. The days of themed roms are over. You are given a clean base to make it your way. So take that and make it yours with a theme and launchers and such.
zelendel said:
Well first thing is MIUI is not really different. They are just coping others as well. Notice how they are still on KK? Yes many features are the Same in alot of roms and that is because users have come to expect those and Devs are working like crazy to get them moved up to 5.0 and working. As for them giving you CM roms that is where your wrong. Many have completely ditched CM roms sources due to their dumb ways of merging untested code.
I wont even talk about Paranoid android. They never came up with anything original.
Android at the base is all supposed to look the same. This is what Google Whats and got it with the nasty thing they call the Material design.
I saw your second post. My answer will still be the same. The days of themed roms are over. You are given a clean base to make it your way. So take that and make it yours with a theme and launchers and such.
Click to expand...
Click to collapse
What I really love about MIUI is that they are working in completely different manner. They are working hard on including new features and providing new looks and with a big market for customization.
Whereas CM are great too, and they are the base ROMs for maybe all the ROMs we are using right now.
I don't think Paranoid didn't did anything new, they gave us Hybrid ROMs. But with Android 5.0, they no more my favorites.
gautam.is.sharma said:
What I really love about MIUI is that they are working in completely different manner. They are working hard on including new features and providing new looks and with a big market for customization.
Whereas CM are great too, and they are the base ROMs for maybe all the ROMs we are using right now.
I don't think Paranoid didn't did anything new, they gave us Hybrid ROMs. But with Android 5.0, they no more my favorites.
Click to expand...
Click to collapse
Almost no ROMs are using cm as a base any more. Miui is just taking ideas from iOS. They are even working on a whole new setup so they can release devices in the us without apple sue them out of business.
zelendel said:
Almost no ROMs are using cm as a base any more. Miui is just taking ideas from iOS. They are even working on a whole new setup so they can release devices in the us without apple sue them out of business.
Click to expand...
Click to collapse
Copying is what they are doing for themes. I don't think that's bad. iOS is more Android, so if MIUI is copying the design then it's not the issue. Their environment is different. So do CMs.
gautam.is.sharma said:
Copying is what they are doing for themes. I don't think that's bad. iOS is more Android, so if MIUI is copying the design then it's not the issue. Their environment is different. So do CMs.
Click to expand...
Click to collapse
So let me get this straight. You think coping is ok yet dont like that all the roms "seem" the same to you?
IOS is more Android?
Your right their environment is different. They dont care what users want or say.
Cm is not even worth mentioning anymore really. They are fast becoming just as big a joke as MIUI in the android world. No one with any real thoughts of their own even use their roms anymore.
The problem is that we all think that the developers actually develop something.
The matter of the fact is that they only tinker with what Google gave them.
So I wouldn't hold my breath for a sense like rom that has its own framework.
No one has got time for that. Big things come from big companies. Or maybe from a team of good friends.
A long time a go a bunch of people gave us Theme Engine, Hybrid Mode, Profiles, PIE, Heads-up, Immersive mode and lots of stuff that was new at the time. I really believe that the creative process is, has been and will be strong on XDA - Developers... but i agree with the OP albeit for different reasons.
I think that as technology, products or processes are understood better, being innovative, creative or "disruptive" becomes harder:
1.- We (the consumer) demand a series of features that become standarized which tramples innovation
2.-And there is the thing with the source material P.E. There is so much a thinkerer can do with a hammer a 2x4 and a couple of nails... Same with android.
3.- As a technology matures the innovation rate diminishes. Look at clocks, TV, videogames or smartphones! Every year there are new models, but little game changing technology even when there are hundred of people working on with, fully paid and with the backing of big companies.
Science and technology advance is not linear... I think that we are on a low point on ROM innovation but to me, that only means that soon somebody will come up with something new and great.
Android roms are same?
Yes they are with a little difference in each and every rom ..coz they are built from the same mother source...AOSP...
Google itself builds it factory images from aosp with touch of google changes...
Every oem uses the aosp and modifies it to make sense, touchwiz, zenui etc etc...
Things have certainly changed in past few years when we only had cm pa pac man ..
Now we have 100s of options ..some developers even kind enough to merge our 'wanted' changes in their rom.
So instead of looking at this thing as 'all are same with little changes' , look it as a 'single thing with 100s of options/modifications' to exactly suit your needs.
Yes its confusing sometimes especially when you are a nexus user
Try a different oem if u want a great change on changing custom roms (migrating from touchwiz to vanilla android gives a wow feeling )
Of course they're 100 pretty much exactly the same roms out there. It's really hard to notice any difference among them. It´s all true. Also calling every room-cooker a developer is in my opinion little too much.
It's been already stated that if you want more variation is better to go for oem devices. however probably at the price of never getting fully working aosp/cm rom (unles we're talking about gpe devices). If you want variation go for flagship oems if you want to enjoy aosp go for nexus.
gautam.is.sharma said:
Do you think all ROMs are basically same in Android 5.0??
Click to expand...
Click to collapse
[Sarcasm ON]
"Same" is a relative term like "IS".
A relative term is that it is different for different people or situations. An example: someone who is 5 feet tall might think someone who is 5 feet six inches tall is tall, but someone who is 6 feet would think that that person is short.
So I voted no, I don't think all ROM's are the same but they are definitely very similar.
[Sarcasm OFF]
~Peace
Agreed, there does not seem to be a lot of innovation in Lollipop ROM features. I have tried Euphoria, TeamUB, crDroid, Slim, RastaPOP, OminROM and XenonHD.
So far they all have the same features. The best one really is XenonHD with its custom long press and double-tap actions on the Nav Bar buttons. This is a great carry over feature from KitKat.
All the other ROMs suck in terms of "new" features.
+1 ..
I guess after 3 4 yrs being on xda, flashing roms with different features, developers amazing us with new and unique features every few months, for me Now it all comes down to the daily use of these features
The PA per app color, pie and omni roms split screen were something that i could use as a daily driver. I really miss PA roms Pie, slimpie somehow is just isnt the same. I miss the tablet mode from PA too.
What i want as a user is a smooth stable rom with some basic tweaks that i dont find on a stock rom and less battery drain. Which i pretty much have with LiquidSmooth.
The speed of innovation has slowed down or rather there arent many more innovative things to do that can be used for daily use anymore i guess. Im not complaining here, just a thought.
Sent from my Nexus 4 using XDA Free mobile app
Gravitybox or MiUi CM is not same