I've been having some trouble finding the screen resolution without the status and navigation bars. Does anybody know this?
crossbred900 said:
I've been having some trouble finding the screen resolution without the status and navigation bars. Does anybody know this?
Click to expand...
Click to collapse
I just tried measuring it using the "Pointer location" feature in the "Developer options" menu. I'm not sure how accurate this is seeing as I had to eyeball it, but looks like status bar the top is 50 pixels thick and the navigation bar the bottom is about 95 pixels.
Knowing the resolution is 1920x1200, grabbing some calipers and measuring it out might be more accurate.
Of course, nothing will be as good as breaking into the code and actually seeing the values.
EDIT:
Did a screenshot with the layout bounds highlighted and opened the .png in Paint. I measured 48 pixels for the status bar and 96 pixels for the nav bar. It corroborates what I found in these links:
http://www.transformerforums.com/fo...07-rom-jb-4-3-katkiss-multi-window-tf101.html
http://www.drastic-ds.com/viewtopic.php?f=5&t=99
Yeah, it's a slow day at work...
Sent from my HTCONE using Tapatalk 2
Thank you.
Related
I'm currently using cm9 nightly build and everything works pretty well.
I know that in AOKP we can change the on-screen navibar's colour, size etc and I think it is a great feature. However I just figure out an alternative way to further delay the screen burn-in, sorry I'm a noob i don't know jack about coding...
Is it possible that, in each time, when you turn on your screen, your navibar's keys colour will change randomly. For example, when you turn on your screen, the keys are yellow, you turn off your screen and turn on it again, this time the keys are red etc.
With AOPK, you can disable the Nav Bar and change transparency. Enabling 180* rotation the Nav Bar follows. You can enable Nav Bar options in the Power Menu as well, but that's not exactly convenience.
There is also this gesture app LMT, but I don't use it: http://forum.xda-developers.com/showthread.php?t=1330150
I just hide the top and bottom bar each day with aokp, browse the web with total full screen, and my burn in is gone. Just need to exercise those pixels is all.
The power button menu has a show/hide nav button shortcut, so easy to do.
How long would it take for burn in? Back on my Samsung Vibrant, never had that issue, and it was Super Amoled.
I don't do any fancy things like you guys do. I just rotate my phone from portrait to landscape to where the nav bar is next to the front cam. I do this every time i'm on landscape. That way all the pixels get used/exercised. I don't suffer from any burn in had my phone since Feb.
Andie00 said:
I don't do any fancy things like you guys do. I just rotate my phone from portrait to landscape to where the nav bar is next to the front cam. I do this every time i'm on landscape. That way all the pixels get used/exercised. I don't suffer from any burn in had my phone since Feb.
Click to expand...
Click to collapse
that's a great idea, we can also use our phone upside down with the option rotate 180 degree on. lolol I can't stop laughing when I see myself using my phone upside down lol
ohcanada said:
that's a great idea, we can also use our phone upside down with the option rotate 180 degree on. lolol I can't stop laughing when I see myself using my phone upside down lol
Click to expand...
Click to collapse
Glad I could help Since the front of the phone is pretty much all black doesn't even make a difference to how it looks (cam on the left or right or even down )
I bought my phone from an online store in Romania on February 22.I have warranty and other things, it was brand new. I kept the screen on full brightness, and Dynamic color mode. That's how I like it. I was aware of burn in so I switched colors with a display tester every 3 days or so. Yesterday I noticed that the spot where status bar is used to be in portrait mode is brighter than the rest of the screen when displaying blue, white and grey colors. Brighter not Darker. I searched on Google images and that doesn't look like burn in. It wasn't here until yesterday when I spotted it. It's barely visible with display tester but in Games videos photos and multi colored things it can't be finded, You need to look with max attention. I used Nova launcher to hide the status bar. I also heard that there are 2 different things, image retention which is fixable and permanent burn in. I searched for something like this but I don't seemed to find something good. I don't know what it is,I never browsed the Web without changing the pixels where the status bar is for more than 20 minutes. I heard burn in occurs in extreme cases. I don't know how this happened so that's why I'm asking you guys. I don't know even what to do it bothers me only in display tester, but otherwise the screen is perfect. Please give me an advice because I don't want to have a faulty screen.. Can it even be repaired under warranty for that?
No one knows what's the problem?
Maybe you could post a photo ?
Look at the top of the screen...That's actually what I'm seeing when looking on a blue test background.This kind of discoloration/brightness where the notification bar usually is when in portrait mode.This is not a screenshot or photo ,it's just a blue image that i modified to show about i'm talking about.It also happens on grey and white and cyan .I couldn't take a photo because i have a crap 7 MP shooter ,and one crapper 2 MP shooter on my old Galaxy Y.I tried them both but noone of them can catch thatstrange discoloration/burn-in/brightness
Xda don't let me to post links..That's the link without the X'es so delete X from this link to go to the image hXttp://i4XX4.tinypic.coXXm/2w4g39j.jpgX
I really don't know what this can be.
I have the same problem! I noticed it a few weeks ago. The bar on top, when in full screen mode, is slightly brighter/lighter compared to the rest of the screen. I can see it the most when using the browser. The screen looks slightly more yellow compared to the grayer (or something like that) bar. Remember the bar is not actually there, just the discoloration in its place. I have no idea what is causing this and I'm hoping it's not hardware related.
It ain't hardware if it shows up in a screenshot. Looks like the exact dimensions of the status bar, almost as if it's compositing it or it's shadow placeholder where it expects it to be. Try a different ROM, or install the Simplistic Framework and try changing the status bar's colour and transparency setting, see if it makes any difference.
vanButton said:
It ain't hardware if it shows up in a screenshot. Looks like the exact dimensions of the status bar, almost as if it's compositing it or it's shadow placeholder where it expects it to be. Try a different ROM, or install the Simplistic Framework and try changing the status bar's colour and transparency setting, see if it makes any difference.
Click to expand...
Click to collapse
I wrote that.It doesn't show up in screenshots.I edited a blue picture to look exactly like my phone screen.The problem I think it's the screen itself.And the reason for why I edited a picture is that as I said my shooters can't spot it.Any ideas?Also I use the stock ROM ,un-rooted..Everything stock ,including the notification bar.I just have a custom launcher wallpaper and widgets...
It shows up when you turn the phone in landscape mode as well. It remains on the side as a vertical discoloration where the notification bar resides when in portrait mode. I'm not pleased to say the least.
Techweed said:
It shows up when you turn the phone in landscape mode as well. It remains on the side as a vertical discoloration where the notification bar resides when in portrait mode. I'm not pleased to say the least.
Click to expand...
Click to collapse
Exactly what's happening to me.
Made in china phones r crap..made in korea by samsung is gud quality
If you have the warranty the warranty, why not use it? Since the problem is from the phone itself.
This is same like what happen to OG note..i thought sammy already solve the problem when they using RGB instead of pentile on our note 2.. this is not good...
I check mine, so far nothing yet. But i afraid now!!
Sent from my GT-N7100 using xda app-developers app
naimmkassim said:
This is same like what happen to OG note..i thought sammy already solve the problem when they using RGB instead of pentile on our note 2.. this is not good...
I check mine, so far nothing yet. But i afraid now!!
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I also thinked that it won't happen on Note 2 too ,but here it is.I'll go further and I'll send it in the service ,after my holiday ends.This thread is good to maintain active because it may help people that also came along this problem
I always set brignest to auto and screen movie mode. So maybe it did save mine from that problem
Sent from my GT-N7100 using xda app-developers app
naimmkassim said:
I always set brignest to auto and screen movie mode. So maybe it did save mine from that problem
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
My phone was on Dynamic and Full Brightness all the time.I love oversaturated and bright screens.LOVE AMOLED <3
Well I found a solution to the problem. It takes time to pull off and is still a work in progress for me but it's working.
I created an image that matched the resolution of the phone screen. I then made a rectangle at the top of this image that presents the exact size of the status bar and colored it white. The rest of the image was colored black.
I installed an app that keeps the screen on without dimming when plugged into the charger. Overnight I display the image I created with the screen set to stay awake and don't dim at full brightness. So what you see is a black screen with a full brightness white strip where the status bar is supposed to be.
This process quickly "ages" the status bar area and it slowly starts to match the rest of the screen. I've been doing it for almost a week and the difference between the two sections of the screen is starting to diminish. I bet a couple more weeks of this and the difference between the two sections will be gone.
I got the problem as well. And I'm telling as many people as I can because I'm annoying like that. Seriously, I hate the fact that I spent such money on faulty phone...Samsung galaxy note 2. <blech>
Unfortunately, Camera has stopped.
Hello everyone. Most of us are familiar with the intense light bleeding at the bottom of the device that shows up in light backgrounds and low brightness. It can get really distracting in some videos or games when the brightness is low. So, since replacing it has little chance to fix this, i took a lool at my Nexus 4 and noticed how the navigation bar stays on the right in landscape mode. This would hide the bleeding on the G if properly rotated. There must be a way to force the position of the nav bar to a specific side on the screen. Any ideas how this could be accomplished? The GDA app unfortunately is incapable of hiding the normal nav bar for me.
Sent from my Nexus 4 using Tapatalk
Morning all.
I am trying to make a fancy battery bar widget using 4 progress bars each curved 90 degrees and rotated to make a full circle, and each individual bar only showing a 25% range of the battery level, so bar 1 is 0-24%, bar 2 is 25-49 % etc.
What I'm trying to do now is split the bars into sections depending on the battery level, so when the battery is below 75% but above 50, I want the 3rd section to split into 5 chunks but have the first two bars stay solid... if you get what I mean.
But I've searched and tried to find the Advanced Parameter for progress bar chunks/splits and I cannot find it. The text on the advanced parameter button in Zooper says "...control almost any aspect of this module...", and I'm not bashing, but is this one option not available or have I missed the appropriate keyword from my XDA/Google searches?
Thanks
Wrong thread
@Mokum020
Thanks for the tip I think that's the way to go.
I'll tell you what as well, trying to get the segments lined up with eachother is a PITA!
Mokum020 said:
How about making two progress bars for each section, one solid and one in chunks and show/hide them with the offset parameter at a certain % level:
Solid
Code:
[ox]$#BLEVN#>=75?1000$[/ox]
Chunks
Code:
[ox]$#BLEVN#<75?1000$[/ox]
Click to expand...
Click to collapse
Very Smart Solution!!!
P.S. I'm a robot
Ratchet_Guy said:
Very Smart Solution!!!
P.S. I'm a robot
Click to expand...
Click to collapse
I thought this was an interesting idea so I built my own version of it, attached. Would like to see the OP's as well if willing to share.
As the OP mentioned getting the segments to line up to the exact pixel/millimeter is easier said than done, but sometimes close enough looks...close enough lol.
Hi Guys, so I've increased the dpi to custom under developer settings to 581. Everything seems to work great except for touch position on the dialer and it's pretty irritating. Anyone knows a solution to this or to selectively reduce the dpi on tbe dialer app? I'm not rooted. Look at the screenshot of the issue. Thanks!
I use 589, and no issues, but with 600, the notifications panel becomes very narrow, but no issues with anything else
i use 480 w lowered font size and "fineprint" font.... everything works perfect
winol said:
I use 589, and no issues, but with 600, the notifications panel becomes very narrow, but no issues with anything else
Click to expand...
Click to collapse
Tried 589 and same issue. Can you confirm you don't have the issue on your dialer? Weird why this would be.
I just double checked, at 589, the dialer is normal, but, I have the screen resolution at wqhd+, fhd gives me some troubles in the zone of the nav bar, and I say zone because I hide the nav bar, gestures work ok, but, buttons appearing there become unresponsive, the same for the bottom row of the keyboard
winol said:
I just double checked, at 589, the dialer is normal, but, I have the screen resolution at wqhd+, fhd gives me some troubles in the zone of the nav bar, and I say zone because I hide the nav bar, gestures work ok, but, buttons appearing there become unresponsive, the same for the bottom row of the keyboard
Click to expand...
Click to collapse
For some reason I still have the issue in the OP screenshot. I've resorted to 520 now with QHD+, things are slightly better on the dialer but still largely the same.