Former Writer · May 16, 2012 at 05:30 am

Google Music Limits Device Deauthorization

For those who use Google Play Music often, you probably already know about the eventual need to deauthorize devices on your Google account when it fills up. This is especially true for the flashaholics out there who flash a ROM every other day and have to go into Google Music twice a month to get rid of the older “devices.” That’s problematic for a couple of reasons—namely because your Google Music is authorizing the same device over and over, and calling it a new device. And more importantly, because Google has now limited the number of times you can deauthorize devices.

XDA Senior Member Amphibliam posted a thread to alert users of the change, which has apparently been rolled out over the last 60 days. While the first few comments weren’t very affirming, reports began to roll in of the telltale banner stating that a particular user has deauthorized too many devices.

This has serious implications. First and foremost, flashaholics are gonna have to quit flashing things cold turkey to avoid hitting the 10 device limit because once that limit is reached, you can’t deauthorize your devices to add more. There have been some reports that you can email Google support and they’ll deauthorize the older devices for you; but if it’s true, it’s hardly convenient. Currently, there are only two ways around this new rule—either create a new account and re-upload your music to the servers or restore a Nandroid backup from a ROM that was working before. Using Titanium Backup (or any other app-specific backup) has been shown to not work, unfortunately.

With all the talk of Motorola further locking down devices, users and developers alike were hoping that Google would have an influence over Motorola’s decision to unlock the bootloaders. However, with Google locking up Google Music against flashers and root users, it seems as though Google is taking a page out of Motorola’s book. It’s a slippery slope from here. Let’s hope Google either undoes this decision or stops while they’re ahead.

To learn more, head on over to the original thread.


_________
Want something on the XDA Portal? Send us a tip!
TAGS:

Former Writer

Former Writer is an editor on XDA-Developers, the largest community for Android users.
Mathew Brack · May 25, 2015 at 06:00 am · no comments

Android M Code Name: Macadamia Nut Cookie

While the official name for the latest iteration of Android has yet to be revealed, the code name used internally by Google has been seen to be Macadamia Nut Cookie (MNC). This will almost certainly not be the final name for the release with rumors so far leaning towards milkshake, much like Key Lime Pie became Kit Kat and Lemon Meringue Pie became Lollipop. The acronym MNC has now also started to appear in several locations in AOSP, just look out...

XDA NEWS
Chris Gilliam · May 24, 2015 at 03:59 pm · 2 comments

XDA Recap: This Week In Android (May 17 – 23)

Another week, another recap. The Sunday tradition marches on this week with a fresh no-nonsense look at big-picture news. Here in the digital XDA writers’ room, we spend our days pouring over an average of 2,500 news items and forum threads every 24 hours. Only the most timely and interesting bits survive the editing process, but the portal’s front page still sees weekly counts in excess of 100 posts. This is a glut of content to absorb, especially if following...

XDA NEWS
Mario Tomás Serrafero · May 24, 2015 at 11:00 am · 1 comment

Sunday Debate: Are Smaller Bezels Better or Worth It?

Bezels have been getting smaller and smaller as the years go by, and while devices from 2011 needed to trim some fat, there is no absolute rule that says that smaller bezels, after a happy medium, are beneficial to a phone. Part of this is that, with today’s current smartphone paradigms, an absolute lack of bezels does not produce an inherently better user experience.   With each technological advancement come limitations and compromises of some sort, and bezels are not...

XDA NEWS
Share This