Samsung Galaxy Note II Source Code Released 32
An anonymous reader writes "Samsung has released the source code for the Samsung GALAXY Note II. This clears the way for custom ROM's for the smartphone. From the article: 'It's now been posted for the international GT-N7100 model, giving developers a peek at the 5.5-incher's inner workings and allowing them to get to work on new mods.'"
Link in summary is (slightly) wrong (Score:5, Informative)
http://www.engadget.com/2012/10/08/samsung-releases-galaxy-note-ii-source-code/ [engadget.com]
Re:Link in summary is (slightly) wrong (Score:5, Informative)
Why link to an ad-filled hit-whore website?
How about straight to the source:
http://opensource.samsung.com/ [samsung.com]
Re: (Score:2, Informative)
Re: (Score:1)
Link [engadget.com]
In case anyone here actually wants to read the article.
Just as I suspected. (Score:5, Funny)
Copyright (C) 2005, 2006, 2007, 2008, 2009 Apple Inc. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY APPLE INC. AND ITS CONTRIBUTORS ``AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES,.....
Re:Just as I suspected. (Score:5, Funny)
Re: (Score:2)
Is that the Webkit source? Some of that is in the 2 clause BSD licence, and Apple are involved in it. The original authors were the KDE project though.
Re: (Score:3)
This is much better than the competitors walled garden(s). I'd much rather have control of my own landscape, weeds and all, than have a perfectly designed and maintained landscape that somehow still feels cold and sterile.
But Apple gives you a fully hoe'd garden [youtube.com]! All they want is your money (and all of it).
With Android (S3 user here, my daughter got HTC), you get the garden you want.
Re: (Score:1)
With Android (S3 user here, my daughter got HTC), you get the garden you want
So long as you don't want to change the configuration of the garden. That would require you to find a way to dupe one of the garden staff into giving you Head Gardner privileges.
However that same exploit is also what bad guys use when they want to trash the garden, but we overlook that in Android World for some reason.
Re: (Score:1)
Hey now, we only allow extended car metaphors here. We'll have none of your wild garden talk!
Re:good, freedom (Score:4, Informative)
The complete lack of any signature checking of /system when flashing images with Odin makes rooting Samsungs child's play.
I have to give Samsung credit - while working with the Exynos platform is a nightmare for a Cyanogenmod device maintainer, their lenient bootloader locking policies are unsurpassed.
meh (Score:5, Insightful)
Re: (Score:1)
It's better than nothing, and it's because of them we can be sure to see custom firmwares like CyanogenMod within days, more likely hours of its release. And it's definitely better than most other manufacturers that wait months to release the source (or those that don't at all).
Re:meh (Score:5, Insightful)
Wrong. If you look at the history of CM bringups, kernel source is a small part of the equation.
I have no idea why this was able to make Slashdot. Really, since when is an Android manufacturer doing the utterly bare legal minimum of what they are required to do by the GPL newsworthy? Do we even know if they're even complying with the GPL with this release? (See below...)
As to CyanogenMod on Note 2 - It's not going to happen unless a new maintainer steps up to the plate. None of the current Exynos maintainers have any intention on purchasing any additional non-Nexus Exynos devices. We're tired of Samsung's constant GPL violations (Frequently, their source releases do NOT match that of shipped devices - for example none of the source releases for the Note 10.1 produce a viable BCM4334 driver for wi-fi.) and of their total lack of cooperation with the open source community.
Take a look at the omapzoom (TI) reference platform source. Take a look at CodeAurora (Qualcomm) reference platform source. Then take a look at the Insignal git repos, or one of Hardkernel's 2GB tarballs. Note that of the two latter examples (both for Exynos), neither has a respository with any git history. They also don't even remotely match anything that is in Samsung's shipped devices in addition to being vastly outdated. If you use the Hardkernel or Insignal hardwarecomposer source code on a device, and then completely delete hwcomposer, you will see ZERO DIFFERENCE in behavior!
Background: I am the CyanogenMod co-maintainer for the AT&T Galaxy S II (SGH-I777), International Galaxy Note (GT-N7000), and Note 10.1 (GT-N8013). The GT-N8013 is my last non-Nexus Exynos device as I'm tired of working with an undocumented platform with no source code and broken hacked-up binaries. On a regular basis, the quality of CM on Exynos devices lags months behind OMAP and Qualcomm devices due to this. I'd like to, for once, be able to actually maintain a device that's in good shape and start focusing on adding new features, instead of constantly fighting massive bugs due to the lack of documentation of Samsung's blobs. (Of which we have FAR more to deal with than OMAP or Qualcomm devices.)
Re: (Score:2, Funny)
Mod this up!!!!
If you have no idea what he just said, his 3-digit UID and Cornell e-mail should give you a hint that he knows his shit.
Re: (Score:1)
Re: (Score:2)
I'm rather surprised by this. Didn't cyanogen get hired by Samsung? Why aren't Samsung's open source releases and documentation better?
Re:meh (Score:5, Interesting)
He works for Samsung USA. Samsung Korea is the one controlling nearly anything Exynos-related. The situation for Qualcomm and OMAP-based Samsungs is quite a bit better - While it seems he doesn't have the authority to use any source code outside of what is available from CAF, the fact is he has a high degree of familiarity with these devices and hence knows how to get the CAF stuff to work VERY well. (The USA guys have, historically, primarily worked with Qualcomm-based devices.)
The CM Exynos maintainers do have a contact within Samsung Korea, but nearly all of the time when our contact forwards requests to the relevant department, the answer is either "no" or it is a blatant lie. (See the above comment about the Note 10.1 GPL compliance issues - the OSRC guys actually had the balls to claim that the UEALGB build, which was preinstalled on every Note 10.1 sold in the USA for at least one month, was a "leak" and hence they didn't have to provide source that matched it.) Our contact DOES care and wants to make a difference, but their management and the other departments within Samsung Mobile are completely noncooperative.
Re: (Score:2)
BTW as an SGH-1777 owner, thanks! Running a CM10 without issues.
Re: (Score:2)
Re: (Score:2)
Probably a little bit of both. "Mine, mine, mine!" and "Go away, you smelly nerd."
Re: (Score:2)
WRONG. The bcmdhd driver IS GPLv2.
See https://github.com/CyanogenMod/android_kernel_samsung_smdk4412/blob/jellybean/drivers/net/wireless/bcmdhd/bcmsdh_linux.c [github.com] as one example.
The only place in which your statement is valid is the AR6k fiasco on the Tab 7 Plus and Tab 7.7 - These DO have a driver that is dual-license GPL and BSD from Atheros, Samsung chooses BSD. While it is insanely frustrating, I can't throw Samsung under the bus for GPL noncompliance with this one. However, I can for bcmdhd.
Re: (Score:2)
It's an unofficial winzip kang... Winzip kangs NEVER manage to make it to the finish line, it's simply impossible.
You know, it's the perfect opportunity for a new maintainer to create a device try and to try and patch support into the kernel... But if no one has even bothered to do that it's not good.
Bringing up CM10 on the device won't be difficult - Getting N7100 working as well as I9300 wouldn't be difficult at all. It's just that none of the current maintainers with Exynos experience have any desire