Develop Bugs

The GPL obligates Samsung to give us the kernel source

Samsung has given us a kernel source. However, from all the devs, I have heard that this is not the source code for the kernel that is on our phones, and the resulting compiled kernel is not exactly the same as the stock flashed kernel.
The GPL doesn't obligate Samsung to release a source for a kernel, it obligates Samsung to release the source for our kernel.
Maybe if enough of us contact Samsung on this issue, they will release the correct source. I found a way to contact their open-source department about this.
Go to:
https://opensource.samsung.com/
Select Mobile => Mobile phone from the dropdown
Search on the page for SPH-D710 (that's our phones' model number)
On the far-right there is an envelope you can use to contact them.
Use it and ask that they release the actual source code for the shipped kernel version.

I think this came up on a few phones before, maybe it was my OG Epic. I think I remember they have 90 days or "in a timely manner" to release the source. When it all comes down to it, there really isn't much we, or anyone can do, to force it. It's almost an honor system.
Some of the devs around here will have better specifics though.

jirafabo said:
I think this came up on a few phones before, maybe it was my OG Epic. I think I remember they have 90 days or "in a timely manner" to release the source. When it all comes down to it, there really isn't much we, or anyone can do, to force it. It's almost an honor system.
Some of the devs around here will have better specifics though.
Click to expand...
Click to collapse
Did the OG Epic fellows ever manage to get Samsung to release the real source?

jirafabo said:
I think this came up on a few phones before, maybe it was my OG Epic. I think I remember they have 90 days or "in a timely manner" to release the source. When it all comes down to it, there really isn't much we, or anyone can do, to force it. It's almost an honor system.
Some of the devs around here will have better specifics though.
Click to expand...
Click to collapse
There is no 90 day grace period. The kernel source code must be made available when the compiled kernel is made available.

Really, the only recourse is to sue. And since Google owns the copyright, my guess is that they would have to be the ones to sue (not a lawyer, so not 100% sure).
The odds of Google suing Samsung are about as good as the odds of OJ finding the real killer, so we are basically screwed.
Situations like this seriously undermine the open source nature of Android. If it happens enough to where Android loses market share because people doubt Google's commitment to open source, then they might do something about it. Since this issue probably only matters to a few percent of Android users, that's not very likely.
Don't get me wrong - I'm still a big fan of Google, but their philosophy of "do no evil" cannot be maintained forever as a publicly traded corporation. In the long run, "shareholder value" and the bottom line will win. Even more the reason to do what we can to keep Android as open as possible.
Sent from my SPH-D710 using xda premium

Maybe if enough of us contact Samsung on this issue, they will release the correct source. I found a way to contact their open-source department about this.
Go to:
https://opensource.samsung.com/
Select Mobile => Mobile phone from the dropdown
Search on the page for SPH-D710 (that's our phones' model number)
On the far-right there is an envelope you can use to contact them.
Use it and ask that they release the actual source code for the shipped kernel version.

Some one with some pull around here needs to contact Cyanogen... He does work for Samsung after all.
Samsung Galaxy S II

I don't think it is clear whether
1) source is the wrong source
2) source is incomplete but builds ok
3) source is broken/buggy
4) source is correct, but build parameters are slightly off

Okay, so I just received a response from Samsung actually.
♦ classification : Mobile Phone ♦
♦ model name : SPH-D710 ♦
Dear Customer,
Thank you for your continuous interest in our product.
Supported kernel version(EG30) is correct.
Where did you check the version?
Sincerely yours,
You may find the source code
Click to expand...
Click to collapse
Could a dev chime in on how we know the source version provided is incorrect? I have seen this referenced numerous times, with it cited as a possible reason LOS seems exacerbated on custom ROMs. If no dev sees this, can anyone point to one of the threads where a dev said this so that we can ask them for more information?

