yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] 7175:
I think most roms keep init.d support rom-side, so a service is triggered in /init.rc or /init.local.rc that runs /system/bin/sysinit which in-turn executes "run-parts /system/etc/init.d". You can check for this service with:

grep -E '(sysinit|init\.d)' /init.*

... in the terminal/adb. init.rc be modified in the ramdisk to include the service if neither the rom nor the kernel provides init.d support. Nuclearmistake made a flash zip to add init.d support this way, but I can't seem to find it. I could guide you through it's process in the terminal, which isn't too difficult.

Also to check if it's in sbin, do:

grep -rE '(sysinit|run\-parts)' /sbin

.
[Samsung Galaxy Nexus] Thymo:
So this means it's supported? If so i just have to do mkdir /system/etc/init.d right?

EDIT: Picture doesn't want to upload but it shows this

init.carbon.rc:# sysinit (/system/etc/init.d)
[Samsung Galaxy Nexus] Ashtrix:
[MENTION=4615478]boype[/MENTION], After running for more than 48hrs of r55, I can confirm that r54 runs cooler over r55 in various scenarios (wifi, gaming) plus more stable, battery and a bit of more speed....

Running r54 now :good: !!

P.S : That wifi recon bug is gone on my slimkat 7.4, could also be a rom issue i guess as most people reported that....
[Samsung Galaxy Nexus] boype:
The wifi bug is most likely not gone whatsoever. Its occurrence is just a little peculiar:

When you reboot your phone and immediately connect to your wifi, the bug will not occur.

When you leave home / disable wifi for some and then come back home / reconnect wifi, the bug is there.

At least this is what I observe with my phone.
[Samsung Galaxy Nexus] Ziyan:
Sounds like something else is wrong. I just tried it, works fine, it shows the charging images and the percentage too. Here's how last_kmsg should look like.

[ 0.000000] Kernel command line: ... androidboot.mode=charger ...
[ 4.738342] charger: --------------- STARTING CHARGER MODE ---------------
[Samsung Galaxy Nexus] Ashtrix:
-deleted-

Bug still persists, i was wrong...:(
[Samsung Galaxy Nexus] FredFS456:
No, that's what I tried first. specifically:

su [saw root confirmation in the form of "#"]
cat /proc/last_kmsg > /sdcard/last_kmsg.txt [says something about last_kmsg not found]

I dunno. What might be interfering with it? r54 works with the charging images and percentage for me fine, but r55 doesn't (just restoring back and forth w/ Trickster MOD). I might try to re-download the kernel, but I dunno if that would help, seeing that it boots and runs fine. Xposed is not kernel-level I think, so those modules should not be interfering. I'm running:

PA4.5beta2, Xposed 2.6.1, baseband UGLL1, bootloader PRIMELC03
[Samsung Galaxy Nexus] aosp:
[MENTION=4615478]boype[/MENTION] offmode should work after reverting this OMAPFB: Do not suspend on FB BLANK, instead disable panel · 1a54175 · boype/kernel_tuna_kk44 · GitHub - http://goo.gl/BsKgFD

Like [MENTION=2633638]Ziyan[/MENTION] did below

Revert "OMAPFB: Do not suspend on FB BLANK, instead disable panel" · 1c66a65 · Ziyann/omap · GitHub - http://goo.gl/mYCIsV

Caused bootlogo delay on tuna.
[Samsung Galaxy Nexus] siealex:
R55 uses 224 MHz as the lowest frequency, earlier builds use 192 MHz. Isn`t this the cause?
[Samsung Galaxy Nexus] Ashtrix:
I never used 192MHz step only 384 as min for me ;). Plus the ol r54 is smooth over the r55 in my experience as for now...
[Samsung Galaxy Nexus] thomstrack:
Google Stock Jelly Bean 4.3 (JWR66Y) :)
[Samsung Galaxy Nexus] 7175:
Yeah it looks like the sysinit service is there, so yes, just (mkdir /system/etc/init.d; chmod 0755 ...) and test out some scripts that you can verify, e.g.:

#!/system/bin/sh
# test file write at startup
date > /sdcard/date

edit- Forgot to mention I'm getting some nice results on R55 with Vanir 4.3.1: Check this out:

https://www.dropbox.com/s/vvan5sh1zbfsawi/Screenshot_2014-08-25-08-34-15.png
[Samsung Galaxy Nexus] SoftWord:
have u noticed problems like lag, low memory etc?
[Samsung Galaxy Nexus] FredFS456:
No, I believe that r54 also uses 224MHz as lowest step.
[Samsung Galaxy Nexus] infectedorganism:
Would a logcat give some insight as to why my phone soft reboots after 24 hours?

I notice my phone getting slower as it approaches 24 hours uptime. After it passes the 24 hour mark, a soft reboot is inevitable -- its just a matter of time.
[Samsung Galaxy Nexus] thomstrack:
3~4 days with Fancykernel r55 and not noticed lags or low memory in no time . So far everything is running very smooth and fast. :)
[Samsung Galaxy Nexus] aosp:
[MENTION=4615478]boype[/MENTION] any plans to add cpuboost?

https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-11.0/drivers/cpufreq/cpu-boost.c

https://github.com/CyanogenMod/android_kernel_google_msm/commits/cm-11.0/drivers/cpufreq

So we can remove the dated tuna power hal lib power_tuna.so once and for all ?
[Samsung Galaxy Nexus] FredFS456:
Okay, I just had a unprompted reboot about an hour ago (r54). So I'm supposed to post the last_kmsg, right? So I tried to get it again, but still the same error. Even if you only want reports on r55, I want to know how for the future. Here's the procedure:

1. I fire up Terminal Emulator

2.

su

See confirmation in the form of the

root@maguro:/ #

3.

cat /proc/last_kmsg > /sdcard/last_kmsg.txt

from this line, I get:

sh: cat: /proc/last_kmsg: No such file or directory

What am I doing wrong? I have busybox v1.22.1 bionic (dunno whether that's relevant).
[Samsung Galaxy Nexus] freshgiammi:
Guys, it's obvious that you can't get any last_kmsg.

Boype disabled the Android Ram Console to get some more ram (like 3-4mb). This causes no last_kmsg.

[MENTION=4615478]boype[/MENTION] you really shoud revert this commit and the one before. https://github.com/boype/kernel_tuna_kk44/commit/608ffb0d677898c1680f6ef1d8343231e572bb92
[Samsung Galaxy Nexus] boype:
If there's any issue that can't be fixed without it, it would definitely make sense to re-add it, sure. But as long as we talk about the battery percentage not showing up while power-off-charging and we even know what's wrong, I'll leave it disabled.
[Samsung Galaxy Nexus] boype:
pre56_1

Hi, pre56_1 is here (OP) for you to test:

Focus:

trying to increase stability (fix random reboots)

fix battery percentage not showing while phone-off-charging

speed ;)

As for the speed part: I wrote some sioplus fixes. Dunno if they actually boost your phone to warp-speed :p
[Samsung Galaxy Nexus] massoudsh:
+1
[Samsung Galaxy Nexus] pkgnex:
[MENTION=4615478]boype[/MENTION],

The "fix battery % not showing while phone-off-charging" is definitely corrected in pre56_1.

Not that I really cared... but just to confirm on another device...
[Samsung Galaxy Nexus] infectedorganism:
Would someone mind posting the current minfree values? I don't think I'm applying the correct ones via init.d.

Thanks in advance.
[Samsung Galaxy Nexus] osm0sis:
Hey boype!

Just wanted to mention you could do lines 3-4 with the props I set with fscheck. :)

# WA for android 4.3: remount data and cache with proper options
for partition in data cache ; do
line=`$bb grep $partition fstab.tuna`
if $bb echo $line | $bb grep -q "ext4" ; then
$bb mount -o remount,noatime,nosuid,nodev,noauto_da_alloc,nomblk_io_submit /$partition
fi
done

if [ `getprop ro.fs.$partition` == "ext4" ]; then

:good:
[Samsung Galaxy Nexus] creeve4:
12288,15360,18432,21504,24576,30720
[Samsung Galaxy Nexus] Ashtrix:
[MENTION=4615478]boype[/MENTION], I guess the reduction in framebuffer mem from r54 to r55 caused the low performance in games and overall boost, just an idea sorry if i was wrong......tryin r56_1 now..

Thanks :good: !

Edit : First impressions, its faster like r54 :good: but there's this heating up faster overtime(bootup after optimizing many apps, Wifi usage, gaming, charging) similar to r55 and unlike r54. All voltages, clocks same !!
[Samsung Galaxy Nexus] Nelson George:
Touch control

is fancy supports touch control, because i tried touch control, and pgm.....they are not working...

pgm cause random reboots..

one more request,...how to enable slide2wake without touch control app.??

any suggestion
[Samsung Galaxy Nexus] aliesz:
Nope.
[Samsung Galaxy Nexus] morfances:
Fancy Kernel has always supported touch control with the CM11 module on all versions. Personally, I have the touch control v.1.85 and works fine .If you have problems send me PM
[Samsung Galaxy Nexus] Nelson George:
Thanks Again

touch control v.1.85 works fine with fancy kernel,.. but it is not available on play store,.. but i found a copy from devhost.

Thank you again
[Samsung Galaxy Nexus] Thymo:
Hey guys,

Last couple of weeks been having issues with my GPU. Whenever i'm on battery it just crashes. Doesn't happen when i'm on external power (charging/pc) or have my screen off. Might this happen due to the GPU not receiving enough power?

Recently had my USB board replaced.
[Samsung Galaxy Nexus] pattyboi:):
what do you mean "just crashes"
[Samsung Galaxy Nexus] Thymo:
It shows a whole bunch of gibberish on the screen (like the old tv's) for a split second and then i can only turn it back on when it's charging. Otherwise it'll just crash again.
[Samsung Galaxy Nexus] pattyboi:):
Download syslog from the play store,then replicate the issue,once you do go to syslog (after you plug in so the screen is stable) and check only kernel log,then take log,then go to your sdcard and into the syslog folder and copy and past the contents of that file in pastebin.com and link it here
[Samsung Galaxy Nexus] boype:
How exactly do you measure that it's heating up faster? Just a feeling, or do you have a specific benchmark / app you run?

For me, pre56_1 is cooler than all 50+ releases - subjectively, no benchmark.

Fancy does not set minfree values at all - so it's ROM defaults.

Here comes the bash scripting pope ;)

Thanks, I'll change this in the future.

How exactly is power.tuna.so connected to this?

Is there a 3.0 kernel port available somewhere already? I'd like to test this, but lack the time to implement it (given that this still needs some 3.0 kernel adaption).
[Samsung Galaxy Nexus] Thymo:
That's the problem. I've been watching logs for days now but it doesn't show anything of interest.
[Samsung Galaxy Nexus] Ashtrix:
Well after your post i ran everything and the results were alright (sorry for miscalculations :( ), running vaux volatage of 2900 instead of 3100 now but one thing i'm sure of is pre56 runs very fast over the r55 & no freezes .

Thanks for the update !!
[Samsung Galaxy Nexus] aliesz:
Pre_56 runs very good and stable on 4.3 stock ROM, like the other recent anykernel2 versions. Thank you [MENTION=4615478]boype[/MENTION]. :)
[Samsung Galaxy Nexus] pkgnex:
[MENTION=4615478]boype[/MENTION],

Sorry if you've already included these commits, but I thought you should be aware of them if you weren't already:

http://xdaforums.com/showpost.php?p=54970271&postcount=45164
[Samsung Galaxy Nexus] boype:
Included since like forever ;)
[Samsung Galaxy Nexus] pkgnex:
I figured as much! ;)
[Samsung Galaxy Nexus] Ashtrix:
[MENTION=4615478]boype[/MENTION], It's better here with Vaux at 2900 rather than 3100 on pre56, all that heatup and misconception is caused by this, I missed it at first then ran it again (the prev post) on this voltage and results were good .

May i know why did u revert this from r54 "slightly undervolt VAUX3 (display) from 3.1 to 2.9 Volts" on pre56 :confused: ?

Thanks !!
[Samsung Galaxy Nexus] osm0sis:
Haha I never said I was infallible, but you can if you want. :p
[Samsung Galaxy Nexus] motorazrv3:
Just wanted to say pre 56_1 is working without any probs. Damn fast kernel.

THX.
[Samsung Galaxy Nexus] Ashtrix:
Test

After a through observation here are my results pre56 vs r54....this time no mistakes:)

No overheating, Uv'd the Vaux display voltage from 3100 to 2900.

Got a freeze today after a long call with pre56, phone just wont wake up battery pull was needed...

Edit : Antutu v4 results attached.
[Samsung Galaxy Nexus] manolone:
is it of any use the lagfix apk on fancy r54? or the ftrim feature is already included in the kernel or in android kitkat as well?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] büscher:
Does anyone have wifi tethering issues too? The tethering starts but there is no notification (maybe rom related) but the wifi ap gets up and I can see the wifi with my tab. Accessing it works, I can enter the passkey but it wont go behind "authenticating". Tried on r54 and pre56_1...
[Samsung Galaxy Nexus] infectedorganism:
I just tested this and I don't have any of the problems you've described -- everything is working as it should.
[Samsung Galaxy Nexus] pkgnex:
I don't have any issues at all with wifi tethering on any versions of Fancy from r54 to pre56_1.

fstrim is auto-run in kit-kat. It's not kernel-related.

You can still run lagfix (or just run fstrim on the /data and /cache partitions in a terminal emulator yourself), it's just really not necessary anymore.
[Samsung Galaxy Nexus] tostep:
Where can I read that fstrim is auto-run in kit-kat? And why is my phone faster after I fstrim /data and /cache partitions and reboot?
[Samsung Galaxy Nexus] Jar3112:
Of i remember well fstrim included in 4.3+ is automatically run when the phone is idle in charge for more than 1 hr

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] SoftWord:
it's usefull Synapse. It's an hard work to do?
[Samsung Galaxy Nexus] joelmonty:
Anyone got random reboot on r55? I'm on stock 4.3 works great though, but just got a reboot.
[Samsung Galaxy Nexus] Culex316:
I also got a random reboot... Twice.. While my phone was sleeping.

I couldn't grab a last kmesg. I'm running CM11.
[Samsung Galaxy Nexus] FredFS456:
Someone commented some pages back that boype added a patch that increases the RAM at the expense of not being able to grab last_kmsg ever. So I guess no need to try when that's still in. Also, latest theme engine patches are extremely unstable, just so you know.
[Samsung Galaxy Nexus] SoftWord:
For me too theme engine is unstable with some themes

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] boype:
The random reboot issue is acknowledged, I also got a few. I'm currently testing things by myself to get rid of this.
[Samsung Galaxy Nexus] pkgnex:
I think you may have already fixed it with pre56_1. I had one random reboot while on r55, but I haven't had one yet on pre56_1 in several days of usage.
[Samsung Galaxy Nexus] RevengeFNF:
Since 56_1 i did have not any random reboot.
[Samsung Galaxy Nexus] RW-1:
Boype, pre56_1 running fine on shiny ROM, and when plugged in onto the charger after a min, I get the batt percentage thing, which wasn't a dealbreaker for me anyhow (I almost never charge while off, it's on and available hehehe).

I just wonder how much more Boype Juice you can cram into this thing to make it run fantastic!

Are we eventually going to run up against the Boype version of moore's law? :)

Simply Awesome Work!
[Samsung Galaxy Nexus] pkgnex:
I doubt it.

Boype's G-Nex improvements can be described by a "side-ways 8".
[Samsung Galaxy Nexus] siealex:
I got a random SOD at night on pre56-1.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] AquilaDroid:
Under volting?

From my Nexus 5
[Samsung Galaxy Nexus] lparcshinoda:
Is it possible to have back the stock charging animation? Also, 90% of times I get the phone rebooted after boot if using the set-on-boot option of Trickster MOD to change screen colors and brghtness options. Other than these the pre56_1 is GREAT :)
[Samsung Galaxy Nexus] RW-1:
You would have to ask Boype that .... likely not.
[Samsung Galaxy Nexus] qtoo941:
I am still using this version of Fancy R55. It was like fourth version which [MENTION=4544860]osm0sis[/MENTION] compiled with fixed anykernel and fixed usb-otg. And since i flashed it on Cataclysm 4.3 ROM i haven't had a single reboot. It is just rockstable. And i am scared to flash any newer version like pre-r56.
[Samsung Galaxy Nexus] pkgnex:
Wuss.

:p
[Samsung Galaxy Nexus] morfances:
I have bootloop with rom 4.4.4 ..back to r54
[Samsung Galaxy Nexus] siealex:
Today I got a random reboot while backing up my apps with Titanium.
[Samsung Galaxy Nexus] boype:
pre56_2

Hi,

pre56_2 is available from the OP.

Trying to improve stability and speed and stuff ;)
[Samsung Galaxy Nexus] creeve4:
Your latest commits on Github are from August 21. I assume you are building the test versions from your local source. Will you please push the latest commits that are in pre56_1 and _2? I'm slowing learning kernels and like to see your work, thanks!
[Samsung Galaxy Nexus] boype:
I'm obligated to push the sources, so of course I will do that if you wish. In general, I never publish the sources before a major release. That is because I try, change remove, reorder commits quite often with test releases. The result on github would be a big mess and hardly structured.

Also, because of the described testing procedure, the state of pre56_1 cannot be pushed anymore - I already changed, removed and reordered a lot since then.

I might push r56 tonight anyway. Are you okay if I only push that instead?
[Samsung Galaxy Nexus] aliesz:
Is this kernel compatible also with MIUI ROM?
[Samsung Galaxy Nexus] boype:
r56

Here we go:

r55 >> r56

arch/arm/mm: several (cache-, page-)memory improvements and fixes

sioplus iosched: several logic improvements and one important fix (check github if interested in technical details)

lower display brightness by ~6 percent (now that content adaptive brightness is off by default, bright images shine a little too bright for my taste. this change has already been applied in pre56_1 and pre56_2)

several reverts of commits from r55 that might have been reducing stability

ramdisk/anykernel2: fix all types of encryption with Unified v2 (by osm0sis)

Sources are pushed to github, too.

Have a nice Sunday!
[Samsung Galaxy Nexus] RevengeFNF:
I was looking to you Github. You have made 263,691 commits to the kernel since you started. Wow... Thats a lot of commits :good:
[Samsung Galaxy Nexus] boype:
Nononono :D

More than 260k are inherited b from the tuna kernel source
[Samsung Galaxy Nexus] qtoo941:
Flashed r56-AnyKernel2 over Cataclysm and it booted fine without bootloop. Gonna see if it's as stable as r55-anykernel2-osmod (fixed usb-otg). I hope it has at least the same stability. Btw i also tried the last 4.3 JB version of Omni and flashed R56 over it. And guess what - it booted fine and the ROM was very smooth even with stock settings.

I got a question: Would somebody post good settings for OnDemandPlus please. I want to make it more battery friendly so i can sacrifice some perfomance at all. I was big fan of OnDemand governor because this is the most stable governor but in last two weeks i am using OnDemandPlus and i am surpriced.
[Samsung Galaxy Nexus] rjshrjndrn:
For r56 stable and smooth. But for pre56_1 there was a problem of killing background apps aggressively. Hope it's not inherited.
[Samsung Galaxy Nexus] creeve4:
Yes, that is understandable. Thank you
[Samsung Galaxy Nexus] lparcshinoda:
Still facing the same issue: when using Trickster MOD to appy settings after boot, the phone have a reboot. But this ONLY happens when the screen is off during the precise moment when the settings are applied.
[Samsung Galaxy Nexus] siealex:
Switch off Content Adaptive Brightness in Trickster. It's a known hardware bug.

Sent from my paranoid fancy galaxy nexus
[Samsung Galaxy Nexus] lparcshinoda:
Ok, thanks... this wasn't happening with the stock kernel anyway
[Samsung Galaxy Nexus] thomstrack:
Flashed r56 over r55 (wipe cache/dalvik) on Stock Jelly Bean 4.3 and running smooth and fast. :)
[Samsung Galaxy Nexus] 7175:
Great release! Running on my daily driver: Vanir 4.3.1 final. I'm getting some real nice battery life since pre56-02. My screen usage is 70-80% which is damn excellent. Some issues I had with radio connectivity have vanished. That might be from switching back to FA02 radios on my toro though.

Yeah I really like ondemandplus with max frequency set to 1036800. Then I would just leave governor settings default or maybe adjust inter_hifreq to 729600. With 1036800 max, this still feels like 1200000 max for 0ther kernels. Another really good tweak for saving battery is to change vaux3_6030 to 2500(screen voltage). You can use trickster or run this line in the terminal:

echo -e 'VAUX3_6030: 2500 mV\nVMMC: 1800 mV' > /sys/class/misc/customvoltage/regulator_voltages

edit: I only recommend trying this tweak with toro/toroplus phones. The maguro variant has a different screen that runs with a higher voltage, as Siealex pointed out.
[Samsung Galaxy Nexus] Reinvented:
#dedication
[Samsung Galaxy Nexus] qtoo941:
Thank you for this tips (i also clicked thx button! ;d). Would you provide me link for Vanir 4.3.1 for maguro please?
[Samsung Galaxy Nexus] siealex:
It increases the screen brightness three to five times. Do you decrease it manually?
[Samsung Galaxy Nexus] Culex316:
2600 is the absolute limit for setting that voltage without making the screen become brighter.

I have it at 2600 and it's great for saving battery.
[Samsung Galaxy Nexus] 7175:
@ Siealex : Hmm, I guess the screen voltage may be different for maguro. Now that I remember this may just be a tweak you only want to use on toro/toroplus. Sorry, I will edit my post.

Yeah let us know how that vaux3_6030 tweak works out. You might not want to use that with a maguro device now that I think about it.

That Vanir link is hard to find unless you've scoured their site for it. :) Here you go man: http://www.emccann.net/nuclearmistake/VanirAOSPRelease/maguro/vanir_maguro_4.3.1.zip
[Samsung Galaxy Nexus] creeve4:
There is no perceptible screen brightness change between voltages ranging from 2500 to 3100 on my maguro.

A voltage of 2400 does result in a brighter screen. Anyone know why this is?

Who else can provide data?
[Samsung Galaxy Nexus] AgentSmith:
A more economical screen could have a huge impact on total battery time. But since I have a Maguro I'll wait until it's clear whether or not it's a good idea to lower this value.
[Samsung Galaxy Nexus] McDuffSmith:
just flashed on 4.3...

smoothest kernel I've ever used.

if i may request something: Inteliplug. that would be crazy awesome to have in here.

anyway dude, awesome kernel.
[Samsung Galaxy Nexus] Charmacas:
Any sort of hotplug governor does not work well with our device. It just causes problems. That's at least my experience.
[Samsung Galaxy Nexus] McDuffSmith:
in my experience inteliplug isn't bad and saves battery. its also not a governor, its a driver. works with any governor.
[Samsung Galaxy Nexus] santi1993:
Its working well on Cataclysm 4.3?
[Samsung Galaxy Nexus] Culex316:
r56 is running great on my CM11 Galaxy Nexus...no random reboots so far :good:

Great job, [MENTION=4615478]boype[/MENTION]!
[Samsung Galaxy Nexus] Ashtrix:
r56 working great, even on gaming it's cool and fast.

Thanks boype :good: !!
[Samsung Galaxy Nexus] büscher:
I immediately had SODs with r56... Like r55 and the pre56... Back on r54 and all is well. Didnt play with tunables so far. Because of battery pulls and no response on adb while dead I cant provide any logs...
[Samsung Galaxy Nexus] SoftWord:
For me great as usually!
[Samsung Galaxy Nexus] aliesz:
On stock 4.3 it is running very good and smooth.
[Samsung Galaxy Nexus] gautam_nexus:
When applying adblocking from adway on r56 I get a bootloop but its not present in r56 pre 2.
[Samsung Galaxy Nexus] creeve4:
Adaway is working fine for me with r56 and SlimKat
[Samsung Galaxy Nexus] cujo6801:
Same on DirtyUnicorn

Sent from the "DOG" pound
[Samsung Galaxy Nexus] quickdraw86:
r56 is working great for me on 4.3 and 4.4.4 ROMs... Excellent work.
[Samsung Galaxy Nexus] Piti8576:
With r56 my init.d Script doesn't work, no off the parameters is set.

#!/system/bin/sh

# Screen Off Min Freq
echo "384000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "384000" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq

# Headphone Volume Boost
echo 1 > /sys/devices/virtual/misc/soundcontrol/volume_boost

# High Performance Sound
echo 1 > /sys/class/misc/soundcontrol/highperf_enabled

# DTM Skip
echo 1 > /sys/module/bcmdhd/parameters/dtim_skip_override