Database Users

[SOLVED] Eris "Undead Call" Problem (AOSP/Froyo/GB) Fixed!

While poking around today, I discovered that I could deterministically cause "rild" to segfault - every time I tried it.
The method I used was to turn on WiFi with the Mobile Data network already running, and then I would launch the app "Wifi Analyzer" (farproc). Almost immediately the "rild" (Radio Interface Layer Daemon) would segfault. (Strictly speaking, I don't know if using WiFi Analyzer was necessary - my WiFi has beacons turned off, and sometimes I can't establish a session straight away; using a scanner seems to get my AP to come out of it's sleep).
That consistency convinced me to use strace to attach to the already-running "rild" daemon, and spew to a log file.
Note that historically, the SIGSEGV faults that were logged to the logcat output at the moment of the "undead call" implicated a problem in the fclose() call - almost as if something was trying to close a file that had not been opened correctly.
So, there in the strace output, was this:
Code:
16:43:23 writev(6, [{"\3", 1}, {"HTC_RIL\0", 8}, {"(t=1297817003)%% $HTC_3GIND:0\\r\\n\0", 35}], 3) = 44
16:43:23 open("/data/data/com.android.dmportread/history", O_WRONLY|O_CREAT|O_APPEND, 0666) = -1 ENOENT (No such file or directory)
16:43:23 chmod("/data/data/com.android.dmportread/history", 0666) = -1 ENOENT (No such file or directory)
16:43:23 writev(6, [{"\3", 1}, {"HTC_RIL\0", 8}, {"at_notify_cdma_g23_data_entry():Can't open /data/data/com.android.dmportread/history successfully \r\n\n\0",102}], 3) = 111
16:43:23 --- SIGSEGV (Segmentation fault) @ 0 (c) ---
a quick peek at /system/lib/libhtc_ril.so shows that - yep - buried in there is a reference to
/data/data/com.android.dmportread/history
So, I tried the following:
Code:
[COLOR=green][B]
mkdir /data/data/com.android.dmportread
chown radio:radio /data/data/com.android.dmportread
touch /data/data/com.android.dmportread/history
chown radio:radio /data/data/com.android.dmportread/history
[/B][/COLOR]
and guess what - no more segfaults. [SIZE=+3]YES![/SIZE]
If this is the cause of the "undead" call (seems highly likely), the explanation appears to be due to a bug in the HTC vendor library lbhtc_ril.so : a file open() fails, but the corresponding "close()" operation takes place anyway, and that is where the fault (segmentation violation) occurs. There is a stupid dependency of the libhtc_ril.so file on the DMPortRead.apk app.
Probably the only reason that this bug does not express itself in HTC "factory" 2.1 ROMs is because of the presence of DMPortRead.apk app - presumably that creates/maintains the history file.
[SIZE=+1]See the 3rd post of this thread for downloadable patch/script files[/SIZE]
If any of you are consistently experiencing the "undead call" problem, please consider testing the above to see if you think it is the fix. (I believe it is.)
bftb0

I knew I liked you!
I'll have to try this out when I get home.

Here's a flashable .zip and also a shell script which may be used in Gscript lite - you need to unpack the "unpackme.zip" file to get to them. ("unpackme" is NOT flashable).
I realized after I was 95% of the way through putting together the installer script that there was absolutely no reason to do this in an offline fashion (that is, "overflashing" it during a recovery boot) - it is perfectly fine to do what needs to be done in a shell script any time you please with the regular OS is running. Oh well, the ROM devs can look at it and use whatever they want from it (or nothing at all).
You can run the CureUndead_v0.9.sh script either from within the Gscript Lite app (you need to give the script root privilege), or you could use adb to push it to /data/local and chmod it and execute it by hand. Note that Gscript Lite on GingerBread has this annoying bug where it prints "stderr:" for every line in the original script. It's not my script that's doing that - it's either a problem with Gscript Lite, or something unusual about GSB.
Oh, yeah - the way the script is written, you can run it as many times as you want; as a side effect, this will truncate to zero length any prior history file.
MD5's and sizes of contents of "unpackme.zip":
0bf8c49312e61c436d379a24255b12f3 CureUndead_v0.9.sh - 421 bytes
9d459f9f598f51fffa98cf832c524e50 CureUndead_v0.9.zip - 2,678 bytes (this one is flashable)

Going to try it out... Thanks for this!

nice work...

Very interesting... so this is something that would need to be done post flash, what do you think...
... we use that lights.sh script conap put together in /system/xbin/ that runs @ every boot to initialize the lights for trackball/notifications... would it work if I added the lines to that? I'm not sure if it would cause issues running it @ each boot or not?
Trying to figure out a different way to add this pre-build too.

This is huge if it's the fix. Incredible work.

oceanminded said:
This is huge if it's the fix. Incredible work.
Click to expand...
Click to collapse
I think it is the fix

workshed said:
Very interesting... so this is something that would need to be done post flash, what do you think...
... we use that lights.sh script conap put together in /system/xbin/ that runs @ every boot to initialize the lights for trackball/notifications... would it work if I added the lines to that? I'm not sure if it would cause issues running it @ each boot or not?
Trying to figure out a different way to add this pre-build too.
Click to expand...
Click to collapse
Well, I'm putting together a flashable "fix" file that just uses the installer script, so it could be rolled up into a ROM install as well.
The one thing you might want at boot (rather than only at ROM install time) is some kind of zero-ing out of the history file every once in a while, so that it doesn't grow without bound. I only watched it for a short period of time, and it was only 4 lines long; it might not ever grow big, but that seems like the right thing to do.

So I guess I'll wait until one of you genuises makes this "point and click" simple. I don't have a clue how to implement this on my own. Awesome work bftb0 !

Sheesh you're a brain OP. Awesome job!
Sent from my Ginger Tazz using XDA App

Interesting... what's the undead call bug you're talking about? I've been getting this funny bug on long calls where sometimes the phone app just crashes after 15-30mins or so. I get the crash window, and if I force quit, it shows no signal until I reboot the phone. If that's the one, a fix would be really nice. Running KaosFroyo v39 and never flashed a new radio BTW.
I've also seen the same thing on the WiFi signal. I have SSID broadcast turned off, and it takes it's sweet time picking it up on its own, but running WiFi analyzer seems to wake it up.

ufmace said:
Interesting... what's the undead call bug you're talking about? I've been getting this funny bug on long calls where sometimes the phone app just crashes after 15-30mins or so. I get the crash window, and if I force quit, it shows no signal until I reboot the phone. If that's the one, a fix would be really nice. Running KaosFroyo v39 and never flashed a new radio BTW.
I've also seen the same thing on the WiFi signal. I have SSID broadcast turned off, and it takes it's sweet time picking it up on its own, but running WiFi analyzer seems to wake it up.
Click to expand...
Click to collapse
What he is referring to is during a call you get the tones and vibration like the call has been dropped but then you can hear the person on the other end again and the call was never dropped. What you are describing is a new one to me...

CondemnedSoul said:
What he is referring to is during a call you get the tones and vibration like the call has been dropped but then you can hear the person on the other end again and the call was never dropped. What you are describing is a new one to me...
Click to expand...
Click to collapse
Ah yeah, I've had that happen too. I didn't think of it, though, since it wasn't all that annoying to me. I already ran the fix anyways, so I'll see if it helps either problem.

I haven't had the problem for some reason, but I just entered all that in a terminal window on my phone (and wasn't that tedious). Thanks!

