Ok looking for a bit of Android testing.

[Chontler]

Simply: You've added the ability to use the back button to pause. If I ever use that method, I can no longer control the ship in expert mode again unless I exit.

[p-saurus]

I can't replicate that behavior (expert mode not working after pausing with back button) on either my Nexus 7 or my Galaxy S3. The Nexus is bone stock and the Galaxy is rooted with the stock ROM. The new build seems to function properly on both devices for me.

[Chontler]

After some more fiddling:
I've reinstated the stock buttons. The back works fine. The issue actually is that settings/menu button - the one with the 3 dots. I have my nexus7 set up so that a 3 finger tap is the settings/menu button. if I three finger tap it locks the expert mode.

So, I disable all my hacks and click the 3 dot menu/settings button (whatever it is) a couple of times and it locks the expert mode control for a few seconds. I was wrong in assuming it was the back button, but that's because I use a three finger swipe to bring the back button on screen!

...but yeah, after a couple of presses, that 3 dot button is glitching the expert mode control.

[gilesgoat]

Erm .. what is .. 'the 3 dots button' supposed to do / for / called ???

[Chontler]

I don't know. Some kind of app menu thing.
The bottom right on this:


online photo storage

[p-saurus]

Okay, I also lost controls on the Nexus after pressing that button. It doesn't appear on the Galaxy.

[Googer]

I don't have such a button on my Note II either but also initially had issues with expert controls not wanting to work. A bit more playing around (note entire sure what I did, still have to test some more to see) and it now it works fine and (not surprisingly given the Note II's a beast spec-wise) super-smooth, with my problem now just being that I'm awful (best result so far was reaching wave 9 or so).

I haven't gotten a chance to test on an old Dell Streak 7 (which is Tegra 2-based) I have laying around yet but I hope to shortly. Another thing I haven't gotten a chance to test yet (I don't know if it's implemented yet but it'd be cool if so) is controller / external input support (and even reconfigurable key support that I could map to a controller via an IME would suffice personally for this ).

[sdetoni]

On my a10 allwinner tablet clone, I have no problems with keys(home,back,menu , vol up,voldown). Tried pushing them all, paused/unpaused... expert/novice mode, all worked as it should....

Been playing off/on today, up to level 34 ... no crashes or glitches... it does heat up the cpu/gpu chip quite substancially though

while not as fluid as my wife's ipad 3, still very playable on a budget tab.

[gilesgoat]

WHY ??? WHY ??? WHY ??

http://www.yakyak.org/viewtopic.php?f=2 ... 9#p1563439

[toxibunny]

Yikes...

[gilesgoat]

And the reason I used OpenSL instead of "SoundPool" is because I read stories around of people saying that using SoundPool was creating 'strange issues' with lot of other things.

OpenSL and 'buffers' was looking like the simplest straightforward way to just play some silly samples.

Note I use only ONE player object and I do mixing "by hand" so "could not be simpler than that".

[gravy]

Does OpenAL soft still look so terrible?

[gilesgoat]

OpenAL has even more troubles, anyway I think I fixed that thing.

Java .. GHZ processors ... megabytes of ram ... oses .. "and one becomes stupid to play a buffer of samples" ..

Let's check again what 1K of ram, 8Kb of ROM and 20 Mhz can do ...



"They went to the moon with less than a Z80 .. " .. etc.

[KlaxonCow]

So far not been able to try from PC because the PC seems not to want to recognize something of my Andorid tablet and cannot find an opportune driver for it

You're using the Versus Touchpad 7 tablet, yes? (I gather from reading your other post about your other problems with file transfers.)

Yes, the problem with that cheap-and-cheerful tablet is that it's actually made by some unknown / unnamed Chinese / Taiwanese manufacturer somewhere - it's just rebranded and sold on by people like "Versus" and others - so it's a tremendous pain finding the USB Drivers needed to make it work on Windows.

Google are utterly useless in your quest, because they just say "find the manufacturer's USB drivers" / "go to the manufacturer". But goodness knows who they are with these rebranded tablets (and they'd probably turn out to be of zero use anyway, even if you knew).

But, luckily, after an age of searching, I finally discovered this invaluable little page:

http://choruscode.blogspot.co.uk/2012/0 ... oblem.html

Yes, in the end, it's just some stupid Windows thing. The truth is, Google's generic USB driver is perfectly good for your tablet and would work just fine. But Windows won't install the drivers for you because the device IDs don't match up (and only Google device IDs are listed in their install script, I suppose understandably enough).

So, the trick in fooling Windows into actually installing and using the USB driver is to use "Device Manager" to find out the tablet's device ID directly and then editing the relevant file to add your device ID to it. Windows then sees the matching device IDs it expects and will then actually install and use the USB driver.

You would not believe how long the search was to discover this, Giles. But, anyway, you're in grand luck because, as I already did it, now you don't have to. Just follow the instructions on that page.

Once sorted, the ADB thingy should then work properly in Windows and then Eclipse will be able to see and directly communicate with your tablet.

[gilesgoat]

In case it's not "clear" yet it's since yesterday I restarted on this Android thing, I am trying my best to finish asap to implement 'the few last missing things', took me 1 day and 1/2 to wrap my head around 'layouts','listviews','gravity','lists adapters','HashMap' and stuff like that.

Thanks Goat I said I did not want to mess up "too much" with Android and Java ...

I hope I never to touch ( too much ) all this shit again.

I am also trying to make it 'as simple as possible' ..

Anyway back to you soon as soon as I'll have something new.