The Samsung Galaxy S6 and Galaxy S6 Edge are already proving to be amongst the head turners of 2015. From favoring their inhouse Exynos 7 SoC over the Snapdragon 810 SoC (which ended up causing issues to its main rival); to ditching the removable battery and micro sd card slot in favor of a more "premium" device, the flagship duo have a lot going on for them at this stage. Regarding the premium redesign which replaced plastic with metal and glass,...
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!
Join us in a fun Sunday Debate on Cyanogen Inc. Come with your opinions and feel free to read some of our thoughts, then pick your side or play devil’s advocate to get your voice heard and engage in friendly discussion. You can read our food-for-thought or jump straight into the fray below! CyanogenMod is widely recognized across XDA for its solid performance, great feature set and far-reaching (and also long-lasting) support for all sorts of devices, from...
There are tons of choices to choose from when looking for a great alarm app for Android. While the stock Clock app for AOSP does the job, it may lack some of the more advanced features from competitors. Let us know what your favorite alarm clock app is for Android and why.