ICS 4.0.1 Source Code out! - Captivate Android Development

Yay!!! That was unexpected!
Original Post
Setting up the source tree
From Jean-Baptiste Queru-
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 istory of the Android source code tree, which naturally includes all the source code for the Honeycomb releases. However, since Honeycomb as a little incomplete, we want everyone to focus on Ice Cream Sandwich. So, we haven't created any tags that correspond to the oneycomb releases (even though the changes are present in the history.) JBQ, on behalf of the AOSP team.

Sweet I'm gitting it right now

that means get to work devs!

Freaken awesome! Thanks.....
Sent from my SAMSUNG-SGH-I897 using xda premium

YESSSS
o...m...g. so the rumors were true....i'm excited and i just can't hide it

Great news for all the talented developers especially on the Captivate side of things...have fun guys!
Sent from my SAMSUNG-SGH-I897 using XDA App

Wow. This is fantastic. Hope devs could put this to good use. Wish I could help... But I don't know enough about developing (yet!)

I wonder if old captivate devs would come back to do one final update on their roms?
*cough* watsa *cough*
>_> <_<

+9999999999999990000000000000000000
That would be awesome

Wow talk about unexpected and exciting news! If only I knew how to build a working ROM from this...

Time to get cookin'!
Sent from my SAMSUNG-SGH-I897 using XDA App

This is awesome, but does this not mean we also have to wait for samsung to come out with the drivers and associated stuff to actually use this on our devices?
I thought something like this happened with Gingerbread also in the past.

I'm downloading it now, and we could make a port from the Nexus S, which is very similar to the Captivate!
Sent from my SAMSUNG-SGH-I897 using xda premium

I dont have time to try this right now, but someone could try following this guide:
http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Compile_CyanogenMod_(Linux)
And in the line that says:
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
Change it to:
repo init -u git://github.com/CyanogenMod/android.git -b ics
And just see what happens, I checked on Github and the CM team has already created an ics branch

loganmc10 said:
I dont have time to try this right now, but someone could try following this guide:
http://wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Compile_CyanogenMod_(Linux)
And in the line that says:
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
Change it to:
repo init -u git://github.com/CyanogenMod/android.git -b ics
And just see what happens, I checked on Github and the CM team has already created an ics branch
Click to expand...
Click to collapse
But we don't know if they have it built yet! Wait a whole and yet compiling later, It took me 5 minutes to add repositories and start repo for ICS AMD it is downloading NOW!
Sent from my SAMSUNG-SGH-I897 using xda premium

b-eock said:
we could make a port from the Nexus S, which is very similar to the Captivate!
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
The nexus s code isn't in this release yet, just the galaxy nexus.

But the devs are gonna port from the Galaxy Nexus to the Nexus S, which our devs will take over and work their magic, I will take a hit at it to!
Sent from my SAMSUNG-SGH-I897 using xda premium

b-eock said:
But the devs are gonna port from the Galaxy Nexus to the Nexus S, which our devs will take over and work their magic, I will take a hit at it to!
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Really? I think they would just be better off waiting a few days for the official nexus s code.
IMO there's no reason to do a hacky/dodgy job if you can be patient and wait for the inevitable official build config.

good stuff! im gonna take a look at this in just a sec

mystichobo said:
Really? I think they would just be better off waiting a few days for the official nexus s code.
IMO there's no reason to do a hacky/dodgy job if you can be patient and wait for the inevitable official build config.
Click to expand...
Click to collapse
lets be honest, no one wants to wait, I can't even wait to flash the new nightly every day

Related

Android 2.3 aosp source code

http://developer.android.com/sdk/android-2.3.html
I believe this is it.
Sent from my GT-I9000 using XDA App
**** YES! Let's hope for a port today.
This is the aosp source code I believe. Not the same as a couple of days ago.
Sent from my GT-I9000 using XDA App
Meaning, there is no reason to port this instead of Nexus S. The Nexus S Gingerbread is very similar to the Galaxy S already so easier port, and is probably newer. Still nice for devs tho
also I see that SDK doesn't include Market
You can get the market from the Gapps zip.
yes, you can, but there's still no reason to port this over Nexus S, though it is fun to play with
TheNikkoMan said:
yes, you can, but there's still no reason to port this over Nexus S, though it is fun to play with
Click to expand...
Click to collapse
It isn't easier without the source code
This isn't the source code either. Its just a generic build of Gingerbread. A system.img containing it.
TheNikkoMan said:
This isn't the source code either. Its just a generic build of Gingerbread. A system.img containing it.
Click to expand...
Click to collapse
Correct.. The topic sounded like it was the source...
yet another bogus topic.... moving it off DEV
since it's in the WRONG! section
http://source.android.com/source/download.html
I believe this may be it if the other link is wrong... found it in the Evo 4G forum xD
It's just a link specifying how to set up a build environment and so on. The source isn't out, it's being pushed atm so give up already
Anyone who has a plan to port go on #nsdev on freenode.

