yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] pulser_g2:
Install the Xposed Framework from this thread: http://xdaforums.com/showthread.php?t=1574401
[Galaxy Note II Original Android Development] jerdog:
Awesome work mate. Wish I had a Note 2 to check this on.

EDIT: Wait.. I can use this on any device! Rock on. Thanks!
[Galaxy Note II Original Android Development] chaitanya87:
Wow this is great post. While reading this it makes me learn something like what is going on in background.
[Galaxy Note II Original Android Development] simone201:
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
[Galaxy Note II Original Android Development] pulser_g2:
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...
[Galaxy Note II Original Android Development] pulser_g2:
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!
[Galaxy Note II Original Android Development] simone201:
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)
[Galaxy Note II Original Android Development] pulser_g2:
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 :)
[Galaxy Note II Original Android Development] pulser_g2:
My own notepad of things I need...

http://xdaforums.com/showthread.php?t=1965801

http://xdaforums.com/showthread.php?t=1924905

call record:

http://xdaforums.com/showthread.php?t=1938808

http://xdaforums.com/showthread.php?t=1871525
[Galaxy Note II Original Android Development] Tungstwenty:
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

HOW

s 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.
[Galaxy Note II Original Android Development] sunwee:
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.
[Galaxy Note II Original Android Development] pulser_g2:
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 :)
[Galaxy Note II Original Android Development] astoncheah:
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.
[Galaxy Note II Original Android Development] DirkStorck:
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 !
[Galaxy Note II Original Android Development] pulser_g2:
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...
[Galaxy Note II Original Android Development] DirkStorck:
If I would like to start writing my own mods is there somewhere a guide how to debugg the mod I write?

Thanks!
[Galaxy Note II Original Android Development] iphonest:
one more

can you add:

*:laugh:skip music track with volume button
[Galaxy Note II Original Android Development] pulser_g2:
Addon Repository

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

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

Register for an account (Free, easy, no spam etc)

Go to http://www.villainrom.co.uk/forum/account/join-user-groups

Tick the option for Xposed Uploader, and hit Save. A request will be sent to me for your application. I'll approve it when I see it (should be quite fast, it gives me a popup)

Head back to http://www.villainrom.co.uk/forum/microdownloads/ and click the Upload button at the top right.

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.
[Galaxy Note II Original Android Development] rovo89:
I have changed my global DPI to 192 and then changed some TW apps back to 240 DPI because they seem to be hardcoded for this resolution. Works fine for me. Of course, the mod cannot do magic and display something that doesn't exist. It's just possible to trick the system into thinking it has a different resolution or screen size or so. If there are cases where the resources exist and the app behaves as expected when you change the DPI globally or try the same apk on a real tablet, as much information as possible will help to track down why the changes don't apply.

Do you have any concrete examples? I know that there are many places where the density (dpi) throughout the Android framework. Currently only one of these places is overridden because it's only called once or very few times per app (keeping the performance in mind) and so far does its job very well. The layout that is chosen can depend on a combination of parameters and dpi can be one of them. But the dpi used for this should be overridden already... or do you want to use e.g. 320 dpi resources while using 240 dpi for font size etc.? Not sure if that is possible and if it would work well.

1. No offence, but I think normal font color and size would have worked as well...

2. Which version have you tried? 0.0.3 has a text field for the dpi and I could enter 320 there and save it. Didn't try if it has any effect, but it would be strange if it didn't.

What do you mean with "right now you have default that can be set for all"? You mean the "(default)" in the screen size dropdown? That means "no change" I think. But in general I agree, default settings would be nice and would avoid changes to build.prop. That's only if it works correctly, of course, as I said there are so many places that use it.
[Galaxy Note II Original Android Development] DAGr8:
lol sorry abot the colors , but I linked htis in my thread and I wanted users not to miss it (you know like me some go straight to the good part and forget abou the rest.. )

ok .. I fee l dumb I had wrong apk .. so I edited my post to reflect this ..

