yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Bresch:
just downloaded aokp_maguro_jb-mr1_milestone-2 which is 4.2.1 I believe.

But as far as I can tell in the OP there is no milestone for 4.2.x? or am I missing something?

Thanks for an awesome kernel!
[Samsung Galaxy Nexus] blipp:
Theres no milestone but the latest nightlies are still stable and worth using.
[Samsung Galaxy Nexus] franciscofranco:
r390:

* Start fresh from 4.3 Kernel sources

* Merge everything that was worth merging from all the previous work

* Works on all roms, including CyanogenMod

4.2 support is dropped, so don't bother asking if r390 works something else than 4.3.

Have fun!
[Samsung Galaxy Nexus] MaLiXs:
Thx to you to bring your knowledge to our devices

Send from my CM-Franco-osm0ded GNex
[Samsung Galaxy Nexus] thegtfusion:
HEHEHEHEHEHE (can't control my excitement :D :D :D )

Sent from my Nexus Prime

---------- Post added at 12:30 AM ---------- Previous post was at 12:22 AM ----------

I noticed that I can't toggle fsync anymore? (Doesnt matter, but is it hardcoded now?)

Sent from my Nexus Prime
[Samsung Galaxy Nexus] franciscofranco:
Ups forgot to add fsync :D
[Samsung Galaxy Nexus] thegtfusion:
Hahaha no problem, but it is on now right? By far the smoothest experience on 4.3 man! :D :D

Sent from my Nexus Prime
[Samsung Galaxy Nexus] Edward Stanbury:
i also noticed that there are no set values for the governor settings under fk.u and no high performance wifi and fsync as mentioned before haha apart from that mate this update is smooth as hell ! thanks for your hard work bro :P
[Samsung Galaxy Nexus] phamdt8:
just tried r390 but PGM doesn't work. using cataclysm rom.
[Samsung Galaxy Nexus] Kurre:
Loading modules in 4.3 is disabled. Franco probably didn't change that.

Sent from my SlimBeaned GNex
[Samsung Galaxy Nexus] kuyam:
Cleared the app, but I'm still seeing strange numbers at the voltage control.
[Samsung Galaxy Nexus] convolution:
thanks for the kernel!
[Samsung Galaxy Nexus] Prasad:
Based off of AOSP?

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] abalam:
Works in CyanogenMod!!!!!! You mean JSS15J. You the man Franco!!! Thought I had to miss this fantastic kernel. Keep up the GOOD work:thumbup::thumbup:
[Samsung Galaxy Nexus] nemotheblue:
No milestone for your own MiNCO users?
[Samsung Galaxy Nexus] cmstlist:
First glance I'm noticing no row scheduler. Yet to be added?

Thanks again!
[Samsung Galaxy Nexus] Edward Stanbury:
I'm using row as we speak on r390
[Samsung Galaxy Nexus] dehein:
Just flashed it but i cant use titanium backup to restore my apps? Why

Gesendet von meinem Galaxy Nexus mit Tapatalk 4
[Samsung Galaxy Nexus] elia222:
Change backup folder in titanium backup's preferences from 0 to legacy.
[Samsung Galaxy Nexus] cmstlist:
... then I have no idea why I am not seeing the same option.

Weird. On first reboot row did not appear. But two hours later without a reboot, row is now in the list.
[Samsung Galaxy Nexus] schukje:
Is minco updated to 4.3 yet? If so can you direct me to it?

grtz from crazy bastard from Holland
[Samsung Galaxy Nexus] Edward Stanbury:
Haha the mystery of android I guess ;)
[Samsung Galaxy Nexus] inihccor:
I'll flash it on stock 4.3. Will this kernel increase the volume?

Inviato dal mio Galaxy Nexus usando Tapatalk 4
[Samsung Galaxy Nexus] Prasad:
It will increase volume if you configure it as such in trickster mod or f.ku

