Database Users

What to expect after rooting?

I have a relatively new Aria that I have been considering rooting. Several reasons.
1. Not impressed with the onboard memory and would like to delete bloatware such as Peep, AT&T Maps/Navigator/Hot Spots, Footprints, Friend Stream, IM, Latitude, and a few others. A few of those apps keep showing up in my ATK list, so I'd like to just get rid of them, as I have no intent to use them...why let them wreck my RAM?
2. Speed. I've read enough forum posts to believe that my device will run selected apps faster. Make it so.
3. Use MicroSD card for apps. Hate to be limited to the internal capacity. I expect to partition the new SD card, 1GB dedicated to apps. New card likely to be 8GB.
Here are the questions...
1. I'll be getting a new SD card before the rooting begins. How important is the whole Class 2/4/6 thing. Is Class 4 good enough?
2. If I simply swap out the SD card with a new one before the root, what would I lose besides the photos, movies, music that I have manually transferred to the existing SD card?
3. How do I go about backing up the phone for restoration if the rooting thing doesn't work out?
4. What apps/functionality will I find in the phone after the rooting?
5. Is there a list of apps/files that should not be deleted after the rooting?
6. What is all this "flasing ROM" talk about? How do I chose what I should be flashing? What are the differences and does my device model matter in this decision?

I saw your post in the android forums also and will try to help you out. I can't help you much with your questions about just rooting it, as I switched to a CM6 ROM right after I rooted mine. I am also new the the Aria/hacking world and have only had my Aria for 4-5 days. With that said, I'll help with what I can. If anyone sees my n00b mistakes, please correct me.
1. For an Aria a class 4 MicroSD will be plenty. From what I've read, the classes only relate to write speed and not read speed. Class 4 writes at 4MB/s Class 6 at 6MB/s. I believe this means you would just have to wait a little longer for the files to write to the card. Also, read speed is always faster than write speed. I've also read that the speed rating is not universal. Some companies list their Class rating as their read speed instead of write speed. I've read that Kingston is one of the ones that actually list it as write speed. With this knowledge, I decided to buy a 8gb class 4 MicroSD from Kingston.
2. Before you root, I would format the new MicroSD card and move everything from the old one onto the new one.
I'm getting tired... it's nearly 2am and I can't answer your last questions without researching into all of it. I'll quickly type up what I can answer though.
3. When I rooted my phone, I was walked through using the Ubuntu LiveCD in the IRC. I think I made a backup using Clockwork Recovery, but I'm not totally sure if this program comes on the phone or if I put it there. I've read about unrooting some phone, but know little about it. I do suggest using the Ubuntu LiveCD method for rooting though. It definitely was simple. I also suggest going into the IRC if you are unsure of anything in the rooting process. They are really helpful there even though they don't have to be. Here's a link to the Ubuntu LiveCD root method. http://forum.xda-developers.com/showthread.php?t=741824
4. Like I said, I switched to the CM6 ROM right after rooting so I am not familiar with a stock Aria that's just been rooted. I am pretty sure that it doesn't install any apps and just gives you superuser access to modify the programming.
5. Don't uninstall anything that you aren't sure of unless you make a nandroid backup in Clockwork first. I don't believe it's that simple to just go in there and delete important files anyway. I know that on CM6 I had to access the adb to delete some things. I won't get further into that.
6. A ROM is sorta an emulator. Think how people play Nintendo games on their computers. The ROM emulates a Nintendo system on your computer, so a ROM for your phone emulates another operating system on your phone. (in this case Android 2.2 would being emulated on your phone) You don't have to install a new ROM after you root your phone. You can if you want, but you don't have to. As far as what version to install... I do not know the exact differences in each ROM. I am running CM6 Liberty A012 and don't have problems with it. The different builds of CM6 just fix bugs, I believe. I don't think they are 'theme specific', for lack of a better term, meaning that one isn't better than the other for gps use or whatever. Finally, as long as you have an HTC Aria, your device will work for any mod listed in this Aria forum.
Hopefully I didn't confuse you more and hopefully I didn't give the vets of this forum more work to fix my mistakes. I also hope that what I wrote is at least a little better than letting it go unanswered, as I assume you are as impatient for information as I am.

Anthony1s, your post is spot on except for a bit of confusion on what the term "ROM" really means. You basically have the idea right except that it really has nothing to do with emulation. You aren't emulating an operating system on your phone; you are running it natively!
The "ROM" (in terms of how it applies to an Android phone) is basically the main operating system and a collection of apps necessary for the phone to function. When you "flash" a ROM, you are replacing what is currently on the phone with a new version of the operating system. That's all you really need to know as far as Android ROMs are concerned.
For the Aria, there aren't a ton of options yet on which ROM to use. The Liberated ROMs by attn1 are created by taking the default ROM that comes with the phone and making minor adjustments -- namely, deleting a few built-in apps that most people don't want and removing boot up sounds. If you use this ROM, your phone will appear to function virtually unchanged from the way it comes out of the box. Everything will look the same, it will still have Sense UI on Android 2.1 (Eclair), etc. If the only thing you want is to remove some of the "bloatware" apps, I suggest using one of the Liberated ROMs instead of trying to delete the apps manually. It's a lot simpler this way.
There's also the CM6 Froyo ROM. You can read the thread on it to see all the differences, but it uses Android 2.2 (Froyo) with the default Android UI (not Sense UI). Also, if you install this, you have to do a complete reset on the phone to clear all settings/etc., which is not necessary with Liberated. The CM6 ROM is still in an early development stage which means there are probably some bugs that you will encounter although it may not be anything too significant, whereas the Liberated ROM seems to have almost everything working correctly. The main advantage of this build is the fact that it uses Froyo which has some speed improvements for apps among other new features.
Hopefully that answers all your questions.

