Lately I've been going through the Xperia XA2 Ultra kernel (sdm660) and trying to add new features. Today I was adding in some governors, specific to this post, is the interactiveX governor.
That's when I ran into this error:
/home/alaskalinuxuser/aokp_pie/kernel/sony/sdm660/drivers/cpufreq/cpufreq_interactivex.c:239 …
Oh boy! I finally got AOKP to boot up in an Engineering build for the XA2 Ultra (discovery). However, once you get through the setup pages, it crashes at the home screen. Here's the logcat output:
--------- beginning of crash
08-21 04:12:30.094 3050 3050 E AndroidRuntime: FATAL EXCEPTION …
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 …
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 …
Another strange set of errors while compiling AOKP. It seems like they are in the middle of merging some Lineage commits, but didn't finish them. Either way, I ran into this problem with Ext3Crypt:
compile system.com/vold/Ext4Crypt.cpp:204:12: error: use of undeclared identifier 'fs_mgr_is_wrapped_key_supported'
So, I …
Well, that was a new one to me! I had just build LineageOS and Resurrection Remix for the XA2 Ultra, and now I got this error in the first minute of trying to build AOKP. Here's the full error:
vendor/qcom/opensource/audio/policy_hal/AudioPolicyManager.cpp:2240:65: error: member …
And it wasn't, well, once I learned how to do it properly. Unfortunately it took me an hour to get there! First I monkeyed around with vmware-tools, and vmware-mount, and then I tried kpartx, and all of it was a wash.
Then, after more searching online, I found a guy …
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 …
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 …
[gallery ids="4330,4331,4332,4333,4335,4336,4337,4338" type="rectangular" orderby="rand"]
To God be the glory, I finally finished a XA2 Ultra build of Resurrection Remix! It's Resurrection Remix, Pie flavored! You can check it out on XDA if you would like, but here is my post …