What this does is speed up your tab. Its crazy how well zepplinrox got this to work, but it makes the tablet fly. It doesnt require more battery, nor stress the hardware any. It alters and fixes the OOM groupings, lowmemorykiller and the priorites. I don't want to get into the nitty gritty, but do it and I'm sure you will be amazed!
If you do not have the init.d folder, then you need to load a custom rom. Some custom roms will have this folder. Read on page two, zepplinrox explains it more.
Here is the process to get the supercharger to work and stick on out tabs. Its all spelled out on the original post ( by zepplinrox ) , but this is the short and sweet version.
You need to be rooted and have busybox 1.18.2 or lower.
First off go here and download the script : www.mediafire.com/?w6682pwu52ty5o6
Then download this app : https://market.android.com/details?id=os.tools.scriptmanager&feature=search_result
1. Then you run the script manager and find the V6 script that we first downloaded.
2. When you click on the script, the manager will open,( Make sure the run as root box is ticked under the "run" button ) just hit run in the top left of the screen.
3. Then, you have to just click in the black anywhere and the keyboard will open. Select a number 1, 2, or 3 , this is how fast the text will scroll. Being the screen is so big, select number 1. You will be fine. Hit enter on the keyboard, then lower the keyboard away.
4. You can now see a lot of options, don't get nervous. The script does it all itself. Being that we have so much ram already, the minfrees are already huge, but can be bigger . So options 1 - 7 are smaller than the stock minfrees. You can use either setting 8 or 9. I'm using the setting number 9. So to select the minfrees you want ( either number 8 or 9 ), click on the screen to bring up the keybpard, and hit the number you want ( again 8 or 9 only )!
5. Once that is done you will see the script run some info in front of you. It will say to reboot but don't yet. Type the number 17 in, and you will see it say bye etc. Ok, once it says bye, hit the back soft key in our launcher. Now navigate to this on the screen that in front of you. Keep hitting back until you get to the ''/'' of the tablet. Rom there you will click on ''system'', then click on ''etc'' and lastly on '' init.d '' . In there you will see a file called '' 99SuperCharger'' . Click on that and the script manager will open again, but you need to select certain boxes this time before hitting run. When the screen comes up hit '' run as root '' and '' run on boot ''' and hit save. Once that is done hit run ( nothing happens here, so don't expect to see anything scrolling) , then back out using the back arrow in our launcher. Then reboot your tablet, and that's it. The custom minfrees now stuck, and your supercharged!
Thanks to zepplinrox for this script!
P.s. to find out of the script stuck, reload the FIRST V6 script. Select your speed like we did, then once it is all loaded up you will see a line in there that says prior mifrees ( prior is still your current ) . Just match that up with the number you selected at first.
Thats it.
Here is the op on supercharging, from zepplinrox forum.xda-developers.com/showthread.php?t=991276
Sent from my Galaxy Tab!
so what does this do exactly?
In a nutshell, its a memory manager.
It will speed up your phone, multiasking etc. Its kinda crazy how well it works, and does not require more battery life like overclocking does. What it does it rearrange the OOM groupings, lowmemorykiller and priorties.
Sent from my Galaxy Tab!
cool thanks for the quick reply, can this be used in conjunction with a Task's ROM and pershoot's kernel?
I think I'll wait for others to test this out first seems too good to be true
mickey78 said:
cool thanks for the quick reply, can this be used in conjunction with a Task's ROM and pershoot's kernel?
Click to expand...
Click to collapse
yes. you can use in on basically anything bro.
yes it works anything android based. And for the skeptics, its been out for sometime now. Look here..
forum.xda-developers.com/showthread.php?t=991276
That's the op on this.
Sent from my Galaxy Tab!
Samsung Adrenaline Shot
This has been developed for some days and I am using on my Captivate, it's amazingly fast. I know some files are HC based but written for GB, maybe someone take a look and see if it will work?
http://forum.xda-developers.com/showthread.php?t=1236779
I use SAS, not USAS as it is just a script.
I've been using it for a while on my evo and the same with the tablet. All works well.
Sent from my Galaxy Tab!
I'll follow this thread closely. It always amaze me how a small group of people working together can achieve things beyond what Google themself can achieve with their OS.
Im getting permission denied during the last step (run as boot etc.)
Any ideas? My tab is deffo rooted as other apps that require root work fine.
Cheers!
I haven't got the init.d? What's wrong? I'm using broadcom KH7.
Here is a screen shot.
same for me, i dont get the init.d folder. I saw many permission denied lines in the script, so i run the script again with root. It doesnt help and i restart my Tab... and now i am in a bootloop. So i restore my backup, but can someone tell me what i do wrong?
Thx in advance
Flash
Edit: same for me, like klass1 , i use the Broadcomb stock too
klass1 said:
Here is a screen shot.
Click to expand...
Click to collapse
I also have the same problem, running stock rom.
Is root required?
Hey sorry guys, I'm out of the house. But yeah root required, I think. But not 100% sure as I have always been rooted. And as far as not seeing the init.d folder.. are you fellas all the way back to the '/' in the script manager? Go system, etc,init.d and the 99SuperCharger should be there. In sure why you can't see back that far. Are all or you guys rooted that are having issues? The ron type doesn't matter, as these folders are universal on all roms.
Also I too received some denied lines, but all is working as should. So that shouldn't be an issue.
Sent from a miui powered HTC Evo.
Yes, I am all the way back at / going to /system/etc and I could NOT find the init.d folder after running the script. I am rooted and using the Broodcomb ROM for GT-P7500. I have the same problem the other guys have. Help please!
i didnt have it either, the init.d folder, so i ran a kernel tweak from the creator of V6 scrpit and that created a init.d folder for me then i ran the script again and there it was the 99Suercharger file. So i think you can just create the folder your self, no need to run the kernel tweak, just ad new folder to system/etc called init.d that should fix it for thoose that dont have it created by the script.
And did you noticed a good speed improvment?
Sent from my GT-P7500 using xda premium
How do you create a folder?
Related
I shall take no credit for any of this. Smartsreenath first put me onto the idea, and pretty much anyone if this forum could've managed it. I just had the time to do it all.
Woo! Snakehult, being a genius, has made a clever little zip that uses proper scripts to just change the required value, instead of the whole file. So! Instead of me making an insane number of zips every time ROMs are updated use these instead. Cheers Snakehult!
Attached is a zip file with a whole lot of flashable zips in it. Don't flash the zip you download, extract that one somewhere and look inside
How to use:
Download the attached zip file, and extract it to somewhere on your computer. Inside the zip are a bunch of folders, each folder named after a ROM for the HTC Legend. Navigate into the folder that shares the name of whatever ROM you are using and inside you will find 6 zip files. These zips are flashable. The the zips are names thus: xxx.zip, where xxx is a number. The lower the number, the higher the apparent resolution. Choose a zip, copy it to your SD card and flash it like any other zip. To revert back to how it was simply flash the "160.zip". This just flashes a completely un-modified version of build.prop for your ROM. Make sure you only use the zips form the correct folder for your ROM, or funny things *might* happen.
More info:
By editing the build.prop file it is possible to increase the dpi of an Android device. This essentially scales everything down, so you can fit more on the screen. This is especially nice for browsing the market and the internet; as well as improving, in my opinion, the overall Android experience. The lower the number in the name of the zip, the higher the apparent resolution. It's worth noting that this does *not* change the actual resolution of the Legend; it's still a HVGA device. So you still can't install apps designed for bigger, more powerful phones, like the HTC Desire or Nexus One. This is a somewhat flawed way of achieving this effect, and can have some ugly side effects:
Some apps simply don't scale
HTC-IME mod ends up screwed
Games *can* be rendered unplayable, but not always. Often the menu is the worst affected part.
A work around to fix a number of issues is to disable the built in compatibility mode of Android, and if I knew a way to do this through a zip, rest assured that I would. It'd save me having to explain how to do it. Alas, I don't know how, so here's how:
In your ROM look for an app called "Spare parts". If it's not there look for it in the market. If you open that app and scroll down to the bottom you will find a checkbox option for "Compatibility mode". Ensure that this is *un-checked*, then reboot. Most issues will be resolved. As I learn more about Android I shall keep an eye out for a way to force apps to scale correctly, and if I ever find one I'll update these.
I have also tried values higher than usual, just for kicks. I don't expect them to be useful, nor will I make actual zip files for them, but I went all the way up to 200; and it felt like I was using an HTC wildfire: everything was really quite cramped.
My personal favourite setup is as follows:
CM 6.1, with a 768MHz overclock
My "lcd-density" (this MOD) set to 130
Launcher Pro Plus with 5 icon rows
Below is a paste of what was the first post (when I was just trying to fix a ****-up on my part), and is now here for reference. It has all of the original build.prop files attached.
Attached is a .zip file, which you will need to extract somewhere. It's not for flashing. Within this zip are several folders, each containing a "build.prop". You'll notice that each folder is named after a ROM: Azure, NeonMOD etc. The "Based-on-stock" folder should cover these ROMs:
[ROM] Based on Official WWE_2.03.405.3 ROM + A2SD [Rev 03 - released]
[ROM] UPDATED Almost Stock Legend HTC WWE 2.03.405.3 Radio 7. 08.35.21
You'll need to use ADB to push these files, as I haven't had time to make flash-able zip's for them yet
Instructions:
1. Extract the zip to a suitable directory, and locate the appropriate build.prop
2. Copy the build.prop to your AndroroidSDK/tools folder
3. Reboot your phone into ClockworkMOD recovery and navigate the the "Partitions menu", then click "mount /system"
4. Connect your phone to the PC and start CMD/a terminal window in your AndroidSDK/tools folder
5. Run the command "adb devices" to ensure that the ADB server is running, and that the PC has detected your device correctly
6. Run these commands in this order:
adb push build.prop /sdcard/build.prop
adb shell
mount -o remount,rw /dev/block/system /system
cp /sdcard/build.prop /system/build.prop
This will put your resolution back to default, but should fix everything else too. If you still want a higher resolution then follow the guides in posts 1 and 2 of the other thread. This one.
If you can't use ADB for whatever reason you'll just have to wait it out until myself or someone else create proper, flash-able, fixes. I have done this to try and quickly rectify the issue; assuming, of course, that most people in this forum can use ADB
I will make proper zips, but it's getting late for me...
Click to expand...
Click to collapse
hi
here is a zip for neonmod 0.21 with 135lcd, flashed it on my legend today with rom manager
Wow do we have a lot of ROMs...
Anyhoo, I am currently working on appropriate flashable zips for each ROM, and each ROM will have the following versions:
110
120
130
140
150
160 (original)
I'm doin' 'em as fast as I can..
EDIT:
Current thoughts:
All build by Ali Ba have nice, short build.prop files. The current record for the longest one it held by MyTouch Legend...
TheGrammarFreak said:
Wow do we have a lot of ROMs...
Anyhoo, I am currently working an appropriate flashable zips for each ROM
Click to expand...
Click to collapse
Awesome!
All our lovely ROMs are actively being used, and its great.
Thx for all hard work!
No worries, I hope I haven't missed one
Now to sign 50 60 zip files...
EDIT:
DONE! All finished. I really hope they work. I can't test them all, but there is no reason why they won't work. Lemme know either way.
nice job
thanks bro
nice
spare parts is also in neonmod
xennr3 said:
nice
spare parts is also in neonmod
Click to expand...
Click to collapse
Cool, and you can turn compatibility mode off?
TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
sure
1234
TheGrammarFreak said:
Cool, and you can turn compatibility mode off?
Click to expand...
Click to collapse
thanks for your work! i just tried 130 dpi and it seems really good.. i'll try also others zip asap!
yes with compatibility mode off all softwares i tried work really well!
xennr3 said:
sure
1234
Click to expand...
Click to collapse
Cool, thanks for the info. I'll update the OP when I'm home
Sent from my Legend using XDA App
Wow, really cool mod Love it!
Good job!
Cool, glad you like it
Just flashed 130 for SpeedLegend and it worked like a charm
HTC_IME works here (this isnt the mod)
images dont look so good anymore and stuff, but alright
works fine
edit; TBH I find the 140 to be 'more' compatible overall, and show a better picture (ive tried all the flashables)
thats besides the orgnal setting btw, it gives the best picture by far.
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
SimDroid said:
Im on the same DPI and rom as you TheGrammarFreak. works great. Too bad there is no function for more icons on the homescreens with LauncherPro...
Click to expand...
Click to collapse
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
i glad to hear that someone like you got the idea from my thread........good work ...........and nice job.....you will get all help from me and from my friends
FOLLOW ME http://smartsreenath.blogspot.com/
TheGrammarFreak said:
Yeah it does. On your homescreen press menu, then preferences. In advanced options there is something for it.
Sent from my Legend using XDA App
Click to expand...
Click to collapse
yeah, that is for 5 rows on a screen, but you still can't have 5 icons on a row... That's what I want. I tried ADWLauncher again, but it feels so god damn slow.
Ummm, I have 5x5 icons on my desktop with the stock ADW launcher. Just check out "Settings > ADW > Screen prefs > Desktop cols/Desktop rows"
I'm not sure on which phones this will work.
Motorola Milestone is for certain. Probably other Motorolas as well.
If you have the file /system/bin/mot_boot_mode, then this should work just fine.
Edit: Works on DroidX, Atrix, Bionic, Defy... (I guess it really does have a chance of working if you have mot_boot_mode
Do this at your own risk
What you need:
1. GScript Lite or Script Manager
2. Rooted Phone. For Milestoners, you can use Universal Androot (not in market ?)
3. Busybox Installer
You don't need to have a vulnerable recovery applied.
Why you want it: People on custom roms take it for granted that they can run custom scripts from the /system/etc/init.d folder.
Overclocking, tweaking memory settings, kernel tweaks, etc.
Those on Stock ROMS usually have to resort to 3rd party apps (eg. Milestone Overclock, Auto Memory Manager) that take up memory to do stuff that custom roms do automatically and easily - with boot up scripts.
It's possible for Stock ROMS to get this ability via open recovery but most users may find it overwhelming and confusing as to where to even start.
I have also been working on GScripts to get my SuperCharging / Bulletproof Launcher tweaks to work on all phones without need of 3rd party software.
I found that the easiest way would be with a startup script placed in the /system/etc/init.d - the same way that custom roms do it.
Since alot of users would be uncomfortable with getting it working via open recovery, I converted the open recovery script to work in GScript!
Booya!
Instructions: 1. Extract the attached zip file into the root of your sdcard. The files should then be inside the folder /sdcard/gscript
................... 2. Run GScript Lite
................... 3. Press menu > Add script > Load file button
................... 4. Select "!Autostarts - Enable init.d on Stock ROMS.sh"
................... 5. Leave "Needs SU?" checked and press the Save button.
................... 6. It now shows up in the list of GScripts.
................... Note: GScript will save it internally within it's settings.
................... 7. Run the script by simply selecting it in GScript... and...
................... 8. Get tweaking!
All thanks go to those who put Androidian OpenRecovery together! ie. Skrilax_CZ, Azhad and 89luca89!!
Good job, Joe. I'll test and let you know.
btw, the values that we discussed a few days back work better for me on stock. First 3 from your script and last 3 default values.
Cool beans
zeppelinrox said:
What you need:
1. GScript Lite
2. Rooted Phone. For Milestoners, you can use Universal Androot (not in market ?)
3. Busybox Installer - Have it install the latest BusyBox (v1.19). This ensures GScript doesn't spit out ugly stderr: messages.
You don't need to have a vulnerable recovery applied.
Why you want it: People on custom roms take it for granted that they can run custom scripts from the /system/etc/init.d folder.
Overclocking, tweaking memory settings, kernel tweaks, etc.
Those on Stock ROMS usually have to resort to 3rd party apps (eg. Milestone Overclock, Auto Memory Manager) that take up memory to do stuff that custom roms do automatically and easily - with boot up scripts.
It's possible for Stock ROMS to get this ability via open recovery but most users may find it overwhelming and confusing as to where to even start.
I have also been working on GScripts to get my SuperCharging / Bulletproof Launcher tweaks to work on all phones without need of 3rd party software.
I found that the easiest way would be with a startup script placed in the /system/etc/init.d - the same way that custom roms do it.
Since alot of users would be uncomfortable with getting it working via open recovery, I converted the open recovery script to work in GScript!
Booya!
Instructions: 1. Extract the attached zip file into the root of your sdcard. The files should then be inside the folder /sdcard/gscript
................... 2. Run GScript Lite
................... 3. Press menu > Add script > Load file button
................... 4. Select "!Autostarts - Enable init.d on Stock ROMS.sh"
................... 5. Leave "Needs SU?" checked and press the Save button.
................... 6. It now shows up in the list of GScripts.
................... Note: GScript will save it internally within it's settings.
................... 7. Run the script by simply selecting it in GScript... and...
................... 8. Get tweaking!
All thanks go to those who put Androidian OpenRecovery together! ie. Skrilax_CZ, Azhad and 89luca89!!
Click to expand...
Click to collapse
Hi, good evening.
Excellent work... But I cant see
gscript-All_ROMS-SuperCharge+BulletProof_Pack_v4.zip
It isnt a link.
Thanks. Best regards
Marcos
Hey Zep, will these work on 2.1 eclair? I am running 2.1 for a change. Had enough of the half cooked Froyo and GB roms.
I'm not sure.
Did you flash a custom eclair or stock?
I'd love to get it to work with stock eclair though.
If you have a 10overclock, where is it?
Actually, a good test is if you were able to overclock with AOR's froyo menu after running this gscript
zeppelinrox said:
I'm not sure.
Did you flash a custom eclair or stock?
I'd love to get it to work with stock eclair though.
If you have a 10overclock, where is it?
Actually, a good test is if you were able to overclock with AOR's froyo menu after running this gscript
Click to expand...
Click to collapse
I am currently overclocked using milestone overclock app. There is no 10overclock file in /system/etc/init.d folder. I will try overclocking using AOR after loading modules.
Sent from my Milestone using Tapatalk
In AOR, the eclair overclocking uses the /system/bin/boot_script folder as opposed to the usual /system/etc/init.d folder.
If I do a google search for "eclair /system/bin/boot_script" there aren't that many results.
If I do a google search for "eclair /system/etc/init.d" there are twice as many hits.
So this should work on stock eclair without vulnerability patch
Applying this to a rooted, stock 2.2.1 milestone makes the M logo bootloop... ive tried it twice. Followed the steps exactly..
And I think it may have bricked my phone :S Now it won't turn on anymore...
So buysbox is installed right?
I actually developed the script working with stock telus 2.2.1 so it works.
I had a problem flashing the sbf 2.2 upgrade and was stuck on the M logo.
From recovery menu, I had wiped caches/reset to factory defaults and it booted up.
What have you tried so far?
zeppelinrox said:
So buysbox is installed right?
I actually developed the script working with stock telus 2.2.1 so it works.
I had a problem flashing the sbf 2.2 upgrade and was stuck on the M logo.
From recovery menu, I had wiped caches/reset to factory defaults and it booted up.
What have you tried so far?
Click to expand...
Click to collapse
I can't do anything really. It won't turn on, not even into recovery. No M logo, the screen doesn't even light up, and when I try to charge, the charge light doesn't turn on, and it doesn't charge, and isn't recognized by my comp. Initially it went into a boot loop, but then I restored via nandroid, but then I tried again, and I left the phone for a couple mins, then when I got back, it was really warm and wouldn't turn on or charge. I have a feeling something burnt out. I'm gunna bring it to telus today and try and get a new one.
For charging it, use the wall charger.
Does anything happen if you take the battery out and plug it in?
Normally, you would get a big battery icon with a question mark.
Then put the battery in and it changes to whatever the battery level is.
zeppelinrox said:
For charging it, use the wall charger.
Does anything happen if you take the battery out and plug it in?
Normally, you would get a big battery icon with a question mark.
Then put the battery in and it changes to whatever the battery level is.
Click to expand...
Click to collapse
I don't have my wall charger with me, but I've made some progress I think..
Now when I plug it into usb without the battery, the light goes on, and I can insert the battery without it shutting off. But it still won't turn on , and when I plug it in with the battery in it, the light doesn't come on. I've been trying that battery bypass thing, and my comp is definitely responding to it being plugged in, but only for a second or two.
If you don't have much battery left, you're not gonna get too far.
It'll just keep draining more n more.
Howabout a car charger to charge it in the meantime?
zeppelinrox said:
If you don't have much battery left, you're not gonna get too far.
It'll just keep draining more n more.
Howabout a car charger to charge it in the meantime?
Click to expand...
Click to collapse
I brought it to telus. The battery is fine, theres juice. They tried charging it with a regular wall charger, but still no luck, so in it goes for repairs.
ah ok.
Hopefully it won't take too long to get it back
zeppelinrox said:
ah ok.
Hopefully it won't take too long to get it back
Click to expand...
Click to collapse
They said 2 months is the max, and I'm stuck with a stupid moto backflip.. gunna try and switch it out tho.. btw, your scripts worked awesome in openrecovery when I was using cm7. That bulletproof launcher was perfect
heh.. thanks
So if you had openrecovery going with vulnerable recovery, why did you use the gscript method?
Just curious, it's the same thing really.
But with openrecovery available you would have more options for trying to get it going again.
zeppelinrox said:
heh.. thanks
So if you had openrecovery going with vulnerable recovery, why did you use the gscript method?
Just curious, it's the same thing really.
But with openrecovery available you would have more options for trying to get it going again.
Click to expand...
Click to collapse
I tried that actually, but the overclocks didn't work, and neither did the bulletproof launcher. They worked on custom roms, but not stock.
I see.
In aor's froyo menu there is the enable autostarts which does the exact same as this gscript since I merely copied it lol.
The only advantage of the gscript is that you don't need vr patched and no aor.
Of course both would then allow the overclocking and other stuff on stock roms.
Sent from my Milestone using Tapatalk
requires Root (Superuser/Busybox), and a kernel that supports "init.d" scripts (script files that are stored in /system/etc/init.d/).
The script also has a partner called V6 supercharger they go pretty well together heres a link to the V6 supercharger by zeppelinrox
this script is so easy to use but users might have problems using it so here is a easy install for you all to use i have converted it to run on non samsung phones by renaming the file and removing processes connected to the stock samsung apps
Have Clockwork recovery installed
Download the update.zip from the bottom of the post
Reboot into recovery and install the update.zip
Now for the really easy part
Using Root Explorer navigate to ect/init.d and select mount RW now scroll down to the "97loopy_smoothness_tweak" file and open it in the text editor within root explorer and you will see the 3 main sections to the script they are called
At the start of the script you will see this
Code:
USER_LAUNCHER=""
you need to add the launcher you currently use so that it gets locked in
Resident system apps
Other system apps
Other apps
in the 3 sections you will see lines one code that look the same which are
Code:
if [ $PROCESS_1 -eq "0" ]; then PNAME="com.android.phone"; NICELEVEL=-20; if [ `pidof $PNAME` ]; then renice $NICELEVEL `pidof $PNAME`; PROCESS_1=1; P_CHECK=`expr $P_CHECK + 1`; fi; fi;
All you do to add a app you want to keep in memory for as long as possible is to edit the script and change these values for e.g the stock dialer to go contacts
Code:
PNAME="com.android.phone";
to
Code:
PNAME="com.japps.contactpro";
that will keep Go Contacts EX locked in the background so everytime you wish to use the GC EX dialer you wont have to wait for it redrawing before using it.
To find the process names goto the data/data folder and all the folders you see in there are the process names used by the apps e.g. the com.android.vending folder is the process name for the vending.apk aka market app.
Just to let users no this script will not auto start the apps on reboot and once you first select the app you have added to the script after reboot you will have to wait for the app to redraw the app again into the memory slot once it has done that the app will remain in a cache type(hidden) form until you run the app again then it will return to ram in the foreground.
lpy of XDA said:
What this script hopes to achieve:
- Entering your PIN with minimal/no delay/lag
- Minimising delay with lock screen pattern/unlock (not the time it takes to wakeup, but the touchscreen response lag)
- Having smoother notifications on the status bar, and smoother pulldown menu response
- Minimising Launcher lag while Media Scanner is running (can scroll through screens without heavy pauses)
- Minimising lag when scrolling through the market while icons are still loading
- Installing/Uninstalling apps while continuing other tasks
- Minimising/eliminating intermittent lag spikes in gaming
- No delay in being able to answer phone calls
... you get the idea
Click to expand...
Click to collapse
Thanks goes to the creator lpy @XDA
tweak source:
http://forum.xda-developers.com/showthread.php?t=1137554
Download:
http://www.mediafire.com/?g4fte3m87t3ukui
Install via CWM as update.zip ???
Have you tested this? I'm doing backup right now, and I might, but I'm looking at the script, and it says it's for Galaxy S. There's also a part on one of the first lines where you have to specify your launcher. Also, I don't think the scripts it our init.d even begin with "S_..", but rather with a two digit number, e.g. "06swapon".
EDIT: I edited the file to point to my launcher "com.fede.launcher", and touched nothing else. Named it "18smooth" or something of the sort, and put it in /system/etc/inid.d. The system failed to boot(never got past the second "LG" screen. Maybe it's the rom I'm using, but this is not working so far. I hope your promised tutorial is of use.
nutterbg said:
Have you tested this? I'm doing backup right now, and I might, but I'm looking at the script, and it says it's for Galaxy S. There's also a part on one of the first lines where you have to specify your launcher. Also, I don't think the scripts it our init.d even begin with "S_..", but rather with a two digit number, e.g. "06swapon".
EDIT: I edited the file to point to my launcher "com.fede.launcher", and touched nothing else. Named it "18smooth" or something of the sort, and put it in /system/etc/inid.d. The system failed to boot(never got past the second "LG" screen. Maybe it's the rom I'm using, but this is not working so far. I hope your promised tutorial is of use.
Click to expand...
Click to collapse
yes i have tested it and it works i will be uploading a modded one for the update.zip but if you install it just rename it to 97smoothnees, it asks for the launcher you currently are using e.g. adw launcher but if you have any worries wait until tomorrow for the tut
I think this is helping with battery management because my battery seems to be going down slower
Sent from my GT540 using XDA Premium App
Let's hope I'm wrong. Looking forward to that tutorial.
Downloaded it, and flash'd it in cwm on my girlfriends gt540. In her opinion, it makes a noticeable difference.
Sent from my Nexus S using XDA Premium App
Oki, so I install this script and I must say that it's working. ;-)
Tut added hopefully you can all understand it
Hmm, I don't know why but I don't have "97loopy_smoothness_tweak" in folder.
pRo_lama said:
Hmm, I don't know why but I don't have "97loopy_smoothness_tweak" in folder.
Click to expand...
Click to collapse
let me have a quick check to see whats going on
eoghan2t7 said:
Have Clockwork recovery installed
Download the update.zip from the bottom of the post
Reboot into recovery and install the update.zip
Click to expand...
Click to collapse
I did this and when i'm trying to do next i can't find the file in etc/init.d folder
pRo_lama said:
I did this and when i'm trying to do next i can't find the file in etc/init.d folder
Click to expand...
Click to collapse
i just tried the update.zip again there and it installed fine for me what clockwork version are you using?
but you can extract the zip file and manually add the file to the init.d folder and give it these perrmissions
xxx
xxx
xxx
I have 4.0.1.4.
When I apply script, reboot phone then on screen with PIN I don't have any delay.
pRo_lama said:
I have 4.0.1.4.
When I apply script, reboot phone then on screen with PIN I don't have any delay.
Click to expand...
Click to collapse
try adding it manually to see what happens.
So I must manualy add the file into system and then continue with tutorial ???
yes you coy the script to the ect/init.d folder then continue with the tut
ok, i'm going to try it ;-)
Can't download please mirror on another hoster.
Sent from my GT540 using XDA Premium App
Should this method not eat battery rather than conserving it? As apps run in background correct me if m wrong....
Sent from my GT540 using XDA App
I have been looking through the recent ICS threads and people have had alot of out of memory problems, so I thought I would post this easy to understand tutorial (well I hope it will be easy to understand)
Before starting, on Miroslav's Project Icecream Swift, you need to download busybox installer and install version 1.18.2, busybox included will not correctly determine minfrees.
First download the latest version of V6 at the end of this post, then copy it to your SD card and run it with Script Manager (from the market).
Choose your prefered scrolling speed and in the latest version its pretty much automated, you just have to say yes no a few times but it will auto detect the best settings based on the RAM of the device.
Also do not superclean and reboot, we need to do something else before we reboot.
Ensure you have a file explorer that can view the /system partiton before continuing.
On your phone browse to http://android.mimic.ca
Then click browse and choose your file explorer, and find services.jar in /system/framework then upload it.
After this the site will modify the services.jar and offer a download for it, to make it easy lets just use the update.zip so select that and download it.
Using the stock browser atleast it will go to /sdcard/download.
After this reboot to recovery, scroll to mounts and storage and mount /system manually (when I did not do this it didn't write the modified file) then install the zip.
Wipe dalvik cache and reboot, first boot will take a long time while its upgrading applications then run the V6 supercharger script to confirm you are 100% supercharged and you have your hard to kill or die hard launcher.
Note: On AOKP (atleast this version) because it doesn't have init.d (think its that one) before you first reboot to install services.jar you will need to browse in script manager to /data and find the 99SuperCharger.sh file and make it run on boot to get 100% supercharged.
I don't know if its important but every new rom I use I repatch services.jar just to be safe.
Any questions post here (also if the file doesn't download let me know and I'll upload it and post the link.)
Recovery zips for AOKP and Icecream Swift services.jar can be found below, just mount /system manually and i"nstall zip from sdcard" sorry it took a bit
For me i just use swap works good enough
For me not. Even if i use swap when i try to use gplay and listen music, music app closes itself. (Miro's latest ron)
Sent from my GT540 using xda premium
coto39 said:
For me not. Even if i use swap when i try to use gplay and listen music, music app closes itself. (Miro's latest ron)
Sent from my GT540 using xda premium
Click to expand...
Click to collapse
Thats because swap is not technically used as RAM, what it does is suspends background apps using up RAM, then puts that state in to swap, the apps cannot run from the swap partition, so if you are listening to music and using the browser you will notice this, if you have twitter open, then open a link from a twitter post, the state of twitter gets pushed to the swap partition, to allow the browser to open and run, you then close the browser and it pulls twitter from the swap partition back to RAM giving the illusion of multitasking.
V6 actually gives multitasking by making sure android does not close apps when you have a fair amount of RAM left.
delsus said:
Thats because swap is not technically used as RAM, what it does is suspends background apps using up RAM, then puts that state in to swap, the apps cannot run from the swap partition, so if you are listening to music and using the browser you will notice this, if you have twitter open, then open a link from a twitter post, the state of twitter gets pushed to the swap partition, to allow the browser to open and run, you then close the browser and it pulls twitter from the swap partition back to RAM giving the illusion of multitasking.
V6 actually gives multitasking by making sure android does not close apps when you have a fair amount of RAM left.
Click to expand...
Click to collapse
Thanks for the explanation. I tried to apply supercharger (latest version, Update9RC8.2) to IceCreamSwift second official release bug when it try to apply minfrees the phone reboots.... The version you left works but don't shoy current minfrees, just shows: , , , , ,
coto39 said:
Thanks for the explanation. I tried to apply supercharger (latest version, Update9RC8.2) to IceCreamSwift second official release bug when it try to apply minfrees the phone reboots.... The version you left works but don't shoy current minfrees, just shows: , , , , ,
Click to expand...
Click to collapse
Hmm thats wierd, I have always been able to see them, but if it works it works
delsus said:
Hmm thats wierd, I have always been able to see them, but if it works it works
Click to expand...
Click to collapse
Don't know why but everytime i try to use the script with latest miroslav ICS i got an exception when try to appy supercalculator minfrees then a reboot.
With latest version of the script i can see original minfrees= "1,1,1,1,1,1,1" and when i try to apply new one = Poof! reboot!
Did you installed another busybox or something?... This rom without the script sucks in multitasking matter. (open one app and the others will be closed, is monotasking )
coto39 said:
Don't know why but everytime i try to use the script with latest miroslav ICS i got an exception when try to appy supercalculator minfrees then a reboot.
With latest version of the script i can see original minfrees= "1,1,1,1,1,1,1" and when i try to apply new one = Poof! reboot!
Did you installed another busybox or something?... This rom without the script sucks in multitasking matter. (open one app and the others will be closed, is monotasking )
Click to expand...
Click to collapse
I'll check it on new version of miro's rom tonight when I charge my phone (battery is dead right now) but I normally use the default busybox, it could be that the default has been changed on this rom, download busybox installer from the market and try a version on there, they are all complete so should have no problems on that end, lemme know if it still doesn't work.
delsus said:
I'll check it on new version of miro's rom tonight when I charge my phone (battery is dead right now) but I normally use the default busybox, it could be that the default has been changed on this rom, download busybox installer from the market and try a version on there, they are all complete so should have no problems on that end, lemme know if it still doesn't work.
Click to expand...
Click to collapse
My issue was cause by the minfrees calculated by supercalculator (option 10). Using option 2 is ok but, still have 9-5mb free and if i open 2 apps -> one of them close itself (and like you said, swap does't help with that)... so i have to go back to sdsl 2.0 :/
coto39 said:
My issue was cause by the minfrees calculated by supercalculator (option 10). Using option 2 is ok but, still have 9-5mb free and if i open 2 apps -> one of them close itself (and like you said, swap does't help with that)... so i have to go back to sdsl 2.0 :/
Click to expand...
Click to collapse
Hmm, I'll try myself soon, havent noticed the problem before, I'll report back
coto39 said:
My issue was cause by the minfrees calculated by supercalculator (option 10). Using option 2 is ok but, still have 9-5mb free and if i open 2 apps -> one of them close itself (and like you said, swap does't help with that)... so i have to go back to sdsl 2.0 :/
Click to expand...
Click to collapse
Ok I just resupercharged my phone running miroslav's rom, and I did see your problems, I fixed it downloading busybox installer and using busybox version 1.18.2 and it will detect your minfrees.
Also updated OP with this info and the patched services.jar files.
delsus said:
Ok I just resupercharged my phone running miroslav's rom, and I did see your problems, I fixed it downloading busybox installer and using busybox version 1.18.2 and it will detect your minfrees.
Also updated OP with this info and the patched services.jar files.
Click to expand...
Click to collapse
I did this, but when i run the script for second time to confirm if it worked, it says:
Launcher is DIE-HARD! ie. SUPERCHARGED
but after says:
OOM Grouping Fixes ARE NOT in Effect
...
Current values DON'T MATCH Prior SuperCharge!
this means that didn't worked???
I use miroslav last update 20/05/12
arperalta3 said:
I did this, but when i run the script for second time to confirm if it worked, it says:
Launcher is DIE-HARD! ie. SUPERCHARGED
but after says:
OOM Grouping Fixes ARE NOT in Effect
...
Current values DON'T MATCH Prior SuperCharge!
this means that didn't worked???
I use miroslav last update 20/05/12
Click to expand...
Click to collapse
Did you use busy box installer to install busy box or are you just using the version pre installed? The CM9 one will not work with V6.
Sent from my LG-GT540 using XDA
delsus said:
Did you use busy box installer to install busy box or are you just using the version pre installed? The CM9 one will not work with V6.
Sent from my LG-GT540 using XDA
Click to expand...
Click to collapse
I used busybox installer to get the version 1.18.2
arperalta3 said:
I used busybox installer to get the version 1.18.2
Click to expand...
Click to collapse
Using root explorer check /system/etc/init.d and see if there is a supercharger script in there.
If not try supercharging again, reboot and check, if its still not working find the 99supercharger.sh script and select "run on boot" and reboot, it should work after this.
delsus said:
Using root explorer check /system/etc/init.d and see if there is a supercharger script in there.
If not try supercharging again, reboot and check, if its still not working find the 99supercharger.sh script and select "run on boot" and reboot, it should work after this.
Click to expand...
Click to collapse
thanks, the script is in /system/etc/init.d, i will try to run the script with the option "run on boot" in script manager later
arperalta3 said:
thanks, the script is in /system/etc/init.d, i will try to run the script with the option "run on boot" in script manager later
Click to expand...
Click to collapse
Before you select "run on boot" just try to supercharge again, something could have messed up a little when you applied the minfrees, init.d scripts should run on boot anyway.
delsus said:
Before you select "run on boot" just try to supercharge again, something could have messed up a little when you applied the minfrees, init.d scripts should run on boot anyway.
Click to expand...
Click to collapse
weird weht i run the script in the end it says that everything is ok and active, but when i reboot and clean davilk chache and run again, it says that isnt ok
I have applied V6 Supercharge on this IceCreamSwift ROM. If I do Wipe Data/Factory Reset, do I need to apply V6 again?
Yes
Q&A for [ROM][GPL]Clean_Cm_7.2[26-05-2014]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Possible bug
First of all: Awesome ROM! Never knew CM 7.2 could be this fast and stable!
Second: I've possibly found two bugs:
1, Entering "Settings/CyanogenMod Settings/Lockscreen settings/Delay and timeout" always cause a FC.
Always.
Have tried rebooting and shutting down but the FC remain.
2, Power button does not activate lockscreen, it only shuts the screen off. Pressing power button again or home button will go directly to home screen. The only way to activate lockscreen is to let screen timeout.
Have tried different screen locks but nothing makes power button behave differently.
I've searched around in setting for a way around this but so far unsuccessfull.
Maybe the two issues are related.
And now some requests:
* A big button keyboard? Stock was good with big buttons for my sausage fingers.
* Ability to easily add foreign language keyboards (not system language) and dictionaries.
* Remove delete thread confirmation in messages.
* Remove confirmation when enabling storage by USB connection.
* Ability to easily add sounds without trying to find the setting for each event. Still haven't found out how to change the alarm sound...
I'm not really sure what is causing your problems as I never faced these issues. My suggestion is the following.
1. Reboot to recovery
2. Format system
3. Wipe data&factory reset
4. Install Rom
5. Reboot
6. Reboot again
I take it, that you did not change the Rom package?
Wunder_luftmjuk said:
* A big button keyboard? Stock was good with big buttons for my sausage fingers.
* Ability to easily add foreign language keyboards (not system language) and dictionaries.
Click to expand...
Click to collapse
I left it to the user to download and choose a keyboard on their own. There are plenty in the playstore
* Remove delete thread confirmation in messages.
Click to expand...
Click to collapse
Hm, not really something I would personally enjoy, but maybe
* Remove confirmation when enabling storage by USB connection.
Click to expand...
Click to collapse
Trust me, I tried that one, but couldn't get it to work. I even tried copying the function of the xposed module..
* Ability to easily add sounds without trying to find the setting for each event. Still haven't found out how to change the alarm sound...
Click to expand...
Click to collapse
This is fairly easy, just drop the sounds into /system/media/audio/alarms
Our create a folder structure like media/sounds/alarms on your sdcard.
I hope that helps.
Sorted
Wooaarr said:
I'm not really sure what is causing your problems as I never faced these issues. My suggestion is the following.
1. Reboot to recovery
2. Format system
3. Wipe data&factory reset
4. Install Rom
5. Reboot
6. Reboot again
I take it, that you did not change the Rom package?
I left it to the user to download and choose a keyboard on their own. There are plenty in the playstore
Hm, not really something I would personally enjoy, but maybe
Trust me, I tried that one, but couldn't get it to work. I even tried copying the function of the xposed module..
This is fairly easy, just drop the sounds into /system/media/audio/alarms
Our create a folder structure like media/sounds/alarms on your sdcard.
I hope that helps.
Click to expand...
Click to collapse
Thank you for the help!
The "Delay and timeout" setting kept getting FC, until I went into security setting and disabled all security (pattern, pin, e.t.c.).
After that there was no more FC, and I could change the settings in "Delay and timeout". This also fixed the other "bug" which was power button not locking screen. Subsequently I could again change back security settings to pattern.
The other things I can live with! :laugh:
B.t.w. do you know any kernel that supports adaptive undervolting/overvolting combined with underclocking/overclocking? Also, is there any better governor than "ondemand"?
Suggestions for task killers? Many recommend Greenify but it won't run on android 2.3.x.
My aim is to have maximum battery life when on standby, while still having good performance in times of need.
Thanks again!
Wunder_luftmjuk said:
Thank you for the help!
The "Delay and timeout" setting kept getting FC, until I went into security setting and disabled all security (pattern, pin, e.t.c.).
After that there was no more FC, and I could change the settings in "Delay and timeout". This also fixed the other "bug" which was power button not locking screen. Subsequently I could again change back security settings to pattern.
Click to expand...
Click to collapse
I will dig out my old mini and see if I can reproduce that bug. I never used any security pattern, so that might be the reason I never had any trouble.
B.t.w. do you know any kernel that supports adaptive undervolting/overvolting combined with underclocking/overclocking? Also, is there any better governor than "ondemand"?
Suggestions for task killers? Many recommend Greenify but it won't run on android 2.3.x.
Click to expand...
Click to collapse
I don't think that there is a kernel that supports custom uv for the galaxy mini. However I found that the ondemand governor works very well. I could never really complain leaving it on 600 mhz. I have to admit though that it is an old phone, so don't expect any wonders .
My battery backup was always a minimum of 2 days, but I don't do any gaming. I used my phone as a phone... ( And a bit of music and internet).
Taskkillers are generally a bad idea, as they will just cause a cat and mouse game between them and a dodgy app. I'm not sure if the xposed module (I think the name is something with service disable) was backported to gingerbread. Anyway I never used it and if you want to try something maybe go for "auto start disabler free" from the playstore. That is what I used.
I hope this helps to enjoy your mini a bit more
New bug
OK I guess I have to play around with settings and apps to see how battery life can be extended.
B.t.w. I found a new bug: Camera shutter sound can't be disabled. Even when turned off in CM settings the camera will still play the click.
This is the best rom i have been used
its light, fast, and very stable.
thats what i want
I have 2 questions,,is this rom for galaxy mini gt-s5570..and can i flash over jellybean rom with full wipes,or do i have to revert to stock first?
blueangel4ever said:
I have 2 questions,,is this rom for galaxy mini gt-s5570..and can i flash over jellybean rom with full wipes,or do i have to revert to stock first?
Click to expand...
Click to collapse
you can just wipe and then flash this rom..
i'm from jelly bean rom too, and i'd do that
Damn man! Your ROM is completely stable, really like it a lot .. I personally recommended this theme http://forum.xda-developers.com/showthread.php?t=1499191 to you guys cause it is looks PERFECT to combine with the HOLO Launcher by Mobint, if you guys confront with lagging issue, just use this setting (Setting > CyanogenMod setting > Performance > CPU Setting & select Governors choose to PERFORMANCE and set MAX CPU Frequency to 806 MHz & reboot
ICS Theme that I found
This theme i found on xda is a great companion with this rom and HOLO Launcher
Bootsplash
Can I flash a "bootsplash.zip" in this ROM?
Make a backup first and then try...
Next time try to ask in a nice way and I might test it for you...
Wooaar? Its seems I can't flash the "bootanimation.zip" [installation aborted]
S5 bootanimation that I dig from xda website
you should reconsidered to place back the GINGERBREAD "Zombie ART" picture as it will brings an original ROM feels ... and sorry for asking that way the other day, it was a joke, sorry dude .. btw you did really a good job
Since when is a boot animation flashable anyway? You should just put it into system/media.
But I also deleted the script that executes the boot animation from /bin, so you would have to replace that as well.
I will not put the zombie art back in, as it is of no use, but just steals space.
Already tried to put it at system/media, but didn't works .. tell me about the script please? how to replace it
and take a look at this dude http://forum.xda-developers.com/showthread.php?t=2708316
This is indeed a flashable zip. Two things come to my mind.
1. Your recovery simply doesn't like the zip. Which version are you using?
2. Your zip is broken. Maybe the download did not finish?
In either way you have to replace the bootanimation binary in /bin. You can grab it from any rom, replace it and give it the proper permissions. Our you wait till I come back home and upload it for you.
I use yagya CWM 5.0.2.8 Touch recovery and indeed I finished the download 100% using IDM .. really hope you can help me .. thanks btw
Ok, as I have no power for today and my laptop is empty I quickly patched something up in my phone. I'm not sure if that is going to work...
Give it a shot and let me know.
Flash via recovery.
Wooaarr said:
Ok, as I have no power for today and my laptop is empty I quickly patched something up in my phone. I'm not sure if that is going to work...
Give it a shot and let me know.
Flash via recovery.
Click to expand...
Click to collapse
Installation complete but still blank screen & about the binary you ask me to grab it on another rom, you mean any rom?? including other phone rom?? as I do not download any custom rom for Galaxy Mini other than yours & my internet is not as fast as light tho, could you upload the binary script?? then replace it using root explorer right? then what is the proper permission to put on that binary script later?