Google Assistant was introduced at Google I/O last year, as a more personal voice assistant than Google Now. Since then, it has been made available on several platforms - Pixel phones, the Google Home, Android TV, and Allo. But Assistant is still unavailable on non-Pixel phones without a special build.prop tweak. Now the Open GApps team has made enabling Assistant a little easier.
It's no secret why CyanogenMod is the most popular custom ROM out there; not only does it support a metric crapload of Android devices, but it also keeps them going far past their primes. The latest devices to get support for CM14.1 (Android 7.1 Nougat) nightlies include two variants of the Galaxy S III, the second-generation Moto X, a few Oppo devices, two versions of the HTC One Max, two Xiaomi phones, and more.
Earlier today, some disappointing news came from Steve Kondik, CyanogenMod's founder and Cyanogen Inc.'s cofounder; because of Cyanogen Inc.'s failure, "(CyanogenMod) is very much affected." For the time being, though, CyanogenMod maintainers are still churning out new builds of CM14.1 (Android 7.1 Nougat) for many devices. We've got seven new devices with CyanogenMod 14.1 nightlies this time around (well, more like five, since two pairs of the devices are almost exactly the same).
Cyanogen Inc. may be dying as a company, but the voluntarily-maintained CyanogenMod ROMs are still alive and kicking. Case in point: seven more devices are joining CyanogenMod 14.1, which is based on Android 7.1 Nougat. Six of these Android-powered machines have builds already up, but one doesn't yet.
OnePlus phone owners can probably agree that the company needs to work on faster OS updates. (It's a safe bet: pretty much everyone can agree on that, including Nexus owners.) OnePlus is trying. To that end, the company has announced that its two disparate Android software builds will be merged into one: Oxygen OS and Hydrogen OS. I'll pause for a moment to allow the chemistry nerds to make an H2O joke before we continue.
After releasing an OxygenOS 3.5 Community Build for the OnePlus 3 a little over a week ago, OnePlus has already issued an update that fixes a few complaints. For such a small version bump (3.5.0 to 3.5.1), this update actually packs quite a few improvements.
Microsoft's home-built (or home-bought) smartphone lineup may not be long for this world, but it looks like the development community isn't giving up on it. The Nokia Lumia 520 is an entry-level Windows Phone 8 device, announced back in 2013, and later succeeded by the Lumia 525 and 530.
A few days ago, XDA developer banmeifyouwant posted a video of his in-progress CyanogenMod 13 port to the Lumia 525. The video shows CM13, based on Android 6.0, booting on the device as well as opening and closing apps.
The developer only demonstrated the 525 booting, but he is currently working on kernel tweaks to allow the 520 to boot as well.
Who says that Nexus owners get to have all the fun? Yesterday an innocuous XDA thread claimed to have a beta version of an Android 7.0 build, ready and waiting for Huawei's dual-camera phone, the P9. Usually that sort of post when we're still weeks or months away from a full AOSP release of a new Android version is, to put it bluntly, bunk. But in this case, users who have flashed the ROM say that it's functional and apparently legitimate - Huawei's proprietary EMUI skin, marked as version 5, is running on top of Nougat. It's working on the EVA-L09 model; others may not be compatible.
The CyanogenMod Team continues to expand its list of officially-supported devices, and now the LG section of said list is longer by four entries. Yesterday the CM servers started spitting out nightly builds for the LG G3 S, the LG G3 Beat, The LG G2 Mini, and the LG Optimus L70 smartphones. All of them are CyanogenMod 13 (Android 6.0), and they're all available for download and flashing right now. At the time of writing three of them have two nightly builds, while the G2 Mini has only one.
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.