Scott586 said:
So I guess I'll wait until one of you genuises makes this "point and click" simple. I don't have a clue how to implement this on my own. Awesome work bftb0 !
Click to expand...
Click to collapse
I put up a script in the 3rd post in this thread which you could use in the Gscript Lite app. You will still need to figure out how to use Gscript Lite, but at least no "adb" or command-prompt typing is needed.
Everybody else - I would appreciate hearing back from you after you try this, especially if you have been experiencing the "undead call" bug frequently. (I've used my phone for calling so little recently I don't think it has happened to me in more than 5 weeks.) The more often it was happening to you in the past, the more valuable your feedback is now.
bftb0

bftb0 said:
I put up a script in the 3rd post in this thread which you could use in the Gscript Lite app. You will still need to figure out how to use Gscript Lite, but at least no "adb" or command-prompt typing is needed.
Everybody else - I would appreciate hearing back from you after you try this, especially if you have been experiencing the "undead call" bug frequently. (I've used my phone for calling so little recently I don't think it has happened to me in more than 5 weeks.) The more often it was happening to you in the past, the more valuable your feedback is now.
bftb0
Click to expand...
Click to collapse
thanks for the script bf, that's all I needed to add it in the rom. I'll be a tester also, as I do experience the bug quite often, but only on long calls which isn't as frequent for me currently. Bravo sir!
P.S. I will be sure to add "# Undead call fix by bftb0" in the rom and OP page

workshed said:
thanks for the script bf, that's all I needed to add it in the rom. I'll be a tester also, as I do experience the bug quite often, but only on long calls which isn't as frequent for me currently. Bravo sir!
P.S. I will be sure to add "# Undead call fix by bftb0" in the rom and OP page
Click to expand...
Click to collapse
dope
this is good news. great job op and workshed if u add it to your gb rom lol
love you both!

flashed it on gsb1.4. i'll let you know how it goes.

:O OMG! That always happens, but I thought I was crazy XD So I'm going to try this.
Sent from my Droid Eris ♥ (running Ginger Tazz v5 [eat your heart out Jobs])

irritating power up noise

When the Galaxy Note powers up, it shows a video and makes some noisy music. how can i suppress it?

I was wondering the same thing last night! Seems kind of ridiculous to have a loud jingle upon start up that's impossible to silence.

Seriously......wow is the phone really that good that you guys need to complain about the sound the phone makes when it starts? I can't beleive how many people complain about small stuff like this......

Gunner86 said:
Seriously......wow is the phone really that good that you guys need to complain about the sound the phone makes when it starts? I can't beleive how many people complain about small stuff like this......
Click to expand...
Click to collapse
They are asking for a fix with an issue that is easily understandable...to be honest, you're complaining more than they are lol

Have you tried to put it in silent mode before restarting?

Gunner86 said:
Seriously......wow is the phone really that good that you guys need to complain about the sound the phone makes when it starts? I can't beleive how many people complain about small stuff like this......
Click to expand...
Click to collapse
It is a fair complaint, because you can't silence it.
If your GNote decides to crash/reboot during a meeting......
I have to find the post, but if you are rooted, you can delete the ogg file with the startup sound.

For rooted users to stop the startup sound...
\system\etc\
Rename these file(s)
PowerOn.wav
or
1_Power_on.ogg
or both

settings-sound-volume. Set system volume to zero. it does not seem to affect anything else.

That worked great, thanks! I used Root Explorer to rename those two files. And yes, having the phone making noise at inappropriate times is exactly what I wanted to avoid.
Edit, I already renamed the files before trying the system volume. That would be interesting if the boot audio really is the only thing affected by "system" volume.

maxh said:
That worked great, thanks! I used Root Explorer to rename those two files. And yes, having the phone making noise at inappropriate times is exactly what I wanted to avoid.
Edit, I already renamed the files before trying the system volume. That would be interesting if the boot audio really is the only thing affected by "system" volume.
Click to expand...
Click to collapse
I have been using that method on my galaxy s for 18 months and never found anything else affected by it. Seems to work the same on my Note.

maxh said:
That worked great, thanks! I used Root Explorer to rename those two files. And yes, having the phone making noise at inappropriate times is exactly what I wanted to avoid.
Click to expand...
Click to collapse
Thanks, it worked for me too, but instead of root explorer, which you need to pay for, I used ES explorer, free, enabling root access in the config menu.

that's reassuring. When I read about nulling the system volume, I am so sure I'm going to miss some notification.

Never Worked For Me On I717R
The funny thing is that my power on/boot up sound never worked. After I rooted I noticed both the 1_Power_On.ogg (plays sound) & the PowerOn.wav (no sound) in the etc folder. I am sure that the second one overrode the 1st, causing no sound on start up. I just removed the second & renamed the 1st to PowerOn.wav, now I have the sound.

MoWeb said:
For rooted users to stop the startup sound...
\system\etc\
Rename these file(s)
PowerOn.wav
or
1_Power_on.ogg
or both
Click to expand...
Click to collapse
Big Thanx.

Can't you change the boot animation too and that get rid of it?

how often do u guys re-start ur device???
for me maybe once a week...!

andreww88 said:
Can't you change the boot animation too and that get rid of it?
Click to expand...
Click to collapse
As you wish. Clicky

[Q] Remove Camera Click Sound

Heya, new to fiddling with root files but really wanted to get rid of camera click. Followed advice about renaming camera_click.ogg in terminal Emulator using:
ADB shell
SU
mount -o remount,rw /dev/block/mtdblock4 /system
mv /system/media/audio/ui/camer_click.ogg /system/media/audio/ui/camera_click.ogg.old
(source: www droidforums net/forum/droid-hacks/23107-droid-remove-camera-click-shutter-sound html) - sorry new poster not allowed to post url
Now have issue when open stock camera and vid in Motorola Atrix (gingerbread 2.2.2) where:
1) camera opens, but have lost all previous images.
2) camera takes silent shot
3) camera 'locks' open and can't return to 'desktop', can't view image taken,, can't access menus etc
Basically camera is stuffed...
is there a solution, is there code to go back and follow some of the other advice in here etc?

It is a setting. What's the point?
Sent from my MB860 using xda premium

it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!

have you tried to add the following line to local.prop file located in /data?
ro.camera.sound.forced=0
If you don't have the file then just create the file and add it, otherwise append it to the end of file.
File permission is: 0644
Good Luck

I never heard of adding ".old" on the end of the file. I always add ".bak", then reboot. Works everytime.
EchoK8 said:
it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!
Click to expand...
Click to collapse

I giggled when I read gingerbread 2.2.2
Sent from my SAMSUNG-SGH-I777 using Tapatalk

Thanks for pointing that out, that gave me a good laugh to start the day off.
Phalanx7621 said:
I giggled when I read gingerbread 2.2.2
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Click to expand...
Click to collapse

EchoK8 said:
it's a setting what's the point? Thanks for taking the time to reply. I did mention this is all new to me. I asked a question because i do't know the answer. It's a swttibg whats the point is hardly helpful.
To anyone else, i'd appreciate any help or advice. As i mentioned i'd just like to undo what i've done usibg script i found on another forum. looking forward, hopefully, to hearing from you!
Click to expand...
Click to collapse
I was on my phone at the time (tiny keyboard) and was trying to succinctly say that if you open the camera app and touch "settings", there is an option to quiet the click.
When I first read your OP I didn't notice that you identified Gingerbread as v2.2. You are confused. v2.2 was named Froyo (frozen yogurt). Gingerbread is v2.3. My answer relates to Gingerbread. If you are actually on Froyo, I don't remember if the setting was available on that release.
So, in Gingerbread silencing the camera is a setting and there is no point performing internal surgery.

Yep, ok, noob blunder. Novice blunder, amatuer, beginner whatever blunder. Glad you all got a giggle, and thanks for pointing it out. I was told at the shop it's Gingerbread. The About phone states 2.2. So, if that makes it Froyo then great, i've learnt the basics today. Thanks for your help again!
Well re- the settings, froyo or otherwise, yes there is a setting to turn sound off. You turn it to off and it still makes the click sound, volume can't be altered. Hence diving off the deep end and into something i know very little about - internal surgery!!
Live4nyy - is there a simple way to rename to .bak (you see my level of expertise here - none! - in asking).. forward some script for me at all?
or
CSharpHeaven that sounds gr8... any way to explain to a complete novice how to do that?
I thank anyone who sticks with me to reply after this MUCHLY as you know you are dealing with a friking novice

Seriously....why would you want to silence your camera again?

Do you have root? If yes, then you can just use any file manager that has root access, ES File Explorer works I've heard, and just go to the folder where the sound file is (/system/media/audio/ui) and just select to rename the file and add ".bak".
EchoK8 said:
Yep, ok, noob blunder. Novice blunder, amatuer, beginner whatever blunder. Glad you all got a giggle, and thanks for pointing it out. I was told at the shop it's Gingerbread. The About phone states 2.2. So, if that makes it Froyo then great, i've learnt the basics today. Thanks for your help again!
Well re- the settings, froyo or otherwise, yes there is a setting to turn sound off. You turn it to off and it still makes the click sound, volume can't be altered. Hence diving off the deep end and into something i know very little about - internal surgery!!
Live4nyy - is there a simple way to rename to .bak (you see my level of expertise here - none! - in asking).. forward some script for me at all?
or
CSharpHeaven that sounds gr8... any way to explain to a complete novice how to do that?
I thank anyone who sticks with me to reply after this MUCHLY as you know you are dealing with a friking novice
Click to expand...
Click to collapse

