hunds 3.4 ET kernel hotplug config questions - Asus Transformer TF700

I was able to install the new kernel to cromi-x 5.04 but I want to tune the hotplugging configuration for better battery life.
0 0 0 is the benchmarking performance mode right? Is 8 12 16 a normal setting good for battery life? Also these settings are in both 50cleantweeks and 99hundsapp init files. Hunds app only updates his script. Should I manually change 50cleantweaks to show the same values or are they over written by the 99hundsapp when its loaded during boot?

troyboy162 said:
I was able to install the new kernel to cromi-x 5.04 but I want to tune the hotplugging configuration for better battery life.
0 0 0 is the benchmarking performance mode right? Is 8 12 16 a normal setting good for battery life? Also these settings are in both 50cleantweeks and 99hundsapp init files. Hunds app only updates his script. Should I manually change 50cleantweaks to show the same values or are they over written by the 99hundsapp when its loaded during boot?
Click to expand...
Click to collapse
The init.d script will executethe 50 before the 99. So the 99hundsapp will be your setting.. You can remove the one in the 50cleanTWEAKS or put a number sign in front of it to comment it out. 0 0 0 is used when you want to disable the hotplug... The default for hund v3.4 is 7 10 12. The first number is the numbers of active threads before the second core is running and so on.. I could be wrong, haha. You can find more information on hund post..

Related

[09/01/09] Android - Polaris Userspace and Testing thread

*** PLEASE READ CAREFULLY BEFORE INSTALLING OR FLASHING ANY SOFTWARE POSTED IN THIS THREAD ***
The software posted here is for TESTING purposes only, The Polaris Android Linux development team or any of the posters of software or links to software on this thread, take absolutely no responsibility or liability for damage caused by the result of installing or flashing software or links to software found on this thread - correctly or otherwise, you do so on the sole understanding that you do so at your own risk.
Previous thread was closed because too big you can find lot of information into it with the search button : http://forum.xda-developers.com/showthread.php?t=555000
Hello to all of you, Android user.
This thread is the right place to talk about non-kernel related discussions, questions and requests.
Please, remember that the thread is public, so don't use bad word
So...have fun
-------------------------------------------------------------------------------------------------------------------------------
01-09-09 - new link to files for working wifi
http://www.4shared.com/dir/19593527/...a/sharing.html
From Google Code Vogue-Android:
01-09-09 - Initrd - works with unpartitioned cards, otherwise no changes.
01-09-09 - Rootfs - works with unpartitioned cards, otherwise no changes.
Reserved for future use
Reserved for future use.
Reserved for future use,
Reserved for future use-
what packages do i have to dload? everything?
nicandris said:
what packages do i have to dload? everything?
Click to expand...
Click to collapse
From the first link (4share), you took all but rootfs and initrd, these one you could download it from the other links
You should put name Android in the title to know about what is this thread
whitealien said:
You should put name Android in the title to know about what is this thread
Click to expand...
Click to collapse
Thanks for the suggestion
@Mormy
Could you give us your startup/default haret script? With script whitch you uploaded to 4shared, graphics don't work properly.
Good thing to open a clean thread to speak about testing
I'm currently testing the SquashFs version, latest on http://code.google.com/p/vogue-android/downloads/list
With this system.sqsh : http://vogue-android.googlecode.com/files/hero.zip
And this base files : http://vogue-android.googlecode.com/files/squashfsbasefiles.zip
It's very stable. With this build I haven't got anymore the 'reload UI' problem when I go back to home screen.
But it's very slow. It takes more time to launch application, wake up the phone, open settings... But the scrolling is normally fast.
Wifi doesn't work for me with it.
Maybe I'll try this one tonight : system-090109r1.img on http://code.google.com/p/vogue-hero/downloads/list
I didn't understood how works the last one with 'userinit.sh' system, so I think I will not try it
Averne said:
@Mormy
Could you give us your startup/default haret script? With script which you uploaded to 4shared, graphics don't work properly.
Click to expand...
Click to collapse
I've tried Neocore and won't start either with the 4share startup and with mine.
By the way, this the one I usually have:
Code:
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing
# ppp.password - The password used to connect to the network when dialing
# ppp.apn - Set apn of your provider
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htcpolaris.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "board-htcpolaris.panel_type=3 ppp.apn=tre.it ppp.username=none ppp.password=none pm.sleep_mode=1 mddi.width=324 mddi.height=432 no_console_suspend board-htcpolaris-battery.battery_capacity=1350 clock-7x00.mddi=0xa51 mddi_client_vogue.vsync=0"
boot
Averne said:
@Mormy
Could you give us your startup/default haret script? With script whitch you uploaded to 4shared, graphics don't work properly.
Click to expand...
Click to collapse
Try with '1' instead of '3' for "board-htcpolaris.panel_type" property.
Averne said:
@Mormy
Could you give us your startup/default haret script? With script whitch you uploaded to 4shared, graphics don't work properly.
Click to expand...
Click to collapse
if you mean neocore then yes that is broken in this kernel.
if you are having display issues, then try changing the panel type or try to be more specific on what you mean by "graphics dont work properly".
Ok, this is my default.txt file:
Code:
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htcpolaris.panel_type=0 ppp.apn=orange ppp.username=orange ppp.password=orange pm.sleep_mode=1 mddi.width=336 mddi.height=448 lcd.density=160 no_console_suspend board-htcpolaris-battery.battery_capacity=1350 mddi_client_vogue.vsync=0"
boot
With this settings display works fine, but you must disconnect usb cable before press [Run] button in haret.
Hi ,
with the last files taken from bally site I have wifi working but data connection li ke previous release taken from vogue-android sometime starts sometimes no.
And with this files I can't start calling it creashes.
No Gps..
Why start up logo is changed? and button mapping?
Averne said:
Ok, this is my default.txt file:
Code:
set RAMSIZE 0x08000000
set MTYPE 1723
set KERNEL zImage
set initrd initrd.gz
set cmdline "board-htcpolaris.panel_type=0 ppp.apn=orange ppp.username=orange ppp.password=orange pm.sleep_mode=1 mddi.width=336 mddi.height=448 lcd.density=160 no_console_suspend board-htcpolaris-battery.battery_capacity=1350 mddi_client_vogue.vsync=0"
boot
With this settings display works fine, but you must disconnect usb cable before press [Run] button in haret.
Click to expand...
Click to collapse
why have you got lcd density set at 160 and width and height at 336x448?
this is not my startup file. you should try that first.
Does somebody know what are the benefits of using 'squash FS' system instead of old standard system.img?
Kiiv said:
Does somebody know what are the benefits of using 'squash FS' system instead of old standard system.img?
Click to expand...
Click to collapse
if you are really interested: (from http://groups.google.com/group/andr...ad/e4ce4f06f982d51b/30fa2b5deb6533b2?lnk=raot)
I think it would be a good idea to compress /system/bin and /system/
lib at least with squashfs, I have done this on a couple ubuntu and
gentoo systems and it actually increased performance and space
significantly!
Reasons (short version): decompressing data is faster than reading it
from the hard drive, in most current computers, especially when you
have multiple programs reading from the disk, causing thrashing, and/
or when the data on the disk is fragmented. You can read more details
about what was done and the results on http://forums.gentoo.org/viewtopic-p-4732709.html#4732709
Squashfs is intended for general read-only file system use and in
constrained block device/memory system, it can also be combined with a
union mount system like unionfs and aufs for read/write access.
We will be able to improve android boot time, app launch time, and
increase space, what more could we ask for? Maybe a little bit more
ram? Whats up with compcache too?
So now we just need to compile squashfs-tools for android and
experiment, im pretty damn excited to try this!
Also ubifs has lzo compression, not sure how that would work either,
it seems ubifs is favored over jffs2 and yaffs2
Well right now it looks squashfs+lzma wont be in the kernel until
2.6.30 found this via:
http://www.squashfs-lzma.org/
So I think we are left with UbiFS with lza compression but I have no
idea on how to add it to the kernel, and test this out, im really
interested in seeing some results and doing some benchmarks, if
someone more knowledgeable than me can help out that would be awesome
defcon
found a nice pdf comparing the filesystems:
http://free-electrons.com/doc/flash-filesystems.pdf
Benchmarks Of Yaffs2, JFFS2, SquashFS, & UBIFS:
http://free-electrons.com/pub/conferences/2008/elce/flash-filesystems...
Seems like people are already using ubifs on android:
http://groups.google.com/group/android-porting/browse_thread/thread/a...
Reference:
http://forums.gentoo.org/viewtopic-p-4732709.html#4732709
http://jt0.org/news/squashing_usr_and_the_2629_kernel
Hum, thank you for the link
So I don't understand why it's slower with squash FS on my phone... I will try to find other discussions on the subject.

BaCeM-TWEAK, Kernel Module for enable UV and Governor

sgy kernel have some issue related with cpu frequency.
first, cpu latency is not set correctly. the effect, non build-in freq governor can not working at all.
second, missing frequency table so cpu freq stat is not working. that bug make cpu spy (and other similar app) not working.
so, i write small loadable kernel module to solve that issue. i make my tweks as module so it can works with stock kernel. and for addition, i add under-voltage capability.
download and flash zip file in recovery mode. you can edit init.d script (00bacem-tweak) to change under-voltage.
if your device become unstable make both voltage higher, but keep it under stock kernel default value. i am not responsible to anything happen on your phone so be careful when tweak that value.
before install latest version (0.2), if you already install old version, flash bacem-remove-0.2.zip from recovery mode. and then flash bacem-tweak-0.2.zip
warning : it's not for noob (in real life)
to change uv manually run from terminal
Code:
echo -20mV > /proc/sys/bacem/volt/cpu
and to check if your under-voltage success
Code:
cat /proc/sys/bacem/volt/cpu
Source code
https://github.com/irfanbagus/BCM-tweak
BaCeM-tweak under bacem branch.
Build :
BCM-tweak 0.1
- Initial release
BCM-tweak 0.1.1
- Fix init.d script
- Add interactive governor
BaCeM-tweak 0.2
- Change name to BaCeM-tweak
- Support more than 2 freq
- Auto detect (and auto fix) missing cpufreq table
- Using sysctl to control under-voltage
- Real-time under-voltage. no need to unload module to change uv, and no need change frequency to apply under-voltage
BaCeM-tweak 0.2.1
- Apply workaround for instability on stock rom using init.d script. Not beautiful solution but at least it's work.
- Fix bug in memory allocation
- Fix for potential incompatibility with merruk kernel
Can use cygwin? If can maybe i will try.
Thanks for another work again and must follow.
I'd like to help but I'm completely newb in android and linux stuffs.
no need installed linux. using adb shell or ssh is enough. the reason i am not release yet because uv. without proper knowledge you could make your sgy over voltage easily.
i put source code in gitub
https://github.com/irfanbagus/BCM-tweak
and since nobody pm me, then i will test by myself. maybe need 1-2 days until i release binary build.
okay.. i think the CPU frequency table isn't going to be an easy job.
BCM21553 only allows x13 cpuspeed multipler on your thread about setcpu fix.. maybe..
ARVolutionz said:
okay.. i think the CPU frequency table isn't going to be an easy job.
BCM21553 only allows x13 cpuspeed multipler on your thread about setcpu fix.. maybe..
Click to expand...
Click to collapse
that the easiest part. ok, not real table but enough to make governor working. and because it's still using stock kernel, only 312mhz and 832mhz available. i am working on recovery zip file right know. i will upload in few next hour.
i already upload kernel module binary and init.d script. check first post. as soon as you find problem, disable init.d script and please report. i am not include custom governor yet. i already build ondemand, but it's make ui become lag so i am not include in zip file. tomorrow i will try to build interactive governor.
[edit]
just in case your phone failed to boot, use file in attachment to remove bcm-tweak. use from recovery mode.
I've changed the voltage value but both nofrills and antutu said that the frequencies are not changed. still showing 832 and 312mhz. the performance score indeed increased but how could we know that the module is really working or not?
kurotsugi said:
I've changed the voltage value but both nofrills and antutu said that the frequencies are not changed. still showing 832 and 312mhz. the performance score indeed increased but how could we know that the module is really working or not?
Click to expand...
Click to collapse
i think because still use stock kernel with same freq and from 1st post its only change voltage. maybe can see the different with app that can show our voltage before and after use bcm-tweak.
In init.d/00bcm-tweak what efect if you change echo 312000 to echo 600000 or else number?
kurotsugi said:
I've changed the voltage value but both nofrills and antutu said that the frequencies are not changed. still showing 832 and 312mhz. the performance score indeed increased but how could we know that the module is really working or not?
Click to expand...
Click to collapse
savie said:
i think because still use stock kernel with same freq and from 1st post its only change voltage. maybe can see the different with app that can show our voltage before and after use bcm-tweak.
In init.d/00bcm-tweak what efect if you change echo 312000 to echo 600000 or else number?
Click to expand...
Click to collapse
it does not change frequency and it should not give improvement to performance. its only effect 3 things : cpu voltage, cpu freq statistic, and cpufreq latency (only the number, not actual latency). to check if module loaded, make sure folder "/sys/module/bcm_tweak" exist.
be careful when change voltage, don't set too low. to see if voltage control is working, i try to change voltage 1V and it's successfully to ... death no error, no restart only stop working and i have to pull out battery to restart my phone.
irfanbagus said:
it does not change frequency and it should not give improvement to performance. its only effect 3 things : cpu voltage, cpu freq statistic, and cpufreq latency (only the number, not actual latency). to check if module loaded, make sure folder "/sys/module/bcm_tweak" exist.
be careful when change voltage, don't set too low. to see if voltage control is working, i try to change voltage 1V and it's successfully to ... death no error, no restart only stop working and i have to pull out battery to restart my phone.
Click to expand...
Click to collapse
Well that speaks that this is absolutely working, right?
Still observing it
Sent from my GT-S5360 using xda premium
I'm afraid the init.d script didn't work. I can't find bcm_tweak in /sys/module/. this is what I do to make it work. I edited '#!/system/xbin/busybox sh' to '#!/system/bin/sh' and 'bcm-tweak.ko' to 'bcm_tweak.ko', rename the ko file as in init.d script, reboot.
@ irfanbagus;
Can you share your custom kernel
kurotsugi said:
I'm afraid the init.d script didn't work. I can't find bcm_tweak in /sys/module/. this is what I do to make it work. I edited '#!/system/xbin/busybox sh' to '#!/system/bin/sh' and 'bcm-tweak.ko' to 'bcm_tweak.ko', rename the ko file as in init.d script, reboot.
Click to expand...
Click to collapse
sound like busybox applet problem. can you do this for me ? run in terminal
Code:
/system/xbin/busybox
and see if your busybox has build-in command "sh" and "insmod". i'll try to fix it tonight
premolikeshtc said:
@ irfanbagus;
Can you share your custom kernel
Click to expand...
Click to collapse
this is my 'custom kernel'
I want the boot.img,,
my busybox version doesn't have sh but it does have insmod. I forgot the version its 1.17 or something. I'm not sure if the newer one have sh. and btw, we already have insmod in /system/bin.
Work great.
Result with antutu after restart use bcm21553
1.non bcm-tweak 1375
2.bcm-tweak 1560
Result with antutu after restart use performance
1.non bcm-tweak 1572
2.bcm-tweak 1573
Still on original number not change anything in 00bcm-tweak file
@prem:
http://forum.xda-developers.com/showthread.php?t=1620243 --> kernel bootscript
http://forum.xda-developers.com/showthread.php?t=1598803 --> kernel dualboot
http://forum.xda-developers.com/showthread.php?t=1545930 --> ext4 modules for kernel
Thanks a lot
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
Which governor is working actually ?

install TF700 KitKat 4.4.4][CROMBi-kk][Sep 6]

