I'm creating this A - Z dictionary because I myself struggled a lot with the Android/Thunderbolt jargon when I first entered the Root scene. I would assume that other newly rooted Thunderbolt users will struggle and are struggling with the same thing, and I think a tool like this might help them. Keep in mind that most of these terms are either Android-specific or Thunderbolt-specific (if there is enough variance between the general Android and specific Thunderbolt meaning). So, without further ado...
The Thunderbolt Root User's Dictionary v1.0.2!
VVV A - M VVV
A
A2SD: 1. (abvr., n.) Apps 2 SD [card]. A root-only application used to move applications from your Thunderbolt's internal memory to a separate partition of your SD card. The partition uses an ext filesystem (either ext2, ext3, or ext4), which is the same filesystem that Andorid's internal memory uses. A2SD made its debut in CyanogenMod before the days of Froyo, in which Google added their own method of moving applications to the SD card without partitioning it.
1u. A2SD has a paid version and a free version, both of which are available in the Android market.
ADB: 1. (abvr., n.) Android Debug Bridge. A tool included with the Android SDK (Software Development Kit) which is located in the platform-tools folder of the un-packed ASDK. It interacts with your device by way of specific commands issued by the user from a separate device.
1u. Unless you use a one-click root method, you will have to use ADB in order to root your Thunderbolt.
AOSP: 1. (abvr., n.) The Android Open Source Project. A Google-led project whose goal is to further the development and to maintain the Open-Source Android operating system. AOSP hopes to accomplish it's goal by making the Android source code available to all interested parties, from device manufacturers to private developers.
1u. Cyanogenmod is an AOSP-based ROM.
B
Baseband: 1. (n.) Essentially, a driver for your Thunderbolt's radio. In theory, upgrading your baseband will give you a better radio signal, however in reality, an upgrade could potentially worsen your signal. Usually the baseband version is the same as the CDMA version for any given radio.
1u. Some basebands will only work with certain ROMs.
Bloatware: 1. (n.) Applications which are installed prior to the Thunderbolt's purchase but which serve little or no purpose, are obsolete and/or of poor quality, or are just plain dumb.
1u. Slacker radio, and application pre-loaded on the Thunderbolt, is usually regarded as bloatware.
Bootloader: 1. (n.) A set of code containing instructions for the operating system which is executed at every boot/reboot. Your bootloader has a simple user interface (hboot, see separate entry) which allows for debugging modification prior to boot. 2. (n.) [Unlocked] Bootloader: A bootloader which has been hacked to allow for limitless third party customization. With an unlocked botloader, users can load custom firmware, kernels, themes, and more. From an unlocked bootloader, you can boot normally, into recovery mode, or power down, amongst other options. Unlocking your bootloader voids your manufacturer's warranty.
1u. When you power on your device, bootloader will run before any other applications.
2u. I got my unlocked bootloader today and loaded up Cyanogenmod!
Brick: 1. (n.) A Thunderbolt which makes for a better paperweight than a mobile device; A Thunderbolt which is missing key functionality or which no longer functions and which cannot be recovered by rebooting normally, in recovery, or by means of RUU. 2. (v.) Brick[ed]: To have damaged your Thunderbolt, either physically or on a software level, so that it is beyond repair, at which point it becomes a Brick (see Brick, 1. (n.)).
1u. Adrenelyne: *Eyes closed* Is it a brick guys?
2u. Arednelyne: I BRICKED THE DAMN THING!
Busybox: 1. (n.) A small software application which provides many standard UNIX tools, although these tools are not as capable as their larger GNU Core Utility counterparts. Unless you intend to develop Android, all you really need to know about Busybox is that it is needed in order to root your Thunderbolt.
1u. Just as the self-proclaimed name, the "Swiss Army Knife of Embedded Linux", implies, Busybox is a set of many UNIX tools packaged into a small file.
C
CDMA: 1. (abvr., n.) Actually lengthened to CDMA2000, but often shortened simply to CDMA. CDMA, in terms of the Thunderbolt, is a wireless air interface used to transmit voice, data, and signaling data between the Thunderbolt and Verizon cell sites. It is responsible for your 1X/3G data connection as well as for your voice call connection. Your call connection signal strength is represented by the signal bars in the notification bar at the top of your screen, while your 1X/3G connection is represented by their corresponding icons located to the left of the signal bars (no 1X/3G/4G icon means you have no data connection).
1u. CDMA technology was first used in cordless home telephones.
ClockworkMod: 1. (n.) A popular custom replacement for the stock Android recovery console. With ClockworkMod, users can access advanced commands that stock recovery does not offer. Otherwise inaccessible commands can be executed, such as storage mounting options, .zip flashing, and nandroid backup restoration. ClockworkMod is a tool used often by developers and is something that you will see a lot of as a rooted Thunderbolt user.
1u. I booted into ClockworkMod mode so that I could flash Imoseyon's newest kernel, v15.4926.0010010.666test47
CyanogenMod: 1. (n.) Custom firmware based on the Android Open Source Project (AOSP). CyanogenMod (often shortened to CM, or CM7 for version 7.x) offers features not found in the stock Thunderbolt firmware, and it runs Gingerbread, not Froyo. CM7 is currently in the Alpha stage of development for Thunderbolt users.
1u. Users who use CyanogenMod are able to browse the web in incognito mode.
D
Dalvik: 1. (n.) A virtual machine designed by Google for use in the Android operating system. Sometimes shortened to DVM or DalvikVM. 2. (n.) Dalvik [Cache]: A cache of small .dex files which are used to quickly and efficiently load applications. Basically, when Android starts up, the DalvikVM scans through all of your applications (files with .apk extensions) and application framework. It then optimizes the bytecode (tiny code commonly used for efficient software execution) for each application into a .dex file and stores that file in the Dalvik Cache. The applications are then run using the .dex file (optimized bytecode). By doing this, Android is able to speed up to execution of applications by loading them from smaller .dex files instead of larger .apk files. This is why when you install a new ROM, it takes longer to boot for the first time (because the DalvikVM is scanning and optimizing each application/framework). Every time an application (or framework library) changes or is installed, it’s re-optimized into a .dex file and the cache is updated.
1u. Dalvik is named after a fishing village in Iceland.
2u. Many custom ROMs give you the ability to clear your Dalvik cache at any time.
Debloat: 1. (v.) To remove the bloatware from your Thunderbolt. 2. (adj.) Debloat[ed]: A ROM which comes with some or all bloatware removed.
1u. If you want to debloat your ROM, just flash the debloat patch!
2u. Many ROMs come debloated and deodxed.
Deodex: 1. (n.) A patch of sorts that involved the un-odexing of a ROM. An odex, simply put, is a collection of bits of different applications that have been pulled from their original sources prior to boot with the intent to speed up the boot process. Therefore, a deodex is the patch applied to a ROM which all the bits from all the different applications have been returned to their respective sources. *Note: Most ROMs come either odexed or deodexed.
1u. BAMF ROMs are all deodexed prior to their release (plus they're awesome )
E
eMMC: 1. (abvr., n.) Embedded MultiMediaCard. eMMC is simply a storage solution with MMC interface, flash memory, and controller. The average Thunderbolt user only needs to know that the Thunderbolt uses 4GB of eMMC as it's internal storage, although Android and other system partitions (one for hboot/bootloader, one for recovery, and one for Android itself) take up roughly 1.4GB of that, leaving only 2.6GB that can be used for application and data storage. So in terms of the Thunderbolt, eMMC is just a technical term for internal storage.
1u. eMMC has a high capacity, reliable write, boot, and sleep modes, a dual data date, support for multiple partitions, and security enhancements over MMC.
ETA: 1. (abvr., n.) Estimated Time of Arrival. In the world of Android development, ROMs, kernels, RILs, etc. are created at whatever pace their developers decide to create them at. It is considered disrespectful to demand an ETA for any custom software or code because, quite frankly, we're lucky to have dedicated developers who are kind and talented enough to produce such things at no cost. One should not, under any circumstance, ask for ETAs. Period. /Thread.
1u. Sooooooo.... whats the ETA on that CM7 RIL?
F
Firmware: 1. (n.) In its most basic form, software that has been written onto read-only memory (ROM). However, firmware in the context of Android and Thunderbolt could be defined as the software that drives the device. It is both programs and code whose purpose is to control the hardware of the Thunderbolt, and is therefore essential to your Thunderbolt's operation.
1u. Verizon is pushing out a firmware update on the 30th... NOT!
Flash: 1. (v.) To install custom software, which is packaged into a .zip, onto your Thunderbolt through recovery mode. When you flash a custom ROM, or when someone refers to flashing a patch, the thing being flashed is the thing being installed. Therefore, if the term flash throws you off, just pretend it says "install" instead.
1u(a). I am going to flash the latest version of BAMF later today.
1u(b). Once the patch has been flashed, your data connection should be restored.
Freeze: 1. (v.) Freezeing is a function within the application Titanium Backup which allows the rooted user to "freeze", or temporarially disable, any application (including system applications). Freezing is useful in disabling bloatware that cannot be uninstalled.
1u(a). I am going to freeze My Verizon; that app is annoying!
Froyo: 1. (n.) Version 2.2 of the Android operating system. Thunderbolts currently come with this version of Android.
1u. My Thunderbolt is running Android version 2.2.1, which is categorized as Froyo.
G
Gingerbread: 1. (n.) Version 2.3 of the Android operating system. Often abbreviated to GB.
1u. I wish my Thunderbolt could have some yummy Gingrebread...
GPU: 1. (abvr., n.) Graphics Processing Unit. Your Thunderbolt's GPU is akin to your computer's video card. It is a chip, much like a CPU, which is responsible for manipulating and altering memory/data related to graphical output. A GPU does this more efficiently than a CPU because of the way that such memory/data is arranged (in parallel as opposed to in series).
1u. Imoseyon's kernels offer several GPU enhancements that are baked straight into his kernel code.
H
HBoot: 1. (abvr., n.) HotBoot. Located on a partition of your Thunderbolt's eMMC, HBoot allows you to boot into other eMMC partitions such as bootloader, recovery, and your regular ROM. HBoot is the first thing that runs when you power on your Thunderbolt. By default, HBoot simply loads bootloader when your device is powered on. However, you can boot into HBoot in order to access its various features by using ADB or by holding your volume down and power buttons simultaneously.
1u. Hboot is easily the hardest term to research
HDPI: 1> (abvr., n.) High Dots Per Inch (DPI). DPI is a measure of screen pixel density, so a higher DPI always means a higher resolution screen, meaning a higher definition image. The Thunderbolt, being an HDPI device, has a better screen than the Eris, which is an MDPI device, or Medium DPI.
1u. Some Google App (GAPPS) packages are made for HDPI devices and others for MDPI/LDPI devices.
I
I/O Scheduler: 1. (abvr., n.) Input/Output Scheduler. The I/O scheduler is code that is tasked with deciding the order in which I/O operations are submitted to the eMMC and SD card. Common goals of many I/O scheduler are to minimize time wasted by hard disk seeks, to prioritize a certain processes' I/O requests, to give a share of the disk bandwidth to each running process, and to guarantee that certain requests will be issued in a particular time frame. Everyone has their own opinion about which I/O scheduler is the best for Thunderbolt, and each kernel varies with which I/O schedulers it supports.
1u. The default I/O scheduler for CyanogenMod is BFQ.
J
=====================================
K
Kernel: 1. (n.) The bridge between applications and the actual data processing done on the hardware level. Basically, the kernel talks to hardware components like the RAM and CPU inside the Thunderbolt and assigns the proper amount of each of the component's resources to be used for an application's tasks. In Android, the kernel is also used to control the CPU clock speed and voltage, as well as other hardware-related functions.
1u. You can upgrade your kernel just like you can upgrade your ROM, but only if you're rooted!
L
LTE: 1. (abvr., n.) Actually lengthened to 3GPP Long Term Evolution, but often shortened to just LTE. In your Thunderbolt, LTE is responsible for your 4G wireless data transfer. Although LTE does not officially qualify as a 4G network, it is often marketed as such.
1u. The Thunderbolt runs on Verizon's 4GLTE network, although LTE coverage is currently only in large cities.
M
MD5: 1. (n.) A 128-bit hash that functions as a compact digital fingerprint for a file. Since almost every MD5 hash is unique (although mathematically its not impossible for multiple files to have the same MD5 hash), they are often used to verify the validity of downloads for your Thunderbolt, such as ROMs and kernels. 2. (n.) MD5Sum: [AKA checksum] A program used to calculate the MD5 hash of a given file. You'll use an MD5Summer in order to make sure your downloaded ROM/kernel/mod is 100% good.
1u. Always check the MD5 hash before you flash a ROM or kernel!
2u. An MD5Summer can be found here.
VVV SEE POST #2 FOR N - Z VVV
N
Nandroid: 1. (n.) A complete backup image of your Thunderbolt which can be restored in the event of phone problems or failure. A nandroid can be created in a number of ways, the most popular of which is through the application ROM Manager by selecting the option "Backup current ROM". Nandroids are saved onto your SD card, so wiping your data in order to flash new ROMs won't affect them! A nandroid is the best safety net for users experimenting with unstable ROMs or kernels.
1u. I flashed a ROM for a different device by mistake, so I booted into recovery and restored my BAMF nandroid backup!
Nightlies: 1. (n.) Nightly releases of a ROM, usually one which is AOSP-based. These releases are often less stable than official versions of the ROM because nightlies are changed on a nightly basis, meaning that some small bugs are inevitably overlooked. The CyanogenMod team coined the term and currently hosts nightlies for download on their servers, but only for devices which already have stable CM releases.
1u. Since CM is still working out the kinks in its RIL, OMFGB, another AOSP-based ROM with a working RIL, has begun releasing nightlies.
O
OTA: 1. (abvr., n.) Over The Air. Usually used in the context of an OTA update. 2. (n.) OTA [Update]: An update which is pushed, or sent out over the air, by Verizon. OTA updates are sent to all wireless customers. There are rumors that Verizon will soon send out an OTA update which will take the Thunderbolt from Froyo to Gingerbread.
1u. Verizon patched Android OTA.
2u. Hopefully, Verizon will give us Gingerbreads with an OTA update soon
Overclock: 1. (v.) To increase the CPU clock speed (which is measured in GHZ, or gigahertz) from its stock settings in order to increase the Thunderbolt's processing speed. The long-term results of overclocking on a mobile scale have yet to be determined because the ability to overclock and retain stability has only recently been achieved.
1u. I have my Thunderbolt overclocked to 1.41GHZ
P
Port: 1. (v.) To take a custom ROM/mod/kernel/theme/etc made for one device and adapt its code and architecture to run stably on the Thunderbolt. 2. (n.) A custom ROM/mod/kernel/theme/etc for a device other than the Thunderbolt which has been adapted to run stably on the Thunderbolt.
1u. Many people coming from different devices want their favorite ROMs ported over to the Thunderbolt.
2u. Kingdom is a port that many Thunderbolt users run.
Q
=====================================
R
Radio: 1. (n.) Software which controls all of the Thunderbolt's wireless communication, from CMDA to LTE. Without a radio installed, you won't have a data signal or a network signal. 2. (n.) The radio on the hardware level is what sends and receives wireless signals via the Thunderbolt's internal antenna.
1u. I want to upgrade my radio to MR2 when Gingerbread becomes more stable.
2u. The Thunderbolt's radio can receive data at 4G speeds.
*For general knowledge* >>> Head over to the Obligatory Thunderbolt Radio Thread to get your hands on basic Froyo radios. The first 4 radios on that page are for Froyo ROMs, but the last one is for Gingerbread only! For instructions on how to flash a radio, check out my FAQ Thread (coming soon...)
Recovery: 1. (n.) A mode which exists on a partition of your Thunderbolt's eMMC that can be accessed either through the use of ADB or through bootloader. In recovery mode (stock), you can factory reset your device and recover your operating system by flashing a signed ROM. There are few other options accessible in stock recovery mode. *Note: Not to be confused with Clockworkmod (see seperate entry).
1u. I really want to get rid off all this junk I've installed, so I booted into recovery and did a full factory reset.
RIL: 1. (n.) Radio Interface Layer. Its a large amount of pretty basic code that essentially helps software in need of network access communicate with the radio hardware itself. I'm paraphrasing here, but the process is something along the lines of: An application needs some kind of network usage --> the main phone application --> RIL --> two different RILs, the latter of which sends the signal out to the tower. Its sort of like the kernel of the radio.
1u. CM7's RIL is currently being worked on; when it's complete, CM7 should be headed towards its first official Thunderbolt release!
ROM: 1. (n.) Read-only memory. A ROM, in Android and Thunderbolt, is custom firmware designed either by the device manufacturer (signed firmware, where the word signed indicates its authenticity as manufacturer firmware) or by a third party (custom firmware). Installing a ROM involved flashing the .zip that it is compressed within through Recovery mode.
1u. Flashing custom ROMs is a great way to gain more control over your device!
ROM Manager: 1. (n.) An application used to perform a variety of root-only tasks such as creating a nandroid, downloading a ROM straight to your Thunderbolt, partitioning your SD card in preparation for A2SD, etc.. ROM Manager is included in many ROMs, but it can be downloaded for free from the Android market.
1u. You can use ROM Manager to run a fix permissions script, which is a tool that can sometimes fix force close problems.
Root: 1. (n.) In Linux (which Android is based on), the equivalent of administrative privileges on the system level. Therefore, obtaining root on your Thunderbolt equates to obtaining access to administrative rights on your phone. 2. Root[ing]: (v.) The act of obtaining root access on your phone. This can be done through ADB or by using the newer and experimental one-click root methods.
1u. A root user can edit system files, which unlocks all the potential of custom ROMs.
2u. Rooting your phone is the best way to get a full, unhindered user experience.
Rosie: 1. (n.) HTC's Sense-based dock and launcher application. Rosie is the in charge of your homescreens, dock, app drawer, etc.. It can be replaced by other launchers, such as LauncherPro, ADW Launcher, or GO Launcher.
1u. Most of the things you can do on your homescreens are done within Rosie.
RUU: 1. (n.) ROM Upgrade Utility. A file which allows the rooted user to revert recovery from ClockworkMod to stock, return to an un-rooted state, and turn S-OFF to S-ON. An RUU should be used when all things fail, when root access is no longer desired (ie if you need to bring your phone into Verizon to have it replaced), etc.. The average user will probably never have to use an RUU.
1u. My Thunderbolt's USB port stopped working, so I used an RUU to make my phone look normal and brought it to Verizon to have it replaced
S
S-OFF: 1. (n.) Security-OFF. In order to successfully root a Thunderbolt, flash custom ROMs, and access most /system/ files, you must first obtain S-OFF (the Thunderbolt ships with S-ON, or Security-ON). When S-OFF is obtained, the Thunderbolt no longer scans flashed firmware, boot animations, splash boot pages, or kernels for official signatures, meaning the user is grated full control over his/her phone. You can check your S status by booting into hboot (bootloader).
1u. I gained S-OFF so that I could flash GINGERTH3ORY and bake cookies on my battery
Sense: 1. (n.) HTC's default user interface for most of their Android-based mobile devices. Basically, Sense controls the Thunderbolt's lockscreen, launcher, and theme/skin by default, unless a desensed ROM is used or a 3rd party application bypasses Sense's control. 2. (v.) [De]sense: The process of removing HTC's Sense from your Thunderbolt, allowing for even more customization and no stock feel whatsoever. Desensing is usually done at the ROM level, and most ROMs will note whether or not they are desensed or not.
1u. I personally dislike the default Sense lockscreen, so I installed WidgetLocker and got rid of it!
2u. BAMF Stripped is the perfect example of a desensed ROM.
Stock: 1. (n.) Simply put, the default settings for a the Thunderbolt. A stock Thunderbolt would be one that is un-rooted, unmodified, and otherwise untouched on a software level. Restoring to stock refers to revoking root access and turning S-OFF to S-ON.
1u. You might want to return your Thunderbolt to its stock settings before you bring it in to Verizon and claim you don't know why it caught fire that one time
Superuser: 1. (n.) An application used by root users to grant applications root access. Superuser allows users to select from a variety of different options, including remembering a specific application's root access, meaning it only needs to be cleared for root access once. Superuser is currently the easiest method for granting root access to applications.
1u. Superuser displays toast notifications whenever an application is granted root access.
Swap: 1. (n.) AKA Paging. A memory-management tool that creates a user-defined amount of virtual memory on the eMMC for Android to use in addition to the Thunderbolt's RAM. Using swap, Android can move larger amounts of data from RAM to the eMMC, allowing for more RAM to be free at any given time. Data is exchanged between the RAM and the swap partition based on size and priority. In theory, using swap will increase your Thunderbolt's performance because the RAM is free more often and in larger quantities.
1u. There are rumors that using swap will eventually kill your eMMC due to the fact that eMMC can only be written to a certain amount of times, however no one really knows the long term affects of many eMMC writes, so any claims should be viewed as speculation.
T
Titanium Backup: 1. (n.) A popular root-only application that contains many tools that a root user may want/need to use. Titanium Backup's main function is to create a backup of a user's applications, application data, and system data on the SD card so that a user can clear their data, flash a new ROM, and then restore their backed-up applications and data to the new ROM. However, Titanium Backup can also be used to uninstall system applications, move applications to the SD card, and freeze/defrost applications. Titanium Backup can be downloaded for free from the Android market.
1u. Das BAMF ROMs include the free version of Titanium Backup.
Toast Notifications: 1. (n.) A notification which pops up (much like toast ) to display itself at the bottom of the screen. Many background applications will use toast notifications in order to alert the user to its activity.
1u. Superuser uses toast notifications to notify the user of applications which are being granted root access.
U
UI: 1. (abvr., n.) User Interface. On a stock Thunderbolt, Sense would be considered by most to be the UI, although HTC sometimes agrees and sometimes disagrees. Either way, the UI is usually a graphical, physical way for the user to manipulate the intangible software and hardware contained within a device. A UIs goal is to be simple, visually appealing, and user-friendly, while still maintaining functionality and advanced capability.
1u. Sense, the Thunderbolt's UI, can be almost entirely removed by flashing a version of BAMF Stripped.
V
Voltage: Used only in reference to Overclocking, see O. 1. (n.) Controls how many volts go to the CPU at different clock speeds. A lower voltage means longer battery life, but a voltage too low on a clock speed too high can lead to instability and system crashes. ; under- and over- are relative to stock CPU clocks.
1u. The stock CPU voltages consume battery life very quickly.
W
WIP: 1. (abvr., n.) Work In Progress. Usually used in reference to a ROM, implying that it is not currently finished, or in beta form.
=====================================
X
=====================================
Y
=====================================
Z
Zipalign: 1. (n.) A tool used by ROM developers that optimizes Android application files (.apk's). Essentially, zipaligning a ROM ensures that all applications are compressed relative to the start of the file. All the average user needs to know is that a zipaligned ROM means less RAM consumption, and that's always a good thing!
1u. Most of the popular Thunderbolt ROMs are zipaligned prior to their release.
=====================================
==============ANDORID===============
=====================================
Well that's it for now! I'll be updating this daily for a while (until I run out of stuff to update it with). I'll keep it constantly maintained, and look out for a Frequently Asked Questions thread coming soon!
And just as a footnote guys, I really don't know that much about Android. I created this for myself just as much as I created it for the good of the community, and throughout writing it I learned a lot (you really think I knew what the hell deodex meant? dalvik cache? chyeah, okay). So if you learn something from this, pay it forward, help someone else with the new knowledge you've acquired! I'm totally open to corrections to current entries or even to entirely new entries, just post your thoughts below
ENJOY!!!
Here is a running list of the entries which I'm not sure are totally accurate (I'm actually not sure if any of the entries are totally accurate, but these are the ones I'm sure aren't). If you think something should be changed with one of these, well, you're probably right, so let me know
- ADB
- Bootloader
- Kernel
- Deodex
- Busybox
- ROM
- Radio
- OTA
- Firmware
- Zipalign
- RUU
- S-OFF
- Dalvik
- Rosie
- I/O Scheduker
- Swap
- eMMC
- RIL
- CDMA
- LTE
- Baseband
- HBoot
- GPU
=================================
The Coming-Soon List
- Launcher Application
- Fix Permissions
- Background Application
- Foreground Application
- SIM card
- Root Explorer
- Terminal Emulator
- Linked tutorials for many of these terms are coming just as soon as I figure out how I would like to format them... Stay tuned
If you see a term that you don't understand while navigating the Thunderbolt forums, post a request in this thread and it will be added!
Changelog
6/27/2011 @ 2:30AM - v1.0 released after a full day of typing, 28 entries!
6/28/2011 @ 3:45AM - v1.0.1 released with 20 entries added.
7/7/2011 @ 12:30AM - v1.0.1 with an additional 2 terms and split the OP into two separate posts to bypass character limit.
*** Please let me know if you see any typos, grammar errors, or any other errors that are unrelated to the meaning of the definitions! ***
MattBeyers said:
Changelog
6/27/2011 @ 2:30AM - v1.0 released after a full day of typing!
Click to expand...
Click to collapse
Nice work. Much appreciated!
Sent from my ADR6400L using XDA Premium App
azturbomini said:
Nice work. Much appreciated!
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Thankya
Thanks for this. Coming from only Moto Android phones, I didn't know some of these terms but now I do!
Mods, please sticky.
Sent from my ADR6400L using XDA Premium App
For your ADB entry...
SDK = Software Development Kit
adb is located in platform-tools directory.
Suggestions: Hboot, MR
edit: for thoroughness purposes, those should have their own entries
nerozehl said:
For your ADB entry...
SDK = Software Development Kit
adb is located in platform-tools directory.
Click to expand...
Click to collapse
Fixed
cuguy said:
Suggestions: Hboot, MR
edit: for thoroughness purposes, those should have their own entries
Click to expand...
Click to collapse
Later today, I'll be adding something like 15 more terms, and I'll be sure to sneak those in there as well But could you just clarify what you mean by MR? Do you mean the MR radios?
v1.0.1 released
Added 20 more terms to the list, check it out
Bump. Hopefully this gets stickied soon
Sent from my ADR6400L using XDA Premium App
Absolutely fantastic. Thanks for the effort. If not done yet - mods - please sticky!
Thanks for all the support guys! We've been stickied!! . Watch out for v1.0.2 version later today
Sent from my Mecha using XDA Premium App
MattBeyers said:
Thanks for all the support guys! We've been stickied!! . Watch out for v1.0.2 version later today
Sent from my Mecha using XDA Premium App
Click to expand...
Click to collapse
Good, now I can stop bothering the moderator
Sent from my Xoom using XDA Premium App
This is great. Thanks for getting it started!
Thanks! Great help for noobs.
Thanks fore your time, a good basic primer
Great dictionary for the entry level person. Wanted to double check any new terms coming from my OG droid. Needed clarification on radios and HTC specific terms. Thanks.
Rick
Can I suggest a couple of entry edits which might make this dictionary a little more accurate? Feel free to edit to fit language and format...
CDMA: a.k.a Channel Division Multiple Access: This is the wireless air interface for Verizon, Alltel, Sprint, US Cellular, the virtual carrier Boost Mobile, many portable phones, as well as many satellite uplinks and downlinks. In function, it all devices hosted "talk" to the tower through an assigned code, or language, simultaneously. As opposed to LTE/GSM technologies, which "talk" to the tower based on an assigned frequency and/or time slot. Imagine it like this: the tower knows all the languages on earth and can hear them all at the same time... and speaks them all at the same time. You phone in a particular cell speaks an assigned language so to avoid other phones speaking the same language in the same cell. All handsets are "heard" at the same time, but as distance increases, the handset must "shout", or broadcast stronger, to be heard as well as other devices in the cell, hence the sometimes shocking drain on a CDMA device battery when on a cell's edge.
CDMA2000: A Quallcomm patented communictions technology based on the CDMA mode of air access. Specifically, this pertains to the methods and protocols which towers and handsets use to communicate with each other. Subsets of CDMA2000 would be 1XRTT, EVDO rev.0, EVDO rev.A, EVDO rev.B (not implemented currently).
If any of that is useful, feel free to include it.
Related
Hi All,
Here is my second contribution to the Android community, android2sd!
I tried to make the installation a bit more straight forward and the readme very verbose.
There is NO going into recovery and wiping of the Android to install this construct. (Of course you can if you want to have a clean slate to build from but it is by your choice only!)
Remove .zip from filename, then unrar (sorry to zip users, zip was too big) the package and copy the android2sd.sh install script to the Android say /data/local and make executable with something like chmod 0750 and copy the android2sd.img install image to the sdcard. (Detailed instructions are in the readme file.) Once the install is complete, you can delete both install files.
Execute the script {where ever you installed it}ie:
/data/local/android2sd.sh and follow the instructions.
Included are several of my scripts (updated from the ones in data2sd) and the rules still apply, adjust or remove as you see fit. The readme explains them all.
I have noticed an improvement in speed based on the install, but you can judge for yourself and tweak as you see fit!
The construct uses Overlay Profiles to overlay the Android system and thus any changes to the Android once loaded, are actually done to the overlay profile thus you have like a safe mode which is the untouched Android under the overlay.
Hope you find it useful!
Darkstrumn
Darkstrumn said:
Hi All,
Here is my second contribution to the Android community, android2sd!
I tried to make the installation a bit more straight forward and the readme very verbose.
There is NO going into recovery and wiping of the Android to install this construct. (Of course you can if you want to have a clean slate to build from but it is by your choice only!)
Remove .zip from filename, then unrar (sorry to zip users, zip was too big) the package and copy the android2sd.sh install script to the Android say /data/local and make executable with something like chmod 0750 and copy the android2sd.img install image to the sdcard. (Detailed instructions are in the readme file.) Once the install is complete, you can delete both install files.
Execute the script {where ever you installed it}ie:
/data/local/android2sd.sh and follow the instructions.
Included are several of my scripts (updated from the ones in data2sd) and the rules still apply, adjust or remove as you see fit. The readme explains them all.
I have noticed an improvement in speed based on the install, but you can judge for yourself and tweak as you see fit!
The construct uses Overlay Profiles to overlay the Android system and thus any changes to the Android once loaded, are actually done to the overlay profile thus you have like a safe mode which is the untouched Android under the overlay.
Hope you find it useful!
Darkstrumn
Click to expand...
Click to collapse
Damn man. Good work.
sounds interesting, what is this all about?
brilliant?!? I think.
So basically, this is a non-destructive method that enables us to run new roms on the G1 without flashing? Am I reading this right? If so... wow.
edit: or, erm... maybe not... i think i've been up too long. Gonna have to watch this thread to get a better grasp on this. interesting nonetheless.
Rename To RAR
Darkstrumn said:
Remove .zip from filename, then unrar (sorry to zip users, zip was too big) the package and copy the android2sd.sh install script to the Android say /data/local and make executable with something like chmod 0750 and copy the android2sd.img install image to the sdcard. (Detailed instructions are in the readme file.) Once the install is complete, you can delete both install files.
Click to expand...
Click to collapse
very interesting .. at first i failed to see this part as i'm sure many pay skip over the whole "rename to rar" thing - LOL - so this loads profiles from the SD to the phone
for anyone having trouble with the whole "rename" process try this:
http://files.lucidrem.us/jf/android2sd.rar
as i know windows with hidden file extensions does not allow a rename easily
So what exactly does this do? I see install instructions, but no description.
Overlay Profiles...
tr.slate said:
So what exactly does this do? I see install instructions, but no description.
Click to expand...
Click to collapse
Well,
I've worked up the natural progression to this XXX2SD business, and have made an Android2SD construct which can expand the Android similarly to the the previous constructs, but puts /system, /data and /cache on sd.
So let me explain the overlay thing:
An overlay profile is a snapshot of the Android file system, namely /system, /data, and /cache.
The initial profile is called 'android2sd' and is a snapshot of your android at the time of install, plus the file system structure as explained in the readme adding the mnt/ dir structure and additional scripts in bin/ (which you can remove or adjust as you need).
Typically I reckon folks would only have the one profile and under it your original Android. But you can create additional profiles and set them up however you like. The overlay is overlayed on top of the Android file system with any changes or edits to the system affecting the profile and not the Android under.
The effective change is that the /system /data/, cache are moved to the sdcard thus expanding them to however large your sdcp2 is; on a class 6 card also improving access time.
A second benefit is that the underlying Android is safe from alteration and can be booted into like a 'safe mode'. (It can also serve as the base for new profiles, or you can make new profiles from active overlays. These snapshots can serve as a form of backup, but that is a fringe benefit.
It cannot protect the Android from update.zip installs exactly, as those will modify the Android directly, but say you try a theme and it gafs your 'droid...you can reapply the firmware update to clean out the theme, then copy the desired profile back to the Android and restore the Android to the state of the profile. (I would recommend having a 'base' profile of the Android but not using that as an active profile which will thus serve as a backup) Note: To restore the Android as described above, you cannot restore using a profile with 250+ apps in /data as the Android doesn't have the space for it!
Originally I used unionfs for the overlays but it was too slow.
Hope that explains things here; the readme has far more detail.
I've gotta go, but if I see that I've been as clear as mud, I'll try to explain better when I have more time.
Hmm just out of curiosity: What are you using now? Bind mounts?
I got a little bit lost in setup, I am not sure if I had problems because I was using Cyanogens latest or something else but either way Im going back to JF to try this.
I installed it using the "-COMMIT" addition
But when I made it to installing/linking apps things wouldnt link
Maybe I will let a few other people try it first.
More info...
[email protected] said:
Hmm just out of curiosity: What are you using now? Bind mounts?
Click to expand...
Click to collapse
Yes. Originally it was to have a multi profile layered system using unionfs: union0 the ro base snapshot and union1 the rw profile containing the copy-on-write data. But as the tests went on, the unionfs was too slow to use for /data; Android is unforgiving of unresponsiveness and was ANR'ing the apps that didn't respond fast enough.
The faster bind mount means that union1 is now not used and union0 is rw.
The reason I wanted the union0,union1 path was that the union0 could serve as base and various profiles could be layered over any part of the file system granting "Lego" like flexibility in how the user could adjust their a2sdLoader.sh script (the android2sd loader which controls the overlay process).
You could have a pristine base and several "change" profiles that you layered to your liking and could change any sub layer to different effect.
While you still can under this paradigm, it is not as compact.
But the unionfs option is not completely done away with. It can still be used for the above layering but shouldn't be used for that apps and package system.
An example of the layering I'm on about:
The Android 0-layer which the base layer is a snapshot of.
The base layer is pristine (fully configured settings, but minimal apps loaded, maybe a particular base launcher layout and wallpaper).
A change profile containing my apps and package system
A change profile containing a version of etc with reconfigured bluetooth settings.
A change profile with a theme (manually installed, or snapshot to profile and restored to pristine)
Now I could take these 4 profiles and arrange several different setups:
'base' with all apps loaded, themed with custom bluetooth
'base' with all apps loaded, themed with normal bluetooth
'base' with all apps loaded with custom bluetooth
'base' with all apps loaded with normal bluetooth
'base' with all apps loaded
'base' themed with with custom bluetooth
'base' themed with normal bluetooth
'base' with custom bluetooth
'base' with normal bluetooth
...
Those would be set to serve as the ro union0 and the rw union1 which will hold the copy-on-write changes to the overlay (which preserves the sub layers)
You could have several more theme profiles and have a script that randomly chooses one at boot...
You could simply use the overlay to protect a favored configuration. Should anything untoward happen such as accidentally damaging the packages.xml file while experimenting with the system, you could simply delete the change profile, make a new blank change profile and the damaged files are undone.
The things one can do with the overlay concept are limited only by your imagination and need (and if they slow down app processing too much causing ANR's)
It vary well could if done correctly allow one to have multiple roms as profiles and switch them based on the selected profile, but I have yet to experiment on that...I reckon that is my next move! (Note that this path would have a high space cost as the roms are about 40MB zipped!)
brandenk said:
I got a little bit lost in setup, I am not sure if I had problems because I was using Cyanogens latest or something else but either way Im going back to JF to try this.
I installed it using the "-COMMIT" addition
But when I made it to installing/linking apps things wouldnt link
Maybe I will let a few other people try it first.
Click to expand...
Click to collapse
Taken from [Rom] CyanogenMod:http://forum.xda-developers.com/showthread.php?t=518851
"DO NOT RUN ANY OTHER APPS2SD APPLICATIONS ON THIS BUILD. YOU WILL BREAK YOUR SYSTEM. THEY ARE NOT NECESSARY BECAUSE THIS ROM WILL DO A2SD AUTOMATICALLY AND BETTER!"
The android2sd construct pretty much falls into the A2SD category and thus is likely the reason you had issues with the install.
My Android is based on JF 1.51... and thus your mileage will vary based on the rom you are using. I reckon with a rom derived from theh JF roms, the install may work as intended.
As I go into the next construct build process, I will see if I can't make it multi-rom compatible (to support multi-rom profiles) I'm sure it will take some time to do as I would have to use my actual Android to test with, but no worries!
Hope that helps a little. Sorry it's not better news though.
An excellent "misuse" of this concept would be to run ion (picking it for its speed and almost stock nature) with a hero overlay (picked due to known instability as we are still developing it) so that ion would serve as a "safe mode" for when you crash hero.
I have a spare phone if i crash this and a secondary sd for if that gets corrupted. Let me know if you need help testing.
twistedumbrella said:
An excellent "misuse" of this concept would be to run ion (picking it for its speed and almost stock nature) with a hero overlay (picked due to known instability as we are still developing it) so that ion would serve as a "safe mode" for when you crash hero.
Click to expand...
Click to collapse
Interesting thought, and if this could be done, I suppose it would be possible to have bluetooth working in ION while using a Hero overlay?
Request for feedback...
Hi All,
Those who've installed android2sd, how is it going?
Can you give some pros and cons of your experience so I may improve things going forward? (Hopefully no cons exists!)
I know that roms that already make use apps2sd will encounter issues as the apps2sd and android2sd function similarly and thus step on each other. I may be able to detect this condition and adjust for it going forward...we'll see.
Thanks in advance for your input!
Darkstrumn
LucidREM said:
very interesting .. at first i failed to see this part as i'm sure many pay skip over the whole "rename to rar" thing - LOL - so this loads profiles from the SD to the phone
for anyone having trouble with the whole "rename" process try this:
http://files.lucidrem.us/jf/android2sd.rar
as i know windows with hidden file extensions does not allow a rename easily
Click to expand...
Click to collapse
Thanks for putting the rar up, XDA wouldn't take the .rar and I didn't want to signup to a file-share site just yet.
And it being seemingly natural to make windows show file extensions, it didn't cross my mind to make a note about that.
Thanks again!
Darkstrumn said:
Thanks for putting the rar up, XDA wouldn't take the .rar and I didn't want to signup to a file-share site just yet.
And it being seemingly natural to make windows show file extensions, it didn't cross my mind to make a note about that.
Thanks again!
Click to expand...
Click to collapse
How come no one is trying this? It seems to me an excellent idea and would be really cool to boot mutipe roms if someone figures that out. I'm not testing this because I'm using appstosd and didn't want conflicts...but no one else with jf1.51 Rom is testing this idea?
Just curious
so wait a second. let me get this straight ... if I have a class 6 8gb card i might be able to install a hero build without rosie or widgets with the original launcher on the sd card that might actually come sorta, kinda, a little close to a speed that might be bearable? at least for like 5 minutes?
Can this be adapted to install bigger roms such as hero without the dangerspl .
XD
Ill try this with ion later tonight
wow this is beautiful work! now to test it!
Im trying so hard to understand this lol.. Correct me on my errors but from what i read this is my hypothesis on what i think this does..
This is like a apps2sd but with data and that type thing from the build we are using? And you Said this takes snapshots So we can create several profiles of the phone? Like for example have a profile with some apps loaded and another profile with all removed and be able to switch between them at will?
NOTE: This is old and has been replaced by Fresh Evo 1.0.1. I decided to start a new thread because this one was just too huge.
http://forum.xda-developers.com/showthread.php?t=726090
Click to expand...
Click to collapse
Geek For Me is proud to release:
Fresh Evo 0.5.3 for your Sprint Evo 4g
NOTE: Fresh Evo now assumes that you have NAND unlocked (part 2 of rooting). This means you are fully rooted and have write access to /system/ even when you are booted up. If you have not unlocked NAND protection then you should do so before flashing this rom!
This release was delayed for way too long due to various things out of my control (school, work, other projects, and a crashed hdd last weekend) so I'm happy to finally get it out!
I have been getting asked a lot when I'll integrate the new OTA update. I don't plan on including it until an RUU for it leaks out because it's a much better way to get files than to copy off patched ones. With that said Sprint pulled the update anyways due to it bricking people's phones. Haha. So just be patient and I'll update once it's out. Here's an analogy for you. You install Windows on a computer and then do all the windows updates. You then hunt down the random files that have changed and pull them off that computer, and just copy them over to another computer that hasn't had windows updates done, in an attempt to update it. While that may end up working, it is not nearly as clean as just getting an updated copy of windows that already has the updates on it and reinstalling it. THAT is why I don't plan on putting the OTA in until I have an RUU for it.
Do a data wipe! This version 100% requires one, even if you are coming from Fresh Evo 0.x. This should however be the last wipe required! It has also been reported that Clockwork Recovery is not wiping sd:ext properly. So if you do a data wipe (data, dalvik, cache, and sd:ext) and are still getting FC's or boot loops then you need to flash Amon's recovery and use it instead. In order to flash this rom you need to be rooted (unrevoked method doesn't count as root) to flash this. How To: Root Your Sprint Evo with NAND unlocked. Always make a nandroid backup, I can't be held responsible if something breaks, etc, etc.
Expect 1 loop at the very first boot! This is a side effect of the fixed vanilla lock. The very first time you boot up the phone it will load the lockscreen and then boot loop one time and then come up.
If it continues to loop then go here.
Go here to see all reported bugs: http://link.geekfor.me/freshevobugs -- if you are having a problem then check that page first, and read these release notes in their entirety!
Base: RUU_Supersonic_1.32.651.6
Changes from 0.3 to 0.5.3 (0.4 never made it to an official release):
Added Fresh Updater! Check the How To for information on setting it up and using it. This project has been on the back burner for months, and I'm happy to finally have brought it back and finished it up. Thanks to cyanogen and firefart as it's based on CMUpdater. It is built off of R657 which is the newest commit.
270 degree auto-rotation (you can turn the phone to the right or the left for landscape) -- Thanks to Optedoblivion for pointing me in the right direction
Fully fixed vanilla lock screen -- see screen shots. Use Fresh Updater to grab one of the vanilla patches to enable it. HTC's lock is enabled by default.
Landscape rosie (disabled by default!) -- see screen shots to see the issues with this. It is functional however it is definitely a hack. You will see some issues with using it. It doesn't look pretty, but it does work! Thanks to jschisurf for pointing me in the right direction on this one. NOTE: I have landscape rosie disabled by default! If you want to try it out then grab one of the patches in Fresh Updater to enable it. See the Fresh Updater How To for help with that.
Landscape settings.apk -- no problems here. Works fine.
12 new Rosie widgets. 7 that are available for our phone and 5 that aren't.
Profiles, ringtone, battery, call mom, coin flip, daily challenge, dice, notes, quick record, tasks, tip calculator, and today in history.
These are made by HTC and will only work in Rosie.
802.11N enabled (2.4 ghz only, not 5ghz) -- thanks to chuckhriczko!
Another brand new boot screen! -- thanks to wrx4memp
Updated DarkTremor apps2sd to 2.7 version 3 version 2. Version 3 was moving dalvik-cache to the sdcard even though it was set to not do so. Will upgrade to v3 when it's fixed. Thanks to tkirton!
Fixed wifi tether force close (still using the newest 2.0.5 pre 2)
Stock files have been resigned. This should prevent the need for any future wipes (not counting any major software changes by HTC/Sprint).
Updated launcher pro to 0.6.3
Updated google maps to 4.3.0
Updated estrongs file explorer to 1.4.2.2
Updated rom manager to 2.0.0.2 -- Note as mentioned above that clockwork recovery is currently having issues wiping sd:ext. So if you are having trouble with bootloops or FC's after flashing this rom then you need to use Amon's recovery instead. Additionally because of Fresh Updater, rom manager may not be needed anymore. VOTE BELOW on if you want me to continue including rom manager or not.
I have still chosen to NOT include adless browsing in my rom. I used adless browsing in all of my Hero Android 1.5 roms because it actually blocked ads from the browser. In Android 2.1 this functionality stopped working so I stopped including it. It was pointed out to me that while it doesn't block them in the browser, it does block them in apps (background data). The reason I am choosing to not include this is because as a developer myself, I feel that the authors deserve to get paid for what they do if you want to use their app. If you are choosing to use their free ad-driven application then I don't want to contribute to people blocking those ads and preventing the dev from getting paid.
Fresh Evo Features:
All APK's have been png optimized and zipalign'd
png optimize goes through every APK and losslessly compresses the png (picture) files without causing any type of visual change. This provides a smaller apk file size that loads faster. Each APK has then been zipalign'd. From Android's developer page: zipalign is an archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
While this does free up space on /system/ (as seen below) it is not done to make free space considering we have more than enough. It is done purely for a performance gain. Every day use of the phone will go smoother and stock applications will respond faster. The reason this works is because it has reduced the application file size as much as 50%, so they load in to memory faster and run smoother.
Additionally all applications in /data/ (even ones you downloaded) will be zipalign'd on boot if they need to be.
Not every apk takes png optimization + zip align well. I've done it on enough roms that I think I know which ones cause issues now, but if you are getting FC's on any apps (I can't test them all) then let me know and I'll get it resolved. Thanks!
Apps2sd enabled! Using Darktremor by tkirton.
Apps2sd takes all applications from /data/app and /data/app-private and moves them to a partition on your sdcard. It was originally created for phones that didn't enough enough space on /data/ to store a large number of applications. This has mostly been resolved on the Evo because we have over 400mb of space allocated to /data/. However for some people this isn't enough. Additionally if your apps are stored on your sdcard then you can do a data wipe and they will still be there (albeit settings will be lost, but you won't need to reinstall them).
You do not have to use apps2sd if you don't want to use it. If you just don't format your sdcard with an ext partition (leave it all as fat32 like it is from the factory) then apps2sd will stay turned off.
How to setup apps2sd on Fresh Evo and warnings about apps2sd
Battery optimizations
The stock mms.apk was possibly causing a wake lock. I have swapped it for a different one while I do some testing.
Raised VM kernel dirty page writeback frequency to 15 seconds. This wakes the phone up less often for background VM activity. Every single application in Android is technically running in a VM (virtual machine) so that's why this helps (as recommended by lesswatts.org).
Compcache 0.6.2 / Ramzswap enabled -- Thanks to toastcfh for compiling the modules! Compcache creates a RAM based block device (named ramzswap) which acts as swap disk. Pages swapped to this disk are compressed and stored in memory itself. Compressing pages and keeping them in RAM virtually increases its capacity. This allows more applications to fit in given amount of memory. This will only kick in when the stock memory (which the Evo has plenty of) gets low.
I have tuned the default to be 100mb ramzswap size with 40% swappiness
You can check compcache's use by opening an adb shell and typing: rzscontrol /dev/block/ramzswap0 --stats
ES File Explorer
ROM Manager -- Fresh Evo does show up as an available download in the free version of ROM Manager, so you can use it to update Fresh Evo right through your phone if you want.
Launcher Pro
Wifi Tether (free 3g and 4g wireless tethering)
Qik
Facebook moved to /data/ so that it can be uninstalled
Custom boot screen thanks to wrx4memp!
Added PowerTOP 1.11. From LessWatts.org: Programs can make your [phone] use more power. PowerTOP is a Linux tool that helps you find those programs that are misbehaving while your [phone] is idle. -- Compiled by cyanogen.
To run PowerTOP just open an adb shell and type: "powertop -d". It will scan for 15 seconds and then print out a report.
The first section will show you what % of time your phone spent running at what Mhz. In the screen shot above my phone was asleep so it was at 245Mhz the whole time.
The next section shows wakeups-from-idle per second. 50-80 would be normal. If you are in that range then you don't have a problem.
The next list is the top causes for wakeups. Compare your list to mine (I only showed the top 3).
All the way at the bottom it will have optimizations that can be made to lower power use. These changes can not be made to the rom itself, they must be made to the kernel. While other roms claim they made changes to the kernel, if they are using the stock kernel (if they aren't over-clockable then they are using the stock kernel) then they didn't. While there is a kernel source available to us, I have chosen to continue using the stock kernel until our official source is released by HTC for stability reasons.
I have chosen to NOT include adless browsing in my rom. I used adless browsing in all of my Hero Android 1.5 roms because it actually blocked ads from the browser. In Android 2.1 this functionality stopped working so I stopped including it. It was pointed out to me that while it doesn't block them in the browser, it does block them in apps (background data). The reason I am choosing to not include this is because as a developer myself, I feel that the authors deserve to get paid for what they do if you want to use their app. If you are choosing to use their free ad-driven application then I don't want to contribute to people blocking those ads and preventing the dev from getting paid.
See the official change log for all previous notes and changes! READ IT. It can answer a lot of questions if you are new to Fresh Evo.
DOWNLOAD: http://geekfor.me/new-release/fresh-evo-053/
RADIO: 1.39.00.05.31 (make sure you are running the newest radio if you are having problems with 4g)
New screen shots:
Older: screen shots:
Thanks to D/\SH at smartphonejunkie.com for the video! This is from the last version of Fresh Evo but he has some nice things to say.
Any plan to get this into ROM Manager? I find that app to be super convenient.
sph33r said:
Any plan to get this into ROM Manager? I find that app to be super convenient.
Click to expand...
Click to collapse
Yup it will be, I was just waiting to release so that the links worked.
Flashing now. The one thing I missed when leaving the Hero was fresh rom's. Thanks Flipz
flipzmode said:
Yup it will be, I was just waiting to release so that the links worked.
Click to expand...
Click to collapse
Awesome! I'm glad to see developers embracing that software.
Can't wait to try it, it sounds great.
Haha mad people must be downloading this your site is having issues establishing a database connection
Nvm seems fine now
Flashed with no problems. My Evo is Fresh!
Thanks Flipz
flipz just made my weekend!
Can we install directly over Fresh 0.1c Beta without a wipe?
Flashing now. Thanks Flipz
TheBiles said:
Can we install directly over Fresh 0.1c Beta without a wipe?
Click to expand...
Click to collapse
Shouldn't be a problem. And yea, the site is getting murdered. I just enabled super cache.
drbgotenks said:
Flashed with no problems. My Evo is Fresh!
Thanks Flipz
Click to expand...
Click to collapse
Hahahaha... I've been dying to say that!!!
Great to see you here flipz!
The beta version was running fine for me but I am excited to see the public version released.
For anyone not familiar with flipzmode's work, just flash this ROM and you'll be a fan!
omg I SO wish my Evo's battery isn't dead right now.
Awesome stuff. Was a huge fan of the hero roms. Now on to bigger and better things
The rom manager wouldn't let me flash. It didn't force close, it just said failed. To fix, I changed the setting in the very bottom panel to an older version, then changed back to the current one and it worked fine.
Flipz,
I love the idea with moving some of them to /data/app... which got me thinking... why not move almost everything there? That way everyone can uninstall whatever they don't like... or at least moving everything you can, over there to allow everything to still work.
Hey Flipz... I noticed that the Hero kitchen worked to push some of the .apk's back to the Evo. But some return an error..and fail.
For example the HTCFMRadio apk;
Can u clarify, when u say: adb shell mount /sdcardadb shell mount /systemadb shellcp /sdcard/fresh-removed-apks/WHATEVERAPP.apk /system/app
Like would "adb shell mount /sdcardadb shell mount /systemadb shellcp /sdcard/fresh-removed-apks/WHATEVERAPP.apk /system/app be all one command line? Or where should that be broken up at? I tried doing adb shell/mount /sdcard and it said "Usage: mount [-r] [-w] [-o options] [-t type] device directory..
drbgotenks said:
The rom manager wouldn't let me flash. It didn't force close, it just said failed. To fix, I changed the setting in the very bottom panel to an older version, then changed back to the current one and it worked fine.
Click to expand...
Click to collapse
Ditto. Did the the fix you suggested, and it's back in action.
Tenny said:
Flipz,
I love the idea with moving some of them to /data/app... which got me thinking... why not move almost everything there? That way everyone can uninstall whatever they don't like... or at least moving everything you can, over there to allow everything to still work.
Click to expand...
Click to collapse
Damn good idea, a second this if it could be done! It would be the most customizable ROM ever!!!!!
I started a new thread for this release because the other one was just too huge. I also want to apologize for how long this release took. Life is crazy.
Geek For Me is proud to release:
Fresh Evo 1.0.1 for your Sprint Evo 4g
NOTE: Fresh Evo now assumes that you have NAND unlocked (part 2 of rooting). This means you are fully rooted and have write access to /system/ even when you are booted up. If you have not unlocked NAND protection then you should do so before flashing this rom!
If you are coming from Fresh Evo 0.5.3 then just as I promised, no wipe is required. However if you are having problems then of course... wipe.
If you are coming from ANY other rom: do a data wipe! This version 100% requires one. This should however be the last wipe required! It has also been reported that Clockwork Recovery is not wiping sd:ext properly. So if you do a data wipe (data, dalvik, cache, and sd:ext) and are still getting FC's or boot loops then you need to flash Amon's recovery and use it instead. In order to flash this rom you need to be rooted (unrevoked method doesn't count as root) to flash this. How To: Root Your Sprint Evo with NAND unlocked. Always make a nandroid backup, I can't be held responsible if something breaks, etc, etc.
Expect 1 loop at the very first boot! This is a side effect of the fixed vanilla lock. The very first time you boot up the phone it will load the lockscreen and then boot loop one time and then come up. If it continues to loop then see above.
Go here to see all reported bugs: http://link.geekfor.me/freshevobugs -- if you are having a problem then check that page first, and read these release notes in their entirety!
Base: RUU_Supersonic_1.47.651.1 -- NEW!
Changes from 0.5.3 to 1.0.1:
Built off of the new 1.47.651.1 base!
Updated apps2sd to DarkTremor 2.7.5-pf4a
Updated Fresh Updater to 1.2
Mostly just visual changes. Turning the "themes" tab in to patches + themes + tweaks tab. More to come on that.
Make sure to Check the How To to setup and use Fresh Updater if you haven't before.
Added back FriendStream and Peep
For the beta versions of 1.0.x I had removed them, but I just found that too many people were having issues related to them not being there, so I've put them back in.
Made new boot.img containing the newest HTC kernel (789bf291)
Updated boot screen thanks to wrx4memp -- the "O" was made solid. While it wasn't wrong in the first place and was the font he used, we agreed it would be better to just make it solid.
Updated Launcher Pro to 0.6.7.2
Updated Rom Manager to 2.0.0.5
Updated Qik to 0.03.54
Check the download links below for an updated radio and wimax image.
If you are currently having problems with 4g then check the wimax.img download page below for links to help. If your 4g worked fine on Fresh 0.5.3 and then stopped working, make sure you are using the newest wimax.img and radio.img, and then do a full wipe and re-flash the rom.
If you are having problems with Google Maps then check the FAQ (linked below)
Click to expand...
Click to collapse
Standard Fresh Evo Features:
Fresh Updater! Check the How To for information on setting it up and using it. Thanks to cyanogen and firefart as it's based on CMUpdater. It is built off of R657 which is the newest commit.
270 degree auto-rotation (you can turn the phone to the right or the left for landscape) -- Thanks to Optedoblivion for pointing me in the right direction
Fully fixed vanilla lock screen -- see screen shots. Use Fresh Updater to grab one of the vanilla patches to enable it. HTC's lock is enabled by default.
Landscape rosie (disabled by default!) -- see screen shots to see the issues with this. It is functional however it is definitely a hack. You will see some issues with using it. It doesn't look pretty, but it does work! Thanks to jschisurf for pointing me in the right direction on this one. NOTE: I have landscape rosie disabled by default! If you want to try it out then grab one of the patches in Fresh Updater to enable it. See the Fresh Updater How To for help with that.
Landscape settings.apk -- no problems here. Works fine.
12 new Rosie widgets. 7 that are available for our phone and 5 that aren't.
Profiles, ringtone, battery, call mom, coin flip, daily challenge, dice, notes, quick record, tasks, tip calculator, and today in history.
These are made by HTC and will only work in Rosie.
Wifi tether (free wireless 3g/4g tether)
Stock files have been resigned. This should prevent the need for any future wipes (not counting any major software changes by HTC/Sprint).
I have still chosen to NOT include adless browsing in my rom. I used adless browsing in all of my Hero Android 1.5 roms because it actually blocked ads from the browser. In Android 2.1 this functionality stopped working so I stopped including it. It was pointed out to me that while it doesn't block them in the browser, it does block them in apps (background data). The reason I am choosing to not include this is because as a developer myself, I feel that the authors deserve to get paid for what they do if you want to use their app. If you are choosing to use their free ad-driven application then I don't want to contribute to people blocking those ads and preventing the dev from getting paid.
All APK's have been png optimized and zipalign'd
png optimize goes through every APK and losslessly compresses the png (picture) files without causing any type of visual change. This provides a smaller apk file size that loads faster. Each APK has then been zipalign'd. From Android's developer page: zipalign is an archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
While this does free up space on /system/ (as seen below) it is not done to make free space considering we have more than enough. It is done purely for a performance gain. Every day use of the phone will go smoother and stock applications will respond faster. The reason this works is because it has reduced the application file size as much as 50%, so they load in to memory faster and run smoother.
Additionally all applications in /data/ (even ones you downloaded) will be zipalign'd on boot if they need to be.
Not every apk takes png optimization + zip align well. I've done it on enough roms that I think I know which ones cause issues now, but if you are getting FC's on any apps (I can't test them all) then let me know and I'll get it resolved. Thanks!
Apps2sd enabled! Using Darktremor by tkirton.
Apps2sd takes all applications from /data/app and /data/app-private and moves them to a partition on your sdcard. It was originally created for phones that didn't enough enough space on /data/ to store a large number of applications. This has mostly been resolved on the Evo because we have over 400mb of space allocated to /data/. However for some people this isn't enough. Additionally if your apps are stored on your sdcard then you can do a data wipe and they will still be there (albeit settings will be lost, but you won't need to reinstall them).
You do not have to use apps2sd if you don't want to use it. If you just don't format your sdcard with an ext partition (leave it all as fat32 like it is from the factory) then apps2sd will stay turned off.
How to setup apps2sd on Fresh Evo and warnings about apps2sd
Battery optimizations
The stock mms.apk was possibly causing a wake lock. I have swapped it for a different one while I do some testing.
Raised VM kernel dirty page writeback frequency to 15 seconds. This wakes the phone up less often for background VM activity. Every single application in Android is technically running in a VM (virtual machine) so that's why this helps (as recommended by lesswatts.org).
Compcache 0.6.2 / Ramzswap enabled -- Thanks to toastcfh for compiling the modules! Compcache creates a RAM based block device (named ramzswap) which acts as swap disk. Pages swapped to this disk are compressed and stored in memory itself. Compressing pages and keeping them in RAM virtually increases its capacity. This allows more applications to fit in given amount of memory. This will only kick in when the stock memory (which the Evo has plenty of) gets low.
I have tuned the default to be 100mb ramzswap size with 40% swappiness
You can check compcache's use by opening an adb shell and typing: rzscontrol /dev/block/ramzswap0 --stats
ES File Explorer
ROM Manager -- Fresh Evo does show up as an available download in the free version of ROM Manager, so you can use it to update Fresh Evo right through your phone if you want.
Launcher Pro
Wifi Tether (free 3g and 4g wireless tethering)
Qik
Facebook moved to /data/ so that it can be uninstalled
Custom boot screen thanks to wrx4memp!
Added PowerTOP 1.11. From LessWatts.org: Programs can make your [phone] use more power. PowerTOP is a Linux tool that helps you find those programs that are misbehaving while your [phone] is idle. -- Compiled by cyanogen.
To run PowerTOP just open an adb shell and type: "powertop -d". It will scan for 15 seconds and then print out a report.
The first section will show you what % of time your phone spent running at what Mhz. In the screen shot above my phone was asleep so it was at 245Mhz the whole time.
The next section shows wakeups-from-idle per second. 50-80 would be normal. If you are in that range then you don't have a problem.
The next list is the top causes for wakeups. Compare your list to mine (I only showed the top 3).
All the way at the bottom it will have optimizations that can be made to lower power use. These changes can not be made to the rom itself, they must be made to the kernel. While other roms claim they made changes to the kernel, if they are using the stock kernel (if they aren't over-clockable then they are using the stock kernel) then they didn't. While there is a kernel source available to us, I have chosen to continue using the stock kernel until our official source is released by HTC for stability reasons.
I have chosen to NOT include adless browsing in my rom. I used adless browsing in all of my Hero Android 1.5 roms because it actually blocked ads from the browser. In Android 2.1 this functionality stopped working so I stopped including it. It was pointed out to me that while it doesn't block them in the browser, it does block them in apps (background data). The reason I am choosing to not include this is because as a developer myself, I feel that the authors deserve to get paid for what they do if you want to use their app. If you are choosing to use their free ad-driven application then I don't want to contribute to people blocking those ads and preventing the dev from getting paid.
See the official change log for all previous notes and changes! READ IT. It can answer a lot of questions if you are new to Fresh Evo.
Check the Fresh Evo FAQ here before you ask questions!
Fresh Evo FAQ: http://geekfor.me/faq/faq-fresh-evo/
Fresh Evo Reported Bugs: http://link.geekfor.me/freshevobugs
Fresh Evo Official Change Log: http://geekfor.me/evo/21/fresh-evo-official-change-log/
DOWNLOAD: http://geekfor.me/new-release/fresh-evo-101/
RADIO: 2.05.00.06.10 (make sure you are running the newest radio)
WiMax Radio: 25641
You must use the new WiMax radio with this rom. First flash the rom, and then the new WiMax radio. Read the release notes with the radio. This will NOT fix your phone if you are having problems with 4g. If you have been a Fresh user all along and haven't flashed any radios and stuff that weren't from me then this will work perfectly for you. If you do have any issues then just do a full data wipe and then reflash the rom. But if your 4g is already broken then follow the link in the release notes for the WiMax radio to get that fixed.
Click to expand...
Click to collapse
New screen shots:
Older: screen shots:
Reserved for once.
I'm gonna test this right now. ;D
Will this be on Rom manager?
downloading and testing now, im excited
I have the Rom manager with the clockworkmod recovery and I keep tryin to flash the recovery RA through the terminal from the market because I'm not to familiar with fastboot. I'm tryin to use the fresh update but it won't work with clockwork recovery. Can someone please help???
Currently downloading via Fresh Updater..
Love your roms Fresh keep up the good work
What he said - thanks man, we really appreciate it!
Issues With Wireless Tether...
Whenever I click the giant green wifi button the app force closes, anyone else experiencing this?
Flipz..... you've outdone yourself man.
This rom is super fast and stable... thanks again for the hard work....
smonme said:
Issues With Wireless Tether...
Whenever I click the giant green wifi button the app force closes, anyone else experiencing this?
Click to expand...
Click to collapse
you will need to remove it, then reinstall it.
dadoc04 said:
you will need to remove it, then reinstall it.
Click to expand...
Click to collapse
could you link me to the apk for reinstall?
smonme said:
Issues With Wireless Tether...
Whenever I click the giant green wifi button the app force closes, anyone else experiencing this?
Click to expand...
Click to collapse
I have had this a couple times on different builds. Go to applications, remove the wireless tether, go here h**p://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_5-pre2.apk&can=2&q= from your phone and it will reinstall, this has always fixed my issues with force close. You must uninstall first though.
Well that sucks... this rom has been in testing for a week and not a single person mentioned the wireless tether FC. haha. I'm sorry guys.
flipzmode said:
Well that sucks... this rom has been in testing for a week and not a single person mentioned the wireless tether FC. haha. I'm sorry guys.
Click to expand...
Click to collapse
mine wireless tether hasnt FC at all...
Tapatalk has tho... but it seems random. Im using the latest 1.69
Ive only seen it happen twice though.
Perfect!!!!!! On the Tether issue, reload binairies (sp) fixed my just fine.
Jetdr said:
Perfect!!!!!! On the Tether issue, reload binairies (sp) fixed my just fine.
Click to expand...
Click to collapse
For us noobs, how do we reload binaries? Getting fc issue too.
Also, I thought Peep was removed by default (again, I could be mistaken).
Just want to clarify one thing. Do we need to wipe the device if upgrading from Fresh 0.5.3?
In the release notes there you say you have to wipe first, which I did, and stated you wouldn't have to wipe again. Now this has the exact same statement in it. Just want to make sure I do the right thing.
Oh yeah, great ROMs. This is my first Android phone and you make it so much better.
Vivix729 said:
For us noobs, how do we reload binaries? Getting fc issue too.
Also, I thought Peep was removed by default (again, I could be mistaken).
Click to expand...
Click to collapse
Noob version :
Use a program like Uninstaller or Titanium Backup to uninstall Wireless Tether.
Search Market for Wireless Tether for root users. Install. Done.
Crackbone said:
Noob version :
Use a program like Uninstaller or Titanium Backup to uninstall Wireless Tether.
Search Market for Wireless Tether for root users. Install. Done.
Click to expand...
Click to collapse
Oh, so it's literally "reinstall". I thought there was some fancy adb command or something
And...First post on XDA.
I'm looking into the steps necessary to remove the non-vital T-Mobile / LG apps from this phone if for no other reason than to free up system resources. I've done quite a bit of reading on how the Android OS handles memory, etc and this shouldn't be a terribly difficult process, But this phone is my lifeline and I can't screw this up! (Read: I can't afford a bricked device)
Looking within XDA itself, I came across several "help, I've screwed this up" threads and one Development thread, but unfortunately those are all assuming that you are going to actually mod the device, not root/remove/unroot the device as I'm suggesting. A search online gave me a couple resources into things like 'Safe' files to remove, an intro into the ADB, and two different methods to root the device. Others yet have suggested using things like Titanium Root for backing up the device on a 'just in case' level of thinking.
Here's the series of steps that I'm pretty sure I'm looking to stick to.
1) Gather info/tools;
2) Backup phone (Read: User is smart and does his own data archive for essential data);
3) Master Reset phone;
4) TempRoot phone;
5) Create a flashable copy of the factory ROM (for when I get around to upgrading);
6) Remove bloatware and create a copy of modified ROM;
7) Unroot and enjoy more resources;
During the 'Remove Bloatware' process I'd be removing as much as safely possible, but nothing that'll compromise the functionality of the phone. As much as I really don't use the Genius function, I can see how removing that might somehow break the Home UI. I would go as far as removing things like FB, Twitter, etc because I can always download a newer version of them and save a few kb/mb of space on the system partition in the process. If after all of this I become comfortable enough In this, then I'll consider doing the same for mom's Exhibit 2. I'd kill to have her battery life though. >.<
Phone Stats: As reported by SystemPanel Lite
Build ID: GRK39F
Model: e739
Host: Ubuntu
Type: gichul.yoo
User: user
Version: V10u-Jan23-2013.2EDE7D073
Release: 2.3.6
SDK: 10
Kernel: Linux version 2.6.35.7-perf([email protected])(gcc version 4.4.3(GCC)) #3 PREEMPT Wed Jan 23 15:07:10 KST 2013
I've asked TMO and they say that this device will more than likely not be receiving any future OTA updates so I shouldn't have to be concerned with that. Warranty is not a concern, but not having a device is. This thing keeps me on task for many things in life and that's key for my lifestyle and medical limitations. This is my second smart phone so I'm comfortable with interacting with the system recovery screens, etc so long as I know the process being followed is accurate. Lastly, if there are any specific apps that would help in this process, then please let me know. If needed I can provide a list of currently used apps that relate to system maintenance, etc.
Greetings,
I am currently working on a 100% Android Marshmallow v6.0.1 variant for the Samsung On5 SM-G550T/1 (T-Mobile).
THIS IS NOT A THREAD ON HOW TO ROOT YOUR PHONE
This thread assumes you have already rooted and installed TWRP on your phone and have basic understanding on to backup and recover your phone.
If you need that sort of help, please see my other thread:
https://goo.gl/jWNVNX
Reasons for Project:
I started this project for two reasons:
- Frustration for the lack of support for an otherwise great phone.
- Stumbling across the Samsung Factory Test Rom doing research for other projects.
This ROM has a a 100% Native Driver Set for Android v6.0.1 on the SM-G550T/1. The driver set is identical for the TMO or MetroPCS variants, but the EFS folder will remain different for each.
I'm going to outright confess that I am not a programmer and this is truthfully the first ROM I am trying to develop on my own. I'm a Project Manager and Software Designer by trade, but I rarely get this deep into ROM developments. I figured it was a good project to take on to learn the nitty griddy of what a truly pure Android Experience looks like. That being said, I'd greatly appreciate any help anyone can contribute and will make all my work freely available to anyone wanting to help provided that everyone participating goes into it with good faith that they have no intent on making substantial gains from this project.
Usage of these ROMs/Files/Programs are subject to the following licenses:
- Google's Android Open Source Project Licnese (AOSP):
https://source.android.com/setup/start/licenses
- Google's Individual Contributor License Agreement:
https://cla.developers.google.com/about/google-individual
- Apache Software License, Version 2.0
http://www.apache.org/licenses/LICENSE-2.0
- Samsung Open Source Release Center (OSRC) License:
http://opensource.samsung.com/reception/
That being said, I believe this remains a good enough device, IMHO, to transition people into Android or to provide to people not requiring a fully featured phone.
KNOX Status:
The Factory Test ROM is mostly clean having all the drivers intact and lacks most Samsung Bloatware "tampering". It *DOES* have some preliminary containers for KNOX installed, but none of it is active and takes up less then 1 MB of total space after cleaning passes to remove as many traces as could be removed without breaking things. It is currently being "managed" by an init.d script that generates the folders. I haven't been able to track down yet.
Known Issues:
- 100% Pure Android Menus.
- Rooted/Super User.
- Sound, Camera, GPS, TMO Modem, Wifi, Bluetooth 100% working.
- 100% Native Tethering.
- Adblocker pre-installed (for both Apps and Websites).
- The smallest amount of KNOX installations outside of Lineage. >1mb of KNOX is present with the only items being present are installer containers.
- I'm trying to track down Init.d files that loads with Android and automatically disables/flushes WIFI.
- By default, the power button is set a 100ms push time to turn off (not show power menu). I'm trying to figure out a work around for this.
- I'm trying to find a compatible Contacts Storage file.
- There is no shutdown menu.
Please note that any released versions of this ROM will have makeshift ways to get around these issues.
Downloads:
Please see the second post in this thread.
How to Install:
#01.) Backup your device.
#02.) Download the zip file for the TWRP backup.
#03.) Unzip the TWRP backup.
#04.) Load the downloaded restore into your TWRP Backup Directory.
#05.) Boot into TWRP Recovery.
#06.) Restore the ROM copied into your TWRP Backup Directory.
#07.) Reboot.
Note: No personal data has been configured.
References:
Update Log:
https://goo.gl/CEGCx9|
Required System Apps for Samsung Phones:
https://goo.gl/emTvgX
Things I Could Use Help On:
- A very good way to figure out what Init.d files are doing what without reading through them.
- A good way to change the PIT so we can move 2 gig from the System Rom into the User Rom space.
- Easy methods for changing key button presses.
- A shutdown menu setup.
- A way to make this into an installer.
Note that all those things I'm working on ALREADY, but suggestions would be helpful.
Thanks in advance for any help anyone offers.
Donations Welcomed:
Dev elopement of this ROM is timely, I appreciate any contributions you wish to provide.
https://goo.gl/esVVqA
DOWNLOAD LINKS:
[2019-03-11] Android (v6.0.1) Build #13 [RC] - Google
https://www.androidfilehost.com/?fid=1395089523397913770
- Note, due to Google Now being installed on this one, I can't configure the home long press as the restart menu.
[2019-03-11] Android (v6.0.1) Build #13 [RC] - Diagnostics
https://www.androidfilehost.com/?fid=1395089523397913771
[2019-03-02] Android [v6.0.0] Build #10F [RC]
https://www.androidfilehost.com/?fid=1395089523397908668
i would love to test this rom
Its been taking a little longer then I expected to get it working correctly --- I've been having trouble tracking down some bugs, but with a little luck, I'll post the Google variant tomorrow.
Here is a "working" version to look at:
https://www.androidfilehost.com/?fid=1395089523397901430
It's a restore for TWRP (not an install).
It has all the aforementioned bugs, but is pretty clean only with a few basic utilities installed on it.
I'm trying to track down a number of things:
How to change the Power Button function:
In my most current build, I have made the power button simply put the device to sleep with a long hold of the home button bringing up the power menu. I can't for the life of me figure out where the power button menu lives at or how to define it.
Normally, you'd go edit /system/usr/keylayout/Generic.kl, however, editing it button 116 (the power button) for "Power" only makes it turn off. I can remap it easily as sleep. I compared several other ROMs who use the exact same parameter.
My current version, I just use an app to remap several of those functions; but I don't feel like that's a "release worthy" fix.
Factory Mode:
I can't figure out how to get this version of the ROM to get out of factory mode. The only real problem this causes is, on bootup, it will display a message saying as such and then disable WIFI and turn off the sound. Both, of which, can be immediately be turned back on. It also disables power saver modes.
At first, I thought this was an Init.d file, but after doing some digging I determined this has to the /efs/factoryapp/factorymode file. I may need to swap elements from another EFS to get this fixed.
Contacts Storage:
This is another one I can't seem to track down, but I have a working idea how to fix it. At current, anything that uses Contact Storage won't work. I wonder if the contact storage I have on the system is simply incompatible for some reason. I'm going to try to pull over those system apps from another working rom.
Storage
I've mapped out all the partitions but am having trouble figuring out how to actually change the partitions. There is a whole 2 GB being wasted on the system partition. I'm actually very surprised that no one has ever released a rom with this fixed.
I've tried using parted, but my ADB Install is messed up something major and I cant track down that problem. Reinstalled ADB hasn't fixed it. Its largely a PC problem on my end; a problem I'm dragging my feat going and trying to fix. This is an issue I REALLY wish I could use PC tools for :-\. I've done these changes a thousand times on Windows based machines, but never on a Linux based OS.
Now that I think about it, maybe I should try doing this from the terminal prompt in TWRP. I just wish the keyboard in TWRP didn't suck :-\.
Other Thoughts:
Beyond those very vexing bugs, I have to honestly say that I feel like this experience on this rom is vastly superior to that of the stock Samsung Experience. Sure, these issues are vexing, but I'm also seeing much less system overhead (CPU usage, RAM usage) with this Rom then anything else outside of Lineage.
Update
Here's an update for everyone who might be interested:
The last couple of week's I spent an ENORMOUS amount of time trying to track down as much as I can to get this ROM to work as intended.
For those interested, I've developed a completely new spreadsheet describing everything that's bloatware versus needed items:
https://goo.gl/emTvgX
This spreadsheet will probably be handy for EVERYONE working on Samsung related devices. When its a little more clean, I'll throw it some place better; but since this is specific towards this device, I'll keep it here for now.
It describes everything in /system/app/ and /system/priv-app/ in Samsung's default install and which of those items are actually needed for a 100% clean Android Experience.
I've also rolled through the architecture and have cleaned a lot of "junk" out of the system. Overall, I've pulled it the system from around 1.3 gb installed all the way down to about 800 mb and still feel confident I can trim more out of it.
I've also made it a point to install as much updated system apps as possible. Its been a game of juggling Google, Samsung and other ROM apps to find what works. In general, there are only one major programs left that are Samsung based in any way and that's the Samsung Phone Service app; which seems like its required to interface with the specific hardware on the phone. I've tracked down a number of native Google teleservice.apk-s and none have worked to date.
I am, sadly, still having the aforementioned problems:
- Contacts won't sync despite being able to connect to the contact services and seeing what backups are available. Manual restores work and updating contacts TO the server works now.
- The Power Button turns off the device immediately. The problem resides in a configuration somewhere that's telling the "Power" function to not bring up the power menu. The power menu is in the system, but appears to be renamed or something. I'm having trouble tracking this down. For documentation sake, in theory you should be able to just go to /system/usr/keylayout/General.kl and edit button 116, but that doesn't work.
- The phone is still locked into "Factory Mode". Various documentation says that if you go to /efs/FactoryData/factorymode and edit the contents to "ON", it should resolve this issue, but it doesn't. I feel that the problem resides in the CSC folder and EFS folder, but I haven't gotten around to testing yet. I suspect if you swap the CSC and EFS folders out and set all the correct permissions it might fix that. As it stands now, however, its only a minor inconvenience.
Overall, there's a lot more junk to sift through on the last two problems. The first problem I am kind of stumped on.
If you want to download the ROM and look at it or run it, you can follow the below link. It's currently setup with my "trouble shooting environment" making key places to tinker with easily accessible.
DOWNLOAD HERE:
https://goo.gl/MuPqE3
@LighthammerX
Im very grateful for this site where we can come and learn from one another. I just wanted to say thanks for taking time to work on this device and then sharing your findings. I've been using my on5 for 2 months now after other device died. I'm in the process of moving now but once I'm done with that I'm going to scope out this bad boy and see if I can figure out a few things. Appreciate you sharing your information with us all. Cheers.
Sent from my on5ltemtr using XDA Labs
Thanks. I'm glad to see there's some interest here. IMHO, with the right setup, this little phone is actually a very nice device today.
I actually took a lot of what I learned from hack this ROM apart and applied it to Super Starz to get it running a lot cleaning as my daily runner until/if I get these few bugs figured out.
Personally, I think the most valuable thing I've been learning is just how bloated Samsung Devices truly are out of the box.
I'm going to go ahead and dump my progress log here too so you guys can see what I've been toiling with in hopes someone has some specific feedback on issues and if I am in the right place or not:
https://goo.gl/CEGCx9
As of the writing of this post, I'm virtually confident any problems I am experiencing has nothing to do with /efs/ or /system/csc/.
I've found some inconsistencies in /etc/ and in a few other directories in /system/.
I still wonder if there isn't a init.d file I haven't tracked down yet, but personally I find folder compares faster and easier to try to normalize then I do init.d files.
When it comes to folder compares, I can do a fast reboot and see if things break. When it comes to lines of code, I have to do a bulk of edits, reboot and hope for the best.
Just as an FYI, I plan on completely rewriting the OP when things are at a place where things work.
For anyone following the thread, the Downloads Section has been updated.
This seems really interesting ? I've been trying to find a good ROM for a while with little success, so hopefully this might be the one. I just have one question: what are the differences between the Google and Diagnostics versions of this ROM?