Sent from the inner sanctum of my mind.
[Samsung Galaxy Nexus] sui785:
Lost root after flashing this kernel, not sure if it's rom/kernel related because I read on G+ that some kernels(AKSP/Golden kernel) doesn't make you lose root. Anyway fixed it with flashing SuperSU 1.51. Am running PA 3.92 preview.
[Samsung Galaxy Nexus] safendi:
Franco can you add the governor hyper in your kernel?
[Samsung Galaxy Nexus] nemotheblue:
Nope, still V7 based on 4.2. That's why I asked about a milestone. I understand the nightlies from now on will only be for 4.3
[Samsung Galaxy Nexus] Jerreth:
Is this kernel compatible with the new nexus 7 2013 model? I was reading about this being compatible with 4.3 devices but wanted to be model specific rather than just jump in.
[Samsung Galaxy Nexus] The Gingerbread Man:
Kernels are device specific, flashing this on your new tablet will make it not boot up into android and you I'll have to fastboot flash the Google factory image to fix it.
[Samsung Galaxy Nexus] Jerreth:
thank you that's what I thought. cant wait until Francisco gets a new n7 to work with.
[Samsung Galaxy Nexus] thegtfusion:
franco's interactive is the best you can get :D
[Samsung Galaxy Nexus] franciscofranco:
Well I haven't made a single change on interactive on r390. I will only add input_boost_freq, the rest is pretty much working fine as far as I can see.
[Samsung Galaxy Nexus] Astug:
CFQ was the default I/O scheduler for me after flashing r390. Any particular reason or is deadline still preferred?
[Samsung Galaxy Nexus] dracon6ai:
Running like a champ Frano (r390). Thanks a ton
[Samsung Galaxy Nexus] franciscofranco:
No specific reason, I just left it as Google ship. CFQ tuned runs as fine as any other IO scheduler.
[Samsung Galaxy Nexus] djlah:
is r390 support USB-OTG ?
[Samsung Galaxy Nexus] Edward Stanbury:
ROM related mate I had a quick scan of the PA thread and meany other users said the same thing :P
[Samsung Galaxy Nexus] designori:
r390 is flawless and awesome. i admire franco. and now i am waiting for osm0sis!
[Samsung Galaxy Nexus] franciscofranco:
Yeah I think I can pretty much release a Mlestone soon, this thing is more than stable.
[Samsung Galaxy Nexus] :
sry 4 this question but does this kernel has an own ramdisk or anykernel?

Nexus Prime Powered by Rasbean & Trinity
[Samsung Galaxy Nexus] mikiept:
Olá Francisco!

You did not include BFQ in r390 for some particular reason?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] thegtfusion:
Own ramdisk

Sent from my Nexus Prime
[Samsung Galaxy Nexus] heartbeat.rulez:
is this important?

Gesendet von meinem Galaxy Nexus mit Tapatalk 4
[Samsung Galaxy Nexus] creeve4:
[MENTION=4544860]osm0sis[/MENTION]

Are these parts of your init script included in the 384-osmod? If so, where?

# wait for systemui, increase its priority and make it unkillable
while sleep 1; do
if [ `pidof com.android.systemui` ]; then
systemui=`$bb pidof com.android.systemui`;
busybox renice -18 $systemui;
echo -17 > /proc/$systemui/oom_adj;
chmod 100 /proc/$systemui/oom_adj;
exit;
fi;
done&

# lmk whitelist for common launchers and increase launcher priority
list="com.android.launcher org.adw.launcher org.adwfreak.launcher com.anddoes.launcher com.android.lmt com.chrislacy.actionlauncher.pro com.cyanogenmod.trebuchet com.gau.go.launcherex com.miui.mihome2 com.mobint.hololauncher com.mobint.hololauncher.hd com.qihoo360.launcher com.teslacoilsw.launcher com.tsf.shell org.zeam";
while sleep 60; do
for class in $list; do
if [ `pgrep $class` ]; then
launcher=`$bb pgrep $class`;
echo -17 > /proc/$launcher/oom_adj;
chmod 100 /proc/$launcher/oom_adj;
busybox renice -18 $launcher;
fi;
done;
exit;
done&
[Samsung Galaxy Nexus] osm0sis:
I'm seeing some weird **** with r390.. :(

192MHz causing instant freezes at complete kernel defaults (f.Ku reset + reboot, and no init.d scripts running).

Setting MPU voltages in f.Ku jumps by 50mV instead of 25mV and when you tap out to save it may or may not be what you entered. Also, more of a f.Ku note, we're missing CORE and IVA as of the recent update and it would be great to have them back. :)

I notice you've put all the root method stuff in another .rc file, which was a great idea, but I'm not sure you've got them all correct, SuperSU should have it as --auto-daemon and we decided core root root critical would be good here. And the daemonsu call should be at the top so it's dominant over any other calls to su in the case they're all SuperSU.

I've also got those mount option tweaks for init.rc and fkbootscript.sh updates I worked out for the JB4.3 hybrid. Want me to mod your r390 ramdisk and send it your way? :good:
[Samsung Galaxy Nexus] bigknowz:
Bad timing?

Can confirm init.d quirks, some things hit (colors, scheduler) and others didn't (min/max frequencies). I also went into terminal and did a run-parts, same result.

As far as 192 freeze, I'll keep you posted, running that now.
[Samsung Galaxy Nexus] osm0sis:
Yeah, I seemed to be able to run 192MHz okay when I was setting voltages with my init.d script, but complete defaults gave me an instant freeze+reboot when I switched to it. I'm wondering if there's something funky going on with the voltage interface or stock hardcoded voltages that might cause this.

Also, thanks for remidning me: Interactive doesn't seem to allow us to change the tunables currently. :)
[Samsung Galaxy Nexus] Edward Stanbury:
+1 exact same thing happens here but for now the init.d scrips are saving my but haha ahh well still able to enjoy the goodness !
[Samsung Galaxy Nexus] smileyanz:
Been using franko's from day one. R390 working great here riding something explosive, also on jellybro, mind you I haven't tweaked much. I'll try a few more tweeks lol but I'm not clued up like some of u guys!! Thanks franko!!!!
[Samsung Galaxy Nexus] G-DannY:
r390 on 4.3 factory image, 1305mhz-192mhz, 729mhz max screen off, interactive/cfq, -50mv on all voltages, perfectly smooth and 0 reboots or freeze.
[Samsung Galaxy Nexus] SahilC:
I'm considering trying MinCo when v8 comes out ;)
[Samsung Galaxy Nexus] :
How is your battery doing?

Thanks

Nexus Prime Powered by Rasbean & Trinity
[Samsung Galaxy Nexus] G-DannY:
at least as good as the same settings on Cyanogenmod 10.1 and r384 that I was using before ;)

But with slightly more smoothness, especially in "over time" steady performance.
[Samsung Galaxy Nexus] bigknowz:
Scipt derp

It seems like more than an init.d issue. I have scripts that run on headset plug in/out. Not all settings took on headset in

#!/system/bin/sh
# 29-Jul-2013

# crank up when headset plugged in
# min max cpu depends on kernel
if cat /proc/version | grep tiny
then
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
echo 920000 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

elif cat /proc/version | grep franco
then
echo 1228800 > /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
echo 1036800 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq

elif cat /proc/version | grep fancy
then
echo 1228800 > /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
echo 1036800 > /sys/devices/system/cpu/cpufreq/interactive/hispeed_freq
fi

echo "12134,15175,18216,21273,24314,30382" > /sys/module/lowmemorykiller/parameters/minfree

Took: hispeed_freq, minfree

Failed: screen_off_max_freq

So its the same issue for me as with init.d, can't change cpufreq. My intereactive tunables did take on init.d.
[Samsung Galaxy Nexus] The Gingerbread Man:
I had something weird earlier I wanna see if you guys can reproduce it. Go to terminal, enter

Su

Killall servicemanager

Device should hot reboot. For me when I unlocked the screen again it just hot rebooted again and I did this about 4 times in a row, then I powered off and powered back up and it booted fine and ran as normal. Stock 4.3 rom, Franco 390, nexus louder patch flashed, su 1.51 and latest busybox
[Samsung Galaxy Nexus] :
yes same here, if I set min to 192 and reboot Trickster will crash and phone will reboot. Tried 4 times and always crash and reboot. This only happen if min is set to 192. If its higher no problem
[Samsung Galaxy Nexus] kboomdj:
How can I put this Kernel with 4.3 factory image? I need CWM or by GNEX Toolkit I can do this?

Sorry for the questions, I'm a begginer.. :rolleyes:

