yashsingh1/xdaforums huggingface dataset:
[myTouch 4G General] wealthy23:
I am using the 2nd version no problems but how is coredroid becuase i have been using sense i just need stability feature are cool but being stable is my focus and does that rom have any tweaks?
[myTouch 4G General] dead-zon:
The only thing that I do not like about Virtuous roms is that they do not update their roms often. A there are some things that do not work but on most of the other roms they do. I would not recommend you going back to Unity rom
[Motorola Droid Bionic] gk1984:
I'm a sprint user bu my fiancé has the bionic and had the lg revolution before that. Both phones wouldn't work is the signal bars and data indicators were white. They had to be blue to function. There have been many times they would stay white on both phones and had to switch to airplane mode today fixes the issue. With sprint, this isn't an issue. It just works. Both networks, sprint and Verizon, are cdma, so what's the problem?
[Motorola Droid Bionic] projektorboy:
It depends on what you're trying to do with the phone at the moment. You should still be able to get to websites. However, things like email, Play Store, and other Google things may not work. From what I've come to understand, when the signal indicator turning a color (blue, green, red, etc depending on OEM customizations) is an indicator that the phone is connected to Google services. When it's grey it's merely indicating the presence of a data network and you may or may not be able to connect to the internet.

This behavior can also be observed if you activate an Android device without entering an email address. The signal indicator will never be anything other than grey because it doesn't have any reason or ability to connect to Google services.
[Motorola Droid Bionic] gk1984:
Thanks, then what's keeping it from connecting? It happens way too often and keeps her frustrated. She can't do anything at this point when it's like this.
[Motorola Droid Bionic] lance2ecnal:
Settings?

If the phone is totally stock then it might just be a settings issue. My bionic takes a minuet to connect to the internet even though it's connected to the network. Check to see if are any settings that turn off or restrict that data usage
[Motorola Droid Bionic] smokedkill:
When it turns white, the data connection went dead. When its blue, its active. It happens to me occasionally, similar to a hiccup. It could be due to a mathematical glitch in the radio.
[EVO Shift 4G Q&A, Help & Troubleshooting] B RAD G 296:
Would it possible to port something like warm rom to this phone, i tried synergy warm rom but it the KB light problem?
[EVO Shift 4G Q&A, Help & Troubleshooting] prboy1969:
It should be possible. What Device was the Rom originally on? The KB light? Do you mean the one where the KB opening turns on the charging light? If so that can be fixed.
[EVO Shift 4G Q&A, Help & Troubleshooting] strapped365:
A little services.jar from SS fixes synergys problem, mostly because their work was based off miks as was mine :D

Sent from my HTC MyTouch 4G Slide running MikXE
[EVO Shift 4G Q&A, Help & Troubleshooting] B RAD G 296:
that would be good fixes and the change the personalize button from browser button to it being a personalized button.

Or at lest make a theme of it and out it on miks rom, or start with a new rom.
[EVO Shift 4G Q&A, Help & Troubleshooting] prboy1969:
Ok now that you know, have at it ;)

TEAM MiK

MikROMs Since 3/13/11
[EVO Shift 4G Q&A, Help & Troubleshooting] strapped365:
Well just deodex the services.odex from SS and push it to system/framework.

But to unmap the Rosie I'm not sure how easy it would be because I'm not sure how it was done. My computer is loaned to my parents for now because theirs took a nose dive so I wouldn't be able to see how it was done. But an idea would be find like a MikShifted-G beta from when it was stock and push its Rosie.apk to system/app and maybe it would work. Or have prboy post just the Rosie.apk if he still has the beta on his computer ( which he should he stockpiles ROMs ) anyways time to get cleaned up after a 12 hour day of work

Sent from my HTC MyTouch 4G Slide running MikXE
[EVO Shift 4G Q&A, Help & Troubleshooting] prboy1969:
I wouldn't call it Stockpiling per say :silly: . Well..... ok I Stockpile Roms :laugh: . But it does come in Handy ;) .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
DTS audio *used* to work outofthebox in both DicePlayer (my old favorite), and in MX Player (my new fav), but both of them REMOVED the dts codec a few months ago apparently because of the threat of lawsuits from using unlicensed code.

