Posted 20 August 2012 - 07:54 PM
You just wiped Dalvik/ Turned on Debugging or did something else that you were told to do... Take the time to LEARN about what the hell you are doing
****A-Z Android Dictionary, know what the abbreviations mean****
****AOSP**** Android Open Source Project's Website with lots of info
***Wiping Data/Factory Reset***
Wipe data/factory reset does what the name says, it resets the current rom you are using back to its original state it was when you installed it, without the data you added, like your apps and personal data, contacts APN settings, bookmarks etc, thats what it does nothing else, thats what the setting is for in clockwork mode recovery
***Wiping***... What you should be wiping
Go to mounts and storage and select it.
Go to format / system and select it.
Scroll down to format system and select yes.
Go to format / data and select it
Scroll down to format data and select yes.
Go to format / cache and select it.
Scroll down to format cache and select yes
Not Needed but I know I will never hear the end of it if I don't include Wiping Dalvik
Go to Advanced and select it
Go to Dalvik Cache and select it
Your personal files are 100% safe, this full wipe will not wipe the internal sd card and will not wipe the external sd card, all your pictures, mp3s, videos and anything you have downloaded will still be there when you install your custom rom.
However what it will wipe is the first 2gb partition which holds the operating system and all personal user data like your contacts, bookmarks, APN settings for Internet access, accounts etc...
Dalvik is the managed runtime used by applications and some system services on Android. Dalvik was originally created specifically for the Android project. Dalvik is the process vitual machine (VM) in Google's Android OS. It is the software that runs the on Android devices.
***De-Odex*** (I.E. A deodexed Rom)
Android uses a a java based virtual machine as the bases for running programs. This virtual machine is called Dalvik. A .dex file contains the cache used by the Dalvik VM (called Dalvik-cache) for a program and is stored inside the .apk. A .odex file is an optimized version of the .dex file which gets stored next to the .apk as opposed to inside the .apk. This process is done by default to system apps. Deodexing is the process of converting the .odex files back into .dex to be stored inside the .apk so that things can be more easily modified. So a deodexed rom is one that has been through the deodexing process. Deodex can just as easily be called Unodex or any other pre-fix you wish to use.
The radio stack is responsible for the phone functionality of the device. This includes
1)***GPRS*** is a radio technology for GSM networks that adds packet-switching protocols. As a 2.5G technology, GPRS enables high-speed wireless Internet and other data communications. GPRS networks can deliver SMS, MMS, email, games and WAP applications.***
2)***GSM***, a 2G technology, is the de facto European standard for digital cellular telephone service, and it is also available in the Americas. GSM is the most widely used of the three digital wireless telephone technologies (TDMA, GSM and CDMA), and it supports voice, data, text messaging and cross-border roaming. The SIM (Subscriber Identification Module), a removable plastic card that contains a users data, is an essential element in a GSM network.
GSM operates in multiple frequency bands, GSM 900, GSM 1800, GSM 1900. When GSM is working on a radio frequency of 1800 MHz, it is sometimes referred to as DCS 1800, GSM1800 or PCN.****
3)***UMTS***The 3G mobile telephone standard in Europe, standardized by ETSI. It supports a theoretical data throughput of up to 2 Mbps. Initial trials began in 2001, and it should be rolled out in most of the world by 2005.***
4)***GPS operations as well as camera functionality. The version you use depends on who your carrier is as users have reported versions working better on one carrier than the other. The wiki pages contain the latest versions available to download and install.
The bootloader is the first thing to load once you turn on the device, this does the job of booting up the device hardware and loading various items into memory before the ROM starts in the device. The bootloader is also responsible for enabling the flashing of new ROMs and other components such as the Radio and the Ext_ROM.
The central or core software component of most operating systems. Its responsibilities include managing the system's resources (the communication between hardware and software components) and can provide the lowest-level abstraction layer for resources (especially memory, processors, and I/O devices).
Android (like many other Smartphone operating systems) runs on the Linux kernel. The Linux kernel was created in the early 1990’s by a gentleman named Linus Torvalds in Helsinki Finland. It’s incredibly stable, incredibly friendly, and incredibly difficult for the layman to understand and modify. Thankfully it’s also very popular so it has been ported on to a multitude of hardware, including our Android devices.
Think of the kernel as an interface layer between the hardware and software on your device. The kernel decides when things happen, such as the LED indicator gets lit. An application sends a request to the operating system to blink the LED. The operating system then sends the request to the kernel, which makes the light flash for the amount of time requested by the OS.
What sounds like a round-about way to get things done is also what makes the system so scalable and robust. Application developers only have to code in a way the operating system understands and the kernel makes it work on the hardware. This also keeps the application running in it’s own user-space and separate from the kernel. That means when you run the latest uber-cool app that wasn’t designed for your particular OS version, or is still very beta and it crashes, the kernel gives you the option to Force Close the application and the kernel can run untouched.
In a standard Android ROM (we will leave developer images and the like for another discussion) the kernel is bundled along with a set of instructions that tell the device how to load the kernel and the OS during boot. This is the boot.img that you see inside a zipped ROM that your not able to easily open. The device knows to extract this image to internal memory (the ramdisk) and follow a series of scripts (init scripts) to load the kernel and then the other portions of the OS. That’s what’s happening while you’re watching the boot animation. Interestingly enough this is done the same way for a PC, your smartphone, an Android tablet, or even a smart Linux powered toaster. If you’re feeling exceptionally geeky, plug your Android phone into the USB port on your PC and let the PC boot from the USB device. No, it doesn’t actually load, but you can watch the animation while it tries to match up the hardware support with what’s inside your PC. As I said, Linux is amazingly scalable and as a result so is Android.
***OS***... Operating System of course but what does it actually do????
Once the kernel is loaded, the init scripts tell the Operating System to load. Android is the user interface for a custom built Java virtual machine called Dalvik. Dalvik was written by Dan Bornstein, who named it after the fishing village of Dalvik in Iceland, where his family originated from. The debate of which Java VM is superior is best left for another discussion, so I’ll simply say that DalvikVM is a register-based machine versus true JavaVMs which are stack based.
The Dalvik machine creates executable files (.dex files) which can be interpreted by the OS and run by the end user. These .dex files are OS version dependant. That simply means that applications and core functions built to work with one version of Android may or may not work well with other versions. Google provides the tools through it’s Software Development Kit (SDK) for applications to communicate with the OS.
No smartphone would be complete without a set of functions that allow the device to be used as intended. Things like the phone and dialer interface, the calendar, the messaging system are core functions of the Operating System. In Android, these are run on top of the kernel as separate applications. The merits (or lack of) of providing these needed functions as separate applications is once again best left for another discussion, but this is what allows developers like HTC or Motorola to replace the standard functions with alternatives that provide a different look and feel from stock. HTC’s onscreen keyboard or Motorola’s MotoBlur contact list are great examples of this. The “little guy” isn’t left out of the mix either. Handcent SMS or Chomp SMS can integrate into the OS very well, as most of us already know.
An additional set of Core Functions are provided by Google. Popularly called GoogleBits, things like Gmail, sync, Gtalk and the Android Market are applications written by Google that give an extra set of useful functions to the OS. You’ll find these on all smartphones, as well as many other Android devices
Nexus 7 Running [4.1.1][AOSP] Codeman Android 3.1.0 [JB] on top of Trinity Seven Alpha63d
***Gtalk @ firstname.lastname@example.org***
OG ---------> DX ----------> Bionic