Enable Native Call Recording [OOS] [ROOT/NON-ROOT] [APP/MAGISK MODULE/ADB/TASKER]

L

Lartsch

Senior Member
Oct 23, 2012
186
215
0
Karlsruhe
Nov 9, 2018 at 6:55 PM
Sadly, this mod breaks the Viper4Android magisk module (reports abnormal driver status). When a profile is loaded it tries to enable again (you can hear it) but instantly gets disabled (probably because of the infinite command execution). Worked again after disabling the call recorder module.
... Wasn't sure where to report this one, sorry if this doesn't belong here. Still, I hope you can maybe sort this out or can recommend a bypass. Would love to use your module as well but viper is essential for me.

Best wishes,
Lars
 
shadowstep

shadowstep

Forum Moderator
Staff member
Jun 6, 2014
4,292
8,105
263
30
Ambala
Nov 9, 2018 at 7:01 PM
Lartsch said:
Sadly, this mod breaks the Viper4Android magisk module (reports abnormal driver status). When a profile is loaded it tries to enable again (you can hear it) but instantly gets disabled (probably because of the infinite command execution). Worked again after disabling the call recorder module.
... Wasn't sure where to report this one, sorry if this doesn't belong here. Still, I hope you can maybe sort this out or can recommend a bypass. Would love to use your module as well but viper is essential for me.

Best wishes,
Lars
Click to expand...
Already fixed in the latest version of the module. Magisk Repo has also been updated with the fix. Your issue will be resolved after updating. :)
 
shadowstep

shadowstep

Forum Moderator
Staff member
Jun 6, 2014
4,292
8,105
263
30
Ambala
Nov 10, 2018 at 9:28 AM
Lartsch said:
Yes, absolute sure now. I installed another time and the same error. Same behaviour with the script method.
Click to expand...
Script won't work - I just realized I forgot to update that. The Magisk module however is working fine alongside ViPER4Android.
@DvLAx3l Can you double check? I did the same changes as the test module that I sent to you for testing, which worked fine for you and resolved compatibility issues with ViPER4Android for you.
 
  • Like
Reactions: DvLAx3l
L

Lartsch

Senior Member
Oct 23, 2012
186
215
0
Karlsruhe
Nov 10, 2018 at 11:49 AM
shadowstep said:
Script won't work - I just realized I forgot to update that. The Magisk module however is working fine alongside ViPER4Android.

@DvLAx3l Can you double check? I did the same changes as the test module that I sent to you for testing, which worked fine for you and resolved compatibility issues with ViPER4Android for you.
Click to expand...

Yes I saw that afterwards, but the module still doesn't work for me. When I use OxyMod to set it, it seems to work. I have no clue left what the problem could be. In the end, Viper installations/setups and compatibility settings can differ.

I'm on a OnePlus 6T by the way, ElementalX, latest OxygenOS. Selinux is set to enforcing (but it was the same when I had it permissive) with V4A XHifi and normal V4A (the versions by ahrion, zackptg5 etc.) running on top of the Audio Modification Library (Magisk module by ahrion & zackptg5 as well). Both V4A apps run in normal mode. Magisk is 17.3. That I have XHifi installed should not be of any matter, since the problem also occured when I only had the normal V4A.

Just out of interest, why does your script / OnePlus implementation of the necessary setting interfer with Viper?
 
Last edited:
shadowstep

shadowstep

Forum Moderator
Staff member
Jun 6, 2014
4,292
8,105
263
30
Ambala
Nov 10, 2018 at 5:25 PM
Lartsch said:
Yes I saw that afterwards, but the module still doesn't work for me. When I use OxyMod to set it, it seems to work. I have no clue left what the problem could be. In the end, Viper installations/setups and compatibility settings can differ.

I'm on a OnePlus 6T by the way, ElementalX, latest OxygenOS. Selinux is set to enforcing (but it was the same when I had it permissive) with V4A XHifi and normal V4A (the versions by ahrion, zackptg5 etc.) running on top of the Audio Modification Library (Magisk module by ahrion & zackptg5 as well). Both V4A apps run in normal mode. Magisk is 17.3. That I have XHifi installed should not be of any matter, since the problem also occured when I only had the normal V4A.

Just out of interest, why does your script / OnePlus implementation of the necessary setting interfer with Viper?
Click to expand...
I updated the Magisk module and the script to run the command infinitely after every 60 seconds to alleviate the issue of OnePlus turning off the native call recording after some time, if enabled manually. However, I forgot to make the infinite loop run asynchronously, i.e. forgot to make it run independent of other processes due to which the V4A process had to wait indefinitely, making V4A nor process at all. With the latest v5.3 of the module, however, I updated the infinite loop to run asynchronously to fix this.
 
  • Like
Reactions: SourPower and DvLAx3l
Depressed T.Bear

Depressed T.Bear

Senior Member
Jun 3, 2013
859
669
123
Berlin
Nov 10, 2018 at 11:38 PM
shadowstep said:
I updated the Magisk module and the script to run the command infinitely after every 60 seconds to alleviate the issue of OnePlus turning off the native call recording after some time, if enabled manually. However, I forgot to make the infinite loop run asynchronously, i.e. forgot to make it run independent of other processes due to which the V4A process had to wait indefinitely, making V4A nor process at all. With the latest v5.3 of the module, however, I updated the infinite loop to run asynchronously to fix this.
Click to expand...
I'm still on 5.1 and the call recorder was never deactivated magically. Just wanted to let you know ;)
I'm afraid of updating to the latest version, I assume that something which is running infinitely in the background may decrease battery life.

Sent from my OnePlus 6 using XDA Labs
 
shadowstep

shadowstep

Forum Moderator
Staff member
Jun 6, 2014
4,292
8,105
263
30
Ambala
Nov 11, 2018 at 5:29 AM
Depressed T.Bear said:
I'm still on 5.1 and the call recorder was never deactivated magically. Just wanted to let you know ;)
I'm afraid of updating to the latest version, I assume that something which is running infinitely in the background may decrease battery life.
Click to expand...
Good for you! Many people reported the magical removal of the option - so I had to look for workarounds. Also, I had similar concerns about battery life because of the infinite loop, but if you read through the thread, many people reported that that wasn't the case/it was negligible (a modified module was posted some time back, I just incorporated the changes from that module, so referring to the observations of that module + other Tasker scripts that were posted that used to run every x minutes to active native call recording). :)
 
  • Like
Reactions: dandemonic
shadowstep

shadowstep

Forum Moderator
Staff member
Jun 6, 2014
4,292
8,105
263
30
Ambala
Nov 13, 2018 at 3:20 PM
crumble6 said:
v5.1 didn't work for me so I will be sticking with v5.3
Click to expand...
Yeah well, different Magisk module versions have worked for different people, unfortunately. It's not possible for me to keep maintain different versions for all the people, hence I reverted. If v5.3 is working for you, definitely stick to it. I'm just glad it's working fine for you. If you ever need the old zip handy, just in case, let me know and I'll upload it here. :)
 
andreacos92

andreacos92

Senior Member
Mar 6, 2014
190
82
58
Bologna
Nov 26, 2018 at 2:13 PM
With v5.4 I have again the same problems with other Magisk modules (i.e. Viper4Android) we had with v5.2, that then were solved with v5.3.
I rolled back on v5.3 at the moment :)
 
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone