Opera Mini 4.1: FULL multiplatform tutorial & review

[Guest Menneisyys]

[teaser]Opera Mini 4.1: FULL multiplatform tutorial & review

I don’t need to introduce Opera Mini for any serious mobile device user – it’s been one of the best browsers ever since the release of version 4.0 with all its goodies like favorite synchronization and full layout mode, the latter being excellent on (W)VGA Pocket PC’s and high-resolution Symbian devices like the Nokia E90. Note that I’ve written a review & full comparison to other browsers HERE – please DO read it if you don’t know what Opera Mini is or how it compares to other browsers, in which cases you might want to prefer it to native, fully-fledged browsers like Opera Mobile. Also, make sure you read my two Web Browsing Bibles, linked from the OM4 article, for additional info & comparisons. Finally, note that the linked article only discusses version 4.0; 4.1 is even better and more featureful.

The just-released 4.1 beta takes things even further and implements a lot of long asked-for functionalities. It’s REALLY worth upgrading; note that it can coexist with older versions (including 4.0) on the same handset. That is, if you, for some reason, find it useless, you can easily switch back to the older version without having to reinstall / reconfigure anything.

1.1 Availability; which version to go for?

[/teaser]

Navigate to http://mini.opera.com/beta either with your phone’s WAP browser or, if you have Opera on your desktop, with it:

(mobile browser)

(Opera on the desktop)

and select any of the upper three links. On the next screen,

just press the left softkey (Continue); then, unless you want to put it in a self-created category, just click OK while it’s on root:

On the following dialog,

just press OK; do the same on the one that follows:

The file will be compiled and you can start it right away by answering Yes on the final screen:

After this, everything is done in the already-known way: accepting the license, pressing buttons for generating a pseudo-random sentence etc.

Note that the 4.1 beta page linked from operamini.com, http://www.operamini.com/beta/, doesn’t contain the signed versions, only the unsigned ones. Therefore, if you only have Mozilla Firefox or Internet Explorer on your desktop, make sure you download the file from inside your Web browser on your handheld. The only exception is BlackBerry, where there isn’t a separate version on the only-handheld or desktop Opera page; then, you can safely download the ZIP file from http://www.operamini.com/beta/ with any desktop browser and use the BB Desktop Manager to quickly install it on your BlackBerry.

If you have a Windows Mobile device with Jbed 3.1, any of the signed versions will do. Note that some people state you need to go for the all-certificate version; that’s not true with Jbed 3.1. Make sure you DO download a signed version and not the unsigned one so that you can easily (without any hacking) can get rid of the security prompts.

Note that, should you still not have Jbed 3.1, read THIS for more info & the download links.

1.2 What’s new?

1.2.1 Custom text input field

With the new URL input field, address autocompletion works just great:

Note that

1, unlike with Opera Mobile 9.5 (and just like any other browser, including pre-9.5 versions of Opera Mobile), the titles of these pages aren’t displayed, only the URL’s

2, copy / paste doesn’t work. If you do need it (and you do have a compatible JVM – it’s only the non-recommended TAO that isn’t), you’ll need to switch to the regular, native JVM URL editor by pressing Delete (right softkey, shouldn’t you have a device with a built-in hardware back key like MS Smartphones) once and, then, go down to highlight "Insert Symbol":

Then, just press Action on it to get into the traditional URL input field, with the traditional menus.

3, textual input may be problematic on keyboards with combined numeric and alphabetical keys; for example, on the HTC Vox. In there, the numeric keys will always be considered as keypad numeric buttons; that is, they’ll input a for 1, d for button 2 etc. However, as they’re treated EXACTLY the same way as keypad buttons, you can still input any character or (with long-pressing) number with them. You’ll need to know the latter for numeric input with devices that have a separate numeric row (like the HTC Universal).

4, the Input Address field being new also results in the old system-level browser invocation script not working any more. To fix this,

• either switch off the new direct input by just unticking the, by default, enabled "Direct address input" checkbox in Tools / Settings:
  
  
  
  
  
  
• or, alternatively, go for a modification of the current script version available HERE. (Incidentally, note that, now, there’s a full C++ implementation of the invocation script HERE. It’s still not compatible with 4.1 unless you untick "Direct address input" as explained above.)
  

1.2.2 Signing

First in Opera Mini’s lifetime, it comes signed. What does this mean? When deployed under a capable, compatible JVM (for example, Jbed 3.1), it’ll, upon trying to access the Net / the local file system for saving pages / downloading / uploading files, it’ll prompt you for permission:

(reading the file system)

(writing the file system)

In there, you’ll notice a (compared to the unsigned case) new "always, don’t ask again" menu item (I’ve highlighted it in the following screenshot):

Make sure you do select this before pressing OK. This will make sure you won’t ever need to answer this question any more.

Upon trying to saving pages, it even prompts you to switch to the signed version, should you still have a non-signed one:

The link indeed takes you to a tutorial:

(as can clearly be seen, there is not a single word on Windows Mobile. Note that the tutorial is also directly available HERE)

1.2.3 Page Saving

The new page saving feature allows for saving the current page, along with all its resources (images), to a file. The file is in the native (condensed HTML in textual mode + JPEG images) format of Opera Mini currently not readable by other applications. Should you still need some of the contents for copy/paste operations, you can still directly copy from the file with a text viewer. This also means this also allows for some kind of rudimentary copy/paste functionality if you use an external file viewer like that of Resco File Explorer. Then, based on the (latest) timestamp of the saved page (the saved pages have cryptic filenames; however, you can easily recognize them based both of their timestamp in the file system and their header, which contains the title of the page), you view it and look for the info you wanted to copy to clipboard (and, from there, to, say, Notes or Word Mobile). As you can see, it’s in no way so easy than, say, copying and straightforward than copying the full / the visible textual contents of the page into a text input field, where a user could already highlight anything and copy to the clipboard (unless she uses TAO Intent), though. Hope the Opera coders also implement this, otherwise, very simple-to-code feature.

Note that the page saving target dialog is only displayed once (upon the first page saving attempt) and is pretty much far away from being pretty and/or intuitional (and, of course, it has missing functionality present in, say, the standard OS file save dialog like creating subdirectories) but it still does the job. Just select the directory you’d like to save your pages to. Again, remember this can’t be changed later so select a directory with sufficiently large free storage.

First, you’ll need to select the storage type you’d like to save your pages to. In the following screenshot, I’ve selected Storage Card:

After pressing Action, you’ll be shown the directories in there. You can select any of them (and, then, iteratively, any of its subdirectories etc.). Just press Select (left softkey) on the directory you’d like to save your stuff in. For example, in the following screenshot, I’ve stayed on Storage Card when pressing the key; this means it’ll store the pages in the root of the card:

(note that, as the storage card roots can only have up to 128 files, this isn’t the best thing to do unless you’re absolutely sure you only want to save some pages.)

Finally, you’ll be prompted a "Page saved." message:

Get rid of it with the Action button.

After this, all the saved pages will be listed in Tools / Saved Pages (and the latest three on the startpage):

A VGA screenshot with more than one saved page:

1.2.4 Finding text in pages

Tools / Find in page implements something I’ve been asking for years: in-page text search. It not only iterates over all the occurrences of the searched-for word (see the "Next" left softkey), but also conveniently highlights all the occurrences. In the following screenshot, you can see the results of searching for the word "Opera" in the Opera Mini forums:

1.2.5 In-app file up/download

A lot of users have been asking the Opera folks for allowing for in-browser download and, even more importantly, upload.

1.2.5.1 Download

In-browser downloading, for Windows Mobile users, isn’t that important. It’s probably mostly MS Smartphone users that will find this useful because, as has also been explained in my MS Smartphone Web Browsing Bible (see section 1.1.1 Fixing the binary file download problem), the built-in Internet Explorer Mobile only downloads certain types of files. For Symbian users with, say, a Nokia N95 with a pre-20 firmware version, it’s more so because Symbian often killed Opera Mini when loading up Nokia Web for handling the download. This isn’t an issue with the new firmware version any more, of course – neither is with N95 8GB, N95-3, N82 or the soon-to-come, new, DVB-H enabled N-series models.)

Note that, while file system access is supported in the latest and most recommended Jbed 3.1, this isn’t necessarily the case with other MIDlet Managers. Therefore, you’re strongly recommended to upgrade to Jbed 3.1.

The new in-Opera download looks like this:

If you select Save As, you’ll be presented the usual file selector; here, I instruct it to save the contents on the storage card:

Then, the download will start:

If, instead of Save As, you select Open:

you’ll be taken to IE:

which downloads the file:

Unfortunately, if you go for in-process download, you can’t do anything else during downloading – as is the case with regular page loading. That is, you end up staring at the download screen. If you absolutely hate this and/or the download takes too much time (for example, during fetching a looooooong MP3), go for downloading within Internet Explorer Mobile and switching back to Opera Mini for browsing. You can safely do this: IEM will just download the file in the background without problems. (Unless, of course, you haven’t registered the file type with the system. Then, you’ll need to stick strictly with the built-in downloader of OM4.1.)

1.2.5.2 Upload

With Jukka "Yucca" Korpela’s excellent article & tester suite File input (or "upload") in HTML forms:

Then, the usual Opera file handler will be shown (not that of the OS). Let’s upload some text file:

and the results are as expected:

(note that it the (later?) 4.0 series it is rendered as can be seen in HERE but, of course, the "Choose" file chooser couldn’t be activated)

In this regard, Opera Mini (along with the commercial (!) Opera Mobile and [the, currently, severely crippled Technical Preview] NetFront) is the only browser to support file upload on the MS Smartphone platform. Let me point out that the built-in Internet Explorer Mobile (still) doesn’t support upload.

2. What’s still missing / problematic?

Now, in addition to direct copy/paste of textual contents, I only miss navigating (switching back) to any already-downloaded page while loading a new one. You can only navigate on the current page while fetching a new page but can’t use, say, #5 to quickly bring up the list of currently open pages and quickly switch to another page. There isn’t a "download page in background" feature either, which would be able for allowing this. This can be a nuisance, particularly on inherently sloooooooooow platforms like the current crop of BlackBerries.

Also, on Pocket PC devices with a built-in keyboard could benefit from some similar keyboard layout than on BlackBerries. On the latter, you can use the (wide and easy-to-reach) Space button to scroll a page down. I wish you could do the same on Windows Mobile devices. (In there, you still must use the "8" button, which is pretty much out of reach in two-hand, "bedtime" operation.)

The problem of "flashing", non-displayed pictures, particularly with pages heavily loaded with them, is still present.

Finally, the lack of italic support is (still) a big pain in the back. I don’t understand why the Opera folks don’t implement this (must be related to the additional storage the custom, smallest character set would require with added italic support, I don’t know – if that’s the problem, at least non-smallest characters should have this support) – after all, ALL major KVM’s do support rendering text in italics. (See my related tests in my MIDlet Bible.)

3. BlackBerry

The BlackBerry version doesn’t support signed versions; that is, as has already been pointed out, you MUST go with the unsigned one. I haven’t encountered any problems with it; page saving / loading, the new address autocomplete etc. all worked just great. I haven’t encountered the common bug with all OM 4.0 versions: that is, the BlackBerry (at least my T-Mo branded 8800) completely locking up upon loading pages. However, this doesn’t mean these bugs have been fixed: I "only" played with the new version on my BB for two or three hours and the aforementioned bug only turns up, say, once a day or two days, assuming actively using OM for at least 2-3 hours a day.

4. Symbian

I’ve also (quickly) tested the new (unsigned) version on my Nokia N95 v20. I haven’t really run into problems so far; neither have my fellow N95 users in the Opera Mini forum. I’ll later report on whether Opera Mini 4.1 still exhibits the well-known, but, fortunately, pretty rare problem of completely locking up the handset, which, as with the BlackBerry, can only be fixed by removing and reinserting the battery.

[Guest Menneisyys]

UPDATE (later the same day):

1. MoDaCo frontpage

2. note that the above-recommended Jbed 3.1 is NOT compatible with WM5 (or with even older operating system versions), only WM6. If you're still on WM5, use the old, "Cloudyfa" 2.1 version instead; or look around at XDA-Devs, where, according to THIS post, the 20080222 version of 3.1 is WM5-compatible.

[Guest Menneisyys]

UPDATE (04/05/2008):

1. I’ve tested the above (in the previous update) mentioned Jbed Java 3.1 20080222 (available HERE; mirrored HERE for your convenience). It runs flawlessly under WM5 (not only WM6). It supports 3D (tested with Need for speed carbon and Night Fever; neither of them run under the non-3D-capable Cloudyfa 2.1), (as usual, excellent) sound. It can’t be directly installed onto a storage card, however. (As with some older versions, it’s possible it can be hacked there, though, with some manual file copying and registry / start menu link rewriting – I haven’t tested this.)

I’ve also thoroughly tested JBed_20071119.3.1_3dMod_HeapSizeFix_v2_wm6(lovetz1) linked from THIS MoDaCo thread. As a plus, it can be directly installed on a storage card, as opposed to the version above. It, however, doesn’t support sound at all. Otherwise, it seems it’s pretty much the same as the version above – except for WM5-compliance: I haven’t tested the WM5-compliant subversion. I’d stick with the 20080222 (the first) version unless you really need every single byte in your built-in storage.

Note that neither version was able to run the s60v3 (Nokia) version of Command & Conquer 3: Tiberium Wars, the latest-and-greatest real-time strategy from EA Mobile – upon loading the mission (and displaying the progress bar), it just locks up. (Needless to say, it’s working flawlessly on the Nokia N95 v20). It seems no Jbed version is compatible with this excellent game.

2. XDA-Devs user JZ SmartMort has released a very promising title making Opera Mini the system-level browser much simpler and offering a LOT of additional functionality. See his thread HERE. Note that he also posted a somewhat shorter post HERE (in THIS thread, should you also want to read the possible, future discussion of his app).

[Guest fozzie]

Great post. Thanks.

Just for info, I'm running the TAO JVM (v11.1.7.1036) that's been updated to allow session security (instead of just oneshot), as described >>here<<. I found that I couldn't install any of the signed versions of this latest Opera Mini beta and so installed the unsigned one. With my setup, saving and retrieving pages works fine, with just a single prompt about reading/writing to the device for the session.

Edited April 5, 2008 by fozzie

[Guest UndeadDevil]

Opera Mobile 9.5 blows the holy c**p out of Opera Mini 4.1. And yes OperamMobile 9.5 BETA is out and runs great. Its weird suddenly having Flash Adverts, being able to use YouTube in Browser, and generally having such amazingly fast performance.

[Guest fozzie]

I'm really liking the improvements in 4.1. A big thumbs up.

Having got things working, I thought I'd give a different JVM a try. I installed Jbed Java 3.1 20080222 as mentioned above and what can I say; there's a huge performance increase over the TAO JVM. Opera Mini really flies now :D

I also installed the 'WM6 OperaMiniAsDefaultBrowser - WithSelectionDialog.cab', available >>here<<.

[Guest samsul]

Opera Mobile 9.5 blows the holy c**p out of Opera Mini 4.1. And yes OperamMobile 9.5 BETA is out and runs great. Its weird suddenly having Flash Adverts, being able to use YouTube in Browser, and generally having such amazingly fast performance.

Hi,

Any chance of dowload link or e-mail me the files, [email protected]

Thanks

[Guest dario69]

UPDATE (04/05/2008):

Note that neither version was able to run the s60v3 (Nokia) version of Command & Conquer 3: Tiberium Wars, the latest-and-greatest real-time strategy from EA Mobile – upon loading the mission (and displaying the progress bar), it just locks up. (Needless to say, it’s working flawlessly on the Nokia N95 v20). It seems no Jbed version is compatible with this excellent game.

It appears to lock up but give it a minute. It does go past the screen. At least it does for me.

[Guest Menneisyys]

Great post. Thanks.

Just for info, I'm running the TAO JVM (v11.1.7.1036) that's been updated to allow session security (instead of just oneshot), as described >>here. I found that I couldn't install any of the signed versions of this latest Opera Mini beta and so installed the unsigned one. With my setup, saving and retrieving pages works fine, with just a single prompt about reading/writing to the device for the session.

