OnePlus has been teasing a new product for a while now, hailing it as a game-changer which isn't a tablet or a smartwatch. While speculations were rife about what this game-changing device could be, the company did confirm that the product was indeed a drone in their recent AMA. A tweet and vine from OnePlus shed some more light on this product, which was confirmed to be named as DR-1 (dr-one, get it?) and was to reach stores "next month". In a...
Next Version of Android to Cause Even More Issues for Root App Developers
You may recall that a few months back, XDA Senior Recognized Developer Chainfire analyzed some upcoming changes to AOSP that will likely appear in the next publicly available version of Android. As a quick refresher, the two commits in question at the time made life a little more difficult for root app developers by preventing the SU binary from executing files stored on the /data partition. Because of this change, root-enabled applications that extract and execute files from app-specific directories in the /data partition will have to be updated in order to work on the next version of Android. Luckily, Chainfire detailed a few potential workarounds that were added to his How to SU page. These workarounds include extracting the code and running it from RAM or rootfs, piping commands directly to SU, and so on.
Now, a few more changes have been made to AOSP, which will very likely appear in the next version of Android–be it 4.4.3, 4.5, or whatever other version number Google decides to bestow onto this new build. For starters, changes to SELinux to make it significantly more secure now require more complicated context switching than what was detailed in Chainfire’s previous workarounds. Next, it appears that ART will indeed be the default runtime compiler in the next version of Android. And due to its current immature state and restrictions imposed by SELinux, ART may cause crashes that take down the entire system when incorrect calls are made. Finally, it appears that PIE (Position-Independent Executable), which has been supported since Android 4.1, is now required on non-statically built executables.
Despite all of the changes detailed above, Chainfire already built and released a new version of SuperSU (1.97) that works around all of the potential issues. You can obtain this build directly from the SuperSU thread. Chainfire also updated his How to Su guide with information regarding these changes and how to work around them. And for the full story on all of these root-related changes, head over to Chainfire’s Google+ post.
Want something on the XDA Portal? Send us a tip!
With XDA being a community of Android enthusiasts, it is not uncommon to see lots of bashing on Apple's iPhone here. There are different reasons for the hate, but we'd like to hear your number one reason for not going with the iPhone. Let us know your thoughts below!
If you are familiar with Xiaomi, you might have heard that they are not the most compliant when it comes to the General Public License that makes the core of Android open to us. The terms of the GPLv2 state that since the Android kernel is based on the Linux kernel, which is licensed under GPL,v2 Android has to be open-source for everyone to study or modify, and those that modify the Android kernel have to make their sources immediately available for...