(UPDATE: DicePlayer dev juami posted below that they were refused even the option to buy a license for DTS, because they prefer to deal with the big industry players instead; also, DicePlayer can still play dts IF you install an external codec plug-in)

Just curious what most people are doing out there in order to play their mkv videos with the very common DTS audio track (vs the less common AAC/MP3/etc audio tracks). Re-encoding phone-friendly versions with HandBrake; using an old app with DTS support; using a PAID app that paid the licensing fee (can't find one), or, something else...

EDIT: I'm going to keep a list here of players that are known to support DTS or not:

DTS IS SUPPORTED OTTB (for now):

VLC Beta - (h/w 1080p decode works! - BEST option, but, the app must be sideloaded, since it shows as incompatible with the US S3 in the Play store. See Time_Zone's post below for the attached VLC apk. Thanks!)

BS Player - (s/w ONLY (eats battery): h/w mode always falls back to s/w mode, but dts is ok. 720p s/w == ok; 1080p s/w == CPU can't keep up; too choppy)

Rock Player - (s/w ONLY (eats battery): no DTS when in h/w video playback mode, and s/w playback is blocky crap. Also, the app fails to playback a video when sent a video intent to play from another app)

DTS NOT SUPPORTED:

Video Player default - (Touchwiz, AOSP (CM10, AOKP, ...))

MX Player - (updated versions removed codec; google for old apk version)

Dice Player - (updated versions removed codec; google for old apk version (2.0.6), or try searching XDA for external plug-in support instead.)

Mobo Player
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Time_Zone:
VLC BETA... you have to search for it. It does work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Awesome. I'll give it try, even through from what I've read the beta is still very buggy & laggy.

Wonder how long they'll "get away with it" before removing DTS support too.

EDIT: VLC beta is currently incompatible with the US SGS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
FWIW, BS Player is one of the few I've found that can handle DTS Audio, however, it fails to playback do h/w accelerated playback of the video, and falls back to s/w, so it's choppy with 720p, and fails with 1080p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Time_Zone:
huh... This one seems to be working for me...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Whoa! That works! Wonder why the Play store shows it as incompatible...

So, after enabling h/w acceleration (disabled by default), my 720p & 1080p vids play without a hiccup. Smooth video & crisp dts audio. I'm not seeing all the bugs that are warned about. :) Thanks man.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Time_Zone:
If I try to skip ahead or behind off a cifs mount across network the audio goes out of synch... Thats the only bug I have seen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juami:
Diceplayer is not discontinued. ( https://play.google.com/store/apps/details?id=com.inisoft.mediaplayer.a&hl=en )

and there are a way to enable un-supported codec

search "xda diceplayer dts"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
The impression I got is that DicePlayer switched from AdSupported&Paid versions to DonationWare in preparation of becoming AbandonWare. In any case, they removed DTS, so it's out of the running, and from the comments I read about the external dts workaround you mentioned: it doesn't work as well. VLC wins for now. Thanks, though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NZtechfreak:
For myself I have a backed up apk of the last MX Player to ahve DTS and I simply install that on new devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juami:
That is your impression. but I am working for upgrading diceplayer. We do not adandon diceplayer. I am very upset and feel that I should really adondon diceplayer. Why do I do bothering jobs like supporting JB and fixing bugs and adding external codec features.

removing DTS is another problems. MX also remove DTS. we have same situations.

did you copy libffmpeg.so to /sdcard ( root of internal storage memory ). and enable custom plug-in and restart diceplayer?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
I didn't realize you were one of the DicePlayer devs when I replied. So, sorry 'bout sounding as if I was bashing DicePlayer.

I used your app for over a year mainly because it was fast, played just about everything I threw at it, and because it was and still is the only player (afaik) that can browse & directly stream from windows network shares (without having to first mount samba/cifs in a separate app). It was just the loss of DTS and the (false) impression of it becoming abandonware that made me leave it.

Mind if I ask how much the lawyers were asking for a DTS licensing fee? And, how is it that VLC and others are getting away with it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] juami:
DTS deny to sell thier products to sw player makers.

We already contact them to buy license. But they refuse to sell.

They want to sell DTS license to hw vendor like samsung.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xtrememorph:
And Samsung don't want to buy to put it in their hardware... don't they know that make their handset sells even faster??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xtrememorph:
Trying out to video on Galaxy S 3 Jelly Bean (Omega V14)

Dice Player - Error prompt "Video playback Sorry, this video cannot be played." just by starting the app

MX Player - 1.6F show version not supported and close

VLC Player - Software mode playback on some videos ok, enable hardware with have choppy videos

Not sure is upgrading to JB worth it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
I see no Omega ROM in the dev forum... and when I google it, it says it's still ICS, not JB.

Anyhoo, VLC Player has been great for me, and it's all I use now since it plays everything I throw at it (like DicePlayer used to). My only minor gripe with it is that it's sometimes herkyjerky in the first 3 seconds of video before it 'catches up', so I can never see the first few seconds of some videos.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ghost77:
If rom is CyanogenMod ,ASOP/AOKP they won't have samsung media codecs. That's why hardware acceleration not working.

Flash samsung stock based rom with proper kernel i recommend this ktoonsez sammy kernel . And video playback will work properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Platinum1986:
very interesting thread, i hope mx player will be compatible with DTS audio in near future.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dikime:
MX won't be compatible cause of the mentioned legal issues, but they added support for custom ffmpeg builds, which eventually might help adding DTS support back... if someone does it ofc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
might try Dice player again with the dts tweak, but i have been using vplayer for videos with DTS. Free in the play store and works rather well.

Well just like last time Dice player freezes and lags, with certain MKV files such as anime. BS Player is by far the best player around and love the LAN features, just wish the UI was cleaner.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indianajonesilm:
Now that MX Player 1.7 was released with instructions on how to build a custom FFmpeg with DTS support,has anyone tried it out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
Did a quick google search after you reply and found this I hope someone can build this. I would rather not start a VM just for this :p and just be handed on a silver platter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] koljanowak:
I've build ffmpeg for mxplayer successfully for my Nexus 7. MKV with DTS plays fine now.

However, there is a small detail missing in the Howto. Building as described leads to a working ffmpeg version which still doesn't handle DTS. One has to remove the following three lines from config-ffmpeg.sh:

--disable-demuxer=dts \
--disable-parser=dca \
--disable-decoder=dca \
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] buvk:
i built ffmpeg using the instructions here:

https://sites.google.com/site/mxvpen/ffmpeg

and also removing the 3 lines you mentioned, but i'm still not hearing any audio with a dts mkv

any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] koljanowak:
Did you copy all five .so files

