Does some one happens to know visible pixel height? notification bar takes cca 40px and soft keys around 80 i think, but i would appreciate if some one knows exact pixels.
ty
ok, so if anyone will be interested in this, android pixel calculations are not so simple, found some infos
http://developer.android.com/design/style/metrics-grids.html
http://www.brandbuildercompany.com/...-independent-pixel-formula-for-mobile-devices
But for simple things like wallpapers, i measured that visible height is 1133px (for 316dpi), that way notification bar and soft keys won't cut the image, correct me if i missed something.
Related
I searched and came up with nothing. Is there a MOD available to reduce the size or hide the soft key bar all together (restoring with some gesture maybe)?
The idea being you would have more screen real estate at all times. The reality is we don't truly have a 4.65" screen, its more like 4.4" (unless watching video). This becomes especially annoying when using the browser...those soft keys take up a good .25" of screen real estate!
I would even be happy to cut the soft key bar pixel-width in half and use the 3 small dots like in the camera app.
Hi guys. I'm the proud owner of a Galaxy Nexus with no screen defects (except for black splotches that only show up on black screen in a pitch dark room, so that doesn't matter). My brightness usually remains around 15%. It's been only 2.5 months, and I've noticed something. If the screen is displaying WHITE (with the top bar and the navigation keys hidden), the top-right of the screen has a slightly blue tint (at the place where the clock, WiFi, and the signals are displayed, and these elements are usually blue as you might know). I know I'm acting like a little OCD, but that's what my observation is. I don't want my beautiful screen to depreciate this way
My question is, how do I avoid this burn-in?
In addition to that, I also want to hide the on-screen navigation keys (but that's not a priority right now, would be good if you could help with that as well). In short, I want to avoid all sorts of burn-in to this AMOLED screen due to elements that are constantly displayed on the screen (like the navigation keys area, the status bar (and the clock, battery etc.).
Sorry if this is a repeated post or if this isn't the correct section. I've searched the forums but didn't find a solution.
Thanks in advance...
There really isn't much you can do about the burn in, specially on SAMOLED displays, it's part of their life cycle. One thing that does come to mind to slow down the burn in is to use something like PA's PIE, which turns the nav and status bar areas into usable real estate.
The bottom row of pixels on my screen, when lit, are significantly brighter than the rest of the display. It's only noticeable when the background behind the back/home/app-switcher buttons is transparent or they are completely hidden.
Is/was this a common issue? I don't see this sort of problem mentioned in the other display issues thread(s).
Is there anything I can do at this point about this?
Hi,
can somebody please tell me how to add the 3rd row of quick setting toggles in the Oreo update like it was with Nougat?
I've tried Oreo for the third time now but several things simply don't work anymore or got worse in comparison with Nougat.
I could live with a few of those but only having two rows of quick setting toggles is definatily not one of them.
I tried gravitybox (it's missing the option to manage the vibration strength of the virtual buttons and the battery tile now has additional text which takes up all the space so the temperature part isn't visible anymore.)
Furthermore I had to buy a substratum theme to not vomit from the white quick settings panel. With the march security update the installation is now as tedious as with Nougat due to the forced reboot.
The Xposed module HowGiveLolli doesn't work anymore and the centered normal letters instead of all upper case was a real nice feature.
Why are the points in the settings app regrouped so it's harder to find specific settings?
There are simply so many bad design choices in my eyes I can't bring myself to live with Oreo due to not finding substitute functions for the missing ones.
Kind regards
I know you posted this last month so you hopefully figured it out, but either way I thought I'd share the answer since someone else might want to know in the future.
It has to do with the display scaling in Settings\Display\Advanced\Display Size. If set to default or large, you only get two rows of quick settings. If you set to small, the UI shrinks and as a side effect you get three rows of quick settings tiles. You can always increase the font size afterward if it's too small, but reducing the display scaling is the only way to have enough room to display three rows.
ABQNM said:
I know you posted this last month so you hopefully figured it out, but either way I thought I'd share the answer since someone else might want to know in the future.
It has to do with the display scaling in Settings\Display\Advanced\Display Size. If set to default or large, you only get two rows of quick settings. If you set to small, the UI shrinks and as a side effect you get three rows of quick settings tiles. You can always increase the font size afterward if it's too small, but reducing the display scaling is the only way to have enough room to display three rows.
Click to expand...
Click to collapse
Thanks for posting the solution. I simply restored my Nougat backup as I never upgraded my bootloader for that matter. I don't think I'll be using Oreo until I get a new phone which possibly can't be a Moto Z3 because I'm not really convinced they will release anything more than the Z3 play.
ABQNM said:
I know you posted this last month so you hopefully figured it out, but either way I thought I'd share the answer since someone else might want to know in the future.
It has to do with the display scaling in Settings\Display\Advanced\Display Size. If set to default or large, you only get two rows of quick settings. If you set to small, the UI shrinks and as a side effect you get three rows of quick settings tiles. You can always increase the font size afterward if it's too small, but reducing the display scaling is the only way to have enough room to display three rows.
Click to expand...
Click to collapse
Hi and thanks for this trick : as a matter of fact I was always on "small" in Nougat and it worked nice with 3 rows, but with Oreo I needed to switch to "smaller" to switch from 2 to 3 rows :silly:
Seems like lots of pixel devices are suffering from screen burn in of the home buttons. Anyone else notice how annoyingly bright they are? Seems like it causes permanent damage after a while. What's everyone's thought on the issue? Does Google need to fix this or I am just in the minority in seeing this issue come up on multiple pixel devices?
It changes it's colors in Pie so no problems so far with 4 months old phone. Using bright wallpaper to get grey bars most of the time and dark themes to get color shifts from white to grey more often here.
I use "fluid n.g." for navigation, it gets rid of the possit of nav bar.
I also use the quick tiles apps to add immersive mode toggle to my quick tiles, I use it to put the status bar in immersive mode to hide it. So now status bar burn in.
No item is stationary on my phone. Burn in is the last of my problem, I've learned my lessom