Hey everyone,
I have my dev environment setup on my Linux machine, and am interested in starting an AOSP build of 4.0.4 (remove touchwiz and keep it stock), and have been following the guides for building from source, but I am stuck.
-setup dev environment
-downloaded source
-ensured I have all packages
where do I go from here?
In http://xda-university.com/as-a-developer/getting-started-building-android-from-source it tells me to setup a device target. I have pulled down the Samsung source files from their open source site. Where do I deposit these? Just a bit confused on how to keep rolling on this.
Thanks,
Bluefalcon13
Related
Where should i start first to learn how to code for android, make roms and compile the android tree?
or just a good place to start?
From what starting point?
Building android to make custom builds involves knowing lots of things; java, c, linux, gcc build system, android platform, etc, etc.
To make apps you just need to know java and the android platform.
Start here: http://developer.android.com/
Code for Home screen Pull up Menu
I have a similar request but was unsure if I should start a new thread, If this needs to be moved my apologies (I also searched through Q&A forums as well and came up empty ). Where or how could I get the source code for the Home Screen pull up menu? I checked out the Google Source Code but it requires Linux or Mac OS and I run Windows Vista.
cingall said:
I have a similar request but was unsure if I should start a new thread, If this needs to be moved my apologies (I also searched through Q&A forums as well and came up empty ). Where or how could I get the source code for the Home Screen pull up menu? I checked out the Google Source Code but it requires Linux or Mac OS and I run Windows Vista.
Click to expand...
Click to collapse
i don't think you can compile the source code in windows
david1171 said:
i don't think you can compile the source code in windows
Click to expand...
Click to collapse
Yeah, I'm considering running Linux on my laptop alongside Vista, as I have hit dead-ends on a couple projects simply because you need Linux for different things . All I really need is a place that I could find the source; I had an idea that I proposed to mohsinkhan47 for his Vista theme and he asked me to find the code for the pullup menu. It would be much appreciated if anyone could guide me in the right direction.
i know where you can get the entire source code. grab it from here
Thanks for the link, that was the site that I went too before but says I need either Linux or Mac OS. Still scouring the android sites but coming up with nothing .
Yeah I do not think there is a way to compile the source in windows. I guess like stericson once said "you're going to have to get your hands dirty and use linux" (it was something like that.
Guess I gotta break my cherry sometime, thanks all for the advice.
http://groups.google.com/group/android-building/msg/c0e01b4619a1455a?pli=1
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.htmlCheck 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.)
Click to expand...
Click to collapse
http://source.android.com/source/downloading.html
groups for linaro source
current groups for aosp source
a miscellaneous reference
Would anyone have thoughts to add addtional group tags to the default manifest?
The default.xml could be organized and commented to break up
core (bare metal aosp)
omni (omnirom specific)
build (toolchain and things for compiling)
developer tools (I personally think things like eclipse and adt are fluff even for downloading since I'm probably downloading these types of things independently)
chipset (arm, x86, mips)
device (grouper, mako, etc)
host (ex: windows, mac, linux)
I could then repo init with
repo init -u https://github.com/omnirom/android.git -b android-4.3 -g core,omni,build,arm,linux,mako
and pull down 4 GB instead of 10 GB
original announcement from JBQ
AOSP is big, and downloading and storing all of it consumes a fair
amount of bandwidth and space.
We've been investigating ways to make it smaller. One visible part of
that work is that the master tree is "only" 6.5GB, while Jelly Bean is
about 8.5GB.
We're aiming to go further. Today, I'm deploying an experiment that
can help shrink things.
Repo recently added a feature called "manifest groups" that allows to
restrict the list of projects being downloaded.
I've set up the manifest for the AOSP master branch to include a few
groups. Here are the groups I added:
"device": files that are specific to flagship devices but aren't
necessary to build a generic platform.
"darwin": files that are only necessary when building on a darwin host
(i.e. MacOS).
"linux": files that are only necessary when building on a linux host.
"arm": files that are only necessary when building for ARM targets.
"mips": files that are only necessary when building for MIPS targets.
"x86": files that are only necessary when building for IA targets.
Here's an example, which allows to build the ARM emulator on a linux
host. In this case, the download is 3.6GB, which is a significant
improvement over a full tree:
repo init -u [URI] -g default,-darwin,-device,-x86,-mips
The syntax is hopefully self-explanatory. Note that this is only
currently supported in the master branch.
I'm looking at the possible evolutions:
-marking the projects for individual device families (i.e. crespo,
tuna, stingray, panda), so that it's possible to download the files
for one specific device without getting them all.
-marking the projects that are necessary to work on the developer tools.
-marking the projects that are necessary to work on CTS.
There's also a possibility that repo will eventually know to
automatically ignore host-specific projects.
Longer-term, we're investigating the possibility of not downloading
the entire source history for projects where it's both large and
unnecessary.
I'm open to feedback and suggestions. Please let me know whether
that's useful, whether that works, which of the future directions
would be useful... and which future features I've forgotten that'd
make life easier.
Thanks,
JBQ
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Click to expand...
Click to collapse
That would be wonderful, especially for people with bad connections or small SSDs. :good:
I'm going to experiment with the current groups and see if they yield a reasonable savings. It may just be a matter of a how-to on the wiki.
would be awesome for me
update:
Code:
repo init -u https://github.com/omnirom/android.git -b android-4.3 -g default,-darwin,-device,-x86,-mips
gave me a .repo folder of 6.1GB and build works fine
what's the size without those -g switches?
i did the same with AOKP recently
if you want to have a look
http://gerrit.aokp.co/12009
http://gerrit.aokp.co/12146
http://gerrit.aokp.co/12156
http://gerrit.aokp.co/12642
http://gerrit.aokp.co/12749
I am trying to make my own build of Lineage OS so that I can learn more about howto enable I2C devices so that they are available in SensorManager.
I browsed through the repos at https://github.com/lineage-rpi but could not find instructions on how to perform a build from scratch.
The repo looks like it is the right place to go and it seems like android_local_manifest/manifest_bcrm_rpi.xml has all the right links to the other repos (kernel source, proprietary and android_device). However I do not see any reference to the android source code. Or do I need to get the android source code from source.android.com?
Can someone share the "repo" commands so that I can pull all of the source code? I will work out howto build it form there.
Hi, guys.
Android Studio newbie here. I'm a loooong time Linux user/ sys admin, but have just downloaded Android Studio. My motivation for doing so, was to give an existing (neglected) open source app a once over, ideally with a Linter, some code quality checking and maybe refactoring. Essentially, bringing it up to current Android standards. I've installed AS on my Linux Mint box, and have added the GitHub repository. I can see the code, and lint options in the menus, but don't know where to start. Does anyone know of a flowchart, or process I could follow?
Many thanks,
Chris