Jump to content

Getting Google Music (here's what I did)


Recommended Posts

Guest Paul
Posted

In response to requests on Twitter, I thought i'd knock up a quick post about the process I went through to get my Google Music account set up.

Basically I...

Step 1 - requesting an invitation

I requested an invitation on the day Google Music was announced at http://music.google.com/about/. The invite request form IP checks to ensure you are in the US, so you need to be connected via a VPN located in the US. I used http://www.privateinternetaccess.com (my VPN of choice as it's free with MoDaCo Plus).

Step 2 - installing the latest Google Music software

After requesting the invite, I installed the latest version of Google Music ready for when the invite arrived! :(

This can be achieved by either installing MarketAccess and spoofing your location as the US, or by installing this APK.

Step 3 - trying to boost my chances by spoofing a 3.1 equipped Xoom

Twitter and MoDaCo member @anditails mentioned that he had received an e-mail inviting him to Google Music as he had an Android 3.1 equipped Verizon Xoom. In fact, he has a UK WiFi Xoom that he had flashed with the 3.1 ROM. This got me thinking. <_<

I edited the build.prop on my Eee Pad Transformer, substituting in the lines below:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HMJ37
ro.build.display.id=HMJ37
ro.build.version.incremental=124251
ro.build.version.sdk=12
ro.build.version.codename=REL
ro.build.version.release=3.1
ro.build.date=Sat May 7 02:22:32 PDT 2011
ro.build.date.utc=1304760152
ro.build.type=user
ro.build.user=android-build
ro.build.host=android-test-7.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Xoom
ro.product.brand=verizon
ro.product.name=trygon
ro.product.device=stingray
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=stingray
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=trygon-user 3.1 HMJ37 124251 release-keys
ro.build.fingerprint=verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys
ro.build.characteristics=tablet
# end build properties[/code]

before doing a hard reset, re-setting up the device, running the Market, running Music and doing everything else I could think of to make Google see me. :P I left the configuration like this for a few hours then restored my normal backup.

[b]Step 4 - the invite arrives[/b]

Lo and behold, a few days later, my invite arrived in e-mail! :rolleyes:

I tried to accept it in the browser but it gave me the same error being outside the US, so I connected the VPN to accept. This is the last time I needed to use the VPN. I can now upload / download / play music on my PC and phone over a regular connection. And it's great! :D

[i]I hope this might help someone get on... please post below if you have any success![/i]

P

Guest Jamibu
Posted
I tried to accept it in the browser but it gave me the same error being outside the US, so I connected the VPN to accept. This is the last time I needed to use the VPN. I can now upload / download / play music on my PC and phone over a regular connection. And it's great! :P

P

I'm using an actual UK wifi Xoom that I upgraded to 3.1 and I have everything working now....though I don't remember having to vpn to accept the invite. Other than that, and not needing to spoof device, I followed the same route!

Guest redmongoose
Posted
In response to requests on Twitter, I thought i'd knock up a quick post about the process I went through to get my Google Music account set up.

Thanks, will edit the build.prop when I get home. Anything to perhaps speed up the invite process :rolleyes:

On another note I just replaced my entire build.prop file on the transformer last night with the xoom 3.1 build.prop and unsuprisinly it doesn't like it :P

Guest BrumBrum74
Posted

Can this editing be done on a phone build.prop? Nexus One?

My Transformer is stuck in customs. :P

Guest redmongoose
Posted

OK how freaky is this.......

just edited the build.prop on device, made folder read only and bam new gmail :P "You're Invited!" :rolleyes:

Yay

Thanks for instructions though!

Guest Johnrg
Posted

Thanks Paul!

Great tips as always.

And... less than an hour after sending my request... I've got my invite! Woohoo! :P

Uploading 9,000 tracks!

Guest praga
Posted

Yay same here got my invitation in From Cappy MIUI Rom with this instructions

Guest kartman_21
Posted

Can I do the same (using build.prop from xoom) on the galaxy S2?

How to upload this to my /system folder using adb?

Guest BrumBrum74
Posted
Thanks Paul!

Great tips as always.

And... less than an hour after sending my request... I've got my invite! Woohoo! :P

Uploading 9,000 tracks!

Did you edit on a HTC Desire or a Transformer?

Guest Johnrg
Posted
Did you edit on a HTC Desire or a Transformer?

My transformer.

Guest TheMathMan
Posted
Yay same here got my invitation in From Cappy MIUI Rom with this instructions

Can I ask if you made your build.prop exactly the same as above?

Did you remove any additional build information provided by Samsung and did you restart? I'm concerned restarting with this build.prop may do bad things on an S2!

Guest BrumBrum74
Posted

Got Invited as well. :P Thanks Paul for info. :rolleyes:

Guest guitarfreak
Posted

Ive edited in the lines posted but mines still saying Transformer under model number?

everything else has changed, 3.1 etc (wish it was lol)

Guest Matchstick
Posted

That's worked for me as well.

Excellent :P

Guest DaBeeeenster
Posted

I got my invite and am now uploading my library, but when I run the Music app on my SGS2 it doesn't ask me if I want to connect to the online service. Am I missing something?

Guest Johnrg
Posted
I got my invite and am now uploading my library, but when I run the Music app on my SGS2 it doesn't ask me if I want to connect to the online service. Am I missing something?

It took a while for the music app to register the Music Beta. keep it running for an hour and see if it picks up on it. If not, clear its data and reboot, leaving it running again for a while and you'll get a prompt to allow access to Google Music.

Guest DaBeeeenster
Posted
It took a while for the music app to register the Music Beta. keep it running for an hour and see if it picks up on it. If not, clear its data and reboot, leaving it running again for a while and you'll get a prompt to allow access to Google Music.

Ah great ta.

Upload process so far has been very very smooth.

One other question - Is it possible to tell the app where to store the music? Would rather it went on my external SD card...?

Guest mimminito
Posted
Ive edited in the lines posted but mines still saying Transformer under model number?

everything else has changed, 3.1 etc (wish it was lol)

Same. Hopefully someone will clarify this is ok (maybe its a hardware setting, not sure) and hopefully will get an inv soon!

Guest DaBeeeenster
Posted
It took a while for the music app to register the Music Beta. keep it running for an hour and see if it picks up on it. If not, clear its data and reboot, leaving it running again for a while and you'll get a prompt to allow access to Google Music.

Clearing the storage through settings then re-running the app sorted it out.

There's no option to set where it caches the files though which is *really* annoying! I want them on the MicroSD...

Guest DaBeeeenster
Posted
Clearing the storage through settings then re-running the app sorted it out.

There's no option to set where it caches the files though which is *really* annoying! I want them on the MicroSD...

I wonder if I could root the device and put a symlink in to point to the SD?

Guest DonVincenzo
Posted
Same. Hopefully someone will clarify this is ok (maybe its a hardware setting, not sure) and hopefully will get an inv soon!

Me too - I've had it sitting with the build.prop modified for about 12 hours now and still nothing...

Also, did everyone who had success follow Paul's path all the way along (i.e. after adjusting the build.prop, hard reset, setup tablet and use market etc for a few hours, then restore nandroid)?

Thanks!

Guest kartman_21
Posted

hi all,

I tried to edit the build.prop both with full example of Paul but also using the Galaxy S2 base build.prop.

unfortunately this is not succesfull, as after edit and reboot of phone, the phone keeps rebooting (bootloop), after I have to reflash my phone.

Does someone have any idea how to make this work for the SGS2?

original build.prop

---

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=GINGERBREAD

ro.build.display.id=GINGERBREAD.XWKDD

ro.build.version.incremental=XWKDD

ro.build.version.sdk=10

ro.build.version.codename=REL

ro.build.version.release=2.3.3

ro.build.date=Tue Apr 26 09:00:32 KST 2011

ro.build.date.utc=1303776032

ro.build.type=user

ro.build.user=root

ro.build.host=DELL103

ro.build.tags=release-keys

ro.product.model=GT-I9100

ro.product.brand=samsung

ro.product.name=GT-I9100

ro.product.device=GT-I9100

ro.product.board=GT-I9100

ro.product.cpu.abi=armeabi-v7a

# Samsung Specific Properties

ro.build.PDA=I9100XWKDD

ro.build.hidden_ver=I9100XWKDD

ro.build.changelist=161513

ro.product.cpu.abi2=armeabi

ro.product.manufacturer=samsung

ro.product.locale.language=en

ro.product.locale.region=GB

ro.wifi.channels=

ro.board.platform=s5pc210

# ro.build.product is obsolete; use ro.product.device

ro.build.product=GT-I9100

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=GT-I9100-user 2.3.3 GINGERBREAD XWKDD release-keys

ro.build.fingerprint=samsung/GT-I9100/GT-I9100:2.3.3/GINGERBREAD/XWKDD:user/release-keys

# Samsung Specific Properties

ro.build.PDA=I9100XWKDD

ro.build.hidden_ver=I9100XWKDD

ro.build.changelist=161513

ro.tether.denied=false

ro.flash.resolution=1080

# end build properties

#

# system.prop for asop5000

#

rild.libpath=/system/lib/libsec-ril.so

rild.libargs=-d /dev/ttyS0

ro.sf.lcd_density=240

dalvik.vm.heapsize=64m

# Samsung USB default mode

persist.service.usb.setting=0

#

# ADDITIONAL_BUILD_PROPERTIES

#

ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html

ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html

ro.com.google.locationfeatures=1

ro.com.google.clientidbase=android-samsung

ro.com.google.gmsversion=2.3_r3

media.stagefright.enable-player=false

media.stagefright.enable-meta=false

media.stagefright.enable-scan=false

media.stagefright.enable-http=true

media.stagefright.enable-rtsp=false

ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html

ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html

ro.com.google.locationfeatures=1

keyguard.no_require_sim=true

ro.config.ringtone=01_Minimal_tone.ogg

ro.config.notification_sound=01_Sherbet.ogg

ro.config.alarm_alert=Good_Morning.ogg

ro.config.media_sound=Media_preview_Touch_the_light.ogg

ro.opengles.version=131072

ro.setupwizard.mode=OPTIONAL

ro.secdevenc=true

ro.wtldatapassword=true

net.bt.name=Android

dalvik.vm.stack-trace-file=/data/anr/traces.txt

----

thanks

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.