Can somebody give me some pointers how to disable shutter sound on stock LG camera app by repackaging it?
I went as far as:
1. download LGCameraApp.apk using:
Code:
adb pull /system/product/priv-app/LGCameraApp/LGCameraApp.apk
2. Pull framework using :
Code:
adb pull /system/framework/lge-res/lge-res.apk
3. Decompress framework:
Code:
apktool if lge-res/lge-res.apk
[code]
4. Decompress apk:
[code]
apktool d ../LGCameraApp.apk -f
[code]
Now I'm trying to find where is the goddamn shutter sound, so that I could kill this annoying thing. Pointers?...
Well, the sound file for it resides in system-media-audio-ui. File afaik is cam_snap_0.ogg. Perhaps looking for that and poiting it to a null file?
I too want to disable the annoying shutter sound on my G7.
Do not know it will help you guys, but if you are rooted and using Magisk - please test attached module which I have crafted long time ago - works flawlessly and disables shutter sound on ULM Oreo 10i with Magisk 19.3 for me.
This would be help!
Silent Mode ᴾᴿᴼ on Google Play!
vlad48 said:
Do not know it will help you guys, but if you are rooted and using Magisk - please test attached module which I have crafted long time ago - works flawlessly and disables shutter sound on ULM Oreo 10i with Magisk 19.3 for me.
Click to expand...
Click to collapse
Do you have something similar for the screenshot sound?
rpgdev said:
Do you have something similar for the screenshot sound?
Click to expand...
Click to collapse
Here we go...
(Added silent camera_click.ogg to \system\media\audio\ui\)
vlad48 said:
Here we go...
(Added silent camera_click.ogg to \system\media\audio\ui\)
Click to expand...
Click to collapse
Awesome bro. Thanks!
I tried the module vlad48 posted but either I goofed up or something, didn't work on Pie, for me.
So created one that I can verify works on V35 Pie and V30 Pie, follow This Link.
Really not sure why the other didn't work as they both do the same thing. Anyway, it's certainly nice not to have the shutter click sound. You won't hear it when pressing the vol down either. Thanks vlad48 for pointing the direction on how to do that.
cheers
https://play.google.com/store/apps/details?id=com.mggm.shiiitmode
No root. You're welcome
Related
So, after some research, I found out to fix the AOSP gesture typing on Cm 13. This simple fix works on all devices (So far) running Cyanogenmod 13. So, without further ado, lets get into this.
So depending on what Gapps package you flashed to your device, you may need to download the "Google Keyboard" (https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin&hl=en) and if your device already has it, then right on!
So, using a file exploring app, (I had some slight trouble with the CM File Explorer) go to Root>Data>App>com.google.android.inputmethod.latin-1>lib>arm and stop.
Once you are there, you should see a file named "libjni_unbundled_latinmegoogle.so" this is the file you need to get the gesture typing working.
So, what you want to do is copy that file to System>Lib. After you've done that, rename the file to "libjni_latinemegoogle.so"
And congratulations! You did it! Now, a quick reboot and your gesture typing should be working, if not, post in the comments and I'll try and fix it for you.
P.S. I know there is a way to do this using a terminal app like "Terminal Emulator" but I had issues doing so. If anyone out there knows how to do this, please share how in the comments!
The specified ARM folder is empthy.
Edit: Don't use CM File Manager as it won't find the file. Also keep in mind that some languages don't support swype functionality.
Excuse the lazy copy-and-paste job from the CyanogenMod Forums, but I have got this to say:
aha360 (CyanogenMod Forums) said:
Thank you very much for helping me out with fixing the AOSP Keyboard Swype gesture fix @MrPockets and @TacoTank
Here's a flashable ZIP with the addon.d BASH survival script so that if you want to install nightly updates and do anything relating to this, you can just flash this ZIP package without the fear of losing this feature.
This has also been tested on CM14 (Android Nougat) and I can confirm that this works without any issue whatsoever.
Enjoy.
https://1drv.ms/u/s!Agj5mSliZ57Fhkekg-w8mQap1umU
Source: https://forum.cyanogenmod.org/topic...ure-typing-fix/?do=findComment&comment=610733
Click to expand...
Click to collapse
aha360 said:
Excuse the lazy copy-and-paste job from the CyanogenMod Forums, but I have got this to say:
Click to expand...
Click to collapse
Hi, I tried to install your zip from recovery, but in my AOSP Unlegacy-Android Marshmallow it did not work. Any troubleshooting?
miomaguro said:
Hi, I tried to install your zip from recovery, but in my AOSP Unlegacy-Android Marshmallow it did not work. Any troubleshooting?
Click to expand...
Click to collapse
https://onedrive.live.com/redir.asp...&authkey=!AC0r2z3f0hk72Bc&ithint=folder%2czip
Download, and extract the whole folder to:
Code:
/system/app/
Be warned that this may cause problems as this was taken from Lineage 7.1.1 so backup your LatinIME files before making any changes.
aha360 said:
https://onedrive.live.com/redir.asp...&authkey=!AC0r2z3f0hk72Bc&ithint=folder%2czip
Download, and extract the whole folder to:
Code:
/system/app/
Be warned that this may cause problems as this was taken from Lineage 7.1.1 so backup your LatinIME files before making any changes.
Click to expand...
Click to collapse
Thanks for your help. Do you think only the shared object will be enough?
miomaguro said:
Thanks for your help. Do you think only the shared object will be enough?
Click to expand...
Click to collapse
The shared object (that is modded to support Swype) and the Swype gesture flashable ZIP will suffice
//Thank you all for 30k+ Views. You're amazing guys//
You want Android 8 with Viper4android to?
Thread created check my profile...
Hi,
at first im not responsible for anything that happens to your phone OK?
Fine Let's Start.
If you are on cm skip all until the cm section
Supported kernel list and known errors/bugs see second post
Step 1
- Flash full Factory Images.
- Install TWRP, remember you have to be decrypted.
Step 2
- Install Android 7 ROM by tupac4u / or any other rom / or leave stock
- Reboot //if nessesairy
Step 3
- Flash ElementalX's N Kernel.
- Flash Viper5.0_Stock.zip in Recovery / or any other viper
- Reboot.
Step 4
- Install driver.
- Open File Explorer and delete /system/vendor/etc/audio_effects.conf
- Reboot.
Step 5
- Set enforcing to permissive (You have to do it at every Reboot!).
- In Viper open Menu->FX-CompatibleMode->yes // you can try without, it may work
- Enjoy Viper.
CM Section
1. Flash arise sound mod ( link down below )
2. And IMPORTANT flash super su
3. Disable audio fx and reboot
SPOTIFY FIX
1. Download that file
https://drive.google.com/file/d/0BxyY1q0qeeeEeUFGT3JHeDZLZkE/view
2. Place it under /system/etc
3. Reboot
PURE NEXUS ONLY WORKS WITH BUILD 10/25!!!
If it worked leave a reply.
Alternative Download link for ARISE Viper here:
http://forum.xda-developers.com/android/software/r-s-e-sound-systems-auditory-research-t3379709
Unsupported Rom/Kernel
Kernel:
- Stock
- Jolla
ROM:
F.A.Q.
Q: Spotify isn't working with that
A: Force enable Viper4Android and turn FX Mode to compatible. Then restart both applications.
Q: Why ElementalX Kernel?
A: That's the only Kernel who works with Viper except Stock kernel. Elite Kernel may also work but it hasent been updated since the Dev Previews.
Q: Is that also working with the stock rom?
A: Yup. Also works with (nearly) any stock based ROM.
Is there a definite way of checking if it's working? Not by sound?
Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Sent from my Nexus 5X using Tapatalk
how to set permissive mode permanently?
Nightshadow931 said:
Yes, just check driver status in viper when something is playing in the background. If it says 'processing', then it's working.
Btw, why would I need custom kernel for viper?
Click to expand...
Click to collapse
I found that it isn't working on jolla Kernel and Stock.
Did you enable viper in app itself?
Not sure, but maybe you need to enable it on order to see 'processing'..
Did the installation of driver went well?
Sent from my Nexus 5X using Tapatalk
enzippo said:
how to set permissive mode permanently?
Click to expand...
Click to collapse
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.
Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".
Try some other app like play music, v4a won't work on all apps if they have their own equalizer.
Sent from my Nexus 5X using Tapatalk
Blinkiz said:
Nice that someone is trying to get Viper4Android to work on Nexus 5x with Android 7.0 (Nougat). Sadly it does not work, tried your way but it does not enable me to get Viper4Android to work in Spotify.
Selinux is in permissive, your viber4android package is in place, audio_effects.conf removed, Android 7 by tupac4u installed and complete factory image installation before all this. No go..
Viper4android driver status does not complain but processing is always "no".
Click to expand...
Click to collapse
For those who want to use Viper4android with Spotify change fx compatible Mode to compatible in Viper settings. Then Open Spotify and go to Settings->Equalizer that should bring up Viper. Select Force enable and close Viper and Spotify. Open up both again and Boom Viper is there.
How find Android 7 by tupac4u ??
EDIT.
I found him already
Did someone get it working with stock rooted ROM?
noidea24 said:
use a file exlorer with root privileges like es or root explorer and go to /etc/init.d directory, create a file and named "08setperm" (without quotes) and add the below lines in the file and save it..
#!/system/sh
setenforce 0
And give full permission (rwxrwxrwx)
reboot and you should be good. if for some reason your init.d script doesn't launch then download and install universal init.d tool and enable it.
Click to expand...
Click to collapse
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.
trhacker01 said:
Idk if this will work on the new version, but this zip I've attached here sets the previous ElementalX-N5x-1.17 kernel permissive permanently. I'm not on nougat yet, waiting for Xposed.
Click to expand...
Click to collapse
In gonna give it a try
Nightshadow931 said:
Did someone get it working with stock rooted ROM?
Click to expand...
Click to collapse
Me not
Thargorsson said:
In gonna give it a try
Click to expand...
Click to collapse
Nope it don't works
Thargorsson said:
Nope it don't works
Click to expand...
Click to collapse
thats how im running right now, just checked. only with the universal init.d though
noidea24 said:
thats how im running right now, just checked. only with the universal init.d though
Click to expand...
Click to collapse
Ur saying that permissive zip works with the universal init.d?
trhacker01 said:
Ur saying that permissive zip works with the universal init.d?
Click to expand...
Click to collapse
As long as the zip creates/places a file in the init.d to change selinux then i guess it should work
Hello everyone,
My sensor went bad after screen replacement. It always detects as near. Until now I was using xposed to disable it. But now after upgrading to Android N, I don't have xposed and I don't know how to fix it.
The screen is turned off when I make/attend a call, making it difficult to end.
Is there any config file or something in source where I can disable it??
Thank you.
You can use settings>accessibility>Use power button to end call...
Thanks. I am doing what you said now. But still it would be better if I get and solution to disable it.
swapnil0545 said:
Thanks. I am doing what you said now. But still it would be better if I get and solution to disable it.
Click to expand...
Click to collapse
I have not tested in N, but it works in MM.
Copy android.hardware.sensor.proximity.xml the known position and change its string
Code:
<feature name="android.hardware.sensor.proximity" />
to
Code:
<feature name="" />
Go to the TWRP.
Mount the partition system.
Check the permission and assignment to groups for file android.hardware.sensor.proximity.xml
Rename the file android.hardware.sensor.proximity.xml
Copy the changed file android.hardware.sensor.proximity.xml to the /system/etc/permissions
Change the file permission and assignment to groups that have the original file.
Reboot.
The solution for that it change the black thing make the bigger hole on sensor of light and the small one with other
Default for that is small one with sensor light and bigger one for something else
So sorry for bad language see that steps here
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
ze7zez said:
I have not tested in N, but it works in MM.
Copy android.hardware.sensor.proximity.xml the known position and change its string
Code:
<feature name="android.hardware.sensor.proximity" />
to
Code:
<feature name="" />
Go to the TWRP.
Mount the partition system.
Check the permission and assignment to groups for file android.hardware.sensor.proximity.xml
Rename the file android.hardware.sensor.proximity.xml
Copy the changed file android.hardware.sensor.proximity.xml to the /system/etc/permissions
Change the file permission and assignment to groups that have the original file.
Reboot.
Click to expand...
Click to collapse
I am going to try this. I hope I don't soft brick it.
swapnil0545 said:
I am going to try this. I hope I don't soft brick it.
Click to expand...
Click to collapse
Hey did you get it to work?
I've tried - no, did not work on 7.1.
Have you any other solution? I've the same issue on nexus 6p After display replacement. And now on nougat i can't fix it. Simeone Can help me?
My other solution was to recompile Dialer.apk with proximity disabled.
digital0 said:
My other solution was to recompile Dialer.apk with proximity disabled.
Click to expand...
Click to collapse
Where is the apk located? I'm running 7.0 and cannot find it in the system/apps folder.
On CM14 it is in /system/priv-app/Dialer/
digital0 said:
My other solution was to recompile Dialer.apk with proximity disabled.
Click to expand...
Click to collapse
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
You are a life saver
digital0 said:
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
Click to expand...
Click to collapse
You just helped me with the biggest inconvenience on my phone. I used sensor disabler on xposed but this is a perfect fix for a broken proximity sensor and android 7 ?
sweetmyke said:
You just helped me with the biggest inconvenience on my phone. I used sensor disabler on xposed but this is a perfect fix for a broken proximity sensor and android 7
Click to expand...
Click to collapse
hello sir
I have this issue in my nexus 6 and want to disable Proximity Sensor but without Xposed Installer Framework for Android 7,I couldn't.
would you please tell me how did you use this Compiled App????
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Thank You.
driftking132 said:
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Click to expand...
Click to collapse
You should run these commands on a PC, to which phone is connected by USB cable.
digital0 said:
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
Click to expand...
Click to collapse
Just out of curiousity, what was the reason to comment out the ALTER TABLE line in DialerDatabaseHelper.java?
I've attached my version of the fix that I've been running since CM13, now recompiled for CM14.1. There's effectively only one line of code changed. Source is up-to-date to Feb 6, 2017.
As far as I can tell, digital0's version works just as well, so there's no reason to try mine if you're not having issues with his.
Same way to install the apk. Attached diff for the curious.
Shimakaze said:
Just out of curiousity, what was the reason to comment out the ALTER TABLE line in DialerDatabaseHelper.java?
Click to expand...
Click to collapse
The CM build I used at the time of compiling gave the error. It is most probably not needed now.
driftking132 said:
hello sir
I have this issue in my nexus 6 and want to disable Proximity Sensor but without Xposed Installer Framework for Android 7,I couldn't.
would you please tell me how did you use this Compiled App????
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Thank You.
Click to expand...
Click to collapse
Sorry for taking so long to respond but I just used root explorer system/priv-app/dialer and replaced dialer.apk. Make sure that you set the permissions to rw-r-r...reboot, let me know if I helped
sweetmyke said:
Sorry for taking so long to respond but I just used root explorer system/priv-app/dialer and replaced dialer.apk. Make sure that you set the permissions to rw-r-r...reboot, let me know if I helped
Click to expand...
Click to collapse
its worked but in call screen there is no answer/ reject buttons please fix this
I'm running Ditto Note 7 ROM on 6.0.1 on my N910C
I already have Busybox and SELINUX set to permissive.
Someone please help
Ok I managed to fix it, I followed this guy's workaround.
slit said:
Thanks, but the ViPER4Android-supolicy zip took care of selinux
Also, if anyone's interested I've finally managed to make it work permanently. You need to remove the deep buffer stuff from audio_policy.conf (placed at system/etc) with a root explorer, AND remove/uninstall/disable SoundAlive in system apps.
Click to expand...
Click to collapse
Recently it has come out xposed framework by rovo89 for android N:
https://forum.xda-developers.com/showthread.php?t=3034811
Has anyone tried it on the p10 lite, with rom stock + recovery + root? or in some other device huawei with rom stock and emui 6?
Thanks in advance.
I've tried it and it works fine, but since I rooted my p10 and installed xposed my battery started to drain noticeably faster, so I went back to stock.
I use xposed with magisk v14 and no battery drain(I think)
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/su.d
mpiero11 said:
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/du.d
Click to expand...
Click to collapse
I get this too, but to fix I just untick all enabled modules in xposed, reboot, enable modules again and reboot again.
hayabusa2yk said:
I use xposed with magisk v14 and no battery drain(I think)
Click to expand...
Click to collapse
How did you install magisk?
plerohero said:
How did you install magisk?
Click to expand...
Click to collapse
Just flash in TWRP
sorry for my bad English
mpiero11 said:
Testing and work fine.
Some times, after reboot, xposed in disabled. Need run this attached script on init, in /su/su.d
Click to expand...
Click to collapse
I am facing the same problem and when I tried to use your solution its not working either.
I somehow able to found out the error (by using init.d scripts app):
Path is not correct for
/data/user_de/0/de.robv.android.xposed.installer/conf/enabled.modules.list
/data/user_de/0/de.robv.android.xposed.installer/conf/modules.list
On checking the path appears to be correct. Then whats the issue here? Please guide.
My P10-Lite is rooted. So I can see the path actually exists in my phone's root folder.
Thanks
mzeeshan2 said:
I am facing the same problem and when I tried to use your solution its not working either.
I somehow able to found out the error (by using init.d scripts app):
Path is not correct for
/data/user_de/0/de.robv.android.xposed.installer/conf/enabled.modules.list
/data/user_de/0/de.robv.android.xposed.installer/conf/modules.list
On checking the path appears to be correct. Then whats the issue here? Please guide.
My P10-Lite is rooted. So I can see the path actually exists in my phone's root folder.
Thanks
Click to expand...
Click to collapse
Change permisions for .sh file, chmod 777 to script, reboot and enjoy.
No problems for my.