Related
Hi guys,
I have a problem with my SONY Z5 Compact on Android 6.0 (stock rom from Sony).
After a certain boot time (I don't know the "real" time), videos can't be played. I've tried video on Youtube, Facebook, Dailymotion (an app like Youtube for a different website), 9GAG app, and video cannot be loaded or played.
If I reboot my phone, videos are playable for a while, then the bug is coming back again, and I have to reboot again to be able to play video.
The issue isn't here on Chrome or on the stock Video app (to watch video stored on my memory card) or using YT player small app (a pop-up player, but I prefer the official YT app).
My phone is rooted (SuperSU) and running Xposed.
I've tried to wipe Dalvik using TWRP, but it fixed nothing.
Do you guys have any idea to fix this problem?
Thanks.
EDIT:
I've something that might be useful: I've installed Molotov.tv (a french TV service that is still in beta). I get the following error:
Code:
decoder init failed omx.qcom.video.decoder.avc
After reboot, I'm able to use the player, without errors.
So maybe it's the "whole" problem
Previously posted here
Will an
Code:
adb logcat -v long > problem.txt
or
Code:
adb bugreport
will help ?
Thanks
Thibault1171 said:
Will an or will help ?
Thanks
Click to expand...
Click to collapse
Yep. It's dumping logcats required by developers in order to find the culprit.
However, you may need to uninstall Xposed first (also unroot and/or reflash stock + factory reset) then see if it's still happened.
Sent from my ASUS_Z00A using XDA Labs
Hi guys
I've updated from 32.1.A.1.185 to 32.2.A.0.305 (Android 6.0 to 6.0.1), clean flashing. I've root systemless, same for Xposed, just in case it change something.
The following error is still happening:
There was a problem while playing
Tap to retry
Click to expand...
Click to collapse
I've performed a logcat, I've copy/pasted the full minute log when I've tried playing Youtube video (See here for logcat) . I can provide full logcat if you need it.
I saw this in logcat:
Code:
Line 2945: Unsupported mime audio/alac
Line 2951: Unsupported mime audio/dsd
Line 2957: Unsupported mime video/divx
Line 2963: Unsupported mime video/divx311
Line 2969: Unsupported mime video/divx4
Line 2981: Unsupported mime video/mp4v-esdp
Line 2999: Unsupported profile 4 for video/mp4v-es
Line 5485: Failed to get type for: content://com.sonymobile.tasks.provider (Unsupported URI: content://com.sonymobile.tasks.provider)
Line 14961: Failed to get type for: content://com.sonymobile.tasks.provider (Unsupported URI: content://com.sonymobile.tasks.provider)
Line 18337: Unsupported mime audio/alac
Line 18343: Unsupported mime audio/dsd
Line 18349: Unsupported mime video/divx
Line 18355: Unsupported mime video/divx311
Line 18361: Unsupported mime video/divx4
Line 18367: Unsupported mime video/mp4v-esdp
Line 18373: Unsupported profile 4 for video/mp4v-es
Line 24807: Unsupported mime audio/alac
Line 24813: Unsupported mime audio/dsd
Line 24819: Unsupported mime video/divx
Line 24825: Unsupported mime video/divx311
Line 24831: Unsupported mime video/divx4
Line 24837: Unsupported mime video/mp4v-esdp
Line 24843: Unsupported profile 4 for video/mp4v-es
Does anyone have an idea to fix this?
Thanks a lot
EDIT: file too big for attachment, so you can read it on dropbox : https://dl.dropboxusercontent.com/u/43917893/youtubeissue.txt
EDIT2: I've disabled Xposed, rebooted.
I've logcat while playing a Youtube video, I also have the "unsupported mime video" error, but the video is playing well. So I think this error doesn't rely on anything
So it's Xposed.
Just ignore unsupported mime warnings in logcat. These warnings mean that your hardware doesn't support decoding of audio/video formats as shown.
Sent from my ASUS_Z00A using XDA Labs
Hey,
I don't know if it's xposed, because after every reboot, I'm able to play video for a while (when I was using xposed and root).
If I'm able to play videos for a couple of days, it's certainly this.
But I don't saw anything in logcat. Did you?
Thanks
EDIT (2h later): even with Xposed disabled, I just got the "There was a problem while playing Tap to retry" error
Hey. Xposed is not responsible as the bug occurred while xposed was disabled
Thibault1171 said:
Hey. Xposed is not responsible as the bug occurred while xposed was disabled
Click to expand...
Click to collapse
You said before that you're able to play videos again after disabling Xposed...
Sent from my ASUS_Z00A using XDA Labs
I've edited my post 2 hours later because the bug occurred again :crying:
Seems to be a known bug : http://www.digitaltrends.com/mobile/android-lollipop-problems/8/
Hi, I've wiped cache and dalvik cache this morning (about 13 hours ago)
I've just tried to play a YouTube video, and the error is back....
Sent from my Sony Xperia Z5 Compact using XDA Labs
Phone is up for less than 15 hours. I have to reboot again to be able to watch videos...
Sent from my Sony Xperia Z5 Compact using XDA Labs
Phone is up for 23 hours, and videos are still playable.
It seems that the bug occurs very randomly, not at a stated amount of time (like 8h after reboot, or 12h)
Do you guys have an idea of what can be the problem?
Thanks
Sent from my Sony Xperia Z5 Compact using XDA Labs
Hi, I'm back with the bug :crying:
Sent from my Sony Xperia Z5 Compact using XDA Labs
Mibox3 just received Android TV update to Oreo. MxPlayer now doesn't list files on external storage. No problems though using VLC. Suggestions?
Also, regarding Oreo, any updates on PiP?
Same problem here Updated Mi Box MDZ-16-AB to Oreo and its not working on NTFS or exFAT32 formated USB drives, works fine in FAT32 formated USB drives .
LOG FILE:
E *MX.Directory: Can't open directory '/storage/emulated'. errno=13
E *MX.jni/Files: realpath(/storage/E000A25E00A23C02/MOVIE4-KILLERS[rarbg]) failed. errno=2
oroboros74 said:
Mibox3 just received Android TV update to Oreo. MxPlayer now doesn't list files on external storage. No problems though using VLC. Suggestions?
Also, regarding Oreo, any updates on PiP?
Click to expand...
Click to collapse
Same problem with me, hope the new update for MX Player
Kodi also cannot access files. However X-plore app is able to browse through the files in the hard disk.
Hopefully we can get some support for this problem.
@oroboros74 @sreecalicut @teru2botzu @Emi68
The error no 2 in Linux denotes that there is no such file/directory exists.
This problem is basically due to the firmware bug. In our tests, most of the file managers have failed to list the files. Some file manager may only work if you grant the exclusive access to the USB device. They will mount with their own drivers. But, the files will not be accessible for other apps. Only very few apps are working without any special permissions. We will investigate further for the possible workarounds.
Thirumalai.K said:
@oroboros74 @sreecalicut @teru2botzu @Emi68
The error no 2 in Linux denotes that there is no such file/directory exists.
This problem is basically due to the firmware bug. In our tests, most of the file managers have failed to list the files. Some file manager may only work if you grant the exclusive access to the USB device. They will mount with their own drivers. But, the files will not be accessible for other apps. Only very few apps are working without any special permissions. We will investigate further for the possible workarounds.
Click to expand...
Click to collapse
MXPlayer's main competitor, VLC has figured out how to do this properly with Oreo (VLC also has Oreo's picture-in-picture). For now Mibox users (and other Android TV 8+ users?) can migrate to VLC.
I can confirm X-plore and MiXplorer both work as expected wrt external storage usage.
Hopefully MX Player can catch up to Android O (now that P is coming out)!
I found a workaround to watch the files in MX Player, not a solution but still I can watch my stuff.
I use the ES File Explorer to browse the drive and chose Mx Player as default player, so far it works
Thirumalai.K said:
@oroboros74 @sreecalicut @teru2botzu @Emi68
The error no 2 in Linux denotes that there is no such file/directory exists.
This problem is basically due to the firmware bug. In our tests, most of the file managers have failed to list the files. Some file manager may only work if you grant the exclusive access to the USB device. They will mount with their own drivers. But, the files will not be accessible for other apps. Only very few apps are working without any special permissions. We will investigate further for the possible workarounds.
Click to expand...
Click to collapse
Emi68 said:
I found a workaround to watch the files in MX Player, not a solution but still I can watch my stuff.
I use the ES File Explorer to browse the drive and chose Mx Player as default player, so far it works
Click to expand...
Click to collapse
Even ES file explorer show as blank until or unless you grant the exclusive access to control the USB drive. When you give exclusive access, the drive is mounted using ES's own drivers. Not the system default one. The drive won't be visible to any apps. We will try to escalate this issue with xiaomi team.
Before update 6 version perfectly saw all hard drives with NTFS. After update 8 version writes"cannot recognize drive". This is a mockery of customers. Nothing more to buy XAOMI!
We are investigating further for a possible workaround for this firmware bug. We will try our best to get it resolved at the earliest.
oroboros74 said:
MXPlayer's main competitor, VLC has figured out how to do this properly with Oreo (VLC also has Oreo's picture-in-picture). For now Mibox users (and other Android TV 8+ users?) can migrate to VLC.
I can confirm X-plore and MiXplorer both work as expected wrt external storage usage.
Hopefully MX Player can catch up to Android O (now that P is coming out)!
Click to expand...
Click to collapse
I don't like VLC user interface, the problem is why VLC can read external storage but MX Player can't do that. Until now I am still used MX Player, I open with File Commander, sorry for my poor English.
Update on this issue
Thirumalai.K said:
Even ES file explorer show as blank until or unless you grant the exclusive access to control the USB drive. When you give exclusive access, the drive is mounted using ES's own drivers. Not the system default one. The drive won't be visible to any apps. We will try to escalate this issue with xiaomi team.
Click to expand...
Click to collapse
Update July 6 2018:
The developers of the implementation of the Android TV for the Mi BOX today are working on a new beta and apparently they already fixed the NTFS problem as well as a HDCP 2.2 problem, and they are working on fixing a number of different bugs.
The beta testers group is now closed but, sadly even when the beta where ready the Google Certification takes 1 month minimum
More info:
xiaomi.eu/community/threads/mi-box-3-oreo-ota-update-bugs-post-your-bug-issues-here-please.44773/
@oroboros74 @sreecalicut @teru2botzu @Emi68 @yandexsru
We have added a workaround for this issue & It will be included in the next update.
---------- Post added at 03:28 PM ---------- Previous post was at 03:28 PM ----------
[/COLOR @oroboros74 @sreecalicut @teru2botzu @Emi68 @yandexsru
We have added a workaround for this issue & It will be included in the next update.
Thirumalai.K said:
@[email protected]@[email protected]@yandexsru
We have added a workaround for this issue & It will be included in the next update.
Click to expand...
Click to collapse
That's great news! Any idea on the timeline for that?
oroboros74 said:
That's great news! Any idea on the timeline for that?
Click to expand...
Click to collapse
It's already shared with our Private Testers. We will try our best to make it available at the earliest.
fingers crossed and let's hope fixed soon
Well, after trying to debug why Kodi was not recognizing my 5TB Seagate portable HD's for the past 8 hours I am at least happy to have found this thread and hear that Xiaomi has fixed the problem. Not very happy that we have to wait months for Google certification before we can get a fix though.
I currently have 4 MiBox devices that I use as Kodi media centres. The first two I bought in May and they came with Marshmellow and they both worked perfectly. The last two I purchased in July and they came with Oreo pre-installed, but unlike my Nvidia Shield, the Kodi app will not read the HD with all my media content which makes these devices unusable to me. So now I have to return the last 2 Miboxes to Wal-Mart and wait until an update is available for download. Very disappointed that I am not even able to revert back to the Marshmellow version that worked.
I have now learned something about AndroidTV... I thought it was the greatest thing. Now that I see Google has implemented its DRM into AndroidTV by forcing users to re-format their external HD's to secure downloaded content aka preventing you from copying your paid stuff to other devices...I won't be promoting it anymore. When reformatting your external HD it even tells you that you cannot even use it on another device meaning it's impossible to update your media library, same as the Xbox.
@Thirumalai.K - Is there an easy way to get notified when the next update will be available for everyday users?
HeeneyCS said:
Is there an easy way to get notified when the next update will be available for everyday users?
Click to expand...
Click to collapse
Hopefully, It will be included in the next update. If you are interested to check the private version, feel free to leave an email to [email protected]. We will be happy to share with you. You can check yourself and share the feedbacks.
Mibox just received an update today which seems to have fixed the external drive problem... Still hoping for PiP support from MxPlayer before the next big thing comes out.
I recently found out that a device require widevine L1 to play copyrighted content in HD from streaming services like Netflix and so(no effect on YouTube). And it turns out redmi note 5 pro(whyred) is missing L1 it does have L3(used to play standard quality) and not only this device turns out a lot of devices including likes of one plus 5, pocophone etc have the same problem and to my knowledge this is not something that can be fixed with a software update it somehow related to hardware so i would like your thoughts on this particular issue and if there is any chance that it can be fixed.??
EDIT: Just found a modded version of Netflix with hd enabled don't know if it's fully functional (can't test now) but it's s temporary fix (the Netflix version is old) but here's the link
MediaFire:http://www.mediafire.com/file/i08g9us89xeu1xf/netflixlatest.hdonly.apk/file
CREDIT: Here's the link to the original thread
http://www.mediafire.com/file/i08g9us89xeu1xf/netflixlatest.hdonly.apk/file
NOTE: I am not in anyway associated with the making of the app all the credit is to the op of the above mentioned thread and i will not update this thread regardless of the future development of the modded version of Netflix
there is no way to enable L1 level security on this mobile.... Don't know about other country atleast in India we hardly use Netflix. All are busy in hotstar Jio tv Amazon prime and lastly netflix (very few people)
SunilSuni said:
there is no way to enable L1 level security on this mobile.... Don't know about other country atleast in India we hardly use Netflix. All are busy in hotstar Jio tv Amazon prime and lastly netflix (very few people)
Click to expand...
Click to collapse
Well that could be their marketing strategy but still man it's a little bit upsetting knowing that the user don't have the ability to play videos in HD
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.
Hi,
Is anyone able to get hotstar working on mate 30 Pro? I can't see football videos, live matches and movies and series.
Anyone bypassed widevine for this?
Even I am unable to see it... This is happening even though hotstar is available on Huawei App Galary. Most English content is not available.
Is there any Netflix kind of hack for this?