So the scrolling on the notification bar feels about the same no matter which ROM I choose. It is kind of bugging me that when I scroll quickly it is noticeably laggy. This leads me to believe that it isn't some performance setting but some kind of cap. Also, it isn't simple lag because you can watch the screen refresh at seemingly equal intervals when you drag the notification bar. I OCD on the smoothness of scrolling on everything but especially about the notification bar drop down.
Any Ideas?
Edit: So I think there is a soft cap of 60fps and this could possibly be the cause. Is it possible there is a cap specifically for the notification bar? I unpacked the SystemUI.apk just looking around because I am interested in learning more about android but realized that until I learn more about androids functions and syntax there is almost no point. I did look through the StatusBarService file and found where I believe it is tracking the finger and moving the status bar and I did not notice any specific cap in this location. I assume it would be further along into the system.
After all that trouble (not so much trouble to me but w/e) I think it is probably just a system FPS cap that I hope isn't in the kernel. It is not in the build.prop like on some phones or if that changed for some reason.
hope this helps
you can Remove the FPS cap entirely
Debug.gr.swapinterval=0
off=0
Lower fps but no cap = Dyn
on = 1
if its still lagging then you could try finding Force GPU rendering (use 2d Hw accel in apps) (it should be in developer options)
if that doesn't work try adding "persist.sys.use_16bpp_alpha=1" to your build.props and if those don't work , try them all together if you didn't already
Related
First off, grovelling apologies for what is probably a painfully newbie-ish question - I am entirely new to Android phones. I have tried searching - came across this thread, for example: http://forum.xda-developers.com/showthread.php?t=1124669 - but haven't found much in the way of practical solutions yet. This may conceivably be more of an "Android question" than a "Galaxy S2 question" as well, I'm not sure....
Anyway: one of things I use my phone for an awful lot is watching videos. What I'd like to be able to do is get the the display a little closer to a properly callibrated TV - so the whitepoint should be somewhere near D65, proper white balance across the whole grey-scale, the gamma somewhere near 2.2 across the scale, primary colours not too saturated, and so on.
The main problems at the moment seem to be that the white point is pushed quite badly towards the blue, and that the green primary colour is oversaturated (this is in line with the findings in the thread above). So my question is: what can one do about this?
I've investigated the "Display" settings menu, and discovered the "auto-adjust screen power" option which (again, according to the thread above) improves the gamma (reducing black-crush) at the cost of somewhat reducing maximum brightness. I've also spotted the "background effect" option; setting this to "Movie" makes colours a bit less over-saturated, but green saturation still isn't right. And within the standard video-playing application I've got the "colour balance" set to "Warm", which helps with the blue push a little, but not enough.
Are there any other display adjustment/callibration options that I've missed? Are there any apps which allow the display characteristics to be tweaked? And are there any 3rd-party video-playing apps which allow more precise callibration of the overall colour balance without compromising playback performance?
Hi, curious question.
I'm wondering why the Nexus7 doesn't allow you to slow scroll/pan down at single pixel steps. Always seems to be in 2-3 pixel jumps. I got a bad habit of scrolling web pages while reading from iOS but on my N7 I get these kinda anoying start/stop jerks.
Is this related to the virtual pixel resolution being lower than the actual screen resolution? And would changing it allow one to match the virtual pixels to the screen pixels and get smoother slow speed panning?
Anyone know if some custom ROMs optimize for this?
BR
POTS101 said:
Hi, curious question.
I'm wondering why the Nexus7 doesn't allow you to slow scroll/pan down at single pixel steps. Always seems to be in 2-3 pixel jumps. I got a bad habit of scrolling web pages while reading from iOS but on my N7 I get these kinda anoying start/stop jerks.
Is this related to the virtual pixel resolution being lower than the actual screen resolution? And would changing it allow one to match the virtual pixels to the screen pixels and get smoother slow speed panning?
Anyone know if some custom ROMs optimize for this?
BR
Click to expand...
Click to collapse
I have been struggling with this issue for days. Looked into kernel code hoping to find anything related to scrolling or touchscreen but nowhere to find such a thing. It has nothing to do with virtual pixel resolution. If you swipe your finger at a degree of between 45-90 (accapted as scroll up by the system), Y coordinates change by 3 pixels where as X coordinates can change by 1.. Therefore its not a limitation, it is kind of scroll sensitivity which is 3px.. I've seen other devices can scroll by 1 pixel.
I believe google has set this value to 3 because of rendering issues, since its gonna render the screen 3 times more if it is set to 1. Maybe it is the optimum sensitivity. Lower than 3 pixels may disrupt buttery smoothness but its just a guess..
I hope one dev can lead us the right piece of code where it is set to 3 and we can change it ourselves to test the best..
You guys can try the problem yourself actually by installing the "Multi-touch accuracy check" app from market, which shows the exact pixel of the touch..
the xy coordinates readout from the developer "show touches" setting shows the 3pixel increments too.
when panning something just a bit faster than dead slow then suddenly gets rid of the jumps and goes smoother as well.
could it be a battery saving thing that they just get rid of taxing the cpu/gpu when people like me do these constant slow scroll pans on webpages and books etc.?
POTS101 said:
the xy coordinates readout from the developer "show touches" setting shows the 3pixel increments too.
when panning something just a bit faster than dead slow then suddenly gets rid of the jumps and goes smoother as well.
could it be a battery saving thing that they just get rid of taxing the cpu/gpu when people like me do these constant slow scroll pans on webpages and books etc.?
Click to expand...
Click to collapse
2 more thoughts:
a) this relatively coarse sensitivity can lead sometimes (not often) lead to a +/-3 pixel uncertanty in a UI element and cause it to jittter - sometimes happens when finger pressure changes.
b) I had for a while thought that it may be linked to the size of the touch sensors on the display. Being a lower cost device I figured that the HW resolution may be lower than pixel count. But I'm pretty sure that you must be always hitting multiple sensors and the system should just interpolate to a finer resolution.
POTS101 said:
the xy coordinates readout from the developer "show touches" setting shows the 3pixel increments too.
when panning something just a bit faster than dead slow then suddenly gets rid of the jumps and goes smoother as well.
could it be a battery saving thing that they just get rid of taxing the cpu/gpu when people like me do these constant slow scroll pans on webpages and books etc.?
Click to expand...
Click to collapse
When scrolled a little bit faster, it still increases by 3px , not 1.. I also assume that it is about battery saving but if I can find a way to decrease the step size, I'd love to try it by myself..
Also It can be related to the sensors , as you mentioned, but not likely.. It can catch 1px changes when swiped horizontally..
Any news on this?
As far as I can see, this is only related to touch screen; if you use a usb mouse, you can actually see the scroll by one pixel at time, and there is no graphical issues. With mouse all seems smoother...
At this point, I think It's an hardware issue of the touch screen, as the system can easly support 1px scrolling
aLPaSLaN07 said:
I have been struggling with this issue for days. Looked into kernel code hoping to find anything related to scrolling or touchscreen but nowhere to find such a thing. It has nothing to do with virtual pixel resolution. If you swipe your finger at a degree of between 45-90 (accapted as scroll up by the system), Y coordinates change by 3 pixels where as X coordinates can change by 1.. Therefore its not a limitation, it is kind of scroll sensitivity which is 3px.. I've seen other devices can scroll by 1 pixel.
I believe google has set this value to 3 because of rendering issues, since its gonna render the screen 3 times more if it is set to 1. Maybe it is the optimum sensitivity. Lower than 3 pixels may disrupt buttery smoothness but its just a guess..
I hope one dev can lead us the right piece of code where it is set to 3 and we can change it ourselves to test the best..
You guys can try the problem yourself actually by installing the "Multi-touch accuracy check" app from market, which shows the exact pixel of the touch..
Click to expand...
Click to collapse
My two cents...I tried this approach and when you move your finger with about 5 degree you can get 1 pixel change by Y and 3 pixels change by X. And if you move your finder with about 85 degree you get 1 pixel by X and 3 pixels by Y. It seems that hardware can handle the 1 pixel change by X or Y. It looks like the touch events are throttled by the system based on the distance between points.
There is no decent and satisfying answer to this yet .. I'm still waiting for a solution..
I was really happy with my LG G5, until after a week or so, I noticed that the screen actually seems to have problems with "fast" change of movement. And I am really annoyed at this point by it, because I compared it with other devices of mine, and it's not that bad on these older devices. For example my old phone, a Samsung Galaxy S3, doesn't have this issue at all.
You can easily notice it in the Android settings (use list view). When you now slowly move up/down with your finger, you see that all fonts have a "ghost-effect" (get blurry) of not properly refreshing in time. There is a bit of border / re-draw affect around each word on the screen.
You will notice it also for example on the app store scrolling down / up, or in an app drawer (if you have a launcher with app drawer) and scroll through the app list.
On my phone i have no ghosting or problems with fast change of movement. There is a website called "testufo" where you can test your display for ghosting and FPS.
Title, pretty much. I change my color settings and they only apply to the dual screen when attached, and not at all when disconnected. It's the exact opposite with specific game settings. I can change a game's resolution and framerate settings and this works on the main screen, but NOT on the dual screen. When I swipe the app on lower settings from the main screen to the dual screen I can see the resolution increase.
EDIT: Specs - Verizon model, newest update. Which I'm irritated about because I kept myself on the base firmware this whole time waiting for root and finally gave up, hoping it would fix this, along with a plethora of other issues. It fixed some of the minor ones, but not the big ones like this or others.
Do you think it would be possible to achieve variable refresh rate of Xperia 1 mark 3 screen?
I mean display instead of always running in 120Hz or 60Hz would run in 120Hz when scrolling and even in 1Hz or 10Hz when nothing moving on screen (for example reading or watching a picture).
That would help with battery life and reduce the heat.
We could select to always run in 120Hz or in hybrid mode.
Do you think software can do this?
I think it's possible if someone work with software or fw.
the real question is if Sony will work on that (probably not) or if modding community will work on that when and if TWRP or other rom will support Xperia 1 III.
Maybe (but this is just a big speculation) with the new android release google will support variable refresh rate inside Android
Unless the screen can run at those refresh rates, sony can't do anything. if the hardware is not capable, software/firmware can't do anything. My take on this is if our xperia 1 III had vrr screens, sony wouldve already implemented it in their android to take advantage of it. so therefore, our screens most likely aren't vrr and therefore stuck at 60 or 120hz.
as for the 40hz in game mode, the screen still runs at 60hz as per developer settings show refresh rate, so it only reduces the fps of the game, not the refresh rate of the screen.
I think probably we will get the "ProMotion" feature on an update. I hope sony does it.
What is ProMotion feature?
Since this device was released tbh we didn't receive any new feature/function or changes to better for our phone.
Apart from reducing cpu's clock speed to reduce abnormal extreme heating there are either feature removals (like Music - disablement of downloading metadata from Internet) or just security patches... Literally nothing. I still hope for vivid mode for better colors and many updates to camera (4k 60fps in main camera, 21:9 picture s in main camera, night mode, better quality as I noticed some blur on the edges + pics are too soft). Also hoping for better battery utilisation and maybe bring back super stamina mode.
And bring back sony Album and other xperia iconic apps :/
Sony Album can be side loaded from APK Mirror. I loaded it but deleted it because I saw no benefit...YMMV. I believe there are other "Sony" apps available there also.
Indeed it is available and still working, but we do not know for how long it will work, especially after new system updates. Like android 12, then 13 etc