Unfortunately, my Kindle is from 2011 and gave the error: There is a problem parsing the package. Most likely the OS is way too old.

My wife has a much newer model. I will steal it and report back if I have any luck. 

https://www.dropbox.com/s/zjrpdetqn89drud/qconsole.log?dl=0

Enjoy 

This time I installed virto's build and got the same error

https://www.dropbox.com/sh/9aeb5venswilb5s/AADJilNeYdXCv10HXDbojgOMa?dl=0 

Looking at the log, it appears the engine thinks everything loaded ok and it proceeds to start playing the demo.

Does it make sound in the background and just show a white screen while doing it?

Either way, I'll try to eventually get my hands on a 2012 Kindle Fire from a friend I know, just to satisfy my curiosity and see if I can get it to work. 

@Baker fantastic job, but would it be possible in the next release to rise The step left / right icons at the same level of the fwd icon. In my opinion this would lead to an increased playability. What do you think? 

I'm about 80% I know what's up with your Kindle and can fix it if it is playing the sound. I saw something in the log you posted that made me think.

@icaro - Thanks! I tried to make it very nice. Yeah, the controls need some tuning and it'll come. I've got a little bit of a queue at the moment. 

ICARO is right about the position of the move icons -- at least util a better control option comes along.

But while we're still using the current setup, I'll also mention, in addition to my previous preference for:

Jump
Attack
Change

that the buttons along the right could be positioned like:

. . . . . . Jump
Change Attack


with the buttons grouped around the bottom right corner. That still puts all buttons close to the Attack button for easy access. 

 

Away from Kindle

Have fun with other issues meanwhile 

 

When touching the hud bar at the bottom of the screen, still let the camera move with continuously held thumb swipe.

Have you been able to reproduce the camera reversing effect? 

@qmaster - I know what you mean about the "camera reversing", I haven't developed a plan to properly "clip the drag look" if someone attempts to look beyond where Quake will let them. And other one will be a yes. 

Good News! It's only a drawing bug! When I turned up the volume, I heard the familiar sounds of Romero blowing up the Zombies... 

Great! That's why I mentioned if it was playing sound.

The reason it is rendering white is your Kindle doesn't have an OpenGL extension allowing non-power of 2 textures.

When I had checked the source, I found I had commented out a couple of lines of code I wrote in the video section upsizing to a power of a 2 size. 

I'm getting the error: 'Not enough memory free; check disk space' but I have almost 2GB of free device space on the phone. It's a Galaxy Note 3.

Anyone have any ideas? I'm mot very good at reading code but that error message comes from here: https://github.com/ericwa/Quakespasm/blob/master/quakespasm/Quake/main_sdl.c

Could this be related to RAM instead? The phone only has 1GB of memory. 

It's RAM. It is also asking for more RAM than it needs. I'll reduce the RAM it asks for in the next release which I am hoping for Sunday.

If you don't want to wait, you could alter the command line how to set command line just putting "-heapsize 256000" without the quotes in the quake_command_line.txt or if that still didn't work, putting "-heapsize 192000" 

I've tested on some retired phones. What info would be most helpful? Model numbers? Frame rates? Happy to take some time and collate data for you. They are mostly older Motorola phones but all shapes and sizes.

I horde all our older phones for some reason. 

Ah! Thanks dude! Had a feeling a simple command line would fix it but didn't know how to do access it. Heapsize 256000 worked like a charm.

Btw, are the controls setup set in stone? Reason why I ask is coz I played almost the entire Quake II campaign on my Android phone ( https://www.apkmonk.com/app/com.n0n3m4.QII4A/ ) and those controls felt much better and extremely smooth compared to the ones you chose. I'm mostly referring to the movement + mouselook. Also, they were customizeable. Maybe something to look into!

Great port btw. Thanks for making it! 

I'll work on the controls until everyone here is satisfied. I'll check out the QII4A link you provided.

I knew going into this that the controls would be the #1 that needed refinement. The touch-driven menu that allows things like touch slider dragging was the hardest part.

Controls will take a few revisions to satisfy everyone.

@dumptruck - I'm satisfied with the feedback we have on existing devices, we have quite a range of feedback on devices. 

But it stopped working when I updated from Android 4 to 5. likely it counts for Q2A and Q3A too. All made by the same guy. 

I see the weird lines in the water surface only when I am actually inside the water.

And using a bluetooth keyboard, lookspring and "centerview" (bound to a key) just stop working sometimes, then they start working again, then they stop working again.... I can't really tell under what circumstances they stop working or start working again. 

As you are a power user, you don't have +mlook/-mlook anywhere in your config or binds do you?

Without checking, I do not believe "centerview" works with mouselooking on.

Since mouselooking doesn't apply to QuakeDroid, I haven't considered the possible interaction between the controls and +mlook/-mlook.

If this doesn't have anything to do your setup, let me know ... I'm thinking aloud a bit.
----
On the other hand, lookspring was extensively tested. Should work anytime you start moving. Again, interaction with +mlook/-mlook has not been considered -- if that applies. 

You might try a bind like "-mlook; force_centerview; +mlook" and see what happens.

I give centerview some thought. On a desktop, there is no way to improve centerview but on mobile there actually is because on mobile you know if a look operation is in progress because it requires a specific action to occur (which is a drag has started obviously). 

I haven't touched mlook. And I can't replicate the problem again, after Quakedroid crashed and I restarted it. If it happens again, I'll try the force_centerview 

2-3 days out