Database Users

anyone know how to build from aosp?

im trying to learn how to build i am a complete noob to linux but i learn quick already installed ubuntu 11.04 and have jdk 5 already installed for froyo as i would like to make a 100% working froyo build. the repo sync is still running and after that i am installing sdk for linux i just need a starting point to making the roms and kernels into a flashable.zip and other pointers that would be helpful. any advice is welcomed thanks in advance
host Executable: acp (out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp)
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.5.2/libstdc++.so when searching for -lstdc++
/usr/bin/ld: skipping incompatible /usr/lib/x86_64-linux-gnu/gcc/x86_64-linux-gnu/4.5.2/libstdc++.a when searching for -lstdc++
/usr/bin/ld: cannot find -lstdc++
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/acp_intermediates/acp] Error 1
i get this error when trying to "make"
fixed it have to use this sudo apt-get install gcc-multilib g++-multilib zlib1g-dev lib32z1-dev lib32ncurses5-dev gperf
compiling now

skater4690 said:
all the stuff you said...
Click to expand...
Click to collapse
You're trying to build an aosp rom for the vibrant with 2.2 code? You do know there's a reason we don't have a build like that, correct?
The closest aosp 2.2 we got was CM6 partially functioning. Besides, gingerbread is what people want.
Sent from my SGH-T959 using XDA App

geoffcorey said:
You're trying to build an aosp rom for the vibrant with 2.2 code? You do know there's a reason we don't have a build like that, correct?
The closest aosp 2.2 we got was CM6 partially functioning. Besides, gingerbread is what people want.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yes that's what I'm gonna try to do whether everyone wants gb doesn't matter to me I'm doing it for myself and to learn

This is a great reference that got me started. A lot of basics are covered in rom building, and it might answer some questions you don't even know you have yet.
Good luck.
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html

Br1cK'd said:
This is a great reference that got me started. A lot of basics are covered in rom building, and it might answer some questions you don't even know you have yet.
Good luck.
http://forum.androidcentral.com/hacking/6037-general-rom-faq.html
Click to expand...
Click to collapse
Thanks ill take a look at it when I get home I have a 15 page guide lol but ill look through that too never too much info

You might want to start with the CM7 source. Far as I know, that's the most stable code tree you can find for the Vibrant - the raw AOSP code will not work out of the box.
Starting from 2.2 AOSP you won't even know if it's a missing driver, bad compile, bug you introduced, bad build environment, etc when it doesn't work. Start with something that does work, and you can learn and try things out in a more controlled environment.

Saiboogu said:
You might want to start with the CM7 source. Far as I know, that's the most stable code tree you can find for the Vibrant - the raw AOSP code will not work out of the box.
Starting from 2.2 AOSP you won't even know if it's a missing driver, bad compile, bug you introduced, bad build environment, etc when it doesn't work. Start with something that does work, and you can learn and try things out in a more controlled environment.
Click to expand...
Click to collapse
Well I wanted to do a froyo build and I don't think there was much for cm6 on the vibrant
But if you wanna toss me a link for cm6 then ill give that a shot
Side note this is my 666 post lol

skater4690 said:
Well I wanted to do a froyo build and I don't think there was much for cm6 on the vibrant
But if you wanna toss me a link for cm6 then ill give that a shot
Side note this is my 666 post lol
Click to expand...
Click to collapse
I suggested CM7 because it works. Don't think CM6 ever did, very well, so it doesn't really tie in with my suggestion to start from a functional build..
Here's CM7 code checkout and build instructions: http://cmsgs.com/mediawiki/index.php?title=Building_and_Installing_Gingerbread_from_Source_vibrant
I can't find the CM6 code in my quick search, sorry.

Saiboogu said:
I suggested CM7 because it works. Don't think CM6 ever did, very well, so it doesn't really tie in with my suggestion to start from a functional build..
Here's CM7 code checkout and build instructions: http://cmsgs.com/mediawiki/index.php?title=Building_and_Installing_Gingerbread_from_Source_vibrant
I can't find the CM6 code in my quick search, sorry.
Click to expand...
Click to collapse
Its cool Eugene has a nice cm6 rom but its not finished ill ask whoever made a aosp froyo rom for the fascinate for some pointers and cant do gb cause I set my jdk for froyo which uses jdk 5 I'm trying to learn everything all at once lol Linux and building Roms lol I'm familiar with how android works system files and such just needs tobhurry up so I can get out of work and get on doing some things

