Related
Am I the only one who is unhappy with the slim pickings of ROMs that are available for the SK4G?
Does anyone know anything about an ASOP ROM?
It's AOSP (Android Open Source Project) and you're not the only one not happy with the current SK4G options. I personally want MIUI or CM7, but seeing as we're currently stuck with Froyo, we'll have to see what the devs can cook up.
Sent from my SGH-T839 using XDA App
For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.
sduvick said:
For future reference, questions go in the General forum, not the Development Forum.
As for AOSP or MIUI, I know that AyoTeddy and Revolution are currently working on separate MIUI roms, and for AOSP, I'm working on that, but not sure exactly what you want from AOSP that's different from what we have?
If you are unhappy with the selection of ROMS here, you are always welcome to make your own, android is open source for a reason.
Click to expand...
Click to collapse
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App
ayoteddy said:
If they want the real miui we will need some sort of aosp gingerbread to start with and a custom CM7 kernel or something.. Since we dont have either yet I guess we'll have to make the best out of what we have now like we have been. But those wanting a taste of miui may like what I have planned for my next release.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
And so anticipation had set in, i can't wait ayoteddy. im very excited. SMX was great, and SMGC was awesome, and now with this? whewwww. think i better go lay down, lol.
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Thank you for joining the Sidekick 4G section , & we welcome you but if you want you could pause the game's for the ROM if anything & Question 1 is a no & Question 2 no cause they have to be compiled with the 2.3 kernel .
- Said by Sduvick
jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse
Revolution, thanks for relaying my responses.
jmpz, I tried building the source before, but was unable to build it completely, but that was possibly because of some errors with my dependencies. The kernel compiles fine from source, you just need to pull initramfs, or you can get it from Dr. Honk's github.
Thank you for your answers.
So, can anyone enumerate the list of drivers which we should extract from kernel?
I can name these:
1) Keyboard
2) Mic
3) 2 speakers
4) buttons
5) front camera
6) rear camera
7) trackpoint
8) lcd
9) digitizer
10) 3.5 jack
Please correct me and add missing
If I understanding it rightly the key problem is getting proprietary drivers from the kernel. Right?
nope, the key problem is trying to build the system entirely, without any errors, which may be easier with someone following a stock designed build environment. I don't use Ubuntu which is what has the listed dependencies for every tutorial I can find. You can get the drivers out of Dr. Honk's voodoo kernel ramdisk here: http://forum.xda-developers.com/showthread.php?t=1145139
There shouldn't be any problems if you just set up a build environment following the directions in any of the tutorials, then add the platform from the samsung source.
I'm a linuxoid - so these tutorial are for me. Thank you for the link.
By the way, drivers are in Linux Kernel, so I don't think that I need to use Samsung Platform from the source. Instead I wanna use platform from AOSP or Cyanogen. Correct me if I'm wrong.
I think that grabbing drivers from kernel source from samsung would be enough to build the rom.
jmpz said:
I'm also interested in porting CM7 to Sk4g cause I'm used to when I had G1 and now I'm using Sk4g without it.
I have programming skill and understanding of linux architecture. I've read about android architecture and AOSP and how to build Cyanogen from source. I'm running a tech firm (about 30 employees) - we are developing games that's why I don't have enough time to port it faster but I'm going to do it in a month or two.
So, I need help from experienced dev for android who is willing to build AOSP rom for Sk4g.
Here is what I'm going to do:
1) I'm gonna try to build Kd1 rom from source (there is an opensource code from samsung) and flash it to my Sk4g
2) Change the platform in original source to AOSP 2.2 and remove all TMOBILE apps - then build and flash
3) I'll try to find all hardware specs of the phone to compare with other samsung devices. It can help to exctract proprietary drivers of the phone. I think that the drivers are commonly the same, but I need to identify it.
After that I'm gonna upgrade to AOSP 2.3 but I don't have enough knowledge right now. Can some experienced devs answer the questions:
1) Are the linux kernels of AOSP 2.2 and 2.3 identical?
2) Can I use device drivers from 2.2 on 2.3?
If someone is interested in this project - please let me know and let's start the job. I think that my progress wouldn't be fast due to lack of time.
Click to expand...
Click to collapse
I 100% support your efforts. I want Cyanogen on the SK4G badly, but I'm not sure what kind of help a non-programmer like me could do, but do have some experience with flashing phones and such, so if there is anything you need let me know.
If you do get rolling heavily on this, I'd be willing to donate monetarily to your efforts.
If anyone can get CyanogenMod 7 on the Sidekick they would definetely get a donation from me. Id be thrilled. Glad to see its going to be worked on.
Sent from my Sidekick 4G using XDA Premium App!
I am building an aosp ROM for the galaxy player 5.0 as an independent study at my school. I have the stock kernel for it that I extracted out of an odin image and I was wondering, do I have to build aosp around the kernel because I heard aosp kernels aren't good with the drivers and I need every function to work. I have found many tutorials for aosp and I am not going to use Googles since I can't understand that as much as other ones on the internet. Can someone enlighten me on the subject so I'm not going to fail, its due by january and I am still on the fence about whether I can do this. I just need some guidance and not to have somebody do it for me.
Hey guys, I have been looking for a jb miui ROM for this device and i cant find one, i know there are some ics miui ROMs, but i would really like a jb miui ROM.
There is one for the vibrant, can I use it for my Galaxy s 4G or can anyone port it to our device?
Vibrant MIUI JB ROM:
http://forum.xda-developers.com/showthread.php?t=2289234
Thanks
i'll build it when miui comes out with miui 4.2
airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
Thank you i will be looking forward to it.
Beast said he would do it.
sent from me
that's been in my queue for a while along with aokp aries and paranoid android.
airfluip1 said:
i'll build it when miui comes out with miui 4.2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2313073
Just because there are some homebrew ports doesn't mean that MIUI is 4.2 yet.
http://en.miui.com/download.html
Official Downloads
Author : MIUI Developer Team
Kernel : Android 4.1
Latest update : 3.6.21
Download : http://www.miui.com/download.html
Language : Chinese and English
Click to expand...
Click to collapse
Why does it matter ? We use unofficial ROMs anyway...
sent from me
That's like saying that since a car, airplane, and weed-whacker all run on gas, you should just put the same stuff in each. Actually, the unofficial ROMS is a more tenuous connection than my gas connection. It's more like saying that since a bullet train, horse, and diesel bus all run on fuel, the fuel which goes into each shouldn't matter. It's all fuel.
Hey, you could (please don't) use an unofficial Vibrant ROM too. That's unofficial. What's the difference? The difference is that it won't work. And might brick your phone. That's bad.
Our only current Aries kernel is 4.2.2 and still has issues. MIUI is still 4.1.2 and would introduce an entirely new set of issues tied into GPS, Bluetooth, and so forth if/when a 4.1.2 Aries kernel was compiled. Does that make it impossible? No. But it means that as the build impetus - when MIUI is 4.2 - has not happened yet... it's not a great use of time yet. Unless one of the devs wants it. In which case, MIUI being not-updated is something they don't need to be hammered over the head with.
http://forum.xda-developers.com/showthread.php?t=2313073
4.2.2?
Port. If YOU see source linked from that page so our devs could actually do something useful to build that...
Hi Theraze
I have to disagree with you.
Port is not a dirty word and most of our ROMs are actually ports and not built from source. Furthermore, MIUI ROM is usually ported and not built from source and only recently did Xiaomi open their sources for the public. Even more than that, both MIUI versions brought to us by Beast were ports from Nexus and not built from source.
Now, regarding the incompatibility between kernel & OS - if it works on Nexus, I assume the adjustments were made, so one can enjoy both 4.2.2 & MIUI benefits. There is no logical reason why it couldn't be ported to our beloved device.
sent from me
I'm not saying it can't be done. I'm saying that our build-from-source dev who asked you to let him know when it hit 4.2 hasn't had his request met.
Does that mean that someone (him or another dev) CAN'T port it? Nope. But it makes it a lot less likely that air can just pull the source in and compile it using the Aries bits if the buildable MIUI is still only 4.1.2 and our Aries is 4.2.2 instead.
Again, I think we're agreeing on the general bits... yes, this is possible. But airfluip1 asked to be notified when buildable MIUI was 4.2.2 and that's when he said he'd build it. Not port it.
I don't care if a ROM is ported or built from source.
I will try to play with porting it myself.
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.
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