Database Users

Samsung releases captivate source code...

http://www.droiddog.com/android-blog/2010/07/samsung-releases-captivate-source-code/
Has anyone seen this?
Does anyone know if this includes the encrypted drivers that are currently a hurdle in the path of custom ROM development?

I saw more files there than in the Galaxy S source, and for a moment thought the source was there, but actually it was just leftovers from the build process and the source still isn't there.
However, asedeno claims that Samsung are going to release the source, as the modules are GPL:
http://forum.xda-developers.com/showpost.php?p=7422651&postcount=55
(I'm still not sure if we're confusing "encrypted" with "compiled" here, though..?)

metadan said:
http://www.droiddog.com/android-blog/2010/07/samsung-releases-captivate-source-code/
Click to expand...
Click to collapse
GT-i9000 source is also available online - hxxp://forum.xda-developers.com/showthread.php?t=740378

Source code building a vanilla ROM

So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...

hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
I unfortunately haven't the answer but I'd like to add that I am curious about this too.

dalingrin said:
I unfortunately haven't the answer but I'd like to add that I am curious about this too.
Click to expand...
Click to collapse
I'll second this and ask that if you do figure it out, please share with the community.

I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.

hallfleming said:
So talking to my buddy about all the "junk" loaded on the Samsung, he kept raving about how his old Nexus One was just the way I would like it. I would like to have a "plain" version of Android 2.1 on my phone. I have a coworker friend that's a Linux guru that's willing to help. Here's my questions.
Can I take take the Samsung released source for the hardware drivers and compile it with a stock Android 2.1 platform? I'm not asking for step by step. More of a 10,000 foot how to. Is that possible?
Can you leave the CSC and Modem info the same and just install a PDA ROM with Odin? Or would you be overwriting all of that info on the phone?
Thanks and if this has been answered before, please fill free to say "search is your friend" and give me the links...
Click to expand...
Click to collapse
Check out this wiki from cyanogen:
http://wiki.cyanogenmod.com/index.php?title=Main_Page
On the bottom right you will see an advanced section that explains how to build from source code. (aosp)
Good luck!!! It's definitely not for me, not with kids and a full time job!

Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
rajendra82 said:
I think that vanilla Roms are a little further away in the future. First step in the process right now would be for someone to be able to compile a kernel from the Samsung released source code that works. Unfortunately the current Captivate kernel source code, when compiled, causes issues (voices garbled, lag when waking up the phone) that are not present in the stock precompiled kernel. These bugs are apparently not present in the other versions of the source code. Once these initial bugs are ironed out, we can truly start down the path of having custom fixes, and the devs can start to focus on bigger challenges, like making the vanilla Eclair or Froyo Roms to start working with our kernel. Good thing about this phone is that there are going to be so many versions of it, that parallel development is happening on multiple platforms. This will likely produce independent breakthroughs that could be theoretically ported between the platforms, but unfortunately it also slows down the development of each platform due to the quirks that have to be overcome. I hope that, in the future, we get to a place where all the source codes are merged into master repository that has all the necessary improvements and the ability to overcome individual platform quirks, so that the development can proceed more rapidly.
Click to expand...
Click to collapse

Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.

hallfleming said:
Also for clarification, when you bought a Nexus One straight from Google for AT&T, was it considered "Vanilla"? Is the build on that phone just like someone downloaded the source for 2.1 and compiled it with the hardware drivers and that's it? I'm wondering what all comes on a "basic" Andriod ROM straight from the source.
Click to expand...
Click to collapse
Nexus One is as Vanilla as it comes. Just straight up Android! I don't think there is anything added to stock 2.1 or 2.2 on the Nexus.

hallfleming said:
Good info. I haven't seen a post on people testing out the source code testing and their experience. Can you IM or point me to that?
Thanks!
Click to expand...
Click to collapse
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a developer, I can't personally contribute to the process. But it is interesting to me anyway.

I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
rajendra82 said:
Most of the kernel compiling struggles are documented here:
http://forum.xda-developers.com/showthread.php?t=740747
Mimocan himself has started some work on it here:
http://forum.xda-developers.com/showthread.php?t=747040
There are also people having success mixing Vibrant ROM on the Captivate with some GPS crash issues:
http://forum.xda-developers.com/showthread.php?t=746466
I am trying to follow those threads, and since I am not a deveoper, I can't personally contribute to the process. But it is interesting to me anyway.
Click to expand...
Click to collapse

