Hi All,
Share your tips here for boost up your Archos,
Anyone use extra SWAP instead of official one (64M)?
I will use 512MB for SWAP in /data/swap512 and custom /data/local.prop to enhance my Archos, but it seems not enough.
Update: 14-07-2011
My Archos seems faster than before since I've installed:
1. Sysctl Config
2. Spare Parts 4
in Sysctl Config, I use belowsetting:
min free kbytes: 32568
dirty ratio: 5
dirty background ratio: 3
vfs cache pressure: 1
Oom allocating task: Enabled
also I ticked compcache in Spare Parts then Reboot.
*I think Swap and Compcache can not be turn on in same time since I type 'free' in terminal and there is no swap memory anymore.
please share yours here.
Cheers!
Leo
I'll be honest and say that my Archos 70 is running like my Nexus S, it's mental man, I can't believe I'm using the Archos, I've got no lag, it's super fast, looks good, no hicups, and thats after finding scripts, build, local.prop tweaks, sysctl.conf tweaks, android tweaks, ALL of which I found here, just search for build.prop tweaks, or sysctl tweaks and you'll find them,
You need ROOT by the way
@LeoNg628:
What do you think you want to do that would need 512MB swap?
What is slow/laggy?
If Uruk is slow and laggy, you are doing something serious wrong.
You do understand that the archos is not the replacement for a quadcore gaming computer?
fzelle said:
@LeoNg628:
What do you think you want to do that would need 512MB swap?
What is slow/laggy?
If Uruk is slow and laggy, you are doing something serious wrong.
You do understand that the archos is not the replacement for a quadcore gaming computer?
Click to expand...
Click to collapse
Claim down bros
I am just curious and looking for some tweaks to boost up my Archos more than now.
I've installed UD 1.1rc once, but I think Custom ROM is not yet suitable for my Archos since my Archos 70IT is A70H, which is a HDD version.
If I install the UD into my Archos, it will automatically installed into my HDD and it will cause the battery drain quickly and not usable...T^T
Therefore, I am already give up on SWAP 512, because it make my Archos very unstable and reboot sometimes....
So, I just open a thread for our Archos user to share their great info here and let us discuss here...
btw, do you have any idea to boost up the official FW?
(I'm using 2.3.81 with rw Root)
SWFlyerUK said:
I'll be honest and say that my Archos 70 is running like my Nexus S, it's mental man, I can't believe I'm using the Archos, I've got no lag, it's super fast, looks good, no hicups, and thats after finding scripts, build, local.prop tweaks, sysctl.conf tweaks, android tweaks, ALL of which I found here, just search for build.prop tweaks, or sysctl tweaks and you'll find them,
You need ROOT by the way
Click to expand...
Click to collapse
Firstly, thanks your hints.
But any source that directly workable on our Archos?
I've found this:
http://forum.xda-developers.com/showthread.php?t=929448
and this:
http://forum.xda-developers.com/showthread.php?t=1015108
also a great help Spare Parts:
http://forum.xda-developers.com/showthread.php?p=12310102
VM tips:
http://forum.xda-developers.com/showthread.php?t=523707
Build.prop hints from Moto:
http://forum.xda-developers.com/showthread.php?t=771232
second:
http://forum.xda-developers.com/showthread.php?t=1026169
Does the Multiboot work on the 70H?
If it works, that gives a boost allready because it has a compcache and some other tweaks.
It also comes with root and an union fs that lets you change the system files of the std android.
fzelle said:
Does the Multiboot work on the 70H?
If it works, that gives a boost allready because it has a compcache and some other tweaks.
It also comes with root and an union fs that lets you change the system files of the std android.
Click to expand...
Click to collapse
I haven't try multiboot on my A70H, I've just have installed SDE after I buy it.
And I gain compcache after install Spare Parts..
Hey all - hopefuly this is the correct place for this question. I am developing a custom kernel for the Samsung Replenish baseod off of samsungs open source code. I have thus far gotten the kernel to compile and run just fine on the phone. I have also added the SmartassV2 and Interactive governors. No matter which one i set as default through the phonemodel_defconfig, each time I recompile and load the new kernel, it always default back to OnDemand governor.
I have no problem selecting either of the 2 new governors through SetCPU (and the setting does stick from boot to boot as long as I select "Set at Boot") so I know the governors are properly linked into the kernel. I thought that the kernel would start with the default one I selected, but it does not. Is this how thigs are supposed to operate, or am I missing something. I did update the cpufreq.h file in the include directory.
Any suggestions - is this even the correct place for a post that is this low level.
Thanks!
dmrlook said:
Hey all - hopefuly this is the correct place for this question. I am developing a custom kernel for the Samsung Replenish baseod off of samsungs open source code. I have thus far gotten the kernel to compile and run just fine on the phone. I have also added the SmartassV2 and Interactive governors. No matter which one i set as default through the phonemodel_defconfig, each time I recompile and load the new kernel, it always default back to OnDemand governor.
I have no problem selecting either of the 2 new governors through SetCPU (and the setting does stick from boot to boot as long as I select "Set at Boot") so I know the governors are properly linked into the kernel. I thought that the kernel would start with the default one I selected, but it does not. Is this how thigs are supposed to operate, or am I missing something. I did update the cpufreq.h file in the include directory.
Any suggestions - is this even the correct place for a post that is this low level.
Thanks!
Click to expand...
Click to collapse
As far as i know, cpu scaling governor can also be set by init script in ramdisk and /etc/init.d other than default setting in kernel config. You might need to check if there's any init script that contain a line like :
'write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand '
or
'echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor'
Those lines will set the cpu scaling governor everytime the phone reboots.
In my device (xperia mini pro), that first line is in init.semc.rc in root folder of ramdisk. It should be different in your device
The second line is usually in a script in init.d folder, but stock rom usually doesn't support init.d, so afaik it only exists in custom rom.
greenAlgae said:
As far as i know, cpu scaling governor can also be set by init script in ramdisk and /etc/init.d other than default setting in kernel config. You might need to check if there's any init script that contain a line like :
'write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor ondemand '
or
'echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor'
Those lines will set the cpu scaling governor everytime the phone reboots.
In my device (xperia mini pro), that first line is in init.semc.rc in root folder of ramdisk. It should be different in your device
The second line is usually in a script in init.d folder, but stock rom usually doesn't support init.d, so afaik it only exists in custom rom.
Click to expand...
Click to collapse
Thanks for the response. the kernel does support init.d (now, stock did not) but there are not scripts in there as of yet. I also went through all the other startup *.rc scriipts and found one that was echoing ondemand into the scaling_governor file. I tried both comment the line out and reflashing new ramdisk, and chaning it to echo smartassV2 and reflashing new ramdisk. In all cases, Ondemand still comes up.
I've also added a script to init.d that echos governors other than ondemand to scaling_givernors, and still, when the phone is booted, ondemand it is. Note that if I echo some other governor to the file at this point, it does change (I imagine this is what setcpu does in the background anyway).
Could the android system system itself be changing it to ondemand?
Thanks for the help!
dmrlook said:
Thanks for the response. the kernel does support init.d (now, stock did not) but there are not scripts in there as of yet. I also went through all the other startup *.rc scriipts and found one that was echoing ondemand into the scaling_governor file. I tried both comment the line out and reflashing new ramdisk, and chaning it to echo smartassV2 and reflashing new ramdisk. In all cases, Ondemand still comes up.
I've also added a script to init.d that echos governors other than ondemand to scaling_givernors, and still, when the phone is booted, ondemand it is. Note that if I echo some other governor to the file at this point, it does change (I imagine this is what setcpu does in the background anyway).
Could the android system system itself be changing it to ondemand?
Thanks for the help!
Click to expand...
Click to collapse
Well, actually I never try to change the default governor from ondemand before. Partly because I compiled my kernel using official/stock kernel source, so there's only those stock governor options and ondemand seems to be the best option. My phone is SE Xperia Mini Pro / sk17i and currently running Freexperia CM7 rom. The kernel provided has very good performance but seems to cause the battery draining too fast for me, so I compiled a 'stock' kernel to use with it.
After your post above, I tried to add more governor options from freexperia kernel source, recompiled the kernel, edit the init script in ramdisk, and flashed it to my phone.
Here's my result:
- the script in init.d doesn't seems to change the default governor. I don't know exactly why. Other script in init.d seems to run just fine, I can set scaling_min_freq and scaling_max_freq with it. I also check the permission, it's rwxr-x-r-x, but it doesn't seem to be executed at boot.
- in every startup, the rom executes the script in /data/local/userinit.sh too, but setting default governor from that script also doesn't succeed.
- only thing that can change the default governor is adding the line 'write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor smartassV2' in 'on boot' section of the init.semc.rc file.
I'm not a developer and i know every rom might be different. So you might need to ask in your rom specific thread, one of the devs might be able to help you there.
Otherwise, you can always set the default governor at boot using app like 'setcpu' or ' No-frills CPU Control'
dmrlook said:
Hey all - hopefuly this is the correct place for this question. I am developing a custom kernel for the Samsung Replenish baseod off of samsungs open source code. I have thus far gotten the kernel to compile and run just fine on the phone. I have also added the SmartassV2 and Interactive governors. No matter which one i set as default through the phonemodel_defconfig, each time I recompile and load the new kernel, it always default back to OnDemand governor.
I have no problem selecting either of the 2 new governors through SetCPU (and the setting does stick from boot to boot as long as I select "Set at Boot") so I know the governors are properly linked into the kernel. I thought that the kernel would start with the default one I selected, but it does not. Is this how thigs are supposed to operate, or am I missing something. I did update the cpufreq.h file in the include directory.
Any suggestions - is this even the correct place for a post that is this low level.
Thanks!
Click to expand...
Click to collapse
today i was looking for a solution like you and watched this post,finally i could solve the problem.Look at the scripts on /system/etc folder, in my case there was a script located there that changed the governor to ondemand,its name init.qcom.post_boot.sh maybe on your device it has other name.
old thread, i know, but im attempting to root a samsung replenish thats running 2.3.6. can anyone help? nothing is working.
EDIT: LOL. i was thinking "this phone is that old...? this is ridiculous that its running a higher form of gingerbread than my 4 month old phone is......" but i was looking at the join date not the post date, and i thought the thread was 3 years old. LOL
This thread Is a compilation of speed tweaks and mods I have gathered from the forums and used on my Galaxy Player 4.0. I can vouch for all of these tweaks, and all provide at least a modest performance improvement. I claim no credit for any of these mods, the glory goes to the fabulous devs who have created them.
To show you the possible performance increase, I have all of these tweaks installed with the Terrasilent kernel and Klin's R5 ROM, plus an Overclock to 1.5 GHZ, and I have scored over 2750 in Quadrant, as indicated in the screenshot below.
If you have any potential tweaks or suggestions, PM me, and I will check them out!
Note to devs: I believe I have posted this in the right section, as this does not 100% pertain to development.
Now, let's get cracking!
Tweak No. 1: convert RFS filesystem to EXT4.
RFS has been tweaked since it debuted on the galaxy S over two years ago, but still is not quite up to par with today's standards.
Steps:
1. Flash the Terrasilent kernel/ Klin's R3 (basically a kernel with Clockwork recovery 5+ on it)
2. Make a nandroid backup (make sure you have enough free space!)
3.after you reboot, navigate using a file explorer on the Gplayer to the recovery directory and rename all files (excluding boot.img) from .rfs.tar to .ext4.tar.
4. Open up nandroid.md5 and change all filenames (again, excluding boot.img) from .rfs.tar to .ext4.tar
5.Save that, reboot into recovery, perform a full restore, and reboot into download mode.
6. reflash the kernel you were using, and you are done!
The performance improvement is amazing, and I would recommend using this tweak to anyone, since it's safe, and provides a huge boost!
Tweak no.2: Universal Adrenaline shot.
This is an amazing tweak that has provided the biggest improvement for me. It should be pretty risk-free if you follow my directions. Do NOT try to unzip and manually install, as you will have to reflash you rom (bootloop). Additionally, you will have to reinstall any init.d tweaks you have currently, as this script wants to ensure no conflictions, and deletes them all
Steps:
1. Head to this link, read, and download Adrenaline shot v14 (don't worry, our device can handle the two risky tweaks).
2. Boot into recovery, and flash!
3. After flashing, I would optionally format /cache. After reboot, you should see a drastic performance increase!
Tweak no.3: EXT4 Journalism tweaks.
EXT4 is much faster than RFS, but on our Players, the lag is still noticeable, just navigating around the UI.
WARNING:This provides a nice speed increase, especially to large games, but if you have an unclean shutdown, or force restart your Gplayer, YOU WILL HAVE TO RESTORE!
Dire warnings said, This actually increases the smoothness of the Gplayer a decent amount, although for me the risk far outweighs the benefit.
Your partitions are as follows:
System: STL9
Data: mmcblk0p2
Dbdata: stl10
cache (use this partition if you want to test):stl11
Remember, you need su permissions for all of this!
Instructions:
1.First, FSCK the partitions (make sure you answer no to all but the first questions, as that could lead to file corruption! the errors are generated when the partition is accessed during the FSCK, which generates an error, since data is in a different section than it was before. Don't worry, most/all of those errors are flukes. The instruction is: e2fsck -f /dev/block/(partition name)
2. Disable journalism with tune2fs: tune2fs -O ^has_journal /dev/block/(partition name)
Note: tune2fs will not have the capabilities necessary unless you install the one from the one shot adrenaline tweak above.
3.reboot and enjoy!
If you want to reverse this, you will have to restore a nandroid backup, as CWM formats EXT4 with journalism, and a format is required to reset it. On the same note, you will have to reapply this tweak every time you restore a nandroid backup, just something to keep in mind.
Tweak no.4: Supercharge, and apply Loopy smoothness!
I am sure everyone knows about the ubiquitous v6 supercharger script out there, and it provides a big performane increase! Also, Loopy smoothness helps a lot in stabilizing launcher performance, and I view them to be equally valuable.
1. Visit here to download the latest supercharger script, and here to download T2 of loopy smoothness.
2. Launch the supercharger from the /sdcard/download directory, go throught the basic instructions, and the custoomize, reboot, and install nitro lag nullifier. Optionally install for easier access. I would also explore some of the other options especially reindexing.
3. move the loopy smoothness script into the init.d directory, open it, and remove the quotation marks around the launcher name if you are using the touchwiz launcher, or delete the quotations and name and add your launcher's process name (run ps in terminal emulator and find the most likely name, or look it up).
That's it! you should notice a definite performance increase, especially improvements in multitasking thanks to v6 supercharger. The launcher should also be a lot smoother.
Bonus (I have it in R5 rom, but have not actually applied it)
head here, download the latest script, and run it. It should add some extra build.prop tweaks that will greatly boost performance!
Some final suggestions:
1. Move to a custom launcher.
Using touchwiz, I always had about 125+- ram free after using a taskiller, but when I moved to go launcher EX (imho, the best launcher for the gplayer out there, beautiful, not hard on resources, and very customizable), I had over 160+ free after using a taskiller, which resulted in far smoother operation, and excellent multitasking!
2. use ondemand or ondemandx.
All the Gplayer profiles are good, but ondemand, although not the best at power saving, provides the best performance on our aging system, and gives a little extra juice when you need it.
3. use the deadline governor.
None of the other I/O governors come even close to NOOP and Deadline, but deadline is better for everyday use, and noop is better if you have several file transfers occurring at once (eg. hooked up to a computer, updating apps, and browsing the web). It comes down to your usage style, but I prefer Deadline.
4. Disable uneeded /system/app apps.
Fortunately our Gplayer is pretty bloat free, but you can disable more apps if you want. You should rename them to .apk1 instead of deleting them, just in case. Do not delete phone.apk, because for some reason it breaks the default camera app ( you can delete it if you don't use it).
Open up a terminal, run the ps command, and disable any system, apps you recognise in the list (una, fota, etc.).
Beta: Format sdcard as ext2
I had limited success with this mod, and it is definitely worth hassle of converting to ext2. Unfortunately, you must have an init.d script that runs at boot, and there will be the occaisonal permissipn issue, but chmoding the sdcard fixes that.
Steps:
1. Backup all of your /sdcard data
2.connect the gplayer to a linux computer in mtp mode.
3. Open a terminal, and type:
sudo umount /dev/sdx
sudo mkfs.ext2 /dev/sdx
4. Disconnect it from the computer. It will output an error when the media scanner runs, this is okay.
5. Create an init.d script with the following info:
#!/system/bin/sh
mount rw /dev/block/vold/179:1 /mnt/sdcard
chmod 777 /mnt/sdcard
chmod 777 /mnt/sdcard/*
chmod 777 /mnt/sdcard/Android
chmod 777 /mnt/sdcard/Android/*
6. Reboot, and restore your data.
That should be it! I used ext2 because i got permission errors with ext3/4 constantly, and ext2 was stable. The performance improvement is amazing, especially with apps that store data to /sdcard. My performance is at least doubled! Even thouh this is beta, I STRONGLY recommend doing this, as the performance is incredible (as I said)!
Note: after doing this, windows machines will not recognize the player, you will have to do all file transfers via linux.
Note: of app data is not recognized after restore, delete and redownload, after backing up the save file/s. At the moment, it is the only way I have to fix it.
Enjoy the speed!
Dalvik machine: the ULTIMATE speed booster.
I was poking around lately, and I discovered that dalvik settings are really far more powerful than most people give them credit for. Using them on an (unreleased) version of EtherealRom gave me a nice speed increase!
All of these can be added/edited in build.prop, if you so choose, under the variable "dalvik.vm.dexopt-flags=".
The most important one is u=y. This indicates that you want all VM code to be optimized for a single core, and provides a NICE speed boost. The next most important is o=a, as that indicates that you want it to optimize ALL the code, instead of selective batches.
I will update this later, I am exhausted right now, and need some sleep.
I now have my own custom rom that you can flash, that includes most of these amazing features (no ext converting, that has to be manual), plus some more! Note: this rom is ONLY for the 4.0. you will have to restore if you flash it onto the 5.0!
Download
That's it! I will certainly add on as time progresses, but at the moment that is all I can remember/know about, so be sure to pm me with potential tweaks so I can put it up here!
hanthesolo said:
This thread Is a compilation of speed tweaks and mods I have gathered from the forums and used on my Galaxy Player 4.0. I can vouch for all of these tweaks, and all provide at least a modest performance improvement. I claim no credit for any of these mods, the glory goes to the fabulous devs who have created them.
To show you the possible performance increase, I have all of these tweaks installed with the Terrasilent kernel and Klin's R5 ROM, plus an Overclock to 1.5 GHZ, and I have scored over 2750 in Quadrant. If you don't believe me, I will put up a screenshot, as I don't have screen capturing software on my Gplayer right now, and it's too much of a hassle.
If you have any potential tweaks or suggestions, PM me, and I will check them out!
Note to devs: I believe I have posted this in the right section, as this does not 100% pertain to development.
Now, let's get cracking!
Tweak No. 1: convert RFS filesystem to EXT4.
RFS has been tweaked since it debuted on the galaxy S over two years ago, but still is not quite up to par with today's standards.
Steps:
1. Flash the Terrasilent kernel/ Klin's R3 (basically a kernel with Clockwork recovery 5+ on it)
2. Make a nandroid backup (make sure you have enough free space!)
3.after you reboot, navigate using a file explorer on the Gplayer to the recovery directory and rename all files (excluding boot.img) from .rfs.tar to .ext4.tar.
4. Open up nandroid.md5 and change all filenames (again, excluding boot.img) from .rfs.tar to .ext4.tar
5.Save that, reboot into recovery, perform a full restore, and you are done!
Note: after converting, my /data partition is deleted/not recognized when booting into recovery on the terrasilent kernel. I think this may be an isolated incident, but you have been warned!
Tweak no.2: Universal Adrenaline shot.
This is an amazing tweak that has provided the biggest improvement for me. It should be pretty risk-free if you follow my directions. Do NOT try to unzip and manually install, as you will have to reflash you rom (bootloop). Additionally, you will have to reinstall any init.d tweaks you have currently, as this script wants to ensure no conflictions.
Steps:
1. Head to this link, read, and download Adrenaline shot v14 (don't worry, our device can handle the two risky tweaks).
2. Boot into recovery, and flash!
3. After flashing, I would optionally format /cache. After reboot, you should see a drastic performance increase!
Tweak no.3: EXT4 Journalism tweaks.
EXT4 is much faster than RFS, but on our Players, the lag is still noticeable, just navigating around the UI.
WARNING:This provides a nice speed increase, especially to large games, but if you have an unclean shutdown, force restart your Gplayer, YOU WILL HAVE TO RESTORE!
Dire warnings said, This actually increases the smoothness of the Gplayer a decent amount, although for me the risk far outweighs the benefit.
Your partitions are as follows:
System: STL9
Data: mmcblk0p2
Dbdata: stl10
cache (use this partition iuf you want to test):stl11
Remember, you need su permissions for all of this!
Instructions:
1.First, FSCK the partitions (make sure you answer no to all but the first questions, as that could lead to file corruption! the errors are generated when the partition is accessed during the FSCK, which generates an error, since data is in a different section than it was before. Don't worry, most/all of those errors are flukes. The instruction is: e2fsck -f /dev/block/(partition name)
2. Disable journalism with tune2fs: tune2fs -O ^has_journal /dev/block/(partition name)
Note: tune2fs will not have the capabilities necessary unless you install the one from the one shot adrenaline tweak above.
3.reboot and enjoy!
If you want to reverse this, you will have to restore a nandroid backup, as CWM formats EXT4 with journalism, and a format is required to reset it. On the same note, you will have to reapply this tweak every time you restore a nandroid backup, just something to keep in mind.
Tweak no.4: Supercharge, and apply Loopy smoothness!
I am sure everyone knows about the ubiquitous v6 supercharger script out there, and it provides a big performane increase! Also, Loopy smoothness helps a lot in stabilizing launcher performance, and I view them to be equally valuable.
1. Visit here to download the latest supercharger script, and here to download T2 of loopy smoothness.
2. Launch the supercharger from the /sdcard/download directory, go throught the basic instructions, and the custoomize, reboot, and install nitro lag nullifier. Optionally install for easier access. I would also explore some of the other options especially reindexing.
3. move the loopy smoothness script into the init.d directory, open it, and remove the comments around the launcher name if you are using the touchwiz launcher, or delete comments and name and add your launcher's process name (run ps in terminal emulator and find the most likely name, or look it up).
That's it! you should notice a definite performance increase, especially improvements in multitasking thanks to v6 supercharger. The launcher should also be a lot smoother.
Bonus (I have it in R5 rom, but have not actually applied it)
head here, download the latest script, and run it. It should add some extra build.prop tweaks that will greatly boost performance!
Some final suggestions:
1. Move to a custom launcher.
Using touchwiz, I always had about 125+- ram free after using a taskiller, but when I moved to go launcher EX (imho, the best launcher for the gplayer out there, beautiful, not hard on resources, and very customizable), I had over 160+ free after using a taskiller, which resulted in far smoother operation, and excellent multitasking!
2. use ondemand or ondemandx.
All the Gplayer profiles are good, but ondemand, although not the best at power saving, provides the best performance on our aging system, and gives a little extra juice when you need it.
3. use the deadline governor.
None of the other I/O governors come even close to NOOP and Deadline, but deadline is better for everyday use, and noop is better if you have several file transfers occurring at once (eg. hooked up to a computer, updating apps, and browsing the web). It comes down to your usage style, but I prefer Deadline.
4. Disable uneeded /system/app apps.
Fortunately our Gplayer is pretty bloat free, but you can disable more apps if you want. You should rename them to .apk1 instead of deleting them, just in case. Do not delete phone.apk, because for some reason it breaks the default camera app ( you can delete it if you don't use it).
Open up a terminal, run the ps command, and disable any system, apps you recognise in the list (una, fota, etc.).
That's it! I will certainly add on as time progresses, but at the moment that is all I can remember/know about, so be sure to pm me with potential tweaks so I can put it up here!
Click to expand...
Click to collapse
Very nice thread! I'll try it once my device finishes charging. How did you manage to get 1.5 OC?
Thanks! you can tell I am more than a little OCD about my device's performance
I was able to achieve a stable OC by setting the internal voltage to 1.19V, and my core voltage to 1.4V, using Tegrak Overclock. This gives a nice increase to the performance of my player!
hanthesolo said:
Thanks! you can tell I am more than a little OCD about my device's performance
I was able to achieve a stable OC by setting the internal voltage to 1.19V, and my core voltage to 1.4V, using Tegrak Overclock. This gives a nice increase to the performance of my player!
Click to expand...
Click to collapse
I'm not really familiar with OC at all but you just change the voltage and the 1.5 OC option will appear? Didin't you modify your kernel a bit to do this?
As I said in the OP, I have the Terrasilent kernel installed, which allows by default overclocking up to 1.2 GHZ. If you install Tegrak Overclock Ultimate, you can load it's module and overclock up to 2 GHZ with a max internal voltage of 1250mv, and a max core voltage ov 1400MV. Suprisingly easy, actually, and an invaluable tool. You can also change the I/O governor like I suggested from it as well. Attached is A screenshot of my quadrant score (I decided to do it anyway). The score is slightly lower than I said because I have Journalling disabled (to much of a hassle to keep restoring every day).
hanthesolo said:
As I said in the OP, I have the Terrasilent kernel installed, which allows by default overclocking up to 1.2 GHZ. If you install Tegrak Overclock Ultimate, you can load it's module and overclock up to 2 GHZ with a max internal voltage of 1250mv, and a max core voltage ov 1400MV. Suprisingly easy, actually, and an invaluable tool. You can also change the I/O governor like I suggested from it as well. Attached is A screenshot of my quadrant score (I decided to do it anyway). The score is slightly lower than I said because I have Journalling disabled (to much of a hassle to keep restoring every day).
Click to expand...
Click to collapse
Oh ok you have tegrak ultimate. I had tegrak free and the limit was 1.3. Also for the journaling why don't you make a script to execute it at each boot?
Yeah, You can do some crazy stuff in the ultimate version!
I will upload the screenshot in the OP, the way I did it wouldn't work the first time
I didn't make journalism a init.d script because it is a one-time tweak, you apply it, and you have to reformat to go back! I also didn't spell out the instructions verbatim in case someone wants to selectively apply this tweak or use it as reference.
zaclimon said:
Oh ok you have tegrak ultimate. I had tegrak free and the limit was 1.3. Also for the journaling why don't you make a script to execute it at each boot?
Click to expand...
Click to collapse
Also, I have triesd to make an init.d script to disable journaling and putting tune2fs in /system/xbin, but it errors out because you can only disable journaling when the partitions aren't mounted. So what I did was copy tune2fs to a directory, boot into recovery, unmount all the partitions and then disable journaling.
Surprisingly my quadrant score jumped by 400 points.
Sent using Tapatalk
klin1344 said:
Also, I have triesd to make an init.d script to disable journaling and putting tune2fs in /system/xbin, but it errors out because you can only disable journaling when the partitions aren't mounted. So what I did was copy tune2fs to a directory, boot into recovery, unmount all the partitions and then disable journaling.
Surprisingly my quadrant score jumped by 400 points.
Sent using Tapatalk
Click to expand...
Click to collapse
I was able to do it (albeit with warnings during e2fsck) using merely the terminal emulator, and after fixing permissions on tune2fs (I manually placed it). I checked it with tune2fs -l /dev/block/(partition) | grep features, and it claimed that I removed the has_journalism flag. Plus, I got the wonderful benefit of corruption after an unclean shutdown.
Is Rom compatibile with SGP 5.0(International) if not can you please pm me some advice about how to port it on SGP 5.0 ?
Unfortunately, This rom is based soly on the SGP 4.0, and would be very difficult to port onto the 5.0. I am currently working on a flashable zip file that contains most of these tweaks, so you won't have to use the rom.
Ok thanks mate , i try two tweaks and its amazing....its awesome feeling when onecore processor 1.5Ghz defeat dualcore Tegra 2
Which two did you try?
what score did you get?
It DOES feel pretty awesome to see quadrant shoot up past a tegra device
Sneak preview: me and Klin are working together on his next version of his rom, and it will have all of these tweaks, plus some extras (read: ext4 sdcard)!
One thing I am not certain about with the adreneline shot; do I need to manually delete my init.d scripts, or will flashing this delete them?
Sent using Tapatalk
The scipt will delete them for you when you flash, but it shouldn't cause any issues if they are not deleted. If some conflict, it may reduce the overall performance boost, but that's the worst that could happen.
hanthesolo said:
Which two did you try?
what score did you get?
It DOES feel pretty awesome to see quadrant shoot up past a tegra device
Sneak preview: me and Klin are working together on his next version of his rom, and it will have all of these tweaks, plus some extras (read: ext4 sdcard)!
Click to expand...
Click to collapse
I try Ext4 and Adrenaline and i get 2612 points I enjoy for flashable pack of tweaks Nice work mate and good luck with all your projects PS sorry for my bad english
Glad it works! I am almost done testing ext4 sdcard, and I will have the steps up here soon. Additionally, Klin will release an update to his ROM with my tweaks includded in the next couple of days, along with more than one new goody
I don't get how you get such a high io score! My io is around 800!? I installed the adreneline tweak, but nothing noticeable, perhaps even worse performance. I have ext4 (I think, since I installed klin's r5). I use deadline scheduler. I also use v6 supercharger. What are you people's quadrant score with just the adrenaline and supercharger? No overclock.
Sent using Tapatalk
Klin's R5 only formats /system as ext4. to get the full benefit (and the noticeable increase), do it on all partitions using the guide on the OP. I would also use noop, as it seems to be slightly faster than deadline on ext4. Once you do that, you should get the increase.
Well, I just tried to convert to ext4 following your instructions, but following the reboot, it has been on the solid "samsung" (not the pulsing one) screen for several minutes, is this normal, or did something bad happen?