I tried building CM and ResurrectionRemix for Nexus 5X and got the same error:
Code:
using prebuilt boot.img from BOOTABLE_IMAGES...
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 53, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 49, in main
common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img)
File "/home/gururoop/android/cm13/build/tools/releasetools/common.py", line 1443, in MakeRecoveryPatch
_, _, patch = d.ComputePatch()
File "/home/gururoop/android/cm13/build/tools/releasetools/common.py", line 1131, in ComputePatch
p = Run(cmd, stdout=subprocess.PIPE, stderr=subprocess.PIPE)
File "/home/gururoop/android/cm13/build/tools/releasetools/common.py", line 87, in Run
return subprocess.Popen(args, **kwargs)
File "/usr/lib/python2.7/subprocess.py", line 710, in __init__
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
make: *** [/home/gururoop/android/cm13/out/target/product/bullhead/system/bin/install-recovery.sh] Error 1
make: Leaving directory `/home/gururoop/android/cm13'
I tried downloading the repo afresh, but got the same error. Any help would be highly appreciated.
Install: https://play.google.com/store/apps/details?id=com.termux
Then open Termux
Type:
apt update; apt install sqlite
SU
Then type:
/data/data/com.termux/files/usr/bin/sqlite3 /data/user/0/com.google.android.gms/databases/phenotype.db
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__enable_call_recording", 0, 1, 0)
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__force_within_call_recording_geofence_value", 0, 1, 0)
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__use_call_recording_geofence_overrides", 0, 1, 0)
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__force_within_crosby_geofence_value", 0, 1, 0)
Next:
Clear dialer data
Open dialer and force close (clear from recent apps)
Open the dialer once again and in settings screen, you should see: "call recording"
Optional:
Depending on your location, you might get a pre-recording prompt notifying you (and the other party on the line) that the call may be recorded. This can be disabled by unzipping the attached file and copying the files to: /data/data/com.google.android.dialer/files/callrecordingprompt
Then in termux, run the following command
SU (unless your initial Termux session is still running)
chmod -R 777 /data/data/com.google.android.dialer/files/callrecordingprompt
Please note that disabling this prompt may be illegal depending on your jurisdiction. Some places however only require single party consent. Hence, why I posted this. You are responsible to know the laws of your jurisdiction. I will not be held liable for you breaking the law.
Major props to this thread: https://forum.xda-developers.com/t/...ding-in-stock-dialer-app-root-needed.4321719/
And @gisthere and @Liranazuz5
The above is a modification from their work on that thread. Most notability the removal of some ";" in the code that caused database errors and the combination of 2 different posts (flag implementation + app w/ database flags sync).
Intention of this thread: bring this information to Pixel 6 Pro owners. Please go and like the original thread/user posts (instead of this thread).
mkhcb said:
Install: https://play.google.com/store/apps/details?id=com.termux
Then open Termux
Type:
apt update; apt install sqlite
SU
Then type:
/data/data/com.termux/files/usr/bin/sqlite3 /data/user/0/com.google.android.gms/databases/phenotype.db
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__enable_call_recording", 0, 1, 0)
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__force_within_call_recording_geofence_value", 0, 1, 0)
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__use_call_recording_geofence_overrides", 0, 1, 0)
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__force_within_crosby_geofence_value", 0, 1, 0)
Next:
Clear dialer data
Open dialer and force close (clear from recent apps)
Open the dialer once again and in settings screen, you should see: "call recording"
Major props to this thread: https://forum.xda-developers.com/t/...ding-in-stock-dialer-app-root-needed.4321719/
And @gisthere and @Liranazuz5
The above is a modification from their work on that thread. Most notability the removal of some ";" in the code that caused database errors and the combination of 2 different posts (flag implementation + app w/ database flags sync).
Intention of this thread: bring this information to Pixel 6 Pro owners. Please go and like the original thread/user posts (instead of this thread).
Click to expand...
Click to collapse
Good info. For those of us that are too lazy to go through those steps, there is also a tiny app available to enable call recording as well (rooted devices only). Just install, enable from the app, and after 15 minutes or so you should see the call recording button/option. Been using on my device for a bit now and no issues. There are also a ton of flags available you can experiment with, just use caution in doing so. I am not the dev and no credit goes to me. Just sharing the devs (jacopotediosi) work:
Releases · jacopotediosi/GAppsMod
Tweak Google apps (e.g., Phone and Messages) to unlock hidden features (e.g., available only in some countries or on certain devices). Root is required. - jacopotediosi/GAppsMod
github.com
scott.hart.bti said:
Good info. For those of us that are too lazy to go through those steps, there is also a tiny app available to enable call recording as well (rooted devices only). Just install, enable from the app, and after 15 minutes or so you should see the call recording button/option. Been using on my device for a bit now and no issues. There are also a ton of flags available you can experiment with, just use caution in doing so. I am not the dev and no credit goes to me. Just sharing the devs (jacopotediosi) work:
Releases · jacopotediosi/GAppsMod
Tweak Google apps (e.g., Phone and Messages) to unlock hidden features (e.g., available only in some countries or on certain devices). Root is required. - jacopotediosi/GAppsMod
github.com
Click to expand...
Click to collapse
Nice find!
mkhcb said:
Install: https://play.google.com/store/apps/details?id=com.termux
Then open Termux
Type:
apt update; apt install sqlite
SU
Then type:
/data/data/com.termux/files/usr/bin/sqlite3 /data/user/0/com.google.android.gms/databases/phenotype.db
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__enable_call_recording", 0, 1, 0)
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__force_within_call_recording_geofence_value", 0, 1, 0)
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__use_call_recording_geofence_overrides", 0, 1, 0)
INSERT INTO FlagOverrides(packageName, user, name, flagType, boolVal, committed) VALUES("com.google.android.dialer", "", "G__force_within_crosby_geofence_value", 0, 1, 0)
Next:
Clear dialer data
Open dialer and force close (clear from recent apps)
Open the dialer once again and in settings screen, you should see: "call recording"
Major props to this thread: https://forum.xda-developers.com/t/...ding-in-stock-dialer-app-root-needed.4321719/
And @gisthere and @Liranazuz5
The above is a modification from their work on that thread. Most notability the removal of some ";" in the code that caused database errors and the combination of 2 different posts (flag implementation + app w/ database flags sync).
Intention of this thread: bring this information to Pixel 6 Pro owners. Please go and like the original thread/user posts (instead of this thread).
Click to expand...
Click to collapse
Hi buddy,
All credit for these call recording values goes to @gisthere !
But yeah, i'm still using that method on the P6Pro.
Just a note, in some regions there is a stupid voice message whenever you start recording. So, in order to eliminate that just replace these two files in /data/data/com.google.android.dialer/files/callrecordingprompt with the files inside that that zip file attached. Rename the unzipped files accordingly .
Liranazuz5 said:
Hi buddy,
All credit for these call recording values goes to @gisthere !
But yeah, i'm still using that method on the P6Pro.
Just a note, in some regions there is a stupid voice message whenever you start recording. So, in order to eliminate that just replace these two files in /data/data/com.google.android.dialer/files/callrecordingprompt with the files inside that that zip file attached. Rename the unzipped files accordingly .
Click to expand...
Click to collapse
So I replaced the files and now it says "Recording Failed" when I replaced the files. What permissions are your files? Any tips?
Edit: seems like the files above are corrupt and hence why I can't get it to work.
Edit 2: It appears that the file owner, which I can't seem to reproduce, has to be exactly the same as the original file.
Edit 3: chmod -R 777 /data/data/com.google.android.dialer/files/callrecordingprompt seems to have fixed the issue.
Can we uninstall sqlite after the changes are done?
@mkhcb "Edit 3: chmod -R 777 /data/data/com.google.android.dialer/files/callrecordingprompt seems to have fixed the issue." -> This with the corrupt files or the original files?
mkhcb said:
So I replaced the files and now it says "Recording Failed" when I replaced the files. What permissions are your files? Any tips?
Edit: seems like the files above are corrupt and hence why I can't get it to work.
Edit 2: It appears that the file owner, which I can't seem to reproduce, has to be exactly the same as the original file.
Edit 3: chmod -R 777 /data/data/com.google.android.dialer/files/callrecordingprompt seems to have fixed the issue.
Click to expand...
Click to collapse
I should've mentioned that smh, sorry buddy, it was late..
WhoIsJohnGalt1979 said:
@mkhcb "Edit 3: chmod -R 777 /data/data/com.google.android.dialer/files/callrecordingprompt seems to have fixed the issue." -> This with the corrupt files or the original files?
Click to expand...
Click to collapse
The files are not corrupt, I thought they were since I couldn't open it with VLC. Even if it is corrupt, it works with the right permission .
These are just an "empty" wav files, that's all .
Liranazuz5 said:
These are just an "empty" wav files, that's all .
Click to expand...
Click to collapse
I figured based on the size. I thought it would at least be 1 second of nothing sounds, but nope.
mkhcb said:
I figured based on the size. I thought it would at least be 1 second of nothing sounds, but nope.
Click to expand...
Click to collapse
Yeah lol, 00:00 seconds recording.
Great job on that guide, nicely done Sir!
scott.hart.bti said:
Good info. For those of us that are too lazy to go through those steps, there is also a tiny app available to enable call recording as well (rooted devices only). Just install, enable from the app, and after 15 minutes or so you should see the call recording button/option. Been using on my device for a bit now and no issues. There are also a ton of flags available you can experiment with, just use caution in doing so. I am not the dev and no credit goes to me. Just sharing the devs (jacopotediosi) work:
Releases · jacopotediosi/GAppsMod
Tweak Google apps (e.g., Phone and Messages) to unlock hidden features (e.g., available only in some countries or on certain devices). Root is required. - jacopotediosi/GAppsMod
github.com
Click to expand...
Click to collapse
This module worked very well on my pixel 6 for almost 7 months. now, suddenly the phone starts to prmopt"not support in your region"
How it woks for you now?
Chmod is a linux or terminal command. Will it work if we just change the permissions in a root explorer on the phone?
Spookymyo said:
Chmod is a linux or terminal command. Will it work if we just change the permissions in a root explorer on the phone?
Click to expand...
Click to collapse
Yes
Edit: Darn sorry for the bump. I got a notification and thought this was a new question. Then I realized the notification was a like, not a reply to my thread.
I purchased the full version of 'call recorder' by skvalex. Pricy, but just works.
fil3s said:
I purchased the full version of 'call recorder' by skvalex. Pricy, but just works.
Click to expand...
Click to collapse
I can confirm it is working without any problems. Thanks for the heads up!