while searching the android forum i came upon this script..... SMURFED OUT
pros: highly customisable script,, optimization as per user requirement ...
battery tweaks, memory tweaks, speed tweaks, governor tweaks, 3g and wifi tweaks, SD card tweaks, and a bunch of random tweaks. Some collected from a bunch of different phones tweaks and others created by developer.
----The script will search out every line in your build.prop and remove any line that is there that I am adding and remove it first to reduce duplicate codes. It will remove a whole list of other init.d files that conflict with it. Will also create a few other files and folders to add functionality and speed optimization to your phone.
What if you do not like the tweaks that I added.....well the script creates back-ups for you and you can choose the option to Un-Smurf and it will set you back to before you installed.---
READ MORE HERE THE ORIGINAL THREAD --
http://forum.xda-developers.com/showthread.php?t=1517724
thanks the developer if u find it useful for use......
IMPORTANT--- please dont fill up the thread with-- is this better than that script or anything else,, use this if it suits your need .... else u always have a variety to choose from....
this one script is for DEODEXED ROMS only...... closes most of the system app thus freeing up memory increasing battery life and removes lagginess
http://forum.xda-developers.com/showthread.php?t=1665331
ummm, just a doubt, are scripts optimised for odexed or deodexed ROMs?
If yes, would the smurf script work for an odexed ROM?
didnt find anything related on that thread
[P.S. - I hope this isnt a very obvious fact that i missed
Soumitra.5693 said:
ummm, just a doubt, are scripts optimised for odexed or deodexed ROMs?
If yes, would the smurf script work for an odexed ROM?
didnt find anything related on that thread
[P.S. - I hope this isnt a very obvious fact that i missed
Click to expand...
Click to collapse
generally all scripts work for both odexed and deodexed.....
but the smurfed out is for any rom...odexed or deodexed...
the second script is for deodexed only ...as the script is to handle the system apps control..u can enable or disable further system apps by editing the script using root explorer like file manager
It seems to be a very good script.Hope the developer continue to update it. I have installed the script on TranX rom but need to make a clean install to see the results. Will post later.
Edit: Having problems with wifi and 3g. They don´t turn on.Wifi goes on and off.
gengi said:
It seems to be a very good script.Hope the developer continue to update it. I have installed the script on TranX rom but need to make a clean install to see the results. Will post later.
Edit: Having problems with wifi and 3g. They don´t turn on.Wifi goes on and off.
Click to expand...
Click to collapse
i also think y aint the script is unknown till now....
Related
Sorry for posting this here but I am a junior members and I can't post in dev. I already flashed speedy, how do I flash road runner? Do I need to delete all speedy files first or just flash over top?
Id also like to know
Sent from my DROID X2
neckbonest said:
Sorry for posting this here but I am a junior members and I can't post in dev. I already flashed speedy, how do I flash road runner? Do I need to delete all speedy files first or just flash over top?
Click to expand...
Click to collapse
1. Go here and download 0vermind's init.d re-hack
2. Flash the init.d re-hack in BSR (Bootstrap Recovery)
3. Flash Speedy v2 (Road Runner)
4. Reboot twice
To make sure the scripts are working go to /data and check for "ZipAlign log" if you see it, the scripts are working.
Don't be sorry. This section is for general which includes Q&A
Does anyone know if these scripts will work with the atrix ports?
I am a noob and didn't want to start a new thread that would clutter up so this seemed like the best place to ask.
They should work on atrix port but in theory you don't need to flash the init.d hack its already built into atrix port.
rkuhldude77 said:
Does anyone know if these scripts will work with the atrix ports?
I am a noob and didn't want to start a new thread that would clutter up so this seemed like the best place to ask.
Click to expand...
Click to collapse
Yes the scripts are working GREAT with the Atrix port
I install this morning and my phone is working outstanding
7 hours and my phone is still at 80%
the min CPU freq is set @ 250 up from 216
another question...so now that naven updated his scripts do i even need this? Or would it be smart to install this over navens latest release?
rkuhldude77 said:
another question...so now that naven updated his scripts do i even need this? Or would it be smart to install this over navens latest release?
Click to expand...
Click to collapse
It depends which scripts u prefer. They are different in some ways...and u may need to delete parts of conflicting scripts or entire script itself. I saw some people had problems when trying to do that. Just make ur nandroid before trying to be safe.
U could just push the scripts into init.d folder u want to use and fix permission/owners.
So the scripts from these two guys are named differently, does navens have the script that helps battery or can I just add that specific one from overmind into navens zip file?
If so what is the name of the script?
Sorry again I am a noob and am just trying to figure this stuff out
I wanted to say thanks for your interesting work on RoadRunner. I've flashed it, along with the hack, and it wasen't loading as I wasen't seeing Zipalign. log. but realized maybe I should reload busyox, hch I did. Then upon reflashing roadrunner, the zipalign.log appeared. Al started speeding up after this as well as increasing battery life. So thanks again
Steve
Just a quick question about system tuner tweaks. Is it better to have them applied after booting or via init.d script(assuming your rom supports it)?
ElAguila said:
Just a quick question about system tuner tweaks. Is it better to have them applied after booting or via init.d script(assuming your rom supports it)?
Click to expand...
Click to collapse
I'd use the app....g
gregsarg said:
I'd use the app....g
Click to expand...
Click to collapse
its an option in the app...
You can have them applied with initd or after the boot sequence has completed...
I myself use initd
Init.d support is available in only a limited amount of kernel use.
My reply was an attempt to prevent confusion among users that don't have init.d kernel support.
And honestly, many don't even know what it is. Especially those with stock devices.
And if init.d support is toggled on without supported kernels, it often FC's...or. worse ....see threads on stock rooted att note.
I should have been more specific, and said,
Use the " on boot completed " setting in the app ..it works the same and won't give you migraine headaches later ..sorry ....g
Guys, I own an Xperia U. I've updated it to ICS build number 6.1.1.C.1.0 via flashtools. After using for few days, I applied v6 supercharger script as I didn't feel this rom snappy. It worked fine but now after 2 weeks it's causing errors. Errors are like Windows' "Not responding" plz wait. Also, my battery backup dropped. Are there any favorable settings for xperia u?
Same problm
I also had a window popping every 10sec indicating I had a minfree
Values mismatch
V6 supercharger
Why dun u rerun the script and select moderate settings
Which setting r u using?? Aggressive???
drsanket_xperia_u said:
Same problm
I also had a window popping every 10sec indicating I had a minfree
Values mismatch
V6 supercharger
Why dun u rerun the script and select moderate settings
Which setting r u using?? Aggressive???
Click to expand...
Click to collapse
I tried all three 512 settings but no luck. Whenever I open fb, I get error. I even tried the superchager calculator settings, which are actually a bit non-annoying than above three but after few time phone becomes slower.
I have also applied Pimp my rom tweaks but not the minfree values. Only I/O scheduler tweaks and three sleepers in kernel section.
Do you think that has anything to do with this freezing errors?
Vtrendzzy said:
I tried all three 512 settings but no luck. Whenever I open fb, I get error. I even tried the superchager calculator settings, which are actually a bit non-annoying than above three but after few time phone becomes slower.
I have also applied Pimp my rom tweaks but not the minfree values. Only I/O scheduler tweaks and three sleepers in kernel section.
Do you think that has anything to do with this freezing errors?
Click to expand...
Click to collapse
Did you patch the services.jar ? V6 worked fine for me but when I patched services, I got loads of FCs, huge lag and rom became nearly unusable
Let me know Cheers
Min3r said:
Did you patch the services.jar ? V6 worked fine for me but when I patched services, I got loads of FCs, huge lag and rom became nearly unusable
Let me know Cheers
Click to expand...
Click to collapse
Services.jar were patched automatically during installation for me via internet....
So it means we need not patch it??
I suggest you avoid it.. Just use Supercharger's mem tweaks without the Services.. But it might just have been an off case with me though.. Not sure
Min3r said:
Did you patch the services.jar ? V6 worked fine for me but when I patched services, I got loads of FCs, huge lag and rom became nearly unusable
Let me know Cheers
Click to expand...
Click to collapse
I did patch services.jar
So you mean I shouldn't have done that? Also, when I used its earlier version i.e. V8 script, I didn't even bother to patch services.jar. Coz I didn't know about it, seriously. The new script tells you whether you've patched services.jar or not. V8 script never gave me errors instead it did its convincing job very well.
I'll try v8 script again when I re-flash my stock rom 6.1.1.C.1.0 which is pretty snappy but still I have to find out whether zepplinrox's script works for 512mb ram devices or is it just hokum.
Don't use the V8 script.
Just use the latest V6 http://goo.gl/1JPl8
For ICS and up, use the latest Ultimatic patcher http://goo.gl/IvGL1
If your ROM is pre-ICS you don't need any patch for supercharging - but you can use the patcher for mulititasking mods
zeppelinrox said:
Don't use the V8 script.
Just use the latest V6 http://goo.gl/1JPl8
For ICS and up, use the latest Ultimatic patcher http://goo.gl/IvGL1
If your ROM is pre-ICS you don't need any patch for supercharging - but you can use the patcher for mulititasking mods
Click to expand...
Click to collapse
First of all, thanks for your reply.
As I said earlier, I'd re-flash my stock rom, so I did it. It pretty fast now. I applied the script without patching anything. It's working like a charm. With pimp my rom, I only applied the sleepers mod.
So my conclusion is to flash the 6.1.1.C.1.0 rom again if you guys are having problems. And apply only these settings. For more brief answers, you can ask me
Also battery is pretty darn amazing. Even though I changed my systemUI,apk, there's no change in its performance.
I figured I would convert this mod to our device using code in the unified thread. (Props to original author and Rompnit).
It took a bit of tweaking to get it to work on the Sprint variant but it seems to be functioning as intended.
This is for Odexed stock(ish) roms only!
It replaces services.jar and build.prop. If you have tweaks to your build prop that you don't want set to defaults then I recommend you install the jar and odex file manually and edit your build.prop with whatever tool you see fit
A lot of mods affect the services.jar as well, noteably the unlock hotspot mod. That's why it's included FREE with this mod.
What a deal!
The changes I made to the build.prop are simply these additions. The rest is stock
#CRT Mod
persist.sys.screen_on=fade
persist.sys.screen_off=crt
These can be changed to set your on/off animation type. Options are CRT/FADE/NONE
Standard Use at Your Own Risk stuff Blah Blah
Enjoy
It's usually better to provide a deodexed copy as odexed relies on the same exact framework that it was odexed with to be present for the files to function at all
On the other hand, deodexed will function on any rom including odexed roms (when yup delete/move the odex files affected)
CNexus said:
It's usually better to provide a deodexed copy as odexed relies on the same exact framework that it was odexed with to be present for the files to function at all
On the other hand, deodexed will function on any rom including odexed roms (when yup delete/move the odex files affected)
Click to expand...
Click to collapse
I provide Odexed mods mainly because nobody else is doing it. And because odexed versions are usually the first thing people ask for, and because deodexing seems to break too many functions I use like private mode and S-Health issues.
I'll post the edited smali if anyone wants to use it for anything.
townsenk said:
I provide Odexed mods mainly because nobody else is doing it. And because odexed versions are usually the first thing people ask for, and because deodexing seems to break too many functions I use like private mode and S-Health issues.
I'll post the edited smali if anyone wants to use it for anything.
Click to expand...
Click to collapse
I wasn't criticizing, merely commenting
CNexus said:
I wasn't criticizing, merely commenting
Click to expand...
Click to collapse
np, It's all good.
Return to Stock
How can I go back to stock? remove the CRT animation and changes you made to Services
ramik911 said:
How can I go back to stock? remove the CRT animation and changes you made to Services
Click to expand...
Click to collapse
Replace the services.jar and services.odex with a stock version and remove the added entry in build.prop
thnx
Is this only for root devices? Are there any CRT mods for none roots? I did a search and so far this is the only thread with CRT.
dwss said:
Is this only for root devices? Are there any CRT mods for none roots? I did a search and so far this is the only thread with CRT.
Click to expand...
Click to collapse
You would need root access to flash the completed product to your device.
What would it take to port the crt mod to moar 7 rom.i had it on stock rom with xposed. I want to get it back without xposed.
Introduction:
Hello everyone!
The idea to this 'project' did blossom after having an conversation with @pkgnex in the past about the general idea of creating something else that follows what he started with his PK's Tuning Script for Pixel 2 (XL) but with a twist, mainly as a complement to his own thread that you can find here, but also with a completely different vision and focus on what the script itself should achieve (and deliver) for kind of results for myself and for all of you personally, of course, that wants to try it out and use it as a "daily driver".
Shortly explained.
This script is created with the goal of improving both battery life and performance on our Pixel 3 (XL) devices, and after a whole range of configurations and various set-ups, I've come up with something that, in my eyes, is worth sharing with all of you so that you can try it out yourself and judge on your own, with constructive feedback on what can be improved or added in future releases - if desired. My philosophy is, and will always be, this:
If something can be improved or altered in a positive way so the average user can feel and see a difference, then go for it. Non stop.
The latest release can be found here.
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Note: This script is not recommended to be modified or customized by the user.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Enabled, and fully configured, Boeffla generic kernel wakelock blocker
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
CPUSet improvements & optimizations
Schedtune tweaks (Improves responsivness)
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements/what you need for getting this script fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest possible version of Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation/How-To use & abuse:
1) Download the attached ZIP
2) Extract the script
3) Move the script to the following location;
/data/adb/service.d and give it the following & needed file permissions (0755)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Note: If you still are unsure how to do for making my kernel configuration / modification work & be up and running behind the scenes, then please read @Phalanx7621 phenomenal guide here or check out @Phalanx7621in-depth video here. The installation method is the same for all generations of released Pixels!
Credits:
@franciscofranco for all the information on which kernel wakelocks that is safe to block
@Phalanx7621 for his phenomenal how-to guide
@Lord Boeffla for his awesome generic kernel wakelock blocker
@pkgnex for inspiring me walking into this partially unknown territory.
@flar2 for his excellent EXKM application and ElementalX Kernel
@osm0sisfor his Magisk Busybox module
Everyone that I've forgotten to mention here
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2019-01-07
Last updated: 2019-01-07
Update!
Note: Don't forget make a folder named "logs" at the root of your internal storage before applying version 1.0.
Version 1.0 (Initial release):
- Initial release!
- Copied over a huge amount of various enhancements from BlackenedMod for Wahoo (Pixel 2 / Pixel 2 XL) + tuned a couple "crucial" Pixel 3 (XL) specific easter eggs
- Blocked a few safe-to-fully-purge kernel wakelocks for slightly improved battery life during idle / deep sleep
- Fully enabled and adjusted all of the Schedutil hispeed based / specific tunables for both of the clusters with the intention of keeping the phone both smooth and snappy while maximizing overall battery life as far as possible
- Included, but commented out, so you can enable power efficient workqueues on-the-fly directly within the script
- Some very additional minor & miscellaneous enhancements and adjustments both here and there
Enjoy!
Magisk manager app keeps stopping while checking for updates after installing script. Is this expected?
Edit, after a reboot magisk is back to normal. I'll keep an eye on this to see if I can repeat it and maybe capture a logcat.
Sent from my [device_name] using XDA-Developers Legacy app
Very interesting! Thanks for the effort! As I consider myself a modding-greenhorn, I'm waiting for the experiences other users have with that Mod!
cheers
georgs_town said:
Very interesting! Thanks for the effort! As I consider myself a modding-greenhorn, I'm waiting for the experiences other users have with that Mod!
cheers
Click to expand...
Click to collapse
Do you have any first impressions so far to share?
*Cheers*
Rommco05 said:
Blackenedmod is heavymetal magic. Pure awesomeness, I run this mod on Mi8 and my breath time to time stop. I don't feel any performance degreasing (maybe opposite) but huge improvement in battery life. Thanks!
(I removed some lines which aren't suitable for Mi8)
Click to expand...
Click to collapse
Which specific lines did you remove?
Testing currently on my op6t.
jacksummers said:
Testing currently on my op6t.
Click to expand...
Click to collapse
Enjoy!
:highfive:
xFirefly93 said:
Enjoy!
:highfive:
Click to expand...
Click to collapse
Loving it.. u should release it everywhere....
Thanks man!
This is the OnePlus 6t T-Mobile version coverted to international version..
Can you use this with the stock kernel or does it need to be with a custom kernel? I'm currently unlocked and rooted with Magisk but running stock otherwise. Thanks
What files should be in the logs folder? I made the logs folder but it's disappeared on reboot so I don't know if working or not?
cooltech786 said:
Can you use this with the stock kernel or does it need to be with a custom kernel? I'm currently unlocked and rooted with Magisk but running stock otherwise. Thanks
Click to expand...
Click to collapse
Should work with stock.
acidspider said:
What files should be in the logs folder? I made the logs folder but it's disappeared on reboot so I don't know if working or not?
Click to expand...
Click to collapse
A automatically generated output log file which tells you if the script is working or not.
A little, but important, update will be released at the end of this week once I am off from work. Perhaps at Saturday if everything is going as planned!
Just wait.
How have the initial release btw performed so far for everyone? :highfive:
xFirefly93 said:
Should work with stock.
A automatically generated output log file which tells you if the script is working or not.
Click to expand...
Click to collapse
Any of these? Dates are not right, phone wasn't even released then. ???
acidspider said:
What files should be in the logs folder? I made the logs folder but it's disappeared on reboot so I don't know if working or not?
Click to expand...
Click to collapse
I saw someone post on here to create the log folder on root and of course it doesn't survive a reboot. I read thru his script and had a duh moment. You need to create the logs folder at the root of the sdcard, /storage/emulated/0.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
I saw someone post on here to create the log folder on root and of course it doesn't survive a reboot. I read thru his script and had a duh moment. You need to create the logs folder at the root of the sdcard, /storage/emulated/0.
Click to expand...
Click to collapse
That's better. ???
Have been using it for the past few days. Definitely notice better battery life through the blocking of wakelocks. Haven't noticed any difference in performance so seems to be worth running. No issues with stability at all either. Great work!
Can this be run along side naptime ? Also layman question: is this similar to naptime?
Edit: Ok I tried it on Pixel 3 with Elemental X kernal and I'm stuck on the white boot screen with google logo...Any idea ?
I had your script running along side Magisk v18 Stable on Bootleggers Ver. 4 and noticed Viper4Android wouldn't load correctly. It was showing in the Magisk logs but not showing in my app drawer. Per the link below I noticed the last think to load was your script so I deleted it and rebooted. Viper then worked and I was able to reproduce the issue by adding back the script and once again fix it by deleting the script. I really love your script and would like to use it but, Viper is a must for me. Are there any lines in the script that could be deleted or altered for Viper4Android to load correctly via Magisk?
https://www.google.com/amp/s/forum....module-viper4android-fx-2-5-0-5-t3577058/amp/
jon2jay said:
Just an update. Script is great im getting approximately 6 and change hours of SOT.
AOD off.
Location on.
WiFi always on.
kirisakura kernel
Exkm installed (no real tweaks made no idea where to start)
Also in response to previous post, viper working fine for me w/ script, root and this init script.
Click to expand...
Click to collapse
Are you running the factory image? It might be related to me running Bootlegger v4.
jon2jay said:
Just an update. Script is great im getting approximately 6 and change hours of SOT.
AOD off.
Location on.
WiFi always on.
kirisakura kernel
Exkm installed (no real tweaks made no idea where to start)
Also in response to previous post, viper working fine for me w/ script, root and this init script.
Click to expand...
Click to collapse
A update will come when I feel that I've found something that is worth sharing