@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.
Best posts made by op-us
-
RE: Annoyances - please consider addressing themOpera for Android
-
RE: Annoyances - please consider addressing themOpera for Android
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 -
RE: Annoyances - please consider addressing themOpera for Android
@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...)...
Latest posts made by op-us
-
RE: Annoyances - please consider addressing themOpera for Android
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...
Anyway...
Thanks for helping and steering me in the right direction to discover some more insight into ARM, android and opera! -
RE: Annoyances - please consider addressing themOpera for Android
@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...)...
-
RE: Annoyances - please consider addressing themOpera for Android
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 -
RE: Annoyances - please consider addressing themOpera for Android
@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. -
RE: Annoyances - please consider addressing themOpera for Android
@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.
-
Annoyances - please consider addressing themOpera for Android
Not specific to the current version (52.3), but still there are the following annoyances.
-
Autorefesh of tabs after a while when switching tabs.
In my experience it's useless and rather annoying. Pages are - in my experience - only from cache, so no real refresh is being done. It's a waste of time as one has to wait for the autorefesh is done to reload the page manually to get a real refesh of the respective page. Also, in this day and age, many webpages are dynamic pages that automatically push new content. Again, in these cases an autorefresh is unnecessary, a waste of time and thus annoying.
-> Therefore my request would be: Please make autorefresh of tabs optional. -
Crypto wallet. I don't need it, I don't want to use it, I have disabled it. But still I get an annoying popup (that I can't make disappear) if some page seems to have to do with cryptos.
-> Please! If Crypto wallet is disabled in settings, please make the browser leave the user be with annoying popups regarding the respective settings. It has a reason why I disabled a specific option: I don't want to get bothered with it! Ever!
Please consider my proposals.
Thank you for trying to make the browser better with each version!Mike
-
-
RE: How to disable javascript - or how to force legacy twitter on opera mini?Opera Mini
@ legacy twitter: Please re-read my post. I didn't say twitter wasn't working with extreme mode. I said legacy twitter not working anymore with extreme mode since a few months back.
But: Since June 4th I have it working again. I did some testing and finally added ma.twimg.com on the black list in adaway. It didn't make any difference. I didn't reboot the device and didn't restart consciously opera. But 1-2 days later finally twitter loaded in legacy/classic design mode again instead of the "normal"/desktop design which requires cookies to be enabled to show content.
So, if Opera didn't do any changes to their "proxy"-server settings I guess blocking that url/domain that hosts twitter's js files using adaway seems to work even though initially it didn't look like.@ search engines: Thanks for the hint! Of course my favourite one uses post, too... But at least I now can add some more.
-
How to disable javascript - or how to force legacy twitter on opera mini?Opera Mini
It all was fine until a few months back.
I was using probably v38.x, cookies disabled, extreme data saving.
And I could load legacy twitter.Then v39.x came out I installed it and a few days later or so I couldn't get legacy twitter to load. I even went back to v38 - which is a p.i.t.a. on android as downgrade isn't really possible, at least not without loss of data/settings - even with backup and rooting etc.
But to no avail.Since then I can't read twitter anymore as twitter will not set any cookies on my watch and twitter won't let me see anything without cookies - as I can't get opera mini (now v42) to load twitter legacy. Which even works on desktop (any browser) - just disable cookies (and maybe javascript), but that does not work on opera mini anymore.
I read somewhere in another context that opera changed the behind the sceenes settings for the server that feeds the data saving modes. So maybe Opera enabled javascript for twitter in data savings modes i.e. on that feeding server. I don't know. I only know that I don't like what happened a few months back (maybe march or february 2019?).
Is there any way to disable javascript on opera mini (or maybe opera for android) or way to it rather easily via firewall or other blocking?
And as we're at it: When will opera mini or opera for android finally be able to enable and disable features on a domain basis and not just generally for all sites? There are sides that I will never ever allow to set any cookies - that's why I have to use both opera browsers available for android, one that has cookies enabled and one that hasn't.
Also, why can't I set a custom search engine? The default ones are not to my liking, especially in opera mini. And having to go via the startpage which is just a fancy way of bookmarks, is a little old-fashioned for my taste.Cheers,
Mike -
RE: Opera for Android 46Opera for Android
Thanks for the reply.
I re-checked. First on another phone not to wreck my fully set one again.
Result: No difference between v45 and v46 regarding the "full screen button" on the other one.
Reassured by this I went to update the first one too, again.
Result: No "full screen button". The screen size is slightly smaller than on the test phone, but that should not make any difference for Opera v45 vs v46.
So I just checked if the display orientation might have to do something with it. Changed it from fixed on landscape to automatic and turned the phone - and back.
Result: Now the "full screen button" is displayed again in v46 on the first phone, too.Strange behavior. But glad I was able "fix" it.
So, thanks again for your reply.
Btw: As for the "look" of it: The button was just missing and all the others evenly spaced over the bottom bar. As there was now one button less to accommodate there was a little more space between all the buttons ("back", "forth", "home", "tabs" "opera/menu") compared to the situation including the "full screen button".
-
RE: Opera for Android 46Opera for Android
Is it just me or has "full screen" mode (on demand) been removed in v46?
Full screen (as in removing upper and lower bar) when scrolling down is nice (but was already there in v45), but doesn't help if the page can't be scrolled at all.
I don't see any "full screen" button in v46, had to go back to v45 (with all the pain that comes with it: reconfigure and re-setup the whole thing because "downgrade" is not allowed).
Did I just didn't see the button?