Related
I am having a problem with any media player except the stock one. I want to use a 3rd party media player, so that I don't have to convert my movies to something compatible with the stock media player. the problem is whenever I use a 3rd party media player, I hook the phone to my tv, and the movie plays for a few minutes, then it stops, and loses my place, this is very irritating. This doesn't happen on the the stock media player. Does anyone have any ideas? I have tried at least 6 third party media players, and they all stop every few minutes... For now I am just converting my movies for use with the stock player, but this is time consuming.
it depends on what app you're trying to use. you might want to see if there's an extra codec pack. i know that mobo player has a lot of add-on codec packs. if this is the case and the dev is smart, the codec packs are usually in the market, just like the original program.
also, you may want to try something with soft decoding included, if you're not already.
moe. said:
it depends on what app you're trying to use. you might want to see if there's an extra codec pack. i know that mobo player has a lot of add-on codec packs. if this is the case and the dev is smart, the codec packs are usually in the market, just like the original program.
also, you may want to try something with soft decoding included, if you're not already.
Click to expand...
Click to collapse
Most of the players had soft decoding, and it isn't a codec pack, the videos play, but suddenly stop. The only one that doesn't do that is the stock one. Has anyone else had this problem? Do you all use the stock player?
does it only do it when using tv out or does it happen on the device screen, also? what rom/kernel are you using?
Have you. Tried remote for vlc? I think you can play media on the sd card. Not sure haven't tried it but worth a shot if you haven't.
sent from my ice cream sandwhich MT4GS
moe. said:
does it only do it when using tv out or does it happen on the device screen, also? what rom/kernel are you using?
Click to expand...
Click to collapse
So it seems to only do it when using the tv out function, which is really cruddy, because I don't want to watch movies on my tiny phone, I want to watch them on the big tv. I am using Bulletproof 1.0, and the stock kernel. I am going to try remote for vlc right now, but I am thinking the problem is something to do with the tv out function.
I understand the frustration. My educated guess would have to be that it has something to do with a kernel conflict. Try a different rom and/or kernel. There are, also, some updates for bulletproof now, too.
Sent from my myTouch_4G_Slide using XDA App
moe. said:
I understand the frustration. My educated guess would have to be that it has something to do with a kernel conflict. Try a different rom and/or kernel. There are, also, some updates for bulletproof now, too.
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
If I remember correctly this happened on other roms too, but I will try again. I tried the new bulletproof, but I liked the old one better. I haven't tried a different kernel though, so I will start flashing different kernel/rom combos, to see if it makes a difference.
yellowjacket1981 said:
So it seems to only do it when using the tv out function, which is really cruddy, because I don't want to watch movies on my tiny phone, I want to watch them on the big tv. I am using Bulletproof 1.0, and the stock kernel. I am going to try remote for vlc right now, but I am thinking the problem is something to do with the tv out function.
Click to expand...
Click to collapse
Sorry, I missed this thread. I'm kinda skimming over the boards while i'm doing paperwork and such, so i'm skipping over things and not realizing it. (hate januaries, always so busy)
Anyways, it's a codec issue. You'll only get the problem when outputting to tv - and soft-decoding only solves part of the problem.
What's happening is your file format is too far away from what the hardware can handle easily while it's also trying to feed the video out and keep the screen active on the device.
Even though you check soft-decoding in the app, without proper codecs installed it defaults some or all of the work back to the hardware.
I use Mobo Player, free video app and is hands-down my favorite one on Android. It lets you choose soft-decoding in the settings menu, but they also supply a codec you can find in the market.
I'm using the ARM V7_VFP codec from the same author as Mobo Player, and don't have a problem with it. When I do reflash and forget to install it then it goes back to randomly cutting out while i'm enjoying my movie/show or whatever.
Edit: This Google Market Link will get you to the right codec for our device.
I suppose I should have mentioned something about it in my ROM thread, since I included it in Bulletproof for that reason - but, there's a lot going on here lol.
I should have seen this thread yesterday, but I suppose i'm looking at it the wrong way since I get to skim the forums while i'm getting work done. (as opposed to not being able to browse them at all.)
Anyways, Mobo Player is free, and so is the codec, so all you lose for trying is time - give it a shot and see where it gets ya.
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
moe. said:
I understand the frustration. My educated guess would have to be that it has something to do with a kernel conflict. Try a different rom and/or kernel. There are, also, some updates for bulletproof now, too.
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Nah, I haven't made any updates to Bulletproof recently, though i'd like to squeeze one out around work soon.
Blue6IX said:
Sorry, I missed this thread. I'm kinda skimming over the boards while i'm doing paperwork and such, so i'm skipping over things and not realizing it. (hate januaries, always so busy)
Anyways, it's a codec issue. You'll only get the problem when outputting to tv - and soft-decoding only solves part of the problem.
What's happening is your file format is too far away from what the hardware can handle easily while it's also trying to feed the video out and keep the screen active on the device.
Even though you check soft-decoding in the app, without proper codecs installed it defaults some or all of the work back to the hardware.
I use Mobo Player, free video app and is hands-down my favorite one on Android. It lets you choose soft-decoding in the settings menu, but they also supply a codec you can find in the market.
I'm using the ARM V7_VFP codec from the same author as Mobo Player, and don't have a problem with it. When I do reflash and forget to install it then it goes back to randomly cutting out while i'm enjoying my movie/show or whatever.
Edit: This Google Market Link will get you to the right codec for our device.
I suppose I should have mentioned something about it in my ROM thread, since I included it in Bulletproof for that reason - but, there's a lot going on here lol.
I should have seen this thread yesterday, but I suppose i'm looking at it the wrong way since I get to skim the forums while i'm getting work done. (as opposed to not being able to browse them at all.)
Anyways, Mobo Player is free, and so is the codec, so all you lose for trying is time - give it a shot and see where it gets ya.
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
Nah, I haven't made any updates to Bulletproof recently, though i'd like to squeeze one out around work soon.
Click to expand...
Click to collapse
And another job well done.
Sent from my myTouch_4G_Slide using XDA App
Blue6IX said:
Sorry, I missed this thread. I'm kinda skimming over the boards while i'm doing paperwork and such, so i'm skipping over things and not realizing it. (hate januaries, always so busy)
Anyways, it's a codec issue. You'll only get the problem when outputting to tv - and soft-decoding only solves part of the problem.
What's happening is your file format is too far away from what the hardware can handle easily while it's also trying to feed the video out and keep the screen active on the device.
Even though you check soft-decoding in the app, without proper codecs installed it defaults some or all of the work back to the hardware.
I use Mobo Player, free video app and is hands-down my favorite one on Android. It lets you choose soft-decoding in the settings menu, but they also supply a codec you can find in the market.
I'm using the ARM V7_VFP codec from the same author as Mobo Player, and don't have a problem with it. When I do reflash and forget to install it then it goes back to randomly cutting out while i'm enjoying my movie/show or whatever.
Edit: This Google Market Link will get you to the right codec for our device.
I suppose I should have mentioned something about it in my ROM thread, since I included it in Bulletproof for that reason - but, there's a lot going on here lol.
I should have seen this thread yesterday, but I suppose i'm looking at it the wrong way since I get to skim the forums while i'm getting work done. (as opposed to not being able to browse them at all.)
Anyways, Mobo Player is free, and so is the codec, so all you lose for trying is time - give it a shot and see where it gets ya.
---------- Post added at 02:39 PM ---------- Previous post was at 02:33 PM ----------
Nah, I haven't made any updates to Bulletproof recently, though i'd like to squeeze one out around work soon.
Click to expand...
Click to collapse
Thanks, I am flashing bulletproof 1.1 again, and hoping to get things running well. I will keep you updated. I was running bulletproof 1.0, so I think that was what they were talking about , when they said there was an update.
So, you've motivated me to look a little deeper.
Looks like Wifi-calling is also causing a whole mess of trouble on the device.
It can't do something, and keeps trying, which is part (if not all of) why the system can't keep up with a movie.
I just removed it from my build a little while ago after I couldn't get it to play nice, and I can't describe how much more smoothly my system is running without it (minus a couple of hiccups because it's not there anymore and things are expecting it to be)
I'm going to rebuild a Bulletproof distribution without the wifi-calling and see what kind of data I can dredge up to compare to - but I have a feeling this is the other piece of the puzzle for why it's not working right.
I'm on the same version of wifi-calling that has been around for a while - I think there was an update to it in one of the OTA updates? Can't remember.
I'm pushing the edge of exhaustion, it's been a few days, so i'm probably not gonna get to it tonight, but it's the next thing on my list. Figured i'd mention it here in case anyone wanted to experiment with it in the meanwhile.
I'm not kidding when I say it's literally like a whole new device without wifi calling - I honestly can't believe what a difference it's absence is making.
Blue6IX said:
So, you've motivated me to look a little deeper.
Looks like Wifi-calling is also causing a whole mess of trouble on the device.
It can't do something, and keeps trying, which is part (if not all of) why the system can't keep up with a movie.
I just removed it from my build a little while ago after I couldn't get it to play nice, and I can't describe how much more smoothly my system is running without it (minus a couple of hiccups because it's not there anymore and things are expecting it to be)
I'm going to rebuild a Bulletproof distribution without the wifi-calling and see what kind of data I can dredge up to compare to - but I have a feeling this is the other piece of the puzzle for why it's not working right.
I'm on the same version of wifi-calling that has been around for a while - I think there was an update to it in one of the OTA updates? Can't remember.
I'm pushing the edge of exhaustion, it's been a few days, so i'm probably not gonna get to it tonight, but it's the next thing on my list. Figured i'd mention it here in case anyone wanted to experiment with it in the meanwhile.
I'm not kidding when I say it's literally like a whole new device without wifi calling - I honestly can't believe what a difference it's absence is making.
Click to expand...
Click to collapse
You deserve your rest! I just wanted to report back, that I am still having the same problem. I updated to bulletproof 1.1, and installed the codec that you linked to, still had the problem. The movie will play for a few minutes, and then suddenly stop. I then installed all the codecs for mobo player, and still nothing. I can't remember if this happened on the stock rom or not. My boyfriend is still on the stock rom, so when he come by tonight, I will test a 3rd party media player on his, to see if there is still the same problem. If it works on stock, I may just flash back to stock for now, to save me the trouble of converting a lot of my movies. Thanks for all your help Blue.
Also, I can't wait to see the rom without wifi calling!
If you have the android sdk set up on a computer you can plug into, set your phone to usb-debugging/charge only and plug it in and watch the output.
You'll see the wifi calling app (kineto) going nutzo - i've been trying to mak it behave for a while because some people mentioned liking using it (even though it doesn't work so well) but tonight was the last straw with it.
Now that it's gone from my device, I can't tell you how much smoother it's been running. The whole output on my screen going all the way back to before I posted last (so, i've moved past the buffer in the log) and not one error msg.
That was unheard of with the wifi calling app on the device, and it made it look like it was more then one app causing the problem. Got rid of that one, and it solved pretty much the whole thing.
I wasn't having an issue with it crashing out of the movie earlier today - but I just set a friend of mine up with rooting his new MT4GS, so I flashed mine fresh alongside when we did his yesterday (day before?) ...
You might wanna try just axing that real quick before you go flashing all over again - just a thought
Finishing up my last call of the night, i'll catch up with you all tomorrow - hope it works out for you.
Blue6IX said:
If you have the android sdk set up on a computer you can plug into, set your phone to usb-debugging/charge only and plug it in and watch the output.
You'll see the wifi calling app (kineto) going nutzo - i've been trying to mak it behave for a while because some people mentioned liking using it (even though it doesn't work so well) but tonight was the last straw with it.
Now that it's gone from my device, I can't tell you how much smoother it's been running. The whole output on my screen going all the way back to before I posted last (so, i've moved past the buffer in the log) and not one error msg.
That was unheard of with the wifi calling app on the device, and it made it look like it was more then one app causing the problem. Got rid of that one, and it solved pretty much the whole thing.
I wasn't having an issue with it crashing out of the movie earlier today - but I just set a friend of mine up with rooting his new MT4GS, so I flashed mine fresh alongside when we did his yesterday (day before?) ...
You might wanna try just axing that real quick before you go flashing all over again - just a thought
Finishing up my last call of the night, i'll catch up with you all tomorrow - hope it works out for you.
Click to expand...
Click to collapse
I do have sdk installed and working on my computer, but I am still a newb when it comes to actually using it lol. Just so you know, I had my boyfriend try to run a movie with tv out on my tv, with mobo player, and it crashed too, and he is on stock. The problem is definitely not rom related. I am going to try getting rid of wifi calling and see if that improves anything. I will let you know.
yellowjacket1981 said:
I do have sdk installed and working on my computer, but I am still a newb when it comes to actually using it lol. Just so you know, I had my boyfriend try to run a movie with tv out on my tv, with mobo player, and it crashed too, and he is on stock. The problem is definitely not rom related. I am going to try getting rid of wifi calling and see if that improves anything. I will let you know.
Click to expand...
Click to collapse
Appreciate the confirmation it's not ROM related - It's one thing for me to say it as the creator of the ROM, another thing for a third party to verify it.
Are you on a windows machine? If so:
In your SDK folder, go to the 'tools' folder. In it you will find a file called "ddms.bat"
Open this, and it will launch a DOS window, which then launches a GUI after a few mins.
Welcome to the dalvik debug monitor window.
Now what you do, is go to settings on your device. In the "Connect to PC" option, set it to "charge only"
Then, back in the settings menu, go to "applications" then "development" and make sure "USB debugging" is checked.
(also might be a good idea to check "stay awake")
Now you can plug the doubleshot into the computer without having it disable your sdcard access, and let it just run like normal.
Plug it into the computer, and you will see it pop up in the list in the dalvik debug monitor.
You can watch what it's doing and see if you have any issues.
It might help you to track down this problem, and see about a resolution. DDMS is one of the primary troubleshooting tools you should be using to figure out what's going on on your device.
Often times I just let one of my doubleshots stay plugged in to ddms while i'm sitting here, and just have the log running while i'm working on the laptop next to the pc. Familiarizing yourself with the device in this fashion will help a lot in terms of development, but even as just a user you will get a huge understanding of what the device is doing.
The first time it injected the A-GPS data while I was connected to DDMS was awesome - little things like that give you a huge understanding of what's going on.
Also, it'll keep running if you reboot the device while it's connected - lets you see what happens when it shuts down but also what happens when it first boots up.
----
Removing wifi calling has been such a great move - trying to fight with it and getting it to play nice is like trying to get water to flow uphill.
I just threw together a flashable Bulletproof zip without it and am getting ready to flash it to my phone, we'll see how this goes but I have a feeling that the wifi calling app is a large part of the remaining problem once the correct codec is installed and you have soft-decoding active.
Okay, something isn't right now.
For a while Moboplayer was working fine with soft decoding and output to television, but now I can't get too far before it fatally crashes out.
I am wracking my brain trying to figure out why it was working for a while but now is not - meantime, the generic player will output to television without crashing...but suffers the odd video issue present with hardware decoding that makes it not so great. Gets artifacts on-screen and doesn't properly display the video on the television smoothly, yet appears fine on the device itself.
There is an answer somewhere - i'm not sure what it is, but it'll be found ... we just need to keep trying.
Either need to figure out why any aftermarket player crashes (I think it has something to do with audio - but that could be misleading since the headphones jack we are using for video output counts as audio - at least in the logs)
Ive had the same issue with mx player,mobo player,v player with just the device itsel. I didnt have the codec packs for mx or mobo player installed at the time tho. I got vplayer working by changing the buffer & disabling hardware decoding. Here are the specs for the video I was playing at the time: Video 724 kbps xvid Audio 5.1 AC3 Resolution 640x272 2.35:1
pimppoet said:
Ive had the same issue with mx player,mobo player,v player with just the device itsel. I didnt have the codec packs for mx or mobo player installed at the time tho. I got vplayer working by changing the buffer & disabling hardware decoding. Here are the specs for the video I was playing at the time: Video 724 kbps xvid Audio 5.1 AC3 Resolution 640x272 2.35:1
Click to expand...
Click to collapse
Working as in it'll play the whole video through without crashing out?
Blue6IX said:
Working as in it'll play the whole video through without crashing out?
Click to expand...
Click to collapse
yea...the apps never force closed only randomly stopped for me intially but. ok so far now with no stops. I havent watched ne other movies since then to really test it out. I also found an
alpha build of vlc player here http://dl.cvpcs.org/android/test/common/VLC-noneon.apk
Each time I power my Android TV stick (Jelly Bean) on, having set MX Player to be the default player, I am asked by every app to select a player as default, it will then remember my choice, until I turn the Android off, them when I turn it on, the default setting is not remembered and I have to set it again. This happens only with MX Player.
I have tried clearing defaults, clearing data and uninstalling and re-installing.
It started after either of the last two updates.
Can you help?
Many thanks,
Sylar
sylar66 said:
Each time I power my Android TV stick (Jelly Bean) on, having set MX Player to be the default player, I am asked by every app to select a player as default, it will then remember my choice, until I turn the Android off, them when I turn it on, the default setting is not remembered and I have to set it again. This happens only with MX Player.
I have tried clearing defaults, clearing data and uninstalling and re-installing.
It started after either of the last two updates.
Can you help?
Many thanks,
Sylar
Click to expand...
Click to collapse
If I am not wrong, MX player is nothing to do with default app selection.
Android controls the default app to be used. If you select always when the app list appears it will be remembered till you manually clear the default or till a new application istalled which can be associated with the same extension.
If it's not remembered even after selecting always, or being reset after restart then there may be chances of bugs in your android rom.
MX Player default app selection
ktsamy said:
If I am not wrong, MX player is nothing to do with default app selection.
Android controls the default app to be used. If you select always when the app list appears it will be remembered till you manually clear the default or till a new application istalled which can be associated with the same extension.
If it's not remembered even after selecting always, or being reset after restart then there may be chances of bugs in your android rom.
Click to expand...
Click to collapse
That's the problem, it doesn't remember, and it only happens with M Player, and since the most recent updates, the android has never had a problem until then, nor has it with any other app, the button to clear the defaults listed under the MX Player is apps will be active once the 'select always' has been chosen, once it is switched back on it will not remember. Again i saw this is only with MX Player, not the android software, as it does NOT happen with any other, so its unlikely to be the ROM.
Can you advise any steps that may fix this problem?
Will resetting the Android do it?
Will a re-install fix?
Thanks,
Sylar
sylar66 said:
That's the problem, it doesn't remember, and it only happens with M Player, and since the most recent updates, the android has never had a problem until then, nor has it with any other app, the button to clear the defaults listed under the MX Player is apps will be active once the 'select always' has been chosen, once it is switched back on it will not remember. Again i saw this is only with MX Player, not the android software, as it does NOT happen with any other, so its unlikely to be the ROM.
Can you advise any steps that may fix this problem?
Will resetting the Android do it?
Will a re-install fix?
Thanks,
Sylar
Click to expand...
Click to collapse
Clear data & uninstall
Reinstall from play store.
If you still encounter the problem,
Try to download the old version which is worked well earlier and check whether it's working currently or not?
If the old version is still working then report here with the working version number. It will be helpful to identify the problem.
Just to add my experience here:
My Android 4.2.1 has been doing this also - and only since I updated to the Pro version from 1.7.35 release.
I've been trying to track down the reason - and recently read that the Pro release can have an issue where ALL settings are lost due to a flaw in Android
but in my case all other settings are remembered.
I reinstalled, I reset my Android TV, I only loaded two apps - MS Player and ES file explorer - I reset it again and formatted the SD memory card,
but it is still happening.
I select the default player for all the filetypes to be MX Player and it remembers it - but at some stage it will ask to select the media player app again
and my TV only has the web browser and MX Player shown - as I select the media from a HTTP server on my local machine.
The free ad-supported version didn't show this problem.
I'm just adding this in case someone recognises the symptom - and my Android system is terribly locked down Kogan 47" Agora Smart TV - in Australia.
I will roll back to the ad-supported version and report back in a few weeks (If I forget and someone is interested then please reply to remind me)
foxidriver said:
I will roll back to the ad-supported version and report back in a few weeks
Click to expand...
Click to collapse
Just updating the thread: It's a week later and the issue hasn't re-occurred with the ad-supported version of MX Player V1.7.37
If others can report their Android version then it may show if it is a flaw in specific versions.
foxidriver said:
Just updating the thread: It's a week later and the issue hasn't re-occurred with the ad-supported version of MX Player V1.7.37
If others can report their Android version then it may show if it is a flaw in specific versions.
Click to expand...
Click to collapse
If anyone is still reading this thread, a workaround to this very annoying problem, is with root, freeze all other video players, then Android has no choice but to use the one you left unfrozen, as the default, without asking
Thanks for your reply, Detection. It may help others,
I will add here that my Android machine is locked down and doesn't give Root permissions, but I also want to say
that my TV has problems with every other paid app I have tried (random rebooting, slow, flaky).
I have reformatted and tested a number of times, and loading a paid app causes it to do these things. My Android version is speshul.
Free ad-supported apps work quite well - something to do with authentication is borked.
I just recently got a Nexus Player and one of the first things I did was install Plex. I was having two big problems with my Nexus Player though, both of which started immediately.
First, the microphone on my remote controller was really malfunctioning. It would almost always fail, either only recognizing the first word or two I said, or not recognizing any of them at all. It was really bad. At first, I thought I had a defective device.
Second, the Backdrop (i.e., the "screen saver") would never activate automatically on its own after the pre-set time. If I went into settings, I could manually start it, but it wouldn't start on its own - my Nexus Player would just sit at the home screen indefinitely.
While troubleshooting, I finally got around to uninstalling Plex, and to my surprise, both of the above problems went away. The microphone now works almost flawlessly, as it should, and Backdrop is activating fine. I put Plex back on, and the problems both came back. I then uninstalled it again, and voila, both problems went away.
Has anyone else noticed either of these issues? Unfortunately they're forcing me to leave Plex uninstalled from my Nexus Player for the time being.
I believe it is known that the current build of Plex is buggy as all hell. Use kodi beta 1 or the recompiled 13.2 in the xbmc thread for now instead.
Sent via Tapatalk on the Oneplus One
ktownhero said:
I believe it is known that the current build of Plex is buggy as all hell. Use kodi beta 1 or the recompiled 13.2 in the xbmc thread for now instead.
Sent via Tapatalk on the Oneplus One
Click to expand...
Click to collapse
Thanks! I used to be a hardcore XBMC user back in the day before I started using Plex for its Chromecast support. I'm going to check it out.
nyijedi said:
Thanks! I used to be a hardcore XBMC user back in the day before I started using Plex for its Chromecast support. I'm going to check it out.
Click to expand...
Click to collapse
Make sure to specifically use Kodi Beta 1 or the recompiled 13.2. All of the other versions I've tried crash during video play back.
Plex is awesome, I still use the server so I can have my library synchronized. That said, you can use PleXBMC and the Amber skin to essentially make XBMC/Kodi into a free Plex app. The $150 price tag for lifetime is what keeps me from fully committing to Plex.
Hi--I have used this a long time, suddenly it has become non-functional, I suspect due to the 1.7.32 update, but not sure.
--Android 4.3 (I've avoided 4.4 to retain full functionality of the SD card...)
--MX Pro 1.7.32
--Samsung Galaxy Note 10.1 2014
--Could not follow directions for alogcat because the nature of the problem makes MX unuseable once it crashes--there is no way to hit the "settings" button in MX Player Pro at that point.
PROBLEM
So, I bring up my file list as per normal. I click on a vid. The vid does not play. In fact, there is merely a blank screen. Eventually I'm returned to the home screen of the tablet and advised that MX Player has crashed. Sometimes, I don't even get the blank screen. It just automatically disappears and returns me to the tablet's home screen. Once that happens, the program never works again (until reinstalled or data cleared) and won't even let me into the program. Clicking its icon simply brings up a blank screen, then I get "Unfortunately, MX Player Pro has stopped..."
Troubleshooting
I have tried clearing cache, data and also reinstalling. The last two DO allow me to once again bring up the File List from "folders view." It looks normal once again. However, once I try to play vids, the same, exact result occurs, i.e., nothing actually plays and the program crashes with the screen going blank.
CLUES
a) I also have this on my phone, where it continues to work fine, but on my phone, I only have a handful of FLVs. The tablet has lots of other formats, primarily mp4. On my Note 4 phone, however, I'm running 4.4 KitKat.
b) If I access the video in a roundabout fashion, by clicking on it from a File Manager, the File Manager then offers to play it with the native vid player OR Mx Player. Then, it works fine. The exact same video. Of course, then I can't access any other parts of the MX P program, and I am no longer able to use the file list Mx Player P builds.
c) I tried playing with various settings, like hardware decoder, and what not, but it did not seem to help much.
My thought is that the version supporting Lollipop has done something that Samsung does not like in conjunction with 4.3
Any thoughts welcomed. TIA
monsieurms said:
Hi--I have used this a long time, suddenly it has become non-functional, I suspect due to the 1.7.32 update, but not sure.
--Android 4.3 (I've avoided 4.4 to retain full functionality of the SD card...)
--MX Pro 1.7.32
--Samsung Galaxy Note 10.1 2014
--Could not follow directions for alogcat because the nature of the problem makes MX unuseable once it crashes--there is no way to hit the "settings" button in MX Player Pro at that point.
PROBLEM
So, I bring up my file list as per normal. I click on a vid. The vid does not play. In fact, there is merely a blank screen. Eventually I'm returned to the home screen of the tablet and advised that MX Player has crashed. Sometimes, I don't even get the blank screen. It just automatically disappears and returns me to the tablet's home screen. Once that happens, the program never works again (until reinstalled or data cleared) and won't even let me into the program. Clicking its icon simply brings up a blank screen, then I get "Unfortunately, MX Player Pro has stopped..."
Troubleshooting
I have tried clearing cache, data and also reinstalling. The last two DO allow me to once again bring up the File List from "folders view." It looks normal once again. However, once I try to play vids, the same, exact result occurs, i.e., nothing actually plays and the program crashes with the screen going blank.
CLUES
a) I also have this on my phone, where it continues to work fine, but on my phone, I only have a handful of FLVs. The tablet has lots of other formats, primarily mp4. On my Note 4 phone, however, I'm running 4.4 KitKat.
b) If I access the video in a roundabout fashion, by clicking on it from a File Manager, the File Manager then offers to play it with the native vid player OR Mx Player. Then, it works fine. The exact same video. Of course, then I can't access any other parts of the MX P program, and I am no longer able to use the file list Mx Player P builds.
c) I tried playing with various settings, like hardware decoder, and what not, but it did not seem to help much.
My thought is that the version supporting Lollipop has done something that Samsung does not like in conjunction with 4.3
Any thoughts welcomed. TIA
Click to expand...
Click to collapse
Already there is a sticky thread in which I have already explained the procedure to collect the log immediately after crash.
Install MX Log collector app
Open It immediately after the MX Player Crash
Save the logs & Upload here
Does it crashes in all decoders?
If you are using H/W+ disable it & Check again.
long press the video & select Play using | S/W decoder
Check whether it still crashes or not.
ktsamy said:
Already there is a sticky thread in which I have already explained the procedure to collect the log immediately after crash.
Install MX Log collector app
Open It immediately after the MX Player Crash
Save the logs & Upload here
Does it crashes in all decoders?
If you are using H/W+ disable it & Check again.
long press the video & select Play using | S/W decoder
Check whether it still crashes or not.
Click to expand...
Click to collapse
It does not matter whether or not I use HW or SW decoding.
I upgraded the tablet to KitKat. That did not matter either.
I tried to upload the log files from MX Log here. Each time (3x now!) it gave me "invalid file" and refused to accept the upload. Oh, well.
monsieurms said:
It does not matter whether or not I use HW or SW decoding.
I upgraded the tablet to KitKat. That did not matter either.
I tried to upload the log files from MX Log here. Each time (3x now!) it gave me "invalid file" and refused to accept the upload. Oh, well.
Click to expand...
Click to collapse
You can upload to any file sharing network like dropbox & post the link here.
If you are not allowed to post the links, use masking like h**p://www.google.com
ktsamy said:
You can upload to any file sharing network like dropbox & post the link here.
Click to expand...
Click to collapse
It would not let me post links even with asterisks. I took out the http in its entirety. That didn't work either. I took out the dropbox reference as well. That did not work either. Have no clue at this point.
*Indeed, it wouldn't even let me quote your post with the partial link you referenced.
monsieurms said:
It would not let me post links even with asterisks. I took out the http in its entirety. That didn't work either. I took out the dropbox reference as well. That did not work either. Have no clue at this point.
*Indeed, it wouldn't even let me quote your post with the partial link you referenced.
Click to expand...
Click to collapse
Uncheck "auto parse links" at the bottom of the post reply page.
drop****box.com/s/l4mzbrlj0sh1ajf/build.prop?dl=0
drop******box.com/s/n18by6pewz706de/log.txt.gz?dl=0
another data point
FYI, just in case it helps, not as a "zing," BS Player works fine and normally. MX continues to work (on tablet and despite recent updates) only when a file is clicked from My Files file manager. It just won't deal with its own list of videos.
monsieurms said:
FYI, just in case it helps, not as a "zing," BS Player works fine and normally. MX continues to work (on tablet and despite recent updates) only when a file is clicked from My Files file manager. It just won't deal with its own list of videos.
Click to expand...
Click to collapse
@monsieurms There was an issue on Note 10.1 2014 European ROM and it might be fixed on 1.7.34
Please try latest version also try clear app data, MX Player's internal database looks like corrupted. This issue is also fixed but once corrupted database will never be recovered.
bleu8888 said:
@monsieurms There was an issue on Note 10.1 2014 European ROM and it might be fixed on 1.7.34
Please try latest version also try clear app data, MX Player's internal database looks like corrupted. This issue is also fixed but once corrupted database will never be recovered.
Click to expand...
Click to collapse
I tried it again--I'd already done that after upgrading to 1.7.3.4---but it did not help. I am not in Europe---North America.
monsieurms said:
I tried it again--I'd already done that after upgrading to 1.7.3.4---but it did not help. I am not in Europe---North America.
Click to expand...
Click to collapse
@monsieurms Would you send log again using 1.7.34? Thanks!
Given your comment on list db corruption and the fact that some vids in small directories do work, I tried copying all the vids to a new directory. That didn't work.
I cleared data again and also downloade the arm7 Neon custom codec specified in the Decoder settings. That did not help either. (It did find and install the codec.)
With the clues you gave me, I experimented a little. In particular, I noticed that some vids in small folders (small in terms of # of videos), played fine. I thought at first, as mentioned earlier in the thread, it was a difference in format. But as we've seen, all the videos play fine if accessed from File Manager--so that's not it. With the addition of your clue on database corruption, I thought perhaps the issue was folder size. I divided the one large folder into two, 50-50. That fixed it.
I would say you have still an issue here---the program chokes with a large of vids in the database. It doesn't seem to bother other programs, including the native video player and BS, and it didn't seem to bother MXp Pro until the recent wave of updates. So, I suspect something went wrong somewhere.
monsieurms said:
With the clues you gave me, I experimented a little. In particular, I noticed that some vids in small folders (small in terms of # of videos), played fine. I thought at first, as mentioned earlier in the thread, it was a difference in format. But as we've seen, all the videos play fine if accessed from File Manager--so that's not it. With the addition of your clue on database corruption, I thought perhaps the issue was folder size. I divided the one large folder into two, 50-50. That fixed it.
I would say you have still an issue here---the program chokes with a large of vids in the database. It doesn't seem to bother other programs, including the native video player and BS, and it didn't seem to bother MXp Pro until the recent wave of updates. So, I suspect something went wrong somewhere.
Click to expand...
Click to collapse
Would you send log using 1.7.34 or test version on following link?
https://sites.google.com/site/mxvpen/translation/test-build
Whenever I try to open any video file in any app using MX Player or MX Player pro. I get a message that says 'MX Player has stopped'
I have attached the logs. Start @ timestamp 13:07 for a test trying to play a video from the internal movie library
This is using Android TV x86 7.1.
VLC plays fine.
Tried MXplayer version 1.8.21. Same issue
Bump.... Anyone?
dcol said:
Bump.... Anyone?
Click to expand...
Click to collapse
Apologize for the delay.
We have tried to reproduce the issue on the android emulator with android TV 7.1.1 firmware. But, we couldn't reproduce the issue. Can you please collect the complete system logs using ADB?
MXPlayer said:
Apologize for the delay.
We have tried to reproduce the issue on the android emulator with android TV 7.1.1 firmware. But, we couldn't reproduce the issue. Can you please collect the complete system logs using ADB?
Click to expand...
Click to collapse
Did another bug report which includes the system logs, and used adb logcat for another log report. If there is any other log you need, you will have to give me instructions on how to get it.
dcol said:
Did another bug report which includes the system logs, and used adb logcat for another log report. If there is any other log you need, you will have to give me instructions on how to get it.
Click to expand...
Click to collapse
We have investigated from our end. But, couldn't reproduce the issue.
Have you rooted the device and changed anything on system partition?
In your logs, we have noticed crashes on some other media related system libraries as well.
We have checked on the Google Play data as well. There weren't any similar crashes reported on the nexus player. MX Player uses several android internal modules for performance reasons. Since you are facing the issues with even older versions, it looks like some firmware bug triggers the issues on MX and some other system libraries that rely on some particular modules. can you please update your firmware to the latest and check again? It may fix your issues.
MXPlayer said:
We have investigated from our end. But, couldn't reproduce the issue.
Have you rooted the device and changed anything on system partition?
In your logs, we have noticed crashes on some other media related system libraries as well.
We have checked on the Google Play data as well. There weren't any similar crashes reported on the nexus player. MX Player uses several android internal modules for performance reasons. Since you are facing the issues with even older versions, it looks like some firmware bug triggers the issues on MX and some other system libraries that rely on some particular modules. can you please update your firmware to the latest and check again? It may fix your issues.
Click to expand...
Click to collapse
No I haven't rooted anything, not even sure how to do that. Just installed the Android TV and added apps. Using a third party launcher called 'Top TV Launcher 2'. Also have VLC and mpv players (both work fine)
When you say firmware, are you referring to the computer BIOS or the Android TV? Both are at the latest version I can find, which is not that easy to find for Android TV. Can you PM me a link to the version you are using and I will try it. Thanks.
dcol said:
No I haven't rooted anything, not even sure how to do that. Just installed the Android TV and added apps. Using a third party launcher called 'Top TV Launcher 2'. Also have VLC and mpv players (both work fine)
When you say firmware, are you referring to the computer BIOS or the Android TV? Both are at the latest version I can find, which is not that easy to find for Android TV. Can you PM me a link to the version you are using and I will try it. Thanks.
Click to expand...
Click to collapse
Are you using the android TV firmware on the PC? Can you provide us more info?
As we have mentioned, MX Player uses several android internal modules to improve the performance. So, if some system module is broken on your Android TV ROM, it will affect the apps that make use of them.
Yes, the Android x86 for PC is the base OS on the PC. I tried other flavors of Android TV and MX Player doesn't work on any of them. I even tried using a different PC with different specs with same results. MX Player crashes as soon as it displays an image or plays any media.
Bump... MX Player still not working. Where do we go from here?
All the Android x86 for PC OS'es are already rooted. None of them will run MX Player. Also Amazon Prime Video and Google Video fails exactly the same way. They must use the same libraries that MX uses. What logs or info can I upload to get this resolved?
All other apps I have tried work fine. VLC, MPV, Archos, ES Player, Kodi.
Any help on this is appreciated. Tell me what logs or info I can upload.
How can I see which modules are crashing? I am not that familiar with the Android OS. Minimal Linux knowledge and a guru with Windows.
Here are the debug logs
dcol said:
How can I see which modules are crashing? I am not that familiar with the Android OS. Minimal Linux knowledge and a guru with Windows.
Here are the debug logs
Click to expand...
Click to collapse
Since it's a crash caused by the android internal libraries, it is very difficult to fix this until or unless we find a way to reproduce. Unfortunately, we couldn't still figure out a way to reproduce the issue. We have even tested on the Android x86 (7.1-r2 from http://www.android-x86.org). But, MX Player works as expected. Have you tried this one on your PC?
Yes I have this is the one I am using right now, so I have to assume it is a hardware/driver related issue. I am using a Dell Optiplex 9010 with i5-3570 4GB memory and 128GB SSD drive. What are the specs of the hardware you have used and I will try to duplicate it?
One other clue is that besides MX Player Pro, Amazon Prime video and Google video also crash as soon as you try to open a video. VLC, MPV, Kodi, ES Player, EXO, and Archos all work fine. I am sure the issues are related.