Related
There's tons of questions alike this one, but I want to focus more into this thread "http://forum.xda-developers.com/showthread.php?t=913610". I want my phone's performance to be better, though flashing this custom ROM would cause me to reformat my phone so I'd rather just do the build.prop modification. It's just that i don't know which files to modify, any help?
You need to tell more about your phone flash version rooted or not if rooted what do you have installed on it, if you can do that I can help you.
Kradovan
Oh sorry, totally forgot bout that my phone is running on 2.0.2.A.0.24 rooted.
Short how to
OK we are in business
There is several ways to do what you want, to get some more speed out of your phone. Manually you can make modifications to build.prop but nothing much will happen. A bit smoother operation and bit longer battery life. For direct build.prop
modification you need Root Explorer application. After you install Root Explorer you will be able to browse and modify stuff on your phone.
To modify build.prop start Root Explorer and navigate to "/system" folder and you will find build prop in it. On top of screen you'll see line containing info about how much used and free space is in your system folder and if it is mounted as r/o or r/w. If you are looking at it a first time it should be r/o(read only) and next to it should be button Mount as r/w tap on it and root manager will pop up asking for root permission (allow it) and after that your system folder will will change ro r/w.
Now we can modify anything in system folder so be careful you can mess up your phone (nothing that re flashing wont cure)
Finf build.prop file and long press on it.
Menu will pop up
Scroll almost to the bottom and select open in editor and build.prop will be open in internal editor.
Now you can modify existing lines an add new once
I'll list relevant modifications here:
dalvik.vm.heapsize=26m - Optimal heapsize for most X10s
build.prop Modifications lines need to be typed in
windowsmgr.max_events_per_sec=220 - Makes scrolling smoother
wifi.supplicant_scan_interval=180 - Slows down the WiFi scan to every 3 minutes, saves battery
mot.proximity.delay=150 - Makes the screen off/on proximity sensor more responsive
there is also modification for screen resolution an that line is is already in build.prop
ro.sf.lcd_density=240 - you can change 240 to 200 so LCD density will bi bigger and more stuff will fit on your screen but some applications will not like that but you can change that back at any time.
These are basic tweaks and not much of a bang
If you want Quadrant speed up to 855 and dual touch there are lot more of changes to be made.
If you are interested you can search developer part or I can write it up for U.
P.S. back button will save build.prop and make backup of your original file
After save restart your phone so changes can take place.
You can copy build.prop to your SD card and then copy it to PC and edit it there but after copying it back to phone you need to set permissions as they were on original file.
Good luck Kradovan
kradovan said:
OK we are in business
There is several ways to do what you want, to get some more speed out of your phone. Manually you can make modifications to build.prop but nothing much will happen. A bit smoother operation and bit longer battery life. For direct build.prop
modification you need Root Explorer application. After you install Root Explorer you will be able to browse and modify stuff on your phone.
To modify build.prop start Root Explorer and navigate to "/system" folder and you will find build prop in it. On top of screen you'll see line containing info about how much used and free space is in your system folder and if it is mounted as r/o or r/w. If you are looking at it a first time it should be r/o(read only) and next to it should be button Mount as r/w tap on it and root manager will pop up asking for root permission (allow it) and after that your system folder will will change ro r/w.
Now we can modify anything in system folder so be careful you can mess up your phone (nothing that re flashing wont cure)
Finf build.prop file and long press on it.
Menu will pop up
Scroll almost to the bottom and select open in editor and build.prop will be open in internal editor.
Now you can modify existing lines an add new once
I'll list relevant modifications here:
dalvik.vm.heapsize=26m - Optimal heapsize for most X10s
build.prop Modifications lines need to be typed in
windowsmgr.max_events_per_sec=220 - Makes scrolling smoother
wifi.supplicant_scan_interval=180 - Slows down the WiFi scan to every 3 minutes, saves battery
mot.proximity.delay=150 - Makes the screen off/on proximity sensor more responsive
there is also modification for screen resolution an that line is is already in build.prop
ro.sf.lcd_density=240 - you can change 240 to 200 so LCD density will bi bigger and more stuff will fit on your screen but some applications will not like that but you can change that back at any time.
These are basic tweaks and not much of a bang
If you want Quadrant speed up to 855 and dual touch there are lot more of changes to be made.
If you are interested you can search developer part or I can write it up for U.
P.S. back button will save build.prop and make backup of your original file
After save restart your phone so changes can take place.
You can copy build.prop to your SD card and then copy it to PC and edit it there but after copying it back to phone you need to set permissions as they were on original file.
Good luck Kradovan
Click to expand...
Click to collapse
What are the tweaks to change LED notification in 2.2 beta 3..i get one led flash in 10 seconds,normally it is 3 seconds.
How can I make my quadrant speed up to 855 or more?
Sent from my X10a using XDA App
kunalgahlot said:
What are the tweaks to change LED notification in 2.2 beta 3..i get one led flash in 10 seconds,normally it is 3 seconds.
Click to expand...
Click to collapse
i have quasition plz
any lines can i add them to build.prop to get mutitouch?and how can i get arabic langauge from sony ericsson without change my region nombe
my phone x10i rooted F:2.0.a.0.504 eclair 2.1update1
I've already set up simple tweaks like dual touch, buzybox and xRecovery, and yeah, i want the extra tweaks for 855 quadrant speed, mind writing it up?
JIT
hawk13 said:
I've already set up simple tweaks like dual touch, buzybox and xRecovery, and yeah, i want the extra tweaks for 855 quadrant speed, mind writing it up?
Click to expand...
Click to collapse
To get speeds up to 855 there is only one thing to do that is to install JIT 0.2
For you the easiest way to do that it is through xRecovery.
The procedure and files are described in http://forum.xda-developers.com/showthread.php?t=885977&highlight=JIT+xRecovery
Download the file and follow the instructions to the letter especially resetting dalvick cash if you do not clear cash your phone will suffer random crashes. Quadrant scores will float from 720 to 855 depending on what is running on your phone.
Hope that this is what are you looking for.
Good luck Kradovan
GREAT!
I got a quadrant score of 831, thanks dude! although it's still below Galaxy S, i still did it's thing ^^
hawk13 said:
I got a quadrant score of 831, thanks dude! although it's still below Galaxy S, i still did it's thing ^^
Click to expand...
Click to collapse
Ignore that mate, quadrant is OK, but certainly not definitive. My brothers Galaxy absolutely destroys my x10 on quadrant, but actually using the phone mine is so much faster and smoother. Plus the fact he cannot even get close to me on Linpack is highly amusing.
Linpack? that's new, what's it do?
An app that tests the CPU performance.
So heapsize=26 is the best for the X10?
Flo95 said:
An app that tests the CPU performance.
So heapsize=26 is the best for the X10?
Click to expand...
Click to collapse
I prefer a heapsize of 32, suits me better. It is quite subjective though.
Sent from my X10i
There's a great build.prop editor in the newest flash tool.
Also, check the modded 2.1 camera thread in the apps section for some lines to add that improve video capture (works on stock cam too)
Sent from my X10a using XDA App
Liberty Toolbox
https://market.android.com/details?id=com.jrummy.liberty.toolbox
Liberty toolbox - in the market - free ware
Although this was built for Motorolla devices, it works on the X10 and most functionality is fine, including ability to mod your bootscreen, zipalign apk files, clear cache, modify build.prop and other useful tools.
Here is full info on the app functions and wish it ran fully for X10 - only about 80% working but what you are asking for is covered.
• App Management:
* Apps2SD
* Remove/Backup system/data apps
* Install Add-Ons on the fly (blur, non-blur, extras, etc.)
* Backup/restore feature
• Liberty Mods
* Switch between transition animations
* Change boot logos
* Set Build Properties * File editor included by Fr4gg0r *
* Install Fonts
* Install Themes from the toolbox
* Pulldown-bar text editor
* Icon Chooser (change application and battery icons)
• Liberty Tweaks
* Ad Blocker (Block/Unblock)
* Cache Manager (clear/move to SD)
* Free Memory
* Manage Boot Animation
* Mount system rw, fix permissions, zipalign apps, etc.
• Reboot Options
* Reboot, reboot bootstrap, reboot recovery, powerdown
• Settings
* App Theme (change theme of toolbox)
* Notify for ROM updates/patches
* Lockscreen Settings
* Recovery safe mode
* Overclocking
* Sysctl Support
* Camera Shutter Sound
* Tools (Spare Parts, Dev Tools, Testing Menu)
* Restore apps feature
* Set install location on boot
* Zipalign apps on reboot
* Clear cache on reboot
* Fix permissions on reboot
Fr4gg0r
de.Fr4gg0r.SGS.Tools_55.apk
Although not designed for X10 - the aspect for build.prop mods was developed by Fr4gg0r who is an XDA member and into Galaxy S development, very good with it as well I might add.
This seems to work for me!
i definatly prefer to change build.prop on flashtool.
can type better, see better and dont screw with that file lol
i cant imagine the 5/6 changes/adds i made typing on phonne
liberty
It didn't seem to be able to change my boot screen though...
Re:liberty
scratch that, dint read about the liberty ROM installation part.
I am running stock rooted RUU released on 4-19 by jcase.
I loaded Adrynalyne’s kernel 5.10.11 [2.6.32.21] control freak v2. I am able to adjust the VDD levels on the fly using terminal through commands such as
Echo “-25” > /sys/devices/system/cpu/cpu0/cpufreq/vdd_levels or adjust each individual speed voltage. Unfortunately, these settings reset after a reboot.
There are two files labeled 00vdd_levels with rwxr-xr-x permissions and a 00vdd_levels~ with rw-r--r—permissions in the /system/etc/init.d folder. I have tried to manually change the voltage levels through root explorer and changed the name of the files to 99vdd_levels, but the stock voltages reload after each reboot. I have spent several hours trying to get these modifications to be permanent. I may be searching for the wrong edit, but I really need some assistance.
Please help me with the scripts or recommend a thread that has the instructions on how to perform these tweaks. TIA
The one with the ~ at the end was probably generated by vi when someone didn't save properly. The file without the ~ is the one to edit. Make sure your settings aren't commented out with a hash (#)
ETA: In fact the ~ file may also be causing a problem. Remove it and see what happens.
Thanks for your reply. I deleted ~file and have spent hours trying multiple methods to get the script working, but I have not been successful. I know have 10 posts so I can post my issue in the development thread made by the kernel dev and hopefully he can help me since he created the kernel.
I wanted to post this on the 500+ page GSB ROM thread, but alas I need 10 posts under my belt first (9 now!).
Like others who upgraded to GSB v3.2, my soft-key lights quit working. Apparently v3.3 fixed this, but I'm still having the same issue. I wiped dalvik, but did not do a full wipe. Is a full wipe necessary to fix this issue?
Also, I'm having a lot of problems getting zeppelinrox's SuperCharger scripts to work. When I run them in Gscript, I get tons of stderr's. So I rebooted into Clockwork's recovery, mounted /system, mounted /data, and mounted /sdcard. Then I ran the script again from adb. It looks like the script is trying to make changes to /system/etc/rootfs/init.mapphone_umts.rc. This file doesn't exist on my phone, I don't even have the rootfs folder. It appears as though other GSB3.3 users aren't having this problem. Why is mine different?
[poo]
Scratch that first part. The lights are working. I just never paid much attention to them before they stopped working, didn't realize that they were triggered by a sensor. Duh!
I still have the SuperCharger issue, though. I'd really like to get that working!
[poo]
Use script manager to run the script.
I'm making progress, but I'm not quite there yet. I got the same results with Script Manager. Then I noticed that the scripts included with GSB v3.3 were v5 of SuperCharger. So I tried v6 SuperCharger in Script Manager and things seemed to go much much better. The bulletproof launcher setting is sticking after a reboot, but the minfrees get reset back to 6, 8, 16, 36, 40, 40 every time. I've tried all three balanced settings.
[poo]
poo706 said:
Scratch that first part. The lights are working. I just never paid much attention to them before they stopped working, didn't realize that they were triggered by a sensor. Duh!
I still have the SuperCharger issue, though. I'd really like to get that working!
[poo]
Click to expand...
Click to collapse
Sensor so that they only come on when it's dark? Was wondering the same...
I'll follow this thread since I don't have the 10 either and want to get the SuperCharger scripts working as well, because I'm getting the same errors others are getting.
v3.3 also fixed a bug I was having where if I had the Google web widget search on my homescreen and hit the search magnifying glass softkey, the Google widget would move to the top of the homescreen and almost be stuck there, but looks to be good now.
Have you tried SuperCharger v6 with Script Manager, or just v5 with Gscripts?
[poo]
v5 was only for milestone.
You have to use V6.
There might be something overwriting minfrees on boot.
No wonder everyone's having so many issues. I think we all assumed that shed would have bundled the correct version with GSB.
Any idea, off the top of your head, what programs might be also trying to set minfrees at boot?
[poo]
poo706 said:
Have you tried SuperCharger v6 with Script Manager, or just v5 with Gscripts?
[poo]
Click to expand...
Click to collapse
Hmm, no idea? I installed and went into Script Manager and ran cRom-BulletProofLauncherOnly.sh and ran Balanced3, but got the errors all others were getting.
Edit: I used Script Manager and ran those scripts in /gscript. The v6 versions are in a different thread? I just found them, I'll have to install them at home since I don't have my charger here.
Edit x2: Looks like it's one .sh file. Run it in gscript and then select the type of memory management you want, that's it right? wshed says he's running bullet and balanced3. How do you get bullet running?
Download this .txt file and remove the .txt extension:
http://forum.xda-developers.com/attachment.php?attachmentid=586107&d=1304484146
Run that .sh script with Script Manager. It's all in one, no need for all of the individual scripts that were included with GSB. This is the main thread for SuperCharger:
http://forum.xda-developers.com/showthread.php?t=991276
As I said, the script works great. Bulletproof launcher setting sticks, but not memory settings.
[poo]
Use Script Manager and load the single V6 Script.
If you have Auto Memory Manager, disable superuser permissions so it doesn't load settings on boot.
If you have Autokiller Memory Optimizer, you can disable the apply settings on boot option.
If you need to, you can always use Script Manager to load /system/etc/init.d/99SuperCharger on boot.
zeppelinrox said:
Use Script Manager and load the single V6 Script.
If you have Auto Memory Manager, disable superuser permissions so it doesn't load settings on boot.
If you have Autokiller Memory Optimizer, you can disable the apply settings on boot option.
If you need to, you can always use Script Manager to load /system/etc/init.d/99SuperCharger on boot.
Click to expand...
Click to collapse
Yea, the big confusion was everyone was using the v5 scripts and nothing was working... I'll def hit up the v6 tonight, thanks.
I've never installed Auto Memory Manager or Autokiller Memory Optimizer, so those aren't the culprits. Using Script Manager to load /system/etc/init.d/99SuperCharger on boot did work. But I'm a little confused. Aren't all the scripts under init.d run at startup anyway? If true, then using Script Manager to load S99SuperCharger just runs it again, right?
[poo]
Thats right.
Using SM to load it on boot is just a workaround until you figure out what else is loading minfree values.
Since you don't have a minfree app installed, it there may be something else in the init.d folder or perhaps another boot script folder such as a userinit file or folder
I think I found it, /init.rc seems to be the culprit. I take it that init.rc gets executed after all of the scripts in init.d? I'd really rather not have to load SM at boot every time just to override the settings in init.rc. I assume that editing init.rc in some form or fashion would be the best way to go? I could either change the values in init.rc and remove S99SuperCharger, or leave S99SuperCharger in place and comment out the conflicting lines in init.rc.
Thanks for all the help, by the way!
[poo]
Editing init.rc isn't the right approach. It looks as though it gets rewritten at startup. I pulled init.rc via adb, added some text to a commented out line, pushed it back, and rebooted. The text I added was gone after the reboot. So now the question is: how and when is init.rc getting created? If init.rc is already in place by the time 99SuperCharger gets run, maybe 99SuperCharger could just modify init.rc prior to its execution.
[poo]
Actually, init.rc wouldn't interfere with 99SuperCharger.
On the milestone there is:
/init.rc
/init.mapphone_umts.rc
/system/etc/rootfs/init.rc
/system/etc/rootfs/init.mapphone_umts.rc
The first 2 items I can't edit they get created on boot.
The 2 items in the rootfs folder I can and it sticks.
If I have a init.d/99SuperCharger file, it would supercede the *umts.rc file and that file supercedes the init.rc
So the bootscript>*umts.rc>init.rc
I think that only way 99SuperCharger doesn't stick is if your ROM doesn't even load it (there actually was a bug in CM7 for milestone where it didn't load) or you have a userinit.d folder or file
edit: okay look for folders...
/data/local/userinit.d
/sd-ext/userinit.d
or files
/data/local/userinit.sh
/sd-ext/userinit.sh
Also, I wonder if you do have an *rc file (like init.mapphone_umts.rc) that can be hacked... heh
Already looked in both of those places, no files or folders of interest. What creates init.rc, do you know?
[poo]
Its in the boot.img file I believe.
Maybe reflashing the rom will fix it?
Sent from my Milestone Powered by my V6 SuperCharger
I'm trying to run the v6 version but I can't find the Interactive option anywhere in Script Manager. I go to config and it's not there. Help?
Edit: found the new version of script manager you touched the screen for input haha, and got it running.
In most of custom ROM description I see
"Dalvik to cache tweak"
"Memory tweak"
etc
What is this ?
Search here and google do not help much.
Modified dalvik.vm.heapsize and Low level memory killers possibly
《tapatalked from galaxy s3》
What exactly modified if there is no init.d scripts ?
Which file(s) added modified for the tweaks ?
Most certainly only the build.prop
It's the configuration files that manages most of the Android userland settings including DPI, Cache, ...
There exist several apps in the market which allow you to hot-change the values. Requires root of course.
However you should only change the values you understand and keep a backup copy of the file. You can mess up the phone pretty bad to the point of not booting or not displaying an usuable interface. If you're backed up, you can always recover through ADB (in Recovery mode) by replacing the file with the original.
I find there is no real need to tweak the file, it's good as-is.
I'd like to remove tweaks, already included in most custom ROM's
Create your own rom
Sent from my GT-I9300 using xda premium
For All Defy and Defy + JB Roms
*****Disclaimer***
- Before flashing the BM.Memfree.Defy.zip please patch your service.jar first and place it in the zip /system/framework/
You can get your services.jar from the rom you're currently using with a root explorer. It is located in system/framework/
To Patch it read from *Optional Memfree tweak* in the quote....
Thanks to Husi10 for the heads up
Please thank brainmaster for the zips - Here
Also lambgx02 for his work on the seeder - Here
Below is the original quote from brainmaster read it to know more about the tweaks
brainmaster said:
Here is the description of the Tweaks:
Scripts in the /system/etc/init.d folder:
08dalvik - Moves the Dalvik cache from the ext4 /data/dalvik to the faster yaffs /cache/dalvik partition
95zipalign - This is more enhanced zipaligning method. Its zipaligning the apps in the /system/app and /data/app. It also creates the database that contains infos on apps that are already zipaligned, and checks that databe on reboot. If all apps are zipaligned, it skips the zipalign process. Zipaligning is useful because its reducing the amount of used RAM
99bmtweak - Contains the tweaks that I've collected and enhanced over the time. Included are IO tweaks, TCP tweaks, SDCard ReadAhead tweak, SQLite Vacuum Database tweak
hosts file in the /system/etc folder:
Hosts file makes your Phone ADFree.
resolv.conf file in the /system/etc folder:
Google DNS Servers
placeholders in the /system/app and /data/app folders:
If you want to add a system app or install data/app with the CWM Zip file, just drop the apk in the /system/app or /data/app folder in the CWM Zip file and they will be installed when you flash the CWM Zip.
/kernel folder:
Enables the init.d script support.
updater-script in the /META-INF/com/google/android folder:
Deletes the Cache and Dalvik Cache, mounts the /data and /system partitions, copying the needed files. It sets the permissions. If you are editing that file, be SURE to use the Notepad 2 or Notepad ++ and use the Unix file system encoding when saving the file, not the regular Notepad Windows app.
build.prop tweaks Injector in the /tmp folder:
Injects the values in the /system/build.prop file. The /tmp/mytweaks.sh file shouldn't be edited! The file /tmp/misc contains the buildprop tweaks. You can add your own build.prop tweaks in that file.If you are editing that file, be SURE to use the Notepad 2 or Notepad ++ and use the Unix file system encoding when saving the file, not the regular Notepad Windows app, also IF you use comments (#Disable.ADB.Notification.Icon), DON'T use spaces, use ONLY the underline or dot character! These tweaks are included:
Code:
#Disable.ADB.Notification.Icon
persist.adb.notify=0
#Disable.Google.OTA.Checkin
ro.config.nocheckin=1
#Disable.Google.Reports
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
#Enable_Google_DNS_Servers
net.dns1=8.8.4.4
net.dns2=8.8.8.8
#HSPA.Tweaks
ro.ril.hsxpa=2
ro.ril.gprsclass=12
ro.ril.hsdpa.category=16
ro.ril.hsupa.category=8
#Dalvik.Optimization
dalvik.vm.execution-mode=int:jit
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,o=v
Installation
Step 0: You must be rooted!
Step 1: Download the Busybox installer app and install the Busybox to /system/xbin. Again - install the Busybox to /system/xbin not to /system/bin!
Step 2: Reboot to recovery and install the BM.Tweaks.NEXUS.S.zip file.
Optional Memfree tweak - set to 100 MB:
In order to use the Memfree tweak on every ROM, extract the /system/framework/services.jar from the ROM and upload it to android.mimic.ca, let the site edit the file, download the edited services.jar and put it in the BM Memfree zip file. Then flash the BM Memfree zip in the Recovery.
The attached Memfree zip is for the stock JZO54K ROM.
Optional BM Seeder:
You can read everything about the tweak here.
This is my version adjusted for the Nexus S.
How can I be sure that the tweaks are working?
Open the RootExplorer and click on the /cache folder. IF the dalvik-cache folder is present, THEN the tweaks are working properly. Check also your /system/build.prop file for the #Brainmaster Tweaks area.
The tweaks are universal - not ROM version related, and can be flashed over any ROM but ONLY for NS or NS4G.
Disclaimer:
ALWAYS make a NANDroid Backup of your current ROM so that you can go back if you don't like the tweaks.
I will NOT reply any users PM's regarding this thread or my ROMs, only the DEVs should contact me over PM.
If you are user and have questions, write HERE in the thread.
BEFORE asking any questions, make sure that you read this post.
Click to expand...
Click to collapse
Ok So what I have done here is to modify the updater-script to work for the defy.... That's it
I haven't really touched anything else as am not a dev so can't tweak it specially for our defy but since our hardware is similar to the nexus s then I think it should be fine
Notes -
- People with a lot of apps installed on the phone either delete the 08dalvik file from the zip before flashing or after because you may not be able to install apps after this is due to the tweak using the /data partition for dalvik-cache.
- If you have already flashed the zip then Delete 08dalvik from system/etc/init.d.
-You want want to also check this out Don't use this and seeder zip at the same time.
Instructions - Flash zips in recovery and reboot
Don't forgot to patch your services.jar if your using the BM.Memfree.Defy.zip
Changelog
Seeder -
Updated rngd binary for seeder ---- It deepsleeps now noticeable reduced battery drain
BM tweaks & Memfree -
updated to the latest version from brainmaster
Downloads
http://www.mediafire.com/?k0gxranyqnt9w
Mirrors are always welcome
Credits for the original work :
Brainmaster
Lambgx02
Patch the services.jar? How would I do that? I understand the rest
Thank U For the Brainmaster's Tweaks for our Defy
ldnjoe said:
Patch the services.jar? How would I do that? I understand the rest
Click to expand...
Click to collapse
Updated OP with more tips
Kayant said:
Updated OP with more tips
Click to expand...
Click to collapse
In order to use this tweaks should I remove the tweaks that I have from pimp my rom first?
There is any difference with the included in pimp my rom?
This ones are better?
Edit: I don't think that the memfree or seeder binary is included in pimp my rom. I'll give it a try in PAC.
I'm currently using some tweaks I have been collecting and they give me some good results.
Hope this will increase the performance even more.
So, any feedback on results yet? I know it's a fresh mod, but still
Nailtrail said:
So, any feedback on results yet? I know it's a fresh mod, but still
Click to expand...
Click to collapse
Haven't really tested it fully yet but when I tested CM10 with chrome & a some apps in the background it was smooth I mean there was not lag in scrolling for me on chrome when browser theverge.com but as always there was whitespace because of our slow phone
The BM seeder thing really does work I think because one place I see the phone being me optimized is when you wipe dalvik cache for instance It takes ages for it to optimize the apps again if you have many but with the BM seeder tweak installed the process for me was at least two times faster
Btw I had all tweaks installed.......
Thank you Kayant for the release, that was really fast!
I flashed everything, seem to be great as excepted! I don't know if it's placebo effect but when I saw "optimizing app" during 3 time less than usual I think that's powerful.
We need more time to debate about stability or battery but my first impressions are great.
Thank you again for your awesome work.
Sent from my MB526 using xda app-developers app
Husi10 said:
Thank you Kayant for the release, that was really fast!
I flashed everything, seem to be great as excepted! I don't know if it's placebo effect but when I saw "optimizing app" during 3 time less than usual I think that's powerful.
We need more time to debate about stability or battery but my first impressions are great.
Thank you again for your awesome work.
Sent from my MB526 using xda app-developers app
Click to expand...
Click to collapse
+ 1 its the same here.. just testing now..
Nailtrail said:
So, any feedback on results yet? I know it's a fresh mod, but still
Click to expand...
Click to collapse
At the moment am just testing...
I only install the seeder binary but I can say that i had seen an improvement in the default browser and in the play store.
I don't see much lag on it. I don't have much bandwidth so could be it that prevent me from seeing the hole potential of the seeder.
Sometimes stuck from loading the play store content for example but it doesn't bother at all.
I'm very happy with the results.
will be testing this and report back later.
here the link for services.jar mod for cna 4.0 by kayant.
credits to blk_jack
Seems to be working
Thanks Kayant! :good:
Seems to be working... the browser works faster and the lock screen waking is much faster....
There seems to be an improvement in gaming performance....
still testing...
do I need to wipe cache or dalvik before or after installation?
Edit: never mind, I'm testing it now, first impression the load of apps is super fast, I have 170 apps loaded in less than 2 minutes, awesome!
thanks for sharing.
modified a version from brainmaster's zips cause I don't like all build.prop changes and I'm to lazy to patch service.jar
the seeder mod with init.d script from brainmaster works better than the original one load only, it makes the phone faster in response and loading apps.
the zipaglin works and the other tweaks else, but need more testing.
@Kayant
The website for modding services.jar says its for ICS and I had read in V6 thread that the website method wont work for JB. In his second post he gives alternate method.
zopeon said:
@Kayant
The website for modding services.jar says its for ICS and I had read in V6 thread that the website method wont work for JB. In his second post he gives alternate method.
Click to expand...
Click to collapse
Thanks.... Will update the OP later ....
Edit - OP updated now checking to see if the tweaks need updating (v6)
Let's Go ^_^
zopeon said:
@Kayant
The website for modding services.jar says its for ICS and I had read in V6 thread that the website method wont work for JB. In his second post he gives alternate method.
Click to expand...
Click to collapse
Agree, since i modified the services file and put the mem tweak started to get much more lag than without it.
It won't work in PAC.
I just put the 08dalvik in init.d, along with 95zipalign and the zipalign file into xbin. That should do right? I mean I want just the dalvik to /cache and the zipalign tweaks.
So I have been using V6 supercharger for ages. Now I turned off the supercharger zipalign option and then realized there is no zipalign in /xbin for CM10, it has never been running till now!
So, guys... One should probably disable V6 Supercharger completely, for these tweaks to work as they should? Or not?
I've finally supercharged my phone after a couple of months and now, a week after flashing, it's still running at the same smooth speed, where it would slow down after half of that time without the supercharger...
Want to try this, anyway, so, are the two compatible in any way..?
Cheers, Kayant, for the Defy version!
niksy+ said:
So, guys... One should probably disable V6 Supercharger completely, for these tweaks to work as they should? Or not?
I've finally supercharged my phone after a couple of months and now, a week after flashing, it's still running at the same smooth speed, where it would slow down after half of that time without the supercharger...
Want to try this, anyway, so, are the two compatible in any way..?
Cheers, Kayant, for the Defy version!
Click to expand...
Click to collapse
I suppose you should turn off V6 if you choose the Memfree tweak, and also zipalign.
But see my post above, zipalign probably isn't running if you are using CM10, check system/xbin to make sure!
But personally I let V6 handle the memfree and stuff, I know it works so I'd rather not try something else