I heard that Samsung has released the kernel source files for the exynos. Does that mean that we will get a lot of roms like cyanogenmod and miui? I bought the S6 and I never knew it is hard to make roms for my device. Is it the same case with the S7?
Still the same ....exynos is closed source processor ... They have to release kernel source but not propriety files like drivers etc
Sent from my Nexus 6 using Tapatalk
Related
There is samsung's ics for galaxy s 2, so is it possible to port it to sgs?
http://www.sammobile.com/2011/12/14/exclsuive-android-4-0-1-by-samsung-for-sgs2-custom/
There are only few features what can be ported to i9000 cause of reallly diffrent pcb used in sgsII.. more realiable is using sources from nexus S when they will be avaible... also if samsung is working on ics for sgsII they can use their resources to made rom for i9000 preaty fast.. and here is one more thing samsung not forgot about us cause of relasing few new roms in past month even yesterday xD
Ok, thanks for your answer. Let's hope that nexus s ics sources comes out soon.
We have ufficial ics from samsung
Sent from my GT-I9000 using XDA App
there are already very good ports by team hack sung, why bother with those other ones?
Nexus S also as not received the official ICS yet, their ICS ports are weaker than the i9000 ICS ports
quite offtopic answer but team hack sung could make their build more modern.. that means go step further and dont using old kernel resources 2.6.35/7 and go direct to kernels 3.0.8... (they need to port drivers to new api anyway) only nikademus pawtip onecosmic AFAIK(I'm new here in i9000) trying to do sth with it... but i know that kerels 3.0.x works with less laginnes after some time,, its may be cause of many junks and workarounds in obsolete 2.x.x kernels.... thats my point
Yeah as said the ICS builds posted in the Android Development forum would be much better than bloated touchwiz ICS. If you have problems with bugs it's best to be patient until they are fixed.
OK, so so here is a thought. Since the stock ROM for the I9500 and the Korean SHV-E300 has all of the lib files necessary for creation of a ROM, why doesn't someone just use those to try to port a ROM over to see how it would actually work? I just came from the Exhibit 4G and that is pretty much how our device tree was created. Using other phones and our own libs. I know it would take a dedicated dev to do this or attempt it. But in the end it should be very rewarding. Tell me what you guys think.
Sent from my SHV-E300K using Tapatalk 2
lunerceli said:
OK, so so here is a thought. Since the stock ROM for the I9500 and the Korean SHV-E300 has all of the lib files necessary for creation of a ROM, why doesn't someone just use those to try to port a ROM over to see how it would actually work? I just came from the Exhibit 4G and that is pretty much how our device tree was created. Using other phones and our own libs. I know it would take a dedicated dev to do this or attempt it. But in the end it should be very rewarding. Tell me what you guys think.
Sent from my SHV-E300K using Tapatalk 2
Click to expand...
Click to collapse
+1
any dev that can verify this ? possible or not ? any port rom would do Ex. MIUI Rom
It is kind of like porting but not really. It would be using all of our already made drivers that are in .so format and then using partial or full frameworks from the custom ROM sources to build. Just look at it like taking Ubuntu 13.10 and running Gnome 3.8 on top of it as the shell. Neither one of them get along with each other but there are ways to make them coexist and work well together.
Sent from my SHV-E300K using Tapatalk 2
Does google or samsung post the rom source for GPE devices, like google does for nexus?
I ask because I could not find any source @ google's repo for this device, yet - i see people posting that they build i9505g roms from source.
Thanks.
erid2thed said:
Does google or samsung post the rom source for GPE devices, like google does for nexus?
I ask because I could not find any source @ google's repo for this device, yet - i see people posting that they build i9505g roms from source.
Thanks.
Click to expand...
Click to collapse
No. The GPE devices are not supported in AOSP. The ROMs and kernels are built by the OEMs, with support from Google. Samsung makes the GPL sections of the kernel available, but no ROM code and no binaries/drivers. As far as factory images go, those would have to be provided by Samsung and they do not provide them. I am surprised, however, that SamMobile doesn't have anything available.
Sent from my Nexus 10 using Tapatalk 4
oldblue910 said:
No. The GPE devices are not supported in AOSP. The ROMs and kernels are built by the OEMs, with support from Google. Samsung makes the GPL sections of the kernel available, but no ROM code and no binaries/drivers. As far as factory images go, those would have to be provided by Samsung and they do not provide them. I am surprised, however, that SamMobile doesn't have anything available.
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Thanks
BTW - i made a kernel for 4.4 roms on the m919/i9505g
dont have enough posts to post it here, but uploading source to github.
Been on it for a few days, and I like
MODS: can i post kernel in this section until I get enough posts? or do i need to wait before I post kernel?
I want to try and build KitKat from source for the note 3.
Firstly, is it possible, using the AOSP source? (Not CM)
The Samsung kernel source code comes with a "platform" package, can this be used for building a working rom for N9005?
I've already built the kernel, now I want a rom from source.
Also, I did read CM have started working on it for the Note 3, is there current w.i.p code available?
I am mostly interested in how to get it to boot.
Sent from my SM-N9005 using Tapatalk
Hey guys, title says it all. Ive been hearing about CAF since 4.3 and I did do a lot of Googling. But I have no idea what it is. If someone can explain it to me, I'd be really grateful!!
Have a look here: https://www.codeaurora.org/projects/all-active-projects/linux-msm
So I'm assuming CAF stands for Code Aurora Firmware?
It's basically drivers and such from Qualcomm instead of AOSP or stock Google. Other Qualcomm devices use these and the performance is supposedly better.
Sent from my Nexus 7 using Tapatalk