yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] underwaterjr:
Good idea, but I don't think anybody will take the time when the official ones will be posted any day now.
[Nexus 7 Android Development] slebit:
Binaries is now available for download.
[Nexus 7 Android Development] mastamoon:
They must have been watching my conversation!! :P
[Nexus 7 Android Development] Sultanxda:
"revision" is the branch of the repository to pull from. By default for the CM11 manifest it is "cm-11.0", but my binary repo is on branch "master".
[Nexus 7 Android Development] Streuli273:
How do I change SELinux from Enforcing back to permissive? Is there anything to do this, at the moment it has broken my Ultimate Dynamic Navbar, so home and back don't work. On 4.2-4.3 I could just tap on SELinux statues in about tablet and turn it on or off, but in KK I can't do that.

A bit off topic but I was wondering if I could disable it before building a ROM, flashing a self-compiled modified zip with it disabled.

Any scripts or modifications to turn this off?

Thanks.

Edit: solved with selinux Disabler from play store. Came out literally just after I posted this.
[Nexus 7 Android Development] underwaterjr:
Anybody able to help me? pastebin
[Nexus 7 Android Development] fattire:
Just curious if you set sun java 1.6 to the default...?
[Nexus 7 Android Development] underwaterjr:
I did do that but I also have java 1.7 on the machine should I remove that?
[Nexus 7 Android Development] Screw Muggz:
You dont have to remove java 1.7, just switch to 1.6 for building. This should do it, then select the correct java version:

sudo update-alternatives --config java

hope that helps.

EDIT:

I remember that for some reason when I would set 1.6 as the default, for whatever reason it would keep reverting back to 1.7,

so I set this line in my .bash_aliases file (Im better with Fedora and would have used .bashrc instead, but it works) :

export JAVA_HOME="/opt/jdk1.6.0_45"

of course you would have to change the path if this isn't where you jdk is located.
[Nexus 7 Android Development] underwaterjr:
Ok thanks I will play around and see what happens.
[Nexus 7 Android Development] Screw Muggz:
I just wanted to report that I have also had a successful build with the 4.4 binaries using the above mentioned revision.
[Nexus 7 Android Development] jschill31:
Hello,

Can you clarify what exactly you changed and where? It has been a long time since I have had to revert anything (nook days) and my old brain is failing me this morning? I understand I need to "revise" the bold but not sure where to go to add the lines.

Thanks!

Cheers

Edit: OK, I think I figured out what to edit...at least it is building
[Nexus 7 Android Development] underwaterjr:
Ok you guys are the smartest guys in the whole universe. Even with java 6 set as default it still wouldn't build. I completely removed java 7 and woo hoo got a build and using it now.

Thank you!!
[Nexus 7 Android Development] webdroidmt:
@fattire

There seems to be an issue with native USB OTG in the latest CM11 builds. I'm posting it here because I remember you solved the fstab/vold issues in CM for native OTG when 4.3 first came out. Also, I figured it would be a good thing to get it squared away before CM goes to nightlies.

Here's the deal, native USB OTG worked correctly on the first CM11 builds from both koko98 and swordrune10. From troubleshooting, it seems that the common denominator for both builds is /bin/vold.

Fstab grouper in the ramdisk and storage_list.xml in framework-res are good in both builds mentioned above but I noticed that the vold file in bin has changed in size and I'm guessing in functionality.

Now, USB OTG doesn't automount a flash drive on boot and when you try to mount it, it acts like it's being recognized, but it shows as blank storage in both settings/storage and a file manager. This same behavior occurs on both new CM builds. Please keep in mind, I'm talking about native OTG, not having to use an app like stickmount. This was functional on CM 10.2 and was functional on the first CM11 builds.

I'm guessing that there was a commit somewhere around 11/13 or 11/14 that broke vold??? I was hoping that you would look into this and weave some of your magic. :laugh: As always, thanks for all the great stuff you do here.

Mike T
[Nexus 7 Android Development] fattire:
Here are the changes to vold in the past few days...

Here is the fstab file... so who wants to figure out what we need to change? :) Last time I remember just changing fstab.grouper to the new 4.3 format... I don't use OTG myself so it's hard to check... you're saying it shows as "blank storage" meaning there's no file system or what? I wonder if vfat is still used given that FUSE layer that's now on everything. Or maybe not..

Take a look at this-- it describes how the voldmanaged line should be set:

<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>

That's the format for > 4.3, where:

