I have started looking at the sources of Android (the main source tree of the operating system not the Android project that opens up in Eclipse) and was able to successfully compile it for my N1. However, I was wondering if there is tutorial out there that tells provides an overview of the source tree. If someone was not involved in embedded development, how does one go about understanding the source tree?
Where it concerns the apps, the tree is pretty much straightforward. The rest is mostly understandable by names, but I don't know if there's any guide out there. I'd like to know too.
Oops.. sorry. I was not talking about application development. I have some experience with that. I am talking about the sources we checkout using git. I hardly have any experience with compiling code for embedded devices so I was looking into what each folder does. For instance, frameworks, libcore, vendors etc.
Big part of the sources in git repo are system apps - that's what I've meant.
Unfortunately, I don't have experience with system side of things.
vendors - collection of scripts with settings for each phone of each vendor (compilation settings, switches, etc).
i looked for the same thing when i first looked at the github tree, it was a bit overwhelming. no walk thru exists that i know of. i just learned to search each branch from the main page, i.e. the msm family for qualcom cpu phones, the samsung kernel, etc. wish it was a bit clearer.
Thanks! I am sure the community would be interested in such a documentation except that it will be terrible if I start writing it though I can make an initial attempt in doing so. I will see if xda has a wiki where I can put this stuff. But please do let me know if XDA provides us with such a wiki already.
EDIT: Never mind. I found the wiki here. I will try to fit it somewhere.
Related
A project for our Kernel devs maybe? i found this in the I9000 Forums and though i might keep it going over here in the Vibrant quadrant of XDA.
http://forum.xda-developers.com/showthread.php?t=812879
Most people don't yet know that many Android software leak all sorts of information to the internet with only scant user acknowledgement (basically what you accept when you install the app).
Due to this and the fact that there are already privacy information harvesting apps for Android on the marketplace - a team of security experts have created TaintDroid:
What is TaintDroid?
From the project's web page: "A realtime monitoring service called TaintDroid that precisely analyses how private information is obtained and released by applications "downloaded" to consumer phones."
From: http://appanalysis.org/index.html
How can I install TaintDroid?
As TaintDroid is currently compiled into the kernel, you cannot easily install it, but you have to cook your own kernel. Instructions (for Nexus 1) are available at the project web site: http://appanalysis.org/download.html
How does TaintDroid work?
Here's a video demonstrating how TaintDroid works once it is installed and configured:
http://appanalysis.org/demo/index.html
Why would you want to install this?
There can be many reasons for installint TaintDroid:
- You want to learn about privacy features and play with Android kernel
- As it is currently impossible to differentiate between innocent and sneaky Android apps based only on what access rights they request, you may want to dig in deeper
- You are worried about what apps are doing behind your back and you want to know which apps to uninstall
- You want to help create Android a more secure and privacy-protected platform, instead of the swiss cheese it currently is
What can you do?
As compiling kernels is mostly beyond the reach of mere mortals currently, consider cooking TaintDroid into your kernel, if you are cooking one yourself and offering it available for others to try and use.
Hopefully increased awareness and usage will bring this program eventually into other modders and perhaps even Google's attention and something more easily accessible is offered for the public at large.
BTW, I'm just a user, interested in getting TaintDroid on my own Galaxy S. I'm not affiliated with the research program, but I like what they are doing. This information is purely FYI.
Click to expand...
Click to collapse
Cool Idea. probably could have thought of a better name.
GrundleDroid or GoochDroid, perhaps?
Lol true but it would be a great idea to add into our kernels
Sent from my SGH-T959 using XDA App
junglizste said:
Cool Idea. probably could have thought of a better name.
GrundleDroid or GoochDroid, perhaps?
Click to expand...
Click to collapse
TaintDroid - it's just in-between ........
I don't know if this is the right place to ask but I think I'll post here instead of development. I want to get into making my own slightly tweaked kernels but I really know nothing about whets where in the repository (like what file I would look in for clocks or voltages). I was just wondering if someone could point me toward some documentation so I can at least have a but of an idea. Thanks!
Developing anything is pretty complicated without some codding skills so I would advise against trying to code your own kernel although if you want to I can't stop you but in your position I would have posted in android development section you may get faster results.
I have experience in coding in c++, html, some assembly, wrote a very basic bootloader that doesn't really do much for a pc. I'm just looking to make some minor changes. (clocks or voltages)
# include <iostream>
using namespaces std;
void main()
{
cout <<"Well in that case I guess you could but like I said you'll probably get more responses in the android development section then nexus one Q&A.\n\nBTW I'm no expert in c++ just wanted to do this as a little joke all I know are the basics ";
cin.get();
}
NOTE: I know code is not supported in most forums so if a mod wants to delete this feel free it was just a joke so.
Very nice but unfortunately wouldn't compile in my compiler thanks to microsoft requiring include stdfax or whatever it is that I have to add up there with precompiled headers.... A pain but I never really learned gcc and its rules
Will post in dev section thanks for the suggestion!
Oh well I just noticed something and I'm going to guess that's why it didn't compile for you I made a typo up there it's not "namespaces" it's "namespace".
meltbox360 said:
I have experience in coding in c++, html, some assembly, wrote a very basic bootloader that doesn't really do much for a pc. I'm just looking to make some minor changes. (clocks or voltages)
Click to expand...
Click to collapse
All you have to do is browse some of the repositories here in the dev section. Click the GitHub link to pershoot or intersects repository. Then go to the kernel project/source and click "commits" at the top. Look thru each commit to get an idea of what's going and being changed in the kernel. The good stuff will be from months ago so you'll have to keep going back far thru the commits to find the significant changes.
Then setup your own build environment. Cyanogen wiki has a step by step tutorial guide that's straight forward and rather easy to get going.
When done that, just practice making some tiny code changes to the kernel, something that interests you, and try to compile it. You'll prob get an error so tweak it till it compiles with no error, then flash it to your device and see if it works.
It's fun to do and you can get setup pretty quickly with all the info available to us.
NNow that Web OS is open source, do you think we could get it to run on the nook?
WEB OS goes open-source says webos
http://developer.palm.com/blog/2011/12/open-source/
sdk
https://developer.palm.com/content/resources/develop/sdk_pdk_download.html
I would certainly think it's possible. WebOS is Linux-based, so you could probably reuse the existing Android Linux kernel... you'd just have to get all the userland stuff working on it.
That said, I don't know if anyone's been actively looking at doing WebOS on the NC (or WebOS on any non-HP devices, for that matter).
There was an effort porting pre-open-source WebOS to the Hero (referred to here: http://forum.xda-developers.com/showthread.php?t=948473) but it got shut down at the time.
androidifyme said:
NNow that Web OS is open source, do you think we could get it to run on the nook?
Click to expand...
Click to collapse
A question like this from someone called "androidifyme"?
The WebOS source hasn't actually been released yet, they have only announced a plan to do so in the near future with no specific dates given. Also, they won't be releasing the entire OS at that time based on the line in their press statement that they "also will contribute ENYO, the application framework for webOS, to the community in the near future along with a plan for the remaining components of the user space."
---------- Post added at 09:24 AM ---------- Previous post was at 09:18 AM ----------
slab said:
I would certainly think it's possible. WebOS is Linux-based, so you could probably reuse the existing Android Linux kernel... you'd just have to get all the userland stuff working on it.
Click to expand...
Click to collapse
the Android kernel is pretty heavily modified from the stock Linux kernel to work with the Android system, and for all we know the WebOS Linux kernel could be the same way. I doubt it would work just like that, however having working kernel sources from Android would certainly make it easier to get device-specific drivers working in the WebOS Linux kernel. And like I said in my other post, unfortuantely the userland stuff does not appear to be a part of their initial open source plan anyway
boomn said:
The WebOS source hasn't actually been released yet, they have only announced a plan to do so in the near future with no specific dates given. Also, they won't be releasing the entire OS at that time based on the line in their press statement that they "also will contribute ENYO, the application framework for webOS, to the community in the near future along with a plan for the remaining components of the user space."
---------- Post added at 09:24 AM ---------- Previous post was at 09:18 AM ----------
the Android kernel is pretty heavily modified from the stock Linux kernel to work with the Android system, and for all we know the WebOS Linux kernel could be the same way. I doubt it would work just like that, however having working kernel sources from Android would certainly make it easier to get device-specific drivers working in the WebOS Linux kernel. And like I said in my other post, unfortuantely the userland stuff does not appear to be a part of their initial open source plan anyway
Click to expand...
Click to collapse
You are Ignorant, I just built my webos sdk, and could compile a webos platform I am just curious and will be looking into what needs to be done. name means nothing, I like the idea of several options and learning at this point because one linux to another doesnt really matter, at some point the nook, should have its own distro like its calling itself a "nookbuntu", so why not. and it would be nice to be able to utilize other carrier or os services that dont work on android vs webos. to stay connected
boomn said:
the Android kernel is pretty heavily modified from the stock Linux kernel to work with the Android system, and for all we know the WebOS Linux kernel could be the same way. I doubt it would work just like that, however having working kernel sources from Android would certainly make it easier to get device-specific drivers working in the WebOS Linux kernel.
Click to expand...
Click to collapse
Yeah, I wouldn't expect it to be drop-and-go, but I also wouldn't expect the kernel to be the biggest stumbling block.
slab said:
Yeah, I wouldn't expect it to be drop-and-go, but I also wouldn't expect the kernel to be the biggest stumbling block.
Click to expand...
Click to collapse
I agree *10 chars
---------- Post added at 09:59 PM ---------- Previous post was at 09:56 PM ----------
androidifyme said:
You are Ignorant, I just built my webos sdk, and could compile a webos platform I am just curious and will be looking into what needs to be done.
Click to expand...
Click to collapse
Sorry, but I have to repeat: WebOS is not open-sourced yet.
An SDK is just a set of tools to help developers build and test WebOS apps on their pc, and one of those tools is a pre-compiled image of WebOS for use in an emulator. It won't allow you to build WebOS itself, only apps that work in WebOS.
As required per the GPL, the source has always been available for their versions of the Linux kernel and various open-source libraries and tools they use (link here). The rest of the OS, including a lot of the system programs and libraries, the user interface, the libraries needed to actually run WebOS apps, etc has not been open-sourced yet. They announced the plan only a couple weeks ago, and they have a lot of work ahead of them before they can start releasing code for parts of WebOS. For example, they will have to strip out and/or replace any code or libraries they have bought licences for from other companies. Cleaning up "colorful" comments in the code is pretty important to many companies too
Again I understand your attemt to be lame, please shut up, and leave this thread as you are ignorant.
http://developer.palm.com/blog/2011/12/open-source/
https://developer.palm.com/content/resources/develop/sdk_pdk_download.html
androidifyme said:
Again I understand your attemt to be lame, please shut up, and leave this thread as you are ignorant.
http://developer.palm.com/blog/2011/12/open-source/
https://developer.palm.com/content/resources/develop/sdk_pdk_download.html
Click to expand...
Click to collapse
Thanks for the continuing and escalating insults while I try to explain this all.
I've read all of those links as those were some of my sources for my previous posts. Your first link is to the announcement that they have a plan to release the source ("HP will make...", not "HP has now released..." or anything similar) to parts of the OS ("underlying code of webOS") in the near future. Further down you find where they make it clearer that their initial release won't be the complete source to WebOS ("HP also will contribute ENYO, the application framework for webOS, to the community in the near future along with a plan for the remaining components of the user space.").
As for the SDK, I already covered that. From that page: "HP webOS 3.0.4 SDK contains the libraries necessary to do both JavaScript development and C/C++ development". It's a set of development tools for app programmers. Wikipedia has a good summary article about SDKs here. HP/Palm been releasing updated versions of the SDK since WebOS first hit the market on Palm phones, otherwise 3rd party developers would not have ever been able to properly make apps that can run in WebOS, and the SDKs have never included the full WebOS source. Please excuse my silly analogy, but if WebOS were a house then the SDK might be a woodshop set up for building furniture to put in that house.
If you don't trust me then check wikipedia's current page about the WebOS open source plan that says: "On December 9, 2011, HP announced its plans to release WebOS source code under an open-source license at some time in the near future." Or google for "webos source code released" and see if you find anything besides the SDK, the GNU tools I mentioned earlier or a whole lot of news articles about the announced plan to eventually open-source their OS. Or check the WebOS Dev forum here on XDA, including comments like this one. When the base code is finally released there will be a lot more talk about it on all of those places.
Yup you are officialy 10 and stupid, an sdk by definition is open source, htc sense is not open source but android is, this is what hp had done with webos, we will be able to create full distrobution of webos and configure it for a device and use the tools in the sdk to compile apps for that device. You might be able to read but you obviously have no coding skills. That all being said, just leave this thread once and for all we dont need you and your annoying as hell. but you seem to be a decent googler just hope one day you can get paid for it. until then keep googleing maybe youll learn something.
Oh and if you do contact them, and register they will send you the whole package to begin developing, thanks for letting me prove you wrong I have contacted them to receive such package. The reason for such measures is to keep fools like you from even trying to play with their source
Wow. I can see the fruitlessness of trying to add further proof. You'll have to figure out reality on your own then. Please do me the favor of revisiting this thread once you've received all the HP files and had a chance to try building WebOS
I couldn't be 10 because it was about 10 years ago that I started using Linux. Got a minor in Computer Science since then too
boomn said:
Thanks for the continuing and escalating insults while I try to explain this all.
I've read all of those links as those were some of my sources for my previous posts. Your first link is to the announcement that they have a plan to release the source ("HP will make...", not "HP has now released..." or anything similar) to parts of the OS ("underlying code of webOS") in the near future. Further down you find where they make it clearer that their initial release won't be the complete source to WebOS ("HP also will contribute ENYO, the application framework for webOS, to the community in the near future along with a plan for the remaining components of the user space.").
As for the SDK, I already covered that. From that page: "HP webOS 3.0.4 SDK contains the libraries necessary to do both JavaScript development and C/C++ development". It's a set of development tools for app programmers. Wikipedia has a good summary article about SDKs here. HP/Palm been releasing updated versions of the SDK since WebOS first hit the market on Palm phones, otherwise 3rd party developers would not have ever been able to properly make apps that can run in WebOS, and the SDKs have never included the full WebOS source. Please excuse my silly analogy, but if WebOS were a house then the SDK might be a woodshop set up for building furniture to put in that house.
If you don't trust me then check wikipedia's current page about the WebOS open source plan that says: "On December 9, 2011, HP announced its plans to release WebOS source code under an open-source license at some time in the near future." Or google for "webos source code released" and see if you find anything besides the SDK, the GNU tools I mentioned earlier or a whole lot of news articles about the announced plan to eventually open-source their OS. Or check the WebOS Dev forum here on XDA, including comments like this one. When the base code is finally released there will be a lot more talk about it on all of those places.
Click to expand...
Click to collapse
Why are(/were) you even trying to explain something to an A hole like him?
Sent from my MB502 using XDA App
Though I do appreciate your comments. They further cleared the picture in my mind
Sent from my MB502 using XDA App
therkr said:
Why are(/were) you even trying to explain something to an A hole like him?
Sent from my MB502 using XDA App
Click to expand...
Click to collapse
I should have asked myself that earlier
Wow guys.... Take this kind of flaming elsewhere.. Its not welcome at xda..
Pointless thread closed.
So I look through the built in repo and I install a lot of things on my old phone to play with. However on the primary I only use FOSS. If a module doesn't have a git page then I don't install it.
I was thinking it would be neat if someone maintained a separate F-Droid repo specifically for xposed modules which are open source. Since xposed itself is open source you could have that on there as well.
It'd be nicer if there was a filter option in the program itself but I'm sure the devs are busy and the above would just be easier.
Maybe it is possible to add "Open source modules" in Sort mode (in Xposed Installer -> Download). It will simply check if Source link for module is not empty.
Who can take this idea and contribute this feature to Xposed?
Waking up this thread. I would also really like to have a structured list of modules which are open source for security reasons. Is this available anywhere yet?
E--Man said:
Waking up this thread. I would also really like to have a structured list of modules which are open source for security reasons. Is this available anywhere yet?
Click to expand...
Click to collapse
Maybe we can get "repo db" and look for source code field. But "in app implementation" is prefered. @rovo89
pyler said:
Maybe we can get "repo db" and look for source code field. But "in app implementation" is prefered. @rovo89
Click to expand...
Click to collapse
Where could we obtain the DB with those fields? I would never install any closed-source modules on my devices. Doing so is absolutely ludicrous in my opinion.
Also, is there a list of verified and trusted (by @rovo89 or someone alike) Xposed modules anywhere?
This is a very important topic...
Thanks,
E.
See https://github.com/rovo89/XposedInstaller/issues/249
The information about the source code URL is available in the repository XML file already and could easily be read be the installer. The issue is up for grabbing. I would appreciate a quick outline if the intended implementation though, so I can intervent regarding architectural decisions before someone writes a lot of code.
I can't give any "trust" recommendations for any but my own modules. It would mean that I would have to analyse the complete source code, verify that the APK actually matches that source code and repeat these steps for every new versions.
Well, if module is open source, anybody can check code so I think there is almost zero chance for malwares or so...
Closed sourced and obfuscated modules are the worst ones. Avoid them. They can do basically everything in background and user knows nothing.
So any skilled dev who is able to create new filter in Xposed Installer for open source modules here? It could be good addition.
pyler said:
Well, if module is open source, anybody can check code so I think there is almost zero chance for malwares or so...
Closed sourced and obfuscated modules are the worst ones. Avoid them. They can do basically everything in background and user knows nothing.
So any skilled dev who is able to create new filter in Xposed Installer for open source modules here? It could be good addition.
Click to expand...
Click to collapse
Really?..
Anybody can check sources, but who will?..
And can you trust their results?..
FOSS can be riddled with exploits like Heartbleed for years, and no one will notice anything. There are even competitions on hiding malicious code inside innocent one...
Only a small number of experienced and skilled developers will be able to find such malware, and believe me - 99% of them don't waste their time on reading, understanding and checking for exploits the sources of all software they use...
@rovo89, thanks for responding to this thread.
I am just wondering if anyone has any updates on the development of an Open Source repository.
Also, I feel that it would also be helpful if we had some sort of a "Developer Trust Rating" as well as a "Code Reviewer" status to ensure that the code of a particular module (or even revision if someone volunteers to take it that far) is both safe and/or that the code has been inspected.
Without this, installing modules on devices means we could be installing software that can be as malicious as it can get.
Lastly, where can I download the XML file that lists XPosed modules along with the "source code URL", and how can I validate that the source code in the URL matches that of the XPosed module itself?
Thanks.
E--Man said:
Also, I feel that it would also be helpful if we had some sort of a "Developer Trust Rating" as well as a "Code Reviewer" status to ensure that the code of a particular module (or even revision if someone volunteers to take it that far) is both safe and/or that the code has been inspected.
Click to expand...
Click to collapse
That's a nice vision, but I doubt that you will find enough people to actually do this who you trust and who would be willing to take the responsibility.
E--Man said:
Lastly, where can I download the XML file that lists XPosed modules along with the "source code URL", and how can I validate that the source code in the URL matches that of the XPosed module itself.
Click to expand...
Click to collapse
Check the source code of the installer for the URL, I don't remember it. But there is no way you can check an APK and find out whether it's built from a certain source. That would only be possible if the developer gave the source code to a trusted party, who would compile it and sign it with their keys. If you trust that third party AND inspect the source code, then you can be sure that it's not malicous. That's F-Droid's model, as far as I know.
YaDr said:
Really?..
Anybody can check sources, but who will?..
And can you trust their results?..
FOSS can be riddled with exploits like Heartbleed for years, and no one will notice anything. There are even competitions on hiding malicious code inside innocent one...
Only a small number of experienced and skilled developers will be able to find such malware, and believe me - 99% of them don't waste their time on reading, understanding and checking for exploits the sources of all software they use...
Click to expand...
Click to collapse
Hello there my Russian friend. I will respectfully disagree with you on this point and I will explain why. Right here on XDA, we have many highly-skilled developers who are the authors of countless lines of code translating into ROMs, modules, enhancements, etc. Much (if not all) of these projects are free to distribute and created as a contribution to the community. In other words, to ask "who will check sources" is the same thing as asking "who will create custom ROMs for people?" or "who will create invaluable/indispensable modules such as XPosed?" or even the general question of "why would someone do this for free?".
It is evident that all of these exist already and that people do indeed contribute, so coupled with the fact that the XDA community is over 5 million members in size, I think there will be developers who may be interested.
The only reason I can see someone not supporting this is if they have an interest not to do so, such as being the author of a closed-source (or open-source) malicious module.
"FOSS can be riddled with exploits like Heartbleed for years, and no one will notice anything"
Yeah but if it was closed source there is a chance it would have never been found.
Also saying that "no one would bother to check the code" is a horrible argument. At least give people the option to inspect it if they want to.
Bump, has anyone taken this to the next step? I am still interested!
Please use the QUOTE feature when replying to me to get my attention. Thanks!
Bump, has anyone taken this to the next step? I am still interested! <br />
<br />
Please use the QUOTE feature when replying to me to get my attention. Thanks!<br/>
Please use the QUOTE feature when replying to me to get my attention. Thanks!
I think more filters in general would be a good thing. There are a lot of Asian based apps that I have no interest in, nor do I play Pokemon/Ingress.
Categories for what country you're in or if an app is for gaming/banking/etc... would be nice. Maybe have the API levels it will work with too, and then just not show anything outside of that range.
I suppose someone could just make an F-Droid repo specifically for xposed/magisk apps too, though I would prefer it if it were officially maintained/sanctioned.
Swift V/B]
Formerly unlocked, a simple module, that unlocks your device from OEM restrictions.
HOW?
Unlocked removes OEM restrictions through different features.
FEATURES:
GPU TWEAKS:
UPLIFTS YOUR GPU BY SETTING UNIQUE AND LEGIT BUILD PROP TWEAKS THAT ACTUALLY WORKS. (based from .cpp files from google. and cs.android.com)
ART OPTIMIZATION:
OPTIMIZES YOUR RUNTIME THROUGH DALVIK OPTIMIZATION, WHERE ANDROID RELIES MOST OF THE TIME.
CGROUPS OPTIMIZATIONS:
UNLOCKED PROPERLY SETS WHAT IS MOST NEEDED FOR A SMOOTHER EXPERIENCE.
TASKSET AND I/O OPTIMIZATIONS:
THIS TELLS ANDROID WHICH SERVICES SHOULD BE PRIORITIZED
HOW TO KNOW IF ITS WORKING?You can check logs @/android folder
Swift V1 Initial Release!
- this is unlocked but no adjshield or binaries, uses pure android shell optimizations (that actually works).
- buildprop tweaks (filtered from git commits, cs.android.com)
- task process, cpu, priorities optimization.
-based from fix for chatheads lag on arrow os (gingko) and aims to fix evo x (pine tested on havoc, pep).
enjoy. Also pls try lazy tweaks if you have time
link:https://forum.xda-developers.com/apps/magisk/module-lazy-tweaks-t4163249
telegram for support and inquiries
https://t.me/lazytweak
Release Channel
Lazy Tweaks Releases
https://t.me/lazytweaks
downloads:
see attachment
CREDITS
@yc9559 a.k.a matt yang(project was based from qti )
source code: https://github.com/yc9559/qti-mem-opt
xda
My carrier prob doesn't wanna mess up my phone. Thank you. I'll stick with ktweaks
@lAlKenDi I noticed that you're using the GNU General Public Licence for this project and lazy tweaks. But you're also including binaries and apks that you do not provide the source for. Those two situations do not go together...
If you want to use GPL you'll also need to provide the full sources. Otherwise, use a different license that doesn't have this as a prerequisite...
(Note that I'm not here as a forum moderator. This is not my moderation area... I'm just a regular user that noticed a discrepancy.)
Didgeridoohan said:
@lAlKenDi I noticed that you're using the GNU General Public Licence for this project and lazy tweaks. But you're also including binaries and apks that you do not provide the source for. Those two situations do not go together...
If you want to use GPL you'll also need to provide the full sources. Otherwise, use a different license that doesn't have this as a prerequisite...
(Note that I'm not here as a forum moderator. This is not my moderation area... I'm just a regular user that noticed a discrepancy.)
Click to expand...
Click to collapse
oh crap, i forgot about it. i will provide the full sources. thank you for reminding sir.
Updated links and sources will be adding github soon.. if you have any issues just private message or contact me at telegram
XDA is not a funnel for people wanting to offsite people to another medium (and ive heard all the excuses, and dont buy any of them)
Im getting rather tired of this stuff
Telegram should be banned as a dirty word on here...id close any thread where the default reponse was "visit us on Telegram for x"
Over it
Telegram links removed because we dont want to cause issues nor "offsite" people and to keep things civil.
V2 is up!
Unlocked will stay dormant after a while but stay tuned!
will give a try on this, let see if it makes android one smoother on Mi A2 Lite
@lAlKenDi Followup on this: https://forum.xda-developers.com/showpost.php?p=83757753&postcount=3
I see you added a link to QTI-mem-opt's sources. Awesome. Except the two binaries you're using from there (adjshield and fscache-ctrl) doesn't actually have any sources there either... Which means that @yc9559 is in violation of the GPLv3 licence as well. Bummer...
If you don't have the sources, you can't just slap GPL on there and call it a day.
zafuro said:
can xda users stop being so salty about their ****ty outdated platform dying
Click to expand...
Click to collapse
Perhaps you should rethink being a member, and hateposting
Didgeridoohan said:
@lAlKenDi Followup on this: https://forum.xda-developers.com/showpost.php?p=83757753&postcount=3
I see you added a link to QTI-mem-opt's sources. Awesome. Except the two binaries you're using from there (adjshield and fscache-ctrl) doesn't actually have any sources there either... Which means that @yc9559 is in violation of the GPLv3 licence as well. Bummer...
If you don't have the sources, you can't just slap GPL on there and call it a day.
Click to expand...
Click to collapse
hello sir good day! Looking into the issue, we decided to remake unlocked without the binaries from yc9559. Again we would like to make an apology for this matter. As lazy tweaks promises we always wanted to transparent, open source, no lies etc. thank you for pointing it out. we appreciate it.
Update
Update is Up!
we removed adjshield and fscache but we bring a different and simple pure android optimization. Enjoy!
lAlKenDi said:
Update
Update is Up!
we removed adjshield and fscache but we bring a different and simple pure android optimization. Enjoy!
Click to expand...
Click to collapse
Is this still being updated?