Android Studio v1.5 just rolled out to the stable channel today and it's absolutely packed with a feature. Truth is this release was mostly focused on bug fixes, performance improvements, and other fine tuning. Of course, for a tool used in professional software development, those certainly aren't bad things. Take a look as Reto Meier explains the changes and trolls teases Android developers with a mystery box that surely must include new language support, or a fully functional theme editor, or... something more likely.
The one notable addition can be found in the Memory Profiler. It's now capable of detecting leaked activities while testing.
Google has already talked about new features in the upcoming Android Wear 1.4 update, but so far the only place you can experience them is on the new LG Watch Urbane 2nd Edition LTE. Updates for other watches are pending, but in the meantime developers can get ready for the new version with the API 23 SDK, which Google is currently in the process of rolling out.
By now most orders for the Nexus 6P have been delivered, or at least getting close. If you haven't tried unlocking the bootloader yet, it might come as a surprise that the 'fastboot oem unlock' command no longer works. Attempting to use it with the Nexus 6P fails with a message that it is an unknown instruction. Don't worry, this doesn't have anything to do with drivers, and it isn't a fluke. Google had Huawei replace the oem command in the Nexus 6P bootloader with the new flashing command. Here's what it will look like:
fastboot flashing unlock
fastboot flashing lock
fastboot flashing unlock_critical
fastboot flashing lock_critical
fastboot flashing get_unlock_ability
There are two levels of unlocking: normal and critical.
The Unreal Engine serves as the core for any number of games across PCs, consoles, and mobile phones alike. When a new version comes out, the changelog is big. Really, really big. Not all of the changes introduced in version 4.10 affect Android, but a solid number of them do.
Today, the Bluetooth SIG announced a series of improvements on the Bluetooth standard's "technology roadmap" in 2016 would offer enhanced range, speed, and mesh networking capability for the wireless communication protocol.
It's not clear if these changes will be part of a new standard (like Bluetooth 4.2 and beyond) or if there will be improvements applicable to older specs as well. In addition, we don't know if any of these improvements would require changes to the Bluetooth hardware itself, or whether both host and device must support the spec to see any kind of benefit. It's not even clear when we'll be able to expect devices with the improvements.
The Snapdragon 820 is far from a secret, but today marked the official "launch" of the upcoming chipset from Qualcomm in New York. The 820 is a huge bet for Qualcomm on the future of its high-end SoC business, marrying the latest technologies across the board for what it hopes will be the ultimate mobile processor.
The 820's full specification sheet, such as it is, is below.
The 820 will be manufactured on a 14nm FinFet process, sporting four brand-new Kryo CPU cores designed by Qualcomm. This marks a departure from the ARM reference cores Qualcomm has used exclusively on its 2015 lineup and which have arguably been a source of woe for the company this year.
This is a guest post by Ricardo "arcee" Cerqueira who takes things apart for sport, on a quest to understand how they work. He currently works on Android devices at Cyanogen.
As people started receiving their Nexus 6Ps, some began freaking out over a new message that comes up on the screen when booting into fastboot mode: “QFUSE: ENABLED,” with wild speculative theories coming up regarding what it does and doesn’t do, what kind of limitations it’s imposing, and wondering if and how it can be “disabled.” So... what’s this qFuse thing, anyway?
Think of an eFuse as the mind’s eye representation of a bit that only flips one way, or something that can only be done once on a piece of writeable flash.
Google began rolling out v8.3 of the Play services framework a few weeks ago, and it looks like it's in a wide release. While this version didn't present with any direct user-facing features and only a few cryptic hints for a teardown, it did bring some definite improvements to the Play services SDK. There are some changes to streamline the sign-in experience for app developers and users alike, along with some additional enhancements that should make it easier for developers to set up new user accounts. New APIs have also been added to make data delivery more efficient between a phone and an Android Wear watch.
Google promised monthly security updates for Nexus devices, and so far, the company has delivered. It's November 2nd, and we're now receiving this month's dose of security patches. Over-the-air updates are heading out to devices, but if you rather get the goods now, factory images are already up.
In our final Android 6.0 Compatibility Definition Document post, we'll be looking at a small[-ish] clause added in the security section of the CDD. Previously, Google had not actually defined any particularly specific requirements about factory resets for Android devices. While all devices have such a function, they may differ in their efficacy and level of security post-wipe. And while we don't have any reason to believe a particular manufacturer is not already meeting these new requirements (a point I will stress), it's good to see Google is at least laying down a clear mandate on this issue going forward.
Basically, it was possible, pre-Android 6.0, for a manufacturer to merely conduct a logical wipe when doing a factory reset of a device.