Related
Info from this thread originally - http://forum.xda-developers.com/showthread.php?t=760805
Since we are using larger screens google recommends we change our dpi from 240 to 160, this probably looks fine for stock builds but on sense builds everything looks crazy. I currently have mine(on a sense build) at 210 however feel free to change it to what is best for you.
to perform this modification
pull the build.prop from /system/build.prop
open the file using a text editor and change ro.sf.lcd_density=240 to ro.sf.lcd_density=160(or whatever number you choose)
then push the file back to /system/build.prob
(i used a paid app called root explorer for this process)
if you want you use terminal emulator or adb here are the commands:
su
cp /system/build.prop /sdcard
then once youve edited the file
cp /sdcard/build.prop /system
you can use the same commands over adb by entering adb shell
download the spare parts app from the market and untick the compatibility mode then reboot (this fixes the issues some apps have with scaling)
the result of this mod is more things fit on the screen e.g. lists and web pages and games like raging thunder 2 look better as they arent being stretched out as much.
i recommend for a sense build: 200 to 220
for a vanilla build 160-220
if anyone has any better numbers please post
SCREENSHOTS ON NEXT PAGE
TO MAKE USE OF THE EXTRA SPACE ON THE HOMESCREEN INSTALL ADW LAUNCHER AND SET THE COLUMNS AND ROWS TO 6X6 (SCREENSHOTS ON PAGE 6) , THE SAME CAN BE DONE FOR THE APP DRAW
http://members.ping.de/~sven/dpi.html
input the values for HD2, you get ~217 dpi if you want to be anal about it
I wonder what effect not specifying any DPI would have...
this would be great if the lockscreen wallpaper would be retained... changing the dpi messes with the static wallpapers set...
I've tried 200, looks ok. I've always thought that we need to up the dpi, at 240 its way too huge for our screen.
160 messed everything up for me, the notification bar etc only filled half the screen. Other than that it looked awesome though! 200 might be the best, would be good to hear other opinions, not got a great deal of time to test
Is there a way to do it without Root Explorer?
FreakyFerret said:
Is there a way to do it without Root Explorer?
Click to expand...
Click to collapse
Go to your windows mobile, then edit the same file from the same folder of the Android. (not sure whether this works on all build, Shu8i build does work)
jubeh said:
http://members.ping.de/~sven/dpi.html
input the values for HD2, you get ~217 dpi if you want to be anal about it
I wonder what effect not specifying any DPI would have...
Click to expand...
Click to collapse
217 looks like 220 and leaving it blank sets it 160(thats what it looks like i cant tell really since it is blank)
pongster said:
this would be great if the lockscreen wallpaper would be retained... changing the dpi messes with the static wallpapers set...
Click to expand...
Click to collapse
would using a higher res wallpaper fix this?
Jragar said:
160 messed everything up for me, the notification bar etc only filled half the screen. Other than that it looked awesome though! 200 might be the best, would be good to hear other opinions, not got a great deal of time to test
Click to expand...
Click to collapse
160 on sense didn't mess up my status bar although some widgeds dissappeared. Which build are you using?
Interesting thread. I am using Mattc 1.5b Froyo. Anybody tries this? I am afraid of screwing my almost perfect setup.
Let me know what setting you used.
xkravenx said:
Interesting thread. I am using Mattc 1.5b Froyo. Anybody tries this? I am afraid of screwing my almost perfect setup.
Let me know what setting you used.
Click to expand...
Click to collapse
im on the same build as you with 210
copy out ur android folder onto ur hardisk as backup before u do the mod and u are safe if ur screen becomes black or u dun like it or it glitches badly and u cant modify it since u cant see the screen display properly..
This is sick,now my screen looks massive.Thx 4 the info..
"I pity the fool that owns an iPhone 4"
Sent from my HD2 using XDA App
please can you post before and after pictures
with 220 most of the apps doesnt scale properly and some doesnt work at all. Back to 240.
I set mine to 210.
It's hard to see the difference. I use MattC 1.5b with Froyo version...
The icons for "folder organizer" look smaller. But everything else seems to be the same. e.g. the htc sense applications, home, etc.
Maybe my mind is playing tricks on me.
here are some screenshots from the dpi changed from 240 to 200
xcooling said:
please can you post before and after pictures
Click to expand...
Click to collapse
This is what I've tried with mattcnexusleo1.1_512....
the 240 / 200:
I like the 200, it makes the keyboard smaller enough for me to type easier.
**mods please delete my post. JJbdoggg raced me to it...only sec's late sorry...
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
palosjr said:
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
Click to expand...
Click to collapse
Yeah your right same goes with me. I can't change it either that is why i used mattcnexusleo1.1_512 build. It worked with it...
palosjr said:
the settings wont keep on shu8i builds... weird... i tried modifying build.prop both on the phone and on pc... after pushing and rebooting it doesnt change, it actually changes back to 240... i tried the spare parts workaround, unchecking compat. mode and still no luck. any ideaS?
Click to expand...
Click to collapse
/android/root/system/build.prop
apeatan said:
Yeah your right same goes with me. I can't change it either that is why i used mattcnexusleo1.1_512 build. It worked with it...
Click to expand...
Click to collapse
You change build for that ? o-o
Shubcraft have cyanogen mod, wich is much more easier to make updates, no need to push anything and its great if you do a mistake see post above
-great tip thanks ! My screen looks really huge now at 200.. The appdraw is impressive too ... I'll wait for tomorrow to see if these smaller fonts are still readable with the sun.
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
I have unfortunately touchwiz can't handle the change, i mean it still works but it doesn't adapt to the new size, neither does the dialer. tried turning off compatibility mode in spare parts, but that did nothing.
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Okay im looking at that line so how do i edit it? Forgive me im new to this stuff /
SGS2 rooted and Overclocked to 1.5ghz stock rom p
No prob. Using Root Explorer, navigate to /system/ and make sure to hit the button in the top right "Mount R/W"
Long press "build.prop" and select Open in Text Editor
Make the change to the line "ro.sf.lcd_density=240" to whatever you want (200 probably works best)
Hit Menu softkey and choose "Save & Exit"
Root Explorer will automatically save a backup copy of build.prop
Reboot your phone to apply DPI change.
There is also a free root file manager called Super Manager, but I haven't used it.
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
nickshertzer said:
Here is a screenie from when I was running CM7.1 nightly 9 with ADW EX launcher set to 8x8 homescreen with DPI set to 200
The dialer was compressed, but nothing that some editing of the numerical PNG files in contacts.apk couldn't fix. It worked fine, no force closes anywhere.
Super simple to do, just use Root Explorer to edit /system/build.prop and change the line:
Code:
ro.sf.lcd_density=200
...save + exit and reboot.
The smaller the number, the more compressed the pixels. My Dell Streak 5 default is dpi 160, so using a 4x4 touchwiz homescreen at 240 dpi is taking some getting use to.
Some market apps will refuse to install at anything other than stock dpi. Not a big deal, revert changes + reboot + install + mod dpi again + reboot + done.
For the record, I'm using UnNamed 1.1 this week at stock DPI (and amazed that I kinda like TW4)
Click to expand...
Click to collapse
Nick I tried your method several different ways and have been going around an around with this for several weeks on our phone and also Sprint version too and the revert back does not stick or still allow to download/update the apps from the market. Tried restarting, clearing cache and resetting the market data and restarting but it still would persist and not allow the updates and incompatibility. The only success I experience is right after I update to a newer version of ROM or clean install all together (which for obvious reasons) resets the phone and then allows the update actions. It is just very frustrating that the DPI change would hinder "Certain Apps" from updating. Anyone have ideas on a future solution besides Nicks input on the manual fix? I think we have brilliant screens with lots of potential for various display options and I miss using the 200dpi settings, but application updates and use of the market is much more important for daily use.
---------- Post added at 11:27 AM ---------- Previous post was at 11:20 AM ----------
fone_fanatic said:
I came from a dell streak as well so the stock 240 density was WAY too big for me. Mine is set to 200 now and like it much better! But i ditched TW and i'm currently running UnNamed + ADWex.
nickshertzer, i'm currently attempting to edit the Phone.apk so the dialer stretches out. How did you go about doing this? I've got the Phone.apk decompiled, can't it be fixed by editing the dip values in the .xml files?
I found this thread with a script to edit the dialer for the I9000 that i'm attempting to use as a rough guide.
Click to expand...
Click to collapse
I have used the dialer files from this thread you mentioned and it all works fine on this ROM the only down side is once you theme that it changes to the themed dialer and goes with the 240 adjusted dialer. I would hope you could share your input and steps (If not too complex) to allow themers to integrate into their themes for multi dpi users.
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
poofyhairguy said:
No need to edit build.prop, this app does it for you:
http://www.appbrain.com/app/lcd-resolution-(root)/com.wemobs.android.lcdresolution
My biggest issue is the fact that the market sometimes won't let you install stuff at non240 densities.
Click to expand...
Click to collapse
this has been posted as an issue, go here and star it to bring it to the attention of the android devs.
qwertyaas said:
With the talk of Samsung releasing the SGSII line with just about the lowest resolution on the market, has anyone been using an LCD Density changer (or just changed the density) to effectively give a better resolution?
How are the results? Does it cause any issues in apps or what not?
Click to expand...
Click to collapse
Lowest res on the market? 800x480 is the industry standard at the moment. Not the best, but certainly not the lowest.
Sent from my Galaxy S II (i777) using XDA Premium.
I use 180 on a daily basis. In order to get around the dialer issue. I replace contacts.apk in Unnamed 2.21 with the one from Mikey's Serendipity 8.2 works perfectly except for the already in-call dialer pad which i rarely ever use is still small but the regular dialer is now stretched to full screen. It comes down to editing a .xml file or two if you want to attempt yourself.
Hperdroid has touchwiz that works on 160. it is my understanding most market things work with that density
Sent from my GT-I9100 using xda premium
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
hekoman said:
I am running the CM7 lastest nightly and I have my lcd density to 220. It makes everything look not so huge as it normally is on 240. It does not break anything as far as I can tell.
Click to expand...
Click to collapse
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Man_Cave_Tech said:
How does the dialer look at 220? I'm running Turkbey, and everything looks great and proportional at 200 and 220 except for the dialer. It becomes offset to the left, so I'm just keeping it at stock 240.
Sent from my Galaxy S II (i777) using XDA Premium.
Click to expand...
Click to collapse
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
jazzboyrules said:
I use my phone at 220 without any issues. I have stopped using the stock dialer since I tried DW contacts. It didn't have any problem when I switched from 240 to 220.
People having issues with stock dialer at 220 could try it out.
Sent from my AT&T Samsung Galaxy S II
Click to expand...
Click to collapse
Ok, thanks for the input. I'll give that a try when I get home from work tonight.
Sent from my Galaxy S II (i777) using XDA Premium.
I've been using a LCD Density of 185 for as long as I can remember. It's rare now to see an app that doesn't like a custom lcd density setting. Occasionally I run into an app on the market that doesn't like it, and I get the banner at the top of the screen. Since I edit the build.prop for my density setting I have to keep an app handy just incase I get the market issue. But it's an easy fix- use app to get back 240 density> manage applications> market> clear data. Open market> download desired app! Love 185. Probably wouldn't go any lower personally but... for the most part, most apps will happily still work and fill the screen
What do we won lowering the density?
RatusNatus said:
What do we won lowering the density?
Click to expand...
Click to collapse
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Coreym said:
User preference. By lowering the density you virtually make the screen bigger. (More can fit on the screen)
sent from my Galaxy SII
Click to expand...
Click to collapse
But it's not the same using a launcher that gives you more columns and rows?
Just saying
Saludos desde Ecuador
The last days I was playing a little bit with the density on my phone. At first you want to know which ROM I'm using. > CM9 latest build. I would like to set my density to 178 or also to 170, these are densities, the phone can show without a blurred screen, or blurred icons. Everything works fine and looks bombastic! But the problem is, that the phone.apk keeps crashing.
Everything is working until a density of 190. Below this value, phone.apk crashes everytime you start a call, or are called.
I know this problem is not new, but other threads are not answered and very old.
So... Anyone knows, whats the problem? Why it is. And how we could fix it?
I will try to disable compatibility mode in spare parts, but I don't think that it will work.
Anyone knows a workaround or maybe has a modded phone apk for ics?
Thanks in Advance!
EDIT: As I thought, compatibility mode won't change anything.
Silberpfeil3110 said:
The last days I was playing a little bit with the density on my phone. At first you want to know which ROM I'm using. > CM9 latest build. I would like to set my density to 178 or also to 170, these are densities, the phone can show without a blurred screen, or blurred icons. Everything works fine and looks bombastic! But the problem is, that the phone.apk keeps crashing.
Everything is working until a density of 190. Below this value, phone.apk crashes everytime you start a call, or are called.
I know this problem is not new, but other threads are not answered and very old.
So... Anyone knows, whats the problem? Why it is. And how we could fix it?
I will try to disable compatibility mode in spare parts, but I don't think that it will work.
Anyone knows a workaround or maybe has a modded phone apk for ics?
Thanks in Advance!
EDIT: As I thought, compatibility mode won't change anything.
Click to expand...
Click to collapse
I don't know how to solve your problem man,but I suggest you give exDialer a go.It's as smooth,functional and cool-looking(even has an ICS theme available) as the ICS dialer.It'd make for a good alternative until you find the solution.
i'm using 185 on cm9 and phone.apk is working great for me.
Sent from my GT-I9100 using XDA
tolis626 said:
I don't know how to solve your problem man,but I suggest you give exDialer a go.It's as smooth,functional and cool-looking(even has an ICS theme available) as the ICS dialer.It'd make for a good alternative until you find the solution.
Click to expand...
Click to collapse
The problem is that it isn't the dialer that crashes, but InCallScreen. exDialer still uses the default InCallScreen, so it still crashes.
supermult said:
i'm using 185 on cm9 and phone.apk is working great for me.
Click to expand...
Click to collapse
I believe it breaks once you go below 182. If you were to drop your density to 180, you'd see the crashes, too.
hi,
i read very often about reducing density from twohundred and xxx to one hundred and xxx.
but nobody explained, whats the advantage of reducing this.
can somebody explain to me please?
regards - sui
As everything's a bit smaller, more stuff fits on the screen.
its a problem which isnt even fixd in the latest cm9 build so no, wait for fix!
But when everything is smaller, the widgets wont fit on the homescreen... ?
... sent by my SGS2 tapatalked ...
My first post after searching the forums.
Overcome Series v2.3.1 is the first ever rom installation I've done on my Galaxy Tab P7500 (after stock HC3.2 got corrupted lost touchwiz and status bar).
The rom's great, faster, far louder sound. But I have problem with all fonts. Compared to the old stock rom all the fonts seem to be pixelated, fuzzy, similar if not as bad as an Ipad 2.
On stock 3.2 System Info app reported back the screen resolution as the whole 1280x800 while on Overcome rom I get 1280x752 (the user area?) as resolution report.
Has anyone had the same problem and found a fix or knows what I can do? I have reflashed but nothing changed. Many thanks and best
Izzy
You need root for this.
You can use FontChanger (Market) or change the font yourself in system/fonts
Download the font you want from dafont.com or something, Then rename it as the same, I think it's DroidSandBold.tff , But you need to rename the font to those and replace the ones there, and voila it will change to what you wish.
Too much hassle? Font Changer does the same
Misledz said:
You need root for this.
You can use FontChanger (Market) or change the font yourself in system/fonts
...
Click to expand...
Click to collapse
Many thanks. I downloaded the app and it identified a missing density parameter. I then flashed Pershoot's latest kernel and got no error message. I'm assuming screen resolution 1280x752 as reported by Android System Info is okay? Previously it stated 1280x800 with HC3.2. I can still see any font is less dense than it used to be but I guess it's a give-and-take Thanks for the advice!..
Best
Glad that helped and worked for you I had resolution errors aswell thinking that it was 720 when I had tried linux on it only to find out the resolution is bigger than it seems. First i've heard of that
Misledz said:
Glad that helped and worked for you I had resolution errors aswell thinking that it was 720 when I had tried linux on it only to find out the resolution is bigger than it seems. First i've heard of that
Click to expand...
Click to collapse
Being a newbie... I still can't work out why the 3.1 or 3.2 stock roms give higher resolution to the Overcome 3.2. I did a restore to the former just to check and alas I get better font density (very crisp) than now back to Overcome.
I kinda lost my original stock 3.2 when the touchwiz and status bar disappeared, leaving with no Kies update options. So its becoming a steep learning curve!
Many thanks
Hello guys,
Could you help me? I'm trying to use Themer, but I cante because the resolution/DPI.
I have a Moto G, and I use the 220 DPI (I dont like BIG icons)
Thanks.
vcnicinho30 said:
Hello guys,
Could you help me? I'm trying to use Themer, but I cante because the resolution/DPI.
I have a Moto G, and I use the 220 DPI (I dont like BIG icons)
Thanks.
Click to expand...
Click to collapse
Ditto. I believe my LCD Density Value is set to 245. But themer can't handle that so I am wondering what people are using?
vcnicinho30 said:
Hello guys,
Could you help me? I'm trying to use Themer, but I cante because the resolution/DPI.
I have a Moto G, and I use the 220 DPI (I dont like BIG icons)
Thanks.
Click to expand...
Click to collapse
Only stock DPI is supported.
ThemerSupport said:
Only stock DPI is supported.
Click to expand...
Click to collapse
Any intention to support multi DPI?
Alot of Custom ROMS allow easy changing of the DPI, Seems your limiting your potential market.
I Love Themer, I just cannot use it, as Landscape and Multi DPI do not work properly.
dave7802 said:
Any intention to support multi DPI?
Alot of Custom ROMS allow easy changing of the DPI, Seems your limiting your potential market.
I Love Themer, I just cannot use it, as Landscape and Multi DPI do not work properly.
Click to expand...
Click to collapse
In the future we might look at multi DPI support, however at this moment the task is a lot harder than it sounds. Sorry about that.
ThemerSupport said:
In the future we might look at multi DPI support, however at this moment the task is a lot harder than it sounds. Sorry about that.
Click to expand...
Click to collapse
I completely understand the complexity of the multi DPI.
But has anyone considered some pre defined DPI's
So at least the user can get a Near Enough DPI, and then tweaking the theme to fit perfectly is only minimal changes.
Again just a theory, I have never really worked on DPI.
dave7802 said:
I completely understand the complexity of the multi DPI.
But has anyone considered some pre defined DPI's
So at least the user can get a Near Enough DPI, and then tweaking the theme to fit perfectly is only minimal changes.
Again just a theory, I have never really worked on DPI.
Click to expand...
Click to collapse
There's a strange relationship with a device's DPI and resolution, which is why many device aren't supported (such as the G3). We've tried what you've suggested, however "near-enough" isn't what the average user wants
ThemerSupport said:
Only stock DPI is supported.
Click to expand...
Click to collapse
What the stock dpi value?? :320DPI?
brunodu91 said:
What the stock dpi value?? :320DPI?
Click to expand...
Click to collapse
That depends on what device you are running. This site should help: http://dpi.lv/
problems with themer app
ok I have a rooted galaxy mega and when I use the themes it fills main screen but doesnt fix rite.. is this a resolution problem please help
jlm4241985 said:
ok I have a rooted galaxy mega and when I use the themes it fills main screen but doesnt fix rite.. is this a resolution problem please help
Click to expand...
Click to collapse
Hi, unfortunately the Mega isn't supported just yet due to its resolution. Hopefully it will be soon though!
I have a rooted Nexus 5 with SlimKat ROM running. SlimKat changes the DPI by default, but using BuildProp Editor I changed it to the stock 445 DPI. However, Themer says my resolution is wrong. If I set Themer as my default launcher, I can press the home button and see the default Themer appearance, I just can't download anything from the app. Any suggestions? Thanks in advance!
I was running trents rom on the GN2 at 270 and it looked ok. I have gotten away from this application recently though.
KRex1313 said:
I have a rooted Nexus 5 with SlimKat ROM running. SlimKat changes the DPI by default, but using BuildProp Editor I changed it to the stock 445 DPI. However, Themer says my resolution is wrong. If I set Themer as my default launcher, I can press the home button and see the default Themer appearance, I just can't download anything from the app. Any suggestions? Thanks in advance!
Click to expand...
Click to collapse
Hi, try changing it to the default DPI settings (480), as this should help Themer recognize the themes.
Good luck!
220
I also use 220
ThemerSupport said:
Hi, try changing it to the default DPI settings (480), as this should help Themer recognize the themes.
Good luck!
Click to expand...
Click to collapse
It works perfectly now, thanks! By the way, Themer is awesome - great work!
Hi, I have Sony T2 ultra Dual. although its resolution doesn't support for themer. but after root, when I change its DPI value to 320, now its resolution is 1184*720. and themer is working perfect on it. May be it will help.