I flashed my first ROM last night, and tried to play music using Google Music Beta, which I downloaded from the market. When I try to play the music, the app keeps on force closing. I tried reinstalling the app, tried reflashing the rom, but nothing seems to work. Any help would be appreciated.
Did you perform a full wipe before flashing the rom? I'm running 2.1 (remix) as well using mr2.5 and the kernel that came packed with BAMF 2.1. Having no issues using google music beta. Don't have much in the way of advice, just chiming in to help you narrow down where your issue is coming from (namely that the rom itself shouldn't be the issue). Might want to verify the md5, never know when you might snag a bunk download.
Suboof said:
Did you perform a full wipe before flashing the rom? I'm running 2.1 (remix) as well using mr2.5 and the kernel that came packed with BAMF 2.1. Having no issues using google music beta. Don't have much in the way of advice, just chiming in to help you narrow down where your issue is coming from (namely that the rom itself shouldn't be the issue). Might want to verify the md5, never know when you might snag a bunk download.
Click to expand...
Click to collapse
Yes, I performed a full wipe before flashing the ROM, assuming that means data/factory reset, cache, dalvik cache, battery stats...did that three times. Not sure if I am supposed to do it more. Also checked the md5, downloaded and flashed it twice more after the first time, and still can't get it to work.
Hrm, afraid I don't have much else to suggest outside of verifying settings within the music app itself. As I said, was primarily just letting you know the rom itself shouldn't be the issue. Sorry I cant be of more assistance . Might try a different rom and see if the issue persists, but if you're liking the 2.1 thats far from an actual solution even if it does solve the problem.
Suboof said:
Hrm, afraid I don't have much else to suggest outside of verifying settings within the music app itself. As I said, was primarily just letting you know the rom itself shouldn't be the issue. Sorry I cant be of more assistance . Might try a different rom and see if the issue persists, but if you're liking the 2.1 thats far from an actual solution even if it does solve the problem.
Click to expand...
Click to collapse
Never mind, I thought I got it working, but after playing a song, it crashed. I might just go back to stock rom, not a really big issue.
hksg said:
I flashed my first ROM last night, and tried to play music using Google Music Beta, which I downloaded from the market. When I try to play the music, the app keeps on force closing. I tried reinstalling the app, tried reflashing the rom, but nothing seems to work. Any help would be appreciated.
Click to expand...
Click to collapse
I was having the same problem (just 20 minutes ago). The app would load, the albums and tracks would appear, and then when I went to play one of them it would force close. What I did to correct the problem was to to reflash 2.1 in recovery without wiping. I let in reboot and now its working fine.
I am running bamf 2.0 - 5 and it works for me.
Although it Sometimes makes my phones signal drop to 1x so maybe flash a new radio?
THUNDERBOLT
poisonj5 said:
I was having the same problem (just 20 minutes ago). The app would load, the albums and tracks would appear, and then when I went to play one of them it would force close. What I did to correct the problem was to to reflash 2.1 in recovery without wiping. I let in reboot and now its working fine.
Click to expand...
Click to collapse
Tried this, then even flashed the new ROM RC1 and RC2, and still am unable to get it working. Any help is appreciated. I just keep on getting the same issue, Error playing requested track. And then when I go to check the app data, I see the numbers going in and out, flickering, and have to force stop and then uninstall.
hksg said:
Tried this, then even flashed the new ROM RC1 and RC2, and still am unable to get it working. Any help is appreciated. I just keep on getting the same issue, Error playing requested track. And then when I go to check the app data, I see the numbers going in and out, flickering, and have to force stop and then uninstall.
Click to expand...
Click to collapse
same for me. I'll be going back to stock or another ROM until this gets solved
theredspecial said:
same for me. I'll be going back to stock or another ROM until this gets solved
Click to expand...
Click to collapse
ATM, I am using Lighting Rom 3.3.1, which is a Froyo ROM, but I might try one of the other Gingerbread ROM's available. But I really did love that DasBamf ROM, and the issue seems to be amongst just a few of us.
Bump.
Still having Google Music force close on Das BAMF RC3. Can anyone confirm that it works?
I can confirm I'm having the same issue with BAMF 2.1 stripped. I tried reloading the rom without wiping and fixing permissions and still getting a force close when I attempt to play anything from the cloud.
Sent from my ADR6400L using XDA Premium App
hksg said:
Bump.
Still having Google Music force close on Das BAMF RC3. Can anyone confirm that it works?
Click to expand...
Click to collapse
It is listed as a known issue in the RC3 thread, but they are having trouble reproducing it. I had the same problem with RC1, but after I wiped and loaded RC3, it appears to be working fine now. I only loaded it last night and tested a little this morning though, so problems could still develop. When I was having trouble with RC1, I tried the procedure of uninstalling Google Music, unmounting SD card, reinstalling Music, and then remounting SD card. It didn't work with RC1, but I did the same thing prior to testing Music on RC3. I have no idea if that made any difference either way, but it won't hurt to try.
Edit: The known issue could be referring to the HTC Music app, not the Google one, now that I look at it again.(Still reading through the entire RC3 thread)
FreemanB said:
It is listed as a known issue in the RC3 thread, but they are having trouble reproducing it. I had the same problem with RC1, but after I wiped and loaded RC3, it appears to be working fine now. I only loaded it last night and tested a little this morning though, so problems could still develop. When I was having trouble with RC1, I tried the procedure of uninstalling Google Music, unmounting SD card, reinstalling Music, and then remounting SD card. It didn't work with RC1, but I did the same thing prior to testing Music on RC3. I have no idea if that made any difference either way, but it won't hurt to try.
Edit: The known issue could be referring to the HTC Music app, not the Google one, now that I look at it again.(Still reading through the entire RC3 thread)
Click to expand...
Click to collapse
It was indeed the HTC Music app that is the known issue. I posted in the thread, and I provided a logcat, so hopefully someone with more experience than me can understand it.
I'm having the same issue on DAS BAMF 2.1 on latest lean kernel.
I can get it working 99% of the time with wifi only. If i use 3g or 4g the app force closes. I've tried different kernels as well.
Anyone else able to confirm if this issue is wifi/3g/4g related? Im able to use the player only if I use wifi.
Maybe this can help the devs push out a patch in 2.2
I am using it right now on RC3
Sent from my ADR6400L using XDA Premium App
I'm also able to get it to work if i wirelessly tether to another thunderbolt. Only time I have an issue is if I'm using the 3g/4g radio.
I just go to Google music and play from the cloud
Sent from my ADR6400L using XDA Premium App
BlackHoleSlam said:
I just go to Google music and play from the cloud
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
I mean I can access music.google.com from the browser but that kind of defeats the purpose of the app/widget.
My friend who has the same rom isn't getting the issue.
Okay so I'm up to date with ComRom 2.1 (PBJ -50) and everything is working except the Napster App won't let me sign in. It does not force close, it just wont log in and it gives me the error
"We did not recognize your member name or password. Please re-enter your member name and password."
My wife's fascinate is bone stock and she can log into the Napster App with my sign in info without issue so it's not an apparent issue on Napster's end.
I can also log into Napster through the browser, but it doesn't let me play.
I was able to sign into the Napster app in 1.3.
Does anyone have any ideas on how to fix / get around this. I flashed the myfiles patch to see if that would do anything but same issue.
Thanks in advance
I have the except same problem except on I am on OTB 1.5 if that makes any difference behind the scenes. I have not tried any other roms except the leaked Gingerbread which in fact does work.
Who still uses napster? But really it is probably a network problem on your end, try again later.
Sent from my SCH-I500 using XDA App
My friend beside me login just fine, but I am still getting the same error. He is on stock rom, just rooted.
Ok so I have been looking over the forums and I hope I didn't miss it if there is a post already about this so I am going to go ahead and ask away. If it has been posted and I did miss it then I apologize for beating a dead horse.
I have tried the Liquid Gingersense (v1.4, v1.5, and v1.6) and CyanogenMod (v7.1.0-RC1.5.2 and v 7.1.0-RC1.6.1) and have not had any luck. Along with some minor esthetic issues I had with the CyanogenMod, I had noticed that the Gingersense actually disabled my radio and I was unable to make any calls and the signal bars would just show up with an "x" next to it. I rebooted many times and kind of tinkered around and tried other ways of turning it on or playing with LTE on/off to see if that would help in any way and I never did get it enabled.
When I would look at the "Quick Setting" (if I recall the name correctly), the icon for me to enable it was greyed out so clicking on it did nothing at all. Has anyone had this issue? Did I perhaps miss doing something when setting this up? Any help on this would be greatly appreciated.
You mentioned that you had no signal with Gingersense but not with Cyanogenmod so I'm not sure if this is your case but did you flash the radio suggested for those roms? MR2, GB leak, etc. If not, you can find links in the pinned thread at the top of the Q/A.
Also, remember when switching between roms to wipe data/cache.
No actually I did not try that. So if I do get time to do that do I do the ROM then the radio thing? I do believe I came across a.radio deal and thought " I wonder if I need to install that?" But never tried. I figured it safer to ask and not break my phone than to break it and figure out how to fix it...lol
Sent from my ADR6400L using XDA App
Ya sounds like you need to flash an Mr2 or higher radio. Check the q&a stickys for links and instructions.
Sent from my HTC Thunderbolt
Well I decided to give it another shot. I have GingerSense v1.7 installed and did the MR2 install and it all works perfectly. I have a few apps I need to reinstall and a couple icons to redo but other then that everything looks great and seems to work smooth. Thank you guys for the help. I greatly appreciate it.
Actually the only issue I am having right now is that every...I dont know maybe 5 minutes or so there is an error that pops up that Im not sure how to get rid of. It says...
"The application Google Services Framework (process com.google.process.gapps) has stopped unexpectedly. Please try again"
Any ideas or thoughts about this?
Well I think I have discovered the root of this error. I have noticed that when I text and if o click on the Mic to do voice to txt that even though the screen pops up as if it OS going to record, it does absolutely nothing. How to fix it is where I am still stumped though.
Sent from my h4x0r3D ADR6400L using XDA App
Well it seems I have been noticing some weird things that are making me think maybe I should try Gingersense v1.5
At first my camera was working but Im not sure why it isnt now. I cant do pics or video and lastnight when I was trying to Skype with my cousin in CA the video cam didnt work for me. I also have been getting two different errors...
1) The process com.google.process.gapps has stopped unexpectedly. Please try again.
-AND-
2) The application Talk (process com.google.android.talk) has stopped unexpectedly. Please try again.
I also had noticed that it seems to take a bit longer for the phone to boot in comparison to what it used to and especially when it was brand new and not yet rooted. I have a custom static image that says "HTC quietly rooted" and a WWII themed Android boot animation". When I reboot I get a black screen for about 30 seconds then the custom HTC image comes up for about 20-25 seconds then the custom animation plays THEN once that's done I'm booted into my phone.
Is there any kind of way to cut those times down for faster booting? Well I think I will have to keep messing with this and see what I can do...
Has anyone had luck getting Huluplus working on classicnerd? I have the modded apk file, I've removed the hosts file, but it still wont play because of the ads needing to load.
Not sure whats causing the blockage at this point as all the old tricks from Xron aren't working.
Anyone have any luck?
If you flash it, they will.... ok, that just doesn't work.
You can get Hulu to work via the web with a modified Flash but I wouldn't bother until they get hardware acceleration working. It's not really watchable and just stutters and locks up.
I haven't been able to get the Hulu apk to work on any ics based rom for the Touchpad no matter what I try.
If you absolutely must have Hulu on the touchpad at this point, I hate to say it, but you are probably just better off with a Gingerbread based ROM.
Or do a simple restart and boot into webOS. That's the beauty of it.......people go through so much trouble trying to make things work on the "Touchpad" that already do.....just takes 2 minutes to restart, then Skype works, Camera Works, Hulu works!!! Pretty cool.
I agree with webOS for now. There is nothing wrong with booting into that until the hardware decoding gets worked out. At least this gets us by unit then.
digthemlows said:
Or do a simple restart and boot into webOS. That's the beauty of it.......people go through so much trouble trying to make things work on the "Touchpad" that already do.....just takes 2 minutes to restart, then Skype works, Camera Works, Hulu works!!! Pretty cool.
Click to expand...
Click to collapse
i wasn't able to find skype in webos. how did you get it?
It's baked in under phone and video calls. Under settings tab you can find accounts where you can log in.
Sent from my ADR6300 using XDA App
eckwheet said:
It's baked in under phone and video calls. Under settings tab you can find accounts where you can log in.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
thanks, i'll try that when i get home. i was looking for it earlier and was stumped.