Develop Bugs

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!

Has somebody the patched version for the O2 Wap-flat???
I need it .. Pleeeeese

Works great indeed. I have a new cooked rom installed on my Artemis and it's asking me to allow a connection every time. Tried many midlet managers from TAO and none of them give me the security setting where I can change it to 'session'. The Esmertec manager refuses to start. Any tip on this?

this work great with all roms for hermes had a flashing day yesterday and it worked with all thankz for review good for new users
thankz,
jdac21§

I wish it was easier to use this. Having to load the java emulator and run through the questions is kind of annoying.

kiddyl said:
Works great indeed. I have a new cooked rom installed on my Artemis and it's asking me to allow a connection every time. Tried many midlet managers from TAO and none of them give me the security setting where I can change it to 'session'. The Esmertec manager refuses to start. Any tip on this?
Click to expand...
Click to collapse
Give a try to Jbed.
BTW, what Tao versions did you try? 11.x? Did you give a try to the somewhat older (10.x) series? The latter has an explicit Security menu.
I've also elaborated on this in my forthcoming Midlet Manager Bible; did you check out the charts? They are already public - see the dedicated thread at http://forum.xda-developers.com/showthread.php?t=326768

maevro said:
I wish it was easier to use this. Having to load the java emulator and run through the questions is kind of annoying.
Click to expand...
Click to collapse
1. You mean the questions the first time you start it? After that, you'll be only asked once each time you restart the midlet manager.
2. in addition, if you use the Tao Intent manager (or IBM J9), you can create a direct link to the midlet as has also been explained in my forthcoming article - see http://forum.xda-developers.com/showthread.php?t=326768

One problem on the HTC TOUCH is that if you enter a long text in a text box, for example replying to this thread, then once you press the OK button the browser closes.
I tried preparing this reply with Mini Beta2 but could not due to problem already mentioned. Finally done with Opera Mobile.
Regards

Menneisyys said:
1. You mean the questions the first time you start it? After that, you'll be only asked once each time you restart the midlet manager.
2. in addition, if you use the Tao Intent manager (or IBM J9), you can create a direct link to the midlet as has also been explained in my forthcoming article - see http://forum.xda-developers.com/showthread.php?t=326768
Click to expand...
Click to collapse
I have a direct link on my Ubiquio 503g but it is still annoying and I hope that Opera 9 will be out sooner then later...

kiddyl said:
Works great indeed. I have a new cooked rom installed on my Artemis and it's asking me to allow a connection every time. Tried many midlet managers from TAO and none of them give me the security setting where I can change it to 'session'. The Esmertec manager refuses to start. Any tip on this?
Click to expand...
Click to collapse
Simply search for risidoro's midlet manager in the forum. There you have to confirm only once per session.
Works perfectly on my artemis.

maevro said:
I have a direct link on my Ubiquio 503g but it is still annoying and I hope that Opera 9 will be out sooner then later...
Click to expand...
Click to collapse
Still no word on Opera Mobile 9's real release date. That is, I wouldn't hold my breath.

Here's an excerpt from my fortcoming Midlet Bible on all these issues:
2.4 TAO Intent
This is the MIDlet manager having come with almost all HTC-manufactured WM5 Pocket PC’s and Smartphones. Now that the developer no longer exists, HTC seems to have switched to Esmertec Jeodek / Jbed instead (and independent MS Smartphone / PPC PE manufacturers like Sharp or Samsung prefer Aplix JBlend instead). However, this still means there’s a HUGE number of installed userbase of this MIDlet manager.
Currently, two major releases of these titles are widely used: the 10.1 series and the latest 11.1 series. Of course, if you have a Pocket PC / Pocket PC phone (Windows Mobile Professional / Classic) and not just a Smartphone (where only 10-series MIDlet managers run), you’ll want to go for the latter as it’s compatible with many more standards and MIDlets than the former one (for example, the 10.1 series was unable to run any of the jBenchmark benchmarks I’ve thrown it at – it just exits when starting them. This may have been a memory issue, in which the 11.1 series is also better). In addition, it also supports MIDlet groups (screenshots: 1 2 3 4), which is also a definite advantage over the 10.1 series.
There are a LOT of different 11-series TAO Intent MIDlet managers out there. At first, it’d be very hard for a beginner to choose. In the following section, I explain what these versions are, how they compare to each other etc.
First, let’s start with the latest version, 11.1.7.1034 (or 1034 for short; from now on, I’ll only use the last four, in our case, relevant version numerals to refer to a given version), which is available HERE for download. It’s meant for any kind of PPC PE phones – but NOT for non-phone devices. If you don’t plan to run applications using the Net (for example, Opera Mini), you can safely install this version (even on a storage card). However, if you DO plan to run Net-related MIDlets, forget it right away – this version uses the wrong approach (prompting each time, not each session) network access-wise. And, again, if you have a non-phone Pocket PC, forget about it too.
What does this Net access problem mean? Upon trying to access the Net, they prompt the user to allow the operation each time there is any kind of communication. For example, if you browse the Web with Opera Mini, you’re presented this dialog each time you click a link. This is, of course, unacceptable.
While the 11-series (as with the older, 10-series) Intent MM does have a dedicated “security” setting dialog (just tap-and-hold the icon of the deployed MIDlet and select “Security”) where you can set authentication to the much more user-friendly “session” (which only prompts the user just once, at the beginning of each session – that is, after starting Opera Mini), the publicly available, installable .1034 version doesn’t let for setting anything in this dialog. As can clearly be seen, only “Oneshot” is available – not only with Net access, but also with other settings – even with Local connectivity. Opposed to this are all the other (former) 11.x versions, where “Session” and, with local access, “Blanket” are also available. If this is a problem, you will want to pick a 11-series version that doesn’t suffer from this bug.
In order to 1, getting rid of the Net authorization bug and 2, find non-phone-capable TAO Intent versions, we’ll need to go back in time a while and switch to version .1023. There, basically, are five versions of this CAB file.
The PPC Phone version HERE
The non-phone PPC version HERE
The “turbo” version for PPC Phone is HERE
The “turbo” version for standard (non-Phone) PPC is HERE
The above links point to modified, enhanced versions of the original TAO Intent manager. These modifications have been done by Russian hackers ZuRiUs and dFine1107 and involve the ability to be installed on a storage card and to be installed on non-HTC devices, including non-phones (for example, the Dell Axim x51v). That is, these do contain major hacks and improvements.
Finally, XDA-Developers hacker risidoro’s version is HERE (only for PPC Phones; it doesn’t run on non-phone devices)
Of these, I recommend the “turbo” versions most, for both PPC and PPC Phone Edition models. While I haven’t really measured remarkable speed increase with the jBenchmark tests, many users have reported generic speedup with at least starting / loading MIDlets. This is because many library files have been decompressed by the creator, meaning no decompression needed in runtime. This may indeed result in some speed increase. (Note that this trick doesn’t work the 10.1-series TAO Intent MM’s; this is why only the new series has a separate “turbo” version.) Note that this also means this version occupies about two times more storage than the non-turbo one; therefore, if you have little built-in storage, consider installing it on a storage card.
Note that, while risidoro’s version is very popular, it’s, in my opinion, not as good as the Russian hacks. The sole reason for this is that it can’t be installed on a storage card. This, particularly if you have little built-in storage or plan to install dozens or hundreds of midlets, can be pretty bad news – don’t forget TAO Intent manager stores MIDlets under a subdirectory in its home directory, which means it’ll dump its deployed MIDlets on your storage card if you install it there, leaving your built-in storage uncluttered. That is, even if you instruct it to be installed on a storage card, it’ll install itself into the main storage (meaning the MIDlets will also be put in there later).
Risidoro’s only major advantage over all the other, listed (Russian) .1023 installers (and, for that matter, the .1034 one) is that it correctly sets file associations, unlike the Russian CAB’s. This means if you click a JAD or a JAR file in the local file system (or on a Web page), it’ll correctly deploy it. With the Russian CAB’s, this isn’t possible (if you install them on a storage card; when installed to the main memory, they’ll require no Registry import), unless you import THIS Registry file I’ve created for your convenience. Note that it assumes your storage card is named “Storage Card”. If it’s not the case (because you use a localized (non-English) device or a Pocket PC with two storage cards), make sure you change the occurrences of “Storage Card” to the name of your card before importing the script.
Note that some cooked ROM’s (for example, XPlore 1.1, mUn's aRTM and mfrazzz’s XDA Mobile 6 Release 2a – but not Release 3, which already switched to the Esmertec MM) contain the .1029 version (see for example THIS for more info on this particular version). It has no session problems either. It’s, currently, not available as an installable CAB file, though - this is why you will want to check out the .1023 (or, if the net access bug isn't a problem, .1034) version(s) instead.
So far, I’ve only discussed Pocket PC compatibility. Unfortunately, as has already been pointed out, the above-linked 11.1 series can’t be used on (touchscreen-less) MS Smartphone (Windows Mobile Standard) models. You will need to get THIS file if you want to install TAO Intent (v10.1.7.561) on your WM5+ Smartphone. Should you need a WM2003 one, get THIS (v10.1.0.14) instead.
EDIT & BREAKING NEWS: Risidoro has patched the .1034 version so that it supports session-based Net authorization. This means you will want to go for .1034 even if you want to run apps using the Net.
See his thread at http://forum.xda-developers.com/showthread.php?p=1484696 - a worthy read. The direct link to his patched .1034 CAB is at http://www.webalice.it/risidoro/intent/Risidoro_Intent_MIDlet_Manager_11.1.7.1034.cab
He has also published the .1029 CAB in his post.

