New Library for Controlling Access Points on Android 2.2+

Recognized F-Droid developer mvdan has written a library to access hidden methods in Android’s WifiManager and grant control over access points on Froyo and above. With this library, you can: enable and disable access points, configure an AP using WifiConfiguration, get your device’s IP address in your AP network, and get a list of clients connected to your AP. If you have written an app that in any way uses wifi, this link and its corresponding Reddit thread are well worth your attention.

from xda-developers » xda-developers | New Library for Controlling Access Points on Android 2.2+ http://ift.tt/1EZ0j5P
via IFTTT

Motorola “Bounce” Coming to USA as Verizon Droid Turbo 2

If reputed leaker @upleaks is to be believed, the shatterproof Motorola Bounce will make its way to the USA in the form of the Droid Turbo 2. The Droid Turbo 2 will be a Verizon exclusive upon launch.

from xda-developers » xda-developers | Motorola “Bounce” Coming to USA as Verizon Droid Turbo 2 http://ift.tt/1EYuYA4
via IFTTT

Stagefright Exploit CVE-2015-1538 Available For Testing From Zimperium

Zimperium has made the CVE-2015-1538 “Stagefright” exploit publicly available for testing and further research purposes. The exploit is in the form of a python script that generates an MP4 exploiting the Stagefright vulnerability. Head on over to get the python script!

from xda-developers » xda-developers | Motorola “Bounce” Coming to USA as Verizon Droid Turbo 2 http://ift.tt/1EYuSZg
via IFTTT

Niantic Labs’ Next Game Fuses Pokemon With Ingress In Pokemon Go

Niantic Labs, in collaboration with The Pokemon Company, is aiming to merge the social aspects of geo-location based games like Ingress with the awesome fun of capturing Pokemon. The game will be available in 2016 on Android as well as iOS devices, and will also feature its own smart wearable in the form of the Pokemon Go Plus.

from xda-developers » xda-developers | Niantic Labs’ Next Game Fuses Pokemon With Ingress In Pokemon Go http://ift.tt/1UE0ASQ
via IFTTT

Initial Details of the Samsung Galaxy S7 Surface

Fresh off the back of Apple’s announcements yesterday, some of the first details of Samsung’s next flagship have emerged from benchmarks and an industry source. Specs include either a S820 or new Exynos processor based on the Mongoose M1, a new 20MP ISOCELL camera sensor, and a method of accelerating SD card read/write speed to UFS2.0 territory.

from xda-developers » xda-developers | Initial Details of the Samsung Galaxy S7 Surface http://ift.tt/1EY8q2w
via IFTTT

XDA Forum for the NVIDIA Shield Android TV Now Live!

NVIDIA’s Shield Android TV has been seeing some decent interest and activity in the enthusiast circles. And to add some more awesomeness to an already great piece of tech, we have added forums for the Shield Android TV! Head on over to the forums to meet and discuss with other Shield TV owners.

from xda-developers » xda-developers | XDA Forum for the NVIDIA Shield Android TV Now Live! http://ift.tt/1OfjmLo
via IFTTT

AOSParadox, a New ROM for the OnePlus One With a Fresh Perspective

AOSParadox is the first ROM for the OnePlus One that isn’t based on the CM device tree. Instead, it’s directly based off CAF AOSP (CodeAurora Forums; CAF AOSP is basically stock AOSP with additional optimizations for Qualcomm devices) repos, making it as close to AOSP as you can get on a non-Nexus.

Why is the device tree important? If you’re not familiar with ROM development, it’s a crucial part of any ROM you use and describes your hardware so that it can be used by the system. Without using a device tree, developers can’t build a ROM. AOSParadox builds upon the CAF Qualcomm device trees but leaves it almost untouched. Instead, a new tree definition is used as an overlay, with only the necessary modifications to the original tree made by Qualcomm in order to boot the device.

This results in all Qualcomm features being available, such as Factory Reset Protection (FRP) which requires a password before a factory reset can be performed, making it harder for thieves to make use of stolen devices. The philosophy behind the ROM is to have everything made in mind for the OnePlus One alone, without having common definitions. The goal is to create an optimized AOSP ROM that is easily accessible by other developers, by making updates and development easier since it makes it unnecessary to test on multiple devices, and this results in cleaner code.

Different branches are used for each chipset (currently, the msm8974 and msm8226, respectively used for the OnePlus One and the Moto G/Moto G 2014, which are also supported), and each chipset has “optional” branches to organize them further for specific devices. The AOSParadox device tree also uses a different, chipset-specific ramdisk for the same goals as highlighted above. Because of some other incompatibilities, you should be aware this means it won’t be compatible with current custom OnePlus One kernels (or more specifically, the boot.img).

If you’re a developer interested in checking out the device tree, or a user looking for the closest experience to AOSP you can get, head over to the AOSParadox forum thread to get started!

 

Check Out XDA’s OnePlus One Forum >>

from xda-developers » xda-developers | AOSParadox, a New ROM for the OnePlus One With a Fresh Perspective http://ift.tt/1OdLXR0
via IFTTT