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...
Related
Attached Are The 3 Latest Updates For The 3GTurboCharger, V6 Supercharger, And 98KickassKernelTweaks.
General Instructions:
1. Place All Scripts On Root Of SD Card.
2. Rename The Scripts Removing .txt
3. You Must Create The "init.d" Folder Inside /system/etc Prior To Running The 98KickassKernelTweaks Script.
4. Use Script Manager To Load The Scripts.
5. All Scripts Need To Have "RUN AS ROOT" Checked First.
6. Then Select "RUN" And Follow The Instructions On The Screen.
7. Proceed To Next Set Of Instructions If Your Script(s) Warrant It.
Advanced Instructions For V6 Supercharger And 98KickassKernelTweaks:
1. Menu>More>Advanced Options>Config Check "BROWSE AS ROOT
2. /data 99Supercharger.sh Check Off Both "RUN AS ROOT And RUN AT BOOT"
3. /system/etc/init.d 98KickassKernel Check Off Both "RUN AS ROOT And RUN AT BOOT"
4. ***Possible Your Device Will Also Create 99Supercharger If The "init.d" Folder Exists.
More Info On It Go Here:
3GTurbocharger And KickassKernelTweaks
http://forum.xda-developers.com/showpost.php?p=15948434&postcount=1127
V6Supercharger:
http://forum.xda-developers.com/showthread.php?t=991276
As A Reminder This Was Created By Zeppelinrox And All Credit Goes To Him.
Files Are Now Attached For Easy Download.
I was under initial impression these werent needed after the GB update? I guess i was mistaken?
SuBDivisions said:
I was under initial impression these werent needed after the GB update? I guess i was mistaken?
Click to expand...
Click to collapse
This Post Doesn't Specify For Froyo Or Gingerbread Users. It's Up To The User, And I'm On Gingerbread And I Find All 3 Beneficial.
Now that we have the init.d hack will the kickasskernal with the IO tweaks work? Or should I just use the IO tweaks that come with navenedrob's script?
I Vote You Should Try It And See If It Works. Make A Backup First.
It boot looped...........
Do I have to sbf? Or could I just use the nandroid?
Throw The Phone Out Now. You Royally Messed Up. Geez Leave You Alone For One Minute And Look What You've Done. Nandroid Is Just Fine, No SBF Necessary.
WAAAAHHHHH no fair.... oh look it rebooted.....
So yea I am gonna try to use the IO tweaks from navenedrob's script as well as the cpu tweak from his script oh on top of the SD read ahead one. Those should work well with supercharger and kickasskernal I think. Those do not touch the cpu freq right?
I Don't Have Any Reason To Believe It Would.
Awesome, everything is working great.
My cpu is set to 1000 min and max. Sd read ahead is working but umm how do I know if the IO tweaks are working?
Sent from my DROID X2 using Tapatalk
Anyhow... now that I have my cpu at 1000 min/max I want to separate the cpu freq tweak and have different freq scripts for battery saving.
Sent from my DROID X2 using Tapatalk
How are these scripts running for X2 owners? Any major issues so far?
triton302 said:
How are these scripts running for X2 owners? Any major issues so far?
Click to expand...
Click to collapse
I Think They Work Fantastic, Personal Opinion. No Issues At All.
Mods like this one should also go to the Droid X2 Dev forum.
navenedrob said:
Mods like this one should also go to the Droid X2 Dev forum.
Click to expand...
Click to collapse
This Was Actually A Toss Up, Because Zep Started A Thread In The General.
i tried the scripts on p3 and it actually made it use marginally more ram and it was glitchy. i dont remember what numbers i used but i got them from this forum somewhere. either way when i tried to undo it i got a reboot loop so i sbfed and went back to p3. after looking into it some more ive read some places that you dont need this if you arent running froyo. any truth to this?
I Don't Think It's Been "Proven" But Rather A Preference. I'm Using All 3 On P3's Along With Various Other Tweaks I've Taken From Others. I Have 40 Running Apps With 100Mb Of Ram And My Phone Is Still Lightning Fast. So My Conclusion Of "Truth" Is These Help Tremendously. On The Other Hand A User Like Yourself Claims It's Worse. I Hope That Helps In Understanding What You're Asking.
so what you are saying is that its personal preference and doesnt really matter that much?
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.
how many people here use the V6 Supercharger Script with their Streak?
I'm having trouble with it and was hoping other more adept streakers know what the hell is going on with mine...
so I've run probably every script since the first one, but, it turns out the instructions I got weren't as complete as they could have been, and inadvertantly, I ran the scripts as the .txt and .pdf file formats that they came in.
I also saw a tutroial that involved changing a file name using root explorer, which I also never did.
i also did this for the 3G and kernelizer tweaks aswell
so now I have the latest script version and I notice that it's not working, I have no idea how long ago it stopped...
what I would like to know is:
A: how to totally clean all of it from my system, in order to start a totally fresh install.
B: how to properly install all three of the the scripts on the streak.
anybody nice enough to help me?
I use it...since version 8.
I use the latest version, along with the 3g & kick ass kernal tweak.
I use option 6, multitasking, 512 leaded.
Drop in here>> http://forum.xda-developers.com/showthread.php?t=991276 I'll bet someone can help you.
I've tried following all the instructions, even some from other tutorials, I've un supercharged and started from scratch.
how did you make yours stick?
bugmenotacc said:
how many people here use the V6 Supercharger Script with their Streak?
I'm having trouble with it and was hoping other more adept streakers know what the hell is going on with mine...
so I've run probably every script since the first one, but, it turns out the instructions I got weren't as complete as they could have been, and inadvertantly, I ran the scripts as the .txt and .pdf file formats that they came in.
I also saw a tutroial that involved changing a file name using root explorer, which I also never did.
i also did this for the 3G and kernelizer tweaks aswell
so now I have the latest script version and I notice that it's not working, I have no idea how long ago it stopped...
what I would like to know is:
A: how to totally clean all of it from my system, in order to start a totally fresh install.
B: how to properly install all three of the the scripts on the streak.
anybody nice enough to help me?
Click to expand...
Click to collapse
It has been made very clear by some of the senior developers here that V6 does not work on the Streaks because of some type of conflict with how the memory is allocated or configured or something, that's one of the reasons that it isn't implemented into the ROMs... so it's just snake oil, a placebo for a Streak owner. I'm not saying it doesn't work on other devices, but it DOES NOT work on the Streak
Is there a post by a dev anywhere that explains it?
Will AutoKiller Memory Optimizer work? It must this device that it doesn't work on... the minfree file disappears or something
zeppelinrox said:
Is there a post by a dev anywhere that explains it?
Will AutoKiller Memory Optimizer work? It must this device that it doesn't work on... the minfree file disappears or something
Click to expand...
Click to collapse
Yeah, but for the life of me I can't remember exactly where but what I wanna lean towards it being in fards' GingerStreak thread
I'll try and find it...
BUT the newest version does put ALL the supercharging in init.rc...
A dev just has to put it in their boot.img
zeppelinrox said:
Is there a post by a dev anywhere that explains it?
Will AutoKiller Memory Optimizer work? It must this device that it doesn't work on... the minfree file disappears or something
Click to expand...
Click to collapse
I used to have it installed but I couldn't see where it was ahving any effect or benefits so I uninstalled
I'm wanting to see what the V6 Scripts will do for CM7 but I cannot for the life of me get them to stick upon reboot.
I have them setup via Script Manger to run as root. I've gone in, did option 6 (0,4,10,12,14,15) and option 20.
Upon reboot, the settings in /sys/module/lowmemorykiller/parameters/adj are set back to the default CM7 settings
I've tried setting the properties in both local.prop and build.prop, but nothing seems to stick.
I've tried integrating the settings of the init.rc into the ROM and not doing that.
None of these options seems to make the low memory killer settings I set in V6 stick and it ALWAYS reverts back to the stock CM7 settings.
I know I can just rerun the script after it's done booting, but I never had to do this with other ROMs as it would integrate fine in /etc/init.d and run.
I see in the /etc/init.d a S99SuperCharger script with the correct permissions set. I can run it via sh and it sets the properties correctly.
It just seems that CM7 is overwriting the low memory settings somewhere and I don't know where. I don't see it occurring in any of the supplied scripts from CM7 in the /etc/init.d and I don't see it in the build.prop file.
Any ideas? I know I could just tell Script Manager to run the script on boot, but that's usually not recommended except as a last resort.
I guess the real reason I would like to get this working the way it normally does (via the init.d scripts) is just to understand what CM7 is really doing.
Thanks!
Perhaps CM7 has some sort of memory management of it's own that sets things back to the defaults on boot????????
I know, not much of an answer but it's the best I can come up with.
robocuff said:
Perhaps CM7 has some sort of memory management of it's own that sets things back to the defaults on boot????????
I know, not much of an answer but it's the best I can come up with.
Click to expand...
Click to collapse
That's what I figured is happening. I just have to determine where it's happening at.
I see that the V6 scripts are running, but something is setting it AFTER the init.d process is done.
I also checked the /data/SuperChargerRan log file and this is what I saw:
02-16-2012 09:20:53: Applied Settings from /system/etc/init.d/S99SuperCharger!
02-16-2012 09:20:54: DIDN'T Apply Settings from /data/99SuperCharger.sh!
Not sure why the second one isn't working.
Looking at the /sys/module/lowmemorykiller/parameters/adj file, it's back to the original settings that CM7 has: 0,1,2,4,7,15
iBolski said:
I'm wanting to see what the V6 Scripts will do for CM7 but I cannot for the life of me get them to stick upon reboot.
I have them setup via Script Manger to run as root. I've gone in, did option 6 (0,4,10,12,14,15) and option 20.
Upon reboot, the settings in /sys/module/lowmemorykiller/parameters/adj are set back to the default CM7 settings
I've tried setting the properties in both local.prop and build.prop, but nothing seems to stick.
I've tried integrating the settings of the init.rc into the ROM and not doing that.
None of these options seems to make the low memory killer settings I set in V6 stick and it ALWAYS reverts back to the stock CM7 settings.
I know I can just rerun the script after it's done booting, but I never had to do this with other ROMs as it would integrate fine in /etc/init.d and run.
I see in the /etc/init.d a S99SuperCharger script with the correct permissions set. I can run it via sh and it sets the properties correctly.
It just seems that CM7 is overwriting the low memory settings somewhere and I don't know where. I don't see it occurring in any of the supplied scripts from CM7 in the /etc/init.d and I don't see it in the build.prop file.
Any ideas? I know I could just tell Script Manager to run the script on boot, but that's usually not recommended except as a last resort.
I guess the real reason I would like to get this working the way it normally does (via the init.d scripts) is just to understand what CM7 is really doing.
Thanks!
Click to expand...
Click to collapse
Hehehehe... Me thinks you should search the forums a little bit. When I was testing cm7 for DZK, I tried EVERYTHING I used on previous ROMs, to include V6_SuperCharger. V6_SuperCharger DOES NOT WORK with CM7! The BIGGEST reason is the mapping for the memory slots are different with CM7, so fudging with them tends to cause massive issues and slowdowns. The reason it does not stick is most likely (speculation here) due to CM7 settings things back to it's optimized default settings.
Keep in mind that CM7 is an "optimized" AOSP based ROM... That means NO BLOATWARE! I am running with roughly 315 apps, most of which I use on a WEEKLY basis. Some, only monthly.
There are a few issues that I have noticed, root/su issues, sometimes system crashes on boot, sometime bluetooth crashes on boot, sometimes the dialer crashes... But with non-root apps, this thing SCREAMS!
Also, CM7 incorporates it's own memory management system that works better than the Moto Blur based ROMs. Just my two cents.
Ciao!
Moonshadow, thanks for the explanation. I did do a search and for some reason, your post didn't come up. Now that I search, I find it. I'll attribute it to an ID-10T or PEBKAC error.
iBolski said:
I'll attribute it to an ID-10T or PEBKAC error.
Click to expand...
Click to collapse
Are you REALLY sure about that??? It could be that Google just hiccuped during that nanosecond that your search on XDA was running... And didn't affect anyone elses searches...
You can be like Apple and blame/sue everyone else... (Just joking!)
Ciao!
Besides cm 7 does not need any script runs good as it is.
I am not sure if someone else has posted this already. But I couldn't find one, so here you go. (Please let me know if I'm mistaken)
I made two small edits to the boot.img of the stock (leaked) ICS rom in order to satisfy my needs:
1. ability to run init.d scripts,
2. start adb in root.
They are very simple and anyone with a little knowledge can do it himself, but it still is convenient to have someone else do it, isn't it? I, for one, searched the forum in vein.
Here's a short explanation of what it is, and how to utilize the features.
1. init.d :
You can place your own shell scripts in /etc/init.d (you have to create the directory yourself, of course) and run them at boot time. If you prefer the CM style userinit.d, you could create a script like:
Code:
#!/system/bin/sh
# call userinit.sh and/or userinit.d/* scripts if present in /data/local
if [ -e /data/local/userinit.sh ];
then
log -p i -t
userinit "Executing /data/local/userinit.sh";
logwrapper
/system/bin/sh /data/local/userinit.sh;
setprop
fi;
if [ -d /data/local/userinit.d ];
then
logwrapper busybox
run-parts /data/local/userinit.d;
fi;
and place it in init.d (credit: CM team). After that, you can place additional scripts without remounting system partition. Just don't forget to chmod appropriately.
A word of caution: Don't go wild and install all those tweaks found in other forums without checking to see their contents. I found that most of them to be either irrelevant or even harmful to the Amaze. Remeber, we've got one of the best phones on the market and wouldn't want to ruin it by running tweaks designed for our 'lessor' siblings!
2. adb root :
I was getting tired of the inability to adb push files to user restricted directories. Also, I use Droid Explorer a lot, but was tired of its inability to obtain root even though my phone is rooted. So I basically changed the default.prop and everything is fine now.
Added benefit is that 'adb remount' works now.
Well, that's it. Too simple, but until someone comes up with a nice kernel with these mods built in, we got to live with what's available.
DISCLAIMER : Should I even include a disclaimer? Why not? This is just a stock boot.img with minor modifications to its ramdisk portion, and it shouldn't harm your phone. If it doesn't work, simply reflash the stock boot.img found in the stock/leaked ICS roms. However, I don't want anyone to brick his phone, so don't flash this unless you know what you are doing. Also, I've seen some people bricking their phones merely by trying to flash innocent files like this one. Hard to believe, but anything can happen, so I will not be responsible if you brick your phone.
INSTRUCTIONS :
0. be sure you got the ICS build 4.0.3 with the stock kernel. rooted and have installed busybox (for init.d support only).
1. download the attached boot.img.
2. place the file where adb/fastboot can find it.
3. flash it using 'fastboot flash boot boot_new.img.
4. reboot.
5. try 'adb shell' and see if you get # prompt.
6. add some scripts in /etc/init.d and reboot and see if it runs.
It runs on my Amaze running the newer leaked ICS rom (unlocked bootloader, rooted, and busybox from the market). If you have any other settings, it probably won't do any good.
That's it, guys. Hope you have some fun with it (like I did).
Just flashed your modified boot.img so far everything works as described. Going to attempt my backlight script now. Just reflashed the stock RUU as certain Roms were giving me WiFi issues. Thanks
Is this why adb remount never worked?? I asked a few people and they acted like I was crazy.. I KNEW there had to be a reason it wasn't working.. I guess my only question is why was it no one thought to do this since the ICS release except you? LOL.
Edit: And I am out of thanks, this is my mental note to come back and hit thanks when I get some to give again!
Edit2: As advertised it works flawlessly, as advertised. It will be awesome to be able to push files to my phone and all the other things I couldn't do before! A simple tweak, as you said, still appreciated!
seems like were getting some more people around here that actually contribute to the amaze forums. thanks guys...carry on
Thank you very much
Now to find some scripts to run, lol.
Thank you all for the kind words! As I said in the OP, I was curious at first about the usefulness of my post. I truly believe that, if HTC had given us more power to mod this phone, this forum would have been 10 time more active with all sorts of useful stuff. Come on HTC, you give us the best phone (even better than the One series!), and why do you want to cripple us?
Double0EK said:
Just flashed your modified boot.img so far everything works as described. Going to attempt my backlight script now. Just reflashed the stock RUU as certain Roms were giving me WiFi issues. Thanks
Click to expand...
Click to collapse
As I didn't test the boot.img with any roms around, I don't know what went wrong with your wifi. That's why I only promised it would work with the NEWER stock ICS rom. Is it possible that you flashed the boot.img to a custom rom that is based on the OLDER leak?
Additionally, if the rom dev has made his/her own mods to the boot.img, it would not be compatible with the stock boot.img like mine. I didn't add, remove or move any files.
Silentbtdeadly said:
Is this why adb remount never worked?? I asked a few people and they acted like I was crazy.. I KNEW there had to be a reason it wasn't working.. I guess my only question is why was it no one thought to do this since the ICS release except you? LOL.
Edit: And I am out of thanks, this is my mental note to come back and hit thanks when I get some to give again!
Edit2: As advertised it works flawlessly, as advertised. It will be awesome to be able to push files to my phone and all the other things I couldn't do before! A simple tweak, as you said, still appreciated!
Click to expand...
Click to collapse
Hehe, yeah it is because of some security settings that phone manufacturers chose to enable in order to minimize customer support costs, I guess. Instead, they should give us all the power (and funding, too) so that we can support each other at XDA!
mrmako777 said:
seems like were getting some more people around here that actually contribute to the amaze forums. thanks guys...carry on
Click to expand...
Click to collapse
bilek06 said:
Thank you very much
Click to expand...
Click to collapse
I've used more than two dozen smart phones in the past, including ancient pda's and even iPhones (ouch!), and I think the Amaze has the best (mix of) hardware. I, too, wish there were more devs here, and wonder why some great devs around didn't see the potential in it. Well, HTC isn't doing something right...
Dark Nightmare said:
Now to find some scripts to run, lol.
Click to expand...
Click to collapse
Hard to find anything useful for the (already mighty) Amaze, isn't it?
Things I would add for myself are like:
- house keeping: delete cache, move/copy important files from internal to external sdcard, etc.
- renice phone and input method a bit. How about acore? Probably not...
- zipalign, maybe, if you're fanatic about it.
- save logs and erase oldest ones. Gosh, what am I saying? We've got so much storage space. Oh, well. If we save the logs in external sdcard, we can view them even when the phone doesn't turn on...
Hehe, I think I should search.
I never flashed your boot.img on custom roms only on the stock. I have better WiFi with stock.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
ringochan said:
Hard to find anything useful for the (already mighty) Amaze, isn't it?
Things I would add for myself are like:
- house keeping: delete cache, move/copy important files from internal to external sdcard, etc.
- renice phone and input method a bit. How about acore? Probably not...
- zipalign, maybe, if you're fanatic about it.
- save logs and erase oldest ones. Gosh, what am I saying? We've got so much storage space. Oh, well. If we save the logs in external sdcard, we can view them even when the phone doesn't turn on...
Hehe, I think I should search.
Click to expand...
Click to collapse
Lol searching, was thinking about the v6 supercharger script, still reading into it though.
I use Cache Cleaner NG to clean. Set it on Auto with new method 2 times a day.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Double0EK said:
I never flashed your boot.img on custom roms only on the stock. I have better WiFi with stock.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Click to expand...
Click to collapse
I must have misread your original post. My bad. But then, I have no idea about your wifi problem with the modified boot.img. I didn't touch anything other than 2 things that I mentioned. And my wifi is working just fine. It's spooky.
Dark Nightmare said:
Lol searching, was thinking about the v6 supercharger script, still reading into it though.
Click to expand...
Click to collapse
LOLOLOL! That guy is something! I mean the guy who created the v6 script. Yes, I think his concept is right on. I may borrow some of his tweaks like app grouping and oom/minfree. I've done similar adjustments when I was still using my G1/Dream, but with Amaze with de-bloated ICS, I am already getting (almost, if not) everything he is promising we can achieve with his script.
The only lag I have is when some background services are busy. But I don't really want to make them low priority (yet).
What do you think you like to achieve using v6? I may be able to help because I myself want to experiment some.
Double0EK said:
I use Cache Cleaner NG to clean. Set it on Auto with new method 2 times a day.
--------------------------------
It's Better To Fail At Originality
Than To Succeed In Imitation.
--------------------------------
Click to expand...
Click to collapse
Hehe, you know that some script junkies won't approve of ANY apps to take over what he can do with scripts, right? I've seem many. No, I've worked with many! They refused to use GUI text editors, LOL!
ringochan said:
LOLOLOL! That guy is something! I mean the guy who created the v6 script. Yes, I think his concept is right on. I may borrow some of his tweaks like app grouping and oom/minfree. I've done similar adjustments when I was still using my G1/Dream, but with Amaze with de-bloated ICS, I am already getting (almost, if not) everything he is promising we can achieve with his script.
The only lag I have is when some background services are busy. But I don't really want to make them low priority (yet).
What do you think you like to achieve using v6? I may be able to help because I myself want to experiment some.
Click to expand...
Click to collapse
Hey, if you want to try out something cool, check this out.. http://android.mimic.ca/ it patches the services.jar file to change the OOM priority, evidently in a way more effective than the supercharger script can do it. I was going to try to include it in the latest update for my rom till I decided I wanted to work on other things.. the guy who made supercharger script helped design the patch for the file though Just thought you may be interested.
Silentbtdeadly said:
Hey, if you want to try out something cool, check this out.. http://android.mimic.ca/ it patches the services.jar file to change the OOM priority, evidently in a way more effective than the supercharger script can do it. I was going to try to include it in the latest update for my rom till I decided I wanted to work on other things.. the guy who made supercharger script helped design the patch for the file though Just thought you may be interested.
Click to expand...
Click to collapse
erm... it CAN'T be more effective than supercharging... because it IS SuperCharging
Well, 50% of it. The other 50% comes from the script when on ICS.
Why do you think that website is integrated into the latest V6 Scripts?
That needs to be done in addition to the V6 script when using ICS roms to get 100%.
Of course, non ICS roms get 100% supercharged with the script itself since there's no need to patch services.jar
zeppelinrox said:
erm... it CAN'T be more effective than supercharging... because it IS SuperCharging
Well, 50% of it. The other 50% comes from the script when on ICS.
Why do you think that website is integrated into the latest V6 Scripts?
That needs to be done in addition to the V6 script when using ICS roms to get 100%.
Of course, non ICS roms get 100% supercharged with the script itself since there's no need to patch services.jar
Click to expand...
Click to collapse
LOL. Did you search yourself? HAHA. Yes, we are talking about how awesome your scripts are..
I would be using them myself but I can't figure out a setting that really makes it awesome like it did with my old vibrant!
Edit: And thanks for the explanation, that makes more sense than whatever post that lead me to your patch.
what is a modified boot image?
what is the different between the modifed boot image and the android we can download from the developer google site/?