as I said the example is systemui .. because of limitations set by android.policy jar in phonewindowmanager tablet ui / phablet ui will only occur under specific dpi , I hacked mine as a workaround but it requires additional changes to an 'already heavily modified systemui this mod tho almost becomes obsolete with this awesome app (see screenshots) ... I was also under the impression that some apps were dependant on this as well but after soem testing it seems I was wrong..

about the no change (default) yes thats what I mean .. I think default shoudl reflect the phone 's standard dpi .. right now if I lower the build.prop to 160 well then everythign becomes default to 160 ...

here are few screeenshots :
[Galaxy Note II Original Android Development] Tungstwenty:
I think this could be done by designing another panel to select settings for all apps at once, unless some of them happen to have individual settings. Or perhaps a whitelist as well, to prevent some of the apps to be affected by those default settings.

That way, you could simply change the default DPI to e.g. 200 except for "android", "...billing", "calculator", etc.

Please remember that this has nothing to do with changing build.prop, which probably changes other things that this mod doesn't (only the resource loading and rendering "zoom").
[Galaxy Note II Original Android Development] rovo89:
@DAGr8: I tried to change the system UI on my 4.0.3 stock ROM to tablet mode. It tried to load the tablet status bar when I used 600x1024 and had the tablet mode checked. But it crashed because it couldn't find some resource (or it was of the wrong type). I think this is what you meant before with the additional resources. I don't know what changes are necessary in the policy, but I guess they would be the smaller problem. But I don't have the time to dig deeper into this now, sorry.

And for the "(default)": not sure what you mean. That's the screen size. It's independent from the density (dpi) and therefore also from build.prop.
[Galaxy Note II Original Android Development] DAGr8:
Well yea.. see my screenshot..

when you set the dpi lower for system ui using this app.. it crashes because it's trying to load phablet mode.. and you don't have the resources by default for this on tw base .. On mine all resources are set.. so it will load phablet..and it would load tablet if the app would allow it..

it won't load is tablet..

whatever settings you use in the app..

system ui won't load tablet unless you lower the build.prop dpi setting..

If you don't wanna spend time hacking your system ui to verify this just use cm base (or is exposed only for tw i forgot) and you ll se what imean

As for the policy jar hack its very simple..you just change 600 (hex )to 320 ( in my case) but as isaid this mod is pretty useless now that we have this wonderful app.. all we really need is a way to handle all dpi in one shot as we discuss earlier..
[Galaxy Note II Original Android Development] Tungstwenty:
In the mod, (default) means "do not change". The same for "0" on the DPI field.

If you hacked your build.prop to have X as the DPI, then that X

is

the default for your device and the mod won't do anything to change it unless you set specific apps to a certain DPI.

As I mentioned above, a better solution might be allowing a default value to be applied to all apps but a few whitelisted ones, without changing build.prop.

For information on how android decides which resources to load, you can read this document: http://developer.android.com/guide/practices/screens_support.html

---------- Post added at 10:27 PM ---------- Previous post was at 10:21 PM ----------

0.0.4 of the app settings mod was added in the previous post.

It now has a button to list the contents of /res/ so you can have an idea of what kind of settings can be tried in order to load alternate layouts that are present.

The simpler resources like strings aren't displayed, though, as they're bundled within resources.arsc and need to be parsed.

Does anyone have any pointers on how that can be achieved from within an android app?
[Galaxy Note II Original Android Development] DAGr8:
must be my english (2nd language for me ) I completely get what the app does , just trying to explain what it doesnt , and why a work around is

"needed " (there is one since pa doesnt chnage the build prop and does swap the mode to tablet ui ) although they do require a reboot for this ..

your workaround solution is fine by me , as what i woudl do is exacttly what im doing right now , set the build.prop to tabletui mod (160) reboot , then go in your app and overide it for all apps 1 by one by setting them all back to 320 (asiode for those i want dual panel or lower dpi )

so if you add the ability to set it to *dpi globally that works for me and for any aosp base rom aswell ..

as to parse the arsc file im sure its doable but at what cost ? I thinnk that part of the app is perfect butthats just my opinion ..
[Galaxy Note II Original Android Development] turilo:
Excellent :D