I have the Emertec Jbed JVM on my Tmobile MDA. Been running Opera mini 4 beta 2 without a hitch. This morning I got up and went to do some surfing and the JVM refused to load. It starts for a second then quits. I have not deleted any files on my PPC. I have no idea why it would just stop working. Any of you run into this problem?
John

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

davis4559 said:
I have the Emertec Jbed JVM on my Tmobile MDA. Been running Opera mini 4 beta 2 without a hitch. This morning I got up and went to do some surfing and the JVM refused to load. It starts for a second then quits. I have not deleted any files on my PPC. I have no idea why it would just stop working. Any of you run into this problem?
John
Click to expand...
Click to collapse
Yes, it's timed out. There was a time-bomb in it. See my related thread.

that sucks. is the pay version offered by handango the same?

davis4559 said:
that sucks. is the pay version offered by handango the same?
Click to expand...
Click to collapse
Dunno as I haven't had the chance to test it. I'll contact them and ask whether they want to release a trial.

Have you seen the Opera Mini MOD versions? It can do some of the things you mention as failings: copy text/images/links to clipboard, open >1 pages in tabs.
http://www.opera-mini.ru/index_e.html
How to get it into english:
http://www.htcwizardweb.net/node/854

Menneisyys said:
Here's an excerpt from my fortcoming Midlet Bible on all these issues:
However, if you DO plan to run Net-related MIDlets, forget it right away – this version uses the wrong approach (prompting each time, not each session) network access-wise. And, again, if you have a non-phone Pocket PC, forget about it too.
Click to expand...
Click to collapse
Hi Menneisyys,
i've solved the problem with Intent midlet manager 11.1.7.1034. Now it will ask connect permission on a per-session basis!
I've published the hacked 1034 together with previous 1029 and 1023 HERE.
Please, update your great guide!!!
Bye and thanks for your always-perfect work!

[X51V] ROM WM6.1 EN Professional, private pure edition

