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

[ROM] LOL v. 1.4.2 (with kernel 2.2.2+oc+lagfix)(+ how to create powermenu on LGP500)

Hello everybody, this is my first homemade ROM and everything started more like a joke.. (that’s the reason of its name.. ) rather than because of the necessity of a different ROM - I just wanted to experiment a bit in order to improve my knowledge!
The Void (thanks to Noejn) I was using before was working flawlessly, but I was curious to learn the procedure of cooking my own, so I tried, and when a problem showed up I resolved them.. it was a great way to learn something new!
First I made it for personal use only, then talking to my friends on an Italian android forum they wanted to try it, so they became my beta testers (MicheyKnox since the first day and NioBee from the second on).
During the last week many other users installed the Rom and I made some minor bug fixes and improvements and now it’s ready to be published here…!
But let’s go to the TECHNICAL SPECIFICATIONS:
* based on the v10q (Froyo 2.2.2)
* rom deodexed
* zipaligned
* root + superuser + busybox
* a2sd (darktremor script) + dalvik-cache on ext partition
* HW acceleration by default enabled
* Jit by default enabled
* Kernel froyo 2.2.2 recompiled by me with oc+lagfix (thx to drellisdee and mik_os)
* CPU automatically set 245/729/interactive
* gingerbread keyboard
* adw.launcher + adwnotifier
* customized theme with circular battery
* updated Google apps
* also includes: terminal emulator, OI file manager
* customization scripts: appinst and cpuclock
* customized POWERMENU able to reboot the phone or reboot directly in recovery
* BaBa (Burning Apple Boot Animation)
* wifi power (set by default to 20 dBm, edit the script /system/etc/setwifi.sh for modify this value)
* support for wlan wpa adhoc
* market hack (the market will seem that you are using Froyo 2.2)
BaBa is a Boot animation which is made of two different animations I found on XDA dimensions and timings where adapted in order to fit our needs (thanks to MickeyKnox )
Some apps like facebook, twitter and layar were removed, they can easily be installed through the Marked!
Removed: AppAdvisor and LG update advisor.
Other apps removed:
Code:
AIME.apk (LG Keyboard)
AnalogClockWidget.apk
BookmarksWidget.apk
CalendarWidget.apk
CarHome.apk
CarHomeLauncher.apk
ClockWeatherWidget.apk
DigitalAlarmWidget.apk
DualClockWidget.apk
GenieWidget.apk (news and weather widget)
LGHome.apk (launcher LG)
MagicSmokeWallpapers.apk
MemoWidget.apk
MessageWidget.apk
PhotoWidget.apk
Protips.apk
VisualizationWallpapers.apk
ConnectionManagerWidget.apk
Email.apk
LiveWallpapers.apk
Talk.apk
For these apps I created a script that allows you to install or uninstall them in a very easy way, without the need of root explorer.
To open this script go to Terminal Emulator (installed by default) or use adb shell from your PC and write:
su
appinst
a menu will popup where you’ll find all the options, just follow the onscreen instructions.
(the script works taking its files from the LOL directory in your SD Card, so if you delete this directory, the script won’t work!)
With my second script: cpuclock you’ll be able to change the default frequency in LOL without the need of installing other apps, to use it go to Terminal Emulator or via adb shell from your PC and write
su
cpuclock
and then follow the onscreen instructions, all your settings will be available after you reboot your device.
DOWNLOAD LINKS:
LOL v 1.4.2 (multiupload)
md5: 648e91a9d8458039d4937c4911acaf82
INSTALLATION (please follow these steps carefully):
What you need: root + custom recovery
* Reboot into custom recovery (through 3-button combo)
* Partition SDcard (swap: 0, ext: 512 – or bigger if you like), convert ext2 to ext3
* wipe everything (data/factory, cache, dalvik-cache, ext, android_secure)
* Toggle PC-USB connection and copy the downloaded zip you wish to flash into the root of your SDcard; unplug afterwards
* flash from SDcard and choose the file you just copied
* reboot
On first boot it takes some minutes for the phone to load: DON’T PANIC! Wait for at least 5-6 minutes!
************************************************************
I prepared a zip with the scripts translated into English (the original scripts in the Rom are in Italian)
just download and flash over.
************************************************************
Thanks to MickeyKnox for beta testing, for BaBa and for the time spent together on msn while I was cooking
Thanks to NioBee for beta testing and for her tips and suggestions (and for this translation from Italian )
Thanks to the guys on XDA where I found the tools needed to cook my ROM (dsixda + others) and to mik_os for his fantastic kernel
original discussion (in Italian): androidworld.it
************* standalone kernel ***************
zip in AnyKernel Updater by Koush package
kernel 2.2.2 + oc + lagfix by mik_os/Der_Caveman
kernel 2.2.2 + oc + lagfix by LG
SCREENSHOTS:

