Related
Hi
I found some tweak to improve battery life..not bad... i get it from some old forum when i am using TP.
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Battery]
change from 5000 to 20000
Note: Remember to restart
You harm, you can always revert it back if you think it does not work :>
Sorry I didnt want to put them on the already Tweak post cos I not sure it will work for other :> Until it is confirmed by everyone. I work for me at least :>
what is it thats being changed exactly?
This tweak is for changing the amount is polled to the battery status so often that it actually drains the battery a LOT.
From default 5000 (5seconds) to 20000 (20seconds)
ah.. i see. problem is, i dont have a way to edit the regestry on the device lol.
Lyian said:
ah.. i see. problem is, i dont have a way to edit the regestry on the device lol.
Click to expand...
Click to collapse
http://www.google.com/search?q=registry+editor+pocketpc
is it harmful in any way??
I just recently learned about modify the build.prop...and I came across camera build.prop tweaks and I was wondering if they were necessary for the epic touch 4g.
the tweaks i found were:
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
My phone is rooted with Blazer Rom and has the lastest El26 modem...I use the thunderbolt script package...and crawj's modified high bit rate camera...
thanks in advance
Couldn't tell you honestly. I don't use build.prop camera edits - mine are done in the media_profiles.xml located in /system/etc
Most edits in the build.prop so far have been disproved to do anything. I think at one time long ago Android may have used the build.prop for certain settings but now I think it's more or less just an info file for some programs to read. That way they know which settings to use, applications available, or information to display.
Not saying Crawj doesn't know what he's doing - he's a great dev. However we all know too well that old habits or ways of thinking die hard. Happens all the time with technology. Just my personal opinion.
KCRic said:
Couldn't tell you honestly. I don't use build.prop camera edits - mine are done in the media_profiles.xml located in /system/etc
Most edits in the build.prop so far have been disproved to do anything. I think at one time long ago Android may have used the build.prop for certain settings but now I think it's more or less just an info file for some programs to read. That way they know which settings to use, applications available, or information to display.
Not saying Crawj doesn't know what he's doing - he's a great dev. However we all know too well that old habits or ways of thinking die hard. Happens all the time with technology. Just my personal opinion.
Click to expand...
Click to collapse
ah i see which would explain why an init.d script supperceeds whats written in the build.prop...if both are trying to change the same value...so if i added those i guess they are called scripts (not sure if they have a different name than init.d) does it make a difference or do i need to remove them because of the uncertainty of if they are functional...i guess what im getting at is does extra clutter in the build.prop affect anything...
i think crarjs modified camera makes its changes in the media.profile like you mentiontioned... i found those tweaks and added them myself to see if they would do anything
do u make added anything your build.props or because of the actual functionality is uknown do u just not mess with it?
I just don't touch the build.prop at all since from what I've seen it does nothing. I will post my media_profiles.xml tomorrow for you to look at if you want but I don't know of any scripts to put in an init.d file. Doesn't mean there isn't some code out the to edit a property like the flash duration, intensity, and so on.
Sent from my SPH-D710 using XDA App
lets see, change dpi in build.prop, yep. Change vm heap size, yep, Im gonna say the other build.prop settings will work if entered correctly, and actually work on your phone model.
Sent from a phone with kNOw CIQ
TeamERA said:
lets see, change dpi in build.prop, yep. Change vm heap size, yep, Im gonna say the other build.prop settings will work if entered correctly, and actually work on the on your phone model.
Sent from a phone with kNOw CIQ
Click to expand...
Click to collapse
Of course those can also be set in an init.d file. What do you think the V6 and V8 scripts do? The numbers aren't magical, though I'm sure at times we've all thought so
The OP has understood it correctly - most things you change in the build.prop do absolutely nothing. Especially if they don't exist in our phone (see: hspa class). However, for the properties it can effect - well those are superseded by the init.d scripts or by any shell script.
EDIT: I also believe (not 100%, I'm not a dev) that most of the cameras properties as far a quality, resolution, file format, etc, are set in the .xml file. So entering anything contradicting what's in the .xml will be a waste of space just cluttering up your build.prop file and possibly increasing boot times.
well on that note i am going to remove what ever camera tweaks i added because as i already mentioned im using an already modified camera...and to be honest i just realized the values i added in the build.prop were already set and standard on the stock camera...so lord only knows what kind of confusion im causing lol
lunchboxVA said:
well on that note i am going to remove what ever camera tweaks i added because as i already mentioned im using an already modified camera...and to be honest i just realized the values i added in the build.prop were already set and standard on the stock camera...so lord only knows what kind of confusion im causing lol
Click to expand...
Click to collapse
Well here's that media_profiles.xml I told you about. Feel free to use it, I know some of the devs have made their own so I'm not taking credit. Mines actually a modified stock version made for potatomans tweaked camera. Just make sure to change the permissions (rw-r-r) and ownership of it after putting it in /system/etc if you do use it.
thank u...pardon the dumb question but how do i read it will it open in wordpad?
I would use notepad or download Notepad++ (it's free). The second option is probably the best but I've never really had an issue using the other.
Hello,
I'm reactivating this thread since I cannot talk with samm every now and then to update the OP from this thread here.
What works:
It is stable for a daily driver but there are definitely things that doesn't work. For starters, the Hero is too small for ICS since we don't have any GPU posibility. Adreno 130 drivers are oh, too small and too bad for animations on ICS, they suck even in GB and Froyo. Still, the statusbar and fling are much smoother than other android releases because that's how ICS is built. It is more RAM friendly and it looks, well, sexy!
Will try and update this rom when it will be possible. We might jump on the bandwagon of 4.0.4 if I can make it to move faster than it moves right now (yes, I have an experimental build).
If one of you want to join me to develop this rom further, send a PM and I will send you some details about what is in the works, how far it is. I know there are few people that can work on builds here on Hero thread but if we work together, we can pull this out one more time.
FLASH THIS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR:
- YOUR BRAIN
- YOUR HOUSE
- YOUR PHONE!
ON with the ROM. What has been changed:
Added:
Code:
- Google Music apk (yes, official google music app);
- Explorer.apk
- Latest and greatest LV Kernel 1.2+
- Revert to Evtoolbox back from 4.0.3 builds
- Set the cpu to scale at 352-672 from startup
- Tweaked the build.prop a little (added some experimental lines)
Why this is v3?
Because the memory management inside the kernel (remember, INSIDE THE KERNEL) is tweaked and fixed to nice values in order to allow our hero to better multitasking (you can find these values in my other rom called 1ceCream BEAST Flavor). No need for tweaks in init.d to do the job, no bull****.
Just plain and simple!
If you are texting someone, sending an email, playing a game, doing something, and you are locking the screen, after unlocking you will find that the application is ON the screen, and is not closed how it is in many other roms for hero. The multitasking with my values is so much better, you will definitely like it!
Click to expand...
Click to collapse
The rom moves fast, even if it is ICS, I have the animations on and no force GPU in Developer settings and it is still moving so much fast than the older builds.
Overall, I am happy with this release and I hope you will be too! Post me some of your opinion and tell me if it is fast or am I dreaming!
Some user's feedback:
Loxxy said:
wow 'HeroICS v3' is running on rocket power !!! what the hell
amazing job
Click to expand...
Click to collapse
Carrier Internet connection issue:
- Create Manual APN for provider's internet connection.
DOWNLOAD HeroICS v3
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Good work. Flashing now.
How about keeping this as lite as possible, only the absolute essentials pre-installed, everything else as optional zips / apk. For instance, I personally have no use for the music player.
I would really like to see a bare bones, fast and stable ics rom where you just add what you need.
---------- Post added at 03:56 AM ---------- Previous post was at 03:16 AM ----------
Unexpected reboot just as I was about to install Opera Mini. Followed by: "New Sim Detected, reboot required." Never seen that before.
I've applied CSL00's values.
Wonder if V6 Supercharger or Auto Memory Manager can improve things.
Play Store is noticeably faster. Unsure if was CSL00's values or the introduction of AMM.
Regarding the error message: 'No more room on this home screen.'
In Play Store app. Menu > Settings > Deselect Auto-add widgets.
Second unexpected reboot, otherwise things are getting faster. No wifi issues, BT still won't pair.
Running AMM on 'Aggressive.'
CSL00 said:
If you make these changes maybe you'll see better performance, the hero can't handle dithering on anything higher than stock GB or Sense froyo and doesn't have enough RAM for 48mb of dalvik heapsize. I may be wrong but these always worked for me in the past altough ICS is supposed to be better on RAM.
dalvik.vm.execution-mode=int:fast
dalvik.vm.heapsize changed to 24m or 32mb
persist.sys.use_dithering=0
Click to expand...
Click to collapse
dalvik execution mode was on fast until I changed it in the last second to "jit".
vm.heapsize was changed to 48 because I was testing 32 mb and I saw that it takes a little while to enter in one application. With 48 mb the time is reduced somehow. Please feel free to change it to 32 mb if you want. Dithering, well here is a mistery, I don't know if this works in ICS. It does look a little better than with it changed to 0 and my phone can suport dithering pretty well.
About the reboots, please install set cpu and set your max cpu frequency to a respectable value such as 691 or lower. I suggest using governor smartassV2.
The whole rom does feel a little snappier but we have an issue when someone calls you and after 20 seconds the call gets interrupted. I'll look into that today after work and see if I can fix it somehow.
I've tried Supercharger, the V8 doesn't wanna start on ICS and when applied V6 with option 6, the phone just got stuck on bootloop.
The reason that I've made it like this with apk.s that you can easly uninstall is that I didn't want you guys to have to flash any other optional zips or anything. But as I said, feel free to do what ever you want and uninstall those unused apps.
Oh, If you want to try supercharger yourself, you have to first delete these scripts from /etc/init.d:
03tweaks
04netspeed
05fixsdcardspeed
06loopy_smoothness_tweak
15cleanup_init_ram
16sqlite_optimize
17speedy_modified
Just to avoid any unexpected issues.
L.E:
CAN SOMEONE PLEASE, make a LOGCAT while you are in a call and save it to a txt? I want to see if we can narrow down the problem of disconnecting. I am unable to make a logcat atm.
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
lost101 said:
1ceb0x, back to using your original build.prop, and Setcpu. Things seem more stable.
I'm looking for a notification toggle (cm-style) that has no icon when running (or only hides it, leaves a space.)
I will make a logcat, but I've tried aLogrec and all it seems to produce is an empty file. Should it not be dumping info on any activity I do?
Click to expand...
Click to collapse
Seems stable than samm000's build.prop?
Glad to hear this.
As for the logcat, you cannot use any of the readers on the market because they will not work on ics. I've tried to make a log using android sdk but it seems that we need a file called 'main' in /dev/logs. I tried to make the file manually but then I've encountered an EOF read error on cmd. I forgot to make permissions for the respective file. Will make it again now and see how it goes.
As for cm notification toggle, I don't know what are you talking about. The notification toggle on ICS is nicer than any other available .
Tell me if you have calls issue (your call is disconnected after some seconds)?
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
6mins+ this time and still going...
lost101 said:
Well it is probably more stable because I reduced the cpu speed.
In a voicecall now, 2mins+. Call lost around 3 mins.
Click to expand...
Click to collapse
Did you checked the box "Force GPU rendering" in Develop Options?
Is it stable because I've added graphical tweaks and some tweaks to speed...
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+.
I ended the call myself at 22mins.
lost101 said:
Yeah, 'Force GPU rendering' is enabled. In a voicecall now, 10mins+
Click to expand...
Click to collapse
10 minutes without disconnecting? What's your settings on network? GSM ONLY, or WCDMA preferred?
(to see this, please go to dialer and dial *#*#4636#*#* , then go to Phone information, scroll down and you will see the value above the button "Turn Off Radio").
as default the version is WCDMA preferred. What Radio firmware are you using?
also, did you installed Habarug's tweak to hide the end button call during a call? (it's in samm000's thread).
this information will be helpful! cheers
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
lost101 said:
WCDMA preferred. Radio: 63.18.55.06PU_6.35.15.11
I have not installed Habarug's tweak.
Click to expand...
Click to collapse
and you had 10 minutes without disconnecting? you were able to end the call normally?
1ceb0x said:
and you had 10 minutes without disconnecting? you were able to end the call normally?
Click to expand...
Click to collapse
It was 22mins when I ended the call myself.
Regarding notification toogle this is what I mean: 15 toggle status bar as implemented in this rom. Check the video.
Very ODD.
I have 63.18.55.06OU_6.35.15.01 on my device with WCDMA preferred but I keep getting call disconnected after 10 seconds or so.... regarding the notification status bar power widget, I don't know what to say. I'm not a dev so...
i'm trying to find a way to make a log cat of the calling issue because I don't really want to change my radio because my version seems to be battery friendly...
thank you for your support
Obviously the notification thing isn't even important right now. I shouldn't really have mentioned it.
I thought this radio was considered one of the best to be using, and find the battery life to be good on it.
Don't know if its the best really. But I've flashed it anyway. Since this will end my calling interrupt, it will be a small price to pay if the battery doesn't play well.
Will test the voice calling. Btw, I am maybe working on RC2, with some new tweaks and fixed latinime.apk keyboard..
can confirm right now that the latinime.apk is fixed.
@Habarug: are you using my mod or sam's rom?
Thanks lost, will try your radio, im on .14 atom
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
lost101 said:
Just to clarify, the radio I am using still has calls dropping with ics. It seems to happen at random times. 1 minute into a call, 3 minutes or not at all. Maybe it's because of the numbers I am ringing. I can't be sure they would not drop anyway. But it sounds like it is doing better than some other radios.
Also, what about having a build based off ics 4.0.4?
Click to expand...
Click to collapse
we have to fix this issues first and then talk about another version. anyhow, 4.0.4 is much laggier than this version. i saw a bit of logcat and some awkwardly errors regarding the "animations" but i was unable to save the log for future use.
I've asked Maclaw, a dev from Galaxy Gio/Fit/Mini who made CM9 possible on those device to look at our build and maybe with some luck he can see something that make this calls drop...
managed to past 3 minutes in call with your radio version lost101. cheers
L.E: I am unable to send PM's. so i cannot ask Maclaw for help.. too bad! I'll just have to post on their op!
Come on people.. test the build!
i searched for this topic but I couldn't find any thread about sysctl tweaks for the Desire. So I think it's about time...
(hope this is the right Forum?)
I found one thing in a different device's forum though, that I did try on the Desire with success:
vm.swappiness = 0
even though Android doesn't have swap by default (and my Desire neither) there was vm.swappiness set to 20. so setting it to 0 should not make a difference...but it does!
it massively increased responsiveness and speed of my Desire, as well as raising the score in Antutu benchmark from around 2500 to around 2800 points!
And I don't see any disadvantages.
I'm not sure though if this setting is set on stock kernel too because I'm using CM7, but it seems the same (nexus7 has swappiness 60, and does it have swap? couldn't really see a difference there tho)
You mostly find posts where people wanna set it to some value if they use swap, but setting it to 0 seems to be some secret?
Is it the same on other ROMs/kernel/devices? Try it and report back please
I like my 'new' phone but I guess there could be tweaked even more and people already tried...
So does anyone else have found good sysctl tweaks for our good old Desire?
to be continued...
Links:
Some infos on sysctl settings for HTC Flyer: http://forum.xda-developers.com/showthread.php?t=1470125
Some nice app to edit sysctl and other settings http://www.3c71.com/android/?q=node/916
Tried it, don't really notice any difference not better nor worse.. Thanks for the tip though, gonna leave it to test for some longer time..
Greetz
TimHermans said:
Tried it, don't really notice any difference not better nor worse.. Thanks for the tip though, gonna leave it to test for some longer time..
Click to expand...
Click to collapse
hmm what ROM do you use? Maybe that makes differences. Or your Desire didnt lag before anyway
Thanks for your reply.
I'm on VJ's CM10.1 v6.2
Greetz
*I no longer have this phone so these values and builds will not be updated if you would like to add new values for this phone or add tweaks to existing builds then feel free to post them on this thread.
*This requires root
I decided to make this thread to share with you guys a tweak that I found that really helped my battery life. I was never able to get more than 3hrs of screen on time on my phone or get decent standby times on lollipop like I did when I was on marshmallow but I may have found a solution. I stumbled on this thread: http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557 by soniCron give the guy a thanks while you're over there. This guide is for CPU settings to increase battery life and performance. I saw that it was for the Nexus 5x and because the g4 and 5x have the same CPU I decided to give it a shot. I never noticed much performance improvements but I did notice a big battery improvement like I said before. There are many different flavors of tweaks to try and I ended up going with GhostPepper and then tweaking it to my liking.
Here are my settings for the G4 based on GhostPepper
https://docs.google.com/spreadsheets/d/1Yn-qtExspkzINkhtjHBhQyrbtSdMLH9ls4booeqsfh4/edit?usp=sharing
* 8/14/16 If you used the settings from the beta build Turtle or modded GhostPepper check to make sure your settings are up to date. I just changed some target load numbers slightly and fixed an error with the values for above_hispeed_delay. I also fixed an error with a value for the modded GhostPepper settings.
*8/15/16 Slight changes to beta settings to increase smoothness and battery life slightly
*8/17/16 Small change to beta settings to increase smoothness more and changed development status of Turtle to stable beta meaning you can probably use it without worrying about battery drain or slow downs though it does need more testing to move it to daily use
After changing these values with some type of kernel tweaking app I used kernel adiutor, make sure all CPU boosting settings like touch boost or input interval are off or at 0
After applying these settings you should see noticeable improvements in battery life
If you find any better settings add them to the thread.
*I am not responsible if your phone dies, bootloops, bricks, or causes the world to explode.
Unfortunately, this requires root, so no-go on MM.
konradsa said:
Unfortunately, this requires root, so no-go on MM.
Click to expand...
Click to collapse
I meant to put that in the post updating it now.
I found simply changing my governor to interactive greatly increased my battery life. I am going to try this and see what I get. I'll post results.
trxrider31 said:
I found simply changing my governor to interactive greatly increased my battery life. I am going to try this and see what I get. I'll post results.
Click to expand...
Click to collapse
OK great this uses the interactive governor.
New Beta Settings
I have updated the main post with a link to a list of settings one of them is the one that was on there before and the other is one I am working on. The beta I just added seems fairly decent from my testing though this is my first time trying to make my own The small core settings are ones that I did and the Big core settings are slightly tweaked GhostPepper settings. This one seems smooth from my testing maybe not as smooth as the first one I added but it does seem to have a little better battery life when doing light gaming. If your adventurous go for it and report any issues and the battery life you are getting. I also turned all thermal settings off like Core control, VDD, and Temp throttle. It didn't have any affect on my temps if anything they went down a little maybe 1 or 2 degrees but did seem to help smoothness and making sure the governor settings acted right on both profiles.
*I am not responsible if your phone dies, bootloops, bricks, or causes the world to explode.
*If you used the settings from the beta build Turtle or modded GhostPepper check to make sure your settings are up to date. I just changed some target load numbers slightly and fixed an error with the values for above_hispeed_delay. I also fixed an error with a value for the modded GhostPepper settings.
Just wanted to post an update on the battery life I am getting with the beta settings. I managed to get almost 5hrs of screen on time with the Turtle settings beating my previous longest screen on time from the images in the first post. I managed to do this with even more demanding tasks. In the first post the battery times are with mainly web browsing this time I was mainly watching Netflix and YouTube for about 3hrs worth of my screen on time. My brightness was also 10% higher than the first time. I also did a standby test and managed to only drain 3% overnight and it said I would get 139 hrs of standby time which I think is insanely good.
Battery life test
I just ran the Geekbench 3 battery test and managed to get 5 hrs 45 min and a score of 3456 on the beta settings. I managed to beat the G4 battery time by 50min and this was with 30% brightness and Bluetooth, WiFi, and Cell on no airplane mode. I also managed to beat the G3 and almost got the same battery time as the OnePlus One.
*Comparisons where made from the battery times here:https://browser.primatelabs.com/battery-benchmarks
Shorty88jr said:
I just ran the Geekbench 3 battery test and managed to get 5 hrs 45 min and a score of 3456 on the beta settings. I managed to beat the G4 battery time by 50min and this was with 30% brightness and Bluetooth, WiFi, and Cell on no airplane mode. I also managed to beat the G3 and almost got the same battery time as the OnePlus One.
*Comparisons where made from the battery times here:https://browser.primatelabs.com/battery-benchmarks
Click to expand...
Click to collapse
Hi, dude. I'm very interested in tweaking my G4 to get better battery life as at the moment I need to charge it twice a day. I just have a noob question, could you please tell me how you disabled touchboost using Kernel Adiutor?
IvanN8458 said:
Hi, dude. I'm very interested in tweaking my G4 to get better battery life as at the moment I need to charge it twice a day. I just have a noob question, could you please tell me how you disabled touchboost using Kernel Adiutor?
Click to expand...
Click to collapse
Go to the CPU section then scroll all the way down till you get to a section that says CPU Boost. Set the Interval to 0 Sync Threshold disabled and Input Interval to 0. The input boost frequency will never disable for me but with the above settings it shouldn't matter because it will never run anyway.
Shorty88jr said:
Go to the CPU section then scroll all the way down till you get to a section that says CPU Boost. Set the Interval to 0 Sync Threshold disabled and Input Interval to 0. The input boost frequency will never disable for me but with the above settings it shouldn't matter because it will never run anyway.
Click to expand...
Click to collapse
Ok. I really thank you. Just entered the values, I will give it a try and report back on how it goes. Those numbers you got look really good.
IvanN8458 said:
Ok. I really thank you. Just entered the values, I will give it a try and report back on how it goes. Those numbers you got look really good.
Click to expand...
Click to collapse
I would try the GhostPepper settings first. The beta settings seem to give me better battery but they are still a work in progress and not as smooth as the other settings but you can use them if you want any feedback on those settings would be appreciated. I was also surprised how much those settings did for my battery life.
I decided to do a benchmark on how much of a difference there was between stock and the custom settings and to show I wasn't making stuff up by saying that I used these settings and magically got almost double battery life With the stock settings I got just a hair over 3hrs vs almost 6hrs on the tweaked CPU settings. You can see the results from stock in the IMG. The results for the tweaked settings are near the bottom of the first page.
IvanN8458 said:
Ok. I really thank you. Just entered the values, I will give it a try and report back on how it goes. Those numbers you got look really good.
Click to expand...
Click to collapse
How is your battery life after trying the settings out for a few days?
hey man i just tried yours and let we see the performance in next day. anyway the tweak that youve done is only on the CPU? no GPU or whatsoever? what if i implemented from others, let say other G4 users that tweak the GPU and i combined with your CPU tweak. any problem?
Hey man, how could I get the tweak for this setting? Thank you
I didn't think you could tweak the kernel without an unlocked bootloader for the Verizon G4 (vs98613b)?
elrosid said:
hey man i just tried yours and let we see the performance in next day. anyway the tweak that youve done is only on the CPU? no GPU or whatsoever? what if i implemented from others, let say other G4 users that tweak the GPU and i combined with your CPU tweak. any problem?
Click to expand...
Click to collapse
Yes just CPU and yes you can use GPU tweaked combined with the CPU tweaks just be aware it may affect stability.
glees.shin said:
Hey man, how could I get the tweak for this setting? Thank you
Click to expand...
Click to collapse
You need to be rooted then use the app kernel adiutor and change the values in the app.