A night at the Opera

If you have your own website, as most people do, just make an  page with all your links on it and use the awesome Proseemo page and type your own website in 1 time! Bookmark that baby and your good to go! It would be nice if someone could get Opera 4+ to work.

Yes... Just read the thread.

Can someone please sticky some instructions on how to get the Opera Browser? Because it's hard to thread through 14 pgs of posts? I would be eternally grateful

I've taken a peek at the development data for Opera Mini 3.1.2 just for comparison with Opera 4.1. Version 3.1.2 has 2 different version a high memory and a low memory. Low memory 3.1.2 is for phones using MIDP 1.0 and conversely the high memory is for MIDP 2.0 capable phones.

As stated in various posts through out the site, LCDUI/MIDP 2.0/ Java ME is the culprit here. Opera Development staff have stated they won't make a special version of 4.1 because the issue is not Opera's coding. Qualcomm is the true culprit here as they're the ones that supplied the "hacked" version of MIDP 2.0 to Sprint. For what reason? Who knows! Maybe it was for exclusivity reasons. Sprint can't make money on 3rd party applications you download from sites like GetJar. This cuts into their continued profits... just a thought...

So the truth shall set you free.  This isn't just Sprints issue any longer. Sprint has to work with Samsung AND Qualcomm in order to fix their deliberate less than complete MIDP 2.0 implementation. The simple fact Sprint and Samsung would have allowed Qualcomm to sell them a Java ME environment that is not industry standard is beyond me... They had to have taken into consideration all the upset customers that would be missing out on "industry standard Java" applications. AND I believe the above information lends itself as to why Sprint has a developer contest going on.

Also, on-screen keyboard implementation is looking good. BAW and InstinctInsight have alluded to a fix sometime within the next couple of months. Of course no word on an exact date which keeps the tradition of Sprint's lackluster notification efforts. 

It's possible. 4.1 is leaps and bounds over the previous release. But if the number 1 issue affecting distribution is solely based on Java, then I think it's completely safe to say it'll work right 'out of the box'.

You're completely right. I've experienced the same exact behaviour as well.

What I'm referring to is when Sprint, Samsung, and Qualcomm all finally roll out the final missing link.

The reason 4.1 runs fine the first time is that the complete instruction set is not loaded. Essentially it is bypassing the normal instruction set because a successful installation should mean compatibility on the device. Of course that's assuming the device was compatible to begin with, which Opera has stated the instinct is not at this time. Once an attempt is made on the second running of the program it asks for a certain instruction, which by the programs logic should exist but since it's trying to call up an instruction set that doesn't exist then the natural behaviour of the program would be to 'hang' until the program is given the proper instruction. And I base this off my experience with failed programming I've done in the past. You're not going to get full functionality out of a program that never took into consideration that some phone developer was going to omit portions of the standard code. Clearly this is the case. All programs work the same. Absence of instruction leads to chaotic, or in Opera's case, stalled and errant behaviour.

I honestly don't see why Opera couldn't work once the Instinct receives full Java at a later OTA update. OM 4.1 obviously utilizes some technology that 3.1.2 does not. What that truly is, is a mystery to me. The real test will come when we get full Java. I'd be happy if I was right and I'd love to be proven wrong!

Thanks much, I only spend like 10 min a day on here, not a lot of time at work