hi
I already install this rom. and then install asus apps. but now when I push settings on tablet nothing happened.
I want to flash it again and to clean the tablet first.
what are the steps?
1to go to advanced wipe settings and wipe:
dalvik cache
system
cache
data
internal storage?
or just factory reset?
than install?
thanks!!
OK Iinstalled everything again and i see asus keybord and story,but where are the witdgest that where with balance mode super ips pannel??very dissapointed
bennnnnn said:
hi
I already install this rom. and then install asus apps. but now when I push settings on tablet nothing happened.
I want to flash it again and to clean the tablet first.
what are the steps?
1to go to advanced wipe settings and wipe:
dalvik cache
system
cache
data
internal storage?
or just factory reset?
than install?
thanks!!
OK Iinstalled everything again and i see asus keybord and story,but where are the witdgest that where with balance mode super ips pannel??very dissapointed
Click to expand...
Click to collapse
Very disappointed? Hmmm not the best way to encourage the devs to support you. You need to do some reading before flashing roms I guess.
First not all Asus Apps are supported. Kansasboy is doing his best to port them - it's a lot of work in some cases so you should be thankful he tried.
Second balance mode is there you just haven't found it. Enable developer settings but clicking the build number in about rom 7 times and a performance tab will appear - you can take it from there
Third - super IPS is now rolled into the one brightness bar. Max brightness = super ips max. Min brightness = non super ips min brightness.
This is a CM11 based ROM not an ASUS Stock based ROM. If you want the enhanced Asus experience please flash CROMi-X 5.4
BTW this rom has taken the best part of 6 months for me and lj50036 to build (as well as others like _that and hardslog who help support). We work on it every single day - literally.
re
sbdags said:
Very disappointed? Hmmm not the best way to encourage the devs to support you. You need to do some reading before flashing roms I guess.
First not all Asus Apps are supported. Kansasboy is doing his best to port them - it's a lot of work in some cases so you should be thankful he tried.
Second balance mode is there you just haven't found it. Enable developer settings but clicking the build number in about rom 7 times and a performance tab will appear - you can take it from there
Third - super IPS is now rolled into the one brightness bar. Max brightness = super ips max. Min brightness = non super ips min brightness.
This is a CM11 based ROM not an ASUS Stock based ROM. If you want the enhanced Asus experience please flash CROMi-X 5.4
BTW this rom has taken the best part of 6 months for me and lj50036 to build (as well as others like _that and hardslog who help support). We work on it every single day - literally.
Click to expand...
Click to collapse
first - I am really appreciate the develppers and this rom!! and many many thanks!!!
iam tring to say that iam disappointing from the tablet itself - because asphalt 8 runs too slow!! even in medium - un playable - and I overclock the processor to 1.8 ghz per core I tought it would change after I install custom rom or I have aproblem with my tf700.
is there any benchmark software to check it?
bennnnnn said:
asphalt 8 runs too slow!! even in medium - un playable - and I overclock the processor to 1.8 ghz per core
Click to expand...
Click to collapse
Asphalt 8 is GPU limited. It runs acceptable on medium details even in balanced mode after running this script:
Code:
#!/system/bin/sh
echo 0 > /sys/kernel/tegra_cap/core_cap_state
echo 0 > /sys/devices/gr3d/enable_3d_scaling
am display-density 160
am display-size 1280x800
To switch back to native resolution:
Code:
#!/system/bin/sh
am display-size reset
am display-density reset
re
_that said:
Asphalt 8 is GPU limited. It runs acceptable on medium details even in balanced mode after running this script:
Code:
#!/system/bin/sh
echo 0 > /sys/kernel/tegra_cap/core_cap_state
echo 0 > /sys/devices/gr3d/enable_3d_scaling
am display-density 160
am display-size 1280x800
To switch back to native resolution:
Code:
#!/system/bin/sh
am display-size reset
am display-density reset
Click to expand...
Click to collapse
thank u so much!!
where do I write this please?