manekineko said:
Okay, so I just received a response from Samsung actually.
Could a dev chime in on how we know the source version provided is incorrect? I have seen this referenced numerous times, with it cited as a possible reason LOS seems exacerbated on custom ROMs. If no dev sees this, can anyone point to one of the threads where a dev said this so that we can ask them for more information?
Click to expand...
Click to collapse
+1
I was surprised to get a response from them so quickly.
If we don't get a response from a dev it wouldn't be to hard to investigate ourselves.
-Compile kernel from source (they give instructions)
-Flash to phone
-show different version # compared to stock

I just got the same reply. We need some info on what to say back. Developers please chime in. Thanks
Sent From My Evo Killer!!!

Okay, so I tracked down one of the places where I've seen reference to the fact that the source Samsung released isn't right.
The ACS Stock Kernel thread says:
Well as everyone knows, the source released from samsung was some bull****... LoStKernel, makes the best use of that source and adds lots of tweaks, and in my opinion is the best compiled custom kernel available...
But, some people stand by the point that only the stock pulled kernel is free from LoS, or is the LoS is least Rampant for them in that kernel.. But they want CWM too!
Click to expand...
Click to collapse
I private messaged the dev of that kernel, chris41g.
I also contacted zedomax, since he's also a kernel dev and I figure as such he might know something about this.
If anyone can think of anyone else that can shed more light on this, feel free to chime in.

manekineko said:
Okay, so I tracked down one of the places where I've seen reference to the fact that the source Samsung released isn't right.
The ACS Stock Kernel thread says:
I private messaged the dev of that kernel, chris41g.
I also contacted zedomax, since he's also a kernel dev and I figure as such he might know something about this.
If anyone can think of anyone else that can shed more light on this, feel free to chime in.
Click to expand...
Click to collapse
Good. Please post when you get some info as I would love to email Samsung back about this.
Sent From My Evo Killer!!!

Evo3d people have some individuals who would request a kernel source whenever a new kernel was released. I forget specific names, but these people would get in touch with the legal department of HTC, and the source would usually be out within a month...

I've heard back from Zedomax and chris41g.
Zedo didn't know anything about this kernel source differing issue.
chris41g says that it is obvious the source and the stock kernel differ. According to him they have different version numbers and different configs, which should show up in dmesg and kmsgs. Unfortunately, he doesn't actually have an Epic 4G Touch, so he's not able to explain in more detail.
Can any who is on a compiled from source (not stock) kernel take a look at this and provide any more information on this?

If you talk.to Chris, tell him we can hook up my phone and he can access anything needed with TeamViewer like he did when he made one of his kernels
Sent from my Nexus S 4G using xda premium

JohnCorleone said:
If you talk.to Chris, tell him we can hook up my phone and he can access anything needed with TeamViewer like he did when he made one of his kernels
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Thanks, I messaged back Chris and let him know.

Keep up the work on this cause musclehead
Sent from my Nexus S 4G using xda premium

They will likely not release it in any other form. Chances are, they stripped proprietary bits from it before release, and didn't adjust the source to make usable after doing so. Its basically up to developers to fix it in this case.
If this is case, which I'm sure it likely is, as I've had conversations with Samsung about these types of things before, there really is no recourse other than someone stepping up and fixing the source. Samsung isn't required to release proprietary bits, and they're also not obligated to release source code that builds and boots the device right out of the box.
Good luck.
Sent from my SCH-I500 using XDA App

jt1134 said:
They will likely not release it in any other form. Chances are, they stripped proprietary bits from it before release, and didn't adjust the source to make usable after doing so. Its basically up to developers to fix it in this case.
If this is case, which I'm sure it likely is, as I've had conversations with Samsung about these types of things before, there really is no recourse other than someone stepping up and fixing the source. Samsung isn't required to release proprietary bits, and they're also not obligated to release source code that builds and boots the device right out of the box.
Good luck.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
This makes no sense, as the "proprietary bits" are the changes that are made to the kernel that fall outside of the vanilla kernel that google releases. You're saying those changes dont have to be released makes no sense. Otherwise everyone would just be re-releasing the same stock kernel that google puts out. All changes to the kernel made outside of whatever comes stock MUST be released according the to the GPL. So it doesnt matter what conversations you may or may not have had with whatever Samsung personnel. All that needs to be provided in this case is the differences in what we have and what they released. If a non-disputable change is found and easily comparable, then they have no legal choice.

[Q] Source Code is released with Google phones?

Hi.
I moved from S2.
Just got my GN today.
Unlike other phones, is it the case that Google phones have the Source Code released on the spot by Google?
I couldn't stand owning an Android phone, and having Samsung holding back the SC (and therefore disabling the ability of devs - such as CM - to make a stable roms based on AOSP. This was kinda of an oxymoron; on the one hand, an Android phone which is meant to be open. On the other, limited by not having the code).

http://code.google.com/android/nexus/images.html
here's the factory images. you can compile your own ROM from source if you want and it will work and there's a link on the side to do that (if you have the GSM version)

Zepius said:
http://code.google.com/android/nexus/images.html
here's the factory images. you can compile your own ROM from source if you want and it will work and there's a link on the side to do that (if you have the GSM version)
Click to expand...
Click to collapse
This makes one raise the Q: why would ANYONE buy a NON-GOOGLE phone?????
(S2 rant!)

Yes, source code is alwsys released for nexus phones. Thats the beauty of it. You can change code and compile your rom with ease and no hassle. Just like it came from the factory lol.

RogerPodacter said:
Yes, source code is alwsys released for nexus phones. Thats the beauty of it. You can change code and compile your rom with ease and no hassle. Just like it came from the factory lol.
Click to expand...
Click to collapse
AMAZING! What Android SHOULD BE LIKE !!!!

++ Calling all WebOS entusiasts and devs! ++