Oh, and sorry for the bad english too!
[Samsung Galaxy Nexus] The Gingerbread Man:
You can flash it with a custom recovery or using Franco's app or using an app called flashify after you have updated to a 4.3 rom
[Samsung Galaxy Nexus] kboomdj:
I don't rooted my phone, just unlocked the bootloader. Need to be rooted to flash by an app?
[Samsung Galaxy Nexus] The Gingerbread Man:
Yup you need to root to flash by an app. Find chainfires thread and flash supersu 1.51 through a custom recovery and that's all you need to do to root 4.3 roms.
[Samsung Galaxy Nexus] creeve4:
[MENTION=4544860]osm0sis[/MENTION] ?
[Samsung Galaxy Nexus] osm0sis:
Bro, my post immediately following that answered you indirectly.
[Samsung Galaxy Nexus] creeve4:
fkbootscript.sh

I missed that, it was at the very end of your post and quite indirect.
[Samsung Galaxy Nexus] osm0sis:
You're indirectly welcome. ;)
[Samsung Galaxy Nexus] hotrodwinston:
Ok weird things to report - using 390 on Jellybro cm10.2 0805 I had no problems with 192 freezing that has been reported - just updated (dirty flash) to 0807 and when setting minimum to 192 locked as soon as I pressed apply in trickster - then rebooted as I was removing my case to pull battery.
[Samsung Galaxy Nexus] marcocsh:
Hey Franco! Will you add PGM support?
[Samsung Galaxy Nexus] AndyGnex:
Isnt it supposed to be the other way around?

Sent from my bathroom throne.
[Samsung Galaxy Nexus] parkson:
Ability to load modules must be enabled in kernel
[Samsung Galaxy Nexus] AndyGnex:
:) i honestly seriously didnt know. That previous question wasnt rhetorical or sarcastic in any way, hope no one gets offended. Never used pgm nor have i ever bothered to check it out. Peace :D

Sent from my bathroom throne.
[Samsung Galaxy Nexus] osm0sis:
4.3 breaks module loading.
[Samsung Galaxy Nexus] shawnaye:
Boype just posted a test kernel with working PGM support.
[Samsung Galaxy Nexus] bbernardini:
Just curious...anybody know what the differences are, if any, between r390 and the Franco kernel included in Paranoid Android 3.95? I've been using Fancy Kernel since I switched from AOKP to PA, but I'm willing to switch back if the PA folks think highly enough of Franco's work to include it in their ROM.
[Samsung Galaxy Nexus] osm0sis:
The PA one is like "f.K Lite" - exposed interfaces for tweaking and latest patches to keep it competitive as a "stock" kernel. Definitely recommend going for the real deal franco.Kernel here. :)
[Samsung Galaxy Nexus] boype:
It is not broken, it has just been disabled by Google on purpose
[Samsung Galaxy Nexus] osm0sis:
Seeing some differences vs. stock tuna kernel:

charger, init, sepolicy (different binaries)

file_contexts:

many additions and deletions

property_contexts:

r390 "bluetooth." and "persist.service.bdroid." lines removed

seapp_contexts:

r390 "untrusted_app" line changed "levelFrom=none" to "levelFrom=app"

r390 "seinfo=google" line added

fstab.goldfish, init.goldfish.rc, ueventd.goldfish.rc (added)

I've reconciled the fstab.tuna, init.rc and init.tuna.rc differences so far, and I assume the binaries are just the newer versions from AOSP, but I'm not sure what to do about this context file bull****. Also the goldfish files don't exist in the stock ramdisk anymore starting with JB4.3, so not sure if we want/need those either.

I noticed there were some TCP buffer tweaks in init.rc over stock defaults as well, but left those mostly alone.

Edit: Merged the file_contexts versions, and went with the newer or larger contexts version for the others since their changes were only one-way. I'm reading that goldfish is just for emulator crap, so I'll leave it be as well.

Edit 2: Good news! I fixed the crash setting the min to 192, and being able to set the governor tunables. :D A bit more testing and I'll put it up and email to Francisco.

