I've written a software that edit build.prop but it seems that's not enough since the resolution does not change (but i've installed LCD density changer before )
- dalvik.vm.heapsize
- ro.sf.lcd_density
Looking for some informations, others apps use busybox to tweak this parameters without modifying build.prop. Where can i found some help about thoses points ?
Any comments would be helpfull !
Thx
Did you try doing a reboot after editing it? I know the LCD density app does a hot reboot to take effect
Sent from my Incredible using XDA App
've rebooted but the params are clearly not taken into account.
Maybe a previous installation of LCD density have tweaked the system directly
using a script or variable that override build.conf.
I'm a beginner trying to offer all thoses services in a widget but this is a long way
Related
So I have been using Root Explorer to adjust my LCD Density but recently my adjustments haven't been taking affect. After making a change to the build.prop, I reboot my phone. No change has taken affect. I can go back in to the build.prop file and verify I have changed the value. Even when I use the LCD Density app it shows that my LCD density is 190 (screen resolution really isn't 190). I then set the density with the app and the resolution finally is at 190. Anybody else having this issue? I just hate having to readjust the LCD density after every reboot.
Thanks
Sent from my HTC Vision using XDA App
Go into settings (LCD Density app) and set it to "Save as System density" then apply and then click the test button
Have been using LCD Density changer from 240 to 220 dpi on the gorgeous super AMOLED plus screen.
Only recently I realised that in the Android Market the install/download button does not appear when this resolution is changed from default. If I were to set to 240, it is OK. However this does not affect all apps. Searching apps is fine, just not able to install/download.
Now I have to change to default 240 to install certain apps then change to desired resolution.
Anyone knows how to solve this?
In short, there's no permanent fix that I now of, but just a warning:
Use an app like LCD Density Changer in the Market so you can safely toggle the resolution without getting stuck and needing to wipe your data
If you set the resolution in the build.prop below 240 it not only removes the download/install from the page in the Market but with the latest Market version it also gives a message highlighted in bright yellow that the application in not compatible with the device. I also found that even if I changed the build.prop line back to 240 and rebooted I was stuck without access to the majority of the apps I use. I had to wipe data to fix the problem.
What I'm doing is leaving my resolution at 210 and once a week switching back to 240 to update any apps that need updating. Occasionally I have to switch the resolution to download a new app as well. It's not exactly convenient, but it works.
I had changed my lcd density to 380 to get a better looking screen, but I noticed my camera was all messed up.
So I put my density back to 480, and now I am unable to download a lot of common apps from the play store!
For example...Weather Bug, Candy Crush, etc....
I am on T-Mobile variant.
I only changed this line in the build prop: ro.sf.lcd_density=480
Am I forgetting to do something else?
Any help would be much appreciated!
Well first of all, use the textdroider_dpi app to change the dpi instead of changing the prop file.
I believe that's the proper method as some other files are affected together. Experts correct me if I'm wrong.
And when the camera screws up, install Xposed and use the module "App settings" to change the dpi of only camera to stock. That will do the trick.
Clear data etc from market and try again.
Sent from my LG-D802 using xda app-developers app
Is here a someone who can change DPI from stock to 460 or 480 for a stock camera and for TW? I really like lower DPI on this device and if I did it mentioned apps aren´t usable
Or small advice how can I make it will be also good. (which apk tools I need, which line I must edit inside apk, ......., ) I will try to do it myself.
Thanks
So I rooted and wanted to set the screen PPI/DPI to the actual calculated value of 400-403 (Motorola says it's 403 but the actual calculated value is 400.53). Problem is, it screws up the icons in the camera app and Google Search bar on the homecreen. I've attached screenshots to show you what I mean, but I'm sure most of you are aware of this happening as it tends to when you lower the DPI/PPI. The screens of the screwed icons are at 403 DPI/PPI and the screens where the icons are fine are at the default 480 DPI/PPI.
Does anyone know of a way to fix this? Or is it just something that can't be helped at lower DPI/PPI values?
How did you change your DPI? I read that the adb method alone is not enough. You must change the value on build.prop too. Making the two things may work.
update app camera via Google Play Store que resolve!!!!
Or use appsetting to change dpi in apps.
Skickat från min XT1562 via Tapatalk
I have this exact same issue. I changed DPI to 400 using adb. I also have profile picture thumbnails messed up in both Viber and Whatsapp. So far I haven't found any solutions. Changing DPI to 360 works for the camera, but not for thumbnails in Viber or whatsapp.
I'm using 440. Stock is 480. If you in increments of 40 it works. Try 400
ToYeD said:
So I rooted and wanted to set the screen PPI/DPI to the actual calculated value of 400-403 (Motorola says it's 403 but the actual calculated value is 400.53). Problem is, it screws up the icons in the camera app and Google Search bar on the homecreen.
Does anyone know of a way to fix this? Or is it just something that can't be helped at lower DPI/PPI values?
Click to expand...
Click to collapse
Mother of all ad blocking ???
dpacmittal said:
I have this exact same issue. I changed DPI to 400 using adb. I also have profile picture thumbnails messed up in both Viber and Whatsapp. So far I haven't found any solutions. Changing DPI to 360 works for the camera, but not for thumbnails in Viber or whatsapp.
Click to expand...
Click to collapse
PPI is a hardware component i.e how many pixels are there in a inch of screen.
DPI is a software component in broad terms i.e how much area a software is allocated. so changing it to too low will have bad effects.
change the DPI to 430-440 it looks nice and it will solve your problem.
---------- Post added at 06:29 AM ---------- Previous post was at 06:23 AM ----------
LuizHenrique91 said:
How did you change your DPI? I read that the adb method alone is not enough. You must change the value on build.prop too. Making the two things may work.
Click to expand...
Click to collapse
it would be easy if you are rooted. simply go to /system/build.prop and look for ''ro.sf.lcd_density=480'' and change it accordingly.
ToYeD said:
(Motorola says it's 403 but the actual calculated value is 400.53).
Click to expand...
Click to collapse
It's 403,5.... The screen is not exactly 5.5 inches
Sent from my XT1562 using Tapatalk
Do what I did, install the AppSettings via Xposed, choose the DPI you want normally in build.prop, In the AppSettings settings, select Motorola Camera and place it in the DPI 480 (stock), so I use here without problems.