A BIG DECISION ON ANDROID. Needs opinion.

CRxTRDude

CRxTRDude

Member
Okay guys, I got some news for you. I have done what seemed to me impossible before, updated OpenBOR's Android port to support a more recent SDL2 build than the one provided (SDL2 2.0.2 as opposed to 2.0.0).

Here are the highlights for SDL2 2.0.2 in Android:
EDIT: strike that, that does not compute.

As you guys can see the biggest milestone for this SDL version is external joystick support and now we can disable the accelerometer as joystick. This is good news for most people that want to use external joysticks as controllers. (I might assume that we can have multiple players now, I guess) The bad news is apparently we need to build the port in Android 3.1+, which means devices using Android 2.2 could not run OpenBOR if we use this SDL version.

Now I want you guys on your opinion on this, I moved this on a separate topic so that I will not crowd my own thread (the Modified Android port thread). Do you want support to older versions or do you want to limit our scope for Android from 4.0+*?

Opinion is welcome here, but I will not answer technical problems yet, we need first to make this work in the first place before I dare to fix problems.

* Moving it up a notch, because 4.0 is a good start for the minimum requirement, since most recent phones still have this OS at a certain point.
 
I have my phone with gingerbread 2.6, im not sure how's performance when playing on phones with android 2.2 ? These were with 700mhz processors maximum or something? So i think its still possible to enjoy some games and i would leave compatibility between systems how it is.
Is there any fps boost or something at all to make it worthwile to switch?
For now i suggest dont do it ,just disable gyro sensor for eternity and forget about it, limiting people like that just because of higher number after SDL is too big price especially if it works really fine how it is.Whats the real advantage of using newest SDL version besides higher version number and pluggin joysticks midgame ? These are not really any serious advantages worthy your time to code support of this new SDL.
Joypad actually works completely fine on my GPD device and old openbor android build.
 
It's shame most phones don't have physical keys…
IMO they’re not very fit for hard-core games like games on OpenBOR.
Maybe adding some touch supports for Android build is much more practical.
 
I agree with you though, you're right about that bWWd. Respect that, I'm no utunnels to make a difference here, but that doesn't mean I can't do anything here. I got your advice on this, but I'll stick to my guns. That does not mean that I will go ahead gungho and commit. Thanks for your advices though.

For that, I'll try to do disabling the accelerometer by hand now. Sorry about that guys, I think Illu might want to transfer it to the modified android build thread if it's okay.
 
Well its just not worthy your time which chould be spent coding something else, joystick support isnt that important cause you can map joystick normally if you just disable gyro sensor.
IF there would be improvement of something like fps boost or more compatibility then it would be worth it but its kinda opposite with compatibility which is always a bad thing to limit userbase.
Even for my GPU cards im using old drivers most of the time, i thought its normal cause many new drivers for older devices are broken.Not really a big deal to use old version.
 
Well, I want to question regarding the joystick and gyro, your GPD have both the joystick and gyro? I want to know the log for who is loaded first and second.
 
yeah i have accelerometer in GPD like most smartphones, i couldnt setup my own controls because its always on and i have to press buttons fast to make it register as new key in openbor controls menu or try a couple of times until it works bu my gamepad was workign right away i just swapped positions of jump and attack.
 
You must log in or register to reply here.
Back
Top Bottom