Android OS Forum banner
1 - 20 of 77 Posts

·
Premium Member
Joined
·
4,348 Posts
For anyone who would rather get the proprietary files for your Galaxy Nexus for CM10 (or pretty much any other AOSP build) from a trusted repository instead of pulling them from your device, create a file called local_manifest.xml with the contents mentioned below and put it in your .repo directory (it's in the top directory for your CM 10 source). After editing, make sure to do repo sync once again. The below example is for toro, but the only difference is changing any mention of "toro" for "maguro" or "toroplus." I will leave it to the user to do that themselves


Example for Toro:

Contents of the file you need to create if it does not exist for Toro (local_manifest.xml):

(If you're using the latest CM, you can just clone it from here as well: https://github.com/y...oprietary_files)

https://github.com/yareally/android_proprietary_files/blob/master/local_manifest.xml (see here for the example because I don't want to maintain it in 2 separate places)

After creating the file with the contents, go ahead and run repo sync like normal and you're set. "The Muppets" is a github repository used by many of the CM members to hold miscellaneous files mostly related to proprietary stuff on various devices. Koush used to have them on his own github, but he and others all decided to merge them there instead.

NOTE: if you wish to build for something other than Android 4.2.2, replace cm-10.1 with whatever branch listed on the github link above.

Directions for ToroPlus and Maguro, etc:

To use with toroplus or maguro or whatever device, just sub out any mention the word "toro" from the XML markup above you have to paste for whatever you are trying to build. Didn't feel it was necessary to paste for all three devices since that's the only difference.
 

·
Premium Member
Joined
·
3,873 Posts
Is this working? It appears to be dumping all devices into vendor/samsung/toro which then leaves you with a path of vendor/samsung/toro/toro to get to the prop files.
 

·
Premium Member
Joined
·
4,348 Posts
Is this working? It appears to be dumping all devices into vendor/samsung/toro which then leaves you with a path of vendor/samsung/toro/toro to get to the prop files.
realized I pasted a mistake:

This should look like this:

Code:
<br />
<br />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="jellybean" /><br />
<project name="TheMuppets/proprietary_vendor_imgtec" path="vendor/imgtec" remote="gh" revision="jellybean" /><br />
I got over zealous about adding toro to things. Sorry about that. (editing the OP right now). Glad someone actually replied to tell me, thanks, lol.

Path tells it where to go on your own PC....so the way it was, it was most likely sticking all the prop files for every device in the "toro" directory or whatever. If you already synced, you can probably just move them up one directory or whatever. That or just remove all the vendor files and resync.

This is how your directory structure should look under vendor if all goes well: http://pastie.org/pr...2suxb5om2rmvudw
 

·
Registered
Joined
·
1 Posts
The broadcom bluetooth driver was split out into its own project, so local_manifest.xml also needs this line:

<project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="gh" revision="jellybean" />

Also missing, for the "orientation sensor," though things seem to work without it:

<project name="TheMuppets/proprietary_vendor_invensense" path="vendor/invensense" remote="gh" revision="jellybean" />

Caveat: http://knowyourmeme.com/photos/234765-i-have-no-idea-what-im-doing
 

·
Premium Member
Joined
·
4,348 Posts
The broadcom bluetooth driver was split out into its own project, so local_manifest.xml also needs this line:

<project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="gh" revision="jellybean" />

Also missing, for the "orientation sensor," though things seem to work without it:

<project name="TheMuppets/proprietary_vendor_invensense" path="vendor/invensense" remote="gh" revision="jellybean" />

Caveat: http://knowyourmeme....a-what-im-doing
Thanks, adding them to the OP. I missed those as they were part of the Samsung device tree when Koush had his own. Never actually use bluetooth so this is the first time I realized it was missing, since it builds fine without it.

Also, those are correct as they are :)
 

·
Registered
Joined
·
187 Posts
Doing this at any time is fine, it doesn't have to be before the first repo sync. Obviously you will need to call repo sync again after you add this, but syncing first and then doing this won't make a difference.

Also, are you sure that this is necessary?
Code:
<br />
<remote fetch="http://github.com/" name="gh" revision="master" /><br />
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="jellybean" /><br />
I don't think it is, I'm going to try it out now without it and report back.
 

·
Premium Member
Joined
·
4,348 Posts
Doing this at any time is fine, it doesn't have to be before the first repo sync. Obviously you will need to call repo sync again after you add this, but syncing first and then doing this won't make a difference.

Also, are you sure that this is necessary?
Code:
<br />
<remote fetch="http://github.com/" name="gh" revision="master" /><br />
<remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="jellybean" /><br />
I don't think it is, I'm going to try it out now without it and report back.
It would take some rewriting of the xml a bit as those are basically nicknames for the urls, but they're not entirely necessary. I've never tried to remove them, but based on their intentions, I would say it will not pull from those if removed. Feel free to try though, it won't hurt anything.
 

·
Registered
Joined
·
187 Posts
It would take some rewriting of the xml a bit as those are basically nicknames for the urls, but they're not entirely necessary. I've never tried to remove them, but based on their intentions, I would say it will not pull from those if removed. Feel free to try though, it won't hurt anything.
I did, it didn't work. Then I forgot to report back...
 

·
waffler
Joined
·
885 Posts
How would I go about doing this for d2att? Apparently I'm n00b and am doing something wrong.
 

·
Premium Member
Joined
·
4,348 Posts
Discussion Starter · #11 ·
How would I go about doing this for d2att? Apparently I'm n00b and am doing something wrong.
One would have to know what proprietary files it needs first.
 

·
Registered
Joined
·
187 Posts
How would I go about doing this for d2att? Apparently I'm n00b and am doing something wrong.
I believe that you would be good with just this line:

Code:
<br />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="jellybean" /><br />
Of course, you would also need a device tree for the phone as well, which you could get by using the "lunch" command and then entering the corresponding number for the d2att. (For me it's 5, I can't guarantee it's the same for you.)

EDIT: oops, I saw d2att and thought Droid 2. I probably should have known that it was NOT a Droid 2 on AT&T... Changed the code.
 

·
Dev Lackey
Joined
·
142 Posts
Maybe themuppets arent updated, but im having trouble with this in building CM10.1. Can anyone confirm? and anyway to fix?
 

·
Premium Member
Joined
·
4,348 Posts
Discussion Starter · #15 ·

·
Supporting Member
Joined
·
4,550 Posts
Am unable to complete a build of 10.1 for Toro...

My current manifest:

Code:
<manifest><br />
  <remote fetch="http://github.com/" name="gh" revision="master" /><br />
  <remote fetch="https://github.com/TheMuppets/" name="TheMuppets" revision="cm-10.1" /><br />
  <project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="gh" revision="cm-10.1" /><br />
  <project name="TheMuppets/proprietary_vendor_imgtec" path="vendor/imgtec" remote="gh" revision="cm-10.1" /><br />
  <project name="TheMuppets/proprietary_vendor_broadcom" path="vendor/broadcom" remote="gh" revision="cm-10.1" /><br />
  <project name="TheMuppets/proprietary_vendor_invensense" path="vendor/invensense" remote="gh" revision="cm-10.1" /><br />
  <project name="CyanogenMod/android_device_samsung_toro" path="device/samsung/toro" remote="github" revision="cm-10.1" /><br />
  <project name="CyanogenMod/android_kernel_samsung_tuna" path="kernel/samsung/tuna" remote="github" revision="cm-10.1" /><br />
  <project name="CyanogenMod/android_device_samsung_tuna" path="device/samsung/tuna" remote="github" revision="cm-10.1" /><br />
</manifest>
Build fails with:

Code:
target thumb C: vim <= external/vim/src/version.c<br />
external/vim/src/tag.c:103:1: warning: missing initializer [-Wmissing-field-initializers]<br />
external/vim/src/tag.c:103:1: warning: (near initialization for 'ptag_entry.fmark') [-Wmissing-field-initializers]<br />
external/vim/src/tag.c: In function 'add_tag_field':<br />
external/vim/src/tag.c:3765:10: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]<br />
make: *** No rule to make target `vendor/cm/proprietary/Term.apk', needed by `/home/redflea/android/cm10/out/target/product/toro/system/app/Term.apk'.  Stop.<br />
make: *** Waiting for unfinished jobs....<br />
target thumb C: vim <= external/vim/src/window.c<br />
[email protected]:~/android/cm10$ <br />
Appreciate any hints!! :)
 

·
Premium Member
Joined
·
4,348 Posts
Discussion Starter · #18 ·
you're missing the terminal emulator cm includes. either add it to the directory or comment it out of the make file under their vendor directory.
 

·
Supporting Member
Joined
·
4,550 Posts
you're missing the terminal emulator cm includes. either add it to the directory or comment it out of the make file under their vendor directory.
Thanks! Between you and Ballocaust's post, I'm now building. :)

Ballocaust said:
[background=rgb(245, 245, 245)]cd vendor/cm[/background]
[background=rgb(245, 245, 245)]sh get-prebuilts[/background]
[background=rgb(245, 245, 245)]This will pull down the terminal emulator apk and lib that's killing your compile.
[/background]

Updated the CM 10.1 build guide in my sig...
 

·
Registered
Joined
·
3 Posts
Hi

Will this method work for latest (master) AOSP sources ?
I really need to build working (with camera, BT etc) version of AOSP not CM.
If not, maybe someone know how to find vendor files for AOSP (Maguro) ?
 
1 - 20 of 77 Posts
Top