DirtyUnicorns 11.7.2 UNOFFICIAL
I just finnished compiling this morning. I used Magisk to root . Gapps i have are old so i havent tested them completely store works youtube doesnt no browser downloaded chrome it works to play music and videos. The camera, wifi, usb, headphones work bluetooth will pair but will not receive files. Battery life is lacking. I havent tested much as i just finished compiling this morning . its a wip so flash at own risk.
11/22/2018
https://www.androidfilehost.com/?fid=11410963190603855908
Tried it.
Joker1716 said:
DirtyUnicorns 11.7.2 UNOFFICIAL
I just finnished compiling this morning. I used Magisk to root . Gapps i have are old so i havent tested them completely store works youtube doesnt no browser downloaded chrome it works to play music and videos. The camera, wifi, usb, headphones work bluetooth will pair but will not receive files. Battery life is lacking. I havent tested much as i just finished compiling this morning . its a wip so flash at own risk.
11/22/2018
https://www.androidfilehost.com/?fid=11410963190603855908
Click to expand...
Click to collapse
Booted up, no SIM recognition, Bomb bootanimation though! Keep working man.
Awesome Rom
I just installed the nougat for galaxy nexus. Whoa . . . .couldn't believe how awesome this rom is . Love to have it on my daily driver s3 att.
GREAT WORK !!!!
Hi there - I guess this might be a question for @electrikjesus but the IPTS Surface Pro stable build (11.10) doesn't appear to have the Android-x86 options in Settings. This means a number of ARM games don't run. I can install the stable 11.9 build on a Surface Pro (2017) and the Android-x86 options are there, can be enabled and games run. However, using the firmware as per the documentation to enable touch on a Surface Pro does not work on the non-IPTS 11.9 build (presumably by design).
Is there a way to get the Android-x86 options on the IPTS stable Surface build please? Everything else is working just great (I know there are issues with cameras, mics, sleep, etc.)
I also tried the 12.6 build but couldn't get touch working, tried the old 11.6 (11.4?) Surface builds but no Play Store, etc, etc. The 11.10 works great IF I could enable the Native bridge. I have the 11.9 installed on a Dell XPS 13 and everything works super, including touch.
Thanks in advance,
Shaky
Having recently upgraded my ROM to android10 with L17.1 I was surprised to see direct audio recording of internal sound has become an issue. I'm aware from reading around that google removed the function in a8 and there are some workarounds, but they all seem to involve screen recorders.
I'm looking for a simple audio recorder to capture the internal sound without mic.
My nexus 7 flo is rooted with the magisk, twrp and unofficial lineage builds but I don't have xposed framework installed (I'm toying with adding it).
Secondly, I'm still on the factory kernal. Is there much benefit in flashing one of the newer XDA built versions? Can anyone recommend which one for L17.1?
As ever - many thanks.
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
Since the launch of Android 10 Google has developed ASHA. (Audio Streaming Hearing Aids.) For a long time this was only available on the Pixel lineup. With Android 11 developers have been able to implement this in their custom roms.
My question now is whether LineageOS 18.1 supports ASHA. If it has been added, does it work? There is no such thing listed on the wiki and nothing was posted in threads on XDA or Reddit regarding ASHA. Other custom Android 11 roms such as EvolutionX does support ASHA.
At the moment my OnePlus 6T does meet the requirements for ASHA. (Bluetooth 5.0 LE)
Hopefully one of you can answer this question. Thank you in advance.