OK I'll probably get flamed by people like I did in the Development forum calling my simple question "STUPID"..... but could this be the link to the source code for the P6210?
https://opensource.samsung.com/index.jsp
We already knew where the source code was. The problem is that they have not provided the wifi drivers in the correct form, according to garyd9 the wifi drivers are only binary, so i think that means he won't be able to do much with those wifi drivers. Another problem is that the source has not been updated to work with the newest over the LA3 firmware samsung has provided according to garyd9. If we didn't have the source code, then garyd9 wouldn't have been able to build a custom kernel for our tablet. You can find his kernel here http://forum.xda-developers.com/showthread.php?t=1421466
Sorry if it sounds like if i'm being mean to you, but the source code links had already been posted a long time ago in the development section http://forum.xda-developers.com/showthread.php?t=1375911
Related
Nearly days I get an open souce code of i5800 and I just a new one in the compling world,so I hope someone can help me find something useful in configuring the code or some books useful.
If you have a qq number and our time are not rushed ,we can communicate in this way.(No facebook or twitter in china....How big the wall!)
My QQ number is 361180509
not sure I understood what you mean, do you have access to newer (froyo) kernel sources for I5800? if so, please do share
eclair kernel source is on opensource.samsung.com, and they compile just fine with the official Android toolkit, but Samsung's changes for Froyo are nowhere to be found (a few modules missing, touchscreen and accelerometer being the most notable), and the kernel doesn't compile anyway.
ze-m0n5t3r said:
not sure I understood what you mean, do you have access to newer (froyo) kernel sources for I5800? if so, please do share
eclair kernel source is on opensource.samsung.com, and they compile just fine with the official Android toolkit, but Samsung's changes for Froyo are nowhere to be found (a few modules missing, touchscreen and accelerometer being the most notable), and the kernel doesn't compile anyway.
Click to expand...
Click to collapse
Not sure if i get you right, do you say it does, or it does not compile? If not, we should request propper sources from Samsung.
sorry,I just don't find the offical source code website before posting this.Cause I just a freshman and I haven't got my PC....
maybe I'll compile the source code later.Sorry to make these mistakes.And I'm chnese.So my english is poor.....
Sent from my GT-I5800 using XDA App
FadeFx said:
Not sure if i get you right, do you say it does, or it does not compile? If not, we should request propper sources from Samsung.
Click to expand...
Click to collapse
eclair sources compile just fine, both with my system cross-compiling toolkit (arm-android-linux-gnueabi managed on gentoo by crossdev) and with the prebuilt one that comes with the Android platform
I might give it a try to actually boot it (but I would need to construct an initramfs, and it's a lot of work, and I kinda need to get back to "proper" work, I was consumed by Android during the last 3 weeks since I got the phone )
ze-m0n5t3r said:
eclair sources compile just fine, both with my system cross-compiling toolkit (arm-android-linux-gnueabi managed on gentoo by crossdev) and with the prebuilt one that comes with the Android platform
I might give it a try to actually boot it (but I would need to construct an initramfs, and it's a lot of work, and I kinda need to get back to "proper" work, I was consumed by Android during the last 3 weeks since I got the phone )
Click to expand...
Click to collapse
You can use the initramfs from Eclair.. I'm assuming you're talking about 2.1.. since 2.2 sources aren't out yet for this phone.
Link for the initramfs for Eclair is here: http://www.multiupload.com/U6GB5BB3HI
This is the JK1 I think - or whatever eclair rom I posted up previously
can someone explain to me if you were to find the android 3.0-3.2 firmware and or source code files that are used on a tablet (obviously itd be a honeycomb os), with the source code file could work on porting a honeycomb rom be attempted ? or is the firmware/source code im speaking of incorrect of whats needed in rom development. I found an article and have downloaded what was both labeled source code (there were versions used by manufacturer for android 3.0 -3.2) i downloaded the 3.0 version of the "source code" and i also downloaded a matching version of the firmware for android 3.0 used by manufacturer. just looking for more insight before i start posting links or anything, want to make sure I'm giving accurate information .
Jon_Mull said:
can someone explain to me if you were to find the android 3.0-3.2 firmware and or source code files that are used on a tablet (obviously itd be a honeycomb os), with the source code file could work on porting a honeycomb rom be attempted ? or is the firmware/source code im speaking of incorrect of whats needed in rom development. I found an article and have downloaded what was both labeled source code (there were versions used by manufacturer for android 3.0 -3.2) i downloaded the 3.0 version of the "source code" and i also downloaded a matching version of the firmware for android 3.0 used by manufacturer. just looking for more insight before i start posting links or anything, want to make sure I'm giving accurate information .
Click to expand...
Click to collapse
Given that Google has not officially released the source code, you'd be posting warez which is against forum rules. Once Google officially releases source, devs could try to port it to the G2x but with ICS so close to being released/announced, I bet most people would wait for that since it officially supports smaller and lower resolution screens like the ones in phones.
Your correct google has not but other manufactures of tablets using honeycomb have. Following the general public license released the source code which has been made aware of to google by said manufacture. The source code as well as firm ware is readily available without by passing anytype of payment or "pirating" . So how would this be considered warez?
I was under the impression that they only released their specific bits of code and not the entire source code. I may be wrong, this isn't something I've been watching closely.
I don't think Honeycomb has been released yet. All custom roms are stock based. We have OC/UV kernels but the roms are just slight variants of stock.
Sent from my LG-P999 using xda premium
Maybe i misread something , but if you google something along the lines of asus honeycomb source code, you'll find a link to asustek which has said source code for various versions of honeycomb , ie 3.0-3.2 don't quote me on it being 100% being what people are looking for just something i stumbled across
Hi,
Nowadays I'm going to do some work in firmwares and I've looked for the full P6200L source tree in a lot of places, but I had no success.
In this post (http://forum.xda-developers.com/showthread.php?t=1576553&page=1) I saw a huge and great discussion regarding port cyanogen 6 to the devices P6200 like. Unfortunately I'm not allowed to post comments directly there.
Can some one point to me where can I find the latest source code that @aorth is using to generate those builds?
ss.plinio said:
Hi,
Nowadays I'm going to do some work in firmwares and I've looked for the full P6200L source tree in a lot of places, but I had no success.
In this post (http://forum.xda-developers.com/showthread.php?t=1576553&page=1) I saw a huge and great discussion regarding port cyanogen 6 to the devices P6200 like. Unfortunately I'm not allowed to post comments directly there.
Can some one point to me where can I find the latest source code that @aorth is using to generate those builds?
Click to expand...
Click to collapse
Guys, @aorth send a message to me. I think this thread may be closed now.
Thanks.
hello, so i have been in communication with huawei regrading the kernel source. i mentioned the lack of source files for the mate 7 and how its part of the google/android agreement that oems must share all relevant sources for devices that use any part of android. they replied with the usual reply about how they will work hard to resolve this issue and whatnot. the rep did give me a link to the kernel source which i believe is for kitkat but i cant be sure so i hope that someone can verify.
having said that, why cant the kitkat source be used to build for lollipop and marshmallow? im still using a nook hd+ that is running MM......... WHAT??? how is this possible if the only kernel provided was for ICS? anyway, im going to keep poking at them until they either give up the LP/MM sources of they tell me to ****off. so, if anyone can please check out the link i would really appreciate it.
Lollipop Kernel?
Well as you all know, Nougat just landed officially on Newer Nexuses & AOSP Source code. and unfortunately N5 wasn't "good enough" to get official google support, but we'll soon get Nougat test on our beloved N5 thanks to great Dev community supporting it.
but i was wondering the Question that title says !
though AOSP Source code is uploaded for 7.0 release , there are some binaries that i believe closed source https://developers.google.com/android/nexus/drivers#hammerhead , and i think they should be updated as well to properly work any new update on device , that's why we see binary files updated by google till now for every official update.
but as N5 is now drop-out of Official support,so google surly will not provide updated binary patches, so does hardware company (Broadcom, Qualcomm , LG ) provides these patches after official support OR our Dev do some digging even though they are closed source and finally by trial & error they fix/updates these binaries ? if it's done by Devs individually, wouldn't everyone's thought for dealing with problem might be different which ends up making some ROMs more stable on one area and others in some different area !
( PS: Well you might got it from Question it self that i'm not a proper technical person in Android and even in that matter in coding , i'm just a guy who wonder these thing & tried to find answer on google but didn't get any satisfactory so end up asking in new thread instead on QA thread so that some one like me also get to know about it also , my previous device (Samsung i9070 ), having closed source CPU (NovaThor U8500) & CPU maker drifted from business , gave insane trouble to XDA devs while porting unofficial updates, so they fed-up and drifted away to new device within months which makes me more curious about this Question, hopefully i'll get proper answer from a Dev/Experienced Member )
jineshpatel30 said:
Well as you all know, Nougat just landed officially on Newer Nexuses & AOSP Source code. and unfortunately N5 wasn't "good enough" to get official google support, but we'll soon get Nougat test on our beloved N5 thanks to great Dev community supporting it.
but i was wondering the Question that title says !
though AOSP Source code is uploaded for 7.0 release , there are some binaries that i believe closed source https://developers.google.com/android/nexus/drivers#hammerhead , and i think they should be updated as well to properly work any new update on device , that's why we see binary files updated by google till now for every official update.
but as N5 is now drop-out of Official support,so google surly will not provide updated binary patches, so does hardware company (Broadcom, Qualcomm , LG ) provides these patches after official support OR our Dev do some digging even though they are closed source and finally by trial & error they fix/updates these binaries ? if it's done by Devs individually, wouldn't everyone's thought for dealing with problem might be different which ends up making some ROMs more stable on one area and others in some different area !
( PS: Well you might got it from Question it self that i'm not a proper technical person in Android and even in that matter in coding , i'm just a guy who wonder these thing & tried to find answer on google but didn't get any satisfactory so end up asking in new thread instead on QA thread so that some one like me also get to know about it also , my previous device (Samsung i9070 ), having closed source CPU (NovaThor U8500) & CPU maker drifted from business , gave insane trouble to XDA devs while porting unofficial updates, so they fed-up and drifted away to new device within months which makes me more curious about this Question, hopefully i'll get proper answer from a Dev/Experienced Member )
Click to expand...
Click to collapse
Short answer: they don't. Either they use old binaries that still work, or they use binaries from similar devices that are updated. For example, the nougat build available here for the nexus 5 has been built on old marshmallow binaries. Only the kernel can be modified since it's open source. There is not much we can do with closed source blobs unfortunately...