Google Music locks up when Samsung Galaxy S3 goes idle

[Ytsejamer1]

I finally had to uninstall the updates for Google Music. I believe the update on November 12 is what started causing these problems, for me at least. I was getting the issue where music started playing from the phone speaker instead of the car speakers when the aux cable was plugged in. There were two quick fixes, unplug cable and reinsert or pause song and start playing again. One of those "fixes" seemed to cause my other problem, songs "playing" longer than they actually were. The song would end at 3:15 for example but the clock would keep ticking time and the next song wouldn't play. This required a Force Stop.

I have had none of these problems since uinstalling updates. I left info regarding this problem in my review in the Play Store and also in a bug report directly from the app. No response yet or new update.

It's definitely the latest version of the Google Music app...I've been working with one of the Google Music specialists and he had me capture some logs when recreating the problem. I used alogcat to capture the logs. Unfortunately the android devs changed the permissions on one of the log directories in 4.1 so it required me to set them manually to read only for the alogcat app. Once I did that, the logs started flowing into the program.

Hopefully there is a resolution to the issue sooner than later. In the meantime, going back to the stock JB Google Music app that is included by default and unchecking the auto-update option on that app gets me by. The older version works fantastic.

 

[Chosen414]

thanks for the help reading this just cleared up so much BS wit google music...im going back to zune soon as i get another 64 gig micro sd card.

 

[Ytsejamer1]

I heard from the Google Music specialist that they made some changes on the back end and asked me to simply upgrade to the current version of Google Music on the Play store. I'm happy to report that all oddball issues with the latest Google Music seem to be fixed. I'm not privy to any details as to what they did, but all appears normal now! No more "locking up" after three songs, no more sound coming out the speaker on the second song, etc.

Update to your hearts content.

 

[JS_racer]

Not seeing a newer version than November 12. That version sucked bad for me, lockups, wakelock till a reboot, cover art issues. I went back to the original version. Looking forward to a fix. Were you told to retry the nov 12 version? Or something newer?

Thanks

 

[Ytsejamer1]

Not seeing a newer version than November 12. That version sucked bad for me, lockups, wakelock till a reboot, cover art issues. I went back to the original version. Looking forward to a fix. Were you told to retry the nov 12 version? Or something newer?

Thanks

They didn't release a new version...they apparently found something possibly on their back end that was adjusted. Honestly, I'm not sure what they found, but no new version was released. The November 12th version is indeed working normally now on the S3.

 

[tillerrw]

They didn't release a new version...they apparently found something possibly on their back end that was adjusted. Honestly, I'm not sure what they found, but no new version was released. The November 12th version is indeed working normally now on the S3.

I installed this same version for again two weeks ago. It is working better but I still get the bug where music comes from the phone instead of the headphones and a track stops. It doesn't happen as often but it still happens on my S3.