Ah... just having fun with root...!
So, if you want to get rid of the camera sounds, follow these steps on your rooted X10:
Prerequisite:
Rooted X10 using the root tutorial (http://forum.xda-developers.com/showthread.php?t=711907).
Busybox installed (download from market)
Fire up your favorite terminal emulator on the phone or launch a shell using "adb shell" (requires android sdk) and run along:
First make the /system partition writable:
Code:
# mount -o remount,rw -t yaffs2 /dev/mtdblock2 /system
Checkout these files:
Code:
# cd /system/media/audio/camera
# ls -l sound0
-rw-r--r-- 1 0 0 9164 Feb 21 02:48 no_sound.ogg
# ls -l sound1
-rw-r--r-- 1 0 0 4384 Jun 29 04:33 af_success.ogg
-rw-r--r-- 1 0 0 6515 Jun 29 04:33 self_timer.ogg
-rw-r--r-- 1 0 0 10806 Jun 29 04:33 shutter.ogg
-rw-r--r-- 1 0 0 5987 Jun 29 04:33 start_rec.ogg
-rw-r--r-- 1 0 0 6279 Jun 29 04:33 stop_rec.ogg
And there are more directories like sound2 and sound3. OK so basically, just replace each of the sounds under soundX folder with no_sound.ogg
Code:
# cp sound0/no_sound.ogg sound1/af_success.ogg
# cp sound0/no_sound.ogg sound1/self_timer.ogg
# cp sound0/no_sound.ogg sound1/shutter.ogg
# cp sound0/no_sound.ogg sound1/start_rec.ogg
# cp sound0/no_sound.ogg sound1/stop_rec.ogg
So when you've got sound1 folder fully patched, simply copy it over sound2 and sound3:
Code:
# cp sound1/* sound2/
# cp sound1/* sound3/
Et Voila!
(You may have to restart the Camera app by killing it via Task killer application or simply restart your phone)
Further development:
Want the phone to say "Say Cheese..."?
You can basically record your own sounds in "ogg" format and replace them in the respective folder either sound1, 2 or 3... but just make sure that you record sounds which are under 5 seconds or so... longer sounds really doesnt make much sense and I really don't know how the Camera app is designed to handle it... YMMV.
You pervy, upskirt-shooting /b/-tard.
Actually, I can set there to be no camera-sound through the settings. Can't you guys do that?
pally777 said:
Actually, I can set there to be no camera-sound through the settings. Can't you guys do that?
Click to expand...
Click to collapse
yea i think I had that option before I rooted my phone... but the japanese firmware that the root relies upon doesnt !
j4mm3r said:
yea i think I had that option before I rooted my phone... but the japanese firmware that the root relies upon doesnt !
Click to expand...
Click to collapse
Slightly off-topic: Didn't Japan recently made it a law that cameras had to make a sound to avoid the secret upskirt-shots the japanese guys are so fond of?
ddewbofh said:
Slightly off-topic: Didn't Japan recently made it a law that cameras had to make a sound to avoid the secret upskirt-shots the japanese guys are so fond of?
Click to expand...
Click to collapse
thats it... this is why i wanted to help our japanese fan boys!!
or.. you know.. /system/default.prop
ro.camera.sound.forced=0
...
Hi,
i post here, because i dont have access to the dev part (10 posts limit maybe).
For the french guys, i have the working files for the hw keyboard.
I'll post them when i get up !
Edit : This is a simple zip file , dont use it with recovery mode !!!!!
Instructions :
unzip file, connect to the phone in adb shell , make /system rw , put the file in /system/usr/keychars (.bin) and /system/usr/keylayout (.kl) . Make the symbolic links to the scholes file. reboot !
I'll test with a more simple(generic) solution.
It's not possible to have an apk?
Nice pat972 I test it now !!
can you explain " Make the symbolic links to the scholes file" please ? (In french toooo )
Ok , let me know if you have a problem with the menu key ! i'll correct it !
For the symbolic links : when you are in the directory , you can do a "ls -l" , you'll see a file pointing to another one, originally pointing to something with "jordan".
you have to do "ln -s /system/usr/keylayout/file.kl sholes-keypad.kl".
No , i don't know how to do apk files !
Thanks for your answer but this don't work.. I have run the folowing command :
>adb remount
remount succeeded
>adb shell
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# cp /mnt/sdcard/a/umts_milestone2-keypad.kcm.bin /system/usr/keychars
# cp /mnt/sdcard/a/umts_milestone2-keypad.kl /system/usr/keylayout
# cd /system/usr/keychars/
# ln -s /system/usr/keylayout/umts_milestone2-keypad.kl sholes-keypad.kl
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# exit
exit
>adb reboot
It's good? or I do a mistake ?
Ok it 's good , but you mix all the symbolic and directories !
so here it is :
# cd /system/usr/keychars/
# ln -s /system/usr/keychars/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
# cd ../keylayout/
# ln -s /system/usr/keylayout/umts_milestone2-keypad.kl sholes-keypad.kl
pat972 said:
Ok it 's good , but you mix all the symbolic and directories !
so here it is :
# cd /system/usr/keychars/
# ln -s /system/usr/keylayout/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
# cd ../keylayout/
# ln -s /system/usr/keylayout/umts_milestone2-keypad.kl sholes-keypad.kl
Click to expand...
Click to collapse
Sorry for this BIG mistake ... but this don't work too....... I think because I do this mistake ! So I come back tomorrow to do new test
Thanks for help!
Sorry for this BIG mistake ... but this don't work too....... I think because I do this mistake ! So I come back tomorrow to do new test
Thanks for help!
Oups it's me, bad bad , sorry i copy paste your line, but there is a mistake in it again !
For the bin file, it is , keychars directory :
# ln -s /system/usr/keychars/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
then you do a "ls -l" to verify the symlink in each directory :
# ls -l
-rw-r--r-- root root 896 2011-08-24 06:26 umts_milestone2-keypad.kcm.bin
-rw-r--r-- root root 896 2011-07-12 22:00 qwerty2.kcm.bin
-rw-r--r-- root root 896 2011-07-12 22:00 qwerty.kcm.bin
lrwxrwxrwx root root 2011-08-24 05:13 sholes-keypad.kcm.bin -> /system/usr/keychars/umts_milestone2-keypad.kcm.bin
You see that the sholes file point the umts one in the keychars directory not the keylayout !
In fact, this is the problem but when I do this commande line, the result is :
"Link failed file exist"
What I must delete ?
You must delete:
/system/usr/keychars/umts_milestone2-keypad.kcm.bin
so do a
Code:
rm /system/usr/keychars/umts_milestone2-keypad.kcm.bin
Thanks for your answer, but always the same message ...
I have delete "sholes-keypad.kcm.bin" after and can finish all code line but don't work............. I test to restore ROM and restart this
Edit : Now it's work, so the commande line are (if you have put the 2 files on the "a" folder in the SDcard ) :
Code:
>adb shell
# mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
# cp /mnt/sdcard/a/umts_milestone2-keypad.kcm.bin /system/usr/keychars
# cp /mnt/sdcard/a/umts_milestone2-keypad.kl /system/usr/keylayout
# cd /system/usr/keychars/
# rm sholes-keypad.kcm.bin
# ln -s /system/usr/keychars/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
# cd /system/usr/keylayout/
# rm sholes-keypad.kl
# ln -s /system/usr/keylayout/umts_milestone2-keypad.kl sholes-keypad.kl
# mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
# exit
>adb reboot
Hi, did someone test this. If you select different country (like german) did the hardware keyboard also switch?
Hi, no i did not, but i would say no ! I have an idea , but i need to test it ! I'll change the bin file and let you know! While im here, it just test your new bluremail.apk and it doesnt seems to work with classic mail ! Said no connection.
Sent from my MotoA953 using XDA App
@walter79 : Yes I have test to change country, but nothing change !
@pat972 : all the "alt" are not good ! (numbers, etc...)
@alex could you do a "ls -l" in each directory and post it here !
@walter : I do some quick test, what appears to me is that my keyboard is always in azerty no matter what locale i put in build.prop or when i change the language setting in the menu.
I also replace my modified keychars by the froyo one, and the keyboard is again in azerty. They are minor differences , more particularly the froyo keychars mix azerty and qwerty layout !
what i think is that the language menu don't change the hw.keyboard layout
I can't see in "cd /system/usr/keychars/" the "Shole.....bin" ....
Code:
# cd /system/usr/keylayout
cd /system/usr/keylayout
# ls -l
ls -l
-rw-r--r-- root root 3295 2011-08-25 11:34 umts_milestone2-k
eypad.kl
-rw-r--r-- root root 4132 2011-08-25 11:16 qwerty.kl
-rw-r--r-- root root 245 2011-08-25 11:16 AVRCP.kl
-rw-r--r-- root root 75 2011-08-25 11:16 cpcap-key.kl
lrwxrwxrwx root root 2011-08-25 11:37 sholes-keypad.k
l -> /system/usr/keylayout/umts_milestone2-keypad.kl
# cd /system/usr/keychars/
cd /system/usr/keychars/
# ls -l
ls -l
----rwxr-x root root 896 2011-08-25 11:36 umts_milestone2-k
eypad.kcm.bin
-rw-r--r-- root root 896 2011-08-25 11:16 qwerty2.kcm.bin
-rw-r--r-- root root 896 2011-08-25 11:16 qwerty.kcm.bin
#
pat972 said:
Oups it's me, bad bad , sorry i copy paste your line, but there is a mistake in it again !
For the bin file, it is , keychars directory :
# ln -s /system/usr/keychars/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
then you do a "ls -l" to verify the symlink in each directory :
# ls -l
-rw-r--r-- root root 896 2011-08-24 06:26 umts_milestone2-keypad.kcm.bin
-rw-r--r-- root root 896 2011-07-12 22:00 qwerty2.kcm.bin
-rw-r--r-- root root 896 2011-07-12 22:00 qwerty.kcm.bin
lrwxrwxrwx root root 2011-08-24 05:13 sholes-keypad.kcm.bin -> /system/usr/keychars/umts_milestone2-keypad.kcm.bin
You see that the sholes file point the umts one in the keychars directory not the keylayout !
Click to expand...
Click to collapse
So , your problem is you don't have the link in the keychars ! so do it , it must look like my previous post (quote) .
# ln -s /system/usr/keychars/umts_milestone2-keypad.kcm.bin sholes-keypad.kcm.bin
and do a ls -l to verify it !
All works now ! Sorry ...but I don't understand why the 1rst time this command line don't work....pearhap's can't do the 2 files in the same time (reboot between) ???
Thanks for your help !
[Thread edited and changed, because partially solved]
Device: asus Nexus 7
Android Version: 4.2.2
Build: JDQ39
rooted
I have installed SSHDroidPro (v1.9.6) - https://play.google.com/store/apps/details?id=berserker.android.apps.sshdroidpro and Terminal IDE (v2.02) - https://play.google.com/store/apps/details?id=com.spartacusrex.spartacuside
Code:
/storage/emulated/legacy # which rsync
/storage/emulated/legacy # which mkdir
/data/data/berserker.android.apps.sshdroidpro/home/bin/mkdir
Code:
-rwx------ 1 u0_a86 u0_a86 1012309 Dec 5 2011 /data/data/com.spartacusrex.spartacuside/files/system/bin/rsync
What do I have to do, that _this_ rsync is used by SSHDroidPro? I would like to use all shell.commands from Terminal IDE with SSHDroidPro.
It helped to copy rsync set the permissions to 755 and link it:
Code:
cp /data/data/com.spartacusrex.spartacuside/files/system/bin/rsync /data/data/berserker.android.apps.sshdroidpro/dropbear
ls -l /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
-rwxr-xr-x 1 root root 1012309 Mar 10 01:37 /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
ls -l /data/data/berserker.android.apps.sshdroidpro/home/bin/rsync
lrwxrwxrwx 1 root root 60 Mar 10 01:38 /data/data/berserker.android.apps.sshdroidpro/home/bin/rsync -> /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
And then:
Code:
/storage/emulated/legacy # which rsync
/data/data/berserker.android.apps.sshdroidpro/home/bin/rsync
The rest of the posting was deleted, because it was a bug in my script. But what can I do, so the ssh-server can use the commands ot the IDE-Terminal?
Hi im porting rom but i dont have this device.
can anyone just open terminal emulator and type
su
ls -l dev/block/platform/msm_sdcc.1/by-name/system
and post here the output?
it will not harm your device ls command only lists files pls i cant do anything without that
I got this:
[email protected]:/ $ su
dev/block/platform/msm_sdcc.1/by-name/system <
lrwxrwxrwx root root 2015-10-08 11:47 system -> /dev/block/mmcblk0p21
[email protected]:/ #
Click to expand...
Click to collapse
Was that what you wanted, or did you want the file it mentions in the output?
Hello, I hope someone has seen this before. I am not sure how I managed to break S7, as it was working, initially. I am running PE1 firmware, and factory reset before following the root guide, in the verizon guide forums. But now I have the problem where supersu will not auto start on bootup. I have to connect the usb cable to my pc, and use adb and manually start it. Root and Supersu are loaded. The only thing I have to run is:
C:\adb\adb.exe shell /system/etc/launch_daemonsu.sh
Then disconnect the usb cable, and all is well. Everything seems to be correct. What am I missing? I really do not want to start completely over. I have run the verizon debloat v2 and v8. I had to manually start supersu to flashfire the v8 script. Also in the same guide. All the root checker apps will see that you have root, but they say you are missing a super user app.
C:\adb\adb.exe shell /system/etc/launch_daemonsu.sh
mkdir: '/su': File exists
cp: /cache/stock_boot_*: No such file or directory
cp: bad '/cache/stock_boot_*': No such file or directory
/data/su.img: recovering journal
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
skipping journal recoverybecause INCOMPAT_RECOVER was clear.
check whether gdt & bitmap free count is vaild
/data/su.img: clean, 25/2048 files, 1399/8192 blocks
ext2fs_close2 : fs->write_bitmaps is null
ext2fs_close2 : normal operation, return 0
mount: No such file or directory
mount: No such file or directory
supolicy v2.74 (ndk:arm64-v8a) - Copyright (C) 2014-2016 - Chainfire
Patching policy ...
(Android M policy compatibility mode)
- Success
<Then disconnect the usb cable, supersu will work fine now.>
C:\adb>adb shell cat /system/etc/init.sec.boot.sh
#!/system/bin/sh
echo "init.sec.boot.sh: start" > /dev/kmsg
# start deferred initcalls
cat /proc/deferred_initcalls
## strace for system_server
#str=""
#while [ "$str" = "" ]; do
# str=`ps | grep system_server`
# sleep 0.1
#done
#
#pid=${str:10:4}
#echo "init.sec.boot.sh: strace -tt -T -o /data/log/strace.txt -p ${pid}" > /dev/kmsg
#strace -tt -T -o /data/log/strace.txt -p ${pid}
/system/etc/launch_daemonsu.sh
/data/s7startup/startupscript.sh
C:\adb>adb shell ls -la /system/etc/launch_daemonsu.sh
-rwx------ root root 4686 2016-07-03 13:32 launch_daemonsu.sh
Thanks again.
Did you push the supersu app to you device?
Is that to say uve got supersu installed but it won't start? If that's so I would check the box for start supersu during bootup. Unless im just completely missing your issue and im sorry if I am.