[Q] Which is technically better: AOSP or image-based ROMs? - Nexus 6 Q&A, Help & Troubleshooting

The reason I ask is because image-based ROMs seem to be trouble-free, even if you flash Cataclysm mod over it to get some customization w/o using Xposed.
I would imagine that image-based ROMs would be better for the device, since they are build specifically for the device. As opposed to AOSP ROMs which are built from source, then customized to work with the device.
The reason I ask is because I keep bouncing between TuPac's stripped-down image-based ROM and PureNexus.
Any thoughts around this?

MrBrady said:
The reason I ask is because image-based ROMs seem to be trouble-free, even if you flash Cataclysm mod over it to get some customization w/o using Xposed.
I would imagine that image-based ROMs would be better for the device, since they are build specifically for the device. As opposed to AOSP ROMs which are built from source, then customized to work with the device.
The reason I ask is because I keep bouncing between TuPac's stripped-down image-based ROM and PureNexus.
Any thoughts around this?
Click to expand...
Click to collapse
theres no such thing as "customized to work with the device" for a nexus. aosp is made to work on nexus devices, period. and no, its the same exact thing technically. its like zips, they are all different. some forms compress your stuff down a little, some much more. yet at the end, they are exactly the same.
when you are flashing an aosp based rom, its made exactly for your device, period. this isnt a samsung device, which needs a modded aosp rom to run, its a nexus, what aosp roms are made for. oh, and those stock based image roms. i wouldnt consider them real roms. id consider them basic stock roms with stuff just thrown in. aosp roms they build from scratch, with the options/features built in.

simms22 said:
theres no such thing as "customized to work with the device" for a nexus. aosp is made to work on nexus devices, period. and no, its the same exact thing technically. its like zips, they are all different. some forms compress your stuff down a little, some much more. yet at the end, they are exactly the same.
when you are flashing an aosp based rom, its made exactly for your device, period. this isnt a samsung device, which needs a modded aosp rom to run, its a nexus, what aosp roms are made for. oh, and those stock based image roms. i wouldnt consider them real roms. id consider them basic stock roms with stuff just thrown in. aosp roms they build from scratch, with the options/features built in.
Click to expand...
Click to collapse
Thanks for your response. I understand all that.
It seems like more can go wrong with AOSP-based ROMs since they are built and not provided from the factory image. Take Android Pay for example. It simply works on image-based ROMs but requires fixes or certain work-arounds to work on AOSP-based ROMs (flash a certain Gapps, make sure root is systemless, etc).
In my experience, and maybe it's just my device, but it seems like image-based ROMs run more fluid, but AOSP-based ROMs are faster, if that makes any sense. It almost seems like the image-based ROMs are better optimized for the device or something but they seem to slow down over time, the more the device is used.

MrBrady said:
Thanks for your response. I understand all that.
It seems like more can go wrong with AOSP-based ROMs since they are built and not provided from the factory image. Take Android Pay for example. It simply works on image-based ROMs but requires fixes or certain work-arounds to work on AOSP-based ROMs (flash a certain Gapps, make sure root is systemless, etc).
In my experience, and maybe it's just my device, but it seems like image-based ROMs run more fluid, but AOSP-based ROMs are faster, if that makes any sense. It almost seems like the image-based ROMs are better optimized for the device or something but they seem to slow down over time, the more the device is used.
Click to expand...
Click to collapse
well, first off, aosp and stock are two completely different roms. stock roms also have closed source code included, where aosp roms dont have that code included, so they WILL run differently, as two different roms should.
---------- Post added at 03:20 PM ---------- Previous post was at 02:58 PM ----------
anyways, the answer to your question is really simple.. better is whatever is better for you,personally. to you, image based roms are better. for me, aosp is better.
as a real answer of which is better doesnt exist, its all which is better for you(or me).

Had you followed the rules you would know threads like this don't stay open long.
There is no best. Or better. There is only what works for you.
Most people that get a nexus device do it for the active development. Which does mean some bugs here and there, but that is the fun. In learning, finding and killing bugs. If you got a nexus for any other reason you really are not doing yourself any favors.

