(12-13-2014, 06:49 AM)Gir Wrote: [ -> ]Phones are Phones, for Calling people, why would Processor manufacturers develops there chips to run demanding software like Dolphin, it's a waste to invest in Expensive ARM tablets for Dolphin, Dolphin is well optimized for Intel Processors, so wait for Skylake Windows Tablets.
I have a windows tablet that runs Dolphin just fine... Phones are not just phones, they do many of the things you would do from a computer now. The year is 2014, not 1999. Lets be realistic here, we all understand the limitations of our current devices, but that doesn't mean development for them should cease, that logic is backwards. I don't mean to insult your opinion but I don't feel it belongs here when the purpose of this entire thread/forum section is to discuss the Dolphin Android development progress. Nobody is wasting money to invest in Expensive ARM tablets for Dolphin, they are trying to run it on devices they already have.
I would like to request any further negativity be taken elsewhere so this topic can be kept on topic. Thank you
(12-13-2014, 07:06 AM)RyudoSama Wrote: [ -> ]they are trying to run it on devices they already have.
They really shouldn't for they will be disappointed, another issue, is that people using demanding software on there Tablets, will make there devices heat up, overheating can cause battery discharge.
(12-13-2014, 07:28 AM)Gir Wrote: [ -> ] (12-13-2014, 07:06 AM)RyudoSama Wrote: [ -> ]they are trying to run it on devices they already have.
They really shouldn't for they will be disappointed, another issue, is that people using demanding software on there Tablets, will make there devices heat up, overheating can cause battery discharge.
Overheating can cause battery discharge? That whole sentence makes no sense. Maximum thermal temps in ARM devices are easily below what would cause damage to a battery, not that "discharge" is even correct terminology. Dolphin is not pushing tablets any further than games would in terms of thermal and power strain, so statements like this are completely stupid. You sir are backwards, and frankly dolphin on android is an exploration in how far we can push common modern technology. Go back to your x86 desktop and leave us alone if you disagree, but coming in here and expecting anyone to give a @&$) about your baseless statements is stupid. Also, good luck running dolphin smoothly on those craptastic AMD specs.
(12-13-2014, 05:22 AM)Sonicadvance1 Wrote: [ -> ]Ah. I actually know what that issue is.
Adreno 4xx devices aren't being detected properly in our framework and it is attempting to use glBufferSubData which is broken garbage on Adreno.
I need to add the a4xx devices to our system to let it fall back to glBufferData.
Where should I keep an eye out for said change?
I have been checking
https://buildbot.dolphin-emu.org/builders/release-android
(12-13-2014, 05:12 AM)RyudoSama Wrote: [ -> ]Keeping to the topic of the thread, I did some extensive testing with this app and I love the progress being made thus far. I tip my hat to all of the developers that are working on it.
That being said, there appears to be a huge performance gap from the snapdragon 800 with adreno 330 compared to the snapdragon 805 with adreno 420. The emulator works better on the older snapdragon processors for some reason, and I would love to know why. I originally suspected the native display resolution of the note 4 2560x1440 being to blame but I wonder now if that is even the case.
Just as a side thought, is it possible to add directx11 as an option as well as opengl es 3.0 since that is supported by the note 4? Curious if that would make a difference at all.
The game I was testing with primarily was Smash Bros Brawl, which gets 14fps on the intro video, but for some reason as soon as the start button is pressed and the press start screen appears, the fps drops down to less than 1fps and gets stuck. I have noticed that the app appears to crash and causes android to close any other apps in what appears to be an attempt to free up memory for the app/game, possibly due to a memory leak? The note 4 comes with 3GB of ram which should be enough.
Any thoughts on how we can get this running, I am open to any suggestions and will test any changes anyone can suggest.
I just pushed a fix for Adreno 400, the large performance gap between Adreno 400 and Adreno 300 should be resolved.
(12-20-2014, 07:57 AM)Sonicadvance1 Wrote: [ -> ] (12-13-2014, 05:12 AM)RyudoSama Wrote: [ -> ]Keeping to the topic of the thread, I did some extensive testing with this app and I love the progress being made thus far. I tip my hat to all of the developers that are working on it.
That being said, there appears to be a huge performance gap from the snapdragon 800 with adreno 330 compared to the snapdragon 805 with adreno 420. The emulator works better on the older snapdragon processors for some reason, and I would love to know why. I originally suspected the native display resolution of the note 4 2560x1440 being to blame but I wonder now if that is even the case.
Just as a side thought, is it possible to add directx11 as an option as well as opengl es 3.0 since that is supported by the note 4? Curious if that would make a difference at all.
The game I was testing with primarily was Smash Bros Brawl, which gets 14fps on the intro video, but for some reason as soon as the start button is pressed and the press start screen appears, the fps drops down to less than 1fps and gets stuck. I have noticed that the app appears to crash and causes android to close any other apps in what appears to be an attempt to free up memory for the app/game, possibly due to a memory leak? The note 4 comes with 3GB of ram which should be enough.
Any thoughts on how we can get this running, I am open to any suggestions and will test any changes anyone can suggest.
I just pushed a fix for Adreno 400, the large performance gap between Adreno 400 and Adreno 300 should be resolved.
I am super excited, I just got home from work and have been checking like a fiend for the past few days, going to try it out now. I saw it pop up right before checking this forum. Thanks a ton!
Tested new push on my Note 4 Qualcomm version, on Android 4.4.4
Still does not run on OpenGL ES 3, all games have graphical errors to the point of unplayablity
Interpreter seemingly runs slower than on older versions
When your device gets Android 5.0 Samsung should be moving your video driver from version 84 to version 102 or 104. If they do get these updated video drivers then the graphical issues will be gone.
(12-20-2014, 09:21 AM)Sonicadvance1 Wrote: [ -> ]When your device gets Android 5.0 Samsung should be moving your video driver from version 84 to version 102 or 104. If they do get these updated video drivers then the graphical issues will be gone.
I came up with pretty much the same test results, but I am still extremely happy with the fact that it is at least meeting my expectations now for this hardware. I definitely look forward to the updated drivers baked into the 5.0 Kernel.
It really astonishes me how fast technology evolves, I never would have imagined cell phones playing gamecube/wii games, but it is truly right around the corner. Good times.
I am really suprised how well the devs are doing with optimizing this emulator - the current dev build is smoother on my note 4 and much more stable - this is really coming along I have also noticed much less throttling too if it wasnt for adrenos broken drivers then i would label some games as playable on this device