Google Music 0.89TB bug. - Sprint Samsung Galaxy Note II

I am getting this weird bug where google play music shows it is using 0.89TB of my storage, but it actually isn't (obviously). And my phone functions as normal with 8th free space. I have 3 screen shots showing this bug.

Related

Issue with stock Music Player using available RAM!

Hey Folks,
I have an issue with the built-in stock Music player constantly taking all of the available RAM, which causes Android to start killing other processes like the launcher (Apex Pro), Tasker, nearby devices service (force closes occasionally), etc. It is very odd. I have tried several attempts to remedy the situation. I have, so far, cleared the Media Storage data, cleared the Cache partition from the boot recovery menu, have music on built-in storage and un-mounting my MicroSD card, to which none of these efforts helped. It seems like the Music Player app has a memory leak, which I am wondering if this was introduced in 4.3. I did not see it listed yet in the 4.3 issue threads, and not really sure if 4.3 is the culprit. I upgraded to the S4 from an S2 recently and a week later the official 4.3 upgrade was available. Thus, I do not know if this issue was happening in 4.2.2.
The interesting thing is that this leak or loop is occurring whether or not I have music on the device. So, to be clear, the issue specifically is when I launch the Music Player and then go to Task Manager to see the used RAM, the RAM will just continue to get used up until it reaches about 1.70GB or so out of 1.78GB available and then Android will start killing other processes to accommodate for more memory. This is when Apex and /or Tasker and other services start getting the ax. What's more, if I kill the Music Player (either right away or later), the memory continues to be consumed until it reaches about 1.5GB - 1.6GB and then finally releases and drops to 700MB - 900MB.
I am on a stock ROM, non-rooted and I have also confirmed this issue with my wife's S4 as well. We can use Google Play Music with no issues, but prefer the stock player if there is a solution to this "memory leak" or other situation that is causing the issue. If anyone has some insights as to what this issue is and a fix, please let me know. Also, if anyone can launch the Music Player and watch the RAM in Task Manager to confirm that this is or is not occurring on other S4s out there as perhaps it is an issue that some may not have noticed. In fact, my wife has been using her device in the car for a couple of weeks and streaming with Bluetooth and not noticed this was occurring. However, if she were to have music and use Maps/Navigation at the same time with this issue, Maps will get killed along with other multitasking tasks. I happened to noticed this behavior when I moved my music on the device and was playing around with the player, when I saw that Tasker restarted itself and then shortly after the nearby devices service forced closed and the music app got real sluggish. I then started observing the RAM usage with the launch of the player and realized why apps were closing. The funny part is that the music plays fine and never dies, it just kills everything else in its wake.
Any insight to this will be greatly appreciated. Also, I have been scouring the forums and Google in general to see if this has been mentioned and have not found this exact situation. However, if I did overlook a thread/post that has this as a known issue, please let me know what that link is. Thanks.
First off, damn. You might want to take a refresher course on how to say what you mean without all the extra words. You wrote a book man. 90% of what you typed is unnecessary. Nobody wants to read all of that and must won't even entertain a response. Just a friendly heads up.
Now, are you sure that the RAM is being taken up by the music app and not a combination of apps/processes? The stock task manager isn't very good for situations like this so you'll need to download a system monitor. There are quite a few out there, take your pick.
Could be that when you open the music player the media scanner is eating up RAM along with other processes. Those together are killing your memory. If that's the case you need to create a .nomedia file to place in the folders on your internal/external memory. Also, do you have any other music or media apps installed?
Figure out those then post back. You might try uninstalling all your apps then reinstall them one by one ( backup first). Yes, it can take a while if you have a lot but once you install the culprit - you'll know it. Hope that helps.
SOLVED!!
Ah, thanks for the heads up! Sorry about the long-winded post, I just wanted to convey the issue and what I have done so far. In future posts, I will be much more concise and to the point.
On a good note, I have solved my issue and found that if you disable/freeze/uninstall apps but still want to use the built-in music player, there is a conflict if you disable S Voice. I was going through the settings in the music player and noticed the voice control feature (which was unchecked), but clearly the player still wants to talk with or "see" S Voice out there. I took a shot in the dark and once I re-enabled S Voice, the gobbling of RAM from the music player launching stopped. Yay!!
Not solved!
Well that victory was short lived. That seemed to have only worked for about 10 minutes and it is back to the same memory gobbling issue when the player is launched. I reactivated Google Play Music and am using that with no issues, so it seems that will have to do.
Well that was all I had. I don't use the stock music player since I stream with Google Music.
You might look in the app store for an app to replace the stock one. Then uninstall the stock app so you don't have the issue anymore.
Sent from my SGH-M919 using xda app-developers app

