Introduction
I've made a Definite Guide on Android thread for i9000 that focuses on a few optimizations/scripts I've picked up over the months I've spent on XDA. I truly enjoyed sharing my knowledge with the i9000 community and since the tips/guide/scripts can also be applied here (save some exceptions that I would list down below),I would like to share this with the Captivate community too.
Exceptions
Take note that the guide is primarily for i9000 units. There are a few differences I can note here that you should be aware of:
1. The guide points out some kernels/ROMs that are for i9000. Hence the phones you are using may have different ROMs/kernels that may or may not correlate with the one in the guide.
2. The guide also mentions some apps/tweaks that are particularly alien to your unit and you may have never encountered it in your use of your phone or in XDA. Please ignore them for now, I'll make an effort to make the guide compatible in the future (with feedback from you guys of course )
3. Journaling scripts that are attached like the JournalingOn.zip and Acid Tweaks - Removed Useless Stuff and 00remount may not work well with your unit or it may completely brick it. I don't know this, but if you can post your mount partition configuration, I am willing to make the scripts work for you. You only have to type "mount" on your Terminal Emulator and provide the output to me, and I'll provide the rest. Zach's script however, have high compatibility towards a lot of phones, and thus can be used for your unit. Take note that there is a slight risk that it won't work well. If it doesn't, please post your problems here, and I'll try to fix it. Hence, it's best that you make a nandroid backup before attempting to use any tweaks here.
3. I've compiled a guide on a few notable tweaks in XDA here: LINK. If you would like me to evaluate scripts/tweaks/anything that you do not understand due to their terms being alien to you, I'll be glad to explain it here
Guide
You can refer to the guide here:
LINK
pikachu01 said:
Introduction
I've made an Android Optimization Tips thread for i9000 that focuses on a few optimizations/scripts I've picked up over the months I've spent on XDA. I truly enjoyed sharing my knowledge with the i9000 community and since the tips/guide/scripts can also be applied here (save some exceptions that I would list down below),I would like to share this with the Captivate community too.
Exceptions
Take note that the guide is primarily for i9000 units. There are a few differences I can note here that you should be aware of:
1. The guide points out some kernels/ROMs that are for i9000. Hence the phones you are using may have different ROMs/kernels that may or may not correlate with the one in the guide.
2. The guide also mentions some apps/tweaks that are particularly alien to your unit and you may have never encountered it in your use of your phone or in XDA. Please ignore them for now, I'll make an effort to make the guide compatible in the future (with feedback from you guys of course )
3. Journaling scripts that are attached like the JournalingOn.zip and Acid Tweaks - Removed Useless Stuff and 00remount may not work well with your unit or it may completely brick it. I don't know this, but if you can post your mount partition configuration, I am willing to make the scripts work for you. You only have to type "mount" on your Terminal Emulator and provide the output to me, and I'll provide the rest. Zach's script however, have high compatibility towards a lot of phones, and thus can be used for your unit. Take note that there is a slight risk that it won't work well. If it doesn't, please post your problems here, and I'll try to fix it. Hence, it's best that you make a nandroid backup before attempting to use any tweaks here.
3. I've compiled a guide on a few notable tweaks in XDA here: LINK. If you would like me to evaluate scripts/tweaks/anything that you do not understand due to their terms being alien to you, I'll be glad to explain it here
Guide
You can refer to the guide here:
LINK
Click to expand...
Click to collapse
can this work on stock rom?
q659503934 said:
can this work on stock rom?
Click to expand...
Click to collapse
Which tweak are you particularly interested in? Yes, they will work on stock ROM, but you could tell me which you are particularly interested in, and I can tell you how it would work
pikachu01 said:
Which tweak are you particularly interested in? Yes, they will work on stock ROM, but you could tell me which you are particularly interested in, and I can tell you how it would work
Click to expand...
Click to collapse
the Script tweaks,i think it's most usefull
q659503934 said:
the Script tweaks,i think it's most usefull
Click to expand...
Click to collapse
The script tweaks can be used in a stock ROM, but you would need a custom kernel that supports init.d.
pikachu01 said:
The script tweaks can be used in a stock ROM, but you would need a custom kernel that supports init.d.
Click to expand...
Click to collapse
the post you published is helpful,ths
Well I sport your thread in my sig now, but nice to see you've made a thread for Capy users to get more exposure and discuss it.
Kyuta Syuko said:
Well I sport your thread in my sig now, but nice to see you've made a thread for Capy users to get more exposure and discuss it.
Click to expand...
Click to collapse
Thanks for the sig up
Yes, I would want to share this knowledge with as many people as possible. Thank you for helping my effort!
Great guide, just one problem, I've deleted the system apps you've written, and the notification bar is gone lol :S Do you have any clue which app is it?
Elad92 said:
Great guide, just one problem, I've deleted the system apps you've written, and the notification bar is gone lol :S Do you have any clue which app is it?
Click to expand...
Click to collapse
The only one I'm not confident at is Perso. That's why it's better to freeze it rather than delete it. Deleting it makes it harder to restore.
You can freeze it with System Tuner (free app) or Titanium Backup Pro (Paid)
Of course I was freezing, but a quick reboot solve the problem.. Thanks again for this great guide!
As for the memory leaks problem, can you explain more? Will I have to write those commands every time the phone is being laggy?
Elad92 said:
Of course I was freezing, but a quick reboot solve the problem.. Thanks again for this great guide!
As for the memory leaks problem, can you explain more? Will I have to write those commands every time the phone is being laggy?
Click to expand...
Click to collapse
Great
There's a script called drop in the 3rd post. You can use it with Script Manager once you feel the lag coming in. However, to get rid of the lag entirely, you have to tweak the LMK so that free memory doesn't drop below a certain threshold. You can use Auto Memory Manager or Supercharger for that.
Thanks, used this first way, created a nice widget that will do the script
pikachu, just wanted to let you know. Your scripts are incredible. The difference in battery life after adding the 2 scripts to init.d is incredible. I was going through the one. I'm on Apex 10.1 w/ TalonDev 0.5.1.3 was wondering if there would be any added benefit of changing the awake_governor to OnDemandX instead of Ondemand and if you could recommend any other fun things I can try that would be great also.
EDIT: Also still in my init.d is the s70_darky_zipalign scripted would it be recommended to remove that or keep it.
nh5 said:
pikachu, just wanted to let you know. Your scripts are incredible. The difference in battery life after adding the 2 scripts to init.d is incredible. I was going through the one. I'm on Apex 10.1 w/ TalonDev 0.5.1.3 was wondering if there would be any added benefit of changing the awake_governor to OnDemandX instead of Ondemand and if you could recommend any other fun things I can try that would be great also.
EDIT: Also still in my init.d is the s70_darky_zipalign scripted would it be recommended to remove that or keep it.
Click to expand...
Click to collapse
Yes, the VM settings actually save more battery as the number of I/O transactions are kept at the minimum.
You can change it to OndemandX, but OndemandX's main difference with Ondemand is the sleep code as well as the high threshold (95 opposed to 80 in Ondemand). This would result in a generally more powersaving but slower scaling method.
Since conservative is already used when sleeping, using OndemandX is counterproductive IMHO.
The darky zipalign script doesn't work as Darky rom doesn't come with the zipalign binary. You can zipalign with Rom Toolbox (in the market). Also 99.9% of APKs that are used are already zipaligned from the start(you can check this with Rom Toolbox). Don't need to zipalign again.
pikachu01 said:
Yes, the VM settings actually save more battery as the number of I/O transactions are kept at the minimum.
You can change it to OndemandX, but OndemandX's main difference with Ondemand is the sleep code as well as the high threshold (95 opposed to 80 in Ondemand). This would result in a generally more powersaving but slower scaling method.
Since conservative is already used when sleeping, using OndemandX is counterproductive IMHO.
The darky zipalign script doesn't work as Darky rom doesn't come with the zipalign binary. You can zipalign with Rom Toolbox (in the market). Also 99.9% of APKs that are used are already zipaligned from the start(you can check this with Rom Toolbox). Don't need to zipalign again.
Click to expand...
Click to collapse
I made a mistake here. Rom Toolbox doesn't zipalign your APKs well. It failed to detect an unzipaligned APK in my ROM. I will publish a guide to zipalign, but it's pretty much manually done.
Made some pretty big changes to the guide.
Please refer to it when you have the time!
Related
☜☆☞ Check's RAM Management Script ☜☆☞ V4 Twin Turbo [CF-Root Adaptation]
If this thread helps u Rate it 5 ☆☆☆☆☆
If not give me one reason why it cant get the 5 Stars
V4
Twin Turbo
RAM Optimization for You AceI do not take any responsibility if your phone bricks
This Script TURBO BOOST'S YOU RAM! Try it and feel the difference within
CUSTOMIZED RAM TWEAK/HACK FOR THE ACE
This script Gives a Performance boost to the RAM Management significantly on the Ace.
You can use this on any ROM, the values are a result of trial and error when being tested for several days in heavy use and darky's help too .
This is a Super Stable version of the Script and is completely adapted into CF-Root tweaks big thanks to ketut.kumajaya for helping me out
Core Tweak
pdflush writeback daemons wake up time gap increased. Will help to achieve better battery life.
dirty_ratio reduced to 85%
vfs_cache_pressure increased to 10 - better balance between dentries and inodes reclaim/retain
EMPTY_APP processes limit set to 90MB - high enough
Multitasking Greatly Improved
Free Ram Memory also has been improved! [Just hit the clear memory button and see it your self]
Installation
Just Flash it via CWM.
And follow the steps in the video.
Delete all other ram scripts!
be sure that you are on ext4.
Watch the video on Youtube >>HERE<<
Feedback: If you are using it, please leave a comment. If it gives problems report back and I will try to work on it
Credits.
JUWE11 for letting me use his Script [For his original script]
Darky for his values
ketut.kumajaya for CF-Root adaptation and working with me on the script
Video Comparison b/w this & JUWE's Ram Script [for proof as i got lot of requests for it]
Watch the video on Youtube >>HERE<<
Sorry for the voice in the video's guys, I had 2 Surgery done on my neck which is the reason for my voice being like it is!
Development is a result of my hard-work! So if guys love my work help me keep it alive by contributing.
Reserved
for future use
will try it now. i'll post feedbacks later. crossed fingers
Darky is female...
Why is it "twin Turbo" though?
I'm pretty sure Darky is a guy.
consegregate said:
Darky is female...
Why is it "twin Turbo" though?
Click to expand...
Click to collapse
haa V2+V2= Twin Turbo!
joking man
simply coz i like it like that name
Infinityyy said:
I'm pretty sure Darky is a guy.
Click to expand...
Click to collapse
+1
He is a Guy!
Joël Staub that's his name
do i have to delete S98ChecksramhackV2?
Really? In twitter she has her profile picture and everyone seems to be calling she... lemme check galaxy s forums
Jun Hong said:
do i have to delete S98ChecksramhackV2?
Click to expand...
Click to collapse
yes you have to delete it
I see now you put the script into 00tweaks.
I still don't feel any difference though, only that Quadrant dropped from 1800+ to 1700ish, but well... it's Quadrant
Another issue I have is with these changes it closes SetCPU from background after opening a game so I have to restart it manually, it happened with v2 too.
consegregate said:
Really? In twitter she has her profile picture and everyone seems to be calling she... lemme check galaxy s forums
Click to expand...
Click to collapse
darky is a a "HE" http://www.darkyrom.com/community/index.php?members/darkyy.1/ check the Gender:
the girls Photo is his Girlfriends photo!
Ya I checked his Photo Gallery and edited my post before you replied
Apparently he lives not far from my hometown.
And it's on my way when I drive to Genève next week lol
hi, i already patched the script, then i tested the quadrant standard then i got about 1050 score lol... how do i know if i patched it right? by the way inside my init.d are the following: 00tweaks, 01apps2sd, 99complete. which one should i delete? im running the coderom v2x-2b rom...
Hatshipuh said:
I see now you put the script into 00tweaks.
I still don't feel any difference though, only that Quadrant dropped from 1800+ to 1700ish, but well... it's Quadrant
Another issue I have is with these changes it closes SetCPU from background after opening a game so I have to restart it manually, it happened with v2 too.
Click to expand...
Click to collapse
Thanks for your feedback!
appreciate it.
This script is a best of both worlds deal! better ram optimization+battery life!
so that's the reason for the drop!
as you said "Quadrant" is Quadrant after-all. ahha do the benchmark twice you will get a better score hah !
also yes 00tweaks thats true. ketu helped me in testing
not sure with why SetCPU is giving troubles! i will check it out.
if u really want to know the difference this script produces.
flash to FirstUA rom and then compare before and after installing the script u will definitely see a huge difference!
Thanks again for the great feedback.
alvinbam2728 said:
hi, i already patched the script, then i tested the quadrant standard then i got about 1050 score lol... how do i know if i patched it right? by the way inside my init.d are the following: 00tweaks, 01apps2sd, 99complete. which one should i delete? im running the coderom v2x-2b rom...
Click to expand...
Click to collapse
This patch should overwrite your old 00tweaks with a new one.
So no need to delete anything.
Did you convert your file system into ext4?
alvinbam2728 said:
hi, i already patched the script, then i tested the quadrant standard then i got about 1050 score lol... how do i know if i patched it right? by the way inside my init.d are the following: 00tweaks, 01apps2sd, 99complete. which one should i delete? im running the coderom v2x-2b rom...
Click to expand...
Click to collapse
i have posted videos in the thread check them out.
will help u.
don't delete anything!
are u on ext4?
alvinbam2728 said:
hi, i already patched the script, then i tested the quadrant standard then i got about 1050 score lol... how do i know if i patched it right? by the way inside my init.d are the following: 00tweaks, 01apps2sd, 99complete. which one should i delete? im running the coderom v2x-2b rom...
Click to expand...
Click to collapse
got the same files in my init.d
used ketut.kumajaya's CF-Root adaptation.
Had to to do research on darky there, and yes, he's a guy alright.
another interview with darky.
Hahaha thought darkyy is female all along, my bad.
Female developers are rare though. I'd say 90% xda users are guys with gadget fetishes.
Using your twin Turbo, can't see significant differences yet. Shall install gosms and check out the loading time.
can i use this on stock 2.3.4 roms? like flsah it in recovery????
[Kernel KH3&KJ3]Red Nebula [sched tweaks, vm tweaks, ondemand tweaks][zipalign added]
This kernel does not support lagfix(ext4) at least not till I finish work on cwm and build in universal lagfix
Added Zipalign version (file ends in ZA)
Here it is Red Nebula v1.2 (kh3 and kj3 versions now). Its modified from boogs kernel (thank you for the use of your kernel as the base boog without it this wouldn't have been possible) with a lot tweaked and added. Quadrant for me runs around 2000 with it. I recommend cf bench by chainfire or antutu for benchmarking instead though as they have a lot more tests that matter in the android world and as we all know Quadrant means jack anyways. UI is extremely smooth and lag free and system is always extremely responsive.
Update:1.2 is released (pulled 1.0 and 1.1 all together) it includes a few more tweaks for responsiveness and helps out cf bench scores overall and lowers quadrant again, wtf quadrant. ;p
Remember this kernel is tweaked to give a highly responsive lag free device it is not built to get crazy high test scores as most of the tweaks I made improve overall i/o performance, disk throughput, java efficiency, and keep as much memory free as possible without going overboard killing everything in the background, a lot of the tweaks also will help battery life to some extent.
Also please don't request a lag fix version, I built one and it really didn't make much, if any, difference and that's with over 150 apps on my phone. Something about GB on the captivate seems to negate the effects lagfix normally has on performance so I left it out to simplify things and cut down on space in the kernel to save for future tweaks.
##List of mods(Updated)##
#tweaks to lmk keeps mem use down without going overboard
#aggressive version should keep mem free around at least 60mb
#swappiness is tweaked for speed when switching between open apps
#vfs_cache_pressure tweaks help improve overall performance but may require
a reboot every other day in the standard version to keep things snappy aggressive version shouldn't suffer as from this side effect as badly
#various other kernel scheduler tweaks
#tweaks to cpu scheduler(designed for on demand governor only)
#tcp/ip modified for speed and security
#other vm property tweaks improve speed and batterylife
#custom boot animation support for sanim.zip (KH3 still has no boot anim, sorry guys this thing is killing me trying to get working.)
#internal memory (SD) tweaks to reduce disk overhead and increase throughput
#added a new zipalign version of the kernel (the ones that have ZA at the end of the name it will zipalign all apks /system and /data that are not already aligned. just gives an extra little boost to performance.
note: I'm having problems getting custom bootanims working still for kh3, it won't show one so dont freak if you don't see anything after the att screen. It also helps boot time slightly if enough request is made I will post another version with the bootanimation re-enabled to the normal galaxy s boot.
##need to fix##
just bootanim support for now
##fixed in kj3 kh3 fix coming once I can figure out kh3's problem with me##
/\/\Thanks to Kyuta/\/\
##Installation Notes##
To begin as always I am not responsible for any damage to your device or loss of data damage.
Make sure you disable lagfix if it is enabled before installation of my kernel it absolutely doesn't support lagfix and I don't want anyone ended up with a soft or hard brick for trying to flash over a lagfixed device.
Installation is straight forward download the Red Nebula zip attached below and flash through cwm as normal. The only thing to keep in mind is this will wipe all you init.d scripts but it does back them up to /sdcard/initd_backups in the new versions just in case you want to try re-adding any later.
I set it to remove them to prevent scripts already in place from messing with those included with the kernel. Also the kernel doesn't work for nandroid backups as with pretty much all gb kernels so far so please don't try unless you are't worried about bricking.
Also the installation does clear caches for you during installation but feel free to do it anyways afterwords if you want.
note about initial boot up lag: After boot when the system is loading your homescreens you will most likely encounter a small lag at first then everything should come up very fast after a second or two. This is due to the read ahead buffer tweaks I made. They are loading up more information initially and this is what is causing it. The reason for me going slightly more aggressive than the norm is after initial boot up overall read/write rates are dramatically improved over other values I've tried and it makes for a much snappier feel overall, especially when opening gallery, accessing large music libraries and opening file managers.
Feel free to ask questions and leave feed back.
##Credits##
Boog-for the use of his kernel as a base
Kyuta-for help with getting bootanims fixed
ddoubt-for pointing out I forgot to fix the symlink in my
updater script for bootanimtion
All the people at IBM making manual pages
All the people who have made pages/manuals about the linux kernel & tweaking it
Without the above none of this would have been possible.
##side note to other devs##
you may include my tweaks and values in your kernels with credit given, I've spent countless hours researching and testing to get this project to where it is now. About 30-40% of the values used have been previously used by many others before but the rest I found researching manual/reference pages and some I found to work best through trial and error. The scripts except 99completed and the bootanimation script are my own work and while most are basic they are mine so please don't include them in tweak packs, kernels, and rom & kernel packages without permission.
##--updated links for fix to init.d backup scritpt and error in updater-scritpt!!--##
Wow, some body use stock please test this kernel. I will try when I back to stock ^^!
Heres a few test screens. Oh and I forgot to mention ram usually runs between 158mb-220mb. It pretty much has the zram tweaks but modified to values I decided on after reading dozens of linux kernel pages. Some values you might find in other scripts but most arent.
Its also optimized for the on demand cpu governor and I recommend overclocking with tegrak to get the most out of my tweaks.
CF bench
{
"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"
}
Speed test mobile:
Note about speed: this is pretty much absolute max my wifi can run. I'd be glad to see other results and see if I can't improve speed more.
And a nenamark just for fun:
I know its sideways and a little hard to read.
Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
The GB bootanimation binary supports sanim.zip and not bootanimation.zip Not sure if that helps.
smooth.... flashed using SGS Kernal Flasher after turning off Lagfix. So far so good!
Congrats on ur kernel Jsmokey Nice to see more guys step up in the dev, specially when others are leaving due to phone upgrades. I personally don't use ur kernel yet (i9k user so far) but it's great for us cappy users to have more choises to pick from, so I *****slapped ur thxbutton
Kyuta Syuko said:
The GB bootanimation binary supports sanim.zip and not bootanimation.zip Not sure if that helps.
Click to expand...
Click to collapse
Tried that too when I was working on it still no luck. Only thing I could get to play them was the script from the old onix froyo kernel but the anim would just keep playing and according to logcat the ui was loaded completely.
And thanks everyone. I'm glad you like it. I spent alot of time researching linux kernel manual pages to find the best combinations of tweaks to put together and spent many late nights debugging,
Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
Jsmokey said:
Here it is Red Nebula v1.0. Its modified from boogs KH3 Kernel with a lot tweaked and added. Quadrant for me runs around 2000 with it. I recommend cf bench by chainfire for benchmarking instead though as it has a lot more it tests it runs and as we all know Quadrant means jack anyways. UI is extremely smooth and lag free and system is always extremely responsive.
Also please don't request a lag fix version, I built one and it really didn't make much, if any, difference and that's with over 150 apps on my phone. Something about GB on the captivate seems to negate the effects lagfix normally has on performance so I left it out to simplify things and cut down on space in the kernel to save for future tweaks.
##List of mods##
tweaks to lmk keeps mem use down without going overboard
various kernel property tweaks
tcp/ip modified for speed
vm properties tweaked for speed and batterylife
and quite a bit more
note: I'm having problems getting custom bootanims working so for now it won't show one so dont freak if you don't see anything after the att screen. It also helps boot time slightly if enough request is made I will post another version with the bootanimation re-enabled to the normal galaxy s boot.
##need to fix##
just bootanim support for now
##Installation Notes##
To begin as always I am not responsible for any damage to your device or loss of data damage.
Installation is straight forward download the Red Nebula zip attached below and flash through cwm as normal. The only thing to keep in mind is this will wipe all you init.d scripts and replace them with the one's included in the kernel so make sure you have a backup of them before flashing just in case you want to try re-adding any later. I set it to remove them to prevent scripts already in place from messing with those included with the kernel. Also the kernel doesn't work for nandroid backups as with pretty much all gb kernels so far so please don't try unless you are't worried about bricking.
Feel free to ask questions and leave feed back.
Click to expand...
Click to collapse
Congrat jsmokey, hope to see more for the latest leaks. Good Luck
LOSTLOGIC89 said:
Congrat jsmokey, hope to see more for the latest leaks. Good Luck
Click to expand...
Click to collapse
Thanks and I plan on working with them I just started this project weeks ago as a rom/kernel package but they both were taking up so much time I decided to split the kernel off and get it out there.
As soon as I finish up my rom I'm going to work on something for the newest leaks.
Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
very exciting! can't wait for KJ3 version. Thanks for you hard work.
zvadim said:
very exciting! can't wait for KJ3 version. Thanks for you hard work.
Click to expand...
Click to collapse
I actually have kj3 decompiled on my pc so if I have time I might go ahead and whip something up tonight if you want to test for me since I haven't started work on a kj3 rom yet and work on my kh3 rom doesn't leave much time for me to test others and let me know how it works.
Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
Any plans on releasing your ROM?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Hivol said:
Any plans on releasing your ROM?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Click to expand...
Click to collapse
Of course, I hate to give an eta but i'd say around a week and half and I should have pretty much everything wrapped up. Its been in the works since kh3 came out but I've spent a ton of time testing tweaks on it and the theme.
I posted a couple teasers of custom buttons and my battery gauge in the captivate themes post your homescreen thread if you want to check it out. I've been running it for weeks now and a few close friends have been lucky enough for me to put it on their cappy's for em.
Same as with the kernel ill be moving everything to a kj3 base as soon as the kh3 version is done.
Edit: I wanted to mention that I will be updating the first post to be a little more in depth of what the values and tweaks really do. Only reason I haven't is its alot of typing to really explain things properly and I hopefully should have some more tweaks ready in the coming weeks as I dig more into how the linux kernel handles things. I've came along way in understanding how the kernel works in the past few weeks but I still have mountains of information to go through.
Sent from my I897 w/Antares Darkcloud, Red Nebula kernel, & 1.3Ghz OC using Tegrak.
Ok add the following to the end of your init.rc file and see if it helps with the sanim.zip.
Code:
on property:sys.boot_completed=1
stop samsungani
Kyuta Syuko said:
Ok add the following to the end of your init.rc file and see if it helps with the sanim.zip.
Code:
on property:sys.boot_completed=1
stop samsungani
Click to expand...
Click to collapse
Thanks kyuta I'll give that a try a little later and see what happens. I might just switch back to the old onix script and give it a try since its the only thing i could get to play the animations at all. I'm sure that will work though with a little tweaking to fit with the set up i used with the onix bootanim script.
Also this goes out to everyone I got kj3 all compiled just waiting on xpackage to let me know if its booting or not and I'll post it up for everyone, or if anyone else running kj3 that can flash asap and let me know if it boots or not is interested just let me know and I'll pm you the link to get it.
KH3 gave me fits on getting boot animation to work correctly. Just finally had to give it a timelimit eg: sleep 20 then kill it. The leaks after kh3 work better.
Also, the newer kernels will run on kh3, and vise versa
Makes for easy testing, flash it, not good? flash back.
boog said:
KH3 gave me fits on getting boot animation to work correctly. Just finally had to give it a timelimit eg: sleep 20 then kill it. The leaks after kh3 work better.
Also, the newer kernels will run on kh3, and vise versa
Makes for easy testing, flash it, not good? flash back.
Click to expand...
Click to collapse
I kind of figured it was a kh3 problem with the bootanims thanks for the info I'll also give that a try after I get done with all the kernel sched tweaks i'm finishing testing and researching. Next update should be about as responsive as it gets, I don't think there's gonna be much to tweak left after I'm done, and it should greatly improve on i/o rates overall even more than the first release.
Sweet, wasn't sure how things would go flashing the newer kernel leaks over kh3 so i hadn't tried it so I'll go ahead and give it a flash then and see what happens.
Update
flashes and boots fine but it still loops the anim non stop on kj3 and i left it exactly as you set it up for the bootanim boog. I swear this thing is just out to drive me completely insane! I'm gonna try a couple things and see how it goes and I'll post back asap.
update again
OMFG I love you kyuta that worked perfectly!!!! It finally stops when its supposed to lol.
I'll get it uploaded in a few when i get the last few things checked out and make sure all my tweaks are being applied properly.
Check OP for link to KJ3 Kernel! And to Kyuta and Boog I can't thank you guys enough for the help you guys are life savers.
KJ3 Kernel
I backed up the init.d file with root explorer (etc>init.d) and flashed through CWM. No problems. My boot animation worked (sanim.zip).
Quick run through several programs and long press keys working, BT working, GPS working (LOL, at as well as it has at 15ft accuracy).
So far all is good. I will run it tomorrow to see how is does for battery.
I am also running Illuminance 1.1 for the ROM.
CWM version is v4.0.1.5 with the kernel.
Boot scans seem faster.
I know signal is the modem but I am getting -71dBm 20 asu with the KE3 modem and Red Nebula kernel. It is 0130 here in Norfolk but that is the best signal I have gotten.
xpakage said:
I backed up the init.d file with root explorer (etc>init.d) and flashed through CWM. No problems. My boot animation worked (sanim.zip).
Quick run through several programs and long press keys working, BT working, GPS working (LOL, at as well as it has at 15ft accuracy).
So far all is good. I will run it tomorrow to see how is does for battery.
I am also running Illuminance 1.1 for the ROM.
Click to expand...
Click to collapse
Glad to hear it and as DDNV pointed out at first things will seem a little laggy at boot and I believe this is mainly due to increased read ahead buffers, which would cause sort of a momentary pause since they take a bit more time to fill then the default but loads very fast after that initial stutter since its loading a lot more info at once, 2048k compared to 128k default. I ran alot of sdcard speed tests with different settings and this seems to be the best balance between high read/write rates and initial system start up lag.
In the tests I ran it was like night and day in read/write speed compared to other values I tried. Also in my gallery I have well over 1000 images icons, photos, screenshots, etc and with the buffer tweaks it loads all of them almost instantly when I open it and it use to take between 10-20 seconds with default buffers. I will add this to op so people arent thinking its just lagging for no good reason at start up.
anybody tried the v6 supercharger and loopy????
Yes v6 works fine, didn't really see such a great improvement in speed but I presume that's mostly just because of our phones low end spec, I prefer not to tweak so much now though so I don't use any memory tweaks anymore........
Tried v6. Didn't notice any difference at all.
Ahh the good old placebo scripts. Don't bother with them, they either don't do anything or tweak stuff that android/Linux are perfectly good at managing for themselves.
Sent from my Galaxy S2 running CM9 Alpha
but it works superbly in p500 roms,
really good, look this rom full of scripts
http://forum.xda-developers.com/showthread.php?t=1382033
Just because there are lots of scripts in a rom doesn't make them any good.
Have you looked at what the supercharger script is doing? Do you understand the changes it makes? There are a lot of things in that script that simply do not apply to android, the rest are placebo effects or "tweaks" that do nothing for real world usage and just boost scores in quadrant.
Sent from my Galaxy S2 running CM9 Alpha
schiznik said:
Just because there are lots of scripts in a rom doesn't make them any good.
Have you looked at what the supercharger script is doing? Do you understand the changes it makes? There are a lot of things in that script that simply do not apply to android, the rest are placebo effects or "tweaks" that do nothing for real world usage and just boost scores in quadrant.
Sent from my Galaxy S2 running CM9 Alpha
Click to expand...
Click to collapse
im talking abt smooth scrolling and ram management... -.-
not quadrant scores zzzz
Even if you do go for the V6 Script,a bit of advice - stay away from the network / 3g tweaks. There are quite a few not-so-happy endings on the Wildfire forum for people who used them. (Which involved using an RUU to go back to a stock sense ROM, rerooting and coming back to CM)
I respect everyone's view on this kind of stuff and each to there own. Here's my take on them.
After numerous attempts of getting v6 to run I managed it only to have it screw my phone up totally and as 3xeno stated I had a ballache getting my phone back lol.
Juuwes script thing was easy to install but I seriously couldn't tell you if it was doing anything as I noticed no improvement.
Now at the times when everyone was going mad for these kind of tweaks I came across an app called autokiller memory optimizer.
http://forum.xda-developers.com/showthread.php?t=1267425
To this day I swear by this little beauty. Some may say I be under the placebo spell but I doubt it with the amount of times I've run my phone with and without the app through numerous scenarios and I always end up setting it back up again. To me this is my preferred method as I can set exactly what I want tweaking, lower certain apps oom levels and set totally custom low memory kill levels too,I've yet to see a script that gives me that control.!!! The advanced options are very good too e.g changing my sdread speed and lowering my wifi scan time. Ok enough of the selling lol I have no connection to this app or the dev but I seriously recommend everyone to try it. Hey if its not for you then go try one of the others mentioned.
" once its gone,its GONE."
Hey people, this is my first post.
So basically this post is for people still using xperia x8 / w8.
TIPS to increase performance :
1. Install a custom ROM (with a custom kernel). It's no use installing a ROM on stock kernel because it's not very fast and battery life is low too ( I like Minicm7 and Minicm10)
2. After installing the kernel and rom, install a nice launcher. (LauncherPro for gingerbread and nova /apex for ice cream sandwich or jelly bean).
3. Tweak cyanogenmod performance settings : increase vm heap size, allow purging of assets, disable surface dithering, set cpu governor to smartassv2. Overclock if you want but not too much.
4. Use v6 supercharger script. (easy to follow and works great). Do it only if you have custom kernel, because on stock it asks to update busybox which soft bricks the phone).
5. Use autostart manager to remove unnecessary apps from boot.
6. Install apps that you need.
7. Enable "long press to kill apps" in development and kill after you use them like browsers etc.
8. Don't use task killer.
Battery life tips (I assume you are on custom ROM with custom kernel) :
1. Use setcpu and enable profiles. Make the following
A) Screen off - Set Minimum and maximum values of clock the lowest.
B) Battery levels - Choose the maximum to any value below 600 mhz but above 320 when say, the level is less than 40 percent or maximum 480 when the level drops below 50 percent.
2. Make sure you uninstall Dsp manager with titanium backup or root uninstaller.
It sucks lots of battery.
3. Don't set auto brightness.
4. Keep vm heap size to 32.
5. Set governor to on-demand using set cpu for all profiles. AS WELL as for normal usage. (where there are sliders)
6. You may use antutu battery saver. It may or may not work for you.
7. Use v6 supercharger script.
That's it. Press thanks if I helped.
Sent from my E15i using xda app-developers app
I appreciate you for the effort you made.
But there are already many threads about it and also I think that most of the x8 users do have knowledge of these basic things..
Cheers..:beer:
sent from my phone using hands and brain...
dagger said:
I appreciate you for the effort you made.
But there are already many threads about it and also I think that most of the x8 users do have knowledge of these basic things..
Cheers..:beer:
sent from my phone using hands and brain...
Click to expand...
Click to collapse
Sir, Thank you for your review and the beer Yes I am aware of the fact that many people know about it but are tired going through many threads so I compiled a list. That's all.
Exactly this thread will be helpful for noobs much. Nice info :thumbup:
Sent from my XPERIA X8 using Tapatalk 2
@op you may want to review some info. for example, for performance, smartassv2 isn't really the best choice (interactive or ondemand, anyone?). you may also want to remove v6 supercharger since noobs will ultimately ask a lot of questions about it (specially ics/jb users). conversely, ondemand is NOT the best choice if you want to save battery. it has a hair trigger that jumps to max freq and stays there for a long time (like interactive but with different conditions for scaling iirc). there are also lighter launchers than nove/apex/launcherpro. uninstalling or freezing unused apps can also help performance instead of trying to kill them (specially with apps that simply restart themselves). you also have the undervolt option. and updating busybox will not necessarily cause issues if you're on custom kernel. i've updated mine on cm7&10 without issues. i do think gdx (at least on stock kernel) bootloops if you update it. as daggre said, we already have lots of tuts about this, so it would be best to give accurate info or else it will just confuse users.
Hey i heard that if i use my sd card for page file i can increase ram or something like that but is it safe i heard that sd card life will get decreased
KillForFun said:
Hey i heard that if i use my sd card for page file i can increase ram or something like that but is it safe i heard that sd card life will get decreased
Click to expand...
Click to collapse
Yes you can use Swapper 2. Useful only if you use class 6 SD card or above. otherwise no use.
cascabel said:
@op you may want to review some info. for example, for performance, smartassv2 isn't really the best choice (interactive or ondemand, anyone?). you may also want to remove v6 supercharger since noobs will ultimately ask a lot of questions about it (specially ics/jb users). conversely, ondemand is NOT the best choice if you want to save battery. it has a hair trigger that jumps to max freq and stays there for a long time (like interactive but with different conditions for scaling iirc). there are also lighter launchers than nove/apex/launcherpro. uninstalling or freezing unused apps can also help performance instead of trying to kill them (specially with apps that simply restart themselves). you also have the undervolt option. and updating busybox will not necessarily cause issues if you're on custom kernel. i've updated mine on cm7&10 without issues. i do think gdx (at least on stock kernel) bootloops if you update it. as daggre said, we already have lots of tuts about this, so it would be best to give accurate info or else it will just confuse users.
Click to expand...
Click to collapse
Sorry for the mistakes. I wrote smartass v2 because interactive sucks too much battery and isn't practical to use. I would like to delete the thread. I'm new here so please tell me how. I will update the facts and then write
tsinghxda said:
Sorry for the mistakes. I wrote smartass v2 because interactive sucks too much battery and isn't practical to use. I would like to delete the thread. I'm new here so please tell me how. I will update the facts and then write
Click to expand...
Click to collapse
you'll have to ask a mod to delete the thread. why not just update it though? it's a good thread for new guys. just update some info and you're good to go.
cascabel said:
you'll have to ask a mod to delete the thread. why not just update it though? it's a good thread for new guys. just update some info and you're good to go.
Click to expand...
Click to collapse
Alright, I'll update by Monday. Thanks
Haha, thanks for the tips :good:
To the moderators : I am making this thread on the request of members and not trying to promote any rom or kernel.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------
To all the readers : This is just a sharing of Experience of mine, not to be mistaken as a thread for promoting any kernel or rom. Also, all the posts asking which is the best rom/kernel or saying that this kernel is the best and recommending someone just because you like it, shall be reported to the moderators. So be careful of what you post. Also, don't spam the thread by writing just thank you, thanks etc. there is button on the left bottom of each post for that purpose.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Post 1 : General discussion of experience, crashes etc.
Post 2 : Link to the kernels
Post 3 : FAQ(to me )
Post 4 : Important Must Read stuff.
Click to expand...
Click to collapse
[size=+2]The Beginning[/size]
After much waiting and ETA posts by users, when DN3 v5+ was launched, it was met with quite some positive reviews, and being a loyal user to that rom since v2(why, you ask. It's because I like stock like looks that come with my phone, but under the hood optimizations and available customizability and features).
And just in time, Samsung had released the kernel sources for Touchwiz kitkat, so everyone including me were waiting for a good custom kernel, which would allow us to tweak our device to a further extent. During some random discussion @singhpratik87 informed me about an upcoming custom kernel called Nadia kernel, which was made by a small group of devs and modders calling themselves as EmoTdroiD Team.
So, as experiment hungry scientist for my device I am, I went ahead and flashed it. After just some time, I saw that it wasn't yet fully mature and still under construction, although it gave me a good amount of tweaking with the Trickster Mod and a usable battery life, so I went on to search for other kernels too, which would be satisfying my needs, and I found AGNI and Phoenix kernel compatible with my device and rom.
When I started using those, I noticed that many users wanted to know of a good custom kernel they could use, and thus kept spamming different threads asking questions, so I got an idea that I will test the kernel thoroughly and do a proper writeup, so users can be better informed of their needs.
[size=+2]The testing begins[/size]
As I had to begin the test and be thorough with everything I quickly bookmarked some guides to reading a logcat, downloaded tools on PC to capture logcats from boot to shut-down, downloaded each and every kernel and recommended fixes(if any).
I thought of beginning with my stock kernel, since it is the one deemed as the most stable. I got a good battery life but not the advanced tweaking. So, at first I decided to test the most near to stock phoenix kernel, which doesn't have much customisability but is quite stable(for me) for my daily use, but I always have wanted advanced tweaking, so I decided to go for the highly acclaimed AGNI kernel, followed by the under development Nadia kernel.
[size=+2]Stock kernel and Phoenix kernel[/size]
Obviously a starting point for testing the rom itself, I started with the stock kernel. My governor for all the time was pegasusq due to it being optimized properly for multicore systems, but I realized that my music used to have a bit of stutters every 15-20 seconds, so I read and read and found the cause, which you can find on the 31st page of the Nadia Kernel thread(don't be lazy, search for it, I have at least provided the link for the thread ), so I set up profiles suing Xposed module performance profiles and had the switch to ondemand governor whenever I wanted to listen to music, and that made for a smooth experience for me.
As the technology on device gets faster and better, there is one thing we crave for - battery life. Although I got 5 and half hours screen time with 24 hours sage on stock, I still wanted more, seeing that people managed to get upto 7hrs screen time with that usage(I don't know whether they listened to music for at least an hour everyday, though). What can be the best way for getting a better battery life? Underclock? not any way, I want my device to perform to it's full potential rather than be a super sluggish long lasting one. Any more guesses? Undervolting, you say? Yes, that's just what I needed, CPU/GPU undervolting and better control on the governors and LMK(low memory killer).
[size=+2]Reading, Researching, Writing and considerations of various possibilities[/size]
Many of the users who have known me from the time I've joined XDA know that I'm of the kind who is willing to spend his time in reading and solving problems on his own, rather than ask questions repeatedly, so that's what I did again - start reading :cyclops:
I read about the problems faced, questions asked, solutions provided, suggestions given and the proper changelog and FAQs for the kernels.
I researched about how users feel with a kernel, I saw their comments on the threads, I read about their problems faced, their attitude towards the developers and fellow members(which can turn out to be a bit-off when someone is unable to find a solution and gets frustrated) and what they have done to obtain something or how they managed to correct their problems.
Now, after compiling all the things I read and researched about into a small 30+ page word document I wrote to myself, it was time for me to flash a good custom kernel.
Again, which do I go for first? I had to spend my time thinking about the possibilities taking place and the issues I read about :
1) AGNI had some problems with downloading of some apps(Fixed now, but was present when I had to test).
2) AGNI doesn't play well with folder-mount(Dev is working on fix).
3) Nadia gave a bootloop when flashed over AGNI ( as reported by @NickVXD).
4) Some users lost root access when flashing Nadia(Rare and fixed in latest R4).
5) Nadia uses Trickster Mod and thus doesn't provide a full fledged GUI for tweaking the parameters( Dev plans to integrate the best app for this, Synapse, in a bit of time).
[size=+2]It begins with AGNI[/size]
After much thinking, I decided to go for AGNI first, because a bootloop and lost root aren't a big issue for me, as I always keep the fixes with me and know how to recover from these small issues.
I made a nandroid backup, in case for a bootloop, flashed the kernel and wiped cache and dalvik cache and rebooted and I was greeted with my lockscreen(yes it booted successfully) and AGNI control app in my app drawer. I began my testing for the lower clocks, conservatively ramping governors, high undervolts( my device can bear upto -80 on CPU and -75 on GPU while still being stable) and lower GPU clocks, because the first thing I wanted was battery life and indeed I got it.
Then, since I was at home only for a long time(many know why) and had thge charging port next to me(lucky me ) so I decided to give a try to other settings as well. The first thing I wanted for my device was a good read speed for my internal and external SD, so I benchmarked and logged performance for each scheduler over an extensive period of time and found Row suited my needs, because I don't write lots of stuff onto my device's memory, but rather need higher priority for reading of the already present memory blocks.
I tested with different governors now and the name of each is self explanatory so I won't tell which gave me the best battery life or performance. Anyways, I tested the smoothness, battery life, framerate in general use to heavy games, device temperature and noted down each and every value thoroughly.
I benchmarked the SD card read write with different cache sizes and noted down each value.
I tested different LMK minfree values and wrote down the results to myself.
I tested the power saving load balance for performance to battery ratio and wrote down the results thoroughly.
I used the 512mb preloadSWAP and checked and wrote down it's results.
I tested the LZ4 ram with different values and wrote down my results. Did the same for Swappiness priorities, and FRandom RNG entropy generator.
I checked the effects of Dynamic file sync and filesystems checking on boot and again, wrote down.
[size=+2]Shifting to Nadia[/size]
I was done with all the possible combinations of settings with AGNI and now it was time for Nadia kernel. I had been active at the thread for quite some time, helping users and even requesting features.
I read some complaints about lost root and bootloop if used after AGNI, and indeed I got a bootloop once, but naturally, as I am not of the types who would just go ahead for anything, I kept a nandroid backup just before flashing, and then I restored my backup, and some user mentioned using the AGNI script cleaning tool for driving away the issues, so I downloaded that and read through the updated script, and then after I was done I decided that I trust my own experienced hands rather than automated tools, so I removed the required init.d scripts from /system/etc/inti.d (Be careful not to remove 00test and 99superSU daemon, as these are needed for proper functioning of root rights).
After I was done, I flashed the kernel, but a bootloop again , silly me realized that I forgot to wipe cache and dalvik cache, which actually I understood from the logcat, so I went to recovery and did that and my phone was up.
After all was up I opened Trickster Mod and went on to customize my kernel and test different settings.
I did the tests with the available settings and wrote down the results like I had done before.
Contrary to as some users had mentioned, I didn't experience lost root, so all was fine for me, and after the R4 release of the kernel some days ago, no one has complained of any such error.
[size=+2] Finalizing [/size]
After I was done with my thorough testing, capturing logcats on hourly basis and for each system crash or reboot(rare) and compiling of a 60-page word document for each kernel's testing(except for stock and phoenix, which gave me no more than 15 pages :silly: ) it was time for me to report everything, as I had promised to various users.
I read through my writings, preserved logcats and memories and collected everything to write up and express this testing in the best manner I could manage(I usually turn out to be short tempered and rude, so it was another challenge for me).
I also had to decide which kernel to keep for my daily driver(I won't report that here, and neither will answer it via PM, though there are exceptions for the PM one, maybe @smeet.somaiya and @singhpratik87, because I trust them for this and I and they both know why).
[size=+2]And this small article is the outcome of all what I had done over the course of the time I had spent[/size]
Links to the Kernels
Phoenix Kernel - http://forum.xda-developers.com/showthread.php?t=2759906
AGNI Kernel - http://forum.xda-developers.com/showthread.php?t=2311094
Nadia Kernel - http://forum.xda-developers.com/showthread.php?t=2760203
FAQ
How did the testing take so long time?
Click to expand...
Click to collapse
Yes I agree that I took a lot of time, the kernels had a lot of settings to explore, but most of it could be done quite quickly and the results logged down, but the main delay was caused due to problems with my lower back which I had in the month of may, some emotional issues also strayed me away from this motive, so I apologize for any delay and to keep you guys waiting.
May I know your settings and any results/logs you have written to yourself?
Click to expand...
Click to collapse
A big NO. It is because the usage pattern and requirement for each of us is quite different and it can be that my settings give you a worse battery life. Also, I won't show those logs/notes to anyone no matter how good friend/relative/pet/neighbour/acquaintance he/she is because those are results for me, and is can also be that your device can take higher or lower undervolting as compared to me.
Any suggestion to which kernel I should use for getting this/that?
Click to expand...
Click to collapse
Again, NO. I won't entertain these kind of questions or spam on this thread, and while none have seen it yet, I am stricter than a moderator with the rules of this forum and any post relating to asking or suggesting a kernel to someone shall be instantly reported to a moderator and I want the readers here to follow this behaviour too.
I have this/that issue with this kernel, any help?
Click to expand...
Click to collapse
Post this in the respective kernel's thread and you'll get a much better and quicker reply, though I may occasionally feel like reply too, if you get lucky(but don't try to by spamming the thread, else instead of you post I will report your profile itself).
You haven't mentioned your battery life in any post
Click to expand...
Click to collapse
Yes, I forgot.
Anyways, Have a look at these screenshots.
Total battery time
Time I listened to music on my battery test days
Screen time
Note : I listened to music for only 1 hour, by setting up a timer, because this provided the ideal conditions for possible calculations of total time I can get on the battery. Also, my battery is quite old(not replaced or checked even once since I bought the device on the 2nd day of launch in India)
I need better battery life/ this feature/ that feature, so what kernel do you suggest me?
Click to expand...
Click to collapse
I can't suggest anything. There are no best kernels, you'll have to check about which one satisfies your needs and is stable too(remember read, read and read thoroughly and be patient).
I tried undervolting but my device gets unstable even on small values or doesn't respond to voltage change and continues to use stock voltages
Click to expand...
Click to collapse
Nearly forgot that one.
Use this Xposed module to disable the touchwiz DVFS, which has the highest priority for voltage and frequency settings, even more than the kernel, and causes more problems than fixes.
Important Notes
Battery life on stock kernel and Phoenix kernel was some, but with just half an hour less of screen time than the one I have shown in my screenshots.
The difference of battery life between was just of 12 seconds between AGNI and Nadia, so what are you going to do in those 12 seconds? Type Nuclear launch codes?
There were some random reboots, shutdowns on both AGNI and Nadia, but extremely rare and because I undervolted too much, both are equally stable for their current stage.
If you are going to post a reply here, post something worth reading, no spam.
Got a suggestion for me, which you think I might not be knowing? I appreciate you posting it here, will try to consider it gladly
There are to be no suggestions given to users for switching kernels just because you use it and like it, I will report that post at the instant I see it.
Don't worry about me being super strict with all this, usually I'm quite soft to everyone and would be willing to help without any hesitation, but don't want unnecessary spam here, neither do I want any fights for which a moderator has to kick in and do the cleanup and also serve you with a warning which you won't like to see.
Thank you for the time you spent on this.
EDIT : Just read through the whole thing. Great guide(?) indeed. It helped me make better choices regarding kernel settings.
Nice info..thanks mate..keep it up..?
Sent from my GT-N7100 using XDA Premium 4 mobile app
nice writeup..
i lack patience for such research as i get no mental energy remaining after development
Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v98 (4.4.3) + AGNi pureCM v2.8.0 kernel
psndna88 said:
nice writeup..
i lack patience for such research as i get no mental energy remaining after development
Sent from F2FS FORMATED I9300 Temasek CM11 Unofficial v98 (4.4.3) + AGNi pureCM v2.8.0 kernel
Click to expand...
Click to collapse
Thanks
And I have tried making some small mods/these and I know it's really tiring for the brain to have everything done correctly and make sure that users are happy.
Sent from my RPG with auto targeting
Nice thread mate. It really showed that it needed a lot of time and patience to know your best setting to optimize your phone depending the usage. This inspires me not to just stick on a single thing but to take the risk and explore for the other things. Again, thanks you mate. Now I may go and explore my own settings. Cheers!!!!
Sent from my SM-G900F using Tapatalk
i posted thanks by mistake, i edited it
but how can i delete my post ?
Sent by my AWP #Unzoom
---------- Post added at 07:56 AM ---------- Previous post was at 07:45 AM ----------
what does undervolting do ?
Sent by my AWP #Unzoom
amit.dhatrak95 said:
i posted thanks by mistake, i edited it
but how can i delete my post ?
Sent by my AWP #Unzoom
---------- Post added at 07:56 AM ---------- Previous post was at 07:45 AM ----------
what does undervolting do ?
Sent by my AWP #Unzoom
Click to expand...
Click to collapse
Don't worry if you did it by mistake.
And undervolting means controlling of voltages and reducing the power requirement per clock.
Sent from my RPG with auto targeting
@KNIGHT97
Last month I accidentally undervolted my cpu to -100mv
That caused my phone to freeze. I rebooted it. It booted fine but freezed at the lockscreen after boot.
So I decided that I should flash the agni-oc-uv-reset.zip which is saved in your sdcard as soon as you flash agni kernel. But that zip failed to flash. I tried with philz, twrp both.
What could be the reason?
Sent from my GT-N7100 using Tapatalk
smeet.somaiya said:
@KNIGHT97
Last month I accidentally undervolted my cpu to -100mv
That caused my phone to freeze. I rebooted it. It booted fine but freezed at the lockscreen after boot.
So I decided that I should flash the agni-oc-uv-reset.zip which is saved in your sdcard as soon as you flash agni kernel. But that zip failed to flash. I tried with philz, twrp both.
What could be the reason?
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
High undervolting has led to freezes that you have figured out. But zip failing to flash? I can't seem to comment on that, becuase I don't know about that issue, was that something like status 6/7 or bad zip error?
Sent from my RPG with auto targeting
KNIGHT97 said:
High undervolting has led to freezes that you have figured out. But zip failing to flash? I can't seem to comment on that, becuase I don't know about that issue, was that something like status 6/7 or bad zip error?
Sent from my RPG with auto targeting
Click to expand...
Click to collapse
Yeah. forgot to mention. status 7 it said. Error executing update-binary.
Flashed stock kernel then and everything was fine.
After that I went on to check the zip file. And shockingly it was of 0 bytes.
So I think there was some error in extracting that zip while flashing agni kernel.
Anyways that has been fixed in the latest version. Was just informing you☺
Sent from my GT-N7100 using Tapatalk
smeet.somaiya said:
Yeah. forgot to mention. status 7 it said. Error executing update-binary.
Flashed stock kernel then and everything was fine.
After that I went on to check the zip file. And shockingly it was of 0 bytes.
So I think there was some error in extracting that zip while flashing agni kernel.
Anyways that has been fixed in the latest version. Was just informing you☺
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Yea, I saw the earluer ones just now, seems to be an typo in updater script which caused status 7 error.
But yes, glad that its fixed now.
Sent from my RPG with auto targeting
KNIGHT97 said:
Yea, I saw the earluer ones just now, seems to be an typo in updater script which caused status 7 error.
But yes, glad that its fixed now.
Sent from my RPG with auto targeting
Click to expand...
Click to collapse
What typo was it?
And yeah one more thing, kindly let me know what does Frandom rng to? It uses random entropy generator but can't figure out what it is exactly☺
Sent from my GT-N7100 using Tapatalk
smeet.somaiya said:
What typo was it?
And yeah one more thing, kindly let me know what does Frandom rng to? It uses random entropy generator but can't figure out what it is exactly☺
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Frandom is a Linux kernel random number generator, which is 10-50 times faster than what you get from Linux' built-in /dev/urandom. And it uses very little (/dev/frandom) or none (/dev/erandom) of the kernel's entropy pool, so it is very useful for applications that require a handy source for lots of random data.
Its most common use seems to be wiping large hard disks with random data before encryption
here you have the link for more info: http://billauer.co.il/frandom.html
Enviado desde mi GT-N7100 mediante Tapatalk
smeet.somaiya said:
What typo was it?
And yeah one more thing, kindly let me know what does Frandom rng to? It uses random entropy generator but can't figure out what it is exactly☺
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
I couldn't figure put the typo, but that's the most probable problem for status 7 error.
And your answer for Frandom RNG is already answered below
Pafcholini said:
Frandom is a Linux kernel random number generator, which is 10-50 times faster than what you get from Linux' built-in /dev/urandom. And it uses very little (/dev/frandom) or none (/dev/erandom) of the kernel's entropy pool, so it is very useful for applications that require a handy source for lots of random data.
Its most common use seems to be wiping large hard disks with random data before encryption
here you have the link for more info: http://billauer.co.il/frandom.html
Enviado desde mi GT-N7100 mediante Tapatalk
Click to expand...
Click to collapse
So if the kernel has in impact on memory, would it be possible to allocate the data into random blocks onto the memory, both internal and external, just like it is on 64-bit. Intel has managed a 64-bit kernel so maybe you can look at that to get some idea about it.
Or is this thing completely 64-bit only?
Sent from my RPG with auto targeting
KNIGHT97 said:
So if the kernel has in impact on memory, would it be possible to allocate the data into random blocks onto the memory, both internal and external, just like it is on 64-bit. Intel has managed a 64-bit kernel so maybe you can look at that to get some idea about it.
Or is this thing completely 64-bit only?
Sent from my RPG with auto targeting
Click to expand...
Click to collapse
Didn't even get a single word of what you said. My knowledge on memory allocating is limited. I always make mistakes in sums related to memory mapping in my microprocessor exams??
Sent from my GT-N7100 using Tapatalk
---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------
Pafcholini said:
Frandom is a Linux kernel random number generator, which is 10-50 times faster than what you get from Linux' built-in /dev/urandom. And it uses very little (/dev/frandom) or none (/dev/erandom) of the kernel's entropy pool, so it is very useful for applications that require a handy source for lots of random data.
Its most common use seems to be wiping large hard disks with random data before encryption
here you have the link for more info: http://billauer.co.il/frandom.html
Enviado desde mi GT-N7100 mediante Tapatalk
Click to expand...
Click to collapse
Okay. Got what you mean. But what is its application on a phone with limited memory?
Sent from my GT-N7100 using Tapatalk
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
@KNIGHT97
What I meant to say is please elaborate. Don't mind was just kidding☺
Sent from my GT-N7100 using Tapatalk
smeet.somaiya said:
Didn't even get a single word of what you said. My knowledge on memory allocating is limited. I always make mistakes in sums related to memory mapping in my microprocessor exams??
Sent from my GT-N7100 using Tapatalk
---------- Post added at 11:59 AM ---------- Previous post was at 11:57 AM ----------
Okay. Got what you mean. But what is its application on a phone with limited memory?
Sent from my GT-N7100 using Tapatalk
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
@KNIGHT97
What I meant to say is please elaborate. Don't mind was just kidding☺
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
hi do you know how can I enable frandom in nadia kernel