Introduction
Welcome to the Mesmerize Glossary!
This glossary is written specifically with the Samsung Mesmerize, the US Cellular version of the Samsung Galaxy S, in mind. The terms defined below may loosely apply to similar Galaxy S models, or on a case-by-case basis for other devices. It is written for the "advanced beginner"; if you aren't sure what 3G or 4G is, or what the difference is between GSM and CDMA, I would instead recommend starting with the XDA Wiki's Acronyms and Glossary pages to start building your knowledge base from. A few terms from those pages may also appear here if they are especially applicable.
This glossary is intended to both define and describe terms you might see frequently here in the forums, such that no external wiki or forum thread link should be required, though links may still be offered for further reference at the reader's option. Enough information should ideally be provided on each term to offer a strong understanding of the term in the context it is commonly used, but generally, neither advanced knowledge nor in-depth guides or walkthroughs really belong here.
Should you notice that a term you know a definition of--or would like to have defined--is not present, please post to this thread to request it be added or explained.
Using the Glossary
For completeness and ease-of-use, some information may be repeated across the glossary for users searching just for one particular term. The Glossary has been created so that a visual scan of the bolded terms allows users to search the glossary in that way.
If you prefer to search for a term via your browser's Find function, search for "((term)) -" (that is, your desired term, a space, and a hyphen). This should result in locating the exact term you're searching for. Additional wordings of terms (such as nicknames, acronyms of other terms, etc.) have also been included to allow for better search results when using a browser's Find function. Note that these additional wordings may not themselves fit alphabetically, but have been included with their associated term in order to conserve post space.
Terms
Sorted alphabetically.
AOSP - Acronym, also Custom ROM.
Acronym: Android Open Source Project. The group created by Google that continues to develop the Android operating system. Also includes any non-Google member of the Android development community.
Custom ROM:
Author: many various authors and porting contributors.
"Ported" for Mesmerize (and many other devices) from the most generic version of Android available.
Platform Info: Android 2.2 (Froyo), AOSP based.
Kernel: Voodoo-compatible AOSP Kernel included, though a separate download of the ROM.
In the context of a Mesmerize, the Samsung- and US Cellular-free version of the Android operating system as ported (at least in terms of how Android interacts with the Kernel) to the Mesmerize. Excellent battery life with the voodoo-compatible AOSP kernel, and very fast without the Samsung or US Cellular apps. Note that AOSP ROMs and Kernels are NOT compatible with TouchWiz ROMs or Kernels.
Amend Scripting -
Amend Script -
Amend - Scripting Language. An old scripting language used to flash ROMs and Mods to a phone within a recovery or other automated flashing process. Google deprecated Amend in Android 1.5, and has since switched to Edify scripting. Supported only by CWM 2.5.x. (see also: Edify)
BLN - Mod. Backlight Notification mod. Some Android devices have LED indicators to show when you've received a text or e-mail without turning the screen itself on. Since Galaxy S devices do not have LEDs, the Backlight of the soft buttons (Menu, Home, Back, and Search) to fill that role. Note that this requires a BLN app to control. Newer ROMs may not need this mod, or have its functionality included in the ROM/Kernel.
Bootloader - Framework. The text interface that allows interaction with the kernel, application framework, and so on, for the purpose of flashing custom ROMs and other development functions. Note that on many Android devices, either the manufacturer or the carrier have chosen to run a locked framework, making development for the device much more difficult.
Specific to the Mesmerize (as well as the Fascinate and Showcase, at least), Samsung and US Cellular both chose to leave the bootloader unlocked, and the Mesmerize was easily rooted the day after it was released. The Bootloader is what is technically seen when using either the stock recovery, or the custom CWM recovery. Note that users who have loaded the QuickBoot app will simply reboot their phone when selecting the "Bootloader" option.
"Blue" Recovery -
Blue Recovery - Framework. The stock Android recovery. Named for the blue text the menu options use.
Clockworkmod -
Clockworkmod Recovery -
CWM -
CWM Recovery - Framework. The custom Recovery portion of the ROM Manager app originally created by Koush. By way of the Bootloader interface, it allows you to create or restore a Nandroid backup (everything but the kernel is saved to SD card in clockwork/backups/), wipe the system data and cache (Dalvik) partitions (sometimes necessary before flashing a new ROM), flash .ZIP packages saved on the SD card containing ROMs, Mods, Kernels, etc.
Originally, the Mesmerize was restricted to CWM Red, a modified version of CWM 2.5.x which recognized both Amend and Edify scripting types. Since then, several versions of modified CWM 3.0.x have been made available, and have been themed to come in several different colors. These can be found as stand-alone flashes, or bundled into ROMs. CWM 3.0.x only recognizes Edify scripting. Though previously it was recommended to stick with CWM Red for its support of Amend scripting as well as Edify, nearly all of the modern ROMs and Mods available have been written to use Edify. The newer MTD-based ROMs use CWM 4.x, which uses the original orange coloring.
NOTE: Certain MTD-based ROMs for the Mesmerize (and Fascinate and Showcase) are now fully supported by ROM Manager, so users using those ROMs can now install CWM 4.x via ROM Manager.
CWM also offers functions to enable or disable the Lagfix function of the Voodoo kernel (note that a Voodoo-compatible kernel must also be loaded for this menu to function). (see also: Amend, Bootloader, CWM Red, Edify, Lagfix, Nandroid, Voodoo)
Dalvik - The name of the Android-specific Java-based virtual machine (VM) that executes the code for apps. Each app runs in its own Dalvik VM. This allows for a smoother user experience since, for example, if an app crashes, it doesn't crash the entire operating system, but simply the virtual machine in which it was running.
Before running an Android app, Dalvik converts it into a Dalvik Executable, or DEX file. Prior to being converted to a DEX file, an Android app has certain Java classes stored within it for easy execution; these classes are similar to DLLs on a Windows system.
An Optimzed DEX file, or ODEX, is a cache of the Android App's Java classes converted for use with a DEX file. This makes executing those functions faster since they are cached, but makes editing or hacking the apps more difficult, since not all the code is contained within just the APK file; you can often find APK and ODEX files by the same name when browsing with a powerful enough file manager app.
Dalvik was originally developed by Dan Bornstein, and he named it after the fishing village of Dalvik, Iceland, where some of his ancestors lived.
Deodex - Verb. To literally De-ODEX an app or ROM. Specifically, this takes the ODEX cache and compiles it back into the APK file, leaving just the APK file. This makes altering the APK file much easier. (see also: Dalvik, ODEX)
Download Mode - Process. The process by which the phone is prepped for flashing with Odin or Heimdall. Remove the battery and connect the phone to a computer via the USB cable. Hold the Volume Down button until a screen with yellow text saying "Download Mode" and an Android shoveling rubble appears. In the Odin window, a small box should change to yellow, indicating it has recognized the device and it is ready for flashing. Note that no indicator will be present in Heimdall.
EA11 -
EB11 -
EB16 -
EC10 - Android Version. EC10 is the current release build of Froyo (Android 2.2.1) as released by US Cellular for the Mesmerize. Previous (leaked) builds include EA11 and EB16. Note that EB11 is specifically a Showcase build, and not for Mesmerize. This version is partially deprecated now as Samsung has recognized a "Missed Calls" issue with this build, as well as in their Eclair builds, although no official ROM has been released yet. That said, the EE19 leaked ROM addresses this "Missed Calls" issue. (see also: EE19)
EC01 Radio - Mod. This is actually the radio from a recent source drop from the Fascinate. Some users have reported faster 3G speeds and faster GPS pinpointing while using this radio. It also allows for the use of Fascinate ROMs without the need for porting, since Fascinate handles certain things different than the Mesmerize (such as SMS padding, etc.). Note that this radio was renamed from the original "ED01" source drop.
Eclair - Android Version. - The Google-specified codename of Android 2.1. Of note is the alphabetically progressing, food-themed naming convention.
Edify Scripting -
Edify Script -
Edify - Scripting Language. The current scripting language used to flash ROMs and Mods to a phone within a recovery or other automated flashing process. Google deprecated Amend--the previous scripting language--in Android 1.5, and at that time switched to Edify scripting. Supported by CWM 2.5.x, CWM 3.0.x, and CWM 4.x. (see also: Amend)
EE19 - A leaked version of Froyo (Android 2.2.1) that addresses the "Missed Calls" issue identified by Samsung for US Cellular customers. The naming convention puts the release date on or about May 19th, so this is the freshest version of Froyo available to the Mesmerize. At this time, work is still being done to build custom ROMs off of this release.
ESKBL - Mod. Stands for "Extended Soft Key Back Light". A mod specifically for the Mesmerize that allows you to alter how the backlight on the softkeys function.
Fascinate - Device Model. Specifically, this is the model of Samsung Galaxy S available for Verizon customers. Because its model number is SCH-I500, as the Mesmerize's model is, certain components such as mods, ROMs, and themes have been more readily ported between the two models. NOTE: Always ensure the Fascinate component you wish to use on your Mesmerize is actually compatible, some are not.
NOTE: The Fascinate has recently been retired on the Verizon website in favor of a newer Samsung model, likely the not-yet-released Samsung Stratosphere.
Flash - Verb. To transfer or "write" a ROM image, Kernel, Recovery, or complete package of any of the three onto the "flashable" (or writable) memory (ROM) of the Android device.
Framework - At least within the context of Android devices and this glossary, the basic components that make up the core of a complete Android installation; they include the Recovery, Kernel, and OS.
Froyo - Android Version. The Google-specified codename of Android 2.2. Short for "Frozen Yogurt". Of note is the alphabetically progressing, food-themed naming convention.
GAPPS - Mod. An abbreviation for a collection of "Google Apps" for Android devices; Gmail, Google Talk, the Android Market, and so on. This package varies by ROM, and depends on which apps the ROM author chose to include.
Hienz 57 -
H57 -
Heinz 57 - Custom ROM.
Author: Created by dfgas, now being managed by BakedTator. Froyo version based on EC10 Pick-n-Pack v0.3 by phidelt82; Gingerbread version based on ??
Designed for Mesmerize/Showcase.
Platform Info: Android 2.2 (Froyo), or Android 2.3 (Gingerbread); TouchWiz-based, EC10 build (Froyo), ?? build (Gingerbread).
Kernel: Voodoo-compatible TouchWiz kernel included.
This ROM bundles a lot of different mods and customizations commonly requested. The name refers to the fact that portions from several different ROMs were included to some degree; Some ED01 frameworks were included to allow sbrissen's 6-lock mod to work (settings for this mod have been included in the settings menu), while it contains the MIUI Music Player. The Phone.apk and Dialer tab are from sFc, and it includes the Mr. Home launcher, essentially a version of ADW Launcher with some additional mods. It includes nemesis2all's OTB TouchWiz kernel, as well as the voltage control app. (see also: Pick-N-Pack)
Kernel - Framework. Specifically, it is a bridge between the applications in an operating system and the processing components of the hardware. In short, it connects the software to the hardware.
In the context of an Android device, because the hardware drivers are contained within it, it can be replaced with a different kernel to change the way your device's hardware functions; overclocking, undervolting, sound and graphics tweaks, and so on are all customization options offered by using a custom kernel.
For additional information, see the XDA ROM vs. Kernel wiki page.
Kies - Software. The Samsung-created flashing software designed for flashing official Samsung/US Cellular-created ROMs to your device.
Lagfix - Mod. The process by which a Galaxy S device is sped up, typically by tweaking or entirely replacing the file system.
Samsung chose to utilize the RFS filesystem on the Galaxy S, but as a result, the way in which the device access the file system is notably slow. Some lagfixes will encapsulate an Ext2-based filesystem within the RFS filesystem, but since part of the filesystem is still RFS (not to mention that this method wastes a large portion of memory), it is not optimal.
The preferred Lagfix method is the Voodoo custom kernel, which backs up the device's data to the SD card, erases the RFS filesystem and then creates a much more modern Ext4 filesystem, and then writes the device's data back to the newly created filesystem.
Put simply: The older, slower filesystem is replaced with a newer, faster one, and the device operates notably quicker for many users.
Note that users running an MTD-based ROM do not need to enable Lagfix (and in fact, cannot disable it), since the ROM is build to inherently use Yaffs2/Ext4 filesystems.
WARNING: It is nearly always recommended to DISABLE LAGFIX when flashing your device. There may be times when this is not needed, but it is best practice to be prepared to disable this when flashing anything to your device. Flashing anything to your device while any Lagfix is enabled can result in soft-bricking your device.
MIUI MTD -
MIUI - Custom ROM.
Author: many various authors and porting contributors.
Originally designed for the Nexus One and HTC Desire, later ported to many other devices, including the Mesmerize and Showcase by way of the Fascinate port.
Platform Info: Android 2.3 (Gingerbread), AOSP based.
Kernel: MTD-compatible AOSP Kernel included. Non-lagfix Voodoo features supported.
Originally a Chinese-developed ROM based on AOSP, this unique Custom ROM is a visual blend of AOSP and Apple's iOS, all the while delivering the fast and powerful AOSP performance. Some parts of the ROM may still be in Chinese (most notably online themes), and some users have complained about an increase in battery usage; also, not all features are currently working for the Mesmerize-specific port (as with any AOSP build for the Mesmerize). As with iOS, there is no App Drawer, and any app downloaded is immediately displayed on one of the main screens. Deleting the icon will uninstall the app. However, folders like those in iOS are also present to allow for app sorting. There is also extensive theming support available for MIUI directly accessible from the Theme Manager app, allowing the ROM to be very highly customizable without rebooting or reflashing.
No definition of what "MIUI" stands for as an acronym was available after extensive research; it is thought by some that the name is not actually an acronym, but instead possibly a phonetic name pronounced as either "My UI" or "mee-oo-ee".
Nandroid - App, now Genericized Trademark. A Portmanteau of the terms "NAND Backup" and "Android". The original app, called Nandroid Backup, performed complete NAND backups, and the term "Nandroid" has simply become the colloquial term to refer to a NAND backup (in the same way one might make a Xerox--a photocopy--or ask for a Kleenex--a facial tissue). (see also: NAND Backup)
NAND Backup - Process. Capturing a complete system backup, called an Image, of the contents of the main OS partition of the onboard storage memory of an Android device. Note that this DOES NOT backup the Kernel or Recovery. NAND Flash Memory is the specific type of flash memory commonly used for USB drives, SD cards, Solid-State Drives, and other such non-volatile memory consumer products.
No AM/PM - Mod. Similar to No-Clock, but removes the "AM/PM" notation from your status bar (the area at the top of your screen) as some prefer to see the time in the top right, but want to conserve space in the status bar by removing AM/PM.
No-Clock - Mod. Removes the clock from your status bar (the area at the top of your screen) as some prefer to rely on their widget clock or other preferences.
ODEX - Process. The process (usually done automatically when an APK is run by the Dalvik virtual machine) by which the Dalvik cache of an APK or ROM is separated from the actual executable in order to more quickly run the App. Lets the app run faster, but since not all of the code is contained within the APK, makes it harder to develop or edit the APK. Stands for "Optimized Dalvik Executable. (see also: Deodex, Dalvik)
Odin - Software. A device-flashing utility for Windows created by Samsung, used for flashing ROM images and other OS components onto your Samsung device. Utilizes TAR files, and occasionally also PIT files depending on what you're flashing. Though many prefer it to flashing via recovery when given the option, Odin can potentially flash images to your device when Recovery cannot (or your recovery is damaged). Leaked releases from Samsung/US Cellular will most often be found formatted for Odin flashing.
CWM Orange -
"Orange" Recovery -
Orange Recovery - Framework. The original custom Recovery as installed by the ROM Manager app. Note that Galaxy S devices running Froyo should not typically be running Orange Recovery, as it is not fully compatible. However, devices running MTD ROMs will use CWM Orange 4.x, which is normal (and the only custom recovery available that supports the MTD file formatting). (see also: ROM Manager)
PnP -
Pick-n-Pack - Custom ROM.
Author: Phidelt82.
Designed for Mesmerize.
Platform Info: Android 2.2 (Froyo), TouchWiz-based, both EC10 and EE19 builds.
Kernel: Kernel not included. Use a TouchWiz-based kernel.
This ROM is specifcally designed to allow the user to "Pick" and choose which Samsung- and US Cellular-designed apps they wish to have loaded on their device, "Pack" them into a flashable ZIP file, and flash that ZIP onto the phone as a Mod pack. Also includes Mods such as Puzzle Lock and Accurate Battery Mod.
Port - Verb. To bring a mod, ROM, theme, or other component from one device to another.
In the context of the Mesmerize, this is most often done with components to or from the Fascinate or Showcase, as they are similar/nearly identical models, but occasionally from other phone models as well. (See also: Fascinate, Showcase)
Puzzle Lock - Mod. A mod which alters TouchWiz itself by removing the standard "slide glass to unlock" screen and replacing it with a puzzle lock screen (while using a stock ROM, this is normally only seen if you miss a call or message while your phone is locked)
Recovery - Framework. A Pre-boot environment similar in appearance to BIOS on a PC which allows you to recover your device by, at the very least, flashing back to the original stock configuration (factory reset). Also refers to the partition of any Android device where the data to perform recovery options is stored. Because it is a partition separate from the actual Android operating system, it may or may not be affected by changes or customizations you make to your device. Flashing stock ROMs will always change your Recovery to a stock Recovery. Custom ROMs may or may not alter your Recovery. A common example of a custom recovery would be CWM Recovery.
CWM Red -
"Red" Recovery -
Red Recovery - Framework. This refers specifically to an altered version of Clockworkmod (aka CWM) 2.5.x specifically designed to be compatible with the Galaxy S device. Note that ANY Mesmerize user running Froyo (Android 2.2) can only run either Red Recovery, or a Fascinate/Mesmerize custom 3.0.x CWM, as the original Orange Recovery as installed by ROM Manager is not compatible with the Mesmerize based on the type of scripting used. Note also that Mesmerize users running Eclar (Android 2.1) can also opt use Red Recovery.
Note that this recovery has been partially deprecated in favor of modified CWM recoveries based off of CWM 3.0.x, since more or less all modern ROMs and Mods use the Edify scripting language.
ROM - Android Image. A shortening of the term "ROM image". The ROM (Read-Only Memory) image is at least a full install of the OS framework, and may or may not include a Kernel or Recovery as well.
Official or "stock" ROMs include all three frameworks (OS, Kernel, and Recovery), as well as apps and services pre-installed, including those from both the device manufacturer and cellular service carrier (in the case of the Mesmerize, that would be Samsung and US Cellular, respectively).
Custom ROMs are typically based on Official ROMs, but have had one or more components altered or replaced; Custom ROMs may or may not include a kernel (stock or custom), a recovery (again, stock or custom), as well as additional apps and services installed, or even the removal of the apps and services normally installed by the manufacturer and carrier. Most frequently, a custom ROM will not include a recovery as it is typically flashed to the device while booted to recovery, but whether a kernel is included is largely up to the author. A thread containing a custom ROM would ideally state whether it contains a kernel, if which.
For additional information, see the XDA ROM vs. Kernel wiki page.
ROM Manager - App. The app that, among other things, installs the original Clockworkmod. Also allows for other functionality for ROMs, recoveries, recovery boot behavior, and so on. The original CWM that ROM Manager installs has orange text, and is therefore referred to as "Orange" recovery (this, and the app's icons, and the main website directly reference the film "A Clockwork Orange").
NOTE: At this time, if you're using a Samsung Galaxy S device that has been upgraded to Froyo (Android 2.2), you SHOULD NOT have ROM Manager installed, as the "Install CWM" and "Reboot to Recovery" options within that app are NOT compatible with Galaxy S devices running Froyo. You should be using the "Red" recovery instead, or a modified 3.0.x-based CWM recovery. It's worth noting that the Red recovery also works with Eclair (2.1) (this has not been tested with 3.0.x-based custom CWM recoveries). On the other hand, users running MTD-based ROMs will find CWM Orange 4.x flashed to their device, as it is the only custom recovery that supports MTD file formatting. As a result, certain MTD-based ROMs for the Mesmerize (and Fascinate and Showcase) are now fully supported by ROM Manager, so users using those ROMs can now install CWM 4.x via ROM Manager. (see also: Clockworkmod, Red Recovery, Orange Recovery)
Root - verb. To provide Superuser access to an Android device. Some apps require your device to be rooted in order to function. Term originated from from the Unix term of the same name, which described the user given full and total permissions over a Unix system (similar to Administrator on a Windows system). (See also: Superuser)
SGS - Acronym. Short for "Samsung Galaxy S".
Showcase - Device Model. Specifically, this is the model of Samsung Galaxy S available for Cellular South customers. Because its model number is SCH-I500, as the Mesmerize's model is, certain components such as mods, ROMs, and themes have been more readily ported between the two models. Potentially even closer to the Mesmerize than the Fascinate. NOTE: Always ensure the Showcase component you wish to use on your Mesmerize is actually compatible, some are not.
Su -
Superuser - user permission, also app.
User Permission: Another name for a Root user, someone with full and complete access to all portions of an OS. (See also: Root)
App: An app that allows you to control which apps may request Superuser access, view a log of apps that have done so, and control the way in which both you and other apps interact with the device while having Superuser permissions.
Three Finger Method -
Three Button -
Three Button Method - Process. The manual process of entering recovery mode. First, power the phone off. Then, simultaneously hold down the Volume Up, Volume Down, and Power buttons. The Samsung logo will appear; continue holding the buttons. Once the Samsung logo disappears and reappears again, release the buttons. You should now be in recovery mode.
As an alternative, you can use the following method if the first does not work. Once again, power off the phone first. Then, Simultaneously hold down the Volume Up, Volume Down, and Power buttons. The Samsung logo will appear; slide the finger on the volume button down so that it's only holding down the Volume Down button. The Samsung logo should disappear and reappear. Release the buttons. You should now be in recovery mode. Note that this does not work for users running an MTD-based ROM, since such a ROM flashes CWM Orange 4.x, which does not recognize this key combination. (see also: Recovery)
TouchWiz - Framework. The default Samsung-created graphical user-interface, or Shell, that provides touch sensitivity, app launching, and other user interface functions on all stock Galaxy S devices (and other specific Samsung devices). Can be replaced with other Shells. (see also: TWLauncher)
TWLauncher - App. The default TouchWiz Launcher; the actual application part of TouchWiz. Alternatives such as Launcher Pro, ADW Launcher, and so on are available on the market.
UV - Verb. The term is a shortening of "Undervolting", which is the process of providing the device with less power than it was originally designed to receive in order to achieve better battery longevity. This is done within the kernel.
Voodoo - Framework. A series of custom kernels designed specifically for the Galaxy S device and originally created by Supercurio. Voodoo's primary features are to allow the user to enable Lagfix, as well as color "temperature" (some Galaxy S devices apparently have a slightly blueish tint to them), and sound tweaks. Kernels that are voodoo compatible (i.e. not specifically by Supercurio but including the code that enables those functions) may also include functions such as BLN, UV, and so on. (See also: BLN, UV, Lagfix)
Credits
Names listed alphabetically.
Authors: Bdemartino, ChromWolf.
Editors: Bdemartino, Phidelt82.
Sources: XDA Forums, Wikipedia.
Term Contributors: butcher1966 (bootloader), getosquirrel (for Download Mode and Three Button Method), Legato525 (for BLN), Phidelt82 (for ESKBL, GAPPS, and sFc history)
Special Thanks: Sd73ta, for his additions to the Glossary XDA Wiki page and the ROM Vs. Kernel XDA Wiki page. Supercurio, for his explanation on the Project Voodoo site for how Voodoo changes the file system. Svetius, for his work on the Acronyms and Glossary XDA Wiki pages.
Post reserved for future additions.
...I figure this'll be a work in progress. I've had a couple people edit this so far, and it'll only get better as the community tweaks it, adds to it, and corrects it. It'll always be evolving, but especially now. So if you see something you think is incorrect, post constructively, and I'll do my homework and fix up what needs fixing.
In the end, I just hope it helps people get a better beginner's understanding of Android, and the Mesmerize in particular; a one-stop-shop for all the terms. Hope it helps.
o/
Excellent glossary ChromWolf!
Thanks to all that helped!!
Sent from my SCH-I500
Thanks for handling this ChromWolf! I pm'd jerdog to get this stickied.
Great work man!!!
How bout adding three button method and download mode?
getosquirrel said:
Great work man!!!
How bout adding three button method and download mode?
Click to expand...
Click to collapse
Adding.
ChromWolf said:
Adding.
Click to expand...
Click to collapse
Just a little addition to the 3 button method, it works best if you hold all 3 buttons until you see samsung, then drop your thumb down to just holding volume down the rest of the way(if holding with the hand placed on the back of the phone palm facing you, thumb on volume side and forefinger on power). sometimes it's easier to do with the back case off (makes the buttons more exposed)
bdemartino said:
Just a little addition to the 3 button method, it works best if you hold all 3 buttons until you see samsung, then drop your thumb down to just holding volume down the rest of the way(if holding with the hand placed on the back of the phone palm facing you, thumb on volume side and forefinger on power). sometimes it's easier to do with the back case off (makes the buttons more exposed)
Click to expand...
Click to collapse
I can certainly agree on it being easier with the case off, but I've not had any troubles just holding both Volume Up and Volume Down... Maybe I just have big hands though. The process you're describing seems more of a 2-button method though. Does it rely on enough pressure being applied to the Volume Down button such that the Volume Up button is still being pressed down, or is it more that you've already hit it for long enough into the process that it doesn't need to be held down anymore?
Sounds like at the very least, I need to update to say it can take a few attempts, make sure you're pressing hard enough for both buttons, and how to properly hold the phone. How have other people fared?
ChromWolf said:
I can certainly agree on it being easier with the case off, but I've not had any troubles just holding both Volume Up and Volume Down... Maybe I just have big hands though. The process you're describing seems more of a 2-button method though. Does it rely on enough pressure being applied to the Volume Down button such that the Volume Up button is still being pressed down, or is it more that you've already hit it for long enough into the process that it doesn't need to be held down anymore?
Sounds like at the very least, I need to update to say it can take a few attempts, make sure you're pressing hard enough for both buttons, and how to properly hold the phone. How have other people fared?
Click to expand...
Click to collapse
When I first tried getting my phone into recovery by holding all 3 buttons the whole time, it wouldn't work - so I asked around and the instruction I posted is what was given to me to assist - and it worked like a charm. Since then - it's second nature for me to do it this way - but if others aren't haven't issues then maybe there isn't a need to reference it
And to answer your question no, the pressure is on both volume up and down (and power) 3 button, then once the samsung screen comes up i slide the thumb down to only holding down - that is what works 100% of the time for me.
Sweet .....
BootLoader ?
I definitely need to do an update again for 3-button, Bootloader, and EC01 Radio. Maybe sometime tonight if reflashing my phone doesn't take too long. Thanks for the suggestion, butcher1966!
Finally had a chance to update the Glossary; added Bootloader and EC01 radio, as well as updating a few terms like Three Button Method and MIUI, and also a few minor cleanups.
Very nice work, very well done and thought out. Thank you.
This is an amazing guide! Well done, it helped me alot when I was confused on a few things. Thanks for making this!
Updated to add Heinz 57, and update sFc, plus a couple "additional" spellings to enhance the browser search functionality.
Wow, very nice!!!! This is an excellent reference esp for those that don't get here that often and can't keep up with the devs! Thanks much!
How about the new AmendtoEdify and thenewer red cwm?
butcher1966 said:
How about the new AmendtoEdify and thenewer red cwm?
Click to expand...
Click to collapse
Sorry I haven't gotten back to this sooner! I've had my head buried in MIUI builds (which haven't gotten anywhere thus far)...
I can definitely update the CWM entry, and should also note that themed CWM recoveries are available (I'm rocking the H57 green recovery, because green is cool).
I'm unsure if I should include Amend-to-Edify though; that's something only an advanced user would really need to care about, and this is really more geared towards "advanced beginners"... That said, I dislike the idea of just arbitrarily excluding information based on my own judgments of its validity to the target audience, so I think I'll open this one up to the floor: For those still watching, do you think the intelligent-but-not-yet-experienced user should know what Amend-to-Edify is?
If you were to add it I think it should go into a section labeled advanced with a label saying if you don't know what amend and edify and cannot fix a bricked phone. This may not be for you. As someone who does tech support there are times that you should withhold info. So really its up to you. I don't think it would hurt but then again I don't know the possible worse case scenarios from someone like me experimenting with it as well as don't want to see a influx of post to fix things that really should have never been broke in the first place. That goes back to if you cannot fix a bricked phone this is not for you deal.
Anyway those are my thoughts on it.
Tap-a-Talked
ROM Ipioneer Slim 10c v0.1
A light, clean & faster rom!!!
Disclaimer:
/***
* Your warranty is now void (and I'm sure it was void before this process).
* I am not responsible for hard or soft bricked devices, boot loops, dead or corrupt sd cards, strange behavior or you getting a heart attack 'cuz your youtube app is not working properly.
* YOU and only YOU are choosing to make these modifications, do not blame on me.... I will just ignore you.
***/
iPioneer Slim 10c v0.1 is a light, clean and fast custom rom designed for the Lg G Pad X 8.0 (T-Mobile variant only) and it's aim is to become a replacement for the default system of this device.
iPioneer Slim 10c v0.1 it is light because it only takes 519.8Mb of disk space which is a big difference when you compare the 1.2Gb of a stock rom, it is clean because it only contains the essential apps to make it work properly and it is faster because the whole system have been 100% optimized.
iPioneer it have been designed with the User Freedom in mind, it only provides you with the basic OS so you can do what you need to do on top of that.
Features:
Based on stock (10c)
Rooted
Busyboxed
Init.d Support
Extremely debloated (very serious)
Deodexed
Zipaligned
Nova as default launcher
Installation instructions:
Download the rom to your desire location (link to download to the end of this post).
Boot into Twrp recovery and do a standard wipe (factory reset).
Install the downloaded rom .zip.
Reboot the device.
Be patient, is going to take more time than a regular stock rom to boot into the system, at first is going to be stuck at T-Mobile logo but after few seconds is going to enter into App Optimization mode and after that you will be able to setup your system.
Enjoy it.
First things to do after you install this rom:
Add your google account (if you didn't complete that step at the first setup).
Download your favorite app manager (Rom Toolbox, Titanium, etc.).
Freeze the application called App Updates in order to stop the system update beacon for OTA. I removed 3 core apps in order to stop OTAs but it seems to be very integrated with the system, there is no way I can remove it from the rom without breaking the system. This is the most practical way to my knowledge right now.
Optionals things to do after you install this rom:
You can uninstall Nova Launcher if you want as is not part of the system apps, but before you need to install your favorite launcher. If you don't install another launcher and remove Nova you will have a broken system and most likely you'll have to re-flash the rom.
On purpose bugs and missing options:
On purpose bugs are bugs that comes when you remove a functionality from the system but it can not be removed from a third party component, example: LG VPN app it has been removed but the options remains in the Settings of the device and when you tap that option you will provoke a crash event, the way to resolve this is to decode the third party component (very difficult) or reinstall the missing part (in this case the LG VPN app).
iPioneer Slim 0.1 it comes without some apps that can not be removed from the system setting options, this is like that because I believe that these apps are not necessary for all people, if someone need them they can be downloaded/replaced from the Play Store or I will provide a flashable file with these apps so you can install them.
On Purpose bugs (located at settings):
From the Share & Connect menu:
File Sharing that contains BLE and Android Beam doesn't work, package SmartShare it has been removed.
Media Server (DLNA) doesn't work, package SmartShare that also contains SmartShare.MediaServer it has been removed.
Lg Airdrive doesn't work, package LGAirDrive & LGAirDriveSettings were removed.
From More>VPN menu:
LG VPN doesn't work, package VpnClient_LG it has been removed. Basic VPN it works.
From Display menu:
Home screen doesn't work, packages LGHome, HomeSelector, LGHome_Theme_Optimus, com.lge.launcher3, com.lge.launcher2.theme.optimus were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.
Missing options (located at settings):
Smart Cleaning not present, package LGSpringCleaning it has been removed.
Cloud (cloud integration in settings) not present, package CloudHub (maybe dependant on SmartShare package) it has been removed, please also note that this cloud integration it was integrated on the stock File Manager, so... if you want a full integration of the Cloud service on settings maybe you will have to install the stock File Manager provided by LGFileManager package.
From Backup & reset menu:
LG Backup is not present, packages LGBackupLauncher and LGBackup were removed.
From About tablet menu:
Update Center and its content (App updates & System updates) is not present, packages com.lge.appbox.client (app updates), com.lge.updatecenter & LGUpdateCenter (main menu for updates) were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.Flashable zip with system apps:
Coming soon when I have a free time.
What to do if you get the OTA notification:
Freeze the app called App Updates with your favorite app manager.
With your favorite file manager go to /cache and delete the update.zip (the downloaded ota).
Tap on Restart & Install button on OTA pop-up, the pop-up it will start counting to 0 in order to restart but your device won't restart because there are 3 core apps removed from this rom plus 1 app that you just disabled (all these 4 app controls the OTA), the notification is just gonna disappear, push recent button and clear the ota pop-up window.
Bugs Report:
If you find a bug in this rom just notify me about that in this thread, please, just use the title as "Bug Report" so I can pay close attention to that, my time is very limited. Thank you.
Feature Request:
If you want a feature to be added into future revisions of this rom just notify me about that in this thread, please, just use the title as "Feature Request" so I can pay close attention to that, my time is very limited. Thank you.
More info:
-------------------------------------
Device: Lg G Pad X 8.0
Model: LGV521
Code Name: b3
Carrier: T-Mobile
Android version: 6.0.1
Security patch level: 2016-07-01
Software version: V52110c
Link: https://www.androidfilehost.com/?fid=385035244224403624
Screenshots:
Default View: (sorry guys, I was not able fix Nova in order to show an organized and clean layout by default).
Default App Drawer: remember this is an extremely debloated rom, only the most basic core apps remains.
Settings view, yes some options are not present, read above about this.
Software info.
Reserved 2...
For some reason this post doesn't show up on ET page: lg-g-padx
Too bad, a lot of people won't be able to see this rom, but I can do nothing.
If someone knows an admin who can fix this issue please make mention of this post to him. I would do it but I don't have the time to.
Thank you.
Some screenshots added on post #2...
How fast does it run compared to the stock rom?
Munns86 said:
How fast does it run compared to the stock rom?
Click to expand...
Click to collapse
How fast it can go is a subjective matter:
It will depend on hardware lifetime span (how you use it and how other people use this tablet).
It will depend how much apps and content you put in it (the more things you download the more slow android is gonna be, this is kind a Swap area).
I did not do a benchmark, when I declared that is faster than a stock rom is because that speed response enhacement it comes based on the Deodex and Zipalign process. It can be or maybe not noticeable to your eyes but based on deodex and zipalign process is for sure that is faster than an odex and not-zipaligned rom.
The best answer is that you need to try it on your own and see the difference.
Sent from my LG-H918 using Tapatalk
Poll added at the beginning (not visible in tapatalk or xda app).
Please only select the apps that you really need or you really think that should comes with the next revision of iPioneer Slim rom.
This will help me to build a better version with features that users needs.
C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!
xtremelora said:
C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!
Click to expand...
Click to collapse
The reason is that the xda app can't see the vote going on.
Personally, I will be excited to see a cm/aosp custom build, which will sure draw much more attention.
googlephone said:
The reason is that the xda app can't see the vote going on.
Click to expand...
Click to collapse
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...
xtremelora said:
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...
Click to expand...
Click to collapse
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.
googlephone said:
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.
Click to expand...
Click to collapse
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.
xtremelora said:
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.
Click to expand...
Click to collapse
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.
Munns86 said:
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.
Click to expand...
Click to collapse
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.
xtremelora said:
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.
Click to expand...
Click to collapse
There is already a TWRP recovery for v521. Why you need to compile cm recovery?
googlephone said:
There is already a TWRP recovery for v521. Why you need to compile cm recovery?
Click to expand...
Click to collapse
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk
xtremelora said:
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.
shabbypenguin said:
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.
Click to expand...
Click to collapse
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.
xtremelora said:
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.
Click to expand...
Click to collapse
i built it from scratch, id be careful looking too much at the v500, it's a snapdragon 600 SOC which is very old and is a quad core. the 615 in the g pad x is octacore and much newer. even the ramdisk is going to have big differences in how its handled.