Closed GoogleCodeExporter closed 9 years ago
There are known problems with some Motorola devices, where the client worked on
0.9.1
but fails on 0.9.2 (see issue 46), though the error is different. In issue 46
the
client could at least be started. Anyway, I would suggest you have a try with
the
client 0.9.1 which is still available in the download section if you _search
all_
downloads.
You could also have a try with ClientCustomization - if you are lucky you can
fix the
problem with one of the documented client tunings.
Often phones are not very verbose on errors, as in your case, that's why I
cannot
provide a more specific answer, sorry.
MicroEmu compliation should provide similar working apps as when using WTK. So
far I
don't know of any case where the WTK version works but the MicroEmu fails.
Original comment by obensonne@googlemail.com
on 14 Feb 2010 at 8:50
0.9.1 doesn't work...
I wonder if I could write an app that would try to launch remuco and would
print the
errors on the screen.
I'll try to customize the client while waiting for an answer
Thanks a lot.
Original comment by GNUtoo@no-log.org
on 15 Feb 2010 at 11:48
According to http://www.dpsoftware.org/result.php?marca=motorola&modello=v3 the
RAZR-V3 has no Bluetooth support within Java apps and with reference to
http://www.dpsoftware.org/result.php?marca=motorola&modello=v3&test=net the
v3's Java
support is MIDP2.0 and CLDC 1.0 but CLDC 1.1 is required by Remuco. The latter
one is
the reason why the client app does not start on your phone. But even if it
would, the
missing Bluetooth support would make it quite useless.
Sorry for the bad news.
Original comment by obensonne@googlemail.com
on 15 Feb 2010 at 12:17
Original comment by obensonne@googlemail.com
on 15 Feb 2010 at 12:20
Setting bluetooth permission doesn't change the fact that it crashes...
Original comment by GNUtoo@no-log.org
on 15 Feb 2010 at 12:50
If you have experience with MIDlet development, you could try to hack a CLDC 1.0
compliant version of the client. In the file build.properties replace set the
cldc.jar property to point to a CLDC 1.0 jar
(http://code.google.com/p/remuco/source/browse/client/jme/build.properties.examp
le#71).
Then build the client, look for compilation errors and try to fix them (don't
know
hoe much work this is nor if it is possible to replace all CLDC 1.1 references
by
CLDC 1.0 variants).
Original comment by obensonne@googlemail.com
on 15 Feb 2010 at 12:52
I didn't saw the previous comment while posting.
So this phone is mostly useless.
Thanks a lot!
Original comment by GNUtoo@no-log.org
on 15 Feb 2010 at 12:53
Closing. Guess there's not much demand here. Reopen otherwise.
Original comment by obensonne@googlemail.com
on 7 Mar 2010 at 11:02
Original comment by obensonne@googlemail.com
on 8 Mar 2011 at 6:38
Original issue reported on code.google.com by
GNUtoo@no-log.org
on 14 Feb 2010 at 6:48