Related
Version 5.x of xtrROM builds on the heritage and continues the evolution of this fast reliable feature rich ROM that you as the user can customize to enhance your Droid Eris Android experience! This ROM has a very Vanilla feel but is based on the core HTC framework to offer the best relibility possible in a custom ROM. I am reliant on my phone at work so stability and consistent quality of user experience are the top priorities for xtrROM. If you like the HTC Sense experience then be sure to check out xtrSENSE and if you would like a "pure" Vanilla 2.1 AOSP experience then be sure to try VanillaASOP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Base xtrROM Features:
All the goodness of Android 2.1 with Root access and Superuser permissions
A very Android ASOP Vanilla feel from removing HTC "bloat"; while embracing reliable HTC sync and app coordination
Fully odex to save as much "usable" internal space as possible and provide faster boot times
Over clock support - default to 710400
Many reliable "hacked" tweaks such as: Collin_ph battery tweak, some Flash support, OpenGLES 1.1, new Android Market, wired tether, etc...
Included opensource GScript app allows you to easily turn on/off core ROM settings (CPU OC, Apps2sd, Cache2sd, JIT, etc...) with one-click
Live wallpapers as a separate module you can enable
Full Cache2cache support (see details below) - better use of the /data/ and /cache/ file blocks which opens up unused internal storage allowing you to install close to 100 apps without using Apps2sd!
Apps2sd support (see instructions below)
Customized theme including wallpapers, phone dialer, keyboard, bootanimation, and other small touches...
Lean and very crisp running ROM - it almost "feels" lighter in your hand!
Designed to be a stable everyday ROM
Check out the change log to see the full evolution and details
Credits and General Public License (GPL):
HTC kernel source: http://member.america.htc.com/download/RomCode/Source_and_Binaries/desirec_2.6.29_8a03cb9a.tar.bz2
Zanfur OC kernel support – source: http://forum.xda-developers.com/showthread.php?t=679102
GScripts source: http://code.google.com/p/gscript-android/source/checkout
Wired tether source: http://code.google.com/p/android-wired-tether/source/checkout
Built from the July Verizon 2.37.605.4 Eris code base
bertoch for hosting and helping me understand Linux
dsixda for his time saving kitchen – source: http://forum.xda-developers.com/showthread.php?t=633246
gr0gmint on how to make jit (mostly) work with HTC ROMs – source: http://forum.xda-developers.com/showthread.php?t=684535
ChainsDD for Superuser – source: http://forum.xda-developers.com/showthread.php?t=682828
vash8806 for Flash 10 source: http://forum.xda-developers.com/showpost.php?p=7316925&postcount=46
synaptyc for custom boot animation - source:http://forum.xda-developers.com/showthread.php?t=768513
rogro82 for starting GScript - source: http://forum.xda-developers.com/showthread.php?t=486486
nfinitefx45 from the Hero CDMA forum on his companion work with cache2cache
thenestor on help with the DroidXIME keyboard
firestrife23 for helping me understand permission issues with the init.d process
Damageless and TrevE for a model on how to do apps2sd (originally based on tkirton's Darktremor A2SD work) and other boot settings
t2noob on the July patch
Collin_ph for the battery tweak code – source: http://forum.xda-developers.com/showthread.php?t=737352
dearmasfamily for OpenGLES1.1 - source: http://forum.xda-developers.com/showthread.php?t=915058
xda member beta testers (you ROCK)
other xda members for tips and tricks
Download xtrROM5.0.1: http://zach.xtr.i6ix.com/xtrROM5.0.1.zip
MD5 checksum:1e5482eb3fc8486182151c5fad01a253
Default ROM Configuration:
You do not need to run any scripts unless you would like to change the following default configuration:
Live Wallpapers: Not supported (you must run GSript to enable)
dalvik.vm.heapsize: 24m
min free memory values: "balanced" (1536,2048,4096,10240,12800,38400)
CPU Overclocked: Min-245760 Max-710400
CPU Governor: Ondemand
Just In Time Compiler (JIT): Off
Cache Location: Cache2cache On
Apps2sd: Off
User service and battery tweak: Off
Thanks to Canop you can flash other Kernel options from the links below:
BFS - http://forum.xda-developers.com/showthread.php?t=772053
CFS - http://forum.xda-developers.com/showthread.php?t=774211
Get older versions of xtrROM in the change log
OPTIONS AND CONTROLS:
Stock Battery Icon
If you prefer the stock battery icon over the circle battery then flash the below zip.
Make sure to wipe dalvik-cache AFTER flashing this zip
Stock battary Icon: http://zach.xtr.i6ix.com/xtrStockBattery.zip
Live Wallpapers
Live Wallpapers is a feature you can enable for this ROM. I have included my favorite for you to try and you can get others from the Market. Many of the live wallpapers from the market DO NOT function well on our Eris or do not "stick" after reboot, our hardware is underpowered for most and I also find them to be a battery drain. That said I still run a few at times because they are just COOL !
To enable live wallpaper functionality just run the appropriate GScript.
Android ASOP Keyboard and Themed Dialer
This ROM uses a custom themed Android ASOP keyboard as the default keyboard and I have themed the phone dialer to match. If you prefer the standard HTC style keyboard check out jonasl HTC_IME mod keyboard – source: http://forum.xda-developers.com/showthread.php?t=624416. Or if you would like the stock setup download and flash the below .zip file.
Stock keyboard and dialer: http://zach.xtr.i6ix.com/xtrStockKeys.zip
LOOKS LIKE THIS DOES NOT WORK FOR XTRROM5.0 ONLY OLDER VERSIONS - I'LL UPDATE SOON FOR XTRROM5.0...
Clear HTC Lockscreen
It is my personal favorite and since I make the ROM I get to pick . To update the lockscreen go to the Photos app - select the photo you want - select the Set as option - and then select lockscreen.
To get back to the clear lockscreen just run the set_lockscreen_clear.sh GScript and reboot your phone.
GScript
I have compiled and incorporated the opensource GScript app to load and one-click run user settings.
To setup your GScripts complete the following steps:
1. After opening GScript press the menu button and select "Add script"
2. A new window will open.
3. Press the Load file button
4. Select a script from the list (each is obviously named as to its function)
5. Ensure Needs SU? is checked
6. Now select "Save" and you have added your script
7. To run just select it from the list in the main GScript screen
8. Some scripts may prompt you to reboot the phone for the change to take effect.
There are a lot of scripts but remember your phone has been setup great by default with this ROM and if you do not understand the function or purpose of a GScript then best to not save and run it . One can always search this forum and ask others about all the fun things you can now do with your phone! I will look to add a list of each GScript and its function as time allows...
Wired Tether
For wired tether to work you must make sure that your computer has the appropriate RNDIS drivers. Learn how to do this at the android-wired-tether Wiki.
Per roirraW "edor" ehT:
The wiki incorrectly states, or implies, that Windows 7 includes the RNDIS support. Or at least, they imply that Windows 7 includes the RNDIS driver necessary. I can confirm that neither Windows 7 x86 or x64 works with tethering out of the box. The instructions for XP users are correct and also work for Windows 7. Just download HTCSync for your device (Eris) and install it, and it'll install the correct driver.
Flash Support
A hacked version of Flash 10.1.123 is baked into this ROM however it has proven to be hit and miss and preforms more like a flash "lite"... Full flash sites such as Halo do not work however many others do; they may just take a while as the Eris is not a powerful phone
Performance Improvements:
Free Internal Memory and Dalvik-cache heapsize - I have update default user settings to allow a larger dalvik heapsize of 24mb (think more space for apps to play) AND optimized how memory is freed up using Androids internal task killer.
Default min memory free: “balanced” (1536, 2048, 4096, 10240, 12800, 38400)
Default dalvik vm heapsize: 24m (48m with JIT on)
To change dalvik vm heapsize or min memory free settings you can just run the appropriate GScript.
If you would like to further modify the default min memory free settings then download Autokiller or MinFreeManager, these apps will allow you to set and monitor the min memory free values. For more information on Androids “internal task killer” and min memory free values go here.
default Overclock Settings - the ROMs kernel supports overclocking and as part of the custom sysinit process I have added scripts that automatically set the below CPU clock settings when the phone boots:
Min: 245760
Max: 710400
I have included a few GScripts to change between stock cpu settings and default overclock settings without using a market app . You can also run the report_cpu_freq script from GScript to get a printout of which frequencies and time in each you phone has been operating.
To change CPU overclock settings just run the appropriate GScript.
If you would like to further modify OC settings then download SetCPU or Overclock Widget, these apps will allow you to set and monitor the CPU speed. Remember YOU CAN DAMAGE YOUR CPU IF RUN TO HOT FOR TO LONG with higher settings. MAKE SURE TO RUN THE set_cpu_stock GSCRIPT IF YOU INSTALL A MARKET APP. The internal overclock support may overwrite the market app settings...
JIT - JIT (Just In Time compiler) is a built in option for the ROM but is off by default. For a detailed overview of JIT go here. PLEASE NOTE for Android 2.1 JIT is not stable with all applications and can cause odd things on your phone.
To enable/disable JIT just run the appropriate GScript and reboot your phone.
User Services Power Management (Collin_ph Battery Tweak) - I have built in a user services that runs at a polled interval and can set the performance settings of your phone in realtime. The first script that is available is a 2.1 HTC framework version of the Collin_ph Batter Tweak. For a detailed overview of you can view the original thread at here.
The power management battery tweak is disabled by default but there is a gscript to enable plus you can run "battconf" from terminal on the phone or adb shell to configure... The battery tweak runs a script every 60 (or less if you are on power) to poll the capacity of the battery, and as the battery goes down the cpu max freq is progressively lowered. It also changes the CPU write characteristics (all of which I do not yet fully understand). You can see all the details in the /system/bin/batter_tweak file.
I take no real credit on this and just ported the concept to the HTC framework and HTC kernel (with the zanfur OC patch). This took a lot of work and I fixed a few bugs but the concept is not mine and all Collin_ph.
When you first run terminal remember to type "su" (or equivilent for your app) to run as root and select "1" then enter when first prompted after starting "battconf".
So how do I know it is working? just run the report_log.sh GScript and you will see when it logs a change to the system settings. Also you can run the report_system_settings.sh GScript and for a display of current settings. This process will be faster if you plug into a power source and wait about 60 seconds
To enable/disable the battery tweak just run the appropriate GScript (user_service_batterytweak_enable.sh or user_service_batterytweak_disable.sh) and reboot your phone.
Cache Location (Cache2cache):
By default, the dalvik-cache has been relocated from the internal /data/dalvik-cache/ directory to the internal /cache/dalvik-cache directory. The Eris comes with an internal /cache/ file block of 130mb that is not used! After reviewing a number of xda member file system usage reports (thanks xtrROM and xtrSENSE users!) the MOST reported use of this space was 5%... So by moving the dalvik-cache to this free area you now have over 150mb on internal /data/ for apps and over 75mb in internal /cache/ for dalvik-cache. This means that you can probably install close to 100 apps WITHOUT having to partition and move anything to the SD Card ext!
You can also move the dalvik-cache to your sd card ext or back to the stock internal /data/ file block.
To change the dalvik-cache location just run the appropriate GScript and reboot your phone.
So why does my Settings>SD card & phone storage>Internal phone storage only show 150mb or less? This is because this number ONLY reflects the /data/ file block on your phone and does not "see" the /cache/ block that is now being used for dalvik-cache storage. You can run the GScript report_system_settings script to see amount available in /cache/.
Apps2sd and Cache2sd:
I have revamped my implementation of apps2sd to use simpler and better organized scripts. For apps2sd to work you must first complete the listed prerequisites and it is a good idea to read through the "things you may want to know about apps2sd" section. Although it can provide gobs of space for apps, Apps2sd is not for everyone as it ties the stability of your phone to your SD card... If you do not need the space I would recommend that you keep the default of DISABLED; if you want to try you can always disable it again however there is always the chance of issues.
To enable/disable apps2sd and cache2sd just run the appropriate GScript and reboot your phone.
Prerequisites
If you have not setup your SD card (for those new to Apps2sd) as per tkirton:
BACKUP YOUR SD CARD TO YOUR COMPUTER. Can't stress this enough, as partitioning will wipe the entire card.
Reboot into recovery
In Android System Recovery, select Partition sdcard
In the Partition sdcard menu, select Partition SD
Follow the instructions on the phone to partition your SD card. Most folks seem to recommend using the default values however you can go larger or smaller use values 256, 512,768,1024. You will also be asked to set a swap size; I stayed at 32mb (anticipate future ROM options to allow moving swap to sd)
Once the partition is initially created you must then convert to ext3 - In the Partition sdcard menu, select SD:ext2 to ext3. Follow the instructions on the screen.
Press the back button on the phone to go back to the main menu.
Your SD card is now ready to work with an Apps2sd supported ROM.
Things you may want to know about apps2sd
Bootloop protection is built in if your SD card is corrupted or is removed from the phone with Apps2sd enabled. Your apps will go away but your phone will boot .
There are 3 subsets of data associated to an app when it is installed and run on your phone.
1) /data/app/ (and /data/app-private) - actual .apk files we think of as the applications that are not system apps (i.e. installed on /system/app)
2) /data/data/ - the files produced by ALL apps (system apps and market apps) during installation that are used by the Android system to run the app
3)/data/dalvik-cache/ - app cache file and work space for ALL apps (system apps and market apps).
From root explorer (or similar) you can browse to the /data/app OR the /system/sd/app folders and you will see the same thing, both will tell you how much space you have used and have left. The way apps2sd works is by "linking" the /system/sd/app to the /data/app folder so that the Android system thinks it is accessing the /data/app it is really at /system/sd/app.
I have seen using Apps2sd cause issues with some.zip flash updates as they try to write directly to the /data/app folder which no longer "physically" exists
If you get into a bootloop issue using apps2sd boot into amon_ra recovery and try one of the follow:
1) from the Other menu option select the Fix apk uid mismatches
2) from the Wipe menu option complete a)Wipe data/factory reset b)Wipe Dalvik-cache c)Wipe SD:ext partition
Apps2sd and Cache2sd Basics
When you run the apps2sd or cache2sd script, upon reboot, it will move ALL your existing apps or cache to the sd card ext partition and ALL future apps and cache will be installed and stored on the sd card ext partition.
Running the apps2internal or cache2internal script, upon reboot, it will move ALL your existing apps or cache to the /data block of internal storage and ALL futures apps and cache will be stored in internal storage.
With HTC based ROMs it is all or nothing and you cannot move individual apps like in the CyanogenMod ROMs.
So how do I know Apps2sd is on? - You can run the GScript report_system_stats which will give you a printout of what fileblocks are used as well as a “true/false” value for Apps2sd On. You can also go to menu>Settings>Sd card and phone storage - when on space available under Available storage will go down at a VERY slow rate when new apps are installed.
TO INSTALL:
YOU MUST HAVE A ROOTED PHONE
download the xtrROM .zip file
complete NANDROID backup
copy the .zip file to the root of your sd card
From Wipe data/factory reset, Wipe Dalvik-cache, and Wipe SD:ext partition (folks coming from previous versions may try no wipe updates but a full wipe is always "cleanest")
flash the xtrROM file from sd card
reboot (first boot may take around 10 minutes)
complete short setup and let your accounts sync
you can save and run GScripts to personalize settings at any time
Available Market Apps You May Want to Add:
Widgetsoid - provides the CyanogenMod style customizable power widget that can be put in the notificaton bar
Root Explorer
Launcher Pro
Tips
For an even faster feel turn off window animations under Settings>Sound & Display>Animaiton.
To update the lockscreen goto the Photos app select the photo you want and select the Set as option and then select lockscreen.
Random FC - Lower your overclock settings or turn off JIT. Our little Eris's can only do so much and not all hardware is equal... Also remember this ROM is quite fast in stock form and higher Linpack scores DO NOT make for a better user experience
Google contact sync issus? check out the following fix http://forum.xda-developers.com/showpost.php?p=6796805&postcount=102. I think this is not uncommon coming from 2.2 Froyo ROMs as they seem to sync with Google a little differently and I do not think the folks at HTC or Google built their systems with the thought that users would be jumping back and forth between versions as much as we all do...
Slow facebook sync? per erishasnobattery: log into your facebook account on your computer - Click Account>Application Settings>under Authorized - remove listing for HTC Sense.
To turn on vibration with keypress for the keyboard long hold the ?123 button in the bottom left and select Android keyboard settings>Vibrate on keypress
If you have 50% time without signal under Settings>About Phone>Battery>Cell Standby complete the "airplane trick" by turning Airplane mode on wait just a few seconds and then Airplane mode off (search the forum for "time without a signal")
If you are syncing facebook then you may want to remember to check the "View contacts" for facebook from the People app Menu>View setting
Turn off notifications for Superuser from the Settings tab of the app
Known Issues
Messaging sometimes FC when send and IMMEDIATE rotate from portrait to landscape. The message still sends and the app stays open there is just an annoying FC on the screen...
Flash does not work for some sites, Halo for example.
The keyboard does not have an updateable user dictionary
Verizon NFL does not work with JIT on
CHANGE LOG:
Click here to view the full change log
Sweet! Thanks! Going to flash when I get home. Is OTA disabled?
USE AT YOUR OWN RISK - settings above 710400 have been reported unstable on some Eris's and YOU CAN DAMAGE YOUR CPU IF RUN TO HOT FOR TO LONG with higher settings.
Weird....I've been running mine on 768000 for the longest time now with no problems what so ever.
kenshincbb said:
USE AT YOUR OWN RISK - settings above 710400 have been reported unstable on some Eris's and YOU CAN DAMAGE YOUR CPU IF RUN TO HOT FOR TO LONG with higher settings.
Weird....I've been running mine on 768000 for the longest time now with no problems what so ever.
Click to expand...
Click to collapse
And I run at 806 but he is saying this for the majority of ppl. So if they DO damage their phone, they dont blame him.
always good to have more options ...i will check it out
rvpartsguy said:
always good to have more options ...i will check it out
Click to expand...
Click to collapse
You really try everything dude. It's a very nice thing to do.
Anyone try it with JIT yet?
Wondering if wired tethering would be included in a later release? Seems to work somewhat faster than wireless for me.
Spencer_Moore said:
You really try everything dude. It's a very nice thing to do.
Click to expand...
Click to collapse
I've been lurking for quite a while, just recently started posting on xda. Pretty sure I've tried all of the ROMs too.
Just got this one downloaded, about to flash it and see how it goes. Won't have to worry about A2SD with over 140mb of internal memory. Outstanding!
Nice Job
Just got XTR setup and it is very responsive. If battery life is decent then I will definitely use this everyday! Excellent effort and I commend you on your opening page. Very clear and consise!
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
Wondering if wired tethering would be included in a later release?
Click to expand...
Click to collapse
Thanks for the feedback. I will add wired tethering to the StockApps.zip flash and re post tonight or tomorrow.
-------------------------------------
Sent via the XDA Tapatalk App
Jit Failure for me.
My first try with jit on this rom locked up. Maybe too much sense left. But you know what, this rom is plenty fast without it.
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
Sweet! Thanks! Going to flash when I get home. Is OTA disabled?
Click to expand...
Click to collapse
OTA is disabled.
-------------------------------------
Sent via the XDA Tapatalk App
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
My first try with jit on this rom locked up. Maybe too much sense left. But you know what, this rom is plenty fast without it.
Click to expand...
Click to collapse
Thanks for trying it out and the feedback! This ROM still runs on the core HTC framework and during my testing with jit could not get it stable enough for a daily ROM.
-------------------------------------
Sent via the XDA Tapatalk App
The widgets are broken apparently. I installed Advance Task Killer and everytime I click on it, it'll vibrate and that's it. OC widget isn't working either. Any ideas?
[EDIT] Oh, reboot was needed. Disregard.
Advanced task killer is not needed. The autokiller app does a much better job. Get rid of atk.
-------------------------------------
Sent via the XDA Tapatalk App
Great running ROM. No troubles yet. Thanks.
I'm running Launcher Pro Beta instead of Sense UI. JIT works GREAT. Getting 5.3mflops @ 806mhz. 5.1mflops @ 768mhz. This thing is FAST!!
I noticed you said this has LWP, so I'm assuming nav wont work then since that seems to be a common them. ie Alyosius
Re: [ROM][6/3/2010] xtrROM2.0 [stable,lwp, oc]
I noticed you said this has LWP, so I'm assuming nav wont work then since that seems to be a common them. ie Alyosius
Click to expand...
Click to collapse
Nav works very well with lwp on this ROM & I use almost daily. the Nav I have included is Googles NOT the HTC version which is where I believe (though I have fully tested) the issues are caused.
-------------------------------------
Sent via the XDA Tapatalk App
Pure Vanilla 2.1 AOSP - well as much as reasonable .
zach.xtr and I are pleased to offer Vanilla2.X! (BIG credits to zach.xtr for tweaking and help with getting all bugs worked out. zach.xtr truly made this blazing quick... and freed up TONS of internal phone storage!)
checkout the change log for a full feature list and details.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Remember to donate to the developers that make this possible!
Credits:
bertoch for hosting and Linux help
dsixda for his time saving kitchen - http://forum.xda-developers.com/showthread.php?t=633246
Conap and Decadenc3 for their CFS kernel with OC and for MMS fix - http://forum.xda-developers.com/showthread.php?t=774211
Conap for his support and general help and a few libs from CELB - http://http://forum.xda-developers.com/showthread.php?t=679194
punk.kaos for his Trackball notification/softkey fixes - http://forum.xda-developers.com/showthread.php?t=685594
Gnarlyc for his Android Builder for quick access to 2.1 AOSP source - http://forum.xda-developers.com/showthread.php?t=707414
Framework43 for his pioneering work with AOSP 2.1 builds and a few "Senseless" parts - http://forum.xda-developers.com/showthread.php?t=686870
nfinitefx45 from the Hero CDMA forum on his work for cache2cache - http://forum.xda-developers.com/showthread.php?t=790889
other xda members for tips, tricks and beta testing (you ROCK)
SERIOUSLY... DONATE TO ONE OF THE DEVS ABOVE. IF IT WASN'T FOR THEM, YOUR ERIS WOULD BE THE PHONE THAT "COULDN'T"
-----------------------------------------------------------
Base Vanilla2.X Features:
All the goodness of Android AOSP 2.1 with root access superuser permissions
Built from AOSP 2.1 source including all your favorite AOSP 2.1 apps!
Custom sysint process to optimize ROM system settings
Smart design for a tailored user experience (only turn on the features what you want!)
Overclock support - default setting overclock to 710400
Apps2sd and Cache2cache support (see instructions below)
designed to be a stable everyday ROM
Check out the change log below to see details
-----------------------------------------------------------
Download Vanilla2.0.4: http://zach.xtr.i6ix.com/Vanilla2.0.4.zip
MD5 checksum: ae9eb1cf3c67dd08ea31c8cd5ec11dfb
-----------------------------------------------------------
Vanilla2.X Options:
GScript
For Vanilla2.X we have compiled and incorporated the opensource GScript app (see http://code.google.com/p/gscript-android/) to load and one-click run user settings.
To setup your GScripts complete the following steps:
1. After opening GScript press the menu button and select "Add script"
2. A new window will open.
3. Press the Load file button
4. Select a script from the list (each is obviously named as to its function)
5. Ensure Needs SU? is checked
6. Now select "Save" and you have added your script
7. To run just select it from the list in the main GScript screen
8. You must reboot the phone for the change to take effect.
-----------------------------------------------------------
User Services Power Management (Collin_ph Battery Tweak) - I have built in a user services that runs at a polled interval and can set the performance settings of your phone in realtime. The first script that is available is a 2.1 HTC framework version of the Collin_ph Batter Tweak. For a detailed overview of you can view the original thread at here.
The power management battery tweak is disabled by default but there is a gscript to enable plus you can run "battconf" from terminal on the phone or adb shell to configure... The battery tweak runs a script every 60 (or less if you are on power) to poll the capacity of the battery, and as the battery goes down the cpu max freq is progressively lowered. It also changes the CPU write characteristics (all of which I do not yet fully understand). You can see all the details in the /system/bin/batter_tweak file.
I take no real credit on this and just ported the concept to the HTC framework and HTC kernel (with the zanfur OC patch). This took a lot of work and I fixed a few bugs but the concept is not mine and all Collin_ph.
When you first run terminal remember to type "su" (or equivilent for your app) to run as root and select "1" then enter when first prompted after starting "battconf".
So how do I know it is working? just run the report_log.sh GScript and you will see when it logs a change to the system settings. Also you can run the report_system_settings.sh GScript and for a display of current settings. This process will be faster if you plug into a power source and wait about 60 seconds
To enable/disable the battery tweak just run the appropriate GScript (user_service_batterytweak_enable.sh or user_service_batterytweak_disable.sh) and reboot your phone (Quick Boot makes this easy!).
** If you run into issues using the default Term Emulator (in Dev Tools), please download "Android Terminal Emulator" from the Market.
-----------------------------------------------------------
Wired Tether
For wired tether to work you must make sure that your computer has the appropriate RNDIS drivers. Learn how to do this at the android-wired-tether Wiki.
Per roirraW "edor" ehT:
The wiki incorrectly states, or implies, that Windows 7 includes the RNDIS support. Or at least, they imply that Windows 7 includes the RNDIS driver necessary. I can confirm that neither Windows 7 x86 or x64 works with tethering out of the box. The instructions for XP users are correct and also work for Windows 7. Just download HTCSync for your device (Eris) and install it, and it'll install the correct driver.
Performance Improvements:
I HIGHLY recommend setting your Animations (Spareparts) to either OFF or FAST for a much smoother, faster experience.
Free Internal Memory and Dalvik-cache heapsize - We have update default user settings to allow a larger dalvik heapsize of 24mb (think more space for apps to play) AND optimized how memory is freed up using Androids internal task killer.
Default min memory free: “balanced”
Default dalvik vm heapsize: 24m (38m with JIT on)
To change dalvik vm heapsize or min memory free settings you can just run the appropriate GScript.
If you would like to further modify the default min memory free settings then download Autokiller or MinFreeManager, these apps will allow you to set and monitor the min memory free values. For more information on Androids “internal task killer” and min memory free values go here
Overclock Settings - the included kernel supports overclocking and as part of the custom sysinit process we have added scripts that you can run to overclock the CPU without using a market app. You can also run the report _cpu_freq script from GScript to get a printout of which frequencies and time in each you phone has been operating.
To enable/disable overclock just run the appropriate GScript.
If you would like to further modify OC settings then download SetCPU or Overclock Widget, these apps will allow you to set and monitor the CPU speed. Remember YOU CAN DAMAGE YOUR CPU IF RUN TO HOT FOR TO LONG with higher settings. MAKE SURE TO RUN THE set_cpu_stock GSCRIPT IF YOU INSTALL A MARKET APP. The internal overclock support may overwrite the market app settings...
JIT - JIT (Just In Time compiler) is a built in option for the ROM but is off by default. For a detailed overview of JIT go here. PLEASE NOTE for Android 2.1 JIT is not stable with all applications and can cause odd things on your phone.
To enable/disable JIT just run the appropriate GScript and reboot your phone (Quick Boot makes this easy!).
Cache2cache & Cache2sd:
By default, the dalvik-cache for Vanilla2.0 has been relocated from the internal /data/dalvik-cache/ directory to the internal /cache/dalvik-cache directory. The Eris comes with an internal /cache/ file block of 130mb that is not used! After reviewing a number of xda member file system usage reports (thanks xtrROM and xtrSENSE users!) the MOST reported use of this space was 5%... So by moving the dalvik-cache to this free area you now have over 151mb on internal /data/ for apps and over 97mb in internal /cache/ for dalvik-cache. This means that you can probably install close to 100 apps WITHOUT moving anything to the SD Card ext!
You can also move the dalvik-cache to your sd card ext or back to the stock internal /data/ file block.
To change the location of dalvik-cache you can just run the appropriate GScript and reboot your phone (Quick Boot makes this easy!).
Apps2sd:
Apps2sd for Vanilla2.0 is incorporated in the custom sysinit process. For apps2sd to work you must first complete the listed prerequisites and it is a good idea to read through the "things you may want to know about apps2sd" section. Although it can provide gobs of space for apps, Apps2sd is not for everyone as it ties the stability of your phone to your SD Card... If you do not need the space we recommend that you keep the default of DISABLED; if you want to try you can always disable it again however there is always the chance of issues.
To enable/disable apps2sd just run the appropriate GScript and reboot your phone (Quick Boot makes this easy!).
Apps2sd Basics
When you run the apps2sd , upon reboot, it will move ALL your existing apps to the sd card ext partition and ALL future apps will be installed and stored on the sd card ext partition.
Running the apps2internal script, upon reboot, it will move ALL your existing apps to the /data/ block of internal storage and ALL futures apps will be stored in internal storage.
For NON CyanogenMod based ROMs it is all or nothing and you cannot move individual apps.
Apps2sd Prerequisites
If you have not setup your SD card (for those new to Apps2sd) as per tkirton:
BACKUP YOUR SD CARD TO YOUR COMPUTER. Can't stress this enough, as partitioning will wipe the entire card.
Reboot into recovery
In Android System Recovery, select Partition sdcard
In the Partition sdcard menu, select Partition SD
Follow the instructions on the phone to partition your SD card. Most folks seem to recommend using the default values however you can go larger or smaller use values 256, 512,768,1024. You will also be asked to set a swap size; I stayed at 32mb (anticipate future ROM options to allow moving swap to sd)
Once the partition is initially created you must then convert to ext3 - In the Partition sdcard menu, select SD:ext2 to ext3. Follow the instructions on the screen.
Press the back button on the phone to go back to the main menu.
Your SD card is now ready to work with an Apps2sd supported ROM.
Things you may want to know about Apps2sd
Vanilla2.X has bootloop protection built in if your SD card is corrupted or is removed from the phone with Apps2sd enabled. Your apps will go away but your phone will boot .
There are 3 subsets of data associated to an app when it is installed and run on your phone.
1) /data/app/ (and /data/app-private) - actual .apk files we think of as the applications that are not system apps (i.e. installed on /system/app)
2) /data/data/ - the files produced by ALL apps (system apps and market apps) during installation that are used by the Android system to run the app
3)/data/dalvik-cache/ - app cache file and work space for ALL apps (system apps and market apps).
From root explorer (or similar) you can browse to the /data/app OR the /sd-ext/app folders and you will see the same thing, both will tell you how much space you have used and have left. The way apps2sd works is by "linking" the /system/sd/app to the /data/app folder so that the Android system thinks it is accessing the /data/app it is really at /system/sd/app.
I have seen using Apps2sd cause issues with some.zip flash updates as they try to write directly to the /data/app folder which no longer "physically" exists
If you get into a bootloop issue using apps2sd boot into amon_ra recovery and try one of the follow:
1) from the Other menu option select the Fix apk uid mismatches
2) from the Wipe menu option complete a)Wipe data/factory reset b)Wipe Dalvik-cache c)Wipe SD:ext partition
So how do I know Apps2sd is on? You can run the GScript report_system_stats which will give you a printout of what fileblocks are used. You can also go to menu>Settings>Sd card and phone storage - when on space available under Available storage will be over 150mb will go down at a VERY slow rate when new apps are installed.
To Install
YOU MUST HAVE A ROOTED PHONE WITH THE AMON_RA RECOVERY PARTITION
download the base Vanilla 2.X.zip file
complete NANDROID backup
copy the .zip file to the root of your sd card
From amon_ra recovery Wipe data/factory reset, Wipe Dalvik-cache, and Wipe SD:ext partition
flash the Vanilla2.X.zip file from sd card
reboot - first boot will take a while (i.e. over 10 mins - deodexed ROMs take longer on first boot)
complete short setup and let your accounts sync
Setup GScripts
you can now one-click toggle settings at any time
-----------------------------------------------------------
Tips:
Random FC - Lower your overclock settings or turn off JIT. Our little Eris's can only do so much and not all hardware is equal... Also remember this ROM is quite fast in stock form and higher Linpack scores DO NOT make for a better user experience
If you have 50% time without signal under Settings>About Phone>Battery>Cell Standby complete the "airplane trick" by turning Airplane mode on wait just a few seconds and then Airplane mode off (search the forum for "time without a signal")
Turn off notifications for Superuser 2.3.5 from the Settings tab of the app
Pure AOSP 2.1 does NOT play wma/wmv files. I have attempted to fix, but still a work in progress. Please download "yxplayer Pro" from the market if you need wma/wmv capabilities.
-----------------------------------------------------------
KNOWN ISSUES:
autobrightness not working
camera zoom not working
trackball notify only once with message... ** (see below)
NFL Mobile from Verizon app does not work with JIT
xda dev app may have intermittent issues logging in for first time with JIT
MMS video recived issue (true for ALL known AOSP ROMs)
-----------------------------------------------------------
** If you prefer that Notifications are mapped to the LED light instead (it will continually flash to notify you, as opposed to the default trackball light, which will only flash once), you can download the following and flash in recovery:
http://zach.xtr.i6ix.com/LED-Notifications.zip
-----------------------------------------------------------
Change Log and Such
Change Log
Vanilla 2.0.4 Change log
More minor updates...
Download: http://zach.xtr.i6ix.com/Vanilla2.0.4.zip
MD5 checksum: ae9eb1cf3c67dd08ea31c8cd5ec11dfb
fixed Contacts category bug and updated contacts
fixed NAND ext backup issue by changing the mount point for sd ext to /system/sd instead of /sd-ext/ (ALL apps2sd/cache2sd related scripts and the init.rc file)
updated a number of gscripts
New userservice framework and battery tweak service now built into the custom sysinit process
added Multi-Touch browser
updated kernel (modified CFS kernel)
updated superuser (chainsdd)
updated maps
updated street
updated voice
updated market
Vanilla 2.0.3 Change log
Minor updates...
Download: http://zach.xtr.i6ix.com/Vanilla2.0.3.zip
MD5 checksum: 8a15ca3c277ceb2b6b0e4cfeff808a96
updated to newest BFS kernel
updated build.prop to enable wma (recognized, still not playing)
install Live wallpager support via GScript (Although fun ... MOST LWP DO NOT WORK WELL ON ERIS HARDWARE )
fixed set min memory GScripts
removed default overclock (run the set cpu overclok gscript to turn on)
added Gscript support to set min CPU freq value of 19200 (for you battery save folks) and max value of 748800
updated to older version of street.apk (the street view on nav) as the current sometimes displayed a half transpartent white/black overlay
updated the icon of the settings to match the new stock 2.1 icon set...
Vanilla2.0-beta
Initial release of pure Vanilla AOSP 2.1 sweetness... A BIG thanks to tenzomonk for getting this nice little ROM going!
Download Vanilla2.0: http://zach.xtr.i6ix.com/Vanilla2.0-beta.zip
MD5 checksum: d122323a996c1d0a067578c64f0b23dd
new 2.6.29.6 BFS Kernel
"Purest" 2.1 ASOP Eris ROM to date (A LOT of work went into getting everything STOCK and running smooth and reliably for the ERIS)
Rooted with current Superuser 2.3.5
Full overclock support with built in default settings of 710400
Full Apps2sd support (easy toggle with Gscripts)
Full Cache2cache and Cache2sd support - default to /cache/ which opens up close to 250mb of INTERNAL phone storage! (easy toggle with Gscripts)
Just In Time (JIT) Compiler support (easy toggle with Gscripts)
Custom sysinit process to allow user control and optimize ROM performance settings
Current stock 2.1 Vanilla apps:
Clock (with working weather)
Browser
News and Weather
Music
Gallery 3d (smooth and fast!)
Contacts (with market facebook sync)
Email
Messaging (with working MMS)
Camera
Calendar
Calculator
Added
Wireless Tether
Wired Tether
Corporate Calendar
Dev Tools
Spare Parts
Current 1.3.2 Facebook (can be uninstalled)
Quick Boot
Custom build of GScripts
Much more that we have forgotten
This build looks very nice. I am not a big fan of the dialer though. I used that dialer in the Froyo builds and don't like how it does not have smart dialing. I rely on smart dialing very extensively. May I ask what AOSP means? How does that compare to the kernel that is used in the xtrSense rom?
Thanks for all of the hard work you devs do to give us these great roms to increase the life of the Eris. I think, and have always thought the Eris is the best phone I have ever owned.
Jeff
thanks jeff! for the dialer... we didn't change anything in regards to the "Vanilla" feel. we were both just looking to get a "real" 2.1 AOSP release out
AOSP = Android Open Source Project
as for the kernel, check this post here for full details:
http://forum.xda-developers.com/showthread.php?t=772053
Downloading right now... SO excited! ......... giggity
This ROM needs live wallpapers Other than that..... I can tell this is going to be my daily ROM already, just from playing with it for like 3 minutes. Can't wait for updates!
Thanks for the rom. Everything good so far. Just one thing could you guys keep the original eris camera format. I like the old camera that takes up the entire screen when taking pictures.
sowhat808 said:
Thanks for the rom. Everything good so far. Just one thing could you guys keep the original eris camera format. I like the old camera that takes up the entire screen when taking pictures.
Click to expand...
Click to collapse
i believe you are referring to the HTC Camera. (Un)fortunately, this ROM has no HTC framework built-in...
------------------------------------------------------------------------------
as for LWP's... that's certainly a possibility moving forward
mmm Gotta Try this !! thanks !!!
Its about time Tenzo and Zac!
Question,
I've been running the 1.9 beta. Should I do a full wipe and flash?
GPS has been working perfectly for me on that version by the way.
Glad to see two great devs on one project! Thanks for all the hard work!
So we have found one bug in the set minmemory gscripts where the vales do not set after reboot... a missplaced quotation mark : (
[EDIT] fixed and will be in next relase...
Sent from my Eris using XDA App
Seanydizzley said:
Its about time Tenzo and Zac!
Question,
I've been running the 1.9 beta. Should I do a full wipe and flash?
GPS has been working perfectly for me on that version by the way.
Glad to see two great devs on one project! Thanks for all the hard work!
Click to expand...
Click to collapse
yes... you will have to wipe. we have incorporated a lot of changes, new kernel, etc. thanks for the testing! it's much appreciated! you should have no GPS issues with this release either
Awesome! Flashing now! Great work guys! Glad to see it go public.
The best of luck to you both!
Zach and Tenzo, got a question before I flash this. Since you have freed up so much internal app space, A2Sd does not seem to be really needed. Can the ROM be booted without a partitioned card (and then of course never run the script to turn A2SD on)?
Thanks
caleris said:
Zach and Tenzo, got a question before I flash this. Since you have freed up so much internal app space, A2Sd does not seem to be really needed. Can the ROM be booted without a partitioned card (and then of course never run the script to turn A2SD on)?
Thanks
Click to expand...
Click to collapse
yup... that's how i'm running it now
tenzomonk said:
yup... that's how i'm running it now
Click to expand...
Click to collapse
Super, that is how I will try it as well.
Thanks
Great job! Thanks. I just flashed it, and so far so good. I've never had to make so few pre-flash changes before.
It seems as if the contacts are being sorted incorrectly on my phone, headings are not being displayed based on first letter. The only headings displayed are "S" and "e". Not sure if this is a setting on my end or an issue with the dialer/contacts.
Great job on the ROM, I'm always looking for good AOSP ROM.
wshuman3 said:
It seems as if the contacts are being sorted incorrectly on my phone, headings are not being displayed based on first letter. The only headings displayed are "S" and "e". Not sure if this is a setting on my end or an issue with the dialer/contacts.
Great job on the ROM, I'm always looking for good AOSP ROM.
Click to expand...
Click to collapse
ahhh, you are right! good find!
they actually do sort correctly for me... but the S and E are the only "headings" shown.
will get that fixed up
you credit nfinitefx45 for his work on cache2cache but I can't seem to pull up anything with forum search within CDMA forum.
I was going through another site & came across a Terminology Guide. I couldn’t find something similar here so just wanted to take it upon myself to create a well organized post providing abbreviations & terminology so that any one, Master or Newbie, can have a quick reference guide to all things droid. I myself do not know everything but I do know some things & I believe with some help from the moderators & contributing members of xda-developers, we can throw together a one-stop-shop for all the droid info.
[FONT="]A special thanks to [/FONT][FONT="]Sam Fisher [/FONT][FONT="]at[/FONT][FONT="] droidforums [/FONT][FONT="]for the inspiration[/FONT][FONT="]!![/FONT]
Thanks to My_Immortal, OmegaRED^ & Spaarc for their suggestions & information shared!
________________
ADK: Android Development Kit, What people use to develop anything for the Android such as ROM's
The ADK (Android development kit) is divided into 3 parts
1. Android SDK (Software development Kit): used to make easy programs which only require touch & some sensors , e.g. Games
2. Android NDK ( Native Development Kit): this is used to Create apps which require Hardware or Use the native binaries & libraries of Android , eg. Camera , CyanogenMod Settings, Oxygen Settings , etc.
3. Android PDK ( Platform Development Kit): As the name suggests this is the main kit which allows to make all ".mk" files (eg. Android.mk, etc) & most of the files found on github
Basically Dev's like FXP , Z , Achotjan , kxhawkins , etc. Use the PDK to make AOSP/CM7 ROMs from source
& Also use NDK to edit the system apk's etc. to make it stable
adb: Android Debug Bridge, a command-line debugging application included with the SDK. It provides tools to browse the device, copy tools on the device, & forward ports for debugging. If you are developing in Eclipse using the ADT Plugin, adb is integrated into your development environment.
AOSP: Android Open System Project, usually you will see this term when referring to a program or ROM. This will mean that the program or ROM was taken from Google & does not contain any modifications done by the phone Manufacturer or the phone service provider. This is Android the way Google intended.
Application Programming Interface (API): An interface used by applications to communicate with each other. An API is a library that may include specification for routines, data structures, object classes, and variables. APIs are particularly useful in extending a platform.
Apps2SD: A method of storing items and Cache on the device’s microSD card, allowing you to run apps on external memory.
Boot Animation: A term for a graphical representation of the boot process of the OS. Boot animation can be a simple visualization of the scrolling boot messages in the console, or it can present graphics or some combination of both. Boot animation is not necessarily designed for marketing purposes, but can enhance the experience of the user as eye candy, or provide the user with messages to diagnose the state of the system.
Baseband or Radio: In communications & signal processing, the baseband describes signals & systems whose range of the frequencies measured from close to 0 hertz to a cut-off frequency, a maximum bandwidth or highest signal frequency; it is sometimes used to describe frequencies starting close to zero
Boot Loader/SPL: In literal terms, boot loader is code that is executed before any Operating System starts to run. The concept of boot loaders is universal to virtually all Operating systems that include operating systems on your PC, laptop, Smartphone, & other such devices. Boot loaders basically package the instructions to boot operating system kernel & most of them also have their own debugging or modification environment. As the boot loader kicks off before any piece of software on your device, it makes it extremely processor specific & every motherboard has its own boot loader.
Boot Loader/SPL (Unlocked): A locked or unlocked boot loader is what gives you access to “root.” “Root” is another big word in the Android community. If you “root” a device, it means you have “super user” access or “administrator” access to the operating system that runs on your phone. Root access of your Android device gives you the ability to flash ROMs.
One of the most popular ROMs was created by a team called the CyanogenMod(CM), & their current rom is CM7, which is built on Android 2.3 Gingerbread. What this means is that if you have a phone that has an unlocked boot loader & root access, you can flash the CM7 ROM to your phone with a couple more steps. This also means that you can get access to most of the features in the latest version of Android that is commercially available, without having to wait for your manufacturer or carrier to give you an official update.
Boot Loop: Simply means something is preventing the phone from completing it's boot cycle & is stuck between the boot animation & the unlock screen, creating a looped animation. This is often fixed by either reloading a NAndroid, or Reflashing a ROM from the xRecovery/ClockworkMod Recovery/Flashtool.
Brick or Bricked: Jargon for a completely unrecoverable device, (no more than a brick or paperweight)
Note: It is my understanding that radio will boot first, followed by other systems. So it is IMPORTANT that your radio image/version will work with your SPL image/version. This is the one & only reason for phones being bricked. You cannot brick your phone by flashing a ROM or Boot image or recovery image. Once you flash the wrong radio for the SPL, the only known method of recovery is to send the phone back into SE for repair.
How do I know the phone is hard-bricked? A hard-bricked phone cannot boot into boot loader, recovery, or into normal operation modes. You cannot connect to a hard-bricked phone via adb or fastboot. You can only see one screen on the phone & it will be the first splash screen.
Bug or Software Bug: An Error or flaw in software that produces a failure or unexpected/unwanted result. Typically created from incorrect code, this is why some ROMs are better & smoother running than others because developers have taken the time to input "perfect" code (read put in a lot of hours & hard work)
Busybox: A single multicall binary that packages the functionality of most widely used standard Unix tools, BusyBox provides a fairly complete environment for any small or embedded system.
Canvas: A drawing surface that handles compositing of the actual bits against a Bitmap or Surface object. It has methods for standard computer drawing of bitmaps, lines, circles, rectangles, text, and so on, and is bound to a Bitmap or Surface. Canvas is the simplest, easiest way to draw 2D objects on the screen. However, it does not support hardware acceleration, as OpenGL ES does. The base class is Canvas.
COMPCACHE: (compressed caching) is, in short, virtual swap, setting aside a certain percentage (usually 25%) of your RAM as 'compressed' swap. Compcache compresses the data that would normally go to swap, then moves it back into RAM, and reverses the process when moving it out of the 'compressed' swap. However, this is a classic space-time trade-off. You effectively get more RAM from the compression, but it is slower than 'normal' RAM due to the CPU time required to compress and decompress the swapped pages.
ClockworkMod: A recovery program that is often used to apply updates, ROMs, or create a back up or restore a backup file
Custom ROM: A custom ROM can range in definition from some custom code modifications to make Android run better on a device, all the way to changing the homescreen, background services, and default software.
Many software experts collaborate together in communities to build the fastest or most feature filled ROM’s. The most popular today are CyanogenMod (which supports over 70 devices!), AOKP (a lightweight ROM with plenty of customization options), and Android Revolution, a heavyweight ROM which often focusses on looking great. Just because these Android builds are made by ‘ordinary people’ and not highly paid developers at HTC or Samsung doesn’t mean they are full of bugs or risky to use. In most cases the software built by communities is ten times better. Release cycles are much shorter, fun features can be put in, and anyone can contribute an idea to the development.
DALVIK: An open source, register-based virtual machine (VM) that’s part of the Android OS. The Dalvik VM executes files in the Dalvik Executable (.dex) format, a format that is optimized for efficient storage and memory-mappable execution & relies on the Linux kernel for additional functionality like threading & low-level memory management. The virtual machine is register-based, and it can run classes compiled by a Java language compiler that have been transformed into its native format using the included "dx" tool. The Dalvik core class library is intended to provide a familiar development base for those used to programming with Java Standard Edition, but it is geared specifically to the needs of a small mobile device.
Dalvik Cache: A program cache area for the program Dalvik. Dalvik is a java based virtual machine that is the basis for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the dalvik-cache is the result of dalvik doing a optimization of the running program. It's similar to the prefetch files in Windows.
DDMS: Dalvik Debug Monitor Service, a GUI debugging application included with the SDK. It provides screen capture, log dump, and process examination capabilities. If you are developing in Eclipse using the ADT Plugin, DDMS is integrated into your development environment.
Deep Sleep: A state when the CPU is off, display dark, device is waiting for external input.
Density-Independent pixels (dp): A virtual pixel unit equivalent to one physical pixel on an average, “medium” density 160 dpi screen. On higher ppi screens, dp’s are scaled to retain a constant size (px = dp * (dpi/160)). For example, on a 200 dpi screen, the dp would take up 1.25 physical pixels.
Dots per inch (DPI, or dpi) is a measure of spatial video dot density, in particular the number of individual dots that can be placed in a line within the span of 1 inch (2.54 cm).
De-odex: Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file & put it back inside the apk. This allows you to easily replace files (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) & to deodex services.jar, you need to deodex everything.
Dev. or Developer: An individual that creates, or alters a file in such a manner as to advance the program
Drawable: A compiled visual resource that can be used as a background, title, or other part of the screen. A drawable is typically loaded into another UI element, for example as a background image. A drawable is not able to receive events, but does assign various other properties such as "state" and scheduling, to enable subclasses such as animation objects or image libraries. Many drawable objects are loaded from drawable resource files — xml or bitmap files that describe the image. Drawable resources are compiled into subclasses of android.graphics.drawable.
Fastboot: Protocol used to update the flash file system in Android devices from a host over USB. It allows flashing of unsigned partition images.
FC/FC’s: Short for “force close,” meaning an app that has crashed.
Flash: Rewrite the software/firmware on your phone using a computer to "flash" or completely rewrite the memory (ROM) of your phone. This is done using ODIN.
Flash Memory: a program technology that can be electrically erased & reprogrammed
Flashtool: It is a S1 flashing software that works for all Sony phones from X10 to Xperia Z Ultra. They all use the S1 protocol for flashing firmwares.
This program was originally made to flash sin files downloaded by SEUS or PCC. From time to time, sin files have been bundled into what is now well known FTF (Flash Tool Firmwares). That is the core of Flashtool and the reason of its name.
Flashtool can also easily unlock the bootloader of the phone using the BLU icon as far as the bootloader of your phone is unlockable.
Flashing: The ROM memory used in smartphones and tablets etc. is often same as flash memory found in SD Cards and USB flash drives, simply optimized for better speed and performance while running the operating system.
Hard Reset: The act of resetting your phone to its “factory” state. A hard reset erases all user data, logins, and passwords. This process may or may not erase the contents of the internal storage and/or microSD card as well.
JIT: The Just-in-Time Compiler, released with Android 2.2, it’s a method of greatly speeding up apps in Android. The JIT compiler analyzes an app’s code and converts it, allowing the app to run faster. It does all this while the application is running, hence “just in time.” The JIT compiler for Android functions with a very short “warm up” time; it doesn’t take very long to analyze the code before it starts working.
Kernel: The main component of Android operating system.
It is a bridge between applications & the actual data processing done at the hardware level.
The kernel's responsibilities include managing the system's resources (the communication between hardware & software components).
[Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources
(especially processors & I/O devices) that application software must control to perform its function.
It typically makes these facilities available to application processes through inter-process communication mechanisms & system calls.
Operating system tasks are done differently by different kernels, depending on their design & implementation.]
Launcher: Collectively, the part of the Android UI on the home screen that allows you to launch apps, make phone calls, etc. It is built into Android, or can be purchased in the Android Market.
Manifest File: An XML file that each application must define, to describe the application's package name, version, components (activities, intent filters, services), imported libraries, and describes the various activities, and so on. See The AndroidManifest.xml File for complete information.
Nine-patch / 9-patch / Ninepatch image: A re-sizeable bitmap resource that can be used for backgrounds or other images on the device.
Nandroid or Nandroid Backup: A file typically created in the custom recovery program, such as xRecovery, that is a carbon copy of whatever state your phone is in before a drastic change is made. The file then can be moved onto or off of the SD card for later use in case something should go wrong in the ROM or Update, or a Boot Loop occurs
ODIN: It is the program you can use to flash phones.
e.g. : 'Odin Multi-Downloader v3.95' is used to flash the Samsung Galaxy. It's usually included in firmware packs.
OEM: Original Equipment Manufacturer, the people who actually put together electronic hardware. Also refers to any equipment original to the phone, or produced by the company for the phone
OpenGL ES: A cross-platform API for full-function 2D and 3D graphics on embedded systems. Android provides OpenGL ES libraries that you can use for fast, complex 3D images. It is harder to use than a Canvas object, but better for 3D objects. The android.opengl and javax.microedition.khronos.opengles packages expose OpenGL ES functionality.
OS: Operating system, I.E. Windows Vista, LINUX or MAC or Android
OTA: Over-the-Air; method T-Mobile, & some other phone companies, uses to update Android phones. The new versions of Android are developed by Google & then released to OEM's, Sony Ericsson in our case. The OEM then writes drivers that enable the new software to work on the phone's hardware. They also develop any specialized UI (user interface), like Timescape & Mediascape, or other software they want to include. Once this is complete, they turn it over to the cell phone company, (e.g.)Tmobile, who then have to do the final checks to make sure the update works, & then distributes it over there data network using their cell transmitters.
Overclocking (OC): Speeding up the CPU past the factory presets to achieve a faster & more responsive device (prolonged run can be injurious to your device, so be careful.
Partition: The phone’s internal memory (not the SD Card) is solid-state (flash) memory. It can be partitioned much like a normal hard drive can be partitioned. On an Android device, the Bootloader exists in its own partition. Recovery is another partition; radio, system, Cache, etc. are all partitions.
Here are the standard partitions on an Android phone:
/misc – miscellaneous…
/boot – bootloader, kernel
/recovery – holds the recovery program (either clockworkmod or RA recovery for a rooted Evo)
/system – operating system goes here: Android, etc.
/cache – cached data from OS usage
/data – user applications, data, settings, etc.
The below partitions are not Android-specific. They are tied to the hardware of the phone, but the kernel may have code allowing Android to interact with said hardware.
/radio – the phone’s radio firmware, controls cellular, data, GPS, bluetooth.
/wimax – firmware for Sprint’s flavor of 4G, WiMax.
Recovery Mode: A small separate operating mode you can boost your device into, used for device administration. Two popular custom recovery modes for our device are xRecovery and ClockworkMod.
ROM: Read Only Memory, a program used to make changes to anything from the look of the home screen to icons to custom boot animation.
Root: Common word associated with giving a user "super user" access to their phones programming & other various aspects that would normally not be possible, also known as "Jailbroken" for iPhone's, "Administrator Rights" in Windows OS.
Shell or SSH: The shell is the layer of programming that understands & executes the commands a user enters. In some systems, the shell is called a command interpreter. A shell usually implies an interface with a command syntax (think of the DOS operating system & its "C:>" prompts & user commands such as "dir" & "edit"). secure shell or ssh is a network protocol that allows data to be exchanged using a secure channel between two networked devices
Soft Reset: The act of rebooting your phone, whether intentionally or otherwise, same effect as when you remove and replace the battery.
SQLite: An embedded relational database management system contained in a relatively small (~275 kB) C programming library. It is multitasking concerning reads. Writes can be done only one-at-a-time. It is a popular choice for local/client storage on web browsers. It has many bindings to programming languages. It is arguably the most widely used database engine, as it is used today by several widespread browsers, operating systems, embedded systems among others
Stock: Simply means an unaltered state, such as when you first purchase your phone from Verizon/Your Service Provider or when you repair your phone using PC Companion or SE Update Service(SEUS)
SU: "Super user", or root permissions
SWAP: is, in short, virtual RAM. With swap, a small portion of the hard drive is set aside and used like RAM. The computer will attempt to keep as much information as possible in RAM until the RAM is full. At that point, the computer will begin moving inactive blocks of memory (called pages) to the hard disk, freeing up RAM for active processes. If one of the pages on the hard disk needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the hard disk ('swapped'). The trade off is disks and SD cards are considerably slower than physical RAM, so when something needs to be swapped, there is a noticeable performance hit.
Unlike traditional swap, Android's Memory Manager kills inactive processes to free up memory. Android signals to the process, then the process will usually write out a small bit of specific information about its state (for example, Google Maps may write out the map view coordinates; Browser might write the URL of the page being viewed) and then the process exits. When you next access that application, it is restarted: the application is loaded from storage, and retrieves the state information that it saved when it last closed. In some applications, this makes it seem as if the application never closed at all. This is not much different from traditional swap, except that Android apps are specially programmed to write out very specific information, making Android's Memory Manager more efficient that swap.
Theme: A set of icons, backgrounds & app trays that change the aesthetics of the overall look of the Android & its applications. It has a set of properties (text size, background color, and so on) bundled together to define various default display settings. Android provides a few standard themes, listed in R.style (starting with "Theme_").
TWRP: TeamWin Recovery Project – or TWRP for short – is a fully touch-based custom recovery that was initially developed for Nexus devices, but has since been made available for countless other smartphones and tablets as well, in form of both official and third-party builds.
TUN/TAP: Refers to a network TUNnel, operates within layer 3 packets, or ip packets. Packets sent by a system via a TUN/TAP device are delivered to a user-space program that attaches itself to the device. A user space program may also pass packets into a TUN/TAP device. In this case TUN/TAP device delivers (or "injects") these packets to the operating system's network stack thus emulating their reception from an external source.
Underclocking(UC): Slowing down the CPU mainly to limit battery usage
Undervolting(UV): Basically keeping the clock speed same (or overclocking it) & reduce the voltage at each cpu cycle.
Updater Script: A scripting language called Edify for all Android OS since “Donut.” Updater Script is used with recovery mode, to perform a wide range of functions on files and permissions.
xRecovery: A recovery program based on the ClockworkMod Recovery sources used to apply updates, ROMs, or create a back up or restore a backup file
Zipalign: An archive alignment tool that optimizes the way a .apk is packaged. Doing so enables the Android operating system to interact with the application more efficiently, and hence has the potential to make the application and system much faster. Execution time is minimized for zipaligned applications, resulting is less RAM consumption when running the .apk.
File Types:
.dex: Compiled Android application code file. Android programs are compiled into .dex (Dalvik Executable) files, which are in turn zipped into a single .apk file on the device. .dex files can be created by automatically translating compiled applications written in the Java programming language.
.sbf: Summation Briefcase File
.apk or APK's: An .apk file extension denotes an Android Package (APK) file, an .apk file can be opened & inspected using common archive tools. Each Android application is compiled and packaged in a single file that includes all of the application's code (.dex files), resources, assets, and manifest file. The application package file can have any name but must use the .apk extension. For example: myExampleAppname.apk. For convenience, an application package file is often referred to as an ".apk".
.tar: Similar to a zip file(derived from tape archive), a tar file archives multiple files into one file
.tgz: TGZ files (gnu-zipped .tar file) are commonly used as install packages for Slackware Linux.
pheeeeww!!This took sometime!!
Well this is all I can think of off the top of my head but as I think of more I will edit them in here & I encourage the mods to put things that I either forgot or just simply am not aware of. Also I request fellow user to suggest any terms frequently used & not added or any discrepancies found, kindly PM me!!
Thank you & happy hacking/flashing!!
_____________________________________
X10 LED States:-
--------------------------------------
W-LOD: White LED of DEATH.
--------------------------------------
Sometimes a R-LOD is similar to a W-LOD but the LED is red instead.
Usually results in a Reboot, or a Freeze or a Crash
-------------------------------
Flashing R-L: Red LED.
-------------------------------
Led flashes RED 3 times.
Indicates Requirement for Charge
--------------------------------
G-LS: Green LED Steady.
--------------------------------
LED goes Steady GREEN while USB is plugged in.
Flash Mode Entered/Fully Charged.
CPU : -
----------------------------------------
Central Processing Unit: -
----------------------------------------
It's pretty much the heart of your device pumping data through & from all the attached devices the Kernel & Modules is its soul & it's OS is it's skin & flesh.
-----------------------
Core Clock Speed: -
-----------------------
It is the actual clock speed that the CPU is running at. "Not the multiplied speed."
It's good to remember a CPU's performance is also effected by its memory's speed.
Similar rules exist for the GPU (Graphics Processing Unit).
Nice effort! Thanks!
Although, you got the Kernel thing wrong:
kloud_ said:
Kernel: The govenor of the CPU usage and Battery output, one can upload certain Kernals to achieve greater performance speed of their device at the cost of some battery life
Click to expand...
Click to collapse
Kernel: It's the main component of Android operating system.
It is a bridge between applications and the actual data processing done at the hardware level.
The kernel's responsibilities include managing the system's resources (the communication between hardware and software components).
[Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources
(especially processors and I/O devices) that application software must control to perform its function.
It typically makes these facilities available to application processes through inter-process communication mechanisms and system calls.
Operating system tasks are done differently by different kernels, depending on their design and implementation.]
My_Immortal said:
Nice effort! Thanks!
Although, you got the Kernel thing really wrong:
Kernel: It's the main component of Android operating system.
It is a bridge between applications and the actual data processing done at the hardware level.
The kernel's responsibilities include managing the system's resources (the communication between hardware and software components).
[Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources
(especially processors and I/O devices) that application software must control to perform its function.
It typically makes these facilities available to application processes through inter-process communication mechanisms and system calls.
Operating system tasks are done differently by different kernels, depending on their design and implementation.]
Click to expand...
Click to collapse
Thanks for correcting me... got a bit distracted and thus the blunder. My bad.
Have edited the term
Good work thaks
Sent from my GT-I9000 using Tapatalk
Brilliant. Prefect for newbies. I wish there was something like this when i started lol.
Sent from my X10 TripNMiUI-1.8.19 using XDA App
kylec said:
Brilliant. Prefect for newbies. I wish there was something like this when i started lol.
Sent from my X10 TripNMiUI-1.8.19 using XDA App
Click to expand...
Click to collapse
better late than never!!
Nice work Bro, great idea, wants a sticky
colossus said:
Nice work Bro, great idea, wants a sticky
Click to expand...
Click to collapse
thanks Smarts or Colossus!
vERY nice guide
The ADK (android development kit) is divided into 3 parts
1.Android SDK (Software development Kit) : used to make easy programs which only require touch and some sensors , eg. Games
2.Android NDK ( Native Development Kit) : this is used to Create apps which require Hardware or Use the native binaries and libraries of Android , eg. Camera , CyanogenMod Settings , Oxygen Settings , etc.
3.Android PDK ( Platform Development Kit) : As the name suggests this is the main kit which allows to make all ".mk" files (eg. Android.mk , etc) and most of the files found on github
Basically Dev's like FXP , Z , Achotjan , kxhawkins , etc. Use the PDK to make AOSP/CM7 ROMs from source
And Also use NDK to edit the system apk's etc.. to make it stable
That's some knowledge from my side
spaarc said:
vERY nice guide
The ADK (android development kit) is divided into 3 parts
1.Android SDK (Software development Kit) : used to make easy programs which only require touch and some sensors , eg. Games
2.Android NDK ( Native Development Kit) : this is used to Create apps which require Hardware or Use the native binaries and libraries of Android , eg. Camera , CyanogenMod Settings , Oxygen Settings , etc.
3.Android PDK ( Platform Development Kit) : As the name suggests this is the main kit which allows to make all ".mk" files (eg. Android.mk , etc) and most of the files found on github
Basically Dev's like FXP , Z , Achotjan , kxhawkins , etc. Use the PDK to make AOSP/CM7 ROMs from source
And Also use NDK to edit the system apk's etc.. to make it stable
That's some knowledge from my side
Click to expand...
Click to collapse
Thanks Spaarc.
Will add it right away! Thanks once again
This could be called "AndroidDictionary for noobs"
Infinity Ytinifni S. Sent from Xperia X10i-modded.
X10 Led States:-
----------------------
W-Lod: White LED of DOOM.
--------------------------------------
Sometimes a R-lod is similar to a W-lod but the LED is red instead.
Usually results in a Reboot, or a Freeze or a Crash
R-R-L: Red Rolling LED.
-------------------------------
Led flashes RED 3 times.
Indicates Requirement for Charge
G-LS: Green LED Steady.
--------------------------------
LED goes Steady GREEN while usb is plugged in.
Flash Mode Entered and or Fully Charged.
Cpu's. Central Processing Unit:-
----------------------------------------
It's pretty much the heart of your device pumping data through and from all the attached devices the Kernel and Modules is it's soul and it's OS is it's skin and flesh.
Core Clock Speed:Is the actual clock speed that the CPU is running at. "not the multiplied speed."
It's good to remember a CPU's performance is also effected by it's memory's speed.
Similar rules exist for the GPU.
This place was so color less i figured i would bring some.
haha
thanks for the post OmegaRED^
thanx pretty usefull info out there.!!
Definetly a Sticky. Thanks very much!
Now I know what a "WLOD" is. I had no idea before.
Karl
i though WLOD is stand for White LED of death....just like blue screen of death for windows (but who cares...it still got same meaning anyway )
anyway...nice thread....should request for sticky
Arnold.Alexius said:
i though WLOD is stand for White LED of death....just like blue screen of death for windows (but who cares...it still got same meaning anyway )
anyway...nice thread....should request for sticky
Click to expand...
Click to collapse
Thanks... it stands for death but I liked the way it sounds so didn't change what OmegaRED^ had suggested!
A few corrections.
OTA: Over The Air.
tar: Tape ARchive - archive consisting of multiple files that has not been compressed.
tgz: compressed tarbol (tape archive) usually with gzip.
shell: the standard command language interpreter.
ssh: secure shell - provides secure encrypted communications between two untrusted hosts over an insecure network.
This was an easy explanation for all noobs, like me. Thanks
ynkamat said:
This was an easy explanation for all noobs, like me. Thanks
Click to expand...
Click to collapse
You're welcome!
Warm Regards
kLouD
Sent from my X10i on J's CM7 & DooM's v4 kernel using XDA Premium App
i found this in xperia x10 general section maybe we should have the same thread in our general section
[source] xperia x10 general section from kloud_
I was going through another site & came across a Terminology Guide. I couldn’t find something similar here so just wanted to take it upon myself to create a well organized post providing abbreviations & terminology so that any one, Master or Newbie, can have a quick reference guide to all things droid. I myself do not know everything but I do know some things & I believe with some help from the moderators & contributing members of xda-developers, we can throw together a one-stop-shop for all the droid info.
A special thanks to Sam Fisher at droidforums for the inspiration!!
Thanks to My_Immortal, OmegaRED^ & Spaarc for their suggestions & information shared!
________________
ADK: Android Development Kit, What people use to develop anything for the Android such as ROM's
The ADK (Android development kit) is divided into 3 parts
1. Android SDK (Software development Kit): used to make easy programs which only require touch & some sensors , e.g. Games
2. Android NDK ( Native Development Kit): this is used to Create apps which require Hardware or Use the native binaries & libraries of Android , eg. Camera , CyanogenMod Settings, Oxygen Settings , etc.
3. Android PDK ( Platform Development Kit): As the name suggests this is the main kit which allows to make all ".mk" files (eg. Android.mk , etc) & most of the files found on github
Basically Dev's like FXP , Z , Achotjan , kxhawkins , etc. Use the PDK to make AOSP/CM7 ROMs from source
& Also use NDK to edit the system apk's etc.. to make it stable
adb: Android Debug Bridge, a command-line debugging application included with the SDK. It provides tools to browse the device, copy tools on the device, & forward ports for debugging. If you are developing in Eclipse using the ADT Plugin, adb is integrated into your development environment.
AOSP: Android Open System Project, usually you will see this term when referring to a program or ROM. This will mean that the program or ROM was taken from Google & does not contain any modifications done by the phone Manufacturer or the phone service provider. This is Android the way Google intended.
Baseband or Radio: In communications & signal processing, the baseband describes signals & systems whose range of the frequencies measured from close to 0 hertz to a cut-off frequency, a maximum bandwidth or highest signal frequency; it is sometimes used to describe frequencies starting close to zero
Boot Loader/SPL: In literal terms, boot loader is code that is executed before any Operating System starts to run. The concept of boot loaders is universal to virtually all Operating systems that includes operating systems on your PC, laptop, Smartphone, & other such devices. Boot loaders basically package the instructions to boot operating system kernel & most of them also have their own debugging or modification environment. As the boot loader kicks off before any piece of software on your device, it makes it extremely processor specific & every motherboard has its own boot loader.
Boot Loader/SPL (Unlocked): A locked or unlocked boot loader is what gives you access to “root.” “Root” is another big word in the Android community. If you “root” a device, it means you have “super user” access or “administrator” access to the operating system that runs on your phone. Root access of your Android device gives you the ability to flash ROMs.
One of the most popular ROMs was created by a team called the CyanogenMod(CM), & their current rom is CM7, which is built on Android 2.3 Gingerbread. What this means is that if you have a phone that has an unlocked boot loader & root access, you can flash the CM7 ROM to your phone with a couple more steps. This also means that you can get access to most of the features in the latest version of Android that is commercially available, without having to wait for your manufacturer or carrier to give you an official update.
Boot Loop: Simply means something is preventing the phone from completing it's boot cycle & is stuck between the boot animation & the unlock screen, creating a looped animation. This is often fixed by either reloading a NAndroid, or Reflashing a ROM from the xRecovery/ClockworkMod Recovery/Flashtool.
Brick or Bricked: Jargon for a completely unrecoverable device, (no more than a brick or paperweight)
Note: It is my understanding that radio will boot first, followed by other systems. So it is IMPORTANT that your radio image/version will work with your SPL image/version. This is the one & only reason for phones being bricked. You cannot brick your phone by flashing a ROM or Boot image or recovery image. Once you flash the wrong radio for the SPL, the only known method of recovery is to send the phone back into SE for repair.
How do I know the phone is hard-bricked? A hard-bricked phone cannot boot into boot loader, recovery, or into normal operation modes. You cannot connect to a hard-bricked phone via adb or fastboot. You can only see one screen on the phone & it will be the first splash screen.
Bug or Software Bug: An Error or flaw in software that produces a failure or unexpected/unwanted result. Typically created from incorrect code, this is why some ROMs are better & smoother running than others because developers have taken the time to input "perfect" code (read put in a lot of hours & hard work)
Busybox: A single multicall binary that packages the functionality of most widely used standard Unix tools, BusyBox provides a fairly complete environment for any small or embedded system.
COMPCACHE: (compressed caching) is, in short, virtual swap, setting aside a certain percentage (usually 25%) of your RAM as 'compressed' swap. Compcache compresses the data that would normally go to swap, then moves it back into RAM, and reverses the process when moving it out of the 'compressed' swap. However, this is a classic space-time tradeoff. You effectively get more RAM from the compression, but it is slower than 'normal' RAM due to the CPU time required to compress and decompress the swapped pages.
ClockworkMod: A recovery program that is often used to apply updates, ROMs, or create a back up or restore a backup file
Dalvik: An open source, register-based virtual machine (VM) that’s part of the Android OS. The Dalvik VM executes files in the Dalvik Executable (.dex) format & relies on the Linux kernel for additional functionality like threading & low-level memory management. The virtual machine is register-based, and it can run classes compiled by a Java language compiler that have been transformed into its native format using the included "dx" tool.
Dalvik Cache: A program cache area for the program Dalvik. Dalvik is a java based virtual machine that is the basis for running your programs (the ones that have the .apk extension). In order to make access times faster (because there's not JIT (just in time) compiler installed by default), the dalvik-cache is the result of dalvik doing a optimization of the running program. It's similar to the prefetch files in Windows.
DDMS: Dalvik Debug Monitor Service, a GUI debugging application included with the SDK. It provides screen capture, log dump, and process examination capabilities. If you are developing in Eclipse using the ADT Plugin, DDMS is integrated into your development environment.
Deep Sleep: A state when the CPU is off, display dark, device is waiting for external input.
De-odex: Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file & put it back inside the apk. This allows you to easily replace files (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) & to deodex services.jar, you need to deodex everything.
Dev. or Developer: An individual that creates, or alters a file in such a manner as to advance the program
Drawable: A compiled visual resource that can be used as a background, title, or other part of the screen. A drawable is typically loaded into another UI element, for example as a background image. A drawable is not able to receive events, but does assign various other properties such as "state" and scheduling, to enable subclasses such as animation objects or image libraries. Many drawable objects are loaded from drawable resource files — xml or bitmap files that describe the image. Drawable resources are compiled into subclasses of android.graphics.drawable. For more information about drawables and other resources.
Fastboot: Protocol used to update the flash file system in Android devices from a host over USB. It allows flashing of unsigned partition images.
Flash: Rewrite the software/firmware on your phone using a computer to "flash" or completely rewrite the memory (ROM) of your phone. This is done using ODIN.
Flash Memory: a program technology that can be electrically erased & reprogrammed
Kernel: The main component of Android operating system.
It is a bridge between applications & the actual data processing done at the hardware level.
The kernel's responsibilities include managing the system's resources (the communication between hardware & software components).
[Usually as a basic component of an operating system, a kernel can provide the lowest-level abstraction layer for the resources
(especially processors & I/O devices) that application software must control to perform its function.
It typically makes these facilities available to application processes through inter-process communication mechanisms & system calls.
Operating system tasks are done differently by different kernels, depending on their design & implementation.]
Manifest File: An XML file that each application must define, to describe the application's package name, version, components (activities, intent filters, services), imported libraries, and describes the various activities, and so on. See The AndroidManifest.xml File for complete information.
Nine-patch / 9-patch / Ninepatch image
A re-sizeable bitmap resource that can be used for backgrounds or other images on the device.
Nandroid or Nandroid Backup: A file typically created in the custom recovery program, such as xRecovery, that is a carbon copy of whatever state your phone is in before a drastic change is made. The file then can be moved onto or off of the SD card for later use in case something should go wrong in the ROM or Update, or a Boot Loop occurs
ODIN: It is the program you can use to flash phones.
e.g. : 'Odin Multi-Downloader v3.95' is used to flash the Samsung Galaxy. It's usually included in firmware packs.
OEM: Original Equipment Manufacturer, the people who actually put together electronic hardware. Also refers to any equipment original to the phone, or produced by the company for the phone
OpenGL ES: Android provides OpenGL ES libraries that you can use for fast, complex 3D images. It is harder to use than a Canvas object, but better for 3D objects. The android.opengl and javax.microedition.khronos.opengles packages expose OpenGL ES functionality.
OS: Operating system, I.E. Windows Vista, LINUX or MAC or Android
OTA: Over-the-Air; method T-Mobile, & some other phone companies, uses to update Android phones. The new versions of Android are developed by Google & then released to OEM's, Sony Ericsson in our case. The OEM then writes drivers that enable the new software to work on the phone's hardware. They also develop any specialized UI (user interface), like Timescape & Mediascape, or other software they want to include. Once this is complete, they turn it over to the cell phone company, (e.g.)Tmobile, who then have to do the final checks to make sure the update works, & then distributes it over there data network using their cell transmitters.
Overclocking (OC): Speeding up the CPU past the factory presets to achieve a faster & more responsive device (prolonged run can be injurious to your device, so be careful.)
ROM: Read Only Memory, a program used to make changes to anything from the look of the home screen to icons to custom boot animation
Root: Common word associated with giving a user "super user" access to their phones programming & other various aspects that would normally not be possible, also known as "Jailbroken" for iPhone's, "Administrator Rights" in Windows OS.
Shell or SSH: The shell is the layer of programming that understands & executes the commands a user enters. In some systems, the shell is called a command interpreter. A shell usually implies an interface with a command syntax (think of the DOS operating system & its "C:>" prompts & user commands such as "dir" & "edit"). secure shell or ssh is a network protocol that allows data to be exchanged using a secure channel between two networked devices
SQLite: An embedded relational database management system contained in a relatively small (~275 kB) C programming library. It is multitasking concerning reads. Writes can be done only one-at-a-time. It is a popular choice for local/client storage on web browsers. It has many bindings to programming languages. It is arguably the most widely used database engine, as it is used today by several widespread browsers, operating systems, embedded systems among others
Stock: Simply means an unaltered state, such as when you first purchase your phone fromVerizon/Your Service Provider or when you repair your phone using PC Companion or SE Update Service(SEUS)
SU: "Super user", or root permissions
SWAP: is, in short, virtual RAM. With swap, a small portion of the hard drive is set aside and used like RAM. The computer will attempt to keep as much information as possible in RAM until the RAM is full. At that point, the computer will begin moving inactive blocks of memory (called pages) to the hard disk, freeing up RAM for active processes. If one of the pages on the hard disk needs to be accessed again, it will be moved back into RAM, and a different inactive page in RAM will be moved onto the hard disk ('swapped'). The trade off is disks and SD cards are considerably slower than physical RAM, so when something needs to be swapped, there is a noticeable performance hit.
Unlike traditional swap, Android's Memory Manager kills inactive processes to free up memory. Android signals to the process, then the process will usually write out a small bit of specific information about its state (for example, Google Maps may write out the map view coordinates; Browser might write the URL of the page being viewed) and then the process exits. When you next access that application, it is restarted: the application is loaded from storage, and retrieves the state information that it saved when it last closed. In some applications, this makes it seem as if the application never closed at all. This is not much different from traditional swap, except that Android apps are specially programed to write out very specific information, making Android's Memory Manager more efficient that swap.
Theme: A set of icons, backgrounds & app trays that change the aesthetics of the overall look of the Android & its applications. It has a set of properties (text size, background color, and so on) bundled together to define various default display settings. Android provides a few standard themes, listed in R.style (starting with "Theme_").
TUN/TAP: Refers to a network TUNnel, operates within layer 3 packets, or ip packets. Packets sent by a system via a TUN/TAP device are delivered to a user-space program that attaches itself to the device. A user space program may also pass packets into a TUN/TAP device. In this case TUN/TAP device delivers (or "injects") these packets to the operating system's network stack thus emulating their reception from an external source.
Underclocking(UC): Slowing down the CPU mainly to limit battery usage
Undervolting(UV): Basically keeping the clock speed same (or overclocking it) & reduce the voltage at each cpu cycle.
xRecovery: A recovery program based on the ClockworkMod Recovery sources used to apply updates, ROMs, or create a back up or restore a backup file
File Types:
.dex: Compiled Android application code file. Android programs are compiled into .dex (Dalvik Executable) files, which are in turn zipped into a single .apk file on the device. .dex files can be created by automatically translating compiled applications written in the Java programming language.
.sbf: Summation Briefcase File
.apk or APK's: An .apk file extension denotes an Android Package (APK) file, an .apk file can be opened & inspected using common archive tools. Each Android application is compiled and packaged in a single file that includes all of the application's code (.dex files), resources, assets, and manifest file. The application package file can have any name but must use the .apk extension. For example: myExampleAppname.apk. For convenience, an application package file is often referred to as an ".apk".
.tar: Similar to a zip file(derived from tape archive), a tar file archives multiple files into one file
.tgz: TGZ files (gnu-zipped .tar file) are commonly used as install packages for Slackware Linux.
pheeeeww!!This took sometime!!
Well this is all I can think of off the top of my head but as I think of more I will edit them in here & I encourage the mods to put things that I either forgot or just simply am not aware of. Also I request fellow user to suggest any terms frequently used & not added or any discrepancies found, kindly PM me!!
Thank you & happy hacking/flashing!!
_____________________________________
X10 LED States:-
--------------------------------------
W-LOD: White LED of DEATH.
--------------------------------------
Sometimes a R-LOD is similar to a W-LOD but the LED is red instead.
Usually results in a Reboot, or a Freeze or a Crash
-------------------------------
Flashing R-L: Red LED.
-------------------------------
Led flashes RED 3 times.
Indicates Requirement for Charge
--------------------------------
G-LS: Green LED Steady.
--------------------------------
LED goes Steady GREEN while USB is plugged in.
Flash Mode Entered/Fully Charged.
CPU : -
----------------------------------------
Central Processing Unit: -
----------------------------------------
It's pretty much the heart of your device pumping data through & from all the attached devices the Kernel & Modules is its soul & it's OS is it's skin & flesh.
-----------------------
Core Clock Speed: -
-----------------------
It is the actual clock speed that the CPU is running at. "Not the multiplied speed."
It's good to remember a CPU's performance is also effected by its memory's speed.
Similar rules exist for the GPU (Graphics Processing Unit).
Tnx for the info. This very useful specially to us noobs....
Sent from my E15i using xda premium
Everyone browse this forum must read this at least one time!!!!!!!!!!
Sent from my X8 using xda premium
AOSP: Android Open System Project, usually you will see this term when referring to a program or ROM.
Click to expand...
Click to collapse
AOSP is Android Open Source Project
posted via Tapatalk 2 Beta
Thanks for sharing.
Sent from my E15i using Tapatalk
Improve your battery life tenfold by PureMotive
tested and working at: SGS, Xperia Play, HTC Inc S, the battery life has increased significantly
Original link: http://forum.xda-developers.com/showthread.php?t=1621808http://forum.xda-developers.com/showthread.php?t=1621808
PureMotive said:
Okay guys, I just thought I'd give you my mod for achieving good-great battery life. This is the mod I use in Anthem™ which has given me 50+ hours on a single charge. Feel free to include it in your own ROM or whatever. Please give credit or thanks or both
First: Here is a flashable .zip of the mod that may or may not work with your ROM. I'd still advise doing it manually.
Sysctl.conf - Outdated as of 4/29/2012
Step 1
Open up your ROM.zip (or whatever it's called) in 7zip (Windows) or Betterzip (OSX) and locate
sysctl.conf in /system/etc
If it's not in this directory, create it.
Step 2
In your sysctl.conf file, paste the following code and save it.
Code:
#sysctl.conf file
fs.nr_open=1053696;
fs.inotify.max_queued_events=32000;
fs.inotify.max_user_instances=256;
fs.inotify.max_user_watches=10240;
fs.lease-break-time=10;
fs.file-max=165164;
kernel.threads-max=525810;
kernel.random.write_wakeup_threshold=256;
kernel.random.read_wakeup_threshold=128;
kernel.panic=5;
kernel.sched_compat_yield=1;
kernel.panic=0;
kernel.panic_on_oops=1;
kernel.msgmni=2048;
kernel.msgmax=64000;
kernel.shmmni=4096;
kernel.shmall=2097152;
kernel.shmmax=268435456;
kernel.sem='500 512000 64 2048';
kernel.sched_features=24189;
kernel.hung_task_timeout_secs=30;
kernel.sched_latency_ns=18000000;
kernel.sched_min_granularity_ns=1500000;
kernel.sched_wakeup_granularity_ns=3000000;
kernel.sched_shares_ratelimit=256000;
kernel.sched_child_runs_first=0;
fs.lease-break-time=10;
fs.file-max=65536;
net.core.wmem_max=524288;
net.core.rmem_max=524288;
net.core.rmem_default=262144;
net.core.wmem_default=262144;
net.core.optmem_max=20480;
net.unix.max_dgram_qlen=50;
net.ipv4.tcp_keepalive_time=900;
net.ipv4.tcp_keepalive_probes=5;
net.ipv4.tcp_keepalive_intvl=156;
net.ipv4.tcp_timestamps=0;
net.ipv4.tcp_sack=1;
net.ipv4.tcp_fack=1;
net.ipv4.tcp_window_scaling=1;
net.ipv4.tcp_tw_recycle=1;
net.ipv4.tcp_tw_reuse=1;
net.ipv4.tcp_congestion_control=cubic;
net.ipv4.tcp_syncookies=1;
net.ipv4.conf.all.rp_filter=1;
net.ipv4.conf.default.rp_filter=1;
net.ipv4.tcp_synack_retries=2;
net.ipv4.tcp_syn_retries=2;
net.ipv4.tcp_max_syn_backlog=1024;
net.ipv4.tcp_max_tw_buckets=16384;
net.ipv4.icmp_echo_ignore_all=1;
net.ipv4.icmp_ignore_bogus_error_responses=1;
net.ipv4.tcp_no_metrics_save=1;
net.ipv4.tcp_fin_timeout=15;
net.ipv4.tcp_keepalive_intvl=30;
net.ipv4.tcp_keepalive_probes=5;
net.ipv4.tcp_keepalive_time=1800;
net.ipv4.ip_forward=0;
net.ipv4.conf.default.accept_source_route=0 ;
net.ipv4.conf.all.accept_source_route=0;
net.ipv4.conf.all.accept_redirects=0;
net.ipv4.conf.default.accept_redirects=0;
net.ipv4.conf.all.secure_redirects=0;
net.ipv4.conf.default.secure_redirects=0;
net.ipv4.udp_rmem_min=6144;
net.ipv4.udp_wmem_min=6144;
net.ipv4.tcp_rfc1337=1;
net.ipv4.ip_no_pmtu_disc=0;
net.ipv4.tcp_ecn=0;
net.ipv4.route.flush=1;
net.ipv4.tcp_rmem='6144 87380 524288';
net.ipv4.tcp_wmem='6144 87380 524288';
net.ipv6.conf.default.use_tempaddr=2;
net.ipv6.conf.all.use_tempaddr=2;
net.ipv6.conf.all.temp_prefered_lft=3600;
net.ipv6.conf.default.temp_prefered_lft=3600;
vm.dirty_ratio=90;
vm.dirty_background_ratio=80;
vm.oom_kill_allocating_task=1;
vm.overcommit_memory=1;
vm.page-cluster=3;
vm.drop_caches=3;
vm.min_free_kbytes=4096;
vm.panic_on_oom=0;
vm.dirty_expire_centisecs=1000;
vm.dirty_writeback_centisecs=2000;
vm.oom_kill_allocating_task=0;
vm.vfs_cache_pressure=10;
vm.min_free_order_shift=4;
vm.laptop_mode=0;
vm.block_dump=0;
PureMotive said:
I updated the OP with a new code (Thanks to Tiny). I just removed the semicolons. Use this version if the other does not work for you.
Click to expand...
Click to collapse
If the above code does not work for you, try this one. It has the semi-colons removed. Thanks Tiny
Code:
#sysctl.conf file
fs.nr_open=1053696
fs.inotify.max_queued_events=32000
fs.inotify.max_user_instances=256
fs.inotify.max_user_watches=10240
fs.lease-break-time=10
fs.file-max=165164
kernel.threads-max=525810
kernel.random.write_wakeup_threshold=256
kernel.random.read_wakeup_threshold=128
kernel.panic=5
kernel.sched_compat_yield=1
kernel.panic=0
kernel.panic_on_oops=1
kernel.msgmni=2048
kernel.msgmax=64000
kernel.shmmni=4096
kernel.shmall=2097152
kernel.shmmax=268435456
kernel.sem='500 512000 64 2048'
kernel.sched_features=24189
kernel.hung_task_timeout_secs=30
kernel.sched_latency_ns=18000000
kernel.sched_min_granularity_ns=1500000
kernel.sched_wakeup_granularity_ns=3000000
kernel.sched_shares_ratelimit=256000
kernel.sched_child_runs_first=0
fs.lease-break-time=10
fs.file-max=65536
net.core.wmem_max=524288
net.core.rmem_max=524288
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.optmem_max=20480
net.unix.max_dgram_qlen=50
net.ipv4.tcp_keepalive_time=900
net.ipv4.tcp_keepalive_probes=5
net.ipv4.tcp_keepalive_intvl=156
net.ipv4.tcp_timestamps=0
net.ipv4.tcp_sack=1
net.ipv4.tcp_fack=1
net.ipv4.tcp_window_scaling=1
net.ipv4.tcp_tw_recycle=1
net.ipv4.tcp_tw_reuse=1
net.ipv4.tcp_congestion_control=cubic
net.ipv4.tcp_syncookies=1
net.ipv4.conf.all.rp_filter=1
net.ipv4.conf.default.rp_filter=1
net.ipv4.tcp_synack_retries=2
net.ipv4.tcp_syn_retries=2
net.ipv4.tcp_max_syn_backlog=1024
net.ipv4.tcp_max_tw_buckets=16384
net.ipv4.icmp_echo_ignore_all=1
net.ipv4.icmp_ignore_bogus_error_responses=1
net.ipv4.tcp_no_metrics_save=1
net.ipv4.tcp_fin_timeout=15
net.ipv4.tcp_keepalive_intvl=30
net.ipv4.tcp_keepalive_probes=5
net.ipv4.tcp_keepalive_time=1800
net.ipv4.ip_forward=0
net.ipv4.conf.default.accept_source_route=0
net.ipv4.conf.all.accept_source_route=0
net.ipv4.conf.all.accept_redirects=0
net.ipv4.conf.default.accept_redirects=0
net.ipv4.conf.all.secure_redirects=0
net.ipv4.conf.default.secure_redirects=0
net.ipv4.udp_rmem_min=6144
net.ipv4.udp_wmem_min=6144
net.ipv4.tcp_rfc1337=1
net.ipv4.ip_no_pmtu_disc=0
net.ipv4.tcp_ecn=0
net.ipv4.route.flush=1
net.ipv4.tcp_rmem='6144 87380 524288'
net.ipv4.tcp_wmem='6144 87380 524288'
net.ipv6.conf.default.use_tempaddr=2
net.ipv6.conf.all.use_tempaddr=2
net.ipv6.conf.all.temp_prefered_lft=3600
net.ipv6.conf.default.temp_prefered_lft=3600
vm.dirty_ratio=90
vm.dirty_background_ratio=80
vm.oom_kill_allocating_task=1
vm.overcommit_memory=1
vm.page-cluster=3
vm.drop_caches=3
vm.min_free_kbytes=4096
vm.panic_on_oom=0
vm.dirty_expire_centisecs=1000
vm.dirty_writeback_centisecs=2000
vm.oom_kill_allocating_task=0
vm.vfs_cache_pressure=10
vm.min_free_order_shift=4
vm.laptop_mode=0
vm.block_dump=0
Step 3
Now we need to enable it. So, navigate to /system/etc/init.d and create a file with the following code:
Code:
#!/system/bin/sh
# grep sysctl /etc/init.d/*
# Load /sys/etc/sysctl.conf
sysctl -p
sysctl -p is what initializes the code.
Just FYI: You don't actually need these lines:
Code:
# grep sysctl /etc/init.d/*
Code:
# Load /sys/etc/sysctl.conf
So this would have just sufficed.
Code:
#!/system/bin/sh
sysctl -p
If the above code does not work for any reason, try this:
Code:
#!/system/bin/sh
sysctl -p /system/etc/
Name your file something like this 10sysctl
Save your file.
NOTE: Your ROM must support init.d. You can do this by using dsixda's android kitchen
Step 4
Save your ROM and install it via recovery
OR
you could just push the files into your current ROM and try them out.
Step 5
For operating the script enter the following code in terminal emulator
Code:
su
sysctl -p
is all that is really needed to run the script. So here are some more options:
If you think that init.d is being faulty, enter in terminal emulator
Code:
su
sysctl -p
and then
Code:
sysctl -a| grep vm
What this does is manually start up sysctl.conf and then verify it with the succeeding code.
OR
Ignore what
Code:
sysctl -a| grep vm
is outputting and just see if you experience better battery life (you should)
----------- For knowledge -----------
Credits to imoseyon for portions of the info
Ok, so what exactly is sysctl.conf?
The sysctl.conf is a configuration file for "sysctl" which is an interface for dynamically changing kernel parameters in the Linux OS. The configuration file contains the following elements, vm.min_free_kbytes, vm.dirty_ratio, vm.dirty_backgroud_ratio, vm.vfs_cache_pressure, vm.oom_kill_allocating_task. There are many other elements within the file, but we will be primarily focusing on these specifically (the vm prefix stands for virtual memory). The sysctl.conf file should be located in /etc (/system/etc) by default. To enable it you need your ROM to execute "sysctl -p" somewhere during the boot process (or shortly afterward). We will also be discussing how to enable it if it is not already done so. You can also run sysctl -p manually to enable it any time after the OS is started.
Now, let’s get down to what sysctl.conf does and how it works.
min free kbytes (vm.min_free_kbytes)
This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
dirty ratio (vm.dirty_ratio) and dirty background ratio (vm.dirty_background_ratio)
This controls how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
VFS Cache Pressure (vm.vfs_cache_pressure)
Now here is where it gets interesting! File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
oom allocating task (vm.oom_kill_allocating_task)(enable or disable, generally in Linux this value is either a "1" or a "0," representing as on or off.)
This enables or disables killing the OOM-triggering task in out-of-memory (oom) situations. If this is set to zero, or disabled, the OOM killer will scan through the entire task list and select a task based on heuristics to kill. This normally selects a rogue memory-hogging task that frees up a large amount of memory when killed. If this is set to non-zero, or enabled, the OOM killer simply kills the task that triggered the out-of-memory condition. This avoids the expensive task list scan, which can take mass amounts of time and "hang" or freeze the system.
block_dump (vm.block_dump)
This enables block I/O debugging when set to a nonzero value. If you want to find out which process caused the disk to spin up (see /proc/sys/vm/laptop_mode), you can gather information by setting the flag.
When this flag is set, Linux reports all disk read and write operations that take place, and all block dirtyings done to files. This makes it possible to debug why a disk needs to spin up, and to increase battery life even more. The output of block_dump is written to the kernel output, and it can be retrieved using "dmesg". When you use block_dump and your kernel logging level also includes kernel debugging messages, you probably want to turn off klogd, otherwise the output of block_dump will be logged, causing disk activity that is not normally there.
overcommit_memory (vm.overcommit_memory)
This controls overcommit of system memory, possibly allowing processes to allocate (but not use) more memory than is actually available.
0 - Heuristic overcommit handling. Obvious overcommits of address space are refused. Used for a typical system. It ensures a seriously wild allocation fails while allowing overcommit to reduce swap usage. root is allowed to allocate slighly more memory in this mode. This is the default.
1 - Always overcommit. Appropriate for some scientific applications.
2 - Don't overcommit. The total address space commit for the system is not permitted to exceed swap plus a configurable percentage (default is 50) of physical RAM. Depending on the percentage you use, in most situations this means a process will not be killed while attempting to use already-allocated memory but will receive errors on memory allocation as appropriate.
page-cluster (vm.page-cluster)
This controls the number of pages which are written to swap in a single attempt. The swap I/O size.
It is a logarithmic value - setting it to zero means "1 page", setting it to 1 means "2 pages", setting it to 2 means "4 pages", etc.
The default value is three (eight pages at a time). There may be some small benefits in tuning this to a different value if your workload is swap-intensive.
panic_on_oom (vm.panic_on_oom)
This enables or disables panic on out-of-memory feature. If this is set to 1, the kernel panics when out-of-memory happens. If this is set to 0, the kernel will kill some rogue process, by calling oom_kill().
Usually, oom_killer can kill rogue processes and system will survive. If you want to panic the system rather than killing rogue processes, set this to 1.
The default value is 0.
Panic is a system error that is detected by the kernel.
dirty_expire_centisecs (vm.dirty_expire_centisecs)
How old "dirty" data should be before the kernel considers it old enough to be written to disk. It is expressed in 100ths of a second.
dirty_writeback_centisecs (vm.dirty_writeback_centisecs)
This is the interval of when the writeback daemons periodically wake up and write "old" data out to disk. It is expressed in 100ths of a second.
Click to expand...
Click to collapse
Woah.!!
Sent from my GT-S5830 using Tapatalk
Flashable ZIP
Tenfold huh? should give it a try..
EDIT (updated):
Heres a flashable zip to make things a little easier:
Instructions:
1. Reboot to CWM
2. Mount system
3. Flash
DOES IT WORK?
See for yourself
v2-04/30/2012 [without semi-colons of sysctl.conf (refer Step 2) & removed extra lines of 10sysctl (refer step 3)]
pure AWESOMENESS
Sent from my GT-I9100 using xda premium
Is it working. For ace?????
Sent from my GT-S5830 using Tapatalk 2
Anyone comfirm this working?
added to my future rom
Sure.. after 30min from the first post someone definitely will answer if it extends battery life
Let's see who'll be the first to notice that his bettery last longer
Thanks for sharing this
Is it compatible with CM9?
I installed this on my 2.3.6 based ROM and everything is smooth so far. I also ran the supercharger scripts and all 3 had no errors just in case anyone was wondering if they'd conflict with eachother.
/me Flashed,charging Batt ... ->Start
Testing ...edit with notes follows in 24h ...
Thx 4 sharing
(Edit) for me the battery jumps stopped,its more accurate...but i dont have more battery life.
Verstuurd va men ace via Tapatalk
Installed on 2.3.6 based ROM. Everything went smoothly installing. I ran the V6 turbocharger scripts and it didnt cause any errors to come up in case anyone was wondering.
Sent from my VS910 4G using xda premium
Just installed now, on CM9, Beta 8 by the GalaxyICS team.
Currently charging, and I will show a battery life screenie tomorrow and report on the performance
Downloaded, short term testing looks promising, played angry bird for 30mins, that use to drain like 10% battery, now it's only 6%. Not ten fold but still, improvement from just a file, i'll take that any day, this should come standard on all roms now
Does it works on Lewa rom?
Yes i think it was we need It appears to save battery ... Tomorrow i will do full test with full charge
ok installed 5 minutes back on Lk's I two Rom aka cyanogenmod. no problem but I notified a significant change in speed.. phone feels faster. battery backup dropped two percent in 3 minutes of edge usage. ll update this post after 5 hours.. those who want to install do it without fear its installing no bootloops no errors...
thanks for the share
---------- Post added at 08:01 AM ---------- Previous post was at 07:38 AM ----------
kohrangi said:
Does it works on Lewa rom?
Click to expand...
Click to collapse
Yes it works...
Mmm... testing... im at hospital for 2 days without my charger so... It will come handy if works.
Thanks!
Enviado desde el hospital usando Tapatalk con la mano derecha (soy surdo pero tengo suero)
A question, though: is this version of the mod any different from the original? Because the flashable zip of the original mod is bigger than the one posted here. Just curious. Anyway, I'm going to install the original. I'll come back later with answers.
AlterJack said:
A question, though: is this version of the mod any different from the original? Because the flashable zip of the original mod is bigger than the one posted here. Just curious. Anyway, I'm going to install the original. I'll come back later with answers.
Click to expand...
Click to collapse
Files sysctl.conf are the same. Original sysctl.conf contains one empty line at the end of file - that is all.