I'd like to replace my shutter sound. Does anyone have a sound file of a shotgun blast/ slide rack?

Thannnks

island-guy said:
Seriously....why would you want to silence your camera again?
Click to expand...
Click to collapse
i actually dont want or need to silence it again. my query is how to restore my camera to a mode where it is functional bcs at the moment its stuffed. If theres a simple string to go back that'd be ideal.

live4nyy said:
Do you have root? If yes, then you can just use any file manager that has root access, ES File Explorer works I've heard, and just go to the folder where the sound file is (/system/media/audio/ui) and just select to rename the file and add ".bak".
Click to expand...
Click to collapse
Ok, got 'root explorer'... so simple just to enable R/W and rename.. Thanks. Changed to .bak . Seems better, actually appears to take photos and has more functionality than after i ran that script... but
I don't know what that original script did. Here's what using my built in camera is like:
1) Turn Camera on. Opens, appears normal. Take photo fine. Thumbnail (link to camera roll) in bottom corner as per usual, which disappears after a few seconds as per normal.
So far so good.
2) After taking another photo decide to click on thumbnail to open camera roll. Camera Roll opens but says there are no pictures to display. return (via 'back' menu button) and the thumbnail of the images is there again. Ok, weird.
3) Try take another photo... nothing happens, wait a few seconds and camera switches off back to ;desktop'. Try open camera again but no dice. In fact all phone functionality gone, frozen, locked up, including menu buttons below screen. Put phone to sleep by pressing rear button briefly. Press rear button again to awake. Unlock swipe is slow to respond (a few seconds) and then back to main desktop screen. Can once again open camera. Repeat process from dot point 1).
4) next time go to camera roll, this time locks up on camera roll (which has no images to display again). Sleep and wake up camera, slow swipe unlock, can take photos again when open camera. repeat step 1 - 3 again!
5) Sleep, wake up phone. This time straight to gallery instead of camera. Gets stuck telling me it's loading media files. Frozen.
6) sleep- wake - slow swipe unlock. This time to video. Same thing as camera. Frozen.
I could go on.... but im sure the idea is clear!
used root explorer to simply remane camera_click.ogg to original name. Same as above
Tried camera zoom fx app incase it was the built in camera app. This won;t even open - well, it starts but then says i need to force it to close.
Does this need a factory reset??!
Ta

Have you rebooted? Maybe try and go into "Manage Applications" under the "All" tab and find the camera and "clear data"?
EchoK8 said:
Ok, got 'root explorer'... so simple just to enable R/W and rename.. Thanks. Changed to .bak . Seems better, actually appears to take photos and has more functionality than after i ran that script... but
I don't know what that original script did. Here's what using my built in camera is like:
1) Turn Camera on. Opens, appears normal. Take photo fine. Thumbnail (link to camera roll) in bottom corner as per usual, which disappears after a few seconds as per normal.
So far so good.
2) After taking another photo decide to click on thumbnail to open camera roll. Camera Roll opens but says there are no pictures to display. return (via 'back' menu button) and the thumbnail of the images is there again. Ok, weird.
3) Try take another photo... nothing happens, wait a few seconds and camera switches off back to ;desktop'. Try open camera again but no dice. In fact all phone functionality gone, frozen, locked up, including menu buttons below screen. Put phone to sleep by pressing rear button briefly. Press rear button again to awake. Unlock swipe is slow to respond (a few seconds) and then back to main desktop screen. Can once again open camera. Repeat process from dot point 1).
4) next time go to camera roll, this time locks up on camera roll (which has no images to display again). Sleep and wake up camera, slow swipe unlock, can take photos again when open camera. repeat step 1 - 3 again!
5) Sleep, wake up phone. This time straight to gallery instead of camera. Gets stuck telling me it's loading media files. Frozen.
6) sleep- wake - slow swipe unlock. This time to video. Same thing as camera. Frozen.
I could go on.... but im sure the idea is clear!
used root explorer to simply remane camera_click.ogg to original name. Same as above
Tried camera zoom fx app incase it was the built in camera app. This won;t even open - well, it starts but then says i need to force it to close.
Does this need a factory reset??!
Ta
Click to expand...
Click to collapse

