Question Screen Mirror missing on Pixel 7 Pro

Search This thread

Psychlone

Senior Member
Apr 30, 2010
197
91
OnePlus 7 Pro
Google Pixel 6a
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)

photo_2022-12-24_14-27-07.jpg



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)

photo_2022-12-24_14-33-25.jpg



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.
 

schmeggy929

Recognized Themer
Apr 13, 2008
3,086
2,160
New Jersey
Google Pixel 7 Pro
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.
 

MrBelter

Senior Member
Apr 10, 2011
1,767
795
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.
 

Psychlone

Senior Member
Apr 30, 2010
197
91
OnePlus 7 Pro
Google Pixel 6a
Huh?
I can cast perfectly with just the stock quick tile
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.

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

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.
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+
 
  • Like
Reactions: HipKat

LLStarks

Senior Member
Jun 1, 2012
2,063
1,351
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.
 
  • Like
Reactions: letmedanz and kkjb
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+
That's correct. And I assume all your devices are on the same Network, right?? It's an odd problem for sure
 

MrBelter

Senior Member
Apr 10, 2011
1,767
795
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+
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.
 
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.
You know, I hadn't even considered that
 
  • Like
Reactions: MrBelter

NippleSauce

Senior Member
Jun 23, 2013
544
370
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.
 
Last edited:

chetly968

Senior Member
Jul 15, 2014
463
104
Paradise Valley
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
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.
 

moniec15

New member
Oct 28, 2009
4
5
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.
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!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    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
  • 5
    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
    3
    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)

    photo_2022-12-24_14-27-07.jpg



    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)

    photo_2022-12-24_14-33-25.jpg



    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.
    2
    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.
    2
    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.
    1
    Huh?
    I can cast perfectly with just the stock quick tile