Database Users

[Q] Timeout for music player PowerAmp

Hi,
I'm sure I can find settings to regulate timeouts of programs. Lately I gave PowerAmp a try, very neat music player, but when my screen times out PowerAmp does aswell after 5 - 15 mins. First, the program was in my "force close" list in my task manager. I took it out but it still closes.
Somebody?

My phone had the same problem,
took me ages to find out what was wrong - all those google searches paid off tho!
just go to:
Settings > Applications > Running Services
and then delete the original Connecting Music player service...
and if that still doesnt work,
deleting the google listen service may do the trick
let me know if it works

I haven't had the bug for a while but this is a good clue. Thank you so far, I will update here once I tried it out.

Hello,
I'm actually facing the same problem, no matter the player I'm using, the music shut down a few minutes after the screen goes dark.
How do you managed to get rid of the "Connecting music player"??? (called "Lecteur de musique connecté" in my french phone)
I found it in the Settings > Applications > Running Services
but I can't uninstall it (button is disabled).
Please help, thank you

Hi,
well I have not been playing music with PowerAMP lately. But to get rid, or better freeze the program, I guess Titanium Backup would do the job. Why don't you try it out to freeze the native music player with it.

Thank you for your response.
Titanium backup needs my phone to be rooted, so I opened z4root and use the temporary root. A few minutes later, white screen and then it says "temporary root applied. You are now rooted until your next reboot"
I ran Titanium backup which said again that my phone is'nt rooted or that busyBox is'nt installed, but it is.
So, I ran busybox (1.17.1) which says that the phone is'nt rooted too.
So it seems to me that I screwed up with z4root but how?
I don't want to be permanently rooted.
(I will look for an answer on this forum as well)
Thank you

I was having trouble with all the music players crashing as well. I rooted, froze (with Titanium Backup) the Connected Music Player (and other motoblur stuff) and I don't think I've had any trouble ever since with my preference - Cubed player.
goldensgui: I saw somewhere else on these forums that temp root doesn't really work for MM2 - but you can unroot your phone anytime - I do have the option to undo the permanent root (not sure if it works [correctly])

Well, thank you dymonaz, I've followed your advice and rooted my MS2.
I had to root it twice because the first try froze my phone (I waited more than 30 minutes staring at the rolling icon ^^) and I reboot it
The second try was a success (only 2 minutes)
Then, I had no problem with Titanium Backup.
I froze the "Connecting music player" with it and a few motorola's stuff like TV channels etc.
But this didn't solve my problem. I restart my phone (who know's), but no change. So I uninstall and reinstall my player for the nth time and this time IT WORKED and I'm currently using it.
I hope it will last.
Thank you all for your help

I'm afraid I was wrong The fact that it didn't crash for almost two weeks after rooting/disabling motobloat didn't solve the problem, as it crashed again, with the same issue as I was having before:
AudioHardwareMot(1110): AudioStreamOutMot: standby called
AudioHardwareMot(1110): Output 0x12480 entering standby
AudioHardwareMot(1110): Closing Output device
Click to expand...
Click to collapse
Go figure

It really sucks.
It does'nt work anymore and I don't now why.
Frustrating
dymonaz, how did you manage to get this log?

I was using OSMonitor (from the Market) - it has a log viewer.
It requires a lot of scrolling to find these messages, but after reviewing all the other messages for around a few minutes before and after the crash, there was nothing else that made sense to be the cause, so I ruled them out and figured these are the ones...
I have no idea who "called the standby" or why, but there's a very poorly documented standby() method AudioHardwareInterface in Android source code. Didn't have time to dig deeper yet.

I found that, whatever the player I'm using, every time it shuts down.
02:07:07.100 Kill com.maxmpz.audioplayer (pid 5555): provider com.android.providers.media.MediaProvider in dying process android.process.media
Does someone have an idea?

Do you guys put the gallery in the auto-kill list in task manager?
I read a post from other forum long time before, I remember they found out that excluding gallery from auto-kill list would work!
I personally tried to put gallery into auto-kill list before(I forget it will shut down the music player). after I exclude it, the music player never stop unexpectedly again
have a try!

