Mini 5 on Samsung Flight: A few questions/issues.

Mini 5 on Samsung Flight: A few questions/issues.

This browser is around 3 times faster at loading pages than the one that it came with so I'm extremely happy with it so far. Unfortunately, I'm having a few issues

I can't seem to get a signed version for my phone so I'm stuck with a java virtual keyboard at the bottom of the screen making the browser window pretty small. Also, my phone asks me if I want to continue because "there may be data charges" every time I load a web page.

My phone came with two browsers pre-installed. I've gone to m.opera.com/detect with both of them to submit some info. One of the browsers is netfront based and the other is some very old and AT&T customized version of Opera Mini. When downloading Mini 5, I go to m.opera.com and select other download options. Then I click on the link that allows you to select a signature. I've downloaded all 3 types with both of my pre-installed browsers and every time I still have the virtual keyboard and a notice about charges on every page I go to.

I've posted my browsers User Agent information in a different thread but here it is again.

SAMSUNG-SGH-A797/A797UCIIB SHP/VPP/R5
NetFront/3.5 SMM-MMS/1.2.0 profile/MIDP-2.1
configuration.CLDC-1.1

Hopefully this gets taken care of sometime soon. I'd like to be able to use Mini 5 to it's fullest ability without my phone harassing me about charges that won't occur or have the bottom 1/4th of my screen taken up by a useless virtual keyboard.


EDIT: I decided to give OM 4.2 a go. It didn't ask me about data charges but it still had the virtual keyboard at the bottom. I noticed scrolling on 4.2 is a lot snappier than 5 for me. Scrolling in OM 5 is more sluggish and it would occasionally scroll back to where I started when I lifted my finger off the screen.

Bump

Try again: with your native browser go to mini.opera.com
Select the signing option first, then d/l 4.2. This may not cure the virtual k/b issue. You might want to check out hofo on how to edit that out. Agreed, 4.2 is "snappier" than 5.0

Also, check this out! http://my.opera.com/community/forums/topic.dml?id=539841

Originally posted by H82typ:

Try again: with your native browser go to mini.opera.com
Select the signing option first, then d/l 4.2. This may not cure the virtual k/b issue. You might want to check out hofo on how to edit that out. Agreed, 4.2 is "snappier" than 5.0

I've tried downloading 4.2 and 5.0 with all 3 signature options with both of my native browsers. None of them get rid of that stupid java keyboard. I would just use 4.2 because it's faster and doesn't bug me about extra charges, but I really like the tabs and speed dial in 5.0.

Originally posted by H82typ:

Also, check this out! http://my.opera.com/community/forums/topic.dml?id=539841

I've been there already, and have gone to that detect page in both of my phones browsers.

I'm not sure you'll be able to get rid of the virtual k/b. That might require some work by Opera.

Originally posted by H82typ:

I'm not sure you'll be able to get rid of the virtual k/b. That might require some work by Opera.

Yeah unless you want to get your hands dirty hacking the jad file you'll have to wait until we get around to doing this on our side.

There are instructions here on the forums, though, if you search around. It should work on virtually any Samsung device with this problem.

Originally posted by dmarks:

Originally posted by H82typ:

I'm not sure you'll be able to get rid of the virtual k/b. That might require some work by Opera.

Yeah unless you want to get your hands dirty hacking the jad file you'll have to wait until we get around to doing this on our side.

There are instructions here on the forums, though, if you search around. It should work on virtually any Samsung device with this problem.

Happen to have a rough estimate on when it'll be fixed? If not, I'll try to fix it myself.

Also, I read somewhere that a socket connection is faster but when I switch to it, I can't go to any web pages. Could that have something to do with OM not being properly signed or is it being blocked by AT&T?

Originally posted by CJRhoades:

Originally posted by dmarks:

Originally posted by H82typ:

I'm not sure you'll be able to get rid of the virtual k/b. That might require some work by Opera.

Yeah unless you want to get your hands dirty hacking the jad file you'll have to wait until we get around to doing this on our side.

There are instructions here on the forums, though, if you search around. It should work on virtually any Samsung device with this problem.

Happen to have a rough estimate on when it'll be fixed? If not, I'll try to fix it myself.

Also, I read somewhere that a socket connection is faster but when I switch to it, I can't go to any web pages. Could that have something to do with OM not being properly signed or is it being blocked by AT&T?

Socket connection depends on your device or network operator.I couldnt use socket on nokia 5130,but could use it on N73,with the same operator.

AT&T doesn't allow socket.

Originally posted by H82typ:

AT&T doesn't allow socket.

That explains it.

Originally posted by H82typ:

AT&T doesn't allow socket.

Thanks. HTTP it is.

Originally posted by CJRhoades:

Originally posted by dmarks:

Originally posted by H82typ:

I'm not sure you'll be able to get rid of the virtual k/b. That might require some work by Opera.

Yeah unless you want to get your hands dirty hacking the jad file you'll have to wait until we get around to doing this on our side.

There are instructions here on the forums, though, if you search around. It should work on virtually any Samsung device with this problem.

Happen to have a rough estimate on when it'll be fixed? If not, I'll try to fix it myself.

I don't have an estimate for you, unfortunately. Needs to be prioritized internally first.