Database Info

[APP] Android Storm 2.0 / Coreplayer

Hi,
Just ran into this interesting Chinese app: Android Storm 2.0
Site: http://shouji.baofeng.com/
Player link: http://dl.baofeng.com/mobile/AndroidStorm.apk
I think it is used (my Chinese is very bad) for their iptv services they offer.
Not very intersting to many of you I guess. But what if I tell you this is Coreplayer with a different GUI. Yep Coreplayer.
So the big question: who from this board is gonna make the best Android player on the planet with this?
Cheers
EDIT: Codecs (ARM6+)
Code:
[MODULES]
libsplitter.so
libmad.so
libmpeg1.so
libmpeg4.so
libcodecwrapper.so
libaac.so
libac3.so
libamr.so
libasap.so
libcamera.so
libflac.so
libmatroska.so
libmikmod.so
libmpc.so
libspeex.so
libtemplate.so
libvorbishq.so
libvorbislq.so
libwavpack.so
libtta.so
libbhdserver.so
libstpserver.so
libstpclient.so

played a few videos using that app (CorePlayer i assume). It works (when it does) but doesn't seem to show the spectacular performance I was hoping for. MX Player and Dice Player both show better performance AND much more broad codec/stream support that CP. I guess that's why CoreCodec is only releasing it to OEM - the app isn't optimized for all the different platforms/cpu's/etc Android is being ran on.
I'm assuming replacing the decoder libraries with those from the phone that CorePlayer came on will improve performance. Hopefully they aren't too dependent on the hardware they came on.

I've been using the MX player for a long while now - and seriously this one has a lot more to do. I've tried the Core Player port - on my Epic sometime ago.
cheers
AK

I am used to Coreplayer/TCPMP from the WinCE days. Those were the best for my PNA.
On Android I always used YXPlayer. Now I have switched to BSPlayer. Mainly beause of LAN/NAS support. I think coreplayer has a lot to catch up on Android. As they also started as opensource with TCPMP, other projects on Android have left them far behind now.

[APP][2.3+][Weekly Builds] XBMC For Android Nightlies

