Database Develop

[Q][Sprint] Kernel compile

I'm having a problem compiling a kernel for a
Sprint CDMA 7" GT.
I use unpack-initramfs to grab the rootfs from
the original EF17 kernel.
I put that dir location in CONFIG_INITRAMFS_SOURCE=""
in the p1_defconfig file in Kernel/arch/arm/configs
In the kernel directory I issue the commands:
make clean
make p1_defconfig
make
The kernel compiles fine, but there's a 3Mb
difference between the original EF17 kernel
and the one I compile.
If I extract the rootfs from my kernel it's
the exact same as the one extracted from the
original. Have I missed a step? I've done this in the past for my Epic 4G.

i have similar issues that i've been battling with..the kernel coming out smaller isn't 100% indicative of a bad compile...i bet your kernel will boot but 3g (and possibly sound and more) don't work
i emailed samsung open source explaining what i did to compile and this was their response.
my query:
I downloaded the source code for the SPH-P100. I followed the directions in the README_kernel.txt to compile. As well as setting up the unmodified initramfs from the stock kernel. I can boot the kernel on the device however the resulting zImage size is 4.2MB compared to the 5.7MB zImage pulled from the device. I've not made any extra changes to the config or anything else other than what is needed to compile. Despite the size difference using the unmodified p1_defconfig (except setting the initramfs path), the problem that I have is the 3G radio will not start. I get a circle with the slash in the status bar and any dialer codes that pertain to the radio just force close. dmesg and logcats do not turn up any useful information or errors. Flashing the stock kernel back to the device alleviates the issue. So my questions are as follows: Is the source code complete? If so what could I be missing that would cause the radio to not start? Thank you in advance for any input on the issue.
Click to expand...
Click to collapse
and their response:
[SAMSUNG OSRC COMMENTS DELIVERY NOTIFICATION]
Dear customer,
Thank you for your continuous interest on our product.
We received your request on OSRC.
We reviewed your inquiry but unfortunately we couldnt publish the source code for some modules, because it is loadable kernel module and contains samsung proprietary code.
We published open source codes that are covered licenses which have obligation of publishing source code. (ex. GPL, LGPL, MPL...etc)
But we do not guarantee that open source code is excutable in target device. We are sorry for not giving you an correct anwser upto your satisfaction.
We are sorry for not giving you an correct anwser upto your satisfaction.
Thank you!
Sincerely yours
Click to expand...
Click to collapse
so for now until we can figure out what is missing we are out of luck as they are no help
when i have time i'll gladly work with you, oldmacnut, and any one else that can contribute into making a working base kernel from source

Thanks. This truly sucks and will impact my future choice of product purchases.

[DEVS] You too can build a CM-based AOSP ROM

Obviously, I am going to be cleaning up some bugs with the CM7 build...
But, for those of you who might be inclined to develop a CM-based AOSP ROM, feel free to check out my github source to see what's involved:
https://github.com/Hashcode
Or you can:
repo init -u https://[email protected]/Hashcode/cm4D3.git
repo sync
To pull the entire set of android files that I use for compiling the current build.
Please note that the Board Config is currently setup to generate Safestrap .zip files.

Great job
Thank you for everything you have done for the droid 3!

Is there a kitchen for DROID 3 roms. Running windows 7
Sent from my DROID3 using xda premium

You need to be running Linux to do this hardcore kind of stuff.

Like Ubuntu I had it set up in VB and detain. Was just wondering if there was some thing for Motorola roms out there. I have had HTC phones this my first moto with android on it.
Sent from my DROID3 using xda premium

I'm starting to tinker with building (learning, actually) ROMs. I'm running Linux Mint Debian - has there been a kitchen built for D3?

Hashcode said:
repo init https://[email protected]/Hashcode/cm4D3.git
Click to expand...
Click to collapse
That should be
Code:
repo init -u git://github.com/Hashcode/cm4D3.git -b gingerbread
or whatever URL you want to use from the access URL box at https://github.com/Hashcode/cm4D3.
And of course "gingerbread" could be "ics" if your excitement about being on the bleeding edge overrides what should be a fairly sensible fear reaction to the term "bleeding edge".
@Hashcode: You don't use your own ALSA repos? (Comparing with my own generated manifest for your project...)
Also, are you planning on pulling newer Gingerbread manifest changes into your tree? I noticed CyanogenMod have gained a u8150 device tree, and I happen to have one of those, but your manifest doesn't list it...
Ooops. I have a u8510. >_< But the question stands...

