yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] GeyerA:
Hi, oh yes I am very happy as it has to work one time and then you got your baseline (can't stop thinking about blobs - the name is funny).

But now, it opened up a bunch of new problems. If you do not mind, can you talk for a sec about that linaro thing and if you think is is worth to add? I will continue to stay on AOSP because I can suffer/learn more.....:). Later when I see CM is mature, I will compile from there.

I am also thinking to add Halo (just to try). If you have a word on this .......
[Nexus 7 Android Development] fattire:
:rolleyes:

Linaro is a series of optimizations to increase performance. I did it with 10.1 for nook and didn't notice much of a difference, but that was OMAP3 and I think the big jumps were at least in OMAP4. If you choose to go off the reservation, you're doing your own experimental stuff so I'm not going to be much help there... but :fingers-crossed: good luck and let me know if it works...
[Nexus 7 Android Development] GeyerA:
All right, then I think it is time to start to chase Sparksco :). I also think for normal users, the noticeable difference might be small but I am not having the right knowledge to judge. The AOSP which I compiled yesterday was already smoother than the 4.2.2 which I run...but also, fresh install is always better I suppose. Any comments on adding Halo for instance? (and embedded Superuser).
[Nexus 7 Android Development] Archaic1881:
Just finished setting up my buildmachine again and started building. I only forgot tot enable caching so it will probably take all night before i see some results. :-$
[Nexus 7 Android Development] ratcav:
If anyone is interested I'm building cm 10.2 clean nightlies

http://xdaforums.com/showthread.php?t=2029151
[Nexus 7 Android Development] fattire:
For anyone building, I merged in the 10.1 cm kernel changes, so please test. I'd also appreciate some feedback on whether the bluetooth low energy changes cause problems. I haven't had any, so I'll include it tonight unless anyone notices something wrong....

ft
[Nexus 7 Android Development] fattire:
fstrim?

Okay here's a question...

So according to this, android 4.3 on grouper is supposed to use fstrim, which will keep the performance from slowing down over time...

But I can't find it enabled, either in the upstream init.grouper.rc or in logcat on my n7... the patch to vold is there, the binary is there, and it looks like everything the kernel needs is there too..

Anyone have any thoughts? is it running on your builds? I just don't see it in my logcats...
[Nexus 7 Android Development] ratcav:
I ran out of thanks, but thank you, you're the man :D
[Nexus 7 Android Development] Gandalf:
for the blobs, could i just flash the stock 4.3 AOSP and run the ./extract-files script ? or has the script not been updated to pull the necessary files for 4.3 yet?

already got my own builds running on my AT&T S4 (since I have a little trick to get my stuff for that), now looking into N7
[Nexus 7 Android Development] Archaic1881:
You can download and install the blobs from Google, I don't know if the other method works.

Is there a specific reason or time to make clean/clobber or can I just keep on brunching?
[Nexus 7 Android Development] fattire:
the extract-files script hasn't yet been updated. I was thinking of doing it, but hey-- anyone wanna do it for me and submit a pull request?

I haven't found any reason to make clean/clobber yet in the last few days...
[Nexus 7 Android Development] Gandalf:
I'll look into it right now. its 5am EST, don't have work until 8pm EST.. plenty of time on my hands :highfive:

---------- Post added at 05:04 AM ---------- Previous post was at 04:51 AM ----------

put all 7 archives in my main source dir, decompressed them, ran ./<file-name>.sh , and got this in /vendor:

did that happen as it should? making all those directories within /vendor ?
[Nexus 7 Android Development] fattire:
I think perhaps vold should be examined... especially this commit which is what essentially breaks it and has changed from 4.2.2 to 4.3 with the new grouper.fstab file (rather than /etc/vold.fstab)

That looks right. The folders I have are:

asus broadcom cm elan invensense nvidia nxp qcom tmobile widevine
[Nexus 7 Android Development] fattire:
...and...

.....vold fixed. This means that Internal Storage is now mounting via MTP. It also gets rid of the crash when you try to go to Storage from Settings. I think it may also allow USB OTG to work, but someone will have to try that...

Also, BLE is in.

Everyone do a fresh repo sync and make sure :P
[Nexus 7 Android Development] bangsti:
[MENTION=3041959]fattire[/MENTION]

