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
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
Sorry if this has already been posted before but I came across it and never heard about it before. It changes your screen size like you were changing the resolution on a monitor. I went from 240 default down to 200 and it seems like a perfect size without making everything too small
https://market.android.com/details?id=lv.n3o.lcddensity&feature=search_result
you can also change it from the build.prop...knowing how to edit it is a must for any android user imo
ugothakd said:
you can also change it from the build.prop...knowing how to edit it is a must for any android user imo
Click to expand...
Click to collapse
I really never knew about this. To me at least having the smaller scale size looks and feels better than stock. How come we dont see rom/theme releases with this mod?
I think for Developers personal preferences, also I'm not quite sure they could change the build.prop with a theme, but in the case of a Rom I believe that keeping it on a basic level works out in the best for the general population, but also allows those who are more prone to making changes on their own to go ahead and attempt it for themselves.
Thanks for the thread though man, I've been iffy about whether this app would work for the Epic, I truly appreciate it.
Yep build.prop is the way to go.
I don't think I could go back to stock density. 172 looks excellent.
dpesnt the dialer get offset to bottom left when changing the density or is that only on themed dialers?
Sent from my SPH-D700 using xda premium
JohnCorleone said:
dpesnt the dialer get offset to bottom left when changing the density or is that only on themed dialers?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yessir it does.
DialerOne and GoDialer are fantastic as a replacement.
darkierawr said:
Yep build.prop is the way to go.
I don't think I could go back to stock density. 172 looks excellent.
Click to expand...
Click to collapse
Omg Darkie I love you lol. 172 looks amazing.:O
Sent from my Epic 4G
darkierawr said:
Yessir it does.
DialerOne and GoDialer are fantastic as a replacement.
Click to expand...
Click to collapse
Thanks for the heads up on the alterrnate dialers darkie! "Thanks" clicked.
Sent from my SPH-D700 using xda premium
Freakin killer app.....
Thanx man
Very cool mod!...I'm not sure I can go as low as 172, but even a minor adjustment to 200 really makes a wonderful difference...I especially like the overall effect to the launcher.
One drawback though...I'm going to have to retrain my muscle memory because of the slight change in location of various things.
It'll be interesting to see if there's any way to make a minor adjustment to the default dialer so it can properly scale...Also, it looks like I'm going to have to take a look at the Wired Tether app because it looks fairly odd.
.
Edit: I solved the wierd layout in Wired Tether app using appleflap's suggestion in this thread to turn off Compatibility Mode...However, I'm on SRF 1.2, so I did it through Settings-->Lockscreen Parts-->General.
.
OK...After a data wipe of the Market app, I just noticed this density change caused the Market to identify 21 of the 102 apps I currently have installed as not compatible...Bummer.
.
xanthinealkaloid said:
OK...After a data wipe of the Market app, I just noticed this density change caused the Market to identify 21 of the 102 apps I currently have installed as not compatible...Bummer.
.
Click to expand...
Click to collapse
Sorry for not giving you the heads up.
With my density so low NOTHING works with the new ****ty market. I reverted back to the older market. Where everything is compatible.
What is the pixel density of the Evo 3D? (trying to mimic that if I can)
Also, does this app cause the New market to FC or something?
Hmmm, so does anyone know the step process to changing the density with my phone total crashing with fc? ?
place witty Epic comment here
darkierawr said:
Sorry for not giving you the heads up.
With my density so low NOTHING works with the new ****ty market. I reverted back to the older market. Where everything is compatible.
Click to expand...
Click to collapse
+1
I set my density to 180...still rocking the 2.3.6 market
|| Acer || said:
What is the pixel density of the Evo 3D? (trying to mimic that if I can)
Also, does this app cause the New market to FC or something?
Click to expand...
Click to collapse
No...The issue is with the version 3x market because there's a new compatibility check in place which references the LCD density value, so this change can cause previously installed apps to appear incompatible according the the new market removing them from your installed list
.
thatdudepoops said:
Hmmm, so does anyone know the step process to changing the density with my phone total crashing with fc? ?
place witty Epic comment here
Click to expand...
Click to collapse
Are you using the stock TouchWiz launcher?...I've read it can be problematic when doing this mod.
.
Well, I'm on my way to fixing the compressed dialpad...I did the widths to see if the pngs would stretch without looking like a 1960's color TV.
I'm gonna finish this up later, but now it's time for a RedBull break.
.
xanthinealkaloid said:
Are you using the stock TouchWiz launcher?...I've read it can be problematic when doing this mod.
.
Click to expand...
Click to collapse
I'm using zeam....
place witty Epic comment here
Has anyone done this? I just set my density nd it looks gorgeous. The Samsung keyboard started crashing Instantly. Not a huge deal I switched to SwiftKey tablet and everything is okay. However here and there galls seems to crash now. This is keeping talk from staying logged in which is a problem. Has anyone else attempted the same thing and seeing different results? As much as I love the added screen real estate (especially the split with the keyboard and aide ide visibility) its not a better tradeoff to losing talk. Unfortunately logcat reveals no direct insight into what is causing the crash only that the process is stopping. Any advice is welcome, as I'd like to keep the rest change.. I set both density values to 240.
Sent from my SPH-L900 using Tapatalk 2
Sess said:
Has anyone done this? I just set my density nd it looks gorgeous. The Samsung keyboard started crashing Instantly. Not a huge deal I switched to SwiftKey tablet and everything is okay. However here and there galls seems to crash now. This is keeping talk from staying logged in which is a problem. Has anyone else attempted the same thing and seeing different results? As much as I love the added screen real estate (especially the split with the keyboard and aide ide visibility) its not a better tradeoff to losing talk. Unfortunately logcat reveals no direct insight into what is causing the crash only that the process is stopping. Any advice is welcome, as I'd like to keep the rest change.. I set both density values to 240.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
reboot into recovery and wipe cache and dalvik...............im having no fc issues and im running at 240 as well. g-talk works fine for me as well.
t3project said:
reboot into recovery and wipe cache and dalvik...............im having no fc issues and im running at 320 as well. g-talk works fine for me as well.
Click to expand...
Click to collapse
Did you mean you're running at 240 as well? 320 is default.
Blankrubber said:
Did you mean you're running at 240 as well? 320 is default.
Click to expand...
Click to collapse
yes, typo..........running at 240, 280 is nice as well
t3project said:
yes, typo..........running at 240, 280 is nice as well
Click to expand...
Click to collapse
Haha, okay. I switched to 240 and haven't had problems yet, other than the funky sized dialer and such.
Blankrubber said:
Haha, okay. I switched to 240 and haven't had problems yet, other than the funky sized dialer and such.
Click to expand...
Click to collapse
yea, any of the stock apps need smali edits to fit the screens with different dpi
Blankrubber said:
Haha, okay. I switched to 240 and haven't had problems yet, other than the funky sized dialer and such.
Click to expand...
Click to collapse
This fixed my dialer problem looks good! im on 240.
https://play.google.com/store/apps/...251bGwsMSwxLDEsImNvbS5tb2Rvb2h1dC5kaWFsZXIiXQ..
I also flashed the 4.2 camera witch was full screen but FC because of the 360 view thing. But im going to flash this tonight and see if its fixed.
http://forum.xda-developers.com/showthread.php?t=1996205
---------- Post added at 03:05 PM ---------- Previous post was at 03:03 PM ----------
t3project said:
yea, any of the stock apps need smali edits to fit the screens with different dpi
Click to expand...
Click to collapse
Is this hard? Maybe link me and i can try it or hopefully someone can fix it.
t3project said:
reboot into recovery and wipe cache and dalvik...............im having no fc issues and im running at 240 as well. g-talk works fine for me as well.
Click to expand...
Click to collapse
Ill give it a try. Good to hear you have no problems. There is still hope
Sent from my SPH-L900 using Tapatalk 2
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