[INQ] KERNEL/BLN for Froyo

Not sure if the kernel source has even been made available to the awesome devs we have while I was considering/searching for BNL for froyo.
Has the kernel been made available and if so has anyone looked at what it would take to implement BLN?
If not, whatever, I can wait a little longer.... and if Samsung has their way.... 2 years till my contract ends.
~T1
The source likely won't be released until the update is official and pushed out
Sent from my SCH-I500 using XDA App
There is a post in dev section about kernel source being built for the fascinate from the i9000 source. It is alpha at the moment.
I don't see an official source being released until months after the OTA.
I did see that the i9000 alpha was release yesterday or the day before. While I don't understand all of what was said the basic principle is that there are problems with the video drivers and/or modules.
Worth a shot to ask though since I am not sure if BLN is baked in or is a loadable module?
Sent from my SCH-I500 using XDA App
Terror_1 said:
I don't see an official source being released until months after the OTA.
I did see that the i9000 alpha was release yesterday or the day before. While I don't understand all of what was said the basic principle is that there are problems with the video drivers and/or modules.
Worth a shot to ask though since I am not sure if BLN is baked in or is a loadable module?
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
It is baked into the kernel drivers for the touchkeys. Until SirGatez/birdman/someone get the i9000 source working, there can't really be any modifications done that require modifications to kernel source. The only other option would be Samsung releasing the source that we need, but that is likely not going to happen first, and will probably be about a month or so after the release of Froyo is official.
Well I guess that answers that. Certainly wish them the best of luck within the i9000 source. Now off to hate/bash the samsung representative fellow lurking around.
Sent from my SCH-I500 using XDA App

CM8 Ice cream sandwich

Since the fascinate has been merged with cyanogenmod mainline, does this mean it will be supported when AOSP ice cream sandwich source code gets released? Or does Jt need to dev the whole phone over again for CM8?
I would go ahead and say Cyanogen should take over totally now. Because like he said it will probably be the last update he does. If they have everything working that should give them a template to work from for 4.0. Just a guess though.
He's still working on cm7 along side the cm team , and they compile and host the files
0|-| |\|035, 7|-|3 L337 |-|4><0R5
p\/\/|\|3D /\/\'/ 700|\|
Sent from XDA Premium App
hesh.monster said:
He's still working on cm7 along side the cm team , and they compile and host the files
0|-| |\|035, 7|-|3 L337 |-|4><0R5
p\/\/|\|3D /\/\'/ 700|\|
Sent from XDA Premium App
Click to expand...
Click to collapse
Still anxiously waiting for fascinatemtd to appear on their website!
Sent from my I500 using XDA Premium App
Someone will have to the necessary porting. Ice Cream Sandwich will more than likely contain a much newer version of the Linux kernel, so at the very least, the Fascinate specific drivers will have to be ported to work with the newer internal API.
People on the CM team might be able to do a lot of the porting themselves, but, they will need people specifically with the Fascinate for actually testing out the code (which they may or may not have).
Headcase8911 said:
Still anxiously waiting for fascinatemtd to appear on their website!
Sent from my I500 using XDA Premium App
Click to expand...
Click to collapse
Might be soon, might be months. Those guys are hella busy over there, so they'll get to it when they get to it. My old Eris has had "official" CM7 since last year and it's still not on the CM wiki. Lol.
sarkozy said:
Might be soon, might be months. Those guys are hella busy over there, so they'll get to it when they get to it. My old Eris has had "official" CM7 since last year and it's still not on the CM wiki. Lol.
Click to expand...
Click to collapse
Ouch
Sent from my I500 using XDA Premium App
Jt will still have to maintain it for the fascinate, he just meant that it'll be the last compiled and distributed build of CM7 by him. Since the build bots and downloads.cyanogenmod.com take care of those two.
Sent from my SCH-I500 using XDA App

A500 roms?

