I was given a Samsung J5 with an old copy of Android Marshmallow where I disabled most of the animations that would irritate and annoy me.
I don't use it for the browsers, only for making calls, taking pictures, writing a few notes (with some tools I found that were free and not ad paid for)
Now the for pictures I found this tool but had to patch the bootloader to make it work,
https://apkfab.com/samba-filesharing-for-android/com.funkyfresh.sambaIt was built for phones with extra buttons but the J5 only has 3. I found by depressing the two excluding the middle brings up the menu but have to keep holding down then use another finger to select then it will open the settings but after letting go it will go to a screen to select open programs and I'd just reselect.
So I when I take pictures, turn on the wifi, open a shortcut and copy it over but on a newer Sony phone with Lineage missing those buttons no chance to access the menu but I got it working in a way that it is useful without many of the animations, suggestions and predictive word stuff. I do see a few dimming overlays that I can't turn off like when adjusting the brightness which I find stupid because it darkens background more that I am trying to get the measure of behind the brightness slider.
There was this
touch overflow overscroll thing I can't remember the setting name of it now that I was able to turn off in Android Marshmallow but still appears in Android 9:
https://www.eevblog.com/forum/dodgy-technology/dimming-madness-with-chrome-and-mobiles/msg3580326/#msg3580326and an increase with these things but darker that hurt my eyes when most of the screen/background flips from light to dark to light excessively:
That's some of the reasons I despise them when animations/decoration(excessive dimming/flashing) that interfere causes me discomfort to my eyes that I can' turn off. Before I installed Linageos on this Sony phone the stock firmware had this screen that use to suddenly appear with gestures I couldn't turn off and a version of Microsoft swiftkey that had no setting to turn off suggestions, spell checker, predictive stuff and in settings just something about collecting the words I type and sending it to Microsoft labs for analysis... what an insult and they won't allow me to free up room on the keyboard with things I don't want or need. I found I couldn't install the original Android keyboard that I know have settings to disable that stuff so that's when I found Lineage but still many animations I find I can't turn off.
I have seen someone's new Android phone some months ago just setting up the wifi details and noticed the brightness adjust no longer dims as I was adjusting it to low.
Still seems to be an issue:
https://support.google.com/pixelphone/thread/132936922/how-to-turn-of-android-12-overscrollEdward van Raak Mar 25, 2022
This isn't only messing with people eyes. While the screen is in this bouncing animation clicks aren't registered. This is incredibly annoying if you flick a page up and then quickly select a radio button, or text or list item or whatever.
However came up with this idea at Google probably is causing millions upon millions of unnecessary clicks around the world each day. And nobody is outraged.
Or maybe this is just my OEM, but still, WTF!
User 495737937406355213 Apr 26, 2022
The overscroll effect is awful, and makes me dizzy every time I see it! I've disabled animations to get rid of it, but that causes problems in various apps. Please, please make it possible to turn off the overscroll effect.
User 2013977589997406614 May 8, 2022
This makes me feel literally sick as well, who could think it was a good idea?
I wonder about the amount of work that may into this sort of stuff:
https://stackoverflow.com/questions/39277258/overscroll-glow-not-working-on-scrollable-div-in-webviewOverscroll 'glow' not working on scrollable div (in webview)?
Asked 6 years, 3 months ago Modified 6 years, 3 months ago Viewed 958 times
* I'm having some issues getting the 'overscroll glow' to work on a scrollable div. ** The first problem is finding answers or documentation on this because this thing has a lot of names, I'm not entirely sure what the correct term is and most of them I tried confuse google (i get a lot of results for 'overflow:auto;' etc). So for clarity, here's an image of the effect I'm looking for:
I'm having some issues getting the 'overscroll glow' to work on a scrollable div.
The first problem is finding answers or documentation on this because this thing has a lot of names, I'm not entirely sure what the correct term is and most of them I tried confuse google (i get a lot of results for 'overflow:auto;' etc). So for clarity, here's an image of the effect I'm looking for:
*look, it's overscroll glow!
Anyway, my problem is this: I did have this effect when my html/body elements were scrollable but when I moved things to divs (in this case the .content element), it stopped working.
Something like this:
html, body {
overflow: hidden;
width:100%;
height:100%;
margin:0;
padding:0;
}
.appbar {
position: absolute;
top:0; left:0; right:0;
height:56px;
background-color:#ccc;
}
.content {
position: absolute;
top:56px; left:0; right:0; bottom:0;
overflow-x:hidden;
overflow-y:auto;
-webkit-overflow-scrolling: touch;
}
.make-it-scrollable {
height:200%;
}
<body>
<div class="appbar"></div>
<div class="content">
<div class="make-it-scrollable"></div>
</div>
</body>
On iOS I get the elastic 'rubber banding' effect when I try to scroll past the content (thanks to the -webkit-overflow-scrolling) but on Android I get nothing.
Is this by design? (meaning: is the overscroll effect disabled or 'not implemented' for divs with overflow:x?
Or am I missing something?
Oh btw I'm testing this on Android 5.1 with the latest Chromium based webview (it's a cordova app)
Yes, what good does that do to the user?
Nothing
What benefit does it to provide to them?
None
How does this make the content any clearer?
Interferes and obscures whatever it is covering up
What if the user doesn't want to see this crap?
What about those with light sensitivity?
Tough luck
*"He's having issues" implementing it but what about those it annoys and suffer from it.
** "The first problem" was not a problem before where when it could be switched off pretty much everywhere but now developers like this one are looking to override it and force everyone to see their effect in everything they can for the sake of it like that is more important than everything else.
It seems to me like they are create to make work for themselves by creating problems that were not problems before.