Many Thanks, all is good and the Problems are fixed.
[Nexus 7 Android Development] dparrothead1:
OTG works. Thanks.
[Nexus 7 Android Development] elicik:
I don't do this because the official repos don't actually have cm-10.2 device and kernel branches for grouper yet. Once they do, I'll be happy to do that. Meanwhile, I'll keep using fat-tire's repo as it has the following features:
[Nexus 7 Android Development] Archaic1881:
Just checking: does focal force close for everyone ?
[Nexus 7 Android Development] fattire:
Focal was working two days ago but now it FCs for me...

My plan is to push to upstream cm-1.2 branch once its decently stable. Maybe in a day or two. There are no cm 1.2 nightlies yet so no hurry.

Also, was someone working on updating extract-files.sh? Thx!
[Nexus 7 Android Development] bluecarbon:
Awesome. Thanks for the guide, and everything. I'm now running my first build. I had to start from scratch once, but my second time through worked well.
[Nexus 7 Android Development] sparksco:
Hi fattire. I'm confused on a few things. Maybe you can answer some of these questions, thx!

1. You say to use Google blobs however cm AFAIK uses TheMuppets now for building their Roms. So the script is obsolete? A local_manifest.xml should pukk these repos in fine right?

2. Are device maintainers responsible for the device trees and/or kernels or what exactly? I don't see much activity from the maintainers besides merge such and such change from gerrit code review occasionally. But now your taking pull request on your personal github too? So is gerrit no longer the official way to submit parches now? :confused: I think you guys updated the extraction before, but now you don't seem interested in doing it?...

Thanks again [MENTION=3041959]fattire[/MENTION]!
[Nexus 7 Android Development] fattire:
Remember, the 10.2 branch is brand new, and afaik there are no cm 10.2 builds being automated yet. The CM build system hasn't yet been set up, we're in super-early days here. The extract-files script is a helpful way for in future people to pull the blobs directly from the 4.3 stock devices when they are doing their own builds. Getting from Google is another option.

Yes, sorry for the confusion. Gerrit and the official repos are the correct way to submit code. I decided to do my own build (something anyone can do-- I simply used AOSP 4.3 as a base and cherry-picked stuff into the current cm-10.1 branch) before the stuff goes to the official repository, and do it in the open so that others could build as well and let me know if they see any issues before creating a new branch.

I want some of the other groupers maintainers to look at what I've done, then to push the kernel and device to cm-10.2 pretty soon, at which point everyone can submit to gerrit, etc. as per usual.

In other words, this is just temporary.
[Nexus 7 Android Development] fattire:
BFQ updated...

FYI-- just updated bfq from v5 to v6r2.... BFQ is an IO Scheduler. Select it from Settings->Performance->IO Scheduler.
[Nexus 7 Android Development] elicik:
This broke my build.... I now get some errors with brunch grouper

brunch grouper
including vendor/cm/vendorsetup.sh
Looking for dependencies
Adding dependencies to manifest
[B]CyanogenMod/android_kernel_asus_grouper already exists[/B]
Syncing dependencies

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3
CM_VERSION=10.2-20130801-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.10.3-1-ARCH-x86_64-with-glibc2.3.4
HOST_BUILD_TYPE=release
BUILD_ID=JSS15J
OUT_DIR=[B]censored[/B]
============================================
[B]Note that this is where breakfast grouper would end, and where mka bacon would start[/B]
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.3
CM_VERSION=10.2-20130801-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.10.3-1-ARCH-x86_64-with-glibc2.3.4
HOST_BUILD_TYPE=release
BUILD_ID=JSS15J
OUT_DIR=[B]censored[/B]
============================================
[B] File "build/tools/findleaves.py", line 95
print r
^
SyntaxError: invalid syntax
File "build/tools/findleaves.py", line 95
print r
^
SyntaxError: invalid syntax
File "build/tools/diff_package_overlays.py", line 88
print r
^
SyntaxError: invalid syntax
No private recovery resources for TARGET_DEVICE grouper[/B]
Target boot image: /home/eli/android/system/out/target/product/grouper/boot.img
----- Making uncompressed recovery ramdisk ------
/home/eli/android/system/out/host/linux-x86/bin/mkbootfs /home/eli/android/system/out/target/product/grouper/recovery/root > /home/eli/android/system/out/target/product/grouper/ramdisk-recovery.cpio
usage: mkbootimg
--kernel <filename>
--ramdisk <filename>
[ --second <2ndbootloader-filename> ]
[ --cmdline <kernel-commandline> ]
[ --board <boardname> ]
[ --base <address> ]
[ --pagesize <pagesize> ]
[ --ramdisk_offset <address> ]
-o|--output <filename>
make: *** [/home/eli/android/system/out/target/product/grouper/boot.img] Error 1
make: *** Waiting for unfinished jobs....
[Nexus 7 Android Development] Archaic1881:
My build is broken too, i didn't really look at it yet but I think mine got up to recovery. I will look at it more detailed later.
[Nexus 7 Android Development] fattire:
Upstream issues? Try repo syncing today later and let me know if it's still screwy
[Nexus 7 Android Development] ratcav:
My build works perfectly, thanks!
[Nexus 7 Android Development] bluecarbon:
Same here.
[Nexus 7 Android Development] Archaic1881:
I probably sync'd at the wrong time, i did a make clean (just to be sure), resync & the new build was fine after that.
[Nexus 7 Android Development] ekanix20:
in terminal it says that i t can't find the command repo, so I'm stuck there.. any suggestions?

