My Nexus player has been struck with the dreaded Soap Opera Effect. Essentially it's a motion blur type effect that affects streaming video. Netflix, Plex, etc.
This has been happening since updating to v5.1. Anyone else having this issue? Any ideas on how to fix it?
This video will give you an idea. To see the effect, I had to run at 720p 60fps or higher.
https://www.youtube.com/watch?v=882c25af2hM
DVDWSN said:
My Nexus player has been struck with the dreaded Soap Opera Effect. Essentially it's a motion blur type effect that affects streaming video. Netflix, Plex, etc.
This has been happening since updating to v5.1. Anyone else having this issue? Any ideas on how to fix it?
This video will give you an idea. To see the effect, I had to run at 720p 60fps or higher.
https://www.youtube.com/watch?v=882c25af2hM
Click to expand...
Click to collapse
Isn't 60fps going to do that every time? Go back to 24fps and enjoy...
Maybe I'm confused...
Yeah sorry, I didn't explain clearly.
On the Nexus player we're not watching 60fps content. Just regular 24 or 30 or whatever.
I posted the youtube video so that you might see an example of what we're seeing on our TV. When watching that example video, I was only able to see the motion blur when I was watching it at 60 fps.
If you're getting any sort of frame-interpolation on video playback it is more likely that it is being done by your TV (if you have a 120Hz+ television) then the Nexus Player itself, because as far as I know the player does not have the software or hardware capabilities to do so and even if it did it wouldn't showup as a bug it would have to be enabled with some sort of third-party hack or application.
tl;dr: if you're seeing frame-interpolation in your videos, check your TVs settings and ensure "Smooth Motion" or "True Motion" or anything with that sort of name is disabled.
We're looking into that. It's an old POS TV that does 1080p, and not much else. We looked through the menu's and online, but found nothing about motion or any sort of video processing.
I'm going to test the Nexus Player with another TV and see what happens.
can confirm
It's not the TV can confirm after the update the nexus player is experiencing soap opera effect. are there settings to disable the effects?
The same thing is happening to me since the Android 5.1 update on my Nexus Player, but only under certain circumstances. The tv it is attached to is 1080p 60hz.
If i cast from plex to the Nexus Player, I get the soap opera effect, however if I use the plex app on the Nexus Player itself, I do not get the effect. Its infuriating. Does anyone know what is causing this or how to fix it?
LostSol said:
The same thing is happening to me since the Android 5.1 update on my Nexus Player, but only under certain circumstances. The tv it is attached to is 1080p 60hz.
If i cast from plex to the Nexus Player, I get the soap opera effect, however if I use the plex app on the Nexus Player itself, I do not get the effect. Its infuriating. Does anyone know what is causing this or how to fix it?
Click to expand...
Click to collapse
I have the exact same issue. And my TV is an old Sharp 60hz which has none of that Motion/Flow technology. It only happens when I cast. No issue if I use the app. I am not sure I like this effect.
Ok....well this brings up my question....
I installed showbox via air share. ...I was seeing how well it works (testing it) it I notice on the whole horizontal bottom...2inch thick it's black/white. .........all of the movie is colored but the 2inch thick whole bottom is b/w. ....I also notice after 25 to 30 min into the movie it buffed and went to the beginning of movie (played on movie) haven't tried a different movie yet
It seems the soap opera effect only happens with apps that use the native android media player (i.e. Showbox, Starz Play, Encore Play) and it is in fact, VERY ANNOYING. I know Chainfire has a tweak that allows you to change the Hz for playback, but I haven't tried it yet.
i actually would like soap opera effect on my android tv box (mk808b plus)..any idea how the nexus player does it?
yeahman45 said:
i actually would like soap opera effect on my android tv box (mk808b plus)..any idea how the nexus player does it?
Click to expand...
Click to collapse
I'm also keen on trying to port it to my device, I did some digging and found the SDK responsible for it, sadly it's intel, so unless it can be ported to some other system it's essentially useless to us.
It seems to rely on some sort of ISV lib, probably standing for Intel Smart Video, so I presume it'll be a lot of work bringing it to other devices.
https://software.intel.com/en-us/articles/frame-rate-conversion-frc-in-intel-media-sdk
https://android.googlesource.com/device/asus/fugu/+/master/video_isv_profile.xml
http://review.cyanogenmod.org/#/c/96342/3/device.mk
https://android.googlesource.com/pl...n/utils/+/ce70dcd/ISV/profile/isv_profile.cpp
Pleaaase i would love video interpolation on my Nexus 6p!!!!
That is the only reason i prefer watching stuff on my pc(with SVP interpolation) even though my nexus AMOLED is awesome(on srgb of course)
Hello,
recently I installed a streaming videos app called Showbox and have the latest version installed.
Oddly enough I get a grey bar at top when watching movie on Showbox when in full screen.
I have another streaming app, Netflix and I have no grey bar at top problem, only with Showbox.
What is the cause of this grey bar problem? I have no weather app or other GPS app that's from third-party.
This is what I'm talking about:
http://i.imgur.com/euhw0pi.jpg
the grey bar is the area that is meant to be overlayed by the app, in which you can swipe downward to show the status bar. This feature of android is a part of Android, but the app is supposed to overlay it, as stated in the SDK. The developer hasn't set the proper parameters. Write a review and email the developer in the Play store, and give them your phone model and it should be fixed soon.
MX player is far superior to any other player in Android, then why a generic icon that is the same that everyone?
I guess that the design is needed to allow identify it as a player but I guess that the letters MX could be integrated with the play icon in order to achieve something more memorable. There aren't other players that can be identified with only two letters and the icon could get the advantage of it, overlapping them to the play icon or in the top.
By the way I know that the developer doesn't plan any IOS version but it would great.
karlpj said:
MX player is far superior to any other player in Android, then why a generic icon that is the same that everyone?
I guess that the design is needed to allow identify it as a player but I guess that the letters MX could be integrated with the play icon in order to achieve something more memorable. There aren't other players that can be identified with only two letters and the icon could get the advantage of it, overlapping them to the play icon or in the top.
By the way I know that the developer doesn't plan any IOS version but it would great.
Click to expand...
Click to collapse
People never become satisfied of other's work.
Hi, I was linked here through the MX Player app on my Android S9 Plus. The MX Player was working fine years ago, so I believe these past few updates must have triggered these issues below I am hoping you can help me resolve.
1. The icon should stay on my lock screen, but it keeps disappearing after some time. Restarting the player does not help at all, the icon just vanishes for some reason. The only way it would reappear is if I stop using the player for some time, as if the player needs some kind of rest or break, this never happened in the past.
2. The videos I watch now show titles so big that they don't even fit entirely on the top bar of the videos, looks very strange and inconvenient. I checked again and again, over and over, in the settings but found nothing to change the font of the video title. Again, this is also something that never had to be adjusted in the past, the title would look perfectly fine and fit perfectly in the top bar with its default settings.
Please help. I really appreciate and love using MX Player on my Android phone, in fact I have been using MX Player for years now, so I really do hate it when new updates come in just to screw things up randomly. Honestly if those are just optional improvements I really shouldn't have updated the app accidentally, I mean really everything has been working nicely up to this point it's just so upsetting. Help please, thank you
Hey all.
I preordered the Pixel 7 Pro, rooted it right out of the box and have been using it for months now. Overall it's been a great phone but I'm **STRUGGLING** with some basic things that bug the crap out of me and I'm reaching out for some input.
First of all, the x64-only architecture. I know there's nothing you or I can do about it, but it's BS that Google introduced it without any warnings at all.
I fully realize that app developers need to update their software to be compliant with the future, that's a given, but there are several that still haven't updated their app to be compliant that I used multiple times per day. Things like where their app incorrectly identifies my Pixel 7 Pro as a tablet with a weird resolution and it automatically adjusts to a split screen while in portrait mode, making everything illegible. That one sucks because it's my invoicing program that I've got years of invoices in. Another app FC every time I try to full-screen the app - unbearable when it's the app for your security cameras. BOTH devs have been notified months ago and still no progress on a fix even though they've updated their apps a half dozen times since then.
Second, the screen mirror function is completely missing from my Pixel 7 Pro. I'm unclear if it's something I've done or if Google made it so this is the new "normal".
On my previous phone, a OnePlus 7 Pro, running Derpfest A12, I could pull down the shade, tap "Screen Cast" and it would find my 2 Chromecasts AND my Samsung TV and would connect to the TV with one more tap.
On the Pixel 7 Pro, it only sees the 2 Chromecasts, no TV is found at all. Yet I can cast Youtube directly to the TV without any extra button presses, no issues at all - just cannot mirror my screen like on the OP7P.
In my screenshots, note that my Chromecast devices are named "trojan.B and trojan.D", that's to help deter the neighbors from even trying to connect LOL.
OnePlus 7 Pro Cast settings: (notice the "Enable wireless display" option at the upper right that's 'hidden' under the 3 dots)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And my Pixel 7 Pro Cast settings: (note there is no 3 dots where I can enable wireless display and that the TV doesn't show up at all)
Have I done something to disable casting to my TV? This is driving me nuts. Everything I've read online and watched in youtube vids shows that this *should* be possible.
I've gone into Google Home and set up everything that's available in there, but the TV still doesn't show up.
Third thing that's KILLING me about this phone is that Viper4Android doesn't work because there is no x64 driver (yet). Of course this is subjective. I prefer V4A over everything else, have been an avid user of V4A for years and have custom built profiles for each of my devices. I'm currently just skating by with Wavelet, but I've tried JamesDSP and I can get kind of close, but it's not like V4A for me.
I know that there are some people working on it and that they're making progress with a new x64 driver and the app overall, but man, this one really hurt.
If I had known that my new $1100 phone was going to be this much trouble for me, I would've just stuck with the OP7P or went in a different direction. I'm currently feeling like I spent $1100 to be partially disabled and unhappy with what's supposed to be the best phone on the market.
Ideas and thoughts that are helpful are much welcomed.
Huh?
I can cast perfectly with just the stock quick tile
You are correct on Google springing x64-only architecture. However we all were notified that the future will be 64 bit only system 2 years ago. Second screencast works just fine on my phone, there is even a quick settings toggle. V4A was a great App prior to Android 13. It was the main reason why I even root .All developers were giving a 2 year notice to be 64bit compatible. Developers are the ones to blame for them not working on the Pixel 7 series. Luckily JamesDSP is a great alternative to V4A. Loudness, bass and clarity are pretty close to profiles I used in V4A.
Screen mirroring was removed from Android when Marshmallow was released in 2015. Natively Android now only uses Chromcast or DIAL which is what YouTube uses, OnePlus will have implemented their own solution to re-enable it.
HipKat said:
Huh?
I can cast perfectly with just the stock quick tile
Click to expand...
Click to collapse
That's what I'm talking about and what doesn't work on my phone. At least I know I can factory reset and get that functionality back I guess.
I literally did nothing weird to my phone, I rooted it right out of the box and installed my apps but my Screen Cast toggle only shows the 2 Chromecast devices and not the TV. Same network, same subnet, no VPN or firewall in between - it's my internal network! (I literally install end-user internal networks for a living)
Thanks for the screenshots verifying it's possible. Something is obviously borked with my phone.
schmeggy929 said:
You are correct on Google springing x64-only architecture. However we all were notified that the future will be 64 bit only system 2 years ago. Second screencast works just fine on my phone, there is even a quick settings toggle. V4A was a great App prior to Android 13. It was the main reason why I even root .All developers were giving a 2 year notice to be 64bit compatible. Developers are the ones to blame for them not working on the Pixel 7 series. Luckily JamesDSP is a great alternative to V4A. Loudness, bass and clarity are pretty close to profiles I used in V4A.
Click to expand...
Click to collapse
Yep, I realize about the x64 architecture, and I don't want to go backwards. I also realize it's 100% the dev's fault. 2 years is a long enough time to completely recode their app if need be, but it's like it caught some of them off guard. FWIW, their apps do install but our screen resolution forces the app to think it's a larger screen than it is and so when they use split screen in portrait mode, it's truncated or bunched up all together, or it simply FC the app. The apps work perfectly just like they used to other than this.
As for JamesDSP, I can't make it work right. I mean, I can get kind of close, but I actually get frustrated before I can get it close enough to my liking. Like you, I have only rooted my last couple phones for V4A and was severely disappointed to learn that it can't even be installed on the P7P. For whatever reason, JDSP just doesn't do what V4A did for me.
MrBelter said:
Screen mirroring was removed from Android when Marshmallow was released in 2015. Natively Android now only uses Chromcast or DIAL which is what YouTube uses, OnePlus will have implemented their own solution to re-enable it.
Click to expand...
Click to collapse
Maybe I didn't use the correct wording?
HipCat shows that when they hit the "Screen Cast" QS tile, they can select their TV and it mirrors exactly what's on their phone. I assume that what we're looking at in HipCat's screenshots is indeed a direct phone to tv cast. When I tap my Screen Cast QS tile, it shows the 2 chromecasts in the house but not the TV, whereas my OnePlus 7 Pro shows them and the TV too and when I select it, it mirrors what's on my screen.
The TV is a 2020 Samsung 75" Q60, it's been able to do this with my OP7P and my older Galaxy S8+
Pixel doesn't support Miracast screen casting (wireless display) and hasn't for years. It's an intentional design and it doesn't matter what your old phone could do. Same reason we can't do video out over USB.
Some newer TVs do support Google's casting protocol and can use that for true screen mirroring. I've seen some LG and Sony TVs do that.
Psychlone said:
Maybe I didn't use the correct wording?
HipCat shows that when they hit the "Screen Cast" QS tile, they can select their TV and it mirrors exactly what's on their phone. I assume that what we're looking at in HipCat's screenshots is indeed a direct phone to tv cast. When I tap my Screen Cast QS tile, it shows the 2 chromecasts in the house but not the TV, whereas my OnePlus 7 Pro shows them and the TV too and when I select it, it mirrors what's on my screen.
The TV is a 2020 Samsung 75" Q60, it's been able to do this with my OP7P and my older Galaxy S8+
Click to expand...
Click to collapse
That's correct. And I assume all your devices are on the same Network, right?? It's an odd problem for sure
Psychlone said:
First of all, the x64-only architecture. I know there's nothing you or I can do about it, but it's BS that Google introduced it without any warnings at all.
Click to expand...
Click to collapse
Google advised devs about a year ago that x64 only was coming and they to plan accordingly
Psychlone said:
Maybe I didn't use the correct wording?
HipCat shows that when they hit the "Screen Cast" QS tile, they can select their TV and it mirrors exactly what's on their phone. I assume that what we're looking at in HipCat's screenshots is indeed a direct phone to tv cast. When I tap my Screen Cast QS tile, it shows the 2 chromecasts in the house but not the TV, whereas my OnePlus 7 Pro shows them and the TV too and when I select it, it mirrors what's on my screen.
The TV is a 2020 Samsung 75" Q60, it's been able to do this with my OP7P and my older Galaxy S8+
Click to expand...
Click to collapse
Looks like Hipcat is casting to an Android TV (as well as a raft of Google products), as i said screen mirroring (well Miracast) was removed from android in 2015 and if you have had another phone working it is because they have added a solution of their own.
MrBelter said:
Looks like Hipcat is casting to an Android TV (as well as a raft of Google products), as i said screen mirroring (well Miracast) was removed from android in 2015 and if you have had another phone working it is because they have added a solution of their own.
Click to expand...
Click to collapse
You know, I hadn't even considered that
I've been working with this awesome developer who figured out how to screen mirror from a Pixel phone to a Samsung TV via DLNA.
This app is in beta, but IT WORKS!!!
The app is called Screen Mirror Max
Screen Mirror Max - Apps on Google Play
Multi-Screen Mirror to Chromecast and Roku TVs with Audio, also to Web Browser
play.google.com
So weird. I have noticed this too when I was using my Pixel 6 Pro. I could still cast to my Samsung TV until I upgraded to Android 13. Once I was on A13, the same Samsung TV could no longer be casted to from the same phone.
It is unfortunate, however, it is what we currently have. I snagged a 4K Chromecast in order to use casting again, however, the quality and aspect ratio is rather horrible via the Chromecast vs how it was with direct casting to the TV. So, needless to say, but I haven't used casting ever since these changes went into effect.
Side note, but the lack of video transmission over USB-C kinda stinks too. I mean, you technically can over USB-C if you buy a specific adapter for around $50 - $60, however, it results in too many cables sitting around. Additionally, the quality still is not as good as it should be over a wired video connection and the audio doesn't transfer properly (as it transfers with around -75db volume) =(.
Moral of the story from these changes would be to buy a new television that has more modern app features built in so that you no longer need to stream from your phone. However, we don't all have an extra few thousand dollars laying around to purchase a new television, haha. So, I've settled to lose my good eyesight sooner and to just squint at my phone instead lol.
To remedy this, I think that I will get the Pixel Fold once the price drops to around $1000 flat. At that price, along with my store credit and my P7P trade-in, I am hoping that I can get it for around $300. But, of course, one can always wish =P.
moniec15 said:
I've been working with this awesome developer who figured out how to screen mirror from a Pixel phone to a Samsung TV via DLNA.
This app is in beta, but IT WORKS!!!
The app is called Screen Mirror Max
Screen Mirror Max - Apps on Google Play
Multi-Screen Mirror to Chromecast and Roku TVs with Audio, also to Web Browser
play.google.com
Click to expand...
Click to collapse
Hey that's awesome if it actually mirrors the screen without an website work around. I'm trying to use it and it seems it will only cast videos or photos and stuff and not actually mirror to my Samsung. I'm probably doing something wrong but I haven't had a chance.to really work out the UI yet.
chetly968 said:
Hey that's awesome if it actually mirrors the screen without an website work around. I'm trying to use it and it seems it will only cast videos or photos and stuff and not actually mirror to my Samsung. I'm probably doing something wrong but I haven't had a chance.to really work out the UI yet.
Click to expand...
Click to collapse
Yeah I'm not sure what you're doing on your end but I can straight up screen mirror.
Like I said, there is a delay, but screen mirroring works from my Pixel 7P!