{
"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"
}
My First thanks to Football. As there was a mysterious A05 from Football embedded in his Magic x51v when he sold it, I've decided to continue his work with this A06 WM6.1 rom
I am starting this new thread as the new rom offers a lot of new features (compare to the previous béta)
Original thread here.
Current status is:
Rom A06 PROß00Cp (private "pure" edition):
WM6.1 Professional - CE OS 5.2.19949 (Build 19949.1.2.0) with "4.8 MB Pagepool"
And includes the following
-- SDHC support
-- WPA-TSK vagus fix.
-- NetCF 3.5
-- SQLCE 3.5
-- Softkey Applet (a powerfull applet that allows you to change your softkey without having to soft reset)
-- TCPMP 0.72 with subtitle support and YouTube support (Subtitle support for SMI in video "Intel 2700G" mode and not in "Intel 2700G Decoder" mode)
It also includes aac & ac3 plugin. TCPMP is an alternative to WM Player. File associations is availble in TCPMP settings
nota: You can also use the new Subtitle plugin , just put subs.plg under \windows and go to tcpmp settings, subtitles to activate the plugin, It's great because it can run under "Intel 2700G Decoder" mode with higher performance than the older one. Thanks will5
-- PIE 6.1 and YouTube plugin, scrolling can be done using directional button, PIE Ramdisk is available in Scripts & Tricks section (it uses ram for PIE cache to improve performance). About the YouTube Plugin, it works natively. If you surf on YouTube with PIE, when you click on a video a context menu will be displayed (see screenshot above). Then you will be able to save the video or to view it online through TCPMP.
-- DF's PIM Backup 2.8 (a replacement for Data Backup)
-- PocketRAR 3.71
-- Windows Live 10.6.33.0600
-- aximsite wireless switcher
-- x51v Mix
-- ozVGA and WM6.1 trueVGA dlls, to switch in TrueVGA mode
-- MortScrip 4.1
-- rlToday with minii skin (see today screen shots), an alternative for Date today plugin, it display home time, plus 2 other time zone.
-- NoPluginsToday, a switcher to quickly de-activate all your plugin and re-activate them all. Plugin de-activation will boost your device.
-- MagicButton, is activated by default, so all application will close and release memory instead of being minimized (a replacement for switcher bar)
-- XnView, a better alternative for Pictures & Video, File associations is available in XnView Options. (nota: xnview embed a screen capture functionality)
-- Ramdisk see "Menneisyys" article
-- Hibernate, a powerfull tool to claim unused memory.
-- Remote Desktop Mobile
-- UC ROM capability
with following registry tricks:
HKEY_LOCAL_MACHINE\System\ObjectStore\RegistryType=0 , (file based registry)
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Navigation\"4-Way Nav"=0
Why cook a Professional rom for a non phone PDA?
The idea is to have this rom offer a better compatibility for PDA phone based applications.
This rom will first boot in WM6.1 Professional this is mandatory to have the last version of PocketCM run properly on the x51v.
I strongly suggest this freeware, it's a must for your axim (Don't forget to use a vga skin).
Running under WM6.1 Professional will display some phone related information on the upper toolbar.
To avoid that you can easily switch to WM6.1 Classic using Pro2classic under Scripts & Tricks section. Pro2Classic is a switcher that you can use to switch the OS in any of the Professional or Classic mode.
Béta00Cp, download link
Thanks wllw from 4PDA for Mirroring WM6.1 Professional Beta00B | WM6.1 Professional Beta00B
Previous béta thread for WM6.1 Classic private rom
You can use Paveld PPeditor if you want to change PagePool and generate a new crc file. (Thanks Paveld & wllw from 4pda)
Instruction to use Paveld PPeditor
Thanks Football, I started this project mainly because you sold your device. Then you came back with the fastest x51v ROM ever.
Thank you for let me know of your tweaked boot.rgu. I also used your kitchen so this new A08 Pro rom also include different applet organization and UC Rom Capability from Football kitchen.
Original A08 Classic rom and kitchen from Football are available here.

Very nice Makuu... I will start the flashing process now. I will let you know what, if any, issues I find.

Woooooooow!!!
Many thanks for share!

God. Have to wait 20 minutes. God damn you rapidshare!

At work-----must remote in to home PC now!
Makuu my friend--awesome work as usual. Will flash it tonight. Can't wait. (My lrToday skin is a little better though )

Not sure if you were aware Makuu, but a new version of Windows Live has been released.
http://forum.xda-developers.com/showthread.php?t=384178

Makuu, first... love the new ROM (even though having a few issues). For a list of issues/comments so far, read on:
(1) The volume control shows both the speaker and a phone's speaker. I believe that you corrected this in a previous ROM to hide the phone volume slider.
(2) I am having a problem (when MagicButton is running) when I go into the Dell WLAN Utility, the OK / X button, as well as all MagicButton icons (top of screen), stop responding. The start button still works so I go into Task Manager and kill the Dell WLAN Utility when I want to exit. I believe this may be related to the 'Home' icon and the WLAN connection icon sharing the same location on the top bar. (NOTE: As a work-around, if you toggle MagicButton off before using the Dell WLAN Utility, then it does not lock up the OK / X button)
(3) I am assuming that you changed the WLAN drivers? I am noticing some strange behavior with WLAN that I did not have in the previous Beta 006. For instance, when I go into the Dell WLAN Utility, click Settings (Wireless tab) and then highlight and hold my wireless network to make the sub-menu pop up, and choose Turn Off Wi-Fi it works to turn off the Wi-Fi as expected. However, if I try to hold it again and choose Turn On Wi-Fi, it does not appear to turn it back on... I just get the pinwheel spinning constantly (the busy symbol). It does appear that the Wi-Fi is turned on again, but it doesn't stop showing busy. If I click OK a couple times to get out of the WLAN Utility, the Wi-Fi icon is missing from the lower right of the screen (next to the Bluetooth icon). This also worked fine in Beta 006, although I think I remember the icon disappearing a couple of times in Beta 006 also. This makes me wonder, do we actually need the Dell WLAN Utility, or can we just use the default Wi-Fi configuration utility that comes with WM6.1? (NOTE: The Wi-Fi icon reappears after a soft-reset)
(4) Another issue with the WLAN Utility. I am having to usually turn on, then off, then back on the Wi-Fi in order to get it to connect. Sometimes, when i turn it off, then back on again, it shows immediately connected on the bottom icon (next to Bluetooth) but the icon at the top of the screen stays not connected. If I turn the Wi-Fi back off and on again, it usually clears up the issue. It is generally less reliable to connect to my wireless network now though. I suspect that you made some changes to the Wi-Fi... different drivers or something, because I did not have these issues with Beta 006.
(5) What does the 'NoPlugins Today' program do? It does not appear to do anything when I try to launch it.

Thanks mphayvanh, your skin is better for Landscape but because of the today screen it 's difficult to read the time.
djlenoir, I will check the Msn Live version that you mentioned but last time I tried a newer version, It was bigger than the one I use and so to get it working would mean that I had to remove something else from the ROM.
(1) This is a normal issue when you are running in WM6.1 Professional. That's why I have provided a switcher to WM6.1 Classic (see scripts & tricks section). Under WM6.1 classic this issue will disappear.
(2) I could not reproduce your issue with WLAN utility. But sometime MagicButon gets tricky to use.
(3) & (4) I didn't change anything there it's still the same like in beta 006.
(5) It's a toggle for activating/deactivating all the today plugin that you regularly use. After calling it once. Go to Today. Then call it again and again. You'll see what I mean.

concerning the problem 2 with wlan and magicbutton, it exists since the x51v exists. I have seen it the first time when I was still with the standard dell wm5 rom, and installed vBar (another utility that closes running programs).
You should have precised that the problem doesn't occur in all screens of the WLAN Utility, but just the one where you might enter the password to access the WirelessLan.
The problem appears with any program that replaces the smart minimize button.
I think that this screen of the wireless lan utility has a special behaviour with the smart minimize button, and that special behaviour cannot be controlled by MagicButton or other similar tools.
I have read somewhere that you can use control+Q to avoid killing the task.
Anyway I don't think this is a realy annoying Issue, since it works by exiting MagicButton before loading this screen.

