Related
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
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 All,
Does anyone know of a good DPI for the Find 7a? the stock 480 is a bit big for me.
I now DPI is a subjective thing, but I don't want to pick one where apps don't run properly.
sniper-joe said:
Hi All,
Does anyone know of a good DPI for the Find 7a? the stock 480 is a bit big for me.
I now DPI is a subjective thing, but I don't want to pick one where apps don't run properly.
Click to expand...
Click to collapse
320 is probably way too low, and that's the next valid step down.
(In theory, 400 was added by Android 4.4, however while Android supports it, the Play Store does NOT so you'll encounter lots of app compatbility issues - see the various complaints stemming from the Z Ultra GPe running a 400 DPI configuration.)
Entropy512 said:
320 is probably way too low, and that's the next valid step down.
(In theory, 400 was added by Android 4.4, however while Android supports it, the Play Store does NOT so you'll encounter lots of app compatbility issues - see the various complaints stemming from the Z Ultra GPe running a 400 DPI configuration.)
Click to expand...
Click to collapse
I have just rebooted using 320 and it's perfect! Everything works fine!
By the way Entropy, do you have a find 7a? I have been following your work for a long time!
sniper-joe said:
I have just rebooted using 320 and it's perfect! Everything works fine!
By the way Entropy, do you have a find 7a? I have been following your work for a long time!
Click to expand...
Click to collapse
What app did you use to change DPI???
Stock rom or modded?
Mord0rr said:
What app did you use to change DPI???
Stock rom or modded?
Click to expand...
Click to collapse
The option to change the system DPI is built into Dirty Unicorns, however, I have used texdroider DPI app on stock roms, but sometimes stock ROMS throw a fit.
sniper-joe said:
The option to change the system DPI is built into Dirty Unicorns, however, I have used texdroider DPI app on stock roms, but sometimes stock ROMS throw a fit.
Click to expand...
Click to collapse
Ah!
That one i tried and it din`t work....
When I changed the DPI I ran somewhere around 400 and used a modified play store to get around the incompatible error. Then Google started updating the play store too much and the dev for the modified play store fell behind and I just went back to default DPI. When I find the thread I'll link it.
Find what? Who the heck is OPPO?
*edit*
http://forum.xda-developers.com/showthread.php?t=1839871
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
Hello!
I've been using Android N on my 5x for a while, but I missed Xposed too much and snapchat started to refuse cooperating, so I downgraded to Marshmallow.
The only thing I miss from Nougat is the DPI setting, I've gotten used to having it smaller on N. So my question is, what is the DPI set to when you choose the "Smallest" (leftmost) option in the Display Size setting on Android N? Googling turned up nothing, and I need to know this number so I can manually set it on Marshmallow.
Thanks in advance!
Edit build.prop
ro.sf.lcd_density=420
D00 said:
Edit build.prop
ro.sf.lcd_density=420
Click to expand...
Click to collapse
That's the default density. For future reference to anyone who might find this thread, the number I was looking for was 356.
xdpirate said:
That's the default density. For future reference to anyone who might find this thread, the number I was looking for was 356.
Click to expand...
Click to collapse
Thanks, can I set it any smaller without any issues?