I've got the same problem and thats so bad.. -,-

You were right about the gallery put in auto-kill list, WongJames.
I came with the same conclusion removing one by one the applications in the list.
And it appears that the gallery shares the same provider with the music player.
Sorry about the delay and thank you.
(One new weird thing is that gmail doesn't sync anymore since my player is back)

i didn't understand one thing: i have to put the gallery.apk into the black-list (of which program?) or put it out the black-list?

skaburn said:
i didn't understand one thing: i have to put the gallery.apk into the black-list (of which program?) or put it out the black-list?
Click to expand...
Click to collapse
DO NOT put the stock gallery into auto-end list of ANY task manager/ task killer
And I found out one thing, freezing the stock gallery in titanium backup would not shut down the music player
I used to use Quickpic, so stock gallery is useless to me

I must say that ever since I upgraded with the 2.2.2 SBF, I haven't had a single crash.
I do have all the crapware frozen: http://forum.xda-developers.com/showpost.php?p=11180030&postcount=17

Good to hear that. At least Moto fixed that.

WongJames said:
Do you guys put the gallery in the auto-kill list in task manager?
I read a post from other forum long time before, I remember they found out that excluding gallery from auto-kill list would work!
I personally tried to put gallery into auto-kill list before(I forget it will shut down the music player). after I exclude it, the music player never stop unexpectedly again
have a try!
Click to expand...
Click to collapse
Thank you WongJames, this is my first post in this forum, and the don't-auto-kill gallery-advice actually works for my MM2

[Q] Lollipop 5.0 aggressive background app quitting

I'm on 5.0 with Xposed and the ColorFade Memory Leak fix. However, it seems that Lollipop is still force closing background apps too quickly. I play Hearthstone a lot, and I used to background it to go on chrome or respond to a text message or something in Kitkat 4.4 with no issues. Now on 5.0, it will close very quickly. I even hit home sometimes and went right back into the app without doing anything else, and saw that it had closed instantly. Is there any fix for this, or do I just have to wait?
I also noticed that when I was using Google maps and Spotify, then opened Waze, the first two would force close as well. This wasn't an issue on KK 4.0 either.

have the same issues on the stock firmware

I'm on tmo and I have the same problem. it's with stock and AOSP. I can't run pocket cast and anything else for fear of pocketcast (or google music for that matter) closing. I wonder if there is a way to increase it's priority so lollipop won't close it.

xcom923 said:
I'm on tmo and I have the same problem. it's with stock and AOSP. I can't run pocket cast and anything else for fear of pocketcast (or google music for that matter) closing. I wonder if there is a way to increase it's priority so lollipop won't close it.
Click to expand...
Click to collapse
I heard that TouchWiz by Samsung wasn't supposed to have this issue even though all other flavors did, but considering I'm having it, it's not the case.
There's a thing in the Xposed module, App settings, called resident which allows an application to be forced/higher priority in memory, but I find it either doesn't work because lollipop's force close background apps is too strong, or it only makes the background apps stay a tiny bit longer.

Update: I found out today that my issue was disabling Touchwiz's DVFS in the Wanam Xposed module. Re-enabling it fixed all my issues it seems.

Spartan117H3 said:
Update: I found out today that my issue was disabling Touchwiz's DVFS in the Wanam Xposed module. Re-enabling it fixed all my issues it seems.
Click to expand...
Click to collapse
Wow, is that what's been happening? I've been having this same problem on my T-mo Note 4 N910T (Lollipop 5.0.1) with apps aggressively being killed. I've been pulling my hair out because I had no idea why. After seeing your post and disabling the DVFS killer I no longer have this issue. Overlooked it because it just wasn't in my list of things that would be causing it. Thank you!

Default app triggered by Bluetooth

When I enable bluetooth on my S5 in my car, it auto syncs with my Ford Sync systems, so I can play my stuff through the car speakers. When connected, it auto triggers an app and plays the audio straight away. Is there anyway to select which app gets automatically triggered to play? I can't see why its choosing one app and not another.
Thanks,
Jon

Have a look under
Settings>>Applications>>Default Applications.
If your bluetooth app is listed there, press the 'clear' button next to it.
The next time you start bluetooth audio, you'll be prompted to select which app you want to use.....
http://i.imgur.com/rVnFwJM.jpg

There is nothing under Default Applications. The app in question is Smart Audiobook Player. Its so annoying because I want my podcast player to auto start, not Smart Audiobook Player. Surely there is a way to stop this?

Is this a 'system' or 'user' app?
And do you have root access?
http://i.imgur.com/rVnFwJM.jpg

I do not have root access. Not sure what you mean by system or user app. is there a way for me to check?

Did you install the app yourself (user) or did it come preloaded (system) on the phone?......
http://i.imgur.com/rVnFwJM.jpg

I installed it myself. Its Smart AudioBook Player.

Uninstalling this app *should* clear any default startup actions......
Then re-install it as normal.
The next time you enable Ford sync/bluetooth, you *should* see a dialogue box prompting you which app to choose for the job.
If you don't see this, and this app still auto starts, then it might be worth looking in the app settings to see if this auto start can be prevented......
These are the only options I can think of.....If they don't work, I really don't know what else you could try......
Edit.....is 'Ford Sync Systems' an app on your device too?
If it is, there may be something in that apps settings that is auto-activating the other app......
http://i.imgur.com/rVnFwJM.jpg

Problems getting Viper4Android running with Spotify on Galaxy s6 edge+ (SM-G928F)

hey guys,
during the past two days I tried to get Viper4Android FX running on my Galaxy s6 edge+ (SM-G928F) with headphones. With help of this post http://forum.xda-developers.com/galaxy-s6-edge/general/viper4android-complete-setup-guide-neon-t3141316 I finally got the correct driver status (Neon enabled: Yes, Enabled: Yes, Processing: Yes (while running a player)).
For PowerAmp it works properly but not so for Spotify! Like I said Viper4Android shows "processing: Yes" but there is no difference in sound. Even if I change what ever I want. If I do the same in PowerAmp you can hear the difference instantly. That's why I think it isn't working for Spotify.
I checked the Equalizer setting in Spotify and got redirected to Viper4Android (I guess how it should be). I deinstalled the drivers and reinstalled, same problem. I tried the Fx compatible mode but there is no sound after a second but spotify is still "playing". I cleaned cache/davlik cache, deleted all data of the spotify app and of course I freezed the apps SoundAlive and AdaptSound with TitaniumBackup. I tested freezing Google Music and PowerAmp as well but still the same problem.
So could you guys help me fixing this ****?
Thanks
EDIT: Perhaps I should mention that when I moved the com.vipercn folder from /data/app to /system/priv-app the app wasn't visible anymore. So I had to install it once again. If I don't install it again there is no symbol of the app anymore. Is there any opportunity to force my android 5.1.1 to start the app from /priv-app folder without installing it again?

Allright guys - I GOT IT!
Problem was the activated UHQ Upscaler in Settings > Sounds and Notifications > Effects > UHQ Upscaler. Additionally I had to check the FX compatible mode in Viper4Android. After these two changes Viper4Android works well with Spotify.
I thought the sound effects would be deactived when freezing Soundalive and AdaptSound. That was not the case.
Damn, if I had tried to get Viper4Android running with the phonespeaker and noticed the difference in functionality compared to headphones a bit earlier, I could have avoid starting this thread. Sorry!

Maybe you can help me. I have basically spent a whole day trying to get it work. I even installed a fresh install of a new ROM and tried it on two different kernals. Here are my steps exactly!
Im on 9287 and i tried the Artex Kernal and the modified T-Mobile Stock Kernal
1. Install Free Version of Busybox
2. Disabled and also Uninstalled Sound alive and Adapt Sound (Tried both methods)
3. Installed the zip file presented on this post http://forum.xda-developers.com/gal...-edge-root-t3072183/post60417795#post60417795
4. Open Viper FX, Grant Super User, install driver, reboot
5. Enable Viper Fx. Try to play music off google music. Check to see driver status - Enable - Yes Processing - No
Any help will be great

Ok I tried it when i was in my car with bluetooth audio and it works super well! The highs are soo crisp! I cant get it to work with headphones though. Any suggestions?

S7 Edge Notification Delay and A Lot of Other Problems

Recently I am having notification delays with my S7 Edge G935F. I have read through some posts on this forum and other sources and can't figure it out.
Here are some of the problems:
1. notifications are often delayed for more than thirty minutes
2. if I want to manually check notification when it does not pop up, unlocking the screen does not make the notification show, I have to actually launch the specific app to see the notification
3. It is more than just not showing the notification, when I am using some instant messaging apps (like WeChat), I can't see new messages coming in while the app is running in the front. I have to press the home button and get back to home screen, then re-enter the app, then the messages show up. This happens to many other apps as well.
4. Other things go wrong as well. For example, my Android Auto was set to launch whenever I get into my car and car bluetooth is connected. It is also delayed, by more than hours. It often launches long after I finish my driving and get back home sitting on my couch.
5. Downloading new apps from Play Store has problems as well. It downloads to 100% and just stops there, it does not start installation. I have to use Settings->App to kill Play Store and re-open it to "refresh" it, then it starts to install.
6. After installation of new app, it does not show up on my screen or app draw inside my launcher. I can see the app installed in Play Store. I have to kill launcher and re-open the launcher to make it "refresh" the app list then I can see new app inside the app draw.
I have also tried a lot of ways to fix it:
1. change app to not battery optimized -> didn't fix it
2. update firmware -> didn't fix it
3. factory reset -> works for the first day then it goes wrong again
4. flash to a different firmware (official ROM in different regions) -> works for the first day then it goes wrong again
5. use third-party ROM (Lineage OS) -> completely fix the problem, but too buggy to use
I can see the general idea of what's going wrong, some events happened (connected to car Bluetooth, new messages coming, app finished downloading, new app installed, etc.) and the system is not responding correctly. I am not very familiar with Android development but I feel like something is wrong with the "event handling" or "event raising" inside Samsung's Android system.
Please post reply if you have any idea or are facing the similar problems.
EDIT:
The phone is on Android 7.0, Build Number NRD90M.G935FXXU1DQER

You've stated that flashing the custom ROM solved the problem, so maybe you should try flashing a different rom that's a bit more stable.
From personal experience i can recommend the SuperStock rom. It's stock (obviously) and it's debloated and very stable with pretty good battery life as far as i remember.
there is some info about it here: https://forum.xda-developers.com/s7-edge/help/want-to-root-custom-one-stay-stock-t3631098?styleid=18 (ignore the root part).

Hi,
did you find any solution to this problem ? cause i got the same problem, and i'm going crazy... few months already and can't figure out what is the problem...
the temporary fix i've found is disabling the "google app" in application manager... it fix the problem but i can't use any Google app features (and i like using them...).
I've found few ppl experiencing the same problem searching on internet but no one with a real fix...
if someone more experienced can help debut this it would really mean a lot...

I think it is the battery optimization setting. You may check the settings>battery>advanced settings>optimize apps. You need to keep the apps un-optimized if you want the notifications and sync.
Also, you may check if Sync is on or off.
If these two does not solve, factory reset if you are on stock ROM. If on a custom ROM, you may check a different ROM

Hi,
Thanks for your reply. Actually none of this works... The only thing that "fixes" the issue is disabling the Google app in the application manager... That's why its so weird...
The problem started around July/August 2017 for me...
As i discovered that disabling Google was fixing the problem, i assumed that they'll correct it by updating the app... But only one update of the app was ok, all others would make the problems reappear...
Messing with battery optimization settings doesn't change anything for me... Factory reset as well... The problem comes back as soon as the google app gets updated...

Try clearing cache and deleting data from the Google app the time the problem occurs

already tried... doesn't help at all...