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
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,
Before my S2 was rooted and loaded with EaglesBlood Netflix was working properly, but after that whenever I try to pull up the app with my phone it takes me to the android market and says that Netflix isn't compatible with my device.
Any thoughts on how I can solve this?
Thanks.
S0AMAZING said:
Hi everyone,
Before my S2 was rooted and loaded with EaglesBlood Netflix was working properly, but after that whenever I try to pull up the app with my phone it takes me to the android market and says that Netflix isn't compatible with my device.
Any thoughts on how I can solve this?
Thanks.
Click to expand...
Click to collapse
Are you running any apps that change the screen/lcd density? This will cause that to happen.
azsl1326 said:
Are you running any apps that change the screen/lcd density? This will cause that to happen.
Click to expand...
Click to collapse
This is the likely culprit.
ap77 said:
This is the likely culprit.
Click to expand...
Click to collapse
Know any workaround for this? Or do I have to set it back to normal whenever I want to get an app?
Fantasysage said:
Know any workaround for this? Or do I have to set it back to normal whenever I want to get an app?
Click to expand...
Click to collapse
revert back to 240 when finished installing, just go back to the density that you want. It will work after that. It seems the installer is checking up on screen resolution prior to installing/downloading.
zoth said:
revert back to 240 when finished installing, just go back to the density that you want. It will work after that. It seems the installer is checking up on screen resolution prior to installing/downloading.
Click to expand...
Click to collapse
Yep, this is the "solution." It's very odd that Google has decided to enforce a pixel density standard....
ap77 said:
Yep, this is the "solution." It's very odd that Google has decided to enforce a pixel density standard....
Click to expand...
Click to collapse
I know why be worried about the desity?
Maybe its because when you program for Android you set images and layout objects based on density and screen size if you want to make your app dynamic. Android pulls this information from the app and lays out the GUI based on what folders they layout objects are in.
Sent from my SGH-T989 using XDA App
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 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
make sure you have the lg drivers install. if u dont , head over www.lg.com - support - software and drivers - browser by product. v30 and ur carrier.
connect ur device and on ADB
use command
adb devices
this will tell u if ur devices is connect.
you will see a message like this
"list of devices attached"
"LG9Xxxxxxxxxxxxxxxxx device"
if nothing shows up. make sure u have the drivers install correctly and reboot ur pc.
next use this comand
adb shell wm density XXX
In X i choose 450 (i attached a pic as an example)
you choose the DPI number tha works for u.
460, 470 also work great. please share ur DPI # if it works.
enjoy
Which of the launchers is that one?
CHH2 said:
Which of the launchers is that one?
Click to expand...
Click to collapse
nova launcher
Have you noticed any wonkiness in any of the LG apps after changing dpi?
NeutronBomb said:
Have you noticed any wonkiness in any of the LG apps after changing dpi?
Click to expand...
Click to collapse
not at all. but i did notice that 450 is small and when i do 460,470. it doesnt become smaller. it actually gets bigger. so i believe the dpi is limited to 450 or something closer to. now everything looks shaper, better and u can see more in the screen.
right now im on 470 which for me 450 was to small.
i believe 470 should be around (430 real dpi). not sure why dpi is working this way at least is working.
eduardmc said:
not at all. but i did notice that 450 is small and when i do 460,470. it doesnt become smaller. it actually gets bigger. so i believe the dpi is limited to 450 or something closer to. now everything looks shaper, better and u can see more in the screen.
right now im on 470 which for me 450 was to small.
i believe 470 should be around (430 real dpi). not sure why dpi is working this way at least is working.
Click to expand...
Click to collapse
Anything is better than the default setting. Everything in the GUI is comically large the way it's set out of the box.
eduardmc said:
make sure you have the lg drivers install. if u dont , head over www.lg.com - support - software and drivers - browser by product. v30 and ur carrier.
connect ur device and on ADB
use command
adb devices
this will tell u if ur devices is connect.
you will see a message like this
"list of devices attached"
"LG9Xxxxxxxxxxxxxxxxx device"
if nothing shows up. make sure u have the drivers install correctly and reboot ur pc.
next use this comand
adb shell wm density XXX
In X i choose 450 (i attached a pic as an example)
you choose the DPI number tha works for u.
enjoy
Click to expand...
Click to collapse
Change DPI breaks AOD like on G6...?
Killua96 said:
Change DPI breaks AOD like on G6...?
Click to expand...
Click to collapse
Nope. it actually makes it look better (smaller and sharper)
eduardmc said:
Nope. it actually makes it look better (smaller and sharper)
Click to expand...
Click to collapse
Good, could you please add to the guide the tested DPI? In this way other users can be sure to use a correct value.
Thanks for the guide!
Full screen Youtube
I have successfully changed my DPI to 470. I just checked out a youtube video afterwards and noticed black bars on the sides when in full screen. I do not remember if these bars were there prior to changing my DPI. Does anyone know if the black bars are there by default due to the aspect ratio?
rlaxed311 said:
I have successfully changed my DPI to 470. I just checked out a youtube video afterwards and noticed black bars on the sides when in full screen. I do not remember if these bars were there prior to changing my DPI. Does anyone know if the black bars are there by default due to the aspect ratio?
Click to expand...
Click to collapse
lol black bars have always been there. no luck on the zoom full screen function of the S8. I wish lg would add this in the future
I changed my DPI to 450, and it looks good, perhaps just a wee bit tiny. What's the stock DPI, so I can play around and find some middle ground?
NotATreoFan said:
I changed my DPI to 450, and it looks good, perhaps just a wee bit tiny. What's the stock DPI, so I can play around and find some middle ground?
Click to expand...
Click to collapse
switch to 470 or 480. it will make things a little bigger. not sure why dpi is working this way. if u want to reset it to stock. just go into display size and move the slider
eduardmc said:
switch to 470 or 480. it will make things a little bigger. not sure why dpi is working this way. if u want to reset it to stock. just go into display size and move the slider
Click to expand...
Click to collapse
Lower amount=smaller text etc. It always worked this way. Other way to reset is to send command with argument reset(adb shell wm density reset)
Sent from my LGE V30 using XDA Labs
Minto107 said:
Other way to reset is to send command with argument reset(adb shell wm density reset)
Sent from my LGE V30 using XDA Labs
Click to expand...
Click to collapse
That ADB command is still on the carrier branded versions of this phone?
You've tested this?
ChazzMatt said:
That ADB command is still on the carrier branded versions of this phone?
You've tested this?
Click to expand...
Click to collapse
I didn't test it but it should work regardless of software, it's more core dependent as it's in android at least since kitkat days
Sent from Galaxy Tab A10 with 7300 battery ))
Minto107 said:
I didn't test it but it should work regardless of software, it's more core dependent as it's in android at least since kitkat days
Sent from Galaxy Tab A10 with 7300 battery ))
Click to expand...
Click to collapse
LG removed most of the ADB commands on the carrier branded models.
ChazzMatt said:
LG removed most of the ADB commands on the carrier branded models.
Click to expand...
Click to collapse
Good to know. I live outside US so I always get international variants. I never understood that you have 30 variants of each phone just because stupid carriers. International supports all bands
Sent from Galaxy Tab A10 with 7300 battery ))
Minto107 said:
Good to know. I live outside US so I always get international variants. I never understood that you have 30 variants of each phone just because stupid carriers. International supports all bands
Sent from Galaxy Tab A10 with 7300 battery ))
Click to expand...
Click to collapse
Right now, only carrier branded versions released. Official carrier unlocked versions US998 (North America) and H930 (Europe) will reportedly be released end of October. Sometime after that will be placed on LG Developer Bootloader Unlock list.
ChazzMatt said:
Right now, only carrier branded versions released. Official carrier unlocked versions US998 (North America) and H930 (Europe) will reportedly be released end of October. Sometime after that will be placed on LG Developer Bootloader Unlock list.
Click to expand...
Click to collapse
Good to know. Thought it's already out. I went to store yesterday to see V30 but they said it's coming 2nd November. Pure curiosity, no more LG for me
Sent from Galaxy Tab A10 with 7300 battery ))