TBBle said:
That should be
Code:
repo init -u git://github.com/Hashcode/cm4D3.git -b gingerbread
or whatever URL you want to use from the access URL box at https://github.com/Hashcode/cm4D3.
And of course "gingerbread" could be "ics" if your excitement about being on the bleeding edge overrides what should be a fairly sensible fear reaction to the term "bleeding edge".
@Hashcode: You don't use your own ALSA repos? (Comparing with my own generated manifest for your project...)
Also, are you planning on pulling newer Gingerbread manifest changes into your tree? I noticed CyanogenMod have gained a u8150 device tree, and I happen to have one of those, but your manifest doesn't list it...
Ooops. I have a u8510. >_< But the question stands...
Click to expand...
Click to collapse
Thank you for pointing out that my repo init line was wrong. I fixed it for those that were having issues.
Also, for those watching my manifest for ICS, I'm getting an error when syncing:
error: revision refs/heads/master in manifests not found
I'm trying to fix that. Correction: Fixed it and double-checked with a repo sync.
Some quick answers:
- I tried to customize the alsa source to fix some of the audio issues. But it ended up being a bit more complex than just changing ALSA. Motorola added a layer into the audio system for handling HDMI audio and in call audio volume.
When you build stock AOSP Gingerbread using the alsa drivers, the libaudio.so file ends up being all of the ALSA calls. If you examine the libaudio from the D3, you'll see that it is nothing of the sort. It's the customized mixer lib for RDS voice and HDMI audio. There's another lib from the phone: libaudio_ext.so which ends up being the alsa calls.
All of which made customizing just the alsa code risky at best as the further away from the version of alsa that was used on the phone, the less likely that the custom libaudio would work.
I probably still have the unfinished hardware_alsa git out on github, but it's not active in the current build.
- I can occasionally check for updates to the CM7 manifest and add them, or if you fork the manifest and add it in there that works as well.
Side Note: I may need to pick your brain on an EGL 0x0500 erorr I'm getting in the ICS code. I'm fairly certain it's an enum value that our version of the PowerVR drivers aren't set to handle, but I'd like to confirm that for my troubleshooting. And it seems that you might have some knowledge in that area

Where/how does someone begin working on building a ROM once they've downloaded these files? I'd rather dive into code and learn Android rather than using a menu driven wizard. Is there a tutorial somewhere? What tools are needed?
Sent from my DROID3 using XDA App

Phibernaut said:
Where/how does someone begin working on building a ROM once they've downloaded these files? I'd rather dive into code and learn Android rather than using a menu driven wizard. Is there a tutorial somewhere? What tools are needed?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
This would be the starting point that you're looking for:
http://source.android.com/

Hashcode said:
Side Note: I may need to pick your brain on an EGL 0x0500 erorr I'm getting in the ICS code. I'm fairly certain it's an enum value that our version of the PowerVR drivers aren't set to handle, but I'd like to confirm that for my troubleshooting. And it seems that you might have some knowledge in that area
Click to expand...
Click to collapse
Some, but probably not enough. I'm happy to look, but I'm actually moving internationally tomorrow so I may not have 'net access for a week or so. >_< (That's why I've been trying so hard to get backup working. ^_^)
Once I'm settled in I will probably use fdisk to repartition my device or have a poke at hacking sd-ext support into safestrap, so I can start playing with custom ROMs.
Did you see my safestrap-ME863 nandroid patch in the Safestrap thread, BTW? It's got a couple of TODOs, but seems safe and roughly correct to me. http://forum.xda-developers.com/showpost.php?p=19683372&postcount=249
It could also form the basis for detecting when /preinstall can't be used as safe-system although I didn't look to see if there's already code to do that.

Does anyone know of a site where I can peek at reference code for random things (Apps, Kernal etc.)? It'll make it easier to understand how the code works. I haven't look at any code yet so I don't even know what language apps and the os are programmed in. (Java, C, C++, Ruby)
Sent from my D3-CM7-SS using xda premium

tenchi19134 said:
Does anyone know of a site where I can peek at reference code for random things (Apps, Kernal etc.)? It'll make it easier to understand how the code works. I haven't look at any code yet so I don't even know what language apps and the os are programmed in. (Java, C, C++, Ruby)
Click to expand...
Click to collapse
Just pull down the repo as Hashcode describes in this thread - you'll have all of the Android source. To the best of my knowledge, it comprises of mostly C, C++, and Java, but there is probably a smathering of some other things like ASM, perl, BASH, etc.
And to those who are asking if there is a kitchen, there is, it's called make

S5830i defconfig use cooperve_defconfig when building from source

Hi friends of XDA,
I think this might be helpfull for some of you trying to compile kernel from source for S5830i, for the first time.
If you are following the great tutorials to build your first kenrel like:
http://forum.xda-developers.com/showthread.php?t=1748297 from thewadegeek
The first thing taht will happen, is that you cant pull defconfig from /proc/config.gz for S5830i.
Why? There is no such file for your device in there.
Normally the next you will do, is go to the stock sources readme file. And will find out the defconfig is totoro_defconfig
You will compile the kernel with no errors, and you will feel very happy, until you flash your recently compiled kernel and see that you get stuck in the boot_logo screen.
Ok, dont panic, solution is very easy. Samsung readme file is a general readme.
Here is the quid of the question:
totoro_defconfig is not the correct defconfig for S5830i.
S5830i defconfig is bcm21553_cooperve_defconfig
You will find this defconfig in the sources, at:
common/arch/arm/configs folder
Hope this helped. If it helped dont doubt to press the thanks button, this will be very appreciated.
Thank you and sweet kernel development.