Sent from my Nexus 7
[Nexus 7 Android Development] h00py:
Hey FT I was just reading the comments for your change "Add extract-files/setup-makefiles scripts. Should match Google's blob locations.". Does this mean you're the device maintainer for the Nexus 7 now? If so, congrats :good:

---------- Post added at 07:41 PM ---------- Previous post was at 07:33 PM ----------

Have a read of the first part of this page called "Installing Repo" and that should fix your problem.
[Nexus 7 Android Development] fattire:
So this is a Windows issue it sounds like-- I'm not too familiar with what USB drivers you might need-- can anyone help him out w/this?

I'm a little unsure as to where this permissions error you're experiencing occurred.. with fastboot? If so, maybe try

sudo fastboot flash recovery recovery.img

See if that works a little better.

See h00py's suggestion above. You probably need to adjust your PATH and/or give repo execute permissions via chmod.

Looks that way.. at least for now. Someone had to do it :) It won't just be me though. I believe/hope I'll be sharing the job.
[Nexus 7 Android Development] h00py:
I couldn't get my windows adb to recognise my nexus 7 for ages. I eventually had to use this to get the right drivers http://xdaforums.com/showthread.php?t=1809195

If you're sure your Windows drivers are working try killing adb and running it as root on your VM. My adb will only see devices if I do this.
[Nexus 7 Android Development] ekanix20:
I can't even install Java.

This comes up in my terminal:

root@emil-MS-7673:~# sudo apt-get install sun-java6-jdk

Reading package lists... Done

Building dependency tree

Reading state information... Done

Package sun-java6-jdk is not available, but is referred to by another package.

This may mean that the package is missing, has been obsoleted, or

is only available from another source

E: Package 'sun-java6-jdk' has no installation candidate

Kinda embarrasing question. But how do I do? I really cant seem to figure it out.
[Nexus 7 Android Development] h00py:
Installing java was a pain for me too. Only method I found that worked was the "update 3" part at the bottom of this page http://happy-coding.com/install-sun-java6-jdk-on-ubuntu-10-04-lucid/
[Nexus 7 Android Development] ekanix20:
Thanks but i think i figured it out, used this guide. http://www.liberiangeek.net/2012/04/install-oracle-java-jdk-7-in-ubuntu-12-04-precise-pangolin/

I hope that Java 7.0 works :fingerscrossed:
[Nexus 7 Android Development] myepicyear:
I got the error inside of clockwork recovery when flashing the finished build package. It gives an "error 7", and says it's permissions are wrong/couldn't create some symlinks.

But, after it "fails" to flash, if I press reboot system, clockwork recovery asks me if I'd like it to fix system/xbin/su, and if I say yes, it does boot....but I can't rely on that solution forever.
[Nexus 7 Android Development] z1gackly:
I believe I installed the sdk properly. I'm not entirely clear what you mean by "linked" though.

The other advice looks very useful. I had assumed that all devices would be passed through, but I will try that. Thanks.

It works.in windows, and I tried it as root in Ubuntu. I'm thinking it may well have been that I did not understand how to set up Virtualbox as described above.
[Nexus 7 Android Development] tonyp:
As I'm going to get a N7 during the next days I thought I'll check out the build instructions already... and finally I can correct something from the great fattire (or embarrass myself if this is wrong) :D

Apperantly at Android (CM) "make clean" removes $OUT completely - and make clobber is just calling make clean.

Even the link you have in the above post is updated to this fact.

Here's an extract from the CM main.mk file:

https://github.com/CyanogenMod/android_build/blob/jellybean/core/main.mk

