anyone got an Android phone?

[disabled]

Anyone got a high end Android phone here? I just bought one for my brother and am playing around with the SDK a bit.

This is a little earth editor like. You can touch-draw pixels on the screen and they are drawn to the center. There is no collision detection yet, so they just fly through each other and never stop flying through the center.
I got a Samsung Galaxy S here and I can draw around 40000 particles at 30 fps. The physics can probably be accelerated a bit, but the drawing already eats up a lot of the cpu cycles. I'm not sure, if it can be accelerated any further. If any it gets slower.
The sad thing is, the phone is for my brother, he's not around till Tuesday or Wednesday so I got the phone till then and will be without an Android phone after that. So I won't be able to develop it further.
Anyone got a phone and want the apk to test it out? Its not fun and not finished, its more like a benchmark of what could be done. And it won't be up on the market, because I don't have a phone and thus don't see a need to register with the market...

[disabled]

Just a quick update: I implemented proper physics, that is you can add black and white holes like in EE and the particles actually move like they should. Still no collision detection though.
With 40k particles, the speed went down to 12.6 fps (1), so I looked for ways to improve it and found the native development kit. Converting the physics into C gave a nice boost to ~28 fps with 40k particles! I never expected that, but perhaps the compiler also uses the SIMD extensions of the processor.
Even faster would be to use the GPU to calculate the physics. They are embarrassingly parallizable, so perfectly suited for GPUs. But using C was the first step to accomplish.

Sadly my brother returned from his journey this evening and will get the phone soon. So this project was fun as long as it lasted, even if nobody cared.
I hope to continue, when I get an android phone on my own. I plan to do it since some time now, don't expect it before the end of the year.
Still, if anyone wants the (now very unstable but feature rich) apk, just leave a note.

*edit* (1) I initially had a value of 4.5 fps there, but I forgot to turn the debug mode off. That doesn't affect native performance though, because C code creates no debug statistics...

[nmagain]

Don't double post

[disabled]

Thanks for your contribution...

Posts without Active Contribution
Risk: 5% warning

[nmagain]

Double Posting
Risk: 5%

[disabled]

So? Go tell a moderator I double posted and ask for my 5%, I'll ask for your 10% for posting twice without a contribution later...
I don't care about 5% warning if I think a double post is usefull.

[clockwork]

I agree, I double post when I find it useful. Even triple. Though it's usually not that much of an emergency. Not to mention a double post will catch a staff's eye. So they can hopefully read it. Though I rarely do this about I always contribute all of my opinion in a single post so I can save myself from coming later.

[~Memzak~]

Meh... It's mostly a pain for staff to come and merge posts....

...but I did it once or twice, to bump a thread I wanted to be used... (as it had fallen off the page)

[zaixionito]

Nmagain, stop being a person who is obsessed with rules. I, for one, found Disabled's post very useful. It make me think better of him, and worse of you.

On topic:
Sadly, I don't even have a smart phone. If I did, it would be android though, I wish I could use the SDK...

[Qwerty]

Yay for Zaix being on-topic. Let's all follow his example and stop bickering about who broke the rules.

[disabled]

Not that anyone seems particularly interested in this one, but I had my hands on a HTC magic this weekend and tested it. Its one of the first android phones ever created and fairly slow compared to todays beasts.
Still it managed to do 40k particles at 10fps on its smaller screen using the native mode. While physics and drawing needs about an equal amount of time on the Galaxy S, physics will be the limiting factor on the magix, and I don't have high hopes of ever speeding it up significantly. Well on new phones I could recode it in assembler, but slower phones don't have SIMD extensions, so there is not much to be gained there...