Database Develop

Mortscripts for Icon based plugins like ipt,wad, ifonz and others

I wanted to share my Battery percentage script and icons for iphontoday plugin. But I believe it can be used for other UI if anyone tries it on another UI please post. So if you have any icon based scripts please post them here and we will keep them in one thread.
This could not be possible without
Chance63
Sir.John
j101399
MiToNiOeS
Biglittlewhateva
Heres my version of chances mybatterylevel it shows battery percentages 1% at a time.
Updated 8-12-09
1. changed location of battery.png and battery.mscr
2. Added option to have battery folder with icons it on sd card
Please unistall any old version before running new version
Unistall
To remove delete icon of of iphonetoday page then unistall cab then go to device memory and make sur it deleted the battery folder and in device memory if there is a battery.png or battery.mscr then remove it before installing new cab
Download
1. download cab to desktop
2. Unzip cab anywhere on device memory
3. Install cab on device memory it will make a folder called battery and it will place the battery.png and the battery.mscr in device memory no folder
4. If your running iphonetoday UI then follow the next steps
5. Make a new icon image will be battery.png found in device memory no folder
6. EXE will be battery.mscr found also in device memory no folder
7. Uncheck animation and save your done
To run battery folder from SD card follow these steps used for low memory devices
1. download cab to desktop
2. Unzip cab anywhere on device memory
3. Install cab on device memory it will make a folder called battery and it will place the battery.png and the battery.mscr in device memory no folder
4. If your running iphonetoday UI then follow the next steps
5. Download storage.zip
6. Unzip on desktop
7. Copy the battery.mscr to device root over writing the other one
8. Now on device move the battery folder to you sd card
9. You can delete the battery folder off of device memory if you copied it instead of moving it
10. Make a new icon image will be battery.png found in device memory no folder
11. EXE will be battery.mscr found also in device memory no folder
12. Uncheck animation and save your done
For now to show battery charging icon when you plugin phone tap the Icon (We are working on getting this done automatic) When you unplug wait a few seconds and the charging icon will be gone and show the percentages again.
{
"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"
}
The first attachment is the cab has everything in it
The second attachment is icons only zip
The third attachment is the mortscript file

Update 11032010: Version 0.9
My toggle Icons scripts for iPT Version 1.0c and later: using the Reload icons function
I tried to make some use of this function and have done some mort-scripts to toggle:
- Bluetooth on/off
- GPRS on/off
- Irda on/off
- Phone on/off
- Volume on/vibrate/mute
- Wifi on/off
- Screen resolution WVGA/VGA/SQVGA
- IPhoneToday interface itself
plus a script to reload all icons "on demand" I enclose in this post.
The package contains everything required but additionally relies on the following programs to be installed:
## Requirements
- IPhoneToday (obiviously)
- MortScript
- iReflect icons by bluemaxx (or all_icons zip available below)
- WVGAfix3 by cotulla
##in addition the following files are required and up for download in archive "tools_required.zip":
- SetVolume.exe
- VJVolubilis.exe (toggles everything else. Wifi only for WM 5.0)
- Wirelesstoggle.exe (toggles Wifi for WM 6.1)
##Installation
1. copy .zip to PPC
2. unzip archive to a folder of your choice
3. alter sjToggle.ini to reflect the paths to the unzipped binaries and the iReflect icon-directory
4. you may have to alter the shortcuts bluetooth.lnk, wifi.lnk and others to point to the correct directory of VJVolubilis.exe
5. in IPhonetoday create links to the mortscripts (*.mscr) enclosed.
6. (For IPT version 1.1 and lower) Icon names to point to in iReflect-directory are:
- bluetooth_toggle.png
- gprs_toggle.png
- irda_toggle.png
- phone_toggle.png
- volume_toggle.png
- wifi_toggle.png
- wvgafix3_toggle.png
##Version 0.9 - Modifications
- works with IPT version 1.4.x and higher
- no change in functionality otherwise!
### Version 0.8
Sorry for another short-timed update. The idea of adding the possibility to toggle iPhoneToday itself (open/close fullscreen mode) came a bit sudden otherwise I would have included it in 0.7a right away.
Should come in handy, if you want to use your normal today screen as well (for SPB pocket plus for example). Just place a link to ipttoggle.mscr on your today screen and IPT, in startmenu or programs.
### Version 0.7a
- no change in functionality for users of IPT version 1.1 and lower
- added distinction for IPT version 1.2 and higher to make use of the newer and faster single-icon-refresh function
- In this version you find two scripts "reload_all_icons" enclosed. One for IPT version 1.1 and lower & one for 1.2 an higher. Make sure to run the appropriate version for your system
- bugfixes for reload_all_icons.1.2.mscr in version 0.7a: icon-positions sometimes got screwed up with reloading them. Fixed now.
ALL users of 0.62 please read this:
please open wifitoggle.mscr and look for
Code:
# Evaluate WM Version
#
If ( SystemVersion(major.minor) <= 5.3 )
wm6 = 0
ElseIf ( SystemVersion(major.minor) = 5.4 )
wm6 = 1
The values given should be 5.1 and 5.2 instead of 5.3 and 5.4
SORRY!!
##Thanks to MiToNiOeS, tronikos and bluemetalaxe for obivious reasons.
Thanks to mustela7 for pointers on the new version for IPT 1.4.x
Enjoy!
John
To keep the post clearly arranged, I stripped all then older Modification history. If you are interested to track the development over the time, please find the history at the end of file sjToggle.ini now.
dll: 251

Last Update: Version 0.7 as of 18th March 2010
plus a zip-package with 10 sets of Alarm on/off icons (mostly from the iReflect theme of bluemetalaxe)
Hi everybody,
I was a bit unsatisfied with the alarm notification of MiToNiOeS georgous Plugin.
As I use my phone regulary as a day-to-day alarmclock, the notification "there is one future alarm set" aka. no matter whether it is this year or next) wasn't very helpful. I wanted to know whether my Phone will wake me up *tommorrow* (weekdays) or *NOT* (weekends).
Long story short: I did a mortscript to cover my requirements. As I use Klaxon2 by Dutta this script is designed for this alarm clock, but in general, every other alarm application with a registry setting for the next alarm should be addressable.
If anyone wants to provide registry keys for other alarms, I would love to have a look at them. I will need the registry key to the next alarm setting as well as information about when you have set a (sample) alarm, and what notation the regkey is like.
For example: for Klaxon the Regkey in question is
Key: HKCU\Software\Klaxon\NextScheduledAlarmInfo
Value: 15.08.09 15:09:00
for an alarm that obviously goes off at 9 minutes past 3pm on August 15th
###Version 0.7
+ scripts updated to work with iPhoneToday version 1.4.x and higher
- no change in functionality for prior version though
###Version 0.6
+ added possibility to display next alarm time set as icon name. This is for IPT versions 1.2 and higher only.
- no change in functionality for versions 1.1 and lower. As of now, you can just stick to version 0.41
###Version 0.5
+ added distinction between IPT version 1.1 and lower & IPT version 1.2 and up so you can benefit from the faster and smoother single reload function for icons introduced in IPT 1.2 and up
- no change in functionality for versions 1.1 and lower. As of now, you can just stick to version 0.41
###Version 0.4.1
+ script enhancements: reduced number of Sub-Routines to make the script faster
+ added possibility to run the script soley (without starting the alarm_software before)
###Version 0.4
+ added support for MortPlayer's alarm function
+ rewrote the calculation scheme. Hopefully this works now as intended
+ notification bug shall be gone now.
+ notification also shows the time of the next alarm now
###Version 0.3
Version 0.2 was never published, so don't get puzzled
Version 0.3 sees a major update: beside Klaxon, two more alarm softwares are supported now: G-Alarm and PocketWakeUp.
Hence the old name was somewhat outdated and I have gone for a more "general" approach *g*
The zip now contains 3 files:
-sjAlarm.ini: modify your setting in here
-sjAlarm.script: this does the work. Leave it alone.
-sjAlarm.mscr: a wrapper script you can execute. depending on your settings, it first runs *your* Alarm software and updates your icon on exit. This way you can have one icon that display clock and alarm state and onclick starts your alarm software. This means, you can replace your link to G-Alarm, Klaxon etc. with a link to sjAlarm.mscr!! See the screenshots attached for how it may look like.
###Version 0.1
Initial Version
Instead of using an own icon to address the alarm clock, I thought, it would be a neat idea to combine it with the freshly added clock by MiToNiOeS. Therefore I added two empty icons to use for the clock, one of which carries the alarm notification.
Main feature is a configurable timeframe you can specify to check whether an alarm is set or not. E.g. "check if any alarms are due within the next 5 days" as well as a freely configurable update-automatism (manually or every xx minutes)
##Thanks to MiToNiOeS, tronikos and bluemetalaxe for obivious reasons.
Thanks to chancer63 for pointers on the new version for IPT 1.4.x
Enjoy!
John
If you feel like sharing your alarm on/off icons, I'll happily add them to the package
Thanks for more than 150 downloads

All sorts of tiny mortscripts...
A collection of rather simple, yet probably useful MortScripts, which can be used as well as serve as some sort of self-studying learning tutorial. Anyways: Enjoy
############
get_icon_position-function.mscr
No script, but more of a function for fellow mortscripters to evaluate the screen and icon number in IPT where a given mortscript resides.
I wrote this in order to get rid of the neccessity to ask the user to specify "nScreen" and "nIcon". Instead this function, when called, crawls through icons.xml and evaluates the position of the screen and icon where a string you can specify resides.
Set the variable my_scriptname to a string of your choice. This can be a *.mscr file as well as an icon name. (ATTENTION: this is case-sensitive) Then a function called "get_icon_position" is called and stores the value of the screen in question in variable "screen_no" and "icon_no" respectively, which you can set to nScreen, nIcon or whatever.
For some reason this script works, but I have to admit, I had no expierience with LOOPS (with scripting at all for that matter) whatsoever, so I wasn't always completely sure of what I was doing here *LOL* It was quite a long way reading other scripts, of try and error. Hence, such curious value settings like screen_no = -2 for a start.
So if anyone of you scripting-wizards wants to take the time to cleanup my code: your very welcome to ;-)
As this all sounds a bit academic, I'll provide an example use:
Let's say, you have holdemdoggs battery script running and placed the icon on the second screen, as first icon of the second row on a screen with 3 icons per row (see bold no.):
1 2 3
4 5 6
7 8 9
-----
B B B
To set up the function, provide
my_scriptname = "battery.mscr"
as "search-string". When you run the function now it will set the following variable = values
screen_no = 1
icon_no = 3
As IPT starts counting screens and icons with "0" these numbers will correspond with the ones to set as n0Screen and n0Icon for the battery script running on IPT 1.2 an up
Just coming to think of a limitation, that this function still has.
ATTENTION: currently this will not work if the icon resides in the bottom bar.
############
sjBattery ver. 001
A rather different Battery approach, intended especially for old devices with weak batteries. This script is not run periodically but on demand only. Hence, it does not stay in memory and only costs energy and memory when executed.
If executed the script pops up a message for 3 seconds stating the battery left in percent.
As you only need to execute the script (no "chi-chi"), you can perfectly link to it from any icon based launcher using a static battery icon
############
sjMirror ver. 001
When I noticed that there are companies out there that actually CHARGE for an application they call shaving mirror, I decided to script it in case somebody wants / needs it.
sjMirror is a little mortscript that enables the front camera for a one time start of the camera application, and sets everything back to normal (aka backside camera) after use.
Hence, you have a tiny but somewhat neat one-click pocket/shaving mirror application, that does no lasting changes to the registry.
Requirements
well, obiviously a second/front camera on yoour device ;-)
How it works
-> the script sets your front camera as default,
-> starts the camera application and waits till it's loaded
-> sets your normal camera as default again, while camera app is still open
-> and exists
So you can use your front camera as long as you have the application open, but as soon as you close it and restsart it again it'll have your back camera re-enabled.
ver.001 should be the first, stable and last version of that script *lol*
############
sjReset version 0.1
A tiny script to reset your device. You can configure whether you want to be asked before restarting or whether your pocketpc soft-resets without any prior notice. Alter Variable "sure" (0/1) in the script to whatever you favour.
############
ENJOY!
John

holdemdogg said:
I wanted to share my Battery percentage script and icons for iphontoday plugin. .........
For now to show battery charging icon when you plugin phone tap the Icon (We are working on getting this done automatic) ..........
Click to expand...
Click to collapse
Here is a first try:
Code:
#to be up- to- date when switching the phone on, thx to BOBO_01
RunOnPowerOn ("\iPhoneToday\battery\battery.mscr" )
Attention: You changed the script name from "mybatterylevel" to "battery" (and the path as well) so if someone had already installed this script before it's possible that it's still in the NotificationQueue causing trouble. You should remove it with
Code:
RemoveNotifications( "\iPhoneToday\mybatterylevel.mscr" )
.
CU

Sir.John said:
When I noticed that there are companies out there that actually CHARGE for an application they call shaving mirror, I decided to script it in case somebody wants / needs it.
.................
Click to expand...
Click to collapse
...auf was die Leute so alles kommen... *wunder*
Idea: are there two different versions planned: men and women...
CU

chancer63 said:
Here is a first try:
Code:
#to be up- to- date when switching the phone on, thx to BOBO_01
RunOnPowerOn ("\iPhoneToday\battery\battery.mscr" )
Attention: You changed the script name from "mybatterylevel" to "battery" (and the path as well) so if someone had already installed this script before it's possible that it's still in the NotificationQueue causing trouble. You should remove it with
Code:
RemoveNotifications( "\iPhoneToday\mybatterylevel.mscr" )
.
CU
Click to expand...
Click to collapse
oh Thank you very much I didnt get an error or anything because I did a clean install to moniter it for flaws I will add this as soon as I get home.
Again theres no way this script wouldve worked without all your hard work on the original script.

I just noticed an "oddity". The batter script folder contains 100+ icons, two of which are name battery.png and battery0.png. Those are blank battery and 0%. I was just about to re-enable the script and went to point the icon to the blank and it was gone, replaced by the 0% icon image. I now have two 0% icons but one is named battery.png. WTF?
Somehow the icon for blank battery is being replaced by the 0%er. It is overwriting the image but leaving the name intact.
I think I figured it out. Here is how to recreate it on your phone...
While the script is running and a battery image other than blank is showing, disable the script (edit icon, remove link to script, save). Now go and check the image that is called battery.png. My guess is, it will now have the image of the last image displayed. I just did it with 100% displayed and now the battery.png image is 100% instead of blank. The name remained the same. I also did it while on charge and it replaced blank with charge png.

I'm not sure whether I got this right, but what you describe seems not to be and oddity rather than "works as designed"
Explanation:
as the link to the icon fro iPT is static per definition the only chance to alter the image is to replace the the picture the icon links to. Hence you link to "battery.png" which gets constantly overwritten (and the display refreshed) according to the actual value...this may be "copy battery0.png battery.png" or "copy battery100.png battery.png".
Or did I get you completely wrong?

Biglittlewhateva said:
I just noticed an "oddity". The batter script folder contains 100+ icons, two of which are name battery.png and battery0.png. Those are blank battery and 0%. I was just about to re-enable the script and went to point the icon to the blank and it was gone, replaced by the 0% icon image. I now have two 0% icons but one is named battery.png. WTF?
Somehow the icon for blank battery is being replaced by the 0%er. It is overwriting the image but leaving the name intact.
I think I figured it out. Here is how to recreate it on your phone...
While the script is running and a battery image other than blank is showing, disable the script (edit icon, remove link to script, save). Now go and check the image that is called battery.png. My guess is, it will now have the image of the last image displayed. I just did it with 100% displayed and now the battery.png image is 100% instead of blank. The name remained the same. I also did it while on charge and it replaced blank with charge png.
Click to expand...
Click to collapse
Seems like a made an error on the script and the placement of the icons I included them in the same folder. The battery.png updates with the current battery level. Then if you make any changes like remove the icon then place it back then it can be confusing on wich icon to pick im going to change the location of the battery .png and the script and see if it helps out I'll be uploading it soon. Sorry for the mistake give me about an hour or so and I'll have it done

@ Sir.John, I believe you got it right.
@ holdemdogg, sounds good. I'll be back in a bit. Gotta walk the dog.

Hello,
I tried to do the same script as Sir.John (jkklaxon) but for G-Alarm.
I think (thanks for your comments/reports) I have only a bug when an "programmed alarm" is 'ON' (only working days or other...). I think it's completely functional for quick alarms.
Thanks for comments and thanks Sir.John for his script.
The scripts are made for :
- three icons in \iphonetoday\icons\
- two scripts in \iphonetoday\lnk\
- take jk_alarm.png for clock (with type = "clock") and execute = "G-Alarm.mscr"

Hi
if I'm not mistaken you check for
HKCU\Software\ageye\g-alarm\$ID\OneTime
and for a string that reads YY.MM.DD.HH.MM.SS
is that correct?
Where will programmed alarms be stored in registry?
Is it possible to post a screenshot or an export of g-alarm registry key?
kind regards, John

