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
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.
Hi all,
My new phone did not survive a single day without (towel-)root. So after getting root, I was thinking about changing DPI.
default in /system/build.prop is 480. I changed it to 360 and 420, both seems fine for the GS5. As a scale referenced I used values from http://forum.xda-developers.com/galaxy-nexus/general/info-official-galaxy-nexus-lcd-density-t1392089 - my Galaxy Nexus is running at 246 just fine.
But sadly, the stock lock screen is now shifted left. Any idea how I can replace the stock lock screen with another fingerprint-ready lock screen? A lock screen with 4x4 pattern would also do.
Thanks in advance.
PS: If I have time, I will make a thread similar to the linked above.
Is the camera workin properly on 360 and 420? thanks and the phone keypad?
I may be wrong but as far as i know you have to edit SystemUI for the lockscreen to look correct, or you can use app settings from xposed to change SystemUI back to 480 but that changes more than the lockscreen. As for camera and keypad, those need to be changed back to 480 in app settings, i wouldnt say its required but its not going to work very well on anything but stock dpi, i personally run 320.
Sent from my SM-G900A using Tapatalk
So I just bought my brand new Note 4 (SM-N910W8) and of course the first thing I did was root it and install xposed framework. Everything works fine, I always change the DPI on my Note phones because I like to make use of the extra screen real estate. This worked fine as well, that is until I installed my Sview (S View cover) on it.
The sview window appears fine in the new DPI but across the bottom portion there is a black bar (the screen is off on the bottom third of the window).
I tried using the Xposed app settings mod to change the sview portion of the UI back to 640 DPI (the native resolution), but this didn't work!
has anyone else experienced this on the Note 4? any suggestions to make it work while having the rest of the phone in 480 DPI mode?
Helllpppp
Can you post a picture of what's exactly happening?
c_est_la_vie said:
So I just bought my brand new Note 4 (SM-N910W8) and of course the first thing I did was root it and install xposed framework. Everything works fine, I always change the DPI on my Note phones because I like to make use of the extra screen real estate. This worked fine as well, that is until I installed my Sview (S View cover) on it.
The sview window appears fine in the new DPI but across the bottom portion there is a black bar (the screen is off on the bottom third of the window).
I tried using the Xposed app settings mod to change the sview portion of the UI back to 640 DPI (the native resolution), but this didn't work!
has anyone else experienced this on the Note 4? any suggestions to make it work while having the rest of the phone in 480 DPI mode?
Helllpppp
Click to expand...
Click to collapse
I'm about to do the same
What new setting did you put for the dpi?
This seems to be the same problem with the lock screen and dpi settings. Unfortunately it seems like the dpi settings are baked into the system ui and cannot be modified unless dpi is changed for everything. If been there. Good luck
ravni said:
I'm about to do the same
What new setting did you put for the dpi?
Click to expand...
Click to collapse
I edited the build.prop to have a DPI of 480 instead of 640 (the native DPI).
It's the same thing that happens when you make the same change to the DPI on Note 3 with S-View covers as well.
I am still trying to figure a way to fix this, has anyone found anything new?
The Picture 1 shows what's happening to the Sviewcover. Picture 2 shows me tricking the phone into believing that the Cover is closed (by using a magnet).
I used Xposed App Settings to set the system DPI to 480 (from 640 stock). I set the Sviewcover.apk to 640 as well so the Sviewcover is not misaligned to the left side.
BUT here is the problem, there is a Black bar at the bottom half of the Sviewcover which renders it useless and ugly. The ONLY way I have found to fix this is NOT to alter the DPI for "Android System" and leaving it stock. That way the Sviewcover would show up perfectly without the black bars.
But that defeats the purpose of altering the DPI first place. Why can't samsung allow two zoom levels for user to choose so we can either choose big icons or more screen spaces?
there is a semi solution for this
usually people use rom toolbox to change the entire dpi.
first you must return the dpi to the normal 640 in rom toolbox
then in app settings Xposed change com.android.systemui dpi to 480
and then go to Android System (Android) and change the dpi back to 640
don't forget each time you must turn on the app setting and save after the change
this might effect some of the apps and show it in normal size but it will fix your problem
plus you can change any app's dpi to 480 from app settings later and make it small again.
c_est_la_vie said:
So I just bought my brand new Note 4 (SM-N910W8) and of course the first thing I did was root it and install xposed framework. Everything works fine, I always change the DPI on my Note phones because I like to make use of the extra screen real estate. This worked fine as well, that is until I installed my Sview (S View cover) on it.
The sview window appears fine in the new DPI but across the bottom portion there is a black bar (the screen is off on the bottom third of the window).
I tried using the Xposed app settings mod to change the sview portion of the UI back to 640 DPI (the native resolution), but this didn't work!
has anyone else experienced this on the Note 4? any suggestions to make it work while having the rest of the phone in 480 DPI mode?
Helllpppp
Click to expand...
Click to collapse
In app settings, as well as setting the DPI to 640 you also have to tick the box "apply res to widgets" If you don't, the widgets still render at the system DPI. You have to apply the 640 DPI to the com.android.keyguard (I think that's what it's called it's got keyguard in the name).
Yup, Batfink is right. I forgot about the apply to widget setting, bur when I finally applied it everything was good.
omid_freesky said:
there is a semi solution for this
usually people use rom toolbox to change the entire dpi.
first you must return the dpi to the normal 640 in rom toolbox
then in app settings Xposed change com.android.systemui dpi to 480
and then go to Android System (Android) and change the dpi back to 640
don't forget each time you must turn on the app setting and save after the change
this might effect some of the apps and show it in normal size but it will fix your problem
plus you can change any app's dpi to 480 from app settings later and make it small again.
Click to expand...
Click to collapse
This will make the main UI at 640DPI which defeats the purpose of changing the DPI first place.
---------- Post added at 03:19 PM ---------- Previous post was at 03:18 PM ----------
Applethrow said:
Yup, Batfink is right. I forgot about the apply to widget setting, bur when I finally applied it everything was good.
Click to expand...
Click to collapse
I checked "apply to widgets" for both Keyguard and Sviewcover but the Black bar is still present.
When I come to think of it, I only changed dpi for the system.ui process. Then set keyguard, camera, contacts etc to 640. Didn't touch Android System.
Applethrow said:
When I come to think of it, I only changed dpi for the system.ui process. Then set keyguard, camera, contacts etc to 640. Didn't touch Android System.
Click to expand...
Click to collapse
This is a semi-fix as you would have to alter the DPI for EVERY app to render at 480DPI but I guess this is the ONLY method at the moment :crying:
Yes, you are absolutely right. Just tried it and s-view window got a black bottom bar. Maybe I'll have switch to my wallet flip cover lol