Database Develop

Script To Enable Voice Navigation in Google Maps for Cyanogen ROM's

Google Maps Voice Navigation was much simpler to set up on a Cyanogen ROM then reading the thread made it seem, so I made a script that follows the same process I did, and though it should work, I have not tested it, so please let me know if it needs any fixes. It will back-up any necessary files to the sdcard, so there are no real worries in giving it a try.
1. Download Google Voice from the market
2. Unzip the file, and make sure the two files, build.trout.prop, and mapsnav.sh are on the root of the sdcard.
3. Open the terminal and enter
Code:
su
sh sdcard/mapsnav.sh
This will do its work then reboot the phone. When it is back up, you should be set.

Doesn't seem to work for me. Upon running the script, I got a few errors ("Google not found," "Cannot locate dalvik-cache on sd," etc.; the phone rebooted before I could get a look at all of them). After the reboot, I still had the same old Maps. I tried installing the APK provided in the zip, which seemed to be a successful install, but still, no navigate feature.

jay652 said:
Doesn't seem to work for me. Upon running the script, I got a few errors ("Google not found," "Cannot locate dalvik-cache on sd," etc.; the phone rebooted before I could get a look at all of them). After the reboot, I still had the same old Maps. I tried installing the APK provided in the zip, which seemed to be a successful install, but still, no navigate feature.
Click to expand...
Click to collapse
Are you using a Cyanogen ROM, with apps2sd?

cloverdale said:
Are you using a Cyanogen ROM, with apps2sd?
Click to expand...
Click to collapse
Yupp, 4.2.3.1, or whatever the second-latest one is.

The problem is that your dalvik-cache and maps folders seem to be somewhere other than on my phone. If you first clear your dalvik cache, find the maps folder in /data/data/, and erase it, then run the script, it should work. I will figure this out and post when I get off of work.

I got the "no google found" error.
Also on boot up im missing gmaps all together.
edit: i also forgot to mention while the script was running scoreboard and mixzing forceclosed.. and on boot up advanced launcher foreclosed about 5 times.

[Script] droidNavi
Try this to have the DROID maps w/Navi correctly installed.
Download the droidNavi.zip file
1: place DroidMaps folder on the root of your /sdcard
2: go into terminal
3: su
4: sh /sdcard/DroidMaps/naviScript.sh
and let it do its thing, also you must reboot once the script is done

ravenjr said:
Try this to have the DROID maps w/Navi correctly installed.
Download the droidNavi.zip file
1: place DroidMaps folder on the root of your /sdcard
2: go into terminal
3: su
4: sh /sdcard/DroidMaps/naviScript.sh
and let it do its thing, also you must reboot once the script is done
Click to expand...
Click to collapse
Will this work got the Magic too or just the Dream?

works for me thanks alot, i was hoping someone would make a script.... it did tell me google not found but it works =)

ravenjr said:
Try this to have the DROID maps w/Navi correctly installed.
Download the droidNavi.zip file
1: place DroidMaps folder on the root of your /sdcard
2: go into terminal
3: su
4: sh /sdcard/DroidMaps/naviScript.sh
and let it do its thing, also you must reboot once the script is done
Click to expand...
Click to collapse
i did this. Everything seems to have worked out fine... but i get forceclose upon opening navigate
got it to work. I had to install the speechsynth stuff from the settings.

Works great thx.

ravenjr said:
Try this to have the DROID maps w/Navi correctly installed.
Download the droidNavi.zip file
1: place DroidMaps folder on the root of your /sdcard
2: go into terminal
3: su
4: sh /sdcard/DroidMaps/naviScript.sh
and let it do its thing, also you must reboot once the script is done
Click to expand...
Click to collapse
This worked great! only problem is Google Voice doesn't work afterward. It force closed at first, then I reinstalled it, now it just will not download messages and will not call out.

almus said:
This worked great! only problem is Google Voice doesn't work afterward. It force closed at first, then I reinstalled it, now it just will not download messages and will not call out.
Click to expand...
Click to collapse
did you set it back up after the reinstall?