hallfleming said:
I've seen these before. I thought they were just edited versions of ROM's sucked off a existing phone. Are these compiled from scratch?
Click to expand...
Click to collapse
The first two are attempts to recompile the kernel to put in the ext3/ext4 mimocan fix. The third one I believe is a script for boot logo animation hack to achieve the same thing.
I forgot to mention one more thread:
http://forum.xda-developers.com/showthread.php?t=739823

So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?

hallfleming said:
So we've got the source code with drivers and know which ones to use from the T959 for fixing the voice issue. We've got the stock kernel. What's left to creat a plain jane captivate?
Click to expand...
Click to collapse
I'm guessing not too much. There are somethings that would need to be edited such as handling the capacitive buttons. The i9000 roms handle buttons differently regardless of the kernel so, its apparently an OS level config.
I've been wanting to work on this but I've been neck deep in source code from work.
Here is a good how to: http://forum.xda-developers.com/showthread.php?t=704561

Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App

hallfleming said:
Thanks for the link. The US codes out there so we don't need i9000 port
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
My point was that given the I9000 rom needs source level changes in order to work as expected(haptic feedback on certain buttons, etc) then running an AOSP build may require some source level changes as well. It may not be as simple as building and flashing.

[SOURCE] Gingerbread sources released by Samsung

Samsung has released sources for Gingerbread update:
https://opensource.samsung.com/reception/reception_main.do?method=reception_search&searchValue=5830

gr8 news... )

Any new stuff over leaked rom?
XDA ♥

Really? By what do you make sure it is gingerbread?

fzn0268 said:
Really? By what do you make sure it is gingerbread?
Click to expand...
Click to collapse
GT-S5570_S5670_S5830_Opensource_GB.zip

It is indeed gingerbread.

Great news! My cygwin setup waiting for this. I have Linux but do something with different way always excited

i've dowloaded it... how do I install this?

plotinus said:
i've dowloaded it... how do I install this?
Click to expand...
Click to collapse
You don't install it, The source code is needed to build a custom kernel, but either enable overclocking or generally tweaking it to improve performance. You need the Android SDK to compile a kernel.

But, can we get the OS from this source or it's just the kernel?
Sent from my GT-S5830B using XDA App

Install Linux eg Ubuntu, down it, build it directly or git AOSP source then build.
My computer is unstable, or I can use it to port CyangenMod. But I have git AOSP source, I might try to build one. However, how to flash the built is a big trouble...

been trying to dowload this for a whole day. each time only got 10kBps speed, and resulting in timeout. also cannot resume. wth samsung????

Went well for me so here's my upload
http://www.multiupload.com/KR566WYN13

Help
Guys,
I have difficulties in understanding the given tutorial by Samsung. Do you any link to more comprehensible tutorial in order to make this update work?
Thank you so much.

Guys wht is this for?
Cant understand about this..im from sourh east asia..
What should i do?

geraldgeron said:
Guys wht is this for?
Cant understand about this..im from sourh east asia..
What should i do?
Click to expand...
Click to collapse
this is the Gingerbread source code for Samsung GT-S5830. It is primarily for those who wants to build custom ROMs.

chinoyray said:
this is the Gingerbread source code for Samsung GT-S5830. It is primarily for those who wants to build custom ROMs.
Click to expand...
Click to collapse
and custom kernels

I897UCKK4 Source Code is out.

I'm preparing to be flamed, but I figured I might as well create this thread. Now I know many of you know this, along with the i896 source, is out, but there wasn't a thread for it and the i896 one had issues, so here . Hopefully we can get some development going for those of us that want *shutters* Audience Chip drivers, along with the many features that are present in the i9000 roms.
Just search KK4 on here: https://opensource.samsung.com/index.jsp

nygfan760 said:
I'm preparing to be flamed, but I figured I might as well create this thread. Now I know many of you know this, along with the i896 source, is out, but there wasn't a thread for it and the i896 one had issues, so here . Hopefully we can get some development going for those of us that want *shutters* Audience Chip drivers, along with the many features that are present in the i9000 roms.
Just search KK4 on here: https://opensource.samsung.com/index.jsp
Click to expand...
Click to collapse
Doesn't bother me anymore since now ICS is doing great.
But, if really want to stick with GB(usually MIUI and CyanogenMOD).
I would like:
a.) The Audience Chip thingy.
b.) Battery life.

