Database Info

[Q] Source Code Base to build ROMs for SGS4G

Hello All,
I am new to the android platform. So please forgive if this is too trivial a question.
1. How do I obtain source code for a specific platform and a specific phone?
Is it segregated that way?
2. How do I build ROM and package it to deploy on the phone?
Please provide pointers to these and I am willing to go through the documents/literature. Please help.
Thanks in advance!!

Two answers first question go in general section second start here http://forum.xda-developers.com/showthread.php?t=1117554 very good read hope this helps
sent from gingerbread 2.3.3 sgs4g ROOTED

rose2jam said:
Two answers first question go in general section second start here http://forum.xda-developers.com/showthread.php?t=1117554 very good read hope this helps
sent from gingerbread 2.3.3 sgs4g ROOTED
Click to expand...
Click to collapse
Thanks for the quick response! I have been going over that thread quite extensively but I can't seem to locate threads for
1. How to get the source code for the instrument( SGS4G) ?
2. How to build a complete ROM which is flashable? Basically, How to package it for deployment, like the other developers do on this forum.

androcton said:
Thanks for the quick response! I have been going over that thread quite extensively but I can't seem to locate threads for
1. How to get the source code for the instrument( SGS4G) ?
2. How to build a complete ROM which is flashable? Basically, How to package it for deployment, like the other developers do on this forum.
Click to expand...
Click to collapse
You didn't post in the right section, this needs to go in the general section.
You'll need to download the phone's source:
https://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=t959v
You should grab both files there. You'll need to build this on Linux or anything that has G++ for ARM.

FBis251 said:
You didn't post in the right section, this needs to go in the general section.
You'll need to download the phone's source:
https://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=t959v
You should grab both files there. You'll need to build this on Linux or anything that has G++ for ARM.
Click to expand...
Click to collapse
Thank you so much! I am already onto it!

Moved to proper forum.

androcton said:
Thank you so much! I am already onto it!
Click to expand...
Click to collapse
Did you ever get it working? I also found Dr. Honk's public git here:
https://github.com/drhonk/android_device_samsung_sgs4g
You can see the source for the Bali kernel here:
https://github.com/drhonk/Bali-V4G
Tell me how it goes.

FBis251,
Thanks for the resources! Currently I am still trying to get my dev-env setup properly, somehow have some installation/setup issues with the GNU/LINUX ARM toolchain. Meanwhile, I could build the kernel from the android base from source.android.com.
I have the system.img and other files in the out directory. The build went through but with lot of warnings. Here is the buildlog. Please let me know if something is amiss. Thanks!
Assuming the build went fine, I am not quite sure how to load that onto the device. I am trying to run an emulator though....will get back on that.

androcton said:
FBis251,
Thanks for the resources! Currently I am still trying to get my dev-env setup properly, somehow have some installation/setup issues with the GNU/LINUX ARM toolchain. Meanwhile, I could build the kernel from the android base from source.android.com.
I have the system.img and other files in the out directory. The build went through but with lot of warnings. Here is the buildlog. Please let me know if something is amiss. Thanks!
Assuming the build went fine, I am not quite sure how to load that onto the device. I am trying to run an emulator though....will get back on that.
Click to expand...
Click to collapse
Have you tried looking at:
http://source.android.com/source/building.html
Apparently you can just flash the image you just made... Try to see if you can open the .img as a .tar...?
I'm having trouble compling the bali kernel... I'll try again tomorrow.

FBis251 said:
Have you tried looking at:
http://source.android.com/source/building.html
Apparently you can just flash the image you just made... Try to see if you can open the .img as a .tar...?
I'm having trouble compling the bali kernel... I'll try again tomorrow.
Click to expand...
Click to collapse
Hi FBis251,
Can you please tell me how did you go about setting up the dev-env(the cross compiling toolchains). Are you using linux( which flavor, I am using Ubuntu 11.04 Natty Narwhal). I have some problems setting up the toolchains...as mentioned in the below link
https://opensource.samsung.com/recep...rchValue=t959v
Any ideas??