src: A path under sysfs (usually mounted at /sys) to the device that can provide the mount point. The path must start with /.

mount_point: Filesystem path where the volume should be mounted.

type: The type of the filesystem on the volume. For external cards, this is usually vfat.

mnt_flags: Vold ignores this field and it should be set to defaults

fs_mgr_flags: Vold ignores any lines in the unified fstab that do not include the voldmanaged= flag in this field. This flag must be followed by a label describing the card, and a partition number or the word auto. Here is an example: voldmanaged=sdcard:auto. Other possible flags are nonremovable, encryptable=sdcard, and noemulatedsd.

On grouper that line is:

/devices/platform/tegra-ehci /storage/usbdisk vfat defaults voldmanaged=usbdisk:auto

As it was working previously, I assume we have it right, but possibly one of those vold checkins screwed it up?
[Nexus 7 Android Development] jgramkow:
I get the following and it stops the build:

----- Making recovery image ------

Made recovery image: /home/jeremy/android/system/out/target/product/grouper/recovery.img

make: *** No rule to make target `vendor/asus/grouper/proprietary/btmacreader', needed by `/home/jeremy/android/system/out/target/product/grouper/obj/EXECUTABLES/btmacreader_intermediates/btmacreader'. Stop.
[Nexus 7 Android Development] webdroidmt:
@fattire

Thanks for your reply and info. Wow, lots of recent commits for vold. Anyway, from my limited knowledge, fstab.grouper appears to be correct unless Google has introduced something else here. Unfortunately, comprehending vold is above my pay grade, so I don't think I can shed any more light on that. Regarding my meaning of storage being blank, in CM file manager it would show usbdisk but when you select that "folder", it won't show the contents and goes to a parent folder.

Additionally, if you go into settings/storage, the OS will say it's preparing storage but nothing happens. Oddly enough, I replaced the current vold file with the one from koko98's earlier build and OTG capability came back. However, although you could properly access the usb drive via settings/storage and any file manager, when trying to install ANY apk from usbdisk, it resulted in a parsing error. File transfer to and from the usbdisk seems to work fine.

Now, to throw another curveball, I reverted back to koko98's first build from 1108 and...the same parsing error when trying to install apks. I just never initially noticed this because I hadn't installed any new sideloaded apks. Everything was either Titanium or installed from PS. Fyi, just tried and same thing happens on swordrune10's earlier build.

I'm on multirom, so I'm gonna' "clean up" and just install a fresh CM11 to see if that may be a factor. I just need to charge up my N7 from all the constant flashing and nandroiding ( is nandroiding a word?) LOL That's one of the great things about multirom, makes it really easy to try lots of different roms with little to no danger. :)

Hopefully, this will work out, as I've mentioned in the past with an 8GB N7, OTG is big for me.

Thanks again,

Mike T
[Nexus 7 Android Development] fattire:
Did you use extract-files.sh or setup-makefiles.sh to get the props/blobs/binaries? If so, you shouldn't have. Those need to be updated (volunteers?). In the meanwhile, or in the meantime as some people say, you should clear out vendor/ and use the proprietary binary file installers provided by Google.

Someone should probably update the setup-makefiles.sh. Who wants to do it?

Let's see if this vold issue is something (A) caused by your multirom and all the stuff you were talking about (B) something that's affecting other devices. If its not just grouper, we should look to upstream to figure out what the problem is. I let people know that there do seem to be issues with OTG + vold, so we'll see if it's a wider issue beyond ourselves... I'm suspecting it is, because I do think we've got the right vold.grouper setup (unchanged from 4.3) and the right kernel stuff (also unchanged)...
[Nexus 7 Android Development] jgramkow:
It was extract_files.sh as instructed in the Wikipedia guide.
[Nexus 7 Android Development] webdroidmt:
Well, I cleaned everything up and still the same parsing error when installing apks from usbdisk, so looks like multirom is not the problem. This issue was present on both current CM roms, as well as the current Slimkat rom.

I'm going to keep using the vold file from the first CM build even though it gives me the parsing error. It still performs all other OTG usbdisk functions and when I need to install a sideload apk, I can transfer it to internal storage. I thought maybe it was some kind of permissions issue or selinux yet Titanium has no problem backing up and restoring on the usbdisk. I've tried so many combinations to make it work, I'm stumped. LOL

You're probably right about it being a wider issue and I'm counting on people more experienced than me to fix it. :D

