android-discuss, Want to help us port our iPhone app to Android?

1. Trying to get rid of my last few Long calculations in my game and completely turn it into FP format. System.currentTimeMillis() giving me a headache.

Like the topic of the thread says. In my game I would like to turn all
the calculations into FP format. I can eliminate pretty much
everything else but I still need to do the the following calculation
in long format.

Code:
long t = this.lastUpdateTime - System.currentTimeMillis();


The value I get from this is the time passed since last frame, which
is like.. two digit millisecond value, which naturally is more than
good for FP stuff. After that calculation I turn the resulting value
into FP integer and use it with the rest of my calculations but I'd
like to get rid of that long calculation too. Any ideas how to go
around this to do it in FP format?

I mean, I'm pretty sure I cannot just go and do a normal conversion to
FP format in this style:
Code:
int fpT = t * (1<<16);

because there is always the change that it'll overflow and as the
numbers that System.currentTimeMillis() give out are BIG.

So any advice how to keep the same "accuracy" of the timer but get rid
of the long calculation and have it replaced with nice and fast FP
calculation. Any advices on how to trim down the
System.currentTimeMillis() or what ever to get around this are greatly
appreciated.

Cheers guys.

-- 

2. Get body movement (e.g. turn around)

I'm working on an app that needs body movements as inputs. So
basically I want to know if a person turns around completely (360).
If a the person does sthg happens inside the application. My problem
for now is: How to figure out if a person turned around?
I don't see an approach with gps as the person is not moving enough.
So I thought about the compass or acceleration sensor but I have no
clue how to manage that. I'd really appreciate some ideas / hints /
tipps!

Cheers

Moritz

-- 

3. SMS text garbled using native Messaging app when message spans two text messages?

4. Debugging on mobile 2

5. Droid/Milestone: GL_OES_framebuffer_object reported but not working

6. AES decryption is slow....

7. Mohon gabung ..