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, I am thinking of buying Nexus 7, but I would really like to have some way to stream it's display to at least computer. That can be most easily (well, more like the most primitive way) by sending content of framebuffer via wifi. That however requires the framebuffer to be accessible and reasonably big (eg. small).
Now, I do not have it yet, and I do not know anybody who has it, so I am asking you to get some info about framebuffer for me. It will not take more than 5 minutes and only things you need is ADB and root.
So, if you decided to help me, thank you, and let's get started.
I want you to just run several commands on your device under root and then send me the result files.
1. Device permissions
Code:
ls -l /dev > /sdcard/xda_tass.txt
ls -l /dev/graphics >> /sdcard/xda_tass.txt
These two commands will tell me what device files are available on N7 and their permissions. The output is saved to file on sdcard (well, I hope the memory in N7 is called /sdcard. If not, just change it to some existing path).
2. Testing the framebuffer
Code:
time (cat /dev/graphics/fb0 > /dev/null) >> /sdcard/xda_tass.txt 2>&1
This command will tell me how long does it take to read framebuffer. Run it 3-5 times, so that I have some average values. If "/dev/graphics/fb0" does not exist, try "/dev/fb0".
Code:
cat /dev/graphics/fb0 > /sdcard/xda_tass.dat
Copies the framebuffer into file, so that I know how big it is and which format does it have. This is like taking screenshot, so make sure there is not something embarrassing on your display
3. Send me the files
Take files "xda_tass.txt" and "xda_tass.dat", ZIP em' up and put it somewhere. That is all.
I would be really glad if somebody could do that for me, thanks
Here you go
http://db.tt/3WBr5BWK
Also the sdcard is now /storage/sdcard0, yeah idk why
Sent from my Nexus 7 using Tapatalk 2
Thank you
Looks okay, even though the framebuffer is huge. Well, I suppose it is not a problem to compress it on that quad-core craziness. And, it has two framebuffers (fb0 and fb1) - I wonder why.
Also, I cannot decode data from that framebuffer. Could you please get me also the second framebuffer?
Code:
cat /dev/graphics/fb1 > /storage/sdcard0/xda_tass_fb1.dat
Tasssadar said:
Thank you
Looks okay, even though the framebuffer is huge. Well, I suppose it is not a problem to compress it on that quad-core craziness. And, it has two framebuffers (fb0 and fb1) - I wonder why.
Also, I cannot decode data from that framebuffer. Could you please get me also the second framebuffer?
Code:
cat /dev/graphics/fb1 > /storage/sdcard0/xda_tass_fb1.dat
Click to expand...
Click to collapse
Here you go
http://db.tt/Nt6kBM83
Sent from my Nexus 7 using Tapatalk 2
Data from fb1 look about as random as those from fb0 to me. Gonna need some more samples, but I can do that by myself once I'll have my own N7.
Thanks for helping me
Tasssadar said:
Data from fb1 look about as random as those from fb0 to me. Gonna need some more samples, but I can do that by myself once I'll have my own N7.
Thanks for helping me
Click to expand...
Click to collapse
No problem lol
Sent from my Jelly Nexus S
@Tasssadar how did you decode the framebuffer? I'm actually trying to get a screenshot of MultiROM, but I can't figure out how to decode it. I'm trying to open it with GIMP by changing the settings and moving the width value, but I can't get a clear image.
Your signature says you have the 2013 Nexus 7. MultiROM doesn't use framebuffer on that device because of severe kernel driver bug. You can still take screenshots though - tap on the screen with four fingers at once. The screen should flash and screenshot will be saved to /sdcard/multirom/ (accessible in Android only with root in /data/media/0/multirom).
The format should be RGB Alpha and the dimensions should be 1200x1920.
Tasssadar said:
Your signature says you have the 2013 Nexus 7. MultiROM doesn't use framebuffer on that device because of severe kernel driver bug. You can still take screenshots though - tap on the screen with four fingers at once. The screen should flash and screenshot will be saved to /sdcard/multirom/ (accessible in Android only with root in /data/media/0/multirom).
The format should be RGB Alpha and the dimensions should be 1200x1920.
Click to expand...
Click to collapse
Damn, you put so many easter eggs in MultiROM
That's interesting though... That's why when pulling the framebuffer I only got a black screen. In the recovery, instead, I could get something "visible" (still not the actuall image, though).
@Tasssadar Is it still possible to take screenshots on the new multirom for flo? When I tap with four fingers nothing happens.
Since v27, screenshots are taken with power+volume down combo like in Android ( you have to press power button first though, cause I'm lazy). They are also saved as PNG instead of raw data, and they are in folder /sdcard/Pictures/Screenshots like Android screenshots. I mentioned it in the changelog
Please remember to make a backup image of your phone before experimenting.
============ WARNING!! =============
The highest setting is VERY loud (as I found out) and could potentially rip apart the speaker on your phone!
Exercise extreme caution when using this. You risk permanent damage to your phone and your ears.
2013-Jan-20
-----------------
Thanks xda-developers members "skvalex" who wrote ALSAMixer and "chdlock" who is helping me figure out
how ALSA is mapping the audio chipset, we can now temporarily adjust the Digital Volume on the Nexus 4.
Unfortunately, the selected volume doesn't "stick" because the audio driver re-writes it every time it re-opens an audio stream.
A stream is usually opened when a music track begins to play so then the digital volume will reset back to default.
We need a kernel developer to modify the audio driver so it opens an audio stream using a user-selected Volume level.
***
If you don't mind setting the volume frequently or just want to try this out here's what you need:
1) Get ALSAMixer from the Play Store. It was updated recently and you need the latest version.
Please consider a donation to the author.
2) You can re-program the audio chipset by editing fields in ALSAMixer. Here is a list of what we can control so far.
Headphones volume:
Left: RX1 Digital Volume (numid=27)
Right: RX2 Digital Volume (numid=28)
Speaker volume:
RX3 Digital volume (numid=29)
Camcorder volume:
DEC6 Volume (numid=39)
Microphone volume:
DEC7 Volume (numid=40)
-----------------------------------------------
old OPs
-----------------------------------------------
2013-Jan-15
----------------
The creator of ALSAMixer updated it to correctly install for Nexus4. (Uninstall removes the app but the ALSA libraries remain on the phone.)
https://play.google.com/store/apps/details?id=com.skvalex.alsamixer&hl=en
Thank you so much!
--------
http://forum.xda-developers.com/attachment.php?attachmentid=1653124&d=1358438577
This is a piped output of "alsa_amixer -c 0 contents" from a stock Nexus 4 (4.2.1)
2013-Jan-13
-----------------
Is anyone successfully running ALSA on their Nexus 4?
If you do please share instructions to do so.
I am on stock 4.2.1(rooted/busybox) and I ran the AlsaMixer from
the Play Store but it doesn't seem to complete the installation.
http://forum.xda-developers.com/sho...ited Edition Kit★☆★ | aokp,minco,pa,rasbean |
Shameless promotion
Sent from my Nexus 4
Next you're going to tell me that you want systemd and PulseAudio on your device too, right?
I wiped to stock,
I installed AOKP-jb-mr1-build1,
then Nocturnal 1.4 LE for AOKP
and the ALSAMixer still doesn't work. It installs but I get the same blank screen with no settings.
What am I doing wrong?
I'm not sure what that app is, I just meant that some of the audio mods in the kit ROM referred to ALSA audio libs.
As you can tell I'm not the expert, sorry if that's not what you were referring too
Sent from my Nexus 4
I am looking for a way to control the audio stream parameters in particular the gain of the microphone.
Somebody suggested using ALSA and I'm trying get it going.
-Mindroid- said:
I am looking for a way to control the audio stream parameters in particular the gain of the microphone.
Somebody suggested using ALSA and I'm trying get it going.
Click to expand...
Click to collapse
I have only a Nexus 7, and the SoC is different from the Nexus 4, but look for alsa_amixer (installed by AlsaMixer) from within a console and execute
"alsa_amixer -c X contents" (without the quotes)
where X is one of the card numbers shown in your /proc/asound directory (e.g. card0 [X=0], card1 [X=1], etc). In my case, X=1 is the actual card where (a lot of) values can be set. One of those values is called "ADC Boost Gain"(I guess a programmable analog gain?).
I established a call with CSipSimple and successfully raised that parameter by 24dB in mid-call by executing "alsa_amixer -c 1 cset numid=20 2" [the default value was 0 and each step increases the level by 12dB]
You can query individual parameters by executing alsa_amixer -c X cget numid=Y
YMMV with the Nexus 4. Good luck!
Thank you! This looks really promising.
I only have "card0" aka [apq8064tablasnd].
When trying to execute "alsa_mixer -c 0 contents" I get an error stating that I'm missing
library "libasound.so". Any ideas what could be wrong?
I'm not sure whether libasound.so came with the AlsaMixer app. If it did you may need to copy the library into a system library path, e.g. /system/lib. If not, I could send you the library that I have. I actually forgot whether I found the library somewhere online or whether I cross-compiled it myself...
Sent from my Nexus 7 using xda app-developers app
ALSA on Nexus 4 sound capabilities
ALSAMixer in the Play Store was updated to support Nexus 4. See OP.
---------------------------------------------------------------
The attached file is the output of running
alsa_amixer -c 0
I'm new to ALSA and have trouble figuring out which one is the microphone gain control.
I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.
amarb70 said:
I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.
Click to expand...
Click to collapse
If I understand correctly the app is just an installer that puts the ALSA libraries on your system.
If you are not using them it probably doesn't matter if they are there or not. You can contact the app creator about it.
-Mindroid- said:
ALSAMixer in the Play Store was updated to support Nexus 4. See OP.
---------------------------------------------------------------
The attached file is the output of running
alsa_amixer -c 0
I'm new to ALSA and have trouble figuring out which one is the microphone gain control.
Click to expand...
Click to collapse
Post the output of
alsa_amixer -c 0 contents
Any labels containing "ADC gain" or "Boost" would be prime candiates
amarb70 said:
I have installed this app but unfortunately I don't know how to completely uninstall it help please?:thumbup:
..sent from space.
Click to expand...
Click to collapse
Restore your back up
Sent from my Nexus 4 using xda premium
alsa_amixer c- 0 contents
chdloc said:
Post the output of
alsa_amixer -c 0 contents
Any labels containing "ADC gain" or "Boost" would be prime candiates
Click to expand...
Click to collapse
Thank you for being so patient with me!
I'm such a Linux noob. It took me forever to figure out that I need 'su' to do anything.
I will update the OP to link to this file.
-Mindroid- said:
Thank you for being so patient with me!
I'm such a Linux noob. It took me forever to figure out that I need 'su' to do anything.
I will update the OP to link to this file.
Click to expand...
Click to collapse
Holy smokes! This is one complicated mixer! And I've seen many.
It may help in narrowing choices down by you capturing another
alsa_amixer -c 0 contents
while you are on a call and look at the diffs. While you do that (being on a call, but don't run anything else that may use audio such as music playback apps) also report the output of
cat /proc/asound/card0/pcm0p/sub0/status
to make sure that phone calls are actually routed through ALSA. Anything but "CLOSED" is good.
I do not have a Nexus 4 so I cannot help trying to find the best parameters for a given application. The app ALSAMixer should help I would think.
Does this program now actually display anything?
chdloc said:
Holy smokes! This is one complicated mixer! And I've seen many.
It may help in narrowing choices down by you capturing another
alsa_amixer -c 0 contents
while you are on a call and look at the diffs. While you do that (being on a call, but don't run anything else that may use audio such as music playback apps) also report the output of
cat /proc/asound/card0/pcm0p/sub0/status
to make sure that phone calls are actually routed through ALSA. Anything but "CLOSED" is good.
I do not have a Nexus 4 so I cannot help trying to find the best parameters for a given application. The app ALSAMixer should help I would think.
Does this program now actually display anything?
Click to expand...
Click to collapse
It's a long shot but if you are in the New York tri-state area I wouldn't mind meeting up and letting you mess around with the Nexus4.
The invitation is open to anyone with ALSA experience. I would love to learn more about it first-hand.
As far as I can tell:
- ALSAMixer installs the ALSA libraries and displays the control set. I tried modifying a value with it and it didn't work.
It's a matter of wrong syntax I think, I will contact the app creator about it.
- Terminal Emulator works. I was able to change the value of "AUX_PGA_LEFT Volume" with the following command:
alsa_amixer cset numid=54 39
I'm not sure what this one does yet but I will investigate later today.
- unfortunately, during a phone call "proc/asound/card0/pcm0p/sub0/status" (playback) as well as
"proc/asound/card0/pcm0c/sub0/status" (capture) report "closed". Earlier I tried recording a voice call from an app
and trying to prepare an audio stream with MediaRecorder.AudioSource.VOICE_CALL throws an exception.
- when recording an audio stream with MediaRecorder.AudioSource.MIC and CAMCORDER
"proc/asound/card0/pcm0c/sub0/status" reports audio stream parameters. I'm attaching the piped output of
"alsa_amixer -c 0 contents" during a voice call, recording with mic and recording with camcorder.
-Mindroid- said:
[...]
- when recording an audio stream with MediaRecorder.AudioSource.MIC and CAMCORDER
"proc/asound/card0/pcm0c/sub0/status" reports audio stream parameters. I'm attaching the piped output of
"alsa_amixer -c 0 contents" during a voice call, recording with mic and recording with camcorder.
Click to expand...
Click to collapse
This is fun...
There is certainly a difference between the "idle" set of parameters you had posted earlier and the ones that you took during a voice call.
I found some good information that explains the parameters here
https://github.com/psykick5/android_device_lge_mako/blob/master/snd_soc_msm_2x_Fusion3
Try to change numid=48 (i.e. 'ADC1 Volume') and numid=40 (i.e. 'DEC7 Volume'); these two parameters should change the microphone level, provided automatic gain control does not compensate for the changes.
(It bothers me, though, that the range of values shown by alsa_amixer and the ones shown in the above link don't match)
Make sure that the changes stick by issuing
alsa_amixer cget numid=X
For phone calls I would certainly change numid=65 (i.e. 'TX6 HPF cut off') from 0 (apparently really only a DC offset filter) to 2 (apparently a high-pass filter with a cutoff frequency of 150Hz), which would be good enough for HD voice.
chdloc said:
This is fun...
There is certainly a difference between the "idle" set of parameters you had posted earlier and the ones that you took during a voice call.
I found some good information that explains the parameters here
https://github.com/psykick5/android_device_lge_mako/blob/master/snd_soc_msm_2x_Fusion3
Click to expand...
Click to collapse
Great find! This seems to be exactly what we need.
Most intriguing there are also facilities for Voice Call and FM Radio audio streams. Those are not currently working on
the Nexus4 at the moment and this might shed some light on a possible solution.
I find some of their nomenclature confusing. They use "TX" for recording and "RX" for playback.
Also they seem to set values twice - :1:0 for turn off and :1:1 for turn on. Do I have to issue commands twice?
I confirmed with 'cget' that I am indeed setting values with 'cset'.
chdloc said:
Try to change numid=48 (i.e. 'ADC1 Volume') and numid=40 (i.e. 'DEC7 Volume'); these two parameters should change the microphone level, provided automatic gain control does not compensate for the changes.
(It bothers me, though, that the range of values shown by alsa_amixer and the ones shown in the above link don't match)
Make sure that the changes stick by issuing
alsa_amixer cget numid=X
Click to expand...
Click to collapse
It seems that DEC7 controls to the MICROPHONE stream and DEC6 the CAMCORDER.
I will focus my attention on these.
chdloc said:
For phone calls I would certainly change numid=65 (i.e. 'TX6 HPF cut off') from 0 (apparently really only a DC offset filter) to 2 (apparently a high-pass filter with a cutoff frequency of 150Hz), which would be good enough for HD voice.
Click to expand...
Click to collapse
I was wondering about that myself. There is very bad low frequency noise on video recordings so I will
definetly look into this.
-Mindroid- said:
I find some of their nomenclature confusing. They use "TX" for recording and "RX" for playback.
Click to expand...
Click to collapse
Actually, the nomenclature is quite common, TX, i.e. transmit [to the network] denotes the signal to be transmitted (taken from from microphone)
while RX is the receive signal [from the network] to be played back through a loudspeaker.
-Mindroid- said:
Also they seem to set values twice - :1:0 for turn off and :1:1 for turn on. Do I have to issue commands twice?
Click to expand...
Click to collapse
No, you will have to issue the command only once. Without having looked at the underlying code I tend to think that the first number denotes the type, i.e. integer vs string, and the second number the actual value.
Another interesting observation is that the SoC of the Nexus 4 seems to support SRS TruMedia via an effects mixer, which reportedly has potential to improve audio considerably (http://www.srstechnologies.com/content.aspx?id=1269 , I believe).
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...
The sleep deprivation torture device called the LG G4 shall torture our souls no more. I don't know what went through the minds of the one(s) incompetent enough to think that it would be wise that this phone should make a loud noise when finished charging (even when in priority mode), but here's how to get rid of it.
Might be applicable to other devices (LG G3? G2?). I'm not sure, though, so don't hang me up on it. I haven't found a guide anywhere on Google, and it took me a long while before I figured out this solution, despite its simplicity.
Requires root. Unless you find some other way to move/remove system files.
Steps:
1. Make sure you have root.
2. Install and/or open your favourite root file browser app (ES File Explorer/Root Explorer/Dora the explorer/whatever your preference is)
2.1. Depending on your file explorer, you might have to remount the /system partition as read/write.
2.2. When using ES File Explorer specifically, make sure Root Explorer is on.
3. Navigate to /system/media/audio/ui/
4. Observe the source of your suffering: FullBattery.ogg
5. Remove it, rename it or replace it with an ogg file containing John Cena's theme
See bottom of post for screenshot showing this process in ES File Explorer.
Alternative steps: With adb shell
Code:
adb shell
su
mount -o remount,rw /system
mv /system/media/audio/ui/FullBattery.ogg /system/media/audio/ui/FullBattery.ogg.getout
What to do when you don't have root:
While the sound does play in priority mode, it doesn't play when the phone is in "No Interruptions" mode. That can be exploited in a very dirty hack:
1. Install and/or open your favourite automation tool (Tasker, Condi, whatever)
2. Create the following profile:
- When charging AND
- Battery percentage is between 99% and 100%
- Set to No Interruption Mode
3. Create another profile:
- On the event that the battery is full
- Set the interruption mode to all or priority, depending on your preference (I like my phone being in Priority Mode when I sleep)
Note:
- This approach is hacky
- it has failed me at seemingly random times (I don't know why)
- inserting the power cable while the battery is between 99 and 100 percent will make it stay on No Interruption mode indefinitely.
- There's a window of time in which you will be completely unreachable, even if you want to be.
In short: this solution isn't that great. Use the root solution above.
Thank you very much sir. I already did rename every ogg noise file there is in "ui". Works great for everything except Batteryfull. Now I did delete the sound and I will report back.
Send from outer space using telepathy
It is NOT working... *sigh* I deleted the sound. My LG G4 still plays that sound! What can I do? Is there a place where sounds are cached? Can/should I delete DALVIK or ART Cache or both? How would I do that?
Well I did it: I downloaded a silent sound mp3, renamed it to FullBattery.ogg, placed it into /system/media/audio/ui/. Finally no more annoying sound in the middle of the night. Why the LG G4 keeps playing this sound even when the file is physically deleted is beyond me. Must be some sort of fall back sound that is compiled into the system sources. I had a contact in Threema applied a "New message" sound. After a while I removed this notification, gave this contact notification sound "silent" (stock android). Somehow the LG G4 insists in playing a sound for that contact. The same exact annoying BatteryFull.ogg sound which I never assigned to anything or anyone. So I guess whenever the LG G4 wants to play a sound but can not find any audio it plays that crap which is redundantly in the source code for the lazy coder to work with...
Thanks for this. I'm going to have nightmares about being woken up to AND HIS NAME IS JOHN CENA in the middle of the night now >.>