[DIS][DEV]Android Kernel and Rom Modding for GT-P52xx - Galaxy Tab 3 10.1 Android Development

For the last 2 weeks, a few of us has been working on a project of modding p52XX kernel here,
http://forum.xda-developers.com/showthread.php?p=59379382#post59379382
However, as we are getting off topic and involving more other project including modding custom rom with kernel, unbricking etc, so suggested by our senior member @r2d23cpo , I've created a new thread that only discussing about the project that we are going on.
useful resources:
SGT3 10.1 Rom Developing by learning developers
http://forum.xda-developers.com/showthread.php?t=2643970
Unbricking:
http://forum.xda-developers.com/gal...p52xx-soft-t3051604/post59361000#post59361000
Android Image Kitchen:
http://forum.xda-developers.com/showthread.php?t=2073775
How to build x86 Kernels:
http://drebsdorf.net/content/samsung_gt3/KernelHowTo.html
NOTE: IF YOU ARE NOT A DEVELOPER THEN DO NOT INVOLVE HERE AND POST USELESS COMMENT. YOU MAY ASK QUESTION HERE BUT ONLY ABOUT THIS TOPIC, DO NOT TALK CRAP!

So if you want to start that thread please do so
Click to expand...
Click to collapse
@r2d23cpo @Daniel-TAz00 , @Max4000 here we go, lets continue our discussion here...
I know I Mention CM10.1. Please be aware there in no Official Working Cianogenmod for our device, the most we have is Angel_666 work. I had taken a lot of work to get where hi is at.
For know I suggest you not to get involved in CM10.1. I have bad Internet, It took me 1 moth just to downlond ripos and patches just to see it compile boot and recovery images. It does not produce a working system.img.
Now what I try to say before is that a 4.2.2 CM10.1 boot & recovery images had make my life more easier. At least that is my impression. Just give me some time I will post the images I use. Then you can place your Kernel on it.
Click to expand...
Click to collapse
@r2d23cpo yeap, i can see that there is very limited resources for CM 1x going on. so i think i will try to do R&D on it, hopefully i can get to finish it before may (my university intake). I think before i can get a working CM, I will try to use stock boot.img and hopefully it works. I downloaded all version of source code that i can get on opensourcesamsung and hopefully i can get something working out if it.
some time ago I wrote a thread called, SGT3 10.1 Rom Developing by learning developers => http://forum.xda-developers.com/show....php?t=2643970. This is a suggestion, just to keep on good xda standing. Wait for you answer
Click to expand...
Click to collapse
Your thread contain a tones of useful information hopefully it can benefits those who need it. I have seen people complaining ( Including my self) that p52xx series have limited developers, so i thought of being one my self, start up some active project and keep this device running.

Nice!
Ok guys @r2d23cpo @Daniel-TAz00 , @Max4000 lets have fun here.
First I know I mention twice 4.2.2 - CM10.1 and there is a reason, No Selinux Files in boot nor recovery images! That makes me happy.
But lets be clear, Cianogenmod for Tab3 10.1 is like a Dog witching to received a fillet.! The only prove of concepts has been made by Angel_666 in his thread [Development][Source]CyanogenMod 11 for SGT-3 10.1 by Angel_666 => http://forum.xda-developers.com/showthread.php?t=2633554. Thanks Angel and all that help him for those long days of work.
Now there are many thread in AOSP or Cianogenmod for TAB3 10.1. with time all got forgotten. So, Do not waist your time for now on that road to hell.
I my self burn out 1 moth some time ago on 4.2.2 CM10.1 , and I only got to compile a none working firmware. But It produce boot.img and recovery.img. Now This files are in fact worthless by them self. boot.img will not boot to a system and the recovery has issues with lag response. So Why then did I mention it. Because there is NO SELinux on them. That makes those files the perfect TEST Sandbox to try new things. So without more explanation I am attaching the files I build. I am attaching them here in update.zip form for easily installation. Be aware they are build for GT_P5210. But guess what, if you used them for testing, it do not matters because they in fact incomplete.
Code:
CM10.1_boot.zip 12.6 MB
h__ps://mega.co.nz/#!HkJVCDxK!wzKnciQx50QkIbe65-3l-DtfCy0lavoKRw4tUY2wGDA
CM10.1_boot.zip 12.6 MB
h__ps://mega.co.nz/#!HkJVCDxK!wzKnciQx50QkIbe65-3l-DtfCy0lavoKRw4tUY2wGDA
So forget to dedicate time in CM R&D. It is useless for now. Well that is not true. It may be possible to take Angels CM11 tree and modified it to meet CM10.1. Who knows it may work!. But believe me it takes a lot of time to paste all patches and correct all compilation error just to get a final CM compilation for x86!!! I had warned you.
Now I do not know if you have realized, I know all this not because I am Senior. I am not, I am just a newbee like you. But I was playing with kernel/initramfs in
[DEVELOPMENT]TAB310.1-Run a Linux distro natively ==> http://forum.xda-developers.com/galaxy-tab-3/general/development-tab310-1-run-linux-distro-t3008521
But I got sick and now I will continue my work. It is just clearly related to what you are trying to do.

Now I do not know if you have realized, I know all this not because I am Senior. I am not, I am just a newbee like you. But I was playing with kernel/initramfs in
Click to expand...
Click to collapse
@r2d23cpo actually everyone make their own ways to become a good developer or a senior. I my self did the same thing, asked a lot of questions, brick my device unlimited times. And now I can pick up easily.
So forget to dedicate time in CM R&D. It is useless for now. Well that is not true. It may be possible to take Angels CM11 tree and modified it to meet CM10.1. Who knows it may work!. But believe me it takes a lot of time to paste all patches and correct all compilation error just to get a final CM compilation for x86!!! I had warned you.
Click to expand...
Click to collapse
Actually you are right, after i summit this thread, i have googled for resources a while now and i gave up on it because there is too much problems going on. So now i just wanna try to mod my boot.img that i got from sammobile.com and try to flash it to enable wifi dongle support.
@Daniel-TAz00 , Can you try to compile a kernel that based on stock rom? I noticed there is a lot people who prefer stock rom on this device.

can anyone help me out here?
http://forum.xda-developers.com/galaxy-tab-3/help/adb-detect-tab-3-fastboot-dosent-weird-t3052404
I have tried every possible solution i can think of and google of.

Jacker31 said:
@Daniel-TAz00 , Can you try to compile a kernel that based on stock rom? I noticed there is a lot people who prefer stock rom on this device.
Click to expand...
Click to collapse
The boot.img I made should work for stock roms aswell.
Anyway, back last year when I built my kernel, I took a bunch of notes with the idea of writing a detailed android kernel tutorial. It's not at all done, but contain a bunch of specific GT-P52xx info.
Here are my notes on compiling the GT-P5210 kernel: http://drebsdorf.net/content/samsung_gt3/KernelHowTo.html
*Crossposting*
Getting the proper monitor mode broadcom drivers should be possible, which broadcom chip do we have tho?
https://code.google.com/p/bcmon/source/browse/trunk/#trunk/bcm4329/driver/src/bcm4329
Anyone know which is the latest kernel source file? (i could surely compile for the P5200 aswell)
http://opensource.samsung.com/reception/receptionSub.do?method=sub&sub=F&searchValue=GT-P5210
I suspect its: GT-P5210_EUR_KK_Opensource.zip (I will get the sources for the other versions of the tablet aswell)

Daniel-TAz00 said:
The boot.img I made should work for stock roms aswell.
Anyway, back last year when I built my kernel, I took a bunch of notes with the idea of writing a detailed android kernel tutorial. It's not at all done, but contain a bunch of specific GT-P52xx info.
Here are my notes on compiling the GT-P5210 kernel: http://drebsdorf.net/content/samsung_gt3/KernelHowTo.html
Click to expand...
Click to collapse
I didnt really take down notes, but I actually have like 10+ tabs open with information that i need for doing things.

*Crossposting*
Getting the proper monitor mode broadcom drivers should be possible, which broadcom chip do we have tho?
https://code.google.com/p/bcmon/sour...Fsrc/bcm4329
Anyone know which is the latest kernel source file? (i could surely compile for the P5200 aswell)
http://opensource.samsung.com/recept...Value=GT-P5210
I suspect its: GT-P5210_EUR_KK_Opensource.zip (I will get the sources for the other versions of the tablet aswell)
Click to expand...
Click to collapse
I used the SEA KK version instead of EUR since I got my device from singapore. I got stuck in broadcom.* error while compiling the kernel, and its alright after i disabled it in menuconfig.