I think the voltage issue is more with f.Ku now as editing them individually jumps by 50 instead of 25 and crashes since I think it's getting the number wrong; it all still works fine from the sysfs. Hopefully [MENTION=3292224]franciscofranco[/MENTION] can fix the arrows and also let us tap on the number to edit it on the line as well. We also still need IVA and CORE back in f.Ku.
[Samsung Galaxy Nexus] osm0sis:
http://d-h.st/users/osm0sis/jb4_3/
[Samsung Galaxy Nexus] The Gingerbread Man:
Os I think it would be cool if you know how to change the kernel version label under settings/about phone/kernel version and show the build time stamp, that's if you have the know how :)
[Samsung Galaxy Nexus] shreddintyres:
Hey os after flashing the tcp settings are unavailable

Fku says it's related to busybody issues, did you make any changes to busybox?

Reinstalling busybox with stericson's busybox installer Fku returns to working form
[Samsung Galaxy Nexus] bigknowz:
echo permission denied

Was playing around with screen_off_max_freq in terminal and received Permission denied error. I have a headset script that lowers and raises depending on whether it is plugged in. Do I have to move the location of my script from sdcard to some root directory like xbin? If so, do i need to edit my permission file in init.d to

mount -o rw,remount /system
chmod -R 777 /system/etc/init.d
chmod -R 777 /system/xbin
mount -o ro,remount /system

?
[Samsung Galaxy Nexus] osm0sis:
Nah, it shows up in /proc/version and /proc/sys/kernel/version but you can't change it. It's baked into the kernel zImage itself. Otherwise I would have slapped an "osmod" on there long ago. ;)

Works fine here. If you're using stericson's Busybox app, it just recently added an option that disables the kernel's included ramdisk busybox (by deleting it after every boot). Disable that stupid setting and reboot.

Should work fine from wherever. No need to change perms. If you're root and you invoke the script with sh pretty much anything should work.

sh /system/etc/init.d/00script
[Samsung Galaxy Nexus] bigknowz:
Output from terminal

root@toro:/system/xbin # sh headsetout.sh

Linux version 3.0.89-4.3-fancy_kernel-r37-ext (boype@nerdbox) (gcc version 4.7 (GCC) ) #1 SMP PREEMPT Wed Aug 7 15:56:09 CEST 2013

headsetout.sh[19]: can't create /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq: Permission denied

root@toro:/system/xbin #
[Samsung Galaxy Nexus] osm0sis:
If you're not using my r390-fixed then why would you expect it to work and/or expect me to be able to do something about it? :rolleyes:

Literally zero problems here.
[Samsung Galaxy Nexus] Astug:
I cleared the f.K. app data, flashed your fixed version, went back into the app and set the minimum CPU freq. to 192, my phone instantly froze, black screen and rebooted. This happened on stock JWR66V.
[Samsung Galaxy Nexus] hotrodwinston:
same with me img flash thru flashify on jellybro cm10.2.

Tried zip and works great - maybe uploaded wrong img?
[Samsung Galaxy Nexus] osm0sis:
Impossible. I dragged the img into the zip in order to make it.. My money is it's still some voltage bull**** from f.Ku. :confused:

Try my emergency reset zip?
[Samsung Galaxy Nexus] wasdf:
Just one question, are franco going to add a wifi fix like the Facny Kernel? Here is the workgroud (Actually I don't know what is the fix for, I don't have any problem with my wifi but is there any user experiencing such wifi problem? Just a recommendation..)

http://xdaforums.com/showpost.php?p=42882499&postcount=10
[Samsung Galaxy Nexus] Astug:
There was no need. The phone booted up just fine, with the defaults that is. I tried it again just now, set it to 192MHz and so far so good. Really strange.

EDIT: Or did you mean I should try flashing the emergency reset zip and see if something happens if I set it to 192MHz again?
[Samsung Galaxy Nexus] osm0sis:
Yeah, I think it just needed the defaults. If anyone else has that problem, try my emergency reset zip then see if it still happens.
[Samsung Galaxy Nexus] Astug:
Alright, I'll try that. I'll report back tomorrow, sleep tight all.

EDIT: Haha, I couldn't wait untill the morning. But I just flashed the emergency reset zip, rebooted, booted back into recovery, wiped cache & dalvik cache, flashed your fixed version and set it to 192 and again, instant freeze, blackscreen, hot reboot. Something is not right here.
[Samsung Galaxy Nexus] AutomaticFailure27:
What is the setting to disable in Stericson's busybox? I looked, what seems everywhere, and can't find an option. Is this only a 4.3 issue or would this affect the 4.2.2 kernel as well?

