Go Back   Android Forums > Community Info & Talk > FAQs
FAQs Android, Device, and Forum FAQs

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

Like Tree15Likes
  • 15 Post By El Presidente

Closed Thread
 
LinkBack Thread Tools
Old November 10th, 2011, 08:27 AM   #1 (permalink)
Beware The Milky Pirate!
Thread Author (OP)
 
El Presidente's Avatar
 
Join Date: Jan 2011
Location: Scotland
Posts: 26,610
 
Device(s): Xperia Z1, Nexus 7 3G, HTC One X, SGS3 Mini
Carrier: EE

Thanks: 14,037
Thanked 15,838 Times in 8,502 Posts
Default Root Terminology

ClockworkMod/Recovery Images
ClockworkMod (or any recovery image) is the piece of software used to install a custom ROM on your phone, flash themes, kernels or other scripts etc. You can install ClockworkMod via ROM Manager or push it manually via ADB Commands. If you're new, I'd recommend using ROM Manager as it's a 1 click, job done type deal. The recovery image is loaded either via ROM Manager or by powering on your handset whilst holding Volume down and selecting Recovery in the bootloader. For a guide on how to use clockwork, click here.

Alternative recoveries include Amon Ra and 4EXT Recovery, but for simplicities sake, Clockwork is probably you're easiest choice.

Please note that you cannot flash clockwork on Samsung Phones using ADB, or ROM Manager (you'll hard brick the device). If there is a version of clockwork (specific to that particular Samsung device) it must be flashed using Odin.

Titanium Backup
Once you've rooted, if you want to install a custom ROM. Generally before installing a custom ROM you'll need to wipe the handset before hand. As a consequence you'll lose all apps and associated data, however using Titanium Backup, you can backup your apps and data after you've flashed your ROM. Click Show below for a guide on how to backup your apps with TB:




Kernel
The kernel is the OS at its most basic format and acts as the bridge between Android and the phones hardware. It looks after things like voltages, power consumption, WiFi Strength (to a certain degree), CPU speed and the scheduler (see above). It's also one of the first things the bootloader kicks in to life after your handset is switched on. A decent kernel can make a massive difference to performance and battery life. There's a very good overview of what a kernel is/what it does here.


Overclocking
Allows you increase the speed of the phones CPU to increase performance. Generally, Custom ROMs have performance improvements over stock software so overclocking is not essential and I wouldn't recommend it unless you know what you're doing. However, if you decide to go down that route, you can use SetCPU or No Frills CPU to do so. In Cyanogen ROMs, there is an overclock option in the Performance menu so you don't need any 3rd Party tools.. If you do decide you want to overclock, be very careful and don't fire in massive increases straight away as you could really damage your handset. It's also best not to uncheck "Set on Boot" whilst you're still testing what your phone can do safely. Conversely, you can also underclock to increase battery life.

Governor
The Governor controls how the kernel sets the CPU speed, dependant on usage. There's a detailed list of how the different Governors work below:

Quote:
interactive - Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
smartass - Is an improved version of interactive governor
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
brazilianwax - Very agresive version of smartass
interactiveX - Tweaked Interactive governor by Imoseyon by adding more features like suspend/wake profile
ondemandX - Tweaked and ported from 2.6.38 base Ondemand governor by Imoseyon by adding more features like suspend/wake profile
Scary - It's based on Conservative which has a slower ramping than Ondemand but then again it has Smartass elements which is a governor with one the fastest rampings
SavagedZen - Another Smartass-based kernel with many modifications aiming to attain both better battery and performance.
Batterysave - When the cpu load increases past the threshhold it scales up to the next speed and takes another load sample and keeps doing that(best on battery life/performance ratio)
There's also an excellent post here on pretty much everything you want to know on kernels and governors.

It's worth noting, that not all kernels support all governors, this is taken from LordMod's thread here, another thread by knzo on XDA and a little info from Tresezk.

Scheduler
The scheduler controls what percentage CPU is given to each running task. There are 2 Android/Linux schedulers, CFS (Completely Fair Scheduler) & BFS (Brain **** Scheduler). CFS ensures that all running tasks/apps will be given an equalish amount of the CPUs processing power, perfect for multi-tasking. BFS means the app running in the foreground receives the lions share of CPU. BFS is ideal for people who use their phone for gaming.

Personally, I tend to go for CFS as I find BFS slightly worse on battery life, but each to their own. CFS should be fine for most people, but you're free to experiment yourself.

Here's also a little info on NOOP and Deadline Elevators from Tresezk:

Quote:
The Deadline elevator uses a deadline algorithm to minimize I/O latency for a given I/O request. The scheduler provides near real-time behavior and uses a round robin policy to attempt to be fair among multiple I/O requests and to avoid process starvation. Using five I/O queues, this scheduler will aggressively re-order requests to improve I/O performance.

The NOOP scheduler is a simple FIFO queue and uses the minimal amount of CPU/instructions per I/O to accomplish the basic merging and sorting functionality to complete the I/O. It assumes performance of the I/O has been or will be optimized at the block device (memory-disk) or with an intelligent HBA or externally attached controller.
Radio/RILs
The Radio controls all external communication, WiFi, Phone Calls, 3G, GPS, Bluetooth etc. Your current radio is listed under the baseband version in the About Phone section in settings. Most ROMs devs will recommend a Radio to work with their ROM. Failure to match a radio can result in poor battery life, weak signal, no WiFi etc. However, it's dependant on each phone/ROM. I've had mismatched Radios before and I've never noticed that much of a problem.

Flashing a radio is a pretty risky operation so make sure you have at least 60% battery whilst doing so (although the phone is plugged in whilst you're flashing, it doesn't charge). It's also important you ensure the download isn't corrupt, you can do this with MD5 Checker. Instructions are included with the download. Match the MD5 checksum of the radio.img (Wherever you download the radio from should provide this), not the zip file. (Might only be relevant to the Desire HD???)

Please read the instructions and follow them precisely before you go ahead and flash a radio. A bad radio flash can permanently and unrecoverably brick your handset. I've done it a couple of times (flashed a radio, not bricked my phone ) and I know I can type the instructions off by heart, but I still make sure I have them in front of me, just to be on the safe side. It's very easy to do, but just be careful when you do it!!!!

If you're not comfortable with flashing a radio and you're mismatched, you can flash something called a Radio Interface Layer or RIL. The RIL controls how the radio and the handset talk to each other and normally comes in zip format and flashable in clockwork. See the post I linked to for more info. RILs are only really relevant for Sense based ROMs, there's no need for CM7 or MIUI.

EXT3/EXT4
These are just a Linux file systems, similar to the FAT32/NTFS in Windows. EXT4 is supposedly faster and can handle larger file sizes. A lot of ROMs still use EXT3, but the ROMs that support EXT4 will offer an additional download which will wipe and format the phone's file systems to EXT4. This is flashed in clockwork. Having used an EXT4 ROM with the EXT3 file system and vice versa, I've never encountered an issue.

By default, the wipes in Clockwork format to EXT3.

__________________
Site Rules & Guidelines / Staff List / Ask the Staff
Want to bring naughty posts to our attention? Use:
Be respectful to each other - That's what we're all about.
El Presidente is online now  
Last edited by El Presidente; November 4th, 2012 at 02:13 AM. Reason: Changed the order of some stuff.
The Following 196 Users Say Thank You to El Presidente For This Useful Post:
1ryno9 (December 20th, 2011), 2012HereforNow (October 7th, 2013), 2GigayteSD (March 5th, 2013), 2snguyen (May 21st, 2012), adoduran (February 14th, 2013), ahmad301 (March 15th, 2012), Ahtisham (March 10th, 2014), akogecko13 (January 2nd, 2013), Andima (March 9th, 2012), andybog (January 1st, 2013), AndyOpie150 (December 1st, 2011), anjang1980 (August 14th, 2012), ankurchitkara (January 2nd, 2013), ArielAguayo (February 5th, 2012), Atma (December 29th, 2011), AtomicAJ (July 19th, 2013), azkittenkat (March 22nd, 2013), B4tnam (May 9th, 2012), Babsp (February 3rd, 2012), babybee122 (June 27th, 2012), badblue1 (April 16th, 2013), BajaGadget (May 20th, 2012), balaz (December 24th, 2012), bandit409 (January 30th, 2013), barcellos (July 20th, 2012), BCwrangler (June 1st, 2012), BigDumbRedneck (June 29th, 2012), bigmac11 (March 13th, 2014), blh6393 (February 28th, 2013), Blindfitter (February 10th, 2013), BostonSean (August 28th, 2012), brotherswing (December 29th, 2011), Bryant627 (February 25th, 2012), buteman (December 24th, 2011), bylerj1 (April 23rd, 2012), caounda (July 5th, 2012), capncobol (September 19th, 2012), celticdiamondz (June 12th, 2013), cheko_lokz (February 5th, 2012), ChristyC (June 19th, 2012), CNubel (February 26th, 2012), cookies (February 17th, 2012), cwb449 (February 11th, 2013), D-U-R-X (March 14th, 2012), DancingBear015 (December 28th, 2012), danielunde (May 13th, 2012), Dianed (March 29th, 2013), DIncNewbie (September 3rd, 2012), dkl1 (September 14th, 2012), dlphillips (December 24th, 2011), doughsellz (March 27th, 2013), dragula2012 (June 7th, 2013), Drewper (May 31st, 2012), drmg (April 25th, 2012), DwayneE75 (May 13th, 2012), e a (April 4th, 2012), ElDroid22 (April 18th, 2012), elyoung70 (December 30th, 2011), emagineit (December 3rd, 2011), f9linda (January 21st, 2014), fieldhand1 (January 5th, 2013), FlakoMx (December 22nd, 2012), flamborn (February 28th, 2012), FRUIZV (November 24th, 2013), FullMetalMikey (June 23rd, 2012), Fuzzy13 (March 13th, 2012), GamerKingFaiz (November 11th, 2012), gandalfsmother (July 12th, 2012), gayMboi (November 25th, 2012), Gibby999 (April 21st, 2013), gkt4734 (April 3rd, 2012), gogomouse1 (February 7th, 2012), Granite1 (January 10th, 2012), Herman1941 (July 10th, 2012), HeroLau (April 9th, 2012), HoboHorse (November 3rd, 2012), HPS451 (January 4th, 2013), hvrc (March 26th, 2012), indypan (January 8th, 2013), ivotkl (February 2nd, 2013), Jayplac (June 22nd, 2012), jazzboyrules (January 22nd, 2012), JBynder11 (August 3rd, 2012), jconeab (August 12th, 2012), jdas20 (April 5th, 2012), jeyltd (June 4th, 2013), jhonier (September 18th, 2013), JJLuchiano (November 10th, 2012), Johnware43 (May 3rd, 2012), JonBoyU4eA (June 12th, 2013), jroderka30 (February 2nd, 2012), kalser (February 17th, 2012), Kapi91 (February 4th, 2012), KappnKronix (April 5th, 2013), karlp (May 23rd, 2013), Katmandu (January 21st, 2012), Kattie (November 29th, 2011), killaclownrain (December 6th, 2012), KOCHAB (November 15th, 2012), KOLIO (April 22nd, 2012), l0t3k (September 8th, 2012), laidback1 (August 5th, 2013), lauraluv099 (February 27th, 2014), Lilium (August 23rd, 2012), lookinin (December 22nd, 2012), lunadna (October 20th, 2012), macguru42 (December 8th, 2012), Mad Chad (November 5th, 2013), manoranjan2050 (December 26th, 2011), mark10mx (April 23rd, 2012), mayankr (April 3rd, 2012), MBGN (January 28th, 2012), Mehta23 (June 12th, 2012), Metroid Prime (October 29th, 2012), miashottangel (June 15th, 2012), MjK3 (December 21st, 2011), momist (February 8th, 2013), MrElvey (August 8th, 2012), MrsGreen (March 10th, 2012), msayy (February 26th, 2014), N00bsauce (December 28th, 2012), NeuroGuy (October 27th, 2012), NewYorkGiant (May 12th, 2012), NiceGuyJon (November 12th, 2012), NinerBikes (January 29th, 2012), noahvale61 (February 21st, 2012), obsidianwings (February 23rd, 2012), ocnbrze (January 29th, 2012), Odo (September 29th, 2012), owsleybear11 (March 30th, 2014), oxid (September 14th, 2012), ozkuro (February 28th, 2014), panhandleguy (August 27th, 2012), paponando (September 4th, 2012), parkerskouson (December 12th, 2011), Pauljok1 (September 24th, 2012), Petrah (August 30th, 2012), pickelweasel (September 10th, 2013), PinoyBoy (October 23rd, 2012), PolicyWonk (November 21st, 2011), possebob (May 2nd, 2013), radiowave21 (March 5th, 2012), rakesh1988 (June 21st, 2012), ramdrew (February 6th, 2012), raoulduke333 (November 20th, 2012), RNixon (March 2nd, 2013), rstephenson (June 8th, 2013), RunningTheRed (February 8th, 2012), s8lam2000 (May 7th, 2012), sabresfan (July 22nd, 2012), Sankofa416 (February 27th, 2012), scary alien (November 11th, 2011), screener06 (September 5th, 2012), scriddle (May 6th, 2012), secretpla (June 24th, 2012), shaon010 (March 27th, 2013), ShinySide (December 9th, 2011), shoeb7 (February 13th, 2012), skarni (January 2nd, 2012), Slubgob (December 17th, 2011), sm0kex (May 10th, 2012), soareaper (January 6th, 2012), sole07 (May 8th, 2012), spinningtop82 (June 1st, 2013), stelleri (January 14th, 2014), sticky55 (May 16th, 2013), Syrman (February 16th, 2013), tannguera (July 19th, 2013), tbeilfuss (June 3rd, 2012), Ted Roo (January 5th, 2013), teo5856 (February 2nd, 2012), TheClammer (March 4th, 2013), thehoz (May 9th, 2013), thornev (January 19th, 2012), ticoti68 (February 27th, 2012), Tipjar (March 2nd, 2012), Tresezk (November 12th, 2011), usmccobra1 (April 3rd, 2013), uttercaro (October 14th, 2013), Visiontrix (August 9th, 2013), vpina1986 (August 16th, 2013), vsulima (October 24th, 2012), vtecboy (April 20th, 2012), vzekic (July 17th, 2012), Wabonline (August 8th, 2013), wccanard (April 23rd, 2013), whs37 (November 23rd, 2012), worldgonemad (November 24th, 2013), yankies2 (March 4th, 2013), zamorano78 (November 27th, 2012), zr0w69 (January 16th, 2012), ZulkarneynMS (May 3rd, 2013)
sponsored links
Closed Thread


Go Back   Android Forums > Community Info & Talk > FAQs

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


LinkBacks (?)
LinkBack to this Thread: http://androidforums.com/faqs/443075-root-terminology.html
Posted By For Type Date
[HOW-TO] Change to 4.0.4 yakju from yakjuxw (or ANY other version) OP Update 10/04/12 - Page 82 - xda-developers This thread Refback April 15th, 2012 07:48 PM


All times are GMT -5. The time now is 02:03 AM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.