yashsingh1/xdaforums huggingface dataset:
[T-Mobile LG V10 Android Development] warBeard_actual:
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!
[T-Mobile LG V10 Android Development] danstheman7:
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.
[T-Mobile LG V10 Android Development] xtremelora:
Nice...

Desde V10 (LG-H901)
[T-Mobile LG V10 Android Development] kongming:
For all variants? Is it compatible with H961N LP?

Looks promising and wanted to try.
[T-Mobile LG V10 Android Development] roosxter:
How do I know it worked? I followed the steps
[T-Mobile LG V10 Android Development] BoiBundy:
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)
[T-Mobile LG V10 Android Development] iamtheon:
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|root@pplus:/ # mv init.qcom.post_boot.sh /system/etc

mv: init.qcom.post_boot.sh: remove: Read-only file system

1|root@pplus:/ #
[T-Mobile LG V10 Android Development] 11868:
i got problem with the !!!!!!cd /sdcard , writing

i tried cd /storage/emulated/0

and worked for me
[T-Mobile LG V10 Android Development] iamtheon:
I tried that, but doesn't hurt trying again.

Edit: It worked. I did the same thing lol oh well thanks [MENTION=5961870]11868[/MENTION]
[T-Mobile LG V10 Android Development] agrenwa:
Can this be done with the root explorer instead of terminal emulator?
[T-Mobile LG V10 Android Development] klbjr:
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?
[T-Mobile LG V10 Android Development] warBeard_actual:
Your system wasn't mounted as rw when you executed the command

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.

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.
[T-Mobile LG V10 Android Development] rirozizo:
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 :)
[T-Mobile LG V10 Android Development] danstheman7:
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.
[T-Mobile LG V10 Android Development] amoot329:
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?
[T-Mobile LG V10 Android Development] warBeard_actual:
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.

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.

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.
[T-Mobile LG V10 Android Development] rirozizo:
I recommend Google Drive or Box
[T-Mobile LG V10 Android Development] Negan:
[MENTION=7372544]warBeard_actual[/MENTION]

Great job buddy on this.... [MENTION=309990]freeza[/MENTION] 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!
[T-Mobile LG V10 Android Development] freeza:
bencze, proof or it didn't happen
[T-Mobile LG V10 Android Development] jaysonic88:
Thx [MENTION=7372544]warBeard_actual[/MENTION]

Going to bang on it awhile and see if any anomaly come up (none so far). Though frankly the fact that i just loaded the 007 ROM from Eliminater74 may sku results. So far so good though.
[T-Mobile LG V10 Android Development] Vipery:
I will try it now, sorry didn't see the little update. I swap old script file with this new one on the Techlyfe zip (ZRam removed) and flash it. Than report asap.
[T-Mobile LG V10 Android Development] warBeard_actual:
[MENTION=7358920]jaysonic88[/MENTION] [MENTION=6066294]Vipery[/MENTION] and everyone else... If you are coming from a stock ROM, or reflashing a new ROM, don't forget to remove the zram file in /etc
[T-Mobile LG V10 Android Development] jaysonic88:
Ok so now i'm intermittently getting a toast notification saying, "The network is unavailable!" and then wifi disconnects. It'll reconnect but from what i can tell it's goes off and on. Wifi Calling obviously didn't like it and is no longer enabled. [MENTION=7372544]warBeard_actual[/MENTION]
[T-Mobile LG V10 Android Development] demoncamber:
Testing now, not on wifi so can't speak for wifi calling atm

---------- Post added at 09:53 PM ---------- Previous post was at 09:11 PM ----------

Ok yes, still having the app issue with the test version
[T-Mobile LG V10 Android Development] dimm0k:
back to the WiFi calling... do you recall installing BusyBox previously when WiFi calling broke? I'm currently in the process of putting things back together and after installing BusyBox to /su/bin I noticed WiFi calling broke!
[T-Mobile LG V10 Android Development] warBeard_actual:
Can you guys post the file from last time that works?
[T-Mobile LG V10 Android Development] Scooter5150:
Just trying to help...

8182a74943b50f4e22671b7e931d9ee1

That's the md5 of the file I'm currently running, dated 27MAY2016.

****ing smokes.

Ah... I'm on AT&T. I don't get that cool Wifi calling stuff.
[T-Mobile LG V10 Android Development] warBeard_actual:
Everyone here, please try this one and report back. Pretty sure I found the problem.

https://drive.google.com/file/d/0BzM9W6qUvx-gTXY4TDNCTHB0bVE/view?usp=drivesdk

Thanks.
[T-Mobile LG V10 Android Development] Scooter5150:
Working well here...

MD5 = da146d7745690e48ff3bbe505e09e32a
[T-Mobile LG V10 Android Development] Bildo41383:
how do i know i have the right model for this mod?
[T-Mobile LG V10 Android Development] warBeard_actual:
Open terminal emulator app,

Run this command:

cat /proc/cpuinfo

if you see 8992 anywhere, you can use this.
[T-Mobile LG V10 Android Development] dimm0k:
mind sharing what the problem was?
[T-Mobile LG V10 Android Development] warBeard_actual:
Is the issue resolved for you? Want to make sure everyone is good before I say what I found... Don't want a placebo effect.
[T-Mobile LG V10 Android Development] dimm0k:
honestly I have to say my issue of no WiFi calling was due to BusyBox and not your mod that broke it... if you have any answers on BusyBox, please share!
[T-Mobile LG V10 Android Development] jaysonic88:
[MENTION=7372544]warBeard_actual[/MENTION]

With the latest one you posted here at this link https://drive.google.com/file/d/0BzM...w?usp=drivesdk

I can confirm that my wifi calling is working as expected and my wifi is not disconnecting/reconnecting anymore. Thank you!

---------- Post added at 05:23 PM ---------- Previous post was at 04:56 PM ----------

[MENTION=5687667]dimm0k[/MENTION]

Which busybox version? I'm using this one, https://play.google.com/store/apps/details?id=stericson.busybox.donate&hl=en The Busybox Pro and i occasionally do a smart install. I haven't immediately noticed issues but occasionally i will find wifi calling broke without any obvious culprit.
[T-Mobile LG V10 Android Development] dimm0k:
[MENTION=7358920]jaysonic88[/MENTION] that's the exact version I used and installed to /su/bin. I noticed that after painstakingly restoring my system section by section, while also backing up and restoring backups from TWRP each step of the way that as soon as I installed BusyBox, WiFi calling stopped working. this actually happened more than a couple of times and I realized it only after I had verified SuperSU, Xposed, and a bunch of apps worked properly with WiFi calling before I tried BusyBox again. as soon as it installed and I rebooted, WiFi calling never came back. extra proof to myself was after uninstalling BusyBox that WiFi calling worked again. if you do a search on the Internet there's actually a few cases of users reporting this, however none of them came across a solution... so I'm still searching.
[T-Mobile LG V10 Android Development] warBeard_actual:
Those of you having issues with busybox, install it to /system/xbin and not /su/bin, issue should go away.
[T-Mobile LG V10 Android Development] warBeard_actual:
Good to know. Seemed odd. Thanks for following up.
[T-Mobile LG V10 Android Development] Techlyfe:
So the recent one you posted, is that official or not necessary now that busybox seems to have been the culprit to the wifi issues?
[T-Mobile LG V10 Android Development] demoncamber:
Late to the party,but trying now

---------- Post added at 10:45 PM ---------- Previous post was at 10:35 PM ----------

So far so good, I think you got it dude.
[T-Mobile LG V10 Android Development] raging9:
So far so good...(end of day 1 after replacing file)
[T-Mobile LG V10 Android Development] warBeard_actual:
Keep testing, I'll update the main links if nobody reports any issues the next couple of days with the lockups.

Thanks again, guys. Sorry for the small blip there.

The gist of the issue is that the file was corrupted.

And again, as stated before, the file had nothing to do with WiFi calling being borked.
[T-Mobile LG V10 Android Development] Bildo41383:
Looking like I cant, damn.
[T-Mobile LG V10 Android Development] warBeard_actual:
You know, I misspoke, try this...

cat /system/build.prop

"ro.product.board=msm8992"

That line should be somewhere in the output. It means you have a snapdragon 808
[T-Mobile LG V10 Android Development] demoncamber:
Still testing, not a single issue yet.
[T-Mobile LG V10 Android Development] Scooter5150:
Checking in. Solid here, as well.
[T-Mobile LG V10 Android Development] MiamiCubano305:
Rename file?

Do we re name the file to init.qcom.post_boot.sh? The file is a .txt when downloaded. The name of it is 0BzM9W6qUvx-gTXY4TDNCTHB0bVE.txt
[T-Mobile LG V10 Android Development] warBeard_actual:
Sounds like we've got it pretty well figured out. The file appears to have been corrupted. I retraced every chance I made, one by one, and couldn't single out one specific issue with the settings I implemented. All I did to fix it, was make a new file from scratch.
[T-Mobile LG V10 Android Development] gillim74:
I've been running it with no issues
[T-Mobile LG V10 Android Development] warBeard_actual:
I'll update the main links tomorrow night. Thanks for testing, guys.
[T-Mobile LG V10 Android Development] Techlyfe:
Damn, gotta hate when you backflip through hoops only to find out you just needed to take a small step forward to figure out the problem. GJ man!
[T-Mobile LG V10 Android Development] warBeard_actual:
[MENTION=4608158]vitök[/MENTION]

[MENTION=6066294]Vipery[/MENTION]

[MENTION=4450292]demoncamber[/MENTION]

[MENTION=5687667]dimm0k[/MENTION]

[MENTION=2626255]ratchetrizzo[/MENTION]

[MENTION=5703276]raging9[/MENTION]

[MENTION=7358920]jaysonic88[/MENTION]

[MENTION=7457986]Scooter5150[/MENTION]

[MENTION=4224764]Techlyfe[/MENTION]

Hey, guys, first and foremost, I apologize for the bad file. Want to assure you that the issue has been resolved, and my sincerest thanks for those of you who tested this out for me to confirm a few things (mainly that I wasn't going crazy). The gist of the problem was that the file had been corrupted - no good. And, for lack of a better simple way to put it, it was probably not executing all the way, was writing some nebulous values somewhere, who knows.

Since we’re clear from a system stability aspect, I made a couple of changes while I was in there so your data should hang out in RAM a bit more (not much more). The dangerously version is still included in the change log.

I will work on the ROM this week.
[T-Mobile LG V10 Android Development] dimm0k:
if you get the chance, can you update the first post as to what this newer version of the non-dangerously version does? there looks to be quite a lot of changes between this new version and the one that was released on the 25th according to the changelog. for example swappiness is now 10 vs 40 previously.
[T-Mobile LG V10 Android Development] ZeNiXxX:
Thanks.

You don't have to apologize in my opinion. It's normal that things aren't always running perfect. moreover we are a Tester community , we test and report so it's all right. We can at least test and report that's our work here :)

Gesendet von meinem LG-H815 mit Tapatalk
[T-Mobile LG V10 Android Development] Vipery:
Hey mate, don't need to apologize. Those things are normal, users also esixt for testing releases from developers. The important thing is that you care about us and works on a fix. You are the best!

Just one thing, can I manually replace the file with a file explorer and set permissions. Or it's that important make it from terminal emulator? Let me know!

---------- Post added at 10:41 PM ---------- Previous post was at 10:40 PM ----------

Or even better, can I take the Techlyfe file, than replace the old script with the latest one and flash the zip,
[T-Mobile LG V10 Android Development] ratchetrizzo:
I didn't have a problem with the version that was supposed to be corrupted, I didn't change over to the testing build until yesterday and things are still working nice and smooth. I'll update to the one you just posted later today or tomorrow when time permits. Thanks for the great work. I'm still on lp if it makes a difference, I just haven't seen the need to update and redo everything in mm when everything is working so well for me as is.
[T-Mobile LG V10 Android Development] warBeard_actual:
[MENTION=6066294]Vipery[/MENTION] , of course, there is more than one way to do it. The bottom line is: the existing file in /system/etc gets deleted, the new one gets copied over and permissions are set. However you choose to do that is up to you, it won't effect the outcome. I just enjoy terminals because they are faster for me and a great learning tool for most. And thank you

[MENTION=2626255]ratchetrizzo[/MENTION] , you should consider making the jump, man. 6.0 is quite a leap in performance and overall system fluidity. The java compiler Google introduced in M is quite a breath of fresh air on this device. Battery life improvements, hardware efficiency, software efficiency.

To sum up what I changed, I decided to move towards more of a vm knob in sync with some of the common desktop distros like RedHat and Mint. The only exception being swappiness. I've reduced it to maximize performance by minimizing the likelihood of swap memory being used when it really isn't needed. My opinion is that swapping should occur as a failsafe for OOM conditions. So, setting the value at 10% or less is really where its at. I've read tons of various materials on this, and that approach makes a bit more sense for us. If we were dealing with low end, slower devices, with less resources onboard, I'd be thinking more in line with the 3.10.84 kernel's default settings.

I also reduced the back_seek_max tunable for cfq.

Not much was done, but it'll be better.
[T-Mobile LG V10 Android Development] Scooter5150:
No worries! And no apology necessary. I'm glad to help (however small) in any whatever way I am able. Thank you for your work!
[T-Mobile LG V10 Android Development] Techlyfe:
Thanks again and agreed, no need to apologize. Isht Happens!

Oh and thanks for including the Hash, makes it easier to verify the files.

Here's are the zips for the lazy people :P

Myself included of course :)

