Nokia 6630 Specific questions related to jsr184 , m3g , etc

[www.rzr.online.fr]

Hi ...
I have some questions which are specific to Nokia 6630 :

Nokia 6630 MIDP/2.0 CLDC/1.1 (176x208x16) http://www.forum.nokia.com/devices/6630


* How to tune emulators to have the same behaviour that the original device ?

* Does not display version AB.CD.EF but only AB.CD

* Do you have any info on nokia imprementation of jsr184 ?

* At the same time i can test opensource midlets on it, just page me

* Anyone experienced weird behaviour between WTK, Nokia-RI and Nokia6630 (like Sprite3D and Alpha channel)

* If you notice some bugs in 6630 implementation of M3G , Please tell about them in this thread

* Jar limitation :

http://www.forum.nokia.com/devices/6630

Memory:
Heap size: Memory allocated dynamically
Shared Memory for Storage: 10 MB
Max JAR Size: Memory allocated dynamically

I will make tests to figure this out

It seems that nokia 6630 has a 1Mbyte (1048576 bytes) Jar limitation
i tested hardly a 1041704 archive

* Known bugs are about :
- midp2/ GameCanvas : http://discussion.forum.nokia.com/fo...653#post134653
- m3g / Sprite3D
- Midi playback


Mine is
Firmware V 2.39.124 17-10-04 RM-1 (cheat code is : *#0000# )
_________________
http://rzr.online.fr/java.htm -- Diet3D OpenSource 3D Mobile

[Pinga123]

One more, cannot play midi sound in Java

[grahamhughes]

Pinga123: Can you tell me what firmware version you have?

I'm having problems with MIDI on 3.45.110, though they seem fine on 2.39.151.

Cheers,
Graham.

[www.rzr.online.fr]

Originally posted by www.rzr.online.fr
* Jar limitation :

http://www.forum.nokia.com/devices/6630

It seems that nokia 6630 has a 1Mbyte (1048576 bytes) Jar limitation
i tested hardly a 1041704 archive

I installed a midlet (size may be nearest to the jar's size limit) and I can not start it,

Even WORSE I can not upgrade it , or remove it because it is not listed in the application manager, while icons appears on "desktop"...

I suppose my device need a reset, please help me on how to.

BTW, how to reach some tech support ...


Nokia6630 - Firmware V 2.39.124 17-10-04 RM-1 (cheat code is : *#0000# )
_________________
http://rzr.online.fr/java.htm -- Diet3D OpenSource 3D Mobile [/B]

[henqvist]

Bug list:

3D:
- Sprite3D doesn't work.
- Values given to "depth offset" does not affect rendering in the way the are described in JSR-184 specification.
- Bone rotation is not compatible with other JSR-184 implementations or tools (whether this is a bug in nokia phones or other phones is a matter of taste).

General:
- Floating point exponent overflow
(i.e 0.000000001f * 0.00000001f = -12341234123.0f)

+ a few others that we are still working on to get answers from nokia

[taarnio]

Here's a list of known M3G related bugs in Nokia 6630. These have all been fixed by now, but they are present in at least all 2.x firmware versions:

1. Sprite3D works fine in render(World), but not in render(Node, Transform). Workaround: Put all sprites into a World.

2. Depth offset does not work properly. This bug originates from the OpenGL ES engine, so it also affects Symbian applications.

3. The background image may flicker on and off when scrolled. A wrapping background image is erroneusly not drawn if the crop rectangle is outside of the viewport. Workaround: Use a modulo operation to always put the crop rectangle within the viewport.

4. Camera and light transformations in Graphics3D are left in an incorrect state after a render(World). Workaround: Set the camera and lights manually.

5. Transformable.pre/postRotate does not work. This happens after setting an initial orientation with Transformable.setOrientation(0, 0, 0, 0), which is legal according to the spec but results in invalid values internally. Workaround: Any non-zero axis to setOrientation(0, ...) will work.

6. The Loader fails to load compressed M3G files produced with HI's exporter. This is because of a bug in handling of empty sections. Workaround: do not tick the "Compress" checkbox in the M3G Converter tool.

I'd also like to address the bone rotation issue raised by "henqvist" to clear up any confusion. The Nokia implementation is very strictly according to the specification in orientation animation. We expect all other implementations and M3G tools to also become conformant in the near future, now that the issue has been identified and resolved in the JSR-184 Maintenance Release. (See issue #38 in the JSR-184 Change Log, http://www.jcp.org/en/jsr/detail?id=184).

Best regards,
Tomi Aarnio
JSR-184 Maintenance Lead
Nokia Research Center

[omkar123]

Can u pls. explain the problems u faced with Sprite3D?