The adoption of Google Music has been dismal. Maybe it’s because we expect Google services to erupt like a volcano and immediately soar into the sky, blanketing the people below in Google awesome ash. Or maybe it’s because iTunes, Pandora and Slacker Radio already have a foothold ’round those parts. Or it could be that Google Music is only currently available in the U.S.
My guess is as good as yours, however there might be some sunshine on the horizon in the form of a developer, Simon Weber. Simon has been working on his unofficial Google Music API for a month, and has pretty much every functionality of the service coded into the API. Only one major implementation is missing at the moment: support for uploading formats other than .mp3. Unfortunately, however, the API is currently coded in Python, restricting it to desktop platforms. It isn’t impossible to port it to a mobile-friendly language though, and thankfully Aaron Gingrich of Android Police has put Simon in contact with CM9 [music player] Apollo developer Andrew Neal.
This could mean we see a port of the API to mobile platforms, pending the result of Neal and Weber’s collaboration. The only problem that will immediately come to mind reading “unofficial”, “Google”, and “API” is action taken by Google to, well, cease and desist. I don’t think that’s likely to happen, as Mr. Weber will be interning at Google this summer — possibly bringing official Google support for the API in the near future. This could be great news for Google Music, as integration into Android applications could surely inject some much needed life into the service’s disappointing adoption stats.
source: android police
If you are anything like me you must be getting excited to see ICS first hand, not only in person, but on your very own device. Not every one is going to be able to run out and purchase the new Galaxy Nexus and some can hardly wait for the official ICS update to roll-out for scheduled devices.
The peeps over at XDA have taken the wait away for you brave Nexus S owners who are willing to port an early unofficial build. The build is pretty close to the real thing but it is definitely not official. This build is based on an earlier version of ICS and some of the new Android 4.0 features are missing. There have been reports of minor issues ones that by no means make the device unusable: a few of the new icons are missing, NFC is a bust, the camera might have some glitches, and this build is sans facial recognition.
If you have a rooted device and are familiar with flashing ROM’s you may want to give this a whirl, if not I suggest just waiting it out a couple more weeks until Google pushes out the official release. Reports are saying that for an unofficial port it is super stable so if you’ve got a brass set and want to give it a try, hit the link below. Remember, anything YOU do to YOUR phone is at YOUR own risk!
We put out an article earlier this week, telling you that HTC had put up a post on their official Twitter, basically telling everyone that had used the unofficial Froyo update for their EVO should switch to the official version. Now, HTC is sending another official reminder for early adpoters to hurry up and wait on them for assistance getting to the official update.
A post left on their official Twitter now states:
If you installed an unofficial update on EVO last week, we working on a simple, effortless solution. Please bear with us a bit longer.
All you EVO owners out there on Froyo, whether official or otherwise, let us know in the comments how your phone is running!