just got worms world party, and i can't play >.< none of the buttons will work except to move around. I tried this post with editing the hex in the same file but the fire button won't work.
the buttons codes are
green=0x72
red=0x73
center=0x86
camera=0xcc
but when i put them into the hex they arn't even what i assigned them to and none of them fire.
Has anyone had any luck with this game?
Related
Has anyone found an nes emulator that works on the vogue? I've tried pocket nes and pocket nester neither work.
I have PocketNES on my Touch... It works fine I just have to reassign buttons every time I reopen the ap.
I use pocketnester with no problems at all.
http://sourceforge.net/projects/pnester
now where to get roms?
winmobilelawyer said:
now where to get roms?
Click to expand...
Click to collapse
YEAHH!!
http://mobile.surrealnetworks.com/NesRoms.htm
Enjoy!
I dont get how you run this emulator, and where do the roms go to?
harveeey sayz said:
I dont get how you run this emulator, and where do the roms go to?
Click to expand...
Click to collapse
anywhere really. Pocketnestor automatically searches all directories for roms. I keep them in a folder on my storage card.
that being said, i'm finding this doesn't work that fast on the Vogue. It's near if not impossible to press two command buttons at the same time (say up and A or left and B...or even A+B together), so i find that it limits the games that can be played
i also find that certain games run *reaaall* slow, even if i update threading to realtime.
Anyone have trouble assigning the call button to the controller on the touch?
i followed the link to sourceforge, but which file am i supposed to download and extract onto my HTC touch? i'm still very new to this, any help would be appreciated.
Bacchus416 said:
anywhere really. Pocketnestor automatically searches all directories for roms. I keep them in a folder on my storage card.
that being said, i'm finding this doesn't work that fast on the Vogue. It's near if not impossible to press two command buttons at the same time (say up and A or left and B...or even A+B together), so i find that it limits the games that can be played.
Click to expand...
Click to collapse
Totally. i've discovered that for that reason, most action and platform games are useless. However, any type of puzzle game doesn't require multiple key touches... also, RPGs are great. I've been playing Final Fantasy 3(english hack) for a week now, and it's made my trips to work AWESOME.
Bacchus416 said:
i also find that certain games run *reaaall* slow, even if i update threading to realtime
I found that increasing the frame skip and thread priority in options helps with this. problem is,i find that if my thread priority high or real-time , when you're done with your emulator - you'll need to soft reset. It seems to cause some kinda memory loop
Click to expand...
Click to collapse
Hi I have FPse and cannot for the life of me configure it so that I can play my favorite classic X-Com on my G1. I have everything configured including the BIOS file but I cannot get the hardware buttons to work. When I assign a hardware key it appears as though it assigns and then when i go to play nothing works. Please help. Thanks.
Wow, not 1 reply, y'all stank! Figured it out on my own. Hate this forum. C ya.
Please help us test it out and report bugs/issues. Thanks
Just search "adosbox" in Google, I am not allowed to post external URL here.
Any kinds of help are welcome
Hi, i downloaded this last night for one reason and one reason only (for now anyway) - to play championship manager and i managed to get it start a new game it took over an hour to do it and then simple things like changing pages takes over a min so it esentially unplayable.
Other that great work and i wish i could be of more help but im afraid ive never done any software programming in my life
Wow, this is perfect so far. I just tried cyberdogs on it and it ran amazing. The program is really easy to get running. Is there a way to mount hard keyboards to the controls?
Just tried it. works like a charm.
Yep, works awesome.
Sent from my GT-I9000 using XDA Premium App
I am really enjoying adosbox right now on my Transformer, but lack of 3.1 mouse support has saddened me to the point where I compiled from source myself. I have it working sort of (on the java end), but because the build screen size doesn't match with the actual screen size, I am having issues with the mouse not following perfectly. I would like to get mouse support working better for 3.1 devices (and probably better emulation going for pre 3.1 devices), but I need to edit some of the C files for that. Unfortunately I have not done much native code on Android, so I am running into problems compiling. The ndk-build script seems to fail on me with an error of "missing separator" in the SDL-1.2 make file. Sadly I have never used make so I don't know how to correct it.
Today I saw the build_instructions.txt in jni/application/dosbox/. Are you building through this instead of the ndk (do I need to get gcc ARM cross compiling installed on my linux box)? In either case where does the dosbox-0.74-cfg-pelyaSDL.tar.gz come from?
Any help you could give me in getting the native part to build would be appreciated. Then I can focus on getting some usability stuff working and throw patches your way.
P.S. The feedback page is broken.
Hi. That's great news.
I love dosbox an I appreciate your work.
If you don't mind I will post some issues here.
I've installed adosbox 0.2.5 on my Desire Z.
I've tried to run some apps and games.
Dos Navigaror: Usable.
1. Mouse trackpad emulation works quite well, however it only moves in x,y axis separately. No intermediate directions (I suppose the hardware does not allow it). Any possibilities to solve this?
2. Touch screen mouse movement works quite well - however with delay.
2a. Well, sometimes there is no mouse. I swing on the screen with no effect.
3. It does not respond to screen tap as a left mouse click. Well it works sometimes. I have no control on that.
3a It does not respond to double tap (double click) at all.
4. No possibility to bind/emulate arrow keys. I can't find such function in dosbox menus. ---edit --- I could bind some keys but... see the edit part down there.
5. On PC I've been using config to autostart Dos Navigator with dosbox start. How to do it on Android? I couldn't find .conf file on my device.
System shock: starts but unplayable.
1. I've got a slide show. I've increased the CPU cycle to 1000 even to 2500 with no satisfactory effect.
2. On screen mouse movement works but the cursor jumps into different position when tapping.
3. With no option for binding keys this game is 100% unplayable.
Hocus Pocus: works but no arrow keys.
1. It starts nicely.
2. It reacts on "FN" key - the hero is shooting.
3. However no hardware arrow keys makes the game unplayable. Moving with trackpad sucks so much that the game is unplayable.
Oxyd Magnum: Playable but not exciting.
1. It react on taping the screen.
2. On screen mouse works well but with some ugly delay. This takes out most of the fun.
So the main issues I see are the cpu speed, mouse delay and the hw keys binding.
You are making a great job.
However making dos games being fun on the phone needs good controls workaround. Without that - no fun.
Thank you.
Don't forget we appreciate your work.
-------------edit-----------
Keys binding:
The .dosbox\mapper-0.74.map file (the file for binding keys) can not be found from the phone level. It must be done from a PC level. It's not a big issue but what to hide the file for?
After rebinding left FN, left shift and tab keys Hocus Pocus is quite playable.
It would be nice if you provide us the list of numbers for HW keys on some devices.
I can't bind "menu" as right arrow. And I can't bind search, sym, and the two shortcut keys. They are left useles.
And binding some keys as arrows disables trackpad!
Sound:
No mater what number I set for cycles I can't make the sound to play smoothly.
Any suggestions?
Someone knowns the makefile system for adosbox "libapplication.so"?
Ive been trying for a long time to recompile adosbox for mips, and i still unable to compile that file, not even for arm.
Hello,
I am using aDOSBox to run QBASIC (yes I know there are "better" and "faster" interpreters/compliers, but some have bad issues, see one comment about writting files on X-11 BASIC, others have a max file size) with an external keyboard (so I can see the screen while typing - can you make the virtual keyboard transparent?).
I have found that some keys do not work nor processed correctly in this version (freshly gotten from Google Play), namely the "." when shifted (I get ":" every time, all other punction keys appear to be fine). At first I though this was a KCM problem (had problems with mismapped keys on a Droid X), but while I was briefly able to rooted my tablet (someone please read/question my post/question about the Azpen A701 rooting) I was able to view the generic.kcm and other kcm files (lost root right after this) and those files define the shift period combination correctly. Also I get a ">" when I hit that combination in the 920 Text Editor.
Function keys seem to send to Android key processes (opening/launching other apps) instead of work in the program. Insert, Delete, Home, and End do not seem to be working at all.
Hey guys, I bought FPSE within the first day of getting my Xperia Play. The thing is an emulator machine and FPSE is a fitting addition. Love it so far. Few questions/problems:
1) My phone is unrooted/stock. It seems enabling the g sensor involves editing .ini files and such? Is it possible for me to do without compromising my warranty? Could you provide a link/video that explains how to do it on one of the more recent versions of FPSE?
2) What is the deal with the options for touchscreen analog and "Swipe" analog? I've only tried with Medal of Honor Underground but they're EXTREMELY hard to use. They take a strong push to get started moving, then JUMP in the direction you''re holding extremely fast, making aiming very very hard. Is this the norm with these options? Is it difficult to emulate the analog sticks of playstation?
3)Both of the above questions have to do with shooting games on FPSE. What settings do you guys use for first person shooting games? especially on xperia? I'm starting to think I should just give up on the genre for use with FPSE. (I'm not going to harp on the touch-stick support for xperia play like most, I understand thats probably really annoying to incorporate, especially with Verizon users STUCK in 2.3.2!!)
4) For PS ISOs with the "track 1" and "track2" parts, what do I do?? SF Alpha 3 has those components and I'm not sure what to do/how to rename it so it will work (with just track 1 it boots up like ps one boot screen, then black)
5) I found a SF Alpha 3 that only is one .bin file, but it runs SOO slow on FPSE, no matter what system/video options i tinker with. Does anyone have a definite rom/config for SF Alpha 3 on FPSE that they could tell me? Its one of my favorite games for PsONE.
Thanks in advance for anyone who answers any of my questions/thoughts
I can't answer everything, but I'll tell you all I know
1. I've tried the G sensor on FPSE once or twice and it worked fine without having to change any .ini settings. Can you tell me exactly what you did and I'll try to replicate this
2/3. I've only used the d-pad for movement in FPS games. without the touch pad supprt I stay away from them in FPSE. I do wish there was a way to impliment the analogue sticks better without touching the screen, but till then my advice would be to stay away.
Others on here may know of a better way to emulate them
4/5. We don't like any kind of warez/downloading. My advice would be to buy a disk and rip it to get a true legal copy of the game to play on FPSE. This should also miss out any anomolies. For anything else, it would be worth going on their own forums and asking about specifics of game support.
IMO (educated guess) I think the files need to be in one file format. So when you rip the file, rip it into one iso, this should put all files on the disc into a single file, as the iso is an image of the disc
Hope that helps, let me know how you get on - especially with the touch pads/analogue sticks
Hiya Everyone,
I've just rooted my Nook Simple Touch and have it all working from a USB keyboard which is great!
I really need the Nook as my unit has no mains electricity and I use solar panels instead which can be difficult at times as they are mounted in the window and are facing the wrong way really but it is what it is. I know everyone is alarmed at the amount of power it uses when in USB mode but it's nothing compared to the 5 watts my DAB radio pulls! To be honest it's even at lot less than the 1.5watts of the LED light!
Anyway it's basically great but I want to get it working as well as I can for my application.
I'm using a new text editor from F-Droid called Text Warrior:
https://f-droid.org/repository/brow...com.myopicmobile.textwarrior.android&fdpage=4
It's the best text editor I've found for the Nook so far and it's also a GNU application with source code!
If you havn't already checked out the F-Droid stuff I really recommend it as a lot of the apps there work on the Nook and it can be hard to find stuff for the earlier versions of Android.
Anyway that's my setup. What I'm wondering is if it's possible to assign keys on my USB keyboard to do different things and how I would go about doing that? For instance it might be cool if I could use the Esc key as a back button or the extended win keys menu key as an android menu button and things like page up and page down etc. How could I go about setting the keys up for different functions? Anyone have any idea?
Freya
FreyaBlack said:
Hiya Everyone,
I've just rooted my Nook Simple Touch and have it all working from a USB keyboard which is great!
I really need the Nook as my unit has no mains electricity and I use solar panels instead which can be difficult at times as they are mounted in the window and are facing the wrong way really but it is what it is. I know everyone is alarmed at the amount of power it uses when in USB mode but it's nothing compared to the 5 watts my DAB radio pulls! To be honest it's even at lot less than the 1.5watts of the LED light!
Anyway it's basically great but I want to get it working as well as I can for my application.
I'm using a new text editor from F-Droid called Text Warrior:
https://f-droid.org/repository/brow...com.myopicmobile.textwarrior.android&fdpage=4
It's the best text editor I've found for the Nook so far and it's also a GNU application with source code!
If you havn't already checked out the F-Droid stuff I really recommend it as a lot of the apps there work on the Nook and it can be hard to find stuff for the earlier versions of Android.
Anyway that's my setup. What I'm wondering is if it's possible to assign keys on my USB keyboard to do different things and how I would go about doing that? For instance it might be cool if I could use the Esc key as a back button or the extended win keys menu key as an android menu button and things like page up and page down etc. How could I go about setting the keys up for different functions? Anyone have any idea?
Freya
Click to expand...
Click to collapse
You can easily change what your keyboard keys do in the file /system/usr/keylayout/qwerty.kl. I personally use a very good modified one by Renate with a few of my own modifications.
Thanks so much Nookie! That looks great! I will try and install it today.
I'm also running the Nookie terminal emulator BTW which I think must be something to do with you?
Right off to give it a go!
Freya
FreyaBlack said:
Thanks so much Nookie! That looks great! I will try and install it today.
I'm also running the Nookie terminal emulator BTW which I think must be something to do with you?
Right off to give it a go!
Freya
Click to expand...
Click to collapse
It might. I did make a few modifications to the original Terminal Emulator and probably put it up for download somewhere here on the forums. What's the package name (/data/app)?
How'd the .kl installation go for you?
I discovered Noogie and after a lot of messing about I managed to get the qwerty.kl installed and working quite well.
Sadly it seems it's not going to be easy to reprogram for a UK keyboard though as you can only reprogram entire keys and not their shifted states.
In the UK the @ and " symbols are swapped with one another but on the upside the # key now does a # so that's nice.
I'm going to get used to the USA keyboard layout and be driven nuts when I switch back to a UK keyboard again!
I'm sure the terminal emulator must be your version as it has nookie in the filename.
Freya
FreyaBlack said:
I discovered Noogie and after a lot of messing about I managed to get the qwerty.kl installed and working quite well.
Sadly it seems it's not going to be easy to reprogram for a UK keyboard though as you can only reprogram entire keys and not their shifted states.
In the UK the @ and " symbols are swapped with one another but on the upside the # key now does a # so that's nice.
I'm going to get used to the USA keyboard layout and be driven nuts when I switch back to a UK keyboard again!
Freya
Click to expand...
Click to collapse
Hmmm. I see your point, and it's a good one, indeed. Tell you what - I'll work on it this week and tell you if I come up with anything by Sunday night. Sound good?
FreyaBlack said:
In the UK the @ and " symbols are swapped with one another...
Click to expand...
Click to collapse
See http://forum.xda-developers.com/showpost.php?p=59922517&postcount=406
Thanks Renate,
I ended up sitting in a hotel room with a hex editor but I got it to work and have since spent quite some time on Solar with the Nook.
Thanks again for your help with that!
Now I'm back to civilisation for a while and I'm wondering if it is possible to get the cursor keys to work properly too.
They don't seem to move up and down and side to side in the text in the way I would expect!
Is it possible to fix that as well or is that just an android feature!
Freya
FreyaBlack said:
Thanks Renate,
I ended up sitting in a hotel room with a hex editor but I got it to work and have since spent quite some time on Solar with the Nook.
Thanks again for your help with that!
Now I'm back to civilisation for a while and I'm wondering if it is possible to get the cursor keys to work properly too.
They don't seem to move up and down and side to side in the text in the way I would expect!
Is it possible to fix that as well or is that just an android feature!
Freya
Click to expand...
Click to collapse
Does this happen when your Nook is in portrait mode, landscape mode, or both?
If they work correctly in portrait but don't work right in landscape, there is a fix that I applied several months ago that resolves the issue.
ИΘΘK¡€ said:
Does this happen when your Nook is in portrait mode, landscape mode, or both?
If they work correctly in portrait but don't work right in landscape, there is a fix that I applied several months ago that resolves the issue.
Click to expand...
Click to collapse
OUCH! Yes you are totally right.
I'm using an ipad stand from a pound shop to hold the Nook in place and it fits quite nicely in Landscape.
Also I just find it's a bit more like a normal laptop setup when in Landscape mode too.
I didn't click what was happening. Doh!
So how do I go about fixing that?
I guess I have to swap the cusor keys around?
Freya
@FreyaBlack,
Kind of, yeah. Follow the instructions at this post by Renate to apply a patch to /system/framework/services.jar that will prevent your arrow keys from rotating when in landscape mode.
Good to go!
I'm back to civilisation for a while but sadly I havn't been able to get this to work. I don't quite understand what you are supposed to do and I usually use ssh or similar rather than adb.
What does this mean?
Then you edit in the replacement in smali/com/android/server/KeyInputQueue.smali
Click to expand...
Click to collapse
I assume I need to change services.jar in some way.
Do I use the attached file?
Freya
@FreyaBlack,
After you acquire services.jar on your PC, the next step is to decompile it using this command:
Code:
apktool d services.jar
Then, go into the root folder of where you decompiled that file, and navigate to the .\smali\com\android\server\ directory. In that folder, locate the file KeyInputQueue.smali. Open that file with a good text editor (like Notepad++ on Windows), delete the entire contents and copy/paste in the entire contents of the partf.txt file attached to Renate's post I linked two posts above. Save that file.
Now, all you have to do is recompile the edited services.jar file using this command:
Code:
apktool b [the directory where you extracted the file originally] services.jar
Only thing left after that is to replace the existing services.jar on your Nook (located in /system/framework) with the one you just created, reboot your Nook, and you're good to go.
You can also use my mergesmali utility to merge correctly formatted patches.
nook121patch.zip has patches for various things that can be selectively supplied.
They are both found in the signature under "mergesmali".
Hiya Renate,
So you mean I can find a patch for the file or something and use mergesmali to apply it?
I assume Nookie is saying I need the Android SDK or the java sdk to make the changes but by doing this patch thing I can sort this without having to do that?
I have my hex editor to hand but a whole SDK is more than my 3G connection can handle right now!
Freya