It worked well before .13 OTA update, after that I thought it was some bugs in .13 so I wait till .14 but still not being able to play a single RMVB file ....
I have tried to store it in different locations including micro-SD , SD card, USB drive and internal storage. None of it work for me...
I use MX Player and Mobo player in this case.
one thing I notice, when I turn on my prime (not from sleep) and immediately get into file manager and play the RMVB file, then it's working again until I leave the program and back to home, it won't play again...
wondering if anyone has the same problem as I do.
here is the picture when I encounter the error message
please help if u know how to fix that~ thx in advance
anyone has the same question?
Can you upload a sample?
very nice of u replying me =D
I am out and could not get a sample yet, but will upload more details of what rmvb I tried to play.....
I have a whole library in rmvb including animations, documentations and dramas which can't be play smoothly on my old laptop
wish that I can fix this problem asap
and thx very much for replying~
One of the rmvb file I use has this property which I copied from GOM player on my laptop~
*** VIDEO INFO ***
Input Type : YV12(RAW)
Input Size : 700 x 396
Output Type : YV12
Output Size : 700 x 396
FrameRate(Frame/sec) : 0.00 (25.00)
*** AUDIO INFO ***
SampleRate(Sample/sec) : 44100
BitRate(Bit/sample) : 16
Channels : 2
KBitRate(KBit/sec) : 0
another file I got this:
*** DIRECTSHOW FILTER LIST ***
1. Default DirectSound Device
2. VMR9 - Renderless mode
3. Gretech Audio
4. Gretech Video
5. MPC - RealVideo Decoder
6. MPC - RealAudio Decoder
7. MPC - RealMedia Splitter
8. Gretech File Stream
*** VIDEO INFO ***
Input Type : YV12(RAW)
Input Size : 720 x 408
Output Type : YV12
Output Size : 720 x 408
FrameRate(Frame/sec) : 11.89 (23.98)
*** AUDIO INFO ***
SampleRate(Sample/sec) : 44100
BitRate(Bit/sample) : 16
Channels : 2
KBitRate(KBit/sec) : 0
thank you for inspecting my problems! and hope this piece of info would help
I have the same problem. MX player simply cannot play any rmvb files. Mobo Player can only play some of my rmvb files.
Those are the same rmvb files that my Prime used to play perfectly on MX player.
Any help please?
hey!
I found a way to fix this ~
try move your rmvb files to yr prime's internal storage under /video
MX Player will automatically search these files and I manage to play those file just like what I can do before .13 update
but it only works when those file under /video .... this is kinda annoying but I can still watch some of my fav movie on prime for now... lol
hi my guys
i've a silly question! coz im a Noob
lemme explain what is my mean:
custom kernels supports init.d and we can create own tweaks and save these files into init.d directory,
for example this one :
vm.dirty_ratio=20;
i found dirty_ratio in /proc/sys/vm/dirty_ratio.
but when i open this file with text viewer , i see another value for this parameter!
like this : 35
and other parameters that we can write in initd tweak files!
every time i change values , when i open original file in /proc/sys/vm/ i see constant values! ( for example 35 for dirty_ratio )
i think ROM or some apps control this parameter!
it means if we change this parameters for customization , we cant see any changes!
emmm , jelly sandwich - maxio made - custom rom control this parameters??????
or you have same problems with all ROMS???????
or this is a common situation??????
sorry for poor english!
My Device : Xperia Ray
ROM : Jelly Sandwich 8.5
Kernel : Advanced Stock.587
Unlocked , Rooted!
Maybe the init.d script not properly created..init.d script must have execution lines in the script and # symbol.
Sent from my gorgeous ST18i
yamin8000 said:
hi my guys
i've a silly question! coz im a Noob
lemme explain what is my mean:
custom kernels supports init.d and we can create own tweaks and save these files into init.d directory,
for example this one :
vm.dirty_ratio=20;
i found dirty_ratio in /proc/sys/vm/dirty_ratio.
but when i open this file with text viewer , i see another value for this parameter!
like this : 35
and other parameters that we can write in initd tweak files!
every time i change values , when i open original file in /proc/sys/vm/ i see constant values! ( for example 35 for dirty_ratio )
i think ROM or some apps control this parameter!
it means if we change this parameters for customization , we cant see any changes!
emmm , jelly sandwich - maxio made - custom rom control this parameters??????
or you have same problems with all ROMS???????
or this is a common situation??????
sorry for poor english!
My Device : Xperia Ray
ROM : Jelly Sandwich 8.5
Kernel : Advanced Stock.587
Unlocked , Rooted!
Click to expand...
Click to collapse
You can check your init.d scripts with script manager (or something similar) before you jam them into the init.d folder. This way you can test them with out having to reboot your device. There is a pretty good tut for init.d from irridaki here: http://forum.xda-developers.com/showthread.php?t=1422061 It is mostly for getting init.d to work on stock roms...but it should work on custom roms as long as there is init.d support....
to change a value in /proc you have to use:
Code:
echo [I]value[/I] > /proc/[I]path/to/file[/I]
so in your case it's
Code:
echo 20 > /proc/sys/vm/dirty_ratio
Haaop said:
to change a value in /proc you have to use:
Code:
echo [I]value[/I] > /proc/[I]path/to/file[/I]
so in your case it's
Code:
echo 20 > /proc/sys/vm/dirty_ratio
Click to expand...
Click to collapse
thnx man
yes, i saw this pattern for setting values to parameters
ill check it plus will tell u the feedback
Tested in (probably works in other Sony devices as well):
Xperia Z2 23.1.A.1.28 5.0.2
Rooted
Unlocked bootloader
If you have been greeted by these hateful messages when trying to connect to Miracast (EZcast)
"Could not turn on Screen mirroring. The output device is not ready or does not support HDCP."
"Could not start mirroring on the screen. Make sure the output device supports HDCP."
Probably you already have tried changing /system/etc/wfdconfig.xml:
Code:
...
<ContentProtection>
<Valid>1</Valid>
...
to
Code:
...
<ContentProtection>
<Valid>0</Valid>
...
After that the mirroring probably worked but got greeted by
"The output device does not support HDCP. You can only mirror unprotected content of the following applications:
Xperia Home, Video, Music or Walkman, Settings"
and then just before the mirroring get disconnected
"
Your output device does not support HDCP. Cannot mirror. You still can mirror some apps and unprotected content to the device."
There is a very easy fix, in this file /system/build.prop just below
Code:
persist.debug.wfd.enable=1
add
Code:
persist.debug.wfd.appmonitoring=1
and then from ADB
Code:
adb shell su setprop persist.debug.wfd.appmonitoring 1
Restart your phone, it should work.
As @s107ken mentioned in #14, In case of boot loop, go to TWRP and then
Code:
adb shell chmod 644 /system/build.prop
Cheers
themightydeity said:
Tested in (probably works in other Sony devices as well):
Xperia Z2 23.1.A.1.28 5.0.2
Rooted
Unlocked bootloader
If you have been greeted by these hateful messages when trying to connect to Miracast (EZcast)
"Could not turn on Screen mirroring. The output device is not ready or does not support HDCP."
"Could not start mirroring on the screen. Make sure the output device supports HDCP."
Probably you already have tried changing /system/etc/wfdconfig.xml:
Code:
...
1
...
to
Code:
...
0
...
After that the mirroring probably worked but got greeted by
"The output device does not support HDCP. You can only mirror unprotected content of the following applications:
Xperia Home, Video, Music or Walkman, Settings"
and then just before the mirroring get disconnected
"
Your output device does not support HDCP. Cannot mirror. You still can mirror some apps and unprotected content to the device."
There is a very easy fix, in this file /system/build.prop just below
Code:
persist.debug.wfd.enable=1
add
Code:
persist.debug.wfd.appmonitoring=1
and then from ADB
Code:
adb shell su setprop persist.debug.wfd.appmonitoring 1
Restart your phone, it should work.
Cheers
Click to expand...
Click to collapse
Thanks !!!
All ok with mirroring!!!
themightydeity said:
and then from ADB
Code:
adb shell su setprop persist.debug.wfd.appmonitoring 1
Restart your phone, it should work.
Cheers
Click to expand...
Click to collapse
where i have to write this? if i use adb from pc it says that not found the file. from terminal emulator it says device not found. Can you explain it?
edit: ok now works. any mode to send 5.1 audio for film? default is 2ch
fer2503 said:
where i have to write this? if i use adb from pc it says that not found the file. from terminal emulator it says device not found. Can you explain it?
edit: ok now works. any mode to send 5.1 audio for film? default is 2ch
Click to expand...
Click to collapse
How you do this any tutorial?
For adb
Edit: Got it!
Working flawlessly!
after doing like what OP showed, i also got the file not found at the final step. Could someone help me sort this out
p/s: actually i received the error :
sh: persist.debug.wfd.appmonitoring: not found
I use terminal emulator:
Write in this order:
Su
Press enter and after write:
setprop persist.debug.wfd.appmonitoring 1
now reboot and all Works
Works for me! Xperia ZL 6506
Not needs run
Code:
adb shell su setprop persist.debug.wfd.appmonitoring 1
Encripted content like Netflix not works!
Hi! Should it work with locked bootloader? Root required? Thanks!
i see the display mirroring on tv in 720p only, not in 1080p with my z1. with other device the microsoft display adapter works at 1080p. any solution about that?
Thank you so much, this worked great, I can now get my screen mirroring working again.
I had no idea that unlocking the boot loader would kill HDCP...
Thanks for the hard work.
zaryab360 said:
How you do this any tutorial?
For adb
Edit: Got it!
Working flawlessly!
Click to expand...
Click to collapse
i also got error msg "device not found" while entering adb command ... can u plz me how to do it??
OMG, i waited this so long, thanks a lot
z1c 5.0
Hi, after doing everything OP described my phone went on to bootloop after restart. I restored everything from TWRP backup and tried again, same thing happened after changing the build.prop and rebooting (now I didn't even change wfdconfig.xml, so the changed build.prop must be causing the bootloop, right?). Am I doing something wrong?
adb shell chmod 644 /system/build.prop
Sent from my GT-I9305 using XDA Free mobile app
thanks a lot s107ken, that solved the bootloop problem, but still screen mirroring doesn't work properly and gives me HDCP error. I am on 5.1.1 btw... could that be the real issue here?
Work on Xperia M4 Aqua with unlocked bootloader!
Display mirroring on tv in 720p only, not in 1080p but I'm hapy
Thanks!
Followed steps as they are ... No difference running existenz premium 3.5v Z2
Are there way to change resolution? I see some rows about resolution in wfdconfifg.xlm
Enviado desde mi E2303 mediante Tapatalk
Thanks, that works for me.
I skiped the last step, but it worked for me...
Fixed everything!
Can't believe it! That fixed everything!
Few things I want to note:
I did this on a Unlocked / Rooted Xperia Z4 LTE (v.260)
I followed all the steps listed in the original post and ended up in a bootloop.
Using the method @s107ken mentioned above ( adb shell chmod 644 /system/build.prop ) in TWRP fixed the bootloop.
Can confirm this is still working on the newer devices. Great to be able to cast to large screens again. Thanks @themightydeity and @s107ken
I have a x86 built Android box and this device has HDMI and onboard sound out.
Sound is working fine from the onboard sound out but does not work with the HDMI.
I ran "alsa_aplay -l" and can seen there is only "card 0" and this card has 3 devices.
The HDMI is at hw:0,3
So I then ran "dd if=dev/urandom bs=8000 count=1 | alsa_aplay -D plughw:0,3" and can hear sound from the HDMI.
Looks like I needed to change the default device.
So I created "/system/etc/asound.conf" and added the following:
Code:
pcm.!default {
type hw
card 0
device 3
}
ctl.!default {
type hw
card 0
device 3
}
This didn't seem to work.
So I then created "~/.asoundrc" with the same code listed above but that didn't work.
I ran "cat /system/usr/share/alsa/alsa.conf" to verify that it should be reading both "asound.conf" or ".asoundrc" but it looks like Android is ignoring these config files.
Welcome!
Short and painless for You
No Root needed
Download the Android Platform Tools from Google
Extract the Folder Containing adb & fastboot
open a Terminal in the extracted Folder
run one by one:
adb shell
service call SurfaceFlinger 1035 i32 x
(x can be 0,1,2 or 3)
0. 1096x2560x60Hz
1. 1644x3840x120Hz
2. 1644x3840x60Hz
3. 1096x2560x120Hz
Feel free to spend Me a Coffee if You enjoy this! <3
@Miustone
I'm sorry, but the same subject is already covered HERE, and you are participating in it.
This OP is closed