a little how to
ok, i wrote a little tutorial on how to create a powermenu
sorry for my english
************************************************************************************************
for first step i used this tutorial (i only removed the option "donwload"):
http://forum.xda-developers.com/showthread.php?t=811532
(copied from thread above)
untermensch said:
Step 1.
the first thing we need to do is add string and image resources to framwork-res
for this example I am using a stock JI6 ROM your resource id's will be different
if on another ROM
use apk_manager to decompile framework-res
open "res\values\strings.xml" and add our string resources
Code:
<string name="reboot_recovery">Recovery</string>
<string name="reboot">Reboot</string>
save and close
open "res\values\public.xml" and assign our strings resource id's
scroll until you get to the end of the "<public type="string"" id list
note the id of the last string, in this example it is "10403c2" sometimes
the id's are out of order so search for "10403c2 + 1" or "10403c3"
if the next id is unused then we can start assigning id's to the strings
we added.
Code:
<public type="string" name="reboot_recovery" id="0x010403c3" />
<public type="string" name="reboot" id="0x010403c5" />
now is a good time to add the image resources so add your icons to
"res\drawable-hdpi"
and assign id's to them the same way we did for the strings
in this example, using the example icons in the zip file I had
Code:
<public type="drawable" name="reboot" id="0x010803aa" />
<public type="drawable" name="recovery" id="0x010803ab" />
save and close
now framework-res has the resources needed for this mod use
apk_manager to compile.
Click to expand...
Click to collapse
step 2: (This part is based on untermensch's tutorial to which i have made serveral changes to let it work on LG)
now we are going to add the extra options to the power menu
decompile android.policy.jar with baksmali
open com\android\internal\policy\impl\GlobalActions.smali and change the line 436 from
Code:
const/4 v0, 0x3
to
Code:
const/4 v0, 0x5
insert the following line at line 462 (the original line 462 becomes line 486)
(remember to change reboot and recovery's image/string id with the ones used in the first step)
Code:
const/4 v1, 0x3
new-instance v2, Lcom/android/internal/policy/impl/GlobalActions$7;
const v3, 0x10803e0 # reboot icon resource id
const v4, 0x104039d # 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
const/4 v1, 0x4
new-instance v2, Lcom/android/internal/policy/impl/GlobalActions$8;
const v3, 0x10803e1 # recovery icon resource id
const v4, 0x104039c # recovery string resource id
invoke-direct {v2, p0, v3, v4}, Lcom/android/internal/policy/impl/GlobalActions$8;-><init>(Lcom/android/internal/policy/impl/GlobalActions;II)V
aput-object v2, v0, v1
save and exit
(here starts my real job )
ok now copy GlobalActions$3.smali to GlobalActions$7.smali
edit GlobalActions$7.smali
search and replace all GlobalActions$3.smali to GlobalActions$7.smali
and change this line:
Code:
const/4 v1, 0x1
invoke-static {v0, v1}, Lcom/android/internal/app/ShutdownThread;->shutdown(Landroid/content/Context;Z)V
to
Code:
const/4 v1, 0x1
const-string v2, "now"
invoke-static {v0, v2, v1}, Lcom/android/internal/app/ShutdownThread;->reboot(Landroid/content/Context;Ljava/lang/String;Z)V
save and exit
now copy GlobalActions$3.smali to GlobalActions$8.smali
edit GlobalActions$8.smali
search and replace all GlobalActions$3.smali to GlobalActions$8.smali
and change this line:
Code:
const/4 v1, 0x1
invoke-static {v0, v1}, Lcom/android/internal/app/ShutdownThread;->shutdown(Landroid/content/Context;Z)V
to
Code:
const/4 v1, 0x1
const-string v2, "recovery"
invoke-static {v0, v2, v1}, Lcom/android/internal/app/ShutdownThread;->reboot(Landroid/content/Context;Ljava/lang/String;Z)V
save and exit
recompile android.policy.jar with smali
done

PaoloM70 said:
Hello everybody, this is my first homemade ROM
Click to expand...
Click to collapse
GREAT, glad to see you posted your Rom here...!!
I am using this rom since the very beginning, and I can only recommend it... give it a try!

FANTASTIC ROM great work is the BEST ROM I've never had, SPECTACULAR!

very very good rom grazie paolo

Hiya, well done m8!
....As Paolo said in his post, i've been betatester for LOL Rom.
Well this rom is absolutely stable, never had a crash since started to use it.
Scripts, reboot and recovery-reboot mods are a great add-on....
i never found something like this in any rom i tested in past.
I really hope our xda friends will appreciate this ROM as we do!!!
oki, be good.
Mickeyknox

good work man

Molto bella e velocissima!!!!!!!
Grazie Paolo

vicvic said:
Molto bella e velocissima!!!!!!!
Grazie Paolo
Click to expand...
Click to collapse
Vic i'm not sure (kidding) but i suppose u should write in english.... foreign guys wont understand italian....

Awsome!! Please, how you boot option into power-off menu?

you have to modify some xml in folder values in framework and the androidpolicy.jar

great works!!!

The_ERROR said:
Awsome!! Please, how you boot option into power-off menu?
Click to expand...
Click to collapse
i just modified the framework-res.apk and android.policy.jar
exact procedure I followed is hard to explain ...btw i started my work from this thread
http://forum.xda-developers.com/showthread.php?t=811532

I do get "preparing SD card"error(i'm ussin the 2gb card...

CrysiZ said:
I do get "preparing SD card"error(i'm ussin the 2gb card...
Click to expand...
Click to collapse
Do you get this error after having finished flashing?
I think the problem could be connected to app2sd...
usually it is not recommended to use it on lower class SD, better if class4 or higher..

So how kn i remove it?

very very good, thanks!

CrysiZ said:
So how kn i remove it?
Click to expand...
Click to collapse
I'm sorry, app2sd is part of the rom, and for the moment it's not possible to remove it without recompiling the whole...
But can you explain me WHEN exactly you get this error? During flash or afterwards? Did you manage to boot up the sistem at least once?

lol
excellent will give it a try. god with so many nand backups I am losing my train of thought.

Ye..it worked for 30 min or so and then it started to get this error.

[GUIDE] How to get Transparent App Drawer [Launcher2.apk or Trebuchet.apk]

Hi Guys,
I have been asked many times how I was able to do transparent app drawer.
Description:
Transparent app drawer by definition means you can see the homescreen wallpaper whilst in app drawer instead of the default black background.
Tools needed:
1) apktool
2) notepad++
3) 7zip
Files needed: (Depending on ROM type)
1) trebuchet.apk, or
2) Launcher2.apk
Steps [HOW TO]:
1) decompile trebuchet.apk or Launcher2.apk
2) go to \res\layout\apps_customize_pane.xml
replace android:background="#ff000000" with android:background="#00000000"
There are two instances in this file.
3) now SMALI CODE.
go to
\smali\com\cyanogenmod\trebuchet\
or
smali\com\android\launcher2\
4) open Launcher.smali and delete the following method: updateWallpaperVisibility
Also delete all its references in Launcher.smali and other smali files. Usually this method is referenced in Launcher$13.smali and Launcher$17.smali and AppsCustomizePagedView.smali
However, it could be different from file to file depending on how it was built from source. Therefore, to know the file names exactly, just use notepad++ and use Search in Files feature and search for updateWallpaperVisibility in the decompiled apk samli folder. It will tell you where this method is referenced.
Example of Smali:
Delete all this method starting from .method to .end mothod.
This code is in Launcher.smali.
.method updateWallpaperVisibility(Z)V
.locals 3
.parameter
.prologue
const/high16 v1, 0x10
.line 2322
if-eqz p1, :cond_1
move v0, v1
.line 2323
:goto_0
invoke-virtual {p0}, Lcom/android/launcher2/Launcher;->getWindow()Landroid/view/Window;
move-result-object v2
invoke-virtual {v2}, Landroid/view/Window;->getAttributes()Landroid/view/WindowManager$LayoutParams;
move-result-object v2
iget v2, v2, Landroid/view/WindowManager$LayoutParams;->flags:I
and-int/2addr v2, v1
.line 2325
if-eq v0, v2, :cond_0
.line 2326
invoke-virtual {p0}, Lcom/android/launcher2/Launcher;->getWindow()Landroid/view/Window;
move-result-object v2
invoke-virtual {v2, v0, v1}, Landroid/view/Window;->setFlags(II)V
.line 2328
:cond_0
return-void
.line 2322
:cond_1
const/4 v0, 0x0
goto :goto_0
.end method
Click to expand...
Click to collapse
Having done this deletion, use notepad++ to search for updateWallpaperVisibility
Use fine in files function in Notepadd++, it will tell you exactly where this method is referenced. Then delete all the lines containing this method reference.
Example:
invoke-virtual {p0, v0}, Lcom/android/launcher2/Launcher;->updateWallpaperVisibility(Z)V
Click to expand...
Click to collapse
so, you have to delete the above line completely, and also any lines in all smali files containing "updateWallpaperVisibility"
After deleting the method and all of its references, just compile the apk and make your flashsable zip.
I use APKTOOL and 7zip for that.
Example:
Before:
{
"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"
}
After:
Enjoy

