Related
Hi All,
Below a message from google about releasing ICS Time to DEV !
Greatings
Antonius
https://groups.google.com/group/android-building/msg/c0e01b4619a1455a
Hi! We just released a bit of code we thought this group might be interested in.
Over at our Android Open-Source Project git servers, the source code
for Android version 4.0 (Ice Cream Sandwich) is now available.
Here's how to get it:Follow the instructions at
http://source.android.com/source/downloading.html
Check out the
'ics-release' branch:repo init -u
https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That's it! However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus. Build configurations for other devices will come
later.
Unfortunately we still don't have our Gerrit code review servers back
online. That remains our top priority though, and we hope to have them
back soon.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
JBQ, on behalf of the AOSP team.
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Yessssssss
now let the games begin!!
Good news! Hopefully the devs can do something magic!
What does this actually mean for us DHD users? is it simply a matter of putting 2 and 2 together, and bam we have a rom? or will it take a few weeks, and be extremely difficult because I notice everyone saying this is only for the Galaxy Nexus, so it is pretty much like porting I guess?
Repsys7 said:
What does this actually mean for us DHD users? is it simply a matter of putting 2 and 2 together, and bam we have a rom? or will it take a few weeks, and be extremely difficult because I notice everyone saying this is only for the Galaxy Nexus, so it is pretty much like porting I guess?
Click to expand...
Click to collapse
It will be very easy
Thanks for letting the devs know
Sent from my Desire HD using XDA App
@Antonius
Really? I hardly believe that.
Having the source code is very important, not everything. Release source code is for Galaxy Nexus, a different device. We need a working kernel and support for our hardware. Real devs are probably working on that now. The real work begins from here, and I hardly believe we will have something functional until CM9 starts having night builds... 1-2 months from now
Maybe we get the first nightly as a christmas gift.
alienmind said:
@Antonius
Really? I hardly believe that.
Having the source code is very important, not everything. Release source code is for Galaxy Nexus, a different device. We need a working kernel and support for our hardware. Real devs are probably working on that now. The real work begins from here, and I hardly believe we will have something functional until CM9 starts having night builds... 1-2 months from now
Click to expand...
Click to collapse
I think you need to read the post again this is the Source code it is a build up for gingerbread as i saw the code this night it was released the drivers and support are gonna be build very easaly but still it can take up to 1 a 2 weeks before release (Altrough i think some devs will release today for other devs to work on it) Also we need to keep in mind that there will be bugs in the system (Its still a child )
Greatings
Antonius
Multiple threads already on this. One is enough for development section. Moving to General
hahaha :-D at last.............waiting 4 it
In the words of many a drunk person at music festivals across the country
"HERE WE, HERE WE F*CKING GO"
Antonius123 said:
I think you need to read the post again this is the Source code it is a build up for gingerbread as i saw the code this night it was released the drivers and support are gonna be build very easaly but still it can take up to 1 a 2 weeks before release (Altrough i think some devs will release today for other devs to work on it) Also we need to keep in mind that there will be bugs in the system (Its still a child )
Greatings
Antonius
Click to expand...
Click to collapse
I think you need to read a bit harder
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus
Click to expand...
Click to collapse
This still needs porting, new kernel building, etc. I think a couple of months for alpha/nightly builds for DHD sounds about right.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
I hope as soon as possibile!
You where mistaken my friend: http://forum.xda-developers.com/showthread.php?t=1343361
check this thread!
hopscotchjunkie said:
I think you need to read a bit harder
This still needs porting, new kernel building, etc. I think a couple of months for alpha/nightly builds for DHD sounds about right.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Click to expand...
Click to collapse
Being a photographer is not conducive to having ICS beta builds without camera... and i'm a flashaholic! What am I to flash?!
Since it's been open sourced, any chance of porting it to the Galaxy Nexus? FirefoxOS also has been ported, so I would think WebOS would be possible. Any info on that? Would love to experiment with WebOS if it can be ported.
Parts of webOS have been open sourced, however the full open webOS 1.0 is not slated to be released until September.
Until then, no dice. Also depends highly on variant and availability of open source drivers.
Sent from my Galaxy Nexus using Tapatalk 2
jthatch said:
Parts of webOS have been open sourced, however the full open webOS 1.0 is not slated to be released until September.
Until then, no dice. Also depends highly on variant and availability of open source drivers.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ahh one of the people somewhere else in this forum said it had been fully open sourced. Not yet I guess. Also, aren't all the drivers for the gnex in the AOSP repo? So that shouldn't be a problem
Sent from my Galaxy Nexus
AshtonTS said:
Ahh one of the people somewhere else in this forum said it had been fully open sourced. Not yet I guess. Also, aren't all the drivers for the gnex in the AOSP repo? So that shouldn't be a problem
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
All GSM models and VZW yes, Sprint not yet. Those available should work as open webOS will use the standard linux kernel. However it is my understanding, and I could be wrong, that some models, namely the CDMA ones still use proprietary binaries with permission to distribute for AOSP. Not that they couldn't potentially be used for a port, just that it is a bit more of a grey area.
jthatch said:
All GSM models and VZW yes, Sprint not yet. Those available should work as open webOS will use the standard linux kernel. However it is my understanding, and I could be wrong, that some models, namely the CDMA ones still use proprietary binaries with permission to distribute for AOSP. Not that they couldn't potentially be used for a port, just that it is a bit more of a grey area.
Click to expand...
Click to collapse
It's my understamding that the sprint one will NEVER be in the AOSP repository. Google said so I think. So I guess it would be harder for that one. I guess now I know it'll easily be possible for a WebOS port at least for the Maguro and Toro (which I have).. I wonder if someone will take up the cause, or I'll have to do it myself...
When will we see a aosp rom for our note 3
Tomorrow when the clock strikes 12. I promise
Sent from my magic spaceship
When people stop asking for ETA's.
sent from my sm-9005.
Yerv Melkonian said:
When will we see a aosp rom for our note 3
Click to expand...
Click to collapse
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!
d12unk13astard said:
When will we see people stop asking for aosp roms? Thats the real question, this phones barely a month old smh.
Sent from my note 2 ya bish!
Click to expand...
Click to collapse
We're just excited. Let us wag our tails and scratch at the door until our owner opens the door for us. So to speak. LOL!
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
I would love to see that
Sent from my SM-N900T
Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk
dragonstalker said:
Lol. There won't be an Aosp until the Google edition is released. Somebody has to recode removing all TW. Or Google release a base. The S4 port is in the works but taking time
Sent from my SM-N9005 using xda premium
Click to expand...
Click to collapse
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
You sir have just explained the reason I fell in love with android, aosp, the rooting community. A lot of people don't get and are unappreciative of the works of ROM devs. So much greed and selfishness I've seen on xda since after the g1 days. Its always *****ing and bickering and this and that and demanding. Thank you to all the devs out there. Without you guys, android will be a Disney Land that never opened its gates
Sent from my SM-N900T using xda app-developers app
pathtologos said:
Is there a Google edition or developer edition coming? Has that been confirmed anywhere? I too am really missing cm, aokp, pa, and especially pac man. Man, what I'd give for pac man on this beast! I REALLY hope we get some aosp love.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
+24
CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
Why would you quote me and say exactly what i said in a long drawn out explanation. I'm guessing you missed the punctuation in my response. I mean you said everything i said, down to how the CM is a work in progress. Sheesh.
CalcProgrammer1 said:
That's not entirely how it works. You don't remove TW, TW is closed source and there's nothing to base off of that you'd ever have to remove TW from. You have to rebuild the device specific stuff and base off AOSP source, aka the stuff Samsung hasn't touched at all. Samsung's already done that, but of course they don't release their source apart from the kernel (which they have to due to GPL). That's where CM and other devs come in, they recreate the device-specific makefiles and source code parts by hand that support the device on the larger stock AOSP codebase, then you include those device-specific parts in your manifest file and you now have a build target to build AOSP-based ROMs for the new device. CM already demonstrated that they have AOSP booting and thus the device-specific code partway there, but in the screenshot they posted it looked like modem wasn't working yet. Give it time.
I do wish they would just post their current code though, it's an open source project. The more people looking at it the faster it will get done, but for some reason they're awfully slow about releasing their WIP code.
Click to expand...
Click to collapse
DUDE I couldn't have said it better myself. You devs are wizards.
Hey all,
I was wondering, since the new Android L came out, how come no one is rushing to have it on our S3? Is there a version that exists already? And if not, who would like to work on this (maybe with me)?
Thank you in advance.
There is not a single device with Android L and the source code has not been released. There are two preview builds that are not final for the Nexus 5 and 7. You should check your facts with a few seconds of googling before starting a thread like this.
sigmarelax said:
There is not a single device with Android L and the source code has not been released. There are two preview builds that are not final for the Nexus 5 and 7. You should check your facts with a few seconds of googling before starting a thread like this.
Click to expand...
Click to collapse
Google has released the SDK of the final Android 5.0 (L). Why would someone not be able to take the image file from there and make a port?
Porting a ROM is not as easy as it sounds.
I had Android L on my Nexus 4 for a while and didn't like the interface. Even after many revisions, it still is not perfect on the Nexus 4.
audit13 said:
Porting a ROM is not as easy as it sounds.
I had Android L on my Nexus 4 for a while and didn't like the interface. Even after many revisions, it still is not perfect on the Nexus 4.
Click to expand...
Click to collapse
That's true, I agree. I read some guides here on XDA on how to port a ROM. I'd very much do it for my S3, but there are some things i am not sure about, like the kernels and the modems. Ill need to read up on it if I decide to do it myself.
scrat55 said:
Google has released the SDK of the final Android 5.0 (L). Why would someone not be able to take the image file from there and make a port?
Click to expand...
Click to collapse
The SDK is not an operating system. It is documentation on how to create apps that will run well and look nice on the operating system. The images for the nexus 5 and 7 could indeed be ported, but it would take a good chunk of time and be buggy (as interfacing with certain hardware probably would be broken). It would also make no sense to work on such a port project because Android L source code will likely be released in early November. Building Android L for the S3 from source code would be much more ideal, and will definitely be done once L's source code is released
sigmarelax said:
The SDK is not an operating system. It is documentation on how to create apps that will run well and look nice on the operating system. The images for the nexus 5 and 7 could indeed be ported, but it would take a good chunk of time and be buggy (as interfacing with certain hardware probably would be broken). It would also make no sense to work on such a port project because Android L source code will likely be released in early November. Building Android L for the S3 from source code would be much more ideal, and will definitely be done once L's source code is released
Click to expand...
Click to collapse
Ah roger that, thank you for a well explained reply mate.
Cheers!
Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
I got my 5x last Tuesday and forgot how little I like "pure" android. I think the usual progression is flash aosp then flash cyanogenmod once the nightlies start to stabilize. I know I'm in the minority but the nexus phones usually have too much Google on them for my taste. I like the hardware, but the software is another story.
At any rate, I'm also waiting for the binaries and device tree so that I can start building my own.
m4r0v3r said:
Waiting for the sources that is, what are porters planning on sticking on this? Personally I want the sources to attempt to port Sailfish, only reason I bough the phone. I currently have the Nexus 5 and the OS runs buttery smooth thanks to the porters over at #sailfishos-porters
Am even wondering did I make a mistake buying this device when the Nexus 5, is more than enough omph to power the OS. But I've got it and gotta try, to atleast expand my own knowledge base.
also do you guys know how chainfire managed to build the kernel for it without the sources?
Click to expand...
Click to collapse
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
sn0warmy said:
WTF?
The phone has been out for less than a month. Have some patience or start learning to develop yourself, rather than creating a useless thread, just to whine.
Click to expand...
Click to collapse
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
drsn0w said:
If you knew much about how android works, you'd know that chainfire didn't make a kernel. He took the boot image and modified some fstab, prop, and sepolicy stuff, repackaged it, and released it. He didn't build his own kernel.
In any case, I'm curious about this, how long does it usually take google to release their sources?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
m4r0v3r said:
oh yeah Ill just go and create a kernel, and while am at it, I may as well write my own drivers. Maybe I'll call my kernel linox, and adopt this policy of sharing my source code so other people could collaborate. Maybe using some sort of version control, call Hit or something, maybe on some website called HitHub.
Yeah that sounds like a good way to develop it...Or Google could hurry the **** up and release the sources and binaries so I wouldn't have to.
Well if you read my post you'd see I was curious about what people wanted to port.
Not make but people have been saying it was built with forceencrypt disabled so I thought he built the kernel with that flag, (ie he had the sources). But it seems thats not the place to change it
Click to expand...
Click to collapse
timjp692 said:
Wow the self-entitlement is real nowadays, patience bro. You cant have everything instantly when you want it.
Click to expand...
Click to collapse
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
m4r0v3r said:
what to expect an open source based phone to have the sources with it?
No I know I can't have everything when I instantly want it, but really what could be the reason for the delay. Since am already pretty pissed about the force encryption.
Click to expand...
Click to collapse
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Offer a bounty if you're that impatient.
sn0warmy said:
I'm sorry, but you sound like a whiney little 12 year old who is used to having everything they want RIGHT when they want it. Kind of sums up the turn this forum has taken over the past couple of years.
In the real world you'll learn that good things take time. The phrase, "patience is a virtue" holds true merit.
Click to expand...
Click to collapse
Apology accepted.
bblzd said:
Offer a bounty if you're that impatient.
Click to expand...
Click to collapse
For what exactly? Someone to break in Google servers and take the source code? lol
m4r0v3r said:
For what exactly? Someone to break in Google servers and take the source code? lol
Click to expand...
Click to collapse
I'm waiting too- it's not like google is still working on the binary drivers and just building the production rom with hacked up device trees until they get the real ones. I could be mis-remembering, but in the past, I thought the factory roms and binary drivers were available the day the devices were released.
I can certainly understand being patient with devs who are working on roms (for free/beer/donations), but google is done with the rom and has already released it to production. The factory image for the 6p was delayed as well. It's not a secret- they are going to push it to every one who bought a phone. My conspiracy theory is that google is trying to bury aosp, and merging android and chrome will be another stab into the heart of both privacy and freedom.
and its outtt
m4r0v3r said:
and its outtt
Click to expand...
Click to collapse
Waiting for some real nexus thing then