That is the wrong twrp. No version number, no phone model (in this case dreamlte) where did you pick that up from even?can somebody help me fix this error on installing twrp? thank you
That is the wrong twrp. No version number, no phone model (in this case dreamlte) where did you pick that up from even?can somebody help me fix this error on installing twrp? thank you
@madhatter57so regarding the audio issue, i tried last kernel/app version and put the audio cpu value all the way up to 1700ish. Sometimes it works, sometimes it doesn't, but overall it seems better.
I also noticed that sound gets distorted sometimes when adding too many effects, that might have to do with processing power as well?
adb shell
su
top
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
3739 audioserver 20 0 102M 8.9M 4.3M S 73.3 0.2 35:36.56 audioserver
3853 mediacodec 20 0 53M 3.6M 2.5M S 8.0 0.0 34:47.50 media.codec hw/[email protected]
3831 media 20 0 112M 4.7M 3.7M S 7.3 0.1 0:06.96 mediaserver
3709 audioserver 20 0 37M 3.5M 2.1M S 6.3 0.0 4:10.75 [email protected]
23259 root 20 0 12M 4.0M 3.4M R 4.6 0.1 0:04.08 top
4014 system 18 -2 5.3G 288M 201M S 1.6 7.7 24:32.48 system_server
...
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
3739 audioserver 20 0 102M 5.8M 4.1M S 46.6 0.1 44:16.54 audioserver
3853 mediacodec 20 0 53M 3.5M 2.2M S 5.0 0.0 35:47.16 media.codec hw/[email protected]
3831 media 20 0 113M 4.4M 3.3M S 4.6 0.1 0:59.05 mediaserver
3709 audioserver 20 0 38M 2.9M 1.9M S 4.3 0.0 4:54.78 [email protected]
PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS
23452 u0_a196 20 0 6.0G 287M 221M S 13.6 7.7 0:36.88 com.sec.android.app.music
25990 root 20 0 12M 4.5M 3.6M R 6.0 0.1 0:00.43 top
23753 u0_a88 20 0 4.6G 151M 133M S 3.0 4.0 0:12.42 com.sec.android.app.soundalive
25927 system 20 0 3.7G 96M 90M S 2.0 2.5 0:00.14 com.samsung.android.lool
1512 root 0 -20 0 0 0 D 1.3 0.0 4:05.04 [cpu_dvfsd]
1118 root 0 -20 0 0 0 D 1.3 0.0 3:42.08 [gpu_dvfsd]
24000 u0_a8 20 0 4.2G 102M 98M S 1.0 2.7 0:00.32 com.samsung.android.app.aodservice:provider
2011 u0_a225 20 0 4.2G 150M 126M S 1.0 4.0 0:17.89 com.ace2nutzer.settings.g95x
4014 system 18 -2 5.3G 292M 199M S 1.0 7.8 25:31.59 system_server
22819 u0_a195 20 0 4.2G 138M 124M S 0.6 3.7 1:08.14 com.futuremark.dmandroid.application
5423 system 20 0 3.8G 112M 102M S 0.6 3.0 1:48.84 com.sec.android.sdhms
3831 media 20 0 108M 5.3M 3.2M S 0.6 0.1 1:13.57 mediaserver
3739 audioserver 20 0 105M 6.4M 4.0M S 0.6 0.1 46:18.90 audioserver
what happened to the idea of moving audio processing to the big cpu?
yesterday i posted a message on how to reproduce the issues, today i can't see it, not sure if it's some bug from xda...excuse me also for being slow and not following all the messages here, sometimes the xda app doesn't notify me of posts here.
i just rename the latest twrp version. 3.6.x somethingThat is the wrong twrp. No version number, no phone model (in this case dreamlte) where did you pick that up from even?
Don't use 3.6.x. It was giving me a bootloop. Use the one in the first page of the thread.
Won't start like what?Hi guys. I've been using your kernel for about 1-2 months now, and now I've created an account on xda. Developer, can you help me, some games won't start for me. name: standoff 2
I think it's because of the RAM. I'm fine with my phone.
@madhatter57
Did you reduce the little CPU Freq from stock value ? - Try to keep at 1690 MHz. Also check your little CPU suspend max_freq, try to keep 1690 MHz as well. And on Audio PM-QOS put 1690 MHz as well.
up_threshold value and boost on/off doesn't matter since we can set PM-QOS.
I use the original "Samsung Music" app and even if I enable all the sound improvements it still works fine with just 832 MHz. (tested with headphones, screen on/off)
Maybe you go over 0dB = distortion. Or little CPU is over 100% load.
Best way to check this is by using ADB while music is running over screen off with headphones.
e.g.
Code:adb shell su top PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS 3739 audioserver 20 0 102M 8.9M 4.3M S 73.3 0.2 35:36.56 audioserver 3853 mediacodec 20 0 53M 3.6M 2.5M S 8.0 0.0 34:47.50 media.codec hw/[email protected] 3831 media 20 0 112M 4.7M 3.7M S 7.3 0.1 0:06.96 mediaserver 3709 audioserver 20 0 37M 3.5M 2.1M S 6.3 0.0 4:10.75 [email protected] 23259 root 20 0 12M 4.0M 3.4M R 4.6 0.1 0:04.08 top 4014 system 18 -2 5.3G 288M 201M S 1.6 7.7 24:32.48 system_server ...
audioserver 73% with "UHQ Upscaler" + "Dolby Atmos"
PM-QOS 832 MHz = no scratching at all.
If I set 1690 MHz for PM-QOS i get only 46% load on audioserver:
Code:PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS 3739 audioserver 20 0 102M 5.8M 4.1M S 46.6 0.1 44:16.54 audioserver 3853 mediacodec 20 0 53M 3.5M 2.2M S 5.0 0.0 35:47.16 media.codec hw/[email protected] 3831 media 20 0 113M 4.4M 3.3M S 4.6 0.1 0:59.05 mediaserver 3709 audioserver 20 0 38M 2.9M 1.9M S 4.3 0.0 4:54.78 [email protected]
Note if even @ 1690 MHz you get over 80% load on audioserver it's an issue with too high CPU load and therefore the only way to fix would be to use other codecs that are more efficient or to move audio stuff to the big CPU. That would work but it'll drain a lot of battery for just playing music lol.
Personally I play music with only "Tube Amp-Pro" and there is almost no load at all and works just fine without to force any higher CPU Freq for the little core. In fact it works fine with 455 MHz:
Code:PID USER PR NI VIRT RES SHR S[%CPU] %MEM TIME+ ARGS 23452 u0_a196 20 0 6.0G 287M 221M S 13.6 7.7 0:36.88 com.sec.android.app.music 25990 root 20 0 12M 4.5M 3.6M R 6.0 0.1 0:00.43 top 23753 u0_a88 20 0 4.6G 151M 133M S 3.0 4.0 0:12.42 com.sec.android.app.soundalive 25927 system 20 0 3.7G 96M 90M S 2.0 2.5 0:00.14 com.samsung.android.lool 1512 root 0 -20 0 0 0 D 1.3 0.0 4:05.04 [cpu_dvfsd] 1118 root 0 -20 0 0 0 D 1.3 0.0 3:42.08 [gpu_dvfsd] 24000 u0_a8 20 0 4.2G 102M 98M S 1.0 2.7 0:00.32 com.samsung.android.app.aodservice:provider 2011 u0_a225 20 0 4.2G 150M 126M S 1.0 4.0 0:17.89 com.ace2nutzer.settings.g95x 4014 system 18 -2 5.3G 292M 199M S 1.0 7.8 25:31.59 system_server 22819 u0_a195 20 0 4.2G 138M 124M S 0.6 3.7 1:08.14 com.futuremark.dmandroid.application 5423 system 20 0 3.8G 112M 102M S 0.6 3.0 1:48.84 com.sec.android.sdhms 3831 media 20 0 108M 5.3M 3.2M S 0.6 0.1 1:13.57 mediaserver 3739 audioserver 20 0 105M 6.4M 4.0M S 0.6 0.1 46:18.90 audioserver
Didn't implement it so far, since it doesn't seem to be really needed.
Yes I know, you'd posted on Note8 forum, we are here on S8 forum.
That is not how it works
Standoff 2 can run on toasters. There has to be another reason.Hi guys. I've been using your kernel for about 1-2 months now, and now I've created an account on xda. Developer, can you help me, some games won't start for me. name: standoff 2
I think it's because of the RAM. I'm fine with my phone.
Hmm I don't think it's any kernel issue. Also I doubt it's related to too low RAM. This kernel has the biggest amount of RAM for the S8 exynos series. So probably it's a bug with the game itself. Maybe Android 9 not fully compatible for that game. Or maybe not compatible with the ROM ? Have no idea what ever custom ROM you use and what ever mods you did on ROM side. Good luck.Hi guys. I've been using your kernel for about 1-2 months now, and now I've created an account on xda. Developer, can you help me, some games won't start for me. name: standoff 2
I think it's because of the RAM. I'm fine with my phone.
thanks brother, if you need any testing, let me know.@madhatter57
Alright, I'll see what I can do for next release. Thanks for your inputs.
I used 2 ROMs, it was a regular android 9 stock. And horizon ROM please help. It works for me with a regular kernel, but yours will be betterHmm I don't think it's any kernel issue. Also I doubt it's related to too low RAM. This kernel has the biggest amount of RAM for the S8 exynos series. So probably it's a bug with the game itself. Maybe Android 9 not fully compatible for that game. Or maybe not compatible with the ROM ? Have no idea what ever custom ROM you use and what ever mods you did on ROM side. Good luck.
@madhatter57
Alright, I'll see what I can do for next release. Thanks for your inputs.
For dex you need charger to active the dex i don't know that can happen with this maybe dev know where the issue is,Hi @ace2nutzer
just wanna thank you for all your work (and active contributors of course) and let you know that i'm realllllllly late for joining the party, i started using your kernel since 20220624 version and right now i'm enjoying the 20220701 version in combine with the latest stock rom i had from OTA. Never really thought i would need root or even change the recovery/kernel coz the stock rom and kernel was already good as it is.
Originally, my motivation to jump aboard was the dex and drivedroid support.. but now i got the UV tuning madness coming back to me, still trying hard not to tweak performance settings til i'm sure my applications works without issue
there are 2 questions tho :
- drivedroid works but still can't figure out to working dex on my non-smart tv, is there a specific setting i need to switch before it could be activated?
- ANYBODY here use filmorago? mine used to work with no issue on stock kernel, but now it hangs on the splash screen but never enters ANR or crash. logcat shows nothing weird except for EGLint returns 0x3000 (tried clearing data, corpses/remnants, uninstall-installing, enabled all permissions for that darned app to no avail)
any solutions / recommendations appreciated.
TIA
I have test it and stuck at splash screenANYBODY here use filmorago? mine used to work with no issue on stock kernel, but now it hangs on the splash screen but never enters ANR or crash. logcat shows nothing weird except for EGLint returns 0x3000 (tried clearing data, corpses/remnants, uninstall-installing, enabled all permissions for that darned app to no avail)
Nope, this is not how it should be done. You need Linux OS (e.g. Lubuntu) with installed "git" versioning system.
#
# NOTE! Don't add files that are generated in specific
# subdirectories here. Add them in the ".gitignore" file
# in that subdirectory instead.
#
# NOTE! Please use 'git ls-files -i --exclude-standard'
# command after changing this file, to see if there are
# any tracked files which get ignored after the change.
#
# Normal rules
#
.*
*.o
*.o.*
*.a
*.s
*.ko
*.so
*.so.dbg
*.mod.c
*.i
*.lst
*.symtypes
*.order
*.elf
*.bin
*.tar
*.gz
*.bz2
*.lzma
*.xz
*.lz4
*.lzo
*.patch
*.gcno
*.ll
modules.builtin
Module.symvers
*.dwo
*.su
#
# Top-level generic files
#
/tags
/TAGS
/linux
/vmlinux
/vmlinux.32
/vmlinux-gdb.py
/vmlinuz
/System.map
/Module.markers
#
# Debian directory (make deb-pkg)
#
/debian/
#
# tar directory (make tar*-pkg)
#
/tar-install/
#
# git files that we don't want to ignore even it they are dot-files
#
!.gitignore
!.mailmap
#
# Generated include files
#
include/config
include/generated
arch/*/include/generated
# stgit generated dirs
patches-*
# quilt's files
patches
series
# cscope files
cscope.*
ncscope.*
# gnu global files
GPATH
GRTAGS
GSYMS
GTAGS
# id-utils files
ID
*.orig
*~
\#*#
#
# Leavings from module signing
#
extra_certificates
signing_key.pem
signing_key.priv
signing_key.x509
x509.genkey
# Kconfig presets
all.config
# Kdevelop4
*.kdev4
# platform specific
scripts/rkp_cfp/common.pyc
scripts/rkp_cfp/tmp/
# custom files
clean
arch/arm64/boot/Image
*.dtb
rejects
git init
git add .
git commit -am "initial commit"
git remote add master https://github.com/opensourcefreak/KOLUMN_Kernel.git
git push --set-upstream master master
git commit -am "CPU: added OC support"
git push
Yes but probably it's locked like all the other clocks it was. So it needs first some hacks like always. I remember on Ace 2 we OC'ed lcd_clk from 50 MHz up to 100 MHz. 100 MHz was sometimes unstable, but 80 MHz worked stable. Now that "50" is just LCD_CLK not refresh_rate. Also I don't know how it should be calculated ... 50 MHz = 60 hz and @ 100 Mhz = 120 Hz lol. Anyway at 80 MHz, probably around 100 Hz was it possible to scroll text without to cause eye cancer. Here on S8 there is also such LCD_CLK, but even increasing it, I don't see any difference, maybe I'll try this once again. There is also refresh value = 60, but even changing this @ 100, just changes nothing, so I suspect it's locked like I said.Hey @ace2nutzer. I have a question. It’s just a random one out of curiosity though, theory. I don’t ask to have it implemented because I know it isnt worth it at all.
But would AMOLED overclock be possible? Could somebody make S8’s screen go from say 60hz to 65hz? Or is 60hz hardware limit?
Yes, that's right, because it gets out of sync. @ 80 or 100 hz it'll run probably smooth without the need to adapt other stuff in ROM, which is way more complicated.I was see the option when using mhl in screen option there 75hz rate for monitor but that reduce quality of the screen i mean the color get washed but in reality screen that still 60hz sometime i face glitch when use 75hz
Good idea, I'll see if I can do something.hello guys, could someone help me and tell me how I can mount a usb hdd in ntfs format? I have the ntfs option activated but the unit does not appear, I think I need to mount it, how could I do it?
You should definitely be more specific.When i install this kernel i get stuck in the boot screen (Samsung galsxy s8 powered by android) Model: G950F Exynos variant
su // only for termux app
cd /sys/module/abox/parameters
cat user_pm_qos_lit // check current value
echo 949000 > user_pm_qos_lit // e.g. set to 949 MHz
# To apply the change at boot, like always, copy paste the cmds to
# /system/etc/init.d/99_user without the "su" cmd of course.
adb shell
su
cd /sys/power
# print dvfs table so we can see current votlage table !
echo 1 > print_dvfs_table
dmesg
[ 5808.312763] dvfs_type : dvfs_mif - id : 0
[ 5808.312784] num_of_lv : 12
[ 5808.312791] num_of_members : 4
[ 5808.312802] lv : [2093000], volt = 850000 uV
[ 5808.312814] lv : [2002000], volt = 850000 uV
[ 5808.312825] lv : [1794000], volt = 762500 uV
[ 5808.312835] lv : [1540000], volt = 712500 uV
[ 5808.312846] lv : [1352000], volt = 675000 uV
[ 5808.312856] lv : [1014000], volt = 637500 uV
[ 5808.312867] lv : [ 845000], volt = 606250 uV
[ 5808.312877] lv : [ 676000], volt = 593750 uV
[ 5808.312887] lv : [ 546000], volt = 587500 uV
[ 5808.312896] lv : [ 421000], volt = 581250 uV
[ 5808.312907] lv : [ 286000], volt = 581250 uV
[ 5808.312917] lv : [ 208000], volt = 581250 uV
[ 5808.312938] dvfs_type : dvfs_int - id : 1
[ 5808.312945] num_of_lv : 7
[ 5808.312951] num_of_members : 16
[ 5808.312962] lv : [ 667000], volt = 781250 uV
[ 5808.312972] lv : [ 533000], volt = 756250 uV
[ 5808.312982] lv : [ 400000], volt = 643750 uV
[ 5808.312991] lv : [ 333000], volt = 612500 uV
[ 5808.313001] lv : [ 267000], volt = 587500 uV
[ 5808.313011] lv : [ 178000], volt = 575000 uV
[ 5808.313020] lv : [ 107000], volt = 575000 uV
[ 5808.313040] dvfs_type : dvfs_cpucl0 - id : 2
[ 5808.313047] num_of_lv : 18
[ 5808.313053] num_of_members : 1
[ 5808.313062] lv : [2808000], volt = 1300000 uV
[ 5808.313071] lv : [2704000], volt = 1175000 uV
[ 5808.313082] lv : [2652000], volt = 1150000 uV
[ 5808.313092] lv : [2574000], volt = 1081250 uV
[ 5808.313102] lv : [2496000], volt = 1037500 uV
[ 5808.313113] lv : [2314000], volt = 962500 uV
[ 5808.313123] lv : [2158000], volt = 906250 uV
[ 5808.313133] lv : [2002000], volt = 868750 uV
[ 5808.313144] lv : [1937000], volt = 850000 uV
[ 5808.313154] lv : [1807000], volt = 812500 uV
[ 5808.313164] lv : [1703000], volt = 781250 uV
[ 5808.313175] lv : [1469000], volt = 737500 uV
[ 5808.313185] lv : [1261000], volt = 706250 uV
[ 5808.313196] lv : [1170000], volt = 687500 uV
[ 5808.313206] lv : [1066000], volt = 668750 uV
[ 5808.313216] lv : [ 962000], volt = 656250 uV
[ 5808.313227] lv : [ 858000], volt = 643750 uV
[ 5808.313237] lv : [ 741000], volt = 625000 uV
[ 5808.313256] dvfs_type : dvfs_cpucl1 - id : 3
[ 5808.313262] num_of_lv : 12
[ 5808.313268] num_of_members : 1
[ 5808.313279] lv : [2002000], volt = 1300000 uV
[ 5808.313289] lv : [1898000], volt = 1200000 uV
[ 5808.313300] lv : [1794000], volt = 1137500 uV
[ 5808.313310] lv : [1690000], volt = 1062500 uV
[ 5808.313321] lv : [1456000], volt = 937500 uV
[ 5808.313331] lv : [1248000], volt = 831250 uV
[ 5808.313342] lv : [1053000], volt = 775000 uV
[ 5808.313352] lv : [ 949000], volt = 743750 uV
[ 5808.313363] lv : [ 832000], volt = 712500 uV
[ 5808.313373] lv : [ 715000], volt = 675000 uV
[ 5808.313384] lv : [ 598000], volt = 643750 uV
[ 5808.313394] lv : [ 455000], volt = 618750 uV
[ 5808.313413] dvfs_type : dvfs_g3d - id : 4
[ 5808.313419] num_of_lv : 9
[ 5808.313426] num_of_members : 1
[ 5808.313436] lv : [ 839000], volt = 750000 uV
[ 5808.313447] lv : [ 764000], volt = 750000 uV
[ 5808.313457] lv : [ 683000], volt = 700000 uV
[ 5808.313467] lv : [ 572000], volt = 718750 uV
[ 5808.313478] lv : [ 546000], volt = 706250 uV
[ 5808.313488] lv : [ 455000], volt = 693750 uV
[ 5808.313499] lv : [ 385000], volt = 693750 uV
[ 5808.313509] lv : [ 338000], volt = 693750 uV
[ 5808.313520] lv : [ 260000], volt = 693750 uV
[ 5808.313539] dvfs_type : dvfs_intcam - id : 5
[ 5808.313545] num_of_lv : 4
[ 5808.313551] num_of_members : 4
[ 5808.313561] lv : [ 690000], volt = 812500 uV
[ 5808.313572] lv : [ 680000], volt = 687500 uV
[ 5808.313583] lv : [ 670000], volt = 637500 uV
[ 5808.313593] lv : [ 640000], volt = 575000 uV
[ 5808.313610] dvfs_type : dvfs_cam - id : 6
[ 5808.313616] num_of_lv : 7
[ 5808.313623] num_of_members : 22
[ 5808.313633] lv : [ 690000], volt = 793750 uV
[ 5808.313644] lv : [ 680000], volt = 793750 uV
[ 5808.313654] lv : [ 670000], volt = 756250 uV
[ 5808.313665] lv : [ 660000], volt = 693750 uV
[ 5808.313675] lv : [ 650000], volt = 693750 uV
[ 5808.313685] lv : [ 640000], volt = 575000 uV
[ 5808.313696] lv : [ 630000], volt = 575000 uV
[ 5808.313713] dvfs_type : dvfs_disp - id : 7
[ 5808.313719] num_of_lv : 5
[ 5808.313725] num_of_members : 2
[ 5808.313735] lv : [ 630000], volt = 750000 uV
[ 5808.313746] lv : [ 533000], volt = 712500 uV
[ 5808.313756] lv : [ 356000], volt = 631250 uV
[ 5808.313767] lv : [ 214000], volt = 587500 uV
[ 5808.313777] lv : [ 134000], volt = 575000 uV
[ 5808.313794] dvfs_type : dvs_g3dm - id : 8
[ 5808.313800] num_of_lv : 9
[ 5808.313807] num_of_members : 1
[ 5808.313817] lv : [ 839000], volt = 0 uV
[ 5808.313827] lv : [ 764000], volt = 0 uV
[ 5808.313837] lv : [ 683000], volt = 0 uV
[ 5808.313847] lv : [ 572000], volt = 718750 uV
[ 5808.313858] lv : [ 546000], volt = 712500 uV
[ 5808.313869] lv : [ 455000], volt = 700000 uV
[ 5808.313880] lv : [ 385000], volt = 700000 uV
[ 5808.313890] lv : [ 338000], volt = 700000 uV
[ 5808.313900] lv : [ 260000], volt = 700000 uV
[ 5808.313917] dvfs_type : dvs_cp - id : 9
[ 5808.313924] num_of_lv : 3
[ 5808.313930] num_of_members : 1
[ 5808.313940] lv : [1500000], volt = 850000 uV
[ 5808.313951] lv : [1066000], volt = 731250 uV
[ 5808.313961] lv : [ 800000], volt = 731250 uV
# lets say you want to undervolt big CPU Freq step 2314 MHz @ 900 mV:
# the format string is here: "rate volt" (KHz uV)
echo "2314000 900000" > cpu_big_volt
# after that you could again print the dvfs table to verify if new voltage was successfully applied.
echo 1 > print_dvfs_table
dmesg
# now lets say you want to undervolt little CPU Freq step 1690 MHz @ 950 mV:
# the format string is here: "rate volt" (KHz uV)
echo "1690000 950000" > cpu_lit_volt
# now likely you want to undervolt GPU Freq step 546 MHz @ 650 mV:
# the format string is here: "rate volt" (KHz uV)
cd /sys/kernel/gpu
# first check current GPU volt table:
cat gpu_asv_table
GPU, vol, min, max, down_stay, mif, cpu0, cpu1
839000, 750000, 43, 75, 1, 2093000, 0, 0
764000, 750000, 42, 75, 1, 2093000, 0, 0
683000, 700000, 38, 75, 1, 2093000, 0, 0
572000, 718750, 47, 75, 1, 2093000, 0, 0
546000, 706250, 37, 75, 1, 2093000, 0, 0
455000, 693750, 38, 75, 1, 2093000, 0, 0
385000, 693750, 41, 75, 1, 2093000, 0, 0
338000, 693750, 33, 75, 1, 2093000, 0, 0
260000, 693750, 33, 75, 1, 1352000, 0, 0
echo "546000 650000" > gpu_volt
# and check ...
cat gpu_asv_table
GPU, vol, min, max, down_stay, mif, cpu0, cpu1
839000, 750000, 43, 75, 1, 2093000, 0, 0
764000, 750000, 42, 75, 1, 2093000, 0, 0
683000, 700000, 38, 75, 1, 2093000, 0, 0
572000, 718750, 47, 75, 1, 2093000, 0, 0
546000, 650000, 37, 75, 1, 2093000, 0, 0
455000, 693750, 38, 75, 1, 2093000, 0, 0
385000, 693750, 41, 75, 1, 2093000, 0, 0
338000, 693750, 33, 75, 1, 2093000, 0, 0
260000, 693750, 33, 75, 1, 1352000, 0, 0
# you can undervolt every single step, so lets undervolt 455 MHz step as well @ 650 mV:
echo "455000 650000" > gpu_volt
# now maybe you want even to undervolt RAM.
# we need to go again to /sys/power ...
cd /sys/power
# take a look at the dvfs table, the very first entry "dvfs_mif - id : 0"
this is RAM freq - volt table and our max_freq is 1794 MHz.
# we will undervolt Freq step 1794 MHz @ 700 mV:
# the format string is here: "id rate volt" (intent KHz uV)
# this sysfs interface is universal and you can undervolt any voltage table you want by using the corresponding "id":
echo "0 1794000 700000" > update_dvfs_table
# and verify:
echo 1 > print_dvfs_table
dmesg
# id 4 would be for GPU (dvfs_g3d) and so on ...
# to run all the cmds for undervolting at boot, just do something like this:
# open the script /system/etc/init.d.a2n/a2n_user and copy paste your cmds:
cd /sys/power
echo "2314000 900000" > cpu_big_volt
echo "1690000 950000" > cpu_lit_volt
echo "0 1794000 700000" > update_dvfs_table
cd /sys/kernel/gpu
echo "546000 650000" > gpu_volt
echo "455000 650000" > gpu_volt
# under the line: "# A2N init.d Script"
# save and enjoy !