libavcodec.so
libavformat.so
libavutil.so
libswresample.so
libswscale.so

into a folder on your device? And have you selected that folder in MX Player as "Custom codec"? And after a restart of MX Player, is the folder name still shown under "Custom codec"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] buvk:
yep, thats exactly what i did
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoganMcClay:
Hi,

I don't get it, trying to compile ffmpeg for an hour and I get stuck on some parameters in build-ffmpeg.sh... What shoud TARGET1 & TARGET2 point to ? Tried to give there the *.so found in the unpacked codecs APK and that's a no-go...

Also, this part :

cp libavutil/libavutil.so $TARGET1/
cp libavutil/libavutil.so $TARGET2/
cp libswresample/libswresample.so $TARGET1/
cp libswresample/libswresample.so $TARGET2/
cp libavcodec/libavcodec.so $TARGET1/
cp libavcodec/libavcodec.so $TARGET2/
cp libavformat/libavformat.so $TARGET1/
cp libavformat/libavformat.so $TARGET2/
cp libswscale/libswscale.so $TARGET1/
cp libswscale/libswscale.so $TARGET2/

is trying to copy files that doesn't exist... Maybe because first part isn't set correctly.

koljanowak, can you point me how you've done it ?

Thanks by advance :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
you have to set the target folders so output of the codecs

I replaced $target1 to /usr/src/android-ndk-r8b/T1=../libs/armeabi-v7a/neon and do the same for $Target2 but point it to a different folder.

What I don't get is what does it need to Target folders, I tried both codecs folders and they both play DTS on H/W+ only
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoganMcClay:
Sorry but don't undestand what you did.

That's for instance what i've set for now, but doesn't work :

build-ffmpeg.sh

