POSTS TAGGED: Script
Posted October 21, 2014 at 10:30 pm by GermainZ
Ever needed to check the I/O usage of apps? If so, you probably tried searching for an iotop port, a Python script for Linux–only to find none and either write one in a hurry or manually check /proc/ yourself.
Luckily for you, XDA Forum Moderator and Recognized Developer laufersteppenwolf has written a shell script to replicate the original features of iotop. It will allow you to examine I/O loads/usage for every process, see the total amount of read and written bytes or even the current read/write speeds.
Before you use the script, though, you’ll have to make sure you have the following:
- A rooted device.
- A kernel with I/O accounting enabled. This usually isn’t the case by default, but you can
Posted October 15, 2014 at 06:00 pm by Tomek Kondrat
As is the case with every Unix-based operating system, Android uses symlinks. A symbolic link is a special type of file that contains a reference to another file or directory in the form of an absolute or relative path, which affects pathname resolution. In Android, they are mostly used in the /bin and /xbin folders, where all the executing binaries are kept.
If you want to make your own symlinks or get to know which files are a part of Toolbox or Busybox, you can find out manually by entering some commands in Terminal. You can also use a script written by XDA Senior Member LENAROX. Chklnk is nothing but BASH script that can identify the symlinks easily with just one command. After pushing to selected system folder and . . . READ ON »
Posted July 25, 2014 at 04:00 pm by Tomek Kondrat
When it comes to device testing, there are two types of people on XDA. The first group blindly believes that one additional benchmark point makes a particular ROM or kernel the best, and they install it immediately. The other group takes benchmark results with a grain of salt, and take them into consideration with other performance metrics. Antutu or Quadrant are two of the most popular benchmark applications available for Android. However, there are many, many more options available for those looking to test specific aspects of their devices.
Posted May 24, 2014 at 02:30 pm by Tomek Kondrat
RAM management works a bit differently on Android than it does in Windows. For example, more RAM doesn’t mean wasted memory in Android, but rather that applications are cached so that they can be accessed more quickly at a later time. There are plenty of interesting discussions on the topic, but that’s not the point of this article.
If you’ve ever tried to check the free RAM on your Android device, you probably used the free command in Terminal Emulator. This works the same way as it does in Linux, and it shows you both free and used memory. If you are using a swapfile, it’s shown as well. But if you want to learn more about your device’s RAM usage, you need additional . . . READ ON »
Posted May 15, 2014 at 11:30 pm by Tomek Kondrat
To build your very own source-built custom ROM, you need Linux or OS X running natively or through a virtual machine . But even most fully fledged distros can’t build Android without installing some dependencies. The only exception might be BBQLinux by XDA Senior Recognized Developer codeworkx.
A few weeks ago, we talked about scripts to build a ROM or kernel easily. Since then, this project has expanded. If you run Ubuntu, Arch, or a spin-off like Xubuntu, Lubuntu, or Manjaro, you are probably looking for an easy way to set up this build environment without googling which packages should be installed. Luckily, XDA Forum Moderator laufersteppenwolf wrote a simple BASH . . . READ ON »
Posted May 11, 2014 at 08:30 am by Tomek Kondrat
With a much certainty, we can say that Aroma is one of the most widely used projects here on XDA. We have talked about it countless times in the past. This system was created by XDA Recognized Developer amarullz, and it has since dramatically changed how we install ROMs, kernels, and flashable modifications by allowing us to select which applications, libraries, and boot animations we would like to have installed. It’s almost a given that everyone reading this has already seen a thread with the word AROMA in the title.
Posted April 24, 2014 at 09:30 pm by Tomek Kondrat
Creating a kernel, ROM, or any other development project requires knowledge and tools. While this knowledge can be obtained from books and other resources, tools must be created from scratch. Well, not all of them, as here on XDA there are plenty of interesting projects that are shared with the community.
When you are building a ROM, you need to execute a few commands to get the build process started. Manually entering lines takes time, and there is a great chance of making a typo and having to repeat the process. XDA Forum Moderator and Recognized Developer laufersteppenwolf decided to share his solution by presenting a set of scripts that will allow you to speed up the preparation proc. . . READ ON »
Posted April 18, 2014 at 06:30 pm by Tomek Kondrat
Some of you may think that writing code is the hardest part of development. It’s not, as the real fun starts when you have to debug an application or function. That’s why Android Debug Bridge is so important, and you can find images like this in many threads. And obviously, digging through thousands of logcat lines is every developer’s “favorite” activity.
Logcat likes to bombard users with more or less relevant information regarding various issues. To free yourself from mpdecision, thermal-engine and sensors.msm8960.so warnings, you should try out a script written by XDA Recognized Developer and Contributor broodplank1337. Lib Cleaner removes the specific lines of cod. . . READ ON »
Posted February 18, 2014 at 07:00 am by Tomek Kondrat
Ever heard about Docker? If you have, you surely know what a great piece of development work it is. If you haven’t, I’m going to explain what exactly Docker is and why it should be considered in the Android development world. Quoting the Docker website:
. . . READ ON »
Docker is an open-source engine that automates the deployment of any application as a lightweight, portable, self-sufficient container that will run virtually anywhere.
Docker containers can encapsulate any payload, and will run consistently on and between virtually any server. The same container that a developer builds and tests on a laptop will run at scale, in production*, on VMs, bare-metal servers, OpenStack clusters, public instances