[TUTORIAL]Xposed module devlopment

Search This thread

samkpo

Senior Member
Sep 7, 2014
58
17
You can add more filtering to only alter parameters when you need, using these:

Name of the method calling the hooked method: param.method.getName()

Name of the class of the method calling the hooked method: param.thisObject.getClass().getName(),
Hi, thanks for the suggestions. I tried what you said but it didn't throw anything good.
This is the code:
Code:
try{
    XposedBridge.log("Declaring class: " + param.method.getDeclaringClass().getSimpleName() );
} catch (Exception e) {
    XposedBridge.log("Error: " + e.getMessage());
}

try{
    XposedBridge.log("Method name: " + param.method.getName() );
} catch (Exception e) {
    XposedBridge.log("Error: " + e.getMessage());
}

try{
    XposedBridge.log("Class name: " + param.thisObject.getClass().getName() );
} catch (Exception e) {
    XposedBridge.log("Error: " + e.getMessage());
}

try{
    XposedBridge.log("Declaring class name: " + param.thisObject.getClass().getDeclaringClass().getName() );
} catch (Exception e) {
    XposedBridge.log("Error: " + e.getMessage());
}

try{
    XposedBridge.log("Class canonical name: " + param.thisObject.getClass().getCanonicalName() );
} catch (Exception e) {
    XposedBridge.log("Error: " + e.getMessage());
}

And this is the result, for every call it's the same:

08-26 19:48:24.813 I/Xposed ( 4106): Declaring class: Typeface
08-26 19:48:24.814 I/Xposed ( 4106): Method name: create
08-26 19:48:24.832 I/Xposed ( 4106): Error: Attempt to invoke virtual method 'java.lang.Class java.lang.Object.getClass()' on a null object reference
08-26 19:48:24.832 I/Xposed ( 4106): Error: Attempt to invoke virtual method 'java.lang.Class java.lang.Object.getClass()' on a null object reference
08-26 19:48:24.832 I/Xposed ( 4106): Error: Attempt to invoke virtual method 'java.lang.Class java.lang.Object.getClass()' on a null object reference

