When I try to use screen mirroring to connect to my Samsung smart TV(nu7100) I get an error "Your output device does not support HDCP. Cannot mirror. You still can mirror some apps and unprotected content to the device."
When I mirror from the settings or music app, it works, but nothing else. I have an Ulefone power 5, and a Samsung a8+, and they both work flawlessly with the same tv.
I tried on a miracast dongle on another tv, with the same error (the other phones do work on the dongle as well)
I followed the instructions from https://www.youtube.com/watch?v=1wIM67kVVL8 but no difference.
How can I get this working? Pretty basic feature...
Do you root your phone? My phone rooted and can't connect to my sony tv
Yeah, I assume you unlocked the bootloader.
It needs a hack to ignore the missing DRM keys.
Damn, yes I am rooted so bl unlocked..
Are there any hacks the community knows about that work? I had run xperifix on oero to fix the camera, which didn't work, and flashed stock pie, which fixed the camera but didn't fix the drm keys..
Kobro said:
Damn, yes I am rooted so bl unlocked..
Are there any hacks the community knows about that work? I had run xperifix on oero to fix the camera, which didn't work, and flashed stock pie, which fixed the camera but didn't fix the drm keys..
Click to expand...
Click to collapse
Did you switched to SeLinux Permissive after you installed XperiFix on Oreo?
MartinX3 said:
Did you switched to SeLinux Permissive after you installed XperiFix on Oreo?
Click to expand...
Click to collapse
I did but that did not help the camera. I don't know if it helped the drm. Should I try setting that now to see of it solves the hdcp issue?
It IS a fix if so, but I don't really think having selinux always be permissive on a rooted device seems very safe..
Kobro said:
I did but that did not help the camera. I don't know if it helped the drm. Should I try setting that now to see of it solves the hdcp issue?
It IS a fix if so, but I don't really think having selinux always be permissive on a rooted device seems very safe..
Click to expand...
Click to collapse
Did you unlock the bootloader on PIE or on OREO?
If the camera preview in OREO with permissive doesn't work, the xperifix is not active.
Did you do a custom installation with A/B, VENDOR and by choosing the magisk.zip?
MartinX3 said:
Did you unlock the bootloader on PIE or on OREO?
If the camera preview in OREO with permissive doesn't work, the xperifix is not active.
Did you do a custom installation with A/B, VENDOR and by choosing the magisk.zip?
Click to expand...
Click to collapse
Unlocked in pie, downgraded to oreo, ran xperifix exactly as you described, but it still didnt work. Then upgraded to pie again and camera was fixed but I don't know how or what did it
Kobro said:
Unlocked in pie, downgraded to oreo, ran xperifix exactly as you described, but it still didnt work. Then upgraded to pie again and camera was fixed but I don't know how or what did it
Click to expand...
Click to collapse
If you have a camerapreview in PIE then you don't need the camerafix in PIE.
And probably the xperifix won't work.
They changed the way how the DRM keys are getting removed from the TA partition.
Now less features are lost after unlocking.
MartinX3 said:
If you have a camerapreview in PIE then you don't need the camerafix in PIE.
And probably the xperifix won't work.
They changed the way how the DRM keys are getting removed from the TA partition.
Now less features are lost after unlocking.
Click to expand...
Click to collapse
Camera preview worls and no green images eother. In the settings I see rhe xreality things, and I assumed the other drm things worked too. Question is, what do I do about the HDCP issue now in pie?
Kobro said:
Camera preview worls and no green images eother. In the settings I see rhe xreality things, and I assumed the other drm things worked too. Question is, what do I do about the HDCP issue now in pie?
Click to expand...
Click to collapse
Maybe switching to a custom ROM after OEMv8 got released with some TAMA camera fixes and test it there?
If it doesn't work there, you can write a bug report and it may get fixed.
But stock. umhhhh DRM.
I kind of found a workaround. For me the reason I need to screen mirror at all is to watch videosvstores on my phone, on the big screen. So I found apps in the play store that can stream without hdcp. (Allcast etc) So, it's not full mirroring, but at least I can cast my videos, that'll have to do for now.
Related
I have an H8266 on .84 firmware no updates available.
Faruk.ErdaL said:
I have an H8266 on .84 firmware no updates available.
Click to expand...
Click to collapse
Xpericheck.com
MartinX3 said:
Xpericheck.com
Click to expand...
Click to collapse
the title... anyways Ive got the xperifix but still the camera preview is black also video recording doesnt work properly. what do you recommend? installing aosp rom would fix the issues?
Faruk.ErdaL said:
the title... anyways Ive got the xperifix but still the camera preview is black also video recording doesnt work properly. what do you recommend? installing aosp rom would fix the issues?
Click to expand...
Click to collapse
Oh.
I did Only read your text.
Oreo + xperifix needs the permissive.zip buried in the twrp thread
I have unlocked my bootloader on CE .84 firmware, and couldn't get camera preview working in any version, how do I do that permissive. Zip thing also I couldn't find about it on the thread and I seriously need help, I dont care about security updates I just want the phone properly working with its camera.
Faruk.ErdaL said:
I have unlocked my bootloader on CE .84 firmware, and couldn't get camera preview working in any version, how do I do that permissive. Zip thing also I couldn't find about it on the thread and I seriously need help, I dont care about security updates I just want the phone properly working with its camera.
Click to expand...
Click to collapse
If you use the PIE firmware .126 together with magisk and the existenze ROM, you get a working camera.
If you need the noise reduction, too, then you need, together with OREO, Magisk and the Xperifix, this permissive.zip.
https://github.com/Jman420/magisk_selinux_manager
Just download the repo as zip file, rename.it correct and install it in the magisk manager app as module.
existenze rom doesnt work either black preview also broken internal storage so it cant save photos
Faruk.ErdaL said:
existenze rom doesnt work either black preview also broken internal storage so it cant save photos
Click to expand...
Click to collapse
You need the vbmeta parameters mentioned in the first page of the TWRP topic
Or the camera will stay black.
It need to be repeated email you use flashtool, Emma or newflasher.
Did it broke after wiping in TWRP?
you need advanced wipe and wipe data, internal storage, dalvik.
Not only the normal wipe.
And you need to boot the .126 one time without Existenze, to correctly install the baseband drivers.
PS: Existence is only compatible with .126
MartinX3 said:
You need the vbmeta parameters mentioned in the first page of the TWRP topic
Or the camera will stay black.
It need to be repeated email you use flashtool, Emma or newflasher.
Did it broke after wiping in TWRP?
you need advanced wipe and wipe data, internal storage, dalvik.
Not only the normal wipe.
And you need to boot the .126 one time without Existenze, to correctly install the baseband drivers.
PS: Existence is only compatible with .126
Click to expand...
Click to collapse
holy fukin **** it worked on oreo, thank u so much all i gotta do is waiting for xperifix to be updated
MartinX3 said:
If you use the PIE firmware .126 together with magisk and the existenze ROM, you get a working camera.
If you need the noise reduction, too, then you need, together with OREO, Magisk and the Xperifix, this permissive.zip.
https://github.com/Jman420/magisk_selinux_manager
Just download the repo as zip file, rename.it correct and install it in the magisk manager app as module.
Click to expand...
Click to collapse
is noise reduction the only thing missing in pie? 4k hdr video and hdr photos work on pie?
Faruk.ErdaL said:
is noise reduction the only thing missing in pie? 4k hdr video and hdr photos work on pie?
Click to expand...
Click to collapse
They seem to work at my device.
Faruk.ErdaL said:
existenze rom doesnt work either black preview also broken internal storage so it cant save photos
Click to expand...
Click to collapse
Nope
There is no broken internal storage, this is TWRP encryption.
Wipe internal sd in recovery will solve your issue.
Envoyé de mon H8266 en utilisant Tapatalk
Hey!
I have always rooted my android phones, but after flashing last update and bricking my OnePlus 3T (and since I haven't used anything that needs root lately) I decided to revert everything to stock and lock my bootloader (no problem).
The problem is that after I fixed everything and installed all of my apps I noticed that I am failing safetynet . A little bit of testing and I realized that I set SELinux to permissive when my phone was still rooted....
So now I have a locked stock phone with permissive SELinux, is there any way to change this without having to unlock the phone (and deleting everything...)? Maybe if I could temporarily install SU binaries? Is that possible? (Running OxygenOS 9.0.4 .)
Thanks!
If you need root you have to unlock the bootloader... I think there was a locked bootloader hack to install root on old OxygenOS, but I doubt that works now.
But, are you sure about SELinux? If you've returned everything to stock it should be enforcing by default.
Didgeridoohan said:
If you've returned everything to stock it should be enforcing by default.
Click to expand...
Click to collapse
You are right: it SHOULD be that way. Sadly, this is the third report of selinux is permissive after crossing the 5.0.x to 9.0.x barrier - at least; two more can be found at the official los thread.
This proceduere has been reported to fix this (havn't tried myself, since I havn't faced the issue): https://forum.xda-developers.com/showpost.php?p=79816636&postcount=2670
Alright, I guess I'll just have to unlock the bootloader and fix that. Thanks for the help!
Update: I did something similar to the guide nvertigo67 sent:
1.Used the unbrick tool.
2.Sideloaded 5.0.8.
3.OTA:ed to 9.0.3.
(Haven't followed the other steps since I do not want a custom rom and don't need to flash any nandroid backup.)
Now, everything is completely stock but SELinux is still permissive and I am still uncertified... about to go crazy :crying:.
Yuvve said:
Update: I did something similar to the guide nvertigo67 sent:
1.Used the unbrick tool.
2.Sideloaded 5.0.8.
3.OTA:ed to 9.0.3.
(Haven't followed the other steps since I do not want a custom rom and don't need to flash any nandroid backup.)
Now, everything is completely stock but SELinux is still permissive and I am still uncertified... about to go crazy :crying:.
Click to expand...
Click to collapse
If your 3 steps doesn't work, perhaps sticking to the guide and only skipping to flash los and gapps is a solution. l could imagine the exact order and the reboots may play in. Otherwise I've no clue why it has worked for @zezinho7 but not for you.
Has 5.0.8 been enforcing before the ota to 9.0.3? If so, you can always use my modded fw to work around until you've found the solution.
hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.
You didnt do it right. I would suggest youtube the magisk rooting process
Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead
Cristian-104 said:
hi to all, has anyone managed to root on galaxy s10 with the July security patch update? I tried the same method with magisk but there is nothing to do, every time it gives me a different error. In the last attempt I made during the boot phase, in the upper left corner, it was written: "only official released binaries are allowed to be flashed" or something like that.
Click to expand...
Click to collapse
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.
TheUndertaker21 said:
Same tried to root it
I, was able to get it to root but the camera still makes my device rebooted
And tried to do it with ap file by changing recovery inside to the patched twrp that didn't work just booted into stock recovery instead
Click to expand...
Click to collapse
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).
Jannomag said:
TWRP ≠ Root.
With the latest patch the camera crashes if TWRP is flashed. With stock recovery everything should work fine.
I'm on Exynos ASG8 without any issues, except slow wifi in apps (not browser).
Click to expand...
Click to collapse
OH that's a known issue then?
I need my custom rom and twrp lol
TheUndertaker21 said:
OH that's a known issue then?
I need my custom rom and twrp lol
Click to expand...
Click to collapse
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)
Jannomag said:
It is...nearly everytime Samsung throws out a new security patch TWRP is crashing the camera.
This is what I found out after having the same issue. I don't know if there's a new version for the latest patch.
Aren't the custom roms based on One UI? Shouldn't the stock recovery still work? (I really don't know)
Click to expand...
Click to collapse
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon
TheUndertaker21 said:
TWRP is good to have if something goes wrong.
I can have custom rom without twrp but that's not the whole of it.
Hope it gets patch soon
Click to expand...
Click to collapse
It's easy to flash it, even without running system.
Hi everyone, I'm still ASD4 and basically haven't update since because everything is a hassle these days. Now I thought maybe it's time to update, but keep reading things like this and camera, wifi bootloops problems etc.
Are these issues a real thing? or just some individual cases where it happens?
It's real like a $2 dollar bill.
bininga59 said:
I have already tried EVERYTHING, in download mode I can not get the> Prenormal <to> Check ing <. The option of OEM lockdown is there, has always been there.
Click to expand...
Click to collapse
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.
FlatOutRU said:
You have to turn off all data ( wi-fi and 4g) and manually set the date to 7 days back.
Click to expand...
Click to collapse
I have already made. As I said, I unlock the bootloader and lock (developer option or download mode) as I want,> prenormal <does not go away.
Did a root today without issues on my S10 with ASG8
ru_dimka said:
Did a root today without issues on my S10 with ASG8
Click to expand...
Click to collapse
everything works? twrp installed? magisk etc.?
chieco said:
everything works? twrp installed? magisk etc.?
Click to expand...
Click to collapse
There is no twrp for ASG8. Others stuff works well!
ru_dimka said:
There is no twrp for ASG8. Others stuff works well!
Click to expand...
Click to collapse
I'm always afraid that I install something or make a small change and end up in a bootloop... I wish twrp and everythign work just fine like before and I could make a backup after installing a rom and doing the most basic stuff.
Since this is the first post that comes on Google for "only official released binaries" "s10".
I had this problem again and again, and it seems that it was caused by one of the reboot not being done with the correct timing with the 3 buttons.
The thing I was missing was after flashing the patched AP files (and the other files).
When you restart, keep the 3 buttons pressed until you see the blue screen and then release only power (keep vol up + bixby) to get into reset mode.
I think I didn't keep them pressed long enough.
If the device restarts, keep pressing the 3 buttons (never let it restart without pressing them).
Once the factory wipe has been done: Restart with the 3 buttons, and keep them pressed until 1 to 2 sec after the screen that asks you to press the power button to continue.
Which custom rom is best for redmi note 8 in ANDROID 11
Opinions are different from person to person. You should do a research on this subject then choose anything to your taste. Easier this way than asking someone. In this way you'll gain knowledge and you'll be able to provide tips and advises to others.
Anyway, you should stay away from the latest update to A11 from Xiaomi!!! The official update is garbage!!! I regret so much doing this step... lost some useful and basic functions. Looks like their devs are stupid really... or just hate their customers.
Just try whatever you thing is ok for you.
MadK9 said:
Opinions are different from person to person. You should do a research on this subject then choose anything to your taste. Easier this way than asking someone. In this way you'll gain knowledge and you'll be able to provide tips and advises to others.
Anyway, you should stay away from the latest update to A11 from Xiaomi!!! The official update is garbage!!! I regret so much doing this step... lost some useful and basic functions. Looks like their devs are stupid really... or just hate their customers.
Just try whatever you thing is ok for you.
Click to expand...
Click to collapse
You are absolutely right. Android 11 update is like a diseaster
rafat.mym said:
You are absolutely right. Android 11 update is like a diseaster
Click to expand...
Click to collapse
whats the problem? mine works fine and much faster
jjsan said:
whats the problem? mine works fine and much faster
Click to expand...
Click to collapse
There must be something that makes your device smooth... maybe rom variant? Locked bootloader??
Share us more details please.
MadK9 said:
There must be something that makes your device smooth... maybe rom variant? Locked bootloader??
Share us more details please.
Click to expand...
Click to collapse
Unlocked bootlader, rooted (magisk for payment and adaway)
Rom variant is
Miui 12.0.2 RCXEUXM
Full wipe after upading to 11
Thanx.
Well, I also have an unlocked bootloader, but no Magisk and EEA Rom... but did not tried factory reset after update.
I also tried to flash Magisk but had issues with bootloop when I patched boot image and I gave up...
MadK9 said:
Thanx.
Well, I also have an unlocked bootloader, but no Magisk and EEA Rom... but did not tried factory reset after update.
I also tried to flash Magisk but had issues with bootloop when I patched boot image and I gave up...
Click to expand...
Click to collapse
ive installed magisk via twrp (renaming .apk to .zip and flashing)
i've read many posts about wiping data after upgrade
jjsan said:
Unlocked bootlader, rooted (magisk for payment and adaway)
Rom variant is
Miui 12.0.2 RCXEUXM
Full wipe after upading to 11
Click to expand...
Click to collapse
My firend, how did you fix the payment (with magisk)?
Jendrooo said:
My firend, how did you fix the payment (with magisk)?
Click to expand...
Click to collapse
5 days ago something happened and its not working for now. waiting for solution. you can search for cts profile here in forum.
Jendrooo said:
My firend, how did you fix the payment (with magisk)?
Click to expand...
Click to collapse
Android Repository
MagiskHide Props Config v6.0.2-v132 (72) ⚡Magisk Module ⚡Change your device's fingerprint, to pass SafetyNet's CTS Profile check. Set/reset MagiskHide sensitive prop values. Change any prop values easily, and set your own custom props. ⚡️GitHub Repository ⚙Changelog: - Fix problems when trying...
t.me
Remember : A11 sux !
loopypalm said:
Android Repository
MagiskHide Props Config v6.0.2-v132 (72) ⚡Magisk Module ⚡Change your device's fingerprint, to pass SafetyNet's CTS Profile check. Set/reset MagiskHide sensitive prop values. Change any prop values easily, and set your own custom props. ⚡️GitHub Repository ⚙Changelog: - Fix problems when trying...
t.me
Remember : A11 sux !
Click to expand...
Click to collapse
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?
Jendrooo said:
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?
Click to expand...
Click to collapse
payment is not possible even on android 10 now.
i like 11 more than 10
Jendrooo said:
1. In your opinion it is better to install V12.0.4.0 with android 10 or stay on V12.0.2.0 with android 11?
2. After installing MagiskHide Props Config v6.0.2-v132 (72), will I have trouble adding a credit card to gpay? (on android 11)?
Click to expand...
Click to collapse
1-none , -----> custom rom
2-IDK about payment things
jjsan said:
ive installed magisk via twrp (renaming .apk to .zip and flashing)
i've read many posts about wiping data after upgrade
Click to expand...
Click to collapse
Managed to install Magisk again (older version...), gain root and activated OTA survival on OrangeFox Recovery. So far, no issues but still afraid to try A11 again...
MadK9 said:
Managed to install Magisk again (older version...), gain root and activated OTA survival on OrangeFox Recovery. So far, no issues but still afraid to try A11 again...
Click to expand...
Click to collapse
what were your problems?
best thing for me is setting phone to airplane mode and it lets bt on if was connected before.
and really nice and smooth system
Well, there were several bugs on my device which I was unable to sort them out and decided to go back to 12.0.4.0...
Most annoying one was the impossibility to share a file from file manager by swiping up to a file... A message came on screen telling me there is no app to handle the action on my personal profile or something like that... Whaaat?
Another bug was the 3 fingers screenshot option... Not there... Just not working... Or dynamic icons... This function also was not available anymore...
I had no patience digging for bugs, was pissed and flash the goddamn device with the previous working version of android... Was so angry that I forgot to back up my data and lost all my personal files!!!
But of course, I did not factory reset my device after A11 update... This move, should not exist!!! Why this option is never applied on iphones??? Of course they're not perfect but update after update and never, ever had issues with the device and never had to factory reset it after a major update.... Jesus Christ, this android....
well. i understand that.
3 fingers screenshot can be activated from notifications.
funny thing is possibility to activate new notification centre. its not there. unless you look for it in search. funny thing - your phone has to be in english
i was android developer for 3 years and I like this system just because these possibilities.
im rooted. i can edit hosts file and make adblock perfect and simple.
but for normal people just for using phone there is iPhone. its simple and working.
or also samsung devices are quite good but pricey
About 3 fingers screenshoot: The option was enabled in my device, so even if it was active, the function did not worked!
start camera from lock screen was moved to double volume up but also not working. ist still beta
Hey,
I got my Pixel 7 last week and installed Graphene OS on it, however after some days I noticed it behaved very strange.
No buttons on the phone worked anymore, neither the power nor the volume buttons. After I did a full reboot the buttons worked again, but then the fingerprint scanner is not available anymore?!
As i very much like to have both, the buttons and the finger print, working I did a factory reset and installed LineageOS. But now I have the same beavior again after 2 days with the new ROM.
Did anyone experiences something similar already? Do you think this is a hardware issue? Can I still get a replacement if I already unlocked the bootloader and tinkered around with the OS on the phone?
Sounds like a hardware issue. Although its a bit strange that it would affect either the fingerprint sensor or the buttons. Could you describe what goes on with the fingerprint sensor in more detail?
Well the fingerprint hardware is simply not available, conpletely gone from the settings, doesn't show up on the lockscreen, like it doesn't even exist on the device.
If I then reboot the hardware is available again but the whole OS is super buggy, the buttons don't work and the phone will soft reboot after a few minutes.
Before you call it a hardware issue why not flash back to stock and verify. Most likely a rom issue and I'm sure the other rom pulls from the lineage source, most do. Would also explain the issue persisting on two different roms.
Yeah I will try it but the Android flash tool failed on me on 2 seperate machines. So now I habe to do it manually with adb it seems.
But even if the Stock ROM works, it's still weird, as nobody else reporting on this.
elba96 said:
Yeah I will try it but the Android flash tool failed on me on 2 seperate machines. So now I habe to do it manually with adb it seems.
But even if the Stock ROM works, it's still weird, as nobody else reporting on this.
Click to expand...
Click to collapse
I seem to recall a problem with fingerprint disappearing from screen and settings like you described. I think it was in the Pixel 6 forums months ago. I don't remember any details.
It's not unusual to lose certain functions with a custom ROM but the button problem is definitely unusual. Whether it's software or hardware, if you can reproduce at least one of these problems with stock Android then I think you have your answer. And as long as factory firmware is installed, bootloader is locked and you factory reset it, you should be ok returning the phone for repair or replacement.
Thanks for the answer!
Today I finally had the time to flash a factory image. After rooting and restoring all my apps the issue reappeared after about 20 min. on the stock rom it was even more severe. Now I uninstalled magisk and flashed the stock init_boot.img file and until now it seems fine.
Can the patched boot image cause the problems described above, or even an unlocked bootloader?
elba96 said:
Can the patched boot image cause the problems described above, or even an unlocked bootloader?
Click to expand...
Click to collapse
If these problems are caused by bootloader unlocking or rooting stock Android I think the same would've happened to other people by now and it would have been mentioned.
Regarding the bootloader, was GrapheneOS fully erased? In particular its verified boot key.
GrapheneOS CLI install guide
Command-line installation instructions for GrapheneOS, a security and privacy focused mobile OS with Android app compatibility.
grapheneos.org
If that's not it, or something similar leftover from Lineage, I think you should forget any modifications long enough to reproduce your problems in the phone's factory state. Just run flash-all.bat (or bash equivalent) and let it wipe, lock the bootloader, install updates and use the phone. Time consuming, I know. But if there are hardware issues one or both problems may show up again and it's less of a mystery.
manjaroid said:
Regarding the bootloader, was GrapheneOS fully erased? In particular its verified boot key.
Click to expand...
Click to collapse
Thanks for the notice, I forgot about this!
So far the stock rom without root performs ok, no problems. It just sucks to not have all the customizations I'm used to for the last 10 years...
Maybe try not restoring any apps and see if it still persists.
manjaroid said:
If these problems are caused by bootloader unlocking or rooting stock Android I think the same would've happened to other people by now and it would have been mentioned.
Click to expand...
Click to collapse
@elba96
Maybe it's too soon to dismiss Magisk patching as the problem. You might try Magisk stable 25.2 or canary 25206 if you've been patching with one of the newer 26.x releases.
I'm starting to suspect my patched boot image may be the cause of a new problem on a Pixel 5. Either that or it's a new Android bug.
My problem is similar to one of yours: a lost function combined with a disappearing setting. SmartLock hasn't worked right since the April update a couple days ago. When I check its settings all three SmartLock options are gone. Rebooting brings them back and I'm able to get SmartLock working again. The problem seems to repeat when the phone goes idle and locks down.
By now I'm pretty sure it was the patched boot image. Until now (2 days) the stock ROM doesn't show any bugs.
And now that you say it. I used Magisk 26 for the patching as it rolled out right when I was setting up my phone. Should have stayed with v25.x it seems.
I'll give it 1 or 2 days more just to be sure and then I'll try it with Magisk v25.x again.