The readme from the opensource site says:
Code:
HOW TO BUILD KERNEL
1. Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI.
2. Extract kernel source and move into the top directory.
3. Execute 'make vibrantplus_rev00_defconfig'.
4. Execute 'make' or 'make -j<n>' where '<n>' is the number of multiple jobs to be invoked simultaneously.
I just googled thw 2009q3-68 version since I couldn't find it on the site after signing up and came across this:
http://www.codesourcery.com/sgpp/lite/arm/portal/release1033
I actually haven't gotten the kernel to compile without errors yet, and I haven't tried building the platform source until later today. You'll have to modify the makefile, look for the variable called CrossCompile and set it to the main /bin folder from the CodeSourcery toolchain.
Should be something like
Code:
CROSS_COMPILE ?= /home/user/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi-
I'll give you more details later, I'm still learning as I go too.
Also, something I came across to speed things up when you do the make, apparently if you have a quadcore processor, you can use make -j 8 (or just multiply however many cores you have by 2) and the compile should run as fast as possible.
Keep me posted.

FBis251 said:
The readme from the opensource site says:
Code:
HOW TO BUILD KERNEL
1. Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI.
2. Extract kernel source and move into the top directory.
3. Execute 'make vibrantplus_rev00_defconfig'.
4. Execute 'make' or 'make -j<n>' where '<n>' is the number of multiple jobs to be invoked simultaneously.
I just googled thw 2009q3-68 version since I couldn't find it on the site after signing up and came across this:
http://www.codesourcery.com/sgpp/lite/arm/portal/release1033
I actually haven't gotten the kernel to compile without errors yet, and I haven't tried building the platform source until later today. You'll have to modify the makefile, look for the variable called CrossCompile and set it to the main /bin folder from the CodeSourcery toolchain.
Should be something like
Code:
CROSS_COMPILE ?= /home/user/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi-
I'll give you more details later, I'm still learning as I go too.
Also, something I came across to speed things up when you do the make, apparently if you have a quadcore processor, you can use make -j 8 (or just multiply however many cores you have by 2) and the compile should run as fast as possible.
Keep me posted.
Click to expand...
Click to collapse
I followed the procedure mentioned in that readme file, but with additional info from other site,,
I extracted the source code from samsung open source, and then used the toolchain from the android base and it looked like it built(lot of warnings), but i cant find zImage anywhere?Wondering what ever happened during the build,,,
command used: make -j4 ARCH=arm CROSS_COMPILE=/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- zImage
Build abruptly end, no build logs anything, see file for build output.
Is there anything that I am missing?, Please help!
And, Don't you think the build log is unusually small for a kernel build?? :O

androcton said:
I followed the procedure mentioned in that readme file, but with additional info from other site,,
I extracted the source code from samsung open source, and then used the toolchain from the android base and it looked like it built(lot of warnings), but i cant find zImage anywhere?Wondering what ever happened during the build,,,
command used: make -j4 ARCH=arm CROSS_COMPILE=/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- zImage
Build abruptly end, no build logs anything, see file for build output.
Is there anything that I am missing?, Please help!
And, Don't you think the build log is unusually small for a kernel build?? :O
Click to expand...
Click to collapse
Folks on the forum, any ideas, the open source code from samsung sure looks like it has built all the '.o's but abruptly stop without even a warning as to what is wrong? Please help. Thanks in advance!

androcton said:
Folks on the forum, any ideas, the open source code from samsung sure looks like it has built all the '.o's but abruptly stop without even a warning as to what is wrong? Please help. Thanks in advance!
Click to expand...
Click to collapse
Okay, I got the kernel to compile after getting rid of the
1. "error: 'SEGMENT_SIZE' undeclared" problem, I had to turn on the Make V=1 ( verbose mode) explicitly to get to this point.
2. Next the compilation stopped saying "make[3]: *** No rule to make target `net/ipv4/netfilter/ipt_ecn.o', needed by `net/ipv4/netfilter/built-in.o'."
I had to remove the netfilter support from the kernel. I REALLY did not know how to solve this problem. Now that I have built the zImage( really small compared to the zImage that gets posted around in the forum) I am now concentrating on how get netfilter back into the kernel, for it is an important module for anything to do with TCP/IP security n filtering.
Finally,
3. How do I package this to the phone as a complete bootable ROM? Please help! Thanks in advance!

I found this thread, it might be useful. I can't try it until later though.
http://forum.xda-developers.com/showthread.php?t=704561

[Q] Can't get AOSP to boot

Whenever I build AOSP from source, it sticks on the "Google" screen (the actual bootloader logo, not the ROM bootanimation) and won't go further. This has happened on several build systems too (source redownloaded from the repo each time). Is it more likely to be a kernel or rom issue?

abtekk said:
Whenever I build AOSP from source, it sticks on the "Google" screen (the actual bootloader logo, not the ROM bootanimation) and won't go further. This has happened on several build systems too (source redownloaded from the repo each time). Is it more likely to be a kernel or rom issue?
Click to expand...
Click to collapse
It could be kernel. Easiest way to ascertain that is to flash a known working kernel immediately afterwards and see what happens.

rootSU said:
It could be kernel. Easiest way to ascertain that is to flash a known working kernel immediately afterwards and see what happens.
Click to expand...
Click to collapse
I left the system "booting" for a little while and I managed to get a logcat. Some major services are dying. I'll attach them.

It's probably not worth looking at logcats until you identify if the issue is ROM or kernel related. Logcats only tell you what Android is doing, not what kernels are doing. You'd need a dmesg for Kernel.
Try and flash a kernel first and see what happens. The closest to stock AOSP the better.
You should also reverse this test by taking a known working ROM and flash your kernel to it... It could be the error in your build is affecting both.

How are you installing the AOSP build? I can't remember what I did wrong, but at one point in my AOSP build attempts, I got the permissions wrong on my build.prop and what you describe is exactly what I experienced. Google screen but no boot animation, but did have logcat with multiple random looking failures. This line in your logcat is a clue:
Code:
I/DEBUG ( 168): Build fingerprint: 'unknown'
It should be mode 644:
Code:
-rw-r--r-- 1 root root 3341 Feb 24 08:53 build.prop

Did you add the vendor proprietary files? You can find these on TheMuppets github.
Sent from my HTC Desire using xda app-developers app

Chromium_ said:
Did you add the vendor proprietary files? You can find these on TheMuppets github.
Sent from my HTC Desire using xda app-developers app
Click to expand...
Click to collapse
I've never built AOSP for the Nexus, but I when I was building for the HTC deesire, I was under the impression that the google repo contained (and was designed for) everything for the Nexus one... was this not the case?

rootSU said:
I've never built AOSP for the Nexus, but I when I was building for the HTC deesire, I was under the impression that the google repo contained (and was designed for) everything for the Nexus one... was this not the case?
Click to expand...
Click to collapse
Dont believe so. When I last built for the nexus 5 using purely what was in AOSP, I encountered the same issue that this guy is having. The build will successfully compile, but wont actually boot. The solution for me atleast was to clone TheMuppets proprietary vendor repo for lg, add it to my source tree, run "make clobber", and build again.
Also on the official android building page, they instruct you to obtain the proprietary binaries prior to building, so it probably is indeed a necessary step.

Chromium_ said:
Dont believe so. When I last built for the nexus 5 using purely what was in AOSP, I encountered the same issue that this guy is having. The build will successfully compile, but wont actually boot. The solution for me atleast was to clone TheMuppets proprietary vendor repo for lg, add it to my source tree, run "make clobber", and build again.
Also on the official android building page, they instruct you to obtain the proprietary binaries prior to building, so it probably is indeed a necessary step.
Click to expand...
Click to collapse
Super, Thanks for the info.

local_manifest or roomservice
Can anyone PM me or just post his correct "local_manifest.xml" (or it called "roomservice.xml"?)
I'm failing to properly build AOSP, any of my builds result in no Broadnand service. No 3G/Data...
Thanks