Thanks Drumist. I got a question that I've had on my mind for two days. I've read that the Nexus One gets more MFLOPS because froyo 2.2 uses a JIT compiler. Does the CM6 ROM use a JIT compiler or is that something we have to wait for in the official release? I don't mean to hijack, but your knowledge reminded me of my question.

Yes, the CM6 ROM has the JIT compiler. It's one of the reasons the benchmarks for the Aria on CM6 are almost double that of the stock rom. You can actually turn it off as well if you hit Menu > Cyanogen Mod Settings > Performance Settings.

My switch and why...plus some questions. Thanks.

Well, even though I actually don't have a problem with WinMo 6.5 outside of a few minor annoyances I've decided to make the switch over to Android...guessing NAND...though, still looking to here about WinMo 7...
I'm just noticing that there is more support and apps being developed for Android and the future of my HD2 suddenly shows more growth...have my fingers crossed waiting for Netflix to resolve the DRM issues they have with Android!
I was always waiting for a solid Android build that actually replaced WinMo (NAND is finally here). During that time I used WinMo and actually liked it. First thing I will miss is the customization. I don't think there's another Mobile OS that beats it in that department...and I REALLY like customizing.
I've been using Android more now and still don't understand how the NAND will work. Have read a lot...as far as installing, that won't be a problem with me. My questions start with customizing. Where will the media folder be? Is there a folder on the SD card that Android associates ring tones with? I make my own ringtones as mp3 files, so i need to know the structure of how Android handles media. WinMo was simple. Also, the Android build I was using did not support USB without major hickups...well...it just didn't work. I'm not going to assume all Android builds are like this, but can I expect Android to be able to link via USB and I can work with it as a storage device and create folders and organize in this manor?
I know you guys work hard and appreciate it, so please do not take this the wrong way. Which Android build is the most stable at this time with all features working? I ask this cuz I notice there tends to be some builds that come along much slower than others and bugs as well as a lack of hardware support can occur. Is there a build that's considered stable and all hardware is supported?
I've basically been trying to make Android provide the same experience as far as apps and ease of use I had with WinMo...I think I'm there.
Does Android have a set structure with Wallpapers...ringtones...documents and such? Example...does each file type have its own folder on the device or storage card in which Android associates the tools which manages them? I always keep my device clean and move all files to the card that don't NEED to be on the device. Is this possible with Android?
Android play well with Microsoft Docs?...Word?
I've always felt that Android ran smoother than WinMo 6.5. I noticed after a while it can get a little sluggish. Is Android like that? I believe Android is Linux base? I'm expecting memory management to better. On PC, I'm use to any Unix based OS to out perform WinAnything with resource management.
I also noticed something strange about some of these apps in the Android market. One, a lot of adds within the apps. Two, a lot of these apps tend to require access of priveledge areas that can be security risks...to make it worse you fine yourself saying why a browser would need access to anything else outside on internet and maybe GPS. Other apps have access to areas that make no sense to me.
Are their security issues with Android...it's market...or apps?
That's all i can think of now. Didn't have a moment to proof read, so please excuse me. Have to take care of a few things. be back shortly.
Thanks.

WOW! What can I say... Ditto. I love WinMo, but I'm fearful that I'm watching it's death rattle. Win Phone 7 seems like a illegitimate infant in a world of fast moving, focused, college freshmen (albeit, not the brightest).

