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?
So a while ago I discussed with my friend rohit joshi (developer of tegra overclock) about a system file called adj, and how it may be responsible for sometimes disturbing ram behaviour. It couldn't be adjusted AFAIK on 4.1, but it seems to allow modification on 4.3.
1: Mount system R/W
2: Open /sys/module/lowmemorykiller/parameters/and open the file named adj
3: Change it to the following: 0,10,25,50,80,150 and save the file
Now please observe ram management in intense situations such as using chrome or heavy games, so far I have noticed no irrational behavior like asphalt 8 committing suicide etc, but its early days and we need more data. Custom values are welcome but please mention what you used
Note: These values reset upon reboot
Sent while my supervisor wasn't looking
Great,work on eXistenZ 2.1.5!
Before:429MB ram free
After:563MB ram free!
On stock without this mod i have 429mb free LOl
I think Supercharger solve those problems this way for two years now.
Hmm this isn't really it's purpose, also these values fluctuate on their own btw . It's supposed to stop foreground processes and other important stuff from getting killed in low memory situations, for example once my alarm stopped responding because I was busy extracting a zip file. This fix is for this kind of wierdness
Sent while my supervisor wasn't looking
asphalt 8 close by itself if i play tokyo track.. on other track game works nicely
@non4 said:
3: Change it to the following: 0,10,25,50,80,150 and save the file
Click to expand...
Click to collapse
Could you explain more what these values are...
is it oom_adj parameters
and why changing them so drastically?
Default values are 0,58,117,235,529,1000
Shouldn't we try first minfree parameters which are also IMHO odd...
15000,17532,20065,22598,25131,30263 which equals (Nx4/1024)
58.6 68.5 78.4 88.3 98.2 118.2 Megabytes
I change mine to 8192,16384,18432,24576,32768,65536 or 32,64,72,96,128,256 Mb
so far so good... will see over a longer period of time... :silly:
freedom74 said:
Could you explain more what these values are...
is it oom_adj parameters
and why changing them so drastically?
Default values are 0,58,117,235,529,1000
Shouldn't we try first minfree parameters which are also IMHO odd...
15000,17532,20065,22598,25131,30263 which equals (Nx4/1024)
58.6 68.5 78.4 88.3 98.2 118.2 Megabytes
I change mine to 8192,16384,18432,24576,32768,65536 or 32,64,72,96,128,256 Mb
so far so good... will se over a longer period of time... :silly:
Click to expand...
Click to collapse
I changed them this way simply based on advice given, as I say different values are welcome I don't fully understand it myself however what I know is it seems to be working. I have been told that newer snapdragon devices have different adjacent values to other phones. This causes apps that SHOULD be closed to instead not be closed and so the system resorts to closing your fave game or whatever. Adjacent and minfrees have a relationship but I'm not sure exactly how it works, will try and find some better info on it
Sent while my supervisor wasn't looking
poran123 said:
asphalt 8 close by itself if i play tokyo track.. on other track game works nicely
Click to expand...
Click to collapse
Hmm just spotted your comment there, I've been running Tokyo fine on high graphics, have you done anything else to the ram like change the minfrees? Feel free to play around with these values and report if you have any luck
Sent while my supervisor wasn't looking
@non4 said:
Hmm just spotted your comment there, I've been running Tokyo fine on high graphics, have you done anything else to the ram like change the minfrees? Feel free to play around with these values and report if you have any luck
Sent while my supervisor wasn't looking
Click to expand...
Click to collapse
i didnt change anything only did what is written on the op....
poran123 said:
i didnt change anything only did what is written on the op....
Click to expand...
Click to collapse
Lol, I just got the dreaded home crash! Will continue to experiment, it makes no sense how bad it is, I just ran this game on high graphics on a galaxy s2 and homescreen didn't even redraw when I was done!
I found some info on this driver here:
https://android.googlesource.com/ke...4ac/drivers/staging/android/lowmemorykiller.c
It might actually be worth trying higher values instead of lower ones from what I'm reading here
Sent while my supervisor wasn't looking
How is it going with adj settings?
According to http://forum.xda-developers.com/showpost.php?p=5442369&nocache=1&z=6948587024309106
adj values determines how apps will be killed in case of Out Of Memory situations
Numbers are, similar to minfree settings connected to
ForegroundAPP, VisibleAPP, SecondaryServer, HiddenAPP, ContentProvider, EmptyAPP and hence the numbers
0,58,117,235,529,1000
The higher number, more probably the process will bi killed.
You can say "if free memory goes below XXXX then kill some process with oom_adj greater then YYY; if free memory goes even more below than ZZZ then start to kill some processes with oom_adj greater than XYXY. and so on.."
Click to expand...
Click to collapse
So, values 0,10,25,50,80,150 for adj
will give results but also kills too many processes, maybe some important ones.
Maybe someone that have expeirience with linux kernels can answer the question:
Who sets oom_adj parameter of a process?
IMHO, by setting these adj values, you tell system to treat all processes with oom_adj higher than 150 like EMPTY_APP
Will try changing adj settings but perhaps with some less agressive parameters... let's say half of the original
0,25,50,100,250,500
someone told that actually sony latest framework that eat ram.. not by apps/bloatware.. which mean even though we kill foreground app.. it will load more cpu after that.. will raise more probs such as lags n battery drain.. but simply for playing heavy games i think it works..
sony knows this issue... maybe they will fix it in the next update.. maybe
I've been playing around and conclude that this works somewhat but you must lower your minfrees too for maximum effect, not sure what the best combination of values is just yet, seems lower = better, but too low may cause lag as ram fills up. One more thing is I noticed sometimes adj changes it's values back, perhaps if it considers them invalid as it only happens with certain values I tried
Sent while my supervisor wasn't looking
danielhariri said:
sony knows this issue... maybe they will fix it in the next update.. maybe
Click to expand...
Click to collapse
Is there a place to report a bug?
Yes I know they are aware of the issue but if more people report a bug, greater is the chance that they release a patch.
hi
i Change it to the following: 0,10,25,50,80,150 and save the file but When it was reset phone, Has not changed ... whay ?
/sys is not a real directory
It's a virtual file system so everything you change vanishes after reboot.
If you have some settings other than defaults you want to put into /sys you can do it via init.d scripts during the boot time.
Sent from my C5303 using xda app-developers app
freedom74 said:
/sys is not a real directory
It's a virtual file system so everything you change vanishes after reboot.
If you have some settings other than defaults you want to put into /sys you can do it via init.d scripts during the boot time.
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
Catch !! sorry
I just did that? 0,58,117,235,529,1000 After rebooting Can not be changed? not changed!!
Well, I said if you want your values get inserted automatically you need init.d script.
But since these values we talk about here are still unconfirmed and for testing I think it's better to stick with manual entering rather than automatic.
What I do is that I typed as SU in command prompt using Android Terminal app a command
echo "0,10,25,50,80,150“ > /sys/module/lowmemorykiller/parameter/adj
Same for minfree settings
Sent from my C5303 using xda app-developers app
freedom74 said:
Well, I said if you want your values get inserted automatically you need init.d script.
But since these values we talk about here are still unconfirmed and for testing I think it's better to stick with manual entering rather than automatic.
What I do is that I typed as SU in command prompt using Android Terminal app a command
echo "0,10,25,50,80,150“ > /sys/module/lowmemorykiller/parameter/adj
Same for minfree settings
Sent from my C5303 using xda app-developers app
Click to expand...
Click to collapse
And for init.d
#! /system/bin/sh
echo "0,10,25,50,80,150“ > /sys/module/lowmemorykiller/parameter/adj
Sent while my supervisor wasn't looking
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,
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
I am searching about how to limit the battery voltage to increase the timelife of battery, someone know here what file controls it on Galaxy S8 and a method to make it work just on boot time?
flipeicl said:
I am searching about how to limit the battery voltage to increase the timelife of battery, someone know here what file controls it on Galaxy S8 and a method to make it work just on boot time?
Click to expand...
Click to collapse
either use a weaker charging block not the fast charger or find the option in battery settings to shut off fast charge
But you know about the file that control it? Some smartphones use /sys/class/power_supply/battery/voltage_max.
flipeicl said:
But you know about the file that control it? Some smartphones use /sys/class/power_supply/battery/voltage_max.
Click to expand...
Click to collapse
yea but if your like me on a locked bootloader,We cannot modify those kernel files so those are the only two options for locked snap dragon
TheMadScientist said:
yea but if your like me on a locked bootloader,We cannot modify those kernel files so those are the only two options for locked snap dragon
Click to expand...
Click to collapse
It's not a locked bootloader, which is the file?
flipeicl said:
It's not a locked bootloader, which is the file?
Click to expand...
Click to collapse
Heck I dont know its been so long since Ive been able to play with them
You can use a Magisk module for that. What it actually does is to change "charging_enabled" (or similar) to 0 when it reaches the desired load percentage (aka certain voltage)
It is called Magic Charging Switch (mcs), though it may be not compatible with your device. Give it a try
bamsbamx said:
You can use a Magisk module for that. What it actually does is to change "charging_enabled" (or similar) to 0 when it reaches the desired load percentage (aka certain voltage)
It is called Magic Charging Switch (mcs), though it may be not compatible with your device. Give it a try
Click to expand...
Click to collapse
But on S8 there is no file like voltage_max to define this using some shell script?
flipeicl said:
But on S8 there is no file like voltage_max to define this using some shell script?
Click to expand...
Click to collapse
Dont think so, depends on the device. In my case, I tried to do the same with a Nexus 7 2013, but was impossible...
Try looking for any of the files in /sys/class/power_supply