Related
Hello
Can i change dpi stock 240. Someone have tested?
kvadde said:
Hello
Can i change dpi stock 240. Someone have tested?
Click to expand...
Click to collapse
A solid-state screen's DPI is a physical attribute, you cannot change it.
I believe OP is referring to the soft DPI settings in build.prop. You must root, then edit the ro.sf.lcd_density setting in build.prop. It's already 240 on CM, not sure about stock though.
Cat McGowan said:
A solid-state screen's DPI is a physical attribute, you cannot change it.
Click to expand...
Click to collapse
You are talking about PPI, not DPI
Stock DPI is also 240.
But why would you want to change that??
If some app is not displaying to your satisfaction, it's better not to modify build.prop, because it could lead to unexpected weird behaviors.
Better is to use the "Xposed Framework" with the module "App Settings"; there you can specify individual DPI settings for each app. The safer and more flexible solution! I use it without problems on all my devices.
Felimenta97 said:
You are talking about PPI, not DPI
Click to expand...
Click to collapse
You have it backwards.
kvadde said:
Hello
Can i change dpi stock 240. Someone have tested?
Click to expand...
Click to collapse
As you didn't specify whether you want this on stock firmware or an AOSP ROM, I'd suggest to try the PACman port to the XTZ, as it includes per-app DPI modifier. It's currently in nightlies and no fully stable release as of yet, but it's worth to try if you really need that feature.
DPI = Dots Per Inch
PPI = Pixels Per Inch
The reason we've started to use PPI instead of DPI is because of PenTile, since that technology yields more pixels than dots per inch (dots are shared between adjacent pixels). Both are properties of the hardware but by telling Android you have a different DPI you can scale the UI. This procedure will make graphical elements that makes use of their physical size on the display (rulers, printing tools, etc.) show up at incorrect sizes.
For example, if you have a virtual measurement tape, you'll need to multiply all values with the original DPI divided by the new DPI. So if you choose to change your tablets DPI to 120, making every UI element scale to half of the original size, you'd need to multiply every value by 240/120=2 for it to match up with the real world.
I hope this clears things up.
Shanliang- said:
As you didn't specify whether you want this on stock firmware or an AOSP ROM, I'd suggest to try the PACman port to the XTZ, as it includes per-app DPI modifier. It's currently in nightlies and no fully stable release as of yet, but it's worth to try if you really need that feature.
Click to expand...
Click to collapse
As I already said: No need to change firmware. Just install Xposed framework with App Settings module on rooted device, and you can freely modify DPI per app.
CM12.1 support DPI adjustment natively (if you see some apps still show bigger font, then try modify the build.prop to same value, this may help.)
========================
B320/B322 update screwed up below DPI adjustment. Thanks @medwatt testing, see #45 for details. For values like 240 or 260, the phone is completely blank, and if you do 'adb shell logcat *:E', you can see the resource not found error all over the place.
========================
Edit on July 3, 2015:
On Lollipop B309, the ro.sf.lcd_density is in build.prop already and set to 320, we can change it to smaller value: (make a backup first)
Code:
ro.sf.lcd_density=240
you can use any number between 240 to 320. Save then reboot. (Thanks @ArkAngel06 point out this entry still works)
Then everything is working fine. No expose needed and didn't see any big problem so far.
One problem we noticed is stock 'Browser' app FC, pls use your favorate 3rd party browser instead. (The one i currently use is boat browser)
========================
Following is original post for JellyBean 4.3
===Normal disclaims applies, be careful and know how to use adb to restore /system/build.prop before you try this=============
You phone may brick if this file got corrupted.
ROOT is required to change the LCD density.
Today trying to play around the DPI of display, and noticed the stock value is 320:
Code:
getprop | grep dens
[ro.sf.lcd_density]: [320]
But our 720p display native DPI is 240. That's why all the stuff display so big??
Anyway, I backed up /system/build.prop, and play a little bit.
I recommend simply use Root Browser with "RB Text Editor" to do the task. Other DPI changer app may work and convenient, but it is more risky and may do some change unknown to the phone. Due to lack of backup/restore recovery right now, I prefer manually editing the file myself.
Adding following to the end of /system/build.prop.
Code:
ro.sf.lcd_density=264
For some different varies like Consumer Cellular version, or MT2L05 version, you can try following if above doesn't work:
qemu.sf.lcd_density=264
Not sure it is a bug or what, when I use ES file explorer to edit the file, If I select edit mode right after open the file, it won't scroll to the end of file. I have to scroll to the end first in view mode, then select edit mode. Anyway, Root Browser editor works without any problem.
Following is some test result:
Code:
______________ System UI________ Settings__________ Gallery
180__________force close
200______________ok____________ force close______ force close
220______________ok____________ force close______ force close
240(native)______ok____________ force close______ force close
260______________ok____________ force close______ force close
264______________ok________________ ok____________force close
280______________ok________________ ok____________force close
320(stock)______ ok________________ ok________________ ok
Also, for all DPI less than 320, the stock lock screen shortcut is not displayed properly.
I think I will stick with 280 (update, now I am using 264) for a few days and see if I found more problems. And it should be easy to find an alternative gallery app.
The smaller font and everything actually make the display more clear and sharp
PS. I know there is font size in display settings, but the DPI change will make system zoom everything based on this new display density.
Thanks aragon257 and others feedback, some info from below is collected from the replies. Thanks.
MORE INFO/UPDATE:
. There is Exposed framework modules (like app settings) to do per app DPI settings. Please see end of this post for more info.
. The app force closing caused by lower DPI is purely software (view layout arrangement) issue, so lowering DPI will not do any harm to hardware.
. List of Apps that Force Close. I list them from higher DPI to lower DPI, The apps that crashes in higher DPI will also crash in lower DPI.
DPI 264 or 280: Currently I am using 264.
Lock Screen: No crash here. The app short cut moved to center of the circle, and requires less distance swipe to unlock.
Gallery (Also affecting camera since it start Gallery when you view pictures)
Alternative: "Galleray KK" and "Camera KK" from play store works pretty good, though it is Ads supported.
DPI 240:
Settings
Phone app when receiving calls.
Use Xposed Framework
OK, set DPI to 240 in build.prop, I need use Xposed module "App Settings" to set following App DPI to higher value to make the phone fully work:
Code:
Gallery(com.android.gallery3d): 297 (dp: 320x480)
Phone(com.android.phone): 264
Settings(com.android.settings): 264
SystemUI(com.android.systemui): 264
This number is set to lowest possible value, of course you can set to 320, then related apps will be bigger.
Please see attachment for some screenshot: (Left is stock 320 DPI, right is 264 DPI)
Thanks for doing all the research here
Use xposed and install app settings. Use it to give those apps that crash the default DPI. Just tried working great. And thanks about the tip of adb build.prop backing up.
Running at 240 DPI here.
Edit: Play store wouldn't download anything until I cleared the cache.
Edit again: Actually viewing images and trying to use the camera causes the gallery to crash... Ill fix it
FINAL Edit: Installed the kitkat camera and gallery. I had to unisntall the old gallery first. This works for me
Great, that xposed module is pretty cool, but for now I must resist as we don't have recovery yet
BTW, I have updated first post to correct the System UI FC number, it is 180, not 220. ie, DPI can be as low as 200 and the phone is still usable. So, native 240 is a pretty safe value.
Also, the "Huawei home" FC start showing up from 220 and below, though I am using Nova launcher.
Cheers.
I was having problems with incoming calls crashing the phone app. So back to 320, but using App Settings to change my downloaded apps to 240
Admired by this thread:
http://forum.xda-developers.com/galaxy-nexus/general/info-official-galaxy-nexus-lcd-density-t1392089
Call me bored, today I have tried more DPIs, and found 264 is the lowest number that Settings is working. Since the crashing is just cause by GUI view arrangement issue, nothing to do with hardware etc. So I will stick with 264 for now.
For the past few days with settings 280, I only noticed gallery is the problem. I didn't try too much widget/apps. Everything else I tried works pretty good.
Please refresh my memory, is lowering the DPI making the image smaller? If so, im interested.
yes, everything (font,icon,layout)will be smaller. but image actually maybe different story. try and see yourself!
so what apps are better in tablet mode for me to try?
Bobvark said:
so what apps are better in tablet mode for me to try?
Click to expand...
Click to collapse
I didn't use any particular tablet mode etc stuff, the lower DPI gives me more space asset, thats all.
xordos said:
I didn't use any particular tablet mode etc stuff, the lower DPI gives me more space asset, thats all.
Click to expand...
Click to collapse
ok, so Chrome, gmail, what would be good DPI for those? I'm a little worried about f'n up my phone and don't just want to do trial and error.
Is 240 the standard you all are using?
Bobvark said:
ok, so Chrome, gmail, what would be good DPI for those? I'm a little worried about f'n up my phone and don't just want to do trial and error.
Is 240 the standard you all are using?
Click to expand...
Click to collapse
264 or 280 should be safer. 240 the settings app wont work.
Added some screenshot to the 1st post.
I wanna mess with this later
aragon257 said:
I was having problems with incoming calls crashing the phone app. So back to 320, but using App Settings to change my downloaded apps to 240
Click to expand...
Click to collapse
ok, now with a twrp backup taken, I installed xposed and now i got exact same problem. 240 is really sweet dpi, even the lock screen layout is good.
I tried complete delete phone.apk, and contacts.apk, but looks like not easy to find a good replacement. other dialer app from play store still requires these two apks. And i checked my other phone 4.3 rom, they force close. will continue to the search.
Have you tried it with the xposed programs? I know it worked for gallery but not sure for settings.
oncouch1 said:
Have you tried it with the xposed programs? I know it worked for gallery but not sure for settings.
Click to expand...
Click to collapse
Thanks. Didn't try gallery with app settings module yet. For 240 dpi, call out/in problem is what I am focused on right now.
Was trying app settings with 240, I set phone dialer etc. at stock setting but forgot had face lock so when I restarted, crash due to camera (what a [email protected]!) Thank you guys for TWRP so I could restore! . On vacation and no PC to try and adb to modify build.prop.
Sent from my MT2L03 using XDA Free mobile app
xordos said:
Thanks. Didn't try gallery with app settings module yet. For 240 dpi, call out/in problem is what I am focused on right now.
Click to expand...
Click to collapse
yes, with exposed module, at 240 dpi, gallery/camera works fine, settings also worked, only phone app still FC. so now i am at 264, and use exposed to fix gallery.
Silly question, app settings didn't work on dialer?
oncouch1 said:
Silly question, app settings didn't work on dialer?
Click to expand...
Click to collapse
when calls come in, phone apps FC when dpi is 240 ( and app settings use 320 for com.android.phone)
EDIT:
OK, Maybe this defeat the purpose, set SystemUI to 264 resolve the incoming call problem. The incoming call crashed the phone app because the StatusBar trying to get a phone icon resource but failed.
To summary, In build.prop DPI set to 240, I need use Xposed "App Settings" to set following App DPI to higher value to make the phone fully work:
Code:
Gallery(com.android.gallery3d): 297
Phone(com.android.phone): 264
Settings(com.android.settings): 264
SystemUI(com.android.systemui): 264
This number is set to lowest possible value, of course you can set to 320, then related apps will be bigger.
Hi
Can someone mod. the SamsungCamera3.apk for another screen resolution ? I have it set to 420 dpi (build.prop) and the camera app is now just too small
And when i change the app with xposed(app settings), than the s-health app crash...
thx
Change the camera app DPI back to 640 on app settings. As for s-health, I recommend freezing the app with titanium backup if you don't use it.
datom84 said:
Hi
Can someone mod. the SamsungCamera3.apk for another screen resolution ? I have it set to 420 dpi (build.prop) and the camera app is now just too small
And when i change the app with xposed(app settings), than the s-health app crash...
thx
Click to expand...
Click to collapse
Can you post a screenshot with the camera interface set at 420dpi? And what are the other Samsung apps that don't play well with this dpi? Thanks!
Disable secure storage using wanam or editing build.prop to fix s health. Might need to clear its app data as well.
djnoicatse said:
Change the camera app DPI back to 640 on app settings...
Click to expand...
Click to collapse
How i do that man ? Thanks
install xposed framework then install app setting, then set camera app to dpi = 640
I am doing this way too, my system dpi is 480 right now.
Cool, it works. Can even turn camera sound off ... Thanks m8.
Now that we have root and kernel adiutor, we might be able to change the dpi to the screen dpi with it.
Has already someone changed this?
According to the dpi calculator:
https://www.sven.de/dpi/
We should have ~197 dpi, but there is 280 in the build.prop
Actually how many dpi does our watch have?
I set the calculator above to 2.3 so the result reads 1,63x1,63 display.
But other calculators are different...
Change it for whole android is not perfect. Try instead the Xposed module app settings to change dpi for specific apps.
I have found a way to enable 120hz on WQHD+ display setting
For root
1. Install Easy DPI Changer [Root]
2. Change resolution to 1436x3192 and DPI to desired size that you like. I have 384
3. Go to settings and set refresh rate to 120Hz
Without root
1. Use adb
2. Change resolution to "adb shell wm size 1436x3192" and DPI to desired size that you like. I have 384 "adb shell wm density 384"
3. Go to settings and set refresh rate to 120Hz
Screenshot 1 - Screenshot 2
Have fun!
Cholens said:
I have found a way to enable 120hz on WQHD+ display setting (You need root)
1. Install Easy DPI Changer [Root]
2. Change resolution to 1436x3192 and DPI to desired size that you like. I have 384
3. Go to settings and set refresh rate to 120Hz
Have fun!
Click to expand...
Click to collapse
no way without root??
Sent from my SM-G988B using Tapatalk
I have updated it for non root as well
carlitobahsoun said:
no way without root??
Sent from my SM-G988B using Tapatalk
Click to expand...
Click to collapse
Cholens said:
I have found a way to enable 120hz on WQHD+ display setting
For root
1. Install Easy DPI Changer [Root]
2. Change resolution to 1436x3192 and DPI to desired size that you like. I have 384
3. Go to settings and set refresh rate to 120Hz
Without root
1. Use adb
2. Change resolution to "adb shell wm size 1436x3192" and DPI to desired size that you like. I have 384 "adb shell wm density 384"
3. Go to settings and set refresh rate to 120Hz
Screenshot 1 - Screenshot 2
Have fun!
Click to expand...
Click to collapse
Hey Thank you very much for sharing this tweak! I'll test battery life
BTW just wondering in case I wanted to go back to stock... I'd just change the resolution, and that's it, right?
Thanks, settings that seem to look the best for me:
adb shell wm size 1436x3192
adb shell wm density 511
Set "Font Size" to 2
Will check this by tonight. Nice !
How to change all back to stock? Especially the density and font size?
Nakashima Taiki said:
How to change all back to stock? Especially the density and font size?
Click to expand...
Click to collapse
Just change resolution in settings like normal, and change DPI in developer options to 411
-------------
Unfortunately with this new resolution it causes an empty gap around the edge of the screen
*Detection* said:
Just change resolution in settings like normal, and change DPI in developer options to 411
-------------
Unfortunately with this new resolution it causes an empty gap around the edge of the screen
Click to expand...
Click to collapse
Thank you. How about the font size? Should I just change it in the font size and style setting?
Nakashima Taiki said:
Thank you. How about the font size? Should I just change it in the font size and style setting?
Click to expand...
Click to collapse
Yea, just change it from settings to whatever looks best for you, I set it to 2
*Detection* said:
Yea, just change it from settings to whatever looks best for you, I set it to 2
Click to expand...
Click to collapse
Thanks. Is the empty gap happened because of the dpi?
Update: I think because the resolution for WQHD+ is 3200x1440. Can we have the 120Hz with that resolution rather than 1436x3192?
Thanks my friend.
What About batery impact??
Enviado desde mi SM-G988B mediante Tapatalk
Nakashima Taiki said:
Thanks. Is the empty gap happened because of the dpi?
Update: I think because the resolution for WQHD+ is 3200x1440. Can we have the 120Hz with that resolution rather than 1436x3192?
Click to expand...
Click to collapse
No, it sets to WQHD and sets back to 60Hz, I tried
*Detection* said:
No, it sets to WQHD and sets back to 60Hz, I tried
Click to expand...
Click to collapse
I see. That's why
Gofo_81 said:
Thanks my friend.
What About batery impact??
Enviado desde mi SM-G988B mediante Tapatalk
Click to expand...
Click to collapse
I don't notice much difference than on FHD+ 120hz in battery life. that it used a little more is normal
How is this possible? I was under the impression the panel itself is unable to support this due to hardware limitations ?
digitaljeff said:
How is this possible? I was under the impression the panel itself is unable to support this due to hardware limitations ?
Click to expand...
Click to collapse
This is what I have read multiple places also that it was a hardware limitation.
digitaljeff said:
How is this possible? I was under the impression the panel itself is unable to support this due to hardware limitations ?
Click to expand...
Click to collapse
aussiesausage said:
This is what I have read multiple places also that it was a hardware limitation.
Click to expand...
Click to collapse
Yeah! It is hardware limited. The device is actually running at HD+ on that resolution, and the phone is capable of running HD+ @120hz but if you set the WQHD+ screen size correctly (1440x3200) the phone will run only @60Hz.
jimbo77 said:
Yeah! It is hardware limited. The device is actually running at HD+ on that resolution, and the phone is capable of running HD+ @120hz but if you set the WQHD+ screen size correctly (1440x3200) the phone will run only @60Hz.
Click to expand...
Click to collapse
Is whi i have puted 1439x3199 and recognises like WQHD+ AND WORKS LIKE A CHARM at 120hz....
YouTube recognises for watching at 1440 résolution
Nmc_alves® said:
Is whi i have puted 1439x3199 and recognises like WQHD+ AND WORKS LIKE A CHARM at 120hz....
YouTube recognises for watching at 1440 résolution
Click to expand...
Click to collapse
It's not 120Hz at that resolution, I tried too, it says 120Hz but is actually 60Hz, it's not smooth like 120Hz