I have a very weird issue with my Droid Eris. First off I had Kaosfroyo v29 on there with no problems and my music and everything was working perfectly. But then i Flashed Kaos Froyo V34 in this order (clear battery/rotation/dalvik/then flash v34). I get back and the music apps (Default music app, Meridian, and Mix Zing) and they all start skipping my music after a couple seconds of playing it. it continues to skip each song sometimes after 14 seconds other times before it even starts. It does this with the loudspeaker and when there is a headset connected. I don’t believe it is a hardware issue as it doesn’t do this in when I do my nandroid restore to v29. I have tried reformatting my sd and just putting a couple songs on there. Ive tried using headphones/not using them. Ive tried turning wifi off and then playing music (heard that could be an issue). ive tried other things as well but idk what it could be. If I clear/factory reset and then flash v34 streight, it doesn’t have this issue. When I do apps with data restore with titanium and reset the phone. The issue is back! So im thinking it might be an app I have? I looked at all my music related apps and don’t see one that could be causing it. I don’t have an app killer (although I have autokiller installed but I don’t think that could be causing it). I really want to just update from v29 to v34 but I cant live with music doing this. My last resort would be to just use v29 as I don’t want to lose the state of all my apps and stuff. Music doesn’t skip in Pandora or music palyed through wifi in Zumodrive. It only skips in the default music app and the other music apps. Really frustrating. At first I thought it could also be my metamorph skin but that wasn’t it also(that was back when I was trying to update from v29 to v30 other versions with the same issue…) it always skips to the next song on the list, not fastforward or anything. also sometimes it shuts off and reboots automatically because of the skipping.
I really really wanna update. Any solutions? Ive looked through my apps and cant really see anything that might be causing this. any suggestions would help. Thanks.
Did you flash the memory? It's the first wipe option in the A RA bootloader.
DS36 said:
remove setcpu and autokiller
Click to expand...
Click to collapse
i uninstalled both and then restarted and the problem was gone! i reinstalled autokiller and it works fine(after another restart). but then in installed setcpu again and then it started doing it again right away! without even doing a restart.. So it seems to be the culprit. How is setcpu interfering with it? i had it set on like 748/480 with a couple other profile settings. Also why would it start acting up now? it was working fine with setcpu in v29.
I've been experiencing this problem ever since I've had the phone. More often than not, accessing the Gallery will cause the system to freeze and I have to take out the battery to reboot. I applied the OCLF and it seemed to help for a little while, now this phone is back to it's old tricks. Has anyone else experienced this? Is there something I can do to fix it? I'm running stock btw.
I personally have not seen anyone else post that issue. I had an issue before when pics would not show because Media Scanner was not running... the roms I am on lately seem to resolve that though (back then when I had the issue I used an app in the market to scan my media and then the pics would show).
You say stock, do you mean stock JI6... as in you have done nothing to the phone?
Maybe not an option, but why not try a custom rom and see if that fixes the issue... if it does not, unroot and tell Samsung what's wrong and get a replacement.
I usually hate when people mention getting replacements, but you sound like you have a legit problem and not trying to work the system.
digitaltoddy said:
I've been experiencing this problem ever since I've had the phone. More often than not, accessing the Gallery will cause the system to freeze and I have to take out the battery to reboot. I applied the OCLF and it seemed to help for a little while, now this phone is back to it's old tricks. Has anyone else experienced this? Is there something I can do to fix it? I'm running stock btw.
Click to expand...
Click to collapse
yes, this is a common issue on stock 2.1.1 firmware right now, happened to me constantly, when it does this someone told me that when you open gallery, theres a memory leak bug which opens and then phone can't handle so it freezes.
Flash a custom ROM, i use axura 2.1, so far its been the fastest, most stable for me.
idk if this will work but ask for a gallery.apk from different roms where the leak has been fixed, and then try that, or just flash a new rOM.
digitaltoddy said:
I've been experiencing this problem ever since I've had the phone. More often than not, accessing the Gallery will cause the system to freeze and I have to take out the battery to reboot. I applied the OCLF and it seemed to help for a little while, now this phone is back to it's old tricks. Has anyone else experienced this? Is there something I can do to fix it? I'm running stock btw.
Click to expand...
Click to collapse
i had this problem when i just wantes to use stock with root. this is actually common problem with ji6 roms that still use the stock gallery apk.for some reason the stock gallery in ji6 always tends to lock up.there's a fixed version of the apk floating around somewhere.
I had this same problem with JI6, but it went away when I updated to the leaked JK6. This or any recent custom rom should fix the problem for you.
Sent from my SGH-T959 using XDA App
As i said its a memory leak bug, which has been fixed, you should either get a different gallery.apk from newer roms, or get a new rom.
I suggest a newer rom, but its up to you.
If you are running JI6, then this is a common problem for many people.
i had the same problem with my first and second vibrant, i updated to jk6 on number 2 and it went away.
can anyone post the apk to fix this????
Also interested in a the new Gallery .apk.... probably would have to push it using adb? I'm probably just gonna jump right on JL5 tonight.
Hi all! I am running Bionix V 1.2.1 with the dragon kernel5 - all in all, I am very satisfied, but lately I've been running into a few problems that I'm pretty sure I caused during my more reckless period of flashing test kernels (at least, that's when the symptoms appeared). The first and most annoying issue is that the Music Player will play the first song I select without any problem, but at the end of the song, rather than moving to the next track, the app freezes eventually resulting in a force close. Same thing happens with sound player and a gingerbread music app i dl'ed from the market...also sometimes after the watching a video from the gallery. I'm assuming this is because I've corrupted something (perhaps something to do with CorePlayerService?) This sometimes also coincides with issue #2: the notification bar will be inaccessible occasionally, usually accompanied by some general lag, only fixed when I kill and restart launcher.
Now, I know that whatever my problems may be, i would probably be well served to odin back to stock, root, and start over now that I'm done being a jackass--but that seems like overkill, considering how narrow my problem is.
Has anyone else experienced this? (or is that like asking, "i ate some raw, spoiled meat this morning and now I'm violently ill....anyone else experience this?") Does anyone have general insight? Perhaps even a quick fix that obviates the need to spend a couple hours on damage control...?
P.S. if there is already a thread that COMPLETELY covers this, please don't flame me to death....i did at least TRY to find it ;x
This has always been a problem for me since Nero 3. It's the rom not the kernal. I think it's a bad flash. I just odin back to stock and reflash. I tried replacing MusicPlayer.apk in system/app but that still didn't work. I hope someone finds a solution.
Heh...good to know i'm not alone. Also, I don't know if this is at all related, but starting at the same time I noticed quadrant now freezes at h.264 decoding and also had to fc... Guess I'll be re flashing...
Sent from my SGH-T959 using XDA App
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.
So I just recently started having this annoying bug in Google Music on my phone where after each song, the media volume resets to max for the next song. Anyone know why this may be happening or have any similar experience with a bug similar to this?
I'm having the same issue. I think it might be related to my updating from AOKP ICS to CM10/JellyBean without wiping. But everything else is working just beautifully and all my stuff is still there, so I don't want to wipe and am hoping for a different fix for this issue. But so far deleting data, un-/re-installing the app aso. didn't help. Any hints appreciated.
Same issue here. I have recently installed RR JB 3.0.6 running Siyah kernel. Not enough posts to post in that section yet, so I'll start off here