Build.prop Performance Tweaks.

Build.prop Performance Tweaks. - Motorola Triumph

Hey everybody, just wanted to share the below build.prop performance tweaks. I have been using them for some time now trying different values to see what works the best. From what I have been able to tell any difference made using these tweaks is most noticeable using Stock or a Stock based Roms. Performance wise I would not expect to find the Holy Grail within these lines but they do seem to make a difference and can help with a few minor annoyances. Feel free to test them out and let everyone know what you think, at your own risk that is.
General Performance
debug.sf.hw=1
Edit existing line,
dalvik.vm.heapsize=48m
Saves power
ro.ril.disable.power.collapse=1
pm.sleep_mode=2
windowsmgr.max_events_per_sec=60
wifi.supplicant_scan_interval=180
*If you don’t keep Wi-Fi active lowering the value below the default of 90 seems to make Wi-Fi connect faster after being turned on but will consume more power if turning Wi-Fi off has been forgotten when not in range of a known network.
ro.mot.eri.losalert.delay=1000
*Should smooth out disconnects and reconnects, saving battery. Seems to brake tethering with CM7, let me know if anyone else experiences this issue.
Raises quality of images
ro.media.enc.jpeg.quality=90
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
Increased Media & Streaming Performance
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960 net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
*Note: I don't know why but the forum is placing spaces in the above lines that are not there. The spaces are not present when I edit and have even tried retyping them in Word and then pasting the lines in but it still shows the spaces after saving, kind of frustrating. The ends for the above lines should all be the same ending values for each line (=4096,87380,256960,4096,16384,256960). I don’t know why but for whatever reason anytime I save the post the spaces appear.
Disable error checking (Should speed things up a bit)
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
Disable sending usage data
ro.config.nocheckin=1
To make the phone ring faster when dialing out
ro.telephony.call_ring.delay=0
Disable black screen issue after call (Thanks to Whyzor for finding why looking into the other tweaks)
ro.lge.proximity.delay=150
mot.proximity.delay=150
Disable USB Debugging icon from Status Bar. (Just the Icon, debugging remains enabled.)
persist.adb.notify=0
Improve 3g data speeds
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.enable.3g.prefix=1
ro.ril.hsdpa.category=20
ro.ril.hsupa.category=6
ro.ril.hsxpa=3
There is some debate on the effectiveness of these lines, see comments below. If you have used the 3g script put out by the developer of theV6 Turbocharger script then they have already been applied to your device. It may just be in my head but why I haven’t seen any difference in speed tests YouTube definitely seems to display much faster, especially the thumbnails on the startup page after opening the App.
Next few can be found in the CM7 Performance settings but am including them in case someone would like to use them on another Rom like Miui.
Lock Home Screen into memory
ro.HOME_APP_ADJ=1
Use Jit (Dalvik just-in-time compiler)
dalvik.vm.execution-mode=int:jit
Enable Surface dithering (Improves image quality at the cost of performance)
persist.sys.use_dithering=1
Allow purging of assets (System can free more Ram when needed)
persist.sys.purgeable_assets=1
Disable animation for faster startup
debug.sf.nobootanimation=1
To apply any of the above Tweaks you will need a File Explorer with Root Permission. I use Root Explorer so the below steps are assuming Root Explorer is being used. This can also be done using ADB or QtADB; if ADB would be preferred in place of a File Explorer then you probably do not need directions for doing so. You will find instructions for using the QtADB interface below. It is also important to check that any of these lines have been included with your Rom.
1, Navigate into the system folder.
2, Mount the folder as R/W by tapping on the Mount R/W tab found at the top of the screen.
3, Long press on the Build.prop file and select open with text editor.
4, Add desired lines at the bottom of the script.
5, Tap menu key and select save and exit. The original Build.prop will be saved as Build.prop.bak.
6, Save the file in safe place just in case you would like to switch back
7, Reboot!
Please note that on occasion a 2nd reboot was required for the tweak was applied, USB debugging notification for example. Unless noted I have not had any issues with these lines breaking anything. With that said I also wipe both the Dalvik and Cache Partitions when performing the reboot.
This can also be done very easily using QtADB for those who are not familiar with ADB. QtADB can be installed in a few minutes by following the directions provided in the link below.
http://androidforums.com/triumph-all-things-root/494579-adb-gui-noobs.html
Once installed among many other very useful features this will give you the ability to just drag and drop the Roms Build.prop file onto your computers desktop, open the file in notepad or on other text editor, add the desired lines and then drag & drop the modified Build.prop file back into the system directory on the Triumph and reboot the phone all on your computer and without actually touching the device.
Before giving more details on how to use QtADB for the purpose of modifying the Build.prop having ADB in some form or another can be very helpful in general. One example is that after updating to CM7 one of my favorite Apps would FC when started. I was able to do a logcat with ADB and send it to the developer of the app. Based on the information provided in the logcat the developer was able to fix the issue in the next release. Anyway it’s very simple so here we go,
1, select /system/ from the dropdown outlined above in Red.
2, Drag and drop the Build.prop file highlighted Blue into the adjacent area on the left, follow the blue arrow. I have desktop selected for easier navigation but ware on the computer the file is moved does not matter as long as you remember where the file has been moved. Changing the location the file is saved is as easy as selecting the directory from the dropdown like was done with the Red outlined box in the first step above.
3 open the build.prop file now located on your computer inside notepad or another text editor, add the lines you would like to use at the end of the text file and then save. In notepad you may need to select Word Rap from the format tab from the menu at the top of the Notepad Window for the file to display correctly. I use notepad ++ and never have issues with the file displaying incorrectly. Would highly recommend making a copy of the original build.prop before editing and keeping in a safe place before editing the file.
Notepad++ can be downloaded here,
http://notepad-plus-plus.org/download/v5.9.8.html
4, once we have made our edits it’s time to move the modified file back to the Triumph. Drag and Drop the modified Build.prop back into the devices system folder. Follow the blue arrow from the below example.
5, after the file has been moved back into the system folder select the Shell tab outlined in the black box.
6, Type reboot into the command line and your Triumph will now reboot using the modified Build.prop. Please note that on occasion a 2nd reboot was required for the tweak was applied, USB debugging notification for example. Unless noted I have not had any issues with these lines breaking anything. With that said I also wipe both the Dalvik and Cache Partitions when performing the reboot. If you would like to wipe caches just type "reboot" recovery into the command line.
I also came across this App for editing the build.prop. I don't have much experience with the App but if anyone would like to check it out,
https://market.android.com/details?id=com.joeykrim.buildpropeditor

Thanks for posting this, but you should know that build.prop entries are highly rom specific. So what works for one rom might not do anything in another rom. That applies even when both roms are, for example, Froyo. The worst thing that can happen is that your entries end up doing nothing. For example, for the proximity sensor, only one of those would do anything on your device (if either one even worked). I think ro.lge.proximity.delay is for LG phone roms. The LG optimus V has many ro.lge entries. You should also verify that the build.prop entries are being saved at all. With the Optimus V, the kernel would overwrite some of the entries after the build.prop values were read in. To see what your final values are, open adb shell or terminal emulator and type in "getprop".
I'm still trying to decide between a modified stock rom and miui rom based purely on batter life. I've been trying to tweak values on both, but nothing seems to change. After overclocking and undervolting, build.prop tweaks, blocking apps from using data, and streamlining the roms, I still get ~3% loss per hour on idle on both roms. I used to get 1% on the optimus v.

Thanks, the ADB trick is very helpfull. The battery thing is tough.

freddysam said:
I'm still trying to decide between a modified stock rom and miui rom based purely on batter life. I've been trying to tweak values on both, but nothing seems to change. After overclocking and undervolting, build.prop tweaks, blocking apps from using data, and streamlining the roms, I still get ~3% loss per hour on idle on both roms. I used to get 1% on the optimus v.
Click to expand...
Click to collapse
That 3% loss is about what I get on the gb/ics based roms when wifi is enabled and left on. Make sure that you don't have wifi or bt enabled if you're using one of those roms and want your phone to deep sleep.

Has anyone tried these on CM7?
I wanna try these out, but it's my gf's phone and I really dont wanna **** it up xD

xLoveHateLegend said:
Has anyone tried these on CM7?
I wanna try these out, but it's my gf's phone and I really dont wanna **** it up xD
Click to expand...
Click to collapse
I have put the majority of these tweaks into a script that runs on boot.
The script can be found here,
http://forum.xda-developers.com/showthread.php?t=1609729
The Build.prop script or Hollyname script as I like to call it is posted below the 108 script. If you follow the instructions it will not make any permanent changes to the build.prop and can easily be applied or disables. Also yes I have been testing these on CM7 for the most part.

Related

Change Your Screen Resolution on HTC Evo 4g

