I hope someone knows the answer to this...
The DPI of the nook color is rated for 169dpi, yet the build.prop has it set to 161.
Changing it to the hardware correct value even solves some little graphics bugs. Like the "line on notification bar"
So why does it not match HW
Sent from my NookColor using Tapatalk
As explained by dal:
dalingrin said:
Note that lcd_density is an integer value only. Additionally, when using mdpi, 160 is the default lcd density. Any other lcd density with mdpi involves interpolation. If you compare 160 and 169.x you can see that the images used for icons are significantly more blurry at 169.
The reason I chose 161 instead of 160 was to workaround a Market bug that caused the my apps list to fail to load. In my limited testing it seems Market 2.3.4 may have fixed the issue. If so, I plan to switch back to 160 which has the best image quality and best app compatiblity with the exception of Google Maps. However, 160 will need more testing with the latest Market to make sure the "my apps" list is completely fixed.
Click to expand...
Click to collapse
dalingrin said:
The problem with densities greater than 160 is the interpolation that must happen. I just checked for good measure and the icons are definitely not as sharp. Additionally, you will see artifacts from the interpolation such as gradients on the Gingerbread keyboard and the notification drop down.
In my testing I saw no difference in font rendering.
Keep in mind that another motivation for moving to 160 is that afaik, all apps scale properly to full screen. Any deviation from the mdpi standard 160 causes some apps not to scale to full screen. An example is Google Reader. If you click on an article to read, it will give you a libwebcoreview but it does not scale to full screen at >160.
Click to expand...
Click to collapse
fmkaiba said:
I hope someone knows the answer to this...
The DPI of the nook color is rated for 169dpi, yet the build.prop has it set to 161.
Changing it to the hardware correct value even solves some little graphics bugs. Like the "line on notification bar"
So why does it not match HW
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
You can use 169. Despite what people think, 160 is the best value to use for the Nook. Anything other than 160 means extrapolation or interpolation must take place. This is why nearly every HDPI phone uses 240, not 231 or 248, despite their real world DPI. However, there is a bug in the Android Market @ 160 on tablet size screens. For now I have it set to 161 to get around that bug. I don't use 169 because icons and such are more blurry due to the extra extrapolation needed. Until Google fixes the market there isn't a good DPI for us to use. Each has its own problems, 161 has a line in the notification bar but sharp icons, 169 doesn't have a line in the notification bar but has blurry icons....etc
Dalingrin, are you aware of any ill effects from running lower DPIs, such as 140?
That's where I've had mine for months, and I love it. Then again, I'm also running at 1920x1080 on my 15" laptop.
I love this forum!
Thankyou for a clear and logical answer I couldn't get anywhere else!
Sent from my DROIDX using Tapatalk
Sorry for necrothreading, just wanted to point out that Market 2.3.6 (from gapps 0613) still has a problem with My Apps @160dpi. :/
Rodney
Related
Has anyone had success with the LDC Density app? My friend used it on his galaxy s it was pretty cool
I tried it and my phone just froze. Had to do a battery pull to fix it.
Yes, im rooted.
this has been answered multiple times in a few thread.
maybe if you tried searching you'd have an answer.
Froze on my rooted TB with Adrynalyne's Rom. Curious to see if anyone has this working.
Didn't work for me either. Just manually edited /system/build.prop to change it around. Messes with the look of the Sense Clock Widget, and certain skins for the SenseUI.
Chris Hansen said:
Didn't work for me either. Just manually edited /system/build.prop to change it around. Messes with the look of the Sense Clock Widget, and certain skins for the SenseUI.
Click to expand...
Click to collapse
where in the build.prop do you edit the file?
nm found the line. it was obvious enough
FWIW 190 has been a good number for me. I was at 200 for awhile, set it at 190 today and it runs pretty well.
So I take it you aren't running Sense then? Because anything lower than 240 messed up the flip clock and some of the themes bar at the bottom.
I am sure I am not alone when I say this but does anybody know why the fonts on the screen are so massive? Was this phone originally intended for people with failing vision?
Why, with such a lot of real estate, doesn't htc squeeze in more info into the screen so that we lessen scrolling? Beats the hell out of me.... Its irritating to say the least. The net effect is that I have a bigger phone than the inc but I have exactly the same amount of info on the screen. I really do not see the point...
Rant over - now how do we lower font size and line spacing without messing everything up. Any easy fixes? In the uber z rom for the inc, gmichaelow made a zip that changed font sizes and line spacing to much lower levels without messing anything up. So its possible. LCD density is definitely not the answer.
khanam said:
I am sure I am not alone when I say this but does anybody know why the fonts on the screen are so massive? Was this phone originally intended for people with failing vision?
Why, with such a lot of real estate, doesn't htc squeeze in more info into the screen so that we lessen scrolling? Beats the hell out of me.... Its irritating to say the least. The net effect is that I have a bigger phone than the inc but I have exactly the same amount of info on the screen. I really do not see the point...
Rant over - now how do we lower font size and line spacing without messing everything up. Any easy fixes? In the uber z rom for the inc, gmichaelow made a zip that changed font sizes and line spacing to much lower levels without messing anything up. So its possible. LCD density is definitely not the answer.
Click to expand...
Click to collapse
I thought the exact same thing, my Droid has a higher resolution than the Thunderbolt (480x854 for OG Droid vs. 480x800 for Thunderbolt). Everything was blown up like crazy. I don't understand why they wouldn't have gone higher for a crisper look to rival the sleek look of the iPhone. There should be font packs out there, but I'm not sure where yet. Lowering my density to 190 definitely looks a lot better for everything but the notification bar icons. I'm going to look into smaller fonts as well, but for now, I'm happy with the lowered density, as it also makes things on screen look more crisp.
I've heard people talk about this in the past, but never fully understood what it did? Any explanation of what this actually does is appreciated. Thanks in advance
Just look at my picture compared to the stock setup. Mine is much crisper and smaller. It's like upping the resolution basically.
Chris Hansen said:
I thought the exact same thing, my Droid has a higher resolution than the Thunderbolt (480x854 for OG Droid vs. 480x800 for Thunderbolt). Everything was blown up like crazy. I don't understand why they wouldn't have gone higher for a crisper look to rival the sleek look of the iPhone. There should be font packs out there, but I'm not sure where yet. Lowering my density to 190 definitely looks a lot better for everything but the notification bar icons. I'm going to look into smaller fonts as well, but for now, I'm happy with the lowered density, as it also makes things on screen look more crisp.
Click to expand...
Click to collapse
Thanks. Will try this. Hopefully it does not mess any widgets.
Sent from my thunderbolt
Lcd density just hangs on my phone. I'm running storm. Anybody else manage to get it working on that rom?
Sent from my thunderbolt
Does anyone have themes out for specific lowered densities? I have found that when I lower the density, the bottom dock (Where the phone, app tray and personalize button are) looks disconnected and not very nice. Only thing holding me back.
Is there a way to keep with the stock launcher and theme it so it fits or would I be forced to switch to another launcher to alleviate that problem?
going to give this a try and see how it goees
i tried 225, 220, 210 and would rather just leave it at stock 240 than have blurry status bar icons...that drives me nuts and makes the phone look like ****..the rest of the screen looked perfect at 225 for me tho..
I run at 190. I used to run at 140 on my dinc. I hate big resolutions. I don't use the sense launcher so I don't have aproblem with it getting messed up
Sent from my ADR6400L using XDA Premium App
Even manually editing the build prop (CHMOD 777) I'm unable to get the changes to take effect. Any advice?
Gimpeh said:
Even manually editing the build prop (CHMOD 777) I'm unable to get the changes to take effect. Any advice?
Click to expand...
Click to collapse
Use root explorer, find build.prop, open it in a text editor, change the line that says LCD density. Save and exit, reboot. Done.
FatTony666 said:
Use root explorer, find build.prop, open it in a text editor, change the line that says LCD density. Save and exit, reboot. Done.
Click to expand...
Click to collapse
Yeah thats what I meant by manually changing the build prop.
Just curious now that we have had a good amount of time to mess with our NC tablets... What density did you settle on and why?
I am running the RC4 of CM7 and have tried 160, 161, 181, and 204 and still don't know which I like the best.
Did anyone find one they think worked the best for apps and also the looks of it and now have decided that you are going to keep it at a certain density from now on?
Just wondering what the masses are finding on it.
Where does one go to change the density on a cm7 build? I've heard this fixes some apps not fullscreening when downloaded from the market.
I prefer stock.. We have a high res screen (for its size), and we should use it that way. The icons look horrible at fisher price size... bleh. 160 for me.
I've learned to deal with the stock LCD density because I'm lazy, and don't want to change it every time I update. That being said, I've found that 210 not only looks good, but I could not replicate the market and app issues everyone was talking about. I personally like the larger objects, and being forced to have a limited amount of widgets and such makes the interface, honestly, minimalistic. If you do try that resolution out, please let me know if everything works as it should. I'm curious if it works for others.
I am on customized Nookie Froyo and using 200. The touch screen is smoother and responds better with 200. The larger icon is easier on my eyes. I switched back and forth between 160 and 200 for about three weeks. Finally settled on the 200.
Stock 161 for me.
for all the people having issues with densities, did they try disabling Compatibility mode?
i never had issues with Market, Maps, etc with changing LCD Density on any of my devices.
I use 160 on my Nook and 190 on my G2.
Faralon said:
Where does one go to change the density on a cm7 build? I've heard this fixes some apps not fullscreening when downloaded from the market.
Click to expand...
Click to collapse
I use LCD Density from the Market to change density on the fly. I go between 190 and 200 as a good compromise since I still use the stock ereader stuff but haven't made it permanent yet.
CM7 RC4 with density 204 here.
I've used 140 on every custom ROM I've installed... I still keep it minimalistic though with 2 or 3 widgets on a single home screen.
Faralon said:
Where does one go to change the density on a cm7 build? I've heard this fixes some apps not fullscreening when downloaded from the market.
Click to expand...
Click to collapse
I don't use an LCD Density app, I just edit /system/build.prop using RootExplorer's built-in text editor.
I just flashed CM7 on my Nook Color last night. While it looks and works great on the 7" screen I did notice some things were a bit too small and hard to read. You can always increase font sizes in specific applications but that's not a consistent solution to the problem. After experimenting with different DPIs, I found 187 to be okay but still a bit too small in some areas, 240 to be too large, and 204 to be just about perfect, allowing me to keep font sizes set to normal in applications and the handle on the notification tray remains in the center. Blurriness hasn't bothered me too much yet. I'm curious what values other people are using.
As an aside, why does increasing the DPI make elements larger and not the reverse? Thinking of it as "dots per inch," I would think more dots within an inch means a rendered element would fit into a smaller space...
Honestly, I've found the default 161 quite usable so I haven't played with it for quite some time.
Sent from my Apple IIe
hololight said:
Honestly, I've found the default 161 quite usable so I haven't played with it for quite some time.
Sent from my Apple IIe
Click to expand...
Click to collapse
Ditto. 240 (and such) just create icons wayyyy to big for me. I have a high res screen, i want to use it as such.
I personally like 140, however you lose "My Apps" ability in the market at this DPI.
The default 161 with a different font applied works for me. (The font is mentone, in case you were wondering.)
I tried 180 for awhile but that screwed up the formatting on a lot of apps.
Default for me. Tried many others and they either made the icons look big and stupid or really screwed up formatting in some apps.
I've been using 187 for about a month now. I think it looks nice, and really helps with the close-to-edge unresponsiveness by having slightly bigger objects to poke. I enjoy spending unreasonable amounts of time crafting custom UI's, and certain setups really pop with higher LCD density settings. I ran 210 for a while combined with a really sleek super simple interface. Ended up scraping it because it required an insane amount of widgets and 500 megs of RAM just wasn't enough.
Play around with the popular settings. Personal preference trumps what ever you'll read here.
Sent from my NookColor using Tapatalk
I just stick with 161.
Still rocking the Incredible with the XDA Premium App.
I need to use 160 for some apps to go fullscreen (Google Reader & FieldRunners). But this kills My Apps in the market. Does anyone know a DPI that will scale these apps correctly and keep the market working 100%?
JonMayer said:
I need to use 160 for some apps to go fullscreen (Google Reader & FieldRunners). But this kills My Apps in the market. Does anyone know a DPI that will scale these apps correctly and keep the market working 100%?
Click to expand...
Click to collapse
Fieldrunners works at any DPI if you turn off compatibility mode. The only fix for GoogleReader is to use a different program
Market works fine at 161+
Thanks for the info on the game. I'm going to reboot and try that out now. I used to love that game on my iPod Touch.
I figured the Reader app just hasn't been updated in forever is why. I'll stick with my 161 then. I like the size of everything on the screen and it's still comfortable for me to read.
I use the default setting..
If you have the new Market, I would recommend using 160.
160 will be the new default as soon as more folks get the update Market.
dalingrin said:
If you have the new Market, I would recommend using 160.
160 will be the new default as soon as more folks get the update Market.
Click to expand...
Click to collapse
My first thought when the new Market appeared was, "OMG I hope it works at 160 so I can have both my Market and Google Reader working at the same time!"
And.... so far so good! Woooooooooooooot!
dalingrin said:
If you have the new Market, I would recommend using 160.
160 will be the new default as soon as more folks get the update Market.
Click to expand...
Click to collapse
SiMi clock doesn't display correctly at 160.
It doesn't display correctly at 161, either, but it's worse at 160.
161 leaves a column of pixels unused on the right side in portrait, where the wallpaper shows through the clock's background.
160 makes the clock's background very thick, and overlaps my power button widget in landscape mode.
I've been using 169. This creates the least bit of widget overlap between the clock and power bar, and also makes the clock cover the entire row in portrait. It makes desktop icons a tad blurry, though. Everything else displays fine.
gadzooks64 said:
My first thought when the new Market appeared was, "OMG I hope it works at 160 so I can have both my Market and Google Reader working at the same time!"
And.... so far so good! Woooooooooooooot!
Click to expand...
Click to collapse
Sorry to burst your balloon. After a couple of reboots, My apps disappears (just like before).
What are you doing exactly when you lower it, and what do you get from it?
I saw a few threads about it but they're all procedures and instructions.
It just makes things on the screen smaller. You can therefore fit more stuff on the screen, if you are using a launcher that allows adjustable row/column settings.
Beware however that TouchWiz looks pretty nasty on non stock settings. Also the dialler and other bits and pieces won't display correctly. You can however adjust it back again.
It is most useful to me where it can display much more in the same screen area. Some apps are not multidpi friendly and do not show correctly, eg the dailer and some games.
nobnut said:
It just makes things on the screen smaller. You can therefore fit more stuff on the screen, if you are using a launcher that allows adjustable row/column settings.
Beware however that TouchWiz looks pretty nasty on non stock settings. Also the dialler and other bits and pieces won't display correctly. You can however adjust it back again.
Click to expand...
Click to collapse
When you say "it just makes things on the screen smaller," is it the icons or other stuff onscreen getting smaller or the screen getting bigger? I'm using GoLauncher EX and I was wondering about that setting on custom rows/columns that goes up to 10. I was wondering how would that fit.
dchsub said:
It is most useful to me where it can display much more in the same screen area. Some apps are not multidpi friendly and do not show correctly, eg the dailer and some games.
Click to expand...
Click to collapse
So also I guess that's why a lot of the "lower DPI"-related threads are about looking for compatible apps. Thanks!
Do many people tweak their DPI? Can you share examples of significant advantages of doing so that's worth the hassle of looking for apps/themes that would work on the adjusted DPI? Thanks again!
nobnut said:
It just makes things on the screen smaller. You can therefore fit more stuff on the screen, if you are using a launcher that allows adjustable row/column settings.
Beware however that TouchWiz looks pretty nasty on non stock settings. Also the dialler and other bits and pieces won't display correctly. You can however adjust it back again.
Click to expand...
Click to collapse
You're everywhere, nobnut! (Sorry for the off-topic)
Anyway, I hope soon everything will be smooth when changing dpi (maybe CM port or ICS). It's really useful for us with good sighting, I've been using my HD2 at 160 dpi instead of 240 and it's not only neater on the homescreen but very useful in some apps (and a less toyish aspect )
I suddenly want to switch to 240 DPI but the effort scares me.
Found this: http://forum.xda-developers.com/showthread.php?t=1369162&page=2
I don't like how it doesn't work for some apps as of now, though I never heard of Samsung ever accommodating DPI changes? That's why I didn't learn of this from somewhere else before the forums. :O
rerp said:
I suddenly want to switch to 240 DPI but the effort scares me.
Found this: http://forum.xda-developers.com/showthread.php?t=1369162&page=2
I don't like how it doesn't work for some apps as of now, though I never heard of Samsung ever accommodating DPI changes? That's why I didn't learn of this from somewhere else before the forums. :O
Click to expand...
Click to collapse
Just try this app: https://market.android.com/details?...wxLDIxMiwiY29tLmlubm9kcm9pZC5kcGljaGFuZ2VyIl0.
It's easy as hell, you can try and then undo effortlessly. But I'm sticking to 320 until... until I try again 240
rerp said:
When you say "it just makes things on the screen smaller," is it the icons or other stuff onscreen getting smaller or the screen getting bigger? I'm using GoLauncher EX and I was wondering about that setting on custom rows/columns that goes up to 10. I was wondering how would that fit.
Click to expand...
Click to collapse
Everything is smaller. Everything.
Yes, Go Launcher looks good at a lower dpi once you have set the rows and columns. Shortcuts, texts, widgets etc will all display as smaller.
For example O at 320 might look like o at 240.
To edit, there are apps to use (if you are noob ). The best way is to open the build.prop file in the 'system' folder, find the line ro.sf.lcd_density=320 and change the 320 to your value... then reboot.
Just remember the default value is 320 if you want to return again.
AzureD said:
Just try this app: https://market.android.com/details?...wxLDIxMiwiY29tLmlubm9kcm9pZC5kcGljaGFuZ2VyIl0.
It's easy as hell, you can try and then undo effortlessly. But I'm sticking to 320 until... until I try again 240
Click to expand...
Click to collapse
nobnut said:
Everything is smaller. Everything.
Yes, Go Launcher looks good at a lower dpi once you have set the rows and columns. Shortcuts, texts, widgets etc will all display as smaller.
For example O at 320 might look like o at 240.
To edit, there are apps to use (if you are noob ). The best way is to open the build.prop file in the 'system' folder, find the line ro.sf.lcd_density=320 and change the 320 to your value... then reboot.
Just remember the default value is 320 if you want to return again.
Click to expand...
Click to collapse
Thanks for the link but I don't think that changing the DPI itself is any difficult. It's cleaning up the possible mess after, with changing the incompatible apps. I've heard some of them won't work right on different DPIs. Is there a thread for that around here?
Also, I read one about S-Memo not working nicely, and I use that app a LOT, so I guess I'll be monitoring what they do in that thread too.
I do like how it looks like though. Makes me feel the phone is even bigger.
At 240 (default DPI for 800x480) "all" (can't tell for sure) apps will work. Everything also looks good since, again, it's the default Android DPI and some UI elements will look like crap if you set it to 260 or so. Try out the app and see if you like it. If not just reboot the phone and it'll be back to normal.
Sent from my iPad GT-N7000 using xda premium
Wait... Need some clarification about this... I've gotten some games in the market before and I uninstalled them because they didn't go full screen. They left like a fourth of the screen unoccupied and simply black. If I switched to 240, you think they would take the full screen?
Sent from my GT-N7000 using XDA App
no. for example, live holdem pro looks the same crap on 320 and 240 too
Sent from my GT-N7000 using XDA App
That's not nice. Are there any workarounds for such apps? I thought DPI would be a solution.
I know most of you with think why would i want to increase the DPI of Galaxy note.. Lets just say a special person needs to use it and requires REALLY REALY LARGE fonts.. The largest possible hopefully.. is it possible to increase the DPI higher than 320? if so how?.. Most apps i found only limit to 320 DPI.. what is a safe DPI can i use higher than 320?.. Thanks alot..
if you need large font, just go to settings, accessibility, and change the font size from 'normal' to 'huge'. that should help with some apps. but i think what you want is lower dpi. fonts occupy a set number of pixels on screen. higher dpi makes the pixels smaller and hence font smaller, lower dpi makes the pixels larger, hence font larger.
Souai said:
if you need large font, just go to settings, accessibility, and change the font size from 'normal' to 'huge'. that should help with some apps. but i think what you want is lower dpi. fonts occupy a set number of pixels on screen. higher dpi makes the pixels smaller and hence font smaller, lower dpi makes the pixels larger, hence font larger.
Click to expand...
Click to collapse
Its already in Huge but, the its still to small for him to read.. If i decrease the DPI, The resolution of the phone increases and the fonts become smaller.. I tried it.. So far, i got the screen to go up to 400 DPI and the fonts get larger, however if i go beyond the default 320 DPI, the settings application FC.. Anyone have an advice?
xyzsor said:
Its already in Huge but, the its still to small for him to read.. If i decrease the DPI, The resolution of the phone increases and the fonts become smaller.. I tried it.. So far, i got the screen to go up to 400 DPI and the fonts get larger, however if i go beyond the default 320 DPI, the settings application FC.. Anyone have an advice?
Click to expand...
Click to collapse
Not sure if and how it'll work for you, but there's a "Font changer" app on the market, which can resplace default Droids Sans font on rooted device with any .ttf font of your choosing.
What you could try - if DPI attempts fail - is finding some readable font which will be bigger on the screen. What I mean is that when I tried replacing default device font with e.g. Segoe UI or Tahoma or Calibri (copied from my Windows), some of those fonts were visibly smaller or bigger than Droid Sans - maybe there is sth that's much much bigger than the rest - Arial Black or Impact perhaps?
also - CyanogenMod builds for other devices had small app called Spare Parts, which enabled changing the deafualt font size for all apps. There is similar Spare Parts app on the market, did not try it, but maybe it also has the same ability
xyzsor said:
Its already in Huge but, the its still to small for him to read.. If i decrease the DPI, The resolution of the phone increases and the fonts become smaller.. I tried it.. So far, i got the screen to go up to 400 DPI and the fonts get larger, however if i go beyond the default 320 DPI, the settings application FC.. Anyone have an advice?
Click to expand...
Click to collapse
The higher the DPI the smaller the fonts will get. Best try to get some large fonts installed. If you are able to change DPI then it means you are rooted so try Absolute System Root Tools or Jrummy Root Toolbox and both have a lot of fonts ranging from small to large and they change the fonts of every text on the phone !!!
I also thought higher DPI, smaller font size. But indeed, higher DPI, bigger font size (like in PC Display)
on ICS, Changing DPI causes bootloop
Has anyone noticed that making these changes on ICS causes the phone to fail to boot? Quite annoying, as I'd like to make better use of the screen estate.
Actually if you use romtoolbox it wont fail at boot. At least with fpi bigger then 219
Sent from my GT-N7000 using Tapatalk 2