yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] debernardis:
R: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Hello, could it be possible to have the 15 toggles (or 23 toggles, or whatever) mod as an Xposed app?

Thanks all :) and a :beer: to the devs
[Galaxy Note II Original Android Development] ocujos:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Does Call Recorder work on CM10.1? (ie. AOSP/AOKP 4.2.1)
[Galaxy Note II Original Android Development] rovo89:
Version 1.3.2 of Tweakbox is available in the Tweakbox thread for Xposed 2.1+ users, fixes one thing if you want to keep on using the status bar color tweak. No other changes.

To answer your question, yes that could be possible.

However, you probably wanted to know if someone is willing to spend several hours to actually do it. It's easier for Samsung's ROMs which already have some toggles, so their concept can be used and extended. I think there are some major differences between 4.0 and 4.1 stock ROMs in this regard, so a mod would only work for either one and would have do (partly) redone for the other version. But yeah, if someone really wants to have it, it could be worth the effort. Not for me though, as I'm using CM10.1.

There is an easy way to find out:

1. Download the module.

2. Install and activate it.

3. Reboot.

4. Check if it works.

Don't hope for it too much though, I have only seen this particular modification for stock-based ROMs so far. It's as simple as answering the phone app's question "is voice recording possible" with "yes". The actual implementation has to exist already in your ROM. And I think it's an addition by Samsung.
[Galaxy Note II Original Android Development] Zisworg:
I'd like to thank pulser and rovo so much: you did (and are doing) a great job!!

Otherwise, my question is about your (above) answer, pulser: did you eventually work on one of those points? I'm still looking for 3way reboot and battery mod :o

Thanks for reading :)

EDIT: Call recorder and Scrolling_launcher_wallpaper are properly working on GS3 stock rom 4.1.2
[Galaxy Note II Original Android Development] Mundo Hackz:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Okay I got the module XposedAppSettings and now my phone. Apk is small and I wanted to change to big again how do I do it is it thru the android system or systemui.
[Galaxy Note II Original Android Development] MohammadAG:
I did start on the 3 way reboot menu a week ago, but gave up cause I couldn't get it to work.

https://github.com/MohammadAG/Xpose...adag/extendedpowermenu/ExtendedPowerMenu.java

Reason it causes a crash is because of new AlertDialog.Builder(mContext).

logcat mentions something about a null token for the window, but I don't get why, I tried using GlobalActions.java's mContext and PackageManager.java's mContext (dumb, but I was desperate :p).

Edit: exact error:

W/WindowManager( 3436): Attempted to add window with non-application token WindowToken{427b90b8 token=null}. Aborting.
E/AndroidRuntime( 3436): *** FATAL EXCEPTION IN SYSTEM PROCESS: WindowManagerPolicy
E/AndroidRuntime( 3436): android.view.WindowManager$BadTokenException: Unable to add window -- token null is not for an application
[Galaxy Note II Original Android Development] rovo89:
Are there any errors in /data/xposed/debug.log?

Here are some comments about the source:

- for findAndHookMethod in handleLoadPackage, always use lpparam.classLoader

- I would try to avoid references to anonymous subclasses ("GlobalActions$5") wherever possible as it has a big impact on compatibility

- I think all the code you currently have in initZygote is only needed in the system_server (package "android"), so you could move it to handleLoadPackage. You probably should set xposedminversion to 2.1+ as the callback is fired early enough only since this version.

- the PackageManagerService has nothing to do with your code. You also don't really need reflection at all. Once mContext has the correct contents, you can get your reference to the PowerManager inside replaceHookedMethod. Before that point, you don't need it anyway.

- that constructor for GlobalActions doesn't exist (and this should also be mentioned in debug.log). you need to specify the correct parameter types. Or just use XposedBridge.hookAllConstructors(clazz)

These comments are rather generic and maybe not the solution to get it working immediately. But hopefully, they help anyway. ;)
[Galaxy Note II Original Android Development] :
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

