I tested some modules and other plugins etc. nothing worked, until I tried to follow the steps mentioned in this thread (I use AOSP Dialer, ArrowOS Vanilla nad Nikgapps Core): https://forum.xda-developers.com/t/how-to-enable-native-call-recorder.3996233/I just want to pick up this issue one more time.
I searched the web a little, and there is at least one patch solution (haven't tried that until now).
But as far as I got it, LineageOS implemented the "recording per country" option first time in LOS 15.
I'm pretty sure that I had an official LOS 16.0 on my BQ Aquaris X Pro before its display died (R.I.P. ), and that I found a Magisk module that enabled the call recording button on the dialer - and it worked very well (although it was only stated to work with LOS 14 & 15, as far as I remember)!
Anyway, I wanted to test it, but I'm not able to find it anbymore.
Does anyone know that module as well (and have it still availiable somewhere), and if so, is it working for the ArrowOS on Poco X3?
Before the root there are no problems with banking applications. After the root I only had to hide Magisk from the settings and the banking applications did not detect it. The safetynet test with or without root, it always passes the test.I have 2 questions for this thread:
1) On the original post there is stated no magisk is need but I would assume your banking apps etc would still recognize your phone as rooted? Which I didn't try because I instantly flashed magisk after first boot. I used the GAPPS version for this.
2) Is there something I can do about a kernel panic seems to be caused by a fatal error on modem. Modem subsystem failure reason seems to be LTE (something about my carrier service)? Maybe a de-sync between wifi and 4G?
Anyway it causes my phone to reboot some time more severe than other times. This is an anoying occurance.
Thanks in advance.View attachment 5278813
Before the root there are no problems with banking applications. After the root I only had to hide Magisk from the settings and the banking applications did not detect it. The safetynet test with or without root, it always passes the test.
What test did you run from the terminal?, to try it in mine and give you my resul
I solved it by putting the call dialer that comes installed as the default application, not I had it like this so why I use a call blockerThe code " *#*#4636#*#* " does not work. Previously it worked without any problem. Right now I am on the latest build.
Is this how it's supposed to be?
The OrangeFox referred to in that post is outdated. Get the latest version.Well I have to do a clean flash after force uninstalling Android Auto (mistake) and want to make sure I do it right. I have these instructions from the first time I flashed Arrow:
View attachment 5281379
Is this still the right method for a clean flash? Its different because with my last phone I had to do an advanced wipe on the phone and format data before installed the ROM.
Fixed in version twrp-3.5.2_10-4-suryaI'm getting the error:
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))
Updater process ended with ERROR: 1
Error installing zip file
Please can someone help! Tried formatting data multiple times
I'm yet in the process of figuring it out. I'm completely caught off-guard by this weird issue all of a sudden as there has been literally no changes been made to the device sources nor the rom source so at this point i'm not sure what's even causing it. I've also decompiled the twrp and went through its contents but everything looks fine and dandy in there.Ganesh, since you're here, any information on the TWRP encryption issue after the June 9 build?
1) Download and install latest fastboot ROM which is based on Android 11 (MIUI V188.8.131.52.RJGEUXM Stable Official Update forI was on the latest global MIUI and tried to install Arrow, but got a bootloop to orange recovery.
I followed all the steps, so I'm at a loss for what happened. Orange fox says something about encryption, but the main page of the rom mentions nothing about that for flashing it from stock MIUI.
I reflashed it stock, unlocked bootloader again, installed the TWRP mentioned in the first post.
Then installed latest Arrow GAPPS with it, formated data.
It installed fine, but the ROM wasn't working. System crashing all the time during config.
That is because you do not have the 4pda account. That is why it shows that error.
Wtf are talking about, who said I was on MIUI vendor, I was very clear in my post that I was on the first OSS version before updating to latest ArrowOS.Neither morals nor stories, i have installed all OTA updates automatically through recovery, except when the developer decided to migrate to OSS Vendor. The installation problems or errors are not due to recovery. They are the fault of users who do not read the recommendations. The migration process has already been discussed for several pages. I don't understand why there are still users stupid to upgrade from a MIUI provider build to the new OSS provider build, simply wanting to update the recovery .zip, when this would mean data loss without having made a copy of security, and then they come here with their irony to complain or cry that they have lost their information
To everyone, please STOP this misconception about having the need to flash magisk in order to pass safety net. Do read the OP I've clearly mentioned there's no need of a magisk or modules for safety net. Device is certified and passes safety net out of the box without need of any modifications.Mission Impossible in all custom ROMs !
1. Safetynet check the bootloader status and will automatically fail if magisk is not installed (Magisk Hide ON must be applied for this) !
2. Furthermore, now you have to install the safetynet-fix module to make your banking apps working !
3. Finally, you must hide Magisk Manager.apk with a random name too (Magisk Settings)
I'm aware of the notification led issue, its interlinked to an sepolicy denial from vendor which is quite tricky to address it while we're using the prebuilt/stock vendor. For now you can assume it as a trade off for enforcing builds. I'm working on a fix, once we start a full transition towards an OSS vendor these issues will be more convenient to be addressed.Even dev says in dec the 3rd changelog that notification led was implemented, it still doesn't work for me