Have you tried turning it off and on again?
[Samsung Galaxy Nexus] osm0sis:
Every kernel with a busybox in the ramdisk. Swipe all the way to the right to get to the Settings, then it's the top option, pretty clearly labeled.
[Samsung Galaxy Nexus] AutomaticFailure27:
So, I'm guessing the top two options that show "applet: [ and [["

Just uncheck those from the install and all should be fine?

Have you tried turning it off and on again?
[Samsung Galaxy Nexus] osm0sis:
The other right. :p

Swipe to the left to get all the way to the right.

About 192, yeah, I'm not sure what's up there. Like I said, it was happening to me before with the original r390. Something weird about the voltage interface or hardcoded voltages is still my only guess. Not sure why it works fine for me now where it didn't before..

---------- Post added at 01:46 AM ---------- Previous post was at 01:01 AM ----------

... I think SmartReflex is enabled again. That might explain some of this ****.

Try disabling all SR and see if that fixes the freezes with 192 please:

#!/system/bin/sh
# chmod -R 755 /system/etc/init.d

echo 0 > /sys/kernel/debug/smartreflex/sr_mpu/autocomp;
echo 0 > /sys/kernel/debug/smartreflex/sr_iva/autocomp;
echo 0 > /sys/kernel/debug/smartreflex/sr_core/autocomp;
[Samsung Galaxy Nexus] cmstlist:
I'm not seeing this in Busybox Free. The rightmost panel is just an About page. Is this only a feature in non-free Stericson Busybox?
[Samsung Galaxy Nexus] AutomaticFailure27:
Yeah, I knew it was going to sound stupid once I posted it. I am on the free version and the only tabs I have are Applets, Install Busybox, and About Busybox.

Also, OT, How did you manage to set up your signature? I really need to read before I post stupid questions.
[Samsung Galaxy Nexus] The Gingerbread Man:
Same here, also using the free version
[Samsung Galaxy Nexus] nahrizulashraf:
I haven't been on franco for quite some time. Does this mean the latest kernel 390 wont be compatible with other than 4.3 roms?
[Samsung Galaxy Nexus] shreddintyres:
please read the op, clearly answers your question ie r390+ is ONLY for 4.3 it has a different ram disk and im assuming many other things under the hood that make it incompatible with <4.3

Cheers
[Samsung Galaxy Nexus] nahrizulashraf:
I've read the op, just need confirmation. Thank you.
[Samsung Galaxy Nexus] Brett3rThanU:
Just installed PA 3.94 which came with Franco 3.0.89. I also purchased Franco Kernel Updater to adjust color settings and adjust frequency. However, when I try to save my color settings it appears to save, but when I go to "Load" I don't see any saved settings. Also, every time I change the max frequency it reverts back to 1228MHz after I leave the app. Any idea what's going on?
[Samsung Galaxy Nexus] SahilC:
Can someone tell me where to get 4.2.2 versions? Either the official ones, or Os'. I'm fine either way ;)

Checked the OP, no sign of it.
[Samsung Galaxy Nexus] adeklipse:
From franco's FTP:

http://minooch.com/franciscofranco/GalaxyNexus/JB/JB-4.2.2/zips/
[Samsung Galaxy Nexus] osm0sis:
Ahhhh haha the option is in Pro.. Hadn't occurred to me that it wouldn't be in free. I wonder if it's still doing it under the hood..

If you haven't already found it, bbcode for my sig is linked in my odds and ends thread. :)

The last 4.2.2 (r384) is on http://minooch.com/franciscofranco as always, and r384-osmod is on my Dev-Host, http://v.ht/osm0sis or http://v.ht/osmod as always. :good:

---------- Post added at 01:54 PM ---------- Previous post was at 01:35 PM ----------

Anyone else try this yet? I was actually getting SODs with my custom voltages until I disabled SR manually. I think it may be the root of most of the r390 problems since everything else lately (eg. lower default hardcoded voltage) has been built on it being disabled like it's been in recent memory all the way to r384.