I don't know about AOKP & AOSP?
Plz, Someone ,tell me.
Sent from my ST25a using xda premium
You could have Wiki'ed them anyways
AOKP (Android Open Kang Project) is an aftermarket custom ROM for many Android devices. A solid AOSP base with a multitude of features has made this ROM grow rapidly in popularity since it was first released in November 2011.
The Android Open Source Project (AOSP), led by Google, is tasked with the maintenance and further development of Android. If you find a custom ROM that is based on AOSP, that means it will be closer to the original, vanilla Android created by Google rather than the bloated software created by Samsung, HTC, LG, and Motorola.
Basically they both a ROM's
For more info Google Them
Thank If Helped
Related
Hi.
I am a noob, not a techy
just curios - how can your devs build ICS roms when Samsung themselves did not build/create/honed/refined the Vibrant for Android 4?
What I am trying to ask is, how can your devs manage to control the hardware via android 4, if Samsung did not supply the codes/drivers/source?
Thanks
I'm not 100% sure but I think I read somewhere you can use the source code to build a ROM and then they used the Gingerbread bootloader/kernel and from there it's debugging.... again I could be wrong.
I think they took the source, and compile the source with the characteristics of the device. then applications that do not work, modified or exchanged for other versions of other rom, like the kernel, and other modifications, which is why the rom, there are many versions which fix bugs Version earlier after many users try it. (an example of this is the ICS Passion, which is now in its version 13)
Well passion is based on cm9. Which is aosp rom using source code android releases. Basically if you have drivers for hardware and a device tree you can use that source to build for any device.
Wherelse Samsung roms are usually not directly from source but just modded firmware from Samsung leaks. Oems do use close sources drivers though, usually better and get more out of hardware.
Sent from my SGH-T959 using XDA App
Google has pushed Android source code for Jelly Bean
Google has now
pushed the Android 4.2 Jelly Bean
source code to the AOSP (Android Open
Source Project). The SDK platform is
now available to developers, so hopefully
we will see some custom ROMs based
on Android 4.2 appear in the not too
distant future.
The SDK includes access to a number of
features including interactive lock screen
widgets, a ‘Daydream’ interactive
screensaver mode, support for exteral
displays and native RTL support. We do
hope that Sony received the PDK prior to
this and is already hard at work
optimising Android 4.2. Time will tel
Source
http://www.xperiablog.net/2012/11/14/source-code-for-android-4-2-jelly-bean-released/
Sent From Xperia Sola White (MT27i)
Rooted Stock ICS
Hit Thanks If I Helped!!
Useless for our devices
Sony released sources to 6.1 soft(ics) few days ago.
Sent from my MT27i using xda app-developers app
Why isn't there any 4.1 Rom for Sony xperia p? Source code was released long.time back. Also it meets all the requirements of jellybean
Sent from my HTC One X using xda app-developers app
yes, but no one except fxp and sony are working on it
so development is going slow
screensaver? i hope "they" develop it :fingers-crossed:
Also CyanogenMod is working on it:
CM 10.1 Status Update
So we continue to work through the merger of 4.2 code and our CM enhancements. A branch in our github repos called mr1-staging has been created to facilitate the merger and is the target for core CM items (not features).
mr1-staging is not meant to be compile-able, its only purpose is to be a staging grounds for our core work. Chances are, it is useless for independent builders.
CM 10.0 (4.1.2) code is in jellybean-stable, if you are working on a bug-fix for the last stable release, patches should be submitted against that branch. If/when we do another 4.1.2 release (ie CM 10.0.x), it will originate from code in this branch.
Once staging is done in mr1-staging, we will push all that code to a 'CM10.1' branch, and eventually back to our primary 'jellybean' branch. This process is in place to make sure that we effectively move forward from CM 10.0 code, instead of starting over as was seen with the jump from Gingerbread to ICS. Patches from gerrit will be accepted towards CM 10.1, but for now, please have patience while we work through mr1-staging.
While the 4.2 updates are on a smaller scale, they do present some changes that will need to be considered and will effect our implementation of features. Just to name them briefly: Telephony Split, Multi-User, Quick Settings, and Lock-Screen Widgets. These items will be a strong focus when the initial CM10.1 branch is created.
On the feature front, +David van Tonder decided to make his weekend productive, and has already worked on the code for the majority of our MMS enhancements: Emoji support, sms split, gestures and templates, quick messaging. Notably MMS auto retrieve is not being forward ported as Google fixed that themselves. As stated above, patches will hit gerrit review after this staging process is completed.
As always, a timeline isn't and won't be available. We will continue to provide updates as we have them.
From Google+ CM profile.
Hello...
You might have noticed that our 4.1 Jellybean thread has been up for a few days while we're working on it.
Tell you what - I can see that this is going to take a bit time, therefore we're firing this project up...
What is it about?
Bringing pure Android experience to Galaxy-line mobiles.
I personally dislike all those OEM modifications and community eye-candy.
Let's bring pure Android experience to the scene!
Sakura AOSP Project releases/in-dev
Android 4.1 Jellybean
http://forum.xda-developers.com/showthread.php?t=2008632
(in-development, OS boots and seems to run, except for framebuffer)
Android 2.3.7 Gingerbread
http://forum.xda-developers.com/showthread.php?p=34665892
(in-development)
AOSP repo mirror
If Google isn't fast enough... Well:
http://sakurahost.eu/pub/aosp-mirror/platform/manifest.git
Useful development resources
Mirrored for fast downloads in here:
http://sakurahost.eu/pub/
focus on working 1 by 1
we can get all
i'm downloading oxigen source. but until 10gb it's not finished
i'll try later.
im busy right now
hey can we create our own version of android like, for example, (Android 4.3 dev by someone not in the google android company)....
Short answer: No
Think yourself if that would be possible then why would everyone stuck on jellybean.
Sent from my HTC Wildfire using xda app-developers app
You are a genius
Sent from my GT-S5830 using xda app-developers app
imda1 said:
hey can we create our own version of android like, for example, (Android 4.3 dev by someone not in the google android company)....
Click to expand...
Click to collapse
Technically there is no reason why not Android is open source and you could freely fork the code and start building your own modified version and then distribute as you see fit.
This is after all what the likes of Cyanogen Mod do, but at the end of the day you would still have to work off a current version and mod to your needs.
zacthespack said:
Technically there is no reason why not Android is open source and you could freely fork the code and start building your own modified version and then distribute as you see fit.
This is after all what the likes of Cyanogen Mod do, but at the end of the day you would still have to work off a current version and mod to your needs.
Click to expand...
Click to collapse
So, what you mean is that all ROMs actually are android version, right?
Then what does an android version exactly mean?
Does it define a unique -
ROM +kernel
ROM
Kernel
ROM +kernel + extra innovation
???
imda1 said:
So, what you mean is that all ROMs actually are android version, right?
Then what does an android version exactly mean?
Does it define a unique -
ROM +kernel
ROM
Kernel
ROM +kernel + extra innovation
???
Click to expand...
Click to collapse
Yes, all ROMs which are released are based on Android Open Source Project's (AOSP) source. Initially Google have to release the source (Latest is Android 4.2) and then manufactures like Samsung, HTC, Sony, LG etc. works on their own to provide the updated Android version to their phones skinned with their proprietory UI's or themes.
Android version exactly means changes in features added by Google itself, which are incorporated by Manufactures when they push updates to their phones.
ROM is actually the term used for your Operating System. Kernel is complete different subject related to ROMs, it works as the medium of communication between your hardware and the operating System thus involving drivers and CPU controls.
Could someone tell me what Liquidsmooth is based off of. I've read in someplaces that it says CM, while some say AOSP.
jcruz942 said:
Could someone tell me what Liquidsmooth is based off of. I've read in someplaces that it says CM, while some say AOSP.
Click to expand...
Click to collapse
It is based on AOSP as mentioned here on their website, "LiquidSmooth is an aftermarket firmware based on the Android Open Source Project.
Dedicated to providing users with smooth, stable and fast ROMs. A Lightweight modified AOSP base, and then add the features you crave." AOSP is used as the base and then many CM features (Theme Chooser, etc.) are added in as well.