case $1 in
neon)
TARGET1=/home/vmware/Documents/ffmpeg/ffmpeg_v7_neon__1_7.apk_FILES/lib/armeabi
TARGET2=/home/vmware/Documents/ffmpeg/ffmpeg_v7_neon__1_7.apk_FILES/output
;;

Do you say you've modified it that way ?

case $1 in
neon)
/usr/src/android-ndk-r8b/T1=../libs/armeabi-v7a/neon
/usr/src/android-ndk-r8b/T2=../libs/output/ffmpeg_v7_neon/armeabi
;;
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
I messed up the end as you can see below, but it generated the 5 *.so files in both T1/T2 directories, and I just manually created the lib folder and moved them to the appropriate folders. What I do not understand why it generates target1/target2 directories with the same *.so files when only one folder with the so files are required. So is the S3 armeabi-v7a or armeabi?

build-ffmpeg.sh: line 10: /usr/src/android-ndk-r8b/T1=../libs/armeabi-v7a/neon: No such file or directory
build-ffmpeg.sh: line 11: /usr/src/android-ndk-r8b/T2=../libs/output/ffmpeg_v7_neon/armeabi: No such file or directory
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] buvk:
well i got it to work

under settings > general, i had to reset settings, and then set it to use custom codec again after i restarted the app. worked perfectly right after that.

and for those of you having issues compiling, tech support on mx's forums posted the compiled codec.

https://groups.google.com/d/msg/mx-videoplayer/Yfn0mlU7RW4/Z_F_Y5KmZ3EJ
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] koljanowak:
Those target directories are irrelevant for our use case. Placing the .so in different target directories is a part of the MX Player build process, which leads to an APK containing different versions of ffmpeg for all supported CPU types. We need to build only for our own CPU type and then copy the five .so files by hand to a folder of our own choosing on the device.

Only the first four commands in build-ffmpeg.sh are relevant, and you can even enter them by hand:

cd ffmpeg
../config-ffmpeg.sh $1
make clean
make -j8

You must insert your architecture (neon, tegra2, v6_vfp, v6, v5te, x86, mips) as argument to config-ffmpeg.sh (replacing $1). And of course you have to make the necessary changes in config-ffmpeg.sh beforehand, which is

- change "NDK=..." to point to where you extracted your NDK,

- delete "-DMXTECHS" and "-lmxutil", as mentioned on the MX Player Howto page,

- delete the three lines disabling DTS and DCA, as mentioned in my first post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoganMcClay:
Thanks, got it working :)

Anyway, it seems to work also with the one posted a little above on MX google groups even on different arch (tried on HTC HD2 NANDroid, Asus Transformer Prime and Samsung Galaxy S3). In configuration>Codecs>Custom codecs I just pointed the "libavcodec.so" file.

That way, we don't need to compile it for each and every platform ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] koljanowak:
Maybe, but it depends on how those architectures are related. A more modern ARM CPU will execute code for older ARMs, but you may miss optimizations for your CPU this way, and this could impact performance and/or battery life. Or worse, if you use code which was compiled for a more modern ARM CPU than yours, the code may contain instructions which don't work on your CPU. Also, ARM, x86 and MIPS and are not related at all and are completely incompatible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoganMcClay:
Right, I haven't tested that far. What I was saying is it's just decoding fine on a bunch of different ARM processors i've tested.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zetsui:
why is this such a big thing...is there a huge quality difference between DTS and stereo?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cook:
Hello,

Is someone can post compiled versions for neon and for tegra2 ?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] koljanowak:
I would post them, but as a newbie I am not allowed to. I can provide links via PM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cook:
Please do it I will post it there
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] koljanowak:
It looks like I'm not so new anymore:

mxplayer-v1-7-ffmpeg-2012-09-16-neon.zip (md5: e5bf7c05c680006d81fbccefb79fc713)

-> https://anonfiles.com/file/e5bf7c05c680006d81fbccefb79fc713

mxplayer-v1-7-ffmpeg-2012-09-16-tegra2.zip (md5: c64f7dc461d3f4c2bbda08c726f478c9)

-> https://anonfiles.com/file/c64f7dc461d3f4c2bbda08c726f478c9

