Develop Bugs

[Q] What is AOKP?

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?
õ_Ô

[Q] ics custom rom & camera what exactly is the problem?

In most of the custom rom threads, dev's do not like being asked about why the camera doesn't work. But I can't seem to find the answer so i'm posting it here.
What exactly is the problem with ics and camera's? why are there so much difficulties in enabling the camera in ics?

madcow_mda said:
In most of the custom rom threads, dev's do not like being asked about why the camera doesn't work. But I can't seem to find the answer so i'm posting it here.
What exactly is the problem with ics and camera's? why are there so much difficulties in enabling the camera in ics?
Click to expand...
Click to collapse
Because ics is a new android base and they are working as hard as they can to get it working. They don't want to hear about it not only because its in the list of what doesn't work and don't want bug reports, they also have put in an incredible amount of work and so many people put pressure on them about the camera as it is. Developing roms and kernels without a working base to start with is incredibly painstaking and is not easy. It's amazing they have gotten as far as they have with it since ace devices have no official ics base to work with. Just be patient. It will all get worked out eventually.

And don't forget that camera is not the most important in a phone
So they're going step by step... this is a very good way to proceed.

Because camera is for cam whores jk
Sent from my Inspire 4G using XDA App

The guys at the Desire development managed to get the camera working: http://forum.xda-developers.com/showthread.php?t=1403113
It's a rough hack and not very stable yet but works!

Also, the current ICS roms are running 2.6.x kernels, I'm positive it has something to do with that. Wonder if we'll even see 3.x on the DHD! Hope so!

Don't understand me wrong. I have great appreciation for the work that dev's do. Everyday I enjoy the fruits of the custom rom that I have loaded onto my device.
It was just that the camera in ics seems to be a problem for many custom rom developers and I assumed that it was something more specific to the developements with ics.

Gizmoe said:
Because ics is a new android base and they are working as hard as they can to get it working. They don't want to hear about it not only because its in the list of what doesn't work and don't want bug reports, they also have put in an incredible amount of work and so many people put pressure on them about the camera as it is. Developing roms and kernels without a working base to start with is incredibly painstaking and is not easy. It's amazing they have gotten as far as they have with it since ace devices have no official ics base to work with. Just be patient. It will all get worked out eventually.
Click to expand...
Click to collapse
The guy was simply asking for info. He just wanted to know if anyone has an idea why the cam is a commom obstacle for different devs.. He wasn't underestimating the developers' work(who during my 5 years with xda, has proven to be the Gods of mobile modding!)
No harm in asking, right?
Sent from my HTC Desire HD using Tapatalk

madcow_mda said:
Don't understand me wrong. I have great appreciation for the work that dev's do. Everyday I enjoy the fruits of the custom rom that I have loaded onto my device.
It was just that the camera in ics seems to be a problem for many custom rom developers and I assumed that it was something more specific to the developements with ics.
Click to expand...
Click to collapse
The kernel has changed and that requires new libaries to allow the camera to interact with it, these are the properiatary blobs that only HTC can officialy provide, now it should be possible when one of the DHD sister phones i.e Desire Z are provided with an official build that the camera can be reverse engineered, but if not it's gonna be a matter of trial and error to get any knid of functionality.
BTW If anyone with a better than my sketchy understanding wants to butt in and correct me please feel free
BTW BTW Lordclockan has a build with partialy working camera up and running

I agree with you. All the best to the devs ! Good luck !

[Q] AOKP or CM9 kang?

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.

[Q] ROM Development and AOSP Development overlap?

Pardon the noobish question, but with the release of AOSP Sources for 4.0.4, I'm wondering: How much duplication goes on between ROM devs and AOSP devs?
When ROM devs and Kernel devs are tweaking kernels, are they fixing and optimizing the same things as AOSP devs? Or are they more often working on two different sides of the code, and fixes from one side advance the state of the art for the other?
Another way to put this: Right now, I'm using a custom kernel. Is it likely that a 4.0.4-based custom kernel will actually offer improvements over the current 4.0.3-based version of the same dev's kernel? Or have devs already made most of the tweaks that the AOSP devs did, resulting in a very modest improvement.
I'm just trying to temper my excitement a bit. I know that 4.0.4 would likely be huge coming from stock 4.0.2, but if the ROM devs are already well ahead of the AOSP folks, I won't expect 4.0.4 Gummy to be that different than 4.0.3 Gummy (for instance).

The devs merge the new code and stay current. They keep their tweaks too etc.

RogerPodacter said:
The devs merge the new code and stay current. They keep their tweaks too etc.
Click to expand...
Click to collapse
I understand, but I'm wondering how often the Dev tweaks ARE the new changes in a new AOSP release.

wanderfowl said:
I understand, but I'm wondering how often the Dev tweaks ARE the new changes in a new AOSP release.
Click to expand...
Click to collapse
Thats pretty rare, though may happen once in a while. Mostly the devs work on new features code and additions. I'll try to think of an example and post if it comes to me.

RogerPodacter said:
Thats pretty rare, though may happen once in a while. Mostly the devs work on new features code and additions. I'll try to think of an example and post if it comes to me.
Click to expand...
Click to collapse
The only one I can think of is the swyping of the notifications
Sent from my Galaxy Nexus using xda premium

[concept] CM9

Hi!
Guys maybe should we need this 4.2/4.3 stuff with no support for 'non neon' arch
and make full working CM9 (maybe PAC) ROM
we don't have this one... only ICS stock/mod Mod Edit..profanity removed
what do U think??

Well, I think you'd get more people on board if you phrased it in a way less insulting and/or demotivating towards the devs.
Most of them, if not all, have put in a lot of their free time doing pretty amazing stuff, and brought AOSP goodness in many different flavours to our Glides.
I would personally like one ROM, which is a stable all-rounder. A final, definitive build, if you will. But I think that would require a group of devs hammering out the kinks, and a lot of time. I personally wouldn't mind less features, as long as the regular things work, including GPS and VOIP. The only added thing I wish for, aside from debloated stock, is being able to UV/OC the CPU.
But whatever happens, I'm grateful to all the devs here. Even for just trying, and coming up with impressive ROMs.
Sent from my SGH-I927 using xda premium

I have a linux system up, CM9 repo sync'd and downloaded the samsung opensource for ICS kernel ....
If you read through the CM9 thread, Dman dropped it and went right to CM10 ...
Now on CM10.1, which we're on now (JB 4.2 ?) the Tonyp bluetooth doesn't compile (so i've read) BUT in the thread for his device (LG Optimus 2x) the bluetooth (headset profile) would work with the bluez built into it on 10.1 (jb 4.2.1) ...
Now, I did buy a Relay 4G, it's in the mail so I'll be able to play with my glide as much as I want without taking so much time etc. so i could play w/ ICS ... but just suggesting this isn't enough without actually doing something to help out ....
What've you done to pitch in and make this idea happeN?

To All Devs,
I say a big thank you for all the execellents ROMs created I never knew the hard work you guys put in to it until I tried to create a custom ROM for a Chinese android phone(tecno L3).kudos to you all.
Sent from my SGH-I927 using xda premium

Any chance to revive this idea of a CM9 fully working? No voice-BT and no Skype bugs.