In this post I'd like to share a small bit of Android information with you. I've discovered it while looking around at the build.prop file and did some research on it, and it turns out to be a pretty cool and powerful feature. Of course, seeing as this requires root you can probably already guess that it involves some more-than-consumer level risk, so anything you do here is your responsibility. This is not a tweak for a fairly novice user. You will need some basic knowledge on command line terminal and how to copy/edit files. I will be assuming you know how to setup and run ADB, and how to execute it and work with it in command prompt.
What's this mod do? Basically it changes your resolution (not really, but for simplicity sake we'll say it does) to a higher pixel density. What this means is everything on your screen will look smaller as if you changed your resolution on your PC to a higher setting. Now obviously we don't want to increase this too much or it will make our screen look bad and be impossible to read things, so I recommend you stick with the settings I have and only tweak it if you're daring.
Now for setup:
1: You require root access for this to work, so make sure you have it prior to doing anything else.
2: Next you will need to get your build.prop file from the /system directory. An easy (and free) way to do this is to use Astro file manager. Open up Astro, navigate to /system/ and copy the build.prop file to the sdcard.
3: Hook the phone up to your PC and enter USB Mass Storage mode. Open the drive on your computer and copy the build.prop file to the desktop.
4: IMPORTANT: make a second copy of this file, and rename it to: build.prop.BAK - accept the change to filetype and leave it alone for now.
5: Open up build.prop using notepad. Once its open you'll see a whole ton of text assuming you have Word Wrap enabled. Press Control + F and type in "density" then press enter.
6: Close out the search menu and find the number "240" to the right of "density"
7: Change the number from 240 to 200. Save the file and close notepad. (Note - higher numbers means bigger text/objects, smaller numbers means smaller text/objects allowing you to fit more on the screen)
8: Put your phone back into PC Mode, and then enable USB Debugging in Settings->Applications->Development
9: At this point I assume you have ADB setup on your PC. Copy and paste the modified build.prop file into the folder with ADB, and then open up a command prompt, change directory to wherever you have ADB installed (ex: cd C:\adb\ ), and type in "adb devices" without the quotes to start ADB and make sure your device is configured properly
10: Now you must push the modified build.prop file to your sdcard. To do so type this in:
adb push build.prop /sdcard/build.prop
11: You should see the text indicating it successfully transferred the file. Now type in "adb shell" without quotes. You should see a $: appear. Once it does, type in "su" and it should change to a #: sign.
12: Now that you're in root access, you must mount /system as read/write to copy over the new build.prop file. To do so type this in exactly as it is, making sure to not skip any spaces or use wrong letters/characters:
mount -o remount,rw /dev/block/system /system
You should see the line repeated and that means it went ok. If you get anything else like an error, somethings not right with the text you entered. Go back and double check it.
13: Now we'll copy the file from the sdcard to the system directory to overwrite the old build.prop file:
cp /sdcard/build.prop /system/build.prop
Again, you should see the line repeat below to confirm it copied it successfully. You can now reboot the phone to make the changes happen (note: for a speedy reboot, simply type in "reboot" from the #: prompt, this will drop you out of root shell and do an automatic reboot of your phone pretty neat)
Once your phone is booted back up you should notice some pretty significant changes in appearance. Everything will look smaller much akin to the changes you see on your desktop PC when you increase the resolution from say 800x600 to 1600x1200. In case you want to change it back to the old look, simply re-trace your steps using the original build.prop file, with the pixel density set to 240 instead of 200.
Screenshots for comparison. Note how lines of text are fully exposed in the new screenshots compared to the old ones, where it has to scroll/cut off text in App names etc:
http://forum.androidcentral.com/motorola-x-roms-hacks/32035-how-resolution-tweak-req-root.html

Or you can save a whole lot of time and effort and use this app. http://www.xda-developers.com/android/lcd-density-changer-application-v3-0-released/

I think that is pretty sweet bro!! Great finding
Sent from my PC36100 using Tapatalk

njfoses said:
Or you can save a whole lot of time and effort and use this app. http://www.xda-developers.com/android/lcd-density-changer-application-v3-0-released/
Click to expand...
Click to collapse
Been using this for a few days now. It works great. They should have released the Evo with the higher resolution from the start.

Looks great in my opinion. I lowered just slightly to 220 and i used RootExplorer to just change the Build.prop file.

Shouldn't this be in general? This is like dpi in windows lol... not resolution

rawdikrik said:
Looks great in my opinion. I lowered just slightly to 220 and i used RootExplorer to just change the Build.prop file.
Click to expand...
Click to collapse
yeah, root explorer is fantastic. it even creates a backup for you after you edit the file.

The interesting part about this is, I made a thread about the density change back when the EVO first launched and nobody cared lol

Just changed to 200 with the aforementioned app, the only problem I have is the main status bar and most of the popup menus and stuff look like crap. Hoping we can find some higher resolution (or whatever) pieces to use. Might be because I'm using Manup's theme.

bdoople said:
Just changed to 200 with the aforementioned app, the only problem I have is the main status bar and most of the popup menus and stuff look like crap. Hoping we can find some higher resolution (or whatever) pieces to use. Might be because I'm using Manup's theme.
Click to expand...
Click to collapse
i noticed that too....so i just went to like 215. 200 was looking good though

ro.sf.LCD_Density=240
Is that the proper value to change in root explorer?
Right below it, there is another value of 160, that's why I ask. I'm on an Evo
Poor resolution has always bugged me. On such a big screen, that number of pixels really isn't enough. This will be a great mod, just don't wanna mess it up.
Thanks.

see there's an easier way to do everything, by that i mean there is an app for that, lol.

scottspa74 said:
ro.sf.LCD_Density=240
Is that the proper value to change in root explorer?
Right below it, there is another value of 160, that's why I ask. I'm on an Evo
Poor resolution has always bugged me. On such a big screen, that number of pixels really isn't enough. This will be a great mod, just don't wanna mess it up.
Thanks.
Click to expand...
Click to collapse
The line below it (With the value of 160) has a # in front of it as that is the default value if none specified. Change the 240 to 200 or 220 or 210 or 190 etc depending on your preferences. Again, appelflap has an awesome application to easily do this for you and it provides a boot monitor as well that will check to make sure you can see the screen, and if you can't it will revert back to default setting in case you mess something up. It costs approximately $1 and is well worth it.

On my evo I am using the app and I set mine to 180. Everything looks fine so far. I don't recommend using it with the sense launcher at this level though.
Sent from my PC36100 using XDA App

Appreciate all the feedback. When it comes to system tweaks like this, I've always preferred to do them manually. Makes it easier to keep track of changes, and, if you know what's goin on 'behind the scenes'. Even with winmo, I always would opt for tweaking via registry editor, rather than some blind, hands-off tweak app.
Thanks all, though.
Edit: ok, foot in mouth. So I opened root explorer, found build.prop, opened it clicked the mount R/O toggle, but can't seem to edit it no matter what. NVM, found editor
Also, I checked out the app on the market, looked at comments and saw lots of people say that density broke certain apps, and can't get back to normal, broken phones, blah blah blah
Anyone speak to this?

Exposes lame apps
Worked great on rooted EVO running CM6.2.
Need to increase the power of my bifocals now!
Also exposes lame apps that display set screen resolutions, such as WeatherChannel. Poopnoodles!

Very cool find, not one I will be keeping though. The taskbar icons get a bit blurry, and the widget/icon spacing looks ugly.

njfoses said:
Or you can save a whole lot of time and effort and use this app. http://www.xda-developers.com/android/lcd-density-changer-application-v3-0-released/
Click to expand...
Click to collapse
Just tried that. Was able to make a few changes with no problems. As soon as I tried to go back to the stock settings my phone would no longer boot past the white EVO screen. Doing a restore now
And of course the restore isn't working properly for some reason. Argh.

yeah
Yeah, I read the thread by Appleflap, about his app, and it really sounds like there are a lot of issues from doing this (at this point), some of which cannot be recovered from. And at the very least, there are apps and icons that won't scale properly, and there's no fix for that but to find new ones (from the horses mouth).
Things to be worked out by some real sharp devs.

I'm not totally convinced that this makes things anything beyond just smaller. I've been testing this a various resolutions and am not sure it really adds any new pixels...aren't "pixels" more hardware related? If it were just a software thing wouldn't everyone do it?

[Script][Guide] V6 Supercharger by Zeppelinrox or how to kill lags in ROMs! U9RC7!

This script is made by Zeppelinrox all credits, thanks and donations should go to him for his amazing work! here is his original thread [Script]V6 SuperCharger! The ONLY Android MEMORY FIXER! 3G & KAK!
ICS users should check this page for GB follow the guide below
most recent supercharger files are found here
--------------------------------------------------------------------------
Recommended settings for Sense 3.5 ROMs:
- Build.prop + integrate
- Balanced 512HP settings (number 6. Ledded)
- BulletProof launcher
- DON'T INSTALL Nitro Lag Nullifier
- Kickass kernelizer + IO tweaks
--------------------------------------------------------------------------
I will not be updating this guide when new versions are out simply because they never stop the general guidelines below should apply on newer versions, i will update only if we have a major change
--------------------------------------------------------------------------
For smooth sense 3 launcher check here [FIX] Ultra & Super, Liquid Smooth Rosie for Sense 3 & 3.5 ROMs
Many of us complain about launcher lags or frame rate drops, the launcher itself might be 60fps smooth but once you start using your device and loading it, sudden lags start creeping up.
A lot of this is due to the way android handles multitasking, Zeppelinrox’s script has been always around but I’m sure many of the users didn’t hear of it, so in order to lessen the pressure on our favorite chefs, i thought i should post a specific guide specific to the Desire HD users
What the script does is tweak android memory minfrees and applications priority, it attempts to insure lag free operation of the launcher and also prevents launcher redraws
Thankfully our device have a generous amount of RAM so it shouldn't have side effects on battery etc, we will still have apps running in the background just not as busy and at lesser priority then the launcher, It's not a task killer app
I won’t go into technical details which are better explained in Zeppelinrox's OP let’s just say the results will speak for themselves, you can easily control what the script is doing and you can undo it at anytime
V6 Supercharger is currently in beta for the U9 version and has been expanded, it now it includes a kernel tweaker and 3G speed booster too, here is a step by step guide, remember this script is universal it should work on any android, in my case I tried it on ARHD v6.1.1 official sense 3.0
Make sure you have Root, init.d scripts enabled at boot, latest busybox and do a nandroid backup
Download Script Manager https://market.android.com/details?id=os.tools.scriptmanager&feature=search_result
Download the scripts V6_SuperCharger_for_Android-Update9_RC6.9.sh.pdf and KickAssKernelizer_Tweaks_Installer_Update_3_RC6.sh.pdf from this post http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021 rename them to V6_SuperCharger_for_Android-Update9_RC6.9.sh and KickAssKernelizer_Tweaks_Installer_Update_3_RC6.sh
Place the script files in an easily accessed folder on your SD card
Open script manager and then press menu > more > advanced options > config and tick “browse as root”, allow root once requested
Browse to the scripts location and click on V6_SuperCharger_for_Android-update9_RC6.9.sh, make sure to tick “run as root” but don’t tick “run at boot” otherwise we will face issues, the script runs at boot automatically, press run
Once loaded follow the onscreen instructions, select text speed (1 is the fastest and hidden 0 for super fast), the script will ask for init.rc integration which is a further measure to insure the launcher priority will stick, init.rc method has risk of boot issues, so insure you have a backup and proceed.
Once done loading the script will detect that the device has 620MB RAM and suggest custoomizer calculator settings, you can choose your own preference from option 2 to 9, the insured free memory is the last number in the list of mem frees, the bigger the number the less active running apps in the background, it will also shut down apps based on priorities, like explained in the list of options for more multitasking you can choose less minfress by going for the 512HP options, please don't complain about multitasking gone since you can control how much minfrees you want! otherwise if you choose to trust the supercharger calculator select option 10 and supercharger will apply the best settings for your device available RAM
For further improvements select option 20 (nitro lag nullifier) and enable it warning! i suspect that this setting increases "LCD ghosting" at high frame rates
Press back and kill the script, browse to the scripts location and click on KickAssKernelizer_Tweaks_Installer_Update_3_RC6.sh, make sure to tick “run as root”, press run. The script will request permission to Install and then to modify the IO scheduler and warns for possible bootloops, in the case of ARHD and ER3BUS ROMs I had no issues and I selected yes, you can opt for no, the rest of the tweaks will still be implemented
Once done, close the script and reboot the device, you can select Superclean option 29 (wipe caches and reboot) for clean operation, now enjoy smooth lag free launcher and android
The script will always let you know whether the launcher is locked in memory or not, if locked it will advice against locking the launcher in memory in order to enable priority tweaks, in sense ROMs its usually left unlocked, but some chefs lock it, in CM ROMs you unlock using the "Lock home in memory" option, some third party launchers have an option in settings.
If launcher's new DIE HARD or BULLETPROOF state doesn't stick after restart (you can tell by running the script) then go to option 26 (Driver Options) and set the method to build.prop, you can choose init.rc integration which will insure the priorities will stick but as warned there is a risk of bootloops. You can also disable the script boot animation and change the text speed again from this menu.
Otherwise you can leave it, the minfrees will still be in effect even if locked, but not the priorities.
At any time you can undo the script tweaks, by running the surpercharger script and select options 14 and 15, unkernelizer and unsupercharge you can also check this in case you run into bootloops due to kernelizer
You can also try zeppelinrox ‘s 3G turbocharger and Die-Hard Battery Calibrator scripts http://forum.xda-developers.com/showthread.php?p=18703418#post18703418
The details above are simplified for noobs like me, much more info can be found in Zeppelinrox‘s OP

hamdir said:
Many of us complain about launcher lags or frame rate drops, the launcher itself might be 60fps smooth but once you start using your device and loading it, sudden lags start creeping up.
A lot of this is due to the way android handles multitasking, Zeppelinrox’s script has been always around but I’m sure many of the users didn’t hear of it, so in order to lessen the pressure on our favorite chefs, i thought i should post a specific guide specific to the Desire HD users
Thankfully our device has a generous amount of RAM, what the script does is tweak android memory minfrees and applications priority, it attempts to insure lag free operation of the launcher and also prevents launcher redraws, I won’t go into technical details which are better explained in Zeppelinrox's OP let’s just say the results will speak for themselves, you can easily control what the script is doing and you can undo it at anytime
V6 Supercharger is currently in beta for the v8 version and has been expanded, it now it includes a kernel tweaker and 3G speed booster too, here is a step by step guide, in my case I tried it on ARHD v6.1.1 official sense 3.0
Make sure you have Root and make a nandroid backup
You should have Busybox v1.8.2 or less, the script has issues with Busybox higher than 1.8.2, you should downgrade using busybox installer from the market https://market.android.com/details?id=com.jrummy.busybox.installer&feature=search_result
Download Script Manager https://market.android.com/details?id=os.tools.scriptmanager&feature=search_result
Download the scripts V6_SuperCharger_for_Android-update9_beta_6.1.sh.txt and KickAssKernelizer_Tweaks_Installer_Update_3_test_5-OPTIONAL_IO_TWEAK.sh.txt from this post http://forum.xda-developers.com/showpost.php?p=15948434&postcount=1127
Place the script files in an easily accessed folder on your SD card
Open script manager and then press menu > more > advanced options > config and tick “browse as root”, allow root once requested
Browse to the scripts location and click on V6_SuperCharger_for_Android-update9_beta_6.1.sh.txt make sure to tick “run as root” but don’t tick “run at boot” otherwise we will face issues, the script runs at boot automatically
Once loaded follow the onscreen instructions, select text speed (1 is the fastest) and let it proceed, the script will detect that the device has 620MB RAM and suggest the 768HP settings , select option 8 (super 768HP aggressive), you can go for more aggressive minfrees with option 9, this basically means the device will always have around 250MB of free memory which means less active running apps in the background, it will shut down apps based on priorities, it will insure 150MB for the launcher in the third slot
For further improvements select option 17 (nitro lag nullifier) and enable it
The script will always let you know whether the launcher or locked in memory or not, if locked it will advice against locking the launcher in memory in order to enable priority tweaks, in sense ROMs its usually left unlocked, but some chefs lock it, you can unlock by quitting the script and adding ro.HOME_APP_ADJ=0 to the top of the build.prop file in the system folder (using root explorer) otherwise you can leave it as is, in case of ARHD 6.1.1 the launcher is locked by default, the minfrees will still be in effect even if locked
Press back and kill the script, browse to the scripts location and click on KickAssKernelizer_Tweaks_Installer_Update_3_test_5-OPTIONAL_IO_TWEAK.sh.txt, the script will request permission to modify the IO scheduler and warn for possible bootloops, the script advices noop or deadline scheduler, in the case of ARHD6.1.1 I had no issues and I selected yes, you can opt for no the rest of the tweaks will still be implemented
Once done, close the script and reboot the device enjoy smooth lag free Sense 3 launcher and android
At any time you can undo the script tweaks, by running the surpercharger script and select options 13 and 14, unkernelizer and unsupercharge
You can also try zeppelinrox ‘s 3G turbocharger script http://forum.xda-developers.com/showpost.php?p=15948434&postcount=1127
The details above are simplified for noobs like me, much more info can be found in Zeppelinrox ‘s OP http://forum.xda-developers.com/showthread.php?t=991276
all credits, thanks and donations goes to Zeppelinrox for his amazing work!
Click to expand...
Click to collapse
thx for sharing my friend

How do I install version Busybox v1.8.2? I only find 1.14.3 and above.
I tried manually install but I dont understand.
I hope to hear from you soon

Thanks for simplifying. I see hime everyday and I don't get these walkthrough's lol

Amazing guys!! Really impressive!!
Installed on RCMix Runny 1.3 sense 3.5 and it works...a lot!!;-)
Is it right use this script on a sense 3.5?
Just one thing...now my ram is ALWAYS up to 230/250 just like on the first boot, and the smoothness it's amazing..really close to perfection..I've just experienced one weird thing..when you scroll the homescreens continuously, sometimes there's a jump between pages, from page 1 to 3 for example..I've tried to clean sense data and run wipe dalvik, but this weird issue is still here..maybe the script needs some time to work properly?
Thanks for sharing this masterpiece in Android;-)
Inviato dal mio HTC Desire HD usando Tapatalk

Glaxo said:
How do I install version Busybox v1.8.2? I only find 1.14.3 and above.
I tried manually install but I dont understand.
I hope to hear from you soon
Click to expand...
Click to collapse
latest requirement is Busybox 1.18.2 OR LOWER

nice tool, thanks for sharing
OP writes 1.18.2 or lower
---------- Post added at 03:57 AM ---------- Previous post was at 03:56 AM ----------
tingardz said:
latest requirement is Busybox 1.18.2 OR LOWER
Click to expand...
Click to collapse
only seconds before me
---------- Post added at 04:42 AM ---------- Previous post was at 03:57 AM ----------
I just tried it with RCMix3D Runny v1.2 and it's fantastic C:

Awesome! This has definitely made a noticeable difference in smoothness, thanks for sharing!

liljom said:
nice tool, thanks for sharing
OP writes 1.18.2 or lower
Click to expand...
Click to collapse
hamdir said:
[*]You should have Busybox v1.8.2 or less, the script has issues with Busybox higher than 1.8.2, you should downgrade using busybox installer from the market https://market.android.com/details?id=com.jrummy.busybox.installer&feature=search_result
Click to expand...
Click to collapse
I see 1.8.2, guide should be updated

correct version 1.18.2, typo fixed

Great, thanks for share i will try it now.

Has this script any effect on the battery?

The title says 'in any rom ', and so CM 7 works too?

Slight improvements on RCMix3D VoidU 1.1...

Thanks for this hamdir. Can't wait to try those but I have 2 questions:
1. I currently have busy box 1.19. What do we lose by downgrading?
2. Does the downgrade have to be permanent or only temp until we run the scripts and then we could upgrade again? Other apps rely on this and so I don't want to break their functionality (i.e. Titanium Backup)

Arhd 6.1.1 and unity v9 kernel and i for sure see improvments. Big thanks
Old man with Sense 40+

andreasy said:
Thanks for this hamdir. Can't wait to try those but I have 2 questions:
1. I currently have busy box 1.19. What do we lose by downgrading?
2. Does the downgrade have to be permanent or only temp until we run the scripts and then we could upgrade again? Other apps rely on this and so I don't want to break their functionality (i.e. Titanium Backup)
Click to expand...
Click to collapse
Just download 'Busybox Installer' and you can upgrade/downgrade Busybox with just one click.

lululala said:
Just download 'Busybox Installer' and you can upgrade/downgrade Busybox with just one click.
Click to expand...
Click to collapse
I know this but this wasn't my question.

reneftw said:
Has this script any effect on the battery?
Click to expand...
Click to collapse
well its not a task killer, it just tweaks the way android handles priorities and memory, you will still have apps running in the background
i didn't see any side effects especially since the DHD has good amount of RAM

andreasy said:
Thanks for this hamdir. Can't wait to try those but I have 2 questions:
1. I currently have busy box 1.19. What do we lose by downgrading?
2. Does the downgrade have to be permanent or only temp until we run the scripts and then we could upgrade again? Other apps rely on this and so I don't want to break their functionality (i.e. Titanium Backup)
Click to expand...
Click to collapse
no side effect of lesser busy box as far as i can tell, it all depends on what BusyBox features the ROM is using, but it should be fine
you can still try to run it BusyBox, but for example the built-in reboot feature in the script won't work

[ROM] [Huawei U8300] Vicky for Huawei Ideos Chat - updated 2013/feb/19

