yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] nlabrad:
Hello guys.

I'm sorry if this has been answered before in this thread, i'm not able to read all the 155 pages atm.

I'm in the breakfast step.

The thing is that when it was downloading dependencies, i suffered a power outage and the connection dropped. It synced the repo, but not the deps. Now if i re-run the command, it won't download the deps that it was pulling.

As i don't know what breakfast downloads, i can't delete it to go back to the state previous to the breakfast. Or at least get the deps downloaded.

I stopped the process here because i don't know what problems this could bring in the future of the build.

If anyone has any tip for me, i would be very grateful. Thanks.

This is the last log:

Repository synced!

Looking for dependencies

Adding dependencies to manifest

Adding dependency: CyanogenMod/android_kernel_asus_grouper -> kernel/asus/grouper

Using default branch for android_kernel_asus_grouper

Syncing dependencies

remote: Counting objects: 2186611, done.

remote: Compressing objects: 100% (335906/335906), done.

Receiving objects: 19% (431165/2186611), 142.11 MiB | 367.00 KiB/s

fatal: Unable to look up github.com (port 9418) (Name or service not known)
[Nexus 7 Android Development] sparksco:
external/bluetooth doesn't have anything to do with grouper blobs...
[Nexus 7 Android Development] sparksco:
When you run brunch (not breakfast) grouper it will add the dependencies to .repo/local_manifest.xml and download them...

AFAIK breakfast is deprecated.
[Nexus 7 Android Development] nlabrad:
I used breakfast because the tutorial said to, it makes sense to me because it does some things before running mka. I ran brunch and it did the same, should i remove local manifest?
[Nexus 7 Android Development] sparksco:
Step #8

"Then try brunch grouper and see what happens."
[Nexus 7 Android Development] underwaterjr:
I've set up my source a couple of times and just add grouper device and kernel to my local_manifest file and don't use the breakfast command.
[Nexus 7 Android Development] nlabrad:
Well i did a repo sync, and all the following steps and it built successfully.
[Nexus 7 Android Development] strat6:
Fattire's After You Build Guide

OK... So I got it to build. Brunched my own nightlies. I'm looking at cm's official downloads and I flashed a ROM more current than what's available to download (SWEEEEET!!!). Could you please give us all some examples on how to do other things after the build like "cherry pick" stuff and customize our builds more by adding apps and all the other stuff on the after u build wiki. All the stuff I've seen about cherry picks is pretty generic. A part II or something to your guide would be cool!
[Nexus 7 Android Development] sparksco:
brunch grouper does the same thing the first time...

Did you search the net? cherry-picking is more of development testing than building as the patches on gerrit code review may have bugs and/or be unstable.
[Nexus 7 Android Development] strat6:
Yeah I've searched the net and found stuff but I'm talking about for grouper and CM10.2 specifically. Fattire's guide wasn't a generic guide. I'm saying a device specific "After You Build" guide. I would have never even thought that a noob like myself would be able to compile android and I guess I just want to keep moving forward. Grouper 4 Life!!!! Just kidding;p
[Nexus 7 Android Development] Archaic1881:
Then read the wiki, all information is there...
[Nexus 7 Android Development] fattire:
See http://wiki.cyanogenmod.org/w/Build_for_grouper#Success.21_So....what.27s_next.3F

Particularly http://wiki.cyanogenmod.org/w/After_You_Build

And

http://wiki.cyanogenmod.org/w/Development

Congrats on the build!
[Nexus 7 Android Development] Dj8218521:
Any idea's?

dj8218521@dj8218521-X202E:~/android/cm-10.2$ make otapackage -j4

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=4.3

CM_VERSION=10.2-20130830-UNOFFICIAL-grouper

TARGET_PRODUCT=cm_grouper

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

TARGET_CPU_VARIANT=cortex-a9

HOST_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-3.8.0-19-generic-x86_64-with-Ubuntu-13.04-raring

HOST_BUILD_TYPE=release

BUILD_ID=JSS15Q

OUT_DIR=/home/dj8218521/android/cm-10.2/out