Samsung's readme file isn't general, they just took the Galaxy Y's readme (even the model says GT 5360).
What's stranger is that the CHN sources have the correct info.
Also, I didn't need to pull anything. I just used the default config:
Code:
export ARCH=arm
export CROSS_COMPILE=<path>
make bcm21553_cooperve_defconfig
make -j16

Hi GermainZ,
Thats right,never had a look at the CHN readme. I wonder why the other sources are uploaded looooollll strange Samsun guys.
Never the less, forgot to post the next in the original thread.
I recomend to have an original copy of bcm21553_cooperve_defconfig as when you start modifing it some options may fail and its recomended to have a fresh one to copy paste quicly.
Even more for my kernel i copy original file and rename it to nit_defconfig and give it a version number ej nit01_defconfig, its agood practice have latest working defconfig as you will be modifying the file a lot, btw nit is how i call my kernel as you all ready know, this comes from new innovative technologies the name of one of my companys i created recently
But good appreciation GermainZ is always my pleasure to talk with you
Sent from my GT-S5830i using xda app-developers app

Thanks for your tips bro! You had a significant part in booting my kernel. Will add u in credits

No problem hell_lock.
Thank you.
Sent from my GT-S5830i using xda app-developers app

[Q]Building From Source (Single Modules / Bare Minimum Version)

My Question to the Dev's is is there a Guide on How to Build Single APP Packages eg Calculator from Source Without building the entire android from Source is possible to build eg libjpeg from source as a single module.
i have tried the mmm command all it did was spit out errors you fix one get ten more and so on
I also tried using NDK by inserting the open source libs into a jni folder and modifying Android.mk to look similar to the sample jni resulted in errors this is the only Guide i can't find as there many on building entire android but sometime one only needs specific modules and not entire build.
If above not possible is there a bare minimum version where it only builds android core frameworks and like one lib /app ?

i did not try this .
u can download the package like if u want trebucket launcher then download full android_packages_apps_trebuckhet.
recompile it to get the trebucket apk
once againg i did not try this out

defcomg said:
My Question to the Dev's is is there a Guide on How to Build Single APP Packages eg Calculator from Source Without building the entire android from Source is possible to build eg libjpeg from source as a single module.
i have tried the mmm command all it did was spit out errors you fix one get ten more and so on
I also tried using NDK by inserting the open source libs into a jni folder and modifying Android.mk to look similar to the sample jni resulted in errors this is the only Guide i can't find as there many on building entire android but sometime one only needs specific modules and not entire build.
If above not possible is there a bare minimum version where it only builds android core frameworks and like one lib /app ?
Click to expand...
Click to collapse
Mmm won't help as it needs to link against other parts of the system. That's why you need to do a full build before you can mmm
In theory you can take the app and try to import it into eclipse, and regard it just as an app project.

I tried to build twrp for A605k but..

there is no such kernel,device tree,vendor for my device.
I could build device tree via twrpbuilder tree generator,
but kernel cannot be found in opensource release center.
why am i need A605k? not F or FN or else?
that's because when i used A605FN recovery it has so many errors... and it makes me build twrp for A605K.
not for other models..
but.. i failed,
device tree built via twrpbuilder tree generator doesn't have omni.dependencies file
so, what do you guys think how can i fix those annoying things?
I know, this is not a question area, but i want to make Discussion with you guys to get a idea

Well if your trying to build a device tree and kernel source and vendor start with downloading android source in linux there are many great guides for this then download the sources for the A600F/FN or any other current model of the A600 then there will be a file in the folder for whichever source you downloaded that will allow you to pull resources from your phone like kernel recovery device vendor files ect.. use that and then import it to the same folder than try to build TWRP and test it to see if you get a working build if not then go back and try again their are many sources for learning how to compile twrp for devices that dont have it read those and try again.
Sent from my [device_name] using XDA-Developers Legacy app

tmvkrpxl0 said:
there is no such kernel,device tree,vendor for my device.
I could build device tree via twrpbuilder tree generator,
but kernel cannot be found in opensource release center.
why am i need A605k? not F or FN or else?
that's because when i used A605FN recovery it has so many errors... and it makes me build twrp for A605K.
not for other models..
but.. i failed,
device tree built via twrpbuilder tree generator doesn't have omni.dependencies file
so, what do you guys think how can i fix those annoying things?
I know, this is not a question area, but i want to make Discussion with you guys to get a idea
Click to expand...
Click to collapse
I did find the kernel and source here: http://opensource.samsung.com/recep...menu_item=mobile&classification1=mobile_phone
(page 44 for SM-A605FN - A605FNXXU1ARD7)
I would like to build it myself, but my android development knowledge is limited (i do have a solid linux knowledge though).
Is this guide obsolete (https://forum.xda-developers.com/showthread.php?t=1943625)?
If yes, anyone knows where can i find an up-to-date one?
If not, any idea where BoardConfig.mk can be found?

Where can we find a guide on how to build a twrp? I would really like to learn how to do it