Does anyone else get input lag (that lasts for a few minutes to hours) each day?
Every day (most of the time at around the same time) I'll get horrible input lag that will last from a few minutes to hours that will make the button presses on the remote take 3+ seconds just to register and execute on the Fire TV.
I sideloaded an app to check the CPU usage and it doesn't seem like there is any major CPU usage when I'm experiencing input lag.
This is a very annoying problem with my Fire TV and I'm not sure if other people experience the same problem.
If you have root access,you can use Trickster Mod after installing busybox to increase GPU performance by setting the Govern to performance.
This will partially overclock it to always run 400Mhz instead of going down to lower values which causes inconvenient lags.
I managed to get extremely fast performance after enough consecutive hours of on-time.
You could also get Kernel Tuner to make sure all four CPU cores are enabled and at the proper .384-1.7 settings.
My CPU0 was strangely disabled with the maximum clock on zero but I enabled the core by sliding it to 1.7 where it should actually be.
There is some hidden buttons on the main screen for turning CPU1,2,and 3 on/off you can find with the arrow keys.
You can also set your color bit depth to 32bit or 16bit while 24bit is the default for some reason.
Mine runs perfectly fine on 32bit and it appears to look much sharper.
Why is the default set to 24bit when 32bit works fine and looks better?
retroben said:
If you have root access,you can use Trickster Mod after installing busybox to increase GPU performance by setting the Govern to performance.
This will partially overclock it to always run 400Mhz instead of going down to lower values which causes inconvenient lags.
I managed to get extremely fast performance after enough consecutive hours of on-time.
You could also get Kernel Tuner to make sure all four CPU cores are enabled and at the proper .384-1.7 settings.
My CPU0 was strangely disabled with the maximum clock on zero but I enabled the core by sliding it to 1.7 where it should actually be.
There is some hidden buttons on the main screen for turning CPU1,2,and 3 on/off you can find with the arrow keys.
You can also set your color bit depth to 32bit or 16bit while 24bit is the default for some reason.
Mine runs perfectly fine on 32bit and it appears to look much sharper.
Why is the default set to 24bit when 32bit works fine and looks better?
Click to expand...
Click to collapse
Won't this cause the FTV to overheat? I'm thinking about doing this myself, but wouldn't want to cause any premature damage for a slight increase in performance.
The GPU is not far from max when set to normal mode.
It would usually stick around 320Mhz while occasionally going up to 400Mhz.
The heat has not been much different with performance mode keeping the GPU at 400Mhz.
Don't mess with the Quad-Core CPU modification,because that is the main thing that might overheat you.
I keep mine completely on default apart from enabling that one strangely disabled CPU core.
Out of 212F possible degrees,Trickster Mod's Temperature Info reads out 120F right now after quite a few hours of usage while the "battery" says 86F.
retroben said:
The GPU is not far from max when set to normal mode.
It would usually stick around 320Mhz while occasionally going up to 400Mhz.
The heat has not been much different with performance mode keeping the GPU at 400Mhz.
Don't mess with the Quad-Core CPU modification,because that is the main thing that might overheat you.
I keep mine completely on default apart from enabling that one strangely disabled CPU core.
Out of 212F possible degrees,Trickster Mod's Temperature Info reads out 120F right now after quite a few hours of usage while the "battery" says 86F.
Click to expand...
Click to collapse
Ok thanks I'll give it a try.
I also recently acquired two nice apps that use root to customize settings for a major performance boost in general and with "touch" related performance as well.
I have noticed a smoother touch scroll in browsers,faster menus,and app loading speeds.
The two apps are called Performance Booster and Digitizer Booster.
Performance:
https://play.google.com/store/apps/details?id=com.gejos.android.performancebooster
Digitizer Booster (responsive touch):
https://play.google.com/store/apps/details?id=com.gejos.android.digitizerbooster
There is also some donate and pro versions of Performance Booster that allow double boost and triple boost.
retroben said:
If you have root access,you can use Trickster Mod after installing busybox to increase GPU performance by setting the Govern to performance.
This will partially overclock it to always run 400Mhz instead of going down to lower values which causes inconvenient lags.
I managed to get extremely fast performance after enough consecutive hours of on-time.
You could also get Kernel Tuner to make sure all four CPU cores are enabled and at the proper .384-1.7 settings.
My CPU0 was strangely disabled with the maximum clock on zero but I enabled the core by sliding it to 1.7 where it should actually be.
There is some hidden buttons on the main screen for turning CPU1,2,and 3 on/off you can find with the arrow keys.
You can also set your color bit depth to 32bit or 16bit while 24bit is the default for some reason.
Mine runs perfectly fine on 32bit and it appears to look much sharper.
Why is the default set to 24bit when 32bit works fine and looks better?
Click to expand...
Click to collapse
Hey Retroben,
Can you do a posting with all your tips in the forum? your tips have greatly helped me out. Im sure many will greatly appreciate the performance boosts you helped us get.
I got to gather my findings before I can,but I'll see what I can do.
The major speed increase with GPU Govern set to "performance" while 400Mhz is my biggest accomplishment of findings.
I will need to devise a series of steps for each of my findings,so it might take a long while.
The 32bit Color Depth does seem a lot more vibrant and crisper than 24bit.
If anyone is curious, I found out that having a controller plugged in can cause the random input lag.
Someone had mentioned that on another website so I unplugged my xbox controller from the Fire TV and I haven't had any input lag since then.
retroben said:
Performance:
https://play.google.com/store/apps/details?id=com.gejos.android.performancebooster
Digitizer Booster (responsive touch):
https://play.google.com/store/apps/details?id=com.gejos.android.digitizerbooster
There is also some donate and pro versions of Performance Booster that allow double boost and triple boost.
Click to expand...
Click to collapse
I'm curious about what these apps actually do. The dev won't say; it looks like a lot of it build.prop style tweaks but I'm not sure if it's directly editing the file or adding a loadable script someplace.
On the 24 vs 32 bit color: it's not clear to me that for a TV screen, there's an advantage to 32 bit color. There will be a performance improvement in graphics, as the GPU is calculating many fewer bits per pixel.
The 8 bit and 24 bit images in the Wikipedia article are pretty interesting to look at on a display. I'm surpised by how similar they are on my computer display at its normal 32 bit resolution:
8 bit
{
"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"
}
versus 24 bit
An excellent interactive comparison of bit depths is at
http://www.cambridgeincolour.com/tutorials/bit-depth.htm
IF I can extract the tv from the teenager anytime soon, like tomorrow, I'll look at that cambridge image on the set as well. On the computer, at 16 or 32 bit, the difference in appearance of the last two images in it is very subtle.
retroben said:
I got to gather my findings before I can,but I'll see what I can do.
The major speed increase with GPU Govern set to "performance" while 400Mhz is my biggest accomplishment of findings.
I will need to devise a series of steps for each of my findings,so it might take a long while.
The 32bit Color Depth does seem a lot more vibrant and crisper than 24bit.
Click to expand...
Click to collapse
I have all for cores running on Performance max thanks to Kernel Tuner and the GPU on Performance at 400 with Tweak mod and i switched to 32 bit and im running a bit slower now with FF Type Zero in PPSSPP compared to before. I think im going to switch back to 24 bit and hopefully get a bit more speed back.
THAT IS WHAT I SAID NOT TO DO!
The CPU cores all set to that height will majorly overheat your device,and might kill it.
The most you should do is use Kernel Tuner to set the minimal speeds up to something around 50% full.
I reccommend either leaving it at the default or setting it around the 500 range.
Leave the CPU Govern alone,but GPU on performance mode with Trickster Mod is fine.
The Kernel Tuner's 32bit option does not negatively effect the performance enough (if at all),so you can keep it on with no problems.
The framerate of PPSSPP is dependant on what settings are used.
I have almost everything enabled and I get fluid 60fps with DBZ Budokai Shin.
I also get a nearly stutterless fps with SRB2PSP which normally runs abysmal on the actual system.
My PPSSPP settings...
Graphics:Non buffered,frame limit unchecked with 50% alternative speed,all of performance enabled, and the two speedup hacks enabled.
System:Multithreading and I/O disabled with native 330Mhz PSP clock speed on 2000/3000 mode.
A majority of games will have visual issues (Simpsons Game 3D graphics broken [I blame Qualcomm]) while the two I have tested (DBZ Shin and the SRB2PSP homebrew/port) work nearly flawlessly at full rates.
The 50% alternative rate is really helpful for better performance,since the game still goes up to full speed.
retroben said:
THAT IS WHAT I SAID NOT TO DO!
The CPU cores all set to that height will majorly overheat your device,and might kill it.
The most you should do is use Kernel Tuner to set the minimal speeds up to something around 50% full.
I reccommend either leaving it at the default or setting it around the 500 range.
Leave the CPU Govern alone,but GPU on performance mode with Trickster Mod is fine.
The Kernel Tuner's 32bit option does not negatively effect the performance enough (if at all),so you can keep it on with no problems.
The framerate of PPSSPP is dependant on what settings are used.
I have almost everything enabled and I get fluid 60fps with DBZ Budokai Shin.
I also get a nearly stutterless fps with SRB2PSP which normally runs abysmal on the actual system.
My PPSSPP settings...
Graphics:Non buffered,frame limit unchecked with 50% alternative speed,all of performance enabled, and the two speedup hacks enabled.
System:Multithreading and I/O disabled with native 330Mhz PSP clock speed on 2000/3000 mode.
A majority of games will have visual issues (Simpsons Game 3D graphics broken [I blame Qualcomm]) while the two I have tested (DBZ Shin and the SRB2PSP homebrew/port) work nearly flawlessly at full rates.
The 50% alternative rate is really helpful for better performance,since the game still goes up to full speed.
Click to expand...
Click to collapse
Yeah i just did performance govern for a temp performance test, i get the same speeds on ondemand just fine. but i'll try turning off multithreading and I/O and test it again with the other tweaks you said for PPSSPP.
For what its worth, I noticed the lag immediately following updating to the latest fw. On the original fw the ftv felt so fast and snappy and now is feelz slow and laggy.
It must be related to new bloatware like the kiddy mode and music management.
If you press alt+tab on a keyboard to view recent apps,the media options like apps games videos and photos will be listed,which means they run every time you pass the related options.
Root users need not worry,because rbox will have the homescreen options mod for removing the options soon.
I want to wittle it down to search,home,and settings so I can access things much faster.
Related
Note: This project originally came form Nexus S: Fidelity in Nexus S forum and I added Galaxy S support in version 2.0. This first release for Galaxy S so I don't expect everything to work fine like Nexus S especially I/O tweak that might not work well with Micro-SD card.
***WARNING!!! THIS MOD IS FOR PEOPLE WHO LOVE HAVING ULTIMATE AUDIO PLAYBACK SYSTEM ONLY (LOW LATENCY, LINEAR BIT-STREAM, AUDIO PERFORMANCE AT ITS BEST). IT'S NOT AIMED FOR LONG BATTERY LIFE OR FAST/SMOOTH PHONE AND MAY NOT WORK RIGHT ON YOUR PHONE. I'M NOT PROMISING ANYTHING ABOUT SOUND QUALITY IMPROVEMENTS AND DON'T WANT TO DEBATE ABOUT IT***
After spending months in github looking in Voodoo Sound code and gotta admit I have no idea how it could get any better. Finally, i found something interesting to improve sonic quality that can make us audiophiles smile for higher fidelity. Time to say goodbye to Android life with just Voodoo + cool music player alone.
Six months ago...after ICS firstly released, Google patched audiostream buffer in Nexus S' audio library increasing buffer size and latency after fixing latency delay in 4.0.2 and so on. For normal people's perspectives, it should be a good move as we get stable audio stream, more battery friendly and no more delay issue.
However, some purist computer audiophiles may not agree and have strong motto about 'low latency'. Some Windows players like JPLAY and XXHighEnd went far enough to feed single byte buffer feeding audio card. Not that lower is always better as I prefer minimum hardware buffer size over something extraordinary.
Back to the topic, so I messed around with Nexus S' audio library wondering why no one ever tried that before. As this is first attempt, I'll try to make things as extreme as possible according to what it's capable off.
As there're a lot of misconceptions about latency and jitter stuff so I'm not gonna explain how any those stuff will do about audio performance. Better let your ears decide it as it wouldn't hurt to try. Let's see what this brings to you now.
Features:
Features come in build packages below. Make sure to read all of them as you need to carefully pick out the best for your need. I added my own platform optimizations script in version 2.0 and improved audio library according to new platform performance. I also added Galaxy S (I9000) device support and will try to make more devices like Galaxy Tab and Galaxy Nexus in future. Also keep in mind that there's no best sounding build without sacrificing system's stability.
Builds:
platform: This is innovation of the year for all Android.....no for all Linux-based audio systems and technically work on any Android devices too. Specialized platform for lowest possible I/O latency and CPU utilization having audio thread optimized to its finest having real-time I/O with priority at highest level, Voodoo Sound and Color configuration for purist un-altered sound, kernel resource scheduling optimized to highend DAW level, CPU+I/O+kernel optimized for low latency, audio effects being disabled completely and plus_music patched audio library. It'll have to remove all existing scripts in init.d as most of them can screw this ones up. It'll give you best environment to run even more extreme patches in 2.0 at more battery-friendly setup.
plus_general: Designed for battery-friendly build at 10ms latency playback. You can use this on any ROM, kernels, tweaks you like. General build uses original ICS frame buffer size before modifications and trimmed down buffer size to be the same size as ICS frame for direct frame buffer transfer. I recommend getting plus_general if you don't want to get sloppy second like other builds.
plus_music: Also designed for battery-friendly like general but use even smaller frame buffer size to only 128 at 8 frames for 5ms latency playback at stock environment. It's designed for only music playback alone so you may get some playback problems aside from music playback. To make this stable, I increased number of frames in buffer pool from 4 to 8 according to ALSA's ideal specifications. It works fine on most governors but 100MHz or deep idle may cause some problems. This still works fine on most apps except you try having music played in background on intensive apps.
plus_google: This is alternative design for ideal 5ms latency playback based on plus_general design. Frame buffer size being reduce from original ICS frame buffer size (448) to 256 at 4 frames. The reason I picked ALSA's specifications for music is most ALSA drivers configured for low-latency use that but doesn't mean it's generally better than this ones. I personally prefer lower frames rather than lower frame size at same pool size.
extreme_direct: Designed for those who want to go extreme with lowest possible hw/sw buffer design having buffer pool exactly the same size as output buffer. It's plus_music having number of frames in buffer pool trimmed down from 8 to only 2. Yes.....2 for smallest possible frame buffer pool. You need to install optimized platform environment to keep this stable or run it on high performance setup.
extreme_linear: Designed for those who want to go extreme with smallest possible frame buffer size design. It has only 32 frame buffer size (1/32 of normal buffer size) and have 8 frames in buffer pool. I doubt you can run this at stable level without optimized platform. It has highest battery consumption of all but doesn't mean it works the best. Direct design provides fuller dynamics with more depth while this ones gives you richer ambient with smooth sound.
extreme_insane: Designed for those who want to go extreme with everything smallest possible. It has 32 frame buffer size (1/32 of normal buffer size) and only 2 frames in buffer pool making buffer pool 1/4 of other extreme patches. I said insane because it's beyond what this phone is capable of technically. Even in specialized platform on performance govenor may not music played till the end without single spike. You can only try making it stable with steve.garon's filesync off kernel after patching specialized platform. The reason I didn't include his kernel in because it causes occasional reboots and currupt data partition due to disabled filesync running insane task.
Downloads
nexus_s_fidelity_platform
nexus_s_fidelity_plus_general
nexus_s_fidelity_plus_music
nexus_s_fidelity_plus_google
nexus_s_fidelity_extreme_direct
nexus_s_fidelity_extreme_linear
nexus_s_fidelity_extreme_insane
nexus_s_fidelity_restore
Changelog
[03/05/12] Version 2.0
-Added audio thread priority optimizations to highest level
-Added audio I/O priority optimizations to highest real-time level
-Added CPU optimizations for low latency playback
-Added Galaxy S (I9000) device support
-Added kernel resource scheduling optimizations
-Added I/O optimizations for low latency playback
-Changed Voodoo Sound headphone gain to 0db (2db has too high hiss on low impedance phone)
-Fixed clear old scripts in init.d that didn't work last time
-Removed libaudioeffect_jni.so as it increase more load and latency
-Removed DSPManager as it can't be disabled and keep showing error during music playback
-Removed wildestpixel tweaks
-Tweaked audio library improvements
|-plus_music uses library from version 1.0 for Alsa's ideal specifications
|-plus_google added as alternative ideal 5ms design based on Google's Android code
|-extreme_direct now has 1/2 frame buffer size comparing to 1.1 version
|-extreme_linear now has 1/8 frames comparing to 1.1 version
|-extreme_insane added with everything smallest from other extreme patches
|-restore now also remove installed optimizations and restore libaudioeffect_jni.so
[28/04/12] Version 1.1
-Added plus_general for all-around use at 10ms latency playback
-Added plus_music for music focused use at 5ms latency playback
-Added extreme_direct and extreme_linear for non-compromise builds
-Added restore for people who want to use current AOSP build
[27/04/12] Version 1.0
-Initial release with kernel/tweaks for 8x1/8 frame buffer optimized for 5ms latency playback
If you experiences any playback problems, try changing minimum frequency or use suited governors, I/O, CPU settings in NSTools. I'm quite satisfied with battery-life in version 2.0 and never have issue after finalizing version 2.0.
Im sure its gonna work as the audio driver is the same. Good work Windows X!
Sent from my Nexus S using Tapatalk 2
Flashing
Edit: Flashed nexus_s_fidelity_plus_google.zip v2.0 (cm9 snapshot build:devil2 0.79 kernel:smartass v2:sio) and i must say i can notice significant change in sound quality.... dunno if its jus placebo but high n lows are jus awesome!!! thankx... will try other zips as well
Edit: audio playback is not smooth... it skips now n then +battery life is poor... will try future releases... nw back to stock... thankx
Looks interesting
Will flush... Thanks a lot for all your hard work and efforts.
I really appreciate what you're trying to do here. However, latency has nothing to do with audio quality, and JPLAY and XXHighEnd are what I like to call placebo-players.
Unless something is critically broken with the Android playback system, then this will have no measurable effect.
Using this system is not like using ASIO or WASAPI in windows.
Funkstar De Luxe said:
I really appreciate what you're trying to do here. However, latency has nothing to do with audio quality, and JPLAY and XXHighEnd are what I like to call placebo-players.
Unless something is critically broken with the Android playback system, then this will have no measurable effect.
Using this system is not like using ASIO or WASAPI in windows.
Click to expand...
Click to collapse
Have you tried it? Though I already said it's for people who want low latency audio and won't debate about it or promise about SQ, I'd like to point out tons of engineers having latency issue for pro audio apps to work properly in Android. Do some research about latency problems in Android and PulseAudio for more promising insight.
Btw, it seems I'm facing I/O starvation problems as I set read_ahead to 0. Trying to adjust it right now hoping to push 2.1 along with new device.
placebo-players, hahaha :ddddd
have fun in your 'bit-perfect' world measuring SQ with rightmark frequency responsce
OP: well, sticking to the topic, im testing at the moment, lots of thanks for making this.
looks like linear is almost stable for me, i have to toy a bit more though
p.s. i had to disable deep sleep
I think I made some progress about I/O optimizations. It seems to produce more linear I/O streaming with better stability and while keeping no read ahead cache. I'm going to test this with extreme patches and see how things will work there. Hopefully to get this stable with Galaxy S too tomorrow
btw, it's possible to make deep idle stable with extreme but not sure if recent optimizations will work with it.
I suspect you own the windows program called "Fidelizer" right.
If so, really appreciate your previous work.
Will flash this tool soon.
<i love Tapatalk and I9000>
Thx for this nice mod! I appreciate all mods that improve audio. Hopefully works with deep idle soon.
--------------------------------
Windows X said:
btw, it's possible to make deep idle stable with extreme but not sure if recent optimizations will work with it.
Click to expand...
Click to collapse
you mind sharing how?
then havin cpu on 400MHz wouldn't be that painful
btw shame we have so little of ram, you could afford caching files to RAM -> no SD read ahead problem
archdoraz said:
I suspect you own the windows program called "Fidelizer" right.
If so, really appreciate your previous work.
Will flash this tool soon.
<i love Tapatalk and I9000>
Click to expand...
Click to collapse
Fidelizer is also my work too. Thank you. I'm also Thai btw.
dark_knight35 said:
Thx for this nice mod! I appreciate all mods that improve audio. Hopefully works with deep idle soon.
--------------------------------
Click to expand...
Click to collapse
Actually, I used to get deep idle working on extreme patches but it'd be impossible with highly optimized I/O for lowest latency. I tried changing scheduler to noop alone leaving the rest to defaults and worked fine with deep idle but buffered stream won't be as good as what I'm listening to now. You can look forward to 2.1 for better optimizations.
pwlj said:
you mind sharing how?
then havin cpu on 400MHz wouldn't be that painful
btw shame we have so little of ram, you could afford caching files to RAM -> no SD read ahead problem
Click to expand...
Click to collapse
Extreme patches won't suffice for 200MHz. I monitored from adb and it keeps jumping up all the time which is very bad comparing to 400MHz that always stay the same if you listen to music alone. For deep idle, it's like I mentioned above. I just removed my I/O optimizations leaving noop scheduler alone and it worked fine. But I love bufferless I/O so you'd better stick with plus files if you want to keep deep idle.
Thanks.
What is the best quality mod?
is there an order for flashing this mods or I need to select only one mod?
For best version, that really depends on user preferences. Some prefer plus over extreme, some prefer google over music, some prefer direct over linear, etc. If you want good platform, make sure to flash platform along one of those above.
OK Flashed Plus_Music and switched back default and then back to Plus_Music again,
I found that I can notice it only a bit (like 5%) difference.
However I'm not an audiophile, just a serious listener,
so I can't recognize every detail of a sound.
The thing I noticed was clarity, if there was a difference.
I can also felt that the phone was slowed down a bit, not as
smooth as the default setting. I dont know about battery life
coz I just flashed it. Anyway, don't take this seriously,
I suggest you all to try a patch and report.
However, I admit that I was quite confused reading the op.
My suggestion is to make it easier to read, like splitting technical
detail into lists. I have problem choosing a patch coz I dont
understand the detail at all TT (my bad).
Anyway, thanks for your effort on this work and hope you
keep doing this. I will keep a look on this thread.
Equipment: SGS i9000 / Slim Rom 3.5 / Semaphore 1.1.1s kernel
/ Shure SE530 earphone / Flac and 320Kbps songs.
@archdorz Yes, the difference isn't very big, but with other sound improvements, you really get a nice sound. And to performance and battery, I think it will get better in coming releases.
--------------------------------
kosta20071 said:
Thanks.
What is the best quality mod?
is there an order for flashing this mods or I need to select only one mod?
Click to expand...
Click to collapse
Reducing buffer sizes have no effect whatsoever on sound quality.
http://forum.xda-developers.com/showpost.php?p=25624775&postcount=91
Windows X said:
extreme_linear: Designed for those who want to go extreme with smallest possible frame buffer size design. It has only 32 frame buffer size (1/32 of normal buffer size) and have 8 frames in buffer pool. I doubt you can run this at stable level without optimized platform. It has highest battery consumption of all but doesn't mean it works the best. Direct design provides fuller dynamics with more depth while this ones gives you richer ambient with smooth sound.
Click to expand...
Click to collapse
{
"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"
}
Sorry couldn't resist
supercurio, I think you should at least post something like I tried plus_music (128x8) and extreme_direct (128x2) but couldn't notice difference at all except stability lag. Too sad that I have yet to see people posting they tried but they can't get into what I proposed. Maybe absurdity is too high for them to give a try I guess.
And worst of all, what you bold is misinterpreted, really. I said direct design as design philosophy not extreme_direct. I'm quite disappointed seeing people carelessly make fun of things they don't really care about like this. I know this device can produce output for just 5mW and no where close to actual design. Don't take extreme stuff too much and consider proper things like plus ones please.
FYI: smooth sound caused by transient response of dynamics being trimmed down making bandwidth seems wide and good depth is not trimmed that bad. That's why there's designer in audio/video circuit having bufferless motto who want to avoid using buffer.
I think I agree with earlier posters can you show some numbers or data that PROVES your process works. Not to stir the pot anymore but the community knows and trusts supercurios work. I am a previous vibrant user now a nexus s user and Voodoo sound has been proven to be effective time and time again. So far all I have seen for your mods is user feedback which best case is very subjective.
You have the un-enviable task or trying to prove that your mods are inherently better against one of the most trusted audiophiles on xda. I will continue to follow this tread as its interesting but like so many others here, I inherently trust supercurio as over the 2ish years of voodoo I have yet to see that his information or processes are wrong or flawed.
Hi guys, bit of a strange problem here - using any emulator (any of robert brogalias, as well as supergnes or animaonline), I'm getting sound and framerate stuttering at consistent intervals. It seems like something is hitting the cpu when this happens, but I don't know what might be doing it - I have "betterbatterystats" and it shows that "audioOut_2" is causing 12.8 percent of partial wakelocks, don't know if this could be related.
Power saving features are all off, to my knowledge.
I've only installed very few apps, like PowerAmp, CPU Spy, titanium backup and a couple others. Rebooting the phone makes no difference, removing the SD card after copying roms to the internal memory made no difference, stopping the media scan service did nothing, I even flashed roms to Clean Rom 3.5 and it didn't change. I wiped dalvik and the other cache beforehand.
Any ideas? My tegra 2 tablet can run these emulators flawlessly at 60 fps all day!
f3tf said:
Hi guys, bit of a strange problem here - using any emulator (any of robert brogalias, as well as supergnes or animaonline), I'm getting sound and framerate stuttering at consistent intervals. It seems like something is hitting the cpu when this happens, but I don't know what might be doing it - I have "betterbatterystats" and it shows that "audioOut_2" is causing 12.8 percent of partial wakelocks, don't know if this could be related.
Power saving features are all off, to my knowledge.
I've only installed very few apps, like PowerAmp, CPU Spy, titanium backup and a couple others. Rebooting the phone makes no difference, removing the SD card after copying roms to the internal memory made no difference, stopping the media scan service did nothing, I even flashed roms to Clean Rom 3.5 and it didn't change. I wiped dalvik and the other cache beforehand.
Any ideas? My tegra 2 tablet can run these emulators flawlessly at 60 fps all day!
Click to expand...
Click to collapse
You didn't make any under clock profiles did you? And is there a setting to change emulator settings back to default? Perhaps you changed something that made it go whack.
Sent from my GT-N7100
no problem here with fpse
i love to play Crash Bandicoot :laugh:
@rbiter said:
You didn't make any under clock profiles did you? And is there a setting to change emulator settings back to default? Perhaps you changed something that made it go whack.
Sent from my GT-N7100
Click to expand...
Click to collapse
Haven't changed any clocks, nope. Emulator settings are default - changing frameskip to 0 makes the sound lag even worse, and allowing frameskip creates big jumps every 3/4 of a second or so. Happens regardless of the emulator used.
Forcing CPU to 1600mhz constant also has no effect.
Governor default or performance? Can't think of much else besides power saving mode but it should run fine on that too.
Sent from my GT-N7100
Doesn't seem to matter on performance or default. I'm still running the stock kernel, think I should overclock? I really shouldn't need to though when a stock tegra 2 can handle it with 0 frameskip, sound quality on max... even NES is stuttering.
I did a complete restore, no change.
f3tf said:
Doesn't seem to matter on performance or default. I'm still running the stock kernel, think I should overclock? I really shouldn't need to though when a stock tegra 2 can handle it with 0 frameskip, sound quality on max... even NES is stuttering.
I did a complete restore, no change.
Click to expand...
Click to collapse
No need to over clock. The emulators have run fine on my older hardware under clocked just fine. The only thing it could be is a setting jacked up inside the emulator. Nintendo and super Nintendo run easily on ARM chip sets. Fpse and n64 would give it a run for it's money though. You sure you don't have something in the background hogging up horsepower?
Sent from my GT-N7100
No problem with epsxe here smooth as butter stock 4.1.2. It's most likely the rom you're using.
Stock or Clean Rom has the same issue.
epsxe is a different story, I can run that just fine. My benchmarks are pretty standard for quadrant, I'm really out of ideas - maybe the refresh rate of the phone is slightly higher or lower than the emulator is trying to run at, causing either frame skipping or sound jumps? Any other users with an eye for framerate here noticed minor frame jumping in, say, sonic 1, 2, or 3 on MD.emu? I bet it's there, but then if you turn frameskip to 0 (like I would on my tf101) the sound goes to hell instead.
I'm using Snes9x EX and AndroGens (as well as Fpse) and don't have any of the problems you describe. Maybe you should give those a shot, and if you get the problem with those too, you might have a hardware issue?
Sent from my GT-N7105 using xda app-developers app
Snes9x EX gives me the issue as well. Play mario world and run as fast as you can on level ground left and right a few times, see if the image has some slight jumps in it. Lots of people wouldn't even notice this.
Otherwise, turn frameskipping to 0. Does the sound start having issues? If it does, you have the same problem as me.
Reading around, I've found that the Note 2 apparently runs at a 58 hz refresh rate, where most everything else (including the emus) expect 60, causing the video or audio to have issues (you can have one or the other, but not both). I'm running the stock kernel, if you're running perseus it might be ok... which kernel are you running?
f3tf said:
Snes9x EX gives me the issue as well. Play mario world and run as fast as you can on level ground left and right a few times, see if the image has some slight jumps in it. Lots of people wouldn't even notice this.
Otherwise, turn frameskipping to 0. Does the sound start having issues? If it does, you have the same problem as me.
Reading around, I've found that the Note 2 apparently runs at a 58 hz refresh rate, where most everything else (including the emus) expect 60, causing the video or audio to have issues (you can have one or the other, but not both). I'm running the stock kernel, if you're running perseus it might be ok... which kernel are you running?
Click to expand...
Click to collapse
Oh, youre right, it does this for me too. It's really barely noticeable though, I hadn't noticed before now. I'm also on the stock kernel.
What did you mean by sound issues? Turning frameskip off maybe makes the sound a tiny biy faster at some points than it should be, but that too is barely noticeable and could just be my imagination.
But you're right, theres definitely an issue there, and I do wonder if you're right about the refresh rate.
Sent from my GT-N7105
Yeah I tried the perseus kernel, no change, sadly.
For sound issues, I get skips and stutters every couple of seconds in MD.emu, NES.emu, snes9x ex, SuperGNES, Animaonline SNES, and presumably all the others which require a tight synchronization of audio and video. Doesn't seem to be overly noticeable on epsxe, but then I haven't played any games which run at a tight 60 FPS on that one, either. Official games have no problems.
Running 1800 mhz makes no difference, either.
I've emailed Robert Broglia about the issue, I'll update if he replies - anyone else, let me know if you find a fix!
Received a reply from Robert (damn that guy is a machine), pasta'd below
***************
Hi, thanks for the heads up on the Galaxy Note 2, not sure why all these manufacturers are using screens with such odd refresh rates. For example, the Kindle Fire is 53Hz and the Xperia Play is 62Hz. Luckily the Nexus 7 I just picked up has a perfect 60Hz refresh rate so 0 frameskip works well on it.
In the next update I'm switching over to a more precise method for getting the device's clock so I wonder if it might help space the frames out a bit more evenly on your device. The best solution will probably be to use frameskip 0 but adjust the input audio frequency to speed-up/slow-down the audio to match the refresh rate, so I'll look into adding this for a future update.
f3tf said:
Received a reply from Robert (damn that guy is a machine), pasta'd below
***************
Hi, thanks for the heads up on the Galaxy Note 2, not sure why all these manufacturers are using screens with such odd refresh rates. For example, the Kindle Fire is 53Hz and the Xperia Play is 62Hz. Luckily the Nexus 7 I just picked up has a perfect 60Hz refresh rate so 0 frameskip works well on it.
In the next update I'm switching over to a more precise method for getting the device's clock so I wonder if it might help space the frames out a bit more evenly on your device. The best solution will probably be to use frameskip 0 but adjust the input audio frequency to speed-up/slow-down the audio to match the refresh rate, so I'll look into adding this for a future update.
Click to expand...
Click to collapse
Interesting. I wonder if it's worth me emailing the devs of the emulators I use.
Sent from my GT-N7105
That's very interesting that our quad-core 1,6Ghz with 2 GB ram struggles to emulate the SNES
CPU: Custom 65C816 at 3.58 MHz
RAM: 128 Kb
Max Colors on Screen: 256
Max Sprites: 128, 32 per scanline
Sound Channels: 8 ADPCM
Sound Memory: 64 Kb
That's a challenge
victorator said:
That's very interesting that our quad-core 1,6Ghz with 2 GB ram struggles to emulate the SNES
CPU: Custom 65C816 at 3.58 MHz
RAM: 128 Kb
Max Colors on Screen: 256
Max Sprites: 128, 32 per scanline
Sound Channels: 8 ADPCM
Sound Memory: 64 Kb
That's a challenge
Click to expand...
Click to collapse
It's actually not hardware power that we're lacking - we could probably emulate snes at fullspeed with 400 mhz on a single core if the emu was very well coded, and obviously we have tons more power than that. It's a function of how the emulator draws the screen and plays the sound - almost every device runs at 60hz, so every application expects the maximum speed to be 60 FPS, but the note 2 is actually 58 hz. This creates a (much larger than you'd expect) jump in the fluidity of the emulator when running with frameskip set to auto, and it creates an annoying audio jump/skip if frameskip is turned off.
In this situation, you can have perfect video or audio, but not both. One workaround is to slow down the audio to match the 58 frames instead of the 60.
If you use supergnes, you may as well email him because it happens in that emu too. Snex9x EX is way better than supergnes, though.
I can confirm the same thing is happening for my Galaxy Note II, although mine is the US Sprint CDMA/LTE variant. It also has a refresh rate of 58.002 Mhz and I use nearly all of Robert Broglia's emulators. On this device, it's either sound regularly skips with frameskip set to 0, or (nearly) perfect audio with stuttering video when frameskip is set to Auto.
This device is a beast, so this shouldn't be happening at all. :-/
Half Life 1 can now be fully played on Android with the use of the DosBox Turbo App. Here you will learn how to run the game and watch some in-depth, low fps gameplay(1-10) with my Galaxy Note 2. To see the step by step creation guide head over to the LSGameChannel and Learn how to make this fun PC game an Android port. Big thank you to the LSGameChannel for making the video guide.
[Video] How to play Half life on the Samsung Galaxy Note 2
Click Here to watch the LSGameChannle Video "How to run Half-Life on Android (DosBox Turbo)"
DosBox Turbo By:Fishstix
https://play.google....ix.dosbox&hl=en
Recommended System Requirements:
CPU Quad-Core 1.6+ or Dual-core 1.5+GHz, equivalent or better.
GPU Adreno 220, Nvidia Tegra2/3, equivalent or better.
1GB, 512. My Config asks for a min or 256MB & shouldn't be run on a device with less than this.
8GB disk space
1)Install DosBox Turbo. Go into Config/DosBoxSettings/ and make sure Manual mode is selected. You will need to restart the app for it to take effect.
2)Download and extrat the Half Life for Android folder.
3)Copy and paste the two files (HL.img & dosbox.conf) into the internal memory or sdcard on your device.
4)Start DosBox Turbo and enjoy Half Life.
Notes:
-You can enable GPU Rendering by go to settings/Screen and Rotation Settings/GPU Rendering(Check)
-You can improve the scale quality by going to settings/Screen and Rotation wettings/Scale Quality/HQ Scale(Slower)
-Galaxy Notes users may want to disable "Power Saving" mode to improve performance.
How to run Fallout 1 & 2 on Android with Sound, Patches & Mods Video+Guide:
[media]http://youtu.be/hYTTrHbQcBo[/media]
How to run Fallout 1 & 2 on Android with Sound, Patches & Mods Video+Guide Thread @ XDA:
CPU Master (free) Overclocking App:
https://play.google....asterFree&hl=en
Sweeeeet! Using your guide, I got it working on my Nexus 7. I did make one change, I set cycles = max and that seems to have make the audio much much better, the tradeoff being that the framerate is a bit slower.
GPU Rendering
gururise said:
Sweeeeet! Using your guide, I got it working on my Nexus 7. I did make one change, I set cycles = max and that seems to have make the audio much much better, the tradeoff being that the framerate is a bit slower.
Click to expand...
Click to collapse
Hey, glad you got it working! The auto setting will give you the best sound quality but will cost you some performance.
Try doing this
-You can enable GPU Rendering by go to settings/Screen and Rotation Settings/GPU Rendering(Check)
RolandDeschain79 said:
Hey, glad you got it working! The auto setting will give you the best sound quality but will cost you some performance.
Try doing this
-You can enable GPU Rendering by go to settings/Screen and Rotation Settings/GPU Rendering(Check)
Click to expand...
Click to collapse
+1:good:
+1 thanks
Half-Life on Samsung Galaxy Note 2 N7100 with Stock Rooted 4.1.2 Firmware
Good work, but this barely passes for even mildly playable. Why? 1-10 fps is nothing but a big pile of steaming bs. I mean, why waste time on this crap when you can play better native games.
Also, I think we should all be thankful to the id software, because if they had not released their game engine as free-source, the guy called n0n3m or something like that could have never developed the DIII4A app. Its fantastic, I got a rock steady 25-30 fps without fail. Also, I played Quake 1,2,and 3 along with RTCW(Return to Castle Wolfenstien) with HD enabled 1080p screen size without problems.
As far as HL is concerned, this game cannot be enjoyed at the framerate the DOSbox turbo is giving. Quite frankly,its pathetic and one should not even try to waste time as I did, because the game is a classic and can be only be enjoyed with full audio. Oh, and did I forget to mention the fact that there is no audio in the gameplay?
My Verdict: This project has a rock solid future as just being able to even get to the in-game screen was like drinking the sweet morning dew from the leaf blades of lemon grass, but quite frankly, it has a long way to go to even come under the category of playable.
: TECHNICAL CONCLUSION :
1) PLAYABLE : Yes, goes in game and is playable as long as you dont mind the bs framerate.
2) FRAME RATE : 1 -10 on a QUAD-CORE PROCESSOR WITH QUAD-CORE GPU
3) AUDIO : No
4) GLITCHES : Yes, Multiple, with wierd graphics here and there.
5) WORTH TRYING : Hell yeah, if you are a dev and wanna contribute to make it better, or just a casual tester or a user. Definitely worth a shot.
Wow...this community is great. I swear...people are blowing me away with these kind of mods. Good stuff sir!
HELP!!!!
This worked for the first time but after i tried to load it again it said has performed an illegal operation and must be shutdown!
I tried everything but it wont boot
HELP
Hey,
I have found this video on YT: http://www.youtube.com/watch?v=jrJM5OVpmMI .
He wrote: "Cpu is not overclocked. I have rooted phone."
And I'm confused ;\ why this guy a way better fps in this games? Shadowgun Dead Zone in UNPLAYABLE on my htc one v. In Trial Extreme 3 I have about 33% less FPS :\
btw. I have cleared cache\ram. I have 150mb of free ram.
I have found a work around method so I'll write it down, maybe it will be useful for someone:
I dunno why this guy has so good fps on a 'standard' device but I have found a good way to increase fps in games:
If you have CyanogenMod go to settings and at the bottom you will have 'performance' option; inside you can find 'processor', inside maximum something. - go there and change 1024MHz to 1400MHz. Also change 2nd option from ondemand to SMARTASSV2. That will gives you better performance when processor will need it, like in games. In fact it gives about 30% more fps without any serious consequences. (No, no serious battery draining or crashing or anything).
Why is it that despite of having same configuration as OnePlus3, ZUK can't play 4KHDR @60fps as smooth as OP3? Though it can, after some tweaks, but not as efficiently & smooth as OP3(unrooted). I used same Version of MXPlayer and same file for comparison.
I tried all custom kernels available (Heliox,Jaguar,Darkmoon) and Latest versions of major ROMs(RR,AEX,ViperOS). And still didn't match the playback quality of OP3.
Please tell me if there are more kernels or ROMs yet to be tried, which can bring substantial step-up in performance, or which will just Play 4KHDR @ 60fps.
Overall, the User Experience is super-smooth but
this small thing is eating my brain :crying:
d3vyarth said:
Why is it that despite of having same configuration as OnePlus3, ZUK can't play 4KHDR @60fps as smooth as OP3? Though it can, after some tweaks, but not as efficiently & smooth as OP3(unrooted). I used same Version of MXPlayer and same file for comparison.
I tried all custom kernels available (Heliox,Jaguar,Darkmoon) and Latest versions of major ROMs(RR,AEX,ViperOS). And still didn't match the playback quality of OP3.
Please tell me if there are more kernels or ROMs yet to be tried, which can bring substantial step-up in performance, or which will just Play 4KHDR @ 60fps.
Overall, the User Experience is super-smooth but
this small thing is eating my brain :crying:
Click to expand...
Click to collapse
First of all, You are comparing "THE BEST" SD820 phone with probably the 3rd or 4th best SD820 phone (antutu wise). Secondly, even on the OP3, why would you choose to play 60fps 4K videos that too HDR ones?! That's ridiculous for anyone. I'm hoping the logical explanation to why you're doing this is to kinda benchmark the phone. But even then a lot of SD653 and SD810 phones can breeze through this benchmark easily. It's even more ridiculous that you've tried almost all roms and kernel combos just for a luxury video playback.
Anyways coming to the point, I tried the Sony 4K 60fps HDR Swordsmith video on my Z2+ (AEX4.6 Official with HelioX 3.18.80) via MX with HW (not plus) decocer and the video was running smooth AF. Infact, compared to playback my friend's OP3 running OxyOS 5.0, my Z2+ had zero hiccups throughout the video while the OP3 had 2 or 3 towards the middle. The interesting thing is that I achieved these results while running CPU underclocked to 1996 & 1401. But technically speaking that shouldn't be a problem in the video playback coz HW decoder runs exclusively on the GPU. Concluding my point, don't watch ridiculously high quality videos on phone and don't change roms and kernels to achieve desired playback, just adjust and optimize them.
Incrovantilist said:
First of all, You are comparing "THE BEST" SD820 phone with probably the 3rd or 4th best SD820 phone (antutu wise). Secondly, even on the OP3, why would you choose to play 60fps 4K videos that too HDR ones?! That's ridiculous for anyone. I'm hoping the logical explanation to why you're doing this is to kinda benchmark the phone. But even then a lot of SD653 and SD810 phones can breeze through this benchmark easily. It's even more ridiculous that you've tried almost all roms and kernel combos just for a luxury video playback.
Anyways coming to the point, I tried the Sony 4K 60fps HDR Swordsmith video on my Z2+ (AEX4.6 Official with HelioX 3.18.80) via MX with HW (not plus) decocer and the video was running smooth AF. Infact, compared to playback my friend's OP3 running OxyOS 5.0, my Z2+ had zero hiccups throughout the video while the OP3 had 2 or 3 towards the middle. The interesting thing is that I achieved these results while running CPU underclocked to 1996 & 1401. But technically speaking that shouldn't be a problem in the video playback coz HW decoder runs exclusively on the GPU. Concluding my point, don't watch ridiculously high quality videos on phone and don't change roms and kernels to achieve desired playback, just adjust and optimize them.
Click to expand...
Click to collapse
My point on playing the best video quality I have, bcz ZUK can, why not. I tried LG Cymatic Jazz HDR to test the playback(details attached).
Back when I had ZUI, it could not play the video at 60 fps. But when I flashed first RR, I was surprised by the result. In MX Player Pro with HW+, it could play super smooth with absolute 0 lag.
Then came updates and further more I flashed many ROMs but never got that playback. Changing kernels didn't help. And now I've same ROM and kernel as you do, because you know.
The fact that you can play 4KHDR @ 60fps, may be bcz ur video isn't having 10 bit color depth. Please attach your video details, I wanna see. If our videos are of same quality, then I may be having some other issue.
Its strange however, you're playing 4KHDR on HW.
Also, do you have Substratum theme or Xposed modules installed? Just curious if these affect performance in any way.
d3vyarth said:
The fact that you can play 4KHDR @ 60fps, may be bcz ur video isn't having 10 bit color depth. Please attach your video details, I wanna see. If our videos are of same quality, then I may be having some other issue.
Its strange however, you're playing 4KHDR on HW.
Also, do you have Substratum theme or Xposed modules installed? Just curious if these affect performance in any way.
Click to expand...
Click to collapse
No Substratum No Xposed. And the video I tried has same video specs as yours (attached).
Incrovantilist said:
No Substratum No Xposed. And the video I tried has same video specs as yours (attached).
Click to expand...
Click to collapse
Is it possible that Xposed and Substratum are somewhere causing pain to the system?
Also, I once changed some screen values through Kernel auditor and tried to undo that. I don't know if they're default now, I'm attaching SS just tell me if they're same. I'll try uninstalling Substratum and Xposed and keep system as Lite as possible and then check.
Thanks for your attention and help
d3vyarth said:
Is it possible that Xposed and Substratum are somewhere causing pain to the system?
Also, I once changed some screen values through Kernel auditor and tried to undo that. I don't know if they're default now, I'm attaching SS just tell me if they're same. I'll try uninstalling Substratum and Xposed and keep system as Lite as possible and then check.
Thanks for your attention and help
Click to expand...
Click to collapse
Substratum can have some slowing effect on GPU due to its theme engine but that'll be possibly unnoticeable in a SD820. Xposed should be harmless (afaik with my previous phones) unless you are running GPU affecting modules. I don't use substratum because I was perfectly happy with CM theme engine and now that it's gone, I'm not so keen for a replacement. Xposed went meaningless after Lollipop & the birth of Magisk (for me atleast). And lastly about Screen values in KA, they don't have any effect on GPU unless ofcourse you're running grayscale which might actually save you some power (but might be unstable). If you want to reset the values, just uncheck apply on boot under screen settings and reboot. FYI, I ran almost all KCAL profiles I found online and "Perfection" (that's the name of the KCAL profile) for OP2 is giving the best visuals in my perspective. Try it if you want. Happy to have helped you ?✌?
Imo the zuk z2 is not as good at playback than I expected. Even 1080p60 video drop frames constantly at 2x playback speed
Also the phone dont have a hdr screen so why even try to play hdr content anyway
pipyakas said:
Imo the zuk z2 is not as good at playback than I expected. Even 1080p60 video drop frames constantly at 2x playback speed
Also the phone dont have a hdr screen so why even try to play hdr content anyway
Click to expand...
Click to collapse
Playing a 60fps video at 2x speed would mean 120fps, that's out of our screen limit. For that purpose display needs 120Hz refresh rate as in New Razer phone, or some frames will get skipped(frame drops) as you noticed.
And the reason why I wanna play that, I search of playing that thing smoothly, I've learned many things. It simply gives me satisfaction.
Incrovantilist said:
Substratum can have some slowing effect on GPU due to its theme engine but that'll be possibly unnoticeable in a SD820. Xposed should be harmless (afaik with my previous phones) unless you are running GPU affecting modules. I don't use substratum because I was perfectly happy with CM theme engine and now that it's gone, I'm not so keen for a replacement. Xposed went meaningless after Lollipop & the birth of Magisk (for me atleast). And lastly about Screen values in KA, they don't have any effect on GPU unless ofcourse you're running grayscale which might actually save you some power (but might be unstable). If you want to reset the values, just uncheck apply on boot under screen settings and reboot. FYI, I ran almost all KCAL profiles I found online and "Perfection" (that's the name of the KCAL profile) for OP2 is giving the best visuals in my perspective. Try it if you want. Happy to have helped you ?✌?
Click to expand...
Click to collapse
I removed Substratum and Xposed, even Shox audio mod, but result was same.
Though Performance as CPU Governor gives 100% results, but you said you've Under-Clocked ur CPU to 1996MHz, that did surprise me.
Which CPU & GPU governor do you use? Also which I/O Scheduler? I'm curious.
d3vyarth said:
I removed Substratum and Xposed, even Shox audio mod, but result was same.
Though Performance as CPU Governor gives 100% results, but you said you've Under-Clocked ur CPU to 1996MHz, that did surprise me.
Which CPU & GPU governor do you use? Also which I/O Scheduler? I'm curious.
Click to expand...
Click to collapse
Fiops scheduler.
CPU Governor is Interactive. (default on HelioX)
GPU Governor is Msm-adreno-tz. (default on HelioX)
Incrovantilist said:
Fiops scheduler.
CPU Governor is Interactive. (default on HelioX)
GPU Governor is Msm-adreno-tz. (default on HelioX)
Click to expand...
Click to collapse
I use same settings
I think I need to do more research on this.
Updating to Oreo smoothed everything out :fingers-crossed: