Opera for Android 52
-
Nevermura last edited byHi there,
Im a designer and I worked some HTML5 ads for a website. One of them have multiple exits (I used the same html5 code as the ads posted via Google Double Click). I use the latest version of Opera available on Google Play and this banner doesnt displays at all.
Any suggestions ? -
A Former User last edited by
@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
-
Nevermura last edited by
I mention I dont use any AD blocker, the rest of ads on the page are ok, only this one, with multiple url's has a problem. I verified and on other browsers it seems to display, on Opera it appears only a blank unclickable space.
-
miyukiwork Opera last edited by
@ginger1984
what exactly lags?
Start page news, web-pages, the UI in general, search suggestions, settings?
-
miyukiwork Opera last edited by
@Nevermura said in Opera for Android 52:
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.
-
A Former User last edited by A Former User
@miyukiwork high end devices send much more information of touch screen events. Here we discussed how we decided it became high end devices with sensitive touch screen overload not only Opera but Al other browsers that currently do not filter message cue.
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.
-
A Former User last edited by
@leocg but this causes pages to run slowly. that's why I turn off data saving. because it connects to another country like VPN. so pages are loading late.
-
-
A Former User last edited by
@leocg and the application uses more than our internet quota. About data saving
-
-
kir last edited by
The new tab gallery is awful... I use 15-20 tabs usually and browsing through them is so uncomfortable now. I downgraded to version 51 again but lost all my open tabs
Why did you change it? It LOOKS more clunky and less stylish and is also less comfortable and user-friendly.
-
miyukiwork Opera last edited by
@ginger1984
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.
-
A Former User last edited by
@miyukiwork all Samsung Exynos SOCs are affected when applications use Blink browser engine like Opera, Kiwi, Chrome, MeWe, Yandex. As long as it does use Native Development Kit to use Blink Chromium engine. It happens at all websites. With exception of WebView browsers like Opera Mini.
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.
-
A Former User last edited by A Former User
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.
-