[APP][5.0+] Spectrum - A kernel manager for users [ROOT]

{
"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"
}
Spectrum​
Index:
This post: Overview, features, screenshots, and development.
2nd post: How to add Spectrum support to your kernel
3rd post: Spectrum Injector
What:
Spectrum is a simple, profile oriented kernel manager that allows developers to create profiles to serve to their users. This is useful for users who are inexperienced with kernel tweaking or users who want something that's a single click away.
How:
Choose from Balance, Performance, Battery, or Gaming profiles to quickly and easily change kernel settings to your preference, now even easier with the included QuickTiles.
Features:
Dark Material Design theme
4 Profiles to choose from: Balance, Performance, Battery, and Gaming
Nougat Quicktile support
Launch QuickTile
Profile selector QuickTile
Customizable kernel name string
Easy to add, yet versatile kernel support
some eastereggs but shhh
History:
I initially intended Spectrum to be a companion app/updater for my kernel, Electron. However, I decided to make the app open and available for any developer to integrate into their kernel so that more users can have a simple kernel experience.
Download:
Spectrum on Google Play
Spectrum is also open source, you can find it on GitHub.
Thanks:
I'd like to give a special thanks to @The Flash for being an early adopter of Spectrum with Flash Kernel, and the tons of support and testing he gave while Spectrum was in development. I'd also like to thank @xanaxdroid for all the testing, critiquing, and support throughout development. Also, a huge thanks to @franciscofranco for the inspiration and giving code improvement tips. Couldn't have done it without you guys.
XDA:DevDB Information
Spectrum Kernel Manager, App for all devices (see above for details)
Contributors
frap129
Source Code: https://github.com/frap129/spectrum
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2017-05-04
Created 2017-05-04
Last Updated 2017-07-15
How to add Spectrum support to your kernel:
Original documentation: GitHub
You'll need to add these 2 files to your devices ramdisk:
init.spectrum.rc
init.spectrum.sh
These files can be found on Github https://github.com/frap129/spectrum/tree/master/ramdisk
Now we have to include these ramdisk files. To do this, add
Code:
import /init.spectrum.rc
to the top of your devices main ramdisk file, usually called init.DEVICENAME.rc.
Next let's add your kernel name to the app. Open init.spectrum.rc and change "Electron" in
Code:
setprop persist.spectrum.kernel Electron
to your kernel's name.
Now just customize the 4 profiles in init.spectrum.rc to your liking! Profile 0 (Balanced) is the default, however, this can be changed in init.spectrum.sh. Here's my init.spectrum.rc file as an example:
Code:
# SPECTRUM KERNEL MANAGER
# Ramdisk file for profile based kernel management
# Implimentation inspired by Franco's fku profiles
# Initialization
on property:sys.boot_completed=1
# Set default profile on first boot
exec u:r:init:s0 root root -- /init.profiles.sh
exec u:r:su:s0 root root -- /init.profiles.sh
# Enable Spectrum support
setprop spectrum.support 1
# Balance (default profile)
on property:persist.spectrum.profile=0
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor relaxed
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 302400
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1708000
write /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor chill
write /sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq 633600
write /sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq 1958400
write /sys/module/cpu_boost/parameters/input_boost_enabled 1
write /sys/module/cpu_boost/parameters/input_boost_freq "0:960000 1:960000 2:960000 3:960000 4:0 5:0 6:0 7:0"
write /sys/module/cpu_boost/parameters/boost_ms 0
write /sys/module/cpu_boost/parameters/input_boost_ms 40
write /sys/module/cpu_boost/parameters/migration_load_threshold 15
write /sys/module/cpu_boost/parameters/sync_threshold 0
write /sys/module/msm_performance/parameters/touchboost 0
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/boost_count 5
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/boost_ceiling 10
write /sys/devices/system/cpu/cpu4/cpufreq/chill/boost_count 10
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/freq_step 6
write /sys/devices/system/cpu/cpu4/cpufreq/chill/freq_step 4
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/down_threshold 60
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/down_threshold_suspended 85
write /sys/devices/system/cpu/cpu4/cpufreq/chill/down_threshold 75
write /sys/devices/system/cpu/cpu4/cpufreq/chill/down_threshold_suspended 99
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/up_threshold 70
write /sys/devices/system/cpu/cpu4/cpufreq/chill/up_threshold 90
write /sys/class/leds/lcd-backlight/max_brightness 255
write /sys/class/kgsl/kgsl-3d0/devfreq/governor msm-adreno-tz
write /sys/module/adreno_idler/parameters/adreno_idler_active 1
write /dev/cpuset/foreground/cpus 0-2,4-7
write /dev/cpuset/foreground/boost/cpus 4-7
write /dev/cpuset/top-app/cpus 0-7
write /sys/module/lazyplug/parameters/nr_possible_cores 8
# Performance (based on DrunkSauce Lite)
on property:persist.spectrum.profile=1
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 302400
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load 75
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay 0
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate 40000
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq 960000
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack -1
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads 80 384000:33 460800:25 600000:50 672000:65 787200:70 864000:85 960000:90 1248000:92
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time 50000
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/boost 1
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/align_windows 0
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis 166667
write /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq 633600
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/go_hispeed_load 90
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/above_hispeed_delay 0
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_rate 20000
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/hispeed_freq 1440000
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_slack -1
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/target_loads 74 768000:73 864000:64 960000:80 1248000:61 1344000:69 1440000:64 1536000:74 1632000:69 1689600:67 1824000:72
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/min_sample_time 30000
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/boost 1
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/align_windows 0
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/use_migration_notif 1
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/use_sched_load 1
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/max_freq_hysteresis 20000
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/boostpulse_duration 80000
write /sys/module/cpu_boost/parameters/input_boost_enabled 1
write /sys/module/cpu_boost/parameters/input_boost_freq "0:1248000 1:1248000 2:1248000 3:1248000 4:0 5:0 6:0 7:0"
write /sys/module/cpu_boost/parameters/boost_ms 80
write /sys/module/cpu_boost/parameters/input_boost_ms 420
write /sys/module/msm_performance/parameters/touchboost 0
write /sys/class/leds/lcd-backlight/max_brightness 255
write /sys/class/kgsl/kgsl-3d0/devfreq/governor msm-adreno-tz
write /sys/module/adreno_idler/parameters/adreno_idler_active 1
write /dev/cpuset/foreground/cpus 0-2,4-7
write /dev/cpuset/foreground/boost/cpus 4-7
write /dev/cpuset/top-app/cpus 0-7
write /sys/module/lazyplug/parameters/nr_possible_cores 8
# Battery
on property:persist.spectrum.profile=2
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor relaxed
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 302400
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1248000
write /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor relaxed
write /sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq 633600
write /sys/devices/system/cpu/cpu4/cpufreq/scaling_max_freq 768000
write /sys/module/cpu_boost/parameters/input_boost_enabled 0
write /sys/module/cpu_boost/parameters/input_boost_freq "0:0 1:0 2:0 3:0 4:0 5:0 6:0 7:0"
write /sys/module/cpu_boost/parameters/boost_ms 0
write /sys/module/cpu_boost/parameters/input_boost_ms 40
write /sys/module/cpu_boost/parameters/migration_load_threshold 15
write /sys/module/cpu_boost/parameters/sync_threshold 0
write /sys/module/msm_performance/parameters/touchboost 0
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/boost_count 6
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/boost_ceiling 12
write /sys/devices/system/cpu/cpu4/cpufreq/chill/boost_count 12
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/freq_step 6
write /sys/devices/system/cpu/cpu4/cpufreq/chill/freq_step 4
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/down_threshold 70
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/down_threshold_suspended 85
write /sys/devices/system/cpu/cpu4/cpufreq/chill/down_threshold 75
write /sys/devices/system/cpu/cpu4/cpufreq/chill/down_threshold_suspended 99
write /sys/devices/system/cpu/cpu0/cpufreq/relaxed/up_threshold 75
write /sys/devices/system/cpu/cpu4/cpufreq/chill/up_threshold 90
write /sys/class/kgsl/kgsl-3d0/devfreq/governor powersave
write /sys/class/leds/lcd-backlight/max_brightness 100
write /dev/cpuset/foreground/cpus 0-2,4-5
write /dev/cpuset/foreground/boost/cpus 4-5
write /dev/cpuset/top-app/cpus 0-5
write /sys/module/lazyplug/parameters/nr_possible_cores 6
# Gaming
on property:persist.spectrum.profile=3
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 302400
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/go_hispeed_load 75
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/above_hispeed_delay 0
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_rate 40000
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/hispeed_freq 960000
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/timer_slack -1
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/target_loads 80 384000:33 460800:25 600000:50 672000:65 787200:70 864000:85 960000:90 1248000:92
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/min_sample_time 50000
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/boost 1
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/align_windows 0
write /sys/devices/system/cpu/cpu0/cpufreq/interactive/max_freq_hysteresis 166667
write /sys/devices/system/cpu/cpu4/cpufreq/scaling_governor interactive
write /sys/devices/system/cpu/cpu4/cpufreq/scaling_min_freq 633600
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/go_hispeed_load 90
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/above_hispeed_delay 0
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_rate 20000
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/hispeed_freq 1440000
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/timer_slack -1
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/target_loads 74 768000:73 864000:64 960000:80 1248000:61 1344000:69 1440000:64 1536000:74 1632000:69 1689600:67 1824000:72
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/min_sample_time 30000
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/boost 1
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/align_windows 0
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/use_migration_notif 1
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/use_sched_load 1
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/max_freq_hysteresis 20000
write /sys/devices/system/cpu/cpu4/cpufreq/interactive/boostpulse_duration 80000
write /sys/module/cpu_boost/parameters/input_boost_enabled 1
write /sys/module/cpu_boost/parameters/input_boost_freq "0:1248000 1:1248000 2:1248000 3:1248000 4:0 5:0 6:0 7:0"
write /sys/module/cpu_boost/parameters/boost_ms 80
write /sys/module/cpu_boost/parameters/input_boost_ms 420
write /sys/module/msm_performance/parameters/touchboost 0
write /sys/class/leds/lcd-backlight/max_brightness 255
write /sys/class/kgsl/kgsl-3d0/devfreq/governor msm-adreno-tz
write /sys/module/adreno_idler/parameters/adreno_idler_active 0
write /dev/cpuset/foreground/cpus 0-2,4-7
write /dev/cpuset/foreground/boost/cpus 4-7
write /dev/cpuset/top-app/cpus 0-7
write /sys/module/lazyplug/parameters/nr_possible_cores 8
Recompile and your ready to go!
Some tips for profiles:
Make sure all profiles tweak the same parameters. Parameters don't get reset, when profile changes, so you have to make sure to change them back.
Not all profiles have to be complex! You could have one profile for your kernel and just use spectrum for minor tweaks
Spectrum injector
Spectrum Injector is a new method of adding spectrum support to your kernel! If the kernel you're running doesn't support Spectrum, you can add support without modifying it by flashing the spectrum injector zip. If the kernel does support Spectrum, flashing the zip will overwrite it and allow you to create your own profiles without decompiling the boot.img.
NOTE: These profiles are empty by default! You must customize them for them to do anything.
How to:
To create your profiles, you only need to modify the files located in /sdcard/Spectrum/profiles/ on your device.
These profiles are like ramdisk files, they accept commands of the format:
Code:
write /path/to/file value-to-set
along with all bash commands included in android such as
echo
chmod
chown
cp
mv
setprop
Once you have created your own custom profiles, you can apply them with the Spectrum app. Feel free to share your creations with other users, but remember, I'm not responsible for poorly written profiles that harm your device.
Download:https://www.androidfilehost.com/?fid=745425885120749066
Noice, thanks
p70shooter said:
Noice, thanks
Click to expand...
Click to collapse
Testing spectrum, sadly I'm not able to add the quicktile. It disappears before I can drag it onto my active QT...
Augustin79 said:
Testing spectrum, sadly I'm not able to add the quicktile. It disappears before I can drag it onto my active QT...
Click to expand...
Click to collapse
That's a Nougat issue. Adding more columns to your QS should be a temp fix.
The Flash said:
That's a Nougat issue. Adding more columns to your QS should be a temp fix.
Click to expand...
Click to collapse
Ah, of course! Thanks
Augustin79 said:
Ah, of course! Thanks
Click to expand...
Click to collapse
Wow @The Flash as faster at support than me for my own app. Guess thats how he got his name
Looks promising, but I'm awful at tuning kernel
Sent from my Redmi 3 using XDA Labs
frap129 said:
Wow @The Flash as faster at support than me for my own app. Guess thats how he got his name
Click to expand...
Click to collapse
krasCGQ said:
Looks promising, but I'm awful at tuning kernel
Sent from my Redmi 3 using XDA Labs
Click to expand...
Click to collapse
One thing that helped me a lot was just learning what the tunables actually do: https://android.googlesource.com/ke...3.10/Documentation/cpu-freq/governors.txt#222
That documentation is a bit dense but can help a BUNCH when tweaking the governor. I'm always available to help with learning about tunables
Now testing the battery oriented profile with flash kernel and 7.1.2 PN. Thanks @frap129!
weazie said:
Now testing the battery oriented profile with flash kernel and 7.1.2 PN. Thanks @frap129!
Click to expand...
Click to collapse
Glad you like it!
Till now it's running amazingly for me. Great idle battery life and very smooth with the default settings. Great job!!
frap129 said:
Glad you like it!
Click to expand...
Click to collapse
For some odd reason, the device was awake all the time, but I didn't have BBS or wakelock detector installed... Now I do. I'll be back
weazie said:
For some odd reason, the device was awake all the time, but I didn't have BBS or wakelock detector installed... Now I do. I'll be back
Click to expand...
Click to collapse
That's not really a Spectrum issue, since the app doesn't hold any wakelocks.
Could you please attach the GitHub files... I'm having a hell of a time getting them downloaded on mobile...
Edit: I got it... But man...
Sent from my Nexus 6 using Tapatalk
rignfool said:
Could you please attach the GitHub files... I'm having a hell of a time getting them downloaded on mobile...
Edit: I got it... But man...
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Why are you downloading them on mobile? Patching your ramdisk on your device?
frap129 said:
Why are you downloading them on mobile? Patching your ramdisk on your device?
Click to expand...
Click to collapse
Android Image Kitchen for Mobile Magisk version
by @Oms0sis
And yeah... No Linux machine at my house...
I've been hacking Franco's profiles into the kernels I use for a few weeks now... And this makes my life a little easier... I only have to edit one file... And import one script and I can run the 3 things I use on init...
I wonder if you could use the image kitchen to modify on device thru the app interface...
Oh... And I get a crash on startup with the app...http://cloud.tapatalk.com/s/590d20a022a97/Log_2017-05-05_21-01-26.txt
Sent from my Nexus 6 using Tapatalk
rignfool said:
Android Image Kitchen for Mobile Magisk version
by @Oms0sis
And yeah... No Linux machine at my house...
I've been hacking Franco's profiles into the kernels I use for a few weeks now... And this makes my life a little easier... I only have to edit one file... And import one script and I can run the 3 things I use on init...
I wonder if you could use the image kitchen to modify on device thru the app interface...
Oh... And I get a crash on startup with the app...http://cloud.tapatalk.com/s/590d20a022a97/Log_2017-05-05_21-01-26.txt
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks for the log! It looks like a rom issue as it doesnt report an error or reason that it stopped, but i could be wrong. I'll look into it