Sir.John said:
Hi
if I'm not mistaken you check for
HKCU\Software\ageye\g-alarm\$ID\OneTime
and for a string that reads YY.MM.DD.HH.MM.SS
is that correct?
Where will programmed alarms be stored in registry?
Is it possible to post a screenshot or an export of g-alarm registry key?
kind regards, John
Click to expand...
Click to collapse
Yes you are right. You can have several alarms stocked.
Yes, i try to join an export of G-Alarm (for me for the moment the script is very well )

Thanks heaps, this is helpful. (my pity: You need to get up as soon as me btw ;-))
Would you mind to post an reg-export of a programmed alarm as well? Perhaps we can sort something out to read these alarms in correctly as well.
For both excerpts you posted (IDs 0 and 1) a "OneTime" string was set, so I assume these two are quick alarms, no?
John

[EDIT] Shoot I realized my icons were not updaating, I fixed the code and uploaded the script file. XDA time 03:56pm
This is a great place to put these ++1 for starting the thread
Here is my version of chancer63's battery script, just like holdemdogg said, thank you goes out to chancer63 for starting that battery script idea. This version of the battery script runs every 15 minutes during normal daytime hours and every hour and a half during the night. It also displays when charging (you have to tap the icon to start it, unless you want to wait). When charging, it updated every 60 seconds. I have also built in a "kill" for the old location of the script, so help avoid errors.
To install;
Download and unzip the file
Copy the file into your iPhoneToday folder
Create an icon, and set the image to \iPhoneToday\battery\battery.png and set the executable to \iPhoneToday\battery\mybatterylevel.mscr. Now tap the icon and the script will do the rest. Please note that when you 1st start it, the level will be 100%; it will update in a few seconds from there.

I wanted to repost this here; I also have not tested it, but going to soon:
chancer63 said:
For problems with the NotificationQueue I found this:
http://www.nicque.com/PQz/OmapClockRemover.htm
BUT I couldn't try it yet, so be careful please.
CU
Click to expand...
Click to collapse

Normally the file "1" is a programmed alarm for working days.
I will try to program a quick and a "programmed" alarm ASAP and export the reg.
EDIT : Programmed alarm is in file "1" and quick alarm is in file "2".

SWeet, thanks for all your efforts
edit: need to go home now, first. But will have a look at your output tonight.
John

Running battery percentages from storage card
I'm rewritng the script now so peeps can put there battery folder (the one with all the icons) on there storage card to save space I should have it done in a few. This should help with low memory devices

[ROM]Fission 2.5.7 DroidX - Vanilla Generic Android - AOSP Like - Fission ROM Manager

A flashback to when ROM was first booted ... the good ol' days.
Team DeFuse Presents
Vanilla Android 2.5.7
Only use themes made for 2.5.5+ if you want to keep lots of new features in Fission!!!​
Video Install Guides for Fission ROM Manager can be found HERE. Thank you darkonion for making the vids
Text version of instructions located below.
{
"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"
}
About Us & ROM:
The first generic Android platform for current and future Droid devices. We are a bunch of mad hackers, modders and developers that were not happy with the current model of Droids being "Blurred" so we began a mission to rid our devices from the blurriness of VZW Android systems. It started with a crazy idea of messing with the Droid2 SDK that has turned into a full fledge AOSP generic type of ROM. We have incorporated many features that were only seen in AOSP ROMs before this. Some of the features include Reboot in Power Menu, custom built Framework, vanilla Android GUI, totally blur free app folder and many more AOSP like features to come in the short term future.
Features:
True Vanilla ROM with generic Android feel, not themed to look line one. No blur apps...
Reboot in Power Menu.
Custom Framework - 10% battery increments with display percent number & without.
Overclock ready out of box.
Lots of free memory.
ROM has root and has been deodexed, and zip alligned.
Busybox installed and symlinks have been applied.
Clean base for you to customize how you like.
And many more...
Fission ROM Manager:
Fission ROM Manager (FRM) is a utility we developed to make modifying your Droid phones much easier. It was designed for the new Android user but also very useful for the more advanced user. You can download ROMs, themes, updates add ons and much more. Once your downloads are done you can install everything within Android. No need to go into recovery any more.
HotFix:
Check Fission ROM Manager for 2.5.5 HotFix. Brings it up to 2.5.6
Team DeFuse Members:
Developers
AngDroid - Team Leader, Project Manager & Developer
braway - Developer
Drod2169 - Developer
Requiem4D - Developer, IT dude & Kernel Specialist
IRC & Forum Support
WalCs - Support Manager - Developer Assistant
Themers
javroch
MJones1052
barracuda
Joe772
tgwaste
StuntinX
draya1986
Web Design & Maintenance
WebKaiser
Jcatt
Web:
Team DeFuse
IRC:
IRC Server - Freenode.net
Chanel #teamdefuse
Twitter:
@Team DeFuse
@AngDroid
Themes:
Check Fission ROM Manager. Many themes are up.
Changelog:
2.5.6 -> 2.5.7
New settings package
New contact package
2.5.5 -> 2.5.6
Cleaned up framework.
DX - Fixes Calendar bug
2.4.3 -> 2.5.5
Tweaks to framework, AOSP Sliders with Rotary Lockscreen option. Can change lockscreen options by using Lockscreen app in app draw. Thanks to kejar31 for the help in pointing me in different direction to get them done!
Custom contact ringtones may be fixed, key word being “may”.
USB Tethering enabled, need tether plan for it to work. Working on free hack
Notepad as been updated to latest version.
Do not use any themes that are not made for 2.5.5.
Themers…just update to the new framework, nothing else has changed.
DX Builds coming later today and then D2 Global builds.
2.4.2 -> 2.4.3
Removed Sound and Speach Recoder
Added new Sound Recorder that can be launched from App Draw
Added 10% Battery Display option to FRM. Will reset current theme back to Stock Fission.
2.4 -> 2.4.2
DX build gets new framework whcih should fix the random USB reboot when plugging in.
All previous fixes are now included
Latest Android Market
More Code Cleaning
Full version ROMs and Upgrades are available. Upgrade will only replace packages. It will not wipe app or framework folder.
No reason to wipe cache or data if coming from Fission ROM for either Full ROM or Upgrade.
2.2.1 -> 2.4
All Devices are now equal. Perform and look the same.
Framework improvements all around. Colors, placement of graphics...lots of little changes.
Almost all apps for each device have been rebuilt from source. Either from AOSP source or Moto source.
Each device now has device specific apps. Will help of future Blur add on. Many people been asking for many different Blur apps so there will be an add on Blur package. Blur package will be heavily modified Blur services and then each app will be an individual add on.
MMS menu compose graphic now fixed.
Phone mute fixed.
Rebuilt Moto Apps (MediaGallery, Cam and Music) are now standard. They work better and will help with Blur add on. Generic Android Apps will be available on FRM.
All devices now use Moto Multi-Touch keyboards. They are themed as Generic Android Keyboards.
More cleaning of code and tweaks...
Few other changes I can not think of right now
Small bug with Global ROM. If you need to activate, slide out keyboard and hit the number key you need to use.
No need to wipe data or cache if coming from previous Fission ROM; however the installer will wipe your system folder so back up any changes you have made to your system folder.
DO NOT USE 2.3.1 Themes. They will work but you will lose lots of changes. Themers are working hard now to update themes.
I must say these are the best Fission ROMs so far. Lots of love and hard work went into them.
Install Instructions:
All install instructions can be found on Team DeFuse Website.
Bug Reporting:
Please use Our Google Code Project Home to report bugs. You can find it HERE.
Search before posting bug. The bug may have been reported and fixed.
Donations:
Thanks to everyone who has donated. If you would like to contribute to our cause you may do so by clicking HERE, thank you very much.
Downloads:
Droid 2, Droid 2 Global, Droid X, Droid Pro & Fission ROM Manager - DOWNLOAD
By clicking the download link and proceeding to download page, you agree to that you have read everything in this post.
Click HERE if you agree.
Thanks!

Themes
Themes
Some are included with ROM.

Installed percentage from fusion folder and not showing up in notification bar. Am I doing something wrong?
Sent from my DROIDX using XDA App

Working great! No problems here.

zehkaiser said:
Working great! No problems here.
Click to expand...
Click to collapse
Same here...great job!!

Running 2.1 since friday now. Low +1.1MH , no prob at all. Even with Javroch's BlackOut theme for 2.1. works great

Cell standby battery usage
ang, quick question. Cell standby is still showing massive battery use, as well as 50% time without signal. You said before it is just a visual bug, but I wanted to ask what makes you think do, because my battery life still seems to be suffering with these roms. Love them generally, but am getting much worse battery life than I had before. Used to get 24+ hours.
Thoughts? Thanks for the sweet rom.
Anyone else report the best battery life they are sering under normal usage? I can sometimes drop 10 or more percent in less than 45 mins.