Fate-Silver said:
Doesn't bother me anymore since now ICS is doing great.
But, if really want to stick with GB(usually MIUI and CyanogenMOD).
I would like:
a.) The Audience Chip thingy.
b.) Battery life.
Click to expand...
Click to collapse
What? I'm not making anything. I was informing the community (those who didn't know) of the source code.

nygfan760 said:
What? I'm not making anything. I was informing the community (those who didn't know) of the source code.
Click to expand...
Click to collapse
Yea, I know.
I just want to tell AT&T/Samsung is SLOW for their firmware codes sharing... too stingy...

Fate-Silver said:
Doesn't bother me anymore since now ICS is doing great.
Click to expand...
Click to collapse
yea I been onICS for 24 hours now ,, its great , but nothing special I see very few differences in anything , except I am missing all of the features I m use to on GB .
imo dotn believe the hype , the only 2 things I like about my current ICS set up is sixstring kernel allows me to OC higher then on sammy rom (not higher then cm7 tho) and the launcher is pretty cool but still not as nice as on the gnex .
Eventho its 2.3.5 I welcome source of KK4
eventho Im 2.3.6 (i9000 base )

I'm looking forward to the more refined kernels the source code release should bring around. Those features we've been missing will now be possible.

nygfan760 said:
I'm preparing to be flamed, but I figured I might as well create this thread.
Click to expand...
Click to collapse
Why? There is already a thread created in General. This is where searching comes in handy.

Red5 said:
Why? There is already a thread created in General. This is where searching comes in handy.
Click to expand...
Click to collapse
Saw the thread. It is a discussion thread about the firmware, this thread is to alert people of the actual source code, so we can get new kernels and stuffs Also, aren't most source code threads posted in here? At least for Froyo, and i896 GB, I believe they were.

Audience chip support was already extracted from the I896 gingerbread source kernel. It is available in the i9000 captivate corn kernel. Specifically gave me thanks for being able to introduce audience tip finally.
If you would like Audience support in any other kernels just contact the developer of corn.. A few months ago

TRusselo said:
Audience chip support was already extracted from the I896 gingerbread source kernel. It is available in the i9000 captivate corn kernel. Specifically gave me thanks for being able to introduce audience tip finally.
If you would like Audience support in any other kernels just contact the developer of corn.. A few months ago
Click to expand...
Click to collapse
I know, I know, I have been running it for a while now.

but im surprised that kk4 was final release. had time-stamp issue.
but now if we can get a unbranded kernel, we can have a complete unbranded rom with the ATT removal mods i posted while back.

TRusselo said:
but im surprised that kk4 was final release. had time-stamp issue.
but now if we can get a unbranded kernel, we can have a complete unbranded rom with the ATT removal mods i posted while back.
Click to expand...
Click to collapse
I'm pretty sure that problem only happens when you put AT&T software on an i896. I can't say for sure though because both my cappy's are canadian. Anyways I don't think ts a problem with the phone per se.. I think its a network thing. There is no time stamp issue for people on the AT&T network that I know of.

KK4 Source has been available since around Christmas. Some of the I897 kernel devs have been trying to compile a kernel from source but have been running into issues with the kernel not booting which is why you haven't seen any yet.

erbsmokah said:
I'm pretty sure that problem only happens when you put AT&T software on an i896. I can't say for sure though because both my cappy's are canadian. Anyways I don't think ts a problem with the phone per se.. I think its a network thing. There is no time stamp issue for people on the AT&T network that I know of.
Click to expand...
Click to collapse
Its a network AND software issue. Either they can fix the problem though the network, (its been done before) or you can de-compile the MMS.apk and change a line of code to fix the problem.
Kyuta Syuko said:
KK4 Source has been available since around Christmas. Some of the I897 kernel devs have been trying to compile a kernel from source but have been running into issues with the kernel not booting which is why you haven't seen any yet.
Click to expand...
Click to collapse
that was the kh2 rogers i896 source that they were having trouble with.... or are they having trouble with kk4 also???

TRusselo said:
Its a network AND software issue. Either they can fix the problem though the network, (its been done before) or you can de-compile the MMS.apk and change a line of code to fix the problem.
that was the kh2 rogers i896 source that they were having trouble with.... or are they having trouble with kk4 also???
Click to expand...
Click to collapse
He is a kernel dev but yeah I hope that isn't the problem.