Just a quick question: why are you sticking with TAO? Because of the arbitrary font size setting capabilities (which can be pretty important on a VGA device - but not on a QVGA one like yours) or the unlimited co- / background execution capabilities? (IMHO, Jbed is far better in every other respect.)

EDIT: now I see you've switched to Jbed in the meantime and found it much better :D

[Guest Menneisyys]

It appears to lock up but give it a minute. It does go past the screen. At least it does for me.

Are you also using Jbed? If yes, which version?

The MIDlet JAR file is Command_Conquer_3_Tiberium_Wars_240x320.jar , dated 02/28/2008 11:39 AM and of size 600,964 (from HoFo) - is your version the same?

[Guest Menneisyys]

Opera Mobile 9.5 blows the holy c**p out of Opera Mini 4.1. And yes OperamMobile 9.5 BETA is out and runs great. Its weird suddenly having Flash Adverts, being able to use YouTube in Browser, and generally having such amazingly fast performance.

Yup, OM 9.5 does have some advantages over OM4.1. The latter, however, has some definite advantages over OM9.5 too:

- much lower data usage (important if you aren't on an unlimited data plan)

- much faster download over GPRS [ / EDGE] - or plain slow connections

- pretty much bugfree, unlike the (unofficial) beta of OMobile 9.5 :D

- much lower memory footprint; is able to keep 30 pages (!!!) in the memory at the same time, and you can very eaisly switch between them

- free

[Guest Menneisyys]

UPDATE (04/06/2008): I have some very good news for you all.

1. Several of my readers have asked (see for example THIS) whether it’s possible to change the page save directory in Opera Mini 4.1 after you’ve set it first. Contrary to the popular belief (you must reinstall it from scratch), it’s actually very easy to do this:

a. if you have originally selected a removable storage card as the target media, you only need to remove it before trying to save any page on it. Then, you’ll be prompted an error message and, on the next page saving attempt, you’ll be offered the chance of setting the new save directory. That is, if you’ve originally given Opera Mini a storage card, you can change the save path without any need for hexediting files.

b. if you have provided it with a movable / deletable directory in the built-in storage (or, for that matter, on the storage card), just move (cut / paste) the entire directory somewhere else on your device – or on your storage card. That is, if you’ve given \My Documents to it, just cut it with the built-in File Explorer and paste it to in any other subdirectory. (Of course, you’ll need to paste the directory back once you’re ready with the – failed – page saving attempt if it’s a directory used by other apps too – like \My Documents.)

3, if, for some reason, neither of the above-listed ways works, you’ll need to do some hexediting. To do this, search for the in the name of the directory in the \Windows\appdb\s?__d?.db files with, say, Total Commander (Alt-F7) on the desktop Windows and just change this occurrence to another directory with a hexeditor. An example showing changing \My Documents to \Storage Card with a hexeditor:

Again, it’ll be FAR easier to temporarily remove / move the directory than hexediting – only do the latter if you simply can’t (temporarily) delete the directory because you’ve given it, say, \Windows or some other, undeletable directory.

2. the native C++ version of the invocation script has been updated to be compliant with 4.1. In addition, badbob001 has updated his MortScript to be compatible with 4.1 and he is also doing automatic (!!!) descriptor parsing & discovery to automatically find the current position of the OM deployment (just like the JZ SmartMort's brand new script I've reported on above), which, so far, needed to be done (once) by hand. See his updated script HERE. Both advancements are discussed HERE, starting with page 10 (post #91).

[Guest JZ SmartMort]

Announcing JZ SmartMort v1.2, just released. This is the one to stop the DEFBROWSER problem, it also uses badbob001's pixel seeking logic. I tested on a bunch of platforms like WM6 WM5 & PPC 2003. You will love this one :D release notes below.

Get it here: http://forum.xda-developers.com/showthread.php?t=382043 or on SourceForge

v1.2 *** 2008-04-13

- Added badbob001's superior logic for pixel seeking instead of arbitrary pauses.

- Wrote a .Net executable to deal with the DEFBROWSER & MSPIE issues with running MortScript and passing command line arguments - yeah baby! WM5 & PPC 2003 will need .Net Compact FWK 2.x and above, WM6 works out of the box.

- Added a JBed troubleshooter to the Install script. It checks registry and Start Menu shortcuts. It does not fix anything automatically but does report findings back to you. I saw problems when people try different CABs of JBed versions.

- Added device Unlock/Lock capability to Install script. JBed install errors on WM6 emulators until registry is manipulated. If fails, search web for SDA Full Application Unlock.

- Added ability to set a default browser through the Install script, no manual script editing required.

- Fixed UTF file parsing and stripping quotes from jbed command.

- Dropped TAO Intent support - too slow and seems to fail to install on WM6 emulators.

- Dropped Opera Mini 2.0x support - hard to test pixels because it's white and full screen.

[Guest Menneisyys]

UPDATE (04/19/2008):

1. Unfortunately, it seems none of the Jbed 3.1 versions are able to run Opera Mini 4.1 beta on touchscreen-less MS Smartphones (but NOT on Pocket PC's!!!) if you switch to other apps (for example, the home screen) and, then, back, you will no longer be able to control Opera Mini. I've tested this on my WM5 s310 / Oxygen (major problems) and, with HTC's recently-released ROM upgrade, upgraded WM6 s710 / Vox (not that frequent problems but still annoying). At XDA-Devs, other people have also reported the same problem with their Smartphones.

If you do encounter problems like this and can't refrain from task switching, you'll want to downgrade to the Cloudyfa 2.1 version available HERE. Note that it can safely co-exist with 3.1 if you've installed the latter in another directory (for example, on a storage card or a flash disk) - then, it's only the file associations that will be needed to, say, quickly switched if you don't want to manually deploy a MIDlet from inside the GUI of the specific MIDlet manager. That is, you don't need to delete Jbed 3.1 if you plan to keep it for example for M3G gaming.

Note that touchscreen-equipped Pocket PC's do NOT suffer from this problem!

2. Ebenezer has released a fixed version of his Jbed 3.1 MIDlet manager HERE. Now, it does create a link file in Start Menu / Programs on both Pocket PC's and MS Smartphones. It also installs to any target media (not only "Storage Card"s) without problems. Note one caveat, though: the link file (the one the installer puts in the Start menu) has \Storage Card wired in, which doesn't work with any storage card (or flash disk) named other than "Storage Card". Hope this is fixed some time; in the meantime, just manually edit the link file to have the correct path.

[Guest JZ SmartMort]

Announcing JZ SmartMort v1.3

This version has a lot of enhancements, please read the release notes below.

Get it here: http://forum.xda-developers.com/showthread.php?t=382043 or on SourceForge

v1.3 *** 2008-05-25

- Created a CAB file for distribution. If upgrading, please remove or rename the entire JZ folder. To install the CAB your phone will need to be uncertified app-unlocked. You can use this standalone utility: http://www.gpcarreon.com/?p=151

- Mort has allowed me to distribute his FREE MortScript, when you install JZ SmartMort it will place Mort's CAB files in the "MortScript Installs" folder, found underneath your JZ install location. This makes it easier to install all components necessary to run my software w/o having to download more from the web.

- CAB file will create a Start Menu shortcut for JZ Installer.

- Pulled out the .Net executable file from the pack, found a MortScript workaround instead.

- Storing everything in the registry. Optimized scripts for light memory usage and speed.

- Added PPC support to map the JZ Action script to the Application 2 hardware button.

- Added NetFront 3.5 support and verified all Opera Mini versions above 3.1

- Default browser has a timeout now which is user defined, default is 5 seconds.

- Opera Mini enhancements: 8 paste methods, adjust trim units, use different methods to pop the Opera Mini URL input screen and enable/disable "Auto-Complete Address Input"

- Ability to create the Opera Mini shortcut on your Start Menu.

- You can use the action/button mapped script to choose a JBed/Java app from a list. Added a JBed security prompt patcher along with the Application Unlocker which is also a part of the pack.

- HELPERS folder underneath the JZ installation area has scripts to reset device, kill voice notes, list JBed apps to run, Kill IE & Kill MortScript.exe.

- Ability to reset JZ SmartMort settings.

- Ability to select with cursor & copy to the clipboard (will ask how many seconds to allow cursor selection)