Monday, January 28, 2008

Opera Mini 4, Intent Midlet Viewer, Esmertec Jbed, AT&T Tilt

So I've been using Opera Mobile 4 for some time on my Tilt. When I switched the ROM over to the stock HTC ROM awhile back, I sorta lost my ability to use Opera Mini and GMail midlets on my Tilt using the Esmertec Jbed midlet container. It always told me I needed a data connection to use either one of the apps (I have an unlimited data plan, fyi) and failed out. Same way with google maps (sometimes, not always).

Well, awhile back I read a tip about turning off the proxy server (wap.cingular.com) on my MEdiaNet connection to improve performance. Now, I didn't really see an improvement in performance, but didn't see any degradation either, and as having no middleman is better, I nuked the proxy setting on the device.

Well, awhile back, but awhile after the aforementioned awhile back, I was racing browsers against someone at work on Verizon and noticed that Opera Mini was behaving slower than IE was. I wanted to know why...given Opera PPC beat the pants off of IE in the round 2 of the race.

I couldn't sleep last night, so I was looking into this. I loaded up my old Jbed midlet container because I wondered if the connectivity issues I had before with it were related to the proxy issue (they were) and it connected fine to Gmail...so I reinstalled Opera Mini into the Jbed midlet store and ran it...not only did Opera Mini start up faster, but it loaded pages *much* faster also. GMail was faster too.

So, I uninstalled the Intent Midlet manager I picked up over on xda-developers and used the Jbed installed in the ROM. I'd recommend that anyone who took my advice before and installed the Intent Midlet viewer remove it, fix the proxy settings, and use the Jbed one.