Related
I have been waiting for a long time assuming some developer might take up development for Xiaomi Mi-ONE phone which ships with MIUI ROM as stock, with recovery that can let you boot into two different partitions for flashing an updated ROM when you need etc.
However, there seems to be absolutely no interest in developing for this phone, even after the sources are out ! I bought this phone hoping I can make good use of the "unlocked from factory " ecosystem. The phone has a recovery, but it can flash only an update.zip file which means i can only update the OS with a newer MIUI version that releases every week. Other than that, there is no custom kernel/recovery that i can use with this phone, simply because there is nothing developed yet.
Having a custom recovery would help people flash MODS like beatsaudio apks & libs, framework mods etc . I somehow like this phone even with all this handicap of custom recovery not being available yet, but hope some one starts a development effort for this beast of a phone and help ppl like me
I would myself try and help in whatever way i can for the development of this phone, but since i have never tried any development activity for a phone, i am at sea !!
Esteemed developers, plz help !!
cwm mi-onespuniq;27636172]I have been waiting for a long time assuming some developer might take up development for Xiaomi Mi-ONE phone which ships with MIUI ROM as stock, with recovery that can let you boot into two different partitions for flashing an updated ROM when you need etc.
However, there seems to be absolutely no interest in developing for this phone, even after the sources are out ! I bought this phone hoping I can make good use of the "unlocked from factory " ecosystem. The phone has a recovery, but it can flash only an update.zip file which means i can only update the OS with a newer MIUI version that releases every week. Other than that, there is no custom kernel/recovery that i can use with this phone, simply because there is nothing developed yet.
Having a custom recovery would help people flash MODS like beatsaudio apks & libs, framework mods etc . I somehow like this phone even with all this handicap of custom recovery not being available yet, but hope some one starts a development effort for this beast of a phone and help ppl like me
I would myself try and help in whatever way i can for the development of this phone, but since i have never tried any development activity for a phone, i am at sea !!
Esteemed developers, plz help !![/QUOTE]
My mi-one is awaiting.collection at the post office, so keep on eye on miui-au
---------- Post added at 03:26 PM ---------- Previous post was at 03:23 PM ----------
And the reason there is no custom kernel/recovery/rom is because no source is available. The rom is not open source (only a few apps are), and no kernel source has.ever.been made public (which is against gpl, i know, but its the truth)
lenny_kano said:
My mi-one is awaiting.collection at the post office, so keep on eye on miui-au
And the reason there is no custom kernel/recovery/rom is because no source is available. The rom is not open source (only a few apps are), and no kernel source has.ever.been made public (which is against gpl, i know, but its the truth)
Click to expand...
Click to collapse
well its good then.. i ll keep an tab on miui-au Thanks for the info.
I heard MIUI is actually built on CM9 base. So could it be possible to take AOSP CM9 kernel source and tweak it for MI-One ? I guess most of the hardware is similar between Nexus S & Mi-One, except for some specific functionality. May be i should give it a try .. do you hav any suggestions ? I basically hate the stock recovery which comes with this phone, coz it allows me to flash only update.zip and not any other zip file unlike the awesome CWM recovery !!!
And you most likely won't many developers are not happy about what the Dev of MIUI did by taking the code of another developer making it closed source and then selling it. Not to mention there are things that are legal in China that are not in the rest of the world. With a huge China government backing backing it makes many people avoid it.
sent from my cell in Arkham
krispuniq said:
well its good then.. i ll keep an tab on miui-au Thanks for the info.
I heard MIUI is actually built on CM9 base. So could it be possible to take AOSP CM9 kernel source and tweak it for MI-One ? I guess most of the hardware is similar between Nexus S & Mi-One, except for some specific functionality. May be i should give it a try .. do you hav any suggestions ? I basically hate the stock recovery which comes with this phone, coz it allows me to flash only update.zip and not any other zip file unlike the awesome CWM recovery !!!
Click to expand...
Click to collapse
The mi-one is more similar to the htc sensation than anything else, but no, without device specific stuff from xiaomi its just not gonna happen. I might try sometime if i can do it just via ramdisk mods but i doubt it (wouldnt hold your breath).
As for the comment about taking stuff and selling it, that was hardly the case. CM was used as a base for ports, but the mi-one rom (which is the only one thats "sold") is xiaomi code. The only thing theyve done which is a violation of other developers is not releasing the kernel source.
Hi,
I see at least 3 different CM11 roms based on kitkat:
* http://forum.xda-developers.com/showthread.php?t=2524961 [ROM] CyanogenMod 11.0 | Android 4.4.2 KitKat [KANG] [May-6]+[NIGHTLIES]
* http://forum.xda-developers.com/showthread.php?t=2530073 [ROM][STABLE][Android 4.4.4] CyanogenMod 11 with 3.0.16 kernel [July 25, 2014]
* http://forum.xda-developers.com/showthread.php?t=2692278 [UnORom][3.4Kernel] CM-11 Android 4.4.4 [Stable v2.0][29 July][Final]
All more or less unmaintained as far as I can see - please correct me if I'm wrong!
What are the remaining difficulties to get a official CM11 ROM out of these? Then a lot more infrastructure from CM could be used - e.g. development tools, build machines & downloads. If the problem is to get a build machine on which 3-5 persons could would together over the Internet - I'll spend a vserver on my own dedicated server if there is a serious effort to bring up an official CM11 ROM.
If there are rather tiny things I could try(!) to help - I have almost no experience with android system development, but with Linux and development (C, Java, embedded devices,...) in general.
Two links for the rough procedure:
* http://wiki.cyanogenmod.org/w/Doc:_porting_intro - the hard part, but luckily almost done (isn't it?)
* http://wiki.cyanogenmod.org/w/Doc:_Submitting_A_Port - the final
Wiki-entry: http://wiki.cyanogenmod.org/w/Pyramid_Info
+1 for uptodate pure CM11 rom for sensation. I hope someone will join to you.
I think Flemmard's variant of CM is ready to be official!
official CM11 to Sensation!!!! We need it
+1
+1 It would be great thing for senny to so see official CM11 because many developers left us.
I don't think it's possible to make an official CM11 for our phone. IIRC, to be official it can't use legacy drivers and for the CM11 to work on our phone, I think we are using drivers from ICS because that's until where our drivers are updated, I'm not sure.
And "official" one in other hand would be amazing, I tried PA and etc but I always return to CM.
scanferr said:
I don't think it's possible to make an official CM11 for our phone. IIRC, to be official it can't use legacy drivers and for the CM11 to work on our phone, I think we are using drivers from ICS because that's until where our drivers are updated, I'm not sure.
And "official" one in other hand would be amazing, I tried PA and etc but I always return to CM.
Click to expand...
Click to collapse
Flemmards CM use KK drivers.
+1 for me too.
It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
That's not true... Team Venom also left us
For now we have official slimkat builds and maybe bilal liberty still develops for senny.
That's sad. We had many great developers and suddenly many of them left us. It will be great to see official CM builds.
Thats very sad, why they all leaving, i dont understand that. How's Ivanich latest 08/27 rom? Better than Sultan 07/25?
greetz
macicgangsta said:
That's not true... Team Venom also left us
For now we have official slimkat builds and maybe bilal liberty still develops for senny.
That's sad. We had many great developers and suddenly many of them left us. It will be great to see official CM builds.
Click to expand...
Click to collapse
bilal don't support our device anymore.
Inf1n1te said:
...Ideas?
Click to expand...
Click to collapse
The good thing is that all the great developers left us with good ROMs.
I think it is difficult to replace the devs. I can't fix the bugs they didn't fix until now, but I would like to try to keep at least one of the Cyanogenmod ROMs updated with upstream. I think in a month or two I will have time to start with that (if no one else is doing it until then).
@mifritscher: I think the lack of a build (or at least download-) server was a problem for devs here and then. So yes, your offer could be very helpful! Thanks for that!
Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
Albinoman moved to Galaxy S5
SultanXDA has forced to developing Nexus 5 device
Shantur give up his work and we can flash new builds only if Sajito will up new version (contains upstream changes)
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
Sensation is a 3 year old device. i think as the devs have moved on to other devices, so should we. though our sensation has a lot of potential, i dont think devs will work on an android L port or making CM11 official. though there is hope with ivanich & bilal_liberty
Inf1n1te said:
It's good to take a question - how many developers are developing at this moment?
[....]
Ivanich has decided to close his storage, so we cannot download anything...
...Ideas?
Click to expand...
Click to collapse
I can give storage space and bandwidth if it's useful, please contact me to discuss the details.
I can build but i dont know how to make a device tree so if someone can do the device trees i can do the builds
I don't know if we have everything working as on stock, also I don't know if the rom would pass cts.
But even if everything works, I don't think there's anyone around who has enough time to maintain an official build.
But at this point there's only one cm which is still updated and that's ivanich's one. Where's the difference in having an official build?
Where to go from here?
I'm just a casual user looking for a ROM. Going through these threads is confusing and so many links are dead.
What available for the sensation right now?
cynamun said:
I'm just a casual user looking for a ROM. Going through these threads is confusing and so many links are dead.
What available for the sensation right now?
Click to expand...
Click to collapse
Except for official slimkat all available and maintained roms are part of DevB so just click here in forum in the dev:db bar on roms.
Hi guys,
I always read in the Xda forum but never wrote or asked a question...usually someone already asked them.
so I have the Mi 5S PLUS...but I hate the miui UI. can't get used to it. And yesterday I finally found that there are custom ROM for this device.
So I got few questions.
1. As far as i know, the source code hasnt been released but should be released soon. should I wait for a ROM that uses the source code?
2. I see that the most popular costum ROMs for this device are - Lineage and resurrection remix. In terms of battery life, stability and bug free rom. which one is the best?
3. I see there is one ROM with the tag [OFFICIAL]....does this mean it uses the source code? if not, what does it mean?
thanks a lot to those that answer
eliko2000 said:
Hi guys,
I always read in the Xda forum but never wrote or asked a question...usually someone already asked them.
so I have the Mi 5S PLUS...but I hate the miui UI. can't get used to it. And yesterday I finally found that there are custom ROM for this device.
So I got few questions.
1. As far as i know, the source code hasnt been released but should be released soon. should I wait for a ROM that uses the source code?
2. I see that the most popular costum ROMs for this device are - Lineage and resurrection remix. In terms of battery life, stability and bug free rom. which one is the best?
3. I see there is one ROM with the tag [OFFICIAL]....does this mean it uses the source code? if not, what does it mean?
thanks a lot to those that answer
Click to expand...
Click to collapse
1. Source code is released but rom based on source code are not released yet .You can use them but their are some bugs,
2.You can check yourself
3. Official means official rom from lineage team or other maintainers just like Global MIUI rom from xiaomi is official while xiaomi.eu is unofficial .
You can check for source in rom page for more info about what device tree and source code it uses
ashish289 said:
1. Source code is released but rom based on source code are not released yet .You can use them but their are some bugs,
2.You can check yourself
3. Official means official rom from lineage team or other maintainers just like Global MIUI rom from xiaomi is official while xiaomi.eu is unofficial .
You can check for source in rom page for more info about what device tree and source code it uses
Click to expand...
Click to collapse
Thanks for the answers. But I asked because I prefer to install one and that's it. and if someone used the both ..why not to hear opinions.
I recomend RR
eliko2000 said:
Thanks for the answers. But I asked because I prefer to install one and that's it. and if someone used the both ..why not to hear opinions.
Click to expand...
Click to collapse
The reason that people don't recommend one over the other is because YMMV. I know I came from a cyanogen ROM with my previous phone and dirty unicorns on the phoen before that (along with a whole set of custom ROMs). In the end though, I found them all to be "similar". Yes, some do some things differently like some offer a lot of CPU governors, while others keep the list pretty tight. Some default with swap space on, some don't use swap space at all (this phone shouldn't need swap space). Sometimes the difference between two ROMs is just the launcher.
For me, I don't really like the MIUI launcher. It feels a lot like an iphone. This isn't a bad thing. Some people like it. I just install Apex (from the play store) and my issues with the ROM were mostly resolved. The only remaining problem is MASS STORAGE. But, based on my experience with mly previous phone, I doubt I'll find a ROM that natively supports it. But I know how to hack my way in and get that going (just need root... which requires an unlocked bootloader... and if I am reading things correctly, you need to wipe everything which I currently not willing to do... but may have found a workaround... going to test it out tomorrow).
bmg002 said:
The reason that people don't recommend one over the other is because YMMV. I know I came from a cyanogen ROM with my previous phone and dirty unicorns on the phoen before that (along with a whole set of custom ROMs). In the end though, I found them all to be "similar". Yes, some do some things differently like some offer a lot of CPU governors, while others keep the list pretty tight. Some default with swap space on, some don't use swap space at all (this phone shouldn't need swap space). Sometimes the difference between two ROMs is just the launcher.
For me, I don't really like the MIUI launcher. It feels a lot like an iphone. This isn't a bad thing. Some people like it. I just install Apex (from the play store) and my issues with the ROM were mostly resolved. The only remaining problem is MASS STORAGE. But, based on my experience with mly previous phone, I doubt I'll find a ROM that natively supports it. But I know how to hack my way in and get that going (just need root... which requires an unlocked bootloader... and if I am reading things correctly, you need to wipe everything which I currently not willing to do... but may have found a workaround... going to test it out tomorrow).
Click to expand...
Click to collapse
Wipe everything is very simple connect the phone via USB cable to PC and via twrp wipe everything then past a Rom on the phone and flash it, that's it
venezolano69 said:
Wipe everything is very simple connect the phone via USB cable to PC and via twrp wipe everything then past a Rom on the phone and flash it, that's it
Click to expand...
Click to collapse
Wiping everything is easy, yes, but I want to avoid wiping if I don't have to.
Got the phone rooted without needing to wipe it (yay), but getting mass storage enabled failed on me. I can't seem to write to the file I need to which confuses me... but that is off topic so I'll refrain from boring you with details on that.
Back on topic, if you are switching to a custom ROM you will need to wipe things. I personally would wait for a custom kernel to come out before you start playing with custom ROMs unless the custom ROM has a feature you REALLY want. With my previous phones, the one that had a custom Kernel as well as custom ROMs was a lot more stable and had a lot fewer bugs. The one that had only factory kernel, the custom ROMs were flaky. They mostly worked, but they did have bugs. If I got a phone call or called somebody and they hung up first, it would crash the dialer and the dialer would fail to start again until I rebooted. Now a custom kernel may not have helped that, but since the kernel was based on a previous version of Android, it was unstable.
The current custom ROMs (that I have seen) are all based off of the stock kernel and not newer ones so I personally do not expect to see much benefit in changing ROMs except having different bloat and a different launcher. Well, at lest for the things I use my phone for. But YMMV.
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.