Mike T
[Nexus 7 Android Development] jschill31:
A big thank you to Fattire for once again getting me to fire up my build machine... You Rock! I have learned more from you in the past few years than any other dev. BTW I also can confirm full build with new blobs. As listed prior all that needs to be changed is: edit vendor/nvidia/grouper/keymaster/keymaster_grouper.cpp few lines from the top all you need to change is #include <UniquePtr.h> to #include <utils/UniquePtr.h> and then go to bed because it takes a long time to compile.

Cheers
[Nexus 7 Android Development] webdroidmt:
Well, there's one more thing that I tried and it worked. :good: I remember you saying that 4.4 pretty much followed 4.3 with fstab etc.so it made me think of trying to match the exact combo of fstab.grouper, storage_list.xml and vold.

Long story short, the vold file from CM 10,2 4.3 works perfectly with seemingly no ill effects. It works exactly as it did in 4.3, ie; native OTG usb storage that automounts with no need of an app like stickmount. It shows up properly in settings/storage, works correctly with file managers and Titanium Backup.

Fyi, the vold replacement works with SlimKat as well as CM. This will not work on a stock rom, as it uses a different fstab, storage_list and vold.

Thought this would be a nice temporary fix for those that need/want native OTG ability until it's fixed upstream. Although the CM 4.3 binary works in both CM11 and SlimKat 4.4, I've linked the Slim 4.3 binary which also works in SlimKat, for those that may want Slim's native binary. Although, it works either way. :)

NO LONGER NEEDED! Removed Dead links.

EDIT: Looks like this workaround does not work with CM11 Official/Unofficial android 4.4.1/4.4.2. It seems that something has changed in the CM11 stock ramdisk in builds starting from Dec 07. If you still want to use this workaround, you need to use a custom kernel with a ramdisk that is compatible with CM11.

This will work with M-Kernel a64 or higher and Lean Kernel 3.0 or higher. If you use Franco Kernel, it will work with the r76 version that Osmosis fixed. These kernels could also stop working in future releases if they make changes to their ramdisk similar to CM stock kernel but for now they do work.

So to be clear, on CM builds of 12/07 or later, you need to flash both the 4.3 vold binary zipfix and a custom kernel, either M-Kernel, Lean Kernel, or the Franco Kernel fixed by Osmosis. This works and will work until CM either fixes it so we don't need it, or breaks it again with commit or two. :laugh:

Thanks for all your feedback.

Mike T
[Nexus 7 Android Development] fattire:
So this looks like it's the binary that was indeed the problem, and must have been one of the vold checkins I linked to earlier... if so, then upstream should probably be notified...maybe even see through elimination if you can figure out which of the checkins it is--

you know that if you cd to the vold source and type mmp (make module), ONLY the vold module will be build and pushed to the device, right? You can I think specify a don't-use-previous-object-files with something like mm -B to build from scratch...

here are the commands and what they do:

- mm: Builds all of the modules in the current directory.

- mmp: Builds all of the modules in the current directory and pushes them to the device.

- mmm: Builds all of the modules in the supplied directories.

- mmmp: Builds all of the modules in the supplied directories and pushes them to the device.

- mma: Builds all of the modules in the current directory, and their dependencies.

- mmma: Builds all of the modules in the supplied directories, and their dependencie

Anyway, if you're feeling genreous with your time, since you have the OTG stuff, if you want to try to see if you can rebuild a "good" vold binary, then let the maintainer know which commit broke it, that'd be much appreciated, surely-- and then you'll get your mainline fix even faster :)
[Nexus 7 Android Development] koko98:
Im getting these errors when syncing repo:

error: prebuilts/clang/linux-x86/arm/3.3/: platform/prebuilts/clang/linux-x86/arm/3.3 checkout 9e3db43b140dac1244a4a1df79d1622ce0a79b44
error: prebuilts/clang/linux-x86/mips/3.3/: platform/prebuilts/clang/linux-x86/mips/3.3 checkout 6abb1bd849c7e7bfcc3906ea2c115eaf53564206
[Nexus 7 Android Development] webdroidmt:
I guess you assume I can code or build but I can not. If this is to be fixed, someone else will have to do it.

Mike T
[Nexus 7 Android Development] fattire:
Ah. Okay, so someone who's building and has a OTG extenral storage device i guess will have to do it. Or, if as we assume the probelm is upstream, let's hope someone on another device who has the same problem fixes it :) Otherwise... I might be able to mess with it at some future point. I have an OTG cable just bought... it should work with a USB drive or something right?
[Nexus 7 Android Development] webdroidmt:
Thanks, man. If you can get to it at some point awesome, if not I'll just continue to swap out the vold binary. :)And yes, it should work with a usb flash drive that doesn't require external power with no problem.

