Hi!
I'm rooted but whatever I set for DPI settings it doesn't seem to matter. I tried apps and directly editing the build.prop, no difference?
tbatliner said:
Hi!
I'm rooted but whatever I set for DPI settings it doesn't seem to matter. I tried apps and directly editing the build.prop, no difference?
Click to expand...
Click to collapse
add qemu.sf.lcd_density=320 or whatever dpi you want into the build.prop then restart
Thank you! ☺
Related
Anyone have tried reducing DPI on our device? Any disadvantages of this operation? Like screwed up icons or something?
Sent from my HTC One SV powered by Saturn III.
Have you tried xposed & appsettings?
I've just noticed the thread about it (XDA App haven't shown it to me or may I missed it). Will do a try, I only hope I won't make a mistake anywhere.
Bazdir said:
I've just noticed the thread about it (XDA App haven't shown it to me or may I missed it). Will do a try, I only hope I won't make a mistake anywhere.
Click to expand...
Click to collapse
I use xposed an appsettings without any problem.
With the other solution (to change dpi in build.prop) you will have the problem that several apps seem to be incompatible and Play Store won't update these "incompatible" apps any longer.
Sylvia said:
I use xposed an appsettings without any problem.
With the other solution (to change dpi in build.prop) you will have the problem that several apps seem to be incompatible and Play Store won't update these "incompatible" apps any longer.
Click to expand...
Click to collapse
So... Setting 217 DPI will cause problems with updating apps such as jakdojade.pl or something like that? God damn it, I hoped, I would have a bit smaller interface like One S has.
And thanks for the feedback.
Bazdir said:
So... Setting 217 DPI will cause problems with updating apps such as jakdojade.pl or something like that? God damn it, I hoped, I would have a bit smaller interface like One S has.
And thanks for the feedback.
Click to expand...
Click to collapse
Personally, I had no update issues in reducing the dpi to 217 in build.prop
The only problem is that some apps will look glitchy (sense interface, torch), for them you'll need to set dpi back to 240, using something like appsettings for xposed framework
madpausa said:
Personally, I had no update issues in reducing the dpi to 217 in build.prop
The only problem is that some apps will look glitchy (sense interface, torch), for them you'll need to set dpi back to 240, using something like appsettings for xposed framework
Click to expand...
Click to collapse
Good. I've tried installing Xposed Framework to get Appsettings module, but then I've been spammed with illegal information. Do I have to install busybox? Or may I just forgot to set system rw in ES File Explorer... I just realised that might be the solution.
EDIT: Well... That haven't worked either. Only app_process have been patched. If I will push xposedbridge by myself, then it should work?
EDIT2: Okay, that haven't changed anything.. Any idea?
Sent from my HTC One SV powered by Saturn III.
Bazdir said:
Good. I've tried installing Xposed Framework to get Appsettings module, but then I've been spammed with illegal information. Do I have to install busybox? Or may I just forgot to set system rw in ES File Explorer... I just realised that might be the solution.
EDIT: Well... That haven't worked either. Only app_process have been patched. If I will push xposedbridge by myself, then it should work?
EDIT2: Okay, that haven't changed anything.. Any idea?
Sent from my HTC One SV powered by Saturn III.
Click to expand...
Click to collapse
Flash back stock boot.img with fastboot, install xposed, flash back the kernel/boot.img you used before.
old.splatterhand said:
Flash back stock boot.img with fastboot, install xposed, flash back the kernel/boot.img you used before.
Click to expand...
Click to collapse
I was wondering, if it wasn't caused by non-stock kernel. Then you picked up the idea here in this thread. And it worked. Thanks!
Bazdir said:
I was wondering, if it wasn't caused by non-stock kernel. Then you picked up the idea here in this thread. And it worked. Thanks!
Click to expand...
Click to collapse
I had the same problem
I'm bumping up this thread again, because I tried to take a DPI one step lower, so it means - 216 DPI. I have to tell, that the interface looks much better than it was on 217. The notification icons are sharper and all the icons and texts are sharper too. I really recommend to try it.
(I didn't want to make a new thread, so I posted it here.)
I find 216 still too large for my liking. I've been running 200 for a while without any issues. It's a good balance.
I am also using the multi-dpi version of google play so no probs there either.
The ONLY minor issue is that it cuts off the bottom of the 'Recent Apps' (the part showing the app name) which isn't a big deal for me at all as I can see what the app is anyway.
Hello,
I was previously on stock 5.0 with ElementalX kernel and SuperSU. I updated to 5.0.1 using TWRP, and everything is working good. I then tried to use BuildProp Editor to change lcd density like usual to 440 or 400, but when I hit apply, and reboot it is back at 480. I don't have computer to try adb route, but any ideas?
CptanPanic said:
Hello,
I was previously on stock 5.0 with ElementalX kernel and SuperSU. I updated to 5.0.1 using TWRP, and everything is working good. I then tried to use BuildProp Editor to change lcd density like usual to 440 or 400, but when I hit apply, and reboot it is back at 480. I don't have computer to try adb route, but any ideas?
Click to expand...
Click to collapse
Just open build.prop with a text editor or file browser/manager and edit the line lol
Lethargy said:
Just open build.prop with a text editor or file browser/manager and edit the line lol
Click to expand...
Click to collapse
Doh, yes this worked. Thanks.
Hello everyone,i was wondering if there is anyway to edit the build.prop to enable the Hidden settings?afaik only MHA-AL00C00 habe the ability to hide the navigation bar.
Thank You in Advance.
i wanna know how to hide it as well.
ywl3k said:
i wanna know how to hide it as well.
Click to expand...
Click to collapse
You can try to activate feature a retractable navigation. Need full ROOT
Method:
Using RootExplorer go to System and keep a copy of the build.prop. If does not help, restore stock recovery. Then open the build. prop in a text editor and find the following line ro.config.hw_navigationbar=false(change to true)
If such lines do not exist you just need to enter
ro.config.hw_navigationbar=true
Put "permission 0644 and reboot
mai55 said:
You can try to activate feature a retractable navigation. Need full ROOT
Method:
Using RootExplorer go to System and keep a copy of the build.prop. If does not help, restore stock recovery. Then open the build. prop in a text editor and find the following line ro.config.hw_navigationbar=false(change to true)
If such lines do not exist you just need to enter
ro.config.hw_navigationbar=true
Put "permission 0644 and reboot
Click to expand...
Click to collapse
edit- done but Didn't have any kind of settings after edit n reboot
None of the usual methods work so far. I too would love a way to disable them as I prefer to just use LMT pie controls with no nav bar.
NeutronBomb said:
None of the usual methods work so far. I too would love a way to disable them as I prefer to just use LMT pie controls with no nav bar.
Click to expand...
Click to collapse
And if make changes here system>vendor>build.prop
Using RootExplorer go to System and keep a copy of the build.prop.
Then open the build. prop in a text editor and find the following line ro.config.hw_navigationbar=false(change to true)
If such lines do not exist you just need to enter
ro.config.hw_navigationbar=true
mai55 said:
And if make changes here system>vendor>build.prop
Using RootExplorer go to System and keep a copy of the build.prop.
Then open the build. prop in a text editor and find the following line ro.config.hw_navigationbar=false(change to true)
If such lines do not exist you just need to enter
ro.config.hw_navigationbar=true
Click to expand...
Click to collapse
Can anyone confirm if this actually works? When I tried editing the build.prop previously it glitched the screen out and I had to wipe. Have you done this and successfully disabled your navigation bar?
NeutronBomb said:
Can anyone confirm if this actually works? When I tried editing the build.prop previously it glitched the screen out and I had to wipe. Have you done this and successfully disabled your navigation bar?
Click to expand...
Click to collapse
In chinese locations AL00C00 this is the default
NeutronBomb said:
Can anyone confirm if this actually works? When I tried editing the build.prop previously it glitched the screen out and I had to wipe. Have you done this and successfully disabled your navigation bar?
Click to expand...
Click to collapse
i have done this and after reboot there is still no option for me to hide the navi bar
www.xda-developers.com/how-to-hide-the-navigation-bar-in-emui-5-0/amp/
That removes the Navbar but unfortunately LMT or any similar apps don't work when swiping from up the bottom of the screen, only the sides work.
neilphetamine said:
www.xda-developers.com/how-to-hide-the-navigation-bar-in-emui-5-0/amp/
Click to expand...
Click to collapse
That's not working unfortunately, not on my mate 8 at least even though I have EMUI 5.0
I'm looking for a way to change the default font without xposed. (Just root) Somebody have an idea?
memocatcher said:
I'm looking for a way to change the default font without xposed. (Just root) Somebody have an idea?
Click to expand...
Click to collapse
I used magisk module.
First set your font to roboto in settings/font
Second you go to magisk manager, downloads and search for fonts. Low, all of theese might not work properly I don't know.. I use exo 2 font without any issues.. I have also tried 2 others without issues.
Use magisk
Use a file explorer like Root Explorer and navigate to "/system/fonts". Paste the fonts you want to use in the folder. You should get a prompt asking you if you want to overwrite the existing font. Accept and then reboot.
Just use ifont if you have root.
Thanks guys!
I tried ifont and it did not work with rooted 1+6 and H2os and Pie with Magisk
Use TypeFace
https://play.google.com/store/apps/details?id=pixkart.typeface
Then you get previews of the fonts and have whole bunch to choose from.
memocatcher said:
I'm looking for a way to change the default font without xposed. (Just root) Somebody have an idea?
Click to expand...
Click to collapse
Would recommend to go ahead and use Magisk. It worked well with my OP5 and now OP6. Have tried using Hifont earlier. Though I uninstalled the app could not restore it back to the normal font until factory reset ( very painstaking).
uses APK fontster ( required root), works very well with many sources.
https://fontster.uptodown.com/android
I am rooted with the pixel 2 font mod installed through magisk, in the phone settings switch to Roboto font, install Ifont and choose a font. Reboot and install chosen font again, reboot
https://play.google.com/store/apps/details?id=com.kapp.ifont
Enjoy
Hello,
I've changed the dpi with root with several different apps to 340 and after a reboot I have to set it again.
I've also changed the dpi in build.prop and it's still resetting every reboot. Any suggestions?
I have no solution, but I would like to see screenshots with 340 dpi settings.. please share..
ykjae said:
Hello,
I've changed the dpi with root with several different apps to 340 and after a reboot I have to set it again.
I've also changed the dpi in build.prop and it's still resetting every reboot. Any suggestions?
Click to expand...
Click to collapse
Here's a Magisk module I just created that changes the dpi to 340.
I suggest you read up on Magisk modules (see the URL in the README.md) so that you understand how it works.
BillGoss said:
Here's a Magisk module I just created that changes the dpi to 340.
I suggest you read up on Magisk modules (see the URL in the README.md) so that you understand how it works.
Click to expand...
Click to collapse
I'm a long time user of magisk. Still somehow managed to end up in crash dump mode. Any suggestions?
Lots of different things cause crash dumps.
Some are easy to get out of; others may require the use of the MSM Tool.
And the Magisk module I gave you wouldn't cause a crash dump.
PM me if you want to discuss this further.
BillGoss said:
Lots of different things cause crash dumps.
Some are easy to get out of; others may require the use of the MSM Tool.
And the Magisk module I gave you wouldn't cause a crash dump.
PM me if you want to discuss this further.
Click to expand...
Click to collapse
I'll pm you.