Discussion in 'Android Devices' started by emuneee, Jul 30, 2010.
Samsung releases Captivate source code Boy Genius Report)
Downloading as we speak...
ummm ... wow
It's almost as if they want to give AT&T the finger. I wonder if they're doing this so that people can compile a kernel without the AT&T garbage. Good for them!
So forgive my ignorance, but what can you do with this?
Well if you know how to do it, now you can change the phone software to do whatever you want, completely bypass AT&T and their "improvements", and all this without having to reverse engineer, hack, or transmogrify code from another "sister" platform.
This is fantastic news. Like I said, it's a giant middle finger to AT&T and their trying to control and lock down open source.
Not really, I don't see it as a Dick move or as giving At&t the finger.. what percentage of users can really take advantage of this?
A WHOLE GAGGLE! Spend some time over at XDA forums and you'll understand just how many devs there are out there. I'm forecasting a Custom Froyo 2.2 ROM in the next 2 - 4 weeks for this phone. That doesn't mean it'll be shaken of all bugs, but it'll be there for evaluation.
This is big, and here is why. If you google Samsung Galaxy S mimocan speed fix, you will see a video of a European i9000 Galaxy S owner's Galaxy S with a modified 2.1 kernel have a Quadrant score higher than the highest ever recorded before (Google Nexus One with Froyo). The way the speed fix works is by recompiling the kernel to support ext3 file system, then moving your application data to a ext3 partition on the external sd card, and then simlinking to those directories. With that fix, this phone will fly even with the current 2.1 firmware. The fix was not available to us until now because the source code of the i9000 Galaxy S was available, but that for Captivate was not. Now that we have source code, this fix can be made available to us provided Samsung has released all or enough of the code to allow recompilation and not withheld important files due to them containing proprietary code.
Browsing through the source:
You can make changes to the kernel and build it....read what rajendra82 said above me. Hopefully, this gets released soon.
You can also cook Android 2.2 ROMs as well. You just download the generic Android 2.2 source code, overwrite the files from the Captivate source code and build. However, whether it works or not is an entirely different story...lol.
But this makes cooking a LOT easier.
Perfect timing. Today I should be done with my summer graduate classes and start poking around with this!
Okay... can one of you get going on the GPS fix? PM me when you're done, thank you.
This is fantastic news. I'm hoping that Samsung can get a nice GPS-fix out the door as well to allow the devs to work with that firmware to cook Android 2.2 ROMs.
I wish I had a bit more spare time to look into ROM building and customization, it would be one heck of a fun side project (especially since I'm looking to pick up a cheap Nexus One from a friend as well). It's been almost 10yrs since I've touched any programming, so I'm not sure about the time it would take to get up to speed. Perhaps I'll just ask around to see if someone wants a reliable tester.
can anybody give me a lowdown on how to do this?
Do you know how to program? Chances are, if you have to ask what to do with this, you won't be able to do it
It depends on what exactly Samsung has provided. I haven't had a chance to look at and try to build the code. I'm assuming that they have provided the source code for their version of Eclair (hopefully without at&t's crappy apps). If that's the case, you can modify the code to your liking and build your own version of their operating system.
Umm, no - actually, it's per the Google/Android/GPL/Apache license.
Like Linux, if you want to use it, you must release source code that is not your own proprietary property.
I remember reading that Android was released under the Apache license, but I dunno how they can just do that at will, considering they are using the Linux kernel, which is under the GPL. Unless the kernel itself is GPL, and the rest is Apache...
I dunno - these licensing situations are ALWAYS sticky and confusing...
I know under GPL they would have to release any changes they make to GPL code, which is NOT the case under Apache licensing...
Don't get excited just yet. We still don't know how much of the code they're withholding.
Holy Jeebers guys. It looks like over at XDA that this is, indeed, the real deal.
Yup... Looks like the GPS driver is in there too... I give it two weeks before someone at XDA makes a better driver, or we discover it is truely a hardware problem...
Go into your GPS settings and just try turning on Skyhook. I did this and left the other settings factory and while at work in the parking lot I did a "where am I' and in less than 20 seconds I had the address and zip code etc on my screen.
Awh, more reading lead to the source drivers still being encrypted.
This has nothing to do with giving the finger to AT&T. :shakes head: Many other source codes were also put out today, including the Droid X source code.
This has nothing to do with AT&T.
Yes yes... I know... I've read about and tried every fix...
They don't work...
Also, skyhook is only good when you are in a densely populated area. It gets it's location info based on nearby wifi networks. Not GPS...
The GPS (Global Positioning SATTELITE - not wifi) sytem on the phone does not work.
Couple newer posts show that they shouldn't be and will be released as early as Monday