almus said:
This worked great! only problem is Google Voice doesn't work afterward. It force closed at first, then I reinstalled it, now it just will not download messages and will not call out.
Click to expand...
Click to collapse
I am having the exact same problem. This has happened to me before, and this fixed it at the time. But the solution does not apply here... anyone else with Google Voice problems?
--- fixed! ---
ok in debug mode I see these:
11-13 23:35:17.845: ERROR/GoogleVoice(2939): Unable to prepare post-Donut Contact API
11-13 23:35:17.845: ERROR/GoogleVoice(2939): java.lang.ClassNotFoundException: android.provider.ContactsContract$Contacts
...
Click to expand...
Click to collapse
I tried messing around with swapping out the contacts but gave up for now. I've replaced my build.prop and build.trout.prop files with the backed up ones and GV is working again. I've read that some people have seen the navigation menu disappear when they do this - it doesn't sound likely, but I'll be watching out for that for the next few days I guess.
So - go back to your prop files and GV and GM will both work, at least for now.

fixed! (I think)
hmm how do I delete a dupe post?

[MOD] PRL Write Enabler for Sprint Galaxy S4 [MDC][MDL][MJA]

First off this work is based on Digiblur's PRL Write Enabler from the Sprint Galaxy S3 forum. I simply modified it & packaged it for our Sprint Galaxy S4 devices.
Here is the original S3 post that this was found in... http://forum.xda-developers.com/showthread.php?t=2159054
Also, post #8 below provides additional info.
I tested it by flashing with TWRP and it worked on my stock, rooted S4 with the MDC and MDL releases.
If you're on a stock rooted Rom and not using TWRP, you can just copy the HiddenMenu.apk from inside the zip file downloaded into /system/app/ and overwrite the one that's there. (You'll need a root enabled file browser to do this of course).
Thanks to Unknownforce here is a version for MJA...
http://www.androidfilehost.com/?fid=23212708291676468
Enjoy!!

This certainly will save me from having to use CDMA WS to switch like I just did yesterday. 55014 was not working well for me in my market so I switched back to 25014.

What is write enabler?

Keeps aborting for me

THEGAMEPLAY94 said:
Keeps aborting for me
Click to expand...
Click to collapse
You mean the install of the zip?
If so, you can pull the APK out of the zip and replace HiddenMenu.apk in the system folder (make a backup first). You may want to also set the permissions to rw-r-r after replacing the system app. Reboot, then you should be good to go.

@ChadH42,
I know it seems like I'm harping on you but I'm really not..
You need to update the OP on - 1. What is this? 2. What does this do? 3. Why is this in the Development Section.. ?
A good OP leads to less questions.. Development Sections aren't for information. That would be considered a Discussion Thread that belongs in General.
Let's keep the Dev section clean from the start.
My suggestion - Edit the OP on the What's/Why's?/How To's and you won't get posts like mine.

To the OP, updated your title as [WIP], and I suggest you provided additional information so that folks aren't bricking their new devices.
I will check in, if you need anything, let me know.

What this MOD does (in case the OP takes a little while to chime in)
What this MOD does is modifies our ##DATA# (select View) menu to allow for the PRL Write option to appear and function. With this menu option, the user can change their PRL on the fly from the device itself by placing a copy of the desired PRL in the root directory of Internal Storage and name it "test.prl" (no quotes), dial ##DATA# (choose View), tap Write PRL, tap the sub-menu option Write PRL ---wait--- and then the device reboots with the test.prl PRL applied upon reboot. Not every PRL works and sometimes it takes a couple of tries.
A tip for multiple PRL options is to, of course, keep a folder of the PRLs you like and keep them labeled in there. Copy the desired PRL to proper place as needed and just remember to rename the copy to "test.prl". Switch back and forth as you please. I hope this helps clear some confusion and helps some find purpose with the MOD like I have.
For a clear set of instructions that I did not want to just copy verbatim, check the link below. Also, if you are having issues with the zip not installing in CWM, just extract the APK from the ZIP (inside the system/app folder), use Root Explorer or your favorite root-access file explorer to place the APK in the APP folder, apply the proper permissions and reboot.
Ref from the GS3: http://forum.xda-developers.com/showthread.php?t=1748516

So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2

jayjay7411 said:
So I unzipped the file, replaced the hidden menu original apk with the new one, then set permissions, rebooted, then tried ##3282# and the view and edit options do not appear.. .. It just blanks out the items I just entered
Sent from my SPH-L720 using Tapatalk 2
Click to expand...
Click to collapse
Did you clear Cache when you rebooted?
What ROM are you using?

ChadH42 said:
Did you clear Cache when you rebooted?
What ROM are you using?
Click to expand...
Click to collapse
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.

lilmikeyv said:
+1...same thing is happenening to me...Im on force rom. when i type in the dialer code it just blanks out.
Click to expand...
Click to collapse
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.

O okay. Its currently not a necessary thing for me at the moment, just nice for when I travel to Alabama. Hopefully later on someone gets it working on deodex.
Sent from my Nexus 4 using Tapatalk 2

ChadH42 said:
I just tried this mod with the Force ROM and it did the same thing (blank options). The only thing I can think of is that it works with the odex version of the stock ROM so maybe its a problem with deodex ROMs of which Force is one.
Click to expand...
Click to collapse
I am actually running it on the Rooted Stock DeOdexed ROM. So I don't think it is an Odex/DeOdex issue...might be a Force ROM issue.
Also, moot point for Force ROM (1.0+) anyway because the PRL Write mod is already included with that.

I'm also having this problem and I'm pretty sure it was working this morning. I haven't flashed anything since then.
edit-- I tried:
1. wiping both cache's
2. killing background process "OIThiddenmenu"
neither fixed it.

I reinstalled the stock odex ROM and flashed this again and it worked.

Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.

Unknownforce said:
Just an FYI, OP, I get Error Status 6 when trying to flash this via recovery, which indicates one of two things. Either the format of the file is incorrect or there is a syntax error. The syntax looks fine, but opening in basic Notepad shouldn't "look pretty" like it currently does. So it's likely it was edited with a non-Unix-compatible text editor like Notepad or MS-Word...
To make modifications to an updater-script (or just about any Android/Linux files like this) you need something like Notepad++ or gVim.
Anyways, I did a quick test with this, and it does in fact not work on my ROM as it is, but I see why it's failing, but I don't know what exactly it's trying to reference yet. (It fails with an id number instead of a name, so I'll have to de-compile some things to find it.)
I'm not sure it's a ROM issue or a MOD issue yet. (meaning it might have to be updated for each custom ROM, depending on how they are configured) But I'll track it down and update when I can.
Click to expand...
Click to collapse
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.

