Worked right away on my redmi note 3 (64-bit arm) and mi note2 (x86_64 tablet). It's software rendered!

Two control suggestions:
- if you hold the "move forward" touch area and tap the "jump" button, you stop moving forward.
- currently if you press the "move forward" onscreen button and move your finger to the "move back" area, without lifting it up, it keeps walking forward 

is it capable to handle sepulcher? 

Excited to test this out 

I had to touch hold the links and open in a new tab or else it is just black. FYI. 

And Baker becomes an instant Quake legend. 

@ericw - I'll check that out. Never noticed during testing. This has been tested to death on the 2 phones available. (With tons and tons and tons of coop played). It has also been refined to death, but I can think of some more refinements.

@pulsar - I haven't had time to add Sepulcher support yet. But it is on my list. Now that I have this big project out (it's a relief, I hate have major modifications on my hard drive) --- I can focus on things like that.

@dumptruck_ds - I think you'll love it. ;-)
@QMaster - Thanks! My worst fear is that I have had only 2 devices available for testing and Android is a diverse ecosystem. 

I had to touch hold the links and open in a new tab or else it is just black. FYI.

Could you explain this in detail like I'm not sure what you mean? My mind is sapped from this project. 

I'm slightly surprised it worked on your x86_64 tablet. But also happy. I think I only compiled for ARM, so the x86_64 must translate somehow.

(I also did some hasty Googling and concluded x86/x86_64 Android was a rather rare beast -- but apparently I am wrong?). 

currently if you press the "move forward" onscreen button and move your finger to the "move back" area, without lifting it up, it keeps walking forward

That is proper operation.

When you touch the surface, the "down" checks what it hit. The button is the "owner". And that button remains down until that finger is lifted.

Windows does this as well.

If I went full overboard Minecraft style, I would make the virtual arrow keys a singular directional zone. I considered doing that, but want to hold off for now. 

Rendering would be incredible on the Retina screen, running AD and all the modern maps.

Is there a chance that may happen? 

I did a lot of the QuakeDroid testing playing coop with -- an iPad!!!!

I am not going to rule out putting some sort of iPhone Quake on the Apple App Store.

I want to gauge the interest with this first.

There is, in fact, an iPhone build in the source that has not been tested on a Retina display (I used an iPad 2 for testing, I have some sort of iPad Air 3 (?) sitting 12 feet away (3 meters for non-USAians, haha) but I'd have to upgrade my XCode and deal with new fussiness.

My main concern is I care more about mappers and putting maps on an iPad/iPhone/iPod Touch is a real PITA.

The iPhone + friends offers a superior experience, has the better development environment, but from a mapper perspective the file system is locked down in a rather cruel way. Android, while perhaps protecting the users less, enables them to have enough convenience.

Anyway, I'll meditate on this in the coming weeks.

I want Quake everywhere, because mapping is an enlightening and enjoyable experience and Quake makes it happen. 

On my S7 Edge, using Google Chrome mobile app. Touching links above goes to an all black webpage. Website says it's loaded and address at the top is correct but nothing shows on the page.

Touch and hold, popup with link options comes up, touch "open link in a new tab" and webpage loads fine i the new tab. Not sure why the links are being wierd. Oh well.

Now to see about finishing playing DM4Jam on my phone. Yay! 

The touch keyboard for entering your name in setup is AMAZING! 

I'll see if I can fix the links, after you post I tried Chrome on mobile it acted weird.

I thought after years and years of Acid-2 and Acid-3 tests and such, that the mobile Chrome would behave like the desktop Chrome, but stupidly it is not true. 

I should have the web site rendering for mobile Chrome resolved, let me know if it works properly for you. 

works fine on my huawei p10 plus (64bit)

good job! 

Cool! Android has many different models + different processors. 

QuakeDroid has been updated resolving the jump + forward bug ericw reported.

(The single changed source file is available in builds folder where the source code can be downloaded.) 

Works with no issues so far. I'm away from my pc for the weekend but will get pak1 when I go home again. 

Works with no issues so far. I'm away from my pc for the weekend but will get pak1 when I go home again. 

Wow, software rendering Quake on a phone! I suggest an option to hide the Android navigation bar, to use all the screen. 

@mgtroya

I suggest an option to hide the Android navigation bar, to use all the screen.

It is supposed to be fullscreen. It is on both the devices I have tested on.

I'll check some Android dev forums and see if I can find any info on that kind of issue in apps. 

Thanks for feedback. 

Is the Android navigation bar on your device a screen rendering of the (<--) (Home) (==) buttons that on other phones are physical buttons?

Like your device doesn't have physical buttons but they are instead rendered on the screen? 

This runs smooth as butter on my mediocre Samsung from 2015. I'll see how it fares on a Huawei once it gets finally shipped (fucking TNT).

I was going to say "tapping to shoot isn't too responsive" but then I remembered it's double tap, and it worked fine. A single tap would be more intuitive for the user though, I think?

Quitting doesn't actually shut down the app - it resets the game and minimizes the window.

All in all, a great Easter gift!