mxplayer-v1-7-ffmpeg-2012-09-16-v6_vfp.zip (md5: 553367b419e6c855b6eb32f7abd35ec1)

-> https://anonfiles.com/file/553367b419e6c855b6eb32f7abd35ec1

mxplayer-v1-7-ffmpeg-2012-09-16-v6.zip (md5: 342a2a8bda3f9a8ebd5b62e95a8593a2)

-> https://anonfiles.com/file/342a2a8bda3f9a8ebd5b62e95a8593a2

mxplayer-v1-7-ffmpeg-2012-09-16-v5te.zip (md5: 6ea66726b362a73e9b962be7a05af3a6)

-> https://anonfiles.com/file/6ea66726b362a73e9b962be7a05af3a6
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Thanks. It's just sad the hoops people have to jump through to get DTS support.

(I'm still using the VLC Beta because it 'just works'.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
DTS is multi-channel vs 2-channel stereo, so yes, when output via HDMI or DLNA there's a huge difference, but even if only listening to content on your phone with headphones it's just more convenient to just have all audio work without having to re-rip / re-encode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MarcusHD:
Hi,

did one of this Codecs work on Nexus 7? I have tested the codecs in mxplayer-v1-7-ffmpeg-2012-09-16-neon.zip with the latest MX Player from Play Store, but I have no DTS sound.

Thanks.

Gesendet von meinem Nexus 7 mit Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] koljanowak:
I have a Nexus 7 and a Galaxy Nexus, and the neon version works on both. In fact, the neon version is the only one which I could test myself.

Look at the previous messages in this thread, another user had to reset all settings in MX Player before it started to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MarcusHD:
Now it works. Thanks! :)

Gesendet von meinem Nexus 7 mit Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GodofGodz:
I got a Galaxy Note 10.1 running latest Mx Video Player Pro and using mxplayer-v1-7-ffmpeg-2012-09-16-neon.zip codec. After i pointed mx video to the folder it told me to restard which i did then i proceeded to play a normal 8 gig mkv bluray rip with dts, at first no sound then i check which decoder it was using. It was on HW, then i change it to SW decoder, Low & behold works like a charm....

Now am super happy...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Well, that sucks, because it means that DTS decode only works in software decode mode like the other players I tested except for VLC Beta which can h/w decode 1080p with DTS.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] buvk:
On gs3 I'm using hw and it works fine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
Same thing happened to me but it S/W i was getting artifacts and still do, don't know why. Anyways change to H/W+ and DTS will work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DoubleYouPee:
Can anyone explain what to do with these LIB files? I can't find a recompiled APK with DTS anywhere
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Copy this pre-built libffmpeg to /sdcard/libffmpeg.so then enable it as a plug-in in DicePlayer, mxplayer, etc. WorksForMe, but, for whatever reason, VLC Beta is still smoother than Dice (and I hate how dice always quits (or crashes) back to the sdcard root even after I tell it to stick to my SAMBA server...)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dark_Avenger:
koljanowak,

please compile the latest ffmpeg with DTS support for MX Player 1.7.6... I got every time "C compiler test failed." error when I try to compile myself.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeky82:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Xellotath:
Is this going to fix 'unsupported audio codec: dts' error showing since update?

Will we need to keep doing this after every update? (i might just turn off automatic update if so)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeky82:
I think that for 1.7.6 version we need to recompile it. In the official site (I can not post the link because I have less the 10 posts :( ) is reported "From version 1.7.6, file names are changed to libavutil.mx.so, libavformat.mx.so.. so forth to resolve conflict with system library file". I think that the problem is due to this, because for 1.7.4 and 1.7.5 I always used the same ffmpeg linked in this thread without re-compile it :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Xellotath:
Found one for 1.7.6 here

https://groups.google.com/forum/?fromgroups=&pli=1#!topic/mx-videoplayer/Kloo-L8ejIw
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeky82:
thanks ... it works great! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] darkforcesjedi:
Thanks for this thread. The VLC beta and the ffmpeg decoder with MX player both work on my SGS3 for sprint. I can't wait til I get home and can try it on my Transformer Prime. I am a little behind the curve. I just set up a UPnP server on my NAS the other day and was dismayed when I had no DTS support after I tried accessing it using my phone and tablet.

:victory: