Hi all,
first things first i dont have a problem its just a question out of curiousity.
I was i the App "Easy DPI Changer" to change the DPI scaling on my OP3 to 480.
That was when i saw the "Display Info" Page was showing a Resolution of 2064x1080, which in it self is a strange meassure.
Everywhere i checked (and how i remembered it) the OP3 & 3T where using a Panel with a Resolution of 1920x1080p.
Now my question, where are the other 144 pixel coming from?
Do i have some naughty pixels that make babys when im sleeping? (that would be the new definition of creepy though)
Or (the more likly one) is it because i dont use the on-screen Buttons and the that space is used?
Thanks in advance and happy weekend
DeMon
Your second assumption is correct. The absence of navigation bar causes the app to assume the physical screen size (or so called resolution) wrongly. Here we see the app trying to add or subtract its available pixels (for example, on yours its 1920x1080, on mine with navigation bar, it's 1790x1080).
The way I (or anyone) can know it's the navigation bar is due to the only number increasing or decreasing is the physical vertical size. So, how do we know precisely what's causing the size to increase apart from assuming it? Maths, that's what.
First, we should know that everything on your screen is displayed in a metrics known as 'dp', density-independent pixels. This metric relies on the dpi, pixel density per inch. Thankfully, this metric can be easily converted to dp, with the formula of:
px = dp * (dpi / 160)
Thanks to the peeps at the Android Developer Support Site for supplying the formula.
So, we have our formula and metrics. Let's insert the numbers.
We know the size of navigation bar is constant, 48dp, whichever or whenever you are, as long as it has a navigation nar, it's 48dp. Of course, some ROMs have a feature to resize this to your willing. But, we aren't going to factor that, we're going to what the standard says.
Then, the DPI is a pretty easy variable to figure out, it's 480.
Punch the numbers and you have:
px = 48 * (480 / 160)
px = 48 * 3
px = 144
Voilà. 144 pixels. Add this to our original vertical resolution, 1920, and we have 2064. Funny thing is that even if you set this to a different DPI, it still works. Let's try the case on mine. I have 48dp navigation bar height with 432 DPI.
px = 48 * (432 / 160)
px = 48 * 2.7
px = 129.6
Add up that 129.6 to 1790 and we'll have, well, 1919.6 but you can round that up to 1920.
I can also consider those pixels making babies, that isn't off the logic.
Cheers!
F4uzan said:
Your second assumption is correct. The absence of navigation bar causes the app to assume the physical screen size (or so called resolution) wrongly. Here we see the app trying to add or subtract its available pixels (for example, on yours its 1920x1080, on mine with navigation bar, it's 1790x1080).
The way I (or anyone) can know it's the navigation bar is due to the only number increasing or decreasing is the physical vertical size. So, how do we know precisely what's causing the size to increase apart from assuming it? Maths, that's what.
First, we should know that everything on your screen is displayed in a metrics known as 'dp', density-independent pixels. This metric relies on the dpi, pixel density per inch. Thankfully, this metric can be easily converted to dp, with the formula of:
px = dp * (dpi / 160)
Thanks to the peeps at the Android Developer Support Site for supplying the formula.
So, we have our formula and metrics. Let's insert the numbers.
We know the size of navigation bar is constant, 48dp, whichever or whenever you are, as long as it has a navigation nar, it's 48dp. Of course, some ROMs have a feature to resize this to your willing. But, we aren't going to factor that, we're going to what the standard says.
Then, the DPI is a pretty easy variable to figure out, it's 480.
Punch the numbers and you have:
px = 48 * (480 / 160)
px = 48 * 3
px = 144
Voilà. 144 pixels. Add this to our original vertical resolution, 1920, and we have 2064. Funny thing is that even if you set this to a different DPI, it still works. Let's try the case on mine. I have 48dp navigation bar height with 432 DPI.
px = 48 * (432 / 160)
px = 48 * 2.7
px = 129.6
Add up that 129.6 to 1790 and we'll have, well, 1919.6 but you can round that up to 1920.
I can also consider those pixels making babies, that isn't off the logic.
Cheers!
Click to expand...
Click to collapse
Wow didnt thought of this kind of extended answer. Thanks for that .
This explains so much
so long
DeMon
Related
Using AndroSensor, I get the following output from my HD2:
800x480
160 dpi (custom set)
Logical Density: 1.0
X DPI: 254
Y DPI: 254
Refresh Rate: 60Hz
32-Bit colour
Which looks fine. But the One X gives:
1280x720
320dpi
Logical Density 2.0
X DPI: 345.0566
Y DPI: 342.23157
Refresh Rate: 58Hz
32-Bit colour
Why are the X and Y DPI values different? Should they not be the same for a square pixel ratio?
Also, a minor thing but why a refresh rate of 58Hz and not 60? Is AndroSensor just not reading it right?
The reason I ask about the X/Y DPI thing, is that the screen jumping bug looks like a monitor trying to autofit a non-native resolution signal, and perhaps this is related somehow?
Or are the physical pixels not square?
I have no idea but I'm going to post here so this thread is not forgotten in time cuz if this is related to the screen flickering issue (that isn't really gone with 1.28 OTA) I think it deserves more attention
Dave Trouser said:
But the One X gives:
1280x720
320dpi
Logical Density 2.0
X DPI: 345.0566
Y DPI: 342.23157
Refresh Rate: 58Hz
32-Bit colour
Click to expand...
Click to collapse
None of those DPI values are correct for the screen anyway which is roughly 312dpi.
The odd values are from DisplayMetrics in Android itself. Android tries to be device independant and a lot of the "pixel" values are actually Density Independant Pixels which need to be converted to physical pixels.
I don't think this is significant. My One X has exactly the same values and it doesn't have the screen corruption or tearing at all.
It makes sense then. The refresh rate is meant to be at 60, not 58, or else you get flicker. I remember seeing an identical problem on a monitor recently, where the refresh was slightly off 60 and caused flickering. This could be what's causing it. I will run a test on my other HTC One X that seems bug free to see if it is also running at 58. The one I'm posting from is currently doing 58.
So I've been messing around with wallpapers on my Galaxy Nexus (Jelly Bean 4.1.1). I've tried several 720x1280 and 1440x1280 wallpapers and didn't crop any of them (or rather, I selected the whole image when it prompted me to crop them).
Now we all know that the Galaxy Nexus has soft keys at the bottom (96 pixels) and a status bar at the top (50 pixels). Obviously, if selecting an image with 1280 pixels in height, parts of that image will be cropped.
There are two "logical" ways that the Galaxy Nexus can do this:
1- Crop 96 pixels from the bottom and 50 pixels from the top.
2- Average them out --> (96+50)/2 = 146/2 = 73 (crop 73 pixels from the top and bottom and display what's left in the centre).
But it doesn't seem to be doing either one of those. After messing around with Photoshop and comparing different crops, I've come to the conclusion that the Galaxy Nexus is in fact cropping a total of 146 pixels, but it's doing it backwards.
It's cropping 96 pixels from the TOP of the image and 50 pixels from the BOTTOM of the image...
Now this isn't a big deal or anything, but who decided to do it this way and why? It seems like a lot of trouble for nothing.
What's up with that?!
The same thing happens with tablet wallpapers. I don't know why either. http://www.rarst.net/hardware/android-tablet-wallpaper-size/
The link above says:
- area to the top becomes visible in applications menu;
- area to the bottom becomes visible in home screen settings menu;
Click to expand...
Click to collapse
But I don't see that at all. There is no background showing in my app drawer on my ASUS tablet. And I don't have a "home screen settings menu".
ive wondered about this too.. ive never looked into it but now you have i wanna know why they do it like this!! weird
Phhoenyxx said:
So I've been messing around with wallpapers on my Galaxy Nexus (Jelly Bean 4.1.1). I've tried several 720x1280 and 1440x1280 wallpapers and didn't crop any of them (or rather, I selected the whole image when it prompted me to crop them).
Now we all know that the Galaxy Nexus has soft keys at the bottom (96 pixels) and a status bar at the top (50 pixels). Obviously, if selecting an image with 1280 pixels in height, parts of that image will be cropped.
There are two "logical" ways that the Galaxy Nexus can do this:
1- Crop 96 pixels from the bottom and 50 pixels from the top.
2- Average them out --> (96+50)/2 = 146/2 = 73 (crop 73 pixels from the top and bottom and display what's left in the centre).
But it doesn't seem to be doing either one of those. After messing around with Photoshop and comparing different crops, I've come to the conclusion that the Galaxy Nexus is in fact cropping a total of 146 pixels, but it's doing it backwards.
It's cropping 96 pixels from the TOP of the image and 50 pixels from the BOTTOM of the image...
Now this isn't a big deal or anything, but who decided to do it this way and why? It seems like a lot of trouble for nothing.
What's up with that?!
Click to expand...
Click to collapse
Man, you got a loooooot of free time
Sent from my AOKP Nexus using xda Premium
When I'm logged out, it's OK. (Chrome browser, 1024 points wide screen.)
Please use the 1024 width style - the default style for the forum is greater than 1024 pixels for it's min-width. The selector is at the bottom of the page on the left.
bitpushr said:
Please use the 1024 width style - the default style for the forum is greater than 1024 pixels for it's min-width. The selector is at the bottom of the page on the left.
Click to expand...
Click to collapse
Thanks a lot for this tip! It was really annoying to be forced to scroll sideways all the time. Shouldn't this be the default theme? In my opinion webpages should always scale to the display resolution and 1024 px is probably good enough for mobile phones and most laptops still out there.
I'm using an X41 thinkpad, firefox 20 something on linux in fullscreen.
haraldhh said:
…In my opinion webpages should always scale to the display resolution…
Click to expand...
Click to collapse
I agree: Never before have a I had a problem with a website in my portrait-mode, 1080 x 1920 monitors …
The 1024 is working out rather nicely, despite the implication of, well, "1024 on a 1080 screen," but still: Why is it a manual switch?
As the title says I've already set the phone to QHD+ (3120x1440), default factory setting was FHD+ (2340x1080)
I've also set both Font Size and Display size to Small
Yet pretty much everything remains still pretty big.
In my old phone (Razer Phone 2) after I make these changes I get a lot of screen real-state space back, but that doesn't seem to be doing much.
To simply put it, I want to be able to read a long text per row, than having the same long text wrap around a few times, regardless if they are the Title of a web page, SMS text, email, whatever.
For example:
When I run Waze (GPS nav) in the 1+9 Pro everything is Large, the GUI (user interface) is taking up too much screen realstate, yet on my old phone (RPP2) after making those same size changes everything reduced in size, opening up the Map to show a lot more streets and area.
Size:
5.72 inches, 90.2 cm2 (~72.0% screen-to-body ratio) RP2
6.7 inches, 108.4 cm2 (~90.3% screen-to-body ratio) 1+9 Pro
Resolution
1440 x 2560 pixels, 16:9 ratio (~513 ppi density) RP2
1440 x 3216 pixels, 20:9 ratio (~525 ppi density) 1+9 Pro
See technically speaking our 1+9 Pro should be able to show lot more stuff on screen, yet I actually get a lot less than from my old RP2.
Trying to figure out if I'm missed any additional Settings I could change from the stock OS, or perhaps we'll need some 3rd party Apps like Screnshift to tweak the ppi or some other hack that we could use.
AllGamer said:
As the title says I've already set the phone to QHD+ (3120x1440), default factory setting was FHD+ (2340x1080)
I've also set both Font Size and Display size to Small
Yet pretty much everything remains still pretty big.
In my old phone (Razer Phone 2) after I make these changes I get a lot of screen real-state space back, but that doesn't seem to be doing much.
To simply put it, I want to be able to read a long text per row, than having the same long text wrap around a few times, regardless if they are the Title of a web page, SMS text, email, whatever.
For example:
When I run Waze (GPS nav) in the 1+9 Pro everything is Large, the GUI (user interface) is taking up too much screen realstate, yet on my old phone (RPP2) after making those same size changes everything reduced in size, opening up the Map to show a lot more streets and area.
Size:
5.72 inches, 90.2 cm2 (~72.0% screen-to-body ratio) RP2
6.7 inches, 108.4 cm2 (~90.3% screen-to-body ratio) 1+9 Pro
Resolution
1440 x 2560 pixels, 16:9 ratio (~513 ppi density) RP2
1440 x 3216 pixels, 20:9 ratio (~525 ppi density) 1+9 Pro
See technically speaking our 1+9 Pro should be able to show lot more stuff on screen, yet I actually get a lot less than from my old RP2.
Trying to figure out if I'm missed any additional Settings I could change from the stock OS, or perhaps we'll need some 3rd party Apps like Screnshift to tweak the ppi or some other hack that we could use.
Click to expand...
Click to collapse
In dev options change the dpi to a larger value, stock is 384, smaller text etc is larger number. I like 411 ...
zoman7663 said:
In dev options change the dpi to a larger value, stock is 384, smaller text etc is larger number. I like 411 ...
Click to expand...
Click to collapse
Are you referring to the setting "Smallest width" ?
it's set to 411 dp by default.
other than that, I can't seem to find an actual setting for "dpi" which is what I was looking for as well.
AllGamer said:
Are you referring to the setting "Smallest width" ?
it's set to 411 dp by default.
other than that, I can't seem to find an actual setting for "dpi" which is what I was looking for as well.
Click to expand...
Click to collapse
Yes, mine was defaulted at 384 but doesn't matter. Raise that value and things on the screen will become smaller.
zoman7663 said:
Yes, mine was defaulted at 384 but doesn't matter. Raise that value and things on the screen will become smaller.
Click to expand...
Click to collapse
That did the trick.
I set it to 525 maximum for this phone, now I got alot of screen space, feels good, less claustrophobic
Damn I thought 450 was small wow lol
i set mine to 601 - which is phablet, and also switches the keyboard layout (enter key isn't on the bottom left, where i find it to be an annoying position). Pretty tiny - but lots of real estate. G
Just out of curiosity what smallest width number are you guys running? I know you can make some adjustments to display size/font size in display settings but I'm talking about the number you set in developer options. I'm running 512 looks pretty good to me. The options in display settings didn't allow me to go as small as I wanted.
znel52 said:
Just out of curiosity what DPI are you guys running? I know you can make some adjustments to display size/font size in display settings but I'm talking about the number you set in developer options. I'm running 512 because that is the DPI listed on all the spec sheets for the screen. Looks pretty good to me.
Click to expand...
Click to collapse
Do you mean DPI or PPI?
If you are referring to PPI (jea 512 is the P6 Pro max) this does not change the actual PPI of the screen (obviously), only sets DPI scaling (ability to adjust the size of on-screen content).
Decreasing the value will give you larger icons and make text easier to read.
Increasing it will make on-screen elements smaller and fit more content on the screen.
You can also achieve that with the Pixel launcher built-in font & screen size options, so I don't really see the point here. (Settings -> Display -> Font size / Display size).
Morgrain said:
Do you mean DPI or PPI?
If you are referring to PPI (jea 512 is the P6 Pro max) this does not change the actual PPI of the screen (obviously), only sets DPI scaling (ability to adjust the size of on-screen content).
Decreasing the value will give you larger icons and make text easier to read.
Increasing it will make on-screen elements smaller and fit more content on the screen.
You can also achieve that with the Pixel launcher built-in font & screen size options, so I don't really see the point here. (Settings -> Display -> Font size / Display size).
Click to expand...
Click to collapse
The point is pretty simple, the adjustments in the display settings only go so far. I want on-screen elements smaller than those settings allow. Smallest options in settings gives you a minimum width of 484 and I wanted a higher number. Guess I should have just said the smallest width settings in developer options.
510 here and much preferring it!
Morgrain said:
Do you mean DPI or PPI?
If you are referring to PPI (jea 512 is the P6 Pro max) this does not change the actual PPI of the screen (obviously), only sets DPI scaling (ability to adjust the size of on-screen content).
Decreasing the value will give you larger icons and make text easier to read.
Increasing it will make on-screen elements smaller and fit more content on the screen.
You can also achieve that with the Pixel launcher built-in font & screen size options, so I don't really see the point here. (Settings -> Display -> Font size / Display size).
Click to expand...
Click to collapse
Hi! I'm sorry to bother you but I have a question, that is, you see my phone is oppo f9 and I have 432 dp and I'd like to change it to 700. Can I change it to that number? if yes, does it affects my phone performances? The "developer options" is quite new for me, so I'd like to ask before taking action
I have been running smallest width 720 for a few years now, which I think translates to something like 320dp. I ran the same on my previous Note phones. It takes me a minute to focus in the morning but I enjoy the extra space and viewing websites in full desktop mode instead of fisher price mobile versions.
It's really up to you to fiddle with the number until you find something that works for you, but I can verify 700+ works fine without breaking anything.
FWIW I ran it at 1024 for awhile too, that didnt break anything either but was too small for me. I don't know what the exact cutoff is but at a certain resolution you'll notice that Android and apps will flip over to a tablet experience. I prefer this, but it may influence your choice.
592 dpi also with 6 pro and 7 pro
anyone using Poco X3 NFC ? any suggestion on your smallest width ?
Only tried up to 800 so far. Maybe try 1024 once i very comfy w 800.