Opera Mini 19 beta for Android
-
A Former User last edited by
-High Saving perform poorly.
a) If it gives error page, then for that period all the pages would do the same. I guess it is a server issue?
b) often times, with heavy/poorly coded sites the page will freeze, but only the page. Menu, tabs etc. works normally.
c) some sites with interactive layout have some issues. usually the image placement in screenshot, etc. a little off. (See one of Jakartanotebook.com product entry)These problems exist in O18 for a long time, I hope by the time it reaches stable they will be fixed, cause from what i've read and seen so far it seems that O19beta has just aesthetic changes.
@xirit32 :
- for Opera for Android I don't see why it won't adopt the features from the mini if the team see fit. they are from one company, right?
- for turn off images in High Saving, it maybe possible with ad-block-esque approach. Who knows?
Opera has built its mobile base around Mini so Opera for Android comes at a second or... last place. Mini is updated with every WebView update immediately, while O for A sits at a chromium version of 50 while chrome beta is on 53. That shows a lot doesn't it?
About turning off images I'm not sure this works as it's currently "fake" in O for A, when you use extreme mode in Mini the browser switches to the presto engine which cuts from the client side a lot of stuff, it's not a matter of heavier compression, you can check in html5test.com for example how much is being disabled. We need a similar approach, from the client side.
Cookies are not the same for the same reason they use different engines and probably different servers. But what needs to be fixed is that Mini does not keep you logged in if you close and restart the browser in any mode a thing that works fine in O for A.
-
Deleted User last edited by
updated opera mini 19 beta to 19.0.2254.106904
running well and no hiccups so far, appears more stable than the first beta.
the changed ui feels quite useful, definitely a keeper.
one would wish for the adress field without google, though. and maybe a cookie management.
many thanks, cheers.
-
kululuz last edited by
-High Saving perform poorly.
a) If it gives error page, then for that period all the pages would do the same. I guess it is a server issue?
b) often times, with heavy/poorly coded sites the page will freeze, but only the page. Menu, tabs etc. works normally.
c) some sites with interactive layout have some issues. usually the image placement in screenshot, etc. a little off. (See one of Jakartanotebook.com product entry)These problems exist in O18 for a long time, I hope by the time it reaches stable they will be fixed, cause from what i've read and seen so far it seems that O19beta has just aesthetic changes.
@xirit32 :
- for Opera for Android I don't see why it won't adopt the features from the mini if the team see fit. they are from one company, right?
- for turn off images in High Saving, it maybe possible with ad-block-esque approach. Who knows?
Opera has built its mobile base around Mini so Opera for Android comes at a second or... last place. Mini is updated with every WebView update immediately, while O for A sits at a chromium version of 50 while chrome beta is on 53. That shows a lot doesn't it?
About turning off images I'm not sure this works as it's currently "fake" in O for A, when you use extreme mode in Mini the browser switches to the presto engine which cuts from the client side a lot of stuff, it's not a matter of heavier compression, you can check in html5test.com for example how much is being disabled. We need a similar approach, from the client side.
Cookies are not the same for the same reason they use different engines and probably different servers. But what needs to be fixed is that Mini does not keep you logged in if you close and restart the browser in any mode a thing that works fine in O for A.Mini is not actually updated with every webview.It is Opera for Android.
The difference can be highlighted loading twitter and different web apps based on google and other progressive web appsand I just love the PGAs
the image off option is not fake...but in case of secure connections like Google and wikipedia or other shopping portals
the opera turbo proxy does not compress the data.
As you can see in many secure connections the old pestro engine does not work in case of Opera mini
So,actually Opera is more secure than mini if you want high privacy.I prefer to use opera as default rather than mini because of its seamless browsing experience
Opera also supports serviceworker scripts which can work offline.If you look just at the core,Opera is much advanced than mini -
A Former User last edited by
Mini is not actually updated with every webview.It is Opera for Android.
Opera for Android is based on chromium and as I said it's sitting currently on chromium 50 while chrome beta is using chromium 53 so its been some time after it was updated for the last time (>2 months).
Mini with no compression or on high is using WebView, that's a fact and you can check it searching for it in these forums or the official blogs. Or visit some "about my browser" site and check the agent. In extreme mode mini uses the "old" presto engine 9.8/12.16the image off option is not fake...but in case of secure connections like Google and wikipedia or other shopping portals
Yes it is I've tested it extensively with only http sites and with data monitoring applications and it consumes almost the same as with setting it to low quality images and certainly at least 20% more than opera mini on the same settings. Try testing it for example with opera max.
So Opera for Android is quite useless to me, the only things I'm missing from it are the ones I've requested in my previous post. -
d-wa last edited by
Opera has built its mobile base around Mini so Opera for Android comes at a second or... last place. Mini is updated with every WebView update immediately, while O for A sits at a chromium version of 50 while chrome beta is on 53. That shows a lot doesn't it?
I thought it was Blink or something.
About turning off images I'm not sure this works as it's currently "fake" in O for A, when you use extreme mode in Mini the browser switches to the presto engine which cuts from the client side a lot of stuff, it's not a matter of heavier compression, you can check in html5test.com for example how much is being disabled. We need a similar approach, from the client side.
Extreme compression made possible because there's server (which actually have the Presto engine) in between which loads all completely first then compress and send it to client. I don't see how this gonna be applied to client device utilizing WebView. Maybe this could explain OfA's behaviour.
Unless like I mentioned block the image files before it loads. After that just need to figure out the image frame.
Cookies are not the same for the same reason they use different engines and probably different servers. But what needs to be fixed is that Mini does not keep you logged in if you close and restart the browser in any mode a thing that works fine in O for A.
As a matter of fact it did save my login sessions, but I don't know, it randomly log me out once in a while.
For shared cookies, there's must be a way, I believe. -
A Former User last edited by
Opera has built its mobile base around Mini so Opera for Android comes at a second or... last place. Mini is updated with every WebView update immediately, while O for A sits at a chromium version of 50 while chrome beta is on 53. That shows a lot doesn't it?
The difference comes from the engine. While OfA render a webpage like a PC browser (built-in engine), OM utilize Android WebView on client device for High Saving.
I know that already as you can see from the bold highlights, I was commenting on why O4A lags so much in updating compared to Mini even though they are the same company as you 've said
But what needs to be fixed is that Mini does not keep you logged in if you close and restart the browser in any mode a thing that works fine in O for A.
As a matter of fact it did save my login sessions, but I don't know, it randomly log me out once in a while.
For shared cookies, there's must be a way, I believe.Check it again with high savings on wifi for example, in this forum or any other, including Opera's blog which uses Disqus, you always have to login again if you close the browser and load it again. O4A with data compression on works fine as expected.
-
d-wa last edited by
Yeah, that's why I edit my post.
And for the second point the WebView is a dependency. It didn't comes with each of mini's updates. It's in the device.
You can't compare the two for it.Check it again with high savings on wifi for example, in this forum or any other, including Opera's blog which uses Disqus, you always have to login again if you close the browser and load it again. O4A with data compression on works fine as expected.
I've checked just now. force stop it, facebook not logged out.
But writing this, once I post comment I've logged out? Maybe it just this forum?
Does 'data savings on wi-fi' have any effects?
-
A Former User last edited by
a) We have a known issue that in very rare cases, the network does not work until you restart the browser. This is by far the client issue.
Actually that's not rare at all, you only have to load up some other app that is using a VPN like Opera Max or Surfeasy who change the IP (connect, disconnect etc.) and you get this behavior.
Maybe it just this forum? Does 'data savings on wi-fi' have any effects?
You are right it doesn't happen with some other forums I 've just tested right now, only with this and with disqus logging. (Wifi compression on)
-
hammerjoe last edited by
where is the user agent option? i want the desktop vesion of a website and i keep getting the mobile version.
-
mvtreo last edited by
Please bring back the "find in page" button. It was substituted by the arrow button (redundant, IMHO).
-
jackob11 last edited byOpera Mini beta 19.0.2254.106904 frequently crushed on my device. The built in adblocker has some problems. After I disable the adblcker & browse internet. Many website notify me that 'I've adblocker enabled' So, I check it again but it was disabled.
Thumbs down. Booooooooo !!!!! -
jackob11 last edited by
It seems Opera Mini beta got update today (just saw this via Opera Mini)
https://play.google.com/store/apps/details?id=com.opera.mini.native.beta&hl=en
But what the heck? Still I'm not getting any update via Google Play. Then I try some online downloader which can able to fetch & download play apps via web browser. Such as apk-dl.com
& it shows Opera Mini beta got an update today (24 august) but it still the previous version "Opera Mini beta 19.0.2254.106904"
What's this ?????? -
miyukiwork Opera last edited by
Now we have pushed a new beta today. In this version, we focused on fixing bugs. If you have any problems, please let us know.
-
A Former User last edited by
Like jackob11 said it's nowhere to be found in Google Play. What is the build number of the new version?
-
-
jackob11 last edited by
Still I'm not getting any update from Google Play.
For me, it's showing the previous version which was updated on 17 August
Any direct link to download the new version ??? -
-
A Former User last edited by
Just now as well, took a while. @miyukiwork Please fix bug ANMEXT-26271 regarding the vanishing of the navigation bar when selecting/copying text while in fullscreen mode with status bar (classic layout), a very annoying, browser breaking bug that is also in Mini Stable for quite some time.
-
miyukiwork Opera last edited by
@xirit32, thanks for reporting the issue. We'll look into ANMEXT-26271.
-
miyukiwork Opera last edited by
@xirit32, scrolling up gives you the bottom navigation bar again right?
