Hello all,
I would like to propose a possible solution to the difficulty at times of finding different scripts for Android.
Basically what I am proposing is using a public repository of various open source scripts for Android that can be modified, improved upon, and maintained by the community.
I have already created a git repository here, as well as created and added a couple of scripts myself and plan to add others that I have found across the forums (With proper credit of course).
This could prove to be very useful for devs and users alike.
Please feel free to fork my repo and add any scripts you may have and even improve upon the ones already there.
Suggestions and constructive criticism are more than welcome.
Github Repository
That's only for Android scripts or scripts for desktops that are related with Android, like for example adb and rooting scripts?
EDIT: Just looked at the repo and my question is answered. I'm forking and adding some
Hi,
Sorry for the basic question here. I just want to compile and build an apk from an android open source project; but i don't know how to !!
I'm on ubuntu 13.10. I have downloaded the Android ADT bundle from developer android com /sdk/ index.html
I've run eclipse (from ADT bundle) and have imported a downloaded version of the open source project.
The open source project is Prey github com / prey / prey-android-client
The project is setup in eclipse but i see red flags and doesn't run (because it doesn't know how to run).
Can you guys point me to a guide or tell me how to compile & build an apk out of this.
Unfortunately the README file in the repository is useless (i.e. blank!)
Thanks.
shanehelms said:
Hi,
Sorry for the basic question here. I just want to compile and build an apk from an android open source project; but i don't know how to !!
I'm on ubuntu 13.10. I have downloaded the Android ADT bundle from developer android com /sdk/ index.html
I've run eclipse (from ADT bundle) and have imported a downloaded version of the open source project.
The open source project is Prey github com / prey / prey-android-client
The project is setup in eclipse but i see red flags and doesn't run (because it doesn't know how to run).
Can you guys point me to a guide or tell me how to compile & build an apk out of this.
Unfortunately the README file in the repository is useless (i.e. blank!)
Thanks.
Click to expand...
Click to collapse
I would say you should go though the getting started guides on d.android.com and things will become a little more clear
Hello!
I'm hoping to get custom kernel & rom development up and running quickly for the G5 community, and have created a git repository which provides a kernel source base to start with.
What I've done is taken the v10a release sources and modified them to work with build directories and multiple variants. (should they be unlocked or receive the CodeFire treatment at any time)
Here's where to start: https://github.com/jcadduono/nethunter_kernel_g5/tree/stock-6.0
If you'd like a somewhat updated kernel, the stock-6.0.y branch will be patched from Linux 3.18.y branch at kernel.org, see:
https://github.com/jcadduono/nethunter_kernel_g5/tree/stock-6.0.y
Different from the absolute stock defconfigs, I've made the following changes:
Module signature verification disabled
Unnecessary debugging flags separated into debug_defconfig (use EXTRA_DEFCONFIG=debug_defconfig to enable them)
Flags that were previous set to module (=m) have been set to =y (built-in) in case incompatibilities are unable to load stock modules
Each known variant & target is listed in build.sh comments. The default variant when building with ./build.sh is h850 with debugging disabled.
When using the Makefile, VARIANT_DEFCONFIG=variant_xxx_defconfig adds the additional settings per variant to the target defconfig. (by default stock_defconfig)
build.sh is set up to automatically build a dtb.img after creating the kernel Image.gz based on whichever variant you've built for.
You can use ./menuconfig.sh to modify the stock defconfig, or you can copy the stock_defconfig to another name such as my_defconfig and use TARGET=my ./menuconfig or TARGET=my ./build.sh
It's easier to just set the default target in build.sh/menuconfig.sh - each have their configuration options near the top of the files.
Be sure to edit the config variables in build.sh and menuconfig.sh before using. The VERSION file gets appended to the kernel version shown in `uname` when using build.sh.
The toolchain must be pointed to the correct location before it can build. Be sure to have libncurses5-dev and colordiff packages installed for menuconfig.sh.
For a toolchain, I recommend using the GCC Linaro aarch64 5.3 2016.02 release. You can use basically any aarch64 toolchain though.
Download here: https://releases.linaro.org/compone...o-5.3-2016.02-x86_64_aarch64-linux-gnu.tar.xz
You can start by forking my repository on GitHub and giving it your own name if you like. Extra interesting commits are available in the other branches that you should be able to cherry-pick without issues should you be interested in them.
Looking to test your kernel Image.gz + dtb.img?
Look no further than my LazyFlasher repository!
See here: https://github.com/jcadduono/lazyflasher/tree/kernel-flasher
Simply do:
Code:
git clone -b kernel-flasher https://github.com/jcadduono/lazyflasher.git kernel-flasher
cd kernel-flasher
cp /path/to/Image.gz /path/to/dtb.img ./
make
(simply place your kernel Image.gz (optional) and dtb.img (optional) in the root of the repository and type make!)
And you'll have your own dynamic kernel flashing zip for custom recoveries!
The kernel-flasher repository is capable of great things. You can create scripts in patch.d to do anything you like.
Add files to the ramdisk-patch folder and create a script that copies them into the $ramdisk folder and they will be rebuilt into the ramdisk!
By default, no-verity-opt-encrypt is there as an example.
Using setprop in patch.d scripts allows you to set props in default.prop with ease.
Add functions to patch.d-env to make them globally usable across patch.d scripts.
See other branches for more examples, like how to add f2fs lines to the fstab, or patch for system mode SuperSU.
LazyFlasher is the installer used in the Kali NetHunter project. You can also find more examples in the kali-nethunter GitHub!
Good luck, and happy kernel developing!
Thanks so much for posting this.
Code:
./obligatoryn00bstatement
Sorry for not being too knowledgeable here (yet?) and if this sort of comment doesn't belong.
I am a Computer Science major who really wants to learn some skills to hopefully give back to the community.
Is this an area that I could be of use or should I perhaps spend more time going through material on the XDA-U site?
toefurkey said:
Thanks so much for posting this.
Code:
./obligatoryn00bstatement
Sorry for not being too knowledgeable here (yet?) and if this sort of comment doesn't belong.
I am a Computer Science major who really wants to learn some skills to hopefully give back to the community.
Is this an area that I could be of use or should I perhaps spend more time going through material on the XDA-U site?
Click to expand...
Click to collapse
I'm a little tired and somewhat intoxicated here at 3:45 AM so this is going to be a bit of rambling and so on...
While it's certainly a good idea to study up on what interests you before digging into it, sometimes it really can be easier just to dive in to your hobby.
I'm a high school drop out, never made it through college. Everything I've learned is by taking the great work done by the open source community and reading their code and applying it to other projects. That's the great thing about open source and nonrestrictive licenses. Everything is there for you to figure out, make changes, borrow code, run into problems, and the best part - search for solutions that others have already provided in their struggle to do exactly what you're doing.
Have an idea for a great feature? You can probably find it already implemented in another kernel somewhere.
Find the work someone else has done and modify it to fit your needs, but don't forget to give them credit for their work that you've used!
If you're going to start writing your own code, be certain to keep it tidy and variables/functions with meaningful names and comments so that not only others can understand and learn from it, but that you can return to the same code later on and understand it. Confusing code is how bugs tend to show up and become almost impossible to squash.
What I'm trying to get across here is don't be afraid to not be original. Don't be afraid to use others work to accomplish what you want, so long as they receive some attribution. The quickest way to learn how things work is by understanding what's already there and available to you.
You'll notice that there's projects all over XDA with special features ported from one device to another. Isn't it great having the all the best features people have added to other devices on one really nice device that you have?
PS I've never been on the XDA-U site before, so I can't give an opinion there.
I forgot what I was on about so I'll end this here lol.
?jcadduono you're on fire man thank you for everything you've been doing so far with such little resources.
Sent from my LG-H820 using XDA-Developers mobile app
jcadduono, thanks for the info and wonderful words of wisdom!
I totally agree on what you're saying and my goal is to try diving into this as a hobby. The hardest part for me isn't so much the coding part, but just figuring out a starting point to get grounded and build upon and I feel like what you've provided here is perhaps the starting point I need. Now it's just up to me to push myself in my free time.
Hi, i am new to kernel developing, but i did some roms myself before, so no total linux noob.
I cloned your 6.0.y and want to start from there, but im a little bit lost. Do i need to follow the steps @ github, or is your branch kinda pre setup ?
Toolchain path is also set to the one you gave a link too.
Pinu'u said:
Hi, i am new to kernel developing, but i did some roms myself before, so no total linux noob.
I cloned your 6.0.y and want to start from there, but im a little bit lost. Do i need to follow the steps @ github, or is your branch kinda pre setup ?
Toolchain path is also set to the one you gave a link too.
Click to expand...
Click to collapse
Hopefully once the toolchain path is set you should only need to run ./build.sh to actually build the kernel and dtb.
You may be missing some items for menuconfig.sh, which should just be solved by apt-get install colordiff libncurses5-dev
If building inside a ROM tree, it should be fairly simple for developers to adjust their ROM configs to add more to the kernel make command line, such as VARIANT_DEFCONFIG.
No matter what i do, kernel builds, but no dtb.img will be created. Any ideas where to look / what to test ?
I have stock-6.0.y, and did the h850 one.
Hi, is the stock-6.0.y branch removed?
I didnt find it. and need the right defconfig
greetz
mericon
Raccoon is a Google Play desktop client for downloading apps. Use cases:
Access Play even if your device/ROM comes without GAPPS
Protect your privacy by using a dedicated account for downloading apps.
Keep local copies of large apps, so you don't have to download them again.
Rollback troublesome updates.
Features not found in other APK downloaders/mirrors:
Download free AND paid apps.
Download large apps with OBB expansion files.
Download older app versions (for downgrading)
Spoof arbitrary devices to get around compatibility restrictions.
Use proxies to get around region locks.
RACCOON WEBSITE
XDA:DevDB Information
Raccoon, Tool/Utility for all devices (see above for details)
Contributors
onyxbits
Source Code: https://github.com/onyxbits/raccoon
Version Information
Status: Stable
Current Stable Version: 4.0.1
Stable Release Date: 2016-06-15
Created 2016-06-15
Last Updated 2019-03-27
Seems promising !
Would definitely give it a try & report back soon.
On a related note: I'm also in the process of rewriting Dummydroid, a companion tool for spoofing arbitrary Android devices. Any artists around here willing to contribute an application icon (must be in SVG format and under a creative commons license)?
Used to work for me, lately it just hangs by signing in.
Loved it!
Newyork! said:
Used to work for me, lately it just hangs by signing in.
Loved it!
Click to expand...
Click to collapse
Can you check if there's an exception thrown on the console?
New version (4.0.1) is available!
Hey Everyone, just managed to port ColorOS OMOJI to non-oppo devices, and thought i should share it as tbh omoji are quite fun to mess with
Download:
Ported APK
Install:
Install like any other apk, but play protect will most likely ask you if you really want to install it as I had to resign the apk.
Screenshots from Galaxy S21:
SC 1
SC 2
Notes:
I've not allowed versions below 11 because I've not tested them. If someone with a Android 10 device or lower would like to test, contact me on Discord: Fiery#9119
Thanks to:
apktool for helping me decompile and rebuild
stack overflow for also helping me with that
oppo for OMOJI
also oppo for not putting a strong lock on who can use OMOJI
Can't download
File no detected