Hi,
Is there any way to pull just one specific device's proprietaries from The Muppets repository rather than every device from a specific vendor ?
Seems a terrible waste of bandwith and storage to pull them all instead of just the one required.
Any and all help offered will be much appreciated thank you in advance.
Search terms were:
Code:
git download folder from repository
https://stackoverflow.com/questions/7106012/download-a-single-folder-or-directory-from-a-github-repo
https://github.community/t5/How-to-...-a-specific-folder-from-a-GitHub-repo/td-p/88
Related
I'm having a problem compiling a kernel for a
Sprint CDMA 7" GT.
I use unpack-initramfs to grab the rootfs from
the original EF17 kernel.
I put that dir location in CONFIG_INITRAMFS_SOURCE=""
in the p1_defconfig file in Kernel/arch/arm/configs
In the kernel directory I issue the commands:
make clean
make p1_defconfig
make
The kernel compiles fine, but there's a 3Mb
difference between the original EF17 kernel
and the one I compile.
If I extract the rootfs from my kernel it's
the exact same as the one extracted from the
original. Have I missed a step? I've done this in the past for my Epic 4G.
i have similar issues that i've been battling with..the kernel coming out smaller isn't 100% indicative of a bad compile...i bet your kernel will boot but 3g (and possibly sound and more) don't work
i emailed samsung open source explaining what i did to compile and this was their response.
my query:
I downloaded the source code for the SPH-P100. I followed the directions in the README_kernel.txt to compile. As well as setting up the unmodified initramfs from the stock kernel. I can boot the kernel on the device however the resulting zImage size is 4.2MB compared to the 5.7MB zImage pulled from the device. I've not made any extra changes to the config or anything else other than what is needed to compile. Despite the size difference using the unmodified p1_defconfig (except setting the initramfs path), the problem that I have is the 3G radio will not start. I get a circle with the slash in the status bar and any dialer codes that pertain to the radio just force close. dmesg and logcats do not turn up any useful information or errors. Flashing the stock kernel back to the device alleviates the issue. So my questions are as follows: Is the source code complete? If so what could I be missing that would cause the radio to not start? Thank you in advance for any input on the issue.
Click to expand...
Click to collapse
and their response:
[SAMSUNG OSRC COMMENTS DELIVERY NOTIFICATION]
Dear customer,
Thank you for your continuous interest on our product.
We received your request on OSRC.
We reviewed your inquiry but unfortunately we couldnt publish the source code for some modules, because it is loadable kernel module and contains samsung proprietary code.
We published open source codes that are covered licenses which have obligation of publishing source code. (ex. GPL, LGPL, MPL...etc)
But we do not guarantee that open source code is excutable in target device. We are sorry for not giving you an correct anwser upto your satisfaction.
We are sorry for not giving you an correct anwser upto your satisfaction.
Thank you!
Sincerely yours
Click to expand...
Click to collapse
so for now until we can figure out what is missing we are out of luck as they are no help
when i have time i'll gladly work with you, oldmacnut, and any one else that can contribute into making a working base kernel from source
Thanks. This truly sucks and will impact my future choice of product purchases.
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
Hi all, i have been busting my head and still cant find like a proper tuto to do this.
If a repo does not have a phone/tablet added into it, how can i go ahead and add that device to a repo, so it can be synced?
example: add android_device_xxxxxx to the repo list in the repo github
What i will need to change or where.
I would really appreciate your pointing finger to the right way for me to get this.
Thank you.
Anyone built already a flashable .zip file or .img files for Android One (Sprout) smartphones? Anyone can upload the latest version here? I'm not of a techy type of person but it seems like a lot of Android One users are looking for an easy installable ROM for their Android phones. Like this for example: http://forum.xda-developers.com/general/xda-assist/flashable-firefox-os-rom-android-one-t3160682
I found this link: https://github.com/b2g-sprout/ however a lot of them are not technically enough and even I don't even know what to do with these files even though I have already tried using Firefox's instructions and some other articles on the Web about Porting FFOS. Full instructions on how to build Firefox OS from the files on the given link would also be appreciated. And also an example on how to update them for the latest version. Thanks for all willing to help...
Technically, the files from b2g-sprout github can be directly built after syncing AOSP source code.
The guide itself is mentioned in the B2G readme file here
https://github.com/b2g-sprout/B2G/blob/master/README.md
Building HELP!!!
F4uzan said:
Technically, the files from b2g-sprout github can be directly built after syncing AOSP source code.
Click to expand...
Click to collapse
Can you give me specific instructions then on what to do with these files then? Please. I tried extracting "B2G" and "B2G-manifest" on my Home Directory then the "device-sprout" to the folder inside B2G: "device/google/sprout/" and I have no idea what to do to the others but when I try "./config.sh", it keeps on telling me that "sprout.xml" doesn't exist which I have no idea why. I am still very confused and hoping that you can solve this thing. I would also want to help and upload builds if ever, posting it on those users asking for a Firefox OS build for their Android One phones. Hope you can help us... :angel: I'll note you on those posts also so don't worry. :good: I will appreciate it also if you are to upload an already built rom for Firefox OS 'coz I have searched every corner of the internet already and there's not yet a version for Sprout. Thank you very much...
Still Searching
I have been searching everywhere for weeks now but still no answers. Anyone can help? Sorry but I'm really a big fan of the Open Web... And would really want to create apps for FFOS. :crying:
Hello
I’m building my own android image (so obviously I have the source code)
I want to add my own drivers (specific ones), but I have no idea about how to add them, so any help?
Regards
Any help guys ? srsly, i'm very stuck here
do you mean your device tree?
DSA said:
do you mean your device tree?
Click to expand...
Click to collapse
yes
If the device trees exist, you will need to add a local_manifests folder & roomservice.xml into your repo folder with the relevant details included, mine is attached as an example.
If not, you will need to create them, heres a couple of initial guides:
[GUIDE] How to make a device-tree for your phone
Welcome in this new tutorial! In this thread, i'll try to explain you how to create a device-tree. This is one of the most important part in the rom porting. So let's start right now! Warning: i took as example an Samsung phone and 7.0 rom. 1...
forum.xda-developers.com
How to create Device tree for Android Rom building
How to create Device tree for Android Rom building I assume you already downloaded source code before we start please do following 1. Install unpackbootimg Go to https://github.com/jsharma44/bootimg-tools and download as a zip or use git...
forum.xda-developers.com
Drivers can change for every device. Which devices do you want to support?