Do more on the web, with a fast and secure browser!

Download Opera browser with:

  • built-in ad blocker
  • battery saver
  • free VPN
Download Opera

Annoyances - please consider addressing them

  • @op-us How those pop-ups look like? Never saw any like that here.

  • TAB becomes a external process so if a TAB crashes, or memory killer of Android kicks in and a not visible TAB is killed, it has to be reloaded in memory again. If you would see process list in a phone developers options, you would see several processes called Opera, usually 1 for every webpage. Enabling developers options is what you need to do and to tell here how much memory free you have? Some phones have much crapware that 4 gigabyte is almost full by just doing nothing. The developers options in your phone can be enabled by pressing the build date of your phone in system settings then in about your phone page. See Google.

  • @leocg
    It slides up from the bottom bar (navigation/tabs etc.) and is about 2.5x the height of the bottom bar. It says something along the lines of: DApp detected. For full experience you need to finish setting up your wallet.
    And the only choice offered is going to the wallet setup "page". No "leave me alone" or "I'll do it later" or "cancel" or anything else as an alternative.

    Also, there's an annoying "Please try the new opera touch" pop-up.

  • @ginger1984
    So, the reason that doesn't happen with opera mini (which doesn't display all pages as they should look like and therefore making opera for android as a secondary browser necessary - apart from the fact that both can't handle domain-based cookie management, so one is setup with, the other is setup without cookies enabled) is that opera mini is not based on chrome (but presto - still?)?
    Thanks for the explanation.
    No stock android running here, so, no(t much) crapware. Lots of tabs though and several apps open at all times. 🙂

  • @op-us how much memory does your device have?

    Webview which is used in Opera Mini is part of system services and used to render almost everything in Android including applications. So such Webview based browser has shared memory and is of much higher priority to not be shutdown.

    Opera Mobile is a NDK native development kitty browser, far more advanced but cannot have shared memory with Webview.

  • @ginger1984

    Thanks for the insights into the workings of android systems!

    According to CPU Info:

    Total RAM: 1350MB
    Available (= free?) (with my use case): ~ 400-700MB
    Threshold (not sure what that means, maybe = minimum of free RAM for system not to crash): ~140MB

  • @op-us tested in developer options, Opera creates here 2 processes using 210 megabytes for each at BBC website. That is with all images loaded. Including Opera master process that's around 480 megabytes.

    Part of memory in your phone is used for the Video GPU, so I think you have 1500 megabytes phone.

    Your phone should be able to do around 3 to 4 pages at BBC website without memory management pushing a not visible TAB its process out of memory.

    In my case I am at a tablet with 2300 megabytes free left.

    How much memory is free with your tool if you open up 3 BBC pages in TABs? Remember to fully brows a webpage, since that will load images for sure.

    Then look after every new extra open page how much free memory. But open old tabs until you notice a tab is reloaded instead of kept in memory.

    Difference here is you are probably on a phone and I now at tablet. I use desktop mode. And modern websites are known to be memory hungry.

    Say for example with 6 pages simultaneously open at your phone in different tabs in opera freeing memory happens. Provided that you test it after scrolling through the whole page.

    If you would test data saving with very low images quality in Opera it would save memory but I understand you want original.

  • @ginger1984
    Yes, just checked for features of the phone online, it's 1.5GB of RAM.

    Also finally checked the developer section's RAM overview:
    "Opera for Android" has 4 entries while having 18 tabs "open", "Opera Mini" has just one entry while having 33 tabs "open".

    Apparently, CPU Info's "available" space/RAM isn't really "free" RAM as the developer's sections RAM view shows some 65MB of free RAM while CPU Info about 400MB "available"... On the other hand, in the developer's sections there are two view options, "processes in cache" and "active services". With the latter the free RAM value matches the value of CPU Info.
    With "processes in cache" the opera instances are shown and shows a lower value for free RAM.

    On both versions of Opera data saving is activated.

    So, the limited RAM seems to lead to "Opera for Android" to have to auto-reload the pages. I just thought it was a "feature" as a few versions back opera finally made it optional to have a new tab opened automatically after a certain amount of time of idle (or something along these lines...)... 🙂

  • @op-us impressive how you learned to diagnose the technical details. If you like it you can search at internet How Android Memory Management Works. My S8 can for example open many tabs without reloading while my galaxy S3 from 2012 with 748 megabytes RAM or 1 gigabyte if GPU RAM included can only open 3 tabs without reloading.

    Websites became at a level that consumes a lot of memory. Hence I advise people if possible to have 6 gigabyte RAM or at least 4 gigabyte of RAM.

    Also the Android operating system started asking more RAM.

    Thanks for learning that important open tabs in your situation probably are preserved if you close other tabs first.

  • @ginger1984

    Sorry for the long delay of my reply - I always forgot to go here when I was on the pc. And when I remembered I was afk... 🙂

    Thanks for helping and steering me in the right direction to discover some more insight into ARM, android and opera!