UPDATE (04/25/2008):
1. XDA-Developers forum member
m3uch4 has published a
decent tutorial on creating shortcuts for Jbed – highly recommended.
2.
badbob001, who has just released a new, 0.09b version of his
StartOperaMini by adding the exclude list feature (and a LOT of other goodies – make sur eyou check out
the dedicated XDA-Devs thread!),
has found out a pretty easy-to-use fix for the above-mentioned Jbed 3.1 resume bug: if you have Direct Address Input disabled (it’s enabled by default), press #1 to open the Enter Address window. Then cancel out and the Opera Mini screen should be responsive again. (BTW, this might work with other dialogs requiring manual input – I don’t know, haven’t tested the latter.) Incidentally,
he has also found out the problem is surely a Jbed-related issue because the Gmail MIDlet is also affected by it. Let me cite him: “
One thing you may want to investigate is Jbed's background running option. If I run jbed, turn on background running, then launch opera mini, the problem seems to not occur with my limited testing. Since I prefer to directly launch opera mini, it would also be nice to have a way to enable background running by default.
If enabling background running really fixes the issue, then I guess it's a bug with jbed 3.1 restoring itself from its own suspend mode.”