re: water alpha ... are you sure? Type r_novis 1 in the console.

The looking down beyond your feet -- you can't look down more than all the ways nor can you look up more than all the way. That kind of behavior is baked into Quake on client side, server and input side. I know what you mean though.

@dumptruck - I'll be getting around to controls. The double tap to jump for instance sounds right. 

I don't know that this would help, but I think what I will do is make it so any tap opens the menu during the start demos.

I'm not sure that this will help with what you described.

I'll be doing another update in a few days. 

I've seen something similar mentioned in the SDL bug tracker/forums, = not sure if it's relevant:
https://bugzilla.libsdl.org/show_bug.cgi?id=2291
https://discourse.libsdl.org/t/android-device-displays-everything-in-purple-tones/21237 

Wierd, wateralpha is working now.

Looking up/down: the issue occurs before the pitch ever reaches full 90/-90. It is a matter of swipe right/left during up/down inverting once the pitch changes around 80 or so during the same swipe. Inverting = swipe left to look left actually stops turning left and starts turning right within the same continued touch if you look far enough up or down within that same continued touch.

Bug report: if a console command fails, e.g. map not found, the full screen console no longer registers the touch and does not bring up the touch keyboard. You have to start a new game before the console registers touch again. 

@ericw - Thanks for the link. According to that, it seems to imply that specifying the color format RGBA 565 might solve virto's tint problem.

SDL_GL_SetAttribute(SDL_GL_RED_SIZE, 5);
SDL_GL_SetAttribute(SDL_GL_GREEN_SIZE, 6);
SDL_GL_SetAttribute(SDL_GL_BLUE_SIZE, 5);

@qmaster - Another great catch -- yeah, I'll check to make sure console forced up allows access to the on-screen keyboard in the next version. Quake thinks it is in the game, but it isn't. 

QuakeDroid Virto Blue Screen Fix Attempt

If it works, ericw is your hero!

I attempted to locate matches to the symptoms of your problem but never would have found that link. 

Just tried it- works perfectly now! Great work! 

Great! Glad to hear it! We're batting 1000% again.

My greatest fear on release was the diversity of the Android platform from models to Android versions to processors.

/Mega-thanks to ericw! It could have been weeks before I came across that kind of information! 

I suppose your support implementation differs than Quakespasms, because I still can't play aristical's map in dm4jam because it is greater than 80000 verts. I haven't actually tested AD itself yet though. 

I didn't go full dynamic. I want to see if a minimal skinny implementation worked first. I'll go full dynamic next version so there is effectively no cap. 

Neither Mark V nor QuakeDroid can load Artisitical's map. We even put a "this map requires Quakespasm" warning in the dm4jam start menu before the teleporter to this level. 

I just wanted to test it after Baker added sepulchre support to QuakeDroid, something MarkV doesn't have yet either.

I'm trying to get my Gunter badge for the month ;) 

Just downloaded the new version this morning and reinstalled. It did update as the console now has an underscore.
I am still getting the lines on transparent water mentioned in posts #60 and #85.

Samsung J5 Prime still running Android 6.01 

On my phone, the Huawei P9 lite Quakedroid works perfectly fine.
I wondered if my Kindle Fire HD tablet from 2012 could handle Quake, and the shareware downloaded perfectly fine, then it just got stuck on a white screen. Don't really bother about, only maybe. I bet you can find issues more important, I bet it will lag the hell out of the Kindle (1.2 Ghz Dual-Core, 1GB of total RAM) 

I'm glad it works well on your phone!

should run on any Android phone made in the last 5-6 years

For the 2012 Kindle, it might not have enough RAM or might be out of storage space. It could also be that the version of Android is too old. Also it is my understanding that Amazon rolled their own (outdated) Android especially on older Kindle Fire tablets.

Thanks for letting me know about the 2012 Kindle Fire. I think I know someone with one of those sitting around and I might be able to get ahold of it in a few weeks (at a minimum to satisfy my curiosity to see if I can get it to run).

You might be able to free up some space on it and still get it to work. 

Got at least 10GB of free space. Of the 1Gb RAM, it should still have 400 Mb free. Maybe. Just guessing, cause Amazon patched out the task-view. I can run a N64 Emulator though 

Yeah, sounds like you are fine on storage. My Android phone, storage is more of an issue (4 GB) and during testing I managed to run myself out of space a few times.

If you posted Quakeid1qconsole.log off your device folder pic via USB, I might be able to learn something useful about the crash.

(You usually need to restart the device first to see the file. Android uses MediaStore to keep track of files and rescans on boot, Quake doesn't have a good way to update MediaStore because it is a low-level native C application.)

1) You might try the APK for Virto I made in post #100 to see if that works. It tells the device the desired color format.

2) Seems from your description that video works (download flashes the screen, changing the shading as it downloads) and that download works.

Barring that, I have a friend of friend who I know had a 2012 Kindle Fire, but it won't be quick to get ahold of it. 

I'll have to play around. I'm hoping it isn't "luck of draw" depending on screen resolution. I modified the algo but apparently on some resolutions the draw stretches favoring certain columns more of liney look on the transparent water. 

I am pretty sure I have a 2012 Fire. Will confirm with you. This project is so cool I want to help out where possible. I can also test on other models. I have access to a Pixel and a 1st and 2nd gen Moto X. I'll report back. 

Could you check if your 2012 Fire has the problems that brassbite does? 

Yep. Will report back this evening. 

Can't revall the year, 2013 maybe 2012. 

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