[EDIT]
Update: It seems after a couple of reboots and launches of app manually on watch/phone it seems to be working correctly
---------------------------
I've just reset watch and also ran an update to latest build. I've also recently done a clean install of rom on phone.
Upon getting setting some apps up I've noticed that the Android Wear voice actions seems to be having issues assigning/recognising apps correctly. For example Play Music kept assigning a podcast app and would not let me use Google Play Music unless I uninstalled the podcast app. I've also noticed things like "Start A Workout" and other fitness actions are greayed out and wil not let me assign apps at all, were as start a run is auto assigned to Google Fit and lets me assign others.
Has anybody else has similar issues/knows what's wrong?
Related
Hi all,
I hope this issue has not been raised before, did not find anything with a search.
Sometimes I have the Issue that whenever I try to open the Google Music App, another App is opened (and if that happens, it is that app consistently regardless of how often I try to open Google Music).
If it happens, then it does not matter whether I open Google Music from the App Drawer, from the dockbar, or any other shortcut on the homescreen.
The problem is only fixed when the device is restarted. I went to the apps menu in settings and killed the app that opened (in this case it was the contacts app, in another case Foursquare) when I tried to open Google Music. Google Music was not open and not in the Cache. Still, issue remained until after a restart.
I have not yet found a way to replicate this behaviour in a consistent manner.
I am on 4.0.1, ITL41F.
Any ideas / comments?
Thanks,
Moritz
I had the same thing happen on my HTC Inspire. I think it is a problem with Google Music. My GNex has only done it once or twice.
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
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 ?
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.
Does anyone else have this issue where some apps such as instagram, discord, or twitter not run in the background after clearing the recent apps screen? I have tried re-installing the apps, as well as setting their battery options to unrestricted, but to no avail. Because of this I am unable to receive any notifications from these apps. If anyone has experienced this and knows a fix I would really appreciate help.
i think i have the same issue,
received it yesterday
hopefully we get a global rom soon
The only workaround I have for this is to lock the apps that I want running in the recent apps screen. I don't like it because I have a habit of clearing my recent apps every now and then, but it will have to do for now.
CWJ_93 said:
The only workaround I have for this is to lock the apps that I want running in the recent apps screen. I don't like it because I have a habit of clearing my recent apps every now and then, but it will have to do for now.
Click to expand...
Click to collapse
The same thing happens to me. It does not happen to me with all the apps but I have verified that with several. for example the ExpressVPN app only works for me if I have the app open in "recent", if I close it the app stops working
messages app not working also, i had to install google messages and it's ok
Hi
Go to Device Shield APP /App management
change the setting in App auto Strat and background running.
I will start a new religion in your name. Ty my savior.