Database Info

[UPDATED 24.03.2011] X10 Theme Reference

24.03.2011: Added a link to the themes section and added my last post here for a while (maybe ):
_calum_ said:
So I'm back after dropping off the face of the planet for a while I've been getting into WP7 development and so my X10 has been in the top drawer for a couple of months... I may get into Android development soon but at the moment I'm a bit short on time (as always ).
I still would like to get the timescape animations sorted (I hate being beaten ) but I just can't seem to get the cheecksum figured out. If I ever get them sorted I'll update this post again, but until then I probably won't do anything more with my X10.
I hope this post has been helpful. See ya
Click to expand...
Click to collapse
This thread was opened to consolidate the information/knowledge about themes for the x10. It is basically a reference thread with key bits of information and links so that a new user can find all the necessary information in one place. At the moment this is spread out all over the place, there are a lot of different threads with different bits of information, and the lack of updates in Draken Korin’s sticky makes it pretty hard to find new information. It should also help us avoid the old ‘where the hell was that image…?’ and ‘where was that … thread again?’.
Please PM me or post any useful information that is missing, especially the OPs of the threads in the Themes section below. I will continually update this thread with any new information or links.
All useful information that is posted here will be added to this first page, so that you don't have to wade through pages of posts to try and find something. Everything after the first page should therefore either be repeated on this page somewhere or is just conversation. Please yell at me should this not be the case
Please help me out by posting information, ideas etc.
Creating Themes for the x10:
1. Getting Started
2. Using ADB
3. Creating a theme
4. Modifying XML files and adding resources
5. Modifying Services.jar
6. Timescape/Mediascape
7. Resource locations
8. Theme collection
9. Recovery tips
Change log
14.11.2010 - Added section 4
18.11.2010 - Updated section 3 with a complete guid for modifying .9.png's
25.11.2010 - Updated section 7 with text color locations in the xml files
21.12.2010 - Added a link to MrRusch's tool to section 4
24.12.2010 - Added link to 2.1 Sources to section 5

Getting Started
Before getting started on a theme you'll need to set a few things up. Here's a list of everything you'll need:
Root. Your phone will need to be rooted
Java SDK (JDK). You'll need to install the JDK (and JRE) before you can start modifying the contents of your phone. Check out this video of Chewitts if you're having problems on x64 systems.
ADB (from the Android SDK). You need ADB to push/pull files to and from your phone (see the next post)
X10 Drivers. The drivers are usually installed if you install SEUS. Sometimes however you may need to do a manual installation (from my experience mainly on Win7 x64 machines).
The easiest way to make sure everything is set up properly is to install someone elses theme. Check out this post (1.6) or this post (2.1) for instructions.
After you've done all that take a look at this.

Have you installed someone elses theme yet? If not then go directly to jail, do not pass GO and do not collect £200
Using ADB
There's an ADB Guide here (thanks to XPeriaX10iUser for having this in his sig ): ADB, Fastboot, and Nandroid for Noobs
Before you start need to unsecure the shell. Use the following adb commands to do this if you haven't already (to reverse it do chmod 0755... thanks XperiaX10iUser ):
Code:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
chmod 4755 /system/bin/sh
This is all described in the links posted in the Getting Started section above
Thanks to MrRusch for making our lives easier with this tool. For those of you new to this, you should still read the guide linked above so that you know what is actually going on.
Here's a step by step for pulling the framework from your phone and pushing it back. The original post is here. The boot animation mod at the bottom is for 1.6. In 2.1 it is found in system/media/bootanimation.zip.
@gavriel18: I hope it's OK to use this here, if not then let me know.
gavriel18 said:
Step 1:
Connect phone to pc, enable usb debugging and open adb. Type:
adb pull /system/framework/framework-res.apk framework-res.apk
That will pull your framework-res.apk to whatever folder is displaying in your command line.
Step 2:
Find the framework-res.apk on your hard drive, right click and open with 7zip.
Step 3:
Use png's here or create your own and dump into the appropriate folder within framework-res.apk.
Step 4:
When you are done editing the files open up adb and type the following command:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb push framework-res.apk /sdcard/framework-res.apk
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
That will put the new framework-res.apk on your phone. It should automatically reboot (if not reboot it) and your changes should be applied!
When running the script above you can replace framework-res.apk with whatever you want. For example, Timescape.apk
Remember, it is CASE sensitive I made this problem many times)
If you would like to pull an entire folder put a slash at the end of the last word. For example, adb pull /system/etc /etc"/" (no " in actual script )
Courtesy of corruptfate is the steps to modify the startupshow (post #207)
step 1: open adb shell
step 2: type "adb shell"
step 3: type "su"
step 4: type "mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system"
step 5: type "mkdir system/etc/semc/startupshow"
step 6: exit and redo step 1 - 4
step 7: type "mkdir system/etc/semc/startupshow/default"
step 8: exit and open command prompt again, this time type "ddms"
step 9: look for the default folder in system > etc > semc > startupshow > default
step 10: push the images into that folder
Click to expand...
Click to collapse

Creating a theme
So, now that we’ve got the framework-res.apk onto our hard drive, we can take a look at creating a theme. The only skill that is really required to change the appearance of the framework (this is the system file that contains the notification bar, settings etc.) is being able to edit .png image files to suit your tastes. If you can do this then it is just a matter of knowing how to extract the images, and how to update the .apk with them after editing.
.9.png's
Before we start we need to take a look at a special kind of image in android apk’s: the .9.png’s. These are recognisable, as the name suggests, by the double extension *.9.png.
.9.png's are images with a bit of extra information embedded. They contain information on how they can be stretched, and where the content can go (e.g. for a button background, which area of the background can contain the text).
This information is contained in a single pixel border (the guides) around the image and can be added using draw9patch. The catch here is that the guides must be compiled into the image before it can be used.
The Border: For the most part, you will not have to edit the border of a .9.png because, as long as you follow the guide below, the guides will already be in the image and you will not need to change them. If you do need to create your own (I’d assume you know enough not to be reading this though ), you can find more information here.
Editing the Framework
In this example we will look at editing framework-res.apk. However, the process can be used on any apk.
The method described below may seem overly complicated for those who have experience in this area, but it is (in my opinion) the easiest ‘sure-fire’ way to make sure you don’t have any problems (especially with the .9.png’s).
In rare cases, when the .apk your modifying doesn’t have any .9.png’s (e.g. the Recent Calls widget) then you can skip straight to the ‘Updating images using Drag/Drop’ section below.
Requirements:
You will need the following:
7zip apktool - this is included in the attached file themes.zip
Some people use WinRAR instead of 7zip, but apktool uses some 7zip commands internally so make sure it is installed (I think, I know this is the case for APK Manager, I still need to test this for apktool, but hey, just use 7zip, it's free and works exceptionally well).
Setting up:
In the attached zip file (themes.zip) you will find a copy of my theme creation environment. It’s not too complicated, it only contains a couple of folders so I know where everything is, three key batch files (all one-liners) and apktool.
The first thing we need to look at is install_framework.bat. This contains the following line:
Code:
java -jar apktool.jar install-framework stock\framework-res.apk
All this does is tell apktool to install the framework on your system. The resources from stock\framework-res.apk will be extracted to a default location. If you don’t do this then you will not be able to recompile other apk’s that rely on the framework (you will get a ResourceNotFound error).
The other batch files decompile and build the framework, these are the ones that need to be modified if you start working on a different apk:
Code:
[B]decompile.bat[/B)
java -jar apktool.jar d stock\ framework-res.apk working\ framework-res
[B]build.bat[/B]
java -jar apktool.jar b working\framework-res out\framework-res.apk
I have included the stock X10 framework. If you use on of the other frameworks out there you may find that you get a lot of errors when trying to recompile. That’s because someone got lazy with the .9.png’s
As we are modifying the framework directly we do not need to run install_framework.bat, for a different apk (e.g. Phonebook.apk) you may need to run this first to avoid errors when decompiling.
Decompiling and Building:
1. Run decompile.bat. After this you will see that the working folder is filled with the contents of the apk. The images we need to modify are in the subfolders res/drawable-hdpi and res/drawable-land-hdpi. If you look at some of the .9.png’s in there you can see the guides (see the attached image). This makes it really easy to edit them, you can just edit them like any other image (as long as you do not touch/alter the guides).
2. Edit any images that you want. For the .9.pngs I usually make a copy without the 1 pixel border so that I can edit the entire image, then I paste the copy back into the middle of the original .9.png. You don’t have to worry about the guides, they are already set correctly.
I have created a tool that takes the stock x10 status bar icons, removes the background and sets them to a colour of your choice here. This was made to make my life easier by minimizing the time I spend in photoshop.
3. Run build.bat. This compiles the framework, embedding the guide information into the .9.png’s. The output framework is in the out folder. Do not push this to your phone as it is incomplete and the resources.arsc is stored incorrectly. If you do push it to your phone then you get to reflash
Now you can just drag the edited images out of the generated framework onto your hard drive and use steps 4. and 5. of the Drag/Drop method described below to update your framework.
Updating images using Drag/Drop:
1. Open the .apk in 7zip and browse to the appropriate image folder (almost always the res\drawable-hdpi folder)
2. Drag/Drop the images you want to edit to your hard drive. Leave the .apk open in 7zip
3. Edit the images in your favourite program (photoshop or similar)
4. Drag/Drop the images back into the .apk that is still open
5. Use the process described in the previous post to push the framework back to the phone
The reason that the .apk is left open in this process is that some (all?) of them are signed and updating them in this way doesn’t mess with the signature. I’ll admit to not being 100% sure about this, I’m sort of thinking now that people just had problems re-packing due to files being compressed that shouldn’t have been (see the section on editing XML files and adding resources to see what I mean). Please correct me on this one.
This also [almost] goes without saying, but: Make a backup before you start (you can look at the installer for Chewitts Dark10 theme to see how to do this).
OK, now you can start messing with the appearance of your phone, have fun
Credits
Thanks to Mr_Element for the help testing this process and making it easier to follow
Thanks to damnitpud for his post here, without which I would still have been a bit lost in draw9patch.

Modifying XML files and adding resources
First up, thanks to MrRusch for pointing out that the resources.arsc was being zipped differently. It would have taken a few more flashes to figure out how to pack it into the apk without that little nugget
Secondly, thanks again to MrRusch for this post. Using apktool 1.3.1 means the resources are not compressed, but you still can't just flash the resulting framework. So either use MrRusch's tool or follow the instructions below.
The XML files in the framework-res.apk (and the other apps) are stored in a compiled form, making them impossible to edit without decompiling them. The process of decompiling them and recompiling is reasonably simple but care is required if any images/resources are added to the apk.
Modifying the xml files opens up certain things that can’t be changed by just modifying some image files. The best example is changing the battery icon in the notification bar to show a different image for each percentage instead of just 10%, 20%, 40% etc.
When you modify xml files and add resources to your apk, make sure you copy ALL the modifications made to the stock apk each time after compiling. I have noticed strange effects if I don't do this such as the wrong images being used - I am assuming that in the newly compiled resources.arsc the image references/IDs change when compiled, but I'm not really sure yet. An example of this is when I tried to add the signal strength mod mentioned above to a framework that included the battery icon mod below. This only worked if I also copied the battery mod files to the framework (even though they were already in the apk) after recompiling the signal strength mod. If I just copied the files required for the signal strength mod then the battery indicator would start showing the wrong images (see here, specifically posts 52, 56 and 57).
Battery Icon:
Here is a step by step for modifying the battery icon in the framework. To do this you will need to download apktool and install 7zip (other compression programs may work, but I’ve only used 7zip).
Decompile the framework using the following command:
Code:
java -jar apktool.jar d framework-res.apk framework-res
This will decompile the framework-res.apk that’s in the current command window folder into a subfolder framework-res
Find the xml files you need to modify, e.g. the battery icon xml res\drawable\stat_sys_battery.xml and edit them. This is assuming, of course that you know what needs to go in the XML file . For the battery XML it is pretty obvious, just copy/paste the existing nodes and change them so you have the necessary percentage entries, see the attachment for an example with 100 steps.
Add any necessary resources to the appropriate folder. For the battery icon you need to create an image for each percentage (or download one of these) and add them to the res\drawable_hdpi folder. The name is the same as the name in the xml (stat_sys_battery_*.png)
Rebuild the apk using the following command:
Code:
java -jar apktool.jar b framework-res out\framework-res.apk
This will create a new framework-res.apk in a subfolder out.
IMPORTANT: Do not push this apk to your phone unless you want to reflash
Extract the xml files and images from the newly generated apk (you can use the original images, but the xml files must be the newly compiled ones from the new apk). Add these files to the original framework-res.apk that you want to push to your phone (see the previous post).
Extract the resources.arsc from the root of the apk
Rename the original framework-res.apk from your theme to framework-res.zip
Right-click the extracted resources.arsc and choose the 7zip menu item ‘Add to archive’
In the dialog that appears set the achive field at the top to the framework-res.zip from step 7. And set the archive format to zip. Now set the Compression level to store and click OK(if you do not do this your phone will not boot). The settings are in the attached screenshot.
Rename framework-res.zip to framework-res.apk and double check that the compressed size or resources.arsc is the same as the original size (see screenshot)
Done. Push the new framework to your phone.
Status Bar Text:
The style for most (all?) UI elements can be found in res/values/styles.xml. This xml file is only available in a decompiled framework. In the compiled version everything in res/values is compiled into resoureces.arsc.
The status bar text style is named TextAppearance.StatusBar. The file is pretty large so it's best just to do a search for the name. The definition looks like this:
Code:
<style name="TextAppearance.StatusBar" parent="@style/TextAppearance">
<item name="textSize">16.0sp</item>
<item name="textStyle">normal</item>
<item name="textColor">@color/semc_text_color_primary</item>
</style>
You can easily adjust the size or make the text bold using the textSize and textStyle elements (see here for a description of these attributes and their values). The color uses the @color/... notation. This is a reference to a color resource, these can be found in colors.xml. We could just change this to a direct color entry (see here for an example), but then we wouldn't have a resource that can be reused for other parts of the UI.
If you open colors.xml you can find this:
Code:
<color name="semc_text_color_primary">#ffffffff</color>
This sets the primary text color to white (ARGB: FFFFFFFF = White). Changing the value of this will change the color of all primary text throughout the phone (settings menu etc.). If we just want to change the notification bar then it's best to add a new color. To do this just duplicate the above color definition and change the name and color:
Code:
<color name="semc_text_color_primary">#ffffffff</color>
<color name="semc_text_color_custom">#9900ff00</color>
And then adjust the style to use this new color resource:
Code:
<style name="TextAppearance.StatusBar" parent="@style/TextAppearance">
<item name="textSize">16.0sp</item>
<item name="textStyle">normal</item>
<item name="textColor">@color/semc_text_color_custom</item>
</style>
Now recompile and copy resources.arsc to your framework as described above and push the framework to your phone for semi-transparent green text in your status bar

Modifying Services.jar
To modify services.jar we need to decompile the classes.dex file contained within. We can do this with baksmali:
1. Open services.jar (found in system/framework) with 7zip
2. Extract classes.dex from the archive
3. Open a command window and use the following to decompile:
Code:
java -jar baksmali-1.2.5.jar -o out\services classes.dex
4. You will now have a subfolder out\services with the decompiled .dex classes (smali files)
These sort of modifications will not be necessary very often. Two things that have been looked at so far are changing the text color on the status bar clock (just the clock, not the notification text) and changing the signal strength to show dBm instead of just the bars. The text color of the clock is relatively simple and is described below. The signal strength mod was done by MrRusch and requires a bit more code, he describes the process here.
I have attached a converter MrRusch has put together to convert java to smali. This is really helpful when trying to figure out how to modify the smali or event just trying to figure out what a piece of smali code does.
Since the 15th of december the sources for 2.1 are available here. Now we can see how the original java relates to the decompiled smali code.
You can find a reference for all the smali ops here. This one is more complete but I prefer the first purely because it's a bit more compact and it has most of what I need anyway. Thanks to untemensch and JesusFreke for the links.
Status Bar Clock Color:
I have since figured out how to do this without changing any code, just by changing some xml in res/layout, but I will keep this here as I think it is a nice, easy to follow example to start out with.
This section describes how to modify the color of the clock in the status bar without changing the color of the notification text (changing all of the status bar text is described in the xml section above).
First we need to have a look at the smali file com\android\server\status\StatusBarIcon.smali to see how the color of the clock text is set. I use Visual Studio to view/edit the smali files, but you can use any text editor - I have seen PSPad recommended a few times.
If we look at the init method we can see the following piece of smali code:
Code:
.line 44
.local v15, textColor:I
const/4 v13, -0x1
.line 50
.local v13, styleIndex:I
const v18, 0x1030079
:try_start_1f
sget-object v19, Lcom/android/internal/R$styleable;->TextAppearance:[I
move-object/from16 v0, p1
move/from16 v1, v18
move-object/from16 v2, v19
invoke-virtual {v0, v1, v2}, Landroid/content/Context;->obtainStyledAttributes(I[I)Landroid/content/res/TypedArray;
move-result-object v5
.line 53
.local v5, a:Landroid/content/res/TypedArray;
const/16 v18, 0x0
move-object v0, v5
move/from16 v1, v18
move/from16 v2, v16
invoke-virtual {v0, v1, v2}, Landroid/content/res/TypedArray;->getDimension(IF)F
move-result v16
.line 54
const/16 v18, 0x3
move-object v0, v5
move/from16 v1, v18
move v2, v15
invoke-virtual {v0, v1, v2}, Landroid/content/res/TypedArray;->getColor(II)I
move-result v15
Here's a run-down:
I'm pretty sure the lines that start with a '.' are comments from the decompiler.
The .line 4 entries are just a reference to the line number in java source-code. And I think the .local v15, textColor:I entry just notes the v15 variable name and type (I = integer).
The first bit of interest is the line invoke-virtual {v0, v1, v2}, Landroid/content/Context;->obtainStyledAttributes(I[I). The obtainStyledAttributes method definition can be found here. There are a few overloads, but the call is to the method that accepts an integer and an integer array as parameters - hence the (I[I), I and [I. The three variables in braces at the start denote the object that the method is being called on (the Context object) and the two parameters respectively. The first parameter (v1) is a resource ID and a few lines up the v18 variable is copied to this (move/from16 v1, v18 - this means move the value from v18 to the v1 variable). v18 was declared a few lines above again with the value 0x1030079. This ID can be found in the framework xml-file res/values/public.xml and the value is the name of a style (TextAppearance.StatusBar) that can be found in res/valus/styles.xml (see the xml section above).
The result of obtainStyledAttributes is copied to v5 (move-result-object v5) which (in .line 54) is copied to v0 which is then used to call Landroid/content/res/TypedArray;->getColor with the two integer parameters v18 (0x3) and v15 (0x100 - this is the color black). The first parameter is the index of the color in the style array (index 3 in v5) and the second is the default value (black).
The result of getColor() is then copied to v15 and reused later when setting up the text view for the clock:
Code:
.line 61
.local v14, t:Landroid/widget/TextView;
move-object v0, v14
move-object/from16 v1, p0
iput-object v0, v1, Lcom/android/server/status/StatusBarIcon;->mTextView:Landroid/widget/TextView;
.line 62
new-instance v11, Landroid/widget/LinearLayout$LayoutParams;
const/16 v18, -0x2
const/16 v19, -0x1
move-object v0, v11
move/from16 v1, v18
move/from16 v2, v19
invoke-direct {v0, v1, v2}, Landroid/widget/LinearLayout$LayoutParams;-><init>(II)V
.line 65
.local v11, layoutParams:Landroid/widget/LinearLayout$LayoutParams;
const/16 v18, 0x0
move-object v0, v14
move/from16 v1, v18
move/from16 v2, v16
invoke-virtual {v0, v1, v2}, Landroid/widget/TextView;->setTextSize(IF)V
.line 66
invoke-virtual {v14, v15}, Landroid/widget/TextView;->setTextColor(I)V
All this means that to change the color of the clock text only, we need to declare a new style and use the ID of this style in the call to obtainStyledAttributes. When adding the style to styles.xml I keep it in the same place as the other status bar styles:
Code:
...
<style name="TextAppearance.StatusBar" parent="@style/TextAppearance">
<item name="textSize">16.0sp</item>
<item name="textStyle">normal</item>
<item name="textColor">@color/semc_text_color_primary</item>
</style>
<style name="TextAppearance.StatusBar.Clock" parent="@style/TextAppearance">
<item name="textSize">16.0sp</item>
<item name="textStyle">normal</item>
<item name="textColor">@color/semc_text_color_clock</item>
</style>
...
The name of the style can be anything, what is important is the ID reference in public.xml, and that a color semc_text_color_clock is declared in colors.xml (see the xml section above).
The style reference in public.xml must have an ID that starts with 0x0103****. This is the ID range for styles, strings and other resources have a different ID range. I always add the new style at the bottom of the style group so that I can easily see which is the next free ID:
Code:
....
<public type="style" name="SEMCTheme.Dialog.Alert.Vanilla" id="0x01030139" />
<public type="style" name="TextAppearance.StatusBar.Clock" id="0x0103013a" />
....
Now that we have added a new style we just need to adjust the smali code to use it. Change the code above from:
Code:
.line 50
.local v13, styleIndex:I
const v18, 0x1030079
to:
Code:
.line 50
.local v13, styleIndex:I
const v18, [B]0x103013a[/B]
Now our new style is used for the call to obtainStyledAttributes. We then need to recompile the smali to a classes.dex file and update the services.jar:
Run the following command to recompile the smali:
Code:
java -jar smali-1.2.5.jar -o out\classes.dex out\services
The output file may be a slightly different size than the original classes.dex but as long as you don't get any errors it will be OK.
Now open services.jar with 7zip and update it with the new classes.dex (drag/drop).
Done Push the services.jar to your phone with adb and reboot (make sure you have updated framework-res.apk with the new xml resources first, otherwise our new ID will point to a non-existant resource)

Timescape/Mediascape
Timescape and Mediascape use a different format for some of the images (for mediascape it's just the background on the first page). Timescape also has some animation files to control the wave in the background and the color of the paginator. In 1.6 we can modify all of these, for 2.1 I still haven't got the animations sussed.
All of the information I have collected, including tools for converting the images, can be found here (the 2.1 converter tools are linked at the top of the first post).
If you're just looking to modify the first page of mediascape then it is here: /system/usr/semc/seee/files/ms_bg_background_home_icn.acet
Here are the two dark themes that I have done for Timescape:
1.6
2.1 (without animations)
and the following themes also include Timescape mods:
Dark10 by Chewitt
Enigma by Mobzter

Resource locations
Images:
gavriel18 has posted some of the standard mods here.
XML:
I have attached some images where you can see the effects of changing the most common colours in res/values/colors.xml. It looks pretty horrible, but you can see what you need to change
I still haven't figured out how to change some of the colours (e.g. the network provider text in the status bar) but I will update this when I find out more...
Please PM me or post any other mods that you've made that were well hidden. We can add them here to avoid searching for them again later.
This especially applies to all the OPs from the next post

Theme collection
Update (24.03.2011): There is a much more up-to-date list here with all the new themes.
Here's a list of some of the existing themes around:
2.1:
Dark10 by Chewitt
X10 Res Mods by XperiaX10iUser
ElementaL by Mr_Element
Pitch Black by Shukla
Xdre4m by PoTi_96
PGFX™ Eternity by SEMPITERNAL
Transparent Status Bar Theme by thefunkaygibbon
HTC Sense and Stock Android Status Bar by dk2000zx
Enigma by Mobzter
1.6:
Dark10 by Chewitt
Frankendroid by Bazza1976
Enigma by Mobzter
Red Theme by djsystem
There's also a lot more here thanks to gavriel18
If I have missed any please PM me or post here and I'll update the list. I just scanned the first 3 pages in the forum.

Recovery tips
This post will be used for tips etc. on recovering your phone if it won't boot (if this never happens to you then you're not trying hard enough )
From here:
MarylandCookie said:
Future tip: For anyone who needs to reflash due to a bad upload of an app i would recommend just flashing the system.sin file (ive done this on a number of occasions!!)...
Your phone will boot up (will take a little longer than usual) and the only difference will be is that you will have all your system apps back but you will need to re-root. Everything else will be the same
Even better if you have the One Click Root app found here:
http://forum.xda-developers.com/showthread.php?t=834428
Click to expand...
Click to collapse
From here:
gavriel18 said:
Possible reasons your phone won't boot after modifications:
images anren't stored properly, right format, right size etc.
unpacked apk improperly, use 7zip, it doesn't mess anything up
you signed the package before pushing it- unless you know what you're doing follow the directions to a tee and you should be fine
pushed the package to the wrong directory, /system/framework-res.apk XX, /system/framework/framework-res.apk
I'm sure many other reasons, these were the only ones I encountered
How to get past boot screen:
Use backup framework-res.apk and push that one to your phone. Remember to place that one where the modified one is.
To see if adb sees your phone type adb devices, if a serial number pops up try pushing your original, if not...
Flash your phone again from scratch . Sorry, I don't know any better way yet.
Click to expand...
Click to collapse
from bitter personal experience :
If anyone does mess their phone up so much that not even the SE logo shows up (just a black, maybe flickering, screen) and a reflash/seus repair doesn't help. Then what sorted me out was a reflash to Generic Nordic 1.6 using jerpelea's flash tool - the same one I used to get the 2.1 update early - then boot the phone, shut down again and run seus for the 2.1 update.
Click to expand...
Click to collapse
Not directly related, but here's a tip from XperiaX10iUser:
To reverse chmod use 0755 instead of 4755.

This would indeed be helpful. Thanks.

This definitely needs to be sticky'd! It beats looking over pages and pages worth of threads to find the correct ones. It's a lot harder to search through threads without getting completely creative with your search strings so as to cull out all of the useless threads.
Thanks for this! I just posted about a theme I'd like to work on and requested this information!

Wow, great tutorial Calum. Thank you once again for all your hard work!

Thanks for the feedback guys

Great thread! Why on earth the mods haven't thought to sticky this is beyond me.

great thread Callum!
i vote yes for sticky also!

Thanks for all the hard work _calum_ and all the other themers too!

Thank you for this Ultimate theme reference thread... It definitely should be sticky....

XperiaX10iUser said:
Great thread! Why on earth the mods haven't thought to sticky this is beyond me.
Click to expand...
Click to collapse
As I told you the other day... because we cannot be monitoring every single thread in this site...
Also, we only do stickies upon request...
In either case, great guide.
Thread stuck.

egzthunder1 said:
Thread stuck.
Click to expand...
Click to collapse
Thanks
And thanks for all the other posts as well. Now you guys just need to tell me what's missing

[MULTI-MOD] Reboot Option, Percentage Battery, Percentage WiFi, & ASU Signal Strength

[MULTI-MOD] Reboot Option, Percentage Battery, Percentage WiFi, & ASU Signal Strength
I managed to port untermensch's modification to add reboot option(s) to our power menu. See original thread for more information on the process.
Alternative versions also include the Super Circle Battery modification, my own WiFi percentage indicator and ASU network signal strength mods.
{
"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"
}
Requirements:
1. Root privileges
2. Choose appropriate firmware version below.
2.3_3.0.1.G.0.75_GENERIC
See this post for Reboot Option only.
See this post for Reboot Option & Percentage Battery.
See this post for Reboot Option & Percentage Battery & WiFi Percentage & ASU Signal Strength.
See this post for Reboot Option & Percentage Battery & WiFi Percentage & ASU Signal Strength + Roaming.
2.1.A.0.435_GLOBAL See this post.
2.0.2.A.0.24_GLOBAL See this post.
2.0.A.0.504_GLOBAL See this post's attachments.
Note: This replaces core system files, i.e. will remove previously installed themes and modifications. If you have problems, push back the original files.
Automatic (xRecovery) Installation:
Reboot into xRecovery and flash update.zip if supplied.
Automatic (ADB GUI) Installation:
Use the X10 Mod Tool, to push the files to the device.
SystemUI.apk goes in system/app if present, and rest in system/framework.
Manual (Terminal Emulator) Installation:
1. Unrar archive.
2. Copy extracted files to /sdcard, and
3. In Terminal Emulator:
a) make sure you have super user permissions (su),
b) remount /system partition as read-write (mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system),
c) replace framework.jar (dd if=/sdcard/framework.jar of=/system/framework/framework.jar),
d) replace android.policy.jar (dd if=/sdcard/android.policy.jar of=/system/framework/android.policy.jar),
e) replace SystemUI.apk (dd if=/sdcard/SystemUI.apk of=/system/app/SystemUI.apk) if present,
f) replace framework-res.apk (dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk) if present, and
g) reboot device (reboot) if not automatic.

Thanks Mr. Rusch glad your also modding the x10

Tested on my Singapore X10i but it cannot boot up, I am repairing my X10 via the PC Companion now.

Under contruction
Percentage Battery
A. The 101 stat_sys_battery_X.png and 21 stat_sys_battery_charge_X.png images of which the modification is based, need to be inserted into framework-res.apk.
1. Decompile framework-res.apk with APK Tool or X10 Mod Tool.
2. Add images to res/drawable-hdpi/.
B. These images then need to be referenced in public.xml as drawables.
1. Open res/values/public.xml in e.g. Notepad.
2. Find last drawable-id and increment by one hexadecimal value (XxXXXXXXXX).
3. Create and add all of your drawables as below, incrementing by one hexadeimal value per item.
Code:
<public type="drawable" name="stat_sys_battery_X" id="XxXXXXXXXX" />
4. Save and Close.
C. The XMLs controlling the battery stats (stat_sys_battery.xml and stat_sys_battery_charge.xml) need to be adjusted to percentage levels (100 on battery, and 20 at charging).
1. Replace stat_sys_battery.xml with the one attached to this post.
2. Replace stat_sys_battery_charge.xml with the one attached to this post.
3. Recompile framework-res.apk with APK Tools or X10 Mod Tool.
Replace framework-res.apk on your device.
Reboot Option
A. The reboot.png needs to be inserted into the framework-res.apk.
1. Decompile framework-res.apk with APK Tool or X10 Mod Tool.
2. Add reboot.png to res/drawable-hdpi/.
B. This image is then to be referenced in public.xml as a drawable.
1. Open res/values/public.xml in e.g. Notepad.
2. Find last drawable-id and increment by one hexadecimal value (XxXXXXXXXX).
3. Create and add your drawable as below,
Code:
<public type="drawable" name="reboot" id="XxXXXXXXXX" />
C. The string "Reboot" needs to be added as well, in public.xml and strings.xml.
1. Find last string-id and increment by one hexadecimal value (XxXXXXXXXX).
2. Create and add your string as below,
Code:
<public type="string" name="reboot" id="XxXXXXXXXX" />
3. Save and Close public.xml.
5. Open res/values/strings.xml in e.g. Notepad.
6. Create and add your string as below,
Code:
<string name="reboot">Reboot</string>
7. Save and Close.
8. Recompile framework-res.apk with APK Tool or X10 Mod Tool.
D. ShutdownThread.java needs to be modified to handle the reboot-command from the power menu.
1. Decompile framework.jar with X10 Mod Tool or baksmali.jar.
2. Open com\android\internal\app\ShutdownThread.smali in e.g Notepad.
3. After the last entry in the "# static fields" section, add
Code:
.field public static mReboot:I
4. Search for "invoke-static {}, Landroid/os/Power;->shutdown()V", and add the following code before this line.
Code:
sget v1, Lcom/android/internal/app/ShutdownThread;->mReboot:I
const/4 v2, 0x1
if-eq v1, v2, :reboot
5. After the next return-void statement, add this code
Code:
:reboot
const-string v4, "now"
invoke-static {v4}, Landroid/os/Power;->reboot(Ljava/lang/String;)V
return-void
This will send the "now" command to the kernels shutdown process. When we get our kernels sorted, we can add other commands such as "recovery" or "download" here.
6. Save and Close.
7. Recompile framework.jar with X10 Mod Tool or smali.jar.
E. GlobalActions.java needs to be modified to present the reboot-
drawble/string in the power menu.
1. Decompile android.policy.jar with X10 Mod Tool or baksmali.jar.
2. Open com\android\internal\policy\impl\GlobalActions.smali in e.g Notepad.
3. In the "createDialog" method, extend the array by changing this
Code:
const/4 v0, 0x3
new-array v0, v0, [Lcom/android/internal/policy/impl/GlobalActions$Action;
to this
Code:
const/4 v0, 0x[B]4[/B]
new-array v0, v0, [Lcom/android/internal/policy/impl/GlobalActions$Action;
Note here that depending on how many options that already exist in your power menu, this constant's value may differ. The point is - increment it by 1.
4. Add the reboot menu item by adding the following code after last instance of "aput-object v2, v0, v1"
Code:
const/4 v1, 0x3
new-instance v2, Lcom/android/internal/policy/impl/GlobalActions$7;
const v3, XxXXXXXXX # reboot icon resource id
const v4, YxYYYYYYY # reboot string resource id
invoke-direct {v2, p0, v3, v4}, Lcom/android/internal/policy/impl/GlobalActions$7;-><init>(Lcom/android/internal/policy/impl/GlobalActions;II)V
aput-object v2, v0, v1
Note: Swap XxXXXXXXX for the drawable-ID and YxYYYYYYY for the string-ID. The constant v1 decides the placement in the array we extended above. So you can adjust this if you want to place the entry somewhere other than at the end. But remember to adjust the other entries as well then.
5. Save and Close.
6. Now make a copy of GlobalActions$3.smali and rename it to GlobalActions$7.smali.
7. Open GlobalActions$7.smali in e.g Notepad.
8. Replace all instances of "GlobalActions$3" inside it, with "GlobalActions$7".
9. Search for "invoke-static {v0, v1}, Lcom/android/internal/app/ShutdownThread;->shutdown(Landroid/content/Context;Z)V", and add the following code in the line before
Code:
const/4 v2, 0x1
sput v2, Lcom/android/internal/app/ShutdownThread;->mReboot:I
10. Save and Close.
11. Recompile android.policy.jar with X10 Mod Tool or smali.jar.
Replace framework.jar, android.policy.jar and framework-res.apk on your device.
Percentage WiFi
A. The 21 stat_sys_wifi_signal_X.png images need to be inserted into framework-res.apk (<2.3.3) or SystemUI.apk (>2.3.3).
1. Decompile framework-res.apk with APK Tool or X10 Mod Tool.
2. Add images to res/drawable-hdpi/.
B. These images then need to be registered as drawables in public.xml.
1. Open res/values/public.xml in e.g. Notepad.
2. Find last drawable-id and increment by one hexadecimal value (XxXXXXXXXX).
3. Create and add all of your drawables as below, incrementing by one hexadeimal value per item.
Code:
<public type="drawable" name="stat_sys_wifi_signal_X" id="XxXXXXXXXX" />
4. Recompile framework-res.apk (<2.3.3) or SystemUI.apk (>2.3.3) with APKTool or X10 Mod Tool.
C. StatusBarPolicy.java needs to load the new WiFi-drawables into status bar.
1. Decompile services.jar with X10 Mod Tool.
2. Open StatusBarPolicy.smali in e.g. Notepad.
3. Go the start of the constructor at ".method static constructor <clinit>()V".
4. Increment " .locals X" by one decimal value.
5. Under " .prologue", add another registry to extend the array with,
Code:
const/16 vX, 0x21
Note: vX is also incremented by one decimal value.
6. Now search for "sput-object v0, Lcom/android/systemui/statusbar/policy/StatusBarPolicy;->sWifiSignalImages:[[I"
The three rows above this, will look like this
Code:
new-array vX, vY, [I
fill-array-data vX, :array_Q
aput-object vX, vZ, v4
6. In the first row, swap vY to the constant we created to initiate the array with.
7. From the second row, copy the ":array_Q" value and go to this marker.
8. Extend this array at the end with references to the drawables-IDs we registered in public.xml earlier.
Note: The ID-format is backwards, i.e.
0xXXt 0xYYt 0xZZt 0xQQt = 0xQQZZYYXX
9. Save and Close.
10. Recompile services.jar with X10 Mod Tool.
D. WifiManager's calculateSignalLevel() functions decision-logic needs to be modified for the 20 levels of WiFi (5% increments).
Note: This function should according to the APIs work as is, as it recieves the array-length as maximum value. For some reason though, I constantly face OutOfBoundsExceptions when using this. Instead, I have created my own logic in java, converted it into smali-code, and replaced the original function with it.
1. Decompile framework.jar with X10 Mod Tool or baksmali.jar.
2. Open WifiManager.smali in e.g. Notepad.
3. Replace the "calculateSignalLevel" function with the one attached to this post.
4. Save and Close.
5. Recompile framework.jar with X10Mod Tool or smali.jar.
Replace framework.jar, services.jar and framework-res.apk on your device.
ASU/dBm Signal Strength
A. The 33 stat_sys_signal_X.png images need to be inserted into framework-res.apk.
B. These images then need to be registered as drawables in public.xml.
C. StatusBarPolicy.java needs to be modified to choose drawable by ASU-value.
D. StatusBarPolicy.java needs to load the new ASU-drawables into status bar.
E. For roaming to work, same process (1-4) needs to be repeated for stat_sys_r_signal_X.png images.

Thank you very much for your mod, tested on my X10 with 2.1 Global Generic and work very well.
To serve options:
Recovery and Download?
Great Work
PD: It would be possible to modify the text of the options?:
Reboot----- for Reiniciar
Recovery----for Recuperar
Download--- for Descargar
It's because I have the X10 in Spanish

tiggerbcn said:
PD: It would be possible to modify the text of the options?:
Reboot----- for Reiniciar
Recovery----for Recuperar
Download--- for Descargar
It's because I have the X10 in Spanish
Click to expand...
Click to collapse
You'd have to mod the APK. So depends how comfortable you are with this.
Edit: Decompile the APK, modify strings.xml, and recompile.
Sent from my X10i using XDA App

Buffff, that will not do, be so kind to modify that file and put it here to download it?, I've put a link to this post in a forum Spanish and there are some who call me, but I have the tools to edit these files
Thanks
PD:and these options are used?
Recovery and Download

Hi, MrRusch. How can I install ONLY that grey battery icon with the percentage within it? Is it possible?
Thanks in advance
PS: I'm the one who asked tiggerbcn for the spanish translation btw

is it possible to modify it to have the reboot option only?
as I dont think I would be using the other options...and would rather not press them by mistake....he he

MrRusch said:
You'd have to mod the APK. So depends how comfortable you are with this.
Edit: Decompile the APK, modify strings.xml, and recompile.
Sent from my X10i using XDA App
Click to expand...
Click to collapse
where i can find that "stings.xml" ?
thks

rendeiro2005 said:
where i can find that "stings.xml" ?
thks
Click to expand...
Click to collapse
It's in res\values in the APK.
Zenghelis said:
Hi, MrRusch. How can I install ONLY that grey battery icon with the percentage within it? Is it possible?
Thanks in advance
PS: I'm the one who asked tiggerbcn for the spanish translation btw
Click to expand...
Click to collapse
You will find the battery mod itself in this thread.
tiggerbcn said:
Buffff, that will not do, be so kind to modify that file and put it here to download it?, I've put a link to this post in a forum Spanish and there are some who call me, but I have the tools to edit these files
Thanks
PD:and these options are used?
Recovery and Download
Click to expand...
Click to collapse
Sorry all, but I will not be making language-specific mods, as this would lead to requests for lots of different languages. If you want to modify it to your language, follow the instructions I have given here (or consult your national chef for help).
As for the latter part of your question - perhaps someone else here can answer this, as this is my first Android device.
mith500 said:
is it possible to modify it to have the reboot option only?
as I dont think I would be using the other options...and would rather not press them by mistake....he he
Click to expand...
Click to collapse
Yes, this version is coming.

MrRusch said:
It's in res\values in the APK.
Click to expand...
Click to collapse
thks a lot.
i`m trying to create a new theme with animations, battery info, etc and i don`t want just install.
thks

rendeiro2005 said:
thks a lot.
i`m trying to create a new theme with animations, battery info, etc and i don`t want just install.
thks
Click to expand...
Click to collapse
Now you got me
how the hell i`m suppoused to mess if i don`t have that folder???
yours don`t have it as mine

rendeiro2005 said:
Now you got me
how the hell i`m suppoused to mess if i don`t have that folder???
yours don`t have it as mine
Click to expand...
Click to collapse
You need to decompile it, not just extract it as an archive. Use apktool or client such as APK Manager to access meta-data from resources.arsc.

MrRusch said:
You need to decompile it, not just extract it as an archive. Use apktool or client such as APK Manager to access meta-data from resources.arsc.
Click to expand...
Click to collapse
forget it
i`m working with that now
thks

i`m sorry but i need your hel with one more thing
were i can find "com\android\internal\app\ShutdownThread.smali "?
it`s suppoused to be on framework but we only have framework-res andi can`t find that
thks

rendeiro2005 said:
i`m sorry but i need your hel with one more thing
were i can find "com\android\internal\app\ShutdownThread.smali "?
it`s suppoused to be on framework but we only have framework-res andi can`t find that
thks
Click to expand...
Click to collapse
No, sorry this is embedded in framework.jar, not framework-res.apk. You will need to deodex this file with baksmali to decompile, edit, and then recompile with smali. But FYI you don't need to touch anything but the APK if you only want to change the language. For this editing strings.xml is enough.

MrRusch said:
No, sorry this is embedded in framework.jar, not framework-res.apk. You will need to deodex this file with baksmali to decompile, edit, and then recompile with smali.
Click to expand...
Click to collapse
ooops
ok
thks

I have now added the single option version, only displaying the Reboot (normal) alternative. This one also comes in two versions, with the default battery indicator, or the percentage one. See screenshots in first post.

MrRusch said:
I have now added the single option version, only displaying the Reboot (normal) alternative. This one also comes in two versions, with the default battery indicator, or the percentage one. See screenshots in first post.
Click to expand...
Click to collapse
sorry again
what`s the command to compile android.policy.jar?
thks

[Tutorial] How to Modify Android AutoBacklight Characteristics

I know, there are some hints about how to modify the terrible behaviour of AutoBacklight already existing in this forum. But they are all hidden deep inside some device specific ROM threads. So I like to cross post here, what I already partly posted in the Saga ROM dev section.
Androids AutoBacklight on most devices has a habit to not quite reasonably adapt to environmental light conditions. Especially in dark environment, the screen is usually not getting dark enough. You need to manually set the backlight value for ebook reading in a dark room e.g.
To overcome this issue is not exactly easy. But it's manageable.
What you need is a ROOTED DEVICE (!!) and APK-Manager.
The task is to modify the AutoBacklight values within arrays.xml, which is located inside framework.res.apk
I did this on my HTC Desire S. It should work for all HTC Androids and all other devices as long as you find the arrays.xml after decompiling the framework.res.apk. No garantie though for other devices. Just have a look to your files to see if it's there.
And here's the step by step procedure:
on Phone:
copy framework.res.apk from \system\framework to SD-Card (use e.g. RootExplorer)
on PC within APK-Manager folder:
1. place framework.res.apk into folder "place-apk-here-for-modding"
2. clear old files in projects folder if necessary
3. run Script.bat
4. Option 22 - select project --> select framework.res.apk
5. Option 9 - Decompile apk
6. apk is beeing decompiled and extracted to the projects folder now
7. keep APK-Manager script window open in background
8. go to \projects\framework-res.apk\res\values\
9. edit arrays.xml in editor accordingly, this is the interesting section:
Code:
<integer-array name="config_autoBrightnessLevels">
<item>11</item>
<item>41</item>
<item>91</item>
<item>161</item>
<item>226</item>
<item>321</item>
<item>641</item>
<item>1281</item>
<item>2601</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValues">
<item>25</item>
<item>31</item>
<item>38</item>
<item>51</item>
<item>71</item>
<item>92</item>
<item>128</item>
<item>171</item>
<item>204</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValuesUp">
<item>25</item>
<item>31</item>
<item>38</item>
<item>51</item>
<item>71</item>
<item>92</item>
<item>128</item>
<item>171</item>
<item>204</item>
<item>255</item>
</integer-array>
<integer-array name="config_autoBrightnessLcdBacklightValuesDown">
<item>25</item>
<item>31</item>
<item>38</item>
<item>51</item>
<item>71</item>
<item>92</item>
<item>128</item>
<item>171</item>
<item>204</item>
<item>255</item>
</integer-array>
Keep the "config_autoBrightnessLevels" untouched. Just modify the "config_autoBrightnessLcdBacklightValues", "config_autoBrightnessLcdBacklightValuesDown" and "config_autoBrightnessLcdBacklightValuesUp".
10. back to APK-Manager Script - Option 11 - compile apk
11. after a while of compilation, you will be asked if you want to keep unmodified files from original apk --> answer Y
12. content from original framework.res.apk is beeing extracted to folder \keep
13. now you will be asked to delete all the files you modified in \projects to delete in \keep (think a while, it makes sense!)
14. in our case, you only need to delete resources.arsc (as we only modified a XML)
15. hit Enter in script window and the compilation will finish
16. look at \place-apk-here-for-modding, there's an unsignedframework.res.apk beside your original framework.res.apk
17. Option 12 - sign apk
18. look at \place-apk-here-for-modding, unsignedframework.res.apk will now be renamed to signed...
--> this is your new framework.res.apk to be uploaded to UOT-Kitchen. Copy it somewhere and rename it back to framework.res.apk
19. You can not simply copy it back to \system\framework. It has to be cooked and flashed.
20. Go to UOT-Kitchen website (http://uot.dakra.lt/kitchen/), open a new kitchen and do nothing but upload your new framework.res.apk. You don't need to upload all the other files as long as you do not want to apply any other modification.
21. submit the kitchen work and wait to be cooked
22. get your UOT-***.zip from the kitchen once it's available in the pickup section
23. put the zip to your phone an flash it through eighter Recovery or ROM-Manager as any other flashable update.zip
Done.
The values you see in the code section above are the ones that work best for me on the Desire S. Your milage may vary. Here's a characteristics comparison between my values and the ones that came with stock ROM.
Attached find the Excel file to do your own characteristics calculation.

OpenDelta OTA for all phones

Hi i have tested a lot of OTA apps and configs and they are very annoying until i stop thinking for a moment and I find a solution for having true OTAS updates and not depending from other users just like Nexus Devices OTAS.
Ok we started:
First of all we need to download Android Bundle with contains SDK and Eclipse
Here it is:
http://developer.android.com/sdk/index.html?hl=sk#download
After it is download and installed.
You are going to download my fixed source for supporting from Android 4.1.2 to 4.4.2.
https://github.com/werty100/OpenDelta
And Click on:
{
"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"
}
Them open Eclipse...
Go to file/Import:
Next and locate were is the download source
Then Finish...
Wait until it is import....
Go to res folder, values and open config.xml:
Here are the important values for making work your OTA in your phone.
Code:
<!-- Property to read for ROM version -->
<string name="property_version">ro.delta.version</string>
<!-- Property to read for device identifier -->
<string name="property_device">ro.delta.device</string>
This should be put in build.prop:
Ex:
ro.delta.version=1.0.2
ro.delta.device=i9000
You can modificated all values but you should modificate this ones:
Code:
<!-- URL base to find .delta files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_delta">https://delta.omnirom.org/nightlies/%s/</string>
<!-- URL base to find .update and .sign files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_update">http://delta.omnirom.org/nightlies/%s/</string>
<!-- URL base to find the full zip files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_full">http://dl.omnirom.org/%s/</string>
Indicates where to find the ZIP for your phone...
Also you can modificate all UI and values....
After the essentials modifications you will need to compile APK:
Go here and click on selected item..
You will need to create your own KeyStores
Rellenate also this:
https://dl.dropboxusercontent.com/u/26870831/rellenate.png
Them just put destination and click finish:
After all of this you have to modificate the Settings.apk of your rom:
Decompile with the script/tool you like more and go to:
In res/values:
String.xml
Add this:
Code:
<string name="system_update_settings_list_item_title">System updates</string>
<string name="system_update_settings_list_item_summary" />
Paste it near baseband_version string kernel_version string etc...
Then go to public and paste this near device_info_settings:
Code:
<public type="string" name="system_update_settings_list_item_title" id="0x7f0c06d7" />
<public type="string" name="system_update_settings_list_item_summary" id="0x7f0c06d8" />
Then go to xml/device_info_settings.xml:
And copy this in the firs lines after:
Code:
<?xml version="1.0" encoding="utf-8"?>
<PreferenceScreen android:title="@string/about_settings"
xmlns:android="http://schemas.android.com/apk/res/android">
Paste this:
Code:
<PreferenceScreen android:title="@string/system_update_settings_list_item_title" android:key="system_update_settings" android:summary="@string/system_update_settings_list_item_summary">
<intent android:action="android.settings.SYSTEM_UPDATE_SETTINGS" />
</PreferenceScreen>
<PreferenceScreen android:title="@string/additional_system_update_settings_list_item_title" android:key="additional_system_update_settings">
<intent android:targetPackage="@string/additional_system_update" android:action="android.intent.action.MAIN" android:targetClass="@string/additional_system_update_menu" />
</PreferenceScreen>
After Compiling Settings.apk you will have full OTAS

Tomorrow More

Today more
Publish on HTCMania haha

Update New settings for OTA

Just a quick question:
Code:
[B] <!-- URL base to find .delta files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_delta">https://delta.omnirom.org/nightlies/%s/</string>
<!-- URL base to find .update and .sign files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_update"http://delta.omnirom.org/nightlies/%s/</string>[/B]
<!-- URL base to find the full zip files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_full">http://dl.omnirom.org/%s/</string>
If we want to configure it to our directory, what should we inclue on .delta files & .update and .sing files?

With this OTA guide will I have to boot into recovery to flash a OTA?

You can't use this for any other ROM because we don't know what we should had on .delta & .update & .sign files

Howdy! Some general stuff:
You should credit original developer of OpenDelta (that's Chainfire @ OmniROM)
Proper way to make own, patched version is Pulling the original repository (easiest way is using "Pull" button on GitHub there: https://github.com/omnirom/android_packages_apps_OpenDelta) and then patching it - this way you preserve all the commits history (and credits to original authors)
_MarcoMarinho_ said:
You can't use this for any other ROM because we don't know what we should had on .delta & .update & .sign files
Click to expand...
Click to collapse
There we got with an example:
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.sign
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.update
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.delta
.delta file is JSON
.sign is binary signature
.delta is binary delta data
...and
GUESS WHAT! There's an opensource stuff to generate ALL of the above.
Completely! Automagically!
https://github.com/omnirom/android_packages_apps_OpenDelta/tree/android-4.4/server/

Rebellos said:
Howdy! Some general stuff:
You should credit original developer of OpenDelta (that's Chainfire @ OmniROM)
Proper way to make own, patched version is Pulling the original repository (easiest way is using "Pull" button on GitHub there: https://github.com/omnirom/android_packages_apps_OpenDelta) and then patching it - this way you preserve all the commits history (and credits to original authors)
There we got with an example:
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.sign
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.update
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.delta
.delta file is JSON
.sign is binary signature
.delta is binary delta data
...and
GUESS WHAT! There's an opensource stuff to generate ALL of the above.
Completely! Automagically!
https://github.com/omnirom/android_packages_apps_OpenDelta/tree/android-4.4/server/
Click to expand...
Click to collapse
Thanks so much :highfive:
So I just need to modify few things, generate ALL stuff and then upload it to my server right?

Yup. Looks like. I'm not really experienced with OpenDelta but knowing Chainfire it's all easy to work with.

Post for subscription

when it comes to these stuff (git with coding and xml and OH MY GOD!) i am a total noob.
i still don't know how do i generate these files. I understand .zip is the whole ROM, but i have no idea how i can make .update .sign and .delta and what should i put in them and all.
hehe, to me, all i see is three beautiful files here https://github.com/omnirom/android_packages_apps_OpenDelta/tree/android-4.4/server/ which i know nothing about how i can use them to get the files.
i guess i'll wait for the "tomorrow more"

@_MarcoMarinho_ you can find on the github readme how to generate the Delta files.
Server-side
To create the delta files on the server, you need several things, some of which can be found in the server directory. The main thing is the opendelta.sh script. It contains a configuration section which you can edit with the correct file locations on your own system. Quite likely you will need to create a wrapper script that pulls in your previous release and your current release, and pushes out the created delta files.
The script depends on xdelta3, zipadjust and minsignapk.
For the builds on your server, make a copy of the jni directory - do not compile inside jni because you may mess up the build of libopendelta.
xdelta3 can be built in (the copy of) jni/xdelta3-3.0.7 by calling ./configure and make.
zipadjust can be built in (the copy of) jni by calling:
gcc -o zipadjust zipadjust.c zipadjust_run.c -lz
dedelta (not used by the script, but maybe helpful when debugging) can be built in (the copy of) jni by calling:
gcc -o dedelta xdelta3-3.0.7/xdelta3.c delta.c delta_run.c
minsignapk Java source is in the server directory, as well as a prebuilt minsignapk.jar file that should work on most systems.
Click to expand...
Click to collapse
If you are however to lazy to set up all that stuff check my script on github you can find here:
https://github.com/Myself5/CarbonDelta_server_software/
(I used it for my unofficials and when we tested CarbonDelta (which is based on OpenDelta))
Check the readme on how to install it and use it.

Myself5 said:
@_MarcoMarinho_ you can find on the github readme how to generate the Delta files.
If you are however to lazy to set up all that stuff check my script on github you can find here:
https://github.com/Myself5/CarbonDelta_server_software/
(I used it for my unofficials and when we tested CarbonDelta (which is based on OpenDelta))
Check the readme on how to install it and use it.
Click to expand...
Click to collapse
Thank, thanks so much, now I understand
-----
When I should put your repo? inside pakcages/apps?

_MarcoMarinho_ said:
Thank, thanks so much, now I understand
-----
When I should put your repo? inside pakcages/apps?
Click to expand...
Click to collapse
In any folder where you want it. It must not be inside your Roms Sourcecode. To create the delta update and sign files just follow the readme

Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<!-- Output some debug strings -->
<item type="bool" name="debug_output">false</item>
<!-- Property to read for ROM version -->
<string name="property_version">ro.euclidean.version</string>
<!-- Property to read for device identifier -->
<string name="property_device">ro.euclidean.device</string>
<!-- %s is expanded to property_version value. .zip, .delta, .update, .sign extensions added when needed -->
<string name="filename_base">euclidean_%s</string>
<!-- Path deltas are stored, relative to sdcard root -->
<string name="path_base">EuclideanDelta</string>
<!-- URL base to find .delta files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_delta">http://euclideanrom.grn.cc/downloads/%s/delta/</string>
<!-- URL base to find .update and .sign files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_update">http://euclideanrom.grn.cc/downloads/%s/delta/</string>
<!-- URL base to find the full zip files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_full">http://euclideanrom.grn.cc/downloads/%s/</string>
This is my setup.
I can't figure it out why I don't receive the updates

@werty100 will this work for lollipop?

gcng said:
@werty100 will this work for lollipop?
Click to expand...
Click to collapse
You need the new app source code.

Hey guys. I want add support OTA in my builds. I'm fully understand what need to be changed on client side and how generate *.delta and *.update files, but what i need for server side?
Just place files at some path, and somehow mystical way the application will find it.. or need some json script, which protocol need to use, how app retrieve list of files/information from server...
Thanks in advance.

ElArchibald said:
Hey guys. I want add support OTA in my builds. I'm fully understand what need to be changed on client side and how generate *.delta and *.update files, but what i need for server side?
Just place files at some path, and somehow mystical way the application will find it.. or need some json script, which protocol need to use, how app retrieve list of files/information from server...
Thanks in advance.
Click to expand...
Click to collapse
just add them to web server.

[GUIDE] How to convert Chinese roms based to International [TouchWiz]

[GUIDE] How to convert Chinese roms based to International [TouchWiz]
Requeriments
Chinese firmware/ROM that want convert
Official European/American firmware/ROM of the same device (Ex: SM-G920F)
Tickle my Android or Advanced Apktool (Easy way)
Be sure to install WinRAR and Notepad+ in your PC
Patience, Time and Concentration
So now we can start to convert
- Create a folder with the chinese base and create another for the international one
- Decompress the 2 firmwares in the correspond folder
- Now in system delete all the chinese folders related like this: *Much of the apps contain this "chn" in his name
/system
/system/chn_sipdb (Chinese Keyboard)
/system/SOGOUDB (Chinese Keyboard)
/system/festival
/system/finder_cp
/system/CSC (Due to is configured to China region) *Backup features.xml and others.xml
/system/preload (It contain chinese store, depending of firmware)
/system/app
/system/app/CMAWeatherPhone201X
/system/app/ChinaHolidayProvider
/system/app/com.samsung.festival.chinadefault_* (If exist, delete all the folders with this name)
/system/app/SamsungChineseIMEvX
/system/app/EventNotificationPhase3
/system/app/Festivalchinadefault
/system/app/GreetingCard
/system/app/SLocation and /system/lib/slocation
/system/app/MyEventWidget
/system/app/InCallUI
/system/app/SearchBoxBaidu_OPEN
/system/app/YellowPage (Could be located in priv-app too)
/system/priv-app
/system/priv-app/AMapNetworkLocation, XNetworkLocation_Baidu, (If exist)
/system/priv-app/SAssistant (If exist)
/system/priv-app/EventCenter
/system/priv-app/SMusicChn
/system/priv-app/BstSpamCallService
/system/priv-app/SVoice* (Delete all SVoice related files including VoiceWakeUp)
/system/priv-app/SecContacts_X_CHN and /system/priv-app/SecMms_X_Chn
/system/etc and /system/lib
/system/etc/gps.conf and system/etc/gps.xml
/system/lib/slocation
- After to delete all the chinese bload related is time to add all the international apps (/system/app and /system/priv-app) and the 2 gps files (system/etc) that we delete it in the last step
- Now is time to decompile so is necessary Tickle my Android or Advanced Apktool
So from your chinese and international firmware/rom take /system/framework/framework-res.apk and decompile (Install the frameworks for dont get error while decompile)
- If dont get error we can continue, from international framework take all /framework-res.apk/res/raw-xx and /framework-res.apk/res/values-xx folders and copy to chinese framework without overwrite existent files
- Then go to /framework-res.apk/res/values folder and open arrays.xml
Search:
HTML:
config_locationProviderPackageNames
And replace the whole string-array by this:
HTML:
<string-array name="config_locationProviderPackageNames">
<item>com.google.android.gms</item>
<item>com.android.location.fused</item>
<item>com.amap.android.ams</item>
<item>com.amap.android.location</item>
<item>com.baidu.map.location</item>
</string-array>
Save it and open strings.xml
Search:
HTML:
config_networkLocationProviderPackageName
And replace the whole string by this:
HTML:
<string name="config_networkLocationProviderPackageName">@null</string>
Search:
HTML:
config_geocoderProviderPackageName
And replace the whole string by this:
HTML:
<string name="config_geocoderProviderPackageName">@null</string>
NOTE: In some custom roms like aurora, some extra features are added in /framework-res.apk/res/values/arrays.xml and /framework-res.apk/res/values/strings.xml so search at final of the xml if exist chinese strings, if exist so translated it, can use google translator if dont understand.
- Save it and recompile the chinese framework-res.apk
Now decompile android.policy.jar (Lollipop), services.jar (Marsmallow) from chinese firmware/rom
Lollipop
- Decompile android.policy.jar with Tickle my Android or any tool that decompile classes.dex
- Go to android.policy.jar/smali/com/android/internal/policy/impl and open GlobalActions$99.smali and GlobalActions$SinglePressAction.smali
- Chinese strings are decoded in unicode so u need search this with notepad+ "\u"
- In GlobalActions$99.smali search
HTML:
const-string v2, "\u
Replace "\u..." by:
HTML:
const-string v2, "Reboot Options"
- In GlobalActions$SinglePressAction.smali search
HTML:
const-string v2, "\u
Replace "\u..." by: *Some lines above u can see the correct order, but almost always this is the order
HTML:
const-string v2, "Reboot"
HTML:
const-string v2, "Hot Reboot"
HTML:
const-string v2, "Download"
HTML:
const-string v2, "Recovery"
HTML:
const-string v2, "Safe Mode"
- Save and recompile back android.policy.jar, be sure that the modified date is different and more recent than original, u can check it open the compiled file with winrar, because some android tools don't compile correctly the .jar files
*Updating guide..:

Reserved

Reserved

Great thread
I will try keep it updated with changes needed

Isn't it possible to just flash an european ROM via Odin?

Checkit53 said:
Isn't it possible to just flash an european ROM via Odin?
Click to expand...
Click to collapse
No You Will BRICK your Device

Ale95 said:
[GUIDE] How to convert Chinese roms based to International [TouchWiz]
Requeriments
Chinese firmware/ROM that want convert
Official European/American firmware/ROM of the same device (Ex: SM-G920F)
Tickle my Android or Advanced Apktool (Easy way)
Be sure to install WinRAR and Notepad+ in your PC
Patience, Time and Concentration
So now we can start to convert
- Create a folder with the chinese base and create another for the international one
- Decompress the 2 firmwares in the correspond folder
- Now in system delete all the chinese folders related like this: *Much of the apps contain this "chn" in his name
/system
/system/chn_sipdb (Chinese Keyboard)
/system/SOGOUDB (Chinese Keyboard)
/system/festival
/system/finder_cp
/system/CSC (Due to is configured to China region) *Backup features.xml and others.xml
/system/preload (It contain chinese store, depending of firmware)
/system/app
/system/app/CMAWeatherPhone201X
/system/app/ChinaHolidayProvider
/system/app/com.samsung.festival.chinadefault_* (If exist, delete all the folders with this name)
/system/app/SamsungChineseIMEvX
/system/app/EventNotificationPhase3
/system/app/Festivalchinadefault
/system/app/GreetingCard
/system/app/SLocation and /system/lib/slocation
/system/app/MyEventWidget
/system/app/InCallUI
/system/app/SearchBoxBaidu_OPEN
/system/app/YellowPage (Could be located in priv-app too)
/system/priv-app
/system/priv-app/AMapNetworkLocation, XNetworkLocation_Baidu, (If exist)
/system/priv-app/SAssistant (If exist)
/system/priv-app/EventCenter
/system/priv-app/SMusicChn
/system/priv-app/BstSpamCallService
/system/priv-app/SVoice* (Delete all SVoice related files including VoiceWakeUp)
/system/priv-app/SecContacts_X_CHN and /system/priv-app/SecMms_X_Chn
/system/etc and /system/lib
/system/etc/gps.conf and system/etc/gps.xml
/system/lib/slocation
- After to delete all the chinese bload related is time to add all the international apps (/system/app and /system/priv-app) and the 2 gps files (system/etc) that we delete it in the last step
- Now is time to decompile so is necessary Tickle my Android or Advanced Apktool
So from your chinese and international firmware/rom take /system/framework/framework-res.apk and decompile (Install the frameworks for dont get error while decompile)
- If dont get error we can continue, from international framework take all /framework-res.apk/res/raw-xx and /framework-res.apk/res/values-xx folders and copy to chinese framework without overwrite existent files
- Then go to /framework-res.apk/res/values folder and open arrays.xml
Search:
HTML:
config_locationProviderPackageNames
And replace the whole string-array by this:
HTML:
<string-array name="config_locationProviderPackageNames">
<item>com.google.android.gms</item>
<item>com.android.location.fused</item>
<item>com.amap.android.ams</item>
<item>com.amap.android.location</item>
<item>com.baidu.map.location</item>
</string-array>
Save it and open strings.xml
Search:
HTML:
config_networkLocationProviderPackageName
And replace the whole string by this:
HTML:
<string name="config_networkLocationProviderPackageName">@null</string>
Search:
HTML:
config_geocoderProviderPackageName
And replace the whole string by this:
HTML:
<string name="config_geocoderProviderPackageName">@null</string>
NOTE: In some custom roms like aurora, some extra features are added in /framework-res.apk/res/values/arrays.xml and /framework-res.apk/res/values/strings.xml so search at final of the xml if exist chinese strings, if exist so translated it, can use google translator if dont understand.
- Save it and recompile the chinese framework-res.apk
Now decompile android.policy.jar (Lollipop), services.jar (Marsmallow) from chinese firmware/rom
Lollipop
- Decompile android.policy.jar with Tickle my Android or any tool that decompile classes.dex
- Go to android.policy.jar/smali/com/android/internal/policy/impl and open GlobalActions$99.smali and GlobalActions$SinglePressAction.smali
- Chinese strings are decoded in unicode so u need search this with notepad+ "\u"
- In GlobalActions$99.smali search
HTML:
const-string v2, "\u
Replace "\u..." by:
HTML:
const-string v2, "Reboot Options"
- In GlobalActions$SinglePressAction.smali search
HTML:
const-string v2, "\u
Replace "\u..." by: *Some lines above u can see the correct order, but almost always this is the order
HTML:
const-string v2, "Reboot"
HTML:
const-string v2, "Hot Reboot"
HTML:
const-string v2, "Download"
HTML:
const-string v2, "Recovery"
HTML:
const-string v2, "Safe Mode"
- Save and recompile back android.policy.jar, be sure that the modified date is different and more recent than original, u can check it open the compiled file with winrar, because some android tools don't compile correctly the .jar files
*Updating guide..:
Click to expand...
Click to collapse
Excellent guide make one guide for xperia cs39h.

Sony developers said:
Excellent guide make one guide for xperia cs39h.
Click to expand...
Click to collapse
A) Would it kill you to be nicer? You catch more flies with honey than with vinegar.
B) Why don't YOU use what he gave you and try to modify it to work on your phone? Then you can post a tutorial to help out others as well
C) Why did you quote the WHOLE OP

Any chance this would work on a locked bootloader, though we have root, such as the s7?

Is it possible to convert the firmware Galaxy Folder 2 (SM-G1600)?
https://drive.google.com/file/d/0B2QhEXa2ySgkNTFFX1R2RnRCN2M/view?usp=sharing

Nice guide! Bro!

Nice guide.
I have a 1 question. How to remove Chinese clock date from Notification Header?
{
"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"
}

i have a marshmallow china rom
. but not deodexed, original stock. how to edit services.jar and framework... without deodexing whole roms

Garry050 said:
Nice guide.
I have a 1 question. How to remove Chinese clock date from Notification Header?
Click to expand...
Click to collapse
Its in system ui
Compare dateview smali with stock one