Is there some way i can fake my dpi for the purposes of the market. My phone's default is 240, but I like my dpi set to 190 as that complements my screen size really well ... however, when market looks at that, it assumes I have a tablet and removes most apps etc ... is there a way I can fake my dpi to 240 (it doesn't need to change it to 240, just make the market think it is 240) without having to manually change it to 240 and restarting the phone?
dunno if this will work for u
http://forum.xda-developers.com/showthread.php?t=863519
Indirect deserves a salute for rooting the NT
http://forum.xda-developers.com/showthread.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/practices/screens_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.
e.mote said:
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.
Click to expand...
Click to collapse
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.
e.mote said:
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.
Click to expand...
Click to collapse
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?
Can any dev explain the phenomena that I experience with Navigon when altering the Interface DPI with Paranoid Android? Not that they have to, I'm just curious.
If I set the DPI lower than 320, Navigon blows the interface up to freakish levels. Setting Navigon's per-app DPI back to 320 only makes it worse.
To get Navigon to display properly (and like stock 320 DPI), I have to set it to 160 DPI. With the XPosed framework, I can set the DPI back to 320 to remove the graphical glitch and set the app to view as it was before I changed the UI's DPI.
If I want the interface shrunk to match the rest of my UI, which I have at 190 DPI, I have to manually edit to properties.conf file to set the DPI to 100.
If no one can answer, hopefully this will help others who might have experienced this with other apps.
Hey I Have Ported A Rom to My Device Having Rosolution of 240 x 320 But Now ported rom's app drawer not fitting to screen and lock screen not at center .
i there is any way to fix it ?
try increasing or decreasing the DPI just add ro.sf.lcd_density= (watever dpi you want) check you stock ppi just third party apps like cpuz or anythings reliable
in your case your case you wanna reduce the size of the app drawer try decreasing the DPI value from stock so lets say if you have a dpi of 200 at stock get it down to 180 dpi or still big then 160 dpi reduce it till you think the app drawer fits your screen perfect you will have problems with the dialer just ask for help about it even i could not figure out how to resize the dialer
For those who don't know you can change DPI in the dev menu under "Minimum Width" (not taking any responsibility if you mess something up lol there is a reason it is hidden in the dev menu). The default is 411.
So far I have tried 10 different settings but due to the aspect ratio of the screen I cannot find the perfect DPI for games but also for everyday use. Not a fan of changing DPI just to play a game when I have a few minutes to kill. Any one have better luck?
Mine is currently at 441 (which means it must have adjusted itself from the 440 I set it to), and I think it's pretty good for daily use.
Can't really speak for games though.
Yep I'm using 480 at the moment and games seem to fit great but some apps don't like it
I've had mine set to 530 (it defaults to 533 after exiting settings for some reason) for a while. I found that setting it to anything above 550 results in a misaligned finger register where taking one place registers about 4mm above it. As much as I'd love to set it to 570, doing so results in this misalignment.
I haven't noticed any issues with 530. Only thing that messes up is Samsung's keyboard, but I use the AOSP Android L keyboard with the symbols.
Could you please post images of these gaming issues you are referring to?