============================================

build/core/base_rules.mk:130: *** device/asus/grouper/android_device_asus_grouper/recovery: MODULE.TARGET.STATIC_LIBRARIES.librecovery_ui_grouper already defined by device/asus/grouper/recovery. Stop.

dj8218521@dj8218521-X202E:~/android/cm-10.2$
[Nexus 7 Android Development] TheDarkDefender:
anyone please?
[Nexus 7 Android Development] #define:
I think the get-prebuilts script hasnt been run..
[Nexus 7 Android Development] TheDarkDefender:
Holy cow! Noobest mistake ever! I usually run it but this time,i cleaned up the source and forgot to add it to my script.

Thanks a lot man :)

Sent from my Nexus 4
[Nexus 7 Android Development] #define:
Happy to help..
[Nexus 7 Android Development] Dj8218521:
Could anyone help me out?

Was compiling for about 5 minutes and ran into this;

:(

Export includes file: external/pigz/Android.mk -- /home/dj8218521/android/cm-10.2/out/target/product/grouper/obj/EXECUTABLES/pigz_intermediates/export_includes

Import includes file: /home/dj8218521/android/cm-10.2/out/target/product/grouper/obj/EXECUTABLES/vim_intermediates/import_includes

make: *** No rule to make target `vendor/cm/proprietary/Term.apk', needed by `/home/dj8218521/android/cm-10.2/out/target/product/grouper/system/app/Term.apk'. Stop.

make: *** Waiting for unfinished jobs....

Export includes file: external/vim/src/Android.mk -- /home/dj8218521/android/cm-10.2/out/target/product/grouper/obj/EXECUTABLES/vim_intermediates/export_includes

dj8218521@dj8218521-X202E:~/android/cm-10.2$

EDIT: fix was the get-prebuilts and i didn't see it on last page.
[Nexus 7 Android Development] Codekrypt:
You need to run get-prebuilts.

Sent from my Nexus 4
[Nexus 7 Android Development] Dj8218521:
Got it!! Back up and running! :)

Thanks though!
[Nexus 7 Android Development] Codekrypt:
Great. No problem!

Sent from my Nexus 4
[Nexus 7 Android Development] GeyerA:
Error message AOSP

Hi, I know this is for CM but maybe somebody got a clue why this error now shows up. I was compiling before without problems but since I synced my repo to JSS15Q, it stops compiling right after starting...

geyera@debian:~/Calogeyer_AOSP$ make otapackage -j4
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3
TARGET_PRODUCT=full_grouper
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a9
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-2.6.32-5-amd64-x86_64-with-debian-6.0.7
HOST_BUILD_TYPE=release
BUILD_ID=JSS15Q
OUT_DIR=out
============================================
Checking build tools versions...
build/core/base_rules.mk:64: *** Module name: platform.xml
build/core/base_rules.mk:65: *** Makefile location: frameworks/base/data/etc/Android.mk
build/core/base_rules.mk:66: *
build/core/base_rules.mk:67: * Module is attempting to use the 'user' tag. This
build/core/base_rules.mk:68: * used to cause the module to be installed automatically.
build/core/base_rules.mk:69: * Now, the module must be listed in the PRODUCT_PACKAGES
build/core/base_rules.mk:70: * section of a product makefile to have it installed.
build/core/base_rules.mk:71: *
build/core/base_rules.mk:72: *** user tag detected on module.. Stop.
[Nexus 7 Android Development] sparksco:
I don't think Debian is officially supported...
[Nexus 7 Android Development] GeyerA:
Hi Sparksco, thanks for your answer. Actually was working before on my Asus laptop running Debian and also Lifebook. Just stopped yesterday when I synced the repo. No clue what has gone wrong or what I modified that does not anymore. I will delete all and start over again....:(

UPDATE, I un-did the last changes and found forking the platform_frameworks_base caused the issue. I must have caught the wrong version. All compiling now....sorry for the fake alert...:)
[Nexus 7 Android Development] underwaterjr:
If anybody cares I updated to ubuntu 13.10 and compiled just fine.
[Nexus 7 Android Development] GabrielSousa:
did you solve this ?

