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

patalao

patalao

Senior Member
Jan 24, 2009
1,204
953
0
Feira
Apr 7, 2016 at 10:50 AM
After a cicle of battery here are my stats with your second upload and some changes from my side to serve my needs on G4.
Rom: Assics Rom v1. 3
Kernel: imperium kernel 2.6
Apps for battery: Greenify and Doze settings editor

My stats with some gaming and data always changing between wifi and 4G because of bad wifi on work.









Waiting for your new update to test.
 
  • Like
Reactions: warBeard_actual
W

warBeard_actual

Senior Member
Mar 27, 2016
363
1,130
0
Apr 7, 2016 at 11:02 AM
patalao said:
After a cicle of battery here are my stats with your second upload and some changes from my side to serve my needs on G4.
Rom: Assics Rom v1. 3
Kernel: imperium kernel 2.6
Apps for battery: Greenify and Doze settings editor

My stats with some gaming and data always changing between wifi and 4G because of bad wifi on work.









Waiting for your new update to test.
Click to expand...
I might add, for you, specifically, that I would do maybe some comparison tests with the stock file, and mine, on the stock kernel. You are running Android 6.0 (I can tell by your screen on time ss) and you are not only using a different ROM, but a different kernel than stock as well.

Users simply be aware of this, as results vary across versions of Android, inherently. Just test your own device, and monitor improvement or degradation.

That being said, this looks good, and I'm sure you will be pleased with the next iteration of the shell scripts. I've been running them today and the results have been excellent.
 
Last edited:
  • Like
Reactions: patalao
W

warBeard_actual

Senior Member
Mar 27, 2016
363
1,130
0
Apr 7, 2016 at 7:22 PM
supergear said:
Quick note date should red 4/6/2016

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

---------- Post added at 07:04 PM ---------- Previous post was at 07:03 PM ----------


*Read

Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Fixed it. You'd think that the time in front of a terminal would mean that no mistakes are ever made.... sometimes it is the reason. lol

thx

After a full charge of testing, here are the first test results, keep in mind yours may still vary, but this was an improvement of about 34 minutes of screen on time for me (see screenshots)
 

Attachments

Last edited:
  • Like
Reactions: danstheman7 and Nandroid28
D

danstheman7

Senior Member
Apr 20, 2011
493
64
0
Long Island NY
Apr 8, 2016 at 4:52 AM
warBeard_actual said:
Fixed it. You'd think that the time in front of a terminal would mean that no mistakes are ever made.... sometimes it is the reason. lol

thx

After a full charge of testing, here are the first test results, keep in mind yours may still vary, but this was an improvement of about 34 minutes of screen on time for me (see screenshots)
Click to expand...
Looks great to me! When will you post this new edit? Looking forward to it!
 
  • Like
Reactions: warBeard_actual
ousoonerchase

ousoonerchase

Senior Member
Oct 22, 2012
179
76
0
Norman
Apr 8, 2016 at 5:32 PM
Charliebill33 said:
So, I remain unsure as to what to do; none of my init.qcom match the post_boot; while the post_boot is referenced by something else. So should I remove the post_boot I have and then wedge in your new post_boot amongst the init.qcom directions? Any help would be appreciated.

Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
Same question here. After applying the new folder and setting permissions, and reboot, I checked kernel adiutor and it's not showing the new CPU governor is what is being used. I haven't changed any settings other than applying the file you provided, and kernel adiutor is not set to apply on boot. What am I missing?

Edit: added pictures
 
Last edited:
  • Like
Reactions: warBeard_actual
W

warBeard_actual

Senior Member
Mar 27, 2016
363
1,130
0
Apr 8, 2016 at 9:52 PM
Charliebill33 said:


So, I remain unsure as to what to do; none of my init.qcom match the post_boot; while the post_boot is referenced by something else. So should I remove the post_boot I have and then wedge in your new post_boot amongst the init.qcom directions? Any help would be appreciated.

Sent from my LG-H901 using XDA-Developers mobile app
Click to expand...
First question, is what device and OS are you using? If you have an MSM8992, the file should be there, unless you removed it. Did you try to execute the terminal instructions in the OP?

ousoonerchase said:
Same question here. After applying the new folder and setting permissions, and reboot, I checked kernel adiutor and it's not showing the new CPU governor is what is being used. I haven't changed any settings other than applying the file you provided, and kernel adiutor is not set to apply on boot. What am I missing?

Edit: added pictures
Click to expand...
Same reply for you as for CharlieBill. Did you already try to follow the OP instructions.


Bottom line is that if you are using a device that has the MSM8992, you should have this file built into your /system/etc.

The update is coming tomorrow, I have been doing some extensive testing the last few days with very positive results. I'm currently looking at 17 hours off the charger, at 17% battery, with close to 6 hours screen on time. This is another improvement for my own device, given my own usage on a daily basis.

I will be putting up a build.prop file as well, with some more instructions for the proper implementation of the post_boot.sh file - specifically, dealing with the stock zram modules (there is another file in /system/etc that should be removed completely if you are using this mod for your device.)

EDIT*** added some photos here... I'll post the new file tomorrow
 

Attachments

Last edited:
  • Like
Reactions: raging9, Charliebill33, ousoonerchase and 1 other person
Charliebill33

Charliebill33

Senior Member
Dec 29, 2015
97
61
0
Seattle, WA
Apr 10, 2016 at 4:00 AM
warBeard_actual said:
First question, is what device and OS are you using? If you have an MSM8992, the file should be there, unless you removed it. Did you try to execute the terminal instructions in the OP?



Same reply for you as for CharlieBill. Did you already try to follow the OP instructions.


Bottom line is that if you are using a device that has the MSM8992, you should have this file built into your /system/etc.

The update is coming tomorrow, I have been doing some extensive testing the last few days with very positive results. I'm currently looking at 17 hours off the charger, at 17% battery, with close to 6 hours screen on time. This is another improvement for my own device, given my own usage on a daily basis.

I will be putting up a build.prop file as well, with some more instructions for the proper implementation of the post_boot.sh file - specifically, dealing with the stock zram modules (there is another file in /system/etc that should be removed completely if you are using this mod for your device.)

EDIT*** added some photos here... I'll post the new file tomorrow
Click to expand...
Warbeard, I'm using a TMO LG V10 with the MSM8992 SoC. I'm running Siraltus deodexed ROM (thread in TMO V10). I wiped and clean flashed yesterday and wiped again.

I have yet to see or find the file and I have read the OP (several times) and with the Terminal Emulator I've gotten about 2/3's through before it says the file I'm referencing isn't there.

I'll try again tomorrow. With next week's V10 Marshmallow rollout, will these tweaks stick or be over-ridden by the new code?

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

Charliebill33

Senior Member
Dec 29, 2015
97
61
0
Seattle, WA
Apr 10, 2016 at 4:08 PM
Amd4life said:
Running the same siraltus rom, and the files ARE present. Try using root explorer to move the files manually. Its must easier that way. Just make sure you change the permissions properly
Click to expand...
Please pardon the ignorance. I found the post_boot file and made the change using root explorer. I've checked permissions on the post_boot and they are enabled, I also set the zramswap to .bak (per OP). I moved the downloaded post_boot file to the etc folder before deleting the original post_boot file.

Based upon the above, my remaining question is: should the post_boot file have grown to 97 KB; when the original file was 64 (and change), while the downloaded post_boot file was 14 (and change)?
 
llawen

llawen

Senior Member
Dec 5, 2012
340
169
0
Apr 12, 2016 at 12:56 AM
Double checked and file was moved to system/ECT will see how it goes. Thanks.
The phone does feel snappier

Sent from my LG-H901 using Tapatalk
 
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone