Best posts made by ginger1984

@sirius16 unfortunately cannot get it to work while in other browser it does

Example, make a bookmark that contains this as address and name it scrolldown....

javascript:window.scrollTo(0,document.documentElement.scrollHeight)

In a long webpage using this bookmark should scroll down the entire page.

It did work in the past before chromium engine. In the opera presto engine days it did work.

Pasting this in address bar should have worked too....

javascript:window.scrollTo(0,document.documentElement.scrollHeight)

Duckduckgo does indeed work fine with VPN mode. And it's logical the VPN allows certain traffic kinds like what's used for browsing.

Galaxy S8 has it too. Both in Chrome and Opera. But not in a Webview based browser. I have an Exynos SOC and not a Quallacom unfortunately. Yes it's a Samsung thing. At XDA people noticed it too. Alone the Samsung browser working great is unfortunate.

At these devices Opera Mini does use Webview and yes Webview then it works very smooth.

At my Samsung Quallacom SOC Tablet it works fine, but not at Exynos SOC based phone or tablet.

Rumor has it people with Samsung Galaxy S10 with Exynos SOC have it too.

I prefer Opera, but on Exynos SOC of Samsung it's not Opera.

I am sorry. Since Opera and even Google cannot, without working together with Samsung about Exynos specific details on it, undo this.

If I buy another Samsung, I think I will select it not to have Samsung it's own SOC, the Exynos.

I don't believe Samsung doesn't know. But all Exynos users are probably affected.

Keywords: Samsung Galaxy Scrolling Stutter Chrome Opera

Note: This is not specific to all models, but only certain Samsung SOC, mainly Exynos.

I replied at your YouTube and I recognize it, since it is like as if Scrolling happening only at say 10 frames per second. I can really visually count the number of frames.

Kinetic Scrolling isn't really noticable though.

Sad story, ironically since Chrome has it too, and Chrome is also Webview in Android, questions are;

Why does an application not known as a browser but using just Chrome still works smooth?

Well, I would sit at the table with Samsung if I were Google. Since Google it's browser suffering too, only Samsung Browser or Opera Mini ( used Webview ) are working smooth.

And yes I factory reset, everything, it took months to understand.

It's Samsung doing something. At least at Exynos SOC. Not all Samsung devices have Exynos so Opera HQ team might find perfect smooth Scrolling at supposed same device, though it has same name it might have different SOC.

@samstabauser said in Bad scrolling:

@leocg

no difference between kinetic-scrolling and normal scrolling style? hardly to believe.

by the way

I use a Samsung Tab A 2016 tablet (T580) with current Android 8.1 but Andorid 7 was the same.
https://www.notebookcheck.net/Samsung-Galaxy-Tab-A-10-1-2016-Tablet-Review.171710.0.html

Coud be possible that this bug only exist on certain android devices.
The stutter scrolling behaviour also exist on my Huawei honor 6x.
https://www.notebookcheck.net/Honor-6X-Smartphone-Review.207056.0.html
Thats why i still use older Opera for android apk´s on this device too.

Should really be investigate by software engineers.

one more thing 30 vs 60 fps
https://www.youtube.com/watch?v=ChsT-y7Yvkk

https://www.testufo.com/ (on of my fav tech sites)

My Samsung Galaxy S3 from 2012 spare phone with Lineage OS Nougat works fluently in scrolling. Only because of its 700 megabyte memory I can open 3 websites only simultaneously. But hey it's faster than my 4000 Megabytes memory Samsung Galaxy S8.

I tried scrolling with Samsung Browser in pop-up over tiny window over Opera. In developer options of my phone I enabled GPU profiler, and Webview seems detached from directly getting touch screen input and works very well like Opera mini is smooth.

Samsung browser has a detached from touchscreen directly like GPU profile too.

Communicating touchscreen events directly to Opera or Chrome main thread that is also the viewport seems to be culprit here.

I suggest Opera developers to try a simple overlay window that passes touch events forward to the web viewport in NDK since directly communicating with NDK is problematic. Not only for Opera but for Yandex, Chrome, Brave browsers...

Opera could do this as Opera Dev version e.g.

I turned almost into Steve Jobs. Steve was known for forcing the development team to look for another better way.