i have this error too
[Nexus 7 Android Development] koko98:
Can I use JWR66V blobs for latest 4.3.1 building?

Enviado desde mi LT30p mediante Tapatalk
[Nexus 7 Android Development] TheDarkDefender:
Yes

Sent from my Nexus 4
[Nexus 7 Android Development] fattire:
CM 11.0 Build Instructions

Well folks, it's that time again. The new source for cm has dropped, and it's time for you adventurous folk to start 'abuilding.

Some tips, if you've built the latest CM already...

1. cd ~/android/system (or wherever your source is) then

repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0

2. check your .repo/local_manifests/roomservice.xml to make sure the following are there

<project name="CyanogenMod/android_device_asus_grouper" path="device/asus/grouper" remote="github" revision="cm-11.0"/>

<project name="CyanogenMod/android_kernel_asus_grouper" path="kernel/asus/grouper" remote="github" revision="cm-11.0"/>

The above should be set up when you do the "breakfast grouper" command as well. (I don't think the revision="cm-11.0" is necessary any more btw since that's the default branch you're on.)

3. the 4.4 binary blobs/proprietary files are available here.

4. repo sync to grab the new CM 10.4 source.

5. If you plan on using gapps for 4.4, I guess find those yourself.

6. DO NOT USE JAVA 1.7 if you want this to build. You need Java 1.6, preferably sun's. If you're using ubuntu, you can do this to select the default java:

sudo update-alternatives --config java

7. Then try brunch grouper and cross your fingers.

Also, if you follow this thread a few more steps, you'll see more build info, including some screenshots and a screencast from kitkat running on n7 2012 :)

And finally, if you turn off the Dalvik VM and turn on the ART (Android Runtime) alternative-- you may have screwed up your device. Here's how to fix it.
[Nexus 7 Android Development] sgt. meow:
There are 4.4 PA Gapps.

And what's different in CM11 other than the "CM factor"? I'm thinking of stepping into ROM-building and I already have the AOSP base sorted; don't wanna sync a repo unless something major (that can't be cherry-picked properly) has changed between CM and AOSP.
[Nexus 7 Android Development] underwaterjr:
Will the java 1.7 thing eventually be sorted out or should we switch back to 1.6 permanently.
[Nexus 7 Android Development] koko98:
I havea compiled aosp and chromium takes around 4 hours.....

Enviado desde mi LT30p mediante Tapatalk

---------- Post added at 02:05 PM ---------- Previous post was at 01:50 PM ----------

Cannot find local_manifest folder.
[Nexus 7 Android Development] sparksco:
Sorry to hear [MENTION=3041959]fattire[/MENTION] about your Nexus 7 charging port. I have the same problem with my 2012 Nexus 7. It charges fine, however my computer no longer recognizes it when I plug it in via USB, for both USB debugging and also does not mount storage on Linux or Windows. Making it virtually impossible to develop for or test development on for logcats and other things.

It's been great fun guys. I'm waiting g for my nexus 5 to play with and plan on giving my daughter my n7 for Christmas since it still charges at least.
[Nexus 7 Android Development] fattire:
Yeah... i actually got it to charge last night, but won't be able to play with it until tonight...

as for what's new.. it's CM... not everything is working-- I think the dialer and launcher are still stock for example. Aside from that, until I get this built in the next few days I'm not sure what's in and what's out. But AOSP is pretty great, so if you like that, use that.

The build broke fairly early last night:

/media/test/jellybean/out/host/linux-x86/obj/SHARED_LIBRARIES/libESR_Portable_intermediates/src/ArrayListImpl.o: file not recognized: File truncated

I'd give the source a day or so to stabilize...
[Nexus 7 Android Development] MidnightNinja:
Just so everyone knows, there are a number of issues with the CM branch right now, the first two being Terminal and the Local_SDK_version.

I will update if I get anywhere, but I see little point if Im going to get a working CM11 build by the time they fix all the issues on their end.