last time we had the play button to launch app. it was handy to see the outcome
[Galaxy Note II Original Android Development] Androssama:
It's there :http://xdaforums.com/showpost.php?p=37455436&postcount=744
[Galaxy Note II Original Android Development] dstryrwiz:
How would I go about restoring per app DPI settings after a ROM wipe, or is that not possible? I have tried restoring data to the module, but it seems to just show as if the DPI has been changed, but doesn't actually do anything to the apps in question. Thank you.
[Galaxy Note II Original Android Development] rovo89:
Restoring the data of the App Settings app e.g. with TB should work. Apart from that, you of course need to make sure that the Xposed framework is installed again and that the App Settings module is activated. Also, don't forget to reboot.
[Galaxy Note II Original Android Development] dstryrwiz:
I have all of that and no luck. Under the module it shows all my changes, but they won't actually implement.
[Galaxy Note II Original Android Development] rovo89:
Do the changed DPI values etc. show up in App Setttings? Maybe it helps to go to one of the modified apps and hit the save button again. The settings need to be world-readable, which is not the standard. The permissions should be set again on the next save.
[Galaxy Note II Original Android Development] dstryrwiz:
Tried that and still didn't seem to work. I ended up just rewiping my current ROM to start over for now and I'll try this again likely tomorrow to see if I can somehow get it to work.
[Galaxy Note II Original Android Development] tacchan23:
This mod to eliminate the home button lag could be nice if someone could make an exposed module :)

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

Just an idea!
[Galaxy Note II Original Android Development] AllanJH:
Will TweakBox work at all on JB? It says ICS in the title, but I saw it posted on the Note II forum at one point.
[Galaxy Note II Original Android Development] rovo89:
Some tweaks could work.. but I developed it for a 4.0.3 stock ROM, Galaxy S2. Now I'm on CM10.1, which has many of the tweaks built-in. That's why I don't give much support anymore for Tweakbox. You can try it, see if it works for you, but I'm not planning to add support for more ROMs. If someone is really interested in one of the tweak, feel free to look at the source code and extract it into a separate module, then fix it for your ROM (and maybe others).
[Galaxy Note II Original Android Development] neol23:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

The most functions work on JB 4.1.1, except CRT effect + one or two others, which I don't use ;)...
[Galaxy Note II Original Android Development] zhuchella:
ToALL

Can somebody made the module for cutting off the black line on the incoming phone calls ?
[Galaxy Note II Original Android Development] rovo89:
I mentioned a new module with codename "kolobok" some time ago in this thread. Well, for those who are interested, it's a module to use custom, even animated smileys in the standard MMS/SMS app. As it's device-independent, I have created a thread for it in the general Android section: http://xdaforums.com/showthread.php?t=2138089
[Galaxy Note II Original Android Development] liquidguru:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Fantastic! Working perfectly on monx's latest ROM.

sent from somewhere
[Galaxy Note II Original Android Development] mxpxboi:
Got it working with the Gmail app, and now shows tablet version. But I can't get Words with Friends to do the 10" tablet version. I wanted to try it. Any suggestions?
[Galaxy Note II Original Android Development] kevin_diu:
Hi,

Is there any mod to enable/disable per-app HWUI rendering?? thanks :)
[Galaxy Note II Original Android Development] rovo89:
I think this could be done in the same place as some of the other settings.. however, what's the benefit? If you can get hardware acceleration, wouldn't you want to use it wherever possible? If something doesn't work with hardware acceleration, the developer of the app should have disabled it already and then it makes little sense to re-enable it.
[Galaxy Note II Original Android Development] lncoln:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

I had that issue as well...you have to click the "resident" tab in the individual app settings, of the xposed settings app, that you're trying to change. Then reboot...worked for me.