@boti99 Message pump overflow from touchscreen events. @miyukiwork maybe you can forward this to your team deciding what is important.

Stutter is observed in such a stable way, that it seems touch events overflow the message que. When this happens, touch events are dropped. Then browser viewport stops responding a short time, perhaps 100 millisecond. Then the touch events message que is ready to be filled with new touch events, and it happens again. As in native development kit Opera seems to not be able to filter out unimportant messages fed from the touch screen. Like it's not necessary to process for example duplicate touch events. This is not happening at all devices.

At least it's such a stable stuttering and so depending on touch events, ask your team for studying how many events a touchscreen can send in so little time. It's rather Opera now wants to process all events but that is unadvisable.

A millisecond pause for example in processing the message pump from touchscreen events can prevent this flood.

https://www.quora.com/Why-does-Android-scrolling-animation-stutter

Managed to solve it. After every firmware update you have to do the following. Which most people won't understand.

Clear Opera App cache
Reboot into official Samsung recovery and wipe cache.
Bootup

Most people including me will give up before especially wiping cache from official Samsung recovery.

But I did wipe it. And everything is smooth for now. Opera seems to be the first app that will stutter but you'll have to clear Opera cache and wipe cache partition. At Samsung devices.

Remember not all people are understanding to go into recovery mode and wipe cache partition. It worked fine but I consider it luck.

Did you update Android webview?
Did you update Opera?
Did you update play services?

If so first reboot and if it doesn't work wipe cache which most people won't understand.

At xda you can find how to wipe cache for a device and that is very difficult for average user.

For now opera is smooth again until webview and firmware updates and so on and on and on.

@nikoseleftherios you solved it. Every browser sends a header when visiting a website. Almost every browser includes the mobile device name. This device name is extracted. The website knows the device name and with java script makes a popup telling what device one has.

I could only make this working without device name at my tablet. In always desktop mode.

The popup is therefore at the website happening.

You now know what actually happened. It isn't something to worry about but it's annoying. Future coming chromium based browsers will omit the device type name.

It is however usually used to decide what type version of a website will be shown. However nowadays the screen size should be enough for websites to know.

@andrew84 this can be fixed.

The smaller image is scaled by the Android graphics device interface. As I tested it too, the smaller images are the results of scaling dark shades. If it would have been light shades it would have worked.

Solution, during animation to small nothing to do. Once at small scale a carefully scaled other image identical but scales and dithered and blurred takes over the full scale image. This must be done for every dull scale image having a small scale duplicate that especially takes dark colors in mind.

There are in fact only 256 shades of grey for example usually and of these shades of grey most people see only difference between 32.

It's because the colors are 256 in blue or green or red drom which in dark areas probably it's more like 16 colors of blue or green or red.

And you and I can see this.

This is why different images that have

Color dithering

should replace it in overview.

This is a limitation in all 8 bit color r,g,b.
https://en.wikipedia.org/wiki/Dither

This requires someone to carefully check and dither small scale images at an AMOLED screen.

Dither is an intentionally applied form of noise used to randomize quantization error, preventing large-scale patterns such as color banding in images.

I have seen this in many applications like at a TV or anything as soon as dark shades are involved. Without dithering images shown in small it would never work. Android cannot do this itself. It simply requires another set of images that are only different in size. But the small scale images carefully dithered. Please see Wikipedia link with how with black and white only it is perfectly possible to show every shade of grey to human perceived eyes.

Figure 5. Depth is reduced to a 16-color optimized palette in this image, with no dithering. Colors appear muted, and color banding is pronounced.

Figure 6. This image also uses the 16-color optimized palette, but the use of dithering helps to reduce banding.

Both images have 16 colors only, but you should see definitely a huge difference.

@inkvizitor install Opera desktop version and login to see, don't forget that with mobile you need:

1 Password

2 Password phrase

I think you didn't input 2, the password phrase.

@darvinya in the past holding that button opened a new tab, now another menu.

@monikataware you require Tasker from Google play, and time to learn how it works. I use it to make opera Fullscreen.

@monikataware tasker can do that I do it with many apps but learning tasker is steep learning curve.

Hopefully opera settings will get an option to hide system taskbar.