Hi all. I've been having a problem with my phone where audio cuts out through the Music app at random times. I can play music through Soundcloud and Mixcloud and Songza and Youtube and Digitally Imported without a problem. I've cleared the data many times on both the Google Play Music and Music applications through the Application Manager. I also tried uninstalling the updates for Google Play Music and still no go. I started to think that it may be just my microSD card, so I tried playing music off my HAM2's memory, with my microSD card ejected, and I still get music stopping at random times. I think I kind of narrowed it down to the Music application, I'm not too sure though. Any help would be awesome.. Perhaps anybody with the same problem? Oh and by the way I had a HAM2 variant and I did the conversion in order to get Lollipop. Other then this problem I don't seem to have any other issues.
yes, this is well known issue, and you can find it, for example, in the 'lets mod' thread in general subforum.
For me, i have tried freezed 'power geniel' system app, I feel the issue is gone, but not sure, will use more time and see.
Xordos are there any negative effects to freezing power genie?
hi, actually looks like freeze 'power genie' has no effect because it is still running. This is same behavoir in JellyBeans. Under JB, this app need to be removed/renamed to resolve missing notification issue(freeze doesn't work). For music pause issue, it is not very freq, maybe I will wait till their official lollipop release. Someone said it is fixed in newer version.
I had this same issue on B309 lollipop. I upgraded to B320 and I have not had this issue since.
xordos said:
hi, actually looks like freeze 'power genie' has no effect because it is still running. This is same behavoir in JellyBeans. Under JB, this app need to be removed/renamed to resolve missing notification issue(freeze doesn't work). For music pause issue, it is not very freq, maybe I will wait till their official lollipop release. Someone said it is fixed in newer version.
Click to expand...
Click to collapse
The best way to disable powergenie is to rename the apk and odex file in the system/app directory. Just add .bak to the end of both.
Updates B320 states that the audio bug is fixed in the changelog.
I actually went back to JB and couldn't be happier. B320 seemed to totally break the system ui when the DPI was set to below 300. That's not usable for me.
ArkAngel06 said:
The best way to disable powergenie is to rename the apk and odex file in the system/app directory. Just add .bak to the end of both.
Updates B320 states that the audio bug is fixed in the changelog.
I actually went back to JB and couldn't be happier. B320 seemed to totally break the system ui when the DPI was set to below 300. That's not usable for me.
Click to expand...
Click to collapse
B321 is pretty good.
kimtyson said:
B321 is pretty good.
Click to expand...
Click to collapse
Have you tried to change the DPI? I lose status bar and nav bar at anything below 300 on b320.
ArkAngel06 said:
Have you tried to change the DPI? I lose status bar and nav bar at anything below 300 on b320.
Click to expand...
Click to collapse
I have not tried to change anything, so far. I am not rooted. I'm testing the pre-release lollipop and staying clean.
Related
Is anyone getting endless force closes after installing the new Google Play Music? I've tried using two different Touchwiz Roms and even CM 10.1 and all of them seem to have issues running the app. Thoughts?
+1 on that issue. I just uninstalled play music for the time being. It was ridiculous the number of times it fc'd on me
Sent from my SCH-I605 using Tapatalk 2
Yea it does it on every device I own x.x
Sent from my SCH-I605 using Tapatalk 2
so it sounds like its an error with the app? I guess it makes sense because it's such a new service but it's also weird that some people are having no issues at all.
also having force closes
On my note running jedi rom, nexus 4 and my tablet. The radio feature works fine on PC but it won't start on the 4 or my tab. The music app itself closes constantly on my note though. I uninstalled the app and reloaded a previous version so I can atleast still listen to my purchased tunes.
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I had the same force close problem on my GS3 only fix I found was to unroot. Once I unrooted it worked fine.
Sent from my SGH-T999 using Tapatalk 2
It's a very strange problem that alot of folks are having, I did take the update and I've had zero problems although they did change alot in this update. Im running clean rom 4.5 with perseus kernel, no overclock or undervolt, idk if it matters what your running it should be stable either way I use it all the time but still getting used to the new look. .
M.A.D.NoTe.||
Looks like the update doesn't like too many songs. Deleted a few hundred and it works.
yeahmann said:
Looks like the update doesn't like too many songs. Deleted a few hundred and it works.
Click to expand...
Click to collapse
How many sings do u have stored
codemansGT said:
How many sings do u have stored
Click to expand...
Click to collapse
I have over 1000. It worked with 400-something.
I have just over 7000 songs. I am on an S3 on T-Mobile. I tried the new Google play music on several roms, included stock rooted and the app was unusable because of the force closes. I reverted back to the old version of Google play music, unrooted, let my music sync, then upgraded to the new version through the play store, and it has been working for 3-4 days without any problems. I rerooted the phone to test and sure enough the force closes came back. I repeated the process stated above and it works perfect again. I am convinced "root" was causing the force closes... At least in my case. Hope this helps.
Sent from my SGH-T999 using Tapatalk 2
Sloopdawgg said:
Is anyone getting endless force closes after installing the new Google Play Music? I've tried using two different Touchwiz Roms and even CM 10.1 and all of them seem to have issues running the app. Thoughts?
Click to expand...
Click to collapse
I was having the same problem and I just found a way to make it work for me.
1. Turn off phone.
2. Eject SD card
3. Reboot
4. Open Play Music and go through the setup making sure that it doesn't crash
5. Turn phone back off and insert SD card
6. Reboot
For me after those steps it is still working.
Edit: Until I put my music back on my sd card.
cmo220 said:
I was having the same problem and I just found a way to make it work for me.
1. Turn off phone.
2. Eject SD card
3. Reboot
4. Open Play Music and go through the setup making sure that it doesn't crash
5. Turn phone back off and insert SD card
6. Reboot
For me after those steps it is still working.
Click to expand...
Click to collapse
I thought the SD Card was the issue too. I've got a little over 3000 songs and I thought it was the loading process causing the FC's so I had done what you post above on 3 separate roms and all have FC'd. It has even FC'd before even launching the application. I have decided to just wait it out and hope that Google solves this issue soon. I have faith in them to get things fixed pretty soon like they usually do. Thanks for the tips though!
Sloopdawgg said:
I thought the SD Card was the issue too. I've got a little over 3000 songs and I thought it was the loading process causing the FC's so I had done what you post above on 3 separate roms and all have FC'd. It has even FC'd before even launching the application. I have decided to just wait it out and hope that Google solves this issue soon. I have faith in them to get things fixed pretty soon like they usually do. Thanks for the tips though!
Click to expand...
Click to collapse
I forgot that I had taken all my music off of my SD card before I did those steps. Once I added it back to my card it started happening again after I refreshed. But it didn't start until near the end of the refresh. It looks like there are certain tracks that it doesn't like, or after a certain amount of music on your sd card it stops working.
+1 on this issue, hope they fix it soon, having to use the touchwiz music player and it sucks.
non-rooted, galaxy s II with 4.1.2, about 3000 songs and 64 gb sd card.
Sloopdawgg said:
Is anyone getting endless force closes after installing the new Google Play Music? I've tried using two different Touchwiz Roms and even CM 10.1 and all of them seem to have issues running the app. Thoughts?
Click to expand...
Click to collapse
This time I'm pretty sure I have the fix. It is definitely working for me. There's a problem with the album art in the mp3's ID3 tags. I'm pretty sure it's only the art from a few of them but good luck finding which ones. If you delete all the album art from all mp3's you should be able to run the app without problems. You'll have to delete all the music from your phone and re copy it. You might have to delete everything you've uploaded to Google then re upload that too, but I'm not sure about the last part. Hope this helps.
cmo220 said:
This time I'm pretty sure I have the fix. It is definitely working for me. There's a problem with the album art in the mp3's ID3 tags. I'm pretty sure it's only the art from a few of them but good luck finding which ones. If you delete all the album art from all mp3's you should be able to run the app without problems. You'll have to delete all the music from your phone and re copy it. You might have to delete everything you've uploaded to Google then re upload that too, but I'm not sure about the last part. Hope this helps.
Click to expand...
Click to collapse
I was thinking the same problem being with album art but I can install Google Music without ANYTHING on my SD card and external SD card and it will still crash. It's very odd so I guess I'm just going to wait until Google pushes next update that will hopefully fix it. I've seen quite a good amount of people complaining so I'm sure Google will look into it.
Sloopdawgg said:
I was thinking the same problem being with album art but I can install Google Music without ANYTHING on my SD card and external SD card and it will still crash. It's very odd so I guess I'm just going to wait until Google pushes next update that will hopefully fix it. I've seen quite a good amount of people complaining so I'm sure Google will look into it.
Click to expand...
Click to collapse
I saw some people say yesterdays update fixed the problem but I'm not sure since I already wiped album art. If you have uploaded music to Google with album art it doesn't like that could still be causing the problem.
cmo220 said:
I saw some people say yesterdays update fixed the problem but I'm not sure since I already wiped album art. If you have uploaded music to Google with album art it doesn't like that could still be causing the problem.
Click to expand...
Click to collapse
Wow. I have not even tried updating for the past few days. I just updated, streamed a few songs, and smoothly went through my library without a single FC. Looks like they have updated and it is working just fine now for me! Thank you very much! haha
Sorry if this thread already exists.
You have no idea how happy I am this ROM exists!! But I cannot get SMS working. I get FC's on every SMS app I try including Hangouts. Anybody else getting this and/or have a remedy? Thanks
I was about to post the same error here, I have an Amaze with Videotron, S-Off, Super CID, HBOOT-1.93.2222 (JuopunutBear), TWRP as a recovery.
I tried everything, I tried different Gapps, I also tried without installing Gapps, I tried sms apps from the Play Store and Hangouts too. The only thing I haven't tried is formatting my internal SD card. (it was a clean install, all formatted and cache cleared). I also tried switching to ART but I had the same problems.
Everytime I try to just open the sms apps, the app crashes. I managed to see the error once and it was something about SQL but it might be a misinterpretation from my part.
Calls, 4G and WiFi were all working perfectly too.
After some research on Google, I tried installing busybox, xposed framework and uninstalling Voice+, but nothing works. The basic messaging app just closes without any kind of message and other apps show that it stopped working.
(I tried the Evervolv rom 4.4 and SMS were working on that one, maybe it's a setting with my network type as I am on Videotron in Canada and it is using AWS, maybe a setting under *#*#4636*#*# ??)
I want to contribute and sen some log of that error, how can I do that? I am familiar with roms, kernels, etc but not that much with logs... I tried many roms before and never got that specific problem...
Thanks to anyone who can help with this issue!
It's not just you SMS simply doesn't work on this rom and I was surprised to see that no one else pointed this out in the original thread. The default Messaging app closes immediately when you try and open it. Other SMS apps also crash either immediately upon opening them, or when you try to send a message (hangouts & SMS Pro for example). This is the only thing keeping me from using this amazing rom as my DD.
I have the same exact problem with SMS- will try the evervolv 4.4 though was really looking forward to CM11
Edit: also didnt have any other problems with the rom except for the black boxes and the camera
Let's hope there is a way to fix it!
I would post the question in the official thread but I do not have enough posts to do so unfortunately
Heck I couldn't even try SMS due to the black box issue, that's why I didn't mention it in the original thread.
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
anybody get the SMS working on this ROM so far?
pbergonzi said:
For those with the black box issue--are you using the correct gapps?
In olden days there were some issues with some google things not working, and people uninstalling the ones that came in gapps and downloading them fresh from the play store.
Have you gone into recovery and fixed permissions?
Again, in days of yore, this might straighten some things out.
Is it possible that black-boxing has something to do with CPU frequency, and is it possible to tweak up the speed through developer options and lose the boxes?
I haven't tried this rom yet, as I'm currently sticking with the stable(r) cm10.
Good luck.
Click to expand...
Click to collapse
The black box issue has nothing to do with GPU or CPU speeds. There are discussions on the dev threads. The issue affects other legacy devices on various KK based source builds, not just Amaze and CM. The consensus is this seems to be related to the default browser which has changed in KK. This would also explain why it effects other gapps too.
MS92 said:
anybody get the SMS working on this ROM so far?
Click to expand...
Click to collapse
Not that I'm aware of.
Media Issues
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
ranwal said:
The ROM is pretty good for the most part.
I just have this problem where Play Music gives this error, "Cannot play the music track you requested"
I clear my media storage and try to rescan my SD card but none of the apps work. They all crash.
Is there anyway to fix this?
Click to expand...
Click to collapse
Maybe app settings for the app and Erase App Data?
can i get a link for the updated adreno drivers? thanks!
865DETH said:
can i get a link for the updated adreno drivers? thanks!
Click to expand...
Click to collapse
Yes you can its on last three pages of orignal thread you also have to sign up for that
Sent from my HTC_Amaze_4G using Tapatalk
as the OP says and i quote that only non working things are
1. camera exposure
2. tethering
but as the thread goes ahead we read more prolems/bugs
May i ask what is the current status for bugs/not working and other issues and what has been fixed and any other stuff we should flash over the ROM like driver, may it be upoaded to the OP for ease as its reall hard to search for those things on mobile app. thank you and good luck.
Anyone else have issue disabling their microphone while in a call? I tried with both the speaker phone and regular handset mode, the "no mic" icon enables but my caller can still hear me. The Hold button seems to work fine though.
FYI, it took a while for the battery to figure itself out. I wiped the battery stats before flashing everything and the first few days I got a lot of jumping battery levels. I let it charge all the way down as much as I could then rebooted and did a full charge and rebooted again and then full charge again. That seemed to reset the battery level to the correct state.
I also , enabled Device/GPS only for the location detection other wise the google services at 50% or more battery.
I'm running the 2014-02-16 build, with the updated video drivers.
Camera is not working
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Any updates for the camera isssue??
Shahxz said:
I have also installed this pacman rom 4.4.2. all is well instead of camera.
Click to expand...
Click to collapse
Since PAC uses the CM device tree for its source any issues with CM will also be evident in PAC. Until the CM devs are able to resolve the camera exposure issue it will exist in both ROMs.
Librastar said:
Any updates for the camera isssue??
Click to expand...
Click to collapse
Think about your question for a minute. Have you seen any recent posts in the CM dev thread indicating an update which solves this issue? If you had just taken a moment to look at the dev thread instead of posting this you would have answered your own question. It's not like the CM-11 thread is incredibly long, it's only 28 pages total. This post is just laziness on your part and an unnecessary waste of bandwidth.
is there any alternate app in the market, i tried couple of apps but nothing useful
@Odysseus1962
If I were to compile AOSP, which variant would you suggest for me to build?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Hi all,
I am using GingerBread for Samsung Note 1. My music player no longer updated the playlist when I added new songs to the phone.
I guess there must be crash in the updating of the playlist database. Any method that I can use to determine how the crash happened and then I can try to fix it? (I rooted the phone )
Thanks.
peterhon said:
Hi all,
I am using GingerBread for Samsung Note 1. My music player no longer updated the playlist when I added new songs to the phone.
I guess there must be crash in the updating of the playlist database. Any method that I can use to determine how the crash happened and then I can try to fix it? (I rooted the phone )
Thanks.
Click to expand...
Click to collapse
First off...Gingerbread?! Really?! There are stable versions of Jelly Bean for your phone! Secondly, are you using the stock Samsung music player, or another app. But I would go into Settings / Application Manager and clear the data of your music app. Hopefully once you restart it, it will rebuild your playlists. That or your media scanner isn't working that well. Typically when you reboot, it should rescan the media on your phone and then it'd show up in the app.
Thirdly... Gingerbread?! lol Please, do yourself a favor and update! Not only will you have better performance (and likely battery life), but you will have access to more apps, lots of new features, as well as a more secure / safer system.
As far as telling what happened, you would have to get a logcat going when the issue happens (though I am not so sure there will be anything obvious for this sort of thing). Easiest way to do logcats are probably just on the phone with an app like alogcat.
es0tericcha0s said:
First off...Gingerbread?! Really?! There are stable versions of Jelly Bean for your phone! Secondly, are you using the stock Samsung music player, or another app. But I would go into Settings / Application Manager and clear the data of your music app. Hopefully once you restart it, it will rebuild your playlists. That or your media scanner isn't working that well. Typically when you reboot, it should rescan the media on your phone and then it'd show up in the app.
Thirdly... Gingerbread?! lol Please, do yourself a favor and update! Not only will you have better performance (and likely battery life), but you will have access to more apps, lots of new features, as well as a more secure / safer system.
As far as telling what happened, you would have to get a logcat going when the issue happens (though I am not so sure there will be anything obvious for this sort of thing). Easiest way to do logcats are probably just on the phone with an app like alogcat.
Click to expand...
Click to collapse
really strange..
https://dl.google.com/dl/android/aosp/mantaray-lmy47d-factory-63eade7f.tgz
Have fun!
Hm, it's been sitting on "sending bootloader" for a while now. Should I be worried?
So far feeling very good and fast, nice update
Rand Brittain said:
Hm, it's been sitting on "sending bootloader" for a while now. Should I be worried?
Click to expand...
Click to collapse
Welp, doing it over on a different port and cable seems to have handled it.
Flashed it.
Might be placebo but it seems much smoother.
Also the recent bug is fixed and the toggles in the Account Sync have been changed.
Images flashed......"optimizing app 98 of 154" so first 5.1 boot should be soon.
Anybody tested this bug?
http://forum.xda-developers.com/nexus-10/help/android-5-0-sound-problem-charging-t2939672
tylerdurden83 said:
Flashed it.
Might be placebo but it seems much smoother.
Also the recent bug is fixed and the toggles in the Account Sync have been changed.
Click to expand...
Click to collapse
What about wifi performance and the audio bug wile/straight after charging/docked?
I don't understand what the bug is. I never experienced it before, but I can try to replicate it in 5.1 if you explain what I am supposed to do clearly.
isarebe said:
I don't understand what the bug is. I never experienced it before, but I can try to replicate it in 5.1 if you explain what I am supposed to do clearly.
Click to expand...
Click to collapse
What I got is, sometimes when starting the N10 while charging, there is no sound at all, and I have to reboot the N10 without charging to get the sound back.
I tried with 5.1 and so far, 5-6 times, no bug, but as I said is only happening sometimes before...
Audio Bug Squashed?
It looks like 5.1 has fixed the audio bug. It has for me at least.
Anyone experience lag when pulling the notification tray on the home screen?
matejilic said:
Anyone experience lag when pulling the notification tray on the home screen?
Click to expand...
Click to collapse
Using the default Launcher3, not really. The Google Launcher lags when pulling down the tray, and lags all other animations for that matter. It always has since 4.4, but I put up with it because I like the GEL. It doesn't lag anywhere else thankfully, so it's your call.
On March 10th I did a factory image update to 5.1 but did not wipe user data on both my Nexus 10 and 5.. At least for me, this is the best version of Lollipop I've experienced.
My Nexus 10 was more stable than my Nexus 5 on any 5.0.x release but it seems that all the issues I'd been experiencing are resolved. On 5.0.x my Nexus 5 experienced the memory leak causing UI slow downs, odd reboots, total freezes needing power cycles and frequent disconnects of both WiFi and my cell network.
Android 5.1.0 did break the K9 email reader but that was fixed this morning and Jota+ SMB support currently is not functioning. On the Nexus 10 my battery stats still does not update always showing 100% charge even when its been off the charger for hours. Its been like that for a long time including with KitKat.
I am rooted and use a number of app beta versions including Nova Launcher, GMD Gesture Control and GMD Auto Hide Software keys, Viper4Android and they all worked before and after the OS update. That is a little surprising as previous Lollipop 5.0.x updates had broken more apps when they were first released. For the first time in a long time MX Player Pro still worked after an OS upgrade.
This was what the Lollipop release should have been. I'm happy especially as my Nexus 5 is as reliable as it was with KitKat.
That's great. Smooth
My 5.02 Nexus got an OTA to 5.1 last night (I'm in the UK). Everything seems fine and I am really happy that I have a tablet that is still supported.
Alan
Is anyone getting a screen freeze? Basically the screen just freezes but the unit seems OK ie it's not a system crash. It needs resetting to work again.
Sent from my Nexus 10 using XDA Free mobile app
Warren_Orange said:
Is anyone getting a screen freeze? Basically the screen just freezes but the unit seems OK ie it's not a system crash. It needs resetting to work again.
Click to expand...
Click to collapse
Sometimes, but always related with Chrome playing videos.
Hi.
I have narrowed it down to when i bring up google search with the swipe up gesture. Once on google search the screen becomes unresponsive. But a can reboot by pressing the power button and choosing 'reboot now'. I may try and reinstall it.
This only started happening with 5.1.
Sent from my Nexus 10 using XDA Free mobile app
Warren_Orange said:
I have narrowed it down to when i bring up google search with the swipe up gesture.
Click to expand...
Click to collapse
In my case I have that feature replaced by a more useful one: a handy launcher:
https://play.google.com/store/apps/...store&pcampaignid=APPU_1_cw0YVbWgJ8XTU_77gYgP
It never freezes.
For context, I'm running lineage (19-20220824-NIGHTLY-dre) and this issue happens on every single camera app I've tried.
If I record a video let's say like a 2 second recording and then go to open that video the clip suddenly is an hour long with basically the entire hour being a single frame and the last 2 seconds being the 2 seconds I recorded. What's even weirder is the audio from the video plays during the first two seconds and then doesn't for the remaining time. Overall really weird and frustrating and I've spent hours trying to figure out what would cause this to no avail. Additional most gallery apps won't even open the videos recording and no pc can open them either. Any ideas?
Have you tried update Lineage? It's most recent update is 9/21 it looks like your about 4 updates behind. Not sure if it'll fix your issue though as I did not use camera while using Lineage and have since gone back to stock due to a display bug.
Edit: If you do want to update it SHOULD be fairly simple. You just go to settings>system>update and it should pull whatever the newest update it and install in the background. Note that even though it shouldn't cause any errors, there's always the chance it will so just be aware and ready.
Link575 said:
Have you tried update Lineage? It's most recent update is 9/21 it looks like your about 4 updates behind. Not sure if it'll fix your issue though as I did not use camera while using Lineage and have since gone back to stock due to a display bug.
Click to expand...
Click to collapse
Yup just updated to the most recent version, still same issue
Looeelooee said:
Yup just updated to the most recent version, still same issue
Click to expand...
Click to collapse
Ah ok, sorry that's all I got. You could always submit a bug report on the Lineage gitlabs and hopefully someone gets to it.
This is why I stick to US OEM Stock rom.
I can de-bloat it and EVERYTHING works.
scanman0 said:
This is why I stick to US OEM Stock rom.
I can de-bloat it and EVERYTHING works.
Click to expand...
Click to collapse
You got a debloat list or something you follow? I could go for that see if smooths stock a little when playing pokemon go.
I have the latest LIneage, with the same problem, and am completely lost with what it could be. Recording videos in Snapchat works normally, but the stock camera, GCAM, and the GrapheneOS camera all have this issue, probably because they all use the Camera2 API.
I encountered this problem today but the uploads on Google photos came out correct (when I 'free up space' )
I am having this issue as well, just checking to see if anybody might have discovered anything