ChadH42 said:
Thanks for all your help here..
I had the error status 6 problem in the beginning and thought I fixed it. You are correct that I used MS WordPad to edit the files.
Click to expand...
Click to collapse
I think TWRP can read the non Unix type characters, which is why it works on a different recovery.
I'm hoping it's a mod issue and I can just modify the mod to work universally regardless of the rom. But we'll see.
Sent from my SPH-L720 using xda app-developers app

fails in recovery for me.
says error executing updater binary in zip
in stock rooted...

Google Dialer with caller ID and contacts

This is a repost from the Moto X Pure section. LINK
Follow the instructions to backup and then flash the AOSP dialer and contacts in TWRP. This worked perfectly for me on my Turbo.

Works great. Thanks!

I'm considering flashing this. Then I got to looking at these apps in the play store. Of course it shows that they're incompatible with all my devices, but my question is to ask if after flashing this, has anyone tried updating to the updated apps that are in the Play Store? Of course if I don't get a response in the next few minutes, I'll probably give it a shot anyway. After a nandroid, naturally.

I was able to get the contacts to install and initiated, and the dialer installed, according to Aroma, but for some reason, it wouldn't initiate. I suspect it's something to do with it being CM. I recall that CM somehow broke the dialer compatibility, back in either 10 or 11...
Sent from my DROID Turbo via Tapatalk. Now with that cyanogenmod goodness.

