One of the key features of Huawei’s Emotion UI (EMUI) is the ability to install custom themes onto the device.
Themers can package their work into .hwt files that can then be applied by EMUI’s theme manager application. Users can customize the lock screen style, wallpapers, icons, background colors, and finally the font.
However, some users who upgraded to EMUI 5.0, the latest version based on Android 7.0 Nougat, have found that the “Font Style” option is missing. Furthermore, it appears that these users cannot even change their fonts by applying custom themes that have packaged their own fonts. I can confirm that this is the case on the Huawei Mate 9, as have many others.
Fortunately, there is quite an easy fix available to re-enable switching the font style, and it doesn’t require root. If you have a Huawei device on EMUI 5.0 and cannot find the “Font Style” option under Settings –> Display or in the customization menu of the system theme manager, then all you need to do is send the following ADB shell command:
adb shell settings put system hw_hide_font_style false
(Note: if you can’t get ADB working, make sure you have the proper driver installed. Installing HiSuite will automatically fetch the right driver.)
Reboot, and you should now be able to edit fonts on your Huawei device running EMUI 5.0! I hope you find this tip useful. This doesn’t appear to be a problem on every device running EMUI 5.0 (I’ve seen mixed reports on the Mate 8, P9, and Honor 8 forums), but if you haven’t been able to edit your font hopefully this will work for you. It certainly did for me!
Original link
Related
MaxFTW said:
OP3T, Oxygen OS 4.1.3 rooted with Magisk, stock kernel
Can't apply any theme to my phone. I successfully install substratum, grant it with all the permissions including root, but when it comes to applying themes some problems occur. First of all I don't get this "rebuilding cache" phase or something (right after clicking onto a theme inside the app) since it takes me directly to 'applying theme' part. Of course I choose Oxygen OS correctly and toggle all the apps. After the applying process I get the notification that everything went well and that I have to reboot but after doing so nothing happens and the UI is still stock.
Logcat: https://www.dropbox.com/s/un205p3f6823o5x/4_6044085571880484896[1].txt?dl=0
EDIT
Tried disabling Magisk Busybox, enabling core only mode etc.
Click to expand...
Click to collapse
Coming from Substratum subforum with no solution, got directed to device specific section. Above is basically what I'm struggling with at the moment.
BTW I tried numerous themes, also Swift Dark (which is supposed to be the most forgiving of all)
Go in and manually grant all permissions to masquerade and substratum
I had an issue like this before with one specific app that wouldn't get themed. It showed up on the list and when I apply the theme, everything looks normal. But when I reboot, the app remains unthemed and the Swift Black page does not highlight the app with the green text. Not sure what happened, but dirty flashing OOS fixed it.
There's no touch disable mode since Oreo update.
Anyone experience same problem?
Sent from my VTR-L29 using Tapatalk
Yes... looking for solution for about a week. We need a hw_XXX entry for that feature to enable it.
It´s like font chooser, which you can enable by adb with this command "adb shell settings put system hw_hide_font_style false".
did you find the solution?
DarkHorse said:
did you find the solution?
Click to expand...
Click to collapse
nope. I would need at least honor 7x getprop command result.
DallasCZ said:
nope. I would need at least honor 7x getprop command result.
Click to expand...
Click to collapse
Want my result from P10 Lite EMUI 8 Android Oreo?
I talked to Huawei support on facebook and they told me that:
"Hello, in Android 8 Touch-disable mode is enabled by default and can not be turned off. Best regards"
So i asked is it unavailable to disable it by ADB too:
"Unfortunately, this function has stopped being editable on Android Oreo"
I don't know what to think about this...
surma1231 said:
Want my result from P10 Lite EMUI 8 Android Oreo?
I talked to Huawei support on facebook and they told me that:
"Hello, in Android 8 Touch-disable mode is enabled by default and can not be turned off. Best regards"
So i asked is it unavailable to disable it by ADB too:
"Unfortunately, this function has stopped being editable on Android Oreo"
I don't know what to think about this...
Click to expand...
Click to collapse
I think it is in emui somewhere.. same as honor 7x has DT2W/DT2S (double tap to wake/sleep) mode. It is about to find the proper command to enable/disable it. Same as function to turn on font chooser (whjich was on emui hidden since version 5 or 6). It is still possible to enable the font chooser by adb shell command (in settings/display there will show an option to choose font). Of course it is useless now, because font chooser is in theme app and also accessible trough long press on themeapp icon. but still this function is in EMUI8 and was disabled in EMUI6. So i think all the features of various huawei/honor devices are in all EMUI8 firmwares but we have to find how to enable/disable them.
1- by looking into system/build.prop or system/vendor/build.prop (the old way, not so much used by Huawei these days)
2- by looking and comparing getprop results across various Huawei honor devices
3- by reverse ingeneering the settings.apk and other main apk files (need lot of time for this).
I did this three steps on various models i had and found lot of features that wass disabled/hidden, or was for high end devices and in my device firmware were disabled.
Would be great to have getprop result and build. prop files from a huawei/honor device which still has TOUCH DISABLE MODE option in settings acessibility.
DallasCZ said:
I think it is in emui somewhere.. same as honor 7x has DT2W/DT2S (double tap to wake/sleep) mode. It is about to find the proper command to enable/disable it. Same as function to turn on font chooser (whjich was on emui hidden since version 5 or 6). It is still possible to enable the font chooser by adb shell command (in settings/display there will show an option to choose font). Of course it is useless now, because font chooser is in theme app and also accessible trough long press on themeapp icon. but still this function is in EMUI8 and was disabled in EMUI6. So i think all the features of various huawei/honor devices are in all EMUI8 firmwares but we have to find how to enable/disable them.
1- by looking into system/build.prop or system/vendor/build.prop (the old way, not so much used by Huawei these days)
2- by looking and comparing getprop results across various Huawei honor devices
3- by reverse ingeneering the settings.apk and other main apk files (need lot of time for this).
I did this three steps on various models i had and found lot of features that wass disabled/hidden, or was for high end devices and in my device firmware were disabled.
Would be great to have getprop result and build. prop files from a huawei/honor device which still has TOUCH DISABLE MODE option in settings acessibility.
Click to expand...
Click to collapse
Okay, i started to searching for peoples who have access to build.prop and can send the getprop result UNDER EMUI 8.
surma1231 said:
Okay, i started to searching for peoples who have access to build.prop and can send the getprop result UNDER EMUI 8.
Click to expand...
Click to collapse
it can be also emui5.. just the device should have the desired option enabled.
DallasCZ said:
it can be also emui5.. just the device should have the desired option enabled.
Click to expand...
Click to collapse
Already got P9 Lite EMUI 5.0.3
getprop result
EDIT #1: Second getprop -> Result
No need for build prop or to be rooted.
I just found the solution. Hallelujah!
Download the Settings Database Editor app on Google Play:
https://play.google.com/store/apps/details?id=by4a.setedit22
In the System Table screen, scroll down to the bottom towards the 'T' section and find "Touch Disable Mode 1". Tap on it and change it to 0 to turn it off and hit save.
Please thank if it works for you ?
tboy2000 said:
No need for build prop or to be rooted.
I just found the solution. Hallelujah!
Download the Settings Database Editor app on Google Play:
https://play.google.com/store/apps/details?id=by4a.setedit22
In the System Table screen, scroll down to the bottom towards the 'T' section and find "Touch Disable Mode 1". Tap on it and change it to 0 to turn it off and hit save.
Please thank if it works for you
Click to expand...
Click to collapse
Dude, it works!!! Huawei P10 Lite EMUI 8.0.0 Beta Android 8.0
All root applications need to be systemless to work on EMUI 9.1, old/classic root methods do not work anymore with the newest EMUI 9.1.
EMUI 9.1 introduces the EROFS filesystem for system partitions, which is a strictly read-only file system. This means no write support for anything using root to alter system files, you cannot permanently delete any system apps anymore. However, disabling system apps and bloatware is still possible.
Root features which aren't systemless such as the default hostfile adblocking (e.g. Adaway), root uninstallers, rw root file explorers, converting user apps to system apps, these all can't make (permanent) system changes anymore.
To make the adblocking work again in 9.1 you need to enable the Systemless hosts option in the Magisk Manager as a fix, reboot, and then apply the hostfile.
This also mean if you previously were running FakeGAPPS edxposed module with MicroG you can't do this anymore, as you can't uninstall the original gapps, therefore the MicroG the app signatures will conflict with microg, making it impossible to install. Edit: there is a systemless MicroG which runs instead of the system installed gapps, it's available in the Magisk manager (you still need edxposed and fakegapps for signature spoofing).
It makes me worry for EMUI 10/Android Q, Huawei really doesn't like custom software running on their phones.
EROFS file system
Dialaeialio said:
All root applications need to be systemless to work on EMUI 9.1, old/classic root methods do not work anymore with the newest EMUI 9.1.
EMUI 9.1 introduces the EROFS filesystem for system partitions, which is a strictly read-only file system. This means no write support for anything using root to alter system files, you cannot permanently delete any system apps anymore. However, disabling system apps and bloatware is still possible.
Root features which aren't systemless such as the default hostfile adblocking (e.g. Adaway), root uninstallers, rw root file explorers, converting user apps to system apps, these all can't make (permanent) system changes anymore.
To make the adblocking work again in 9.1 you need to enable the Systemless hosts option in the Magisk Manager as a fix, reboot, and then apply the hostfile.
This also mean if you previously were running FakeGAPPS edxposed module with MicroG you can't do this anymore, as you can't uninstall the original gapps, therefore the MicroG the app signatures will conflict with microg, making it impossible to install.
It makes me worry for EMUI 10/Android Q, Huawei really doesn't like custom software running on their phones.
Click to expand...
Click to collapse
It is for this reason that I quickly turned around and replaced 9.1 with 9.0. I am even looking at going to Oreo to be able to use TWRP. That will allow more flexibility instead of being restricted to how much one can customize his or her own phone. 9.1 may become unpopular with Huawei users.
cindybabe said:
It is for this reason that I quickly turned around and replaced 9.1 with 9.0. I am even looking at going to Oreo to be able to use TWRP. That will allow more flexibility instead of being restricted to how much one can customize his or her own phone. 9.1 may become unpopular with Huawei users.
Click to expand...
Click to collapse
Honestly, this update looks to me more like an update for Huawei and to push their own ecosystem, Huawei services and their HiVoice/HiTouch/HiWhatever crap even more, than it is an update for the users. They are trying to replace everything google with their own alternative and I don't think it's because they will play nice with my data and will be different than Google.
I also have a Huawei smartwatch if I set in the Huawei Health app that I live in the EU then I have to login with a Huawei account to use it, if I say I live in the USA I can still use it without logging in. Soon I might have a brick around my arm because I need an account to use my self-bought device unless I send all my health data straight to China. (To pair my GT watch to my phone I have to send my location or it won't link lmao)
I have the feeling they will start to hide more and more features behind a login screen to access, I am not a hypocrite, I don't use anything Google either, but I feel like I have less and less control over my data and phone... It's really a shame that the custom OpenKirin roms use a generic Huawei camera apk which isn't as good as the stock EMUI one and have some annoying papercut bugs (the OpenKirin developers are still amazing though for giving us a choice and creating a custom rom alternative).
When I bought my Mate 10 Pro you could still unlock your bootloader, and it seemed like it could be a popular device for tech enthusiast and they surgically killed all attempts to modify your own device since then...
And so we never got the big amazing community here that could have been supporting these phones, like the Oneplus phones.
Mostly we have been getting Magisk and all other nice features despite Huawei trying to being as difficult, and because of amazing developers who took the extra time to support EMUI.
I like the phone, it's great hardware, fast, amazing camera, a bit slippery and glassy to hold (but I have a decal on the back), but I wouldn't buy it again, or a different Huawei device for that matter. It's just much effort to do anything for me when you can do the same thing in twrp in two minutes.
-----------
Also it seems like you can install MicroG systemlessly through the Magisk Manager as module which 'overwrites' the gapps systemlessly.
cindybabe said:
It is for this reason that I quickly turned around and replaced 9.1 with 9.0. I am even looking at going to Oreo to be able to use TWRP. That will allow more flexibility instead of being restricted to how much one can customize his or her own phone. 9.1 may become unpopular with Huawei users.
Click to expand...
Click to collapse
Do you mind sharing how you downgraded back to 9.0? I am trying to downgrade my Mate 10 pro BLA-29 C432 from 9.1 to 9.0 or lower. Thanks
Crossover12 said:
Do you mind sharing how you downgraded back to 9.0? I am trying to downgrade my Mate 10 pro BLA-29 C432 from 9.1 to 9.0 or lower. Thanks
Click to expand...
Click to collapse
HiSuite lets you do that:
Update -> Switch to other version -> you'll get Earlier versions tab.
taddzio said:
HiSuite lets you do that:
Update -> Switch to other version -> you'll get Earlier versions tab.
Click to expand...
Click to collapse
Do you know if that this method will lock my bootloader? I am trying to avoid relocking my bootloader.
taddzio said:
HiSuite lets you do that:
Update -> Switch to other version -> you'll get Earlier versions tab.
Click to expand...
Click to collapse
IT is not working anymore, at this moment.
Greetings!
I would like to change the look of Android Auto in my car, primarily hiding the navigation bar.
Following the video indications on the net, I installed the following APPs on my Galaxy S9 smartphone (Android 10 OS): Substratum Lite; Synergy and Estras for AA.
It would seem that everything works, but after selecting the New Theme and confirming the installation, unfortunately everything crashes with the following statement "Some overlay (s) cannot be installed"
=== com.google.android.projection.gearhead
Failed to compile overlay
I ask if anyone can show me how it is possible to resolve the matter. Thank you!
Hi. I have update my OnePlus to OOS 12... and all tasks I use stop working.
What can I do...?
I have root (magisk)...
But Tasker cant change any system setting anymore.
- can't change display timeout any more...
- can't turn AOD on/off
What I need to change thet to work on android 12... it's all working perfectly on 11
Please help
were you prompted to add back all of Tasker's permission requests? You may need to manually re-allow them (including SU with Magisk).
You can also get a lot of help at the official reddit r/tasker where the developer posts frequently.
I try..m didn't change anything... All tasks are in "green" and all seems to work... but non of system settings change.
On the end I find out it's ****ing Oppo Color OS, that make problem with everything....
If anyone know how to make tasker, and probably other apps working fine ln Colot OS, please help...