I can't understand why if I cahnge the system DPI, the rest of apps still apply defaualt dpi... This didn't happen with Oxygen 11..
How can I fix this?
Astur_Torque said:
I can't understand why if I cahnge the system DPI, the rest of apps still apply defaualt dpi... This didn't happen with Oxygen 11..
How can I fix this?
Click to expand...
Click to collapse
I see there is now option to change DPI from standard settings under Screen options, did you try that? There are 3 options to choose from.
Related
Hey guys,
I want to apply certain themes for CM 9 but they gave me errors that this theme is not compiled properly and all that stuff so I changed my DPI value to 140 so I want to ask that if I kept my DPI value to 140 will there be any problem with hardware or any other thng ??
varun26296 said:
Hey guys,
I want to apply certain themes for CM 9 but they gave me errors that this theme is not compiled properly and all that stuff so I changed my DPI value to 140 so I want to ask that if I kept my DPI value to 140 will there be any problem with hardware or any other thng ??
Click to expand...
Click to collapse
no
Hello,
A great colleague of mine who also owns a xperia S like me
loaded SlimNasomi rom (I think 4.2.2) and did change lcd DPI.
Screen displays more info and icons are smaller. Look nice.
Is it a way to do it with official 6.2.b.1.96 rom ?
I found a thread on a forum about root'ing the phone and
updating a file build.prop in /system, updating ro.sf.lcd_density
I even found an app 'Google Play DPI Fix Tool'
Did anyone already try to play with LCD DPI's ?
Thanks. Cheers from Belgium,
Thierry
I use Texdroider DPI - it worked on stock JB, rooted.
switzerland92 said:
I use Texdroider DPI - it worked on stock JB, rooted.
Click to expand...
Click to collapse
Can I ask you how does it works?
cabi.costa said:
Can I ask you how does it works?
Click to expand...
Click to collapse
It changes build.prop to desired dpi. I use it because it's faster and it really works. I tried on stock ROM, OpenSEMC and letama's AOSP 4.3.
And what is the range of values to stay in to avoid an endless bootloop?
yes that's the question, What value did you use for. in .200 fw i used a lcd density changer soft (don't remember the name) and guess what i got endless loop. I used 244 or something like that.
I usually use 240 and I didn't have any problems with that dpi.
It is standard Android dpi so most apps work just fine. Stock ROM look good but it has some minor offsets (gradient in notification bar as far as I remember).
I have been talking about this in the themes section in an old thread. I keep seeing people have issues with the dpi apps. I personally just edit build prop manually as it is not hard. I use Anttek explorer for my file browsing and edits. I would also suggest you try Xposed framework and per app dpi module. The magic LCD number is 192 for tablet mode. If you set home to 160 it goes into tablet mode but the status bar will not combine at the bottom. There is also another xposed module that forces tablet mode and works well but is still buggy. You also loose small apps.
There is a way to force tablet mode with out the dpi change but I have to figure out how to do that and even then not sure it will actually work. Need to ask some smali experts to help me.
... and what about if in endless bootloop ? ... :crying:
You must make backup before any modifcations
Yea it is a great idea to have a backup when messing with the system. If something goes wrong you can just go back to where you started.
When I change the DPI on any custom rom, why does it spoil recents?
The recents menu becomes blacked out, unless I revert to original DPI.
Fixed-It was a problem with my theme
akhil1999 said:
When I change the DPI on any custom rom, why does it spoil recents?
The recents menu becomes blacked out, unless I revert to original DPI.
Fixed-It was a problem with my theme
Click to expand...
Click to collapse
Maybe problem with the theme..... No such problem here.... Neither in Stock nor custom room....
Hit thanks If it helps....
heys guys..
i tried to change the resolution and dpi(?) on the tablet(8.4 t320) with secondscreen(google play app) to have better results with the dolphin emulator system and apps crash,and i'm forced to restart..
any thoughts or solutions????
i'm using the stock rom with root..
any thoughts or solutions????
Click to expand...
Click to collapse
Sorry, but only the obvious: uninstall it and look for a different way to change dpi.
I've never had success changing resolution or dpi on mine (8.4 t325) with stock or modified stock rom. Only on CM11 (which I'm using now) could I do it, either through terminal or an app.
For anyone wondering in the future, LineageOS supports both MHL AND resolution changing - at least in its current state.
I've been using Android Nougat for quite few months now and in it I used to change the display size to small in Display settings.
Have switched back to stock sense marshmallow for some reasons. Can anyone help me change the display size on Sense Marshmallow like Nougat ?
@ckpv5 can you help me ?
abdulwakil said:
I've been using Android Nougat for quite few months now and in it I used to change the display size to small in Display settings.
Have switched back to stock sense marshmallow for some reasons. Can anyone help me change the display size on Sense Marshmallow like Nougat ?
@ckpv5 can you help me ?
Click to expand...
Click to collapse
Have you tried Nova launcher,it works great on Dev Edition
Steveromingagain said:
Have you tried Nova launcher,it works great on Dev Edition
Click to expand...
Click to collapse
Yes, I know Nova is an option but it just resizes the home screen and app drawer, not the whole system.
I'm looking for something that can change the whole system display size like in Nougat.
abdulwakil said:
I've been using Android Nougat for quite few months now and in it I used to change the display size to small in Display settings.
Have switched back to stock sense marshmallow for some reasons. Can anyone help me change the display size on Sense Marshmallow like Nougat ?
@ckpv5 can you help me ?
Click to expand...
Click to collapse
Just change the default value of
ro.sf.lcd_density=480
in build.prop to your preferable value.
When running stock, mine is
ro.sf.lcd_density=400
Or use dpi changer app like Easy DPI Changer (from Play Store) if your stock ROM is rooted and write protection disabled.
ckpv5 said:
Just change the default value of
ro.sf.lcd_density=480
in build.prop to your preferable value.
When running stock, mine is
ro.sf.lcd_density=400
Or use dpi changer app like Easy DPI Changer (from Play Store) if your stock ROM is rooted and write protection disabled.
Click to expand...
Click to collapse
I tried changing DPI Density through adb with wm density command as I'm not rooted. The density changed but icons on lock screen and the switches in settings were broken.
I was trying to change it to 432 which was the density when I selected small in nougat display settings.
Which lockscreen version ?
I'm on htc lockscreen 8.04.879556 (apkmirror), no issue.
ckpv5 said:
Which lockscreen version ?
I'm on htc lockscreen 8.04.879556 (apkmirror), no issue.
Click to expand...
Click to collapse
Stock Lockscreen. 7.50.653327, I RUU'ed. Should I install from apk mirror with nodpi ?
Doesn't matter no dpi or 480. I always go for no dpi whenever available.