this...is my BOOM stick!
[Galaxy Note II Original Android Development] rovo89:
Just to clarify: "resident" is to make the app stay in memory for as long as possible. I don't see any connection to the settings. I even tried it myself: Made a backup with TB, killed App Settings, deleted the data storage for the app, restored only data with TB. The settings are still world-readable (which is required because they are applied in the target app) and they still apply after a reboot.
[Galaxy Note II Original Android Development] Mundo Hackz:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

Does the Xposed Installer and modules uses RAM on the phone.. The same as without using them??
[Galaxy Note II Original Android Development] rovo89:
Sure they do use RAM. Not directly the installer (as long as it's not running), but the framework and the modules are always in the RAM because they contain code and variables that need to be stored somewhere. The good thing is that most of that is shared between all apps, so they take the RAM only once. Some modules might initialize additional stuff only for certain apps (e.g. my Smiley Replacer). This memory will be freed together with the app.
[Galaxy Note II Original Android Development] djnoicatse:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

I'm having problems setting then stock Samsung keyboard back to 320 DPI for me to use on my Note 2. System is set at 240dpi and running stock I317MVLBMA3 4.1.2. Just wondering is anyone else is having this issue...Here's a screenshot of what I'm talking about

Thanks in advance
[Galaxy Note II Original Android Development] guthrien:
I tried installing some modules today, but none are working as it seems the XposedBridge.jar was updated? Would it be best to roll back that file?
[Galaxy Note II Original Android Development] rovo89:
Yes, that's a known issue. I haven't investigated why that happens though. Question is, is it necessary to change the DPI of the keyboard? The keys can't be wider than the screen and if the aspect ratio is kept, the height should be fixed as well. But then again, I haven't used the Samsung keyboard for more than the first few days, then I switched to Swiftkey. So maybe there is indeed something weird happening.

No, you should always use the latest version. Instead, make sure that you got the latest version of the modules. All modules created or updated in 2013 should be compatible with Xposed 2.0 final or later (which doesn't necessarily mean that the module will work - some work only for certain ROM versions).
[Galaxy Note II Original Android Development] djnoicatse:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

If I don't change the DPI to stock 320...the keyboard will FC. Tried using a modded keyboard that supports multi-dpi but that doesn't work as well. I've been using 4.2 keyboard but it doesn't play too well with the multi window because it lacks the floating keyboard which the stock Samsung keyboard has.

Thanks for the reply though
[Galaxy Note II Original Android Development] guthrien:
Nevermind, dumb, dumb mistake on my part. The modules were fine, I was installing an older version of the Framework. Ugh. Thank you for your time and reply.
[Galaxy Note II Original Android Development] rovo89:
I'm not sure I understand your question... do you mean whether Jkay's framework could be turned into an Xposed mod?

Jkay has made many many changes. Many of them would probably be possible to re-implement with the Xposed framework. Some are easier, others harder to implement. Usually, the bigger the changes compared to the base ROM are, the longer it takes to implement them. Sometimes the functionality is just disabled, then a tweak can be done very fast.

This is when you know which changes exactly he has made and why - reverse engineering is always a lot harder. And given the amount of changes, there will be some that need to be done differently on different base ROMs. Even if its was possible, it would be very much work.

On the other hand, taking his work as inspiration and re-implementing some isolated improvements could be possible.
[Galaxy Note II Original Android Development] :
Thank you so much for all your help with this. If i understand correctly something that is all ready there can be manipulated so would it be possible to force the auto rotate to work on the homescreens meaning we could use the phone in tablet mode ? That will be a really useful tweak
[Galaxy Note II Original Android Development] ldx00:
This is great! Everybody should click on the Newsworthy thing to get this on the portal. I'm going to look into this too as I find I can't justify moving to CM as the SPen support doesn't quite seem to be there yet. this could make it redundant!
[Galaxy Note II Original Android Development] rovo89:
What I meant is: Sometimes Samsung has already implemented a feature (like call recording), but they have disabled it under certain conditions. These are the easiest tweaks, because you just need to remove the check.

It's also possible to add new features - the effort depends on the feature to be added. The same applies to modifications. There is no general answer to this.

Regarding the auto-rotation: I'm not using the default launcher but GoLauncher Ex. It has support for rotation (but I don't use it), so if the default launcher hasn't, it's a limitation of the app. If it works on tablets, the question is if phones and tablets get the same app, just with a detection which kind of device it is running on. In this case, the code for the rotation would be there and would just need to be unblocked. Otherwise, if the phone launcher doesn't include the rotation code, you would have to write it yourself... and considering that it's not just a simple rotation, but that you probably expect the landscape view to use the space a bit differently than in portrait mode, this could become much work easily.
[Galaxy Note II Original Android Development] :
Thank you for explaining it for me, I understand a bit better now. My thinking was the galaxy tabs use touch wizz and have tablet mode so maybe it was all ready there on the phone and just need activating.

---------- Post added at 09:05 PM ---------- Previous post was at 08:59 PM ----------

@pulser_g2 Would it be possible to make this a sticky and use it as a repository? Hopefuly this would encourage more devs to use XposedFramework to create mods which I think was the whole point of your original post.
[Galaxy Note II Original Android Development] pulser_g2:
Don't worry, you don't need to hit newsworthy :) We're aware of it and will cover it on the news portal when I get time to do a proper write-up that does it justice...
[Galaxy Note II Original Android Development] pulser_g2:
Yeah if the features are there already it's easy to add!

Regarding sticky and repository, yes it is possible but I think we want to wait until I get the time to format up a better post for items. That way people can see what's available. And then it might be worth sticking. But right now I'm not sure it's good enough... I'd like to make it better and less confusing and get all the modifications together, and maybe make a couple more :)
[Galaxy Note II Original Android Development] Tungstwenty:
100% agreed.

It good enough for those involved to be coming back, and those are the ones that matter the most at this stage :)
[Galaxy Note II Original Android Development] pulser_g2:
Indeed, I want to try out my to-do list first too...

Firstly to look at Garyd9's modifications for touchwiz launcher, and try to get the various width and height adjustments possible. Maybe even within a settings UI :D

also I have a few others to look at like power menu mod, and stuff mentioned on the other pages
[Galaxy Note II Original Android Development] coolfire:
Customising the TW launcher would be awesome! I like it lots, but use 3rd party ones because of its limitations to widths & heights... :victory:
[Galaxy Note II Original Android Development] pongster:
Interesting. You got me at "DPI on a per-app basis". :)

Which configuration files would I need to edit to test per-app DPI changes?

Also, I noticed the debug.log show that the CRT Effects in Tweakbox are looking for the file usually available on Jkay's ext.jar (PowerManagerService$BrightnessState) so they currently don't work. Does that mean if we can compile an ext.jar that has this file using native libraries (libsurfaceflinger.so) instead of replacing them would make CRT work? or is this file supposed to be in the patched libsurfaceflinger.so?

Finally, I can confirm that the following tweaks available on Tweakbox work on a Stock based 4.1.1 ROM (HyperNote):

Statusbar Color Change

Skip Tracks with Volume Keys

Turn on screen when unplugging

Market Change DPI

Hopefully I can find the time to tinker and try getting the clock on the statusbar centered and other useful UI tweaks.
[Galaxy Note II Original Android Development] rovo89:
The configuration file for Tweakbox is /data/data/de.robv.android.xposed.mods.tweakbox/shared_prefs/de.robv.android.xposed.mods.tweakbox_preferences.xml

You can insert the following there:

<string name="dpioverride/com.google.android.apps.maps/locale">en_US</string> (language/locale)

<int name="dpioverride/com.sec.android.app.calculator/density" value="240" /> (density)

Also available:

<int name="dpioverride/com.sec.android.app.calculator/swdp" value="600" />

<int name="dpioverride/com.sec.android.app.calculator/wdp" value="600" />

<int name="dpioverride/com.sec.android.app.calculator/hdp" value="600" />

