search

nongthaihoang / custom_font_installer

Custom Font Installer for Android
GNU General Public License v3.0
112 stars 10 forks source link

Google-related Settings crashing/not opening with CFI installed #2

Closed cyangalaxy closed 2 years ago

cyangalaxy commented 2 years ago

With CFI installed (using default configs), Google Settings, Find My Device, and other Google-related Settings don't open for me.

I use a Pixel-based Custom ROM. It has built-in font customisation, which does not change the font for the Settings Category Title, but Google Settings can be opened when using one of the built-in fonts.

CFI however does change the font for the Settings Category Title, but many Google-Settings crash with CFI installed.

This leads me to believe that this specific Title-font needs to be Google Sans.

Can I exclude this type of text/font so that Google Settings can open again with CFI ? Or do you know other way to fix Google-Settings crashing?

Here are 2 screenshots, first image is Comic Sans by my ROM (excludes Title-font, Google Settings work), and the second image is "Segoe Variable" using CFI (includes Title-font, Google Settings crash) Screenshot_20220930-172919_Settings Screenshot_20220930-173229_Settings

nongthaihoang commented 2 years ago

Magisk and CFI alone does not cause Google settings or any apps to force close. You probably have other modules installed, i.e., Universal Safetynet Fix, other root-hiding modules. And most importantly, Your ROM is Android 12 and later. I am just a font module maker. I'm not capable of fixing this Magisk vs Android problem. Fortunately, there's a workaround that works for most people. Please check the issue #1.

cyangalaxy commented 2 years ago

Magisk and CFI alone does not cause Google settings or any apps to force close. You probably have other modules installed, i.e., Universal Safetynet Fix, other root-hiding modules. And most importantly, Your ROM is Android 12 and later. I am just a font module maker. I'm not capable of fixing this Magisk vs Android problem. Fortunately, there's a workaround that works for most people. Please check the issue #1.

Thank you for the reply! That was exactly my issue! I'm using the Magisk Module "Universal SafetyNet-Fix" by kdragon to pass SafetyNet. Using AFDKO worked! I did see the closed issue, but thought it was a different issue.

This also explains why I had this issue with other Font Modules.

Thanks for your time & for making OhMyFont and CFI! They're really awesome software! I will close this issue.