There are so many Power Banks out there. However, they are not all the same. Some sacrifice weight for capacity. Others do the opposite. Some come with two ports and some come with more, while others come with less. Some are just batteries with a case around it, but others have some unique features. In this episode of XDA TV, Producer TK reviews the RAVPower RP-WD02 Wireless Filehub & Portable Travel Router. This device is the successor to the RP-WD01...
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!
Most of this article doesn't only apply to Telegram+ -- it just happens to be an example that got a lot of coverage elsewhere, with many authors or commentators putting the full blame on Google, Telegram, the Telegram+ developer or even WhatsApp Inc (eh?). In this article, we'll try to look at the different aspects to provide a clear view of what actually happened, and what can (and hopefully will) improve with regards to developers in general and the Play...
Ever since custom recoveries and roms became popular, nandroid backups have been the fall back method for all android enthusiasts, irrespective of their confidence levels. They allow easy backup and restore in case things go wrong, which happens invariably when a modification is being tested. With that being said, how relevant are Nandroid Backups to this day? Back in 2011, when the world of Android was being awed by the likes of the Samsung Galaxy S2, a little modification made its appearance...