hi,
Is there any way to reduce scrolling speed in the P10? It's just way too fast, you just either keep your finger on the screen or you swipe and it goes all the way down the page. In the P8 I has more control, slower swipe would mean slower scrolling, faster swipe - faster scrolling. Also slowing down was very linear. There's no such thing in the P10, if I want to go to something in the middle of the page "slow swipe" doesn't make any difference - it scrolls through 95% of the page and then quickly slows down near the end. It's not linear at all. And I'm not talking only about third party apps, same applies to the settings or multitasking menu.
Related
Hi, there's one thing I don't like in the galaxy note: I noticed that the scrolling speed of lists or any screen isn't natural, it's faster than my finger.
Probably Samsung did it because it has a wide screen so we don't need to make too wide gestures, but I don't like it. I have big hands and I would prefer a natural scrolling speed (1x).
Is there a way to achieve this?
Thanks
I just upgraded from a Galaxy Tab (original) to a Nexus 7, and while most everything else is a sweet upgrade, scrolling has become a consistently frustrating experience.
On my Galaxy Tab (Gingerbread), scrolling is simple and intuitive. I "flick" my finger across the screen and it scrolls fast (even if it might be too fast sometimes) and the inertia continues the way I would expect (more like Froyo as opposed to iOS), and swiping scrolls as fast as I swipe no matter how long I press my finger to the screen. However, on the Nexus 7, if I flick, sometimes it flicks fast, sometimes it flicks very slow, and sometimes it comes to a dead stop when I release my finger. If I swipe, it behaves better, but doesn't seem to go the speed of my finger unless I hold it down longer. I feel like a little kid trying to get a toy to work. It's not intuitive, and I'm not sure if the problem is the design of Jelly Bean or the Nexus 7's hardware, or the device has a manufacturing defect. As a comparison, the homescreens flick and swipe appropriately most of the time. Apps seem to have the same scrolling frustrations for me as the browser and settings lists.
Can someone tell me how Jelly Bean is supposed to work with flicking and swiping? What about in apps like Chrome, games like Devil's Attorney, or settings lists? Also, the homescreens.
If can adjust Android's default scrolling speed and inertia (and swiping and flicking responsiveness) through root, I'll do that, but I'm not sure there's anything else I can do before that.
Just saw this today, have not tried it yet myself but it sounds like this is what you are looking for.
http://forum.xda-developers.com/showthread.php?t=2082060
Nexus 7 touch response FIX
Sent from my MB855 using Tapatalk 2
I installed the Jelly Bean update and immediately noticed the scrolling is different.
There's 2 ways to scroll, you can put your finger down and drag it where the page moves in sync with your finger, or you can flick it and let it coast up a bit.
If you want to scroll 1 page by dragging, you have to move your finger the entire height of the screen. If you scroll through hundreds of pages that becomes way too much repetitive work and hurts your hand.
Luckily there's some roller physics like the page is on wheels, so if you drag a little then let go it won't just stop, but will coast a little further then decelerate to a stop.
Then if you do a faster little flick, you can cause the page to scroll 1 whole height by moving your finger a much smaller distance. Then if you wanted to scroll hundreds of pages, instead of dragging the full height, you can use smaller flicks to move from page to page.
But in Jelly Bean, it didn't work that way. It felt like the page was heavier, with more friction, where when you let go from dragging it didn't coast much and slowly decelerate, it was very abrupt coming to a halt and didn't move beyond where you let go.
Then if I did a tiny flicking motion like I always do to change pages, it didn't work. It moved only a small amount, not a page, and it didn't coast where I could then keep flicking it to make it quickly scroll through.
It was like the friction was up, and in order to fling you needed to use more distance and speed, and then it would just go quickly really far. In ICS it was more sensitive, with more variation in between, where you had finer control over how far it rolled.
JB was like the wheels were all rusted and barely wanted to turn, so you're trying to push this shopping cart like it's a huge brick where you have to scoot it with each push and it's not rolling.
I tried a complete reset, I tried editing the build.prop properties for min and max fling velocity, and I tried the latest release from another country, but it was the same. So I flashed ICS back on, and immediately it was so much smoother and less effort to scroll through many pages.
Anyone else notice that? The global scroll physics in JB changed. It's not just some apps, it's everything, including the settings pages. I was surprised I didn't see anyone mentioning it, since just trying to use it for a short while cramped up my hand.
And this is called lagging, I assume. All note users of jb roms complaining about.
Sent from my GT-N7000 using xda premium
Lag has to do with speed of response. I saw that too. Like when I pulled down the top menu drawer I could see the buttons at the top drawing in chunks, instead of instantly appearing and animating smoothly. Scrolling in general could be choppy, and the whole interface felt sluggish.
But this is different. This is settings in the physics. The Android views have friction settings (like getScrollFriction()), and I assumed Samsung modified them from how they were for ICS.
Besides the heavier friction and less sensitivity for flings, it'd also mess up when trying to scroll. Very often I'd just do a normal attempt to scroll down a webpage a little with a short movement down, and it'd instead go up! The opposite direction.
ICS doesn't do that, and everything is much faster feeling, more sensitive. Which was surprising because the main reason why I wanted to upgrade was for the "butter" thing where it was supposed to feel smoother.
The home screen seemed smooth though. Well, after it loaded fully. There was a delay, when it paused and waited for all the icons to preload, and then once it did it started moving again and was smooth. But before that it was chunky.
I was hoping someone knew if there was a configuration file to modify those global friction settings. I don't know if you can set friction in build.prop, the fling settings didn't seem to do much if anything. That wouldn't fix the lag, but it'd be better if the physics were the same as ICS.
That's the first thing I noticed when I upgraded from ICS to JB.
It felt like flingy. It felt much more anchored.
I think it's 'project butter'.
Since I got my S21U 3 months ago I noticed the One UI Home Apps where you swipe right and left in either the drawer or on the pages. The transition is not smooth like it should. it is not lag, it is like random frame drop happening while moving left and right through the UI icons. I didn't notice fps drops in the settings or normal scroll in apps.
It is just that weird random fps drop during animation icons transition in the main page/drawer.
I have tried everything possible, from full reset to manually disabling services by package disabler to monitoring the CPU/GPU usage and FPS to forcing fixed 120Hz and I couldn't find a fix.
I am using the G9980 Snapdragon version 512GB/16GB
I noticed it as well. Comes And goes randomly.
Had an A72 with OneUI 3.1 with the same issue as well.
I love this phone, but there is one huge annoyance, there doesn't seem to be a way to make the screen actually run at a sustained framerate.
I have it set to 144hz in the menu, but it routinely drops to 60fps or 120fps depending on the app
This normally isn't a big problem, except nova launcher only runs at 60fps and so scrolling the app drawer is incredibly bad.
Pokemon Go also only runs at 60fps...and since the game operates at 1/2 vsyn, the effective fps is only 30, which is atrocious compared to the 72fps it runs at on the ROG6
Don't confuse Screen Refresh Rate and Frames Per Second. Totally different things.
jwoegerbauer said:
Don't confuse Screen Refresh Rate and Frames Per Second. Totally different things.
Click to expand...
Click to collapse
I mean... Not really
Obviously the screen always runs at a refresh rate of 144hz because it isn't a VRR display(as far as I know that doesn't exist on phones)
So what you are changing in settings is always the frame rate that the phone is rendering at.
Your phone should ALWAYS be rendering at the frame rate you select in the settings menu... But this phone doesn't seem to do that, and it's annoying because it makes the usage experience worse than every other phone I have
BigDog87 said:
I mean... Not really
Obviously the screen always runs at a refresh rate of 144hz because it isn't a VRR display(as far as I know that doesn't exist on phones)
So what you are changing in settings is always the frame rate that the phone is rendering at.
Your phone should ALWAYS be rendering at the frame rate you select in the settings menu... But this phone doesn't seem to do that, and it's annoying because it makes the usage experience worse than every other phone I have
Click to expand...
Click to collapse
Most of the reviews I've read/watched confirm what you've said. When you set 144hz, it runs that way in the default launcher and all the menus, but when you open certain apps, if they don't support 144hz natively then they just don't run at 144hz. The reviews seem to indicate that the developers of said apps need to enable support for 144hz.
So I was poking around the settings, and entered developer mode. There's an option to force the screen to stay at 144hz at ALL TIMES. It's called LOCK REFRESH RATE. I was able to confirm this works because there is also an option to SHOW REFRESH RATE which displays the screen refresh rate in the upper corner of the display. Before I locked the refresh rate, I used the show refresh rate function to view the refresh rate using different apps. In the phone menus, and app drawer, and google feed, etc the phone would remain at 144hz. But when opening some apps like Chrome for example, the refresh rate would drop to 120hz, etc. However, when I LOCKED the refresh rate in the dev options, the screen refresh rate stayed at 144hz in EVERY app and scenario I was in. It does state that this will drain your battery more rapidly when selecting to lock the refresh rate in the developer options. FYI