possible battery saver for eclipse .5 - Motorola Droid X2

if you go to /system/etc/init.d/ you will find S00tweaks
make sure that this is running on boot and as root. now open it up. scroll 1/2 way down until you see the section "Tweaking CPU freq and governor..."
in the 4th and 5th if blocks you should see something about echoing the value of 456000 to /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq and /sys/devices/system/cpu/cpu1/cpufreq/scaling_min_freq change that value to 216000
i was just looking around the system and found this script and didnt remember installing it so i opened it and read it. for some reason the governor is ondemand but doesnt have the min cpu freq set to the actual minimum frequency. im not sure if this will save battery since i just did it a few minutes ago but i see no reason to not have the min freq on an ondemand governor not be the minimum speed. so for everyone running eclipse .5 when your cpu has been idle its been running at a faster speed than it has to

Cool. If this script is in the system/etc/init.d folder doesnt it automatically run on boot?
If so can we just use a text editor and change these values or does it need to be done using script manager? I was under the assumption that since the init.d hack we no longer needed to use script manager to run as root and on boot. That as long as the script was in the init.d folder it would be run at boot.
Please correct me if I am wrong.
Also thank you for posting these values, I had attempted after Nitro referenced it in the OP this using the text editor but wasn't sure it was actually working.

I believe nitro has baked this script in to his rom. This is one of the reasons the phone runs so much faster and smoother, at the cost of battery consumption of course. But, by setting the min freq of the processor to 456, this helps the phone wake up faster and with the removed bloat and lack of blur, there is nothing in its way to cause the OS to run low on memory and possibly lock up and cause a reboot/give cause for a battery pull....
Somebody correct me if I am mistaken or am assuming anything here....

jeremy46er said:
Cool. If this script is in the system/etc/init.d folder doesnt it automatically run on boot?
If so can we just use a text editor and change these values or does it need to be done using script manager? I was under the assumption that since the init.d hack we no longer needed to use script manager to run as root and on boot. That as long as the script was in the init.d folder it would be run at boot.
Please correct me if I am wrong.
Also thank you for posting these values, I had attempted after Nitro referenced it in the OP this using the text editor but wasn't sure it was actually working.
Click to expand...
Click to collapse
oh yeah i forgot about the 2nd init.d running anything in there i guess i can take them off of run on boot now

DAG425 said:
I believe nitro has baked this script in to his rom. This is one of the reasons the phone runs so much faster and smoother, at the cost of battery consumption of course. But, by setting the min freq of the processor to 456, this helps the phone wake up faster and with the removed bloat and lack of blur, there is nothing in its way to cause the OS to run low on memory and possibly lock up and cause a reboot/give cause for a battery pull....
Somebody correct me if I am mistaken or am assuming anything here....
Click to expand...
Click to collapse
well im not sure about all that but i know that an ondemand governor runs at the min freq until the cpu is under a certain load then it jumps to the max freq until it is done. the way that it is currently set, it would be running at 456mhz all night instead of 216mhz which i could see it killing the battery. as for the wakeup and what not id assume it would put a decent load on the cpu so it would be running on max.

DAG425 said:
I believe nitro has baked this script in to his rom. This is one of the reasons the phone runs so much faster and smoother, at the cost of battery consumption of course. But, by setting the min freq of the processor to 456, this helps the phone wake up faster and with the removed bloat and lack of blur, there is nothing in its way to cause the OS to run low on memory and possibly lock up and cause a reboot/give cause for a battery pull....
Somebody correct me if I am mistaken or am assuming anything here....
Click to expand...
Click to collapse
There's still blur in nitros roms. The Apps may be aosp, but the blur framework is still there, else it would be a custom rom, not a stock based one.
Sent from my DROID X2 using Tapatalk

ilovesoad said:
There's still blur in nitros roms. The Apps may be aosp, but the blur framework is still there, else it would be a custom rom, not a stock based one.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
Always gonna be blur cuz it's a blur kernel too.
Sent from my DROID X2 using xda premium

i was poking around even more looking to see if it has the conservative governor, and it appears that the only 2 that it has are performance and powersave. so why is ondemand even in the script? is it some blackmagic where ondemand is only accessible while 2ndinit is doing its thing?

ilovesoad said:
There's still blur in nitros roms. The Apps may be aosp, but the blur framework is still there, else it would be a custom rom, not a stock based one.
Sent from my DROID X2 using Tapatalk
Click to expand...
Click to collapse
I meant he relative lack thereof not the not the fact that there is a complete lack of....

update before i go to work, it appears to be working i fully charged it at noon and rebooted it. im currently at 87% so that would be about 3% per hour where before i averaged 5%+ an hour.

Yea this won't give you much of any more battery life. It's on the Speedy Hack and can be done yourself for a long time. It's good you changed it back, no clue why it was bumped up theirs no need at all.

Related

Undervolting with SetCPU on Atrix

In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
just experiment, start with small increments (don't save your settings!!!) see if it reboots, if its stable for a day or two, increase it, when it starts crashing dial it back a notch.
Just like overclocking except in reverse and with voltage basically.
note I'm not sure re: kernel requirements, I haven't tried it yet with my atrix, and my current ROM runs stock kernel I think.
its hit and miss, for example on my SGTab I can't undervolt at all or else it crashes all the time, others get away with -100mAh across the board (bastards), but mine is happy on 1.1OC.
WTFsandwich said:
In my neverending attempt to extend my battery life, I installed SetCPU. The underclocking with profiles has extended my battery some, but Id like more.
I know very little about undervolting, its a new concept to me. Could someone elaborate on it, and may've suggest voltages for each speed setting? I hear it can do wonders for battery life.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
If you like cars it seem this will be the best way to explain it
http://forum.xda-developers.com/showpost.php?p=15947019&postcount=643
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Yes, start conservative.
Another way to use setcpu to improve your battery life is to set a screen off profile to restrict the CPU speed to minimum when the screen is off.
I tried that one, but it kept stalling my phone when turning the screen back on when it was at the bare minimum.
EDIT: For anyone wondering, -75 seems to cause frequent freezes.
Sent from my MB860 using XDA App
mramirezusa said:
If you like phones it seem this will be the best way to explain it
Think of it as tweaking the CPU of a phone to use just enough power to prevent it from failing in order to conserve battery life without affecting it's normal operation.
Click to expand...
Click to collapse
Fixed that for ya!
WTFsandwich said:
That is an excellent analogy. Basically, trial and error?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Any overclocking or underclocking is always trial and error. Rule of thumb is to only ever change one thing at a time in small increments, then test before adjusting again. Your approach should be methodical and not haphazard, i.e. in a PC change cpu clock speed in small increments until you fail to boot or BSOD, then change voltage in small increments until you boot and are stable again. Monitor temperatures all the time, and add cooling if necessary. If you take a methodical approach, and don't rush things, you can achieve surprising results with hardware/software tweaking.
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
A good test is to just use it as you normally would. If the phone doesn't reboot, you're good to go.
Sent from my MB860 using XDA App
edit: pls delete
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
WTFsandwich said:
What would be a good way to test once I increment a voltage?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Do something CPU intensive also to see if it crashes, like play a game. You want to stretch the phone to the limits to test it at the most extreme condition you will use it under.
WTFsandwich said:
So, I had checked off set at boot on the voltage screen. Unfortunately, this has rendered my phone to continually reboot and freeze, as one voltage is too low.
I do have a nandroid backup from right before installing SetCPU, and backups of working voltages, but I can't get the working ones restored before SetCPU starts and freezes my phone.
Is there a way I can default or disable the SetCPU settings without having to reflash the ROM or a backup of it?
Click to expand...
Click to collapse
Maybe a factory/data wipe?
Other than that I can't think of anything myself.
ddddddddddddd
you may try to use default stock kernel, on wich overcloking do not work.
re: setcpu, sorry I think you have to reflash... thats why you don't save the settings until you're sure
there is no shortcut way.... you may be fine for a day but next day it keeps crashing. Happened to me on my SG tab when I went to 1.2 for example, I thought it was hunky dory then a few days later crashing galore.
the longer you leave it for the better you are, its really your call to make. Some people prefer the extra speed and will live with a crash or two a week (not me, its my phone not gaming pc lol).
not sure how much stress testing you can/should do. Back when I was OCing PCs I would leave stress tests running overnight, but probably not a good idea to 100% CPU a phone overnight lol

SetCPU vs. Voltage Control

So far I've just been using SetCPU for over/underclocking but have never messed with undervolting. I was wondering what most people use if your main priority is undervolting for better battery life. I'm running Siyah 2.6.7 with SHOstock ROM. Any help/feedback is appreciated.
mpkothari said:
So far I've just been using SetCPU for over/underclocking but have never messed with undervolting. I was wondering what most people use if your main priority is undervolting for better battery life. I'm running Siyah 2.6.7 with SHOstock ROM. Any help/feedback is appreciated.
Click to expand...
Click to collapse
Well, undervolting is very tricky. Each CPU differs in its ability to undervolt, so settings that work for one may not work for others. You'd have to do some testing. I recommend either a.) undervolting one tick and run AnTuTu benchmark multiple times as well as a demanding game/app (Run them for a long time), or b.) undervolting one tick and using your phone normally as per your current usage and if by the next morning it's still running as normal, repeat one tick.
Do NOT set "Set on Boot" to on until you've run these tests and have had no issues.
Hope this helps a little.
Do not worry about 1400,1600 mhz till later since that's when your overclocking.
Bump everything else down by 25mv, run the stress test and a few intensive programs like benchmarks/games.
Keep doing that till you start to notice problems and then revert to the best setting you had. (make sure to backup or not set on boot)
Once you go through all that then you can do it for individual mhz and see which can still be lowered.
This should keep you busy for a hour or so.
I'll share what I posted in another thread. Doing stress tests are fine, but if you test throughout the course of a day or more, you have the opportunity to come across situations you might not think of during testing.
Simba501 said:
Ouch....I think the best way to experiment with undervolting is to use Voltage Control. Save the stock settings as your boot settings (it saves everything - governor, frequencies, etc; so, make sure those are what you want them to be as well), then undervolt (at the beginning of the day). If you make it to the end of the day with typical usage, you can save those as your new boot settings. Undervolt further at the beginning of another day, etc. Once you make it to the point where you get locked up, voltage control will set the previous values at boot and you'll know that those are your limits.
EDIT: If you want to play it extra safe, run values for more than one day.
Click to expand...
Click to collapse
I'm at work right now trying not to get easily distracted by xda since I keep checking whether or not an ICS leak has been ported or something. Thanks guys for your much appreciated input. I've been running with all voltage values knocked down by 50mV with the exception of 1.4 and 1.6 GHz. Those I kept stock since I'm not overclocking. So far so good actually with sio/ondemand and Max 500 Mhz. It's surprisingly smooth and battery of course is doing exceptionally well at these settings. Switched over to voltage control for now.
Sent from my SAMSUNG-SGH-I777 using xda premium
I personally have become very fond of voltage control where as I'd previously been using set-cpu for nearly ever since the H1 and mytouch days. Voltage controls just allows more freedom and tweakability.
Alucardis666 said:
I personally have become very fond of voltage control where as I'd previously been using set-cpu for nearly ever since the H1 and mytouch days. Voltage controls just allows more freedom and tweakability.
Click to expand...
Click to collapse
Right there with you. just "converted" to Voltage Control. (thanks Simba!)
K Rich said:
Right there with you. just "converted" to Voltage Control. (thanks Simba!)
Click to expand...
Click to collapse
Heh, glad I'm not the only defector
Simba501 said:
I'll share what I posted in another thread. Doing stress tests are fine, but if you test throughout the course of a day or more, you have the opportunity to come across situations you might not think of during testing.
Click to expand...
Click to collapse
That's the post I was thinking of, I just honestly couldn't figure out where I saw it or who wrote it.

Don't use SetCPU or cpu monitors with ICS!!!

Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Actually when I was on the second ics leak, and setcpu worked fine. I know this because I benchmarked before and after setting frequencies
Sent from my ADR6425LVW using XDA
benchmarking doesn't mean it wasn't running at full tilt when you didn't need it to. unless your kernel magically doesn't include perflock, it was.
also, there are some combinations of setcpu and monitoring that will work. at one point if i used setcpu, cpu monitor, and one other which i forget now, it would work, kind of. definitely not recommended.
Thats why I deaded mine. Phone was constantly overheating
Sent from my ADR6425LVW using xda premium
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
tspderek said:
since i stop fighting with the kernel i've had nothing but great battery life and performance since the first ICS leak.
Click to expand...
Click to collapse
Agreed. I had set CPU try to disable perflock and limit to 1200mhz on conservative and it ended up being worse battery and slower overall.
You're exactly right I advise everyone I discuss the topic with to make sure and avoid trying to over ride perflock with a CPU management app. It causes a conflict in my opinion which is a huge battery drain and also causes excessive heat due to the process of fighting for its life.
Sent from my ADR6425LVW using xda premium
I've been saying this I even started a thread to smash this rumor of ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels.
THERE WAS NEVER ANYTHING WRONG WITH ANY ICS LEAKS. JUST USER FAULT
Sent from my ADR6425LVW using XDA
richii0207 said:
I've been saying this I even started a thread to smash this rumor if ICS kernels running bad...apparantely people like to give out wrong information on these forums, reminds me of the news channels
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
con247 said:
You are correct. I would say upwards of 20% of what I read here is incomplete or straight up wrong.
Click to expand...
Click to collapse
My favorite part is when they try to sound like a dev, I guess everyone's a dev on here ;-P. At least I only say something I know from EXPERIENCE and not what I read ;-)
Sent from my ADR6425LVW using XDA
jayochs said:
tsp, what i don't understand is why something like system panel, which shows you scaling (but doesn't let you change it) showed the proper correct scaling between 384 and 1512 and hardly EVER hit full throttle on GB, but on ICS, it's always showing full throttle.
then i installed your widget you showed me, and it showed constantly chagning like system panel used to on GB.
any idea why? which one is rgiht??
Click to expand...
Click to collapse
the widget i posted is what you want. it should be scaling up and down, and settling eventually when nothing is really going on. the system panel that you tried clearly affected the perflock in some way. from what i understand, some apps/widgets look at the cpu itself, while others hit up the kernel for status. the ones that hit up the kernel are the issue. i'm not 100% on this, that's just what i've been told. all i know is my experience seems to match this.
tspderek said:
Many have complained about issues with the kernel in ICS. On any build, it is vital that you not use setcpu or any other cpu scaling app. Don't change the max/min freq, don't change the governer, nothing. Perflock will constantly reset any changes and cause the cpu to run at either full throttle or full min - no in between. Until we get kernel source and custom kernels, this will always be the case. It's something HTC does.
Many cpu monitor apps will do the same. The link in my sig has more info, and a link to a cpu monitor app that is safe to use with our kernel.
Click to expand...
Click to collapse
Hmm, that's weird, cause I've been using setCPU with ICS on the Rezound for months and it works great! My CPU scales fine and hits all the frequencies its supposed to. The min and max frequencies do change around seemingly randomly, but anyone can see by watching the current frequency display that it is always somewhere in between the range I selected, and always appropriate for the system load.
I've always had CPU Master installed. I just removed it, we'll see how it goes.

will setcpu work?

I'm all confused now about with s-on only being able to write to system in recovery...does that mean setcpu won't work or the values won't stick on reboot
thanks in advance
omario8484 said:
I'm all confused now about with s-on only being able to write to system in recovery...does that mean setcpu won't work or the values won't stick on reboot
thanks in advance
Click to expand...
Click to collapse
You got it! I just wouldnt even bother with setcpu right now its really not necessary. Technically many of its controls wont work at all because we dont have access to the system partition at all while booted meaning build.prop mods and many kernel tweaks are not accessable. Just w3ait till kernel source drops to start playing with that stuff. Its really not necessary anyway yet. This SOC is a hoss!!!!:laugh::good:
I installed SetCPU and it does work for controlling the CPU speed, but you obviously can't overclock. I originally wanted to use it to lower the speed when the display is off, but it was doing a great job on it's own and rarely went above 384MHz when it was just sitting, so I uninstalled it. The only thing I found that didn't work was the graph that shows the usage at each speed.
geoff5093 said:
I installed SetCPU and it does work for controlling the CPU speed, but you obviously can't overclock. I originally wanted to use it to lower the speed when the display is off, but it was doing a great job on it's own and rarely went above 384MHz when it was just sitting, so I uninstalled it. The only thing I found that didn't work was the graph that shows the usage at each speed.
Click to expand...
Click to collapse
If you wanna know that just download cpuspy!

