Related
This is a great site with source code for all their OI apps and sample implementations. Definitely check it out if you're a dev:
http://www.openintents.org/en/
Hey devs, lawyers and people who know about GPL
I have a question about using GPL'ed source code in a closed source application.
Another question has been easily answered in the news comments, but as libav/ffmpeg is LGPL and has a nice legal.html it was solved quickly.
Here is what it's all about:
- I'm going to use Linux kernel drivers code (several (ten-)thousand lines of code across 10+ files) for several USB devices using JNI and the Android USB host interface
- I'm writing a wrapper / "glue" library so almost no changes have to be made to the GPL code (to keep compatibility with newer versions of the GPL code)
Now my question is: Can I link all the *.o in one shared library or do I have to separate GPL code and wrapper (may be closed source) code into different shared libraries (wrapper may still link to GPL code).
If this is illegal, does my wrapper code have to be GPL'ed as well, because it links against GPL code?
And how much / what of my application has to be GPL'ed since it uses GPL'ed code in any way?
As you can see I'm a bit confused about all the GPL stuff and don't want to get sued or blamed for violating the GPL.
PS: I'm still not sure if I may open source the app or not, but in case I don't want or can't to, I want to be legal at least.
I've done some more research and found out that it is not possible to link closed source directly to GPL'ed code, BUT it is possible to link against LGPL which itself is compatible with the GPL.
So in other words: The wrapper library itself will be open-sourced under the LGPL but the Android application, where most of the work will be done (UI, services, device handling, interfaces, etc.), may be still closed source.
Does this work?
chrulri said:
Does this work?
Click to expand...
Click to collapse
No, it doesn't. Read me. Unless one will pipe all the data flow through command line interface where the GPL'ed binary is running in a separated process (e.g. child process). Well even this is still a "slippery" path, concerning legal issues.
I guess I'll just GPL my app and hope for donations once it's published.
I am starting android dev soon.
I want to use open source apps and modify them than publish them to google play for commercial use?
Does open source really mean I am able to use the open source code from f-droid and modify and use for commercial?
Is this how developers are efficiently coding these days? Is writing a program from scratch obsolete if it is available in open source?
Does anyone know any successful google play store apps that are purely based off open source? It would be helpful to see examples.
Muzei and Dashclock are both open source and good examples of how android apps should be.
But be aware that just because an app is open source that doesn't mean you can modify it and distribute is as your own
Source: Slashdot
Qualcomm has forced GitHub to remove over 100 repositories due to "unauthorized publication, disclosure, and copying of highly sensitive, confidential, trade secret, and copyright-protected documents." Among the repositories taken down were for CyanogenMod and Sony Xperia. The issue though is that these "highly sensitive" and "confidential" files are Linux kernel code and reference/sample code files that can be easily found elsewhere, including the Android kernel, but GitHub has complied with Qualcomm's DMCA request.
Click to expand...
Click to collapse
That's not good.
Umm... Wow
Then, there is this...http://www.androidpolice.com/2014/0...some-belonging-to-cyanogen-sony-and-qualcomm/
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
https://developer.sony.com/develop/open-devices/
Unified 4.9 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Bug tracker
https://github.com/sonyxperiadev/bug_tracker/issues
Excited to see that y'all are opening things up
As someone who has been enjoying the Xperia 10 since launch, I'm excited to see that y'all are opening things up! It'd be amazing to see a list of Sony projects used in these phones and whether they are open source, whether there's a plan to open-source them, or details on why there is a necessity for them to remain proprietary. Having roadmaps for these things feels like a simple way to maintain straight-forward communication with users.
Thanks for sharing this with everyone and striving to keep things open!
Since now the kernel and firmware are freely available, when can we expect a build of TWRP to be available for the Xperia 10?
jerpelea said:
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
https://developer.sony.com/develop/open-devices/
Unified 4.9 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Bug tracker
https://github.com/sonyxperiadev/bug_tracker/issues
Click to expand...
Click to collapse
Hi, I love the Xperia Open Devices initiative, please keep that up.
A few issues though: the Xperia 1 still hasn't been added to the Open Devices list, and Xperia Transfer Mobile doesn't work with the Xperia 1 and Xperia 10. And DRM keys for the camera is a bit lame; the original Xperia Z didn't have DRM issues when installing custom-ROMs on it, and neither should newer high-end Xperia flagships.
Anyway, my requests/feedback:
1) Please add the Xperia 1 to the Open Devices list (it's beyond me how you can include the Xperia 10 to Open Devices, but not the Xperia 1, what's up with that?).
2) Please update the Xperia Transfer Mobile so that it works with the Xperia 1/10, and also with Xperia devices that run on LineageOS (I have LineageOS running on my Xperia Z, and XTM doesn't work on it, and that's lame). I need to move my app data from my Xperia XZ to my Xperia 1.
3) Please bring back the stylish OmniBalance design as seen and perfected on the original Xperia Z and especially the Z2. The Xperia 1 design is a step in the right direction compared to the Xperia X series (whose design was very generic and pedestrian compared to the Xperia Z series), and the Xperia 1 design is reminiscent of the Xperia Z2 somewhat, but it's not quite a home run if you know what I mean. The Xperia Z2 is the sexiest smartphone ever, looks totally futuristic and something like straight out of Back to the Future 2 or Voltron.
Anyway, that's just my 2 cents. It's not exactly comforting that the Xperia 1 still isn't on the Open Devices list. Over the years, I've had a lot of respect for Sony for your Open Devices commitment.
@jerpelea
Now that Sony very regretfully abonded the xz1c after 1 Android update, although the device having treble etc.
When do you expect the drivers for xz1c for Android 10 is stable.
https://developer.sony.com/file/dow...es-for-aosp-android-10-0-kernel-4-14-yoshino/
The word on the forums are the drivers are unstable as of now, to be used for meaningful Android 10 aosp.