[Galaxy Note 4 Android Development (Snapdragon)] robertanderson1776:
I did a compare of the build.props for [MENTION=2359141]thebroken[/MENTION] 's ResurrectionRemix Nougat build that I've been using stable on my TRLTETMO N910T for a while, against [MENTION=4251307]micky387[/MENTION] 's LineageOS Oreo build. Here's the differences I see.

Some are of course different because the code is from different projects (RR vs LOS), and other stuff is because the RR build was specific to the N910T. I've omitted the stuff that seemed clearly different to me due to only these two reasons.

Other stuff I'm not certain is different because it should be, or because its an oversight, and if it is an oversight, whether it has any substantive impact on the stability of the build in this thread for LOS Oreo. I might be a Java dev for a living, but this is the first time I've even looked closer at the builds, so I'm very inexperienced in interpreting what's important in this file versus what isn't.

If any of these differences might explain some of the issues with the camera, call audio, bluetooth audio, GPS issues, etc that have been reported by myself or others, let me know. Again I'm not familiar with what these properties are used for, so those that have been doing builds might spot something that jumps out at them as a glaring issue.

Missing in the

LOS Oreo

build.prop file versus the

RR Nougat

build.prop file:

rild.libargs=-d /dev/smd0

telephony.lteOnGsmDevice=1

ro.telephony.default_network=9

dalvik.vm.dex2oat-swap=false

ro.sys.fw.dex2oat_thread_count=4

ro.product.first_api_level=19

persist.audio.fluence.voicecomm=false

persist.audio.ssr.3mic=false

persist.speaker.prot.enable=false

persist.spkr.cal.duration=0

ro.audio.flinger_standbytime_ms=300

ro.config.combined_signal=true

ro.config.media_vol_steps=30

ro.config.vc_call_vol_steps=15

ro.qc.sdk.audio.ssr=false

tunnel.audio.encode=false

bt.max.hfpclient.connections=1

qcom.bluetooth.soc=rome

camera2.portability.force_api=1

sys.hwc.gpu_perf_mode=1

ro.opengles.version=196609

ro.opa.eligible_device=true

ro.nfc.port=I2C

persist.data.netmgrd.qos.enable=true

persist.radio.lte_vrat_report=1

ro.telephony.ril_class=trlteRIL

sys.keymaster.loaded=true

net.tethering.noprovisioning=true

persist.data.iwlan.enable=true

ro.data.large_tcp_window_size=true

ro.disableWifiApFirmwareReload=true

persist.data.iwlan.enable=true

ro.data.large_tcp_window_size=true

ro.disableWifiApFirmwareReload=true

dalvik.vm.heapgrowthlimit=256m

ro.bootimage.build.fingerprint=samsung/lineage_trltetmo/trltetmo:7.1.1/NOF27B/92eb853d73:userdebug/release-keys

Missing in the

RR Nougat build.prop versus the

LOS Oreo

build.prop

ro.opengles.version=196608

persist.data.ds_fmc_app.mode=0

persist.data_netmgrd_nint=16

persist.omh.enabled=1

persist.radio.fill_eons=1

persist.radio.use_se_table_only=1

persist.net.doxlat=true

net.tethering.noprovisioning=true

ro.systemui.burn_in_protection=true

persist.bt.enableAptXHD=true

dalvik.vm.heapgrowthlimit=256m

persist.radio.apm_sim_not_pwdn=1

media.recorder.show_manufacturer_and_model=true

I can't imagine that would cause a bug in an app, so this is probably inconsequential

ro.bionic.ld.warning=1

ro.treble.enabled=false

Things that are different in the LOS Oreo build.props (first) versus the RR Nougat build.props (second):

ro.build.tags=test-keys vs ro.build.tags=release-keys

ro.build.description and ro.build.fingerprint also contain the variation on test-keys versus release.keys... not sure if any app code behaves differently based on these props

audio.offload.buffer.size.kb=32 vs audio.offload.buffer.size.kb=64

ro.sf.lcd_density=560 vs ro.sf.lcd_density=480

dalvik.vm.heapsize=768m vs dalvik.vm.heapsize=512m

dalvik.vm.heapminfree=2m vs dalvik.vm.heapminfree=512k

ro.lineage.releasetype=UNOFFICIAL vs rr.build.type=Unofficial

I suspect these property names are not interchangeable, but they may be unique to the projects themselves, so I'm not sure about these two

dalvik.vm.stack-trace-dir=/data/anr vs dalvik.vm.stack-trace-file=/data/anr/traces.txt

I suspect the first just specifies a dir and allows the caller to use a default filename, while the latter provides an explicit dir and filename, so I think this is inconsequential