Getting the proper monitor mode broadcom drivers should be possible, which broadcom chip do we have tho?
https://code.google.com/p/bcmon/sour...Fsrc/bcm4329
Click to expand...
Click to collapse
Code:
[email protected]:~# cd Kernel
[email protected]:~/Kernel# make ARCH=i386 android_santos10_open_r00_user_defconfig
arch/x86/Kconfig:496:warning: defaults for choice values not supported
drivers/staging/mrfl/Kconfig:25:warning: choice value used outside its choice group
drivers/staging/mrfl/Kconfig:31:warning: choice value used outside its choice group
arch/x86/configs/android_santos10_open_r00_user_defconfig:3123:warning: override: reassigning to symbol SYNC
arch/x86/configs/android_santos10_open_r00_user_defconfig:3615:warning: override: reassigning to symbol SECURITY_SELINUX
arch/x86/configs/android_santos10_open_r00_user_defconfig:3616:warning: override: DEFAULT_SECURITY_SELINUX changes choice state
arch/x86/configs/android_santos10_open_r00_user_defconfig:3618:warning: override: reassigning to symbol NETWORK_SECMARK
#
# configuration written to .config
#
[email protected]:~/Kernel# make menuconfig
scripts/kconfig/mconf Kconfig
arch/x86/Kconfig:496:warning: defaults for choice values not supported
drivers/staging/mrfl/Kconfig:25:warning: choice value used outside its choice group
drivers/staging/mrfl/Kconfig:31:warning: choice value used outside its choice group
#
# configuration written to .config
#
*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.
[email protected]:~/Kernel# make arch=i386 -j2
scripts/kconfig/conf --silentoldconfig Kconfig
arch/x86/Kconfig:496:warning: defaults for choice values not supported
drivers/staging/mrfl/Kconfig:25:warning: choice value used outside its choice group
drivers/staging/mrfl/Kconfig:31:warning: choice value used outside its choice group
make[1]: Nothing to be done for `all'.
make[1]: Nothing to be done for `relocs'.
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
VDSOSYM arch/x86/vdso/vdso32-int80-syms.lds
VDSOSYM arch/x86/vdso/vdso32-sysenter-syms.lds
VDSOSYM arch/x86/vdso/vdso32-syms.lds
LD arch/x86/vdso/built-in.o
LD arch/x86/built-in.o
CC net/mac80211/main.o
CC drivers/net/wireless/at76c50x-usb.o
CC net/mac80211/status.o
CC drivers/net/wireless/ath/main.o
CC drivers/net/wireless/ath/regd.o
CC net/mac80211/sta_info.o
CC drivers/net/wireless/ath/hw.o
CC drivers/net/wireless/ath/key.o
CC net/mac80211/wep.o
LD drivers/net/wireless/ath/ath.o
LD drivers/net/wireless/ath/built-in.o
CC drivers/net/wireless/b43/main.o
CC net/mac80211/wpa.o
CC net/mac80211/scan.o
CC net/mac80211/offchannel.o
CC drivers/net/wireless/b43/bus.o
CC drivers/net/wireless/b43/tables.o
CC net/mac80211/ht.o
CC drivers/net/wireless/b43/phy_common.o
CC net/mac80211/agg-tx.o
CC drivers/net/wireless/b43/phy_g.o
CC net/mac80211/agg-rx.o
CC net/mac80211/ibss.o
CC drivers/net/wireless/b43/phy_a.o
CC drivers/net/wireless/b43/phy_lp.o
CC net/mac80211/work.o
CC net/mac80211/iface.o
CC drivers/net/wireless/b43/tables_lpphy.o
CC drivers/net/wireless/b43/sysfs.o
CC net/mac80211/rate.o
CC drivers/net/wireless/b43/xmit.o
CC net/mac80211/tkip.o
CC drivers/net/wireless/b43/lo.o
CC net/mac80211/aes_ccm.o
CC drivers/net/wireless/b43/wa.o
CC net/mac80211/aes_cmac.o
CC net/mac80211/cfg.o
CC drivers/net/wireless/b43/dma.o
CC drivers/net/wireless/b43/pio.o
CC net/mac80211/rx.o
CC drivers/net/wireless/b43/rfkill.o
LD drivers/net/wireless/b43/b43.o
LD drivers/net/wireless/b43/built-in.o
CC drivers/net/wireless/b43legacy/main.o
CC net/mac80211/spectmgmt.o
CC net/mac80211/tx.o
CC drivers/net/wireless/b43legacy/ilt.o
CC drivers/net/wireless/b43legacy/phy.o
CC net/mac80211/key.o
CC net/mac80211/util.o
CC drivers/net/wireless/b43legacy/radio.o
CC net/mac80211/wme.o
CC net/mac80211/event.o
CC drivers/net/wireless/b43legacy/sysfs.o
CC net/mac80211/chan.o
CC drivers/net/wireless/b43legacy/xmit.o
CC net/mac80211/driver-trace.o
CC drivers/net/wireless/b43legacy/rfkill.o
CC drivers/net/wireless/b43legacy/debugfs.o
CC drivers/net/wireless/b43legacy/dma.o
CC drivers/net/wireless/b43legacy/pio.o
LD drivers/net/wireless/b43legacy/b43legacy.o
LD drivers/net/wireless/b43legacy/built-in.o
CC drivers/net/wireless/bcmdhd/bcmsdh.o
<command-line>:0:0: error: "CUSTOM_MAX_TXGLOM_SIZE" redefined [-Werror]
<command-line>:0:0: note: this is the location of the previous definition
<command-line>:0:0: error: "DYNAMIC_F2_BLKSIZE_FOR_NONLEGACY" redefined [-Werror]
<command-line>:0:0: note: this is the location of the previous definition
<command-line>:0:0: error: "CUSTOM_GLOM_SETTING" redefined [-Werror]
<command-line>:0:0: note: this is the location of the previous definition
<command-line>:0:0: error: "CUSTOM_GLOM_SETTING" redefined [-Werror]
<command-line>:0:0: note: this is the location of the previous definition
<command-line>:0:0: error: "CUSTOM_GLOM_SETTING" redefined [-Werror]
<command-line>:0:0: note: this is the location of the previous definition
CC net/mac80211/mlme.o
In file included from drivers/net/wireless/bcmdhd/bcmsdh.c:43:0:
drivers/net/wireless/bcmdhd/include/bcmsdbus.h:66:2: error: #warning "SDPCM_DEFGLOM_SIZE cannot be higher than SDPCM_MAXGLOM_SIZE!!" [-Werror=cpp]
cc1: all warnings being treated as errors
make[4]: *** [drivers/net/wireless/bcmdhd/bcmsdh.o] Error 1
make[3]: *** [drivers/net/wireless/bcmdhd] Error 2
make[2]: *** [drivers/net/wireless] Error 2
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
CC net/mac80211/pm.o
CC net/mac80211/rc80211_minstrel.o
CC net/mac80211/rc80211_minstrel_ht.o
LD net/mac80211/mac80211.o
LD net/mac80211/built-in.o
LD net/built-in.o
[email protected]:~/Kernel#

Jacker31 said:
Code:
[email protected]:~# cd Kernel
[email protected]:~/Kernel# make ARCH=i386 android_santos10_open_r00_user_defconfig
Click to expand...
Click to collapse
Ello, what are you up to? You compiled .... something
You might want to remove -Werror flags from the makefile, otherwise default option is to exit on compile warnings

Daniel-TAz00 said:
Ello, what are you up to? You compiled .... something
You might want to remove -Werror flags from the makefile, otherwise default option is to exit on compile warnings
Click to expand...
Click to collapse
oh ~ for that make ARCH=i386 android_santos10_open_r00_user_defconfig i thought was a process of generating config. because i saw somewhere that i have to run it first, but i lost the link though.
Never mind, I was in confused and i figured it out...
Code:
#Create Boot.img
Now I copied the boot.img to /home/android/WRKDIR_BOOT/ from the P5210UEUAMI8.zip rom we found on XDA (by Mod57)
cd /home/android/WRKDIR_BOOT/
unmkbootimg -i boot.img
This will extract the boot.img into its parts.
It also will spit out the command you need to rebuild the image, save that for later.
Copy /home/android/WRKDIR_KRLSRC/arch/x86/bzImage to /home/android/WRKDIR_BOOT/bzImage
Change the parameters of the rebuild command you saved and change
--kernel bzImage
--ramdisk ramdisk.cpio.gz
-o boot-MI8.img
ex. (PLESE DO NOT USE, this is an example cmd, your offsets may vary, unless you need bricks for a house , I cant recommend it.)
To rebuild this boot image, you can use the command:
mkbootimg --base 0 --pagesize 2048 --kernel_offset 0x10008000 --ramdisk_offset 0x11000000 --second_offset 0x10f00000 --tags_offset 0x10000100 --cmdline 'init=/init pci=noearly console=ttyS0 console=logk0 earlyprintk=nologger loglevel=4 hsu_dma=7 kmemleak=off androidboot.bootmedia=sdcard androidboot.hardware=santos10wifi androidboot.spid=xxxx:xxxx:xxxx:xxxx:xxxx:xxxx androidboot.serialno=01234567890123456789012345678901 ip=50.0.0.2:50.0.0.1::255.255.255.0::usb0:on vmalloc=172M' --kernel bzImage --ramdisk ramdisk.cpio.gz -o boot-MI8.img
@Daniel-TAz00 one question, can i just use other tool to pack like this one in the attachment? I like to use it as it has a gui.
the attachment (there is a 8mb limit so i uploaded to mega instead.) : https://mega.co.nz/#!6hkSTYJY!gUa0VeQ-6nDh2TMw4Ul23nPt6RLP8r0Wg3UFDJUr7vQ

Jacker31 said:
@Daniel-TAz00 one question, can i just use other tool to pack like this one in the attachment? I like to use it as it has a gui.
the attachment (there is a 8mb limit so i uploaded to mega instead.) : https://mega.co.nz/#!6hkSTYJY!gUa0VeQ-6nDh2TMw4Ul23nPt6RLP8r0Wg3UFDJUr7vQ
Click to expand...
Click to collapse
Looks like it might be able to. I don't for sure though

