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.
Related
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
Hello
Since the last update (1.7.38 the one where the notification area player changed) there are some issues I'm facing with long mp3 files. Not bugs but they are pretty annoying!
I listen to long mp3 files like recorded radio shows (2 hours) and audio books and here's what happens in this version that didn't happen before:
1) The notification area player disappears after a short time whereas in the previous version it didn't disappear unless i pressed the "x" button. So that way i cannot resume fast whenever I want to without having to open the app!
2) The mp3 starts at a previous point when the 1) happens and i have to resume it from the player itself (i have to open the app again) (e.g. I stopped it at 1:30:27 and when i resume from the app it starts at 1:00:00 and not where I paused it)
Please fix those issues. or just restore them to how they were
Otherwise the player rocks and it's op with subtitle sync and all those encoders! (imagine i couldn't even play some of the long mp3 files in other players!!)
Thanks and keep up the good work! cheers!
I think I was polite and described my problem. Why NO answer???
It will be now!
well done thank you!
Very strange issue, but everything is possible, try lastest beta version.
I will try to reproduce this on my phone and I will come to let you know.
problem continues!
josuearisty said:
Very strange issue, but everything is possible, try lastest beta version.
I will try to reproduce this on my phone and I will come to let you know.
Click to expand...
Click to collapse
Still after update on new version and reinstalling 2-3 times no fix at all ! can I find and use the version before 1.7.38 which worked well?
beerovios said:
Still after update on new version and reinstalling 2-3 times no fix at all ! can I find and use the version before 1.7.38 which worked well?
Click to expand...
Click to collapse
Looks like app crashed while playing mp3. Would you try other decoders (HW, HW+, SW)?
Typically HW decoder would not crash at least.
You can select default decoder based on file extension on Settings > List > File extension.
Hello, since the last update the background play option dont work.
I play a video from web (stream) and turn off my phones display, after 4-5 minutes the player close itself.
MX Player Free
1.9.3 ARM V7NEON
Xperia X F5121
Android 7.1.2
The previous version works fine on the same phone and settings.
steve233 said:
Hello, since the last update the background play option dont work.
I play a video from web (stream) and turn off my phones display, after 4-5 minutes the player close itself.
MX Player Free
1.9.3 ARM V7NEON
Xperia X F5121
Android 7.1.2
The previous version works fine on the same phone and settings.
Click to expand...
Click to collapse
kindly collect a bug report immediately after the issue & share here.
without it, it will be very difficult to understand the root cause of the issue.
where i have to send it?
Fixing MX player background play issue in Oreo
With the Oreo update every app now has Individual power saving settings. So if an App is using intelligent power saving Android will aitomatically shut down back ground running after a certain period of time or if multiple apps start running at the same time. So if you play Youtube while running MX player, Android power management can shut it down.
To fix the background play issue I tried the following
1. Open settings
2. Go to App Management
3. Find and open Mx player
4. Tap on power saving
5. Change from Intelligent control to Allow running in background
This worked for me.
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.
I use the next and back buttons on my Bluetooth headset to act as fast forward and rewind.
For this purpose, I have enabled 'Media buttons' and 'Next/Prev → FF/Rew' in the settings,
but when the app is running in the background, 'Next/Prev → FF/Rew' does not work.
When it is in the background, it is not converted and simply works as 'Next/Prev'.
Also, when the app is in the foreground, it will work as 'FF/Rew' as expected.
Note that the 'Double/Triple Press → Next/Prev' option has nothing to do with this behavior,
and will behave as described above whether it is on or off.
Additionally, the above is how it works in the conventional video player. If you open an audio file in the 'NEW PLAYER', it will behave like "Next/Prev" regardless of the app status.
Huawei Mate 10 Pro BLA-L29 EMUI 10.0.0.180
MX Player Pro 1.35.8
SONY MDR-AS600BT
HI @panam510 ,
Please try this build and report back if this fixes your problems.
https://mxplayer.s3.amazonaws.com/test/pro/Player_pro-neon_direct_v8-release-36ef9331ea.apk
MXPlayer said:
HI @panam510 ,
Please try this build and report back if this fixes your problems.
https://mxplayer.s3.amazonaws.com/test/pro/Player_pro-neon_direct_v8-release-36ef9331ea.apk
Click to expand...
Click to collapse
Thanks for the fix!
That build worked fine as 'FF/Rew' both in the foreground and in the background (in Conventional Video Player).
Hi, i had the same problem and this apk fixed it, many thanks!
I noticed that now a few official updates have been launched on GPlay - but this bug is still present in the newest version, therefore i still have to use this slightly outdated APK. Is it going to be fixed on official installation in Google Play?