I have been running the build for a while now and I haven't had any issues with fingerprint auth. If you are able to reproduce the issue, get a bug going with logcat so that dev can take a look at it.
I haven't had any issues with SafetyNet on latest build. Did it stop working when you upgraded from previous build to the new one? Or this is a new install? Along with Magisk props, I guess you also have MagiskHide enabled?I've been trying to get the safetynet work with the latest update but no progress. For Magisk props, I have selected pixel 4, 4a with android 11 even oneplus 5 with android 10, safetynet fails repeatedly.
Does anyone have any idea of what is going wrong?
I think because of safetynet fail, I can't make wireless NFC payments in stores.
You are missing one important step there. MagiskHide Props module is required to fake the device signatures. You need to also go into Magisk settings and enable MagiskHide (this is not a separate module). This setting hides magisk from Google Play Services (and can be used to hide it from Banking apps and such).No this is my first install with the latest build. I did exactly as mentioned in previous posts.
Install MagiskHide props from Magisk modules, then use termux to go into props, select fingerprint, oneplus 5/ pixel / etc, do reboot and check on Magisk app for Safetynet. It gives me attestation failed, same goes for any other safetynet app checker from google playstore.
Do I have to mess around with MagiskHide props settings too? Like boot stages, use vendor fingerprint for treble or edit props values etc?
So just to give a brief idea of my installation setup: linearOS18.1 nightly from server, Magisk 23 zip file and Nikiapps basic version. I am installing all of these with factory reset option in the twrp 2.3.5 version.
Wow thanks alot. That did it. I can't believe I missed this.You are missing one important step there. MagiskHide Props module is required to fake the device signatures. You need to also go into Magisk settings and enable MagiskHide (this is not a separate module). This setting hides magisk from Google Play Services (and can be used to hide it from Banking apps and such).
Does you Play Store now claims to be certified on the device? That may be the issue but should have gone away with clearing the data and reboot.
Unfortunately, by the time I had noticed your reply, I had reinstalled the build from the 8th of June.
I solved it by doing an another clean install with pixel v11 selected. It's working flawlessly. ThanksDoes you Play Store now claims to be certified on the device? That may be the issue but should have gone away with clearing the data and reboot.
Regardless for Netflix, you can always sideload the apk from trusted site like apkmirror.
That's weird. I just tested it on latest build (06/21) and it seems to be working fine on my end with GCam. Maybe ask in the GCam thread if anyone has similar issue there.
The only major thing broken is Wifi Display (which is used to mirror your phone screens to external displays). If that is a deal breaker to you, should probably stay on OOS. But apart from that everything else works just fine.
I don't know what Amazon fire stick uses in general. Is this cast button in Youtube or Netflix or Hulu application? If so that's using Google's API and should work on LOS. If this is something custom only between Prime Videos and Fire Stick YMMV.
Ok I found a solution, I don't know if it's realy clean, but I will tell you what I have done, first I tried to wipe cahce and Dalvik cache, no success. After, I tried to uninstall Magisk from TWRP, no success. I tried to reinstall Magisk from TWRP, no success. I tried to applicate the new LineageOS update once again, no success. And so my last solution was to tried to install "MindTheGapps" over the "NikGapps" that I install before and then ... MIRACLE that's work.
Now my question : It's good to have the twice Gapps installed,The NikGapps and the MindTheGapps?
And if not, how to uninstall NikGapps?
I don't know if you figured it out but as you see the AOD option is not visible in the menu.
Locking BL on LineageOS gives you no benefit except that the boot message disappears. The problem of SafetyNet remains.They seem to be detecting unlocked bootloader. Although some effort has been made with Magisk modules to circumvent this it seems like they're unsuccessful.
Have you tried relocking your bootloader as detailed in past posts since you don't have Magisk? Even if you did I think safety net may not pass and thereby loosing access to some other apps like GPay but your current unlock detecting apps might work.
For navigation button LED switch you can use the script from my earlier post. I have it set up to run at boot.Greetings maintainers and contributors. Great work
It's been a day into 20210705 build with MindTheGapps, Magisk 23, DotFix and GCam. Things seem to be stable right now but its too early to comment about finer details.
I would like to ask suggestions for the replacements of couple of minor tweaks which were available on OOS like,
I couldn't find settings for those on LOS is there a magisk module?
- Navigation button(HW) LED switch.
- Quick Settings mobile data sim selection.
- Safetynet does not pass. Magisk hide & MagiskHide Props Config help here.
- Wireless display does not work
- Relocking bootloader https://forum.xda-developers.com/t/...s-18-1-for-oneplus-5-5t.4173997/post-84770085 (thanks for @Eric_Lev ) (not suggested though)
/* * Your warranty is now void. * * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about features included in this ROM * before flashing it! YOU are choosing to make these modifications, and if * you point the finger at me for messing up your device, I will laugh at you. */
Today after my cheeseburger was connected to the charger for hours and did not charge at all I discovered this message "Plugged in, can't charge at the moment":View attachment 5278115
I'm on 18.1 for a few days now. Never saw such a message before. I rebooted the phone whithout disconnecting the charger and now it Dash-charged nicely. That is why I think the cause of this strange behaviour is in the OS.
Issue was caused by CAF change in kernel a while back.Same here. Happened three times since I'm on 18.1. In all three occurences I plugged in the charger directly after I had a usb audio dac connected while using the usb audio player pro app. I use this dac and app regularly and normally the phone charges fine afterwards, so not sure if there is any relation.
For the rest very happy with 18.1!