"Vanilla" device tree

Hey folks,
i'm trying to get a "vanilla" aka unmodified device tree for the Shield Tablet K1. I know that you can sync over from nvidia's gitweb, tough the device tree is looking weird.
When i look at let's say cm's android_device_nvidia_shieldtablet it looks different. So i wonder how i would go from nvidias mutated tree to cm's layout without actually just forking it from cm.
Reason is, i want to port another custom rom over to the shield tablet, but i can't neither figure out how i'd do that with nvidias sources, nor how i would create a device tree similar to cm's, without any modifications.
I googled around for about 2-3 months now and still have no clue, so if anyone could give me a hint, i'd be very grateful!

What's wrong with the cm tree?
Unjustified Dev did the initial port of everything by hand. I've done maintainance manually since then. And to my knowledge, there's only been one other person to do a manual conversion (vartom). All custom ROMs derive from my tree. Should work in aosp as well. If there's something you need different from the cm tree, you can just add it on top. Or if something is broke in general, I need to know and fix it.

There's nothing "wrong", just not " clean", if you catch my drift. It's just a matter of reverting inwanted things, but yeah.. feels dirty.
Anyways, thanks for the info, man.

*shrugs* Okay, if you want to set up a new tree, nothing's stopping you. I wouldn't mind someone else knowing how to do it (pretty sure I'm the only active dev that has experience there), but it's a lot of parsing and research. I'll say that CMs trees are 95% unmodified from Nvidia's upstream, though. It's just rearranged into an aosp style tree. The kernel is a merge of the console and tablet since they were 98% identical anyways. I do my best to keep everything as clean as possible since I don't want to do through the work of making a lot of modifications every time a new release comes out... Engineers are lazy like that. I think the only things that aren't pure identical copies are the LTE init files and the unified device stuff (making the wifi only and lte models work in one ROM).

Nah, don't get me wrong there, i don't want to discredit you there.
I'm more talking about cm specific things like gello browser and stuff. Like i said, just a matter of a few changes to not include these. I'm just a beginner in any way, i can just follow instructions at best, i don't know c, and almost no java at all. So what you do is an astounishing task - it's just a personal preference coming and starting with nexus devices to tinker around, i have had the luxury of an AOSP tree, that's pretty much "my dilemma". I'm unexperienced and thus this might take a while for me. I've started to modify your device tree the day before yesterday, but i have something done wrong, as when i start compiling it'll ask if it should use " full_eng" config. (6.0.1 is used)
Again, thanks for putting me in the right direction, also for your efforts in maintaining our device.

What ROM are you trying to build? You could look at Carbonrom or Blissrom to see the rename changes needed to use the tree in a different ROM. Those should be similar across the board. I think the only CM specific package references would be gello and snap. Those commits could be reverted easily enough. Or if the ROM doesn't have them, I think they'd be ignored even if left as is.

Hi,
you can take a look at here
the base was the official cm tree, this is not vanilla but it s a K1 only tree.

Steel01 said:
What ROM are you trying to build? You could look at Carbonrom or Blissrom to see the rename changes needed to use the tree in a different ROM. Those should be similar across the board. I think the only CM specific package references would be gello and snap. Those commits could be reverted easily enough. Or if the ROM doesn't have them, I think they'd be ignored even if left as is.
Click to expand...
Click to collapse
I'm trying to port OmniROM https://docs.omnirom.org/Porting_Omni_To_Your_Device
Shouldn't be that difficult, i'm just doing something wrong.
kylon said:
Hi,
you can take a look at here
the base was the official cm tree, this is not vanilla but it s a K1 only tree.
Click to expand...
Click to collapse
Thank you, man.
I've forked it and will use it as a base.

Oh, omni. I build TWRP from omni. Take a look at the following two commits.
https://github.com/TeamWin/android_...mmit/c8e564a5ea44d963ab8d0e7829d9becd2ad5b0c0
https://github.com/TeamWin/android_...mmit/9b8772627795492f3380d2bf86680c09aada92c9
I haven't built the full ROM, but that should work. If you're using a K1 specific tree, the only difference should be in omni_shieldtablet.mk, instead of gsm.mk, use whatever omni has for tablet wifi only.

Steel01 said:
Oh, omni. I build TWRP from omni. Take a look at the following two commits.
https://github.com/TeamWin/android_...mmit/c8e564a5ea44d963ab8d0e7829d9becd2ad5b0c0
https://github.com/TeamWin/android_...mmit/9b8772627795492f3380d2bf86680c09aada92c9
I haven't built the full ROM, but that should work. If you're using a K1 specific tree, the only difference should be in omni_shieldtablet.mk, instead of gsm.mk, use whatever omni has for tablet wifi only.
Click to expand...
Click to collapse
Thank you, man. In fact i heavily orientaded on TWRP sources in this case. Also took a look at zombipop's repo.
Still whatever i do all i get is
[[email protected] omni]$ brunch shieldtablet
build/core/product_config.mk:241: *** No matches for product "omni_shieldtablet". Stop.
WARNING: Trying to fetch a device that's already there
Traceback (most recent call last):
File "build/tools/roomservice.py", line 352, in <module>
fetch_device(device)
File "build/tools/roomservice.py", line 320, in fetch_device
git_data = search_gerrit_for_device(device)
File "build/tools/roomservice.py", line 81, in search_gerrit_for_device
device_data = check_repo_exists(git_data, device)
File "build/tools/roomservice.py", line 58, in check_repo_exists
"exiting roomservice".format(device=device))
Exception: shieldtablet not found,exiting roomservice
build/core/product_config.mk:241: *** No matches for product "omni_shieldtablet". Stop.
** Don't have a product spec for: 'omni_shieldtablet'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Click to expand...
Click to collapse

Oh, brunch won't work because it wants to sync from the upstream server. Use lunch instead. Then run make to build.

Steel01 said:
Oh, brunch won't work because it wants to sync from the upstream server. Use lunch instead. Then run make to build.
Click to expand...
Click to collapse
Looks like a derp moment, i just had to modify the devicetree in another directory which is the actual working dir, instead on androidsrc/device/nvidia/shieldtablet directly. Like i said i just did something wrong.
It' compiling now, thank you for all the support!

Need help building a ROM [SOLVED]

So I began with this whole endeavour like a week ago and while I've learnt a couple of things I'm still hitting my head against a wall. The issues seem to be regarding the Kernel I'm using, someone mentioned that I'm supposed to be using the source Kerner of the ROM but isn't the Kernel device specific?
I'm also getting some errors regarding neverallows, a user suggested to ignore them but as far as I understand you should not be doing that.
So any pointers, suggestions or tips?
Here are my sources as well as the errors I'm getting.
Device tree: https://github.com/celepharn/device_xiaomi_vince/tree/havoc-11
Vendor tree: https://github.com/celepharn/vendor_xiaomi_vince/tree/havoc-11
Kernel Source: https://github.com/celepharn/kernel_dark_ages_vince
ROM Source: https://github.com/Havoc-OS
Haste or Dogbin URL (here are the errors as displayed in the terminal): https://del.dog/wiryckoful.txt

look like the compilation stop because of sepolicy usually you just remove and it would compile

ineedroot69 said:
look like the compilation stop because of sepolicy usually you just remove and it would compile
Click to expand...
Click to collapse
Remove what exactly? I'm pretty new to this.

celephrn said:
Remove what exactly? I'm pretty new to this.
Click to expand...
Click to collapse
i uploaded the compile log on pastebin so it's much easier to read
on line 493 its where it stop
also notice on line 499 it say " Please fix the policy "

ineedroot69 said:
i uploaded the compile log on pastebin so it's much easier to read
on line 493 its where it stop
Click to expand...
Click to collapse
Ahh you mean in the domain.te and coredomain.te files? I'm doing that right now, will get back to you when I'm through. Thanks!

