[LG V30 Guides, News, & Discussion] Septfox:
As part of a minor project I'm halfheartedly working on and probably won't finish, I've been having a gander through some of the XMLs in lge-res.apk from 20s/Oreo. bool.xml contains true/false settings, since that's...what a boolean value is. They control configurable system defaults and enable/disable some features in the ROM.

This isn't intended to be one of those "LOOK GUYS ALL THESE FEATURES WE COULD ENABLE", just a bit of a fun. Most of the ones set to false probably aren't actually attached to anything and would be disregarded if changed, or the feature they control is buggy/incomplete/unusable.

Some notable entries:

<bool name="config_powerLight_available">false</bool>

No hardware lights for you.

This is probably referring to some proprietary thing elsewhere in an LG ROM (note the "an", not necessarily THIS one), not actual lights, as googling it reveals nothing.

<bool name="config_enable_aod_widget">false</bool>

<bool name="config_enable_signboard_widget">false</bool>

AOD and SignBoard are the same thing.

Makes me wonder if a custom widget option was considered and scrapped, or this simply disables the controls and music widgets by default.

<bool name="not_true">false</bool>

GOOD.

<bool name="config_lg_safe_media_volume_enabled">true</bool>

"Everyone hated that."

<bool name="config_quick_memo_hotkey_customizing">false</bool>

Oooh.

<bool name="config_is_using_embedded_battery">true</bool>

Annnnd that was the first nail in the coffin.

<bool name="config_chameleon_supported">false</bool>

Cloaking is factory-disabled so you don't lose your phone.

<bool name="config_userConfigLedBrightness">false</bool>

<bool name="config_hasBackLed">false</bool>

<bool name="config_hasColorBackLed">false</bool>

Remember when phones had notification lights and screen backlights, guys?

Pepperidge Farm remembers.

<bool name="config_lge_safe_media_volume_enabled">true</bool>

:v

<bool name="config_lcd_oled">true</bool>

And if you ignore the black crush that happens under ~32 brightness along with the inconsistent grey levels on most panels, it's pretty good.

<bool name="config_knock_off_available">false</bool>

Yet...it is.

<bool name="config_two_phone">false</bool>

Confirmed: phone is one phone.

I wonder if this is for dual-SIM and set elsewhere.

<bool name="config_shaking_gesture">false</bool>

I miss my Turbo/Maxx's flashlight/camera gestures.

<bool name="config_support_smartpouch">false</bool>

Canceled accessory, I suppose.

<bool name="config_hasOneColorLed">false</bool>

In every way. *sigh*

<bool name="config_improveLCDWhiteSpot">false</bool>

You get your white spots in their natural unenhanced state.

<bool name="config_smart_battery">false</bool>

Too bad, it would have been a worthy inclusion if it's what I'm thinking of.

(A.i.X. includes a system app to limit the maximum battery charge, to prolong battery lifetime, and I personally use an Automate flow to do the same)

<bool name="config_image_quality_enhancement">false</bool>

Oh :\

<bool name="config_main_aod_enabled">false</bool>

<bool name="config_main_aod_mipi_enabled">false</bool>

<bool name="config_poled_aod_enabled">true</bool>

unfh POLED hype

<bool name="config_model_joan">true</bool>

Well now I'm curious what happens if this is set to false.

<bool name="config_notch_display_enabled">false</bool>

Fond memories of when LG was one of the holdouts before giving up and adopting all the Apple/Samscum garbage fads. I guess they did hang onto the headphone jack to the bitter end, so there's that...

<bool name="config_rearside_volume_key">false</bool>

<bool name="config_rearside_power_key">true</bool>

Having extensively messed about with my mother's old HDX 8.9" Amazon tablet, I can say that rear-facing volume buttons are one of the most annoying damn things.

<bool name="config_support_RFRPE_AOL">true</bool>

I haven't the faintest idea what this is, and google has no idea either, but...good...?

<bool name="config_use_lg_multi_alc">true</bool>

Because why use AOSP autobrightness, when you can instead use a homebrew system presumably based loosely on something inferior your phones used way back in the day, that's an annoying pain in the ass for the user to look at/use and has no user-facing adjustability by default?

<bool name="config_use_roundcorner_mask">false</bool>

Remember when this set the bar for the stupidest thing LG was starting to do on their phones? Golly, we were all so innocent back then. They certainly didn't waste much time making us all realize that there're *always* poorer decisions for them to make.

<bool name="config_enableWaterproof">false</bool>

I guess technically it's not.

<bool name="config_support_blank_surface">true</bool>

Helpful!

(graphics subsystem stuff, I think)

<bool name="config_glove_mode_enabled">false</bool>

This actually does something if set to true via a system settings app: on Samsung phones, where it can be a useful tweak.

Unfortunately our firmware, digitizer, or both don't support it, so enabling it does nothing on the v30.

<bool name="config_power_volumedown_reset">true</bool>

It's interesting that the sole method of forcibly restarting the phone (aside from draining the battery or disassembling it to remove the battery) is technically optional.

<bool name="config_touchscreen_turn_on_button_light">false</bool>

I fondly remember actual buttons under the screen on the phone "chin", then later "physical" dedicated digitizer buttons, and the button backlight that came with both...but will readily admit to liking immersive mode+gestures more. Easier to customize, smoother to use, more space for actual screen.

Sure do miss hardware QWERTY, though.

<bool name="config_support_forced_poweroff">false</bool>

Vol-/Power button combo is a low-level LG firmware thing, soooo I assume this refers to holding down the power button alone to trigger...whatever it is that holding the power button down triggers in non-LG phones.

<bool name="config_scaleYCoordinateOfMotionEventInSecondScreen">false</bool>
<bool name="config_transferMotionEventToStatusBar">false</bool>

Probably would have been interesting to play with on handsets with a second screen e.g. v20.

<bool name="config_enable_exceptionalLed">false</bool>

:(

<bool name="config_support_secret_mode">false</bool>

And it'll continue being a secret to everyone.

<bool name="config_quick_memo_hotkey_long_enable">false</bool>

More "would have been a worthy inclusion" stuff. Seriously, how - as a company hoping to succeed - do you look at competition like Samscum and their fixed-function button that everyone hates, and go "yea lets do the exact same thing with our shortcuts, users hate customization"?

<bool name="config_support_abs">true</bool>

Phone has Antilock Brakes.

<bool name="config_use_screen_auto_brightness_adjustment">true</bool>

Oh? And where would that be, LG?

(you can set the mix/max limits for autobrightness with root access, but as far as I know there's only one relevant system setting for ALC and it does nothing for LG's implementation)

(aforementioned mix/max settings are in /sys/module/mdss_fb/parameters/ fyi; I strongly recommend setting backlight_min to 35+ to prevent low enough brightness to crush blacks out)

<bool name="config_battery_swap_feature_enabled">false</bool>

Would have been cool.

<bool name="config_enable_suggestion_card">true</bool>

Say "Ok Google, I have a suggestion for LG", and one of those suggestion/opinion/'how was your experience' cards spits out the top of the phone. Try it!

That's all I found particularly notable or amusing. XML in its entirety follows.

Spoiler content hidden.