February 19, 2014 By: eagleeyetom
Before Motorola was acquired by Lenovo, the OEM released two very interesting smartphones. The Moto X and Moto G were the first and probably the last devices made by the formerly American OEM in a cooperation with Google. Not so long ago, we talked about the Moto G receiving an unofficial CyanogenMod port. Now, however, the G and a few other Motorola devices will receive official CyanogenMod nightlies.
The CM team has released three unified builds, which is a bit of a surprising move, considering that the list of supported devices is quite long. The “mysterious” moto_msm8960 build will work with the Photon Q, Atrix HD, Razr M, and Droid Razr HD. The second build, dubbed moto_msm8960dt, should work with dual-core devices like the Moto X, Droid Maxx, Droid Mini, and Droid Ultra. You need to figure out which phones are which, as builds for other devices will simply not work properly or even can brick your device. So be sure to double check before flashing, and check your home forum here on XDA to get the necessary info.
A build for the Moto G is separate due to its internal hardware. And I can’t can’t write about official nightlies for device code named falcon without mentioning XDA Senior Member dhacker29, who did a terrific job bringing up the device tree for this phone.
Motorola devices aren’t the only receiving these new unified builds. A couple of Samsung devices will receive unified builds as well. The list of phones is quite long and includes following devices:
Builds include only Qualcomm-based devices, as Exynos devices are still using platform-specified builds.
As you can see, the CyanogenMod team are on fire and make things as easy as possible both for developers and end users. The builds are located over on the official CyanogenMod download page. You can also check out the source code by visiting team’s Github and typing the name of the device in the search box.
[Big thanks to XDA Recognized Contributor herna for the tip!]
January 14, 2014 By: Will Verduzco
Google-owned Motorola keeps courting us by making all of the right moves, as they have been updating all of their current devices to KitKat left and right. We first saw the update make its way to the Verizon Moto X, even before the Google Play edition devices received their updates. And then a little under one month ago, Android 4.4.2 started rolling out to the Moto G.
Now, Googoorola has released the GPL-mandated kernel source code files for the well liked Moto G running KitKat. Back in early December, we saw the release of these same open source files for the device’s initial Jelly Bean firmware release. And now, they have been updated for Android 4.4, enabling your favorite aftermarket kernel devs to do what they do best. If you’re a kernel or ROM developer looking to get in on building a KitKat-capable kernel for the Moto G, make your way over to the SourceForge link below.
And in other Motorola news, the KitKat rollout that began on the Droid Maxx/Ultra/Mini as a preliminary soak test is now seeing a widespread rollout to the greater population of Verizon Droid users. This comes nearly one month after the initial soak test, and comes in at the same software version 19.5.3. Unfortunately, as we’ve seen from Verizon as of late, it also packs a little more bloatware. This comes in the form of a newly integrated NFL Mobile app, as well as the new “SSO client.”
Are you happy with Motorola’s efforts to appeal to the aftermarket development and enthusiast communities? Let us know in the comments below, and don’t forget to visit the Moto G and Droid Maxx/Ultra/Mini forums!
December 19, 2013 By: Will Verduzco
Earlier today, we commended Motorola on its efforts to work with the development community on the Moto X. Now, we’re going to congratulate them once again on a very expedient Android 4.4 KitKat update for the Droid Maxx/Ultra/Mini devices.
The update bumps up the software version to 19.5.3, and packs all the expected Android 4.4 goods. Curiously, while the Droid Mini is explicitly named on Verizon’s official Twitter page, only the Droid Ultra and Droid Maxx show up on their support docs. Unfortunately as we’ve seen from Verizon as of late, it also packs a little more bloatware. This comes in the form of a newly integrated NFL Mobile app, as well as the new “SSO client.”
The update is currently starting to roll out in the form of a staged OTA update, and the OTA has not yet been captured. But once it’s captured, we’ll update this post with the download link!
What are your thoughts on this update? Are you a fan of how fast Verizon and Motorola pushed this out, or are you more bummed that there is yet another piece of bloat? Let us know in the comments below, and share your thoughts in the update soak test thread!
October 24, 2013 By: Will Verduzco
Hardware capacitive buttons seem to be a love-it-or-hate-it affair. While many of us seem to prefer the versatility of the on-screen buttons most commonly seen on modern Nexus devices, others instead favor the increased usable screen real estate made possible by having dedicated keys outside of the display.
If you happen to own an HTC device, you are probably a fan of dedicated hardware buttons. But that’s not to say that you can’t tweak them to make them work better for you. XDA Senior Member denversc created an app called Capacitive Buttons Brightness, which does… Well, you guessed it. It allows you to change the brightness of your capacitive buttons.
Currently, the app officially supports the HTC One X (dual- and quad-core variants), HTC One X+, HTC One, and HTC One S. That said, many users have found that it also works on other devices such as the HTC One V, HTC Desire HD, HTC Evo 3D, Motorola Droid MAXX, and LG Optimus G.
The app allows you to change brightness in 3 steps: dim, bright, and off. The default on most Sense-based ROMs seems to be bright, whereas it is usually set to dim on most AOSP-based ROMs. Please note that the “off” setting does not work if you have the GV Integration app installed. Naturally, root access is required… But who here isn’t rooted anyway?
September 16, 2013 By: Will Verduzco
When the Moto X was released, many were upset to learn that despite Google’s positive influence during development, the device was still not truly open. And let’s be honest, there were never any false pretenses about the state of Motorola’s state of developer friendliness. However, it looks like master hacker and XDA Elite Recognized Developer jcase has done it again.
Not too long ago, jcase created MotoRoot for the Droid lineup. This used the previously covered Android bug 9695860 to gain system user. Then, a symlink attack created by jcase himself was used to obtain root access. Today, however, a better solution has appeared.
Courtesy of jcase once again, PwnMyMoto begins by using bug 9695860 (just like its predecessor) to gain system user. It also uses the symlink attack featured in MotoRoot to gain root access. New to PwnMyMoto, however, is what happens next: After gaining root, a bootloader vulnerability is exploited, allowing for write protection on the /system partition to be bypassed. And in the process, the stock recovery is removed, preventing unwanted future OTAs from interfering with the rooted state.
Naturally, any unauthorized modification carries with it an inherent risk. However, if you wish to root, you must take these risks in order to free your device. To get started, head over to the linked threads below. Congrats to jcase on the great work once again!
[Many thanks to jcase for the tip!]