Weekly Edition
Return to the Development pageRecent Features
| |||||||||||||
The Android source is back online
The Android source repository has been offline since the kernel.org
compromise; it has now returned
on a new site. Services like Gerritt will take a little longer still.
"To reiterate, these servers contain only the 'gingerbread' and
'master' branches from the old AOSP servers. We plan to release the source
for the recently-announced Ice Cream Sandwich soon, once it's available on
devices."
(Log in to post comments)
Old Android source Posted Oct 20, 2011 8:39 UTC (Thu) by coriordan (guest, #7544) [Link]
Just to clarify, only the source for *old* versions of Android has been (re)published. Not the source for the current version.
(I was confused when I saw this story title, and at the same time a Slashdot story "Android Source Code Gone For Good?")
Old Android source Posted Oct 20, 2011 14:08 UTC (Thu) by mikachu (guest, #5333) [Link]
At least one of the subrepositories had a 3.2r1 tag, saw it scroll by while repo syncing earlier. Presumably one of the GPLed projects.
Old Android source Posted Oct 20, 2011 15:32 UTC (Thu) by ajross (subscriber, #4563) [Link]
Seems like you're exactly right. Chromium might be an exception,
though maybe it has some GPL subcomponents.
$ for i in $(find . -name .git); do (cd $i && git tag | fgrep -q android-3 && echo $i); done
Old Android source Posted Oct 20, 2011 14:33 UTC (Thu) by rfunk (subscriber, #4054) [Link]
Yes, it's a little confusing, but calling it "not current" isn't exactly right either. It really depends on what you consider current.
2.3.7 (on the site) is the latest phone version that's been released on any devices (and actually newer than most of what's out there now). 3.0 is tablet-only, and was never going to be released as source. 4.0 has been demoed, but nothing running it has been released yet. Supposedly 4.0 source will be released sometime after the first device is out.
better than nothing Posted Oct 20, 2011 18:04 UTC (Thu) by b7j0c (subscriber, #27559) [Link]
it would be nice if this was less of a cathedral...but for the time being i don't see any alternatives.
The Android source is back online Posted Oct 20, 2011 21:19 UTC (Thu) by jmorris42 (subscriber, #2203) [Link]
But does it actually build? I just pulled 2.3.7_r1 and am trying to build it on F15 and not having any luck. I have pulled in every 32bit lib and -dev package I can find any reference to and it just won't go. Anyone else having problems?
Fairly quickly dies with:
frameworks/base/libs/utils/RefBase.cpp:507:67: error: passing const android::RefBase::weakref_impl as this argument of void android::RefBase::weakref_impl::trackMe(bool, bool) discards qualifiers [-fpermissive]
The Android source is back online Posted Oct 21, 2011 1:39 UTC (Fri) by cuviper (subscriber, #56273) [Link]
Hey, I fixed that! :) But my commit only went into master. :(
Try in frameworks/base/: git cherry-pick c4fbbe06
The Android source is back online Posted Oct 21, 2011 17:32 UTC (Fri) by jmorris42 (subscriber, #2203) [Link]
Yup, that did it. Thanks. I have the emulator running with the browser open. So it looks like the repo is complete.
Now on to my mad goal of trying to port 2.3 to my Blu Tango that shipped with 2.2 and isn't likely to ever see an update from the vendor. Got it new for $70 off eBay to start learning about Android so I ain't exactly complaining, it is a project! And it is certainly smaller and lighter than the Handspring Visor it is replacing. Downside is daily recharging instead a monthly battery change.
Blu Tango Posted Oct 22, 2011 20:45 UTC (Sat) by tialaramex (subscriber, #21167) [Link]
Although getting it working on the Blu Tango specifically is very much your problem, the CyanogenMod project's source (on github) may offer some inspiration for how to bodge things where the vanilla Android source doesn't cope with some odd thing a vendor has done on a specific phone.
The other thing you probably want is Blu Tango kernel source. There's almost certain to be some hardware in there that doesn't have mainline drivers, and no doubt the patches to make it work will be grotesque, but you want them anyway. In theory the device should have come with instructions for how to get your source, in practice it may involve plaintive phone calls or even lawyer letters.
Blu Tango Posted Oct 26, 2011 0:28 UTC (Wed) by jmorris42 (subscriber, #2203) [Link]
Yea, already put in an email request for kernel source. Might have to skip Blu and go straight to Compal since they are the people who actually make the hardware. Difference is Blu has a Florida point of presence, making an enforcement action on them a lot more plausible than going after a huge faceless Chinese ODM.
Doesn't look like the bootloader left in fastboot support either so that will make testing a lot less simple. The kernel version number reported is between the version that stock 2.2 and 2.3 ships. No way to know what is actually in it though without sources. It claims 2.6.32.9-perf in /proc/version and the release notes for 2.3 say it uses 2.6.35 so I'd probably be missing something important if I tried just replacing userland and keeping the same kernel.
Odd thing is the Android source seems to only include a binary blob for a kernel image so I can't just compare the stock kernels to see what Google added. Google wouldn't be able to get away with that sort of GPL violation so I'm sure I'll find their source in a separate archive as I dig around though, I'm still looking around the Android universe and learning.
As for Cyanogen Mod, oh yes I'd love to get there as an endpoint but as a start I'd like to figure out how to get Clockwork Mod going. Just having that available would do wonders so that is where I'll probably begin.
Blu Tango Posted Oct 26, 2011 0:59 UTC (Wed) by cuviper (subscriber, #56273) [Link]
Yeah, I'm not exactly sure why Android doesn't build the kernel along with the rest. The kernel source was available on android.git.kernel.org under kernel/common.git, kernel/msm.git, etc. I can't find anything at those paths on the new server though, and they don't have gitweb up to browse yet.
You can see the kernels on CodeAurora though. They've patched beyond what Google provides, but it looks like the original sources are pushed under aosp/* branches.
Blu Tango Posted Oct 26, 2011 2:04 UTC (Wed) by dlang (✭ supporter ✭, #313) [Link]
they are setting up a new repo for android
http://groups.google.com/group/android-building/msg/c73c1...
the load for android was a strain on kernel.org so google is setting up a new set of servers to handle it.
Blu Tango Posted Oct 26, 2011 2:17 UTC (Wed) by cuviper (subscriber, #56273) [Link]
Yes, I know, that's the whole point of the parent LWN article. But while all the Android userspace is on the new android.googlesource.com server, I can't find their kernel trees there.
The Android source is back online Posted Oct 21, 2011 8:47 UTC (Fri) by mikachu (guest, #5333) [Link]
The whole tree builds a working emulator that starts up and boots something that looks like a phone here.
|
|||||||||||||