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

[demoncamber]

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.

Late to the party,but trying now

Sent from my LG-H811 using Tapatalk

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

Good to know. Seemed odd. Thanks for following up.

So far so good, I think you got it dude.

Sent from my LG-H811 using Tapatalk

 

[raging9]

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.

So far so good...(end of day 1 after replacing file)

 

[warBeard_actual]

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?

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.

 

[Bildo41383]

Open terminal emulator app,

Run this command:

cat /proc/cpuinfo

if you see 8992 anywhere, you can use this.

Looking like I cant, damn.

 

[warBeard_actual]

Looking like I cant, damn.

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

 

[demoncamber]

Still testing, not a single issue yet.

Sent from my LG-H811 using Tapatalk

 

[Scooter5150]

Checking in. Solid here, as well.

 

[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

 

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

 

[gillim74]

I've been running it with no issues

 

[warBeard_actual]

I'll update the main links tomorrow night. Thanks for testing, guys.

 

[Techlyfe]

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.

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!

Sent from my LG-H901 using XDA-Developers mobile app

 

[warBeard_actual]

@vitök
@Vipery
@demoncamber
@dimm0k
@ratchetrizzo
@raging9
@jaysonic88
@Scooter5150
@Techlyfe

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.

 

[dimm0k]

@vitök
@Vipery
@demoncamber
@dimm0k
@ratchetrizzo
@raging9
@jaysonic88
@Scooter5150
@Techlyfe

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

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.

 

[ZeNiXxX]

@vitök
@Vipery
@demoncamber
@dimm0k
@ratchetrizzo
@raging9
@jaysonic88
@Scooter5150
@Techlyfe

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

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

 

[Vipery]

@vitök
@Vipery
@demoncamber
@dimm0k
@ratchetrizzo
@raging9
@jaysonic88
@Scooter5150
@Techlyfe

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.

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!

Sent from my LG-H815 using XDA-Developers mobile app

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

Sent from my LG-H815 using XDA-Developers mobile app

 

[ratchetrizzo]

@vitök
@Vipery
@demoncamber
@dimm0k
@ratchetrizzo
@raging9
@jaysonic88
@Scooter5150
@Techlyfe

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.

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.

 

[warBeard_actual]

@Vipery , 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
@ratchetrizzo , 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.

 

[Scooter5150]

@vitök
@Vipery
@demoncamber
@dimm0k
@ratchetrizzo
@raging9
@jaysonic88
@Scooter5150
@Techlyfe

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.

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!

 

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