Music app not working

I recently bought one of the unlocked fire phones and added google play, all the services, etc. to it and so far everything has worked fine. i tried to launch the music app today for the first time and it wont open. the phone does not respond at all when i touch the music app icon, so i download prime music app and tried it but it crashes right after launching. this is the only problem i have experienced so far and was wondering if anyone else has had a similar problem or knows how to fix this problem. thanks!
I also just recently bought one of the unlocked phones and had a similar problem. The first night I got the phone I transferred a bunch of media from my old phone including my music and was able to use both the music app and Prime music app. Then the next day both apps went dead. I tried all the usual stuff like clearing data and cache, reinstall prime etc. but nothing worked. Unfortunately I had to resort to a factory reset on the phone to fix it. Ever since then (around two weeks) they have been working fine.
My only complaint is for some reason the default music app doesn't show album covers for some of my music while they all show in Prime music.
I know why the music apps stopped working now! After adding the Google Play Store there is an update offered for Amazon Prime music. This update will kill Prime and the regular music app on the phone. I just installed the update a little bit ago by accident and sure enough both apps went dead. Went back to the play store and my apps and clicked uninstall on Prime Music and it uninstalled the update and now both are working again.
Same happened to me. Just make sure to disable auto-updating within google play store to prevent it from happening again.
what version of the app does work? can someone link this app to me ?

[Q] Problems caused by Google Play Store

So I'm having two pretty major problems with my phone.
1. The Music app doesn't work.
2. My screen goes blank during a call, and I cannot hang up
1. When i tap the Music icon, it "bumps," but nothing happens. If I use Firefly to check a song, and click the store link, it will open, and I can buy the song. But if I try to go to my media from there, the app crashes.
2. I'm assuming my prox sensor is locked or something? As soon as I begin a call, the screen goes black. The only way I can hang up is to hold the power button for 40s to force a shutdown, or if my headset is handy, I can switch it on and that will reactivate the screen.
I have contacted Amazon support about issue #1 and the first question the support girl asked was if I had installed any third-party apps through the Google Play Store. She said that she had seen this issue before and that was always the culprit.
Has anyone else experienced these issues? Any way to track down what app is causing them?
The easiest way to figure it out is to uninstall Google Play Store for now, and any other apps that you might have installed one by one, and see which ones makes a difference.
FYI I have the Play Store installed with a bunch of my usual apps and my Music app works fine.
Amazon music app will stop working if you update the app through Google Play. Go to your setting in Google Play and select "Do not auto-update apps". Un-install the music app through Google Play and the Amazon music app should start the work properly, if not re-install the music app through Amazon.
If you have a screen protector without a hole for the proximity sensor that is located below the front camera then that is the reason why the screen turns off and you are not able to hang up.
jack9955 said:
Amazon music app will stop working if you update the app through Google Play. Go to your setting in Google Play and select "Do not auto-update apps". Un-install the music app through Google Play and the Amazon music app should start the work properly, if not re-install the music app through Amazon.
If you have a screen protector without a hole for the proximity sensor that is located below the front camera then that is the reason why the screen turns off and you are not able to hang up.
Click to expand...
Click to collapse
Thanks for the advice!
I do have the Google Play Store set for manual updates, but it is possible that I accidentally did an "Update all" at some point. I know I did it once and screwed up Netflix, but I was able to just delete and reinstall from Amazon.
Unfortunately, since it's a Fire Phone, Amazon Music is not available in the app store, it's built in. Does anyone know of any way to "reinstall" the app other than restoring the phone?
Regarding the proximity sensor, I don't have a screen protector, and I forgot to mention that it's not constant. Yesterday, I was able to make a call normally. And often, rebooting will solve the problem temporarily as well.
If the Amazon Music was accidentally installed through Google Play it may still be on your phone. Use ES File Explorer to see if you have Amazon Music installed in your User Apps and System Apps. If so then use ES File Explorer to un-installed the music app that is in your User Apps.

