Related
I know LiquidSmooth is based on Slim, which I believe is based on AOSP source. Either Slim is ported to our phone and Liquid is built on top of it, or Liquid, based on Slim, is ported to our phone (or they're both the same thing). Well, what stops someone who can take Slim and make it into LiquidSmooth, from basing it off of GPE instead?
Come to think of it, I've only seen ROMs based on GPE offer a couple tweaks. Nothing as extensive as something like LiquidSmooth. Can a GPE not be modified as extensively? Isn't it required to have its source posted due to the GPL or something?
dragontology said:
I know LiquidSmooth is based on Slim, which I believe is based on AOSP source. Either Slim is ported to our phone and Liquid is built on top of it, or Liquid, based on Slim, is ported to our phone (or they're both the same thing). Well, what stops someone who can take Slim and make it into LiquidSmooth, from basing it off of GPE instead?
Come to think of it, I've only seen ROMs based on GPE offer a couple tweaks. Nothing as extensive as something like LiquidSmooth. Can a GPE not be modified as extensively? Isn't it required to have its source posted due to the GPL or something?
Click to expand...
Click to collapse
GPE isn't aosp, it's Google play edition software. It isn't open sourced to be built off of. Think of it as more of a Sense or touchwiz interface than AOSP build. A GPE rom is built specific for each device it's operating on.
A GPE rom written for an HTC m8 will not work on a samsung galaxy s5, simply because the kernels are different. AOSP roms have the same kernel for all devices. That's mainly what would keep a developer from basing a rom off of a GPE code.
Slim is built AOSP source code, along with many other roms. Liquid chooses to use slimroms as a base, but it could choose to use CM, AOKP, or another AOSP base of their choosing. This doesn't apply to GPE.
GPE roms can be modified to do whatever the developer wants them to do. However, the whole point of GPE roms is to have a very fast, debloated close to stock experience. People looking for GPE roms aren't really looking for all the bells and whistles that go with highly modified stock or aosp roms.
Whoa... There is no such thing as a ROM that will run on both an HTC One M8 and a Samsung Galaxy S5. That isn't a valid limitation of GPE. Kernels are always device specific, too. You might get a universal kernel that works across variants of one phone, but I've never heard of a kernel, an aftermarket one anyway, that will run on devices across manufacturer lines. Then again, I don't follow kernels as closely as I have ROMs.
GPE isn't open source? That's news to me. I mean, I thought all Android builds had to provide source. I mean, rule #1 of XDA is don't ask for ETAs, but I saw a moderator demand source on a ROM "sooner than later." Not naming names because I'm sure the moderator was within rights, but it seemed to at least partially contradict the spirit of the famous rule.
dragontology said:
Whoa... There is no such thing as a ROM that will run on both an HTC One M8 and a Samsung Galaxy S5. That isn't a valid limitation of GPE. Kernels are always device specific, too. You might get a universal kernel that works across variants of one phone, but I've never heard of a kernel, an aftermarket one anyway, that will run on devices across manufacturer lines. Then again, I don't follow kernels as closely as I have ROMs.
GPE isn't open source? That's news to me. I mean, I thought all Android builds had to provide source. I mean, rule #1 of XDA is don't ask for ETAs, but I saw a moderator demand source on a ROM "sooner than later." Not naming names because I'm sure the moderator was within rights, but it seemed to at least partially contradict the spirit of the famous rule.
Click to expand...
Click to collapse
Ehh, GPE may be open sourced. I think Google has to release the information for it.
AOSP though definitely isn't as specific, the kernel has to be signed for each device but it's overall much easier to port the kernel over to another device.
kernels
The Linux kernel is a monolithic kernel and all device specific drivers are compiled in the binary unless they are stand alone modules. Android itself is open source, but it does NOT use the GPL v2 licence. The code for many of the drivers and other device-specific software is closed source and only available as binaries. XDA strictly enforces providing source code for kernels because that is a strict stipulation of GPL v2. A custom ROM generally doesn't require source code since many stock-derived ROMs don't begin with source code. Sense and GPE would be varieties that don't originate from source code.
Hey guys, you who used stock 5.1 and custom ROMS that are having the latest Android version (5.1.1): what differences do you notice?
As we all know 5.1.1 is the latest version which fixes the memory leak, and Moto is still a version behind on 5.1.1: stock only is Android 5.1.
How would you compare stock to the latest Android version with the latest bugfixes and memory leak fix?
Would it be possible that Moto backported 5.1.1 fixes to stock 5.1?
Can a moderator edit "bases ROM's" to "5.1.1-based custom ROMS? I made a typo
Sparubens said:
Hey guys, you who used stock 5.1 and custom ROMS that are having the latest Android version (5.1.1): what differences do you notice?
As we all know 5.1.1 is the latest version which fixes the memory leak, and Moto is still a version behind on 5.1.1: stock only is Android 5.1.
How would you compare stock to the latest Android version with the latest bugfixes and memory leak fix?
Would it be possible that Moto backported 5.1.1 fixes to stock 5.1?
Click to expand...
Click to collapse
It is more a question of CM12.1 vs Stock ROM.
With the Stock Motorola Lollipop you have (at least in theory) a bug free ROM, it will work in every situation and scenarios.
Where with a custom ROM you will have more experimental features, a more tunable kernel and settings (that can either improve or break a ROM) and, to be honest, more support as they update almost every week where Motorola go very slow.
Pupet_Master said:
It is more a question of CM12.1 vs Stock ROM.
With the Stock Motorola Lollipop you have (at least in theory) a bug free ROM, it will work in every situation and scenarios.
Where with a custom ROM you will have more experimental features, a more tunable kernel and settings (that can either improve or break a ROM) and, to be honest, more support as they update almost every week where Motorola go very slow.
Click to expand...
Click to collapse
Yeah that's true. I was just wondering if the 5.1 version still has the memory leak which was resolved in 5.1.1. Also, CM12 based roms don't support notification tickers anymore, not even through Xposed so that's a bit pity too. But they do have features you can't find in stock or Xposed.
Just wondering which ROM gives the best performance, CM12 or optimized stock or just plain AOSP without any tweaks.
Sparubens said:
Yeah that's true. I was just wondering if the 5.1 version still has the memory leak which was resolved in 5.1.1. Also, CM12 based roms don't support notification tickers anymore, not even through Xposed so that's a bit pity too. But they do have features you can't find in stock or Xposed.
Just wondering which ROM gives the best performance, CM12 or optimized stock or just plain AOSP without any tweaks.
Click to expand...
Click to collapse
I can't say if Motorola fix the Memory issue or not. I can say too that some CM12.1 ROMs did have memory issues even at 5.1.1 but i think all are gone now.
About performance, a custom ROM for sure will bring you that. I'm not a big fan of motorola "optimizations" for our devices, in fact i would say they don't do at all.
It all depends really, you could get stock 5.1 with moggy kernel v12 which is very smooth being a linaro based kernel with other optimizations as well. (I was running that earlier today)
But you could also get a custom ROM such as blisspop. Which is very very poorly developed on our device.
A ROM that the developer uses as a daily driver is likely to be better than stock. However you'll find ROMs such as BlissPop where the developer does not run the ROM on our device and merely syncs with latest sources and uploads the builds without testing them first.
Those ROMs are likely to provide worse performance and definitely less stability than stock. Unless of course you flash a custom kernel over it, but then you've just got a sugar coated turd. And nobody wants a turd.
Sent from my XT1045 running CM 12.1 7/23 build with Optimus Kernel R38 using XDA Free mobile app
Travisholt92 said:
It all depends really, you could get stock 5.1 with moggy kernel v12 which is very smooth being a linaro based kernel with other optimizations as well. (I was running that earlier today)
But you could also get a custom ROM such as blisspop. Which is very very poorly developed on our device.
A ROM that the developer uses as a daily driver is likely to be better than stock. However you'll find ROMs such as BlissPop where the developer does not run the ROM on our device and merely syncs with latest sources and uploads the builds without testing them first.
Those ROMs are likely to provide worse performance and definitely less stability than stock. Unless of course you flash a custom kernel over it, but then you've just got a sugar coated turd. And nobody wants a turd.
Sent from my XT1045 running CM 12.1 7/23 build with Optimus Kernel R38 using XDA Free mobile app
Click to expand...
Click to collapse
YEs that is true, also there are some ROMs that are much more experimental then stable.
So a research would be need.
That being said, stock is always the safest bet but a nice custom ROM will be superior if he find one.
I'm personally very happy with Euphoria and the R35 version of the Optimus Kernel.
But you (@Sparubens ) would need to flash all the roms to find the one who fit you better, stock and non stock
It's worth considering the difference in Battery-life of Stock Firmware / ROMs in comparison to non-Stock custom ROMs. That could be an interesting thread.
Pupet_Master said:
YEs that is true, also there are some ROMs that are much more experimental then stable.
So a research would be need.
That being said, stock is always the safest bet but a nice custom ROM will be superior if he find one.
I'm personally very happy with Euphoria and the R35 version of the Optimus Kernel.
But you (@Sparubens ) would need to flash all the roms to find the one who fit you better, stock and non stock
Click to expand...
Click to collapse
I did flash almost every ROM here but there always seems to be an issue:
-CM12.1 is stable and fast, but doesn't have 4 tiles per row option in QS Settings and doesn't support notification ticker anymore (Xposed), SaberMod is smooth (Beeto) but there's a bug where you can't access SuperSU without dialing a code
- SlimROM wasn't a good experience when trying it to use as daily driver, sluggish and bad multitasking
- CM12.1 based ROMS like CrDroid and Euphoria I do really like, have some bugs like screen pinning causing reboot (CrDroid) and also no real Xposed support for CrDroid and Euphoria doesn't register all touches on the keyboard and makes my phone a bit hot, otherwise I would be very happy to have it as a daily driver, AICP was running okayish but there's been a bug for over a month that when opening the data quick menu, the percentage is misaligned, and it still hasn't been fixed.
- Stock 5.1 is nice, but it's a version behind 5.1.1 so that's not very nice either. Also heavily lacking in options, but I can use Xposed. Also there are 2 carrier labels on the lockscreen which makes no sense at all..
Also, in custom ROMS the torch doesn't seem to be functioning fully, the light density is not at it fullest. Sadly there seem to be some quirks with every ROM.
I'm ready to make compromises and have a ROM as daily driver which doesn't support notification ticker (basically all of them atm) but then there's also the torch issue sadly which pushes me more back to stock. But then again, nobody knows if stock still has the memory leak and opinions have been very different from person to person about stock 5.1.
Some interesting opinions over here, keep 'em coming!
@lost101 I personally think that there's no custom ROM that can match the battery life of stock, it has been impressive, surely on Lollipop.
Sparubens said:
Also, in custom ROMS the torch doesn't seem to be functioning fully, the light density is not at it fullest.
Click to expand...
Click to collapse
A solution for this problem seems not to be far away
http://forum.xda-developers.com/showpost.php?p=62028617&postcount=155
Sparubens said:
I did flash almost every ROM here but there always seems to be an issue:
-CM12.1 is stable and fast, but doesn't have 4 tiles per row option in QS Settings and doesn't support notification ticker anymore (Xposed), SaberMod is smooth (Beeto) but there's a bug where you can't access SuperSU without dialing a code
- SlimROM wasn't a good experience when trying it to use as daily driver, sluggish and bad multitasking
- CM12.1 based ROMS like CrDroid and Euphoria I do really like, have some bugs like screen pinning causing reboot (CrDroid) and also no real Xposed support for CrDroid and Euphoria doesn't register all touches on the keyboard and makes my phone a bit hot, otherwise I would be very happy to have it as a daily driver, AICP was running okayish but there's been a bug for over a month that when opening the data quick menu, the percentage is misaligned, and it still hasn't been fixed.
- Stock 5.1 is nice, but it's a version behind 5.1.1 so that's not very nice either. Also heavily lacking in options, but I can use Xposed. Also there are 2 carrier labels on the lockscreen which makes no sense at all..
Also, in custom ROMS the torch doesn't seem to be functioning fully, the light density is not at it fullest. Sadly there seem to be some quirks with every ROM.
I'm ready to make compromises and have a ROM as daily driver which doesn't support notification ticker (basically all of them atm) but then there's also the torch issue sadly which pushes me more back to stock. But then again, nobody knows if stock still has the memory leak and opinions have been very different from person to person about stock 5.1.
Some interesting opinions over here, keep 'em coming!
@lost101 I personally think that there's no custom ROM that can match the battery life of stock, it has been impressive, surely on Lollipop.
Click to expand...
Click to collapse
That's why we have a lot of roms outthere, everyone can choose what match better with everyone, if you want something without issues choose stock, but don't have the optimizations options, if you prefer the options, choose the one you consider is better, but always have to sacrifice something
Enviado desde mi peregrine mediante Tapatalk
Im currently on stock 6.x but my phone is getting pretty full and bugs out sometimes so I think its about time I do a fresh flash.
Is it possible to do a nandroid backup to a NAS server? A 64GB nandroid backup to a already full phone is kind of hard.
Next, I can either go 6.x or 7.x
7's notification style and doze battery life optimizations seems nice. Automatic system updates using another partition also seem good but I imagine that can only be used on Pixel.
6.x I imagine though is more stable.
So which ROM?
I personally like Android nougat more than M. Also, i find it stable enough for daily driver. I have been switching between various Nougat ROMs to find out which i like more. I am finally settled with Cm 14.1 nightlies for now.
RESURRECTION REMIX [5.8.0]
Awesome ROM with tons of customization.
RazerSharp said:
RESURRECTION REMIX [5.8.0]
Awesome ROM with tons of customization.
Click to expand...
Click to collapse
Resucrrection is way to bloated/heavy. Im sure our phone can take it but.
Looking for a Marshy? Sultans is your best bet. Simple. Stable. Clean. Reliable.
I tested almost all nougat roms. I'm stuck with legend right now, for me seems the most balanced and without serious bugs.
What about jgcaap's rom? Isn't it any good?
Official Nightly vs Jcaap vs Resurrection Remix, which is the best?
Thank you for threads like this - you can't ask in a particular ROM's thread about other ROMs... I tried the "unofficial" (CAF) 7.1.1 Ressurection Remix and I've had problems with the screen going black, doesn't mean anyone else will. So, I'm also looking for which 7.1.1 ROM to try next and want other's opinions because I just don't have time to try ALL of them myself, full wipe, install all the apps and data again, setup everything... For a day or two then on to the next over and over, but I do try to try at least a few.
The ONLY reason why I don't want 7.1.1 for certain right now is no Xposed for it yet. But, perhaps I can live without Xposed for a while as long as I have: root, adblock, privacy guard, profiles...
I'm thinking to try the "Official" 7.1.1 Resurrection Remix next? Opinions?
I recommend jgcaap's CM14.1. It's been very fast and stable with good battery life for me. He's also busy implementing Sultan's camera blobs, so camera quality is also going to be nice. Try it out for yourself, you won't regret it!
Which nougat ROM has the best battery life and the smartbar/fling navbar features?
I'm not giving up Xposed without that navbar LOL
Oh, didn't remember that Xposed isn't avalaible for 7.x yet.
Forget it. 6.x based ROMs then.
Any other NON CM based recommendations?
riahc3 said:
Any other NON CM based recommendations?
Click to expand...
Click to collapse
Purenexus
C4SCA said:
Purenexus
Click to expand...
Click to collapse
I'm having issues finding the ROM that works best for me too. I've had to resort to cm ROMs because I can't find an aosp based MM ROM that has the latest security patches. There's so few of them too . I'm currently on jgcaaps cm13 running lightning caf v50 color. Its pretty stable, but I can't for the life of me figure out why the darn thing bootloops immediately after setting selinux to enforcing. I've always set it to enforcing for security reasons in the past, and had no issues. Jgcaaps cm13 I think has the best camera hal of all the ROMs because its using color os. Not caf, sultan, or cyanogenmod (I don't even know how people consider cm hal usable).
For 7.1.1 I've tried some of the ROMs but they're missing way too many features IMO. The camera hal is one (most are using cm or caf, meh) the only 7.1.1 ROM I know of that possibly has color os hal is jgcaaps cm14. Another thing is xposed. I don't like to give google full permission over my entire system to record and do as they please, therefore I use microg. The only thing is to get micro g working, you need to have a ROM that either supports fake signatures in the developer options (ROM maintainer has to implement this, its not too hard) or an xposed module to force fake signatures. I haven't come across a single ROM here that has micro g support so I'm forced to use xposed. On top of that I use the xprivacy xposed module which is miles better at protecting your privacy than privacy guard or appops.
So yeah personally I think jgcaaps cm13 ROM is the best we have right now for MM roms. All the other MM ROMs haven't been updated with security patches in quite a while from my experience. If you don't use micro g or xposed then I would recommend jgcaaps cm14 for the color os hal, but I havent checked out his ROM in a while. I wish there was still some development on MM for our oneplus one because it seems I'm stuck between choosing discontinued MM ROMs for features + stability or actively maintained ROM with bugs + less features. I've been working on finding out how to merge security patches in to discontinued ROMs because of this. But I don't have much time in my life right now sadly.
ThunderThighs said:
I haven't come across a single ROM here that has micro g support so I'm forced to use xposed.
Click to expand...
Click to collapse
danieldmm's TugaPower ROM has microG support out of the box and there's no need to install it as a system app. HAL is still CM but it is updated very frequently (I think it supports delta OTA updates) and has latest security patches too. Had absolutely no bugs for me when I used it last time :good:
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
Hello everybody,
I'm new to the rom and kernel community and have an ageing pixel 2 device as a DD. After spending a lot of time looking for the perfect combo (rom+kernel) for my device I still am unable to zero in on the right combo for me. I know that Performance and battery are the aspects I look for the most while keeping the build as stock to google as possible without losing features and everything worked if not the same, better than before. I need help from the community to choose.
I have read about numerous builds like Pixel experience, Lineage, Proton aosp, and kernels like kirisakura, sultan, xenial (v5/v6), kazuki etc. I wanted to make the jump to the latest a12 or 13 build available but did not know which rom to go for while not compromising on battery and performance. People ask to stay on a11 and update kernel instead, for that I know it will be xenial kernel since it is apparently better than even the regularly updated sultan (also xenial isnt built for a12+ which sucks) citing it has the most number of commits or whatever. Is there anyone who faced this and chose a route that made sense? I was thinking of Pixel experience or LOS 19 or proton maintained by Enes and flashing sultan considering he updates regularly. If there is an a11 that is inherently better than any a12 rom out there please let me know so I can just flash that and also flash the inherently better xenial kernel along with it. Bonus if you think blackened mod or PK's tuning script makes a difference and is better than new kernel and new rom.
Thanks in advance.