Related
Hey Guys
I have a Galaxy note 3 N9005 , rooted and still running stock rom
from my previous android devices i know that deleting the camera sound files or modifying the name will prevent the camera
form making sounds such as focus and shutter etc...
so using root explorer i went to system/media/audio/ui and i added .bak to all the camera sound files and rebooted the phone
but still all the sounds were there , so i deleted the files camera_shutter_ogg and all the ones similar
since my device (and many others by region) dont have the option in the settings to do it
even after this method
adding this line of code <CscFeature_Camera_ShutterSoundMenu>true</CscFeature_Camera_ShutterSoundMenu> to others.xml in system/csc
after that i tried using some apps but nothing worked and i am assuming its because the files are no longer there because i deleted them
and then after i used the Wanam xposed method but still no results and i am pretty sure its because the files are not there because it adds .bak at the end of their names to disable them
so now i am stuck with the sound , honestly i dont know how the sound is playing since the files are not even there.
And I know I can get another camera from the play store with no sound but I want to keep using the stock one
any help regarding this issue is highly welcomed
There are sound files within the camera apk. I tried modifying them earlier but when I replaced the stock apk, it would not launch. Had to reflash stock to return it. If you find out how to do it, please let me know. From what I've read, the camera sounds you deleted are only the ones from the front facing camera.
How to do it - This is how I removed the camera, I think:
- I deleted all the camera related ogg files from system media ui
- I changed system csc custom.xml where it says camera shutter on to off (my guess is that this fixed it)
^If this does not work, read through the post and see what happened, maybe it was something else. Not sure as I have done so many things at once.
-------------------- Original post:-------------------------------------------------------------
I live in Australia,
Although there is no law here for cameras to have a sound, Samsung thought that putting a permanent sound on would be a great idea. In reality it makes the camera useless.
So I wanted to remove the camera shutter sound and did this -this worked on my note 3-:
1. rooted the phone
2. went to system/app - removed samsung.camera.3.apk (or sth like that)
3. opened the app with winrar, went to res/raw and replaced all .ogg files with empty text files with the .ogg extension, identical to the ones with the sounds
4. put the app back in system/app
5. restarted the phone
---
problems:
A) the original samsung app has been replaced with the google stock one
B) when i go to system/app and try to open samsung.camera.3 it says " there was a problem parsing the package”.
* when i put the app with the changed ogg files on the SD card and try to install it from there it does not let me... it just ends up saying app not installed.
* if i put the samsung app with the original ogg files in system/app i still get the parse error... but if i try to install this one from the SD card it does get installed.
* if i take the .ogg files from the samsung app and put them back in my modified app it still doesnt let me install it from the SD card
(the install from unknown sources is clicked)
Please help me!
I have discovered that if I replace just shutter.ogg I can install that app from the SD card and the shutter sound is gone. However, the zoom click is not.
Based on this I guess the parse error is either:
a) as I put ogg files that were empty, the overall size of the app changed
b) samsung has some way of telling if you replace some files in that app
?!?!
LE: I have used zipsigner 1.1 to resign the app with the changed ogg files. Now I can install it from the SD card -still does not work inside system-, but it force crashes when I try to use it. I seriously do not understand what is going on.
On the Note 3 I just replaced the ogg files with empty renamed text files and it worked perfectly.
So now I have replaced all the ogg files with renamed working ogg files -not empty text files renamed- and it still force closes even if I can install the app after resigning it...
what the f is going on?
Another thing I noticed - inside the Note 3 camera app I dont see any classes.dex file which exists inside the Galaxy S5 camera app. Wonder why.
Any idea at all would be really appreciated!
LE; for some reason now it will not let me install the original samsung app anymore either. I have no freaking idea why not since I could install the original before. Now the installer runs and then it says app not installed. Unbelievable.
LE2: i have also edited customer.xml. Which is strange is that I had to disable knox first before being able to edit it. While on the Note 3 i could edit the file easily.
I just hold the power button down and put the phone onto vibrate or mute.
Sent from my SM-G900F using Tapatalk
The thing is that there is a law in korea and japan that all cameras must make sounds. I guess they are too paranoid (stupid) when it comes to privacy. This law does not exist in America or Europe. That is why in those areas you can put it on mute or silent and there is no camera sound anymore. Unfortunately, for some messed up reason, HTC and Samsung send „Oceania”-zone phones to Australia. And they come with no way to turn that sound off, even if there is no legal requirement here.
---
Anyway, my biggest problem now is that it will not let me install the original samsung app anymore either. And I do not understand why. All I did was install and uninstall modified camera apk. So why cant I install the original one anymore?!
Ok so...
I went to the Applic Manager, All apps and then emptied the cache for a lot of processes that seemed related to installing stuff or cameras.
After that I could Install the original camera app from the sd card again.
Surprisingly enough I see that now I can finally mute the camera.
This is either because:
- I deleted all the camera related ogg files from system media ui
- I changed system csc custom.xml where it says camera shutter on to off (my guess is that this fixed it)
...
Anyway so now the sound is gone and the original app back.
The sound is also gone in the google app. I couldn't turn it off in this app either before.
So yeah...
---
Sent from my SM-G900I using xda app-developers app
I am rooted. I copied the original shutter.ogg and shutter_multiple.ogg to my Mac. With Audacity I opened the files and amplified the whole stream by -50dB (so its totally silent). Then I safed these files as ogg and put them back to /system/media/audio/ui. What I did exactly was I first renamed the original souds and put the new files there afterwards so I did not overwrite any file. Then I changed the attributes to 644 and it worked without a reboot.
I am in germany and here we have the same law like in korea. So you cannot turn of the shutter sound in settings of the camera.
ElenaPower said:
I am in germany and here we have the same law like in korea. So you cannot turn of the shutter sound in settings of the camera.
Click to expand...
Click to collapse
Are you sure? cause last year I used the firmware for Germany on the S4 to mute the camera...
I tried this method, but I don't have a custom.xml file. The closest I have is a customer.xml file. And it doesn't have a shutter setting in it to turn off.
Sent from my Galaxy S5
Hello, all...
I've asked this question in the leak thread, but it moves so fast that I don't think a lot of attention is being paid to it.
So, I'll try to make it quick. When I installed Beans's pre-rooted 4.4.2 leak ROM, I realized that the emoji being displayed in Hangouts were different - not the typical Google emoji, but more similar to the emoji that you find in Go!Messenger, Handcent, and other SMS apps that support emoji.
I suspect that Samsung has included their own emoji, and had them baked into Hangouts, but I can't seem to fix it. Even by removing hangouts and installing it from the Play Store, or restoring from Titanium Backup.
When I choose to add a smiley in a Hangout... I can see them in the list... but when I pick one, it switches to some other (samsung's?) version of it in the text box, as well as the conversation. My friends see the normal one on their end... and likewise when they send me one, it shows up as the alternative.
Is anyone else seeing this issue? I'd think that I would have seen it mentioned.
I found a thread on an HTC device that advised a user with a similar issue to rename a stock font, and I tried a similar approach, with no results.
With my DPI changed to 320, I can't even tell what emoji are being used, as this new brand is much smaller than the standard ones.
This bugs me. I want the google emoji back.
Any help? Thanks!
DrPhant0m said:
Hello, all...
I've asked this question in the leak thread, but it moves so fast that I don't think a lot of attention is being paid to it.
So, I'll try to make it quick. When I installed Beans's pre-rooted 4.4.2 leak ROM, I realized that the emoji being displayed in Hangouts were different - not the typical Google emoji, but more similar to the emoji that you find in Go!Messenger, Handcent, and other SMS apps that support emoji.
I suspect that Samsung has included their own emoji, and had them baked into Hangouts, but I can't seem to fix it. Even by removing hangouts and installing it from the Play Store, or restoring from Titanium Backup.
When I choose to add a smiley in a Hangout... I can see them in the list... but when I pick one, it switches to some other (samsung's?) version of it in the text box, as well as the conversation. My friends see the normal one on their end... and likewise when they send me one, it shows up as the alternative.
Is anyone else seeing this issue? I'd think that I would have seen it mentioned.
I found a thread on an HTC device that advised a user with a similar issue to rename a stock font, and I tried a similar approach, with no results.
With my DPI changed to 320, I can't even tell what emoji are being used, as this new brand is much smaller than the standard ones.
This bugs me. I want the google emoji back.
Any help? Thanks!
Click to expand...
Click to collapse
I would love to know how to fix this as well
bump.
I've succeeded in breaking it even worse. Through some hellish combination of renaming some fonts with "emoji" in the name in /system/fonts... and using the font installer in ROM Toolbox Pro to hack things up even worse... I now just have standard non-color (black lines on background) emoji in hangouts. ugh!
Can't someone smarter than me tell me how to fix this?
DrPhant0m said:
bump.
I've succeeded in breaking it even worse. Through some hellish combination of renaming some fonts with "emoji" in the name in /system/fonts... and using the font installer in ROM Toolbox Pro to hack things up even worse... I now just have standard non-color (black lines on background) emoji in hangouts. ugh!
Can't someone smarter than me tell me how to fix this?
Click to expand...
Click to collapse
Put the two .ttf files in your /system/fonts folder (backup originals if you want) and change permission to -rw-r--r--
Put the .xml file in your /system/etc folder (again, backup original if you want) and change permission to -rw-r--r--
Reboot phone, and hopefully everything works fine
LoneAsp said:
Put the two .ttf files in your /system/fonts folder (backup originals if you want) and change permission to -rw-r--r--
Put the .xml file in your /system/etc folder (again, backup original if you want) and change permission to -rw-r--r--
Reboot phone, and hopefully everything works fine
Click to expand...
Click to collapse
That was your first post? I'm honored to have popped your xda cherry.
I tried the switching and renaming of fonts biz... and it hasn't worked. However, the mention of this xml file is new to me.
Can you elaborate? When/where/how did you learn of this approach?
DrPhant0m said:
That was your first post? I'm honored to have popped your xda cherry.
I tried the switching and renaming of fonts biz... and it hasn't worked. However, the mention of this xml file is new to me.
Can you elaborate? When/where/how did you learn of this approach?
Click to expand...
Click to collapse
I didn't like the stock emoji on the Note 3 so I decided to change it to the stock Android one. After searching online, I found that those files were the ones you need to change. I got them from a GPE system dump. The .ttf files are the stock emoji. The .xml file basically is how the fonts are prioritized (as far as I can tell) which makes the stock emoji default before the Samsung one.
Anyway, that's how I got it to work on my phone. I'm not exactly sure how/why it worked but it did for me.
has anyone else tried this, the samsun emoji are god awful??
I just used the method outlined by LoneAsp and it worked for me.
Sent from my SM-N900V using Tapatalk
I attempted the method described by LoneAsp and it didn't work for me. Not sure if it matters, but I'm using a Galaxy Note II on the DN3 ROM.
I downloaded Emoji Switcher (root) from the Play store and it seems to have done the trick. There are some missing icons, however, and I'm not sure if the author will be updating this app to use the updated font files anytime soon.
jp.esteban said:
I attempted the method described by LoneAsp and it didn't work for me. Not sure if it matters, but I'm using a Galaxy Note II on the DN3 ROM.
I downloaded Emoji Switcher (root) from the Play store and it seems to have done the trick. There are some missing icons, however, and I'm not sure if the author will be updating this app to use the updated font files anytime soon.
Click to expand...
Click to collapse
I should have updated my OP... but I used Emoji Switcher to fix this problem, as well. I used the Samsung ones for a while... and I'm currently on the default Google ones. (The samsung ones include a few awkward-looking ones. Kind of creepy. lol) I haven't noticed any missing icons. Which ones are missing?
With my modified DPI (changed to 320 from 480)... the icons were so small that they weren't fun to use or receive... so I used an xposed module, App Settings, to change the font scale to 200%. This makes longer messages kind of a chore, but overall I'm glad the text is so much bigger. The emoji are much better, that's for sure.
Speaking of Hangouts and xposed modules... I also recommend "Stickers for Hangouts" which enables "add sticker" and "add drawing" to your attachment options in Hangouts. https://play.google.com/store/apps/details?id=com.quinny898.app.stickersforhangouts
Until now... "stickers" were only an option in the iOS version of Hangouts. Does that make sense? (answer: no)
Thanks LoneAsp!!
LoneAsp said:
Put the two .ttf files in your /system/fonts folder (backup originals if you want) and change permission to -rw-r--r--
Put the .xml file in your /system/etc folder (again, backup original if you want) and change permission to -rw-r--r--
Reboot phone, and hopefully everything works fine
Click to expand...
Click to collapse
Thanks!!!, works great for me!!, Galaxy S4 i9500
I recorded sound from the sound recorder and tried to send it via stock messaging however I get an error file size to large however the file size is only 633.8 kb and 649,025 bytes file is a. M4a I tried renaming it to a mp3 but still no luck I have exposed installed is there any setting or module I can I install or change to make this work?
Also please note I am unable to use another messaging app due to me using the gear 2 neo watch
is there anyway to increase the mms file size ?
ex-28 said:
I recorded sound from the sound recorder and tried to send it via stock messaging however I get an error file size to large however the file size is only 633.8 kb and 649,025 bytes file is a. M4a I tried renaming it to a mp3 but still no luck I have exposed installed is there any setting or module I can I install or change to make this work?
Also please note I am unable to use another messaging app due to me using the gear 2 neo watch
is there anyway to increase the mms file size ?
Click to expand...
Click to collapse
Yes it's possible as a lot of custom ROMs modify the maximum MMS file size. Search XDA for details, but I believe that it would be done by decompiling the stock app and editing the value in mms_config.xml. Alternately you may be able to find a modified copy of the stock MMS app to the same effect.
.
OK thanks been searching around but so far no luck... Least I know it's possible just have locate a resolution now.
fffft said:
Yes it's possible as a lot of custom ROMs modify the maximum MMS file size. Search XDA for details, but I believe that it would be done by decompiling the stock app and editing the value in mms_config.xml. Alternately you may be able to find a modified copy of the stock MMS app to the same effect.
.
Click to expand...
Click to collapse
able to dig up any more info for me on this , can't seem to locate a thing or modified apk for the s5 or a way to increase the mms file size...
would truly appreciate it.
ex-28 said:
able to dig up any more info for me on this , can't seem to locate a thing or modified apk for the s5 or a way to increase the mms file size...
would truly appreciate it.
Click to expand...
Click to collapse
Well I don't know how you aren't finding anything. I just did half a dozen searches and even poor keyword choices pull up results.
But anyway, go read the descriptions of some custom S5 ROM support threads. A lot of them list as a feature that they have modified the stock MMS size limit. The modified apk will be in the custom ROM.
If you don't intend to install their full ROM, respect their hard work and ask the Dev for permission to use his modified apk, rather than just steal it. And don't forget to click the thanks button in his thread too. I noticed that you aren't consistent on doing that when people help you and it is the absolute least that you should be doing to acknowledge them.
.
As title says.. I was a little overzealous removing some bloatware, & I THINK this may be why I'm having problems with an app
I have a Rooted Samsung S4 with Android 4.3 (but unfortunately the KNOX has been 'tripped') which allows me full access to the phones built in apps.
(not flashed custom ROMS.. hate to go through hassle of reinstalling everything - especially game data, hence why still 4.3)
Thought I'd remove some bloat - so I usually rename a couple of bloat, run for a while to see if there's any problems - then totally remove them when I'm happy nothings goes wrong
Unfortunately this one time - I accidentally removed (i.e deleted) the default Samsung camera/gallery app instead of 'freezing'/renaming them (can't remember the names - I THINK they were something like gallery2 or similar) & of course I didn't make a backup.
Nevertheless I 'replaced' them with a combination of the google edition 'photosphere' camera (for the 'extra' features) & open camera (very small basic camera app) and use quickpics app as the 'Gallery' (even with these installed - still takes less space than the default Samsung Camera/Gallery comb IMHO)
I know that the Google Photosphere camera doesn't save to ExtSDCard, but thought this isn't a major problem as I can easily move them from intSD to ExtSD using ES File Explorer..(Yeah I know I could install some 'framework' thingy with additional plugin/script, but I'm trying to REMOVE bloat - not add it)
The problem I have, which I suspect is due to me deleting the default camera, is that I sometimes use Picsplay Pro to edit/crop/resize pictures etc. Under settings it allows the save location to be either 'Picplay Pro' or 'Camera'. 'Picplay Pro' folder is situated on the IntSDCard, while 'Camera' is (I believe) set up for the ExtSDCard
Picplay Pro works fine until I try saving.. if I have the 'Save to PicPlay Pro' selected - it works fine & saves the edited pictures to the IntSDCard
IF I select 'Save to Camera' however - when saving I get the usual 'PicPlay Pro has stopped for..' message
I suspect that it's not actually a problem with Picplay Pro app as such.. just that since the default camera isn't installed - Picplay can't find the correct Camera 'setting' to save to ExtSDCard (or something along that line)
What I'd like to confirm is..
IS it a Picplay Pro problem (anyone else having trouble using the 'Camera' setting ??)
IS there any way I can re-install the original Samsung 4.3 Camera/Gallery App(s) to 'fix' the missing setting - if so, how ?
IS there any file/setting I could edit to fix this problem ??
Can anyone offer advice ??
Many Thanks in Advance for any assistance
Extracting the camera apk from a stock 4.3 rom might do. Then copy it to /system/app folder (or wherever the system apks are), set the right permissions and reboot phone. And hope that it boots up
Thanks for the suggestion..however.....
Went to Sammobile and downloaded a stock rom (same one as installed in phone -took a while though) but unable to open it the find app...
Normal winzip says 'unsupported forrmat' ( or something like that), es file explrer cant open it.. but Bandizip did manage to let me view contents but all that in their is 2 file.. 1 large md5 and cant remember the other but it was v.small
Can you explain how I am to extract the required files ?
Or
is there someone who can post a link to a version ?
Once again many thanx for taking time to reply
Winrar opens them.
Thanks for that Lenny, it opened it .. now what ??
I used Winrar to open 'the ZIP file Stock ROM ('I9505XXUEMK8_I9505BTUEMK5_BTU.zip')
Inside are the 2 files I mentioned (I9505XXUEMK8_I9505BTUEMK5_I9505XXUEMK8_HOME.tar.md5' and 'SS_DL.dll')
I then use Winrar to open the largest file (the 'I9505...') & that shows me several files
aboot.mbn
boot.img
cache.img.ext64
hidden.img.ext64
modem.bin
NON-HLOS.bin
recovery.img
rpm.mbn
sbl1.mbn
sbl2.mbn
sbl3.mbn
system.img.ext4
tz.mbn
I assume that the apps are stored in one of these (I also assume it's the 'system.img.ext4' one as its the largest). however trying to open it with winrar & all I get is windows (8.1) saying 'How do you want to open this type of file. look for app in the store' - so I'm guessing winrar can't open ext4 files
I've googled and found that to 'view/extract ext4' use either 'ext2read' or 'Diskinternals Linux Reader' - tried both.. ext2read doesn't show anything at all - just a white screen & Linux Reader only allows me to 'backup' the system file.. I can't see no way to extract apk (cant even view the files inside tobe honest)