First off, I would like to say that I love this phone. I've built a couple takes of CM using the Cyanogenmod source, and am quite aware that it is based off of AOSP along with other custom modifications etc. I may be wrong, but from what I can infer, the buildspec.mk file that you must copy to the root of the source folder determines the build when you make. If CM is made from AOSP, and already contains a full working AOSP setup/configuration, how would I go about building a straight AOSP rom from the source without any external additions?
Sent from my HTC Vision using XDA App
thrice43 said:
First off, I would like to say that I love this phone. I've built a couple takes of CM using the Cyanogenmod source, and am quite aware that it is based off of AOSP along with other custom modifications etc. I may be wrong, but from what I can infer, the buildspec.mk file that you must copy to the root of the source folder determines the build when you make. If CM is made from AOSP, and already contains a full working AOSP setup/configuration, how would I go about building a straight AOSP rom from the source without any external additions?
Click to expand...
Click to collapse
Everything is based on AOSP. Everything. If you want to build pure AOSP, you need to download AOSP from AOSP. You can't build pure AOSP from source that IS NOT pure AOSP because it HAS BEEN CHANGED.
Moved to Q&A
dhkr123 said:
Everything is based on AOSP. Everything. If you want to build pure AOSP, you need to download AOSP from AOSP. You can't build pure AOSP from source that IS NOT pure AOSP because it HAS BEEN CHANGED.
Click to expand...
Click to collapse
Well, I pulled the files from AOSP git but I have no other build/make files to go off of other than Cyanogen's. How would I know what lines to comment out and what lines to keep?
Sent from my HTC Vision using XDA App
I think you will have more to do to get something built from scratch. From a software engineering perspective you will have to use some code that was built to bridge between the hardware (G2 specific) and the stock operating system. This is a classic UNIX paradigm - the source is portable, but you have to have the interfaces to the hardware to hook in and create a complete set.
I'm finding that my phone has a Froyo WiFi calling app, and this is being used under Gingerbread because I'm using CM7.0.3 (Gingerbread based ROM). Not a clean combination.
I'm working from the CM source tree... Take a look here: http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_Vision
Tommy.
Related
I'm tired of CyanogenMod, it there always seems to be something wrong with it, this there a custom Gingerbread Rom out there does work 100%? I am no expect on modding Roms but I am guessing CM team strips the original OS down and rebuild it, any that keep the working OS and just have some nice mods for it?
No, because there is no official Gingerbread rom for the Wildfire, ALL ROM's for it are built from source. (Or based on other ROMs, which themselves are built from source) (Except SFM, obviously, which is build from the Salsa ROM - But its not really complete for daily use as you know)
3xeno said:
No, because there is no official Gingerbread rom for the Wildfire, ALL ROM's for it are built from source. (Or based on other ROMs, which themselves are built from source) (Except SFM, obviously, which is build from the Salsa ROM - But its not really complete for daily use as you know)
Click to expand...
Click to collapse
Thanks, so let me get this straight in my mind, 2.3.3 mod like Cm7 are built for other android phones who got Gingerbread officially? so they only way to get the kind of ROM I am looking for would be to look for a 2.2 ROM?
No, CM7 is built from the source code of the Android OS. Its not based on any phone's ROM.
I was assuming from your query you were looking for a GB ROM based on the official ROM, which is why I posted that.
So, what's the difference between "4.0.4 merged into build" vs true 4.0.4 AOSP builds?
And the same question for kernels with "4.0.4 merged into build" vs true 4.0.4 kernels?
Will it get better when the devs are going to build from 4.0.4 source from the ground up?
Cuz until now I'm not really that impressed with the 4.0.3/4 "hybrid" builds (i.e. I find LiquidSmooth v1.2 a lot smoother/ faster/ better on battery than the AOKP b29 "4.0.4 merged" build)
Just curious
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
adrynalyne said:
It means they moved their customizations to 4.0.4????
So if you are not impressed, it has nothing to do with their merges. It has to the do with the rom itself.
Click to expand...
Click to collapse
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Ti2 said:
Thanks for your prompt answer
So - it's not the other way around, like they optimized their roms with implementing 4.0.4 optimizations?
You mean like Romanbb already took the 4.0.4 source and implemented his customizations?
Just trying to learn here
Click to expand...
Click to collapse
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Ti2 said:
Cheers mate, thanks for the insight it's very much appreciated
I just looked up your thread - when will your new 4.0.4 rom be up? I'll try it - I'm ready for a shift hehehe
Click to expand...
Click to collapse
There are some things in the work (besides 4.0.4) that need to be finished yet, but I would say it won't be much longer.
adrynalyne said:
Ok so, this is how we do it, usually. We have out own customized repos, and then we sync with AOSP. So everything is the current AOSP tree it is synced to, other than the customized repos.
What we do then, is diff our changes to the current 4.0.4 code and add them back, and then re-sync our customized repos.
Some roms sync from multiple sources. For example, AOKP syncs from AOSP, custom repos and Cyanogenmod. So if CM is not updated to 4.0.4, neither is aokp, to certain degrees (I am sure CM is).
I don't know about Liquid, but we (Team BAMF) sync directly and only from aosp and our own custom repos. We just finished the switch to 4.0.4.
So if you find Liquid better, its not to do with 4.0.4 and everything to do with the rom
Click to expand...
Click to collapse
Have you released a 4.0.4 rom mate?
Stretlow said:
Have you released a 4.0.4 rom mate?
Click to expand...
Click to collapse
We have merged with 4.0.4, but we havent released an update yet, no.
Ok, Ive falshed many roms and have got to know many things about roms, kernels etc.
I'm still confused with one thing though....
What's AOKP & AOSP??
Ive seen many roms with that written and a few with Not AOSP Written on them.
Anyone Help me out here?
Thanks!
AOSP - Android Open Source Project.
AOKP - Android Open Kang Project.
An AOSP ROM is a ROM based on the Android Open Source Project from Google. An AOKP ROM is a modified AOSP with various tweaks and customization.
Kang is a word that is somtimes misconstrued to mean stealing other's work and to some it has a negative connotation. In reality though, it's starting with another's work and building on it to (hopefully) make it better. It makes sense that most devs appreciate being mentioned when their work is in play within a particular rom so that's why we often see a list of mentions when various tweaks/mods/etc are utilized.
Click to expand...
Click to collapse
AOKP Android Open Kang Project
AOSP Android Open Source Project
Just do a quick google/forum search for more info.
Thanks soumya_digi & zeeshansohail
But for AOKP is just mean the http://aokp.co/ project or all project based on a AOSP?
I mean, if I take a CM and do some change, will be a AOKP?
No right?
So AOSP are all the rom based on purecode, AOKP is just the aokp.co project.
CM is one of the AOSP
AOKP are just the rom maked by team kang, maybe also based on AOSP project..
I'm confusing.
Hi everyone
Can u tell me what are AOKP and AOSP roms?
what do they do?
are they better than sense roms?
AOSP is an original ROM unmodified as Google intended it to be.
AOKP is based on AOSP but has some slight modifications but not modified to the extent of CM (Cyanogen)
As to if they are better or not well that is a matter of opinion, in terms of performance yeah all AOSP, AOKP and CM ROM's will run smoother and faster than a Sense ROM but there are plenty of people who enjoy the functionality of a Sense based ROM and those who don't.
Thank you! always wondered what that was.
KN
awesome............ dud....
aosp = android open source project
aokp = android open kang project (link https://sites.google.com/site/androidopenkangproject/)
Kokacrime said:
and what's the difference between aosp roms and stock roms, besides e.g. preinstalled samsung apps?
Click to expand...
Click to collapse
It's not really about the Samsung/Sense apps more about the whole "layer" that i.e. Samsung/HTC put over the basic rom, (touchwiz and sense in the case of samsung/htc).
So if you'd take those layers/apps away you would just have the basis which is just AOSP.
Personally, AOKP is better as it takea some influence from CyanogenMod, which is THE most popular ROM available for devices
Sent from my Desire HD using Swype beta for Android!
new website for AOKP
aokp.co/index.php/news
They are finally in milestone 6 , ICS final and will start in JB from fresh! That's awesome news because DHD is still supported. There's pics with DHD working with JB.
aokp.co/index.php/news
Sent from a dream.
So do you need clockwork recovery to flash or use aokp?
civydcex said:
So do you need clockwork recovery to flash or use aokp?
Click to expand...
Click to collapse
No. AOKP ROMs are like any other ROM; they can be flashed from any recovery compatible with your phone.
dstylazz said:
AOSP is an original ROM unmodified as Google intended it to be.
AOKP is based on AOSP but has some slight modifications but not modified to the extent of CM (Cyanogen)
As to if they are better or not well that is a matter of opinion, in terms of performance yeah all AOSP, AOKP and CM ROM's will run smoother and faster than a Sense ROM but there are plenty of people who enjoy the functionality of a Sense based ROM and those who don't.
Click to expand...
Click to collapse
Generally, can we classified ROMs as AOSP, AOKP, CM, MIUI, Sense. Am I right there is other category ?
Sent from my HTC Desire HD using xda premium
mohazia said:
Generally, can we classified ROMs as AOSP, AOKP, CM, MIUI, Sense. Am I right there is other category ?
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
It depends on the phone. For example, on this phone we have Sense because of HTC; other phones will have other overlays (like Samsung's TouchWiz). Also, some ROMs don't reside neatly in one category; for example, we have codefireX because of Team Codefire, which is descended from AOSP, CM, and some AOKP ideas.
Hello
I came from black berry so little confused on everything. Can somebody help me understand some of this.
Sent from my Galaxy Nexus using Tapatalk 2
They're branches of ROM development. Different individuals and teams work on their own ROMs and distribute them regularly. They each have their own features, looks and performance tweaks that they think are best.
As a quick start, "AOSP" is the Android Open Source Project. Google maintains the open source Android code, and individuals can pull from it and build their own ROMs off of that. So when someone says their ROM is "AOSP based", they're saying that they pulled the source from Google then modified it.
And like-wise with CM10/AOKP they provide their own source code.
CM10 = Cyanogenmod team. A very popular ROM. They do have their own ROM but also provide their own source code for those wanting to start with an already modified base. As an example CM10 based ROMs usually come with certain additional features like the CM kernel, profiles, etc.
AOKP = Android Open Kang Project. As the name suggests it is also the same idea. A source code provided by a developer of a Popular ROM (AOKP) for other users to use. Also comes with features not included in the base AOSP ROM
If any of that is wrong someone will correct me I'm sure