Fattire, do you have a gchat that you'd be willing to pm to me? I'd like to pick your brain about the binary issues.

Edit: Bluetooth is the next error...

Edit: So here is a list of what goes wrong and when with the build

1) Local_sdk_version

2) Terminal being added

3)Bluetooth

4)Selinux-This is a kernel issue...there is something wrong with devices.te/ all the .te files

5) aaannnd kernels broke. No clue what i specifically did yet, but the kernel is going to need significant upbringing from the 4.3 branch. Maybe I have to merge in the 4.4 branch?
[Nexus 7 Android Development] fattire:
The Virtue of Pastebin

Also, for what it's worth-- it's usually a better idea to copy/paste the text contents of your log to a pastebin site such as gist.github.com or pastebin.com rather than take a screenshot. Then just post the resulting link.

The reason for this is that screenshots are sometimes hard to read (especially on phones and other small screens) and you can only capture what is on screen at that moment. I fyou grab the log and paste it for people to examine, you can include much more information, including stuff that may have lead up to the error..

Just a thought.

ft
[Nexus 7 Android Development] ekanix20:
When i started the building process it said that I had a wrong version if java, do I need to re do everything or can I just install the proper java version and start the building process again?

Sent from my GT-I9100
[Nexus 7 Android Development] napster113:
Yes sorry I will next time, I'm still trying to get my head around Linux .:)

Sent from my Nexus 7 using DroiDevs 2
[Nexus 7 Android Development] napster113:
Ihave included the paste bin text.

I'm running dual boot ubuntu, with 500mb swap and 40gb 4ext, I have installed java jdk 6 and the android sdk and updated it, but for some reason I keep getting the errors in the text provided.:crying::crying::confused:
[Nexus 7 Android Development] z1gackly:
Posting this from my second build with my first cherry pick, and it may be a very minor thing, but I no longer have mobile data widgets in the power widget settings.

I just want to thank you, Fat Tire, for setting me on this road. I know I'm gonna have a lot of fun with this!
[Nexus 7 Android Development] Nark.GA60:
Thanks fattire, I followed the instructions and built my first ROM! I also threw in the changes to get the tablet UI for good measure. :)

I could only adb as root until I did the udev rules. Instructions are here under "Configuring USB Access".

http://source.android.com/source/initializing.html
[Nexus 7 Android Development] fattire:
How to take pictures and videos and such...

Hey congrats to the above for their builds.

I posted this in the 720p thread in this forum, but if you missed it. Try this:

adb shell

$ su

# pm enable com.android.gallery3d/com.android.camera.CameraLauncher

Component {com.android.gallery3d/com.android.camera.CameraLauncher} new state: enabled

Should make the Camera app visible.
[Nexus 7 Android Development] JDima:
I seem to be missing cmparts - where should they be located?

Before CM10, I've only used CM7, the settings were available from the main screen. With this build, I see only four menus under "interface" and "performance" at the bottom. Is that correct?
[Nexus 7 Android Development] Nark.GA60:
It's in System. Above the Sound settings.
[Nexus 7 Android Development] BillGoss:
I could never get USB connectivity (and, therefore, ADB) working properly on Ubuntu and virtualbox. I switched to VMware Player and it worked perfectly.

You can also simplify the udev rules to just one line - valid for all Nexus devices:

SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"

Sent from my Nexus 7
[Nexus 7 Android Development] Nark.GA60:
I have this. Covers just about everyone.

# Acer
SUBSYSTEM=="usb", SYSFS{idVendor}=="0502", MODE="0666"

#ASUS
SUBSYSTEM=="usb", SYSFS{idVendor}=="0B05", MODE="0666"

#Dell
SUBSYSTEM=="usb", SYSFS{idVendor}=="413C", MODE="0666"

#Foxconn
SUBSYSTEM=="usb", SYSFS{idVendor}=="0489", MODE="0666"

#Garmin-Asus
SUBSYSTEM=="usb", SYSFS{idVendor}=="091E", MODE="0666"

#Google
SUBSYSTEM=="usb", SYSFS{idVendor}=="18D1", MODE="0666"

#HTC
SUBSYSTEM=="usb", SYSFS{idVendor}=="0BB4", MODE="0666"

#Huawei
SUBSYSTEM=="usb", SYSFS{idVendor}=="12D1", MODE="0666"

#K-Touch
SUBSYSTEM=="usb", SYSFS{idVendor}=="24E3", MODE="0666"

#KT Tech
SUBSYSTEM=="usb", SYSFS{idVendor}=="2116", MODE="0666"

#Kyocera
SUBSYSTEM=="usb", SYSFS{idVendor}=="0482", MODE="0666"

#Lenevo
SUBSYSTEM=="usb", SYSFS{idVendor}=="17EF", MODE="0666"

#LG
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666"

#Motorola
SUBSYSTEM=="usb", SYSFS{idVendor}=="22B8", MODE="0666"

#NEC
SUBSYSTEM=="usb", SYSFS{idVendor}=="0409", MODE="0666"

#Nook
SUBSYSTEM=="usb", SYSFS{idVendor}=="2080", MODE="0666"

#Nvidia
SUBSYSTEM=="usb", SYSFS{idVendor}=="0955", MODE="0666"

#OTGV
SUBSYSTEM=="usb", SYSFS{idVendor}=="2257", MODE="0666"

#Pantech
SUBSYSTEM=="usb", SYSFS{idVendor}=="10A9", MODE="0666"

#Pegatron
SUBSYSTEM=="usb", SYSFS{idVendor}=="1D4D", MODE="0666"

#Philips
SUBSYSTEM=="usb", SYSFS{idVendor}=="0471", MODE="0666"

#PMC-Sierra
SUBSYSTEM=="usb", SYSFS{idVendor}=="04DA", MODE="0666"

#Qualcomm
SUBSYSTEM=="usb", SYSFS{idVendor}=="05C6", MODE="0666"

#SK Telesys
SUBSYSTEM=="usb", SYSFS{idVendor}=="1F53", MODE="0666"

#Samsung
SUBSYSTEM=="usb", SYSFS{idVendor}=="04E8", MODE="0666"

#Sharp
SUBSYSTEM=="usb", SYSFS{idVendor}=="04DD", MODE="0666"

#Sony Ericsson
SUBSYSTEM=="usb", SYSFS{idVendor}=="0FCE", MODE="0666"

#Toshiba
SUBSYSTEM=="usb", SYSFS{idVendor}=="0930", MODE="0666"

#ZTE
SUBSYSTEM=="usb", SYSFS{idVendor}=="19D2", MODE="0666"
[Nexus 7 Android Development] biohazrd51:
I'm pretty sure you can just install the correct Java, but I can't remember if you need to link the appropriate java files using update-alternatives. It may do it automatically depending on how you install.
[Nexus 7 Android Development] ekanix20:
im getting this error when trying to build the rom.

http://pastebin.com/4QwRu8SX
[Nexus 7 Android Development] biohazrd51:
What Java are you running?

$ java -version
[Nexus 7 Android Development] z1gackly:
Wondering how to change my build so that ro.modversion comes out with the correct date in build.prop. Thanks.
[Nexus 7 Android Development] sparksco:
Building your own roms is fun. I thought maybe I would offer up my manifest to anyone that wants it. It's cm10 based. You don't need to run ./get-prebuilts since Rom Manager is removed, and terminal emulator is already built into the rom automatically.

repo init -u https://github.com/pbeeler/android.git -b jellybean
repo sync

Also don't need to add a local_manifest.xml since I'm using my own kernel and device tree (source for that is also on github). Just start building for grouper and it will download the extra needed repos and start building. Don't need ./extract-files.sh either, it's literally just sync and build.

Optionally there is a build script in the root of the source you can use to build for Grouper

./Grouper
[Nexus 7 Android Development] marty331:
My build went fine. But when I flashed it I got boots loops.
[Nexus 7 Android Development] sparksco:
Hi Napster, I see your building as root. A better approach might be to create a build script and set it with superuser permissions. Reason being is root doesn't always have access to all the tools/packages it needs to build. You can do that by typing something like this from the root of the source directory:

gedit grouper

Then paste or type your build commands in, this is the one I'm using

https://github.com/pbeeler/android_build/blob/jellybean/tools/build-scripts/Grouper

After save file and closing run the commands:

chmod 777 grouper

Then to execute:

./grouper
[Nexus 7 Android Development] goodloop:
device grouper vs recovery compatibility

target thumb C++: librecovery_ui_grouper <= device/asus/grouper/recovery/recovery_ui.cpp

device/asus/grouper/recovery/recovery_ui.cpp:23:20: fatal error: device.h: No such file or directory​

I failed building with above error message. I checked the code , seems that recovery_ui.cpp can't find device.h, which should be locate at bootable/recovery in AOSP. but in CM10 it disappeared.

the CM10 is using CWM recovery. is it compatible with current grouper device repository?:confused:
[Nexus 7 Android Development] sparksco:
The only time you should ever see that error is when your just running make command. Don't build cm10 like a aosp ROM. You need to follow make with something like bacon e.g. make bacon, or just the brunch command brunch grouper.
[Nexus 7 Android Development] koko98:
Modify android.mk files and change 19 with current.

Enviado desde mi LT30p mediante Tapatalk
[Nexus 7 Android Development] MidnightNinja:
I have the AOSP 4.4 Source downloaded, so I copied the correct sdk (19) folder over.
[Nexus 7 Android Development] MidnightNinja:
Fattire, is it possible to point cm to the stock kernel vs the cm derived one? Just asking since we know the AOSP prebuilt kernel works
[Nexus 7 Android Development] fattire:
I didn't notice any changes to the AOSP prebuilt source for 4.4, but you can just change the device/asus/grouper/BoardConfig to use a prebuilt kernel. See the wiki, particularly the part about falling back to prebuilts.

And btw-- another plug for the wiki.. we worked hard on it, especially the development section, so always look there first :) (not saying you should have in this case, but speaking generally...)
[Nexus 7 Android Development] MidnightNinja:
Alright, sorry for the inconvenience. Thanks!
[Nexus 7 Android Development] krylon360:
fattire is my her0 :-p will build tomorrow. And see if I can boot the good old encore while I'm at it. Guess I'll charge it tonight. :)
[Nexus 7 Android Development] fattire:
Har :)

So a couple more tips. Thx to dhacker29...

* Replace device/asus/grouper/sepolicy with the one from aosp. We're using the aosp sepolicies for the moment. I expect that will change, so remember-- all this stuff we're doing now is just quick and dirty to try to get to a build that might be close to working...

* mv the SEPOLICY lines from BoardConfigCommon to BoardConfig as you see in AOSP...

(This gets done in the commits below, so don't do by hand like this)

UPDATE: Notice in the log of changes there are a few "snapshot to" commits from the last 7 days? I'm betting those need to go in too. I'm gonna stop the build and apply 'em as best they fit.

UPDATED AGAIN: Okay, created two more full commits to mirror what was done in AOSP hopefully. Start with the untouched latest repo and then try applying these (in order). NOTE that they don't update the cm.mk fingerprint for 4.4, so you can feel free do that yourself before building. Something like:

#Set build fingerprint / ID / Product Name ect.

-PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=nakasi BUILD_FINGERPRINT="google/nakasi/grouper:4.3/JWR66V/573038:user/release-keys" PRIVATE_BUILD_DESC="nakasi-user 4.3 JWR66V 573

+PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=nakasi BUILD_FINGERPRINT="google/nakasi/grouper:4.4/KRT16M/573038:user/release-keys" PRIVATE_BUILD_DESC="nakasi-user 4.4 KRT16M 573

Assuming this builds, I'll have to add a third commit to update the fingerprint. If you have breakage, please compare my commits to the "official" ones from AOSP and see what I may have done wrong.

While it builds, I'm having a drink. I fully expect to come back to shards of shattered code everywhere.