Related
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
Hey guys,
After I rooted my S4, I went in Titanium and uninstalled a lot of the bloatware, including ChatOn. Now I'm having issues with the Samsung text-to-speech engine, which I've heard is attributed to the lack of ChatOn. However, I did make a backup of all the apps, but restoring ChatOn didn't fix the problem, and when I start ChatOn, I just get a black screen. And any time I open the text-to-speech options, it just starts giving me "Unfortunately, Samsung text-to-speech engine has stopped." I can't look at the settings, change the language, or anything.
Does anyone know how to properly restore ChatOn, or some other way to circumvent this problem?
You can only download it on play store or samsung apps and just go to titanium backup and "convert to system app" is that I would try. Anyway I don't think deleting chaton may get you this problem, once I always have deleted it.
Enviado de meu GT-I9300 usando o Tapatalk 2
ODIN to the factory
I'm no developer but I don't think ChatOn is the cause of this because I've deleted it before on my Note 2 and it never gave me any problem like that. Although I was running OS 4.1.2 and S4 is 4.2.2. But I think it is something else you have froze or deleted. I would recommend go through TB and search the apps you have frozen or deleted that has to do with txt to speech like Talkback or something like that & restore them one by one to see if that corrects it. Just a suggestion.
Change your text to speech provider to google and that error goes away.
Sent from my GT-I9505 using xda app-developers app
---------- Post added at 01:11 PM ---------- Previous post was at 01:10 PM ----------
My device >language and input >text to speech >google.
Sent from my GT-I9505 using xda app-developers app
Thanks for the responses, everyone.
But yeah I guess I got the idea from here: http://forum.xda-developers.com/showthread.php?p=41287449 and another thread somewhere.
So, I guess my problem is a bit complicated, and pretty difficult to explain.
1) I already have Google TTS checked, and I don't get the Samsung TTS error unless I (a) open a Samsung app (like S-voice), or (b) open up my TTS settings.
2) I don't really care about S-voice, although when people ask me to show me S-voice, I'd like to have it functional.
3) The only reason I bring this issue up is because I'm trying to enter my TTS settings in order to enable Light Flow or LEDBlinker Accessibility.
4) The reason it's making me enter TTS settings is because for some reason my system language and TTS language don't match up. >_<
It's all very bizarre and roundabout, but I've just gotten a feeling from some threads that uninstalling certain Samsung Apps (like ChatOn) can cause these TTS problems. I don't have any other apps uninstalled with TiBU, although I do have a few ATT apps frozen.
I'm beginning to think Odin'ing back might be my only option, though I'd like to avoid it. :/
bhatbhai said:
Thanks for the responses, everyone.
But yeah I guess I got the idea from here: http://forum.xda-developers.com/showthread.php?p=41287449 and another thread somewhere.
So, I guess my problem is a bit complicated, and pretty difficult to explain.
1) I already have Google TTS checked, and I don't get the Samsung TTS error unless I (a) open a Samsung app (like S-voice), or (b) open up my TTS settings.
2) I don't really care about S-voice, although when people ask me to show me S-voice, I'd like to have it functional.
3) The only reason I bring this issue up is because I'm trying to enter my TTS settings in order to enable Light Flow or LEDBlinker Accessibility.
4) The reason it's making me enter TTS settings is because for some reason my system language and TTS language don't match up. >_<
It's all very bizarre and roundabout, but I've just gotten a feeling from some threads that uninstalling certain Samsung Apps (like ChatOn) can cause these TTS problems. I don't have any other apps uninstalled with TiBU, although I do have a few ATT apps frozen.
I'm beginning to think Odin'ing back might be my only option, though I'd like to avoid it. :/
Click to expand...
Click to collapse
I'm with you on this. I wish I could find more help on this problem. I did the exact same thing and had the same results: I backed up and then uninstalled ChatOn and ChatOnV using Titanium Backup. That made S-voice and S-Translator stop working. So I tried re-installing ChatOn and ChatOnV but they would just freeze when opening, so I uninstalled those again and searched for ChatOn in the play store, installed the two apps (ChatOn and ChatOn Video & Voice) and now ChatOn works, again. The problem is, S-Voice and S-Translator do not. I also switched to using Google TTS in the settings, but I really would like to get S-Voice to work again (S-Translator I can live without, but I'd love it if S-Voice worked). I can't figure out how to get that to work correctly short of Odin-ing, which seems like a lot of effort.
mnrbradley said:
I'm with you on this. I wish I could find more help on this problem. I did the exact same thing and had the same results: I backed up and then uninstalled ChatOn and ChatOnV using Titanium Backup. That made S-voice and S-Translator stop working. So I tried re-installing ChatOn and ChatOnV but they would just freeze when opening, so I uninstalled those again and searched for ChatOn in the play store, installed the two apps (ChatOn and ChatOn Video & Voice) and now ChatOn works, again. The problem is, S-Voice and S-Translator do not. I also switched to using Google TTS in the settings, but I really would like to get S-Voice to work again (S-Translator I can live without, but I'd love it if S-Voice worked). I can't figure out how to get that to work correctly short of Odin-ing, which seems like a lot of effort.
Click to expand...
Click to collapse
After I froze some bloatware, I actually started having problems with the Samsung text-to-speech (FC's repeatedly, very annoying). To fix the issue, I switched away to Google's TTS, and then froze the Samsung TTS to get it to go away. This, in-turn, broke S-Voice. To fix S-Voice, iirc, I ended up converting it to a User App and it began working again. Quite strange.
Try fiddling with these in different orders. Take backups with TiBu first, of course. As a last resort, Odin'ing to stock should fix anything.
EDIT: also, for broken apps (like Chat-On), try clearing the cache and data for each using TiBu (cache option is on page2).
Change text to speech to google it goes away.
Sent from my Samsung-sgh-i337 using xda app-developers app
Aou said:
After I froze some bloatware, I actually started having problems with the Samsung text-to-speech (FC's repeatedly, very annoying). To fix the issue, I switched away to Google's TTS, and then froze the Samsung TTS to get it to go away. This, in-turn, broke S-Voice. To fix S-Voice, iirc, I ended up converting it to a User App and it began working again. Quite strange.
Try fiddling with these in different orders. Take backups with TiBu first, of course. As a last resort, Odin'ing to stock should fix anything.
EDIT: also, for broken apps (like Chat-On), try clearing the cache and data for each using TiBu (cache option is on page2).
Click to expand...
Click to collapse
You are a fantastic person. Converting S-voice to a user app worked perfectly.
Sent from my Nexus 10 using Tapatalk HD
Aou said:
After I froze some bloatware, I actually started having problems with the Samsung text-to-speech (FC's repeatedly, very annoying). To fix the issue, I switched away to Google's TTS, and then froze the Samsung TTS to get it to go away. This, in-turn, broke S-Voice. To fix S-Voice, iirc, I ended up converting it to a User App and it began working again. Quite strange.
Try fiddling with these in different orders. Take backups with TiBu first, of course. As a last resort, Odin'ing to stock should fix anything.
EDIT: also, for broken apps (like Chat-On), try clearing the cache and data for each using TiBu (cache option is on page2).
Click to expand...
Click to collapse
I tried clearing the cache like you mentioned, but I didn't try freezing the Samsung TTS. I didn't have Titanium Backup Pro, so I couldn't do that, but I went ahead and made the purchase and froze Samsung TTS and that fixed it (I also changed S Voice to a User App, although I'm not sure if that is what fixed it or freezing the TTS).
At any rate, thanks for the help! S Translator works now, as well. I went ahead and froze several other apps that I don't need (rather than removing) and everything is smoother and less bloated
FIXED!
bhatbhai said:
Hey guys,
After I rooted my S4, I went in Titanium and uninstalled a lot of the bloatware, including ChatOn. Now I'm having issues with the Samsung text-to-speech engine, which I've heard is attributed to the lack of ChatOn. However, I did make a backup of all the apps, but restoring ChatOn didn't fix the problem, and when I start ChatOn, I just get a black screen. And any time I open the text-to-speech options, it just starts giving me "Unfortunately, Samsung text-to-speech engine has stopped." I can't look at the settings, change the language, or anything.
Does anyone know how to properly restore ChatOn, or some other way to circumvent this problem?
Click to expand...
Click to collapse
I did the exact same thing. Deleted some bloat ware (including chat on) and S Voice stopped working correctly. Even though I had a back up on TB I it didn't fix the error message. Finally I just unrooted it (just youtube how to unlock & unbrick galaxy s4). Very simple and straight forward. It took it back to factory firmware, then I just rooted it again. And no I'm obviously not going to delete chat on.
How to convert it to user app?
te
Aou said:
After I froze some bloatware, I actually started having problems with the Samsung text-to-speech (FC's repeatedly, very annoying). To fix the issue, I switched away to Google's TTS, and then froze the Samsung TTS to get it to go away. This, in-turn, broke S-Voice. To fix S-Voice, iirc, I ended up converting it to a User App and it began working again. Quite strange.
Try fiddling with these in different orders. Take backups with TiBu first, of course. As a last resort, Odin'ing to stock should fix anything.
EDIT: also, for broken apps (like Chat-On), try clearing the cache and data for each using TiBu (cache option is on page2).
Click to expand...
Click to collapse
Hi bro ... can you tell how to convert s-voice to a user app? please do reply ! im, stuck with this ... else ill have to factory reset which will b a long process!
firecruz said:
te
Hi bro ... can you tell how to convert s-voice to a user app? please do reply ! im, stuck with this ... else ill have to factory reset which will b a long process!
Click to expand...
Click to collapse
I used Titanium Backup to do this. I'm not sure if this option is available in the basic version - I purchased Pro a very long time ago. Reply if you need some specific instructions.
So naturally one of the first things I did with my new G2 was to root it, since I have a few favorite apps that require root.
Then I did something stupid: I told Titanium Backup to "Integrate updates of system apps into ROM" - hey, it always worked great with my DesireHD running JellyTime. Well, didn't work so well in this case, leading to many of the "bundled" apps simply disappearing, and others (particularly Google apps) crashing.
Most of the Google apps I fixed by simply uninstalling them using TiBkup, then reinstalling from Play... but one it particular I really liked, that I can't find anywhere else, was the bundled "Photo Album" app - like Gallery, but better. Still trying to figure out a way to get this back, short of re-flashing the stock ROM.
I tried doing a full backup of ALL apps in TiBkup, then uninstalling the Photo Album from there (which SAID it worked), then restoring it from backup... but no go. And of course, this isn't an app that's available in Play.
Any other suggestion (other than re-flashing) to get this and others back to where they were? Is there a list of all the bundled apps that came with this phone?
What about reflashing gapps?
GApps isn't really the problem - SOME of the Google apps had issues, but those I could uninstall and then reinstall from the Play Store. It's the Photo Albums app that I'd really like back, and it doesn't appear to be on the Play Store at all. What I need is another G2 that I can export an .apk of the missing apps (or at least of the ones I liked)...
Soundy106 said:
GApps isn't really the problem - SOME of the Google apps had issues, but those I could uninstall and then reinstall from the Play Store. It's the Photo Albums app that I'd really like back, and it doesn't appear to be on the Play Store at all. What I need is another G2 that I can export an .apk of the missing apps (or at least of the ones I liked)...
Click to expand...
Click to collapse
Here is a link the LG apps themselves from the G2. You can download, unzip and install the apks you want.
https://docs.google.com/file/d/0Bx8G-Ji7ejK9T1hvcVJPOFNnZTg/edit
Jimi Mack said:
Here is a link the LG apps themselves from the G2. You can download, unzip and install the apks you want.
https://docs.google.com/file/d/0Bx8G-Ji7ejK9T1hvcVJPOFNnZTg/edit
Click to expand...
Click to collapse
Awesome, exactly what I was looking for... unfortunately install fails on any of them I tried. Tried launching the APKs from both Root Browser and ES Browser, same thing. "Unknown sources" is checked...
Is there a log somewhere that might show me what's going on?
I guess worst case, I have to back everything up and re-flash the stock rom...
Are you running the stock rom or another rom?
Stock - only got the thing a couple weeks ago. I probably wouldn't really worry about it, but there were a couple of the bundled apps I really liked that I want to get back.
And honestly, I've looked at a couple of the other ROMs listed here and considered it, but unlike the bloated nonSense on my old HTC, I really like a lot of the stock LG functionality... and of course, I'm worried that some of the stock apps I like might not work on a custom ROM.
I'm on android version 7.0 stock and without root and I can't play any vodeo on youtube (the app) and facebook (also app).
Youtube: The video wont even start loading or playing there's just a black screen with a message saying: There was a problem while playing. Tap to retry.
Facebook: the video plays for like half a second and then immediately stops.
I tried to delete the app cashe, unistall all the app updates but it didnt help.
Any suggestions?
Thank you everyone.
Jayhrb said:
I'm on android version 7.0 stock and without root and I can't play any vodeo on youtube (the app) and facebook (also app).
Youtube: The video wont even start loading or playing there's just a black screen with a message saying: There was a problem while playing. Tap to retry.
Facebook: the video plays for like half a second and then immediately stops.
I tried to delete the app cashe, unistall all the app updates but it didnt help.
Any suggestions?
Thank you everyone.
Click to expand...
Click to collapse
Something that would surely fix the issue is reinstalling the stock firmware. That may be a little drastic, however I am sure it will work. I know my way with fixing software issues but mostly only on rooted devices. Good luck!
TnT_ said:
Something that would surely fix the issue is reinstalling the stock firmware. That may be a little drastic, however I am sure it will work. I know my way with fixing software issues but mostly only on rooted devices. Good luck!
Click to expand...
Click to collapse
I have no idea how to do that. I guess it's quite a process...
Could you explain it to me like I'm five year old please.
Jayhrb said:
I have no idea how to do that. I guess it's quite a process...
Could you explain it to me like I'm five year old please.
Click to expand...
Click to collapse
https://lmgtfy.com/?q=Flash+stock+firmware+nexus+6p
I have no idea if this could even be answered in these forums, but here goes.
I use Vaulty to hide pictures on my phone with a password. Restoring data and app has always worked from TB, from phone to phone or ROM to ROM. Today I flashed a custom OOS ROM and it didn't go so well.
Behavior: Hangs/ freezes during any kind of gallery search or media loading. This eventually results in a force close. The settings work, but if you try to switch accounts, it will hang on the screen where it's trying to find old vaults.
Things I have done: Force close the app, clear data, clear cache. Uninstall and reinstall from Play Store. Uninstall and restore only app from TB. Froze 3rd party gallery apps. Set the default gallery app. I even installed another vault program - Vault. This app won't even load up AT ALL. It goes black immediately upon trying to open it. This led me to think something else might be going on.
Has anyone seen anything like this? Anything I could try?
xgerryx said:
I have no idea if this could even be answered in these forums, but here goes.
I use Vaulty to hide pictures on my phone with a password. Restoring data and app has always worked from TB, from phone to phone or ROM to ROM. Today I flashed a custom OOS ROM and it didn't go so well.
Behavior: Hangs/ freezes during any kind of gallery search or media loading. This eventually results in a force close. The settings work, but if you try to switch accounts, it will hang on the screen where it's trying to find old vaults.
Things I have done: Force close the app, clear data, clear cache. Uninstall and reinstall from Play Store. Uninstall and restore only app from TB. Froze 3rd party gallery apps. Set the default gallery app. I even installed another vault program - Vault. This app won't even load up AT ALL. It goes black immediately upon trying to open it. This led me to think something else might be going on.
Has anyone seen anything like this? Anything I could try?
Click to expand...
Click to collapse
Did you manage to solve this problem? I facing same problem in my device.
Apcoolboy said:
Did you manage to solve this problem? I facing same problem in my device.
Click to expand...
Click to collapse
I actually managed to recover the pictures, saved them of the phone and switched to keepsafe, it works better. I found that adding the app manually and logging in, trying to restore just data from TB, and a bunch of other combinations finally allowed me to recover the pictures. This was a while back so I don't remember exactly but eventually I got it.
xgerryx said:
I actually managed to recover the pictures, saved them of the phone and switched to keepsafe, it works better. I found that adding the app manually and logging in, trying to restore just data from TB, and a bunch of other combinations finally allowed me to recover the pictures. This was a while back so I don't remember exactly but eventually I got it.
Click to expand...
Click to collapse
Thanks for the response. My problem is, I have old vaulty backup on my phone and no app installed. Today I tried to install app to recover my backup. But it went blank screen as soon as I open my app. Tried different apks of different versions from net. But it won't go beyond black screen. Tried all cleanup, cache removal from twrp and from app settings. But same. Aldo tried to install different vault app to check what happen and surprisingly it also freeze at app startup screen and won't go beyond black screen. I think it's ROM problem and some file would be corrupted which belongs to vault apps working. Last resort is to flash fresh ROM and try. (I even didn't restore app backup from tb as I didn't have one. Always installed fresh app from play store)
Apcoolboy said:
Thanks for the response. My problem is, I have old vaulty backup on my phone and no app installed. Today I tried to install app to recover my backup. But it went blank screen as soon as I open my app. Tried different apks of different versions from net. But it won't go beyond black screen. Tried all cleanup, cache removal from twrp and from app settings. But same. Aldo tried to install different vault app to check what happen and surprisingly it also freeze at app startup screen and won't go beyond black screen. I think it's ROM problem and some file would be corrupted which belongs to vault apps working. Last resort is to flash fresh ROM and try. (I even didn't restore app backup from tb as I didn't have one. Always installed fresh app from play store)
Click to expand...
Click to collapse
I went as far as to try to find out how to convert those proprietary .vaulty files back to pictures with some kind of file converter online. I didn't get very far with that method but that might be the last resort. I think I ended up flashing another ROM at the time too and maybe it was dumb luck that I was able to get it back.