wesamothman said:
Hi Guys,
I have been asked many times how I was able to do transparent app drawer.
Description:
Transparent app drawer by definition means you can see the homescreen wallpaper whilst in app drawer instead of the default black background.
Tools needed:
1) apktool
2) notepad++
3) 7zip
Files needed: (Depending on ROM type)
1) trebuchet.apk, or
2) Launcher2.apk
Steps [HOW TO]:
1) decompile trebuchet.apk or Launcher2.apk
2) go to \res\layout\apps_customize_pane.xml
replace android:background="#ff000000" with android:background="#00000000"
There are two instances in this file.
3) now SMALI CODE.
go to
\smali\com\cyanogenmod\trebuchet\
or
smali\com\android\launcher2\
4) open Launcher.smali and delete the following method: updateWallpaperVisibility
Also delete all its references in Launcher.smali and other smali files. Usually this method is referenced in Launcher$13.smali and Launcher$17.smali and AppsCustomizePagedView.smali
However, it could be different from file to file depending on how it was built from source. Therefore, to know the file names exactly, just use notepad++ and use Search in Files feature and search for updateWallpaperVisibility in the decompiled apk samli folder. It will tell you where this method is referenced.
After deleting the method and all of its references, just compile the apk and make your flashsable zip.
I use APKTOOL and 7zip for that.
Example:
Before:
After:
Enjoy
Click to expand...
Click to collapse
Superman™
---------- Post added at 07:25 PM ---------- Previous post was at 07:24 PM ----------
THis is nice
Superman™