Oh yeah, these zips are easily updated just by adding the most recent tweak into the root of the zip. I use winrar and can just drag and drop the file into the zip and it will update it. It will not work if the file name is anything other than init.qcom.post_boot.sh, the only thing is the nice little words that come up during the installation won't match the versions, no biggie and u can even edit that if you like.
[T-Mobile LG V10 Android Development] sirsomething:
[MENTION=7372544]warBeard_actual[/MENTION] on the latest non dangerously build on g4 it seems to use little cores more with 1440mhz than with a lower frequency (while in use of course). Is this normal?
[T-Mobile LG V10 Android Development] Bildo41383:
Do i need both zip files per version?
[T-Mobile LG V10 Android Development] raging9:
No, you only flash one of them. "remZ" removes your ZRAM file if you haven't done it already and the "keepZ" doesn't remove the ZRAM file. It's up to you on which you choose. I'm using the "dangerous remZ" and I have yet to experience any issues. Hope this helps..
[T-Mobile LG V10 Android Development] MiamiCubano305:
The downloads are .txt files.

I'm not understanding how to implement them as a file, and unable to locate the flashable zip warBeard_Tweaks050916.zip)
[T-Mobile LG V10 Android Development] Techlyfe:
What browser are u using?

Check one of my most recent posts anytime Warbeard releases an update, usually within 24 hours there will be links to the new files.

Btw, just for more clarity, early on there was a question wether to keep zram or remove zram, I only made it easier for those who wanted to test keeping zram or removing zram and to see if either or is a benefit to the tester personally.

It is still recommended by Warbeard to remove zram.

There was a slight wondering on whether to keep it when using his dangerously tweak, to avoid the memory ceiling I believe.
[T-Mobile LG V10 Android Development] warBeard_actual:
The question was more of a thought, really. Not anything truly recommended. This was before we figured out the freezing issues.

The bottom line is you will hit a wall eventually, but Linux does a good job of cleaning up your RAM cache and killing processes that are expendable once you start to approach the limit.

I still have found it very difficult to truly force OOM situations with this device to the point where you are locking up OS and halting IO operations, creating lag, etc.

You can absolutely use zRAM if you need to, it is what it is there for, but expect a hit in performance and battery life. Totally up to the user, at the end of the day.
[T-Mobile LG V10 Android Development] Mr.FREE_Bird:
Yes, I noticed the same thing... But I don't really mind, since I use and test this tweak it seems that my battery life has been improved.

Don't know about you? Does it have a negative impact on your battery life of your G4?
[T-Mobile LG V10 Android Development] sirsomething:
Yeah, it has a negative impact. On casual tasks it behaves well but the phone starts heating while browsing and normal stuff. While using camera it almost burns. So it's a no go for me
[T-Mobile LG V10 Android Development] trungvov10:
So I just need to rename the original file in system/ect, then drop the new one in, set permissions, right?

Btw, how is it work for everyone so far?
[T-Mobile LG V10 Android Development] raging9:
Correct...then obviously reboot your phone. And definitely do it. My phones been a waaayyyy better since I've used this mod. And you can always switch it back...but your probably won't if it works like mine. Good luck! Oh and remove your ZRAM file, too if you wish. I did bc warbeard recommends it and like I said..I love the change in performance. Refer to OP for the info on the ZRAM file. Good day.
[T-Mobile LG V10 Android Development] trungvov10:
so ummm.. can u just tell me how to delete zram file? I thought zram will be disable when the file is replaced
[T-Mobile LG V10 Android Development] demkantor:
You can always flash my aroma installer

It has the options to back up and restore your current setup (in regards to this mod)

And can flash warberad_actual's latest tweak - it also uninstalls zram

(If you choose to backup before you make changes via aroma installer when you restore zram will come back too)

http://xdaforums.com/showthread.php?t=3388850
[T-Mobile LG V10 Android Development] trungvov10:
the lastest is the dangerous verson?
[T-Mobile LG V10 Android Development] demkantor:
Yes but I have e no issues using the past few days now. I will go ahead and add his previous version shortly, just been a bit busy

And if you read through his explanation it's more of an overall warning and is still unlikely to cause issues for anyone, of course this will depend on how you use your phone - but haven't seen much of complaints

Also note you can quick restore via aroma if you run into trouble

I suggest you try it, may be the best thing I've done to this phone since root