Bugs in Experience Rom 7

Experience Rom 6 was superb but version 7 is full of bugs...Let me point out the bugs,please
Google play services are not working properly.Severe problems with play store hence
Security and Fingerprint option in settings menu doesn't work.When clicked it immediately takes to home screen.
Some applications are not turning on.They spurts up and close all of a sudden...
Music continuous to play even on calls...
Etc Etc...
Kindly fix these issues and make the Rom awesome...
sibikallikkat said:
Experience Rom 6 was superb but version 7 is full of bugs...Let me point out the bugs,please
Google play services are not working properly.Severe problems with play store hence
Security and Fingerprint option in settings menu doesn't work.When clicked it immediately takes to home screen.
Some applications are not turning on.They spurts up and close all of a sudden...
Music continuous to play even on calls...
Etc Etc...
Kindly fix these issues and make the Rom awesome...
Click to expand...
Click to collapse
Post in the respective thread and not here

Question Google photos bug?

Hi all,
Got my Pixel 6 Pro and while battery life has been rubbish but is now settling, I have a weird bug with Google Photos.
I can't access the "memories" properly as every time I click on one I just get a black screen. If I leave the screen on, after about 2 minutes it will show up but God knows what is happening in-between.
I have also noticed that some photos all taken on the same day show up as multiple days on photos. It's fine if I look in a browser Weird as hell. I've tried to Clear cache, uninstalled, reinstalled, cleared data.
Is anyone else having similar issues? There's a Google questions thread with the same issue and it's not been solved yet. Any ideas?
I seem to have the same problem. My device runs noticeable warm. Google photos lags crazy and the media storage app (you have to show system apps) seems to use 20GB storage. Something is wrong. Were you able to fix this?
I ended up speaking to Google over chat and they sent me a new device but it's got the same issue. Accessing memories still gives me a black screen.
Maybe this is some weird Google Photos caching thing. I'm gonna see if it settles after a few days
I haven't had these problems (yet) and I've been using Google Photos a ton since I got the phone last Wednesday. Apps up to date? On the .036 OTA?
Yeah apps are all up to date and rocking the 0.36. Weird.
@kiz84 could you check what your "media storage" app shows as user data? mine shows 20.78GB that's insane.
Where is the media storage app?
settings -> apps -> all apps -> three dots and "show system" then search for "Media Storage"
my memories works fine
device doesnt run warm on google photos
but my user data for media storage is 28.10gb
thats about 10gb of video and 17gb of photos. A quick check shows the video size to be about right. im not going to count up the images sizes
Thanks! It's 18.55 GB!
Just connected my phone to my PC and yes I do have over 20gb of media on the device !
I think the media size is ok because I have a lot of WhatsApp stuff in there too. Memories sometimes appear and sometimes are just blank. If I click on them, they just appear black. Weird. Must be a bug surely.
@wilbur-force in case you're still having this black screen issue with memories, it seems to have solved itself. I didn't do anything tbh but now they are working fine
Sorry, wrong person I meant @Air ! Please see above

Categories

Resources