Related
Just a few tweaks for those who are rooted and not flashing custom roms. some will already be in there, just edit them.
use root explorer, go to system, click mount r/w hold build.prop till a menu pops up and click the text editor one.
read the entire build.prop to ensure no duplicates
also dont misspell!
If its already in there just edit it. if you dont know what your doing dont bother with this.
render ui with gpu
debug.sf.hw=1
smoother scrolling
windowsmgr.max_events_per_sec=150
better battery by reducing wifi scans
wifi.supplicant_scan_interval = 150
dalvik memory heap size
dalvik.vm.heapsize=48m
screen ppi or font density
ro.sf.lcd_density=235
turn off dithering, not needed anymore in gingerbread
persist.sys.use_dithering=0
more memory
persist.sys.purgeable_assets=1
smoother experience
debug.performance.tuning=1
video.accelerate.hw=1
dalvik.vm.dexopt-flags=m=y
camera/camcorder mods
ro.media.capture.maxres=8m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=70
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
better pics
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.jpeg.quality=100
better playback
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-record=false
i dont use all of these but most. it helps.
Keep in mind in order to update in the future you must keep a back-up of your build.prop to restore if you want to update.
once your done restart
Thanks but do you have a short description of what the tweak will enhance? Some are obvious, but others are not. Thanks again.
Sent from my MoPho using XDA Premium.
just edited with some descriptions
Thanks for this. I havent unlocked my bootloader yet so this is something I can play around with to see if I can squeze anything more out of this MoPho!
bigbassbrent said:
Thanks for this. I havent unlocked my bootloader yet so this is something I can play around with to see if I can squeze anything more out of this MoPho!
Click to expand...
Click to collapse
Yes its basically making changes to your build.prop no unlocked bootloader needed. An easier way to do this is to pull the build.prop and get it on your comp then make the changes and replace current build.prop. Id make a backup of unmodified build.prop.
So if these tweaks are not in the stock build prop, is there a specific place in the file they go? Or can I just copy paste to anywhere, such as the bottom.
They can go at the end. If my memory serves me correct, the following ones were already in the build.prop and just needed changing. (I didn't do any of the media related ones)
windowsmgr.max_events_per_sec=150 (default = 70)
wifi.supplicant_scan_interval=150 (default = 45)
dalvik.vm.heapsize=48 (default = 40)
ro.sf.lcd_density=235 (default = 240)
I had to add the following lines at the end of the build.prop
persist.sys.use_dithering=0
persist.sys.purgeable_assets=1
debug.performance.tuning=1
video.accelerate.hw=1
dalvik.vm.dexopt-flags=m=y (this one was already present and the same)
I'm just learning, but I remember seeing something about there needing to be a blank line at the end of the file. (hit enter after the last line) Dont know if this is true in this case but I figured I'd put one just in case.
So any that has applied these tweaks which are the best to use for performance enhancement and do you notice the enhancement?
Oh how to make a backup too do I just write it down our what.
Sent from my iphone killer
abrcrmdl23 said:
So any that has applied these tweaks which are the best to use for performance enhancement and do you notice the enhancement?
Oh how to make a backup too do I just write it down our what.
Sent from my iphone killer
Click to expand...
Click to collapse
All of the changes I listed in my last post are aimed at gaining performace except for the ro.sf.lcd_density=235 (default = 240) line which to me just made the fonts smaller. I ended up setting this one back to 240.
As far as performance gains, I didnt record any benchmarks before I made the changes so I don't have a good baseline, but I compared my scores to another unmodified photon.
Smart Bench 2011
Modified scored 3345, 2665
Stock scored 2823, 2656
Quadarant Standard
Modified scored 2624
Stock scored 2743
Based on Quadrant scores, I'm not sure what we have accomplished by making the changes. The Smart Bench scores seemed to be somewhat better after the changes. I'll continue to watch and report any other findings.
Thanks for the info. The only tweak I made so far is the dalvik cache tweak. It made the phone much smoother and faster. Is there any disadvantage in bumping up the dalvik cache up to 55 or 60?
These changes will not show up much in benchmarking, however they will make the device feel smoother and faster. better scrolling and better experience. changing how the device renders the ui wont make your quadrant go up
clifton421 said:
Thanks for the info. The only tweak I made so far is the dalvik cache tweak. It made the phone much smoother and faster. Is there any disadvantage in bumping up the dalvik cache up to 55 or 60?
Click to expand...
Click to collapse
People have mixed opinions about what's the best setting, the higher number allows apps to cache more memory into the ram.
I usually set mine to 64m
if you set it too high each program will use more memory and the available memory for other programs will be reduced
So I was looking through my build prop and has anyone else noticed there are a lot odd Verizon references in there like it says the photon is a Verizon wireless world device, and there is other VZW references it also makes mention
of something that enables lte connectivity and ehspa or something like that
Sent from my iphone killer
abrcrmdl23 said:
So I was looking through my build prop and has anyone else noticed there are a lot odd Verizon references in there like it says the photon is a Verizon wireless world device, and there is other VZW references it also makes mention
of something that enables lte connectivity and ehspa or something like that
Sent from my iphone killer
Click to expand...
Click to collapse
Sprint phones roam on Verizon
so I have never used adb to edit things on my computer do I just open adb up and is there a button to link the 2? i don't really feel like editing these from my phone.
Use root explorer, it makes things soooo much easier.
Is there any change in battery life?
By the way where in the text do i put this syntax's?
Sent from my MB855 using XDA App
Uh what the hell is this shlt. Omg
Sent from my MB855 using XDA App
to pull you have to
Code:
adb pull build.prop/system c:\target folder
Code:
c:\[user_name_\target folder > adb shell
$su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblk3 /system
# exit
$exit
c:\[user_name_\target folder > adb push build.prop /system
c:\[user_name_\target folder > adb shell
$su
# mount -o remount,ro /dev/mtdblock3 /system
#exit
$exit
c:\[user_name_\target folder > adb reboot
{
"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"
}
This only works on Gingerbread, not anything else. We are still working on finding alternative tweaks for ICS and JBThis is a MOD to boost the performance of the Adreno 205 GPU in the Xperia Play. (This mod should also work on other Adreno devices (Adreno 205+) and whilst some people have had some success I cannot confirm which devices other than the Play it works with)
This mod is a joint collaboration/venture of me and CosmicDan. However, as of version 0.2 CosmicDan has unfortunately left the Xperia 2011 range for better things. I wish him every success in the future.
CosmicDan was able to find a variant of the 'adreno_config.txt' file that contains settings that should work on our device. Since finding this we have found numerous combinations of settings that increase the performance of our chips. See below.
What does it do?
The configuration file consists of multiple options, each which do their very own unique 'tweaking' to the way the GPU performs. One of the most notable options we are using is 'triJuice', an explanation of which is below:
If our phones were to have their own driver application, what this would be doing is essentially moving the 'Quality/Performance' slider towards 'Performance'. This tells the GPU to concentrate on 'Performance' rather than 'Quality'.
See CosmicDan's explanation here:
It's common graphics stuff and the same for PC's, we have told the GPU to put a focus on performance instead of quality. But the quality is not sacrificed much, it's barely noticeable. Maybe some games will look not so well, you'll have to test and see.
It's like we've lowered effect and texture detail on a system-wide level, allowing the CPU and GPU to give more time to work on geometry and frame updates and such. Useful because many games don't have settings for graphics quality.
Click to expand...
Click to collapse
Another notable option is 'forceAutoTextureCompression'. This saves RAM and makes texture rendering faster, but the actual loading of the game might be a tiny bit slower - however once it's loaded it will have faster rendering.
A list of possible settings for this configuration file are below (For detailed descriptions please see attached)
Post 3 lists which settings tend to increase or reduce performance, I will not give instructions on how to modify this however if you to intend on making your own config file please use Post 3 as a guide.
Code:
; Performance Analysis
performance=normal
disableExtraSwapBlit=0
ignoreGLFlush=0
; Binning
binning=hw
forceGuardband=0
guardbandValue=0
forceGmemSize=0
gmemSize=0
veboSetting=0
veboSetting=0
numBins_weight=80
numGroups_weight=20
; Logging
log.resolves=0
log.pm4=0
log.pm4mem=0
log.shaders=0
log.sc_dev=0
log.sc_dev_shader_name=sc_dev_dump.txt
log.cffdump=0
log.cffdump_with_ifh=0
log.cffdump_no_memzero=0
log.dumpx=0
log.primitives=0
; Debugging
waitForIdleAfterDraw=0
waitForIdleOnSubmit=0
disableSwapTsIdle=0
clockGating=off
useSafeMode=0
redirectDebugMessages=0
forceChipId=Default
; Primitive Conversion.
convertTristrips=default
convertTrifans=default
convertLineloops=default
shader_sub.write=0
shader_sub.read=0
shader_sub.trivialfs=0
; Features and Performance
facenessCulling=default
vboDataAlignment=natural
enableOptimizedTextureUpdates=1
enableOptimizedVboUpdates=1
forceAutoTextureCompression=1
triJuice=1
enableInlineConstantUpdates=1
enableMemoryPool=1
enableFastClears=1
ditherSafeFastClears=0
shadowGmemInAppBuffers=1
textureTiling=0
preserveZStencilOnSwap=0
allowDepthExport=0
untileDynamicTextures=1
fullSurfaceDynamicUpdatePath=1
useGpuTilingHints=1
; MultiSampling Antialiasing (MSAA)
MSAASmoothing=Normal
MSAABufferAllocation=never
forceMSAAMode=0
MSAAMode=0
VAESEnable=0
VAESGenericError=0
VAESFailNth=0
VAESDoNotFailFirstN=0
VAESRandomSeed=0
VAESFailPercent=0
; 2D Settings
2D.HwBlt=1
2D.eglSwapMode=noidle
2D.forceEglSwapInterval=0
2D.eglSwapInterval=0
; LEIA Features
leiaEnableLrzWrites=0
leiaEnableLrzExpansion=0
leiaExportColorForLrzUnresolve=0
leiaEnableFastLrzUnresolves=0
; Oxili settings.
oxiliDisableLazyUpdates=0
oxiliDisableChunkedUpdates=0
oxiliForceShaderDirectUpdates=0
oxiliForceConstantDirectUpdates=0
oxiliForceIstoreCacheMode=1
oxiliForceCstoreSingleBuffer=0
oxiliForceShaderSingleContext=0
oxiliForceSuperthreadMode=1
oxiliForceVsSingleThread=0
oxiliForceFsSingleThread=0
oxiliForceSingleSp=0
oxiliSkipClears=0
oxiliForceSysmemRender=1
; Other settings
FPSCap=60
allowFloatFBOs=1
suppressTimestampInterrupts=0
GPUIdleTimeout=off
GPUIdleTimeoutMsec=0
Please ignore the values of the above settings unless otherwise stated. The majority of these are stock/default values for our device.
Downloads - Official repository
AdrenoBooster v0.7
AdrenoBooster v0.6
AdrenoBooster v0.5 - Quality Edition
AdrenoBooster v0.4.1 - Battery Edition
AdrenoBooster v0.3 - Minimal Edition - This version will give you the best performance - stability ratio. Whilst the other versions may give you better performance but in some rare instances lower quality/artifacts, this version should give you the best of both worlds.
AdrenoBooster v0.1
AdrenoBooster v0.2
Instructions
Download and copy the ZIP to SD Card. Then flash using CWM.
NOTE: Please ensure you reboot your device after the first boot post-installation of the mod or it will not be active.
Requirements
Init.d support
Root
Any Gingerbread ROM
Screenshots
IMPORTANT!! - Please ensure you thank 'CosmicDan' as well for this fantastic mod. A huge portion of the work has been done by him!
(See 5th post if you would like to 'Thank' him)
Troubleshooting
First, give yourself another reboot - Just in case!
If it still doesn't seem to be working for you, check to see if the files have copied to your device. Check the following locations for the following files with any file manager with Root support.
/system/etc/init.d - Filename: 93adreno
/system/etc - Filename: adreno_config.txt
You should also see adreno_config.txt in the following location if the init.d script is working correctly: /data/local/tmp
If this file is not in this location then chances are you do not have init.d support.
Black screen on boot? See here: http://forum.xda-developers.com/showpost.php?p=40013461&postcount=377
Extras
You can assist with the testing of some of these settings by doing the following:
Open a new text file in a standard text editor (Notepad++ or Notepad for Windows)
Choose values from the above post to put into your configuration file. (Use the attached adreno_config.txt file as an indication of what setting does what)
Save this new file as 'adreno_config.txt'
Copy this text file to your phones SD Card.
Open your File Manager on your phone (I use ES File Explorer)
Prepare adreno_config.txt on your SD Card for copying
Navigate to /Data/local/tmp and paste the file there
Reboot.
Please be aware that if you have any cleaner init.d scripts this will NOT work, as when you reboot /data/local/tmp will be deleted.
Devs/Chefs/Tinkerers
If you would like to add this to your ROM please simply drop a short request in this thread or PM.
After which, please ensure proper credit is given.
Current Antutu Highscore
(With the benefits of this mod) - By CrypticRook
Manually Uninstalling the Mod
Navigate to the following locations and remove the files.
/system/etc/init.d - Filename: 93adreno
/system/etc - Filename: adreno_config.txt
/data/local/tmp - Filename: adreno_config.txt
Tested Settings
Untested:
preserveZStencilOnSwap - enabling might improve performance at the increased risk of visual artifacts
Dangerous:
facenessCulling - Turning on causes crash on boot
FPSCap - setting to anything other than 0 (even to 60 or 100) causes unstable 2D rendering
2D.eglSwapMode=interrupt - Causes unstable/looping 2D rendering. Applications fail to initialize.
fullSurfaceDynamicUpdatePath - reduces 3D performance by around 10%.
Performance Boosts:
forceAutoTextureCompression - Turning this on seems to help a LOT with 3D performance. Might increase load times by a a tiny amount.
triJuice - setting it to the max value of 3 increases particle/shader/lighting performance a LOT with a minor loss in quality
forceMSAAMode - enabling this will force no anti-aliasing as long as MSAAMode is left at 0. Could increase performance on some things but make them look very chunky
2D.HwBlt - Enabling this should enhance GPU hardware acceleration in gingerbread. It says default is enabled but I've set it to 1 anyway.
oxiliForceVsSingleThread=1 - Must be enabled with oxiliForceFsSingleThread=1 for performance increase. Prolonged usage has negative impact (Needs more testing).
oxiliForceFsSingleThread=1 - Must be enabled with oxiliForceSingleSp=1 for performance increase. Prolonged usage has negative impact (Needs more testing).
oxiliForceSingleSp=1 - Must be enabled with oxiliForceVsSingleThread=1 for performance increase. Prolonged usage has negative impact (Needs more testing).
clockGating - Turning this on might save power consumption (Currently being tested more to confirm). However there is no performance drop by having this enabled
Seemed to hurt performance: (I did not test these much, could do with more tests one-by-one)
leiaEnableLrzExpansion - enabling might.... do something.
leiaEnableFastLrzUnresolves - enabling might improve performance
oxiliDisableChunkedUpdates - enabling might improve performance
oxiliForceShaderDirectUpdates - enabling might improve performance
oxiliForceConstantDirectUpdates - enabling might improve or reduce performance
oxiliForceShaderSingleContext - enabling might improve performance at cost of quality
oxiliForceSuperthreadMode - enabling might improve performance or reduce it. Probably conflicts with above one.
suppressTimestampInterrupts - enabling might improve or reduce performance
Null/No Difference - These options made no effect on performance from their default settings
shadowGmemInAppBuffers - no effect on performance or quality
Great! Really looking forward to seeing what you can do
Thanks for letting me know you opened a topic
I've been doing some research and here's what ideas I've found so far:
clockGating - Turning this on might save power consumption. Will need to test if it has a performance hit.
facenessCulling - Turning on causes crash on boot
forceAutoTextureCompression - Turning this on MIGHT save RAM and/or MIGHT increase load times/CPU usage.
triJuice - raising this value might increase performance but decrease quality of mipmapping.
shadowGmemInAppBuffers - disabling might improve performance but break some things
preserveZStencilOnSwap - enabling might improve performance at the increased risk of visual artifacts
fullSurfaceDynamicUpdatePath - enabling might improve performance at the increased risk of visual artifacts
forceMSAAMode - enabling this will force no anti-aliasing as long as MSAAMode is left at 0. Could increase performance on some things but make them look very chunky
2D.HwBlt - Enabling this might enhance GPU hardware acceleration in gingerbread. It says default is enabled but I've set it to 1 anyway.
2D.eglSwapMode - changing to interrupt mode might.... do something. LETS TRY IT!
leiaEnableLrzExpansion - enabling might.... do something.
leiaEnableFastLrzUnresolves - enabling might improve performance
oxiliDisableChunkedUpdates - enabling might improve performance
oxiliForceShaderDirectUpdates - enabling might improve performance
oxiliForceConstantDirectUpdates - enabling might improve or reduce performance
oxiliForceShaderSingleContext - enabling might improve performance at cost of quality
oxiliForceSuperthreadMode - enabling might improve performance or reduce it. Probably conflicts with above one.
oxiliForceVsSingleThread - enabling might improve or reduce performance
oxiliForceFsSingleThread - enabling might improve or reduce performance
oxiliForceSingleSp - enabling might improve or reduce performance
FPSCap - setting to 30 or 60 might help with all-round performance and reduce lag spikes. Maybe.
suppressTimestampInterrupts - enabling might improve or reduce performance
Right, that's a lot of things for me to try one by one. If anyone else wants to, go for it. Just remember it could completely break your boot
Re: [WIP] Adreno Configuration Settings [Improved Performance?]
I did lol.. In the adreno thread xD
Ill make it more clear next time.
I've just tried a few things... Managed to make Antutu crash lot. Just finally completed a full benchmark but then the OS died. Going well so far. Cya in about 7 hours!
Edit: it looks like you can copy it to data/local/temp and the settings will apply for next boot. After which it is then removed from the directory. Which for me makes things a bit easier!
Sent from my R800i using xda app-developers app
Oh by the way, copying the config file to /system/lib/egl/ definitely does nothing. I tested by setting FPS cap to 5, no effect. File needs to be at /data/local/tmp/ - it does *not* get wiped on reboot so its OK.
EDIT: THe file isn't removed from /data/local/tmp/ for me =\ maybe you have an init.d script that erases it or something.
Re: [WIP] Adreno Configuration Settings [Improved Performance?]
Possibly. Ill check.
Btw, I just managed 13fps on the OpenGL ES2.0 test on Antutu. It was hilarious, so many artifacts... But it passed it!
...Until it died on the SD card test. If you use Antutu I suggest doing custom tests and taking SD out. Or reducing OCs. I think my 1.6ghz may be the problem.
Or perhaps we should use stock clock a to base our tests on?
Edit: seems like almost every setting you try also kills the bootanimation lol
Sent from my R800i using xda app-developers app
Spizzy01 said:
Possibly. Ill check.
Btw, I just managed 13fps on the OpenGL ES2.0 test on Antutu. It was hilarious, so many artifacts... But it passed it!
...Until it died on the SD card test. If you use Antutu I suggest doing custom tests and taking SD out. Or reducing OCs. I think my 1.6ghz may be the problem.
Or perhaps we should use stock clock a to base our tests on?
Edit: seems like almost every setting you try also kills the bootanimation lol
Sent from my R800i using xda app-developers app
Click to expand...
Click to collapse
I can't get past the 2D/sprite test in Antutu (the little Androids) it freezes at the end lol. Boot animation was always OK for me....
Yeah, using a stock clock would be a good idea. But I'm on 1.4 ghz anyway because that's what I've always used and always been stable on.
EDIT: I think setting FPSCap to 60 was the reason for Antutu freezing on 2d test.
EDIT2: You are using LuPuS GB kernel right? Because Turbo Kernel has backported KGSL drivers, so that's probably why we not only have different performance scores but may have different results with these configs.
---------- Post added at 01:24 PM ---------- Previous post was at 01:13 PM ----------
DUDE! New Gingerbread record!
/data/local/tmp/adreno_config.txt:
Code:
facenessCulling=off
forceAutoTextureCompression=1
triJuice=3
2D.HwBlt=1
CosmicDan said:
I can't get past the 2D/sprite test in Antutu (the little Androids) it freezes at the end lol. Boot animation was always OK for me....
Yeah, using a stock clock would be a good idea. But I'm on 1.4 ghz anyway because that's what I've always used and always been stable on.
EDIT: I think setting FPSCap to 60 was the reason for Antutu freezing on 2d test.
EDIT2: You are using LuPuS GB kernel right? Because Turbo Kernel has backported KGSL drivers, so that's probably why we not only have different performance scores but may have different results with these configs.
---------- Post added at 01:24 PM ---------- Previous post was at 01:13 PM ----------
DUDE! New Gingerbread record!
/data/local/tmp/adreno_config.txt:
Code:
facenessCulling=off
forceAutoTextureCompression=1
triJuice=3
2D.HwBlt=1
Click to expand...
Click to collapse
OMFG! LEGEND!
Gonna test on mine and report back ASAP. Gimme 10 - 20 mins, depending on when I can get a free sec @ work. Lol. xD
Edit: Unable to replicate your score at the moment. Getting stock scores, most likely something to do with those pesky init.d scripts. Deleting now and will report back shortly
In the next turbo kernel release I'll make the kernel do a symlink from /data/local/tmp/adreno_config.txt to /system/etc/adreno_config.txt (it will be linked before init starts so will apply straight away), that way we can include modified config with ROM's.
You could just make an init.d script do the same thing, but then the ROM will need to be rebooted again (because adreno driver is already loaded).
CosmicDan said:
In the next turbo kernel release I'll make the kernel do a symlink from /data/local/tmp/adreno_config.txt to /system/etc/adreno_config.txt (it will be linked before init starts so will apply straight away), that way we can include modified config with ROM's.
You could just make an init.d script do the same thing, but then the ROM will need to be rebooted again (because adreno driver is already loaded).
Click to expand...
Click to collapse
I think I'll include an init.d script with my ROM, so that in the event someone isn't using your Kernel it will still work as intended.
...At least, after a reboot.
Doing Antutu now btw, ITS CRAZY FAST OMG. About to give you results. UNO MOMENTO!
OMFG!
This actually brought a tear to my eye... Lmfao... XD
Spizzy01 said:
I think I'll include an init.d script with my ROM, so that in the event someone isn't using your Kernel it will still work as intended.
...At least, after a reboot.
Doing Antutu now btw, ITS CRAZY FAST OMG. About to give you results. UNO MOMENTO!
Click to expand...
Click to collapse
Yeah I realized that too, already done it for Turbo UI Classic (which is uploading now). This should work:
/system/etc/init.d/93adreno:
Code:
#!/system/bin/sh
#
if [ ! -h /data/local/tmp/adreno_config.txt ] then
ln -s /system/etc/adreno_config.txt /data/local/tmp/adreno_config.txt
fi
EDIT:Woohoo! Play broke the 7000 mark
Now I wonder how Jellybean on Turbo Kernel performs.... maybe closer to 8000 lol! And the visual quality of the orc fight 3D test looked OK for you yeah?
CosmicDan said:
Yeah I realized that too, already done it for Turbo UI Classic (which is uploading now). This should work:
/system/etc/init.d/93adreno:
Code:
#!/system/bin/sh
#
if [ ! -h /data/local/tmp/adreno_config.txt ] then
ln -s /system/etc/adreno_config.txt /data/local/tmp/adreno_config.txt
fi
Will be good to know if the results on LuPuS GB kernel are worse, better or the same with this config.
Click to expand...
Click to collapse
My test was done on LuPuS GB.
Sorry - I moved back from your Kernel last night. =x
Thank's for the script. I'll add it to v0.5 Aurora now. xD
Edit: Agreed. JellyBean should have crazy scores... Right, I'm gonna test a few of the other configs. From that list you've done, can you 'tick' off which you have already checked please? Just so I can continue where you left off at.
Orc fight looked perfectly fine. If it were a HD movie I'd say it had a low bit-rate, but it's not... So I have no idea what to call it, but it does look ever so slightly more grainy. But this is barely noticeable at all.
I looked in /data/local/tmp/ and there was no adreno_config.txt I'm using joka wild any ideas did I have to do something before hand using LuPuS v6 480p I'm very interested because I use this a a gaming device as I have a nexus 4
Spizzy01 said:
My test was done on LuPuS GB.
Sorry - I moved back from your Kernel last night. =x
Thank's for the script. I'll add it to v0.5 Aurora now. xD
Edit: Agreed. JellyBean should have crazy scores... Right, I'm gonna test a few of the other configs. From that list you've done, can you 'tick' off which you have already checked please? Just so I can continue where you left off at.
Click to expand...
Click to collapse
I edited my last post since you uploaded results
That's OK, I'll still win the record by being first to test Turbo UI (JB) score lolz
EDIT: OK, I'll edit that list.
extremetempz said:
I looked in /data/local/tmp/ and there was no adreno_config.txt I'm using joka wild any ideas did I have to do something before hand using LuPuS v6 480p I'm very interested because I use this a a gaming device as I have a nexus 4
Click to expand...
Click to collapse
You need to move the file there yourself.
See attached.
Move the file to /Data/Local/tmp and reboot. Ensure you have no init.d scripts that clear cache or tmp though, as it will not work.
OK here's what my data is.
Untested:
clockGating - Turning this on might save power consumption. Will need to test if it has a performance hit.
shadowGmemInAppBuffers - disabling might improve performance but break some things
preserveZStencilOnSwap - enabling might improve performance at the increased risk of visual artifacts
fullSurfaceDynamicUpdatePath - enabling might improve performance at the increased risk of visual artifacts
oxiliForceVsSingleThread - enabling might improve or reduce performance
oxiliForceFsSingleThread - enabling might improve or reduce performance
oxiliForceSingleSp - enabling might improve or reduce performance
Dangerous:
facenessCulling - Turning on causes crash on boot
FPSCap - setting to anything other than 0 (even to 60 or 100) causes unstable 2D rendering
Performance Boosts:
forceAutoTextureCompression - Turning this on seems to help a LOT with 3D performance. Might increase load times by a a tiny amount.
triJuice - setting it to the max value of 3 increases particle/shader/lighting performance a LOT with a minor loss in quality
forceMSAAMode - enabling this will force no anti-aliasing as long as MSAAMode is left at 0. Could increase performance on some things but make them look very chunky
2D.HwBlt - Enabling this should enhance GPU hardware acceleration in gingerbread. It says default is enabled but I've set it to 1 anyway.
Seemed to hurt performance: (I did not test these much, could do with more tests one-by-one)
2D.eglSwapMode - changing to interrupt mode might.... do something. LETS TRY IT!
leiaEnableLrzExpansion - enabling might.... do something.
leiaEnableFastLrzUnresolves - enabling might improve performance
oxiliDisableChunkedUpdates - enabling might improve performance
oxiliForceShaderDirectUpdates - enabling might improve performance
oxiliForceConstantDirectUpdates - enabling might improve or reduce performance
oxiliForceShaderSingleContext - enabling might improve performance at cost of quality
oxiliForceSuperthreadMode - enabling might improve performance or reduce it. Probably conflicts with above one.
suppressTimestampInterrupts - enabling might improve or reduce performance
I made a quick Update ZIP to flash the mod/script and updated the first few posts.
You have been fully credited of course in the updater_script
Gonna look into other settings now.
Edit: I'm not sure I like the new Mediafire layout :|
Hi all.
I was wondering,what "homemade" tweaks like init.d/script manager scripts or build.prop do you use with your S3...
When i say homemade i mean tweaks you apply on your own,not any tweaks that come with the rom you use.
Tweaks that you've tried and liked,tweaks that you'd recommend.
Here's the things i do to make my S3 more lag free:
-Use Greenify
-Custom script for script manager attached below(updated 27/3/13)
-Build.prop almost clean as i found many of the tweaks unusable in 4.1 or to interfere with the System.
-No init.d tweaks currently (sometimes zipaling and sqlite defrag)
-Custom STweaks settings(Perseus) including overclock,they're too many to write if you want i can attach some screenies.
-Currently testing Crossbreeder mod but with the above my S3 was already fast enough so not much differency,if any.
-zRam 650mb script for a kernel that supports zRam attached below also to be used for script manager.
User's tweaks:
Build.prop tweaks
dxppxd said:
This one is for the soft keys, tablet-like home, menu, back buttons on screen (with respective screen reduction). Adding the line on build.prop:
Enable
qemu.hw.mainkeys=0
Disable
qemu.hw.mainkeys=1
Popular tweak, for the sake of those who don't know them yet.
Click to expand...
Click to collapse
So that's my list right now.
Got anything good to share?
Re: "Homemade" tweaks for your S3.
This one is for the soft keys, tablet-like home, menu, back buttons on screen (with respective screen reduction). Adding the line on build.prop:
Enable
qemu.hw.mainkeys=0
Disable
qemu.hw.mainkeys=1
Popular tweak, for the sake of those who don't know them yet.
dxppxd said:
This one is for the soft keys, tablet-like home, menu, back buttons on screen (with respective screen reduction). Adding the line on build.prop:
Enable
qemu.hw.mainkeys=0
Disable
qemu.hw.mainkeys=1
Popular tweak, for the sake of those who don't know them yet.
Click to expand...
Click to collapse
Thank's,i read many guys use this one.
Bump?
No one uses his own tweaks,only what comes with the rom?
nfsmw_gr said:
Bump?
No one uses his own tweaks,only what comes with the rom?
Click to expand...
Click to collapse
well, yes But i'm interested in the script you posted. What exactly did you change the minfree values and ratios to ? Would these values give more multi-tasking or are they engineered towards having free ram ?
Also Greenifying google maps (as a user app) gives a huge boost to battery life, unless you have Google Now enabled
ArbiterGR said:
well, yes But i'm interested in the script you posted. What exactly did you change the minfree values and ratios to ? Would these values give more multi-tasking or are they engineered towards having free ram ?
Also Greenifying google maps (as a user app) gives a huge boost to battery life, unless you have Google Now enabled
Click to expand...
Click to collapse
Hehe..
Well this is leaning towards better multitasking and most importantly lag free system and multitasking.
I lowered the adj values a bit because stock S3 were killing my apps a bit too fast for me,they're "inspired" from the original Galaxy S only a bit modified to suit the S3.
I found them to be working nicely for me,give them a go if like and post here or pm me.
Except from the adj values i modified a bit the values of sysctl.conf like dirty ratio vfs cache pressure and some nr_request config.
I changed my values a bit right now and also disabled iostats to make it even more less laggy so i'll upload this when i get home.
I usually have around 70mb free ram but my S3 doesn't lag at all,yay!
Now trying 500mb zRam and it's going very nice...i may add it to the op soon...
OP updated 27/3/13.
As asked in the title above.
If it is then which apps will work. I need the fingerprint sensor and great battery life so I can not go with a CM based rom but would like to try some changes to improve the performance in stock. I see the governor in use is marked interactive but have not gotten to much more details about the cpu perimeters used.
I swear by Kernel Adiutor, and actually used it on my rooted stock rom Honor 5X to do exactly this and set the governor to batterysaver. Great results, though being a stock kernel, there's obviously a lack of options/governors.
Try this (screenshots) turn off use sched load on both Cpus and migration notif also.
Build.prop add this:
wifi.supplicant_scan_interval=300
power.saving.mode=1
ro.vold.umsdirtyratio=20
ro.media.enc.jpeg.quality=100
cpu.fps=auto
gpu.fps=auto
ro.fps_enable=1
ro.fps.capsmin=30fps
ro.fps.capsmax=60fps
boot.fps=25
U can play around with the hotplug driver to manage cores at sys/devices/system/cpu/cpu0/core_ctl
Thats what ive gotten so far
Thanks. I started some adjustments with kernel adiutor and it has gotten a little better. I will try the build.prop tweaks.
It would be nice to find out the cause of lag in stock.
Well with the fps/build.prop tweaks my Phone seems lagg free. Lets see if you can make a difference!
Is it me or is the build prop in this phone unusually large! ?
johnciaccio said:
Is it me or is the build prop in this phone unusually large!
Click to expand...
Click to collapse
It is just add that line what ive posted somewhere
Introduction:
Hi everyone and welcome to another guide. Today I will be teaching you how to get the most out of that Exynos 9820, inside that S10 of yours. We will be focusing on three main things in this guide. Debloat, Mtweaks and DVFS (The ace up our sleeves). So without further ado, lets get right to it.
Requirements:
1. A OneUI ROM, or custom ROM, with Magisk - If the ROM comes pre-debloated, even better, you can skip Step 1.
2. MTweaks - https://github.com/morogoku/MTweaks-KernelAdiutorMOD/releases - Mtweaks is going to be controlling our kernel and helping us get extra power.
3. A root explorer - I use solid explorer, its the easiest and looks the nicest but has a trial date, although any explorer is fine.
Step 1: Debloating:
Now this should come as no surprise, that having a light operating system, will obviously benefit performance. Now I'm not gonna sit here, and type all the apks, permissions etc. that you have to remove. However the three apks that are essential to better gaming performance, are GameLauncher, GameOptimizingService and Gametools. I will explain why in the next section:
1. Gamelauncher: The app in itself isn't that bad, the main problem is its control on the performance of the device. It isn't the main culprit here, but any link that the service has to the kernel needs to be stopped for the future steps.
2. GameOptimizingService: This is the main culprit and the service I am referring to. GOS has this "feature" to control the performance of the device, and whether to focus on performance or focus on battery. After extensive testing, this app does the inverse of what it is supposed to do as it tends to throttle performance, regardless of what setting you place it on and for the steps I'm going to explain later, you will know anything linked to controlling the kernel needs to be killed.
3. GameTools: Once again, not the main culprit, but as I have stated before, it has a link to the throttling service, and unfortunately has to go, along with the other three apks.
The path for the three apks:
system/app/GameOptimizer
system/app/GameOptimizingService
system/priv-app/GameHome
system/priv-app/GameTools_Dream
system/etc/permissions/privapp-permissions-com.samsung.android.game.gamehome.xml
system/etc/permissions/privapp-permissions-com.samsung.android.game.gametools.xml
system/etc/permissions/privapp-permissions-com.samsung.android.game.gos.xml
I know that most people love the organization skills of Game Launcher and the functionality of Game Tools, but all I ask for is a little leap of faith here, when I say they aren't good for gaming performance. Of course you can continue the guide without the removal of these apks, but I cannot guarantee the performance I promised at the start of the guide.
Step 2: Disabling DVFS
The second step on this journey is going to be the disabling the absolutely horrible thermal throttling system on any Samsung device known to man, called DVFS. It is singlehandely the main reason, why your exynos chipset cannot play games at the same framerate as a Snapdragon chipset from two years ago, and is also why AOSP tends to not throttle like OneUI does. Today we will be killing it, and restoring the CPU and GPU performance of your device.
Note: Disabling DVFS will have lots of obvious benefits which will be very noticeable, but does come with its own sets of downsides. Once killed, you have to reboot the device to re-enable DVFS as with DVFS disabled, there is nothing telling the kernel to be conservative and therefore, there will be a slight increase in drain while using apps. All you have to do to fix it, is reboot the device and DVFS re-enables itself.
Note 2: Every time you reboot, you will have to repeat this process as DVFS does re-enable itself, so keep this guide handy, or memorize the steps.
Lets get started. (I will post screenshots of me using solid explorer)
1. Open up your root file explorer, grant Magisk permissions and goto the root folder (or main system directory)
2. Once you are in the root directory, goto the folder called sys
3. Then goto the folder called devices
4. Then goto the folder called platform
5. Now search the word "mali"
6. Press on the first folder you see
7. Now look for three files, dvfs, dvfs_max_lock and dvfs_min_lock
8. Press and hold on the file dvfs and goto its properties
9. Now goto its permissions and disable all its permissions. There should be a single tick mark on any of the permissions.
10. Now save the file and do the same for dvfs_max_lock and dvfs_min_lock
Thats it. You have now disabled the thermal throttling system on your device. Now remember, by doing so, your device won't throttle until its hit the chipset thermal limit (which is a lot higher than DVFS's thermal limits), so don't run the overclock we plan on using unnecessarily (You don't need max performance to scroll through Instagram XD)
Step 3: MTweaks
What is MTweaks? Mtweaks is a kernel manager that was built by @morogoku specifically for exynos based devices. Now with this kernel manager, you now have access to your CPU and most importantly your GPU. When we killed GameLauncher, Gametools and GameOptimizationService, we removed the ability for GOS to throttle the device in advance. When we disabled DVFS, we set the kernel free of the five year old messing with the settings, when things got a bit too intense, and now we have the ability to fully utilize our kernel.
Now after extensive testing, touching the CPU frequencies tends to have the inverse effect unless your underclocking to save power, so we're not going to adjust its frequencies. The GPU is going to be the main area of improvement. Before you go-to play whatever game you want to play, if it is something light, set the minimum frequency to half of the maximum frequency. So if its something light like candy crush, set the GPU's minimum frequency to 325mhz and the GPU Power Policy to Always ON. If you plan on playing something that's going to require a lot more horsepower, like lets say, PUBG Mobile with UHD and all settings maxed out via GFX Tools (Yes I am a madman), put the GPU's minimum frequency at 702mhz and the GPU Power Policy to Always ON, and thats it, your done. You should now be able to outperform or at least match the performance figures given in your Antutu Benchmark. Keep in mind obviously the thermal restrictions, and as a rule of thumb, check Mtweaks once in a while to check your temps. The main temp I've noticed to take an increase is the battery, and keeping it below 45C is optimal while gaming. The GPU and CPU don't need to be monitored.
Disclaimer: I will not be held responsible for any nuclear explosions because you pushed your device too hard by using this guide. Please be responsible and be aware that your phone is a phone, not a gaming PC with a huge fan to cool it off
Conclusion:
I will post a screenrecording of my s10's gameplay of PUBG Mobile on UHD with all settings maxed out on GFX Tools, and screenshots of MTweaks and solid explorer. I hope this guide helped you achieve the gaming performance you desired out of your Exynos based Galaxy S10. Hit the thanks button if I helped you
Well, it seems to do the job very well. No lags for now, im playing full graphics with wqhd+ display settings (like never before, it really fly). Cons: a little more battery consumption and more heat (but no so much really). If this was an S7 it will burn your fingers for sure. So, i think this mod on S10 can't damage the phone, only the battery life can be shortened on a large-term if the use is heavy. But... is one thing on another.. i prefer playing good. Thank you for the guide.
Skulldron said:
Introduction:
Step 1: Debloating:
Now this should come as no surprise, that having a light operating system, will obviously benefit performance. Now I'm not gonna sit here, and type all the apks, permissions etc. that you have to remove. However the three apks that are essential to better gaming performance, are GameLauncher, GameOptimizingService and Gametools. I will explain why in the next section:
1. Gamelauncher: The app in itself isn't that bad, the main problem is its control on the performance of the device. It isn't the main culprit here, but any link that the service has to the kernel needs to be stopped for the future steps.
2. GameOptimizingService: This is the main culprit and the service I am referring to. GOS has this "feature" to control the performance of the device, and whether to focus on performance or focus on battery. After extensive testing, this app does the inverse of what it is supposed to do as it tends to throttle performance, regardless of what setting you place it on and for the steps I'm going to explain later, you will know anything linked to controlling the kernel needs to be killed.
3. GameTools: Once again, not the main culprit, but as I have stated before, it has a link to the throttling service, and unfortunately has to go, along with the other three apks.
The path for the three apks:
system/app/GameOptimizer
system/app/GameOptimizingService
system/priv-app/GameHome
system/priv-app/GameTools_Dream
system/etc/permissions/privapp-permissions-com.samsung.android.game.gamehome.xml
system/etc/permissions/privapp-permissions-com.samsung.android.game.gametools.xml
system/etc/permissions/privapp-permissions-com.samsung.android.game.gos.xml
Click to expand...
Click to collapse
If only disable the packed with some app It's same?
xaloundros said:
If only disable the packed with some app It's same?
Click to expand...
Click to collapse
While I haven't tested this myself, in theory it should work, however further testing could be required