Loving it so far! Great work!
Sent from my DROIDX using Tapatalk

blueb0x said:
Installed percentage from fusion folder and not showing up in notification bar. Am I doing something wrong?
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
is your battery fully charged? it doesnt show 100%. only shows 90% or below.

lordloki77 said:
ang, quick question. Cell standby is still showing massive battery use, as well as 50% time without signal. You said before it is just a visual bug, but I wanted to ask what makes you think do, because my battery life still seems to be suffering with these roms. Love them generally, but am getting much worse battery life than I had before. Used to get 24+ hours.
Thoughts? Thanks for the sweet rom.
Anyone else report the best battery life they are sering under normal usage? I can sometimes drop 10 or more percent in less than 45 mins.
Click to expand...
Click to collapse
i'm getting outstanding battery life with 2.1 final. and i've seen a few others say that too. i'm not seeing the cell standby issue either. Did you do a 2.2 sbf prior to installing? did you follow the install instructions? there's a couple new important steps that were added today.

So far so good, just need to look for that addon file from the last version that added batt % to notification bar.
Edit: did that earlier but reason it wasn't working earlier was cause I was installing the 10% followed by the regular framework; canceling it out. I got too excited.
Sent from my DROIDX using XDA App

blueb0x said:
So far so good, just need to look for that addon file from the last version that added batt % to notification bar.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
it's in the /fission/addon folder on your sdcard.

lordloki77 said:
ang, quick question. Cell standby is still showing massive battery use, as well as 50% time without signal. You said before it is just a visual bug, but I wanted to ask what makes you think do, because my battery life still seems to be suffering with these roms. Love them generally, but am getting much worse battery life than I had before. Used to get 24+ hours.
Thoughts? Thanks for the sweet rom.
Anyone else report the best battery life they are sering under normal usage? I can sometimes drop 10 or more percent in less than 45 mins.
Click to expand...
Click to collapse
I did some Googling and apperently this is a common issue. People seem to be split on if its actually effecting battery life. The battery manager fcs and the fact that it doesn't happen every restart make it harder to pin down.
Since I do believe it effects my battery life if I reboot my phone I immediately put it into airplane mode for a second a then take it out. That solves the 50% problem and I don't think its ever spontaneously started without me rebooting the phone.
Sent from my DROIDX using XDA App

lordloki77 said:
ang, quick question. Cell standby is still showing massive battery use, as well as 50% time without signal. You said before it is just a visual bug, but I wanted to ask what makes you think do, because my battery life still seems to be suffering with these roms. Love them generally, but am getting much worse battery life than I had before. Used to get 24+ hours.
Thoughts? Thanks for the sweet rom.
Anyone else report the best battery life they are sering under normal usage? I can sometimes drop 10 or more percent in less than 45 mins.
Click to expand...
Click to collapse
It is just a visual bug, been confirmed many times from different users. Did you follow install instructions? I am having no problems with battery life as many others.
This is what my battery manager looks like...

coolj478 said:
I did some Googling and apperently this is a common issue. People seem to be split on if its actually effecting battery life. The battery manager fcs and the fact that it doesn't happen every restart make it harder to pin down.
Since I do believe it effects my battery life if I reboot my phone I immediately put it into airplane mode for a second a then take it out. That solves the 50% problem and I don't think its ever spontaneously started without me rebooting the phone.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Should've added that I am seeing excellent battery life. Going on 20 hours and only lost 30%. I still get fcs on the battery manager. I can fix it by wiping battery stats but the fcs eventually come back.
Sent from my DROIDX using XDA App

coolj478 said:
Should've added that I am seeing excellent battery life. Going on 20 hours and only lost 30%. I still get fcs on the battery manager. I can fix it by wiping battery stats but the fcs eventually come back.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
The battery manager app does FC every now and then with me too. Braway and I are working on tracking it down. We have a few ideas to what is causing it so it might be able to get fixed.
I heard it does it on the stock ROM too, can anyone confirm that?

Anyone here experiences the the DX_Keyboard doesn't show up after installing from the SD_Card. I remember this has been fixed in the RC3 patches. Also tapping the phone icon from the launcher doesn't open up the dial keypad anymore. There is no phone icon in the app draw neither. Any advice?

Angdroid said:
The battery manager app does FC every now and then with me too. Braway and I are working on tracking it down. We have a few ideas to what is causing it so it might be able to get fixed.
I heard it does it on the stock ROM too, can anyone confirm that?
Click to expand...
Click to collapse
I used stock rom 2.2 for a long time and have not encountered any FC issues. I think you should perform a factory reset and do not restore data from any backup software.

Angdroid said:
The battery manager app does FC every now and then with me too. Braway and I are working on tracking it down. We have a few ideas to what is causing it so it might be able to get fixed.
I heard it does it on the stock ROM too, can anyone confirm that?
Click to expand...
Click to collapse
I used stock 2.2 (moto blur) on the droid x and can confirm it happened all the time.
Sent from my DROIDX using XDA App

Ok so with 2.1 Final...do I still have to install the vanilla framework file inside the addon directory to get 10% battery increments? (all I want is the increments, I don't care for the visual on the battery itself) Thanks.

[HOW-TO] Work-arounds for issues with stock Nook Color ROM

Since the same questions seem to be getting asked a lot, here are some methods for getting past stock NookColor ROM limitations in a single thread:
1. How do I keep wifi from turning off when the screen goes to sleep?
- download Spare Parts from the market and set wifi sleep policy to never.
. . . mixed results have been reported with this method, but this appears to be the best known fix at the moment.
2. I restored and re-rooted, now I can't log in to my B&N account!
- get NookColorTools app (if not installed during root, it's on xda). Under All Settings, open the 2nd (of 3) setting called Wireless near the bottom. This will begin their registration process again.
3. How do I install a different keyboard?
- if it's in the market, first purchase/install it-- if it's a stand-alone apk, skip that and move on to the next paragraph. If you just downloaded it from the market, find the apk somewhere in data/app/ and copy from there.
Now place the app's apk (Root Explorer works great) in system/app (mount system as r-w first). Look at the file's permissions (long hold on it and choose Permissions from the menu), and match it to the permissions of the other files in that folder. Reboot. Then open your trusty NookColorTools, select keyboard, and you should be able to switch to it. Not all keyboards are currently working, but this is a great way to find out if it does that doesn't require renaming or deleting your current keyboard.
4. How do I get Swype on here?
- right now, you can't. Swype requires a copy that matches your device's resolution, and the only version of Swype that matches ours (1024x600) is the copy that ships with the Galaxy Tab, but, to my knowledge, nobody has gotten it completely working on here without causing major system crashes (not to mention the apk couldn't be posted on xda even if it was eventually hacked to work).
SlideIT keyboard is another trace keyboard that DOES work on the NookColor, and I've been very happy with it (it's come a long way since I tried it last summer and quickly uninstalled it). The method in #3 above should work to install it.
5. Wait, I can't copy and paste on the NookColor??
- not through the OS, no. There is a solution though. It involves getting an app called Copy Paste It from the market (paid, but there's a trial version). You'll probably need to set it to rotate clockwise (in settings), or it'll get screwy.
When you want to copy, activate the function from the notification, and it'll let you frame the text to copy:
{
"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"
}
The second part, pasting, requires having a keyboard with a Paste setting in it. Again, SlideIT has this on the special characters keyboard (I'm not a troll for SlideIT, just a happy customer). I'm not sure which other keyboards have this feature, if any (if you know, post, and I'll update this). Assuming you have a keyboard with paste, it'll paste what the Copy Paste It app copied.
6. Why is everything on my screen so small?
- this is because the NookColor's stock LCD density is 169.333, which is pretty low (Galaxy Tab is 240). Unlike resolution, which is hardware-based, density is software-based and can be changed. If you search the market for LCD density, there are a couple apps that will do this--a free one that won't survive a hard reboot, and a paid one that (supposedly) will.
If you want to make it permanent for free, you can edit your build.prop file. Again, use Root Explorer to open system/build.prop (BACKUP FIRST!), find the following two lines:
ro.sf.lcd_density.xdpi=169.33333
ro.sf.lcd_density.ydpi=169.33333
If you wanted your density to be 250, you'd replace them with the following single line:
ro.sf.lcd_density=250
Save the edited file, and reboot.
Here are two of my Galaxy Tab-esque homescreens set to 250:
. . . Now, jacking up your LCD density much above 200 will make your status bar look wonky and cut-off. One solution for this is to set it to 250, like above (by changing build.prop - I think the apps I mentioned only allow multiples of 20), which will make it look clean (as long as wifi is on). The only problem there is that you'll lose your status bar clock and Notifications in portrait mode . . .
. . . the solution for THIS is to get two apps: hellostatusbar, and quick launch. Set quick launch to open hellostatusbar on a home- button double press, and it will display your Notifications.
Also note that raising the density can cut-off parts of the stock Barnes & Noble software (they're designed for the lower density), so this mod is probably better for people like me who use the Kindle app and ezPDF for reading.
7. If I don't want to use softkeys, can I remap the hardware buttons to do something different?
Yes. In Root Explorer, navigate to system/usr/keylayout, make a backup of TWL4030_Keypad.kl, then open the original with text editor and change the entry for key 115 ( volume up) and/or key 114 (volume down) with something like BACK, MENU, or SEARCH. Save the file. Reboot, and they'll be whatever you changed the entry to.
If you want easy volume controls after remapping these buttons, a market app called Volumer++ can be set to live in your notifications for easy access. Otherwise, you can change them from settings.
8. How do I set my wallpaper so that the resolution looks good?
- I used a market app called Wallpaper Set & Save. It's easy, and resolution looks great. I think it cuts off the image a little bit, but not much. I think this method will suffice for many people, but if you want it to be sized perfectly, do the following (credit to swapdotavi for the instructions):
[Get an image that is at least 1200x1024, crop it (without scaling) to 1200x1024. If you're using Photoshop, copy the entire image, then create a new file sized 1200x1024. Then paste the image and use the arrow to drag it around to whatever looks best to you. Save the file as a .png, transfer to your nook, and use Wallpaper Set & Save to choose the new file.]
. . . Since we share the same resolution with the Galaxy Tab, the wallpapers that came with it look phenomenal (in my opinion) on the NookColor. Follow this link to pick them up:
http://galaxytabwallpapers.net/original-galaxy-tab/
9. Can I change the lockscreen slider to look like stock Android or Sense?
- yes - get an app called WidgetLocker. Set it to look how you want. Then, under Behavior, set Homehelper as your system home. Still under Behavior, go to Home to Launch, and pick your real launcher (Launcherpro, ADW, etc.). Also, under Advanced, be sure to check both the Root Bypass of 5 Second Rule, and Retain Keyguard.
10. My NookColor seems sluggish - is there a way to speed it up?
Most of you will already know this, but Setcpu is a market app that can speed things up and improve battery life. CPU Tuner is a free alternative that's similar, but I've had more experience with setcpu, and can vouch much more for it.
My recommended settings:
Min 600
Max 800
Governor: OnDemand*
check 'set on boot'
... And one profile enabled:
Screen Off
Min 300
Max 600
Governor: Ondemand
... And another optional setting (for even a little more extra zip):
under Advanced:
change "Up Threshold" to 35
* for the fastest setting, set the governor in the main CPU setting to Performance (with 800 max). It may drain your battery quicker, but mine still holds up surprisingly well on performance--and the nook is very fast.
These are just settings that work for me. Feel free to experiment. Also, some people were having their Nook randomly reboot, and changing the governor from conservative to ondemand helped.
11. Any other battery-saving tips?
In case you missed the rival xda threads arguing over who thought of it first, there was a potentially useful battery-saving trick in there:
Go back in Root Explorer, and in system/app, mount as r-w and rename Phone.apk and TelephonyProvider.apk to anything else (adding .bak onto the end would be fine).
Basically, you're removing android system files that may be wasting juice looking for a non-existent cell service. It's unsure if or how much this actually improves battery life, but it very well could, and it certainly won't hurt anything changing their names.
12. Why aren't my favorite live wallpapers working?
I'm not sure, but here's how to get the rest of them going:
Download this file: http://db.tt/ur0c98s
It will fail installing, but if you use Root Explorer, copy it from your download directory, go to system/app, set as r-w... Then long-press on any file in that directory, and look at its permissions. Now paste your LiveWallpapers.apk there and change its permissions to match the others. Your live wallpapers should work now!
The Nexus wallpaper won't work, but just install Nexus Revamped from the market - it's identical, it's free, and it has customization.
If you're using one of the more system-intensive Live Wallpapers (like "Water"), I'd recommend using all of the Setcpu changes from #10 above to keep things snappy (also know that LWP's can drain battery quicker).
13. How can I get my Google contacts in here?
If you aren't concerned with them showing up in the B&N Contacts app, and are more interested in having them come up as auto-suggestions when typing an email address or Google Voice text number, there's a way (credit to jadambpharm):
- Go to gmail on the web, click on contacts (left side), then More Actions, then Export. Choose .vcard format. Transfer that file to your SD card.
- get a Market app on your Nook called Import Contacts. Point it to the contacts.vcard file you just got, and they'll now come up for auto-fill suggestions!
14. How can I prevent the Nook from automatically updating the firmware?
- Change the name of etc/security/otacerts.zip to anything else (doing this in Root Explorer works fine). So far, this had looked pretty solid in successfully disabling OTA updates.
15. Why won't YouTube play videos in HD?
For some reason, the YouTube that's installed from rooting won't do it. To get a version that plays HD:
- uninstall your current YouTube via Titanium Backup
- download this version from the Evo (credit aludal): http://db.tt/y5vVvI2
- rather than installing this one, rename it youtube.apk and copy it into system/app (w/permissions matching the other apk's in that folder)
It should be there now, ready to play HQ clips. If not, reboot first.
I'll update as I think of more. Enjoy your modestly-priced, unintentional Android tablets!

Reserved 10 chars

How about "What size should wallpaper images be?"
I suggest this because I dont know

swapdotavi said:
How about "What size should wallpaper images be?"
I suggest this because I dont know
Click to expand...
Click to collapse
I didn't resize them manually, I just used an app - will update OP in a minute with that, and again later when I get the chance to research manually setting them . . .

I don't know either, but I've had good luck with searching for 'wallpaper' on Google images with size set to 1024*1024 and then using 'set as wallpaper' from dolphin browser HD.
Sent from my NOOKcolor using XDA App

pest789 said:
I don't know either, but I've had good luck with searching for 'wallpaper' on Google images with size set to 1024*1024 and then using 'set as wallpaper' from dolphin browser HD.
Sent from my NOOKcolor using XDA App
Click to expand...
Click to collapse
The Galaxy Tab wallpapers I've used all look phenomenal too. Same resolution, so its tailor-made. Easy to find them with a google search.

For some reason changing the lcd density didn't do a damn thing through build.prob after reboot. What did I do wrong?
Edit:
And I did save it before rebooting so I'm not sure what I did wrong...

wvcachi said:
3. How do I install a different keyboard?
- if it's in the market, first purchase/install it-- if it's a stand-alone apk, skip that and move on to the next paragraph. If you just downloaded it from the market, find the apk somewhere in data/app/ and copy from there.
Now place the app's apk (Root Explorer works great) in system/app (set system as r-w first). Reboot. Then open your trusty NookColorTools, select keyboard, and you should be able to switch to it. Not all keyboards are currently working, but this is a great way to find out if it does that doesn't require renaming or deleting your current keyboard.
Can you please explain the 'set system as r-w'?
Thanks
Click to expand...
Click to collapse
Click to expand...
Click to collapse

@beejis - make sure you're losing the xdpi and ydpi parts and merging it into a single entry. Look closely at the example in the OP. Also, make sure you're editing the entry that isn't commented out (don't bother editing the lcddensity entry with a # in front of it) a few lines earlier. If for some reason that didn't work, then use the free app from the market to change it.
@k8108 - if you're using Root Explorer, it's a little button up top when you're navigating system/, which lets you toggle mounting system as 'read-write' and 'read-only.'

Beejis said:
For some reason changing the lcd density didn't do a damn thing through build.prob after reboot. What did I do wrong?
Edit:
And I did save it before rebooting so I'm not sure what I did wrong...
Click to expand...
Click to collapse
Comment out these lines (add # to beginning):
# ro.sf.lcd_density.xdpi=169.3333
# ro.sf.lcd_density.ydpi=169.3333
Add this line:
ro.sf.lcd_density=254
I already had a line similar that I uncommented, and I run mine at 254.
169.3333 / 2 = 84.6666
169.3333 + 84.6666 = 254
I am probably overthinking it, but it looks good. You can make that number 250 if you want.
The Program LCD Density lets you select specific densities as well, but is only soft. Nice for testing.

k8108 said:
Can you please explain the 'set system as r-w'?
Thanks
Click to expand...
Click to collapse
http://nookdevs.com/NookColor_Making_system_partition_Read-Write
From adb shell, run this code:
Code:
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system

ThrowingKs said:
http://nookdevs.com/NookColor_Making_system_partition_Read-Write
From adb shell, run this code:
Code:
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
Click to expand...
Click to collapse
...I got the impression he was using Root Explorer, in which case it's a little button that says r-w.

I have used the free market app to change the lcd density and it makes most of the interface fantastic except for a couple things. As noted the status bar doe mess up but that I am not worried about but the screen density change to, 250 in my case, really screws up the formating of my nook library and shop. I use them quite a lot to read newspapers and such so if anyone else has this experience let me know how/if you deal with it.
Sent from my LogicPD Zoom2 using XDA App

foethalove said:
I have used the free market app to change the lcd density and it makes most of the interface fantastic except for a couple things. As noted the status bar doe mess up but that I am not worried about but the screen density change to, 250 in my case, really screws up the formating of my nook library and shop. I use them quite a lot to read newspapers and such so if anyone else has this experience let me know how/if you deal with it.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
Good point - I'll note that in the OP. I don't use the B&N stuff, so it's easy for me to forget that not everyone on xda is in the same boat.

Where does the SlideIT.apk go after you install it from the market? I can't put it in the system/app folder because i can't find it. Any ideas?
NookColor+ XDA 4 ever

cgtombstone said:
Where does the SlideIT.apk go after you install it from the market? I can't put it in the system/app folder because i can't find it. Any ideas?
NookColor+ XDA 4 ever
Click to expand...
Click to collapse
Look in data/app, and find the file named com.dasur.slideit.apk. Copy/paste that into system/app (hit r-w first of course), then reboot and switch keyboards via NookColorTools.

My bad I was searching for it in root explorer and I gues the search function was skipping the data folder for some reason ( or I'm missing something). Thanks anyway.
NookColor+ XDA 4 ever

Thanks bookmarking this thread

wvcachi said:
I didn't resize them manually, I just used an app - will update OP in a minute with that, and again later when I get the chance to research manually setting them . . .
Click to expand...
Click to collapse
Ah perfect did not see your update. I see you found Set and Save, but you mentioned you might update with exact size instructions later. I actually went and did a bit of research, so maybe I can save you some time
To get an perfect wallpaper using 5 screens, like in ADW:
- Get an image that is at least 1200x1024
- Crop (dont scale) it to 1200x1024. A really easily way to do this is open the file in Photoshop, copy the entire image, then create a new file that's exactly 1200x1024. Then just paste the image and use the arrow to drag it around to whatever looks best to you.
- Save the file as a .png
- Get it on to your nook. (SD card transfer, email and download, whatever)
- Open Wallpaper Set & Save
- Point it towards the folder you have your wallpapers in
- Select the wallpaper you want
- Hit apply
Bam. Perfect wallpaper, no stretching, no compression. Looks great! I'll post screens later today if I remember
I used a 1920x1200 wallpaper I had on my PC, cropped it, emailed it to myself, then used Set & Save to place my wallpaper. It's really crisp.
edit: And thanks for the lock screen information! Going to do that tonight; sick of the stock screen

MOD, can we get this stickied? Lots of good info!

Lower Auto-Brightness Settings for DEODEXED FROYO / GINGERBREAD Sense ROMs

Hi all,
I'm a LeeDroid HD user, and I've spent some time over the last few weeks tweaking the auto-brightness settings to maximise battery life. I've reached a point where I haven't found any problems with my settings for 4 or 5 days now, which I think is a pretty good test. It's on the low side under most light conditions, but I've tried to find a point where I can comfortably read the screen without holding it up to my face, and when outside, this includes wearing sunglasses.
Obviously screen brightness is a very personal thing, so you might not like where I've ended up. When you want to impress your friends with your awesome DHD, you can always override the auto setting and just crank up the brightness control manually
Sharing my settings is also not simple either, since it requires a mod to res-framework.apk, which is used for themes. So ... what I will do is show you a graph of my changes to so you can see what I'm doing:
{
"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"
}
(Left side of graph is a dark room, right side is the harsh West Australian sun)​
And make a flashable zip available for Lee's default ROM, with no themes installed (Base_LeeDroid_Lower_Auto_Brightness_Patch).
And another flashable zip to use if you've installed the "LeeDrOiD Notification power widget" from the LeeDroid HD OP (LeeDroid-PNW-Lower_Auto_Brightness_Patch).
And I've already had a request to make one for the "Stock 1.84" theme from here, so that's also attached (Stock_1.84-Lower_Auto_Brightness_Patch).
If you have another theme/mod installed, I think that flashing the above will wreck it ... be warned!
If you have a specific theme/mod you're using and want to try my settings, just send me a link to it and I'll cook up a flashable zip for it ... it doesn't take long. Alternatively if you know what you're doing, I can provide my arrays.xml file and you can do it yourself.
ALL files in this post are to be flashed with cwm 2.5.1.3 ... I haven't tested with any other version.
Even though I've tested all these patches myself, I'm not an expert at this, so PLEASE PLEASE PLEASE take a nandroid backup first in case I've done something fundamentally wrong.
If you don't like my settings, you can either restore your nandroid backup, or if it was a theme specific patch, you could just apply the theme again.
If it all goes pear-shaped ... I TAKE NO RESPONSIBILITY!
Hope somebody (other than myself) can benefit from my experimenting
If any themers want to incorporate my settings, it's just a change to arrays.xml inside framework-res.apk, nothing else. I'll also attach my arrays.xml (zipped), feel free to use it. As a courtesy, please credit me for the auto-brightness settings If you use them.
As mentioned above, if anyone would like to patch this on top of a specific theme/ROM you have already flashed, just ask and I can cook it up. If you feel like making it easier for me, all I need is framework-res.apk, so if you have a link to just download that, you'll get your patch quicker than if I have to download the entire theme
If anyone has arrived here from the LeeDroid thread, be aware that these are NEW versions of the files, as the ones in that thread were based on the wrong version (they were too low in the 40-90-160 range).
Cheers all, any feedback is appreciated
I have since put together a DIY guide on how to mod the auto-brightness settings inside framework-res.apk yourself. Thanks to those who contributed. Here's the guide!
This was all done on myWindows XP SP3 machine.
1. Download and install a recent Java Runtime Environment (JRE), if you don't already have one. I won't go through those steps, google it. If you're unsure, you can always come back to this step later if it's not working.
2. Download APK Manager from here: http://forum.xda-developers.com/showthread.php?t=695701 ... there's probably lots of good info in this thread if you have questions later about this tool.
3. Unzip the file wherever you want, mine is just on my desktop.
4. I was advised to replace the version of apktool.exe in the 'other' folder with an earlier version. I don't know if this is necessary, and I don't know what version I now have ... possibly 1.3. ** Multiple people have needed to downgrade to the older apktool.exe that I use, so I have attached it to this post. Just extract apktool.exe from the zip and place it in the 'other' folder, replacing the existing apktool.exe.
5. OK, now you should be ready to go! Grab your framework-res.apk either from your phone, or straight from the ROM you've flashed if you haven't applied any themes. framework-res.apk can be found in /system/framework.
6. Copy your framework-res.apk into the "place-apk-here-for-modding" folder.
7. Run script.bat. If you see a text menu pop up then all is good. If you get an error then you've done something wrong! Probably related to your JRE.
8. Choose Option 9 - Decompile apk. Wait until it finishes. Minimise this window now, we'll come back to it later.
9. Go into your projects folder, and you will have a new folder there called framework-res.apk, double click it.
10. Navigate to res/values
11. Open up arrays.xml in a text editor such as Notepad++. Using Windows built in notepad app could cause issues due to Windows -> Linux compatibility issues.
12. Scroll down to the section where it says "<integer-array name="config_autoBrightnessLevels">". This is the section that defines the steps of the ambient light sensor. You probably won't need to adjust these values for now.
13. The next section down should be "<integer-array name="config_autoBrightnessLcdBacklightValues">", this is where the tweaks really begin. The values here relate directly to how bright the screen is at the steps defined in the section above. Minimum value is 1, maximum value seems to be 249, but that could be incorrect. Would make more sense for it to be 255.
14. Change these values as you wish, but change them to the same thing in all these 3 sections - config_autoBrightnessLcdBacklightValues, config_autoBrightnessLcdBacklightValuesUp, config_autoBrightnessLcdBacklightValuesDown.
15. The next 2 sections - config_autoBrightnessButtonBacklightValues, and config_autoBrightnessKeyboardBacklightValues do the same thing, except for the hardware buttons, and keyboard buttons (if present) respectively. Adjust these if you wish.
16. Save the file.
17. Navigate back to the root of the APK Manager directory.
18. Return to your APK Manager window.
19. Choose option 11 - compile APK.
20. When prompted if this is a system APK, type y. Hit Enter.
21. When prompted if you want to copy additional files, type n. Hit Enter.
22. Choose option 22 - Set Current Project
23. Choose option 2 - unsignedframework-res.apk
24. Choose Option 5 - Zipalign apk
25. Choose Option 24 - Quit. On my script version you have to choose option 24 twice. I assume it's a bug on my version, hopefully you won't have to do the same thing.
26. Congrats! You now have a modded framework-res.apk!! You'll find it in the folder "place-apk-here-for-modding", with the new name "unsignedframework-res.apk". Copy it somewhere else (eg. desktop) and rename it to framework-res.apk.
*** If you know how to copy the modded file into a pre-existing flasheable zip, then by all means go for it. If not, continue following the steps below to create a flashable zip in the UOT Kitchen ***
27. Go to the UOT Kitchen - http://uot.dakra.lt/kitchen/ Hopefully it's not busy and it lets you in! If not, you'll have to wait.
28. Go to the file upload tab and upload your new framework-res.apk file.
29. If this is a FROYO ROM that you're modding, then that's it! If it's a GINGERBREAD ROM, then you also have to grab SystemUI.apk and com.htc.resources.apk from your ROM or phone and upload these also. SystemUI.apk can be found in /system/app and com.htc.resources.apk can be found in /system/framework
30. Go back to the Summary tab, then click "Submit Work to Kitchen".
31. When it's done, download the file, boot into cwm, ***DO A NANDROID BACKUP***, then flash your file!
If you've done it right, you're auto-brightness settings should be applied!
If you get stuck in a boot loop, or it just doesn't boot at all ... lucky you have a nandroid backup!
Please note that as this thread progresses, newer versions of the files get posted which makes these ones in the OP redundant. I'll leave them up for now just in case someone needs them, but in general, you'll want to dig deeper into the thread to get flashable files for newer versions of ROMS.

Excellent post.
I will take a look at your final arrays.xml, but I'm happy (so far) with the one I've cooked up with modified at the dimmer end of the scale.
Over the next day or so, I'm going to try and add extra steps (double) into the array, making a more linear or at least a smoother curve. As you said in Lee's thread, not sure if it's up to the build of the kernel.
Even if I can successfully add the extra values and flash, maybe I won't notice if its really working and the values are applied or they are just ignored by the ROM or kernel? What's the worst that can happen? Backup...........

Using the GPS Status & Lux Meter I was able to double check the phone light sensor invrements in:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>

UpInTheAir said:
10-40-90-160-225-320-640-1280-2600-10240 (pls correct me if I've missed any out)
Click to expand...
Click to collapse
That looks right to me, I've not noticed any others in my testing
UpInTheAir said:
Would the 'driver' for the light sensor need to be modified for extra steps (ie. 10-25-40-70-90-125-160-...........) and then the array?
Click to expand...
Click to collapse
Yep, I believe that's right. New drivers would need to be compiled into the kernel, and then the array modified accordingly. This is still something I'm not 100% sure on though, since their could also be a hardware limitation here.
UpInTheAir said:
Any idea how this correlates to the array.xml?
<integer-array name="config_autoBrightnessLevels">
<item>21</item>
<item>42</item>
<item>84</item>
<item>159</item>
<item>336</item>
<item>672</item>
<item>872</item>
<item>1281</item>
<item>2601</item>
Click to expand...
Click to collapse
The way it works is, if the light sensor returns a value of 10 (which is < 21), then it returns the first value of the array. If it's 40 ( 40 > 21 and 40 < 42) then it'll use the 2nd value ... and so on. that's why there's one extra value in the backlight values arrays than there is in the brightness level arrays, because it's the in betweens, plus less than the first value, plus greater than the last value.
Does that answer your question? Or did I mis-understand?

Thanks for the reply. Confirmed what I had thought.
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system. I run W7, so that's no an option right now. It still is a little beyond my scope of knowledge, but I'm learning bit by bit and also a lot of reading what others have said and researching Mr. Google.
Another useful app is Sensor List, which can graph the changes in lx, but the values are the same as above.
Looks like I'll be keeping this PC when I eventually upgrade so I can run Linux on it to play around...........

UpInTheAir said:
Been looking up on how to de-compile the kernel, but most tools seem to point to lynux system.
Click to expand...
Click to collapse
No need to de-compile it dude ... Lee publishes his kernel source code on github!
https://github.com/LeeDroid-/htc-kernel-ace
As for making changes and then re-compiling it ... I have no idea either

Thanks, will check it out and see if I can find out anything useful.
I don't really want to bother Lee as he's either quite busy or having some well deserved time 'off' before the official GB release.
It's not that big a deal to me (as you said, could be hardware limitation, so no chance anyway), but more of having a play, seeing where things are and what happens and why.

Hi mate,
Sorry, I'm late...
Great thread.
Just few questions:
The value I got (have ever seen) in my GPS status are: 10-40-90-160-220(5)?-640-10240
I have not seen these readings: 320, 1280 and 2600.
So, do I need to download and flash arrays.xml.zip first?
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
I had a thorough test on the one slopppy posted for me in LeeDrOid's thread. I works great except when the reading is at 40. At 40, the brightness is lowered to minimum. I know this as the button light has lit up. (My phone got 40-90-160 under fluorescent light, so if brightness is lowered to minimum at 40, it means it goes too low [for me].) Apart from this, everything works fine.
Sitting in the car under the sun, the brightness works well. Screen is readable even with sunglasses on. Walking out from the car, under direct sunlight, brightness still works fine.
Like what I said before, may be we should not be too particular about how it works under the sun as it maybe too bright an environment for our eyes to notice the difference.
So bro slopppy, what should I do now if I want to try them out now?
Regards!

So, do I need to download and flash arrays.xml.zip first?
Click to expand...
Click to collapse
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
What is Base_LeeDroid-Lower_Auto_Brightness_Patch.zip, your initial modified version?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid but no themes/battery mods etc on top of it
What is LeeDroid-PNW-Lower_Auto_Brightness_Patch.zip then?
Click to expand...
Click to collapse
That's the patch you use if you installed LeeDroid and then installed the "Notification Power Widget" from the OP of the LeeDroid HD thread.
Stock_1.84-Lower_Auto_Brightness_Patch.zip means I can use it with my battery mod, right?
Click to expand...
Click to collapse
Yep, this is the one you should flash mate
works great except when the reading is at 40. At 40, the brightness is lowered to minimum.
Click to expand...
Click to collapse
I think that 40 isn't a value I come across in my daily life! haha ... I've only ever seen it when I mess around with the sensor to try and make it hit different readings. Couldn't hurt to up it a little I guess.
So bro slopppy, what should I do now if I want to try them out now?
Click to expand...
Click to collapse
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go

slopppy said:
Woooaaaaaaah, slow down .... no, no that's not for patching! That's just if anyone wants to use these values in their own themes.
...
You should download and flash "Stock_1.84-Lower_Auto_Brightness_Patch.zip". You don't need to do anything else, it will just replace my previous one that you patched. Try it first, since it's different from the one you already have, but I think you might find the same issue. If so, I'll boost the backlight a little at 40 for you.
Let me know how you go
Click to expand...
Click to collapse
Thanks mate. Will do a thorough test again for this.
Value 40 is when I'm sitting at the corner and the phone facing away (opposite) the light. My eyes did not notice any much difference in brightness but my phone's sensor did.
Thanks more for the last sentence of your previous post... (maybe push it up a little to 8%-10%? frankly, me too not sure whether it will suit me more... my suggestion, 40 - 8-10%, 90 - 10-12% and 160 - 12-15%)
Edit: Oh, luckily I'm patient enough to wait for your reply this time...lol

Quick feedback for indoor test:
My personal opinion:
at 40, the brightness is a lowered to minimum and button light turn on, hence, a little too low.
at 90, didn't notice any difference in brightness. However, the button light turned off. So there must be an increment but not noticeable to my eyes. Still too low. (the one posted for me in LeeDrOid thread doesn't have this issue)
at 160, a little (really little only) too bright. Few percent reduction is better.
Will again update my feedback for outdoor test.
Regards!

HoneyHD Theme.
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813

What about Kalagas theme...i would be very appriciate

Is this for Froyo only because i can't find arrays.xml inside GB framework-res.apk

Yes, sloppy should be a bit more specific, but in his defence, he does mention in the first post cwm recovery 2.5.1.3,...... relative only to LeeDrOiD Froyo.
Sent from my Desire HD using XDA App

Yep, good point, sorry about that. It's for Froyo SENSE ROMs only.
Anyone know how I can modify the title of the thread??
I'll get on to the requests now.
Cheers,

hamurabi1 said:
What about Kalagas theme...i would be very appriciate
Click to expand...
Click to collapse
Which version of Kalagas theme are you running? There seems to be a zillion of them

kennykenneth said:
is it possible to make one for Honey Hd Theme,
http://forum.xda-developers.com/showthread.php?t=1028813
Click to expand...
Click to collapse
Hi,
The framework-res.apk from Honey HD doesn't want to play ball. It gets a couple of errors when I decompile it, then totally flips out when I try to recompile it. It's an intense theme ... maybe he's doing some things which are incompatible with the way I'm going about my changes.
You could always see if the developer is nice enough to cook you up a version using my arrays.xml from the OP. He has other changes in his arrays.xml as well, so he would have to make sure he just uses the auto-brightness section.
Sorry mate!

slopppy said:
Which version of Kalagas theme are you running? There seems to be a zillion of them
Click to expand...
Click to collapse
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].
Thank you!

hamurabi1 said:
I am running this version:
Full Kalagas_Mixed_Theme_LeeDroid_HD [v2.0 09/03/2011 - compatible with LeeDroid HD 1.5.0/1.5.1/2.0.0/2.2.2/2.2.3].!
Click to expand...
Click to collapse
Here you mate
As stated in the OP, please do a nandroid backup first ... better safe than sorry ...

[Guide]The Quest for Better Battery Life on Your S5

Hello guys and gals! Been a while since I've started a thread heh. So let me start off by saying this thread is a collection of both tweaks I've found through my incessant tinkering and apps I've come across throughout the last few years. That being said the apps I will cover are the work of the developers who created them and all credit goes to them.
Settings Tweaks:
One of the first things I do on any Android phone is enable Developer Options under system settings (you do so by tapping build number under about phone 7 times). There is a specific group of settings in there that can help give you more screen on time with less battery drain.
{
"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"
}
Window animation scale, Transition animation scale, and Animation duration scale can all be turned off. Without having to draw these animations constantly your screen will consume less power, and may even seem snappier.
I know there are very mixed reviews of Smart Stay, but I feel like it can only help. Samsung has also included some settings to adapt the brightness and color based on the onscreen image in order to save battery. I assume that can only help our cause. Disabling the screen to wake on all buttons except power can also save wasted battery from your screen turning on in your pocket (there are xposed modules that can do this or you can get into editting key layouts with a root browser).
Lastly, as far as user level things for helping with more screen on and less power use, keeping your wallpaper on grayscale or dark images and using dark theming really helps as drawing light colors on the screen uses more energy.
Power Saving Tools:
The first on the list is a heavy hitter, the app Greenify. I cannot stress enough how crucial this app is. It allows you to put set apps into Hibernation, stopping them from running in the background and eating your memory and causing wakelocks preventing deep sleep. It has a great built in auto-hibernation option in settings which I highly recommend enabling.
I also suggest supporting the developer and buying the pro version. It enables some experimental features which backbone on the Xposed framework, allowing you to hibernate system apps, which proves very useful for running services that don't need to be 24/7.
Paired best with Greenify is any one of the large selection of battery monitoring apps. The best one in my opinion is GSam Battery Monitor, it gives you a detailed breakdown of what is using your battery so you can hone in on sources of drain. BetterBatteryStats and Wakelock Detector are a couple more of my favorites.
Tasker is quite possibly one of the best apps out there. Another one I highly suggest to support the developer and buy the pro version. You can set up automation tasks to control your phone without lifting a finger. In order to get the results we're trying for it will also need the plugin app Secure Settings.
I have 3 profiles that are relevant. The first 2 are linked, Home Mode and Away Mode. Home Mode sets all of the settings shown above in the At Home task when WiFi detects that it is near my home network. When WiFi detects it is NOT near my home network, the settings change to what is shown in the Away task image above. Allowing Tasker to control the aspects will help make sure your phone is more battery friendly when you are away from a power source.
The third profile is a simple Shake to Greenify, which hibernates all set apps through Greenify by a good shake of the phone.
Even though we cannot overclock due to the locked bootloader, don't forget about the option to underclock which can greatly save power. I use SetCPU to run 2 profiles, one which slows the CPU to a crawl when the screen is off preventing any apps from going too crazy with cpu wakelocks. The other profile gives the full range of voltages when the screen is on. I prefer to use OnDemand as my governor to save cpu power for when I need it.
Last on the list is Lux Auto Brightness. The free version does just fine; this app controls your light sensor far better than the native auto brightness setting, and the different update modes give you different options as to how you want the brightness adjustments handled.
With this list of tweaks and helpful app usage, I encourage you to test and try different things to find what works best for you. Hopefully I have helped in your quest for better battery life. Cheers!

Can I safely hibernate any of these system apps?
Thanks for the detailed info, I am always looking for better battery stats!

I would Greenify Quick connect, S Finder, and ROM Mart. If you need to use the app it will exit hibernation once you go into it.

What all do you have greenifyed? I don't wanna greenify something and mess up my phone, I have an AT&T S5.

Basically anything coming up in Greenify showing wakelocks and long run times gets Greenified.

So one I greenify something will I have to regreenify it if I use the app again?

No, once you Greenify it it will hibernate any time you trigger the hibernate all option, either by shortcut, shake, or auto-hibernation. When you use the app it will wake up, and will re-hibernate when hibernate all is triggered again.

I originally saw your post in the Dynamic Kat thread, two days with four hours of screen time is amazing! Is there anything else that you can tell me (apps or settings) that will increase my battery life? I've done everything you said in your guide. I usually get 13hr of battery with two hr of screen time.

Stephenparrigin said:
I originally saw your post in the Dynamic Kat thread, two days with four hours of screen time is amazing! Is there anything else that you can tell me (apps or settings) that will increase my battery life? I've done everything you said in your guide. I usually get 13hr of battery with two hr of screen time.
Click to expand...
Click to collapse
I personally use power savings mode and restrict the processor and turn on gray scale. I get around three days generally, but I don't use my phone nearly as much as my tablet.

whmgreen said:
I personally use power savings mode and restrict the processor and turn on gray scale. I get around three days generally, but I don't use my phone nearly as much as my tablet.
Click to expand...
Click to collapse
The only time I use powersave mode is when I'm out and my battery is less than 25 percent. At work I usually listen to music for at least 4 hours, and at night I usually play games for at least 2 hours. The only other things I can recommend are freezing a crap ton of system apps in Titanium Backup. Also, any games that you have that give push notifications will hang out in memory, so disabling notifications will help keep them from waking up. And it goes without saying that bluetooth, gps, wifi, and mobile data should stay disabled until you need them, and turned back off after you use them. Regularly check BetterBatteryStats and Gsam Battery Monitor to see what's using your battery the most and nip it in the bud.

You also need to know that smartphone batteries these days are smart as well. They learn your usage patterns and adjust accordingly. When I first got this phone my average battery life was 12 hours, and after about a week it lasted a lot longer. Then after flashing DK my battery life went straight into the toilet for about 3 days until it re-learned. You have introduced a bunch of new changes to your phone, so it may take a few days or even a week to fully adjust to everything. It can also never hurt to go to safestrap and clear your cache and dalvik cache.

Here was first day testing out Sm-G870A. Mostly just WiFi usage this day. Might have got 10 hours.
Straight out of box.
Here few days later with kool_active.
Samsung unlock bootloader on SM-G870A ...

XRange said:
Here was first day testing out Sm-G870A. Mostly just WiFi usage this day. Might have got 10 hours.
Straight out of box.
Here few days later with kool_active.
Samsung unlock bootloader on SM-G870A ...
Click to expand...
Click to collapse
That is impressive my friend! For the sake of the Guide do you use any of the same techniques I employ or do you have other methods you could give to aid in the quest?

Just froze most if not all bloat. Set screen on least brightest inside house. Add u can see WiFi & mobile signal where full strength. So that might had some to do with it. Mobile was on AT&T Micro cell that day also. Use most stuff as everyone else, xpose, gravity box, greenify, tb to freeze bloat.
Samsung unlock bootloader on SM-G870A ...

Oh man been looking for better ways to safe battery and bam just found them .. Thx man awesome article .. as big fan of tasker i have totally forgot about that app ... Could you post tasker profiles?

wizardslovak said:
Oh man been looking for better ways to safe battery and bam just found them .. Thx man awesome article .. as big fan of tasker i have totally forgot about that app ... Could you post tasker profiles?
Click to expand...
Click to collapse
I'm always willing to help! I will post full breakdowns of my battery saving ones only though to stay on topic in the thread. Any thing not battery life relevant can be shared through PM

Also glad you enjoyed the guide!

d34thbl00m said:
Also glad you enjoyed the guide!
Click to expand...
Click to collapse
thx again..

Feel free to post screenshots of the battery I've helped you save!