Database Develop

What density did you settle on?

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.

[Q] DPI in cyanogen 7

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

increasing LCD density to 240 converts ui to gingerbread

Could work at maybe 220 or 200 but at 240 for sure it's gingerbread.
Edit: works @ 220 also.

double1 said:
Could work at maybe 220 or 200 but at 240 for sure it's gingerbread.
Click to expand...
Click to collapse
is it located in build.prop

Its amazing....

Can we have some screenshots please?

Check the video:
http://www.engadget.com/2011/05/20/android-honeycomb-has-hidden-gingerbread-interface-enabled-by-h/

Ok that's just friggin bizarre...

Hello, Ice Cream Sandwich.

I didnt have the lcd parameter in my build.prop. Is that possible?
Second I added it but it does not seem to have done anything. I bumped it to 220.

Under what folder is the build.prop file?

It is located under System.

Cant find the line where to change the LCD density in the build file?

Brolloks said:
Cant find the line where to change the LCD density in the build file?
Click to expand...
Click to collapse
I didnt find it in mine, so I just added it in: ro.sf.lcd_density=220

i just used the lcd density app.

You can also add it to /data/local.prop.

I noticed while themeing that all the gingerbread icons where in the Xoom apks..
I guess all the density hack does is use the HDPI instead of the MDPI drawable folders
This takes it to high density from medium density.
It's all making sense to me now

I tried 200 and went into an infinate boot loop, had to hard boot to get out of it

Brolloks said:
I tried 200 and went into an infinate boot loop, had to hard boot to get out of it
Click to expand...
Click to collapse
What!? I was gonna try 200 but now I'll wait.

I actually would not recommend editing the build file, if you screw it up with a too high etting you will probably have to reflash it with an older image, rather use the LCD setting app, that way you can reset it

I used the lcd density for root app off the market and changed it to 180 and 200 and got the gingerbread look. But its useless cuz it u have no access to ur back and home buttons. Once u click into n app or something ur stuck.
Sent from my PG06100 using Tapatalk

Yeah, really need the physical buttons for this unless someone can code in some virtual buttons.

So What's the deal with DPI and the market?

I recently installed CM9 a1 on my touchpad and one thing that has been really confusing is the dpi settings and market compatibility. I found that flashing the 120 dpi zip makes the texts really small and even unreadable due to the low pixel density of tp. I tried changing the font size setting to large but unfortunately it only affects system ui and apps but not the third party ones.
My question is, if I change my dpi from stock 160 to 120 or 132 (by editing build.prop) What happens to my installed apps? Do they get updates as usual? And what happens to the apps that are not compatible with the new dpi, do they show up as "unsupported on your device" or just disappear from the market?
Overall, what configuration do you guys recommend?
Thanks

Apps would still run on lower DPIs. Some apps/games need you to toggle the screen stretch to work. You probably won't get updates for many apps. You can fix it by pushing the modified market into system/apps and then fixing its permission. The problem with the modified market is that sometimes it will update, in that case you'll have to clear the app data for the market. Its pretty easy to spot if your market has reverted because the layout is different. Or you can just change the DPI every time you want to install something and reboot and change it back when you're done.
I've been running on 132dpi since the ICS was available. I always change the build.prop in the zip before I flash. I even put the movies market in the gapps zip.
Samsung Captivate CM9 - Glitch Kernel | HP TouchPad CM9 - Bricked Kernel

I use the free app, DPI Changer to change dpi without having to mess with the build.prop file. Also, there's a paid app, LCD Modder Pro, that will make the market work with just about any dpi. I use 155. I read somewhere that it's proportionally the correct dpi for the TP.

chicle_11 said:
I use the free app, DPI Changer to change dpi without having to mess with the build.prop file. Also, there's a paid app, LCD Modder Pro, that will make the market work with just about any dpi. I use 155. I read somewhere that it's proportionally the correct dpi for the TP.
Click to expand...
Click to collapse
I tried the modder pro, but eventually market get's stuck again. the native dpi for the TP is 132 (that's what it is in webos). Wish next to 120 and 160 Dalingrin would also give us a dpi132 patch for the newest builds.

Why doesn't Google just add 132dpi into the next market app so its all official

Beanchimp said:
Why doesn't Google just add 132dpi into the next market app so its all official
Click to expand...
Click to collapse
Because of the variation in screen sizes and resolutions on various devices.

