As everyone know, it's legal to use LGPL libs in commercial software but it's mandatory to provide your closed source object files somewhere, so people can repack the software with new or modified version of those libs. Think about a commercial android app which uses some LGPL libs. I want to find the best way to provide the object files beside LGPL libs without making my customers concerning about these things.
There's three major questions about it:
How to provide an instruction manual for others to how to repack an APK file with those objects (is there any sample of such an instruction?)
What kind of tools needed for repacking?
Where to provide these materials to comply with license? (ex. In App itself, in a website related to that app or other locations)
Thanks in advance
Related
i have always been under the impression that aosp is android OPEN SOURCE project..therefore anyone can use it, you shouldnt need "permission"..just proper credits....did anyone get permission from google to use the code in the first place? So could someone please explain to me who the hell owns this code...thanks
Firstly, I'm not a lawyer so if you use the source code for Android, make a million dollars, and Google comes after you, don't come to me.
Now that that's out of the way, in open source projects, the source code is usually owned by the author. For example, if someone decided to make an alternate version of an open source project, he/she would own that code.
But owning the code doesn't mean someone can do anything with it. The thing that makes Open Source code open are the terms of use, or license that accompanies it. Most open source licenses describe (among other things) that people are free to do whatever they want with the code as long as derivative works follow the same license, include the license text and are also made available in source code form.
But this is just a general explanation of common open source license terms. For more details, have a look at the license that ships with the Android source code. Since it can change you're better off just delving in and reading it.
Enjoy,
- chris
As Android is built off of Linux and filed with the GPL2 license that would be your best option. As for permission being asked that is an XDA rule as it is respect which is very lacking as of late. Also the reason for developers holding the best stuff to themselfs and other respectable developers that know what real development is. Using the work of others and adding a theme is not development neither is kang builds. Far too much of this going on.
cttttt said:
Firstly, I'm not a lawyer so if you use the source code for Android, make a million dollars, and Google comes after you, don't come to me.
Now that that's out of the way, in open source projects, the source code is usually owned by the author. For example, if someone decided to make an alternate version of an open source project, he/she would own that code.
But owning the code doesn't mean someone can do anything with it. The thing that makes Open Source code open are the terms of use, or license that accompanies it. Most open source licenses describe (among other things) that people are free to do whatever they want with the code as long as derivative works follow the same license, include the license text and are also made available in source code form.
But this is just a general explanation of common open source license terms. For more details, have a look at the license that ships with the Android source code. Since it can change you're better off just delving in and reading it.
Enjoy,
- chris
Click to expand...
Click to collapse
Thanks for taking the time to write that...I think I understand a little now
Sent from my PC36100 using XDA App
I'm familiar with apktool and have been using it for some time to decompile apps and modify them, usually just cosmetic changes through xml. However, I am beginning to see how easy it is to change actual functionality of an app via smali edits. I see in the Google Play terms of service:
You agree that you will not, and will not allow any third party to, (i) copy, sell, license, distribute, transfer, modify, adapt, translate, prepare derivative works from, decompile, reverse engineer, disassemble or otherwise attempt to derive source code from the Products, unless otherwise permitted, (ii) take any action to circumvent or defeat the security or content usage rules provided, deployed or enforced by any functionality (including without limitation digital rights management or forward-lock functionality) in the Products, (iii) use the Products to access, copy, transfer, transcode or retransmit content in violation of any law or third party rights, or (iv) remove, obscure, or alter Google's or any third party's copyright notices, trademarks, or other proprietary rights notices affixed to or contained within the Products.
Click to expand...
Click to collapse
I'm wondering what others think about this clause, and whether modifying an apk to allow functionality that would normally not be allowed by the app (for example, allowing additional game levels if a user has purchased them through some external means) violates the terms.
The Android development team is very important to have a good creative . The good creative can give the huge benefits to the development team. Especially for new Android app development team, Very important ! But pirated Android applications appear, one in which ideas fall through. How to make Android app piracy does not occur, is the developer of the first task.
Whether individuals or companies, from idea to development and subsequent market promotion.it is difficult to develop Android applications that need to spend a lot of manpower and resources,If it is, being decompiled, stealing the core source code, code embedded advertising and charging Android application. So all the efforts were in vain.
But now there's a new Android application source code encryption to appear ——ijiami（Love encryption）
This technology is available for Android application, encrypted protection: Do not need to change any source code, there is no SDK, and does not affect the user experience, and shields to prevent decompiling.
This not only protects the Android developer's interests, but also to protect the interests of the users.
爱加密——ijiami.cn
Hi.
I am Leo. I am a visual UX designer within a product team. I have an honest question, that I could not find being discussed anywhere on the web.
I am aware of the multiple asset formats that are required for Android development (hdpi, xhdpi, xxhdpi, and so on). Since I read that most new startups find it easier to develop apps for the mobile devices first in iOS format instead of Android, my question is this:
Is anyone to your knowledge working on an Android solution to this need for multiple image formats? I know this is required because so many different devices and screens are supported. But i have always wondered why no one is working on something in the code that would take the most high density image and 'res' it down via the code, to work on all devices. Therefore allowing a visual UX designer like myself, the ability to design at the highest resolution and provide only one image asset to my development team.
For iOs devices to sets of image assets are supplied to engineering. standard size and the @2x size. I believe Android adoption and apps would increase if the production time for these image assets could be minimized by business.
Thank you for any info, that helps me understand if this is not doable or any links to articles where people are discussing this very issue.
Sincerely,
Leo
First of Im not a dev just self taught myself alot "basic things" And im Probably going to us the wrong Jargon and what have you so be warned
I wanted to Get this Conversation going and see if there is a way to Port all the necessary things ( runtimes, frameworks and API's) From the Steam OS To android
Im looking to see if its possible and maybe getting some Dev's discussing It.
Im not expecting this to be developed just that the possibility if their is any be explored
Im also not talking about 100% compatibility (for either the games available or phones) as either of those options are ridiculous (the latter is more so IMO )
Download for the steamOS
The Aggrement may infact stop this from being developed
(ii) you may not modify the Steam Client, except that, in the case of the Linux version of the Steam Client, you may modify scripts and other documentary and graphical files, but not any files containing the term "bootstrap" in the file name, provided that you do not modify any icons, change any copyright or other notices, or alter this or any other license agreement that is included with the Steam Client, and provided further that any modifications you make are identified by you as modifications from the original Steam Client provided by Valve;
Click to expand...
Click to collapse
Some Q: Is SteamOS open source?
All of the base operating system components are open source. The Steam client itself is proprietary, as are some proprietary third party drivers.
Click to expand...
Click to collapse
Posibly Helpful Links
SteamOS FAQ
Valve's Github