[Q] Integrating MX Codecs into AOSP build - MX Player

Hi,
I'm having troubles using the stock JB Android 4.1.2 play m3u8 live streaming. Issue described in:
http://stackoverflow.com/questions/26181554/stock-android-h264-decoder-failing-on-m3u8-url-files
After some debugging, seems to me that only the "baseline profile" is supported by the stock SW codec (frameworks/av/media/libstagefright/codecs/on2/h264dec), while the stream has the entropy_coding_mode_flag set (i.e. it is a CABAC encoding - I'm not an expert about H264, but I read it's a rather different encoding scheme).
So, I was wondering if it was ever possible to entirely replace the libstagefright/codecs provided with stock AOSP with the SW codecs of MX Player, which seems to be working fine on the same m3u8 stream.s.
Any idea if ever feasble and, if so, about how to proceed?
thanks
Fabio

ffxx68 said:
So, I was wondering if it was ever possible to entirely replace the libstagefright/codecs provided with stock AOSP with the SW codecs of MX Player, which seems to be working fine on the same m3u8 stream.s.
Any idea if ever feasble and, if so, about how to proceed?
Click to expand...
Click to collapse
E.g. I was thinking if that was possible by simply hacking the codec declarations in
device/.../.../media_codecs.xml
or if a more complex code integration in AOSP is required. Note - I can rebuild AOSP for my device.
Any advice welcome, anyway.

I think its not only a matter of software, hardware must supports it.

ffxx68 said:
E.g. I was thinking if that was possible by simply hacking the codec declarations in
device/.../.../media_codecs.xml
or if a more complex code integration in AOSP is required. Note - I can rebuild AOSP for my device.
Any advice welcome, anyway.
Click to expand...
Click to collapse
Even if you declare, if it's not supported by your gpu then it will simply through a error.
Mx player uses the hardware decoders included with your system. If it's not supported ffmpeg is used. But, it will use the cpu to decode the video.
So, there won't be much benefits.