There are official releases for neon and ICS+ devices over on xbmc.org.
For Tegra2 / GB devices I'm likely not going to be working on them much, if at all going forward. I no longer have a Tegra2 or GB device and version 13 of the upstream code base has some changes that will make it very difficult to support the Tegra2 going forward.
Thank you to staticaDK, repvik, lavero.burgos, and XBMC Android for their help with mirroring.
staticaDK has suffered equipment failure and his mirror is down. Any links / bookmarks to his mirror will no longer work. Please DO NOT use old links to this mirror
The xbmchub.com guys are launching http://www.xbmcandroid.com/. The forums are open for registration for anyone that is interested.
We also have a FreeNode channel #xbmcandroid for those that are interested.
I have also broken out a lot of the information from this XDA thread as separate threads on xbmcandroid.com
Please note these are unofficial builds of XBMC, please report issues here or xbmcandroid.com ONLY
Builds are now auto-run every Sunday (through out the day). I will no longer be directly linking to the builds, please head over to the mirrors (links below) to download a given build.
XBMC, What is That?
XBMC is a media player / HTPC software package that does just about anything you'd want on a home theater box or a portable media device. See http://www.xbmc.org for more information.
Why Here?
I have been maintaining nightly builds of XBMC for Android and after a few requests and realizing my posts have been cross-linked it's time to create a central spot for the builds.
Schedule of Builds
Builds are now run automatically every Sunday.
What Is Special About These Builds?
I have re-built the CrystaX NDK that is required for XBMC from sources and made some compiler flag changes in order to improve NEON device support and to support the Tegra2 or other non-NEON devices. These are unsupported changes, particularly the Tegra2 and any other device without NEON. The official XBMC stance is NO device lacking NEON will receive support.
What Is / Is Not Supported
All builds are now built for 2.3.x (GingerBread) or higher devices. ARM ONLY. I will not be releasing MIPS or x86 builds.
Google TV devices are UNSUPPORTED. I do not know if / when the XBMC dev's will be supporting Google TV.
I will not be releasing aplayer builds. I will be leaving it up to Pivos to do releases. Please visit the Pivos forums for the latest builds with AMLogic hardware decode support.
Which Build Do I Want?
There are two builds, one for Tegra2 devices and another for NEON devices (see below for specifics). If you are not sure which type of device you have, try the NEON build and if it crashes, then use the Tegra2 build. If you have a non-NEON devices that is not the Tegra2, the Tegra2 build will run, but not all that great.
XBMC Compatibility List (Clickable link)
FAQ
Why is the APK so large?
This is a full build of XBMC including dependencies, resources and the like. There is a lot to the build and output. See http://pastebin.com/LgnWzdHW for a breakdown of what is contained within the APK including file sizes.
Does zipalign help with the size of the apk?
I ran zipalign and it didn't reduce the file size, likely won't help given what is packed in the apk.
Is there a better skin for touch screens?
Under the appearance settings there is a skin named "Touched" that works much better on touch screen devices than the default.
Does my hdmi out / dock / etc work for tv playback?
There are reports of this working properly in this thread and others.
Can I change the resolution for hdmi / similar playback?
Initial reports indicate this is not possible currently.
Does it work with CyanogenMod 10 (CM10)?
Maybe. Some users have reported success with CM10, others have had issues.
How do I get Fahrenheit Temperature?
Settings > System > International -> Change your region to USA if you want Fahrenheit
Common Problems
My screen starts flickering / freaking out: Kill the app, clear the app cache, restart devices, try again. Continue until the problem goes away.
I cannot play SD / 720p / 1080p content without stutters / dropped frames / audio sync issues / etc: Tough luck. Right now hardware decode support isn't complete, if your CPU can't process the video in software, you're stuck for the time being. The XBMC devs are working on hardware decode support and it will be done in due time. Do not ask for a deadline, there isn't one right now.
Battery life: Expect a pretty bad battery drain. This has been confirmed by a few others as well as the devices I tested. Given the project is targeting set-top boxes and similar equipment I would not expect this to be addressed until other, larger items are taken care of. Please do not complain to the official team about this item, complain here.
Resource utilization is high: This is known. Not going to change for awhile, do not complain to the official team, complain here.
Audio does not work: The XBMC audio levels and Android audio levels are not the same, you will need to adjust the volume in Android up to a higher level before launching XBMC most likely.
DVD Navigation may or may not work properly: This is known and being worked on by the main XBMC team.
/data is inaccessible: This partition is not accessible from XBMC.
Touchscreen Non-Responsive: Some users have reported the touchscreen taps aren't registering well or at all. The Toshiba Thrive 7" and 10" tablets seem to suffer the worst from this.
Tegra2 / non-NEON Problems (Must Read)
If your device does not have NEON, DO NOT COMPLAIN TO XBMC. Complain here.
Problems Under Investigation
XOOM 3g's running EOS ROMS appear to crash with a 0xdeadbeef pointer dereference
Working Add-Ons
1Channel -- Developer PM'd me and the choppyness is fixed in latest version (url in add-ons links below)
Anarcintosh's Icefilms
BBC iPlayer 2
dpstream
Freecable
fs.ua
FTP Sources
Icefilms
Navi-X
PBS
Samba Sources
Shared Library: http://forum.xda-developers.com/showpost.php?p=29899425&postcount=57
TED Talks plugin works great.
The Trailers plugin
Tuxbox
TVCatchup
Tvlinks
Broken Add-Ons
Bluecop's Amazon (crashes trying to unload librtmp.so -- symbol not found)
Bluecop's Hulu
MLBMC: Major League Baseball Media Center
myvideo.de
Trakt.tv stable. The version on github works on Windows, can anyone validate the version from git works on Android?
TuneInRadio
WebDav HTTPS

Sources
XBMC
Official: https://github.com/xbmc/xbmc
My Fork (Includes Tegra2): https://github.com/mcrosson/xbmc/
Android NDK
Official: http://www.crystax.net/en/android/ndk/7
The above NDK is no longer used in my builds. I have tweaked the sources to include better NEON / Tegra2 support. My customizations are not available currently, but I am working on an NDK release based on the CrystaX changes and will be publishing my work once I am further along.
Add-On Links
lavero.burgos mirror: http://four-nineteen.com/veronica/XDA Developers/XBMC 4 Android/Addons/
1Channel: https://github.com/bstrdsmkr/1Channel -- Support: http://www.xbmchub.com/forums/1channel-plugin/
Jezz_X's re-touched skin
This is an alternative to the included "Touched" skin.
http://forum.xbmc.org/showthread.php?tid=128494
Builds (~50Mb each)
See above for compatibility. If you are unsure, try the NEON build first, if it works use it. Otherwise use the Non-NEON build.
Google TV devices are UNSUPPORTED. I do not know if / when the XBMC dev's will be supporting Google TV.
I will not build AMLPlayer builds, If you have a Pivos device, visit their forums for build information and releases
I will not build MIPS or x86
I have setup a goo.im mirror in addition to those below. It will contain the 2 most recent builds linked below. You can find the files here or within goo manager (devs/kemonine/xbmc and available in play store)
Mirrors / Builds
Builds are now auto-run every Sunday (through out the day). I will no longer be directly linking to the builds, please use the following mirrors to obtain a release.
Please note the box mirror contains every build that has been previously published and is more complete for legacy builds than the google code mirror
Box (link)

