Np, it's my jobThanks for being helpful @strongst, as always!
Nice ! Didnt see that one. Wondering which solution will be the most battery consuming then...
I've tested all a few days and didn't encounter any problems regarding battery drain.
I think he means which method to enable native call recording is the most efficient.
Every method enables call recording in a different way. Battery life isn't impacted as I mentioned here https://forum.xda-developers.com/on...ble-call-recording-boot-t3634292/post77976068
I can only give a feedback for my setup, so everyone should test the different methods.
I was meaning to ask, has your Tasker profile been running effectively? No random call recording option disappearing? If so, I'll add that to the OP as the recommended option.
Yeah, it's running excellent and option did not disappear, but as said: better to test before decide for an methodI was meaning to ask, has your Tasker profile been running effectively? No random call recording option disappearing? If so, I'll add that to the OP as the recommended option.
Don't use OOS, don't plan on using OOS, so can't test, unfortunately. I'll take your word for it.Yeah, it's running excellent and option did not disappear, but as said: better to test before decide for an method
Thanks!
Ah, I meant the others, not youDon't use OOS, don't plan on using OOS, so can't test, unfortunately. I'll take your word for it.
Hi guys! I've updated the OP. Changes include removal of the build.prop edit method, top recommendation now changed to an updated Tasker profile, Magisk module update and boot script update.
Hi ,Hi guys! I've updated the OP. Changes include removal of the build.prop edit method, top recommendation now changed to an updated Tasker profile, Magisk module update and boot script update.
i chckd your tasker profile that works 100% but
we NEED to run that cmd at boot(eventprofile) once too. (recommmend 30s wait at boot event if u use magisk as root)
or that event will never be true if at phone boot call record is disabled. (like after a clean flash,or if u get a call same time under phonerestart and phone disables it ,but tasker didnt had time to run the profile ,then phone boots up with value 0 , so that event never runs.
Last edited:
Just use the v2 apk in conjunction with the Tasker profile, and that should take care of the scenario that you're talking about. The apk will handle on boot command run while the Tasker profile will handle the command run whenever the global variable changes from then onwards.
I made my own tasker profile out of ideas from this thread. It contains 3 cases:Just use the v2 apk in conjunction with the Tasker profile, and that should take care of the scenario that you're talking about. The apk will handle on boot command run while the Tasker profile will handle the command run whenever the global variable changes from then onwards.
- enable after boot (delayed a bit)
- enable when airplane mode is switched off
- enable when it gets disabled (this idea is really smart and elegant, thanks for the creator)
Then all my use cases are covered. I'm just planning a widget to monitor the state of the call rec value.
u need only 2 profiles 1 enable task ,
you only need the boot enable option to secure the variable change event (in Shadowsteps profile) to be sure true if "oneplus/APM/or any case"disables it sets[event] var to 0.
in case its 0 and set to 0 the event(shadowste0s profile) never well be true,
so we set it to 1 at boot,
and the profile from Shadowstep reacts on every variable change an sets it to 1 again and again if needed
Last edited:
@shadowstep thanks as always for your work, but the last update break (I don't how and why) viper4android, I've tried every version of viper and no one work until I disable your module... I should have the previous update on my computer @ home, I'll let you know if works or it's something else.
Last edited:
@shadowstep, the problem might be that the infinite loop isn't running asynchronously. Maybe if the entire script contents was contained in '()&' the problems with other mods will go awayDvLAx3l;78102098 [user=5893314 said:
Thanks for your report and testing the test module that I sent to you as well. OP is now updated with the updated module containing the fix and I've pushed the update to Magisk Repo as well.
As always, thanks for the tip mate! Appreciate you always being there and helpful. :highfive: