yashsingh1/xdaforums huggingface dataset:
[Magisk] Displax:
Pixel`s update:

Pixel 3=google/blueline/blueline:11/RQ3A.211001.001/7641976:user/release-keys__2021-10-01
Pixel 3 XL=google/crosshatch/crosshatch:11/RQ3A.211001.001/7641976:user/release-keys__2021-10-01
Pixel 3a=google/sargo/sargo:11/RQ3A.211001.001/7641976:user/release-keys__2021-10-01
Pixel 3a XL=google/bonito/bonito:11/RQ3A.211001.001/7641976:user/release-keys__2021-10-01
Pixel 4=google/flame/flame:11/RQ3A.211001.001/7641976:user/release-keys__2021-10-01
Pixel 4 XL=google/coral/coral:11/RQ3A.211001.001/7641976:user/release-keys__2021-10-01
Pixel 4a=google/sunfish/sunfish:11/RQ3A.211001.001/7641976:user/release-keys__2021-10-01
Pixel 4a (5G)=google/bramble/bramble:11/RQ3A.211001.001/7641976:user/release-keys__2021-10-01
Pixel 5=google/redfin/redfin:11/RQ3A.211001.001/7641976:user/release-keys__2021-10-01
Pixel 5a=google/barbet/barbet:11/RD2A.211001.002/7644766:user/release-keys__2021-10-01
[Magisk] xunholyx:
There was someone asking on the Pixel 5 Q&A for the current fingerprint for Android 12 to use to get Call Screening with this module saying he couldn't find it (he's used it before for this). I figured you would already have it, but in case you don't:

google/redfin/redfin:12/SPB5.210812.002/7671067:user/release-keys
[Magisk] nicesoni_ash:
Hi,

I have a K20 Pro (Indian) version, I just noticed recently that my cts profile is failing to pass so I began to find solutions.

First I updated Universal safetynet fix module, it didn't fix it so I tried this module, I applied K20 Pro(Indian) fingerprints but that didn't fix it either.

My playstore was certified before but after clearing data and updating fingerprints, it's now changed to not certified.

Can someone suggest what more I can do to fix this?

Thank you.
[Magisk] Didgeridoohan:
I've replied to your post in the main Magisk thread. Please do not double post...
[Magisk] Coldtrain6989XD:
Hey guys I have a really bad issue. My pixel 4a jailbroken with magisk, with a switched out fingerprint from 4a to 3a with universal safety fixed latest and latest magisk props config is not pass safety net.
[Magisk] Didgeridoohan:
If you're using a stock ROM you don't need to change the device fingerprint, and if you're using a custom ROM you should ideally use the fingerprint for your own device.

But, you're failing both basic integrity and CTS profile, so my first guess would be that you need to enable MagiskHide (or toggle it off and on again if it is enabled)...

More: https://www.didgeridoohan.com/magisk/MagiskHide#hn_Both_CTS_profile_and_Basic_integrity_fails
[Magisk] Coldtrain6989XD:
It worked for some reason it was off magick hide.
[Magisk] Didgeridoohan:
There's nothing in that log about MagiskHide being active...
[Magisk] Coldtrain6989XD:
I just turned it back on
[Magisk] MarceloASG:
Samsung Galaxy J8 SM-J810M (10)

samsung/j8y18lteub/j8y18lte:10/QP1A.190711.020/J810MUBU3CUF1:user/release-keys

Security patch June 1, 2021
[Magisk] LNS:
Anyone knows where I can download the discontinued MagiskHide from?

View attachment 5431283
[Magisk] zgfg:
Which Magisk do you have installed?

If you moved to Magisk Alpha, there is no MagiskHide anymore - it's DenyList instead
[Magisk] LNS:
I did move to alpha, but only after not finding magiskhide in the v23 module repo. (Did I miss someting?) Magiskhide props confiig doesn't detect detect DenyList, does, it? I tried moving back to v23 but had some trouble I couldn't get root to work, thank god it worked on alpha again :p cause I got no backup.

....

...omg, tell me it was in settings like DenyList..

I'll try get v23 to work again

edit: v23 = sorry I meant the normal/stable magisk
[Magisk] zgfg:
MagiskHide is option in Magisk (Stable, Canary) - it was NEVER a module or something

MHPC does work with DenyList from Magisk Alpha

If you are not familiar with Magisk Alpha, pls search for Alpha and read in XDA Magisk General thread

In short, open Magisk Alpha settings, scroll and find Zygisk, enable and reboot

Then do similarly, enable DenyList (Enforce option)

Then open Configure DenyList and enable GMS as you usually had with Magisk Stable/Canary (Search, enable System and OS apps, Google Play Services...)

Reboot, then check SafetyNet

From the command line:

magisk --denylist ls
[Magisk] LNS:
Dang, I used magisk years ago a bit and had the notion it was a module. I will do look into the general thread. (DenyList however doesn't show any google services except AR, the rest is only user installed apps.) Anyhow, jumping onto magisk general, thanks!
[Magisk] zgfg:
You had to enable Show System apps and Show OS Apps.

Then search for Google Play Services.

Then manually enable its one or two processes (the same as AUTOMATICALLY get enabled for Magisk Hide in the good old Magisk Stable).

Also, Magisk Alpha has no more Modules Repo

All in all, who does not have specific needs for Alpha and Zygisk, better stay with the old Magisk Canary/Stable.

TJW will sooner or later push the new Magisk also with Zygisk and DenyList and without Modules Repo. Till then, enjoy the old Magisk
[Magisk] LNS:
That worked a charm(curtana)! And I just(so to speak till I managed to correctly quote you on my edit from the phone) saw that the post is just over a year ago.
[Magisk] Vuska:
Hi... my samsung s10+ G9750 has failed CTS too.. using Stock Rom

any video or step by step after using this module ?

I'm still confused about what to do.. 🙏
[Magisk] ipdev:
Hi. :)

Not sure if there is a video or step by step guide..

The link to the the documentation for this module is in the OP. ;)

MagiskHide Props Config - Documentation - GitHub - Link

I know the documentation can be a little overwhelming to start with. 🙃

You can skim through most of it (slow down on sections that are important).

Since it is a newer device I would recommend reading these two sections.

MHPC Documentation - Force BASIC key attestation - GitHub - Link

MHPC Documentation - Set/reset MagiskHide Sensitive props - GitHub - Link

Once thing to note.

When you run the props command, you will see this option.

4 - Edit MagiskHide props (active)

Make sure the sensitive props are actually active.

Select option 4 and double check.

The sensitive props that show (enabled, not active) will not be adjusted on boot.

Cheers. :cowboy:
[Magisk] savage44:
Hi,

Why can't I set fingerprint to HD1903 (OnePlus 7T)? Whenever I try to set this fingerprint it setting HD1905 for me :/
[Magisk] Didgeridoohan:
No idea... I can't reproduce. How about providing the module logs?
[Magisk] savage44:
Hey, thanks for your reply!

I sent you logs via pm message :) Sorry for bothering.
[Magisk] Didgeridoohan:
Everything checks out with the fingerprint you've set with the model, it's the EU one. The only place where the HD1905 prop is set is in the default values for the ROM.

You should check with your ROM developer... They're the ones that have set the model prop to HD1905.
[Magisk] savage44:
Oh well. I'm using Lineage OS 18.1, the official ones. So nothing to do with MHPC. Thank you :)
[Magisk] totyax:
Anyone for this?
[Magisk] Didgeridoohan:
I doubt it...

And I've no insight into why you might be experiencing authentication problems.
[Magisk] totyax:
Safetynet passed with this module (and Lenovo Note fingerprint), but with the newest Lineage OS, doesn't need it, because safetynet passed without it. But with all custom OS the problem, in the apps (banks, keepass) fingerprint doesn't work.

As I read the forum, this problem for other peoples.

Example see:

#1

"Karatep will pass safetynet by default (karate will never, as all the build.fingerprints fail on custom)"

#2

"

K6 doesn't have any certified fingerprints. So it won't pass

Don't discuss about fingerprints which isn't related to karate devices."

(remark: "Karate" is my device)

Thank you for your attention!
[Magisk] Didgeridoohan:
It sounds to me like you are connecting the device fingerprint (build fingerprint) for the ROM to the fingerprint authentication on your device. Don't do that... They have nothing to do with each other.

If no custom ROMs for your device can use fingerprint authentication in apps, that's an issue with the ROM and you can't fix that with simple prop changes.
[Magisk] totyax:
I think I understand about, thank you for the answer!
[Magisk] galen11:
hi,

i can not bypass cts check by using the following fp,

basicIntegrity passed.

how can i troubleshoot it?

thanks.

ginkgo:/ # getprop| grep finger

[ro.bootimage.build.fingerprint]: [google/redfin/redfin:11/RQ3A.210805.001.A1/7474174:user/release-keys]

[ro.build.fingerprint]: [google/redfin/redfin:11/RQ3A.210805.001.A1/7474174:user/release-keys]

[ro.build.version.preview_sdk_fingerprint]: [REL]

[ro.odm.build.fingerprint]: [google/redfin/redfin:11/RQ3A.210805.001.A1/7474174:user/release-keys]

[ro.product.build.fingerprint]: [google/redfin/redfin:11/RQ3A.210805.001.A1/7474174:user/release-keys]

[ro.system.build.fingerprint]: [google/redfin/redfin:11/RQ3A.210805.001.A1/7474174:user/release-keys]

[ro.system_ext.build.fingerprint]: [google/redfin/redfin:11/RQ3A.210805.001.A1/7474174:user/release-keys]

[ro.vendor.build.fingerprint]: [google/redfin/redfin:11/RQ3A.210805.001.A1/7474174:user/release-keys]

ginkgo:/ # getprop| grep securi

[ro.build.version.security_patch]: [2021-08-05]

[ro.vendor.build.security_patch]: [2021-02-01]

[security.perf_harden]: [1]

ginkgo:/ #
[Magisk] vijaykanth:
Hope to see this device on the printslist soon!

Samsung Galaxy S20 FE (SM-G780F)

Android 11 (OneUI 3.1)

Google Play Update: 1 August 2021

Android Security Patch: 1 August 2021

samsung/r8sxx/r8s:11/RP1A.200720.012/G780FXXU5CUH1:user/release-keys

Thank you! :)
[Magisk] Didgeridoohan:
@galen11 That looks like the Pixel 5 fingerprint included in the module prints list. It's confirmed certified so should pass CTS just fine. But of course, there are many other factors that come into play:

https://github.com/Magisk-Modules-R...DME.md#i-still-cant-pass-the-ctsprofile-check
[Magisk] Flamefire:
Does anyone have an updated Pixel 5 fingerprint for the October 2021 security patch level?
[Magisk] Didgeridoohan:
It was posted here, and it is confirmed certified. I'll eventually get around to updating the list...
[Magisk] Displax:
Pixel | Android 12

Pixel 3=google/blueline/blueline:12/SP1A.210812.015/7679548:user/release-keys__2021-10-05
Pixel 3 XL=google/crosshatch/crosshatch:12/SP1A.210812.015/7679548:user/release-keys__2021-10-05
Pixel 3a=google/sargo/sargo:12/SP1A.210812.015/7679548:user/release-keys__2021-10-05
Pixel 3a XL=google/bonito/bonito:12/SP1A.210812.015/7679548:user/release-keys__2021-10-05
Pixel 4=google/flame/flame:12/SP1A.210812.015/7679548:user/release-keys__2021-10-05
Pixel 4 XL=google/coral/coral:12/SP1A.210812.015/7679548:user/release-keys__2021-10-05
Pixel 4a=google/sunfish/sunfish:12/SP1A.210812.015/7679548:user/release-keys__2021-10-05
Pixel 4a (5G)=google/bramble/bramble:12/SP1A.210812.015/7679548:user/release-keys__2021-10-05
Pixel 5=google/redfin/redfin:12/SP1A.210812.015/7679548:user/release-keys__2021-10-05
Pixel 5a=google/barbet/barbet:12/SP1A.210812.015/7679548:user/release-keys__2021-10-05
[Magisk] r29:
dumb question - I just updated to android 12 SP1A.210812.015 on pixel 4 xl I assume magiskhide wont work to pass ctsprofile right?

My is failing
[Magisk] Didgeridoohan:
Shouldn't be a problem... Have you tried toggling MagiskHide off and on again?
[Magisk] r29:
yup tried everything - universal safetynet fix worked actually

not sure why force basic key was not work i tried couple device builds. very odd
[Magisk] Didgeridoohan:
Ah... In that case it has nothing to do with the update to 12. I was under the impression that you had passed SN before updating, but if you weren't using USNF you wouldn't have passed on earlier Android versions either.
[Magisk] r29:
I did a clean install to 12 though 🤔. on 10/11 I was using forces basic key which was working. I May have missed a step somewhere. But all good appreciate the help.ill try this method again when I get some time to tinker with it.

You might be right I may have had another script on top too.

Safetynet type was basic and only ctsprofile failed.
[Magisk] Didgeridoohan:
So you were using this module and the "Force BASIC key attestation" feature previously? And it didn't work when you tried on A12?

USNF v2.1.0+ is generally a much better solution, so stick with that. But I'd appreciate if you could clarify the above.
[Magisk] r29:
Yup I was using force basic key attestation feature previously from 10/11 . Because I had no modules in magisk so can confirm I was not using usnf prior to upgrading.
[Magisk] bosox284:
Not r29, but I was using this to bypass SafetyNet on A11. I was using 'Force BASIC key attestation' along with a certified device fingerprint back on A11 and it passed SafetyNet. I'm guessing it fails now because there are no certified fingerprints for A12? Either way I'm using USNF now and it passes fine.
[Magisk] ZeoFateX:
I'm passing now with just riru and universal. Had to turn off props config and lsposed and reboot. I had turned every module off and turned the first two on one by one. No need to force attestation or anything apparently. Make sure it's the latest universal as well, since some posts link to older versions.
[Magisk] myhanbing:
How to set ro.debuggable property in v6.1.0?

View attachment 5438593

I don't see the ro.debuggable option here.
[Magisk] Didgeridoohan:
If it's already set to a safe value it won't show up in that menu. Use the "Add/edit custom props" option instead. Reference: https://github.com/Magisk-Modules-R...README.md#setreset-magiskhide-sensitive-props
[Magisk] Didgeridoohan:
PSA

I've been crazy busy with my bachelor's thesis the past few weeks so updates that have been waiting, to both the module and prints list have been put on the back burner. 5 minutes ago I handed that damned thing in though, so after I've slept for a couple of days I can get back to business as usual.

Have a great weekend!
[Magisk] myhanbing:
Thank you!
[Magisk] M1KTA:
Hello everyone, i have xiaomi mi 11 with LineageOS 18. After i install magisk hide props config, i can't recive any notifications. Telegram, Youtube, Gmail and another apps can't send any notification. Can someone help me?
[Magisk] ipdev:
One more update for the fingerprint list.

OnePlus 6T.

From OOS v11.1.1.1 OTA

Cheers all. :cowboy:
[Magisk] Damianek420:
I always used google Pixel 3 xl fingerprint 11(on lineageR mi8 dipper) but changed to DotOs and now with this fingerprint CTS false but with the passing if module turned off
[Magisk] bobpiesz:
It seems basic attestion/cts stopped working on my pixel 5a after latest magisk alpha update.. Safetynet still passes, but basic key/cts will no longer work. Using the same nexus default and all.
[Magisk] pndwal:
Not sure what you mean... Regardless of Evaluation type, if CTS profile match fails you haven't passed SafetyNet.

In any case, please see here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85825005

🤠 PW
[Magisk] bobpiesz:
It's a bit confusing to me as well

Spoiler content hidden.
[Magisk] bobpiesz:
Rolling back to Universal Safetynet Fix to 1.2 fixed the issue:

Spoiler content hidden.
[Magisk] Didgeridoohan:
Updated module to v6.1.1, fingerprints list to v135

So, here's why you guys pay me the big bucks (right? 🤪)! Finally all those submitted fingerprints have been fully tested and included in the ever-growing list of certified fingerprints (although we'll never catch up to Big G).

Small update to the module, but quite the few prints added, most notably the Android 12 prints for the Pixel family (at least those that still see updates). Thank you to @liwenjie119 on Github, @Some_Random_Username, @Displax, @zgfg, @Marciniuk, @cocka11 on GitHub, @vijaykanth and @ipdev. I really appreciate that you guys keep sending me those prints.

Changelog

v6.1.1

Updated custom props so that it's possible to set the same prop with different values during different boot stages.

Updated some module checks to match the new state of Magisk (MagiskHide is dead, long live MagiskHide).

Added fingerprints for LG G8 ThinQ, Samsung Galaxy S20 FE SM-G780F and Xiaomi Redmi K20 Europe. Updated fingerprints for Google Pixel 3 to 5a (all variants), Nokia 6.1 Plus, Oneplus 6T, 9 and 9 Pro (several variants), Xiaomi Mi 9T Europe, Mi 9T Pro Global and Redmi K20 Pro China. List updated to v135.
[Magisk] Marciniuk:
LG G8X ThinQ* ;P
[Magisk] Didgeridoohan:
I've bsolutely no idea what could be causing that. Maybe some conflict with set props...

Maybe if you post the module logs?
[Magisk] Didgeridoohan:
Yeah... Fast fingers, slow mind. :ROFLMAO:
[Magisk] Didgeridoohan:
Probably some conflict with props. Can't say much without logs though...
[Magisk] micbro:
Think there's a way to get SafetyNet working on WSA using "force key attestation"? Tried out the props config on WSA (using the Magisk Canary build) and haven't really got anything changed yet on the Safety Net side of things.
[Magisk] Didgeridoohan:
First of all you'll need Play Services, but I'm assuming you've got that sorted already. WSA won't have hardware backed key attestation, so you're unlikely to need "Force BASIC key attestation" but you'll need to at least use a certified fingerprint. I'm guessing there'll be much more to it than that though...

Of course, in the matter of WSA I've no idea what I'm talking about, so you're probably better of hoping that someone else can answer you... :LOL:
[Magisk] clever_man:
Is anybody can pass SafetyNet on the A12 with Magisk 230010 without Magisk Hide?

I tried Enforce Deny List and added Gpay and Google Services to the list but it still not working.
[Magisk] Didgeridoohan:
I'm passing on A11, but shouldn't be much different on A12...

Apart from adding the gms and unstable processes of Play Services to the deny list (that's all that's needed) you'll also have to spoof the sensitive props that MagiskHide used to change. You can do that with this module's "Edit MagiskHide props" feature. Depending on your device you'll also have to fool keystore to use basic attestation. For now that might be possible with the "Force BASIC key attestation" feature of this module or an older release of Universal SafetyNet Fix (v1.2.0 I believe), until Riru and Zygisk plays nice together or USNF is updated to use Zygisk.
[Magisk] clever_man:
UNSF 1.2.0 worked on A11 but on A12 installation failed with error "A12 (SDK 31) is not supported!"

This module not helped, I tried "Force BASIC key attestation"
[Magisk] Didgeridoohan:
I guess you'll just have to wait then, or downgrade...
[Magisk] lottarake:
Using props config and DenyList as mentioned will do the trick. I'm currently on A12 and passing SN and device is certified with GPay working.

Make sure to clear Play Store and Google Play Services data and cache as well. Forcing attestation won't be needed, just spoofing FP should be enough.

If you need to use LSPosed, Riru is no longer needed and you can resort to the preview builds of zygisk-compatible versions of LSPosed from their TG.
[Magisk] Displax:
Google Pixel 6 | Pro

Google Pixel 6 (12):Google:Pixel 6=google/oriole/oriole:12/SD1A.210817.015.A4/7697517:user/release-keys__2021-10-05
Google Pixel 6 Pro (12):Google:Pixel 6 Pro=google/raven/raven:12/SD1A.210817.015.A4/7697517:user/release-keys__2021-10-05
[Magisk] SotYPL:
I was able to pass all SN checks and get certified in Play Store on both Android 11 (OCtober) and 12 on Pixel 3. To get it working on 12 I had to use older Canary Magisk that supports MagiskHide from May with Riru and USNF 2.1.1 (MagiskHide Props Config was not necessary). On 11 I got it working with latest Canary Magisk, MagiskHide Props Config 6.1.1 and USNF 1.2.0.
[Magisk] Nekromantik:
I will try this on Pixel 6 Pro once you had time to update it with fingerprints for 6 Pro.
[Magisk] Cares:
I have 6 Pro and willing to test whatever you need. I already tried older Magisk with Riru and USNF and didn't work. Latest Magisk of course doesn't work either for SN.
[Magisk] Didgeridoohan:
I'm not the one you should ask about this (I'm assuming that you're asking me, since it's my thread)... I have no way of figuring out what if anything needs to be done to pass SafetyNet on the Pixel 6 and 6 Pro.

Once someone figures it out I might be able to incorporate something into the module, but considering that Google is moving to more and more secure solutions I doubt that simple prop changes will do much.
[Magisk] Didgeridoohan:
Fingerprints list updated to v136

Thank you @Displax for providing the Pixel 6 prints. They're now added to the module list.

The list will update then you run the props command, or by using the -f flag or from the "Edit device fingerprint" menu if you've disabled automatic updates.

Cheers everybody!

New

Google Pixel 6 and 6 Pro
[Magisk] northmendo:
Anyone get Gpay working on the Pixel 6 Pro yet? I have deny list set, cleared all app data and caches and still can't get it.
[Magisk] letm:
Hello,

I want to bypass safetynet but i use a Doogee X5 (Mediatek MT6580 -arm) not list in the fingerprint list . Could you tell me what is the best compatible fingerprint that i can chosse. Thancks.
[Magisk] Olorin92:
Same here - root working fine, denylist seems to be working fine in order to 'hide' root, last thing is getting safetynet to pass. Basic check is working, just CTS profile that fails
[Magisk] Nekromantik:
Even with this module?

We may have to wait for Universal SaftyNet fix to be updated for new Magisk
[Magisk] Pekempy:
Yeah, I've been trying multiple combinations of things including USNF 2.0.0 testing version which runs without Riru. Still failing CTS. Basic integrity passes though.

Hopefully when USNF is built for the latest version without Riru we can pass CTS.
[Magisk] SotYPL:
Just try last Magisk Canary without zygisk from May 12 (https://cdn.jsdelivr.net/gh/topjohn...1f3975a9a548a5d2dff440d9ce9b8a2/app-debug.apk) with latest Riru and USNF 2.1.1. I got it working on Android 12 on Pixel 3 so should work for any other pixel just fine.
[Magisk] eksprestren:
Removed.
[Magisk] dark-basic:
Spoiler content hidden.

I did this, and disable the simulation and pass safetynet
[Magisk] Filo1995:
Xiaomi Redmi K30Pro (Android 11)

ro.build.fingerprint

Redmi/lmi/lmi:11/RKQ1.200826.002/V12.5.5.0.RJKCNXM:user/release-keys

ro.product.manufacturer

Xiaomi

ro.product.model

Redmi K30 Pro

ro.build.version.security_patch

2021-08-01
[Magisk] y3ypTTaTop:
hello, to whom to write to add my Motorola Edge 20 pro phone, sorry, I use google translator.
[Magisk] Didgeridoohan:
Me.

Just post the info here. Take a look at @Filo1995's post right before yours for a great example of what info I'd need to add a device to the list. You can also check the docs for more details:

https://github.com/Magisk-Modules-R...aster/README.md#how-do-i-submit-a-fingerprint
[Magisk] TPelangi:
Xiaomi Mi 6X (Wayne) Android 9

ro.build.fingerprint=xiaomi/wayne/wayne:9/PKQ1.180904.001/V12.0.2.0.PDCCNXM:user/release-keys

ro.product.manufacturer=Xiaomi

ro.product.model=MI 6X

ro.build.version.security_patch=2020-11-05
[Magisk] KreGgiants:
I install the module, but when I go to settings and check MagiskHide or doesn't show in the Supersu menu... And going back to settings, it shows unchecked again.

I'm on Magisk 23.0, Pixel 3a, android 11.

Can't pass anything from safetynet. Any help?
[Magisk] Didgeridoohan:
This module doesn't have anything directly to do with MagiskHide, so I think you want the general support thread...

When you post there, make sure to also post what exact version of Magisk and the app you have installed (easiest might just be to attach a screenshot of the main window of the Magisk app).
[Magisk] Some_Random_Username:
Hi folks, below are newer fingerprints for OnePlus devices, hopefully I got everything right.

As always, OnePlus/OnePlus7/ fingerprint is for GM1901 and GM1905 / OnePlus/OnePlus7Pro/ fingerprint is for GM1911 and GM1917 / OnePlus/OnePlus7T/ fingerprint is for HD1901 and HD1905 / OnePlus/OnePlus7TPro/ fingerprint is for HD1911 and HD1917.

Updated fingerprints:

Spoiler content hidden.

New fingerprints for devices already in list:

Spoiler content hidden.
[Magisk] Techguy777:
Have you guys added pixel 6 pro yet? With features like live transcripts and translations and grammarly Gboard I would love to get those things working