The original write up didn't pan out for me. I renamed the stock dialer and contacts, extracted the ones from the .zip and put them in the folder where dialer and contacts were. System>priv-apps>Dialer/Contacts. I then rebooted and they seem to be working, time will tell. There doesn't appear to be the oft desired Call Blocking. I think that's only on the newer versions, Marshmallow only. The newest versions of these apps that are on the Play Store won't work either, as they're MM only.

Wynnded said:
The original write up didn't pan out for me. I renamed the stock dialer and contacts, extracted the ones from the .zip and put them in the folder where dialer and contacts were. System>priv-apps>Dialer/Contacts. I then rebooted and they seem to be working, time will tell. There doesn't appear to be the oft desired Call Blocking. I think that's only on the newer versions, Marshmallow only. The newest versions of these apps that are on the Play Store won't work either, as they're MM only.
Click to expand...
Click to collapse
I did the same thing. On CF's 1.2.5 odex ROM, renamed the existing dialer.apk and contacts.apk, flashed the zip, and it worked.

GeoFX said:
I did the same thing. On CF's 1.2.5 odex ROM, renamed the existing dialer.apk and contacts.apk, flashed the zip, and it worked.
Click to expand...
Click to collapse
Flashing the .zip wasn't panning out for me. When I did it that way, I didn't have a dialing app. I could go to contacts and initiate a call from there, and it would ring through, but there wasn't an interface for the ongoing call. I couldn't close the line. I removed the .apks from the .zip and placed them in the appropriate folders then rebooted. Really only had one incoming call, yesterday, and it was fine. I don't think that we have video call though, not that I've ever used it, but I didn't notice the icon for it.

Can somebody help me out? I'm trying to figure out the difference between the 5.1 stock contacts and the Google contacts zipped with the Google dialer in the OP. I'm comparing the 2 side by side on my phone and I swear I cant find a difference. I know the Google dialer has differences I am specifically asking about the contacts app. Thanks.

koftheworld said:
This is a repost from the Moto X Pure section. LINK
Follow the instructions to backup and then flash the AOSP dialer and contacts in TWRP. This worked perfectly for me on my Turbo.
Click to expand...
Click to collapse
couldn't get this to work on my droid. i tried the OP way by deleting the folders and letting the flash repopulate them, but the problem is that the zip's folders aren't 'contacts' and 'dialer', but rather 'googlecontacts' and 'googledialer'. i tried to flash and then to rename the contacts and dialer apks, and replace them with the new ones, but i still didn't have a dialer to speak of on my phone after reboot.
anyone find another way that works? i would really love to have this dialer...

I renamed the .apks inside of the Contact and Dialer folders to .bak, then flashed this file.
By the way, I believe that these Google .apks have been updated, but I don't have a clue how to make a flashable .zip. Anyone want to have a go at it?

Wynnded said:
I renamed the .apks inside of the Contact and Dialer folders to .bak, then flashed this file.
Click to expand...
Click to collapse
this is where my hangup is. the folder structure in my system is priv-apps>dialer>dialer.apk; in the flashable zip it's priv-apps>googledialer>dialer.apk
whether or not i rename the original file or delete it entirely, the new dialer apk just isn't routing to the same directory. guess i'll have to be patient and keep on with what i have...

midnitemass said:
this is where my hangup is. the folder structure in my system is priv-apps>dialer>dialer.apk; in the flashable zip it's priv-apps>googledialer>dialer.apk
whether or not i rename the original file or delete it entirely, the new dialer apk just isn't routing to the same directory. guess i'll have to be patient and keep on with what i have...
Click to expand...
Click to collapse
Odd, in the flashable .zip, and as installed, mine drills down as: priv-app>GoogleDialer>GoogleDialer.apk. The structure is the same when I drill down into the .zip file that I keep because I have to rename and flash it again after ROM updates. I can't help you beyond that. Beyond my abilities.

If you are running CM 13, download the latest version of gapps stock from open gapps project. You will have Google Dialer. They have white listed our device"quark" as compatible.
Once flashed make sure that you set the app as default in your app settings.
Sent from my DROID Turbo using XDA-Developers mobile app

During call, wifi icon disappears

During call, wifi icon disappears. Why? Very irritating. It's not a bug, since me and the wife both have a 3T and I have re-flashed mine multiple times in its life span, and that has always irritated me. I often need to make sure I'm on wifi during a long conference call for work. See screenshots. Any ideas?

I also forgot to mention the battery percentage goes away too, which is also handy during a long call.

The culprit is the OnePlus' incall app - you can remove it, but you have to be rooted, unfortunately.

przemcio510 said:
The culprit is the OnePlus' incall app - you can remove it, but you have to be rooted, unfortunately.
Click to expand...
Click to collapse
I am rooted. How do you remove the "incall app"?

izzyfanto said:
I am rooted. How do you remove the "incall app"?
Click to expand...
Click to collapse
Code:
adb shell
su
mount -o remount,rw /system
mv /system/priv-app/OPInCallUI/OPInCallUI.apk /system/priv-app/OPInCallUI/OPInCallUI.apk.bak
reboot
or by navigating to that folder and renaming it with adding .bak extension (or something else) with your favorite file manager

przemcio510 said:
Code:
adb shell
su
mount -o remount,rw /system
mv /system/priv-app/OPInCallUI/OPInCallUI.apk /system/priv-app/OPInCallUI/OPInCallUI.apk.bak
reboot
or by navigating to that folder and renaming it with adding .bak extension (or something else) with your favorite file manager
Click to expand...
Click to collapse
Thanks for the reply. But when I rename it, nothing appears when I'm in call. It rings, but nothing shows. I don't understand how that fixes anything if I can't even use the call menu. Am I missing a step? I had to put it back the way it was.

izzyfanto said:
Thanks for the reply. But when I rename it, nothing appears when I'm in call. It rings, but nothing shows. I don't understand how that fixes anything if I can't even use the call menu. Am I missing a step? I had to put it back the way it was.
Click to expand...
Click to collapse
Replace it with another app

izzyfanto said:
Thanks for the reply. But when I rename it, nothing appears when I'm in call. It rings, but nothing shows. I don't understand how that fixes anything if I can't even use the call menu. Am I missing a step? I had to put it back the way it was.
Click to expand...
Click to collapse
Consider flashing Google dialer - https://forum.xda-developers.com/oneplus-3/how-to/guide-how-to-install-google-dialer-phone-t3443006
With this combo - no problem here.

bunu said:
Replace it with another app
Click to expand...
Click to collapse
przemcio510 said:
Consider flashing Google dialer - https://forum.xda-developers.com/oneplus-3/how-to/guide-how-to-install-google-dialer-phone-t3443006
With this combo - no problem here.
Click to expand...
Click to collapse
Ah gotcha, makes sense. Does the google dialer support dual sim? I use one for personal and one for work. How buggy is it?

izzyfanto said:
Ah gotcha, makes sense. Does the google dialer support dual sim? I use one for personal and one for work. How buggy is it?
Click to expand...
Click to collapse
Supports dual sim, no bugs.

przemcio510 said:
Supports dual sim, no bugs.
Click to expand...
Click to collapse
Sweet. Thank you very much for your help!!

I tried it but I don't see the dual sim for selecting which to use for calling out. Am I missing something?

izzyfanto said:
I tried it but I don't see the dual sim for selecting which to use for calling out. Am I missing something?
Click to expand...
Click to collapse
In system settings, change "default sim for calls" to "always ask".

Hmm strange I had that enabled when I had the module installed. The dialer didn't even show the option to switch sims though. Unfortunately I just had to remove the module through magisk. I use the second sim for business so really need the ability to decide which sim to call from during the day. Thanks for your help

izzyfanto said:
Hmm strange I had that enabled when I had the module installed. The dialer didn't even show the option to switch sims though. Unfortunately I just had to remove the module through magisk. I use the second sim for business so really need the ability to decide which sim to call from during the day. Thanks for your help
Click to expand...
Click to collapse
I don't know what module you installed, I linked you to the zip with Google Dialer framework, I didn't say anything about Magisk.
I'm on AOSP based ROM with GApps atm, so I don't have to flash framework anymore, but when I was on OOS 3.5.4, then after flashing framework and installing Dialer apk from apkmirror, everything worked flawlessly.
Maybe try to do it again - reflash your ROM, flash dialer framework, remove opincallui, install Google Dialer app, set as default, set default sim for calls to always ask.
The choice of which sim to use when calling pops up after dialing a number. The dialer has no buttons for each sim separated.
If you don't want to use Google's dialer, then you can use OnePlus' one. IIRC, after removing opincallui, it still worked.

