I was using 1.7 fwiw. I can try with 1.5. 

Oh yeah, and it might be an AD 1.7 thing anyway since the mouse driven menu from regular ol PC Mark V also doesn't work with 1.7 either. 

Just tried AD 1.7 and then 1.71. Not able to replicate your issue. Mouse driven menu works fine. I also opened AD's 1.71 quake.rc file to see if it contained something unusual ... it didn't.

Obviously you have something going on, but I wasn't able to cause anything unusual to happen.

/Delete config.cfg and autoexec.cfg? 

Replicated your issue.

Sometimes when the config.cfg is being written, for reasons I don't understand the config file gets truncated and it doesn't write the whole thing. Must be some sort of "Android NDK thing".

Delete your config in ad folder.

When I do an update next around Christmas either I'll do some research and find out why Android NDK may sometimes write incomplete files or have QuakeDroid ignore an incomplete config by writing a checksum into the config header.

Android is known to arbitrarily terminate applications whenever it likes, which means verifying the file wrote completely wouldn't work if that is what is going on.

But one way or another, when I do an update around Christmas, I'll make this problem impossible. (Especially since it is very annoying.)

/Excellent bug report! 

I deleted config files in AD and id1, as well as autoexec, and it didn't seem to help. I'll putz around with some other stuff too. 

Btw, I did want to say, despite my issues with AD, everything else I've tried has worked amazing. I'm going to be getting a GPD XD Plus this week and I'll try it on that as well. I suspect that will be an excellent match. 

And my phone that I've been testing on is a Lenovo Moto e4. 

Any chance you've messed with adding Touchstick style controls (like in *cough* Minecraft or PUBG), and the ability to hold shoot down and then still look at the same time. 

When I work on stuff again around Christmas, I'm going to hit up controls more.

Never forgot about your input on that, it just kept getting bumped by [insert bug report] or [insert usability issue]. 

I just got my GPD XD+ today, and while QuakeDroid seems to work really great, there's a major issue: the display is turned 90 degrees, and I can't seem to figure out how to fix that. Any ideas? 

Do you mean upside down?

Or do you mean it renders as a tall screen like this picture? 

Yes, tall and narrow. No idea why though, it's really weird. But the controllers face the right way iykwim 

In Menu->Options->Video Mode, what resolution does it say?

I agree this is major issue, so I will try to do an update Sunday to solve your issue if time will allow me to do it.

Android is really diverse in devices, versions and configuration. 

It lists my res as 720x1280. Also noticed that sometimes the sound randomly doesn't work, but closing and reopening a couple times brings sound back magically. 

I have the new "portrait-verify" version done that I hope will resolve your.

I'll be uploading it in the next 24 hours after I double check some things tomorrow.

Since I don't have the issue myself, you are the only one I can think of that can verify it solves your issue. 

>>Also noticed that sometimes the sound randomly doesn't work

i got this issue too 

I'll keep an eye out for your update. Looking forward to trying it out. 

QuakeDroid GL Orientation Detect Fix:

Download: Android APK

I think it should work. But coding for a situation you cannot duplicate is never a sure thing.

Let me know! 

I'm happy to report that your fix works great on my 2018 model GPD XD Plus. For other GPD owners who care, I suggest setting the gamepad touch mapping off (push the gamepad button and push reset) and then use the config GUI from GPD to select Xbox control emulation. Works great! 

I am glad it solved your issue. 

https://youtu.be/Fdh3Gd_5eHk

Well, here's proof it worked. Thanks again Baker! 

Some apps appropriate the volume buttons for their own purposes (example: naked browser, which can be set so that it navigates through tabs). Such buttons could be used for weapon switching. When doing this, the "next weapon" button could be done with, enabling more screen real estate.
Having this in a vc repo would enable us to contribute an ease your job too ;) 

 

Add support for the volume+ button to shoot, volume- button to cycle weapons. Surely this is possible since the camera app can takeover the volume buttons to take a picture. 

I was trying to play this with an otg keyboard and mouse and found that the mouse can navigate (the mouse is oriented for portrait mode and awkward) it can't be used for aiming. I'm not really interested in aiming with a touch screen so hopefully this is something that can be sorted.