ineedroot69 said:
i uploaded the compile log on pastebin so it's much easier to read
on line 493 its where it stop
also notice on line 499 it say " Please fix the policy "
Click to expand...
Click to collapse
Did that, and got error in
#error "Please don't include <linux/compiler-gcc.h> directly, include <linux/compiler.h> instead."
it's a line in the compiler-gcc.h file located in /havoc/kernel/xiaomi/vince/include/linux
Any clues on how to proceed? I'm going to try with clang to see if it works.
Edit: here's the code in said file.

celephrn said:
Did that, and got error in
#error "Please don't include <linux/compiler-gcc.h> directly, include <linux/compiler.h> instead."
it's a line in the compiler-gcc.h file located in /havoc/kernel/xiaomi/vince/include/linux
Any clues on how to proceed? I'm going to try with clang to see if it works.
Edit: here's the code in said file.
Click to expand...
Click to collapse
usually sepolicy are easy to fix since they point out line # of code and the file location causing issue on your case thou look like you have allow and not allow parameter conflict
also i forgot to say .te file are viewable as text so gedit works on them

ineedroot69 said:
usually sepolicy are easy to fix since they point out line # of code and the file location causing issue on your case thou look like you have allow and not allow parameter conflict
also i forgot to say .te file are viewable as text so gedit works on them
Click to expand...
Click to collapse
I did that, then I got some other errors and the suggestion was to switch to clang-proton, which I did. I got to the part of kernel image building only to fail once again.
These are my updated sources:
Device tree: https://github.com/celepharn/device_xiaomi_vince/tree/havoc-11
Vendor tree: https://github.com/celepharn/vendor_xiaomi_vince/tree/havoc-11
Kernel Source: https://github.com/celepharn/kernel_dark_ages_vince
ROM Source: https://github.com/Havoc-OS
Haste or Dogbin URL (here are the errors as displayed in the terminal): https://del.dog/locorfyvas
I'm certain the issue is building the kernel image, the Image.gz file but don't know how else to proceed, is the kernel I'm using outdated or something?
I'm also getting issues with lines of qseecomi.h located in /kernel/xiaomi/vince/include/soc/qcom, for example in line 108 stating I should put packed after "struct" but such instruction is not clear to me, perhaps would it be something like this?
__struct packed qsee_apps_region_info_ireq {
uint32_t qsee_cmd_id;
uint32_t addr;
uint32_t size;
};

Try to hire a Good developer to solve this issue! Good luck buddy!

mehtamanisha169 said:
Try to hire a Good developer to solve this issue! Good luck buddy!
Click to expand...
Click to collapse
I got it working, the build is now complete. Thanks!

Build Android 11 from source

Hi, I'm trying to build Android 11. When I run the command
repo sync
I obtai the error
fatal: remove-project element specifies non-existent project: platform/prebuilts/gcc/darwin-x86/mips/mips64el-linux-android-4.9
What it means? How can I resolve it?
Many thanks

Check this report from GitHub. It doesn't look like a big deal. Maybe missing resources/files that you probably don't need if you are building an OS for a phone.
I see they simple removed a line from local_manifests/untracked.xml of which contains the error.

Hi, many thanks for your reply. I have removed more than 10 lines from the xml files.
Is it a normal behaviour? Why the files are not correct?

denisgottardello said:
Hi, many thanks for your reply. I have removed more than 10 lines from the xml files.
Is it a normal behaviour? Why the files are not correct?
Click to expand...
Click to collapse
I didn't find a direct answer. But I've searched the errors, and found that your error on the OP has a darwin-x86 on it.
So I did Google that, and found that it is an Operating System that has something to do with Mac OS, released in 2000, still active.
So as the errors of other builders. I noticed that they're building an OS for mobile phones, which does not include, for an example, darwin-x86. So I asked myself .. What's the point of including an arch that you won't need?
I think when you're building the OS, you do export the arch you're targeting, right? So did it include darwin-x86?