Thread Rating:
  • 4 Vote(s) - 3.75 Average
  • 1
  • 2
  • 3
  • 4
  • 5
PCSX2 on Android
Can I suggest to install cpuspy and to check the clock frequency. On my galaxy note, it becomes quites hot at 1.4GHz (default clock)!

Sponsored links

I have my Galaxy Player 5.0 overclocked from 1GHz to 1.3GHz easily, you can feel some warmth but not very hot at all. It just depends on the phone you have.
I have a Nexus 7 with quad core Cpu and Tegra 3 Gpu, I think it could handle a Ps2 emu if it was written for the devise or more importantly Android
ROG Asus G74S laptop
Intel core i7 2670QM @2.2(3.1ghz turbo) Nvidia 3gig GTX560m 8 gigs DDr5 Blue-Ray Burner windows7 64 bit
[Image: r1gyld.jpg]
No, or at least not today or anytime soon.

What about this?! Does anyone notice that I posted stuff about this?!

If it is going to be possible to make a PS2 emulator on Android, x86 is better than ARM.
PCSX2 has a good chance of just working on that, yea.
It'd need some GUI work for the Android layer but the hardware and the Linux Kernel should be up to the task.
Expect simple 2D games to be possible with this.
That's what I'm saying! Plus this is only the first x86 Intel made for mobile, so it will just keep getting better and better when time comes.
I agree about making an emulator, btw i still can't understand how @rama changed mind so fast Wacko

Did the coders came back to the team?
Oh, and thanks for your help. In the and i didn't make the nds emu but did helped Jeffrey on his nds4droid project.
Looky here:

Android is really taking off in emulation, first NDS and now PSP right after? Although it is in early development, it can already play some commercial games which is good. Needs a dynarec though, same goes with nds4droid.

Dreamcast is next for sure, they just need to fix the "remaining issues and such": and

I'm positive PS2 can be next in the lineup.
(11-20-2012, 06:38 PM)V6ser Wrote: I agree about making an emulator, btw i still can't understand how @rama changed mind so fast Wacko

Hmm, what do you mean?
PCSX2 on Android is an issue of the CPU mostly, ARM vs x86.
I'm saying that it's far more likely to happen on x86 than on ARM
(because we don't have to rewrite the whole core to support a x86 handset).

Users browsing this thread: 1 Guest(s)