Database Info

REVIEW: Best, Brand New Java-based Browser Opera Mini 4 beta 2!

I’ve always loved Opera’s Web browsers. On the desktop with a screen having a higher-than-average resolution (say, at least SXGA+), their free desktop Opera browser is by far the best and most useful browser because it’s the only browser with (nearly) flawless dynamic zoom capabilities. On non-dumbphone (that is, in our case, native Windows Mobile) platforms, their Opera Mobile browser is, despite in some lacking functionality and bugs, currently (as of version 8.65 and end of August, 2007) is the best browser. Finally, as far as Java-capable “dumb” phones are concerned, their Java-based and, what is more, FREE Opera Mini is simply the BEST browser out there.
The Opera folks released the first beta of their brand new, 4 series of Opera Mini this June. I’ve reviewed it in the MS Smartphone Web Browsing Bible. Then, it had some annoying bugs and midlet manager (environments to run Java midlets, including Opera Mini) vendor-specific problems (particularly the crashing / quitting problem on (fortunately, only) one Midlet manager and the “too large fonts” problems on all QVGA handhelds).
Fortunately, these problems / bugs seem to have all been fixed. Read on to find out what has changed in the last 2.5 months!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(a VGA screenshot)
(Note that the screenshots were done with the Esmertec Jbed Midlet manager on my HTC Vox / s710 (QVGA Smartphone) and the Tao Intent Midlet manager on the HTC Universal. I’ve also published some other screenshots with some other configurations showing for example Esmertec Jbed running on the latter VGA HTC Universal Pocket PC. Also see the “The Midlet Managers used in the article – how come some of the screenshots are full screen, you may ask” section below for more info on all these questions.)
First, let’s compare the new version to the old. Please read the MS Smartphone Web Browsing Bible (and the “original” Pocket PC Web Browsing Bible linked from it) to get a FULL picture of what Opera Mini is, how it compares to other Windows Mobile browsers etc.
The good
In addition to fixing the font size bug (see below), a new font size, “Extra large”, has been added. With that, the screenshots below (which have been made with the default “Medium” size) are as follows:
(VGA screenshot on the HTC Universal running the latest TAO Intent JVM)
For comparison, with “Small”, the same is as follows:
(VGA screenshot; plain Esmertec JVM QVGA Smartphone screenshot)
There is a brand new submenu, assigned to phonepad button “1”, which offers, in addition to quickly changing between fit to width and full layout modes, reloading and page information, also offers a Link context menu, which allows for opening a given link (you can force it to do this without images) and getting information (that is, the link address; unfortunately, you can’t, say, copy it to the clipboard (screenshot)):
Unfortunately, there’s still no way of parallel loading of more than one link – or, to, say, return to the current page so that you can go on reading it if you initiate the loading of a page from your favorites / bookmarks. These would be more than welcome because, especially with large(r) pages and/or slower and/or not frequently accessed servers, loading times can be pretty high – even in the range of 30-60 seconds.

There are some new hotkeys on handhelds with a dialpad. In addition to the well-known 2/4/6/8 buttons for page scrolling; in full page view, you can use button 5 for quickly zooming in and out (which does the same as the combination of Action and the right softkey, but more conveniently). Furthermore, while the #-prefixed buttons are the same, there is another welcome new hotkey: screen rotation with *# :
This, currently, only rotates between left-handed and portrait view. (In this respect, version 2.04 of the Russian Opera Mini hack (which I don’t link in by purpose – sorry, the app has been declared illegal by the Opera folks) is (still) better: it offers rotating to all the four directions. Not that it’d be that important: on a device with a built-in, slide-out keyboard, it’ll always switch to the right direction when you open/close the keyboard, regardless whether the keyboard opens to the right or the left.)
The biggest bugs have been fixed:
the inability to keep more than 1-2 pages in memory in non-one column mode. An example screenshot of the History list showing this follows:
As can clearly be seen, ALL huge pages were still accessible, requiring no reloading. This is indeed HUGE advantage over beta1!
The font problem has been fixed. The previous beta had too big fonts (even in the “Small” setting) with too much space between the individual rows. The new version is much better in this respect. An example screenshot showing this:
(a screenshot of the same in “Fit to screen” mode. The same on a VGA Pocket PC with Esmertec Jbed using the default Medium font HERE, extra large fonts HERE and Small fonts HERE.)
The bad
There doesn’t seem to be other, new functionality: the menus are the same (screenshot); so is the Settings dialog. In this regard, the above-mentioned Russian hack is still better in some respects (but Opera Mini is indeed catching up and, in many respects, is already far better than the hacked version).
Unfortunately, text using italic is still NOT rendered as italic. This has always been one of the BIGGEST problems with this browser. As has also been pointed out in my related posts (see for example THIS), ALL Windows Mobile-based Midlet managers support italic text – why don’t the Opera folks implement it, then?
Getting, installing
Just point any of your WAP-capable or WAP-enabled (Opera Mobile and IEM are already like this; NetFront must be manually configured to accept WAP pages) Windows Mobile Web browser to http://mini.opera.com/beta/ and click the "Download high memory version" link at the bottom (an IEM screenshot). The installation will automatically start; just make sure you answer Yes / Continue to all questions. After that, just launch the newly-deployed midlet and follow the instructions on the screen.
Compliance
With the current (20070622.2.1) version of Esmertec Jbed (and, therefore, the standard Esmertec JVM coming with most current WM6 devices) I’ve only once encountered a crash: upon having some 10-15 (large) pages open in full page view mode, pressing Save after setting the font size to “Extra large” resulted in Jbed’s getting frozen. This happened to me under TAO Intent too (with one or two pages open); then, just canceling the save operation worked. Then, after re-entering Settings and saving the new configuration again, it already worked flawlessly.
That is, if you encounter hangups after you change the character size, make sure you try to cancel (right softkey) the operation to see whether it helps.
With Tao Intent 11.1.7.1034 (available for download HERE), 11.1.7.1029 (coming with several XDA-Dev cooked ROM’s; I’ve tested it on a Wizard cooked ROM) and 11.1.7.1023 (available for download HERE), I haven’t encountered any crashes so far. That is, (knocking on wood) it seems the Tao Intent crashes have also been eliminated.
The Midlet Managers used in the article – how come some of the screenshots are full screen, you may ask
The QVGA Smartphone screenshots have all been made with the Esmertec Jbed midlet manager; hence the full screen mode on all them.
Don’t mistake the Esmertec Jbed midlet manager for the “plain” Esmertec midlet manager (as of version 20070115.1.1 – the one that comes with the original ROM of the HTC Vox / s710). The latter doesn’t offer full screen capabilities as can be seen in the following screenshot:
(the same screenshot – already shown above – taken with JBed – note that I haven’t used the built-in “full screen” mode of Opera Mini accessible via ** to hide the red bars at the top and bottom). Another reason to install Jbed on top of the Esmertec Midlet manager – in addition to some of its other advantages; for example, much better sound emulation (which can be very important in games). I’ll elaborate on all these questions in my forthcoming Midlet Manager Bible.
The VGA Pocket PC screenshots, on the other hand, have been made using the, in this regard, FAR less recommended TAO Intent midlet manager – hence the unused task- and command bars at the top and the bottom of the screen.
Verdict
This browser is VERY good, particularly when you use it with a decent Midlet manager allowing for real full screen mode. Hope the authors introduce at least support for italic and the ability to, at least, going back to the original page from Favorites while downloading a new page in the background so that you can go on reading the page.
Much as there is still some room for improvement, the bugs of the old, beta1 version seem to be ALL eliminated and even if you didn’t suffer from them (because you used the IBM J9 or the Esmertec JVM and not the Tao Intent one), you’ll certainly welcome the character size and the history list / cache size improvements. If, on the other hand, you’re a Tao Intent user, you will LOVE the stability of the new Opera Mini. (Still, as has already been stated, you’re STRONGLY supposed to upgrade to Jbed – you can just install Jbed on top of your Intent Midlet manager, it’ll work just great.)
All in all, no matter whether you have a Pocket PC or a touch screen-less Smartphone, go get the new Opera Mini – you will LOVE it, I’m absolutely sure!

UPDATE (09/02/2007): Bad news: the linked Jbed version no longer works. See THIS for more info.

New Java-based browser Teashark: really a competitor to Opera Mini 4? Not (yet?)

Thanks to XDA-Developers forum member TalynOne, I was directed to the new Java MIDlet-based browser Teashark. It is also mentioned in THIS blog post too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Availability
You can download the JAR file HERE. Just deploy it under either the Jeodek or Jbed MIDlet Manager. (Do NOT try to deploy it under TAO Intent because the browser is entirely incompatible with all TAO Intent versions!)
Please note that, if the words Jeodek, Jbed, TAO Intent and MIDlet Manager sound Chinese to you, don’t despair: just wait for my long-promised MIDlet Manager Bible, where I explain everything you’ll ever need to know about these programs. In the meantime, feel free to follow the links in the above-linked MIDlet Manager Bible announcement for forum posts and other remarks.
Compatibility, problems, bugs
As I just love Opera Mini 4 (OM4 for short; see review HERE), which I use almost exclusively for Web browsing, I’ve tested the new browser at once to see whether it’s, as mentioned in the above-linked blog post, indeed a decent alternative to Opera Mobile.
I’ve tested the browser with the three most common MIDlet managers out there: TAO Intent (both the 10 and the 11 series), Esmertec Jeodek and Esmertec Jbed. (Haven’t tested it with IBM J9.)
TAO Intent (tested on the HTC Wizard Pocket PC (TAO version 11.1.7.1029 default), the HTC Universal Pocket PC (11.1.7.1036 Risidoro) and the HTC s310 / Oxygen Smartphone (10.1.7.680 default)): absolutely useless. The menus aren’t accessible (neither the hardware nor the software, on-screen keys work) and there’s no way of even navigating on the page – neither the D-pad nor the on-screen / hardware 2/8 or up/down buttons work. Finally, as with the other MIDlet managers, the touch screen can’t be used on Pocket PC’s.
Esmertec Jbed (tested on the HTC Universal): a bit more usable. While it still doesn’t support any kind of touch screen operation, at least it allows for accessing the menu (via a hardware key only). It has the following pros / cons (under Jbed):
Pros
Upon entering an already-entered URL, it has an automatic address completion feature, unlike OM4b2
It displays both italic and bold characters, unlike OM4b2 (OM is totally unable to render italic text and, depending on the actual font size used, it may refuse to render bold too).
The in-page text search works just great (examples: 1 2 3) – I wish Opera Mini had the same feature!
Cons
The rendering of the text is VERY bad: wherever there is a style / color change, the text overlaps as can clearly be seen in THIS screenshot
Scrolling (in full page view mode) is FAR better thought-out in Opera Mini 4 - it takes far less D-pad presses to navigate to a link without annoying screen scrolls.
There is only one character size, unlike with OM4 – no font size setting capabilities as can be seen in this screenshot taken under Esmertec Jeodek on the s710. This is REALLY bad: Java MIDlets have access to, in general, three different font sizes by default.
The default mode is a no-one-column (that is, showing the original layout) mode. On VGA devices, this, in most cases (there are exceptions; for example, the page HERE is rendered almost unreadable because of the need for horizontal scrolling – for comparison, HERE is the same under Opera Mobile 4 beta 2 without using the one-column mode and with Extra large fonts (!) – see the difference? OM4 is WAY better in this respect too), isn’t a problem. In order to enable the default one-column mode, there’s a “page start with mini view” checkbox in Preferences, I couldn’t check it in under Esmertec Jeodek v20070115.1.1 on my s710 (while it worked under Esmertec Jbed v20070802.2.1).
Again, it doesn’t make use of the touch screen in ANY way – not even at selecting from the menus
History doesn’t work at all, unlike with OM4, where you can quickly switch between the visited (and still in-memory!) pages
Generally, it loads pages definitely slower than OM4, while it uses more bandwidth
It doesn’t let for scrolling through the links of the main (home) page: it only scrolls down to the third or fourth (depending on the actual screen orientation) and, then, start from the beginning. On other pages (including the “Visited” page list), there’re no similar problems. Note that this seems to be only a problem with Jbed; with the (older) Esmertec Jeodek (the one, v20070115.1.1, coming with the HTC s710 / Vox Smartphone), I could scroll through all the homepage items
It uses its own text entering method when entering the URL to navigate to or the search expression for text search. (Fortunately, this is NOT the case with in-page text fields/ areas like the Google textfield at the top, where the default one is used. That is, if you absolutely must use punctuations in the URL you need to enter, fire up Google so that you have access to the default, MIDlet manager-provided text input area; there, you’ll already be able to use all the punctuation marks – including the ones on hardware keyboards OR phone dialpads; for example, the one on the HTC s710 / Vox). This means the following:
if you have a built-in hardware keyboard to enter text you will only be able to enter alphanumeric characters but nothing else – not punctuation marks only accessible via a Symbol key (fortunately, the dot, “.”, isn’t one of them – at least on the Universal) or “/”! Think of it: you can’t even directly enter URL’s like www.pocketpcmag.com/blogs because of the inability to enter /! This GREATLY reduces the usability of the app, particularly if used together with Jbed (which, being run always in full-screen and, consequently, hiding the SIP icon) doesn’t allow for bringing up the SIP and entering special characters on it. Note that I don’t know if entering “special” characters (like /) works on a SIP as Teashark is completely useless with the TAO Intent Manager (one of the MIDlet managers to support bringing up the SIP any time).
On Smartphones, the dialpad works in the standard mode (without xB9; the # and * buttons, however, just can’t be used to enter anything else. That is, even if you keep # depressed, you won’t be presented a list of the usable punctuation marks (including for example /), only the # will be repeatedly included.
Still as far as Smartphones are concerned, it’s absolutely unable to make use of the slide-out keyboard of the HTC s710 / Vox.
Verdict
While this browser certainly has some advantages over Opera Mini 4 beta 2 (the in-page text search and the ability to render italic / bold being the most important), in general, this browser is, currently, in no way recommended for Windows Mobile users because of the really bad bugs. That is, just stay away from it.
I let you know as soon as a usable version is released.

UPDATE (09/14/2007 14:15 CET): I've also tested the browser under IBM J9 6.1.1 on a Dell Axim x51v. While, unlike with TAO Intent, you can move around with the D-pad (and click links), the softkeys don't work (not even with hardware buttons), which means you don't have access to the menus at all. That is, it's useless under IBM J9 too.

Hmm... will try. Is it for PPC Phone or SP?
Minimo v0.2, I find that it is very slow.

CWKJ said:
Hmm... will try. Is it for PPC Phone or SP?
Click to expand...
Click to collapse
Both as it's a MIDlet.
CWKJ said:
Minimo v0.2, I find that it is very slow.
Click to expand...
Click to collapse
Yeah, it's VERY slow. Use for example OM4 b2 instead, if you absolutely must use a free browser.

Cross-posting this from a post I made on the Opera Mini forums, since this community is more likely to understand my issues with this browser...
There is something fishy with Teashark.
THINK ABOUT IT.
1) They appeared out of no where with a Java app.
2) There is NO linkable parent company on their site. Can't look up domain registration, can't find out ANY other information AT ALL about them and who they are.
3) They have absolutely NO way to relate back to the community. They have a "blog" run on a wordpress backend. That right there should throw up some red flags. Why would a "company" or WHATEVER they are that is developing a Java browser (with no ads in it mind you), use Wordpress as a blog backend? That just makes no sense to me
4) How exactly does this company make their money? Something tells me you don't want to know if you've been using their browser. They have no advertisements on their site or in the browser. They have to be making money somewhere, because they wouldn't have these proxy servers serving up loads of bandwidth for free. Where is their money coming from? A parent company? Who?
5) Their whole website is fishy. Aside from complete lack of information, why do all links on their site link you to port 8080 on their server? Why aren't they running over standard port 80? Something is odd about that alone.
6) The vendor tag in the app is labeled as "Vendor". Ummmm... what?
Their website traces back to: "IP 69.72.142.98 is from United States(US) in region North America"
That is about the only traceable information I can figure out.
It creeps me out that this mysterious company pops up out of no where and throws this "browser" app out there, with absolutely no effort to disseminate who they are. What is even creepier is that people have downloaded this app and are using it with ZERO knowledge of who this company is or who is behind them!

A review of the latest version has just been published: http://forum.xda-developers.com/showthread.php?p=3571856#post3571856

Web Browsing News as of 10/18/2007: new Opera Mobile, Picsel, Spb Pocket Plus

A lot has happened in the last month on the Web browser scene. Let’s go over the news!
1. Opera Mobile 8.65 Final released!
Since this March, there have been two beta versions of Opera Mobile, without doubt the BEST, fastest and most standards compliant Web browser for the Windows Mobile platform. Now, almost half a year after the release of the first Beta, the final version has, finally, been released, of which I was also a (closed) betatester, working closely together with the developers and decision makers of Opera.
Compared to the 8.65 betas, which I thoroughly elaborated on in the Web Browsing Bible (and, therefore, in here, I don’t elaborate on these new features – make sure you read my roundup above), there are only few changes. There, on the other hand, have been several bugfixes; for example, the really annoying DEFBROWSER bug I’ve, independent of some other people doing the same, discovered and reported HERE).
Design decisions
Single column layout removed. This is a design decision I don’t really agree with. Particularly if you have a VGA device, you MAY find the lack of the single column mode annoying, particularly with sites / pages that, otherwise, would work much better with a well-working One Column mode. An example: a Wikipedia article in PIE’s One Column mode on a VGA device in Landscape mode (Largest charsize, High Resolution enabled) (the same with Fit to screen – as can be seen, it’s pretty much useless) and the same in Opera Mobile (Minimum font size: 8; Zoom: 100%). As can clearly be seen, One Column modes will ALWAYS be able to present more information. You can, of course, use zoom facilities so that the horizontal screen estate is fully filled in but, then, the character size will also grow and, what is worse, the images will also become pixelizated. (Also see THIS thread for more info / discussion.)
Desktop view, which has been made the default (!) viewing mode, has been made much friendlier. Now, it’s using a bit smaller characters than before. Should you still find them too big, switch to the default (fit to screen) viewing mode because setting Menu / Tools / Settings / Minimum font size to even 8 doesn’t seem to do the trick. Thanks to the, most of the time, excellently working new wrapping functionality, makes it possible to live without having to scroll around. This is shown in the following (VGA Landscape) screenshot with the View menu shown:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, the cache is stored on the same drive as the executable program itself. While this is what many people have been asked for (particularly with devices only having 64 Mbytes of Flash ROM, meaning only 10-11 Mbytes of it available to the users – for example, the HTC Oxygen / s310 Smartphone is one of them –, you will definitely like this.
Note that, however, this approach might have negative consequences. As has been explained in my Web Browsing Bible, storing the browser cache on a slow-to-create-files-on storage card (most non-high-end cards are like this) may result in the slowdown of the page loading. If this is a concern to you (because you visit pages that contain a LOT of different images, which are all cached), make sure you manually (!) relocate the cache to somewhere else – or, for that matter, completely disable it in Menu / Tools / Settings / History / Cache Size as can be seen in HERE. To relocate it back to the main storage (or even a RAMdisk, if its being completely deleted each reset and the decrease of RAM memory isn’t a problem either because, for example, you use a 128M RAM model), just follow my previous Opera cache relocation tutorial.
Problems I’ve discovered and/or fixed in the meantime
On MS Smartphone (Windows Mobile Standard) phones, when you have really low RAM memory (you’re running out of it), problems may occur with keyboard shortcuts. Namely, no matter what hardware shortcut button you press, the same functionality (in general, Reload and / or Back) will be executed. This can lead to confusion – at first, it caused me a lot of headache too until I’ve understood how this all works.
All in all, if your hardware dialpad buttons don’t do what they’re supposed to do, you may want to shut down (some) other apps and / or Opera Mobile tabs. This will free up some RAM, which will result in the buttons working again.
There’s still no hardware application button support (you can only tie button shortcuts to dialpad / keyboard buttons), but now that I’ve published a FULL tutorial and explanation of all decent Windows Mobile button enhancers, including how you can configure your hardware buttons to simulate the pressing of numeric (dialpad) buttons, this isn’t that big an issue. Just make sure you read the Button Enhancer Bible and do what’s there.
There had been a problem with non-English operating systems because of the wired-in (English) directory names with the initial release. This, along with manually fixing it, has been fixed in the meantime; that is, current builds no longer have this problem.
Verdict
Opera Mobile is and, as it seems, definitely remaining the best browser for both Pocket PC’s and MS Smartphones. While there still are some glitches (the worst of them, the lack for hardware app buttons, having been fixed by me), these problems are nothing compared to the generic sluggishness and/or Web standards incompatibility with (most of) the other browsers. Make sure you get at least the trial version.
2. New (1.0.5) Picsel version released!
There is (see THIS) also a new version of the Picsel Web browser. To get it, download the CAB file here (mirror HERE). You only need to download the CAB file; you do NOT need to install the previous Picsel version first, no matter what is stated HERE
As opposed to some XDA-Dev folks, I haven’t found much improvement. For example, the CSS compliance is still very bad (the result of the Acid2 test is HERE; that of the CSS1 test is HERE). The Ajax compliance isn’t a tad better either (tested with THIS and THIS test suite).
All in all, there isn’t much improvement. You may still want to give it a try if you are a big fan of the GUI. I, myself, would still stick to either Opera Mini or Mobile. Don’t necessarily believe the hype

3. New Spb Pocket Plus
Spb Pocket Plus has always been one of the best Pocket PC (Windows Mobile Pro / Classic) system enhancers. The brand new, just released 4.0 version boasts, in addition to a lot of new functionalities, a, compared to the much less significant changes during the 2.x-3.x version jump, considerable
(screenshot showing the four tabs, all populated, and the drop-down list (now, only having one element) of the invisible tabs in the upper right corner. For comparison: a screenshot of the context menu of the old, 3.x-series version HERE, also showing there haven’t been any new buttons / any tabs in it.)
It has received the following niceties:
screen dragging mode; note that the autoscroll can be a bit of a pain in the back; it’s sometimes the best to disable it
tabs (with a pretty welcome context menu – very few other products have the same, as can also be seen in the “Tab context menu (if any)” row of the chart of the Web Browsing Bible)
adding the ability to switch off / on keyboard dragging in the context menu
a separate quick access button, next to the “Action” button of the address bar; note that “Search” here makes a quick Google search with the text you enter in the address field.
The settings screen has remained similarly simple – as you can see, there isn’t much to choose from. The same stands for Menu / Spb Pocket Plus, which didn’t change either as can be seen in HERE. As far as saving Web pages is concerned, you can still only save them as simple HTML files – no MHT or full HTML page saving is possible. Incidentally, as can also be seen in the last screenshot, the new SPP version has a system-level (not only available when saving pages, but from every app that would, otherwise, use the system-level, default, very dumb file dialog) file dialog box like that of Mad Programmer, whose FileDialogChanger I’ve often recommended. HERE’s a screenshot of the Setup program where you can en or disable it. (note that, as opposed to Mad Programmer’s FileDialogChanger, you can’t define exceptions – there’re no configuration capabilities of the new “File Open/Save Dialog”).
Compare this to the immense setting / menu options of PIEPlus or even MultiIE and you understand why I still recommend either of these for the serious Internet Explorer Mobile user, as opposed to Spb Pocket Plus. Not that SPP would be THAT bad any more.
It also has some bugs, but, knowing how great the Spb folks at bugfixing are, I’m pretty sure they’ll be fixed VERY soon:
clicking the cross in the upper right corner (to close the IE window) doesn’t work if there are more than one tabs open. You MUST manually bring up the Start menu and switch (in cases, re-run so that the execution is switched to it) to the program you want to. Of course, if you use a third-party task switcher (for example, the highly recommended Magic Button, PHM’s Alt-Tab or almost all the hardware app button enhancers reviewed HERE)
the smooth scrolling mode isn’t really doing what it’s supposed to: in Landscape mode, it’s, in general, scrolling more than it should or even scrolls multiple pages. Some people have also reported other problems with it; see for example THIS.
4. New version of jb5
In the MS Smartphone Web Browsing Bible, I’ve elaborated on the brand new web browser jb5, which, back then, only had a Smartphone version. Late August, a brand new, 5.0.79 version has been released for both the Smartphone and, now, the WM5+ Pocket PC’s. While it’s still having problems and I still consider it much inferior to Opera Mobile / Mini, if you need the special features (for example, in-page text search, which, on the Windows Mobile platform, is only supported by the currently unavailable NetFront and the memory hog & on several handheld models super-slow Minimo) jb5 offers, you might want to check it out. I’ll let you know as soon as it receives a really useful and recommended version.
5. Web Viewer for WM5
There is a brand new multitab IEM plug-in, “Web Viewer for WM5”, HERE.
Unfortunately, this title still has a lot of problems and, consequently, I don’t recommend it. As with jb5, I’ll announce when a useful, bug-free version is released. I also recommend the comments HERE.
6. Other stuff
In some of my earlier articles, I’ve already elaborated on two not really recommended newcomers: TeaShark and UCWEB. IMHO, it’s, currently, pretty useless to bother about these browsers. I’ll let you know when a considerably better version is released.

Menneisyys said:
All in all, there isn’t much improvement. You may still want to give it a try if you are a big fan of the GUI. I, myself, would still stick to either Opera Mini or Mobile. Don’t necessarily believe the hype
Click to expand...
Click to collapse
So it doesn't have any of the cool updated stuff found at the following link?
http://www.picsel.com/flash/uploads/index.html
May not be the best web browser ever, but the pdf and Office viewing is superb. I mean really, was adobe kidding with that awful LE edition?
NS

NotShorty said:
So it doesn't have any of the cool updated stuff found at the following link?
http://www.picsel.com/flash/uploads/index.html
May not be the best web browser ever, but the pdf and Office viewing is superb. I mean really, was adobe kidding with that awful LE edition?
NS
Click to expand...
Click to collapse
I've only compared the Web browsing fcuntionality.

When using Picsel on my phone and the rotate option, it rotates the browser window 90 counter-clockwise. Does anyone know how to change this to 90 clockwise? I ask because I use a P4000/Titan and it rotates the image away from the keyboard.
I've tried some of the registry entries, such as rotatedirection, but they didn't do anything.... or I put the wrong values

REVIEW: Great, free Web browser Opera Mini 4 beta 3 is out – a MUST!

Opera Mini, particularly when used under a decent MIDlet manager, has always been one of the best choices for the Web browsing on any current handset. The new beta version of the forthcoming, 4-series Opera Mini, exactly two months after the last beta (see THIS) has just been released, and boasts a lot of goodies.
Getting it is done the same as before: navigate to HERE with either a mobile browser (or a WAP-capable desktop one, if you're ready to transfer the JAR file to your handset in a way explained in the MIDlet Bible), click the link in the middle of the page and it'll be automatically downloaded and deployed. After that, you can start it in the same way as other MIDlets (or, with Symbian, other programs).
1. Most important bugfixes: cookies, fonts
First and foremost, the cookie problems have all been fixed. These, in the previous, version 2 beta, caused a lot of problems under the, otherwise, excellent and most recommended Windows Mobile Esmertec Jbed MIDlet manager, along with a lot of non-Windows Mobile platforms. These problems are all gone – I’ve never encountered any cookie problem with any sites I use under the most common Windows Mobile MIDlet managers (IBM J9, TAO, Esmertec Jbed). The same (no cookie problems at all) stands for the Symbian-based Nokia N95, Nokia’s current “consumer” flagship model.
Second, some of the font problems have also been fixed. For example, beta2 was unable to render bold typeface with “extra large” characters and, in general, there was abolutely no support for different character sizes in, for example, headers. These problems have all been fixed. For example, as far as the bold + largest font size combination is concerned, see THIS screenshot (showing bold works with the largest chars). When it comes to different font sizes (headers etc), with my standard charsize test page, the tests resulted in excellent results (the following three screenshots have all been taken on a QVGA WM2003 HP iPAQ h2210 running the current (6.1.1) version of IBM J9; as can be seen, there’s no font smoothing with the smallest fonts under J9, just like Jblend, and unlike all the other KVM’s): 1 2 3.
Unfortunately, there’s still no italic support. I don’t know why the Opera Mini folks don’t implement the support for these.
2. High-quality picture support added
So far, it wasn’t possible to see the images inside a Web page in their original glory (unless you downloaded them, that is). Now, with the introduction of the “High” quality image mode, images will be fetched and presented at their original size and quality. This is certainly very good news. Some real-world examples of this and its consequences:
QVGA screenshot (IBM J9 6.1.1 running under WM2003) of a 640*480 pic in non-one column mode (original HERE)
VGA screenshot of a graphics-based chart I’ve posted to HERE: HQ (High Quality) mode; MQ mode and LQ mode. Pretty much different, eh? You’ll want to stick to the HQ mode when you really want to read for example image-based charts in my articles.
3. Opera Link support added
This is one of the best and most innovative new features in OM4b3. So far, even the desktop Opera (let alone the mobile versions!) has been pretty much neglected in this regard; now, this has changed. Please read THIS article for a generic overview of all these questions, along with most of the favorite synchronizer solutions released so far.
I’ve found this pretty intuitive and easy-to-use. You only click the “Synchronize Opera…” link on the startpage, fill in your Opera username / password (or, alternatively, quickly sign up for the service – it can be done right from the Opera Mini GUI!) and click / press Login (left softkey). After this, OM4 announces it has successfully synchronized your bookmarks as can be seen in the following screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, there’s a decent tutorial HERE explaining all these steps on both the desktop and Opera Mini.
Note that, as opposed to the desktop Opera browsers, it’s only links created in any (!) Opera Mini clients (they’ll show up under the “Opera Mini” folder in desktop browsers) that are loaded / synchronized in a way so that they become available locally, without Opera Mini’s having to connect to the central link service and do. Favorites under “More bookmarks” (favorites added in the desktop Opera will be behind this) will always be accessed online. If you find this too slow (I do), make sure you re-create the given links in the main folder of your Opera Mini. One of the easiest way is mass drag-and-dropping (with keeping Ctrl down if you don’t want to move, just copy them) the favorites in the desktop Opera (Bookmarks / Manage Bookmarks…) into the Opera Mini folder there. After a (forced) synchronization (Manage / Synchronize) , the changes will be seen in Opera Mini too and they will be available locally, not on the Web (and not in the “More bookmarks” folder, which, in addition to the lengthy download, also means a screen tap or navigating there).
I had no problems with my synchronization tests between my two desktop Opera browsers (you’ll need the latest, just-released 9.5 version of Opera for this!) and several Opera Mini clients running under both Windows Mobile (tested under several different MIDlet managers: Esmertec, TAO, IBM) and Symbian.
I’m absolutely sure you’ll LOVE this feature. And, of course, consider switching to Opera on the desktop too, in order to make the synchronization flawless and the easiest. Of course, you can access the online favorite repository with a non-Opera desktop browser too, but only in HTML mode, which also means mass-operations like quickly migrating a lot of favorites into Opera Mini (by just moving / copying them between folders) will be impossible. You’ll need a native, local client (that is, the desktop Opera and its Manage Bookmarks… dialog) to do this.
4. RSS Feeds
Feeds, which have also been added in this version, are pretty easy to control / use, albeit are a bit simple; for example, there’re no auto-download or notification capabilities. Its being integrated to the browser has a VERY nice consequence: whenever you’re on a Web page with an RSS feed, you will promptly be notified of RSS feeds being available. In addition, the RSS feed of these pages is pretty easy – again, thanks to the RSS feed integration to Opera Mini.
Subscribing to feeds is pretty simple in the new Opera Mini 4. When a page contains compatible feed(s), on the page, the type of the feed will be displayed. This is a link, which you can follow. Then, you’re shown the contents of the feed. Here, if you click “Subscribe” (again, a link the top of the page), it will be added to the pool of subscribed feeds. This screen can be easily accessed via the “Feeds” link on the start page (or, by presing * and, then, 0 - a new shortcut). As feeds need to be manually refreshed, you will need to click Refresh to see the changes . After it has downloaded the results, their number will be displayed (in parentheses).
Note that with pages having more than one (compatible) feed (for example, XDA-Developers), after clicking the “Feeds” link at the top, you’re shown the list of the feeds as can be seen in HERE. You can, then, select the one you’d like to see and maybe subscribe to.

5. Additional tips - Tables with inner tables
With tables containing inner tables like the one HERE and HERE - as opposed to charts without inner tables like the one HERE), OM4b3 will, at first, provide a map view without any horizontal scrolling. An example screenshot is HERE, as opposed to the way it renders tables without inner ones (see THIS for an example of the latter). With the latter type of tables, it’s not possible to zoom out to minimap view.
6. Some problems you need to be aware of
6.1 No “Fullscreen mode” shown in Options on Windows Mobile
Under all the major (Esmertec’s products, IBM J9, TAO; note that I do NOT recommend Aplix’ Jblend for Web browsing because of the very strict security model continuously prompting the users for authorization) Windows Mobile MIDlet managers, the “Fullscreen mode” is completely missing in the Settings menu (IBM J9 screenshot). This is visible on the Nokia N95 (screenshot HERE) – even using exactly the same high-quality version of OM. The latter means it’s in runtime that OM decides whether to display this checkbox or not. It seems upon realizing it’s running under Windows Mobile (as opposed to the Symbian case), it just hides the checkbox.
Note that this isn’t that big an issue. If you don’t have hardware numeric keys, Ctl + * and Ctl + * works in all the three on the SIP. With hardware keys, it’s even easier: for example, with the built-in keyboard of the Universal, a simple Fn + 8 will make it work. Also see the MIDlet Bible for more info on these questions.
6.2 Gmail problems on Windows Mobile
As is also reported HERE, under Windows Mobile, if you add the main Gmail homepage (NOT Inbox – that is, after logging in!) as a favorite, upon subsequent browsing attempts, the page won’t be shown as can be seen in this TAO Intent .1036 and this Jbed 2.2 screenshot.
Strangely, it does work under Symbian (tested on Nokia N95).
A quick and always-working hack is NOT putting the Gmail homepage directly in Favorites, but your Inbox (after you've logged in). Then, if you need to switch to another account, you can just sign out (link in the top right corner); then, the log-in (main) page will be displayed OK.
6.3 Still no non-Western fonts in smallest charsize
In order to keep the size of the JAR file down, the developers of Opera Mini have chosen NOT to include any non-Western character in their custom, (in most MIDlet manager) edge-smoothed Small font set. Only a rectangle will be displayed upon encountering characters like this. This is pretty much similar to how Thunderhawk, the famous (IMHO, Opera Mini is far more recommended), albeit, for long not updated Windows Mobile Web browser did: it also uses a custom fontset and it also refuses to render anything non-Western.
This means you MUST use at least the Medium font size on your handset (because it uses the native charset of the device and not that of Opera Mini), should you want to read pages using the non-Western alphabet. This is a problem on Symbian devices (tested on the Nokia N95) because of the HUGE charsize of even the “Medium” fonts. Just compare THIS (small) and THIS (medium) screenshots. The latter indeed uses HUGE fonts, and the additional smoothing (not available under Windows Mobile) doesn’t really help this.
Windows Mobile devices fare far better in this respect (example screenshot HERE of a QVGA MS Smartphone running OM4b3 under Jbed. BTW, as can also be seen, no “Full screen” checkbox is visible here, either.)
6.4 Other user-reported problems (I haven’t encountered them)
Some people reported (see THIS) Mobile view (fit-to-screen; renamed from “Fit to width”) doesn’t work as good as under the OM 3.x series. In my practice, I prefer reading pages in non-Mobile view (because, as with Nokia’s browser on S60 3rd devices, Opera Mini does a GREAT job of showing the actual text without the need for horizontal scrolling); therefore, I can’t really comment on this bug.
Opera Mini 4 beta sometimes uses wrong form in webpage
7. Recommended links
The MIDlet Bible (Cross-posts: PPCT, AximSite, XDA-Developers - 1, XDA-Developers - 2, XDA-Developers - 3, FirstLoox, BrightHand, HowardForums, SPT, MoDaCo, PocketGamer.org, PocketGaming.de)
Beta 2 review
MS Smartphone Web Browsing Bible
Pocket PC Web Browsing Bible

Does it support connections via proxy server? (Earlier versions of Opera Mini did not.)

me said:
Does it support connections via proxy server? (Earlier versions of Opera Mini did not.)
Click to expand...
Click to collapse
It does with Jbed and IBM J9. Read the MIDlet Bible.

Menneisyys said:
Second, some of the font problems have also been fixed. For example, beta2 was unable to render bold typeface with “extra large” characters and, in general, there was abolutely no support for different character sizes in, for example, headers.
Click to expand...
Click to collapse
One correction here. I think that the fonts problems were not related with the Opera client but with the Opera server.
I had no idea about that but I realized that this is probably the case because while I was still using the beta 2 it suddenly started rendering bold fonts on the web pages that didn't render before! The day that this happened, coincided with the beta3 release.

me said:
Does it support connections via proxy server? (Earlier versions of Opera Mini did not.)
Click to expand...
Click to collapse
Menneisyys said:
It does with Jbed and IBM J9. Read the MIDlet Bible.
Click to expand...
Click to collapse
Now this is getting interesting in a frustrating kind of way.
Opera Mini v4 betas1,2,3 do support connections through a wap proxy server. The Opera final version does not!
I just installed Opera v4 final and I get a Java exception error that it cannot connect (in Jbed)! I re-installed additionally the Opera v3.1 and connects without a problem. Also the beta3 which fortunatelly I didn't unistall, connects without a problem (together with the rest of the Java midlets I have on my PPC, i.e., Gmail and Mobile GMaps).
Something very strange is going on here, I'll check it out and post to the Opera v4 Final thread.

Also check out my review of the final Opera Mini 4 at http://forum.xda-developers.com/showthread.php?t=344095

Opera Mini 4: A new star is born - the FREE(!) Web browser you MUST give a try to

Opera Mini has a short history (the project was started only slightly over two years ago), but, today, with the release of version 4, it has become one of the most useful, best browsers available for anything handheld.
In this review & tutorial, I provide you with a complete tutorial of installing and using this recently released browser and, in addition, I explain why you may want to prefer it to other Web browsers.
First, some screenshots taken on wildly different platforms / devices:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(VGA Windows Mobile Pocket PC screenshot)
(QVGA Symbian S60v3 Nokia N95 screenshot)
(176*220 Windows Mobile Smartphone screenshot)
Note that note of the above screenshots use real full screen mode – hence the top and bottom bars. The last screenshot with enabled full screen mode can be seen in the following screenshot:
1.1 Why you will want to use it?
You’ll find it a god-send particularly when
you’re over a VERY slow (for example, GPRS) connection and want the fastest browsing solution, preferably with images
yours isn’t an unlimited data plan; that is, you pay big bucks for every Megabytes
you don’t want to pay for a third-party browser (they, in general, cost big bucks)
you’re a desktop Opera user (you should be – give it a try, you’ll love it, particularly if you have a notebook with a high-resolution (at least SXGA+) screen – Opera’s zoom-in features are way better than those of Internet Explorer and are only matched by Mozilla) and you want to synchronize your bookmarks with it as easily and automatically as possible
you look for an easy-to-use, non-separate, integrated RSS reader – that is, you need a Web browser that also notifies you when you surf to a page also having RSS feed
your mobile device is resource-constrained, while you’d like to keep tens of Web pages, preferably with images, open at the same time (without the need for reloading). This is where most (if not ALL) other browsers severely fail, even on high-end mobile devices packed with tens of Megabytes of free (!) RAM memory.
you want something like the minimap feature of the Nokia Web browser on newer Nokia devices, the NetFront 3.4 Technical Previews (which, being just previews, are severely restricted and lack Flash, more than 10 favorites and other goodies) on Windows Mobile or the iPhone Safari browser but usable on any platform (incl. any Windows Mobile device) – but even faster and having much less resource demands
you want something with hardware button / keypad support. Opera Mini supports them just great. If yours is a phone with the dialpad on the front of your phone, you’ll REALLY love these shortcuts because, then, you will rarely (if ever) need to use the softkeys (or, on touchscreen devices, the stylus) to navigate the menus. Using button shortcuts is WAY faster. As opposed to this, (on Windows Mobile) NetFront and Minimo doesn’t support buttons at all and (on Symbian) Nokia Web isn’t very good either. The MS Smartphone version of IEM is, shortcut button support-wise, is also definitely inferior to Opera Mini – it supports far fewer operations than Opera Mini.
In the following two sections, I compare it to the other browsers available for the two current, major mobile operating systems, Windows Mobile and Symbian. (Freely skip the one not pertaining to you.)
1.1.1 How does it compare to other Windows Mobile browsers?
While there’re quite a few Web browsers on Windows Mobile, only few of them are actually usable: the built-in Internet Explorer Mobile (preferably with a capable plug-in like PIEPlus, Spb Pocket Plus 4.x (but NOT older versions) or MultiIE), Opera Mobile and NetFront. These three browsers (and the other Web browsers and IEM plug-ins I, generally, don’t really recommend: Picsel, Thunderhawk, Minimo etc.) all have their strengths and weaknesses, on which I’ve thoroughly elaborated in my two (a separate one for Windows Mobile Pocket PC’s and Smartphones HERE and HERE, respectively) Web Browsing Bibles
1.1.2 How does it compare to other Symbian browsers?
On Symbian, there’re two other, really decent Web browsers.
Opera Mobile is available for all S60 v2 (!) and v3 devices and is pretty decent. For example, unlike its Windows Mobile counterpart, it supports in-page text searching (which is painfully missing from the WM version). It, however, doesn’t use a compression service, which means long downloading times over slow links and has pretty high memory requirements.
Nokia’s Web browser coming with all S60v3 FP1 models is also very decent: it supports in-page searching, Flash Lite, minimap view and a lot of other goodies. However, it’s decidedly slower than Opera Mini and if your phone is a Nokia N95-1 with 64M RAM only, you’ll inevitably run into the MAJOR problems caused by its taking a lot of memory.
While Opera Mini 4 allocates about 10 Mbytes of memory to itself (which is a big letdown on the N95-1), after the initial memory allocation, no more memory will be allocated and you can safely go on browsing.
1.1.3 When will you still need to stick to a traditional Web browser?
Unfortunately, there’re several areas Opera Mini doesn’t excel at. While, say, 95% of the time it works just wonderfully (no wonder I use it for most of my Web browsing on both Windows Mobile and Symbian phones) for just accessing the Web, in the remaining 5% you’ll need to “fall back” to other, traditional, non-Java-based browsers. You wi
if you need full JavaScript and/or AJAX support. Only a subset of these standards are supported (albeit still a LOT more than in Internet Explorer Mobile, Thunderhawk or Picsel!). See THIS for more info if interested.
These browsers will inevitably be invoked when you make Opera Mini download a file (this, however, doesn’t mean you will need to stick to using these browsers!)
As you can’t make Opera Mini the default system browser, links received in e-mails and HTML files in the local file system will still need to be browsed via these browsers – unless (if it’s a remote Web page, not a local, say, HTML file or file attachment) you paste the address of the page to the address bar of Opera Mini (OM for short).
If you need Java applet and/or Flash (Lite) support. It’s with very few pages that you do need them; for example, Handango’s Friday giveouts, requiring full Flash compliance, are one of them. And, for YouTube, you will want to use alternate methods to play, NOT direct, in-line playback. (If you do use the TCPMP plug-in under Windows Mobile, then, you will still need to use IEM.) That is, generally, it’s when you want to play some online Flash games (see THIS Flash Bible for more info if interested) that you will need to stick to a browser supporting Flash.
There are some other restrictions; for example, you absolutely MUST edit text longer than 4-5 kilobytes. Then, because of the MIDlet Manager (also abbreviated as KVM) restrictions, you’ll end up having to switch to a “real” browser – at least for the time of editing.
You need to save Web pages to the local file system and/or copy text out of them. Unfortunately, OM is completely unable to do this. Unfortunately, with current KVM’s, not even copying a URL (for example, that of the current page) to the clipboard is possible.
Again and again, speaking out of experience, a casual user will very rarely need to switch back to these browsers and, after finding out how easy Opera Mini is to use, how quick it is to load pages and operate and how wonderfully low system requirements it has, he or she will want to stick with Opera Mobile.

1.2 Installation
(Note that this section only contains WM5+ Windows Mobile Pocket PC screenshots showing the MIDlet manager Jbed. As I recommend Jbed the most and I do urge you to install Jbed on your phone too, I didn’t bother including screenshots / instructions on installing OM under other MIDlet managers. Similarly, I don’t give you Symbian screenshots either – installing and running OM is done in a very similar way as under WM.)
1.2.1 Installing a MIDlet Manager
If you have a Windows Mobile device with at least WM5 as the operating system (sorry, previous operating systems aren’t supported – not even WM2003SE, let alone even older OS’es) and it’s not the latest models (for example, the Kaiser / Mda Vario III / Tilt) of HTC, then, you will want to download the Jbed MIDlet Manager HERE. If you do this on your desktop computer, transfer the CAB file to your handset and click / activate it from File Explorer (or any other explorer tool like Total Commander). Just install it (it’ll be installed in the main memory) and you’re set – you can go on installing Opera Mini itself.
Jbed will run on ALL Pocket PC’s and Smartphones running at least WM5. If you have an earlier operating system, check out the “Platform compatibility” section (with three rows corresponding to non-phone-enabled Pocket PC’s, Pocket PC Phone Edition and MS Smartphones in turn) in the main MIDlet Bible chart for download links; then, you’ll want to use either TAO Intent or IBM J9. Of the two, I’d prefer the former, but that’s only me.
Note that you can ONLY use this MIDlet manager if and only if your locale is set to a language using Western characters: Spain, France, Finland, you got it. (This doesn’t only cover Western languages; for example, Estonian only uses letters already present in some other Western languages. That is, while Estonian is an East-European language / locale, it’ll still work.) If, on the other hand, you have a, say, Slavonic locale (for example, Slovak), Jbed will NOT work. If your locale is Russian, then, you will want to check out THIS file instead; linked from HERE. Note that the latter MIGHT work with other East-European locales; I haven’t tested this myself.
Also note that if you have a non-phone WM5+ Pocket PC (for example, a Dell Axim x50(v) (with the WM5 upgrade) /x51(v) etc.), you will also need to download THIS file and unZIP its contents to \Windows on your Pocket PC.
1.2.2 Installing Opera Mini itself
If you’d like to download the browser onto your desktop computer and, then, transfer it to your phone, go to THIS page and click the opera-mini-advanced.jar link (I don’t provide a direct link to the latter as it always changes, as newer and newer builds are released). A JAR file will be downloaded. Transfer it to your PDA via ActiveSync, a memory card, a wireless connection, the WinCE File System plug-in of Total Commander etc., fire up Pocket File Explorer on your phone and click it. It’ll initiate the install process.
If, on the other hand, you’d like to do this on your phone, enter the address http://mini.opera.com/ into any of your Web browser on your phone (screenshot HERE) , scroll down and click “Try the new Opera Mini 4” link. This will take you to the page http://mini.opera.com/?rel=4, where you only need to click “Download high memory version”. Then, the installation will start – just like with the offline process outlined in above.
It’s pretty easy to install Opera Mini. You’ll just need to answer OK, Yes and Continue. For example, when you’re presented THIS screen (asking you whether OM should be put in the root folder or any subfolder), THIS and THIS question to to launch it. During the process, you’ll see other dialogs; for example, THIS showing the compilation process.
Now that you’ve launched the app, keep answering OK / Yes / Accept as can be seen in THIS screen. On the next screen, you’ll (again) press OK (the “Yes, but ask me next session” will be selected by default; it’s perfectly OK with us). After this, answer Yes to the next question too and, then, activate Accept to accept the license agreement.
Upon the first execution, after you click a link (and, therefore, initiate a network connection) you’ll need to press at least one button several times until the progress bar is full. You can do this with any button if you have numeric buttons; do this with the D-pad (any directions) if you don’t.
1.3 Usage
After this, you’ll find using OM pretty straightforward by using the two WM5 softkeys (or the touch screen). I’m pretty sure you’ll find it easy to use.
Note that in the review of the previous beta3, I’ve already spent a LOT of time explaining how link synchronization and managing RSS feeds work. Please do refer to the article for a complete overview of both these techniques.
Users new to OM will surely notice that entering text is done differently than using regular Web browsers. Now, if you click (move the focus to and press the Action button on it) a text input field / area, you won’t be able to do an “in-line” edit, but you’ll be taken to a separate and, in most cases, full screen text editor. Jbed’s text editor is one of the best (for comparison: TAO Intent’s (a well-known, widely used KVM) editor has severe restrictions: it doesn’t support copy/paste operations), but keep in mind that it (as with ALL the other KVM’s on Windows Mobile and some KVM’s on Symbian) can’t edit texts larger than some 4 kilobytes.
Note that after exiting (Menu / Exit) or shutting down (with an external task manager tool or by resetting the device) OM, you will need to go to Start / Programs and select the Esmertec Jbed icon (highlighted HERE) and click (or, press Launch while it’s selected) “Opera Mini” inside. Note that if you’re a somewhat more advanced user, you can easily invoke OM4 without starting Esmertec Jbed first (that is, you save some screen taps / button presses) by following my remarks in the “Direct, system-level links (shortcuts) to MIDlets” row of the main chart of the MIDlet Bible.
Under newer Symbian versions, you need to basically do the same as above. The difference is that these newer Symbian versions (as opposed to, say, the MIDlet Manager on the S60v1 N-Gage) puts a direct link to OM into Applications (example screenshot HERE); that is, you don’t need to create these links yourself.

1.4 Changes since beta 3
In addition to some, mostly “dumbphone” (that is, not Symbian / Windows Mobile-related) bug fixes, there is some welcome news for touch screen users.
First, you may already have noticed how complicated it is to reorganize the favorites list on the mobile phone. You repeatedly need to select Manage / Move up (or, down) to move a given favorite up or down, which involves a lot of work (and there’re no sorting capabilities built-in). Of course, if you have access to a desktop Opera browser, you can quickly do this stuff by either quick sorting (Sort / View by … in the context menu) or mouse-based drag and drop.
Now, if you have a touchscreen-based device (for example, a Pocket PC), you can, with the stylus, just highlight a favorite (as you would do when using the traditional way of reorganizing them) and, then, keeping the stylus down, drag it to its new position (note that this will not be animated – that is, you’ll only see the favorite moving after you’re lifted up the stylus from the touchscreen).
In addition, there’s another goodie you might want to know: now, keeping down the stylus on a Web page results in the context menu to be shown. The context menu slightly varies on the markup you’ve invoked it on:
links have a "Link" submenu, allowing for opening the link either with or without images (and also getting its address) as can be seen in HERE
images have a “Open Image” shortcut, which, in addition to showing the image in a new window, also let for downloading and saving it
the page itself (no links / images) “only” have the mobile view switch, reloading and information shortcuts
This context menu is also accessible by pressing “1” on the keypad - or, of course, emulating the keypress on the on-screen software input panel or, finally, assigned to a hardware button. This all has been thoroughly explained in the MIDlet Button Bible – make sure you DO read it because it’ll REALLY ease your life and increase your productivity.
Note that this all has also been (shortly) mentioned HERE.
The home screen also has some new links; for example, the brand new "GameJump" taking you to some freely available Java MIDlet games directly downloadable to your phone. They aren't particularly good; that is, don't expect anything like Gameloft or I-Play-like (see the links to the best Java MIDlet game developers at the end of MIDlet Bible!). I've tested three of these games on my N95: Arcade Park 1 (compared to the native PPC version, REALLY weak), CS Garfield (pretty OK but there're much better, albeit commercial bowling titles for Windows Mobile) and Spin Blocks (not worth bothering on devices with QVGA or larger screen because it uses 176*220). All in all, there's no free lunch; however, you may still want to look around for some games.
1.5 Frequently asked questions / misconceptions
1.5.1 Proxy servers and Opera Mini 4
Some people state (see for example THIS and THIS) the final version of OM4 doesn’t work with proxy servers any more, unlike with earlier OM4 beta builds. I’ve thoroughly tested this and found out that they do work assuming you explicitly switch the network access mode from Socket to HTTP (Menu / Tools / Settings / Network protocol).
1.5.2 Lack of code signing and the consequences
As you may already have noticed, Opera Mini is unsigned. This, unfortunately, means (depending on the actual KVM used and the operator restrictions / customizations) nagging screens when trying to access the Net. With Windows Mobile, you can “hack” the most widely used KVM’s, including the highly recommended Jbed. With Symbian, where the situation can be worse - again, depending on what additional restrictions are added by your mobile operator. Of course, you can always de-brand your device as is explained at, say, HERE.
You may also want to read THIS post (in THIS, pretty instructive thread) on why OM4 isn’t signed by default. (In a nutshell: the high price of the Verisign root certificate would have forced the developers of OM to make their browser commercial.)
I hope someone will be able to come up with a signed version of OM4 that works on at least Windows Mobile (with Jbed at least) and / or Symbian phones.
1.6 Recommended links
Please DO read the articles linked above; most importantly, the MIDlet Bible. It explains a LOT you might not ever have thought of. You will find it REALLY useful. If you do want to use Opera Mini to its full potential, you MUST read it and all the related tutorials (for example, the one on button handling, which is of extreme importance with OM4).