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.
Related
This question is directed to anyone who knows the inner workings of the vending.apk and the android market itself. Through another post about density settings, it seems pretty apparent that, while having density set at 161 allows all the apps in the market to show up, there are still plenty of apps that won't actually RUN unless you are set at 160/159. So it turns into a Catch 22 situation. I know I have used device spoofing via an altered build.prop (or an apk that does the same) for getting apps to appear that are 'proprietary' to other, specific devices, but I'm wondering if it MIGHT be possible to spoof the market into reading our Nooks at being 161 devices, while we are actually at 160 while within our rom (I'm on CM7). This has probably been proposed somewhere else, but I couldn't locate a thread...Anyone have any input about this possibility? If something like this is NOT possible, please let the users know also, if you have a minute. Thanks for looking...(Idea..could we get a secondary "market161" .apk created that we could use indepedently of the one in the latest Gapps to achieve the desired effect?)
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
My Density is set at 200 and everything works just fine (including both Market and Maps).
Mine is set at 240 (need new glasses?) and everything seems to be ok
Trust me...there are enough that don't run at 200....otherwise I wouldn't have bothered posting. 160 seems to be magic for compatibility/scaling, and 160+X gets best market access.
Sent from my PC36100
ganovim said:
Mine is set at 240 (need new glasses?) and everything seems to be ok
Click to expand...
Click to collapse
I actually would assume the 240 would work.. since it's 1 of the 3 native android app densities that devs mass market through compatibility mode to ensure mucho marketshare (120,160,240)..but the icons and such at 240 are just too huge ...can't do it...reminds me of those physical phones with humongous buttons that people have in their house. When I see someone using a new tablet, like take the Galaxy, I can tell pretty much immediately whether they're running stock from the look of their homescreen...Huge, ghastly, labeled icons +(bloatware)=someone not using their device to the full potential, and that makes my inner nerd sad. Nope, even if I go blind I won't do 240....if only because "it just LOOKS stock. The same reason SPB mobile lasted about a week on my nook.
Sent from my PC36100
Sent from my PC36100
FrasierCrane said:
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
Click to expand...
Click to collapse
Thanks...this is exactly what kind of info I needed...new project...sigh..will give it a shot after work tonight...Thanks.
Sent from my PC36100
Sent from my PC36100
FrasierCrane said:
You could write a widget that toggles ro.sf.lcd.density in build.prop between two values, and then use Tasker to toggle the widget when you open the Market (and flip it back when you leave it). But I'm not sure if the Market checks the value in build.prop or what the device is currently using, so it might require a reboot instead.
Click to expand...
Click to collapse
BTW..Is Tasker's U.I. still absolutely archaic? I love all the possibilities from the app.. but it's such a nightmare to use. Is there any other 1 out there that might be easier on the brain?
Sent from my PC36100
mazook98 said:
I actually would assume the 240 would work.. since it's 1 of the 3 native android app densities that devs mass market through compatibility mode to ensure mucho marketshare (120,160,240)..but the icons and such at 240 are just too huge ...can't do it...reminds me of those physical phones with humongous buttons that people have in their house. When I see someone using a new tablet, like take the Galaxy, I can tell pretty much immediately whether they're running stock from the look of their homescreen...Huge, ghastly, labeled icons +(bloatware)=someone not using their device to the full potential, and that makes my inner nerd sad. Nope, even if I go blind I won't do 240....if only because "it just LOOKS stock. The same reason SPB mobile lasted about a week on my nook.
Sent from my PC36100
Click to expand...
Click to collapse
You're really making me want to track you down so I can change your density settings just to mess with you
Sent from my SAMSUNG-SGH-I897 using Tapatalk
wretchedlocket said:
You're really making me want to track you down so I can change your density settings just to mess with you
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
It would be SO on....
Sent from my Nook Color (zoom2) using Tapatalk
mazook98 said:
BTW..Is Tasker's U.I. still absolutely archaic? I love all the possibilities from the app.. but it's such a nightmare to use. Is there any other 1 out there that might be easier on the brain?
Sent from my PC36100
Click to expand...
Click to collapse
It's a pain sometimes, since everything is buried under submenus. I don't think there's anything else comparable, though.
The reason I have the density set at 161 isn't because apps are filtered. It was due to a bug in the Market apk and the Maps apk. Maps 5.1.x would crash on startup on tablets with LCD density 160. Google has fixed this with the most recent version. Unfortunately, Google has not fixed the Market yet. Tablets+160 causes the "my apps" list to not populate.
dalingrin said:
The reason I have the density set at 161 isn't because apps are filtered. It was due to a bug in the Market apk and the Maps apk. Maps 5.1.x would crash on startup on tablets with LCD density 160. Google has fixed this with the most recent version. Unfortunately, Google has not fixed the Market yet. Tablets+160 causes the "my apps" list to not populate.
Click to expand...
Click to collapse
Thanks so much for saving me from making this a bigger issue than it is...I don't need " my apps " to populate since I'm tethered to my Evo about 95% of the time, where they naturally all populate ...I'll just bump it down to 160 permanently, and if ever it becomes something I absolutely need, Ill just bump it back....Thanks for all your amazing work..Donation on the way when I get home from work.
Sent from my PC36100
Maybe im the only one, but whats the visual difference between 160 and 161? why is 160 better?
john10101 said:
Maybe im the only one, but whats the visual difference between 160 and 161? why is 160 better?
Click to expand...
Click to collapse
There are just some apps that wont run / scale correctly unless its at 160... they will just hang and load 4 ever or force close unless they are set at 1 of the 3 native densities for android application development... at least that's what I can glean.. no difference though in appearance, unless you're a cyborg.
Sent from my PC36100
oh this is why my app list wouldnt populate. it doesnt bother me most of the time. everyone seems to have their dpi set for so low. i have mine at 132.33 if i remember it right. can't be any bigger than 140 for sure.
can anyone give me an example of an app that crashes or does not show up on the market due to density conflicts?
the reason i ask is because i run hyperdroid on my HD2 at the default 167. this setting is just plain awesome compared to the 240. i have never had an issue with apps not showing up or crashes / anything due to resolution at this size.
or is this one of the default dev res' and i'm just talking nonsense.
let me know so i can test on my hd2.
pxldtz said:
can anyone give me an example of an app that crashes or does not show up on the market due to density conflicts?
the reason i ask is because i run hyperdroid on my HD2 at the default 167. this setting is just plain awesome compared to the 240. i have never had an issue with apps not showing up or crashes / anything due to resolution at this size.
or is this one of the default dev res' and i'm just talking nonsense.
let me know so i can test on my hd2.
Click to expand...
Click to collapse
Here's one...Try "Fruit Slice" at 161....then try it at others if you want...then run it at 160.
Sent from my PC36100
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
My Personal Density Is 120 But the Major Issue Which Forces Me To Go Back to My Original Phone Density [160] Is Due To
1. Apps Not Resizeing Properly On The Screen
2. Market Apps Getting Incompatible Upon Change
Well I Have Found the Fix for the Second Issue While Checking The XDA Forms The Day Before, Its Tested By Me On Our ACE And Its Really WORKS!
Heres What Must Be Done.
1. Go to Settings >> Applications >> Manage applications >> All.
2. Scroll down and click on Market.
3. Click on the "Clear data" button.
4. Using whatever method you favor, change the LCD density to 160 for now.
5. Reboot your device.
6. Go to the Market and click the Accept button when prompted.
7. Go back and change the LCD density back to whatever you like.
8. Reboot your device.
See Simple And Effective!
Now Must Find The First Fix.
Till Then Bye And Salam.
Samsung Galaxy Ace [Rooted]
Cyanogenmod 7.2 RC0 ICS FINAL
Turboboast v8.5 And SlaidMOD v3
8 GB Class 10 Sd Card Ext
THAnk mE IF I HeLPED
what does the density change even do..
Sent from my GT-S5830 using xda premium
Somebody working this tutorial?
Sent from my GT-S5830
Density change = larger resolution
Herpderp Adreno + Tegra.
Somebody working this tutorial?
Click to expand...
Click to collapse
I Have And It Works!
Works! But 120 is too small for me. About to leave it at like 130 or so
EDIT: Had to restore my phone using a Nandroid Backup. Tried changing the ADW theme and I'm guessing it didn't work correctly and my home screen couldn't load. So I'm guessing a fix is, changing themes in normal 160 density then switch down to whatever you want.
EDIT 2: The problem was that the theme wasn't for LDPI devices. Heads up everyone; make sure your theme supports the density you're setting phone at so you won't get any deformed icons or glitches.
SuperAce609 said:
Works! But 120 is too small for me. About to leave it at like 130 or so
EDIT: Had to restore my phone using a Nandroid Backup. Tried changing the ADW theme and I'm guessing it didn't work correctly and my home screen couldn't load. So I'm guessing a fix is, changing themes in normal 160 density then switch down to whatever you want.
EDIT 2: The problem was that the theme wasn't for LDPI devices. Heads up everyone; make sure your theme supports the density you're setting phone at so you won't get any deformed icons or glitches.
Click to expand...
Click to collapse
Glad For U
Do Thank Me!
alizafar said:
Glad For U
Do Thank Me!
Click to expand...
Click to collapse
Haha. I'm sorry, forgot to press thanks. Good job man
dialer...
I like mine set to 140 but i have only one program that gives a me a problem and thats the dialer... and of course that a pretty big problem lol... any suggestions..
I had earlier posted this in the CM9 thread in the dev section but since no one was replying i thought id come to the general section
Our phone looks so beautiful when the lcd density is changed to 140:
And now the problem :
When i try to make a call or there is an incoming call the phone gives this error-
"Unfortunately com.android.phone has stopped working", and it becomes okay if i revert the density back to 160. This did not happen with CM7 and is there only in CM9.
I believe this is a prob with the phone.apk but i dont know how to edit system files
Can someone PLEASE make a fix for this
EDIT
Guys guess what I fixed it myself
Now you can can lower the density of your screen with the help of this
I just used the phone.apk file from a lower resolution phone's ICS unfortunately I don't remember which phone it was(I think it was htc wildfire). Link to phone.apk attatched.
Oh and I will take full responsibility for any damage this may cause to my phone but none if you try it and something happens to yours ;-)
I had this problem too, but I didn't know that density was the problem, so I went back to CM7. If someone can help fix this issue would be great. I appreciate the effort for anyone that tries to help.
Believe me it would be amazing if somebody could fix this. Our phone begins to look like higher end phones when the density is lowered.
Just wondering, in the screenshot with the status bar pulled down, did changing the density shift the blue circle on the bar (on the bottom) to the left?
Yeah but it still looks better ;-).
Sent from my LG-P500 using XDA
Problem solved.
See first post if you want to try it
What do you mean with Density ?
The Pixel-Density ?
kind regards
xSyntaX
changing the density makes our device look ugly imo.. i like our default density, its perfect.. there is also pixelation here and there with lower density and smaller fonts.. u can increase font size, but well, doesnt suit me.
xSyntaX said:
What do you mean with Density ?
The Pixel-Density ?
kind regards
xSyntaX
Click to expand...
Click to collapse
Yeah pixel density.
harshdoshi25 said:
changing the density makes our device look ugly imo.. i like our default density, its perfect.. there is also pixelation here and there with lower density and smaller fonts.. u can increase font size, but well, doesnt suit me.
Click to expand...
Click to collapse
Technically lowering the density should make our device look ugly. But I find setting the density to around 140 makes the device(and the resolution) look perfect
and iv never faced any pixilation at that density, though setting it to 120(default ldpi) does make it look little pixelated and a bit ugly(and everything too small)
rishabh22 said:
Yeah pixel density.
Technically lowering the density should make our device look ugly. But I find setting the density to around 140 makes the device(and the resolution) look perfect
and iv never faced any pixilation at that density, though setting it to 120(default ldpi) does make it look little pixelated and a bit ugly(and everything too small)
Click to expand...
Click to collapse
call me mad, but i just tried 140 and reverted immediately ! eww ! oh and u on testing kang by lupo ? do u have the problem of grey search box and the line above dockbar ? it becomes white for a milli sec when menu pressed.. plz confirm or deny. (only on testing kang and the update by hephappy)
awesome..
nicce work
harshdoshi25 said:
call me mad, but i just tried 140 and reverted immediately ! eww ! oh and u on testing kang by lupo ? do u have the problem of grey search box and the line above dockbar ? it becomes white for a milli sec when menu pressed.. plz confirm or deny. (only on testing kang and the update by hephappy)
Click to expand...
Click to collapse
Guess uv got too used to the normal density
And iv removed the line from settings so cant say about that but no I don't have any prob with the search box
Edit
I just checked the dock divider and no I don't have any prob with that either :/
hey will this tweak work on xperia x8 with cm9 ?
Yeah it should. I cant tell for sure because I cant try it.
There's no harm in giving it a shot. Just backup before trying.
rishabh22 said:
Guess uv got too used to the normal density
And iv removed the line from settings so cant say about that but no I don't have any prob with the search box
Edit
I just checked the dock divider and no I don't have any prob with that either :/
Click to expand...
Click to collapse
maybe but u dont get that problem ? the search box (the ics square one) is completly white ? thats odd ! ppl did confirm this bug !
u using the new drivers rom right ?
Looks good on ics, I tried on gb and result was : ahhh my eyes
Sent from my LG-P500 using XDA
xperia x8 - not working
androidnerd2 hey will this tweak work on xperia x8 with cm9 ?
rishabh22 Yeah it should. I cant tell for sure because I cant try it.
There's no harm in giving it a shot. Just backup before trying.
I have tried on X8 - not working... error with dialer - not able to place/receive call....Androidnerd - have u tried it? Is it wokring for u?
Thanks
harshdoshi25 said:
maybe but u dont get that problem ? the search box (the ics square one) is completly white ? thats odd ! ppl did confirm this bug !
u using the new drivers rom right ?
Click to expand...
Click to collapse
Im using whatever drivers were there in lupo's test by default
I do have colour banding in some apps like whatsapp, but nothing with the search box.
PEKA22 said:
androidnerd2 hey will this tweak work on xperia x8 with cm9 ?
rishabh22 Yeah it should. I cant tell for sure because I cant try it.
There's no harm in giving it a shot. Just backup before trying.
I have tried on X8 - not working... error with dialer - not able to place/receive call....Androidnerd - have u tried it? Is it wokring for u?
Thanks
Click to expand...
Click to collapse
Works fine on my phone. Which phone.apk are you using the default one or the one iv linked?
Cresqo said:
Looks good on ics, I tried on gb and result was : ahhh my eyes
Sent from my LG-P500 using XDA
Click to expand...
Click to collapse
I had been using this with perfect peso(cm7.2 nightly based) and had got so used to it that at normal density ics was looking ugly to me
Thank you very much for this. I tried the same sort of thing myself, but because I have no idea what I'm doing, I tried taking the Phone.apk from a GB ROM that I was able to change the density on instead of one from a lower-res CM9 ROM and it caused a whole mess of problems, haha. Running Quattrimus CM9 alpha on my OV in beautiful 120 density.
Hi all,
I have found a way to change the dpi without root, just using adb and cmd and it worked like a charm...well, almost. There are a couple of UI glitches that appear when you reduce (or increase for that matter) the dpi.
Firstly, the icons on the home screen mess up, but that's not SUCH an issue as you can install another launcher or in my case, find an icon pack that doesn't show the mess up quite as much (my preferable choice because you see the icons set in different areas of the UI, such as the notifications shade and recents menu, settings, etc.)
Secondly, and the most annoying, is the crop function messes up in the weirdest way. Whether it be when changing wallpaper or trying to crop a picture in CamScanner, the image you choose appears zoomed in and there is no way to zoom out or even move the image around, only zoom in further.
Now, my question is, has anyone managed to find a suitable dpi that MIUI does not have a problem with, or are there some standard dpi's MIUI uses apart from 480? Or has anyone found a way around any of these issues (or any other issues they may have encountered when changing the dpi)? Last but not least, is there a custom version of MIUI out there, or a rom that has it's visuals (and camera app) but custom tailored to suit various dpi's and other modifications?
I really cannot live with the stock dpi of 480, it's like using a phone made for old people, waaaay too large EVERYTHING on a large screen, I want to see more on a large screen. But I also am not yet prepared to go off MIUI as I really like their UI, visually, and I know any other rom will lose a lot of camera quality amoungst some other things like battery life, etc.
Thanks guys in advance for any advice.
Use 400 DPI ..There is no issue ..I am using it from 1Month
Sent from my Redmi Note 3 using XDA-Developers mobile app
Anands3 said:
Use 400 DPI ..There is no issue ..I am using it from 1Month
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Which method?
Sent from my kenzo using XDA-Developers mobile app
Textdroider App from play store
Sent from my Redmi Note 3 using XDA-Developers mobile app
If the original one is 386 I think 400 is kinda useless... Or did you mean 300?
Original is 403dpi if I'm not mistaken. I set mine to 375 and it's absolutely perfect..
Default density is 480.
Code:
[email protected]:/ $ wm density
Physical density: 480
Zak108 said:
Hi all,
I have found a way to change the dpi without root, just using adb and cmd and it worked like a charm...well, almost. There are a couple of UI glitches that appear when you reduce (or increase for that matter) the dpi.
Firstly, the icons on the home screen mess up, but that's not SUCH an issue as you can install another launcher or in my case, find an icon pack that doesn't show the mess up quite as much (my preferable choice because you see the icons set in different areas of the UI, such as the notifications shade and recents menu, settings, etc.)
Secondly, and the most annoying, is the crop function messes up in the weirdest way. Whether it be when changing wallpaper or trying to crop a picture in CamScanner, the image you choose appears zoomed in and there is no way to zoom out or even move the image around, only zoom in further.
Now, my question is, has anyone managed to find a suitable dpi that MIUI does not have a problem with, or are there some standard dpi's MIUI uses apart from 480? Or has anyone found a way around any of these issues (or any other issues they may have encountered when changing the dpi)? Last but not least, is there a custom version of MIUI out there, or a rom that has it's visuals (and camera app) but custom tailored to suit various dpi's and other modifications?
I really cannot live with the stock dpi of 480, it's like using a phone made for old people, waaaay too large EVERYTHING on a large screen, I want to see more on a large screen. But I also am not yet prepared to go off MIUI as I really like their UI, visually, and I know any other rom will lose a lot of camera quality amoungst some other things like battery life, etc.
Thanks guys in advance for any advice.
Click to expand...
Click to collapse
Is it possible to change the density using terminal emulator directly on phone? Or do I need to have PC?
GarbeVR said:
If the original one is 386 I think 400 is kinda useless... Or did you mean 300?
Click to expand...
Click to collapse
No, the original is 480, which is too large...where did you get the number 386 from? perhaps it is another one of their phone's stock DPI, which means MIUI might not warp on this DPI value? Will check it out, but any information you have, please let me know
h4gH said:
Is it possible to change the density using terminal emulator directly on phone? Or do I need to have PC?
Click to expand...
Click to collapse
Not sure about that, I only tried it from the pc, sorry.
Zak108 said:
Not sure about that, I only tried it from the pc, sorry.
Click to expand...
Click to collapse
OK will try at home then.
Just to be sure - phone has to be in FASTBOOT mode to accept ADB commands from PC right?
used some of the suggested DPI's but...
so, thanks guys, used some of the suggested DPI values, 386 and 375, and mostly everything works fine....except still some small issues with the icons and the cropping. try and set a wallpaper for a whatsapp group for example, photo shows as zoomed in and cannot zoom out to choose a crop of the WHOLE image like I used to....have attached some screenshots of what happens to my icons....is this possibly because I am not rooted that the DPI value is not getting set in to the system correctly? Is anyone who is rooted facing the same issues or not?
might convince me to root, this is the first device i have managed to be happy without rooting lol
h4gH said:
OK will try at home then.
Just to be sure - phone has to be in FASTBOOT mode to accept ADB commands from PC right?
Click to expand...
Click to collapse
No, no need....as long as you have ADB drivers installed and you are launching the CMD from within the ADB folder, it will work. Oh and of course USB debugging enabled and the first time it tried to access the phone for ADB details, you will need to allow it to by hitting remember and ok on the phone
h4gH said:
Is it possible to change the density using terminal emulator directly on phone? Or do I need to have PC?
Click to expand...
Click to collapse
Yes. I do bellow commands with Terminal Emulador on Android. My Device is Kenzo with MIUI 8:
su
wm density 400
The value you change to your preferred
Enviado de meu Redmi Note 3 usando Tapatalk
Zak108 said:
so, thanks guys, used some of the suggested DPI values, 386 and 375, and mostly everything works fine....except still some small issues with the icons and the cropping. try and set a wallpaper for a whatsapp group for example, photo shows as zoomed in and cannot zoom out to choose a crop of the WHOLE image like I used to....have attached some screenshots of what happens to my icons....is this possibly because I am not rooted that the DPI value is not getting set in to the system correctly? Is anyone who is rooted facing the same issues or not?
might convince me to root, this is the first device i have managed to be happy without rooting lol
Click to expand...
Click to collapse
Which theme is this?
BlueJeans said:
Which theme is this?
Click to expand...
Click to collapse
Roger Rabbit...I think at the time of the screenshots I was using a different theme for the status bar, but can't remember as I am now using Eureka 8 Pro. Roger Rabbit is the base theme though, quite like the grey simplicity.
GarbeVR said:
If the original one is 386 I think 400 is kinda useless... Or did you mean 300?
Click to expand...
Click to collapse
The original isn't near 386. I went down to 380 and everything it far smaller than a 6 dpi difference. I'd say stock is closer to 430 - 450
Yes man, you was right the original DPI is 440, the app textdroiderDPI was showing me an incorrect value of 386 (maybe a little bug...).
Setting it on 440 with LeDpiChanger gave me a full stock MIUI size
Stock is 480DPI, changers give bad result...just root and change build.prop ro.sf.lcd_density=
Denis:) said:
Stock is 480DPI, changers give bad result...just root and change build.prop ro.sf.lcd_density=
Click to expand...
Click to collapse
Thank you sir, this works for me on MIUI 8.1.1.0 global stable, change my screen density to 420. Icons are perfect.