[Android Software Development] s_firestone:
AerialX, I just want to say thank you for the work you have done to date. This is definitely pushing the boundaries and I could see this being one of the most popular apps on the market compared to the typical live wallpapers Mr. Geiss will probably be proud to see his baby born onto yet another platform. Kudos and I'll definitely be donating.

here is my progress so far on the A500. I also have an HTC HD2, and a MyTouch 4g. I load up and test it on these as well.

NOTES:

NEON works on the A500 :D

Initially I could not get the Neon version to work. It would simply display a black screen. I loaded the non-neon version and that of course worked. Today I thought, what if I was missing something initially...So I re-ran the Neon APK and it worked. It is definitely rendering smoother math. We might be pushing 60fps. More vivid too... Yay!! So far, once it loads it seems stable for at least two hours while doing other things.

Bonus, it switches seamlessly between landscape and portrait. It even works at full speed on the lockscreen (starting back at the 1st visualization of course).

Occasionally (if I make too many changes) it will lose the sound source which I can only restart Android to fix. Manually stopping services has no effect on this.

I have ADB loaded now I just need to get the other half working on the PC and I'll be able to supply you with any info you need.

Visualizations:

Ok, what thought was something amiss in the code when I would perform simple actions on the A500, was actually AnDrop starting back over at the first visualization file, Aderrasi_-_Agitator.milk. I removed that particular visualization from mine due to the overly chaotic nature. That one is pushing so many changes to the screen that you see the raster continually (to the point of being Agitating, hence the name I guess :D ).

Androp restarting at the 1st visualization is able to be reproduced and predictable. Rotating the screen, starting any full-screen app with start Androp over at visualization #1 (alphabetically I think).

I went through with Winamp on my main machine and hand selected some visualizations, checking each. I'm up to 27 working .milk files now. I figured it would be a 1.x vs 2.x issue, but just as many of the 2.x .milk files work.

I'm going make an index of what works and what doesn't. Maybe it will tell off on what is missing. Its been a while since I dug in and

Visualizations that don't work will simply show a white screen (regardless of whether they are written for 1.x or 2.x). I suspect due to use of advanced functionality in Milkdrop 2.x

Only on non-Neon version: I can stop and restart Androp about 5 to 10 times before it reboots Android.

If I manually kill "Music Visualization Wallpapers" and "Live Wallpaper Picker", it does seem to forestall restarting longer...

Visualization notes:

Visualizations do not look the same between PC and Androp. This ranges from movement (certain aspects of the visualization not moving, rotating, etc.) to colors, to screen redraw (decay, fade, etc.). Now to figure out whether these differences are:

Differences in the versions of the Milkdrop/Projectm code.

The inherent limitations of the hardware platform on which they are running, or lack of an accelerated driver, OpenGL vs DirectX.

Differences in how the .milk files themselves need to be tweaked for a

different display. (Zoom, Gamma, etc.)