Disable camera shutter sound in Lineage OS without root? - Android Q&A, Help & Troubleshooting

I recently installed Lineage OS, and everything's great -- but the camera shutter sound is really annoying. It's there when the phone is on silent, it's there in other camera apps, it's even there in screenshots. I've tried disabling the sound through the camera menu but it's still there.
I've looked at several websites:
https://www.reddit.com/r/LineageOS/comments/5xcrtx/any_way_to_disable_camera_shutter_sound/
https://forum.xda-developers.com/showthread.php?t=2348012
https://forums.oneplus.com/threads/...neplus2-discussions-downloads.427906/page-334
https://forum.xda-developers.com/ga...sable-camera-sound-fix-battery-t1079136/page2
The problem in most of these is that they require root. Now I really, really don't want to root my phone.
I've enabled root access for adb, and I was wondering if there's some way I could use adb to disable the sound. (the last link had that option, but didn't work)
Now, some of the other pages I visited had something similar to deleting a camera_sound.ogg sound. Is there a way to do that using adb? Or just any other way that just doesn't having me root my phone?

Using TWRP to Disable Camera Shutter Sound Without Root
satvik2101 said:
...Lineage OS, and everything's great -- but the camera shutter sound is really annoying...
The problem in most of these is that they require root. Now I really, really don't want to root my phone.
I've enabled root access for adb, and I was wondering if there's some way I could use adb to disable the sound...Or just any other way that just doesn't having me root my phone?
Click to expand...
Click to collapse
Welcome to XDA.
You did not mention your device model & LineageOS version which is always important troubleshooting info.
I presume you have TWRP recovery installed. I just tested this on my S3 i9300 running Lineage 14.1 & TWRP 3.2.1-0:
TWRP > Mount > make sure System is selected > Home > Advanced > File Manager > navigate to /system/media/audio/ui/ > tap on camera_click.ogg > Rename File > camera_click.ogg.old > tap the blue confirm checkmark button > Swipe to Confirm > Reboot System > test camera shutter sound when taking a photo.
The second screenshot is the result as seen in a rooted phone using a root enabled file manager.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can do the same with VideoRecord.ogg if you don't want a notifying sound when you start recording a video and to VideoStop.ogg which notifies when you stop recording.
***
"...I've enabled root access for adb" - I have root enabled but curious: how did you do that w/o root?
There is this method using adb but from what I read it requires root: https://forum.xda-developers.com/showpost.php?p=10745756&postcount=5 and it's exactly what TWRP is doing above as seen in the recovery_log:
mv /system/media/audio/ui/camera_click.ogg /system/media/audio/ui/camera_click.ogg.old
May I ask why you don't want to root your phone?
BTW instead of copy/paste the URL of an entire page you can right-click the relevant post's number in the top part & copy it's direct link (permalink). This post's #2 for example.
Please report back if it worked for you or not.
***

Thanks a ton man! This worked perfectly.
I didn't know we had/should post model number or Lineage version ( I created an XDA account just for this question). BTW it's an Mi4i and Lineage 14.1
I'm a total android noob -- the only reason I flashed a custom ROM was because the new MIUI update made it really slow and formatting didn't do anything -- so I don't know if what I did actually enabled root access for adb, but here is the screenshot
The reason I don't want to root my phone is because I don't want to take any unnecessary risks.. Even while flashing the Custom ROM I screwed up a couple of times and it took me 3 hours and right now I really don't have much time to spare.
Thanks man.

Works for HTC One M9 w/ AICP 14.0 (Pie)
curiousrom said:
Welcome to XDA.
You did not mention your device model & LineageOS version which is always important troubleshooting info.
I presume you have TWRP recovery installed. I just tested this on my S3 i9300 running Lineage 14.1 & TWRP 3.2.1-0:
TWRP > Mount > make sure System is selected > Home > Advanced > File Manager > navigate to /system/media/audio/ui/ > tap on camera_click.ogg > Rename File > camera_click.ogg.old > tap the blue confirm checkmark button > Swipe to Confirm > Reboot System > test camera shutter sound when taking a photo.
The second screenshot is the result as seen in a rooted phone using a root enabled file manager.
View attachment 4515572 View attachment 4515576
You can do the same with VideoRecord.ogg if you don't want a notifying sound when you start recording a video and to VideoStop.ogg which notifies when you stop recording.
***
"...I've enabled root access for adb" - I have root enabled but curious: how did you do that w/o root?
There is this method using adb but from what I read it requires root: https://forum.xda-developers.com/showpost.php?p=10745756&postcount=5 and it's exactly what TWRP is doing above as seen in the recovery_log:
mv /system/media/audio/ui/camera_click.ogg /system/media/audio/ui/camera_click.ogg.old
May I ask why you don't want to root your phone?
BTW instead of copy/paste the URL of an entire page you can right-click the relevant post's number in the top part & copy it's direct link (permalink). This post's #2 for example.
Please report back if it worked for you or not.
***
Click to expand...
Click to collapse
Thanks a lot! Even though the camera app I use (HTC Camera) has an option for disabling shutter sound, it wouldn't matter for video recording. Video record sound was always there. Renamed VideoRecord.ogg file as you pointed and the problem is solved, no more video recording sound (shutter sound is still there if I don't disable it, but this is not recorded).

