Yes - I know that Google allows a screencast to Chormcast, but not on smart TVs. Now I have a new LG OLED with WebOS 4.5. A screencast is possible with my wife's Samsung J7, but not with my Pixel2XL - wow!
A "Google"-search didn't really help me.
Magisk module miracast module leads to the bootloop
build.prop cannot be edited with Android Q either, because I cannot mount the system partition in TWRP either.
Does anyone have an idea?
Sounds like "miracast" is the issue. My SmartTV (Philipps 55PUS8804) comes with Android TV and has Chromecast built in. Screencasting works flawlessly. The Pixel2 XL does not come with miracast support out of the box. Maybe you give one of these apps a try: https://play.google.com/store/search?q=miracast
ademmer said:
Sounds like "miracast" is the issue. My SmartTV (Philipps 55PUS8804) comes with Android TV and has Chromecast built in. Screencasting works flawlessly. The Pixel2 XL does not come with miracast support out of the box. Maybe you give one of these apps a try: https://play.google.com/store/search?q=miracast
Click to expand...
Click to collapse
Thanks for the tip. It is actually a "Google - miracast" -issue. Shame on Google - A simple miracast streaming seems to be denied to pixel users!
MartinN6 said:
Thanks for the tip. It is actually a "Google - miracast" -issue. Shame on Google - A simple miracast streaming seems to be denied to pixel users!
Click to expand...
Click to collapse
If you're willing to downgrade you can flash the April factory image and the magisk module will work,i stayed on the April update for a while till Android 10 was released but miracast worked just fine
Related
Hello,
I have a car, the Citroen C-Elysee with support for Android Auto and MirrorLink; Android Auto works ok, but MirrorLink is not supported on MIUI afaik.
I'd read that MirrorLink has more features than Android Auto, so I'd like to test it
Any custom rom, hack app that by any means could enable it ?
Thanks in advance !
No way. Why don't you use Android Auto with root access
https://www.youtube.com/watch?v=vNlIbFHI6oM
shaggyxda said:
No way. Why don't you use Android Auto with root access
https://www.youtube.com/watch?v=vNlIbFHI6oM
Click to expand...
Click to collapse
Yep ! I didn't know about it, works awesome !!!
But I crawled a while until I got it to work: Android Auto version < 3 required, and enable unknown sources in Android auto.
Also I've found a newer version "Plus" with some more options.
Thanks a lot.
does it work with VW infotainment (Passat B8, Discover media) ???
Do not want to use AndroidAuto, limited to Google apps only (Idem with Apple and their system).
Any way to install Mirrorlink, tho?
I have a DS5 and it is not compatible with Android Auto, but only with MirrorLink.
You can't install Mirrorlink on the unsupported phone, since this technology uses hardware components, afaik. It is actually dead technology since there is small set of phones supported (check out on the official mirrorlink website)
mirrorlink unsupported with my mi9 and other xiaomi phones. Crying...
Don't like android auto limited to google apps. beeaaarkk !!! ****.
Hello,
I was trying to mirror the screen of pixel 3xl to samsung smart tv but guess what, wasn't possible to do so.
With BN my s9+, pocophone and s8 can do it easily, since the above TV is recognized as a screen cast device.
I searched on internet about this and all I could find was that pixel devices must be rooted, in buidprop this "persist.debug.wfd.enable" line with value of 1 must be added, in order to get screen casting to work.
Do you guys have the same problem? And if so, what have you done to overcome it?
Cheers
Since there are the pixel smartphones, the method doesn't work anymore. But I had seen a Magisk module somewhere.
Atomregen said:
Since there are the pixel smartphones, the method doesn't work anymore. But I had seen a Magisk module somewhere.
Click to expand...
Click to collapse
screen mirroring works fine, default service is very touch and go, but 3rd party one work fine. I stand corrected, default function only works with google cast now.
Hi there!
Some of you can play hdr content on Amazon prime video? The 7T is supposed to be certified but the maximum quality I can get is fullHD.
Back on November the option was there (settings-quality-streaming) which was 5.8GB/h but it disappeared three weeks ago. Now, the maximum is 1.8GB/h (fullHD).
Thanks.
Nobody with Amazon prime video? Really?
I am happy to check, but I honestly don't know how?
Not present
Just checked it's stuck at 1.8GB/Hr ! Any way to bring it back to 5GB / Hr ?
Cowbell_Guy said:
I am happy to check, but I honestly don't know how?
Click to expand...
Click to collapse
It's quite simple. Play a video with hdr option (the boys, the man in the hight castle, Jack Ryan, carnival row...).
While you are playing it (over WiFi if you can) touch the screen and under the duration bar you will see the resolution (hd, hd 1080 or hdr).
Or you can go to settings-qualitity-streaming (or download) and you should see something above 5GB/h.
swaroopce said:
Just checked it's stuck at 1.8GB/Hr ! Any way to bring it back to 5GB / Hr ?
Click to expand...
Click to collapse
I think is related to Amazon. This happens since they updated the app back on November (blue icon instead of white).
I cannot find the APK corresponding to the October version.
Pantumaca said:
I think is related to Amazon. This happens since they updated the app back on November (blue icon instead of white).
I cannot find the APK corresponding to the October version.
Click to expand...
Click to collapse
I just tried installing last 3 builds from Apkmirror and can confirm all 3 had same 1.8GB / Hr.
Sep build was worse as it has 460mb/hr.
Everytime I tried installing a new build, deleted all the cache and trace files of previous installation and proceeded. No luck
Update on 27th January 2020
I recently purchase the OnePlus 7T - HDR works on Netflix & YouTube. However, doesn't work on PrimeVideo app.
I had a chat with someone from the Amazon Support, here's an excerpt from that conversation (AgentName redacted) -
AgentName: Right now, Phones which has the Widevine L1 certification are able to access the videos in HD format only.
AgentName: Currently, HDR is not introduced in Prime Video app.
Me: Is that a region specific thing?
AgentName: We're adding the support for the phone one by one.
Me: Okay. Is there a list of phones that have already received the support? Something that will keep getting updated so that we can figure out which devices are now compatible
AgentName: We are working on this to adding the support for the phone one by one.
AgentName: To help you out, I've forwarded your expectations to our Prime videos Development Team so that they will look into this and may come up with HDR support for your phone in future updates.
Me: Okay. Thank you for your time AgentName. That's all I needed.
I think OnePlus should've done some work with these companies to ensure that their devices get HDR on these platforms before they mass produce and sell them. Hopefully this issue will be resolved soon. :fingers-crossed:
I'm looking for a stable rom for my tab s 8.4 LTE. Could anyone recommend me a rom where the camera, sim card/LTE, and phone calls work properly? I'd be really grateful. Also, where can I find a stock Samsung ROM just in case I wanted to go back?
I don't have your SM-T705, but I recently did get a used SM-T700 and immediately installed LineageOS 7.1.2 on it with no regrets.
The only place I could find the OEM ROM was SamMobile. Unless you have unlimited patience, I suggest buying the membership (@ $10) long enough to do a premium download.
I'm on 705 and installed 7.1 LOS the only thing I'm missing is Netflix / Prime Video in HD
bustr85 said:
I'm on 705 and installed 7.1 LOS the only thing I'm missing is Netflix / Prime Video in HD
Click to expand...
Click to collapse
Is that because of the LineageOS or because of the Netflix apk? I think I can understand Prime. Amazon doesn't like us Android people. Even though they are one.
wellersl said:
Is that because of the LineageOS or because of the Netflix apk? I think I can understand Prime. Amazon doesn't like us Android people. Even though they are one.
Click to expand...
Click to collapse
It's because it was a challenge to install Netflix (device not supported) once you have your device rooted you also loose the HD capability in Netflix. I haven't found a way to make it work so in the Netflix app the maximum playback quality is sd
bustr85 said:
It's because it was a challenge to install Netflix (device not supported) once you have your device rooted you also loose the HD capability in Netflix. I haven't found a way to make it work so in the Netflix app the maximum playback quality is sd
Click to expand...
Click to collapse
Could you link to that ROM? What about LTE, camera, and phone calls? Does it offer voltage control too? I'd like to to optimize the cpu for better performance and less heat.
Verdinex said:
Could you link to that ROM? What about LTE, camera, and phone calls? Does it offer voltage control too? I'd like to to optimize the cpu for better performance and less heat.
Click to expand...
Click to collapse
The LTE works, I've tried it briefly, and I've made a phone call too, that is fine. I haven't tried the camera or looked into anything with changing CPU frequency. I suspect you could do so via via Magisk or similar. The Rom is LOS 14.1 from this forum you can find it in the android development section.
There is a bug in LineageOS 17.1 on multiple hardware where Miracast/ Screen cast no longer works. I noticed this on my Xiaomi Pocophone F1 (beryllium) when I did a 20200801 nightly upgrade.
My question is, is the bug in the AOSP or the LineageOS? Is it something that Google has done to force people to use Chromecast or is it a problem with the LineageOS that hasn't yet been fixed?
It's a very annoying bug and I wonder how easy it is for the developers to fix? Can it be fixed by a user changing a setting or is it a default setting that an uninformed user is unlikely to be able to change?
BuzLightSabre said:
There is a bug in LineageOS 17.1 on multiple hardware where Miracast/ Screen cast no longer works. I noticed this on my Xiaomi Pocophone F1 (beryllium) when I did a 20200801 nightly upgrade.
My question is, is the bug in the AOSP or the LineageOS? Is it something that Google has done to force people to use Chromecast or is it a problem with the LineageOS that hasn't yet been fixed?
It's a very annoying bug and I wonder how easy it is for the developers to fix? Can it be fixed by a user changing a setting or is it a default setting that an uninformed user is unlikely to be able to change?
Click to expand...
Click to collapse
Usually features can vanish in an android version upgrade, but not in a regular update.
https://wiki.lineageos.org/bugreport-howto.html
kurtn said:
Usually features can vanish in an android version upgrade, but not in a regular update.
https://wiki.lineageos.org/bugreport-howto.html
Click to expand...
Click to collapse
Yes. I would have thought that this was so but Miracast was working until I updated a 20200801 nightly build. That's why I think that it might be a default setting.
I also noticed this:
https://forum.xda-developers.com/showpost.php?p=64121701&postcount=10
Maybe that will solve the problem?
BuzLightSabre said:
There is a bug in LineageOS 17.1 on multiple hardware where Miracast/ Screen cast no longer works. I noticed this on my Xiaomi Pocophone F1 (beryllium) when I did a 20200801 nightly upgrade.
My question is, is the bug in the AOSP or the LineageOS? Is it something that Google has done to force people to use Chromecast or is it a problem with the LineageOS that hasn't yet been fixed?
It's a very annoying bug and I wonder how easy it is for the developers to fix? Can it be fixed by a user changing a setting or is it a default setting that an uninformed user is unlikely to be able to change?
Click to expand...
Click to collapse
Google creates Android Compatibility Definition Documents, in which it is written:
Code:
5.8. Secure Media
If device implementations support secure video output and are capable of supporting secure surfaces, they:
[C-1-1] MUST declare support for Display.FLAG_SECURE.
If device implementations declare support for Display.FLAG_SECURE and support wireless display protocol, they:
[C-2-1] MUST secure the link with a cryptographically strong mechanism such as HDCP 2.x or higher for the displays connected through wireless protocols such as Miracast.
If device implementations declare support for Display.FLAG_SECURE and support wired external display, they:
[C-3-1] MUST support HDCP 1.2 or higher for all external displays connected via a user-accessible wired port.
That's the theory. In practice, everything depends on programmers.
For example.
In the custom ROM with Android 9 for Oneplus One Miracast (connection to Microsoft Wireless Display Adapter) works only in 3 ROMs with 33 that I tested.
In the custom ROM with Android 10 for Oneplus One Miracast (connection to Microsoft Wireless Display Adapter) does not work in any ROM with 25 that I tested.
.
.
Miracast starting working again after build 20200829. There was d"ummy HIDL lib" removed that shouldn't have been removed and now it's back again. https://review.lineageos.org/284011
BuzLightSabre said:
Miracast starting working again after build 20200829.(...)
Click to expand...
Click to collapse
To which model of device do you cast the screen in Android 17.1 using Miracast (WiFi Display)?
.
I have a Panasonic Personal Video Recorder (PVR) model number DMR-BWT955. Under its Function menu there's an option to "Miracast". I select that option and it starts searching for devices. I select the "Screen Cast" option from the drag down menu on my Pocophone and select the "DMR-BWT955" device to connect to. They both do their bits and then I see my Pocophone screen showing up on my TV screen, which is connected to the PVR. My 5.1 surround sound system is also connected to the PVR and so I can not only see what's on my Pocophone but also hear what's it's playing through the 5.1 sound system.
Is that the sort of information that your after?
BuzLightSabre said:
Miracast starting working again after build 20200829. There was d"ummy HIDL lib" removed that shouldn't have been removed and now it's back again. https://review.lineageos.org/284011
Click to expand...
Click to collapse
Hi
Still doesn't work on lineageos 17.1.
I try to connect my tv to honor 5x to miracast screen but see no tv.
I add persist.debug.wfd.enable=1 on build.prop to enble wireless display. Nd see 'Anycast' device
But when I try to connect, lineageos reboot ( hot reboot without vibration neither pin prompt)
I am using 11 mars 2021 build witch is newer than 28 ugust 2020
Build lineageos-kiwi-userdebug 10qq3a 200805.002 d5580ebdfc
Official lineageos.
Worked perfectly on lineageos 14.1, 15, 16
Cheers