Vicky
Current: [Vicky v2.5.5] - Jul/24/2013
Lite Version: [Vicky v2.5.5 Lite v1] - Jul/24/2013
What is Vicky?
- Vicky is a mixed Gingerbread rom based on Cyanogenmod's sources stable/nightly/experimental, for now...
Some Screens
DISCLAIMER:
I'm not responsible for any damage you can do to your phone using my rom nor it is my fault your phone dumped you and loves your cat more than he loves you
Changelog
[Vicky v2.5.5]
Code:
- Slimmed a bit
- Fixed a few typos
- Updated some system apps
- Updated HoloLauncher_2.0.2
- Added Holo notifier and locker
- Adw.Launcher
- Tweaked some more
- Random bootanimation support without using apps
(just place your favorite bootanimation zip at bootanimation's folder in your sdcard)
- Modded kernel with hwuserdata support
- Replaced stock mms app with Huawei SMS/MMS app
- Huawei file explorer
- Latest huawei gb launcher
- Swap support (check Extras section for info)
- fixed problems related with changing phone settings while/after Wi-Fi was on (ex. toggles getting stuck)
- fixed layouts
- themes added
- stock dalvik cache bypassed to cache partition to grant extra space in data partition. new installed apps dalvik cache will be placed on data as usual
(if you need to wipe dalvik cache by necessity of something, in recovery select wipe dakvik cache and select wipe cache)
- Downloads cache moved to /obb (bigger partition and dont require cleanning)
- Some surprises
- Stuff i cant recall now
- Fixed a few typos
- Updated some system apps
- Updated HoloLauncher_1.0.2
- Replaced gps configs (enable internal gps in settings/location and security/gps source) - didnt noticed but since v2.0 the gps.conf was set to Portugal, now is for europe
- Fixed MagicSmokeWallpapers (now there is fog and not moving squares) -> finally no more apps to fix (i hope!)
- Tweaked some more
- Defaults settings changed - only noticed if doing a clean install, wont affect the ones already made
- Latest CM 7.2 sources for Huawei + for Samsung
- Lightly themed
- 60% Tweaked (battery, camera, network) (still no Supercharged script added)
- Increased performance
- Optimized All Apks
- Fixed some bugs
- Improved some libraries
- Improved MDPI layout
- Default kernel set to 600Mhz -> (U can choose other values)
- Original Network Operator Names -> back from the dead (If u find a problem, report)
- Battery PowerBar added
- Fixed Deskclock display size
- Crt animation on/off activated by default
- Bravia Engine added
- ICS Rotation added
- Beats Audio added -> might change that to XLoud, if it doesnt give any problem (battery drain, audio issues or force close)
- Updated APNs and fixed Optimus, Vodafone, Tmn MMS -> if anyone still has problems with the MMS, report it
- 3 Launchers (Adw, Huawei and Holo V1.0.1)
- TouchScreen, compass and battery calibrators
-> Wipes Required - Dalvik, Cache
-> Formats - Boot, System
-> Data Wiping / Factory Reset - no problems were reported by not wiping data but, if u encounter problems (bootloop, FCs, apps not working, etc). u'll need to do a wiping data + dalvik and reinstall all your apps
--> if ur apps are linked, unlink them. After flash/reboot, dalvik cache will rebuild itself with all apps info, including the linked ones. this way, wont exist conflicting doubled dalvik's
- CM 7.2 RC1 sources for Huawei u8150
- Lightly themed
- 40% Tweaked (0% Supercharged)
- Increased performance
- Screen, compass, battery calibrators
- Other Stuff i can't remember now
What do you need to install Vicky
- Vicky ->> [Current version]
- SuperSU [ Tx to Chainfire ->> [v2.82] | | old versions ->>[v1.01] |
- modded Lite GAPPS + Last Playstore for GB ->>[2016/09/22]
- Google Play Services ->>[2016/09/22]
What do you need to install Vicky Lite Version
- Vicky Lite ->> [Lite]
- SuperSU [ Tx to Chainfire ->> [v2.82] | | old version ->>[v1.01] |
- modded Lite GAPPS + Last Playstore for GB ->>[2016/09/22]
- Google Play Services ->>[2016/09/22]
Extras
- [Boot Sound Remover] -> not found
- [TSReset - Screen calibration reset]
- [Mac Address Patcher]
- [On-Screen Keyboard enabler] -> not found
- [On-Screen Keyboard enabler -> Vicky 2.5.4] -> not found
- [Huawei Keyboard] -> not found
- [Ascend ClockWorkMod Recovery 3.0.2.8]
- [Huawei ClockWorkMod Recovery 4.0.1.5]
- [Swap installer] -> Tx to Yank555
How to change ClockWorkMod Recovery
I made it simple by using the same proccess of flashing a rom. you just put the cwm zip file in your sd-card. Reboot to CWMod recovery, select "install zip from sdcard", select your new cwm zip file. After flashing, go to advanced and select "Reboot Recovery". Now you can see your new Recovery.
How to change MAC address
Method 1- unzip MacAdress.zip, go to system\etc\firmware\, open with notepad++ this file "nvram.txt", find this line of code:
macaddr=00:90:4c:14:43:26
write your own mac-address found inside the phone in the battery case, save.
go all the way back, zip META-INF and system folders with Store compression.
or just open MacAdress.zip (not unzip), go to system\etc\firmware\ and drag-and-drop to that folder ur edited "nvram.txt".
flash the new MacAdress.zip, fix permissions, reboot.
Method 2- open RootExplorer in system\etc\firmware and open "nvram.txt" with text editor, locate this line
macaddr=00:90:4c:14:43:26
and write your own mac-adress (like 11:22:33:44:55:66), save and close, reboot.
To install from stock rom you need these ones too
- [z4root]
- [rom manager]
Info
Code:
[COLOR="Red"][B]What is Working[/B][/COLOR]
Apparently almost everything
[COLOR="Red"][B]Bugs/Not Working[/B][/COLOR]
[COLOR="Red"]what are the drawbacks? The bugs that i need to live with of i update?[/COLOR]
FM Radio not working. Almost all phones that had FM Radio, updating to Cyanogenmod made them lose FM Radio because of certified drivers and other issues
Keyboard - some keys that used the double function, like the ".com" key or the "smiley" key, are stuck to using only one function, ".com" stays just "@". if u have keyboard issues (keys switched or something), flash the correct version for your phone. more info at the 2nd post.
TouchScreen calibration - it is not the best compared to the one used on u8300 eclairs, but is something almost as good.
Onscreen Keyboard - since most users use the hardware keyboard, the onscreen keyboard is purposely disabled. so if u want back the onscreen keypad (to use other soft keyboard like go keyboard or, i dont know... tswipe), just ask for a patch enabling it, otherwise i'll keep it disabled as a reminder of the keyboard issues. By request of songrak, a patch enabling the on screen keyboard is available for download, plus a Huawey Keyboard app (tx to RedDeviL). Check the Extras section.
[COLOR="Cyan"]Remember this is not an update for the stock rom, it's a new OS. [/COLOR]
Keyboard access Keys for a turned off phone
Call button + volume up + power -> turn on phone in CWM recovery
Hang up + power -> turn on phone in Bootloader mode (fastboot)
Hang up + volume up + power -> activate the huawey stock rom flashing, it will wipe everything in your phone and flash the stock rom back to phone (if you have a dload folder in your sdcard)
Flashing Requirements
- Rooted phone
- ClockWorkMod Recovery
- Rom files
- Partitioned SD-Card -> Read post 2 for more info
- 100% battery charge (in reality you just need something between 40% and 100%, but this way if u encounter problems, u'll still have energy in the phone to solve them and it will avoid a miss-install resulting from the power ended during flash)
Flashing Procedure
note: - Put the files into the root of your sd card or any other folder of ur liking.
just by my experience, i advice u to put also the dload folder at the root of ur sdcard, with just the updata.app inside. its just in case u experience something (phone not coming out of bootloader after restart or something) and this way u can go back to stock easy and start again
[Stock - 1 to 20] / [Others -> 5 to 20]
1- Install z4root and do a Permmanent Root to the phone
2- Install rom manager and open it
3- Select "flash ClockworkMod Recovery" to install the custom recovery from rom manager, choose huawei ascend recovery
4- go to "all clockworkmod recoveries" and flash a previous version of ClockworkMod Recovery, after finish, do step 3 again and go to 5. (its to avoid conflitcs with the huawey recovery and to avoid no access to CWM recovery)
5- select Reboot into recovery and do a full backup of your current rom (optional, but if u dont do it, u'll lose everything u had - if u want to go back to your previous rom)
In CWMod recovery Menu u use the trackball to go up/down (press it results in a "enter key"), the go back buttom is a go back buttom (lol) and return (enter) key is a enter
6- select wipe data/factory reset from the menu
7- go to advanced and select wipe dalvik cache
8- go to mount and storage and select format boot and format system (use the keyboard enter key to avoid selecting and entering the wrong one with the trackball)
9- Choose "install zip from sdcard" and select Vicky from the menu, go on with the process
10- Once done, again Choose "install zip from sdcard" and select gapps from the menu, go on with the process and again choose "install zip from sdcard" and select SuperSu
11- go to advanced and select fix permissions
12- go back and select reboot system now (remove ur sim card before)
the first boot it should take between 1 to 4 minutes (the phone is in bootloop if u see the animation or the boot sound restarting itself - the screen goes black and the android in a circle appears again, if it does this again and again, its on bootloop. if u dont see that it is fine (since it doesnt stay there for 15 min))
13- Calibrate screen and it will reboot as soon u finish. (read bellow if u miscalibrate screen)
14- insert the sim card before the phone enters the boot animation
15- turn on wifi, check if it is activating, if u dont use the 3G data, turn data off. Configure everything u want to be set ( like the crt animation or the buttons on the status bar or the allow unknown sources install - this one is a must), dont open link2sd nor set the cpu to 710 (or other) yet
16- reboot into recovery (long press the power button and select Reboot and Recovery mode)
17- Choose "install zip from sdcard" and select Boot sound Remover then reboot system, if u want to remove the boot sound
18- go to apps drawer, open No-frils CPU control, there should be there 2 frequencies, 245 and 600, change the 600 (it is the higher frequency the phone is working after reboot) to the value u want (dont worry, all of them were tested and none will grant problems, dont go bellow than 600, u'll slow down the phone and drain battery faster, 710 grants more performance and the battery drain is almost the same as 600), apply and grant superuser permissions
19- Open link2sd, grant permissions and select ext4.
20- Reboot
21- Install Google play Services (com.google.android.gms-7.8.95_(2113048-032)-7895032-minAPI9.apk) <- i don't know if Google PS will update itself for the most recent one (and bigger one) but it can be denied by going inside the playstore, searching for Google play Services and in the options, de-select auto-update.
22- Enjoy
(one thing, after the 1st boot and after the sim pin screen - if u have the sim card inserted -, let the phone stay a while in the touchscreen calibrator, there is chance that u need to insert the pin again and that will restart the calibration and could miscalibrate the screen. if u dont that to happen, insert the sim card before the 2nd boot)
If by any chance u miscalibrate the display - Go back in recovery mode and flash TSReset, reboot and go to Calibration app in Cyanogenmod settings
advice for a perfect install/config
- 1st boot - before calibrating screen wait till holo locker locks screen, then unlock, give a few seconds, then calibrate, this way u'll avoid the restarting of the calibration app. if, cant reach the unlock button, rotate phone
- 3rd boot - [Very important] Give 2 minutes before entering pin because file system is being changed (dalvik cache is being recreated on cache partition and if the OS is loading apps, the dalvik wont be perfectly moved)
- after selected the home launcher, you can freeze the other ones, using link2sd (selecting the launchers that you dont want, long pressing them and freeze) ou by using the applications section in settings.
p.s. u can disable the holo locker when u want to
- the boot sound is activated, i let it stay because, this way, u can see if the phone enters in boot loop after install (the music restarts). when u are done with the configs, u can delete it.
dont bypass the google apps or it will result in no-lockscreen and no receiving calls/sms bug.
(just kidding but they are really, really necessary)
any opinion, bug report, other things about the rom is welcomed to improve the rom
lol. +6k views and only one thanks

Settings
How to partition a SD-Card and how to work with Link2SD + Swap
Using this you can add more apps to your phone and keep a lot of internal memory free
[link2sd]
[XDA - sdcard partitioning]
[how to partition sdcard using windows]
[[GUIDE] Link2SD for Dummies] -> it wasnt me who named it
[[Video] How to Partition Your SDCARD using CWMod Recovery]
[[Video] Partitioning SD for Apps2sd and Swap]
[[GUIDE] Increase RAM using Swap File and Swap Partition] -> it has a text guide for Minitool partition wizard
~Values for the partitions: (as allways, its your choice to increase or decrease those values)
Swap - Max 64mb (initially i had 256mb (too much). even at 128mb and 100% swapiness, it was much. so i tested with 64mb and got the perfect partition size for swap, leaving a couple of free mb if wanted to increase swapiness)
SD-Ext - depends on the size of your sdcard and if you install lots of apps and want to link them so, minimum - 128mb
The rest is for sdcard data
Remember to backup your sdcard before partition it
----------------------------------------------------------------------------------------------------------------------------------------------------------
After flashing the rom, you'll need to calibrate battery.
use the batterycalibration app or the built-in app in CM settings to calibrate battery.
let the phone charge to 100%, wait 10-15 min, open batterycalibration, the battery values should be around 4120 and 4167mv, press battery calibration (do not unplug the phone yet). shutdown the phone, let it stay in charging mode for 5 min. reboot, check the new battery values at batterycalibration (the new ones should be between 4170 and 4270mv), let it sit there for another 5 min and, finally unplug the phone.
-> sometimes after doing the calibration, the battery 1st charge drains in a few (between 8 and 16) hours, but its normal. <-
even it drains the 1st charge, dont worry about doing a 2nd battery calibration. just do a normal charging, after one or two charging/draining cycles the battery will work properly.
----------------------------------------------------------------------------------------------------------------------------------------------------------
keyboard files for other languages
tuono in Adrenalin's thread made several keyboard installers, they work in Vicky's too, they are on the 1st page, 1st post.
u just need to download it, place it at ur sdcard, reboot to recovery, choose "install zip from sdcard", select the language file, after finish, fix permissions and reboot.
----------------------------------------------------------------------------------------------------------------------------------------------------------
GPS settings
the actual gps settings are for europe.
if u are from outside that area or u want a more specific area, u can use the fasterfix app. on its menu there are some gps servers and a custom option. by selecting it, u can write the one gps server u want (if it wasnt on the list). basically, it is just writing down the country abrv.
(france is fr, united kingdom is uk, etc) before the gps server adress.
something like this
uk.pool.ntp.org
for more info, visit http://www.pool.ntp.org/
using gps status app (its on google store), u can see if ur internal gps hardware is working and ur actual location
Note: u8300 huawei's gps was made to be an online gps (a gps assisted by internet), meaning, for it to work with google maps, ndrives and others, it needs to be connected to the internet to work properly (unless u use an off-line gps app that saves the maps in the sdcard and uses the tracking system to navigate, there are a few in google store and they work great without internet)
----------------------------------------------------------------------------------------------------------------------------------------------------------
Important
for the ones that dont like being at the spotlight
(just kidding)
the beats audio boot sound was supposed to delete itself after that 1st boot but apparently busybox (i think?!) cant remove it while the phone is booting
use some root explorer app and delete this file (android_audio.mp3) from this folder "system/media/audio/ui"
or replace it with the sound u like. (needs to be renamed android_audio.mp3) <- i did that and some guys hate my guts
or if u are a windows user, go google (lol ) and search for android commander, or go to the creator thread here in xda, its a very usefull tool and u can use it to delete that file and to do other stuff with ur phone. there is also a linux version but i think its a dead issue, but if anyone want a peek, go see it
----------------------------------------------------------------------------------------------------------------------------------------------------------
TouchSceen Calibration
if the display miscalibrates it self by bad calibration input or other stuff, go to recovery and use the TSReset to reset touchscreen calibration
the rom has some TS values by default, that allows you to go to the screen calibrator and calibrate again without any problems and with more accuracy. this way the old bad calibration input wont interfere with the new one
----------------------------------------------------------------------------------------------------------------------------------------------------------
For just the portuguese users
[Mini-Tutorial] Configurar MMS em Android
os apns foram actualizados com as modificações necessárias mas se, por algum acaso, (ainda?!) não funcionarem as mms, façam o seguinte:
- Instalar APN Portugal
- Abrir o APN Portugal e seleccionar "Configurar APNs"
- (opcional) Colocar o widget do APN Portugal no homescreen (recomendado)
- (opcional para controlar acessos indevidos à internet) Garantir que o widget está vermelho e não verde, ou seja, a internet está desligada OU abrir o APN Portugal e garantir que a internet está desactivada
- Ligar dados no smartphone (Definições - Sem fios e Redes - Redes Móveis - Check Dados activados)
- Testem enviando uma MMS para vocês mesmos.
NOTA IMPORTANTE: Se colocaram o widget, sempre que quiserem aceder à internet sem ser por wi-fi, TÊM que carregar no widget para ele ficar verde, senão não vão conseguir aceder à internet. Se não colocaram o widget têm que ir à app APN Portugal e activar o acesso à internet.
NOTA IMPORTANTE 2: Com a instalação do APN Portugal é possivel permitir/negar o acesso à internet (excepto wi-fi) por parte do smartphone, por isso não há problema de ter sempre os dados activados desde que se faça um bom controlo na APN Portugal para activar ou negar o acesso à internet. Eu tenho os dados sempre ligados e quando necessito de aceder à internet 3G basta-me tocar no widget e voilá. Quando termino a navegação, toco outra vez no widget e a internet fica inactiva.
Click to expand...
Click to collapse

Issues and/or updates info
An annoying "bug"
Only 3 users complained about this <- i thank you for reporting problems, without those reports i'ld assume everything is fine and could neglect bugs or errors and i dont want that
"I have a problem with receiving messages... they come with big delay and/or I receive it multiple times, even though it's not sent to me more than once."
apparently its an occasional memory problem (at least that was my case but i am using dev version 2.5) but could be related to the phone app (no need to explain since i'll see if i can fix it in the next version)
this fixed mine
(the names may be different but i think u know what i am talking about)
go to settings / cyanogenod settings / performance / lock messaging app in memory (<-- check this box)
other fix
uninstall the message aplication, u can use the link2sd to do that, its quicker and easy
install go sms or handcent sms or someother messaging aplication
reply back which one fixed your problem so i can see where exactly is the problem and fix that in the next version
what is to do for next updates
make the keyboard be more like the stock keyboard
add a battery power bar - 90% done but v2.2.7 has an app for that purpose
add a cpu bar - 60% done
fix network tweaks - 80% done - only a few conflict with the cmparts settings and others with the network, so they are not implemmented in v2.0 or v2.2.7 but dont worry the important tweaks are already running at the boot start
fix camera saving 90 degrees rotated files or fixing adrenalin camera transparency menus problem - i will do the one that is quick and wont be more a pain in the a**
fix the camera and gps battery drain that results from their using - that comes from the sources, the problem isnt after their use, is while we are using those apps. a friend is already trying to make them a little less energy drainners, lets see if he can do that
FM radio -> still a pita but dont force close the fm radio app anymore
modding
fix some icons that overcome the text bellow in buttons -> done
a bug resulting in a fc on the config of the light button at cmparts, options are already configured but if we want to change it, it forces close
fix the size of some menus (bigger than adrenalin and some bigger than stock), its a problem because this is an mdpi rom now instead of a ldpi like adrenalin -> 30% done
p.s.- i will try making those fixes not requiring any wiping, its a bummer doing wipes everytime and it wears the nand memory (from what i could investigate, only after 100k wiping cycles, lol, still have lots)
i will put more after
Click to expand...
Click to collapse

Just wanted to report back on version 2.2.7.
It seems to keep more apps in the memory and multitasking is for the first time kinda usable on gingerbread.
Menu buttons are fine now
ICS rotation is awesome!
Still cant notice a difference with beats audio, because our soundcard just sucks more then can be fixed by software, even stock wasn't good.
Bravia engine, can i turn that on and off at some place or is it enabled by default?
Only problem i noticed, after upgrading, the gmail app was gone and if i installed it from the play store it just crashed. Could be fixed by moving the apk to /system/app and fixing permissions.
Seems like its slowly getting better and better.
Thanks for your work!
Silas

that was my fault. i posted the wrong updated gapps (missing facebook, gmail, etc), tx for reporting
later i'll fix that
bravia is on by default in build.prop
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
Click to expand...
Click to collapse
to disable, 1->0
i tried to add an on/off to settings but... (i'll work on that later again). i noticed a difference in the taken pics, not on the camera display (stock cam app sucks, try the sleek cam and see the difference, clear img)
is hard to notice beats audio but u can tell if u put full volume that it doesnt distort audio like stock eclair. try setting a preset in the dsp manager
but that is one of the reasons i'll try xloud or megabass
edit: gapps fixed
edit2: lol
weird stuff
trying to add an Bravia on/off to settings, managed to fc wireless setting in the proccess. the surprising stuff was the free ram it left available.
135/178 mb (available/total) ->>>> something to lookup. to see if it can be managed to have all that free ram and have a full working O.S. <- that would be something really big to this little device (gameboy, lol)
btw, Silas, have u done a data wipe before fashing 2.2.7?

NAZUnlimited said:
edit2: lol
weird stuff
trying to add an Bravia on/off to settings, managed to fc wireless setting in the proccess. the surprising stuff was the free ram it left available.
135/178 mb (available/total) ->>>> something to lookup. to see if it can be managed to have all that free ram and have a full working O.S. <- that would be something really big to this little device (gameboy, lol)
btw, Silas, have u done a data wipe before fashing 2.2.7?
Click to expand...
Click to collapse
We do have 256MB of ram built in, right? Should the os itself really take more then 100MB, as it doesn't even has a GPU to keep up and running?
It actually quite noticeable how much faster the HTC Wildfire is, with the same CPU, but more RAM.
Nope, i didn't do a data wipe, just cache and dalvik. But my phone has now started to behave the same way as with your first patch, it doesn't keep the settings (for example the screen brightness resets itself) and i cant go to airplane mode.
I will see if your latest gapps update fixed that, and then report back. When the always terribly slow rapidshare has finished downloading

funny. my downloads and uploads are fast from rapidshare. i uploaded gapps from my u8300 in 4min. (i might switch to dropbox the big files and leave rapidshare for the stuff with 2mb or less)
according to http://whirlpool.net.au/wiki/huawei_u8300, we have 256mb, but unless the 178mb that appear in status are the ammount of ram available for the user and the missing rest (that dont appear anywhere) for the o.s. ,.... u get the idea.
512mb of memory flash
192mb- data
170mb- system
70mb - cache
3-4mb- boot
1mb- splash screen ( bootlogo)
(the rest for mombo-jumbo partitions like OTA)
the day i figure how to change partitions size without messing the phone internals.... that will be a good day
i was affraid of that. i do not experience that but i flashed with full wipe. not using data wipe was only tested with users that dont keep much stuff in data (almost nothing only apps) and i dont know if they changed the default settings and since none reported any problem, i figured it was fine.
like i said, v2.2.7 is a new rom, only the looks is the same as v2.0. that bug now (since i still didnt put the super 3g tweaks that busted those settings) is probably resulting from the saved settings/info/etc in data partition.
since i removed those tweaks, i have not seen that bug again and i am using v2.2.7 for almost 2 weeks now.

NAZUnlimited said:
funny. my downloads and uploads are fast from rapidshare. i uploaded gapps from my u8300 in 4min. (i might switch to dropbox the big files and leave rapidshare for the stuff with 2mb or less)
Click to expand...
Click to collapse
4min for a 15MB file is not fast for me, im used to about 15seconds for that. (and i still have one of the slowest broadband connections here in sweden )
NAZUnlimited said:
according to http://whirlpool.net.au/wiki/huawei_u8300, we have 256mb, but unless the 178mb that appear in status are the ammount of ram available for the user and the missing rest (that dont appear anywhere) for the o.s. ,.... u get the idea.
512mb of memory flash
192mb- data
170mb- system
70mb - cache
3-4mb- boot
1mb- splash screen ( bootlogo)
(the rest for mombo-jumbo partitions like OTA)
the day i figure how to change partitions size without messing the phone internals.... that will be a good day
Click to expand...
Click to collapse
Running aplications is showing about 50-70MB in total, so the OS must use ~200MB for something
Another thought, would it maybe help us if we use the sdcard for swapping? I'll try that today and look if i can notice any difference
Flash memory is not that much of a problem, as we have app2sd.
NAZUnlimited said:
i was affraid of that. i do not experience that but i flashed with full wipe. not using data wipe was only tested with users that dont keep much stuff in data (almost nothing only apps) and i dont know if they changed the default settings and since none reported any problem, i figured it was fine.
like i said, v2.2.7 is a new rom, only the looks is the same as v2.0. that bug now (since i still didnt put the super 3g tweaks that busted those settings) is probably resulting from the saved settings/info/etc in data partition.
since i removed those tweaks, i have not seen that bug again and i am using v2.2.7 for almost 2 weeks now.
Click to expand...
Click to collapse
It's a pretty random problem. Yesterday the bug was there, but after reflashing the new gapps and replacing superuser with supersu, it's fine again

Optical Fiber still havent reached this part of portugal and 3g data plan is absurd. That example was using the phone and a (lets say) "public" wireless with 10% signal strenght reception. i dont know the up/down capacities of that one ( i just detected it and the rest is history. Lets say i have allways access to the net and never used the 3g data) but most people here buy the 2mb pack (2 mb down / 256kb up) argh, stone age! Normally, at home, i can download 1gb in less than 10min and upload about 2x longer.
I considered swap and and a ram module (zram.ko) too but i hadnt much time to try it.
I am not worryed with the flash memory, like u said, we have app2sd and link2sd. What is annoying for me is seeing all that mb just sitting there un-used
edit: use the sdcard for swapping?
process
- creation of a 3rd sdcard partition for swap
- adapt a script to format that in recovery and other to enable the swap partition at phone boot ()
results so far
pro-swap
- no battery drain resulting from doubled sd-card read/write (none that can be noticed even using other means to check battery outputs)
- phone seems more responsive and the benchmark test results were more stable than the previous ones without swap, in fact, increased an average of 14~20 total points in ram/cpu integer
- still havent noticed much improvement (there is some) in multi-tasking but the phone isnt loaded with much apps (read downside why) and that will tested again when i have loaded the phone
downsides
- according to any devs of swap scripts, Swapping decrease Micro SD's life but it is easier and cheaper to buy and replace a new sdcard than a new internal memory (no argument there, done a quick search and realised that for the price of a memory chip + repair, u can almost buy a phone). in fact, according to one dev, he is still using the same card for 2 years (almost year and half using swap) and he still didnt see any wearing problems in that sd-card area (swap partition) or any other.
- the reason why the phone isnt loaded with much apps is because for the creation of a 3rd partition, i wiped and divided the 2nd partition (link2sd partition) in 2. that interfered with the link2sd script in system and didnt let me either activate swap or link2sd partition or replace the link2sd scripts in system, so i did a fast solution for that, full wipe . what i should've done back then was modify the size and create a new partition using the free space of the 2nd partition and no problems after but some ideas only come after the previous ones failed. lol
- i dont know which is better for swap, if the swapper app in store or just a init.d script at boot. <- tests for later
Sent from my U8300 using xda premium

NAZUnlimited said:
edit: use the sdcard for swapping?
process
- creation of a 3rd sdcard partition for swap
- adapt a script to format that in recovery and other to enable the swap partition at phone boot ()
results so far
pro-swap
- no battery drain resulting from doubled sd-card read/write (none that can be noticed even using other means to check battery outputs)
- phone seems more responsive and the benchmark test results were more stable than the previous ones without swap, in fact, increased an average of 14~20 total points in ram/cpu integer
- still havent noticed much improvement (there is some) in multi-tasking but the phone isnt loaded with much apps (read downside why) and that will tested again when i have loaded the phone
downsides
- according to any devs of swap scripts, Swapping decrease Micro SD's life but it is easier and cheaper to buy and replace a new sdcard than a new internal memory (no argument there, done a quick search and realised that for the price of a memory chip + repair, u can almost buy a phone). in fact, according to one dev, he is still using the same card for 2 years (almost year and half using swap) and he still didnt see any wearing problems in that sd-card area (swap partition) or any other.
- the reason why the phone isnt loaded with much apps is because for the creation of a 3rd partition, i wiped and divided the 2nd partition (link2sd partition) in 2. that interfered with the link2sd script in system and didnt let me either activate swap or link2sd partition or replace the link2sd scripts in system, so i did a fast solution for that, full wipe . what i should've done back then was modify the size and create a new partition using the free space of the 2nd partition and no problems after but some ideas only come after the previous ones failed. lol
- i dont know which is better for swap, if the swapper app in store or just a init.d script at boot. <- tests for later
Sent from my U8300 using xda premium
Click to expand...
Click to collapse
I have been using swapper 2 for a few days now, and while it works fine, and hasnt caused any problems, it also hasn't improved anything that i could notice.
What size and swappines settings do you use?

125mb swap partition (so i have 3 physical partitions in sd-card, 1-fat32 (data), 2-ext4 (link2sd), 3-linux swap (swap partition))
swappiness=100
vfs_cache_pressure=25
apparently, most of the swappers agree that less than 100 almost dont do anything
my previous was 60
"A low value means the kernel will try to avoid swapping as much as possible where a higher value instead will make the kernel aggressively try to use swap space. The default value is 60, and for most desktop systems, setting it to 100 may help to improve overall performance, whereas setting it lower (even 0) may improve interactivity (decreasing response latency.)[1]"

Changin the minfree values to 6,8,16,20,22,24 is giving some truly amazing multitasking!
I can now have about 8-12 apps in the "memory", with nearly instant switching.
My vfs_cache_pressure is at 10, which i think is default, i have 256MB of swap, enabled with swapper 2, but on a seperate partition. swappiness=100
This phone has newer been so fast
Edit: I was voting for stock browser because i want a vanilla experience. But i use Opera Mini 95% of the time, and sometimes Opera Mobile.

tx for the info, silas
i had changed a "bit" those values and oom priorities, etc
vm.min_free_kbytes=18400;
mine were :̶8̶,̶2̶0̶,̶4̶5̶,̶6̶5̶,̶9̶0̶,̶1̶0̶0̶ 10, 16, 55, 70, 85, 100
i'm still testing those for side-effects
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
in the pic above, i used v6 script for tests. even though i changed all values, it still said 50% supercharged. then i figured out why, the script couldnt find the supercharged adj file nor the minfree. v6 puts them in /data to read them at boot start but since i didnt supercharged, my /data didnt have them. (i just altered the rom defaults making a more cleaner version - less files in /data and /init.d - and 100% tweak stick. on the opposite, v6 values didnt stick every 2 boots - dont know why that happened)
i love zepp's work but i dont use v6 supercharger for, mainly, two reasons
1- slows down boot proccess (dont know why), it can be noticed in the boot animation, it becames slower
2- some tweaks in the script block the light, orientation, gps, data toogles (one cant change those if the wifi or data is connected)
what i changed in rom defaults (these are only if using swap)
OOM_MEM_Settings, OOM_ADJ_Settings -> build.prop
minfree 2560,4096,14080,17920,21760,25600 -> (10, 16, 55, 70, 85, 100)
adj 0,3,6,10,12,15
swappiness 100
vfs_cache_pressure 25 -> yeah, the default is set to 10
dirty_expire_centisecs 500 -> will test other values later
dirty_writeback_centisecs 1000 -> same here
dirty_ratio 95
dirty_background_ratio 60
̶l̶e̶a̶s̶e̶-̶b̶r̶e̶a̶k̶-̶t̶i̶m̶e̶ ̶1̶0̶ -> this one is giving me lots of trouble, wont stick
vm.min_free_kbytes=18400;
vm.oom_kill_allocating_task=0;
vm.panic_on_oom=0;
vm.overcommit_memory=1;
kernel.panic_on_oops=1;
kernel.panic=30;
net.core.wmem_max=1048576;
net.core.rmem_max=1048576;
net.core.optmem_max=20480;
net.ipv4.tcp_moderate_rcvbuf=1;
net.ipv4.route.flush=1;
net.ipv4.udp_rmem_min=6144;
net.ipv4.udp_wmem_min=6144;
net.ipv4.tcp_rmem='6144 87380 1048576';
net.ipv4.tcp_wmem='6144 87380 1048576';
this i what i like
a good memory management

It seems like you are trying to get as much free memory as possible. Which isnt exactly what i want to do. Unused memory is always just wasted memory.
The perfect memory management would be when we can have all the memory filled up, but always have something that can be cleaned up when needed.
I havent tried all your values yet, might do that when i have more time, and a computer. Right now im testing out these values: http://forum.xda-developers.com/showthread.php?t=1227269
Also, Rom Toolbox is fantastic for this kind of tweaking, just a tip

That will be a yes and no. I am trying to keep free some internal memory to use when its needed by the current aplication or the os and load up all the rest in swap. Just like what u are doing but using swap as loaded "ram" to give some slack to internal ram for when we need it. I found out that the internal taskkiller kills apps after some time in internal ram, cached or not, even if tricking it to think we have more than 178mb ram ( the oom adjustments) but it doesnt kill the ones mostly present in swap (funny stuff). Other reason was because the phone couldnt reach deep sleep with a loaded internal ram and with taskkiller seeking for terminable apps, all that increased the battery drain. Since i never turn off wifi nor data, i noticed some power drain, higher than the ones before
rom toolbox, i used it a lot before when i was on adrenalin update 2 but it cant alter the lease value too. I can do most of the stuff by head now, in part tx to rom toolbox
Sent from my U8300 using xda premium

I must say, your settings work ok too, pretty much the same result as my earlier settings.
I found something interresting
I was replacing some system apps with the ones from Cyanogen 7.2, and i suddenly noticed that the auto brightness option was back. (I love that feature, relly usable ) It must have been eather Settings.apk or Settingsprovider.apk that did the magic.
But it introduced one bug, which also was on adrenalin earlier, I have too open the wifi settings to make it scan and connect. Could maybe be fixed by changing some scan settings?
Also, replacing some other files made a difference in performance. (Maybe just an illusion...) I think it must have been framework-res.apk and systemUI.apk. Maybe some other apps where optimized too.
And that gave me the stock look back. Nothing back about your theme, but stock looks much better
Replacing camera fixes the menu, (not transparent and horrible to read anymore). Image is still rotated, I might look into that later
All my files are available here:
http://silenz.se/owncloud/public.ph...dddf22a07966e8b75&file=/ownCloud/huawei_tweak
It does really seem a little bit smoother now

nice to see that someone is making stuff for our phone. like tuono once said, "i was starting to feel a little lonely here"
if u are using the ones from u8150, its normal they work good with vicky. like most roms made from cyanogen sources for huawei phones (u81xx/u82xx/u85xx/u88xx/m86x, etc), they all use the official u8150 code and part of vicky's code is also based on those sources, the rest is based on samsung.
about auto-brightness, u replaced the cmparts.apk. the "bug" is on that apk. its not an error in the code but something else interfering with the openning of that setting. i've tried the lux app and it proved me that auto brightness is working. activating the brightness icon (not the app in drawer but the toogle like the wifi, bt) in the toolbar (systemui.apk) and then pressing it until it reach auto, showed that too. i wasnt much concerned with that because i think it works backwards, when in sunlight it reduces the brightness and in darkness is the opposite, it burned my eyes when i used (i have photo-sensitivity <- i think thats the right name in english for that) and u8300 display is hard to see with sunlight and low brightness. but everyone is free to use what they see fit to it.
about performance, u are right. most performance increased is an illusion and its not. i did a couple of tests before i succumbed to the urge to change the stock looks (lol. i was forced by u know who ). i tested with stock look, mod look and stock look with a theme applied (using theme chooser). the results were pretty much the same but only modded looks got allways higher scores. most definitely because most pngs are smaller in kb than the ones from sources and the ones in the theme apk, that size makes all the framework (i'm not just talking about framework-res.apk here but all that is loaded for the display view) to occupy less in memory therefore granting more performance. but all that is if using vicky's apps, generated from vicky's mixed sources. now the reason that u have or appear to have an increased performance is because u replaced most system apps except the jar files. most of them dont make a difference but systemui, settings, cmparts and frameworks-res make. a quicky way to explain is if u think those apps as computer hardware and programs that run at windows start. if u disable some hardware and block some services and programs to start at boot, u will notice an increased performance in the pc, that is what u did. by replacing those apps u disabled some "instructions", since they wont run, more performance. just like when i crashed the network settings and freed a lot of ram. the jar files in frameworks folder use those instructions to make run some stuff like the 1% battery. stock only has 10% battery indicator.
i hope i explained myself well. its 6h in the morning here and i dont sleep for almost 34h. and i have to feed Vicky (btw, Vicky is the cat)
i am a bit curious about some things. why the rom manager and cmwallpapers conflict? those apps are universal. (cmscreenshot, u did have to replaced it, its universal, same code for every gb rom)
about the looks, i am making it a theme chooser app. it will make more easier for me to do the needed stuff in system apps without having to concern about the looks and the ones that dont want that look can easily change it or delete.
other thing, battery seems mor stable now. heres a screenie

NAZUnlimited said:
nice to see that someone is making stuff for our phone. like tuono once said, "i was starting to feel a little lonely here"
if u are using the ones from u8150, its normal they work good with vicky. like most roms made from cyanogen sources for huawei phones (u81xx/u82xx/u85xx/u88xx/m86x, etc), they all use the official u8150 code and part of vicky's code is also based on those sources, the rest is based on samsung.
Click to expand...
Click to collapse
Yes i have those from u8150, because its 90% the same hardware. Just another screen and no keyboard. (and maybe some internal stuff like the acelerometer, but those should "always" work).
NAZUnlimited said:
about auto-brightness, u replaced the cmparts.apk. the "bug" is on that apk. its not an error in the code but something else interfering with the openning of that setting. i've tried the lux app and it proved me that auto brightness is working. activating the brightness icon (not the app in drawer but the toogle like the wifi, bt) in the toolbar (systemui.apk) and then pressing it until it reach auto, showed that too. i wasnt much concerned with that because i think it works backwards, when in sunlight it reduces the brightness and in darkness is the opposite, it burned my eyes when i used (i have photo-sensitivity <- i think thats the right name in english for that) and u8300 display is hard to see with sunlight and low brightness. but everyone is free to use what they see fit to it.
Click to expand...
Click to collapse
But cmparts.apk is just for cyanogenmod, and other roms, even plain android source, has this feature. A fun little fact, even the stock rom could read light sensor data, but the auto brightness feature was missing.
Is it epilepsy you have? Its when you react to fast color/light changes?
It's possible to change the brightness values, and some other nice settings, in the cyanogenmod settings>Display>Automatic backlight
NAZUnlimited said:
about performance, u are right. most performance increased is an illusion and its not. i did a couple of tests before i succumbed to the urge to change the stock looks (lol. i was forced by u know who ). i tested with stock look, mod look and stock look with a theme applied (using theme chooser). the results were pretty much the same but only modded looks got allways higher scores. most definitely because most pngs are smaller in kb than the ones from sources and the ones in the theme apk, that size makes all the framework (i'm not just talking about framework-res.apk here but all that is loaded for the display view) to occupy less in memory therefore granting more performance. but all that is if using vicky's apps, generated from vicky's mixed sources. now the reason that u have or appear to have an increased performance is because u replaced most system apps except the jar files. most of them dont make a difference but systemui, settings, cmparts and frameworks-res make. a quicky way to explain is if u think those apps as computer hardware and programs that run at windows start. if u disable some hardware and block some services and programs to start at boot, u will notice an increased performance in the pc, that is what u did. by replacing those apps u disabled some "instructions", since they wont run, more performance. just like when i crashed the network settings and freed a lot of ram. the jar files in frameworks folder use those instructions to make run some stuff like the 1% battery. stock only has 10% battery indicator.
Click to expand...
Click to collapse
So your framework-res.apk is smaller? (don't have your files left, and rapidshare is still slow ) I might try to write a small python script that decreases the quality of the images.
Could you explain what i have disabled, because everything is still running, that i can notice. Or have you added some services that i disabled? (i get that the battery is updating less often but that shouldn't make a noticeable difference?)
NAZUnlimited said:
i hope i explained myself well. its 6h in the morning here and i dont sleep for almost 34h. and i have to feed Vicky (btw, Vicky is the cat)
Click to expand...
Click to collapse
I read your post a few times, and i think i got most of it now. But you should sleep a little bit now. And fondle the cat from me
NAZUnlimited said:
i am a bit curious about some things. why the rom manager and cmwallpapers conflict? those apps are universal. (cmscreenshot, u did have to replaced it, its universal, same code for every gb rom)
Click to expand...
Click to collapse
The conflicts are just some things owncloud (my hosting service, similar to dropbox, but on your own server) messed up. It's not the most stable peace of software ever written
Cmscreenshot was not exactly the same size, so the might have optimized something since the last release.
NAZUnlimited said:
about the looks, i am making it a theme chooser app. it will make more easier for me to do the needed stuff in system apps without having to concern about the looks and the ones that dont want that look can easily change it or delete.
Click to expand...
Click to collapse
Ok, the perfect thing for me would be a smaller stock theme.
NAZUnlimited said:
other thing, battery seems mor stable now. heres a screenie
View attachment 1135355View attachment 1135356
Click to expand...
Click to collapse
Battery stats never worked for me, it always blames some random app like youtube for 99% of the usage, even if it was running 5seconds
But at least battery life is ok for me, usually enough for a school day.
Edit: I will try to build some apps from source, and maybe reduce the size if possible. Might also try to take a look at the camera.
Edit 2:
I fixed the camera rotation
Available here:
http://silenz.se/owncloud/public.ph...31c0170c4d0dddf22a07966e8b75&path=/Camera.apk
Also i'm working at reducing the memory usage of the framework.
Could someone (NAZUnlimited) please check how much memory "Android System" and the service com.android.systemui is using?
Mine is currently at 21.48MB (was at 20MB directly after boot) and the systemui at nearly 6MB
You can use https://play.google.com/store/apps/details?id=com.rs.autokiller to check that.

Is it epilepsy you have? Its when you react to fast color/light changes?
Click to expand...
Click to collapse
no, not that. a sleeping brain couldnt find the right word or expression
photophobia or light sensitivity. i have cat eyes or bilateral coloboma (cat eyes is cooler, lol). my sight is fine, i just have to wear glasses with lenses that change color with light (i dont know the name of that, photo lenses or something). my coloboma problem is more of a cosmetic thing but it leave me with a high sensitivity to light.
Could someone (NAZUnlimited) please check how much memory "Android System" and the service com.android.systemui is using?
Click to expand...
Click to collapse
ok. after install the program
free ram -> 96MB
Android System -> 20.11MB
com.android.systemui -> 4.53MB
after reboot (here the program changed my oom settings without asking and i didnt apply nothing)
free ram -> 67MB
Android System -> 18.79MB
com.android.systemui -> 4.82MB
reboot 2 (with deny permissions for autokiller and keeping my settings)
free ram -> 85MB (with time or use, some apps will be cached to swap and will free ram)
Android System -> 19.26MB
com.android.systemui -> 4.07MB
i tested the cam. great job on that. now the only thing that remains to fix in that is to unsquare the img we see in the app. there was a cm's cam app that didnt have that problem, only the rotated save problem. dont remember if was in the htc or xperia cm gb.
one thing, reducing with high compression the size of the app is great for the amount of space it occupies in memory ("physically") but it forces the use of more ram to read the app, reducing performance. that is why odexed apps grant more performance (but they grant other problems). the trick is to set the right compression and/or reducing the amount of space the app occupies unpacked (pngs, code, etc). thats why zipalign is very important to deodexed roms
So your framework-res.apk is smaller? (don't have your files left, and rapidshare is still slow ) I might try to write a small python script that decreases the quality of the images.
Could you explain what i have disabled, because everything is still running, that i can notice. Or have you added some services that i disabled? (i get that the battery is updating less often but that shouldn't make a noticeable difference?)
Click to expand...
Click to collapse
no, my frameworks is in fact bigger than the one from sources, it has more files stored inside (if i recall right, something between 260 and 330) (used the trick above).
dont worry about what u have disabled. for stock looks, it wont cause any problems. but just in case, u should do a factory reset (data or just a dalvik reset) and check. if nothing force closes at start, u are fine. most services are in the jar files. u wont have any problems unless u replace those.
about the quality of the images, u need to be carefull there. most pngs stored have visual indicators. if a pixel is missed on those indicators, u'll have visual bugs or worse, the os could stuck at the end of boot and stay there, never starting to the actual interface. i had those problems in a lewa rom (hdpi)

NAZUnlimited said:
ok. after install the program
free ram -> 96MB
Android System -> 20.11MB
com.android.systemui -> 4.53MB
after reboot (here the program changed my oom settings without asking and i didnt apply nothing)
free ram -> 67MB
Android System -> 18.79MB
com.android.systemui -> 4.82MB
reboot 2 (with deny permissions for autokiller and keeping my settings)
free ram -> 85MB (with time or use, some apps will be cached to swap and will free ram)
Android System -> 19.26MB
com.android.systemui -> 4.07MB
Click to expand...
Click to collapse
Ok, mine are at 16.73 and 3.37
I also removed the fotakill app. Huawei will newer send us an OTA-update and it was runnning in the background all the time
NAZUnlimited said:
i tested the cam. great job on that. now the only thing that remains to fix in that is to unsquare the img we see in the app. there was a cm's cam app that didnt have that problem, only the rotated save problem. dont remember if was in the htc or xperia cm gb.
Click to expand...
Click to collapse
That image in the top right?
I also noticed that video recording is broken, no idea why.
NAZUnlimited said:
one thing, reducing with high compression the size of the app is great for the amount of space it occupies in memory ("physically") but it forces the use of more ram to read the app, reducing performance. that is why odexed apps grant more performance (but they grant other problems). the trick is to set the right compression and/or reducing the amount of space the app occupies unpacked (pngs, code, etc). thats why zipalign is very important to deodexed roms
Click to expand...
Click to collapse
Well, why not try to odex all the apk's. The stock rom was odexed. Which problems should it introduce?
I'll do that now and see if i get any performance boost, or bugs
Also, i think the cm7-compiling process is zipaligning system apks automatically.
NAZUnlimited said:
no, my frameworks is in fact bigger than the one from sources, it has more files stored inside (if i recall right, something between 260 and 330) (used the trick above).
dont worry about what u have disabled. for stock looks, it wont cause any problems. but just in case, u should do a factory reset (data or just a dalvik reset) and check. if nothing force closes at start, u are fine. most services are in the jar files. u wont have any problems unless u replace those.
about the quality of the images, u need to be carefull there. most pngs stored have visual indicators. if a pixel is missed on those indicators, u'll have visual bugs or worse, the os could stuck at the end of boot and stay there, never starting to the actual interface. i had those problems in a lewa rom (hdpi)
Click to expand...
Click to collapse
I have wiped data since my big changes, and no problems.
My framework-res.apk is currently 3.9MB, the same size as yours. But i have no idea where i got that from
I have actually replaced my framework.jar, with no problems at all. Mine is ~0,2MB smaller, most likely why my memory usage is lower. Also, some of my other .jar files are smaller, but i haven't tried those yet.
I had changed my images, and saved ~0.2MB there with no problems that i could find.
But the thing i wanted to do was to use a higher compression, but it was already as small as possible. So i reduced the resolution to 70% of the original (in each direction).
Reduced the size of drawable-mdpi to 976.0 kB from 1.1MB. No big changes. I might try to do that again with my new framework-res.apk (the one i don't know where it comes from ) and all the png's.
But i don't think we can save much there.
Edit:
I odexed a few system apps. Settings, systemui, holo launcher, camera, root explorer and play store
I noticed a little bit better performance with the launcher and the play store, but it's nothing revolutionary.
My system files are available here: http://silenz.se/owncloud/public.ph...dddf22a07966e8b75&file=/ownCloud/huawei_tweak
Also the new framework.jar is available there

[UPDATE][ALL ROMS][HOW-TO]Speed Up & Maintain - [CM-7/9/10/10.1][NEW CONCEPTS]

I know, many people here want to have Android 4.x.x on their phones, but unfortunately, because of low-end processor as well as less RAM, these CM10/CM10.1 ROMs are laggy and slow. I am also one of them, but, after using these type of roms since 4 months, I have now got a perfect idea of using them. So, I am sharing the way I use these roms. Many people told that this also helps for CM7 users. So, now I have declared this thread as UNIVERSAL PERFORMANCE THREAD. This method can be used on - Stock | CM7/9/10/10.1.
NOTE : This method is same for PAC ROMS.. because they are based on CM. So, you can use this on PAC ROMs also.
♦ FINDING STABLE VERSION :
First of all, you will need to find a good stable version of any CM7\CM9\CM10\CM10.1 ROM. Find stable version by asking in general discussion thread of those particular ROM and then download that version. But, do not flash now.. Follow next step.
Note : For CM7 users - Official CM7 is best, but if you want you can try it on custom roms also. If you are using CM7 custom or stock based custom rom, then for scripts n tweaks to work, you must delete all the scripts from init.d so that scripts will not get overridden.
♦ SLIMMING THE ROM :
Slimming means making rom size less by removing unwanted and unnecessary applications from system/app. It reduces system memory use. Here is a chart of cm10.1 apps which are safe to remove - LINK
With reference to that chart you should remove following apps with adding alternatives to them.
Note: Left side apps are to be removed and right side apps are alternatives.
● LatinIME.apk - WP7 Keyboard App
● Browser.apk - Holo Web Browser
● CMFileManager.apk - Root Explorer File Manager
● Trebuchet.apk - Holo Launcher
NOTE: On CM7, default ADW is good, but you can also use Holo Launcher.
Other apps that can be removed without alternatives-
● CalendarProvider.apk - One of the big RAM consuming apps. This app start anytime, you do anything, so it will be a big save of memory removing this app. But, you will get problems with calendar sync..
● GoogleCalendarSyncAdapter.apk - Reomove this only if you do not sync calendar.
● Email.apk - If not in use.
● Gmail.apk - If not in use.
● Talk.apk - If not in use.
● GoogleBackupTransport.apk - It is used in google backups, remove on your own risk. (Not a risk, i always remove it.)
● ChromeBookmarkSyncAdapter - No use.
● HTMLViewer.apk - Never needed.
● UserDictionaryProvider.apk - It is useless without LatinIME.apk.
● VisualizationWallpapers.apk - Wallpapers app. Remove it always.
● CMWallpapers - Remove it always.
● VoiceDialer.apk - Do you really use it?
● LiveWallpapers.apk - Dont you care for your battery?
● QuickSearchBox.apk - If you dont use.
● PicoTTS.apk - Text to speech function.
NOTE: Alternative apps should always be installed in system/app only. For that, I recommend you to remove these apps drectly from rom's zip before flashing.
♦ USE OF SCRIPTS N TWEAKS :
Many people use hard scripts n many tweaks to get good performance. But, it is totally wrong.
Highly recommended to use Activo Speeder. It is the best script for performance. Dont use anyother thing with it- such as ram manager, seeder or anyother script.
(Note: If the above script doesnt work on your device then please find another good script and flash it.)
ALTERNATIVE FOR ACTIVO SPEEDER :
After testing a lot, I found that SuperCharger is the best script which can be used with any ROM to get more performance and for perfect RAM Management. Here are some steps on how to use SuperCharger -
● Here is the original thread for SuperCharger script.
● Script can be downloaded from this download page.
● Download latest script as well as starter package if needed (Read Original Thread).
● Now, for 4.x.x ROMs, you do not need to do anything with services.jar. But, for below 4.x.x, services.jar needs to be patched to get SuperCharger Memory Management working.
● Now, copy script to SDcard and run it with Script Manager as root. For more detailed guide plz prefer the original supercharger thread.
● Now, you are running the script. You will find many options and info on screen. Read it all and choose what you want.
NEW DISCOVERY : SUPERCHARGER + CROSSBREEDER = ULTIMATE PERFORMANCE WITH MAX ENTROPY ! - by Dark Passenger
● LINK FOR THE POST.
Here are some tweaks-
In Build.prop -
●
Code:
ro.ril.disable.power.collapse=0
and change the value from 0 to 1. (Add the line with proper value if does not exist)
This one is for battery saving.
●
Code:
dalvik.vm.heapgrowthlimit=48m
If it already exists then just match the values.
This is a VM Heap management for RAM.
●
Code:
ro.ext4fs = 1
Improves EXT4 performance.
● IMP :
Add following lines below "# Other" in build.prop
Code:
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
(If exists, just change the values as above).
(Note: This one will remove location feature increasing performance freeing up more RAM. This frees up to 30mb of RAM)
And now remove NetworkLocation.apk from system/app as well as com.android.location.provider.jar from /system/framework.
For further build.prop tweaking, you can use this great guide -> Click Here. Thanks to Dark Passenger for some build.prop tweaks.
This much tweaking and scripting is enough. DONT USE TOO MUCH TWEAKS N SCRIPTS.
♦ BASIC APPS TO USE :
Your rom's performance also depends on the apps which you use. Always look for apps' memory usage and if the app consumes more ram then try to find an alternative app for it. Here are some basic apps which you should use (i always use them).
● Use Root Explorer as file manager, Holo Launcher as Launcher.
● Use Cache Cleaner App. It is must. Clean cache once a day.
● Use Root Cleaner App. A must have app. Do "Quick Cleaning" twice a day. It will regulate your performance.
You can also freeze the apps you are not using at that time, such as DSPManager (Unfreeze it only at the time of listening songs)
Freezing Google Apps will be a great way to reduce RAM consumption.
● Use this amazing app - Autostarts. This app controls the apps that start automatically in your phone. If you want settings which I use then PM me. I will tell you, how to use this app.
CLICK HERE FOR AUTOSTART APP SETTINGS
● ABOUT TASK KILLERS :
Using task killer is good but, it is also bad. Task killing is actually meaningless. Some apps never really get killed. They start again n again. So, use Autostarts instead task killers. But, here is a nice app for killing processes and freeing RAM. This is the original app. I have themed it to look good. Download it here.
Use it as a task killer, press menu button and include system processes and then start killing processes which are useless.
● Try to use apps as system apps.
● If you are using UC Browser then in its settings, check "Clear Data on Exit". If did, you will see UC will take less than 10mb but, if you wont do this, UC will take more than 15mb.
♦ IMPORTANT TIPS AND SETTINGS :
● Always flash rom with a clean wipe and proper flashing method.
● Do not flash gapps again if they are included in the rom.
● Do not flash internal memory scripts as they reduce performance.
● Use Adrenaline Boost. Boost once or twice a day. Boosting much will increase battery consumption.
● Use Root Cleaner app and freeze the apps which you are not using at that time. Freeze Google Play Store, Google Services Framework and other google apps which are always on. Unfreeze them when you want.
● The apps used for Backup purposes should not be installed always. Keep them in your sdcard and install them when you want and uninstall when done with them.
● Basic apps should always be in system/app.
● In Developer Options -
Set all animations scale to .5x
Set Background Process Limit to "Atmost 4 processes", if issues occur then set it back to "Standard Limit".
Enable "Kill App Back Button". Always use this feature to come out of the apps which do not really exit on pressing just back button.
● Do not expect much from our phone as it is not a high-end phone. Dont expect good battery life but, still to gain good battery life. Keep RAM free by using the ProcessKiller app as told above. I always get 170 mb RAM free.
● Do not charge battery until it gets discharged upto 10% or less. While charging do not remove it till it reaches 100% and 20 mins above that.
● Calibrate battery when needed.
● Avoid use of apps which are always running either in background or foreground.
● Press thanks. .

Re: [HOW-TO] Speed Up & Maintain CM9 | CM10 | CM10.1 ROMs
Very good tutorial i came across so far :good:

+1
So true...great thread...
even i used to things unknowingly but now i know what to keep(apps) and vice versa.. great work..:good:

mni ANKIT said:
So true...great thread...
even i used to things unknowingly but now i know what to keep(apps) and vice versa.. great work..:good:
Click to expand...
Click to collapse
Thnx..

Great
very helpful thread. good job

Good tutorial(surprising no one thought of it sooner, yes me Included).
1. small thing
add explanations for all those tweaks(basically what they do)
eg.
ro.ril.disable.power.collapse=0 : claims to put the phone into deeper sleep but according to the code base seems to be undefined and should actually do nothing
pm.sleep_mode=1 : useless cause ICS and above devices this is a kernel parameter that needs to be passed directly to the kernel on boot(thus putting it to build prop doesn't help).
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
and this just shuts off network locations(for google services).
a good guide to know which leaks are the real thing and which suck(ICS and above only) guide

Dark Passenger said:
Good tutorial(surprising no one thought of it sooner, yes me Included).1. small thingadd explanations for all those tweaks(basically what they do)eg.ro.ril.disable.power.collapse=0 : claims to put the phone into deeper sleep but according to the code base seems to be undefined and should actually do nothingpm.sleep_mode=1 : useless cause ICS and above devices this is a kernel parameter that needs to be passed directly to the kernel on boot(thus putting it to build prop doesn't help).ro.com.google.locationfeatures=0ro.com.google.networklocation=0and this just shuts off network locations(for google services).a good guide to know which teaks are the real thing and which suck(ICS and above only) guide
Click to expand...
Click to collapse
First of all thanks for the info...
actually, for ro.ril.disable.power.collapse=0.. it is default.. but it is written that the value 0 should be changed to 1..
And about pm.sleep_mod.. i will remove that.
The lines -
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
Remove location features.. i forgot to mention that.. but.. network location is useless for some people and eats about 30mb of ram.. always (in any condition) so.. removing location features by these lines is a good way to manage ram..
Thnx for tht link.. i will include that.

OJ said:
First of all thanks for the info...
actually, for ro.ril.disable.power.collapse=0.. it is default.. but it is written that the value 0 should be changed to 1..
And about pm.sleep_mod.. i will remove that.
The lines -
ro.com.google.locationfeatures=0
ro.com.google.networklocation=0
Remove location features.. i forgot to mention that.. but.. network location is useless for some people and eats about 30mb of ram.. always (in any condition) so.. removing location features by these lines is a good way to manage ram..
Thnx for tht link.. i will include that.
Click to expand...
Click to collapse
agood tweak is to switch this
Code:
dalvik.vm.heapgrowthlimit=32m
to
Code:
dalvik.vm.heapgrowthlimit=48m
(enough for our devices) cause this fixes the vm heap to restrict size to 48m(hence preventing the vm heap from spliting).
source :zeplinox
also
Code:
ro.ext4fs = 1
(suppose to improve ext4 filesystem performance).
also anyone tried to change this
Code:
debug.composition.type=gpu
on cm10.1/aokp 4.2
to
Code:
debug.composition.type=mdp
what happens(I mean does it cause bootloop or not).

Dark Passenger said:
agood tweak is to switch this
Code:
dalvik.vm.heapgrowthlimit=32m
to
Code:
dalvik.vm.heapgrowthlimit=48m
(enough for our devices) cause this fixes the vm heap to restrict size to 48m(hence preventing the vm heap from spliting).source :zeplinoxalso
Code:
ro.ext4fs = 1
(suppose to improve ext4 filesystem performance).also anyone tried to change this
Code:
debug.composition.type=gpu
on cm10.1/aokp 4.2to
Code:
debug.composition.type=mdp
what happens(I mean does it cause bootloop or not).
Click to expand...
Click to collapse
Thank you very much.. will add them all soon.

Activo seeder seems to do nothing for me...xcellent replacement is crossbreeder mod which i use everytime along with ram manager app..

swat4samp said:
Activo seeder seems to do nothing for me...xcellent replacement is crossbreeder mod which i use everytime along with ram manager app..
Click to expand...
Click to collapse
As you think.. it is up to you. I think activo is best. But, do not use both together.. use only one thing at one time.

Hey thanks for your awesome guide, to be honest i am using this guide with CM7.2 and i can feel better memory and battery life.
can you please tell me your auto start up settings, i wanna know exactly which apps to disable.

CoDDeZ said:
Hey thanks for your awesome guide, to be honest i am using this guide with CM7.2 and i can feel better memory and battery life.can you please tell me your auto start up settings, i wanna know exactly which apps to disable.
Click to expand...
Click to collapse
Wait, i will give you them..
EDIT: Here are the settings -
(Apps that should be disabled)
During Startup :
Google Services Framework
After Startup :
Contacts
Gallery
Download Manager
Settings
Google Play Store
DSPManager
Google Play Services (all 3)
Google Services Framework (all 4)
Connectivity Changed :
Download Manager
Google Play Services
Google Services Framework (all 3)
Application Installed :
UC Browser (If you have)
Gallery
Contacts Storage
Google Play Store
Google Services Framework
Pico TTS
Themes Provider
Application Changed :
Gallery
Contacts Storage
Google Play Store
Play - My Library
Application Data Cleared :
Google Play Services
Google Play Services
Application Removed :
Gallery
Contact Storage
Google Play Store
Google Play Services (all 2)
Themes Provider
Application Replaced :
UC Browser ( if you have)
Contacts Storage
Time Changed :
Google Play Services (all 3)
Power Connected :
Google Play Services
Note : If you have any other apps installed then disable the apps from those installed ones which you dont want to get started automatically. It depends on you.

Thanks!
BTW, don't remove UserDictionary.apk, when i did, my keyboard kept crashing and force closing every 2 seconds.
Dunno if this doesn't happen at CM9+
Just for CM7, make sure you don't remove the app i mentioned above.

CoDDeZ said:
Thanks! BTW, don't remove UserDictionary.apk, when i did, my keyboard kept crashing and force closing every 2 seconds.Dunno if this doesn't happen at CM9+Just for CM7, make sure you don't remove the app i mentioned above.
Click to expand...
Click to collapse
No it wont happen if you use wp7 keyboard with it.. it also has an inbuilt dictionary in it.
Actually, UserDictionaryProvider.apk and LatinIME.apk are related with each other.. so of we remove one of them n try to use th remaining one.. we will ovbviously get force close.
LatinIME.apk , according to me, must be removed.. because it is near about 10mb ( more than 5mb in cm7)..

Supercharge-CrossBreeding Guide[2.2+]
Supercharger CrossBreeder Combo:-- Yes This will help provide a boost.(this is an alternate to Activo Speeder,Adrenaline engine+boost)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Q.Now you guys ask me why to use crossbreeder along with supercharger ?
Ans.Crossbreeder is an entropy generator(faster refreshing & movements generation in apps) along with dnsmasq cached dns requests(speeds the net)It does nothing where the ram is concerned(and ram is a scarce resource).Here's where Supercharger comes in the combination of min-frees , and fast engine flush(its like an automated adrenaline boost!)allows for much better user experience.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
you can get the latest supercharger v6 script form here its called beast but is safe tested and assured.
you can get latest crossbreeder here.
erikcas has already patched the service.jar so you don't have to do anything
Note : - the service.jar doesn't need to be patched for 2.3 or 2.2 as the values are written & read from build.prop or local.prop(preference to build.prop).
now lets begin.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Install CrossBreeder in recovery its a flash-able zip.
now for the interesting part cross-breeder has certain parts of supercharger in it.Mainly Kernel Mods(KAK)
so in supercharger I'm sure you know how to use it if no here's a small guide.
Guide
install an app called script manager(available in the play-store).
inside the app your first prompt will have an option of browse as root choose it(gets highlighted as blue)and click OK
now navigate to where the downloaded script is located and click on it.
on the top corner there should be an icon of superuser (skull with cross bones) click it and the n click run
now you are running the script....
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
now I wont help you with each and every aspect here(Its actually very simple if confused ask).
main point is to accept nearly everything when asked
a few exceptions are.
if you have zip align is any other script like int2ext then choose to disable boot align and zip align and only enable fix emissions.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
launcher strength = die-hard
Note :don't lock home in memory.
min-frees Settings this is your ram manager :
The setting are not available for 384mb devices(like us) so after a lot of trial and error I found the best working categorization they are as follows :-
Old Settings:
for people who like to have a smooth lag-free experience in their current app BUT no multitasking choose balanced(512hp) categorized by me as aggressive.(option 6)
for people who like limited multitasking along with a fairly lag-free experience choose Quick v6 cust-OOMizer. Categorized by me as balanced. (option 10).
for people who like a large amount of apps open simultaneously and don't mid as many apps open choose 256hp balanced categorized by me as Multitasking (option 3).
New Settings: (only for people who know what they are doing).
These are custom minfree values that can be entered from option 10(custOOMize) and not enabling minfree calculator values.
they are still experimental.
Code:
8,12,30,36,41,47----Balanced(same as minfree calculator).
8,12,33,39,44,50----Aggressive
8,12,24,30,35,41----Multitasking
a good guide to understand min-free settings and OOM is this
Note : disable zram(comp-cache).
Note : disable lock launcher in memory.
now when prompted for kernel strength choose default(thus no conflict with crossbreeder).
Detailing (helps use it).
for detailing choose every 4th boot.
Fast-Engine Flush
for fast engine flush(its kind of like adrenaline boost hell its the same). choose every 6hrs(its automatic wont even know its there) recommended for gb or froyo roms....still lagging choose every 3hrs or recommended is 6 hrs.
NOTE FOR GAMERS
enable fast engine flush every . hrs this will remove cached apps every 6mins allowing for free ram i.e a fast and generally lagfree experience though i recommend to change back to 6hrs once game finishes.
this should allow for a fast and smooth performance with no loss of life.
Thanks and Happy Flashing.

Dark Passenger said:
Supercharger CrossBreeder Combo:-- Yes This will help provide a boost.(this is an alternate to Activido)you can get the latest supercharger v6 script form here its called beast but is safe tested and assured.you can get latest crossbreeder here.erikcas has already patched the service.jar so you don't have to do anythingnow lets begin.Install CrossBreeder in recovery its a flash-able zip.now for the interesting part crossbreeder has certain parts of supercharger in it.Mainly Kernel Mods(KAK)so in supercharger I'm sure you know how to use it if no heres a small guide.Guide
install an app called script manager(availabe in the playstore).inside the app your first prompt will have an option of browse as root choose it(gets hilighted as blue).and click oknow navigate to where the downloaded script is located and click on it.on the top corner there should be an icon of superuser (skull with cross bones) click it and the n click runnow you are running the script....
now I wont help you with each and every aspect here(Its actually very simple if confused ask).main point is to accept everything when asked(launcher strength die-hard).minfrees according to me the minfrees set by the calculator are a tad bit too high(they tend to kill everything if you dont multitask this is the best).a better alternative is to use the balanced settings from 512hp(should be enough but if you get black screen in apps try multitasking 512hp)now when prompted for kernel strength choose default(thus no conflict with crossbreeder).for detailing choose every 4th boot.for fast engine flush(its explained kind of like adrenaline boost). choose every 6hrs(its automatic wont even know its there)....still lagging choose every 3hrs(very risky).thats about it.this should allow for a fast and smooth performance with no loss of life.also please disable zram. and lock home in memory.Thanks and Happy Flashing.---------- Post added at 09:44 PM ---------- Previous post was at 09:42 PM ----------@OJ sorry for piling onto your thread but its such a small matter so didn't want to make one of my own.So we can have this as a comprehensive guide.
Click to expand...
Click to collapse
Why sorry..??? You are helping me.. then no sorry..
BTW, thanks for this new trick.. i am gonna try this.. and will include it in the guide as an alternative to Activo Speeder..
One more thing, it would be nice if you improve this guide a bit.. so that all people will get it.. thnx..

OJ said:
Why sorry..??? You are helping me.. then no sorry..
BTW, thanks for this new trick.. i am gonna try this.. and will include it in the guide as an alternative to Activo Speeder..
Click to expand...
Click to collapse
Sorry was for using your thread but rather than having multiple threads on the same topic I thought we should have one with multiple methods.
OJ said:
One more thing, it would be nice if you improve this guide a bit.. so that all people will get it.. thnx..
Click to expand...
Click to collapse
how so...? Edited it a bit let me know what else is needed

can you please explain what is the benefit of installing app as a system app instead of normally installing in internal memory
Sent from my GT-S5670 using xda premium

Dark Passenger said:
Sorry was for using your thread but rather than having multiple threads on the same topic I thought we should have one with multiple methods.how so...? Edited it a bit let me know what else is needed
Click to expand...
Click to collapse
Now it is perfect.. i will add it soon..

[Guide] [MOD] Tweakers Kit...Modified init.d and sysctl system + Flashable Disabler

Warning
If you read this you may go blind and never become erect again.
And there is a possibilty a sattelite will fall from the sky and crush your house
This most likely can be incorparated into any rom on any phone
Feel free to post this anywhere and include it in any rom(Just Give Proper Credit)
I made this about a year ago .Works quite well
it makes tweaking very easy
designed to make tearing apart full tweak scripts apart and testing lines a nd full scripts e easy.
allows you to make up to 7 totally different init.d profiles . the ability to turn on or off any profile.
So now you can develop 7 profiles to boot from and run any profile in realtime
also gives you 2 sysctl.conf to boot from and two more to run in realtime
you need root and busybox
the contents of the foldet ( etc) go in /etc
the contents of ( bin) go in /system/bin the 6 files containing (run) need to be executeable
now you can put install-recovery.sh in /etc to get everything to run at boot
if you have Gametheorys kernel you can use the sysinit i provided in / system/ bin
if you already have either of these used by something else just add the lines from mine to yours
init.d
put scripts in the main folder like normal
there are folders in side
prof1 to prof 6
you can set scripts in those
the foldercalled Scripts is to store unused stuff
also is the initd control where you can use root browser root explorer or any scriptmanager to run the (on,off or run) scripts
Note, i cleaned out all my scripts but decided to leave the main folder with a setup i use the most Remove them or use at your risk
now you have
sysctl.conf through sysctl.conf4 in your /etc folder
load those with sysctl settings
init the init.d/scripts/sysctl are scripts to turn on or off sysct1 and 2 and run 3-4 in tealtime
More (run at will) profiles
init.run folder
load setups in run1 to run6 folders
at anytime use the control panel in init.run to exec any ofrun1 through run6
Note all profile folders have a subfolder labeled (a) those are just like pocket folders to store unused scripts
FLASHABLE DISABLER
This design has something very valuable
each profile has its own (applet) in /system/bin
the install-recovery.sh execs all init.d and prof1 through prof6 applets
but when you use the control panel to turn on or off the profiles you are sinply changing the permissions to each (applet)
So incase you put a bad script in and boots up in a loop or something else
i made a flashable zip of all the bootable (applets) with permissions all at zero
This will render all the bootable profiles un executeable
your new init.d script throws you in a loop flash the
InitdDisableall.zip below and reboot
None of the profiles will execute
So this basically gives you 7 init,d folders . you can choose which ones to boot from
for instance
i load one folder with my settings.one core turned off and cpu set at 810 and a clogged up conservative governor with agressive lmk
say i want to convert movies or play games i boot from an init,d folder i loaded with both cores at full cpu and multitasking lmk and a different governor set for speed
And i added a realtime run feature
this means i can exec any of these folders in realtime without rebooting
Then as an added bonus there is an additional folder that allows you to load your profiles to 6 more folders that you can easily exec in realtime without booting
the sysctl has the same idea
you get 2 sysctl.conf you can load with different settings and choose which one to boot from
plus 2 more sysctl.conf to load that you can run in realtime
The idea is to be able to have many Profiles of settings prefabbed and the ability to exec them quickly
This makes switching from performance and battery saving very easy
It makes testing and designing your profiles very easy as well
Now if you look at Sepero's Bootbuddy
it runs scripts at boot from the ext sd
this is awsome for me, when testing scripts i test some from bootbuddy
i use this for certain things like build.prop or certain kernel tweaks that i am not confident about
if this tweak causes a bootloop i can remove the sd card and bootup without the tweak
after several bootups with no issue, i move the tweak from bootbuddy over to init.d
But if you only want to use bootbuddy and not init.d i added 2 more bootable folders so you can choose from 3 profiles to boot from or turn all off
HOW To Develop your profiles
When i start on a new phone this is my formula
first i find supported govenors
i choose the slowest governor
then make an init.d script to load the governor of choice at boot
Then i clog up the governor,this means i slow it down
I change the settings so it doesnt scale up very fast and scales down instantly
Maybe lengthen the duration between mpdecisions
This is awesome for battery use and further testing
Next I want to start chopping away at the cpu, So I remove all cpu cores but 1
then limit the cpu to a lower scale
I usually start nat around 900 mhz
Example
The lg motion with Gametheory's oc kernel with added governors
i used the Conservative governor setwith
sampling down 1
up threshold 96
down threshold 95 ( or higher)
one core on only running at 918 mhz
So now your phone is much slower,Much better battery life but less responsive
do an antutu benchmark
make sure to look at the Details,each individual score
NOTE if you dont know how to get started
use an app like Kernel tuner
check the settings and selected run at boot with init.d
close kernel tuner it will create an init.d script for you
now go to your init.d folder and make a copy of the script
go back to Kernel Tuner and Disable the run at boot settings. it will remove its scripts
but you have your copy
Now for the ease of profiling you need to Batch your tweaks
small and identical for easy swapping and removal
like all vm tweaks in a script only ,net tweaks in a script only
and save the varied settings in a folder
when you are done you will have several folders of batched tweaks
forinstance various Governor tweaks like i posted below
The Ondemand Governor
A init.d script to load the Ondemand governor with stock settings
but it has 4 scripts for ondemand governor with Slower settings and 4 with above stock settings
Do this for every governor you use
The same with cpu max limits
From here on the idea is to chop away at the cpu but keep the score the same or better (when i am done i will run the phone at 594 or 702 but is close to responsive as the 918,and when i run the phone at stock or better phone is fassst)
Running the phone at core only and at lower speeds make its much easier to indentify the results of individual tweaks
Next you need to look at your system
/proc/sys is a good place to start
here are many settings we are gonna start changes to optimize our phone.
fs,kernel,net and vm settings are here
Its nice to know this as many phones have the same files found here but a few may vary
Please Check Attact File For Download
Tweak Pak Is Not Flashable.
I Am Not Responsible For Any Damage To Your Device. Try It At Your Own Risk.
Sorry For My Bad English
Hope You Understand What I Want To Say
Credit To rhino889a

*Reserved For Nothing( I Think).

Hi there iam new to all this and I want to copy the files from /system/bin/ into said folder but I keep getting copy operation failed is there a way to work around this?
Sent from my ONE TOUCH 4015A using XDA Free mobile app
---------- Post added at 09:30 AM ---------- Previous post was at 08:42 AM ----------
Nvm using new app gotten past first hurdle
Sent from my ONE TOUCH 4015A using XDA Free mobile app

Database Info

welcome