Opera Mini 10 beta 1 for Android
-
Deleted User last edited by
swipe down to refresh doesn't work in Turbo. also fonts size increases when in Turbo.
Refresh swipe works just fine.
-
Deleted User last edited by
The most impressive feature: night mode settings persist on native player.
-
Deleted User last edited by
swipe down to refresh doesn't work in Turbo. also fonts size increases when in Turbo.
Refresh swipe works just fine.
... on Feeds page.
-
Deleted User last edited by
Reverting (click back) on Opera browser after video playback the top bar is half blocked and scrolling doesn't work until second click back is triggered. I'm guessing that's a functional bug but still is redundant.
-
-
emmausss last edited by
swipe down to refresh doesn't work in Turbo. also fonts size increases when in Turbo. Refresh swipe works just fine.... on Feeds page.
Well the feeds page does not seem to be different from mini mode. As feeds don't even work on opera browser, it may be using mini mode for that.
-
emmausss last edited by
Turbo mode has native video playback support. just streamed a video from YouTube, and it was so fast.
-
vigneshlin last edited by
@sagrid, no bro what i wanted to ask is different story...
opera for android is full browser and using turbo it gives full web experience and its memory is many times larger than that of opera mini... so now opera mini also has turbo mode to display full web experience but with a small memory package...
so what would be the difference between two
-
emmausss last edited by
Turbo has some drawbacks, since it uses server based compression. also opera browser has a fully functional rendering engine, ie chromium, and thus has full support for web based apps and features. I think Turbo was added due to many requests for support for advance JavaScript and HTML 5 support. anyway ios opera mini has Turbo, mini and uncompressed mode, so why shouldn't android get them.
-
-
barsk last edited by
@baunz, it is intentional that Opera Mini leaves night mode after turning off the screen or using other apps. We want to avoid that you pick up your phone in a bright place and are unable to see anything just because you didn't turn off night mode before you stopped using Opera the last time.
-
Deleted User last edited by
@baunz, it is intentional that Opera Mini leaves night mode after turning off the screen or using other apps. We want to avoid that you pick up your phone in a bright place and are unable to see anything just because you didn't turn off night mode before you stopped using Opera the last time.
Persist on lock screen with opera mini in background though, after turning off the screen as you say.
-
barsk last edited by
@emmausss, @vigneshlin, in Opera Mini mode the pages are rendered on the server and Opera Mini just displayes them. In Opera Turbo mode the web pages are rendered on the phone instead.
Opera for Android is a full web browser with the whole browser core built in to the apk so it renders all the web pages completely by itself. To keep Opera Mini small, Opera Turbo in Opera Mini instead uses the browser component built in to Android to render the web pages. So this way it renders web pages locally and gives you the full web experience without actually having a built in rendering engine.
-
barsk last edited by
@baunz, it is intentional that Opera Mini leaves night mode after turning off the screen or using other apps. We want to avoid that you pick up your phone in a bright place and are unable to see anything just because you didn't turn off night mode before you stopped using Opera the last time.
Persist on lock screen with opera mini in background though, after turning off the screen as you say.
It should be disabled after 30 seconds to not accidentally disable night mode if the screen is briefly turned off accidentally while reading a long text without touching the phone for a while.
-
Deleted User last edited by
Turbo has some drawbacks, since it uses server based compression. also opera browser has a fully functional rendering engine, ie chromium, and thus has full support for web based apps and features. I think Turbo was added due to many requests for support for advance JavaScript and HTML 5 support. anyway ios opera mini has Turbo, mini and uncompressed mode, so why shouldn't android get them.
To implement partially HTML5 and ditch that for full support on Turbo doesn't have any sense requested by users or not. I think Opera guys are eager to test Opera Mini native browser and improve Turbo as being the techiest stuff perhaps due to low feedback on Opera Mobile or just following the timetable. In any case doing one move with one purpose only it's a bad strategy.
-
baunz last edited by
Thanks for the feedback... I now understand the importance of the feature going off...
-
Deleted User last edited by
Turn off the screen and turn on again, this forum page being loaded. The scroll is chunked in attempt to scroll up and down. Open another tab + Google search, close that tab + on\off screen thing; result: scrolling problem doesn't persist. Running on a tabled with default app layout, Chrome 30.
-
vigneshlin last edited by
@barsk, so turbo mode in both opera mini and opera for android are same in rendering web pages??
-
Deleted User last edited by
Depending on data sessions at times highlighted terms got an option to be searched with Google Now and other times Search menu doesn't appear. Also http://opr.as/e1x is not linked directly to GP.
Edit: in fact doesn't depend on sessions, from Feeds pages result direct search.
-
hexalys last edited by
A couple things I noticed:
1 - Can't force reload a page yet. Will need a forced proxy refresh.
2 - Text Size has no effect yet. In my case, it uses the Amazon WebView FireOS font size settings as default font size. (be aware of that)
