• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Search This thread

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,594
Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Introduction


Recently it has dismayed me how, across the Android Community, people seem to feel that it's necessary to run a "Custom ROM" in order to get improvements and changes to your ROM. Of course, some of you know it's possible to modify the APK files directly to change things, but these changes need to be done every time your base ROM is updated. Once Samsung starts leaking out updates to 4.2 like a sieve, you guys will be all over them, needing to update your patches and tweaks every time.

Anyway, seeing this displeases me, as it encourages people to see "Custom ROMs" as a commodity, and something you consume. In essence, users were getting their "fix" of tweaks from their "chef", but not learning how to do it themselves, nor realising their beloved chef isn't doing anything magical. In fact, their chef is likely decompiling the applications, and using baksmali/apktool to take apart the app, hard-code in their changes, then rebuild it. This method has worked well for 3 years, but it's been in need of an update for some time.

The Enlightenment

Then I saw this thread by rovo89. That man deserves a beer for every Android user there is, for his work on the Xposed Framework! His and Tungstwenty's work on this has made it possible to modify the core Android system, without doing any actual modifying of applications.

OK... Why are you telling me this?

This invention seems to have pretty much gone unnoticed by the world. The reasons this is vastly superior to any other way of making modifications to apps and the system are:

  • Your modifications are not tied into a single version of the APK or app or framework. If the ROM is updated, the patch should still work perfectly on the new version of the app (this doesn't necessarily apply across major updates like 4.1 to 4.2, but should be fine across 4.1.0 to 4.1.2 style changes).
  • You are not actually modifying any files on the phone! If something goes wrong, you can just disable the support for the framework, and the tweaks will do nothing. As such, it's easier to get a working phone if something dies - in fact there is a ZIP placed on your SD for this very purpose. Just flash it in CWM and it will disable the framework.
  • As no actual files are being modified, it doesn't matter if your ROM is odexed, deodexed, or a bit of both (ie. certain apps deodexed, but frameworks odexed). With this, there is no reason to run a deodexed ROM, since you can change pretty much everything you want to without touching the raw files. So leave them as odex files and you'll not have any problems. Bear in mind we deodex to allow easier customisation, odexed is actually slightly faster, and removes the majority of the dexopt process on first boot.
  • No application signatures are modified, as the apps are not touched, so if you were to use this to modify an app like Maps or Gmail, you won't get issues when trying to update to a new version of the app via the market.

The only way this can succeed is for you to try it. I usually run a "custom ROM" on my phone. For the first time ever, I've been using a stock ROM for a significant period of time. On the Note2 in particular, Samsung is really getting good at this. But they're not perfect. And as such, I started to look at using this to perfect their work.

When you run a custom ROM, look at what you're getting, and ask yourself why it doesn't use this method. I've only made one little modification so far, but it's one that annoys me hugely! The blooming SMS -> MMS conversion when you try to write any form of prose in a text message. I cannot stand the limitation of SMS to 160 characters, so the ability to chain together messages is a godsend to me. Unfortunately though, Google and Samsung seem to like to restrict you to 3 SMS messages worth of text before converting to an MMS message. Which is wonderful, except when you have totally unlimited SMS, but pay for MMS. As such, I was finding my ability to communicate in my usual verbose way somewhat hindered by the messaging app.

Alas that is no longer an issue. If you want to get started, here's how.

OK... How do I use this?

  1. Download and install the APK file from this post - http://forum.xda-developers.com/showthread.php?t=1574401. I have tested it on the N7100, it works fine. Run it, install the framework, grant it root (yes, this requires root!), and reboot. I have mirrored the APK below just in case of issues.
  2. Download and install the APK modification you want from http://www.villainrom.co.uk/forum/microdownloads/
  3. When you get a notification about enabling the modification (after the APK is installed), tap that notification, and enable the plugin by ticking the box.
  4. Reboot your phone
  5. Go test your modification

If you have any issues with this, please paste the contents of /data/xposed/debug.log on a pastebin site or in
Code:
 tags.

[SIZE="5"][B]How can I make my own modifications like this?[/B][/SIZE]

Will post this a bit later, along with the source of this plugin. 

[SIZE="5"][B]References[/B][/SIZE]
[url]http://forum.xda-developers.com/showthread.php?t=1574401[/url]
[url=http://forum.xda-developers.com/member.php?u=4322181]Tungstwenty[/url]
[url=http://forum.xda-developers.com/member.php?u=4419114]Robo89[/url]

[SIZE="5"][B]Sources[/B][/SIZE]
You can find the sources for Xposed Framework at [url]https://github.com/rovo89[/url]
You can find the sources for all Xposed modifications I have made so far on Github:

[url=https://github.com/pulser/xposedSMStoMMS]Disable SMS -> MMS Conversion[/url]
[url=https://github.com/pulser/xposedDisableBatteryFullAlert]Disable 100% Battery Notification[/url]
[url=https://github.com/pulser/xposedEnableCallRecording]Enable Call Recording[/url]
[url=https://github.com/pulser/xposedScrollingLauncherWallpaper]Enable scrolling wallpaper in stock launcher[/url]
[url=https://github.com/pulser/xposedEmailTextColour]Make text in email app message list clearer to read (lighter) on the black background[/url]
 
Last edited:

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,594
Modifications

OK so a few people suggested an addon repository... I have got one sorted :)
Downloads

http://www.villainrom.co.uk/forum/microdownloads/

I've added some of mine so far, but I won't add other people's - they can add them themselves, and maintain them :)

This system is vastly superior to a stickied forum thread, as you can update your own modification (as a developer), and as a user, receive notifications if a modification is updated.

Developers

Use a general title that describes what your modification does. Put in a version string too. I tend to use the format 1.0, 1.1, 1.2 etc, but this is up to you. You can add Alpha or Beta or other designations if you wish.

For author, pop in your name or username. And enter a brief description of what the modification does (which will appear in the index)
Click Categories/Agreements, and select which category the modification falls under. If you think there's a category which should be added, let me know.

Under Full Description, you can enter a detailed description of your modification. Finally, under File Options, use File to Upload to select your APK file. You can optionally add an Image to Upload. The Use File URL should be set to no, and the File URL box left blank.

Users
  • There is no need to register an account to download files from the repository. If you wish to receive notifications of updates, you can register an account - just hit the red "Log in or Sign up" button - you can use a Twitter or Google account if you want, or just make a plain account. It makes no difference.
  • Head across to http://www.villainrom.co.uk/forum/microdownloads/ and have a look at the modifications you want.
  • Click watch file (at the bottom right) if you want notifications about updates to a modification
  • Click Report to report a modification for being malicious or problematic.
  • Click "add comment" to discuss or comment on the modification, or leave a "review" or feedback
  • Click on the stars under (0 votes) to leave a star rating on the modification, which will help generate most popular lists on the main page.

Click to see licence details of mine:


Feel free to use these as you wish, for non-commercial purposes. You may share these for personal use. Note that distribution in any kind of "package" or "custom ROM" is not personal use. Sending a friend a copy is personal use, feel free to do that and share the love.

Feel free to make changes to the source code of the modifications if you think you can improve them, provided you make your changes available in a similar manner. If you fix a bug or error, please send a pull request.

If you wish to use these commercially, please contact me. This includes in any "distribution package", be it a ROM, app, store, marketplace or other package. That's not in the spirit of this project, so get in touch with me and we'll discuss it.

Tl;dr:

End users, have fun, use these, enjoy them, share them, tweak them, just be sure to share your source changes and/or send a pull request if you improve something!

"Custom ROM" Developers, and anyone wanting to try to use these for commercial purposes: Don't. These are to encourage people to learn about these changes, so contact me if you want to do something else with them. Commercial use, including distribution in "Custom ROMs" is not permitted.
 
Last edited:

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,594
How to make your own such modification

This information is NOT complete. This example only uses 1 of about 10 different types of modification. I have spoken to rovo89 and he has said it would probably be possible to document this further. This example covers ONE usage case - I am going to override an entire method.

1. Create a new empty Android project in Eclipse.
2. Within the "application" section of your AndroidManifest.xml, add the following metadata:

Code:
        <meta-data android:name="xposedmodule" android:value="true"/>
        <meta-data android:name="xposedminversion" android:value="2.0rc1.*" />

3. Within the assets folder of the project, add a plain text file, "xposed_init". Within this, I have put

Code:
uk.co.villainrom.pulser.allowlongsms.AllowLongSMS

uk.co.villainrom.pulser.allowlongsms is the PACKAGE name of my Java package. AllowLongSMS is my class name. The purpose of this is to tell the Xposed Framework what to run.

4. Within AllowLongSMS.java (ie. the class name, with .java on the end), I put the following code:

PHP:
package uk.co.villainrom.pulser.allowlongsms; //this sets the package for our project, this is the first part of the value in xposed_init file in assets.

import de.robv.android.xposed.IXposedHookLoadPackage;
import de.robv.android.xposed.XC_MethodHook;
import de.robv.android.xposed.XC_MethodReplacement;
import de.robv.android.xposed.XposedBridge;
import de.robv.android.xposed.XposedHelpers;
import de.robv.android.xposed.callbacks.XC_LoadPackage.LoadPackageParam;

//above includes all the required parts of the xposed framework that we need here

public class AllowLongSMS implements IXposedHookLoadPackage {        //here we declare the class AllowLongSMS. We say it implements IXposedHookLoadPackage, as we want to make use of the hook-in on package load. Other options are available here for working with native libs etc, and resources, but I'm not using these right now.
	public static final String MY_PACKAGE_NAME = AllowLongSMS.class.getPackage()
			.getName();     //this doesn't do anything, I just left it here for if I needed to write logs and wanted to have the package name easily accessible.
	public static final String TAG = "PulserMmsTweak";   //same here, this doesn't do anything.

	@Override //we are going to override the method handleLoadPackage, if it exists further up the hierarchy
	public void handleLoadPackage(LoadPackageParam lpparam) throws Throwable { 
		//this method is called every time a package is loaded. We have a parameter that we're going to call lpparam, that is passed in, that relates to what package was loaded
		if (lpparam.packageName.equals("com.android.mms")) { //if the package that has just been loaded is called "com.android.mms" then
			ClassLoader classLoader = lpparam.classLoader; //create a classloader object that we can now use
			XC_MethodReplacement methodreplacer = new XC_MethodReplacement() {  //create a method replacer object, as we are going to REPLACE an entire method within the mms app.
				protected Object replaceHookedMethod( //we make an object here, that passes in the parameters of what to actually change
						XC_MethodHook.MethodHookParam paramAnonymousMethodHookParam)
						throws Throwable {
					return Integer.valueOf(255);  
					/* THIS IS THE IMPORTANT LINE
					 * This line returns the value 255. Why this happens won't make sense yet, but THIS is where you put your "new method" code.
					 * 
					*/
					
				}
			};
			XposedHelpers.findAndHookMethod("com.android.mms.MmsConfig",  //here we say that we want to find and hook into the method "getSMSToMmsTextThreshold" which is part of the class com.android.mms.MmsConfig. We then say that we're passing this to methodreplacer, which we defined earlier
					classLoader, "getSmsToMmsTextThreshold", methodreplacer);
		}
                //if the package wasn't com.android.mms, do nothing.

	}

}
 
Last edited:

simone201

Inactive Recognized Developer
Sep 21, 2010
4,756
4,896
Lecco
Thanks for continuing that amazing project pulser!!

I think i'm going to create some small apks for some stuff very soon (and release them of course).

Cool stuff as always pulser, keep it up :D
 
  • Like
Reactions: jager13

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,594
Thanks for continuing that amazing project pulser!!

I think i'm going to create some small apks for some stuff very soon (and release them of course).

Cool stuff as always pulser, keep it up :D

The original guys are not gone, was talking to them recently :)

There's scarce documentation so far on this, but I will see what else I can do with it... I might make post 2 a repository of these APKs for now...
 
  • Like
Reactions: victorator

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,594
Wow this is great post. While reading this it makes me learn something like what is going on in background.

Sent from my GT-N7100 using Tapatalk 2

That's the intention :) Glad it worked! This is about learning, and not just "using".

Sure, you can download the APK and use it, but that's no better than just downloading some zipkang ROM that claims it does everything including making your morning coffee... This is about taking a look at HOW it works too :) That way people can make their own tweaks and share them!
 

simone201

Inactive Recognized Developer
Sep 21, 2010
4,756
4,896
Lecco
The original guys are not gone, was talking to them recently :)

There's scarce documentation so far on this, but I will see what else I can do with it... I might make post 2 a repository of these APKs for now...

A small repo for APKs would be really cool and useful for users....

tell me if i can contribute in some ways (i'm an app dev mainly also)
 

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,594
A small repo for APKs would be really cool and useful for users....

tell me if i can contribute in some ways (i'm an app dev mainly also)

I will work something out (I can easily make a repository if this kicks off, so people can upload them and they appear).

TBH right now it's more a case of thinking up some ideas. For now, I can add anything people send into the second post (though I think it would be reasonable that we request source for all such modifications, just given the sheer ability to modify anything that this has...)

I can't think of enough things to tweak, we just need to work out WHAT people will like to modify, and implement it :)

I'll be a good example and put mine onto git shortly :)
 
  • Like
Reactions: jerdog

Tungstwenty

Senior Member
Nov 1, 2011
1,827
4,512
Hey folks,

I'm happy to see some new interest on Xposed.
I've been using it since rovo89 came up with this brilliant idea, and have to admit I was kind of sad to see not many saw its great potential.

Personally, I'm using a couple of hacks for my individual use, but if the community starts to be interested in the HOWs rather than merely nagging about the apks :p I guess I can try to make an effort to clean and share the code.

Please do ask away stuff, I'm eager to seeing this being used to its full potential :)

For now, please check the Tweakbox sources. While the code itself might no longer 100% apply to the most recent S2 stock roms, it's still a nice example of how the hacks can be done.
 

sunwee

Senior Member
May 8, 2009
517
60
this sounds great! like an universal (almost!) patching system. I hope more chef will write mods for this. man...wish i had taken some lessons in coding. :(

for a start, how about some of the often repeated annoyance in stock samsung that drives many to use custom roms just to get these functions:-

1) disable the scrolling quick setting panel when you open notification

2) 15 toggles as implement by guys like Wanam.

3) call recording (ok we got this already)

4) 4 way reboot menu

5) some kind of user definable custom battery graphics.
 
  • Like
Reactions: astoncheah

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,594
this sounds great! like an universal (almost!) patching system. I hope more chef will write mods for this. man...wish i had taken some lessons in coding. :(

for a start, how about some of the often repeated annoyance in stock samsung that drives many to use custom roms just to get these functions:-

1) disable the scrolling quick setting panel when you open notification

2) 15 toggles as implement by guys like Wanam.

3) call recording (ok we got this already)

4) 4 way reboot menu

5) some kind of user definable custom battery graphics.

Yeah this is pretty universal. I'd even remove the word "almost" tbh... :)

For 1, do you mean to disable the scroll animation so that it shows the leftmost icon (wifi) first?

2 is possible, I know samsung has done it on 4.2, is the custom implementation better?

3 is done like you said.

4 should be more than possible.

5 is definitely possible, at least via flashing the modification for the battery style you want...

Thank for the ideas :)
 

astoncheah

Inactive Recognized Developer
Mar 25, 2011
539
672
41
Penang
plus.google.com
i flash custom rom just because i need below few things

1.Call-Record. (done)
2.15 toggle, or maybe add NFC, S Beam, Multiwindow, Smart Stay as well
3.Louder Volume Speaker.
4.CRT Lock and Unlock Screen.
5.4 Way Reboot.
6.Unlimited Multi-Window

thanks for the good work and sharing.
 

DirkStorck

Senior Member
Sep 5, 2009
3,692
813
Hi. So glad to see that this amazing framework didn't "die" :)

I would have one question about the mods...
Ok its likely that for the same device they work on different bases of the rom like DLJ5, ELK4 am I right?
But does a mod that was made for lets say the Note 2 work on a SGS3 or must it be adapted?

Thanks !
 

pulser_g2

Admin Emeritus / Senior Recognized Developer
Nov 27, 2009
19,537
11,594
Hi. So glad to see that this amazing framework didn't "die" :)

I would have one question about the mods...
Ok its likely that for the same device they work on different bases of the rom like DLJ5, ELK4 am I right?
But does a mod that was made for lets say the Note 2 work on a SGS3 or must it be adapted?

Thanks !

If it's touchwiz then it should work - samsung seems to have unified a lot of it.

Jerdog used the SMS to mms patch fine on his s3.

It really just depends on the modification itself tbh...
 
  • Like
Reactions: DirkStorck

Top Liked Posts

  • There are no posts matching your filters.
  • 285
    Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

    Introduction


    Recently it has dismayed me how, across the Android Community, people seem to feel that it's necessary to run a "Custom ROM" in order to get improvements and changes to your ROM. Of course, some of you know it's possible to modify the APK files directly to change things, but these changes need to be done every time your base ROM is updated. Once Samsung starts leaking out updates to 4.2 like a sieve, you guys will be all over them, needing to update your patches and tweaks every time.

    Anyway, seeing this displeases me, as it encourages people to see "Custom ROMs" as a commodity, and something you consume. In essence, users were getting their "fix" of tweaks from their "chef", but not learning how to do it themselves, nor realising their beloved chef isn't doing anything magical. In fact, their chef is likely decompiling the applications, and using baksmali/apktool to take apart the app, hard-code in their changes, then rebuild it. This method has worked well for 3 years, but it's been in need of an update for some time.

    The Enlightenment

    Then I saw this thread by rovo89. That man deserves a beer for every Android user there is, for his work on the Xposed Framework! His and Tungstwenty's work on this has made it possible to modify the core Android system, without doing any actual modifying of applications.

    OK... Why are you telling me this?

    This invention seems to have pretty much gone unnoticed by the world. The reasons this is vastly superior to any other way of making modifications to apps and the system are:

    • Your modifications are not tied into a single version of the APK or app or framework. If the ROM is updated, the patch should still work perfectly on the new version of the app (this doesn't necessarily apply across major updates like 4.1 to 4.2, but should be fine across 4.1.0 to 4.1.2 style changes).
    • You are not actually modifying any files on the phone! If something goes wrong, you can just disable the support for the framework, and the tweaks will do nothing. As such, it's easier to get a working phone if something dies - in fact there is a ZIP placed on your SD for this very purpose. Just flash it in CWM and it will disable the framework.
    • As no actual files are being modified, it doesn't matter if your ROM is odexed, deodexed, or a bit of both (ie. certain apps deodexed, but frameworks odexed). With this, there is no reason to run a deodexed ROM, since you can change pretty much everything you want to without touching the raw files. So leave them as odex files and you'll not have any problems. Bear in mind we deodex to allow easier customisation, odexed is actually slightly faster, and removes the majority of the dexopt process on first boot.
    • No application signatures are modified, as the apps are not touched, so if you were to use this to modify an app like Maps or Gmail, you won't get issues when trying to update to a new version of the app via the market.

    The only way this can succeed is for you to try it. I usually run a "custom ROM" on my phone. For the first time ever, I've been using a stock ROM for a significant period of time. On the Note2 in particular, Samsung is really getting good at this. But they're not perfect. And as such, I started to look at using this to perfect their work.

    When you run a custom ROM, look at what you're getting, and ask yourself why it doesn't use this method. I've only made one little modification so far, but it's one that annoys me hugely! The blooming SMS -> MMS conversion when you try to write any form of prose in a text message. I cannot stand the limitation of SMS to 160 characters, so the ability to chain together messages is a godsend to me. Unfortunately though, Google and Samsung seem to like to restrict you to 3 SMS messages worth of text before converting to an MMS message. Which is wonderful, except when you have totally unlimited SMS, but pay for MMS. As such, I was finding my ability to communicate in my usual verbose way somewhat hindered by the messaging app.

    Alas that is no longer an issue. If you want to get started, here's how.

    OK... How do I use this?

    1. Download and install the APK file from this post - http://forum.xda-developers.com/showthread.php?t=1574401. I have tested it on the N7100, it works fine. Run it, install the framework, grant it root (yes, this requires root!), and reboot. I have mirrored the APK below just in case of issues.
    2. Download and install the APK modification you want from http://www.villainrom.co.uk/forum/microdownloads/
    3. When you get a notification about enabling the modification (after the APK is installed), tap that notification, and enable the plugin by ticking the box.
    4. Reboot your phone
    5. Go test your modification

    If you have any issues with this, please paste the contents of /data/xposed/debug.log on a pastebin site or in
    Code:
     tags.
    
    [SIZE="5"][B]How can I make my own modifications like this?[/B][/SIZE]
    
    Will post this a bit later, along with the source of this plugin. 
    
    [SIZE="5"][B]References[/B][/SIZE]
    [url]http://forum.xda-developers.com/showthread.php?t=1574401[/url]
    [url=http://forum.xda-developers.com/member.php?u=4322181]Tungstwenty[/url]
    [url=http://forum.xda-developers.com/member.php?u=4419114]Robo89[/url]
    
    [SIZE="5"][B]Sources[/B][/SIZE]
    You can find the sources for Xposed Framework at [url]https://github.com/rovo89[/url]
    You can find the sources for all Xposed modifications I have made so far on Github:
    
    [url=https://github.com/pulser/xposedSMStoMMS]Disable SMS -> MMS Conversion[/url]
    [url=https://github.com/pulser/xposedDisableBatteryFullAlert]Disable 100% Battery Notification[/url]
    [url=https://github.com/pulser/xposedEnableCallRecording]Enable Call Recording[/url]
    [url=https://github.com/pulser/xposedScrollingLauncherWallpaper]Enable scrolling wallpaper in stock launcher[/url]
    [url=https://github.com/pulser/xposedEmailTextColour]Make text in email app message list clearer to read (lighter) on the black background[/url]
    78
    Modifications

    OK so a few people suggested an addon repository... I have got one sorted :)
    Downloads

    http://www.villainrom.co.uk/forum/microdownloads/

    I've added some of mine so far, but I won't add other people's - they can add them themselves, and maintain them :)

    This system is vastly superior to a stickied forum thread, as you can update your own modification (as a developer), and as a user, receive notifications if a modification is updated.

    Developers

    Use a general title that describes what your modification does. Put in a version string too. I tend to use the format 1.0, 1.1, 1.2 etc, but this is up to you. You can add Alpha or Beta or other designations if you wish.

    For author, pop in your name or username. And enter a brief description of what the modification does (which will appear in the index)
    Click Categories/Agreements, and select which category the modification falls under. If you think there's a category which should be added, let me know.

    Under Full Description, you can enter a detailed description of your modification. Finally, under File Options, use File to Upload to select your APK file. You can optionally add an Image to Upload. The Use File URL should be set to no, and the File URL box left blank.

    Users
    • There is no need to register an account to download files from the repository. If you wish to receive notifications of updates, you can register an account - just hit the red "Log in or Sign up" button - you can use a Twitter or Google account if you want, or just make a plain account. It makes no difference.
    • Head across to http://www.villainrom.co.uk/forum/microdownloads/ and have a look at the modifications you want.
    • Click watch file (at the bottom right) if you want notifications about updates to a modification
    • Click Report to report a modification for being malicious or problematic.
    • Click "add comment" to discuss or comment on the modification, or leave a "review" or feedback
    • Click on the stars under (0 votes) to leave a star rating on the modification, which will help generate most popular lists on the main page.

    Click to see licence details of mine:


    Feel free to use these as you wish, for non-commercial purposes. You may share these for personal use. Note that distribution in any kind of "package" or "custom ROM" is not personal use. Sending a friend a copy is personal use, feel free to do that and share the love.

    Feel free to make changes to the source code of the modifications if you think you can improve them, provided you make your changes available in a similar manner. If you fix a bug or error, please send a pull request.

    If you wish to use these commercially, please contact me. This includes in any "distribution package", be it a ROM, app, store, marketplace or other package. That's not in the spirit of this project, so get in touch with me and we'll discuss it.

    Tl;dr:

    End users, have fun, use these, enjoy them, share them, tweak them, just be sure to share your source changes and/or send a pull request if you improve something!

    "Custom ROM" Developers, and anyone wanting to try to use these for commercial purposes: Don't. These are to encourage people to learn about these changes, so contact me if you want to do something else with them. Commercial use, including distribution in "Custom ROMs" is not permitted.
    36
    How to make your own such modification

    This information is NOT complete. This example only uses 1 of about 10 different types of modification. I have spoken to rovo89 and he has said it would probably be possible to document this further. This example covers ONE usage case - I am going to override an entire method.

    1. Create a new empty Android project in Eclipse.
    2. Within the "application" section of your AndroidManifest.xml, add the following metadata:

    Code:
            <meta-data android:name="xposedmodule" android:value="true"/>
            <meta-data android:name="xposedminversion" android:value="2.0rc1.*" />

    3. Within the assets folder of the project, add a plain text file, "xposed_init". Within this, I have put

    Code:
    uk.co.villainrom.pulser.allowlongsms.AllowLongSMS

    uk.co.villainrom.pulser.allowlongsms is the PACKAGE name of my Java package. AllowLongSMS is my class name. The purpose of this is to tell the Xposed Framework what to run.

    4. Within AllowLongSMS.java (ie. the class name, with .java on the end), I put the following code:

    PHP:
    package uk.co.villainrom.pulser.allowlongsms; //this sets the package for our project, this is the first part of the value in xposed_init file in assets.
    
    import de.robv.android.xposed.IXposedHookLoadPackage;
    import de.robv.android.xposed.XC_MethodHook;
    import de.robv.android.xposed.XC_MethodReplacement;
    import de.robv.android.xposed.XposedBridge;
    import de.robv.android.xposed.XposedHelpers;
    import de.robv.android.xposed.callbacks.XC_LoadPackage.LoadPackageParam;
    
    //above includes all the required parts of the xposed framework that we need here
    
    public class AllowLongSMS implements IXposedHookLoadPackage {        //here we declare the class AllowLongSMS. We say it implements IXposedHookLoadPackage, as we want to make use of the hook-in on package load. Other options are available here for working with native libs etc, and resources, but I'm not using these right now.
    	public static final String MY_PACKAGE_NAME = AllowLongSMS.class.getPackage()
    			.getName();     //this doesn't do anything, I just left it here for if I needed to write logs and wanted to have the package name easily accessible.
    	public static final String TAG = "PulserMmsTweak";   //same here, this doesn't do anything.
    
    	@Override //we are going to override the method handleLoadPackage, if it exists further up the hierarchy
    	public void handleLoadPackage(LoadPackageParam lpparam) throws Throwable { 
    		//this method is called every time a package is loaded. We have a parameter that we're going to call lpparam, that is passed in, that relates to what package was loaded
    		if (lpparam.packageName.equals("com.android.mms")) { //if the package that has just been loaded is called "com.android.mms" then
    			ClassLoader classLoader = lpparam.classLoader; //create a classloader object that we can now use
    			XC_MethodReplacement methodreplacer = new XC_MethodReplacement() {  //create a method replacer object, as we are going to REPLACE an entire method within the mms app.
    				protected Object replaceHookedMethod( //we make an object here, that passes in the parameters of what to actually change
    						XC_MethodHook.MethodHookParam paramAnonymousMethodHookParam)
    						throws Throwable {
    					return Integer.valueOf(255);  
    					/* THIS IS THE IMPORTANT LINE
    					 * This line returns the value 255. Why this happens won't make sense yet, but THIS is where you put your "new method" code.
    					 * 
    					*/
    					
    				}
    			};
    			XposedHelpers.findAndHookMethod("com.android.mms.MmsConfig",  //here we say that we want to find and hook into the method "getSMSToMmsTextThreshold" which is part of the class com.android.mms.MmsConfig. We then say that we're passing this to methodreplacer, which we defined earlier
    					classLoader, "getSmsToMmsTextThreshold", methodreplacer);
    		}
                    //if the package wasn't com.android.mms, do nothing.
    
    	}
    
    }
    28
    Mod: Per-app settings

    Here's a new mod for you to try.
    I tested it on my stock S2 4.0.3 and it's working, but you may very well expect problems. Just let me know which.
    I do know that on 4.1.x a few problems occur and this might even be unusable, but I'm still investigating. Feel free to try it out, though, as you can always disable it if any problems arise.

    Per-app Settings

    What it does
    Allows you to configure a number of settings which are app-agnostic, i.e. apply to all of them:
    • Screen size & DPI - fools the resource loader so you can have a layout meant for bigger screens and can control the size of fonts and graphics
    • Language - You can have particular apps in a language other than your system wide language (e.g. system lang in English, but Maps+Navigation in your local language for good voice reading)
    • Revoke permissions - Pick which app permissions you want to deny (and then hope that it will work without them, instead of FC'ing :))
    • Keep apps resident in memory - changes some settings to reduce the chances that memory used by the app is freed (on hold for now)
    By now you should know what to do to get this up and running :p

    Enjoy ;)


    EDIT:
    Replaced with version 0.0.3:
    - removed the need to reboot for the settings to have effect (the target app still needs to be restarted, but not the phone)
    - UI revision to be a bit more intuitive
    - Added setting for tablet mode, required by some apps/resources

    0.0.4 is up:
    - Added a button to list existing folders under /res, so you have some hints about what kind of screen settings you may try.

    To understand the kind of screen settings you need to set in order to have "large screen" layouts, you'll need to peek inside the APK with a zip app (e.g. 7-zip) and browse the "res" folder.
    Look for things like "layout-sw600dp" - this will mean there are resources that are loaded only when the smallest (reported) width is 600 or above, and that's something you can experiment in the settings.
    There is also a general size qualifier which can take the values "-small", "-normal", "-large" and "-xlarge". Checking the "Tablet" box activates xlarge.
    You can read more about how resources for different screen sizes are handled here.