Simple, usefull
Thanks for the tutorial, this really helped me, that's my first time modding.
I was looking for a transparent app drawer since i turn on my phone for the very first time.
THANK YOU
From france.

4) open Launcher.smali and delete the following method: updateWallpaperVisibility
Also delete all its references in Launcher.smali and other smali files. Usually this method is referenced in Launcher$13.smali and Launcher$17.smali and AppsCustomizePagedView.smali
However, it could be different from file to file depending on how it was built from source. Therefore, to know the file names exactly, just use notepad++ and use Search in Files feature and search for updateWallpaperVisibility in the decompiled apk samli folder. It will tell you where this method is referenced.
Click to expand...
Click to collapse
This confused me but i figured it out so i thought i might share incase others get confused as well.
To delete the method look in the Launcher.smali for a line that says ".method updateWallpaperVisibility" , delete everything after that until you get to ".end method" (make sure you delete the ".method updateWallpaperVisibility" and ".end method" line as well), to delete the references find each line that has "updateWallpaperVisibility" (using the "find in files" function in notepad++ as stated in OP) and delete the WHOLE LINE. after that recompile and sign the apk and put it into your phone

bfo12 said:
This confused me but i figured it out so i thought i might share incase others get confused as well.
To delete the method look in the Launcher.smali for a line that says ".method updateWallpaperVisibility" , delete everything after that until you get to ".end method" (make sure you delete the ".method updateWallpaperVisibility" and ".end method" line as well), to delete the references find each line that has "updateWallpaperVisibility" (using the "find in files" function in notepad++ as stated in OP) and delete the WHOLE LINE. after that recompile and sign the apk and put it into your phone
Click to expand...
Click to collapse
Deleting a method implicitly means all of it. From function header .method until .end.
I am glad you managed.
--------------------------------------
GT-N7000 - Note I
GT-N7100 - Note II
GT-N8000 - Note 10.1 3G
Motorola Xoom MZ601 - UMTS EURO

Hey, I don't get it at all, what to do here, is this windows os or android os :S (sry for my unknowledge :/ ) , and also don't get why would I need to use a laucher.apk when I already have a launcher on my CM9, I mean I just don't get it, do I modify the apk and then install it ? :/ Could you explain it to a beginner (who knows how to flash and root ) ?

CroVeXx said:
Hey, I don't get it at all, what to do here, is this windows os or android os :S (sry for my unknowledge :/ ) , and also don't get why would I need to use a laucher.apk when I already have a launcher on my CM9, I mean I just don't get it, do I modify the apk and then install it ? :/ Could you explain it to a beginner (who knows how to flash and root ) ?
Click to expand...
Click to collapse
-APK is android related.
-CM roms use trebuchet.apk while aokp uses launcher2.apk. modding way is the same for both. So you pick up the apk related to your rom type.
-then you follow the guide and make a flashable zip to install from recovery.
--------------------------------------
GT-N7000 - Note I
GT-N7100 - Note II
GT-N8000 - Note 10.1 3G
Motorola Xoom MZ601 - UMTS EURO