.PHONY: clean
clean:
@rm -rf $(OUT_DIR)/*
@echo "Entire build directory removed."

.PHONY: clobber
[B]clobber: clean[/B]

tl;dr: at Android it doesn't matter if you type "make clean" or "make clobber" - both just does the same thing (removing the out dir).
[Nexus 7 Android Development] fattire:
Interesting.. they used to be different, I think... Well, either one works I guess. Thanks! :)

("The great fattire"? Oh, c'mon! :silly:)
[Nexus 7 Android Development] z1gackly:
Make sure you have installed it to ~/bin and added that to your path in your .bashrc or equivalent and sourced again.
[Nexus 7 Android Development] remydlc:
Hi guys,

If I don't use/download any recovery such as twr or cwm, would the build leave my existing recovery alone once I flash it? Or it is something that needs to be there?

I have TWR and just read the instructions were different of course, then wondered if I am rooted already maybe I could skip that step and build the ROM without the recovery.img.

Thanks

EDIT: never mind, I just noticed that CMW is normally installed separately, not flashed along with the ROM.

The ROM is building up. Once I find everything went ok, i will try to build AOKP for my N7... granted its development allows for a good install.
[Nexus 7 Android Development] ekanix20:
hey guys, I'm gonna start building now, if I already have clockworkmod on my device, do I need to include that in my building process or is it OK with only the ROM zip?

Then I transfer to ROM to my device and then flash? :)

Thanks

Sent from my Nexus 7
[Nexus 7 Android Development] napster113:
When I try to do a repo sync I keep getting fetch errors, any ideas .

Sent from my HTC One X using DroiDevs 2
[Nexus 7 Android Development] dirtsky:
Thanks for posting this great tutorial. I have used your Nook Color tutorial and it is really good as well. Im going to start up a new linux machine tonight to start building.
[Nexus 7 Android Development] napster113:
This what I'm getting when I try to repo sync, anyone tell me what I've done wrong ,sorry to post again but It's bugging the hell out of me. :)

Sent from my HTC One X using DroiDevs 2
[Nexus 7 Android Development] z1gackly:
Decided to go for a dual boot. Virtualbox is too clunky. Building my first build now, but I can't wait to get to the messing about stage :D
[Nexus 7 Android Development] myepicyear:
I know positively that this does work for most people. It has for me

From the official Android development site:

More rarely, Linux clients experience connectivity issues, getting stuck in the middle of downloads (typically during "Receiving objects"). It has been reported that tweaking the settings of the TCP/IP stack and using non-parallel commands can improve the situation. You need root access to modify the TCP setting:

$ sudo sysctl -w net.ipv4.tcp_window_scaling=0

$ repo sync -j1
[Nexus 7 Android Development] napster113:
Thanks bud I'll give it a try tomorrow'

Sent from my Nexus 7 using DroiDevs 2
[Nexus 7 Android Development] RBMacGregor:
Hi fattire! You got me intrested in building way back in the nook color days and I'm still at it. I have some friends with tilapia an figured it wouldnt be to hard to take your device tree seeing how most of groupers stuff is used by tilapia. I seem to be getting farther and farther along here but I'm running into a issue with my toolchain not liking the kernel. Its been years since I used cm seems to be a litle more difficult to change the toolchain out. Do you have any ideas? Id get you the error but Im mid build again. Thanks for everything you have done for me and the community.
[Nexus 7 Android Development] fattire:
Are you not using the toolchain included with cm? You should talk to nemith as he's putting together the tilapia build I think...
[Nexus 7 Android Development] RBMacGregor:
Great thanks! I am using the standard tool chain. I'll have to give him a shout if I get stuck but I'm been banging along.
[Nexus 7 Android Development] sparksco:
AOSP has a new way of using gcc and the toolchains now. They added two variables TARGET_GCC_VERSION and TARGET_GCC_VERSION_EXP

Have a look in build repo you'll see it. In short, if TARGET_GCC_VERSION or TARGET_GCC_VERSION_EXP isn't set it defaults to gcc 4.7 (their new toolchain). But in their prebuilt kernels I think they still use gcc 4.6... So this would seem problematic for inline kernel building.

At that point there's a couple options. You could set TARGET_GCC_VERSION_EXP := 4.6

in the BoardCofigCommon.mk or find some patches for higher gcc versions like 4.7. I think I have some in my older kernel source. I'll see if I can dig it up.
[Nexus 7 Android Development] ratcav:
Would you like to share if you succeed with building for tilapia?

Thanks :)
[Nexus 7 Android Development] TheDarkDefender:
[MENTION=3041959]fattire[/MENTION]

I implemented your cm10.2 guide for mako,but just replaced the grouper specific ones with the ones for mako. The google blobs were giving issues, rom didnt boot but built fine. So I flashed a cm10.2 unofficial and pulled the blobs from it. Worked fine afterwards.

As always,thanks a ton for the guide! :D

Sent from my Nexus 4
[Nexus 7 Android Development] RBMacGregor:
Thanks for the input. Things are definitely different this time around for tool chain setup. Where I used to just swap to whatever I wanted in envsetup.sh its referenced as targetgccversion and points to variable

# defined in core/config.mk

targetgccversion=$(get_build_var TARGET_GCC_VERSION)

export TARGET_GCC_VERSION=$targetgccversion

Also seems to be fstab changes thats where Im stuck at the moment.

raise ValueError("malformed recovery.fstab line: \"%s\"" % (line,))

ValueError: malformed recovery.fstab line: "/sdcard	datamedia	/dev/null"

Im getting in recovery.fstab

# mount point	fstype	device

/sdcard	datamedia	/dev/null

I think it should be

/sdcard	vfat	/dev/block/sda1

edit. Sorry about dumb questions. I guess everything fstab related now falls under fstab.<device>
[Nexus 7 Android Development] RBMacGregor:
Up on xda. Booted it on my grouper so I dont know if mobile data works. I just put it up so might be a little till I get feedback.
[Nexus 7 Android Development] Archaic1881:
another question that I can't seem to find the answer to:

whenever I just repo sync & brunch grouper I do get a 'working' build, but for example my build.prop is not updated. Also during the weekend the SELINUX stuff has been updated, I did a sync and a brunch but I could not find the SELinux status entry in my 'about tablet'.

The file I get is named properly, and it flashes without issues.

If I make clean first I do get a fully updated build, for example the SELinux status entry was included after that, and the build.prop was also propely updated.

Am I doing something wrong ? Did I google the wrong keywords ? Tell me. :D
[Nexus 7 Android Development] TheDarkDefender:
Well, afaik,that's how it's supposed to work. I don't think you're doing anything wrong here.
[Nexus 7 Android Development] sparksco:
To activate selinux tap it three times...
[Nexus 7 Android Development] TheDarkDefender:
Or this http://xdaforums.com/showpost.php?p=43997507&postcount=575
[Nexus 7 Android Development] sparksco:
Tapping it three times seems easier... :)
[Nexus 7 Android Development] TheDarkDefender:
Yes,lol. That's enabling. I think it comes enabled by default, just like aosp.. Saw a comment by rmcc saying so.

The one i posted is how you change the modes within SELinux. Enabled/permissive/disabled
[Nexus 7 Android Development] sparksco:
It's to switch between enabled and permissive. Permissive being essentially the same thing as disabled. That's why permissive (disabled) is default? The only time I've seen it display disabled is when I'm on a kernel that doesn't support it..
[Nexus 7 Android Development] TheDarkDefender:
Ah ok,i think literally, permissive means it's disabled, but it takes logs of the violations that happen. Disabled doesn't do that. Well, if that's what you meant, ignore this, lol :)
[Nexus 7 Android Development] strat6:
brunch grouper error

I'm getting this error at the end of my build

http://pastebin.com/z6hDU76V

Any ideas? Also, I'm on Ubuntu 13.04.
[Nexus 7 Android Development] celloevan:
Build breaking during kernel comp

I'm having trouble getting cm-10.2 to compile fro grouper... I'm on Debian 6.0.7, and repo sync seemed to go smoothly. But I'm getting stuck during the kernel compilation, and Google hasn't been much help. Any suggestions?

http://pastebin.com/X068cMeN
[Nexus 7 Android Development] sparksco:
ahem, www.pastebin.com :eek:
[Nexus 7 Android Development] celloevan:
Oh yeah, that thing... sorry. My OP updated.
[Nexus 7 Android Development] fattire:
So I'm on my phone and not fully able to look at this but it lookslike the issue is here:

/home/thepenismightier/android/system/external/llvm/include/llvm/ADT/SmallVector.h:249: undefined reference to `llvm::SmallVectorBase::grow_pod(unsigned int, unsigned int)'

collect2: ld returned 1 exit status

A linking error... Anything weird in your llvm? Using a non standard compiler or something?

The penis mightier for $200 Alex...
[Nexus 7 Android Development] celloevan:
Figured this out... There must have been a few old bits floating around my $OUT, because after a make clobber it compiled just fine. Thanks!
[Nexus 7 Android Development] :
going smooth