satvik2101 said:
I recently installed Lineage OS, and everything's great -- but the camera shutter sound is really annoying. It's there when the phone is on silent, it's there in other camera apps, it's even there in screenshots. I've tried disabling the sound through the camera menu but it's still there.
I've looked at several websites:
https://www.reddit.com/r/LineageOS/comments/5xcrtx/any_way_to_disable_camera_shutter_sound/
https://forum.xda-developers.com/showthread.php?t=2348012
https://forums.oneplus.com/threads/...neplus2-discussions-downloads.427906/page-334
https://forum.xda-developers.com/ga...sable-camera-sound-fix-battery-t1079136/page2
The problem in most of these is that they require root. Now I really, really don't want to root my phone.
I've enabled root access for adb, and I was wondering if there's some way I could use adb to disable the sound. (the last link had that option, but didn't work)
Now, some of the other pages I visited had something similar to deleting a camera_sound.ogg sound. Is there a way to do that using adb? Or just any other way that just doesn't having me root my phone?
Click to expand...
Click to collapse
why not root & change the ogg file then unroot.

Related

[HowTo] Activate Adoptable Storage on Marshmallow (with Xposed Framework)

Hey Guys,
in this Tutorial I will show you how to activate the Adoptable Storage function on the M4 Aqua with the help of the Xposed Framework.
Attention: Me or not anyone else is responsible if you proceed with this. We do not take any responsibility for any bricked phones, dead sd cards, void warranties or anything else.
At first let's talk about what we need:
- Android 6.0.1 (I used the Customized FR version. (Build R5C))
- Xposed Framework Installer: Download
- Xposed SDK23 ZIP File (I used v86): Download
- (Minimal) ADB: Download
- Unlocked Bootloader, ROOT and TWRP
So let's go:
1. Unlock your Bootloader and install TWRP like described here. (It may works also like described here without unlock your Bootloader but I didn`t test this.)
2. Install Root like described here.
3. Install the Xposed Framework Installer.
4. Boot into your TWRP. (Press PowerButton + Vol- Button to start your Phone into TWRP)
5. Connect your Phone with USB on your PC. (Make sure you've got all Drivers installed. You will find them in the Flashtool install location.)
6. Move the Downloaded Xposed ZIP to the install location of your (Minimal) ADB
7. Open an Shell were you've installed your (Minimal) ADB
8. Type the following:
Code:
adb devices
If your Phone is now listed you can continue
Code:
adb shell
Now you should see a command line like this: ~#
Then Type:
Code:
mount -w /dev/block/platform/soc.0/7824900.sdhci/by-name/system /system
mount -w /dev/block/platform/soc.0/7824900.sdhci/by-name/userdata /data
mount -w /dev/block/platform/soc.0/7824900.sdhci/by-name/cache /cache
If you become an response that your Resource is busy don't wory. This means it's already mounted.
Now type this:
Code:
twrp sideload
adb sideload xposed-v*-sdk23-arm64.zip
For the * use the version number of your Downloaded Xposed ZIP.
If this is complete type:
Code:
adb reboot
Now it may takes up to 10-20 Minutes until your Phone is booted the first time with Xposed.
After Boot open your Xposed Installer App and go to "Framework". It should look like this, if it is successfully installed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
9. Download the SystemUI Patcher for Lollipop+
10. Acitvate it in Xposed App (don't wonder if in the screenshot is another Module... you don't need this):
Open the Xposed Installer App --> Go to "Modules" --> Tick the Checkbox
11. Open the SystemUI Patcher App, scroll down, select "Enable adoptable storage" and restart your phone:
11. Insert your SD-Card and select "use it as internal storage". (I can't make a Screenshot of this by myself because I've done this before making this Tutorial):
12. Congratulations you've got successfully enabled adoptable storage on your M4 Aqua.
I tested it with the E2303. But it should work with any Version.
Special thanks to @depressed_ for the tipp with the SystemUI Patcher in this post.
And to @alby_var for the Tutorial how to install Xposed on Android 5, because I used this for orientation.
Known Issues: (Everything I or anybody else found)
- Stock Camera App didn't work for me after doing this! .-. It says "Memory unavailable" (I use now the App CameraMX ... This works fine!)
- On your storage settings will be shown some wired Numbers. (See Screenshot(s))
What about some screen(s)? Does it work 100% without any mini errors? People were complaining about their storage. It showed them weird numbers.
Btw thx for mentioning me.
Is this the original android feature being enabled? I think this should work without many problems if it is from android...
Pls make some screen.. Thanks
Sent from my E2303 using XDA-Developers mobile app
Seems good but how can you deactivate it?
Obblet said:
Seems good but how can you deactivate it?
Click to expand...
Click to collapse
I think so. Just go in your Settings --> Storage --> Internal Storage --> Migrate Data --> After this go to your SD-Card --> "Format as Portable"
For the other things:
Disable the Module in the Xposed Installer App and Uninstall the Xposed Framework.
For root and TWRP I use to flash the Original FTF File. (May there is another way... I don't know)
If there's an way to (re)lock the Bootloader, you can do this too. I heard somewhere that there is an way to do this but I don't know how. Sorry.
DarkerJava said:
Is this the original android feature being enabled? I think this should work without many problems if it is from android...
Click to expand...
Click to collapse
I think so because everything looks like the original, but to tell you the truth I don't know this. But it works. :good:
Not working. Memory shows -245677 or somethink. And camera doesn't work...
MK99 said:
Not working. Memory shows -245677 or somethink. And camera doesn't work...
Click to expand...
Click to collapse
Look at the "Known Issues" in first Post.
Camera and installing apps don't work... Is it because of my slow SD Card or is it the common issue?
lukas1838 said:
I think so because everything looks like the original, but to tell you the truth I don't know this. But it works. :good:
Click to expand...
Click to collapse
Thank you for your answer...
Sent from my E2303 using XDA-Developers mobile app
lukas1838 said:
I think so because everything looks like the original, but to tell you the truth I don't know this. But it works. :good:
Click to expand...
Click to collapse
Huh, judging from the new pictures, it seems that it is similar to the adb function... not the real adoptable storage tool.
Obblet said:
Camera and installing apps don't work... Is it because of my slow SD Card or is it the common issue?
Click to expand...
Click to collapse
My camera isn't working too, but installing apps works fine.
lukas1838 said:
My camera isn't working too, but installing apps works fine.
Click to expand...
Click to collapse
So the installing apps error is my SD Card's speed problem? I'm planning to buy a Samsung evo+. will it work?
Obblet said:
So the installing apps error is my SD Card's speed problem? I'm planning to buy a Samsung evo+. will it work?
Click to expand...
Click to collapse
I've got an EVO+ so it should work when the speed is the problem
same here , camera doesnt work but the installing apps works peffectly
Yes, now everything works, and if you want a camera, download a different camera app.
can i uninstall system camera app ? and make another camera app as system app ?
lukas1838 said:
I think so because everything looks like the original, but to tell you the truth I don't know this. But it works. :good:
Click to expand...
Click to collapse
Well, since my E2306 pdated and at first boot running android 6 recognized my SD and enabled it by itself, I guess yes, this might be a stock rom's hidden (in your device) function.
whatsapp cant download image after activate adoptable storage
After using partition in sd card like this link
http://forum.xda-developers.com/m4-aqua/general/adoptive-storage-marshmallow-t3421828/page1
All work fine

Anyone have a guide for how to install V4A?

Hi,
Trying to install Viper4Android to transfer my good Profile files from my old Lenovo P2 to this new Poco F1, but I am unable to get V4A to work. I've tried to flash using magisk modules, both as a system app and user app but nothing works.
It always says abnormal status for the driver and the EQ does not change (except I get that notification crackling sound that I found the fix for here: https://forum.xda-developers.com/poco-f1/how-to/sound-distortion-issue-fixed-custom-t3891118)
Anyone know what might be the issue and what I might do to make it work?
EDIT: Running LineageOS 16, latest nightly build
Never had any issue with viper.
Im on miui stable 10.2.3..
I just flashed the latest viper and viper x hifi.. with audio sound mod. Both are magisk modules.. and are working fine..
How I made it work on my poco with the new app by pittvandewitt and MrWhite214:
Install Viper4AndroidFX via Magisk - select new > material > system app > no lib workaround
Reboot - do not open Viper yet.
Download new Viper app from https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Rename the downloaded apk to ViPER4AndroidFX.apk (might be case sensitive, didn't test)
Delete the existing apk from /system/priv-app/ViPER4AndroidFX
Move new apk where the deleted one was
Reboot
Give Viper storage permissions
Enjoy
If you get crackling during notifications, install the Notification Helper Remover and select to remove the library. Don't install AML since that seems to break bluetooth, at least for me.
Thanks for the answers, I will try them on later today! Forgot to mention that I am on the latest build of LineageOS 16.
stashcat said:
How I made it work on my poco with the new app by pittvandewitt and MrWhite214:
Install Viper4AndroidFX via Magisk - select new > material > system app > no lib workaround
Reboot - do not open Viper yet.
Download new Viper app from https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Rename the downloaded apk to ViPER4AndroidFX.apk (might be case sensitive, didn't test)
Delete the existing apk from /system/priv-app/ViPER4AndroidFX
Move new apk where the deleted one was
Reboot
Give Viper storage permissions
Enjoy
If you get crackling during notifications, install the Notification Helper Remover and select to remove the library. Don't install AML since that seems to break bluetooth, at least for me.
Click to expand...
Click to collapse
Well, that didnt work. Still "abnormal" status on driver
Ultimately tried to install too many times and corrupted my ROM so bluetooth and Wifi stopped working. Cleaninstalled my ROM now to try again if you have any other plan.
stashcat said:
How I made it work on my poco with the new app by pittvandewitt and MrWhite214:
Install Viper4AndroidFX via Magisk - select new > material > system app > no lib workaround
Download new Viper app from https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Delete the existing apk from /system/priv-app/ViPER4AndroidFX
Reboot
Enjoy
If you get crackling during notifications, install the Notification Helper Remover and select to remove the library. Don't install AML since that seems to break bluetooth, at least for me.
Click to expand...
Click to collapse
This worked for me on Havoc! After installing Notification Helper Remover (volume down option) I have no crackle and Bluetooth is working
what rom ur now stable beta custom ?!
Always install viper4 android from this thread https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
installing normally open request for root permissions then reboot automatically
maybe installing busybox NDK magisk will help you if u still have abnormal status hope that will help you solving your problem
its working here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
BTW Rom 9.3.14 beta with magisk 18.1
Antidote03 said:
what rom ur now stable beta custom ?!
Always install viper4 android from this thread https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
installing normally open request for root permissions then reboot automatically
maybe installing busybox NDK magisk will help you if u still have abnormal status hope that will help you solving your problem
its working here View attachment 4728362
BTW Rom 9.3.14 beta with magisk 18.1
Click to expand...
Click to collapse
sorry, forgot to mention that I run LineageOS 16 in the OP. Had a reply in a comment later that explained it but should add it in OP. I will try with busybox!
I've tried all different combinations explained in these threads without success...:
https://forum.xda-developers.com/apps/magisk/module-universal-deepbuffer-remover-t3577067
https://forum.xda-developers.com/poco-f1/help/soundmod-pie-t3868729/page3
https://forum.xda-developers.com/poco-f1/how-to/poco-f1-dolby-effect-t3840883
https://forum.xda-developers.com/android/apps-games/app-viper4android-fx-2-6-0-0-t3774651
Ive tried both ACP and AML, which ruins the BT functionality. Ive tried to change SELinux to permissive. Ive tried removing/renaming the sound files in vendor/lib/soundfx and vendor/lib64/soundfx. Ive tried to rename or delete audio_config.conf (or what it was called). Nothing works! The driver now says that it is fully working, but I am unable to get ANY media sound out of my bluetooth headphones (calls and notifications still work).
Removing ALL of these patches once again enables my BT headphones to play sound, so something must be wrong in the installation of either ACP, AML or V4A.
Found my solution below (from viper4android main thread):
Originally Posted by racerx002
I found that V4A and AptX don't get along. You can disable Bluetooth HD in developer settings and it might work, but then you are missing out on better sound, so it's kind of pointless.
Click to expand...
Click to collapse
That might indeed be the cause if this is also true for LDAC, since I use Sony MDR-1000x as headphones.
EDIT: Confirmed! LDAC and AptX was the problem. Hooked it up to a mobile speaker using BT and it worked wonders using SDC codec. This sucks but still nice that I (read racerx002) figured it out! Thanks a lot for the help! Here's hoping that someone will post a fix for LDAC/AptX!
EDIT: More specifically, it is not LDAC and AptX that is the problem. It is the "Bluetooth sample rate". LDAC streams at 96kHz, while v4a only supports up to 48kHz as of now. Lowering to 48kHz in developer options instantly kicked in the viper4android FX!
Important, have had some problems with v4a for a while. Removing both ACP and AML fixed it for me
hugolol said:
Important, have had some problems with v4a for a while. Removing both ACP and AML fixed it for me
Click to expand...
Click to collapse
Hmm, I too couldn't get it working (with aptx enabled), but both are now running together. I have ViPER4Android FX Legacy Materialized. Settings at install using volume rocker: select new > material > system app > can't remeber the last one, but I chose the recommended.
I also flashed this fix for notifications. I then disabled aptx and enabled V4A master power, everything worked. Then I re-enabled aptx and V4A still works.
However, Aptx OFF(!) sounds better, clearer once I changed clarity settings up a couple of notches
reg66 said:
Hmm, I too couldn't get it working (with aptx enabled), but both are now running together. I have ViPER4Android FX Legacy Materialized. Settings at install using volume rocker: select new > material > system app > can't remeber the last one, but I chose the recommended.
I also flashed this fix for notifications. I then disabled aptx and enabled V4A master power, everything worked. Then I re-enabled aptx and V4A still works.
However, Aptx OFF(!) sounds better, clearer once I changed clarity settings up a couple of notches
Click to expand...
Click to collapse
Oh, thanks! I will try that!
Do you want to share you v4a settings once set up? Would be interesting to see
-install magisk debloater module
-reboot to system
-terminal
-type 'su' to get super user
-type 'debloat'
- u'll get a list
-type 2 for system priv-app
-now find out any kind of equalizer
-debloat it by typing it no
-flash v4a on magisk
-flash audio modification library
-reboot to system
markmywordz said:
-install magisk debloater module
-reboot to system
-terminal
-type 'su' to get super user
-type 'debloat'
- u'll get a list
-type 2 for system priv-app
-now find out any kind of equalizer
-debloat it by typing it no
-flash v4a on magisk
-flash audio modification library
-reboot to system
Click to expand...
Click to collapse
Not audio modification library, audio compatibility patch and use the notification helper to remove the library with the volume down button. AML isn't required and breaks Bluetooth audio

[Q][ROM][Treble] Treble Zoom

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- = Treble Zoom = -​
This custom ROM based on Havoc-OS 3.5.
Prerequisites - bootloader must be unlocked, clean Stock firmware and TWRP must be installed.
What's done:
- integrated GAPPS (Play Market, Chrome, Google Dialer, Messages, Contacts, etc.), but nothing extra. YouTube has been removed because I use YouTube Vanced);
- installed Nova Launcher (I recommend using it as the main one), RootExplorer, Asus File Manager (for simple tasks), Asus Gallery, AdAway ads blocker, Motor Command Center 2;
- integrated Moto camera from the latest firmware draining. Fully working with the work of all camera modules! In addition the best, in my opinion, for this ROM and our phone Google Camera mod;
- working Adaptive Brightness;
- cleaned up and made the system a little bit easier.
Installation Instruction
1. Download the Project Treble system image archive. Unpack the archive and copy the ROM image to an external SDCard.
2. Copy to external SD Card Magisk Installer https://github.com/topjohnwu/Magisk (latest version for today Magisk v20.4), Disable_Dm-Verity_ForceEncrypt https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 (latest version for today Disable_Dm-Verity_ForceEncrypt_03.04.2020 https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip ) and Permissiver_v4 (see attachments)
3. Reboot in TWRP and go to the "Wipe" tab, "Advanced Wipe" and select Dalvik, System, Data, and then go back two steps back and do a "Swipe Factory reset".
4. Install the Treble Zoom system image. In the "Install" tab in the lower right corner click "Install image" and select ROM Image. A window will open in which you should select partition "System Image" in which the image where to be installed. Swipe for confirm flash.
5. When the installation is complete, go to "Wipe" and perform a "Format Data".
6. Install the Magisk.zip, Disable_Dm-V_ForceEncrypt.zip and Permissiver_v4.zip. Reboot into the system and make the settings, use the Project Treble working system.
The first launch will be a bit long, don't worry and be happy!
Noticed problems on Treble Zoom - Does not pass SafetyNet check (ctsProfile: false; basicIntegrity: true). On Google Play, your device is not certified, but applications are installed and updated. Wired headphones are plugged in. When connected, the Bluetooth headset in the Dialer application works, but when listening to audio, video, YouTube is not.
Fingerprint Unlocking by fingerprint is implemented for scanners on the back of the phone. This problem can be corrected in the following way:
Connect the device to your PC and enter the following commands
Code:
adb shell
su
setprop persist.sys.fp.fod.location.X_Y 450,1760
setprop persist.sys.fp.fod.size.width_height 194,194
reboot
A green circle will appear in the display of your device, which is responsible for your fingerprint.
Niiiiice!!! I will try it ?
It Is Android 10?? You have some screenshot??
Does the fingerprint under the display work with this ROM?
Honzule89 said:
It Is Android 10?? You have some screenshot??
Click to expand...
Click to collapse
Yes, it's Android 10.
No screenshots. It's like Andriod 10.
Honzule89 said:
Does the fingerprint under the display work with this ROM?
Click to expand...
Click to collapse
Unlocking by fingerprint is implemented for scanners on the back of the phone.
Moto Zoom has a fingerprint under the display, which means that this reader will be inoperative and the phone can only be unlocked with a gesture or pin. It is a great pity. I will not install this ROM. But still great work
Honzule89 said:
Moto Zoom has a fingerprint under the display, which means that this reader will be inoperative and the phone can only be unlocked with a gesture or pin. It is a great pity.
Click to expand...
Click to collapse
This is GSI. This is a basic image of the firmware, not for a concrete model. Are you ready to donate for Moto Oe Zoom specific firmware development?
Honzule89 said:
I will not install this ROM.
Click to expand...
Click to collapse
The choice is yours. No one is forcing anyone. It's just that up until now it hasn't been possible to get a working system on Android 10.
After the flashes I get this:
Failed to mount '/system's (Invalid argument)
After I unpack the image zip, I rename to .img, maybe that's why, help me please...
ilia3367 said:
Yes, it's Android 10.
No screenshots. It's like Andriod 10.
Click to expand...
Click to collapse
You're truly incredible, thank-you SOOOOOO much for your work. :laugh:
It's amazing that unofficial development is an entire OS version better than OEM work! :good:
Hi,
nice job....i would donate for development....fix bluetooth?
giar72 said:
....fix bluetooth?
Click to expand...
Click to collapse
I tried to fix it, but I couldn't...
sorry...
Hell yeah, nice work. Probably not going to install it since I rely on Google pay and Bluetooth headphones regularly, but it's nice to finally see some roms for this device.
problem help please
ilia3367 said:
- = Treble Zoom = -​
This custom ROM based on Havoc-OS 3.5.
Prerequisites - bootloader must be unlocked, clean Stock firmware and TWRP must be installed.
What's done:
- integrated GAPPS (Play Market, Chrome, Google Dialer, Messages, Contacts, etc.), but nothing extra. YouTube has been removed because I use YouTube Vanced);
- installed Nova Launcher (I recommend using it as the main one), RootExplorer, Asus File Manager (for simple tasks), Asus Gallery, AdAway ads blocker, Motor Command Center 2;
- integrated Moto camera from the latest firmware draining. Fully working with the work of all camera modules! In addition the best, in my opinion, for this ROM and our phone Google Camera mod;
- working Adaptive Brightness;
- cleaned up and made the system a little bit easier.
Installation Instruction
1. Download the Project Treble system image archive. Unpack the archive and copy the ROM image to an external SDCard.
2. Copy to external SD Card Magisk Installer https://github.com/topjohnwu/Magisk (latest version for today Magisk v20.4), Disable_Dm-Verity_ForceEncrypt https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 (latest version for today Disable_Dm-Verity_ForceEncrypt_03.04.2020 https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip ) and Permissiver_v4 (see attachments)
3. Reboot in TWRP and go to the "Wipe" tab, "Advanced Wipe" and select Dalvik, System, Data, and then go back two steps back and do a "Swipe Factory reset".
4. Install the Treble Zoom system image. In the "Install" tab in the lower right corner click "Install image" and select ROM Image. A window will open in which you should select partition "System Image" in which the image where to be installed. Swipe for confirm flash.
5. When the installation is complete, go to "Wipe" and perform a "Format Data".
6. Install the Magisk.zip, Disable_Dm-V_ForceEncrypt.zip and Permissiver_v4.zip. Reboot into the system and make the settings, use the Project Treble working system.
The first launch will be a bit long, don't worry and be happy!
Noticed problems on Treble Zoom - Does not pass SafetyNet check (ctsProfile: false; basicIntegrity: true). On Google Play, your device is not certified, but applications are installed and updated. Wired headphones are plugged in. When connected, the Bluetooth headset in the Dialer application works, but when listening to audio, video, YouTube is not.
Fingerprint Unlocking by fingerprint is implemented for scanners on the back of the phone. This problem can be corrected in the following way:
Connect the device to your PC and enter the following commands
Code:
adb shell
su
setprop persist.sys.fp.fod.location.X_Y 450,1760
setprop persist.sys.fp.fod.size.width_height 194,194
A green circle will appear in the display of your device, which is responsible for your fingerprint.
Click to expand...
Click to collapse
so i tried to install the rom everything wwent well untill it kept booting to twrp then installed again and now it wont boot at all when plugged in it only lights up the moto sign on the back what can i do?
forgot to mention
death1426 said:
so i tried to install the rom everything wwent well untill it kept booting to twrp then installed again and now it wont boot at all when plugged in it only lights up the moto sign on the back what can i do?
Click to expand...
Click to collapse
i think i accidentally hit boot on slot b on twrp if so how can i fix this if it wont boot into bootloader?
To load into slot A, execute the command:
fastboot --set-active=a
Does it still has the moto shortcuts? Like alsways on display and the flashlight gesture?
There is a 3.8 version in the Havoc-os 3.5 link, can I flash it on One Zoom?...
thirdphotographer said:
There is a 3.8 version in the Havoc-os 3.5 link, can I flash it on One Zoom?...
Click to expand...
Click to collapse
This ROM is not the original GSI Havoc-OS image.

How To Guide auto call recording no root

Hello, I have a realme gt2 pro global version with google dialer.
Today, I found the oppo dialer mod, which can use call recording (no root) for oneplus and realme device.
How to use:
1. Install app
2. Set app to call system app.
3. force stop google dialer and turn off it (or can use adb to uninstall it easily).
4. While call or recive a call, choose call recording fuction.
To active auto call recording, I cant find the opition, but I can find the way (may be right or wrong) but u can try. It is use call recording fuction for 15 calls recently and app will be ask you want to use auto recording and u can select auto call recording.
Hope it’s work to you. Sorry for my bad english.
App is working but unfortunately I don't have the option to record calls.
Here
https://forum.xda-developers.com/t/oppo-dialer-oppo-message-app-100-working.4429737/post-86895379
Message app is included additionally
This worked for me:
Enable Native Call Recording + OP Stock Dialer on OnePlus 10 Pro
Hi guys, Just upgraded from OP7T to OP10 Pro as a European user. Call recording functionality does not come with the device here. Had native call recording enabled on my OP7T through jOnePlus Tools and the likes. Jtools Oneplus does not install...
forum.xda-developers.com
Instead of using JOneplus Tool and give it the secure settings permission I directly executed the adb command
Code:
adb shell settings put global op_voice_recording_supported_by_mcc 1
To document my current setup I attach the apps I'm currently using for call recording.
After 15(?) calls the setting to activate auto call recording can be opened. Unfortunately I'm not able to open the setting once again.
Sometimes the call UI of the contacts app is on top and a manual switch to the separately installed UI (com.android.incallui_13.6.6-13006006_minAPI30(nodpi)_apkmirror.com.apk) is required.
Oneplus-call-recorder.apk only changes the setting
Code:
op_voice_recording_supported_by_mcc
so recording can be enabled/disabled.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You need to execute adb command to enable Oneplus-call-recorder.apk by granting permission whereby an instruction appears on first start.
Don't forget to set contacts as default dialing app in Android settings.
TorstenH said:
To document my current setup I attach the apps I'm currently using for call recording.
After 15(?) calls the setting to activate auto call recording can be opened. Unfortunately I'm not able to open the setting once again.
Sometimes the call UI of the contacts app is on top and a manual switch to the separately installed UI (com.android.incallui_13.6.6-13006006_minAPI30(nodpi)_apkmirror.com.apk) is required.
Oneplus-call-recorder.apk only changes the setting
Code:
op_voice_recording_supported_by_mcc
so recording can be enabled/disabled.
View attachment 5779573
You need to execute adb command to enable Oneplus-call-recorder.apk by granting permission whereby an instruction appears on first start.
Don't forget to set contacts as default dialing app in Android settings.
Click to expand...
Click to collapse
Hello,
After the last update IN2023_11_F.62, Call Recording no longer works. Do you have an update to your solution?
It worked until yesterday when I made the mistake of doing the update.
What phone?
criszz said:
What phone?
Click to expand...
Click to collapse
OnePlus 8 Pro​
TorstenH said:
To document my current setup I attach the apps I'm currently using for call recording.
After 15(?) calls the setting to activate auto call recording can be opened. Unfortunately I'm not able to open the setting once again.
Sometimes the call UI of the contacts app is on top and a manual switch to the separately installed UI (com.android.incallui_13.6.6-13006006_minAPI30(nodpi)_apkmirror.com.apk) is required.
Oneplus-call-recorder.apk only changes the setting
Code:
op_voice_recording_supported_by_mcc
so recording can be enabled/disabled.
View attachment 5779573
You need to execute adb command to enable Oneplus-call-recorder.apk by granting permission whereby an instruction appears on first start.
Don't forget to set contacts as default dialing app in Android settings.
Click to expand...
Click to collapse
Does this still work on your OnePlus 10 Pro, after all the updates that has found place since you wrote this post?
If yes, then I am also wondering if this is the correct order, install all the .apk files, then executing this command:
adb shell settings put global op_voice_recording_supported_by_mcc 1
Thanks a lot.
I have the same problem with ONE PLUS 8 PRO, I cant record,
I dont know because the mobile update without permission.
This morning the mobile was reboot and updated
violgore01 said:
I have the same problem with ONE PLUS 8 PRO, I cant record,
I dont know because the mobile update without permission.
This morning the mobile was reboot and updated
Click to expand...
Click to collapse
It's because of the update and the country restrictions, but in the previous versions I managed to activate the call recording function with the help of the above utility and the installation of com.android.incalli provided by @TorstenH which is also above in the thread.
I hope that someone here who knows better will find an updated solution.
I caaaannnnnn
from adb shell install
adb install -d "c:\APK\Phone_InCallUI.apk"
And now I can record
Off course I have installa jOne plus tools
update: If reboot, then lost the record option
update2
C:\Users\vssx>adb install -d Z:\APK\Phone_InCallUI.apk
Performing Streamed Install
Success
What is performing streamed install?
violgore01 said:
I caaaannnnnn
from adb shell install
adb install -d "c:\APK\Phone_InCallUI.apk"
And now I can record
Off course I have installa jOne plus tools
update: If reboot, then lost the record option
update2
C:\Users\vssx>adb install -d Z:\APK\Phone_InCallUI.apk
Performing Streamed Install
Success
What is performing streamed install?
Click to expand...
Click to collapse
If you explain in more detail which Phone_InCallUI.apk (Z:\APK\Phone_InCallUI.apk)
Performing Streamed Install????
Maybe we, the most uninitiated, will understand
This is the file, it is in other topics of this forum.
I have used it before
But when I reboot the phone.. I lost the option of record
violgore01 said:
This is the file, it is in other topics of this forum.
I have used it before
But when I reboot the phone.. I lost the option of record
Click to expand...
Click to collapse
Anyway, in Oxygen 13, jOne plus tools can no longer be installed. So your option is not applicable at least to me.
Thank you!
iulianteodor said:
Anyway, in Oxygen 13, jOne plus tools can no longer be installed. So your option is not applicable at least to me.
Thank you!
Click to expand...
Click to collapse
I have Oxygen 13 too , but I have and older version of jOneplus tools, I think previous version, not the last
The last version have a problems and incompatibilities
iulianteodor said:
It's because of the update and the country restrictions, but in the previous versions I managed to activate the call recording function with the help of the above utility and the installation of com.android.incalli provided by @TorstenH which is also above in the thread.
I hope that someone here who knows better will find an updated solution.
iulianteodor said:
Hello,
After the last update IN2023_11_F.62, Call Recording no longer works. Do you have an update to your solution?
It worked until yesterday when I made the mistake of doing the update.
Click to expand...
Click to collapse
I have the very same issue. Please kindly inform me if you find a solution.
Click to expand...
Click to collapse
violgore01 said:
This is the file, it is in other topics of this forum.
I have used it before
But when I reboot the phone.. I lost the option of record
Click to expand...
Click to collapse
In my phone (oneplus 8 pro) with the last update (F.62) I can't install this apk because my version is newer :\
I have installed joneplustools and Oneplus call recorder, but I don't have any compatibile dialer.
Anyone can help me? :|
Call recording worked in the previus update (F.13).
violgore01 said:
I caaaannnnnn
from adb shell install
adb install -d "c:\APK\Phone_InCallUI.apk"
And now I can record
Off course I have installa jOne plus tools
update: If reboot, then lost the record option
update2
C:\Users\vssx>adb install -d Z:\APK\Phone_InCallUI.apk
Performing Streamed Install
Success
What is performing streamed install?
Click to expand...
Click to collapse
Thank you so MUCH!!!! you are a Jenious works on my oneplus 8 pro f62 build
yaniv.s said:
Thank you so MUCH!!!! you are a Jenious works on my oneplus 8 pro f62 build
Click to expand...
Click to collapse
Can you please give me a link for Phone_InCallUI.apk

(ROOT) (GSI) Samsung Galaxy S20 SCG01 Japan Snapdragon Pixel experience Android 13 GSI

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Steps to Install Pixel Experience Plus GSI Android 13 on Samsung Galaxy S20 SCG01 Japan
Note: I am not the Developer I am sharing…
-Almost everything,
Fingerprint Working
Face unlock not Working only on A13
Phh setting Qualcomm Enable (use alternative audio policy ) unleash the power of snapdragon Audio Clarity for Music Lover
DON'T FLASH GAPPS, ALREADY INCLUDED
Download Links
Odin https://www.odinflash.com/download
TWRP Recovery TWRP 3.7.0_12
Vbmeta_disabled Download
Pixel Experience GSI Download full https://github.com/ponces/treble_build_pe/releases
Magisk Download
Unlock the bootloader
1. Go to your phone's settings
2. Scroll down and click on the "About phone" section
3. Click on "Software information"
4. Tap on the build number several times until you see a message saying "Developer mode has been turned on"
5. Go back to the settings homepage
6. Scroll down to the very bottom and select the "Developer options" section
7. Enable the "OEM unlocking" option
8. Scroll down and enable the "USB Debugging" Option
9. Connect your phone to your computer with a USB cable
10. Turn off your phone
12. Connect Use to only in PC press volume up + volume down at the same hold same time now connect C port to Phone
13. When you see the blue "Warning" screen, long press the volume up button to unlock bootloader
14. After the reset, start a new device setup and connect only to the internet skip all.
15.Enable Developer option if you can see Bootloader unlock tick Now good to go.
Install TWRP Custom Recovery
16. Open Odin
17. Uncheck auto reboot in Odin and flash TWRP in AP slot and vbmeta_disabled.tar in USERDATA Start Flash. (If failed you are not connected internet after Unlocked Bootloader so Follow up 14)
18.Hold volume down and power until the screen goes black then immediately switch to holding volume up and power to reboot into TWRP.
19.Go to Advanced > Terminal, type: multidisabler. (You will see " - Finished." When it is done.)
20.Go to wipe, format data, and type "yes" to confirm.
21.go Back Select "Dalvik / ART Cache" "Data" and "Cache”.
21. Reboot to TWRP
Install Pixel Experience GSI
22. Extract Pixel Experience file now you can see IMG file change name to system.img
23. Copy the system.img and Magisk files to internal storage.
24. TWRP Click Install and down below you can see INSTALL IMAGE choose system.img path is System.
25. Flash Magisk and reboot.
79. Set-up your new ROM !!
ENJOY !!!
To fix safty net (very important) no ned to flash any file.
1. flash magisk after reboot update the magisk and hide magisk manage reboot.
2. Now enable zysik in magisk setting choose play store and play services clear data for both reboot bhammmmm your safetynet is fixed.
SCREEN SHOT
To avoid any confusion between this and full ROMs that include kernels, I have changed the title of your post to appropriately reflect that this is a GSI.
Thanks.
Does this work on g986n
Does this work on g986n
DesrtSailor said:
Does this work on g986n
Click to expand...
Click to collapse
You can try it's an GSI ROM. use this recovery for your Model
https://androidfilehost.com/?w=files&flid=316866
Great one bro. Will VOLTE & all the functions in camera works?
There are 3 versions of gsi available. Normal, lite, vndklite. Which one we need to flash?
Pixel Experience GSI download requires authorization
please post the kernel version screen shot.
psychem said:
please post the kernel version screen shot.
Click to expand...
Click to collapse
bnskdd said:
Pixel Experience GSI download requires authorization
Click to expand...
Click to collapse
No Need any authorization Just download full rom i have tested with full rom only if you want you can check with Slim rom As well.
pratheepdx said:
No Need any authorization Just download full rom i have tested with full rom only if you want you can check with Slim rom As well.
Click to expand...
Click to collapse
Successfully swiped in, thank you for your contribution
High refresh rate working?
The updater function is not working.
Fingerprint sensor is not detecting finger, keeps saying lift and re touch again.
120 fps working finger print is working with latest firmware SCG01KDU1CVG3. try to flash latest stock firmware which is mentioned above and try again.
@pratheepdx bro I have installed the latest files as mentioned still fingerprint is not working. and when I go into the updater option it crashes for some reason. The fingerprint is very crucial and if possible please fix it..
Olink007 said:
@pratheepdx bro I have installed the latest files as mentioned still fingerprint is not working. and when I go into the updater option it crashes for some reason. The fingerprint is very crucial and if possible please fix
Click to expand...
Click to collapse
Do you have tempered glass for your screen or something else? its happens to me as well even with Stock Firmware once removed the issue was resolved for me I've verified that the Pixel GSI Android 13 Fingerprint works without any issue and Android 12 GSI Face Unlock and fingerprint both function flawlessly.
Does this work on s20 ultra snapdragon G9880 ?
Does it support Adaptive brightness? cause I can't find it in the settings.
paazoka said:
Does this work on s20 ultra snapdragon G9880 ?
Click to expand...
Click to collapse
If your bootloader unlockable of course this GSI will work. Try at your own risk.

Categories

Resources