December 29, 2013 By: eagleeyetom
The RemoteController class was introduced in the last version of Android, 4.4 KitKat. According to Google documentation, this class is used to control media playback, display and update media metadata and playback status, and is published by applications using the RemoteControlClient class. In plain English, this means that this class handles the behavior of media players.
It’s a new class used by Google, so it might be a bit problematic to understand how to use it. Luckily XDA Senior Member Dr.Alexander_Breen wrote a comprehensive guide, where he explains what should be done to successfully add this new function to your app. The guide is divided into five points to better understand the use of the new class. The final effect can be seen in a repository on Github, where Dr.Alexander_Breen pushed a sample of his code using this API.
You can find an answer to practically any question you may have in the original thread. This thread is oriented to experienced Android users / developers, so asking about adding this to PowerAmp is a bit pointless. Please keep that in mind, while you learn about the new RemoteController class. We wish you good luck in implementation this class into your personal projects.
December 28, 2013 By: eagleeyetom
Many of us would love to become famous programmers like XDA’s Senior Recognized Developers. But coding isn’t easy, and you need to know the basics and have a working knowledge of whatever language you choose before even getting started. And of course, writing a simple “Hello world!” app is not enough, as you will have to look deeper to create more complicated functions.
If you are looking a good place to begin, you should take a look at the guide written by XDA Senior Member Dark Wraith, who gathered some useful information together and wrote a handy guide with commands for many popular languages like C, C++, Java, Python, and BASH.
With the instructions provided in the thread and added acquired knowledge, you will be able to understand the structure of each language better and hopefully create your first application or modify your favorite ROM. With this guide, you will be also able to edit the overclocking settings and governors of kernels, which is a good practice for the C language.
Dreams sometimes come true, so if you want to start your developer career, make your way to the guide thread and hone your coding skills. We all want to wish you good luck!
If you are working with source code as a programmer writing an app or other project, you need a code revision control system. One of the most popular services used for this is git, which is widely used on sites like GitHub, Bitbucket, and Gitlab. Git is a powerful tool that works on every major operating system. It’s a very handy tool, but you need some skills to use it properly.
Some time ago, Conan Troutman wrote about my guide to GitHub. I didn’t include all the available commands, but with the help of XDA Senior Member jamieg71 and his comprehensive guide available in the XDA-University, Git will be no longer a black magic, but rather a great tool that can be used to control your projects. Jamie included most of the important commands available in Git, which can even resolve the most complicated situations. I don’t have to mention that most of basic commands are available too, so you can easily make your first steps in version control system with this guide.
Most ROM projects use Git, so proper usage of Git and Gerrit will allow for better code collaboration and contribution. More information and a big set of commands can be found in the original thread.
December 21, 2013 By: eagleeyetom
The build.prop is a system file that stores a lot of information needed by Android to work properly. Some entries can help to fix some issues or speed up the device, but mostly of these so called “tweaks” are nothing but placebo. The thread mentioned below will only prove the point that most of said tweaks are nothing more than myths that need to be busted.
Some tweaks work, but most of them simply do nothing. XDA Forum Member LaraCraft304 did a magnificent job and studied the source code in Android to see which tweaks are rubbish. The results are interesting. Almost 20, yes 20, of tweaks that can be found on XDA do nothing, as they have no entries in the source. Android, after reading the code, simply skips them as they are invalid. Interesting, don’t you think?
Of course they are entries that do something, and Laracraft304 presented them with documentation and code examples. This guide only proves that we should not blindly believe in everything and be aware of the placebo effect. The best way is to check the code and verify if a specific entry is worth looking into. Well, that’s the end of my short rant, and I hope that no kittens were seriously injured in the process and that you’re still awake.
If you are interested in seeing some results, make your way to the original thread and check for yourself. Do you believe in build.prop tweaks and use them? Have you fallen for some of the placebo effects before? Leave a comment below and share your opinion.
December 14, 2013 By: wildstang83
Android is a mobile device OS that the open-source community has come to know and love since its inception in 2007. The seemingly endless possibilities of what can be achieved with the OS are intriguing, and they have rekindled the spirits of developers worldwide. As mobile device owners, we often use our interest in Android to push our devices further and customize them to become truly our own.
As with any modifications or customization, tools are necessary. This has led to the creation of tools like Themer, an app that can be downloaded and used to easily select and apply custom themes directly on the device within a matter of seconds.
But where do tools like Themer come from? How are they built? Perhaps an even better question to ask is how is Android built? The answer to these questions is actually very simple: a build environment.
A build environment is a set of tools and directories that a developer has setup on his or her computer. This build environment allows the developer to download the Android source code, which can then be used to create a custom ROM, themes, apps, or anything else related to the OS. Some components of a build environment include a computer, the Java Development Kit (JDK), the Android SDK, the Android source, and of course, a little bit of time and patience.
Finally getting to the point, I want to bring your attention to a build environment that only a handful of developers use: OS X 10.9 Mavericks from Apple. With the right know how and proper setup, working on Android in an OS X build environment can be just as enjoyable as working in any other OS like Linux or Windows.
If you own a Mac, setting up your build environment has now been made simpler thanks to good folks like XDA Recognized Contributor jakew02, who wrote a very thorough guide on setting up a build environment, specifically in OS X Mavericks. While his guide won’t show you exactly how to build things like a custom ROM or kernels, it helps you make sure you and your Mac are better prepared to start your Android development journey.
Being a Mac owner, I’ve used the guide, and have found it to be very helpful. It is really nice coming across jewels like this on XDA. If you are a Mac user ready to start developing, head on over to jakew02’s guide thread to learn more.
December 13, 2013 By: eagleeyetom
Further hiding App Ops in Android 4.4.2, Google sparked many questions about the actual freedom in Android. Thanks to an Xposed Framework module by XDA Forum Member caspase, the functionality known from previous versions of Android was restored. However, Xposed on KitKat is incompatible with ART compiler, which was one of the major improvements of the Google’s operating system.
Fear not, if you thought that App Ops is not for you. Thanks to XDA Recognized Developer Calkulin and his smali assembler code knowledge, the much loved function can be implemented to Android 4.4.2 without breaking ART compiler.
The process of re-adding App Ops is not difficult. You need to have a decompiling tool or a kitchen that is able to decompile Settings.APK and a good text editor (preferably Notepad++ if you are on Windows). All you need to do is pull the APK from your device, decompile it, make the changes thoughtfully described by Calkulin, recompile it, and push the APK back. Of course, your device must be rooted, and ADB is preferable to manually copying the modified APK.
You can learn more about how to restore App Ops on your device by visiting the original thread.