Related
Can we expect Dell to release the kernel source? Are they required to release it?
Yes.......
they are supposed to release it ...
weather they do is another thing...
and if they don't who's gona fight em ... no one can afford it
http://gpl-violations.org/
how do we tell them that we want the source of dell and get them to get it??
@MattAtDell tweeted the other day in reply to some other random user that he would look into it, so its a good outlook that the kernel source will be made available... This will probably be the first phone I'd be willing to try and build a kernel for, lol. I'm sure we'd have a vanilla build of Android 2.1 (probably a bit broken) already IF we had the kernel source, 1.6 and 2.1 run the same kernel version 2.6.29 (froyo is 2.6.32 so it might actually take a bit more effort). This also explains why they show a 2.1 build even though they've committed to go straight to 2.2.
Random user my arse..
He was the first one from Dell that bothered to respond to *MY*query.
You can already build a vanilla froyo including kernel, but its taking a lot of experimenting to get a working combination of settings (I'm using the codearoura (qualcomm) surf ) git..
I may try a generic android git to see if it works..
jmhalder said:
@MattAtDell tweeted the other day in reply to some other random user that he would look into it, so its a good outlook that the kernel source will be made available... This will probably be the first phone I'd be willing to try and build a kernel for, lol. I'm sure we'd have a vanilla build of Android 2.1 (probably a bit broken) already IF we had the kernel source, 1.6 and 2.1 run the same kernel version 2.6.29 (froyo is 2.6.32 so it might actually take a bit more effort). This also explains why they show a 2.1 build even though they've committed to go straight to 2.2.
Click to expand...
Click to collapse
Any success compiling a kernel 2.6.33+ for Streak?
Any success compiling a kernel for Dell Streak? Where to start for it? I've been trying cyanogen kernels, but they don't seem to work or maybe I am doing something wrong creating the boot.img file. Any doc for it?
Thanks in advance!
Kernel source for Dell Streak?
Hi,
I was wondering whether the android kernel uses some kind of standardized kernel versions and configurations that allow people to add a module to an existing kernel in, let's say a dell streak tablet/smartphone.
Is it easy to get the kernel configuration and patches to compile modules for the streak?
Do they put some kind of locking so that nobody having a jtag tool can make the configuration changes to make the kernel read a new module?
jsmanrique said:
Any success compiling a kernel for Dell Streak? Where to start for it? I've been trying cyanogen kernels, but they don't seem to work or maybe I am doing something wrong creating the boot.img file. Any doc for it?
Thanks in advance!
Click to expand...
Click to collapse
ive had lots of success in building kernels, its just that none of them boot!
(technically I think this is known as not succeeding )
Building != Booting
So we have same situation... It's not a matter of building a kernel but booting it right on the device.
But what would be failing? Has anybody seen any log about what is happenning during boot to know what is failing? Because I would understand that a valid kernel would boot the device but some parts that would need propietary code wouldn't work (for example wifi, or whatever)... but no boot at all is quite strange.
Can anyone confirm at least a successful module compiling/running?
Not me
maxrfon said:
Can anyone confirm at least a successful module compiling/running?
Click to expand...
Click to collapse
Not me! Is it really impossible the get it running?
If you ask dell for the linux source code, they must provide it. They have to make the exact source code available that can be used to compile the shipped binaries.
If they won't make it available upon request go inquire with http://gpl-violations.org as recommended earlier.
hey dcordes glad to see you here, I have asked via a few avenues, but was waiting till its available in the USA before pressing them further
theres a Guy popped up on modaco yesterday that thinks the boot.img needs 2k page file but 4k padding and suggested some changes to makeimg to get it to boot properly.
I'll play again later on
quiet bump, tweet by me:
http://www.twitlonger.com/show/3g0ebt
I also put something on twitter.
If you are as pissed as everybody about the lack of the sources, go write a mail to https://lists.gpl-violations.org/mailman/listinfo/legal
They are the attorney to each user of GPL licensed software ! They will tell you what to do. If you browse the archives they will advise to keep asking for sources. We did that. No it's time to collect evidence of the ignored requests and take further steps.
But first we should let that mailing list know ! If nobody will mail it in the next few days I will. I don't have the device but I hate industry going ignorant on customers. It is also an insult to everybody working on the Linux kernel source code. And that's many and includes myself.
cheers
dcordes said:
But first we should let that mailing list know ! If nobody will mail it in the next few days I will. I don't have the device but I hate industry going ignorant on customers.
Click to expand...
Click to collapse
I do have the device.
http://lists.gpl-violations.org/pipermail/legal/2010-September/002235.html
hi guys, did HTC ever release the source code for the 2.1 update?
No. htc are bell-ends and don't even release driver source code, let alone code for their "superior" gui. Hence why it takes a while to port newer versions of android to the hero. Developers have to implement loads of dirty hacks and backports using kernel binary blobs they manage to extract from the 2.1 upgrade.
TheReverend210 said:
No. htc are bell-ends and don't even release driver source code, let alone code for their "superior" gui. Hence why it takes a while to port newer versions of android to the hero. Developers have to implement loads of dirty hacks and backports using kernel binary blobs they manage to extract from the 2.1 upgrade.
Click to expand...
Click to collapse
well thats just bad news!!
but they did afaik release source code for the kernel for many of their phones didn't they, what i would like to know is what does this mean to developers, what can they do with the kernel source?
The kernel is just a modified linux kernel, which has been open source since the early 90's.
Developers can do quite a bit with the kernel, is is basically the bridge between hardware and software.
However, despite running Debian since Etch was the latest stable release, my knowledge of the linux kernel is limited, so you would have to ask a developer for specifics.
TheReverend210 said:
The kernel is just a modified linux kernel, which has been open source since the early 90's.
Developers can do quite a bit with the kernel, is is basically the bridge between hardware and software.
However, despite running Debian since Etch was the latest stable release, my knowledge of the linux kernel is limited, so you would have to ask a developer for specifics.
Click to expand...
Click to collapse
thanks for your help
info on webkit source please..
i was at HTC's Developer Center and i noticed that HTC released the "webkit source code" for several "Sense UI" models, including the HTC Droid Eris, which very much shares our beloved Hero's specs...
i was wondering is this webkit compatible with our GSM Hero, and why didn't HTC release the webkit source for the GSM version?
the reason i'm asking is because i want to take out libwebcore.so alone and patch it, and replace the one in Hero...
Hey guys. So would anyone like to help me out in building an AOSP ROM for the LG Optimus S?
Currently, I have compiled the LG AOSP 2.2 kernel (zImage), and compiled the Android 2.2 AOSP system. Apparently now I need to get the LG vendor tree so I can compile that too into a working system? Can anyone help me out with that? This is my first time ever building a ROM from source code.
i hope someone will listen your help request
I hope so too... I hope so too.
I hope so too, would be nice to have another ROM option for the Optimus S. And this is a stepping stone to CyanogenMod on it
I'm also interested to create a fully working build of 2.2.2 AOSP Froyo.
But I'm new to the Android's world. I need that someone teach me how to build android from source. Also I need to know how to port the LG's drivers.....
I'm willing to help, but I can't program in any language. However, I know the basics, I can compile stuff, can do fairly well with the command line, I use Arch Linux as my main OS (so I can pretty much do compilations and stuff without a problem), etc.
I still don't know much about Android at this time, and contributing to this "project" may be my way of getting to know things
Count be in.. i m good with C,C++ ,shell scripts .tell me wat to do..i m new to android
Building Android from source can be quite tricky when proprietary software must be compiled in. I'm compiling since 2 months on gingerbread and nothing but phone is working... no USB,no camera, no bluetooth ... its now simply a phone^^
But, if your are lucky with Froyo you need only the source from android 2.2.x and the one shipped by LG (I know there are some sources for Optimus One, but don't know about Optimus S). Put it all together and compile the code - while/after compiling you will see lot of errors, there must be fixed by yours.
Have a look at cyanogen CM6.1, there have many fixes built in. If you would like to build a brand new system from scratch by yourself, i'll wish you many luck and lots of time
andy572 said:
Building Android from source can be quite tricky when proprietary software must be compiled in. I'm compiling since 2 months on gingerbread and nothing but phone is working... no USB,no camera, no bluetooth ... its now simply a phone^^
But, if your are lucky with Froyo you need only the source from android 2.2.x and the one shipped by LG (I know there are some sources for Optimus One, but don't know about Optimus S). Put it all together and compile the code - while/after compiling you will see lot of errors, there must be fixed by yours.
Have a look at cyanogen CM6.1, there have many fixes built in. If you would like to build a brand new system from scratch by yourself, i'll wish you many luck and lots of time
Click to expand...
Click to collapse
So in your opinion it would be a lot easier to just build a CyanogenMod 6.1 ROM? Sounds like a plan. I read that I could just pull stuff from the Legend and use that as well? Could you help me with that stuff (pulling from the Legend source, that is)?
Legend stuff is less compatible then i thought. You can't use nothing from there.
As my work at 2.3 is now stopped (I haven't bugs related to working stuff, I have no idea what to do with 3d and gps and I too lazy to patch libcamera now) I hope to start work on CM6 next holiday's.
mik_os said:
Legend stuff is less compatible then i thought. You can't use nothing from there.
As my work at 2.3 is now stopped (I haven't bugs related to working stuff, I have no idea what to do with 3d and gps and I too lazy to patch libcamera now) I hope to start work on CM6 next holiday's.
Click to expand...
Click to collapse
We'll work on it together then? I started a GitHub. github.com/mrinehart93
mrinehart93 said:
We'll work on it together then? I started a GitHub. github.com/mrinehart93
Click to expand...
Click to collapse
As I already got working GSM/Audio/WiFi/Bluetooth/USB/Sensors in 2.3 (port to 2.2 is easy) I will continue work in my repo https://github.com/mik9
Ypu can send your patches via "pull request" functionality.
mik_os said:
As I already got working GSM/Audio/WiFi/Bluetooth/USB/Sensors in 2.3 (port to 2.2 is easy) I will continue work in my repo https://github.com/mik9
Ypu can send your patches via "pull request" functionality.
Click to expand...
Click to collapse
I won't have any time to work on CM tonight or probably the rest of this week, but as soon as I do I'll set up my Github.
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Need 2.2 source code...
2.1 is a dead horse--why bother when 2.2/2.3 are out?
The reason to bother is to at least get AOSP running. Once its on 2.1, it'll be easier to get 2.2 AOSP running on it. But claiming 2.1 is a "dead horse" is the wrong path ... the real question still stands: after 9 months on the market their still are no AOSP ROMs.
MIUI
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
sarim.ali said:
Now that vibrant 2.2 source is released ... we finally have a REAL AOSP port and my all time favorite from my old HD2 the MIUI.... so keep your heads up and wait for it to get finished.
Click to expand...
Click to collapse
Except, the 2.2 source for the Vibrant has not been released. The SGH-T959D that shows Froyo sources on Samsung's site is for the Canadian Fascinate, not the US T-Mobile Vibrant. Samsung has yet to release the 2.2 sources.
oka1 said:
Get a custom rom. There are so many good devs doing them don't waste your time on AOSP....... until they release the actual source code...... on April 22
Click to expand...
Click to collapse
Except the so-called "custom ROMs" are just modifications on the stock theme, a replacement kernel and a change of some of the supplied applications.
There is nothing close to a full "custom ROM" such as CyanogenMod or MIUI because we don't have Samsung's sources. What is passing for a "custom ROM" for the Vibrant are just repackaged files. It is akin to the "ROM cooking" that took place for the WinMo phones, not a truly ground-up build from source that is possible with Android.
EDT/Devs4Android has the MIUI build. From Source.
TW has a 2.2.1 in testing.
EDT has a 2.2.1 Beta released.
TW has a 2.3 AOSP in testing. From Source.
EDT has 2.2 AOSP in testing. From Source.
What you want is out there for you.
Watch the forums and reply when a call for Alpha testers is posted.
Hopefully it won't be long before you see a full TW/EDT/Devs4Android collaboration!
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
mattb3 said:
I think what the original poster is trying to ask (and I have the same question) is why were there never any real 2.1 AOSP, cyanogen5 for the vibrant. The source for 2.1 has been around for many months. Were some other proprietary bits missing, was the released source code such a mess that it was unbuildable, something else? With those questions in mind, why will things be any different when the 2.2 source comes out?
Click to expand...
Click to collapse
Yes, this is more towards what I was getting at. We do not have Samsung's kernel sources for 2.2. And, we do not have a Samsung provided vendor overlay.
When we receive these two pieces, then a true AOSP build will be possible. However, we do have the 2.1 kernel sources, so why wasn't a true AOSP build possible then? What was missing, and can we actually expect Samsung to release the overlay that's needed?
Actually, that's true. I know it was old but why didn't anyone build a 2.1 cyanogen or aosp rom? (Not to say its easy.)
Sent from my SGH-T959 using XDA App
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Where have you been?
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
rpcameron said:
I've been following the development of so-called ROMs for the Vibrant (and other SGS devices), but I have yet to see a single AOSP ROM. Even when Samsung released the original kernel sources for 2.1, there were no AOSP 2.1 ROMs. Why not? Is it because they don't know which BLOBs to pull for insertion or the proper vendor overlays?
Some developers have done great work with SGS kernels (especially supercurio and his Voodoo kernels ... eugene373's tend to always wipe the internal SD card unnecessarily ...). But, a kernel does not a ROM make ... therefore I ask, what is truly missing to build an AOSP ROM. I've gone through the sources, but I don't follow makefiles too well.
I know we have another month or so before Samsung is obligated to release their 2.2 kernel sources, but that should have no impact on 2.1 AOSP ROMs. Therefore, I ask "what is the hold up?" What is missing, and what might I contribute ...
Click to expand...
Click to collapse
For probably the same reason that many phones with non AOSP firmware running 1.5/1.6 did not bother with AOSP 1.5/1.6 when they were released around the time 2.1 source hit. Why bother developing at all for what is essentially an "out of date" OS.
The only people it seems who actively continue to develop for existing (as opposed to new) firmware are manufacturers and carriers. This stupidity should be left to the manufacturers who still do this.
One of the larger snags way back then (sits in his rocking chair on the porch) was a lack of understanding of the phones proprietary aspects and how to work around them. But we have a fairly clear understanding of Samsung's boot process now, and RFS can now easily be turned into a distant memory.
I would wager a guess that the apathy towards 2.1 will not repeat itself once we have 2.2 source widely available and the low level similarities between 2.2 and 2.3 should have Gingerbread being more than the experiment it currently is. It's been barely more than a week since Eugene's little present manifested and there are already proper and stable kernels available.
Keep in mind that the devs we do have, have done a phenomenal job of cleaning up, speeding up, and drastically enhancing our existing 2.2 release. And perhaps to the point where many will not really care, though I know many would still like to see CyanogenMod6/7 properly on this phone.
Master&Slave™ said:
Dude theres been a true AOSP ROM for the Vibrant since like december and thats CM 6.1
Im running it now
Click to expand...
Click to collapse
Um, that's not quite true. The CyanogenMod.com website lists 0 files available for download for either experimental or stable files. The CM6.1 you must be running is not a true CM build.
Also, CM is not AOSP, but rather AOSP with modifications.
phrozenflame said:
A noob question, kindly can someone explain what is the vendor overlay stuff?
Many thanks!
Click to expand...
Click to collapse
The vendor overlay tells the AOSP build system which proprietary files are needed from the device that are not available in source form. This includes things like GPS and video drivers, baseband firmware for wireless radios, &c.
hi everybody !
a month age i decided to compile a new rom for my Galaxy S absolutely from AOSP source ( branch 2.2.1_r1 ) after some compile-time problem and many painful steps to resolve ,eventually the rom successfully built and can boot it up flawlessly on emulator.
i create a nandroid backup of current rom and installed the compiled one. but i am facing new problem :
1- the phone successfully boots but after short while screen began
flicking several time and the phone go in deep sleep and never wakeup
( power button or menu button does not do any thing )
2- touch screen works only for some second that I can unlock the
phone
3- there is no network available
4- I have downloaded samsung opesource package for GT-I9000. it
contains a folder named 'platform' but when i merge these files to
AOSP , the compile process stops and fails again. if there any one can
help me which files from samsung source should i merge and how ? if
you now the answer and dont have spare time then some internet link or
online document is really useful .i have no problem studding and
reading and searching . reaching to target is my only hope .
I am really disappointed why there is not a good and complete step2step tutorial to compile an AOSP rom for galaxy s (GT-I9000) !!
such docs is available for phones like dell streak , desire , dream , magic , .... . i really want to to active these aspect on XDA forum and with help of all you ( mods and masters ) try to create such tutorial that any one in world can use to refer . i think XDA is the only reference on net to collect and create such help and document. please help me and leave PM or comment to agree ot disagree and from where can i start ?!! thank in advanced .
edit :
there is a google groups post that i send my question in Android-platform . if you prefer please join this group and active that post to ask any question related to 'galaxy s compile from source ' .
post located at http://groups.google.com/group/android-platform/browse_thread/thread/da5d6f18f3bd3c9b
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
DiegoConD said:
I have a LG P350 which development has stopped but i want to keep it updated, i have my computer ready for building, also i have kernel sources, Cyanogenmod 11 and 10.1 sources too, (I don't know exactly if 10.1 sources could help) and i know that i need to apply patches to work on Armv6 but i don't know how to apply them to the source code, also i don't know if i would just need the pure source code to build or i need to do more modifications to it and finally, i don't know if the rom would work with 2.36 kernel which it's the most stable one for this device, i'm very new in this but i know that i can keep update my little phone, thank you all in advance for help.
Click to expand...
Click to collapse
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
shimp208 said:
Hello, looking at your situation here is what I can conclude. First off you will need to change things for building on ARMv6 architecture, check this out for example. But your biggest problem will be that Android 4.0+ uses Linux kernel version 3.0+, and with the 2.36 kernel you have a lot of things will be broken and need fixing. That being said if your up for the challenge for it cause that's what were all about .
Click to expand...
Click to collapse
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
DiegoConD said:
Well, i got this http://forum.xda-developers.com/showthread.php?t=2144790 that is the most similar phone talking about hardware, it has 3.0 kernel working well so i thought i could port it, i found this http://stackoverflow.com/questions/15961306/porting-kernel-from-another-device so i think i would have less problems due hardware similarities (Look here http://www.gsmarena.com/compare.php3?idPhone1=3516&idPhone2=3735 ) so, if i have cm11 pure sources, i add this kernel sources and some patches i would have it booting? Sorry for this very dumb question but, i didn't get at all about the armv6 part, how to apply patches, which i would need and all that, i really want to learn about this so thank you for this answer and the next ones :good:
Click to expand...
Click to collapse
The best way to start is use the ARMv6 branch of Cyanogenmod 11, replace the CM 10.1 in the previous linked build guide with cm-11.0 ("repo init -u git://github.com/androidarmv6/android.git -b cm-11.0"), and then to direct the build to use your kernel take a look at this guide on integrated kernel building with Cyanogenmod.