Thanks for getting it to work on non neon. I got the Toshiba thrive

Thank you!!!
Working good on my TF101
Cheers!

Great thread.
Is there any chance you can include a changelog of commits as you are building them then it will have all the information in one place without having to go to github etc.
Just a suggestion

flumpster said:
Great thread.
Is there any chance you can include a changelog of commits as you are building them then it will have all the information in one place without having to go to github etc.
Just a suggestion
Click to expand...
Click to collapse
I will be calling out any noteworthy changes with the builds. Right now I haven't seen anything of note coming in on the commit logs. It looks like they are doing general cleanup and some under the hood work.

Thank you for bringing this to us Tegra 2 users. It works so damn well.

This is fantastic. Absolutely great. Is there anyway to import the visualizers from ProjectM?

kemonine96 said:
I will be calling out any noteworthy changes with the builds. Right now I haven't seen anything of note coming in on the commit logs. It looks like they are doing general cleanup and some under the hood work.
Click to expand...
Click to collapse
Great mate.
It will help to keep things organised. No point in updating daily for minor things but I will definitely update weekly or when a major commit comes.
Thanks one again.

Thank you for this
Flyer

Can someone who has the files upload to adifferent location. I am interested in the tegra2 version
Thanks

hunkyn said:
Can someone who has the files upload to adifferent location. I am interested in the tegra2 version
Thanks
Click to expand...
Click to collapse
Download works for me, I used the stock ICS browser (came with the ROM I'm using). Just hit download.
If you're websensed (at work/school, blocked by IT firewall/censored page), right click the link, copy link address, make a QR code here, install Barcode Scanner, and scan the generated barcode.
Testing on a Tegra 2 phone (it's the 3G version of the Sprint Motorola Photon 4G). I will edit/post with results. FYI, huge file size. Don't download on 3G/4G unless you're a light data user/you have a nice plan (US Cellular 5GB plan, FTW).
//edit: 48.82MB. Good lawd that's a big APK!
It starts...
It can play music... but it's kind of a PITA, vs. your favorite music app. First you have to add the source. Hit browse. "Android Music" is the place your music player is getting it from. It's a placeholder, like the Libraries in Windows 7/8.
You can launch apps from it. Neato.
Videos... Eh... They don't get added as easily as music. "Android videos" might refer to the camera roll, but it's not where I have my videos. I had to add that manually. I have a 720p MP4 of the Fallout 3 intro that MX Player plays like butter, but it plays like crap in XBMC. A 3GP video I took with a dumbphone of my niece b***h-slapping me (she was 2 at the time, and objected "but he's my friend" first, haha) played fine. A shorter 720p video, another MP4 from YouTube, but only 4.5MB as opposed to the Fallout video's 47.3MB, stuttered almost as bad as the Fallout video.
Scrolling is... um, difficult. On the main menu, and if you have to browse for anything. It's gonna fight you. Works if you can grab the itty bitty scroll bar. But if you just grab the directory tree and toss, it may work or it may not. Or it may open the folder you grabbed it by.
Basically... it's nice and fancy but not too practical. Can this receive streams from a PC or server?

Dark Reality said:
Download works for me
FYI, huge file size. Don't download on 3G/4G unless you're a light data user/you have a nice plan (US Cellular 5GB plan, FTW).
Click to expand...
Click to collapse
Downloads were down earlier today. I had forgotten DropBox had limits to how much data can be sent via public links. I also didn't expect to get that many downloads in the course of a day. I've moved my file hosting to another provider that provides more transfer and a dashboard that should let me keep an eye on my limits better.
I have updated the post with links to include file sizes and made a note to see about decreasing the file sizes.

Dark Reality said:
It starts...
It can play music... but it's kind of a PITA, vs. your favorite music app. First you have to add the source. Hit browse. "Android Music" is the place your music player is getting it from. It's a placeholder, like the Libraries in Windows 7/8.
You can launch apps from it. Neato.
Videos... Eh... They don't get added as easily as music. "Android videos" might refer to the camera roll, but it's not where I have my videos. I had to add that manually. I have a 720p MP4 of the Fallout 3 intro that MX Player plays like butter, but it plays like crap in XBMC. A 3GP video I took with a dumbphone of my niece b***h-slapping me (she was 2 at the time, and objected "but he's my friend" first, haha) played fine. A shorter 720p video, another MP4 from YouTube, but only 4.5MB as opposed to the Fallout video's 47.3MB, stuttered almost as bad as the Fallout video.
Scrolling is... um, difficult
Can this receive streams from a PC or server?
Click to expand...
Click to collapse
Which skin are you using? The default in the build is confluence which is optimized for keyboard / remote usage. The settings area has an appearance tab that will let you change to the "touched" skin which is infinately more managable on a smaller screen.
Once you add the sources you can scan the items to the library (including auto-scans on launch) that greatly improves visibility and access to content.
Your success with video is pretty much par for course on the Tegra2. XBMC currently does not have hardware decode support and relys on software rendering. It has 1/2 of the floating point units (why it won't receive official treatment) that you would find on a newer chip which greatly impedes its ability to decode video content. Things will improve once hardware decode support is available (it's being worked on in mainline). I will be working on improving the builds as much as I can while the mainline devs finish up general hardware decode support.
You can setup smb / ssh / upnp / similar sources and they should generally work.

finding a bit hit and miss opening the app on a Tegra 3 - TF300
will try and reboot and see if it's any better - have tried the force close/reopen
anyone else with more luck?
Edit: Reboot has helped - app opens no issue anymore
Thanks for the NEON build - using the Touched skin
Confluence looks better, but Touch is more functional by far!
On a Tegra 3 TF300:
720p AC3 mkv - playback OK but not watchable - stutter. Audio appears to play mostly uninterupted.
1080p DTS mkv - playback OK but not watchable, but audio and video stutter.
Keep up the good work!
Looking forward to a stable build with HW acceleration!

Yeah, I wasn't expecting much out of XBMC. I knew the limitations going in. 0% of the blame on you. Some is on nVidia (Tegra) and Motorola (Photon 4G/Electrify) but some is also on XBMC themselves. MX Player plays HD video beautifully on my phone, although I do have it formatted for my screen. So it's scaled down to 960x540 (not 720p as I stated above). So video playback is possible in Tegra 2. Not sure if MX Player's drivers are open source. Might be worth looking into.
And I was using Confluence, didn't think to change the skin. I use a ROM that has a hybrid tablet mode, so I'm used to touching smaller screen items than many Android users, particularly those on stock builds. I actually had little trouble hitting the tiny touch controls for media on the main screen, and those were some tiny buttons, but I'll check out the other skin.
Other skin checked out, works a lot better, thanks.

Dark Reality said:
Not sure if MX Player's drivers are open source. Might be worth looking into.
Click to expand...
Click to collapse
I will definitely have a closer look I think I ran across it at some point but didn't look too closely.

This works wonderful on my Atrix!

This is pretty awesome development to see bro, good stuff! Keep up the good work, will be tryin it out on my TF101 after work. Man, now I feel I'm really going to want to cop a hdmi mini adapter....
~Poisoned Viper4g LTEvOne by TeamVenom, Lionheart Cranked to 1.72Jigawats Deadline: Ca1ned.

MassStash said:
Man, now I feel I'm really going to want to cop a hdmi mini adapter....
Click to expand...
Click to collapse
I'd hold off until you know if it will perform or not. On the Tegra2's there is hit or miss support for even SD content. Support seems to boil down to container format and audio stream. I know my SD content stored in mkv with ac3/dts audio stutters badly at times. I've heard reports of xvid avi + mp3 audio being much better for playback.

[Q] Integrating MX Codecs into AOSP build

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

[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.

Way to adjust audio offset?

I just started using MX Player over VLC as MX Player has better playback on my Lenovo Tab 2 A10-70, but one thing I did like about VLC was that it allowed for audio offsets to adjust either badly synchronized source material or other situations like laggy bluetooth speakers. Is this a feature that the developers are interested in adding?
On my tablet vs my galaxy s7 it seems like the audio is correct on the s7 but lags one or two frames behind the video for the tablet. I have tried most different combinations of HW+, HW, SW acceleration for both video and audio without luck. If this is something that can be fixed without adding audio offset, I'd like to hear suggestions as well.
Thanks!
Edit: I notice this feature is available in the S7 version but not on my tablet. When I press the 3 dots at the top right of the video the menu options are Play, Display, Audio, Subtitle, Tools, Help on the S7 but on the tablet it is just Play, Display, Subtitle, Tools, Help. Same video file.
Edit: Resolved by downloading 1.8.4 nightly. Apparently 1.8.3 in the play store has a minimum version of 6.0 and I am running 5.0 on the tablet. Possibly an issue with the apk?

No, it's not an issue with apk. It's intentionally done by the developer. There are some of the old device issues which is yet to be resolved. If you sign up for beta testing you will automatically get the latest nightly on google play. For marshmallow it must be released to stable channel since it comes up with some specific fixes for marshmallow devices.
There are some more features in works like new HW+ engine which will be better compatible with most of the devices, better HW+ support for HEVC & more.
According to the information I have received from the MX Player developer, if everything goes as expected the pre marshmallow users will directly get 1.9.0 on stable channel. He is trying to align with the Android N public release.
Sent from my Samsung Galaxy S5 using XDA Labs