ktsamy said:
Even if you declare, if it's not supported by your gpu then it will simply through a error.
Mx player uses the hardware decoders included with your system. If it's not supported ffmpeg is used. But, it will use the cpu to decode the video.
So, there won't be much benefits.
Click to expand...
Click to collapse
I know.... actually, I didn't know ffmpeg was the underlying SW decoder.
I'm afraid my HW GPU doesn't support H264 coded in CABAC. while it does decode seamlessly CAVLC (two flavors of H264 encoding... I found out.).
There will be a benefit in having SW codec, so - at least screen doesn't blank out
I noticed it takes 30-35% CPU while using SW MX Player on those streams. Still acceptable (I don't think GPU will use greatly less power). Final quality is definitely OK.
Any suggestion about how to proceed with ffmpeg codec integration in AOSP? What are the main integration points to consider?
thanks
Fabio

ffxx68 said:
I noticed it takes 30-35% CPU while using SW MX Player on those streams. Still acceptable (I don't think GPU will use greatly less power).
Click to expand...
Click to collapse
I'd just like to note that generally, GPU rendering reduces power consumption dramatically. For example, a SW rendered 30min video will use 25% of battery life on a Nexus 5. The same video reencoded to a GPU-supported codec will use closer to 10% battery.

ffxx68 said:
...
Any suggestion about how to proceed with ffmpeg codec integration in AOSP? What are the main integration points to consider?
...
Click to expand...
Click to collapse
Just for the sake of informing the audience here, I think I found a very good starting point for this, here:
https://github.com/omxcodec/stagefright-plugins

ffxx68 said:
Just for the sake of informing the audience here, I think I found a very good starting point for this, here:
https://github.com/omxcodec/stagefright-plugins
Click to expand...
Click to collapse
I'm working on the porting of the above to my AOSP, but found issues with the integration.. There's something not going well with picture quality. Still debugging (https://groups.google.com/forum/#!topic/android-x86/mTnTe39D5Co).
Meanwhile, let me ask here whether there's any documentation, about how to access access the MPlayer SW codecs from other apps, or AOSP libstagefright.
thanks
Fabio

ffxx68 said:
I'm working on the porting of the above to my AOSP, but found issues with the integration.. There's something not going well with picture quality. Still debugging (https://groups.google.com/forum/#!topic/android-x86/mTnTe39D5Co).
Meanwhile, let me ask here whether there's any documentation, about how to access access the MPlayer SW codecs from other apps, or AOSP libstagefright.
thanks
Fabio
Click to expand...
Click to collapse
FYI
Mx player is free can be distributed with rom without any modifications.
https://sites.google.com/site/mxvpe...e-or-preinstall-on-commercial-Android-device-
You can call mx player free/pro through the api
Read the following link for more information
https://sites.google.com/site/mxvpen/api

Related

XVID and AVI on the G1

there hasn't been an app on the market that could play .avi's. could there be a hack to add the divx codec to the phone or is it just not possible for the phone to play xvid files?
.avi is a container format for video streams, so beyond an app being able to open the avi, codecs need to exist to decode the streams inside.
Android's multimedia architecture is built around PacketVideo OpenCORE. Excerpt from this document on interacting with OpenCORE:
There are several ways to integrate a codec into the PV OpenCore multimedia framework
including as a compressed media I/O component, as a node, and as an OpenMax component
integrated into the OpenMax codecs nodes that are part of the framework. Many codecs,
especially those that include hardware acceleration, implement the OpenMax IL interface making
the OpenMax interface the most straightforward method of integration in those cases.
Click to expand...
Click to collapse
Try CorePlayer..
EDIT: Sorry, did'nt recognize this is Android section Anyway, would be nice to see CorePlayer or TCPMP for Android platform!
Regards,
Carty..
Carty said:
Try CorePlayer..
EDIT: Sorry, did'nt recognize this is Android section Anyway, would be nice to see CorePlayer or TCPMP for Android platform!
Regards,
Carty..
Click to expand...
Click to collapse
If you go to www.coreplayer.com it tells you that its coming soon for the Iphone and Android.
lazee_smurf said:
If you go to www.coreplayer.com it tells you that its coming soon for the Iphone and Android.
Click to expand...
Click to collapse
20$ for a video player? no thanks...
devsk said:
20$ for a video player? no thanks...
Click to expand...
Click to collapse
I love how some people expect all software to be free.
maxdamage2122 said:
I love how some people expect all software to be free.
Click to expand...
Click to collapse
not all, but some. I will pay for super good video editing software with some cool effects. But playing video is very basic.
XviD decompression on a 400 MHz CPU in a Java-like VM.
I lol'd. We'll see.
Gary13579 said:
XviD decompression on a 400 MHz CPU in a Java-like VM.
I lol'd. We'll see.
Click to expand...
Click to collapse
Don't forget that the screen is small. In fact, you can test it out yourself. Pick a video of your choosing, fire up avidemux, choose IPOD preset and encode it at 320x240. Play it on G1. Plays wonderful quality and perfectly smooth.
Don't underestimate the graphics power of this device. It can do more complex h264 (xvid's and divx's successor) perfectly fine.
Gary13579 said:
XviD decompression on a 400 MHz CPU in a Java-like VM.
I lol'd. We'll see.
Click to expand...
Click to collapse
Not at all impossible to decode XviD (if an openmax codec is implemented), given realistic mobile-oriented resolutions and bitrates.
devsk said:
Don't forget that the screen is small. In fact, you can test it out yourself. Pick a video of your choosing, fire up avidemux, choose IPOD preset and encode it at 320x240. Play it on G1. Plays wonderful quality and perfectly smooth.
Don't underestimate the graphics power of this device. It can do more complex h264 (xvid's and divx's successor) perfectly fine.
Click to expand...
Click to collapse
I highly doubt h264 decoding is done within the Davlik VM. Hell, there may even be hardware acceleration for that. But at the moment, any DivX/XviD player would be coded in Java, making is quite a bit slower and harder to do than the h264 version.
Gary13579 said:
But at the moment, any DivX/XviD player would be coded in Java, making is quite a bit slower and harder to do than the h264 version.
Click to expand...
Click to collapse
The UI would be Java, but the codec itself would be a c/c++ implementation that hooked into opencore.
jashsu said:
The UI would be Java, but the codec itself would be a c/c++ implementation that hooked into opencore.
Click to expand...
Click to collapse
Which, currently in Android, would be impossible?
the N95 plays divx/xvid files (just any that you'd find on a computer) perfectly using Coreplayer. I would like to think that the G1 could handle the same files just as well with the same software, given that it has 3 times as much ram and a 30% faster Qualcomm processor...unless the G1 suffers the same problem as every Windows Mobile device by HTC currently on the market.
I do hope not.
devsk said:
not all, but some. I will pay for super good video editing software with some cool effects. But playing video is very basic.
Click to expand...
Click to collapse
so is bread&milk...
leoni1980 said:
the N95 plays divx/xvid files (just any that you'd find on a computer) perfectly using Coreplayer.
Click to expand...
Click to collapse
Because it's written in a native language and runs directly on the cpu and gpu (as opposed to inside a VM)
vihil said:
so is bread&milk...
Click to expand...
Click to collapse
you are comparing bread&milk with features on G1...You need to get a life...
maxdamage2122 said:
I love how some people expect all software to be free.
Click to expand...
Click to collapse
20 bucks is a ripoff whatever way you look at it. I love people who assume people want it for free instead of for a reasonable price.
devsk said:
you are comparing bread&milk with features on G1...You need to get a life...
Click to expand...
Click to collapse
Maybe we all do...
I'm sure someone has already worked their magic and created a video player for Android. All they are waiting for is for Google to allow them to charge for the App on the marketplace.

MX Player and ChromeCast

This is a continuation of the original thread on Google Groups.
Link to original thread: https://groups.google.com/d/topic/mx-videoplayer/Xgb6KKj95vg/discussion
Thanks for starting this up here. Any updates on Chromecast support?
captbunzo said:
Thanks for starting this up here. Any updates on Chromecast support?
Click to expand...
Click to collapse
THIS is the Chromecast solution I feel I have been waiting an eternity for. Best of luck with ongoing development...
Well, Miracast accomplishes a similar result, but as it's live transcoding of your entire screen, it would only have decent video playback on higher-end devices. That and Miracast means you can't do a 2nd task on the phone when the video plays.
From my understanding of Chromecast support right now, Google is slowly rolling out support for different formats and file containers. Not sure how long this will take. MX Player transcoding should mean that anything would be playable, assuming your device can handle live transcoding.
CDB-Man said:
From my understanding of Chromecast support right now, Google is slowly rolling out support for different formats and file containers. Not sure how long this will take. MX Player transcoding should mean that anything would be playable, assuming your device can handle live transcoding.
Click to expand...
Click to collapse
Google is slowly rolling out support for different formats and file containers
Where is the proof or where did you find that
ALSo. I wanted to ask.
Could you please not do one step at a time?
E.g add Chromecast support but for NORMAL. E.g. Basic support. For normal formats which work. Like avia media player.
Thank you
Supported formats: https://developers.google.com/cast/docs/media
As to your question about adding Chromecast support, that would be a question for the developer to answer. @bleu8888
Hopefully we will see this happening any time soon.
Thank you in advance, because we all know MX is the best out there.
Sent from my SM-N900 using Tapatalk
Ok, so what exactly does this mean? Is the developer working on Chromecast support? Any ETA for when it should be expected?
Yes he is working on it; no an ETA has not yet been indicated. Thing is, the developer wants ALL videos to work on Chromcast; this means MX Player must do live transcode on any format that Chromecast doesn't support.
CDB-Man said:
Yes he is working on it; no an ETA has not yet been indicated. Thing is, the developer wants ALL videos to work on Chromcast; this means MX Player must do live transcode on any format that Chromecast doesn't support.
Click to expand...
Click to collapse
Any update to the progress or challenges? eagerly awaiting any news on this, as it would be super to unlock these features through MX player and ChromeCast!
CDB-Man said:
This is a continuation of the original thread on Google Groups.
Link to original thread: https://groups.google.com/d/topic/mx-videoplayer/Xgb6KKj95vg/discussion
Click to expand...
Click to collapse
What I don't understand is WHY don't you do 1 step at a time?
Why cant you simply right now, add the NORMAL chrome cast features, just MP4 files first.
and then later work on every single file format and transcoding?
Im sure many people would like this option?
Is it possible for a modern quad-core ARM phone/tablet to transcode video formats on the fly? I love MX because it literally plays anything I throw at it, but I don't know if this is the same as transcoding these different formats for casting.
Sent from my SGP511 using Tapatalk
@Krisshp Don't know; it was the developer's decision.
@CAL7 well, for 10-bit I would assume it can't handle it, considering only the more recent phones were able to decode it. For 8-bit, it might be possible if the bitrate isn't too high.
CDB-Man said:
@Krisshp Don't know; it was the developer's decision.
@CAL7 well, for 10-bit I would assume it can't handle it, considering only the more recent phones were able to decode it. For 8-bit, it might be possible if the bitrate isn't too high.
Click to expand...
Click to collapse
Cant you give this suggestion (which many ACTUALLY want) to the developer? and take it 1 step at a time?...
Thanks
there are many different options out there to use at the moment if you want to stream to chromecast. I agree with the developer having his standards of exactly what he wants his app to be able to do before releasing it... Kudos to him! :good:
I echo the same sentiment of playya.
I agree with you guys, no need to rush, it must come out when ready... But it would be very nice to be updated about the progress, just to know if we can expect it this month or in december 2015
JerryBels said:
I agree with you guys, no need to rush, it must come out when ready... But it would be very nice to be updated about the progress, just to know if we can expect it this month or in december 2015
Click to expand...
Click to collapse
...... Or just leave us in the dark, alone, crying about our insecurities, struggling to overcome our fear of the unknown, but in the end doomed to the abysses of hell. That's cool too.
Glad to see that there is a possibility of seeing a Chromecast compatible MX Player in the future. Kudos to the devs for wanting to keep the standards up. If you need a beta tester count me in. I have helped with other apps in development. Do love MX Player the best I 've found. Just updated to pro to hopefully help with Chromecast development.

[DEV/THINKTANK] VC1/MPEG2/WMA hardware decode for the Nexus Player

Hello Fellow Nexus Payer Owners! I have started a dev project to get MPEG2, VC1, and WMA hardware decoding working on the Nexus Player in hopes together we can enable this. I have never attempted anything more than built roms from asop with slight modification so Im going to need some assistance on this project
Description of Issue
The Nexus Player had great possibilities had it not been rushed to market with buggy applications and lack of hardware codec licencing. To me this product would be the perfect HTPC if Plex had worked with 5.1 audio (DTS/AC3) pass-through and MPEG2 hardware decoding for use with my HDHomeRun Prime for live TV. But Asus or Google dropped the ball as this is not enabled so the HDHomeRun View app has to fall back to software decoding which make the stream very choppy. Most cable companies are still using MPEG2 for now.
Here is a discussion on the Nexus Player over at the Silicon Dust's Forums:
http://www.silicondust.com/forum2/viewtopic.php?f=81&t=17894
Research into MPEG2 on Android
Searching Around the fourms I stumbled on this post enabling hardware decoding on the Nexus 7 2013 and other ARM devices.
http://forum.xda-developers.com/showthread.php?t=2517925
It seems they pulled libOmxCore.so from Cyanogenmod 11 on various devices and edited the media_codecs.xml. Ive contacted both contributors in hope I can discuss this with them. Im not sure there is any x86 CM12 Devices we can extract the libOmxCore.so from to test on the NP and thats if they have even merged they media codecs in CM12 yet.
Here are some projects and discussion for building ffmpeg into android which may enable MPEG2 decoding:
http://stackoverflow.com/questions/4725773/ffmpeg-on-android
https://github.com/appunite/AndroidFFmpeg
https://github.com/guardianproject/android-ffmpeg
Ffmpeg on Android x86
https://software.intel.com/en-us/android/blogs/2013/12/06/building-ffmpeg-for-android-on-x86
As of right now Im just gathering information to get started on this project so anyone with any input will be appreciated.
Once I get my Nexus Player the way I want it and if there is a custom recover (ahemm TWRP) I will post my personal build for you to try out.
*EDIT* Google has pushed Android 5.0.1 (build LRX22C) to AOSP with reports that it has fixes for "video issues". Fingers crossed they enabled MPEG2 hw decoding so I don't have to
XDA:DevDB Information
VC1/MPEG2/WMA hardware decode on the Nexus Player, Device Specific App for the Nexus Player
Contributors
WhiteWidows, whitewidows, god_md5, kennylam
Version Information
Status: Testing
Created 2014-12-03
Last Updated 2014-12-03
Very very happy to see I'm not the only one interested in this feature. I have a lot of dvd movies muxed into mkv in my plex server. My plex server does not have the power to transcode so to get Nexus player to direct play this is a huge step forward. Thanks!
Skickat från min GT-I9505 via Tapatalk
As an Nexus Player owner, and HDHomeRun Prime user, I'm also very interested in MPEG2 HW decoding.
For now I'm using my ADT-1's for TV... But who knows if Google will keep updating them... so far they are still on preview 5.0 builds.
Me too..
Add me to the list of people interested in this. There is a ton of MPEG2 content out there - US broadcast TV is all MPEG2. Enabling MPEG2 would open a ton of possibilities for this device.
Glad I wasn't the only one interested in this. I think its ridiculous to make a so called TV devices with no mpeg hw decoding
Update is I have been trying to build ffmpeg in to lollypop but it keeps failing. I going to at least try to build lollypop from source (arm) first because its been since jellybean I have done it. I'm a bit rusty ?
Plus one interested.any news?
Sent from my Nexus 7 using XDA Free mobile app
I'm still working on it I got x86 android to build. But with ffmpeg they fail. Work and holidays have been consuming most of my time but I try to put some time into it tomorrow.
We still need a custom recovery to simplify flashing
http://forum.xda-developers.com/nexus-player/general/nexus-player-mpeg2-hardware-decoding-t2996377
In the thread above, they claim that mx player is able to hardware decode mpeg2 with intel code plugin. Has anyone looked into this for a solution?
xomikronx said:
http://forum.xda-developers.com/nexus-player/general/nexus-player-mpeg2-hardware-decoding-t2996377
In the thread above, they claim that mx player is able to hardware decode mpeg2 with intel code plugin. Has anyone looked into this for a solution?
Click to expand...
Click to collapse
When the hdhomerun view app/googles live TV app launches a mpeg-2 stream which in turn uses androids default media player. There is no option to use MX or change to that. I wouldn't want to use MX as the over lays for the guide would not work. I tried another build last night but again it failed. Lat time I built android was back in the ICS daysband never with ffmpeg. I not sure I'm even going about this the correct way.
I just noticed a thread about a CM11 port for the GeeksPhone Revolution which runs an Intel® Atom™ processor Z2560. The processor is 32bit x86, but usually these things are backwards compatible. Maybe you can pull binaries from that image? I'd post a link to the thread and associated image, but since this is my first post on these forums it won't let me.
Any updates on this?
Did this project die?
No....its just my builds always fail compiling with ffmpeg into 5.0. I'm stuck. So if anyone can help !e out it would be appreciated

[Bug report] HW and HW+ decoder lags on some videos

1. Samsung Galaxy Tab Pro 10.1 wifi (SM-T520)
2. Android version: Kitkat 4.4.4
3. Official CyanogenMod 11 nightly 11-20141209
4. When I play some videos and using HW and HW+ decoder, I experience video is out of sync. It looks like there's frame dropping. Problem also exists on my Xperia V with latest CM. I use on both devices custom codecs from this forum. While using SW decoder everything is fine.
Logs are here
https://www.dropbox.com/s/uqvra9vqkefynrl/report_2014-12-13_085318.zip?dl=0
Yeah, I was constantly having the same bug on my stock Android 5.01 Nexus 7 2013. HW mode is not even available for most of my high quality mkvs, while in HW+ mode playback is choppy. In the end the solution was painful, but simple: I gave up Mx player pro and returned to bs player pro. Playback is a lot smoother now with HW mode in bs player. After more than a year with mx player I must say it's an extremely overrated piece of software with a non-existant price/performance ratio. While I like a lot it when it works, it has too many annoying bugs to recommend it anymore.
Mihai B said:
Yeah, I was constantly having the same bug on my stock Android 5.01 Nexus 7 2013. HW mode is not even available for most of my high quality mkvs, while in HW+ mode playback is choppy. In the end the solution was painful, but simple: I gave up Mx player pro and returned to bs player pro. Playback is a lot smoother now with HW mode in bs player. After more than a year with mx player I must say it's an extremely overrated piece of software with a non-existant price/performance ratio. While I like a lot it when it works, it has too many annoying bugs to recommend it anymore.
Click to expand...
Click to collapse
I just checked BS Player (free version) and on my Galaxy Tab Pro 10.1 it was just as choppy as MX Player. Maybe there's a bug in CM 11?
Did it previously work on older versions of your ROM? If yes, then it's likely a ROM issue.
@Mihai B mind posting the media info of the problem videos in question? Was this on stock ROM for the 2013 N7?
CDB-Man said:
Did it previously work on older versions of your ROM? If yes, then it's likely a ROM issue.
@Mihai B mind posting the media info of the problem videos in question? Was this on stock ROM for the 2013 N7?
Click to expand...
Click to collapse
Yes, I am using stock Android 5.01 ROM with a Nexus 7 2013 WiFi only, 32 GB, rooted with chainfire's autoroot, stock recovery, waited for OTA to arrive, factory reset with clear cache partition after applying the update. Worth mentioning that on KitKat 4.4.4. playback was much more smoother on the same files, with the same settings in MX Player. I only have a few applications, nothing that could conflict with MX Player. Here you will find an example of a file lagging when played. Basically every high quality mkv stutters like hell. If you need a file, I can upload it somewhere.
Thank you for your help!
Mihai B said:
Yes, I am using stock Android 5.01 ROM with a Nexus 7 2013 WiFi only, 32 GB, rooted with chainfire's autoroot, stock recovery, waited for OTA to arrive, factory reset with clear cache partition after applying the update. Worth mentioning that on KitKat 4.4.4. playback was much more smoother on the same files, with the same settings in MX Player. I only have a few applications, nothing that could conflict with MX Player. Here you will find an example of a file lagging when played. Basically every high quality mkv stutters like hell. If you need a file, I can upload it somewhere.
Thank you for your help!
Click to expand...
Click to collapse
Is it happens with HW?
If it's so,
Have you tried the same video on Stock Player?
The same should happen with stock player too as HW basically uses android's standard mediaplayer interface.
So, if it stutters on HW, Possibly there might be some issues with in the rom itself.
Have you tried SW decoder?
It might work well since it's based on ffmpeg
HW mode doesn't work at all (mx player says decoder is not supported or something like this), therefore stock player is unable to play it, too. Battery drain is huge with SW mode, what's the purpose of buying applications like MX player that offer accelerated HW decoding then? But just FYI, software mode plays the file flawlessly. The ROM is the purest Android experience one can get right now, so this should not be a problem either. If HW+ mode doesn't work as it should even on stock Android, with developer previews available since months, I don't want to think what will happen with custom ROMs.
We are far away from highly compressed formats like divx, xvid or wmv, high definition content is the present and it seems Mx player with its HW+ decoder can't keep the pace.
I wrote about these problems ever since Android 5 was officially launched a month ago and still no fix was issued.
Mihai B said:
HW mode doesn't work at all (mx player says decoder is not supported or something like this), therefore stock player is unable to play it, too. Battery drain is huge with SW mode, what's the purpose of buying applications like MX player that offer accelerated HW decoding then? But just FYI, software mode plays the file flawlessly. The ROM is the purest Android experience one can get right now, so this should not be a problem either. If HW+ mode doesn't work as it should even on stock Android, with developer previews available since months, I don't want to think what will happen with custom ROMs.
We are far away from highly compressed formats like divx, xvid or wmv, high definition content is the present and it seems Mx player with its HW+ decoder can't keep the pace.
I wrote about these problems ever since Android 5 was officially launched a month ago and still no fix was issued.
Click to expand...
Click to collapse
HW+ uses the same native codecs to decode. Only difference is that H/W uses android media framework and mx player uses its own media framework which itself depends on another android library. So, if any issues on codec configuration will affect both.
MX Player was working well on L preview (except the last one in which google hasn't released the sources).
Do you think your device doesn't has enough power to decode a 720p video natively?. Then, have ever thinked about why your stock player can't play the video?
Just google. MX Payer is not the only product. You will see the very large list of complaints all around the world. You are supposed to blame on Google for the semi baked ROM rather than MX Player.
Look at the article from famous Android Police Portal
http://www.androidpolice.com/2014/1...o-playback-issues-after-updating-to-lollipop/
ktsamy said:
HW+ uses the same native codecs to decode. Only difference is that H/W uses android media framework and mx player uses its own media framework which itself depends on another android library. So, if any issues on codec configuration will affect both.
MX Player was working well on L preview (except the last one in which google hasn't released the sources).
Do you think your device doesn't has enough power to decode a 720p video natively?. Then, have ever thinked about why your stock player can't play the video?
Just google. MX Payer is not the only product. You will see the very large list of complaints all around the world. You are supposed to blame on Google for the semi baked ROM rather than MX Player.
Look at the article from famous Android Police Portal
http://www.androidpolice.com/2014/1...o-playback-issues-after-updating-to-lollipop/
Click to expand...
Click to collapse
Thank you for your answer, Ktsamy.
My device is powerful enough to play a 720p video, as in KitKat there were no problems in doing this. I know about the issues mentioned in the link you posted, but they refer to Android 5.0, and as far as I know, this is one of the reasons Google halted 5.0 OTAs, fixed some of the bugs reported by early adopters and then updated most of the devices directly to 5.01. The video issues found in Nexus 7 2013 were supposed to be fixed in 5.01.
So what has to be done? Should we all patiently wait for Google to eventually fix the native android codecs/libraries problems you say they generated in Lollipop? And while we are waiting, applications like MX Player and other similar products are right now useless for the unlucky ones who have Android L installed?
I mean: ok, we do have a problem, but what about everyone (Google, paid app developers) working on a solution instead of blaming each other?
Mihai B said:
Thank you for your answer, Ktsamy.
My device is powerful enough to play a 720p video, as in KitKat there were no problems in doing this. I know about the issues mentioned in the link you posted, but they refer to Android 5.0, and as far as I know, this is one of the reasons Google halted 5.0 OTAs, fixed some of the bugs reported by early adopters and then updated most of the devices directly to 5.01. The video issues found in Nexus 7 2013 were supposed to be fixed in 5.01.
So what has to be done? Should we all patiently wait for Google to eventually fix the native android codecs/libraries problems you say they generated in Lollipop? And while we are waiting, applications like MX Player and other similar products are right now useless for the unlucky ones who have Android L installed?
I mean: ok, we do have a problem, but what about everyone (Google, paid app developers) working on a solution instead of blaming each other?
Click to expand...
Click to collapse
all lollipop devices aren't affected.
Reportedly Google is aware of this issue.
second thing, Since Google is controlling the ROM, app developers can't fix the issue lies on ROM. But, developers can look for temporary workarounds to resolve the issue. But. No guarantee that all bugs will have some workarounds.
Well, stock 5.0 ROM for Nexus devices is fine, so it might just be a recompile or other issue for 5.0.1. @bleu8888 mind taking a look to see if it's just a simple versioning issue with 5.0.1? The updated OTA was released a few days ago for Nexus devices.
CDB-Man said:
Well, stock 5.0 ROM for Nexus devices is fine, so it might just be a recompile or other issue for 5.0.1. @bleu8888 mind taking a look to see if it's just a simple versioning issue with 5.0.1? The updated OTA was released a few days ago for Nexus devices.
Click to expand...
Click to collapse
CDB-Man, the problem was present on 5.00 as well. I flashed the factory image, posted info about the stuttering in the Android 5 topic, Ktsamy pointed me and others affected by this problem to the same link he provided yesterday. In the mean time Google halted the OTAs for 5.00, fixed some bugs, including the one with the video lag present on the Nexus 7 2013 and directly released OTA 5.01. Unfortunately the stuttering in playing high quality mkvs is still present in MX Player, no matter if the ROM is stock 5.00 or 5.01.
Mihai B said:
CDB-Man, the problem was present on 5.00 as well. I flashed the factory image, posted info about the stuttering in the Android 5 topic, Ktsamy pointed me and others affected by this problem to the same link he provided yesterday. In the mean time Google halted the OTAs for 5.00, fixed some bugs, including the one with the video lag present on the Nexus 7 2013 and directly released OTA 5.01. Unfortunately the stuttering in playing high quality mkvs is still present in MX Player, no matter if the ROM is stock 5.00 or 5.01.
Click to expand...
Click to collapse
If it's fixed it supposed to playable in H/W decoder or by Stock Video Player. But, none of these are working.
Can you do the following?
Long Press the video, Play using H/W decoder. if it says H/W decoder is not supported or automatically switches to S/W, close the playback. Collect the logs & upload here.
BTW, According to leaks Google is planning for another major update to 5.1 in Feb 15 to address the major bugs exists in lollipop
---------- Post added at 09:22 PM ---------- Previous post was at 09:20 PM ----------
CDB-Man said:
Well, stock 5.0 ROM for Nexus devices is fine, so it might just be a recompile or other issue for 5.0.1. @bleu8888 mind taking a look to see if it's just a simple versioning issue with 5.0.1? The updated OTA was released a few days ago for Nexus devices.
Click to expand...
Click to collapse
As I have said already, the issue doesn't appear on all nexus devices. Most of the reports are from Nexus 7.
Thanks again, ktsamy, for your help. I was not very sure about how to collect the log, hope it is okay. It said decoder not supported, then switched to sw.
Same here on stock 5.0.1. But the same player is smooth on 4.4.4. So I guess it's Google's problem.
Ktsamy, have you found the time to check the log I have posted a few days ago?
I have an nvidia shield tablet LTE and can confirm HW+ makes video stutter on my device. Was working perfectly prior to the lollipop update. Hope Google, MX Devs or whoever can resolve the issue. Noticed that SW mode is a HUGE battery drain!
I guess it seems that Google really rushed the release of Lollipop.
Mihai B said:
Ktsamy, have you found the time to check the log I have posted a few days ago?
Click to expand...
Click to collapse
@Mihai B @isamu99 @kneep
I've tried some high resolution videos on Nexus 7 2013 5.0.1 but can't reproduce this issue.
So it looks not like happening with all videos.
So I've tried download one of files having this issue -- The.Secret.Life.of.Walter.Mitty.2013.BluRay.720p.x264.DTS-HDWinG.mkv -- but it is taking forever.
Would someone send download link or torren file having enough seed?
bleu8888 said:
@Mihai B @isamu99 @kneep
I've tried some high resolution videos on Nexus 7 2013 5.0.1 but can't reproduce this issue.
So it looks not like happening with all videos.
So I've tried download one of files having this issue -- The.Secret.Life.of.Walter.Mitty.2013.BluRay.720p.x264.DTS-HDWinG.mkv -- but it is taking forever.
Would someone send download link or torren file having enough seed?
Click to expand...
Click to collapse
Bleu8888, I have PM'd you with the link to the file. If you can't download it, please let me know.

i can't play hevc 10 bit video via hardware decoding

sorry for my poor english,i am chinese
i tried vlc,mx player,plex,kodi,i can only play low bitrate file by software decoding(cpu will run hot,and rarely some artifact),can't use hardware decoding.
snapdragon 821 should be able to play 4k hevc 10bit file,but i can't even use hardware decoding to play 1080p hevc 10 bit file ,
even snapdragon 820 can play this
i can play 8 bit hevc file via hardware decoding,but not 10 bit file
i am using stock rom,can't unkock bootloader(second-hand verizon),system is android 8.0.0 November security patch
i just want to know is this locked in hardware,or software
and why google block it,i just cant understand why
since many people have installed custom rom here,so i think this is the best place to ask
i am new her so i cant ppost link,just google Jellyfish Bitrate Test Files
plz try jellyfish-10-mbps-hd-hevc-10bit.mkv or other 10bit file, if your phone can play it,it should be using hardware decoding
try using logcat, while trying to play the video... it will probably tell u whether or not the video codec is supported or not....
it could be lacking of being implemented is software or hardware. hard to say...
why is this so important anyway?
note: it did play in MX player, but their so calld 'custom codec' is optimized for arm-v7a neon... so way out of date for our hardware is was sluggish on playback
nine7nine said:
try using logcat, while trying to play the video... it will probably tell u whether or not the video codec is supported or not....
it could be lacking of being implemented is software or hardware. hard to say...
why is this so important anyway?
note: it did play in MX player, but their so calld 'custom codec' is optimized for arm-v7a neon... so way out of date for our hardware is was sluggish on playback
Click to expand...
Click to collapse
i also post a issue in google's github page
github.com/google/ExoPlayer/issues/3537
got some log from vlc
may have something to do with ExoPlayer and mediacodec,
and OMX.qcom.video.decoder.hevc
can you play 10 bit hevc video in your custom rom?
wolvenstorm said:
can you play 10 bit hevc video in your custom rom?
Click to expand...
Click to collapse
I don't use a custom com... not everybody around here does...
nine7nine said:
I don't use a custom com... not everybody around here does...
Click to expand...
Click to collapse
i thought you use custom rom because of your link to your Kernel exNoShadez
wolvenstorm said:
i thought you use custom rom because of your link to your Kernel exNoShadez
Click to expand...
Click to collapse
no, the kernel and ROM aren't tied together... you can usually swap them in/out separately...
I development my kernel to use with the stock ROM...

Categories

Resources