AlaskaLinuxUser's Scratchpad

Commit thy works unto the LORD, and thy thoughts shall be established. - Proverbs 16:3

system/bt/stack/btu/btu_hcif.cc:729:22: error: no member named 'BLUETOOTH_CLASSIC_PAIRING_EVENT_REPORTED' in namespace 'android::util'

Several Bluetooth issues were really giving me the run around while trying to compile AOKP for the Xperia XA2 Ultra. Let's take a look:

system/bt/stack/btu/btu_hcif.cc:729:22: error: no member named 'BLUETOOTH_CLASSIC_PAIRING_EVENT_REPORTED' in namespace 'android::util'
android::util::BLUETOOTH_CLASSIC_PAIRING_EVENT_REPORTED, "", handle,
\~\~\~\~\~\~\~\~\~\~\~\~\~\~~^
system/bt/stack/btu/btu_hcif …

error: vendor/qcom/opensource/cryptfs_hw/Android.bp:27:37: unrecognized property "product_variables.lineage.uses_metadata_as_fde_key"

Another random error while compiling AOKP pie for the XA2 Ultra. These calls work properly when compiling Lineage, but don't work in the AOKP source tree, so I did some digging.

error: vendor/qcom/opensource/cryptfs_hw/Android.bp:27:37: unrecognized property "product_variables.lineage.uses_metadata_as_fde_key"

In the end, I found …

E Zygote : java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist

whitelist

More dreaded whitelist errors! Essentially, an app is trying to do something it should not be allowed to do. You can see the logs here:

E Zygote : java.lang.IllegalStateException: Signature|privileged permissions not in privapp-permissions whitelist: {com.android.systemui: android.permission.NAVIGATION_EDITOR, org.omnirom.omnistyle: android.permission.CHANGE_OVERLAY_PACKAGES, com …

Finding the real errors in your Android logcat...

So, you built a rom, and something went wrong. It's stuck at the boot logo, or it does boot up, but doesn't do "xyz" action, or it crashes right after you get to the home screen. You've played this game before, you pull logs, and all you can see is …

Engineering Pie Build for the Sony Xperia XA2 Ultra!

[gallery ids="4302,4301" type="rectangular"]

So it's been a rough start for me, stepping into the modern world with a modern phone that has a/b partitioning and was Android 8.0+. I've built dozens of roms for dozens of phones, some that were even unsupported, and to God …