what is going on with the custom roms on this forum? seems like there is no real action? the custom roms that are available are very buggy and no updates.... anyone know? did most of the developers leave? I know mdeejay from virtuous and he's awesome, wth happen that caused him to leave?
Nothing happened, that's the problem. When Acer releases their 3.2 update then you should see some action. I am betting no dev wants to work on a "test" build and would rather build off the official Acer update coming in a few days (or it better).
I think the lack of development has more to do with not having source code. At this point all the roms are just slimmed down hacked/ports of the original release. If source is ever released then we will see some serious action,
Sent from my A500 using XDA Premium App
Yes, I expect Acer will release source with the update as most manufacturers do. No reason to keep the source private.
Sent from my HTC Vision using XDA App
Acer can release kernel source any time but google isn't releasing HC source. Wait for ice cream sandwich. That release will include source code.
Sent from my Inspire 4G using Tapatalk

Jellybean source being release today.

http://rootzwiki.com/news/_/article...-jelly-bean-source-is-now-being-released-r955
http://www.androidpolice.com/2012/07/09/android-4-1-jelly-bean-released-to-aosp-right-now/
Damn it you beat me to the punch lol
Sent from my SGH-I747M using Tapatalk 2
CM10 soon!!!!!!
Sent from my SGH-T999 using xda premium
hopefully we get CM9 support first
lets see how fast we see something for s3
MMontanez347 said:
hopefully we get CM9 support first
Click to expand...
Click to collapse
Why would they make CM9 for this phone when JB source is released? Lol that makes absolutely no sense.
Sent from my SGH-T999 using xda premium
Serious_Beans said:
Why would they make CM9 for this phone when JB source is released? Lol that makes absolutely no sense.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I believe it was said that jb code is very similar to ics. Cm9 is very close for us. A stable cm9 to cm10 would probably be faster than cm10 built from scratch. Just a guess though, I'm not a dev.
Sent from my GS3
Restola said:
I believe it was said that jb code is very similar to ics. Cm9 is very close for us. A stable cm9 to cm10 would probably be faster than cm10 built from scratch. Just a guess though, I'm not a dev.
Sent from my GS3
Click to expand...
Click to collapse
Nah I mean working off of CM9 would make sense if they could just merge the changes but I doubt it would officially be released just for them to release CM10 after that.
Sent from my SGH-T999 using xda premium
MMontanez347 said:
hopefully we get CM9 support first
Click to expand...
Click to collapse
I really hope we get CM7 before that
/sarcasm
really? why would you want the outdated one?
The CM team is merging the update as we speak. I think we will probably just get CM10 and not CM9 first (could be wrong though)
Sent from my SPH-L710 using xda app-developers app
We will get CM10 before CM9. All development on CM9 is being ceased after version 1.0.0. Just be patient, the source was uploaded something like 2 or 3 hours ago.
I think we will have something by next week
razorseal said:
I think we will have something by next week
Click to expand...
Click to collapse
I think we'll have something by tomorrow morning.. ;-)
Joking aside, this is cool to see.
Sent from my SPH-L710 using xda premium
jsmcmahon89 said:
I think we'll have something by tomorrow morning.. ;-)
Joking aside, this is cool to see.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Joke? don't underestimate the developers on THIS phone, of all phones ) I'm gonna definatelly keep an eye on these forums. if nothing else i expect someone starting a WIP thread, an AOSP built rom, most likely not fully functional ofcourse, but compiled enough to boot up, just to give us a taste while development begins in earnest
This is just what was needed to jump-start development for the SIII
I'm curious, with Verizon's S3 flashing abilities currently being limited to roms stripped of kernels, how will this affect a jellybean rom? Is the ics kernel the same as the jb kernel?
Just rambling here, no disrespect intended and none meant at all just want to learn as much as possible....ICS source has been available the whole time, why wouldn't we have seen a CM9 build if it were that simple (as to have source)? Just cause source for 4.1 is out, it is going to make it that much easier to build an AOSP rom now? Again just trying to learn I know people are pretty snappy at questions like these, lol.
Sent from my LG-P999 using xda premium
mt3g said:
Just rambling here, no disrespect intended and none meant at all just want to learn as much as possible....ICS source has been available the whole time, why wouldn't we have seen a CM9 build if it were that simple (as to have source)? Just cause source for 4.1 is out, it is going to make it that much easier to build an AOSP rom now? Again just trying to learn I know people are pretty snappy at questions like these, lol.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Reason people are saying that we could see CM10 soon is because the CM team think the code should be able to merge right into what they have with CM9, and not break that many things. With CM7 to CM9, they had to basically do everything from the ground up again because ICS was such a huge update over GB. Now JB isn't that big of an upgrade over ICS, in a way it is, but in a way it isn't. Sorry if that sounds confusing.
bigant262 said:
Reason people are saying that we could see CM10 soon is because the CM team think the code should be able to merge right into what they have with CM9, and not break that many things. With CM7 to CM9, they had to basically do everything from the ground up again because ICS was such a huge update over GB. Now JB isn't that big of an upgrade over ICS, in a way it is, but in a way it isn't. Sorry if that sounds confusing.
Click to expand...
Click to collapse
That's easy to understand, and not what I'm asking... what you are saying is its easy to incorporate 4.1 to 4.0, just like it was easy to go to 2.2 to 2.3... I'm asking why is everyone so excited to get 4.1 AOSP, when we don't even have 4.0 AOSP?
Sent from my LG-P999 using xda premium
mt3g said:
Just rambling here, no disrespect intended and none meant at all just want to learn as much as possible....ICS source has been available the whole time, why wouldn't we have seen a CM9 build if it were that simple (as to have source)? Just cause source for 4.1 is out, it is going to make it that much easier to build an AOSP rom now? Again just trying to learn I know people are pretty snappy at questions like these, lol.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I am no dev, but heres how i understand it works;
we start with an announcement of an OS, this is done generally at Google I/O or a Nexus Event, in this case was Google I/O.
On the announcement day, devs receive the SDK; Software Development Kit.
This is released to allow the devs to begin making apps that match and run on the new OS. However, aspiring rom devs then begin to build a rom off the released SDK, generally called an sdk port.
These tend to be made simply to give us an idea of how the system would work and function, and generally might boot up and have a couple working things, but major things tend not to function because the SDK is not made for that.
Then comes the Source code, this is the real deal, it is full code of the system, code that can then be compiled to produce a fully working system, or nearly fully working. Only thing that remains missing is proprietary drivers and such, these tend to be the things specific to each phone, files that would make particular chips work, particular functions, the specific phone kernel, etc. but once you have the source code, you're over 80% done as far as having the resources needed to develop a full rom. at this stage, some devs can produce a fully working, stellar rom, but it will take quite a bit more work than devs who choose to wait for the final stage
Then comes the OTA. this is where all the device-specific stuff comes to the devices, and devs have the absolute and complete freedom to produce a fully working, better than stock, experience. This is where roms flood the dev forums.
So as far as not having AOSP yet, and now this is our chance at AOSP? No, thats not why we dont have AOSP. we dont have it cause no one built it yet; the Touchwiz UX is sooo integrated in the system that untangling and taking it all out is a long and drawn out process, and theyd need to deconstruct what we currently have, take out elements of touchwiz until its all clean, all the while making sure it doesnt break anything else.
but getting the jellybean source code propels devs because now this is a new OS, a new AOSP with its own new interesting properties. and because Jelly bean is a small update compared to ICS, now that we have source code, many of the device specific stuff wont be broken by implementing jellybean code into it, therefore building a Jellybean rom is a faster path to AOSP than untangling the current ICS for Galaxy S III
Does that make sense?
mt3g said:
That's easy to understand, and not what I'm asking... what you are saying is its easy to incorporate 4.1 to 4.0, just like it was easy to go to 2.2 to 2.3... I'm asking why is everyone so excited to get 4.1 AOSP, when we don't even have 4.0 AOSP?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
AOSP in this case is talking about the actual Android Open Source Project. so it is a bunch of code. so why are we excited? we've had ICS AOSP code for nearly a year now, what we dont have is AOSP roms. building an ICS AOSP rom is much harder than building a JB Rom, and we currently have icecream sandwich on the SIII even if its touchwized, and undoing touchwiz is quite a bit of work. but Jellybean...Oh Jellybean, now we got the source, we will start getting that baby soon and it'll boost dev on these devices. make sense?
mt3g said:
That's easy to understand, and not what I'm asking... what you are saying is its easy to incorporate 4.1 to 4.0, just like it was easy to go to 2.2 to 2.3... I'm asking why is everyone so excited to get 4.1 AOSP, when we don't even have 4.0 AOSP?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Not sure if you were trying to come off rude or not, but people are excited because its the newest update, duh. Reason being we don't have 4.0 AOSP is because the phone hasn't been out that long for the US carriers.

Categories

Resources