Mike T
[Nexus 7 Android Development] Phil3759:
Hi,

Hope this is the right place to ask. Didn't find better!

I am trying to add external/libjpeg into cwm bootable/recovery/minui

If I try the basic way (include the library in bootable/recovery/minui/Android.mk), I always get linker errors:

undefined reference to 'jpeg_std_error'
undefined reference to 'jpeg_CreateDecompress'
...

Looking deeper, the static libraries on which rely minui are declared in bootable/recovery/Android.mk

LOCAL_STATIC_LIBRARIES += libminui libpixelflinger_static libpng libcutils liblog

Any help how to modify cm sources to be able to link against libjpeg_static when declared in bootable/recovery/Android.mk ?

If I just do that, obviously it doesn't work

I even tried to copy whole libjpeg folder inside bootable/recovery/libjpeg and directly compile the libjpeg in bootable/recovery/minui/Android.mk, I still get the linker errors

So, I am just looking how cm source works to link these libpixelflinger_static and libpng so that I do the same with libjpeg_static

Many thanks

If you need teh actual sources, let me know. They will be open source obviously once done
[Nexus 7 Android Development] fattire:
New build

Quick heads up... There's a 4.4 build KRT16S now, which doesn't seem to have anything new in the device for N7, but there may be new blobs. See here. I can't do a comparison at the moment (not at home) on a file-by-file basis, but figured I'd mention it if anyone's doing a build..

Update: Did a diff -r of the directories. Doesn't look like any of the grouper binaries are new. Carry on.

Update #2: There were some kernel commits so I'm merging them in and they should appear in the official cm repo as soon as I confirm it works.
[Nexus 7 Android Development] sparksco:
I know I've said this before, but I have a whole guide on Java here on xda... Just go to my profile and you'll find it..
[Nexus 7 Android Development] underwaterjr:
Funny you would say that. I use you posts for java all the time. They are great write ups. I had java 6 set as default and in my bash. But still no go. So I had to rip out java completely and just install java 6 using your guide. I've been using oab to update java but it is not working for java 6 on my machine for some reason.
[Nexus 7 Android Development] solonix:
I have this error

