My OperaYou need to be logged in to post in the forums. If you do not have an account, please sign up first.
The quick workaround is to turn on "Fullscreen edit" under advanced settings. Then Opera Mini will fall back on the phone's native input method.
The long-term solution is to 'teach' Opera Mini your phone's keycodes. To do this you need to file a bug with Opera's BTS at http://mini.bugs.opera.com/ with the following information:
* The phone's J2ME platform string
* Keycodes and labels for each affected key
To obtain this information, you can install the MKey application from http://m.opera.com/mkey
The platform string will be displayed when you first start the application. The keycodes/labels will be displayed after you press each key. With this information our J2ME expert can determine whether it is feasible to create a custom keymap for this phone or not.
After you raise the bug, please post the SKIRNE number here.
Originally posted by Montenell:
after trying to use the fullscreen edit, not only does it not work but i also have to exit the program completely. it seems to freeze up during fullscreen edit
when running the mkey i noticed that it shows this phone as being a touchscreen which it is not
my skirne is 797984
Could you please double-check your Skirne number? There is no such bug as "SKIRNE-797984" in our BTS.
Originally posted by Slycarter:
I have opened a bug report.
My SKIRNE is 79932
Unfortunately, since your JVM returns only 'j2me' as the platform string, there is no sure way to apply a different keymap on runtime. There is nothing we can do about this on Opera's side.
Have you tried installing a different JVM on your device?
Originally posted by seanturvey:
I have opened a bug report SKIRNE-80649
It is unclear from your bug report exactly what the problem is. You must let us know the specific keys that do not have the intended effect, and the keycodes that they return in the MKey application.
Originally posted by dmarks:
Originally posted by seanturvey:
I have opened a bug report SKIRNE-80649
It is unclear from your bug report exactly what the problem is. You must let us know the specific keys that do not have the intended effect, and the keycodes that they return in the MKey application.
My phone is a LG TE365, which is a slider and a semi touch screen. Unfortunately, because the number keys on the physical keyboard are only accessed by hitting the FN key first, I can not hit "0" to quit the test. Also as I said, it is a semi touch screen, this means the touch numbers are only available when dialling a number.
If you can give me the URL to the bug report, I can give them what I have for a keymap esp. Fn (127), Sym (129) and Shift (130) or if you would pass this on, it would help.
Originally posted by seanturvey:
Originally posted by dmarks:
Originally posted by seanturvey:
I have opened a bug report SKIRNE-80649
It is unclear from your bug report exactly what the problem is. You must let us know the specific keys that do not have the intended effect, and the keycodes that they return in the MKey application.
My phone is a LG TE365, which is a slider and a semi touch screen. Unfortunately, because the number keys on the physical keyboard are only accessed by hitting the FN key first, I can not hit "0" to quit the test. Also as I said, it is a semi touch screen, this means the touch numbers are only available when dialling a number.
If you can give me the URL to the bug report, I can give them what I have for a keymap esp. Fn (127), Sym (129) and Shift (130) or if you would pass this on, it would help.
You may add comments to the bug report by replying to the email sent out to your email address when you raised the bug.
In any case, I can see directly where the problem lies from the information above. These modifier keys must not return a unique keycode. Opera Mini expects modifier keys to directly modify the alphanumerical keys on the JVM level. There is unfortunately nothing I can do about this and can only suggest that you use Fullscreen Edit instead.
I posted a very long detailed map of all the keys... Thanks
Originally posted by johnxtampa:
Skirne is 84894. Only 3 keys worked on my phone, spacebar, comma, and period. All keys work on Bolt Browser.
I posted a very long detailed map of all the keys... Thanks
Thank you very much for the detailed data. I've raised the issue to the team so it will be looked at at some point in the future. However, please understand that it might not be possible to cleanly do anything about it on our side without causing unwanted behavior on other devices.