live4nyy said:
Have you rebooted? Maybe try and go into "Manage Applications" under the "All" tab and find the camera and "clear data"?
Click to expand...
Click to collapse
Thanks L4NYY.. yep had rebooted. Tried clearing data but all the same
Had a quick look in the internal storage DCIM folder..All files appear to be there. The one vid file has a play button icon. The .jpg's have the android robot icon. I don't know what was there before. Trying to open the files from here freezes the phone.....
Connecting usb and viewing dcim shows that any images taken since the change to camera_click.ogg appear unknown thumnails in the PC explorer..and can't be opened on the PC via USB connection or when stored locally on the PC itself 'can't display this is an empty file' . This is probably all irrelevant but might be useful to someone, somehere...

Have just noticed today that battery was going flat very quickly. Realised since rooting and using that script (can't decipher which) that location services are no longer working, hence apps that provide location services are continually searching and draining battery. Yes i can turn those services off, but wouldrather resolve the issue!
I'm thinking more and more like factory reset Any thoughts?

Just factory reset. Used Astro File Manager to backup apps before hand, which for interest worked well (although did have to reinstall one by one). Of course Appstore keeps a lsit of purchased apps as a failsafe for thsoe.
After rest, reinstalled apps, including Root Manager. Simply followed Live4NYY's advice, renamed camera_click.ogg to camera_click.ogg.bak
All issues described earlier resolved. Camera functional and silent.
just goes to show sometimes you should ask noob questions. I tried following instructions on a post to avoid annoying the experts with a mum-mum dad-dad question! Anyhow, thnaks to live4nyy for taking the time.
Ciao

The ".bak" just stands for "backup". It will essentially hide any file/app and keep it from running (which in turn frees up RAM). So if you had a system app that you don't use you can just add ".bak" and it would be the same as freezing it. It's much safer than deleting files and apps as you can always go back and remove the extension (and reboot) and it will be back to normal.
EchoK8 said:
Just factory reset. Used Astro File Manager to backup apps before hand, which for interest worked well (although did have to reinstall one by one). Of course Appstore keeps a lsit of purchased apps as a failsafe for thsoe.
After rest, reinstalled apps, including Root Manager. Simply followed Live4NYY's advice, renamed camera_click.ogg to camera_click.ogg.bak
All issues described earlier resolved. Camera functional and silent.
just goes to show sometimes you should ask noob questions. I tried following instructions on a post to avoid annoying the experts with a mum-mum dad-dad question! Anyhow, thnaks to live4nyy for taking the time.
Ciao
Click to expand...
Click to collapse

[Guide][Root] Removing the charging full sound

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 >.>

5/1/2017 || V10 (msm 8992) || CPU, GPU, IO, RAM "Tweaks"

So the dev section here has been active recently with some high quality work, and I am looking to add to the fun
**SEE POST 2 FOR CHANGE LOG**
***VERY IMPORTANT IF YOU ARE GOING TO USE THIS MOD, you need to navigate to the /system/etc folder on your device, and rename the file "init.lge.zramswap.sh" to "init.lge.zramswap.sh.bak" so it does not run at boot.
This is a step by step instruction on how to replace the /system/etc/init.qcom.post_boot.sh file for the LG V10. Be it known, however, that this instruction (and file) can be used with any device running the Snapdragon 808 SoC combo.
What does this do?
Simple. It turns your device into an even more efficient powerhouse. Here are is a list of everything done:
-Interactive Governor tuning for performance and better battery life, a quick description of what I did...
-low load, quick response, low frequency
-high load, quick response, higher frequency
-modified input boost settings for Interactive
-Adjusted GPU target load values
-Switched IO scheduler to noop, and tuned accordingly
-Adjusted minfree values (RAM management, it is a little more multi-tasking friendly)
-Adjusted VM parameters - swappiness, dirty ratios, cache pressure, centisec values, etc (again to complement multi-tasking... your data will hang out a little bit more before being written to disk, but house cleaning won't happen all at once, so there is still good performance and your system won't bog down while it is flushing the toilet)
-DISABLED zRAM!!! - I have no idea why a device with 4 GB of RAM has zRAM enabled. This is purely a waste of CPU cycles and other system resources. You want physical memory, not compressed memory.
-Changed congestion algorithm to cubic (better network performance... assuming the network bandwidth is already there
-Cleaned up the shell file and fixed some errors.
-More to come!
How to do this, we'll just get right to it.
Download this app https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Download this file https://drive.google.com/open?id=0BzM9W6qUvx-gcm1SVDhsTDVWZ3M
And while you are here, check this out, decide which one you want.
http://forum.xda-developers.com/showpost.php?p=66792862&postcount=109
Very important you put the file on the root of your INTERNAL SDCARD!!!
Do not forget to do this.
After you do that, open terminal emulator, and type the following commands in the order they are presented (I would highly recommend just copying them from this post and switching back and forth between your browser and the terminal app):
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
Double check the file has been replaced with a file explorer of some sort, double check permissions, then reboot. Good to go.
Some of this stuff explained http://forum.xda-developers.com/tmo...nux-virtual-machine-explained-part-1-t3386956

CHANGE LOG***
May 1, 2017
-Pretty major overhaul of the file. I've done some stuff on the Axon 7 that has been pretty effective. Rolling those changes out to other devices. https://drive.google.com/open?id=0BzM9W6qUvx-gcm1SVDhsTDVWZ3M
May 31, 2016
-Replaced corrupted files. Good to go now!
Dangerously version (fixed) https://drive.google.com/open?id=0BzM9W6qUvx-gVHBGWEp3QkpURVE md5sum: a632c866e22114c0e18fa335f005293e
May 25, 2016
Quite a bit of changes here...
-VM completely readjusted. vfs_cache_pressure set back to default 100 to fairly reclaim memory pages that have been allocated to block specific data about file location, etc.. there are tons of write ups on this stuff if you guys want to investigate more into what this setting does, how it works. It's basically a fairness multiplier centered around a value 100. + or - that value increases or decreases the probability that the kernel will reclaim those certain memory pages relative to swap.
-Swappiness reduced drastically... from 80 to 40 (default is 60 depending on which kernel you are running)
-dirty ratio and dirty background ratios reduced drastically to avoid massive amounts of data being flushed and causing system hangups when that ceiling is hit. (lol this happened to me... system ran out of mem... *shrugs* I go hard bros)
-Increased the probably of the system to reclaim memory pages, and made a pretty big adjustment to writeback_centisecs and expire_centisecs
-Changed functional aspects of the interactive governor again - it is perfect. Nominal user experience. Same with touch input_boost. This system definitely has a sweet spot, and I'm pretty sure we've found it now.
-Decided to ditch the laptop mode idea and not mess with the RAM console outputs, the functional loss wasn't returning enough reward. So, here we are.
-Adjusted minfree once more, to
-It is important to note that the system will, admittedly, not multitask quite as aggressively. I had to do this, however, for myself mostly. As I was achieving OOM conditions and hitting the high ceilings set in other parameters like dirty_ratio and when it hits that wall, man it hits hard. Complete lock up for a good 40 seconds while everything is getting dumped from memory. I need a phone with more RAM lol. Didn't think that would ever happen on my mobile set up with 4 GB of it but here we are. I suppose I could re-enable zRAM for myself? But that would hardly help as compression ratios aren't going to yield me an extra gigabyte. Ok now I'm rambling. DOWNLOAD THE FILE!

Very interesting, I'll be trying this in the next hour or so! Thanks for posting.
Edit: Made changes as per the instructions and rebooted successfully. No issues so far, we'll see! Thanks again.

Nice...
Desde V10 (LG-H901)

For all variants? Is it compatible with H961N LP?
Looks promising and wanted to try.

How do I know it worked? I followed the steps
Sent from my LG-H901 using XDA-Developers mobile app

roosxter said:
How do I know it worked? I followed the steps
Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Click to collapse
After every line he explains what it does, you would recognize the changes through your usage or maybe non-usage (as far as battery life and RAM management goes)

When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #

iamtheon said:
When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #
Click to expand...
Click to collapse
i got problem with the !!!!!!cd /sdcard , writing
i tried cd /storage/emulated/0
and worked for me

11868 said:
i got problem with the !!!!!!cd /sdcard , writing
i tried cd /storage/emulated/0
and worked for me
Click to expand...
Click to collapse
I tried that, but doesn't hurt trying again.
Edit: It worked. I did the same thing lol oh well thanks @11868

Can this be done with the root explorer instead of terminal emulator?

So this can be used on the G4? And does this overwrite settings within the kernel? If I push this file and I don't like the results can I flash a kernel to get rid of the changes?

iamtheon said:
When I try to move the file it's giving me this error. I have BusyBox and pretty sure it's on read/write access. What am I doing wrong -_-
1|[email protected]:/ # mv init.qcom.post_boot.sh /system/etc
mv: init.qcom.post_boot.sh: remove: Read-only file system
1|[email protected]:/ #
Click to expand...
Click to collapse
Your system wasn't mounted as rw when you executed the command
agrenwa said:
Can this be done with the root explorer instead of terminal emulator?
Click to expand...
Click to collapse
It can, yes, I just prefer the old school way. You can manually drop the file in the /etc folder after deleting the previous one. Just need to make sure the permissions are set appropriately.
klbjr said:
So this can be used on the G4? And does this overwrite settings within the kernel? If I push this file and I don't like the results can I flash a kernel to get rid of the changes?
Click to expand...
Click to collapse
Yes, this can be used on the G4 and any other device using the Snapdragon 808. Overwrite settings within the kernel? No, I wouldn't say that. sysfs is more of a userspace / virtual file system that allows you to interact with the hardware... but the parameters we are working with here are completely writable, not permanent, and more important, will reapply AFTER boot. So, no, flashing a kernel will not revert the changes. If you want to go back, you'll need the original file to replace mine with.
Hope this answers your questions.

Since the file is hosted on Dropbox, anyone who has a dropbox account please choose the login option, and transfer the file to your dropbox before downloading it from your own storage to avoid OP's dropbox being blocked for too many downloads in a row.
Good Job OP, nice to see Junior Members doing something great in the dev section

So I did it last night, and so far battery life seems to be much worse than before when nothing has changed but these tweaks. Any idea why? Battery stats is the same for me as usual with the exception of Android System being at 6% and Android OS at 6% use each.

So far so good, not sure what battery usage will be like. I had terrible lag in a game called Underworld Empire and that has disappeared! How badly was the kernel/system coded before?!
Question , how come your file is smaller than the original? Was there a lot of excess code that was useless?
Sent from my debloated rooted LG V10 using Tapatalk

rirozizo said:
Since the file is hosted on Dropbox, anyone who has a dropbox account please choose the login option, and transfer the file to your dropbox before downloading it from your own storage to avoid OP's dropbox being blocked for too many downloads in a row.
Good Job OP, nice to see Junior Members doing something great in the dev section
Click to expand...
Click to collapse
I'll try to upload the file elsewhere, didn't consider that. However, it is a very small file and dropbox might not notice/care. Good observation.
danstheman7 said:
So I did it last night, and so far battery life seems to be much worse than before when nothing has changed but these tweaks. Any idea why? Battery stats is the same for me as usual with the exception of Android System being at 6% and Android OS at 6% use each.
Click to expand...
Click to collapse
Coincidence maybe? Keep monitoring, report back.
Also, bear in mind: rebooting your system causes a little more activity within the OS the first day or so (particularly google services) and it does have an effect on battery drain.
amoot329 said:
So far so good, not sure what battery usage will be like. I had terrible lag in a game called Underworld Empire and that has disappeared! How badly was the kernel/system coded before?!
Question , how come your file is smaller than the original? Was there a lot of excess code that was useless?
Sent from my debloated rooted LG V10 using Tapatalk
Click to expand...
Click to collapse
Yes, it is smaller because I removed everything that was not relevant to the msm8992 SoC. Qualcomm uses common files for just about everything and anything they can - saves them time, hassle and consolidates work somewhat.
Most of the content removed from the stock file is for other platforms not relevant for us.

warBeard_actual said:
I'll try to upload the file elsewhere, didn't consider that. However, it is a very small file and dropbox might not notice/care. Good observation.
Click to expand...
Click to collapse
I recommend Google Drive or Box

@warBeard_actual
Great job buddy on this.... @freeza mad af!
To everyone else I've been using this for a while and am happy to report my buddy warBeard_actual has been killing it!

bencze, proof or it didn't happen