Ok so let's discuss Vulkan API, the next generation for gaming.. It is believed to be implemented already in Nougat, but I have yet to see the actual effects in game (NFS, HIT, Vainglory, etc..)
And in HIT (heroes of incredible tales), it says phone does not support Vulkan API yet.
So which is it, did they exclude the Vulkan API in the updates that was delivered to us, or am I missing something here?
There's still a lot of devices, that are stuck in Marshmallow and below, it will be long while before the Vulkan API will be the defacto Graphics API for the devs. Until then, we are stuck using the Slow Open-GL ES
Vulkan appears to be there, Dolphin Emator uses it. It appears a bit buggy right now but that's probably the Emulators fault. Vulkan definitely implemented.
damiensturdy said:
Vulkan appears to be there, Dolphin Emator uses it. It appears a bit buggy right now but that's probably the Emulators fault. Vulkan definitely implemented.
Click to expand...
Click to collapse
How can you be sure that dolphin emulator uses it though? Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Vulkan example works so I think Vulkan is working.
Vulkan on Dolphin emulator is working too.
I sent an email to the developer of Heroes of Incredible Tales (HIT) 2 weeks ago and according to them not all device are supported by Maximum graphics yet which I believed the Vulcan, anyway my brother's Xperia XZ with Nougat update can't set the settings to max either.
Freyelis said:
How can you be sure that dolphin emulator uses it though? Thanks
Click to expand...
Click to collapse
Because you get different results when you switch.
I could explain it to you with a long conversion... but you have a OnePlus don't you? Why not just try it for yourself?
Freyelis said:
How can you be sure that dolphin emulator uses it though? Thanks
Click to expand...
Click to collapse
Because when Vulkan doesn't exist, Dolphin says it doesn't exist. (OOS 3), then when it does, it works (OOS 4), and you get an image. It's also significantly faster when using Vulkan. Hopefully it'll stay that way when they iron out the visuals.
https://play.google.com/store/apps/details?id=com.superevilmegacorp.game.vulkan
https://play.google.com/store/apps/details?id=de.saschawillems.vulkancapsviewer
Vulkan is present but not the whole API or be it a older version. It's baked into the core of Nougat so I guess with newer Android versions we will see more features etc.
Hi' i'm using google pixel c (tegra x1) and on latest nougat build (7.1.2) dolphin can't run on vulkan api (all is black on screen). On android O betâ 3 it runs perfectly on vulkan api and for example zelda Twilight princess on open gl api is laggy (less 20 fps) but in vulkan api i have all the time 30 fps ^^
Related
Hey guys, I know you've seen a lot of some emulators on the Play store, for all kind of old-school consoles, NES, SNES, N64... Most of them are released under GPL license, so yes, they are open source. Sadly, the UI design doesn't match with Android's holo (4.0+) style. So, my proposal is simple. Let's develop a couple of free, open source emulators, from XDA members, with a proper UI (I can help with that, I've written a couple of modern looking apps: LockIt, wRotatr, Halo)))). My weak point is JNI. I hate it. Period. I will need a lot of help to get the emulators buiding, but after I get them, you will see a lot of UX/UI improvements.
Sources can be found here. I'd like to start with Nesoid. So, is anybody here, expert on JNI development, willing to help me on this? :good:
Cheers,
D4.
Bumping this, I have archieved some UI fixes. Still not able to build native libraries.
Before
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After
The sad news is that I dropped android < 4.0.3 support
Any news on your progress?
Shadow-Nexus said:
Any news on your progress?
Click to expand...
Click to collapse
I haven't been able to build native libraries yet. Without that there's no emulation
How's the emulation overhaul coming along? Seems like a great project
Sent from my Nexus 7 using XDA Premium 4 mobile app
worhello said:
How's the emulation overhaul coming along? Seems like a great project
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm trying another UI attempt, but it's not yet working (emulation still broken, I haven't found anyone to help me with JNI)
Abandoned
I got a Veer laying around doing nothing, but since its pretty small I was thinking about installing AW on it. There were a couple android builds for it an it ran wheel but the small screen made it a pain to use. The problem here is getting AW to work on it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It has a snapdragon S2 MSM7230 and 512MB of RAM which is not that far from the Gwatch, maybe I could use a build from that one?. Problem could be the screen which is 320 x 400 pixels, while all the other AW watches have a 1:1 ratio with resolutions of 280x280 or 320x320.
I don't expect the qwerty keyboard to work but I would like the mic and speaker so I can write messages and stuff. I think it had NFC but I don't know if that and cameras are supported by AW yet.
Anyone got a Veer too? you can pick one for next to nothing.
MGREX said:
I got a Veer laying around doing nothing, but since its pretty small I was thinking about installing AW on it. There were a couple android builds for it an it ran wheel but the small screen made it a pain to use. The problem here is getting AW to work on it.
It has a snapdragon S2 MSM7230 and 512MB of RAM which is not that far from the Gwatch, maybe I could use a build from that one?. Problem could be the screen which is 320 x 400 pixels, while all the other AW watches have a 1:1 ratio with resolutions of 280x280 or 320x320.
I don't expect the qwerty keyboard to work but I would like the mic and speaker so I can write messages and stuff. I think it had NFC but I don't know if that and cameras are supported by AW yet.
Anyone got a Veer too? you can pick one for next to nothing.
Click to expand...
Click to collapse
I'd be interested on Android Wear on the HP Veer too!
I love my veer from the first sight and If there would be a whatsapp messenger, I would use it forever.
So please, let it happen!!!
http://forums.webosnation.com/hp-veer/328606-android-veer-rooted-play-store-etc.html
It appears work has been done to put Android on the Veer. Now, the real question is, how recent a build can we load? 4.4 full only asked for 512MB of RAM, apparently, so the possibility of running Wear is more than likely, given even now, most of the popular Wear watches still use 512 (with only the ones with a mobile radio asking for 768MB).
This is also noting some existing ROMs. There was Quattrimus CyanogenMod 9 which basically got ICS to work on a variety of low-end LG devices, with only 256MB of RAM. So if you can get a source of AW and just work with some of the drivers on the Veer, it should be possible to patch things up and get most everything working.
A few curiosities though...
Does AW require Bluetooth 4.0 LE? Would it be able to use the wi-fi for Cloud Sync? Would AW be able to run low energy enough for the Veer? Is the chipset efficient enough to do it?
the new version was to be distributed 32.3.A.0.376 http://i.hizliresim.com/l3nZmJ.jpg
Finally
Ota in Indonesia, dual sim version
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my E6883 using Tapatalk
not yet my phone
Indonesia pulled out early
Let's see how does it taste
I could not find the pain i am currently everything perfect smooth
https://forum.xda-developers.com/z5...eria-z5-z5p-variants-drm-keys-t3437902/page16 ......... I as described here was the root
Fingerprint doesnt work |:
I works. It works when you turn it off with the button.
Does anyone have a problem using romu I did not see anything.How the battery situation seemed a little less to me.
I have a vision about the rom I use it as if the charge came as a bit distressed.
Do not have the opinion about rom
Please Help!!! In new update Sony make four A57 cores completely disabled even when stamina is off!!! In addition opengl es is 3.1 and they didnt improve opengl es to 3.2 version but htc m9 and nexus 6p that use the same hardware improve to 3.2 version in android 7!!!
Please test new android !!! Please test it!!! They completely ruined the performance of z5 serries in gaming with disabling 4 cores of cpu!!! We had no heat and battery issue in MM I cant understand why they disable 4 cores??!!! Helpme!!!
uri2010 said:
Please Help!!! In new update Sony make four A57 cores completely disabled even when stamina is off!!! In addition opengl es is 3.1 and they didnt improve opengl es to 3.2 version but htc m9 and nexus 6p that use the same hardware improve to 3.2 version in android 7!!!
Please test new android !!! Please test it!!! They completely ruined the performance of z5 serries in gaming with disabling 4 cores of cpu!!! We had no heat and battery issue in MM I cant understand why they disable 4 cores??!!! Helpme!!!
Click to expand...
Click to collapse
this was already discussed in sonymobile forum. they did not disabled the 4 cores.
use different app. please try to google first before asking for help.
http://talk.sonymobile.com/t5/Xperia-Z5-Z5-Compact-Z5-Premium/CPU-Limit-on-nougat/m-p/1200021/highlight/true#M30569
Without stories and complains:
This libraries enable OpenGL 3.2/Vulkan Api for Adreno 510 GPU, is fully based on Xperia XZ libraries and works ONLY on Nougat (7.x.x) Roms (Some people can try on Aosp 8.0.0 too, no problem )
Code:
Disclamer:
[COLOR="YellowGreen"]
#Ain't my responsibility if your device cause another world war, burn as hell or boot nevermore.
I suppose, you'll should know what are doing with your phone and life here.
If you aren't sure, close the post and go away safe or search: Best Android device ever in Google :D[/COLOR]
[SIZE="5"][COLOR="Red"] This doesn't help to increase points on Benchmarks like Antutu, Geekbench or 3DMark,
haven't effect[/COLOR][/SIZE]
Features
- VR Support (If rest of Hardware is available).
- Smooth in Vulkan API Games (Almost all on 30fps).
- Some shades fixes (For Xperias devices).
Game List With Vulkan Support
GRID Autospot.
Vanglory.
The Talos Principle.
Score! hero.
Need For Speed: No Limits.
Heroes of Incredible Tales.
Dream League Soccer.
Olimpus Rising.
Galaxy on Fire 3.
Supported (and Tested) Devices
Sony Xperia X.
Sony Xperia X Compact.
Xiaomi Redmi Note 3 (Snapdragon).
Xiaomi Mi Max.
Samsung Galaxy C9 Pro.
HTC 10 Lifestyle.
And possibly all Adreno 5xx devices (IDK, really).
Requirements
Rooted device on Stock, Aosp or Custom Rom based on Nougat, TWRP (Or custom recovery for your device).
Screenies
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to Install
Put in Internal or External Memory
Go to Recovery
Install Zip
Wait the process finish
Enjoy
Download
Mega Link
GDrive Mirror
Credits
@MEGAX91 (For Xiaomi Mi Max to Redmi Note 3 Port).
@Sudeep Duhoon (For the idea to make this port for Xperia SD650 devices)
@Sony Mobile (For OpenGL 3.2 Libraries)
@sebasrock156 (For make this possible).
Is this going to increase game ad overall performance of the device?
kloroform said:
Is this going to increase game ad overall performance of the device?
Click to expand...
Click to collapse
Not exactly, but, it should "increase" some frames per second in some games.
I was testing this in games like GTA: San Andreas, and run from 50fps (Stock, without enable "Limited Frames per Second" option), to 55~60fps (With OpenGL Drivers), in another games like NFS: No Limits, isn't visible that "increase" (Stock and With Drivers, works to 30fps).
Not functioning in both PSP and dolphin emu. crash when I select vulkan try to run super Mario sunshine,PSP also same performance both opengl and vulkan,lame
lambha48 said:
Not functioning in both PSP and dolphin emu. crash when I select vulkan try to run super Mario sunshine,PSP also same performance both opengl and vulkan,lame
Click to expand...
Click to collapse
Is for HW limitations (Remember: Part of this, is ported from Adeno 530 GPU).
Hey people!
Since the S6 has quite a limited amount of RAM (for this decade!), would be it more useful to have an Android Go port instead of full-fat AOSP, or even Pixel ports?
I'm no developer and I don't even know much about Android Go so please explain/tell me why this hasn't been done. I'm sure a lot of people have thought of this before but there must be reasons that it's not come into existence, yet.
Thank you sooo much!
A random image from Google Search, just for fun.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Opteronvoz said:
Hey people!
Since the S6 has quite a limited amount of RAM (for this decade!), would be it more useful to have an Android Go port instead of full-fat AOSP, or even Pixel ports?
I'm no developer and I don't even know much about Android Go so please explain/tell me why this hasn't been done. I'm sure a lot of people have thought of this before but there must be reasons that it's not come into existence, yet.
Thank you sooo much!
A random image from Google Search, just for fun.
Click to expand...
Click to collapse
I don't really see a point as to why would anyone make an Android Go ROM for the Galaxy S6 Edge. The 7420 is still really capable enough to run modern versions of Android like A12 or A13 given the right optimisation and patches.
In addition to that, Android Go is just NikGapps Go on top of an AOSP build
ArmashOnXDA said:
I don't really see a point as to why would anyone make an Android Go ROM for the Galaxy S6 Edge. The 7420 is still really capable enough to run modern versions of Android like A12 or A13 given the right optimisation and patches.
In addition to that, Android Go is just NikGapps Go on top of an AOSP build
Click to expand...
Click to collapse
I'm sorry but I didn't say anything about processing power though.
They should introduce a similar feature like RAM Plus on One UI for LineageOS Devices. With that, even the S6 would have no RAM issues in the upcoming years
Exynos 7420 in general is too strong, still going great these days. It just missing the right optimizations for AOSP roms, I bet it could handle A11 or A12 good. The current LOS 19.1 (A12) is currently in development, it still run ok, but because the HWC is broken so yeah.