Sent from my Galaxy Note 2
[Galaxy Note II Original Android Development] lpsi2000:
Maybe I missing something here because you are saying this current mod can do this. If that is the case why don't you try the dialer at 240 and see how it scales on the screen.

I am not sure I failed to say what I wanted to say but my questions had nothing to do with systemui or the Samsung keyboard which are different issues in my book.

1.Samsung keyboard seems to be hardcoded and no one has gotten it to work yet (unless you force to 320).

2. SystemUI is a different issue all together especially when it is related to the tablet mode. BTW with the current mod, we are able to get to the so called Phablet Mode.
[Galaxy Note II Original Android Development] markkohfm:
Like what Dagr8 mentioned, the TW apps do not have the resources to display the apps at the manipulated DPI so there is no way anything can be done for it to scale nicely unless you manually create these resources. There is no way this framework can create those resources automatically.

With this app, at least you have the ability to work with a much lower DPI i.e. 160, and yet have the TW apps to work nicely albeit at 320 or 240 with the modded apps available.

Good enough for most of us I suppose, or at least for me.
[Galaxy Note II Original Android Development] rovo89:
Wouldn't it be easier to identify the place in the code where the density is checked and trick it into thinking it should load the tablet UI? However that may work, this can be decided when we know which criteria trigger the decision and what happens based on this decision.
[Galaxy Note II Original Android Development] lpsi2000:
Okay, then maybe DAGr8 can help us understand what he does to a few of these apps to make them scale at any DPI. For example his modded version of the calculator or dialer in his ROM scales any DPI.

I agree the framework would not create the resources, but I also don't think the resources are created manually to make it at any DPI. That would be creating resources for possibly each DPI. Here is an example http://xdaforums.com/showthread.php?t=863519 on how this was being done a couple of years ago. I am sure things I have changed since then.

---------- Post added at 08:55 AM ---------- Previous post was at 08:53 AM ----------

Agreed that would be much easier and better than the workaround.
[Galaxy Note II Original Android Development] jager13:
+1

I thought it was a buggy restore, so I uninstalled it and reinstalled it again, it opens up normaly and prompts u to either to sign in or register. after u sign in, it crashes!

Just pointing out what happened, maybe it'll be helpfull for the fix :)

PS: Amazing work guys, seriously the per-app dpi is awesome :) thx!

Request: add more colors to ink effect and if it possible to add an exit button on google chrome...

Noted!
[Galaxy Note II Original Android Development] Lennyuk:
A fix is in the works for this, when the framework gets an update.
[Galaxy Note II Original Android Development] Linuxx84:
If I want to delete Xposed I have to click on Unistall (restore app_process) and Clean up (complete removal of the framework), right?
[Galaxy Note II Original Android Development] rovo89:
Clean up includes Uninstall, so if you only need the former. Uninstall keeps the debug log etc.
[Galaxy Note II Original Android Development] DubelBoom:
Hi!

Great mod! I've been waiting for this :)

Only one thing - can you add an option to set tablet mod to all apps at once? Because I want everything to be tablet mode, expect Sammy's apps that will FC...

Thanks!!
[Galaxy Note II Original Android Development] nintendolinky:
Can we have extended power menu with this framework.
[Galaxy Note II Original Android Development] DAGr8:
well yea all in one is waht we all want ..