Especially the first one is used as a condition to load the tablet layouts: http://developer.android.com/guide/practices/screens_support.html#NewQualifiers

So while these settings may not have a direct impact, the make Android load the layout that was meant for larger devices (like this).

The Java class PowerManagerService.BrightnessState should be available for a long time in the original Android code. It's the part where the animation is triggered. For the effect itself, libsurfaceflinger.so contains the relevant code. However, the effect flickers for most ROMs and we have implemented the landscape effect (including rotation-awareness) ourselfs by changing the bits and bytes of libsurfaceflinger.so. This one is the critical part.
[Galaxy Note II Original Android Development] pulser_g2:
Added ScrollingLauncherWallpaper which makes your stock launcher wallpaper scroll as you move homescreen.
[Galaxy Note II Original Android Development] D.O.C:
Took a shot at it, and it works great, you can specify individual dpi settings overriding system ones with a single line....thanks for this. What before took hours of fine tunnin each dip and px before on every xml, has become a 30 sec line editing....thanks!

here is an example forcing 320 dpi on camera, launcher, sms, dialer, phone, fm radio, voice recorder, videoplayer, email and calculator :D
[Galaxy Note II Original Android Development] gtizon:
I know this is more for devs but based on my understanding, this is a great idea! Big fan pulser. Props to both of you!
[Galaxy Note II Original Android Development] pulser_g2:
Well it's not really "for" anyone in particular - Rovo's system will only work if everyone from new users, to experienced developers, feels they can and want to use it. :)
[Galaxy Note II Original Android Development] chemcup:
Can you please make mode for stock launcher that can change the number of rows and column?
[Galaxy Note II Original Android Development] pulser_g2:
I was in the process of that and hit a stumbling block...

@Rovo or Tungs,

Is there a way to override a "dimen" using resource replacement? Couldn't figure out how to create the dimen object in Java...
[Galaxy Note II Original Android Development] coolfire:
That would make me go back to TW from Apex!

Take your time, pulsar_g2... :D
[Galaxy Note II Original Android Development] Tungstwenty:
Have you looked at rovo's tutorial on how to replace resources, here (specifically, the Complex Resources section)?

I'm using the exact same approach here to replace the dictionary files of the stock android 4.2 keyboard.

You'd create a resource of type dimension in your mod apk (or as many as you need later on), and then implement the IXposedHookInitPackageResources so you can replace the original value with your own:

resparam.res.setReplacement("_target_package_", "dimen", "target_res_name", modRes.fwd(R.your_mod_res_id));

If you were to do this programmatically, a Dimension resource is represented as a float. But I don't know what will be its value depending on whether the xml resource is in px, dp, ... I think it will take into account whatever DPI, etc. the device is using and normalize all different types to a single scale.
[Galaxy Note II Original Android Development] hazri1974:
Re: Making "Stock" Custom ROMs Defunct (XposedFramework) - Tweaks for any ROM Version

How to flash this xposed app?...error flashing using Twrp....is it not compatible with Twrp?...tq
[Galaxy Note II Original Android Development] rovo89:
Read the first post here: http://xdaforums.com/showthread.php?t=1574401
[Galaxy Note II Original Android Development] Smokinggun:
How to Enable call recording module on updated version
[Galaxy Note II Original Android Development] rovo89:
Install the latest version: http://www.villainrom.co.uk/forum/microdownloads/enable-call-recording.3/viewfile
[Galaxy Note II Original Android Development] EarlZ:
Is the modded MMS.APK with the sent time compatible with this ?
[Galaxy Note II Original Android Development] rovo89:
Well - what exactly should be compatible? Generally, this can be answered best if you just try it. And as the module change just some parts of the system's and applications' code, you will have good chances that the same modules will work as your base ROM.
[Galaxy Note II Original Android Development] EarlZ:
I am uncertain or probably misunderstood on how this works, basically im on a stock rom.. and theres a modded APK for the mms.apk for it to show the sent time, I suppose I would run this xposed framework first then run the modded apk ?