Related
Hey gang any way to Disable annoying startup/rebooting sound, with root manager I manage to remove most of the unwanted app that came with the vibrant, I wonder if anybody has figure out how to remove sound ?
Thank you all in advanced.
Settings>Sound and display>System volume
Turn all the way down.
Just FYI this also turns off the annoying click noises in some of the UI elements when clicking them.
bchalk said:
Settings>Sound and display>System volume
Turn all the way down.
Just FYI this also turns off the annoying click noises in some of the UI elements when clicking them.
Click to expand...
Click to collapse
thanks for the tip
You should be able to remove the sound by removing the file /system/etc/PowerOn.wav
Hope that helps
Awesome..
Thank you both..
FYI, Turning system sounds all the way down also disables the camera shutter sound. Removing the .wav file is the best way but you need root.
Step by step directions to get rid of annoying startup and shutdown sounds on Vibrant
suchaputz said:
You should be able to remove the sound by removing the file /system/etc/PowerOn.wav
Click to expand...
Click to collapse
Standard disclaimer: YMMV, etc. And assuming a rooted phone.
Using Terminal Emulator (is something better?) and the Android keyboard (the erase on the Swype keyboard doesn’t work in this app) I first:
su -
Then I do this (it is easier for me to cd multiple times):
cd system
cd etc
mv PowerOn.wav notPowerOn.wav
Actually I made it 0 length, momentarily forgetting to be careful, but it works.
To get rid of the Very Loud power off sound I unfortunately was still forgetful and made it zero length and the phone hung at “Goodbye!”. I had to pull the battery.
Fortunately, merely getting rid of the file works fine (as does copying something to the filename).
Try this to get rid of the shutdown noise:
cd system
cd media
cd audio
cd ui
mv Shutdown_128.ogg notShutdown_128.ogg
suchaputz said:
You should be able to remove the sound by removing the file /system/etc/PowerOn.wav
Hope that helps
Click to expand...
Click to collapse
thanks... Do you know the name/location for the poweroff wave?
/system/media/audio/ui/Shutdown_128.ogg
Astitious said:
/system/media/audio/ui/Shutdown_128.ogg
Click to expand...
Click to collapse
thanks,
so, poweron is a wave and shutdown is an ogg? Wonder why they used to different formats and stored them in different locations.
so following the logic of this thread, if i put my own sound files with the same name as the orginal, it should work, right? what about boot animations, is there an easy way to replace or customize those?
Put the phone in silent mode before shutting down once booted up (no sound will be heard on shut-down or boot-up). Of course you will need to turn silent mode off if you want ringing when phone is active.
Sent from my SGH-T959 using XDA App
Yup. They are using some file system with the extension .qmg to tie into the png's, but you can (one of the first things i did) change the bootup and shutdown sounds by simply replacing the stock files with something more to your liking
PhilSlater said:
Standard disclaimer: YMMV, etc. And assuming a rooted phone.
Using Terminal Emulator (is something better?) and the Android keyboard (the erase on the Swype keyboard doesn’t work in this app) I first:
su -
Then I do this (it is easier for me to cd multiple times):
cd system
cd etc
mv PowerOn.wav notPowerOn.wav
Actually I made it 0 length, momentarily forgetting to be careful, but it works.
To get rid of the Very Loud power off sound I unfortunately was still forgetful and made it zero length and the phone hung at “Goodbye!”. I had to pull the battery.
Fortunately, merely getting rid of the file works fine (as does copying something to the filename).
Try this to get rid of the shutdown noise:
cd system
cd media
cd audio
cd ui
mv Shutdown_128.ogg notShutdown_128.ogg
Click to expand...
Click to collapse
Great tip, thanks!
PhilSlater said:
Standard disclaimer: YMMV, etc. And assuming a rooted phone.
Using Terminal Emulator (is something better?) and the Android keyboard (the erase on the Swype keyboard doesn’t work in this app) I first:
su -
Then I do this (it is easier for me to cd multiple times):
cd system
cd etc
mv PowerOn.wav notPowerOn.wav
Actually I made it 0 length, momentarily forgetting to be careful, but it works.
To get rid of the Very Loud power off sound I unfortunately was still forgetful and made it zero length and the phone hung at “Goodbye!”. I had to pull the battery.
Fortunately, merely getting rid of the file works fine (as does copying something to the filename).
Try this to get rid of the shutdown noise:
cd system
cd media
cd audio
cd ui
mv Shutdown_128.ogg notShutdown_128.ogg
Click to expand...
Click to collapse
this is not working for me, it keeps on saying read-only file system.
i have root and terminal is whitelisted. i also tried chmod to 777 but i cannot, getting the same error message. any ideas?
ultraman69 said:
this is not working for me, it keeps on saying read-only file system.
i have root and terminal is whitelisted. i also tried chmod to 777 but i cannot, getting the same error message. any ideas?
Click to expand...
Click to collapse
Prior to making changes to this file did you type 'su' ?
You have to be superuser to mess with these files.
su
cd system
cd etc
mv PowerOn.wav notPowerOn.wav
cd system
cd media
cd audio
cd ui
mv Shutdown_128.ogg notShutdown_128.ogg
Click to expand...
Click to collapse
Wow. Thank you for posting this. Got rid of those suckers straight-away!!!
You know... I don't mind a subtle boot-up or shutdown sequence + sound, but T-Mo has historically installed the loudest/longest files that they can find. The shutdown sound especially was REALLY, REALLY loud. Honestly... stop it, T-Mo!
Anyhow, glad it's easy enough to "fix"
This should really be in the sticky. The sounds are damned annoying...
yipcanjo said:
Wow. Thank you for posting this. Got rid of those suckers straight-away!!!
You know... I don't mind a subtle boot-up or shutdown sequence + sound, but T-Mo has historically installed the loudest/longest files that they can find. The shutdown sound especially was REALLY, REALLY loud. Honestly... stop it, T-Mo!
Anyhow, glad it's easy enough to "fix"
Click to expand...
Click to collapse
They sure do. lol
Does anyone have the poweron.wav for the i9000?
Hi,
there an app to change hdmi output resolution? Or a custom Rom that supports it?
elgar said:
Hi,
there an app to change hdmi output resolution? Or a custom Rom that supports it?
Click to expand...
Click to collapse
[How-To] HDMI Fullscreen Toggle Script
The script has a resolution argument, although 1920x1080 and 2560x1440 are the only ones I have ever heard used with a N10. The script can be run manually from a terminal session or if you can install SManager through a shortcut icon on the desktop. See issues with SManager here.
3DSammy said:
[How-To] HDMI Fullscreen Toggle Script
The script has a resolution argument, although 1920x1080 and 2560x1440 are the only ones I have ever heard used with a N10. The script can be run manually from a terminal session or if you can install SManager through a shortcut icon on the desktop. See issues with SManager here.
Click to expand...
Click to collapse
Thank you very much. I looked at the thread, but can't understand, how do I change resolution to a different one for my monitor?
elgar said:
Thank you very much. I looked at the thread, but can't understand, how do I change resolution to a different one for my monitor?
Click to expand...
Click to collapse
Both the script and raw commands require a terminal emulator app so make sure one is installed. Android Terminal Emulator
Here are the raw resolution change commands if you want to try them yourself. Each needs to be entered at the command line prompt so you always at least need a terminal emulator app.
1) Set screen resolution to 1920x1080:
am display-size 1920x1080
2) Set screen resolution to 2560x1440:
am display-size 2560x1440
3) Reset screen resolution:
am display-size reset
To use the "hdmi_toggle.sh" script in a terminal session:
On a PC:
1) Copy the script directly from the post.
2) Then paste it into a text editor and save with the name "hdmi_toggle.sh"
On your N10:
3) Copy the "hdmi_toggle.sh" script to some directory on your N10.
Running the HDMI toggle script:
a) Open the terminal session emulator app on your N10
b) At the command prompt create a directory for the toggle state file:
mkdir "/scdard/hdmi_toggle"
c) At the command prompt enter (replace the "/directory/ to script/" with the scripts location)
cd "/directory/ to script/"
d) Run the script by entering at the command prompt:
sh ./hdmi_toggle.sh "/scdard/hdmi_toggle" "1920x1080"
The resolution on the N10 should have changed.
e) To return to your original N10 resolution repeat the command in "d"
sh ./hdmi_toggle.sh "/scdard/hdmi_toggle" "1920x1080"
You will not need to do step "b" after the first time as the directory is already created.
This looks like a pain but it is much easy if the script is combined with SManager as explained in the thread. For those without SManager the pain is limited as I do not suspect people will use HDMI a lot.
3DSammy said:
[How-To] HDMI Fullscreen Toggle Script
The script has a resolution argument, although 1920x1080 and 2560x1440 are the only ones I have ever heard used with a N10.
Click to expand...
Click to collapse
Can half the native resolution too (1280x800) and it'll work fine.
3DSammy said:
Both the script and raw commands require a terminal emulator app so make sure one is installed. Android Terminal Emulator
Here are the raw resolution change commands if you want to try them yourself. Each needs to be entered at the command line prompt so you always at least need a terminal emulator app.
1) Set screen resolution to 1920x1080:
am display-size 1920x1080
2) Set screen resolution to 2560x1440:
am display-size 2560x1440
3) Reset screen resolution:
am display-size reset
To use the "hdmi_toggle.sh" script in a terminal session:
On a PC:
1) Copy the script directly from the post.
2) Then paste it into a text editor and save with the name "hdmi_toggle.sh"
On your N10:
3) Copy the "hdmi_toggle.sh" script to some directory on your N10.
Running the HDMI toggle script:
a) Open the terminal session emulator app on your N10
b) At the command prompt create a directory for the toggle state file:
mkdir "/scdard/hdmi_toggle"
c) At the command prompt enter (replace the "/directory/ to script/" with the scripts location)
cd "/directory/ to script/"
d) Run the script by entering at the command prompt:
sh ./hdmi_toggle.sh "/scdard/hdmi_toggle" "1920x1080"
The resolution on the N10 should have changed.
e) To return to your original N10 resolution repeat the command in "d"
sh ./hdmi_toggle.sh "/scdard/hdmi_toggle" "1920x1080"
You will not need to do step "b" after the first time as the directory is already created.
This looks like a pain but it is much easy if the script is combined with SManager as explained in the thread. For those without SManager the pain is limited as I do not suspect people will use HDMI a lot.
Click to expand...
Click to collapse
Thanks a lot! I have tried also "am display-size" command. It also changes the resolution. Does the script work the same?
P.S. Never mind. Just found an answer.
HDMI resolution changer app
I quickly put together this app that changes the resolution when the HDMI cable is plugged / unplugged.
It also uses the am display-size commands and requires su permission. The default resolution is set to 2560x1440 when HDMI is plugged in and can be adjusted in the app.
https://docs.google.com/file/d/0B8C1BFemNlbzS196YTlDNmFSQ3c/edit?usp=sharing
The only annoying thing is when changing to 1920x1080 (at least through terminal) is that your phone gets reset to phone mode so you lose on-screen buttons as well as ruin your launcher (Apex). If you do a am display-size reset you get the on-screen nav buttons back but it's still phone mode, meaning you'll only have them on the right-hand side in portrait.
At least in CM10.1/AOSP. Bit better with AOSPA since you can change it on the fly, but AOSPA has horrible performance if you're doing two displays + gaming.
sbradymobile said:
I quickly put together this app that changes the resolution when the HDMI cable is plugged / unplugged.
It also uses the am display-size commands and requires su permission. The default resolution is set to 2560x1440 when HDMI is plugged in and can be adjusted in the app.
https://docs.google.com/file/d/0B8C1BFemNlbzS196YTlDNmFSQ3c/edit?usp=sharing
Click to expand...
Click to collapse
Wow, thanks! I'll check out when I have a chance!
espionage724 said:
Can half the native resolution too (1280x800) and it'll work fine.
Click to expand...
Click to collapse
Which screen density do I put if my screen resolution is 1440*900? What's the formula?
sbradymobile said:
I quickly put together this app that changes the resolution when the HDMI cable is plugged / unplugged.
It also uses the am display-size commands and requires su permission. The default resolution is set to 2560x1440 when HDMI is plugged in and can be adjusted in the app.
https://docs.google.com/file/d/0B8C1BFemNlbzS196YTlDNmFSQ3c/edit?usp=sharing
Click to expand...
Click to collapse
this app is requesting permission to almost everything on your tablet...
elgar said:
Which screen density do I put if my screen resolution is 1440*900? What's the formula?
Click to expand...
Click to collapse
Desired width / actual width (2560) * actual density (320). So in the case of 1440x900 it would be 180.
mrruin said:
this app is requesting permission to almost everything on your tablet...
Click to expand...
Click to collapse
That is for the superuser access permission; all apps that use su should have that warning. Code is available here if you would like to take a look: https://github.com/sbradymobile/HDMIRes.
This app works really well. But for some reason hdmi out doesn't work on my 19 inch LG monitor.
Is it possible to have a non-root requirement for such an on-off app?
I can do terminal trick non root so hoped it would be doable. Cheers anyway
Sent from my Nexus 7
sbradymobile said:
I quickly put together this app that changes the resolution when the HDMI cable is plugged / unplugged.
It also uses the am display-size commands and requires su permission. The default resolution is set to 2560x1440 when HDMI is plugged in and can be adjusted in the app.
https://docs.google.com/file/d/0B8C1BFemNlbzS196YTlDNmFSQ3c/edit?usp=sharing
Click to expand...
Click to collapse
This great app stopped working in 4.3.
Can you please fix it?
Animor said:
This great app stopped working in 4.3.
Can you please fix it?
Click to expand...
Click to collapse
Here is a link to the update.
https://docs.google.com/file/d/0B8C1BFemNlbzai14Z3ZtckQ5X2s/edit?usp=sharing
sbradymobile said:
Here is a link to the update.
https://docs.google.com/file/d/0B8C1BFemNlbzai14Z3ZtckQ5X2s/edit?usp=sharing
Click to expand...
Click to collapse
Thank you.
I get an error message when trying to install it:
There was a problem parsing the package.
Click to expand...
Click to collapse
Animor said:
Thank you.
I get an error message when trying to install it:
Click to expand...
Click to collapse
I just put up a new signed package at the same link; let me know if you have problems installing it.
Package is fine now, thank you!
sbradymobile said:
I just put up a new signed package at the same link; let me know if you have problems installing it.
Click to expand...
Click to collapse
Hi,
I have checked the app and there are few problems with it:
1. When disconnecting the HDMI cable, resolution didn't change back to original. I had to reboot the N10.
2. I have set HDMI resolution to 1920x1080, but for some reason it didn't display correctly on my 1080p TV. The picture was cut/cropped a bit.
Please assist...
Hello,
I have galaxy note 2 (n7100) international version and im running OmniRom 4.4.2 (31-3-2014)
the rom is great but charging the battery takes alot of time( way too long than normal ),i have flashed several stock /costumed rom and i didnt encounter this problem......
if im writing in the wrong section please provide me with a link so i can report my problem
Thanks in advance
If your device is rooted try to manually apply the charging currency using terminal emulator, adb shell, or so:
Code:
echo "1800" > /sys/devices/platform/samsung-battery/dcp_ac_input_curr
echo "1700" > /sys/devices/platform/samsung-battery/dcp_ac_chrg_curr
dcp_ac_input_curr defines the maximum input, dcp_ac_chrg_curr defines the currency at which your battery will be loaded. If this loads your device faster, some app or OmniROM sets lower values for those variables. If not, I don't know. Make sure you are executing these commands as root.
klenamenis said:
If your device is rooted try to manually apply the charging currency using terminal emulator, adb shell, or so:
Code:
echo "1800" > /sys/devices/platform/samsung-battery/dcp_ac_input_curr
echo "1700" > /sys/devices/platform/samsung-battery/dcp_ac_chrg_curr
dcp_ac_input_curr defines the maximum input, dcp_ac_chrg_curr defines the currency at which your battery will be loaded. If this loads your device faster, some app or OmniROM sets lower values for those variables. If not, I don't know. Make sure you are executing these commands as root.
Click to expand...
Click to collapse
Hey klenamenis, thanks for that. Is there a noob way to check whatever you mentioned here? I have the same problem and i can't really understand what is it i could do.
Sent from my GT-N7000 using Tapatalk
nihilist_bloke said:
Hey klenamenis, thanks for that. Is there a noob way to check whatever you mentioned here? I have the same problem and i can't really understand what is it i could do.
Click to expand...
Click to collapse
Install this app, open it and type in the following commands and post both outputs here:
PHP:
echo /sys/devices/platform/samsung-battery/dcp_ac_input_curr
echo /sys/devices/platform/samsung-battery/dcp_ac_chrg_curr
Just out of curiosity I enter the commands in a Android terminal emulator ,
su -
echo /sys/devices/platform/samsung-battery/dcp_ac_input_curr
and got nothing in return... no value only the echo...
When i do the echo "1800" > /sys/....
command
I get a file not found error.
what's doing this noob wrong?
Sent from my GT-N7100 using xda app-developers app
I'm also having this issue, very frustrating. I recently bought two new Galaxy Note 2 charge at a rate of anywhere from 200-800 mAh, when the amount they should be charging is 1800 mAh. Looking for a fix.
When entering the above command, I also get an error.
CyD13 said:
I'm also having this issue, very frustrating. I recently bought two new Galaxy Note 2 charge at a rate of anywhere from 200-800 mAh, when the amount they should be charging is 1800 mAh. Looking for a fix.
When entering the above command, I also get an error.
Click to expand...
Click to collapse
Sorry to hear that, Mine works fine,
Hi,
to find your Panel manufaturer ID do the following via ADB or Terminal (Note: enter it after fresh boot, the kernel log gets flooded with useless stuff very quick):
Code:
dmesg | grep -i mdss_dsi_panel_init
The output will be something like:
Code:
mdss_dsi_panel_init: Panel Name = 9
Available Panel Types
jdi_novatek_hd_cmd_panel (Panel Name = 9)
lgd_novatek_hd_cmd_panel (Panel Name = 8)
somc,default_panel_0 (Panel Name = default)
somc,default_panel_1 (Panel Name = default)
Without root permission denied?
Sent from my iPad using Tapatalk
@Tommy-Geenexus
Cool Bro!
JDI = JVC
LGD = LG display
And default is... "default"?
Lol how do we know what's the "default" manufacturer?
Regards
mele80 said:
Without root permission denied?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Try via adb shell (adb shell dmesg). This works fine for me without root.
langeveld024 said:
@Tommy-Geenexus
Cool Bro!
JDI = JVC
LGD = LG display
And default is... "default"?
Lol how do we know what's the "default" manufacturer?
Regards
Click to expand...
Click to collapse
Nope, JDI = Japan Display Inc, but LGD is LG (don't know for sure).
The default one is prob. not used in shipping units
Tommy-Geenexus said:
Nope, JDI = Japan Display Inc, but LGD is LG (don't know for sure).
The default one is prob. not used in shipping units
Click to expand...
Click to collapse
Thanks!
Is it possible related to colour and/or buying location and such? (as I've read everyone is talking about)
langeveld024 said:
Thanks!
Is it possible related to colour and/or buying location and such? (as I've read everyone is talking about)
Click to expand...
Click to collapse
I honestly can't tell, but it may or may not be, only a Sony representative can answer that
Returns nothing here when used via ADB. A manual dmesg check also gives nothing.
I got number 9. Do they differ in quality?
Random Username said:
I got number 9. Do they differ in quality?
Click to expand...
Click to collapse
Can't tell so far. People who returned their Z5C to get a new one could check which Panel they got and report any differences.
Im kinda noob when it comes to ADB controles, so any ''detailed'' step by step guide for entering commands to check this thing? I ender adb shell and when i enter the command from the OP i get nada. Help?
Tommy-Geenexus said:
Hi,
to find your Panel manufaturer ID do the following via ADB or Terminal:
Code:
dmesg | grep -i mdss_dsi_panel_init
Click to expand...
Click to collapse
You should probably mention that this will work quite early after system start.
dmesg log is cluttered rather quickly and shows only recent records. That's why some people report nothing in the output.
Back to the topic, I have 9 for the phone bought in central Europe. So, this will be probably most dominant display for EU region.
bubimir13 said:
Im kinda noob when it comes to ADB controles, so any ''detailed'' step by step guide for entering commands to check this thing? I ender adb shell and when i enter the command from the OP i get nada. Help?
Click to expand...
Click to collapse
Turn on usb-debugging, enter adb shell and the command above. Thats it.
OtaruM said:
You should probably mention that this will work quite early after system start.
dmesg log is cluttered rather quickly and shows only recent records. That's why some people report nothing in the output.
Back to the topic, I have 9 for the phone bought in central Europe. So, this will be probably most dominant display for EU region.
Click to expand...
Click to collapse
Yeah you're right, the log get's cluttered pretty easy, working on that already on my Kernel.
Added it to the OP.
also got 9. And also an CE1 version (Croatia). Guess this is going to be a standard for most of Europe.
panel 9 here as well, anyone actually gotten the LG panel? Might just be testing hardware or similar?
Panel 9 here as well...
mdss_dsi_panel_init: Panel Name = 8
report by my Xperia Z5 Compact White
bought in 2015/10/3 in Taipei, Taiwan
mdss_dsi_panel_init: Panel Name = 9
z5c black Germany.
Display has a slight shadow topside that is most noticeable during boot when the white animation is playing.
Panel 9
E5823 Black Italy Rev3
Is there any way to decrease the minimum time for Wear to enter Wifi power save mode? The lowest is 15 minutes, I'd think something like five or lower would be more useful in most cases.
Hi
[NUMINIT] said:
Is there any way to decrease the minimum time for Wear to enter Wifi power save mode? The lowest is 15 minutes, I'd think something like five or lower would be more useful in most cases.
Click to expand...
Click to collapse
Most likely inside an SQLite DB. Like this one:
Code:
/data/data/com.android.providers.settings/databases/settings.db
ranf said:
Most likely inside an SQLite DB. Like this one:
Code:
/data/data/com.android.providers.settings/databases/settings.db
Click to expand...
Click to collapse
It's there, thanks! Now to figure out what the value "2" means on wifi_sleep_policy...
Never mind, there's no entry for that. Seems to be pretty hard to change...
You have root? busybox installed? Then we might have a look at the output from:
Code:
busybox find /data/data/ '*.db'
ranf said:
You have root? busybox installed? Then we might have a look at the output from:
Code:
busybox find /data/data/ '*.db'
Click to expand...
Click to collapse
Oh, I did find settings.db, but there's no entry for the power save timer within the file.
There's a ton of redundant data, though, my God...