Thanks everyone.
I sucked it up and got LCD modder pro. I changed the dpi to 132 and installed the permanent market fix. It worked great and noticed that I get the same update notifications that I get on my galaxy nexus.
The only problem is that the modified market doesn't have a tablet section (My brother's transformer prime does). It seems like modder pro installs the phone version of the market. Is there a fix for that?

ArmanUV said:
Thanks everyone.
I sucked it up and got LCD modder pro. I changed the dpi to 132 and installed the permanent market fix. It worked great and noticed that I get the same update notifications that I get on my galaxy nexus.
The only problem is that the modified market doesn't have a tablet section (My brother's transformer prime does). It seems like modder pro installs the phone version of the market. Is there a fix for that?
Click to expand...
Click to collapse
you may have to edit your build prop to reflect a device so the market shows tablet apps.
try to change it to this:
ro.product.brand=samsung
ro.product.model=GT-I9100
it may or may not work.
I'm afraid you will eventually not need modder pro and instead fix this yourself with a modded trebuchet apk and build.prop. Until recently somebody modded the trebuchet for 132dpi, just like dalingrin provides the ones for 120 and 160. Hopefully that person will do this for alpha2. Also, I personally do not think there is a big difference between 120 and 132, so the 120dpi fix by dalingrin is perfectly fine for me.

derausgewanderte said:
you may have to edit your build prop to reflect a device so the market shows tablet apps.
try to change it to this:
ro.product.brand=samsung
ro.product.model=GT-I9100
it may or may not work.
I'm afraid you will eventually not need modder pro and instead fix this yourself with a modded trebuchet apk and build.prop. Until recently somebody modded the trebuchet for 132dpi, just like dalingrin provides the ones for 120 and 160. Hopefully that person will do this for alpha2. Also, I personally do not think there is a big difference between 120 and 132, so the 120dpi fix by dalingrin is perfectly fine for me.
Click to expand...
Click to collapse
I use nova launcher so no problem there. trebuchet was way too buggy for me even on 160dpi, and lack of grid settings was a deal braeker.
I tried the 120 fix but I noticed even if you change the font size to large in settings, in some apps fonts are so small and pixelized they are unreadable.

ArmanUV said:
I use nova launcher so no problem there. trebuchet was way too buggy for me even on 160dpi, and lack of grid settings was a deal braeker.
I tried the 120 fix but I noticed even if you change the font size to large in settings, in some apps fonts are so small and pixelized they are unreadable.
Click to expand...
Click to collapse
the problem is that market doesn't care what launcher you use. It's trebuchet that needs to be modded to get it to work. Look inside Dalingrin's dpi fixes and you will see two files - trebuchet. apk and build.prop.
Maybe somebody can tell us how to mod trebuchet and we can build our own fix.

DPI Change and SView Cover

Hope someone can help.
I have changed my lcd density through my build prop.
I'm using app settings in xposed and changed the sview Cover app to 480 but there is a black bar at the bottom.
Anyone know how to fix this?

jdubya45 said:
Hope someone can help.
I have changed my lcd density through my build prop.
I'm using app settings in xposed and changed the sview Cover app to 480 but there is a black bar at the bottom.
Anyone know how to fix this?
Click to expand...
Click to collapse
+1

there is a semi solution for this
usually people use rom toolbox to change the entire dpi.
first you must return the dpi to the normal 640 in rom toolbox
then in app settings Xposed change com.android.systemui dpi to 480
and then go to Android System (Android) and change the dpi back to 640
don't forget each time you must turn on the app setting and save after the change
this might effect some of the apps and show it in normal size but it will fix your problem
plus you can change any app's dpi to 480 from app settings later and make it small again.

omid_freesky said:
there is a semi solution for this
usually people use rom toolbox to change the entire dpi.
first you must return the dpi to the normal 640 in rom toolbox
then in app settings Xposed change com.android.systemui dpi to 480
and then go to Android System (Android) and change the dpi back to 640
don't forget each time you must turn on the app setting and save after the change
this might effect some of the apps and show it in normal size but it will fix your problem
plus you can change any app's dpi to 480 from app settings later and make it small again.
Click to expand...
Click to collapse
Thought id note as far as I know the stock DPI is 480.
Sent from my SM-G900A using Tapatalk

I used xposed setting to change my dpi and I used it to specify original dpi of 640 for the sviewcover app but the black bar still persists.

Rakuu said:
Thought id note as far as I know the stock DPI is 480.
Sent from my SM-G900A using Tapatalk
Click to expand...
Click to collapse
you're right, I have a galaxy note 4, I'm sorry
I'm not sure about your original dpi though, but the method should work