Related
Hey,
I'm wondering if anybody can help me figure out why I'm still getting Google Now On Tap when I long-press my home button... My Details:
Phone: 32 Gb Nexus 6P (Rooted)
Android Version: 8.0.0 (OPR5.170623.007, Oct 2017)
Google App Version: 7.13.22.21.arm64
Not sure what other info to include here, but if there's something else that could be effecting this, let me know and I'll provide the info.
Thanks for any help!
FlyOnTheWall43 said:
Hey,
I'm wondering if anybody can help me figure out why I'm still getting Google Now On Tap when I long-press my home button... My Details:
Phone: 32 Gb Nexus 6P (Rooted)
Android Version: 8.0.0 (OPR5.170623.007, Oct 2017)
Google App Version: 7.13.22.21.arm64
Not sure what other info to include here, but if there's something else that could be effecting this, let me know and I'll provide the info.
Thanks for any help!
Click to expand...
Click to collapse
Was it working before and then stopped? Did you recently update your phone? Do you have Google Launcher installed? Language still set to English(US)? Try going through this.
v12xke said:
Was it working before and then stopped? Did you recently update your phone?
Click to expand...
Click to collapse
I'm not 100% sure... I did a clean flash when the 8.0 September image was released and then dirty flashed October on top of it... I didn't think to look between, sorry.
v12xke said:
Do you have Google Launcher installed? Language still set to English(US)?
Click to expand...
Click to collapse
Yes and Yes
v12xke said:
Try going through this.
Click to expand...
Click to collapse
I seem to qualify according to this site, but still no GA.
Just done the October security patch update on mine and Google Assistant and long home press to launch is still working fine.
Try going in and switching off google assistant and then turning it back on may help.
400ixl said:
Just done the October security patch update on mine and Google Assistant and long home press to launch is still working fine.
Try going in and switching off google assistant and then turning it back on may help.
Click to expand...
Click to collapse
How do you do that? Sorry to ask such a basic question, but the only way I know how to do that is through Google Now settings, and the menu item that I'm thinking should be there ('Google Assistant') isn't.
FlyOnTheWall43 said:
How do you do that? Sorry to ask such a basic question, but the only way I know how to do that is through Google Now settings, and the menu item that I'm thinking should be there ('Google Assistant') isn't.
Click to expand...
Click to collapse
It's in the link I sent you.
Settings - Google - Search - Phone
Well hidden
v12xke said:
It's in the link I sent you.
Click to expand...
Click to collapse
400ixl said:
Settings - Google - Search - Phone
Well hidden
Click to expand...
Click to collapse
That's why I referenced that in my reply.... when I go there, it takes me to the same menu as the Google Now settings menu, and there's no "Phone" or "Google Assistant" options.
Opps missed out a step
Settings - Google - Search - Settings - Phone
I am exactly the same build number and security patch version and it is showing there for me.
FlyOnTheWall43 said:
That's why I referenced that in my reply.... when I go there, it takes me to the same menu as the Google Now settings menu, and there's no "Phone" or "Google Assistant" options.
Click to expand...
Click to collapse
So your menu doesn't start with Google Assistant at the top, with Settings directly below? What is at the very top of your Google Now Settings?
v12xke said:
So your menu doesn't start with Google Assistant at the top, with Settings directly below? What is at the very top of your Google Now Settings?
Click to expand...
Click to collapse
Nope... mine goes straight to the "Search" heading... there is no "Google Assistant" Heading...
FlyOnTheWall43 said:
Nope... mine goes straight to the "Search" heading... there is no "Google Assistant" Heading...
Click to expand...
Click to collapse
Hmm. OP said stock Oreo on N6P, but you are running custom fonts and your ROM is for a tablet? Somehow I think you left something out, yeah?
v12xke said:
Hmm. OP said stock Oreo on N6P
Click to expand...
Click to collapse
Please note "(Rooted)" and no use of the word "Stock":
FlyOnTheWall43 said:
Phone: 32 Gb Nexus 6P (Rooted)
Android Version: 8.0.0 (OPR5.170623.007, Oct 2017)
Click to expand...
Click to collapse
........................................................................................................................................................................
v12xke said:
but you are running custom fonts
Click to expand...
Click to collapse
yeah, I used ROM Toolbox to install a custom font and do a couple more tweaks
........................................................................................................................................................................
v12xke said:
and your ROM is for a tablet?
Click to expand...
Click to collapse
The ROM I flashed was this
........................................................................................................................................................................
v12xke said:
Somehow I think you left something out, yeah?
Click to expand...
Click to collapse
I understand that one or more of the tweaks I've done could be causing this, hense:
FlyOnTheWall43 said:
Not sure what other info to include here, but if there's something else that could be affecting this, let me know and I'll provide the info.
Click to expand...
Click to collapse
.
I didn't know where I would be crossing the line into too much, useless into... I was just hoping someone would be able to give me a handful of common things that could cause this. If that's out of the scope of this forum, then I'm sorry for wasting everybody's time.
FlyOnTheWall43 said:
Please note "(Rooted)" and no use of the word "Stock":
........................................................................................................................................................................
yeah, I used ROM Toolbox to install a custom font and do a couple more tweaks
........................................................................................................................................................................
The ROM I flashed was this
........................................................................................................................................................................
I understand that one or more of the tweaks I've done could be causing this, hense: .
I didn't know where I would be crossing the line into too much, useless into... I was just hoping someone would be able to give me a handful of common things that could cause this. If that's out of the scope of this forum, then I'm sorry for wasting everybody's time.
Click to expand...
Click to collapse
What's your root method? This happened to me once before also. I was rooted with Magisk so I installed the add GA module. Quick and easy and it was back. If you are rooted with SuperSU then I would recommend uninstalling it with the uninstaller zip found in the SU thread. Alternatively you can install Magisk over the top of it but all the features like Magisk hide may not work. Another option would be to flash a different Rom. Nitrogen and Cortex are both good options and GA should work by default.
FlyOnTheWall43 said:
Please note "(Rooted)" and no use of the word "Stock":
I understand that one or more of the tweaks I've done could be causing this, hense: .
I didn't know where I would be crossing the line into too much, useless into... I was just hoping someone would be able to give me a handful of common things that could cause this. If that's out of the scope of this forum, then I'm sorry for wasting everybody's time.
Click to expand...
Click to collapse
Rom Toolbox may be running into a conflict with the Pixel Launcher you flashed. I have a similar root and pixel launcher setup minus fonts and other customizations and my shortcut to RT widgets is broken as it will not create the shortcut on the home screen. I haven't had the time to investigate, but it isn't a high priority for me.
Have you tried a clean flash of the October rom?
- Wipe data/dalvik/cache
- flash your various stock rom images (bootloader, radio, boot, system, vendor)
- flash your root method
- flash pixel launcher and reboot into system.
- Setup phone, G Assist, etc.
- Install Rom Toolbox and desired mods
Lengthy process, but it may be worthwhile to contact JRummy, the author of the Pixel launcher, and sending various logs for analysis and help...
hello did you try to clear cache and data from the google app and reboot? that helped me.
murphyjasonc said:
What's your root method? This happened to me once before also. I was rooted with Magisk so I installed the add GA module. Quick and easy and it was back. If you are rooted with SuperSU then I would recommend uninstalling it with the uninstaller zip found in the SU thread. Alternatively you can install Magisk over the top of it but all the features like Magisk hide may not work. Another option would be to flash a different Rom. Nitrogen and Cortex are both good options and GA should work by default.
Click to expand...
Click to collapse
I use Chainfire's systemless root method. I've had GA with this root method before... I'll research Magisk (I've read a little about it, but not enough to be comfortable to jump into it yet) if I'm not able to find another solution. Thank you for your suggestion.
____________________________________________________________________________________________________________________________________________________________________
bb709394 said:
Rom Toolbox may be running into a conflict with the Pixel Launcher you flashed. I have a similar root and pixel launcher setup minus fonts and other customizations and my shortcut to RT widgets is broken as it will not create the shortcut on the home screen. I haven't had the time to investigate, but it isn't a high priority for me.
Have you tried a clean flash of the October rom?
- Wipe data/dalvik/cache
- flash your various stock rom images (bootloader, radio, boot, system, vendor)
- flash your root method
- flash pixel launcher and reboot into system.
- Setup phone, G Assist, etc.
- Install Rom Toolbox and desired mods
Lengthy process, but it may be worthwhile to contact JRummy, the author of the Pixel launcher, and sending various logs for analysis and help...
Click to expand...
Click to collapse
I didn't flash any Pixel launchers... I use Action launcher. I was hoping to avoid wiping all my data, but will do it if I can't get anything else working. Thanks!
____________________________________________________________________________________________________________________________________________________________________
vasilios.kappa said:
hello did you try to clear cache and data from the google app and reboot? that helped me.
Click to expand...
Click to collapse
Yeah, tried that a few days ago and just tried it again, no dice.
I found a magisk module named voenabler. when I installed that I have enhanced LTE option in settings but no use.
Can any dev enable volte in any ROM using that kind of modules??
I know it has discussed many times that zuk z1 can't have volte but I saw this module and thought it'll work.
Itsmeraj said:
I know it has discussed many times that zuk z1 can't have volte but I saw this module and thought it'll work.
Click to expand...
Click to collapse
Will not worked when you read the discussion you've found already. Again: it's the modem update that needs to be provided from the manufacturer.
That module just provides a switch for enhanced LTE , not the logic behind
strongst said:
Will not worked when you read the discussion you've found already. Again: it's the modem update that needs to be provided from the manufacturer.
That module just provides a switch for enhanced LTE , not the logic behind
Click to expand...
Click to collapse
Ok thanx
Itsmeraj said:
I found a magisk module named voenabler. when I installed that I have enhanced LTE option in settings but no use.
Can any dev enable volte in any ROM using that kind of modules??
Click to expand...
Click to collapse
which rom ??? link please....
shirsho said:
which rom ??? link please....
Click to expand...
Click to collapse
You can download this module in any rom.
But don't download this will not work
you can use jio4gvoice app to enable voice calls. (Keep location on to receive calls)
Itsmeraj said:
I found a magisk module named voenabler. when I installed that I have enhanced LTE option in settings but no use.
Can any dev enable volte in any ROM using that kind of modules??
Click to expand...
Click to collapse
am also having this same problem..the magisk module is already installed..but no use of that
This guide is for Mi A2 (Jasmine_sprout) ONLY
Flash at your own Risk
Recently me and some other guys finally managed to install the Android Q DP3 on our Mi A2 and we decided to share the guide with you :
First make sure that you have a backup if anything goes wrong while flashing and that you have downloaded all linked files :
1. Restore the TWRP Backup from here
2. Erase Data and internal Storage
3. Flash DM-Verity & Forceencrypt Disabler from here
4. Erase Data and internal Storage
5. Reboot
Bugs :
1. Bluetooth is not working (Crashes)
2̶.̶ ̶P̶o̶o̶r̶ ̶a̶u̶d̶i̶o̶ ̶i̶n̶ ̶c̶a̶l̶l̶s̶ ̶(̶m̶a̶y̶b̶e̶ ̶o̶n̶l̶y̶ ̶l̶o̶u̶d̶s̶p̶e̶a̶k̶e̶r̶ ̶i̶s̶ ̶w̶o̶r̶k̶i̶n̶g̶ ̶i̶n̶ ̶c̶a̶l̶l̶s̶)̶̶ (just use the new TWRP Backup)
3̶̶.̶̶ ̶̶h̶̶o̶̶t̶̶s̶̶p̶̶o̶̶t̶̶ ̶̶i̶̶s̶̶ ̶̶n̶̶o̶̶t̶̶ ̶̶w̶̶o̶̶r̶̶k̶̶i̶̶n̶̶g̶ (to fix hotspot put attached hotspad.apk in vendor/overlay and if there is no such folder create one)
Other you tell me
Screenshots are attached
NOTE : Since Android Q is a beta and this is WIP dont expect flagship performance or a bugfree experience
Special Thanks to:
@rcstar6696
@willsrockson
@erfanoabdi
@Nail_snail
and every other person who helped to get this working
Wow, great work dude
deleted
StarSix01 said:
This guide is for Mi A2 (Jasmine_sprout) ONLY
Flash at your own Risk
Click to expand...
Click to collapse
Works perfectly fine. And as mentioned on bug list, apart from Bluetooth, Hotspot (though I'm not rely on it much) and in call volume (only loudspeaker) I noticed that phone does recognized USB OTG but it says, it needs to be fixed/format, may be it's just me but OTG works fine though using twrp file manager! And yes, agreed to your point that it is still beta and it can't be completely bug free. Thanks all for providing useful links and testing it extensively before releasing!
NE0HP said:
Works perfectly fine. And as mentioned on bug list, apart from Bluetooth, Hotspot (though I'm not rely on it much) and in call volume (only loudspeaker) I noticed that phone does recognized USB OTG but it says, it needs to be fixed/format, may be it's just me but OTG works fine though using twrp file manager! And yes, agreed to your point that it is still beta and it can't be completely bug free. Thanks all for providing useful links and testing it extensively before releasing!
Click to expand...
Click to collapse
Hotspot is fixed, gonna upload the file when I have wifi already updated the guide
Sent from my Mi A2 using XDA Labs
Any solution for poor audio?
rober788 said:
Any solution for poor audio?
Click to expand...
Click to collapse
In call audio?
Sent from my Mi A2 using XDA Labs
Yes
rober788 said:
Yes
Click to expand...
Click to collapse
No, it's on the bug list, but we're testing some things to get it working
Sent from my Mi A2 using XDA Labs
I think all of the issues is related with apps on vendor/overlay. Btw your hotspot fix is making every app crash. Is there anything specific to copy apk to vendor/overlay (i pushed it from adb)
Users with slow emmc bug can do Androbench test with 512mb to see it will fix?
Ant updates for in call audio?
google canera woks or not ?
malackov said:
google canera woks or not ?
Click to expand...
Click to collapse
you can enable it in build.prop
rober788 said:
Ant updates for in call audio?
Click to expand...
Click to collapse
its fixed gonna publish soon a fix
Cannot signing in Google Account. When I open Setting > Google, only a blank screen shows up and display nothing.
Digital Wellbeing not working as well, it always force stop.
Does anybody have an idea?
liyingheng said:
Cannot signing in Google Account. When I open Setting > Google, only a blank screen shows up and display nothing.
Digital Wellbeing not working as well, it always force stop.
Does anybody have an idea?
Click to expand...
Click to collapse
Install latest GMS (Google play services). Search on apk mirror.
Can I get the link please...
Amnvlad said:
Can I get the link please...
Click to expand...
Click to collapse
https://www.apkmirror.com/apk/google-inc/google-play-services/
Here you go, choose latest one (careful not to choose for tv or wear)
Any updates on low in call audio?
rober788 said:
https://www.apkmirror.com/apk/google-inc/google-play-services/
Here you go, choose latest one (careful not to choose for tv or wear)
Any updates on low in call audio?
Click to expand...
Click to collapse
Sorry but I asked for the Q rom , the one I downloaded from the above link Qbackup.zip isn't working. When I try to flash it is showing error.
Hello,
This is probably my first post in xda. I have been using xda since around 2015 with my first device mi4i. Over the years as a dream to use a flagship level phone i ended up buying s20+ but kind of regret the decision due to lack of active support of custom roms.
Coming to the point. I recently ended up installing GSI rom on s20+ Exynos variant. I did search a lot no direct guide was available hence i am posting my steps to do the same. Let me know of any mistakes.
I tested this with DUJ5 Firmware. So i prefer you flash it if in beta or anything below that.
1)BootLoader Unlock
2)Flash TWRP - any TWRP will do not the lineage/dotos/pixelexperiece recovery. The unoffocial TWRP for s20 will be enough. Ill attatch the one I have with me here. Thanks to twrp-z3s-3.5.2_ianmacd+vbmeta-patched_DUH2. even tjough its DUH2 itll work.
3)Extract the gsi .xz file and copy the image file to the external_sd.
4)As the s20 is using a super partition, direct flash did not work for me. We will need to use the Super GSI installer. Download the attatched super gsi installer and move it to the same location as the gsi image.
5)The script looks its cwd for system.img file to flash, so rename the copied -arm64-ab.img to system.img.
6)Once everything is ready, reboot to the recovery, factory format data, clear everything as required, then flash this Super-GSI-Installer.zip file from the twrp.
7)Voila.. you can reboot once it shows the process completed to your new rom.
Notes;
I havent faced any performance issue in a daily driver use. However, the phone tends to heat up a bit when gaming and charging, compared to the custom lineage or similar tweaked roms for s20.
For camera you can use GCAM by BSG which i have tested and works as it does in the stock rom.
For the usb-c headphone, you can enable the tweaks from setting by phhusson
Let me know how it goes.
For GSI updates follow : {Mod edit}
Thanks to @phhusson for the GSI project and @ianmacd for the twrp. @ponces for earlybird pixelexperience implementation
If you use the phhusons aosp rom, you may face some issue with the twrp after the installation, when i tried to enter the recovery after the installation adn testing, i faced the recovery literally flashing on my display. with pixel experience i did not face that issue, maybe its my error.
link:https://forum.xda-developers.com/f/treble-enabled-device-development-a-ab-roms.7260/
Bugs with GSI A11/12
1)I personally is having trouble finding the auto brightness feature, the devs have enabled it in the rom but i havent cracked that one.
2)Proximity Sensor during call/ Accidental touch / Pocket detection seems to be missing.
3)Volte/Vowifi
4)and some other bugs but nothing i care except for these in day to day usage.
P.S. If anyone can suggest me any fixes for these it would be great.
PM me if any clarifications needed
>{Mod edit}
@mr_scalpel
I've removed the reference to Telegram from your above post. As an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads. These conditions obviously don't apply to your thread or you.
Regards
Oswald Boelcke
Senior Moderator
Oswald Boelcke said:
@mr_scalpel
I've removed the reference to Telegram from your above post. As an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads. These conditions obviously don't apply to your thread or you.
Regards
Oswald Boelcke
Senior Moderator
Click to expand...
Click to collapse
thank you. sorry i missed that .
Check pm
Hi, does 120hz work? Thanks for the guide btw.
Its buggy there is a option to force the 120hz but it will crop in the display when switched to 1080p reolution adn ufo test seems to be aa error when i tested, i guess 120 hz not available as of now
mr_scalpel said:
Its buggy there is a option to force the 120hz but it will crop in the display when switched to 1080p reolution adn ufo test seems to be aa error when i tested, i guess 120 hz not available as of now
Click to expand...
Click to collapse
What about fingerprint unlock?
AllStars101 said:
What about fingerprint unlock?
Click to expand...
Click to collapse
Does not work with any GSI as of now, they are not good with the under display sensor.
Can this twrp you provided mount vendor ? Can we flash any patch like permissiver 5 with this twrp??
sankhauaa said:
Can this twrp you provided mount vendor ? Can we flash any patch like permissiver 5 with this twrp??
Click to expand...
Click to collapse
I havent tested extensively. but i feel that should work
Is it possible to force higher refresh rate on any GSI?
Theo1218 said:
Is it possible to force higher refresh rate on any GSI?
Click to expand...
Click to collapse
dont think itll work outside of samsung firmware
I don't know about GSI but we hard coded 120hz on lineage 17
[ROM][UNOFFICIAL][S20,S20U][120hz] - LineageOS 17.1
I've been having issues with the fingerprint reader and the camera not opening from some apps. Everything else that I've tested has been working fine. Can you please confirm that I followed the process correctly before I dig too much deeper...
forum.xda-developers.com
ChongoDroid said:
I don't know about GSI but we hard coded 120hz on lineage 17
[ROM][UNOFFICIAL][S20,S20U][120hz] - LineageOS 17.1
I've been having issues with the fingerprint reader and the camera not opening from some apps. Everything else that I've tested has been working fine. Can you please confirm that I followed the process correctly before I dig too much deeper...
forum.xda-developers.com
Click to expand...
Click to collapse
Is that only for snapdragon?
Theo1218 said:
Is that only for snapdragon?
Click to expand...
Click to collapse
Correct
mr_scalpel said:
Its buggy there is a option to force the 120hz but it will crop in the display when switched to 1080p reolution adn ufo test seems to be aa error when i tested, i guess 120 hz not available as of now
Click to expand...
Click to collapse
That's right. I was also using the GSI on my S20 Plus Exynos. And when using Force FPS to 1080p/120Hz, it just crops the display. So I have to forcefully use 1440p at 60 Hz, which is a big NO! for me. I switched back to stock soon after as there were no official AOSP builds available for S20 plus series. There was one Lineage 19.1 (A12) but it has been discontinued. Now Android 14 is gonna come out and getting a Samsung phone just feels like a regret. Tried my best to fix the FPS issue but didn't get it fixed (even when personally helped by @phhusson (He tried his best, but I gave up soon after as I couldn't understand anything). Damn, Samsung is like the "Apple of Android" because they basically restrict everything.
Hi, I recently figured out Lineage OS have native call recording feature and is not enabled for all countries. So I asked for some help and found that it is possible to enable call recording by using RRO.
Lineage Call Recording Enabler (Lineage Dialer RRO):This is a Runtime Resource Overlay for the dialer app in LineageOS to enable call recording in all countries.
LineageOS native call recording is enabled or disabled depending on your current location and the those countries are listed here, https://github.com/LineageOS/androi...ler/callrecord/res/xml/call_record_states.xml. One can enable or disable call recording by updating those values and this is what this overlay does.
Below I have provided download link for flashable zip files to flash with recovery or magisk. Flash recovery version with recovery and magisk version with magisk.
Tested on:
Lineage OS 19.1 + Lineage OS Recovery
Lineage OS 20 + Magisk 25.2
How to build RRO and flashable ZIP for recovery and Magisk (OPTIONAL):I was too lazy to put all details here so please read the README.md.
Download links (Github): https://github.com/2shrestha22/lineage-call-recording-enabler/releases/tag/v1.0.1
is it compatible with LOS 20 recovery?
Thanks,
Ahmad Rady said:
is it compatible with LOS 20 recovery?
Thanks,
Click to expand...
Click to collapse
Yes it is. If you use magisk, magisk module is recommended.
The Magisk module works perfectly for me on LineageOS 20 for the OnePlus 7Pro. Thank you!
- First of all many thanks for your efforts, it's really appreciated
- I've installed it on LineageOS 18.1 and it works fine but I could not find any calls recording settings except the output file format, please advise...
mostafa3bdou said:
- First of all many thanks for your efforts, it's really appreciated
- I've installed it on LineageOS 18.1 and it works fine but I could not find any calls recording settings except the output file format, please advise...
Click to expand...
Click to collapse
It only enables call recording feature that was disabled in the country. It does not add any feature.
HatMan22 said:
It only enables call recording feature that was disabled in the country. It does not add any feature.
Click to expand...
Click to collapse
So, is this the default of the Lineage Dialer?
mostafa3bdou said:
So, is this the default of the Lineage Dialer?
Click to expand...
Click to collapse
yes
HatMan22 said:
yes
Click to expand...
Click to collapse
Thanks!
I successfully installed and enabled the module using Magisk, but I am unable to locate the recording button or configuration settings even during call.
va.zahiri said:
I successfully installed and enabled the module using Magisk, but I am unable to locate the recording button or configuration settings even during call.
Click to expand...
Click to collapse
What is your country code?
HatMan22 said:
What is your country code?
Click to expand...
Click to collapse
Sorry for my mistake. I just realized that my country code is IR and that call recording is allowed by default. However, I'm still unable to record calls. Are there any other restrictions that might be causing this issue? I use LOS 19.1
va.zahiri said:
Sorry for my mistake. I just realized that my country code is IR and that call recording is allowed by default. However, I'm still unable to record calls. Are there any other restrictions that might be causing this issue? I use LOS 19.1
Click to expand...
Click to collapse
I don't know any other restrictions. AFAIK recording is only enabled/disabled based on county. Could you ask in official LineageOS thread and update here too?
HatMan22 said:
Hi, I recently figured out Lineage OS have native call recording feature and is not enabled for all countries. So I asked for some help and found that it is possible to enable call recording by using RRO.
Lineage Call Recording Enabler (Lineage Dialer RRO):
Click to expand...
Click to collapse
Best thanks, it also works fine with ArrowOS-13.0 [miatoll, VANILLA build] .
Hello, just installed the module with magisk, but I cant see any options or recoding icon on the dialer. Any idea why ?
My country code is +269
hyad94 said:
Hello, just installed the module with magisk, but I cant see any options or recoding icon on the dialer. Any idea why ?
My country code is +269
Click to expand...
Click to collapse
Check if your country is listed here. https://github.com/2shrestha22/line.../blob/main/rro/res/xml/call_record_states.xml
va.zahiri said:
I successfully installed and enabled the module using Magisk, but I am unable to locate the recording button or configuration settings even during call.
Click to expand...
Click to collapse
Do you have any update on this?
HatMan22 said:
Do you have any update on this?
Click to expand...
Click to collapse
I haven't been able to find a solution to the problem. Firstly, I checked the source code for my LOS 19.1 and it seems to be okay and my country is allowed for call recording in the config file. Then, I tried to get help in the IRC channel of LineageOS, but unfortunately, I couldn't find any useful information there. I even searched and read through sites like Reddit, but in the end, I still couldn't find a solution.
As a last resort, I installed BCR, and it works great, but it's not the native call recorder.
HatMan22 said:
Check if your country is listed here. https://github.com/2shrestha22/line.../blob/main/rro/res/xml/call_record_states.xml
Click to expand...
Click to collapse
Yes, my country is listed: km. And I discovered that the record button only appears when the call is answered and not when it ringing. And the automatic recording doesnt start, you have to press manually and there is no option for that, the only option for recording is audio format. Thx anyway. I think BCR is a better choice for now.
Thank you for this!