@xirit32 In this version, we've mostly removed the experimental UI elements we included in the previous versions.
Significant improvements will come in next versions. (No, 6 months is not the new release cycle, so we'll release faster than that )

At this time only Samsung Browser Beta is faster by using a trick.

When scrolling down or up in Samsung Browser Beta, JavaScript gets a low priority. Which makes scrolling the highest priority task. Many websites for example use JavaScript or rather abuse JavaScript for demanding code that executes simultaneously while scrolling.

Currently Opera Mobile Beta does not have this 'give JavaScript a lower priority for fancy effects' multithreading idea implemented.

I tested many websites and scrolling is always the most important task for a fluent experience. Since those fancy effects while scrolling with JavaScript or whatever are far less important.

Then Opera at Android takes the lead in effectiveness and smoothness over Chrome, Samsung again.

And for all browsers I can say, some websites expect you have the latest very expensive phones, probably since websites developers test mostly on flagships forgetting to optimize their inefficient website design. Since it's cheaper to develop slow fancy website compensates with very expensive phones by the enduser.

I always use tablet mode on mobile and tablet and I am telling you, Ooera is now 2nd. And a very simple thing like Sleep(10); in Opera it's JavaScript code when a user scrolling the website in a loop only in effect while scrolling would make Opera at least equally fast.

Just simple tricks. Once for example the iPhone stopped doing everything except scrolling the website and stopping all other tasks in a webbrowser but their entire OS too. It's called Snappyness.

You could sort all Bookmarks by hand. But there are smarter ways

1 Install Opera for Windows or Opera for Linux etcetera.
2 Create a new user account on the desktop computer, in this example we use Windows. The user account will only be used to manage Opera Mobile so that's why a brand new empty user account must be created.
3 Log out after step 1 and 2 then log in in your special Opera only account you just made. It takes some time and Windows will e.g. say Preparing Your Account.

4 Because of step 1 and 2 and 3, you can now start an empty Opera browser with only a few bookmarks.
5 With Opera Desktop browser connect and synchronize with Opera bookmark account.
6 All your Mobile Bookmarks will now appear in the bookmarks menu. Let is rest a few minutes.
7 Shutdown all mobile devices off connected with this bookmark account it is important your phone or tablet will not interfere.

8 Ok, on desktop go to show all Bookmarks.
9 Right click every folder with your mouse and select 'Sort by name Alphabetically'
10 Repeat step 9 for every sub folder in a folder you want to have in alphabetical order.

11 Your bookmarks will look well very alphabetical sorted, but now the next step, wait 1 minute. Then close Opera Desktop, at the moment you clise Opera Desktop Opera synchronizes back all your bookmarks in alphabetical order this time.

12 Wait 1 minute again. Once again start Opera Desktop, all Bookmarks should be alphabetical sorted, including synchronized back to your shutdown offline Mobile browsers, hence it's very important you did turn off and shutdown your phone and tablet.

That's it, once in a while when your bookmarks are a little messy arranged, simply keep this desktop account at your PC to manage your Mobile Bookmarks. Log out your desktop after closing Ooera desktop second time. Start your Mobile devices up 1 by 1. Start opera mobile on them but not all at the same time. Your Mobile Bookmarks are now managed and made alphabetical with your desktop computer.

Ready! Let me know below, it looks so much nicer in the way I manage my bookmarks on a desktop PC and it's simply right click on a desktop but undoable on Mobile.

Firefox has it the same.

******* Answer 1 *******

What about fix for this odd search bar? Happening quite often if I call app from background...

Also tonsof bugs are still not fixed and were reported even last year. Quite speed of snail...

If you enable auto rotate and move your mobile or tablet from Portrait to Landscape mode physically the screen content should rotate too. Then rotate back. Is the Address/Search bar visible as it should be? And if you go back from Landscape to Portrait again does that temporarily fix this bug?

******* Answer 2 *******

The last version 42.6.2246.114522 does not open the main page of the WiFi router Asus RT-N65U. After entering > > the login and password, a blank page opens. If you restart Opera and try again to open the address of the > > router, the page is opened without authorization. Tried on the Samsung Galaxy A3 (android 5.0.2), Samsung Galaxy > Tab3 (android 4.4.2), XiaomaMi5 (android 6.0.1)

I have the same problem. Following software with a web interface has problems, like some network printers at a fixed IP address in IPv4. Known products problems are:

• Some routers
• Some printers
• Emule and emule mods cannot remember password
• Tixati does not load but password is remembered

The solution to your problem is unfortunately to use Opera Beta for modern experience. And to download Android Opera Mobile that is still functioning on this matter from the Opera FTP site. In the Android directory you will find 3700, that will solve your problem. However you cannot downgrade a Google Play version so you must first uninstall the Google Play normal standard Opera. Then install the Opera version 3700.
(Until Opera has fixed these issues.)

I have contacted several software providers since it happens to be that Google Chrome on Android has these same problems, and Opera and Chrome share the same render engine which obviously changed a lot.

******* Answer 3 *******

How many Opera versions are there for Android?

The latest stable KitKat release is 3700.

From Marshmellow onwards Opera Beta from Google Play as of a few days ago does no longer have microstutter on Marshmellow or Nougat but with Kitkat you should stay with Opera 3700.

This has nothing to do with hardware capabilities. KitKat has an entire different onscreen Hardware Abstraction Layer when you look inside it. So with the same hardware upgraded to Marshmellow suddenly everything works very smooth. Your phone with 2 GigaByte RAM and a Quadcore 1.6 GigaHerz can run the latest Opera Beta fluently provided Marshmellow or later is installed. Did not test Lollipop.

Now there is also at Opera its FTP site in the Android directory OPERA CLASSIC version 12. That version does function at Home Network Webservers and with the software like Emule or Tixati or your Router or your Printer, and it even remembers passwords that Google Chrome and Opera Beta 42 as we speak today cannot remember or login to or perhaps able to login but display stays empty.

So basically you need all 3 kind of Opera's installed. Opera Classic version 12 for Emule, Opera 3700 for KitKat, Opera Beta for enjoying the World Wide Web as it is meant to be.

So there is not yet 1 united browser that does this. To be honest I have Firefox Mobile, Google Chrome Mobile, build in browser from Android, Opera 3700, Opera CLASSIC version 12 and the one I like most Opera Beta from Google Play.

So there are 3 browsers from Opera itself you need depending on scenario. And there are 3 browsers from other sources. So you need 6 browsers instead of 1 single browser. Unless you only visit Web Sites that rely on a single scenario usage only.

Desktop Browsers matured for a very long time, since 1994 I think it became publicly used. So Desktop Browsers evolved 17 years + 6 years equals 23 years to reach a steady state.

Mobile Browsers started taking of around 2007 as commonly used by the public since HSDPA (3G) and 2G Dataplans became affordable. Now Mobile browsers evolved for 10 years only.

In the future people will look back and probably say, how sad for all of us the tragedy, and they have powerful phones in the future I suppose but even better software more mature. And they might say, wow did they really had to wait to boot up a phone or a computer? Speculation. Hope you liked this post.

Opera Beta 42.8.2246.117348

Can many times not reach http printer or other http service on internal network like 192.168.123:8080. After a long time very seldomly it is however functioning.

Opera 37.00 works perfectly

I installed Marshmallow and microstutter in Beta not visible it was KitKat. If you can fix local network devices on whatever port in ipv4 range.

Opera classic 12 functions also properly.

I block regular Opera 42 with the suddenly new enhanced revision of the user interface until when local network works properly to visit webpages for example of a wireless printer or webserver on port 8080.

1 More thing, in tablet mode the topmost 3 bar button popups a far too large window, it should be like menus at top right.

Tested on KitKat, Marshmallow and Nougat. But Marshmallow is best for Note N8000 and Note N7100

Opera programmers can fix it, it started by redisgning of the User Interaction interface.

This is the last stutter free Opera from Opera itself. Version 3700

Verify that it's really Opera server don't install from other sources.

If Opera programmers would use that version as a start all over again point the new overhaul is the only thing to change and errors made or inefficient subroutines can be prevented.

I think the overhaul is mostly done in Dalvik/Art but even then sliding effect of bringing a menu in the screen should not bring my phone or tablet to its knees.

The core render engine is great and is I believe written in Native Development Kit.

That's why I define the Opera browser as 2 seperated programming paradigmas.

I continued using Opera 3700 and don't update the normal version, but every beta release I hope Opera has finally understood what they are missing compared to what Opera had.

Speculation is that Opera has a new development team with not enough experience in User Interaction Interfaces bridged to Native Development Code like the Blink engine core.

The current team is probably so used to microstutter and old Windows 98 animation effects they don't know any better anymore.

I turn into Steve Jobs when I am hungry.

Steve Jobs wouldn't have allowed this and would be very angry. I read Steve Jobs book and he was in language a vulgair man like Mozart but his products were not. Steve Jobs is no longer and me spitting out some language like him wouldn't change Opera development since I have no power and am a customer only.

Sorry, Opera Team you don't know any better anymore, you're used to slow, buggy, and stutter even on high end devices so much.

I turn into Steve Jobs when I am hungry and want to scream! #*#$^&/&^

[quote]
From cbabb7

https://forums.opera.com/topic/19662/navigating-with-links-stops-working

Video Example: https://youtu.be/JXI2NLiV9Pc

Problem: Tapping a link in Opera will sometimes not advance to the page until clicked multiple times. This happens multiple times daily.

Reproduce: Tap a link while browsing a webpage. There isn't a particular page this happens on consistently. My example shows Google results page.

Results: I expect the link tapped will take me to the page, however it does not. I have to tap it multiple times.

Android: v7.1.1
Device: Pixel
Opera: v42.5.2246.114172

[/quote]

Seems related to what I described as Microstutter in the main Overhaul of Opera Topic.

Opera consists of 2 important parts. The user interface that forwards your messages like finger input like wanting to scroll or to click towards the underlying Render Engine (the actual displayed content)

I have several times urged the Opera team the following:

1 It takes the User Interface time to fully grab user input, this causes on my Note 2 and Note 10.1 microstutter and unexpected bumps in scrolling which I unfortunately do observe on your video too.
2 Underlying Render Engine for the website therefore receives a query full of messages from the User Interface suddenly at once causing micro stutter.

3 The problem is that the overhaul is more in a graphical design phase than an optimal performance state. Meaning even your highly powered device isn't able to deal with the code from the User Interface.

4 The user interface code needs to be entirely rewritten but then fully optimization in code. The overhaul until now meant 'how it looks' not that it's fully functional.

Solvable? Yes. Remember the core render engine is nothing wrong.

Seems related to what I described as Microstutter in the main Overhaul of Opera Topic.

Opera consists of 2 important parts. The user interface that forwards your messages like finger input like wanting to scroll or to click towards the underlying Render Engine (the actual displayed content)

I have several times urged the Opera team the following:

1 It takes the User Interface time to fully grab user input, this causes on my Note 2 and Note 10.1 microstutter and unexpected bumps in scrolling which I unfortunately do observe on your video too.
2 Underlying Render Engine for the website therefore receives a query full of messages from the User Interface suddenly at once causing micro stutter.

3 The problem is that the overhaul is more in a graphical design phase than an optimal performance state. Meaning even your highly powered device isn't able to deal with the code from the User Interface.

4 The user interface code needs to be entirely rewritten but then fully optimization in code. The overhaul until now meant 'how it looks' not that it's fully functional.

Solvable? Yes. Remember the core render engine is nothing wrong.

@personal1985
Hi, thanks for giving feedback! We will investigate this and see what we can find regarding the stutter issue.

I found an easy way to make Samsung Galaxy Note 2 N7100 and Note 10.1 N8000 or N8010 scroll fluently.

Simple: As long as (in tablet mode) the user interface is visible or either invisible scrolling is perfect. The stutter can be circumvented by an option to always show the Tablet User Interface in tablet mode at the top of the screen. It's very obvious stuttering happens when deciding to scroll in the User interface into the screen. This started with the new user interface.

So a quick solution in tablet mode is always show the top screen menus. My phone and tablet are big enough.

Dirty: I locked my phone on maximum performance 1600 MHz. Yes it works but drains the battery unbelievable fast. No kernel is available to ramp up fast enough the core frequency from 200 MHz to 1400 MHz just to bring in the menu.

Off course I did undo any CPU clocking. It's not the click speed or CPU power but the Opera Team needs to reimplement such a needed CPU spike not happening.

Improved animation like a simple menu scrolling in shouldn't use max CPU since pressing the menu to get bookmarks especially in the beginning stuttered but improved after a few releases later.

Conclusion: Like firefox standard does always shows the tabbar and addressbar I need Opera to give me and others an option to have these bars always visible. Ironically firefox has an option to not always show these bars and then is buggy but no stutter in firefox.

Solvabel: ? Yes, a simple option always show tab bars and adress bar.

I have tested this by scrolling in al directions. Opera wouldn't consume CPU spikes anymore with such a simple solution.

Using latest Opera beta for Android there's endless loading loop on opera's forum page, cannot login, cannot use at all see in video https://youtu.be/8lxmYnDCr_k
Have to write this post using different browser. Fix soon?

Opera Stable 42 does no longer play any H264 or VP9 video anymore.

I urge the Opera team to blacklist Samsung Galaxy Note 2 N7100 and Samsung Galaxy Note 10.1 N8000 on Google Play and only allow these devices upto Opera 37.0.2 the last version before the overhaul. Reason, the new user interface is to demanding and every website stutters. I always have to revert back to Opera 37.0.2 since later versions behave as described and programmers at Opera perhaps forgot efficient programming. As long as Opera sync is allowed for Opera 37 on my devices I will use Opera. After that unfortunately Google Chrome ironically using 1 version higher as render engine is my only option left. Since Google Chrome doesn't stutter despite the latest shared render engine I regret to inform Opera programmers 'Your code is to demanding and far from optimal as an understatement. You have chosen like Microsoft does for rapid development instead of efficiency which is masked by people not knowing any better.' The law of Microsoft is 'The faster hardware becomes the slower our code is because rapid development is compensated by faster hardware so no one will notice'.

Please blacklist mentioned devices. It harms Opera if they see your latest release. Especially compared to Google Chrome.

Used Opera Beta 42 a few hours on Galaxy Note 10.1 (N8000) and Galaxy Note 2 (N7100). Still stutters like playing a game with short excessive frame rate drops.

In this case the game is scrolling whatever webpage from simple pages to complex ones.

I cannot use this except for beta testing. For daily use I still use the in September 2016 released standard Opera. I already mentioned it started with the UI overhaul despite the same Blink/Chromium engine, only the overhaul has changed something very important.

I update apps 1 by 1 in the Google Play store since otherwise I have to put back a backup

Sad.

I'm unwilling to buy a new tablet and phone for Opera purpose only. As verification I used the latest Chrome with the latest Blink/Chromium engine and it works perfectly.

I don't like Chrome from Google, for example Chrome its user interface.

Also I would like the BOOKMARK icon back on the speed dial home page.