Related
This is the generic GPU drivers for adreno GPU found in snapdragon chipsets by Qualcomm.
Although this will not magically make your GPU fast, updated drivers will fix bugs and show improvements all round.
Thanks to @denzel09 who has repacked the may binaries with correct path for Moto G.
Download Link
http://www61.zippyshare.com/v/59501646/file.html
Stock 4.4.4 Adreno drivers (those who wants to go to default)
http://www72.zippyshare.com/v/11705987/file.html
B]Changelogs[/B]
Changelogs for August
@lost101 has posted changelog
Known Issues:
Applications may hang when repeatedly disconnecting and reconnecting Adreno Profiler while plotting GPU Stall Metrics in Grapher.
Capturing OpenCL metrics with Adreno Profiler Scrubber may crash target application.
Fixes and Improvements:
Fix a failure to release performance counter resources in some cases when using Adreno Profiler with certain NDK apps and OpenCL.
Fix a crash when connecting Adreno Profiler to an app that uses the disjoint timer query extension.
Add support to Adreno Profiler for OpenCL kernel type qualifier arguments.
Add support to Adreno Profiler for clCreateImage() 1D image, 1D image array, 2D image array.
Add support to Adreno Profiler for displaying multiple OpenCL queue/device/context combinations.
Fix a potential target application crash when Adreno Profiler metrics are enabled while the GPU is not idle.
Fix for incorrect scissor results if an app calls scissor and glBufferSubdata() between two draw calls.
Fix an issue with binning configuration calculation when MSAA is enabled.
Add support for ASTC texture formats in Adreno Profiler.
Fix potential null-pointer dereference in OpenCL.
Fix rotation issues with glBlitFramebuffer() and glClipPlane() when device is not in native orientation.
Fix for possible crash when using occlusion query while changing render targets.
Fix incorrect Adreno Profiler capture for applications using 2D texture arrays.
Fix potential crash during VAO validation in buffer update calls.
Add Adreno Profiler support for buffer transmission in clFillBuffer() and clFillImage().
Improve performance when invalidating texture attachments.
Click to expand...
Click to collapse
Tested working on[/B]
XT1033 with stock ROM
XT1032 with stock ROM
XT1031 with Stock ROM
Custom ROM people should report back
abhifx said:
The nexus 4 forum is buzzing with new Qualcomm adreno drivers .
Dont know if this is working with Moto G. Maybe a dev can look into it.
also someone has posted zip files for F2FS partition.
thoughts? Link to the post is as below
http://forum.xda-developers.com/nexus-4/general/qualcomm-adreno-gpu-binaries-t2667759
Click to expand...
Click to collapse
This works also on adreno 305?
About f2fs, we have only data in f2fs but i think that these will be in system...
denzel09 said:
This works also on adreno 305?
About f2fs, we have only data in f2fs but i think that these will be in system...
Click to expand...
Click to collapse
since Adreno 305 has feature parity with 320, i was hoping that the same driver should work. i right now cant check this unless i am near my home system.
abhifx said:
since Adreno 305 has feature parity with 325, i was hoping that the same driver should work. i right now cant check this unless i am near my home system.
Click to expand...
Click to collapse
mmm i have some doubt, but i hope ..
abhifx said:
since Adreno 305 has feature parity with 320, i was hoping that the same driver should work. i right now cant check this unless i am near my home system.
Click to expand...
Click to collapse
I installed it. Can't see anything untowards. Antutu about the same result.
lmulli said:
I installed it. Can't see anything untowards. Antutu about the same result.
Click to expand...
Click to collapse
see the zip, i don't think that paths are the same
denzel09 said:
see the zip, i don't think that paths are the same
Click to expand...
Click to collapse
Guys, it seems download link is dead. Can someone re-upload it ?
@denzel09: what do you mean paths are not the same ? Drivers are in different location in moto G ?
Cheers.
Yes they are in different location. You can see them with root explorer.
Can U plz upload zip somewhere? Original link is not working :-/
Sent from my XT1032 using xda app-developers app
Update.
I repacked the zip with correct folders paths.
Last april version.
To verify install osmonitor from PS, go to message tab and see about adreno build date.
http://www39.zippyshare.com/v/58174828/file.html
Tested only on xt1032.
is there any difference after installing it?
No changes in antutu with this new libraries
When you update your nvidia/amd drivers in your pc you will go always to test them with an antutu-like software ? It's not a good point to start i think. If you see the changelog you ll see how many bugfixes i.e., improvements and so on. Drivers should be always updated by the way.
denzel09 said:
When you update your nvidia/amd drivers in your pc you will go always to test them with an antutu-like software ? It's not a good point to start i think. If you see the changelog you ll see how many bugfixes i.e., improvements and so on. Drivers should be always updated by the way.
Click to expand...
Click to collapse
Are you sure this update isn't just for 320 and 330? I'm gonna flash it, I'll report if I notice any difference
Yes, officially only for that i think.
But remember that you can restore a system backup or in next days i can make the same zip with previous older stock drivers
Well, I don't know if it is a placebo or what, but the phone feels actually a little bit responsive and with smoother animations, just that, I'm not saying that it will be a super performance boost though.
denzel09 said:
Yes, officially only for that i think.
But remember that you can restore a system backup or in next days i can make the same zip with previous older stock drivers
Click to expand...
Click to collapse
I can notice the difference
The boot lag bug has reduced (phone lags for a minute in latest cm builds)
Phone is a bit more responsive
Sent from my Moto G using Tapatalk
I am considering flashing these but I still would like some more feedback. Anyone else did it that could contribute with their experience?
Flashed on xt1031. Nothing is broken I am thinking that the content inside of the apps is loading a little quicker such as UI elements. This could be placebo though. As far as antutu goes, no changes really except I saw a new highest FPS in the 3D test I got a 27.8 at one point, which I have never seen.
Sent from my XT1031 using Tapatalk
It was bound to happen, so here it is. The Grouper running Android 6.0!
What works:
- WiFi
- display
- audio
- Bluetooth (partially)
- Multiwindow
- Auto-rotate
What's broken:
- OTG
- surfaceflinger*
What's untested:
- camera
- NFC
I will not offer a ROM zip at this point due to the fact that the rootfs is inherently insecure for the time being. However, the sources are available below and should be bootable.
Sources:
http://github.com/Grouper-aosp
CREDITS:
@dolorespark - ramdisk fixes, sepolicy fix (3.1 compatible)
@Ziyan - kernel work and device tree
@GtrCraft - device tree help, testing and support
I highly encourage the use of the stock 3.1 kernel. I've modified sepolicy to allow old kernels to run.
Wow ☺
what does it mean, broken surfaceflinger*?
Thanks dude! Will try to flash when rom is linked and when I can access my Nexus 7!
TheXorg said:
what does it mean, broken surfaceflinger*?
Click to expand...
Click to collapse
For some reason, surfaceflinger isn't looking in the /system for the GPU binaries. To bypass this I had to symlink them to the rootfs.
Wow. Though, it would be great if anyone -- or the OP -- could cook the ROM and share the link. Looks good enough.
itskapil said:
Wow. Though, it would be great if anyone -- or the OP -- could cook the ROM and share the link. Looks good enough.
Click to expand...
Click to collapse
A link will be posted as soon as we fix Surfaceflinger and a couple bugs in the 3.4 kernel.
@Motorhead1991 thanks a lot for the heads up! Waiting patiently.. pls tag once it's up. :good:
Having done this already, let me add:
most likely also you have gps broken, and nfc broken
i am guessing selinux is also not doing all it should
also the issue is not with surfaceflinger (that is just the symptom)
I was hoping someone could port 6.0 to this device. Waiting for the OP to show ready to rock and roll !
@Motorhead1991 awesome work @dmitrygr saw a reddit post where you said you are working on nexus 7.... patiently waiting for it after trying your nexus 4 build
2012katas said:
@Motorhead1991 awesome work @dmitrygr saw a reddit post where you said you are working on nexus 7.... patiently waiting for it after trying your nexus 4 build
Click to expand...
Click to collapse
Other way around, friend . @dmitrygr did the N4. I started on the N7 (2012) myself and received assistance from him and others .
Excellent work! I'll be watching this with interest.
Thanks! I'm waiting for your release
Camera, NFC and OTG is not important for me right now.
dmitrygr said:
Having done this already, let me add:
most likely also you have gps broken, and nfc broken
i am guessing selinux is also not doing all it should
also the issue is not with surfaceflinger (that is just the symptom)
Click to expand...
Click to collapse
For NFC, we need to revert this commit - adding it to the device tree is way too problematic, and this shouldn't cause problems for other devices anyways....
For SELinux on 3.1, we need these commits, and we need to remove three recovery-related neverallowed rules from the device tree (not a huge deal really) - these commits are already included in my 3.4 kernel (thanks to the android-3.4 merge), but it's not ready to be shipped... posting a screenshot of M running with 3.4 was a mistake.
For EGL, I use this workaround, which fixes that particular problem without modifying the system libraries - it would be really nice if you knew another, nicer solution, also without modifying the system libraries
Right now, GPS, camera and audio is broken (thought audio might be broken because of camera - I experienced similar symptoms while working on 3.4).
dmitrygr said:
Having done this already, let me add:
most likely also you have gps broken, and nfc broken
i am guessing selinux is also not doing all it should
also the issue is not with surfaceflinger (that is just the symptom)
Click to expand...
Click to collapse
The NFC propably needs the NXP NFC stack which had been dsiabled building by google and can be reverted: https://gerrit.omnirom.org/#/c/14956/
My Optimus G needed relocations for the nfc hardware lib, but I think it might be not needed, anyway this is hacky change to make relocations warnings again: https://gerrit.omnirom.org/#/c/14955/
Ziyan said:
For NFC, we need to revert this commit - adding it to the device tree is way too problematic, and this shouldn't cause problems for other devices anyways....
For SELinux on 3.1, we need these commits, and we need to remove three recovery-related neverallowed rules from the device tree (not a huge deal really) - these commits are already included in my 3.4 kernel (thanks to the android-3.4 merge), but it's not ready to be shipped... posting a screenshot of M running with 3.4 was a mistake.
For EGL, I use this workaround, which fixes that particular problem without modifying the system libraries - it would be really nice if you knew another, nicer solution, also without modifying the system libraries
Right now, GPS, camera and audio is broken (thought audio might be broken because of camera - I experienced similar symptoms while working on 3.4).
Click to expand...
Click to collapse
In hindsight, yeah showcasing 3.4 was jumping the gun a little bit. I just got ahead of myself and wanted to bring hope to people that still use such an "old" device.
Update: I was able to fix gps in a similar way. Also, it seems like 3.1 + M isn't going to play together (serious memory management issues), so I had to switch back to 3.4 (me and @sheffzor are working on 3.4 day and night). So, only camera and audio remains
Sweet! @Ziyan, @sheffzor and all the other devs for the win!
Hello there, I've been working on this for a few days and I thought I'd finally show it off!
Please note that there is absolutely no graphics, only console output! Also, it's not very fast (only runs at 15fps on a SD625) and it only runs old homebrew (e.g. first libtransistor tests and such).
Discord support: https://discord.gg/fn8VV9T
Source code: https://github.com/Cyuubi/MonoNX
Credits:
Ryujinx Team - For the base of MonoNX, without them this would not be possible! Show them some love over at their GitHub (https://github.com/Ryujinx/Ryujinx).
Xamarin - For allowing us C# developers to program on Android.
Dr.Hacknik - Logo design.
Requirements:
An ARM64 or 64-bit x86 processor
NOTE: If you get a ROM load error, close out of MonoNX and go into app info and turn on and off storage permissions. This should fix the issue.
App download: https://play.google.com/store/apps/details?id=com.cyuubiapps.mononx
Test ROM download: https://drive.google.com/open?id=1cVa5BDn1w6FNb6QEKmch2m6k67t_q5c_
Interesting, I'll be looking forward this project. Thanks.
Great work , but can't load rom.
Pankaj Rai said:
Great work , but can't load rom.
Click to expand...
Click to collapse
NOTE: If you get a ROM load error, close out of MonoNX and go into app info and turn on and off storage permissions. This should fix the issue.
Very nice, BUT, I have a very important question.
Do you use on aarch64 target devices dynamic recompilation or you execute directly the code?
If not, would you mind to give an insight?
VIRGIN KLM said:
Very nice, BUT, I have a very important question.
Do you use on aarch64 target devices dynamic recompilation or you execute directly the code?
If not, would you mind to give an insight?
Click to expand...
Click to collapse
Sadly, Hypervisors aren't really possible on Android from Xamarin... So we translate ARM64 -> MSIL/CIL -> ARM64, this is quite a hackjob but it works however it kills performance. MonoNX also works on 64-bit x86 processors, so the same thing works for this.
Toggling the storage permission back and forth changes nothing for me.
Sent from my crosshatch using XDA Labs
Cyubii said:
Sadly, Hypervisors aren't really possible on Android from Xamarin... So we translate ARM64 -> MSIL/CIL -> ARM64, this is quite a hackjob but it works however it kills performance. MonoNX also works on 64-bit x86 processors, so the same thing works for this.
Click to expand...
Click to collapse
Hmm, that still sounds though like something that CAN be tackled among the line.
Like what if somebody would switch (no pun intended, hahahaha) the codebase to Firebase?
UPDATE: Apparently it works with under 4GB RAM. (probably using swap though)
Hello, the app force close for me (test rom and snake homebrew). I can not launch anything. I tried turn on and off. Doesn't help.
Here's what I get when I load the test ROM.
EDIT: The emulator closes shortly afterwards. I have a OnePlus 5 with Android 9.0.3.
Hope upcoming updates soon.
Can you support google pixel c? The same soc as switch!
Maybe the adaptation speed will be faster
I hope I can play D3 on my phone soon
[email protected] said:
Can you support google pixel c? The same soc as switch!
Maybe the adaptation speed will be faster
Click to expand...
Click to collapse
Yeah then the games can run natively therefore no need for emulation. I would actually buy a pixel C over a switch if it can work. Also what about nvidia shield tv that can run mario galaxy at 1080p
So? Where we can find roms for this emulator?
Cyubii said:
NOTE: If you get a ROM load error, close out of MonoNX and go into app info and turn on and off storage permissions. This should fix the issue.
Click to expand...
Click to collapse
Tried not working , btw m using oneplust 3T (Aarch64)
nintendobuster420 said:
Yeah then the games can run natively therefore no need for emulation. I would actually buy a pixel C over a switch if it can work. Also what about nvidia shield tv that can run mario galaxy at 1080p
Click to expand...
Click to collapse
Any site to download roms from?
What do you think should be the minimum requirements for an Android device to play resident evil 7 using this emulator, considering RE7 is a cloud game for Nintendo switch?
Also, I found its rom whose size is about 40 MB (YES, 40MB).
Only 3 games playable as I see the base project. Need some time but waiting for D3
I noticed a new option in the developer options for OOS 10 called Game Driver Preferences. Anyone have a clue what this does? Coming from someone who games a lot on PC, I've never heard of being able to just swap drivers on the fly (without having to uninstall anything)
I just ran 3DMark Slingshot Extreme, both the Vulkan and OPENGL versions under both the system graphics and the game driver and got absolutely 0 difference in scores.
It's probably for upcoming devices that support multiple GPUs, one for heavy task such as gaming and another for lighter tasks. It does nothing on OnePlus 7 Pro.
Or, it's for Vulkan/OpenGL driver switching for devices that support it. I have no idea, just thinking out loud.
Is there a way to set your device to render stuff using Vulkan only
I've been trying to do this for a while and yesterday found a method but it uses magnetar which interferes with CPU and GPU Freq which i don't like and there is no way to turn it off
Is there anything else I can do to get Vulkan enabled?
i dont think thats good cuz vulkan on android is very outdated and most app didnt support it yet
Guan Yu said:
i dont think thats good cuz vulkan on android is very outdated and most app didnt support it yet
Click to expand...
Click to collapse
Thanks for your reply,
I know Vulkan on Android is not the best but it is superior to OpenGL in games that support it (new Android Games e.g Genshin Impact, Apex Legends Mobile)
also found out how to enable it thanks!
BR4UTAL said:
also found out how to enable it thanks!
Click to expand...
Click to collapse
how ?
Guan Yu said:
how ?
Click to expand...
Click to collapse
I used adb shell to do it but you can use edit build.prop too
for shell the cmd would be
setprop debug.hwui.renderer=vulkan
for build.prop just add a line
debug.hwui.renderer=vulkan
but there is a problem incase your rom doesn't support it, it'll auto disable itself like pixel experience plus didn't work sadly...
still searching a better way (which does not use magnetar)
Is Samsung ok?