yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Original Android Development] GezDixon:
Loving the app setting mod but after changing the touchwiz dpi to 270 the notification badges are not round anymore.

Anyone know a fix?
[Galaxy Note II Original Android Development] Austin3161337:
Guys does this include skipping tracks with volume rocker when the screen is off? If so.. This is so awesome!?
[Galaxy Note II Original Android Development] :
That's one of the options in tweakbox
[Galaxy Note II Original Android Development] Austin3161337:
I installed it but it says it's incompatible with 2.0b2 so it's disabled very important feature for me. Thanks
[Galaxy Note II Original Android Development] emprize:
install the updated version framework
[Galaxy Note II Original Android Development] RomBox:
thanks, that did the trick. side effect is that the lock screen now have very small buttons :victory:
[Galaxy Note II Original Android Development] dr.ketan:
Call recording and allow long SMS module available for new framwork?
[Galaxy Note II Original Android Development] Tassos_i:
+1
[Galaxy Note II Original Android Development] Austin3161337:
What should I do here it says I have the latest framework installed or do you mean install the latest tweakbox?
[Galaxy Note II Original Android Development] neol23:
Pres install/update and restart after it. It should say active version 2.0.1 when ready.
[Galaxy Note II Original Android Development] emprize:
uninstall it and download it from op post, it should be 2.0 instead of 2.0rc
[Galaxy Note II Original Android Development] jamesalfred:
I'm having a problem applying this to a Korean Galaxy Note 2. The SMS character limit is only 80. I installed the AllowLongSMS module to no avail. Then I realized, the MMS application in this phone has a slight different name. It's called "SecMMSKor.apk". Any solution to this? I'm really desperate.....
[Galaxy Note II Original Android Development] neol23:
Messeging -> Settings -> Input method -> Automatic

Try it ;)...

...

Nope, do not work with latest version :(.

I hope all old mods will be fixed to work with 2.0 as well...

Anyone? :)
[Galaxy Note II Original Android Development] dr.ketan:
I know that, i have just asked for new module if available.

Anyway New tweak updated and call recording included in it.
[Galaxy Note II Original Android Development] titooo7:
Where can I find that new tweak app? I was also pending of an update of the call recording mod.

Enviado desde mi GT-N7100 usando Tapatalk 2
[Galaxy Note II Original Android Development] rovo89:
http://xdaforums.com/showthread.php?t=1629653
[Galaxy Note II Original Android Development] Isriam:
Wow, could you put that on the mod site also? That's an amazing tool.
[Galaxy Note II Original Android Development] nerys71:
bala_gamer manually modified the Note II keyboard to work at 240dpi. goto his thread to download the apk. tonight when I get home will post the link.
[Galaxy Note II Original Android Development] rovo89:
Yes, eventually I think I will put it there. But I'd like to remove some stuff first and add more limitations about when which feature is expected to work and so on. The thing is... I'm in the process of switching to CM10.1. Now like 90% of the tweaks are useless for me because either they are integrated in CM already, I didn't use them anyway or they are not important enough for me to spend time implementing them again. Especially the first point puts me in a bad position to support the module in the future. I haven't decided yet what to do with that...
[Galaxy Note II Original Android Development] _TB_TB_:
You should get more devices! ;)
[Galaxy Note II Original Android Development] jujuburi:
Oh God! Kindly don't forget us, the non CM people.

Sent from my GT-N7100
[Galaxy Note II Original Android Development] Isriam:
I used cm7 to cm10 and after seeing the speed of note 2 with stock rom I think I'll stay sick for tv out. Good luck though and thanks for the great mods.
[Galaxy Note II Original Android Development] rovo89:
I'm pretty sure that the framework will always be compatible with the major ROMs. I spend much time to improve the framework, installer etc. Fortunately, these things are quite portable. Some adjustments were necessary between 4.0, 4.1 and 4.2, but that was a low percentage of the framework. Changes between different ROMs of the same Android version are even less, I think there is currently only one such differentiation. Whenever something doesn't work on another ROM, we rely on people to report it, along with logs and the will to test possible fixes.