przemcio510 said:
I don't know what module you installed, I linked you to the zip with Google Dialer framework, I didn't say anything about Magisk.
I'm on AOSP based ROM with GApps atm, so I don't have to flash framework anymore, but when I was on OOS 3.5.4, then after flashing framework and installing Dialer apk from apkmirror, everything worked flawlessly.
Maybe try to do it again - reflash your ROM, flash dialer framework, remove opincallui, install Google Dialer app, set as default, set default sim for calls to always ask.
The choice of which sim to use when calling pops up after dialing a number. The dialer has no buttons for each sim separated.
If you don't want to use Google's dialer, then you can use OnePlus' one. IIRC, after removing opincallui, it still worked.
Click to expand...
Click to collapse
Oh ok thanks for the pointers I really appreciate it. I'll have to give it a try again

Dailer recording EU version

Hi,
I ordered the phone yesterday and am excited to have it, it I keep wondering if this one has call recording. Please let me know, because I need this!
Thanks

joefso said:
Hi,
I ordered the phone yesterday and am excited to have it, it I keep wondering if this one has call recording. Please let me know, because I need this!
Thanks
Click to expand...
Click to collapse
It doesn't have (got my phone last Monday)

joefso said:
Hi,
I ordered the phone yesterday and am excited to have it, it I keep wondering if this one has call recording. Please let me know, because I need this!
Thanks
Click to expand...
Click to collapse
You can't record calls in Europe as it is illegal,maybe try changing region to India or somewhere where it is legal.There are apps out there too

manus31 said:
You can't record calls in Europe as it is illegal,maybe try changing region to India or somewhere where it is legal.There are apps out there too
Click to expand...
Click to collapse
Thanks.for.your reply!
No it depends.on which country you are in. Some countries it is not allowed.
I thought coloros had call recording inbuild

valthunder said:
It doesn't have (got my phone last Monday)
Click to expand...
Click to collapse
Does it have Google Dailer?
Does this option not exists? http://www.gadgetdetail.com/coloros-6-how-to-setup-call-recording/
Could you plz check?
Thnx

Call recording is not present in EU ROM. But I'm pretty sure that it will be there as soon as custom stock ROM is out as I think it's simply a property to enable in some file (needs root).

In case you're still searching, there's a solution for rooted EU roms; I tested it successfully:
See https://forum.xda-developers.com/showpost.php?p=81431741&postcount=4

joefso said:
Does it have Google Dailer?
Does this option not exists? http://www.gadgetdetail.com/coloros-6-how-to-setup-call-recording/
Could you plz check?
Thnx
Click to expand...
Click to collapse
It doesn't have Google Dialer. And you can't install it unless you're rooted, because there is no Google Dialer Framework installed. If you are rooted, there is a magisk module that installs Google Dialer Framework, and after that you can install google dialer (but that doesn't have call recording).

cyexdeah said:
In case you're still searching, there's a solution for rooted EU roms; I tested it successfully:
See https://forum.xda-developers.com/showpost.php?p=81431741&postcount=4
Click to expand...
Click to collapse
How did you do that? I followed the whole procedure, but I still can't have call recording.
Maybe I missed something, or I'm not checking in the right place to activate it.
Can you please help me?

asusgarb said:
How did you do that? I followed the whole procedure, but I still can't have call recording.
Maybe I missed something, or I'm not checking in the right place to activate it.
Can you please help me?
Click to expand...
Click to collapse
I just followed the instructions. If you're rooted, just go to /system/etc/oppoRegionMarkFeatures/ in your file manager. You should see a bunch .xml files with country codes, which apparently turn on/off certain features, but for call recording they're probably not relevant. I copied com.oppo.region mark.EUEX.xml first somewhere safe and opened it with an editor. There's a line that says feature name="oppo.phone.nodisplayrecord". I deleted the line, saved and rebooted. This activates the hidden option. Then go to settings, search for "call recording". You should see "System Apps > Call > Call recording" Activate the option "record all calls" (or "record unknown numbers"), call some number. You should see a green "recording standby" icon in the call wait screen and text changes automatically once it starts recording. Recordings are listed in the "Recorder" app. Voila. Ping me later and I can post the screenshots of the settings screens.
HTH

