Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
shyv said:
Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
Click to expand...
Click to collapse
Running 200 here on cm 7 with no problems
shyv said:
Hi
When I set the lcd density from 240 to 200, everything looks great, except the notification bar. The icons are very fuzzy and blurred, maybe CM7 got some problems with scaling them.
Someone got a solution or did someone discover the same problem?
Click to expand...
Click to collapse
In the build.prop, next to the line qemu.sf.lcd_density=200, there's a command on something called debug.fb.rgb565=0, try deleting it.. i remember last time, when i haven't delete it, causes me some graphical issues.
SAPPH1RE said:
In the build.prop, next to the line qemu.sf.lcd_density=200, there's a command on something called debug.fb.rgb565=0, try deleting it.. i remember last time, when i haven't delete it, causes me some graphical issues.
Click to expand...
Click to collapse
well, I just tried it with having this line deleted. My phone got stuck in bootloop then :/
(Note: I had to push the build.prop with ADB on my phone, first I tried to do it on my phone with RootExplorer, I dont know why it didnt work then. I could change the file, but after reboot it was set back to normal again.)
Edit: OK maybe I just made something wrong, I did it again with the RootExplorer method, and the line "debug.fb.rgb565=0" is now gone, but i left the space there. Still no improvements, density is on 200 now Might it be CM7 that I'm using?
shyv said:
well, I just tried it with having this line deleted. My phone got stuck in bootloop then :/
(Note: I had to push the build.prop with ADB on my phone, first I tried to do it on my phone with RootExplorer, I dont know why it didnt work then. I could change the file, but after reboot it was set back to normal again.)
Edit: OK maybe I just made something wrong, I did it again with the RootExplorer method, and the line "debug.fb.rgb565=0" is now gone, but i left the space there. Still no improvements, density is on 200 now Might it be CM7 that I'm using?
Click to expand...
Click to collapse
Which CM7 did you use? Mine on signature, works great all the time.. Well, when i remember the first time i tinkering with lcd density, i tried 160 instead.. The font was so small, my homescreen looks empty enough.. Looks good, but i had some horizontal line on menu.. Increase the lcd density to 200 resolve the problem while still maintaining to look good.. No fuzzy or blurred..
Maybe yours it's no compatible to 200 like mine on 160.. Maybe the hardware itself, i don't know.. Try 210, or 220..
edit: Could u post the pic of the aforementioned prob?
I am using CM7 build #25. The launcher and apps are okie except gameloft games where they don't show in fullscreen mode :| is there any walkaround for them?
lpachuong said:
I am using CM7 build #25. The launcher and apps are okie except gameloft games where they don't show in fullscreen mode :| is there any walkaround for them?
Click to expand...
Click to collapse
Open spare parts apps (if you don't have, try searching the market), untick compatiblity mode, and reboots.. That should fix any app that didn't run fullscreen..
SAPPH1RE said:
Which CM7 did you use? Mine on signature, works great all the time.. Well, when i remember the first time i tinkering with lcd density, i tried 160 instead.. The font was so small, my homescreen looks empty enough.. Looks good, but i had some horizontal line on menu.. Increase the lcd density to 200 resolve the problem while still maintaining to look good.. No fuzzy or blurred..
Maybe yours it's no compatible to 200 like mine on 160.. Maybe the hardware itself, i don't know.. Try 210, or 220..
edit: Could u post the pic of the aforementioned prob?
Click to expand...
Click to collapse
It seems like my device is just compatible to 240 dpi, my phone is not even trying to resize that stuff, the lower I set the dpi the more it gets "unclear".
(The funny thing is, that on the stock rom, everything looks very nice and small. must be something related to the whole roms)
shyv said:
It seems like my device is just compatible to 240 dpi, my phone is not even trying to resize that stuff, the lower I set the dpi the more it gets "unclear".
(The funny thing is, that on the stock rom, everything looks very nice and small. must be something related to the whole roms)
Click to expand...
Click to collapse
Hmm, weird.. Try flashing other CM7..
SAPPH1RE said:
Open spare parts apps (if you don't have, try searching the market), untick compatiblity mode, and reboots.. That should fix any app that didn't run fullscreen..
Click to expand...
Click to collapse
Thx man
I have changed my density to 190 with LCD Density app and everything looks great.
But I have an issue, everytime I reboot my phone it goes back to 240. Then I have to use LCD Density once again and reboot to get back at 190.
Is there a solution to get around this problem?
I´m using latest CM7 nightly build #30.
snowmer said:
I have changed my density to 190 with LCD Density app and everything looks great.
But I have an issue, everytime I reboot my phone it goes back to 240. Then I have to use LCD Density once again and reboot to get back at 190.
Is there a solution to get around this problem?
I´m using latest CM7 nightly build #30.
Click to expand...
Click to collapse
I tried it once and same result for me.
Just use rootexplorer to edit the file and change the density.
Or use adb to "pull" then modify the file and "push" it back:
adb pull /system/build.prop
modify with txt editor
adb push build.prop /system/
Next time use 7zip to modify the files before flashing the ROM.
I alway modify /system/build.prop for the lcd size and /system/etc/gps.conf for time servers before flashing.
truc007 said:
I tried it once and same result for me.
Just use rootexplorer to edit the file and change the density.
Or use adb to "pull" then modify the file and "push" it back:
adb pull /system/build.prop
modify with txt editor
adb push build.prop /system/
Next time use 7zip to modify the files before flashing the ROM.
I alway modify /system/build.prop for the lcd size and /system/etc/gps.conf for time servers before flashing.
Click to expand...
Click to collapse
thanks.
but im not sure how to use adb.
i only get failed cannot write file.
I will go on with the second solution and modify the zip file before flashing the next CM7.
Thanks for your help again.
snowmer said:
I will go on with the second solution and modify the zip file before flashing the next CM7.
Thanks for your help again.
Click to expand...
Click to collapse
Really, this is very easy to do on the phone, without any extra applications. Just use a file explorer with root access (like root explorer), navigate to /system/, open your build.prop file, modify the density line (ro.sf.lcd_density=xxx) to whatever you want and reboot. 190 is working nicely for me (nightly 30/CleanDHD).
snowmer said:
thanks.
but im not sure how to use adb.
i only get failed cannot write file.
Click to expand...
Click to collapse
Sorry, forgot this.
Just type "adb remount" to mount the system in Read/Write instead of ReadOnly
If you're under linux you may need sudo (but don't think so as under w7 you don't need admin...)
I dont see any improvement by changing it to 200 its only bad look now, I will change it back to 240.
And what improvements it should give me, by changing to lower density?
Sent from my Desire HD using XDA Premium App
s2 density at 200 not booting
please assist my s2 is not booting after changing to 200 with lcd density changer on a rooted s2. heeeeeeelp
Related
Anyone else found that when they set a custom density not all apps resize, they seem to keep the default density of the Samsung ROM? even though it has been changed. NOVA HD was one but also dialler app and camera for me.
It is also irritating that touchwiz seems to be locked to particular density as well. Anyone found any workarounds for this?
I assume you've turned Compatibility Mode off in Spare Parts? If not, try that first.
TouchWiz seems to misbehave even with that turned off, but I've had no problems with anything else being too small while running at 192 density.
you weather and clock arent squashed up into the top left hand side of your screen then, leaving about 3/4 inch column down the right hand side?
Have to wait for a good multi dpi theme or rom... but I think without cwm they'll have to wait
Sent from my GT-I9100 using XDA Premium App
Anyone else notice that the video camera starts force closing when the led density is at a non default value?
fpar said:
Anyone else notice that the video camera starts force closing when the led density is at a non default value?
Click to expand...
Click to collapse
for me it's FC's when using 180 LCD Density, 185 works fine.
fpar said:
Anyone else notice that the video camera starts force closing when the led density is at a non default value?
Click to expand...
Click to collapse
YES.!, thought it was just me, didn't realise it was density at first and ended up flashing my phone twice from scratch, second time I didn't use it and no force closes.
Custom ROMS starting to head our way now so hopefully we can get this issue resolved.
stoolzo said:
Anyone else found that when they set a custom density not all apps resize, they seem to keep the default density of the Samsung ROM? even though it has been changed. NOVA HD was one but also dialler app and camera for me.
It is also irritating that touchwiz seems to be locked to particular density as well. Anyone found any workarounds for this?
Click to expand...
Click to collapse
the camera app and the dialer isnt working very well on the resize, im only at 200 density
any fix?
Budske said:
the camera app and the dialer isnt working very well on the resize, im only at 200 density
any fix?
Click to expand...
Click to collapse
Have disabled compability mode in spare parts?
Running mine at 216 no issues so far
Sent from my GT-I9100 using XDA App
Yes, I disabled it..
Added some screens
Sent from my GT-I9100 using Tapatalk
Yeah there's quite a few oddities when changing density. I basically worked around it by replacing most of the default programs.
Dialer: DialerOne
Camera: One of the numerous camera apps in market
Music: Poweramp
Videos: mVideoPlayer
I still have to find decent replacements for Calendar and Contact list, though the contact list doesn't look bad really.
What theme are you using? I like orange
Budske said:
Yes, I disabled it..
Added some screens
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Sent from my GT-I9100 using Tapatalk
Its not a theme, its just the screengrab app that changes the colors, it is not for this phone xD
Sent from my GT-I9100 using Tapatalk
Ok, using this post as reference, I messed around with the Contacts.apk file.
I managed to resize the default dialpad to fit 200dpi.
Note that this apk was only tested on VillainRom. I don't think the signatures are compatible with normal deodexed roms.
However the scrolling aid on the right side when searching through contacts is still too small. Haven't found how to fix that yet.
EDIT: Also fixed the TouchWiz Calculator. Fits nicely on both portrait and landscape mode.
As I mentioned on another post below, if it doesn't work on your ROM, just replace the META-INF directory in my apk with the META-INF from your original apk to resign that package.
NOTE: Previous version of Contacts.apk still had misaligned landscape dialpad. I've fixed it and reuploaded.
JaeCee said:
Ok, using this post as reference, I messed around with the Contacts.apk file.
I managed to resize the default dialpad to fit 200dpi.
Note that this apk was only tested on VillainRom. I don't think the signatures are compatible with normal deodexed roms.
However the scrolling aid on the right side when searching through contacts is still too small. Haven't found how to fix that yet.
Click to expand...
Click to collapse
i wont use this cos the sigs are diferent, but if u can point me where to look to change the settings, i will make my own... or ill just upload my apk for u to fix it, or make it more resizeable.
thx for the help!
Well an easy way for you to get it to work on yours is to download the Contacts.apk that I uploaded. Copy your Contacts.apk somewhere, and open both apks in 7zip. Then just copy the META-INF directory from your apk to my apk. That basically changes the signature. Once that's done my apk should work for you.
JaeCee said:
Well an easy way for you to get it to work on yours is to download the Contacts.apk that I uploaded. Copy your Contacts.apk somewhere, and open both apks in 7zip. Then just copy the META-INF directory from your apk to my apk. That basically changes the signature. Once that's done my apk should work for you.
Click to expand...
Click to collapse
Let's take it one step further, what are the files you changed in your apk? For example, I know with the dialer, we may only need to change dialer_app.xml.
lpsi2000 said:
Let's take it one step further, what are the files you changed in your apk? For example, I know with the dialer, we may only need to change dialer_app.xml.
Click to expand...
Click to collapse
I actually went overkill on the apk. I basically grabbed the layout_resize java file from this thread and ran it on all layout xml files. Basically the script replaces all x dip references to x * 1.5 px. It's a bit unwise actually, but so far it's working as intended. Gonna test it for a few more days to see if replacing all dips broke anything.
JaeCee said:
I actually went overkill on the apk. I basically grabbed the layout_resize java file from this thread and ran it on all layout xml files. Basically the script replaces all x dip references to x * 1.5 px. It's a bit unwise actually, but so far it's working as intended. Gonna test it for a few more days to see if replacing all dips broke anything.
Click to expand...
Click to collapse
I see, yeah that was a little bit too much for me. Nonetheless keep us posted on your progress. I am currently running 182 dpi which is the safest before certain stock applications stop working.
lpsi2000 said:
Let's take it one step further, what are the files you changed in your apk? For example, I know with the dialer, we may only need to change dialer_app.xml.
Click to expand...
Click to collapse
yeah, i want to know what changes u made to fit the 200 density. and some day i will learn how to do stuff and i want to start now
I wiped EVERYTHING and reflashed the ROM. It seemed to have work, but then I was at the default density. Once I used LCD Density to 220, the error happened again. It forces closes. Any help? CM7.1
mapheG2 said:
I wiped EVERYTHING and reflashed the ROM. It seemed to have work, but then I was at the default density. Once I used LCD Density to 220, the error happened again. It forces closes. Any help? CM7.1
Click to expand...
Click to collapse
It's my understanding that altering the density can breaks things, including applications... looks like you'll have to choose between your desired screen density or Wifi Calling app.
This sucks
not sure why you want to change this, on any LCD display the native resolution (and therefore LCD density) whether on a phone, computer, tablet or whatever, is always the clearest, sharpest and best looking!
The icons and text are just too big to my liking after trying LCD density. At 220, as opposed to 240, everything just looks nicer and there isn't noticeably a decrease in sharpness or clarity.
Open spare parts, enable compatibility mode, reboot. See if that fixes it.
^ Nope, I tried that before. That doesn't help. Thanks for the suggestion though!
mapheG2 said:
^ Nope, I tried that before. That doesn't help. Thanks for the suggestion though!
Click to expand...
Click to collapse
Show me a logcat!
I was running dark 1.01, which has 160dpi default and sort of got used to it.
I moved to 27, yet using LCD density app, it won't stick to 160 on reboot
Anyone know how to get it to stay at 160, while dark is getting updated?
Thanks
Amd4life said:
I was running dark 1.01, which has 160dpi default and sort of got used to it.
I moved to 27, yet using LCD density app, it won't stick to 160 on reboot
Anyone know how to get it to stay at 160, while dark is getting updated?
Thanks
Click to expand...
Click to collapse
It will only stick if you use ROM Toolbox.
Or change it in the build prop.
thanks, that program did the trick
Mimis_69 said:
It will only stick if you use ROM Toolbox.
Click to expand...
Click to collapse
Can the DPI be changed on the fly or does it require a reboot. I'm on the same ROM as OP and love it for browsing but it also makes some apps funky so itd be sweet to be able to change on the fly.
regP said:
Can the DPI be changed on the fly or does it require a reboot. I'm on the same ROM as OP and love it for browsing but it also makes some apps funky so itd be sweet to be able to change on the fly.
Click to expand...
Click to collapse
i've used one called LCD Resolution and when it changed it, it didnt do a "full" reboot; but a quick "system restart" . thats how i update my market apps. it's a really quick restart too. just be sure to turn wifi off after it restarts and then back on. it doesnt stick for some reason.
edit: not too sure if it works on ics
Hi everyone!
So, let's suppose that we have a rooted LG G3 (done with the current rooting methods), running stock ROM. Because I always like to cramp as many widgets on the home screen as possible, I want to change the DPI density of the screen (usually 3-rd party launchers allow you to only rescale the shortcuts, but not the widgets). We coud use the Texdroider app from the Play store, but it changes the DPI globally, so I'm worried it might harm the phone... Another way would be to install Xposed Framework - but can it be installed already safely at this point?
Of course ruining the stock Launcher by changing the DPI is not a problem, as I always use some 3-rd party Launchers that can handle layouts more flexibly
I'm also interested in changing LCD density on G3.
Has anyone done it?
Use Per-App Modules via XPOSED to change individual app DPI
radicalisto said:
Use Per-App Modules via XPOSED to change individual app DPI
Click to expand...
Click to collapse
Tnx, but I was thinking on global change. On my old GS2 it was matter of simply editing build.prop file.
My setting was 182 which was great. But I remember that if you over do it, phone will not boot and without nandroid backup it is quite risky.
LittleCannon said:
Tnx, but I was thinking on global change. On my old GS2 it was matter of simply editing build.prop file.
My setting was 182 which was great. But I remember that if you over do it, phone will not boot and without nandroid backup it is quite risky.
Click to expand...
Click to collapse
Use Textroid - You can use Build.Prop it'll work fine, just go no lower than around 400 or you will run into issues (for the record stock is 650)
radicalisto said:
Use Textroid - You can use Build.Prop it'll work fine, just go no lower than around 400 or you will run into issues (for the record stock is 650)
Click to expand...
Click to collapse
Actually 640 is default.
Anyway, 530 is the lowest value. Any below that and apps will start to FC.
Pitty, because on 450 screen is amazing!
LittleCannon said:
Actually 640 is default.
Anyway, 530 is the lowest value. Any below that and apps will start to FC.
Pitty, because on 450 screen is amazing!
Click to expand...
Click to collapse
I went to 480 and lost icons (they became little green androids) I had to set back to 650 for default in order for it to show properly again.
radicalisto said:
I went to 480 and lost icons (they became little green androids) I had to set back to 650 for default in order for it to show properly again.
Click to expand...
Click to collapse
Exactly the same. On 530 icons are still normal.
LittleCannon said:
Exactly the same. On 530 icons are still normal.
Click to expand...
Click to collapse
I'll give 530 a shot and see. Cheers.
radicalisto said:
I'll give 530 a shot and see. Cheers.
Click to expand...
Click to collapse
It is not much as I expected, but still it is better then stock density.
It's a keeper.
changed it to 580 and its bootlooping now. any help?
well...this is kinda roundabout so it works and I'm not complaining...I disabled or removed all of my AT&T apps and the useless LG ones...so I set my dpi to 450 and changed the per app dpi to 530 for the lg apps...problem solves...especially since I barely use the lg apps.
sjavvaji said:
well...this is kinda roundabout so it works and I'm not complaining...I disabled or removed all of my AT&T apps and the useless LG ones...so I set my dpi to 450 and changed the per app dpi to 530 for the lg apps...problem solves...especially since I barely use the lg apps.
Click to expand...
Click to collapse
Could you provide a screen capture to see the difference??
I'm thinking about doing it...
Thanks
nxym said:
changed it to 580 and its bootlooping now. any help?
Click to expand...
Click to collapse
I did the same thing and I'm stuck on this wretched infinite boot loop. Did you get any help on this if so can you please post the fix to your woes?
EDIT: So I tried to use the built-in factory reset ... nothing doing. STILL boot looping. I'm wondering if I should start panicking now? haha
kobbz said:
I did the same thing and I'm stuck on this wretched infinite boot loop. Did you get any help on this if so can you please post the fix to your woes?
EDIT: So I tried to use the built-in factory reset ... nothing doing. STILL boot looping. I'm wondering if I should start panicking now? haha
Click to expand...
Click to collapse
i had to flash the kdz image and get it back to stock.
has anyone been able to change their desity to about 400 to 440 and still use the LG apps, I changed mine to 480 and all my apps like phone/messing apps stopped working?
dkotoric said:
has anyone been able to change their desity to about 400 to 440 and still use the LG apps, I changed mine to 480 and all my apps like phone/messing apps stopped working?
Click to expand...
Click to collapse
LG apps can't go below 530 DPI. You'll need to individually them to 530 or higher to keep them from crashing.
Sent from my LG-D851 using Tapatalk
partylikeaninjastar said:
LG apps can't go below 530 DPI. You'll need to individually them to 530 or higher to keep them from crashing.
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
How do i individualy change them
Sent from my LG G3
dkotoric said:
How do i individualy change them
Sent from my LG G3
Click to expand...
Click to collapse
Use the Xposed Framework with the module "App Settings".
Batfink33 said:
Use the Xposed Framework with the module "App Settings".
Click to expand...
Click to collapse
Im sorry I have been using cayanogen mod for to long how and where do i get that
Sent from my LG G3
Hi,
I have rooted and loaded OxygenOS 3.2.2 stock full rom.
If I add the density line in build.prop, it doesn't change the DPI.
Please see attached screenshot from edited build.prop.
If I change DPI using the toolkit for oneplus 3 found here at Xda, the DPI is changed.
But I get some graphical issues. See attached images.
In one image, as you can see, the editors choice icon gets very big.
In one, the pictures in price spy all are zoomed in by default (and can't be zoomed out.
1) Why can't I change DPI just by editing build.prop?
2) How can I fix the graphical issues after I've changed DPI (using toolkit)? (I'm guessing that I will have the same issue if succeeding to change DPI using build.prop?)
View attachment 3844983
View attachment 3844984
View attachment 3844985
Use "le dpi changer" app its working for me . build.prop cause problem to me too try app
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
Use "le dpi changer" app its working for me . build.prop cause problem to me too try app
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Sorry. But it doesn't work. None of the options in the app.
The only thing working is to change DPI with Oneplus 3 Toolkit. But then I get the graphical issues.
Sent from Oneplus 3
mikjo243 said:
Sorry. But it doesn't work. None of the options in the app.
The only thing working is to change DPI with Oneplus 3 Toolkit. But then I get the graphical issues.
Sent from Oneplus 3
Click to expand...
Click to collapse
But it worked for me make sure you granted it and click " Edit build.prop " button in le dpi changer app and it will tell you to reboot
Sent from my ONEPLUS A3003 using Tapatalk
HIshan Pavidu said:
But it worked for me make surr you granted it and click build.prop button in le dpi changer app and it will tell you to reboot
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
Yes I granted it.
And no, build.prop button doesn't work either. It DOES edit the build.prop. But dpi isn't changed...
Sent from Oneplus 3
mikjo243 said:
Yes I granted it.
And no, build.prop button doesn't work either. It DOES edit the build.prop. But dpi isn't changed...
Sent from Oneplus 3
Click to expand...
Click to collapse
Weird
Sent from my ONEPLUS A3003 using Tapatalk
Change DPI issue.
What are you guys using an app for? just open up Terminal Emulator and run:
su
wm density 420
(You can change the value to whatever, higher makes the DPI less)
DonaldKerabatsos said:
What are you guys using an app for? just open up Terminal Emulator and run:
su
wm density 420
(You can change the value to whatever, higher makes the DPI less)
Click to expand...
Click to collapse
Sure. But it should be able to change in build.prop file.
But the issue is the graphic examples above. Please see them.
Sent from Oneplus 3
I have not noticed any issues, is it possible some values are just not quite right for the actual screen?
right now my DPI is set to 400 and my display looks great.
DonaldKerabatsos said:
I have not noticed any issues, is it possible some values are just not quite right for the actual screen?
right now my DPI is set to 400 and my display looks great.
Click to expand...
Click to collapse
I've tried 400 also.
Please check an app in play store that is editors choice, and submit a screenshot.
Do you have Oneplus 3?
Sent from Oneplus 3
Of course I have the OP3! its pretty awesome, sorry I will update my profile today.
Thanks for the suggestion, I will consider it if my current value becomes an issue for me. This forum is a great wealth of knowledge and I thank everyone here.
:good:
DonaldKerabatsos said:
Of course I have the OP3! its pretty awesome, sorry I will update my profile today.
Thanks for the suggestion, I will consider it if my current value becomes an issue for me. This forum is a great wealth of knowledge and I thank everyone here.
:good:
Click to expand...
Click to collapse
Please check the first image in my post above. Regarding play store. Don't you have the same?
Sent from Oneplus 3
I checked it, yeah not having that issue honestly.
DonaldKerabatsos said:
I checked it, yeah not having that issue honestly.
Click to expand...
Click to collapse
That's really strange. Guess I have to try your way of changing dpi.
Sent from Oneplus 3
Try it and see, I am not trying to troll you at all honestly, let me know how it works out!
I have had my DPI at 400 via this method for about two weeks now and noticed no aberrations of any kind.
BTW, I am on stock OOS with all the updates, rooted, TWRP, Xposed framework installed.
Tried your way now. Both 420 and 400. Still the same issue. So strange.
Is it possible that something got ****ed up when trying this, the toolkit, le dpi changer, and textdroid for changing dpi?
Sent from Oneplus 3
If You have used this Toolkit:
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
then you used this method:
adb shell wm density "value"
try this:
adb shell wm size reset
adb shell wm density reset
or just in the toolkit choose reset dpi in the DPI changing menu
then reboot and use le dpi changer with the build.prop option
I'm using this for some time and no glitches
Always reboot after changing the build.prop file
difference said:
Tried your way now. Both 420 and 400. Still the same issue. So strange.
Is it possible that something got ****ed up when trying this, the toolkit, le dpi changer, and textdroid for changing dpi?
Sent from Oneplus 3
Click to expand...
Click to collapse
I'm using Resurrection custom rom and under display setting can change LCD density 320,360,400,440,480,520,560 and default is 480dpi. A message prompt "Some apps may not function at non-standard DPI" so I assume the standard value should be 480dpi.
I'm on stock with latest update, TWRP, and root. I use 3C Toolbox to edit build.prop adding the line ro.sf.lcd_density and a value of 401. I would try one app at a time to change the DPI with.
sipek said:
If You have used this Toolkit:
http://forum.xda-developers.com/oneplus-3/development/toolkit-oneplus-3-toolkit-unlock-t3398799
then you used this method:
adb shell wm density "value"
try this:
adb shell wm size reset
adb shell wm density reset
or just in the toolkit choose reset dpi in the DPI changing menu
then reboot and use le dpi changer with the build.prop option
I'm using this for some time and no glitches
Always reboot after changing the build.prop file
Click to expand...
Click to collapse
Cool. Can I just put in this in terminal window in the phone?
wm size reset
wm density reset
?
Or do I have to do it from adb shell?
Sent from Oneplus 3