Being an "open source Home Replacement app", I spent a couple of hours yesterday trying to find a public repository where I could get ADWLauncher's code.
Looking at its google projects page, it seems that the project is quite active, yet the latest source I could find is under the CyanogenMod github, with ongoing translations but with sources last updated 3 months ago... In AnderWeb's github things are even worse with last commit over a year ago...
Does anyone know of a public repository where i could get the project's latest source code?
Thanks!
Found it !
Hi florpor,
you can find ADW Launcher repository on GitHub.
As I'm a new user, I cannot post you the URL, so here is the info to find it :
on github, look at the "AnderWeb" user projects. It is the one named "android_packages_apps_Launcher".
However, the project seems to be stalled.
Have a nice chekout
I don't think there is any source for the new version. There were many contributors on that project, but it looks like they have all agreed to go proprietary all of a sudden. They haven't announced anything on their project page, so who knows what's going on.
Related
Does anyone know where I can find the webos 3.0 source code. I would like to find the browser source code in particular.
Proprietary
HP's webOS is a proprietary software, so it's not opened source... though that could change. But I don't think HP would do that. Sorry, there isn't any source code available to the pubic at this time.
I thought Preware had functional kernel source? (meaning you could build a kernel and have all of the drivers "work"...)
Here is something to look at.
http://www.webos-internals.org/wiki/Main_Page
thanks
quickmirror said:
HP's webOS is a proprietary software, so it's not opened source... though that could change. But I don't think HP would do that. Sorry, there isn't any source code available to the pubic at this time.
Click to expand...
Click to collapse
Thank I was just wonder of someone had hacked the OS
Hacked
In what way do you mean hacked? The interface is proprietary but the sound services etc.. use opensource applications like PulseAudio.
That source can be found here:
opensource.palm.com/packages.html
http://opensource.palm.com/packages.html heres the source for some of it at least
My mistake
Sorry about that, Palm owning the OS slipped my mind. Thank you for the link.
On a positive note, the kernel source is there... which should have the driver source that could be migrated into the android kernel... Kernel & patches
if you download the SDK from HP it has some sample code and it has the browser as one of the examples
Browser source (webkit that is) is on the palm site
You can download one of the webOS Doctors and extract it using 7zip. Easy access to a lot of the code, since it's mostly javascript/css.
http://www.webos-internals.org/wiki/Webos_Doctor_Versions
The Browser app is in /usr/palm/applications/com.palm.app.browser/
The sourcecode will be released soon per the news about HP's decision to release it. ENYO 's source code will also be released
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
Hi all,
Is there a specific way to hunt down commits for feature sets in the source of ROMs on github? As a simple example, let's say someone was searching my ROM for how to enable AppOps in AOSP. They would eventually find this commit:
https://github.com/nowsci/platform_...mmit/a766afc88ebed960c2027d3d1539ff9a38be4115
However, many feature additions require changes across many repositories for Android. Let's say I want to find the Expanded Volume Control code for Cyanogenmod. The only way I can think to do this is to clone every single Cyanogenmod repository, print out the git log, and comb through for every mention of "volume" until I find the right commits.
How do other ROM developers shortcut this?
I ask for my own education, and because I think a central repository of "features" that links all the commits and provides the merge commands for AOSP might be a handy thing to start creating in the community (unless there is already a better way).
Thanks!
Gerrit is kinda a pain when it comes to searching but I finally played with Gerrit search syntax and came up with a couple of searches
find everything for cm13 merged in the past 30 days
https://review.cyanogenmod.org/#/q/...-project:^.*device.*+-translation+-age:30days
same but for cm14.x
https://review.cyanogenmod.org/#/q/...-project:^.*device.*+-translation+-age:30days
if you have a login for CyanogenMod gerrit you can save these as menu items for quick clicking
when logged into the gerrit instance go to your account's preferences and save menu items for
cm 13.0
#/q/status:merged+branch:cm-13.0+-project:^.*kernel.*+-project:^.*device.*+-translation+-age:30days
for cm14.x
#/q/status:merged+-branch:cm-13.0+-project:^.*kernel.*+-project:^.*device.*+-translation+-age:30days
now let's walk through the search flags used
this could be entered in the search box on review.cyanogenmod.org
status:merged -branch:cm-13.0 -project:^.*kernel.* -project:^.*device.* -translation -age:30days
let's look at our CM-14.x example since it makes the cm13.0 one make sense as well
status:merged to look for a merged commits
everything else had to be exclusions to get to what we want to see. the age: flag only looks for stuff before a certain date and a minus sign excludes so we'd have to use -age:#days/weeks,etc to show stuff in the past # timeframe
-age:30days
Since we're looking at the past 30 days, most commits (as of this writing) are on the Nougat/cm-14.0 branches and a little stuff on the cm-13.0 branch. So with our 30 day window, any merges NOT cm-13.0 branch are probably gonna be cm-14.x branches. If you can see, when cm-15 comes all you need to do is play with this part.
-branch:cm-13.0
I don't care about everyone's devices. I just want to see plain old CyanogenMod commits so I'll exclude the device and kernel projects. I used regular expressions to exclude any projects with either kernel or device somewhere in the project name. the carat symbol ^ enables regular expressions in Gerrit Search and the rest is regex syntax per Gerrit's documentation.
-project:^.*kernel.*
-project:^.*device.*
I also don't want to see any translation updates so I'll just put in a general exclusion on those
-translation.
I just wanted to write something up for myself. Might as well pass it along.
With these bits and pieces I could probably filter it down a little more but this is the guts of what I need to do so.
edit- refined it a little more
status:merged -branch:cm-13.0 -project:^.*kernel.* -project:^.*device.* -project:^.*hardware.* -project:^.*hudson.* -translation -age:30days
owoify
owoify
This is an Xposed module that turns your system furry. It makes almost every TextView use OwOified speak.
You don't want to use this on your daily driver. Seriously.
Examples
Screenshots
Inspiration
There's been a jailbreak tweak for over a year which does something similar to this, popularised by this tweet by Ninji.
Since then, an npm package sprung up, which was then used to create BBC Bweaking, and more recently my very own Schlatt in OwO
That's how this hellish beast came about. You're welcome.
Download
Downloads can be found on the GitHub releases page, or attached to this post.
Sources
The list of prefixes, suffixes and replacements came from zuzak's owo npm package, under the MIT licence; which itself sourced the list from the jailbreak tweak
Some of the Xposed implementation code came from the classic Hodor module by GermainZ
Source code
...is here on GitHub
What have you done?
This is funny?
Gweat wowk