Related
It seems that since a couple of new builds in, there's suddenly a stream open to the official OTA updates in the CM updater in the unofficial builds of @mo976, are these builds similar or identical? What's the difference?
I might be mistaken though, but wanted to be sure about this..
Thanks a lot, I'm enjoying these builds either way mo976. :good:
Difference is, one is official, and the other isn't. Best to rely on the official one because of the amount of people working on it.
Thanks man :good:
Hey im still running Android 4.4.2 CleanRom and its been a while since ive been around. I feel a bit outdate and was wondering what i should upgrade to. Not looking to do nightly's as i do not have the time, just looking for something new and stable. Let me know what you think. Thanks.
-Cam
camf3xu said:
Hey im still running Android 4.4.2 CleanRom and its been a while since ive been around. I feel a bit outdate and was wondering what i should upgrade to. Not looking to do nightly's as i do not have the time, just looking for something new and stable. Let me know what you think. Thanks.
-Cam
Click to expand...
Click to collapse
Hi, here on xda we dont compare roms, sorry. its just taboo of the worst kind. Also please post questions in the question and answers portion of the forum, thanks and cheers.
I'll go ahead and reply with respect to the split between KitKat and Lollipop. You'll note a bunch of Lollipop-based ROMs appearing. Some have chosen to flash those, to be on the cutting edge. However, the Xposed Framework - one of the most useful customization tooks in the Android world - has not been updated to work with the "ART" (Android Run Time) and instead is only still compatible with Dalvik-based system. The developer of Xposed has indicated that he may work on updating XPosed at some point, but there is no firm commitment or timeline.
I personally will not be upgrading to Lollipop as I find that the tweaks made available by the Xposed Framework and the plethora of modules built for it, are simply too important me to lose by upgrading to what isn't all that radically different of an Android update.
But to each his own. Thought I'd give you a bit of the background.
P.S. Anything by Santod is quality work (NuSenseSix, UnSenseSix, etc). He really knows Android.
Nothing beats stock as far as stability. For newest, well, the newest official software is stock as well until VZW releases Lollipop.
Sacred cows make extra tasty steaks. That said, I'll make recommendations. I think Fluent is as reliable as the stock 4.4.4 and more so than some of the more radically tweaked 4.4.4 ROMs out there built from non-Verizon sources. NuSense is solid as well, but hasn't been updated in a while, is minimally modified, and is based on the oldest of the lollipop releases. if 4.4.4 is all you want, Clean ROM 3.0 was a solid runner for me.
If you can do your own mods then I would go with Lollipop as you don't need xposed if your looking for stable stick to 4.4.4 for now.. Make sure you upgrade your firmware before if you haven't as you r still on 4.4.2 ROM I'm taking a guess your haven't updated firmware.
Tigerstown said:
If you can do your own mods then I would go with Lollipop as you don't need xposed if your looking for stable stick to 4.4.4 for now.. Make sure you upgrade your firmware before if you haven't as you r still on 4.4.2 ROM I'm taking a guess your haven't updated firmware.
Click to expand...
Click to collapse
What do you mean by doing your own mods? Short of coding them, I'm not sure how one would go about getting Samsung Milk to work, or cleaning up the Notification menu, or a bunch of other things that just aren't commonly built into customized ROMs. If you do know of a way to get such things working in Lollipop, do let me know - I'd then be able to make the switch!
godhamba said:
What do you mean by doing your own mods? Short of coding them, I'm not sure how one would go about getting Samsung Milk to work, or cleaning up the Notification menu, or a bunch of other things that just aren't commonly built into customized ROMs. If you do know of a way to get such things working in Lollipop, do let me know - I'd then be able to make the switch!
Click to expand...
Click to collapse
I was just saying if you know how to decompile apks an make code changes an recompile your make your own mods.
Hey guys, I've been searching for ROMS that are for the SM-G925P (I have found some but they're not being maintained anymore). There is a specific one I'm looking for, which goes by the following guidelines:
Deodexed for Xposed (Systemless)
Debloated
Multi-User Support
Using Android 6.0.1
Works with a SM-G925P
That's pretty much what I'm looking for in a ROM.. the only one that's pretty close is Renegade HD, but like I said, its not being maintained anymore
I'd say your best bet is AlexisROM, so far its quite good for me, twisted kernel is also great for Android OS drains (If you do get them with this rom which I use to). I dont think most of the good 6.0.1 Roms are being maintained anymore as theyre getting ready for Android N, they're all quite stable though.
Does that rom run on the SM-G925P? I'm really curious since the last time I tried flashing firmware that wasn't compatible with my phone, it COMPLETELY bricked my phone. Even to the point I couldn't get it repaired. I got lucky the fact that it died and decided to start up again.
Thread closed as duplicate
https://forum.xda-developers.com/sprint-galaxy-s6-edge/help/q-to-date-roms-t3562555
I realize that this is not the first topic to ask for custom ROM advice, and that the general advice is "try some and pick the one you like best". This thread is different in that I am specifically looking for a stable custom ROM. I was surprised to find out that LineageOS does not offer any stable builds for our device, nor does AOKP; they both only offer nightlies. Are there alternatives that do offer stable builds?
You can try Ressurection Remix. I used it last month and its pretty stable. Also this ROM recently (22.12.17) got update.
Also have great customization options too!
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-n-5-8-2-t3587204
But if you want good Oreo 8.1 Rom then I suggest crDroid. I use it now and i am satisfied with it. Only flaw that i cant get Magisk root to work. (also recent update 21.12.2017)
https://forum.xda-developers.com/2015-moto-g/development/rom-crdroid-android-4-0-t3696388
Nothing is as stable as stock.
I am specifically looking for a stable custom ROM
Click to expand...
Click to collapse
me too Nougat will be preferable, so maybe someone with experience will say something, now I am on stable STOCK
do you want a 7.1.1 build (probably CM/Lineage 14.1) or Oreo (probably new aospex https://forum.xda-developers.com/20...xtended-rom-v5-0-t3681997/page53#post75051303 but camcorder not work in 8.x builds have to use footej or cameraFi2.) Holler if you need more pointers. LinOS 15.x is not supported at the moment even though the thread is there.
look at https://forum.xda-developers.com/2015-moto-g/general/pursuing-8-1-osprey-moto-g-2015-t3718416 for pointers to 3 other 8.x builds.
You can try this - Ressurection remix, very stable Nougat 7.1.2
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-n-5-8-2-t3587204
Resurrection Remix is not stable - according to the topic you link to, it's Beta
If Oreo roms do not have full functionality, then I'll have to stick to Nougat!
yep.
I have been running nightlies (12/15 and updated to the 12/29 yesterday just because I was messing with something) on Lineage OS 14.1, and as far as I'm concerned, it seems as stable as a CM 'snapshot'. This is my primary phone, and I haven't had a random reboot, or any issues to speak of like I was used to with older ROMs on previous phones. I've been on it for a few weeks, finally decided it was time to unlock the bootloader and get off of the stock ROM, since the device is well past the stock OTA window.
If you recall on CM, "stable" releases were pretty rare and usually came out well after the next android version was already released. I'm planning to update maybe once a month, I don't see the need to jump on every nightly, but occasionally something interesting gets added to an update.
Hello.. I would like to ask developers which file we need to replace for normal boot (not opposite) ..some custom rooms for nexus 6 boot on moto maxx xt 1225...please look video.
https://youtu.be/RxoNMuIPQbw
jaaa1976 said:
Hello.. I would like to ask developers which file we need to replace for normal boot (not opposite) ..some custom rooms for nexus 6 boot on moto maxx xt 1225...please look video.
Click to expand...
Click to collapse
Thanks bro...
I already knew that, but the Custom ROM developers for Quark are too proud to use what already exists for Nexus 6 in Quark. They prefer to stay back and stay on the hard way.
vinydasilveira said:
I already knew that, but the Custom ROM developers for Quark are too proud to use what already exists for Nexus 6 in Quark. They prefer to stay back and stay on the hard way.
Click to expand...
Click to collapse
You really have no idea what you are talking about. Did you even go to that link and actually read? No, you didn't or you wouldn't be making comments like that.
moto maxx (xt1225) running rom stock of nexus 6. totally unstable. stock 7.1.1
*Kernel AOSP - Quark (This is merely @bhb27 LOS kernel or his standalone, there is NO such thing as "Kernel AOSP -Quark")
*Stock 7.1.1
Click to expand...
Click to collapse
Why would we want to run something like that (unstable Nougat ROM) on our Quarks when we already have VERY STABLE Nougat custom ROMs? Why would we want to run UNstable 7.1.1?
Plus, whoever wrote that seemingly doesn't know what they are talking about either....
If it's "kernel AOSP - Quark" -- well, there's no such thing. That means it's @bhb27's kernel code. There is no "AOSP kernel" for Quark. Whoever wrote that doesn't know much about Quark dev work. No ROM can run on our Quark phones without a compatible kernel, and @bhb27 has coded both LOS stock kernel and his own advanced standalone kernel (with more features, options). All the Quark custom ROMs (including AOSP) use the LOS stock kernel -- which @bhb27 coded. All the Quark custom ROMs actually use the SAME kernel.
If he had said "LOS kernel -- Quark", that would be more accurate. Or @bhb27 kernel".
You can even run @bhb27 kernel with Motorola Marshmallow stock. You don't need a custom ROM. It's a great kernel!
All that YouTube post means is someone took @bhb27 kernel code and managed to horribly port a Nexus 6 stock-based ROM over it. They didn't do any magic -- any more than any other ROM like RR, LOS, AOSP runs on Quark right now, with @bhb27 kernel. All they did was badly port a Nougat 7.1 "stock" ROM that they say is unstable. Whoopee.
I'm all for more ROMs, but you need to understand how ROMs are made -- they are built on the foundation of the kernel. ANY Nougat ROM can be ported to our phones, as long as you use the Quark kernel.
The reason why "stock" ROMs are not done are because they are boring. You wouldn't have the LED notification for instance that @bhb27 created, nor all the options present in Revolution Remix and crDroid. Even @calsurferpunk's LOS ROM is more of a hybrid -- LOS + some of the more popular options in RR. We already HAVE up to date 7.x Nougat ROMs. And they run well. How many more do you want?
This Nougat ROM in this video is running on @bhb27 kernel code -- just like every other ROM we have. So, how is it any different?
What people WANT are Oreo ROMs. The the only reason we don't have Oreo ROMs right now, because @bhb27 has to adapt the last kernel Motorola gave us (Marshmallow) to work on Oreo, the way he did for Nougat.
ChazzMatt said:
You have no idea what you are talking about. Did you even go to that link and actually read? No, you didn't or you wouldn't be making comments like that.
Why would we want to run something like that on our Quarks when we already have VERY STABLE Nougat custom ROMs? Why would we want to run UNstable 7.1.1?
Plus, whoever wrote that seemingly doesn't know what they are talking about either....
If it's "kernel AOSP - Quark" -- well, there's no such thing. That means it's @bhb27's kernel code. There is no "AOSP kernel" for Quark. Whoever wrote that doesn't know much about Quark dev work. No ROM can run on our phones without a compatible kernel, and @bhb27 has coded both LOS stock kernel and his own advanced standalone kernel (with more features, options). All the custom ROMs (including AOSP) use the LOS stock kernel -- which @bhb27 coded. All the custom ROMs use the same kernel.
If he had said "LOS kernel -- Quark", that would be more accurate. Or @bhb27 kernel".
You can even run @bhb27 kernel with Motorola Marshmallow stock. You don't need a custom ROM. It's a great kernel!
All that post means is someone took @bhb27 kernel code and managed to horribly run a Nexus 6 stock-based ROM over it. They didn't do any magic -- any more than any other ROM like RR, LOS, AOSP runs on Quark right now, with @bhb27 kernel. All they did was badly port a Nougat 7.1 "stock" ROM that they say is unstable. Whoopee.
I'm all for more ROMs, but you need to understand how ROMs are made -- they are built on the foundation of the kernel. ANY Nougat ROM can be ported to our phones, as long as you use the right kernel.
The the only reason we don't have Oreo ROMs right now, because @bhb27 has to adapt the last kernel Motorola gave us (Marshmallow) to work on Oreo, the way he did for Nougat.
This Nougat ROM in this video is running on @bhb27 kernel code -- just like every other ROM we have. So, how is it any different?
Click to expand...
Click to collapse
Great. Amazing. You changed my mind ...
Now tell me. Why not use what we have from the Oreo of the Nexus 6 to advance the Oreo of the Maxx? Because the Nexus 6 devs already have Oreo 8.1.0 running on Nexus 6. When I talked about standing back and doing the hard way I was referring to that.
vinydasilveira said:
Great. Amazing. You changed my mind ...
Now tell me. Why not use what we have from the Oreo of the Nexus 6 to advance the Oreo of the Maxx? Because the Nexus 6 devs already have Oreo 8.1.0 running on Nexus 6. When I talked about standing back and doing the hard way I was referring to that.
Click to expand...
Click to collapse
It's about the kernel. The kernel is the foundation of all ROMs. You notice the YouTube video is merely a Nexus 6 NOUGAT ROM that doesn't run well on Quark. Because we have Nougat compatible kernel right now.
@bhb27 actually said he is using some of the Nexus 6 stuff for CLUES to adapt the Quark kernel for Oreo. But it's not easy. Until you have a compatible kernel, no Oreo ROMs will run on Quark. @bhb27 has actually gotten Oreo Resurrection Remix to run on Quark. Have you not seen the screenshots? But at this point it's still unstable.
Once you have a kernel, you can have 100 Oreo ROMs on Quark in a week -- if you find 100 people willing to port the ROMs. It's almost plug and play (for dev maintainers who have those skills). This is why we have had so many "drive by" ROMs dropped into this forum and then those people walk away without ever updating them. They were taking advantage of @bhb27's kernel work. Take ROM, plug in kernel, done. But they never stuck around to keep them updated, or even test them thoroughly, and some didn't even own a Quark phone. One of them even used @bhb27's advanced standalone kernel (not his LOS stock kernel) in their ROM without his permission, so it made their ROM seem better than the other ROMs. It's the same kernel anyone can download and install themselves, but @bhb27 wants you to install that one yourself as it's more complex. He doesn't want it installed as a default kernel -- he doesn't include it in his own ROMs.
He's working on an Oreo-compatible kernel but while everything about Moto Nexus 6 is open source (thanks to Google), it's not the same with Moto Quark. Yeah, even LG Nexus 4 has Oreo, but again, it's totally open source so easier to adapt.
Replying the OP, theoretically what is needed is:
remove the checks from the zip regarding if the devices is Nexus 6, and after installing the ROM flash a compatible kernel, and the thing may boot like that.
But is a lost cause, the only thing similar with MAXX and Nexus 6 is the cpu/gpu and Motorola build it.
All the rest is not compatible, chipset, audio, video, wifi, radio, all the firmware, etc and etc is different, there is too many hardware diference for things to work.
And all of those are supported in a combination of ROM + kernel.
The source to build for Quark and for any AOSP device is not the same, yes is all on the same main Repo but the files used are not the same, that is way it device has it's own configuration/recipe and separated sources files inside the main Repo source.
The only reason way any AOSP device have updates easier is just like Chad wrote, they have all the sources files released, plus the AOSP source is made to be used with AOSP devices, so they need to make very little changes when google releases things to build a working ROM for they devices, plus there is literally hundreds of developers building for AOSP devices simply because is that simple anyone can build and help.
On the oppose to none AOSP devices were there is only a few developers as things are very hard because we don't have sometimes a clue in what to do, as we don't have the devices source, google changes the source on a way that only works with AOSP devices, so after a new OS is released a lot of things is need to be made from scratch.
If any one think is simple to build for any device just go for it, instead of be criticizing and posting none sense about thing you don't now how works.
about the video posted on my channel, I just made a joke at home. I know the limitations, I know the hardware is different. it was only a joke of those who do not have much knowledge, but search knowledge, the kernel used is a custom ROM 7.1.1, I did not say that the kernel is stock 7.1.1.
I admire the work of the developers, when I use a custom ROM, I can imagine how much work it has done to make it functional with few bugs. :good:
---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------
bhb27 said:
Replying the OP, theoretically what is needed is:
remove the checks from the zip regarding if the devices is Nexus 6, and after installing the ROM flash a compatible kernel, and the thing may boot like that.
But is a lost cause, the only thing similar with MAXX and Nexus 6 is the cpu/gpu and Motorola build it.
All the rest is not compatible, chipset, audio, video, wifi, radio, all the firmware, etc and etc is different, there is too many hardware diference for things to work.
And all of those are supported in a combination of ROM + kernel.
The source to build for Quark and for any AOSP device is not the same, yes is all on the same main Repo but the files used are not the same, that is way it device has it's own configuration/recipe and separated sources files inside the main Repo source.
The only reason way any AOSP device have updates easier is just like Chad wrote, they have all the sources files released, plus the AOSP source is made to be used with AOSP devices, so they need to make very little changes when google releases things to build a working ROM for they devices, plus there is literally hundreds of developers building for AOSP devices simply because is that simple anyone can build and help.
On the oppose to none AOSP devices were there is only a few developers as things are very hard because we don't have sometimes a clue in what to do, as we don't have the devices source, google changes the source on a way that only works with AOSP devices, so after a new OS is released a lot of things is need to be made from scratch.
If any one think is simple to build for any device just go for it, instead of be criticizing and posting none sense about thing you don't now how works.
Click to expand...
Click to collapse
perfect explanation... I admire your work