Rooted Nook Tablet Options

---

Indirect deserves a salute for rooting the NT
http://forum.xda-developers.com/show....php?t=1354487

Still running a Nook Color with a dpi of 240 in build.prop, I would very much
get any reports on the following
1. Can the same be done on the NT without too many side affects?
2. Has anyone installed skype and tested the built in Mic?

How about a response as to a rooted Nook Tablet with a higher (240) dpi setting?

speaking completely out of curiosity, how can you display a higher dpi onscreen (if I'm understanding what you're asking), if the display is only capable of 169 dpi?

maybe I'm oversimplifying the question and am not understanding you.

---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------

after doing some searching, are you referring to actual font size?

Android allows different dp settings independent of the hardware dpi for UI design. Details in below link,

http://developer.android.com/guide/p...s_support.html

Density-independent pixel (dp)

A virtual pixel unit that you should use when defining UI layout, to express layout dimensions or position in a density-independent way.

The density-independent pixel is equivalent to one physical pixel on a 160 dpi screen, which is the baseline density assumed by the system for a "medium" density screen. At runtime, the system transparently handles any scaling of the dp units, as necessary, based on the actual density of the screen in use. The conversion of dp units to screen pixels is simple: px = dp * (dpi / 160). For example, on a 240 dpi screen, 1 dp equals 1.5 physical pixels. You should always use dp units when defining your application's UI, to ensure proper display of your UI on screens with different densities.

Originally Posted by e.mote

Android allows different dp settings independent of the hardware dpi for UI design. Details in below link,

The density-independent pixel is equivalent to one physical pixel on a 160 dpi screen, which is the baseline density assumed by the system for a "medium" density screen. At runtime, the system transparently handles any scaling of the dp units, as necessary, based on the actual density of the screen in use.

I understand the advantage to a developer laying out UI that needs to run on different display resolutions, but I don't see an advantage for an end-user. Why would you set your dpi to 240 if you can only display 169 dpi on the device? Won't the tablet simply downsize bit-mapped images when they're actually displayed?

Honest question--I'm probably not understanding something here--and I'm certainly not trying to rile anyone. Thanks!

Per above equation, setting your device's dpi setting to 240 would allow the app to be 150% in size. This aids in legibility, at cost of more screen space.

If you have an NC, you can see this firsthand by adjusting abovesaid dpi setting in build.prop up or down.

Originally Posted by e.mote

Per above equation, setting your device's dpi setting to 240 would allow the app to be 150% in size. This aids in legibility, at cost of more screen space.

Ah, cool. Thanks for the info!

All I wanted to know was if the build.prop can be edited on a rooted NT as I have done on the NC.
Also, I will try once more. Did anyone use the Microphone with skype or some other chat app?