How do I change zram size / disable it with magisk boot script ?

How do i change zram size ? by editing etc/fstab ? or sth else ? i dont like swappoff devblockzram0 cuz its hit or miss
Guan Yu said:
How do i change zram size ? by editing etc/fstab ? or sth else ? i dont like swappoff devblockzram0 cuz its hit or miss
Click to expand...
Click to collapse
HI
The swap device is configured early in the boot process -- on my Zenfone 8 running the original Android 12 from ASUS or the CustomROM OmniROM 12 It's configured with the script
/vendor/bin/init.asus.zram.sh
On other phones the script will be different I assume; just grep for zram0 in the files in /vendor/bin.
The script init.asus.zram.sh uses these properties to get the values to configure the swap device
vendor.zram.disksize=2147483648
vendor.zram.enable=1
This might also be different in other ROMs -- just check the init script to create the swap device on your phone.
Important here is that the script to init the swap devices runs before Magisk is active so you can neither replace the script with a patched version nor change the properties used by the script before the script is running.
So the only useful method to change the size of the swap device is to create a Magisk Script to delete and recreate the swap device (at the time the Magisk script is running the swap device should not be in use).
Examples for how to do that are here:
See here:
https://forum.xda-developers.com/t/how-to-disable-or-change-the-swap-device-in-the-android-12-from-asus-for-the-zenfone-8.4495085/
for a method to change the swap device config in the Original ASUS Android 12
See here:
https://forum.xda-developers.com/t/...p-device-in-the-omnirom-using-magisk.4495415/
for a method to change the swap device config in the OnmiROM 12
Most probably one of the methods will also work for your ROM
And last :
Be aware that /dev/block/zram0 occupies memory only if required, e.g. a not used swap device will only need a few bytes for the control structures
regards
Bernd

Categories

Resources