I had little time, and the little time I had I used answering post.
One thing regards building kernel I will start posting only here for now on.
I did answer to Daniel-TAz00 on what I think is wifi driver ,type bcmdhd or dhd.ko. see here http://forum.xda-developers.com/showpost.php?p=59404794&postcount=37
I saw the issue with fastboot and answered by @moonbutt74. Yes no fastboot for MOSTSamsung devices.
I like moonbutt74
Code:
#!/bin/bash
/<$NDK-TOP>/build/tools/./make-standalone-toolchain.sh --ndk-dir=/<$NDK-TOP> --system=linux-x86 --toolchain=[COLOR="Red"]x86-4.8[/COLOR] --platform=android-17 --install-dir=/opt//toolchains/NDK-x86-4.8-JB
but never tested. I just point to where I have my NDK toolchain. But that previous option should be better. Now I have always tell moonbutt74 that I disagree in using gcc4.8. If you Open README_Kernel.txt you will see that their instructions point to gcc4.6
Code:
ex) CROSS_COMPILE ?= {your google aosp}/prebuilts/gcc/linux-x86/x86/[COLOR="Red"]i686-linux-android-4.6[/COLOR]/bin/i686-linux-android-
In fact I already said that to Jacker31 in http://forum.xda-developers.com/showpost.php?p=59310924&postcount=2 where I explained you should in fact install ggc 4.6 in your Linux distribution so that the "MAKE" get maximun compatibility witch will end up in minimun errors!!!!!
In ubuntu this is done
Code:
sudo apt-get install gcc-4.6 g++-4.6 gcc-4.6-multilib g++-4.6-multilib
sudo update-alternatives --remove-all gcc
sudo update-alternatives --remove-all g++
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.6 20
sudo update-alternatives --install /usr/bin/g++ g++ /usr/bin/g++-4.6 20
sudo update-alternatives --install /usr/bin/cc cc /usr/bin/gcc 30
sudo update-alternatives --set cc /usr/bin/gcc
sudo update-alternatives --install /usr/bin/c++ c++ /usr/bin/g++ 30
sudo update-alternatives --set c++ /usr/bin/g++
sudo update-alternatives --config gcc
sudo update-alternatives --config g++
Yes you Linux distribution will end up with a native 4.6 gcc witch is no the same as the NDK tool-chain you are suggested to use. I also suggested you install a Linix distribution with 32bit even if you have a 64bit!!! This is my personal opinion.
For example I can compile Kernel-GT-P5210_EUR_KK_Opensource without a single error just by adding
Edit Makefile
Code:
CROSS_COMPILE ?= /media/<user>/Ldata/bin/androidndk/toolchains/x86-4.6/prebuilt/linux-x86/bin/i686-linux-android-
"/media/<user>/Ldata" this is just my DiskDrive
and execute
Code:
make ARCH=i386 android_santos10_open_r00_user_defconfig
make ARCH=i386 -j6
"-j6" is use to accelerate the process. Yes my devices is a Intel Core i7 witch in fact has 4 Physical Core but has 4 Virtual Cores thats a Total of 8 Cores, So by using "-j6" I dedicate 6 of my total 8 cores to the compilation. Taking about a 1/4 of the required time!.
This bring me to recall, are we going to use 4.2.2 instead of 4.4.2?
Here are my notes on compiling the GT-P5210 kernel: http://drebsdorf.net/content/samsung...rnelHowTo.html
Click to expand...
Click to collapse
Nice notes thanks Daniel-TAz00
@Daniel-TAz00 one question, can i just use other tool to pack like this one in the attachment? I like to use it as it has a gui.
the attachment (there is a 8mb limit so i uploaded to mega instead.) : https://mega.co.nz/#!6hkSTYJY!gUa0Ve...r0Wg3UFDJUr7vQ
Click to expand...
Click to collapse
moonbutt74 has show me AIK to pack and unpack images.
http://forum.xda-developers.com/showthread.php?t=2073775
This Android Image kitchen has support for Win7, Android and Linux. I normally do not use anything else.
Please be ware that while working in Win7 you can lose the Permission and ownership!! Making the pack image to failed!!! when in fact if you had packed it in Android or Linux it will be ok. The same goes if you are working in Linux but the files are store in Fat32 or NTFS. So be aware of that.

I like moonbutt74
Code:
#!/bin/bash
/<$NDK-TOP>/build/tools/./make-standalone-toolchain.sh --ndk-dir=/<$NDK-TOP> --system=linux-x86 --toolchain=x86-4.8 --platform=android-17 --install-dir=/opt//toolchains/NDK-x86-4.8-JB
but never tested. I just point to where I have my NDK toolchain. But that previous option should be better. Now I have always tell moonbutt74 that I disagree in using gcc4.8. If you Open README_Kernel.txt you will see that their instructions point to gcc4.6
Code:
ex) CROSS_COMPILE ?= {your google aosp}/prebuilts/gcc/linux-x86/x86/i686-linux-android-4.6/bin/i686-linux-android-
In fact I already said that to Jacker31 in http://forum.xda-developers.com/show...24&postcount=2 where I explained you should in fact install ggc 4.6 in your Linux distribution so that the "MAKE" get maximun compatibility witch will end up in minimun errors!!!!!
Click to expand...
Click to collapse
Remember my thread with that some error occur during compiling kernel? the one you answered? that occur and prevent me from compiling even i flagged it to ignore warnings but it end up error. That's happen because i used the wrong gcc build. I have to use the exact build returned in readme_kernel to build it successfully.
One thing regards building kernel I will start posting only here for now on.
I did answer to Daniel-TAz00 on what I think is wifi driver ,type bcmdhd or dhd.ko. see here http://forum.xda-developers.com/show...4&postcount=37
Click to expand...
Click to collapse
Hm...In my opinion, we should just forget about broadcom drivers as the wifi adapters is not as powerful as TL-w772n or that ALFA adapters. In fact most people who wish to use aircrack have either tplink or ALFA, unless they have something else.
Quote:
@Daniel-TAz00 one question, can i just use other tool to pack like this one in the attachment? I like to use it as it has a gui.
the attachment (there is a 8mb limit so i uploaded to mega instead.) : https://mega.co.nz/#!6hkSTYJY!gUa0Ve...r0Wg3UFDJUr7vQ
moonbutt74 has show me AIK to pack and unpack images.
http://forum.xda-developers.com/show....php?t=2073775
This Android Image kitchen has support for Win7, Android and Linux. I normally do not use anything else.
Please be ware that while working in Win7 you can lose the Permission and ownership!! Making the pack image to failed!!! when in fact if you had packed it in Android or Linux it will be ok. The same goes if you are working in Linux but the files are store in Fat32 or NTFS. So be aware of that.
Click to expand...
Click to collapse
Thanks for that, I have totally forgotten about AIK .
"-j6" is use to accelerate the process. Yes my devices is a Intel Core i7 witch in fact has 4 Physical Core but has 4 Virtual Cores thats a Total of 8 Cores, So by using "-j6" I dedicate 6 of my total 8 cores to the compilation. Taking about a 1/4 of the required time!.
Click to expand...
Click to collapse
I am going to get a new i7 MSI laptop soon cant wait for it XD I cant really stand with my current 6yo hp laptop as it will overheat while using MSVs2012 or eclipse . Arrrh sometimes even in vmware. I only have 2 cores on my processors so i cannot actually put up 8 XD.

Hm...In my opinion, we should just forget about broadcom drivers as the wifi adapters is not as powerful with TL-w772n or that ALFA adapters. In fact most people who wish to use aircrack have either tplink or ALFA, unless they have something else.
Click to expand...
Click to collapse
Is this your anwer or somebody else?
Listen I has used this to ,monitor wifi channel used. Some time ago I found hacking to complicated and time consuming. Maybe wrong with todays version.
So to monitor wifi usage I do not need Alpha or any other router.
If you plan to buy a new laptop make yourself sure that the graphic adapter is linux compatible!11 For example,Tab3 is PowerVR witch is not Linux Friendly!1

r2d23cpo said:
Is this your anwer or somebody else?
Listen I has used this to ,monitor wifi channel used. Some time ago I found hacking to complicated and time consuming. Maybe wrong with todays version.
So to monitor wifi usage I do not need Alpha or any other router.
If you plan to buy a new laptop make yourself sure that the graphic adapter is linux compatible!11 For example,Tab3 is PowerVR witch is not Linux Friendly!1
Click to expand...
Click to collapse
thats my answer, just noticed i made typo mistake haha, agree, I like ATI graphic on my HP as it works with Kali and Ubuntu. But i am not sure that MSI i gotta buy (with nvidia) compatible with linux or not as i never heard from anyone before.
correction.
"Hm...In my opinion, we should just forget about broadcom drivers as the wifi adapters is not as powerful as TL-w772n or that ALFA adapters. In fact most people who wish to use aircrack have either tplink or ALFA, unless they have something else."
Hacking maybe time consuming and tired, but with correct usage, it can create fireworks. But people seems to take their knowledge of hacking and use it wrongly.

Unless Daniel-TAz00 objects, I will postpone TAB3 wifi's own driver mod for promiscuous. Please remember I have my own Kernel mod project [DEVELOPMENT]TAB310.1-Run a Linux distro natively ==> http://forum.xda-developers.com/gal...ent-tab310-1-run-linux-distro-t3008521/page11 Now If you go there you see is almost a monologue, me , my ideas and some more of my work. From time to time I get a visit witch offer me great Ideas. But at this point is just Kernel development. That is why I am spending time here with you guys. I see interest in learning and developing. More of us more may gets done. My philosophy learn and spread the knowledge to others. And never forget I am just a newbee just like most of us.
So back to Android Kernel Modding for GT-P52xx.
To share with us you only need to setup your Linux building environment and download Samsung Open Source. I suggest we stick with JB 4.2.2, So for testing it will help if you backup your tablet using TWTP to a external SDCARD. I suggest install the original stock JB 4.2.2. And you can download "GT-P5210_SEA_JB_Opensource.zip" witch I think was the original. So you do that until you see that you can Compile your own Kernel. Then you are ready for some modifications. And join the group. If you need help just ask?
Androids Kernel is just an incomplete Linux kernel. So they share many thing. That means we should be able to go into Kernel. org or similar sites and read their info and try to apply it to us.
Linux Kernel Documentation Index ==> h__ps://www.kernel.org/doc/index-old.html
Menuconfig docs for Linux v3.0-rc7 ==> h__ps://www.kernel.org/doc/menuconfig/
arch/x86/Kconfig v3.0-rc7 ==> h__ps://www.kernel.org/doc/menuconfig/x86.html
Do not waist your MAIN time reading it. Just know you can get there to get info.
Now the main problem when we mod the kernel is that we get Samsung Screen and nothing more. So we need a way to debug the kernel and get info. So you can google debugging Kernel and find many resources.
Now Here is the tricky part. When you boot there is "kernel space" then "user space". You need to remember because kernel security will not allow you to get into kernel space from user space. A nice place to start is
Kernel Debugging Tips ==> h__p://elinux.org/Kernel_Debugging_Tips
And here is what I want to do next. Google eclipse debugging linux kernel. For example
h__p://issaris.blogspot.com/2007/12/download-linux-kernel-sourcecode-from.html
h__p://www.yonch.com/tech/84-debugging-the-linux-kernel-with-qemu-and-eclipse
Now clearly this methods are for Linux Distro like Ubuntu. But I think we can run Our Android and run Ubuntu or kali under chroot like you been doing. Install Eclipse on the tab. Then execute all this on my desktop using VNC ty to the linux on the TAB. And finally I hope to debug the kernel without installing it.
I hope this works.

To share with us you only need to setup your Linux building environment and download Samsung Open Source. I suggest we stick with JB 4.2.2, So for testing it will help if you backup your tablet using TWTP to a external SDCARD. I suggest install the original stock JB 4.2.2. And you can download "GT-P5210_SEA_JB_Opensource.zip" witch I think was the original. So you do that until you see that you can Compile your own Kernel. Then you are ready for some modifications. And join the group. If you need help just ask?
Click to expand...
Click to collapse
i think the original are something like this "GT-P5220_JB_Opensource.zip"
Unless Daniel-TAz00 objects, I will postpone TAB3 wifi's own driver mod for promiscuous. Please remember I have my own Kernel mod project [DEVELOPMENT]TAB310.1-Run a Linux distro natively ==> http://forum.xda-developers.com/gala...3008521/page11 Now If you go there you see is almost a monologue, me , my ideas and some more of my work. From time to time I get a visit witch offer me great Ideas. But at this point is just Kernel development. That is why I am spending time here with you guys. I see interest in learning and developing. More of us more may gets done. My philosophy learn and spread the knowledge to others. And never forget I am just a newbee just like most of us.
So back to Android Kernel Modding for GT-P52xx.
To share with us you only need to setup your Linux building environment and download Samsung Open Source. I suggest we stick with JB 4.2.2, So for testing it will help if you backup your tablet using TWTP to a external SDCARD. I suggest install the original stock JB 4.2.2. And you can download "GT-P5210_SEA_JB_Opensource.zip" witch I think was the original. So you do that until you see that you can Compile your own Kernel. Then you are ready for some modifications. And join the group. If you need help just ask?
Androids Kernel is just an incomplete Linux kernel. So they share many thing. That means we should be able to go into Kernel. org or similar sites and read their info and try to apply it to us.
Linux Kernel Documentation Index ==> h__ps://www.kernel.org/doc/index-old.html
Menuconfig docs for Linux v3.0-rc7 ==> h__ps://www.kernel.org/doc/menuconfig/
arch/x86/Kconfig v3.0-rc7 ==> h__ps://www.kernel.org/doc/menuconfig/x86.html
Do not waist your MAIN time reading it. Just know you can get there to get info.
Now the main problem when we mod the kernel is that we get Samsung Screen and nothing more. So we need a way to debug the kernel and get info. So you can google debugging Kernel and find many resources.
Now Here is the tricky part. When you boot there is "kernel space" then "user space". You need to remember because kernel security will not allow you to get into kernel space from user space. A nice place to start is
Kernel Debugging Tips ==> h__p://elinux.org/Kernel_Debugging_Tips
And here is what I want to do next. Google eclipse debugging linux kernel. For example
h__p://issaris.blogspot.com/2007/12/download-linux-kernel-sourcecode-from.html
h__p://www.yonch.com/tech/84-debugging-the-linux-kernel-with-qemu-and-eclipse
Now clearly this methods are for Linux Distro like Ubuntu. But I think we can run Our Android and run Ubuntu or kali under chroot like you been doing. Install Eclipse on the tab. Then execute all this on my desktop using VNC ty to the linux on the TAB. And finally I hope to debug the kernel without installing it.
Click to expand...
Click to collapse
i will take my time and do a little research as i still got 1 and a half month of holiday before i get into my university.

Jacker31
I know working with the Kernel is fun!
But in reality what is what you want to add to it? What is your objective?

r2d23cpo said:
Jacker31
I know working with the Kernel is fun!
But in reality what is what you want to add to it? What is your objective?
Click to expand...
Click to collapse
em there is a few objective of my point:
1) to spend my time on something useful,
2)for fun
3) tinkering around on my tab3 with kali linux and add in some usb driver.
4) discovering more ideas and maybe i can get started with another project.

Related

How to compile native android code