target thumb C: libSR_AudioIn <= external/srec/audio/AudioIn/UNIX/src/audioin.c
make: *** [/mnt/cm/system/out/target/product/grouper/obj/SHARED_LIBRARIES/keystore.grouper_intermediates/keymaster_grouper.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** wait: No child processes. Stop.
[Nexus 7 Android Development] AndDiSa:
Missing grouper binaries?
[Nexus 7 Android Development] solonix:
I download and extract all binaries, but I'll try to download them again
[Nexus 7 Android Development] solonix:
earned through this link

https://groups.google.com/forum/#!msg/android-building/b66T0PzDIiM/dm_THa2GM4YJ
[Nexus 7 Android Development] MaceBewley:
Hmmmmm....

Built without any errors, but won't boot past the Google splash screen. Thoughts would be appreciated...
[Nexus 7 Android Development] fattire:
missing grouper binaries?
[Nexus 7 Android Development] bhu1:
Anybody know where I can find an unofficial build of cm11 from today or yesterday?
[Nexus 7 Android Development] MaceBewley:
Thinking it could be, was syncing them from The Muppets when building 10.2.

ETA Went ahead an DL'd the blobs. After extracting the .sh files each gives me *******.sh command not found?!?!
[Nexus 7 Android Development] fattire:
You might need to put a "./" in front of the command, to let the computer know that you want to run the file in the current directory (. means current directory, .. means parent directory), a la ./extract-whatever.sh
[Nexus 7 Android Development] fattire:
You can also try sh whatever.sh or bash whatever.sh
[Nexus 7 Android Development] MaceBewley:
Embarrassed to say, I knew that and FORGOT that!! Guess I should stay away from the Scotch while building.....
[Nexus 7 Android Development] fattire:
What are you talking about? That's what makes it a challenge! :good:

____
| |
| |
|____|
| |
( )
) (
.' `.
/ \
|------------|
|JACK DANIELS|
| ---- |
| (No.7) |
| ---- |
| Tennessee |
| WHISKEY |
| 40% Vol. |
|------------|
|____________|

courtesy here.
[Nexus 7 Android Development] sparksco:
Haha that link is awesome, bookmarked.
[Nexus 7 Android Development] sparksco:
Just so you guys know Sun java Oracle decided not to support java 6 anymore and removed all the DL links! But Google still requires it in 4.4 kk?!?!

I have a mirror here if anyone needs it.

https://drive.google.com/file/d/0Bxk7Dj4w1Ib8U3p3d0JiWnp5anc/edit?usp=sharing
[Nexus 7 Android Development] dexviajiboy:
http://d-h.st/search?search_by=1&search_for=grouper
[Nexus 7 Android Development] fattire:
Ooo new build has a bootanim refresh!

Simple.
[Nexus 7 Android Development] webdroidmt:
@fattire

Regarding the broken native OTG usb issue, I think I found something that could be useful. It's a patch to fix OTG on the HTC dlx but maybe more relevant to the N7, one of the code review commenters (Christopher Palmer) pointed to what he believes to be the commit that broke it by changing the vold mount directory. I'm hoping this might also apply to the N7.

Here's the patch with his comment: http://review.cyanogenmod.org/#/c/54461/

Here's the possible offending commit: http://review.cyanogenmod.org/#/c/53366/

P.S. I do like the new CM bootanim. :D

Thanks,

MikeT
[Nexus 7 Android Development] jgramkow:
I have looked and looked for how to do this. Can someone point me in the right direction?
[Nexus 7 Android Development] Zeljko1234:
After hours of building I got:

....
Copying resources from program jar [/home/zeljko/android/system/out/target/common/obj/APPS/Calendar_intermediates/classes.jar]
target Dex: Camera2
target Dex: DSPManager
target Dex: DeskClock
target Static Jar: com.android.emailsync (/home/zeljko/android/system/out/target/common/obj/JAVA_LIBRARIES/com.android.emailsync_intermediates/javalib.jar)
target Dex: Gallery2
collect2: error: ld terminated with signal 9 [Killed]
make: *** [/home/zeljko/android/system/out/target/product/grouper/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1
make: *** Waiting for unfinished jobs....

Any suggestion is welcome :)
[Nexus 7 Android Development] fattire:
Did you possibly run out of hard drive space? Not enough in that clip to fully go off of.

As for the binaries, you just down load the files and run the installers inside.
[Nexus 7 Android Development] Zeljko1234:
Still have about 11 GB left :confused:

I use the same old laptop as for kernel building.
[Nexus 7 Android Development] AndDiSa:
The error message is saying 'killed by signal 9', I.e. sigkill, I.e something / someone has killed the process ...
[Nexus 7 Android Development] fattire:
Yeah.. i thought it could have been the result of running out of space, guess not...

BTW, if you're experiencing some breakage today, it's because someone checked in a commit that breaks the build and hasn't fixed it yet. Should be fixed soon, but for those building for the first time, I don't want them to think they did something wrong.
[Nexus 7 Android Development] J.Abaraxas:
Any word on when pie and expanded desktop will be back?
[Nexus 7 Android Development] Zeljko1234:
Finally successfully made my build. For some reason all building finished but script did make flashable zip so I made it manually.

http://pastebin.com/VQ71VMmb

Any idea what went wrong?

P.S.

Thank you fattire and everyone who contributed to this topic.
[Nexus 7 Android Development] fattire:
Congrats.. did it work for ya? Does it die every time it gets to /home/zeljko/android/system/out/target/product/grouper/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so ?

maybe try

rm -rf /home/zeljko/android/system/out/target/product/grouper/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates

and rebuild?

Anyway, glad it works... make sure the browser works tho :)
[Nexus 7 Android Development] MaceBewley:
Mine errors out at this place, but only on a second build using cache .... (Toro don't) I can clobber and it builds fine.

Just assumed it was due to CM11 being very alpha and changes in the code being merged.
[Nexus 7 Android Development] fattire:
You can clear out your ccache with

ccache -C

I think. (check ccache --help or the manpage if that's not it)
[Nexus 7 Android Development] Zeljko1234:
Thank you for help. I tried what you suggested and takes hours (slow test laptop) to build again and got the same or similar error at the end.

http://pastebin.com/LYZtp8i1

Is it something in CM repository broken or on my machine? Should I try to sync new changes?
[Nexus 7 Android Development] fattire:
The error is here:

Modifying ramdisk contents...

cp: cannot stat `/home/zeljko/android/system/out/target/product/grouper/root/init.recovery.*.rc': No such file or directory

Did you replace the recovery folder, perhaps trying to build twrp or something?