Goal: Bring a fully-functional Open WebOS port to the Galaxy Nexus, GSM and CDMA.
Members: jimmyco2008, PatimusXPrime, nitsua (Team Serendipity, the only team that gives ETAs!)
If you know your way around Enyo or Java or Javascript or WebOS of course, and you're interested in working with us on bringing WebOS to the Galaxy Nexus, drop any one of us a PM or reply to this thread!
-------------------------------------------------------------------------------------------------------------------------------------------
ETAs
Publish a CWM-flashable zip for easier installation - ehhh we didn't give up per sé, but we have a lot to do...
Restore all stock apps to WebOS image - same as above...
ETAs are tricky, and they aren't always accurate, which is why 99.9% of devs don't bother with them.. But I remember as a non-dev, I really wished devs would give ETAs, even if they weren't so accurate. Haters gonna hate. Anyway, if you don't see something in the ETA list, it doesn't mean we aren't working on it. For example, you don't see an ETA for a, I dunno, beta release, but for all we know we could have one in July (doubt it)... So take ETAs with a grain of salt, and give a cheer when one of our ETAs turns out to be accurate.
---------------------------------------------------------------------------------------------------------------------------------------
Downloads
Open WebOS daily builds by the WebOS-Ports Team
Team Serendipity Downloads (patience ain't just for doctors!)
o- recovery-flashable Zip (replaces Android, BACK UP YOUR DATA)
Torrents
The webo-sports-dev-image.ext2 file for Maguro (June 2013)
The .fastboot file that accompanies it
---------------------------------------------------------------------------------------------------------------------------------------
WebOS Files
WebOS.ext2 - The actual OS, pushed to the Galaxy Nexus emulated SD card.
WebOS.fastboot - The boot file flashed in the bootloader to temporarily boot WebOS (until a battery pull).
So when you go to either of the teams' download pages, you'll want the one that ends in .ext2 and the one that ends in .fastboot!
-----------------------------------------------------------------------------------------------------------------------------------------
Serendipity:
"Serendipity means a "happy accident" or "pleasant surprise"; specifically, the accident of finding something good or useful while not specifically searching for it. " - Wikipedia

Other Links & Info
jimmyco2008's "Let's Get This Over With" Guide for the WebOS-Ports Team's port
-------------------------------------------------------------------------------------------------------------------------
Updates
------------
06.06.13
Nothing big, but here's the .fastboot file converted to a boot.img that you can use just like any other boot.img.

Great. More efforts on this. Guys, i can get around to build, test, debug. Anyway, Subscribed.
Sent from my Nexus

Subscribed !
WebOS

I've been following Open WebOS for a while. I still miss my old Pre you know. Don't know too much about what goes into the build process (the WebOS Ports documentation needs work) and I only know a bit of Enyo so I doubt I can contribute. But WebOS on the Gnex sounds great!

Glad someone else is hanging onto WebOS! I agree, see the OP for a link to my guide, it's a little more verbose if you're struggling with theirs.

Very happy to see this! Hope you guys can get a stable release.

We put a hold on this for now, we will revisit it though
Sent from my Galaxy Nexus using Tapatalk 4 Beta

Updated OP with torrent files for the latest fastboot + ext2 file combo for Maguro.

If this will work on the Sprint variant, i'd be willing to sell my Galaxy S3 to be able to use WebOS on the Galaxy Nexus.

AnaMayShun said:
If this will work on the Sprint variant, i'd be willing to sell my Galaxy S3 to be able to use WebOS on the Galaxy Nexus.
Click to expand...
Click to collapse
I also have a sprint nexus... Any word? I would loooove to run webos on my nexus
Sent from my Galaxy Nexus using xda app-developers app

Isn't Sprint CDMA? If it is, this dev team is stating on THE FIRST POST that this will be for both GSM and CDMA variants.
a manta wrote this.

beekay201 said:
Isn't Sprint CDMA? If it is, this dev team is stating on THE FIRST POST that this will be for both GSM and CDMA variants.
a manta wrote this.
Click to expand...
Click to collapse
Goal: Bring a fully-functional Open WebOS port to the Galaxy Nexus, GSM and CDMA

AnaMayShun said:
Goal: Bring a fully-functional Open WebOS port to the Galaxy Nexus, GSM and CDMA
Click to expand...
Click to collapse
And? Your point being....?

beekay201 said:
And? Your point being....?
Click to expand...
Click to collapse
Your original message when quoting me was, "Isn't Sprint CDMA? If it is, very much unlikely it will work" so I showed you the msg in the first quote.

AnaMayShun said:
Your original message when quoting me was, "Isn't Sprint CDMA? If it is, very much unlikely it will work" so I showed you the msg in the first quote.
Click to expand...
Click to collapse
?
Did you even read what you quoted? You're now refering to something that I have edited, because naturally, I went back and reviewed the first post. Still, I don't know how they're going to pull CDMA support, because of all the proprietary stuff.
http://forums.webosnation.com/open-...webos-ports-prealpha-release.html#post3356317
If you read closely, you'll see that the poster is a dev for webos-internals.

following, always dreamed of having webos on a big screen. Trying to figure out if I can do the dual boot thing right now.

Don't get your pants in a knot, guys, we've basically given up. I'll still keep the thread up to date with stuff from the WebOS Ports Team, and should they get to like "beta" status, we'll explore getting it to play nice with the CDMA Galaxy Nexuses (Verizon first, then Sprint).
The WebOS Ports Team is still working on this, though, it turns out they update the build for the Galaxy Nexus pretty regularly.
Also remember that at this point, there are no "toro", "maguro", "toroplus" builds, the one build they have works with all three.
I have to edit the link to their builds, which I'll do right now, find it in the OP...

Would make me very happy to see this come to light. I'll subscribe and I'm open to some closed testing.
Sent from my Galaxy Nexus using xda premium

doing my yearly check in. what's the poop?

Nexus 7 LTE Binaries/Drivers in AOSP?

So as I understand it, much has been made about the difficulty of getting LTE in the Nexus line because of proprietary drivers and binaries. Consequently, when the Nexus 7 LTE was announced many rejoiced that we would finally have AOSP LTE. However, I also heard many caution and say that we could get something similar to the Verizon Nexus that just left that information out of AOSP.
So now that we've got the Nexus 7 LTE out and I believe also have the AOSP for the LTE variant out, what is the answer? Are all of the binaries and drivers there? Also, are there any other binaries or drivers left out of the AOSP?

So checking this page:
https://developers.google.com/android/nexus/images
...it looks like the image for the LTE variant might not have been released yet. If so, then I guess this question is not answerable yet.

... and checking this page, the last update is 7 weeks ago, the JLS36C is missing.
https://android.googlesource.com/device/asus/deb/
Looks like after Jean-Baptiste Queru has quit the AOSP nobody at google cares anymore. The End of AOSP? Hopefully not ... :crying:

So it's out now. Any additional thoughts?

I'm bumping this again as there has been some time to look at it now. thoughts?

Poke_N_PDA said:
I'm bumping this again as there has been some time to look at it now. thoughts?
Click to expand...
Click to collapse
I imagine development and including the binaries will be at the discretion of the devs. Some do it (like Carbon) while many others don't at all.
I think once adoption rate rises it will be more common.

driver binaries and factory images are available for Nexus 7 LTE (razorg). Not if the binaries are complete though.
https://developers.google.com/android/nexus/drivers#razorg
https://developers.google.com/android/nexus/images#razorg
EDIT: sorry, i think i mis-read your question.

[Q] Android L Port

Hey all,
I was wondering, since the new Android L came out, how come no one is rushing to have it on our S3? Is there a version that exists already? And if not, who would like to work on this (maybe with me)?
Thank you in advance.

There is not a single device with Android L and the source code has not been released. There are two preview builds that are not final for the Nexus 5 and 7. You should check your facts with a few seconds of googling before starting a thread like this.

sigmarelax said:
There is not a single device with Android L and the source code has not been released. There are two preview builds that are not final for the Nexus 5 and 7. You should check your facts with a few seconds of googling before starting a thread like this.
Click to expand...
Click to collapse
Google has released the SDK of the final Android 5.0 (L). Why would someone not be able to take the image file from there and make a port?

Porting a ROM is not as easy as it sounds.
I had Android L on my Nexus 4 for a while and didn't like the interface. Even after many revisions, it still is not perfect on the Nexus 4.

audit13 said:
Porting a ROM is not as easy as it sounds.
I had Android L on my Nexus 4 for a while and didn't like the interface. Even after many revisions, it still is not perfect on the Nexus 4.
Click to expand...
Click to collapse
That's true, I agree. I read some guides here on XDA on how to port a ROM. I'd very much do it for my S3, but there are some things i am not sure about, like the kernels and the modems. Ill need to read up on it if I decide to do it myself.

scrat55 said:
Google has released the SDK of the final Android 5.0 (L). Why would someone not be able to take the image file from there and make a port?
Click to expand...
Click to collapse
The SDK is not an operating system. It is documentation on how to create apps that will run well and look nice on the operating system. The images for the nexus 5 and 7 could indeed be ported, but it would take a good chunk of time and be buggy (as interfacing with certain hardware probably would be broken). It would also make no sense to work on such a port project because Android L source code will likely be released in early November. Building Android L for the S3 from source code would be much more ideal, and will definitely be done once L's source code is released

sigmarelax said:
The SDK is not an operating system. It is documentation on how to create apps that will run well and look nice on the operating system. The images for the nexus 5 and 7 could indeed be ported, but it would take a good chunk of time and be buggy (as interfacing with certain hardware probably would be broken). It would also make no sense to work on such a port project because Android L source code will likely be released in early November. Building Android L for the S3 from source code would be much more ideal, and will definitely be done once L's source code is released
Click to expand...
Click to collapse
Ah roger that, thank you for a well explained reply mate.
Cheers!