Had my SGS3 for a while now and it's a true beast of a device, the connectivity alone makes it worth the money let alone the quad core cpu, the rom's that have come along have been great too.
However the issue i've got is the scrolling wallpaper, the way it snaps back when you roll over the last screen and it adjusts the wallpaper back to the other side.
It looks ugly to put it plainly, is there any way to disable the endless loop ? So that when you get to your first or last screen, then they are the edge's and it won't loop over to the opposite side?
Or is there a way to make the wallpaper slide back to the opposite side instead of just flicking from one to the other, it's the only thing that bugs me about the entire system.
I know there isn't any native way to do this besides disabling wallpaper scrolling, that's not what i want to do, i like wallpaper scrolling, i just don't like the way it adjusts with opposite screens.
Hope this makes sense.
Cheers.
Related
anyone having their wallpapers appear just on one side of the screen and other half be black? whats going on? Is this a bug?
I've been having the same issue in landscape. No matter how I crop or what image I use about half the screen is blank and cropped as it was still set in portrait mode. Been hunting for fixes tonight and haven't found anything. I have, however, found a workaround. Multipicture Live seems to have done the trick for me setting the image the way I want it to appear both landscape and portrait with no fuss about cropping. I don't know how much of an added strain it puts on battery life technically being a "live" wallpaper, but at this point it's worth it for me.
Hi guys -
I just upgraded from the Cappy to the Galaxy S2 on AT&T. The phone looks and feels great, but I noticed the colors on the screen are not realistic in some apps. The wallpaper on the homescreen & lock screen looks amazing, but the pictures I take with the camera, and the colors in some of the game apps (i.e. Hanging with Friends) look very different. The colors are over-saturated and dark. I've never had this issue on the Cappy, and was wondering if anyone else had similar problems? I searched online and found the international version has a display mode option setting, which is non-existent on the i777. I tried using the Screen Adjuster app, but it didn't help an awful lot.
Took a screen capture with the phone, but the colors look normal there. Would need to borrow another phone or camera to take a picture...and then will post pics as a side by side comparison on what the screen captures.
Anyone else have this problem and/or know how to fix it?
yuy104 said:
Hi guys -
I just upgraded from the Cappy to the Galaxy S2 on AT&T. The phone looks and feels great, but I noticed the colors on the screen are not realistic in some apps. The wallpaper on the homescreen & lock screen looks amazing, but the pictures I take with the camera, and the colors in some of the game apps (i.e. Hanging with Friends) look very different. The colors are over-saturated and dark. I've never had this issue on the Cappy, and was wondering if anyone else had similar problems? I searched online and found the international version has a display mode option setting, which is non-existent on the i777. I tried using the Screen Adjuster app, but it didn't help an awful lot.
Took a screen capture with the phone, but the colors look normal there. Would need to borrow another phone or camera to take a picture...and then will post pics as a side by side comparison on what the screen captures.
Anyone else have this problem and/or know how to fix it?
Click to expand...
Click to collapse
I assume you are running a stock ROM - if so, I believe Samsung defaults the screen mode to "dynamic" and got rid of the option to select other modes (normal and movie) in their ROMs. Most (possibly all) of the custom ROMs on this forum add that selection option back. menu>display>screen mode.
dandrumheller said:
I assume you are running a stock ROM - if so, I believe Samsung defaults the screen mode to "dynamic" and got rid of the option to select other modes (normal and movie) in their ROMs. Most (possibly all) of the custom ROMs on this forum add that selection option back. menu>display>screen mode.
Click to expand...
Click to collapse
Thanks for the quick response! Yea, I'm still on stock ROM...was thinking of rooting and flashing to a custom one soon. Will report back results of the display after. Thanks again!
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.