Related

Custom Versus Stock ROM

Hi,
Which of the custom ROM do you find better than stock ROM, based on your own experience. What I'm missing by using stock ROM ? you think
aminsa said:
Hi,
Which of the custom ROM do you find better than stock ROM, based on your own experience. What I'm missing by using stock ROM ? you think
Click to expand...
Click to collapse
I guess the answer is, it depends like everything else. Custom ROMs come in a great variety, AOSP, AOKP, TW, hybrid ones like Paranoid. Just flash and try
Personally I like TW. I tried Criskelo and Kingdroid, also tried paranoid(non TW). I liked Kingdroid the best. It has the newer version of TW(as opposed to the stock ROM), somewhat better battery life, more fluid IMHO, better performance overall.
ROMs are more like, to each their own. Try it, you have nothing to lose. I tried a few over a weekend, and settled on one that I dont change often because of lack of time.
I agree..
I agree, too.
Just one more suggestion as this could help you determine faster if the rom does what you need/want:
Root your phone and use a backup software (titanium or backup root, for example), saves you time
If you do this already nevermind
But to answer your question directly: most of the roms focus on smothness and stability, others implement whole new features (in paranoid rom you can choose for every app if you want the tablet or phone version) or make it easier to tweak your system (liquidsmooth would be my example for this). Also, there are several JellyBean ROMs which only miss a few features so you are always up to date and don't have to wait for Samsung's infamous touchwiz-"magic" to be applied...
And it actually teaches you a thing or two about Android and the development for it (at least it did for me )
Hope I could help

Waiting for Android 5.0 Custom ROM? Hopefully this will help!

