Related
Can anyone please explain what AOKP is? I know it stands for Android Open Kang Project, but what is Kang? I've tried searching the forums here and in RootzWiki as well as a general Google search and I've come up with nothing that is helpful.
I've seen a lot of AOKP roms, but no explanation as to exactly what they are, although I've noticed that many of them have a lot of the CM9 mods.
Thank You!
I could be wrong but I'm pretty sure "Kang" is just the name of the team that develops the ROM.
Kinbote said:
I could be wrong but I'm pretty sure "Kang" is just the name of the team that develops the ROM.
Click to expand...
Click to collapse
im not sure if that was what it meant to begin with, but these days it means a rom compiled by a person rather than a server.
so most of CM's roms are compiled automatically by there servers. However some people make CM Kangs by taking the source and compiling it them selves. This means they can add all the commits/mods/features which the servers have but dont have assisgned to the roms for various reasons.
So Kangs will often have slightly newer features and are also less likely to have issues because a user has gone through and made sure everything is in the rom(Hopefully). where as the servers wont know if a driver is broken/missing.
You can also get kangs of other roms i suppose. sorry if i repeated myself
Kang
The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
http://wiki.cyanogenmod.com/wiki/Terminology
AOKP is a play on AOSP, the Android Open Source Project.
AOKP is basically any rom made by or from the CyanogenMod source. It it NOT true CyanogenMod however.
Oh, well I was completely off. Thanks for the corrections.
neok44 said:
AOKP is a play on AOSP, the Android Open Source Project.
AOKP is basically any rom made by or from the CyanogenMod source. It it NOT true CyanogenMod however.
Click to expand...
Click to collapse
AOKP is actually not from CM source. As you can see in his ROM thread, http://forum.xda-developers.com/showthread.php?t=1402341 it has nothing to do with CM9 kangs.
It's just a play off AOSP and the general status of the Android community. AOKP is build from AOSP source, not CM9, even though I use bits and pieces of it. If you look, most of the features to AOKP are unique .
Sent from my Galaxy Nexus using Tapatalk
i stand corrected. i thought it was due to their use of the word in almost everything.
Interesting.
It certainly has the oddest boot animation of the lot. Trés cute..
Thanks Roman!
Romanbb said:
It's just a play off AOSP and the general status of the Android community. AOKP is build from AOSP source, not CM9, even though I use bits and pieces of it. If you look, most of the features to AOKP are unique .
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
oh....... I thought it was a reference to chess ....Android Opening King Pawn 1st...... Thx for clearing that up...........
Wow! Thanks for all the responses. I'm glad that I'm not the only one who didn't know what it meant, but I think I have a better idea now. But why use Kang instead of Source (AOKP instead of AOSP) if it's built from source? I was always afraid to flash an AOKP ROM because I didn't know what it was and just thought that it was a ROM in its early alpha stages and had a ton of bugs.
Thanks again!!!
erik1213 said:
Wow! Thanks for all the responses. I'm glad that I'm not the only one who didn't know what it meant, but I think I have a better idea now. But why use Kang instead of Source (AOKP instead of AOSP) if it's built from source? I was always afraid to flash an AOKP ROM because I didn't know what it was and just thought that it was a ROM in its early alpha stages and had a ton of bugs.
Thanks again!!!
Click to expand...
Click to collapse
Because AOSP is pure stock Android. With AOKP, new features are being added in. So calling his ROM AOSP when its not AOSP is misleading.
AOKP is just simply a name of a ROM. Developers can give their ROM names anything they'd like. AOKP is certainly not buggy and I use it as a daily driver (even on nightlies). Very good ROM and maintained with updates
zephiK said:
Because AOSP is pure stock Android. With AOKP, new features are being added in. So calling his ROM AOSP when its not AOSP is misleading.
AOKP is just simply a name of a ROM. Developers can give their ROM names anything they'd like. AOKP is certainly not buggy and I use it as a daily driver (even on nightlies). Very good ROM and maintained with updates
Click to expand...
Click to collapse
Ok, great! I'm coming from the original Incredible and have never heard of AOKP til now, so thanks for helping clarify for me. Looks like AOKP might be my next ROM choice
Thanks to the OP for creating this thread, I was wondering the same thing.
erik1213 said:
Ok, great! I'm coming from the original Incredible and have never heard of AOKP til now, so thanks for helping clarify for me. Looks like AOKP might be my next ROM choice
Click to expand...
Click to collapse
You're welcome. I've never heard of it either but I just always assumed it was a name of a ROM
I recommend using franco's kernel with the ROM. Both of them push out updates every other day. You can always wait for feedback on the kernel before flashing but they're usually both good to go in terms of stability
There's a lot of debate about what kang actually means. From what I've read it's developed to mean anytime you take bits and pieces of code from other people and incorporate them into your own mod. If you didn't write it then you "kanged" it from someone else. Someone else probably knows the original origin of the word, but at least this gives a good definition.
Sent from my Galaxy Nexus using Tapatalk
so they are or aren't based off of Klingon technology?
õ_Ô
Will there be a cm 9 for the Inc? Because there is a lot of supported phones but not the Inc
I just need to flash something
Sent from my ADR6300 using xda premium
Try kushdeck's ROM, I'm running it and it works great.
Sent from my ADR6300 using xda premium
Kushdecks rom is pretty great. I ran the latest build for several days with no problem.
You guys both didn't answer the question, lmfao Are we getting dropped?
Technically there are no truly supported device for CM9 as they haven't even made any nightly releases. With that said, according to the official statement, QSD8250 devices (Nexus One, Inc, Evo4g) should be supported. That is planned but not definite.
http://www.cyanogenmod.com/blog/cm9-progress-update
Above is the official statement from CM. If you want CM9 support, CUViper is the CM maintainer for the Inc. Coming from a Galaxy Nexus user using AOSP, AOKP is a great ROM based on stock. CM9 is not really even ready on the GNex so I'd say they're still working on it. It's not as simple as a transition from froyo to gingerbread.
Evervolv ICS rom preview is better than omx and INC-Deck imo. I have a post on rootzwiki with everything you need, link to the rom, gapps and the exchange.apk fix
apophis9283 said:
Evervolv ICS rom preview is better than omx and INC-Deck imo. I have a post on rootzwiki with everything you need, link to the rom, gapps and the exchange.apk fix
Click to expand...
Click to collapse
Haha, maybe I should just follow you around apophis and keep giving a +1 to Evervolv ICS p5
But seriously, best ICS rom out there right now IMHO
Hey a good rom is a good rom. Im not bashing other devs but the rom is the most complete at the moment. Since he only post updates on twitter i post everything everywhere i can so more people can have this awesome rom
I used to be a hard core cyanogenmod user and I recently switched over to MIUI which will be coming out with v4 soon
I am much happier with MIUI.. give it a try..
jss24,
Is MIUI v4 based upon ICS? Is there some place that gives info about what can be expected out it. I would like see what they are cooking up.
yes there is a CM9 in the works. most of the ICS builds that are out now for the phone are repo'ed from CM source.
I don't know if CM9 will get inc support but the kushdeck alpha 5 has the camera working now; so feel free to FLASH AWAY!! eh, eh, see what he did there?
There is already a CM9 release out for the INC, but I'm assuming it's very buggy and it is missing some important apps.
Here's the link:
http://rootzwiki.com/topic/10750-romunofficialcm9-with-working-hardware-acceleration/
Be sure to check further down the page for another download that's required in order to boot it up.
Not really a release more along the lines of a port. I dont believe it will have any more support
nope R2 pulled repo from cm so its not a port. they are work on it. we still have one maintainer left. CUViper. i have faith in him.
First line in r2s post says , so i ported cm9 to the inc earlier to see if hardware acceleration worked
Why would he say that if it wasnt a port?
Likely to be a port only, but that's where most of our great ROMs come from. These are called AOSP for a reason...
On another note, CCM7 (V10) is a great ROM to hold you off until ICS hits us in February, oops did I drop dates?
Oh well, I was going to post pictures of my setup, but I guess I am too new.
What is ccm7 v10? Where can it be found
Condemned cm7, ill pass
Now that bytecode has given us CWM, the question becomes what current ROM or branch of cyanogenmod would give us the biggest jump on getting a working image for our phones?
I think CM9 would be a good candidate. It would probably be the most popular choice to get working. I know I'm itching for ICS on our phone. I think it would make it the best phone on the market for now.
I'm no programmer so I can only say my opinion... I think whatever can be done first to get away from LG / AT&T software. If that's CM7, cool, if it's CM9, cool.
I'd think CM7 is the way to go to jump into a custom ROM that you could get working the fastest for this phone. CM7 has been out for a LONG time and it's been well tweaked and it's SOLID!
BUT... CM9 is what's coming (and for more and more phones/tabs, it's what's already here!).
I say even if it takes more effort now (vs. an older and more stable CM7), go right with CM9 and let's get this party started!
Namuna said:
I say even if it takes more effort now (vs. an older and more stable CM7), go right with CM9 and let's get this party started!
Click to expand...
Click to collapse
Why not ICS? Maybe it would be easy to port ICS for Galaxy Nexus to Nitro?
I'd say CM7 since by the time you finish getting CM9 figured out and working with the current kernal, it will have already been released by LG.
I'm going to start working on my own custom rom, at least as long as i can figure out how to get my Ubuntu setup... ugg..
Does anyone know any good guides for making your own AOSP ROMS? Or is it all, learned knowledge and experience?
I sure wish I knew what you guys are talking about. Lol
Sent from my LG-P930 using XDA App
I think CM9 is the way to go.
Question to any who know, if we were to put CM9 or any ICS on the Nitro, will it use hardware acceleration? That is the main feature I have been waiting for.
red_solo_cup said:
I think CM9 is the way to go.
Question to any who know, if we were to put CM9 or any ICS on the Nitro, will it use hardware acceleration? That is the main feature I have been waiting for.
Click to expand...
Click to collapse
Hardware acceleration for the UI? Or 3D / 2D graphics?
I think I read the other day that you can force the UI to use hardware acceleration in the build.prop file. With CWM feel free to tinker.
red_solo_cup said:
I think CM9 is the way to go.
Question to any who know, if we were to put CM9 or any ICS on the Nitro, will it use hardware acceleration? That is the main feature I have been waiting for.
Click to expand...
Click to collapse
unless someone on the CM team gets a nitro, there will be no ICS/CM9 until LG puts out a rom.
We need to just start w/ the basics. Optimize (battery life and performance) what we currently have and go from there.
I find your lack of faith...disturbing
Seriously, I think we can get a pretty damn good rom going if we put some work into it.
AllstarE4 said:
I sure wish I knew what you guys are talking about. Lol
Sent from my LG-P930 using XDA App
Click to expand...
Click to collapse
Allstar, here u go
CyanogenMod: http://www.cyanogenmod.com/
CM7 is based on Gingerbread and is a very optimized and customizable ROM (OS) for the phone, which is generally close to perfect and has a myriad of features that you don't normally find in regular/stock ROMs.
CM9 is the same basic concept as CM7, except it is based on ICS (Ice Cream Sandwich, Android's latest OS).
ICS: http://www.android.com/about/ice-cream-sandwich/
---------- Post added at 08:27 AM ---------- Previous post was at 08:24 AM ----------
In my opinion, our phone is built to support ICS or any iteration of it (clear stated by the 3 softkeys instead of 4 in gingerbread). So I suggest we proceed with either ICS or CM9.
I don't know if it matters, but I think someone should reach out to CM team and inform them of the development. I am sure they will be very interested in developing CM9 for a phone that is clearly intended to be a rival to the Galaxy Nexus.
The main thing to consider is the kernel , ICS runs on 3.xx kernel and gingerbread on 2.6 , porting 2.6 kernel drivers to 3.xx is alot of work. codeaurora kernel is a good start
https://www.codeaurora.org/contribute/projects/qkernel
bytecode64 said:
The main thing to consider is the kernel , ICS runs on 3.xx kernel and gingerbread on 2.6 , porting 2.6 kernel drivers to 3.xx is alot of work. codeaurora kernel is a good start
https://www.codeaurora.org/contribute/projects/qkernel
Click to expand...
Click to collapse
+1
Sent from my LG-P930 using XDA App
I think a simple debloated init.d optimized stock ROM should be the starting point. Starting a long project like CM9 will only slow down the adoption rate of the phone because the progress will be slow. I think most people will want to see a couple of ROM choices before they jump aboard.
Once you use CM9 it will automatically start hardware acceleration for smoothness and my upcoming base ROM that i'm including is going to have hardware acceleration and much more, please stay tune.
mod ammend
moved to general - this isn't a development query
I'm going to bet it will be cm9!
isnt riccardo from G+ already getting close to a ics release for the nitro...
Sent from my LG-P930 using XDA
Is there a difference and if so, what is the difference?
each has changelogs afaik , im using aokp and love it. cant speak for cm yet and unless im mistaken arent they all kangs right now ?
Flash them both, and have a look. It takes all of 5 minutes to flash a ROM. I used the CM9 builds on my Desire, not much of the CM9 extras are working, I'm not sure if that's the same for the Prime.
AOKP has extensive working tweaks, that much I do know.
aokp
difference is its features. cm9 is still in the works so a lot of the options you find in CM7 devices arent present yet.
On zephiK's recommendation I installed AOKP and don't see myself changing. It's a solid ROM.
hondaboi20002 said:
Is there a difference and if so, what is the difference?
Click to expand...
Click to collapse
There will be. There will be.
But for starters, AOPK is like Cyanogenmod, in the sense that both are based in AOSP. Neither are finished, at their current stages.
Im going from CM9 Kang to AOKP right now. CM9 was getting a little laggy for me (when moving around homescreens). And im sold by the AOKP tweaks
Reading the op of both rom threads can answer this
Sent from my Galaxy Nexus
Uhm okay I was going to post a topic similar to this but ill save some room on the forums by asking it here:
What is AOSP and AOKP? What do they mean and what are they? Which one is better and what are the differences? Is it a specific ROM or is it like a category?
azn android said:
Uhm okay I was going to post a topic similar to this but ill save some room on the forums by asking it here:
What is AOSP and AOKP? What do they mean and what are they? Which one is better and what are the differences? Is it a specific ROM or is it like a category?
Click to expand...
Click to collapse
AOSP is Android Open Source Project, Android before manufacturers get their hands on it and install Sense or Touch Wiz. Essentially the Nexus Primes OS. AOKP is Android Open Kang Project a modified AOSP ROM made by Team Kang, with more bells and whistles than the stock Nexus ROM. Hope this helps.
azn android said:
Uhm okay I was going to post a topic similar to this but ill save some room on the forums by asking it here:
What is AOSP and AOKP? What do they mean and what are they? Which one is better and what are the differences? Is it a specific ROM or is it like a category?
Click to expand...
Click to collapse
Fresh blood
AOSP - Android Open Source Project. Simply put, this is Android straight from Google, with no modifications. This is what you have on your phone. All of the ROMs here are built on AOSP - most, like AOKP, add modifications, while some don't.
AOKP - Android Open Kang Project. A ROM by Romanbb and his friends, built on AOSP, that adds many modifications and tweaks that aim to improve the end-user experience.
Yes it does thank you! So basically AOSP and AOKP are categories of the type of ROM a ROM is? Are there any other projects or are these the only two ones? Which one offers more stability and fluidness in the OS?
azn android said:
Yes it does thank you! So basically AOSP and AOKP are categories of the type of ROM a ROM is? Are there any other projects or are these the only two ones? Which one offers more stability and fluidness in the OS?
Click to expand...
Click to collapse
Almost.
AOSP is the version of Android that comes straight from Google. Manufacturers (such as Samsung, HTC, Motorola, etc) usually like to take AOSP ROMs and add their own modifications to it - and that's how we got Samsung's Touchwiz, HTC's Sense, Motorola's MotoBlur, etc.
However, Google partners up each year with a manufacturer to release a Nexus device. These devices are special in that they always come with AOSP, and because of that, they are always the first to receive updates to the Android OS, and are for the most part the devices with the most developer support on forums such as XDA.
AOKP isn't a type of ROM in itself - it is just a name given to a specific ROM. Like AOKP, you have for example CyanogenMod, which is yet a different ROM. Because we have a Nexus device, all of the ROMs you'll see in our development section are all built straight on AOSP. There are many ROMs out there, all unique in their own way, and the best way to find out which one is right for you is simply to try them all out. It may be scary at first, but after your 1st or 2nd flash, you'll become addicted for a few weeks
Thanks! Do you have a ROM that you recommend? Also, if all of the nexus ROM's are built off of AOSP, why is CM9 built off of Kang?
azn android said:
Thanks! Do you have a ROM that you recommend? Also, if all of the nexus ROM's are built off of AOSP, why is CM9 built off of Kang?
Click to expand...
Click to collapse
It's not, where did you read that? CM9 will be built from the ground up using the AOSP released by Google back in November.
Kang are using the Cyanogen GitHub to compile a CM9 beta ROM, as as far as I know, CM haven't released any betas (do they even release beta ROMs?) As far as I know they just go for a final build which is as stable as stable can be, people can't wait for the final builds and build ROMs using their work so we can try them as they are developed by the CM team.
That's my understanding of it anyways.
Oh my bad. I jumped to conclusions when I read the title to this post haha.
azn android said:
Thanks! Do you have a ROM that you recommend? Also, if all of the nexus ROM's are built off of AOSP, why is CM9 built off of Kang?
Click to expand...
Click to collapse
CM is not built off of Kang. Kang is simply a term used to denote a compiled build of a ROM by someone other than that ROM's team or "authorized dealer". For example, User A compiles CM, changed a few lines in the code, and then publishes it here as his own work. That is a kang, and its highly frowned upon.
The reason the CM thread is labeled a "kang" is because there are no official builds of CM9 coming straight from CM yet - they're just experimental builds as of now. The reason why its allowed, is because recognized members of the CM team are releasing them.
I unfortunately don't even have my Nexus yet, but its coming in two days and I'm getting my feet wet. However, from what I've been exposed to, one of the more popular combinations around here seem to be AOKP with Franco's kernel.
I strongly advise you not to flash anything yet, though. You seem motivated to be here, which is good - but you also seem to not know too much about the world of Android yet.
Please, take the time to read through the following links:
Basic Android Terminology
Galaxy Nexus Frequently Asked Questions
Different Guides and Tutorials for the Galaxy Nexus
After you've finished, you'll be a little more familiar with Android and how stuff works. If you have questions, I strongly advise you to search Google and XDA first - I can almost guarantee your question has already been answered before
If you searched, but couldn't find an answer, please post in the Q&A sub-forum - there are many members like myself who love to help new users who are willing to take the time to learn themselves, without expecting others to do their work for them.
Finally, as a general rule, don't post stuff in the development sub-forum that aren't specifically development related. Yes, if you'll go through them, you'll probably see a bunch of posts that aren't tied in directly to development - but two wrongs don't make a right if you have a question about a specific ROM, usually the answer is right in that ROM's thread - if it isn't, most ROMs have IRC chatrooms set up, and if they don't - consider making a thread in the Q&A sub-forum.
Quick question for those who understand more about the kernel than I do.
Why doesn't WiMax work on any of the new ICS builds. I thought the benefit of TeamWin writing the wimax implementation from scratch was we have the source and can tack it into anything. If the ASOP kernel has been released, what is keeping us from plugging in the WiMax bits and complining?
I understand that many of the driver sources are held by HTC and won't work until they release their ICS code. I just thought WiMax would be the first thing that would be implemented.
Thanks
It takes time, and since the code hasn't been released, they have to get it from scratch and test it out until it's nearly perfect. Just be patient.
I'm in no rush, this is just out of sheer coding curiosity.
I thought ICS code was released by Google and the WiMax code was written by the TeamWin guys? If both of these are available what else does it take to get it working?
My only guess would be that google releases a vanilla kernel. We need and Evo ICS kernel, and the source for that kernel has not been released? If that is true, what kernel are current ICS builds using? Anyway, I'd be interested to hear how this all works.
Thanks
amw2320 said:
I'm in no rush, this is just out of sheer coding curiosity.
I thought ICS code was released by Google and the WiMax code was written by the TeamWin guys? If both of these are available what else does it take to get it working?
My only guess would be that google releases a vanilla kernel. We need and Evo ICS kernel, and the source for that kernel has not been released? If that is true, what kernel are current ICS builds using? Anyway, I'd be interested to hear how this all works.
Thanks
Click to expand...
Click to collapse
I think ics builds are using tiamat 4.0.1 kernel
Interesting. I guess that would mean it is supported in the kernel, but the networking connections have yet to be written into the OS then. Thanks for the info.