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.

Samsung has paid a over 5 million dollar in Italy for deliberately slowing down other software with monthly updates. XDA developers is full with such messages.

Only Samsung software is not affected, and I say Samsung browser which also uses Blink engine even got faster.

It's time to enter the Blink Chromium development website. Samsung advice at XDA to just buy a Galaxy every 2 years is not taken seriously and Samsung its profit net halved. People are telling each other that Samsung does what it has been convicted for.

Samsung doesn't want Opera or any other not Samsung product with exception of mobile games.

I read how to compile the blink chromium engine, and 100 gigabyte and time to compile it and find how Samsung destroys competition is not I am willing to do.

On the other hand people started buying less Samsung since this was a better than One Trick Pony trick, but people are aware.

My galaxy S3 from 2012 with opensource barebone Android ROM is for example faster than a modern Samsung phone.

I provided several links, but you probably are not having time to read it.

And it might be inappropriate to tell browser development team at a Android phone that their software is deliberately slowed behind usable.

Since the problem is not for all web sites, we'll think it's a web site issue. If you could tell us which sites are having problems, we can check the problematic behavior, but probably not something we can fix on our end.

Why did you change it? It LOOKS more clunky and less stylish and is also less comfortable and user-friendly.

https://forums.opera.com/topic/29626/bad-scrolling/28

Suggested is starting with last post. I can tell what is wrong only unfortunately. Opera like all other chromium based browsers in NDK is ironically to fast.

Included is instructions how to be certain, low end devices don't have this problem.

The Opera UI works fine. It's the viewport at a random website, rather every website making Opera unusable on high-end devices.

on Opera it appears only a blank unclickable space.

It's a known problem and we might be able to improve it in the future.

what exactly lags?

Start page news, web-pages, the UI in general, search suggestions, settings?

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

Thanks for writing us about the title problem. We have got the same change request (back to the old version) from many other users as well. We'll discuss this problem and try to make it better.

Thank You,

We are sorry, but we cannot do much with the access problem.

Please try the following ways:
Check network connections
Check proxy servers and firewalls
Running Windows Network Diagnosis
ERR_CONNECTION_TIMED_OUT
Check the network connection.
Check the cable condition, and then restart the router, modem or other network devices you are using.

Opera is allowed to access the network in firewalls or antivirus settings.
If it is already in the list of programs accessible to the network, try to remove it from the list and add it again.

If you use proxy server...
Check your proxy settings or contact your network administrator to ensure that the proxy server works properly. If you don't think you should use proxy server: Go to the main menu > Settings > Change proxy server settings. > LAN settings, and then cancel the selection "Use Proxy Server for LAN".

Please write in English, so I can follow up better and other people in this thread can also help you as well.