link to Trebuchet.apk
wesamothman said:
Hi Guys,
I have been asked many times how I was able to do transparent app drawer.
Description:
Transparent app drawer by definition means you can see the homescreen wallpaper whilst in app drawer instead of the default black background.
Tools needed:
1) apktool
2) notepad++
3) 7zip
Files needed: (Depending on ROM type)
1) trebuchet.apk, or
2) Launcher2.apk
Steps [HOW TO]:
1) decompile trebuchet.apk or Launcher2.apk
2) go to \res\layout\apps_customize_pane.xml
replace android:background="#ff000000" with android:background="#00000000"
There are two instances in this file.
3) now SMALI CODE.
go to
\smali\com\cyanogenmod\trebuchet\
or
smali\com\android\launcher2\
4) open Launcher.smali and delete the following method: updateWallpaperVisibility
Also delete all its references in Launcher.smali and other smali files. Usually this method is referenced in Launcher$13.smali and Launcher$17.smali and AppsCustomizePagedView.smali
However, it could be different from file to file depending on how it was built from source. Therefore, to know the file names exactly, just use notepad++ and use Search in Files feature and search for updateWallpaperVisibility in the decompiled apk samli folder. It will tell you where this method is referenced.
After deleting the method and all of its references, just compile the apk and make your flashsable zip.
I use APKTOOL and 7zip for that.
Example:
Before:
After:
Enjoy
Click to expand...
Click to collapse
Could you please paste a link to download original Trebuchet.apk, so that we can work on it? Thanks!

jago84 said:
Could you please paste a link to download original Trebuchet.apk, so that we can work on it? Thanks!
Click to expand...
Click to collapse
The original trebuchet.apk differs from rom to rom on how it was built from source. But you can get it from cm10. It is default launcher in cm10.
If you use another trebuchet from another rom of a different device, it might not work with your device.
--------------------------------------
GT-N7000 - Note I
GT-N7100 - Note II
GT-N8000 - Note 10.1 3G
Motorola Xoom MZ601 - UMTS EURO

I get an error rebuilding apk: integer types not allowed, referred to the 00000000 value of background color...

gpvecchi said:
I get an error rebuilding apk: integer types not allowed, referred to the 00000000 value of background color...
Click to expand...
Click to collapse
This error comes if your aapt of your apktool is not referring to the correct framework. So you have to get the framework apk file from the same rom where you got the launcher or trebuchet and install it in apktool first
Apktool -f framework-res.apk and then decomplile and do your changes and then build it.
-------------------------
Omega's Team Member
-------------------------
Devices:
---------
GT-N7000 - Note I
GT-N7100 - Note II
GT-N8000 - Note 10.1 3G
Motorola Xoom MZ601 - UMTS EURO

Ok... I don't understand the .smali part so I have done it wrong and I can't compile apk because I have edited somehow wrong the .smali files.. :/

manumanfred said:
Ok... I don't understand the .smali part so I have done it wrong and I can't compile apk because I have edited somehow wrong the .smali files.. :/
Click to expand...
Click to collapse
Use notepad++ to search for the method name i mentioned in op. Delete the method all if it and all the lines that refers to it. You have to do this in all smali files that have this reference. Use notepad++ search in files function to search for its all occurences. Or send me the apk and i will see.
-------------------------
Omega's Team Member
-------------------------
Devices:
---------
GT-N7000 - Note I
GT-N7100 - Note II
GT-N8000 - Note 10.1 3G
Motorola Xoom MZ601 - UMTS EURO

wesamothman said:
Use notepad++ to search for the method name i mentioned in op. Delete the method all if it and all the lines that refers to it. You have to do this in all smali files that have this reference. Use notepad++ search in files function to search for its all occurences. Or send me the apk and i will see.
-------------------------
Omega's Team Member
-------------------------
Devices:
---------
GT-N7000 - Note I
GT-N7100 - Note II
GT-N8000 - Note 10.1 3G
Motorola Xoom MZ601 - UMTS EURO
Click to expand...
Click to collapse
OK Thanks! but I use Linux to decompile and recompile + sign & to zipalign apps. so I use Gedit to edit .xml, .smali and other files.
But the issue is that I don't understand .smali files at all!
I can find the lines but I don't know which is the last line which is needed to be deleted, is it from .method x to .method y or to somewhere .line xy or what... :/

manumanfred said:
OK Thanks! but I use Linux to decompile and recompile + sign & to zipalign apps. so I use Gedit to edit .xml, .smali and other files.
But the issue is that I don't understand .smali files at all!
I can find the lines but I don't know which is the last line which is needed to be deleted, is it from .method x to .method y or to somewhere .line xy or what... :/
Click to expand...
Click to collapse
Soon, i will add the code here before and after so that you can do this...

wesamothman said:
Soon, i will add the code here before and after so that you can do this...
Click to expand...
Click to collapse
OK! Thank You!

manumanfred said:
OK! Thank You!
Click to expand...
Click to collapse
OP updated with example codes deletion of .smali files content. This should be straight forward now
In case you still have issues, let me know and I will be more than glad to assist you

Thank You!
It is easier now, but Nexus Launcher's (JB 4.2.2 JDQ39) Launcher.smali doesn't have:
.method updateWallpaperVibility
When I just put updateWallpaperVibility
then it is this one: (line 3117)
Code:
invoke-virtual {p0, v0}, Lcom/android/launcher2Launcher;->updateWallpaperVisibility(Z)V
.line 2691
invoke-virtual....
So it's different..
Anyway Thanks!

manumanfred said:
Thank You!
It is easier now, but Nexus Launcher's (JB 4.2.2 JDQ39) Launcher.smali doesn't have:
.method updateWallpaperVibility
When I just put updateWallpaperVibility
then it is this one: (line 3117)
Code:
invoke-virtual {p0, v0}, Lcom/android/launcher2Launcher;->updateWallpaperVisibility(Z)V
.line 2691
invoke-virtual....
So it's different..
Anyway Thanks!
Click to expand...
Click to collapse
Aha. This is for 4.2.2 jb. Okay. Send it to me and let me see

wesamothman said:
Aha. This is for 4.2.2 jb. Okay. Send it to me and let me see
Click to expand...
Click to collapse
OK, Thanks!
Here is the stock Launcher with rotation enabled:
http://forum.xda-developers.com/showthread.php?t=2145289

[HOW-TO]{GUIDE}Get Ultra Power Saving Mode and Settings menu of S5 to S4![5.0.1]

EDIT : Guide how to port UPSM on S4 on Post #10
First of all IM not responsible if anything happens to your phone, first back it up!
This mod is tested ONLY on i9506, but you can test it on other S4 mobiles and then tell me if it works
And it works only on Stock rooted official Lollipop build
1. Download the zip file Here
2. Extract the file SecSettings.apk.
3. Use a root explorer from your mobile to move the existing Secsettings file to your sd(for backup purposes)
4. Go to /system/priv-app/SecSettings/ and move the file SecSettings.apk to /storage/extSdCard/oldsec.apk
5. Copy the new SecSettings.apk file to your sd.
6. Navigate to /storage/extSdCard and move the new SecSettings.apk to /system/priv-app/SecSettings
7. Give permissions rw--r---r---
8. Reboot device
What you get
Advanced Power saving mode with grayscale mode
All the new lockscreen settings with popping colors
And more..
What is not working
Ultra power saving mode, but i will try to port it.
Random fc on sound settings and data settings. Trying to fix them
If it fails after reboot, or want to revert back restore the original SecSettings.apk

nikosdd said:
First of all IM not responsible if anything happens to your phone, first back it up!
This mod is tested ONLY on i9506, but you can test it on other S4 mobiles and then tell me if it works
And it works only on Stock rooted official Lollipop build
1. Download the zip file Here
2. Extract the file SecSettings.apk.
3. Use a root explorer from your mobile to move the existing Secsettings file to your sd(for backup purposes)
4. Go to /system/priv-app/SecSettings/ and move the file SecSettings.apk to /storage/extSdCard/oldsec.apk
5. Copy the new SecSettings.apk file to your sd.
6. Navigate to /storage/extSdCard and move the new SecSettings.apk to /system/priv-app/SecSettings
7. Give permissions rw--r---r---
8. Reboot device
What you get
Advanced Power saving mode with grayscale mode
All the new lockscreen settings with popping colors
And more..
What is not working
Ultra power saving mode, but i will try to port it.
If it fails after reboot, restore the original SecSettings.apk
Click to expand...
Click to collapse
Thank you very much!
I am waiting for the Ultra power saving mode:good: Really awesomme if it will work.
Thank You
---------- Post added at 03:43 PM ---------- Previous post was at 02:58 PM ----------
faouz said:
Thank you very much!
I am waiting for the Ultra power saving mode:good: Really awesomme if it will work.
Thank You
Click to expand...
Click to collapse

faouz said:
Thank you very much!
I am waiting for the Ultra power saving mode:good: Really awesomme if it will work.
Thank You
---------- Post added at 03:43 PM ---------- Previous post was at 02:58 PM ----------
Click to expand...
Click to collapse
Everything is working except for the sound it is force closing

FC
Thanks, but I have 4-5 FC... on some icons in settings. And the sound its doesnt work.
If you wipe cache and change in build.prop "ro.product.name=SM-N9000" you have the settings app working after reboot.
Tried on i9506 stock.

superpulosu said:
Thanks, but I have 4-5 FC... on some icons in settings. And the sound its doesnt work.
If you wipe cache and change in build.prop "ro.product.name=SM-N9000" you have the settings app working after reboot.
Tried on i9506 stock.
Click to expand...
Click to collapse
I saw the fc later and I'm trying to fix them. Superpulosu changing product name does nothing to the fc

nikosdd said:
I saw the fc later and I'm trying to fix them. Superpulosu changing product name does nothing to the fc
Click to expand...
Click to collapse
Will this work on i9500?

I don't know. I tested it on 9506. If you can test it and write here again for the result but remember to backup your original apk file!

Ok, sorry. You right it does not change nothing if you change build.prop
I had another settings mod and its not working with your settings app.
I have FC on battery, data usage and the sound bug... Maybe you can make it work.
Thanks for your work.

Right now i've managed to port Ultra Power Saving Mode, but when i find time,i will write the procedure right here, or if anyone wants to send me his services.jar file(Please only from deodexed roms, otherwise first deodex rom and then send me the jar file otherwise it will not work), and to give you the short details how to install it. First before you send me this file, open it with winrar or 7zip and see if inside is a file named classes.dex. If not,deodex your rom, if yes send me this file and the model of the phone of course

Ultra Power Saving Mode port
Alright here is the details of how to port UPSM on lollipop rom
First, be sure that you are on a deodexed rom, otherwise search to the XDA about how to deodex your rom(its easy)
Download ApkTool (attached zip file)
Download Emergency apps(attached zip file)
Pull from your phone the services.jar located in /system/frameworks
Open the file services.jar with 7zip or winrar and extract the file classes.dex to the root of apktool
Drag and drop the classes.dex to the cmd file Quick-Baksmali.cmd
Wait for it to finish
Open the newly created folder Classout and go to classout\com\android\server
Open with notepad++ or other text editor the file SystemServer.smali
Search with the keyword "emergency" and you will find 1 result.
Delete the following result starting from - and ending to ...
Code:
.method static final startEmergencyModeService(Landroid/content/Context;)V
.
.
.
.end method
Now add right here this code
Code:
.method static final startEmergencyModeService(Landroid/content/Context;)V
.registers 6
.parameter "context"
.prologue
.line 2194
:try_start_0
invoke-static {p0}, Lcom/sec/android/emergencymode/EmergencyManager;->getInstance(Landroid/content/Context;)Lcom/sec/android/emergencymode/EmergencyManager;
move-result-object v1
.line 2195
.local v1, emMgr:Lcom/sec/android/emergencymode/EmergencyManager;
invoke-virtual {v1}, Lcom/sec/android/emergencymode/EmergencyManager;->readyEmergencyMode()V
:try_end_7
.catch Ljava/lang/Exception; {:try_start_0 .. :try_end_7} :catch_8
.line 2200
.end local v1 #emMgr:Lcom/sec/android/emergencymode/EmergencyManager;
:goto_7
return-void
.line 2196
:catch_8
move-exception v0
.line 2197
.local v0, e:Ljava/lang/Exception;
const-string v2, "SystemServer"
new-instance v3, Ljava/lang/StringBuilder;
invoke-direct {v3}, Ljava/lang/StringBuilder;-><init>()V
const-string v4, "Starting emergency service failed: "
invoke-virtual {v3, v4}, Ljava/lang/StringBuilder;->append(Ljava/lang/String;)Ljava/lang/StringBuilder;
move-result-object v3
invoke-virtual {v3, v0}, Ljava/lang/StringBuilder;->append(Ljava/lang/Object;)Ljava/lang/StringBuilder;
move-result-object v3
invoke-virtual {v3}, Ljava/lang/StringBuilder;->toString()Ljava/lang/String;
move-result-object v3
invoke-static {v2, v3}, Landroid/util/Slog;->d(Ljava/lang/String;Ljava/lang/String;)I
goto :goto_7
.end method
Save this file, and drag n drop the hole folder Classout to the cmd file Quick-Smali.cmd
It will generate a new file named new-classes.dex
Open again services.jar with 7zip or winrar, delete the classes.dex file and insert this newly created dex file, rename it classes.dex and push this file to the device, overwriting the stock services.jar file
DO NOT forget to set permissions rw-r--r--
Copy all the files in the 1st attached zip to /system/apps/ and set the appropriate permissions
After this, you will be able to enable UPSM from the settings mod in post #1 and you can also add it to notification bar with SQLite editor
To do this you must go to settings storage,settings.DB,system and search for notification
Edit the following "notification_panel_active_app_list_for_reset" ,and after the last semicolon( add this
Code:
UltraPowerSaving;
Go to notification settings and restore the buttons and the U.Power saving button will appear
Reboot and everything will work if you followed the whole procedure right
What is not working
While in UPSM, you may not hear voice during a call. Trying to fix it. Stay on for an update

As for the Fc from the settings apk, im testing to see if it will work if i change and the settingsstorage and for now it looks stable.

what you actually did for grid menu ? can you share guide?

Any screenshots to the this new guide?

jagnik said:
what you actually did for grid menu ? can you share guide?
Click to expand...
Click to collapse
You mean for the settings apk?
michaelbelachev said:
Any screenshots to the this new guide?
Click to expand...
Click to collapse
Screenshots about how to install the new secsettings.apk or how to port UPSM? Im afraid that in every model of device, the services.jar is a bit different and the screenshots wont be correct.

nikosdd said:
EDIT : Guide how to port UPSM on S4 on Post #10
First of all IM not responsible if anything happens to your phone, first back it up!
This mod is tested ONLY on i9506, but you can test it on other S4 mobiles and then tell me if it works
And it works only on Stock rooted official Lollipop build
1. Download the zip file Here
2. Extract the file SecSettings.apk.
3. Use a root explorer from your mobile to move the existing Secsettings file to your sd(for backup purposes)
4. Go to /system/priv-app/SecSettings/ and move the file SecSettings.apk to /storage/extSdCard/oldsec.apk
5. Copy the new SecSettings.apk file to your sd.
6. Navigate to /storage/extSdCard and move the new SecSettings.apk to /system/priv-app/SecSettings
7. Give permissions rw--r---r---
8. Reboot device
What you get
Advanced Power saving mode with grayscale mode
All the new lockscreen settings with popping colors
And more..
What is not working
Ultra power saving mode, but i will try to port it.
If it fails after reboot, restore the original SecSettings.apk
Click to expand...
Click to collapse
Please create how to mod SecSettings.apk

Y3dx said:
Please create how to mod SecSettings.apk
Click to expand...
Click to collapse
Hello
You don't mod the secsettings file, you just change it with the file I give you to download. First remember to take a backup at your SD, or even better a nandroid backup. As I've mentioned it has some bugs and due to exams I don't have the required time to fix them in short time but I'm trying

Thanks for your great work. Any news about the FC in the settings app?

Problem solve!!!!!!!!!
I solve some problem..
download UPSM_fix form link.
and install new shealth.apk..................
Use this post for service.jar
http://forum.xda-developers.com/showpost.php?p=60192294&postcount=10
every problem solve...............
sorry I am new here............
thankx
UPSM_fix.zip
New_shealth.apk
setting fc fixed...........
Upsm_fix_v2
flash with cwm......

antugoogly said:
I solve some problem..
download UPSM_fix form link.
and install new shealth.apk..................
Use this post for service.jar
http://forum.xda-developers.com/showpost.php?p=60192294&postcount=10
every problem solve...............
sorry I am new here............
thankx
UPSM_fix.zip
New_shealth.apk
setting fc fixed...........
Upsm_fix_v2
flash with cwm......
Click to expand...
Click to collapse
what problem you actually fixed? Because S health is irrelevant to Settings ui and Ultra power saving mode(i guess so)

antugoogly said:
I solve some problem..
download UPSM_fix form link.
and install new shealth.apk..................
Use this post for service.jar
http://forum.xda-developers.com/showpost.php?p=60192294&postcount=10
every problem solve...............
sorry I am new here............
thankx
UPSM_fix.zip
New_shealth.apk
setting fc fixed...........
Upsm_fix_v2
flash with cwm......
Click to expand...
Click to collapse
antugoogly said:
I solve some problem..
download UPSM_fix form link.
and install new shealth.apk..................
Use this post for service.jar
http://forum.xda-developers.com/showpost.php?p=60192294&postcount=10
every problem solve...............
sorry I am new here............
thankx
UPSM_fix.zip
New_shealth.apk
setting fc fixed...........
Upsm_fix_v2
flash with cwm......
Click to expand...
Click to collapse
UPSM fix 2 is perfect but...
It's force close in lock screen widgets
{
"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"
}

[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