Performance issues on Verizon Galaxy S9+

[jcaubre]

I previously used a Snapdragon 835 GSM Unlocked Galaxy S8+ before picking up my new S9+, and using the Vulkan drivers and having the resolution at 720p, the emulator ran Twilight Princess and Wind Waker nearly flawlessly..... Now on the S9+ with the same settings, I'm lucky to get 20fps and there are black pixels covering the majority of the screen.

Just curious why this device is more powerful than the S8+ I was using previously, yet it runs horribly.

Just FYI... Here are the specs of the phone...

Verizon Galaxy S9+
Snapdragon 845
6gb RAM

Running Dolphin Version 5.0-6582

[JonnyH]

Please report driver bugs to your vendor.

(I know, it's not really a helpful thing to say, but there's pretty much nothing the dolphin devs can do to help, and samsung/qualcomm seem uninterested in fixing half this stuff. While I doubt 'one more' report would drastically change that, "good" bug reports and reproduction cases are always useful, and anything that can even slightly encourage fixes must be good... right?)

[sirio_yagamine]

(03-22-2018, 03:05 AM)jcaubre Wrote: I previously used a Snapdragon 835 GSM Unlocked Galaxy S8+ before picking up my new S9+, and using the Vulkan drivers and having the resolution at 720p, the emulator ran Twilight Princess and Wind Waker nearly flawlessly..... Now on the S9+ with the same settings, I'm lucky to get 20fps and there are black pixels covering the majority of the screen.

Just curious why this device is more powerful than the S8+ I was using previously, yet it runs horribly.

Just FYI... Here are the specs of the phone...

Verizon Galaxy S9+
Snapdragon 845
6gb RAM

Running Dolphin Version 5.0-6582

No dude you are totally wrong  you need to run dolphin with 5.0 1589 ...its the best built so far ,the other ones are just way to raw to use .it has nothing to do with power but rather with optimization 

Cheers 

[MayImilae]

On Android, older versions like that might be a little faster, but only because they are missing important emulation features. They'll be a lot buggier and much more unstable!

[Helios]

lmao.

[Whatnoww]

Unstable qualcomm drivers. That's why OEM's are so hesitant to update drivers once they find a relatively stable one.

[trihy]

I think one dolphin dev should do a text with proper bug reporting to qualcomm. They know better than us why it fails.

Then with that text we can spam the vendors.

[zxcvbad]

(03-28-2018, 01:03 AM)trihy Wrote: I think one dolphin dev should do a text with proper bug reporting to qualcomm. They know better than us why it fails.

Then with that text we can spam the vendors.

This days it's not just bugs to report (yes there are bugs like 32-bit depth buffer on Adreno vulkan driver that could be reported correctly including an example) but it's also lack of features in the drivers. Raising features with qcom or ARM never worked well unless you aren't their partner so they will never prioritize such requests. dualScrBlend was requested 3 years ago, buffer_storage raised 4? years ago with ARM, both isn't implemented.

[JonnyH]

(03-28-2018, 01:03 AM)trihy Wrote: I think one dolphin dev should do a text with proper bug reporting to qualcomm. They know better than us why it fails.

Then with that text we can spam the vendors.

That's not really the correct way to approach this - spamming hundreds of "me too!!!" reports to qualcomm will just get ignored. Internet slactivism never really solved anything - especially if it's aimed at the wrong place (probably most of the people you interact with on the internet are marketing based, and the few engineers don't want to wade through seas of spam to find useful info).

What could be useful is creating a good, cut down test case, showing the issue as simply as possible, and doing the sort of triage that otherwise an engineer would have to do - making this feature "more attractive" on the cost/benefit ratio by reducing their cost.

But this likely requires significant technical expertise*, and a good amount of time, and then no guarantee of a decent solution. There are currently do dolphin devs (I know of) who consider this sort of thing to be the most efficient (and most interesting - remember this is a volunteer project!) use of their limited time. Especially as that would mean pushing other bugs/features aside to make room.

* Or a lot of time and a willingness to learn