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 !!! ****.
Related
Hello, anyone used this headset for hox? is it fully working?
http://www.sonymobile.com/global-en/products/accessories/stereo-bluetooth-headset-sbh20/
ofcourse...
Super-Veloce said:
ofcourse...
Click to expand...
Click to collapse
Have you tried by yorself?
no.. but why shouldn't it work?
Not full compatible
Hi i have an sony sbh-20 and works great in my android 2.2 but in my notebook Asus G51jx with the Bluetooth Broadcom BT-253 module only work the sound or the mic once a time. in other words, not work how handsfree!! and sony techSupport was say not compatible with PC platform. I realy disanimated with my product (sorry if my english not are good, i learning it very slow )
i will are useful for somewhere.
I Quote:http://www.knowyourmobile.com/android/android-kitkat/19689/android-44-kitkat-launches-release-date-features-and-all-sweetest-news
Built in support for IR blasters
“Android 4.4 introduces platform support for built-in IR blasters, along with a new API and system service that let you create apps to take advantage them.”
That means all new Android handsets, providing they have latent IR functionality, can be used to control a myriad of devices including your HDTV and stereo.
And because the API is open to developers there’s likely to be all kinds of IR Blaster features added to current and upcoming applications and content inside Google Play.
Click to expand...
Click to collapse
...So does this mean we can finally get auto-learning IR Remote functionality on our LGOGP, similar to what the LGOG2 has
Crinos512 said:
I Quote:http://www.knowyourmobile.com/android/android-kitkat/19689/android-44-kitkat-launches-release-date-features-and-all-sweetest-news
...So does this mean we can finally get auto-learning IR Remote functionality on our LGOGP, similar to what the LGOG2 has
Click to expand...
Click to collapse
I'm guessing not...
Hey,
I'm currently looking for a smartphone with long battery life and support of HQ sound (LDAC preferred).
I found some ROMs with Android 8.0 and I heard that this version of OS supports LDAC. Does it mean that when I install one of these ROMs, I will be able to use LDAC?
Koprzywa said:
Hey,
I'm currently looking for a smartphone with long battery life and support of HQ sound (LDAC preferred).
I found some ROMs with Android 8.0 and I heard that this version of OS supports LDAC. Does it mean that when I install one of these ROMs, I will be able to use LDAC?
Click to expand...
Click to collapse
LDAC is included in AOSP since Oreo so you should be able to use it on every 8+ ROM until someone will remove it from his ROM. It is visible in my codec selection menu on LOS15.1 but I can't test it for you since I'm not in possession of any wireless headphones. I believe that you should look for information and how it works on other phones threads too, not only here. There is possibility that Lineage doesn't support this codec itself since stock haven't supported it but I'm not sure about that since LDAC is part of AOSP unlike AptX for example where your phone needs to be certified to allow developers to include this codec in official builds.
Basically you can add any existing bluetooth audio codec to your phone's ROM. There's not any hardware requirements besides bluetooth so I believe that you should be able to use it.
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
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