If you are trying to build a 100% working AOSP ROM for the vibrant you are waiting your time. Without source code for the drivers is not possible. Unless you know somebody that works in the development team in Samsung that can give you access to the source code you are out of luck...If you just want to mess around to learn then go for it...

[Q] Does anyone have procrank compiled for the DZ?

I'm looking to get a better handle on process memory usage on my phone. The included tools with the Virtuous Unity ROM don't cut it. I see there is a Google-supplied utility called "procrank" that can be compiled from source, and will report accurate and useful memory stats. Trouble is, I don't know how to cross-compile ARM binaries. Do any of the developers here have a procrank binary built for the DZ/G2 they could send me?
I've done a search on "procrank" here, and apparently there is only a single post on all of XDA. It is someone else asking for the binary too, and they never received an answer. The source is in /system/extras/procrank/. Some more info:
http://elinux.org/Android_Memory_Usage#procrank

Come on man..you've been a member since last year and you still don't know the rules? This is a section for devs to share their work, not a section to ask post questions..that's why there is a section called Q&A..question & answer
Sent from my HTC Desire Z using XDA Premium App

No, the rules say this is the forum about Android development, of which ROM development is a subset, but I imagine discussion about development tools is also valid. procrank is an Android development tool. The Q&A forum is for users asking why they can't change the green LED on their phone to show blue. I'm not confident the folks who tend to check there will know what "procrank" is, and would probably pronounce it "pro-crank" and not "proc-rank".
However, if the mods feel this question is better suited to a wider audience, then I will follow along.

On a whim, I checked the Desire Z CM7 nightlies, and those extra utilities are compiled and included. Just had to extract /system/xbin/procrank and /system/lib/libpagemap.so to the DZ, and away I go.

http://db.tt/s19W09j
You should already have it in /system/xbin depending on your rom...

amazinglarry311 said:
You should already have it in /system/xbin depending on your rom...
Click to expand...
Click to collapse
Yeah, I remember having rsync, tcpdump, etc. using CM-based ROMs on my HTC Hero, but I lost that when I switched to Virtuous Unity on the DZ. That's what made me peek into the CM7 zip. One more thing to add to my prep.sh install tweaking script...

[DEV] Sense 3.5 Development

So after all these threads regarding Sense 3.5 which none worked out in a solution to having this rom stable and resized for our device i started fixing it all by myself because i want this on my phone so much. Anyone who would actually help me in resizing the rom and fixing any issues or providing logcats and stuff and be interested in the development of Sense 3.5 pm me. Development may take a lot of time but we don't have to hurry. Im not saying that i will be the one to fix it immediately, this is just an attempt.
This is the most functional rom http://forum.xda-developers.com/showthread.php?t=1564495

Why not submit the idea to TeamBuzz? I'm sure we could organize roles for developers in TeamBuzz to do something with Sense 3.5

Nice idea Justice, I can help with logcat and resizing, however i have no idea in how to fix gps,bt and wifi
@rayven18 can you provide a link of the most functional sense 3.5 rom for buzz, a list of what needs resizing, what fc and things that doesn't work?
Thanks in advance

Here it is http://forum.xda-developers.com/showthread.php?t=1564495 This is currently the most functional sense 3 rom. It boots and you can work on it. The bugs i know is the ones mentioned in the original thread (framework-res and com.htc.resources need resizing, gps and some services dont function) Because its based on Android Gingerbread 2.3.5, we can experiment with replacing libs and baksmaling services.jar and framework.jar and replace the code with the one from a cm rom that might make the gps and other things work just fine

Lol, 1st i will say good luck.
Now please dont take this as a nasty post but it did make me laugh..... You say " after all these threads regarding sense 3.5..... " and now youve just made another one.
Seriously though goodluck with any developments.
Regards slym.

slymobi said:
Lol, 1st i will say good luck.
Now please dont take this as a nasty post but it did make me laugh..... You say " after all these threads regarding sense 3.5..... " and now youve just made another one.
Seriously though goodluck with any developments.
Regards slym.
Click to expand...
Click to collapse
Hahaha its ok, i actually wanted to mean after all the threads that failed to develop this rom, lets fail again Just kidding, its a nice rom to try and will help me be a better dev

I will try fixing the gps. Downloading rom now.
Sent from my LG-E730 using Tapatalk 2

.xxx. said:
I will try fixing the gps. Downloading rom now.
Sent from my LG-E730 using Tapatalk 2
Click to expand...
Click to collapse
Cool

Thanks for shareing !!!
Justice™ said:
Why not submit the idea to TeamBuzz? I'm sure we could organize roles for developers in TeamBuzz to do something with Sense 3.5
Click to expand...
Click to collapse

[Q] kernel source

Hi! I would like to try myself in kernel development for MT4G. Where can I download the source code (3.0.X.) ? So far I've found on git 2.6.35 and samsung-kernel-msm7x30-ics-3.0 ... But I not sure if it's compatible... Any help will be appreciated! Thanx

Github.com/THEindian/glacier_kernel

http://github.com/elginsk8r/android_kernel_htc_msm7x30-common

elginsk8r said:
http://github.com/elginsk8r/android_kernel_htc_msm7x30-common
Click to expand...
Click to collapse
WOW. Your back!

thanx
Thanx i'll give it a try!!!!
:victory:

.config
Hi. tried to compile one of the kernel sources with a few light changes - i'm getting an error (drivers related..) from make... Maybe I'm using a wrong config file? Which default config file is preferred???Thanx

error details
make[3]: *** No rule to make target `drivers/input/keyboard/pmic8058-keypad.o', needed by `drivers/input/keyboard/built-in.o'. Stop.
make[2]: *** [drivers/input/keyboard] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2
theese are my bugs... help plz!!!

whose kernel are you using?

kernel
i'm using android_kernel_htc_msm7x30-common-jellybean from the link upstairs

themenucha said:
i'm using android_kernel_htc_msm7x30-common-jellybean from the link upstairs
Click to expand...
Click to collapse
I'm no expert on kernel compiling but I have run into problems depending on the toolchain used. For 3.0 kernel I used the Linaro 4.6.2 toolchain from this thread http://forum.xda-developers.com/showthread.php?t=1748297
Cheers

toolchain
well i guess i used the wrong toolchain. (4.3.3)
thanx

Cool, hopefully you can get something running. I have used the 4.3.3 toolchain for GB kernel builds without errors. Good luck!!
Sent from my HTC Glacier using xda premium

Thats a little old. I think linaro is on the 4.8 toolchain, i use 4.7.3 to compile my kernels. I would link you to the source i actually just use the toolchains from the CFX source. Also, i made a kernel compiling script (cause i am lazy ) so i don't really remember where the toolchain is lol

2.6.X.X
So far successfully compiled 2.6.x.x kernel using 4.4.3 toolchain and stock GB kernel from HTCdev site. For training purpose only. Dont have a GB rom to test but it should work. I'll try to compile 3.0.x.x kernel later with a new toolchail. Which one is preferred 4.7 or 4.8?thanx

src
romuloxiii said:
Cool, hopefully you can get something running. I have used the 4.3.3 toolchain for GB kernel builds without errors. Good luck!!
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Hi! plz link me to the source!!!!

themenucha said:
Hi! plz link me to the source!!!!
Click to expand...
Click to collapse
Hi, I use the CyanogenMod repo for the kernel source. I've been building and tinkering with the kernel for a couple of months now (when time permits) and I've had good luck with it. Here is a link for CM Kernel that is compatible with our device: https://github.com/CyanogenMod/htc-kernel-msm7x30
I hope it helps

Am I understanding correctly that I just need to go to the Linaro site here and download the latest release under the 'toolchain build' tab (currently version 4.8) if I want to mess around with compiling a kernel? Confused by some of the other tabs and links on there.
Also, for the record, is this the only source you'd need to build the most current Glacier 3.0+ based kernel https://github.com/Evervolv/android_kernel_htc_msm7x30-3.0.git?
Looking forward to catastrophic failure and the potential melting of my Glacier...
EDIT: answered my own questions. Yes and yes.

[BUILD] [AOKP] [AOSP] [CM] [4.2.2] Discussion Thread [N7000] [JB]

Hey Guys [(Toxic and Rey), and Others] ,
I myself love to learn new things. So couldn't stop from making this thread for your discussion on building AOKP, AOSP, etc. that you want to discuss upon. You can also do that by PMing each other. But we would be missing some crazy interesting stuff. Also we can have others' suggestions. That's why I created the thread. Please use it if you like.
Thanks for sharing your knowledge in advance.

I think you should better discuss with chasmodo, and request him to see if he would allow to have these discussions in his thread. Building AOKP is not different from building CM, no other rom is for that matter.
But as i say, you'll have to request chasmodo. No use having different threads regarding the same thing.

toxicthunder said:
I think you should better discuss with chasmodo, and request him to see if he would allow to have these discussions in his thread. Building AOKP is not different from building CM, no other rom is for that matter.
But as i say, you'll have to request chasmodo. No use having different threads regarding the same thing.
Click to expand...
Click to collapse
Yeah that sure makes sense. But building AOKP isnt as smooth as building CM for the time being. And we will face many errors too. And Chasmodo already said that he didn't like the CM building thread getting heaped up with AOKP build errors. And also we can discuss anything related to building here whether it's CM or AOKP. Let that thread be a guide because most will not face any error while building CM according to Chasmodo's guide. Anyway I'll request him. Let's see what he says.

I like the idea of a separate AOKP compiling discussion thread so I'm gonna go ahead and make use of this thread while its here :good: I have a feeling Chas would approve of us keeping AOKP discussion here. Just gonna repost what I did in Chas' thread and see if anyone has any ideas...
target thumb C++: librecovery_ui_manta <= device/samsung/manta/recovery/recovery_ui.cpp
device/samsung/manta/recovery/recovery_ui.cpp:23:20: fatal error: device.h: No such file or directory
compilation terminated.
To me the error itself here seems irreverent, the fact that its pulling from the manta device tree is what I don't understand. I'm out for the rest of the day today but tonight I'm gonna have another shot at it and see if I cant figure this out.

Re: [BUILD] [AOKP] [4.2.2] Discussion Thread [N7000] [JB]
Need more of the log.
Sent from my GT-N7000 using xda premium

Re: [BUILD] [AOKP] [4.2.2] Discussion Thread [N7000] [JB]
toxicthunder said:
Need more of the log.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I'm about to be home, toxic, I'll post it then
Sent from my GT-N7000 using XDA Premium HD app

target Executable: valgrind (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/valgrind_intermediates/LINKED/valgrind)
target Symbolic: valgrind (/home/supabaws/aokp_jb/out/target/product/n7000/symbols/system/bin/valgrind)
target Strip: valgrind (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/valgrind_intermediates/valgrind)
target StaticExecutable: verifier_test (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/verifier_test_intermediates/LINKED/verifier_test)
target Symbolic: verifier_test (/home/supabaws/aokp_jb/out/target/product/n7000/symbols/system/bin/verifier_test)
target Strip: verifier_test (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/verifier_test_intermediates/verifier_test)
target Executable: vfp-crasher (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/vfp-crasher_intermediates/LINKED/vfp-crasher)
target Symbolic: vfp-crasher (/home/supabaws/aokp_jb/out/target/product/n7000/symbols/system/xbin/vfp-crasher)
target Strip: vfp-crasher (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/vfp-crasher_intermediates/vfp-crasher)
target Executable: webrtc_apm_process_test (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/webrtc_apm_process_test_intermediates/LINKED/webrtc_apm_process_test)
target Symbolic: webrtc_apm_process_test (/home/supabaws/aokp_jb/out/target/product/n7000/symbols/data/nativetest/webrtc_apm_process_test/webrtc_apm_process_test)
target Strip: webrtc_apm_process_test (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/webrtc_apm_process_test_intermediates/webrtc_apm_process_test)
target Executable: webrtc_apm_unit_test (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/webrtc_apm_unit_test_intermediates/LINKED/webrtc_apm_unit_test)
target Symbolic: webrtc_apm_unit_test (/home/supabaws/aokp_jb/out/target/product/n7000/symbols/data/nativetest/webrtc_apm_unit_test/webrtc_apm_unit_test)
target Strip: webrtc_apm_unit_test (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/webrtc_apm_unit_test_intermediates/webrtc_apm_unit_test)
target Executable: wifiLoadScanAssoc (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/wifiLoadScanAssoc_intermediates/LINKED/wifiLoadScanAssoc)
target Symbolic: wifiLoadScanAssoc (/home/supabaws/aokp_jb/out/target/product/n7000/symbols/data/nativestresstest/wifiLoadScanAssoc)
target Strip: wifiLoadScanAssoc (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/wifiLoadScanAssoc_intermediates/wifiLoadScanAssoc)
target Executable: xaVideoDecoderCapabilities (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/xaVideoDecoderCapabilities_intermediates/LINKED/xaVideoDecoderCapabilities)
target Symbolic: xaVideoDecoderCapabilities (/home/supabaws/aokp_jb/out/target/product/n7000/symbols/system/bin/xaVideoDecoderCapabilities)
target Strip: xaVideoDecoderCapabilities (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/xaVideoDecoderCapabilities_intermediates/xaVideoDecoderCapabilities)
target Executable: xaplay (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/xaplay_intermediates/LINKED/xaplay)
target Symbolic: xaplay (/home/supabaws/aokp_jb/out/target/product/n7000/symbols/system/bin/xaplay)
target Strip: xaplay (/home/supabaws/aokp_jb/out/target/product/n7000/obj/EXECUTABLES/xaplay_intermediates/xaplay)
target thumb C++: librecovery_ui_manta <= device/samsung/manta/recovery/recovery_ui.cpp
device/samsung/manta/recovery/recovery_ui.cpp:23:20: fatal error: device.h: No such file or directory
compilation terminated.
There ya go buddy.. I dont see anything of use but that could just be my untrained eye. I just dont undertand what I would need to edit to make it pull from the galaxys2_common device tree (I assume thats where the all files regarding recovery would be) instead of the manta tree.

compare your BoardCommonConfig file with that from CM ..

toxicthunder said:
compare your BoardCommonConfig file with that from CM ..
Click to expand...
Click to collapse
Already did. In fact, I copied most of the cm 10.1 n7000 tree and just edited what I needed to. I'll look a lil deeper, I probably just missed something.

Thanks for using the thread guys. As soon as my exam ends (10th standard board's Exam) I will also get started with AOSP (if possible) and AOKP. I have always wanted to build a pure AOSP rom for our Note but faced quite a number of errors last time. So I'll join you after 6th of March. Till then best of luck with AOKP. :laugh: :good:

Re: [BUILD] [AOKP] [4.2.2] Discussion Thread [N7000] [JB]
CosmoDroid said:
Thanks for using the thread guys. As soon as my exam ends (10th standard board's Exam) I will also get started with AOSP (if possible) and AOKP. I have always wanted to build a pure AOSP rom for our Note but faced quite a number of errors last time. So I'll join you after 6th of March. Till then best of luck with AOKP. :laugh: :good:
Click to expand...
Click to collapse
I look forward to it buddy. It seems like I'm the only one trying to get pure aokp to compile (with the help of toxic of course) other than sixstringsg. It seems like by the time I get it to compile though six string will have already updated the n7000 to 4.2.2 lol. But hey its a learning experience and I've always wanted to give something back to the community. Huge thanks to toxic though, for all the help he's providing :good:
Sent from my GT-N7000 using XDA Premium HD app

Re: [BUILD] [AOKP] [4.2.2] Discussion Thread [N7000] [JB]
CosmoDroid said:
Thanks for using the thread guys. As soon as my exam ends (10th standard board's Exam) I will also get started with AOSP (if possible) and AOKP. I have always wanted to build a pure AOSP rom for our Note but faced quite a number of errors last time. So I'll join you after 6th of March. Till then best of luck with AOKP. :laugh: :good:
Click to expand...
Click to collapse
All the best for your boards
Pay more attention there and not here...
Sent from my GT-N7000 using xda premium

Exam time. I can't spend much time till mid-June on learning Linux and building AOSP/CM.
But I'll keep an eye on this thread.
Life sucks : March-April B Com II exam. I did not attend previous semester so I have to put in mammoths' efforts. May-June Russian language exam and CA CPT.

Re: [BUILD] [AOKP] [4.2.2] Discussion Thread [N7000] [JB]
CosmoDroid said:
Thanks for using the thread guys. As soon as my exam ends (10th standard board's Exam) I will also get started with AOSP (if possible) and AOKP. I have always wanted to build a pure AOSP rom for our Note but faced quite a number of errors last time. So I'll join you after 6th of March. Till then best of luck with AOKP. :laugh: :good:
Click to expand...
Click to collapse
For a 10th standard guy you got a Note... . Good luck with your exams kid....

Re: [BUILD] [AOKP] [4.2.2] Discussion Thread [N7000] [JB]
Galaxtus said:
For a 10th standard guy you got a Note... . Good luck with your exams kid....
Click to expand...
Click to collapse
I had to make do with 1-rupee coins for making calls from the coin-box unit at our school
Sent from my GT-N7000 using xda premium

Galaxtus said:
For a 10th standard guy you got a Note... . Good luck with your exams kid....
Click to expand...
Click to collapse
toxicthunder said:
I had to make do with 1-rupee coins for making calls from the coin-box unit at our school
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
LOL yeah. And toxic I'm being frustrated with so much to study especially the non-science subjects. hehe. Moving quite off-topic now. Thanks and best of luck. :laugh:
Edit: And I also have to do with Payphones at our school. Mobile phones not allowed.

I'm building AOKP for grouper and after the last repo sync there was no Kernel Folder in the device tree any more. At Github I found that
github.com/AOKP/platform_manifest
Now I can't find the place where to put this manual manifest to get the kernel folder.

vet-note said:
I'm building AOKP for grouper and after the last repo sync there was no Kernel Folder in the device tree any more. At Github I found that
github.com/AOKP/platform_manifest
Now I can't find the place where to put this manual manifest to get the kernel folder.
Click to expand...
Click to collapse
Open Gedit and paste the code found at https://github.com/AOKP/platform_manifest/blob/jb-mr1/manual_add_kernel_manifest.sh .
Save it as kernel.sh or kernel_manifest.sh or whatever.sh in the root of your AOKP folder. Start the terminal, navigate to your AOKP folder and do
Code:
chmod a+x whatever.sh
After that, type
Code:
./whatever.sh
and everything should happen automagically.

Now I'm getting that error:
[email protected]:~/aokp$ chmod a+x kernel.sh
[email protected]:~/aokp$ ./kernel.sh
adding kernel repos to your build tree
syncing kernel repos
including device/asus/grouper/vendorsetup.sh
including device/asus/tilapia/vendorsetup.sh
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/generic/mips/vendorsetup.sh
including device/generic/x86/vendorsetup.sh
including device/lge/mako/vendorsetup.sh
including device/samsung/maguro/vendorsetup.sh
including device/samsung/manta/vendorsetup.sh
including device/samsung/toro/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/aokp/vendorsetup.sh
including sdk/bash_completion/adb.bash
error: project kernel/acer/t30 not found
kernel/acer/t30 synced successfully
error: project kernel/asus/grouper not found
kernel/asus/grouper synced successfully
error: project kernel/asus/tf101 not found
kernel/asus/tf101 synced successfully
error: project kernel/htc/msm8960 not found
kernel/htc/msm8960 synced successfully
error: project kernel/lge/mako not found
kernel/lge/mako synced successfully
error: project kernel/motorola/omap4-common not found
kernel/motorola/omap4-common synced successfully
error: project kernel/motorola/omap4-kexec-common not found
kernel/motorola/omap4-kexec-common synced successfully
error: project kernel/samsung/aries not found
kernel/samsung/aries synced successfully
error: project kernel/samsung/d2 not found
kernel/samsung/d2 synced successfully
error: project kernel/samsung/manta not found
kernel/samsung/manta synced successfully
error: project kernel/samsung/msm8660-common not found
kernel/samsung/msm8660-common synced successfully
error: project kernel/samsung/smdk4210 not found
kernel/samsung/smdk4210 synced successfully
error: project kernel/samsung/smdk4412 not found
kernel/samsung/smdk4412 synced successfully
error: project kernel/samsung/t1 not found
kernel/samsung/t1 synced successfully
error: project kernel/samsung/tuna not found
kernel/samsung/tuna synced successfully

vet-note said:
Now I'm getting that error:
[email protected]:~/aokp$ chmod a+x kernel.sh
[email protected]:~/aokp$ ./kernel.sh
adding kernel repos to your build tree
syncing kernel repos
Click to expand...
Click to collapse
That means that either their script or their repo is a bit messy.
Do you have a /kernel/asus/grouper now?