Tweaks are mostly smaller changes in a ROM. And they can be quite specific to a certain ROM or vendor, which makes them hard to port. Development involves of course much code analysis to find the right spot to modify. But it's absolutely necessary to just try things out, write some log messages, see if it works. If I can't test it on my device and have to compile the APK, then give it to someone, explain them what to try, get their feedback, change the code accordingly and start all over again, it takes much longer to create a module. And then I don't even have a personal benefit if it's not for my ROM.

This is one of the reasons that the framework and my modules are open source. Other people who have that device and are interested in the tweak can try and implement/fix it themselves. That's usually easier than starting a new module as there are already some ideas around how it works on other ROMs, but maybe it just needs that one more replacement or so. I'm happy to accept pull requests on Github or patches to add support for more ROMs and features (I don't remember getting anything so far).

So please understand that with the limited time I have, I focus on the tweaks I would personally like to see and actually find useful. I also don't really take feature requests for tweaks (but I do for framework improvements). When I create something, I will share it, so other might use it, learn from my ideas and implementation and maybe even fix it to work with their favorite ROM. While doing so, they will develop their own ideas for new tweaks. Don't just rely on a few developers to create modules, become a developer yourself. After all, you're on a site which has "developers" in its name. ;)

Btw, I'm currently working on a tweak I wanted to have for a longer time (codename: "kolobok") and as far as I can see, it might even be compatible with my S2 4.0.3 stock ROM. :)
[Galaxy Note II Original Android Development] OXINARF:
Humm... I'm curious now.
[Galaxy Note II Original Android Development] arvin2212:
Hello.

I am running on Romov V5 (DLK7) for Note 2 with simplistic control installed (not sure if relevant).

Installed the newest Xposed framework. Installed the NFC screen off module. Installed the Swype module as well.

They don't work. Is there something that i missed? I followed the instructions such as reboot etc and yet it doesn't work. :confused:

I'll attach the debug.log

*renamed it to debug.txt

Thank you.
[Galaxy Note II Original Android Development] markkohfm:
Any one experiencing a lag when writing in s note?

Un-installing the framework solves the problem. Happens only with framework 2.0. Am using Deadman rom on a note 2.
[Galaxy Note II Original Android Development] nerys71:
I am also experiencing pretty annoying intermittent lag. I notice it most in camera/gallery where it is not as responsive a lot intermittently.
[Galaxy Note II Original Android Development] stevehkim:
Is this only for inter. S3? And note 2? Tried on my wifes att s3 and wouldnt boot so i flashed the cwm zip and all is good.

SGS3 JB 4.1.2 Ktuned Kernel
[Galaxy Note II Original Android Development] rovo89:
@arvin2212: I can't see anything about Swype there. Is the module activated? Apart from that, it shows that the NFC mod is enabled and that there are no error messages, neither from the framework nor from the modules. The description of the NFC module says that there is a settings screen which you can either start from the launcher or by clicking on the module name in the Xposed Installer. Maybe you need to configure something there before it works. If this doesn't help, you'll have to wait for a reply by qwerty12, the author of these modules.

@markkohfm, nerys71: I can't really tell how a ROM feels without Xposed as I've been using it since I started development in March last year, but I didn't recognize major lags. And it's pretty hard to find the reason for the lags as the framework is quite big meanwhile and lags don't produce log messages which could help tracking the problems down. If you disable all modules and restart, are the lags still there? Cause if it is a module, chances are much better that the reason can be found as they have usually only a few lines of code.

@stevehkim: It should basically work with any Android phone with an ARMv7 processor and a 4.0+ based ROM (except for those where major changes to the internals of the Android platform have been made). As the phone is working again now, could you please post /data/xposed/debug.log (and debug.log.old if it exists)? Maybe some errors are listed there. If the files don't contain anything like "error" or "exception", these files won't help though. Then I need a logcat of the booting attempts. If adb doesn't work at that time, start the phone normally, make sure adb logcat works, install the framework and then soft reboot. Only the Android processes will be restarted, adb will still work.
[Galaxy Note II Original Android Development] nerys71:
don't know. I thought it was coincidence but others are reporting it. it appears to ONLY happen when I load an app that is set for 320 dpi ?? not sure if that matters.

app setting is the only module I have installed right now. everything else is "standard" for my installs and never displayed the lag.

its intermittent enough that I have ignored it just figured to mention it since someone else mentioned lag.
[Galaxy Note II Original Android Development] arvin2212:
This is after I removed the whole framework. I then reinstalled the framework and installed the NFC module only.

The setting screen of the module provides 2 options, that is either the NFC is activated when the screen is off, or only when the screen is on (Lockscreen) neither of which works.

Edit: The other modules work fine such as (PlayStore link in app settings) but the NFC doesn't work although it is enabled. I assume that the problem lies with the module itself.
[Galaxy Note II Original Android Development] rovo89:
It could matter. As I said, lags are hard to debug and even more if they only appear sometimes. So it helps to know in which situations this occurs. If the lag is ignoreable, it might not even be worth tracking this down. But if it's annoying enough, try it with different settings. Try first if it occurs without the framework (over a longer period). Then see if the lags appear with the framework enabled, but without any modules. Then enable app settings, but use default values for the app (i.e. don't change dpi etc.). This way, you can hopefully isolate the issue.

@arvin2212: Ok, then you have to wait for qwerty12.
[Galaxy Note II Original Android Development] dyehya:
I tried searching but Tapatalk search sucks. I installed app and installed the framework and on initial reboot my phone wouldn't finish booting. Sprint Galaxy S III LJ7 deodexed and customized with KT's kernel and 240dpi patches. Any ideas?
[Galaxy Note II Original Android Development] qwerty12:
Hi,

A simple test: disable the NFC module, install another module (preferably one that requires no configuration) and see if that loads. I just deleted the nfclockscreenoffenabler data folder and rebooted and the module still enables NFC at the lockscreen (its default behaviour). With a log that contains no errors and the preferences part of the NFCLockScreenOffEnabler working correctly in the case that no settings file exists, I have no idea what's going wrong.
[Galaxy Note II Original Android Development] arvin2212:
Hello,

I installed the "PlayStore in App Setting" module and there is a playstore link when i go to the application settings and click on an app that was installed through the playstore.

Should i do what you did? Install the NFC Module and then delete the data folder? If so , where do i find the data folder?
[Galaxy Note II Original Android Development] qwerty12:
OK, that means that there's something wrong with my NFC module. As to what, however, I have no idea :(

There could be an additional check I'm not taking into account; however, I used AOSP code to figure out properly what ApplyRouting does on my I9300 and the N7100 and Samsung didn't deviate heavily from that code for those phones with the normal ROM.

Android's normal "Clear data" option should work, just find NFC LockScreenOff Enabler in the application settings. Reboot and see if it's still not enabling. Afterwards, you can force the preference file to be created by switching settings in the NFC LockScreenOff app (set it back if you want the original setting).

That said, I don't really support unofficial ROMs as I have no idea of the sorts of butchery that goes on within. I can try to help, but I only test - and really expect the module to work - on stock I9300 ROMs only. According to Google Romov V5 (or Romov Extreme V5) doesn't exist so I can't find the Nfc.apk you're using. The Nfc Service app should match the firmware version you're running. Let me know, please, the results of checking that.
[Galaxy Note II Original Android Development] arvin2212:
Appreciate your reply.

Tried your suggestion but it is still not working.

The Rom that I am current using is Here

He has however changed it to V5 Extreme. I am not on that ROM. I am using the one released on the 1st of January (DLK7).

Do you want me to upload my nfc service.apk?

If not, should i go back to a stock 4.1.2 ROM? Will this mod work on stock 4.1.2?
[Galaxy Note II Original Android Development] qwerty12:
Yes, please (it's in /system/app/Nfc.apk) and I'll see if there's any big differences between the one on my S3 and the one (if I can find it) in a N2 stock ROM
[Galaxy Note II Original Android Development] arvin2212:
Here you go :)
[Galaxy Note II Original Android Development] stevehkim:
Here's the debug log. I'm running a ported tw based ROM on my att sgs3. Ported over from T-Mobile. Wicked jb v5 4.1.1
[Galaxy Note II Original Android Development] rovo89:
I think you forgot the attachment. ;) And just a reminder: Error messages are quite obvious. If the file doesn't contain any, please also attach a logcat from the boot attempt.
[Galaxy Note II Original Android Development] porkandbeans:
With the new Xposed Installer 2.01, the only module working is the Xposed App Settings. I get the following errors with the other modules! Can someone please help!
[Galaxy Note II Original Android Development] dyehya:
Since my phone won't boot successfully after I install the framework (without loading any modules) I was wondering if it stores a dump somewhere or what I need to provide to troubleshoot it.
[Galaxy Note II Original Android Development] rovo89:
It does store a log at /data/xposed/debug.log. However, if you could grab a logcat during the failing boot process, that would help.
[Galaxy Note II Original Android Development] antiochasylum:
What do you need help with!? They don't work, that's pretty obvious. Lol.

They need to be updated for the new framework in order to work.
[Galaxy Note II Original Android Development] DAGr8:
Multi dpi mod .= rendering unit changed from dip to px.. x2 meanin a mod that would globaly change both ressources like dimens and xml dip units .. this should work accross the board for any apps .. I dont think this could be done with xpos ed but its truely a simple mod... and would work for any fw.
[Galaxy Note II Original Android Development] dyehya:
Zipped logs attached. I did the boot-time logcat as well as the debug.log Thanks in advance!
[Galaxy Note II Original Android Development] EP2008:
Me too.

It's like a ghost is controlling the app for a few seconds. Annoying to say the least, so I hope a fix is found eventually.
[Galaxy Note II Original Android Development] nerys71:
The lag I noticed was in gallery. I would "swipe up" to look at more pictures and it was not respond to my touch. but did respond if I hit back. I pulled out the stylus thinking my fingers were too cold or something (even tried licking them works most times I have dry skin) but by the time I got the stylus out the lag was gone for the moment.

I have not NOTICED any lag lately though so it might have just been new rom lag ?? but also have not used it heavily the last day or so either. we shall see. I will try to keep notes in case it helps if it happens again.

I am running stock deodex ljc sprint.

would really love to have screen off nfc working :)

I just installed the new 1.1 2.0 compatible version.

it still does not work. although it does work better than before. it works from the lock screen (both options) but neither option works from screen off.

also how in the world do we know if a mod is 2.0 compatible? (without having to just try it :)
[Galaxy Note II Original Android Development] dr.ketan:
I have made repository here according to framwork version

http://xdaforums.com/showpost.php?p=31987959&postcount=8

@ Developer

If you don't wish to share direct link there, kindly let me know and it will be highly appreciate if you provide direct link yourself.

I have already added sources and gace credits to deveoper, still I am sorry if missing anyone please headup

Regards
[Galaxy Note II Original Android Development] rovo89:
Sorry, I don't get what you are saying.. I mean, I don't understand the sentences. If this was directed at me, could you please rephrase it?

Thanks. Crash in the binary... too bad, because the crashdumps are hard to read. But I'll have to look into it.

See my post here: http://xdaforums.com/showpost.php?p=36348178&postcount=454

Well, thanks for the effort, but there is already a repository: http://www.villainrom.co.uk/forum/microdownloads/

So I don't see the need to list basically the same information again. The main problem with your list is that the authors cannot update it themselves, so the list will likely become outdated soon. Just for example, I have released version 2.0.1 of the installer a few days ago, but you still mirror the 2.0 version. I won't support older versions and I think most module developers see it the same way.

I can partly understand that you link to the 2.0 rc2 version of the framework because some modules are not yet updated for 2.0. However, the hotfix version you offer for download was signed by Tungstwenty, so updating it to the latest version requires uninstalling the old version first. And again: No support for older versions.

Finally, you should mention the developers for each module. qwerty12 has developed at least the NFC module (plus some other nice tweaks).

By the way, Tungstwenty's per-app settings module was presented on the XDA Portal: http://www.xda-developers.com/android/per-app-dpi-adjustment-for-the-galaxy-note-2/ (unfortunately it sounds as if "Nop Ph473" had written it, I already added a comment regarding that).
[Galaxy Note II Original Android Development] dr.ketan:
My effort only was there to remove confusion for user, which module to use for which framework.

Main issue is that there is many modules available for older framwork but not for newer. So user can atleast continu using older framwork, who needs till they dont get newer update.

But I can understand when this one is different works developed by different developer, and difficult to make collection under single roof.

Therefore with all due respect to developers, I am removing that post competely.

Again Sorry!
[Galaxy Note II Original Android Development] jujuburi:
Indeed. Think about the new users, not everyone read this topic everyday like me. Those who come and see this topic will find Xposed Installer 2.0 or 2.01, and they will then be redirected to that website, Villainrom, and will download the modules without knowing that only one will work and others will not. This is pretty confusing, as nothing is mentioned aside the modules that if they are compatible with the new installer or not.

Yeah, I know, we all know that devs have no time as they have plenty work to do, that's why they will do when they will do, but we all have work to do and to all of us time is pretty important, not everyone has to be a dev, nor everyone has to be an economist like me, but I do respect others work, and in return I expect the same, is that weird or normal?

No offense, but how long could it take to add a line to the modules that, this is compatible with Xposed 2.0 RC, or 2.0 or 2.01!

:)

Sent from my GT-N7100
[Galaxy Note II Original Android Development] rovo89:
Ok, I can understand that. May I suggest something instead? You could link to the module pages (like http://www.villainrom.co.uk/forum/microdownloads/xposed-app-settings.5/viewfile) instead. Then users will always get the latest version. For the framework version 2.0+, just link to the framework thread.

As all new or updated modules will very likely be compatible with framework version 2.0 or later, you could also just list the modules which are available for rc2 (in the same form as you had, plus the link to the module page) and add a note once once they have been updated to 2.0. If a module isn't listed, it means that it is only available for 2.0+. Once all modules have been updated, the list wil become obsolete.

I really appreciate your efforts, I just want to make sure that it doesn't create confusion in other parts (when it comes to supporting the modules). If users don't update, they might run into problems which have already been fixed in a new version.
[Galaxy Note II Original Android Development] Tungstwenty:
I think the best person to clarify this would be pulser.

He created the repository, which is IMO the best way to publish mods as each author can update their own creations, gather feedback on each mod, etc.

What possibly could be improved is requesting each mod author to include additional info on the repository, such as:

- framework compatibility

- know ROMs / devices where it works or doesn't work

- link to sources if they're public

- etc.

Mirroring, even if pointing to the entries instead of direct downloads, will always be one step behind as those kind of "collection" posts will always be lagging against new entries or updated ones.

EDIT: I have updated the repository entry for XposedAppSettings to include the info above. Perhaps other devs can do the same for their mods.
[Galaxy Note II Original Android Development] pulser_g2:
I am currently updating the modifications for the 2.0.* API, but then I see quotes like this:

Well... quite a while when you're also trying to help run a site like XDA...

I will upload them and add compatibility information. This was a one-off "big update" from what I understand :) I don't think this will become regular.
[Galaxy Note II Original Android Development] dr.ketan:
@rovo and tungstwenry

I respect your opinion, but you can understand what problem occurs here, here modules created by many developers and all having their own wish and opinion (they are best person to judge and I respect their choice too)

But my wish was that till we don't get all modukes update user can continue using old framework with maximum modules e.g. myself using older one bcoz some modules are not available for newer framework.

So I am finding other way to make clear instruction under same post

Just I am seeking assurance from developers to keep older module available for download. And even I can make separate thread and just mentione liwt of framework and module link to original thread.

So they can link to that thread to download, there is repository already there but no clear instructions available which module works for which.

But I will make it only, if developers will happy for that. And we contributers are just helping end user to get thing easy when developers are quite busy.

Respect to all developers.

Edit:

Thank you pulser and tungstwenty for updating info

If there is info available there then nothing more requires

Thank you again all.