Dolphin, the GameCube and Wii emulator - Forums

@ All Others with 2.3 Phones i think you must not used your brain at all ? did u guys read my Thread where i was saying that i overclocked my HTC One S to 2,1 Ghz to reach 17 to 20 Frames ?

it is 2,1 Ghz on phone with 2.3 u wont reach 2 frames trust me on this. sometimes people dont use hear heads to think about it.

i still here to try out on my one s if there is a new build out.

Wow, its a great new that Dolphin is coming to Android.
I'm currently making space on my SD to move the TVC ISO to try on my Iconia Tab A100 (Tegra2 1ghz).

TVC is the only rom I have right now.

I'll let you know once I've tried.

Where can I donate?

Sorry about the lack of updates guys, I started my new job on Tuesday and it has been kicking my ass.

In any case, Monday evening I had made a OpenGL ES 3 context on the phone and did some unnecessary work. I ported over the VideoSoftware backend to OpenGL ES 3(it had already supported GLES2) just to make sure it was possible for it to work, which it did.
Porting VideoSoftware isn't exciting though because it is only pushing a final image to screen so it doesn't provide any speed up.

I then took some time to port the OpenGL plugin to OpenGL ES 3. Currently it runs on the GS4, but it doesn't produce any video output.
I'm going to be spending this weekend working on getting video output working.

If you need any more information, just prod me again, I'm a bit disoriented from the new job still.

(05-04-2013, 05:37 AM)Sonicadvance1 Wrote: [ -> ]Sorry about the lack of updates guys, I started my new job on Tuesday and it has been kicking my ass.

In any case, Monday evening I had made a OpenGL ES 3 context on the phone and did some unnecessary work. I ported over the VideoSoftware backend to OpenGL ES 3(it had already supported GLES2) just to make sure it was possible for it to work, which it did.
Porting VideoSoftware isn't exciting though because it is only pushing a final image to screen so it doesn't provide any speed up.

I then took some time to port the OpenGL plugin to OpenGL ES 3. Currently it runs on the GS4, but it doesn't produce any video output.
I'm going to be spending this weekend working on getting video output working.

If you need any more information, just prod me again, I'm a bit disoriented from the new job still.

Hi, [color=green]Sonicadvance1[/color], thank you so much for taking the time to port dolphin to the android platform. I am new around here, but I registered to thank you. The work you are doing is awesome and I hope you start to fair better with your new job as well. I wish you the best in your progress with the Galaxy S4. However, as a side note, do you think that it is possible to run with the previous phone, the Galaxy S3? I realize that this is really early in development to the point of troubleshooting the S4 to function at a basic level, but I am just curious if you think in the future the S3 could make do? I think you said in the first post that it sort of works, but do you think it could be better in the future or is the only hope upgrading to a S4? Any clarifications are appreciated.

Again, awesome job so far and all the best in the future .

Any phone that currently isn't an Adreno 320 device won't run Dolphin except with the videosoftware video backend. This limits the speed to completely unplayable levels, sub 1FPS on even the fastest devices. Pretty cool as a tech demo but from a usage standpoint, not worth it.

Even with the Adreno 320 phones, they require the absolute latest Qualcomm video drivers (version 14) to even work. Only the Galaxy S4 with the Snapdragon 600 chipset has these drivers at this point in time.

The next update that will be hitting the Play Store will be locked to only devices that support OpenGL ES 3 like the GS4.

Ouch, well hopefully in the future maybe something can be done for lower end phones. I own an S3, so I am out of the picture hehe. But, Either way, the fact that you are taking on such as task is still awesome. Best of luck once again .

(05-04-2013, 03:16 PM)Sonicadvance1 Wrote: [ -> ]Any phone that currently isn't an Adreno 320 device won't run Dolphin except with the videosoftware video backend. This limits the speed to completely unplayable levels, sub 1FPS on even the fastest devices. Pretty cool as a tech demo but from a usage standpoint, not worth it.

Even with the Adreno 320 phones, they require the absolute latest Qualcomm video drivers (version 14) to even work. Only the Galaxy S4 with the Snapdragon 600 chipset has these drivers at this point in time.

The next update that will be hitting the Play Store will be locked to only devices that support OpenGL ES 3 like the GS4.

So do previous snapdragon 600 devices like the DNA get the update? Also, you said the adreno 320 was estimated to have 70 gflops, and that that would be inadequate to play most games at full speed. However, I played wind waker as well as many old metroid games at full speed with a 9600gt that outputs only 34 gflops. Check here to see the gflops output of some older gaming cards: http://www.gpugrid.net/forum_thread.php?id=1150

GFLOPS is not the only way to calculate GPU power . By all mean , more GFLOPS doesn't make a GPU stronger than the others
For most games , an Intel HD 3000 or equivalent GPUs will do the job fine (with native-low resolution . Of course , GPU intensive games are out of the question)
9600GT is abit slower than my 9800GT but I'm sure 9600GT can handle 3x Internal Res (1920x1584) , no AA , 16xAF .There is no comparison here
http://forums.dolphin-emu.org/Thread-minimum-specs-video-card
And Android doesn't eat a lot of resources like Windows ...

Quote:9600gt that outputs only 34 gflops

Nope , 208.0 GFLOPS
http://www.techpowerup.com/gpudb/206/geforce-9600-gt.html
Although my GT 540M has more GFLOPS than yours but my GPU can only handle 2.5xIR (1600x1320) due to low memory bandwidth .

Those GFLOPS you linked are computational GFLOPS versus shader computational power as well. Completely different beasts.

Oops , you're right . I should check his link first