TRusselo said:
that was the kh2 rogers i896 source that they were having trouble with.... or are they having trouble with kk4 also???
Click to expand...
Click to collapse
Both JSmokey and I haven't been able to get a kernel compiled from the KK4 source that we had gotten around Christmas. Though JSmokey said he did have a working kernel before, but isn't certain what he did to make it not work anymore. I've even tried to compile a stock kernel per the included instructions with no luck...

Kyuta Syuko said:
Both JSmokey and I haven't been able to get a kernel compiled from the KK4 source that we had gotten around Christmas. Though JSmokey said he did have a working kernel before, but isn't certain what he did to make it not work anymore. I've even tried to compile a stock kernel per the included instructions with no luck...
Click to expand...
Click to collapse
Same here, there must be something missing. Pulling a dmsg doesn't give much help, something about wanting sh in /system/bin (I think).
I have moved over to cyanogenmod 7 for now, waiting for cm9. Lots to tinker with there.

boog said:
Same here, there must be something missing. Pulling a dmsg doesn't give much help, something about wanting sh in /system/bin (I think).
I have moved over to cyanogenmod 7 for now, waiting for cm9. Lots to tinker with there.
Click to expand...
Click to collapse
.... no our original 2.3 kernel dev has given up

Sounds like the only way to get bln is to go to 2.2 or i9000.

Wdustin1 said:
.... no our original 2.3 kernel dev has given up
Click to expand...
Click to collapse
Maybe we can ask DG for help. I know he has moved on a long time ago, but recently he came back and helped with ICS kernel development. If he could help us getting KK4 kernel compiled from source, I am sure we will see a lot more ROM development going on.

[REQUEST] N8000 Kernel Source

I am about to build a kernel for N8000. But my problem is I can not download from samsung open source site (Very Slow Connection).
Can someone please mirror the update7(MD1) for me on a fast server like dev-host, android file host, mediafire or etc...?
Here's the Samsung open source site:
http://opensource.samsung.com/reception/receptionSub.do?method=search&searchValue=GT-N8000
Thanks in advance.

You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.

kcrudup said:
You may use my GitHub repository, which has a branch "merge-to-ss-jb" that is just the vanilla Samsung kernel, backed by the complete Linux tree.
Also, if you're interested in a complete, up-to-date tree (and what I'm running on my own GNote) you may browse my "kernel-forward" branch.
Click to expand...
Click to collapse
Thanks.
I have two questions if you don't mind.
1. Merge-to-ss-jb is the latest source (MD1)? Is it a good to go for a kernel to be based upon?
2. Is it alright with you that I base my kernel on your own kernel?
I appreciate it if you can help me with some kernel stuff as I am new to this.
Sent from my HTC One X using Tapatalk 4 Beta

csec said:
"merge-to-ss-jb" is the latest source (MD1)?
Click to expand...
Click to collapse
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Is it alright with you that I base my kernel on your own kernel?
Click to expand...
Click to collapse
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.

kcrudup said:
Yeah, it's essentially the official Linux kernel source up to version 3.0.31, overlaid with a cleaned-up version of the 1st Samsung JB kernel release, then each subsequent Samsung Open-Source Release (latest is "#7") is overlaid on top of that. If you build the HEAD of that branch, you'll have a vanilla Samsung kernel as of XXMCD1.
Of course! The entire Linux kernel is built upon Public collaboration; we all share from each other. My kernel has a few selected bits here and there from diverse places like CyanogenMod, Francisco Franco, Xstacy, the upstream kernel, Qualcomm, NVidia ...
I used to post my built kernel up in the ROM threads I used to use on my GNote, but someone complained and I don't really feel like being bothered with my own thread (don't have time for the inevitable newbie SPAM) so until if/when I do go "public" with it, the "kernel-forward" branch on GitHub is the best place to get what I'm running now.
Click to expand...
Click to collapse
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD

csec said:
Great!
Thanks again.
Sent from my GT-N8000 using Tapatalk HD
Click to expand...
Click to collapse
Heard that the published sources have different wi-fi drivers than preinstalled stock kernel.
This is the main reason of allshare cast not working with custom kernels (on the contrary, some s3 custom kernels DO SUPPORT allshare cast), even if status=official and flash counter=0.
Anyone can confirm?
Anyone has the proper ones or know which one (i.e. from a different samsung device) to use?

gitHub link dead