I had a lot of reservations with switching from WM. Mainly related to the phone being able to handle work related stuff. So I too ran WM and android on SD. I must admit though, that after having run android for almost 2 months without loading WM, (I basically pretended I had bought a new phone and forgot all I could do with WM), I had figured out work-arounds and got it running more than sufficiently. The only problem I had was having to back-up the SD in fear of a random reboot corrupting the data.img. Now with NAND, it's no longer a problem. I can honestly say that the switch was easy, and I'm glad I no longer have winmo in my life.
IMO Android is a far superior OS, and I can't sing it's praises enough.
As for all the questions:
Media folder is built like this:
media
->audio
->->alarms
->->notifications
->->ringtones
->->ui
Different folders are available for their obvious uses (i.e. go into ringtone selection, and you don't get the ui folder listed).
USB is more than stable (for me at least), never had a problem since NAND. Having most stuff moved to SDCard the phone hates it when I plug it in as a disk drive, (widgets disappear etc.) but within a minute of unplugging it it's back to normal.
I personally feel the desire build are the best, however as for more stable? I believe we are reaching a plateau where stability is the norm. I have tried nexus builds, and have had no problems with them either, it's just personal taste. The HD builds (Desire HD Base) are a little more 'experimental' but with reading, you'll learn what works on each build, and what doesn't. Figure what's important to you, and check.
The best advice I can give is get hold of SPB Backup (For WM). Do a full backup. Then jump in at android's deep end. (After reading how obviously). If you don't like it, re-flash winmo, redo your backup, and it's like you never left. You won't regret it though.

Man I'd love to dump WM as well, bu I can't bear the thought of all the days going by where I can't be the dude on the bus who reboots into ubuntu to pass the time...sigh.

MattOG said:
The best advice I can give is get hold of SPB Backup (For WM). Do a full backup. Then jump in at android's deep end. (After reading how obviously). If you don't like it, re-flash winmo, redo your backup, and it's like you never left. You won't regret it though.
Click to expand...
Click to collapse
Microsoft My Phone actually does fine with all the backup I need.
I'm still wondering about security issues. Example: http://news.cnet.com/8301-1009_3-20026804-83.html
Also, hit a bump in the road. It would seem that Android doesn't support the Mugen 2600 Extended battery!

The primary security issue with Android isn't Android or Linux, it's Google. Google's security is very problematical, Gmail has been hacked (as has Gmails security software) by someone.*
*Some think it's the Chinese government, the official Chinese response is, "No, it's just kids" but since all hacked accounts we know about have been dissidents, the government theory looks pretty solid....

The primary issue is NOT Google. It's the user.
If you're loading up banking apps on a device that you could lose, be stolen, or bluetooth hacked, then don't blame anyone but oneself.
I've yet to know anyone who's been phone-hacked if that's any consolation.

As a former hd2/android user Id have to say It makes the entire experience of the phone better.
I think it also depends on what you are use to. as far as customizing I would venture to say that there is just as much customization with winmo as there is android. Though id have to say I found myself looking for skins more often than not cause winmo was so ugly to me.
I enjoy having almost direct access to all my data without it having to look like winphone7.
As far as security I think its always been tighter because most people were on different types of phones. now that we have blackberrys and iphones and android phones I think possible viruses will show.
I believe google has a built in kill switch for rogue apps. Also if you buy apps from the legit market you should have no problem!

Ok two things that I'm trying not to get frustrated about before I put a little research into it...
First, why in the world does Android want to crop every image instead of using the entire image as a wallpaper?
I even have wallpapers that are the exact size of the display and Android still wants to crop a small portion of that image?....help please...
Second, why can't I get a simple widget or window dedicated to favorite contacts, such as sense in WinMo does without having to pay for it?
Android doesn't have a simple tool that allows you to setup a favs like Sense does in WinMo? There's this LaucherPro that wants to charge me to do so?
Thanks

Why does Photoshop Express require access to personal information, phone calls and full internet access?

Devils1stBorn said:
Why does Photoshop Express require access to personal information, phone calls and full internet access?
Click to expand...
Click to collapse
checking the install notes It says
the only one that bothers me is the it reads contact info.
the phone state is different than phone info. it basically should shut down when you recieve a phone call. why it needs access to your contacts is why im uninstalling it.
I can also set basic contacts by long pressing a blank spot on the screen and selecting shortcuts>contacts>the actual contact.
wallpaper I believe if you set the picture with the proper resolution it shouldnt crop it

Devils1stBorn said:
Ok two things that I'm trying not to get frustrated about before I put a little research into it...
First, why in the world does Android want to crop every image instead of using the entire image as a wallpaper?
I even have wallpapers that are the exact size of the display and Android still wants to crop a small portion of that image?....help please...
Second, why can't I get a simple widget or window dedicated to favorite contacts, such as sense in WinMo does without having to pay for it?
Android doesn't have a simple tool that allows you to setup a favs like Sense does in WinMo? There's this LaucherPro that wants to charge me to do so?
Thanks
Click to expand...
Click to collapse
1. You can just expand the crop window so it encapsulates your entire wallpaper, if it indeed is in perfect size. Keep in mind the crop window is sized for 3 homescreens or 5 or however many you have, so if your perfect size is for just one screen (480x800) you'll have a bit of a problem there.
2. You can just place contacts on the desktop. That's the closest you'll get without paying for this in LauncherPro. While you're at it, even if you don't want to pay - get LauncherPro and replace the default Launcher already. You'll love its speed superiority immediately.

A lot of devs put permissions on to prevent possible problems, also, not sure if it relates to android, but I know some permissions are needed for things that you would not normally relate them to, possibly things like automatically pausing operations when a call comes in etc...

schunniky said:
1. You can just expand the crop window so it encapsulates your entire wallpaper, if it indeed is in perfect size. Keep in mind the crop window is sized for 3 homescreens or 5 or however many you have, so if your perfect size is for just one screen (480x800) you'll have a bit of a problem there.
2. You can just place contacts on the desktop. That's the closest you'll get without paying for this in LauncherPro. While you're at it, even if you don't want to pay - get LauncherPro and replace the default Launcher already. You'll love its speed superiority immediately.
Click to expand...
Click to collapse
I figured out the contacts on desktop, thanks though!
As for the wallpapers, I do try to expand the Window and it never completely encapsulates the entire image. I just dont get why Android doesn't allow the Wallpaper to remain static while your homescreens maneuver over it.

nook touch answer

hello, today i have receive my nook touch...
i have a question... how do i see a photo (jpg, jpeg ecc...) and read .txt? ?
and, another question... if i root my nook, at startup i can choose the normal mode (with 2 month battery) or do I keep it roored (and the battery does not last long)

Regarding rooting, once you root, it won't go back to original unless you go though the 8 failed boot attempts. But you still can use the original nook reader, social, etc.
I use astro to click on pics and txt, and it opens the proper app (or list all that are able to do so, and I can choose the one I want).

you wiil know when barnes & noble relase a new updating?
the bluetooth has some use?

I'm also waiting for some upgrade, maybe 2.2, not for flash, but for being able to download some extra software. But I haven't seen any news around about this.
Browsing through this forum, I've learned that maybe bluetooth is non-existant, it exist only in the os as a leftover from NC. Gotta wait a little bit more on that.

Perhaps I have not explained well.... i'm waiting for OFFICIAL UPDATE from barnes ad noobles(no android update)....
and one thing I never understood
if i root my nook, at startup i can choose the normal mode (with 2 month battery) or do I keep it roored (and the battery does not last long)
Click to expand...
Click to collapse
thanks a lot!!!!!

The official update can go in two directions:
- Apps update: better browser, fixing some problems with reader, etc., but still using Android 2.1 - Eclair (which is in use right now) or
- OS upgrade with apps update: the same as above, but also changing to Android 2.2 - Froyo, in which you have also the benefit of having some improvements over previous OS version, but may be a little slower, due do increase demand on CPU (if any), or use more battery.
Well, I haven't heard of different battery life from rooted and unrooted version, the only thing is that you may use more battery consuming apps on rooted version, as not all apps are improved to best battery life as the B&N ones.

I'm doubtful they'd go to Froyo with an update because they'd be doing everything they can, at least I hope, to make things such as battery life extensive as possible, so if Froyo is going to use more battery that's unlikely to be a method of progression on the Touch.
There is no Bluetooth on the device, the hardware just isn't there for it, the same way there's no hardware for headphones, or sound of any sort.
Rumor has it that they may be removing the browser completely in the next release, as the initial release was apparently rushed, this would mean that what little of a crappy stock browser is there would be gone completely from the device. Another method they may take with this, may be like the N1E in which the browser became official and more integrated within the system, with official support.
It's doubtful we'll see access to the app store, even though I imagine there could be several apps that could be used even with the e-ink screen. If you want some idea of what might appear or would want to give suggestions for possible update stuff with the next version check out:
http://bookclubs.barnesandnoble.com...sion/N2E-Wishlist-for-1-1-Update/td-p/1056104
None of it's official, but often updates will take a few things from the wish list and add them through the update.
There will be a problem updating if you've rooted. Like with the NC I'm sure that when the update comes, side-loading the update will be broken as it needs a clean /system partition to upgrade to. Also things like TouchNooter won't work until it's been updated with a newer framework.jar

but... if i rooted my nook... can i returmn to official SO? and upgrading? with this guida i can solve? http://forum.xda-developers.com/showthread.php?t=1176783
what do you advise me?
why i can views and download picture but i can't views them in my microsd?
you have an advice for this? for correct heading?
://img94.imageshack.us/img94/1436/22072011296.jpg
and
://img842.imageshack.us/img842/5285/22072011295.jpg
(on link ad <http> )

Moderator, please close. glossary refined and replaced

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.
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.
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
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.
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.
BLN - Back Light Notification - This refers to a popular concept whereby the LED softkeys on the bottom of the phone will blink as a means of notifying the user of missed calls, new texts, emails, etc. Not all kernels are compatible with BLN, and it seems to be a hot topic in the development forums. On phones with compatible kernels, an app will need to be installed from the Marketplace to actually control the settings.
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.
Boot Loop - This happens when something goes wrong and does not allow your phone to boot properly. There are numerous causes and numerous fixes.
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!
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.
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.
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, 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.
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
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. 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, 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.
GB - Gingerbread - Android 2.3. Google likes to name its software releases after sweet foods. Most of our phones are running on this release of Android. There are numerous ROMS and kernels compatible with Gingerbread. These are a good starting point for newly rooted users, as they will feel quite familiar.
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.
ICS - Ice Cream Sandwich - Android 4.0. Google likes to name its software releases after sweet foods. This is Android's latest iteration. It comes pre-installed on the Samsung Galaxy Nexus from Verizon. Several developers have created ways to install ICS on the Samsung Fascinate.
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 a custom kernel will make your phone feel much faster and smoother as it moves through screens and opens apps. To install a custom kernel, you must first install a custom ROM. 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
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.
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. A lot of custom development has been done with the software code from the MIUI system.
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.
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.
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.
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. 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"
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.
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. It is 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. 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 volume up & down buttons and the power button (to select). Essential to rooting are the special recovery programs. The most popular of these by far is CWM Recovery.
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 ROMs a newly rooted user might try are Superclean3, PWGB, and GeeWiz.
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. 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.
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 that require "Superuser permission" to do what they do. Common examples of these apps include Titanium Backup, Root Explorer, 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.
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.
.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. 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 apps and other stuff you don't want (i.e. debloating)
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.
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.
TW - TouchWiz - see "Skin"
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 being a common example. 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.
Voodoo - a.k.a. Voodoo lagfix - There are basically two main types of kernels, voodoo and non-voodoo. The stock kernel that comes with your phone is non-voodoo. 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 kernels, slow and reliable, are the family sedans of kernels. The voodoo 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, voodoo kernels have a somewhat sordid reputation in older forum posts. Overwhelming evidence, though, seems to indicate that many of the current voodoo kernels are quite stable. Many rooted users will tolerate the occasional force close or reboot to gain the speed benefits that voodoo kernels provide.
Examples of non-voodoo kernels: Stock, GeeWiz
Examples of voodoo kernels: KGB, Lean Kernel, Glitch
*Note: Changing to a voodoo kernel or switching between voodoo kernels requires no special precautions. Changing from a voodoo kernel to a non-voodoo 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.

jawman27 said:
Droidstyle's Guide - This is the holy gospel of noob rooting.
Click to expand...
Click to collapse
LOL Best Part!
May i add
"3 finger salute"- slang; this refers to a way of getting into your recovery.[HOWEVER this method is not useful for MTD roms!] holding down the power Button, the volume up, and the volume down button. This could also be used for a phone that is frozen as well to initiate a reboot without pulling the battery.
I know it is in the cwm section but some older devs refer to it as that.
Plus we know most noobs get through one definition of this and TL: DR
But very well put together!! Kudos

"3 finger salute"
Done. Thanks. It's nice to hear feedback from experienced members.

Enyo. - noun. Possible 11 year old prodigy and uberdev. Provides lulz for the Fascinate forums, both intentional and unintentional. See ” KANG".
All kidding aside, this thread is a great idea.

dsrhokie said:
” KANG".
Click to expand...
Click to collapse
All kidding aside, I missed that one.

Kang: The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick) [credit: http://wiki.cyanogenmod.com/wiki/Terminology ]
edit: Got ninja'd on the definition, yours is better jawman....

Well done sir! Between your glossary and my guide, new users will learn everything in a matter of a hour or so....If you look back a year ago this information may of taken a month to aquire.

droidstyle said:
Well done sir! Between your glossary and my guide, new users will learn everything in a matter of a hour or so....If you look back a year ago this information may of taken a month to aquire.
Click to expand...
Click to collapse
Thanks. That means a lot. I may not have ever rooted if not for your guide. I'm all in now, though.

droidstyle said:
Well done sir! Between your glossary and my guide, new users will learn everything in a matter of a hour or so....If you look back a year ago this information may of taken a month to aquire.
Click to expand...
Click to collapse
Yup yup... took a lot of digging a year ago. Nice work.

This was a well thought out guide. I don't consider myself a noob anymore but I still learned a thing or two (like Nandroid).
I hope this gets stickied!
Sent from my SCH-I500 using XDA App

Nice thread ! I was extremely fortunate to fall under the good graces and guidance of Droidstyle when I ventured ( blindly) into the world of rooting and flashing. I can't even count how many times his guide saved my device. I ALWAYS reference his guide when I try to help people on here. Although it is sometimes frustrating asking " noob" questions in XDA ( flaming) , there are a great bunch of people on here that WILL help at least point you in the right direction . Kudos to the OP for writing this glossary!
Sent from my SCH-I500 using XDA App

A few corrections:
adb - Our favorite Uberdev forgot to finish his alphabet packet (just kidding, Uberdev )
AOSP - a mistaken spelling for soap; even our elected lawmakers forgot to finish their alphabet packets, because they tried to make showering mandatory when they tried to pass a bill called SOPA.
.apk - file extension for an application. In this economy, we often have to file many applications to get even one interview for a job.
Auto Reboot - sometimes, with no warning at all, while you're in the middle of playing Angry Birds, your phone just automatically reboots, usually indicating something wrong with your installation. This is occasionally a bug in the ROM or kernel, but if you're a noob, it's probably your fault
Bloat - this is a nice way of saying you have gas because you ate a few too many chili dogs.
Brick - what thugs sometimes throw through your window so you'll be too scared to snitch on them.
Clockwork Recovery - when your kitchen clock is dead, you may have to replace your battery so it will recover.
Debloated - see Bloat above - this is how you likely feel after you pass gas.
Droidstyle's Guide - this makes it much easier for experienced users to answer noob questions in ROM threads; instead of actually answering the noob's question directly, you can say "just look at Droidstyle's Guide." This saves a ton of typing and a ton of time. Think of it as prescribing chicken soup for a patient regardless of what's wrong with him or her
Eclair - the last thing patients with tooth decay should eat, and the first thing we actually eat.
Force Close - this was what Circuit City stores had to do when the economy tanked and all the customers were getting their electronics from Best Buy.
Flash - what nutjobs sometimes do in public when they disrobe.
Freeze - either what you have to do to your ice cream sandwich to keep it from melting, or one of the villians in the movie Batman and Robin.
Froyo - what hipsters tell themselves is more trendy to eat instead of ice cream.
Gingerbread - building material for a house in a German fairy tale.
GeeWiz - what kids used to say in the 1950s when their parents grounded them.
Ice Cream Sandwich - another bad idea for people with tooth decay. See Eclair above.
Kang - either a nickname for Captain Kangaroo, or one of the three old Klingons in the Star Trek Deep Space Nine episode "Blood Oath."
Kernel - an individual piece of corn. You want as many of these as possible to pop (without getting burnt) when you microwave your pouch of Pop Secret.
KGB - the principal intelligence agency of the Soviet Union during the Cold War.
Lean Kernel - a low-fat flavor of Pop Secret. See Kernel above.
MIUI - a sound kittens often make when they want your attention.
OC - a teen drama series that aired on the Fox Network from 2003-2006.
Odin - one of the characters in the movie Thor.
Patch - what pirates sometimes wear over one of their eyes.
Radio - what people used to listen to in the 20th century
Recovery - what people have to go through after serious injuries or sicknesses.
Root - the part of a plant that keeps it anchored in the ground.
Samsung Drivers - NASCAR drivers whose cars have the Samsung logo on them.
Skin - what certain celebrities show too much of on the red carpet.
TB - an acronym for tuberculosis.
Troll - a short, ugly character from a fairy tale; these often live under bridges.
UV - a type of radiation that will give the aforementioned celebrities sunburn if they continue to show too much skin under direct sunlight.
Voodoo - part of a fellow XDA member's username. http://forum.xda-developers.com/member.php?u=4500750
Wipe x3 - the minimum number of times you have to wipe after #tweetingwhilepooping.
zip - what men have to do after #tweetingwhilepeeing (this is often when men ease nature while sitting down so they can keep using Twitter on their Android phones).
Terminators run on Android

Thank you very much.

Sticky it!
Sent from my SCH-I500 using xda premium

In all seriousness, this was an extremely well-written glossary, a valuable resource for the Fascinate community. Very impressive.
Terminators run on Android

Thanks, guys. I'm flattered. I never expected to have such big names even look at this, much less enjoy it.
I should point out to all the noobs reading this that most of the definitions in the glossary are created from the various forum posts of droidstyle, skynet11, neh4pres, xwhofarted, and others like them. Please be sure to use the 'Thanks' button under their names from time to time.

Oh, and nice variant, Skynet. I particularly enjoyed "Patch."

neh4pres said:
Sticky it!
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
I'd love to, but I'm still not clear on the method or etiquette of having a thread stickied.
Should I request myself, or would it be better to have one of the more experienced members do so? I think the glossary has room for improvement (though I've reached the 30,000 character limit), so I'm fine to wait until it's more refined.
To do this correctly, I think we'd need to have droidstyle's guide stickied directly above it. A lot of the stuff at the top of the general section is a bit outdated anyway, so I think it would be a good idea to do it eventually.

jawman27 said:
I'd love to, but I'm still not clear on the method or etiquette of having a thread stickied.
Should I request myself, or would it be better to have one of the more experienced members do so? I think the glossary has room for improvement (though I've reached the 30,000 character limit), so I'm fine to wait until it's more refined.
To do this correctly, I think we'd need to have droidstyle's guide stickied directly above it. A lot of the stuff at the top of the general section is a bit outdated anyway, so I think it would be a good idea to do it eventually.
Click to expand...
Click to collapse
Maybe copy and paste into a new thread and then claim a few posts before others can reply. Then you will have more room.. I'm sure it will be stickied sooner or later.
Sent from my SCH-I500 using xda premium

neh4pres said:
Maybe copy and paste into a new thread and then claim a few posts before others can reply. Then you will have more room.. I'm sure it will be stickied sooner or later.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Will do. Thanks for the tip.

2012 Nexus 7 So Slow It's Almost Unusable

This issue actually started before I updated to 4.4.4. I am currently on 5.02.
I have the WiFi version of the 2012 Nexus 7. I am running the stock Rom, and am rooted (using Wug).
I have several issues with this tablet, but by far the worst is it runs VERY slowly, sometimes taking 15-20 seconds or more to respond to my input.
I have tried doing a factory reset. The problem with that is that the tablet responded better for a day or so, but as soon as I set up my account it began downloading all my apps, making it impossible to determine whether one or more of them is responsible.
I have tried going into developer Options and checking the "Don't keep activities" option. That had no effect.
It's especially maddening when I'm trying to view web pages (using Chrome) and a page takes f o r e v e r to load. Then all those javascript ads that pop up just as the page finally loads (I tried deselecting that as well, but then I can't view slide shows, videos, and user comments on web sites).
It's also fun to click on a link, only to have the page jump right at that instant, resulting in the click hitting an unintended link!
At this point I am out of ideas, other than buying a different tablet, which I can't do right now due to financial reasons.
So my questions:
How do I troubleshoot the speed/lag issue?
How do I prevent my apps automatically installing themselves after a factory reset so I can install them one by one in an attempt to determine whether it's one or two apps causing this?
Is there a pop up blocker available for Chrome (or an alternate browser) to both block, or allow on a case by case basis those dang Javascript ads?
Thanks everyone.
Sent from my Nexus 7 using XDA Free mobile app

leebo said:
How do I troubleshoot the speed/lag issue?
How do I prevent my apps automatically installing themselves after a factory reset so I can install them one by one in an attempt to determine whether it's one or two apps causing this?
Is there a pop up blocker available for Chrome (or an alternate browser) to both block, or allow on a case by case basis those dang Javascript ads?
Click to expand...
Click to collapse
2 of these are easy, the other may take more work.
To prevent the apps from automatically reinstalling, open the play store as soon as the tablet boots up, go to my apps > installed, and click Stop. Then go to Settings in play store, and change auto-update apps option to "Do not update".
There's many adblockers out there, if you're rooted then you shouldn't have a problem installing them. I use AdAway and it works fine, Adblock plus is also popular. Just download the .apk for one you want to use and install it, run the app, then reboot, profit.
As for lag, though it's possible you have an app causing you some issues, this older device is also pretty well known for having a big problem with declining i/o performance over time, and this is more likely the culprit. But any apps that constantly run in the background can exaggerate this further, especially since we also only have 1GB of RAM on this device.
As you mentioned, a factory reset can sometimes help with degrading performance, but it will just degrade over time again through regular use (or as soon as a bunch of apps are immediately restored). This can sometimes be mitigated to a point by using fstrim, but this is not the final solution for everyone.
For me, converting to F2FS format helped with this a lot, it actually felt faster than when it was brand new initially. But it takes some extra work to make the conversion, especially the first time (you have to format your partitions, losing all data in the process, so EVERYTHING you want to keep has to first be backed up elsewhere then restored after conversion). You'll also need to install an F2FS compatible kernel or ROM. Do your research before jumping in if you go this route, and backup your data!

Thanks Prismatic.
I've seen a few posts from people complaining about the slowness of the OG Nexus. Since hardware like cpu's and Ram don't actually slow down (to my knowledge at least), I assume it's usually due to the larger size of newer apps? Like a Windows thing where a version seemingly becomes slower after several years because hardware requirements get more demanding?
But has Chrome for Android really gotten that much larger over these years to cause our little tablets to slow so much? I'm almost at the point where I use my phone (HTC One) more than my tablet for looking things up and browsing.
As far as changing file systems, I'll have to look into whether the community overwhelmingly agrees that the speed gain is worth such a drastic measure. Thanks for the input.
Sent from my Nexus 7 using XDA Free mobile app

Chrome has been a problem (along with Facebook) for my 2012 for a long time. When I did the 5.0.2 upgrade I did a factory reset afterwards about did not let it reinstall apps. I installed some fresh from the Play Store that were essential (none that run continuously) one by one. I replaced Chrome as the default with UC Browser which has Facebook Fast integrated (does FB notifications running in background) and all was like new. The only defect is that you don't have a "share to FB" in other apps. Haven't tried FB Messenger yet either. Beside the system/Google and cloud apps running in the background the major hits are Amazon Kindle and my password manager (50 and 35 MB). UCB (w/FF) are only 7.3 MB. Leaves about 500 free ram.
---------- Post added at 08:11 PM ---------- Previous post was at 08:01 PM ----------
BTW I only keep about a half dozen apps in "Recent Apps" and clear some out when it starts to lag a bit. The 2012 is not up to L's multitasking as L puts each tab or instance of an app there. Open a bunch of tabs in Chrome and you'll see what I mean.

I may try that myself. I already uninstalled FB (I've been suspecting it was a resource hog for a long time now).
I've been out of the loop for over a year though, what is "L"?
Sent from my HTC One using XDA Free mobile app

Let me guess: 16GB version? Those models used really crappy emmc that had a flash firmware bug where IO would get really slow once you hit 2-3 GB free space left on the device. If you're in that position, try freeing up space until you have 3-4GB free. It'll probably speed up again.

rtiangha said:
Let me guess: 16GB version? Those models used really crappy emmc that had a flash firmware bug where IO would get really slow once you hit 2-3 GB free space left on the device. If you're in that position, try freeing up space until you have 3-4GB free. It'll probably speed up again.
Click to expand...
Click to collapse
You are correct that I have the 16Gb version, but under storage it currently says, 8.5Gb free.
XDA Mobile App

Encrypted? If so, it wouldn't matter how much space you have free because as soon as the full-disk encryption operation completed, the internal map in the flash controller that keeps track of free blocks would think that there was no space left on the device (even though the OS and the file system would obviously report otherwise) and the only way to reset it once it gets to that point would be to reformat the file system (ex. Factory reset) which forces the flash controller to clear its internal map and start from scratch.
Either way, if your tablet is not encrypted and you're rooted, you could try to download the LagFix program from the Play Store and have it run fstrim, which would sync up the internal map of the flash controller with the current locations of free blocks of flash memory so the device doesn't keep slowing down trying to manually probe for free blocks every single damn time it needs to do a write operation. You may have to do it every once in a while as that internal map slowly fills up again though (the pro version lets you set a schedule). Theoretically, from Android 4.3 and onward, it's built into the OS and the the OS is supposed to be able to do it automatically based on certain conditions (ex. Idle for a certain amount of time, plugged in or 80%+ battery on a certain schedule), but I found that sometimes it needed to be done more often and it's always nice to be able to run the command manually if needed, although to be blunt, there's no reason why the end user should have to resort to this in the first place. That said, I don't know if LagFix will work on Lollipop (never tried; no longer have a rooted 16gb N7 due to a replacement logic board but a busted USB port so I can't unlock my bootloader to re-root the new board) and the program looks like it hasn't been updated since 2013. One way to find out, though and that'd be to try it.
Switching to F2FS as the file system rather than ext4 might help as well (I really wish I could re-root my device to try it for myself). The speed increases over other file systems when using it on flash memory come from letting the flash controller deal with the disk I/O rather than having the OS schedule things. When you look at the bug and what causes it, it could be the communication between the OS and the flash controller that's the culprit. So using a file system that cuts out the middle man and makes the controller deal with scheduling all the I/O might mitigate the problem (after all, the flash controller works fine when there's lots of free space, it's only when it fills up to less than 3gb of space that the flash controller's algorithm to sync what the file system advertises as free blocks with its own internal map starts to screw up).

I am not encrypted. I will try this LagFix app and report back, hopefully in next day or two. Do you recommend another factory reset first? Is been about three months.
XDA Mobile App

If you want, although I'd try LagFix first to see if that's all you need. If you do go through the wipe, run LagFix every so often to sync things up (assuming it works for you or on Lollipop in the first place).

OK, lagfix does NOT work on lollipop. It gives an error. When I can find the time maybe I'll try to convert to F2FS. Or else when I can find the money, try a new tablet.
Sent from a mobile device.

Question: When you wiped the device previously, how did you do it? If you're using TWRP and use the Advanced options under format to manually wipe /data and internal storage, it'll just use the rm command to delete the files which won't reset the controller's internal map. You need to use the factory wipe option, which will use the mkfs.ext4 commamnd to format the partition (which is what you want). If you've been doing it the wrong way, then that might explain why you're still getting the lag despite having a lot of space still free.
Also, the built-in trim functionality (supposedly) only triggers when the tablet is plugged in or at 70 or 80% battery *and* has been idle for 2-3 hours so if you use the tablet a lot or keep it powered off when not in use, there's a chance that the automated task won't run (and since LagFix doesn't work in Lollipop until the Dev updates it to be compatible, then there's currently no way to manually trigger it). So if you haven't already, try leaving it in powered on and plugged into the wall outlet overnight while you sleep and see if it's better in the morning. Might be worth a shot if all else fails.

Thanks. Yeah, I always leave it plugged in over night to make sure it's ready the next day.
I probably did do a factory wipe, but I'm not certain. Guess I'll try that again eventually.
XDA Mobile App

Cool. Well, if all else fails, there's one last trick to try, which is to zero fill all the empty spaces on the drive to tell the controller that the empty space is indeed empty when it hits the "start probing the file system for empty blocks to perform the write operation" part of its I/O algorithm. You can do that yourself on the command line by using dd to create a giant empty file until the drive is filled up, syncing the file buffers and then deleting the empty file, and then sync the file buffers one last time. There's also an app that can do it automatically, which is just a GUI that calls dd, rm, sync, rm and sync in the background. I forget the name, but it's in the store and I think it has "secure" as part of its name.
I had moderate success with that method as things would speed up again once done, but would slow up again over time as the drive was used. Formatting the partition is preferable because it saves on write operations and thus, wear and tear on the flash drive but the downside is that you lose all your data. And zero-fill was the preferred method outside of re-formatting the partition until someone figured out the fstrim trick. You might be able to run the fstrim command from the command line if you're rooted since LagFix doesn't work anymore on Lollipop, but I forgot what the command line arguments are. Google could probably help with that.
So still a few more things to try before giving up. But I wonder if F2FS would work better. Let us know if you ultimately go that route.

You can run the trim commands from terminal. But I found increasing the minimum clock helped.
Sent from my D6503 using XDA Free mobile app

leebo said:
This issue actually started before I updated to 4.4.4. I am currently on 5.02.
Click to expand...
Click to collapse
WOW same here, I updated from kitkat to 5.02 today and my god, this is TERRIBLE!!!
I keep rebooting in hope that SOMETHING will be better. I know this is an old tablet but I have a good mind to call Google tech support and complain about this abysmal ROM.
I did not do a wipe, just upgraded as you'd imagine that would be all one needs to do, it is a factory upgrade after all...
Some apps take forever to boot and then are inoperable because they can take a minute to respond to a touch (facebook seems the worst)
Others are very laggy but useable (like a cheap phone from 5 years ago).
I guess I have to try a factory reset/wipe.

So just to update: I have been wiping the cache partition about every five days. It lasts about two to three days. I plan on waiting until I have money to get a different tablet before getting a different ROM, or converting to the newer file system (though that will probably be some time from now). In its current condition I can't even give this thing away!
Sent from my Nexus 7 using Tapatalk

Same deal here. When new the Nexus 7 performs great. I have a 2012 8 gb version primarily for platform testing. The interface is so slow now I've given up and just use my phone. The keyboard takes forever to show up. When you first load an app it takes forever and switching between apps takes just as long. The last Nexus and Asus mobile device I will buy for a good while. At least I can still use it to test an app and know that the app will run on a crappy performing device.
Nexus 7 2012 (8gb)
Android 5.1.1
I've done factory resets and it doesn't really help, maybe for a few minutes and then back to the slow clunker. Even after the reset the keyboard is slow as snot to show up.

Just to update, I ended up using Wug's Nexus Root Toolkit to push 5.1 to my Nexus, then I did a factory reset. It had already downloaded 5.1 from Google, but I was desperate.
I had already given up and bought a Samsung Galaxy S 8.1 by then. It's now much faster. Because I bought the Samsung, I'm not using the Nexus very much, so I can't say for certain I cured it. It's worth a try however.
Signature edited to appease the OCD's

I would suggest installing Chroma 22/6/2015. It's very good since Android 5.1.1 fixes some memory leaks over 5.0.2 ^^ It runs perfectly P.S I wanted to sell or blow up my nexus with other roms so it's worth giving it a try ^^ I'd suggest wiping internal storage too after installation so you have a fresher feel ^^
Plz do it :3 You'll not regret it! The UI is pretty coolio too!