After reading some topics on the new JB rom I tried to see the dpi settings over XXLQ2 and it's set to 160. Based on the specs reports, the SGT P6800 has a rating of 190 (ppi). Wait, is dpi different from ppi?
Sent from my GT-P6800 using XDA Premium HD app
Sorry, I could not answer your questions, but just wanted to say that after tampering with the DPI Scaling Settings through build.prop, I pretty messed up my tablet.
After changing the value and rebooted the device the screen stayed black forever.
Thank good I had a Backup.
So please tamper with care on theses settings.
Besides, do you have link for the statement that it is rated at 190dpi ?
Greetings
qwertz
kencad said:
After reading some topics on the new JB rom I tried to see the dpi settings over XXLQ2 and it's set to 160. Based on the specs reports, the SGT P6800 has a rating of 190 (ppi). Wait, is dpi different from ppi?
Sent from my GT-P6800 using XDA Premium HD app
Click to expand...
Click to collapse
The "DPI" you see on build.prop is not necessarily related to the physical DPI/PPI of the device; it works as a guide for the OS. It is how the OS figures out the "size" of the device, and therefore how many pixels each UI element needs to use to have a "standard" size in centimeters.
Let's say an hypothetical device has a 1280x800, 7.7 inch screen. Let's say it uses DPI=190 (which matches the PPI you get if you calculate the number of pixels per inch for its physical dimensions). Now, an Android app asks for an icon on the screen with 0.5x0.5 inches. The framework looks at the DPI setting. An inch of the (logical) screen uses 190 pixels; so, the framework draws an icon with 95x95 pixels.
Our device has 1280x800 pixels (and 7.7 inches diagonal). When using DPI=160, Android estimates our display at 8x5 inches (about 9.5 inches diagonal). So, the same program asks for a 0.5x0.5 icon, the framework gives it an 80x80 pixel icon, which would have exactly 0.5x0.5 inches on that virtual 9.5 inch display; and is smaller than that on our 7.7 inch display.
In short, the DPI setting on build.prop is a way to adjust the size of all display elements on your screen. Lower DPI settings make things smaller, while higher DPI settings make them bigger. As for what setting is the best, only you can tell. I haven't messed with the DPI on my tab. My Galaxy S2 had a default DPI of 240, a "real" PPI of 213, and the best setting for me was at about 180 (fitting much more stuff on the screen). Here on the 7.7 I see the default as good enough. Some people complain that fonts should be bigger: those people could benefit from increasing the DPI.
Google Play offers you software based on your DPI setting. So, unless you use standard values (160-240-the 216? of the Nexus7), be prepared to see the number of apps available shrink a lot. Or, use a hacked Play Store that doesn't check the DPI...
Did anyone change the DPI without screwing the tablet up?
I've tried the JBNexus 7 port and its DPI is much better, but I dont like all the Nexus theming
Related
I know that the galaxy tab resolution is 600x1024, but I am curious if thats a limitation of current android versions or the actual hardware in the device. They mention that honeycomb will support higher resolutions, so would it be possible that we get a resolution increase with the software update? I tried to pull up the specs of the LCD panel used in the device but I couldn't find anything that was directly linked to the existing tablet implementation.
I have to use LCD density, otherwise everything looks too big. Would be nice to have OS support for a higher resolution.
Its limited by what the hardware can handle. In the Tabs case,the screen is maxed at 1024x600.
No company that I am aware of uses a lcd screen that is of a higher res than what they sell it as. It would be a waste of money for them since the resolution is one of the factors of what it costs. In this game, ever penny counts for them.
Look for the Tab2 to possibly have a high res screen.
Thats what I was afraid of. Was hoping that the screen was capable of more and that the OS was holding it back a bit. Maybe honeycomb will do a better job allowing you to customize the scaling like lcd density to emulate a higher resolution. We can always hope.
It would of being nice if they made a 720 panel but %90 of consumers wouldn't care / know what it even meant.
I normally use a LCD Density of 180 on my Tab! My ideal value is 160 but it screws the system Status bar on stock ROM!
Pat123 said:
I normally use a LCD Density of 180 on my Tab!
Click to expand...
Click to collapse
Ditto... I use 180 as well, love it!
Rogue9 said:
Ditto... I use 180 as well, love it!
Click to expand...
Click to collapse
i assume you are still on the stock rom?
below 183 the camera doesnt work on other roms, atlest for me
natious said:
i assume you are still on the stock rom?
below 183 the camera doesnt work on other roms, atlest for me
Click to expand...
Click to collapse
It works with 182
Does anybody know what the default background image resolution will be for the Xoom?
I had gotten the impression from the demo videos that Honeycomb didnt do the whole "pan slightly left and right when moving through the homescreens" thing, but AndroidPolice just posted a few backgrounds that were ripped out of the SDK and their resolution is 1920x1280... which Im having a hard time making sense of. Most notably, the fact that the height is off so much.
I think it's going to be 1280x800, same as the screen resolution.
Maybe the wallpapers in the SDK are covering the xtra large resolution.
And maybe the wallpapers in the final Xoom will be at 1280x800.
let me try...
when you turn the xoom into portrait mode, the height effectively becomes 1280px. So any wallpaper would have to have a height of 1280px to fit the screen.
I read that tegra 2 devices support full hdmi out...meaning if you have an hd tv hooked up to your device running at 1920x1080, the wallpaper would need a width of 1920px to fit the tv....
creating wallpapers at 1920x1280 covers all situations...
sounds good in theory...anyone have a different perspective?
Ahhh, someone else asking a similar question. Although I've posted this elsewhere, and since I'm not the thread starter, I'll post this here...
I’m about to purchase a Xoom, and simply stated, the Xoom has 5 ‘desktops’ that you can ‘pan across.’
I’ve seen a few videos of the Xoom on YouTube, where the ‘wallpaper’ shifts slightly when you pan right or left to another ‘desktop.’
I plan on using this device for a unique purpose, and when I pan right or left, I want the entire background to change.
For the sake of this post, let’s assume I want each desktop wallpaper to be a different color…red, blue, green, yellow, and orange. Further, when I pan, I don’t want to see anything but THAT one color.
So again, the distinction here is…
1) A slight shift in the ‘wallpaper’
Versus
2) a whole new image (color or otherwise) on each of the 5 ‘desktops.’
I'm looking for number 2. Is this possible?
I think the second comment was the good one, it's when the Xoom is put into portrait mode, I should have thought about that.
About the "a whole new image on each of the 5 desktops", I think we'll have to wait for a developer to make a tablet Home replacement with this option.
513 said:
I think the second comment was the good one, it's when the Xoom is put into portrait mode, I should have thought about that.
About the "a whole new image on each of the 5 desktops", I think we'll have to wait for a developer to make a tablet Home replacement with this option.
Click to expand...
Click to collapse
Bummer, that seemed like a simple enough request. lol.
sadiqa122 said:
let me try...
when you turn the xoom into portrait mode, the height effectively becomes 1280px. So any wallpaper would have to have a height of 1280px to fit the screen.
I read that tegra 2 devices support full hdmi out...meaning if you have an hd tv hooked up to your device running at 1920x1080, the wallpaper would need a width of 1920px to fit the tv....
creating wallpapers at 1920x1280 covers all situations...
sounds good in theory...anyone have a different perspective?
Click to expand...
Click to collapse
That makes a lot of sense. The idea of handling portrait also completely escaped me. Thanks
The only thing that still sounds fishy would be the re-scaling the UI resolution to fit the TV, rather than simply scaling to fit. I would think that would (seemingly) open the door to all sorts of shifting and alignment issues that they would have had to handle.
Hmm... well, so much for the idea of using the posted default backgrounds to identify "the" size. Downloaded a few and I'm seeing 2 at 1920x1408 and at least one at 1920x1280
Hmmm...Well if 1920 is the default height for portrait mode, and 1280 (or greater) is the width. Maybe the variation in width causes a "broader" slide when swiping left to right (so more of the image is exposed)?? So you could concievably create a wallpaper that's 1920 x 4000?
So, the Streak's default LCD density is 160, but how did they arrive at that figure?
Is this setting really true to its "native resolution"? It seems like 160ppi is simulating a higher resolution screen. This is how I arrived at this conclusion:
I have an Evo and the text and icons on the Streak appear smaller than the Evo. Given that both devices have the same resolution (800x480), shouldn't the text and icons appear larger since the Streak's screen is larger?
Is it possible to find the true PPI that would yield a "1:1 pixel display"?
I set the ppi to 240 and the text and icons appear proportionally larger than on the Evo as would be expected.
So, why is the default ppi set to 160?
After digging around it looks like the native ppi is 187:
http://www.brighthand.com/default.a...ell+Streak+Google+Android+OS+ATT+Tablet+Phone
I think 200ppi might be the ideal density for this resolution and size display based on the Evo.
The Evo has a hardware ppi of 217 but its software display ppi is set to 240. So, if we apply the same rule to the Streak, then:
240 / 217 = 1.106 * 187 (hardware ppi of Streak) = 206 (software display ppi)
I noticed after doing this and comparing pixels in the icon graphics, the 200pi makes the pixels look sharper and less blurry (anti-aliased).
The reason its set to 160 is so it can utilize the screen size.
If it was set to 240 (like the evo) then it would like just a blown up version of the evo.
For example. the streak's default at 160 lists 3 or so mor apps in market then the evo. But with a simple edit of the build.prop you can set it to whatever you like. I know someone that has their streak set to 240 just because they have bad eyesight.
I personally like mine at 160 cuz i can view more stuff and really use the 5" screen. But the downside is some developers don't code their apps properly and they don't draw right for the 160dpi
fone_fanatic said:
The reason its set to 160 is so it can utilize the screen size.
If it was set to 240 (like the evo) then it would like just a blown up version of the evo.
For example. the streak's default at 160 lists 3 or so mor apps in market then the evo. But with a simple edit of the build.prop you can set it to whatever you like. I know someone that has their streak set to 240 just because they have bad eyesight.
I personally like mine at 160 cuz i can view more stuff and really use the 5" screen. But the downside is some developers don't code their apps properly and they don't draw right for the 160dpi
Click to expand...
Click to collapse
True! And you could do that with any display. This example is kind of a stretch but my Panasonic 720p plasma can display 1080i. I guess it does it thru interpolation and shrinks the image so the whole desktop fits. The result isn't as sharp as a true 1080p display.
By going with 160ppi, are we doing the same thing? I'm curious what resolution it "emulates" by going that low?
As a developer myself, we never had to worry about ppi because pretty everything was as 72ppi! This is an interesting new territory we're moving into with all these different display sizes and resolutions.
But, something I want to understand and figure out a "best practice" or "golden rule" for
Oh, btw, I'm not saying tha HTC's hardware ppi to software ppi ratio is the "golden rule" but they're a billion dollar company, I'm sure they spent some time figuring out why they chose that ratio. In the end it's all very subject at the moment.
Keep in mind that at least with tvs everything's pre-rendered, on a phone it'd be more like a computer game or a desktop, it knows what to strech and what not to.
Android 2.x uses 9.pngs for a lot of strechable dialog boxes so that it should look good at any resolution.
Most apps also come with icons/images in multiple sizes so that it's streching/shrinking one that's already closer to the target size instead of only a single image to all sizes.
It's like the dpi setting in windows, it just zooms everything in/out, it's independent of the resolution. (though windows isnt as good at non-default dpi's, some icons do in fact look worse at non-default dpis since virtually all installs are at it's default dpi)
I find the Dialer crashes often with dpi=200.
Would like to run it 200+ otherwise?
you can change the density to whatever you want. dell liked 160 mdpi for a tablety feel and to utilize the large screen while most manufacturers use the hdpi of 240 to keep the ui elements the same between devices. i found that the interface has to be changed alot to suit this and choosing something in between is a bad idea as you get overlapping ui elements such as buttons and text fields, and things like blurry notification icons.
i would love to go to an hdpi only..not mdpi
Krad said:
i would love to go to an hdpi only..not mdpi
Click to expand...
Click to collapse
all you have to do is modify your /system/build.prop then.
http://www.streaksmart.com/2010/10/how-to-change-lcd-density-on-rooted-dell-streak.html
SonicTab said:
I find the Dialer crashes often with dpi=200.
Would like to run it 200+ otherwise?
Click to expand...
Click to collapse
I'm only using this to replace my iPod touch so I don't use the dialer but everything else runs fine.
Sent from my Xoom using XDA Premium App
SonicTab said:
I find the Dialer crashes often with dpi=200.
Would like to run it 200+ otherwise?
Click to expand...
Click to collapse
I don't understand. Why would lcd density affect program functionality?
What is this? Windows?
I found a free file explorer that opens the file but won't save my edits. I assume I have to change the file to r/w, but I'm not sure how. Any thoughts?
I Used root explorer, change to r/w , edit .
Yes it does crash at times as the Dialer does not scale at all when you change density.
Anyone in Canada looking for a streak let me know.
Here is a good read from the android developer site about dpi's and different screen sizes etc.
http://developer.android.com/guide/practices/screens_support.html
fone_fanatic said:
Here is a good read from the android developer site about dpi's and different screen sizes etc.
http://developer.android.com/guide/practices/screens_support.html
Click to expand...
Click to collapse
That is an excellent article!!!
Can the resolution of the screen be modified like a computer monitor? I'm wondering because we could increase battery life of the device if the GPU doesn't need to push as many pixels. I'm assuming its hard set though.
I'm no expert but I would expect the display controller is preset to only drive the display in its native resolution.
Even if you could change it I doubt it would save power. The same number of pixels would need to be sent to the display. You'd just be changing where the work was done. The display controller would have to use more power to scale the image rather than driving 1:1 to the display.
semlethe3rd said:
Can the resolution of the screen be modified like a computer monitor? I'm wondering because we could increase battery life of the device if the GPU doesn't need to push as many pixels. I'm assuming its hard set though.
Click to expand...
Click to collapse
Please, tell me how you can remove pixels of a computer screen.
beerope said:
Please, tell me how you can remove pixels of a computer screen.
Click to expand...
Click to collapse
Please do not comment if you have nothing to add to a thread. Yes an LCD screen can not change the amount of pixels it outputs, its hardware after all, but the amount of pixels being processed by the gpu can potentially be changed and then interpolated to fit the native resolution of the screen. I was just interested in what people think that have more experience then I have with the device.
semlethe3rd said:
Please do not comment if you have nothing to add to a thread. Yes an LCD screen can not change the amount of pixels it outputs, its hardware after all, but the amount of pixels being processed by the gpu can potentially be changed and then interpolated to fit the native resolution of the screen. I was just interested in what people think that have more experience then I have with the device.
Click to expand...
Click to collapse
I don't know if it makes a difference but you can always change the screen DPI/density.
RoloRacer on Galaxy Note
OP I've been wondering the exact same thing, I doubt it's possible though.
what the OP wants to do is akin to buying a Veyron then running it on one cylinder to save fuel.
beerope said:
what the OP wants to do is akin to buying a Veyron then running it on one cylinder to save fuel.
Click to expand...
Click to collapse
Once again, thank you for your rude opinion that has contributed nothing. If you don't agree with what I'm asking about that is fine, just skip over the thread.
Would be interesting to see if this was possible
I looked into this quite a bit when trying to get better game performance. Changing DPI settings doesn't change the resolution. I'd really like a 1/2 res option, which would be 1280x800.... perfect for games. I couldn't find any way to do this, and I think it would need to be implemented at the kernel/graphics driver level. There was a post on the N10 gaming thread, where someone had started some sort of Google petition to implement features like this. The link from that thread had far more info than I can provide, but I got the impression that this isn't a trivial modification.
Bioorganic, can you post a link to the thread you mentioned? I plan on looking into tackling it myself if I get time, but if someone has already attempted I don't want to recreate the wheel. Thanks in advance.
http://forum.xda-developers.com/showthread.php?t=765639 - [APP] LCD Density Changer - create HighRes screen effect
bayutop said:
http://forum.xda-developers.com/showthread.php?t=765639 - [APP] LCD Density Changer - create HighRes screen effect
Click to expand...
Click to collapse
Screen DPI =/= Actual Resolution. In short, changing screen DPI is basically changing the size of text and buttons, but not the general resolution those said things run at.
Hi xdas and dear community,
Sorry for my bad english in some cases please.
I have been asking questions, on that answers haven't been unveiled yet for me.
I'm asking my self often why LG has built a Display that makes 424 dpi?
Thats great in first sight but as I had looks at what the standard android dpi is
for that great device, i am looking at 480 dpi at all?
Why does LG do that to this great device?
What does the 480dpi SW-Android preference do to the 424dpi HW-Display.
Does this mainly facilitate the Qualcomms work or does it just size up displayed contents on the display (or makes it contents look bigger)?
I played with that dpi and my sense of taste has become a better look at 424 dpi adjustment, 380 dpi is near to small for good reading at regular reading -distance (looks silly if anyone's making strange faces because that's too small ^^ I tried it out at several ppl faces XD )
But back to the roots I ask, why does LG do that and what does it do with a device, in regarding to performance, display and such..
Answer please if you know what you're talking about. I wanna understand and learn from it ( a little bit ).
Best regards to that great community,
mobshredder
You just mixed up ppi and dpi
PPI is a physical thing : ppi stands for pixels per inch and you can find formulas on google to calculate it ( it is size and resolution dependent, so you won't get a round number like 480/360 etc..)
DPI is here for the devs that want to make look their app the same regardless of your screen size and/or resolution.
Everything is explained in this link : http://www.captechconsulting.com/blog/steven-byle/understanding-density-independence-android
:victory: