Delete this post pls.
If you don't use camera.stats.test 5 GCam 6.1 will not work. I don't know what camera.stats.test 5 does or means but without it GCam 6.1 will not work only 5.1 works even 5.3 crashes but if you use that command most of the GCams work
i've already unlocked camera 2 api but when i trying again this method in CMD says "permission denied"
Did you boot with patched Boot IMG? And did you grant root access after ADB shell su command?
I followed your method. SU operation says Permission denied.
Then I installed Magisk manager from APK mirror and skipped the full zip installation.
After this, when I used SU in the terminal. It worked and I have enabled Camera2 API (Confirmed with Camera 2 Probe app).
After restart the device is unrooted and Camera2API is still present.
So I guess OTA is not broken.
GCam Back camera crashes (Arnova version and BSG Version GCam 6.1
GCam 6.1? Did you use the third setprop command? And which GCam version did you use? I suggest u to use the GCam which I have given In the thread.
works fine for me with gcam 6.1, could somebody make this into a magisk module to keep OTA?
akshayakakat said:
GCam 6.1? Did you use the third setprop command? And which GCam version did you use? I suggest u to use the GCam which I have given In the thread.
Click to expand...
Click to collapse
Ya, I used all the commands.
I used the latest GCam by BSG for Mi8.
I tested the version that you shared. It doesn't work too.
GCam 5.1 by Arnova works well.
adaamweber said:
works fine for me with gcam 6.1, could somebody make this into a magisk module to keep OTA?
Click to expand...
Click to collapse
If you install a magisk module then you loose OTA and you cannot keep the module installed if you uninstall magisk. You cannot install magisk module by using fastboot boot patched_boot.img unless you install magisk on your phone which kills OTA.
I have edited it a little btw you need to use
PHP:
setprop persist.vendor.camera.stats.test 5
as well
Update : after adding the new line it works perfect including night mode
It didn't work with me
akshayakakat said:
I have edited it a little btw you need to use
PHP:
setprop persist.vendor.camera.stats.test 5
as well
Click to expand...
Click to collapse
GCam 6.1 works well after this!
It's work for me.. But front camera only can take 5mp instead of full resolution 20mp.. Kinda disappointing because I have another device, moto g5s plus running on arrow os pie, front camera is 8mp and on gcam, it support full resolution..
Gcam 6.1 is working but still sluggish. Anyway thanks for the great guide.
akshayakakat said:
If you install a magisk module then you loose OTA and you cannot keep the module installed if you uninstall magisk. You cannot install magisk module by using fastboot boot patched_boot.img unless you install magisk on your phone which kills OTA.
Click to expand...
Click to collapse
If your statement is true, how did I update from august to september to october to november by OTA?
sktoys said:
Gcam 6.1 is working but still sluggish. Anyway thanks for the great guide.
Click to expand...
Click to collapse
Try the latest gcam from here for pie
https://www.apkmirror.com/apk/arnova8g2/
kishd said:
Try the latest gcam from here for pie
Yes already downloaded v6.1_Final_V1a..will give it a try later. cause sometimes V6.1 will crash or stuck at processing HDR. or there's something I need to tweak in the settings?
Click to expand...
Click to collapse
sktoys said:
kishd said:
Try the latest gcam from here for pie
Yes already downloaded v6.1_Final_V1a..will give it a try later. cause sometimes V6.1 will crash or stuck at processing HDR. or there's something I need to tweak in the settings?
Click to expand...
Click to collapse
Gone back to 5.1 myself.
Click to expand...
Click to collapse
kishd said:
sktoys said:
Gone back to 5.1 myself.
Click to expand...
Click to collapse
Yes I got 5.1 installed but want to try the night sight feature on 6.1 ..Sometimes it's working sometimes it's not..seems like it got focus related bug. The exposure is great but some area seems like it's out of focus.
Click to expand...
Click to collapse
It keeps saying permission denied when I try to do su
akshayakakat said:
Hi Guys,
If you want to Use Google Camera 6.1 on Mi A2 I have a good news for you guys.
You can do it by using temporary root meathod.
First Boot into respective patched_boot.img for your software version using
PHP:
fastboot boot patched_boot.img
If you are on Stable Pie 10.0.1.0 pie you can get patched_boot.img here
After that use
PHP:
adb shell
PHP:
su
PHP:
setprop persist.camera.HAL3.enabled 1
PHP:
setprop persist.vendor.camera.HAL3.enabled 1
PHP:
setprop persist.camera.stats.test 5
[Edit] also use
PHP:
setprop persist.vendor.camera.stats.test 5
[/Edit]
then do
PHP:
exit
PHP:
exit
PHP:
adb reboot
Done you have Camera2 API and Gcam 6.1 will work.
Please do note that I haven't tried relocking the bootloader if anyone can try it I will be very thankful.
I used this GCam 6.1 btw. Can't confirm if any other GCam 6.1 will work or not but it should work.
Click to expand...
Click to collapse
Related
Has anyone found a solution to get v4a working properly on sm-g928f?
Tried by the following steps without success:
1. Copied v4a app to system/priv-apps/...
2. Frozen sound alive and adapt sound service
3. Rebooted
4. Installed driver
5. Rebooted
driver seems to be installed.
Any help appreciated.
thx in advance
bump!
facing the same problem here. even made a clean new odin flash of latest L2 rom (with data wipe), and can't get it to work...
i tried to install as apk, flash different packages from threads here, all without success...
can someone with vfa working please tell us how to proper install it? thx in advance!!
detdroid said:
Has anyone found a solution to get v4a working properly on sm-g928f?
Tried by the following steps without success:
1. Copied v4a app to system/priv-apps/...
2. Frozen sound alive and adapt sound service
3. Rebooted
4. Installed driver
5. Rebooted
driver seems to be installed.
Any help appreciated.
thx in advance
Click to expand...
Click to collapse
Viper works fantastic on device.
These are correct steps :
First you need PERMISSIVE kernel, otherwise it won't work.
You need to DELETE not to freeze sound alive and adapt sound.
In build.prop find the lines or add them as follows ;
Ipa.decode=false
tunnel.decode=false
lpa.use-stagefright=false.
Push Viper apk in private apps.
Set apk permission to
rw-r-r
rw-r
Reboot device.
Run Viper again and follow instructions.
detdroid said:
Has anyone found a solution to get v4a working properly on sm-g928f?
Tried by the following steps without success:
1. Copied v4a app to system/priv-apps/...
2. Frozen sound alive and adapt sound service
3. Rebooted
4. Installed driver
5. Rebooted
driver seems to be installed.
Any help appreciated.
thx in advance
Click to expand...
Click to collapse
Copying and freezing some apps cant make it work properly man. Viper4Android needs lots of frameworks, lib files, effect and permission files etc(build.prob additions).. So; Audax Rom's sound mod is working without any problem(Viper+Dolby Atmos). After flashing the rom you dont even need to install drivers for V4A!!
tin2404 said:
Viper works fantastic on device.
These are correct steps :
First you need PERMISSIVE kernel, otherwise it won't work.
You need to DELETE not to freeze sound alive and adapt sound.
In build.prop find the lines or add them as follows ;
Ipa.decode=false
tunnel.decode=false
lpa.use-stagefright=false.
Push Viper apk in private apps.
Set apk permission to
rw-r-r
rw-r
Reboot device.
Run Viper again and follow instructions.
Click to expand...
Click to collapse
thx for your reply!
as far as i know the build.prop edits are no more necessary in lollipop, the were needed in kitkat.
also the permissive kernel is no longer a requirement, as systemless root and adding the vfa policy fix would work with lollipop stock kernels.
but just to get sure, i tried your recommendations to the point, but with the same result as with my setup:
all seems to be right, but in driver status it says
NEON enabled: Yes
Enabled: Yes
Status: Normal
Audio Format: Supported
Processing: No
Sampling Rate: 48000
the strange thing is: I only get NEON enabled when installing the driver per zip flash, otherwise vfa would install a non neon driver.
i use vfa since years, and i never went into such problems as with samsung 5.1.1...
any ideas what i'm doing wrong??
Hey guys, I know that the G4 doesn't have the greatest camera in the world, but I was just wondering for tinkering/P.O.C. purposes if RAW photos are possible. According to freedcam, this phone is only using the camera1 API, which from what I understand does not natively support RAW capture. Would a custom ROM, like that CM13 build being worked on for example, be able to shoot in RAW format even if the phone doesn't originally support it?
LeifEricson said:
Hey guys, I know that the G4 doesn't have the greatest camera in the world, but I was just wondering for tinkering/P.O.C. purposes if RAW photos are possible. According to freedcam, this phone is only using the camera1 API, which from what I understand does not natively support RAW capture. Would a custom ROM, like that CM13 build being worked on for example, be able to shoot in RAW format even if the phone doesn't originally support it?
Click to expand...
Click to collapse
It seems with Motorola you just need to patch the hal add me on telegram at defcomk them send me the camera.msm**** / camera.vendor.***.so found in /system/lib/hw/
I've seen that defcomg found a solution for moto g5 to get raw working by enabling camera2 API. I want to know if I can use the same terminal command for moto g4 plus to get raw, even if with freedcam only
Martinezjpo said:
I've seen that defcomg found a solution for moto g5 to get raw working by enabling camera2 API. I want to know if I can use the same terminal command for moto g4 plus to get raw, even if with freedcam only
Click to expand...
Click to collapse
It should work the same as Moto G5 plus but it seemed nobody was interested
defcomg said:
It should work the same as Moto G5 plus but it seemed nobody was interested
Click to expand...
Click to collapse
I AM!
I've tried the following codes that you posted here:
Enable Camera 2 API
via editing the build.prop
Code:
persist.camera.HAL3.enabled=1
or
via terminal / shell
Code:
su persist.camera.HAL3.enabled 1
I've tried this code via terminal but returned as "Unknown ID" for the string.
Also, this string at the build.prop wasn't available, so I created, but with no sucess enabling raw.
If you want some files to test, I can help you out. Anyway, I'll look for any string related at the build.prop. If I have any sucess, I'll return here.
Martinezjpo said:
I AM!
I've tried the following codes that you posted here:
Enable Camera 2 API
via editing the build.prop
or
via terminal / shell
I've tried this code via terminal but returned as "Unknown ID" for the string.
Also, this string at the build.prop wasn't available, so I created, but with no sucess enabling raw.
If you want some files to test, I can help you out. Anyway, I'll look for any string related at the build.prop. If I have any sucess, I'll return here.
Click to expand...
Click to collapse
From terminal
Type su grant it permission if it ask
Then type setprop persist.camera.HAL3.enable 1
Reboot then in freedcam clear app data start it check in menu if it's on api2
defcomg said:
From terminal
Type su grant it permission if it ask
Then type setprop persist.camera.HAL3.enable 1
Reboot then in freedcam clear app data start it check in menu if it's on api2
Click to expand...
Click to collapse
The command worked. Camera2 API is now enabled and I was able to enable two raw modes: raw_sensor and raw10. Only raw10 "worked", as the other showed black only.
EDIT1: There are DNGs at the FreeDcam files, but when I've tried to open any, the Moto Files app crash repeatedly.
FreeDcam constantly crashes using the Camera2 API, and I couldn't take any pictures with raw enabled. It just freeze when I hit the trigger button and capture no image. It returns with "Error 4" when doesn't crash.
Also, the 2160p recording option was enabled, but didn't seem to work too. Maybe a tweak in the app would solve these problems?
Martinezjpo said:
The command worked. Camera2 API is now enabled and I was able to enable two raw modes: raw_sensor and raw10. Only raw10 "worked", as the other showed black only.
EDIT1: There are DNGs at the FreeDcam files, but when I've tried to open any, the Moto Files app crash repeatedly.
FreeDcam constantly crashes using the Camera2 API, and I couldn't take any pictures with raw enabled. It just freeze when I hit the trigger button and capture no image. It returns with "Error 4" when doesn't crash.
Also, the 2160p recording option was enabled, but didn't seem to work too. Maybe a tweak in the app would solve these problems?
Click to expand...
Click to collapse
Yeah there is a bug with Moto devices where the camera calibration matrix in the dng becomes invalid rendering it useless there is a workaround for that I'm on telegram @defcomk I'll forward you an apk to test
defcomg said:
Yeah there is a bug with Moto devices where the camera calibration matrix in the dng becomes invalid rendering it useless there is a workaround for that I'm on telegram @defcomk I'll forward you an apk to test
Click to expand...
Click to collapse
Maybe I can help you by testing whatever you're going to develope. ? Seems enabling camera 2 api is not enough for this device. Good luck with your work.
[email protected] said:
Maybe I can help you by testing whatever you're going to develope. ? Seems enabling camera 2 api is not enough for this device. Good luck with your work.
Click to expand...
Click to collapse
I got a g5 plus had the same bug anyway I just hardcoded the metadata that was incorrect all's well
defcomg said:
I got a g5 plus had the same bug anyway I just hardcoded the metadata that was incorrect all's well
Click to expand...
Click to collapse
What changes you made in metadata? Can you help me with that?
Martinezjpo said:
I AM!
I've tried the following codes that you posted here:
Enable Camera 2 API
via editing the build.prop
or
via terminal / shell
I've tried this code via terminal but returned as "Unknown ID" for the string.
Also, this string at the build.prop wasn't available, so I created, but with no sucess enabling raw.
If you want some files to test, I can help you out. Anyway, I'll look for any string related at the build.prop. If I have any sucess, I'll return here.
Click to expand...
Click to collapse
Is it for Moto G5 or G4
Update: Thanks to @MishaalRahman for the great summary article. More discussion there.
Update: Thanks to @GR0S for the app solution, available in this post
Update: Thanks to @doubleaykay for the magisk module, available in this post
I am no developer but I was researching the OP5 DCI-P3 calibration, saw that some international users were able to activate the calibration on their OP3T, and thought I would share what I have found so far. Long story short, this probably works if your device is a OP3T with the S6E3FA5 display panel, but not if your device is a OP3T with the S6E3FA3 display panel.
Note: I believe this changes the actual calibration for the "Default" selection in the display settings, but you will not see the name "Default" change to "DCI-P3"
Sources:
Credit to @rquandt on Twitter for getting the ball rolling: Tweet
Proposed command-line solution from ITHome: Link
Proposed modified apk solution from OnePlusBBS: Link
More discussion from OnePlusBBS: Link
Even longer thread (86 pages) from OnePlusBBS: Link
Even longer thread (583 pages) from OnePlusBBS: Link
This post to Weibo discusses S6E3FA5 vs S6E3FA3 compatibility: Post
Procedure:
Find out if your display panel is compatible (looking for S6E3FA5)
Install AIDA64 and check Display > "Panel ID"
(optional) I also checked to see if the profiles were available on my OP3T running Oxygen OS Open Beta 9 using a file explorer.
Open Terminal Emulator on your phone and enter these two commands:
Code:
su
echo 1 > sys/devices/virtual/graphics/fb0/DCI_P3
The changes will revert to previous configuration on reboot, so this must be re-applied after reboot.
To revert changes
Open Terminal Emulator on your phone and enter these two commands:
Code:
su
echo 0 > sys/devices/virtual/graphics/fb0/DCI_P3
I'm on VertexOS and DCI-P3 profile is not available in said location. Will flash OB9 and report back.
---------- Post added at 03:53 PM ---------- Previous post was at 03:20 PM ----------
It works perfectly, no need to reboot. Looks great, think I will keep it for a while.
I have S6E3FA5. DCI-P3 file is available in it's location. Just tried on Freedom OS 4.1.6, and nothing. Phone switches back to sRGB after reboot... not sure how to actually confirm it's DCI-P3....
twoxa said:
I have S6E3FA5. DCI-P3 file is available in it's location. Just tried on Freedom OS 4.1.6, and nothing. Phone switches back to sRGB after reboot... not sure how to actually confirm it's DCI-P3....
Click to expand...
Click to collapse
You can immediately see the difference in color after issuing the command on Terminal Emulator, especially if sRGB is enabled. DCI-P3 is a lot more colorful, but not quite as the default calibration, which is borderline psychodelic. The selected calibration will still read "sRGB" though, as this new standard isn't officialy included in OP3T software. And yes, after a reboot, calibration will return either to standard values, or sRGB.
Yup got it now, thanks. Looks nice. Too bad it doesn't stick after reboot.
twoxa said:
Yup got it now, thanks. Looks nice. Too bad it doesn't stick after reboot.
Click to expand...
Click to collapse
Yup, that's a shame. Nothing a quick script in Tasker can't fix, though.
redsmith said:
You can immediately see the difference in color after issuing the command on Terminal Emulator, especially if sRGB is enabled.
Click to expand...
Click to collapse
Cool, sounds like it works even if you don't select "Default" before running the commands. Thanks!
redsmith said:
It works perfectly, no need to reboot. Looks great, think I will keep it for a while.
Click to expand...
Click to collapse
twoxa said:
Phone switches back to sRGB after reboot...
Click to expand...
Click to collapse
redsmith said:
after a reboot, calibration will return either to standard values, or sRGB.
Click to expand...
Click to collapse
I'll update the instructions accordingly. Thanks!
redsmith said:
Yup, that's a shame. Nothing a quick script in Tasker can't fix, though.
Click to expand...
Click to collapse
So i think it's useless for now!
Let's hope for a magisk module,maybe...
Still trying to see if there's a way to enable a setting to allow this to work on S6E3FA3 display panels.
Found this mention of a "OPScreenColorMode.java" configuration file on the OP3T but I can't find where that would be on the device.
I decompiled the Settings.apk and couldn't find the file, but I did see a mention of that synonym (as well as OPNightMode and OPReadingMode) inside "display_settings.xml":
Code:
<PreferenceScreen android:title="@string/oneplus_night_mode_enabled_op" android:key="oneplus_night_mode" android:fragment="com.oneplus.settings.better.OPNightMode" />
<PreferenceScreen android:title="@string/oneplus_reading_mode" android:key="oneplus_reading_mode" android:fragment="com.oneplus.settings.better.OPReadingMode" />
<PreferenceScreen android:title="@string/oneplus_screen_color_mode_title" android:key="screen_color_mode" android:fragment="com.oneplus.settings.better.OPScreenColorMode" />
Not sure where to go from here, though.
soccerwuedo5 said:
Not sure where to go from here, though.
Click to expand...
Click to collapse
It won't be there on not supported devices as there is a condition to remove that preference as shown in your attached screenshot.
Hi all,
I packaged this into a Magisk module for everyone to enjoy. It simply runs the provided command as part of the Magisk late_start service.
Here is a link to the GitHub repo: https://github.com/doubleaykay/DCI-P3_Enabler_OP3T. I have submitted it to the repo.
In the meantime, I have attached a zip you can install in Magisk.
I have tested it on my own device and it works perfectly!
Enjoy!
Edit: Yes, this allows it to persist through reboots!
nicesoni_ash said:
It won't be there on not supported devices as there is a condition to remove that preference as shown in your attached screenshot.
Click to expand...
Click to collapse
Thanks for taking a look! It seems the guys on OnePlusBBS have overridden that removal for compatible devices to add the menu items back in on the OP3T. It's over my head but maybe someone can replicate their efforts here.
Root required
Will add srgb button tomorrow
GR0S said:
Root required
Will add srgb button tomorrow
Click to expand...
Click to collapse
I have an A3 display and I still see a change when using DCI-P3!
vampire36 said:
I have an A3 display and I still see a change when using DCI-P3!
Click to expand...
Click to collapse
That's awesome! I tried the app and saw no change but maybe there's some other variable involved.
Magisk module isn't working for me, but the command is
Navi44 said:
Magisk module isn't working for me, but the command is
Click to expand...
Click to collapse
You could at least be more specific and include OxygenOS version and Magisk version for him/her to compare. . .
I have the A5 panel on my 3T, and magisk module isn't working for me. Currently running FreedomOS 2.11.2 with Blu_Spark kernel r151 and Magisk v13. Let me know if there's any other information I should add.
tzbigworm said:
I have the A5 panel on my 3T, and magisk module isn't working for me. Currently running FreedomOS 2.11.2 with Blu_Spark kernel r151 and Magisk v13. Let me know if there's any other information I should add.
Click to expand...
Click to collapse
That is bizzare, maybe it's an issue with Magisk v13. Could you post your Magisk log?
I am using Magisk v12, the stable release, and it works perfectly fine for me.... odd.
Could we have more people test the Magisk module to make sure it works?
GR0S said:
Root required
Will add srgb button tomorrow
Click to expand...
Click to collapse
This works like a charm! The colours take a bit of getting used to though.
Guide to Install Android Pie on your Mi5s
1. Download this ZIP and copy the .img files from the zip to your phone.
2. In twrp wipe system, data ,cache and dalvik.
3. Flash the boot.img to the boot partition and the vendor.img to the vendor partition.
4. Download this ZIP and copy the .img file from inside the zip to your phone and flash it to system
5. Download and copy the zips to your phone and flash it in the right order (from 1 to 3)
ZIP 1 -ZIP 2 -ZIP 3
6. Download and copy the zips to your phone and flash it
Navbar disabler -Lag fix
7. Flash this Kernel
8. Flash Magisk 16.7
9. Boot ROM
10. Install this APKs and give manually "Data transfer tool" all permission
11. Reboot device and finish after that the setup
12. To fix little UI bugs change display size to small in the settings
13. Recommend Kernel Settings Look here
or when you want you can also use his tipp
14. Magisk Module for some small fixes (Mi5s Pie GSI Props )
Add Digital Wellbeing from Google to your settings
Thanks to:
@MZO
@kdrag0n
@erfanoabdi
@Pho3nX
@brigio345
Bugs:
SeLinux Status : Permissive
Flashing Kernel causes the lose of the mtp function but is still recommend because it fixes pretty much bugs.
Button backlight
VoLTE
Sometimes slow download in the PlayStore
A warning message after each reboot (pleas ignore it)
Status updates:
I am working at the moment on a button light fix for the Mi5s.
A working fix for the Mi A1 I have already done :good:
F.A.Q.
How to swap buttons?
Use this App or this App
How to activate double tap to wake?
Use Kernel Adiutor
Which modded Gcam I can use?
All versions you used in previous Android version should work fine in Pie also but maybe you want to give this one a try
What's about sound mods?
Try this version of Viper (Magisk)
Tested and working Magisk Modules:
Blobmoji
Busybox for Android NDK
Cloudflare DNS
Energized Protection
Google DNS
Init.d Injector
MagiskHide Props Config
Mi5s Pie GSI Props
Sysconfig Patcher
xmlpak – a road to vendor apps
did the navigation from Pie is present in this ROM?
rizahakam said:
did the navigation from Pie is present in this ROM?
Click to expand...
Click to collapse
When you don't flash the navbar disabler (step 6) yes
jigs4wkiller said:
When you don't flash by step 6 the navbar disabler yes
Click to expand...
Click to collapse
sorry if it's confusing you, but I mean the gesture from Pie. so if I want gesture from Pie, did I flash the disable navbar or not?
also if I want return to on screen button, I can flash the same file again or not?
rizahakam said:
sorry if it's confusing you, but I mean the gesture from Pie. so if I want gesture from Pie, did I flash the disable navbar or not?
also if I want return to on screen button, I can flash the same file again or not?
Click to expand...
Click to collapse
Tap on the navbar link.
The one zip enable it and the other disable the on screen navigation from Pie.
Good tutorial :good:
And step 13, thermal_mod is useful enough for daily usage
-------------
BTW, is fingerprint will reset after reboot?
fim5646 said:
BTW, is fingerprint will reset after reboot?
Click to expand...
Click to collapse
fingerprint survies reboot
jigs4wkiller said:
fingerprint survies reboot
Click to expand...
Click to collapse
Okay,I know what I did wrong, I didn't complete Pixel Setup due to Internet problem.
I will try to install again. Thanks:good:
Updated F.A.Q.
Update Bug list
Maybe it's a bit early to ask that, but how's battery life in Pie? Do you guys recommend for daily use?
LordStanley said:
Maybe it's a bit early to ask that, but how's battery life in Pie? Do you guys recommend for daily use?
Click to expand...
Click to collapse
It looks alright so far but yes it's a bit early.
I think it's stable enough for daily use but always make a backup.
Wow! Amazing job man, I will try this asap! Will be back with feedback. Thank you so much!
So.... Every function works? Gcam? Many thanks for this rom!
if I want to change the kernel when pepsi kernel been updated, how to change the kernel?
usually I will dirty flash the rom, but for this one I don't know which one need to be flash again
rizahakam said:
if I want to change the kernel when pepsi kernel been updated, how to change the kernel?
usually I will dirty flash the rom, but for this one I don't know which one need to be flash again
Click to expand...
Click to collapse
Reflash the boot.img from step 3 and after that flash the kernel
danbrown162 said:
So.... Every function works? Gcam? Many thanks for this rom!
Click to expand...
Click to collapse
Most of the functions are working and yes you can use any modded gcam
I made a dark themed GCam mod with some little tweaks. It's based on the latest Arnova8G2 Google Camera mod. Maybe someone want to give it a try. https://drive.google.com/file/d/1c8Hg-T8lLf6lED9noB_36TCbd3kX-nvJ/view?usp=sharing
Add digital wellbeing from Google to your settings app.
Just install this apk.
Now i use joneplus tools + oneplus mod dialer for call recording on Android 13.
I miss a spam call blocker...
Any solution to have the automatic call recording function AND spam call blocker with Android 13?
Thanks.
Try using the Google Dialer with the Pixelify Magisk Module.
ChIP_83 said:
Now i use joneplus tools + oneplus mod dialer for call recording on Android 13.
I miss a spam call blocker...
Any solution to have the automatic call recording function AND spam call blocker with Android 13?
Thanks.
Click to expand...
Click to collapse
Hey there, Can you please explain how did you managed to use call recording on Android 13? I have Oneplus 8 pro IN2025 and can't find solution to make Call Recording work after the upgrade to Android 13 from 12
yaniv.s said:
Hey there, Can you please explain how did you managed to use call recording on Android 13? I have Oneplus 8 pro IN2025 and can't find solution to make Call Recording work after the upgrade to Android 13 from 12
Click to expand...
Click to collapse
I solved it like this:
I installed joneplus tools (from the playstore I know that it doesn't work anymore so it must be installed from the apk - in reality I had already installed it)
set the permissions via ADB as required by the various guides (remember to enable Disable Permission Monitoring in developper options)
loaded the modified oneplus dialer
doing so everything works as before, with the difference that I no longer have the screen where I can change the recording options in the dialer, but the recordings still start automatically (I think it is due to the fact that the "modified dialer" goes to "modify " call screen only.
ChIP_83 said:
I solved it like this:
I installed joneplus tools (from the playstore I know that it doesn't work anymore so it must be installed from the apk - in reality I had already installed it)
set the permissions via ADB as required by the various guides
loaded the modified oneplus dialer
doing so everything works as before, with the difference that I no longer have the screen where I can change the recording options in the dialer, but the recordings still start automatically (I think it is due to the fact that the "modified dialer" goes to "modify " call screen only.
Click to expand...
Click to collapse
Thank you sooo much !!! The modified app was the part missing
ChIP_83 said:
I solved it like this:
I installed joneplus tools (from the playstore I know that it doesn't work anymore so it must be installed from the apk - in reality I had already installed it)
set the permissions via ADB as required by the various guides (remember to enable Disable Permission Monitoring in developper options)
loaded the modified oneplus dialer
doing so everything works as before, with the difference that I no longer have the screen where I can change the recording options in the dialer, but the recordings still start automatically (I think it is due to the fact that the "modified dialer" goes to "modify " call screen only.
Click to expand...
Click to collapse
hi ChiP_83,
about the ADB command in step #2, is it
"/adb shell settings put global op_voice_recording_supported_by_mcc 1"?
thanks in advance
This was working on android 11
ADB command with joneplus tools installed
adb shell pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS
ADB command without installing joneplus tools
adb shell settings put global op_voice_recording_supported_by_mcc 1
Hi all. I just tied to set call recording, install joneplus tools, and granted write through adb, install modified dialer, but no luck, call recording not visible. If i try update my regular phone app, looks like it finished with success, but can't find same version number..
Well new android version IN2025_11_F62 and no call recorder again.. any solutions?