We noobs, for good reason, are encouraged to search the forums for answers. The conversations between high level users, though, can sometimes be hard to follow. This glossary should help. It is not a guide. I don't know enough yet to create a guide. It's only a glossary that offers a bit of guidance here and there.
To the noobs: any technical jargon used in a definition should be defined elsewhere in the glossary. To the experienced users: I am a noob writing for other noobs, so please feel free to correct any glaring errors. I would like to keep the definitions both functional and phrased generally in layman's terms. I know I have left out a lot of details, some intentionally, some through ignorance. Further discussion is welcomed.
Glossary
*228 - This is the number to dial from any Verizon phone to activate it. Option 1 activates the phone (linking it to your number and account). Option 2 updates the data roaming, which can evidently enhance your data connection if done from time to time. In certain situations, a dial pad may not be available during the activation call. As an alternative, you can dial *22890 to directly program your phone. Depending perhaps on where you live and which ROM you are using, you can dial *22891 to directly update your roaming. If that fails, you can try *22899 to update roaming, but some users report that this may be risky. Other alternatives include setting up a speed dial as *228,,,,1 or *228,,,,2. The phone reads the commas as two second pauses. Your phone will dial *228, wait for a bit, and then press 1 or 2 automatically.
3 Finger Salute - Using 3 fingers, you hold down the Volume Up, Volume Down, and Power buttons on the sides of your phone. This will boot you into your recovery program. It can also be used to reboot a frozen phone without pulling the battery. This will not work on all ROMs, particularly those using MTD. In fact, if you do it while on an ICS ROM, you will get to see what a bootloop looks like.
adb - Android Debug Bridge - This is a method to connect your home computer to your phone. Generally speaking, it requires properly installed Samsung drivers and the use of the usb cable that came with your phone. People use adb for all sorts of things, including rooting and salvaging a messed up phone. You may see forum discussions where people discuss coding terminology in little grey boxes. These are generally adb commands.
example: adb push something.txt /sdcard/something.txt
AOKP - Android Open Kang Project - A play on the terms "kang" and "AOSP," this is part of a large multi-dev effort to bring the latest Android developments to a number of phones. For our purposes, it is currently under development as a Jelly Bean ROM that we can flash onto our phones. AOKP milestone 6, the final iteration of AOKP ICS, is still regarded as one of the most functional and stable ROMs available for the Fascinate.
AOSP - Android Open Source Project - This refers to the fact that Google shares its Android source code with the world, perhaps its main differentiation from Apple. Any software developer can work with this code. Functionally speaking, developers create AOSP ROMs for the Fascinate. AOSP ROMs could be considered the most pure version of Android, or Android "the way Google intended."
.apk - This is the file extension of ordinary apps and widgets used in Android. If you have the .apk file of a certain app, and you know what to do with it, you can run that app on your phone.
Example conversation:
Noob: I really like this new ROM, but I miss the Samsung Program Monitor widget.
Expert: Just copy the .apk from Nitsuj's stock ROM onto your SD card and install it using Root Explorer
Noob: What's Root Explorer?
Expert: *sigh*
Auto Reboot - This is a check box in Odin. It determines whether your phone will reboot itself after flashing a file in Odin. It doesn't really seem to matter a great deal whether or not it is checked. There seem to be a lot of opinions on this subject. Generally speaking, leaving the box unchecked will not cause any problems. Some problems have been reported in the situation of a failed flash of bootloaders when the box was checked.
Battery pull - Phones can become frozen in all sorts of awkward positions. They sometimes freeze on boot-up screens. They sometimes freeze on screens you won't even recognize. The traditional quick fix was to pull the battery out of the phone, give it a minute, put the battery back in, and then reboot. While this method often works, there is some evidence that it may be harsh on your sd card. The battery pull has essentially been replaced by the act of holding "Volume Up" and "Power" for a while (at least 5 seconds, maybe 10). Shutting down by holding these two buttons is widely regarded as safer than a battery pull.
BL - Bootloader - a.k.a. Boot Loader - This is the rudimentary software that kicks in when a phone is first powered up. Its only real goal is to get the operating system up and running. Some phones, like those from Motorola, have a "locked" bootloader, making it more difficult to use custom kernels. The Fascinate's bootloader was never locked. Here's where it gets complicated: bootloaders are broken down by Android version. There are Eclair bootloaders, Froyo bootloaders, and GB bootloaders. Just being on one version of Android, though, does not mean that you have the corresponding bootloader. It seems that stock Gingerbread phones don't use a Gingerbread bootloader. In fact, to put a GB bootloader on your phone (highly recommended for modern ROMs) you will need to flash a GB bootloader file.
BLN - Back Light Notification - This refers to a popular concept whereby the LED softkeys on the bottom of the phone will blink or light up as a means of notifying the user of missed calls, new texts, emails, etc. Most modern kernels are compatible with some form of BLN. Sometimes, an app will need to be installed from the Marketplace (Google Play) to actually control the settings. More and more, though, the settings can be controlled from within the ROM itself.
Bloat - a.k.a. Bloatware - This term describes all the software that Verizon installed on the phone, but would not allow you to uninstall. Bloat means different things to different people, but it's basically anything stuck on the phone that the user doesn't want. Opinions obviously vary. Common examples of bloat include the NFS Shift racing game, Vcast apps, and Bing.
BML - This is a technical term used by devs to describe the software organization in your phone as it relates to things called partitions. BML is the older, less flexible, and somewhat slower of the two organizational schemes currently available for our phone (MTD being the other). BML was long regarded as the more stable system. MTD ROMs, though, because of their performance benefits and available features, are now the gold standard. A stock Fascinate uses BML, as do several of the custom ROMs (GW, SC3, ,PWGB, TSM Res). Anything involving ICS or JB uses MTD.
Boot Loop - This happens when something goes wrong and does not allow your phone to boot properly. It will actually look like it is repeatedly attempting, but failing to boot up. There are numerous causes and numerous fixes. If you want to see what it looks like, you can do a 3 finger salute while on an ICS ROM.
Bootani - Boot animation. This is the image you see when your phone first boots up. The stock bootani is the Verizon logo. Developers tend to insert their own custom bootanis, and users often like to insert their own as a means of further customizing their phones.
Brick - a.k.a. Paperweight - The ultimate threat that keeps noobs from rooting, this is what people call a phone that does not work at all. It basically has the functionality of a brick or toy block. "Brick" is also used as verb, as in the act of turning your phone into a brick. There are several well established ways to brick phones. The one that noobs are most likely to encounter is the dreaded "Phone" button on Odin. Don't ever touch the phone button, EVER!
Cache - Common to many operating systems, Android included, this is a file where frequently accessed data is stored so as to perform overall performance. Wiping (i.e. clearing/emptying) the cache does not delete any user data, as the cache is rebuilt over time as the phone is used. Functionally speaking, many problems (poor performance, freezes, reboots) can be addressed by rebooting into recovery and wiping the cache and Dalvik cache.
Analogy: when you're reading a book, you could put it back in the bookshelf every time you get to a stopping point. However, it's much easier just to store it on your nightstand (your cache) for a while until you're finished reading it. That way you can access it much faster. If your wife/mom/maid comes and cleans off your nightstand, the book still exists, you just have to take the time to go get it out of the bookshelf again.
CM7 - CyanogenMod7 - This is an alternate version of Android 2.3 put together by a sharp group of developers who are involved in the Android Open Source Project. The CM7 ROM is perhaps most known for its ability to be customized by the user. The CyanogenMod team considers CM7 to essentially be finished, polished, and stable.
CM9 - CyanogenMod9 - This is CyanogenMod's version of ICS. Various releases have been available to the public for some time. Updates continue to be released. Many of the ICS ROMs on our phones carry bits and pieces of CM9. CyanogenMod's development attention has now shifted to CM10.
CM10 - CyanogenMod10 - CyanogenMod's version of JB, currently under rapid development. The various iterations are available as nightlies, which can be downloaded from CyanogenMod's website.
CNA - Codename Android - This is a ROM that, like many others, was available as ICS and is now available as a JB ROM.
CWM - ClockworkMod Recovery - This is an enhanced (understatement) alternative to the phone's normal recovery program. CWM is absolutely central to rooting. Most rooting guides will have you install some version of this program right away, for good reason.
CWM, once installed is accessed as follows:
1. Power down your phone.
2. Using 3 fingers, hold down Volume Up, Volume Down, and Power (see the guides for more specific directions).
Common uses of CWM include:
1. A complete data wipe of your phone (erases all apps, but not your ROM or kernel)
2. Wiping of the cache (often used before making major changes to your phone)
3. Wiping of the dalvik cache (also often used before making major changes to your phone)
4. Wiping battery stats. Some short battery life problems have more to do with your phone's interpretation of your battery than the charge of the battery itself. Wiping these stats can sometimes solve poor battery life issues.
5. Creating and using Nandroid backups.
6. Flashing custom ROMs and kernels (and other things). Users who are crazy about rooting and development will try several new ROMs and kernels in a single day. CWM makes it very easy to install these things and go back and forth.
There are two versions of CWM that most Fascinate users will deal with. There is the CWM 2.5 (CWM-recovery-ALL.tar) that is used for basic rooting or flashing ROMs that are closer to stock (SC3, GeeWiz, TSM Res). Then there is CWM 4 (CWM4_fixed_for_CM7-ODIN.tar) used for flashing MTD ROMs. There are some differences between the two, but they basically work the same way. See Droidstyle's guide for more details. Often, after successful installation of a ROM/kernel combo, one will find a new recovery installed on the phone. Not to worry, though, they all work in very much the same fashion.
Dalvik - This is what's known as a "Java virtual machine." It's the part of the software incorporated into all Android devices that actually runs the apps. It is named after a fishing village in Iceland, home to the ancestors of the developer who first designed the software. For our purposes, when problems occur with our phones, one of the first steps to try would be to reboot into the recovery program and use the available commands to wipe cache and Dalvik cache.
Debloated - This describes a phone that has had the Verizon bloatware removed. Debloating is one of the main motivations for rooting. It can make a phone run more smoothly by getting rid of a lot of things that run in the background. It's also just nice not having all of those useless icons clogging your app drawer. There are two common ways to debloat that most noobs will encounter:
1. Root your phone, install an app called Titanium Backup from the Android Marketplace (Google Play), and "Freeze" anything you consider bloat.
2. Root your phone and install a custom ROM. These ROMs basically come debloated from the developers.
Dev - Developer - These are the people who understand how to write and modify code in the android platform. They are the ones that make rooting fun and easy for the rest of us. They not only create fascinating developments (no pun intended), they package them up in neat little files that simpletons like us can download and install on our phones in a tidy fashion. It is always sad for the community when a recognized dev moves on to another phone. The Fascinate currently has a lot of devs working in a lot of different directions. It's a testament to the inherent potential of this phone.
Development Forum - This is the section of the xda Samsung Fascinate forums that is to reserved for actual development. In this section it is ok for noobs to READ, NOT TO POST. It is important to keep this section uncluttered to promote rapid and efficient exchange of information. It is not the forum in which to post your questions. Also, if you like a dev's work, etiquette dictates that you don't necessarily need to tell him in the Development Forums. You can simply hit the "Thanks" button. He will understand what you mean. The fact that some noobs may have posted in these forums does not serve as justification for other noobs doing the same.
Devil Kernel - This is a relatively new kernel on the Fascinate scene. There is a version for ICS, an alternative to the well-established IcyGlitch kernel, and there is a version for JB. It is the product of German developer DerTeufel1980, and it is undergoing rapid development.
Devil Recovery - As the name suggests, this is a recovery program (an alternative to CWM) from dev DerTeufel1980. Flashing his ROM or kernel will often give you his recovery.
DIDLE - Deep Idle - Some custom kernels can unlock this ability within your phone to dramatically reduce power consumption while idle. Predominantly, it works when the phone's screen is off, but some feature (e.g. a music player) is still running. Some tests by developers show impressive results for decreased battery drain while using DIDLE. Unfortunately for Fascinate users, it must be used with great care because it is well known to cause the Sleep of Death.
Dirty Flash - To properly install a ROM, one should always wipe all user data before doing so. This doesn't mean that the ROM won't flash if you refuse to do. To dirty flash, just clear cache and Dalvik cache and then flash your ROM in recovery.
Why would you do this? Because you're feeling lazy, and you don't want to have to restore your apps and settings.
Why shouldn't you do this? Because you'll have a lot of problems with your phone, call them bugs, blame it on the ROM, and then clog up the development forums with problems that no one else seems to be experiencing.
Download Mode - This is a setting in which you will put your phone when using Odin. There are other ways, but most noobs will reach download mode by powering down, removing the battery, and holding volume down while plugging the factory usb cord into the computer and phone. Odin can only communicate properly with your phone if the phone is in download mode.
Droidstyle's Guide - This is the holy gospel of noob rooting. It can be found in both the General section and Q&A section of xda's Samsung Fascinate forums. Noobs should read every page of the ensuing discussion. A noob with the ability to read and follow directions can be successfully rooted in a matter of minutes. Most of your silly questions that you want to post throughout xda have already been answered in this magnificent guide. Countless questions throughout all Android forums have been answered with nothing more than a link to this guide. If you follow Droidstyle's directions TO THE LETTER, you will be able to successfully do a lot of cool stuff with your phone without experiencing any of the monstrous rooting headaches you may have read about online.
Eclair - Android 2.1. Google likes to name its software releases after sweet foods. The Samsung Fascinate originally shipped with Eclair and hung onto it a really long time. It lacks so many features of later releases, though, that it is essentially a relic that won't come into play.
EH03 - This was the latest (and perhaps final) OTA firmware update from Verizon. Most normal non-rooted Fascinate users will be on the EH03 build number because Verizon basically pushed it out to our phones over the airwaves. It implies that your phone is using Android 2.3 and the EH03 radio. Previous builds shared the alpha-numeric naming system (eg dl09, dj05). Not all builds were officially released by Verizon. Some just sort of showed up on the devs' computers so they could tinker with them.
F. Reset Time - This is a check box in Odin. It's not clear that anyone knows the exact details of what it actually does, nor is it clear what will happen if you leave it unchecked vs checked. It seems to reset some arbitrary counter in your phone. As a general rule, you can either follow the instructions of whatever guide you're using or just leave the checkbox how you found it.
Fassy - a nickname for the Samsung Fascinate
Fast Charge - This is a feature on some ICS ROMs that can be turned on or off. When enabled, it allows your phone to draw as much charge as possible regardless of the charging source. Without fast charge, your phone will place artificial speed limits on charging when plugged, for example, into the USB slot on your computer. Fast charge bypasses these limits, letting your phone believe it is always plugged into a wall charger. It is worth noting that your phone will not be recognized by your computer as a USB device when fast charge is enabled. It will only charge.
FC - Force Close - This is when an app stops working unexpectedly. This can happen to both rooted and unrooted phones. It doesn't cause any damage to the phone. In most cases, the app can just be opened right back up. It seems to depend on a lot of factors, including the quality of the app itself. ROMs and kernels that experience very few FCs are said to be "stable."
Flash - This is a term used to describe the installation of software onto your phone. It refers to fundamental changes in your phone's operating system. It is different from just installing an app from the Marketplace (Google Play). Commonly, people will flash ROMs, kernels, patches, and radios. There are basically two ways to flash new software onto your phone:
1. Odin
2. CWM Recovery (or a comparable recovery program)
Freeze - There are two meanings in general use. One might use this term to refer to his or her phone becoming unresponsive. More commonly, though, it refers to a special ability of a program called Titanium Backup. This program can be downloaded from the Android Marketplace (Google Play), but it requires a rooted phone to work. When Titanium Backup is used to freeze an app or process, that app or process is essentially gone from the phone. It won't show up in the app drawer, and it won't be running in the background. The difference between freezing and uninstalling, though, is that anything frozen can be quickly "thawed," also with Titanium Backup. With the touch of a button, the missing app or process is right back where it used to be. This is a convenient way for newly rooted users to test the waters of debloating.
Froyo - Android 2.2. Google likes to name its software releases after sweet foods. In this case, they refer to frozen yogurt. Some custom ROMs are still based on 2.2. They are known for being extremely well developed and extremely stable.
Gapps - Google Apps - When flashing custom ROMs, the apps on the phone are usually deleted. As an alternative to going to the Marketplace (Google Play) and re-installing all the favorites (Google Maps, Google Talk, Google Voice, etc.), many devs have packaged these into a tidy zip file that can be flashed via CWM. Why don't they just put the Google Apps in the ROM, you ask? Custom ROMs and Google Apps get software updates at different rates, so keeping the two separate allows users to always have the most up-to-date version of each. On MTD ROMs such as CM7 or anything ICS, you generally must flash the gapps package to get the Android Marketplace (Google Play).
GB - Gingerbread - Android 2.3. Google likes to name its Android releases after sweet foods. Most of our stock phones are running on this release of Android. There are numerous ROMS and kernels based on Gingerbread. These are a good starting point for newly rooted users, as they will feel quite familiar.
Github - This is a web-based service where developers can post their code. Depending on the situation, their code can be accessed by other users, modified, or just shared with the world. The site encourages the kind of open source development for which Android is famous.
Governor - This refers to the type of logic your phone uses to control how fast its processor ramps up when needed or slows down when not. The choice of governor can influence overall performance and battery life. In the past, the governor could be selected using an OC/UV program such as Voltage Control or NS Tools. More and more, though, the governor controls are being integrated into the ROM/kernel combo, and can be found under 'Settings.' No one governor is right for everyone. The fun is in experimenting. Here are some (not all) examples and brief descriptions:
performance: Keeps the processor always ramped up to to maximum; useful for benchmarking
ondemand: Rapidly ramps up the processor when needed; gradually slows it down when not needed
conservative: Similar to ondemand, but ramps up more slowly
userspace: The user can define the parameters (for advanced users only).
lazy: This was developed specifically for Android by xda dev Ezekeel. He states it is an enhanced version of ondemand, tuned to our phones' capabilities. Don't be fooled by the name. He tested it with numerous processor-intensive applications.
interactive: Uses a logic to try to predict how quickly it needs to ramp up processor speed, attempting to balance battery life and performance
interactiveX: A tweak on interactive (by dev imoseyon), which locks the processor at the minimum speed when the screen is off
smartass & smartassV2: Modified interactive governors by dev erasmux, they use logic to determine how quickly to ramp up or slow down; designed to optimize battery life without sacrificing performance.
powersave: This keeps the processor always set at the minimum frequency. The name may be a bit misleading, as certain processes will just take longer, using up more battery.
Here's a more complete list from someone who knows a lot more than I do.
Gummy - This is a ROM based off of AOSP. Like many other collaborative dev projects, tt was formerly ICS and now JB.
GW - Geewiz - This is a three piece set of software put together by djp952. He has created a ROM, a kernel, and a custom Recovery (an alternative to CWM). All three can be used together, or each can be installed separately. This package of software is currently well respected for its smoothness and stability, as well as for its ongoing development. GeeWiz is widely considered to be an excellent choice for newly rooted users. The dev has recently released a media player ROM (i.e. no phone component) to get some life out of the old fassy through its Wi-Fi connection.
Heimdall - This program is similar to Odin. It was created by an Australian software company called Glass Echidna. It can be used to flash files onto your phone. Some users prefer this program over Odin. Heimdall can be used with Mac computers, whereas Odin can not. Many high level users regularly use both Heimdall and Odin.
Helly Bean - A Jelly Bean ROM from dev DerTeufel1980.
Hybrid - This describes a system where your phone begins to use some of the better features available in tablets, particularly when it comes to the use of available screen space. Basically, it makes a lot of stuff on your screen smaller so more can be shown on the screen at the same time. A ROM called ParanoidAndroid is currently considered the best iteration of hybrid mode, although other ROMs incorporate it to a certain extent.
ICS - Ice Cream Sandwich - Android 4.0. Google likes to name its Android releases after sweet foods. It comes pre-installed on the Samsung Galaxy Nexus from Verizon. Several developers have created ways to install ICS on the Samsung Fascinate.
Icy Glitch - This is a custom kernel created by a collaborative group of devs headed up by ssewk2x and Tk-Glitch. It is only for use with ICS ROMs such as AOKP and THS. It was extremely popular during the time when ICS was the bleeding edge. Many ROMs of that era were released with an optimized Glitch kernel pre-installed.
init.d - This is a type of script used by developers when they modify Android code. You hear the term a lot because modifications using this type of script have far-reaching effects in the overall performance of the phone. High level users (who aren't quite devs) can even insert bits and pieces of init.d scripts to make minor tweaks to their phones.
Inverted - By default, most Google apps consist of a white screen with dark lettering. Inverting changes this to a dark screen with light letters. There are several advantages to this. Beyond the aesthetic advantages, it tends to be easier on the eyes in low light situations and reduce battery consumption. Inversion is done by talented individuals called themers. For our purposes, groups like Team Baked often put out inverted GAPPS that we can flash instead of the regular ones. There are even 'blacked out' ROMs, where everything is dark.
I/O Scheduler - This refers to the type of logic your phone uses to order and process read and write requests to your phone's hard drive. There are several types, which are listed below, but there is no magic bullet. The joy is in finding the one that works for you in terms of performance and battery life. It is worth noting, though, that certain schedulers were designed to be used with mechanical rotating hard drives, taking the drive's rotational position into account. This does not apply to our phones, which use solid state drive technology. In older ROMs, a scheduler could be selected by using an OC/UV control program such as Voltage Control or NS Tools. In modern ROM/kernel combinations, the scheduler can be selected through the integrated settings. Specific descriptions are beyond the scope of this glossary, but simple Internet searches can expand on any of schedulers listed.
Examples: noop, deadline, cfq, bfq, sio, vr, bfs
* In the absence of a dev's recommendation, if you don't feel like reading up on the subject, you can leave the scheduler at the default or choose noop or sio.
JB - Jelly Bean - Android 4.1. Google likes to name its Android releases after sweet foods. This is the latest version of Android to hit the streets, and devs are flocking to it , making all JB development new and exciting. The development has reached a state where very stable ROMs are readily available.
Jig - This is a tiny Frankensteinian device made of a small chip, a transistor, and the tip of the little micro-USB connector that you plug into your phone to charge it or attach it to your computer. When your phone will not go into download mode through normal means, putting a jig into the phone when the battery is in will make your phone go into download mode. You can make one yourself or buy one online for less than $10.
Kang - Generally used as a verb, this means to take bits and pieces of someone else's coding and to then integrate it into your own. Granted, noobs won't be doing this, but devs do it all the time. For the most part, this is considered a welcome practice among friendly devs, provided it is done correctly and politely. Kanging often serves to better the community as a whole. The key for devs is to give credit to the other devs from whom they have kanged.
Kernel - This is one of the two main components (ROM being the other) of the software running on an Android phone. It is the piece of software that connects the hardware (screen, softkeys, vibration, speakers, etc.) to the other software components. An unrooted phone comes with a stock kernel. It is stable but somewhat slow. Practically speaking, installing (flashing) a custom kernel will make your phone feel much faster and smoother as it moves through screens and opens apps. Generally speaking, installing a new kernel will not change the basic appearance of your phone or erase any of your phone's information. Custom kernels can also unlock several abilities of rooted phones. Examples include:
-wireless tethering (ignoring that pesky $30/month charge from Verizon)
-control over how and when the softkeys at the bottom of the screen light up
-overclocking/undervolting
-voodoo lagfix (This only applies to phones with BML-based ROMs. MTD ROMs don't need lagfix.)
-custom boot animations
KGB - A custom kernel built by comradesven. This popular voodoo kernel is well known because of its many options for customization. It is also considered quite stable and fast. It is the everyday kernel of many rooted users. When installed, it comes with an app that allows a user to easily customize a number of features on the phone.
Lean Kernel - Created by imoseyon, this voodoo kernel is known for its simplicity and stability. He intentionally leaves out a lot of the "bells and whistles" to keep the experience simple, smooth, and fast. Imoseyon works with several phones, so it is imperative that you have the correct version of Lean Kernel, the one appropriate for your phone. It works with TouchWiz ROMs such as SC3 and TSM Res.
Linaro - This is a team of software engineers developing open source software for numerous platforms, particularly as it relates to getting maximum bang for the buck from systems with memory and hardware limitations. For our purposes, many Linaro modifications are making their way into our custom ROMs, promising increased speed and responsiveness.
Logcat - This is a log of all of the processing activity your phone did over a certain period of time. This is useful for bug reporting, as devs can examine logcats and attempt to determine the source of the error(s). Many threads in the development forum request logcats to go alongside any bug reports. A logcat can be generated through adb, and there are also some apps that will do it for you. Random complaints aren't terribly useful for devs, but logcats generally are. This classic cartoon illustrates how many devs feel about disorderly complaints about their work, even though most are far too polite to say anything.
{
"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"
}
Milestone - Devs are always trying to incorporate the latest and greatest features into their ROMs. The add-ons are incorporated as parts of new releases, or "builds." This is what makes development exciting, but it also leads to bugs. Milestone builds occur when the devs sit back, roll up their sleeves, and work the bugs out of all the awesome features they've crammed into their work. The milestones are considered the relatively safe and stable builds. When installed correctly, they rarely experience major bugs.
MIUI - This term is a transliteration of a Chinese name for a special customization of Android actually developed in China. MIUI ROMs can be installed on the Fascinate. They change the look and feel of the Android system, moving it closer to something resembling iOS, the iPhone's operating system. A lot of custom development has been done with the software code from the MIUI system. Many devs will integrate bits and pieces of MIUI into their own ROMs. For example, the TSM Resurrection ROM allows you to use the MIUI battery indicator, which looks completely different from the standard battery indicator.
MTD - This is a technical term used by devs to describe the software organization in your phone, as it relates to things called partitions. The bottom line is that the stock organizational system, called BML, is somewhat fixed and limited, whereas MTD offers devs a great deal of flexibility. Heavily customized ROMs like those from CyanogenMod or anything MIUI rely on MTD file organization. All of our ICS and JB ROMs use MTD. MTD ROMs, generally speaking, experience very little lag, as compared to BML ROMs. When returning to a normal BML ROM from an MTD ROM, special precautions need to be taken.
Nandroid - This is a backup of your entire phone as it stands at that moment in time (ROM, kernel, text messages, your Angry Birds progress, etc.). It is stored on your sd card, which is somewhat immune to your tinkering. A Nandroid backup is a good failsafe for the times when you might want to try out that new experimental kernel your favorite dev has been working on. The files can also be saved on a home computer/flash drive/etc. for safe keeping. Nandroid backups are created using a recovery program like Clockworkmod Recovery. CWM can also use old Nandroids to restore a phone to its previous condition.
Nightly - Nightlies - Some rooted users like the idea of having the most stable, tested, and reliable ROMs available. Others prefer the excitement of being on the cutting edge. Nightlies are the untested regular releases of whatever a certain dev happens to be working on at the time. They package them up, post them online, and let the discussions ensue. These are not for the faint of heart. They are for people who are comfortable addressing freezes, boot loops, and force closes. Having said that, the current nightlies from CM10 are actually quite stable.
Noob - If you have to ask what this means, this is what you are. It's a derivation of "newbie" or "newb," someone who's new to the activity at hand. In many ways, the noob is defined by his actions rather than by the amount of time he's spent rooting phones or posting on xda. Here are a few standard behaviors that will immediately brand someone as a noob:
-Posting new threads to ask questions that have been answered dozens of times. (Hint: It's best to search before posting)
-Posting ROM complaints (without logcat), beginner questions, and other non-development topics in the development forums (It has been theorized that this will ultimately be the end of xda)
-Diving in and flashing away without reading and then posting about your problems (Everyone needs to read the Guide.)
NSTools - This is an app that requires superuser permissions. It can be used to control a variety of the phone's features that are unlocked when running a custom kernel. It can enable fast charge, BLN, overclocking, and undervolting. It often comes pre-installed with ICS ROMs. Most JB ROMs have no use for it.
OC - Overclocking - Computer processors operate at a variety of speeds. When a manufacturer sells a product (like a phone) to the general public, they strictly limit the speed at which the built in processor can operate, even though the processor may be capable of more. This is to promote stability and reliability. Rooted users can overclock their phone's processor, raising the maximum speed at which it can operate. This can be done through various apps, including Voltage Control and NS Tools. Some ROMs even have the controls built into their settings. There are limits, though. Running a processor at too high a speed can cause overheating and/or glitches.
Odin - This is a program of seemingly mysterious origins that allows your home computer to communicate with your phone. You download it to your home computer. Good communication with your phone requires the installation of Samsung drivers on your computer as well as the use of the USB cable that came with your phone. Among other things, Odin can be used to root your phone, install CWM Recovery, install custom ROMs and kernels, and return your phone to stock after you've screwed it up.
*NEVER touch the "Phone" button on Odin. It should be labeled "Destroy your Phone"
OP - Original Post - This refers to the first post in any given thread, the one that started the thread in a discussion forum. A common noob mistake is to hop into a thread on page 27, read for 30 seconds, and then chime in with a question. He is often directed to the OP, which contains the answer to his question.
OTA - Over the Air - These are the official firmware upgrades that Verizon has released over the life of this phone. They were either pushed out to our phones in the middle of the night or offered up for us to download at our convenience. The latest one, EH03, came in December of 2011. Generally speaking, rooted users do not receive OTA updates. Also generally speaking, this doesn't really matter. The updates can be found on xda, and it is unlikely that the Fascinate will ever receive another OTA update.
Patch - This generally refers to a zip file that can be flashed using CWM. The file usually contains updates or small modifications to an existing ROM or kernel. A great example is the patch that reprograms the phone dialer's voicemail button to open Google Voice instead of the standard voicemail or Visual Voice Mail.
PDA Button - This is the button you will want to use when using the Odin program. You should always avoid the "Phone" button.
Pit file - This is a type of file used with Odin when returning your phone to stock. There is a "Pit" button on Odin you can push to enter the pit file you wish to use. An example of a pit file that you will probably use is Atlas_v2.2.pit. To return to stock, you would use a pit file along with a stock ROM, putting both into Odin at the same time. Droidstyle's guide provides detailed instructions.
Project Butter - This is a Google initiative, launched with Jelly Bean, aimed at reducing phone lag, both real and perceived. It involves research into human visual perception, the pairing of GPU and CPU, graphics buffering, and so on. It's purpose is to make your Android phone run "like buttah."
PWGB - Powerwashed Gingerbread - This is a custom ROM created by ccampos784 (with other credits given). Its name implies what it is, a cleaner version of Gingerbread. In its day, it was widely regarded as a well-debloated reliable ROM.
Radio - a.k.a. Modem - This generally refers to the software that manages the phone's connection to the outside world, not the physical device itself. Verizon would release new versions of this software from time to time in their OTA updates. The two most popular ones are currently EH03 (the latest) and EC09. Both of these work with Android 2.3 and the various Android 4.0 ROMs. The choice of radio can determine your 3g download speeds. It's difficult to say that one is better than another. Different users find good results with each one. Both radios are available as zip files that can be flashed in CWM.
Recovery - Your phone comes with a recovery program. You have to choose to boot it up as an alternative to booting up your phone's normal touchscreen interface. An ordinary phone user would probably never even see this program. It's not pretty. It's just functional. It is basically a list of commands and technical terms that you can navigate using the phone's softkeys, volume up & down buttons, and the power button (to select). *Note, the touchscreen is being used more and more in newer recovery programs* Essential to rooting are the special recovery programs such as CWM Recovery. A special recovery program, which is flashed via Odin, will replace the stock recovery program for a rooted user.
Re-Partition - This is one of the check boxes in Odin. This box should be checked only when returning your phone to stock. Of Odin's various check boxes, this is the only one for which widespread agreement of its use exists.
ROM - This is one of the two main components (kernel being the other) of the software running on an android phone. It generally determines the overall appearance of your phone, including which apps are installed by default. The ROM that comes installed on your phone right out of the box is known as the stock ROM. Created by devs, there are numerous custom ROMs available for the Fascinate. Popular Gingerbread ROMs a newly rooted user might try are Superclean3, PWGB, and GeeWiz. The current favorites of the Fascinate community are CM10, AOKP Jelly Bean, and ParanoidAndroid Jelly Bean. The process of flashing a custom ROM to your phone will, generally speaking, erase everything on your phone.
Root - When you buy your phone from Verizon, Verizon still controls it. You are simply a user who is allowed to perform various Verizon-approved activities on it. Gaining root access to your phone grants you the control that Verizon had previously held. Rooting quite literally makes you the "Superuser," opening numerous possibilities for improvement, customization, and ruin. Root access is essential to having a fast, fully customized phone.
Root Explorer - This is an app downloadable from the Android Marketplace (Google Play). As it requires Superuser permissions, it is only functional for rooted users. Its abilities far exceed those of standard file management apps. For example, Root Explorer can copy .apk files directly into the system/apps folder in Android. It's a great way to get that obscure Samsung widget reinstalled on your phone after your favorite developer's ROM washed it away and called it bloat.
Samsung Drivers - This is a small piece of downloadable software that will need to be installed on your home computer before it will be able to communicate with your phone (via Odin or adb).
SC3 - Superclean3 - This is a popular custom ROM created by Nitsuj17 (with other credits given). It has a lot of bloat removed, and it has several excellent additions. It also has a wide variety of readily available patches that allow users to further customize or reinstall things they miss about the stock ROM. It is known for being both fast and stable, and it is widely regarded as an excellent choice for newly rooted users interested in trying a custom ROM.
Skin - This is a program that a phone manufacturer creates with the goal of making its phones more user friendly. It is basically an interface that sits on top of the pure Android guts underneath, hence the term "skin." The skin that comes with Samsung phones is called TouchWiz. This is why our phones don't look quite the same as our friends' HTC or Motorola phones, even though they are all using Android. Some people love TouchWiz. Some people hate it. Some custom ROMs are designed to be used with TouchWiz. Others are designed to be rid of it.
SOD - Sleep of Death - This is when your phone goes into standby mode but then goes into a catatonic state somewhere between being asleep and completely powered down. Users report various degrees of SOD. Some ROMs and kernels have been associated with it, as have certain apps, certain radios, and certain SD cards. Experimenting with fringe OC/UV and didle settings are often responsible these days. Generally, a battery pull (or better, Volume Up + Power) will revive the phone. Once a phone experiences a SOD, it seems likely that it will happen again, so a fix will need to be instituted. A modification of OC/UV settings or a return to stock and clean installation of your ROM, kernel, and apps are recommended.
Superuser - A rooted phone will have a new icon in the list of apps called Superuser. This is what distinguishes a rooted phone from a non-rooted phone. There are numerous apps available on the web and Android Marketplace (Google Play) that require "Superuser permission" to do what they do. Common examples of these apps include NS Tools, Titanium Backup, Root Explorer, Voodoo Sound, NS Tools, and Voltage Control. When a rooted user first runs one of these special apps, the app will ask for Superuser permission. Since you are now the Superuser, you get to press the button that says allow or one that says deny.
S Voice - Korean Siri, courtesy of Samsung.
Swype Beta - One of the early perks of rooting, the latest version of Swype is not available to unrooted users because the Fascinate comes with a special pre-installed (and perhaps outdated) version of Swype. Upgrading gives a slicker version of Swype with a more advanced word selection logic. You must follow a few steps to do it correctly:
1. Change the input method to the Android keyboard (settings->language & keyboard).
2. Uninstall Swype using Titanium Backup.
3. Go to the Swype website, give them your email address, and then follow their lead.
*ICS and JB ROMs don't contain any traces of Swype, so steps 1 and 2 can be skipped for them
.tar - This is the file extension for the files that get flashed via Odin. The file to install CWM, for example, is a .tar file. Another example is the file that returns your phone back to stock.
TB - TiBu - Titanium Backup - This is an app available on the Android Marketplace (Google Play). It is for rooted users only, and it requires Superuser permissions to operate normally. Its two main functions are:
1. Creating backups of your phone (or parts of it) in case you screw it up
2. Freezing or uninstalling apps and other stuff you don't want (i.e. debloating)
Telus - This is a Canadian telecom company. They offer a Samsung Fascinate that is very similar the one from VZW. The Telus Fascinate only works on a GSM network, whereas the VZW Fascinate works on CDMA (GSM and CDMA are different wireless signal technologies). Kernels for the Telus Fascinate won't necessarily be interchangeable with those for the VZW Fascinate.
Thanks button - Once you have created an established account at xda and made a post or two, you will begin to see a button with a little thumbs up sign next to the word "Thanks." This can be found on the lower right corner of someone's post. Pushing this button lets the person who posted know that their work is appreciated. It is considered polite to thank anyone who has helped you, whether or not it was in direct response to your own question. It is always polite to thank the devs whose software you are using. Xda tallies these thanks and gives experienced users a quantifiable measure of their contributions to the community. You will see a thanks meter under other users' names. Helpful people and prolific devs can have hundreds or thousands of thanks.
THS - Team Hacksung - This is a group of developers whose mission is to bring all the best of the custom Android world to Samsung phones. For our purposes, they are currently working with the CyanogenMod code to bring JB to the Fascinate. As CM9 developed, THS worked to make sure it was available for our phones in the form of an easily flashed ROM. In reading about ICS ROMs, you will regularly come across references to THS Build 2. This is a very old version of THS, but it is critical to the installation of our ICS ROMs. THS Builds 1 and 2 contain code that preps our phone to run ICS ROMs. Therefore, if you are coming to ICS for the first time, it is recommended that you flash THS Build 1 or 2 (usually 2) and let your phone boot up one time. Droidstyle's guide will walk you through this process.
Troll - This describes a person who attempts to transform a civil forum discussion into a battle of harsh words. They generally lure people into a massive argument by posting inflammatory remarks that are just slightly off topic. They then sit back and laugh to themselves as the argument develops into the nerd equivalent of a bar fight. To feed a troll and make him stronger, just respond to him. To weaken him, report his posts to moderators.
TSM Resurrection - This is a custom ROM developed by TSM (teamsbrissenmod). Think of it as the "SC3 - The Director's Cut." While similar to SC3 on the surface, it has numerous additions that allow for customization.
TW - TouchWiz - see "Skin"
TWRP - TeamWin Recovery Project - This is an alternative to the traditional recovery program. Rather than using the volume rocker, softkeys, and power button to interact with it, a touchscreen interface is used. While it offers some interesting potential, it is still under development in terms of compatibility with the Fascinate and our popular ROM/kernel setups.
UV - Undervolting - This is a means of attempting to reduce battery consumption when using custom kernels. Rooted users can accomplish this through one of several apps, with Voltage Control and NS Tools being common examples. The point of whether UV reduces battery consumption is highly contentious, but there does seem to be a theoretical basis for its validity, as well as a preponderance of anecdotal evidence.
Voltage Control - This is an app available on the Android Marketplace (Google Play). It requires root access (i.e. Superuser permissions). When used with compatible kernels, it allows you to overclock and undervolt your phone. This would predominantly be used with Gingerbread-based ROMs.
Voodoo - Project Voodoo is a collaborative software development effort started by dev supercurio back when Galaxy S phones first hit the market. Its goal was to optimize the Galaxy S, bringing it up to its full potential. Voodoo innovations have been used by countless rooted users. Voodoo features can only be used on compatible custom kernels. The project consists of three main branches:
1. Voodoo Color - optimizes screen images/video *Not really available in most modern Fascinate setups, but people still talk about how they miss it.
2. Voodoo Lagfix - see below
3. Voodoo Sound - optimizes sound quality for audiophiles *The Voodoo Sound app is available from the Marketplace (Google Play) to control settings.
Voodoo Lagfix - For BML ROMs, there are basically two main types of kernels: Loodoo Lagfix and non Voodoo Lagfix. The stock kernel that comes with your phone is non Voodoo Lagfix. It uses a certain type of file organization that is considered extremely stable. It is also somewhat slow, evidenced by the lag many users have experienced on this phone from day one. Non Voodoo Lagfix kernels, slow and reliable, are the family sedans of kernels. The Voodoo Lagfix kernels are the sports cars. They organize file systems differently, allowing for reduced lag. To extend the metaphor, they are also more likely to be involved in crashes. Lacking the rock solid reliability of their non Voodoo counterparts, Lagfix kernels have a somewhat sordid reputation in older forum posts. Overwhelming evidence, though, seems to indicate that many of the later ones are quite stable. Many rooted users will tolerate the occasional force close or reboot to gain the speed benefits that Lagfix kernels provide. MTD based ROMs (CM7, MIUI, anything ICS or JB) use a completely different file organizational scheme, so they have no need for Lagfix.
Examples of kernels without Voodoo Lagfix: Stock, GeeWiz
Examples of Voodoo Lagfix kernels: KGB, Lean Kernel
*Note: Changing to a Voodoo Lagfix kernel or switching between Voodoo Lagfix kernels requires no special precautions. Changing from a Voodoo Lagfix kernel to a non Voodoo Lagfix kernel requires special precautions.
Wipe x3 - This term refers to the act of wiping the slate clean on your phone. It removes all apps you have installed and any data associated with those apps. It will not erase Android, your ROM, your kernel, or anything on your sd card (your photos and videos are on your sd card by default). The Wipe x3 is often done before making major changes to your phone's system. The process is accomplished through a recovery program such as CWM. Here are the 3 commands (hence the "x3"):
1. wipe data/factory reset
2. wipe cache partition
3. wipe dalvik cache
*Note, performing a wipe data/factory reset will reportedly wipe the cache partition and the dalvik cache, so steps 2 & 3 may be redundant.
zip - For our purposes, this refers to the file type for files that can be flashed with CWM or other recovery programs. For example, if you would like to install the Superclean3 ROM, you would need to download the zip file called sc3_milestone2_full and place it on your sd card.
I like how you split it up, to keep additions in alphabetical order. Nice job.
Sent from my SCH-I500 using xda premium
looking good sir! hopefully this gets stickied!!
droidstyle said:
looking good sir! hopefully this gets stickied!!
Click to expand...
Click to collapse
Your thread first, sensei.
Even better jawman!
Terminators run on Android
droidstyle said:
looking good sir! hopefully this gets stickied!!
Click to expand...
Click to collapse
jawman27 said:
Your thread first, sensei.
Click to expand...
Click to collapse
Both of your threads should be stickied - and droidstyle's thread should have been stickied long ago.
Terminators run on Android
skynet11 said:
Both of your threads should be stickied - and droidstyle's thread should have been stickied long ago.
Terminators run on Android
Click to expand...
Click to collapse
I think we have moderators mia
Sent from my SCH-I500 using xda premium
Sticky please
Sent from my SCH-I500 using xda premium
This is very clear and concise, thank you!
cotton42090 said:
This is very clear and concise, thank you!
Click to expand...
Click to collapse
You're quite welcome.
To everyone: I'm open to suggestions from noobs and senior members alike, so everyone should feel free to post any additions or changes they'd like to see.
Seeking advice from my more knowledgeable buddies...
Please check out the definition for bootloader, and let me know if it's ok. I've been doing a lot of research, but I keep bumping up against the fact that I'm still a noob.
Next, I think I'll tackle i/o schedulers and governors. I probably won't give specific differences in logic, but I might do something along the lines of -
conservative - defaults toward battery savings at the expense of performance
performance - running at max speed all the time (useful for benchmarking)
smartass, interactive, ondemand - all use a slightly different logic to determine when to speed up or slow down the processor, seeking balance between performance and battery consumption.
All input is definitely appreciated.
Did not see a bootloader definition
Sent from my SCH-I500 using xda premium
Alphabetized under 'BL'. I've kept it as a standard to alphabetize under initials used in forum posts, only because that's how the idea for this started for me....decoding of abbreviations.
I suppose this thing is big enough now that it's become more of a Ctrl+F glossary. I'll consider changing the alphabetization scheme if I hear feedback in that direction.
jawman27 said:
Alphabetized under 'BL'. I've kept it as a standard to alphabetize under initials used in forum posts, only because that's how the idea for this started for me....decoding of abbreviations.
I suppose this thing is big enough now that it's become more of a Ctrl+F glossary. I'll consider changing the alphabetization scheme if I hear feedback in that direction.
Click to expand...
Click to collapse
Looks good to me
Sent from my SCH-I500 using xda premium
Nice guide, certainly another good resource to point noobs to in order to expand their knowledge! Just noticed a couple minor things reading through it.
Bootloader - The locked bootloaders of Motorola phones doesn't so much make them harder to root (doesn't make it easier either), but it does mean that they cannot use custom kernels. Since a custom kernel is part of roms like CM7/9, it was very difficult and time-consuming for the developers to come up with a workaround, although it did finally happen in the form of 2nd-init.
Kernel - I don't think that saying you HAVE to flash a custom rom before you can use a custom kernel is entirely true. For example, you should be able to use KGB on stock Verizon EH03, unless I am mistaken. Obviously, any AOSP kernel requires a custom (AOSP) rom.
Recovery - Might want to clarify the differences between stock and the custom recoveries used for the fascinate (which ones are used for stock-ish TW roms, which are used for MTD). Also, using a custom recovery, you can navigate using the soft buttons, you don't have to use the volume and power keys (although you can if you wish).
SOD - I'm not sure which apps, radios, and SD cards have been associated with SOD issues? In my experience, it's been more kernel-related and can often (but not always) be avoided with the correct settings.
UV - There's some good info here regarding undervolting and other battery draining benchmarks. It's from the Nexus S forums, but their hardware is essentially exactly the same as ours.
Voodoo - You talk about lagfix, but don't mention voodoo sound or color. Also, the only "voodoo" implementation in icy glitch is voodoo sound.
Thanks. That is great info. I'll get to tweaking. I've actually been reading up on voodoo sound and color so as to modify the whole voodoo section.
[?]Let me run this by you guys to see if it sounds correct: Voodoo lagfix is only for BML based ROMs because of the nature of the file systems they use. MTD ROMs use a completely different (superior?) organizational scheme, eliminating the need for lagfix.
....learning as I go.
k_nivesout said:
SOD - I'm not sure which apps, radios, and SD cards have been associated with SOD issues? In my experience, it's been more kernel-related and can often (but not always) be avoided with the correct settings.
Click to expand...
Click to collapse
I based this on forum reports from various users describing how they got rid of frequent SODs. They weren't always Fascinate forums. The main app culprit that kept coming up was something called Youmail. The radio reports were just a couple of people saying that flashing a new radio helped. SD card formatting advice abounds, but mostly in older posts (ca. 2010). Another thing that came up a lot was the loss of a WiFi signal. I suppose that could be kernel-related, though. The SOD is not something I've ever experienced, so I'm hardly an authority.
It seemed in reading, though, that there is no one true SOD, but rather several variants. It also seemed that the cause wasn't always easily identified. Perhaps there is more current data debunking all of these old theories. Comments?
My X2 broke again few days ago and this time im up for new Phone because the cost of repair is to high compared for the value. Also i need more battery & a (better) working Camera. Also i need to re-new my Phone Contract, so i can get a new Phone cheap. Before i leave i wanted to share my experiences for new or senior users which use/plan to update to 8.1. This Phone is very tricky, so it may save you a lot of work ^^
--- HOW-TO: Get best 8.1 battery/experience + gps fix ---
~ During my time with victara, I tested all 8.1 ROMs for a long time, gone thru log's, tested a lot of other stuff's and this is my result: (if you want to use X2 as an daily driver) ~
~ This applies to mostly all 8.1 based ROMs ~
1. From system/vendor/lib/hw/ delete power.msm8974.so = this lib is not used by anything since long and it just constantly crashes EVERY damn time you touch the screen. After deleting, reboot device and feel the speed increase instantly.
2. If you're a not playing RAM intensive games, use the SwapTorpedo Magisk module, it gives much more speed by disabling zRAM, which in turn saves a lot of CPU uptime. Our 2Gb RAM are enough to run even 3-5 heavy or more Apps simutanesly.
3. In developer settings at the bottom there is "background check" you can disable it for allmost ALL user Apps like fb etc. Notifications will still work no worry, they go thru Play Services. Also don't disable background check for Playstore & GServices = will result in crashing loops (internally), also you should keep all the calendar and contacts sync open if you want that feature.
4. Greenify has not much power on Oreo, dont use it. Use Naptime for great standby! ( keep "disable on charger" for GoogleSync to work properly)
5. footej Camera delivers best results on this semi broken camera...
6. Put as much Apps into /system partition, because they are faster then (use "stock" GApps package) and reflash it with an updated GApps package every now & then if you update your ROM (maybe once or twice a month)
--> on startup Android automaticly detects if there's a newer version of app in /system & deletes the one in /data ^^
7. If you want fast and fixed GPS then replace the file in /system/etc with my attached one. (unzip it 1st!) Works on all ROMs for victara!
8. Our APNs list file is outdated as hell, i suggest manually edit your settings. --> in "type" add: "default,mms,supl,ims" (supl is for location services and ims for things like VoLTE config)
9. There is a wifi config file missing in /system/vendor/firmware ... /prima/HERE [i dont remember extact location], but you will see WCNSS.conf (or similar name) file which is 0 bytes... copy the original one from /system/vendor/etc/wifi/prima to that location & reboot
10. Bad in-call sound quality & low volume fix: open build.prop in /system
Code:
persist.audio.fluence.voicecall=true
change value to
Code:
persist.audio.fluence.voicecall=false
Code:
ro.config.vc_call_vol_steps=7
change value to
Code:
ro.config.vc_call_vol_steps=8
(stock default)
--> save & reboot. Profit.
12. Allways look if you can disable unused Apps in Settings BEFORE deleting them from /system/app or ../priv-app -> it can cause loops (drain)
13. for getting another hour SOT (tested on new battery, non original but legit one) use Swift black substratum theme for anything. "make use of your amoled"
... will maybe update list later
Most stable, bugless 8.1 ROM? IMO: MokeeOS, why? (good stuff)
-> based on latest LineageOS 15.1 sources, even tho they dont merge every commit from LOS (?)
-> updates every day, even for our chipset
-> EXT4 is allmost 3 times faster than f2fs
-> its rock stable, just no NFC, less flashlight toogle bug, best camera performance of all 8.1 ROMs with footej camera.
BUT YOU NEED TO MOD IT! AFTER EVERY UPDATE. (bad stuff)
- STOP it collecting YOUR usage/location data: download the App i attached. (they removed the option to stop it and added their own location & data miner lol)
-> in system tab -> MokeeSettings -> disable all of its services (stats updating & uploading services etc). It will not affect system, but theres no other way, because they really try to hide it from the user
-> you can also disable analytics from Mokee Pay App
-> after disabling the services, you can uninstall "disable service" app
Dont get me wrong, i dont like many things how they "manage" their ROM & source. Moreover they push their users to donate, for FOSS (=FreeOpenSourceSoftware, get it?). with the work others did, but rebranding, "kanging" it as theirs. (atleast they give credits to Lineage on github). Anyway if your are looking for a stable 8.1 ROM, this is your only choice...
Thank you all in Moto X 2014 forum, i will possibly go for OPO 6 (bad Camera) or S9 (bad Software support by Samsung), cant decide
peace! :fingers-crossed:
Thanks man! i followed your instructions! but i dont know how to do point 2, since i dont know how to install magisk.
Sad to see you go. Thanks for all your works to this aging phone. I still keep mine and I have moved to Moto Z2 Play. Hopefully,I can afford One Plus 6. But,it's not available here. Good luck with your new phone. I'm sure you will enjoy it more.
aBixler said:
Thanks man! i followed your instructions! but i dont know how to do point 2, since i dont know how to install magisk.
Click to expand...
Click to collapse
You simply look for Magisk v16 zip file on xda and flash it in recovery
bejunk said:
You simply look for Magisk v16 zip file on xda and flash it in recovery
Click to expand...
Click to collapse
That's all??? Woow, I looked up on Google and found a couple of complicated tutorials, thanks man.
aBixler said:
That's all??? Woow, I looked up on Google and found a couple of complicated tutorials, thanks man.
Click to expand...
Click to collapse
Yeah. And then you open the app & look for modules. You can test them - and thats the great thing about Magisk - if you dont like them, you can easily uninstall them like an app.
bejunk said:
My X2 broke again few days ago and this time im up for new Phone because the cost of repair is to high compared for the value. Also i need more battery & a (better) working Camera. Also i need to re-new my Phone Contract, so i can get a new Phone cheap. Before i leave i wanted to share my experiences for new or senior users which use/plan to update to 8.1. This Phone is very tricky, so it may save you a lot of work ^^
--- HOW-TO: Get best 8.1 battery/experience + gps fix ---
~ During my time with victara, I tested all 8.1 ROMs for a long time, gone thru log's, tested a lot of other stuff's and this is my result: (if you want to use X2 as an daily driver) ~
~ This applies to mostly all 8.1 based ROMs ~
1. From system/vendor/lib/hw/ delete power.msm8974.so = this lib is not used by anything since long and it just constantly crashes EVERY damn time you touch the screen. After deleting, reboot device and feel the speed increase instantly.
2. If you're a not playing RAM intensive games, use the SwapTorpedo Magisk module, it gives much more speed by disabling zRAM, which in turn saves a lot of CPU uptime. Our 2Gb RAM are enough to run even 3-5 heavy or more Apps simutanesly.
3. In developer settings at the bottom there is "background check" you can disable it for allmost ALL user Apps like fb etc. Notifications will still work no worry, they go thru Play Services. Also don't disable background check for Playstore & GServices = will result in crashing loops (internally), also you should keep all the calendar and contacts sync open if you want that feature.
4. Greenify has not much power on Oreo, dont use it. Use Naptime for great standby! ( keep "disable on charger" for GoogleSync to work properly)
5. footej Camera delivers best results on this semi broken camera...
6. Put as much Apps into /system partition, because they are faster then (use "stock" GApps package) and reflash it with an updated GApps package every now & then if you update your ROM (maybe once or twice a month)
--> on startup Android automaticly detects if there's a newer version of app in /system & deletes the one in /data ^^
7. If you want fast and fixed GPS then replace the file in /system/etc with my attached one. (unzip it 1st!) Works on all ROMs for victara!
8. Our APNs list file is outdated as hell, i suggest manually edit your settings. --> in "type" add: "default,mms,supl,ims" (supl is for location services and ims for things like VoLTE config)
9. There is a wifi config file missing in /system/vendor/firmware ... /prima/HERE [i dont remember extact location], but you will see WCNSS.conf (or similar name) file which is 0 bytes... copy the original one from /system/vendor/etc/wifi/prima to that location & reboot
10. Bad in-call sound quality & low volume fix: open build.prop in /system
Code:
persist.audio.fluence.voicecall=true
change value to
Code:
persist.audio.fluence.voicecall=false
Code:
ro.config.vc_call_vol_steps=7
change value to
Code:
ro.config.vc_call_vol_steps=8
(stock default)
--> save & reboot. Profit.
12. Allways look if you can disable unused Apps in Settings BEFORE deleting them from /system/app or ../priv-app -> it can cause loops (drain)
13. for getting another hour SOT (tested on new battery, non original but legit one) use Swift black substratum theme for anything. "make use of your amoled"
... will maybe update list later
Most stable, bugless 8.1 ROM? IMO: MokeeOS, why? (good stuff)
-> based on latest LineageOS 15.1 sources, even tho they dont merge every commit from LOS (?)
-> updates every day, even for our chipset
-> EXT4 is allmost 3 times faster than f2fs
-> its rock stable, just no NFC, less flashlight toogle bug, best camera performance of all 8.1 ROMs with footej camera.
BUT YOU NEED TO MOD IT! AFTER EVERY UPDATE. (bad stuff)
- STOP it collecting YOUR usage/location data: download the App i attached. (they removed the option to stop it and added their own location & data miner lol)
-> in system tab -> MokeeSettings -> disable all of its services (stats updating & uploading services etc). It will not affect system, but theres no other way, because they really try to hide it from the user
-> you can also disable analytics from Mokee Pay App
-> after disabling the services, you can uninstall "disable service" app
Dont get me wrong, i dont like many things how they "manage" their ROM & source. Moreover they push their users to donate, for FOSS (=FreeOpenSourceSoftware, get it?). with the work others did, but rebranding, "kanging" it as theirs. (atleast they give credits to Lineage on github). Anyway if your are looking for a stable 8.1 ROM, this is your only choice...
Thank you all in Moto X 2014 forum, i will possibly go for OPO 6 (bad Camera) or S9 (bad Software support by Samsung), cant decide
peace! :fingers-crossed:
Click to expand...
Click to collapse
Thanks man, specifically for the power.msm file to delete. The speed boost is amazing!!
Why the **** are developers not merging these changes with their roms? do they just not care?
Galaxyninja66 said:
Why the **** are developers not merging these changes with their roms? do they just not care?
Click to expand...
Click to collapse
Because they are hacks and not the properly way to fix
1.Ext4 is only for System,f2fs is much more faster
2.all other hacks can cause issues...
linckandrea said:
Because they are hacks and not the properly way to fix
1.Ext4 is only for System,f2fs is much more faster
2.all other hacks can cause issues...
Click to expand...
Click to collapse
I do not understand, because some dev say that ext4 is faster and others say it is actually f2fs ... I understand the velocity that f2fs has, but this also brings instabilities to the system, while ext4 is more stable but not is fast as f2fs ... even so they still say ext4 may be faster than f2fs on some devices.the question is, for our victara, what is the best file system?
Leonardoliveira said:
I do not understand, because some dev say that ext4 is faster and others say it is actually f2fs ... I understand the velocity that f2fs has, but this also brings instabilities to the system, while ext4 is more stable but not is fast as f2fs ... even so they still say ext4 may be faster than f2fs on some devices.the question is, for our victara, what is the best file system?
Click to expand...
Click to collapse
F2fs is generally more faster than ext4,
The firstly versions of f2fs(2012-2013) aren't very stable but now f2fs is very stable on the majority of device.
In other words
In general f2fs is a bad idea only if the original kernel isn't shipped with it(not our case)
linckandrea said:
Because they are hacks and not the properly way to fix
1.Ext4 is only for System,f2fs is much more faster
2.all other hacks can cause issues...
Click to expand...
Click to collapse
I have yet to notice a solid speed improvement when switching from f2fs on ANY android device I have owned, plus this isn't the android chef's choice, the user is the one who decides this.
"Not the proper way to fix" - This is irrelevant and only applies if we have a proper way to fix these issues, the fact of the matter is that there is no official fix and these have yet to show any signs of conflicting with anything.
Most "developers" I notice are just creating a real quick build using pre-set instructions then sometimes cherry picking from other device's github sources. I am greatful that work is being done but it makes me want to boot into my old development desktop environment and show these cat's how to make something spicy. It's as easy as adding these fixes into your environment and then building the system image with these changes included, you don't even need to use the terminal to add most of these.
linckandrea said:
F2fs is generally more faster than ext4,
The firstly versions of f2fs(2012-2013) aren't very stable but now f2fs is very stable on the majority of device.
In other words
In general f2fs is a bad idea only if the original kernel isn't shipped with it(not our case)
Click to expand...
Click to collapse
Just wanted to add my 2cents, about f2fs. I generally agree with you and also i read some deep-dive articles in the last few years. To keep it short: To be able to really benefit from f2fs,
you need to have HW (storage (eMMC) chip) which is optimized for it as well as the System/Kernel. f2fs was long in development like you say until it was really better than EXT4. But i think in the case of the Moto X2,
either the HW dont plays well or there is some other problem (i dont know which version of f2fs this phone uses). But what i know, from testing (a lot) and comparing results with an EXT4 ROM, EXT4 was ALLWAYS faster.
In (storage) benchmark apps, especially the random r/w, which is quite important, EXT4 was allways better. When i runned apps like SDmaid, (collecting garbage and doing DB optimizing) it was faster (allmost 2-3 times). Same for games like GTA or others which loaded data. I even mesured it to be sure, took many SS to compare because at that time i wanted to build myself, so i was interested whats better... (than my 2nd X2 broke:crying Anyway try it for yourself & you will see. On my old S3 mini, long ago the dev also updated f2fs version, but it still wasnt better than EXT4, i remember (Lollipop times)
To adress, "that these are hacks": I dont think so because those are doing much good and nothing bad. Maybe its not the most professional way to fix it (commit it properly), but it was the best i could do by then..
- delete power.msm8974.so - really this lib was not used by anything, i spend much time digging the Mokee Sources and doing logs etc... We used the AOSP HAL and the Qualcomm one was just bugging around... It didnt affect anything to delete it by then.. (dont know about now)
- setting "persist.audio.fluence.voicecall=false" its cleaning the sound when you speak to someone in a call using the 2nd mic - but it needs that all plays nicely together. I tested it using 2 phones from friends and off was much better, maybe on stock it works well, but on 8.1 custom that was not the case. Also i found by searching a lot around that many more maintainers disabled it on their ROMs because it wasnt working properly.
- setting "ro.config.vc_call_vol_steps=8" -> its the default value in stock ROM, which i extracted...
- GPS fix was inspired by commit to many devices, which pulled settings via framework - this is the "lazy" version, direct edit. Anyway it was way faster (navigation in maps) no bad stuff in log and secure now.
- about APN file - it was really outdated... & about the wifi file, this is the only one i wasnt sure, but for G3 and S5 (which both are msm8974, custom 8.1) the full file was there?!
ALL the other things are recommendations from me (like IMO), thats why the title of this thread. Last thing, for disabling zRAM (SWAP) it was allready discussed in many tech sites that this is absolutely useless in times of 4+ gb RAM. Also it sucks CPU. In Pie its disabled now. We are on the border with 2gb so its up to personal preferences....
Anyway nice to see you working again on this great device, which i really miss I wanted to better "fix" those, with patches, builds and commits, but my knowledge was to limited to do that so i opted for a diffrent way. Also our source was to messy back then, couldnt really get anything done... and im still learning. Then it broke and that was the end for me on X2.
I wish you all the best, maybe you can do some magic on that device. Peace!
EDIT: Sorry the grammar, its late here and just saw this and had to answer..
bejunk said:
Just wanted to add my 2cents, about f2fs. I generally agree with you and also i read some deep-dive articles in the last few years. To keep it short: To be able to really benefit from f2fs,
you need to have HW (storage (eMMC) chip) which is optimized for it as well as the System/Kernel. f2fs was long in development like you say until it was really better than EXT4. But i think in the case of the Moto X2,
either the HW dont plays well or there is some other problem (i dont know which version of f2fs this phone uses). But what i know, from testing (a lot) and comparing results with an EXT4 ROM, EXT4 was ALLWAYS faster.
In (storage) benchmark apps, especially the random r/w, which is quite important, EXT4 was allways better. When i runned apps like SDmaid, (collecting garbage and doing DB optimizing) it was faster (allmost 2-3 times). Same for games like GTA or others which loaded data. I even mesured it to be sure, took many SS to compare because at that time i wanted to build myself, so i was interested whats better... (than my 2nd X2 broke:crying Anyway try it for yourself & you will see. On my old S3 mini, long ago the dev also updated f2fs version, but it still wasnt better than EXT4, i remember (Lollipop times)
To adress, "that these are hacks": I dont think so because those are doing much good and nothing bad. Maybe its not the most professional way to fix it (commit it properly), but it was the best i could do by then..
- delete power.msm8974.so - really this lib was not used by anything, i spend much time digging the Mokee Sources and doing logs etc... We used the AOSP HAL and the Qualcomm one was just bugging around... It didnt affect anything to delete it by then.. (dont know about now)
- setting "persist.audio.fluence.voicecall=false" its cleaning the sound when you speak to someone in a call using the 2nd mic - but it needs that all plays nicely together. I tested it using 2 phones from friends and off was much better, maybe on stock it works well, but on 8.1 custom that was not the case. Also i found by searching a lot around that many more maintainers disabled it on their ROMs because it wasnt working properly.
- setting "ro.config.vc_call_vol_steps=8" -> its the default value in stock ROM, which i extracted...
- GPS fix was inspired by commit to many devices, which pulled settings via framework - this is the "lazy" version, direct edit. Anyway it was way faster (navigation in maps) no bad stuff in log and secure now.
- about APN file - it was really outdated... & about the wifi file, this is the only one i wasnt sure, but for G3 and S5 (which both are msm8974, custom 8.1) the full file was there?!
ALL the other things are recommendations from me (like IMO), thats why the title of this thread. Last thing, for disabling zRAM (SWAP) it was allready discussed in many tech sites that this is absolutely useless in times of 4+ gb RAM. Also it sucks CPU. In Pie its disabled now. We are on the border with 2gb so its up to personal preferences....
Anyway nice to see you working again on this great device, which i really miss I wanted to better "fix" those, with patches, builds and commits, but my knowledge was to limited to do that so i opted for a diffrent way. Also our source was to messy back then, couldnt really get anything done... and im still learning. Then it broke and that was the end for me on X2.
I wish you all the best, maybe you can do some magic on that device. Peace!
EDIT: Sorry the grammar, its late here and just saw this and had to answer..
Click to expand...
Click to collapse
I agree with you, f2fs in itself is faster than then many applications fail to draw the benefits is another fact (however I'm trying to do a f2fs backport from 3.10y (not very simple because motorola has done many changes departing a lot from the original)),
to talk about the fixes
in PIE I changed the powerHAL to QTI version (which solves the problem)
about wifi config no need to copy it from elsewhere that oreo and pie only see it in / vendor
for the other things i see them as optimization that the user can do only and i have nothing in contrary
Good stuff. Thanks for this. Latest mokee seems to be bug ridden, but I flashed unofficial LOS, and I'm applying these tips. Substratum won't work for me, but otherwise I'm happy so far.
Thanks again.