The default DPI is 560, the screen is 516, i like the 516 dpi setting better, but the lockscreen fingerprint gets out of place, anyone has an idea to fix this behavior?
thanks
xhitm3n said:
The default DPI is 560, the screen is 516, i like the 516 dpi setting better, but the lockscreen fingerprint gets out of place, anyone has an idea to fix this behavior?
thanks
Click to expand...
Click to collapse
Try this? I like how IT looks..
First one says standard and second one says small ..
*Attached a preview*
mikkis2k said:
Try this? I like how IT looks..
First one says standard and second one says small ..
*Attached a preview*
Click to expand...
Click to collapse
the small gives 490DPI, i think its to small, 516 is the sweet spot for me, but locksreen gets broken, you have to change in terminal
Code:
wm density
Phone app is so huge, how to change dpi of only this app?
Related
I feel that everything in the stock rom is unnecessarily big. I tried changing the resolution but it made my hardware navigation keys useless.
changing the dpi solved that problem.
i wanted to know know the difference between the two. And also suggestion on which one should i prefer changing.
p.s. isn't dpi a hardware thing? how can an app change that?
thanks in advance.
just change your dpi
ab014 said:
I feel that everything in the stock rom is unnecessarily big. I tried changing the resolution but it madyo hardware navigation keys useless.
changing the dpi solved that problem.
i wanted to know know the difference between the two. And also suggestion on which one should i prefer changing.
p.s. isn't dpi a hardware thing? how can an app change that?
thanks in advance.
Click to expand...
Click to collapse
Use this app called Dpi changer that's available in the playstore.. Change it to 180 or 190 and reboot your phone.. The higher the value the bigger your icons will be.. Easy! :good:
I am trying to change the DPI with:
adb shell wm density 300
the above works correctly. but anything lower, the screen continuously flickers and is unusable.
for example, can't get the following to work:
adb shell wm density 200
any suggestions?
once we get root, this becomes very easy!!! thanks.
why would someone change the density from 480 (stock set in build.prop) to 200? i think its too low density,that all icons and text will be too small.
200 may be too low, but i like to see more contents on the screen. may be 300 is optimal.
Do you have any luck with this? When I change to 320 the navbar is blank in landscape.
ok, i am able to change the lcd density to 360 without issues.
anything less than 300 (say 280), the screen keeps flickering and it is unusable. don't know why.
deepasadish said:
ok, i am able to change the lcd density to 360 without issues.
anything less than 300 (say 280), the screen keeps flickering and it is unusable. don't know why.
Click to expand...
Click to collapse
maybe, because it too low?
DallasCZ said:
maybe, because it too low?
Click to expand...
Click to collapse
Lol. With my nexus 4 I was able to go up to 160 IIRC.
deepasadish said:
Lol. With my nexus 4 I was able to go up to 160 IIRC.
Click to expand...
Click to collapse
I dont know what is IIRc, but the DPI of nexus 4 is 318 so going to 160 is 50%.
Idol3 has 403 so 200 is below 50% (anyway in build.prom is dPI set to 480 ). I think its too low res and the system is nod made for such low res. It simly dont know how to handle it.
Just my opinion.
DallasCZ said:
I dont know what is IIRc, but the DPI of nexus 4 is 318 so going to 160 is 50%.
Idol3 has 403 so 200 is below 50% (anyway in build.prom is dPI set to 480 ). I think its too low res and the system is nod made for such low res. It simly dont know how to handle it.
Just my opinion.
Click to expand...
Click to collapse
you may be right. i am hoping with CM ROM (and good kernel) it may go all the way. for now i am satisfied with 340.
btw, chrome just doesn't go into tablet UI even at 300.
ps. IIRC - if i recall correctly. thanks.
deepasadish said:
you may be right. i am hoping with CM ROM (and good kernel) it may go all the way. for now i am satisfied with 340.
btw, chrome just doesn't go into tablet UI even at 300.
ps. IIRC - if i recall correctly. thanks.
Click to expand...
Click to collapse
how does look the syste mlike in 340DPI? it must be unreadable
deepasadish said:
I am trying to change the DPI with:
adb shell wm density 300
the above works correctly. but anything lower, the screen continuously flickers and is unusable.
for example, can't get the following to work:
adb shell wm density 200
any suggestions?
once we get root, this becomes very easy!!! thanks.
Click to expand...
Click to collapse
I totally forgot about this command to change DPI! I am so glad you posted this. I was about to root my phone just so I could change DPI. I hate big icons and text. I will end up rooting anyway but this way I don't have to eff with the build.prop as some people have said causes issues with this phone. I set mine to 360 which is perfect... Nova launcher will help me optimize from there
Thanks
DallasCZ said:
how does look the syste mlike in 340DPI? it must be unreadable
Click to expand...
Click to collapse
not really. just try it out - you have nothing to lose and you can easily revert back.
once you get used to the increased screen real estate, you will never go back.
sort of reminds me when I went from 1024x768 to 1280x1024 resolution on some monitor some 15+ years ago.
I experimented at 360 and 400. Both looked good. No strange behavior in the short time I used each of them. I'm not sure what I'll do. I liked 400 a little better than 360. But I might live with the stock 480, too, even though for some things, I preferred the lower dpi. It is like going to higher resolution on a computer monitor and this screen is big enough to benefit.
ROM Toolbox is good for these kinds of edits, though direct editing of build.props is easy enough. Make a backup of that file before you edit it.
Navbar in Landscape
deepasadish said:
you may be right. i am hoping with CM ROM (and good kernel) it may go all the way. for now i am satisfied with 340.
btw, chrome just doesn't go into tablet UI even at 300.
ps. IIRC - if i recall correctly. thanks.
Click to expand...
Click to collapse
Does your navbar work properly in landscape at 340? Mine won't work at 320, it's blank.
dbjungle said:
Does your navbar work properly in landscape at 340? Mine won't work at 320, it's blank.
Click to expand...
Click to collapse
yes, works at 340.
maigre said:
I experimented at 360 and 400. Both looked good. No strange behavior in the short time I used each of them. I'm not sure what I'll do. I liked 400 a little better than 360. But I might live with the stock 480, too, even though for some things, I preferred the lower dpi. It is like going to higher resolution on a computer monitor and this screen is big enough to benefit.
ROM Toolbox is good for these kinds of edits, though direct editing of build.props is easy enough. Make a backup of that file before you edit it.
Click to expand...
Click to collapse
Once xposed framework is working on the Alcatel Idol 3 you can use the "app settings" module to allow per app dpi settings.
my phone currently have 240 dpi as default.. btw here is the specs https://pinoyscreencast.net/item/cherry-mobile-omega-lite-2/
so i wanna know if i can change it to 180 or 160 dpi and what will improve to my phone after lowering it.. thanks..
balot.ko said:
my phone currently have 240 dpi as default.. btw here is the specs https://pinoyscreencast.net/item/cherry-mobile-omega-lite-2/
so i wanna know if i can change it to 180 or 160 dpi and what will improve to my phone after lowering it.. thanks..
Click to expand...
Click to collapse
it only makes things smaller on a screen. So, you can fit more stuff on a screen.
Ashwinrg said:
it only makes things smaller on a screen. So, you can fit more stuff on a screen.
Click to expand...
Click to collapse
one more question, will it reduce the quality of my camera like when taking pics and recording vids?
balot.ko said:
one more question, will it reduce the quality of my camera like when taking pics and recording vids?
Click to expand...
Click to collapse
I don't think it will affect on camera or recording because it only related to display.
If you are trying to change screen dpi with build prop editing then it having a chances of bricking your device if anything goes wrong.
Instead of use "app settings" app to change dpi per app basis. But it requires xposed framework installed to be work.
Oh I have the same DPI and I lowered it to 180 easily... It won't affect the quality of anything and won't ruin anything..
You'll feel weird at the beginning then you're gonna get used to it
Just get a Root Browser then go to /system/build.prop then search for " ro.sf.lcd_density=240" and change the number to 180, save then reboot
Sent from the beige bra section at Target.
You can change the dpi on the stock ROM without ROOT by chaging the "smallest width" setting in developer settings. I have mine set to 550 it's looks amazing!
Here is a screenshot of setting menu at 550.
You could also just change the setting in Settings > Display > Advanced > Display Size > Small
411 is default. 434 is the smallest you can go to get an extra icon of space on the status bar (meaning you can fit another icon before you get the overflow dot). 453 is the magic number for the notification side. "Small" per the post above is 484.
Worth it, you can barely notice a difference otherwise. Now if only we had an option to do ONLY the status bar... then we'd be cookin. But this will do for now.
Pure+ said:
You could also just change the setting in Settings > Display > Advanced > Display Size > Small
Click to expand...
Click to collapse
Nope it's not the same. Putting that setting on small does not work on everything. And this way you can go even smaller then the "small" setting.
Celeras said:
411 is default. 434 is the smallest you can go to get an extra icon of space on the status bar (meaning you can fit another icon before you get the overflow dot). 453 is the magic number for the notification side. "Small" per the post above is 484.
Worth it, you can barely notice a difference otherwise. Now if only we had an option to do ONLY the status bar... then we'd be cookin. But this will do for now.
Click to expand...
Click to collapse
I have the setting pure+ posted on normal and put the setting I posted on 551 I feel like that's the perfect mix for me ATM. I will keep playing with it to see if I can find a better combo.
vwgti18 said:
Nope it's not the same. Putting that setting on small does not work on everything. And this way you can go even smaller then the "small" setting.
Click to expand...
Click to collapse
It actually is. If you change the setting and go into dev options it shows the dpi changed. Only difference is it's defaulting to a predetermined dpi
Pure+ said:
It actually is. If you change the setting and go into dev options it shows the dpi changed. Only difference is it's defaulting to a predetermined dpi
Click to expand...
Click to collapse
Ah yes you are right. Thanks for the heads up.
The small setting only changes it to 484 too big for me still! I like it around 550
vwgti18 said:
Ah yes you are right. Thanks for the heads up.
The small setting only changes it to 484 too big for me still! I like it around 550
Click to expand...
Click to collapse
Full disclosure I didn't check to verify this, although I already suspected it, until you said something lol
Pure+ said:
Full disclosure I didn't check to verify this, although I already suspected it, until you said something lol
Click to expand...
Click to collapse
Yeah the olny problem doing it that way is that the change is not enough to really notice a difference.
unfortunately doing it this way compared to doing it via build.prop makes Swiftkey tiny as well
Any one have a suggestion for something in between stock 411 and small 484? Small is just a bit too much for my taste so looking for a happy medium
can we change the DPI through build.prop yet now that we have root?
I added ro.sf.lcd.density=550 and it doesnt seem to be doing anything
doing it through the developer options makes the keyboard unusable.
pr0adam said:
can we change the DPI through build.prop yet now that we have root?
I added ro.sf.lcd.density=550 and it doesnt seem to be doing anything
doing it through the developer options makes the keyboard unusable.
Click to expand...
Click to collapse
Which keyboard are you using?
I am using Gboard with dpi set to 551 and its fine.
vwgti18 said:
Which keyboard are you using?
I am using Gboard with dpi set to 551 and its fine.
Click to expand...
Click to collapse
SwiftKey but 550 was a bad example. I want to make everything smaller, so I went down to something like 450 and the keyboard was very hard to use. Same with the default Gboard
pr0adam said:
SwiftKey but 550 was a bad example. I want to make everything smaller, so I went down to something like 450 and the keyboard was very hard to use. Same with the default Gboard
Click to expand...
Click to collapse
Are you rooted? If so I can tell you how to make gboard bigger but I am not sure about Swiftkey
vwgti18 said:
Which keyboard are you using?
I am using Gboard with dpi set to 551 and its fine.
Click to expand...
Click to collapse
vwgti18 said:
Are you rooted? If so I can tell you how to make gboard bigger but I am not sure about Swiftkey
Click to expand...
Click to collapse
I am rooted yes so I would love to know besides the Gboard setting that increases the size.
pr0adam said:
I am rooted yes so I would love to know besides the Gboard setting that increases the size.
Click to expand...
Click to collapse
Here check if this will work for you! This is the method I was using on my pixel 2 xl it worked great, just one issue is sometimes I could not get the txt edit to save and had to edit the line then got to setting and force stop gboard then go back and save the text file.
https://www.xda-developers.com/gboard-tweaks-height-sensitivity/
vwgti18 said:
Here check if this will work for you! This is the method I was using on my pixel 2 xl it worked great, just one issue is sometimes I could not get the txt edit to save and had to edit the line then got to setting and force stop gboard then go back and save the text file.
https://www.xda-developers.com/gboard-tweaks-height-sensitivity/
Click to expand...
Click to collapse
Thanks for that link, worked for me on Gboard. Hopefully there will be a solution that I can still use Swiftkey but if not I will be going this route once I get home and adjust the DPI further
pr0adam said:
Thanks for that link, worked for me on Gboard. Hopefully there will be a solution that I can still use Swiftkey but if not I will be going this route once I get home and adjust the DPI further
Click to expand...
Click to collapse
I don't have the Pixel yet & I've never tried changing DPI, so forgive me if this doesn't help or if you've already tried this, but Swiftkey has a setting built in to resize the keyboard. I believe it's normally set at "medium", then there is a "large" & "largest" setting to make the keyboard bigger. Go to Swiftkey Settings>Typing>Resize.
Can anyone tell me what their default DPI is? I changed mine in developer settings, now I forget what it was.
Also, what are you using, and hows it working? I've found 360 and 400 work good, except on 400 the keyboard is too low.
Thanks!
392 dpi
YeepYeep said:
392 dpi
Click to expand...
Click to collapse
Awesome thanks!
i killed tupac said:
Can anyone tell me what their default DPI is? I changed mine in developer settings, now I forget what it was.
Also, what are you using, and hows it working? I've found 360 and 400 work good, except on 400 the keyboard is too low.
Thanks!
Click to expand...
Click to collapse
I'm using 462 DPI looks beautiful with Nova Laucher
phuneas said:
I'm using 462 DPI looks beautiful with Nova Laucher
Click to expand...
Click to collapse
Does that make the GBoard too small to use though? that was a problem I seemed to have.
i killed tupac said:
Does that make the GBoard too small to use though? that was a problem I seemed to have.
Click to expand...
Click to collapse
Makes everything too small to use, big screen microscopic text
If you've changed it in Developer Settings you can change it back to default in Additional Settings > Accessibility > Display > Display Size
RaiderX303 said:
If you've changed it in Developer Settings you can change it back to default in Additional Settings > Accessibility > Display > Display Size
Click to expand...
Click to collapse
yes, but that doesn't seem to help the keyboard situation