This is the same implementation as the g2 boot sound enabler with a few improvements.
i'm not responsible if you blah blah blah. don't be stupid, and don't flash things to your phone without realizing the possible risk. i haven't bricked a phone yet and don't plan on it.
DOWNLOAD:
View attachment bootsound-glacier-CM-signed.zip
MIRROR - Mediafire
This enables custom boot sounds. After flashing and rebooting you should be greeted with the all to famous "DROID" bootsound.
you will also have some new useful commands in terminal:
newbootsound - copies /sdcard/android_audio.mp3 as new bootsound
newbootanim - copies /sdcard/bootanimation.zip as new boot animation
bootsoundoff - turns boot sound off
bootsoundon - turns boot sound back on
Just files named accordingly on your sdcard's root i.e. 'bootanimation.zip' and 'android_audio.mp3'
Flash. Reboot. Enjoy.
Rom developers - feel free to include this in your builds if you so desire, please make sure credit is given accordingly to spiicytuna, mrdaviso, and myself.
if you're running a sense rom there's a totally different way of doing it so, should you be running sense... don't flash. or flash at your own risk, i can't guarantee the outcome.
untested... let me know if things go smoothly, the same process works for the evo g2 etc.. so shouldnt be an issue. make sure your media volume is up, some report if it's muted you wont hear it. (not sure about this, i guess it would be easy to test...)
Thanks this worked GREAT.
thanks worked great on cm7 rc2! so basically i can rename any sound file i want then overwrite the original? or does it have to be done through terminal? sorry for the ?? i am just learning
thanks again!
Terminal isn't required, but the sound you need to replace resides in /system/media so a file explorer with root access would be necessary.
not working?
i have tried this through root explorer and terminal. the outcome is correct in terminal... says that the new boot sound is there. I also was sure to check the volume. and still nothing? please help?
ya doesnt work on cm7 rc4 either
worked great for me ... except that the boot sound plays regardless of whether I have the volume down / muted / etc. before I reboot.
i'm on royalginger v1.5 which is based on cm7 nightly #31
ckisgen said:
worked great for me ... except that the boot sound plays regardless of whether I have the volume down / muted / etc. before I reboot.
i'm on royalginger v1.5 which is based on cm7 nightly #31
Click to expand...
Click to collapse
Why is it based off of #31? Just curious...
DADDYDC650 said:
Why is it based off of #31? Just curious...
Click to expand...
Click to collapse
why didn't you just IM me? el oh el
cos in my researching on the boards and also the other test builds I made - #31 was the most stable overall.
Ya can't seem to get it to work. The script seem to work fine but i think im applying the Audio file wrong can someone post an example? System/media. Running cm rc4
guys here is a manual method of unlocking boot audio...I got this from an older thread that was deleted for some odd reason..
anyway I did not make this script and I do not intend to take credit, but here is a manual way if all else fails.
1. download and rename the bootsnd.txt to bootsnd.sh and NOT bootsnd.sh.sh
2. place the file in the root of your sd card
3. use root explorer to set /system to r/w
4. open terminal type: su and hit enter to gain root priv,
5. type "cd /sdcard" with out the quotes to mount the sdcard root
6. type "sh bootsnd.sh" with out quotes and hit enter wait about 10 seconds then close terminal NOTE* YOU WILL NOT SEE ANY OUTPUT or confirmation! hit enter ONLY once unless you want to eat BOOTLOOPS for breakfast
7. with root explorer push android_audio.mp3 to /system/media
8. reboot and BOOM!
this does NOT work on sense roms, only works with AOSP (any cm builds) as far as I have tested.
I have included my own boot audio its a god of war 3 overture theme portion
now that is my work as I had to chop it up
unzip and rename it to android_audio.mp3 first before pushing it
Requirements
- Ice Cream Sandwich (Android 4.0)
- HTC Device with "Beats" software
- Root Access
SHOULD WORK ON ANY HTC DEVICE WITH BEATS
On the Stock HTC One X, Volume+ does make a difference, but the amount you can boost the volume by is minimal, as are the EQ/Bass adjustments.
While messing with some system files (as you do) I noticed that on HTC devices with 'Beats' software, the 'audio_effects.conf' file (located in 'system/etc') is different from the standard ICS version and is missing a few values. I added the missing ones back in (whilst keeping all the beats stuff intact) and after a reboot, much more EQ control!
This allows you to go louder (not much louder, HTC speakers are terrible and just distort to hell, but you can distort it to your heart's content! )
Much better for the headset EQ too!
It also works alongside Beats just fine!
Instructions
Method One (ADB)
First, Back up your 'audio_effects.conf'
Code:
adb remount
adb pull system/etc/audio_effects.conf
or
Code:
adb remount
adb mv system/etc/audio_effects.conf audio_effects1.conf
Then, extract the file from the attached zip, push the file and reboot your phone
Code:
adb push /link/to/file/audio_effects.conf system/etc/
adb shell reboot
Method Two (File Manager)
Extract the file from the attached zip and put the file on your phone's SDcard
Use Root explorer (or similar) to move the file to system/etc
(backup original file first!)
Permissions might need to be set for the new file (mine's set to "rw-rw-rw-"). Incorrect permissions can cause a Force Close
Then reboot your phone
AUDIO_EFFECTS DOWNLOAD
Few things to bear in mind:
1) Bass Boost will bug out if you turn it up too much, watch out for that
2) Volume can go up to around +14/15. Any higher any it can bug out the audio
3) Echo/Delay doesn't work on ICS
4) Volume+ WILL Force Close if installed alongside DSP Manager. Please be aware of this.
Click to expand...
Click to collapse
That's it, let me know if it works for you!
Enjoy
Cool. I'll give it a go.
From One X
Tested with professional headphones for studio. No change at all.running touch x-treme 2.1.0
smaberg said:
Tested with professional headphones for studio. No change at all.running touch x-treme 2.1.0
Click to expand...
Click to collapse
Huh, that's odd, it works fine on ARHD.
I'll have a look.
Sent from my HTC One X using xda premium
I have the ''old'' 1.8.1 on Leedroid, I set volume boost to 14 and virtual room +6, I am hearing crackling sounds before and/or after system sounds are played.
would this patch correct these?
Meltus said:
Huh, that's odd, it works fine on ARHD.
I'll have a look.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Oops, sorry it works with HTC music player, I use poweramp, but poweramp also works if you uncheck music engine in sound settings. Then also use poweramp eq to your likings.
So the file could use some more tweaking.
Is there any way to make the incall volume louder?
drizztzou said:
Is there any way to make the incall volume louder?
Click to expand...
Click to collapse
Yes - anything as we know from other ports - XLOUD.hack maybe?
all of the ringtones are very low. (speaker is undersized)
smaberg said:
Oops, sorry it works with HTC music player, I use poweramp, but poweramp also works if you uncheck music engine in sound settings. Then also use poweramp eq to your likings.
So the file could use some more tweaking.
Click to expand...
Click to collapse
If you untick 'Direct Sound' or something in the PowerAmp settings it should work fine with Volume+, DSPManager, etc.
Sent from my HTC One X using xda premium
I have a constant message "unfortunately volume+ has stopped". What I did is to rename the file in System/Etc with File Expert (first mount the volume as read/write), than copy the file from the archive in the same folder. Restart the phone and get the message above.
Manafa said:
I have a constant message "unfortunately volume+ has stopped". What I did is to rename the file in System/Etc with File Expert (first mount the volume as read/write), than copy the file from the archive in the same folder. Restart the phone and get the message above.
Click to expand...
Click to collapse
That file won't have anything to do with the force close, I don't think. What does the logcat say?
Sent from my HTC One X using xda premium
Sorry, I'm not familiar with logcat. Please let me know where to look for it?
I had volume+ installed and it opening fine and never had error messages. After put your file, the FC message appear immediately after restart.
Edit: Trying to uninstall and install again the volume+, but no success. I have the paid version, but also tried the free version - same result.
Edit2: Just delete the file and restore the original one - volume+ opening fine, no FC
Manafa said:
Sorry, I'm not familiar with logcat. Please let me know where to look for it?
I had volume+ installed and it opening fine and never had error messages. After put your file, the FC message appear immediately after restart.
Edit: Trying to uninstall and install again the volume+, but no success. I have the paid version, but also tried the free version - same result.
Edit2: Just delete the file and restore the original one - volume+ opening fine, no FC
Click to expand...
Click to collapse
You must set the right permission on the file. Rw.r.r.
I also think this should be the reason, but as not mentioned in OP I don't try to play with permissions. Thanks, Smaberg, it's working fine now. Cheers.
If you installed DSP manager it can conflict with it and do an FC
Manafa said:
I also think this should be the reason, but as not mentioned in OP I don't try to play with permissions. Thanks, Smaberg, it's working fine now. Cheers.
Click to expand...
Click to collapse
Ah, sorry, I wasn't aware incorrect permissions cause a FC. I'll amend the OP.
vegetaleb said:
If you installed DSP manager it can conflict with it and do an FC
Click to expand...
Click to collapse
Yeah, they don't play nice together.
I'll add that to the OP too
Up and running, I am already a Volume+-lover so I just installed the conf file.
Sounds great... just testing Headset and Spotify.
Eveything is louder and more bass.... and this can for sure blow out your ears
Thanks !
Works fine, many THX.....but my problem on One X is that phone calls Sounds and SMS Notifications are really quiet (someone told same before), is there any chance to set volume higher on that!?
Petteri said:
Works fine, many THX.....but my problem on One X is that phone calls Sounds and SMS Notifications are really quiet (someone told same before), is there any chance to set volume higher on that!?
Click to expand...
Click to collapse
Raising the Volume Level under "Speaker" should make it louder. It will probably just distort horribly if you go much louder than stock though
Works good for me... I've been using volume+ since my DHD cheers
Hello fellas
This guide is just a quick how-to CHANGING current audio sound on ICS 4.0.3 and other sound.
DISCLAIMER: THESE TUTORIALS HAS BEEN TASTED ONLY WITH ROOT ICS 4.0.3. STOCK ROM. I WON'T TAKE ANY RESPONSIBILITY IF YOU MESS UP AND BRICK YOUR DEVICE OR ANYTHING ELSE. DO AT YOUR OWN RISK!!!!! Don't forget to NANDROID before trying anything!
So let's get started.
Requirements
1.ROOTED GT-I9100
2.APPS “ROOT EXPLORER (File Manager )” installed on your device. (find in Google Play)
3. “.ogg” audio file. [<60KB size] (if you have other than this file please convert to .OGG audio file first. Use “audio converter” )
4. Audio converter.
What you need to do : “CHANGING CAMERA SOUND”
1.Connect your device to pc
2.RENAME your own .ogg audio file to “Shutter_01.ogg”
3.Copy the “Shutter_01.ogg” file to INT SD/EXT SD where u can find it.
4.Removed usb.
5.ON your device go to ROOT EXPLORER/system/media/audio/ui/
6.Find “Shutter_01.ogg” MOUNT R/O then move to out side (incase you wana use it back)
7.Find your own “Shutter_01.ogg” move to ui to replaced “Shutter_01.ogg”
8.Exit root explorer RESTART your device…
9.You are done….
TEST TOUR CAMERA SOUND AND GIFT ME FEED BACK
RENAME YOUR AUDIO FILE TO THIS IF YOU WANA CHANGE OTHER SOUND
1.TW_Touch.ogg = touch sound
2.Unlock.ogg = Screen Unlock sound
3.Lock.ogg = Screen Lock sound
4.Charger_Connection.ogg = charger connection sound
5.camera_click.ogg = Screenshots sound
Give me your feedback so that I can improve this tutorial. And post here about how your build went. All the best.
Don't forget to hit THANKS if you like my work
I have asked previously on how to enable sound on custom boot animations and was told to just paste the ogg sound file in the corresponding system/ui folder but even after doing that the sound still does not work is there something I'm missing? I have even tried changing the file permissions to match all the other system files (rw-r-r) if that even does anything.
I would like to enable boot sound because there are several custom boot animations that have great accompanying sounds, but since basically every custom rom disables bootup sound I cant enjoy the hard work that was put into making these awesome custom bootups
How to stop the annoying click sound or change it on Amazon Fire Tv
Do you hate or love the click sound when moving around on the Fire Tv? Well if like me you can't stand that annoying sound, I will tell you how to remove that "click" or replace for a sound of your own? This has been tested on my AFTV2 but Im 99.9 % sure it will work on Gen 1 & the Fire Sticks too (I will try on my Fire Stick later) as long as you have root access.
PLEASE READ
This process needs root access & make sure you only change the file I'm talking about, I will not be responsible if you brick your device by being silly & deleting dependable files on your Fire Tv, I advice you don't delete it just incase then If you need to go back you can change or rename with adb. If you want to make a backup with twrp recovery you can back as far as I can see this process Is safe to do & I have tested & have not had any problems (so far).
Steps-
1. Using a file manager goto system/media/audio/ui
2. Select Mount R/W if you haven't already so you have authority to write to the device
3. Select, tick or change the Effect_Tick.ogg file & press rename
4. Rename as Effect_Tick.ogg.bac
5. Exit the file manager & now reboot the device using the select & the play/pause buttons held down together for about 5 or 6 seconds
6. Now a message will flash Up saying something like Effect_Tick.ogg not working or something similar? (Don't panic)
7. Once rebooted the annoying click has gone!
Replacing for a blank file
I have included a download of blank audio which i named Effect_Tick.ogg (just needs to be unziped) if you just replace this with the old sound or .bac the original & push this ogg file in the location system/media/audio/ui & then reboot you will have a non clicking scroll & also wont get any error Effect_Tick.ogg not working messages.
Bringing the click back
If you want to bring the click back, go back into system/media/audio/ui & delete the .bac part at the end of the name so it's Effect_Tick.ogg once again, reboot & it's back.
Changing the click for a different/custom sound
Or after you have done step 4 you could copy a audio file In the ogg format & name it Effect_Tick.ogg & then reboot