Hi everyone,
There has been a few questions on how to compile native android code (for exploits and such). Easy enough.
Go to http://source.android.com/download. You will need to be running Linux. Ubuntu is easiest. Follow the directions to get the source code for android downloaded and compiled.
Run this command
export PATH=/path/to/android/source/prebuilt/linux-x86/toolchain/arm-eabi-4.2.1/bin
Run arm-aebi-gcc or arm-aebi-g++ (depending on the language, c or c++) followed by
-o (OUTPUT) (INPUT)
So, for example, test.c would be:
arm-aebi-gcc -o test test.c
And test.cpp would be
arm-aebi-g++ -o test test.cpp
Just a note, this will make STATICALLY linked files. Meaning any headers will be included INSIDE the executable. Simply put, this means the files will be HUGE for large projects. There is a program, named agcc, which fixes this and can be found here:
http://plausible.org/andy/agcc
Put it in /bin by:
Code:
cd /bin
sudo wget http://plausible.org/andy/agcc
chmod 755 agcc
chmod +x agcc
Run agcc -o (OUTFILE) (INPUT) to compile. Be warned though, if a header is in the file that isn't in bionic (android's smaller libc) it won't compile.
Hope this helps!
+1
Awesome
............(stuipid mistake >>was<< here)..............
Thanks man...
now i can break out my bootable 50 meg linux disc and play around.
love that thing used to use it to crack windows passwords
should see the guys face when you crack his 20 char password in 5 mins without ever needing to use it.
well not really cracking but changing it. used to work at the pentagon. this one guys who used to be support for one dept. thought it would be funny to change all the admin passwords in his office. so when one of the pc's was beyond his repair. i showed up and he was like give me 10 min and i'll log you in. well 5 mins later i was fixing the machine while he was screwing off. boy was he pissed.
how big's gcc? cause i'll need to compile it for my linux.
rigamrts said:
how big's gcc? cause i'll need to compile it for my linux.
Click to expand...
Click to collapse
Massive. You're definitely better off using the prebuilt toolchain found in the Android (N|S)DK.
I would like to add something to this.
libc is essentially derived from the kernel. So, if you take agcc, and make changes to use the libc directory (I don't remember it atm) and NOT bionic, the app won't compile. Simple enough, libc is based of the kernel, so bionic is based of the android kernel. Things missing in bionic that are in libc WON"T work simply because certain kernel calls in glibc DON'T exist on the Android platform.
My exploit relied on the fact that I would be able to compile exploits using glibc, instead of using bionic. So it failed. Thats what I've figured out so far anyways.
zifnab06 said:
My exploit relied on the fact that I would be able to compile exploits using glibc, instead of using bionic. So it failed. Thats what I've figured out so far anyways.
Click to expand...
Click to collapse
Would you be willing to share the code for that exploit, even if it doesn't work? (sorry if you already have, I didn't see it anywhere)
I may be able to help.
Look up anything in our old thread, especially when we were talking about "sys/personality.h". The one I was working with exploited a hole that was patched (min_map_addr).
This blog post
honeypod.blogspot.com/2007/12/dynamically-linked-hello-world-for.html
(Sorry, my account isn't allowed to post links yet.)
gives a minimalist approach to using dynamically linked executables. (In particular, see steps #2 and #3 for the sources for hello.c and start.c) I gave it a try, and it seemed to work without agcc, e.g. with a makefile like the following (and with the arm-eabi- executables in the PATH of the user invoking the make) :
Code:
AR = arm-eabi-ar
AS = arm-eabi-as
CC = arm-eabi-gcc
CXX = arm-eabi-c++
LD = arm-eabi-ld
NDK_KIT = /opt/android/android-ndk-1.5_r1
PLATF_KIT = build/platforms/android-1.5
ARM_INC = $(NDK_KIT)/$(PLATF_KIT)/arch-arm/usr/include
ARM_LIB = $(NDK_KIT)/$(PLATF_KIT)/arch-arm/usr/lib
PLATF_INC = $(NDK_KIT)/$(PLATF_KIT)/common/include
OBJS = hello.o start.o
EXES = hello
hello: hello.o start.o
$(LD) \
--entry=_start \
--dynamic-linker /system/bin/linker -nostdlib \
-rpath /system/lib -rpath $(ARM_LIB) \
-L $(ARM_LIB) -lc -o hello hello.o start.o
hello.o: hello.c
$(CC) -I $(ARM_INC) -I $(PLATF_INC) -c hello.c
start.o: start.c
$(CC) -I $(ARM_INC) -I $(PLATF_INC) -c start.c
clean:
rm -f $(OBJS) $(EXES)
HTH
bftb0
Just curious, but I'm trying to get some native code that I've compiled to run on the Incredible. I've followed the instructions to download the the arm gcc, compiled my C code, and adb push'ed the executable over to /sdcard but I get a "permission denied" error when I try running it from my phone and adb shell. Does the phone have to be rooted in order to run native C compiled executables?
Thanks!
zebdor44 said:
Just curious, but I'm trying to get some native code that I've compiled to run on the Incredible. I've followed the instructions to download the the arm gcc, compiled my C code, and adb push'ed the executable over to /sdcard but I get a "permission denied" error when I try running it from my phone and adb shell. Does the phone have to be rooted in order to run native C compiled executables?
Thanks!
Click to expand...
Click to collapse
On an unrooted phone, push your code to /system/local or another place that you can write to and chmod it to be executable. By default the sdcard is mounted no execute. You will either need to add the directory you put it in to the path or execute it implicitly by specifying it is in the local directory.
for example ./myprogram
I hope that helps. I re-read it and it doesn't make much sense unless you have a firm grasp of the things that happen between the lines.
best of luck.
Thanks. Good stuff.
rigamrts said:
now i can break out my bootable 50 meg linux disc and play around.
love that thing used to use it to crack windows passwords
should see the guys face when you crack his 20 char password in 5 mins without ever needing to use it.
well not really cracking but changing it. used to work at the pentagon. this one guys who used to be support for one dept. thought it would be funny to change all the admin passwords in his office. so when one of the pc's was beyond his repair. i showed up and he was like give me 10 min and i'll log you in. well 5 mins later i was fixing the machine while he was screwing off. boy was he pissed.
how big's gcc? cause i'll need to compile it for my linux.
Click to expand...
Click to collapse
This is one of the most unbelievable stories ive read in a while. The fact that the pentagon had an administration department without policies or security in place to prevent such a widely known method, is comical.
btw, such a linux cd is no secret. Its called pnordahl.
Useful information
I'm surprised to see that many of you don't use the Forum's search function and simply start new topics over and over again. What funny is that the info you put here is old and useless.
I've posted an article on how to compile native C code for Android months ago, with several examples and tools:
http://forum.xda-developers.com/showthread.php?t=514803
or direct link herE:
http://www.pocketmagic.net/?p=682
However this technique is now too old.
The best approach is to simply use the NDK and build a custom Makefile for Cygwin's make under windows or easier under linux, see:
http://betelco.blogspot.com/2010/01/buildingdebugging-android-native-c.html
radhoo said:
I'm surprised to see that many of you don't use the Forum's search function and simply start new topics over and over again. What funny is that the info you put here is old and useless.
I've posted an article on how to compile native C code for Android months ago, with several examples and tools:
http://forum.xda-developers.com/showthread.php?t=514803
or direct link herE:
http://www.pocketmagic.net/?p=682
However this technique is now too old.
The best approach is to simply use the NDK and build a custom Makefile for Cygwin's make under windows or easier under linux, see:
http://betelco.blogspot.com/2010/01/buildingdebugging-android-native-c.html
Click to expand...
Click to collapse
Thank you for your very informative links. I'll take a look tonight, since I find this very interesting and would love to compile a few things for Android.
"What funny is that the info you put here is old and useless." - This was posted almost 10 months ago. That's a long time in smart phone years. By the same token, if it were January 2010 and I was looking for this info, I would assume that a post from May 2009 would be dated too.
"I'm surprised to see that many of you don't use the Forum's search function and simply start new topics over and over again." - Maybe zifnab did search and find your post and deemed your technique too old for Jan. 2010, so he created a new post with newer information. Or maybe he wanted to show a different way to do the same thing. Or maybe he figured that many users only have/take the time to look in their phone-specific forum. No one knows other than zifnab.
Personally, I welcome multiple posts by different people on the same topic. Everyone is different and often have different takes on the same thing. I find it easier to understand many techniques/topics if I get multiple perspectives.
Again, thank you for your contribution.
I need to compile the library with some modifications. how to do it as simple as possible? what will it take?
vlad072 said:
I need to compile the <library> with some modifications. how to do it as simple as possible? what will it take?
Click to expand...
Click to collapse
Did you get any thing in this regard ? Even i want to compile a part for library for the Android 5.1.1 device but not able to find any resource. Help will be appreciated.

[TUTORIAL][KERNEL][GPL] How-to: Compile a kernel for the B&N Nook Tablet

This tutorial will instruct you on how to compile a kernel for the Nook Tablet.
Sources:
-B&N stock source instructions
-Adrynalyne's excellent tutorial for the Mecha
-Compiling kernels for the Arch Linux project
First and foremost, you MUST use a GNU/Linux (hereafter 'Linux') distribution. I don't care if your Mac has a BSD kernel or if you have Cygwin installed, you cannot do this without a full Linux distribution.
To keep this simple, I'm going to assume that you're using the latest version of Ubuntu Linux, version 11.10. I personally haven't used Ubuntu in a long time and so I'll include instructions for Arch when they vary.
Step 0: Pre-project Setup
This link is essential to the entire process, you will need ADB before anything else: [SCRIPT] [Ubuntu] ADB, AAPT, APKTool, Android SDK/NDK, and udev rules auto-installer
Step 1: Setting up a build environment
First, you will need to install the required packages:
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev g++-multilib lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline-gplv2-dev lib32z-dev libgl1-mesa-dev git
Next, you will need a Cross-Compile Toolchain, and for our purposes we will be using the CodeSourcery release recommended by B&N (though newer versions may work):
CodeSourcery Arm Cross-Compiler
Use the IA32 GNU/Linux TAR release.
Step 2: Pulling the Kernel Source
Now, we get to pull the kernel down and prepare it for compiling.
First, create the android directory in your home folder:
Code:
mkdir ~/android
cd ~/android
Then, we pull down the kernel source:
Code:
git clone git://github.com/admiralspark/NT-sparkkernel.git
This may take awhile if you're not on a fast connection, so go make lunch
While it's pulling the repo, untar the CodeSourcery cross-compiling tools into the ~/android directory. This will create a folder inside called arm-2010q1.
Step 3: Build the Kernel
Finally, what you've been waiting for!
We have to export a few things first, to prepare the build environment. Open a terminal and type:
Code:
export BOARD_KERNEL_CMDLINE="androidboot.console=ttyO0 console=ttyO0,115200n8 [email protected] [email protected] [email protected] init=/init rootwait vram=32M,9CC00000 omapfb.vram=0:[email protected]"
export ARCH=arm
export CROSS_COMPILE=~/android/arm-2010q1/bin/arm-none-linux-gnueabi-
Then, we build it:
Code:
make android_4430BN_defconfig
make -jX
Where X is the total number of cpu's +1 (so, on my i7, I have 4 real + 4 virtual cores +1 = 9, so make -j9).
Optionally, running
Code:
make menuconfig
before make -jX will allow you to modify the kernel.
Now, watch the output at the end carefully an you'll see the necessary files that we need:
Code:
Building modules, stage 2.
MODPOST 1 modules
CC drivers/media/video/omapgfx/gfx_vout_mod.mod.o
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
GZIP arch/arm/boot/compressed/piggy.gzip
CC arch/arm/boot/compressed/misc.o
SHIPPED arch/arm/boot/compressed/lib1funcs.S
CC arch/arm/boot/compressed/decompress.o
AS arch/arm/boot/compressed/lib1funcs.o
LD [M] drivers/media/video/omapgfx/gfx_vout_mod.ko
AS arch/arm/boot/compressed/piggy.gzip.o
LD arch/arm/boot/compressed/vmlinux
OBJCOPY arch/arm/boot/zImage
Kernel: arch/arm/boot/zImage is ready
Anything marked with an [M] will need to be remembered, as well as the location of the compiled kernel at /arch/arm/boot/zImage.
And there you go! You've successfully compiled a kernel for the Nook Tablet!
See the next post for instructions on how to actually install and USE the new kernel
This post reserved
Reserved as well
More resources
Cool thanks!
First and foremost, you MUST use a GNU/Linux (hereafter 'Linux') distribution. I don't care if your Mac has a BSD kernel or if you have Cygwin installed, you cannot do this without a full Linux distribution.
Click to expand...
Click to collapse
I think you can build a kernel w/a cross compiler in OS X... but I agree it's probably easier to just use linux... even if from a VM such as virtualbox.
Also, for anyone who wants more resources, kernel-building instructions for NT, NC, and other Android devices have been documented in lots and lots of places, but but more walkthroughs can't hurt. The more info the better!
Loglud's wiki page-- in fact his whole site-- is geared specifically for NT, fwiw, and includes instructions on how to create a boot.img and I think how to flash it as well. Keep in mind though that if you're creating a bootable image w/cyanoboot it's slightly more complicated. I'll let admiral spark give you the precise instructions )
If you do a 2nd part, admiral, you may want to direct people to use fastboot for easy emmc flashing...
Other threads on XDA for the casual reader: this thread, has turned to kernel building, and the 3.0 porting thread might be of interest to more experienced folk who want to help with that effort (and it's making great progress!)
Also, loglud's thread on this topic might have some good info in the comments, though I haven't looked.
Thanks again.
fattire, thanks! The pieces on building a boot.img with irboot included, with Cyanoboot, and then using Anykernel are coming, but I'm a bit caught up in stuff right now.
weekend project
Very straightforward tutorial. I am going to make this my weekend project. I am going to try and add the super charger mods and a couple of other goodies into my build as i go. TY!
Good idea, if you don't mind I might add the supercharger mod as well as beats audio,and set up Chainfire3D for a dedicated "gaming" ROM!
Sent from my CyanogenMod 7 Alpha Final Nook Tablet
admiralspark said:
fattire, thanks! The pieces on building a boot.img with irboot included, with Cyanoboot, and then using Anykernel are coming, but I'm a bit caught up in stuff right now.
Click to expand...
Click to collapse
Sure if you need an assist (esp. w/cyanoboot or 2nd bootloader issues), find me on IRC...
Oh, quick note to those using menuconfig... if you're turning something "on" or "off"-- type space to turn off the feature (you'll see the option have a [ ]), type "Y" (or space again works) to turn it on (you'll see a [*]), or type "M" to compile it as a loadable module (you'll see [M]). You can build modules directly into the kernel, but then it's gonna make the kernel bigger. The only module that's for-sho needed to be loadable is the wifi module... to search for a feature you want to build into the kernel or make a module, use the "/" command.
C64assembly said:
Very straightforward tutorial. I am going to make this my weekend project. I am going to try and add the super charger mods and a couple of other goodies into my build as i go. TY!
Click to expand...
Click to collapse
Good idea. The source up there is a stock kernel with the smartassv2 and interactivex governors added, thats all. Let me know how it comes out, I'd like to implement it permanently in the kernel.
SilentStormer said:
Good idea, if you don't mind I might add the supercharger mod as well as beats audio,and set up Chainfire3D for a dedicated "gaming" ROM!
Sent from my CyanogenMod 7 Alpha Final Nook Tablet
Click to expand...
Click to collapse
Open Source= do it!! Though, if you get the Beats Audio/Chainfire3d working, please PM me and I'll open a branch up to host it on my github, I'd love for that to get working.
Actually, both of you PM me, I'm going to be releasing this kernel with a few more mods hopefully this weekend.
Oh yeah! Maybe we should all start using cyanoboot as a standard for our roms! Just a suggestion but itd be nice!
Sent from my CyanogenMod 7 Alpha Final Nook Tablet

GT-S 5300 kernel recompile

Good morning from Germany!
I would like to recompile my kernel on the gt-s 5300 device, so that i could install / setup some application and modules.
Basically i would like to enable the usb gadget on this android device, as far as i am informed, a kernel recompile is needed.
i have done a few kernel recompiles for linux systems, but never for a android smartphone.
maybe someone could point me to the right path ?
thanks all for your help!
kind regards
no help ?
no help ?
thanks a lot ...
Self-plug.
http://forum.xda-developers.com/showthread.php?t=1748297
thewadegeek said:
Self-plug.
http://forum.xda-developers.com/showthread.php?t=1748297
Click to expand...
Click to collapse
Hello,
Yes I have read your post - and everything worked fine.
My question now is how to get my own module to be compiled?
I have my sourcecode but not sure where to place the module and what references in which Makefile have to be done ..?
Thanks for your help.
Kind regards
Stock GT-5300 kernel built, but won't boot
I've been able to create a zImage from the GT-S5300 open source kernel code, using the bcm21553_cori_04_defconfig as indicated by the accompanying readme file.
However, when I use this kernel to create a boot.img and download using Odin, I get a quick S5300 startup screen, then nothing.
At this point, I'm just trying to build a stock kernel, no modifications. I'm looking for helpful hints on where to find any debug or error messages that will help indicate what is going wrong. I can use Odin to put the prebuilt stock kernel back, and it boots ok once again.
I've compared my boot.img with a stock boot.img (samfirmware sourced), and they are similar in terms of addresses and pagesizes. The ramfs file is also stock, taken from that same stock boot.img. The built kernel is a bit larger than the stock and I'm not sure if I should expect my built kernel to be exactly the same size, or if it's ok for it to be a few KBs different.
Any other parameters or configurations that I might be missing or should check? (And to samsungkid, were there any special steps that you took?)
Thank You!
ric105 said:
I've been able to create a zImage from the GT-S5300 open source kernel code, using the bcm21553_cori_04_defconfig as indicated by the accompanying readme file.
However, when I use this kernel to create a boot.img and download using Odin, I get a quick S5300 startup screen, then nothing.
At this point, I'm just trying to build a stock kernel, no modifications. I'm looking for helpful hints on where to find any debug or error messages that will help indicate what is going wrong. I can use Odin to put the prebuilt stock kernel back, and it boots ok once again.
I've compared my boot.img with a stock boot.img (samfirmware sourced), and they are similar in terms of addresses and pagesizes. The ramfs file is also stock, taken from that same stock boot.img. The built kernel is a bit larger than the stock and I'm not sure if I should expect my built kernel to be exactly the same size, or if it's ok for it to be a few KBs different.
Any other parameters or configurations that I might be missing or should check? (And to samsungkid, were there any special steps that you took?)
Thank You!
Click to expand...
Click to collapse
Thanks for bashing my thread...
Might be better to create your own ?
Will do.
samsungkid said:
Thanks for bashing my thread...
Might be better to create your own ?
Click to expand...
Click to collapse
Hadn't seen much traffic on S5300, saw you 'everything worked fine' comment, and thought I might find some tips here.
I will post a separate thread.
Regards
ric105 said:
Hadn't seen much traffic on S5300, saw you 'everything worked fine' comment, and thought I might find some tips here.
I will post a separate thread.
Regards
Click to expand...
Click to collapse
yes please - coz this thread is still open...
waiting for someone to reply for my last questions...
ric105 said:
I've been able to create a zImage from the GT-S5300 open source kernel code, using the bcm21553_cori_04_defconfig as indicated by the accompanying readme file.
However, when I use this kernel to create a boot.img and download using Odin, I get a quick S5300 startup screen, then nothing.
At this point, I'm just trying to build a stock kernel, no modifications. I'm looking for helpful hints on where to find any debug or error messages that will help indicate what is going wrong. I can use Odin to put the prebuilt stock kernel back, and it boots ok once again.
I've compared my boot.img with a stock boot.img (samfirmware sourced), and they are similar in terms of addresses and pagesizes. The ramfs file is also stock, taken from that same stock boot.img. The built kernel is a bit larger than the stock and I'm not sure if I should expect my built kernel to be exactly the same size, or if it's ok for it to be a few KBs different.
Any other parameters or configurations that I might be missing or should check? (And to samsungkid, were there any special steps that you took?)
Thank You!
Click to expand...
Click to collapse
have you checked command line?
Resolved by switching toolchains. OP query remains...
mr.harsh said:
have you checked command line?
Click to expand...
Click to collapse
No errors reported anywhere that I could find, but thanks for the response.
UPDATE: I resolved my original issue: toolchain was wrong. The readme from samsung tried to tell me, but I refused to listen... Once I changed to the Code Sourcery toolchain, the zImage loaded fine.
But back to samsungkid's issue....
I believe he is still trying to get his own custom module compiled into the kernel. I know that building a module separately as an LKM would work technically, but I don't know if that makes sense for the use case.
Regards
cleudde thetical
ric105 said:
No errors reported anywhere that I could find, but thanks for the response.
UPDATE: I resolved my original issue: toolchain was wrong. The readme from samsung tried to tell me, but I refused to listen... Once I changed to the Code Sourcery toolchain, the zImage loaded fine.
But back to samsungkid's issue....
I believe he is still trying to get his own custom module compiled into the kernel. I know that building a module separately as an LKM would work technically, but I don't know if that makes sense for the use case.
Regards
Click to expand...
Click to collapse
Yes, I would be glad if someone could help me with this...
still working on it
Thanks for every information you can give me !
Maybe I need to give you more details, so:
I downloaded the corresponding kernel for my samsung device.
Then I unpacked the file and opened the readme file, which states:
HOW TO BUILD KERNEL 2.6.35 FOR GT-S5300
1. How to Build
- get Toolchain
Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI.
Extract kernel source and move into the top directory.
$ cd common/
$ make bcm21553_cori_04_defconfig
$ make
2. Output files
- Kernel : kernel/common/arch/arm/boot/zImage
3. How to make .tar binary for downloading into target.
- change current directory to kernel/common/arch/arm/boot
- type following command
$ tar cvf GT-S5300_Kernel_Gingerbread.tar zImage
Click to expand...
Click to collapse
So I downloaded the appropriate toolchain and created my directories under /root/projects/android
[email protected]:~/projects/android# ls
infofiles kernel tarballs toolchain
Click to expand...
Click to collapse
In the directory infofiles are only the readme files from Samsung.
Kernel contains the extracted files from the archives, downloaded from Samsung.
tarballs contain all the tarballs meaning the kernel.tar.gz and the toolchain.tar.gz
toolchain contains the extracted files from toolchain
I then do all the thinks written in the readme file:
[email protected]:~/projects/android# cd kernel/common/
[email protected]:~/projects/android/kernel/common# make bcm21553_cori_04_defconfig
#
# configuration written to .config
#
Click to expand...
Click to collapse
and then I run into an error:
[email protected]:~/projects/android/kernel/common# make
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
arm-eabi-gcc: error trying to exec 'cc1': execvp: No such file or directory
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
Click to expand...
Click to collapse
So could please, anybody help me with me issue?
Thank you !
no one ?
Have you EXPORTed variables to point to the compiler directory?
A guess, but is the error message saying it cannot find the cross compile toolchain? Generally, you need to either export a couple of variables, or add them to the make command line. Something like:
ARCH=arm SUBARCH=arm CROSS_COMPILE= /home/yourhome/toolchains/.../arm-none-eabi- make
Hope it helps.
ric105 said:
A guess, but is the error message saying it cannot find the cross compile toolchain? Generally, you need to either export a couple of variables, or add them to the make command line. Something like:
ARCH=arm SUBARCH=arm CROSS_COMPILE= /home/yourhome/toolchains/.../arm-none-eabi- make
Hope it helps.
Click to expand...
Click to collapse
Thanks.
I added the path to the toolchain directly into the $PATH variable...
Even tried your above statement - the same error again
Maybe need this...
You may need to edit the Makefile:
export KBUILD_BUILDHOST := $(SUBARCH)
ARCH ?=arm
#this is original ---> CROSS_COMPILE ?=/home/aniruddh/sgy/arm-eabi-4.4.3/bin/arm-eabi-
CROSS_COMPILE ?=/home/your_user_name_here/arm-2009q3/bin/arm-none-eabi-
CROSS_COMPILE ?= $(CONFIG_CROSS_COMPILE:"%"=%)
Then you will run 'make' without export any variables.
Regards
tokomotxo said:
You may need to edit the Makefile:
export KBUILD_BUILDHOST := $(SUBARCH)
ARCH ?=arm
#this is original ---> CROSS_COMPILE ?=/home/aniruddh/sgy/arm-eabi-4.4.3/bin/arm-eabi-
CROSS_COMPILE ?=/home/your_user_name_here/arm-2009q3/bin/arm-none-eabi-
CROSS_COMPILE ?= $(CONFIG_CROSS_COMPILE:"%"=%)
Then you will run 'make' without export any variables.
Regards
Click to expand...
Click to collapse
THAT, did the trick!
Thanks a lot for this awesome hint !
I own you
samsungkid said:
THAT, did the trick!
Thanks a lot for this awesome hint !
I own you
Click to expand...
Click to collapse
Thanks to you :good:
tokomotxo said:
Thanks to you :good:
Click to expand...
Click to collapse
Maybe you could answer me another question?
When I want to compile a normal .c program (like a Hello World Program) for my Samsung phone, how would I proceed?
Do I have to write a Makefile for this?
Thanks

[Q] CM KitKat build problem - add prebuilt package?

Hi, I'm trying to build CM KitKat for the Optimus S/V (unsupported by CM). The build is crashing out trying to link libwebviewchromium.so.
It gives dozens and dozens of errors like this:
external/chromium_org/content/browser/android/browser_media_player_manager.cc:70: error: relocation overflow in R_ARM_THM_CALL
At the end it prints this:
collect2: error: ld returned 1 exit status
make: *** [/home/dbrown/cm11/out/target/product/thunderc/obj/SHARED_LIBRARIES/libwebviewchromium_intermediates/LINKED/libwebviewchromium.so] Error 1
It may be a problem with insufficient memory on my build machine (Core 2 Duo laptop with 3 gb ram). For the time being, or in case that's not the problem I'm looking for a work-around. I looked in the Android.mk file for external/chromium_org and saw this:
# Don't include anything if the product is using a prebuilt webviewchromium.
ifneq ($(PRODUCT_PREBUILT_WEBVIEWCHROMIUM),yes)
Is it possible, and if so how can I add a prebuilt webview library so I can get past this error? I just want to get something built for now so I can test it. This would be the first successful build for this device. Thanks!
Open the "external/chromium_org/content/browser/android/browser_media_player_manager.cc"
And go to line Num. 70..
Youd better to see "https://bugs.launchpad.net/binutils-linaro/+bug/641126"
In that case, Loïc Minier was solve the add physical ram.
To try swap memory!
I know this is a bit necro but I thought I'd add.
I got the same error in libchromium. 16Gb ram. Went down to -j1 on make and it compiled. I have a 6-core chip :/
Similar query
For doing the android clean build faster I wanted to avoid building libwebviewchromium. Can someone provide the exact changes needed for this. Is libwebviewchromium.so enough ? or do we have to have related jars as well from first build.
@skinbark @winvinay add the following line to your devices BoardConfig.mk. (I.e. YOURSOURCEFOLDER/device/MANUFACTURER/DEVICE/BoardConfig.mk e.g. ~/AOSP/device/asus/grouper/BoardConfig.mk for me):
Code:
PRODUCT_PREBUILT_WEBVIEWCHROMIUM := yes
Just remember to add libwebviewchromiun.so from another ROM to /system/lib/ afterwards.

[HELP] Compiling Android from source (sm-g360f)

Hi there,
I have Samsung Galaxy Core Prime LTE and I could not find any custom ROMs so I decided that I will try to compile it myself. I downloaded the LineageOS source code from git (cm 14.1), the device trees and kernel from here: github/MSM8916-Samsung, and the samsung vendor files from the extraxt-files.sh script. The qcom-common files from here: github/CyanogenMod/android_device_samsung_qcom-common. Then I set up the environment (source build/envsetup.sh), ran breakfast and everything went fine. And then came brunch... It's running for about 40-50 minutes, and then stopes because "ninja: build stopped: subcommand failed". Here's the output from my terminal: https:/ /drive.google.com/fi le/d/0Bzbi _UspTWqac3ZkV2RhRjJGeW8/view?usp=drivesdk (remove spaces - sorry for that, but I cannot add links yet)
If the ninja log is needed I will post it.
Can someone help me to understand the code and find out why it is failing?
(I am new to developing stuff, but I have already compiled programs back in the days, and I am familiar with Linux, which is my daily driver)
what version of linux are you using at the moment?
Ubuntu 17.04, but I have also tried it on 16.10 last week, and openjdk-8
wasowski02 said:
Ubuntu 17.04, but I have also tried it on 16.10 last week, and openjdk-8
Click to expand...
Click to collapse
I can't speak for others but I have not had success building anything android on 15.10,16.04,16.10... I always end up on a wild goose chase with all the compiling errors. I have consistently compiled without errors using 14.04 with oracle java 8 as that is what many of the manufacturers are using to make their own builds. If or oracle spits errors with 14.04 i try to use the rule of thumb and thats openjdk-6 and jre for LP, openjdk-7 and jre for MM and openjdk-8 for nougat builds but im only working on MM builds at the moment so your results may vary. Hope this helps a bit, just remember you can use sudo update-alternatives --display java to switch versions on the fly if needed and make sure you incorporate Google prebuilts as well. good luck ?
Sent from my LGLS676 using Tapatalk
Sands207 said:
I can't speak for others but I have not had success building anything android on 15.10,16.04,16.10... I always end up on a wild goose chase with all the compiling errors. I have consistently compiled without errors using 14.04 with oracle java 8 as that is what many of the manufacturers are using to make their own builds. If or oracle spits errors with 14.04 i try to use the rule of thumb and thats openjdk-6 and jre for LP, openjdk-7 and jre for MM and openjdk-8 for nougat builds but im only working on MM builds at the moment so your results may vary. Hope this helps a bit, just remember you can use sudo update-alternatives --display java to switch versions on the fly if needed and make sure you incorporate Google prebuilts as well. good luck ?
Click to expand...
Click to collapse
Then I will try 14.04 and see what happens. Thanks for help
@Sands207 Is there by any chance a site where you can learn to do this? Tutorial for noobs of sort.
Sent from my SM-N920P using Tapatalk
ninja_unmatched said:
@Sands207 Is there by any chance a site where you can learn to do this? Tutorial for noobs of sort.
Click to expand...
Click to collapse
Yes, luckily for us xda members we have our own Android college built right into xda https://forum.xda-developers.com/general/xda-university its a great starting point and rom compiling guide is also there. Its all aimed to help new folks find their way ? jump right in ?
If you need TWRP for it I have it. It was built by blaz3r64, but since AA51 is down I can upload it for you. I can confirm that it works on both the ST Galaxy Core Prime and the Boost Prevail LTE.
Sent from my XT1609 using Tapatalk
RealWelder said:
If you need TWRP for it I have it. It was built by blaz3r64, but since AA51 is down I can upload it for you. I can confirm that it works on both the ST Galaxy Core Prime and the Boost Prevail LTE.
Click to expand...
Click to collapse
So I have already downloaded the official TWRP, but thanks for your interest.
I have tried to compile using ubuntu 14.04 (with openjdk-8) as @Sands207, but I get this error:
Code:
FAILED: /bin/bash -c "prebuilts/misc/linux-x86/bison/bison -d --defines=/home/karol/android/system/out/host/linux-x86/obj/STATIC_LIBRARIES/libaidl-common_intermediates/aidl_language_y.h -o /home/karol/android/system/out/host/linux-x86/obj/STATIC_LIBRARIES/libaidl-common_intermediates/aidl_language_y.cpp system/tools/aidl/aidl_language_y.yy"
/bin/bash: prebuilts/misc/linux-x86/bison/bison: No such file or directory
wasowski02 said:
So I have already downloaded the official TWRP, but thanks for your interest.
I have tried to compile using ubuntu 14.04 (with openjdk-8) as @Sands207, but I get this error:
Code:
FAILED: /bin/bash -c "prebuilts/misc/linux-x86/bison/bison -d --defines=/home/karol/android/system/out/host/linux-x86/obj/STATIC_LIBRARIES/libaidl-common_intermediates/aidl_language_y.h -o /home/karol/android/system/out/host/linux-x86/obj/STATIC_LIBRARIES/libaidl-common_intermediates/aidl_language_y.cpp system/tools/aidl/aidl_language_y.yy"
/bin/bash: prebuilts/misc/linux-x86/bison/bison: No such file or directory
Click to expand...
Click to collapse
I recommend trying this keychain as it has full support for what you are attempting https://forum.xda-developers.com/showthread.php?t=3606941 I have tried it myself but Id recommend cleaning your build folder before incorporating them, maybe even a reboot as well. i had forgotten about this but it has far more tools than the normal keychain.
Sent from my LGLS676 using Tapatalk
---------- Post added at 04:29 PM ---------- Previous post was at 04:22 PM ----------
remember to select the right architecture ??
Sent from my LGLS676 using Tapatalk
Sands207 said:
I recommend trying this keychain as it has full support for what you are attempting https://forum.xda-developers.com/showthread.php?t=3606941 I have tried it myself but Id recommend cleaning your build folder before incorporating them, maybe even a reboot as well. i had forgotten about this but it has far more tools than the normal keychain.
Sent from my LGLS676 using Tapatalk
---------- Post added at 04:29 PM ---------- Previous post was at 04:22 PM ----------
remember to select the right architecture ?
Click to expand...
Click to collapse
So I downloaded the new toolchain/keychain/cross compiler (just to make sure - this is the same, yes?), but I cannot find how to choose it to compile android. The official post says:
Code:
# for arm64
export CROSS_COMPILE=$(pwd)/bin/aarch64-linux-gnu-
but as I'm not compiling the kernel I assume it is not what I need (I think) and
Code:
echo $CROSS_COMPILE
does not return anything by default. If I should have used the export function then which file should I choose, because there are many (-strip, -strings, -size, -run, etc.).
There is a directory called toolchain (it contains only binutils) in the folder containing the source code. Should I add a folder called gcc and put the files there? Or maybe I have to run brunch with some options or change an entry in a configuration/make file?
I use the aarch64 version, but not the newest (20170515 not 20170520).
wasowski02 said:
So I downloaded the new toolchain/keychain/cross compiler (just to make sure - this is the same, yes?), but I cannot find how to choose it to compile android. The official post says:
but as I'm not compiling the kernel I assume it is not what I need (I think) and
does not return anything by default. If I should have used the export function then which file should I choose, because there are many (-strip, -strings, -size, -run, etc.).
There is a directory called toolchain (it contains only binutils) in the folder containing the source code. Should I add a folder called gcc and put the files there? Or maybe I have to run brunch with some options or change an entry in a configuration/make file?
I use the aarch64 version, but not the newest (20170515 not 20170520).
Click to expand...
Click to collapse
I do think as you said you will need to run brunch but resetting up your build & source environment to use the new keychain as you attempted to switch from one keychain to the other as well may help if this doesn't work as well take a look at your build configuration. rc file and make sure you don't have double entries or the new keychain missing i usually import the prebuilts i need as I am using arm architecture at the moment but i either download the individual keychain i need and place it in my source folder when i setup my build environment to be added to the build along with my sources before i run lunch because my source folder is untouched by me besides that at that point. I'll be home in an hour or so I'm going to see if i can track down some info to help you get untangled but i do recommend downloading the folder and making a gcc folder with the toolchain folder for arm64 as you said and and adding it to your build ensuring it is clean besides what you need and adding it then attempt to compile again.
I'm​ not sure if I should use aarch64. I have an armv7-a-neon (so 64-bit) and the internet says that aarch64 and arm64 is pretty much the same, but maybe I am wrong and I should use arm instead. But I think that does not matter until I put the new toolchain both to the aarch64 and arm directory (I guess the compilation process will choose the right one automatically). So I've put the compilers into prebuilts/gcc/linux-x86/... folders, but should I delete the old compilers? And then run the environment setup again (all this stuff starts to make sense to me ?)
Sent from my SM-G360F using Tapatalk
wasowski02 said:
I'm​ not sure if I should use aarch64. I have an armv7-a-neon (so 64-bit) and the internet says that aarch64 and arm64 is pretty much the same, but maybe I am wrong and I should use arm instead. But I think that does not matter until I put the new toolchain both to the aarch64 and arm directory (I guess the compilation process will choose the right one automatically). So I've put the compilers into prebuilts/gcc/linux-x86/... folders, but should I delete the old compilers? And then run the environment setup again (all this stuff starts to make sense to me )
Sent from my SM-G360F using Tapatalk
Click to expand...
Click to collapse
Yes you should delete the old ones and set up your enviroment again and it should include them. Also yes the compile proccess should pick the correct one in your case as long as you include them and you have, you are heading in the right direction for sure. :good:
Sands207 said:
Yes you should delete the old ones and set up your enviroment again and it should include them. Also yes the compile proccess should pick the correct one in your case as long as you include them and you have, you are heading in the right direction for sure. :good:
Click to expand...
Click to collapse
So I deleted the old ones and I get this error:
Code:
ninja: error: 'prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin/arm-linux-androideabi-strip', needed by '/home/karol/android/system/out/target/product/coreprimeltexx/obj/lib/libdl.so', missing and no known rule to make it
I guess it's because somewhere in a configuration file there is an entry for the old compiler. I have deleted the out directory and played with the envsetup.sh file (about line 210 there is something about compilers),
Code:
# defined in core/config.mk
targetgccversion=
targetgccversion2=
export TARGET_GCC_VERSION=$targetgccversion
# The gcc toolchain does not exists for windows/cygwin. In this case, do not reference it.
export ANDROID_TOOLCHAIN=
export ANDROID_TOOLCHAIN_2ND_ARCH=
local ARCH=$(get_build_var TARGET_ARCH)
case $ARCH in
x86) toolchaindir=x86/x86_64-linux-android-$targetgccversion/bin
;;
x86_64) toolchaindir=x86/x86_64-linux-android-$targetgccversion/bin
;;
arm) toolchaindir=arm/arm-linux-androideabi-$targetgccversion/bin
;;
arm64) toolchaindir=aarch64/aarch64-linux-android-$targetgccversion/bin;
toolchaindir2=arm/arm-linux-androideabi-$targetgccversion2/bin
;;
mips|mips64) toolchaindir=mips/mips64el-linux-android-$targetgccversion/bin
;;
*)
echo "Can't find toolchain for unknown architecture: $ARCH"
toolchaindir=xxxxxxxxx
;;
esac
but this did not work either. The ninja files don't contain any gcc configuration. So where can I find the right configuration file? (I can't find the suggested configuration.rc file)
wasowski02 said:
So I deleted the old ones and I get this error:
I guess it's because somewhere in a configuration file there is an entry for the old compiler. I have deleted the out directory and played with the envsetup.sh file (about line 210 there is something about compilers),
but this did not work either. The ninja files don't contain any gcc configuration. So where can I find the right configuration file?
Click to expand...
Click to collapse
I usually compile using clang or maven as I only build AOSP atm https://ninja-build.org/manual.html this page includes directions that should assist you. Do you have maven or clang installed on your linux box?
Sands207 said:
I usually compile using clang or maven as I only build AOSP atm https://ninja-build.org/manual.html this page includes directions that should assist you. Do you have maven or clang installed on your linux box?
Click to expand...
Click to collapse
So it seems that nor klang nor maven is installed on my machine (but as my computer claims ninja is not installed either I guess that they may be installed somewhere in the build directories). Should I try them instead of ninja?
wasowski02 said:
So it seems that nor klang nor maven is installed on my machine (but as my computer claims ninja is not installed either I guess that they may be installed somewhere in the build directories). Should I try them instead of ninja?
Click to expand...
Click to collapse
yes absolutely
Sands207 said:
yes absolutely
Click to expand...
Click to collapse
So what I understand is:
(1) Install maven or clang (let's say clang because I found it in the official ubuntu repository)
(2) Configure brunch to use clang instead of ninja
So I checked the internet if there are any options I can use with brunch to run clang, but I didn't find any. Also looked through the envsetup.sh file, but there is nothing there, or I missed it.
wasowski02 said:
So what I understand is:
(1) Install maven or clang (let's say clang because I found it in the official ubuntu repository)
(2) Configure brunch to use clang instead of ninja
So I checked the internet if there are any options I can use with brunch to run clang, but I didn't find any. Also looked through the envsetup.sh file, but there is nothing there, or I missed it.
Click to expand...
Click to collapse
tonight i will try doing some digging to see if i can help you. im away from my computer right now but ill do what i can. i would try would maven. clang assists with aosp primarily but maven should work for you as far as using a custom command to run maven, log out or reboot after you install it and run brunch as you normally would also please read this https://clang.llvm.org/comparison.html

Categories

Resources