***NOTE TO MODERATORS:
I hope you can see what I'm trying to do with this thread. If some kind Dev takes the time to answer soon, then this could be a very informative resource. If no one answers, then the thread is pointless and I will totally understand if you decide to delete it. Thanks ***
Hi to all you amazing Custom ROM chefs.
I'm sure loads of us are waiting for the roll out of M7-based Android 5.0 ROMs, especially as we know the GPE version is imminent, but maybe like me they don't understand the full process. So would someone kindly let me know the following, and by posting it here I'm sure many other people will be able to understand.
Once the GPE image is released, how long do you expect it to take before the image is edited to run on non-GPE phones? And who actually does this? Do all you devs wait for the CM12 nightlies to be released and then base your own ROMs on that? Or is the port very easy once HTC release the GPE ROM, which allows you to build your ROMs from scratch? I read enough on xda to understand that there are some 'big' players out there, like ARHD, Paranoid Android, SlimRom, ASAP, etc. Do other devs wait for these and then do their own mods? And (potential 'grey area') where do the images actually come from? Do HTC happily give their images to the main devs, knowing that there's a whole User Base who will stick with their HTC handsets if they can customise them with 'unofficial' ROMs? After all, if we stick with our M7s and M8s, then we're not buying Samsung or Nexus and the market share tilts ever-so-slightly in favour of HTC.
I hope someone will take the time to explain the Custom ROM process, and I also hope this will stop other users from posting "when, when, when?" threads (irony appreciated).
Thanks in advance,
miles_muso
Since anyone hasn't answered this yet, I'll throw in what I know...
There are three types of ROMs: Google Play Edition, Sense, and AOSP.
GPE roms are stock, Nexus-like roms that have underlying frameworks similar to that of Sense (which I'll get into in a sec) however they are aesthetically virtually the same as the Nexus devices. They receive updates much quicker than their Sense counterparts due to HTC not having as big a role in modifying the interface, etc. They also have apps that are very similar (if not the same) as AOSP apps. SinlessRom GPE and Android Revolution (GPE) are examples of this.
Sense roms are HTC roms. HTC takes the updates Google releases and then proceeds to change it drastically, both under-the-hood and aesthetically. Their interfaces are heavily modified and they often have different apps from AOSP and GPE. These take the longest to release new versions of Android for. Android Revolution HD (Sense) is an example of this.
AOSP comes straight from Google. ROMs such as CyanogenMod are a modified AOSP. AOSP Lollipop is already available to build and it has been built for our M7. AOSP roms are (nearly always) aftermarket roms and can work on all S-On m7 devices. ParanoidAndroid and CyanogenMod are examples of this.
If a user has a phone that ships with HTC Sense, they will typically have to achieve S-Off before flashing a GPE rom. I'm not sure if the same is true for the vice versa, however I can imagine it is.
Now, to answer your question, you can build roms from scratch already (and there are some that have been released). You can't build Sense or GPE from source and you must modify official versions, leaks, or ports. You can build AOSP from source, and since we have somewhat-proper kernel source for Lollipop, it's not as difficult as it is for less-popular devices that don't have that source.
I personally feel like the release of GPE will be most helpful for AOSP in the aspect of kernel sources (as it will be the first OFFICIAL and hopefully BUG-FREE Lollipop for the m7 devices).
I'll add to this post if I can think of anything else.
Hi nuuits,
Thanks for your reply, this is EXACTLY the kind of info I wanted here. Hopefully this will help a lot of people understand the Custom ROM development phases. And, may I ask, when do YOU think we'll start seeing the first batch of ROMs based on Android 5 (apart from CM12, which, as you state, is currently available)?
miles_muso said:
Hi nuuits,
Thanks for your reply, this is EXACTLY the kind of info I wanted here. Hopefully this will help a lot of people understand the Custom ROM development phases. And, may I ask, when do YOU think we'll start seeing the first batch of ROMs based on Android 5 (apart from CM12, which, as you state, is currently available)?
Click to expand...
Click to collapse
Apart from AOSP, you can expect GPE and Sense ROMs when they're either leaked, ported, or released officially.
Leaks are "early builds" (not always intended for the general public's use) that are, well, leaked to sites such as XDA. Ports occur when you take a ROM for one phone (let's say the M8 ) and port it over to ours. Official releases are just that- ROMs pushed by HTC and/or Google.
You can expect custom GPE ROMs when one of the above occurs. I'm putting my finger on "official release", which is projected for the coming week(s), however I can never really know!!
Sense ROMs will come much later than GPE (but still within HTC's 90 day limit- if they keep their end of the bargain). There's an even toss between the above three methods imo- as the m8 will get the Sense update before the m7, we might see a port. Leaks are somewhat likely and the official release will come when it comes (which is hopefully before and probably around the 90 day mark- so January at latest).
After the initial stock ROMs are leaked, ported, or released, there are bound to be updates to your favourite custom ROMs, but of course that depends on the developer in question.

Stock based ROM with customizable nav buttons?

I am looking for a stock based ROM, which there doesnt seem to be many of, that has the ability to change around the nav buttons. I really want to swap that recents and back button and I know we have been able to do it on AOSP based ROMs for a while now. However, AOSP based ROMs get significantly worse battery life from idle drain than the stock based ROMs on my phone at least so I would really like to find one with a stock base. Does such a ROM exist and I am just missing it?
EniGmA1987 said:
I am looking for a stock based ROM, which there doesnt seem to be many of, that has the ability to change around the nav buttons. I really want to swap that recents and back button and I know we have been able to do it on AOSP based ROMs for a while now. However, AOSP based ROMs get significantly worse battery life from idle drain than the stock based ROMs on my phone at least so I would really like to find one with a stock base. Does such a ROM exist and I am just missing it?
Click to expand...
Click to collapse
well, if you wamt a real rom with the additions, then you have aosp as an option. real developers dont put up a stock rom because no source is provided. no source equals no building roms. some people learning how might use stock, but they dont build it, they just add add-ons to it. something like what you are looking for requires framework changes, so the rom has to be built from scratch. amyways, have you looked if xposed provides an option for you?
simms22 said:
well, if you wamt a real rom with the additions, then you have aosp as an option. real developers dont put up a stock rom because no source is provided. no source equals no building roms. some people learning how might use stock, but they dont build it, they just add add-ons to it. something like what you are looking for requires framework changes, so the rom has to be built from scratch. amyways, have you looked if xposed provides an option for you?
Click to expand...
Click to collapse
Oh really? I thought Google had all the source for builds for the Nexus devices. Hmm. That must be why I cant find what Im looking for then. lol.
So Xposed works now on Lollipop? Ill give it a look. Thank you.
EniGmA1987 said:
Oh really? I thought Google had all the source for builds for the Nexus devices. Hmm. That must be why I cant find what Im looking for then. lol.
So Xposed works now on Lollipop? Ill give it a look. Thank you.
Click to expand...
Click to collapse
yea, xposed now works on lollipop. and yea, stock is only build by google. but its easy enough to add some things to it. and aosp is where all the code is provided for us to build our own roms. google dors have all the source, tbey just dump it into aosp for us.

[Q] Best Custom ROM for Stock Kernel?

As much as this might be a really broad topic, I'm new to flashing and trying out new ROM's so some suggestions would be nice for the Nexus 6? Just looking for some honest alternatives to Stock 5.1, wanting to stay on Stock Kernel if possible.
Stock kernel is pretty much the worst of them. Or should i say, least improved. If you're not interested in trying custom kernels just yet, use the one that comes with the custom ROMs you try
As for recommendations, what's everyone likes is different. Look in the development forums, read the features and try them.
wright_ac said:
As much as this might be a really broad topic, I'm new to flashing and trying out new ROM's so some suggestions would be nice for the Nexus 6? Just looking for some honest alternatives to Stock 5.1, wanting to stay on Stock Kernel if possible.
Click to expand...
Click to collapse
What @rootSU said and;
As long as you have a custom recovery and do a nandroid backup of your stable stock build, just try as many roms as you feel like. You don't like it, just restore your backup and bam, 5 minutes your back to exactly where you were. You can even use multirom and boot into different roms. Grab one of the roms from the N6 dev forum and give it a spin, you will never go back! And for what its worth, Benzo is dang good.
wright_ac said:
As much as this might be a really broad topic, I'm new to flashing and trying out new ROM's so some suggestions would be nice for the Nexus 6? Just looking for some honest alternatives to Stock 5.1, wanting to stay on Stock Kernel if possible.
Click to expand...
Click to collapse
rootSU and jackpollard have already covered the basics. However, I will make a recommendation because I know that's what you want - if you want to try a ROM that comes with a very nice kernel so you will not need to flash a custom kernel, I recommend trying Dirty Unicorns. It is my personal favorite ROM to run with the inline kernel (XDA speak for the kernel that comes with the ROM). As these guys said, when you flash a ROM, it generally comes with a kernel. When you hear people on a particular ROM talk about "stock kernel", they really mean the inline kernel that comes with the ROM, not the stock MTV whatever Google kernel. To get technical, I'm not using "inline kernel" correctly either - that actually means a kernel that's built with a ROM, but I'm not even gonna get into all that. I would recommend Dirty Unicorns if you wish to find a ROM that comes with a stock kernel installed that is absolutely awesome. If you prefer a lighter ROM with a more stock-like kernel, I recommend Chroma. Both are excellent ROMs with great kernels that come with them, and both provide kernels that are easy for a new user to learn to configure. It just depends on what you are looking for - you may end up hating both of those ROMs. Also, any ROM that uses leanKernel as its kernel is a good place to start - find one that has a feature list you like, leanKernel is the best starter kernel there is in my opinion. The best thing about it is it is built well enough to still suit the needs of way more advanced users while not intimidating even the newest of noobs in the slighest. So, play around and find what suits you, bu those are a few recommendations to get you started based on the kernels that come with the ROMs and what you are asking for. I hope it helps you out.
Took the plunge and installed the latest Chroma ROM build, safe to say I'm happier with it than stock!
wright_ac said:
As much as this might be a really broad topic, I'm new to flashing and trying out new ROM's so some suggestions would be nice for the Nexus 6? Just looking for some honest alternatives to Stock 5.1, wanting to stay on Stock Kernel if possible.
Click to expand...
Click to collapse
Heres a fun note. Most ROMs have yet to make major kernel changes, this means that, as of now, CM, PA, Omni, and most if not all AOSP ROMs boot on the stock kernel.

Help getting started.

Hello. I just bought my brand new Oneplus 3T. I came from the LG G4. I always used custom roms on my android phones. Unfortunately I have a job now and I don't have much time to play/test all these roms around here.
I'm not asking "the best rom" or "which is better" sort of things.
I just need an opinion for what should I begin with?
I would prefer some stock based rom.
As about the kernel I heard a lot about Franco's kernel but I saw that there is Boeffla kernel too.
Don't get me wrong, I just need something to start from because as I mentioned above I don't have much time to test and choose which is best for me.
Thank you!
I have tested many ROM's and I always come to the same conclusion. Stock is better. I recommend you to use stock OOS, root it and mod it as you wish. It's a powerful OS, without much bloatware (which can anyways be easily removed) and it offers a decent amount of customization. Of course, it's not as customizable as RR, but RR is also unstable and doesn't offer the same camera quality. In fact, most ROMs have a crappy camera. Except PA, apparently, which, of course, has other problems, like idle battery drain. You'll find something that won't make you happy in every rom you try. That was, at least, my experience. I have come to the conclusion that OOS does its job well.
luptatorul said:
I have tested many ROM's and I always come to the same conclusion. Stock is better. I recommend you to use stock OOS, root it and mod it as you wish. It's a powerful OS, without much bloatware (which can anyways be easily removed) and it offers a decent amount of customization. Of course, it's not as customizable as RR, but RR is also unstable and doesn't offer the same camera quality. In fact, most ROMs have a crappy camera. Except PA, apparently, which, of course, has other problems, like idle battery drain. You'll find something that won't make you happy in every rom you try. That was, at least, my experience. I have come to the conclusion that OOS does its job well.
Click to expand...
Click to collapse
This is exactly what I want. I don't want a LineageOS based rom or something like this.
I want a STOCK based rom.
But I don't know with which rom should I start because I saw that there are a few.
Hmm, I'd say freedomOS. It's a very stable ROM, "daily driver" material. It gives you the option to kinda debloat it when you flash the ROM
If you are looking for maximum battery with average use then go for RR with EX Kernel.
Yeah Freedom OS is kind to install because you don't have to do the usual stuff manually, but I've personnaly not noticed anything you can't get on stock OOS.
I'd advice to stay stock, and if later you still want to try some new things there will be plenty of mod material here
If you want something else...try Phoenix AEX ROM..
Really different experience...( EAS based )
Hi, when you are new with this phone I personally would recommend OxygenOpen Beta.
https://forum.xda-developers.com/oneplus-3t/how-to/coming-update-oos-based-7-1-t3564240
This Rom has everything you want, for me absolut stable and has all features you need for normal use. Worth to have a look.
I always had custom Roms on my earlier phones, but this stock Rom is the best I have ever seen. I have unlocked bootloader and rootet phone but since I have my phone (since May) I flashed this Rom and there is no reason for me to change it:angel:
Greets, reinipic
ilooze said:
I always used custom roms on my android phones.
Click to expand...
Click to collapse
Don't feel like you need to flash a custom ROM, just because you "always have". Try the stock OOS for a bit, you'll be pleasantly surprised.
Stock OOS is very impressive. Very little bloat, really close to stock Android, nice customization options, and it just works. It's a big departure from the manufacturer "skins" applied by LG, Samsung, etc. which often (in my opinion) make too many changes, with little added value.
Although, I would suggest unlocking the bootloader now (instead of waiting) even if you do intend to try out the stock ROM for a while. Sinceit is a bit annoying having your data wiped (by unlocking the bootloader - it can't be avoided) and having to setup everything again, if you do decide to install a custom ROM, kernels, etc.
Stick to OOS. It's the best, really. Sultanxda's lineage is amazing for starters.
And Franco kernel on OOS is also "legendary"
Nevertheless, it's upto you to try and tell yourself what rom/kernel suits your needs.
Cheers!
That's the mistake you use custom roms. I always have stock rom on my every device
Stock open beta 10 with custom kernel(optional to remove dm verity flag) + magisk + safety net pass + adway + google assistant + dark mode.... thats it !

Categories

Resources