I am using this https://nllapps.com/apps/acr/ and it works. It just has one bummer and that it doesn't save the number of the person you called. So, you have to assign it after a call.

andrejd1 said:
I am using this https://nllapps.com/apps/acr/ and it works. It just has one bummer and that it doesn't save the number of the person you called. So, you have to assign it after a call.
Click to expand...
Click to collapse
It doesnt work for me. Im EU ROM.

anfederin said:
It doesnt work for me. Im EU ROM.
Click to expand...
Click to collapse
My device is EU rom too. In the settings, I have selected an automatic source of the recording and format is MP3.

andrejd1 said:
My device is EU rom too. In the settings, I have selected an automatic source of the recording and format is MP3.
Click to expand...
Click to collapse
Can you please show it as a screenshot?

Here you go.

andrejd1 said:
My device is EU rom too. In the settings, I have selected an automatic source of the recording and format is MP3.
Click to expand...
Click to collapse
The APK works, bur It records the interlocutor voice at very low level.

anfederin said:
The APK works, bur It records the interlocutor voice at very low level.
Click to expand...
Click to collapse
Yes, it's not perfect but better than nothing, I guess...

cyexdeah said:
I just followed the instructions. If you're rooted, just go to /system/etc/oppoRegionMarkFeatures/ in your file manager. You should see a bunch .xml files with country codes, which apparently turn on/off certain features, but for call recording they're probably not relevant. I copied com.oppo.region mark.EUEX.xml first somewhere safe and opened it with an editor. There's a line that says feature name="oppo.phone.nodisplayrecord". I deleted the line, saved and rebooted. This activates the hidden option. Then go to settings, search for "call recording". You should see "System Apps > Call > Call recording" Activate the option "record all calls" (or "record unknown numbers"), call some number. You should see a green "recording standby" icon in the call wait screen and text changes automatically once it starts recording. Recordings are listed in the "Recorder" app. Voila. Ping me later and I can post the screenshots of the settings screens.
HTH
Click to expand...
Click to collapse
But didn't you replaced the original one with the edited one?
I did it (with TWRP File Manager).
Did you only edited it, without replacing it?
What I did is:
1. Copy the EUEX XML to "internal memory".
2. Edit the copied file removing the whole line (from < to >) and without leaving the blank line.
3. Reboot to TWRP.
4. From TWRP File Manager copy the edited file to origin folder, overwriting the stock XML).
5. Reboot to OS.
As you can see in the screenshot, no more "nodisplayrecord" line and no blank line before "blacklist"line.
Sent from my Realme RMX1931 using XDA Labs

asusgarb said:
But didn't you replaced the original one with the edited one?
I did it (with TWRP File Manager).
Did you only edited it, without replacing it?
What I did is:
1. Copy the EUEX XML to "internal memory".
2. Edit the copied file removing the whole line (from < to >) and without leaving the blank line.
3. Reboot to TWRP.
4. From TWRP File Manager copy the edited file to origin folder, overwriting the stock XML).
5. Reboot to OS.
As you can see in the screenshot, no more "nodisplayrecord" line and no blank line before "blacklist"line.
Click to expand...
Click to collapse
Sent from my Realme RMX1931 using XDA Labs

asusgarb said:
Did you only edited it, without replacing it?
Click to expand...
Click to collapse
Yes. I browsed to the directory and edited the XML file directly using my file manager (I use X-plore but any rooted app should also do).
The copy I made was not for offline-editing purposes, it's a habitual backup just in case
Try editing the file directly. If it doesn't work, you might wanna check if the line is in the other XML files in the same folder. Maybe there is a country-specific XML file.
ps: I'm on 11_A.08, EU version.