In the greater history of computer gaming, Linux is a relative newcomer, still missing out on quite a few AAA titles and only recently gaining access to Steam. While the library of games is growing for the open-sourced OS, the actual development process is still locked in to Windows. Most of the tools used for designing 3D models (e.g. Blender), landscapes, and other graphics have made the transition to Linux, but the primary coding tools are mysteriously absent.
Chainfire has been a busy, busy developer. Just a few days ago he released the first working root app for Android 4.3, and now he's sharing an early alpha of his new location tracking project, GeoLog. It's similar to other coordinate logging applications, but takes full advantage of Google's new Fused Location Provider and Activity Recognition APIs (check out Google's demonstration at I/O) to determine how precisely it should be tracking your position, and if it should even be actively logging at all.
Screen mirroring on Android is still a bit of a hit-and-miss prospect. Plenty of issues can arise from environmental factors like network congestion, to the type of device being used (*ahem*, Tegra). A few months ago, we covered a recent entrant in this market, BBQScreen by XpLodWilD and nebkat. The app was able to deliver a pretty consistent 25 fps from several types of devices over WiFi, Bluetooth, or USB. Unfortunately, several bugs and incompatibilities plagued some users, but the developers have been working hard to remedy many of those issues.
It's no surprise that Google's latest update to our favorite operating system is in instant demand amongst power users and enthusiasts. Without fail, the people eagerly installing 4.3 are frequently the same ones who consider root privileges a necessity for a good Android experience. Unfortunately, it seems a wrench has been thrown into the works when it comes to exposing ultimate access, and people are experiencing more than a few hiccups because of it.
When it comes to beautifying your phone, most of the options involve complicated modding procedures, installing sketchy software, or spending entirely too much time shuffling through configuration screens. Sometimes, all we need is a low maintenance option that does the hard work for us. To that end, Sparky Lock Screen is determined to deliver an ultra-fast, incredibly simple lock screen replacement that looks great without making you work for it.
Simplicity is obviously the driving force behind Sparky.
It's hard to deny that Android Studio has been a big hit since its announcement at Google I/O this year, and despite the "Early Preview" moniker, developers have been flocking to it. Yesterday afternoon, version 0.2.0 was announced through the Android Developers account on Google+. The new version brings several bug fixes and updates to the IntelliJ IDE, Lint, Gradle, templates, layout rendering, and more. While the list of new features is relatively sparse, what has been added it pretty cool.
Hot on the heels of Bluebox's disclosure of the "Master Key" exploit, a Chinese blog has posted details of a similar vulnerability. This attack also sidesteps a bug in the signature verification step and allows seemingly innocent APKs to include a potentially dangerous payload; and like its brethren, Google has already patched the flaw and posted it to the Android Open Source Project (AOSP). The information comes to us from a China-based group (or possibly individual) calling itself the Android Security Squad.
Scary tales about Android malware have been told since before people started guessing what dessert name would start with the letter 'D' (it's "Donut," in case anybody has forgotten.) Most of those claims came and went, amounting to little more than ghost stories. Unfortunately, there are a few real ghouls and goblins for which we should be afraid. Back in February, one such monster was discovered lurking about that allowed modified APKs to be installed on your device while successfully side-stepping the cryptographic signature used to prevent that very thing.
Falcon Pro users have had a front-row seat to quite a bit of drama over the last few months. The events started when the app struck its 100,000 user token limit, which lead to the developer to reset user tokens in an effort to reallocate them to active users. Eventually, all of the tokens were consumed again, in part to the addition of multi-account support, and another "reset" was announced.