yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] TheDarkDefender:
awesome. appreciate the quick response :good:
[Nexus 7 Android Development] :
well...another ultimate failure my os crashed for unknown reasons and honestly...im tired of messing with linux.after 10.10 they went to crap.linux sucks hard nowadays.oh well no os building for me.
[Nexus 7 Android Development] TheDarkDefender:
errors after using Muppets.

I find it similar to the previous error i had.
[Nexus 7 Android Development] #define:
You need all the proprietary repos.. Not just asus.. Nvidia, elan, invensense, widevine, etc..
[Nexus 7 Android Development] TheDarkDefender:
Oh, list them please?
[Nexus 7 Android Development] #define:
Elan, invensense, broadcom, nxp, nvidia, widevine, and asus..
[Nexus 7 Android Development] underwaterjr:
If your trying to build 10.2 I don't think the blobs have been updated yet on TheMuppets for 4.3 yet. If I'm wrong about that, someone with more knowledge please chime in.
[Nexus 7 Android Development] #define:
I saw a 10.2 branch on the muppets asus repo..
[Nexus 7 Android Development] sparksco:
There's a new branch cm-10.2 on the muppets, but nothing for grouper has been updated. This is where things get confusing. Have the blobs been updated for 4.3 or is it using the same old blobs that were in 4.2? And yes I know we need widevine elan ect also.

https://github.com/TheMuppets/proprietary_vendor_asus/tree/cm-10.2
[Nexus 7 Android Development] baggus:
Why can't you just simply download them from here: https://developers.google.com/android/nexus/drivers#grouperjwr66v ? And yes, those for JWR66V work fine with JSS15J also. Tested by myself.
[Nexus 7 Android Development] fattire:
I think dhacker29 submitted a pull request for the blobs, so you might try those. (Incidentally, once those blobs are accepted, that's all that's holding back the nightlies..)
[Nexus 7 Android Development] AlienSr1:
Yep, they work fine :).
[Nexus 7 Android Development] DJLamontagneIII:
Grouper 4.3 binaries are not merged yet there's still a open pull request for them by dhacker29 https://github.com/TheMuppets/proprietary_vendor_asus/pull/41

Edit should have hit refresh lol
[Nexus 7 Android Development] sparksco:
So I'm guessing only certain people have push access to those repos...
[Nexus 7 Android Development] :
Haha one more attempt, hopefully my is don't crash again
[Nexus 7 Android Development] fattire:
That's right... they have been accepted now however...
[Nexus 7 Android Development] :
i keep experiencing the freeze at 99% when downloading the latinime packages??
[Nexus 7 Android Development] :
it keeps freezing at 99% its only at 41% of receiving objects. wth is going on?
[Nexus 7 Android Development] :
this is whats going on right here:
[Nexus 7 Android Development] alershka:
Noobish type question...

At 1am this morning. I repo sync'd and then built. I created a quick shell script Wednesday to automate this, so I ran the script then went to bed.

When I woke up, I flashed the zip, which was dated with today's date. The build prop shows the CM version as yesterday and the build date as the day before.

So I am wondering what happened.

Is it that there were no significant changes in commits from when I tested the shell script two days ago so it built a newly dated file with the same contents?

Is it possible that during the repo sync it didn't connect?

I am hoping to automate this further using cron but I had no success with that when I tried. I did a chmod 755 but it didn't run on time. I guess I need to get some sort of error reporting.

Thanks.
[Nexus 7 Android Development] Utacka:
if build.prop is not deleted from /out folder then its just gonna re-use it. I usually run make clobber to clean entire out folder and using ccache to build faster.

if you dont want to clobber then here is a few alternatives:

make installclean

find ./out/ -name 'build.prop' | xargs rm
find ./out/ -name 'cm_*-target_files-eng*.zip' | xargs rm
[Nexus 7 Android Development] alershka:
Thanks! I will add clobber to script and ccache to my .bashrc.
[Nexus 7 Android Development] sparksco:
Probably a temporary issue with github... Github has had a lot of issues as of late. I'm thinking for my own personal repositories to switch to gitorious.org.
[Nexus 7 Android Development] sparksco:
Make clobber to delete the build.prop seems over the top. make installclean works fine for me every time.

