It's funny how you can assign your wired Headset controls to fpse4android.
If schtruck could fix the latency it would make a nice concept for a new kind of 3.5-jack gamepad.
I'll call it HeadPad.
i900frenchaddict wrote:Would it handle two simultaneous pressed keys?
Tatsumaki Senpūkyaku wrote:It's funny how you can assign your wired Headset controls to fpse4android.
If schtruck could fix the latency it would make a nice concept for a new kind of 3.5-jack gamepad.
I'll call it HeadPad.
schtruck wrote:thankfully, i received my zeemote today too, and i started to implement it using Zeemote SDK...
it start to work, and i must it's a very good device, not as you are describing? very good quality and work very well.
i'll finish to implement it this evening then will release an update... i've played Crash Bandicoot, and it's very good.
Vooder wrote:And a big red first sentence :
"I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT THIS ROM HAS CAUSED. FLASH AT YOUR OWN RISK."
plus problems with warranty are not for everyone, you must know that, esspecially with new phones.
I agreed with fact, that adding 2.1 support is more important than bt pads, and its more profitable for producer, its just a big growth of customers.
In fact, author ignores all posts about 2.1 version, giving no clearly respond.
Shru, can you tell us , will be the 2.1 version ? It's a big part of android society now.
LouCipher wrote:Vooder wrote:And a big red first sentence :
"I AM NOT RESPONSIBLE FOR ANY DAMAGE THAT THIS ROM HAS CAUSED. FLASH AT YOUR OWN RISK."
plus problems with warranty are not for everyone, you must know that, esspecially with new phones.
I agreed with fact, that adding 2.1 support is more important than bt pads, and its more profitable for producer, its just a big growth of customers.
In fact, author ignores all posts about 2.1 version, giving no clearly respond.
Shru, can you tell us , will be the 2.1 version ? It's a big part of android society now.
I'm going to answer this one again, because I like this thread, and am tired of seeing this here. I'm not going out and finding the link to schtruck's post on xda again, you can search yourself if you're interested. Simple explanation is this: fpse currently relies on some API functions that are ONLY present in 2.2 and up (libjnigraphics). Changing that is going to require a major rewrite of some fairly important code, and I've no doubt that it will be a major undertaking on schrtuck's part. It's not the kind of thing he can just hack out one afternoon and post on the market.
So, schtruck, like any dev, has a choice to make. He can either spend a great deal of time backporting the code to work on 2.1 (and even then, it's not that simple. The new code could require significant optimizations, might slow the emu down for existing users) to get some new customers, or he can focus on the many small, comparatively quick and easy fixes that need to be implemented for the existing user base first, then possibly worry about backporting. Me personally, I'd rather have fpse working perfectly and looking (even more) amazing on the currently supported versions of Android before worrying about porting it back to an old version.
@music4lynx - Don't be an ass. No one owes you an emulator. If you don't like waiting, can't or won't upgrade your phone, and just want to bitch, go buy psx4droid. It works on 2.1. And who knows, maybe it will see another update sometime this year.
Edit: So I lied, here's the post: http://www.androidemus.com/showthread.p ... 57#post757
and it's from androidemus, not xda as I originally thought.
Users browsing this forum: No registered users and 15 guests