as for what lpsi mentionned . theres no magic here . systemui is ust long to mod all the ressources .. all im really doing is adidng the layouts form tablet to the systemui , as for dpi .. the good ole dpi to px is all im doing
[Galaxy Note II Original Android Development] Tungstwenty:
What I suggested earlier (perhaps I wasn't clear) was improving the mod so it included another panel where you could set:

- default global settings, which would be applied to all apps except for...

- a list of apps that shouldn't use that global setting

With this in place, doing what has been discussed would be a matter of faking a certain screen size and/or checking the "tablet" option, and checking apps that would ignore that global default.

Apps on the current list that have individual settings would naturally override the default values (and even the exclusion list).

On top of this, something that needs to be tested is what will happen if 2 different DPI values are set:

- one for the rendering, sort of a "zoom level"

- another one for the selection of which layouts, drawables, and other resources to load

Currently the DPI value is used for both situations, but I'll try to test using a different one for the resource loading part. Examples: hdpi(240), xhdpi(320), even if the rendering DPI is set to, say, 180 for smaller contents when drawn on the screen.

I'm a bit busy right now and still didn't have the time to even push the sources to github, so I'm not sure if I'll be able to add this stuff in the next few days. The sources are my priority, so that some of you guys can help a bit with the experiments as well :p
[Galaxy Note II Original Android Development] lpsi2000:
I think you are on the right track for what I am asking.
[Galaxy Note II Original Android Development] corelle:
Wish it was a easier was for Noobs lol
[Galaxy Note II Original Android Development] f3w1n:
@Tungstwenty Is possible to change the dpi for framework-res.apk? and i dont know abaut twframework.apk but maybe there are graphics there aswell.
[Galaxy Note II Original Android Development] pulser_g2:
That's what I'm working on right now!
[Galaxy Note II Original Android Development] nintendolinky:
Can advanced power menu be added using this please.
[Galaxy Note II Original Android Development] hkfan:
For call recording module ...Is it possible not to remove call management button and add a small Red recording button just below the "extra volume" icon.

Just an idea....if no one like then ignore it

Screen shot here

View attachment 1573690
[Galaxy Note II Original Android Development] DAGr8:
Its called android system as for the tw one is not needed ...
[Galaxy Note II Original Android Development] sling:
Enable Call Recording was a no go on ATT Cleanrom3.3 which is puzzling seeing its N7105XXDLK7 4.1.2 Base.

Any info on how to make it work...changes needed I'm up for the challenge.
[Galaxy Note II Original Android Development] geovass:
This is absolutely great effort! 0.0.4 works great on 4.1.2 (Play) ROM.

Thank you
[Galaxy Note II Original Android Development] hkfan:
Working great on my Note 2 with 4.1.2 ...changed to tablet mode for gmail, email, youtube and all work great..

There should be option to take backup of settings....its not easy to configure it every time we flash rom.
[Galaxy Note II Original Android Development] Tungstwenty:
I have uploaded version 0.0.5 to the repository created by pulser: http://www.villainrom.co.uk/forum/microdownloads/xposed-app-settings.5/viewfile

Sources are also now pushed to github.

Note that for version 0.0.5 the package name has been changed, so you can uninstall the previous version and stick with the new package.

Settings can be maintained if you copy "/data/data/tungstwenty.xposed.perappsettings/shared_prefs/ModSettings.xml" to "/data/data/de.robv.android.xposed.mods.appsettings/shared_prefs/ModSettings.xml".

Once you do this switch, you can backup and restore the latter file whenever you want to keep the settings (pay attention to the owner and group - new package user - and permissions - 664).
[Galaxy Note II Original Android Development] nidhish91:
The scrolling wallpaper didnt work for me :/

I have enabled and rebooted my cell but no change. :|
[Galaxy Note II Original Android Development] turilo:
noticed changes are not working or sticking in new app, but could be my backup xml might just start over with new update
[Galaxy Note II Original Android Development] pulser_g2:
I'll investigate that... Are you using stock Samsung launcher?
[Galaxy Note II Original Android Development] nidhish91:
yes I am. I got the extra column on desktop but not the scrolling wallpaper
[Galaxy Note II Original Android Development] :
I noticed that as well. The scrolling wallpaper stopped when the extra row of columns was added to the mod. It worked fine until then. It does seem to work with other launchers though
[Galaxy Note II Original Android Development] pulser_g2:
Indeed guys, seems on 4.1.2 that's changed. I'll add it to my to do list.
[Galaxy Note II Original Android Development] Jonous:
Font color

Can we change the statusbar font color in any way?
[Galaxy Note II Original Android Development] nidhish91:
I am on 4.1.1