Also ccache is only useful on rebuilds, for clean builds it's useless.
[Nexus 7 Android Development] fattire:
Also try http://bitbucket.org...
[Nexus 7 Android Development] sparksco:
Meh. I don't know why but I like the style of https://gitorious.org...
[Nexus 7 Android Development] fattire:
Big Halloween fan maybe?
[Nexus 7 Android Development] sparksco:
Nope, I just like the way it looks... Doesn't look anything like Halloween lulz
[Nexus 7 Android Development] TheDarkDefender:
Haha. Does look Halloween-y. Bitbucket seems better, a lot github-like. The appearance and all. So easier to deal with.

Sent from my Nexus 4
[Nexus 7 Android Development] :
So anyone know of any other git or HTTPS links to get cm10.2 binaries?
[Nexus 7 Android Development] fattire:
settings->about tablet->update cm

if you have 10.1
[Nexus 7 Android Development] sparksco:
I didn't know green, red and orange were Halloween colors. Anyhow, what is so hard to deal with on it? It works just like any other git service does. I suppose I could do some test between the two and see which has the fastest download speeds, but I've never had any issues with gitorious like I have with github..

[MENTION=3041959]fattire[/MENTION] after I merged grouper 4.3, github wouldn't allow me to upload because of large binary files in the device tree. Did you have the same problem? Seems github has new policies on how large binary files can be. Might make it difficult for cm to host some of the repos.
[Nexus 7 Android Development] baggus:
It may be a stupid question, but anyway... How can I exclude default aosp apps from the build tree? I want to get rid of Calendar app and I've searched it in every .mk file in build/ and vendor/cm catalogs, but found nothing. I know I can delete it manually every time from the .zip package, but it's not what I want. Do you have any advise how to track where certain apps/packages are declared to be included in a build?
[Nexus 7 Android Development] fattire:
See http://wiki.cyanogenmod.org/w/Doc:_adding_your_own_app and do the opposite. That is, pull the app from the list of projects to build. That said, don't get rid of any app that is necessary for the os to function...

Additionally you can simply delete the source in project/apps (after removing the project with in your local manifests directory.)

http://wiki.cyanogenmod.org/w/Doc:_Using_local_manifests

See the .repo/manifest.xml file to identify the name and location of the source for the app you want to remove.

In most cases, removing the source won't break anything, but if the build does stop with an error such as "required module X not found",

it'll probably be a line somewhere in a .mk instructing the build system to build the module

. In that case, just remove that line, and cross your fingers that the app you are removing really truly isn't necessary for aosp to run. Btw, the name of the module for each app is usually defined in the Android.mk file in the app's source directory.

Yup.. Not sure why you were re merging aosp, but there are a ton of factory image files plus all those prebuilt kernels in aosp which were hopefully (mostly?) skipped so as not to have an unnecessarily huge repo (cm builds kernels from source) and also because github has binary size restrictions...
[Nexus 7 Android Development] baggus:
So the question is in which .mk file exactly? As I said - I've searched for system apps such as Calendar or QuickSearchBox in all of the .mk files in /build/, vendor/cm and device/asus and found nothing.

I know what the package name is and I know where the source for an app that I want to exclude is located. The problem is which .mk file instructs the build system to include it.
[Nexus 7 Android Development] sparksco:
That's how a lot of cm device maintainers for nexus devices update is by merging from AOSP... You can see it for the Nexus 4

Hence my question if you've also tried merging and had the same issue using github. And also why I'm merging...
[Nexus 7 Android Development] fattire:
So, I've underlined in the post above where you find the name of the module and how to determine which .mk file instructs the build system to include it. Some modules are optional and need to be explicitly told to be built. Other modules will be built and installed if they exist.

