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.
Related
Okay, great device... but really annoying that most apps don't make use of the extra real estate on the screen. Most apps are just blown up versions of for example the Galaxy S2 apps. Meaning most apps are the same but 5.3/4.2 = 1.26 times bigger That's at least a pity The contacts app displays the same amount of contacts on a screen as the Galaxy S2 or S but... with a 1.26 x bigger font (compared to the S2) and 5.3/4=1.33 (lol) x bigger font compared to the Galaxy S
Fortunately there seems to be a setting in the accessibility settings that allows the user to decrease the font in some stock apps. Unfortunately this doesn't work. At least not on my device. Anyone got this working?
And yes, ICS would be a great improvement for such a big screen device.
Is that possible to set another density for the device (maybe you have to root it first)?
siamchen said:
Is that possible to set another density for the device (maybe you have to root it first)?
Click to expand...
Click to collapse
You'd have to root it first, and then push the density down. Not ideal, as some apps then run in a box on the screen, but it does make for smaller fonts, and you can cram more widgets on the screen etc.
I run my HD2 at 160, but then again I have had my eyes lasered!
Root
Go to system/build.prop
Open in editor
change the value of lcd from 240 to 192
See the difference.
U can always go back
All apps wont be scaled to the new lcd value.
eg: TW in sgsII does not scale.
However i always used this value and did not use TW.
Looks very interesting but I'm afraid that I'm not s pro
Sent from my HTC Desire S using XDA App
density change doesn't address the question
Hey ho wait..... this wasn't the question. So does the fontsize changing option work for you guys?
appelflap said:
Hey ho wait..... this wasn't the question. So does the fontsize changing option work for you guys?
Click to expand...
Click to collapse
I think change the font size setting in gingerbread is for display text in text editor or web browser instead of the launcher and most other application as they have their own fixed font size. You cannot do anything to those applications as they has been programmed that way.
siamchen said:
I think change the font size setting in gingerbread is for display text in text editor or web browser instead of the launcher and most other application as they have their own fixed font size. You cannot do anything to those applications as they has been programmed that way.
Click to expand...
Click to collapse
With stock apps I mean the Samsung apps. In the accessibility settings there's an option to change the font size "in the following applications: S planner, Email, Contacts and Messaging" (as stated in the accessibility settings)
Unfortunately this setting doesn't work on my jk4 rom. Maybe others have luck on other roms. Seems like a very usuable option for the note.
drgopoos said:
Root
Go to system/build.prop
Open in editor
change the value of lcd from 240 to 192
See the difference.
U can always go back
All apps wont be scaled to the new lcd value.
eg: TW in sgsII does not scale.
However i always used this value and did not use TW.
Click to expand...
Click to collapse
My lcd.density (or so) was set to 320 on stock!
I changed it to 280 and the system looks now nicer!
Actually, I measured the tab and my calculation would be around 270-280 dpi.
Has anybody other/better data?
By the way, 1st problem after changing lcd density is in S Memo! Background seem to have a fixed 'smaller size' which are then placed wrongly
Another impact: The email-widget does not fit on screen any more (using Launcher Pro) ... Hope in ICS they will fix some of those screen size problems!
fscherz said:
My lcd.density (or so) was set to 320 on stock!
I changed it to 280 and the system looks now nicer!
Actually, I measured the tab and my calculation would be around 270-280 dpi.
Has anybody other/better data?
By the way, 1st problem after changing lcd density is in S Memo! Background seem to have a fixed 'smaller size' which are then placed wrongly
Another impact: The email-widget does not fit on screen any more (using Launcher Pro) ... Hope in ICS they will fix some of those screen size problems!
Click to expand...
Click to collapse
I didn't try it myself yet but I bet it will give a whole lot of trouble with almost every Samsung app on this xhdpi device. Like HTC, they exactly target the screen for which they write software. Unlike most android apps in the market, targeting screens with different specs isn't important. Scaling isn't a requirement for these stock apps. ICS will not solve the problem, because it is still up to the developer which screens will be targeted.
Anyway, back to the original question, I think it is safe to conclude that the font setting doesn't work for anyone. So it is a bug.
I have rooted my phone and tried to use Spare Parts to change the font size to Extremely Small. It works instantly and make the application much more usable. But, there is a problem: The font size will change back to Normal after few hours by itself. Anyone has the same problem?
siamchen said:
I have rooted my phone and tried to use Spare Parts to change the font size to Extremely Small. It works instantly and make the application much more usable. But, there is a problem: The font size will change back to Normal after few hours by itself. Anyone has the same problem?
Click to expand...
Click to collapse
that method also won't scale down graphics to match the smaller fonts. LCD Density Changer accomplishes that and works well.
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
Has anyone with a rooted device tried modifying the LCD density setting in build.prop? What values looked best? Thinking about rooting my phone just for this purpose.
i changed mine with textdroider_dpi app. Mine is currently set on 480
I set mine to 520 a few times but there are some issues with it. Every now and then my phone would go to a full black screen after boot up and before the lock screen and stay there. Lucky I have a full backup before and after I installed xposed. Having the backup I only had to restore system to get my phone back up and running with nothing lost. Very strange but I've now stayed with the default 560.
I've tried 440 and 480. I'm sticking with 480 for now. The only thing I've noticed so far is that the controls at the bottom of Play Music are a little weird at 480. They were worse at 440, iirc. However, it may just be activating a different layout for what it thinks is a different size screen.
Hey,
I played a bit with android screen resolution and DPI. I've changed the resolution to 1080×1920 and DPI 420.
Then I restarted the phone. I knew that some apps will not display correctly after this action so I didn't bother.
However after few weeks I realised that there is no Batter Life gain with lowering the resolution at all so I reverted back to stock: 1440×2560 and DPI 515 and restarted the phone.
I thought that apps will come back to normal but they didn't. I also tried the DPI of 560 + restart but no improvement inside apps at all.
I used the Terminal Emulator and commands "wm size" and "wm density" to perform all tasks.
Is there a way to get back to normal without flashing the stock ROM ?
adb wm density and size works like a charm on my other android devices, i.e. i can change the values with ease, but when it comes to the galaxy view anything other than the stock 1920x1080 and 160 (dpi) seems to throw the tablet for a loop, it causes the "unfortunately the ui system has stopped working" error to pop up, which remains until the values are returned to stock.
is there any way around this? i thought it might be the launcher i was using (nova) so i tried a few others, including the view's stock launcher, but no love... i also read that you need to clear the some system app caches but that didn't work either... any help would be appreciated!
well i've discovered that i can use a lower density without any trouble, for example 140 instead of the stock 160, but anything higher than the 160 stock density causes a systemui error... i've tried several different ways to change the density, adb, build.prop, and a couple of apps, and they all do the trick just fine, however the end result is always a systemui error.
aeneas1 said:
well i've discovered that i can use a lower density without any trouble, for example 140 instead of the stock 160, but anything higher than the 160 stock density causes a systemui error... i've tried several different ways to change the density, adb, build.prop, and a couple of apps, and they all do the trick just fine, however the end result is always a systemui error.
Click to expand...
Click to collapse
---- I second that. unfort, the GV is a tad shy with options / tweaking in general.
or at least until root comes along
; (