You want support, or to report that you device works or does not work? You can open a Github issue. Outside the scope of this site.It uses the Qualcomm Diag protocol, also called QCDM or DM (Diagnostic Monitor) in order to communicate with your phone's baseband. However if it was never part of your system to begin with, you'd need to manually build it into your system. To Add MiraCast is difficult if it wasn't disabled by the manufacturer, usually to enable ChromeCast you'd disable the older MiraCast, so if you're device has ChromeCast you should be able to enable it with the information above. Now you reboot and Miracast can be enabled. If you're Lineage based rom, you will have to add the line. If you're on stock or stock based ROM, you will edit the line. I believe that designing their own cast software was necessary to combat the problems Android was experiencing.Īll you have to do is change one line on your build.prop. MiraCast has never been fully supported by Android, it usually had serious problems trying to convert the screen into a standard 1080 or 720 resolution video, this usually caused just a phone shape video on the screen and not utilizing the entire screen. I can't possibly walk you through all the system modifications that are required but it's definitely possible with root access. Then throw the command: adb shell 'echo =1 >/vendor/build.prop' Next, mount the /vendor partition from within TWRP` Open a elevated command prompt: adb reboot bootloader Open a command prompt and throw these commands: Side note: if this should put you into a bootloop, go into custom recovery TWRP. If 1 is returned, then you should be good to go. Open an elevated command prompt and throw these commands: Go down to this line of code and AFTER it: =1Īdd a new line of code by creating this line: =1 Go into the file /system/etc/wfdconfig.xmlĬhange 1 to 0 to make it look like this code.You could use the nano command to add and/or change values, but for simplicity and to stay in-bounds, just use a file explorer and text editor. The following steps require both require root access and custom recovery TWRP. If Zillinium's suggestion to make changes into the "system / build.prop" does not make it fully function, you might need to also change the "/system/etc/wfdconfig.xml" file also.
0 kommentar(er)
