On certain boot settings such as CPU overclocking is it better to use on boot completed setting or the init.d script? Kinda confused on what the init.d script is any help would be nice..
Using ziggys new kernel and running androtech 3d rc2..
Sent from my Nocturnal 3D using XDA App
Say what?
And using system tuner pro if you overclock and don't use the set on boot option this will revert the settings to whatever they were from the kernal you flashed if you reboot your phone, however if you use the set on boot option then it will set the CPU to your settings when you boot up,
I believe when you check the force all cpus online is when system tuner adds a file to int.d folder to enable the second core,
From my understanding the stuff in int.d folder can be deleted without problems if you know what your doing.
I currently run my CPU at
1.18ghz max.
.3 ghz min.
With out the second core on, and set on boot is checked, I don't use the boot script or the faster app booting options,
Why fix something that ain't broke, it works great.
Shot from my shooter in 3D
injected with cleanrom2.7
elimon91 said:
On certain boot settings such as CPU overclocking is it better to use on boot completed setting or the init.d script? Kinda confused on what the init.d script is any help would be nice..
Using ziggys new kernel and running androtech 3d rc2..
Sent from my Nocturnal 3D using XDA App
Click to expand...
Click to collapse
technical details:
on boot completed is essentially a java function. the android system, after boot has been completed sends a system wide broadcast and any java application which has registered to listen for this broadcast can take action once the broadcast is given. this broadcast is probably the very last step in the complete system booting process.
the init.d script is done more at the linux level. it is usually called and trigger by the init.rc file. essentially, init.d is trigger during the hand off from ramdisk of the kernel to the android operating system.
init.d will technically execute before boot completed signal is sent so it will run first of the two methods.
boot completed will continue to work as long as the java application is installed
init.d will continue to work as long as the kernel supports it and the specific file is present under the init.d directory.
hope that helps!
joeykrim said:
technical details:
on boot completed is essentially a java function. the android system, after boot has been completed sends a system wide broadcast and any java application which has registered to listen for this broadcast can take action once the broadcast is given. this broadcast is probably the very last step in the complete system booting process.
the init.d script is done more at the linux level. it is usually called and trigger by the init.rc file. essentially, init.d is trigger during the hand off from ramdisk of the kernel to the android operating system.
init.d will technically execute before boot completed signal is sent so it will run first of the two methods.
boot completed will continue to work as long as the java application is installed
init.d will continue to work as long as the kernel supports it and the specific file is present under the init.d directory.
hope that helps!
Click to expand...
Click to collapse
Thanks for very usefull information, I use init.d
Related
Ok I'm working on a custom rom and writing some scripts for it to tweak things and automate a few functions. I was messing around today with the android scripting engines for python and java just to see what it was capable of and it basically allows you to write java and py scripts that allow interaction with the android api.
I was wondering; would it be easier to implement the script engines into my rom I'm working on now to create a sort of frontend for my shell scripts adding the usage of api functions like reading sensors, displaying alert pop ups etc.. or just code up an app to act as a script frontend and incorporate it into the rom.
Personally I really like the idea of being able to write scripts directly on the device that can do pretty much anything most apps can do but for the sake of ease of debugging and the end user of the rom it may be better to go with an app to do everything instead.
Any feedback is appreciated.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
The first one. It's better to implement the script engines into your rom. This would allow the scripts to always boot with your rom making it faster and optimized (etc. depending on what scripts you included). Doing this via an app will give the user a choice to use it (and even remove it). If they are necessary, then the rom won't work too well after that. You could also make some tweaks to the build.prop and init.d (if you are including that in your rom) to make the rom even better.
Theonew said:
The first one. It's better to implement the script engines into your rom. This would allow the scripts to always boot with your rom making it faster and optimized (etc. depending on what scripts you included). Doing this via an app will give the user a choice to use it (and even remove it). If they are necessary, then the won't work too well after that. You could also make some tweaks to the build.prop and init.d (if you are including that in your rom) to make the rom even better.
Click to expand...
Click to collapse
I do have init.d incorporated into the rom and am making use of it and have tweaked build.prop quite thoroughly. I've also been tweaking the kernel for the rom. Everything you said though is the same thing that had me leaning towards this option. It would add tons of functionality to my scripts and it'd be very easy to make changes to whatever I need to.
I've also been thinking more about the debugging part and I also believe this would be much easier as every part would be seperate from the main function. So if there were any problems you'd only have to run through the offending scripts code or the call coming from the "main" script instead of an entire program.
Sent from my i897 w/Andromeda 3, Suckerpunch kernel, & 1.3Ghz OC using Tegrak.
Sorry for the incredibly newbish question. (Feel free to refer me to other places this may have been answered.)
There seem to be a lot of "Speedy"/Performance scripts listed in the Sticky on the X2 Dev forum, and I was just wondering if someone would be kind enough to provide a line or two to describe each.
It seems to me like there is a lot of overlap between some of these scripts, especially when considering the tweaks added by various ROMs. So I am most interested in finding out basically which are compatible, and which are most likely to conflict with the available custom ROMs.
Here are a couple, but feel free to add more.
Speedy V6
Init.d Re-hack (required for some scripts)
Init.d Hack v0.6 (required for some scripts)
Speedy Gonzales v1.0 (thread closed)
Power Boost v2.0
-=V6 SuperCharger=-
SetCPU (an app that may/may not work in conjunction with some of the above scripts)
Again, sorry for my nativity here. I know this information can be found in the individual threads, but I'm sure a basic overview would be a really big help for those of us who are just now trying to get into the installation of some good speed scripts. It's also really unclear to a beginner which scripts/apps/ROMs will conflict with each other or which combinations might actually reduce effectiveness & stability.
Thanks!
ya i agree...too many of these overlap with each other.....which work with what kernal???....which works the best....benefits of each??....etc....
init.d hack is a way to allow you to store scripts in a directory called /etc/init.d that will fire up when the phone reboots. Without it, you could create the directory but your phone won't run the scripts.
It's best to flash the init.d hack first which "hijacks" the boot process and will execute any scripts located in the /etc/init.d directory.
Once that is flashed, I find the V6 Supercharger Scripts to be the best for making the phone speedy. I use options 9 and 12. 9 sets the optimal memory settings that seem to prevent music from skipping. Option 12 makes the launcher not get killed in memory which can cause skipping and hi cupping in the X2 as it unloads and reloads from what I understand.
I really haven't used anything else except the V6 Supercharger Scripts. They seem to be the most popular, but what it all boils down to is, experiment with each one and see which gives you the best performance you are seeking.
I also know many ROMS, such as Eclipse, have incorporated the init.d hack and have their own versions of many of these performance scripts in them, so mileage will vary.
Also, the kernel doesn't mean anything. It works with all kernels. But, many of them require Busybox installed since they use various UNIX commands that are not available in the stock image.
question: can't you just save the 99 v6 script as run as root, run at boot after you create the init.d directory instead of having to run the init.d hack? i've never run the init.d hack but have used the run as root run at boot save and it always loads fine on boots.
I really hope I posted this in the right place...
I loaded Eclipse v1.3 yesterday on 2.3.4 and I love it! It works really well. I had the issue about the gps but it went away after 2 battery pulls. I don't have any problems with iheartradio skipping or any other music for that matter. I have even noticed my X2 runs way faster. But, my internet is slower. No matter downloading or browsing, I can tell it is slower than before. Since Eclipse has the init.d already inside, can I download the Speedy V6 zip and flash it when I go into recovery mode? From what I have read in the forum, that should increase the overall speed of the phone. Or, being a noob, am I going about that the wrong way?
---------- Post added at 01:58 PM ---------- Previous post was at 01:37 PM ----------
tallyforeman said:
I really hope I posted this in the right place...
I loaded Eclipse v1.3 yesterday on 2.3.4 and I love it! It works really well. I had the issue about the gps but it went away after 2 battery pulls. I don't have any problems with iheartradio skipping or any other music for that matter. I have even noticed my X2 runs way faster. But, my internet is slower. No matter downloading or browsing, I can tell it is slower than before. Since Eclipse has the init.d already inside, can I download the Speedy V6 zip and flash it when I go into recovery mode? From what I have read in the forum, that should increase the overall speed of the phone. Or, being a noob, am I going about that the wrong way?
Click to expand...
Click to collapse
I'd also like to note: On my CPU tuner app, it always says the Active CPU's are 1/2 and does not pass the test under the "check capabilities" portion of the app. I also had the same result before rooting and loading Eclipse. Will the new script cure that?
h_10 said:
question: can't you just save the 99 v6 script as run as root, run at boot after you create the init.d directory instead of having to run the init.d hack? i've never run the init.d hack but have used the run as root run at boot save and it always loads fine on boots.
Click to expand...
Click to collapse
The main reason for the init.d hack is so u don't NEED script manager to run init.d scripts at boot. One less thing for ur phone to have to start up. One less application running on startup.
What I used to do(when not running a rom w/init.d support...eclipse HAS init.d hack built in along w/liberty (others too I believe)
Is I would flash the hack. Delete all init.d scripts and just run supercharger scripts from there.
that way there was no need to run the supercharger scripts at boot etc...
Upgraded to a Galaxy Note from an HTC Desire Z and though I would share something that isnt very popular with the Galaxy ROM's and hasnt been mentioned here.
It seems that most of the customs roms have overclocking enabled. Most people who do overclock use SetCPU to customize frequencies and perhaps go further with screen off profiles to save battery especially with such a big screen.
There is a better way. A XDA dev, RMK, developed a tiny daemon to run in the background taking way less resources than SetCPU and is many times faster because it is a native daemon without the need for the Android JAVA VM overhead.
However, the initial utility was made for the Desire Z, a single core CPU. Another dev, has made "andrev_oc" with an installer and a program to set the profile for the daemon.
http://forum.xda-developers.com/showthread.php?t=1222020
I have tried this on SAUROM and it works. Here are the steps I used to install:
1) Downloaded the installer APK, this is by far the easiest way. It will install the config, the binary and the auto startup script in init.d
2) Used terminal emulator or ADB to input a special mount because the mount binary does not take the command issued by the installer properly.
Code:
mount -o remount,rw /system /system
3) Installed andrev_oc with the installer APK
4) Install Daemon Controller. Daemon Controller edits the clocking profile and the governor. I found that with SAUROM. Most versions of the program either FC's or fails to detect the daemon. The only version that I found worked was version 2.11.
http://androidrevolution.nl/Sybregunne/DaemonController-2.11.apk
Hope this helps people with battery gripes.
All this was done with busybox 19.4.0, I dont know if this will affect any of the steps here.
Lemme note here, I deserve no credit, all code and all work was done by Eugene_373 and anyone mentioned below, this is simply a share from the T-MOBILE GALAXY s2 section of XDA, I have fully tested this app and found it to be working wonderfully on my SGH-I777
I love eugene's deving hence the share I hope you all enjoy if this has some way helped you in anyway go over to eugene's profile donate/thank him
App Version:
CPU Sleeper
~Free to all XDA Memebers
~ Must Be Rooted to use App
What is it?
Its a fairly simple App that will put CPU 1/2/3 OFFLINE when the screen turns off. Once the screen comes back on, it will allow CPU 1/2/3 back ONLINE.
How does it work?
Since we have Dual & Quad core CPUs, we have a CPU 0 and a CPU 1/2/3, core 0/1/2/3, while the screen is off we really only need to have 1 core active "CPU0", this App will make sure CPU 1/2/3 shuts off while the screen is off, then resumes normal usage when the screen comes back on.
Compatibility?
Works with any Dual Core & Quad Core Devices!
~ICS
~Gingerbread
Battery Saving?
Battery savings all depends on Usage & idle times.
App Download: CPUSleep.apk
Version 1.5 Release Notes:
~ Battery Drain issues 100% Fixed
~ Screen on Lag 100% Fixed
~ SU issues 100% fixed
~ Auto-Start on reboot 100% Fixed
~ Fixed Auto-Start killing Cell Service
~ Su Request on Screen Wake Fixed
~ Debugging enabled for those wanting to check if it's working.
Credits:
Handlerexploit for co-creation of this wonderful App.
Script Version!
Code:
This time I present to you a script that will in theory (and so far for me, in reality) save us some battery without having to risk our hardware with undervolting! I present to you...
[B]CPU Sleeper[/B]
[U]What is it?[/U]
Its a fairly simple script that will put CPU 1 OFFLINE when the screen turns off. Once the screen comes back on, it will allow CPU 1 back ONLINE.
[U]How does it work?[/U]
Since we have dual core CPUs, we have a CPU 0 and a CPU 1, core 1 and core 2, while the screen is off we really only need to have 1 core active, this script will make sure CPU 1 shuts off while the screen is off, then resumes normal usage when the screen comes back on.
[B][COLOR="red"]WARNING! READ THIS![/COLOR][/B]
This script relies on init.d OR script manager! CM9, for some reason, tends to run this at the exact same time it runs some other script (I forget atm which) and it will clash, causing no boot! CM9 users MUST use the script manager version install! Flex Reaper appears to work fine with it as init.d. I strongly urge you to use the script manager version of this, NOT the flashable version. Always make a nandroid backup before modifying the system, including this!
[U][COLOR="Red"]Instructions[/COLOR][/U]
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
[I]Version 1: Flashable[/I]
Same as any of my flashable releases, I did most of the work for you!
Make a full backup
Download to external SD card
Install from SD card
Pick the cpu sleeper zip file
it'll be almost instant
reboot
Shouldn't be any need to clear caches or anything like that.
[I]Version 2: Script only[/I]
This can be run in 2 ways, via init.d support, or via script manager. Both are pretty similar, and can be done a number of ways, however this is the basis of how.
[U]Init.d supported kernel:[/U]
Make a backup!
Download the script file, making sure no extensions get added onto the file. Copy the file to /system/etc/init.d and set the permissions to the following:
XOX
XOX
XOX
Once done, reboot the system, and it will take effect when your system is finished rebooting.
[U]Script Manager[/U]
This method is probably the better method, and should work with any kernel/ROM. Download the script file, making sure no file extensions get added, and copy it to /system/etc. Set the file permissions to:
XOX
XOX
XOX
Once done, load up script manager, select browse as root (if it isn't already set from the crossix mod method in the guide) then browse to /system/etc and select the script file S98cpu_sleep, then select ROOT and BOOT options. After this is set, reboot system.
[U]What do I do if I can't boot after using this?[/U]
You made that backup, right? Ok, then here is what you do.
Hold the power button until the tablet powers off
Press and hold the volume down button, next to the screen lock switch
Press and hold Power (while holding volume down)
Once the recover kernel message comes up, release the buttons
In CWM go to advanced, mounts, mount system, then format system
In TWRP, go to wipe, then wipe system
In CWM go to restore, advanced restore, restore ONLY system
In TWRP select restore, then uncheck all so ONLY system is checked
After restoring system, wipe cache and dalvik cache, then reboot system.
System should boot normally.
[B]Downloads[/B]
Available in 2 versions, script only version which you can place wherever you want and run however you want, or a CWM/TWRP flashable zip that will place the file for you in /system/etc/init.d and set permissions.
Dual Core:
Download: [COLOR="Red"]Script Only - Recommend Install via Script Manager App[/COLOR]
[URL="http://d-h.st/N1N"]CPU Sleeper script only[/URL]
Quad Core:
Download: [COLOR="Red"]Script Only - Recommend Install via Script Manager App[/COLOR]
[url=http://www66.zippyshare.com/v/9249467/file.html]cpusleep[/url]
[COLOR="Red"]Download: ClockworkMod Recovery .zip for T989 / I727[/COLOR]
[url=http://www19.zippyshare.com/v/51836824/file.html]CPU_Sleeper.zip[/url]
Thanks to [COLOR="DarkGreen"]pio_masaki[/COLOR] for rewriting the OP
Used this for a day now. Seems to work. Will test some more. Using the app by the way.
Ported VK w/ bad ass Jkay.
Siyah synthetics and K-tuned for maximum performance.
hotplug, sched_mc
I'm running aokp + fluxxi also..is this app any different from hotplug settings or SCHED_MC level settings in xxTweaker?
Krysten17 said:
I'm running aokp + fluxxi also..is this app any different from hotplug settings or SCHED_MC level settings in xxTweaker?
Click to expand...
Click to collapse
Hotplugging and sched_mc are kind of synonymous. The difference is that sched_mc allows you to force a particular pattern of behavior (1 = fill 1 core first, 2 = activate both). This app attempts to force 1 core offline when the screen is off. It's kind of like an extreme version of sched_mc = 1 in that it doesn't allow both cores to be activated. However, I'm not sure if it is capable of preventing the second core from coming online. It may check periodically and subsequently turn it off. I don't think it would have much benefit on our devices; our hotplugging is competent and sufficient. I suppose anything is worth trying though.
looks interesting!
Every now and then i get cpusleep has been granted superuser permissions when the screen is on and im surfing the net or playing a game.
Ported VK w/ bad ass Jkay.
Siyah synthetics and K-tuned for maximum performance.
stevehkim said:
Every now and then i get cpusleep has been granted superuser permissions when the screen is on and im surfing the net or playing a game.
Ported VK w/ bad ass Jkay.
Siyah synthetics and K-tuned for maximum performance.
Click to expand...
Click to collapse
Oh I forgot to update the APK link its been updated download and install the latest version
Sent from my SGH-I777 using Tapatalk 2
Here's the original thread created by the app dev if anyone was wondering:
http://forum.xda-developers.com/showthread.php?t=1745132
Tried it for almost 3 days. Didnt help. No noticeable gains so I uninstalled
just uninstalled it too after seeing no real gain for two days.
Sent from my SGH-I777 using xda app-developers app
Thanks for all who posted. I'm running xxtweaker fluxii aokp . Any advice other than what's listed here for hot plug settings. Thanks
Sent from my SGH-I777 using xda premium
Does it work fine with setcpu ?
I know there are a couple posts out there on how to fix this, but this is one of the most legitimate ways to fix the multitasking issue we have all come to know and hate on Android devices running Sense. If you don't want to install a whole new ROM, such as MEANROM, you don't have to! This is a small guide to using the V6 SuperCharger script by Zeppelinrox. I know the amount of steps seems like a lot, but it's really not that many. Most of the steps will be followed by just reading what you see on the screen and accepting the recommended option!
Zeppelinrox said:
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
The problem with using minfree tweakers like AMM or AKMO is that it doesn't work the same on all roms.
Secondary apps may be in slot 3 on some roms but in slot 5 in others!
That's why you hear people comment "I tried AKMO but it didn't do anything..."
Most likely it didn't do anything because the apps weren't sitting where they were expected to be.
So fasten your seat belts and enjoy the ride!
Click to expand...
Click to collapse
So, everything you need to know or want to know can be found at Zep's original thread here. There is a lot of information, and because he is so technical, I think that sometimes his instructions can be hard to read for some, so I thought I would put together a VERY SIMPLE GUIDE to give you guys a hand. You can find the best instructions from him under Installing/Using.
http://forum.xda-developers.com/showthread.php?t=991276
On to the instructions...
How To Use Supercharger
Please only proceed if you are rooted and have busybox
Download script manager from the market: https://play.google.com/store/apps/details?id=os.tools.scriptmanager&hl=en
Download zep's latest V6 Script (V6_SuperCharger_for_Android-Update9_RC11_Test_6.sh.pdf): http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
remove the .pdf extension (should now end in .sh) and place on your phone /sdcard (you can use rom tool box or estrongs to rename the file)
At this point, I highly recommend you make a nandroid through TWRP or CWM. The script has a built-in undo feature, which works well, but I still think we all know this is best.
Open up Script manager on your phone. Make sure to check 'Browse as Root' Option
Navigate to the location wher you placed the V6 .sh script
Click the Skull/Crossbones to run as root. This should turn green. NOTE: DON'T USE THE BOOT OPTION
Hit Run
At this point, get ready for an onslaught of text. Don't be afraid and try your best to read even though much of it may not make sense!
You may be asked about your launcher. Answer the question correctly for your setup.
Any time you are asked to press Enter, go ahead and proceed. This is the last time I will tell you to hit Enter for most occasions.
Pick your scrolling speed. I recommend slow or normal the first time you do this, so you can keep up.
On the kernel panic screen, I recommend choosing the Rock(H)ard Option, so hit H and then enter
Accept the Misc and 3G tweaks by hitting Y
Feel free to keep or disable the annoying animation (the scrolling V6 at the beginning of the script)
Hit Y(es) for SuperMinFree Calculator settings. This is an automatic calculation. You can change this later when you get more confident. Many will choose the 1000HP option for our phone (based on available memory)
It will now backup your build.prop and some other system files.
ICS and newer Android services store a lot of the memory tweaks in services.jar. This script will now take you through an ICS patcher. Accept the Automatic Transmission. This will upload services.jar, and download the patched one.
It will eventually tell you that it needs to wipe your caches and restart. You will definitely want to do this. You will need to wait 4-5 minutes while it rebuilds your Dalvik Cache
Almost done! After your phone boots up and stabilizes, go back into Script Manager. Navigate to /data/99Supercharger script. Check the SU (skull/crossbones) and check the boot option.
Zepelinrox said:
- Stock ROMs - It also creates /data/99SuperCharger.sh which you can load up on boot (run as root) with Script Manager. The OOM groupings work as well since it happens on boot in local.prop or build.prop (18 entries added)
Click to expand...
Click to collapse
Reboot your phone and now your phone will run the supercharger script on startup. If you ever want to verify that your script is working, or if you want to mess with any of the extra options (including removal), run the original V6 shell script you downloaded as root, just like we did at the beginning. This will tell you if you are 100% optimized and give you a whole menu of options to play with!
I can actually open multiple apps now and go back to the first one without it having to reload. Waze is the best example. If I ever switched out and then back, it always had to reload...not anymore! Again, this all seems like a lot, but it's really pretty easy once you give it a shot!
Let me know if anything is unclear so that I can adjust this OP to help others.
Make sure to give Zep a 5 Star Rating in his OP and also give him thanks, he is the man!
Reserved just in case.
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
bog3nator said:
ok i need to correct you on one of your steps...DO NOT SELECT THE BOOT OPTION FOR THE SCRIPT. IT COULD CAUSE YOUR PHONE TO BOOT LOOP. only select run as root. it even tells you that on the guide that zeppelinx put in his thread.
edit: sorry for caps but i wanted to point this out before someone made this mistake
Click to expand...
Click to collapse
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
adma84 said:
You have to run /data/99Supercharger as root and give it boot option or it won't be applied at boot. But you are right, if you are worried, you could just run it as root the first few times. I personally always set this one to boot as well. If you had to, you could always adb in recovery, and remove /data/Supercharger if you are having problems.
*EDIT
This is mostly a concern for ROMS/Kernels that utilize /etc/init.d but I will add this caveat to the OP
Click to expand...
Click to collapse
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
bog3nator said:
if the rom uses init.d then the script will install a service to the init folder and it will auto load when then phone is restarted, no need to try and force it to run. also if it is a stock rom (with the script manager program) you can set the 99supercharger to run after boot as a task.
Click to expand...
Click to collapse
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
adma84 said:
What you are saying is exactly the point I made in the OP. Is this unclear? You should only ever run 99Supercharger on boot, not the original V6Supercharge Script. And yes, this is geared mostly towards stock users, who do not have init.d support and therefore need SManager to run the boot script for them.
Click to expand...
Click to collapse
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
bog3nator said:
i understand what you are saying but the boot symbol next to the run ass root symbol in the script should not be checked. if you need it to run at boot the script manager program can do that for you, by setting up a scheduler when you reboot. after boot it will run the script but not during
p.s. let me re-read what you put so i am just not looking stupid lol. i think i need a nap
edit: yea if you need it to run at boot do it through the script manager program and set it up to schedule it to load the script after your phone is already booted to avoid any potential boot loops (but dont check the boot logo at the top left hang corner of the actual script itself
Click to expand...
Click to collapse
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
adma84 said:
Can you post the steps to describe how you personally do boot scripts with SManager?
After Android starts up, it will send a boot intent to all apps registered to receive such an intent. This is where SManager is allowed to execute any scripts you have marked with the boot option. This happens much later than a traditional /etc/init.d start script, but is no less effective. Please let me know how you mark scripts as bootable and I can add that recommendation as well. Thanks.
Click to expand...
Click to collapse
1. open script manager
2. click menu
3. click more
4. click advanced options
5. click scheduler
6. click add new task
7. click select file
8. navigate to 99supercarger file the script created and click on it
9.you can from there click on boot (inside the file you just clicked on)
10. click save
it will boot the script after the phone is done booting, to prevent the possibility of boot looping. you can also create an event to do an engine flush however often you want (i do one at midnight everyday)
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
adma84 said:
This gets executed at the same time during system boot as the method I mentioned. Both are valid. Thanks for the feedback!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i thought you were saying click the boot thing during install ....i am sorry haha i got really tired all of a sudden and stuff wass getting jumbled together...
v6 works awesome though i have been using it for about 1 year now on this phone and my old evo
Also, for anyone that gives this a shot, please post back with your results!
Not to be "that guy" buuuut the effects of v6 at least from my experience with this phone (again fresh frombcustoms preorder release) the day i got it i was rooted and installed v6 because ive used it on all my prior evos since i found it probably right around when zep released lol...anyways on this phone its a strictly placebo effect and actually created more lag and launcher reloads...i was running the 1000hp option and tried the i believe 750hp whatever the one down from 1000 is anyways both of them gave me same results and once i removed the script all was good in the hood as they say lol...but if its working for yall then maybe zep fixed some ish for this problem and i didnt know about it...well this epic runon sentence is finished sorry for the length and useless points
Sent from the depths of hell
yea i also used it on my og evo and i just put it on last night again on this one, tried the 750 option and 1000 option. today at school my memory got so low it locked my phone, that never happened with mean rom and the tweaks he puts in. undoing the supercharge now.
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
adma84 said:
Sorry everyone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
no thanks man for helping out, i just think this phone doesnt do well with it, and that may be because of how HTC changed the multitasking settings themselves. it may conflict with v6
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
wileout said:
Theres something up with it because its def just this phone because nothing solves it at all
Sent from the depths of hell
Click to expand...
Click to collapse
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
bog3nator said:
I wonder if it's hard coded into sense somewhere
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Im thinking its sonething stupid like a character in the code is supposed to be one way and its mirrored the other way lol
Sent from the depths of hell
It's definitely helps with multitasking. I can keep apps open in the background much easier. Problem is that it chokes out the available ram for running apps, so it can make it feel sluggish. I think it's overtweaking the mem settings.