The first two work, but they yield what I already know. The other three throw an exception.. :(
 
  • Like
Reactions: adlx.xda

adlx.xda

Inactive Recognized Developer
Feb 4, 2010
1,541
1,752
Madrid
Hi, thanks for the suggestions. I tried what you said but it didn't throw anything good.
This is the code:
Code:
try{
    XposedBridge.log("Declaring class: " + param.method.getDeclaringClass().getSimpleName() );
} catch (Exception e) {
    XposedBridge.log("Error: " + e.getMessage());
}

try{
    XposedBridge.log("Method name: " + param.method.getName() );
} catch (Exception e) {
    XposedBridge.log("Error: " + e.getMessage());
}

try{
    XposedBridge.log("Class name: " + param.thisObject.getClass().getName() );
} catch (Exception e) {
    XposedBridge.log("Error: " + e.getMessage());
}

try{
    XposedBridge.log("Declaring class name: " + param.thisObject.getClass().getDeclaringClass().getName() );
} catch (Exception e) {
    XposedBridge.log("Error: " + e.getMessage());
}

try{
    XposedBridge.log("Class canonical name: " + param.thisObject.getClass().getCanonicalName() );
} catch (Exception e) {
    XposedBridge.log("Error: " + e.getMessage());
}

And this is the result, for every call it's the same:



The first two work, but they yield what I already know. The other three throw an exception.. :(
Damn you're right, my mistake sorry I was wrong.

I think you need something like this:

Code:
StackTraceElement[] trace = Thread.currentThread().getStackTrace();

for (int i=6; i < trace.length; i++)

{

Log.i(TAG, trace[i].getClassName() + " " + trace[i].getMethodName());

}

Experiment with these and you might find the value of I that gives the values you expect.
 
  • Like
Reactions: samkpo

samkpo

Senior Member
Sep 7, 2014
58
17
Damn you're right, my mistake sorry I was wrong.

I think you need something like this:

Code:
StackTraceElement[] trace = Thread.currentThread().getStackTrace();

for (int i=6; i < trace.length; i++)

{

Log.i(TAG, trace[i].getClassName() + " " + trace[i].getMethodName());

}

Experiment with these and you might find the value of I that gives the values you expect.
I'm gonna try it [emoji6]

Enviado desde mi Moto G mediante Tapatalk
 

Kewkpad

Member
Jul 27, 2016
32
3
Been asking everywhere.. Cant get the clock example to work on my Samsung S7 Edge, howcome?

My guess is different classname or something since the hooking function does not run.
If so, what to do?

Full explanation about my problem: http://stackoverflow.com/questions/...work-hooking-samsung-s7-edge-system-processes

Edit, sorry! Was because of other modules.
Can you write an updated guide for Android Studio? I'd be willing to donate for that, seriously. So hard to find information about xposed development.
 
Last edited:

hamzahrmalik

Senior Member
May 31, 2013
1,658
2,020
Been asking everywhere.. Cant get the clock example to work on my Samsung S7 Edge, howcome?

My guess is different classname or something since the hooking function does not run.
If so, what to do?

Full explanation about my problem: http://stackoverflow.com/questions/...work-hooking-samsung-s7-edge-system-processes

Edit, sorry! Was because of other modules.
Can you write an updated guide for Android Studio? I'd be willing to donate for that, seriously. So hard to find information about xposed development.
Been meaning to do so for so long. Its been like a year. Maybe over this weekend I'll just add the setup for Studio, since the actual programming is of course the same

Sent from my A0001 using Tapatalk
 
  • Like
Reactions: nicesoni_ash

BatedUrGonnaDie

Senior Member
Oct 17, 2016
101
74
Not sure where else to post this but saw some similar questions in this thread and thought maybe someone could help.
I have an app that defines custom classes, and some methods take an array of these classes. I'm having issues hooking these methods because I can't get the correct parameters to pass to findAndHookMethod to find the method. I've tried using findClass to just use a reference to the class, Array.class, Object[].class, and a few others. Really hitting a wall with this and I can't seem to find the answer to this anywhere when I feel like it would be a common problem.
 

hamzahrmalik

Senior Member
May 31, 2013
1,658
2,020
Not sure where else to post this but saw some similar questions in this thread and thought maybe someone could help.
I have an app that defines custom classes, and some methods take an array of these classes. I'm having issues hooking these methods because I can't get the correct parameters to pass to findAndHookMethod to find the method. I've tried using findClass to just use a reference to the class, Array.class, Object[].class, and a few others. Really hitting a wall with this and I can't seem to find the answer to this anywhere when I feel like it would be a common problem.
Could you post a sample of some code

Sent from my A0001 using Tapatalk
 

BatedUrGonnaDie

Senior Member
Oct 17, 2016
101
74
Could you post a sample of some code

Sent from my A0001 using Tapatalk

This is the methods signature:
Code:
private void a(ChatMessageBadge[] paramArrayOfChatMessageBadge, String paramString, StringBuilder paramStringBuilder)
As a temporary workaround I hooked all methods with the name "a" and have been sorting by the primitive types and the length of the args.
 

hamzahrmalik

Senior Member
May 31, 2013
1,658
2,020
This is the methods signature:
Code:
private void a(ChatMessageBadge[] paramArrayOfChatMessageBadge, String paramString, StringBuilder paramStringBuilder)
As a temporary workaround I hooked all methods with the name "a" and have been sorting by the primitive types and the length of the args.
How are you trying to hook it

Sent from my A0001 using Tapatalk
 

awti

New member
Feb 17, 2017
1
0
issue with module loading

after installing the app and activating it..when I am rebooting my device its showing cannot load module in the logs
how will this issue be resolved?
 

RyogoNA

Senior Member
Jul 13, 2010
119
74
I have hooked to com.android.internal.policy.impl.PhoneWindowManager.interceptKeyBeforeQueueing().
I acquired storage dir path using Environment.getExternalStorageDirectory() and tried to do listFiles() but it returns null. Is there any way I can acquire files list?
 

bharat.f4

New member
Mar 31, 2017
3
1
help.

please help me change an integer value in framework-res.apk

Im using the current method to change minimum and maximum brightness levels, but this is not working. What am i doing wrong.

Code:
import de.robv.android.xposed.IXposedHookInitPackageResources;

public class Main implements IXposedHookInitPackageResources {
	public void handleInitPackageResources(XC_InitPackageResources.InitPackageResourcesParam resparam) {
		if (!resparam.packageName.equals("android"))
			return;
		XResources.setSystemWideReplacement("android", "integer", "config_screenBrightnessSettingMinimum", 1);
		XResources.setSystemWideReplacement("android", "integer", "config_screenBrightnessSettingMaximum", 200);
	}
}

Please help.
If possible, please post the method code to change a simple res/values/integers.xml setting in framework-res.apk
 

dape16

Senior Member
Jun 20, 2006
510
119
Compile an abandoned module for a newer SDK

I use this module:
https://xdaforums.com/xposed/modules/mod-disable-desk-dock-t2526496

It was originally developed for Jelly bean, but another user compiled it for both Lollipop and Marshmallow.

Now I have been trying to compile it for Xposed SDK 24 and 25, but with no luck. I have some developer skills and I have spent a lot of time reading all the Xposed documentation and doing tutorials and modifying the module to work with Nougat.
Now my device is running 8.1 so an version that is working with SDK 27 would be the best.

I would be very thankful if someone could give me some directions or info on how to do this project.
 

flamery

Senior Member
Feb 24, 2011
159
42
can we hook applications that are obsuficated by proguard? I assume so since it must be deobsuficated when it loads into memory but how can we find the hooks required first?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 118
    Iv'e recently started a blog on Xposed Module development. It goes through the basics for a beginner and explains in as much detail as possible. You can find it here

    http://xposedtutorial.blogspot.co.uk/p/tutorial-1-setting-up.html


    Edit: I've now decided to keep the tutorial on XDA. I might also keep a copy on the blog, not sure yet

    P.S: A lot of this tutorial is based on the original development tutorial which can be found here, credits to rovo89

    Tutorial 1 - Setting up

    There are a few requirements for making an Xposed Module.
    *Eclipse, or Java IDE of your choice, with Android SDK and devlopment enviornment set up. I'm not going to cover that in this tutorial
    *Knowledge of Java programming language
    *An android phone which supports Xposed, with Xposed installed and working for testing on
    *Some knowledge of Android development
    *Time
    *An idea of course

    For the purpose of this tutorial, we will be creating two modules (using two different features of the xposed bridge). The first will replace the clock in the status bar with a smiley face. The second will change the height of the navigation bar. I will be using Eclipse or Android Studio in this tutorial.

    Eclipse

    NEW: this tool will setup the project for you! http://xdaforums.com/showthread.php?t=2712825


    Firstly you must set up an Android project as normal. For the target API, use the latest available. Name the project Smiley Clock, and choose a package name.

    We won't need an Activity for this module, so don't create one

    1.png

    2.png


    Android Studio


    Firstly you must set up an Android project as normal. For the target API, use the latest available. Name the project Smiley Clock, and choose a package name.

    We won't need an Activity for this module, so don't create one



    OK, that's the project created. Now we need to make Xposed recognize this as a module. Add the following meta tags to your Android Manifest, within the Application tag

    Code:
    <meta-data
                android:name="xposedmodule"
                android:value="true" />
            <meta-data
                android:name="xposedminversion"
                android:value="30" />
            <meta-data
                android:name="xposeddescription"
                android:value="Add a smiley face" />

    3.png


    At this point you can run the application on your test device. It should show up in the Xposed Installer app as a module. Check the box to enable your module and reboot your device. Of course, the module won't do anything yet!

    A good idea at this point would be to add a new filter to your logcat to track error messages from Xposed.

    Studio: Go on Android Monitor (along bottom). Make a new filter and filter by tag name. The tag is "xposed"
    Eclipse:

    Add a filter named "Xposed" and filter by the tag name "Xposed"
    (picture is for Eclipse)
    4.png


    You will now see messages from the Xposed Framework

    5.png


    There will be an error for your module about xposed_init file, don't worry, getting to that!

    Make a new package (same as package name we used when making the Android Project) and within that package make a class. Call it anything, I'll call mine Main.

    6.png


    Secondly add the XposedBridge API jar. This can be found on this thread on XDA. Add the jar to the root directory of the project, NOT the lib directory.
    Eclipse: Right click - build path - add to build path. Do not export it in the Order and Export tab.

    Studio: Right click, add as library. Then go in gradle files and find build.gradle for the app module. Find the dependency which looks something like this
    compile files('src/main/java/com/hamzahrmalik/xposedtutorial/XposedBridgeApi-54.jar')
    and change the "compile" to "provided" so it is like
    provided files('src/main/java/com/hamzahrmalik/xposedtutorial/XposedBridgeApi-54.jar')

    Now create a file in the assets directory called xposed_init.
    Studio users:
    First you will need to make the assets directory. I think the easiest way is to first switch to "project files" view at the top of the navigation pane as shown below. Then create a folder inside src/main called assets. Then place the xposed_init in the assets folder.

    Inside this file, type:

    packagename.classname

    where packname is the name of your package and class name is the name of your class. So in my case I will type

    com.hamzah.smileyclock.Main

    This tells Xposed where to look for the code for the module. You file tree should now look like this

    7.png


    Now the project is set up. In the next tutorial, we will look at how Xposed works, this will help you understand how to make modules.

    Tutorial 2 - Brief introduction to how Xposed works

    This tutorial is not really a true tutorial (gasp!). It will outline some basic features of Xposed which will help you understand future tutorials.
    Xposed allows a developer to access and modify the code for system applications. For example, one useful feature is the "find and hook" feature. This allows a developer to find a method inside another application and add their own code after it. So you could find the method in the Android source code that alerts the user when the wrong pattern is entered, and then instruct the system to hook onto that method and edit the alert to say something else. Another thing that Xposed allows us to do is replace resources. This includes Strings dimensions, drawables and much more. So we could edit the dimension of the navigation bar height (which we will in later tutorials) by replacing the resource which tells it what height to be.

    The next tutorial, we will start exploring the Android code and see what methods to hook to replace the clock with a smiley face!

    Tutorial 3 - Exploring the target and modifying it

    Ok so at this point, you should have an Xposed mod thatdoes nothing. The next step is to work out exactly what we want it to do! We want it to edit the clock, by hooking the method (read the last tutorial for more informtion on this). So the first step is to find that method.

    So visit http://grepcode.com/project/repository.grepcode.com/java/ext/com.google.android/android/ in your browser to view Android's source code. If (in Android 4+) you browse to com.android.systemui.statusbar.policy.Clock.java
    you will find the class that controls the clock. In here, there is a handy method called updateClock() which ppears to be controlling what gets written to the TextView in the statusbar (this whole class extends TextView). Now if you know how to make Android apps (which you should) you will be familiar with TextView. We can manipulate this TextView by changing colour, text, font, size etc, as you could with a TextView in a normal Android app.

    Of course this was easy, but depending on exactly what you want your module to do, you may have to hook many methods. If you've ever modded APK's, you'll know what i mean ;)

    This was another short tutorial, in the next one we will start coding the module

    Tutorial 4 - The Code

    In this tutorial we can finally get to some code. Exciting right?
    OK so we now have the following information
    *We can hook methods using Xposed
    *There happens to be a method which writes text to the clock
    *We can hook this method to edit the text

    So first of all, fire up your eclipse workspace and have you Xposed class implement IXposedHookLoadPackage
    Then add unimplemented methods.
    Your class should now look like:

    Code:
    package com.hamzah.smileyclock;
    
    import de.robv.android.xposed.IXposedHookLoadPackage;
    import de.robv.android.xposed.callbacks.XC_LoadPackage.LoadPackageParam;
    
    public class Main implements IXposedHookLoadPackage {
    
     @Override
     public void handleLoadPackage(LoadPackageParam lpparam) throws Throwable {
      
     }
    
    }

    The method that we are overriding gets called every time the user or system opens an app. We can use the parameter of the method to check when systemui gets loaded, then hook into it and modify the clock. Easy right?

    Add this inside your method

    Code:
    if (!lpparam.packageName.equals("com.android.systemui"))//check if the package being loaded is systemUI
                return;
    //All code here is only called if it is indeed SystemUI
    So now we need our hook, add this code after the return:
    Code:
    findAndHookMethod("com.android.systemui.statusbar.policy.Clock", lpparam.classLoader, "updateClock", new XC_MethodHook() {
                @Override
                protected void afterHookedMethod(MethodHookParam param) throws Throwable {
                 
                }
     });

    NOTE: this will only work because updateClock doesn't need any parameters. If the method you want to hook does, see tutorial 9

    You must also add the following imports statements

    Code:
    import de.robv.android.xposed.IXposedHookLoadPackage;
    import de.robv.android.xposed.XC_MethodHook;
    import de.robv.android.xposed.callbacks.XC_LoadPackage.LoadPackageParam;
    import static de.robv.android.xposed.XposedHelpers.findAndHookMethod;

    Explanation: The findAndHookMethod is hooking onto com.android.systemui.statusbar.policy.Clock
    The afterHookedMethod allows us to add our own code after the system method is executed, so in this case, the code to add a smiley face will go here. The MethodHookParam allows us to modify the TextView of the method we are hooking. So we need to get hold of that TextView, add this code

    Code:
    TextView tv = (TextView) param.thisObject;

    This is the TextView containing the clock, whatever we do with this TextView at this point, will happen to the TextView in the statusbar, So now simply add

    Code:
    tv.setText(":)");

    This will replace the clock with a smiley face. Alternatively, use

    Code:
    tv.appendText(":)");

    to keep the time and add the smiley after it

    Now deploy the app to your test device, and reboot. You should see a smiley face in place of the clock!

    Full Code

    Code:
    package com.hamzah.smileyclock;
    
    import static de.robv.android.xposed.XposedHelpers.findAndHookMethod;
    import android.widget.TextView;
    import de.robv.android.xposed.IXposedHookLoadPackage;
    import de.robv.android.xposed.XC_MethodHook;
    import de.robv.android.xposed.callbacks.XC_LoadPackage.LoadPackageParam;
    
    public class Main implements IXposedHookLoadPackage {
    
     @Override
     public void handleLoadPackage(LoadPackageParam lpparam) throws Throwable {
      if (!lpparam.packageName.equals("com.android.systemui"))
                return;
      
       findAndHookMethod("com.android.systemui.statusbar.policy.Clock", lpparam.classLoader, "updateClock", new XC_MethodHook() {
                @Override
                protected void afterHookedMethod(MethodHookParam param) throws Throwable {
                 TextView tv = (TextView) param.thisObject;
                 tv.setText(":)");
                 
                }
     });
     }
    }

    That's it for SmileyClock, in the next tutorial, we will look at another feature of Xposed, that is, replacing resources, and will enable/disable the screen wake up on unplug and also edit the height of the system navigation bar.

    Tutorial 5 - Replacing Resources

    Xposed allows us to replace resources such as String, int, boolean, dimen, or even drawables. In this tutorial we will enable/disable screen wake-up on unplug and in the next one, replace the dimen of navigation bar height and width to make it half size. Simple resources like int and String can be replaced by passing the new value as a parameter but more complex ones like drawable and dimen must be referenced from your own resources. Don't worry, I'll explain it all!

    First, we will replace a boolean which tells the system whether or not to wake the screen on unplug. There is a boolean in the framework-res.apk (found in /system/framework) which tells the system this information. We can used Xposed to edit this value, without touching the APK. My phone's default is false so I'm going to make it true, if yours is already true, make it false to make it more noticeable. In a future tutorial, when we learn saving preferences, we will add the ability for the user to set the value. For now, it will be hard coded.

    Firstly set up a new project as in tutorial 1. Call it anything. Again, no activity or icon required, though you might want an icon anyway.

    Have your class implement IXposedHookZygoteInit

    and add unimplemented methods. This is called before anything else and we will use it for replacing our resource.

    Add this code inside the initZygote method
    Code:
    XResources.setSystemWideReplacement("android", "bool", "config_unplugTurnsOnScreen", false);

    android is the package name of framework-res, bool is the type of resource (boolean) "config_unplugTurnsOnScreen" is the variable we are replacing and false is the new value.

    Now when you run this module, enable and reboot, you should find that if you plug in a charger, turn off the screen, and unplug it, nothing will happen. If you were to change it to TRUE instead of FALSE, when you unplugged, it would wake the screen.

    In the text tutorial, we will replace the navigation bar height

    Tutorial 6 - Complex Resources

    In this tutorial we will change the height of the navigation bar to 36dp, normal is 48dp. Much is the same as last time, but there are a few differences. Once again, set up a new project. Have your module class implement IXposedHookZygoteInit once again. Also implement IXposedHookInitPackageResources
    Add the unimplemented methods.

    Make a new variable inside the initZygote method:
    Code:
    String MODULE_PATH = startupParam.modulePath;

    In the handleInitPackageResources method, add
    Code:
    if (!resparam.packageName.equals("android"))
    	         return;

    Now we know we are in the right package

    Add:

    Code:
    XModuleResources modRes = XModuleResources.createInstance(MODULE_PATH, resparam.res);

    Use CTRL-SHIFT-O in Eclipse to import the necessary packages.

    Next we need a dimen resource to forward as the height of the navigation bar. Make a new XML files inside /values called dimens.xml. Add this inside it

    Code:
        36dp

    Now all that's left is to forward this to be used. Add this code inside handleInitPackageResources

    Code:
    XResources.setSystemWideReplacement("android", "dimen", "navigation_bar_height", modRes.fwd(R.dimen.navigationbarSize));
    The first 3 parameters are the same as the ones in tutorial 5. The last one has the same function as in the las tutorial, but rather than passing a variable, we are forwarding a resource. This could also be done with drawables, I once made a module to replace all buttons on the navigation bar with the ones found on Xperia ROM's.

    At this point, when you deploy the module, enable it and reboot, your navigation bar should be noticeably smaller.

    In the next tutorial we will look at creating and user interfaces and saving data in ways that both interface and module can read and write to. We will be using the mod we made in tutorial 4, and allow the user to define text rather than have a smiley face.

    Tutorial 7 - User Interfaces and Preferences

    Open up the SmileyClock we made in Tutorial 4. We did not make an Activity so make one now, File>New>Android Activity. Make sure you make it a Launcher Activity. We need to widgets in our UI, a textbox and an Apply button. I'm not going to cover making these, just make sure you have a method called when the button is pressed. Make the EditText id "input" so it will be easier to follow the tutorial because that is what i am making mine.

    When the apply button is pressed in my case this method is called
    Code:
    public void apply(){
    EditText et = (EditText) findViewById(R.id.input);
    String input = et.getText().toString();
    }

    So now I have the user input as a String, I need to save it. Use Android SharedPreferences for this,

    Code:
    SharedPreferences pref = getSharedPreferences("user_settings", MODE_WORLD_READABLE);

    The mode world readable is crucial to allow the Xposed Module to read it, otherwise you will get permission denied. Now get the Editor and save this string as "user_text",
    Code:
    Editor editor = pref.edit();
    editor.putString("user_text", input);

    Now it is saved, we need the Xposed Module to read it. Switch back to the class containing the Xposed Module, the one we made in tutorial 4. Find this line:
    Code:
    tv.setText(":)");

    Instead, replace it with this
    Code:
    XSharedPreferences pref = new XSharedPreferences("com.hamzah.smileyclock", "user_settings");
    //Gets the shared preference 
    String text = pref.getString("user_text", "");
    //reads the value which is saves, using nothing as default value to use if nothing is saved
    tv.setText(text);
    //sets the text to saved value

    When you deploy this and set some text, that text should then appear in the status bar after the clock. Note that when you save this value, it will not change in the statusbar until you restart SystemUI. It might change when time changes, not sure.

    In the next tutorial we will cover modifying layouts

    Tutorial 8 - Modifying Layouts

    Xposed lets us modify layouts in other apps. In this tutorial, we will modify the navigation bar with various tweaks. Firstly we will make the background blue. So make a new Xposed Project and have your module class implement IXposedHookInitPackageResources. This gives is a parameter that can be used for modifying layouts. Add the unimplemented method and add this code inside the method

    Code:
     resparam.res.hookLayout("com.android.systemui", "layout", "navigation_bar", new XC_LayoutInflated() {
    	        @Override
    	        public void handleLayoutInflated(LayoutInflatedParam liparam) throws Throwable {
    	        	
    	        }
    	    });
    com.android.systemui is the package name for the app containing the navigation bar View, layout is the type of resource, navigation_bar is the View name as defined in /res/layout (of SystemUI.apk). Now we need to get a View object for the navigation bar. Add this code inside the overriden method

    Code:
             @Override
    	 public void handleLayoutInflated(LayoutInflatedParam liparam) throws Throwable {
             View navbar = (View) liparam.view.findViewById(
    	                    liparam.res.getIdentifier("nav_buttons", "id", "com.android.systemui"));
         }

    We have gotten the view using the findViewById method, and passing in the ids. We know the id is "nav_buttons" because if we look at /res/layouts/navigation_bar.xml in SystemUI.apk, we see this

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <com.android.systemui.statusbar.phone.NavigationBarView android:background="#ff000000" android:layout_width="fill_parent" android:layout_height="fill_parent"
      xmlns:android="http://schemas.android.com/apk/res/android"
      xmlns:systemui="http://schemas.android.com/apk/res/com.android.systemui">
        <FrameLayout android:id="@id/rot0" android:layout_width="fill_parent" android:layout_height="fill_parent">
            <LinearLayout android:orientation="horizontal" android:id="@id/nav_buttons" android:clipChildren="false" android:clipToPadding="false" android:layout_width="fill_parent" android:layout_height="fill_parent" android:animateLayoutChanges="true">
                <View android:visibility="invisible" android:layout_width="40.0dip" android:layout_height="fill_parent" android:layout_weight="0.0" />
                <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/back" android:layout_width="80.0dip" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_back" android:layout_weight="0.0" android:contentDescription="@string/accessibility_back" systemui:keyCode="4" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
                <View android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_weight="1.0" />
                <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/home" android:layout_width="80.0dip" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_home" android:layout_weight="0.0" android:contentDescription="@string/accessibility_home" systemui:keyCode="3" systemui:keyRepeat="false" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
                <View android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_weight="1.0" />
                <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/recent_apps" android:layout_width="80.0dip" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_recent" android:layout_weight="0.0" android:contentDescription="@string/accessibility_recent" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
                <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/menu" android:visibility="invisible" android:layout_width="40.0dip" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_menu" android:layout_weight="0.0" android:contentDescription="@string/accessibility_menu" systemui:keyCode="82" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
            </LinearLayout>
            <LinearLayout android:orientation="horizontal" android:id="@id/lights_out" android:visibility="gone" android:layout_width="fill_parent" android:layout_height="fill_parent">
                <ImageView android:layout_width="80.0dip" android:layout_height="fill_parent" android:layout_marginLeft="40.0dip" android:src="@drawable/ic_sysbar_lights_out_dot_small" android:scaleType="center" android:layout_weight="0.0" />
                <View android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_weight="1.0" />
                <ImageView android:layout_width="80.0dip" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_lights_out_dot_large" android:scaleType="center" android:layout_weight="0.0" />
                <View android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_weight="1.0" />
                <ImageView android:layout_width="80.0dip" android:layout_height="fill_parent" android:layout_marginRight="40.0dip" android:src="@drawable/ic_sysbar_lights_out_dot_small" android:scaleType="center" android:layout_weight="0.0" />
            </LinearLayout>
            <View android:layout_gravity="top" android:id="@id/deadzone" android:clickable="true" android:layout_width="fill_parent" android:layout_height="@dimen/navigation_bar_deadzone_size" />
        </FrameLayout>
        <FrameLayout android:id="@id/rot90" android:paddingTop="0.0dip" android:visibility="gone" android:layout_width="fill_parent" android:layout_height="fill_parent">
            [COLOR="Green"]<LinearLayout android:orientation="vertical" [COLOR="Red"]android:id="@id/nav_buttons"[/COLOR] android:clipChildren="false" android:clipToPadding="false" android:layout_width="fill_parent" android:layout_height="fill_parent" android:animateLayoutChanges="true">[/COLOR]
                <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/menu" android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="40.0dip" android:src="@drawable/ic_sysbar_menu_land" android:layout_weight="0.0" android:contentDescription="@string/accessibility_menu" systemui:keyCode="82" systemui:glowBackground="@drawable/ic_sysbar_highlight_land" />
                <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/recent_apps" android:layout_width="fill_parent" android:layout_height="80.0dip" android:src="@drawable/ic_sysbar_recent_land" android:layout_weight="0.0" android:contentDescription="@string/accessibility_recent" systemui:glowBackground="@drawable/ic_sysbar_highlight_land" />
                <View android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_weight="1.0" />
                <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/home" android:layout_width="fill_parent" android:layout_height="80.0dip" android:src="@drawable/ic_sysbar_home_land" android:layout_weight="0.0" android:contentDescription="@string/accessibility_home" systemui:keyCode="3" systemui:keyRepeat="false" systemui:glowBackground="@drawable/ic_sysbar_highlight_land" />
                <View android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_weight="1.0" />
                <com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/back" android:layout_width="fill_parent" android:layout_height="80.0dip" android:src="@drawable/ic_sysbar_back_land" android:layout_weight="0.0" android:contentDescription="@string/accessibility_back" systemui:keyCode="4" systemui:glowBackground="@drawable/ic_sysbar_highlight_land" />
                <View android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="40.0dip" android:layout_weight="0.0" />
            </LinearLayout>
            <LinearLayout android:orientation="vertical" android:id="@id/lights_out" android:visibility="gone" android:layout_width="fill_parent" android:layout_height="fill_parent">
                <ImageView android:layout_width="fill_parent" android:layout_height="80.0dip" android:layout_marginTop="40.0dip" android:src="@drawable/ic_sysbar_lights_out_dot_small" android:scaleType="center" android:layout_weight="0.0" />
                <View android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_weight="1.0" />
                <ImageView android:layout_width="fill_parent" android:layout_height="80.0dip" android:src="@drawable/ic_sysbar_lights_out_dot_large" android:scaleType="center" android:layout_weight="0.0" />
                <View android:visibility="invisible" android:layout_width="fill_parent" android:layout_height="fill_parent" android:layout_weight="1.0" />
                <ImageView android:layout_width="fill_parent" android:layout_height="80.0dip" android:layout_marginBottom="40.0dip" android:src="@drawable/ic_sysbar_lights_out_dot_small" android:scaleType="center" android:layout_weight="0.0" />
            </LinearLayout>
            <View android:layout_gravity="left" android:id="@id/deadzone" android:clickable="true" android:layout_width="@dimen/navigation_bar_deadzone_size" android:layout_height="fill_parent" />
        </FrameLayout>
        <View android:id="@id/rot270" android:visibility="gone" android:layout_width="fill_parent" android:layout_height="fill_parent" />
    </com.android.systemui.statusbar.phone.NavigationBarView>


    Now we can call methods we could normally call on a View object. Add
    Code:
    navbar.setBackgroundColor(Color.BLUE);

    When you run this on your phone, your navigation bar will be blue. Now of course you can also call other methods, such as adding in new TextView's or whatever. If you were to inspect the code more closely, you would find there are also ids called "home" "back" and "recent_apps". You could use these to mess around with the buttons, though I cannot imagine what!

    Tutorial 9 - Methods with parameters

    In an earlier tutorial, we covered hooking methods. But what if a method wants a parameter too?

    Say if i want to hook onCreate(Bundle savedInstances) in com.android.settings

    If i hook it using

    Code:
    findAndHookMethod("com.android.settings.Settings", lpparam.classLoader, "onCreate", new XC_MethodHook() {
                
     });

    It will throw a methodNotFound error. So we need to specify the parameters. The method wants a Bundle object. So add Bundle.class as a parameter

    Code:
    findAndHookMethod("com.android.settings.Settings", lpparam.classLoader, "onCreate", [B]Bundle.class[/B], new XC_MethodHook() {
                
     });

    Now lets pretend Bundle.class isnt in the SDK and is a system class so cant be referenced. I would use a String instead:

    "android.os.Bundle"

    Code:
    findAndHookMethod("com.android.settings.Settings", lpparam.classLoader, "onCreate", [B]"android.os.Bundle"[/B], new XC_MethodHook() {
                
     });
    5
    The next few tutorials are up,
    1-Setting Up
    2-Background Info on Xposed
    3-Exploring Your Target
    4-The Code
    3
    The full tutorial is now at the top of this thread and all future tutorials will be added to that post. I will also post another post on this thread when i add one so subscribers will get a message
    2
    Great guide! And Congratulations! You are on XDA Portal!

    I was compiling this guide in MS Word, but you did it first!

    Congrats again!
    2
    Nice Tutorials, but this what you've posted until now is already published by a lot of peoples (also on the offical GitHub-Page).
    It would be awesome if you show some other (non-public) Tutorials, e.g how to make a PreferenceMenu and use it ;)

    #KeepItUp

    In this tutorial i plan to explain every feature of Xposed thoroughly