In other words, the way the makefile/android build system works, any directory with an Android.mk file is identified and built into a giant build tree which determines dependencies and changed files and such... If the Android.mk says this is an OPTIONAL module, then the project won't be built unless it's explicitly called to be built, as in the PRODUCT_PACKAGES list described in the wiki linked above.

However, for some projects, if you remove them from the source, you're done. They won't build.

In the case of the calendar, located in packages/apps/Calendar, LOCAL_MODULE_TAGS := optional so the module won't be built automatically. That means that it's told to build from somewhere. The name of the module is defined by LOCAL_PACKAGE_NAME := Calendar. So you need to find where it's being told to be built.

If you remove the whole project via your local manifest and try to build, I'm guessing you'll get a build error and the offending package will show itself. That said, check build/target/product/*
[Nexus 7 Android Development] fattire:
yes, but didn't I just answer you? The commits with binary packages have not been merged for the reason described above. They were overwhelming github and making the repo gigantic. Fo rthat reason, grouper has always cherrypicked in the device repo and merged in the kernel repo.
[Nexus 7 Android Development] sparksco:
Yup, I think it's odd I've been able to merge two or three other devices, but grouper always contains those new zips or whatever they put in there that make the repo size too big. I was thinking. Couldn't I just do a merge than before pushing to github I could do git rm -f file, then commit merge along with the fixed conflicts? That would remove the large binary files in the merge right?

Also the kernel binary is less than 10 mb's so I don't think that's really the issue. Github has a limit of 90mb I think. So there must be a zip of factory images somewhere that can be removed in a merge. Might make future updates easier?
[Nexus 7 Android Development] baggus:
Thanks, that helped a lot. I've finally found it and if anyone wonders where - build/target/product/generic_no_telephony.mk
[Nexus 7 Android Development] AlienSr1:
Hello everyone, since there are quite a few devs/contributors in this thread you might be interested in this: http://xdaforums.com/showpost.php?p=44746084pos

It is a post by dev/dev admin pulser_g2 about the current state of CyanogenMod and about its future. I recommend checking it out and maybe also share your opinion on this topic.
[Nexus 7 Android Development] fattire:
Why I didn't see TRIM running...

An interesting thing that might be of interest to developers...

Remember my observation back earlier in this thread that I didn't see any TRIM activity in the logs? Thanks to verygreen, I now think I know why.

Apparently some Nook HDs have been bricking due to a corruption bug in Samsung's emmc driver. Grouper has the same MAG2GA emmc as the Nooks and the Epic 4G I guess- and he was wondering what our firmware was (v05 05/2012) vs theirs (v06 08/2012) .

Since as far as I knew we never patched our emmc driver, but no one is having the issue, he asked to look at the kernel, and found this in our Nexus 7 kernel. Apparently, it's checking the emmc firmware, and if it's the bad one (ie, the version mine has), it just turns TRIM off.

Does everyone here have the same emmc firmware?

adb shell

su

# cd cd /sys/class/block/mmcblk0/device

# cat cid | cut -b 19,20

05

# cat manfid

0x000015

# cat date

05/2012

Anyone with those values I think has TRIM turned off. (talking with hashcode, this patch also apparently is needed for the Kindle HDs as well...) There is a similar but different bug that MAG4FA chips are reporting on devices like the HTC One XL. In any event we've got it, so all 2012 N7s running 10.2 should be good, I think.
[Nexus 7 Android Development] fattire:
Wiki page for the above...

FYI: There's now a wiki page set up for the above. Anyone developing for a device that might be affected should take a look. Note that there are corruption bugs known for numerous Samsung EMMCs, and some devices have been released with emmcs from different vendors...
[Nexus 7 Android Development] sparksco:
mine has a even older date of 04/2012...

Am I affected?
[Nexus 7 Android Development] fattire:
Interesting. Can you cat name? I'm guessing some of the groupers use a different emmc.
[Nexus 7 Android Development] h2on0:
name hwrev fwrev manfid oemid date type serial

mmc08g

0x0

0x0

0x000070

0x0100

05/2012

0x070887d
[Nexus 7 Android Development] Skelli:
root@nexus7:~ ssh# cd /sys/class/block/mmcblk0/device

root@nexus7:/sys/devices/platform/sdhci-tegra.3/mmc_host/mmc0/mmc0:0001 ssh# ls -la

drwxr-xr-x root root 2013-08-20 09:14 block

-r--r--r-- root root 4096 2013-08-20 09:24 cid

-r--r--r-- root root 4096 2013-08-20 09:24 csd

-r--r--r-- root root 4096 2013-08-20 09:24 date

lrwxrwxrwx root root 2013-08-20 09:24 driver -> ../../../../../../bus/mmc/drivers/mmcblk

-r--r--r-- root root 4096 2013-08-20 09:24 enhanced_area_offset

-r--r--r-- root root 4096 2013-08-20 09:24 enhanced_area_size

-r--r--r-- root root 4096 2013-08-20 09:24 erase_size

-r--r--r-- root root 4096 2013-08-20 09:24 fwrev

-r--r--r-- root root 4096 2013-08-20 09:24 hwrev

-r--r--r-- root root 4096 2013-08-20 09:24 manfid

-r--r--r-- root root 4096 2013-08-20 09:24 name

-r--r--r-- root root 4096 2013-08-20 09:24 oemid

drwxr-xr-x root root 2013-08-20 09:14 power

-r--r--r-- root root 4096 2013-08-20 09:24 preferred_erase_size

-r--r--r-- root root 4096 2013-08-20 09:24 prv

-r--r--r-- root root 4096 2013-08-20 09:24 sec_count

-r--r--r-- root root 4096 2013-08-20 09:24 serial

lrwxrwxrwx root root 2013-08-20 09:24 subsystem -> ../../../../../../bus/mmc

-r--r--r-- root root 4096 2013-08-20 09:24 type

-rw-r--r-- root root 4096 2013-08-20 09:14 uevent

root@nexus7:/sys/devices/platform/sdhci-tegra.3/mmc_host/mmc0/mmc0:0001 ssh# cat name

MMC16G

root@nexus7:/sys/devices/platform/sdhci-tegra.3/mmc_host/mmc0/mmc0:0001 ssh# cat cid | cut -b 19,20

08

root@nexus7:/sys/devices/platform/sdhci-tegra.3/mmc_host/mmc0/mmc0:0001 ssh# cat manfid

0x000070

root@nexus7:/sys/devices/platform/sdhci-tegra.3/mmc_host/mmc0/mmc0:0001 ssh# cat date

07/2012
[Nexus 7 Android Development] fattire:
Looks like Toshiba makes mmcs that identify themselves with MMC16G. Looks like a few suppliers for grouper. I bet after a fresh boot with a dmesg you can get more info them.
[Nexus 7 Android Development] Skelli:
Here is the dmesg:

http://pastebin.com/zCMx2YSw
[Nexus 7 Android Development] underwaterjr:
u0_a39@android:/ $ su

root@android:/ # cd /sys/class/block/mmcblk0/device

cd /sys/class/block/mmcblk0/device

root@android:/sys/class/block/mmcblk0/device # cat cid | cut -b 19,20

cat cid | cut -b 19,20

05

root@android:/sys/class/block/mmcblk0/device # cat manfid

cat manfid

0x000015

root@android:/sys/class/block/mmcblk0/device # cat date

cat date

06/2012

root@android:/sys/class/block/mmcblk0/device # cat name

cat name

MAG2GA

When I run this command this is the output so I am assuming trim is working for me.

root@android:/ # logcat -d | grep -i fstrim

logcat -d | grep -i fstrim

I/fstrim ( 142): Starting fstrim work...

I/fstrim ( 142): Invoking FITRIM ioctl on /cache

I/fstrim ( 142): Trimmed 349802496 bytes on /cache

I/fstrim ( 142): Invoking FITRIM ioctl on /data

I/fstrim ( 142): Trimmed 8208535552 bytes on /data

I/fstrim ( 142): Finished fstrim work.

root@android:/ #
[Nexus 7 Android Development] fattire:
Not much info...

4.930440] [mmc]:mmc_read_ext_csd:285 ext_csd.sectors 0x1d80000 prod_name MMC16G BOOT_MULTI 0x10

But looks like its not the Samsung model. I did notice it cleaned up some filesystem stuff when it booted. Did you not have a clean shutdown?
[Nexus 7 Android Development] sparksco:
New screenshot with cat name. Looks like MMC08G for my grouper.
[Nexus 7 Android Development] fattire:
This means all you guys get TRIM. i'm jealous :)
[Nexus 7 Android Development] ikslawlok:
Hello everybody.

I try to build for the first time CM 10.2 with CMAccount

I read and apply Build_for_grouper

and adding_your_own_app (i think)

After doing

croot
brunch grouper

I got this error

What can i do, to resolve my problem(s) ?
[Nexus 7 Android Development] AlienSr1:
First I'd try what it suggests.

Run the brunch command with -Xlint:unchecked

so it should be

brunch grouper -Xlint:unchecked
[Nexus 7 Android Development] underwaterjr:
[MENTION=2394329]sparksco[/MENTION]

Hey I see you have other toolchains in your github. So I add these via local manifest but it I'm guessing it won't build with them unless I point the build at your toolchain. So my question is do I edit envsetup.sh or is it more complicated than that. Oh and if this has been asked a million times I will try a better search if you think I can find the answers that way.

Thanks

edit: I have found some good info with a few better searches, I will see how this goes and maybe bug you again if I can't solve my problems. Thanks
[Nexus 7 Android Development] sparksco:
Just make sure you have my external/oprofile. After that you need to put somewhere TARGET_GCC_VERSION_EXP := 4.8

After that it's just various other repo fixes.
[Nexus 7 Android Development] underwaterjr:
I did those things and ran into a build error pretty early I will do some googling and see what I can come up with.

cc1: all warnings being treated as errors

make: *** [/home/jeremiah/android/system/out/target/product/grouper/obj/STATIC_LIBRARIES/libbt-brcm_gki_intermediates/./ulinux/gki_ulinux.o] Error 1

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

---------- Post added at 10:12 PM ---------- Previous post was at 09:42 PM ----------

Ok so I made the TARGET_GCC_VERSION := 4.8 edit in TARGET_linux-arm.mk file and also changed -Werror to -Wno-error in the cflags of this file to try and get past the errors. If what I'm doing is totally crazy let me know...lol. Anyway just learning and kind of banging my head off the wall in the process.
[Nexus 7 Android Development] ikslawlok:
OK thank you I understand what it said now.

After I posted, I had retry, then I had only this error

Pas de règle pour fabriquer la cible « vendor/asus/grouper/proprietary/btmacreader », nécessaire pour « /home/kowalski/.android/developpement-cyanogenmod/android/system/out/target/product/grouper/obj/EXECUTABLES/btmacreader_intermediates/btmacreader ». Arrêt.
make: *** Attente des tâches non terminées....

Is it a "blob" problem ?

Envoyé depuis mon Nexus 7 en utilisant Tapatalk 4
[Nexus 7 Android Development] AlienSr1:
Yes, I had that problem too. You need to replace the extracted files with the ones from "TheMuppets" github.
[Nexus 7 Android Development] webdroidmt:
I have all the same info as yours on an 8GB N7, ie; manfid, cat date and cat name. My cat name is MMC08G, if you look closely at your attached pic, you'll see that yours is the same and not MMC086. :)

Mike T
[Nexus 7 Android Development] sparksco:
Yuppers I checked again and it's a G and not a 6... We have the OG N7's, the very first ones ever made.
[Nexus 7 Android Development] webdroidmt:
OG but still running well...knocking on wood. ;)

OG= Oldie but Goodie? :D

Mike T
[Nexus 7 Android Development] AndroidSmitty:
I have the same problem too. Where is the "TheMuppets" github and what is the files? Please help me.
[Nexus 7 Android Development] TheDarkDefender:
[MENTION=3041959]fattire[/MENTION]

I heard new binaries dropped in. Should we re download and re run those scripts again? Or wait until cm has merged JSS15Q ?

Sent from my Nexus 4
[Nexus 7 Android Development] fattire:
I looked earlier-- I don't think there are any important changes in the device or kernel relating to this new release which seems more geared for 2013 N7s and issues with GPS/multitouch.

As for the binary blobs, I don't think there's anything new here either. Only the JWR66Y ones. The 2013 N7 has the JSS15Q ones.

BTW-- does anyone want to update the extract-files script and setup-makefiles scripts for 10.2 so that it pulls the files from a 10.2.x factory image?
[Nexus 7 Android Development] sparksco:
Really? I see quite a few "update prebuilt kernel" commits in your link you posted. I'd say the kernel has changed some...

As far as the extract-files script you wrote what is there to update? And aren't you the one while wrote up that whole script in the first place? I'm perfectly fine with using TheMuppets.
[Nexus 7 Android Development] fattire:
You could be right, or building a new kernel and installing it into the device/asus/kernel/ directory as a prebuilt may just be a part of their build process. Did you see anything in the kernel source that's new?

Well, the blobs have changed. I didn't do a side-by-side comparison to see if any new files are there (or old ones eliminated) so thats what I was asking for someone to do-- just to make sure that the blobs it pulls are complete and that the .mk files it creates matches the ones in the official blob tar.gz

Yeah, pretty much. So?

Great. Extracting the files is just another option for those who choose to use it.
[Nexus 7 Android Development] sparksco:
The only thing I see new is the kernel configuration to enable SELinux which of course cm uses their own defconfig. It looks like you already have all of that enabled in the new defconfig. I don't know if it makes a difference but I merged SEAndroid grouper kernel and everything works fine.

Blobs idk I never really used the script. I was making a observation that other people might not be able update the script like you...
[Nexus 7 Android Development] ikslawlok:
Ok thank you i found on Github TheMuppets and past in "/android/system/vendor/"

asus/grouper/

broadcom/grouper/

elan/grouper/

invensense/grouper/

nvidia/grouper/

nxp/grouper/

widevine/grouper/

Now my new error is

target thumb C: bluetooth.default <= external/bluetooth/bluedroid/main/../btif/src/btif_dm.c
external/bluetooth/bluedroid/main/../btif/src/btif_dm.c: In function 'btif_dm_upstreams_evt':
external/bluetooth/bluedroid/main/../btif/src/btif_dm.c:1358:13: error: implicit declaration of function 'btif_storage_remove_ble_bonding_keys' [-Werror=implicit-function-declaration]
cc1: all warnings being treated as errors
make: *** [/home/kowalski/.android/developpement-cyanogenmod/android/system/out/target/product/grouper/obj/SHARED_LIBRARIES/bluetooth.default_intermediates/../btif/src/btif_dm.o] Erreur 1
make: *** Attente des tâches non terminées....
[Nexus 7 Android Development] AlienSr1:
Hm, ok. I only had to copy one folder from TheMuppets, I believe it was "vendor/asus/grouper".

So I run the extraction script as described in the wiki and then only copied this one muppets folder.

You can always try the command "make clean" to delete all files in the "out" directory.

If it doesn't work you will have to ask one of the devs in here, as I don't know exactly what the error means.
[Nexus 7 Android Development] ikslawlok:
Ok, thank you for the command line make clean,

but i had the same error, again :rolleyes:
[Nexus 7 Android Development] AlienSr1:
Did you try to extract the proprietary files from your device and afterwards only replacing "/vendor/asus/grouper"? That's the way I did it.

So go over the wiki process again and before building replace only this one folder.
[Nexus 7 Android Development] ikslawlok:
OK, i will try that

Envoyé depuis mon Nexus 7 en utilisant Tapatalk 4