This is just a placeholder post!
i'd like to see someone reverse engineer the playstation app that SE is using so we can dump our own classic PSone ISOs on there!
that'd be cool. because we all know we'll be waiting forever for SE to release all our PSone favs!
I would really like this too.
I'm excited because the Play has the same chip as the HTC Desire HD. Port will happen eventually i'm sure. Heck even the new adreno 205 driver will be awesome.
Keyboard
But without the physical keyboard gaming would be just boring.
that might be true for text based games, but I'n sure you can hook up a keyboard over bluetooth.
Now it would be really cool if we got a psp emulator. So we could play all those psp dumped games from the CFW ages.
First of all, root acces, dont you think=?
friscoltu959 said:
First of all, root acces, dont you think=?
Click to expand...
Click to collapse
once we can oem unlock the bootloader it won't really be that hard at all. Basically just waiting in a holding patern to hear from sony ericson.
you normally have to hack the phone to get root access and then try to overwrite the boot loader so you can install custom roms with custom kernels and roms with root access for other stuff etc. We're just going to bypass that first step, and the manufacturer is giving us the ability to do step 2 fairly easy so custom roms with builtin root access should be relatively simple.
To enable this, we will later launch a web service where an unlock boot loader key can be retrieved by entering your IMEI. This key will be used in Fastboot where you perform the actual unlock boot loader sequence. A more detailed instruction will be provided later, when this service is available.
Depending on the original configuration of your phone, it will be either be possible or not possible to unlock the boot loader. No phone updates are required to enable this functionality.
Click to expand...
Click to collapse
http://blogs.sonyericsson.com/devel...e-boot-loader-in-the-new-xperia™-smartphones/
If i am not totally wrong there is a Play-Station Emulator on the market, which also supports the Game-Pad on the Device, so it should not be a problem to play your old PSX games (the ISO's) on any device, even the Xperia Play. But i'd really like it, if there was a possibility to install a custom rom on it, and yes i know, that the bootloader is locked.
Yeah just put in PSX emulator and run the PS1 isos.
The psx emulator was pulled from the market.
malac0da13 said:
The psx emulator was pulled from the market.
Click to expand...
Click to collapse
Try FPSE works much better then PSX4droid !
installed them both and love FPSE more then PSX4droid
Regards
arcticmedia said:
Try FPSE works much better then PSX4droid !
installed them both and love FPSE more then PSX4droid
Regards
Click to expand...
Click to collapse
Much better, more options, runs faster, more compatibility... Just better
The psx emu was taken down april 1st. Some say it was sony who had it taken down, and some say it didn't use the proper open source licenses...no one really knows what the reason was.
I have closed this thread as it was only a place holder and it has served its purpose.
Related
Mupen64plus-AE
Hi I just wanted to give some attention to the new open source
n64 emulator for android Mupen64plus-AE which was developed by Paul Lamb.
Its currently in its beta testing phase and it would be awesome if other developers wanted to join in and contribute to the project.
Android market link:
https://market.android.com/developer?pub=Paul+Lamb
Heres a link to the latest build + source code:
http://www.paulscode.com/forum/index.php?board=11.0
[This is currently the only emulator for android with xperia touch pad support]
Here is an overview of the emulator:
Here is a comparison video of banjo-tooie running on n64oid and mupen64plus-ae:
Here is an extra video I made of the xperia play touch pads working with the emulator:
Common questions
The GUI is now finished so most of this information is now irrelevant
How do I map the gamepad buttons?
First, install and run the "SDL Scancode Finder" linked below. Press the keys you want to map, and write down the Scancodes that are displayed. Then after running Mupen64Plus AE at least once, close the app and edit the file [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini. Under the [Keyboard] section, enter the scancodes that you wrote down earlier. For the analog stick, use the scancodes for the left and right buttons for "X Axis", and the scancodes for the up and down buttons for "Y Axis". Finally, save the file and restart the emulator.
SDL Scancode Finder:http://www.paulscode.com/source/AndroidSDLScancodeFinder/ScancodeFinder-debug.apk
Alternatively you use my control config and just paste is over the file. Just replace [sdcard]/app-data/paulscode.android.mupen64plus/data/InputAutoCfg.ini with the custom version of the InputAutoCfg.ini
Heres my config: http://dl.dropbox.com/u/13594612/paulscode/InputAutoCfg.ini (right click and save as)
How do I change games?
Delete or rename the file [sdcard]/app-data/paulscode.android.mupen64plus/roms/mario.n64. Place the ROM you wish to play into that directory, and call it "mario.n64" (it doesn't matter what format the ROM is in, just call it "mario.n64", and the emulator will load it instead of Mario64).
How do I remove the touch control overlay?
Go to [sdcard]/app-data/paulscode.android.mupen64plus/skins and delete everything in there except the folder called touchpads, the touch pads folder it what lets you use the xperia play touch pads.
Click to expand...
Click to collapse
*I take no credit in the creation of this emulator all credit goes to Paul and the people behind the original Mupen64plus source code. Im just a tester nothing more haha*
that'd be cool, but even cooler if N64oid got it
Nhialor said:
that'd be cool, but even cooler if N64oid got it
Click to expand...
Click to collapse
N64oid probably never will though. Adding touch pad support cuts of every android device
that has a firmware lower than 2.3 and thats alot of devices.
With Mupen64plus-ae multiple builds can be made so it doesn't effect other devices.
Thats why I feel so strongly that developers should help support this project,
it means that developers can add whatever they want and can create device specific features.
I would love to see this with touchpad support. Waht do you guess how long will it take?
IE-coRe said:
I would love to see this with touchpad support. Waht do you guess how long will it take?
Click to expand...
Click to collapse
Touch pad support is nearly done, my best guess it will either be finished by tomorrow or in a few days. Also just to clarify I am not the one making this emulator.
This the latest build for non qualcomm devices: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug.apk
This is the latest build for qualcomm devices (like the xperia play: http://www.paulscode.com/source/Mupen64Plus-AE/13SEP2011/Mupen64Plus-debug-sortProblem.apk
The xperia play version has very bad graphics at the moment but paul is working on fixing that atm.
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Logseman said:
You mean Paul as in Paul O'Brien, Modaco's overlord and programmer extraordinaire?
Click to expand...
Click to collapse
No the full name of the Paul who is making the emulator is Paul Lamb
Rockin'
Sent from my R800x using xda premium
P.s. I can't wait for this to come to fruition. Finally! A viable way to play Duke Nukem
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Nhialor said:
What are you talking about? Google made it so that multiple versions of the same apk can be uploaded to the market under the same heading, so adding it for our device would therefore NOT rule out other phones, as they could just download the regular version (our version wouldn't be able to be seen by them), also, as a computer science major, it'd be easy to not have this problem if he doesn't want to go down this road, he could do, for arguments sake, if build.prop=="R800i"|"R800x"{control-type="touchpad"}else{control-type="regular"}, or even just a tick box in the option menu...!
therefore avoiding the problem. Obviously it goes a lot deaper than that, but saying that adding support for us would rule out other devices is just not true. It's something else that's stopping him.
Click to expand...
Click to collapse
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
bubblegumballon said:
Well If you actually knew anything about n64oid you would know that its not even on the android market. Its distributed via slideme which does not support uploading of multiple apk's for a single app.
And ive talked to alot of emulator developers and for some reason (Im not entirely sure why) Including touch pad support cuts off support for older versions (lower than 2.3).
Click to expand...
Click to collapse
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Nhialor said:
haha ,completly forgot about that, but still, u see my point about the proper implemantation?
EDIT: Wait, I remember something that either Yonghz or Shtruck said something like the classes needed for this are unaccesible for Froyo and before or something, so you may be right. Apologies
Click to expand...
Click to collapse
No problem and Im sure ive seen Shtruck say something along those lines on the fpsece forums
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
hairdewx said:
I would imagine they would be able to add backwards compatibility after adding touch pad support, but that would take extra time - which they may not be willing to give the time.
Click to expand...
Click to collapse
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
bubblegumballon said:
Im not sure what you mean by backwards compatibility but in the future arm6 devices will be supported as well.
Also touch pads are in the process of being added, in the newest build the touchpad overlay has been added to the screen and different layouts have been made for different screen sizes (phone, tablet, small screens etc).
Click to expand...
Click to collapse
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
hairdewx said:
I meant having N64oid, FPSE, etc. detect the android version and run version specific code to add touch pad support while avoiding the compatibility issues.
I have done that before in software (I am a software engineer for a living) but it takes a long time to do and adds extra things to support. I certainly would not be motivated enough to do that either
Click to expand...
Click to collapse
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
bubblegumballon said:
Im no emulation programmer but alot of emulator developers have said the same thing that implementing the touch pad controls limits it to 2.3+
Im sure if somebody was brainy enough to create an emulator then they would know how to support more versions if it were possible.
also I would like to point out that Mupen64plus-ae supports arm6, It was already implemented but I forgot to update my post.
Click to expand...
Click to collapse
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
hairdewx said:
Touch pads limit it to 2.3+ because of some of the classes and available system calls it needs are only in 2.3+.
But that doesn't mean it's impossible to make one apk support all android versions, just very impractical implementation-wise and probably not worth it.
Click to expand...
Click to collapse
The project is open source so anybody (with the right knowledge) could just go and add touch pad support if they wanted.
Also I would like to point out touch screen controls have now been added but they are still not finished, there are still a few more things to be added like a moving analog stick and lots of optimisations so dont expect it to be perfect just yet.
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
bubblegumballon said:
Mupen64plus-ae now works properly on adreno GPU's (qualcomm chipsets)
It works great on my xperia play! keep in mind that its still not finished yet.
Click to expand...
Click to collapse
did you use the first apk or the "qualcomm" apk?
because Im trying the second apk and its not letting me download the data from paulscode.com...
any help would be appreciated
Hey guys, so me and my best friend bought Nook Tablets yesterday after seeing all the cool things that the rooted Color could do. Weve been playing around with it, and with the help of some threads here have gotten Go Launcher and all those basic apps to work like the Amazon Store and file managers and such.
Ive also got a fun game called Zombieville USA working after many attempts. However, for some reason not every apk i try installing works, and i was wondering why that is. For example, i tried for a while to get GameBoid working so i could play GBA games. It would install, then ask me to locate a bios file, which i then downloaded and got it to recognize, but after i open the actual Rom, it would run for a second and then stop.
Other apks give parsing errors, others just dont work. My friend just successfully got Fruit Ninja to work, and thats pretty much been our achievement of the hour. Were new to android and the tablet scene for that matter, but very well acquainted with jailbroken iPod Touches.
tl;dr why cant i get every app to work? Thanks for taking the time to help
Apps that don't work
One of the reasons might be that the Nook Tablet has only a subset of the hardware the typical Android Smartphone has.
No GPS, no accelerometer, etc.
Even some of the hardware it does have, like blue tooth, has no software drivers in the stock Nook operating system.
If the application you are trying to run is dependent on one of those missing resources, it may well fail. Missing libraries might be downloadable.
Your best bet will be applications known to run on the Amazon Fire, which has a comparable feature set. Rest will be try it and see.
Alright that makes sense, thanks. Ill go look around that forum then and see what i can dig up
Hi guys,
I've just made the switch from iPhone to the Galaxy SIII and am loving the ride so far. I'm a big fan of the old school type games and have been reading up on how to play them on my new phone. Dosbox Turbo is the way forward I believe! So, I've downloaded the program as well as the manager. But I have one problem. How do I get games from my Mac (or PC) to work on Dosbox. As in, do I just hook up my phone and move the games into a created folder on it? Is it that simple? Also, what files does dosbox need to read? The ISO? As you can see I'm a complete noob in regards to anything Android currently and any information or a tutorial would be greatly appreciated!
Cheers!
totallyfukt said:
Hi guys,
I've just made the switch from iPhone to the Galaxy SIII and am loving the ride so far. I'm a big fan of the old school type games and have been reading up on how to play them on my new phone. Dosbox Turbo is the way forward I believe! So, I've downloaded the program as well as the manager. But I have one problem. How do I get games from my Mac (or PC) to work on Dosbox. As in, do I just hook up my phone and move the games into a created folder on it? Is it that simple? Also, what files does dosbox need to read? The ISO? As you can see I'm a complete noob in regards to anything Android currently and any information or a tutorial would be greatly appreciated!
Cheers!
Click to expand...
Click to collapse
DosBox Turbo Getting Started FAQ
If you've never used DosBox before, you should also read the DosBox Getting Started Wiki
Basically, you get the DOS games you want from the internet (GOG, etc) and then unzip and download to a folder on your SD card on your Android Device. Then using DosBox Turbo (or better yet, use the DosBox Manager and create a profile) start your game. Be aware that you may have to run the game's setup.exe utility to change the game's parameters.
Cheers for the reply. A follow up question though. Do you need an SD Card to run the dosbox games or can you use the phones internal memory? Also, if I have the original disc of the game I want to run (I've checked on dosbox to see if its compatible) can I just copy all the files from the disc and use those to run the game(s)?
Ok, so I have been reading up on DosBox and have tried installing and running a couple of games with little success. I thought if I tried running it on my mac first and then moving the files over to my phone once successful would be the best bet but I am still yet to get a game to work on my mac! Bah...
I've done a little hunting for DosBox Turbo guides and or videos but they seem to be very limited. I've also tried contacting the Dev but have had no reply in a week which a little annoying. Sorry to ask again but does anyone know of a tutorial I could follow to install a game via DosBox Turbo so I can follow and learn from it?
totallyfukt said:
Ok, so I have been reading up on DosBox and have tried installing and running a couple of games with little success. I thought if I tried running it on my mac first and then moving the files over to my phone once successful would be the best bet but I am still yet to get a game to work on my mac! Bah...
I've done a little hunting for DosBox Turbo guides and or videos but they seem to be very limited. I've also tried contacting the Dev but have had no reply in a week which a little annoying. Sorry to ask again but does anyone know of a tutorial I could follow to install a game via DosBox Turbo so I can follow and learn from it?
Click to expand...
Click to collapse
DosBox requires significant setup, and if you are a noob, you should also read the DosBox Wiki. Once you get DosBox Turbo setup properly, it works like a charm.
Here's a video on how to use the excellent DosBox Manager add-on. Here's a video on how to setup and use the Gamepad Keyboard.
Contact the dev again. He may have missed your e-mail. I'm sure he's getting many e-mails a day. He's always replied back to me quickly.
The masses never satisfied by what their device can do. Rather they want their devices to do what they were not actually made for. They might be people who would be wishing that they could watch daily soaps on their microwave.
A attempt to get PSP games working on android led to creation PPSSPP emulator. I guess the name is just a play on the name PSP.
Getting to the point now. X8 is a old device and has low specs and thus is not very efficient in running heavy apps. It cannot run PPSSPP too without crashing. So what we do is a work around here.
Instructions:
1.Clear up some space on sd card. 300 MB should be fine
2. Download RAM Extender from here. Its a paid app so i cannot distribute its apk.
3. Download PPSSPP from here or look in the attachments. Its free app with a donate version in market which costs approximately 6.62 US$
4. Open up ram extender and select Optimal value. It would set the values accordingly and then start the swap.
5. Overclock atleast to 768 Hz.
5. Open PPSSPP and run the game.
Not all games work yet
Check out compatible games here
Keep in mind that X8 is very weak phone compared to monsters out there so games might be slow.
I have tried Dragon Ball Z: Evolution and it is slow. Used froyopro with alfs v9c for it. Other smaller games would work smoothly.
One of those would want a proof or it did not happen? Check the attachment for screenshot
Official Site: Here
Questions about PPSSPP? Click here
Think you can help them out? Click here for their github
Not my app...
What about tekken 3?
Does this 'ram expander' works on stock kernel?
wanna thank xda? here
I think ram extender need unlocked bootloader and a custom kernel like nAa or alfs,because stock kernel doesn't support swap.
I'm getting this...
Very difficult to capture the error message ...
huh....
wanna thank xda? here
Gogeta said:
What about tekken 3?
Does this 'ram expander' works on stock kernel?
wanna thank xda? here
Click to expand...
Click to collapse
tekken 3 is for ps1 and 2.. use fpse for ps1 emulator....ps2 emulator.. i dont think you will find any..
and you need swap support..so unless stock kernel allows it you need custom kernel
Would it be possible to emulate android on an android phone? As in, you could supply an app with an android version (or have the app build it for you) an emulate or run it. Any time it asks for something device specific, it would simply run the request back to the stock OS. Said app would kill all but the essential android processes to improve performance. And to return, it could add a shortcut to the app drawer that would close everything and return to the stock. Using this, could we create universal, or at least wider, distributions of android?
Android in your android so you can android while you android....
I love it! its like watercooling a raspberry pi, because you can.
would be amusing to see
Darkcon said:
Android in your android so you can android while you android....
I love it! its like watercooling a raspberry pi, because you can.
would be amusing to see
Click to expand...
Click to collapse
My main idea was to be able to emulate any android version on any other and have it work as if it was built for that device. So if you had a KitKat device, and there were no Nougat ports available for your device (ahem), you could still run Nougat by emulating it. AKA, universal distributions of android.
But that would be pretty ridiculous. Actually, that could be a new benchmarking method: how many stacked emulators can it handle?
The Original Leppa said:
My main idea was to be able to emulate any android version on any other and have it work as if it was built for that device. So if you had a KitKat device, and there were no Nougat ports available for your device (ahem), you could still run Nougat by emulating it. AKA, universal distributions of android.
But that would be pretty ridiculous. Actually, that could be a new benchmarking method: how many stacked emulators can it handle?
Click to expand...
Click to collapse
I can see a few good reasons you'd want to do that, would require root, and alotta work tho
Darkcon said:
I can see a few good reasons you'd want to do that, would require root, and alotta work tho
Click to expand...
Click to collapse
Well, if no-one supports your phone, what other choice do you have? Also, were this a thing, it would be easier for ROM developers, too, as you could simply update a single package.. As for SU permissions...
SU would only be used for, let's see...
Not Bluetooth (can be accessed by other apps)
Not WiFi
Not calling
Switching off your phone? Holding power would just trigger the default power menu, as some system processes would still run and for the most part the emulator app would be treated as any other.
Killing processes for extra efficiency? Maybe. But it would be optional and likely wouldn't make much of a difference.
The Original Leppa said:
Well, if no-one supports your phone, what other choice do you have? Also, were this a thing, it would be easier for ROM developers, too, as you could simply update a single package.. As for SU permissions...
SU would only be used for, let's see...
Not Bluetooth (can be accessed by other apps)
Not WiFi
Not calling
Switching off your phone? Holding power would just trigger the default power menu, as some system processes would still run and for the most part the emulator app would be treated as any other.
Killing processes for extra efficiency? Maybe. But it would be optional and likely wouldn't make much of a difference.
Click to expand...
Click to collapse
Hmm you've got a point there, this could be used to root a phone thats unrootable effectively, like the android emulated inside an Iphone that some people did in the Iphone 4 days
all depends on implimentation, you'd have to set up the emulator to trigger normal events, like power saving cpu states etc in response to the emulated android os's requirements
I've been thinking.
Let's say you decide to emulate AOSP Nougat. You then installed the official Pixel Launcher. While emulating, it would act as it should, as it would be entirely identical to if you were running Nougat.
Then you close the emulation. You then try to open Pixel Launcher; it's already installed. Would it crash?
Ok then...
Would I just look for adb? Or does adb simply ask something else to emulate?