Hi guys.
I have been playing for a long time with CPU ( in the kernel ) of my phone.
Finally, I got some tweaks which worked perfect for my phone (SM-G530FZ) to increase performance. Please test if its improving performance for you.
It can give you smoother gameplay etc.
*If you dont want these values in your phone after setting and if you want to reset them, just reboot.
This mod along with the given below link gave the results which is given in the screenshot. Thanks to @adblocker for this tweaks in the Link.
[OPTIONAL] Link :- https://forum.xda-developers.com/grand-prime/general/lollipop-build-prop-tweaks-t3188026
After mixing the mods in this page and the mods in the given above link. This is the result.
->Services in use (Free ram)
MORE FREE !!!
{
"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"
}
->Cached services (Free ram)
MORE FREE !!!
* INSTALLATION :-
1. Backup your Build.prop located in /system/ (here)
2. Open Build.prop located in above path
3. Leave one empty line.
4. Now copy the code from the [OPTIONAL] link above.
5. Paste in Build.prop and leave two lines.
6. Save it.
8. Reboot.
9. Copy the code in this page given below.
10. Paste in any Terminal Emulator and press enter.
11. Thats it, DONT REBOOT (If you reboot, the code which you pasted in terminal emulator will be reset to default by android).
Code:
su
echo interactive >> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo "10,158,676,794,811,1500" >> /sys/module/lowmemorykiller/parameters/adj
echo "64" >> /sys/module/lowmemorykiller/parameters/cost
echo 0 >> /sys/module/lowmemorykiller/parameters/debug_level
echo "2740,5300,22320,35120,47920,60720" >> /sys/module/lowmemorykiller/parameters/minfree
echo interactive >> /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 76 >> /sys/devices/system/cpu/cpufreq/interactive/go_hispeed_load
echo 2000000 >> /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
echo 40000 >> /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo 20000 >> /sys/devices/system/cpu/cpufreq/interactive/timer_rate
Please inform me if it improves performance.
Also tell me your device model. (So I can know for which it works best)
Enjoy !!!
its like overclocking? if yes then I wont do it lol
Owen007 said:
its like overclocking? if yes then I wont do it lol
Click to expand...
Click to collapse
Yes. But if you want your default to be back again just restart your device. You can check if the values are different from mine after restarting with this code.
cat /sys/module/lowmemorykiller/parameters/adj
Click to expand...
Click to collapse
if the values shown are different from this. -> 10,158,676,794,811,1500
Means that after restarting you default values have been restored.
Thanks alot man its good idea
I will try it later
abooooood said:
Thanks alot man its good idea
I will try it later
Click to expand...
Click to collapse
Anyway, thanks to u too
Related
I've finally managed to compile smartass v2 governor (source code) and get it to work on X10 mini.
Few members insisted if I could give it a try and I accepted the challenge
It is ment for X10 mini stock kernel 2.6.29 preempt mod_unload ARMv6.
{
"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"
}
You can configure various parameters:
Code:
-sh-3.2# pwd
/sys/devices/system/cpu/cpu0/cpufreq/smartassV2
-sh-3.2# ls
debug_mask
up_rate_us
down_rate_us
sleep_ideal_freq
sleep_wakeup_freq
awake_ideal_freq
sample_rate_jiffies
ramp_up_step
ramp_down_step
max_cpu_load
min_cpu_load
Installation guide:
Download the archive and copy the cpufreq_smartass2.ko onto the root of your /sdcard/. Then, type in the following commands:
Code:
mount -oremount,rw /dev/block/mtdblock0 /system
cd /system/lib/modules
cp /sdcard/cpufreq_smartass2.ko .
insmod cpufreq_smartass2.ko
Then you can switch to the smartassV2 governor using SetCPU.
Configuration:
SetCPU does not support configuring it - so you will have to manage from command line. Have a look at this thread to understand how to configure - it is for the old smartass module for X10 - but the configuration is done the same way.
Each parameter (and its meaning) is defined in the source code found above.
Download:
Use it at your own risk!
cpufreq_smartass2_x10mini.zip
Enjoy!
I just installed the module, but now I want to manage it to load at startup. Which is the correct sentence?
echo "smartass" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor [OR]
echo "smartassV2" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
The last one - with smartassV2.
viulian said:
The last one - with smartassV2.
Click to expand...
Click to collapse
how about detial?
i want it at startup, too
Got Mini Pro. Flashed Xperian Blaze, but it's 11W40, so only stock kernel is in play. But when trying to insmod this governor device freezes and reboots.
Is there any other thing I'm missing? Or maybe other way to get additional governors for stock kernel?
This is the first time I try V8 Supercharger. I ran the script busybox_v1.19.4_wraithdu--boot_reinstaller_script_v3--installs_every_boot as root in Script Manager and then I rebooted the phone. After that I ran V8_SuperCharger_Alpha_Milestone_Special.sh as root, selected option 6. Balanced 3 Settings {6,8,26,28,30,32 mb} , then option 19 to exit and then i rebooted the phone. After the boot I went into Script Manager, ran the V8 Supercharger script as Root again, and the result is not the one I wanted. The script confirms Launcher is hard to kill but the minfrees values are the current rom's default {6 8 16 36 40 40 mb} and not the wanted {6,8,26,28,30,32 mb}. The settings just don't stick. I've tried to Unsupercharge and reboot the phone then run the script again but I get the same results. I am using Elelinux-7.2-Hero-v3.7. What can I do to make them stick? Am I doing something wrong?
{
"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"
}
Well, before supercharger it, you have to take a look into /etc/init.d to see what scripts elelinux included in his rom (a2sd, cache2cache, mountext - do not touch these) and if you find some scripts like these: loopy_smoothness_tweak, speedy_modified, clean_ram, 99supercharger, edt_tweaks or anything that hasn't to do with a2sd, cache, mountext, you should delete those, reboot your phone and then try to super charge it. I suggest install busybox installer and choose to install a busybox v 1.8.1 because if you have higher, the script will probably create problems.
Cheers!
1ceb0x said:
Well, before supercharger it, you have to take a look into /etc/init.d to see what scripts elelinux included in his rom (a2sd, cache2cache, mountext - do not touch these) and if you find some scripts like these: loopy_smoothness_tweak, speedy_modified, clean_ram, 99supercharger, edt_tweaks or anything that hasn't to do with a2sd, cache, mountext, you should delete those, reboot your phone and then try to super charge it. I suggest install busybox installer and choose to install a busybox v 1.8.1 because if you have higher, the script will probably create problems.
Cheers!
Click to expand...
Click to collapse
From /etc/init.d/ I removed the script for busybox reinstaller 1.19.4 (forgot the name) and the 99supercharger. I've installed busybox 1.18.1, reboot and tried to unsupercharge, reboot, supercharge again with Balance 3, reboot, but the memfreeze values are not changing. The only ones remaining in /etc/init.d/ are 00banner , 01sysctl, 03firstboot , 04modules , 05mountsd , 06mountdl , 10apps2sd , 12compcache , 20userinit . Which are safe to delete?
Edit: I've sent you a PM
Edit2: I installed busybox 1.18.1 again and after that the script worked as it should and the memfreeze values sticked . I think busybox 1.18.1 didn't work the first time.
Thank you !
Leave it as it is because those are script that makes some things in the rom to work. I see you have included 99supercharger script in the zip, you made the zip after you supercharged it again? if so, the script is applying correctly and the values are these:
echo 0,2,4,7,14,15 > /sys/module/lowmemorykiller/parameters/adj;
echo 1536,2048,6656,7168,7680,8192 >
if you want I can provide you a script to push it in /etc/init.d to change those values but you have to unsupercharge first (and not use it anymore)...
View attachment 06ramconfig.rar
you can push it with a file manager and reboot the phone. push it without archive ofc.
oh well... glad it solved out for ya
CM11 Bootanimation for MDPI and HDPI devices
Decided to make an optimized and a resized one for our devices
{
"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"
}
*Warning
I'm not responsible for devices that undergo bootloops or any errors, it's your choice to make these changes.
*Requirements
-Unlocked bootloader
-Rooted device
*Instructions
Via Root Explorer:
-Place the file in your sd card.
-Rename it as "bootanimation" (Without quotes)
-Copy or move it to root/data/local
-Set permission as r-w-r-r
-Reboot
Via ADB:
-Enable USB debugging in your device.
-You should have SDK installed. Go to platform-tools.
-In notepad++ type
Code:
echo off
pause
files\adb root
files\adb remount
files\adb push files\bootanimation.zip /data/local
files\adb shell chmod 755 /data/local/
files\adb reboot
pause
echo on
-Name it and save it as .bat (Type ".bat" after the name of your file without spaces) save it to platform-tools.
-Place the "bootanimation_HDPI.zip" or "bootanimation_MDPI.zip" to platform-tools.
-Connect your device to your Machine.
-Open the file you created and CMD will appear, press enter, wait for it.
-Your device will reboot, done
*Downloads
bootanimation_HDPI.zip
bootanimation_MDPI.zip
*Credits
CyanogenMod
Downloading for Xperia S!
yeah
support on
xperia e?
benpsam said:
xperia e?
Click to expand...
Click to collapse
If it has HDPI screen size, try it
I need s5 boot animation
Cool. :good:
this is awesome, thanks @JovieBrett! Any chance you could create this in 1080x1920?
The_Benwa said:
this is awesome, thanks @JovieBrett! Any chance you could create this in 1080x1920?
Click to expand...
Click to collapse
I no longer have this original file of it, sorry!
Abdulwahid34 said:
I need s5 boot animation
Click to expand...
Click to collapse
try this link:
http://forum.xda-developers.com/showthread.php?t=2711213
This guide can also be used on any rom running 4.2.2+.
Requirements
→Rooted device
→Xposed framework
→A Brain?
This method may not work on stock because stock roms doesn't supports but still you can try it.
There are two different methods of doing this.
METHOD 1:-
JUST download multi-user app from xposed repository and reboot. You will get a option of User under apps.
{
"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"
}
Now just tap on it and add or manage users.
METHOD 2:-
In a terminal window or ADB, you’ll need to obtain SuperUser/root access. This is generally done by typing in su. After obtaining SuperUser access, type in:
pm get-max-users
Click to expand...
Click to collapse
This should return the numeric result of “1,” which is the maximum number that the current OS is set up accept. If it returns an error, then your ROM is most likely unable to handle multiple users.
Next, you’ll need to change that number to something higher. In the following, I chose to set it to eight users because I felt like it.
Now type in:
setprop fw.max_users 8
pm create-user usernameyouwanthere
Click to expand...
Click to collapse
You may notice the shell reboot, and if you’re on a ROM build that supports multiple users properly, you’ll either get a login request, or a users section will appear under device in system settings. Depending on your ROM, you might even see an option in the developer’s menu to enable user selection in the power menu.
Keep in mind that this may not work completely or be supported by your ROM, but in some instances it’s quite useful. The worst that should happen is that you have to restore a nandroid, or that the max_users changes back to single-user after a reboot.
★How to make it stick
Inspired by a comment from konnor below, this is how I got the multiple user mode to stick:
Code:
adb shell (if you’re not already, you can use terminal emulator if you want)
su
mount -o rw,remount /system
echo fw.max_users=4 >> build.prop
exit
exit
adb reboot (or reboot the device however you want)
From now on out the max_users will always be there when you boot.
After a reboot, swiping down and pressing my face brings me to the lock screen where all users are displayed. Your results may vary so make sure to have a nandroid backup.
Not my work just posting it in XDA.
PRESS THANKS IF I HELPED YOU
REGARDS
banerjeeayan1996
DragonOS Tool ProjectVERY LITE AND EASY TO USE
{
"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"
}
Error recompile window
Error not found file
FEATURES=================
>> Easy to use, great for those who want to venture into this area or for more convenience
v1.0:
>> Automatic processes
>> Self-signed apks, you are free to edit the manifest
>> Autofill in general with the original add-ons of the apk or jar (once compiled it is ready for use)
>> Import in real time of the framework with which you want to work
>> Decompilation/Compilation of the dex using the reliable backsmali (to always ensure the correct compilation in versions such as Oreo/Pie)
v1.5
>> Added language selector (English/Spanish)
>> 3 selectable options to treat apks
(Normal Decompile, Decompile only of dex, Explore the contents of the apk with classy)
>> Semi-encoding for individual xml (more is useful to see and examine them but not to use them)
v2.0
>> Themes Support (Tool customization) (10 themes)
>> Logger v1.0 (logs reco/decompile)
>> Visual corrections and improvement in the structuring
>> Added error warning window in case of failures during recompilation
v3.0
>> Design improvements
>> Added two more options for the apks
(Direct extraction of Source Code in Gradle Source project format / Exploration and manual extraction of it)
>> Added warning window if no file is found
>> Updated backsmali/smali
>> Multiple text color mod Added
>> Greater stability
>> Last but not least, very LITE
INSTRUCTIONS================
*If you want to use a specific framework-res for the compilation, just place it in the folder "framework"
(or if it's the first time you compile something)
I think this one, but as I mention it, it is necessary to have Java
>>>It is more advisable to run it in administrator mode<<<
1. Put the apk/jar/dex or xml (it will only be semi translated, will appear as SemiDecoded-xml-OnlyForView)
2. Open the Decompile and wait for decompiling...
3. In case it is an apk select the option you prefer
4. Make the changes you want
5. Open the Recompile and wait for recompiling...
(can check the logs in case of error)
6. Modified apk or jar will be inside the "FINISH_WORK" folder with the "base" name
(if it's an apk, it's self-signed, you are free to edit the manifest )
(If it is a jar it will also be ready for use, there is no need to put anything else )
7. In case it is a dex it will be inside the "COMPILED" folder
8. After using it, it is recommended to clean the work area, for that only open Clean
DOWNLOADS================
DragonOS Tool v3.0 Stable
CREDITS================
@Misma13(for development tool )
@iBotPeaches(for apktool)
@JesusFreke(for backsmali/smali)
@ apio (for sign)
@ borisf (for classyShark)
@ google (for axml)
@ skylot (for jadx)
@ Igor Pavlov (for 7zip)
If I forget someone please report
Now stable