Opera Mini 19 beta for Android

lantohsay

lantohsay

v19 beta - split address and search bar..looks like band-aids solution..on phone screen..

Deleted User

Deleted User

hi team,

thanks for adress/search bar. could now please cut the cord between adress bar inputs and google's search suggestions, please?

comments and pics on sites like phoronix.com are now accessible w/ extreme savings off, great.

note to users:
for video playback install tubemate as player app.
works perfectly for me, YMMV.
and get another browser (...cough, uc mini, cough, cough...) for megadownloads

just my 2 centavos,
and many thanks again to the opera team.

A Former User

Since it seems that you have abandoned Opera for Android because Mini is more popular and thus your flagship, please add the following to mini:

-the option to completely disable images while on WiFi savings as well, the way it works with extreme savings and not the way it works on Opera for Android which still downloads them but not shows them, wasting precious bandwidth when using WiFi hotspots on a limited MB/GB contract/plan.

-Text wrap and force enable zoom as in O for Android.

These are very important in my opinion, I won't add minor various other things for the moment. Thank you.

d-wa

d-wa

@miyukiwork :
a) so I assume it won't occur in the next update then?
b) but in a page with gifs I can see the image runs. It's like giving impression that only the interactions are disabled for that page. Like 'I can see but can't touch' thing.
c) I guess you right. but in uc browser it is not misplaced. Though the rest of the page rendered horribly. So yeah I guess it just the site.

more High Saving rendering issue:
a) in (High Saving-only) m.olx.co.id ads entry there's a row of five green icons as a means of contacting but when clicking it, nothing happens. On previous versions it working correctly. If I recall correctly it even works in Extreme. It seems to be JavaScript issue.
b) sometimes Facebook, YouTube rendered incorrectly, like trying to load mobile version in Extreme Mode with single column.

And a crucial thing I found is it didn't share the cookies between the two Savings mode. So, why is that?
Another feature favoured is customizable auto High Saving list. I know it already predetermined but we need to decide on our own.
Thank you.

d-wa

d-wa

@cubot : thanks for the heads up, but I think the team should put a little more empathy on ad-block.
for google suggestions : I feel ya, man! Just as soon as I click the history/bookmark results it turns to suggestions, urrgh! Maybe if they move the suggestions below....

@cinamullah :
For YouTube in Extreme Saving Opera Mini can't play it because in general the mode doesn't support flash, or gif, or active JavaScript. but YouTube providing a link to play their videos to applications which could handle the protocol, namely the official YouTube or other third party apps such as the aforementioned tubemate. that's how it is.

@lantohsay :
I found no difficulties whatsoever over speed dial. Have you tried to scroll?

@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?

jackob11

jackob11

There's a new update release for Opera Mini beta. In my opinion it's a bad update, totally horrible.
Only the main menu bar is changed. What about bug fixes, adding new features, improve current features ??

jackob11

jackob11

Moreover there has no "Search in Page" & "Page Sharing" option in the new menu bar but previous version has. Please bring it back

d-wa

d-wa

So the page specific function moved into the three dots?
I don't know man, I always feel tapping the three dots to be a daunting task.
And here I hope that O menu to be like quick settings panel. Even better if customizable.

leocg

leocg Moderator Volunteer

Moreover there has no "Search in Page" & "Page Sharing" option in the new menu bar but previous version has. Please bring it back

Both are still there when you click on the red Opera icon. No new menu bar here.

kululuz

kululuz

Opera has done brilliant bug fixing issues in the newest beta in the high saving video player issues

But I have a few recommendation on the video player of hotstar and twitter in high saving mode

The video player in hotstar in portrait mode only show half leaving another half with black screen

[](https://postimg.org/image/djx1hkz7v/' target='_blank)

image ru

So I have to make it landscape each time with my screen rotation on to show the video fully...but it is not the fullscreen mode,actually it is a bit better than potrait

<a href='https://postimg.org/image/4q650hc97/' target='_blank'>
photo share

these problems persist in hotstar and twitter videos

Generally by default I turn off screen rotation,but to watch hotstar I have to make it landscape again

Please fix the portrait issue and also make a fullscreen button in hotstar like video players in youtube and facebook.

Thank you :happy:

miyukiwork

miyukiwork Opera

Hi, we have released a new beta yesterday. This version has new main menu layout. We've added Night mode in the main menu and moved Find in page and Share function to "+" option in the address bar.

Let us know what do you thing. Your feedback is valuable to us.

A Former User

-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

Deleted User

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

kululuz

-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 apps

and 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

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.16

the 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

d-wa

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

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

d-wa

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

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

hammerjoe

where is the user agent option? i want the desktop vesion of a website and i keep getting the mobile version.