Makuu,
do you plan to build a 6.1 french rom ?

good
Thank you very much
A bug: I can't find bluetooth explorer

miljbee, I need a WM6.1 French rom as basis to do so.
Jack1101, I removed it.

Cool! Will post a generic heads-up to my last misc news article.

makuu said:
miljbee, I need a WM6.1 French rom as basis to do so.
Click to expand...
Click to collapse
Did you saw that ?
http://forum.xda-developers.com/showthread.php?t=380584

makuu said:
This rom will first boot in WM6.1 Professional this is mandatory to have the last version of PocketCM run properly on the x51v.
I strongly suggest this freeware, it's a must for your axim (Don't forget to use a vga skin).
Running under WM6.1 Professional will display some phone related information on the upper toolbar.
To avoid that you can easily switch to WM6.1 Classic using Pro2classic under Scripts & Tricks section. Pro2Classic is a switcher that you can use to switch the OS in any of the Professional or Classic mode.
Click to expand...
Click to collapse
PocketCM is THAT important?
I am not looking forward flashing a phone OS on non-phone ppc... I don't use my PPC as a contact book, I have a phone for that...
I think it's nice that you're investing on this option for the axim users, but I believe that you should not abandon the classic os...

ursoouindio, PocketCM is not part of the rom (But it's really a nice contact application that you can operate without a stylus), it's just that this rom will support it's installation. It's impossible to have it work on any other rom.
miljbee, I could not get the rom it ended to a dead link. If you have a link please post it. However, You talking of a QVGA rom, I need a VGA one.

where is this "scripts & tricks" section ?

It's embedded in the rom in Programs menu.

Bug:
Cannot select the city name when want to add new city time in the irToday.
Keyboard does not show up.
Tried on a fresh hard reset without anything installed, the keyboard still not show up when want to enter city time.
- Thanks for not including the "Bluetooth Explorer". Bluetooth explorer in Lenny's ROM is not working after installing the broadcom bluetooth driver that support A2DP. Bluetooth Explorer is practically useless.

Pip_X said:
Bug:
Cannot select the city name when want to add new city time in the irToday.
Keyboard does not show up.
Tried on a fresh hard reset without anything installed, the keyboard still not show up when want to enter city time.
Click to expand...
Click to collapse
This is a bug with lrToday, not the ROM. I haven't been able to change the initials for the days of the week for my Calendar (see my POST #5 screenshot). This has been an issue with lrToday on WM5, WM6 and still WM6.1 because the keyboard disappears all the time. I should post this issue on Rotlaus' website.

[ROM][GSM][WWE] AC - Naked ROM - 1(WM:23001,HTC:2.07)

NOW DISCONTINUED. SEE POST ON PG7 FOR ALTERNATIVE
AC - Naked ROM
This ROM is designed for "professionals", that is, someone who needs functionality and raw performance over endless crap, gimmicks and slow animated uselessness.
Testing shows it to be extremely fast, uses 45% of memory day-in-day out.
{
"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"
}
(does not include CorePlayer, Garmin XT, Skype or Screen Capture)
Use it if you meet this criteria
1. use the stylus often and dislike big controls designed for fat fingers
2. need raw speed and good looks without animation
3. want minimal installed cabs so you can use your own which you keep in /Storage
4. do all your Comms (phone, messaging, tasks, calendar) from the Today screen
5. use your device as GPS on the move (tested with Garmin, Microsoft Voice command over bluetooth)
6. do not use MMS, upload to facebook or youtube.
7. prefer original WM over HTC apps and feel where possible
8. hate Microsoft Media Player and use CorePlayer or Pocket Player Bundle
9. prefer Voice Command to read out your calls and text messages rather than fancy ringtones
10. don't like Titanium or Manilla that much ('cause it ain't included!)
Installed apps
Adobe Reader 2.5
Office (without Onenote)
Total Commander (replaces Explorer)
HTC: FM Radio, Calc, Camera (inside Pictures & Video)
.NET 3.5
Removed
Windows Media Player & DRM, Titanium, Touchflo & 3D, MS & HTC stuff like marketplace etc
Installation
Once installed it will take a while before Windows starts.
During this time your device will have a blank screen.
It has not been bricked just wait a bit! Also see Known Issues for hints.
Current version & download
1(WM:23001,HTC:2.07)
Recommended Extras
Microsoft Voice Command (working call announcements) - reboot after install & see Settings for reading normal priority txt msgs
HTC Task Manager - reboot after install
Known Issues
prob: no longer asks for screen calibration on install.
fix: Do manually via Settings > Screen until I find a fix.
prob: after installed you'll get a white screen saying "please wait".
fix: Hit one of the top icons and it'll go away.
note: I'm looking for a fix without enabling HTC's RunCC.
prob: clicking the battery icon doesn't do anything (it should really invoke power).
fix: access manually via Settings until I fix.
prob: screen text is default (one size too large imho). Need to find the registry key to notch it down a level.
fix: do manually via "screen"for now.
prob: the background is a gif as I can't workout how to get the compiler to use a jpg for the Default_stwater.
fix: none
issue: slight colour banding because of it.
prob: empty Tools folder on Start-Menu.
fix: delete it from /Windows/Start-Menu/Programs
issue: can't find the location to kill it so you'll need to do manually.

Do you have pics of your version ?

coming up

I can not download the rom file. bad link

It's working fine and has been for hours

Sounds like nice ROM. May I ask you for some pictures?

Of what? It has the default Windows dialer and the start and program screenshots can be found at the top post (I added them). Regards, Andrew

Sounds good... But can u publish yo kitchen, m8, becoze i need to integrate a cirillic dialpad and keyboard to yo ROM?
And make a mirror, plz...

snoopy20 said:
AC - Professional ROM
This ROM is designed for professionals.
It is extremely fast and uses 41% of memory whereas most take 60-70%.
Click to expand...
Click to collapse
Don't you think it would be fair to mention that those "most" roms are using TF3D, and you are not?
There are many roms, in which you can have this "professionalism" in memory and speed if you switch off all interfaces and leave bare WM.
So, be fair, and change this line. Compare it ONLY to bare roms without manila. Then it may be not so super-special, but just another rom without manila....
But of course the "professionals" will see it. It's the "not professional" who may fall for this advert....
P.S. If I switch off manila, then I have 39% after boot-up (with lumos, and other software in background). Is that something special? Not, it's standard. At least with Nataly roms.....

mjaxa said:
Don't you think it would be fair to mention that those "most" roms are using TF3D, and you are not?
There are many roms, in which you can have this "professionalism" in memory and speed if you switch off all interfaces and leave bare WM.
So, be fair, and change this line. Compare it ONLY to bare roms without manila. Then it may be not so super-special, but just another rom without manila....
But of course the "professionals" will see it. It's the "not professional" who may fall for this advert....
P.S. If I switch off manila, then I have 39% after boot-up (with lumos, and other software in background). Is that something special? Not, it's standard. At least with Nataly roms.....
Click to expand...
Click to collapse
Dude cut him some slack.. The guy is just contributing his work. It wouldn't hurt to make a general comparison of his rom with others regardless if it is with touchflo or not since he is not asking money for his rom. At least he did not name 'whose roms were those.' If he wants to call it a professional rom then so be it, nobody has monopoly over that word is it not? Let the user judge for himself if this rom is worth his while or worthy of such title.

Here's two reasons ...
1. there are no startup or scheduled services running so battery life is rather good. In standby last night with no activity and full charge the battery still shows as full (that's 8hrs standby!).
2. there is no Manilla OR Titanium. Which other ROM does that? There is no Windows Media Player. Which other ROM does that?
You'll have to try it out and see why.
Other poster >> I'll zip up the kitchen and post as soon as I get a moment. What are these two packages - if they really add value I'll include them for next release.

Look, I'm cutting slack, etc but... If you publish something, then it's up to public to judge it.
So, it's good there's another cook, only let's be fair. It used to be, that such roms were called inthe thread title [naked] or [no manila] or anything else, BUT it was clear.
reason 1 - hmm, to me it looks like the common fault of all diamonds - battery metering, especially at full charge isn't reliable. For me the way to check it is to measure the mAh drain of the battery. This is closer to being objective.
reason 2 - every rom which is provided with kitchen can do that (remove manila), and lately there are lots of those, so practically everybody can adjust the rom to their liking with or without manila or titanium.
Anyway - what I'm suggesting is a clear and consistent naming and comparison of the roms. Since pietrucci stopped doing benchmarks there are no reliable scores to compare speed, memory etc, so people look at descriptions. Therefore those descriptions should be as accurate (and fair) as possible especially when you are trying to compare one rom with the other.
Good luck with your project.

Well I agreed with what you were saying and made the changes you suggested. I've also changed the 41 to 45% memory as this is what it uses with constant usage over a couple days.
A.

snoopy20, will you make a new b.23004 ROM with 2.09 drivers? And kitchen actually yet...

snoopy20 said:
Here's two reasons ...
1. there are no startup or scheduled services running so battery life is rather good. In standby last night with no activity and full charge the battery still shows as full (that's 8hrs standby!).
2. there is no Manilla OR Titanium. Which other ROM does that? There is no Windows Media Player. Which other ROM does that?
You'll have to try it out and see why.
Other poster >> I'll zip up the kitchen and post as soon as I get a moment. What are these two packages - if they really add value I'll include them for next release.
Click to expand...
Click to collapse
OK, so you've got a fast and stable rom... but a rom that doesn't do almost nothing...!
In that way, it's better buy a cell phone instead of a PPC/PDA...

Ignore the whingers...
..., their venal sniping and their inane comparisons with the work of others.
As the saying goes: "There are none so blind as those that will not see..."
I like that your ROM is geared towards using your phone as a tool, not a toy.
Looking forward to seeing what you come up with in the future...

mjaxa said:
Don't you think it would be fair to mention that those "most" roms are using TF3D, and you are not?
There are many roms, in which you can have this "professionalism" in memory and speed if you switch off all interfaces and leave bare WM.
So, be fair, and change this line. Compare it ONLY to bare roms without manila. Then it may be not so super-special, but just another rom without manila....
But of course the "professionals" will see it. It's the "not professional" who may fall for this advert....
P.S. If I switch off manila, then I have 39% after boot-up (with lumos, and other software in background). Is that something special? Not, it's standard. At least with Nataly roms.....
Click to expand...
Click to collapse
I agree, cut the chef some slack. I take "Professional" as in 'professional users only'. Naked roms do take some patience and skill to tailor to your needs. Some people want a rom that takes little effort others do want more control.

I''m agree with huisie. You make a good job and this ROM realy needed. First, I d't know any other naked wm6.5 ROM with fresh build within. Sec, I d't know any ROMs without WMP and so many deleted trash.
I think You wrong to call your ROm 'Professioal", but the name "Bussiness" are fit correctly: this ROM not for a play, it's for job.

Truely speaking... I am loving this ROM... Thanks a lot....

Excellent, the first happy customer.
I will update to 30004 soon and aim to wrap up the kitchen asap.
If anyone knows how to or where to ask in order to solve these little bugs please let me know or ask away on my behalf.
PS) I'm after stability and bug-free operation over compiling to the latest XIP release so I wont be doing daily updates. Most XIP updates seem to pertain to fixing OEM compatibility and Titanium issues anyway so it's not so much an issue with my ROM.
PS2) I think TaskManager is mandatory but when compiled into the ROM it doesn't run automatically, hence I provide as a separate package. The compiled voice command doesn't read out calls/messages either which is why that is as a package too (tested and working this way).
A.

Multiplatform(!) review: Opera Mobile 10 beta released!

I’ve thoroughly tested the brand new Opera Mobile 10 beta on all the supported mobile phone platforms (Windows Mobile Professional / Standard and Symbian S60). In general, apart from some problems, I liked what I saw – particularly on Symbian and the touchscreen version of Windows Mobile.
The browser is available for download HERE for both operating systems. For Windows Mobile, a unified download (for both subtypes) is provided.
1. Windows Mobile
Also see the XDA-Devs discussion, which starts on THIS page.
1.1 Touchscreen devices
I’ve installed it on the HP iPAQ 210 and found it great. Sure, it lacks some features (for example, the excellent dynamic zooming & text reflowing features of some (not all!) of the 9.50/9.70 builds and the (hacked) Flash Lite support), but, on the whole, I was more than happy with it. It doesn’t load much faster than the older version (9 seconds as opposed to 10) and, as has already been pointed out, lacks some of the goodies; however, it’s a pleasure to use.
Unfortunately, it (still) doesn’t support Opera Link, one of the best features of Opera Mini and the desktop Opera browser. (One of the reasons I’ve completely switched to using Opera on the desktop.)
Also see THIS demo for more info.
1.2 Non-touchscreen (Microsoft Smartphone) devices
1. Unfortunately, the two hotkeys are in no way supported on any of the tested Smartphones (on the s710, including the ones on the hardware keyboard). Therefore, a cursor emulator is needed to access even the menu at the bottom and almost everything. In-page scrolling and, on the Quick access page (default one and the one that comes up when you open a new tab), switching between the address input field, the Google field and the main surface area works OK. (Hotkeys are supported just great on Symbian S60.)
2. There are no button scrolling shortcuts, as opposed to the SP version of 8.65 (the last Opera Mobile version to have a dedicated MS Smartphone version – see my MS Smartphone Web Browser Bible HERE).
3. While you can’t use the hotkeys in fullscreen mode, with SPHelper, you can still access the two buttons in the lower right and left corners. (Hotkey-based scrolling – 2/4/6/8 – works just great on Symbian S60.)
176*220 (old) MS Smartphones running the official WM5 (tested on the HTC s310 (Oxygen)): excellent (tested running from memory card) program / page load time; responsive. Landscape mode isn’t supported – as opposed to the s710.
HTC s710 Vox (320*240 newer Smartphone running the official WM6): running great. However, multi-function keys on the hardware keyboard don’t work (always the numeric values are inserted) – to enter them, you need to use either the on-screen keyboard (which, BTW, is rendered properly even on a 176*220 Smartphone in Portrait mode) or the numeric keypad.
All in all, until the hotkey bug is fixed (operating the browser with SPHelper is really painful), you will want to stick with either the old 8.65 version or Opera Mini. (This, again, only stands for the non-touchscreen-enabled MS Smartphone platform, NOT the touchscreen-based one!)
2. Symbian S60
It’s nice to see Opera to return to Symbian, which they have seemed to have completely neglected in the last few years.
I’ve tested OM10 on the Nokia N95 on firmware version 30 and found it excellent. It has very quick program / page loading; OK multitabs (albeit, after opening two – large, about 600k+ - Wiki pages, when minimizing Opera mobile, it was immediately terminated from memory, showing Opera indeed took up quite a bit of RAM memory. This was expected – if you need multitab supporting up to 30 pages open at the same time, your only choice is Opera Mini.)
Basically, it’s as easy to use as Opera Mini 4.2 and has a lot of additional goodies – for example, text copy/paste is supported and works, unlike in 4.2. (Note that the text copy/paste in the current beta of Opera Mini 5.0 works just fine on Symbian.)
The only problem I found was the lack of support for Flash Lite 3 – to access Flash Lite content, you’ll still need to use the built-in Nokia Web browser instead. (Nevertheless, you will want to use it was a last resort to play back, say, YouTube videos. Dedicated YouTube players are far better at playing back videos – no stuttering, unlike when using Flash Lite.)

Thanks a lot Amigo!, as always great reviews
I´ll post a link to this on Opera Thread
Cheers,

Menneisyys said:
I’ve thoroughly tested the brand new Opera Mobile 10 beta on all the supported mobile phone platforms (Windows Mobile Professional / Standard and Symbian S60). In general, apart from some problems, I liked what I saw – particularly on Symbian and the touchscreen version of Windows Mobile.
The browser is available for download HERE for both operating systems. For Windows Mobile, a unified download (for both subtypes) is provided.
1. Windows Mobile
Also see the XDA-Devs discussion, which starts on THIS page.
1.1 Touchscreen devices
I’ve installed it on the HP iPAQ 210 and found it great. Sure, it lacks some features (for example, the excellent dynamic zooming & text reflowing features of some (not all!) of the 9.50/9.70 builds and the (hacked) Flash Lite support), but, on the whole, I was more than happy with it. It doesn’t load much faster than the older version (9 seconds as opposed to 10) and, as has already been pointed out, lacks some of the goodies; however, it’s a pleasure to use.
Unfortunately, it (still) doesn’t support Opera Link, one of the best features of Opera Mini and the desktop Opera browser. (One of the reasons I’ve completely switched to using Opera on the desktop.)
Also see THIS demo for more info.
1.2 Non-touchscreen (Microsoft Smartphone) devices
1. Unfortunately, the two hotkeys are in no way supported on any of the tested Smartphones (on the s710, including the ones on the hardware keyboard). Therefore, a cursor emulator is needed to access even the menu at the bottom and almost everything. In-page scrolling and, on the Quick access page (default one and the one that comes up when you open a new tab), switching between the address input field, the Google field and the main surface area works OK. (Hotkeys are supported just great on Symbian S60.)
2. There are no button scrolling shortcuts, as opposed to the SP version of 8.65 (the last Opera Mobile version to have a dedicated MS Smartphone version – see my MS Smartphone Web Browser Bible HERE).
3. While you can’t use the hotkeys in fullscreen mode, with SPHelper, you can still access the two buttons in the lower right and left corners. (Hotkey-based scrolling – 2/4/6/8 – works just great on Symbian S60.)
176*220 (old) MS Smartphones running the official WM5 (tested on the HTC s310 (Oxygen)): excellent (tested running from memory card) program / page load time; responsive. Landscape mode isn’t supported – as opposed to the s710.
HTC s710 Vox (320*240 newer Smartphone running the official WM6): running great. However, multi-function keys on the hardware keyboard don’t work (always the numeric values are inserted) – to enter them, you need to use either the on-screen keyboard (which, BTW, is rendered properly even on a 176*220 Smartphone in Portrait mode) or the numeric keypad.
All in all, until the hotkey bug is fixed (operating the browser with SPHelper is really painful), you will want to stick with either the old 8.65 version or Opera Mini. (This, again, only stands for the non-touchscreen-enabled MS Smartphone platform, NOT the touchscreen-based one!)
2. Symbian S60
It’s nice to see Opera to return to Symbian, which they have seemed to have completely neglected in the last few years.
I’ve tested OM10 on the Nokia N95 on firmware version 30 and found it excellent. It has very quick program / page loading; OK multitabs (albeit, after opening two – large, about 600k+ - Wiki pages, when minimizing Opera mobile, it was immediately terminated from memory, showing Opera indeed took up quite a bit of RAM memory. This was expected – if you need multitab supporting up to 30 pages open at the same time, your only choice is Opera Mini.)
Basically, it’s as easy to use as Opera Mini 4.2 and has a lot of additional goodies – for example, text copy/paste is supported and works, unlike in 4.2. (Note that the text copy/paste in the current beta of Opera Mini 5.0 works just fine on Symbian.)
The only problem I found was the lack of support for Flash Lite 3 – to access Flash Lite content, you’ll still need to use the built-in Nokia Web browser instead. (Nevertheless, you will want to use it was a last resort to play back, say, YouTube videos. Dedicated YouTube players are far better at playing back videos – no stuttering, unlike when using Flash Lite.)
Click to expand...
Click to collapse
OP , i have installed you app, good app but a little clunky in my phone.it shuffled for a long time to enter CNN. i like the icon most. LOL

I like it

Slightly out of date review. And now Opera Mobile 11 does not support Windows Mobile.

Opera mini 11 is for me the best Browser on Android platform.

[26.07.2010] Turbo3D v3.0 *FINAL* (also available from Marketplace)

Turbo3D
(Formerly known as HD2/Leo 3D Driver Patch)
{
"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"
}
PLEASE READ THE ENTIRE POST BEFORE DOWNLOADING ! CHEFS: PLEASE SEE this POST.
About
Many Snapdragon devices (HD2, Expo, S200/F1, TG-01, etc) have an issue with OpenGL that makes 3D games very slow and/or stutter. Turbo3D tries to fix this. The driver works on non-Snapdragon devices as well, but I doubt you'll see a lot of difference.
Usage
The CAB file for Turbo3D is attached and called "Chainfire-Turbo3D-X.X.cab", where X.X is the version number.
The Turbo3D driver is fully automatic - just install and reboot - yet you can override the default configuration. A short help file is also included in the configuration tool ("Turbo3D" in the start menu)
The Turbo3D driver can operate in 3 modes:
(1) "Original" - Don't do any magic, just use the stock 3D drivers, mostly terrible
(2) "Fast" - Improve performance as much as possible, works great for most games and apps
(3) "Smooth" (Anti-Stutter) - Prevent stutter lag, some games and apps need this mode to run smoothly
By default, any application the driver does not "know", runs in "Fast" mode. This default can be changed in the configuration tool. As soon as an app runs that uses GL, the driver registers this, and after running it for the first time, the mode to use for this app can be configured in the configuration tool. For most apps and games you will probably never have to change the default settings.
As stated, some apps and games require "Smooth" mode to run fluently (these are marked with a * in the list in the second post), for these you will have to go into the config tool and change the setting for that specific app.
This leaves only one setting in the configuration tool unexplained: the "frame time" setting. By default this is set to "18 ms" which seems to work well for most users. If you find all your GL apps and games are still stuttering, try setting this value to "20 ms" or "22 ms". It will slow down rendering slightly, but it might improve visuals. On my own device I get the very best performance on the "18 ms" settings, with "17 ms" introducing major stutter again.
Please note that the driver settings are read when an application starts. Changing settings in the configuration will not take effect until you restart the application that is using GL.
Compatibility
Compatible with all OpenGL able devices, but you will probably only see benefits on Snapdragon devices.
Installation
Before installing Turbo3D, first manually uninstall any older versions of Turbo3D or HD2/Leo 3D Driver Patch.
After that, just install the CAB (to device, NOT to storage card !), and reboot your device.
Do NOT install Turbo3D on a ROM that has an older version of the driver cooked in !
Marketplace and donations
Over 65 000 users are using my 3D drivers, only a handful have donated. So I'm going to try a little experiment:
You can now also get Turbo3D from Marketplace as an alternative form of donation (no need for PayPal). This is also so the general non-XDA public can get notice of the driver. The price is $ 3.99 / Euro 3.39 - or equivalent in your countries currency. The link only works if Turbo3D is available in your native market. Currently it is available in all English markets, and soon it will also be available in all German, French, and Dutch markets. If you are not from any of these markets, you can navigate to the United States / English or United Kingdom / English markets through Marketplace settings. Please, if you are from inside the EU, use United Kingdom, and if from outside the EU, use United States market (has to do with taxes, saves me a lot of work).
If you decide to give a little back to me through Marketplace, please also leave a 5 star rating and a comment on how well it works on your device and apps / games. This again helps me get more purchases from the non-XDA public
You can still donate directly to me here: http://www.jongma.org/dx.php
I've spent hundreds of hours trying to perfect this - please show your appreciation for my hard work ! Thank you !
Note that there is no functional difference between the version attached to this post and the one on Marketplace, but I would manually uninstall one before installing the other.
Extra
Attached is also a hardware accelerated Direct3D Mobile driver ("Chainfire-TG01-D3DM.cab"). Stock HD2 ROMs do not come with this driver. You could try installing it and seeing if it improves performance for certain apps and games, probably those that use DirectDraw. Some people have for example reported improved performance in CorePlayer using this CAB file. It was originally taken from the TG-01. I've been told by some chefs there is a Microsoft-built D3DM driver floating around that gives even better performance. I would not install this CAB file on anything else but a stock HD2.
Thanks to
lesscro, NuShrike, l3v5y, nrgz28, heliosdev, clubtech, christonabike, aussiebum, kholk, hanskl, GinKage, p50kombi, AstainHellbring and anyone I might have forgotten who helped test or had useful comments, etc.
Download
If you appreciate this patch, please make a donation or purchase it from Marketplace (see above)
NO REDISTRIBUTING THIS DRIVER! FOR COOKING RULES, SEE this POST --- SOFT-RESET AFTER INSTALLATION --- INSTALL ON DEVICE, NOT STORAGE CARD
all downloads << 3.0: 67091

Apps, games, benchmarks
Apps and games
This patch has been tested (at least somewhat) with the following apps and games:
- glBenchmark
- helios.dev "Test OpenGL"
- helios.dev "Test OpenGL 2"
- A few of my own OpenGL test tools
- Sense
- SPB Mobile Shell 3.5 (HW accel)
- Opera Mobile (GL mode, see this post by Tung_meister)
- Cubespace
- NFS Undercover [v0.1.5 doesn't seem to work nice, but v17 does?]
- Electopia Demo
- Boom Blox *
- Tower Defense **
- Flight Commander *
- Monopoly World *
- Xtrakt
- Experiment 13
- PowerVR demos *
* Reported to work best in "slow / anti-stutter" mode
** Reports differ on whether to use "slow / anti-stutter" mode or not
Note that if your phone is busy doing other things it will still make your phone slow! This patch only tries to fix driver-related stutter.
Please report your games/apps, whether they work better or not and in which mode they work right!
glBenchmark
Attached are some glBenchmark results of the various patch revisions. Some awesome improvements in the HD and Pro tests, as well as kTriangles/s. Though glBenchmark is nice, these figures do need to be taken with a grain of salt - it's not all that is important, smoothness and compatibility are also important.
Here's a grab out of the results.
Stock HD2 vs Patch 1.1
GLBenchmark HD ES 1.1: 487% ~ 1598 Frames up from 328
GLBenchmark HD ES 1.1 no GPU Skinning: 502% ~ 1647 Frames up from 328
GLBenchmark PRO ES 1.1: 107% ~ 229 Frames up from 215
GLBenchmark Pro ES 1.1 no GPU Skinning: 157% ~ 625 Frames up from 397
Swapbuffer speed: 496% ~ 556 up from 112
Averages: Lights: 116% ~ 1550 kTriangles/s up from 1350
Averages: Texture Filter: 159% ~ 2150 kTriangles/s up from 1350
Averages: Texture Size: 158% ~ 2150 kTriangles/s up from 1350
Averages: Triangles: 161% ~ 2150 kTriangles/s up from 1350
Test Suite
Well, it's not really a test suite, but here's 35mb of OpenGL ES v1 and v2 apps, games and demos I use for testing: http://rapidshare.com/files/408102039/Turbo3D-TestSuite.rar.html
Note that all of the included files are freely available from XDA, the authors' site, or a freeware app site.

Chefs and Developers
For Chefs
I am putting down some ground rules for using my driver in your ROMs:
The rules apply only to the Chainfire-Turbo3D-X.X package (you can do whatever you want with the TG01-D3DM package).
Cooking the driver patch is allowed if-and-only-if all of these conditions are met:
- The main release and support thread of your ROM is located on XDA-Developers.com
- The download of the ROM is "free for all" (with an exception for closed beta ROMs)
- The release and support threads note that this driver is used, "Chainfire" is credited for it, and includes a link to this thread ( http://forum.xda-developers.com/showthread.php?t=592663 )
- Turbo3D configuration tool must be included, working, and be available through the start menu (or a subfolder thereof)
- All files must end up in \Windows
- You must test it before releasing (NOTE: Turbo3D uses a service! Make sure it is working!)
If you do cook it into your ROM, I request you let me know either by sending me a PM or posting in this thread (thank you). I feel these conditions are fair. If you can't meet all of them, feel free to PM me.
All DLL and EXE files in my CAB are signed with a dummy certificate, you might want to remove those signatures before cooking in.
For developers
This patch blocks 4 bits-per-subpixel modes, but these can still be used by setting EGL_CONFIG_ID in your GL configuration attributes. Attached is a CSV with a listing of all (original) configurations, including their various attributes (including EGL_CONFIG_ID).

Changelogs
v3.0 *FINAL*, 26.07.2010
- Final tweaks
- Marketplace release (EN-US)
- Ready for cooking
- Works on all GL-capable devices, though aside from Snapdragon I doubt you'll see any difference.
v2.60 BETA, 21.07.2010
- Complete rebranding to "Turbo3D"
- CL libraries have been removed, as they don't work and nobody uses them anyways
- Added "help" tab
- Fixed an issue that caused "unknown" apps always to run in "fast" mode, instead of the configured default GL mode
- Fixed an issue related to .NET based OpenGL ES v2 apps
- Frametime is back to 18 ms
- Added "Test Suite" link to first post
v2.50 BETA, 08.07.2010
- Added ordinals to proxied functions, improves compatibility for some OEM-built apps (for example on LG Expo)
- Completely reworked the loading and initialization of the driver, so no ROM files have to be overwritten anymore. This negates the need for a seperate patch for each different device model, and improves compatibility with custom ROMs and newer stock ROMs.
v2.0, 20.04.2010
- Adapted the driver to decide performance factors based on registry instead of hard-coded
- Added CF3DConf, the configuration UI for the driver
v1.1, 01.12.2009
- Added glModeSwitch app to switch between normal (fast) and anti-stutter (slow) modes
- Fixed nasty timing error

Hi Chainfire!
Thanks for the effort. I've just installed your patch. Sadly it doesn't change anything

VanKurt said:
Hi Chainfire!
Thanks for the effort. I've just installed your patch. Sadly it doesn't change anything
Click to expand...
Click to collapse
- Did you soft-reset your device after installation?
- Which exact program/game are you having a problem with and what exactly is that problem.
Again, please note that if your device is busy with other things it will still slow down your game/app. Giving the phone a few minutes after boot-up of 'alone time' usually helps if that is the problem.

Experiment 13 seems to work ok for me, perhaps a little smoother if anything.

Chainfire Hi! First of all thank You for Your work both Leo and O2! Install your patch and electopia running much better than it was before. No lags! testing...

- Did you soft-reset your device after installation?
- Which exact program/game are you having a problem with and what exactly is that problem.
Again, please note that if your device is busy with other things it will still slow down your game/app. Giving the phone a few minutes after boot-up of 'alone time' usually helps if that is the problem.
Click to expand...
Click to collapse
Yes, I resetted the device and closed every running app.
For testing I used a little test-app I just wrote. It displays 16 textured quads and runs only at 5/6 FPS (with or without patch).
(Screenshot and binaries attached)

Me too 5-6 fps

VanKurt said:
Yes, I resetted the device and closed every running app.
For testing I used a little test-app I just wrote. It displays 16 textured quads and runs only at 5/6 FPS (with or without patch).
(Screenshot and binaries attached)
Click to expand...
Click to collapse
How sure are you that that is a driver issue and not a code issue? It didn't even run on any of my other phones I tried it on.

Bloomblox is allot better after the patch!
I tried running test opengl , it scores allot lower after the patch however it runs pretty smooth.
So it looks very promising

Which Test OpenGL? helios.dev?
Numbers aren't everything. I've had it score in the 200k range but it didn't look very nice

Chainfire said:
Which Test OpenGL? helios.dev?
Numbers aren't everything. I've had it score in the 200k range but it didn't look very nice
Click to expand...
Click to collapse
Yes that one , and yes thats why i posted the "however"
Thanks so far Chainfire!

Thaks Opengl work beter but Sense work me very slow

Hm, not 100%
Do you have a simple demo app that runs smoothly using the drivers? I'd be interested to take a look at the code, just to see if I did something wrong...

Stuck!
Thread stuck!

so far everything seems good to me..
never really had lagging, but all the things ive tested appear smoother.
sense is working fine (on the 148 rom)
thrown you 10 euro mate, at least you can buy a pint or two.
the shepherd neame christmas ale is highly recommended.

i use test v1.48 sense (2.5.19211619) work very slow must be test hardreset my hd2

Sense is fine here, but I'm on 1.43... Can't test until I have 1.48, obviously.