FEB-9-15 [] Post_boot tweaks - An *interactive* boost

Drop this file in your /system/etc folder, replacing the stock one. Cleaned up, and modified to work with a stock kernel or lean kernel.
Please open up the file, and read some of the notes I added, so you know what this does and how to change it if you so desire. It is very basic and straightforward.
Also, please remember one thing, if you want to go to the stock kernel, simply change any words in the scripts from "interactiveX" to "interactive".
Recommended lean kernel 3.16 with these scripts.
Designed to work with ALL Galaxy Note 3's running touch wiz 4.4.2 ROMs and running lean kernel or stock kernel. Other kernels are not guaranteed due to the voltages applied.
This will make a huge difference in performance and battery. Been using this (developed by me) for a long time now.
Summary:
*I/O optimization
*tuned interactive parameters
*fixed sysfs permissions for cpu's (root now has full control of sysfs tuneables)
*GPU sysfs identified for user to customize
*screen off frequency set to 1.2 GHz (can be changed by user)
*custom voltage set for bin 2 device. (Read instructions within file to adjust for others bins accordingly)
*custom mpdecision tuning and other relevant instruction regarding mpdecision binary
*general CPU tweaks for better performance, responsiveness and battery life (yes all 3 can be achieved, and are)
Again, open the file with a file explorer (or notepad+ in windows). Read it, understand it, adjust what you want, or leave it be. These settings are very much dialed in for the interactiveX governor of LK. It won't get much better. I'd say take a look at the voltage portion and mpdecision for now (found at the end).
Once more, drop file into the /system/etc directory... Replace the existing one, and reboot.
FILE DOWNLOAD
Updated today... many useful changes, and fixes (set up for stock kernel for now)
https://www.dropbox.com/s/tjlygujptls3lks/init.qcom.post_boot.sh?dl=0
Thanks man!
Thanks man best Antutu score.
Best. Disclaimer. Ever.
Sent from my SM-G900V using XDA Free mobile app
Hahahahahahah I love the disclaimer.
Thanks! Helps a lot
Sent from my SM-N900V using xda app-developers app
I've noticed my phone lags alot less now and some things I had going wrong (if I turned torch on more than 15 seconds it would freeze and Multiwindow didn't like to work) work now. I don't know why or how or even if it is supposed to do anything to those things and it's just a very odd coincidence. But I've noticed my battery life is horrible now. Running it with Alliance 2 and with my ZeroLemon I used to get 10-11 hours on screen time and that's down about half to 5 or 6 hours. I know you said you could tweak stuff but I have no idea about that. Any recommendations for me to change in the script? Thanks again if for anything my phone running smoothly again!
amebiasis said:
I've noticed my phone lags alot less now and some things I had going wrong (if I turned torch on more than 15 seconds it would freeze and Multiwindow didn't like to work) work now. I don't know why or how or even if it is supposed to do anything to those things and it's just a very odd coincidence. But I've noticed my battery life is horrible now. Running it with Alliance 2 and with my ZeroLemon I used to get 10-11 hours on screen time and that's down about half to 5 or 6 hours. I know you said you could tweak stuff but I have no idea about that. Any recommendations for me to change in the script? Thanks again if for anything my phone running smoothly again!
Click to expand...
Click to collapse
If you aren't using lean kernel, you need to change the governor in the script to NOT say "InteractiveX"... Stock, or all other kernels need "interactive"... Otherwise the governor will be stuck on performance.
That is likely your issue.
Most people don't know that the note 3 boots with the performance governor enabled. The /system/etc/init.qcom.post_boot.sh file executes after the boot complete flag and changes the governors, among other things.
Edit the file, change the governor call out to "interactive".
Should fix it.
Thank you sir!
Running amazing after changing things over to "interactive" in the script with the stock kernel. Much more fluid speed on Eclipse with the battery life a bit better. Thanks for sharing! :highfive:
Wow night and day difference by changing that script to just interactive. Been flying all day playing games and watching movies total SOT (with my ZeroLemon) is just over 5 and a half hours screen brightness at about 65% using Lux and Bluetooth and I'm only at 67% awesome job man and thank you for steering me in the right direction!
Is the 300 slot removed from this script?
Also to my understanding this is mainly for the dev edition and lean kernel correct. But most of us r on the retail. Is there anything else to change besides the interactive for better performance?
Sent from my SM-N900V using xda app-developers app
stalls said:
Is the 300 slot removed from this script?
Also to my understanding this is mainly for the dev edition and lean kernel correct. But most of us r on the retail. Is there anything else to change besides the interactive for better performance?
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I can tell you for sure...this scripts works fine for plain jane stock kernel (because that is all you can use on retail Verizon N3) as long as you change the "interactiveX" to just plain "interactive"
Obviously you need root to swap out the script.
Sent from my Note 3 via Tapatalk
donc113 said:
I can tell you for sure...this scripts works fine for plain jane stock kernel (because that is all you can use on retail Verizon N3) as long as you change the "interactiveX" to just plain "interactive"
Obviously you need root to swap out the script.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Big difference in battery life when i changed interacticeX to interactive. Thanks for this OP. :thumbup:
Just want to provide my stats after using the script on eclipse rom 2.2./interactive. Screen on time was 6.5 hours with the phone. Before the script I would average about 4 hours. I want to thank the OP, this was a great tweak. Thumbs up.
Just giving you all a heads up.... I think there may have been a few errors in the stock init.qcom.post_boot file (they are human too, remember).
I am testing a few small changes to certain lines in the "factory" script to make sure. A brief explanation of it is that there are certain lines I removed from the one you all are using right now, and I did so because the file paths being called out did not exist!
However, I was going over this again tonight, getting ready for the official LP release and decided to review this odd discrepancy one more time. After doing some digging, I found that the file that some of those values were intended to be written to, were actually somewhere else!
Doh! - Sammy/QC. It is very possible that this location changed from a previous design or fs structure and somebody simply forgot to modify the script. Very interesting indeed.
Anyways, after I run this for a couple of days and do a little bit more investigating, I'll post the updated script for all of you.
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
red_can_soda said:
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
Click to expand...
Click to collapse
Question. So if this new file is set up for stock kernel for now, is it set to interactive or do we still need to change from interactiveX on retail?
Edit: was being lazy. Went ahead and went through script. Didn't see interactiveX anywhere.
red_can_soda said:
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
Click to expand...
Click to collapse
I'm not so sure the latest script is good or not....on my stock kernel Verizon N3 (NC4 firmware and kernel with NK1 radio) using the new script seems to have killed my battery life. I went from 33% to 20% in about 20 to 30 minutes.
I reset by restoring original script...rebooting...restoring your original script (interactiveX changed to interactive)...rebooting
I had to charge the phone so can't give a real check until I get back to 33% or so.
Sent from my Note 3 via Tapatalk
donc113 said:
I'm not so sure the latest script is good or not....on my stock kernel Verizon N3 (NC4 firmware and kernel with NK1 radio) using the new script seems to have killed my battery life. I went from 33% to 20% in about 20 to 30 minutes.
I reset by restoring original script...rebooting...restoring your original script (interactiveX changed to interactive)...rebooting
I had to charge the phone so can't give a real check until I get back to 33% or so.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Same here on battery drain. Not as smooth either running biggins rom "possible reason". I might try this on a stock Rom to see if that makes a difference. Hard to beat untouched biggins right now though.

Categories

Resources